X Window problem
a.carter at cordis.lu
Tue May 6 03:09:28 PDT 2003
Strange then...Whenever I have booted into single user mode I have been unable
to write to the root partition, even after a mount -a...even with ESC w!q in
vi...Maybe I did something wrong...Would it possibly be likely that mount -a
doesn't report back that / needs fscking first? Everytime I have had to do
this I needed to fsck root first...
Just a thought,
On Tuesday 06 May 2003 12:05, Matthew Seaman wrote:
> On Tue, May 06, 2003 at 11:31:12AM +0200, CARTER Anthony wrote:
> > I think that you should do this first:
> > mount -u /
> > this re-mounts root as read-write, otherwise you are in read-only in
> > user mode...
> > then do:
> > mount -a
> > swapon -a
> Actually, although the handbook recommends 'mount -u /' in
> as does the FAQ in
> it hasn't strictly been necessary for at least a year now. 'mount -a'
> will automatically re-mount the root filesystem read-write anyway. If
> the original poster was following the instructions, that wouldn't have
> been the cause of their latest problem.
> > On Tuesday 06 May 2003 11:15, Eduardo Viruena Silva wrote:
> > > On Tue, 6 May 2003, Gary and El Byrnes wrote:
> > > > I got to the point where I edited the /etc/ttys file back to what
> > > > was. When I tried saving it, I got a message that the file is
> > > > and use ! to override.
> Seems that your /etc/ttys file has ended up without write permissions
> --- that's non-standard: the mode is usually 0644 --- but so long as
> everything has read permission that needs it, won't cause any
> If you're in single user mode then you have superuser powers: you can
> just override the filesystem permissions by:
> Esc : w q !
> from within vi(1) and everything should end up the way you want, and
> you can get on with generating a working X configuration.
More information about the freebsd-questions