public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Drake Wyrm <wyrm@haell.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: use of the /run directory
Date: Tue, 17 May 2011 15:26:11 -0700	[thread overview]
Message-ID: <20110517222611.GA652@fraenk> (raw)
In-Reply-To: <BANLkTi=aD0nLpTQwg18AegNKxe8DZUMXYg@mail.gmail.com>

Nirbheek Chauhan <nirbheek@gentoo.org> wrote:
> 2011/5/18 Olivier Cr??te <tester@gentoo.org>:
> > The main reason is that you want /run to be writable super early in the
> > boot process, before even / has been fscked and re-mounted. That means
> > you can do stuff like starting udevd in parallel with fsck of / which
> > means faster boot. This is one of the things required to get 1 second
> > boot.
> >
> > See http://lwn.net/Articles/436012/
> >
> 
> Related is that you don't need to manually wipe /tmp /var/run
> /var/lock via a service. They're automatically wiped when you reboot.
> This saves time during bootup.

Even if you don't have to wipe them with a service, you're going to need
to mount them with a service. You'll need to mount /run as tmpfs, create
the /run/lock directory, and then mount /run/lock as tmpfs. Do you
really want to add that to localmount?

-- 
Confucius is inscrutable.
God is ineffable.
Beer is inevitable.



  reply	other threads:[~2011-05-17 22:27 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 16:57 [gentoo-dev] rfc: use of the /run directory William Hubbs
2011-05-17 18:11 ` Peter Volkov
2011-05-17 18:28   ` Nirbheek Chauhan
2011-05-17 18:43     ` Ângelo Arrifano
2011-05-17 18:50       ` Nirbheek Chauhan
2011-05-17 19:11       ` Peter Volkov
2011-05-17 19:20         ` Ângelo Arrifano
2011-05-17 19:07     ` William Hubbs
2011-05-17 20:35       ` James Cloos
2011-05-17 20:40         ` Markos Chandras
2011-05-18  0:06           ` James Cloos
2011-05-18  0:43             ` William Hubbs
2011-05-17 19:20     ` Panagiotis Christopoulos
2011-05-17 19:46       ` William Hubbs
2011-05-18  1:31         ` [gentoo-dev] " Duncan
2011-05-18  1:36         ` [gentoo-dev] " Jeroen Roovers
2011-05-18  5:49           ` Eray Aslan
2011-05-18 14:45             ` Henry Gebhardt
2011-05-18 14:51               ` Samuli Suominen
2011-05-18 15:02                 ` [gentoo-dev] " Jonathan Callen
2011-05-17 19:48       ` [gentoo-dev] " Nirbheek Chauhan
2011-05-17 20:00         ` Olivier Crête
2011-05-17 20:07           ` Michał Górny
2011-05-17 20:11           ` Amadeusz Żołnowski
2011-05-17 20:23           ` Rich Freeman
2011-05-17 20:20         ` Panagiotis Christopoulos
2011-05-17 20:28           ` Michał Górny
2011-05-17 20:54           ` Olivier Crête
2011-05-17 21:00             ` Nirbheek Chauhan
2011-05-17 22:26               ` Drake Wyrm [this message]
2011-05-17 22:36                 ` Marc Schiffbauer
2011-05-17 22:46                 ` Nirbheek Chauhan
2011-05-18  0:06                 ` William Hubbs
2011-05-17 22:50 ` Ciaran McCreesh
2011-05-18  0:12   ` William Hubbs
2011-05-23  6:30     ` Ciaran McCreesh
2011-05-23  7:05       ` Nirbheek Chauhan
2011-05-23  7:11         ` Ciaran McCreesh
2011-05-23  7:13         ` Michał Górny
2011-05-23  8:30           ` Nirbheek Chauhan
2011-05-20  8:58 ` Luca Barbato
2011-05-20 16:54   ` Mike Pagano
2011-05-22 19:13     ` Luca Barbato
2011-05-22 21:12       ` Ondřej Súkup

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=20110517222611.GA652@fraenk \
    --to=wyrm@haell.com \
    --cc=gentoo-dev@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