Date: Mon, 5 Jan 1998 01:29:05 -0500 From: "Alfred Perlstein" <perlsta@sunyit.edu> To: "Warner Losh" <imp@village.org>, "Mike Smith" <mike@smith.net.au> Cc: <hackers@FreeBSD.ORG> Subject: Re: Musing on boot Message-ID: <199801050233.CAA00380@fang.cs.sunyit.edu>
next in thread | raw e-mail | index | archive | help
MUHAHAHAH evilness: ( mount /dev/device /mountpoint || ( fsck /dev/device && mount /dev/device /mountpoint) ) & done in the background: if the mount fails, fsck the device then mount... put in a nested shell script we could grep a file with the devs and mount points in it, xargs to the script then do a foreach or something... -Alfred ---------- > From: Mike Smith <mike@smith.net.au> > To: Warner Losh <imp@village.org> > Cc: hackers@FreeBSD.ORG > Subject: Re: Musing on boot > Date: Monday, January 05, 1998 12:30 AM > > > > > > > The idea is to have a list of file systems that *MUST* be present for > > the system to come up. These files systems are fsck'd and mounted > > synchronously. All the rest of the file systems have a fsck kicked > > off in the background, and a mount done when that fsck happens to > > finish. > > List the "optional" filesystems in /etc/fstab with '0' fsck pass values > and 'noauto' mount options, then put > > fsck <special> && mount <filesystem> & > > for each filesystem in /etc/rc.local > > > I thought I'd bounce it off hackers. It seems like such a simple idea > > that something must be wrong with it. > > It's certainly not new. 8) > > > P.S. Code to follow if there appears to be interest... > > I would be inclined to suggest that an option to mount_ffs(8) that > automatically fsck'ed a filesystem before mounting it would be a good > way to go. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801050233.CAA00380>