http://zenlive.linuxish.net/people/akun ... ch-plb.tgz
I mainly adapted it for working from Slackware as well as from Zenwalk.
It will now take the Lilo menu of the first partition you choose, if the first partition on your lilo menu is Zenwalk, you will have Zenwalk's Lilo menu, if it is 'our distro', you will get Slackware current's lilo menu.
Thanks for your testing.
New LiloFix
New LiloFix
What really matters is where you are going, not where you come from.
Re: New LiloFix
It seems to work, but...
1. It doesn't respect settings already present in lilo.conf. My append line got replaced and timeout changed. I think it would be better if it tried to take these options from the existing lilo.conf first. vga mode stayed the same, but maybe I'm just lucky and happened to have the save default?
2. Selecting "edit lilofix.conf" from the menu, results to the file being opened with firefox. Maybe a mimetype thing and nothing to do with lilofix?
3. I tried to also add an ubuntu partition, but that would certainly fail, as there is no file named vmlinuz in there. Maybe it would be a good idea to search for vmlinuz* files in the /boot dir of every partition and prompt which one to use if it finds many of them?
4. Your name is missing a "k" in the about dialog and the readme.txt.
5. packageversion should be 1plb, not just plb. So it can be incremented in a package rebuild.
6. Not sure why you're using the prefix variable. It's only used in a single line.
7. Search for the word "fonctional" in the readme.txt
1. It doesn't respect settings already present in lilo.conf. My append line got replaced and timeout changed. I think it would be better if it tried to take these options from the existing lilo.conf first. vga mode stayed the same, but maybe I'm just lucky and happened to have the save default?
2. Selecting "edit lilofix.conf" from the menu, results to the file being opened with firefox. Maybe a mimetype thing and nothing to do with lilofix?
3. I tried to also add an ubuntu partition, but that would certainly fail, as there is no file named vmlinuz in there. Maybe it would be a good idea to search for vmlinuz* files in the /boot dir of every partition and prompt which one to use if it finds many of them?
4. Your name is missing a "k" in the about dialog and the readme.txt.
5. packageversion should be 1plb, not just plb. So it can be incremented in a package rebuild.
6. Not sure why you're using the prefix variable. It's only used in a single line.
7. Search for the word "fonctional" in the readme.txt
Re: New LiloFix
You may want to take a look how the very Debian-oriented grub2 code is doing this. Of course the list of initrds must be extended to support other distros than debian or suse.gapan wrote:3. I tried to also add an ubuntu partition, but that would certainly fail, as there is no file named vmlinuz in there. Maybe it would be a good idea to search for vmlinuz* files in the /boot dir of every partition and prompt which one to use if it finds many of them?
There's also a nice tools called os-prober which comes from debian, but zw has a package for it already. It can be used to find and determine about any OS installed on about any partition:
http://svn.savannah.gnu.org/viewvc/trun ... iew=markup
If your interested in the configuration system of grub2 in full action install grub2 and os-prober, then run "grub-mkdevicemap -n" and "grub-mkconfig":
http://zenwalk.enialis.net/i486/snapsho ... 6-62.1.tlz
http://zenwalk.enialis.net/i486/snapsho ... h-62.1.tgz
Re: New LiloFix
Thanks for this very thorough test + report...
Existing FB vga mode is detected & used, but that depends on what the existing bootloader (grub, lilo or isolinux/syslinux) defined.
From now on, please remove the k (I'm a big boy now...)
It doesn't try to use existing lilo.conf, since it was originally designed to work with zenlive which had no lilo.conf. But this is a good idea & if a lilo.conf exist, it could use some of its settings... or else, have a pop up window ask for the user to define these setttings.gapan wrote:1. It doesn't respect settings already present in lilo.conf. My append line got replaced and timeout changed. I think it would be better if it tried to take these options from the existing lilo.conf first. vga mode stayed the same, but maybe I'm just lucky and happened to have the save default?
Existing FB vga mode is detected & used, but that depends on what the existing bootloader (grub, lilo or isolinux/syslinux) defined.
Since users can have different editors, It uses exo-open which is supposed to use the preferred text editor... But I'll try to find another solution, like creating a small editing window directly with glade & python. That way we are sure it always works.2. Selecting "edit lilofix.conf" from the menu, results to the file being opened with firefox. Maybe a mimetype thing and nothing to do with lilofix?
Yes, multiple kernels in the same partition + Debian/buntus are next on the todo list....3. I tried to also add an ubuntu partition, but that would certainly fail, as there is no file named vmlinuz in there. Maybe it would be a good idea to search for vmlinuz* files in the /boot dir of every partition and prompt which one to use if it finds many of them?
That is actually the correct spelling but when I was a kid I decided to use my own spelling & add my own k & this has plagued me since... I now try to get rid of the k but a part of me fight it & doesn't let me... which is why I now sometimes use either spelling.4. Your name is missing a "k" in the about dialog and the readme.txt.
From now on, please remove the k (I'm a big boy now...)
I know... I know... (thanks )5. packageversion should be 1plb, not just plb. So it can be incremented in a package rebuild.
6. Not sure why you're using the prefix variable. It's only used in a single line.
I corrected the spelling & removed the 'fully' (for now...)7. Search for the word "fonctional" in the readme.txt
What really matters is where you are going, not where you come from.
Re: New LiloFix
Thanks, I'll check these outShador wrote:You may want to take a look how the very Debian-oriented grub2 code is doing this. Of course the list of initrds must be extended to support other distros than debian or suse.
There's also a nice tools called os-prober which comes from debian, but zw has a package for it already. It can be used to find and determine about any OS installed on about any partition:
http://svn.savannah.gnu.org/viewvc/trun ... iew=markup
If your interested in the configuration system of grub2 in full action install grub2 and os-prober, then run "grub-mkdevicemap -n" and "grub-mkconfig":
http://zenwalk.enialis.net/i486/snapsho ... 6-62.1.tlz
http://zenwalk.enialis.net/i486/snapsho ... h-62.1.tgz
What really matters is where you are going, not where you come from.