Bug in libalias (firewall manipulating)

Hi, just noticed: adding dynamic rules to ipfw via PKT_ALIAS_PUNCH_FW (or the command "nat punch_fw" in ppp) doesn't work: For adding firewall rules, IP_FW_ADD requires getsockopt() instead of setsockopt(). This should also be reflected in the manual page. Below is my fix and a quick test sugg

Re: cardbus help

Warner Losh wrote: >In message <[EMAIL PROTECTED]> John McCullough writes: >: I'd like to get card bus working, however under 5.0-current my pcmcia >: controller is failing to load with the message: >: >: pccbb0: at device 15.0 on pci2 >: pcib2: device pccbb0 requested unsupported memory randg

Re: patch to support sio with NEWCARD

In message <[EMAIL PROTECTED]> YAMAMOTO Shigeru writes: : I make a patch to support sio with NEWCARD. : This patch is to avoid ghost interrupt when a PC-Card was removed. : : This patch has one assamption, : - all Serial PC-Card have a 16450/16550 compatible interface. This is a reasonable

Re: cardbus help

In message <[EMAIL PROTECTED]> Mike Smith writes: : This is a bug in the way that the pccbb code allocates the register : window when it hasn't been set up. The "real" fix actually requires the : PCI code to configure the cardbus controller, but we don't do that yet : (we desperately need to,

Re: cardbus help

In message <[EMAIL PROTECTED]> John McCullough writes: : I'd like to get card bus working, however under 5.0-current my pcmcia : controller is failing to load with the message: : : pccbb0: at device 15.0 on pci2 : pcib2: device pccbb0 requested unsupported memory randge : 0x1000-0x

Re: cardbus help

> I'd like to get card bus working, however under 5.0-current my pcmcia > controller is failing to load with the message: > > pccbb0: at device 15.0 on pci2 > pcib2: device pccbb0 requested unsupported memory randge > 0x1000-0x (decoding 0xf400-0xfbff, 0xfff0-0xf) >

Re: where is the idle_loop in current ?

Luigi Rizzo wrote: > Now, the whole problem here seems to be that kernel threads > are not preemptable, which is something that worries me a > bit because in CURRENT we use them for interrupt handlers as > well, and those used to be preemptable (subject to spl masks) > in RELENG_4. No, the kernel

patch to support sio with NEWCARD

Hi all, I make a patch to support sio with NEWCARD. This patch is to avoid ghost interrupt when a PC-Card was removed. This patch has one assamption, - all Serial PC-Card have a 16450/16550 compatible interface. I tested it on my NotePC and there is no problems. Please try it if you have

Re: df -l broken

David Wolfskill wrote: > >Date: Sun, 25 Nov 2001 22:41:01 +0100 > >From: Paul van der Zwan <[EMAIL PROTECTED]> > > >I noticed the -l option of the df command is broken > > That differs from my experience: > > d141[1] df -l > Filesystem 1K-blocks UsedAvail Capacity Mounted on > /de

Re: df -l broken

Paul van der Zwan wrote: > > I noticed the -l option of the df command is broken. It is supposed to > print df for local filesystems but on my system it prints nothing at all. > I had a quick look at the code , as far as I can tell it uses sysctl to > figure out the mounted filesystems but think

Re: df -l broken

>Date: Sun, 25 Nov 2001 22:41:01 +0100 >From: Paul van der Zwan <[EMAIL PROTECTED]> >I noticed the -l option of the df command is broken That differs from my experience: d141[1] df -l Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s3a158783939195216264%

cardbus help

I'd like to get card bus working, however under 5.0-current my pcmcia controller is failing to load with the message: pccbb0: at device 15.0 on pci2 pcib2: device pccbb0 requested unsupported memory randge 0x1000-0x (decoding 0xf400-0xfbff, 0xfff0-0xf) pccbb0: Could

Re: df -l broken

Paul van der Zwan <[EMAIL PROTECTED]> wrote: > I noticed the -l option of the df command is broken. Same for "mount -a -t local". I noticed this has been broken for more than a year now, maybe two. I've always been too lazy to investigate closer. IIRC, the last FreeBSD versions where it actua

df -l broken

I noticed the -l option of the df command is broken. It is supposed to print df for local filesystems but on my system it prints nothing at all. I had a quick look at the code , as far as I can tell it uses sysctl to figure out the mounted filesystems but thinks all of them are non-local and ign

RE: Sysinstall is still horribly broken.

matusita> OK, a patch is attached below. Sorry, forget to add the patch... try again. If anybody test with boot floppies, available at http://people.FreeBSD.org/~matusita/5.0-CURRENT-20011121-JPSNAP_usedevfs/, please let me know your results. -- - Makoto `MAR' Matsushita Index: install.c

Re: where is the idle_loop in current ?

Now, the whole problem here seems to be that kernel threads are not preemptable, which is something that worries me a bit because in CURRENT we use them for interrupt handlers as well, and those used to be preemptable (subject to spl masks) in RELENG_4. On the other hand, if preemptable threads a

[PATCH] - categorizing (XXX Lines) in NOTES

hi all, this patch will put an end to those XXX lines in the NOTES file, which were regarding uncategorized options.. such as USERCONFIG etc. PATCH is below... (start) *** NOTES.old Sun Nov 25 12:54:58 2001 --- NOTES Sun Nov 25 13:11:35 200

Re: where is the idle_loop in current ?

On Fri, 23 Nov 2001, Peter Wemm wrote: > Luigi Rizzo wrote: > > My understanding is that idle_loop threads _need_ to give up the cpu > > because they are special: they must never be in a run queue, and the > > scheduler knows about them (as a matter of fact, I cannot see where > > in kern/kern_id

subscribe

subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message