From: Jack Johnson <knapjack@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] acme/sam junky in need of advice
Date: Mon, 9 May 2005 16:28:56 -0700 [thread overview]
Message-ID: <6e35c062050509162822c66a1a@mail.gmail.com> (raw)
In-Reply-To: <db681159462449139f66b4be2a3b2eaf@vitanuova.com>
On 5/9/05, rog@vitanuova.com <rog@vitanuova.com> wrote:
> it's just a standard inferno distribution. (plus a .bat file
> to start up the inferno wm automatically - one line)
I've got the same thing going on my USB key. It was pretty trivial to
set up, though because I use mine cross-platform it took a minor
amount of extra oomph.
Though the key is formatted FAT32, I think I ended up doing the
installation on either OSX or Linux due to case sensitivity. Then I
just copied/renamed the appropriate emu binaries for the correct
platforms in the correct places, created batch and shell scripts to
handle the startup and voila.
Since then I've ripped out source/binaries for some of the platforms I
don't use (Solaris), just to recover some space. Plus, I'm also lazy
and haven't updated it in a while, but it works very well.
I had worked/hoped for a while to get it to auth back to my home box,
import the filesystem, etc. -- kind of an Inferno thin client -- but I
really wanted it all to happen from within the WM, but certain aspects
really wanted authentication before the binds to make everything
friendly.
I also messed around with Inferno hosted on Linux for a while, so I
could just VNC to a full-screen session and just pack around the VNC
client. Java VNC client would have worked, too, but how many layers
do you really want to add?
I also pack around 9pm on my key, because I find that useful. My
"butcher box" is currently running Asterisk for a work-related
project, otherwise I'd probably do what everyone else does and just
drawterm home.
Where's that iMac Mini port, so I can just leave a CPU/auth/fileserver
on the bookshelf and be done with it? ;)
-Jack
next prev parent reply other threads:[~2005-05-09 23:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 11:34 Robert Raschke
2005-05-09 15:15 ` Richard Bilson
2005-05-09 15:23 ` Jack Johnson
2005-05-09 15:51 ` Robert Raschke
2005-05-09 23:35 ` rog
2005-05-09 23:37 ` Jack Johnson
2005-05-10 7:20 ` Charles Forsyth
2005-05-10 21:33 ` Bruce Ellis
2005-05-09 23:37 ` Jack Johnson
2005-05-10 12:43 ` Many thanks (Was: [9fans] acme/sam junky in need of advice) Robert Raschke
2005-05-09 15:55 ` [9fans] acme/sam junky in need of advice Richard Bilson
2005-05-10 1:00 ` Richard Bilson
2005-05-09 16:06 ` Skip Tavakkolian
2005-05-09 16:19 ` Robert Raschke
2005-05-09 17:09 ` rog
2005-05-09 17:13 ` andrey mirtchovski
2005-05-09 17:25 ` rog
2005-05-09 22:50 ` Charles Forsyth
2005-05-09 23:28 ` Jack Johnson [this message]
2005-05-09 19:01 ` Ronald G. Minnich
2005-05-09 20:17 ` Bruce Ellis
2005-05-09 20:23 ` rog
2005-05-09 20:52 ` David Leimbach
2005-05-09 20:57 ` Bruce Ellis
2005-05-09 21:28 ` Skip Tavakkolian
2005-05-09 21:41 ` Bruce Ellis
2005-05-10 6:21 ` [9fans] " Matthias Teege
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=6e35c062050509162822c66a1a@mail.gmail.com \
--to=knapjack@gmail.com \
--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).