From owner-freebsd-hackers Wed Nov 1 19:42:50 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA09936 for hackers-outgoing; Wed, 1 Nov 1995 19:42:50 -0800 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA09924 for ; Wed, 1 Nov 1995 19:42:41 -0800 Received: from ast.com (irvine.ast.com [165.164.128.2]) by who.cdrom.com (8.6.12/8.6.11) with SMTP id TAA14249 for ; Wed, 1 Nov 1995 19:42:23 -0800 Received: from fw.ast.com by ast.com with SMTP id AA21422 (5.67b/IDA-1.5 for ); Wed, 1 Nov 1995 19:42:31 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0tAqNU-00008EC; Wed, 1 Nov 95 21:31 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #19) id m0tAqFE-000IxgC; Wed, 1 Nov 95 21:23 WET Message-Id: Date: Wed, 1 Nov 95 21:23 WET To: hackers@freebsd.org From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Wed Nov 1 1995, 21:23:12 CST Subject: Re: More nits Sender: owner-hackers@freebsd.org Precedence: bulk [1]This is a known bug, and it would appear that nobody is particularly [1]keen to change it. I beat my chest about it several times and [1]everybody involved just sort of waffled on it until the subject died [1]down again. Until then, I may just take the automount of the CDROM [1]out of /etc/fstab and have people do it by hand. I hate this, but I [1]lack the time to go fix whatever stupidity it is in our system that [1]prevents the system from coming up whenever a CDROM isn't in the [1]drive. Unless we fix it, /cdrom is coming out of the default fstab [1]in 2.1. Better a system that comes up without a CDROM rather than [1]one that doesn't! I assume it is the same code that refuses to let the system start if one of the hard drives can't be mounted for whatever reason (like it won't spin up!). That has been in BSD since way back. I remember finding it when one of our 11-780 spindles croaked. I doubt the code is able to distinguish between hardware that might not be ready "and that's ok" (ala CDROM), and hardware that might not be ready "and that's bad" (ala hard disk). Perhaps a new "keep going" field should be added to fstab to list mount points you can "live without" and still go multi-user. You might also have to provide an "alternate mount point" field for nested mount points in case the mount point isn't there because "we kept going" when some media wasn't ready. This gets messy. I reported the current action of mounting the CD as a bug in the installation process sometime back as I don't think the install should insert mount entries for the media that was used for the install for several reasons. What if I installed from floppies, should the floppy be remounted on reboot? Or if I used NFS to do the install, should the NFS mount reappear? No, of course not. But it demonstrates an inconsistent treatment of transient media. Transient media (like the installation media) should not be added to fstab, at least as things stand now. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983