From owner-freebsd-hackers Thu Sep 2 8:36:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id D217E155B6 for ; Thu, 2 Sep 1999 08:36:53 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 15196 invoked by uid 1008); 2 Sep 1999 15:36:44 -0000 From: adrian@freebsd.org Date: Thu, 2 Sep 1999 23:36:44 +0800 To: Boris Popov Cc: adrian@freebsd.org, Doug Rabson , "Andrew J. Korty" , freebsd-hackers@freebsd.org Subject: Re: [mount.c]: Option "user"-patch Message-ID: <19990902233644.C1215@ewok.creative.net.au> References: <19990901003014.A1215@ewok.creative.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Boris Popov on Thu, Sep 02, 1999 at 10:03:06PM +0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 02, 1999, Boris Popov wrote: > > without needing yet another setuid binary/binaries.. > > Well, sysctl with list of pathes for user mounts looks good. > Configuration is simple and can be easliy changed at runtime. It is > always better to avoid setuid'ed binaries, this is more worse that > mount(8) can execute other mount_* binaries. > > However, as pointed by Mike Smith, enabling user mounts raises a > risc of kernel panics from, for example, corrupted floppy disk. This > should lead to more stronger *fs code. Ahh, another discussion entirely, which I'm not going to get into without working code. :-) Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message