Save up to 80% on Dental Services!
Plan Includes Free Prescription, Vision and Chiropractic Plan
For only $11.95 Per Month for an individual membership $19.95
a Month for the entire Household.
Please Email to: [EMAIL PROTECTED] stating More Info in the
subject.
Thank You
Frank
To
> Personally, I find it very appealing to be able to perform *arbitrary*
> i/o or i/o-like operations by sending asyncronous messages, and then
> being able to wait on a collection of reply ports until one of the
> operations returns or times out. I guess one reason I like that way of
> operation
Farid Hajji <[EMAIL PROTECTED]> writes:
> Absolutely. No-senders/dead port notification is one of the hardest parts
> to port to a non-mach kernel, like L4.
Please don't talk about these as if they were the same thing. Dead
name notifications are not very important. No senders notifications
*a
Farid Hajji <[EMAIL PROTECTED]> writes:
> Basically, it proved difficult to emulate the complete Mach API. If you
> want to implement L4Mach, it will most likely provide just a subset of
> Mach, so that we can get the Hurd up and running (in a first step).
Making the Hurd run on L4 should be don
> The question was: How do I allocate memory? I'm asking this, because
> there might be a difficulty at this point. We can not use kfree to free
> some memory, so kalloc would fail also, right?
It's the context that's not clear. There are numerous kinds of memory
allocation. The only kinds that
> I'm not really following your question. If you are not hitting this panic
> now, then let's not worry about it until you do.
The question was: How do I allocate memory? I'm asking this, because
there might be a difficulty at this point. We can not use kfree to free
some memory, so kalloc would
Farid Hajji <[EMAIL PROTECTED]> writes:
> * IPC should be only used in stubs during an RPC.
>
> This is very important. Most IPC in the Hurd occurs during
> an RPC call. Most RPC calls _can_ be done in a completely
> synchroneous manner. By sticking to this requirement, it
> wo
