Date: Sat, 10 Oct 2009 12:28:08 -0700 (PDT) From: Richard Mahlerwein <mahlerrd@yahoo.com> To: FreeBSD-Questions <freebsd-questions@freebsd.org> Cc: Polytropon <freebsd@edvax.de> Subject: Re: / almost out of space just after installation Message-ID: <877212.65138.qm@web51003.mail.re2.yahoo.com> In-Reply-To: <20091010200418.8e880250.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--- On Sat, 10/10/09, Polytropon <freebsd@edvax.de> wrote:=0A=0A> From: Pol= ytropon <freebsd@edvax.de>=0A> Subject: Re: / almost out of space just afte= r installation=0A> To: "Chad Perrin" <perrin@apotheon.com>=0A> Cc: freebsd-= questions@freebsd.org=0A> Date: Saturday, October 10, 2009, 2:04 PM=0A> On = Sat, 10 Oct 2009 11:36:08 -0600,=0A> Chad Perrin <perrin@apotheon.com>=0A> = wrote:=0A> > Someone mentioned giving the `home` directory its own=0A> part= ition.=A0 I think=0A> > a separate partition for /usr/home, mounted within= =0A> /usr, is a great idea.=0A> > It would help substantially with system r= ebuilds,=0A> backups, and using=0A> > separate drives for `home`, because t= hat's where the=0A> majority of the=0A> > stuff you want to keep between in= stalls will=0A> reside.=A0 Basically=0A> > everything else within /usr (wit= h the possible=0A> exception of=0A> > /usr/local/etc) is just what happens = when you install=0A> and configure your=0A> > system in the first place.=0A= > =0A> If you can estimate disk requirements good enough, or=0A> simply=0A>= have huge hard disks that can compensate any requirements,=0A> there's=0A>= no problem giving /home a separate partition. There's no=0A> need=0A> to p= ut the mountpoint into /usr, because /home could=0A> "physically"=0A> exist= ; in the "home in usr" setting, /home is just a=0A> symlink to=0A> /usr/hom= e.=0A> =0A> Personally, I often put /home on a separate partition,=0A> simp= ly=0A> because of comfortability. If I can't say enough about how=0A> /usr= =0A> and /home will grow, I go with the default approach. I=0A> sometimes= =0A> even use the "one big /" setting.=0A> =0A> One advantage of /home as a= separate partition is that you=0A> can=0A> easily use dump to create a bac= kup - you simply backup the=0A> whole=0A> partition. You could have a direc= tory, let's say=0A> /home/settings,=0A> where you keep duplicates of /etc, = /usr/local/etc and other=0A> files=0A> that contain settings you consider w= orth being backed up.=0A> =0A> =0A> -- =0A> Polytropon=0A> Magdeburg, Germa= ny=0A> Happy FreeBSD user since 4.0=0A> Andra moi ennepe, Mousa, ...=0A=0AI= agree completely. I also go a step farther and put most other things that= I consider user data in there. Like Subversion repositories and non-user-= specific Samba shares (E.g. "public" type shares). I do not generally want= /tmp on memory, though. While it can be fun and quite a festive thing, I = have far too many systems too limited in RAM to want to do this (my current= "production" system at home is 512 MB of RAM, my "play" box is 256 MB). T= he only time I can really think I'd want /tmp to be in RAM is if I already = had too much RAM for the needs of the box - otherwise, just give me the RAM= ...=0A=0AWhile I'm reasonably happy rolling my own FS sizes, I would be eve= n happier if I didn't have to. As long as we're doing the wish list, I'd g= uess for this (all numbers significantly flexible):=0A=0ADrive < 16 GB =3D = keep current layout?=0A=0ADrive > 16 and < 40 GB =3D =0A/ =3D 1 GB=0Aswap = =3D 1.5x RAM =0A/tmp =3D 2 GB=0A/var =3D 2 GB=0A/usr =3D remaining space=0A= =0ADrive > 40 GB =3D =0A/ =3D 1 GB=0Aswap =3D 1.5x RAM =0A/tmp =3D 2 GB=0A/= var =3D 2 GB=0A/usr =3D 1/2 of remaining space, min 20 GB, max 35 GB=0A/hom= e =3D everything else.=0A=0AAnd, as long as this is a wish list, how about.= ..=0A=0A1) When I create, I would love to not to *always* have to backspace= over like 17 digits every time to type something short like "16G". Can we= just make it operate in MB or something instead of blocks? Does anyone ne= ed smaller than 1 MB divisions now? =0A1.1) If it would take a decimal poi= nt, I'd be fine with GB, for that matter. (For compatibility, allow either= , or . as decimal.)=0A1.2) Or if there was just a quick key to delete all = 14 digits of "number of blocks left" at once.=0A=0A2) When I 'auto' size, I= end up deleting most except / and swap partition and remaking (it is just = habit I 'a'uto before I think, and no harm in it) except the last few times= I've done it, as I deleted all the other partitions, / kept expanding from= the default (512 MB?) until it was 1.5 GB. So I had to deleted them ALL a= nd start over. Bug or Feature?=0A=0A3) Ability to resize any partition dir= ectly, if there's empty space left. So if I have 30 GB of my 400 GB drive = already decided upon, and I decide that I want /var to be 5 GB instead of 2= GB, I would love to be able to just highlight it and press some key to "Re= size" and it would just move the rest of them up to fit.=0A=0AOf course, Ju= st because this is a bike shed doesn't mean I will get upset if any or even= all of this is too much to implement and doesn't make it in any revision o= f sysinstall. It's just a wish list. In fact, I may pull open the code my= self... though I've heard it's pretty nasty...=0A=0A-Rich=0A=0A=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?877212.65138.qm>