Skip to main content

Grub2 is actually OK...

I think it may still need a bit of work on Fedora's implementation of Grub 2, but it is tolerable.  I still like the manual updates of the older grub.  The thing that had irritated me the most, was probably the simplest to remedy - the boot splash screen, or menu screen.  (spalsh.xpm.gz previously).  The grub 2 implementation removes a lot of the complexity of changing that image also.
You no longer have to:  ensure it's a certain size, has a certain color pallete, has the layers flattened, then run some conversion on the image.  In hindsight - the old method really kind of sucked.

Here is the /etc/default/grub that I am currently using:



#grub2-mkconfig -o /boot/grub2/grub.cfg
#grub2-mkfont --output=/boot/grub2/unicode.pf2 /usr/share/fonts/dejavu/DejaVuSansMono.ttf
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Fedora"
GRUB_DEFAULT=saved
GRUB_CMDLINE_LINUX="rd.lvm.lv=vg_neo/lv_swap rd.md=0 rd.dm=0  KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 rd.lvm.lv=vg_neo/lv_root LANG=en_US.UTF-8"
# Custom stuff 
GRUB_DISABLE_RECOVERY="true"  # Removes the Linux Recovery
GRUB_SAVEDEFAULT="true"             # Should make the system save your last choice
GRUB_GFXMODE=1600x900x16            # Not sure this is necessary
GRUB_GFXPAYLOAD_LINUX=keep  # Not sure this is necessary
GRUB_BACKGROUND=/boot/grub/splash-tree.tga  # This tells grub what image to use for a splash




Then run...

[root@neo default]# sh `head -2 grub | sed 's/\#//g'`


The comment at the top are just there as a reminder for the command you need to run after updating the file.
The comment at the bottom reminds me how to update the chosen font.  My updates follow the comment # Custom stuff
The blue comments are not present in my actual grub file - I added them just for this example.


I put my splash image in /boot as it's still a "standard Linux (type 83)" filesystem.  
Labels:

Comments

Post a Comment

Popular posts from this blog

RHN Satellite Server (spacewalk) repomd.xml not found

"repomd.xml not found" If you add a channel, or if your RHN cache gets corrupted, and one of your guests complains that it cannot find repomd.xml for jb-ews-2-x86_64-server-5-rpm (for example) - you need to rebuild your repodata cache. Normally this is an automated job - which is exemplified by the fact that you have obviously built out your entire Satellite environment and never had to do any of the steps you are about to do. So - some prep work: Open 3 terminals to your Satellite Server and run: # Term 1 cd /var/cache/rhn watch "ls -l | wc -l" # Term 2 pwd cd /var/log/rhn tail -f rhn_taskomatic_daemon.log # Term 3 satellite-sync --channel=jb-ews-2-x86_64-server-5-rpm Once the satellite-sync has completed, you >should< see the count increment by one.  If you are unlucky (like me) you will not. You then need to login to the Satellite WebUI as the satellite admin user. Click on the Admin tab (at the top) Task Schedules (on the left) fin
Post a Comment
Read more

Install RHEL 7 on old HP DL380 g5

Someone at work had been running RHEL on an HP DL380 G5 and blew it up.  After several attempts at doing an installation that made me conclude the hardware was actually bad... I kept digging for the answer. Attempt install and Anaconda could not find any disks - try a Drivers Disk (dd.img) both cciss and hpsa.   -- once we did that, when the system would reboot it would say it could not find a disk. hmmm. Boot from your installation media and interrupt the startup at grub. Add hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1 to the line starting with linuxefi press CTRL-X to boot. Once the system restarts after the install, you need to once again interrupt the startup and add the line from above. After the system starts, edit /etc/default/grub and add those 2 parameters to the end of the line starting with GRUB_CMDLINE_LINUX (which likely has quiet at the end of the line currently). then run # cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.orig # grub2-mkconfig -o /boot/grub2
Post a Comment
Read more

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un
1 comment
Read more