On Fri, Oct 03, 2003 at 07:41:21PM +0100, Yoshinori Okuji wrote: > > But I'm not sure what is the right way to fix this problem. One way is to add a > resolver of symlinks in a device map into grub-install. It wouldn't be very > difficult. > > Another idea is to have the grub shell to do all the mappings between a BIOS > drive and an OS device. This might be better, because it is not very good to > have separate code to deal with a device map in grub-install and in the grub > shell.
If I understood correctly, the GRUB shell relies on device.map to translate BIOS devices into kernel device files, and uses standard Un*x calls on /dev to access the devices. Is that it? IIRC, the kernel (at least, when that kernel is Linux) forwards read/write calls to the target when the file is a symlink, but the same doesn't apply to ioctl, so programs that rely on ioctl must be capable of resolving symlinks. I believe a good solution could be to fix kernels to forward requests on ioctl too, if that fixes the problem. Is all this correct or did I miss something? -- Robert Millan "[..] but the delight and pride of Aule is in the deed of making, and in the thing made, and neither in possession nor in his own mastery; wherefore he gives and hoards not, and is free from care, passing ever on to some new work." -- J.R.R.T, Ainulindale (Silmarillion) _______________________________________________ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub
