I read: http://www.tldp.org/LDP/LG/current/jayanth.html and it says to put my 14-color 640x480 image as /boot/grub/splash.xpm.gz. But weird thing is: my /boot/grub contains no splash.xpm.gz (even with hidden files being displayed). I'm using SUSE 10.0 RC1. So where do I put this splash file I create? The following line exists in my /boot/grub/menu.lst file: gfxmenu (hd0,6)/boot/message and I see the file /boot/message which is a CPIO archive at 155.5 KB. Looks like this is it. I use cpio -idv < message on this file (after copying it to /home/myname/testing) and I find a list of files, each of which apparently provides a different component of the GRUB menu. Now what do I do? I want to replace the existing background with one of my own. Thanks.
Shriramana Sharma a écrit :
I read:
http://www.tldp.org/LDP/LG/current/jayanth.html
and it says to put my 14-color 640x480 image as /boot/grub/splash.xpm.gz.
But weird thing is: my /boot/grub contains no splash.xpm.gz (even with hidden files being displayed). I'm using SUSE 10.0 RC1. So where do I put this splash file I create?
The following line exists in my /boot/grub/menu.lst file:
gfxmenu (hd0,6)/boot/message
and I see the file /boot/message which is a CPIO archive at 155.5 KB. Looks like this is it. I use
cpio -idv < message
on this file (after copying it to /home/myname/testing) and I find a list of files, each of which apparently provides a different component of the GRUB menu.
Now what do I do? I want to replace the existing background with one of my own.
Thanks.
Hello, Once you've run : cpio -idv < message the content of the cpio archive has been extracted and the file named "back.jpg" is your background image. Change it with the picture of your choice but with the same resolution ! for instance as I don't like the SuSE green, I made it blue. Then run : ls | cpio -ov > ../message and that's all. Take care not to write the file in the same folder. Michel
Tuesday 04 Oct 2005 15:36 samaye Catimimi alekhiit:
the content of the cpio archive has been extracted and the file named "back.jpg"
Thanks, Catamimi! I'll try that. But I note that the file back.jpg is a true colour 24-bit image, and so it is not necessary to decompose it into 14 colours. I'm gonna try my new image new. The size is 800x601. Is there anything special about the extra row? SS.
Shriramana Sharma a écrit :
Tuesday 04 Oct 2005 15:36 samaye Catimimi alekhiit:
ls | cpio -ov > ../message
Yay thanks! That worked.
and that's all. Take care not to write the file in the same folder.
May I know why not in the same folder?
I think that it is not recommended to write in the folder which you are compressing, since you would compress the new file too !!!
Tuesday 04 Oct 2005 20:44 samaye Catimimi alekhiit:
I think that it is not recommended to write in the folder which you are compressing, since you would compress the new file too !!!
This is crazy! If I understand the command ls | cpio -ov > ../message right, you are giving the output of ls as input for cpio, which is to output to the file specified after >. Well first ls is executed, at which time the new CPIO archive is not yet created, and then cpio is executed with what ls provided it, which does not include the not-yet-created CPIO archive, and after that the CPIO archive is created. How is there a possibility of infinite looping here?
Shriramana, On Tuesday 04 October 2005 18:02, Shriramana Sharma wrote:
Tuesday 04 Oct 2005 20:44 samaye Catimimi alekhiit:
I think that it is not recommended to write in the folder which you are compressing, since you would compress the new file too !!!
This is crazy! If I understand the command
ls | cpio -ov > ../message
right, you are giving the output of ls as input for cpio, which is to output to the file specified after >. Well first ls is executed, at which time the new CPIO archive is not yet created, and then cpio is executed with what ls provided it, which does not include the not-yet-created CPIO archive, and after that the CPIO archive is created.
More or less. First of all, the processes in a pipeline all execute concurrently. The Unix (OK, Linux) kernel's pipe mechanism interacts with the process schedulers to interleave their execution so the amount of data queued in the pipe is bounded (and almost never has to be written to disk). Because of this, it is impossible to say with certainty whether the output file will exist when "ls" executes and hence whether it's included in its output. That's why the output is sent to a different directory, eliminating the possibility that "cpio" will try to include its output in itself.
How is there a possibility of infinite looping here?
No, but only because the output file is place up one level in the file system hierarchy. If for some reason the cpio output had to be in the same directory as the files to be placed in the archive, then the list of files would have to be created first: % ls >/tmp/cpio-files % cpio </tmp/cpio-files >cpio-output But even this is not safe, since simply executing the above two commands twice in a row will guarantee that cpio will try to include one of its inputs in its output. Randall Schulz
I have created the SUSEWiki article: http://susewiki.org/index.php?title=Change_GRUB_background I hope it is useful to others too. I got more command line experience along the way of writing this article. Please check the article for any errors and contribute by corrections, additions, whatever. If you do any such thing, please inform me too so I can learn. Shriramana Sharma.
Monday 10 Oct 2005 22:07 samaye Shriramana Sharma alekhiit:
Can anyone please help in adding this page to: http://susewiki.org/index.php?title=Category:Howto&action=edit Somehow I get only the following text as available for editing: "Articles describing the steps to accomplish a task." I don't see the list at all. Using Konqueror of SUSE 10 Gold. Shriramana.
participants (3)
-
Catimimi
-
Randall R Schulz
-
Shriramana Sharma