From: "Sid Spry" <sid@aeam.us>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] old kernel on Gentoo
Date: Tue, 30 Jun 2020 09:34:44 -0500 [thread overview]
Message-ID: <f40d2ab1-f35c-4bcd-b634-e035d299743c@www.fastmail.com> (raw)
In-Reply-To: <VI1PR10MB156819DF0E7CA7FBFE793045F7960@VI1PR10MB1568.EURPRD10.PROD.OUTLOOK.COM>
On Sun, Jun 21, 2020, at 5:31 AM, Raffaele BELARDI wrote:
> > -----Original Message-----
> > From: james <garftd@verizon.net>
> > Sent: Thursday, June 18, 2020 21:36
> > To: gentoo-user@lists.gentoo.org
> > Subject: Re: [gentoo-user] old kernel on Gentoo
> >
> > On 6/17/20 12:52 PM, Raffaele BELARDI wrote:
> > > Hello,
> > >
> > > I might need to build and run an old 3.x kernel on a Desktop PC for
> > > some very specific tests. Would Gentoo be a good solution?
> > >
> > > I see that currently gentoo-sources only includes 4.x and 5.x sources.
> > >
> > > Thanks,
> > >
> > > raffaele
> > >
> >
> > I use a 3.18.40 kernel, currently, on one of my AMD systems. It has
> > thousands of source build packages, not only from portage but many others.
> >
>
> What about the rest of the system, in particular GCC and the C
> libraries? Do you manage to build the 3.x kernel with up to date system
> or do you need to ''freeze'' some packages?
>
If you don't care about age of the userland most tools are actually very backwards
compatible and should work on a 3.x kernel. You will need to try it, but I expect
the modern @system set of packages would work just fine.
If you do need an old userland what I might try to do is grab an old Debian/Ubuntu
CD. You could then use Portage Prefix to build the older tools you need with a
more contemporary userland. Again, the bigger issue will be old releases falling out
of tree.
next prev parent reply other threads:[~2020-06-30 14:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 16:52 [gentoo-user] old kernel on Gentoo Raffaele BELARDI
2020-06-17 17:36 ` J. Roeleveld
2020-06-17 19:45 ` Michael
2020-06-18 15:45 ` Raffaele BELARDI
2020-06-17 18:44 ` David Haller
2020-06-18 6:16 ` Gerrit Kuehn
2020-06-18 19:35 ` james
2020-06-18 20:02 ` Rich Freeman
2020-06-18 20:47 ` james
2020-06-21 10:31 ` Raffaele BELARDI
2020-06-30 14:34 ` Sid Spry [this message]
2020-07-01 7:32 ` Gerrit Kuehn
2020-07-01 8:35 ` karl
2020-07-02 21:55 ` james
2020-06-30 8:29 ` Andreas K. Huettel
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=f40d2ab1-f35c-4bcd-b634-e035d299743c@www.fastmail.com \
--to=sid@aeam.us \
--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