| 1 |
* Drake Wyrm schrieb am 18.05.11 um 00:26 Uhr: |
| 2 |
> Nirbheek Chauhan <nirbheek@g.o> wrote: |
| 3 |
> > 2011/5/18 Olivier Cr??te <tester@g.o>: |
| 4 |
> > > The main reason is that you want /run to be writable super early in the |
| 5 |
> > > boot process, before even / has been fscked and re-mounted. That means |
| 6 |
> > > you can do stuff like starting udevd in parallel with fsck of / which |
| 7 |
> > > means faster boot. This is one of the things required to get 1 second |
| 8 |
> > > boot. |
| 9 |
> > > |
| 10 |
> > > See http://lwn.net/Articles/436012/ |
| 11 |
> > > |
| 12 |
> > |
| 13 |
> > Related is that you don't need to manually wipe /tmp /var/run |
| 14 |
> > /var/lock via a service. They're automatically wiped when you reboot. |
| 15 |
> > This saves time during bootup. |
| 16 |
> |
| 17 |
> Even if you don't have to wipe them with a service, you're going to need |
| 18 |
> to mount them with a service. You'll need to mount /run as tmpfs, create |
| 19 |
> the /run/lock directory, and then mount /run/lock as tmpfs. Do you |
| 20 |
> really want to add that to localmount? |
| 21 |
|
| 22 |
Why mount /run/lock as tmpfs? If its created within /run its already |
| 23 |
tmpfs |
| 24 |
|
| 25 |
-Marc |
| 26 |
-- |
| 27 |
8AAC 5F46 83B4 DB70 8317 3723 296C 6CCA 35A6 4134 |
Archives