Skip to main content

Fedora 16, Gnome 3, Grub2

Within hours of receiving my new Lenovo T520 I had ripped the restore media and removed the 500gig drive to keep in case of an apocalypse, or something. With a new 750gig drive installed I executed the Lenovo restore to the new drive (installing Windows 7). Post-restore I had to remove the restore partition and resize the Windows partition. I shrunk it to leave 250Gig dedicated to Windows, leaving around 500Gig for Linux.

Initially I found many things about the new Fedora release unsettling. I didn't care for the Gnome 3 interface. As I went to attempt to customize my Grub I became more irritated. I still have a number of things to become comfortable with again, but within days I am digging the Gnome 3 interface (although I think a lot of work still needs to be done, I think I understand why it has went through significant changes and I believe those are good changes), Fedora 16 has some fundamental changes - and like Gnome, there is still some work to be done, but I believe they are taking things in a better direction. As for Grub2. I don't get it. I don't understand it, whatsoever. As far as I can deduce, the Grub fundamentally is quite similar to it's predecessor (if not identical), but what they have done baffles me. They have introduced so many layers of complexity to manage/customize Grub. Previously, you could manually update the "main config file" and you were moving forward. I'm currently stuck trying to do 2 very simple things: update the grub splash image (shown at the boot menu), remove the Windows "System" Partition from the list of bootable environments. I have ranted about this in another post... So, I'll move on.

I like the look-and-feel and I am optimistically awaiting future updates to add functionality and customization options to the desktop. Gnome 3 seems to have become completely extensible. Now you search for functionality you want and add the extension. Good stuff.

I'll need to further research how Linux appears to be going the way of Solaris and the SMF implementation. /etc/inittab is there, but appears to have been completely deprecated. chkconfig still existis and I'm sure you can manage your services that way.

KVM - I had installed VMware Workstation 8 (which was not seamless either) and I got to thinking that I should jump head-first into this and use KVM. So far the verdict is out. KVM has come a long ways, but it simply just does not have the polish that VMware does. I believe it will work, but there will be limitations and I will seemingly take a performance hit. I anticipate rethinking this and I will decide to use/test KVM elsewhere. :-(

Update: I was able to install a Windows 7 VM in Fedora using a OA DVD.  I was then able to validate the Windows Installation using the key on the case decal.

Comments

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

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

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