From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>,
G B <g_patrickb@yahoo.com>
Subject: Re: [9fans] Starting rio on combined CPU, file and auth
Date: Fri, 5 May 2017 01:00:37 +0000 [thread overview]
Message-ID: <CAJSxfm+fVghQUX3XpwShheASrYx3huOUHLuCR+C7SdmcpOnxUA@mail.gmail.com> (raw)
In-Reply-To: <CAMVULc51ARfVfCsGHe-SW+PEeMQZiHExLVg8K8bQa_7ViHnzOw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
A cpu server may not have a display (i.e. uses a serial console). rio runs
fine on any cpu server; your draw device determines where the display is.
On Thu, May 4, 2017 at 5:41 PM Alex Musolino <musolinoa@gmail.com> wrote:
> > Using 9front and set "service=cpu" but rio doesn't start.
>
> This is expected. CPU servers typically don't have any reason to run
> rio. Mine don't even have monitors attached (usually).
>
>
> > I've tried adding screenrc to /rc/bin/cpurc and /cfg/$sysname/cpustart
> > but gives me errors on /dev/draw.
>
> If you compare /rc/bin/cpurc and /rc/bin/termrc you'll see that the
> vga device (#v) is bound only in /rc/bin/termrc. You can arrange
> this in /rc/bin/cpustart, before you include /rc/bin/screenrc, like so:
>
> bind -a '#v' /dev >/dev/null >[2=1]
>
> --
> Cheers,
> Alex Musolino
>
>
[-- Attachment #2: Type: text/html, Size: 1369 bytes --]
next prev parent reply other threads:[~2017-05-05 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <351618734.2458204.1493931402128.ref@mail.yahoo.com>
2017-05-04 20:56 ` G B
2017-05-05 0:41 ` Alex Musolino
2017-05-05 1:00 ` Skip Tavakkolian [this message]
2017-05-05 1:22 ` Alex Musolino
2017-05-05 13:24 ` Charles Forsyth
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=CAJSxfm+fVghQUX3XpwShheASrYx3huOUHLuCR+C7SdmcpOnxUA@mail.gmail.com \
--to=skip.tavakkolian@gmail.com \
--cc=9fans@9fans.net \
--cc=g_patrickb@yahoo.com \
/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).