From owner-freebsd-questions Sat Sep 9 2:35:43 2000 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (zoom0-020.telepath.com [216.14.0.20]) by hub.freebsd.org (Postfix) with SMTP id A037C37B443 for ; Sat, 9 Sep 2000 02:35:40 -0700 (PDT) Received: (qmail 98103 invoked by uid 100); 9 Sep 2000 09:34:51 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14778.1083.408090.23168@guru.mired.org> Date: Sat, 9 Sep 2000 04:34:51 -0500 (CDT) To: j mckitrick Cc: questions@freebsd.org Subject: Re: chown mountpoints In-Reply-To: <88323124@toto.iv> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG j mckitrick writes: > Is it really necessary to chown the mountpoints for every boot to allow > non-users to mount/umount floppies and zips? It seems silly. How does a non-user go about issuing a mount command? :-). Assuming you meant non-root-users, you don't want to let them mount on things they don't own - the security implications are a nightmare. However, the ownership shouldn't be changing across boots. Can you provide more details?