Skip to main content

How to change Grub menu background image

Grub is a Linux boot manager that is used to switch between two or more operating systems installed on your machines. By default, Grub's background is plain black with white text. In this article, we will change Grub's default background to any image of your choice.


1 Create the background image


Using your favorite image editing software, create a logo or an image that will look good even with very few colors. Save your image as a PNG with only 14 colors and resize it to 640x480 pixels.


2 Convert the PNG to XPM

If you use GimpShop or The GIMP, you can directly save your image as XPM. But for Photoshop users, you'll have to use ImageMagick's convert utility to convert your image to the format that GRUB uses (make sure the you have ImageMagick installed). To start converting, open your terminal and issue the following command:

$ convert splash.png -resize 640x480 -colors 14 splash.xpm


3 Compress the image file


Now that we have our image ready, we will need to compress it to make it suitable for GRUB and copy it to GRUB's directory.

$ gzip splash.xpm
$ su -
(Type your root password)
# cp splash.xpm.gz /boot/grub/



4 Configure GRUB to use the new image


All we need to do now is to configure GRUB to use the image that we created. To edit GRUB's configuration, issue the command:

$ vi /boot/grub/menu.lst

Add the following line at the beginning of the configuration file (if it doesn't exists):

splashimage=(hd0,0)/boot/grub/splash.xpm.gz


Change (hd0,0) to the partition where GRUB resides then save the changes you've made and restart your machine. GRUB should use your image now.

Comments

Popular posts from this blog

Java Source Code to Change Local IP Address

Hi guys..

Try This code to change your Local IP address.


import java.io.IOException;
import java.lang.Runtime;
public class Chang_Ip {



public static void main(String args[]) throws IOException
{

String str1="192.168.0.201";
String str2="255.255.255.0";
String[] command1 = { "netsh", "interface", "ip", "set", "address",
"name=", "Local Area Connection" ,"source=static", "addr=",str1,
"mask=", str2};
Process pp = java.lang.Runtime.getRuntime().exec(command1);

}


}

How to preserving HTTP headers in WSO2 ESB 4.9.0 ?

Preserving HTTP headers are important when executing backend services via applications/middleware. This is because most of the time certain important headers are removed or modified by the applications/middleware which run the communication. The previous version of our WSO2 ESB, version 4.8.1, only supported “server” and “user agent” header fields to preserve with, but with the new ESB 4.9.0, we’ve introduced a new new property (http.headers.preserve) for the passthru (repository/conf/passthru-http.properties) and Nhttp(repository/conf/nhttp.properties) transporters to preserve more HTTP headers.
Passthru transporter – support header fields LocationKeep-AliveContent-LengthContent-TypeDateServerUser-AgentHostNhttp transport – support headersServerUser-AgentDate
You can specify header fields which should be preserved in a comma-separated list, as shown below. http.headers.preserve = Location, Date, Server Note that properties(http.user.agent.preserve, http.server.preserve), which were used …

How Schedule failover message processor helps for the guaranteed delivery ?

Before we talk about the failover message forwarding processor, it’s better to understand the big picture of the concepts and use cases. The Scheduled Failover Message Forwarding Processor is part of the bigger picture of themessage store and message processor.

Message Store Message Processor. WSO2 ESB’s Message-stores and Message-processorsare used to store incoming messages and then deliver them to a particular backend with added Quality of Services (QoS), such as throttling and guaranteed delivery. The basic advantage of the MSMP is that it allows you to send messages reliably to a backend service. These messages can be stored in a different reliable storage such as JMS, JDBC message stores. The MSMP powered by three basic components:



1. Store Mediator.
The Store mediator is the synapse mediator and can be used to store messages in the message store.

2. Message Store.
A message store is storage in the ESB for messages. The WSO2 ESB comes with four types of message store implementations …