>OK now I can receive email in Acme in Plan 9 for the Raspberry Pi. I'm
>trying to get auth/fgui to start automatically when I start Plan 9.
>Have tried to put it into the profile file but it doesn't work. Any
>hints greatly appreciated.
auth/fgui requires Rio, so it needs to load after Rio has st
OK now I can receive email in Acme in Plan 9 for the Raspberry Pi. I'm
trying to get auth/fgui to start automatically when I start Plan 9.
Have tried to put it into the profile file but it doesn't work. Any
hints greatly appreciated.
Kind Regards,
Mats
2014-10-15 15:00 GMT+02:00, trebol :
> Steff
> On 19 October 2014 16:36, Charles Forsyth
> wrote:
>
> What I really meant was that few programs care about Dir.type since most
> don't care what serves the names
> as long as they behave as expected. Relatively few programs use the # names
> directly in bind(2) calls:
> it's more common to set
On 19 October 2014 16:36, Charles Forsyth wrote:
> Only a few have any sort of global
> significance, and even that's probably a mistake.
>
What I really meant was that few programs care about Dir.type since most
don't care what serves the names
as long as they behave as expected. Relatively few
On 19 October 2014 16:32, Charles Forsyth wrote:
> Only a few have any sort of global
> significance, and even that's probably a mistake.
>
Ignore that: that statement's wrong since they appear in bind operations in
bind(1), bind(2), /lib/namespace and similar contexts.
I also forgot to add tha
On 19 October 2014 13:30, Carsten Kunze wrote:
> where is the type field of libc struct Dir documented? In source I found
> a compare of field type with the char 'M'. Where can I loop up what 'M'
> means?
>
It's the Unicode character used to identify the device driver within a
kernel,
and are
Hello,
where is the type field of libc struct Dir documented? In source I found a
compare of field type with the char 'M'. Where can I loop up what 'M' means?
Carsten
