In message from "Curt Purdy"
Mikhail Kuzminsky wrote:
But now ./grub-install --root-directory=/mnt --debug /dev/hda
finished w/errors like
/usr2/sbin/grub --batch --device-map=/mnt/boot/grub/device.map no such file or directory
I had similar problems but then did a manual install, pick last option (like bootloader or something), it will pick 3 of the first as dependancies, and pick the middle option letting it do setup for you (I wasted a lot of time picking the third manual option.) It rebuilt everything, put it where it was supposed to and booted fine. It's hell when your OS is smarter than you are ;) I'm sorry, I didn't understood your statements about options selections ... :-(
The problem looks for me as some my "head failure" ;-): /usr2/sbin/grub (i.e. "manual" grub execution !) says "No such file or directory". This situation dosn't depend from mounting point (/usr2 or /mnt or /usr etc), grub is executable (from ls -l) etc. So the possible reason of like "behaviour of grub" looks that grub requires some additional file(s) (by default) which is/are not presented on the places (pathes) where grub want "to see" them. Is it right ? Yours Mikhail
Curt Purdy CISSP, GSEC, MCSE+I, CNE, CCDA Information Security Engineer DP Solutions
----------------------------------------
If you spend more on coffee than on IT security, you will be hacked. What's more, you deserve to be hacked. -- former White House cybersecurity adviser Richard Clarke
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com