, but probably more trouble then it's worth. It's
only for those occasional huge distfiles where it really matters
(currently, the 77M games/vegastrike snatched from a PR.)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Dave
.
Thanks for these hints, I'll try them ASAP,
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us... - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
- sys/kern/init_main.c:217
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us... - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I'm quite certain this was discussed recently, but I can't find it in
the mailing list archives.
I'm getting a few fxp0: device timeout on my supermicro 6010H (dual
1GHz PIII with onboard fxp). Was this resolved?
thanks,
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also
wiif_wi 2 network Lucent WaveLAN/IEEE 802.11 PCMCIA card
- wxif_wx 2 network Intel Gigabit Ethernet (82452) card
xlif_xl 2 network 3COM 3c90x / 3c90xB PCI ethernet card
--- 54,57
dave c
--
Dave Cornejo @ Dogwood Media, Fremont
/release.
*** Error code 1
Stop in /usr/src/release.
*** Error code 1
Stop in /usr/src/release.
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us... - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
apparent side effects.
The corrupted line shows up in many different places and users, and
the exact contents vary, but there's always a (csh) at the end.
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us... - Xochi
To Unsubscribe
more
info.
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us... - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
you wrote:
And just for the record: PERL is right out (of space) for this purpose...
as I assume emacs would be too? :-(
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us... - Xochi
To Unsubscribe: send mail to [EMAIL
Enabled
da1: 17501MB (35843671 512 byte sectors: 255H 63S/T 2231C)
Mounting root from ufs:/dev/da0s1a
SMP: AP CPU #1 Launched!
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us... - Xochi
To Unsubscribe: send mail to [EMAIL
been introduced
when support was added?
thanks,
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us... - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
that (provided nothing is broken).
thanks,
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us... - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
for your help!
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us... - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
to a SMP kernel from April 15th - using a GENERIC
kernel with SMP enabled it exhibits the same problem. Will work my
way back to -stable and see if anything changes...
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us
a routine to start
tracing), or is there anything I can do that might get more info for
the people that know what is going on?
thanks!
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us... - Xochi
To Unsubscribe: send mail
NMI active-hiedge0 0:A2551
===
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us... - Xochi
to be normal process rescheduling (?) which is
mostly idle task time...
Do think there's any use to rolling my source tree back a ways and
compiling a kernel?
thanks,
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
There aren't any monkeys chasing us
Cornejo -
From: Dave Cornejo [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Subject: SuperMicro 6010H SCSI Problems
To: [EMAIL PROTECTED]
Date: Sun, 17 Jun 2001 00:20:47 -0700 (PDT)
X-Mailer: ELM [version 2.4ME+ PL88 (25)]
I finally got a make release done (a heartfelt thanks to all
retrieving revision 1.4
diff -u -r1.4 Makefile
--- Makefile 1999/10/03 02:43:20 1.4
+++ Makefile 2000/10/31 18:06:34
@@ -2,5 +2,6 @@
LIB= gcc_r
CFLAGS+=-D_PTHREADS
+CFLAGS+=-D'__GTHREAD_MUTEX_INIT_FUNCTION(m)=pthread_mutex_init(m, NULL)'
.include "../libgcc/Makefile"
libexec/ld-elf.so.1
(gdb) quit
The program is running. Exit anyway? (y or n) y
juneau#
The system is a dual PIII-600 w/512M RAM if that helps...
--
Dave Cornejo @ Dogwood Media, Fremont, California
"There aren't any monkeys chasing us..." - Xochi
To Unsubscribe: send mail to [EMAIL PROT
PROTECTED]
the latest fetch sends this:
USER [EMAIL PROTECTED]@21
which fwtk apparently interprets as username "[EMAIL PROTECTED]"
at IP address "0.0.0.21"
What is incorrect here? Should FWTK understand this or is fetch
wrong?
dave
--
Dave Cornejo @ Dogw
. If you want v6, run current, don't make the people
waiting for 4.0 wait longer. This is much more likely to cause lost
users than no v6.
--
Dave Cornejo - Dogwood Media, Fremont, California
General Magician Registered Be Developer
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
22 matches
Mail list logo
