I watched the boot script execute. It seems there is this thing called netprofile that runs and gives an option called "test" and "default". If I don't select one, then I guess it goes to default and then complains about someone using 127.0.0.1
I chose the test option. I suspect it was one I set up some time ago when goofing around and exploring my Linux system (which I am using RIGHT NOW! :-D ). In short, I have network again.
Anyhow, mkinitrd returned some interesting things:
[root@localhost linux]# mkinitrd -v --allow-missing --builtin=loop /boot/initrd-2.6.11-6mdk_21MAY2005.img 2.6.11-6mdk_17MAY2005
Looking for deps of module ide-mod
Looking for deps of module ide-probe-mod
Looking for deps of module ide-core
Looking for deps of module ide-disk
Looking for deps of module ext3
Looking for deps of module jbd
Using modules: ./kernel/fs/jbd/jbd.ko ./kernel/fs/ext3/ext3.ko
Using /root/tmp as temporary directory.
/sbin/nash -> /root/tmp/initrd.Q15991/bin/nash
`/lib/modules/2.6.11-6mdk_17MAY2005/./kernel/fs/jbd/jbd.ko' -> `/root/tmp/initrd
copy from /root/tmp/initrd.Q15991/lib/jbd.ko(elf32-i386) to /root/tmp/initrd.Q15
`/lib/modules/2.6.11-6mdk_17MAY2005/./kernel/fs/ext3/ext3.ko' -> `/root/tmp/init
copy from /root/tmp/initrd.Q15991/lib/ext3.ko(elf32-i386) to /root/tmp/initrd.Q1
Loading module jbd.ko
Loading module ext3.ko
/sbin/udev-klibc -> /root/tmp/initrd.Q15991/sbin/udev
/sbin/udevstart-klibc -> /root/tmp/initrd.Q15991/sbin/udevstart
Contents of RCFILE:
echo "Loading jbd.ko module"
echo "Loading ext3.ko module"
echo Mounting /proc filesystem
mount -t proc /proc /proc
echo Mounting sysfs
mount -t sysfs none /sys
echo Creating device files
echo Starting udev
echo -n /sbin/hotplug > /proc/sys/kernel/hotplug
echo Creating root device
echo Mounting root filesystem
mount -o defaults --ro -t ext3 /dev/root /sysroot
echo 0x0100 > /proc/sys/kernel/real-root-dev
pivot_root /sysroot /sysroot/initrd
echo Initrd finished
Creating filesystem with size 504KB and 128 inodes
tune2fs 1.36 (05-Feb-2005)
Setting interval between check 0 seconds
mount: Could not find any loop device. Maybe this kernel does not know
about the loop device? (If so, recompile or `modprobe loop'.)
Can't get a loopback device
LOOK AT THAT!!! I could not even *force* a new initrd! Wow. And look at that system name: localhost. That is not my system's name. Mount just wanted to load that loopback. Why? It looks like mkinitrd is a script and not a binary. I'll dink with it later.
As suspected, mkinitrd was complaining about my presently running kernel.
I complained to my wife the troubles of Linux. She said why do I use it if it is so much trouble? I created these problems. I learn by fixing them. Linux allows me to explore the internals of the OS. Even with the issues I am having running this "beta" from Mandriva, I believe it to be at least as stable and more secure than Windows. Besides, I have a Pii, 450MHz; other than Windows 9x, and OS/2, I cannot think of another OS I can run on my box. Okay... there's QNX. Uh.. I think FreeBSD, too.
< nonsequitor> Hey, IBM, why not make OS/2 open source? < /nonsequitor>
Well... it is 6:43am and I need to get breakfast started.