What is recommended for a public, 'free-for-all', anyone can read or write directory on FreeBSD? What are the reasons for preferring one place over another? Would these work? /usr/local/share/sambapublic/ /usr/share/sambapublic/ /home/sambapublic/ Start Here to Find It Fast!? -> http://www.US-Webmasters.com/best-start-page/ $8.77 Domain Names -> http://domains.us-webmasters.com/
On Thu, 23 Sep 2004, W. D. wrote:> What is recommended for a public, 'free-for-all', > anyone can read or write directory on FreeBSD? > > What are the reasons for preferring one place > over another? > > Would these work? > > /usr/local/share/sambapublic/ > /usr/share/sambapublic/ > /home/sambapublic/All these would work, but follow similar rules as for the /tmp directory. If its publicy writable, have it on a partition that wont impact your system if it gets filled. (ie idealy its own partition but anything but / if you dont have a spare partition) Vince> > > > Start Here to Find It Fast!? -> http://www.US-Webmasters.com/best-start-page/ > $8.77 Domain Names -> http://domains.us-webmasters.com/ > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >
> What is recommended for a public, 'free-for-all', > anyone can read or write directory on FreeBSD? > > What are the reasons for preferring one place > over another? > > Would these work? > > /usr/local/share/sambapublic/ > /usr/share/sambapublic/ > /home/sambapublic/I recommend a separate partition, so that when it eventually gets filled up -- and these things always do -- your system will not be adversly affected. You can mount the partition wherever you want. In your three examples, "sambapublic" could be a file system mounted on /usr/local/share, /usr/share, or /home. What we are talking about here is the OS view. To the Windows user what counts is the share name. On server fattoad, any one of these directories could be shared out as "pub" (or whatever name you like). The windows users will not see the OS pathname. Gary Dunn Honolulu
> At 13:20 9/23/2004, knowtree@aloha.com wrote: > >> What is recommended for a public, 'free-for-all', > >> anyone can read or write directory on FreeBSD? > >> > >> What are the reasons for preferring one place > >> over another? > >> > >> Would these work? > >> > >> /usr/local/share/sambapublic/ > >> /usr/share/sambapublic/ > >> /home/sambapublic/ > > > >I recommend a separate partition, so that when it eventually gets filled up > >-- and these things always do -- your system will not be adversly affected. > >You can mount the partition wherever you want. In your three examples, > >"sambapublic" could be a file system mounted on /usr/local/share, > >/usr/share, or /home. > > Thanks for the info. I just wanted to stick with the FreeBSD > standard if there was one. > > How can I add a new partition? Can that be done after the OS > and data are on the drive? What program? What would it be > called?Not practical unless you install an additional hard drive. Sticking with the drive you have, you would need to backup your data and reinstall FreeBSD from scratch. The extra partition would be created using the Disklable Editor, a sibling to / and /usr and /var and /home. That may be more work than you want to do right now. In that cae, if you want to try it out, use either the home partician or the var partician. We could probably spark a lively debate here as to which is better :-) Bottom line: go ahead and set up samba, to learn how it works. If you want to use it in production (serious, bullit-proof) create that special partition. Gary Dunn Honolulu