From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Apologize to everyone for my nonprofessional
Date: Sat, 15 Oct 2011 15:44:38 +0200 [thread overview]
Message-ID: <20111015154438.686ca63b@rohan.example.com> (raw)
In-Reply-To: <CADPrc83X8ewGevW6-1zzowC01=jHfq_zZ3LSp0LAphyp4gzQNg@mail.gmail.com>
On Sat, 15 Oct 2011 00:34:10 -0700
Canek Peláez Valdés <caneko@gmail.com> wrote:
> /var != /var/run
> /var != /var/lock
>
> /var/run is going in /run, but /var/run (by definition) only contains
> things like PID files and runtime sockets. In the same vein, /var/lock
> also is going into /run/lock. I have acknowledged this from the very
> beginning, and I have been pointing out that implying that because
> those two (really small and bounded) directories of /var are going
> into /run and /run/lock, it doesn't mean that the whole /var will go
> into /. That is disinformation.
It's tirely feasible to need to create a lock file before /var is
mounted, so it makes perfect sense to put those directories on /.
Even better is to create them as a tmpfs so you don't even need disk
drives to get a minimallt usable system.
--
Alan McKinnnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2011-10-15 13:46 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 15:43 [gentoo-user] Apologize to everyone for my nonprofessional Lavender
2011-10-14 15:52 ` Michael Mol
2011-10-14 16:15 ` Dale
2011-10-14 21:41 ` Neil Bothwick
2011-10-14 22:47 ` Dale
2011-10-15 5:10 ` Pandu Poluan
2011-10-15 6:56 ` Dale
2011-10-15 7:09 ` Pandu Poluan
2011-10-15 7:34 ` Canek Peláez Valdés
2011-10-15 7:50 ` Canek Peláez Valdés
2011-10-15 8:35 ` Michael Schreckenbauer
2011-10-15 8:42 ` Canek Peláez Valdés
2011-10-15 8:53 ` Michael Schreckenbauer
2011-10-15 9:11 ` Canek Peláez Valdés
2011-10-15 9:31 ` Michael Schreckenbauer
2011-10-15 9:47 ` Canek Peláez Valdés
2011-10-15 10:05 ` Michael Schreckenbauer
2011-10-15 10:34 ` Canek Peláez Valdés
2011-10-15 10:45 ` Michael Schreckenbauer
2011-10-15 11:04 ` Canek Peláez Valdés
2011-10-15 19:23 ` Michael Schreckenbauer
2011-10-15 10:49 ` Canek Peláez Valdés
2011-10-15 18:57 ` Joost Roeleveld
2011-10-15 23:25 ` Mike Edenfield
2011-10-15 8:37 ` Dale
2011-10-15 9:02 ` Canek Peláez Valdés
2011-10-15 9:15 ` Michael Schreckenbauer
2011-10-15 9:21 ` Canek Peláez Valdés
2011-10-15 9:32 ` Michael Schreckenbauer
2011-10-15 9:49 ` Canek Peláez Valdés
2011-10-15 9:37 ` Dale
2011-10-15 9:54 ` Canek Peláez Valdés
2011-10-15 17:23 ` Dale
2011-10-15 14:23 ` pk
2011-10-15 16:46 ` Claudio Roberto França Pereira
2011-10-15 19:20 ` Michael Schreckenbauer
2011-10-15 21:15 ` Neil Bothwick
2011-10-15 9:53 ` Neil Bothwick
2011-10-15 10:10 ` Canek Peláez Valdés
2011-10-15 11:31 ` Neil Bothwick
2011-10-15 12:19 ` Jonas de Buhr
2011-10-15 13:44 ` Alan McKinnon [this message]
2011-10-15 13:48 ` Alan McKinnon
2011-10-15 18:43 ` Joost Roeleveld
-- strict thread matches above, loose matches on Subject: below --
2011-10-14 16:05 [gentoo-user] 回复： " Lavender
2011-10-17 12:45 ` du yang
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=20111015154438.686ca63b@rohan.example.com \
--to=alan.mckinnon@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