Date: Tue, 30 Nov 2004 14:39:52 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Doug Barton <DougB@DougBarton.net> 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: <Pine.NEB.3.96L.1041130143605.34072F-100000@fledge.watson.org> In-Reply-To: <41AC489E.7050108@DougBarton.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1041130143605.34072F-100000>