The good news is i finally got a working ext3 install, got through
config and lilo and whatnot, i rebooted and...
the bad news is when i rebooted the lilo screen came and worked and
passed off to the kernel but for some reason the kernel paniced and
couldnt find root fs (sda8 or 0808 i think). same result when i tried
to boot to ext2 on sda5. so i used rescue disk to f* around with my
lilo.conf and rerun lilo (i am 99.9999999% sure the prob wasnt the conf
file, but rather the enviro from which i had run it earlier (sda8/ext3
install)). Anyway, I reboot and lilo is as good as it was before and
boots my ext2 (2.4.7-6) and i got to my mozilla messenger where i sit
now. However (i question if it is ext3 prob or 247-7 itself as i am a
clueless sob) the ext3 (sda8) which has 247-7 got to init, where i was
asked what runlevel to enter (i kinda like the choice, but my familia
dont :P) and when i pressed 5 (what i said at install), init told me it
was entering runlevel 5, and then proceeded to inform me that there were
no remaining processes in this runlevel, and locked up. kernel still
worked (yes, i did the numlock test and pressed that little useless
arrow on my keyboard that makes the kernel complain about the unkown
scancode) but ctrl-alt-del,ctrl-c,ctrl-d no worky worky. time for the
button. but the map to sdb (win) in my mbr was fine as is still my sda5
(247-6) and i cant think of what else... i can try to find my
etc/lilo.conf from ext3 which was altered during install to include like
7 entries, with different roots and images and whatever if it would
help. note that this is what gave the kernel panic, and the lilo i run
from sda5 while in rescue mode was good, although so was other. maybe
root info got mixed up or some...i dunno. whatever, ask me for more
info (but tell me what you want).
