Peter Rajnoha [Wed, 2 Sep 2009 11:35:17 +0000 (13:35 +0200)]
LVM/DM rules in dracut
I've looked at the LVM rules used in dracut just recently
and it needs fixing - we should react to change events only
for DM devices, so we have to skip vol_id/blkid call on ADD:
Also, MD devices have their own rules, where vol_id/blkid
is called and where the symlinks are created (when looking
into raw initrd, this is in 64-md-raid.rules).
Also, if those rules are meant to be for DM devices only,
maybe we should skip symlink creation for the other devices
there, to keep the rules clean and straightforward. I think
we shouldn't create/recreate symlinks for non-dm devices in
LVM/DM rules (..should be in appropriate rules for that type
of device):
Victor Lowther [Thu, 20 Aug 2009 20:52:45 +0000 (15:52 -0500)]
Abstract out hostonly vs. generic module installation differences.
This introduces filter_kernel_modules, which should be used to install
all kernel modules that match whatever criteria you want.
If running in --hostonly, filter_kernel_modules will only consider
modules that are loaded in the kernel, otherwise it will consider
all the modules installed on the system for the appropriate kernel.
This drastically reduces initramfs generation time when using --hostonly
by eliminating lots of unneeded filesystem activity.
Victor Lowther [Thu, 20 Aug 2009 03:20:12 +0000 (22:20 -0500)]
Speed up loading block drivers when running with --hostonly
Instead of grovelling through all the modules available for the
kernel looking for block devices, only look at the modules that are
actually loaded. This speeds things up by a rather large amount
when generating the initramfs with --hostonly.
While we are at it, only load the filesystem module that will actually
be used for the root filesystem when running in --hostonly instead
of all the filesystem modules that happen to be loaded at the time.
Victor Lowther [Wed, 19 Aug 2009 20:51:54 +0000 (15:51 -0500)]
Abstract out vol_id vs. blkid usage
Since different distros may or may not use vol_id in udev, and blkid
is generally replacing vol_id, abstract them out into a function which
tries to use vol_id first and blkid second, on the assumption that
blkid can take over for vol_id if vol_id is no longer there.
Marc Grimme [Wed, 19 Aug 2009 08:40:02 +0000 (10:40 +0200)]
Syslog support for dracut
This module provides syslog functionality in the initrd.
This is especially interesting when complex configuration being
used to provide access to the device the rootfs resides on.
When this module is installed into the ramfs it is triggered by
the udev event from the nic being setup (online).
Then if syslog is configured it is started and will forward all
kernel messages to the given syslog server.
The syslog implementation is detected automatically by finding the
apropriate binary with the following order:
rsyslogd
syslogd
syslog-ng
Then if detected the syslog.conf is generated and syslog is started.
Bootparameters:
syslogserver=ip Where to syslog to
sysloglevel=level What level has to be logged
syslogtype=rsyslog|syslog|syslogng
Don't auto detect syslog but set it
Victor Lowther [Sat, 15 Aug 2009 12:38:26 +0000 (07:38 -0500)]
Some quotation cleanups in dracut-functions.
Quotes are generally not needed in when assigning one variable to another,
and are also not needed inside [[ ]] comaprisons, as word splitting and
pathname expansion are not performed in these cases.
Victor Lowther [Sat, 15 Aug 2009 03:51:25 +0000 (22:51 -0500)]
Update dracut-catimages to make it much more robust in the face of
image filenames with spaces, carriage returns, and other such nasty
characters in them. Bash arrays are very useful for these sorts of things.
It ends up installing the label.so control plugin which isn't supposed
to get installed into the initrd. this makes cairo and libX11 and all sorts of
things move into the initrd that aren't supposed to.
dracut-0.7-1 uses a modprobe option (-d) that exists only in
module-init-tools >= 3.7-9, but the 'Requires: module-init-tools'
of dracut is not version-specific.
Warren Togami [Tue, 4 Aug 2009 21:15:39 +0000 (17:15 -0400)]
Temporary hack to provide ifcfg files to OS in a way that might work with existing initscripts.
I am not happy about this. It shouldn't be the job of dracut to do this. The initscripts should
deal with the plain /dev/.initramfs/ifcfg/ directory accordingly. Doing this for now because
notting insists upon it. We need to clean this up after we network option passing working.
Jeremy Katz [Wed, 22 Jul 2009 20:14:00 +0000 (16:14 -0400)]
Support resetting the live overlay
If you're using a persistent overlay, you might want to reset it
at boot time if it has become corrupted somehow. Support using
reset_overlay as a command line optino to do so
Jeremy Katz [Wed, 22 Jul 2009 20:16:59 +0000 (16:16 -0400)]
And support passing in the persistent overlay
The persistent overlay can be specified with an overlay= argument
on the command line. We'll probably try to move this into the
root= syntax soon, but this is the old way that works
Jeremy Katz [Wed, 22 Jul 2009 20:08:49 +0000 (16:08 -0400)]
Support old syntax
livecd-creator previously added 'liveimg' and used root=CDLABEL=;
it's easy enough to support that old syntax for now at least
and it will make it easier to get people testing