From owner-freebsd-stable Sat Nov 25 6: 6:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hse-toronto-ppp119263.sympatico.ca (HSE-Toronto-ppp260651.sympatico.ca [64.230.28.98]) by hub.freebsd.org (Postfix) with SMTP id E730637B4CF for ; Sat, 25 Nov 2000 06:06:21 -0800 (PST) Received: (qmail 95631 invoked by uid 0); 25 Nov 2000 14:11:26 -0000 Received: from unknown (HELO jester) (10.0.0.101) by hse-toronto-ppp260651.sympatico.ca with SMTP; 25 Nov 2000 14:11:26 -0000 Message-ID: <007e01c05766$8b5b48b0$6500000a@jester> From: "Rod Taylor" To: Subject: Fstab issues... Date: Sat, 25 Nov 2000 21:05:50 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_007B_01C05723.7D164FE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_007B_01C05723.7D164FE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable While playing around I managed to fully erase /etc/fstab (on purpose = actually :). Anyhow, on a reboot something rather mistifying happened. It was = obvious that it wouldn't be able to find any devices to mount, and = mounted the / partition read only. Now, the strange thing is that I was = unable to mount / for write (mount /dev/ad0s1a /) without first creating = an fstab file with a fixit disk. I certainly don't believe this is expected as in 2.2.x I seem to = remember having the ability to create fstab if it was killed. As to why I deleted it, I was going to CVS /etc on some production boxes = and wanted to know what the worst case scenario would be if there was a = crash before the initial checkout. The results were using a fixit = floppy. Can this be rectified to not make mount depend on /etc/fstab existing? ------=_NextPart_000_007B_01C05723.7D164FE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

While playing around I managed to fully = erase=20 /etc/fstab (on purpose actually :).

Anyhow, on a reboot something rather = mistifying=20 happened. It was obvious that it wouldn't be able to find any = devices to=20 mount, and mounted the / partition read only. Now, the strange = thing is=20 that I was unable to mount / for write (mount /dev/ad0s1a /) without = first=20 creating an fstab file with a fixit disk.

I certainly don't believe this is = expected as in=20 2.2.x I seem to remember having the ability to create fstab if it was=20 killed.

As to why I deleted it, I was going to = CVS /etc on=20 some production boxes and wanted to know what the worst case scenario = would be=20 if there was a crash before the initial checkout. The results were = using a=20 fixit floppy.

Can this be rectified to not make mount = depend on=20 /etc/fstab existing?

------=_NextPart_000_007B_01C05723.7D164FE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message