public inbox for gentoo-mips@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] Reducing the number of the MIPS supported stages
Date: Wed, 07 May 2014 03:22:38 -0400	[thread overview]
Message-ID: <5369DF3E.6050301@gentoo.org> (raw)
In-Reply-To: <5369DB62.2080607@gentoo.org>

On 05/07/2014 03:06, Markos Chandras wrote:
> 
> There are usually blockers and stuff due to MIPS being ~arch but
> catalyst, as a tool, works fine.
> 
> The livecd stages and netboots, however, were much more
>> problematic.
> 
> I don't think we do that anymore

Haven't in a *long* time.  However, it's been on my todo list for a good
while now.  The thing that killed netboots was the great uclibc break
several years ago where a chicken-and-egg scenario arose.  To compile from
uclibc-0.9.27 to .28, you needed ~gcc-4.4 (I think, maybe it was 3.4...).
However, you couldn't compile the required version of gcc, linked against
uclibc, without the .28 version.  So that broke a *lot* of people.

I have no idea how that was eventually resolved, but without uclibc,
netboots at the time were just too massive for the SGI Indy's to boot.
You'd get a "Not enough space in a FreeMemeoryArea() from ARCS.

Though...nowadays, I think that ARCS error has something to do with byte
alignment and not size.  Seems if you compile things in or out of the kernel
to increase or decrease its size, you can get a size that ARCS will be happy
with.

LiveCDs, OTOH...I do not look forward to even attempting those.  The two SGI
LiveCDs I produced used Gnome GDM, which was possible without sucking in
half of Gnome back then, which is not possible today, as far as I know.  I
don't know what's a good login manager these days, but it might be back to
classic XDM if I do attempt the things.


>> If you can still send me at least one of your stage3 spec files, that'd be
>> appreciated.  It's been 5-6 years since I last messed with catalyst.  The
>> Octane was my build platform, but combined with the bitrot that prevented it
>> from booting, moving, a new job, etc, I never got around to setting up stage
>> building on the O2.  Now that I can boot Octane again, I can at least
>> recover my old spec files, though.  Might help if I ever attempt to tackle
>> the livecd or netboot builds again.
> 
> I will email you a complete set of stage1/2/3 for, say, mips3 and then
> it's easy to figure out what do change for the rest :)

</smirk>

-- 
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28

"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


  reply	other threads:[~2014-05-07  7:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 14:06 [gentoo-mips] Reducing the number of the MIPS supported stages Markos Chandras
2014-05-05 17:04 ` Panagiotis Christopoulos
2014-05-05 17:17   ` Markos Chandras
2014-05-05 17:13 ` Justin Cormack
2014-05-05 17:16   ` Markos Chandras
2014-05-05 17:22 ` Matt Turner
2014-05-05 17:29   ` Markos Chandras
2014-05-05 23:34     ` Matt Turner
2014-05-05 22:02   ` Joshua Kinard
2014-05-05 23:30     ` Matt Turner
2014-05-06  0:15       ` Joshua Kinard
2014-05-05 23:36     ` Matt Turner
2014-05-06  0:09       ` Joshua Kinard
2014-05-06  7:07         ` Markos Chandras
2014-05-06  8:10           ` Joshua Kinard
2014-05-06 17:50             ` Markos Chandras
2014-05-06 21:37               ` Joshua Kinard
2014-05-07  7:06                 ` Markos Chandras
2014-05-07  7:22                   ` Joshua Kinard [this message]
2014-05-06 11:32           ` Anthony G. Basile
2014-05-06 17:40             ` Markos Chandras
2014-05-05 19:19 ` [gentoo-mips] " Anthony G. Basile
2014-05-05 19:33   ` Markos Chandras

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=5369DF3E.6050301@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=gentoo-mips@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