public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Cox <yeahsowhat@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Kernel build no update grub
Date: Thu, 17 Nov 2005 01:50:45 -0600	[thread overview]
Message-ID: <200511170150.46082.yeahsowhat@gmail.com> (raw)
In-Reply-To: <874q6b52bu.fsf@newsguy.com>

On Wednesday 16 November 2005 22:24, Harry Putnam wrote:
> Harry Putnam <reader@newsguy.com> writes:
> > Updating the kernel today, I referenced that piece of the
> > documentation and borrowed this command from it:
> >
> >  genkernel --bootloader=grub all
> >
> > However, not only did it not update grub.conf but grub.conf
> > disappeared entirely following the successful build.
>
> Let me tell this story again briefly... This was quite a knuckleheaded
> move on my part.  Its been so long since I updated my kernel, I forgot
> that I switched to lilo some mnths ago....  So, er I misinfomed the
> genkernel tool.
>
> I'm not sure that should have made any difference in what it did to
> grub.conf or not..

It doesn't make any difference trust me.  I tried genkernel a few months ago 
with the --bootloader=grub option and it it removed everything in my 
grub.conf as well ; the file was 0 bytes afterwards. Lucky for me, I keep 
backups.
  I've never really liked Genkernel though and don't use it. Most of the time 
when I update my kernel it is pretty quick and easy:

I turn on the symlink USEflag which makes a new symlink of my new kernel.
So, after I emerge any new kernel source I just cd /usr/src/linux then 
zcat /proc/config.gz >.config  which copies the config from my current kernel 
then run make oldconfig (any new changes will prompt you); then make 
menuconfig if I want to change anything, otherwise make all install 
install_modules

Then just reboot.  I already have grub configured to use either the vmlinuz 
symlink in /boot which points to my latest kernel image or the fallback  
vmlinuz.old which is my previous kernel image.  The make install copies these 
files into /boot automaticly.


-- 
Chris
Linux 2.6.14-gentoo-r2 i686 AMD Athlon(tm) XP
 01:39:55 up 21:54,  8 users,  load average: 3.21, 2.61, 2.39
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-11-17  7:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 22:25 [gentoo-user] Kernel build no update grub Harry Putnam
2005-11-17  0:01 ` Iain Buchanan
2005-11-17  2:29   ` [gentoo-user] " Harry Putnam
2005-11-17  3:36     ` Iain Buchanan
2005-11-17  5:15       ` Harry Putnam
2005-11-17  4:24 ` Harry Putnam
2005-11-17  7:50   ` Chris Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-16 22:32 Harry Putnam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200511170150.46082.yeahsowhat@gmail.com \
    --to=yeahsowhat@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox