From owner-freebsd-questions Thu Dec 13 16:46:10 2001 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-31-201-166.mmcable.com [65.31.201.166]) by hub.freebsd.org (Postfix) with SMTP id 9453237B417 for ; Thu, 13 Dec 2001 16:46:02 -0800 (PST) Received: (qmail 82252 invoked by uid 100); 14 Dec 2001 00:45:56 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15385.19396.441544.472199@guru.mired.org> Date: Thu, 13 Dec 2001 18:45:56 -0600 To: Annelise Anderson , Nick Rogness Cc: questions@FreeBSD.ORG Subject: Re: FreeBSD 2.1.5 Installation - Disk Space In-Reply-To: References: <15384.55429.649720.20833@guru.mired.org> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" 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\ X-Delivery-Agent: TMDA v0.42/Python 2.1.1 (freebsd4) From: "Mike Meyer" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Annelise Anderson types: > On Thu, 13 Dec 2001, Mike Meyer wrote: > > Annelise Anderson types: > > > If you have less than 600MB allowed for FreeBSD, just use swap and one > > > file system, /. > > My recommendation for new users is to create at most two file systems > > as well as swap: / and /home. Keep your private stuff on /home. That > > way, when you get a new release, you can do a "clean" install onto / > > without losing your data on /home. If you don't much space - where > > "much" depends on what you're planning on doing - having just one file > > system - / - is better. > > You can delete (and then reinstall) a dos-style partition, that is, > a slice. A hard drive in a pc can have four slices, one of which > can be an extended partition (can hold Windows or linux logical > partitions, but not FreeBSD). You can also newfs and then reinstall a BSD partition. > As for the idea that the only purposes of separate divisions of > a slice into partitions (swap always being its own partition, of course, > within the slice) other than / being administrative, the administrative > differences may be very important. You can back up a file system, e.g., > ad0s1f; that's the "unit" dump uses (I think I've got this right). Exactly. Backup strategy is one of the two most important such issues. The other one is doing system updates. It's nice to be able to newfs the system partitions without having to worry about your user data. > You can mount a file system read-write or read-only. I think more > and more there's an interest in mounting /usr read-only; but /var is > of little use read-only, as this is where (unless you change it) the > mail spool, printer spool, and log files live. Right. Wanting some part of the tree to be read-only is a good reason for creating a file system. Similarly, wanting to NFS export two parts of the tree with different sets of permissions is a good reason for creating another file system. > I guess in summary I'd say that for a system that doesn't have > specfic server purposes (like hosting shell accounts, for example) > I'd still go with a slice with /, swap, /var, and /user unless it > was a small slice; small to me right now is 600MB or less. Two years ago, I'd have agreed with you. Greg Lehey convinced me that such extra "pointless" partitions don't do anything but add yet more things that can run out of space. I have two basic system configurations that I use for almost everything (neglecting swap): Basic Server: / and /var. No user data is on the machine. / mounts read only, and the server data files live on /var so they can be updated. User machines: /, /usr, and /home. / is backed up, because it holds so much critical information. /usr isn't, becuase it can be duplicated from any of a number of places. /home is split off from / so that I can newfs / when upgrading the system. More complicated machines have more complicated setups, but they usually include things that aren't part of the standard tree. Nick Rogness types: > Also, many commands have options to "not traverse mount points" > which becomes almost priceless once you actually have to do > something with your machine. Many of them also have other ways to limit the tree traversal. > Disk space usage is also easier to view (with df) and scale with > multiple filesystems. Um - how does having more partitions make disk usage easier to view? I figure it's twice as hard to deal with four partitions as two. And even easier to deal with just one. For example, if I have a 100MB /usr that's 80% full, a 100MB /var that's 20% full, a 1G /usr that's 75%, it takes a bit of figuring to realize that I have 350MB free - and yet I can't install a 300MB package without rearranging things. > It's better and easier to have the functionality up front then it is > to add it later :-) Whether you use it or not. Yup. It's much better to have 1 1200MB file system so you can install that 300MB package in 350MB of free space without having to create room for it. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message