After a long absence, I was just about to get into my new joystick drivers
when it now fails to compile. What's the recommended change?
Stephen
--
The views expressed above are not those of PGS Tensor.
"We've heard that a million monkeys at a million keyboards could produce
I recently purchased a Intel Pro 100+ Server Adapter
for my FreeBSD machine (3.1), but I can't find any information if it is
supported,
or not... I'm also not sure which driver I would use for it.. Intel's
site, and the FreeBSD
site have no information regarding this adaptor's compatibili
The machine itself is back up. Services are being restored
currently.
The machine has now a 12GB vinum filesystem for /ctm and
should not run out of space so fast again.
--
Regards, Ulf.
-
Ulf Zimmermann, 1525 Pacific Ave., Al
On 24 Jun, Nick Hibma wrote:
>
> The logfile for CRON is in the wrong place IMHO. It's in /var/cron/log.
> The FreeBSD style is to put those things in /var/log (/var/log/cron).
>
> Anyone any opinions on this? Which scripts depend on that location?
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr
1) a cross-reference to http://www.freebsd.org/FAQ/FAQ243.html#246
in the docs in /usr/src/release is useful!
how about adding one to the Makefile
2) you can't always do a make release without 1:1 agreement between
your runtime state and the CVS and /usr/src repositaries being use
On Fri, 25 Jun 1999, Vladimir Kushnir wrote:
> Hello,
> Sorry for being annoying but is there still anything wrong with CTM
> generation? The last src-cur delta was from 8th of June.
I know, we're waiting until Ulf gets the new disk up and spinning. It's
taking some time, but I think he's havi
>*apologies*. However, many Award BIOSes (all?) do not allow you to turn
>off UDMA.
All Award BIOSes that I have (for 5 working systems) support it if the
hardware supports it (2 systems).
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of th
On 24 Jun 1999, Dag-Erling Smorgrav wrote:
> "Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> > You misunderstand. I _cannot_ disable UDMA in my BIOS.
>
> I know. The mail you answered wasn't addressed to you.
*apologies*. However, many Award BIOSes (all?) do not allow you to turn
off UDMA.
>
I'm working on a fix to PR kern/12265 (panic when trying to RTM_GET
the default route while there is none).
The problem is that in route_output(), in that case, rn_lookup()
returns the root node of the radix table (he got it from rn_match()),
while the code expects NULL or a node with an AF_INET
Hello,
Sorry for being annoying but is there still anything wrong with CTM
generation? The last src-cur delta was from 8th of June.
Regards,
Vladimir
===|===
Vladimir Kushnir |
[EMAIL PROTECTED], |Powered by FreeBSD
[EMAIL PR
"Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> You misunderstand. I _cannot_ disable UDMA in my BIOS.
I know. The mail you answered wasn't addressed to you.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in th
You misunderstand. I _cannot_ disable UDMA in my BIOS.
Brian Fundakowski Feldman _ __ ___ ___ ___ ___
[EMAIL PROTECTED] _ __ ___ | _ ) __| \
FreeBSD: The Power to Serve!_ __ | _ \._ \ |) |
http://www.FreeBSD.org/ _ |___/___/___/
Bruce Evans <[EMAIL PROTECTED]> writes:
> >controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff
> >
> >Will enable DMA mode with the old driver. It doesn't support UDMA on
> >all chipsets (e.g. ALI), and in some cases may give very poor
>
> Not e.g. ALI (Aladdin IV/V) (unless the ALI suppo
On Fri, 25 Jun 1999, Bruce Evans wrote:
> >controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff
> >
> >Will enable DMA mode with the old driver. It doesn't support UDMA on
> >all chipsets (e.g. ALI), and in some cases may give very poor
>
> Not e.g. ALI (Aladdin IV/V) (unless the ALI supp
>controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff
>
>Will enable DMA mode with the old driver. It doesn't support UDMA on
>all chipsets (e.g. ALI), and in some cases may give very poor
Not e.g. ALI (Aladdin IV/V) (unless the ALI support is broken).
>performance when using UDMA disks,
It seems Jordan K. Hubbard wrote:
> > Are there any plans to port FreeBSD to the IA-64 architecture when it comes
> > out? The docs have recently been released
>
> There have been plans to do this for as long as Intel has had plans to
> make the processor. :)
>
> The question will simply come d
> Are there any plans to port FreeBSD to the IA-64 architecture when it comes
> out? The docs have recently been released
There have been plans to do this for as long as Intel has had plans to
make the processor. :)
The question will simply come down to hardware availability and
documentation.
On 24 Jun 1999, Dag-Erling Smorgrav wrote:
> "Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> > I didn't mean that mode 2 was special, but Ultra DMA mode 2 in its entirety being
> > very nice :) The old driver never did any form of DMA for me, much less UDMA, so
> > I'm very glad to have the ATA
The logfile for CRON is in the wrong place IMHO. It's in /var/cron/log.
The FreeBSD style is to put those things in /var/log (/var/log/cron).
Anyone any opinions on this? Which scripts depend on that location?
Nick
http://www.freebsd.org/cgi/query-pr.cgi?pr=7682
To Unsubscribe: send mail t
Are there any plans to port FreeBSD to the IA-64 architecture when it comes
out? The docs have recently been released
http://developer.intel.com/design/ia64/architecture.htm
so I was wondering if anyone had a chance to look at the stuff.
It'll be a shame to see FreeBSD for Intel go with the la
Make sure you install the include files.
In message <[EMAIL PROTECTED]>, Bruce Burden write
s:
>
> Hi all,
>
> Has this problem been fixed?
>
>===> sbin/ifconfig
>cc -O -pipe -DUSE_IF_MEDIA -DUSE_VLANS -DNS -Wall -Wmissing-prototypes -Wcast-qual
>-Wwrite-strings -Wnested-externs -I.. -
Dag-Erling Smorgrav wrote:
>
> Doug <[EMAIL PROTECTED]> writes:
> > On Wed, 23 Jun 1999, Brian F. Feldman wrote:
> > > A device name isn't necessarily the same as a device node, you know.
> > Actually I do know that, but I've never come across a situation in
> > freebsd where I would call s
Hi all,
Has this problem been fixed?
===> sbin/ifconfig
cc -O -pipe -DUSE_IF_MEDIA -DUSE_VLANS -DNS -Wall -Wmissing-prototypes -Wcast-qual
-Wwrite-strings -Wnested-externs -I.. -c /omni/usr/src/sbin/ifconfig/ifconfig.c
/omni/usr/src/sbin/ifconfig/ifconfig.c: In function `status':
/
Hi Ed,
>
> cc -nostdinc -O -pipe
> -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes
> -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp
> -I/usr/obj/usr/src/tmp/usr/include -static -o dhclient clparse.o
> dhclient.o alloc.o bpf.o conflex.o convert.o dispatch.o errwarn.o hash.o
> icm
"Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> I didn't mean that mode 2 was special, but Ultra DMA mode 2 in its entirety being
> very nice :) The old driver never did any form of DMA for me, much less UDMA, so
> I'm very glad to have the ATA drivers.
controller wdc0 at isa? port IO_WD1 irq 14
Doug <[EMAIL PROTECTED]> writes:
> On Wed, 23 Jun 1999, Brian F. Feldman wrote:
> > A device name isn't necessarily the same as a device node, you know.
> Actually I do know that, but I've never come across a situation in
> freebsd where I would call something one thing in my kernel config f
On Wed, 23 Jun 1999 14:16:23 MST, Doug wrote:
> If you are saying that I ought to include atapicd in my kernel config
> and use the acdN device node, that's all I need to know, but it does
> bring up the question of why the two things are different. It seems
> like unecessary obfuscation to me.
That fixed it. Thanks!
Tim
On Thu, Jun 24, 1999 at 04:44:50PM +0900, Kazutaka YOKOTA wrote:
> >>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried
> >every variation of the kernel I can think of, including GENERIC, and same
> >thing. I finally changed to vt0 and it b
>>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried
>every variation of the kernel I can think of, including GENERIC, and same
>thing. I finally changed to vt0 and it booted up fine.
A bug was found earlier today in syscons_isa.c. Apply the following
patch to /sys/isa/s
Grrr, forgot the trap information:
>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried
every variation of the kernel I can think of, including GENERIC, and same
thing. I finally changed to vt0 and it booted up fine.
I am using the standard sio0 config with the 0x10 flag a
>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried
every variation of the kernel I can think of, including GENERIC, and same
thing. I finally changed to vt0 and it booted up fine.
I am using the standard sio0 config with the 0x10 flag and a /boot.config
file with "-h".
C
31 matches
Mail list logo
