Le vendredi 10 mars 2006 à 03:22 +0100, Michael Banck a écrit :
> some years ago, Jeff Bailey worked on moving the Hurd build system to
> automake. Some people lately got interested in this again, so I got the
> patches from him and am posting them here for people to work on with
> Jeff's consent.
4032 M
Attention to the citizens of United Kingdom!
We have a great job opportunity for you: you get a chance to make the profit of
3000 GBP every month. American company Independent Business Solutions works
already for more then two years on the financ
Worldsentiment.c
om users are voting and discussing what constitutes cheating and
whether Congress acted appropriately when they blocked the Dubai Port Deal.
Also, a there is a new Senti-Match feature when you sign up for free on
WordSentiment.
Senti-Match allows you to hook up with other wor
Hi,
Thomas Schwinge, le Sun 05 Mar 2006 10:34:44 -0500, a écrit :
> On Sun, Jan 08, 2006 at 06:50:40PM +0100, Samuel Thibault wrote:
> > device "iopl" has a bunch of registers: speaker, game port, sound,
> > printer, video, and gives read-only access to any i/o port.
>
> My vote is to remove the
I've been unsubscribed to bug-hurd for several years, but this week I
suddenly started getting messages again. Trying to unsubscribe again
at...
http://mail.gnu.org/mailman/listinfo/bug-hurd
...hasn't seem to have done the job.
Advice?
Greg Buchholz
P.S. FWIW, here's a copy of the header for
Hi,
some years ago, Jeff Bailey worked on moving the Hurd build system to
automake. Some people lately got interested in this again, so I got the
patches from him and am posting them here for people to work on with
Jeff's consent. They still applied fine (or I resolved some conflicts,
don't reme
__БЕЗЛИMИТНЫЕ ТАРИФЫ-(495) 74l 02 OlMТСфедеральный 97
$.* БиЛайнфедеральный MТСпрямой116
$.* БиЛайнпрямой (*
цена указанна без учета НДС)-КОРПОРАТИВНЫЕ ТАРИФЫ-Подключение от 30
$. абонентская плата 0 $Стоимость
___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-hurd
Greetings,
It appears that this mailing list, bug-hurd@gnu.org, (among many others),
has no known owner/moderator, and accepts mail from non-subscribers.
The result is passing through of lots of spam.
So we need to do something. I'm writing to get input on the best thing
to do. Please reply to
TO:人事部负责人：
光大会展中心 综合场: 3/113/183/25 （每周六）
主推1：2006年第二届 IT 汽车 机械 电子 通讯 专业特设场 3/12 （周日）
主推2：2006年第二届 物流 贸易 营销 大型人才交流会3/26 （周日）
主推3：长三角 汽车及先进制造业 中高级人才交流会 3/11（周六）
特别推荐：全国第四届房地产建筑、装潢中高级人才专场招聘会 3/25
场馆：上海展览中心 （ 延
> Then why splitting ioperm()'s work into two i386_io_perm_create()
> and i386_io_perm_modify() calls if people should use ioperm()
> rather than Mach calls? Couldn't gnumach just provide an
> i386_io_perm_modify(ipc_port_t master_port, io_port_t from,
> io_port_t to, boolean_t enable) call instead
Hi,
It's almost only aesthetic but Makefile.in 's variable topfiles lacks
Makerules.in entry. This creates problems with 'make dist'.
2006-03-03 Gianluca Guida <[EMAIL PROTECTED]>
* Makefile.in (topfiles): Add 'Makerules.in'.
--- vanilla/gnumach//Makefile.in2006-02-20 22:17:23
Roland McGrath, le Fri 10 Mar 2006 16:04:05 -0800, a écrit :
> > Then why splitting ioperm()'s work into two i386_io_perm_create()
> > and i386_io_perm_modify() calls
>
> More concretely, it separates the general permission from the specific
> permission, making the latter a transferrable capabili
In the real world, any user of an io port capability is going to know
exactly what ports it's good for, because it has to actually use the ports.
Your example does not seem too likely to me.
Anyway, I'm not saying the interface I wrote is necessarily wonderul.
glibc already uses it for ioperm, b
On Fri, Mar 10, 2006 at 12:31:19PM -0800, Greg Buchholz wrote:
> I've been unsubscribed to bug-hurd for several years, but this week I
> suddenly started getting messages again. Trying to unsubscribe again
> at...
The same happened to me.
Cheers,
Michael
--
http://www.worldforge.org/
___
15 matches
Mail list logo
