DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Also, nx5000 I tried the method that you suggeted but it did not work.The program that I installed still went ahead and made changes to the menu.lst
Which program? I hope not that crappy splashy? It wrecks your menu.lst very easily. After two years of using a debian its in my top 5 worst package I have seen.
This kernel-img.conf only works for new kernel-image installation, I was maybe not clear.
Which program? I hope not that crappy splashy? It wrecks your menu.lst very easily. After two years of using a debian its in my top 5 worst package I have seen.
This kernel-img.conf only works for new kernel-image installation, I was maybe not clear.
Yes you are right. I was talking about splashy. Your guess is right. Just out of curiosity, can you tell me why splashy is bad?
When I tried it, it had overriden my kopt values in menu.lst as if it did not use update-grub but its own mechanism. I then copied back a backup of this file. But what really annoyed me is that it left the /etc/init.d/splashyxx after uninstalling it. So I deleted them. I'm a bit fussy but it never happens in general with debian.
But that's my own opinion and maybe now it is corrected.
The positive thing is that it is in user space while bootsplash is in kernel space and I'm not sure its a good thing to have a bootsplash in kernel space (the only advantage of this is that it can run earlier)
When I tried it, it had overriden my kopt values in menu.lst as if it did not use update-grub but its own mechanism. I then copied back a backup of this file. But what really annoyed me is that it left the /etc/init.d/splashyxx after uninstalling it. So I deleted them. I'm a bit fussy but it never happens in general with debian.
But that's my own opinion and maybe now it is corrected.
The positive thing is that it is in user space while bootsplash is in kernel space and I'm not sure its a good thing to have a bootsplash in kernel space (the only advantage of this is that it can run earlier)
Interesting views. It is always good to share views and ideas. Well I am not sure which version of splashy you used, but I am running this version splashy_0.1.5.svn28_i386.deb and it runs pretty good except updating the menu.lst file(which is now corrected by using the kopt technique, thanks to bobbens).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.