All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Nasrat <pauln@truemesh.com>
To: Linux 8086 <linux-8086@vger.kernel.org>
Subject: Re: Who's doing the SIBO port?
Date: Tue, 17 Dec 2002 21:36:34 +0000	[thread overview]
Message-ID: <20021217213633.GA9153@raq465.uk2net.com> (raw)
In-Reply-To: <200212170917.gBH9H1Ix018482@eddie.loc>

On Tue, Dec 17, 2002 at 09:17:00AM +0000, Richard Wallman wrote:
> After successfully wiping the Internal ramdisk on my 3c (DOH! Where's
> that backup...) I thought it might be easier to ask the maintainer.

Apologies, I've been meaning to update the docs... :(

I'll shout you beer sometime if you are ever in London.

> Who's the current maintainer of the SIBO port, and is there any work

I've been keeping it compilable for elks, so I guess that's me.  however
without workable psion at the moment as it was stolen :(  Will replace
shortly, as my brother may be giving me his.

> being done on it? I think at very least putting a bloody big warning in
> the FAQ along the lines of: "If you don't know exactly what you're
> doing, you're likely to wipe everything, so backup NOW!" rather than
> the kinda weak "It's not worth installing" message in /INSTALLATION

OK - will add a better warning for the sibo stuff and some better
instructions.

Things I want do - enable support for larger ssd's, ensure it doesn't
run out of memory after a few commands.  Try to make work with psions
with lower memory

Paul

      reply	other threads:[~2002-12-17 21:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-17  9:17 Who's doing the SIBO port? Richard Wallman
2002-12-17 21:36 ` Paul Nasrat [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=20021217213633.GA9153@raq465.uk2net.com \
    --to=pauln@truemesh.com \
    --cc=linux-8086@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.