Date: Tue, 04 Apr 2006 11:08:30 -0700 From: Darren Pilgrim <darren.pilgrim@bitfreak.org> To: Stefan Sperling <stsp@stsp.in-berlin.de> Cc: hackers@freebsd.org, Joe Marcus Clarke <marcus@FreeBSD.org> Subject: Re: RFC: Adding a ``user'' mount option Message-ID: <4432B61E.1030403@bitfreak.org> In-Reply-To: <20060404114547.GA1613@dice.stsp.lan> References: <1144042356.824.16.camel@shumai.marcuscom.com> <4430BA79.2030403@freebsd.org> <44316387.1090609@FreeBSD.org> <44321277.7040904@FreeBSD.org> <1144133238.9725.32.camel@shumai.marcuscom.com> <20060404114547.GA1613@dice.stsp.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Stefan Sperling wrote: > Why do GNOME/KDE rely on /etc/fstab on FreeBSD? > > GNOME/KDE could be patched to create mount points > somewhere in the user's home directory, and issue a 'mount device mount_point' > instead of 'mount mount_point' if the user clicks the device icon. Limiting GNOME/KDE to just those mounts listed in /etc/fstab provides a mechanism of access control. If GNOME/KDE allowed user mounts of any device, then it would become possible for users to mount umounted system volumes. Using fstab also makes it possible for GNOME/KDE to mount items with mount options (sync, mode limits, quotas, etc.) and just rely on the system to get it right, rather than having system-specific, parallel mount code.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4432B61E.1030403>