[nycbug-talk] Cool read about history of /bin /usr/bin/

[Edward Capriolo]

/var/lib is ok I think. Each daemon that needs to store data defaults
to /var/lib/${daemon}. Also your logs will go to /var/log, so in
practice /var is all disk besides /boot and / (and home if you are
supporting it). In the end anything that really cares about disk
performance will likely use /mnt/something.

I have seen disks over partitioned 100GB with 10 10GB slices so no
room for a 30GB database. I have seen disk under partitioned 300GB /
root that takes 30 minutes to fsck. Heir layouts make the best
arguments.

Edward


On Mon, Mar 26, 2012 at 3:12 PM, Charles Sprickman <spork at bway.net> wrote:
>
>
> On Mar 26, 2012, at 2:59 PM, Henry M wrote:
>
> I always like reading where certain Unix "formalities" came from.
>
> "Understanding the bin, sbin, usr/bin , usr/sbin split"
>
> http://lists.busybox.net/pipermail/busybox/2010-December/074114.html
>
>
> The history is interesting, but his "get off my lawn" rant about carrying
> this historical cruft is a prime example of why I generally don't enjoy the
> way things are done in the linux world.  There's a good rebuttal to his
> point a few messages further on.  In short, putting stuff essential for
> booting on the root fs still has practical uses.
>
> On a tangent, can anyone explain "/var/lib" in the linux world?  That one
> has always perplexed me.
>
> Charles
>
>
>
> _______________________________________________
> talk mailing list
> talk at lists.nycbug.org
> http://lists.nycbug.org/mailman/listinfo/talk
>
>
>
> _______________________________________________
> talk mailing list
> talk at lists.nycbug.org
> http://lists.nycbug.org/mailman/listinfo/talk
>