From: 320095285153-0001@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Kernels
Date: Sat, 13 Jan 2001 20:29:42 +0100 [thread overview]
Message-ID: <3A60ACA6.A651BCED@gottinger.de> (raw)
In-Reply-To: 20010113143920.A5339@kabbu.akopia.com
"Jerry A!" wrote:
> Hey, I was wondering, what should we be doing for kernels? I know that
> sys-kernel/linux-UP-2.x.x are woefully out of date. Can we look at
> putting them into the Attic and keeping the tree clean and new user
> confusion to a minimum?
Yes that's true we can drop that stuff.
>
>
> In a similar vein, will sys-kernel/linux-sources stay current with
> sys-kernel/linux? Or should we just grab our own sources for
> /usr/src/linux?
The problem in the last weeks was, that 2.4.0-final kernels where
definately not stable and I way allways busy
making new kernel-packages.
The lates 2.4.0ac8 seems to be stable, so I will copy that to
linux-sources.
I presonally prefere the following method if I need a special kernel.
First I run "ebuild kernel unpack", then I cd into
/tmp/portage/linux....../work/linux and configure the kernel or I copy
my private config and autoconf.h manually to the workdir.
After that I continue with "ebuild kernel compile".
Jerry can you send me modified .config and include/linux/autoconf.h
version that include a usefull pcmcia-support?
Bye Achim
>
>
> --Jerry
>
> name: Jerry Alexandratos || Open-Source software isn't a
> phone: 703.599.6023 || matter of life or death...
> email: jerry@akopia.com || ...It's much more important
> || than that!
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2001-01-13 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 19:39 [gentoo-dev] Kernels Jerry A!
2001-01-13 19:29 ` Achim Gottinger [this message]
2001-01-13 19:35 ` Achim Gottinger
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=3A60ACA6.A651BCED@gottinger.de \
--to=320095285153-0001@t-online.de \
--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