Date: Fri, 9 Jul 1999 14:22:47 +0000 (GMT) From: Renier van der Walt <renierv@insnet.net> To: Ladavac Marino <mladavac@metropolitan.at> Cc: freebsd-questions@FreeBSD.ORG Subject: RE: FreeBSD 3.2 question stuff Message-ID: <Pine.LNX.4.10.9907091418140.21250-100000@vampire.uk.insnet.net> In-Reply-To: <55586E7391ACD211B9730000C11002761796EB@r-lmh-wi-100.corpnet.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 9 Jul 1999, Ladavac Marino wrote: > > -----Original Message----- > > From: Renier van der Walt [SMTP:renierv@insnet.net] > > Sent: Friday, July 09, 1999 3:31 PM > > To: freebsd-questions@FreeBSD.ORG > > Subject: FreeBSD 3.2 question stuff > > > > Note: If there is not a /usr/src/sys directory on your system, then > > the > > kernel source has not been been > > installed. The easiest way to do this is by running > > /stand/sysinstall > > as root, choosing Configure, then > > Distributions, then src, then sys. > > ^^^^^^^^ > [ML] There is, the last time that I looked. It is a suboption > of the src option in Distributions. > Duh! I was being stupid & pressed enter instead of space to select it! Sorry to waste your time on that one, and thanks for all this info below... Reg, --R. > > As I just switched from Redhat 6.0 it would also be nice to know how I > > can > > force an fsck on reboot, i.e. what's the FreeBSD version of shutdown > > -F as > > there is none in the manpage. I'm trying to fix this: > [ML] fsck is not needed under FreeBSD if the filesystem has > been cleanly unmounted. umount sets a clean flag, which fsck honors and > do not do any checks. > > you can force fsck with -f flag to fsck > > > # fsck > > ** /dev/rwd0s1a > > ** Last Mounted on / > > ** Root file system > > ** Phase 1 - Check Blocks and Sizes > > ** Phase 2 - Check Pathnames > > ** Phase 3 - Check Connectivity > > ** Phase 4 - Check Reference Counts > > ** Phase 5 - Check Cyl groups > > 1001 files, 19089 used, 20558 free (446 frags, 2514 blocks, 1.1% > > fragmentation) > > ***** FILE SYSTEM STILL DIRTY ***** > [ML] never, ever, do an fsck on a mounted filesystem. You will > lose data, and you may even lose filesystems. > > If you want to fsck a filesystem while the system is running, > umount the filesystem first, or at the very least, remount it read-only. > > If you want to fsck filesystems on boot, even though they have > been cleanly umounted on shutdown, boot into standalone mode and then do > a fsck -f. then reboot (not strictly neccessary, but a good idea > anyway, because / is mounted read-only--you cannot boot without at least > /, and the kernel mounts it for you). > > In order to boot standalone, press space while the boot > countdown runs, and then enter > -s > after boot > > > > Can you help? (or who can?) > [ML] hope this helped. > > > > Regards, > > Renier. > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.10.9907091418140.21250-100000>