public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] eject and util-linux blocker
Date: Wed, 18 Mar 2015 04:33:18 -0500	[thread overview]
Message-ID: <5509465E.6050105@gmail.com> (raw)
In-Reply-To: <7065434.Q7ja2qHd7n@wstn>

Peter Humphrey wrote:
> On Tuesday 17 March 2015 16:07:29 Dale wrote:
>
>> I don't have / on lvm.  /boot and / are on regular partitions.
>> Everything else, /usr, /var and /home, are on lvm.  Keep in mind, I
>> was trying to avoid that init thingy.
> I remember something of that discussion, but not why you wanted to keep /usr 
> on a separate partition. Why is that? Is it one of those sacred cows that 
> "just growed" like Topsy?    :)
>


Well, /boot doesn't change to much, plus it is fairly small anyway.  The
root partition doesn't change a whole lot either.  /usr tho, it tends to
grow.  If nothing else, it grows as KDE grows but it grows with the
number of kernels I have too.  Of course, other packages grows too. 
/var is good to have on a separate partition since sometimes a log file
can grow to some outrageous sizes.  I've actually had that happen twice
over the years.  Something goes goofy and fills up a log file until it
is seriously huge and fills up /var.  /home is separate for obvious
reasons plus mine is really huge.  1.8TBs right now. 

It started out that it was advised to set up partitions like this.  Then
LVM came along and made it even more reasonable since I can grow the
partitions that need it.  The init thingy because of some packages being
moved to /usr didn't hurt the cause I guess either. 

So, I have it set up the way I do because for my setup, it is the best
way.  I can adjust things without having to have spare drives to move
things around with.

Dale

:-)  :-) 



  parent reply	other threads:[~2015-03-18  9:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 14:08 [gentoo-user] eject and util-linux blocker Dale
2015-03-16 15:34 ` Walter Dnes
2015-03-17  1:43   ` Dale
2015-03-17  8:14     ` Alan McKinnon
2015-03-17 17:01       ` Dale
2015-03-17 17:30         ` Alan McKinnon
2015-03-17 18:10           ` Dale
2015-03-17 18:40             ` Mike Gilbert
2015-03-17 20:16               ` Dale
2015-03-17 20:31                 ` Alan McKinnon
2015-03-17 21:07                   ` Dale
2015-03-18  8:54                     ` Peter Humphrey
2015-03-18  9:08                       ` Neil Bothwick
2015-03-18  9:33                       ` Dale [this message]
2015-03-18 10:21                         ` Peter Humphrey
2015-03-18 16:14                           ` Dale
2015-03-18 17:03                             ` Peter Humphrey
2015-03-18 16:37                     ` Rich Freeman
2015-03-18 17:56                       ` Poncho
2015-03-18 18:12                         ` Dale
2015-03-18 21:55                           ` Rich Freeman
2015-03-18 23:12                           ` Peter Humphrey
2015-03-19  4:14                             ` Dale
2015-03-19  9:34                               ` Peter Humphrey
2015-03-19 15:29                                 ` Dale
2015-03-17 18:50             ` Alan McKinnon
2015-03-17 20:20               ` Dale
2015-03-17 20:46                 ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5509465E.6050105@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox