¬¬¬¬¬¬¬¬¬ [EMAIL PROTECTED]@â ¬¬¬¬¬¬¬¬
ªÂ¤¢ ÌqÌã´í說ªªªªªªªªªªªªªªª
[EMAIL PROTECTED]@[EMAIL PROTECTED]@fB[vÅtFeBbV
Èéæ·è¾³ñô
cccccccccccccccccccc
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTE
We have managed to make a bootable GNU cd!
Excellent news! congrats!
--
José E. Marchesi <[EMAIL PROTECTED]>
GNU No es Unix! http://www.gnu.org
GNU España http://es.gnu.org
___
Bug-h
This is a real questionable interface to add. "Number of send rights" is
really not an appropriate notion for the Hurd protocol object abstraction.
It doesn't even necessarily mean very much useful even in a Mach-based
context. It may not be really accurate to say anything other than yes/no
to "a
Roland McGrath wrote:
This is a real questionable interface to add. "Number of send rights" is
really not an appropriate notion for the Hurd protocol object abstraction.
It doesn't even necessarily mean very much useful even in a Mach-based
context. It may not be really accurate to say anything o
> our reference is not a reference to the shared memory object, but to the
> filenode.
> So we need three states: no senders, one, or many (the "one" is useful
> if we want to know
> if we are the only mapper).
>
> This is as much as we need to make users of nattach in SysV SHM happy.
> We know
> #define S_IMAPPED0001 /* Might be mmap'd. */
> #define S_IMAPPEDM 0002 /* Might be mmap'd more than once. */
Actually, for compatibility purposes it's better to reverse the sense of
those bits. i.e.
#define S_IMMAP00001 /* Definitely no mmap's to this.
Roland McGrath wrote:
#define S_IMAPPED0001 /* Might be mmap'd. */
#define S_IMAPPEDM 0002 /* Might be mmap'd more than once. */
Actually, for compatibility purposes it's better to reverse the sense of
those bits. i.e.
#define S_IMMAP00001 /* Definitely
Usted
puede Pensionarse...
... ahora y
disfrutar de una Renta Vitalicia Mensual
Tanto
en el caso que siga trabajando y desee
tener un complemento de su
ingreso
como en el caso que no esté trabajando y no quiera esperar cumplir la