I would like to follow debian and add a tmpfs to /lib/init/rw , which would
serve as a transition from initramfs to real root for files from daemons, which
need to transition from initramfs, like mdmon, dmeventd, rpc.statd, etc.
FYI, /var is not an option, because it can be on a seperate partition.
Currently we use /dev/.initramfs, which is just a workaround, because /dev is
already available.
What do you think?
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
02-04-2010, 12:12 PM
Jon Masters
Proposal: /lib/init/rw
On Thu, 2010-02-04 at 11:09 +0100, Harald Hoyer wrote:
> I would like to follow debian and add a tmpfs to /lib/init/rw , which would
> serve as a transition from initramfs to real root for files from daemons, which
> need to transition from initramfs, like mdmon, dmeventd, rpc.statd, etc.
>
> FYI, /var is not an option, because it can be on a seperate partition.
>
> Currently we use /dev/.initramfs, which is just a workaround, because /dev is
> already available.
>
> What do you think?
Is that specific directory LSB/FHS or similar? I didn't check, but if it
is it seems like a reasonable idea.
Jon.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
02-04-2010, 02:34 PM
Bill Nottingham
Proposal: /lib/init/rw
Harald Hoyer (harald@redhat.com) said:
> I would like to follow debian and add a tmpfs to /lib/init/rw , which would
> serve as a transition from initramfs to real root for files from daemons, which
> need to transition from initramfs, like mdmon, dmeventd, rpc.statd, etc.
My bikeshedding opinion is /lib/init/state might be better. But if
it's just to be temporary, why isn't /dev/.initramfs OK?
Bill
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
02-04-2010, 02:47 PM
Slava Zanko
Proposal: /lib/init/rw
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bill Nottingham wrote:
> My bikeshedding opinion is /lib/init/state might be better. But if
> it's just to be temporary, why isn't /dev/.initramfs OK?
+1.
After starting udev daemon old content of /dev catalog will be hidden
(/dev/.initramfs too). So this better than /lib/init will always visible.
On Thu, 2010-02-04 at 17:47 +0200, Slava Zanko wrote:
> Bill Nottingham wrote:
> > My bikeshedding opinion is /lib/init/state might be better. But if
> > it's just to be temporary, why isn't /dev/.initramfs OK?
> +1.
>
> After starting udev daemon old content of /dev catalog will be hidden
> (/dev/.initramfs too). So this better than /lib/init will always visible.
But isn't this a quirk of how our early boot works?
> Currently we use /dev/.initramfs, which is just a workaround,
> because /dev is already available.
I'd agree with Bill that "state" is a nicer name than rw but Debian has
already been using the rw path name for some time now.
Although it's not directly related there's some discussion on the choice
of the path in this Debian bug:
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
02-04-2010, 05:13 PM
Doug Ledford
Proposal: /lib/init/rw
On 02/04/2010 05:09 AM, Harald Hoyer wrote:
> I would like to follow debian and add a tmpfs to /lib/init/rw , which would
> serve as a transition from initramfs to real root for files from daemons, which
> need to transition from initramfs, like mdmon, dmeventd, rpc.statd, etc.
>
> FYI, /var is not an option, because it can be on a seperate partition.
>
> Currently we use /dev/.initramfs, which is just a workaround, because /dev is
> already available.
>
> What do you think?
I think it's silly to create a second rw tmpfs location. I think this
for two reasons: 1) if you aren't going to move the stuff out of this
temporary location to where it belongs after the filesystems are brought
up, then this location becomes a catch all that multiple things might
need to end up adding to their search path (eg., mdmon would create pid
files here, if those pid files aren't moved or otherwise made accessible
under /var/run later, then subsequent attempts to use things like status
mdmon from an initscript would need to be taught about the new pid file
locations which is something we want to avoid like the plague) and 2) if
you *are* going to do the right thing and move things to their right
locations later, then whether you use /lib/init/rw or /lib/init/state or
/dev/crap_we_wont_leave_here_under_penalty_of_death makes no difference,
it's going to be emptied and deleted eventually anyway, however, adding
a second mount point adds complexity to the early boot process which is
something you always want to be as simple and failproof as possible, so
creating a new namespace for the sake of anal retentiveness about naming
is in fact counter productive and the wrong thing to do. As such, I say
suck it up and deal with /dev/.initramfs.