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

How to enable proxy service security in ESB 4.9.0?

Security is one of the major concern when we developing API base integrations or application developments. WSO2 supports WS Security , WS-Policy and WS-Security Policy specifications. These specifications define a behavior model for web services. Proxy service security requirements are different from each others. WSO2 ESB providing pre-define commonly used twenty security scenarios to choose based on the security requirements. This functionality is provided by the security management feature which is bundled by default in service management feature in ESB. This configuration can be done via the web console until ESB 4.8.1 release, but this has been removed from the ESB 4.9.0. Even though this feature isn't provided by the ESB web console itself same functionality can be achieved by the new WSO2 Dev Studio . WSO2 always motivate to use dev studio to prepare required artifacts to the ESB rather than the web console. Better way to explain this scenario is by example. Following

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 Location Keep-Alive Content-Length Content-Type Date Server User-Agent Host Nhttp transport – support headers Server User-Agent Date 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

How to monitor the Thread CPU usage in the WSO2 Products?

1. Download JConsole topthreads Plugin. 2. Add following entries to the PRODUCT_HOME/bin/wso2server.sh -Dcom.sun.management.jmxremote \ -Dcom.sun.management.jmxremote.port=PORT \ -Dcom.sun.management.jmxremote.ssl=false \ -Dcom.sun.management.jmxremote.authenticate=false \ -Djava.rmi.server.hostname=IP_ADDRESS \ Define your IP_ADDRESS address and PORT (port should be not used anywhere in that instance) 3. Run the JConsole using following command. jconsole -pluginpath PATH_TO_JAR/topthreads-1.1.jar 4. Copy "JMXServerManager JMX Service URL" from the wso2carbon logs after restart the Wso2 Server (Eg:- service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi) to the Remote process with the username and password. 5. Under Top Threads tab you can monitor the thread CPU usage.

PRABATH'S TECH BLOG

Search This Blog