I have your preboot hooks patch incorporated into grub-r2106 along with
a suitably updated version of drivemap, which remains flawlessly working
with 2nd-harddisk Windows XP boots (grub being installed on the 1st
harddisk along with Linux). Had to make a few minor changes to the
preboot hooks patch to get it to build in r2106.
I have also incorporated your mmap services patch as well (again with
minor mods to build in r2106). My question at this point, is how best to
incorporate mmap services into drivemap. I see that in
mmap/i386/pc/mmap.c there is some sort of support for int12 and int15
services. Should I incorporate the drivemap int13 handler here ? Looks
relatively straightforward -- just insert the asm handler into
mmap/i386/pc/mmap_helper.S and update mmap/i386/pc/mmap.c -- (except for
how I place the mapped drives table), or, should I use the mmap.c code
as a template for the drivemap int13 handler plus mapped drives table ?
thanks for any help/suggestions,
John
phcoder wrote:
I haven't yet looked in depth in drivemap patch but it has some
problems. It uses preboot hook interface for which I proposed an
update in my recent patch "preboot hooks". Also it doesn't update
memorymap correctly. For this it should use my "mmap services" interface
John Stanley wrote:
Thanks Felix,
Hurm.. Well, if anyone is interested, I have just made a couple of
additional updates to the drivemap.path.8 code,
and now with r2104 the "unaligned pointer" issue is gone, and it is
working great on my systems. I can post the patch if you or anyone
else is interested.
John
Felix Zielcke wrote:
Am Montag, den 13.04.2009, 21:03 -0400 schrieb John Stanley:
Hi all,
I was wondering what the current status of a grub2 port of the
grub-0.97 "map" and "rootnoverify" commands is? I have found some
work done to this end in the "drivemap.patch" work, but I find
nothing more recent than drivemap.patch.8 dated around Aug 2008.
The current status of it are exactly what you found out.
I don't know if that'll ever change.
Could anyone give me any pointers/direction on what might be
happening here? Could it be that the "norootverify"-functionality
of grub-legasy is lacking here? Or, perhaps, that the "--force"
option is not being honored ?
rootnoverify isn't needed anymore, because root is now just a variable
and not anymore a command which tried to verify it. So basically
rootnoverify is default now.
chainloader --force just skips the check for 0xaa55, normally it
shouldn't be needed with a valid windows bootsector.
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
