Re: Choosing kernel automatically at Boot - Beginner -

From: Ben Steeves (ben.steeves_at_gmail.com)
Date: 10/25/04

  • Next message: W. Guy Thomas: "Re: adding sessions to gdm"
    Date: Sun, 24 Oct 2004 19:41:36 -0300
    To: For users of Fedora Core releases <fedora-list@redhat.com>
    
    

    On Sun, 24 Oct 2004 15:32:09 -0700 (PDT), joshua neff
    <joshua_neff@yahoo.com> wrote:
    > I open the terminal, logged in as root, typed "chmod
    > +w /etc/grub.conf" and it still gives me a permission
    > denied message.

    I'm guessing that's 'cos you typed "/etc/grub.conf" at the command
    prompt -- which means to the shell you were trying to execute
    grub.conf. Grub.conf is not executable (check the permission bits on
    the underlying actual file (/boot/grub/grub.conf) and you'll find it's
    only readable and writable by the owner (root).

    > I did open grub.conf with vi, though.
    > "Default=1" Before I go ahead and change anything, I
    > want to be absolutely sure I'm doing the right thing.
    > If I set the default to 0, will it boot with kernel
    > 2.6.8 by default (instead of 2.6.5 being the default)?
    > Or do I need to set the default to something else to
    > get 2.6.8 to be the default kernel?

    Using vi (or some other editor) is what the initial respondant
    expected you to do.

    Default=x , where x is the number of the clause to choose
    automatically after the value of seconds in "timeout" has expired.
    The clauses are counted from 0. So, if the first clause (denoted by
    the initial keyword "title", the only non-indented line) is the one
    with the newest kernel, that is the one you want.

    After you successfully boot with the new kernel, you can remove the
    old kernels with an "rpm -e kernel-{version}" -- and grub.conf will
    automatically get cleaned up for you.

    -- 
    Ben Steeves                     _                    bcs@metacon.ca
     The ASCII ribbon campaign     ( )            ben.steeves@gmail.com
       against HTML e-mail          X                GPG ID: 0xB3EBF1D9
    http://www.metacon.ca/bcs      / \     Yahoo Messenger: ben_steeves
    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: W. Guy Thomas: "Re: adding sessions to gdm"

    Relevant Pages

    • Re: Etch on USB-HD wont boot - race condition?
      ... notebook but the kernel cannot find the root filesystem. ... I had an initial problem that I think I got solved: On boot, ... Begin: Mounting root file system... ... SCSI device sda: 78140159 512-byte hdwr sectors ...
      (Debian-User)
    • Re: Flaws in recent Linux kernels
      ... Many distributions include other programs which may be ... suitable for exploiting the kernel vulnerability. ... possible to install third-party SUID root programs which may be used. ... A new revision of the Openwall Linux kernel patch, 2.2.19-ow3, is now ...
      (Bugtraq)
    • Re: [PATCH] System Wide Capability Bounding Set
      ... root, you can do anything you want to a machine. ... the threat model becomes how do we prevent one guest from attacking another? ... Which root filesystem do kernel helpers run in in such a setup? ... They need to be able to run arbitrary code in ring 0 of the VM. ...
      (Linux-Kernel)
    • Re: Beige PowerMac G3/266 trouble
      ... I downloaded the minimal "netinst" install CD image from ... The kernel initially seemed to load OK, and told me that it had found the ... At this point it threw up an error saying it couldn't open the root device ... request_module: runaway loop modprobe binfmt-0000 ...
      (comp.os.linux.powerpc)
    • Re: 2.6.9-rc2-mm1
      ... Fails to boot on my Altix. ... diff between 2.6.9-rc1-mm4 and 2.6.9-rc2 indicates some kind of PCI, ... Mounted root readonly. ... -doneshowconsole: Warning: the ioctl TIOCGDEV is not known by the kernel ...
      (Linux-Kernel)