Mailinglist Archive: opensuse (1898 mails)

[Roger Oberholtzer <roger@xxxxxx>]

On Thu, 2010-07-22 at 11:57 +0200, Istvan Gabor wrote:
> 2010. július 22. 10:45 napon Roger Oberholtzer <roger@xxxxxx> írta:
>
> > On Thu, 2010-07-22 at 09:53 +0200, Roger Oberholtzer wrote:
> >
> > > Perhaps I should make a copy of the current initrd and make a grub entry
> > > that boots with that. And make a new initrd with the new modules and
> > > make a grub entry that boots with that instead?
> >
> > Bad form to follow my on message. But I could not wait for confirmation
> > on the list. So I made a new initrd for the new system, removing /
> > adding modules as needed. It works. The disk can live in boot hardware
> > systems, selecting the appropriate initrd via grub.
>
> Could you please write down how to add the required modules to a new initrd 
> image?
> I know it is mentioned in mkinitrd manual but how does the command look in 
> practice?
> Could you give the command line(s) you used when you created your initrd?

I first made a copy of the existing initrd file in /boot (the actual
file, not the symlink to it), and made an entry in grub to boot with
this file. At that point there is only a name change.

I then used YAST: System->/etc/sysconfig Editor. In that, I selected
System->Kernel->INITRD_MODULES, and edited as I saw fit. When I saved
the change (after a confirmation), yast rebuilt the initrd file. Your
original initrd file will be overwritten. Thus the step above.

Just be careful you do not remove something that is needed. This is why
I made the safety copy and grub entry to access it: just in case I mess
up.

-- 
Roger Oberholtzer

OPQ Systems / Ramböll RST

Ramböll Sverige AB
Krukmakargatan 21
P.O. Box 17009
SE-104 62 Stockholm, Sweden

Office: Int +46 10-615 60 20
Mobile: Int +46 70-815 1696

-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx