> The original Hurdish ancestor only has to remain alive for long enough
> for proc to establish its record and copy the owner ID. If the kernel
> actively notifies proc as soon as the process is created with this
> information, we can be guaranteed it gets captured and recorded.
I have been ass
Jeff Bailey <[EMAIL PROTECTED]> writes:
> If we're coping with a kernel panic, can we count on a kernel
> parameter still being in tact?
Yes. Just set a global variable based on the kernel parameter at boot
time, and then only look at the global variable.
__
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> Ah, okay. Is there a special reason not to print it? BogoMIPS has a
> tradition of being the worst benchmark in the world, and we can point at it
> and say: "see? The Hurd has just as many BogoMIPS as Linux." ;)
We shouldn't print it because the k
On Wed, May 16, 2001 at 10:28:32PM +, Adam Olsen wrote:
> My thinking was that a hltonpanic=1 kernel argument would be good.
> The advantage over a configure option is that it doesn't require a
> recompile to use.
If we're coping with a kernel panic, can we count on a kernel
parameter still
Title:
¢Ä ¿À´ÃÀÇ À¯¸Ó ¢Å
¡á°ú½Ã¿åA girl
got an engagement ring, and would seize every opportunity for calling attention to it. In a
group with girl friends no one noticed it. Finally when herfriends
were sitting around talking, she got up suddenly and said, "It's awfully hot
in he
From: Marcus Brinkmann <[EMAIL PROTECTED]>
Subject: Re: page fault in mach_msg_trap
Date: Thu, 17 May 2001 09:41:12 +0200
> Ah, okay. Is there a special reason not to print it?
I don't remember well, but I think it might be because the function
"printk" is not functional at that stage yet in GN
On Thu, May 17, 2001 at 03:32:49PM +0900, OKUJI Yoshinori wrote:
> From: Marcus Brinkmann <[EMAIL PROTECTED]>
> Subject: Re: page fault in mach_msg_trap
> Date: Wed, 16 May 2001 23:57:41 +0200
>
> > We don't have BogoMIPS calulcation in GNU Mach.
>
> IIRC, I included the calculation in GNU Mach.
