public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alain <alain@rexorient.com>
To: Yannick Koehler <yannick.koehler@colubris.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gentoo Kernel Installation Doc
Date: Fri, 10 Jan 2003 08:47:29 -0700	[thread overview]
Message-ID: <20030110154729.GB1535@rexorient.com> (raw)
In-Reply-To: <200301101004.19439.yannick.koehler@colubris.com>

I tend to agree with this, as it would also eliminate a problem I ran into
(which I'm assuming will get fixed for the final 1.4 release):

The 1.4 RC2 CD boots with a 2.4.20 kernel, which happens to recognize and
support the nVidia ethernet port on my Asus A7N8X motherboard (later version
of the 2.4.20 kernel also recognize the 3COM ethernet port, but alas.. I need
only one port to get gentoo going).  After the gentoo install was completed
and I rebooted, I ended up with a 2.4.19 kernel, which doesn't support either
of the ethernet ports without being patched.

Once a new kernel is compiled, the install kernel could be added as a
"fail-safe" backup kernel to the boot menu.

Alain


On Fri, Jan 10, 2003 at 10:04:19AM -0500, Yannick Koehler wrote:
>
>I think it would be nice that I could take the kernel from the LiveCD and 
>installed it as is (including moduels) over my new installation PC instead of 
>building a new one.  For sure I would like to do that past the first reboot 
>but I often got problems where I forgot some required kernel option rebooting 
>into a "Missing console" kernel critical stop or into a "Missing DevFS" 
>state.
>
>Then I have to reboot from the CD, remount everything as it was, chroot and 
>recompile ...  It would be really great that the installation start by having 
>you install the LiveCD kernel with the module get this to be the default 
>kernel for your installation then once rebooted to that new kernel from the 
>hard disk you could then start installing/playing with a new version of the 
>kernel.
>
>At least at that point if the new kernel failed, a simple reboot with the 
>selection through grub/lilo to pick the previous working kernel would be 
>enough to get you back inside a working state to debug your kernel.
>
>That installation could also be simplified by creating an ebuild such as 
>livecd-kernel and having the admin type emerge livecd-kernel to do that step 
>for him.
>
>This would also make it easier for an installation software to get that step 
>automatically done.
>
>-- 
>
>Yannick Koehler
>
>--
>gentoo-dev@gentoo.org mailing list
>

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-01-10 15:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10 15:04 [gentoo-dev] Gentoo Kernel Installation Doc Yannick Koehler
2003-01-10 15:47 ` Alain [this message]
2003-01-10 20:08 ` Nicholas Hockey

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=20030110154729.GB1535@rexorient.com \
    --to=alain@rexorient.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=yannick.koehler@colubris.com \
    /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