From: Nicholas Hockey <tilt@bluecherry.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gentoo Kernel Installation Doc
Date: 10 Jan 2003 15:08:29 -0500 [thread overview]
Message-ID: <1042229309.2452.3.camel@blackhole> (raw)
In-Reply-To: <200301101004.19439.yannick.koehler@colubris.com>
[-- Attachment #1.1: Type: text/plain, Size: 2180 bytes --]
So Copy it over, nothing relly hard about that, tho i am a firm bealiver
that you should know your machine enough to be able to compile a kernel
for it. tho having it do this automaticly would relly take away the
apeal of gentoo for me, i like to be in control, and using some yuppies
pre-fab kernel, with things he thinks i should use, that would just take
up precious HD space, is not the gentoo way.
On Fri, 2003-01-10 at 10:04, 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.
--
Nicholas Hockey (Tilt) <tilt@bluecherry.net>
Unix Administrator
Tilt@EFnet #BitchX
--------------------------------------------------------------------
GnuPG KeyID 4EDE2B84
Key fingerprint = B916 6032 BE3D 490D 2A08 F1BC 948A A4C1 4EDE 2B84
gpg --keyserver wwwkeys.pgp.net --recv-keys 4EDE2B84
--------------------------------------------------------------------
[-- Attachment #1.2: Type: text/html, Size: 2603 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-01-10 20:11 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
2003-01-10 20:08 ` Nicholas Hockey [this message]
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=1042229309.2452.3.camel@blackhole \
--to=tilt@bluecherry.net \
--cc=gentoo-dev@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