Re: Newbie: Correct directory for file server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Wednesday 12 November 2003 04:10, Tom Munro Glass wrote: Thanks Chris. Please take a look at my reply to Scott because the two of you seem to be suggesting contradicting ideas, and I'm keen to learn why! Have done. It's just my preference because I find it easier: the FreeBSD installer as you've noticed, by default, puts the home directories under / usr/home, and creates /home as a symlink. Therefore I found it easier just to tell the installer that /usr/home would be its own partition. Ultimately it's just what you find easiest, there's no right way, though some things are probably frowned upon. Installation is only something you need to do once, after that you cvsup :) The file system on my laptop looks something like this: Filesystem Size Used Avail Capacity Mounted on /dev/ad0s3a 126M90M26M77%/ /dev/ad0s3h 5.8G 2.2G 3.1G41%/usr /dev/ad0s3d 8.8G 7.6G 509M94%/usr/home /dev/ad0s3g 5.8G 3.0G 2.3G56%/usr/home/devel /dev/ad0s3e 197M15M 166M 8%/tmp /dev/ad0s3f 197M88M93M49%/var procfs 4.0K 4.0K 0B 100%/proc linprocfs4.0K 4.0K 0B 100%/usr/compat/linux/proc sauron:/space/test75G64G 3.6G95%/mnt/test /usr/home/devel is a separate partition from /usr/home because I use /usr/ home/devel to compile KDE CVS reguarly, and compiling thousands of source files, even on efficient file systems, is a good way to cause fragmentation, therefore I like to keep it separate from the rest of the system. My server looks like this: Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1a 252M 155M77M67%/ /dev/ad0s1f 252M 9.0M 223M 4%/tmp /dev/ad0s1g 7.3G 4.1G 2.6G61%/usr /dev/ad0s1e 756M 220M 476M32%/var procfs 4.0K 4.0K 0B 100%/proc /dev/ad4s1e 75G64G 3.6G95%/space /dev/vinum/vinum1 144G63G69G48%/vinum1 My home directories here are under /space (though will be under /vinum1 soon when I finish migrating data from /space, an 80GB disk to /vinum1, 2 x160GB in RAID 1 with vinum). /etc/exports on the server looks like this: /space/test /space/persbackup /space/photos -maproot=0 -network 192.168.1.0 - -mask 255.255.255.0 Hope this helps. - -- Cheers, Chris Howells -- [EMAIL PROTECTED], [EMAIL PROTECTED] Web: http://chrishowells.co.uk, PGP ID: 0x33795A2C KDE/Qt/C++/PHP Developer: http://www.kde.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/sjY3F8Iu1zN5WiwRAkoNAJ4gOm9PLfdg0ntSS4f4nAwWlRtrQgCfZxF5 d+1OYiJzqYEVSgCT++bnRyw= =KNgm -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie: Correct directory for file server
Thanks Chris and Scott for your input on this subject - I've found it most helpful. The freedom to tweak the system to your own way of working is great, and I now feel I am better informed on how to do this without doing anything radical that I will regret in years to come. Thanks again to you both. Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie: Correct directory for file server
Tom Munro Glass wrote: On Tue, 11 Nov 2003 15:31, Alex de Kruijff wrote: On Tue, Nov 11, 2003 at 01:53:20PM +1300, Tom Munro Glass wrote: On an intranet file server, the users' private files are obviously stored in /usr/home/username but where is the correct place to store files that are common to many users? Would this be something like /usr/home/public or /usr/local/public or even /var/public? Thanks, There is no default. You can choice your own directory. Placing this in the /usr slice or on a second disk seems reasable. /var wouldn't be advisable. I guessed there isn't a default, but I thought there might be a convention for this and I want to follow conventions where ever possible. Tom Munro Glass Depends on what philosophy you subscribe to- if it's on a local system only, then create a group for members that will need access to it, and create a directory in the /home tree, like /home/'project_foo If it's going to be NFS mounted by other systems, then create an /export directory and put it similarly in there, which has the convenience as you change your filesystems (and you will...) and perhaps share more directories, or add more disk, you can keep them 'centrally' located (or mounted) under a single top level directory.. Unless your /var filesystem is _huge_ (or on the same filesystem as /, ick!), I wouldn't put anything to be shared in the /var tree...(as already mentioned). Likewise, /usr is meant to be capable of being mounted read-only, and contains (generally) static binaries and libraries required for full multi-user (read this as networked) mode operation of the system, so I'd abstain from using /usr either. Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie: Correct directory for file server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Tuesday 11 November 2003 02:52, Tom Munro Glass wrote: I guessed there isn't a default, but I thought there might be a convention for this and I want to follow conventions where ever possible. I prefer to put things onto /usr/home (e.g. /usr/home/public) since my /usr/ home is a separate partition and if I need to reinstall for some reason it won't be lost. I'd say /usr and /var were bad places. - -- Cheers, Chris Howells -- [EMAIL PROTECTED], [EMAIL PROTECTED] Web: http://chrishowells.co.uk, PGP ID: 0x33795A2C KDE/Qt/C++/PHP Developer: http://www.kde.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/sOyEF8Iu1zN5WiwRAn94AKCYAop+I8WCvG0rJKnE9QafeeHVyQCeO+i5 mgwFgVZy5Oivzyp77nT4R6Y= =1/0q -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie: Correct directory for file server
Depends on what philosophy you subscribe to- if it's on a local system only, then create a group for members that will need access to it, and create a directory in the /home tree, like /home/'project_foo If it's going to be NFS mounted by other systems, then create an /export directory and put it similarly in there, which has the convenience as you change your filesystems (and you will...) and perhaps share more directories, or add more disk, you can keep them 'centrally' located (or mounted) under a single top level directory.. Unless your /var filesystem is _huge_ (or on the same filesystem as /, ick!), I wouldn't put anything to be shared in the /var tree...(as already mentioned). Likewise, /usr is meant to be capable of being mounted read-only, and contains (generally) static binaries and libraries required for full multi-user (read this as networked) mode operation of the system, so I'd abstain from using /usr either. Scott Thanks for this Scott. The files are going to be NFS mounted by Linux workstations and SMB mmounted by Windows workstations, so I guess that /export is the right place. I will make this a separate filesystem. I currently have separate filesystems for /, /tmp, /usr and /var. Considering your comment about /usr being mounted read-only, why is /home a link to /usr/home when hme obviously contains variable data? If I use a new filesystem for /home, should I mount this at /home and make /usr/home a link to /home, or do I just mount it at /usr/home? Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie: Correct directory for file server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Tuesday 11 November 2003 19:38, Tom Munro Glass wrote: filesystem for /home, should I mount this at /home and make /usr/home a link to /home, or do I just mount it at /usr/home? The latter is probably preferable. - -- Cheers, Chris Howells -- [EMAIL PROTECTED], [EMAIL PROTECTED] Web: http://chrishowells.co.uk, PGP ID: 0x33795A2C KDE/Qt/C++/PHP Developer: http://www.kde.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/sTzDF8Iu1zN5WiwRAtFBAKCVRGw/wrtqlfE7Qt56LWr2SXGrYwCfWhq9 t1KEvWTUgOOLmNN0ZAFhz7I= =PB2A -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie: Correct directory for file server
Tom Munro Glass wrote: Depends on what philosophy you subscribe to- if it's on a local system only, then create a group for members that will need access to it, and create a directory in the /home tree, like /home/'project_foo If it's going to be NFS mounted by other systems, then create an /export directory and put it similarly in there, which has the convenience as you change your filesystems (and you will...) and perhaps share more directories, or add more disk, you can keep them 'centrally' located (or mounted) under a single top level directory.. Unless your /var filesystem is _huge_ (or on the same filesystem as /, ick!), I wouldn't put anything to be shared in the /var tree...(as already mentioned). Likewise, /usr is meant to be capable of being mounted read-only, and contains (generally) static binaries and libraries required for full multi-user (read this as networked) mode operation of the system, so I'd abstain from using /usr either. Scott Thanks for this Scott. The files are going to be NFS mounted by Linux workstations and SMB mmounted by Windows workstations, so I guess that /export is the right place. I will make this a separate filesystem. I currently have separate filesystems for /, /tmp, /usr and /var. Considering your comment about /usr being mounted read-only, why is /home a link to /usr/home when hme obviously contains variable data? If I use a new filesystem for /home, should I mount this at /home and make /usr/home a link to /home, or do I just mount it at /usr/home? Tom Hi Tom- /usr doesn't _have_ to be mounted read-only, but it's not uncommon to do it on systems connected to the net/susceptible to hacking/just for security. Default Sun for home is /export home, primarily b/c Solaris thinks it's always the NFS server ;-) Most Linux distros use /home, and I'll admit I'm not positive what freeBSD uses as a default, but I expect it to be /home and again, NOT under the /usr tree- home directories contain dynamic, changing data. The /usr filesystem remains static aside from the occasional app that 'must' be installed into /usr/local, or adding vendor packages (think base packages or ports installed for freeBSD), which once it's set up for a production system, may actually stay static for years in some cases (with the possible exception of security fixes depending on the environment). Again, mounting the home dir as /usr/home would preclude you from ever even considering mounting /usr as read-only (or 'immutable' is I _think_ the other freeBSD option?) So, not sure why your system is set up the way it is, but fairly likely it was done that way because of mis-judging disk space requirements, or the way the drive(s) were partitioned... you can always create a new home dir and copy it over via: rm -f /home (removes symlink) mkdir /home cd /usr/home tar cvf - . | (cd /home tar xvf - ) Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie: Correct directory for file server
Hi Tom- /usr doesn't _have_ to be mounted read-only, but it's not uncommon to do it on systems connected to the net/susceptible to hacking/just for security. Default Sun for home is /export home, primarily b/c Solaris thinks it's always the NFS server ;-) Most Linux distros use /home, and I'll admit I'm not positive what freeBSD uses as a default, but I expect it to be /home and again, NOT under the /usr tree- home directories contain dynamic, changing data. The /usr filesystem remains static aside from the occasional app that 'must' be installed into /usr/local, or adding vendor packages (think base packages or ports installed for freeBSD), which once it's set up for a production system, may actually stay static for years in some cases (with the possible exception of security fixes depending on the environment). Again, mounting the home dir as /usr/home would preclude you from ever even considering mounting /usr as read-only (or 'immutable' is I _think_ the other freeBSD option?) So, not sure why your system is set up the way it is, but fairly likely it was done that way because of mis-judging disk space requirements, or the way the drive(s) were partitioned... you can always create a new home dir and copy it over via: rm -f /home (removes symlink) mkdir /home cd /usr/home tar cvf - . | (cd /home tar xvf - ) Scott Thanks again Scott. I understand what you're saying about /usr being for mainly static data and this stacks up with what I've read about Linux and FreeBSD. So I was very surprised when I installed 4.9-RELEASE on a brand new machine (completely blank disks) and it made /home as a symlink to /usr/home! But this seems to be the default for FreeBSD. I'm half way through creating new filesystems for 'home' and 'export' and copying the data across (thanks for the tar tip) and I just have to decide where to mount them. Chris Howells suggests mounting the 'home' filesystem at /usr/home and I think he is suggesting that 'export' would mount at /usr/home/export. This contradicts what you have said above so I'm confused! Chris/Scott - I'd be interested to hear your thoughts on this. Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie: Correct directory for file server
On Wed, 12 Nov 2003 08:47, Chris Howells wrote: Hi, On Tuesday 11 November 2003 19:38, Tom Munro Glass wrote: filesystem for /home, should I mount this at /home and make /usr/home a link to /home, or do I just mount it at /usr/home? The latter is probably preferable. Thanks Chris. Please take a look at my reply to Scott because the two of you seem to be suggesting contradicting ideas, and I'm keen to learn why! Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie: Correct directory for file server
Tom Munro Glass wrote: Hi Tom- /usr doesn't _have_ to be mounted read-only, but it's not uncommon to do it on systems connected to the net/susceptible to hacking/just for security. Default Sun for home is /export home, primarily b/c Solaris thinks it's always the NFS server ;-) Most Linux distros use /home, and I'll admit I'm not positive what freeBSD uses as a default, but I expect it to be /home and again, NOT under the /usr tree- home directories contain dynamic, changing data. The /usr filesystem remains static aside from the occasional app that 'must' be installed into /usr/local, or adding vendor packages (think base packages or ports installed for freeBSD), which once it's set up for a production system, may actually stay static for years in some cases (with the possible exception of security fixes depending on the environment). Again, mounting the home dir as /usr/home would preclude you from ever even considering mounting /usr as read-only (or 'immutable' is I _think_ the other freeBSD option?) So, not sure why your system is set up the way it is, but fairly likely it was done that way because of mis-judging disk space requirements, or the way the drive(s) were partitioned... you can always create a new home dir and copy it over via: rm -f /home (removes symlink) mkdir /home cd /usr/home tar cvf - . | (cd /home tar xvf - ) Scott Thanks again Scott. I understand what you're saying about /usr being for mainly static data and this stacks up with what I've read about Linux and FreeBSD. So I was very surprised when I installed 4.9-RELEASE on a brand new machine (completely blank disks) and it made /home as a symlink to /usr/home! But this seems to be the default for FreeBSD. I'm half way through creating new filesystems for 'home' and 'export' and copying the data across (thanks for the tar tip) and I just have to decide where to mount them. Chris Howells suggests mounting the 'home' filesystem at /usr/home and I think he is suggesting that 'export' would mount at /usr/home/export. This contradicts what you have said above so I'm confused! Chris/Scott - I'd be interested to hear your thoughts on this. Tom Heh- wasn't the joys of C vs C++ enough? ;-) Really not much else to say on it- different people have different reasons, just as some people use only a single / filesystem. I don't, except in the case of what used to be a triple OS booting laptop...some of my preferences I think are pretty 'standard,' others by running out of disk space or filling up the 'wrong' filesystem, or simply trying to keep large or growing filesystems 'sane.'...but sane to me, may not be to someone else ;-) Oh, I don't think Chris said anything about mounting export _under_ home- export is more of a 'sanity' thing when you have a ton of growing filesystems- on some systems, you really don't know going into it just how much storage you may wind up attaching, OR what it might be used for, etc...so imposing a _consistent_ layout from the start (eg, anything that will be exported via NFS goes under /export/* , which generally includes home directories which become /export/home (and you can always symlink back to /home if you'd like, unsure if freeBSDs automounter does things the same as Solaris. Likewise, if you were also going to run Samba to export shares to Windoze systems, in an ideal world you'd find a combination where both Unix and Windows files might co-exist under a user's home directory, if they/you are manipulating/editing in both platforms (OpenOffice or apps under WINE, etc), music shared (which uhh, I never do of course.. ;-) under /export/music etc etcand /usr/* IMHO simply should not have 'data' in it, or anything that has the capability to be changed often.. One of the nice things about freeBSD is that most *nixes have for years tried to impose 'the right way' to do things with respect to directory layout...freeBSD seems to be the first I've seen that does it consistently, although differently in some cases (/usr/local/etc)...anyways, the point is- don't ruin that, for your OWN sanity's sake. If you don't like my personal preferences, come up with something that makess sense to YOU, and that won't drive you insane 5 years down the road when you STILL might have some of the same disks, or at least data copied over to new disks... Scott Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Newbie: Correct directory for file server
On an intranet file server, the users' private files are obviously stored in /usr/home/username but where is the correct place to store files that are common to many users? Would this be something like /usr/home/public or /usr/local/public or even /var/public? Thanks, Tom Munro Glass ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie: Correct directory for file server
On Tue, Nov 11, 2003 at 01:53:20PM +1300, Tom Munro Glass wrote: On an intranet file server, the users' private files are obviously stored in /usr/home/username but where is the correct place to store files that are common to many users? Would this be something like /usr/home/public or /usr/local/public or even /var/public? Thanks, There is no default. You can choice your own directory. Placing this in the /usr slice or on a second disk seems reasable. /var wouldn't be advisable. -- Alex Articles based on solutions that I use: http://www.kruijff.org/alex/index.php?dir=docs/FreeBSD/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie: Correct directory for file server
On Tue, 11 Nov 2003 15:31, Alex de Kruijff wrote: On Tue, Nov 11, 2003 at 01:53:20PM +1300, Tom Munro Glass wrote: On an intranet file server, the users' private files are obviously stored in /usr/home/username but where is the correct place to store files that are common to many users? Would this be something like /usr/home/public or /usr/local/public or even /var/public? Thanks, There is no default. You can choice your own directory. Placing this in the /usr slice or on a second disk seems reasable. /var wouldn't be advisable. I guessed there isn't a default, but I thought there might be a convention for this and I want to follow conventions where ever possible. Tom Munro Glass ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
