> /sys/src/libc/9syscall/sys.h lists 51 system calls.
> ten have underscores. OSEEK is also obsolete.
> that would make 22%.
If you count DEATH and PASSFD in sysproc.c and
sysfile.c, respectively, then it's 25%. They
are the missing syscall numbers 48 and 49.
--
"Christ, what an imagination I've
> We're partly there in spirit; what fraction of the 4e kernel's system
> calls are there for backwards compatibility? ;)
i don't know if that's a rhetorical question or not. it's not hard to answer.
/sys/src/libc/9syscall/sys.h lists 51 system calls. ten have underscores.
OSEEK is also obsole
On 9/1/07, Uriel <[EMAIL PROTECTED]> wrote:
> With this way of thinking we will never catch up with lunix's 400
> syscalls (and counting, not to mention the ioctls)!
We're partly there in spirit; what fraction of the 4e kernel's system
calls are there for backwards compatibility? ;)
Back on topi
On 9/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> It should work now. Brazil's whois server produces non-standard
> output, so we have to recognise it specially, and the output format
> has changed since we last adapted to it.
>
>
still the same: I can't connect from Rio de Janeiro but it
It should work now. Brazil's whois server produces non-standard
output, so we have to recognise it specially, and the output format
has changed since we last adapted to it.
Hello,
Trying to access sources from Rio de Janeiro - RJ - Brazil fails with
'restricted remote address'. Last time I checked, people from Belo
Horizonte - MG - Brazil could connect.
any hints?
iru
With this way of thinking we will never catch up with lunix's 400
syscalls (and counting, not to mention the ioctls)!
uriel
> See /sys/src/libc/9sys/dirread.c and read(5). Plan 9 doesn't have a
> distinct system call for reading directory entries.
>
> --Joel
>
> I put a new Intel PRO/1000 in my Plan 9 server. The card is detected
> by 9load (?) as ether#0 igbe and then as #l1: i82543. There is another
> network interface on board which ist detected as elnk3. I put
> ether0=igbe, ether1=elnk3 in my plan9.ini.
>
> My problem is, that /net/ether0 points a
On 01:25 Sat 01 Sep, Anthony Martin wrote:
> ether0=type=igbe
> ether1=type=elnk3
Works great, many thanks
Matthias
>> ether0=igbe, ether1=elnk3 in my plan9.ini.
>
> I think that should be:
>
> ether0=type=igbe
> ether1=type=elnk3
I second that. It's caught me a good few times, including this
particular incident :-(
++L
> ether0=igbe, ether1=elnk3 in my plan9.ini.
I think that should be:
ether0=type=igbe
ether1=type=elnk3
--
"Christ, what an imagination I've got." - Shalmaneser
11 matches
Mail list logo
