[9fans] Starting rio on combined CPU, file and auth

[9fans] Starting rio on combined CPU, file and auth

[G B]

Fairly new to 9front and Plan 9.? Using 9front and set "service=cpu" but rio doesn't start.? I've tried adding screenrc to /rc/bin/cpurc and /cfg/$sysname/cpustart but gives me errors on /dev/draw.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.9fans.net/private/9fans/attachments/20170504/93eb740a/attachment.html>

Re: [9fans] Starting rio on combined CPU, file and auth

[Alex Musolino]

[-- Attachment #1: Type: text/plain, Size: 584 bytes --]

> 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: 803 bytes --]

Re: [9fans] Starting rio on combined CPU, file and auth

[Skip Tavakkolian]

[-- 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 --]

Re: [9fans] Starting rio on combined CPU, file and auth

[Alex Musolino]

[-- Attachment #1: Type: text/plain, Size: 287 bytes --]

> rio runs fine on any cpu server; your draw device determines where the
display is.

Yes, of course. That was sloppy writing on my part. What I should have said
was:

"CPU servers typically don't have any reason to run rio on a local draw
device."

--
Cheers,
Alex Musolino

[-- Attachment #2: Type: text/html, Size: 589 bytes --]

Re: [9fans] Starting rio on combined CPU, file and auth

[Charles Forsyth]

[-- Attachment #1: Type: text/plain, Size: 243 bytes --]

On 5 May 2017 at 02:22, Alex Musolino <musolinoa@gmail.com> wrote:

>
> "CPU servers typically don't have any reason to run rio on a local draw
> device."
>

I don't even bother including the draw device and hangers-on in cpu servers.

[-- Attachment #2: Type: text/html, Size: 575 bytes --]