https://bugzilla.redhat.com/show_bug.cgi?id=515589
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.
https://bugzilla.redhat.com/show_bug.cgi?id=515630
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.
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.
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
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
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
Fedora/Red Hat live images are implemented as an ext3fs inside of
a squashfs. Writability is achieved with a device-mapper snapshot
on top of that.
This gives the basic support without a lot of things like persistent
overlays, iso md5sum checking, etc and also with a new basic syntax
that has to be specified as root=live:LABEL=...
Hello,
Now a fact that the path is full is checked by
[[ -x $1 ]]
But if the working directory is /bin or a directory with a file named
"mount",
this condition will be met for "inst mount", and "mount" will not be copied
into initrd at all.
As discussed before, it would be nice to be able to specify
the iscsi chap credentials inside the netroot=iscsi:.....
syntax, this patch implements this in a backwards compatible way, like
this:
iscsi:username:pass@127.0.0.1::3260::iqn.2009-01.com.example:testdisk
iscsi:username:pass:reverse:pass@127.0.0.1::3260::iqn.2009-01.com.example:test
The only downside is that the backwards compatibility is broken when there
is an @ in the iscsi target name (very unlikely), that can still be used,
but only like this:
iscsi:@192.168.1.100::3260::iqn.2009-01.com.example:testdi@sk
Victor Lowther