check it!

i integrated google search into the blog. nifty

ever fuck up your initrd?

i did…

now, had this been windows, i fucked up some boot module. i have learned alot in the last 24 hours. like, what mkinitrd does. i was screwing around in yast, and decided to change my ide controller to ata_piix from just piix, weeeelllllll…. my laptop didnt like that. when i rebootedit tried to read my root device, and yeah, couldnt yay!

well, i closed it, and didnt deal with it until about 2 hours ago. i started poking around on the internet, kindof in a hopeless wander. see, my laptop’s CDrom doesnt work. its not the device, is something in the connection to the motherboard. so that threw out the idea of slapping in a rescue disk and going strait to bash. no no no, instead i downloaded Knoppix and tried to boot from USB. that didnt work, because my bios wont boot from usb

so, last resort. i popped out the hard drive and slapped it into my old 600e thinkpad. thank god for that guy. i inserted my rescue disk and got into bash. i poked around a bit, mounted hda2 to /tmp and discovered how the hell this boot process works.  im proud of myself, ive never used mkinitrd before, nor did i even know it existed. but after a few attempts and figuring out why “no modules loaded” kept showing up, i got an initrd-032978409327y40-whatever to compile. i added it to grub and voila.. back into my system

i highly suggest to anyone out there that you DO NOT mess with the ide controller, unless you know FOR SURE what youre doing. ignoring those warnings will probably mess up your system.. if it sayd “DONT TOUCH” then dont touch it.

now, had this been windows, i would have given up, kicked the box, and left for some beer. because we ALL know that it wouldnt have been fixed, all my data would have been lost and i would have had to buy a new hard drive. at least thats what geeksquad would say.