Re: Possible bug in scheduler.

2001-10-19 Thread Alex Levine
John Baldwin wrote: On 18-Oct-01 Alexander Langer wrote: Thus spake Alex Levine ([EMAIL PROTECTED]): resetpriority() calls maybe_resched() at the end after updating p_usrpri based on changed p_estcpu. maybe_resched() uses curpriority_cmp to compare priorities of current and given process and

question about mmap() on FreeBSD3.3

2001-10-19 Thread Kenji Kaneshige
Hello I have a question about the behavior of mmap() in the kernel built without VM_STACK option. The platform is FreeBSD3.3. When the area allocated by mmap() overlaps the area between vm_maxsaddr and USRSTACK, accessing the overlapped area causes Segmentation Fault, although mmap() is returned

vmiodirenable vs isofs, some proof

2001-10-19 Thread Stephen McKay
About a month ago I suggested that vfs.vmiodirenable=1 and the cd9660 file system interract badly. I have not got absolute proof, but I think fairly good evidence of a causal link. At work I have an Athlon 1.4GHz with 512MB ram, IDE disk, IDE burner running FreeBSD 4.4 (no special options).

Re: FYI

2001-10-19 Thread Doug Hass
Tim, Your license with SBS for the DDK would prevent you from posting your code. If you read through it, you'll find that it prohibits the release of any of their DDK code under any circumstances. You could release everything EXCEPT the API for the card that SBS provides and offer the rest in

Re: Possible bug in scheduler.

2001-10-19 Thread John Baldwin
On 19-Oct-01 Alex Levine wrote: John Baldwin wrote: On 18-Oct-01 Alexander Langer wrote: Thus spake Alex Levine ([EMAIL PROTECTED]): resetpriority() calls maybe_resched() at the end after updating p_usrpri based on changed p_estcpu. maybe_resched() uses curpriority_cmp to compare

Re: FYI

2001-10-19 Thread Julian Elischer
On Thu, 18 Oct 2001, Mike Smith wrote: Well, honestly, FreeBSD makes the life of the developers of third-party binary-only drivers fairly difficult. It does? On the whole, actually, I'd say we do a pretty good job of making it easy. The reason is that there are a lot of API

RE: Circular log patches for syslog

2001-10-19 Thread Jeffrey D. Wheelhouse
-Original Message- From: Peter Wullinger [mailto:[EMAIL PROTECTED]] Subject: Re: Circular log patches for syslog Just to spoil the thread: Shouldn't things like this be available as additional package, so that the base system supplies only bas(e)ic functionality an everything

Re: patch #3 (was Re: bleh. Re: ufs_rename panic)

2001-10-19 Thread Yevgeniy Aleynikov
FYI: http://www.securityfocus.com/cgi-bin/archive.pl?id=1mid=221337start=2001-10-15end=2001-10-21 (about how things done in Linux). Zhihui Zhang wrote: (1) I am always wondering why not use a global rename lock so that there is only one rename operation in progress at any time. This

Re: vmiodirenable vs isofs, some proof

2001-10-19 Thread Matthew Dillon
-Matt Matthew Dillon [EMAIL PROTECTED] :About a month ago I suggested that vfs.vmiodirenable=1 and the cd9660 :file system interract badly. I have not got absolute proof,

SBS WANic (was FYI)

2001-10-19 Thread Tim Wiess
I don't doubt that. As I mentioned, there are several factors that I need to check into, especially our agreements with SBS. tim On Fri, 19 Oct 2001, Doug Hass wrote: Tim, Your license with SBS for the DDK would prevent you from posting your code. If you read through it, you'll find that

Re: New rc.d init script roadmap

2001-10-19 Thread David O'Brien
On Thu, Oct 18, 2001 at 11:29:59PM +0200, Cyrille Lefevre wrote: I've prepared a status report about this project. the xml file in attachment have to be reviewed since I've just put descriptions from FreeBSD-rc's Yahoo! Group and your email message. WHY in the world are you sending in a

Re: New rc.d init script roadmap

2001-10-19 Thread Cyrille Lefevre
David O'Brien wrote: On Thu, Oct 18, 2001 at 11:29:59PM +0200, Cyrille Lefevre wrote: I've prepared a status report about this project. the xml file in attachment have to be reviewed since I've just put descriptions from FreeBSD-rc's Yahoo! Group and your email message. WHY in the

system hung with runnable processes

2001-10-19 Thread Jeff Fellin
I didn't see anything like this in the archives, so I'm sending this to the questions list and hackers list for assistance. I am running FreeBSD 4.3 on a L440GX+ motherboard with dual PCI buses: 32/33 and 32/66 dual Pentium III @ 700MHz with 256KB L2 cache. The system is running in Uniprocessor

RE: Circular log patches for syslog

2001-10-19 Thread Mike Meyer
Jeffrey D. Wheelhouse [EMAIL PROTECTED] types: -Original Message- From: Peter Wullinger [mailto:[EMAIL PROTECTED]] Subject: Re: Circular log patches for syslog Just to spoil the thread: Shouldn't things like this be available as additional package, so that the base system

Re: New rc.d init script roadmap

2001-10-19 Thread Giorgos Keramidas
Cyrille Lefevre [EMAIL PROTECTED] wrote: I'm just reporting this one exists as you report the existence of Kevin Way's work two days ago. of course, it would be better to have a -rc mailing list. Not really. One more list to follow, when threads in existing lists will probably be enough

Re: more on Re: Please review: bugfix for vinvalbuf()

2001-10-19 Thread Doug Swarin
Unfortunately, the recent patch to vinvalbuf() hasn't solved all of our problems. We had another, different panic today. The process that caused it was a 'tail' of a growing logfile over NFS. I have actually had this problem before, with FreeBSD 3.4, and reported it then. I believed this PR to

Re: more on Re: Please review: bugfix for vinvalbuf()

2001-10-19 Thread Doug Swarin
On Fri, Oct 19, 2001 at 09:51:10PM -0700, Matthew Dillon wrote: : :Unfortunately, the recent patch to vinvalbuf() hasn't solved all of :our problems. We had another, different panic today. The process that :caused it was a 'tail' of a growing logfile over NFS. : :I have actually had this

Re: more on Re: Please review: bugfix for vinvalbuf()

2001-10-19 Thread Matthew Dillon
:I'm not able to reproduce this at will at the moment. The PR I mention :has a program which it claims can cause the crash, which I will try :running. I'll also try tailing various logfiles, including the one which :caused this crash, which is being written to on the machine that is the :NFS

fxp driver - receive interrupt bundling

2001-10-19 Thread Marko Zec
On http://fly.cc.fer.hr/~zec/index.html you can find a 4.4-RELEASE fxp driver source, with patches that incorporate receive interrupt bundling microcode, borrowed from the Intel's Linux e100 driver. Bundling interrupts for a couple of received Ethernet frames can significantly lower interrupt

Re: New rc.d init script roadmap

2001-10-19 Thread David O'Brien
On Thu, Oct 18, 2001 at 09:47:53PM +0200, Dag-Erling Smorgrav wrote: Dag-Erling Smorgrav [EMAIL PROTECTED] writes: Your rcorder patch is incorrect. Here's a correct patch. Does anybody mind if I commit this and connect rcorder(8) to the build? YES I MIND!! What part of it is on the

Re: New rc.d init script roadmap

2001-10-19 Thread John Baldwin
On 18-Oct-01 Dag-Erling Smorgrav wrote: Gordon Tetlow [EMAIL PROTECTED] writes: Actually, fparseln() is defined in libutil.h (per the man page). I don't have my current box available (power outage at home), but if you could look over it, it should work. Ah, that's right - I couldn't find

TCP windowsize...

2001-10-19 Thread Gunnar Olsson
Hi, Is there someone who can tell me how to set TCP windowsize? Best Regards, Gunnar Gunnar Olsson Phone: +46 8 5062 5762 Xelerated Packet Devices AB Fax: +46 8 5455 3211 Regeringsgatan 67

Re: fxp driver - receive interrupt bundling

2001-10-19 Thread David Greenman
On http://fly.cc.fer.hr/~zec/index.html you can find a 4.4-RELEASE fxp driver source, with patches that incorporate receive interrupt bundling microcode, borrowed from the Intel's Linux e100 driver. Bundling interrupts for a couple of received Ethernet frames can significantly lower interrupt

Re: New rc.d init script roadmap

2001-10-19 Thread Doug Rabson
On 18 Oct 2001, Dag-Erling Smorgrav wrote: John Baldwin [EMAIL PROTECTED] writes: Huh? Int on alpha is 32, and pointer is 64. I thought we were ILP64 on 64-bit archs, but you're right. And I ought to know better... Fortunately (?) it doesn't matter in this case. Function arguments which