From owner-freebsd-questions Wed Dec 12 11:54: 5 2001 Delivered-To: freebsd-questions@freebsd.org Received: from nelly.internal.irrelevant.org (irrelevant.demon.co.uk [158.152.220.121]) by hub.freebsd.org (Postfix) with ESMTP id A2D9A37B509 for ; Wed, 12 Dec 2001 11:53:45 -0800 (PST) Received: from simond by nelly.internal.irrelevant.org with local (Exim 3.33 #1) id 16EFOb-000Bjb-00; Wed, 12 Dec 2001 19:50:25 +0000 Date: Wed, 12 Dec 2001 19:50:25 +0000 From: Simon Dick To: Kevin Oberman Cc: Doug Reynolds , Dimitri T , "questions@freebsd.org" Subject: Re: the door is closed! Message-ID: <20011212195024.GA44104@irrelevant.org> References: <20011212140915.974E637B417@hub.freebsd.org> <200112121930.fBCJURd28098@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200112121930.fBCJURd28098@ptavv.es.net> User-Agent: Mutt/1.3.24i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Dec 12, 2001 at 11:30:27AM -0800, Kevin Oberman wrote: > > From: "Doug Reynolds" > > Date: Wed, 12 Dec 2001 09:08:24 -0500 > > Sender: owner-freebsd-questions@FreeBSD.ORG > > > > On Wed, 12 Dec 2001 08:04:45 +0000 (GMT), Dimitri T wrote: > > > > >i've just installed freebsd and i'm trying to login > > >for the first time but this seems impossible. > > > > > >i'm sure that during the installation i've typed the > > >word 'secret' as the root password but after rebooting > > >this password is not accepted! :( > > > > > >after this i've booted in single mode but when i give > > ># passwd root > > >and try to set the password, i get a "read-only file > > >system". vipw won't do it either.. > > > > boot single user, to get a writeable file system, i do this: > > > > umount -a > > mount -a > > > > that unmounts all systems, and mount remounts all as writeable, then > > run passwd > > While this works, it is just slightly risky. The handbook recommends: > fsck -p > mount -u / You don't actually to do this stage, mount has a special case handling the root filesystem that automatically assumes this flag on the mount -a call. > mount -a > > The first command is important as it makes sure that FS is fully > consistent before allowing writes. (It is probably not really > important on volumes running soft updates.) It's still a good idea :) -- Simon Dick simond@irrelevant.org "Why do I get this urge to go bowling everytime I see Tux?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message