On Fri, Sep 12, 2003 at 08:54:59AM +0200, Morten Rodal wrote:
A little bit of history first. I am having great trouble in running
any of the Mozilla web browsers under -CURRENT with libkse. (If you
are really interested see the thread on threads@)
When I ran Mozilla Firebird with the
I tried to install the 9/15 snapshot which looks like it now supports
Adaptec SATA and Adaptec 1200A Raid controllers. Unfortuneatly on two
systems I tried to install this on, both failed with the error /dev/ad4s1a
no device present.
Since devices are automatically created in 5.X is there any
Hi,
I have -current on my laptop as of yesterdays sources and my suspending
isnt working quite right. The first time I suspend (S3) it works and
comes back to life, but the second time the laptop reboots when it
resumes.
I have now build a new kernel with debuging/ddb and hooked up a serial
On Mon, 15 Sep 2003, 23:48-0600, Scott Long wrote:
All,
I'd like to give a status report for 4.x and 5.x for the developers and
users who didn't attend the DevSummit this past weekend.
4.9:
The 4.9 release is likely going to be pushed back for a few weeks while
the recent instability
On Mon, Sep 15, 2003 at 03:13:30PM -0400, Didier Rwitura wrote:
I am trying to upgrade my sysstem from 4.8-RELEASE-p4 to 5.1
and i getting this error message when I run make -j4 buildworld
Does it actually stop there, or does it go on to rebuild make as the message
suggests it will, and as
Kris Kennaway wrote:
On Mon, Sep 15, 2003 at 03:13:30PM -0400, Didier Rwitura wrote:
I am trying to upgrade my sysstem from 4.8-RELEASE-p4 to 5.1
and i getting this error message when I run make -j4 buildworld
I had the same problem.
Making without the -j4 option works however.
Antoine
RELENG_5_1 builds just fine, but don't mess with make's max jobs with
buildworld.
-Mike
On Tue, 16 Sep 2003, Antoine Jacoutot wrote:
Date: Tue, 16 Sep 2003 09:12:46 +0200
From: Antoine Jacoutot [EMAIL PROTECTED]
To: Kris Kennaway [EMAIL PROTECTED]
Cc: Didier Rwitura [EMAIL PROTECTED],
On Mon, 15 Sep 2003 11:40:07 +0200 (CEST)
Soren Schmidt [EMAIL PROTECTED] wrote:
Okies, you need to update as there has been changes since this that
should fix the problem.
Update yesterday, same symptoms :(
Bye,
Dario
--
Dario Freni ([EMAIL PROTECTED]) - SaturNero on IRCNet, Azzurra
Gruppo
On Tue, 16 Sep 2003, Maxim Konovalov wrote:
PAE MFC brought an incredible instability to stable branch. It
affects 100% of our user community especially when we issued several
SAs since PAE commit. They often can't switch to RELENG_4_x security
branches because even RELENG_4_8 misses
The problem of not being able to reboot without a panic seems to persist on
late current with ATAng and SMP.
Pete
Sep 16 13:16:11 rms21 reboot: rebooted by pete
Sep 16 13:16:11 rms21 syslogd: exiting on signal 15
boot() called on cpu#0
Waiting (max 60 seconds) for system process `vnlru' to
It seems Petri Helenius wrote:
The problem of not being able to reboot without a panic seems to persist on
late current with ATAng and SMP.
The below doesn't say much actually, but I can reboot to my hearts content
on my SMP box here with no problems. What else do you have in that kernel ?
Soren Schmidt wrote:
It seems Petri Helenius wrote:
The problem of not being able to reboot without a panic seems to persist on
late current with ATAng and SMP.
The below doesn't say much actually, but I can reboot to my hearts content
on my SMP box here with no problems. What else do you
Hi!
On Tue, 16 Sep 2003 11:21:01 +1200
Marcos Biscaysaqu [EMAIL PROTECTED] wrote:
Hi There .
I have in comming a couple a Proxim 8480- pcmcia , with Atheros
Chipset and 8482- pci .
someone knows if this card work on Freebsd?
'man ath' has a list of supported cards. There may be more
Le 2003-09-15, Lee Damon écrivait :
Yesterday's cvsup'd and compiled kernel hung at
acd0: CDRW UJDA720 DVD/CDRW at ata1-master UDMA33
atapicam0: timeout waiting for ATAPI ready
This is from the low-level ATA layer. Do you see the same message if you
disable ATAPICAM?
Thomas.
--
Le 2003-09-13, Daniel Eischen écrivait :
cd0 at ata1 bus 0 target 0 lun 0
cd0: HL-DT-ST RW/DVD GCC-4240N D110 Removable CD-ROM SCSI-0 device
cd0: 33.000MB/s transfers
cd0: cd present [3737169375 x 3737169374 byte records]
Several others have reported similar completely bogus sector size
On Tuesday, September 16, 2003, at 06:11 AM, Bruce Evans wrote:
On Tue, 16 Sep 2003, Maxim Konovalov wrote:
PAE MFC brought an incredible instability to stable branch. It
affects 100% of our user community especially when we issued several
SAs since PAE commit. They often can't switch to
On Tue, Sep 16, 2003 at 08:43:00AM -0400, David Rhodus wrote:
Right, say if still the OpenSSH did or still comes out to be
real. Ops, now thats right, we don't have 3.6.1 in STABLE, why ? It
was released on April 1, does that not give one enough time to merge
this in ?
Merging new versions of
Le 2003-09-06, Petri Helenius écrivait :
Should this work or is the work to port this to ATAng still undergoing?
This should work, but does not, so the work is still in progress...
panic: mutex Giant not owned at ../../../dev/ata/atapi-cam.c:117
Please try this patch.
Index: atapi-cam.c
Le 2003-09-06, Guillaume écrivait :
I'm running FreeBSD 5-CURRENT (Aug. 28 2003) on a P3 733MHz, 768MB ram
with a LG DVD-RW/DVD-RAM burner. I would like to know why ATAPICAM is so
slow with my system.
Maybe because ATAPI/CAM does not actually enable DMA. Can you try the
following patch?
On Tue, 16 Sep 2003, Thomas Quinot wrote:
Le 2003-09-13, Daniel Eischen écrivait :
cd0 at ata1 bus 0 target 0 lun 0
cd0: HL-DT-ST RW/DVD GCC-4240N D110 Removable CD-ROM SCSI-0 device
cd0: 33.000MB/s transfers
cd0: cd present [3737169375 x 3737169374 byte records]
Several others
Yesterday's cvsup'd and compiled kernel hung at
acd0: CDRW UJDA720 DVD/CDRW at ata1-master UDMA33
atapicam0: timeout waiting for ATAPI ready
This is from the low-level ATA layer. Do you see the same message if you
disable ATAPICAM?
If I remove ATAPICAM from the kernel the system boots
Bruce Evans wrote:
On Tue, 16 Sep 2003, Maxim Konovalov wrote:
PAE MFC brought an incredible instability to stable branch. It
affects 100% of our user community especially when we issued several
SAs since PAE commit. They often can't switch to RELENG_4_x security
branches because even
On Tue, 16 Sep 2003, Scott Long wrote:
:Bruce Evans wrote:
: On Tue, 16 Sep 2003, Maxim Konovalov wrote:
:
:
:PAE MFC brought an incredible instability to stable branch. It
:affects 100% of our user community especially when we issued several
:SAs since PAE commit. They often can't switch to
Le 2003-09-16, Daniel Eischen écrivait :
I get this even without atapicam in the kernel. Is trying
CAMDEBUG and CAM_DEBUG_CDB going to show anything interesting?
No, indeed, probably not. Can you try the following patch:
Index: ata-lowlevel.c
David Rhodus [EMAIL PROTECTED] writes:
Right, say if still the OpenSSH did or still comes out to be
real. Ops, now thats right, we don't have 3.6.1 in STABLE, why ? It
was released on April 1, does that not give one enough time to merge
this in ?
Is there a specific problem with OpenSSH 3.5
Scott Long wrote:
Bruce Evans wrote:
On Tue, 16 Sep 2003, Maxim Konovalov wrote:
PAE MFC brought an incredible instability to stable branch. It
affects 100% of our user community especially when we issued several
SAs since PAE commit. They often can't switch to RELENG_4_x security
branches
On Tue, 16 Sep 2003, Thomas Quinot wrote:
Le 2003-09-16, Daniel Eischen écrivait :
I get this even without atapicam in the kernel. Is trying
CAMDEBUG and CAM_DEBUG_CDB going to show anything interesting?
No, indeed, probably not. Can you try the following patch:
OK, on a different
At Thu, 11 Sep 2003 14:44:55 +0200 (CEST),
Harti Brandt wrote:
Hi,
I just tried to upgrade one of my systems from a static root from july to
an actual dynamic root. The installworld went fine 'til the place where
/bin/test is installed. At that point the installation stopped with ELF
Bill Moran wrote:
Scott Long wrote:
Bruce Evans wrote:
On Tue, 16 Sep 2003, Maxim Konovalov wrote:
PAE MFC brought an incredible instability to stable branch. It
affects 100% of our user community especially when we issued several
SAs since PAE commit. They often can't switch to RELENG_4_x
Howdy list,
Is the ath(4) driver, like the wi(4) driver, incapable of performing
bridging?
For reference, this is from the bridge(4) manpage:
Bridging requires interfaces to be put in promiscuous mode, and transmit
packets with Ethernet source addresses. Some interfaces (e.g. wi(4))
On Tue, 16 Sep 2003, Richard Nyberg wrote:
RNAt Thu, 11 Sep 2003 14:44:55 +0200 (CEST),
RNHarti Brandt wrote:
RN Hi,
RN
RN I just tried to upgrade one of my systems from a static root from july to
RN an actual dynamic root. The installworld went fine 'til the place where
RN /bin/test is
Apparently, yes.
http://slashdot.org/articles/03/09/16/1327248.shtml?tid=126tid=172
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dag-Erling
Smørgrav
Sent: Tuesday, September 16, 2003 11:54 AM
To: David Rhodus
Cc: Maxim Konovalov; Scott Long;
On Tue, 16 Sep 2003, Scott Long wrote:
Patches have been floated on the mailing list that revert PAE in its
various stages. Maybe those need to be brought back up. Silby? Tor?
Scott
I believe that Tor's commit on August 30th resolved the PAE-related
problems, so there is no need for a
3. A panic caused by sending 64K-1 ping packets, which I can't reproduce.
Is this a firewall induced panic? -sc
--
Sean Chittenden
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
Mike Silbersack wrote:
On Tue, 16 Sep 2003, Scott Long wrote:
Patches have been floated on the mailing list that revert PAE in its
various stages. Maybe those need to be brought back up. Silby? Tor?
Scott
I believe that Tor's commit on August 30th resolved the PAE-related
problems, so there
Is the ath(4) driver, like the wi(4) driver, incapable of performing
bridging?
Yes. Bridging happens outside the operation of the driver.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
Is the ath(4) driver, like the wi(4) driver, incapable of performing
bridging?
Sorry, answered too quickly. ath and wi have the same restrictions. You
can use bridging to hookup a wired and wireless network but not two
wireless networks. I can't tell from your posting what you are trying to
On Tue, Sep 16, 2003 at 12:16:30PM -0400, Mike Jakubik typed:
Apparently, yes.
http://slashdot.org/articles/03/09/16/1327248.shtml?tid=126tid=172
Fortunately, there's allready a patch in the source tree:
TB --- 2003-09-16 16:00:01 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-09-16 16:00:01 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-16 16:01:50 - building world
TB --- cd
I think what he meant was that at on state was known (I don't know the
current state) that as the wi could not be but in promiscuous mode it
could not be used for bridging.. Bridging requires promiscuous mode
(or some very tricky proxy-arp stuff).
On Tue, 16 Sep 2003, Sam Leffler wrote:
Is
Hello,
On Mon, Sep 15, 2003 at 11:42:29AM +1000, Mark Sergeant wrote:
I get the same problem in the same place with current as of today.
I also noticed this issue. I just got a reply from the port maintainer
Alex Dupre as follows:
MR It won't configure. Output on my machine is as below.
I think what he meant was that at on state was known (I don't know the
current state) that as the wi could not be but in promiscuous mode it
could not be used for bridging.. Bridging requires promiscuous mode
(or some very tricky proxy-arp stuff).
You can put wi (and ath) in promiscuous
I'm not sure what I typed there but what I meant to say was
At one stage the wi driver could not be put in promiscuous mode and
the bridging code required that. Most people still think this is true.
On Tue, 16 Sep 2003, Sam Leffler wrote:
I think what he meant was that at on state was
Scott Long wrote:
Agreed. PAE was merged into -stable in three steps. Backing out the
third step and leaving the first two steps removes the instability.
Unfortunately, it was the third step that also was the most complex.
In any case, we have 2 weeks to find the resolution before the
--- /usr/src/sys/modules/Makefile.orig Tue Sep 16 10:42:38 2003
+++ /usr/src/sys/modules/Makefile Tue Sep 16 10:42:54 2003
@@ -126,7 +126,6 @@
twe \
tx \
txp \
- uart \
ubsa \
ubsec \
ucom \
--
Steve
Please compile your kernel with debug symbols (config -g KERNEL) and load
it into gdb to get the actual line of code that is getting that NULL
deref:
gdb kernel.debug
l *scsuspend+0x17
That should show the offending code segment.
-Nate
___
(To recap: I'm having ACPI problems on a DFI CD70-SC, with both 5.1-R and
5-CURRENT. Booting GENERIC doesn't show any problems, however, so there's
a good chance it's a misconfiguration issue.)
Thus spake Damian Gerow ([EMAIL PROTECTED]) [15/09/03 17:34]:
It's attached. There's no APM in
Howdy,
Sam Leffler wrote:
ath and wi have the same restrictions. You
can use bridging to hookup a wired and wireless network but not two
wireless networks. I can't tell from your posting what you are trying to
do.
Sam
I figured now would be a good place to chime in about WDS.
I'm
Nate Lawson wrote:
Please compile your kernel with debug symbols (config -g KERNEL) and load
it into gdb to get the actual line of code that is getting that NULL
deref:
gdb kernel.debug
l *scsuspend+0x17
That should show the offending code segment.
Hopefully I have done this right :)
On Wed, 17 Sep 2003, Andrew Thompson wrote:
Nate Lawson wrote:
gdb kernel.debug
l *scsuspend+0x17
That should show the offending code segment.
(gdb) l *scsuspend+0x17
0xc03d7b17 is in scsuspend (/usr/src/sys/isa/syscons_isa.c:111).
106 int retry = 10;
107
On Tue, Sep 16, 2003 at 11:16:54AM -0700, Julian Elischer wrote:
I'm not sure what I typed there but what I meant to say was
At one stage the wi driver could not be put in promiscuous mode and
the bridging code required that. Most people still think this is true.
I think it is still true.
TB --- 2003-09-16 18:27:08 - starting CURRENT tinderbox run for i386/i386
TB --- 2003-09-16 18:27:08 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/i386
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-16 18:29:00 - building world
TB --- cd
Hi,
I just built a kernel with latest sources, unfortunately, my ath(4) card
stopped working. The device is there, devd sets ip address, route etc.,
just as it did before the upgrade - the problem is that the link is dead,
there's _nothing_ going over the link. It also seems to re-associate
Hello there!
For versions of ata-lowlevel.c 1.9 the ad1 device isn't found.
Below is working dmesg with ata-lowlevel.c 1.9.
-Richard
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the
This may be a dumb question, but I have
a situation where machine A and B both have
enabled serial console. I'm ssh'ing into A to
try and debug a problem on B. I'm trying to
use tip, but am getting interference from the
fact that A also has a serial console.
If i disable the getty, its a bit
Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 15:00]:
I'm almost certain your problem is defining MAXMEM to 512 MB. Remove that
from your kernel config and try again. MAXMEM causes all kinds of
problems. If this doesn't solve it, start with the stock GENERIC and add
back in your
I just built a kernel with latest sources, unfortunately, my ath(4) card
stopped working. The device is there, devd sets ip address, route etc.,
just as it did before the upgrade - the problem is that the link is dead,
there's _nothing_ going over the link. It also seems to re-associate with
On Tue, 16 Sep 2003, Damian Gerow wrote:
Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 15:00]:
I'm almost certain your problem is defining MAXMEM to 512 MB. Remove that
from your kernel config and try again. MAXMEM causes all kinds of
problems. If this doesn't solve it, start with
Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 16:24]:
I have no time to track this down but the output of acpidump -t may help
someone else who might be interested. You're looking for the pointers
that are stored in RSD PTR.
I'm still on 5.1-R, and there's no '-t' flag to acpidump.
On Tue, 16 Sep 2003, Damian Gerow wrote:
Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 16:24]:
I have no time to track this down but the output of acpidump -t may help
someone else who might be interested. You're looking for the pointers
that are stored in RSD PTR.
I'm still on
TB --- 2003-09-16 19:46:27 - starting CURRENT tinderbox run for i386/pc98
TB --- 2003-09-16 19:46:27 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-16 19:49:03 - building world
TB --- cd
On Tue, Sep 16, 2003 at 10:30:50AM -0600, Scott Long wrote:
Mike Silbersack wrote:
On Tue, 16 Sep 2003, Scott Long wrote:
Patches have been floated on the mailing list that revert PAE in its
various stages. Maybe those need to be brought back up. Silby? Tor?
Scott
I believe that
If I start my kernel from september 15, my computer hangs after this message:
atapci0: VIA 82C686B UDMA100 controller port 0xa400-0xa40f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
A kernel from september 7 works normally. A normal dmesg is attached. Anything
I can
--On Tuesday, September 16, 2003 23:09:57 +0200 Arjan van Leeuwen
[EMAIL PROTECTED] wrote:
If I start my kernel from september 15, my computer hangs after this
message:
atapci0: VIA 82C686B UDMA100 controller port 0xa400-0xa40f at device
7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0:
Aloha!
Arjan van Leeuwen wrote:
If I start my kernel from september 15, my computer hangs after this message:
atapci0: VIA 82C686B UDMA100 controller port 0xa400-0xa40f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
Did you wait a while? I just completed my system update
On Tue, 16 Sep 2003, Sam Leffler wrote:
A kernel from Fri Sep 12 works correctly, with the same configuration. I
guess the ath/ieee80211 commits from yesterday/today broke something.
I need more help than this. Try supplying some information like the card
type (e.g. 5212) and your setup
I've tried various cvsup sites (normally cvsup2 or cvsup16 )
and each site returns this message:
Rejected by server: Access limit exceeded; try again later
I've gotten that before but never with all of the hosts out there. Is everyone and
their brother doing a make world today,
are the
On Tue, Sep 16, 2003 at 04:01:39PM -0600, Andrew Lankford wrote:
I've tried various cvsup sites (normally cvsup2 or cvsup16 )
and each site returns this message:
Rejected by server: Access limit exceeded; try again later
I've gotten that before but never with all of the hosts out there.
Sam Leffler wrote:
Is the ath(4) driver, like the wi(4) driver, incapable of performing
bridging?
Sorry, answered too quickly. ath and wi have the same restrictions. You
can use bridging to hookup a wired and wireless network but not two
wireless networks. I can't tell from your posting
In the last episode (Sep 16), Andrew Lankford said:
I've tried various cvsup sites (normally cvsup2 or cvsup16 ) and
each site returns this message:
Rejected by server: Access limit exceeded; try again later
I've gotten that before but never with all of the hosts out there.
Is everyone
On Tue, Sep 16, 2003 at 05:11:02PM -0500, Dan Nelson wrote:
In the last episode (Sep 16), Andrew Lankford said:
I've tried various cvsup sites (normally cvsup2 or cvsup16 ) and
each site returns this message:
Rejected by server: Access limit exceeded; try again later
I've gotten
Yes, I was referring to bridging two wireless interfaces.
David Young (of netbsd) has plans for WDS support that should fit into the
existing 802.11 layer. With his design you should be able to bridge WDS
links using the standard bridge support. No ETA.
Sam
On Tuesday 16 September 2003 23:33, Joachim Strömbergson wrote:
Aloha!
Arjan van Leeuwen wrote:
If I start my kernel from september 15, my computer hangs after this
message:
atapci0: VIA 82C686B UDMA100 controller port 0xa400-0xa40f at device
7.1 on pci0
ata0: at 0x1f0 irq 14 on
On Tue, Sep 16, 2003 at 04:01:39PM -0600, Andrew Lankford wrote:
I've tried various cvsup sites (normally cvsup2 or cvsup16 )
and each site returns this message:
Rejected by server: Access limit exceeded; try again later
I've gotten that before but never with all of the hosts out there.
Aloha!
Arjan van Leeuwen wrote:
On Tuesday 16 September 2003 23:33, Joachim Strömbergson wrote:
Try again and see if it is a real, solid hang, or if it just takes a while.
Thanks! I guess I'm too impatient these days... Yes, it works after waiting
for about 30 seconds. So a correction, it
TB --- 2003-09-16 21:02:39 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-09-16 21:02:39 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-16 21:05:41 - building world
TB --- cd
TB --- 2003-09-16 22:31:03 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-09-16 22:31:03 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-16 22:32:56 - building world
TB
On Mon, 8 Sep 2003, Soren Schmidt wrote:
It seems Nate Lawson wrote:
With a fresh checkout of last night's -current, I cannot boot my laptop.
ATAFD panics the box by reusing freed memory. I do not have a floppy
drive in the laptop and when I do, it's a legacy floppy, not atapi. Here
are
Nate Lawson wrote:
On Wed, 17 Sep 2003, Andrew Thompson wrote:
(gdb) l *scsuspend+0x17
0xc03d7b17 is in scsuspend (/usr/src/sys/isa/syscons_isa.c:111).
106 int retry = 10;
107 static int dummy;
108 sc_softc_t *sc;
109
110 sc =
I spoke too soon. Suddenly it all works.
It never got above 10 clients before today. How about a few
people switch to my server for regular updates? Thanks. :)
Regards,
--
wca
Oh, alright!
Andrew Lankford
___
[EMAIL
Hello all,
I've been wrestling with my nice, shiny new PITA system all week long.
The consensus seems to be that the RAM is suspect. I'm on my second
stick of 512 MB 2700 DDRAM for this thing and this one seems to be worse
than the first one I got. The first one was a Samsung and this one is
I just committed changes to bridge, ipfw, and dummynet. I've been running
these for a while but beware. I'm aware of two LOR issues that I want to
sort out later, after some more changes have gone in. Regardless, if you
encounter problems let me know...
Sam
On Tue, 16 Sep 2003, Don Bowman wrote:
This may be a dumb question, but I have
a situation where machine A and B both have
enabled serial console. I'm ssh'ing into A to
try and debug a problem on B. I'm trying to
use tip, but am getting interference from the
fact that A also has a serial
On Tuesday, September 16, 2003, at 11:54 AM, Dag-Erling Smørgrav wrote:
David Rhodus [EMAIL PROTECTED] writes:
Right, say if still the OpenSSH did or still comes out to be
real. Ops, now thats right, we don't have 3.6.1 in STABLE, why ? It
was released on April 1, does that not give one enough
Scott Reese [EMAIL PROTECTED] writes:
Though I'm not sure if RAM is my problem because I'm not getting Sig 11
errors. I keep getting extremely consistent internal compiler errors
pretty much whenever I try to build *anything*. I've tried to
buildkernel about 16 times today and each time I
Le Mar 16/09/2003 à 09:22, Thomas Quinot a écrit :
Le 2003-09-06, Guillaume écrivait :
I'm running FreeBSD 5-CURRENT (Aug. 28 2003) on a P3 733MHz, 768MB ram
with a LG DVD-RW/DVD-RAM burner. I would like to know why ATAPICAM is so
slow with my system.
Maybe because ATAPI/CAM does not
On Tue, Sep 16, 2003 at 09:47:44PM -0400, David Rhodus wrote:
On Tuesday, September 16, 2003, at 11:54 AM, Dag-Erling Smørgrav wrote:
Is there a specific problem with OpenSSH 3.5 which requires an update
to 3.6.1? Or do you just want me to update it to make the numbers
look pretty on your
--On Wednesday, September 17, 2003 00:24:06 +0200 Arjan van Leeuwen
[EMAIL PROTECTED] wrote:
On Tuesday 16 September 2003 23:33, Joachim Strömbergson wrote:
Aloha!
Arjan van Leeuwen wrote:
If I start my kernel from september 15, my computer hangs after this
message:
atapci0: VIA 82C686B
Sam Leffler wrote:
Yes, I was referring to bridging two wireless interfaces.
David Young (of netbsd) has plans for WDS support that should fit into the
existing 802.11 layer. With his design you should be able to bridge WDS
links using the standard bridge support. No ETA.
I appologize
I've got a Netgear WAG511 (Atheros 5212-based card) and a Netgear FWAG114
wireless router.
I've been trying to get the card and the router talking under FreeBSD.
(Both 802.11a and 802.11g work fine under Windows on the same machine.)
I'm using -current from September 15th.
Anyway, whenever I
TB --- 2003-09-17 04:00:01 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-09-17 04:00:01 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-17 04:02:11 - building world
TB --- cd
91 matches
Mail list logo
