Projects and resources (En) > Contributing to FOSS

grub-customizer for Debian

<< < (3/3)

patrick013:
@DJ

Question for the evening.    Why do some menu entries
end up in the trash ?

For example,   I added a new kernel to Bonsai, the menu entry
does not show up in grub.cfg after running update-grub.    When
I go into your program I see the menu entry in trash and I can
restore it from there.     Then I see it in the grub2 menu at boot and
it boots.   

Is there a limit on menu entries, I can't see why it wouldn't be updated
or would end up in trash.    It's just as good as any other menu entry,  boots
and everything.

THX

Patrick

djohnston:

--- Citation de: patrick013 le 09 juillet 2013 à 05:05:17 ---Question for the evening. Why do some menu entries end up in the trash ?
--- Fin de citation ---

That's a good question, Patrick, for which I have no answer. I didn't write the C code for this program. I just packaged it as a .deb. The man who wrote the code still develops it, as far as I know, and I'll see what I can find out. I packaged this for Debian because the developer only makes it available as an Ubuntu ppa package. But, he does provide the source code, which makes compiling it fairly easy.

Thanks for testing this. Please post anything else you find wrong with it. I haven't tried different fonts yet, so I don't know what can be done there, either.

EDIT: I should also add that Daniel, the author, campaigned for a Debian sponsor as far back as March of 2011. Evidently, nothing ever became of it.

patrick013:

--- Citation de: djohnston le 09 juillet 2013 à 23:22:49 ---That's a good question, Patrick, for which I have no answer. I didn't write the C code for this program. I just packaged it as a .deb.

--- Fin de citation ---

I see.    Well it appears that all new menu entries are put into
trash by design of the proxy scripts.    When taken out of
trash they become regular entries.    This it appears is a normal
operation of grub-customizer and it's proxy scripts.    Fine
with me I just couldn't fathom why my new grub2 menu entries
were put in "trash" at first waiting for me to confirm they should
be taken out.

I've activated the console option so I'm always making text menus.
Seems the font size and width is better on my netbook.

Otherwise, no bugs, just good old grub being good old grub.

Thanks for the response.

Patrick

djohnston:

--- Citation de: patrick013 le 09 juillet 2013 à 05:05:17 ---@DJ

Question for the evening. Why do some menu entries end up in the trash?

For example, I added a new kernel to Bonsai, the menu entry does not show up in grub.cfg after running update-grub. When I go into your program I see the menu entry in trash and I can restore it from there. Then I see it in the grub2 menu at boot and it boots.
--- Fin de citation ---

Patrick,

In order to try to duplicate this, can you tell me:

(a) Which Bonsai iso did you install from?
(b) What kernels do you have installed?

I just reinstalled the DebLXDE respin, updated it, then added the liquorix kernel. After rebooting, both kernels showed in the boot menu, with the newer one selected as default. When I ran the grub-customizer, both kernels were showing and none had been moved to the trash.

Also, after reinstalling the DebLXDE respin, I had to do:

# rm /lib/live/mount/medium/live/filesystem.squashfs
# rm -rf /lib/live/mount/rootfs/filesystem.squashfs

As you pointed out quite some time ago, the remastersys live-installer is not cleaning up all the files after an installation. I'm going to look into what needs to be done there. Should be a simple fix.

patrick013:

--- Citation de: djohnston le 10 juillet 2013 à 11:05:51 ---In order to try to duplicate this, can you tell me:

(a) Which Bonsai iso did you install from?
(b) What kernels do you have installed?


--- Fin de citation ---


--- Code: ---[sdc1            ] [xfs        ] [WHEEZY-3         ] [    10.15 GB] [  8] [ 33]
[sdc2            ] [swap       ] [swap             ] [   909.93 MB] [  8] [ 34]
[sdc3            ] [ext4       ] [OPENBOX1         ] [    10.15 GB] [  8] [ 35]
[sdc5            ] [ext4       ] [BONSAI           ] [    10.15 GB] [  8] [ 37]
[sdc6            ] [xfs        ] [OB-FULL          ] [    10.15 GB] [  8] [ 38]
[sdc7            ] [ext4       ] [LXDE-MINI        ] [    10.04 GB] [  8] [ 39]
[sdc8            ] [xfs        ] [KDE-MINI         ] [    10.04 GB] [  8] [ 40]
[sdc9            ] [ext4       ] [SCORPIO-2        ] [    10.04 GB] [  8] [ 41]
[sdc10           ] [ext4       ] [<unknown>        ] [    10.04 GB] [  8] [ 42]
[sdc11           ] [ext4       ] [<unknown>        ] [    10.04 GB] [  8] [ 43]
[sdc12           ] [ext4       ] [<unknown>        ] [    10.04 GB] [  8] [ 44]
[sdc13           ] [ext4       ] [<unknown>        ] [    10.09 GB] [  8] [ 45]

--- Fin du code ---

The above is an external hard drive.    After installing grub-customizer
to sdc1 I added a 3.4.52 kernel to Bonsai and a 3.2.46 to LXDE-MINI.
Both menu entries ended up in the trash.   The other kernels are 3.2.18
and these are PCL iso's fully updated.     Otherwise grub-customizer
is working fine like update-grub should.

About DebLXDE:   I couldn't install from the iso, the install would boot
but wouldn't startx automatically or from the console.   Can't remember
what it said but it couldn't find it to start startx.    Perhaps your 2 commands
are what it needs.     My last Scorpio ISO I made installed fine but the
darn ISO was over 1 GB.    Probably just use fsarchiver archives in the
future and just change UUID's on a new install.   The smaller remastersys
iso's are just fine though, sizewise and speedwise.

FYI

thanks for the response.

Patrick

Navigation

[0] Index des messages

[*] Page précédente

Utiliser la version classique