Just a small update on developments with this. I finally got some time this weekend to start to bang this out. Once I thought I had it..to my surprise commands like "grub-install" are actually shell scripts (partially generated from .in files..oh autoconf generated scripts..how nice). And they specifically look for commands like "grub-setup". So I'm going to be taking a little more time add patches to the spec files so that everything can ex. "grub2-install" or "grub2-setup" and work harmoniously. So just to let everyone know I'm still working on it :-) . Hope to have a spec and patches out by end of tuesday. On 1/22/07, Jerone Young <jerone@xxxxxxxxx> wrote:
This shouldn't be too big of a deal using the grub2 name. Down the road you can just make a symlink to grub2 that is named grub. Currently I think there just needs to be a migration path to grub2. Hopefully if it can go into FC 7 it can begin the migration. On 1/22/07, Bruno Wolff III <bruno@xxxxxxxx> wrote: > On Mon, Jan 22, 2007 at 12:38:47 -0600, > Jerone Young <jerone@xxxxxxxxx> wrote: > > I can take up this task. I'll put something together this week. Though > > it will be interesting to figure out a way so it does not conflict > > with current grub. This would be a good way to figure out how to get > > them to exist side by side. > > I would think that using something like /boot/grub2 instead of /boot/grub > for config files and naming the executable /sbin/grub2 instead of > /sbin/grub would work OK. Once you do a set up with one of the grubs, > that one will be used for booting, and there isn't a lot you can do about > that. > > The disadvantage of doing this is that down the road you will probably > want to rename grub2 as grub and there will be some pain realted to that. >
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list