Date: Tue, 30 Nov 2004 22:30:58 +0200 From: Ruslan Ermilov <ru@freebsd.org> To: Robert Watson <rwatson@freebsd.org> Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sbin/mount mntopts.h mount.8 mount.c src/sbin/mount_std mount_std.8 Message-ID: <20041130203058.GA20833@ip.net.ua> In-Reply-To: <Pine.NEB.3.96L.1041130143605.34072F-100000@fledge.watson.org> References: <41AC489E.7050108@DougBarton.net> <Pine.NEB.3.96L.1041130143605.34072F-100000@fledge.watson.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, Nov 30, 2004 at 02:39:52PM +0000, Robert Watson wrote: > > On Tue, 30 Nov 2004, Doug Barton wrote: > > > >>FYI, this commit seems to have broken my line in fstab which has worked for > > >>a long time: > > >> > > >>md /tmp mfs rw,-s16m,noatime,nosuid,nodev 2 0 > > >> > > >>Is it useful for the nodev option to cause a hard failure here? Note, I'm > > >>not arguing against either change, just pointing out a side effect. > > > > > > There's no longer a "nodev" option, please ask Poul-Henning for details. ;) > > > > Yes, I understand the mechanics, I'm just curious if you think that this > > should result in a fatal error. It sounds like you think that the answer > > to that is yes, which if that is the correct answer I'm fine with that. > > I think a reasonable alternative would be for use of the nodev option to > silently no-op in all cases but (perhaps) devfs, since the behavior > described for nodev is in fact now simply the way the system behaves. > Maybe the middle ground is to print a warning? > I reverted a part of mntopts.h commit -- now "nodev" in /etc/fstab is recognized again. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBrNiCqRfpzJluFF4RAqOUAJ4wNCdNbmTGrPG/BFxGo7MMCsS5MwCdGP5r f4mq8XUsIEhKZK1Bag9EVdM= =ulo3 -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041130203058.GA20833>