Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Because of a slightly buggy/eccentric harddisk (remind me to back up!) I have to chroot into another partition where I have knoppix and run lilo from there. I've done this before, the problem is that when I chroot I get an infinite loop like this:
/dev/null : access denied
/dev/null : access denied
/dev/null : access denied
/dev/null : access denied
/dev/null : access denied
/dev/null : access denied
...etc
I am running as root of course. The access denied must have something to do with shell permissions and/or what chroot actually does beneath the hood.
But I have no idea how to avoid it. I've avoided it before, but I can't remember how!
I wonder if I should send a bug to gnu coreutils? True, it is something in my (Fedora core 1) setup, but going into a loop like this is in any case a pretty bad handling of whatever the problem is... If I had a sensible error message it would have been a lot easier.
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
What's the command you issue to chroot?
What's the actual problem you face when you try to run lilo from your normal shell?
That error is a bug, but if Fedora wraps chroot (bad idea, but you never know), for example, then it's not necessarily GNU's fault. Before you file a bug report, you'll want to make sure you're filing it with the right group. . .
The issue is something with the MBR on my hda. I tried to install grub from redhat after I got stuck on this problem. When I did that I got a useful error message from grub for the first time: Error 5. From the info file it says "this is bad" because some sanity checks failed.
I later managed to chroot. I remembered what I had to do: I had to mount hda2 manually with
mount -t reiserfs /dev/hda knoppix/
instead of just
mount knoppix
Then it works as it should (and I have lilo in my mbr again... but I think I'll backup that drive!!)
The weird thing is that the same problem exists when I boot with a knoppix cd! So I wonder if it is kudzu? I'll take a look in my fstab and I will try different combintations to see precisely when the bug appears.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.