#8 problems with LILO install from chrooted HD root partition

closed
nobody
None
5
2015-03-04
2006-01-17
rudy
No

LILO messed with "Unable to write /dev/hda. Permission
denied" in chrooted root environment from existing
partition.
Steps to reproduce:
1. Boot INSERT with cheatcodes: toram 2
2. Mount local HD partition with existing linux root, ex.:
mount /dev/hda2 /mnt/hda2
3. Chroot to local hd partition, ex.:
chroot /mnt/hda2
(su -; chroot /mnt/hda2 gives the same result)
4. Run lilo (use proper lilo.conf working when boot
from this local partition)
lilo -b /dev/hda

I've noticed also that lilo -r /mnt/hda2 without chroot
messed with "Unable stat Unnamed device 0x000E" or
whatever (forgot to write down on the paper, sorry). Is
this a bug or feature? How is it related to lvm or
toram cheatcode?

Discussion

  • Matthias Mikuletz

    Logged In: YES
    user_id=335973

    Puh, I'm sorry but I just don't seem to find the time to try
    and reproduce....

    Did you try without 'toram'?
    Did you mount as root?

    Maybe lilo cannot cope with your harddisk setup...?

    Regards
    Matthias

     
  • rudy

    rudy - 2006-04-21

    Logged In: YES
    user_id=1411685

    > Did you try without 'toram'?
    Yes. The same result.

    > Did you mount as root?
    Yes.

    > Maybe lilo cannot cope with your harddisk setup...?
    No. It works fine from Slackware 10.0 rescue disk. Tried
    several computers with Slackware 10.2 and ALTLinux Sysiphus
    installed.

     
  • Matthias Mikuletz

    • status: open --> closed
     
  • Matthias Mikuletz

    Logged In: YES
    user_id=335973

    I'm not sure.

    I cannot test with a different system now, but I would think
    that
    if you're chrooted to a partition, you don't have root
    access outside -
    and the physical device is outside, isn't it?

    Regards
    Matthias

     

Log in to post a comment.