public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] base-system needs developers who care
Date: Mon, 29 Aug 2016 13:18:18 -0400	[thread overview]
Message-ID: <cf995be8-ff9c-dd45-2e8e-846be5eaef7a@gentoo.org> (raw)
In-Reply-To: <1472047708.31785.156.camel@gentoo.org>

On 08/24/2016 10:08, Pacho Ramos wrote:
> El mié, 24-08-2016 a las 16:05 +0200, Lars Wendler escribió:
>>
> [...]
>> Oh, and to all new team members:
>> Please keep in mind to *not* use EAPI-6 for base-system packages yet,
>> so
>> we can retain a somewhat stable upgrade path even for very old
>> systems.
>>
>>
>> Kind regards
>> Lars
> 
> This reminds me a question I have for some time: is it documented in
> some place what are the steps to follow for updating old systems? I
> remember posts like:
> http://blog.siphos.be/2013/12/upgrading-old-gentoo-installations/
> 
> but I don't know if that is "official" or a workaround or... :/
> 
> Thanks a lot for the info!

When I got SGI Octane booting Linux again in 2014, I had a dormant ~2009-era
system still installed on that machine.  Upgrading was...interesting.  Entirely
doable -- I think I hand-jammed a modern Portage into it to get started, then
incrementally step-upgraded the thing over a period of 2-3 weeks until the
system packages were fully working.

Then I got torched by gcc's PR61538, where someone's upstream change tripped up
an atomic fault on the R10000 CPUs these things use, which left me stuck at
gcc-4.8.x.  That went on for 8 months until someone else upstream accidentally
fixed it.  Now, I've just got to figure out this irritating 2GB memory DMA bug...

But still, depending on the age of the install, it's a task that only the
dedicated and OCD should try to tackle.  Everyone else is better off salvaging
config files by mounting the disks in another system, then nuking the old
install from orbit.

I'll let you guys now how the next attempt works out, whenever I get my Indigo2
R10000 to boot again.  I think the Gentoo install on that machine hasn't seen
the light of the Kernel since ~2006.  Probably earlier.

-- 
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
6144R/F5C6C943 2015-04-27
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943

"The past tempts us, the present confuses us, the future frightens us.  And our
lives slip away, moment by moment, lost in that vast, terrible in-between."

--Emperor Turhan, Centauri Republic


  parent reply	other threads:[~2016-08-29 17:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 23:17 [gentoo-dev] base-system needs developers who care Robin H. Johnson
2016-08-23 23:36 ` Anthony G. Basile
2016-08-24  0:03 ` Lars Wendler
2016-08-24  0:08   ` Anthony G. Basile
2016-08-24  1:06     ` Benda Xu
2016-08-24 14:05     ` Lars Wendler
2016-08-24 14:08       ` Pacho Ramos
2016-08-24 14:42         ` Upgrading Old Gentoo - Was " M. J. Everitt
2016-08-29 17:18         ` Joshua Kinard [this message]
2016-08-24 15:32       ` Mike Gilbert
2016-08-24 15:49         ` Michael Orlitzky
2016-08-25  8:00         ` Alexis Ballier
2016-08-24 17:17       ` William Hubbs
2016-08-24 20:33       ` Andreas K. Huettel
2016-08-24  1:11 ` William Hubbs
2016-08-24 17:24   ` Robin H. Johnson
2016-08-24  1:25 ` Patrick McLean
2016-08-24 12:04 ` Jason Zaman
2016-08-24 15:37 ` Mike Gilbert
2016-08-25  8:01 ` Alexis Ballier
2016-08-28  6:34   ` Daniel Campbell

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=cf995be8-ff9c-dd45-2e8e-846be5eaef7a@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=gentoo-dev@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