9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ipaq installation changes
Date: Thu,  5 Jun 2003 09:32:28 +0200	[thread overview]
Message-ID: <1ec9123d8949805be68aeafcf6b19ae7@plan9.escet.urjc.es> (raw)
In-Reply-To: <b29babbe7e7ffb41abeea791354e302e@collyer.net>

> I just installed Plan 9 on an ipaq.  Both Booting101 and the wiki need
> to be updated.  I bought my ipaq used and it appears to have been

Thanks a lot.

> I've put copies of the relevant boot loaders and an updated version of
> Booting101 at www.collyer.net/who/geoff/9/bitsy/ so that others can
> find them easily.
>

Great. I'll copy your Booting101 to sources

> Is anybody working on making the Targus Stowaway collapsible keyboard
> work on the ipaq?  It would sure be easier than trying to hit the
> right keys on the wee keyboard at the bottom of the screen.

Not that I know.

> What do you other folks with bitsies do with them?

Mostly to listen music and some times for meetings. I run out of
battery so often that I cannot use it as a PDA (use a Palm for that).

> I found Plan 9 on the bitsy to be less robust than I'd expected.
> Running mfs and then acme locally crashed it, as did running mfs and
> aux/timesync locally.  When it crashes, I get no messages, just the
> penguin (`you lose, back to Linux', I guess).

I couldnt reproduce this. Did you recompile the 5[acl] set and all the
libraries and commands for the arm after that. Acme crashed for me before
I did that (I really mean acme, and not the kernel).

Did you have the bitsy on the serial line while crashed? Was there
any message in the serial console? The print for the console is disabled
to avoid cluttering the display, messages go to the serial line instead.



  reply	other threads:[~2003-06-05  7:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05  3:33 Geoff Collyer
2003-06-05  7:32 ` Fco.J.Ballesteros [this message]
2003-06-05  7:41   ` Geoff Collyer
2003-06-05  7:46     ` Fco.J.Ballesteros
2003-06-05 13:13   ` David Presotto
2003-06-05 13:38     ` Axel Belinfante
2003-06-05 22:18       ` Geoff Collyer
2003-06-05 22:37         ` Dan Cross
2003-06-05 22:56         ` Martin Harriss
2003-06-06  1:03           ` Lyndon Nerenberg
2003-06-06  1:41             ` Martin Harriss
2003-06-05 16:06     ` Jack Johnson
2003-06-05 16:33       ` John Murdie
2003-06-05 18:36         ` [9fans] handheld computers rog
2003-06-05 18:39           ` Fco.J.Ballesteros
2003-06-05 23:16       ` [9fans] ipaq installation changes Charles Forsyth
2003-06-05 22:12     ` Lyndon Nerenberg
2003-06-05 13:48 Stephen Parker

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=1ec9123d8949805be68aeafcf6b19ae7@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).