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

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...

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 ...

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 ...