- Original Message -
From: Soeren Schmidt [EMAIL PROTECTED]
To: David Xu [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, March 04, 2003 3:56 PM
Subject: Re: ATA MODE_SENSE_BIG timeout
It seems David Xu wrote:
(snip snap)
acd1: read data overrun 34/0
acd1: MODE_SENSE_BIG
Yes, I had problems with icewm in CURRENT too, but tried to compile
it before the mega-commit (version of 3-4 days ago). My workstation
at work (version of two weeks ago) installed icewm from ports without
problem.
I upgraded my ports tree and now I'm running portupgrade -u --all before
try KDE
It seems David Xu wrote:
(snip snap)
acd1: read data overrun 34/0
acd1: MODE_SENSE_BIG command timeout - resetting
ata1: resetting devices ..
done
acd1: CD-RW SONY CD-RW CRX140E at ata1-slave PIO4
Hmm, can you use the acd1 device normally or does it fail (how) ?
-Søren
I've been having a reliable USB issue on my 5-current box (3 Mar, 23:58:25
MST). It's been happening since I upgraded to -current in the DP2 days, and
has happened on two completely independent motherboards. On the more recent
of the two (the previous died) I've enabled USB_DEBUG. Here's the
Damn KMail. Full text to follow:
---
I've been having a reliable USB issue on my 5-current box (3 Mar, 23:58:25
MST). It's been happening since I upgraded to -current in the DP2 days, and
has happened on two completely independent motherboards. On the more recent
of the two (the previous
On Tue, Mar 04, 2003 at 04:21:14AM -0700, Cliff L. Biffle wrote:
Damn KMail. Full text to follow:
---
I've been having a reliable USB issue on my 5-current box (3 Mar, 23:58:25
MST). It's been happening since I upgraded to -current in the DP2 days, and
has happened on two completely
This could well be just something I forgot to do or I'm missing something as
I built my world last night at about 1am when I was knackered, so I apologise
if this isn't an issue.
After I rebooted I checked the sendmail header by telnetting port 25 to check
I had the new version and it had
On Tue, Mar 04, 2003 at 12:04:49PM +, Matt wrote:
This could well be just something I forgot to do or I'm missing something as
I built my world last night at about 1am when I was knackered, so I apologise
if this isn't an issue.
After I rebooted I checked the sendmail header by
Try to do following commands:
# cd /etc/mail
# touch *.mc
# make cf
# make restart
then telnet localhost 25
Yes this sorted it. ESMTP Sendmail 8.12.8/8.12.8.
Cheers :)
Matt.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
This is repeatable. Re-cvsupped using the same tag yesterday
morning and rebuilt on a clean /obj with the same result.
5.0 Release appears to be broken.
On Sun, 2 Mar 2003, Geoffrey wrote:
Ladies and Gentlemen
From a fresh cvsup of RELENG_5_0 this afternoon, make
Hi,
I cvsup'ed my source this morning, and after a successfull 'make
buildworld' I launch 'make buildkernel KERNCONF=GENERIC' - shortly after
it dies with the following message:
sh /usr/src/sys/kern/genassym.sh genassym.o assym.s
perl5 /usr/src/sys/kern/vnode_if.pl -h
Michael Hostbaek wrote:
--ncSAzJYg3Aa9+CRW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi,
I cvsup'ed my source this morning, and after a successfull 'make
buildworld' I launch 'make buildkernel KERNCONF=3DGENERIC' - shortly
walt (wa1ter) writes:
vnode_if.pl is a file from the -STABLE tree, not -CURRENT. Which
kernel are you trying to build?
Doh! Well, when I cvsup'ed I accidently used an old cvsup-src-file for
RELENG_4.. That might explain the problem.
Thanks.
/mich
--
Best Regards,
Michael Landin
Andre Guibert de Bruet wrote:
If you really need to use your workstation, you can try the open source nv
XFree86 driver. It's not as fast as the nVidia detonator driver and it's
not accelerated, but you can at least use X11 at a reasonable resolution
and color depth.
It works well enough for my
walt wrote:
My mini 'disaster' of earlier today was caused by the nvidia kernel
module being autoloaded at boot, which causes an immediate kernel panic.
The newest kernel seems fine until I try to load the module manually,
at which time I still get the kernel panic even after re-compiling
Maxime Henrion wrote:
walt wrote:
My mini 'disaster' of earlier today was caused by the nvidia kernel
module being autoloaded at boot, which causes an immediate kernel panic.
The newest kernel seems fine until I try to load the module manually,
at which time I still get the kernel
Maxime Henrion wrote:
walt wrote:
My mini 'disaster' of earlier today was caused by the nvidia kernel
module being autoloaded at boot, which causes an immediate kernel panic.
The newest kernel seems fine until I try to load the module manually,
at which time I still get the kernel panic even
20030304 label firepipe-3
amrestore: 1: restoring ganymede._.20030304.1
gzip: stdin: decompression OK, trailing garbage ignored
amrestore: 2: reached end of information
cannot open /dev/tty: Device not configured
Tape is not a dump tape
64+0 in
64+0 out
firepipe-3 (oberon._usr.20030304.2
Matt wrote:
After I rebooted I checked the sendmail header by telnetting port 25 to check
I had the new version and it had ESMTP Sendmail 8.12.8/8.12.7 in it. This I
thought was odd as I was expecting it to say 8.12.8 on both. I grepped for
8.12 in /etc/mail and freebsd.cf and sendmail.cf had
On Tue, 04 Mar 2003 07:52:32 -0800, Terry Lambert wrote
If you care, see other posting on how to fix it. Or you could
just edit the version in the config file, and call it a day. I
don't think you will see any differences from regenerating from
the M4 sources.
-- Terry
Yeah, thanks for
On Tue, Mar 04, 2003 at 04:39:46AM -0300, Rossam Souza Silva wrote:
Yes, I had problems with icewm in CURRENT too, but tried to compile
it before the mega-commit (version of 3-4 days ago). My workstation
at work (version of two weeks ago) installed icewm from ports without
problem.
I
Terry Lambert [EMAIL PROTECTED] writes:
Tim Robbins wrote:
Is there a compelling reason why I shouldn't remove netns? That is, does
it serve a purpose now that it could not serve if it was moved to the
Attic?
Might as well move /sys/i386/conf/GENERIC to the attic while
you are at it.
Looks like this email didn't make it to the mailing list. I've not tried the solution
yet, but I figured everyone would like to see this.
James.
Begin forwarded message:
Date: Tue, 4 Mar 2003 18:14:32 +0900
From: Yoshinori KASAZAKI [EMAIL PROTECTED]
To: James Satterfield [EMAIL PROTECTED]
On 2003-03-04 12:43, Matt [EMAIL PROTECTED] wrote:
Try to do following commands:
# cd /etc/mail
# touch *.mc
# make cf
# make restart
then telnet localhost 25
Yes this sorted it. ESMTP Sendmail 8.12.8/8.12.8.
The first version number is the version of your Sendmail executable.
The
On 03-Mar-2003 Andrew Gallatin wrote:
I'm developing a character driver which tracks a lot of state on a
per-open basis. I've got several mutexes in there which are
initialzed at open, and destroyed at close. After a few
dozen opens, witness seems to croak with:
witness_get:
John Baldwin writes:
Unfortunately dead witnesses may still be stuck in the lock order
hierarchy and I haven't figured out yet how to properly handle the
case of free'ing a witness structure from the tree while preserving
the correct lock orders. You can try
Ah, I think I see.
Anybody who uses the cvs-supfile example to get the repository should add
cvsroot-all to their supfile. This is in addition to src-all, ports-all,
doc-all etc.
This is *ONLY* for the folks getting the CVS ,v files via cvsup. If you
use tag=. or tag=RELENG_4, then you are not affected by this.
Hi all,
please point me to the right list if this isn't the right one, but I'm
running into what appears to be GEOM trouble when installing 5.0-RELEASE.
[btw, the below uses MSDOS terminology for partitions, sorry]
The setup is a fairly straight athlon 700 with IDE 2 harddisks, a primary
master
On Tue, Mar 04, 2003 at 11:10:45AM -0800, Peter Wemm wrote:
Anybody who uses the cvs-supfile example to get the repository should add
cvsroot-all to their supfile. This is in addition to src-all, ports-all,
doc-all etc.
This is *ONLY* for the folks getting the CVS ,v files via cvsup. If
On 04-Mar-2003 Hiten Pandya wrote:
John Baldwin (Mon, Mar 03, 2003 at 02:49:21PM -0500) wrote:
On 02-Mar-2003 Juli Mallett wrote:
* De: Hiten Pandya [EMAIL PROTECTED] [ Data: 2003-03-01 ]
[ Subjecte: Possible patch for limiting APs at startup ]
Hello.
Just as the topic says,
On 04-Mar-2003 Soeren Schmidt wrote:
It seems David Xu wrote:
(snip snap)
acd1: read data overrun 34/0
acd1: MODE_SENSE_BIG command timeout - resetting
ata1: resetting devices ..
done
acd1: CD-RW SONY CD-RW CRX140E at ata1-slave PIO4
Hmm, can you use the acd1 device
Stijn Hoop wrote:
On Tue, Mar 04, 2003 at 11:10:45AM -0800, Peter Wemm wrote:
Anybody who uses the cvs-supfile example to get the repository should add
cvsroot-all to their supfile. This is in addition to src-all, ports-al=
l,
doc-all etc.
=20
This is *ONLY* for the folks getting the
On Tue, Mar 04, 2003 at 07:31:27AM -0800, Will Andrews wrote:
Anyone know if maybe the dump format has been changed to the
extent that it breaks Amanda or something? In fact, based on the
64+0 it appears that the header or something similar may have
been broken.
I've seen reports that dump
On Tue, Mar 04, 2003 at 11:45:18AM -0800, Peter Wemm wrote:
No, people who use cvs-all are already getting this stuff. If you use
the cvsup-mirror port yourself, you do not need to change anything either.
Mirrors who use cvs-all (official and unofficial) do not need to change
anything.
OK,
Are all the official mirrors in the USA (cvsup1..17.freebsd.org)
supposed to have the cvsroot-all package? I just tried cvsup16 and it
doesn't have it.
-Original Message-
From: Peter Wemm [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2003 1:45 PM
To: Stijn Hoop
Cc: [EMAIL
On Tue, Mar 04, 2003 at 11:57:34AM -0800, Brooks Davis wrote:
I've seen reports that dump compatability was broken. I'm dumping two
5.0 boxes and one 4-STABLE box to one of the 5.0 boxes and the amverify
I'm current running doesn't seem to have any problem. Thus, I'd tend to
suspect we need
It seems Dag-Erling Smorgrav wrote:
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
No tags, like you said. Previously, with a tags-capable kernel,
enabling tags would cause a continuous stream of timeouts and resets
on both disks.
Just for kicks, I removed the #if 0 in ata-disk.c and got
Brian J. McGovern [EMAIL PROTECTED] writes:
Anyone have any ideas if something has broken, or whether its pilot error?
Please show the output of fetch -vvv some-url-that-doesn't-work
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
Scotty [EMAIL PROTECTED] writes:
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices ..
Disable tags (add hw.ata.tags=0 to /boot/loader.conf). Never worked
for me either (ASUS P5A, ALi M1543 southbridge, IBM DTTA and IC35L
disks)
DES
--
Dag-Erling Smorgrav - [EMAIL
It seems Dag-Erling Smorgrav wrote:
Scotty [EMAIL PROTECTED] writes:
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices ..
Disable tags (add hw.ata.tags=0 to /boot/loader.conf). Never worked
for me either (ASUS P5A, ALi M1543 southbridge, IBM DTTA and IC35L
Soeren Schmidt [EMAIL PROTECTED] writes:
Tags are disabled in -current in ata-disk.c so if the sources are
up to date that cannot be the problem.
Please update and then at least provide a dmesg if it still fails.
top-of-tree:
[EMAIL PROTECTED] /home/des# egrep '(ata|ad)[0-9]'
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
No tags, like you said. Previously, with a tags-capable kernel,
enabling tags would cause a continuous stream of timeouts and resets
on both disks.
Just for kicks, I removed the #if 0 in ata-disk.c and got exactly the
same symptoms as before:
Soeren Schmidt [EMAIL PROTECTED] writes:
It seems Dag-Erling Smorgrav wrote:
ad0: READ command timeout tag=0 serv=1 - resetting
ad0: invalidating queued requests
That why it is disabled, its not working for the time being.
For me, the time being == since it was introduced in the tree. It
On Tue, Mar 04, 2003 at 04:59:33PM +0100, Dag-Erling Smorgrav
[EMAIL PROTECTED] wrote:
Soeren Schmidt [EMAIL PROTECTED] writes:
It seems Dag-Erling Smorgrav wrote:
ad0: READ command timeout tag=0 serv=1 - resetting
ad0: invalidating queued requests
That why it is disabled, its not
This does look odd... maybe there's a leak somewhere... does in use
go back down to a much lower number eventually? What kind of test are
you running? in pool means that that's the number in the cache
while in use means that that's the number out of the cache
currently being used
I don't know how system-specific this problem is, but:
Sony VAIO R505ES
Sound is Intel ICH3 + Yamaha.
This or something closely related has been happening for weeks.
Several times earlier this week and last week sound panic'd, and
also sometimes there was a panic (several different kinds) on
I do one thing in Linux that I want to do in FreeBSD. I store my root
file system as a blow fish, gzipped, encrypted file on a DiskOnChip.
When the Linux kernel boots it loads an initial ramdisk that will open
this file, uncompress, and decrypt. I will then write the good data to
a ram disk.
Petri Helenius (Wed, Mar 05, 2003 at 01:42:05AM +0200) wrote:
This does look odd... maybe there's a leak somewhere... does in use
go back down to a much lower number eventually? What kind of test are
you running? in pool means that that's the number in the cache
while in use
On Wed, Mar 05, 2003 at 01:42:05AM +0200, Petri Helenius wrote:
This does look odd... maybe there's a leak somewhere... does in use
go back down to a much lower number eventually? What kind of test are
you running? in pool means that that's the number in the cache
while in use
Hiten Pandya (Tue, Mar 04, 2003 at 07:01:15PM -0500) wrote:
Petri Helenius (Wed, Mar 05, 2003 at 01:42:05AM +0200) wrote:
This does look odd... maybe there's a leak somewhere... does in use
go back down to a much lower number eventually? What kind of test are
you running? in
For those want to fix ATA code, I have another problem
with CURRENT. I have a Tyan Tiger 230T which is based
on VIA Apollo 133T, south bridge is VIA 686B.
On second IDE, I have a Mitsubishi 52X cdrom as master,
and a Sony 16X CD R/W as slave, when startup, kernel
is always stuck at
Haha. I'm an idjit. Sorry.
That's what happens when you take isa out of the kernel config
(what was I thinking anyway? - fd and atkbdc among others need this and I
knew that).
On Tue, 4 Mar 2003, Geoffrey wrote:
This is repeatable. Re-cvsupped using the same tag
On Wed, 26 Feb 2003, Poul-Henning Kamp wrote:
Is there anybody out there who can try to run a straight -current
on a _real_ i386 class CPU ?
Ie, not a i486, not a Cyrix, not an AMD but a genuine Intel i386DX
(SX would be but too suicidal to be informative).
Well, finally got a kernel to
I'm getting the could sleep with messages repeated over and over on my
Dell Lattitude C800 which uses the maestro3 chip. The sound isn't overly
choppy. It only stutters under disk/compute activity.
Andre Guibert de Bruet | Enterprise Software Consultant
Silicon Landmark, LLC. |
On Tue, Mar 04, 2003 at 03:42:43PM -0800, Pete Carah wrote:
Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with
pcm0:play:0 locked from /usr/src/sys/dev/sound/pcm/dsp.c:748
Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with
I'm seeing
On Wed, Mar 05, 2003 at 12:27:19PM +1000, Andy Farkas wrote:
Well, finally got a kernel to boot on a 16MHz 386SX (suicidal is an
understatement!) - will this do?
Can you post the /var/run/dmesg.boot?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of
With IPFILTER enabled in the kernel, all socket(2) calls inbound/outbound are very
slow. A normal SSH connection within the same subnet takes 5 minutes to connect.
Anything I can provide to pin down the problem?
Jiawei
--
Without the userland, the kernel is useless.
On Mon, Mar 03, 2003 at 12:08:04AM +0100, Jens Rehsack wrote:
Now, that OpenWatcom is released, the FreeBSd port of it should follow.
And maybe someone will try to compile the kernel and world with it.
I hate to be the skeptic, but looking at OpenWatcom 1.0, it only produces
dos and win32
David O'Brien wrote:
On Wed, Mar 05, 2003 at 12:27:19PM +1000, Andy Farkas wrote:
Well, finally got a kernel to boot on a 16MHz 386SX (suicidal is an
understatement!) - will this do?
Can you post the /var/run/dmesg.boot?
Should be very interesting to see the output of this file :)
Yep, this message is no more about KDE. :)
Thanks Sergey, your patch isn't in ports tree yet, but I used it,
ltmdm now compiles and works. I'm running today's version of CURRENT.
kern.osreldate: 500105
dmesg:
ltmdm0: Lucent Winmodem port 0xb000-0xb0ff,0xb400-0xb407 mem
0xdc00-0xdcff
-Original Message-
From: Pete Carah [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2003 2:43 AM
To: [EMAIL PROTECTED]
Subject: Witness problem with sound
I don't know how system-specific this problem is, but:
it's not system-specifiv
Problem:
..
Mar 4 14:56:27 port2
From: David O'Brien [EMAIL PROTECTED]
To: Jens Rehsack [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, March 05, 2003 10:01 AM
Subject: Re: PATCH: type errors in src-tree
On Mon, Mar 03, 2003 at 12:08:04AM +0100, Jens Rehsack wrote:
Now, that OpenWatcom is released, the FreeBSd
Last weekend I had to reinstall Windows XP on my PC and certainly I lost
boot manager. After booting from CD and mounting as root ad0 device, I
replaced boot0 record
using the following command line :
# boot0cfg -Bv -s 1 -t 91 ad0
On my PC I have 14G Windows XP partition(primary partition), 7G
Hi, thanks Maxime, your patch works ok! Well, the nVIDIA driver is
labeled beta quality anyway, so, why not upgrade nvidia-driver port to
support 5-CURRENT too? I'm actually using it, with a ugly hack: applying
the patch, compacting and copying the new distfile, editing Makefile to
comment 4.x
In message [EMAIL PROTECTED], Andy Farkas
writes:
I'll try and get some data for your clock/time tracking requests in a few
days. I assume you want wall-clock tracking info for both with and
without ntpd running?
yes.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED]
On Tue, Mar 04, 2003 at 11:01:25PM -0800, David O'Brien wrote:
On Mon, Mar 03, 2003 at 12:08:04AM +0100, Jens Rehsack wrote:
Now, that OpenWatcom is released, the FreeBSd port of it should follow.
And maybe someone will try to compile the kernel and world with it.
I hate to be the
Hi,
Chris Fowler schrieb:
I do one thing in Linux that I want to do in FreeBSD. I store my root
file system as a blow fish, gzipped, encrypted file on a DiskOnChip.
I have done exactly this some years ago, checkout PicoBSD (freebsd-small
mailinglist). But I don't know the current status of
Hi, there is some plan to port NetBSD's implementation of IP over
Firewire? I know, we have Ethernet over Firewire, but like the Linux
one, isn't a standard...
Just curious.
--
(_ ) Contrary to popular belief,
Any comments on the high cpu consumption of mb_free? Or any other places
where I should look to improve performance?
What do you mean high cpu consumption? The common case of mb_free()
is this:
According to profiling mb_free takes 18.9% of all time consumed in kernel and is
almost
Julian Elischer (Tue, Mar 04, 2003 at 02:53:56PM -0800) wrote:
I thought nwfs used it?
On Wed, 5 Mar 2003, Tim Robbins wrote:
Is there a compelling reason why I shouldn't remove netns? That is, does
it serve a purpose now that it could not serve if it was moved to the
Attic?
That's
On Wed, Mar 05, 2003 at 01:12:55AM +0200, Petri Helenius wrote:
Any comments on the high cpu consumption of mb_free? Or any other places
where I should look to improve performance?
What do you mean high cpu consumption? The common case of mb_free()
is this:
According to
Mike Barcroft wrote:
Terry Lambert [EMAIL PROTECTED] writes:
Tim Robbins wrote:
Is there a compelling reason why I shouldn't remove netns? That is, does
it serve a purpose now that it could not serve if it was moved to the
Attic?
Might as well move /sys/i386/conf/GENERIC to the
Terry Lambert [EMAIL PROTECTED] writes:
Mike Barcroft wrote:
Terry Lambert [EMAIL PROTECTED] writes:
Tim Robbins wrote:
Is there a compelling reason why I shouldn't remove netns? That is, does
it serve a purpose now that it could not serve if it was moved to the
Attic?
Is there a compelling reason why I shouldn't remove netns? That is, does
it serve a purpose now that it could not serve if it was moved to the
Attic?
Tim
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Tim Robbins wrote:
Is there a compelling reason why I shouldn't remove netns? That is, does
it serve a purpose now that it could not serve if it was moved to the
Attic?
Might as well move /sys/i386/conf/GENERIC to the attic while
you are at it. It can serve it's purpose from there, too.
Is
On Tue, Mar 04, 2003 at 07:56:27AM -0800, Terry Lambert wrote:
Tim Robbins wrote:
Is there a compelling reason why I shouldn't remove netns? That is, does
it serve a purpose now that it could not serve if it was moved to the
Attic?
Might as well move /sys/i386/conf/GENERIC to the attic
Why does it need to be removed ? According to me, it would be the same mistake
as the removal of netiso and netccitt. I did not know FreeBSD at this time,
but nowadays, in order to get an OS that supports many stacks, we have to use
NetBSD.
BSD4.4 was designed in order to support many stacks,
In message [EMAIL PROTECTED], Vincent Jardin writes:
Why does it need to be removed ? According to me, it would be the same mistake
as the removal of netiso and netccitt. I did not know FreeBSD at this time,
but nowadays, in order to get an OS that supports many stacks, we have to use
NetBSD.
Terry Lambert wrote:
Is there a compelling reason for removing this working code to
the Attic?
Terry: will you please check your facts? It takes around 30 seconds
to find out that it doesn't even compile.
In file included from ../../../netns/idp_usrreq.c:51:
../../../netns/ns_pcb.h:82:
In message [EMAIL PROTECTED], Peter Wemm writes:
Terry Lambert wrote:
Is there a compelling reason for removing this working code to
the Attic?
Terry: will you please check your facts? It takes around 30 seconds
to find out that it doesn't even compile.
Could we possibly move Terry to the
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Vincent Jardin writes:
Why does it need to be removed ? According to me, it would be the same mista
ke
as the removal of netiso and netccitt. I did not know FreeBSD at this time,
but nowadays, in order to get an OS that supports
On Tue, Mar 04, 2003 at 02:53:56PM -0800, Julian Elischer wrote:
I thought nwfs used it?
nwfs uses netipx. From what I can tell, netipx was based on netns.
Tim
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
What is IPX currently being used for? Legacy systems?
I've been stuck in TCP/IP land for many years now. Have been lucky
enough to not run into any IPX.
On Tue, 2003-03-04 at 18:26, Tim Robbins wrote:
On Tue, Mar 04, 2003 at 02:53:56PM -0800, Julian Elischer wrote:
I thought nwfs used
Peter Wemm wrote:
Terry Lambert wrote:
Is there a compelling reason for removing this working code to
the Attic?
Terry: will you please check your facts? It takes around 30 seconds
to find out that it doesn't even compile.
[ ... lots of trivial to fix warnings and errors ... ]
Tell
* De: Terry Lambert [EMAIL PROTECTED] [ Data: 2003-03-04 ]
[ Subjecte: Re: Removal of netns - politically correct version ]
Peter Wemm wrote:
Terry Lambert wrote:
Is there a compelling reason for removing this working code to
the Attic?
Terry: will you please check your
On Tue, 4 Mar 2003, Terry Lambert wrote:
Tell you what, I'll fix these and post a patch. Will that make you
guys happy?
Yes, as will anything else that cuts down on the metadiscussions and
increases the quality of the codebase.
mcl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
* De: Mark Linimon [EMAIL PROTECTED] [ Data: 2003-03-04 ]
[ Subjecte: Re: Removal of netns - politically correct version ]
On Tue, 4 Mar 2003, Terry Lambert wrote:
Tell you what, I'll fix these and post a patch. Will that make you
guys happy?
Yes, as will anything else that cuts
On Tue, Mar 04, 2003 at 01:35:51PM -0800, Terry Lambert wrote:
Things being removed constantly.
If you will remember, there has been a rocky history with the
removal of functionality in FreeBSD. If you don't remember,
I will be happy to remind you of specific incidents that ended
up
I have at least 1 VPN setup that requires full IPX support.
On Tuesday 04 March 2003 15:32, Chris Fowler wrote:
What is IPX currently being used for? Legacy systems?
I've been stuck in TCP/IP land for many years now. Have been lucky
enough to not run into any IPX.
On Tue, 2003-03-04 at
Terry Lambert wrote:
Peter Wemm wrote:
Terry: will you please check your facts? It takes around 30 seconds
to find out that it doesn't even compile.
[ ... lots of trivial to fix warnings and errors ... ]
Tell you what, I'll fix these and post a patch. Will that make you
guys happy?
Julian Elischer wrote:
I thought nwfs used it?
Nope. But actually looking at the code would have told you that.
Remember, we're talking about the Xerox networking suite here. It's not
like its a widely deployed protocol or something important.
On Wed, 5 Mar 2003, Tim Robbins wrote:
Is
Darcy Buskermolen wrote:
I have at least 1 VPN setup that requires full IPX support.
Yep, but keep in mind that netipx is different to netns. netipx actually
works and is actually useful.
On Tuesday 04 March 2003 15:32, Chris Fowler wrote:
What is IPX currently being used for? Legacy
Terry Lambert wrote:
Peter Wemm wrote:
Terry Lambert wrote:
Is there a compelling reason for removing this working code to
the Attic?
Terry: will you please check your facts? It takes around 30 seconds
to find out that it doesn't even compile.
[ ... lots of trivial to fix
Terry Lambert wrote:
Terry Lambert wrote:
Peter Wemm wrote:
Terry: will you please check your facts? It takes around 30 seconds
to find out that it doesn't even compile.
[ ... lots of trivial to fix warnings and errors ... ]
Tell you what, I'll fix these and post a patch.
On Tue, 4 Mar 2003, Vincent Jardin wrote:
Why does it need to be removed ? According to me, it would be the same mistake
as the removal of netiso and netccitt. I did not know FreeBSD at this time,
but nowadays, in order to get an OS that supports many stacks, we have to use
NetBSD.
If netns
I did some profiling on -CURRENT from a few days back, and I think I haven´t
figured the new tunables out or the code is not doing what it´s supposed to
or I´m asking more than it is supposed to do but it seems that mb_free
is being quite wasteful...
Any pointers to how the new high/low
Wilko Bulte wrote:
On Tue, Mar 04, 2003 at 07:56:27AM -0800, Terry Lambert wrote:
Is there a compelling reason for doing this, other than I
want to make some API/locking change, but I don't want to
have to keep this code working at the same time? Maximizing
Is there a compelling reason
On Tue, Mar 04, 2003 at 11:34:11PM +0200, Petri Helenius wrote:
I did some profiling on -CURRENT from a few days back, and I think I haven´t
figured the new tunables out or the code is not doing what it´s supposed to
or I´m asking more than it is supposed to do but it seems that mb_free
is
Yes, it's normal. The commit log clearly states that the new
watermarks do nothing for now. I have a patch that changes that but I
haven't committed it yet because I left for vacation last Sunday and I
only returned early this Monday. Since then, I've been too busy to
clean up
On Wed, Mar 05, 2003 at 12:24:27AM +0200, Petri Helenius wrote:
Yes, it's normal. The commit log clearly states that the new
watermarks do nothing for now. I have a patch that changes that but I
haven't committed it yet because I left for vacation last Sunday and I
only
1 - 100 of 105 matches
Mail list logo
