During the bombing raid on 11 May 2001 14:38:48 +0200, Juan Quintela was heard
mumbling in fear:
> >>>>> "alex" == alex <[EMAIL PROTECTED]> writes:
>
> alex> I was the one having problems with my mkinitrd and such when I did the
> alex> upgrade to
> alex> 2.4.3-27mdk. Well I dared to do it once more (on another machine) and
> alex> everything
> alex> worked smothly, the only thing I can tell I did differently was not
> alex> to upgrade lilo at the same time...
> alex> This time I had no problems with initrd, booting or supermount (amazing
> alex> it actually worked...:)
>
> Do you mind to resend me the mail where you describes the problems
> with 2.4.3-27mdk???? I lost that email :( I didn't see that report.
> 2.4.3-26mdk has a aic7xxx problem at boot, but I didn't see anything
> bug report here.
Here's mine :)
[root@ayesha boot]# mkinitrd /boot/initrd-2.4.3-27mdk 2.4.3-27mdk
mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
/tmp/initrd.img.nh0jhC: Unknown code P3p 193 while setting up superblock
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
or too many mounted file systems
Can't get a loopback device
I *think* the problem is e2fsprogs-1.19-5mdk and not the kernel itself
Vox, who is glad that he does -ivh and not -Uvh
--
Pain is the gift of the gods, and I'm the one they chose as their messenger....
For info on safety in the BDSM lifestyle http://www.the-vox.com
Think of the Linux community as a niche economy isolated by its beliefs. Kind
of like the Amish, except that our religion requires us to use _higher_
technology than everyone else. -- Donald B. Marti Jr.
Vox populi, vox deii....
