Monday, May 10, 2010

Deleting the Grub Bootloader

If you had a dual boot system say linux and windows. And you wanted to remove linux so you went into windows and deleted the linux partition over there. Next time you restart your windows you will end up in having an error message saying "Grub Error" may be as shown here.





Here is the fix for it.



Do you have Windows installed already? If so, boot from the CD, enter the recovery console (press R when it asks you whether you want to install windows etc.) When you're at the console, type:

fixmbr

and that will remove GRUB from your system.

If you don't have Windows installed, then do a fresh installation of windows. GRUB will be overwritten as part of the installation.

Reinstalling Grub bootloader in Fedora


When a system is too damaged to permit booting from the hard disk drive, it's necessary to boot from another medium. The Fedora installation discs support a "Rescue mode" in which the system is booted from the CD and the hard disk partitions are optionally mounted for access

To access this mode, boot from your Fedora install media and select "Rescue installed system" from the boot menu using the arrow keys and Enter or by pressing the R key

The kerenel will boot from CD and the system will prompt you to select a keyboard style and language from scrollable lists of options. You will then be given the opportunity to enable the network interfaces on the system, either by entering the IP information or by using DHCP.

The system will then present a dialog stating that the rescue environment is about to find and mount the filesystems from your hard disk Fedora installation, and asks if you wish to continue. This is a critical question: if your filesystems are intact and you wish to access the data that is in them, you can select Continue, the default option. If you are concerned about the state of your filesystems and want to ensure that they will not be altered, but still want to access them, select Read-Only.

you will be redirected to root prompt. run this command from there
chroot /mnt/sysimage
  1. Start the Grub shell with the grub command:

    # grub
    Probing devices to guess BIOS drives. This may take a long time.


    GNU GRUB version 0.97 (640K lower / 3072K upper memory)

    [ Minimal BASH-like line editing is supported. For the first word, TAB
    lists possible command completions. Anywhere else TAB lists the possible
    completions of a device/filename.]
    grub>
  2. Use the find command to locate the partition containing the boot files by searching for /grub/grub.conf (or /boot/grub/grub.conf if that fails). Grub will report the partition using its own syntax:

    grub> find /grub/grub.conf
    (hd0,0)
  3. Use the root command to configure the partition from which the boot files are to be loaded (use the partition ID from step 2):

    grub> root (hd0,0)
  4. The partition ID from step 2 can be converted to a drive ID by removiing the comma and partition number -- for example, the partition (hd0,0) is on the drive (hd0). Use the setup command with this drive ID to install the Grub bootloader code:

    grub> setup (hd0)
  5. Exit the Grub shell with quit:

    grub> quit
    #
You can also use rescue mode to set the root password, create alternate superuser accounts, or change or remove a boot password. Whether these are important recovery operations or a type of attack depends only on the context in which they are performed. You can slow down such an attack by configuring the system BIOS to boot only from the hard disk and installing a BIOS password, but that can be reset using a motherboard jumper in most cases.

The moral of the story: if you don't have physical security, you don't have system security.

When you are finished using rescue mode, type exit or press Ctrl-D twice. The system will then reboot.

Sunday, May 9, 2010

Reinstall Ubuntu Grub Bootloader After Windows Wipes it Out


If you run a dual-boot system with Linux and Windows, this has happened to you. You have done a reinstall of Windows, and now you don’t see the linux bootloader anymore, so you can’t boot into Ubuntu or whatever flavor of linux you prefer.
Here’s the quick and easy way to re-enable Grub.
1) Boot off the LiveCD
2) Open a Terminal and type in the following commands, noting that the first command will put you into the grub “prompt”, and the next 3 commands will be executed there. Also note that hd0,0 implies the first hard drive and the first partition on that drive, which is where you probably installed grub to during installation. If not, then adjust accordingly.
#sudo grub
> root (hd0,0)
> setup (hd0)
> exit
Reboot (removing the livecd), and your boot menu should be back.

How to Upgrade Ubuntu 9.10 (Karmic Koala) to Ubuntu 10.04 (Lucid Lynx)


Important Notes Before Upgrade
  • Take a complete Back up all your data. There is no guarantee that all will go well.
  • Before upgrading it is recommended that you read the release notes for Ubuntu 10.04, which document caveats and workarounds for known issues in this version.
  • Be sure that you have all updates applied to Ubuntu 9.10 before you upgrade
Upgrading from GUI:
To upgrade from Ubuntu 9.10 Start the Update Manager from System---> Administration---> Update Manager.


Update Manager should open up and tell you: New distribution release ‘10.04 LTS’ is available.Here you need to click on Upgrade



This will show you Ubuntu 10.04(Lucid Lynx) Release notes click on upgrade



you will get a prompt for your password, enter your password

Preparing to upgrade in progress



If you are using any third party sources in your /etc/apt/sources.list file it will be disabled at the time of upgrade process click close



Setting new software channels in progress






Starting the upgrade process window click on Start Upgrade



Downloading and Installing Packages in Progress



Installing Packages Progress in Terminal


Now You might see a message for continue without installing grub.you must check the checkbox.

Cleaning Up process in Progress


Remove obsolete packages window click on remove



You need to restart the system to complete the Upgrade by clicking “Restart Now”


Upgrading fromTerminal :
            upgrading from terminal run the following command and respond to the terminal queries.

#>sudo do-realease-upgrade

Fedora 13 Linux Virtualization Relies on KVM

Virtualization technology has long found a home in Red Hat's Fedora community Linux distribution. Ever since Fedora 4 emerged in 2005, virtualization technologies have continued to advance in the distro and that remains the case with the upcoming Fedora 13 release set for later this month.
Unlike Fedora's early virtualization features, which all leveraged the Xen open source technology, more recent Fedora releases have relied on KVM. New KVM performance and scalability features for virtualization will debut in Fedora 13 that will help to push the envelope for large-scale virtualization deployments.
"If you look at Linux virtualization features, Fedora has always been the vanguard for virtualization," Fedora Project Leader Paul Frields told InternetNews. "We were putting out KVM before anyone else and we were interested in KVM as it seemed like a much more upstream-friendly feature. Although Xen was definitely a virtualization focus for a few years, Xen had some drawbacks."
Frields noted that from Fedora's perspective, Xen had become a drain on resources for developers since it took a lot of work to get Xen to work together with the Linux kernel for a Fedora distribution release. He added that, in his view, the code base for Xen didn't track exactly with the upstream Linux kernel and as a result, there was a mismatch."KVM changed all of that because of the fact that it is part of the upstream Linux kernel," Frields said. "It has allowed us to focus our resources to devote more time in advancing the usability of virtualization."Among the new KVM features that will debut in Fedora 13 are KVM Stable PCI Addresses and Virt Shared Network Interface technologies. Having stable PCI addresses will enable virtual guests to retain PCI addresses' space on a host machine. The shared network interface technology enables virtual machines to use the same physical network interface cards (NICs) as the underlying operating system.
Frields explained that those two new features will make it easier for administrators to automate their work.
"If you're trying to automate the creation of machines and the way that they share particular bus connections on a host machine, you want to be able to definitely connect it to a particular bus," Frields said. "When you can predict that, you can take advantage of a greater scale of automation." Another new virtualization feature debuting in Fedora 13 is the ^7Frields8^, which is about delivering improved performance. The ^9Frields10^ technology is intended to lower the CPU requirement for Advanced Programmable Interrupt Controller access, or APIC (define), which is used for program timers.
While Fedora is including the new advanced features for scaling virtualization, Frields doesn't necessarily expect that Fedora will be the platform used for large-scale deployments.
"Fedora is a way for people to have a bit of a crystal ball where they can look into the future of Red Hat Enterprise Linux," Frields said.
Red Hat recently released the first beta for Red Hat Enterprise Linux 6 (RHEL 6). As is the case in Fedora, RHEL 6 no longer includes Xen, but instead leverages KVM as the key virtualization technology for Linux. Features that first debuted in Fedora releases are now finding a home in RHEL 6.
"When people look at RHEL 6, they will be seeing the very recent past and present of Fedora," Frields said. "The RHEL roadmap is always oriented towards long-term stability while Fedora will move on and forge new paths and will help define Red Hat Enterprise Linux 7 at some point in the future."

Google Chrome Automatically Installs Google Repository in Linux

This is something that is new. I was trying to install Google Chrome in Ubuntu and in the download page a small note came into my notice. It goes something like this "Installing Google Chrome will add the Google repository so your system will automatically keep Google Chrome up to date".



  • Now, no need to add repository separately to get the latest updates? I always used Mozilla Firefox Browser, a Google Chrome derivative.After installing Google Chrome from deb in Ubuntu, I went on to check my sources.list and this was what I found. 
  • Its the same for other linux distributions such as Open Suse, Fedora too.

Saturday, May 8, 2010

RHEL 3 & CentOS 3 ends


Red Hat Logo Red Hat has published a reminder that version 3 of Red Hat Enterprise Linux (RHEL) reaches its end-of-life (EOL) date on the 31st of October, 2010. The six-month advanced notification is issued in accordance with the the company's Errata Support Policy and means that, after the 31st of October, no further updates, including security updates and critical fixes, will be available for Red Hat Enterprise Linux 3. The EOL date will also affect CentOS 3, which is based on the RHEL 3 source.
The company advises all users to upgrade to a later release. Under the standard 7 year life-cycle, RHEL 5, for example, will be supported until March of 2014. The next version, Red Hat Enterprise Linux 6, is currently in development and is available as a pre-release beta. The latest stable release is version 5.5 from the end of March.

Advertisement