From: Blake McBride <blake@mcbride.name>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9Front network (driver?) issue
Date: Sun, 22 Dec 2013 21:29:51 -0600 [thread overview]
Message-ID: <CABwHSOu0XJCqfjhwn6gJ2b9JYxMj-mx0SvtzLsHnmr8AxwH5Yg@mail.gmail.com> (raw)
In-Reply-To: <CAJSxfm+m-sfaaZY2tXhNP9B=TyGDkL51kZWZtguudea4H6Rc0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
On Sun, Dec 22, 2013 at 9:07 PM, Skip Tavakkolian <
skip.tavakkolian@gmail.com> wrote:
> On Sun, Dec 22, 2013 at 5:43 PM, Blake McBride <blake@mcbride.name> wrote:
>
>> On Sun, Dec 22, 2013 at 6:03 PM, <cinap_lenrek@felloff.net> wrote:
>>
>>>
>>> the drive might be sensitive to the timing?
>>>
>>> can you pull and replug the drive and see if there are any
>>> error messages on the console?
>>>
>>
>> I don't know what "console" is. I don't see anything at my Plan-9 Shell
>> (RC) or on the screen in general.
>>
>>
>>
> see definition of console: http://en.wikipedia.org/wiki/System_console
>
Just in case you are serious about your comment, I understand what a
"console" is in the most generic terms, i.e. your wikipedia reference.
I also understand that Plan 9 (not Plan-9) has a number of servers. I
presume a console would be a window into said server. All this is utterly
useless unless I know the command to get a "console" window into the server
he is referring to. I need the command.
Actually, if you can read, you'd see that I moved on from this issue.
>
> FYI, it is Plan 9 (i.e. there's a space between); also the shell is rc,
> not RC.
>
While you're at it; is it "9-Front" (as Andrey said above) and "9-Atom"?
So, space with "Plan 9" and dash with the other two?
[-- Attachment #2: Type: text/html, Size: 4089 bytes --]
next prev parent reply other threads:[~2013-12-23 3:29 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 18:56 Blake McBride
2013-12-22 19:07 ` cinap_lenrek
2013-12-22 19:42 ` Blake McBride
2013-12-22 19:48 ` cinap_lenrek
2013-12-22 19:55 ` Blake McBride
2013-12-22 20:00 ` andrey mirtchovski
2013-12-22 20:03 ` cinap_lenrek
2013-12-22 20:04 ` erik quanstrom
2013-12-22 20:16 ` Blake McBride
2013-12-22 20:31 ` erik quanstrom
2013-12-22 21:19 ` Blake McBride
2013-12-22 21:30 ` cinap_lenrek
2013-12-22 23:04 ` Blake McBride
2013-12-22 23:13 ` cinap_lenrek
2013-12-22 23:28 ` Blake McBride
2013-12-23 0:03 ` cinap_lenrek
2013-12-23 1:43 ` Blake McBride
2013-12-23 3:07 ` Skip Tavakkolian
2013-12-23 3:29 ` Blake McBride [this message]
2013-12-23 3:37 ` andrey mirtchovski
2013-12-23 3:48 ` Blake McBride
2013-12-23 4:02 ` Kurt H Maier
2013-12-23 6:28 ` Matthew Veety
2013-12-23 9:42 ` Steffen Daode Nurpmeso
2013-12-23 13:57 ` erik quanstrom
2013-12-23 3:49 ` Skip Tavakkolian
2013-12-23 13:38 ` erik quanstrom
2013-12-23 13:58 ` erik quanstrom
2013-12-23 4:52 ` cinap_lenrek
2013-12-23 14:59 ` Blake McBride
2013-12-23 15:04 ` Alexander Kapshuk
2013-12-23 15:11 ` Blake McBride
2013-12-23 15:17 ` Steve Simon
2013-12-23 15:37 ` erik quanstrom
2013-12-23 16:09 ` Tristan
2013-12-23 16:44 ` Steve Simon
2014-02-10 13:27 ` erik quanstrom
2013-12-24 3:43 ` erik quanstrom
2013-12-23 15:17 ` Alexander Kapshuk
2013-12-23 15:04 ` Friedrich Psiorz
2013-12-23 9:34 ` Steffen Daode Nurpmeso
2013-12-23 14:42 ` Blake McBride
2013-12-22 19:54 ` Kurt H Maier
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=CABwHSOu0XJCqfjhwn6gJ2b9JYxMj-mx0SvtzLsHnmr8AxwH5Yg@mail.gmail.com \
--to=blake@mcbride.name \
--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).