Can't make crashdump after panic

[Alex Le Heux]

Hi,

With a kernel from 07:00 (UTC) this morning I started to get a panic every
time during the startup of Windowmaker.

After configuring the system for making a crashdump, I get "panic: Timeout
table full" halfway through the dump.

This is on a stock PII system (weirdest hardware is a ZIP drive :), which
I'm trying to upgrade from a -current from Sep 17. (install new kernel
first, make world after, etc)

Can anyone clue me in here?

Alex

-- 
++---+
|  SMTP: <[EMAIL PROTECTED]>   |  E-Gold: 101979   |
|  ICBM: N52 22.64'6 E4 51.54'1  |  PGP: 0x1d512a3f  |
++---+


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

intpm(4) polling patch

[Takanori Watanabe]

If you get "Device not configured" message, apply following patch and
do 'sysctl -w hw.intpm_poll=1'.If your system is SMP, 'hw.intpm_poll' value
is 1 as a default.(Not tested.)
This is not *the right* solution,but it will work I think.

Takanori Watanabe
http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html">
Public Key
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 


--- /home/ctm/src/sys/pci/intpm.c   Fri Sep  3 03:16:24 1999
+++ intpm.c Thu Oct 14 12:25:28 1999
@@ -43,9 +43,9 @@
 #include 
 #include 
 #include 
-
+#include 
 #include "smbus_if.h"
-
+#include "smp.h"
 /*This should be removed if force_pci_map_int supported*/
 #include 
 
@@ -90,6 +90,9 @@
 static int intpm_attach (device_t dev);
 static devclass_t intsmb_devclass;
 
+static int intpm_poll=0;
+SYSCTL_INT(_hw, OID_AUTO, intpm_poll, CTLFLAG_RW, &intpm_poll, 1, "");
+
 static device_method_t intpm_methods[]={
 DEVMETHOD(device_probe,intsmb_probe),
 DEVMETHOD(device_attach,intsmb_attach),
@@ -379,7 +382,7 @@
 int error;
intrmask_t s;
 struct intsmb_softc *sc = (struct intsmb_softc *)device_get_softc(dev);
-   if(cold){
+   if(cold||intpm_poll!=0){
/*So that it can use device during probing device on SMBus.*/
error=intsmb_stop_poll(dev);
return error;
@@ -656,7 +659,10 @@
 device_t smbinterface;
int rid;
struct resource *res;
-
+#if NSMP>0
+   device_printf(dev,"SMP system so polling mode is default\n");
+   intpm_poll=1;
+#endif
 sciic=device_get_softc(dev);
 if(sciic==NULL){
 return ENOMEM;







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

linux emulation broken..

[Chris Csanady]

It has been getting worse and worse for me recently.  The two
applications where it is noticeable are netscape, and word
(im)perfect.  I was using the linux version of netscape, until
recently when it began hanging for long periods of time during
network or disk activity.  For a while with WP, it was fairly
useable, except I could not print with it.  Now though, I
can't even save files, it hangs at the Save As dialog.

I'm sorry I can't be more specific, but with a kernel from today
it is still broken.  I don't have time to go into it any further
right now, but I thought I would check if others are having
similar difficulties.

I have a lot to do, and it is just extremely irritating right
now.  I swear, nothing relating to linux ever works..  I have
the pleasure of using at it work on a regular basis, and it has
been nothing but a complete PITA.  So much time wasted.  Sorry,
I couldn't help including my $0.02 wrt linux..

Chris Csanady



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

Re: The eventual fate of BLOCK devices.

[Chuck Robey]

On Tue, 12 Oct 1999, Warner Losh wrote:

> In message <[EMAIL PROTECTED]> David 
>Scheidt writes:
> : It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated
> : disk devices.  There may be other RDBMSes that do this. 
> 
> EVERY RDBMS that I've ever seen or had to make work with my drivers
> has been on the raw partition.  This is because the database writers
> DO NOT LIKE OR TRUST the buffer cache due to its non-deterministic
> nature of disk writing.  Are you sure that Sybase uses BLOCK devices
> and not CHAR devices?

Gawd, now that I think of it, about my Informix post, you're right, they
use a raw partition, and their own buffering.

> 
> Warner
> 
> 


Chuck Robey| Interests include C programming, Electronics,
213 Lakeside Dr. Apt. T-1  | communications, and signal processing.
Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and
(301) 220-2114 |   jaunt.mat.net : FreeBSD-current(Alpha)




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

Re: The eventual fate of BLOCK devices.

[Chuck Robey]

On Tue, 12 Oct 1999, David Scheidt wrote:

> On Tue, 12 Oct 1999, Kirk McKusick wrote:
> 
> > I would like to take a step back from the debate for a moment and
> > ask the bigger question: How many real-world applications actually
> > use the block device interface? I know of none whatsoever. All the
> > filesystem utilities go out of their way to avoid the block device
> > and use the raw interface. Does anyone on this list know of any
> > programs that need/want the block interface? If there are none, or
> 
> It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated
> disk devices.  There may be other RDBMSes that do this. 

Informix, should a miracle occur and they decide to suport FreeBSD,
definitely want the same.



Chuck Robey| Interests include C programming, Electronics,
213 Lakeside Dr. Apt. T-1  | communications, and signal processing.
Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and
(301) 220-2114 |   jaunt.mat.net : FreeBSD-current(Alpha)




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

Re: make buildworld breaks during vinum compilation

[Greg Lehey]

On Wednesday, 13 October 1999 at 21:38:07 +0200, Marc van Woerkom wrote:
> I got a stop here:
>
> root@oranje# date; make buildworld
> Wed Oct 13 15:34:04 CEST 1999
> (...)
> cc -O -pipe -DVINUMDEBUG -g -O  -DKERNEL -Wall -Wredundant-decls 
>-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline 
>-Wcast-qual  -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-  
>-I/usr/obj/usr/src/sys/modules/vinum -I/usr/obj/usr/src/sys/modules/vinum/@ 
>-I/usr/obj/usr/src/tmp/usr/include -c 
>/usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c
> /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c: In function 
>`vinumioctl':
> /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c:333: too few arguments 
>to function `initsd'
> *** Error code 1

On Wednesday, 13 October 1999 at 23:19:11 +0200, Gianmarco Giovannelli wrote:
> Me too ...

Pass the pointy hat.  I forgot to commit one of the files in the last
change.  I *did* cvsup and recompile after committing, but I didn't
notice that there was an M flag for vinumioctl.c :-(

It should all be OK now.

Greg
--
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key


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

Fwd: RE: /dev/smb0 on Dell Latitude

[Richard Wackerbarth]

Thanks for your suggestion. I haven't found anything in the archives that seems
to apply. Any help from "current"?

--  Forwarded Message  --
Subject: RE: /dev/smb0 on Dell Latitude
Date: Wed, 13 Oct 1999 17:53:06 -0500
From: "Alejandro Ramirez" <[EMAIL PROTECTED]>


Hi,

You should write this question to [EMAIL PROTECTED], there was
some discusion about this.

Ales

- Original Message -
From: Richard Wackerbarth <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 13, 1999 5:09 PM
Subject: /dev/smb0 on Dell Latitude


> Help! Does anyone have any experience with the smbus on Dell laptops?
> This is today's kernel.
>
> Selected entries in dmesg are below.
>
> When I attempt to find devices the ioctl returns "Device not configured"
on
> /dev/smb0.
>
>
> FreeBSD 4.0-CURRENT #9: Wed Oct 13 08:21:53 CDT 1999
>
> CPU: Pentium II/Xeon/Celeron (267.27-MHz 686-class CPU)
>   Origin = "GenuineIntel"  Id = 0x650  Stepping = 0
>
Features=0x183f9ff
> real memory  = 67043328 (65472K bytes)
>
> apm0:  on motherboard
> apm: found APM BIOS v1.2, connected at v1.2
> pcib0:  on motherboard
> pci0:  on pcib0
> vga-pci0:  irq 11 at device 2.0 on
pci0
> pcic0:  irq 11 at device 3.0 on pci0
> pcic1:  irq 11 at device 3.1 on pci0
> isab0:  at device 7.0 on pci0
> isa0:  on isab0
> ide_pci0:  at device 7.1 on pci0
> chip1:  irq 11 at device 7.2 on pci0
> intpm0:  at device 7.3 on pci0
> intpm0: I/O mapped 840
> intpm0: intr IRQ 9 enabled revision 0
> smbus0:  on intsmb0
> smb0:  on smbus0
> intpm0: PM I/O mapped 800
> pcm0:  at drq 1 flags 0x15 on isa0
> device_probe_and_attach: pcm0 attach returned 6
> devclass_alloc_unit: pcf0 already exists, using next available unit number
> pcf0 at port 0x320 irq 5 on isa0
> pcic: pccard bridge VLSI 82C146 (5 mem & 2 I/O windows)
>
> WARNING: driver smb should register devices with make_dev() (dev_t =
"#smb/0")
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
---


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

World breakage in libc_r?

[John Polstra]

I'm building world on an Alpha and have run into this:

building shared library libc_r.so.4
sigpending.So: In function `sigpending':
sigpending.S:2: multiple definition of `sigpending'
uthread_sigpending.So(.text+0x0):uthread_sigpending.c: first defined here
/usr/obj/a/src/tmp/usr/libexec/elf/ld: Warning: size of symbol `sigpending' changed 
from 68 to 36 in sigpending.So
uthread_sigsuspend.So: In function `sigsuspend':
uthread_sigsuspend.c(.text+0x0): multiple definition of `sigsuspend'
sigsuspend.So:sigsuspend.S:2: first defined here
/usr/obj/a/src/tmp/usr/libexec/elf/ld: Warning: size of symbol `sigsuspend' changed 
from 36 to 236 in uthread_sigsuspend.So
*** Error code 1

I know the cause of it and I know the fix.  The cause is this:

---
dfr 1999/10/09 05:11:32 PDT

  Modified files:
lib/libc/alpha/sys   Makefile.inc 
  Log:
  Remove old sig* wrappers.
  
  Revision  ChangesPath
  1.6   +2 -3  src/lib/libc/alpha/sys/Makefile.inc
---

and the fix is to add sigpending.o and sigsuspend.o to the
definition of HIDDEN_SYSCALLS in "src/lib/libc_r/Makefile".

But there was a similar commit for the i386 a few hours later, and I
haven't heard any complaints about this breakage on i386 systems.  I'm
reluctant to commit the fix for the Alpha until I understand why not,
because it will affect the i386 too.  Can any of you shed some light
on this?

John


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

Re: make buildworld breaks during vinum compilation

[Gianmarco Giovannelli]

At 13/10/99, Marc van Woerkom wrote:

> /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c: In function 
> `vinumioctl':
> /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c:333: too few 
> arguments to function `initsd'
> *** Error code 1

Me too ...



Best Regards,
Gianmarco Giovannelli ,  "Unix expert since yesterday"
http://www.giovannelli.it/~gmarco
http://www2.masternet.it





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

Re: Why Adaptec 1540 bombing?

[Warner Losh]

In message <[EMAIL PROTECTED]> FreeBSD Bob writes:
: The DPT did not run at all.   

I do not have access to the DPT controllers, nor to a EISA system for
testing.

: The 1540A did not run the 3.3 or 3.2,
: but came up fine on 2.2.6 or 2.2.8.  That got me to thinking that
: something had changed in the Adaptec driver and query what and why.

Yes.  CAM happened. :-)  The 1540A card had some interesting problems
with the setting of residuals which the 1540B and later do not have.
CAM requires these transfer counts be accurate or it can get
confused.  I tried to cope as best I could, but without access to an
actual card I couldn't verify that it worked.

Warner


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

Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?)

[zaph0d]

I also must agree for many tasks, IP filter proves superior than IPFW and
NATD for many things which I do.

It seems much more straightforward, more configurable, and also in many
respects more stable and reliable.

It would not bother me in the least if they simply yanked ipfw and natd
from the src tree, and included ipf/ipnat default (not in contrib).

If no one else desires to doso, i'd be happy to maintain whatever
communication or porting nessescary to keep it current and included in the
standard FreeBSD distribution. 


On Wed, 13 Oct 1999, Thomas Stromberg wrote:

> http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/ipnat/Attic/Makefile
> 
> 1.2 Sun Oct 10 15:08:35 1999 UTC by peter 
> CVS Tags: HEAD
> Diffs to 1.1 
> FILE REMOVED 
> 
> Nuke the old antique copy of ipfilter from the tree.  This is old enough
> to be dangerous.  It will better serve us as a port building a KLD,
> ala SKIP.
> 
> 
> Although a heads up in -CURRENT or -security about this would of been
> nice, ye old ipfilter is gone. I definitely cannot disagree with the
> fact that it is an antique copy, and it's a shame that no one seems to
> be taking care of it in the tree. At least in the past, ipfilter was for
> many a much better option then ipfw. Has ipfw improved to the point
> where it functions better as a company firewall then ipfilter? (Okay, so
> the group & user firewalling is neat, but not really applicable for a
> corporate border firewall)
> 
> ipfilters website: http://coombs.anu.edu.au/~avalon/ip-filter.html
> 
> For why I feel ipfilter is better then ipfw (this post was written back
> in December '98, ipfw may have changed greatly since):
> 
> 
>http://www.freebsd.org/cgi/getmsg.cgi?fetch=117538+122112+/usr/local/www/db/text/1998/freebsd-current/19981227.freebsd-current
>   
> (the big 'wanton atticizing discussion')
> 
> A summary of it being:
> 
> - Multiplatform. Runs on IRIX, Solaris, Linux. Comes shipped with
> FreeBSD, OpenBSD, and NetBSD. Keeps us in sync with the other BSD's. 
> - Better logging then ipfw (has ipfw improved? Thats why I switched to
> ipfilter in the first place) 
> 
> It's a shame that no one seems to want to maintain ipfilter in our tree.
> As far as a 'port building kld', I think this may not be the 'smartest'
> way, seeing as anyone who is running a serious firewall would disable
> kld's immediately anyhow. 
> 
> So my question is, what's the direction we're taking here?
> 
> -- 
> ===
> Thomas Stromberg,   Assistant IS Manager / Systems Guru
> smtp:[EMAIL PROTECTED] Research Triangle Commerce, Inc.
>   pots://919.380.9771 x3210
> ===
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-security" in the body of the message
> 



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

Re: Freebsd 4.0 and Linux

[Mike Smith]

> Hi 
>
>What depth of FreeBSD's support for Linux applications under 
>FreeBSD 4.0?  I can't seem to find adequate information online.  
>Does the support comply with our current requirements for Linux?:
>
>minimum kernel version: 2.0.34
>minimum glibc version: 2.0.7-19

Current state of the art is somewhere between RedHat 5.2 and RedHat 6.0.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




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

make buildworld breaks during vinum compilation

[Marc van Woerkom]

I got a stop here:

root@oranje# date; make buildworld
Wed Oct 13 15:34:04 CEST 1999
(...)
cc -O -pipe -DVINUMDEBUG -g -O  -DKERNEL -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-  
-I/usr/obj/usr/src/sys/modules/vinum -I/usr/obj/usr/src/sys/modules/vinum/@ 
-I/usr/obj/usr/src/tmp/usr/include -c 
/usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c
/usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c: In function `vinumioctl':
/usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c:333: too few arguments to 
function `initsd'
*** Error code 1

The verify argument seems missing:
   root@oranje# grep initsd ../../dev/vinum/*
   ../../dev/vinum/vinumext.h:int initsd(int, int);
   ../../dev/vinum/vinumio.h:int verify;   
 /* verify (initsd) */
   ../../dev/vinum/vinumioctl.c:return initsd(objno);
   ../../dev/vinum/vinumrevive.c:initsd(int sdno, int verify)
   ../../dev/vinum/vinumstate.c:ioctl_reply->error = initsd(objindex, 
data->verify); /* initialize another block */

Regards,
Marc




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

Re: SMP stack faults...

[Mike Smith]

> 
> Just a followup question on my question from a week ago or so ther was
> indeed a stack overflow I'd guess- I check the code path more carefully
> and there was a 2KB stack buffer there (oof)- and removing it seemed to
> make the problem go awaySo the question here is "Shouldn't this have
> been a more obvious fault"?

There's probably an argument here for putting a guard page below the 
UP-mode kernel stack, yes.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




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

Re: Why Adaptec 1540 bombing?

[FreeBSD Bob]

> In message <[EMAIL PROTECTED]> Darryl Okahata writes:
> :  If he can't, I've got a 1540A somewhere (in theory ;-) that I'd be
> : willing to lend out (if the address is in the US).  It's been years
> : since I've used it, and so I'm not 100% sure that it still works,
> : though.
> 
> Well, I could install 2.2.x onto a disk and see if that works there.
> Once I do that, I can then know if it works or not. :-)
> 
> Warner

Warner and Darryl.  The 2.2.x series seems to work fine on it
(what I am using on that machine now).  I also have a 1542C controller
that I could try.  Would that one be expected to be any different
from the 1540A?  I also have a Future Domain 16xx controller, and
a DPT 2012 series controller (the original dos EISA controller that
was in the machine).  My goal with the machine (a 1993ish Intel EISA
board with 32M ram, Phoenix bios, and badged Groupe Bull) was to
try the 3.3 and 4.x builds for some play.   I have been running 3.2
or 3.3 on all my other boxes, just fine on IDE controllers.  Since
I ran across these scsi controllers I was thinking of trying them.
The DPT did not run at all.   The 1540A did not run the 3.3 or 3.2,
but came up fine on 2.2.6 or 2.2.8.  That got me to thinking that
something had changed in the Adaptec driver and query what and why.

Any insights are appreciated.   If you need the board for testing,
I could probably arrange that, or, if you have a test snapshot I
could pick up, I could try that too.  What specific info would you
need from dmesg (assuming it will go far enough to get some messages)
or elsewhere?

>From memory, I think it got as far as listing the controller and/or
drives attached, then went off polling for devices and never came
back.  It did that from the 3.3-RELEASE and the 4.0-19990918 snap
(if I have my numbers correct on the snap).  I don't think I tried
3.0/3.1/3.2 on it.

Thanks

Bob



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

Re: Freebsd 4.0 and Linux

[Kris Kennaway]

On Wed, 13 Oct 1999, mariusz wrote:

>What depth of FreeBSD's support for Linux applications under 
>FreeBSD 4.0?

Pretty good - most things run without problems. But, the only definitive
answer is "try it and see".

>Does the support comply with our current requirements for Linux?:
>
>minimum kernel version: 2.0.34

We don't implement the Linux kernel as a whole; it's the API which is
implemented in FreeBSD's Linux mode (i.e. system calls). There aren't many
differences in this regard between the linux kernel versions.

>minimum glibc version: 2.0.7-19

The linux-base port currently installs glibc-2.0.7-29, but you're free to
add/remove RPMs as you see fit, just as with linux :-)

Kris


XOR for AES -- join the campaign!



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

Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?)

[Daniel C. Sobral]

Thomas Stromberg wrote:
> 
> It's a shame that no one seems to want to maintain ipfilter in our tree.
> As far as a 'port building kld', I think this may not be the 'smartest'
> way, seeing as anyone who is running a serious firewall would disable
> kld's immediately anyhow.

Your concerns notwithstanding, a kld is viable. A kld can be loaded
by, well, the loader.

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"I always feel generous when I'm in the inner circle of a
conspiracy to subvert the world order and, with a small group of
allies, just defeated an alien invasion. Maybe I should value myself
a little more?"



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

Re: COMMAND_SET ?

[Daniel C. Sobral]

Doug Rabson wrote:
> 
> On Tue, 12 Oct 1999, Chuck Robey wrote:
> 
> > I'm looking at sys/boot/common/pnp.c so I can find out how pnp is handled,
> > and I found something called a COMMAND_SET, and I can't figure out what it
> > means.  Any takers?
> 
> COMMAND_SET is a macro which is used to build the list of commands
> supported by the loader. The in-kernel pnp code is in
> sys/isa/{pnp.c,pnpparse.c,isa_common.c}.

Just to be obnoxiously pedantic, that is not strictly true. Loader
supports commands not defined with COMMAND_SET. Though Doug might be
refering to the alpha loader, of course. :-)

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"I always feel generous when I'm in the inner circle of a
conspiracy to subvert the world order and, with a small group of
allies, just defeated an alien invasion. Maybe I should value myself
a little more?"




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

Re: COMMAND_SET ?

[Daniel C. Sobral]

Chuck Robey wrote:
> 
> I'm looking at sys/boot/common/pnp.c so I can find out how pnp is handled,
> and I found something called a COMMAND_SET, and I can't figure out what it
> means.  Any takers?

It's a macro. :-) I thought it was defined in that same directory,
even.  It makes a list that is used to define the so-called builtin
commands of loader.

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"I always feel generous when I'm in the inner circle of a
conspiracy to subvert the world order and, with a small group of
allies, just defeated an alien invasion. Maybe I should value myself
a little more?"




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

Re: Proper Whacking & Weeding

[Daniel C. Sobral]

Marc van Woerkom wrote:
> 
> Drawback is speed. While CVSup mirrors the CVS repository quite fast
> I now need an additional cvs update to sync my source tree with the
> CVS repository. And that is quite slow. (But I am working on a
> program that will speed up this process)

Use a local cvsup daemon, and cvsup the source tree from your cvs
repository. Much faster than cvs update. :-)

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"I always feel generous when I'm in the inner circle of a
conspiracy to subvert the world order and, with a small group of
allies, just defeated an alien invasion. Maybe I should value myself
a little more?"




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

Re: package-like feature for the base distrib (was Re: FreeSSH)

[Patrick Bihan-Faou]

Hi,

From: Pierre Beyssac <[EMAIL PROTECTED]>

> There are a _lot_ of pitfalls to this kind of approach, as I have
> discovered using Linux Debian. This would probably open a can of
> worms you have no idea of. IMHO, the single biggest mistake in
> Debian is the all-encompassing package system which can make your
> life miserable in no time.

[...]

I was not talking about things that constitute the "real" core of the
distribution (kernel, basic libraries etc.). I was more thinking about
"userland" stuff that is included in the distribution but might not be
required by everybody. Sendmail for example is something I don't want since
I user qmail. However I have to remove it by hand... Other examples are bind
or perl.

Basically I think anything that has an equivalent and/or an alternate
installation method in/via the "ports" system should be registered with the
rest of the packages.

> And, IMHO, package handling for general-purpose applications and
> package handling for the core system are a very different problem
> and should be handled in very different ways.

Agreed. This is the key. The package/ports system is really great as is. The
split between the distribution and the packages/ports is sometime annoying.
Again I think this mostly concerns "userland" features that are not required
for the core of FreeBSD.


Patrick.

--
MindStep Corporation
www.mindstep.com




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

Re: FreeSSH

[Pierre Beyssac]

[ -security trimmed from Cc: ]

On Wed, Oct 13, 1999 at 11:11:43AM -0400, Patrick Bihan-Faou wrote:
> >pkg_delete lp
> >pkg_delete yp
> >
> >Has anyone done/tried this in the past, and if so, what was the
> > reaction?  Or what do people think?  I realize this sounds a bit like the
> > "everything is an rpm or dpkg" methodology from Linux, but as long as the
> > 'base' packages are handled automatically, then it shouldn't impose the
> > same inconvenience.
> 
> I think that it would be the next best thing since the package/ports system
> (as well as a logical step forward). I would love to see most of the things
> that installed with a "make world" be also registered in the package
> database. This would make things like upgrading bind, removing sendmail etc
> a lot easier.

There are a _lot_ of pitfalls to this kind of approach, as I have
discovered using Linux Debian. This would probably open a can of
worms you have no idea of. IMHO, the single biggest mistake in
Debian is the all-encompassing package system which can make your
life miserable in no time.

I have found this the hard way, because I have to administer a
network of Debian PCs. Any attempt to upgrade something, even a
minor application, rapidly turns into a dependency nigthmare forcing
you to update half of your system. This is made even worse by
endless changes in the glibc, itself included in the package system:
since you can code that dependency in the package system, many
packages require such and such version of the glibc. In turn,
frequent incompatible updates of the glibc are made by the developpers
with the excuse that it's all handled by the package system anyway...

To that, you can add several other flaws (broken stable vs unstable
policy, no /usr/local, many installation scripts asking for
interactive input...).

The bottom line is: I'm much happier with FreeBSD's use of
distributions for the base system than with a Debian-style package
system.

That is no to say there can be no good package system, but we have
to think twice before we implement anything like that, first and
foremost dependencies on system libraries.

And, IMHO, package handling for general-purpose applications and
package handling for the core system are a very different problem
and should be handled in very different ways.

The Solaris way, while far from perfect, is at least usable for
the most past to handle choice at installation and (not too frequent)
evolutions of system components.
-- 
Pierre Beyssac  [EMAIL PROTECTED]


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

Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?)

[Dima Ruban]

Darren Reed writes:
> Well, if someone had of answered my question (to cvs-committers)
> about getting an account fixed up on freefall(?) so I could use
> cvs again, it might not have been forgotten about for quite so
> long.  Maybe I sent the question to the "wrong place", but I
> received no answer to even indicate that!  hmpf!

Well, Mark Murray sent heads up note quite a while ago about freebsd.org
being converted to use krb5.

Send him email and I'm sure he'll help you to fix things.

> On a conspirital note, I think there are numerous ipfw advocates
> within freebsd who hate that ipfilter is better >;-)  Both NetBSD and
> OpenBSD ship with it, and if you're serious about security, maybe
> you should be using OpenBSD anyway, rather than FreeBSD.

Let's not start a flame war here. You posted it to FreeBSD mailing list.
I think it's fairly easy to imagine peoples reaction.

> 
> Darren
> 

-- dima


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

Re: FreeSSH

[James Howard]

On Wed, 13 Oct 1999, Patrick Bihan-Faou wrote:

> Hi All,
> 
> >It strikes me that having the base system be slightly more decomposed
> > could be advantageous.  It would be great to be able to do something like:
> >
> >pkg_delete lp
> >pkg_delete yp
> >
> >Has anyone done/tried this in the past, and if so, what was the
> > reaction?  Or what do people think?  I realize this sounds a bit like the
> > "everything is an rpm or dpkg" methodology from Linux, but as long as the
> > 'base' packages are handled automatically, then it shouldn't impose the
> > same inconvenience.

I just pulled -security and -stable from the CC.

I was talking with a friend of mine the other day about making FreeBSD
more modular.  It would be great if the system were based on "packages"
(not like the ports tree, architectually like the current tree, but
organizationally like the ports tree).

You could have a "net" package (telnet, tn3270, ftp, finger, etc), an "nw"
package (which included all new Netware stuff), an xpg compatability
package (which has lots of things need for XPG compatability), the yp and
lp packages listed above are a good idea, and development package (gdb, 
lint, etc), a mail package (mail, vacation, biff, comsat, sendmail etc)
a perl package, and anything else anyone else wants to abstract out.  Then
make the "base" anything absolutely required to have an operational
system.

This has the benefit of allowing the tree to grow and include new
functionality and prevent software from being pulled out and stuck in
ports (things like stat, tn3270, are much more convient when then are in
the tree).

A more or less randomly thought out email message.  

Jamie



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

Re: Freebsd 4.0 and Linux

[Kip Macy]

This for -questions, but 3.3-STABLE does so presumably current does as
well.
-Kip

On Wed, 13 Oct 1999, mariusz wrote:

> Hi 
>
>What depth of FreeBSD's support for Linux applications under 
>FreeBSD 4.0?  I can't seem to find adequate information online.  
>Does the support comply with our current requirements for Linux?:
>
>minimum kernel version: 2.0.34
>minimum glibc version: 2.0.7-19
>
> Mariusz
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 
> 




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

Iomega Ditto Max Parallel

[Douglas Kuntz]

Has anyone had any success using the parallel version of the Iomega Ditto
Max with current, or is there any support for it?

Douglas Kuntz



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

Re: ipfilter no longer in -CURRENT, whats the direction? (off toipfw?)

[Bill Fumerola]

On Wed, 13 Oct 1999, Thomas Stromberg wrote:

> So my question is, what's the direction we're taking here?

The author was given commit privledges to maintain this in the tree,
obviously this was not done. Peter encouraged a KLD port, and I hope
someone steps up and makes one.

Others have eluded to upgrading it, but I never see those imports.

It's a shame, but I'm glad that Peter cleared the bitrot.

-- 
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED]  -






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

Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?)

[John Polstra]

In article <[EMAIL PROTECTED]>,
Darren Reed  <[EMAIL PROTECTED]> wrote:

> Well, if someone had of answered my question (to cvs-committers)
> about getting an account fixed up on freefall(?) so I could use
> cvs again, it might not have been forgotten about for quite so
> long.  Maybe I sent the question to the "wrong place", but I
> received no answer to even indicate that!  hmpf!

You gave up too easily.  Do you think we're some kind of finely tuned
engine over here?  Send your mail again to [EMAIL PROTECTED], and nag
them every 3 days until your account is fixed.  (Don't bother nagging
next week, as everybody will be at FreeBSDCon.)

> On a conspirital note, I think there are numerous ipfw advocates
> within freebsd who hate that ipfilter is better >;-)

I don't think that's it.  The fact is, ipfilter was in terrible shape
in our source tree.  Nobody had done a thing with it since June of
1998.  From what I heard, it didn't even work reliably under 3.x.
(Did it even compile?)  Some of its source files were duplicated
in "src/contrib/ipfilter" and "src/sys/netinet", with different
versions of the files in the two places.  Working on it was basically
a nightmare.  I know because I did work on it for a client of mine.

I'm a big proponent of ipfilter's features.  I'd love to see it come
back if it were really going to be cleaned up and kept maintained.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra & Co., Inc.Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."-- Nora Ephron


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

Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?)

[John Polstra]

In article <[EMAIL PROTECTED]>,
Thomas Stromberg  <[EMAIL PROTECTED]> wrote:

> For why I feel ipfilter is better then ipfw (this post was written back
> in December '98, ipfw may have changed greatly since):
> 
> 
>http://www.freebsd.org/cgi/getmsg.cgi?fetch=117538+122112+/usr/local/www/db/text/1998/freebsd-current/19981227.freebsd-current
>   
> (the big 'wanton atticizing discussion')
> 
> A summary of it being:
> 
> - Multiplatform. Runs on IRIX, Solaris, Linux. Comes shipped with
> FreeBSD, OpenBSD, and NetBSD. Keeps us in sync with the other BSD's. 
> - Better logging then ipfw (has ipfw improved? Thats why I switched to
> ipfilter in the first place) 

And:

- IP filter does NAT completely inside the kernel
- IP filter has stateful filtering

I'd like to see it come back.  But that means it has to be brought
up to date first.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra & Co., Inc.Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."-- Nora Ephron


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

Re: FreeSSH

[Patrick Bihan-Faou]

Hi All,

>It strikes me that having the base system be slightly more decomposed
> could be advantageous.  It would be great to be able to do something like:
>
>pkg_delete lp
>pkg_delete yp
>
>Has anyone done/tried this in the past, and if so, what was the
> reaction?  Or what do people think?  I realize this sounds a bit like the
> "everything is an rpm or dpkg" methodology from Linux, but as long as the
> 'base' packages are handled automatically, then it shouldn't impose the
> same inconvenience.


I think that it would be the next best thing since the package/ports system
(as well as a logical step forward). I would love to see most of the things
that installed with a "make world" be also registered in the package
database. This would make things like upgrading bind, removing sendmail etc
a lot easier.

However I think that this discussion goes beyond the scope of the "security"
mailing list. I copied it to the "current" and "stable" lists as well. I
guess the discussion should be held in "current"...


Patrick.

--
MindStep Corporation
www.mindstep.com




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

k4 and pam

[Randy Bush]

it seems that, sans warning or UPDATE, pam is now used by k4.  but the
distributed pam.conf has not been hacked to make it obvious how to make
all this work.  is anyone working on this, or should i?

randy


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

Re: People getting automatically unsub'ed from -arch

[Brad Knowles]

At 4:19 PM +0200 1999/10/13, Andre Oppermann wrote:

> That is something qmail has done since the beginning.

With respect to qmail, I have no knowledge of that.  I do know 
that this feature was available in the first public beta of Postfix. 
It was introduced early in the "alpha" stage of Postfix, which from 
Wietse would be comparable to the late beta, gamma, or even "release" 
stages of software from many other authors.

>   I consider qmail and postfix equal, one is stronger
> in one direction whereas the other one is stronger in other aspects.

I am not aware of any advantages that qmail has over Postfix. 
However, I am aware of a number of advantages that I believe Postfix 
has over qmail.  Of course, this is more of that religious issue that 
we should only get into on private e-mail.

>I have no intend to "fight" religiously for qmail, the only
> thing I do is pointing out the strong aspects of qmail/ezmlm for
> big lists.

Support for VERPs definitely has its advantages, and I believe 
that this has long since been incorporated into Postfix.

Of course, I could be wrong -- it's been a very long time since I 
did much of anything with it, and I could be mis-remembering this 
feature.

> I would like, but you just said you would (can) not tell me about it...

At the moment, all I can say is that you should keep a very close 
eye on the releases of Sendmail Pro.  I expect these features to be 
incorporated into that code first, then make their way into RFCs, and 
be released as part of the freely available version of sendmail 
shortly thereafter.


Imagine orders of magnitude levels of reduction in the amount of 
traffic that would have to be transmitted to a remote MTA that serves 
more than one customer.

In fact, you could have MTAs distributed all around the world 
that have their own portion of the world that they serve, with very 
small amounts of data (streamed, even) that must be transmitted in 
order to serve the set of customers.

-- 
   These are my opinions -- not to be taken as official Skynet policy
  
|o| Brad Knowles, <[EMAIL PROTECTED]>Belgacom Skynet NV/SA |o|
|o| Systems Architect, News & FTP Admin  Rue Col. Bourg, 124   |o|
|o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels   |o|
|o| http://www.skynet.be Belgium   |o|
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
  Unix is like a wigwam -- no Gates, no Windows, and an Apache inside.
   Unix is very user-friendly.  It's just picky who its friends are.


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

Err - scratch that. Braino

[Mark Newton]

Ignore that last message (for reasons which are too
damaging to go into in any great depth :-)

- mark


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

4.0-CURRENT on Pentium 200

[Mark Newton]

I have a P200 running -current (from about a week ago) which 
announces that Pentium Pro MTRR support is enabled at boot time.

Is this something I should expect given that the machine isn't
running a Pentium Pro? :-)

   - mark



Mark Newton   Email:  [EMAIL PROTECTED] (W)
Network Engineer  Email:  [EMAIL PROTECTED]  (H)
Internode Systems Pty Ltd Desk:   +61-8-82232999
"Network Man" - Anagram of "Mark Newton"  Mobile: +61-416-202-223


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

Re: People getting automatically unsub'ed from -arch

[Andre Oppermann]

Brad Knowles wrote:
> 
> At 2:28 PM +0200 1999/10/13, Andre Oppermann wrote:
> > Nice paper! Most of the suggestions are already realized in qmail and
> > postfix.
> 
> I realize that Postfix already addresses many of these issues.  I
> was involved in the earlier stages of the beta testing for Postfix,
> and it (and private conversations with Wietse) figured very strongly
> in the development of the later stages of that paper.
> 
> In fact, I like to be able to claim that the idea for using Van
> Jacobsen TCP-style slow-start/bounded exponential backoff for
> parallelism and queue retries was an idea that I contributed to the
> development of Postfix, and is one of the many factors that make it
> superior.

That is something qmail has done since the beginning.

> Of course, that's starting down a rather religious path
> that I don't think we want to traverse.

No.

> >   The best is on page three, "handle at least tens of
> > thousands messages per day per server"... About a year ago I tested
> > qmail's performace with two old 486DX100/16MB/2GBIDE and 10BaseT
> > ethernet.
> 
> And Wietse has done more with less.  Again, more on that
> religious issue that I don't think we want to get started.

Well, the reason these numbers are so "low" is that qmail fsync()'s
every message to the disk. Softupdates was not available at that
time. But that's not the point. I was arguing against sendmail, not
against postfix. I consider qmail and postfix equal, one is stronger
in one direction whereas the other one is stronger in other aspects.

I for myselfs choose qmail for reasons I can tell you in private
email. I have no intend to "fight" religiously for qmail, the only
thing I do is pointing out the strong aspects of qmail/ezmlm for
big lists.

> > As long as these additional performance enhancements are not public
> > available I don't care.
> 
> I'm very surprised to hear that, since there are some extensions
> they've made that I believe will materially change the face of
> delivering customized content via e-mail, and will change it to the
> point where it is virtually completely unrecognizable from where we
> are today.
> 
> I'm sorry to learn that you don't want to learn about protocol
> enhancements of this kind of scale.

I would like, but you just said you would (can) not tell me about it...

-- 
Andre Oppermann

CEO / Geschaeftsfuehrer
Internet Business Solutions Ltd. (AG)
Hardstrasse 235, 8005 Zurich, Switzerland
Fon +41 1 277 75 75 / Fax +41 1 277 75 77
http://www.pipeline.ch[EMAIL PROTECTED]


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

Re: People getting automatically unsub'ed from -arch

[Brad Knowles]

At 2:28 PM +0200 1999/10/13, Andre Oppermann wrote:

>> You don't know all the hacks that they made to sendmail to make
>> it perform at previously unheard of levels.  ;-)
>
> Preciously unheard levels for sendmail?

No, previously unheard of levels -- period.

> Nice paper! Most of the suggestions are already realized in qmail and
> postfix.

I realize that Postfix already addresses many of these issues.  I 
was involved in the earlier stages of the beta testing for Postfix, 
and it (and private conversations with Wietse) figured very strongly 
in the development of the later stages of that paper.

In fact, I like to be able to claim that the idea for using Van 
Jacobsen TCP-style slow-start/bounded exponential backoff for 
parallelism and queue retries was an idea that I contributed to the 
development of Postfix, and is one of the many factors that make it 
superior.  Of course, that's starting down a rather religious path 
that I don't think we want to traverse.

>   The best is on page three, "handle at least tens of
> thousands messages per day per server"... About a year ago I tested
> qmail's performace with two old 486DX100/16MB/2GBIDE and 10BaseT
> ethernet.

And Wietse has done more with less.  Again, more on that 
religious issue that I don't think we want to get started.

> As long as these additional performance enhancements are not public
> available I don't care.

I'm very surprised to hear that, since there are some extensions 
they've made that I believe will materially change the face of 
delivering customized content via e-mail, and will change it to the 
point where it is virtually completely unrecognizable from where we 
are today.

I'm sorry to learn that you don't want to learn about protocol 
enhancements of this kind of scale.

-- 
   These are my opinions -- not to be taken as official Skynet policy
  
|o| Brad Knowles, <[EMAIL PROTECTED]>Belgacom Skynet NV/SA |o|
|o| Systems Architect, News & FTP Admin  Rue Col. Bourg, 124   |o|
|o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels   |o|
|o| http://www.skynet.be Belgium   |o|
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
  Unix is like a wigwam -- no Gates, no Windows, and an Apache inside.
   Unix is very user-friendly.  It's just picky who its friends are.


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

Re: Abit's BP6 and 'lmmon' or 'chm'

[Takanori Watanabe]

In message <[EMAIL PROTECTED]>, Kenneth 
Wayne Culver wrote:
>Will this solve the problem that your xmbmon seems to solve? With xmbmon I
>can look at the temps for my cpu, but with wmlmmon, it gives me the IOCTL
>error.
>

It can use both ISA interface (by opening /dev/io and banging port 
0x295 and 0x296) and SMBus interface.
And the ISA interface will work . If you try to use SMBus interface,
the same result will be there.

But ,with SMBus or with ISA, these are dangerous application.
So I think it should be treated with device driver.
My experimental driver is 
http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/sys/lm-dist.tar.gz
(May be for a bit older CURRENT)
But I wonder how do I specify bus to attach,so that I can prevent a
ttaching Hardware monitor to bktr i2c bus.

Takanori Watanabe
http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html">
Public Key
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 


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

Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?)

[Darren Reed]

Well, if someone had of answered my question (to cvs-committers)
about getting an account fixed up on freefall(?) so I could use
cvs again, it might not have been forgotten about for quite so
long.  Maybe I sent the question to the "wrong place", but I
received no answer to even indicate that!  hmpf!

On a conspirital note, I think there are numerous ipfw advocates
within freebsd who hate that ipfilter is better >;-)  Both NetBSD and
OpenBSD ship with it, and if you're serious about security, maybe
you should be using OpenBSD anyway, rather than FreeBSD.

Darren

In some mail from Thomas Stromberg, sie said:
> 
> http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/ipnat/Attic/Makefile
> 
> 1.2 Sun Oct 10 15:08:35 1999 UTC by peter 
> CVS Tags: HEAD
> Diffs to 1.1 
> FILE REMOVED 
> 
> Nuke the old antique copy of ipfilter from the tree.  This is old enough
> to be dangerous.  It will better serve us as a port building a KLD,
> ala SKIP.
> 
> 
> Although a heads up in -CURRENT or -security about this would of been
> nice, ye old ipfilter is gone. I definitely cannot disagree with the
> fact that it is an antique copy, and it's a shame that no one seems to
> be taking care of it in the tree. At least in the past, ipfilter was for
> many a much better option then ipfw. Has ipfw improved to the point
> where it functions better as a company firewall then ipfilter? (Okay, so
> the group & user firewalling is neat, but not really applicable for a
> corporate border firewall)
> 
> ipfilters website: http://coombs.anu.edu.au/~avalon/ip-filter.html
> 
> For why I feel ipfilter is better then ipfw (this post was written back
> in December '98, ipfw may have changed greatly since):
> 
> 
>http://www.freebsd.org/cgi/getmsg.cgi?fetch=117538+122112+/usr/local/www/db/text/1998/freebsd-current/19981227.freebsd-current
>   
> (the big 'wanton atticizing discussion')
> 
> A summary of it being:
> 
> - Multiplatform. Runs on IRIX, Solaris, Linux. Comes shipped with
> FreeBSD, OpenBSD, and NetBSD. Keeps us in sync with the other BSD's. 
> - Better logging then ipfw (has ipfw improved? Thats why I switched to
> ipfilter in the first place) 
> 
> It's a shame that no one seems to want to maintain ipfilter in our tree.
> As far as a 'port building kld', I think this may not be the 'smartest'
> way, seeing as anyone who is running a serious firewall would disable
> kld's immediately anyhow. 
> 
> So my question is, what's the direction we're taking here?
> 
> -- 
> ===
> Thomas Stromberg,   Assistant IS Manager / Systems Guru
> smtp:[EMAIL PROTECTED] Research Triangle Commerce, Inc.
>   pots://919.380.9771 x3210
> ===
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-security" in the body of the message
> 



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

ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?)

[Thomas Stromberg]

http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/ipnat/Attic/Makefile

1.2 Sun Oct 10 15:08:35 1999 UTC by peter 
CVS Tags: HEAD
Diffs to 1.1 
FILE REMOVED 

Nuke the old antique copy of ipfilter from the tree.  This is old enough
to be dangerous.  It will better serve us as a port building a KLD,
ala SKIP.


Although a heads up in -CURRENT or -security about this would of been
nice, ye old ipfilter is gone. I definitely cannot disagree with the
fact that it is an antique copy, and it's a shame that no one seems to
be taking care of it in the tree. At least in the past, ipfilter was for
many a much better option then ipfw. Has ipfw improved to the point
where it functions better as a company firewall then ipfilter? (Okay, so
the group & user firewalling is neat, but not really applicable for a
corporate border firewall)

ipfilters website: http://coombs.anu.edu.au/~avalon/ip-filter.html

For why I feel ipfilter is better then ipfw (this post was written back
in December '98, ipfw may have changed greatly since):

http://www.freebsd.org/cgi/getmsg.cgi?fetch=117538+122112+/usr/local/www/db/text/1998/freebsd-current/19981227.freebsd-current
   
(the big 'wanton atticizing discussion')

A summary of it being:

- Multiplatform. Runs on IRIX, Solaris, Linux. Comes shipped with
FreeBSD, OpenBSD, and NetBSD. Keeps us in sync with the other BSD's. 
- Better logging then ipfw (has ipfw improved? Thats why I switched to
ipfilter in the first place) 

It's a shame that no one seems to want to maintain ipfilter in our tree.
As far as a 'port building kld', I think this may not be the 'smartest'
way, seeing as anyone who is running a serious firewall would disable
kld's immediately anyhow. 

So my question is, what's the direction we're taking here?

-- 
===
Thomas Stromberg,   Assistant IS Manager / Systems Guru
smtp:[EMAIL PROTECTED] Research Triangle Commerce, Inc.
  pots://919.380.9771 x3210
===


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

Re: Still waiting for xl driver reports

[Thomas Stromberg]

Jim Bloom wrote:
> 
> I keep seeing a watchdog timeout with my 3c905B-TX every time the machine
> boots.  It seems to occur after everything has been probed and /etc/rc has
> completed; around the time I get my login banner. I am running the dhcp client
> to get my IP address.  I don't pound on the network very much so I can't tell
> you how performance is.
> 
> Jim Bloom

I get the same.. 

dmesg:
--
xl0: <3Com 3c905C-TX Fast Etherlink XL> irq 11 at device 14.0 on pci0
xl0: Ethernet address: 00:50:da:07:87:4c
..
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
sio2: not probed (disabled)
sio3: not probed (disabled)
changing root device to wd0s1a
WARNING: / was not properly dismounted
xl0: watchdog timeout
xl0: promiscuous mode enabled
xl0: watchdog timeout

uname:
--
FreeBSD asho.zarathushtra.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue
Oct 12 14:23:39 EDT 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/SPENTA_MAINYU  i386



-- 
===
Thomas Stromberg,   Assistant IS Manager / Systems Guru
smtp:[EMAIL PROTECTED] Research Triangle Commerce, Inc.
  pots://919.380.9771 x3210
===


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

Re: People getting automatically unsub'ed from -arch

[Jonathan M. Bresler]

Ben,

Majordomo has this facility, sending periodic reminder
messages; it is the bounces mailing list .  I used it for a couple
months.  The results were less than satisfactory.  Most people stayed
on the bounces mailing list indefinately.  ;(


jmb


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

Re: People getting automatically unsub'ed from -arch

[Andre Oppermann]

Brad Knowles wrote:
> 
> At 10:11 PM +0200 1999/10/12, Andre Oppermann wrote:
> >   They must be crazy to run a several million recipients
> > mailing list with sendmail...
> 
> You don't know all the hacks that they made to sendmail to make
> it perform at previously unheard of levels.  ;-)

Preciously unheard levels for sendmail?

Who want's spend weeks or days of sendmail tuning to get a peak
performace of x when it takes ten minutes to download and install qmail
or postfix which delivers that as sustained performance??

> If you want to see some of the ideas that I got from them (and
> others), take a look at the paper I presented at SANE'98 entitled
> "Sendmail Performance Tuning for Large Systems" at
> .

Nice paper! Most of the suggestions are already realized in qmail and
postfix. The best is on page three, "handle at least tens of
thousands messages per day per server"... About a year ago I tested
qmail's performace with two old 486DX100/16MB/2GBIDE and 10BaseT
ethernet. Guess what I was able to pump through them? 300'000 unique
messages of about 3KB in 24 hours. Guess what my current production
server can handle a day (PII-350/256MB/54GBSCSIRAID0+1)? About 2.5
million (too bad I don't have a T3). These numbers include the local
deliveries to the maildir.

> There
> are a number of additional enhancements that they made that I still
> can't talk about, however.

As long as these additional performance enhancements are not public
available I don't care.

-- 
Andre Oppermann

CEO / Geschaeftsfuehrer
Internet Business Solutions Ltd. (AG)
Hardstrasse 235, 8005 Zurich, Switzerland
Fon +41 1 277 75 75 / Fax +41 1 277 75 77
http://www.pipeline.ch[EMAIL PROTECTED]


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

Re: Abit's BP6 and 'lmmon' or 'chm'

[Takanori Watanabe]

In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote:
>In <[EMAIL PROTECTED]> Chris D. 
>Faulhaber <[EMAIL PROTECTED]> wrote:

>When I remove one of the CPUs and boot UP kernel on the same
>motherboard both 'chm' and 'lmmon' starts to work (also showed
>values for -5V and -12V looks strange).
Probably the Hardware sensor is not LM78/79 but W83781.

>   So the problems is in driver not working in SMP
>system. Are there any (general) hints where to look for
>such UP/SMP problems ?

I know the problem,but I cannot find out how it could be solved.
The reason is the driver does not catch intrrupt.
Wait a few days. I'll make a patch so that you can use polling 
mode for 'intpm'.

Takanori Watanabe
http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html">
Public Key
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 



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

Re: Abit's BP6 and 'lmmon' or 'chm'

[Chris D. Faulhaber]

On Wed, 13 Oct 1999 [EMAIL PROTECTED] wrote:

>   Additional information:
> 
> When I remove one of the CPUs and boot UP kernel on the same
> motherboard both 'chm' and 'lmmon' starts to work (also showed
> values for -5V and -12V looks strange).
> 

That's due to the conversion factors for the chips on the BP6 being
different than that of the LM78/79; simple fix if someone can test the
results.


-
Chris D. Faulhaber <[EMAIL PROTECTED]>  |  All the true gurus I've met never
System/Network Administrator,|  claimed they were one, and always
Reality Check Information, Inc.  |  pointed to someone better.




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

Re: Abit's BP6 and 'lmmon' or 'chm'

[nnd]

In <[EMAIL PROTECTED]> Chris D. 
Faulhaber <[EMAIL PROTECTED]> wrote:
> On Mon, 11 Oct 1999, Nickolay Dudorov wrote:
> 
>>  Does anybody successfully use ports/sysutils/{lmmon|chm}
>> with the Abit's BP6 motherboard ?
>> 
>>  After 'make install'-ing ports and adding
>> 
>> controller smbus0
>> controller iicbus0
>> controller iicbb0
>> controller intpm0
>> device smb0 at smbus?
>> 
>> to kernel config file (and config, make depend, make, make install,
>> reboot the new kernel) I only receive:
>> 
>> IOCTL: device not configured
>> 
>> from lmmon and chm.
>> 
> 
> This is due to the intpm controller not configuring the motherboards PM
> controller, not because the software.
> 
> I emailed Takanori Watanabe a while back concerning this MB.  His thoughts
> were that: 1) He hadn't heard of the driver working in an SMP environment;
> 2) It may be due to the controller using an unconfigured ISA interface.

Additional information:

When I remove one of the CPUs and boot UP kernel on the same
motherboard both 'chm' and 'lmmon' starts to work (also showed
values for -5V and -12V looks strange).

So the problems is in driver not working in SMP
system. Are there any (general) hints where to look for
such UP/SMP problems ?

N.Dudorov
 


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

Re: How to report problems (was: Request for Flames)

[Michael Lucas]

Greg,

Actually, I used your page (or its predecessor, it looks different
now) back when I started.  ;)

I'd like to do something more detailed on each type of problem.
Eventually, I'd like to turn this into a troubleshooting helper for
the most common problems.  But information gathering is the first
step.

Yes, "troubleshooting wizards" might be beneath FreeBSD's target
market, but with the sort of questions we get on -questions -- or even
-hackers -- I think it would be worthwhile.  Anything to slow the
growth of the mailing lists.

==ml


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

Re: COMMAND_SET ?

[Doug Rabson]

On Tue, 12 Oct 1999, Chuck Robey wrote:

> I'm looking at sys/boot/common/pnp.c so I can find out how pnp is handled,
> and I found something called a COMMAND_SET, and I can't figure out what it
> means.  Any takers?

COMMAND_SET is a macro which is used to build the list of commands
supported by the loader. The in-kernel pnp code is in
sys/isa/{pnp.c,pnpparse.c,isa_common.c}.

--
Doug Rabson Mail:  [EMAIL PROTECTED]
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




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

Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

[Doug Rabson]

On Tue, 12 Oct 1999, Warner Losh wrote:

> In message <[EMAIL PROTECTED]> Doug 
>Rabson writes:
> : Due to the nature of the pnp code, it might be probed as ed1 instead of
> : ed0.
> 
> I have a SBC here that has an onboard PNP ne2000 chip on it.  It comes
> up as ed1 because I have ed0 at a wired address.  I don't see ed0 at
> all, and it just works, so I just hacked my rc.conf to use ed1 rather
> than ed0 like I did when it ran 3.3R.
> 
> Now for the obligitory tangent:
> Does FreeBSD have the ability to reassign IRQs for PNP devices?  I
> have one that is coming up at IRQ 5, but I have a non-PNP device that
> is at 5, but many other IRQs free.  There is no way in the BIOS to set
> which IRQs are used for PNP and which ones are designated for legacy
> devices.

Right now, one can hack isa_find_irq() to restrict which interrupts it
checks. I have been thinking about using a loader environment variable for
this. One existing problem is that a pci device which doesn't match a
driver does not reserve its irq resource. Fixing that still leaves the
case of an unknown non-pnp isa device though.

--
Doug Rabson Mail:  [EMAIL PROTECTED]
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




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