Ask Shadowman

October 2003

October. Crisp cold air, burning leaves, and anti-Linux memo leaks. You, however, are too old to trick or treat; even if you weren't, everyone else's lack of costume enthusiasm and ingenuity has got you down. To top it all off, your moon is in Saturn and your server won't boot. Time once again for the Shadowy one. Not the Great Pumpkin, but he who has but one name. Like Donatello, or that man that they went and decided to just go ahead and call Horse. He is... the Shadowman.

Got a question that you'd like Shadowman to answer? Ask him.

Gerry M. was stranded, got a warning for repeated calls to 911 and cried:
I made some changes to my grub.conf and now my machine won't boot. I attempted to reinstall grub, but since I can't boot, I couldn't. Rescue me.

Shadowman says:
There are a few things you can try, depending on how far into not booting you get. Or don't. Which are:

1. Did you listen to Shadowman on other posts to keep the last known working configuration in grub, along with the kernel it referred to? If so, the old one should still boot.

You're still reading. Sigh.

2. Do you see the grub menu at boot? If so:

-press 'e' to edit the kernel you are trying
-then 'e' again on the kernel line
-add an 's' or '1' or 'single' to the end
-hit enter, then 'b' to boot.

This will bring you to a shell and you can edit grub.conf. (Remember step one and leave a working config, even if you comment it out, since if you are here, you didn't before.)

If all has gone kablooie, you don't remember what you've changed, and drunk with your own hubris you went and deleted the last working configuration and associated kernel; Shadowman will help, despite what Darwin would say on this matter, and move on to option 3.

3. Grab your install media:

-Put in the first cd and boot
-Type 'linux rescue' at the prompt
-'mount /mnt/cdrom'
-cd to the RPMS directory
-rpm -Fvh grub-Package-version

The old Shadow-sense is tingling, which is either that you will be fine or a hot flash. And Shadowman's too young and male for the latter.

Liz O. hadn't seen the new packages she was expecting and wondered:
I was reading about a couple of recent errata and decided to make sure RHN had already taken care of it, since I have it set to auto update. To my surprise, not only was I missing the packages I was worried about, but a few others. Running up2date gave me 'certificate verify failed'. I know I've paid for the year, so I should be active, right?

Shadowman says:
That's an easy fix. A bit back, the RHN SSL cert expired. Affecting use of up2date, rhn_register and RHN applet. Long story short:

Go here:
And follow the instructions, but since you're so good at following instructions what you do is download the RPMs you need into one directory, cd to the directory, and run rpm -Fvh *.rpm

Then you can test to make sure that everything works with 'up2date -p'

If you're really sure you can trust your friendly neighborhood Shadowman to know what's good for you run:

wget -q -O - | /bin/bash

Then you can run "up2date up2date".

MK left without his AK, and it was not a good day:
I'm getting the following error message when i try to run the ./configure command before samba installation:

configure: error: no acceptable cc found in $PATH
What does it mean??

Shadowman says:
It means just what is says, hombre. But since you asked, either you have su'd to root and it lost the path, or you have not installed gcc.

Type 'locate cc | less' and you *should* see /usr/bin/cc... if so, it's the path and you need to 'su -' to root instead of 'su' OR gcc is not installed, which can be remedied easily enough by, well installing gcc.

up2date -i gcc

Will get it and dependencies via RHN.