Date: Fri, 21 Jul 2006 13:22:36 -0500 From: Robert C Wittig <wittig.robert@sbcglobal.net> To: DW <spock@dwinner.net> Cc: freebsd-questions@freebsd.org Subject: Re: mount privileges...what the heck? Message-ID: <44C11B6C.3070406@sbcglobal.net> In-Reply-To: <44C108FE.200@dwinner.net> References: <44C108FE.200@dwinner.net>
index | next in thread | previous in thread | raw e-mail
DW wrote: > So any ideas on why I need to do a chown -R dude:dude after the first > mount?????? Am I missing something, going insane, or is something buggy > here???? You created the directory as root: # mkdir /usr/home/dude/drive2 ...so it belongs to root. I can only assume that... 'Ownership on mount point: dude:dude /usr/home/dude/drive2' ...does not mean that you actually did a # chown dude:dude /usr/home/dude/drive2 ...which is necessary, after root creates a directory. Why didn't you just log in as dude to create the directory that was going to serve as the mount point, as in: % mkdir /usr/home/dude/drive2 ...or $ mkdir /usr/home/dude/drive2 Just yesterday I did exactly this on my PC-BSD (FreeBSD 6.1, basically) First I created, logged in an my 'dude' identity (as opposed to my root identity), and created 4 directories in /home/dude, for mounting four data partitions that exist on a data hard drive that is accessed by PC-BSD, Red Hat Enterprise 3, or Windows XP SP2 (depending on which front-loading, swappable hard drive cage with operating system, I have plugged into the machine. the partitions are Samba shares, when *nix is plugged into the machine, so they are always accessible to other Windows boxes on the LAN. Then, I wrote a shell script called 'mountall', which is the BSD equivalent to the script I have in Red Hat, for mounting the partitions. Then I ran the script, and voila... my Windows 2000 graphics workstation could read and write to the Samba shares as per usual.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44C11B6C.3070406>