From owner-freebsd-questions Fri Jul 9 5:45:16 1999 Delivered-To: freebsd-questions@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 49CEA14E1C for ; Fri, 9 Jul 1999 05:44:35 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Fri, 9 Jul 1999 14:47:19 +0200 Message-ID: <55586E7391ACD211B9730000C11002761796EB@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Renier van der Walt' , freebsd-questions@FreeBSD.ORG Subject: RE: FreeBSD 3.2 question stuff Date: Fri, 9 Jul 1999 14:41:11 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----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. > 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