On Wed, Jan 05, 2000 at 08:47:07PM -0800, David Dawes wrote:
>I've just been doing a build test of the pre-3.3.6 version of
>XFree86 on a recent FreeBSD 4.0-current, and I've noticed that
>/usr/libexec/cpp doesn't predefine the symbol __FreeBSD__. imake
>uses /usr/libe
DEFAULT_CPP "/usr/bin/cpp"
#endif
#if defined(__sgi) && defined(__ANSI_CPP__)
#define USE_CC_E
David
--
David Dawes Email: [EMAIL PROTECTED]
Co-founder/President, The XFree86 Project, Inc Phone: +1 570 775 9502
http://www.xfree86.org/
On Thu, May 20, 1999 at 07:23:49PM +0200, Jean-Marc Zucconi wrote:
>>>>>> David Dawes writes:
>
> > IMHO the problem is in the joystick driver and in your assumptions. By
> > configuring the joystick in your Xserver config file, you're giving the
> >
On Wed, May 19, 1999 at 11:37:51PM +0930, Matthew Thyer wrote:
>The big problem is that the silo overflows continue after I have
>returned the pointer to the mouse (with "xsetpointer pointer").
>
>This should close the joystick device shouldn't it ?
No. I've had a look through some of the XInput
On Wed, May 19, 1999 at 01:20:01AM +0930, Matthew Thyer wrote:
>I have confirmed that the problem occurs if I just do:
>
> xsetpointer Joystick
> sleep 1
> xsetpointer pointer
>
>So M.A.M.E. is unrelated to the problem as Bruce Evans would suggest.
>
>So the problem appears to be with XFree86 no
On Sun, May 09, 1999 at 12:39:56PM +0930, Matthew Thyer wrote:
>*** STOP PRESS *** I have just confirmed that restarting the X server
> is enough to fix the problem. So my apologies to Bruce, -CURRENT
> and the whole FreeBSD community in general for blaming sio.
>
>For the b
On Mon, May 03, 1999 at 08:57:14PM -0400, Brian Feldman wrote:
>On Tue, 4 May 1999, Matthew Thyer wrote:
>
>> My usermode ppp works fine normally as I can quite happily download
>> 4 things at once without a single silo overflow (as I did last night)
>> even when there is lots of disk activity or X
On Thu, Apr 29, 1999 at 12:48:58AM +0930, Mark Newton wrote:
>
>Does anyone know what has happened to cvsup.au.freebsd.org?
I think a disk has died. I'm on leave for a couple of weeks, and haven't
had a chance to go into work to check up on it properly.
David
To Unsubscribe: send mail to major
On Thu, Apr 22, 1999 at 02:01:35AM -0700, Amancio Hasty wrote:
>Just a kind reminder we can unplug and plug a usb mouse as
>well as a usb keyboard currently we have a small problem with
>moused that it does not attempt to gain access of the mouse if there
>is a usb disconnect / connect sequence.
On Thu, Apr 22, 1999 at 10:18:13AM +0200, Nick Hibma wrote:
>I've heard of no one trying, but I (we!) would love to hear whether you
>get this to work.
>
>There is not problem is using two keyboards at the same time, but I am
>not sure whether X can already handle more than one keyboard attached t
On Wed, Feb 03, 1999 at 10:27:15PM -0600, Chris Csanady wrote:
>
>>On Wed, Feb 03, 1999 at 09:53:05PM -0600, Chris Csanady wrote:
>>>I unfortunately have a lot of data to type in, and to my surprise
>>>the keypad is unuseable in vi. It doesn't even work in vim. Thank
>>>god it works on Irix--I th
On Wed, Feb 03, 1999 at 09:53:05PM -0600, Chris Csanady wrote:
>I unfortunately have a lot of data to type in, and to my surprise
>the keypad is unuseable in vi. It doesn't even work in vim. Thank
>god it works on Irix--I thought I would be using ee.
>
>Anyways, here is what happens when I type t
On Fri, Jan 22, 1999 at 11:54:59PM +1100, Bruce Evans wrote:
>>I've been playing with a Promise FastTrack RAID (IDE) controller with
>>3.0-current as of yesterday. Although it is recognised in the PCI bus
>>probe as a "Promise Ultra/33" (it has the same vendor/chip ID as the
>>non-RAID card), the
On Thu, Jan 21, 1999 at 02:06:22PM +0100, Søren Schmidt wrote:
>It seems David Dawes wrote:
>>
>> That didn't improve things, but with the patch I got lots of messages
>> like the following (for a disk attached to the onboard PIIX4):
>>
>> wd1: DMA failu
On Thu, Jan 21, 1999 at 01:21:03PM +0100, Søren Schmidt wrote:
>It seems David Dawes wrote:
>> I've been playing with a Promise FastTrack RAID (IDE) controller with
>> 3.0-current as of yesterday. Although it is recognised in the PCI bus
>> probe as a "Promise Ul
I've been playing with a Promise FastTrack RAID (IDE) controller with
3.0-current as of yesterday. Although it is recognised in the PCI bus
probe as a "Promise Ultra/33" (it has the same vendor/chip ID as the
non-RAID card), the probes in i386/isa/wd.c fail. I added some debugging
printfs to the
16 matches
Mail list logo
