Re: ping error

1999-08-31 Thread John Summerfield
> Levente Farkas wrote: > > > Again, the ping in the package netkit-base-0.10-29.src.rpm from the Red > > > Hat 6.0 distribution does not have the "wrong data byte #8" problem on > > > i386. > > > > have you heard about : > > ftp://ftp.redhat.com/pub/redhat/updates/6.0/i386/netkit-base-0.10-31.i

Unidentified subject!

1999-08-31 Thread kifox
I'm running redhat 6.0 with the kernel that came with it and I'm running into the problem that when I run Midnight Commander 4.5.30 from the shell prompt as either a regular user or as root, mc refuses to respond to the mouse (a belkin 3-button PS/2 compatable mouse) when I either try selecting s

Re: Serial consoles

1999-08-31 Thread H. Peter Anvin
"Edward S. Marshall" wrote: > > On Thu, 26 Aug 1999, Edward S. Marshall wrote: > > Lilo still comes up via the normal console (the keyboard is disconnected > > at this point, but I'd prefer to leave a video card in there as a "just in > > case"); it's completely uncontrollable from the serial con

Re: Serial consoles

1999-08-31 Thread Edward S. Marshall
On Thu, 26 Aug 1999, Edward S. Marshall wrote: > Lilo still comes up via the normal console (the keyboard is disconnected > at this point, but I'd prefer to leave a video card in there as a "just in > case"); it's completely uncontrollable from the serial console. Noone is currently doing this th

Re: unzip-5.40-2: broken spec file patch

1999-08-31 Thread Andrew E. Mileski
A full night of sleep always helps. Here is a better patch that doesn't get rid of zipgrep. -- Andrew E. Mileski - Software Engineer Rebel.com http://www.rebel.com/ --- unzip.spec.orig Mon Nov 30 12:29:39 1998 +++ unzip.spec Tue Aug 31 10:36:28 1999 @@ -1,6 +1,6 @@ %define name unzip %

Re: updboots and lack of documentation

1999-08-31 Thread Matt Wilson
On Tue, Aug 31, 1999 at 04:11:06PM +1000, Kevin Waterson wrote: > Matt Wilson wrote: > > > > > Could you mail me ([EMAIL PROTECTED]) the results of > > sh -x ./updboots /root/Canon /root/Canon/Canon/RPMS 2.2.15-22 > > I seems the problem here was between the keyboard and the chair. > I had run t