There are probably a few weird hacks that rely on true port polymorphism.
But most of the uses can be described as interface subtyping (e.g. file_t
and socket_t are subtypes of io_t).
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mail
The reason for the types in .defs files is for intran/outtran. I would
tend toward using the specific types generally, because that has more of a
chance to be mapped source-compatibly in some other RPC system.
___
Bug-hurd mailing list
[EMAIL PROTECTED
I took a quick look at nbd and it's so simple that I just implemented the
client side for the Hurd. That is, I've added an "nbd" store type to libstore.
So to use it do e.g.:
settrans /dev/nb0 /hurd/storeio -Tnbd hostname:1234
to connect to TCP port 1234 on "hostname". That gives the s
On Fri, Sep 28, 2001 at 01:23:25AM +0200, Farid Hajji wrote:
> * are the more specific types at least _consistently_ used?
> I doubt this is the case: a lot of files simply fall back to
> mach_port_t later
> * are they really needed for architectural reasons, or, more
> precisely,
Hi Marcus,
> I saw that the defs file have nice specific types like ipc_space_t and
> mach_port_name_t, but the C header files almost all have mach_port_t for
> them. In the Hurd, we have a typedef for each of these types and keep
> them in the header. We even use task_t in proc etc.
>
> I am
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> the default pager in serverboot (also used by mach-defpager) is still using
> the legacy interfaces memory_object_set_attributes() and
> memory_object_data_write() to set the ready attribute and receive data from
> the kernel. The newer documentatio
Package: gnumach
gnumach device_open is not paranoid enough about the device name. I haven't
tried it, but I think that having 128 non-digits with no trailing zero will
make gnumach run past the buffer in dev_name_lookup.
Maybe not worth fixing for gnumach (esp as opening a device requires the
Thomas will have to pass judgment on this.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
Hi,
I saw that the defs file have nice specific types like ipc_space_t and
mach_port_name_t, but the C header files almost all have mach_port_t for
them. In the Hurd, we have a typedef for each of these types and keep
them in the header. We even use task_t in proc etc.
I am now using mach_port
Hi,
the default pager in serverboot (also used by mach-defpager) is still using
the legacy interfaces memory_object_set_attributes() and
memory_object_data_write() to set the ready attribute and receive data from
the kernel. The newer documentation suggests that memory_object_ready()
and memory_
> "DW" == Daniel Wagner <[EMAIL PROTECTED]> writes:
DW> Well that's only one side of the truth. AMD had in those K6
DW> series an very fast loop optimation. It was so fast, that
DW> Windows couldn't boot correctly, because they did also
DW> counting down a counter. The result
11 matches
Mail list logo
