Icarus,
Thanks for the pointer. Other references aalso mention mknod too but I am nervrous as I lack the background knowledge of how Linux controsl the devices.
Nevertheless I can report that I am booting the same Linux by "LIlo" first time. That means I have found a temporary solution.
I came across the command mount --bind and tried it out as follow.
(1) Boot to another Linux A that has /dev that has a device name for the Linux B I want to boot (which is hda61). In other word /dev of Linux A has maximum hda63 but Linux B stops at hda24. I do have partitions up hda63 detected fully by Linux A.
(2) I then in Linux A dowhich I believe the full list of /dev of Linux A is now available to Linux BCode:mount --bind /dev /mnt/hda61/dev
(3) I then change root to Linux B and restore LiloThe scheme seems to work satisfactorily. No alteration is done in the /dev of Linux B. Lilo still can't be restored once the Linux B is booted up with the same error as reported in Post #1 before. However as LIlo fails and so it keeps the last working version and so I can continue to boot B.Code:chroot /mnt/hda61 lilo -b /dev/hda61 exit
Although this is not a permanent solution still I am glad that I can understand the root cause ( I think) and have a cure for it, at least temporarily.




Reply With Quote