From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem using genkernel
Date: Wed, 27 Jul 2005 08:39:19 +0100 [thread overview]
Message-ID: <20050727083919.357d4ffe@hactar.digimed.co.uk> (raw)
In-Reply-To: <20050727053623.GD19342@tribus.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
On Wed, 27 Jul 2005 07:36:23 +0200, Waldemar Tribus wrote:
> >Why? If you are comfortable with configuring your kernel by hand, why
> >give up control of the process to a tool that is known to cause
> >problems for many people?
>
> Just wanted to follow gentoo 2.4 to 2.6 migration guide,
> to avoid stipud error which i could make if i would do
> it by myself :)
In my experience, it's easier to fix your own stupid errors than those
made by an automated system...
--
Neil Bothwick
Would a fly without wings be called a walk?
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-27 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 9:35 [gentoo-user] Problem using genkernel Waldemar Tribus
2005-07-25 9:56 ` Zac Medico
2005-07-27 5:33 ` Waldemar Tribus
2005-07-25 10:16 ` Neil Bothwick
2005-07-27 5:36 ` Waldemar Tribus
2005-07-27 7:39 ` Neil Bothwick [this message]
2005-07-27 15:54 ` A. Khattri
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=20050727083919.357d4ffe@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--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