Re: [gentoo-user] How can I control size of /run (tmpfs)?

[Dale <rdalek1967@gmail.com>]

Neil Bothwick wrote:
> On Sat, 26 May 2012 17:17:54 -0500, Dale wrote:
> 
>>> It makes sure that /run is available and writeable early in the boot
>>> process, whereas /var/run may not be and / may be mounted ro.
> 
>> Mine wouldn't be since I have /var on a separate partition.  I guess the
>> devs are getting ready for the ultimate screwup udev and friends is
>> putting in place.
> 
> No, it's avoiding a screwup. If you have /var on a separate partition, as
> I do, and something early in the boot process writes to /var/run
> (or /var/lock) whatever is written disappears when the var filesystem is
> mounted on /var. Using a tmpfs in / prevent this.
> 
> The alternative is to require /var is on the same filesystem as / or
> mounted from an initramfs. ISTR you were rather against such a move.
> 
> This move makes perfect sense, volatile but essential data is kept in ram
> rather than on a filesystem that may not always be available. If you are
> really bothered about the maximum size, remount it, although an option to
> specify this in rc.conf may possibly be useful in some situations.
> 
> 


I was talking about the /usr and/or /var being needed and the init
thingy.  I was not talking about /run using tmpfs or even being used.
In other words, the /usr and/or /var being needed very early in the boot
process is the screwup, not /run being used and on tmpfs.  It appears
that /run is sort of a temp thing while booting and just sort of sticks
around after getting booted, since it is there anyway.  Why not use it?

Sort of hard to explain my thinking sometimes.  lol  I have those days,
quite often I'm afraid.  :/

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"