public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Don Jerman" <djerman@pobox.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Switching from Genkernel to manual build
Date: Wed, 1 Aug 2007 14:40:47 -0400	[thread overview]
Message-ID: <6dc3c33d0708011140g75f65f54t8f6ce07e0923b5c5@mail.gmail.com> (raw)
In-Reply-To: <46B02374.8030009@silvanoc.com>

On 8/1/07, Abraham Marín Pérez <tecnic5@silvanoc.com> wrote:
> Dan Cowsill escribió:
> > Is there any specific process to or problems one might encounter as a
> > result of switching from a Genkernel built kernel over to a manually
> > built kernel?
> >
> As far as I can think of it would be enough getting the config file
> generated by genkernel, editing it through make config or similar and go
> ahead.

Only other thing I ran into (admittedly in 2004 or 2005 or so) is if
genkernel is doing any initrd-magick for you you'll need to either
understand it and do it yourself, or config your kernel so all that
stuff is built-in.  It was a little embarrassing when none of my JFS
partitions got found on that first reboot.  Keep a boot CD or DVD in
case of real disaster, and configure your current boot kernel as an
alternative choice in GRUB until you get the hand-rolled version
stabilized.
--
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2007-08-01 18:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01  4:08 [gentoo-user] Switching from Genkernel to manual build Dan Cowsill
2007-08-01  6:08 ` Abraham Marín Pérez
2007-08-01  7:15   ` Dale
2007-08-01 18:40   ` Don Jerman [this message]
2007-08-01  9:17 ` Kent Fredric
2007-08-01 16:59   ` Volker Armin Hemmann
2007-08-01 20:28     ` Kent Fredric
2007-08-01 21:05       ` Neil Bothwick
2007-08-01 21:22         ` Daniel da Veiga

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=6dc3c33d0708011140g75f65f54t8f6ce07e0923b5c5@mail.gmail.com \
    --to=djerman@pobox.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