public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: debian etch sh3 and sh4
Date: Wed, 23 Jan 2008 13:30:19 +0000	[thread overview]
Message-ID: <20080123143019.a9b6f4cd.Kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <82C85C285793D5ebiharaml@si-linux.com>

On Wed, 23 Jan 2008 07:16:43 -0500
Mike Frysinger <vapier@gentoo.org> wrote:

> On Wednesday 23 January 2008, Adrian McMenamin wrote:
> > On Wed, January 23, 2008 9:53 am, Paul Mundt wrote:
> > > In 16MB you will always be bordering on thrashing just trying to do _any_
> > > basic tasks. Your options are realistically limited to busybox or
> > > throwing the damn thing out (the recommended option). Doing anything more
> > > involved than that was pretty questionable back when the kernel used a
> > > lot less memory, and trying to do builds in that environment is well past
> > > absurdity these days. 64MB is painful, but at least workable.
> >
> > You really are like the Kerryman who, when asked how to get to Dublin said
> > "well, I wouldn't start from here." :)
> >
> > I don't mind the thrashing if it gets me something that works and which
> > can later be used as the basis of a "distro" - which is my aim here.
> >
> > Anyone know how stable swap over nfs is these days? Speed is a secondary
> > consideration.
> >
> > NB: CF or similar isn't an option. In theory you could put a very small
> > swap partition on the Dreamcast's VMUs but access to that is likely to be
> > much slower even than NFS - as it would be rationed to 60 times per
> > second.
> 
> i used to build on the dreamcast, but the swapping was terrible so i gave up 
> and just bought a lantank as it has 64megs ;)
> -mike
> 

We've used ipkg for jlime, which basicly is a minimal version of apt. One would expect great speed, but unfortunantly
that isn't the case. It seems to have a hard time handling the database which is why we've split it up into
smaller pieces.
ipkg is borderline usable on an jornada with 16mb/133mhz so I doubt apt will be any better.

Personally I believe that slackware + some minimal packagemanager is the way to go. Doesn't simplify much for the user
but will be easy to access packages and also maintain diffs against the main sources. Archlinux might also be an option since
I have greater faith in pacman as a package manager, but currently there's no superH port.

I agree with paul that we need to see some commitment to getting stuff into the true release instead of providing "unsupported"/"unofficial" branches which pop up every year or so. 





      parent reply	other threads:[~2008-01-23 13:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 12:22 debian etch sh3 and sh4 Yutaro Ebihara
2008-01-22  0:37 ` Paul Mundt
2008-01-22 11:54 ` Adrian McMenamin
2008-01-22 12:32 ` Paul Mundt
2008-01-22 14:34 ` Mike Frysinger
2008-01-22 15:04 ` Adrian McMenamin
2008-01-22 22:49 ` Mike Frysinger
2008-01-23  9:29 ` Adrian McMenamin
2008-01-23  9:40 ` Manuel Lauss
2008-01-23  9:53 ` Paul Mundt
2008-01-23 10:28 ` Adrian McMenamin
2008-01-23 12:16 ` Mike Frysinger
2008-01-23 13:30 ` Kristoffer Ericson [this message]

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=20080123143019.a9b6f4cd.Kristoffer.ericson@gmail.com \
    --to=kristoffer.ericson@gmail.com \
    --cc=linux-sh@vger.kernel.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