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

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

Extending SNMP to run arbitrary shell script

Why are we here... This is not likely something I would have pursued under normal circumstances.  I happen to be working for a customer/client who is not afforded a lot of flexibility to accomplish their goals.  In this case, the rigor is justified.  They have to sometimes be fairly creative with how they solve problems. In this case they would like to utilize an existing snmp implementation to execute a command (or shell script) on a remote system.  They came to me with the idea of using Net-SNMP extend. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html NOTE:  This is NOT a good implementation strategy in the "real world"  it will simply allow you to test the functionality.  There are a TON of security implications which would need to be taken in to consideration. Implementation Steps: [root@rh7tst01 ~]# yum -y install net-snmp net-snmp-utils ...
Post a Comment
Read more