Greetings,
So I need to evaluate several Linux distributions for deployment here
(converting from Red Hat Linux).
I downloaded/burned pentium3-1.4-20030911-cd{1,2}.iso
I have printed gentoo-x86-install.xml and amd reading as I go through the
steps.
I am using my IBM ThinkPad A21m as the initial test case install (just
rm'd Mandrake from it).
I selected a stage3 install with GRP. (Not certain about GRP, the install
document hasn't covered it much yet).
I have proceeded through the install procedure to step 16.3.
At this point genkernel has been at the point of : Running "make
modules"... (not exactly certain, text has scrolled past more on that
later). It has been at this stage for about 15 or more minutes.
I was afraid it was hung so I moved over to virtual console 2 and was
about to run `top' to confirm that it looked like cc et. al. were still
running. Before running top I ran `ls' on virtual console 2 and was
presented with lots and lots of errors regarding cloop:. eeek!
Messages follow (having to type it in)
hdc: tray open
end_request: I/O error, dev 16:00 (hdc), sector xxxxx
cloop: Read error at post xxxxxx in file /newroot/mnt/cdrom/livecd.cloop, 31093 bytes
lost
cloop: error -3 uncompressing block 264 65536/0/31093/0 5384715-5415808
and it continues on and on and on. Now mingetty is spawning too fast on
virtual console 2 (init delays for several minutes before trying to spawn
mingetty again as usual). Init is spewing these message onto virtual
console 1 so that is why I am not certain about what stage genkernel is in
now.
Strange thing is... I never ejected or even touched the CD drive (hdc)
since placing CD1 in for booting the system.
Am I likely to be hosed here or am I ok to ignore this for the moment and
let the build (genkernel) continue?
If I through genkernel (running on virtual console 1) into the background
(^z; bg) and run top build processes are consuming cpu cycles. cc1's are
coming and going (changing PIDs). So it looks like the build is happening
it is just taking an unusual amount of time (I think). It been perhaps 20
minutes or more so far since it last gave some output. (wow took 5 minutes
to write this).
Hmm. Ok change in behavior. kmod just spewed some messages to the console :
kmod: failed to exec /sbin/modprobe -s -k block-major-7, errno = 2
Yikes! Hmm... now genkernel seems to have completed. Scary.
My gentoo experience started with warm and fuzzy but is proceeding towards
cold and prickly. Wish me luck. Perhaps I'll be able to get grub
installed and this beast booted afterall.
- Mike Hogsett
--
[EMAIL PROTECTED] mailing list
