Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Nov 2001 01:24:32 +0900
From:      Makoto Matsushita <matusita@jp.freebsd.org>
To:        freebsd-current@FreeBSD.org
Subject:   RE: Sysinstall is still horribly broken.
Message-ID:  <20011121012432J.matusita@jp.FreeBSD.org>
In-Reply-To: <XFMail.011119153627.jhb@FreeBSD.org>
References:  <20011120082101T.matusita@jp.FreeBSD.org> <XFMail.011119153627.jhb@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

jhb> Err, well, when we run fsck on an existing partition, we
jhb> shouldn't say 'fsck /dev/ad0s1a', we should use 'fsck_ffs
jhb> /dev/ad0s1a'.  Does that make sense now?  We shouldn't be calling
jhb> fsck_4.2bsd for these filesystems because they aren't 4.2BSD file
jhb> systems per se, they are FFS, possibly with softupdates.

That's make sence to me.  We only run fsck to FFS, so it's safe to
change 'fsck' to 'fsck_ffs'.

jhb> With devfs /dev should have all existing disks and partitions.
jhb> At least if you open the device it will create it for you if it
jhb> is valid.  We should always use the devfs /dev if it is present
jhb> and fall back to /mnt/dev from the CD if it is not.

Maybe we can try to put mount_devfs and mount devfs to /mnt/dev.

-- -
Makoto `MAR' Matsushita

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011121012432J.matusita>