From: "Martín Ferrari" <martin.ferrari@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Newbie looking for pointers
Date: Wed, 15 Oct 2008 17:54:00 -0300 [thread overview]
Message-ID: <b9800b70810151354hd7aef9ew6cd41a347d22b9b9@mail.gmail.com> (raw)
In-Reply-To: <8436e37dfc15c5e28b118613882db7e7@quintile.net>
On Wed, Oct 15, 2008 at 11:55, Steve Simon <steve@quintile.net> wrote:
> Sounds like you understand quite well really, I think you
> are further up the learning curve than you think.
Well, it seems that I wasn't so far away, now I'm happily running a
cpu/auth/file server and many disk-less terminals (even tunneling a
VDE connection thru the internet!) without a glitch. And now I have a
brand new toy to discover :)
Thanks a lot for the help, I was completely blocked.
Tincho.
--
Martín Ferrari
next prev parent reply other threads:[~2008-10-15 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 9:42 Martín Ferrari
2008-10-15 10:22 ` Steve Simon
2008-10-15 10:49 ` Martín Ferrari
2008-10-15 12:10 ` Charles Forsyth
2008-10-15 20:35 ` Pietro Gagliardi
2008-10-15 14:55 ` Steve Simon
2008-10-15 20:54 ` Martín Ferrari [this message]
2008-10-15 23:02 ` ron minnich
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=b9800b70810151354hd7aef9ew6cd41a347d22b9b9@mail.gmail.com \
--to=martin.ferrari@gmail.com \
--cc=9fans@9fans.net \
/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).