Prev: xterm vs. [m]rxvt (WAS: Re: Corporate creep in Linux?(mini-rantette))
Next: hugesmp.s and initrd.img
From: appzer0 on 16 Sep 2009 17:24
emmel a �crit :

> And installpkg and two reboots later (Can't that stupid mkinitrd call
> lilo for me?) it works. Seriously, that script could do some work. A
> failsafe for operating in the wrong directory and automatic executing of
> lilo (if used) would be no end of good. BTW, does anyone know why
> cryptsetup is a link to cryptsetup.static? Wasn't there some problem
> with the static version?

mkinitrd just does its job: make an initrd, nothing more. I suggest you
try the script in /usr/share/mkinitrd/mkinitrd_command_generator.sh to
generate a proper command. Obviously, lilo.conf must be updated to take
your initrd into acccount, then re-run it by 'lilo -v'.

One more point: I always delete the /boot/initrd-tree/ dir before
generating a new one, just in case.

Note: the mkinitrd_command_generator.sh is in the Slack13.0 'mkinitrd'
package, not in 12.2.

appzer0
From: emmel on 17 Sep 2009 05:54
Thus gabriel spoke:

>> And installpkg and two reboots later (Can't that stupid mkinitrd call
>> lilo for me?) it works. Seriously, that script could do some work. A
>> failsafe for operating in the wrong directory and automatic executing of
>> lilo (if used) would be no end of good. BTW, does anyone know why
>> cryptsetup is a link to cryptsetup.static? Wasn't there some problem
>> with the static version?
>
> cryptsetup is a link to cryptsetup.dynamic here. Seems that mkinitrd
> screwed that too.
> I suggest you to take a big look at the mkinitrd script ...

It's the same on my other box, though. And there also is a
cryptsetup.dynamic.
From: emmel on 17 Sep 2009 05:59
Thus appzer0 spoke:

> emmel a écrit :
>
>> And installpkg and two reboots later (Can't that stupid mkinitrd call
>> lilo for me?) it works. Seriously, that script could do some work. A
>> failsafe for operating in the wrong directory and automatic executing of
>> lilo (if used) would be no end of good. BTW, does anyone know why
>> cryptsetup is a link to cryptsetup.static? Wasn't there some problem
>> with the static version?
>
> mkinitrd just does its job: make an initrd, nothing more. I suggest you
> try the script in /usr/share/mkinitrd/mkinitrd_command_generator.sh to
> generate a proper command. Obviously, lilo.conf must be updated to take
> your initrd into acccount, then re-run it by 'lilo -v'.

Wasn't aware of that one... I'll have a look. I just got somewhat
freaked out when I had to restart the machine yet again, because I had
forgotten running lilo. Yet again. :-(

> One more point: I always delete the /boot/initrd-tree/ dir before
> generating a new one, just in case.

Well, that's what -c is /supposed/ to do.

> Note: the mkinitrd_command_generator.sh is in the Slack13.0 'mkinitrd'
> package, not in 12.2.

Not a problem for me, I'm actually running current. The only DVD I had
lying around was 12.2, though. And it was real fun to reinstall gzip and
tar when I got a tar error saying that gzip couldn't be found. Would
have been funny if it hadn't been so annoying. I'm just glad Slackware
packages are easily used manually.
From: emmel on 17 Sep 2009 06:06
Thus emmel spoke:

> Thus appzer0 spoke:
>
>> emmel a écrit :
>>
>>> And installpkg and two reboots later (Can't that stupid mkinitrd call
>>> lilo for me?) it works. Seriously, that script could do some work. A
>>> failsafe for operating in the wrong directory and automatic executing of
>>> lilo (if used) would be no end of good. BTW, does anyone know why
>>> cryptsetup is a link to cryptsetup.static? Wasn't there some problem
>>> with the static version?
>>
>> mkinitrd just does its job: make an initrd, nothing more. I suggest you
>> try the script in /usr/share/mkinitrd/mkinitrd_command_generator.sh to
>> generate a proper command. Obviously, lilo.conf must be updated to take
>> your initrd into acccount, then re-run it by 'lilo -v'.
>
> Wasn't aware of that one... I'll have a look. I just got somewhat
> freaked out when I had to restart the machine yet again, because I had
> forgotten running lilo. Yet again. :-(

post scriptum: mkinitrd_command_generator.sh complained about a missing
lvdisplay, a missing /proc/mdstat and then basicly told me to use
'mkinitrd -c -k 2.6.30.5 -f ext3 -r root -C /dev/sda3 -o /boot/initrd.gz'.
Not very useful IMHO. Well, at least it got my crypto setup right.
From: Eric Hameleers on 17 Sep 2009 14:57
emmel schreef:
> Thus emmel spoke:
>
>> Thus appzer0 spoke:
>>
>>> emmel a écrit :
>>>
>>>> And installpkg and two reboots later (Can't that stupid mkinitrd call
>>>> lilo for me?) it works. Seriously, that script could do some work. A
>>>> failsafe for operating in the wrong directory and automatic executing of
>>>> lilo (if used) would be no end of good. BTW, does anyone know why
>>>> cryptsetup is a link to cryptsetup.static? Wasn't there some problem
>>>> with the static version?
>>> mkinitrd just does its job: make an initrd, nothing more. I suggest you
>>> try the script in /usr/share/mkinitrd/mkinitrd_command_generator.sh to
>>> generate a proper command. Obviously, lilo.conf must be updated to take
>>> your initrd into acccount, then re-run it by 'lilo -v'.
>> Wasn't aware of that one... I'll have a look. I just got somewhat
>> freaked out when I had to restart the machine yet again, because I had
>> forgotten running lilo. Yet again. :-(
>
> post scriptum: mkinitrd_command_generator.sh complained about a missing
> lvdisplay, a missing /proc/mdstat and then basicly told me to use
> 'mkinitrd -c -k 2.6.30.5 -f ext3 -r root -C /dev/sda3 -o /boot/initrd.gz'.
> Not very useful IMHO. Well, at least it got my crypto setup right.

Why do you think it was not useful to you?
It did show you the exact command you need to use in order to create
your initrd. The script is not called "mkininit command generator" for
fun... it does what the name implies.

Eric
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: xterm vs. [m]rxvt (WAS: Re: Corporate creep in Linux?(mini-rantette))
Next: hugesmp.s and initrd.img