Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!uwm.edu!lll-winken!lll-lcc!pyramid!cbmvax!grr From: grr@cbmvax.UUCP (George Robbins) Newsgroups: comp.unix.ultrix Subject: Re: "mount -a -t nfs" problems found and solved Message-ID: <8003@cbmvax.UUCP> Date: 26 Sep 89 08:52:37 GMT References: <89Sep26.001054edt.30815@snow.white.toronto.edu> Reply-To: grr@cbmvax.UUCP (George Robbins) Organization: Commodore Technology, West Chester, PA Lines: 21 In article <89Sep26.001054edt.30815@snow.white.toronto.edu> cks@white.toronto.edu (Chris Siebenmann) writes: > > Well, I found the cause of the problem we were having with "mount -a > -t nfs" getting a SIGSEGV. It turns out that the DS3100 mount is > somewhat stricter (in a sense) about malformed /etc/fstab lines > (although I wish it gave an error message!). There's actually a warning about this feature in the release notes. It sure would be nice if all the ::: like command files, including /etc/passwd understood # comments, but that's another story. On nice thing that crept in somewhere around 3.0 is you can put something like xx in the rw/ro/sw field and have most of the programs cooperate - mount -a doesn't mess with it, but an explict mount by file system name works as does df. Too bad it's not documented or 100% consistant across programs that can access /etc/fstab... -- George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr but no way officially representing arpa: cbmvax!grr@uunet.uu.net Commodore, Engineering Department fone: 215-431-9255 (only by moonlite)