> But that foregoes the point that the code is far more complex and harder to
> make 'obviously correct', a concept that *does* translate well to userspace.
One point is that 'obviously correct' is much harder to 'prove' for
threads (or processes with shared memory) than you might think.
With a
But that foregoes the point that the code is far more complex and harder to
make 'obviously correct', a concept that *does* translate well to userspace.
One point is that 'obviously correct' is much harder to 'prove' for
threads (or processes with shared memory) than you might think.
With a
On Fri, 9 Feb 2001, Miles Lane wrote:
> Helge Hafting wrote:
> > christophe barbe wrote:
> >> Moreover there is no need to be ignorant. With LPP, messages are displayed during
>the boot process and if something goes wrong an little picture inform you. And you
>can switch to the classic console
On Fri, 9 Feb 2001, Miles Lane wrote:
Helge Hafting wrote:
christophe barbe wrote:
Moreover there is no need to be ignorant. With LPP, messages are displayed during
the boot process and if something goes wrong an little picture inform you. And you
can switch to the classic console when you
> however, this brings up an interesting question: what happens if two disks
> (presumably from two different machines) have the same disk label? what
> happens then? for instance, i have several linux machines both at my
> workplace and my home. if for some reason one of these machines dies due
however, this brings up an interesting question: what happens if two disks
(presumably from two different machines) have the same disk label? what
happens then? for instance, i have several linux machines both at my
workplace and my home. if for some reason one of these machines dies due
to
On Sat, 21 Oct 2000, Dennis wrote:
> At 06:43 PM 10/20/2000, [EMAIL PROTECTED] wrote:
>
> >I get this when DMA is enabled:
> >
> >Oct 20 15:39:07 cr753963-a kernel: hdb: timeout waiting for DMA
> >Oct 20 15:39:07 cr753963-a kernel: hdb: irq timeout: status=0x6e {
> >DriveReady DeviceFault
On Sat, 21 Oct 2000, Dennis wrote:
At 06:43 PM 10/20/2000, [EMAIL PROTECTED] wrote:
I get this when DMA is enabled:
Oct 20 15:39:07 cr753963-a kernel: hdb: timeout waiting for DMA
Oct 20 15:39:07 cr753963-a kernel: hdb: irq timeout: status=0x6e {
DriveReady DeviceFault DataRequest
> > But in the end, maybe the rule to only use hand power makes sense. Not
> > because hand-power is _better_. But because it brings in the kind of
> > people who love to work with their hands, who love to _feel_ the wood with
> > their fingers, and because of that their holes are not always
But in the end, maybe the rule to only use hand power makes sense. Not
because hand-power is _better_. But because it brings in the kind of
people who love to work with their hands, who love to _feel_ the wood with
their fingers, and because of that their holes are not always perfectly
On Wed, 6 Sep 2000, Dan Hollis wrote:
> On Wed, 6 Sep 2000, Alan Cox wrote:
> > For things like driver debugging its the only way to work. Hardware simply does
> > not work like the manual says and no amount of Zen contemplation will ever
> > make you at one with a 3c905B ethernet card.
>
>
On Wed, 6 Sep 2000, Dan Hollis wrote:
On Wed, 6 Sep 2000, Alan Cox wrote:
For things like driver debugging its the only way to work. Hardware simply does
not work like the manual says and no amount of Zen contemplation will ever
make you at one with a 3c905B ethernet card.
This is
12 matches
Mail list logo