From: Nix <nix@esperi.org.uk>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Rob Landley <rob@landley.net>,
Chris Lightfoot <chris@ex-parrot.com>
Subject: Re: [uml-devel] When /tmp is not tmpfs.
Date: Sun, 27 Nov 2005 19:43:25 +0000 [thread overview]
Message-ID: <87u0dx7u76.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <200511272010.03698.blaisorblade@yahoo.it> (blaisorblade@yahoo.it's message of "Sun, 27 Nov 2005 20:10:02 +0100")
On Sun, 27 Nov 2005, blaisorblade@yahoo.it whispered secretively:
> Plus, for deep troubleshooting (mainly for kernels) init=/bin/sh is useful.
init=/bin/busybox/sh is also useful for those cases when you've futzed
your libc. :)
>> > No - the kernel doesn't allow storing the full set of infos which are
>> > added by mount there. And frankly I don't want the kernel to do that.
>
>> Why not? It should. Only root can call mount(), so there's no real
>> danger that some attacker will stick megabytes of stuff in there.
>
> Yep, but I don't like the kernel to become a configuration repository... it's
> conceptually similar to the in-kernel Win32 registry (though it's smaller,
> yep).
Well, except that it's just storing, er, data about mount points. It
*already* has to store that!
--
`Y'know, London's nice at this time of year. If you like your cities
freezing cold and full of surly gits.' --- David Damerell
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-11-27 19:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 12:11 [uml-devel] When /tmp is not tmpfs Rob Landley
2005-11-24 20:40 ` Blaisorblade
2005-11-25 8:26 ` Rob Landley
2005-11-25 9:55 ` Jeff Dike
2005-11-25 9:48 ` Rob Landley
2005-11-25 10:52 ` Rob Landley
2005-11-25 11:26 ` Rob Landley
2005-11-25 14:56 ` Nix
2005-11-25 15:03 ` Chris Lightfoot
2005-11-25 15:36 ` Nix
2005-11-25 16:03 ` Rob Landley
2005-11-25 19:33 ` Nix
2005-11-25 20:18 ` Rob Landley
2005-11-25 21:04 ` Nix
2005-11-25 22:31 ` Rob Landley
2005-11-27 16:48 ` Blaisorblade
2005-11-27 18:17 ` Nix
2005-11-27 19:24 ` Rob Landley
2005-11-25 23:33 ` Blaisorblade
2005-11-26 2:12 ` Nix
2005-11-26 11:47 ` Rob Landley
2005-11-27 17:37 ` Blaisorblade
2005-11-27 18:35 ` Nix
2005-11-27 19:10 ` Blaisorblade
2005-11-27 19:43 ` Nix [this message]
2005-11-27 21:21 ` Rob Landley
2005-11-27 18:59 ` Rob Landley
2005-11-27 19:20 ` Blaisorblade
2005-11-27 21:41 ` Rob Landley
2005-11-29 16:52 ` Blaisorblade
2005-11-27 18:31 ` Nix
2005-11-28 1:07 ` Rob Landley
2005-11-29 16:08 ` Blaisorblade
2005-11-29 19:38 ` Rob Landley
2005-11-26 10:44 ` Rob Landley
2005-11-27 16:38 ` Blaisorblade
2005-11-27 18:49 ` Nix
2005-11-27 21:25 ` Rob Landley
2005-11-27 17:10 ` Blaisorblade
2005-11-25 23:46 ` Chris Lightfoot
2005-11-26 10:03 ` Rob Landley
2005-11-26 10:15 ` Chris Lightfoot
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=87u0dx7u76.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=blaisorblade@yahoo.it \
--cc=chris@ex-parrot.com \
--cc=rob@landley.net \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.