3:49 p.m.
I read that dracut is to replace initrd and nash in f12.
I installed f12α, but dracut was not there, only the old
initrd and nash.
If I want to change to dracut, what do I do? Which packages
do I need to install, etc?
Does it make an initram on the fly, or do I install a
package? I noticed that there is dracut-kernel and dracut-
generic available, along with a host of other packages.
Do I uninstall nash and initrd? Or do I keep them as a fall-
back? If so, how would I configure that? What changes do I
make to grub.conf and elsewhere to enable dracut and disable
nash/initrd?
A concern: Does it work reliably? I am not going to face a
situation where I boot and encounter a kernel panic and be
unable to get into my system because there is no initram or
something? That could be almost impossible to solve :-(
6:04 p.m.
On Sat, Sep 19, 2009 at 14:49:55 -0600,
Petrus de Calguarium <kwhiskerz(a)gmail.com> wrote:
If I want to change to dracut, what do I do? Which packages
do I need to install, etc?
For awhile dracut was getting used when kernels were built (and hence you
may have used it withotu realizing it). But because of concerns of being
able to provide appropriate source, things were switch to doing it in
post install, similar to how mkinitrd is used.
Does it make an initram on the fly, or do I install a
package? I noticed that there is dracut-kernel and dracut-
generic available, along with a host of other packages.
You need at least dracut and dracut-kernel. Installing a recent kernel
should pull those in.
Do I uninstall nash and initrd? Or do I keep them as a fall-
back? If so, how would I configure that? What changes do I
make to grub.conf and elsewhere to enable dracut and disable
nash/initrd?
You don't need to do that.
A concern: Does it work reliably? I am not going to face a
situation where I boot and encounter a kernel panic and be
unable to get into my system because there is no initram or
something? That could be almost impossible to solve :-(
If that happens you can still boot the previous kernel. (I even needed to
do that for an earlier version of dracut that had problems with not
using the suggested minor device numbers for raid arrays.) If you do
have a problem, be sure to file a bug.
8:20 p.m.
Bruno and Tom wrote some stuff:
...
I notice that I have dracut (I installed it manually a few
weeks ago) and also dracut-kernel (must have been a
dependency some time ago).
So... Are you guys telling me that I am already using dracut
without realizing it?
I am not sure what Bruno meant by "switch to doing... in post
install?" Like I have to activate it, post install, or it is
now activated without intervention on my part?
9 p.m.
On Sat, Sep 19, 2009 at 19:20:35 -0600,
Petrus de Calguarium <kwhiskerz(a)gmail.com> wrote:
I am not sure what Bruno meant by "switch to doing... in post
install?" Like I have to activate it, post install, or it is
now activated without intervention on my part?
It's a script that gets run after the kernel files have been copied into
place. You don't manually do anything. Previously the file that was used
was already built into the rpm and copied into place.
9:54 p.m.
Bruno Wolff III wrote:
It's a script that gets run after the kernel files have
been copied into
place. You don't manually do anything.
Ok. Sounds good. I like "You don't manually do anything"
improvements :-) It just works on its own, without me needing
to fiddle. I notice that I have 5 initramfs files in /boot,
but only 3 kernels. I guess it doesn't yet clean up after
itself (when yum installs a new kernel and removes the
oldest, leaving only 3). I suppose it is safe for me to
remove those for which I no longer have a kernel.
10:27 p.m.
On Sat, Sep 19, 2009 at 20:54:31 -0600,
Petrus de Calguarium <kwhiskerz(a)gmail.com> wrote:
Bruno Wolff III wrote:
> It's a script that gets run after the kernel files have
been copied into
> place. You don't manually do anything.
Ok. Sounds good. I like "You don't manually do anything"
improvements :-) It just works on its own, without me needing
to fiddle. I notice that I have 5 initramfs files in /boot,
but only 3 kernels. I guess it doesn't yet clean up after
itself (when yum installs a new kernel and removes the
oldest, leaving only 3). I suppose it is safe for me to
remove those for which I no longer have a kernel.
If that's the case, it's a bug and should be reported.
If the initramfs files aren't referred to in your grub.conf, they aren't
being used.
12:53 a.m.
Bruno Wolff III wrote:
If the initramfs files aren't referred to in your grub.conf,
they aren't
being used.
The 3 newest, for which there is a matching kernel, are referred
to in grub.conf. The other 2, matching old kernels long since
deleted, are not referred to anywhere in grub.conf.
I will delete them manually and watch what happens next kernel.
Otherwise, I will be forced to acknowledge that this glitch has
not been repaired and that it is indeed an active bug.
5:19 a.m.
2009/9/20 Bruno Wolff III <bruno(a)wolff.to>:
If the initramfs files aren't referred to in your grub.conf, they
aren't
being used.
I have initrd and intiramfs images for my latest kernel in /boot
I did run plymouth-set-theme --rebuild (or whatever) to enable
"charge" instead of "text" theme, so could that explain it?
5383
days inactive
5385
days old
8 comments
4 participants
participants (4)
-
Andy Burns -
Bruno Wolff III -
Petrus de Calguarium -
Tom Horsley