Moved to bug-hurd, nothing to do with Debian.
settrans pty?? /hurd/term /dev/pty?? pty-master /dev/tty??
settrans tty?? /hurd/term /dev/tty?? pty-slave /dev/pty??
Is this necessary?
If you wish to use virtual consoles, screen etc, yes. If the output
is annoying on the eyes, one could a
- Fork is a hard cost operation.
To get an idea how hard fork() is for us, Gianluca did a simple test,
on GNU/Hurd he got 312 forks/second, and on the same machine but in
GNU/Linux, he got 8170 forks/second.
___
Bug-hurd mailing list
Bug-hurd@gnu.or
I think this is a implementation problem, there is no way to fix
it. Maybe this can be fixed rebuilding all Mach
infrastructure. Can anyone confirm that?
The problems with Mach can be fixed by redesigning the way how IPC's
works. Rebuilding the whole Mach infrastructure is a possiblity,
Sorry for the late response.
Can anyone explain why that overhead happen in Mach?
The large overhead is mostly related to how the Hurd uses Mach.
Running a single-user server system gets you quite decent performance,
but we have a multi-sever design, where the number of context
switches, and I
settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a 192.168.83.39
-g 192.168.83.38 -m 255.255.252.0
Double check your netmask, it should probobly be 255.255.255.0.
And why socket 2 not 1? I have only one ethernet card.
/servers/socket/1 (or 2) has nothing to do with ethernet car
[moving to bug-hurd, more suitable there]
> [EMAIL PROTECTED]:~$ showtrans -t /hurd/*
> /hurd/ext2fs: /dev/hd1s1
> /hurd/ext2fs.static: /dev/hd1s1
You can still save it, settrans -fgap on each (/hurd/ext2fs, etc).
Hope you didn't reboot though.
Maybe you're the first one to make this
