On Sun, Apr 14, 2002 at 07:22:33PM +0200, Jeroen Ruigrok/asmodai wrote:
> -On [20020414 19:14], Matthias Schuendehuette ([EMAIL PROTECTED]) wrote:
> >make: don't know how to make neqn. Stop
> >*** Error code 2
>
> I think David O`Brien fixed this by backing out a commit to make.
>
> In general,
On Sun, Apr 14, 2002 at 07:22:33PM +0200, Jeroen Ruigrok/asmodai wrote:
> -On [20020414 19:14], Matthias Schuendehuette ([EMAIL PROTECTED]) wrote:
> >make: don't know how to make neqn. Stop
> >*** Error code 2
>
> I think David O`Brien fixed this by backing out a commit to make.
I don't think he
-On [20020414 19:14], Matthias Schuendehuette ([EMAIL PROTECTED]) wrote:
>make: don't know how to make neqn. Stop
>*** Error code 2
I think David O`Brien fixed this by backing out a commit to make.
In general, wait a couple of hours or a day before reporting a failure,
since chances are good it
On Sunday 25 March 2001 13:53, Marc van Woerkom wrote:
> > i4b is an ethernet interface, how do you think PPP/HDLC works ? The
> > interface is registered with the networking stack, just like a "real"
> > networking card is. This make the ether device mandatory.
>
> Hi Gary!
>
> I simply lack know
> i4b is an ethernet interface, how do you think PPP/HDLC works ? The
> interface is registered with the networking stack, just like a "real"
> networking card is. This make the ether device mandatory.
Hi Gary!
I simply lack knowledge of how network devices are organized.
It might have been pos
On Sunday 25 March 2001 00:11, Marc van Woerkom wrote:
> > >Ok, I did an ediff against NOTES. Perhaps it was the "1" argument to
> > >
> > >device loop1 #Network loopback device
> > >
> > >that was missing. I'll try again.
> >
> > Hmmm Seems odd. If you get a re
> >Ok, I did an ediff against NOTES. Perhaps it was the "1" argument to
>
> >device loop1 #Network loopback device
>
> >that was missing. I'll try again.
>
> Hmmm Seems odd. If you get a recurrence, you might want to share a
> diff between GENERIC and what
