From owner-freebsd-current Sun Nov 21 0: 0:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 6F6DE1517A; Sun, 21 Nov 1999 00:00:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA03550; Sat, 20 Nov 1999 23:51:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911210751.XAA03550@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Andrey A. Chernov" Cc: Mike Smith , Wilko Bulte , current@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Mount before SCSI comes up ? (was Re: Root mount failed:22 ???) In-reply-to: Your message of "Sat, 20 Nov 1999 02:45:55 +0300." <19991120024554.B5091@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 20 Nov 1999 23:51:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Nov 19, 1999 at 02:52:13PM -0800, Mike Smith wrote: > > > > The diagnostic is relatively harmless, but it suggests that /etc/fstab > > > > is wrong. > > > > > > Here is fstab line, please point what is wrong? > > > /dev/da0s4a / ufs rw,userquota 1 1 > > > > I have no idea; it'd be handy to know what it's trying to mount that's > > failing, but I don't recall that in your output. > > It is NOT say, what it tries to mount that failing :-( That's because it's not actually trying to mount anything. vfs_mountroot_try() is being called with a NULL argument, almost certainly because your loader is out of date (vfs.root.mountfrom does not exist in the environment). It's possible that there's a problem with the loader that's resulting in it not being set; you should instrument /sys/boot/common/boot.c:getrootmount() to determine this. It's also possible that it's being called for some other reason; you should look at vfs_mountroot() to see what else might be the culprit. > Here is quote in more wide scope. > Is it tries to mount root before SCSI devices come up? No; 22 is EINVAL, wheras you would exepect ENXIO (6) for that case. > Waiting 2 seconds for SCSI devices to settle > Creating DISK da0 > Creating DISK da1 > Root mount failed: 22 > Mounting root from ufs:da0s4a This completes successfully, so everything looks happy. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 0:14: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id E546E14D25 for ; Sun, 21 Nov 1999 00:13:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA03651; Sun, 21 Nov 1999 00:04:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911210804.AAA03651@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Gary Jennejohn Cc: "Andrey A. Chernov" , Mike Smith , Wilko Bulte , current@FreeBSD.ORG Subject: Re: Root mount failed:22 ??? In-reply-to: Your message of "Sat, 20 Nov 1999 00:04:37 +0100." <199911192304.AAA27959@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Nov 1999 00:04:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I see this: > > Root mount failed: 22 This suggests you may have an old loader, or the loader's parsing of your /etc/fstab file may be failing. I probably need to add a diagnostic to it to help us track this down. > Mounting root from ufs:da0s4a > [snip] > Root mount failed: 6 > Mounting root from ufs:da0a <-- this is defined in my config file This indicates that we're using the fallback code (intended for this purpose), and that you have a "truly dedicated" disk, ie. the s4 entry is "historically bogus", so whilst the kernel etc. was loaded using slice 4, the disk is not actually sliced at all. There would need to be _two_ error 6 failures before you got to the point where the compiled-in default was tried, I think. > It's normal. Some change which phk introduced into /sys/kern/vfs_conf.c, > I think. No. It _shouldn't_ be normal, provided that your /etc/fstab refers to the correct device. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 0:28: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext03.compaq.com (mailext03.compaq.com [207.18.199.41]) by hub.freebsd.org (Postfix) with ESMTP id 004C114D25 for ; Sun, 21 Nov 1999 00:28:04 -0800 (PST) (envelope-from bruceb@txn.cpqcorp.net) Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext03.compaq.com (Postfix) with ESMTP id 5614F152008; Sun, 21 Nov 1999 02:27:55 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id 54846BC4C2; Sun, 21 Nov 1999 02:27:49 -0600 (CST) Received: from fedex.txn.cpqcorp.net (fedex-s1.txn.cpqcorp.net [16.74.4.108]) by mailint02.im.hou.compaq.com (Postfix) with ESMTP id C4F60B2A43; Sun, 21 Nov 1999 02:27:48 -0600 (CST) From: bruce.burden@compaq.com Posted-Date: Sun, 21 Nov 1999 02:27:50 -0600 (CST) Received: (from bruceb@localhost) by panther.txn.cpqcorp.net (8.9.3/8.9.3) id CAA21469; Sun, 21 Nov 1999 02:24:32 -0600 (CST) Message-Id: <199911210824.CAA21469@panther.txn.cpqcorp.net> Subject: VERSION undefined in To: current@freebsd.org Date: Sun, 21 Nov 1999 02:24:32 -0600 (CST) Cc: 30@txn.cpqcorp.net, Nov@txn.cpqcorp.net, 18@txn.cpqcorp.net, hobbooks@panix.com (71), Confirm@txn.cpqcorp.net, ABE@txn.cpqcorp.net, Book@txn.cpqcorp.net, Inquiry:@FreeBSD.ORG, Technical@txn.cpqcorp.net, Manual@txn.cpqcorp.net, 155@txn.cpqcorp.net Reply-To: bruceb@devnull.mpd.tandem.com X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 0:31: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext02.compaq.com (mailext02.compaq.com [207.18.199.33]) by hub.freebsd.org (Postfix) with ESMTP id 16B7A151EB for ; Sun, 21 Nov 1999 00:31:00 -0800 (PST) (envelope-from bruceb@txn.cpqcorp.net) Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext02.compaq.com (Postfix) with ESMTP id 8B1919A85E for ; Sun, 21 Nov 1999 02:30:59 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id A05B8BC4C3; Sun, 21 Nov 1999 02:30:53 -0600 (CST) Received: from fedex.txn.cpqcorp.net (fedex-s1.txn.cpqcorp.net [16.74.4.108]) by mailint02.im.hou.compaq.com (Postfix) with ESMTP id 55C89B2A42 for ; Sun, 21 Nov 1999 02:30:53 -0600 (CST) From: bruce.burden@compaq.com Posted-Date: Sun, 21 Nov 1999 02:30:59 -0600 (CST) Received: (from bruceb@localhost) by panther.txn.cpqcorp.net (8.9.3/8.9.3) id CAA21479 for current@freebsd.org; Sun, 21 Nov 1999 02:27:42 -0600 (CST) Message-Id: <199911210827.CAA21479@panther.txn.cpqcorp.net> Subject: VERSION undefined in /usr/src/gnu/usr.bin/grep/grep.c To: current@freebsd.org Date: Sun, 21 Nov 1999 02:27:42 -0600 (CST) Reply-To: bruceb@devnull.mpd.tandem.com X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, here is the problem: cc -O -pipe -DGREP -DHAVE_STRING_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_UNISTD_H=1 -DHAVE_GETPAGESIZE=1 -DHAVE_MEMCHR=1 -DHAVE_STRERROR=1 -DHAVE_VALLOC=1 -DHAVE_WORKING_MMAP=1 -DHAVE_LIBZ=1 -DHAVE_FTS=1 -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/grep/dfa.c cc -O -pipe -DGREP -DHAVE_STRING_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_UNISTD_H=1 -DHAVE_GETPAGESIZE=1 -DHAVE_MEMCHR=1 -DHAVE_STRERROR=1 -DHAVE_VALLOC=1 -DHAVE_WORKING_MMAP=1 -DHAVE_LIBZ=1 -DHAVE_FTS=1 -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/grep/grep.c /usr/src/gnu/usr.bin/grep/grep.c: In function `main': /usr/src/gnu/usr.bin/grep/grep.c:1314: `VERSION' undeclared (first use in this function) /usr/src/gnu/usr.bin/grep/grep.c:1314: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/grep/grep.c:1314: for each function it appears in.) Here is the Makefile header: # $FreeBSD: src/gnu/usr.bin/grep/Makefile,v 1.18 1999/11/20 09:40:03 peter Exp $ MAINTAINER= wosch Obviously I could simply define anything I wanted for "VERSION" in the cflags, and go on my merry way, but I thought I would ask what VERSION was supposed to be, and point out that it is missing. Thanks, Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 0:53:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id DE5CC14DF7 for ; Sun, 21 Nov 1999 00:53:15 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 104 invoked by uid 1001); 21 Nov 1999 08:53:13 +0000 (GMT) To: mike@smith.net.au Cc: current@FreeBSD.ORG Subject: Re: Root mount failed:22 ??? From: sthaug@nethelp.no In-Reply-To: Your message of "Sun, 21 Nov 1999 00:04:21 -0800" References: <199911210804.AAA03651@dingo.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 21 Nov 1999 09:53:13 +0100 Message-ID: <102.943174393@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I see this: > > > > Root mount failed: 22 > > This suggests you may have an old loader, or the loader's parsing of > your /etc/fstab file may be failing. I probably need to add a > diagnostic to it to help us track this down. Okay, here's another one. I have 3.3-STABLE on wd0s1a, and -current (from 18. November) on wd0s1d. I boot this by pressing the space bar so I get the "boot: " prompt, and then typing "wd(0,d)kernel". This works fine, except I get the "Root mount failed" error message: ad0: ATA-4 disk at ata0 as master ad0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 31 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 ... Root mount failed: 22 Mounting root from ufs:wd0s1d This is what my fstab for -current looks like: # Device Mountpoint FStype Options Dump Pass# /dev/wd0s1b none swap sw 0 0 /dev/wd0s1d / ufs rw 1 1 /dev/wd0s1f /usr ufs rw 2 2 /dev/wd0s1h /local ufs rw 2 2 proc /proc procfs rw 0 0 With the commit you just did to vfs_conf.c I guess it'll be silent after the next time I've cvsup'ed and built world - I'm just wondering why this happens now. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 1: 1:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 54A7514DF7 for ; Sun, 21 Nov 1999 01:01:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA03911; Sun, 21 Nov 1999 00:51:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911210851.AAA03911@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sthaug@nethelp.no Cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: Root mount failed:22 ??? In-reply-to: Your message of "Sun, 21 Nov 1999 09:53:13 +0100." <102.943174393@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Nov 1999 00:51:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This suggests you may have an old loader, or the loader's parsing of > > your /etc/fstab file may be failing. I probably need to add a > > diagnostic to it to help us track this down. > > Okay, here's another one. I have 3.3-STABLE on wd0s1a, and -current > (from 18. November) on wd0s1d. I boot this by pressing the space bar > so I get the "boot: " prompt, and then typing "wd(0,d)kernel". This > works fine, except I get the "Root mount failed" error message: You should be using the loader to load the kernel. wd(0,d)/boot/loader would be correct. > With the commit you just did to vfs_conf.c I guess it'll be silent > after the next time I've cvsup'ed and built world - I'm just wondering > why this happens now. You're not using the loader, so nothing gets to read /etc/fstab and set vfs.root.mountfrom. Thus the kernel can't use it to find the root filesystem. I should probably emit a diagnostic to the effect that it wasn't set, since in many cases to come that will be fatal for the boot process. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 1:16:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 96F8F14DF7 for ; Sun, 21 Nov 1999 01:16:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id BAA04019; Sun, 21 Nov 1999 01:07:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911210907.BAA04019@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: NewATA on ISA and PCI In-reply-to: Your message of "Sat, 20 Nov 1999 10:27:05 +0200." <38365B59.3D5B2725@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Nov 1999 01:07:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please wrap your messages to 72 columns like other civilised authors. >>>> No, I do not talking about /etc/fstab, I'm talking about what device >>>> kernel is using to mount root *before* starting /sbin/init (e.g. >>>> "changing root device to ..." in dmesg). >>> >>> Hmm, the bootblock or the loader might be responsible.... >> >> This is -current. If the message is "changing root device to..." you >> are out of date and must update before we can help you. >> >> The root mount code has changed quite a lot just recently, and >> debugging the 'old' code isn't practical anymore. > > You are not right - I'm usually rebuilding kernel in one-three days, > and world in a week. My current kernel built from sources sup'ed > (cvsup.freebsd.org) yesterday. There is no room for me to be "not right"; the "changing root device to" message has been gone for quite some time now. If you are seeing it, you are "not right" and are running code built from old sources. To cover your original point; an up-to-date -current kernel correctly booted will mount the device listed in /etc/fstab as the root device "*before* starting /sbin/init". The re-mount of the root filesystem subsequently performed will actually re-use the device that's already mounted there, _not_ the entry from /etc/fstab (this is an enhancement designed to make life easier when /etc/fstab is not quite right, eg. when the kernel has had to guess about the root filesystem, or when it's been moved maually). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 1:52: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles519.castles.com [208.214.165.83]) by hub.freebsd.org (Postfix) with ESMTP id 8CF1D14DFD for ; Sun, 21 Nov 1999 01:52:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id BAA00370; Sun, 21 Nov 1999 01:42:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911210942.BAA00370@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Donn Miller Cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: dd and gzip'd files In-reply-to: Your message of "Sat, 20 Nov 1999 02:26:41 EST." <38364D31.F1AD476E@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Nov 1999 01:42:38 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I recently tried using dd to transfer a binary image to floppy. > > > It was the Linux root disk image, color.gz. Basically, dd works > > > ok with non-gzipped files, but with files in gzip format, it > > > chokes: > > > > > > root@lc186 floppies# dd if=color.gz of=/dev/rfd0 > > > dd: /dev/rfd0: Invalid argument > > > 2453+1 records in > > > 2453+0 records out > > > 1255936 bytes transferred in 42.665771 secs (29437 bytes/sec) > > > > > > Notice the line that says: > > > > > > 2453+1 records in > > > ^^^^^^ > > > > > > For some reason, it is offsetting to 1 before writing to disk. No, that's not what it means. You are ignoring the error message on the preceeding line. "2453+1" means that it has read 2453 complete records and one extra byte. The 'fd' driver has (correctly) refused to write the single trailing byte. > It appears to have worked. I guess the output block size of 16k > is key for floppies, then. The conv=osync does the padding. No, the block size requirement for floppies is 512 bytes, as it is for almost any device. conv=osync is correct if you insist on using the raw device. Note that the optimal block size for 1.44MB floppies is 9k (one track). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 2: 8:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 642EF14CDF for ; Sun, 21 Nov 1999 02:08:14 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id CAA46149; Sun, 21 Nov 1999 02:08:05 -0800 (PST) Date: Sun, 21 Nov 1999 02:08:04 -0800 (PST) From: Julian Elischer To: Mike Smith Cc: Donn Miller , Alfred Perlstein , current@FreeBSD.ORG Subject: Re: dd and gzip'd files In-Reply-To: <199911210942.BAA00370@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > It appears to have worked. I guess the output block size of 16k > > is key for floppies, then. The conv=osync does the padding. I use 18K (one cylinder) but any multiple of 9k should work well. > > No, the block size requirement for floppies is 512 bytes, as it is for > almost any device. conv=osync is correct if you insist on using the > raw device. as this is -current, we only have raw devices now, remember? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 4:47:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 7D65B151D5 for ; Sun, 21 Nov 1999 04:47:19 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id WAA28526; Sun, 21 Nov 1999 22:46:48 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma028522; Sun, 21 Nov 99 22:46:40 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id WAA13585 for ; Sun, 21 Nov 1999 22:36:34 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id WAA25549 for ; Sun, 21 Nov 1999 22:36:33 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id WAA27489; Sun, 21 Nov 1999 22:36:32 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199911211236.WAA27489@nymph.detir.qld.gov.au> To: freebsd-current@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Fsck follies Date: Sun, 21 Nov 1999 22:36:32 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was giving vinum + softupdates a bit of a workout on 4 really old SCSI disks (Sun shoeboxes, if you must know) attached to an aha1542B. The rest of the machine is a Pentium 133 with 64MB of parity ram, a few more disks, and another aha1542B. It runs -current (about 10 days old now). I was copying a newer -current source tree onto the box when I lost power to my house for maybe half a second. Being foolish and shortsighted, I have no UPS. (An interesting side note: out of the 3 machines in use at the time, 2 of the keyboards locked up and required a power down to recover. I was unaware that keyboards could crash.) When the system came back up, fsck -p didn't like the vinum volume. No sweat, I ran it manually. There were many INCORRECT BLOCK COUNT I= (4 should be 0) messages. I assumed this was an artifact of soft updates. The fsck completed successfully. Being paranoid, I reran fsck. This time it reported a number of unreferenced inodes (199 to be exact), and linked them in to lost+found. It is this last item that bothers me. When the first fsck completed, the filesystem should have been structurally correct. But it wasn't. A third fsck confirmed that 2 runs of fsck were enough. I seem to recall sagely advice from days gone by to always run fsck twice and sync thrice. I thought I could forget all that stuff nowadays. By the way, I saved the broken old source tree and compared it to the full tree. There were no unusual differences, except for the broken one being incomplete. So, if fsck were a little better, things would be fine. As good as you could expect, given a power failure. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 7:41: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgw.cablecom.ne.jp (mailgw.cablecom.ne.jp [202.248.199.37]) by hub.freebsd.org (Postfix) with ESMTP id E80D014D0E; Sun, 21 Nov 1999 07:40:42 -0800 (PST) (envelope-from motoyuki@snipe.rim.or.jp) Received: from srv2.cablecom.ne.jp by mailgw.cablecom.ne.jp (8.9.3/3.7W) id AAA22034; Mon, 22 Nov 1999 00:40:26 +0900 (JST) Received: from mail.snipe.rim.or.jp by srv2.cablecom.ne.jp (8.9.3/3.7W) id AAA08040; Mon, 22 Nov 1999 00:40:22 +0900 (JST) Received: from sakura.snipe.rim.or.jp (sakura.snipe.rim.or.jp [192.168.11.4]) by mail.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id AAA56761; Mon, 22 Nov 1999 00:40:19 +0900 (JST) Received: from sakura.snipe.rim.or.jp (localhost [127.0.0.1]) by sakura.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id AAA49063; Mon, 22 Nov 1999 00:40:19 +0900 (JST) Message-Id: <199911211540.AAA49063@sakura.snipe.rim.or.jp> To: knu@idaemons.org Cc: obrien@freebsd.org, ports@freebsd.org, freebsd-current@freebsd.org X-Mailer: mh-e on Mule 2.3 / Emacs 19.34.1 References: <19991120174617.J41154@daemon.ninth-circle.org> Subject: Re: flashplugin Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Mon, 22 Nov 1999 00:40:19 +0900 From: Motoyuki Konno Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Add Cc: to current... Hi, Jeroen Ruigrok/Asmodai wrote: > www/flashplugin dies under CURRENT's gcc 2.95.2 with: > > ===> Building for flashplugin-0.4.3 > c++ -O2 -pipe -I/usr/X11R6/include -I./Lib -I./Plugin -fpic -fno-rtti > -DXP_UNIX -O2 -DCHECK_TEXT_PLAIN -c ./Lib/bitmap.cc > {standard input}: Assembler messages: > {standard input}:1211: Error: no such 386 instruction: `fild' > *** Error code 1 > > Does not matter if I use -O or -O2 happens on both. > > Funy thing is I tried grepping in the sources for fild but couldn't find > it. > > Ideas are welcome to solve this since I am a little in the dark now. Gcc 2.95.2 output asmcodes which contain 'fild' opcode, but /usr/libexec/aout/as (a.out version of as) does not support 'fild'. # /usr/libexec/elf/as (elf version of as) support 'fild'. I found "make -DWANT_AOUT world" of today's -current fails for the same reason. ---------------- ===> libmp cc -O2 -m486 -pipe -I/usr/src/gnu/lib/libmp/../../../contrib/libgmp/mpn/x86 -I/usr/src/gnu/lib/libmp/../../../contrib/libgmp/mpz -DBERKELEY_MP -I/usr/src/gnu/lib/libmp/../../../contrib/libgmp -I/usr/src/gnu/lib/libmp/../../../contrib/libgmp/mpn/generic -DBROKEN_ALIGN -I/usr/obj/aout/usr/src/gnu/lib/libmp -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libmp/../../../contrib/libgmp/mpz/pow_ui.c -o mpz/pow_ui.o {standard input}: Assembler messages: {standard input}:52: Error: no such 386 instruction: `fild' *** Error code 1 Stop in /usr/src/gnu/lib/libmp. *** Error code 1 ---------------- I think we must add the 'fild' opcode to src/gnu/usr.bin/as/opcode/i386.h. -- ------------------------------------------------------------------------ Motoyuki Konno mkonno@res.yamanashi-med.ac.jp (Univ) motoyuki@snipe.rim.or.jp (Home) motoyuki@FreeBSD.ORG (FreeBSD Project) Yamanashi Medical University http://www.freebsd.org/~motoyuki/ (WWW) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 9:32:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id EE88F14D34 for ; Sun, 21 Nov 1999 09:32:25 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-155.skylink.it [194.185.55.155]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id SAA19288; Sun, 21 Nov 1999 18:32:53 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with SMTP id SAA06239; Sun, 21 Nov 1999 18:29:32 +0100 (CET) (envelope-from hibma@skylink.it) Date: Sun, 21 Nov 1999 18:29:31 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List Cc: USB BSD list Subject: HEADS UP: (USB only) usb.h changed, recompile usbdevs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HEADS UP: (USB only) Fields have been added to the usb_devinfo struct, so at least src/usr.sbin/usbdevs needs to be recompiled for the latest and greatest kernel. Ezload, available in ports/misc/ezload, as well if you use it. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 9:58:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id B431314DB9 for ; Sun, 21 Nov 1999 09:58:33 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA35922; Sun, 21 Nov 1999 09:57:57 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199911211757.JAA35922@gndrsh.dnsmgr.net> Subject: Re: dd and gzip'd files In-Reply-To: <199911210942.BAA00370@dingo.cdrom.com> from Mike Smith at "Nov 21, 1999 01:42:38 am" To: mike@smith.net.au (Mike Smith) Date: Sun, 21 Nov 1999 09:57:57 -0800 (PST) Cc: dmmiller@cvzoom.net (Donn Miller), bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I recently tried using dd to transfer a binary image to floppy. > > > > It was the Linux root disk image, color.gz. Basically, dd works > > > > ok with non-gzipped files, but with files in gzip format, it > > > > chokes: > > > > > > > > root@lc186 floppies# dd if=color.gz of=/dev/rfd0 > > > > dd: /dev/rfd0: Invalid argument > > > > 2453+1 records in > > > > 2453+0 records out > > > > 1255936 bytes transferred in 42.665771 secs (29437 bytes/sec) > > > > > > > > Notice the line that says: > > > > > > > > 2453+1 records in > > > > ^^^^^^ > > > > > > > > For some reason, it is offsetting to 1 before writing to disk. > > No, that's not what it means. You are ignoring the error message on > the preceeding line. "2453+1" means that it has read 2453 complete > records and one extra byte. The 'fd' driver has (correctly) refused to > write the single trailing byte. Small technical correction, the value after the + is not bytes, but number of partial blocks: When finished, dd displays the number of complete and partial input and output blocks, truncated input records and odd-length byte-swapping blocks to the standard error output. A partial input block is one where less than the input block size was read. A partial output block is one where less than the output block size was written. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 10: 0:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id DAAD714DA8 for ; Sun, 21 Nov 1999 10:00:21 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id NAA02690; Sun, 21 Nov 1999 13:00:20 -0500 (EST) Message-ID: <19991121130020.A2369@netmonger.net> Date: Sun, 21 Nov 1999 13:00:20 -0500 From: Christopher Masto To: Stephen McKay , freebsd-current@FreeBSD.ORG Subject: Re: Fsck follies Mail-Followup-To: Stephen McKay , freebsd-current@FreeBSD.ORG References: <199911211236.WAA27489@nymph.detir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199911211236.WAA27489@nymph.detir.qld.gov.au>; from Stephen McKay on Sun, Nov 21, 1999 at 10:36:32PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 21, 1999 at 10:36:32PM +1000, Stephen McKay wrote: > When the system came back up, fsck -p didn't like the vinum volume. > No sweat, I ran it manually. There were many > > INCORRECT BLOCK COUNT I= (4 should be 0) > > messages. I assumed this was an artifact of soft updates. The fsck > completed successfully. > > Being paranoid, I reran fsck. This time it reported a number of > unreferenced inodes (199 to be exact), and linked them in to lost+found. > > It is this last item that bothers me. When the first fsck completed, > the filesystem should have been structurally correct. But it wasn't. > A third fsck confirmed that 2 runs of fsck were enough. Presumably you are using vinum for mirroring? I have had to stop doing so after trashing several filesystems. There are some serious bugs that allow the plexes to get out of sync; as reads from a mirror set are round-robin, this can be very bad. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 10:35: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 5195914D49 for ; Sun, 21 Nov 1999 10:34:36 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA17230 for ; Sun, 21 Nov 1999 19:34:31 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: a bad sysinstall/useredit problem From: Poul-Henning Kamp Date: Sun, 21 Nov 1999 19:34:31 +0100 Message-ID: <17228.943209271@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just tried to install a 4.0 snap on a machine with a 3com netcard, this doesn't work, and whats worse I can't make it work. The problem is that the ex0 or ie0 driver, I'm not sure which, hoses the 3com card such that the ep driver cannot read the serial eeprom. I used to be able to disable the ex0 and ie0 drivers in userconfig but that is no longer possible it seems. Anyone know enough about how userconfig works these days to fix this ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 11: 5:21 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id C697B14DD9; Sun, 21 Nov 1999 11:05:19 -0800 (PST) Date: Sun, 21 Nov 1999 11:05:19 -0800 From: "Andrey A. Chernov" To: Mike Smith Cc: sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: Root mount failed:22 ??? Message-ID: <19991121110519.A38340@freebsd.org> References: <102.943174393@verdi.nethelp.no> <199911210851.AAA03911@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199911210851.AAA03911@dingo.cdrom.com>; from mike@smith.net.au on Sun, Nov 21, 1999 at 12:51:59AM -0800 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 21, 1999 at 12:51:59AM -0800, Mike Smith wrote: > You're not using the loader, so nothing gets to read /etc/fstab and set > vfs.root.mountfrom. Thus the kernel can't use it to find the root > filesystem. I should probably emit a diagnostic to the effect that it > wasn't set, since in many cases to come that will be fatal for the boot > process. I just rebuild/reinstall -current /kernel and /sys/boot and update bootblocks via disklabel, as result diagnostic in question gone, but I _not_ see vfs.root.mountfrom variable in my sysctl -a output. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 12: 1: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id CA1AB14DF7; Sun, 21 Nov 1999 12:00:53 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p21-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.150]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id FAA21391; Mon, 22 Nov 1999 05:00:46 +0900 (JST) Message-ID: <38384DB9.AF5FC02A@newsguy.com> Date: Mon, 22 Nov 1999 04:53:29 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Andrey A. Chernov" Cc: Mike Smith , sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: Root mount failed:22 ??? References: <102.943174393@verdi.nethelp.no> <199911210851.AAA03911@dingo.cdrom.com> <19991121110519.A38340@freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > > On Sun, Nov 21, 1999 at 12:51:59AM -0800, Mike Smith wrote: > > You're not using the loader, so nothing gets to read /etc/fstab and set ^^^^^^ > > vfs.root.mountfrom. Thus the kernel can't use it to find the root > > filesystem. I should probably emit a diagnostic to the effect that it > > wasn't set, since in many cases to come that will be fatal for the boot > > process. > > I just rebuild/reinstall -current /kernel and /sys/boot and update > bootblocks via disklabel, as result diagnostic > in question gone, but I _not_ see vfs.root.mountfrom variable in my > sysctl -a output. Loader/kernel environment variables are not sysctls. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Then again maybe not going to heaven would be a blessing. Relkin liked a certain amount of peace and harmony, since there'd been a pronounced shortage of them in his own life; however, nothing but peace and harmony, forever and forever? He wasn't sure about that. And no beer? Very dubious proposition." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 12: 3:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles519.castles.com [208.214.165.83]) by hub.freebsd.org (Postfix) with ESMTP id DA70C15848; Sun, 21 Nov 1999 12:03:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA03284; Sun, 21 Nov 1999 11:53:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911211953.LAA03284@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: a bad sysinstall/useredit problem In-reply-to: Your message of "Sun, 21 Nov 1999 19:34:31 +0100." <17228.943209271@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Nov 1999 11:53:50 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I just tried to install a 4.0 snap on a machine with a 3com > netcard, this doesn't work, and whats worse I can't make it > work. > > The problem is that the ex0 or ie0 driver, I'm not sure which, > hoses the 3com card such that the ep driver cannot read the > serial eeprom. > > I used to be able to disable the ex0 and ie0 drivers in userconfig > but that is no longer possible it seems. > > Anyone know enough about how userconfig works these days to fix this ? Er, it ought to still be possible. What happens when you try? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 12:10:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles519.castles.com [208.214.165.83]) by hub.freebsd.org (Postfix) with ESMTP id ED9D814E2B; Sun, 21 Nov 1999 12:10:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA03373; Sun, 21 Nov 1999 12:01:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911212001.MAA03373@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Andrey A. Chernov" Cc: Mike Smith , sthaug@nethelp.no, current@freebsd.org Subject: Re: Root mount failed:22 ??? In-reply-to: Your message of "Sun, 21 Nov 1999 11:05:19 PST." <19991121110519.A38340@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Nov 1999 12:01:15 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Nov 21, 1999 at 12:51:59AM -0800, Mike Smith wrote: > > You're not using the loader, so nothing gets to read /etc/fstab and set > > vfs.root.mountfrom. Thus the kernel can't use it to find the root > > filesystem. I should probably emit a diagnostic to the effect that it > > wasn't set, since in many cases to come that will be fatal for the boot > > process. > > I just rebuild/reinstall -current /kernel and /sys/boot and update > bootblocks via disklabel, as result diagnostic > in question gone, but I _not_ see vfs.root.mountfrom variable in my > sysctl -a output. I had hoped I made it clear earlier; vfs.root.mountfrom is a kernel environment variable, not a sysctl variable. You can read the kernel environment from the kern.environment sysctl in a slightly non-obvious fashion: get the oid for kern.environment (two values), then add one more value to the oid and iterate it from 0 until you receive ENOENT. Each read will return one string from the kernel environment. You're probably right in that it should be exposed in the sysctl space, yes. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 12:11:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7E66815838 for ; Sun, 21 Nov 1999 12:11:09 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA17644; Sun, 21 Nov 1999 21:10:26 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: current@freebsd.org Subject: Re: a bad sysinstall/useredit problem In-reply-to: Your message of "Sun, 21 Nov 1999 11:53:50 PST." <199911211953.LAA03284@dingo.cdrom.com> Date: Sun, 21 Nov 1999 21:10:25 +0100 Message-ID: <17637.943215025@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911211953.LAA03284@dingo.cdrom.com>, Mike Smith writes: >> >> I just tried to install a 4.0 snap on a machine with a 3com >> netcard, this doesn't work, and whats worse I can't make it >> work. >> >> The problem is that the ex0 or ie0 driver, I'm not sure which, >> hoses the 3com card such that the ep driver cannot read the >> serial eeprom. >> >> I used to be able to disable the ex0 and ie0 drivers in userconfig >> but that is no longer possible it seems. >> >> Anyone know enough about how userconfig works these days to fix this ? > >Er, it ought to still be possible. What happens when you try? It doesn't even show the ie0 driver in visual mode... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 12:34:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.monmouth.com (shell.monmouth.com [205.231.236.9]) by hub.freebsd.org (Postfix) with ESMTP id 9C57B15208 for ; Sun, 21 Nov 1999 12:34:10 -0800 (PST) (envelope-from pechter@pechter.dyndns.org) Received: from pechter.dyndns.org (bg-tc-ppp534.monmouth.com [209.191.63.94]) by shell.monmouth.com (8.9.3/8.9.3) with ESMTP id PAA21589 for ; Sun, 21 Nov 1999 15:31:57 -0500 (EST) Received: (from pechter@localhost) by pechter.dyndns.org (8.9.3/8.9.3) id PAA03509 for freebsd-current@freebsd.org; Sun, 21 Nov 1999 15:33:25 -0500 (EST) (envelope-from pechter) From: Bill Pechter Message-Id: <199911212033.PAA03509@pechter.dyndns.org> Subject: failure in build To: freebsd-current@freebsd.org Date: Sun, 21 Nov 1999 15:33:25 -0500 (EST) Reply-To: bpechter@shell.monmouth.com X-Phone-Number: 908-389-3592 X-OS-Type: FreeBSD 4.0-CURRENT X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been seeing this failure since I tried to rebuild my system (last built on 10/9/99 I didn't see anything in UPDATING or on this list. I'm wondering if there's a possible hardware problem -- but it's done it 3 times and I've cvsup'd three times yesterday and today and started with the same source tree... while in /usr/src/gnu/lib ===> libdialog ===> libgcc ===> libgcc_r ===> libgmp ===> libgmp/doc ===> libmp cc -O -pipe -mcpu=i386 -I/usr/src/gnu/lib/libmp/../../../contrib/libgmp/mpn/x86 -I/usr/src/gnu/lib/libmp/../../../contrib/libgmp/mpz -DBERKELEY_MP -I/usr/src/gnu/lib/libmp/../../../contrib/libgmp -I/usr/src/gnu/lib/libmp/../../../contrib/libgmp/mpn/generic -DBROKEN_ALIGN -I/usr/obj/aout/usr/src/gnu/lib/libmp -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libmp/../../../contrib/libgmp/mpz/pow_ui.c -o mpz/pow_ui.o {standard input}: Assembler messages: {standard input}:54: Error: no such 386 instruction: `fild' *** Error code 1 Stop in /usr/src/gnu/lib/libmp. *** Error code 1 Stop in /usr/src/gnu/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- bpechter@shell.monmouth.com|pechter@pechter.dyndns.org Three things never anger: First, the one who runs your DEC, The one who does Field Service and the one who signs your check. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 13: 2:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles519.castles.com [208.214.165.83]) by hub.freebsd.org (Postfix) with ESMTP id A1AD314E67 for ; Sun, 21 Nov 1999 13:02:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA03767; Sun, 21 Nov 1999 12:52:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911212052.MAA03767@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein Cc: current@freebsd.org Subject: Re: installing onto ami mega raid. In-reply-to: Your message of "Mon, 15 Nov 1999 02:39:26 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Nov 1999 12:52:08 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I spent about 2 to 3 hours last night futzing with sysinstall and > getting the amr.ko file onto the 4.0 install disk (using the > 4.0-19991114 SNAP) I tried adding the amr disks to devices.c in > sysinstall but had no luck. Bah. I knew I forgot something there. That should just about have done it. > After booting the install disks and loading the amr kld (the probe > messages showed that it was detected) I escaped to the prompt > (alt+f4). I saw that the amrd0 /dev/ entries had been created, > but attempts to access them gave "unit 0 not available" (as far as > i remeber) That's not an error message that the driver can produce. It'd be helpful to know what it actually said, and whether you have actually created an array yet. > What exactly needs to be done to get 4.0 installed with a amr disk > as root? Sysinstall needs the patch you supplied; apart from that I'm not aware of anything else. I haven't, obviously, had time to work on this yet. A better diagnostic from you above would save me at least one release build... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 13: 7:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id AE7DE151AD for ; Sun, 21 Nov 1999 13:07:10 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id NAA07317; Sun, 21 Nov 1999 13:33:51 -0800 (PST) Date: Sun, 21 Nov 1999 13:33:51 -0800 (PST) From: Alfred Perlstein To: Mike Smith Cc: current@freebsd.org Subject: Re: installing onto ami mega raid. In-Reply-To: <199911212052.MAA03767@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Nov 1999, Mike Smith wrote: > > > > I spent about 2 to 3 hours last night futzing with sysinstall and > > getting the amr.ko file onto the 4.0 install disk (using the > > 4.0-19991114 SNAP) I tried adding the amr disks to devices.c in > > sysinstall but had no luck. > > Bah. I knew I forgot something there. That should just about have > done it. > > > After booting the install disks and loading the amr kld (the probe > > messages showed that it was detected) I escaped to the prompt > > (alt+f4). I saw that the amrd0 /dev/ entries had been created, > > but attempts to access them gave "unit 0 not available" (as far as > > i remeber) > > That's not an error message that the driver can produce. It'd be > helpful to know what it actually said, and whether you have actually > created an array yet. > > > What exactly needs to be done to get 4.0 installed with a amr disk > > as root? > > Sysinstall needs the patch you supplied; apart from that I'm not aware > of anything else. I haven't, obviously, had time to work on this yet. > A better diagnostic from you above would save me at least one release > build... Unfortunatly all the amr systems I have are now in production, I can not test a new install on them. The way I did manage to do the install was nfs mounting another machine's /, /usr, and /var then using dump/restore to init the system over a hand done disklabel on the amr (disklabel, not sysinstall). I'm sorry. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 14: 8:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 42A8E14C04 for ; Sun, 21 Nov 1999 14:08:37 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id E1A801C2B; Sun, 21 Nov 1999 16:10:02 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id DE189381B; Sun, 21 Nov 1999 16:10:02 -0500 (EST) Date: Sun, 21 Nov 1999 16:10:02 -0500 (EST) From: Bill Fumerola To: Alfred Perlstein Cc: Mike Smith , jthiel@chc-chimes.com Subject: Re: installing onto ami mega raid. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moving this off -current] On Sun, 21 Nov 1999, Alfred Perlstein wrote: > Unfortunatly all the amr systems I have are now in production, I can > not test a new install on them. > > The way I did manage to do the install was nfs mounting another > machine's /, /usr, and /var then using dump/restore to init the > system over a hand done disklabel on the amr (disklabel, not sysinstall). > > I'm sorry. Mike, I have a brand spanking new poweredge with PERC SC/2 give me (or Jeremy, CC'd) a call at the number in my .signature and we'll test whatever you want us to. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - PS. Jeremy, I'm talking about 'tiger'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 15:54:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6409F158AF for ; Sun, 21 Nov 1999 15:54:12 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id PAA13800 for ; Sun, 21 Nov 1999 15:54:11 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA18504 for current@freebsd.org; Sun, 21 Nov 1999 15:54:11 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 21 Nov 1999 15:54:11 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: Route table leaks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Have any of you been seeing route table leaks in -current? I noticed this week that cvsup-master.freebsd.org is suffering from them. I actually had to reboot it because it couldn't allocate any more. From the "vmstat -m" output: Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) [...] routetbl150907 21221K 21221K 21221K 462184 0 0 16,32,64,128,256 Watching it again now after the reboot, the {In,Mem,High}Use numbers are climbing steadily. Also the references to the default route as reported by "netstat -rn" are climbing. (They went from 187 to 193 in the past 2 minutes or so.) The machine is running -current from September 29. It's only doing a couple of things: * Running a CVSup server for the mirrors. * Running a shell script which does a CVSup from freefall every 6 minutes, or as fast as it can go when it takes longer than that. The only other network daemons running on the machine are routed, syslogd, xntpd, portmap, ypbind, sshd, and sendmail (in outbound-only mode). No NFS, no amd. I can think of some experiments to try in order to start to diagnose it. But first, have any of you seen this problem? John -- John Polstra jdp@polstra.com 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 17:38:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from FreeBSD.ORG (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (Postfix) with ESMTP id CA4EC14C88 for ; Sun, 21 Nov 1999 17:38:54 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.3) id CAA00557; Mon, 22 Nov 1999 02:40:43 +0100 (MET) (envelope-from jmz@FreeBSD.ORG) Date: Mon, 22 Nov 1999 02:40:43 +0100 (MET) Message-Id: <199911220140.CAA00557@qix.jmz.org> From: Jean-Marc Zucconi To: current@FreeBSD.ORG Subject: Netscape and -current X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This happens with a kernel/world from today: netscape is unusable. Most of the time it freezes after a few seconds. Here is the tail of kdump: 484 communicator-4.7 RET select 0 484 communicator-4.7 CALL old.sigprocmask(0x1,0) 484 communicator-4.7 RET old.sigprocmask 0 484 communicator-4.7 CALL gettimeofday(0xbfbfb874,0) 484 communicator-4.7 RET gettimeofday 0 484 communicator-4.7 CALL old.sigprocmask(0x3,0) 484 communicator-4.7 RET old.sigprocmask 0 484 communicator-4.7 CALL old.sigprocmask(0x1,0x2000) 484 communicator-4.7 RET old.sigprocmask 0 484 communicator-4.7 CALL select(0xa,0x50011f48,0,0x50011f08,0x50011efc) 484 communicator-4.7 RET select 0 484 communicator-4.7 CALL gettimeofday(0x50011dac,0) 484 communicator-4.7 RET gettimeofday 0 484 communicator-4.7 CALL old.sigprocmask(0x3,0) 484 communicator-4.7 RET old.sigprocmask 8192/0x2000 484 communicator-4.7 CALL gettimeofday(0x50011f60,0) 484 communicator-4.7 RET gettimeofday 0 484 communicator-4.7 PSIG SIGALRM caught handler=0x8fea40 mask=0x0 code=0x0 484 communicator-4.7 CALL sigreturn(0x50011ed4) 484 communicator-4.7 RET sigreturn -1 errno 14 Bad address Any idea? Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 17:50:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 9000615882 for ; Sun, 21 Nov 1999 17:50:51 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id UAA78559; Sun, 21 Nov 1999 20:50:48 -0500 (EST) (envelope-from wollman) Date: Sun, 21 Nov 1999 20:50:48 -0500 (EST) From: Garrett Wollman Message-Id: <199911220150.UAA78559@khavrinen.lcs.mit.edu> To: John Polstra Cc: current@FreeBSD.ORG Subject: Route table leaks In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > are climbing steadily. Also the references to the default route as > reported by "netstat -rn" are climbing. (They went from 187 to 193 in > the past 2 minutes or so.) What does `netstat -ran' say? You're not seeing all the routes without the `-a' flag. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 19: 1:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 8791814E3F for ; Sun, 21 Nov 1999 19:01:22 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9911-Fujitsu Gateway) id MAA07255; Mon, 22 Nov 1999 12:01:21 +0900 (JST) Received: from chisato.nd.net.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-9911-Fujitsu Domain Master) id MAA09766; Mon, 22 Nov 1999 12:01:20 +0900 (JST) Received: from localhost (dhcp7186.nd.net.fujitsu.co.jp [10.18.7.186]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id MAA16409 for ; Mon, 22 Nov 1999 12:01:19 +0900 (JST) To: freebsd-current@freebsd.org Subject: FYI: KAME netinet6 basic part is committed X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991122120134R.shin@nd.net.fujitsu.co.jp> Date: Mon, 22 Nov 1999 12:01:34 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 17 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, FYI, KAME(IPv6, IPsec, and etc update kit for BSDs, http://www.kame.net) netinet6 basic part is committed to freebsd-current. It doesn't yet include several important parts (e.g.no IPsec, no v6 multcast forwarding, no TCP/UDP for IPv6 yet), but now it can assigne IPv6 addr automatically and can reply to IPv6 ping, if the kernel is built with "INET6" kernel config option. Please take care because inpcb structure is changed to be shared between netinet and netinet6. You will need to update include files to build several inpcb aware tools and applications. (fstat, netstat, systat, etc) Yoshinobu Inoue KAME project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 19:58:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 69A4F14D45 for ; Sun, 21 Nov 1999 19:58:41 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA14547; Sun, 21 Nov 1999 19:58:40 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA18970; Sun, 21 Nov 1999 19:58:40 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199911220150.UAA78559@khavrinen.lcs.mit.edu> Date: Sun, 21 Nov 1999 19:58:40 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Garrett Wollman Subject: RE: Route table leaks Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > < said: > >> are climbing steadily. Also the references to the default route as >> reported by "netstat -rn" are climbing. (They went from 187 to 193 in >> the past 2 minutes or so.) > > What does `netstat -ran' say? You're not seeing all the routes > without the `-a' flag. It lists some additional routes with -a, but not many. Here's the latest output (still growing, as you can see): cvsup-master# vmstat -m | grep 'routetbl ' routetbl 822 115K 115K 21221K 2669 0 0 16,32,64,128,256 cvsup-master# netstat -ran Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 204.216.27.17 UGc 393 7 wb0 127.0.0.1 127.0.0.1 UH 3 19 lo0 194.151.64.11 204.216.27.17 UGHW 1 585 wb0 195.113.19.84 204.216.27.17 UGHW3 0 508 wb0 3569 203.139.121.132 204.216.27.17 UGHW3 0 352 wb0 3556 203.178.140.4 204.216.27.17 UGHW 1 867 wb0 204.216.27.3 204.216.27.17 UGHW3 0 9 wb0 3523 204.216.27.16/28 link#1 UC 0 0 wb0 204.216.27.17 0:0:c:4:2e:2e UHLW 7 0 wb0 261 204.216.27.18 0:a0:c9:97:e8:ae UHLW 0 38 wb0 1005 204.216.27.20 0:0:d7:0:4:14 UHLW 2 50 wb0 204.216.27.21 0:a0:c9:a6:e:a6 UHLW 2 188782 wb0 1002 204.216.27.26 link#1 UHLW 2 0 wb0 204.216.27.27 0:a0:c9:a5:f3:7f UHLW 2 32737 wb0 1051 204.216.27.31 ff:ff:ff:ff:ff:ff UHLWb 0 1 wb0 204.216.27.192/28 204.216.27.26 UGc 0 0 wb0 204.216.27.224/28 204.216.27.26 UGc 0 0 wb0 206.213.73.13 204.216.27.17 UGHW 1 62 wb0 John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 20:59:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 9446214A07 for ; Sun, 21 Nov 1999 20:59:41 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id OAA26707; Mon, 22 Nov 1999 14:58:51 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xmaa26613; Mon, 22 Nov 99 14:58:28 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id OAA10705; Mon, 22 Nov 1999 14:57:42 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id OAA10846; Mon, 22 Nov 1999 14:57:44 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id OAA47173; Mon, 22 Nov 1999 14:57:40 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199911220457.OAA47173@nymph.detir.qld.gov.au> To: Christopher Masto Cc: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Fsck follies References: <199911211236.WAA27489@nymph.detir.qld.gov.au> <19991121130020.A2369@netmonger.net> In-Reply-To: <19991121130020.A2369@netmonger.net> from Christopher Masto at "Sun, 21 Nov 1999 13:00:20 -0500" Date: Mon, 22 Nov 1999 14:57:39 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 21st November 1999, Christopher Masto wrote: >On Sun, Nov 21, 1999 at 10:36:32PM +1000, Stephen McKay wrote: >> When the system came back up, fsck -p didn't like the vinum volume. >> No sweat, I ran it manually. There were many >> >> INCORRECT BLOCK COUNT I= (4 should be 0) >> >> messages. I assumed this was an artifact of soft updates. The fsck >> completed successfully. >> >> Being paranoid, I reran fsck. This time it reported a number of >> unreferenced inodes (199 to be exact), and linked them in to lost+found. >> >> It is this last item that bothers me. When the first fsck completed, >> the filesystem should have been structurally correct. But it wasn't. >> A third fsck confirmed that 2 runs of fsck were enough. > >Presumably you are using vinum for mirroring? I have had to stop >doing so after trashing several filesystems. There are some serious >bugs that allow the plexes to get out of sync; as reads from a mirror >set are round-robin, this can be very bad. No, I was just striping them (4 x 660 MB disks, 96 KB interleave). Vinum had nothing to do with the problem. I was just reporting all the facts, just in case. I think there is a fault in fsck. Possibly it is because softupdates changed the rules. Having run md5 over the good copy and the broken (power failure interrupted) copy as well as everything in lost+found, I can say that no corrupted files survived, and everything in lost+found was a good copy of some file or other. So softupdates appears to be doing the right thing. But fsck didn't fix everything broken by the power interruption. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 21 22:12: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 801A814C1A for ; Sun, 21 Nov 1999 22:11:55 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with ESMTP id PAA43328; Mon, 22 Nov 1999 15:11:51 +0900 (JST) Message-Id: <199911220611.PAA43328@rina.r.dl.itc.u-tokyo.ac.jp> To: current@freebsd.org Cc: Seigo Tanimura Subject: HEADS UP! The bridge drivers for sound cards have been committed. From: Seigo Tanimura X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 22 Nov 1999 15:11:51 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The bridge drivers for sound cards have just been committed. These drivers will accomodate coming newmidi drivers. People using Sound Blaster 16/AWE32/AWE64/ViBRA16C/ViBRA16X should add sbc driver to your kernel config file in addition to pcm driver, rebuild and reinstall a new kernel. See LINT as well. This commit also adds pcm support for the following cards: GUS PnP and non-PnP ISA (gusc driver) Crystal Semiconductor CS461x/428x PCI (csa driver) For a GUS non-PnP ISA card, write down the configuration of your card to gusc, not pcm. Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 1:20:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 83E51158F1 for ; Mon, 22 Nov 1999 01:20:38 -0800 (PST) (envelope-from dirkx@webweaving.org) Received: from kim.ispra.webweaving.org (va-178.skylink.it [194.185.55.178]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id KAA28016; Mon, 22 Nov 1999 10:21:11 +0100 Received: from brunte.ispra.webweaving.org (brunte.ispra.webweaving.org [10.0.0.12]) by kim.ispra.webweaving.org (8.8.8/8.8.5) with ESMTP id JAA15664; Mon, 22 Nov 1999 09:18:30 GMT X-Passed: MX on Ispra.WebWeaving.org Mon, 22 Nov 1999 09:18:30 GMT and masked X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Mon, 22 Nov 1999 09:18:30 GMT Date: Mon, 22 Nov 1999 10:18:37 +0100 (CET) From: Dirk-Willem van Gulik X-Sender: dirkx@brunte.ispra.webweaving.org To: USB BSD list Cc: FreeBSD CURRENT Mailing List Subject: Re: [usb-bsd] HEADS UP: (USB only) usb.h changed, recompile usbdevs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Arg. And that breaks half the linux' compiles :-) DW On Sun, 21 Nov 1999, Nick Hibma wrote: > > HEADS UP: (USB only) > > Fields have been added to the usb_devinfo struct, so at least > src/usr.sbin/usbdevs needs to be recompiled for the latest and greatest > kernel. Ezload, available in ports/misc/ezload, as well if you use it. > > Nick > > > ------------------------------------------------------------------------ > Was the salesman clueless? Productopia has the answers. > http://clickhere.egroups.com/click/1702 > > > > -- Easily schedule meetings and events using the group calendar! > -- http://www.egroups.com/cal?listname=usb-bsd&m=1 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 1:49:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from host.cer.ntnu.edu.tw (cer.ntnu.edu.tw [140.122.119.9]) by hub.freebsd.org (Postfix) with ESMTP id 3D019158B3 for ; Mon, 22 Nov 1999 01:49:08 -0800 (PST) (envelope-from clive@host.cer.ntnu.edu.tw) Received: (from clive@localhost) by host.cer.ntnu.edu.tw (8.9.3/8.9.3) id RAA31127 for current@FreeBSD.ORG; Mon, 22 Nov 1999 17:52:19 +0800 (CST) (envelope-from clive) Date: Mon, 22 Nov 1999 17:52:19 +0800 From: Clive Lin To: current@FreeBSD.ORG Subject: ftpd is not listed in pam.conf Message-ID: <19991122175219.A31069@host.cer.ntnu.edu.tw> Reply-To: Clive Lin Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I couldn't remeber since when, I always see a message on my cosole: Nov 22 17:29:42 cartier ftpd[844]: no modules loaded for `ftpd' service Nov 22 17:29:42 cartier ftpd[844]: auth_pam: Permission denied Though it doesn't affect anything when I using ftp to transfer files from other hosts, it looks quite anonying. Then, I added a line into /etc/pam.conf, this message no longer appears. ftpd auth required pam_unix.so try_first_pass (yes, just Gyypcwftpd:wq) May this is not the best way for ftpd to use pam (many other lines for login, may ftpd should be so). But I think ftpd should be listed in /etc/pam.conf. Any plan to fix it in /usr/src/etc/pam.conf ? -- CirX Clive Lin FreeBSD - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 2: 9: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from wit395301.student.utwente.nl (wit395301.student.utwente.nl [130.89.235.121]) by hub.freebsd.org (Postfix) with ESMTP id DE58D14D2C for ; Mon, 22 Nov 1999 02:08:54 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from [10.235.121.14] (helo=vangelderen.org) by wit395301.student.utwente.nl with esmtp (Exim 2.05 #1) id 11pqMg-0003MU-00; Mon, 22 Nov 1999 11:06:30 +0100 Message-ID: <38391580.C3934B@vangelderen.org> Date: Mon, 22 Nov 1999 11:05:52 +0100 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Yoshinobu Inoue Cc: freebsd-current@FreeBSD.ORG Subject: Re: FYI: KAME netinet6 basic part is committed References: <19991122120134R.shin@nd.net.fujitsu.co.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yoshinobu Inoue wrote: > Hello, FYI, > KAME(IPv6, IPsec, and etc update kit for BSDs, http://www.kame.net) > netinet6 basic part is committed to freebsd-current. > > It doesn't yet include several important parts (e.g.no IPsec, > no v6 multcast forwarding, no TCP/UDP for IPv6 yet), > but now it can assigne IPv6 addr automatically and can reply > to IPv6 ping, if the kernel is built with "INET6" kernel > config option. > > Please take care because inpcb structure is changed to be > shared between netinet and netinet6. > You will need to update include files to build several inpcb > aware tools and applications. (fstat, netstat, systat, etc) Thanks! Cheers, Jeroen -- Jeroen C. van Gelderen - jeroen@vangelderen.org Interesting read: http://www.vcnet.com/bms/ JLF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 2:26: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 5B6BA14E1E for ; Mon, 22 Nov 1999 02:25:54 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=propro) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11pqfK-00051j-00 for freebsd-current@freebsd.org; Mon, 22 Nov 1999 10:25:46 +0000 Date: Mon, 22 Nov 1999 11:25:33 +0100 (CET) From: Marc Schneiders To: freebsd-current@freebsd.org Subject: make release failure in docproj/jade Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure whether I can send this to this list... Make release dies in the build of jade right now. c++ -ansi -O -pipe -fno-implicit-templates -I. -I./../include -I./../generic -DS TDC_HEADERS=1 -DHAVE_LIMITS_H=1 -Dconst= -Dinline= -DHAVE_ST_BLKSIZE=1 -DSP_HAVE _BOOL=1 -DSP_HAVE_LOCALE=1 -DSP_ANSI_CLASS_INST=1 -DSP_MULTI_BYTE=1 -c -fPIC -DP IC CharsetInfo.cxx In file included from ../include/CharsetInfo.h:11, from CharsetInfo.cxx:8: ../include/Vector.h: In instantiation of `Vector >': ../include/RangeMap.h:27: instantiated from `RangeMap' ../include/UnivCharsetDesc.h:73: instantiated from here ../include/Vector.h:50: `Vector >::oper ator [](unsigned int)' has already been declared in `Vector >' ../include/Vector.h:52: `Vector >::begi n()' has already been declared in `Vector >' ../include/Vector.h:54: `Vector >::back ()' has already been declared in `Vector >' In file included from ../include/StringOf.h:15, from ../include/StringC.h:8, from ../include/CharsetInfo.h:14, from CharsetInfo.cxx:8: /usr/include/string.h:53: warning: declaration of `int memcmp(void *, void *, un signed int)' /usr/include/string.h:53: warning: conflicts with built-in declaration `int memc mp(const void *, const void *, unsigned int)' /usr/include/string.h:54: warning: declaration of `void * memcpy(void *, void *, unsigned int)' /usr/include/string.h:54: warning: conflicts with built-in declaration `void * m emcpy(void *, const void *, unsigned int)' /usr/include/string.h:59: warning: declaration of `int strcmp(char *, char *)' /usr/include/string.h:59: warning: conflicts with built-in declaration `int strc mp(const char *, const char *)' /usr/include/string.h:61: warning: declaration of `char * strcpy(char *, char *) ' /usr/include/string.h:61: warning: conflicts with built-in declaration `char * s trcpy(char *, const char *)' /usr/include/string.h:64: warning: declaration of `size_t strlen(char *)' /usr/include/string.h:64: warning: conflicts with built-in declaration `unsigned int strlen(const char *)' ../include/Vector.h: In instantiation of `Vector >': ../include/ISet.h:25: instantiated from `ISet' CharsetInfo.cxx:89: instantiated from here ../include/Vector.h:50: `Vector >::operator [](unsigned int)' has already been declared in `Vector >' ../include/Vector.h:52: `Vector >::begin()' has already been declared in `Vector >' ../include/Vector.h:54: `Vector >::back()' has already b een declared in `Vector >' ../include/Vector.h: In instantiation of `Vector > ': ../include/ISet.h:25: instantiated from `ISet' CharsetInfo.cxx:105: instantiated from here ../include/Vector.h:50: `Vector >::operator [](uns igned int)' has already been declared in `Vector > ' ../include/Vector.h:52: `Vector >::begin()' has al ready been declared in `Vector >' ../include/Vector.h:54: `Vector >::back()' has alr eady been declared in `Vector >' ../include/StringOf.h: In instantiation of `String': CharsetInfo.cxx:129: instantiated from here ../include/StringOf.h:38: `String::operator [](unsigned int) ' has already been declared in `String' ../include/StringOf.h:40: `String::begin()' has already been declared in `String' *** Error code 1 Stop in /usr/ports/textproc/jade/work/jade-1.2.1/lib. *** Error code 1 [etc] Marc Schneiders marc@venster.nl marc@oldserver.demon.nl propro 11:20am up 10 days, 23:06, load average: 0.02 0.11 0.07 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 3:26:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 9F8E914C12 for ; Mon, 22 Nov 1999 03:26:23 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 947AC1932; Mon, 22 Nov 1999 12:27:01 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 9329949D2 for ; Mon, 22 Nov 1999 12:27:01 +0100 (CET) Date: Mon, 22 Nov 1999 12:27:01 +0100 (CET) From: Andrzej Bialecki To: freebsd-current@freebsd.org Subject: ANNOUNCE: SPY-0.1 - syscalls monitor Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, SPY allows you to monitor and/or selectively block syscalls on your system. It could be used either as a safety monitoring device, policy enforcement, or debugging tool. You can download the sources (NOTE: -current only) from: http://www.freebsd.org/~abial/spy-0.1.tgz Excerpt of README follows: --------------------------------------------------------------------- This kernel module allows you to selectivly monitor and/or disable execution of system calls (syscalls) on your system, and log detailed info to syslog service. It's sometimes desirable to monitor selected syscalls for security reasons, or for debugging. For example, many security holes are related to setuid/setgid programs. You can monitor and log all attempts to use these syscalls. You can also disable certain syscalls altogether, if you really know what you're doing... Already existing tools (like ktrace(1) or truss(1)) can provide much more detailed information, but they are more fit to tracing single processes or process groups, and not setting overall system policy (speaking of which: this module is an example of very primitive auditing and policy enforcing device). Features -------- Using SPY module you can set up your system to: * log detailed info on execution of any selected syscall. In case of a few most important ones, there are specific handlers to log also the arguments of the syscall in understandable format. They are as follows: execve, set*id, chdir, open, link, unlink, chmod, chown, mkdir, rmdir (You are welcome to add others :-) Any syscall can be monitored, but in general case its arguments cannot be interpreted. * set kind of information to be logged. You can restrict logging on a per syscall basis, with the following constraints (OR-ed): - uid or gid - superuser only - all users except superuser - combination of the above You can also adjust level of logging on a per syscall basis. There are three levels available: - basic: logs minimum information sufficient to identify the syscall and process owner - arg: logs also the arguments of the syscall, if possible - full: logs all information available. * disable selected syscalls, which prevents specified categories of users to use them at all, and any such attempt is logged. By default the SPY module logs attempts to use execve syscall by root owned processes, and setuid/setgid by any user owned process. Default mode for other syscalls, used when you add them to monitoring, is to log all uses with all arguments. --------------------------------------------------------------------- Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 4: 3:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 0EDE814C48 for ; Mon, 22 Nov 1999 04:03:27 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id OAA72949; Mon, 22 Nov 1999 14:02:46 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911221202.OAA72949@gratis.grondar.za> To: Clive Lin Cc: current@FreeBSD.ORG Subject: Re: ftpd is not listed in pam.conf Date: Mon, 22 Nov 1999 14:02:45 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > May this is not the best way for ftpd to use pam (many other lines for login, > may ftpd should be so). But I think ftpd should be listed in /etc/pam.conf. > > Any plan to fix it in /usr/src/etc/pam.conf ? On my list! :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 4:39:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CE53514C1F for ; Mon, 22 Nov 1999 04:39:45 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id EAA03185; Mon, 22 Nov 1999 04:38:17 -0800 Date: Mon, 22 Nov 1999 04:38:16 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Reynolds~ Cc: freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit driver In-Reply-To: <14351.20015.691962.888252@hip186.ch.intel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I'm *almost* there getting this driver to work well (it's now *just* managing to run without barfing all over memory). It's been a humiliating experience- I'm just not that hot with Network drivers as I spend most of my time in mass storage. This chipset is, uh, interesting too (as best as I can tell, any transmit decriptor of less than 60 bytes in length is either ignored or sent out with a frame error). And because I'm less experienced in doing NIC drivers, I'm sure folks will say, "You did WHAT? Why did you do that?"... So, I have some other items to take care of, but I plan to put this out for testing in a couple of weeks (slipped my original schedule, didn't I?).. Just wanted to let you know I hadn't forgotten and dropped it on the floor... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 5:27:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A70A914F93 for ; Mon, 22 Nov 1999 05:27:36 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.040 #1) id 11ptUx-000JwK-00; Mon, 22 Nov 1999 15:27:15 +0200 From: Sheldon Hearn To: Wes Morgan Cc: freebsd-current@FreeBSD.ORG Subject: Re: gdb trouble in 4.0-current In-reply-to: Your message of "Sat, 20 Nov 1999 20:24:47 EST." Date: Mon, 22 Nov 1999 15:27:15 +0200 Message-ID: <76651.943277235@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 20 Nov 1999 20:24:47 EST, Wes Morgan wrote: > (gdb) r > Starting program: /usr/home/by-tor/mms-0.90/./mms > warning: find_solib: Can't read pathname for load map: Bad address > > Segmentation fault (core dumped) You're not alone. The work-around is to compile with --static. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 5:42:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B63111528A for ; Mon, 22 Nov 1999 05:42:35 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p103-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id AAA26062; Tue, 23 Nov 1999 00:49:43 +1100 Date: Tue, 23 Nov 1999 00:42:09 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Sheldon Hearn Cc: Wes Morgan , freebsd-current@FreeBSD.ORG Subject: Re: gdb trouble in 4.0-current In-Reply-To: <76651.943277235@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Sheldon Hearn wrote: > > On Sat, 20 Nov 1999 20:24:47 EST, Wes Morgan wrote: > > > (gdb) r > > Starting program: /usr/home/by-tor/mms-0.90/./mms > > warning: find_solib: Can't read pathname for load map: Bad address > > > > Segmentation fault (core dumped) > > You're not alone. The work-around is to compile with --static. Even that is broken for attaching to running (statically linked) processes. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 5:52:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgw.cablecom.ne.jp (mailgw.cablecom.ne.jp [202.248.199.37]) by hub.freebsd.org (Postfix) with ESMTP id A025414C23 for ; Mon, 22 Nov 1999 05:51:54 -0800 (PST) (envelope-from motoyuki@snipe.rim.or.jp) Received: from srv2.cablecom.ne.jp by mailgw.cablecom.ne.jp (8.9.3/3.7W) id WAA23881; Mon, 22 Nov 1999 22:51:53 +0900 (JST) Received: from mail.snipe.rim.or.jp by srv2.cablecom.ne.jp (8.9.3/3.7W) id WAA00149; Mon, 22 Nov 1999 22:51:51 +0900 (JST) Received: from sakura.snipe.rim.or.jp (sakura.snipe.rim.or.jp [192.168.11.4]) by mail.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id WAA05588 for ; Mon, 22 Nov 1999 22:51:49 +0900 (JST) Received: from sakura.snipe.rim.or.jp (localhost [127.0.0.1]) by sakura.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id WAA08638 for ; Mon, 22 Nov 1999 22:51:49 +0900 (JST) Message-Id: <199911221351.WAA08638@sakura.snipe.rim.or.jp> To: freebsd-current@freebsd.org Subject: Re: failure in build X-Mailer: mh-e on Mule 2.3 / Emacs 19.34.1 References: <199911212033.PAA03509@pechter.dyndns.org> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=ISO-2022-JP Date: Mon, 22 Nov 1999 22:51:49 +0900 From: Motoyuki Konno Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Bill Pechter wrote: > I've been seeing this failure since I tried to rebuild my system > (last built on 10/9/99 > > I didn't see anything in UPDATING or on this list. I'm wondering if > there's a possible hardware problem -- but it's done it 3 times and > I've cvsup'd three times yesterday and today and started with the > same source tree... [snip] > {standard input}: Assembler messages: > {standard input}:54: Error: no such 386 instruction: `fild' I think this error happens because a.out version of as (/usr/libexec/aout/as) does not support `fild' instruction. Please see my post to -current ML, From: Motoyuki Konno Message-Id: <199911211540.AAA49063@sakura.snipe.rim.or.jp> Subject: Re: flashplugin Date: Mon, 22 Nov 1999 00:40:19 +0900 -- ------------------------------------------------------------------------ $B:#Ln(B $B85G7!w;3M|0e2JBg3X(B mkonno@res.yamanashi-med.ac.jp (Univ) motoyuki@snipe.rim.or.jp (Home) http://www.freebsd.org/~motoyuki/ (Web) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 6:32: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from [132.197.97.45] (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 75AB814D73; Mon, 22 Nov 1999 06:32:00 -0800 (PST) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by [132.197.97.45] (8.9.3/8.9.3) id JAA00447; Mon, 22 Nov 1999 09:30:35 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199911220140.CAA00557@qix.jmz.org> Date: Mon, 22 Nov 1999 09:30:35 -0500 (EST) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: Jean-Marc Zucconi Subject: RE: Netscape and -current Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The same here. CURRENT updated and built on Sunday causes native FreeBSD Netscape to lock up. Linux Netscape still works fine. On 22-Nov-99 Jean-Marc Zucconi wrote: > This happens with a kernel/world from today: netscape is unusable. > Most of the time it freezes after a few seconds. Here is the tail of > kdump: > 484 communicator-4.7 RET select 0 > 484 communicator-4.7 CALL old.sigprocmask(0x1,0) > 484 communicator-4.7 RET old.sigprocmask 0 > 484 communicator-4.7 CALL gettimeofday(0xbfbfb874,0) > 484 communicator-4.7 RET gettimeofday 0 > 484 communicator-4.7 CALL old.sigprocmask(0x3,0) > 484 communicator-4.7 RET old.sigprocmask 0 > 484 communicator-4.7 CALL old.sigprocmask(0x1,0x2000) > 484 communicator-4.7 RET old.sigprocmask 0 > 484 communicator-4.7 CALL select(0xa,0x50011f48,0,0x50011f08,0x50011efc) > 484 communicator-4.7 RET select 0 > 484 communicator-4.7 CALL gettimeofday(0x50011dac,0) > 484 communicator-4.7 RET gettimeofday 0 > 484 communicator-4.7 CALL old.sigprocmask(0x3,0) > 484 communicator-4.7 RET old.sigprocmask 8192/0x2000 > 484 communicator-4.7 CALL gettimeofday(0x50011f60,0) > 484 communicator-4.7 RET gettimeofday 0 > 484 communicator-4.7 PSIG SIGALRM caught handler=0x8fea40 mask=0x0 > code=0x0 > 484 communicator-4.7 CALL sigreturn(0x50011ed4) > 484 communicator-4.7 RET sigreturn -1 errno 14 Bad address > > Any idea? > > Jean-Marc > > -- > Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: Alexander N. Kabaev Date: 22-Nov-99 Time: 09:28:45 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 6:55:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 695BE158E0 for ; Mon, 22 Nov 1999 06:55:36 -0800 (PST) (envelope-from n_hibma@skylink.it) Received: from skylink.it (va-166.skylink.it [194.185.55.166]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id PAA13945; Mon, 22 Nov 1999 15:55:34 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id PAA66848; Mon, 22 Nov 1999 15:50:46 +0100 (CET) (envelope-from n_hibma@skylink.it) Date: Mon, 22 Nov 1999 15:50:46 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Dirk van Gulik Cc: USB BSD list , FreeBSD CURRENT Mailing List Subject: Re: [usb-bsd] Re: HEADS UP: (USB only) usb.h changed, recompile usbdevs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hm, I didn't see anything that looked like Linux in the ezload-0.2 program. Did we ever manage to get those diffs across? If not, could you sned them again and I _promise_ I will add them today. Nick > Arg. And that breaks half the linux' compiles :-) > > DW > > On Sun, 21 Nov 1999, Nick Hibma wrote: > > > > > HEADS UP: (USB only) > > > > Fields have been added to the usb_devinfo struct, so at least > > src/usr.sbin/usbdevs needs to be recompiled for the latest and greatest > > kernel. Ezload, available in ports/misc/ezload, as well if you use it. > > > > Nick > > > > > > ------------------------------------------------------------------------ > > Was the salesman clueless? Productopia has the answers. > > http://clickhere.egroups.com/click/1702 > > > > > > > > -- Easily schedule meetings and events using the group calendar! > > -- http://www.egroups.com/cal?listname=usb-bsd&m=1 > > > > > > > > > ------------------------------------------------------------------------ > Was the salesman clueless? Productopia has the answers. > http://clickhere.egroups.com/click/1702 > > > > -- 20 megs of disk space in your group's Document Vault > -- http://www.egroups.com/docvault/usb-bsd/?m=1 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 7:24:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from es-i2.fernuni-hagen.de (ES-i2.fernuni-hagen.de [132.176.7.81]) by hub.freebsd.org (Postfix) with ESMTP id C39F314CF9 for ; Mon, 22 Nov 1999 07:24:08 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from jfh00 (jfh00.fernuni-hagen.de [132.176.7.6]) by es-i2.fernuni-hagen.de (8.9.3/8.9.3) with SMTP id QAA26093 for ; Mon, 22 Nov 1999 16:21:45 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <003401bf34f4$eace0ca0$0607b084@fernunihagen.de> From: "Fritz Heinrichmeyer" To: References: Subject: patch to recognize my soundcard, communicator stopped working Date: Mon, 22 Nov 1999 15:21:50 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the good news: with the following patch my soundcard is recognized again (some machine cycles are wasted ..) *** sbc.c~ Mon Nov 22 07:07:45 1999 --- sbc.c Mon Nov 22 16:04:56 1999 *************** *** 133,138 **** --- 133,140 ---- case 0x45008c0e: /* Creative SB AWE64 (CTL0045) */ if (vend_id2 == 0xe4008c0e) s = "Creative SB AWE64 (CTL0045)"; + if (vend_id2 == 0xc5008c0e) + s = "Creative SB AWE64 (CTL00c5)"; break; #if notdef case 0x01200001: /* Avance Logic */ bad news: as others mentioned also communicator-4.7 is totally unuseable today (wo would use linux or freebsd without mozilla :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 7:29:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.geocrawler.com (sourceforge.net [209.81.8.17]) by hub.freebsd.org (Postfix) with ESMTP id 279A714BD2 for ; Mon, 22 Nov 1999 07:29:18 -0800 (PST) (envelope-from nobody@www.geocrawler.com) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id HAA06728; Mon, 22 Nov 1999 07:27:38 -0800 Date: Mon, 22 Nov 1999 07:27:38 -0800 Message-Id: <199911221527.HAA06728@www.geocrawler.com> To: freebsd-current@freebsd.org Subject: CFLAGS vs CXXFLAGS From: "Grisha Vasilyev" Reply-To: "Grisha Vasilyev" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message was sent from Geocrawler.com by "Grisha Vasilyev" Be sure to reply to that address. Hello All ! I have one little problem: make world works for me only with small patch in gnu/usr.bin/groff/Makefile.cfg: -INCLUDES= -I$(GROFF_DIST)/include +INCLUDES= -I. -I$(GROFF_DIST)/include -I$(.CURDIR)/../include +CXXFLAGS+=$(DEFINES) $(INCLUDES) without this, it fails to find includes... Can anyone explain me, where is the source of this problem? maybe compiler or make rules? Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 7:54:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 09AE914CF4 for ; Mon, 22 Nov 1999 07:54:53 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA84691; Mon, 22 Nov 1999 10:52:48 -0500 (EST) (envelope-from wollman) Date: Mon, 22 Nov 1999 10:52:48 -0500 (EST) From: Garrett Wollman Message-Id: <199911221552.KAA84691@khavrinen.lcs.mit.edu> To: John Polstra Cc: current@FreeBSD.ORG Subject: RE: Route table leaks In-Reply-To: References: <199911220150.UAA78559@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> [quoting me:] >> What does `netstat -ran' say? You're not seeing all the routes >> without the `-a' flag. > It lists some additional routes with -a, but not many. Here's the > latest output (still growing, as you can see): > cvsup-master# vmstat -m | grep 'routetbl ' > routetbl 822 115K 115K 21221K 2669 0 0 16,32,64,128,256 Hmmm. On one of my machines: Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) routetbl 171 24K 184K 10366K 976273 0 0 16,32,64,128,256 Looks fine. Another machine says: routetbl 2755 384K 394K 42708K 928043 0 0 16,32,64,128,256 It also tells me: root@xyz(49)$ netstat -ran | wc -l 118 root@xyz(50)$ netstat -ran | fgrep default default 18.24.10.3 UGc 25 13963 ti0 root@xyz(51)$ netstat -f inet -n | wc -l 1331 Now things start to make sense: root@xyz(55)$ netstat -f inet -n | fgrep CLOSING | wc -l 1287 (this machine still has the bug that Jonathan Lemon fixed). Now it's clear what's going on. The ``missing'' routes have been deleted from the routing table, but have not yet been freed because these old PCBs still hold a reference. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 8:35: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8895A14E50 for ; Mon, 22 Nov 1999 08:34:54 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id IAA17934; Mon, 22 Nov 1999 08:34:40 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id IAA19798; Mon, 22 Nov 1999 08:34:40 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199911221552.KAA84691@khavrinen.lcs.mit.edu> Date: Mon, 22 Nov 1999 08:34:40 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Garrett Wollman Subject: RE: Route table leaks Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > Now things start to make sense: > > root@xyz(55)$ netstat -f inet -n | fgrep CLOSING | wc -l > 1287 > > (this machine still has the bug that Jonathan Lemon fixed). Now it's > clear what's going on. The ``missing'' routes have been deleted from > the routing table, but have not yet been freed because these old PCBs > still hold a reference. Unfortunately, that doesn't seem to be it on cvsup-master: cvsup-master# netstat -nf inet Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 0 204.216.27.25.1379 204.216.27.21.5998 ESTABLISHED tcp 0 17520 204.216.27.25.1378 204.216.27.21.5999 ESTABLISHED tcp 0 0 204.216.27.25.5999 194.151.64.11.3112 ESTABLISHED tcp 0 60 204.216.27.25.22 206.213.73.13.3626 ESTABLISHED tcp 0 0 204.216.27.25.1377 204.216.27.21.5998 TIME_WAIT tcp 0 0 204.216.27.25.1376 204.216.27.21.5999 TIME_WAIT tcp 0 72 204.216.27.25.5999 195.205.77.13.2154 ESTABLISHED tcp 0 12 204.216.27.25.5999 193.193.193.113.3678 ESTABLISHED udp 0 0 127.0.0.1.123 *.* udp 0 0 204.216.27.25.123 *.* cvsup-master# vmstat -m | grep 'routetbl ' routetbl 2274 320K 320K 21221K 7424 0 0 16,32,64,128,256 cvsup-master# netstat -ran Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 204.216.27.17 UGc 1119 11 wb0 127.0.0.1 127.0.0.1 UH 3 28 lo0 130.240.16.109 204.216.27.17 UGHW 1 119 wb0 193.193.193.113 204.216.27.17 UGHW 1 111 wb0 194.151.64.11 204.216.27.17 UGHW 1 41 wb0 195.205.77.13 204.216.27.17 UGHW 1 172 wb0 204.216.27.3 204.216.27.17 UGHW3 0 13 wb0 3563 204.216.27.16/28 link#1 UC 0 0 wb0 204.216.27.17 0:0:c:4:2e:2e UHLW 7 0 wb0 453 204.216.27.18 0:a0:c9:97:e8:ae UHLW 0 88 wb0 1056 204.216.27.20 link#1 UHLW 2 94 wb0 204.216.27.21 0:a0:c9:a6:e:a6 UHLW 2 485678 wb0 1054 204.216.27.26 link#1 UHLW 2 0 wb0 204.216.27.27 0:a0:c9:a5:f3:7f UHLW 2 90723 wb0 3 204.216.27.31 ff:ff:ff:ff:ff:ff UHLWb 0 1 wb0 204.216.27.192/28 204.216.27.26 UGc 0 0 wb0 204.216.27.224/28 204.216.27.26 UGc 0 0 wb0 206.213.73.13 204.216.27.17 UGHW 1 58 wb0 John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 9: 7:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 69D2A15048 for ; Mon, 22 Nov 1999 09:07:09 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA31576; Mon, 22 Nov 1999 09:05:22 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA75206; Mon, 22 Nov 1999 09:05:22 -0800 (PST) (envelope-from obrien) Date: Mon, 22 Nov 1999 09:05:22 -0800 From: "David O'Brien" To: Grisha Vasilyev Cc: freebsd-current@freebsd.org Subject: Re: CFLAGS vs CXXFLAGS Message-ID: <19991122090522.A72381@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <199911221527.HAA06728@www.geocrawler.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911221527.HAA06728@www.geocrawler.com>; from archiver@db.geocrawler.com on Mon, Nov 22, 1999 at 07:27:38AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have one little problem: make world works for me only with small > patch in gnu/usr.bin/groff/Makefile.cfg: ... > Can anyone explain me, where is the source of this problem? maybe Not if you don't provide some _D-E-T-A-I-L-S_. You know, things like your last CVSup, date of last `make world', maybe even THE FREAKING error messages you got (verbose, not paraphrased). You know, something that would help me figure out if this is due to the new compiler. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 9:29:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.5]) by hub.freebsd.org (Postfix) with ESMTP id 5872315048 for ; Mon, 22 Nov 1999 09:29:03 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: by server.amis.net (Postfix, from userid 66) id 05C7ED5C05; Mon, 22 Nov 1999 18:28:15 +0100 (CET) Received: by gold.amis.net (Postfix, from userid 1000) id A7AA11D60; Mon, 22 Nov 1999 18:25:53 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id 7022357E7 for ; Mon, 22 Nov 1999 18:25:53 +0100 (CET) Date: Mon, 22 Nov 1999 18:25:50 +0100 (CET) From: Blaz Zupan X-Sender: blaz@localhost To: freebsd-current@freebsd.org Subject: wi driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to make the wi (WaveLan) driver work in -current. It appears that some changes to the pccard code have broken it (or that I can't find out how to configure it correctly, although I have done it under 3.3 with success). I have this in my config file: controller card0 controller pcic0 at isa? port 0x3e0 irq 10 iomem 0xd0000 device wi0 at isa? port? irq? ...and this in /etc/pccard.conf: io 0x240-0x360 irq 3 5 10 11 13 15 memory 0xd4000 96k card "Lucent Technologies" "WaveLAN/IEEE" config 0x1 "wi0" 7 insert echo WaveLAN/IEEE inserted insert /etc/pccard_ether wi0 remove echo WaveLAN/IEEE removed remove /sbin/ifconfig wi0 delete After bootup, the ISA-to-pccard bridge is found: pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pccard0: on pcic0 pccard1: on pcic0 Just before going multiuser, pccardd seems to kick in and try to configure the wi interface, but I get this on the console: devclass_alloc_unit: wi0 already exists, using next available unit number ...and there is no wi0 interface (and no wi1, ...). Any idea? Running -current as of two days ago. Tried with and without hardwiring the pcic0 to a specific IO address and IRQ, the result is the same. Any idea? Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 9:37:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 964C815923 for ; Mon, 22 Nov 1999 09:37:32 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA01453 for ; Mon, 22 Nov 1999 09:37:57 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: -current will enter feature freeze on December 15th! Date: Mon, 22 Nov 1999 09:37:57 -0800 Message-ID: <1449.943292277@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I'm sure you all never expected it, but we're actually on the road for a 4.0 release in Q1 2000 (hopefully early January) and before we can realistically begin that process, we have to stop throwing kitchen sinks into -current and start making it work again instead. :-) To that end, we'll be declaring a feature freeze on the 15th, after which time people should just be working on tying off the worst of the spurting arteries and spending more time thinking about fixing things like gdb than thinking about significant architectural changes. With any luck, we'll have 4.0 out in time to catch the last of the new millennium celebrations (or riots, depending on who you listen to :). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 9:56:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id BCF4714CEC for ; Mon, 22 Nov 1999 09:56:19 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id SAA17945; Mon, 22 Nov 1999 18:48:44 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id SAA16845; Mon, 22 Nov 1999 18:55:27 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id SAA09286; Mon, 22 Nov 1999 18:54:57 +0100 (CET) (envelope-from ticso) Date: Mon, 22 Nov 1999 18:54:57 +0100 From: Bernd Walter To: Stephen McKay Cc: Christopher Masto , freebsd-current@FreeBSD.ORG Subject: Re: Fsck follies Message-ID: <19991122185456.A9256@cicely8.cicely.de> References: <199911211236.WAA27489@nymph.detir.qld.gov.au> <19991121130020.A2369@netmonger.net> <199911220457.OAA47173@nymph.detir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199911220457.OAA47173@nymph.detir.qld.gov.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 22, 1999 at 02:57:39PM +1000, Stephen McKay wrote: > On Sunday, 21st November 1999, Christopher Masto wrote: > > >On Sun, Nov 21, 1999 at 10:36:32PM +1000, Stephen McKay wrote: > >> When the system came back up, fsck -p didn't like the vinum volume. > >> No sweat, I ran it manually. There were many > >> > >> INCORRECT BLOCK COUNT I= (4 should be 0) > >> > >> messages. I assumed this was an artifact of soft updates. The fsck > >> completed successfully. > >> > >> Being paranoid, I reran fsck. This time it reported a number of > >> unreferenced inodes (199 to be exact), and linked them in to lost+found. > >> > >> It is this last item that bothers me. When the first fsck completed, > >> the filesystem should have been structurally correct. But it wasn't. > >> A third fsck confirmed that 2 runs of fsck were enough. > > > >Presumably you are using vinum for mirroring? I have had to stop > >doing so after trashing several filesystems. There are some serious > >bugs that allow the plexes to get out of sync; as reads from a mirror > >set are round-robin, this can be very bad. It should be the same reason as discussed on freebsd-fs about R5 plexes. It never happened for me. What did you done to crash the fs? > No, I was just striping them (4 x 660 MB disks, 96 KB interleave). Vinum > had nothing to do with the problem. I was just reporting all the facts, > just in case. > > I think there is a fault in fsck. Possibly it is because softupdates > changed the rules. Having run md5 over the good copy and the broken > (power failure interrupted) copy as well as everything in lost+found, > I can say that no corrupted files survived, and everything in lost+found > was a good copy of some file or other. So softupdates appears to be > doing the right thing. But fsck didn't fix everything broken by the > power interruption. > Sometimes fsck tells you that it needs a rerun. See /usr/share/doc/smm/03.fsck/paper.ascii.gz for details about fsck. Are you shure that this was not the case? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 10:44:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 3461214F1D for ; Mon, 22 Nov 1999 10:44:42 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-153.skylink.it [194.185.55.153]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id TAA12591 for ; Mon, 22 Nov 1999 19:45:14 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id RAA67570 for ; Mon, 22 Nov 1999 17:17:16 +0100 (CET) (envelope-from hibma@skylink.it) Date: Mon, 22 Nov 1999 17:17:16 +0100 (CET) From: Nick Hibma X-Sender: hibma@henny.jrc.it Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List Subject: sbc and pcm Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My compliments on the sbc bridge drivers. This is what newbus is supposed to look like. Anyone wanting to know what a bridge driver is, have a look at sys/dev/sound/isa/sbc.c Beautiful in its simplicity: probe attach (create a few children: pcm, midi, etc.) helper functions (alloc/free resource). Cheers, Nick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 11:28:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id C09E814FF0 for ; Mon, 22 Nov 1999 11:28:10 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id OAA10374; Mon, 22 Nov 1999 14:28:00 -0500 (EST) Date: Mon, 22 Nov 1999 14:28:00 -0500 (EST) From: "Matthew N. Dodd" To: Nick Hibma Cc: FreeBSD CURRENT Mailing List Subject: Re: sbc and pcm In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Nick Hibma wrote: > My compliments on the sbc bridge drivers. This is what newbus is > supposed to look like. Anyone wanting to know what a bridge driver is, > have a look at > > sys/dev/sound/isa/sbc.c > > Beautiful in its simplicity: > > probe > attach (create a few children: pcm, midi, etc.) > helper functions (alloc/free resource). Actually, I've a few issues with it but I'm sure Peter will cover anything I have to say. Mostly, sbc.c is handling PnP ID matching in a totally bogus manner. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 12:24:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 47FFC14CD0 for ; Mon, 22 Nov 1999 12:24:33 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 5A75C1C6D; Tue, 23 Nov 1999 04:22:39 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Matthew N. Dodd" Cc: Nick Hibma , FreeBSD CURRENT Mailing List Subject: Re: sbc and pcm In-Reply-To: Message from "Matthew N. Dodd" of "Mon, 22 Nov 1999 14:28:00 EST." Date: Tue, 23 Nov 1999 04:22:39 +0800 From: Peter Wemm Message-Id: <19991122202239.5A75C1C6D@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > On Mon, 22 Nov 1999, Nick Hibma wrote: > > My compliments on the sbc bridge drivers. This is what newbus is > > supposed to look like. Anyone wanting to know what a bridge driver is, > > have a look at > > > > sys/dev/sound/isa/sbc.c > > > > Beautiful in its simplicity: > > > > probe > > attach (create a few children: pcm, midi, etc.) > > helper functions (alloc/free resource). > > Actually, I've a few issues with it but I'm sure Peter will cover anything > I have to say. > > Mostly, sbc.c is handling PnP ID matching in a totally bogus manner. Yes, it's quite bogus and is incompatible with motherboard devices. There should be no vendor ID references in there at all, that's for card ID, not device id. For example, the laptop I have here has a logical device 0x2100a865 (YMH0021) on the motherboard. There are no vendor ID's for motherboard devices, so the probe will fail as vend_id2 is set to a copy of the logical ID. case 0x2100a865: /* Yamaha */ if (vend_id2 == 0x2000a865) s = "Yamaha OPL3-SA2/SAX Sound Board"; break; Also, the MSS driver probes for this card, *and* the new sbc driver? Not to mention problems with some very broken #if's, but to be fair, many have been there for a while. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 12:42:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4052715973; Mon, 22 Nov 1999 12:41:53 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id MAA32956; Mon, 22 Nov 1999 12:41:50 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA05970; Mon, 22 Nov 1999 12:41:49 -0800 (PST) (envelope-from obrien) Date: Mon, 22 Nov 1999 12:41:48 -0800 From: "David O'Brien" To: Motoyuki Konno Cc: knu@idaemons.org, ports@freebsd.org, freebsd-current@freebsd.org Subject: Re: flashplugin Message-ID: <19991122124148.A5950@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <19991120174617.J41154@daemon.ninth-circle.org> <199911211540.AAA49063@sakura.snipe.rim.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911211540.AAA49063@sakura.snipe.rim.or.jp>; from motoyuki@snipe.rim.or.jp on Mon, Nov 22, 1999 at 12:40:19AM +0900 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 22, 1999 at 12:40:19AM +0900, Motoyuki Konno wrote: > Gcc 2.95.2 output asmcodes which contain 'fild' opcode, but > /usr/libexec/aout/as (a.out version of as) does not support 'fild'. Please try this diff: Index: i386.h =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/as/opcode/i386.h,v retrieving revision 1.10 diff -u -r1.10 i386.h --- i386.h 1999/08/27 23:34:33 1.10 +++ i386.h 1999/11/22 20:40:41 @@ -468,12 +468,13 @@ /* load */ {"fld", 1, 0xd9c0, _, ShortForm, FloatReg, 0, 0}, /* register */ {"flds", 1, 0xd9, 0, Modrm, Mem, 0, 0}, /* %st0 <-- mem float */ -{"fildl", 1, 0xdb, 0, Modrm, Mem, 0, 0}, /* %st0 <-- mem word */ {"fldl", 1, 0xdd, 0, Modrm, Mem, 0, 0}, /* %st0 <-- mem double */ {"fldl", 1, 0xd9c0, _, ShortForm, FloatReg, 0, 0}, /* register */ +{"fild", 1, 0xdf, 0, Modrm, Mem, 0, 0}, /* %st0 <-- mem word (16) */ +{"fildl", 1, 0xdb, 0, Modrm, Mem, 0, 0}, /* %st0 <-- mem word */ {"filds", 1, 0xdf, 0, Modrm, Mem, 0, 0}, /* %st0 <-- mem dword */ -{"fildll", 1, 0xdf, 5, Modrm, Mem, 0, 0}, /* %st0 <-- mem qword */ {"fildq", 1, 0xdf, 5, Modrm, Mem, 0, 0}, /* %st0 <-- mem qword */ +{"fildll", 1, 0xdf, 5, Modrm, Mem, 0, 0}, /* %st0 <-- mem qword */ {"fldt", 1, 0xdb, 5, Modrm, Mem, 0, 0}, /* %st0 <-- mem efloat */ {"fbld", 1, 0xdf, 4, Modrm, Mem, 0, 0}, /* %st0 <-- mem bcd */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 13:27:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 8AFF114D42 for ; Mon, 22 Nov 1999 13:27:22 -0800 (PST) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Mon, 22 Nov 1999 13:27:21 -0800 From: "David Schwartz" To: "Jordan K. Hubbard" , Subject: RE: -current will enter feature freeze on December 15th! Date: Mon, 22 Nov 1999 13:27:21 -0800 Message-ID: <000501bf3530$5c5f6040$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 In-Reply-To: <1449.943292277@localhost> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > To that end, we'll be declaring a feature freeze on the 15th, after > which time people should just be working on tying off the worst of the > spurting arteries and spending more time thinking about fixing things > like gdb than thinking about significant architectural changes. With > any luck, we'll have 4.0 out in time to catch the last of the new > millennium celebrations (or riots, depending on who you listen to :). > > - Jordan The last of the new millennium celebrations are still more than a year away. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 13:30:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6D57914D42 for ; Mon, 22 Nov 1999 13:30:33 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA02627; Mon, 22 Nov 1999 13:28:37 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "David Schwartz" Cc: "Jordan K. Hubbard" , current@freebsd.org Subject: Re: -current will enter feature freeze on December 15th! In-reply-to: Your message of "Mon, 22 Nov 1999 13:27:21 PST." <000501bf3530$5c5f6040$021d85d1@youwant.to> Date: Mon, 22 Nov 1999 13:28:37 -0800 Message-ID: <2623.943306117@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The last of the new millennium celebrations are still more than a year away. Well, if you want to get technical, some people have already started early. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 14:16:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 7F3AA14BE7; Mon, 22 Nov 1999 14:15:49 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.224.118]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA3485; Mon, 22 Nov 1999 23:13:21 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id XAA19148; Mon, 22 Nov 1999 23:12:52 +0100 (CET) (envelope-from asmodai) Date: Mon, 22 Nov 1999 23:12:51 +0100 From: Jeroen Ruigrok/Asmodai To: "David O'Brien" Cc: Motoyuki Konno , knu@idaemons.org, ports@freebsd.org, freebsd-current@freebsd.org Subject: Re: flashplugin Message-ID: <19991122231251.A18384@daemon.ninth-circle.org> References: <19991120174617.J41154@daemon.ninth-circle.org> <199911211540.AAA49063@sakura.snipe.rim.or.jp> <19991122124148.A5950@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991122124148.A5950@dragon.nuxi.com> Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991122 22:07], David O'Brien (obrien@freebsd.org) wrote: >On Mon, Nov 22, 1999 at 12:40:19AM +0900, Motoyuki Konno wrote: >> Gcc 2.95.2 output asmcodes which contain 'fild' opcode, but >> /usr/libexec/aout/as (a.out version of as) does not support 'fild'. > >Please try this diff: Compiles flashplugin for me. Flash also works now. But then when you try to load a page with flash it dies with: /usr/libexec/ld.so: Undefined symbol "___get_eh_context" called from navigator-4.7.bin:/usr/local/lib/netscape/plugins/libswf.so at 0x208c22b4 This happened both before and after the gcc upgrade and with navigator 4.6 and 4.7, native FreeBSD versions. But that's probably not your problem David. =) -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Learn e-mail netiquette: http://www.lemis.com/email.html Once sent from the Golden Hall... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 15:18:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 64A2814A21 for ; Mon, 22 Nov 1999 15:18:09 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id JAA31396; Tue, 23 Nov 1999 09:47:24 +1030 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199911222317.JAA31396@gizmo.internode.com.au> Subject: Re: -current will enter feature freeze on December 15th! To: davids@webmaster.com (David Schwartz) Date: Tue, 23 Nov 1999 09:47:24 +1030 (CST) Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG In-Reply-To: <000501bf3530$5c5f6040$021d85d1@youwant.to> from "David Schwartz" at Nov 22, 99 01:27:21 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Schwartz wrote: > Jordan Hubbard wrote: > > With any luck, we'll have 4.0 out in time to catch the last of the new > > millennium celebrations (or riots, depending on who you listen to :). > > The last of the new millennium celebrations are still more than a year > away. Yup, and with any luck we'll have 4.0 out before then :-) - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 15:20:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from nowcool.dhs.org (fx3-1-031.mgfairfax.rr.com [24.28.200.31]) by hub.freebsd.org (Postfix) with ESMTP id A123814A21 for ; Mon, 22 Nov 1999 15:20:45 -0800 (PST) (envelope-from freebsd@nowcool.dhs.org) Received: from localhost (freebsd@localhost) by nowcool.dhs.org (8.9.3/8.9.3) with ESMTP id SAA39123; Mon, 22 Nov 1999 18:18:53 -0500 (EST) (envelope-from freebsd@nowcool.dhs.org) Date: Mon, 22 Nov 1999 18:18:53 -0500 (EST) From: Byung Yang To: "David W. Chapman Jr." Cc: current@FreeBSD.ORG Subject: Re: Promise ULTRA/66 Controler In-Reply-To: <00f001bf32c2$2e77a360$0300a8c0@poseiden.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG try ata0 instead of wdc0 this is what my dmesg says: -------------------------------------------------------------- ata-pci1: irq 9 at device 11.0 on pci0 ata-pci1: Busmastering DMA supported ata2 at 0xcc00 irq 9 on ata-pci1 ata3 at 0xd400 irq 9 on ata-pci1 ad0: ATA-4 disk at ata2 as master ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA66 Creating DISK ad0 Creating DISK wd0 ad1: ATA-3 disk at ata3 as master ad1: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad1 Creating DISK wd1 ---------------------------------------------------------- this is my kernel config: ------------------------------------------------- # IDE controller and disks controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives _________________________________________________ On Fri, 19 Nov 1999, David W. Chapman Jr. wrote: > Anybody have any luck with Promise ULTRA/66 controllers until -current? here's what it detects mine as > > pci0: unknown card (vendor=0x105a, dev=0x4d38) at 8.0 irq 15 > > Any ideas on what I can do would be appreciated. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 15:23: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id CAAF014A21 for ; Mon, 22 Nov 1999 15:23:04 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 176141F80; Tue, 23 Nov 1999 00:23:04 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by shadowmere.student.utwente.nl (Postfix) with ESMTP id 0E1D0B9; Tue, 23 Nov 1999 00:23:04 +0100 (CET) Date: Tue, 23 Nov 1999 00:23:03 +0100 (CET) From: Pascal Hofstee To: Seigo Tanimura Cc: current@freebsd.org Subject: Re: HEADS UP! The bridge drivers for sound cards have been committed. In-Reply-To: <199911220611.PAA43328@rina.r.dl.itc.u-tokyo.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Seigo Tanimura wrote: > The bridge drivers for sound cards have just been committed. > These drivers will accomodate coming newmidi drivers. > > People using Sound Blaster 16/AWE32/AWE64/ViBRA16C/ViBRA16X > should add sbc driver to your kernel config file in addition > to pcm driver, rebuild and reinstall a new kernel. See LINT > as well. > > This commit also adds pcm support for the following cards: > > GUS PnP and non-PnP ISA (gusc driver) > Crystal Semiconductor CS461x/428x PCI (csa driver) > > For a GUS non-PnP ISA card, write down the configuration of > your card to gusc, not pcm. Apparently the commit forget to include the sbc.h and gusc.h files. I only seem to be having the equivalent .c files lying around. -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 15:35:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id ACF7214F4D; Mon, 22 Nov 1999 15:35:12 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by hub.freebsd.org (8.9.3/8.9.3) with ESMTP id SAA25157; Mon, 22 Nov 1999 18:31:25 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Mon, 22 Nov 1999 18:31:23 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: "Alexander N. Kabaev" Cc: Jean-Marc Zucconi , current@FreeBSD.org Subject: RE: Netscape and -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Alexander N. Kabaev wrote: > The same here. CURRENT updated and built on Sunday causes native > FreeBSD Netscape to lock up. Linux Netscape still works fine. > Happens here, too. Can someone with a machine to spare try the following: 1. Go back in date a week, and try the kernel. Does Netscape work? 2. Try a day later. Repeat till netscape breaks. 3. Go to the day it was still working. Read commits between the two times and see what's changed. Could it possibly be the KAME commit? -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 15:39:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id ACC4714F6F for ; Mon, 22 Nov 1999 15:39:48 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 006661F38; Tue, 23 Nov 1999 00:39:35 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by shadowmere.student.utwente.nl (Postfix) with ESMTP id E02E39F; Tue, 23 Nov 1999 00:39:35 +0100 (CET) Date: Tue, 23 Nov 1999 00:39:35 +0100 (CET) From: Pascal Hofstee To: Seigo Tanimura Cc: current@freebsd.org Subject: Re: HEADS UP! The bridge drivers for sound cards have been committed. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Pascal Hofstee wrote: > On Mon, 22 Nov 1999, Seigo Tanimura wrote: > > > The bridge drivers for sound cards have just been committed. > > These drivers will accomodate coming newmidi drivers. [ snip ] > Apparently the commit forget to include the sbc.h and gusc.h files. > I only seem to be having the equivalent .c files lying around. please ignore ... seems the header-files get generated by config -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 15:46:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id CEC2114FCF; Mon, 22 Nov 1999 15:46:03 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id PAA52011; Mon, 22 Nov 1999 15:44:17 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199911222344.PAA52011@troutmask.apl.washington.edu> Subject: Re: Netscape and -current In-Reply-To: from Brian Fundakowski Feldman at "Nov 22, 1999 06:31:23 pm" To: green@FreeBSD.ORG (Brian Fundakowski Feldman) Date: Mon, 22 Nov 1999 15:44:16 -0800 (PST) Cc: ak03@gte.com (Alexander N. Kabaev), jmz@FreeBSD.ORG (Jean-Marc Zucconi), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Fundakowski Feldman wrote: > On Mon, 22 Nov 1999, Alexander N. Kabaev wrote: > > > The same here. CURRENT updated and built on Sunday causes native > > FreeBSD Netscape to lock up. Linux Netscape still works fine. > > > > Happens here, too. Can someone with a machine to spare try the following: > > 1. Go back in date a week, and try the kernel. Does Netscape work? FreeBSD 4.0-CURRENT #1: Mon Nov 15 09:52:45 PST 1999 root@troutmask.apl.washington.edu:/usr/src/sys/compile/TROUTMASK netscape (for FBSD) works fine. > 2. Try a day later. Repeat till netscape breaks. Can't do this at the moment. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 16:19:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 4852715A32 for ; Mon, 22 Nov 1999 16:19:09 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (n_hibma@elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id BAA07383; Tue, 23 Nov 1999 01:19:03 +0100 (MET) Date: Tue, 23 Nov 1999 01:19:05 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: "Matthew N. Dodd" Cc: FreeBSD CURRENT Mailing List Subject: Re: sbc and pcm In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My compliments on the sbc bridge drivers. This is what newbus is > > supposed to look like. Anyone wanting to know what a bridge driver is, > > have a look at ... > Actually, I've a few issues with it but I'm sure Peter will cover anything > I have to say. > > Mostly, sbc.c is handling PnP ID matching in a totally bogus manner. That's not the part I am referring to. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 17:29:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id C16B814C46; Mon, 22 Nov 1999 17:29:42 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id TAA96827; Mon, 22 Nov 1999 19:28:58 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Mon, 22 Nov 1999 19:28:55 -0600 (CST) From: David Scheidt To: Brian Fundakowski Feldman Cc: "Alexander N. Kabaev" , Jean-Marc Zucconi , current@FreeBSD.org Subject: RE: Netscape and -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Brian Fundakowski Feldman wrote: > On Mon, 22 Nov 1999, Alexander N. Kabaev wrote: > > > The same here. CURRENT updated and built on Sunday causes native > > FreeBSD Netscape to lock up. Linux Netscape still works fine. > > > > Happens here, too. Can someone with a machine to spare try the following: > Working on this now. I presume I can just build a kernel, since the machine I am trying to upgrade form -STABLE to CURRENT does this. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 17:31:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id CC34114EA2; Mon, 22 Nov 1999 17:31:25 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA14885; Tue, 23 Nov 1999 12:00:52 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199911222344.PAA52011@troutmask.apl.washington.edu> Date: Tue, 23 Nov 1999 12:00:52 +1030 (CST) From: "Daniel O'Connor" To: Steve Kargl Subject: Re: Netscape and -current Cc: current@FreeBSD.ORG, (Jean-Marc Zucconi) , (Alexander N. Kabaev) , (Brian Fundakowski Feldman) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Nov-99 Steve Kargl wrote: > FreeBSD 4.0-CURRENT #1: Mon Nov 15 09:52:45 PST 1999 > root@troutmask.apl.washington.edu:/usr/src/sys/compile/TROUTMASK > netscape (for FBSD) works fine. I have -current as of 19-Nov-99 and Netscape works fine (well as well at it ever does..) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 18:53:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 0412014C48 for ; Mon, 22 Nov 1999 18:53:11 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 7483 invoked by uid 1001); 23 Nov 1999 02:52:20 -0000 Date: Mon, 22 Nov 1999 18:52:20 -0800 From: Jason Evans To: current@freebsd.org, hackers@freebsd.org Subject: Threads and my new job. Message-ID: <19991122185220.D301@sturm.canonware.com> Reply-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Walnut Creek has hired me as a full time employee to work primarily on improving and expanding FreeBSD's threads support. This is very exciting to me, and I hope my work will be of benefit the FreeBSD community. There is a lot of work to be done in order to make FreeBSD's threads support truly excellent, and it will take more than just me working on it. Fortunately, there are a number of other people also interested in improving threads support, and as work progresses, I expect this will very much be a group effort. Some very fruitful long-range architecture discussions have been taking place on the -arch mailing list, and discussion will likely continue there for some time as design decisions are hashed out. If you are interested in participating in the design discussion, please subscribe to -arch (if you haven't already), read the -arch archives for the past couple of weeks to bring yourself up to speed on what has been discussed so far, read some of the more pertinent references listed throughout the discussion, then jump in. The signal-to-noise ratio on -arch is exceptionally high; please do your part in keeping it that way. What am I going to do? My first mandate is to round out the edges of our current libc_r and to bring it closer to standards compliance before 4.0. Specifically, I know that the following work is necessary: *) Address and close approximately 20 PRs. The list of PRs I know about is: i386/7426, bin/7587, misc/8202, bin/8281, kern/8729, misc/9778, misc/9903, misc/10599, bin/10992, kern/11982, kern/11984, bin/13008, misc/13117, kern/13644, misc/14264, i386/14383, kern/14685, and docs/14858. If there are other PRs that I didn't list that are directly related to threads, please let me know about them in private email so that I can keep track of them. *) Signal delivery fixes. I think Daniel Eischen has already taken care of this. *) Lacking interfaces, such as pthread_cancel() (mentioned specifically in PR bin/7587) need to be implemented. *) Make a real libpthread, rather than relying on the -pthread linker magic. This is high on Daniel Eischen's wish list, so maybe he already has something in the works. =) If you know of other outstanding issues that have a prayer of being addressed before 4.0 ships, please speak up. Jason Jason Evans http://www.canonware.com/~jasone Home phone: (650) 856-8204 "I once knew a happy medium. Her name was Zohar." - James Foster To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 19: 1: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 60A8314C23; Mon, 22 Nov 1999 19:01:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA01520; Mon, 22 Nov 1999 19:00:45 -0800 (PST) (envelope-from dillon) Date: Mon, 22 Nov 1999 19:00:45 -0800 (PST) From: Matthew Dillon Message-Id: <199911230300.TAA01520@apollo.backplane.com> To: Jason Evans Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Threads and my new job. References: <19991122185220.D301@sturm.canonware.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :... :*) Make a real libpthread, rather than relying on the -pthread linker : magic. This is high on Daniel Eischen's wish list, so maybe he already : has something in the works. =) : :If you know of other outstanding issues that have a prayer of being :addressed before 4.0 ships, please speak up. : :Jason : :Jason Evans A natively implemented linux-compatible clone() call would be cool (rather then the one in the linux compatibility suite). Or if not that, then clib support for the equivalent of rfork(RFMEM|RFPROC) (currently C code will crash if it calls rfork() with RFMEM due to the new process not getting a new %esp). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 19:34:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 3790214C2F; Mon, 22 Nov 1999 19:34:37 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by hub.freebsd.org (8.9.3/8.9.3) with ESMTP id WAA40704; Mon, 22 Nov 1999 22:31:36 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Mon, 22 Nov 1999 22:31:35 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: "Daniel O'Connor" Cc: Steve Kargl , current@FreeBSD.org, jmz@FreeBSD.org, ak03@gte.com Subject: Re: Netscape and -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Daniel O'Connor wrote: > > On 22-Nov-99 Steve Kargl wrote: > > FreeBSD 4.0-CURRENT #1: Mon Nov 15 09:52:45 PST 1999 > > root@troutmask.apl.washington.edu:/usr/src/sys/compile/TROUTMASK > > netscape (for FBSD) works fine. > > I have -current as of 19-Nov-99 and Netscape works fine (well as well at it > ever does..) I'm pretty sure that my guess of KAME is correct, as evidenced by times of working and non-working kernels. But what do we do with that not-so-wild guess? > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 19:35:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 731B215A04; Mon, 22 Nov 1999 19:35:38 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id E7D731C6D; Tue, 23 Nov 1999 11:35:17 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Fundakowski Feldman Cc: "Alexander N. Kabaev" , Jean-Marc Zucconi , marcel@freebsd.org, pho@freebsd.org, phk@freebsd.org, current@FreeBSD.org Subject: Re: Netscape and -current In-Reply-To: Message from Brian Fundakowski Feldman of "Mon, 22 Nov 1999 18:31:23 EST." Date: Tue, 23 Nov 1999 11:35:17 +0800 From: Peter Wemm Message-Id: <19991123033517.E7D731C6D@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Fundakowski Feldman wrote: > On Mon, 22 Nov 1999, Alexander N. Kabaev wrote: > > > The same here. CURRENT updated and built on Sunday causes native > > FreeBSD Netscape to lock up. Linux Netscape still works fine. > > > > Happens here, too. Can someone with a machine to spare try the following: > > 1. Go back in date a week, and try the kernel. Does Netscape work? > 2. Try a day later. Repeat till netscape breaks. > 3. Go to the day it was still working. Read commits between the > two times and see what's changed. Could it possibly be the KAME > commit? I'm pretty sure it's this commit to i386/machdep.c: === revision 1.377 date: 1999/11/21 14:46:43; author: pho; state: Exp; lines: +5 -5 Moved useracc() to top of sigreturn as to avoid panic caused by invalid arguments to rutine. Reviewed by: marcel, phk === .. it's right in the area that's breaking netscape: 484 communicator-4.7 PSIG SIGALRM caught handler=0x8fea40 mask=0x0 code=0x0 484 communicator-4.7 CALL sigreturn(0x50011ed4) 484 communicator-4.7 RET sigreturn -1 errno 14 Bad address Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 19:37:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id D451B15044 for ; Mon, 22 Nov 1999 19:37:28 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id WAA13735; Mon, 22 Nov 1999 22:37:12 -0500 (EST) Date: Mon, 22 Nov 1999 22:37:12 -0500 (EST) From: Daniel Eischen To: Jason Evans Cc: current@FreeBSD.ORG Subject: Re: Threads and my new job. In-Reply-To: <19991122185220.D301@sturm.canonware.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Jason Evans wrote: > What am I going to do? My first mandate is to round out the edges of our > current libc_r and to bring it closer to standards compliance before 4.0. > Specifically, I know that the following work is necessary: > > *) Address and close approximately 20 PRs. The list of PRs I know about > is: i386/7426, bin/7587, misc/8202, bin/8281, kern/8729, misc/9778, > misc/9903, misc/10599, bin/10992, kern/11982, kern/11984, bin/13008, > misc/13117, kern/13644, misc/14264, i386/14383, kern/14685, and > docs/14858. If there are other PRs that I didn't list that are directly > related to threads, please let me know about them in private email so > that I can keep track of them. I have a few things already fixed, some have gotten stale and need to be merged into what is now current. Give me another week or so and I can update them. > > *) Signal delivery fixes. I think Daniel Eischen has already taken care of > this. Yes, awaiting review by JB. > > *) Lacking interfaces, such as pthread_cancel() (mentioned specifically in > PR bin/7587) need to be implemented. This is done. Alfred Pearlstein ported NetBSDs (or was it OpenBSD) pthread_cancel() support. I've reviewed and made comments to it, but JB probably needs to review it also. > *) Make a real libpthread, rather than relying on the -pthread linker > magic. This is high on Daniel Eischen's wish list, so maybe he already > has something in the works. =) Not yet :-(. I think libc needs some major work in order to achieve this. You should put this on your ToDo list :-) > If you know of other outstanding issues that have a prayer of being > addressed before 4.0 ships, please speak up. Good Luck in your new job :) I'd love to be able to do this full-time and am envious! Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 19:45:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id A4B1214C2F; Mon, 22 Nov 1999 19:45:03 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 1E28F1C6D; Tue, 23 Nov 1999 11:44:33 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Daniel O'Connor" Cc: Steve Kargl , current@FreeBSD.ORG, jmz@FreeBSD.ORG (Jean-Marc Zucconi), ak03@gte.com (Alexander N. Kabaev), green@FreeBSD.ORG (Brian Fundakowski Feldman) Subject: Re: Netscape and -current In-Reply-To: Message from "Daniel O'Connor" of "Tue, 23 Nov 1999 12:00:52 +1030." Date: Tue, 23 Nov 1999 11:44:33 +0800 From: Peter Wemm Message-Id: <19991123034433.1E28F1C6D@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel O'Connor" wrote: > > On 22-Nov-99 Steve Kargl wrote: > > FreeBSD 4.0-CURRENT #1: Mon Nov 15 09:52:45 PST 1999 > > root@troutmask.apl.washington.edu:/usr/src/sys/compile/TROUTMASK > > netscape (for FBSD) works fine. > > I have -current as of 19-Nov-99 and Netscape works fine (well as well at it > ever does..) I'd be curious to know if this fixes it on a -current kernel (after rev 1.377 of i386/machdep.c) Index: machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v retrieving revision 1.377 diff -u -r1.377 machdep.c --- machdep.c 1999/11/21 14:46:43 1.377 +++ machdep.c 1999/11/23 03:40:49 @@ -871,14 +871,19 @@ { struct trapframe *regs; ucontext_t *ucp; + struct osigcontext *scp; int cs, eflags; ucp = uap->sigcntxp; + scp = (struct osigcontext *)ucp; + + if (useracc((caddr_t)scp, sizeof (struct osigcontext), VM_PROT_READ)) { + if (scp->sigcntxp->sc_trapno == 0x01d516) + return osigreturn(p, (struct osigreturn_args *)uap); + } + if (!useracc((caddr_t)ucp, sizeof(ucontext_t), VM_PROT_READ)) return(EFAULT); - - if (((struct osigcontext *)uap->sigcntxp)->sc_trapno == 0x01d516) - return osigreturn(p, (struct osigreturn_args *)uap); regs = p->p_md.md_regs; eflags = ucp->uc_mcontext.mc_eflags; The problem is that the useracc was moved earlier, and is being done on a larger struct size before we know if it's the right struct or not. My suggested change is to test for only sizeof osigcontext until we know it's the larger (?) ucontext_t. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 20:33:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A879115040; Mon, 22 Nov 1999 20:33:39 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by hub.freebsd.org (8.9.3/8.9.3) with ESMTP id WAA40881; Mon, 22 Nov 1999 22:56:22 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Mon, 22 Nov 1999 22:56:21 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Peter Wemm Cc: "Alexander N. Kabaev" , Jean-Marc Zucconi , marcel@FreeBSD.org, pho@FreeBSD.org, phk@FreeBSD.org, current@FreeBSD.org Subject: Re: Netscape and -current In-Reply-To: <19991123033517.E7D731C6D@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Peter Wemm wrote: > I'm pretty sure it's this commit to i386/machdep.c: > === > revision 1.377 > date: 1999/11/21 14:46:43; author: pho; state: Exp; lines: +5 -5 > Moved useracc() to top of sigreturn as to avoid panic > caused by invalid arguments to rutine. > Thanks! Testing and committing a fix. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 20:37:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id CD64A15040; Mon, 22 Nov 1999 20:37:22 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id WAA20678; Mon, 22 Nov 1999 22:37:10 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Mon, 22 Nov 1999 22:37:10 -0600 (CST) From: David Scheidt To: Peter Wemm Cc: Brian Fundakowski Feldman , "Alexander N. Kabaev" , Jean-Marc Zucconi , marcel@FreeBSD.org, pho@FreeBSD.org, phk@FreeBSD.org, current@FreeBSD.org Subject: Re: Netscape and -current In-Reply-To: <19991123033517.E7D731C6D@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Peter Wemm wrote: > I'm pretty sure it's this commit to i386/machdep.c: Good call! A tree checked out with -D 1999-11-21 14:47 won't run netscape. A kernel built with the same sources, except for 1.376 of i386/machdep.c will. David Scheidt > === > revision 1.377 > date: 1999/11/21 14:46:43; author: pho; state: Exp; lines: +5 -5 > Moved useracc() to top of sigreturn as to avoid panic > caused by invalid arguments to rutine. > > Reviewed by: marcel, phk > === > > .. it's right in the area that's breaking netscape: > 484 communicator-4.7 PSIG SIGALRM caught handler=0x8fea40 mask=0x0 code=0x0 > 484 communicator-4.7 CALL sigreturn(0x50011ed4) > 484 communicator-4.7 RET sigreturn -1 errno 14 Bad address > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 20:43:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 817C715054; Mon, 22 Nov 1999 20:43:45 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id XAA28441; Mon, 22 Nov 1999 23:43:15 -0500 (EST) Message-ID: <19991122234315.A28341@netmonger.net> Date: Mon, 22 Nov 1999 23:43:15 -0500 From: Christopher Masto To: Peter Wemm , "Daniel O'Connor" Cc: Steve Kargl , current@FreeBSD.ORG, Jean-Marc Zucconi , "Alexander N. Kabaev" , Brian Fundakowski Feldman Subject: Re: Netscape and -current References: <19991123034433.1E28F1C6D@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19991123034433.1E28F1C6D@overcee.netplex.com.au>; from Peter Wemm on Tue, Nov 23, 1999 at 11:44:33AM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 23, 1999 at 11:44:33AM +0800, Peter Wemm wrote: > I'd be curious to know if this fixes it on a -current kernel (after rev 1.377 > of i386/machdep.c) Yep, except this needs to come out: > + scp = (struct osigcontext *)ucp; > + > + if (useracc((caddr_t)scp, sizeof (struct osigcontext), VM_PROT_READ)) { > + if (scp->sigcntxp->sc_trapno == 0x01d516) ^^^^^^^^^^ And that does the trick. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 21:32:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 923EA14BE2; Mon, 22 Nov 1999 21:32:37 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id AAA22707; Tue, 23 Nov 1999 00:30:45 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Tue, 23 Nov 1999 00:30:44 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@org.dyndns.org To: Christopher Masto Cc: Peter Wemm , "Daniel O'Connor" , Steve Kargl , current@FreeBSD.org, Jean-Marc Zucconi , "Alexander N. Kabaev" Subject: Re: Netscape and -current In-Reply-To: <19991122234315.A28341@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forget anything I said about KAME being the strong possibility :) As soon as peter noted what commit it could have to do with, I figured it out and fixed it; after testing, I committed it. Be happy :) -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 21:45:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 1EF7114A0B for ; Mon, 22 Nov 1999 21:45:24 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id VAA47177; Mon, 22 Nov 1999 21:45:15 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id VAA64425; Mon, 22 Nov 1999 21:44:36 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199911230544.VAA64425@whistle.com> Subject: Re: wi driver In-Reply-To: from Blaz Zupan at "Nov 22, 99 06:25:50 pm" To: blaz@gold.amis.net (Blaz Zupan) Date: Mon, 22 Nov 1999 21:44:36 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Blaz Zupan writes: | I'm trying to make the wi (WaveLan) driver work in -current. It appears | that some changes to the pccard code have broken it (or that I can't find | out how to configure it correctly, although I have done it under 3.3 with | success). I have this in my config file: It needs to be converted to newbus. I've done this to Bill Paul's Aironet driver for -current (however, his driver doesn't work with an access point correctly but the driver for Linux does so I have some work to do). You can use the /sys/dev/ed driver as a model. I don't have a card like that to test with. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 22 22:14:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 1764B1509A; Mon, 22 Nov 1999 22:14:19 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 248461C6D; Tue, 23 Nov 1999 14:13:12 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Fundakowski Feldman Cc: Christopher Masto , "Daniel O'Connor" , Steve Kargl , current@FreeBSD.org, Jean-Marc Zucconi , "Alexander N. Kabaev" Subject: Re: Netscape and -current In-Reply-To: Message from Brian Fundakowski Feldman of "Tue, 23 Nov 1999 00:30:44 EST." Date: Tue, 23 Nov 1999 14:13:12 +0800 From: Peter Wemm Message-Id: <19991123061312.248461C6D@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Fundakowski Feldman wrote: > Forget anything I said about KAME being the strong possibility :) As > soon as peter noted what commit it could have to do with, I figured > it out and fixed it; after testing, I committed it. Be happy :) Your fix suffers from exactly the same problem.. Suppose down the track that ucontext_t becomes smaller than 'struct sigocontext' ? You're then failing what would have worked. The check against sizeof osigcontext should not be fatal. Index: machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v retrieving revision 1.378 diff -u -r1.378 machdep.c --- machdep.c 1999/11/23 04:09:13 1.378 +++ machdep.c 1999/11/23 05:49:46 @@ -871,14 +871,16 @@ { struct trapframe *regs; ucontext_t *ucp; + struct osigcontext *scp; int cs, eflags; ucp = uap->sigcntxp; + scp = (struct osigcontext *)ucp; - if (!useracc((caddr_t)ucp, sizeof(struct osigcontext), VM_PROT_READ)) - return (EFAULT); - if (((struct osigcontext *)ucp)->sc_trapno == 0x01d516) - return (osigreturn(p, (struct osigreturn_args *)uap)); + if (useracc((caddr_t)scp, sizeof (struct osigcontext), VM_PROT_READ)) { + if (scp->sc_trapno == 0x01d516) + return osigreturn(p, (struct osigreturn_args *)uap); + } /* * Since ucp is not an osigcontext but a ucontext_t, we have to Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 0:10:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id A630714D90 for ; Tue, 23 Nov 1999 00:10:26 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id KAA76941 for freebsd-current@FreeBSD.ORG; Tue, 23 Nov 1999 10:09:51 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199911230809.KAA76941@zibbi.mikom.csir.co.za> Subject: make -j13 world broken To: freebsd-current@FreeBSD.ORG (FreeBSD-current) Date: Tue, 23 Nov 1999 10:09:51 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, A normal "make world" on current is ok, but a "make -j13 world" is broken. I have looked at it a little bit, but I can't figure out what is going wrong. It dies with: -------- cd /usr/src/usr.bin/lex; make beforeinstall install -C -o root -g wheel -m 644 /usr/src/usr.bin/lex/FlexLexer.h /usr/obj/usr/src/tmp/usr/include/g++ -------------------------------------------------------------- >>> Building elf libraries -------------------------------------------------------------- cd /usr/src; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib PERL5LIB=/usr/libdata/perl/5.00503 OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr/libexec CFLAGS="-nostdinc -O -pipe" make DESTDIR=/usr/obj/usr/src/tmp -DNOINFO -DNOMAN -f Makefile.inc1 libraries make: not found *** Error code 127 1 error *** Error code 2 1 error *** Error code 2 1 error -------- John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 1:49:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 8116614E09 for ; Tue, 23 Nov 1999 01:49:45 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA37732; Tue, 23 Nov 1999 09:47:32 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 23 Nov 1999 09:47:32 +0000 (GMT) From: Doug Rabson To: Peter Wemm Cc: "Matthew N. Dodd" , Nick Hibma , FreeBSD CURRENT Mailing List Subject: Re: sbc and pcm In-Reply-To: <19991122202239.5A75C1C6D@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Peter Wemm wrote: > "Matthew N. Dodd" wrote: > > On Mon, 22 Nov 1999, Nick Hibma wrote: > > > My compliments on the sbc bridge drivers. This is what newbus is > > > supposed to look like. Anyone wanting to know what a bridge driver is, > > > have a look at > > > > > > sys/dev/sound/isa/sbc.c > > > > > > Beautiful in its simplicity: > > > > > > probe > > > attach (create a few children: pcm, midi, etc.) > > > helper functions (alloc/free resource). > > > > Actually, I've a few issues with it but I'm sure Peter will cover anything > > I have to say. > > > > Mostly, sbc.c is handling PnP ID matching in a totally bogus manner. > > Yes, it's quite bogus and is incompatible with motherboard devices. There > should be no vendor ID references in there at all, that's for card ID, not > device id. I thought the problem with that (which was present in the non-bridged sb driver too) is that for sound cards, we need to use both logical and vendor IDs to detect things accuratly (a surprisingly large number of cards are just labeled CSC0001 or similar). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 1:56:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 147DB1503D for ; Tue, 23 Nov 1999 01:56:30 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id KAA67539 for current@FreeBSD.org; Tue, 23 Nov 1999 10:51:43 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Tue, 23 Nov 1999 10:51:24 +0100 From: Marcel Moolenaar Message-ID: <383A639C.4D21A2FF@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199911230809.KAA76941@zibbi.mikom.csir.co.za> Subject: Re: make -j13 world broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > A normal "make world" on current is ok, but a "make -j13 world" is broken. > I have looked at it a little bit, but I can't figure out what is going > wrong. It dies with: > > -------- > cd /usr/src/usr.bin/lex; make beforeinstall > install -C -o root -g wheel -m 644 /usr/src/usr.bin/lex/FlexLexer.h /usr/obj/usr/src/tmp/usr/include/g++ > -------------------------------------------------------------- > >>> Building elf libraries > -------------------------------------------------------------- > cd /usr/src; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib PERL5LIB=/usr/libdata/perl/5.00503 OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr/libexec CFLAGS="-nostdinc -O -pipe" make DESTDIR=/usr/obj/usr/src/tmp -DNOINFO -DNOMAN -f Makefile.inc1 libraries > make: not found > *** Error code 127 I assume make(1) has been built, because that's the first constructive thing that happens. Can you check that it has been installed? -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 2:25: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from patachou.sti.com.br (patachou.sti.com.br [200.212.48.251]) by hub.freebsd.org (Postfix) with ESMTP id F2D4A14A00; Tue, 23 Nov 1999 02:24:51 -0800 (PST) (envelope-from VideBula@sti.com.br) Received: from carlos (dial-lc11-149.sti.com.br [200.188.73.149] (may be forged)) by patachou.sti.com.br (8.9.3/8.9.3) with SMTP id IAA18313; Tue, 23 Nov 1999 08:23:15 -0200 Message-Id: <199911231023.IAA18313@patachou.sti.com.br> From: "VideBula" To: VB Date: Tue, 23 Nov 1999 08:19:44 -0300 Subject: VB Reply-To: VideBula@sti.com.br Organization: ViaNet Comunicação & Informação Ltda. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001_4295711_29984,04_4325695,0390625" Content-Transfer-Encoding: 7bit X-Priority: 1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a Multipart MIME message. Since your mail reader does not understand this format, some or all of this message may not be legible. ------=_NextPart_000_001_4295711_29984,04_4325695,0390625 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit ------=_NextPart_000_001_4295711_29984,04_4325695,0390625 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 7bit VideBula-991118

VideBula

 

"Não importa o que tiraram de você,
o que importa é o que você vai fazer com o que sobrou."

 

"Você não pode estar só se gostar da pessoa com quem fica quando esta sozinho." 

RECEBER NÃORECEBER

PUBLICAR CRÍTICAS, DÚVIDAS & SUGESTÕES

------=_NextPart_000_001_4295711_29984,04_4325695,0390625-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 2:30:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 29C6E14A00 for ; Tue, 23 Nov 1999 02:30:30 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id UAA03026; Tue, 23 Nov 1999 20:29:02 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma003018; Tue, 23 Nov 99 20:28:50 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id UAA03018; Tue, 23 Nov 1999 20:28:15 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id UAA29932; Tue, 23 Nov 1999 20:28:15 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id UAA14557; Tue, 23 Nov 1999 20:28:14 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199911231028.UAA14557@nymph.detir.qld.gov.au> To: Bernd Walter Cc: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Fsck follies References: <199911211236.WAA27489@nymph.detir.qld.gov.au> <19991121130020.A2369@netmonger.net> <199911220457.OAA47173@nymph.detir.qld.gov.au> <19991122185456.A9256@cicely8.cicely.de> In-Reply-To: <19991122185456.A9256@cicely8.cicely.de> from Bernd Walter at "Mon, 22 Nov 1999 18:54:57 +0100" Date: Tue, 23 Nov 1999 20:28:14 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 22nd November 1999, Bernd Walter wrote: >On Mon, Nov 22, 1999 at 02:57:39PM +1000, Stephen McKay wrote: >> I think there is a fault in fsck. Possibly it is because softupdates >> changed the rules. Having run md5 over the good copy and the broken >> (power failure interrupted) copy as well as everything in lost+found, >> I can say that no corrupted files survived, and everything in lost+found >> was a good copy of some file or other. So softupdates appears to be >> doing the right thing. But fsck didn't fix everything broken by the >> power interruption. >> >Sometimes fsck tells you that it needs a rerun. >See /usr/share/doc/smm/03.fsck/paper.ascii.gz for details about fsck. >Are you shure that this was not the case? It should print "PLEASE RERUN FSCK" in that case. It did not do so. It looks like other messages like "FILE SYSTEM MARKED DIRTY" are likely in this case. It said "FILE SYSTEM MARKED CLEAN" that evening. Eventually I'll get the time to do repeated powerdowns of my equipment to try to reproduce this. I hope you can see why I'm not rushing into this. :-) Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 3:15:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 17CF014BEC; Tue, 23 Nov 1999 03:14:51 -0800 (PST) (envelope-from reg@shale.csir.co.za) Received: from granite.hip.berkeley.edu (granite.hip.berkeley.edu [136.152.155.25]) by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id NAA96535; Tue, 23 Nov 1999 13:14:13 +0200 (SAT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by granite.hip.berkeley.edu (8.9.3/8.9.3) id DAA23734; Tue, 23 Nov 1999 03:13:51 -0800 (PST) (envelope-from reg) Date: Tue, 23 Nov 1999 03:13:50 -0800 From: Jeremy Lea To: billf@freebsd.org, current@freebsd.org, ports@freebsd.org Subject: Unbreak XFree86 Message-ID: <19991123031350.A28286@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This patch might be a bit heavy handed, but it seems to fix the problem... Index: Makefile =================================================================== RCS file: /usr/home/ncvs/ports/x11/XFree86/Makefile,v retrieving revision 1.68 diff -u -r1.68 Makefile --- Makefile 1999/11/23 04:49:34 1.68 +++ Makefile 1999/11/23 08:09:17 @@ -20,7 +20,7 @@ .include .if ${OSVERSION} > 400011 -BROKEN= problem with /usr/libexec/cpp +#BROKEN= problem with /usr/libexec/cpp .endif IS_INTERACTIVE= yes # configure script asks questions Index: files/kerberos4.diffs =================================================================== RCS file: /usr/home/ncvs/ports/x11/XFree86/files/kerberos4.diffs,v retrieving revision 1.4 diff -u -r1.4 kerberos4.diffs --- kerberos4.diffs 1998/09/23 05:50:40 1.4 +++ kerberos4.diffs 1999/11/23 10:05:40 @@ -34,7 +34,7 @@ +#define Krb4Includes /**/ +#endif +#ifndef Krb4Libraries -+#define Krb4Libraries -lkrb -ldes -lcrypt ++#define Krb4Libraries -lkrb -ldes -lcrypt -lcom_err +#endif +#else +#undef Krb4Includes @@ -170,8 +170,8 @@ diff -udr ../xc.ORIG/programs/xdm/session.c ./programs/xdm/session.c --- ../xc.ORIG/programs/xdm/session.c Sat Aug 23 14:12:29 1997 +++ ./programs/xdm/session.c Sat Aug 23 14:23:51 1997 -@@ -56,6 +56,10 @@ - # include +@@ -62,6 +62,10 @@ + # include #endif +#ifdef K4AUTH @@ -181,7 +181,7 @@ #ifndef GREET_USER_STATIC #include #ifndef RTLD_NOW -@@ -489,6 +493,28 @@ +@@ -498,6 +502,28 @@ } } #endif /* K5AUTH */ @@ -207,10 +207,10 @@ + } + } +#endif /* K4AUTH */ - } - Debug ("Display %s exiting with status %d\n", d->name, status); - exit (status); -@@ -673,6 +699,22 @@ + #ifdef USE_PAM + if (pamh) { + /* shutdown PAM session */ +@@ -717,6 +743,22 @@ } } #endif /* K5AUTH */ Index: patches/patch-4 =================================================================== RCS file: /usr/home/ncvs/ports/x11/XFree86/patches/patch-4,v retrieving revision 1.1 diff -u -r1.1 patch-4 --- patch-4 1999/07/27 14:27:33 1.1 +++ patch-4 1999/11/23 10:58:23 @@ -1,6 +1,15 @@ diff -ur /usr/ports/x11/XFree86/work/xc/config/cf/FreeBSD.cf config/cf/FreeBSD.cf --- /usr/ports/x11/XFree86/work/xc/config/cf/FreeBSD.cf Sun Nov 8 11:19:10 1998 +++ config/cf/FreeBSD.cf Tue Dec 8 10:10:06 1998 +@@ -60,7 +60,7 @@ + #define MkdirHierCmd mkdir -p + + #define CcCmd cc +-#define CppCmd /usr/libexec/cpp ++#define CppCmd /usr/bin/gcc -E + #define PreProcessCmd CppCmd + #define StandardCppDefines -traditional + #if defined(UseInstalled) && (!defined(XF86LinkKit) || !XF86LinkKit) @@ -282,7 +282,12 @@ # define AsmDefines AsmElfDefines #endif @@ -846,3 +855,14 @@ close(fd); return(Len); +--- config/imake/imakemdep.h.orig Tue Nov 23 02:56:33 1999 ++++ config/imake/imakemdep.h Tue Nov 23 02:57:25 1999 +@@ -266,7 +266,7 @@ + #define DEFAULT_CPP "/lib/pcpp" + #endif + #if defined(__386BSD__) || defined(__NetBSD__) || defined(__OpenBSD__) || defined(__FreeBSD__) +-#define DEFAULT_CPP "/usr/libexec/cpp" ++#define USE_CC_E + #endif + #if defined(__sgi) && defined(__ANSI_CPP__) + #define USE_CC_E Please test, polish and commit. Regards, -Jeremy -- | If I was not so weak, if I was not so cold, --+-- If I was not so scared of being broken, growing old, | I would be. I would be... frail. | - jars of clay / much afraid / frail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 3:24:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 37A1314BEC; Tue, 23 Nov 1999 03:24:40 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id NAA79171; Tue, 23 Nov 1999 13:24:16 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911231124.NAA79171@gratis.grondar.za> To: Jeremy Lea Cc: billf@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Unbreak XFree86 Date: Tue, 23 Nov 1999 13:24:15 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This patch might be a bit heavy handed, but it seems to fix the > problem... The KerberosIV bits can go; I have some cleanups that nuke that completely in favour of PAM. Now all I need to do is make PAM work for xdm... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 4: 8:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from drawbridge.ctc.com (drawbridge.ctc.com [147.160.99.35]) by hub.freebsd.org (Postfix) with ESMTP id E45D014D0E; Tue, 23 Nov 1999 04:08:20 -0800 (PST) (envelope-from cameron@ctc.com) Received: from server2.ctc.com (server2.ctc.com [147.160.1.4]) by drawbridge.ctc.com (8.9.3/8.9.3) with ESMTP id HAA13136; Tue, 23 Nov 1999 07:08:05 -0500 (EST) Received: from ctcjst-mail1.ctc.com (ctcjst-mail1.ctc.com [147.160.34.4]) by server2.ctc.com (8.9.3/8.9.3) with ESMTP id HAA20188; Tue, 23 Nov 1999 07:07:33 -0500 (EST) Received: by ctcjst-mail1.ctc.com with Internet Mail Service (5.5.2448.0) id ; Tue, 23 Nov 1999 07:03:21 -0500 Message-ID: <604CC98C4E6BD311AEF900A0C9EA54E1878B17@ctcjst-mail1.ctc.com> From: "Cameron, Frank" To: "'current@freebsd.org'" Cc: "'obrien@freebsd.org'" Subject: RE: Install Glitch Date: Tue, 23 Nov 1999 07:03:20 -0500 X-Mailer: Internet Mail Service (5.5.2448.0) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Works like a charm. Two more I've encountered: lynx: libncurses.so.3 libmytinfo.so.2 Grabbed these from a 3.2-STABLE box and everything seems fine. -Frank > -----Original Message----- > From: David O'Brien [SMTP:obrien@freebsd.org] > Sent: Friday, November 19, 1999 4:15 AM > To: Cameron, Frank > Cc: 'current@freebsd.org' > Subject: Re: Install Glitch > > > I just installed my first current box (19991115) and ran into a couple > of > > glitches with libraries and X. I installed the X-Kern-Developer and > then > > added some extras from custom. The errors I encountered (paraphrased) > were: > > > > missing libc.so.3 and libtermcap.so.2. > > This is now a known problem. Please either grab the libs from a 3-STABLE > snapshot, or email me and I'll email the ones I use. > > I am waiting a little bit longer before adding these libs to the compat3x > collection. > > -- > -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 8:17:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id D9F6B14E4D; Tue, 23 Nov 1999 08:17:06 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p113-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id DAA02057; Wed, 24 Nov 1999 03:24:20 +1100 Date: Wed, 24 Nov 1999 03:16:39 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Peter Wemm Cc: Brian Fundakowski Feldman , "Alexander N. Kabaev" , Jean-Marc Zucconi , marcel@FreeBSD.ORG, pho@FreeBSD.ORG, phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Netscape and -current In-Reply-To: <19991123033517.E7D731C6D@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Peter Wemm wrote: > I'm pretty sure it's this commit to i386/machdep.c: > === > revision 1.377 > date: 1999/11/21 14:46:43; author: pho; state: Exp; lines: +5 -5 > Moved useracc() to top of sigreturn as to avoid panic > caused by invalid arguments to rutine. > > Reviewed by: marcel, phk > === Hmm. My netscape works, but I didn't use merge that commit. I had already inadvertly fixed the bug in another way while cleaning up. Indeed, the proplem is checking the new context before checking that the context is actually new. Here is my version. int sigreturn(p, uap) struct proc *p; struct sigreturn_args /* { ucontext_t *ucp; } */ *uap; { struct trapframe *regs; ucontext_t *ucp; int cs, eflags; #if defined(COMPAT_43) || defined(COMPAT_SUNOS) if (((struct osigcontext *)uap->sigcntxp)->sc_trapno == 0x01d516) return (osigreturn(p, (struct osigreturn_args *)uap)); #endif ucp = uap-> /* ucp */ sigcntxp; if (!useracc((caddr_t)ucp, sizeof(*ucp), VM_PROT_READ)) return (EFAULT); eflags = ucp->uc_mcontext.mc_eflags; regs = p->p_md.md_regs; Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 8:43:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 239DA1530E for ; Tue, 23 Nov 1999 08:43:11 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA38489; Tue, 23 Nov 1999 08:42:54 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA42968; Tue, 23 Nov 1999 08:42:53 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Nov 1999 08:42:53 -0800 From: "David O'Brien" To: "Cameron, Frank" Cc: "'current@freebsd.org'" Subject: Re: Install Glitch Message-ID: <19991123084253.A42937@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <604CC98C4E6BD311AEF900A0C9EA54E1878B17@ctcjst-mail1.ctc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <604CC98C4E6BD311AEF900A0C9EA54E1878B17@ctcjst-mail1.ctc.com>; from cameron@ctc.com on Tue, Nov 23, 1999 at 07:03:20AM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Works like a charm. Two more I've encountered: > > lynx: > libncurses.so.3 > libmytinfo.so.2 Thanks! I've added them to my list. I'm going to populate compat3x from 3.4-RELEASE. So we aren't too far off. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 9:17:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 7454B14A04 for ; Tue, 23 Nov 1999 09:17:29 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id JAA58127 for ; Tue, 23 Nov 1999 09:16:23 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 23 Nov 1999 09:16:23 -0800 (PST) From: Doug White To: current@FreeBSD.ORG Subject: Re: Threads and my new job. In-Reply-To: <19991122185220.D301@sturm.canonware.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Jason Evans wrote: > Walnut Creek has hired me as a full time employee to work primarily on > improving and expanding FreeBSD's threads support. This is very exciting > to me, and I hope my work will be of benefit the FreeBSD community. [insert large amounts of cheering and celebration here] Jason, you are my savior. Go forth and do much to create Truly Kick Ass Threading. Give me my tools to smite these Linux database servers once and for all! :-) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 10:10:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 18C5D14A27; Tue, 23 Nov 1999 10:10:07 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA09145; Tue, 23 Nov 1999 11:09:59 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA14369; Tue, 23 Nov 1999 11:10:12 -0700 (MST) Message-Id: <199911231810.LAA14369@harmony.village.org> To: Poul-Henning Kamp Subject: Re: a bad sysinstall/useredit problem Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 21 Nov 1999 19:34:31 +0100." <17228.943209271@critter.freebsd.dk> References: <17228.943209271@critter.freebsd.dk> Date: Tue, 23 Nov 1999 11:10:12 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <17228.943209271@critter.freebsd.dk> Poul-Henning Kamp writes: : The problem is that the ex0 or ie0 driver, I'm not sure which, : hoses the 3com card such that the ep driver cannot read the : serial eeprom. I've often had to disable the ex driver when I've had cards at 0x300 in order to make the install work. I've been meaning to track it down more, but haven't had the chance. As luck would have it, this too is with the ep driver (well, also the ed driver since the ex probe code in 3.x at least doesn't omit the probe in the range that the ed driver has claimed). Not sure what to do about disabling the driver with userconfig, however. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 10:15:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 5BB0C15360 for ; Tue, 23 Nov 1999 10:15:38 -0800 (PST) (envelope-from forrie@forrie.com) Received: from boomer (boomer.navinet.net [216.67.12.90]) by forrie.net (8.9.3/8.9.3) with ESMTP id NAA00416 for ; Tue, 23 Nov 1999 13:15:36 -0500 (EST) Message-Id: <4.2.2.19991123131419.01495360@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 23 Nov 1999 13:15:58 -0500 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: ps on 4.0-current Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why does ps not show the full path on 4.0 as in 3.3? (for non-root users) ie: 4.0> ps -ax 134 v2 Is+ 0:00.00 (getty) 135 v3 Is+ 0:00.00 (getty) 136 v4 Is+ 0:00.00 (getty) 137 v5 Is+ 0:00.00 (getty) 3.3> ps -ax 312 v0 Is+ 0:00.01 /usr/libexec/getty Pc ttyv0 313 v1 Is+ 0:00.01 /usr/libexec/getty Pc ttyv1 314 v2 Is+ 0:00.01 /usr/libexec/getty Pc ttyv2 ?? _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 10:28:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id C917D153B6 for ; Tue, 23 Nov 1999 10:27:07 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991123132626.61771@mojave.sitaranetworks.com> Date: Tue, 23 Nov 1999 13:26:26 -0500 From: Greg Lehey To: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: ps on 4.0-current Reply-To: Greg Lehey References: <4.2.2.19991123131419.01495360@216.67.12.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <4.2.2.19991123131419.01495360@216.67.12.69>; from Forrest Aldrich on Tue, Nov 23, 1999 at 01:15:58PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 23 November 1999 at 13:15:58 -0500, Forrest Aldrich wrote: > > Why does ps not show the full path on 4.0 as in 3.3? > (for non-root users) > > ie: > > 4.0> ps -ax > > 134 v2 Is+ 0:00.00 (getty) > 135 v3 Is+ 0:00.00 (getty) > 136 v4 Is+ 0:00.00 (getty) > 137 v5 Is+ 0:00.00 (getty) Have you rebuilt world? It looks fine here with a kernel supped this morning and built 20 minutes ago. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 10:32:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 0155214A19 for ; Tue, 23 Nov 1999 10:32:48 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id MAA14961; Tue, 23 Nov 1999 12:32:12 -0600 (CST) (envelope-from dan) Date: Tue, 23 Nov 1999 12:32:12 -0600 From: Dan Nelson To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: ps on 4.0-current Message-ID: <19991123123212.B13601@dan.emsphone.com> References: <4.2.2.19991123131419.01495360@216.67.12.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <4.2.2.19991123131419.01495360@216.67.12.69>; from forrie@forrie.com on Tue, Nov 23, 1999 at 01:15:58PM -0500 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 23), Forrest Aldrich said: > Why does ps not show the full path on 4.0 as in 3.3? (for non-root > users) > > 4.0> ps -ax > > 134 v2 Is+ 0:00.00 (getty) > 135 v3 Is+ 0:00.00 (getty) > 136 v4 Is+ 0:00.00 (getty) > 137 v5 Is+ 0:00.00 (getty) > > 3.3> ps -ax > > 312 v0 Is+ 0:00.01 /usr/libexec/getty Pc ttyv0 > 313 v1 Is+ 0:00.01 /usr/libexec/getty Pc ttyv1 > 314 v2 Is+ 0:00.01 /usr/libexec/getty Pc ttyv2 That just means that on your 4.0 box, the gettys have been swapped out. ps will not swap the process back in just to get the processname unless you give it the -f flag (and are root). -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 11: 5:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 3F01C14F04 for ; Tue, 23 Nov 1999 11:05:35 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id VAA80946 for ; Tue, 23 Nov 1999 21:05:26 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911231905.VAA80946@gratis.grondar.za> To: current@freebsd.org Subject: FreeBSD security auditing project. Date: Tue, 23 Nov 1999 21:05:25 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello FreebSD'ers! [ Apologies to committers, I have Bcc'ed you to ensure you got this; you may get two copies. ] I have been charged with the duty of ensuring that FreeBSD gets a security audit that has the credibility of OpenBSD's. Consider this to be a request-for-discussion that will head us over to the actual work of getting it done. My proposals are pretty simple; 1) We need to eyeball _all_ of the code for potential security holes, and fix those ASAP. 2) I propose that diff(1) FreeBSD with {Open|Net}BSD, and with a security perspective apply those bits that look relevant and that will work. Who nose - we may even pick up some useful featurez! I am prepared to provide a (semi-)automatic tool that folks can submit their efforts to. (Yes, this is a group effort, we all need to get involved and donate our Copious Free Time. All the time that is currently invested in flamewars would be better spent here, *hint* *hint*.) The tool will be web-based and will give a good idea of progress, so we can even turn it into a sort of competition. Here is a starter list of what we need to audit for: o unsafe use of the str*(3) functions; strcat/strcpy/sprintf &c. o unsafe buffer handling (probably better handled by str*(3)??) o tmpfile races. o password buffers not being zeroed fast enough o unsafe use of command line or environment variables (?). o unsafe passing/exposure of sensitive data. o &c. please contribute here.... Let the discussion begin! All contributions welcome. Volunteers for the effort (there were lots of you at FreeBSDCon) please fight your way to the front now! You'll need to be a $#|t-hot programmer, paranoid, and experienced in code auditing to do the actual code review, but any other skills that may be of use (*anything* - volunteers are most welcome!!) please come forward with a miniresume and a proposal. I'll get a mailing list going if this is deemed necessary. Thanks! M To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 11:27:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 73FD115399 for ; Tue, 23 Nov 1999 11:27:05 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcm226.cvzoom.net (lcm226.cvzoom.net [208.230.69.226]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id OAA05087; Tue, 23 Nov 1999 14:07:04 -0500 (EST) Date: Tue, 23 Nov 1999 14:25:35 -0500 (EST) From: Donn Miller To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: <199911231905.VAA80946@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Mark Murray wrote: > Hello FreebSD'ers! > 2) I propose that diff(1) FreeBSD with {Open|Net}BSD, and with a > security perspective apply those bits that look relevant and that will > work. Who nose - we may even pick up some useful featurez! While we're on the subject of possibly borrowing code from NetBSD... NetBSD's wscons looks interesting. Any chance FreeBSD will adopt this, or will we stay with syscons? - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 11:35:19 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 618ED14BEE; Tue, 23 Nov 1999 11:35:17 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 284AE1CD433; Tue, 23 Nov 1999 11:35:16 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 23 Nov 1999 11:35:16 -0800 (PST) From: Kris Kennaway To: Mark Murray Cc: current@freebsd.org Subject: Re: FreeBSD security auditing project. In-Reply-To: <199911231905.VAA80949@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Mark Murray wrote: > 1) We need to eyeball _all_ of the code for potential security holes, > and fix those ASAP. > > 2) I propose that diff(1) FreeBSD with {Open|Net}BSD, and with a > security perspective apply those bits that look relevant and that will > work. Who nose - we may even pick up some useful featurez! I've been slowly trying to do some of this, and got through at least some of bin/ so far (billf has also been doing work on this, as have probably others). Probably this is the easiest way to get progress towards this goal - since FreeBSD is genetically very similar to OpenBSD, they've already fixed most of our security bugs (but not all!). > I am prepared to provide a (semi-)automatic tool that folks can > submit their efforts to. (Yes, this is a group effort, we all need to > get involved and donate our Copious Free Time. All the time that is > currently invested in flamewars would be better spent here, *hint* > *hint*.) The tool will be web-based and will give a good idea of > progress, so we can even turn it into a sort of competition. > > Here is a starter list of what we need to audit for: > > o unsafe use of the str*(3) functions; strcat/strcpy/sprintf &c. I wonder how many instances of the potentially unsafe functions there are in the source tree? :) > o unsafe buffer handling (probably better handled by str*(3)??) > > o tmpfile races. There is still a predictable tempfile name somewhere in binutils(?) which gets invoked during a parallel make world (with -pipe?). Sorry I can't remember more details, it was a while ago I found it. Running make world -j2 with the tempwatch port active will find the file, though. > o unsafe use of command line or environment variables (?). > > o unsafe passing/exposure of sensitive data. > > o &c. please contribute here.... Probably a good resource would be to collect together a bunch of papers/references describing what kinds of vulerabilities exist, how to exploit them, and how to avoid them (e.g. old phrack/bugtraq articles, etc). Programmer education is the key to secure programming! :-) I have some 500+ commit messages in my openbsd folder which are things I need to investigate further for relevancy. Some way of sharing these with the group, adding/removing/vetting changes which should be looked at would be very useful. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 11:43:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 7C22B153B1; Tue, 23 Nov 1999 11:43:14 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id VAA81500; Tue, 23 Nov 1999 21:42:57 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911231942.VAA81500@gratis.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. Date: Tue, 23 Nov 1999 21:42:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have some 500+ commit messages in my openbsd folder which are things I > need to investigate further for relevancy. Some way of sharing these with > the group, adding/removing/vetting changes which should be looked at would > be very useful. I'd be delighted to work with you on getting this lot exposed. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 11:48:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id D1C9215396 for ; Tue, 23 Nov 1999 11:48:44 -0800 (PST) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id UAA04756; Tue, 23 Nov 1999 20:47:44 +0100 (MET) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id UAA24792; Tue, 23 Nov 1999 20:47:39 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199911231905.VAA80946@gratis.grondar.za> References: <199911231905.VAA80946@gratis.grondar.za> Date: Tue, 23 Nov 1999 20:38:06 +0100 To: Mark Murray , current@FreeBSD.ORG From: Brad Knowles Subject: Re: FreeBSD security auditing project. Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:05 PM +0200 1999/11/23, Mark Murray wrote: > I have been charged with the duty of ensuring that FreeBSD gets a > security audit that has the credibility of OpenBSD's. You're just bound-and-determined to get me permanently drooling, aren't you? ;-) Seriously, I do not envy you the job that you have been charged with, but I do wish you all the luck you could possibly receive, and more. Never in a million years did I think I would see the day when either FreeBSD and OpenBSD would converge, or that FreeBSD would start seriously working towards the same kind of serious security posture that, until now, OpenBSD has pretty much owned outright. I don't know how long it's going to take you folks to get there, but I'm beginning to wonder if maybe I can't hold off switching some machines to OpenBSD and to instead do my best to secure them under FreeBSD, and avoid the platform split that would otherwise result (and have to be healed later, once the security audit was complete on FreeBSD). Thanks so much! -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 12: 6:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6943F1514E for ; Tue, 23 Nov 1999 12:06:53 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA02693; Tue, 23 Nov 1999 12:05:54 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Brad Knowles Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-reply-to: Your message of "Tue, 23 Nov 1999 20:38:06 +0100." Date: Tue, 23 Nov 1999 12:05:54 -0800 Message-ID: <2689.943387554@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't know how long it's going to take you folks to get there, > but I'm beginning to wonder if maybe I can't hold off switching some > machines to OpenBSD and to instead do my best to secure them under > FreeBSD, and avoid the platform split that would otherwise result > (and have to be healed later, once the security audit was complete on > FreeBSD). Part of what will make this go a lot faster is people like yourself committing to sticking around and helping us find and fix any security problems we might have, so I certainly hope you can do this! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 12:23:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id 4176515073 for ; Tue, 23 Nov 1999 12:23:44 -0800 (PST) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.1a/8.9.1) id EAA19557; Wed, 24 Nov 1999 04:22:57 +0800 (WST) From: Michael Kennett Message-Id: <199911232022.EAA19557@laurasia.com.au> Subject: Re: FreeBSD security auditing project. In-Reply-To: <199911231905.VAA80946@gratis.grondar.za> from Mark Murray at "Nov 23, 99 09:05:25 pm" To: mark@grondar.za (Mark Murray) Date: Wed, 24 Nov 1999 04:22:56 +0800 (WST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello FreebSD'ers! > [snip] > > I have been charged with the duty of ensuring that FreeBSD gets a > security audit that has the credibility of OpenBSD's. > > Consider this to be a request-for-discussion that will head us over to > the actual work of getting it done. [snip] Great idea. Here are some sites on the web that might be of interest: Security Bugware: http://oliver.efri.hr/~crv/security/ (Nice site, seems to be updated regularly) Security Focus: http://www.securityfocus.com/vdb (Vulnerability database -- a lot of the stuff seems to come from bugtraq) Phrack: http://www.phrack.com/ (Some of the recent phracks have been great. Check out: p48-13: TCP/IP SYN Flooding *** p49-14: Smashing the stack for Fun and Profit (READ IT!) p49-15: PortScanning without the SYN flag p51-05: File Descriptor Hijacking p51-11: The Art of Portscanning p52-16: Piercing Firewalls p53-06: T/TCP Vulnerabilities p54-06: The Belt-and-Suspenders Approach. OpenBSD security p55-08: The Frame Pointer Overwrite ) Regards, Mike Kennett (mike@laurasia.com.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 12:24: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 27D05153BE for ; Tue, 23 Nov 1999 12:23:56 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id PAA46984; Tue, 23 Nov 1999 15:23:23 -0500 (EST) Date: Tue, 23 Nov 1999 15:23:23 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: <199911231905.VAA80946@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Mark Murray wrote: > I am prepared to provide a (semi-)automatic tool that folks can > submit their efforts to. (Yes, this is a group effort, we all need to > get involved and donate our Copious Free Time. All the time that is > currently invested in flamewars would be better spent here, *hint* > *hint*.) The tool will be web-based and will give a good idea of > progress, so we can even turn it into a sort of competition. > Need volunteers, eh? I can be suckered in to helping in regards to building the web-based database for keeping track of the effor's progress. I may be no security expert, but I can build database-driven web sites (I should...it's my day job ;) ). Let me know what I can do to help. > > I'll get a mailing list going if this is deemed necessary. > freebsd-security? :) -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 12:40:59 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id BF9BF14C4F; Tue, 23 Nov 1999 12:40:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A81AB1CD776; Tue, 23 Nov 1999 12:40:57 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 23 Nov 1999 12:40:57 -0800 (PST) From: Kris Kennaway To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: <199911231942.VAA81500@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Mark Murray wrote: > > I have some 500+ commit messages in my openbsd folder which are things I > > need to investigate further for relevancy. Some way of sharing these with > > the group, adding/removing/vetting changes which should be looked at would > > be very useful. > > I'd be delighted to work with you on getting this lot exposed. Sounds good - just let me know what you want me to do. I should have mentioned, BTW, that most of these aren't security-related (but are general functionality enhancements/bugfixes/etc), but some fraction are. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 12:49:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 1D7B414C4F; Tue, 23 Nov 1999 12:49:12 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA82007; Tue, 23 Nov 1999 22:49:10 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911232049.WAA82007@gratis.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. Date: Tue, 23 Nov 1999 22:49:09 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'd be delighted to work with you on getting this lot exposed. > > Sounds good - just let me know what you want me to do. I should have > mentioned, BTW, that most of these aren't security-related (but are > general functionality enhancements/bugfixes/etc), but some fraction are. You know more about what they look like; make some suggestions (this is early days :-) ) .... My management tool here is going to be a hypertext-version of the source tree with the ability to add an audit-trail-kind-of-thingy. So when Joe Blow clicks on (say) src->bin->cat he'll find that (say) markm eyballed the code and kris diffed it with OpenBSD and merged in fixes - "cat now considered safe". There'll be other versions; Eyeballed/NotDiffed, Open, BeingEyballedBy, and so on. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 12:53: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id BC7F814C4F for ; Tue, 23 Nov 1999 12:52:57 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA20646; Tue, 23 Nov 1999 21:35:33 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA02414; Tue, 23 Nov 1999 21:20:42 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911232020.VAA02414@yedi.iaf.nl> Subject: Re: ps on 4.0-current In-Reply-To: <4.2.2.19991123131419.01495360@216.67.12.69> from Forrest Aldrich at "Nov 23, 1999 1:15:58 pm" To: forrie@forrie.com (Forrest Aldrich) Date: Tue, 23 Nov 1999 21:20:42 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Forrest Aldrich wrote ... > > Why does ps not show the full path on 4.0 as in 3.3? > (for non-root users) > > ie: > > 4.0> ps -ax > > 134 v2 Is+ 0:00.00 (getty) > 135 v3 Is+ 0:00.00 (getty) > 136 v4 Is+ 0:00.00 (getty) > 137 v5 Is+ 0:00.00 (getty) () means swapped out processes IIRC. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 12:57:40 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id E595114A21; Tue, 23 Nov 1999 12:57:38 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D3D4E1CD424; Tue, 23 Nov 1999 12:57:38 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 23 Nov 1999 12:57:38 -0800 (PST) From: Kris Kennaway To: Kelly Yancey Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Kelly Yancey wrote: > Need volunteers, eh? I can be suckered in to helping in regards to > building the web-based database for keeping track of the effor's progress. > I may be no security expert, but I can build database-driven web sites (I > should...it's my day job ;) ). > Let me know what I can do to help. Cool, we have a database guy! :) Let me throw in some ideas.. I think it would be very useful to have a database which can track submitted open/netbsd CVS commits (with the code diff included), preferably mapped to the relevant file in the freebsd tree if possible according to a path mapping table (i.e. /some/openbsd/path/file.c mapped to /equiv/freebsd.path/file.c). I guess this is more of a CVS interface along the lines of cvsweb..what we're really doing here is doing a (manual) partial merge of two CVS repositories. But, CVS is a kind of database, right? :) Also useful would be a review status of the freebsd tree. So (approved) people can "sign off" on a particular file or directory as having been reviewed as of a certain date, and we can work in a coordinated fashion. Hmm, again this sounds like a CVS tree, with reviews being tags. Maybe what we actually want is a better RCS system for FreeBSD. > > I'll get a mailing list going if this is deemed necessary. > > > > freebsd-security? :) Hmm, I think most of the traffic would be fairly off-topic for there. I think a separate freebsd-audit list (for discussion of relevancy of changes, discussion of bugs, etc) would be the way to go. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 12:58:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-119.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.247]) by hub.freebsd.org (Postfix) with ESMTP id 9480514A21 for ; Tue, 23 Nov 1999 12:58:51 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA05903; Tue, 23 Nov 1999 20:58:05 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA02408; Tue, 23 Nov 1999 21:03:04 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911232103.VAA02408@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Dan Nelson Cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: ps on 4.0-current In-Reply-To: Message from Dan Nelson of "Tue, 23 Nov 1999 12:32:12 CST." <19991123123212.B13601@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Nov 1999 21:03:04 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In the last episode (Nov 23), Forrest Aldrich said: > > Why does ps not show the full path on 4.0 as in 3.3? (for non-root > > users) > > > > 4.0> ps -ax > > > > 134 v2 Is+ 0:00.00 (getty) > > 135 v3 Is+ 0:00.00 (getty) > > 136 v4 Is+ 0:00.00 (getty) > > 137 v5 Is+ 0:00.00 (getty) > > > > 3.3> ps -ax > > > > 312 v0 Is+ 0:00.01 /usr/libexec/getty Pc ttyv0 > > 313 v1 Is+ 0:00.01 /usr/libexec/getty Pc ttyv1 > > 314 v2 Is+ 0:00.01 /usr/libexec/getty Pc ttyv2 > > That just means that on your 4.0 box, the gettys have been swapped out. > ps will not swap the process back in just to get the processname unless > you give it the -f flag (and are root). $ ps jtva USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND root 222 1 222 9dac40 0 Is+ va 0:00.01 (getty) $ ps fjtva USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND root 222 1 222 9dac40 0 Is+ va 0:00.01 (getty) $ sudo ps jtva USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND root 222 1 222 9dac40 0 Is+ va 0:00.01 /usr/libexec/getty Pc tt $ sudo ps fjtva USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND root 222 1 222 9dac40 0 Is+ va 0:00.01 /usr/libexec/getty Pc tt $ head -1 /etc/motd FreeBSD 4.0-CURRENT (HAK) #9: Mon Nov 22 01:09:55 GMT 1999 This looks a bit wrong.... > -- > Dan Nelson > dnelson@emsphone.com -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 12:59:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 7F7BB153D8 for ; Tue, 23 Nov 1999 12:59:05 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.0.4] ident=ben) by scientia.demon.co.uk with smtp (Exim 3.092 #1) id 11qLfC-0006Pu-00; Tue, 23 Nov 1999 19:31:42 +0000 Date: Tue, 23 Nov 1999 19:31:42 +0000 From: Ben Smithurst To: Dan Nelson Cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: ps on 4.0-current Message-ID: <19991123193142.A2126@strontium.scientia.demon.co.uk> References: <4.2.2.19991123131419.01495360@216.67.12.69> <19991123123212.B13601@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991123123212.B13601@dan.emsphone.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Nelson wrote: > In the last episode (Nov 23), Forrest Aldrich said: >> Why does ps not show the full path on 4.0 as in 3.3? (for non-root >> users) >> >> 4.0> ps -ax >> >> 134 v2 Is+ 0:00.00 (getty) >> 135 v3 Is+ 0:00.00 (getty) >> 136 v4 Is+ 0:00.00 (getty) >> 137 v5 Is+ 0:00.00 (getty) >> >> 3.3> ps -ax >> >> 312 v0 Is+ 0:00.01 /usr/libexec/getty Pc ttyv0 >> 313 v1 Is+ 0:00.01 /usr/libexec/getty Pc ttyv1 >> 314 v2 Is+ 0:00.01 /usr/libexec/getty Pc ttyv2 > > That just means that on your 4.0 box, the gettys have been swapped out. Wouldn't there be a difference in the STAT columns on each system if that were the case? (A 'W' according to ps(1) for the swapped out processes.) -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 13: 5:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 7538A14A21 for ; Tue, 23 Nov 1999 13:05:22 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40331>; Wed, 24 Nov 1999 07:57:03 +1100 Content-return: prohibited Date: Wed, 24 Nov 1999 08:03:52 +1100 From: Peter Jeremy Subject: Re: FreeBSD security auditing project. In-reply-to: To: Kris Kennaway Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov24.075703est.40331@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <199911231905.VAA80949@gratis.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-24 06:35:16 +1100, Kris Kennaway wrote: >> o unsafe use of the str*(3) functions; strcat/strcpy/sprintf &c. > >I wonder how many instances of the potentially unsafe functions there are >in the source tree? :) A 'grep | wc' equivalent over the source tree gives: gets 110 strcat 2860 strcpy 4717 strncat 167 strncpy 1514 sprintf 6839 vsprintf 133 Note that (particularly in the case of gets()), this includes the definition(s) in libraries and declarations in various headers as well as occurrences in comments, strings and structure/union members. There are also occurrences in dead or unused code (eg gnu/usr.bin/as/config/tc-vax.c calls gets() 10 times as well as referring to it in a comment). These counts are based on tokens, not strings, so (eg) fgets doesn't get counted as gets. A string search for (roughly) "scanf.*%s" also picks up 74 cases of un-bounded string scans. And these are the easy ones... Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 13:18:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6CDAC14E73; Tue, 23 Nov 1999 13:18:54 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA03034; Tue, 23 Nov 1999 13:19:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Kelly Yancey , Mark Murray , current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-reply-to: Your message of "Tue, 23 Nov 1999 12:57:38 PST." Date: Tue, 23 Nov 1999 13:19:17 -0800 Message-ID: <3030.943391957@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Also useful would be a review status of the freebsd tree. So (approved) > people can "sign off" on a particular file or directory as having been > reviewed as of a certain date, and we can work in a coordinated fashion. Well, IMHO what you guys most significantly need is a "tinderbox" style page which shows all the external reviewers just how well things are going and what work remains to be done. It should be a professional-looking page which provides useful content and also has a "developer sign-on" feature which allows others to adopt sections for review and/or check things off as reviewed (at which point the visual appearance of the item changes and a datestamp is done so we know when to come back and audit things all over again). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 13:25:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 95B6E153DC for ; Tue, 23 Nov 1999 13:24:57 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id WAA36676; Tue, 23 Nov 1999 22:23:49 +0100 (CET) (envelope-from leifn@neland.dk) Date: Tue, 23 Nov 1999 22:23:49 +0100 (CET) From: Leif Neland To: Mark Murray Cc: Clive Lin , current@FreeBSD.ORG Subject: Re: ftpd is not listed in pam.conf In-Reply-To: <199911221202.OAA72949@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Mark Murray wrote: > > May this is not the best way for ftpd to use pam (many other lines for login, > > may ftpd should be so). But I think ftpd should be listed in /etc/pam.conf. > > > > Any plan to fix it in /usr/src/etc/pam.conf ? > > On my list! :-) > rsh too, while you're at it, please. (Only using it for internal use) Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 14: 0:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 15B5114A24 for ; Tue, 23 Nov 1999 14:00:44 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA44729; Tue, 23 Nov 1999 13:59:41 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA50009; Tue, 23 Nov 1999 13:59:41 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Nov 1999 13:59:41 -0800 From: "David O'Brien" To: Kelly Yancey Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. Message-ID: <19991123135941.A49964@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199911231905.VAA80946@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kbyanc@posi.net on Tue, Nov 23, 1999 at 03:23:23PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 23, 1999 at 03:23:23PM -0500, Kelly Yancey wrote: > I may be no security expert, So??? You can read C code, right? What needs to happen is a leader to take charge and give people direction. If someone gave you a few sequences of code to look for, you could find them right? If you were also given a typical work around, you could apply it, right? Not everyone in the OpenBSD project came into this with a security mindset. Rather it was alot of getting people rallied around the cause and teaching them how to go about it. Before we go off 1/2 cocked, we need to get organized. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 14: 2:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp.manhattanprojects.com (smtp.manhattanprojects.com [207.181.119.22]) by hub.freebsd.org (Postfix) with ESMTP id 2FDDF14C1F; Tue, 23 Nov 1999 14:02:46 -0800 (PST) (envelope-from gerald@manhattanprojects.com) Received: from manhattanprojects.com (xs.lab.glc.com [10.0.0.14]) by smtp.manhattanprojects.com (8.9.1/8.8.7) with ESMTP id QAA20205; Tue, 23 Nov 1999 16:54:18 -0500 (EST) (envelope-from gerald@manhattanprojects.com) Message-ID: <383B0F03.70A84532@manhattanprojects.com> Date: Tue, 23 Nov 1999 17:02:43 -0500 From: Gerald Abshez X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > Let me throw in some ideas.. > > I think it would be very useful to have a database which can track > submitted open/netbsd CVS commits (with the code diff included), > preferably mapped to the relevant file in the freebsd tree if possible > according to a path mapping table (i.e. /some/openbsd/path/file.c mapped > to /equiv/freebsd.path/file.c). Here is my 0.02: I think it would be useful to identify "unsafe" functions, so that anyone can participate in the "eyeball" portion of the game. This means that we need eyeballed, identified as a (potential) problem and fixed, as well as some other possiblities. There is a lot of code out there, and it would help if we could involve the non-programmers in the search. Comments? Gerald. -- This is your FreeBSD -- Where do YOU want to go tommorow? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 14: 3:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6B642153A1; Tue, 23 Nov 1999 14:03:08 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA44764; Tue, 23 Nov 1999 14:03:03 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA50032; Tue, 23 Nov 1999 14:03:03 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Nov 1999 14:03:03 -0800 From: "David O'Brien" To: Mark Murray Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. Message-ID: <19991123140303.B49964@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199911232049.WAA82007@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911232049.WAA82007@gratis.grondar.za>; from mark@grondar.za on Tue, Nov 23, 1999 at 10:49:09PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So when Joe Blow clicks on (say) src->bin->cat he'll find that > (say) markm eyballed the code and kris diffed it with OpenBSD > and merged in fixes - "cat now considered safe". Until the next commit to cat. A security review is never done. We need to be in a mode where every commit is suspect and people are compelled to review it. BDE's use of CTM to review changes is actually rather affective in this reguard. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 14: 7:22 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id E570B14EBF; Tue, 23 Nov 1999 14:07:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D70E41CD7BC; Tue, 23 Nov 1999 14:07:15 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 23 Nov 1999 14:07:15 -0800 (PST) From: Kris Kennaway To: David O'Brien Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: <19991123140303.B49964@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, David O'Brien wrote: > A security review is never done. We need to be in a mode where every > commit is suspect and people are compelled to review it. BDE's use of > CTM to review changes is actually rather affective in this reguard. A CVS tag would also accomplish this and could be slid forward when the new commit is reviewed. I don't know how feasible this would be from the POV of CVS mechanics, but it has the advantage of being in the main tree for everyone to see. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 14: 8:38 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id A920514C1F; Tue, 23 Nov 1999 14:08:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 920F81CD7BC; Tue, 23 Nov 1999 14:08:31 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 23 Nov 1999 14:08:31 -0800 (PST) From: Kris Kennaway To: Gerald Abshez Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: <383B0F03.70A84532@manhattanprojects.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Gerald Abshez wrote: > Here is my 0.02: > > I think it would be useful to identify "unsafe" functions, so that > anyone can participate in the "eyeball" portion of the game. This means > that we need eyeballed, identified as a (potential) problem and fixed, > as well as some other possiblities. There is a lot of code out there, > and it would help if we could involve the non-programmers in the search. > > Comments? Yep, this is part of the "education" component: "this is what an unsafe function call looks like, and this is how to fix it". There's bound to be enough useful documentation out there which we can collect and point to. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 14:15:54 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 02FFF14C1F; Tue, 23 Nov 1999 14:15:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E72191CD7BC; Tue, 23 Nov 1999 14:15:52 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 23 Nov 1999 14:15:52 -0800 (PST) From: Kris Kennaway To: peter.jeremy@alcatel.com.au Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: <99Nov24.075703est.40331@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Nov 1999, Peter Jeremy wrote: > >> o unsafe use of the str*(3) functions; strcat/strcpy/sprintf &c. > > > >I wonder how many instances of the potentially unsafe functions there are > >in the source tree? :) > > A 'grep | wc' equivalent over the source tree gives: > > gets 110 > strcat 2860 > strcpy 4717 > strncat 167 > strncpy 1514 > sprintf 6839 > vsprintf 133 *ouch* :-) > And these are the easy ones... Indeed :-( Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 14:23:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C7A9615436 for ; Tue, 23 Nov 1999 14:23:36 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA45523 for ; Tue, 23 Nov 1999 14:22:58 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA50179 for current@freebsd.org; Tue, 23 Nov 1999 14:22:58 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Nov 1999 14:22:58 -0800 From: "David O'Brien" To: current@freebsd.org Subject: Re: FreeBSD security auditing project. Message-ID: <19991123142258.C49964@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <199911231905.VAA80946@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911231905.VAA80946@gratis.grondar.za>; from mark@grondar.za on Tue, Nov 23, 1999 at 09:05:25PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 2) I propose that diff(1) FreeBSD with {Open|Net}BSD, This is not the easiest thing to do (I've tried). Rather one should look at what changes OpenBSD has done to a piece of code since they imported it from NetBSD and compare with FreeBSD code to see if the OpenBSD change is applicable to us. {Net,Open}BSD kept a lot of Net/2 [influenced] code (not sure how they were allowed to do that), while we started fresh with 4.4BSD. Thus diffs between us and them in userland utils and be quite different. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 14:27: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1A73215487; Tue, 23 Nov 1999 14:26:52 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA45565; Tue, 23 Nov 1999 14:26:27 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA50264; Tue, 23 Nov 1999 14:26:26 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Nov 1999 14:26:26 -0800 From: "David O'Brien" To: Kris Kennaway Cc: peter.jeremy@alcatel.com.au, current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. Message-ID: <19991123142626.D49964@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <99Nov24.075703est.40331@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Tue, Nov 23, 1999 at 02:15:52PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > A 'grep | wc' equivalent over the source tree gives: > > > > gets 110 > > strcat 2860 > > strcpy 4717 > > strncat 167 > > strncpy 1514 > > sprintf 6839 > > vsprintf 133 > > *ouch* :-) This means nothing out of context. I hope we don't go on a witch hunt. > > And these are the easy ones... > Indeed :-( Global search and replace of these can obfuscate code. Things must be looked for in context. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 14:30:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 297DD15455 for ; Tue, 23 Nov 1999 14:30:05 -0800 (PST) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id XAA06558; Tue, 23 Nov 1999 23:29:32 +0100 (MET) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id XAA28917; Tue, 23 Nov 1999 23:29:31 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <2689.943387554@localhost> References: <2689.943387554@localhost> Date: Tue, 23 Nov 1999 23:20:59 +0100 To: "Jordan K. Hubbard" From: Brad Knowles Subject: Re: FreeBSD security auditing project. Cc: Mark Murray , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:05 PM -0800 1999/11/23, Jordan K. Hubbard wrote: > Part of what will make this go a lot faster is people like yourself > committing to sticking around and helping us find and fix any security > problems we might have, so I certainly hope you can do this! I'm certainly willing to do what I can to help, although I have to admit that I may need a bit of help identifying what I can do. ;-) -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 14:32:27 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 1BFEC15433; Tue, 23 Nov 1999 14:32:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0C3451CD7C0; Tue, 23 Nov 1999 14:32:26 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 23 Nov 1999 14:32:26 -0800 (PST) From: Kris Kennaway To: David O'Brien Cc: peter.jeremy@alcatel.com.au, current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: <19991123142626.D49964@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, David O'Brien wrote: > > *ouch* :-) > > This means nothing out of context. I hope we don't go on a witch hunt. Right, but they still need to be checked. > Global search and replace of these can obfuscate code. Things must be > looked for in context. I hope no-one's suggesting we do the former :-) Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15: 4:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (Postfix) with ESMTP id D0F8815254; Tue, 23 Nov 1999 15:04:06 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-mdt.sentex.net [205.211.164.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id SAA21030; Tue, 23 Nov 1999 18:02:07 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.1.19991123175926.04d892f0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 23 Nov 1999 18:02:05 -0500 To: Vlad Skvortsov , freebsd-security@FreeBSD.ORG From: Mike Tancsa Subject: Re: bind vulnerabilities Cc: current@FreeBSD.ORG In-Reply-To: <19991123235738.D595@high.net.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:57 PM 11/23/99 , Vlad Skvortsov wrote: > Sorry for probably a bit stupid question (I've been out of lists for > a while). Are patches for named already in -current or -stable ? > No they have not to either. Use it out of the ports. Be sure to adjust named-xfer "/usr/local/libexec/named-xfer"; // _PATH_XFER accordingly in your named.conf file. This raises a question, why has the new BIND not been committed to current at least ? I am not complaining, just curious as to the rationale ? ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 519 651 3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:11:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 682C1153E1 for ; Tue, 23 Nov 1999 15:11:49 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id RAA19426; Tue, 23 Nov 1999 17:11:37 -0600 (CST) (envelope-from dan) Date: Tue, 23 Nov 1999 17:11:37 -0600 From: Dan Nelson To: Brian Somers Cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: ps on 4.0-current Message-ID: <19991123171137.A19161@dan.emsphone.com> References: <199911232103.VAA02408@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911232103.VAA02408@hak.lan.Awfulhak.org>; from "Brian Somers" on Tue Nov 23 21:03:04 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 23), Brian Somers said: > $ ps jtva > USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND > root 222 1 222 9dac40 0 Is+ va 0:00.01 (getty) > $ sudo ps jtva > USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND > root 222 1 222 9dac40 0 Is+ va 0:00.01 /usr/libexec/getty Pc tt > $ head -1 /etc/motd > FreeBSD 4.0-CURRENT (HAK) #9: Mon Nov 22 01:09:55 GMT 1999 > > This looks a bit wrong.... Now that does look weird. After a bit more investigation, it looks like you can only get the full commandline of your own processes. Root can see all commandlines. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:17:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgw.cablecom.ne.jp (mailgw.cablecom.ne.jp [202.248.199.37]) by hub.freebsd.org (Postfix) with ESMTP id 261C914A17; Tue, 23 Nov 1999 15:17:09 -0800 (PST) (envelope-from motoyuki@snipe.rim.or.jp) Received: from srv2.cablecom.ne.jp by mailgw.cablecom.ne.jp (8.9.3/3.7W) id IAA12012; Wed, 24 Nov 1999 08:15:24 +0900 (JST) Received: from mail.snipe.rim.or.jp by srv2.cablecom.ne.jp (8.9.3/3.7W) id IAA09210; Wed, 24 Nov 1999 08:15:23 +0900 (JST) Received: from sakura.snipe.rim.or.jp (sakura.snipe.rim.or.jp [192.168.11.4]) by mail.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id IAA79848; Wed, 24 Nov 1999 08:15:22 +0900 (JST) Received: from sakura.snipe.rim.or.jp (localhost [127.0.0.1]) by sakura.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id IAA75236; Wed, 24 Nov 1999 08:15:22 +0900 (JST) Message-Id: <199911232315.IAA75236@sakura.snipe.rim.or.jp> To: current@FreeBSD.org Cc: marcel@FreeBSD.org X-Mailer: mh-e on Mule 2.3 / Emacs 19.34.1 Subject: make -DWANT_AOUT world fails Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Wed, 24 Nov 1999 08:15:22 +0900 From: Motoyuki Konno Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, "make -DWANT_AOUT world" on my current box fails because of the recent changes to src/Makefile.inc1. ======== log starts here ======== -------------------------------------------------------------- >>> Building legacy libraries -------------------------------------------------------------- cd /usr/src; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib/aout LIBRARY_PATH=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib PERL5LIB=/usr/libdata/perl/5.00503 OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr/libexec CFLAGS="-nostdinc -O2 -m486 -pipe" /usr/obj/usr/src/tmp/usr/bin/make DESTDIR=/usr/obj/aout/usr/src/tmp -DNOINFO -DNOMAN -f Makefile.inc1 bootstrap-libraries make: don't know how to make bootstrap-libraries. Stop *** Error code 2 ========= log ends here ========= I think we must delete following 2 lines in Makefile.inc1. ======== --- Makefile.inc1.old Wed Nov 24 01:39:15 1999 +++ Makefile.inc1 Wed Nov 24 08:10:25 1999 @@ -808,8 +808,6 @@ @echo ">>> Building legacy libraries" @echo "--------------------------------------------------------------" cd ${.CURDIR}; \ - ${XMAKE} -DNOINFO -DNOMAN -f Makefile.inc1 bootstrap-libraries - cd ${.CURDIR}; \ ${XMAKE} -DNOINFO -DNOMAN -f Makefile.inc1 libraries @echo @echo "--------------------------------------------------------------" ======== -- ------------------------------------------------------------------------ Motoyuki Konno mkonno@res.yamanashi-med.ac.jp (Univ) motoyuki@snipe.rim.or.jp (Home) motoyuki@FreeBSD.ORG (FreeBSD Project) Yamanashi Medical University http://www.freebsd.org/~motoyuki/ (WWW) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:19:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id F1A2614A17; Tue, 23 Nov 1999 15:18:22 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id SAA26261; Tue, 23 Nov 1999 18:12:09 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Tue, 23 Nov 1999 18:12:09 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Bruce Evans Cc: Peter Wemm , "Alexander N. Kabaev" , Jean-Marc Zucconi , marcel@FreeBSD.org, pho@FreeBSD.org, phk@FreeBSD.org, current@FreeBSD.org Subject: Re: Netscape and -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Nov 1999, Bruce Evans wrote: > Hmm. My netscape works, but I didn't use merge that commit. I had already > inadvertly fixed the bug in another way while cleaning up. > > Indeed, the proplem is checking the new context before checking that the > context is actually new. > > Here is my version. Hmm... > > int > sigreturn(p, uap) > struct proc *p; > struct sigreturn_args /* { > ucontext_t *ucp; > } */ *uap; > { > struct trapframe *regs; > ucontext_t *ucp; > int cs, eflags; > > #if defined(COMPAT_43) || defined(COMPAT_SUNOS) > if (((struct osigcontext *)uap->sigcntxp)->sc_trapno == 0x01d516) > return (osigreturn(p, (struct osigreturn_args *)uap)); > #endif I don't see how this fixes things, other than hiding it. Since the i386 memory model we use maps kernel and user memory all at the same time, this code is reading directly from user space memory, right? If this is the case, wouldn't a copyin() be the proper thing to do? At least doing the useracc() would be better than doing nothing, wouldn't it? > > ucp = uap-> /* ucp */ sigcntxp; > if (!useracc((caddr_t)ucp, sizeof(*ucp), VM_PROT_READ)) > return (EFAULT); > eflags = ucp->uc_mcontext.mc_eflags; > regs = p->p_md.md_regs; > > Bruce > > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:20: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id D90B21540D; Tue, 23 Nov 1999 15:19:52 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40341>; Wed, 24 Nov 1999 10:12:50 +1100 Content-return: prohibited Date: Wed, 24 Nov 1999 10:19:37 +1100 From: Peter Jeremy Subject: Re: FreeBSD security auditing project. In-reply-to: <19991123142626.D49964@dragon.nuxi.com> To: David O'Brien Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov24.101250est.40341@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <99Nov24.075703est.40331@border.alcanet.com.au> <19991123142626.D49964@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-24 09:26:26 +1100, David O'Brien wrote: >> > A 'grep | wc' equivalent over the source tree gives: >> > >> > gets 110 >> > strcat 2860 >> > strcpy 4717 >> > strncat 167 >> > strncpy 1514 >> > sprintf 6839 >> > vsprintf 133 >> >> *ouch* :-) > >This means nothing out of context. I hope we don't go on a witch hunt. Agreed. I wasn't suggesting that all these occurrences are examples of unsafe use. They just give an order-of-magnitude indication of the number of places they are used. That said, I'm not sure that going through the code and checking every call to strcpy() (for example) is the right way to go about things. It _is_ possible to use strcpy() safely, at the same time, it is possible to use strlcpy() or snprintf() _unsafely_ (mainly mis- interpreting the return value when the result is larger than the destination buffer). In any case, you still miss the case where someone has implemented their own string copy function and is using it incorrectly. I believe the correct way is a line-by-line audit of all the code, checking for the various security problems. One thing that would help with this task is a list of code patterns that indicate security problems. This list will make it easier for auditors (and will expand over time). I suspect that a 'cvs diff' of the OpenBSD code tree is the best starting point. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:20:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id E8E4315193; Tue, 23 Nov 1999 15:20:52 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id SAA50823; Tue, 23 Nov 1999 18:20:19 -0500 (EST) Date: Tue, 23 Nov 1999 18:20:19 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: <19991123135941.A49964@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, David O'Brien wrote: > On Tue, Nov 23, 1999 at 03:23:23PM -0500, Kelly Yancey wrote: > > I may be no security expert, > > So??? You can read C code, right? What needs to happen is a leader to > take charge and give people direction. If someone gave you a few > sequences of code to look for, you could find them right? If you were > also given a typical work around, you could apply it, right? > > Not everyone in the OpenBSD project came into this with a security > mindset. Rather it was alot of getting people rallied around the cause > and teaching them how to go about it. Before we go off 1/2 cocked, we > need to get organized. > > -- > -- David (obrien@NUXI.com) > Maybe I'm being modest. :) Actually I've been programming for about 10 years (surely not as long as others on this list) and taught C programming for 2 of those years. So yes, I can not only read C code, but I spew it fairly often. In any event, I suspect your comments aren't entirely directed at my quip, but rather at the sentiment. Point taken. Perhaps, I'll start taking a second-look at some of the fine BSD code I've taken for granted all these years. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:22:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 97E5C15433; Tue, 23 Nov 1999 15:21:53 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id SAA03005; Tue, 23 Nov 1999 18:21:17 -0500 (EST) (envelope-from mwlucas) Message-Id: <199911232321.SAA03005@blackhelicopters.org> Subject: Re: FreeBSD security auditing project. In-Reply-To: from Kris Kennaway at "Nov 23, 1999 2: 8:31 pm" To: kris@hub.freebsd.org (Kris Kennaway) Date: Tue, 23 Nov 1999 18:21:17 -0500 (EST) Cc: current@freebsd.org From: mwlucas@gltg.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Here is my 0.02: > > > > I think it would be useful to identify "unsafe" functions, so that > > anyone can participate in the "eyeball" portion of the game. This means > > that we need eyeballed, identified as a (potential) problem and fixed, > > as well as some other possiblities. There is a lot of code out there, > > and it would help if we could involve the non-programmers in the search. > > > > Comments? > > Yep, this is part of the "education" component: "this is what an unsafe > function call looks like, and this is how to fix it". There's bound to be > enough useful documentation out there which we can collect and point to. Speaking as a beginning programmer, longtime FreeBSD user: Given the above, I would be happy to contribute eyeballs. As a network engineer, I spend a lot of time alone with my laptop. Might I suggest a set of instructions along the lines of: a) This is what an unsafe function call looks like b) This is a typical workaround for unsafe call X, Y, Z c) Pick a chunk of code. Begin looking for these calls. d) when you find one of these calls 1) Apply the workaround 2) Make sure the program still compiles 3) submit patch to security-audit-coordinator@freebsd.org e) Repeat until intimately familiar with BSD In fact, I'll go further: If someone can point out a reliable resource on the Net for a) and b), I'll be happy to write up a first draft of "The FreeBSD Security Audit for Beginners". I'm sure that any number of programmers out there would be happy to review it for technical accuracy before putting it into circulation. After all, FreeBSD articles are covering Christmas this year. I suppose the least I can do is write something for you folks for free. ;) ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:24: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6E62715458; Tue, 23 Nov 1999 15:22:30 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id HAA24337; Tue, 23 Nov 1999 07:23:30 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Tue, 23 Nov 1999 07:23:30 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Peter Wemm Cc: Christopher Masto , "Daniel O'Connor" , Steve Kargl , current@FreeBSD.org, Jean-Marc Zucconi , "Alexander N. Kabaev" Subject: Re: Netscape and -current In-Reply-To: <19991123061312.248461C6D@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Peter Wemm wrote: > Brian Fundakowski Feldman wrote: > > Forget anything I said about KAME being the strong possibility :) As > > soon as peter noted what commit it could have to do with, I figured > > it out and fixed it; after testing, I committed it. Be happy :) > > Your fix suffers from exactly the same problem.. Suppose down the track > that ucontext_t becomes smaller than 'struct sigocontext' ? You're then > failing what would have worked. The check against sizeof osigcontext should > not be fatal. That will not happen, though. Your proposal suffers from a very similar problem. Okay, let's assume that ucontext_t is _smaller_ than a struct osigcontext. If it fails the "osigcontext size test", it won't go to osigreturn, fine. BUT, it continues on, and is taken as a valid ucontext_t instead of an EINVAL osigcontext. Do you see where the problem is with this approach? Since the revision I committed went under an assumption that's alway going to be true, and even if it weren't, it would be updated to match the world anyway, I don't see the problem. > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:41:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgw.cablecom.ne.jp (mailgw.cablecom.ne.jp [202.248.199.37]) by hub.freebsd.org (Postfix) with ESMTP id C2EF31542A for ; Tue, 23 Nov 1999 15:41:17 -0800 (PST) (envelope-from motoyuki@snipe.rim.or.jp) Received: from srv2.cablecom.ne.jp by mailgw.cablecom.ne.jp (8.9.3/3.7W) id IAA12358; Wed, 24 Nov 1999 08:40:47 +0900 (JST) Received: from mail.snipe.rim.or.jp by srv2.cablecom.ne.jp (8.9.3/3.7W) id IAA10262; Wed, 24 Nov 1999 08:40:45 +0900 (JST) Received: from sakura.snipe.rim.or.jp (sakura.snipe.rim.or.jp [192.168.11.4]) by mail.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id IAA80751; Wed, 24 Nov 1999 08:40:44 +0900 (JST) Received: from sakura.snipe.rim.or.jp (localhost [127.0.0.1]) by sakura.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id IAA14559; Wed, 24 Nov 1999 08:40:44 +0900 (JST) Message-Id: <199911232340.IAA14559@sakura.snipe.rim.or.jp> To: Marcel Moolenaar Cc: current@FreeBSD.org Subject: Re: make -j13 world broken X-Mailer: mh-e on Mule 2.3 / Emacs 19.34.1 References: <199911230809.KAA76941@zibbi.mikom.csir.co.za> <383A639C.4D21A2FF@scc.nl> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Wed, 24 Nov 1999 08:40:44 +0900 From: Motoyuki Konno Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Marcel Moolenaar wrote: > > A normal "make world" on current is ok, but a "make -j13 world" is broken. > > I have looked at it a little bit, but I can't figure out what is going > > wrong. It dies with: I also found that "make -j world" is broken, with Makefile.inc1 rev 1.93. ======== log starts here ======== -------------------------------------------------------------- >>> Building elf libraries -------------------------------------------------------------- cd /usr/src; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib PERL5LIB=/usr/libdata/perl/5.00503 OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr/libexec CFLAGS="-nostdinc -O2 -m486 -pipe" make DESTDIR=/usr/obj/usr/src/tmp -f Makefile.inc1 libraries make: not found *** Error code 127 1 error *** Error code 2 1 error ========= log ends here ========= > I assume make(1) has been built, because that's the first constructive > thing that happens. Can you check that it has been installed? -------- motoyuki@sakura[280] % cd /usr/obj/usr/src/tmp/usr/bin motoyuki@sakura[281] % ls -alg make -r-xr-xr-x 1 root wheel 168096 Nov 24 08:20 make -------- If you need more information, please tell me. -- ------------------------------------------------------------------------ Motoyuki Konno mkonno@res.yamanashi-med.ac.jp (Univ) motoyuki@snipe.rim.or.jp (Home) motoyuki@FreeBSD.ORG (FreeBSD Project) Yamanashi Medical University http://www.freebsd.org/~motoyuki/ (WWW) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:47:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-83.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.211]) by hub.freebsd.org (Postfix) with ESMTP id 0A1CC1537B for ; Tue, 23 Nov 1999 15:47:50 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA06589; Tue, 23 Nov 1999 23:47:49 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA01547; Tue, 23 Nov 1999 23:52:49 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911232352.XAA01547@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Poul-Henning Kamp Cc: Dan Nelson , Brian Somers , Forrest Aldrich , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: ps on 4.0-current In-Reply-To: Message from Dan Nelson of "Tue, 23 Nov 1999 17:11:37 CST." <19991123171137.A19161@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Nov 1999 23:52:49 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In the last episode (Nov 23), Brian Somers said: > > $ ps jtva > > USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND > > root 222 1 222 9dac40 0 Is+ va 0:00.01 (getty) > > $ sudo ps jtva > > USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND > > root 222 1 222 9dac40 0 Is+ va 0:00.01 /usr/libexec/getty Pc tt > > $ head -1 /etc/motd > > FreeBSD 4.0-CURRENT (HAK) #9: Mon Nov 22 01:09:55 GMT 1999 > > > > This looks a bit wrong.... > > Now that does look weird. After a bit more investigation, it looks > like you can only get the full commandline of your own processes. Root > can see all commandlines. Any comments Poul ? Is this anything to do with the recent command line buffering ? > -- > Dan Nelson > dnelson@emsphone.com > -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:52:31 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 13FDA14DD0; Tue, 23 Nov 1999 15:52:30 -0800 (PST) Date: Tue, 23 Nov 1999 15:52:30 -0800 From: "Andrey A. Chernov" To: Dan Nelson Cc: Brian Somers , Forrest Aldrich , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: ps on 4.0-current Message-ID: <19991123155229.A29997@freebsd.org> References: <199911232103.VAA02408@hak.lan.Awfulhak.org> <19991123171137.A19161@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19991123171137.A19161@dan.emsphone.com>; from dnelson@emsphone.com on Tue, Nov 23, 1999 at 05:11:37PM -0600 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 23, 1999 at 05:11:37PM -0600, Dan Nelson wrote: > Now that does look weird. After a bit more investigation, it looks > like you can only get the full commandline of your own processes. Root > can see all commandlines. Yes, I can confirm it too on recently rebuilded -current. Looks like access to this info becomes too restrictive. Something bad in the kernel, not in kvm library. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:53:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id A367C1542A for ; Tue, 23 Nov 1999 15:53:41 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id AAA19101 for current@FreeBSD.ORG; Wed, 24 Nov 1999 00:53:26 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 150F08864; Wed, 24 Nov 1999 00:36:29 +0100 (CET) Date: Wed, 24 Nov 1999 00:36:28 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Console driver (Was: Re: FreeBSD security auditing project) Message-ID: <19991124003628.A8876@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <199911231905.VAA80946@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Donn Miller: > While we're on the subject of possibly borrowing code from NetBSD... > NetBSD's wscons looks interesting. Any chance FreeBSD will adopt this, or > will we stay with syscons? What features does it have compared to syscons ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:57: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 287C81542A; Tue, 23 Nov 1999 15:56:55 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id AAA31377; Wed, 24 Nov 1999 00:54:16 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Brian Somers Cc: Dan Nelson , Forrest Aldrich , freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: ps on 4.0-current In-reply-to: Your message of "Tue, 23 Nov 1999 23:52:49 GMT." <199911232352.XAA01547@hak.lan.Awfulhak.org> Date: Wed, 24 Nov 1999 00:54:15 +0100 Message-ID: <31375.943401255@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911232352.XAA01547@hak.lan.Awfulhak.org>, Brian Somers writes: >> In the last episode (Nov 23), Brian Somers said: >> > $ ps jtva >> > USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND >> > root 222 1 222 9dac40 0 Is+ va 0:00.01 (getty) >> > $ sudo ps jtva >> > USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND >> > root 222 1 222 9dac40 0 Is+ va 0:00.01 /usr/libexec/getty Pc tt >> > $ head -1 /etc/motd >> > FreeBSD 4.0-CURRENT (HAK) #9: Mon Nov 22 01:09:55 GMT 1999 >> > >> > This looks a bit wrong.... >> >> Now that does look weird. After a bit more investigation, it looks >> like you can only get the full commandline of your own processes. Root >> can see all commandlines. >Any comments Poul ? Is this anything to do with the recent command >line buffering ? Yes, I changed it to this behaviour at warners asking (I think he had the security-meister hard-hat on at the time). I'm personally leaning towards the opinion that the argv is public property and should be visible, but then again, I can see the point in hiding it in some circumstances. I'll stick a sysctl in there which defaults to the "open" position and people who need to hide it can set it to "close" to do so. Will this satisfy everybody ? Warner ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 15:59:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 3118115458 for ; Tue, 23 Nov 1999 15:59:16 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Nov 1999 23:57:42 +0000 (GMT) Date: Tue, 23 Nov 1999 23:57:42 +0000 From: David Malone To: Brian Somers Cc: Poul-Henning Kamp , Dan Nelson , Forrest Aldrich , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: ps on 4.0-current Message-ID: <19991123235742.A4913@walton.maths.tcd.ie> References: <199911232352.XAA01547@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199911232352.XAA01547@hak.lan.Awfulhak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 23, 1999 at 11:52:49PM +0000, Brian Somers wrote: > Any comments Poul ? Is this anything to do with the recent command > line buffering ? I guess it goes with the "stop ps showing the environment" changes. If you remove one it makes sense to remove the other. David. phk 1999/11/21 11:03:21 PST Log: Introduce the new function p_trespass(struct proc *p1, struct proc *p2) which returns zero or an errno depending on the legality of p1 trespassing on p2. Replace kern_sig.c:CANSIGNAL() with call to p_trespass() and one extra signal related check. Replace procfs.h:CHECKIO() macros with calls to p_trespass(). Only show command lines to process which can trespass on the target process. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 16:10:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 2FCF114D96 for ; Tue, 23 Nov 1999 16:10:14 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40331>; Wed, 24 Nov 1999 11:03:10 +1100 Content-return: prohibited Date: Wed, 24 Nov 1999 11:10:01 +1100 From: Peter Jeremy Subject: Re: FreeBSD security auditing project. In-reply-to: <199911232321.SAA03005@blackhelicopters.org> To: mwlucas@gltg.com Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov24.110310est.40331@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <199911232321.SAA03005@blackhelicopters.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-24 10:21:17 +1100, mwlucas@gltg.com wrote: >a) This is what an unsafe function call looks like Without checking a lot of the call context, it is very difficult to categorically state that a particular function call is safe or not. As an example, consider the following: foo(const char *ibuf, ...) { char buf[MYBUFSIZ]; ... strcpy(buf, ibuf); ... } In general, this call is unsafe because there's no apparent restriction on the size of ibuf, but in the particular program, it may be quite safe because the length of ibuf has been checked previously. In this case, it's probably safer to change the strcpy() to a strlcpy() or similar - the cost (and risk) of making the change is probably less than the cost of checking all the places where foo() is called. Now consider the case where `buf' is also passed as an argument - now you don't immediately know the length of either the source _or_ destination buffers. And the unsafe code may not be a function call at all. It's quite easy to have an off-by-one error when working with arrays. If you want to look at standard library functions used unsafely, I think there's a range you need to consider. At one end you have "virtually impossible to use safely" (ie [v][f]scanf("...%s..."), gets(), system() and popen()). At the other end, you have "fairly easy to use without introducing buffer overflows" (ie fgets(), [v]snprintf(), strlcpy()). The other string functions, [v]sprintf() and [v]sscanf("...%s...") fall somewhere in the middle. Note that the range does not extend to "can't be used unsafely" or even "difficult to use unsafely" (at least in C). >In fact, I'll go further: If someone can point out a reliable resource >on the Net for a) and b), I'll be happy to write up a first draft of >"The FreeBSD Security Audit for Beginners". I'm sure that any number >of programmers out there would be happy to review it for technical >accuracy before putting it into circulation. A good start would be to read the general `secure programming' information on the web and look for things that are being done differently. Aleph One posted a good summary in BUGTRAQ last December as Message-id: <19981217112144.B872@underground.org> Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 16:15:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id C2D6514D96; Tue, 23 Nov 1999 16:15:21 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id TAA51837; Tue, 23 Nov 1999 19:13:40 -0500 (EST) Date: Tue, 23 Nov 1999 19:13:40 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Gerald Abshez Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: <383B0F03.70A84532@manhattanprojects.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Gerald Abshez wrote: > Kris Kennaway wrote: > > > > Let me throw in some ideas.. > > > > I think it would be very useful to have a database which can track > > submitted open/netbsd CVS commits (with the code diff included), > > preferably mapped to the relevant file in the freebsd tree if possible > > according to a path mapping table (i.e. /some/openbsd/path/file.c mapped > > to /equiv/freebsd.path/file.c). > > Here is my 0.02: > > I think it would be useful to identify "unsafe" functions, so that > anyone can participate in the "eyeball" portion of the game. This means > that we need eyeballed, identified as a (potential) problem and fixed, > as well as some other possiblities. There is a lot of code out there, > and it would help if we could involve the non-programmers in the search. > > Comments? > I was thinking about this on the drive home... * We need to break the auditing process into managable work units. * We need to note when a commit affects code that was believed to have previously been secure (so that it may be audited again). * We should indicate what parts of the code have been audited without discouraging others from double-checking if they like. * We would like to be able to identify and integrate security fixes already made by OpenBSD or NetBSD easily. * We would like to flag programs as suspect/insecure when they are the subject of bugtraq reports. Are there additional goals anyone else has in mind? I've got some thoughts on implementing these, but my wife is telling me it is time to go :) I'll share when I get back from the movies :) Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 16:15:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 06E9E154A6 for ; Tue, 23 Nov 1999 16:15:30 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dAO0DQQ83185; Tue, 23 Nov 1999 17:13:26 -0700 (MST) Message-Id: <199911240013.dAO0DQQ83185@orthanc.ab.ca> To: David Malone Cc: Brian Somers , Poul-Henning Kamp , Dan Nelson , Forrest Aldrich , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: ps on 4.0-current In-reply-to: Your message of "Tue, 23 Nov 1999 23:57:42 GMT." <19991123235742.A4913@walton.maths.tcd.ie> Date: Tue, 23 Nov 1999 17:13:25 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "David" == David Malone writes: David> I guess it goes with the "stop ps showing the environment" David> changes. If you remove one it makes sense to remove the David> other. After you verify that this change isn't going to break things that assume they can see the *argv list via ps(1). I.e. lightning bolts that do 'kill -MUMBLE `ps -ax|grep foo`'. Which may not be elegant style, but sometimes is the only workable solution. Where this could be an issue is binaries with multiple names. E.g. if bar is a symlink to foo, and you execute bar, ps (old style) reports: 83158 p0 S 0:00.00 bar (foo) I *suspect* in the new scheme when running non-root, you don't see bar show up. If that's the case, we've broken working code. Now, if instead printing *argv[] follows the -e semantics I posted to the list a couple of days ago, all should be well. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 16:16:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 6897A14E61 for ; Tue, 23 Nov 1999 16:16:38 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id QAA21298; Tue, 23 Nov 1999 16:16:17 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 23 Nov 1999 16:16:17 -0800 Date: Tue, 23 Nov 1999 16:16:17 -0800 (PST) From: Kip Macy X-Sender: kip@luna To: Doug White Cc: current@FreeBSD.ORG Subject: Re: Threads and my new job. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: dwhite@resnet.uoregon.edu,current@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Jason, you are my savior. Go forth and do much to create Truly Kick Ass > Threading. Give me my tools to smite these Linux database servers once > and for all! :-) Why do we need to smite the Linux database servers? With threads in their current state they already outperform Linux's native threads by ~50x for things like sending mail. I would assume that the differences in database performance is similar. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 16:38:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 781F415494 for ; Tue, 23 Nov 1999 16:38:55 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id SAA21216; Tue, 23 Nov 1999 18:37:34 -0600 (CST) (envelope-from dan) Date: Tue, 23 Nov 1999 18:37:34 -0600 From: Dan Nelson To: Lyndon Nerenberg Cc: David Malone , Brian Somers , Poul-Henning Kamp , Forrest Aldrich , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: ps on 4.0-current Message-ID: <19991123183733.A21142@dan.emsphone.com> References: <19991123235742.A4913@walton.maths.tcd.ie> <199911240013.dAO0DQQ83185@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911240013.dAO0DQQ83185@orthanc.ab.ca>; from "Lyndon Nerenberg" on Tue Nov 23 17:13:25 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 23), Lyndon Nerenberg said: > After you verify that this change isn't going to break things that > assume they can see the *argv list via ps(1). I.e. lightning bolts > that do 'kill -MUMBLE `ps -ax|grep foo`'. Which may not be elegant > style, but sometimes is the only workable solution. That won't be affected, because anyone that has kill rights to the process will also see the full processname. Now that I think about it, I can't come up with a case where this is really bad. If you're doing ps'es with intent to kill arbitrary processes (in the name of debugging or whatever), you're probably already root. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 16:45: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 3683B1500D for ; Tue, 23 Nov 1999 16:45:01 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40356>; Wed, 24 Nov 1999 11:36:07 +1100 Content-return: prohibited Date: Wed, 24 Nov 1999 11:37:34 +1100 From: Peter Jeremy Subject: buildworld across signal changes not quite right To: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov24.113607est.40356@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to Marcel's latest Makefile.inc1 changes (1.92), a -current buildworld running on an older -current system now progresses much further - in fact it now completes :-). There are, however still a few problems - as far as I can tell, these are all related to the wrong version of perl being called whilst perl is being built in the ">>> Building everything.." section. I'm not sure how to fix this problem. Unlike our other build tools, perl is not designed to be able to be cross-built: It builds bits of itself and assumes they can be safely executed to build other bits. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 16:45:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id A4946154B8; Tue, 23 Nov 1999 16:45:16 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 24 Nov 1999 00:44:10 +0000 (GMT) To: freebsd-current@freebsd.org Cc: obrien@freebsd.org Subject: Lint broken in -current. X-Request-Do: Date: Wed, 24 Nov 1999 00:44:10 +0000 From: David Malone Message-ID: <199911240044.aa67654@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lint no longer works in -current as cpp seems to have lost the -undef option. The option is still shown in the usage message and the man page, but the code seems to have gone walk about! David. 0:30:gonzo 92% uname -a FreeBSD gonzo.home 4.0-CURRENT FreeBSD 4.0-CURRENT #17: Sat Nov 20 13:35:22 GMT 1999 dwmalone@gonzo.home:/usr/src/sys/compile/GONZO i386 0:30:gonzo 93% cpp --help | fgrep undef -Wundef Warn if an undefined macro is used by #if -Wno-undef Do not warn about testing undefined macros -g Include #define and #undef directives in the output -u or -undef Do not predefine any macros 0:30:gonzo 94% cpp -undef cpp: Invalid option `-undef' 0:30:gonzo 95% cpp -u cpp: Invalid option `-u' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 16:53: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 1DE9315493; Tue, 23 Nov 1999 16:52:57 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id QAA43802; Tue, 23 Nov 1999 16:52:55 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199911240052.QAA43802@gndrsh.dnsmgr.net> Subject: Re: FreeBSD security auditing project. In-Reply-To: <19991123142258.C49964@dragon.nuxi.com> from "David O'Brien" at "Nov 23, 1999 02:22:58 pm" To: obrien@FreeBSD.ORG Date: Tue, 23 Nov 1999 16:52:54 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 2) I propose that diff(1) FreeBSD with {Open|Net}BSD, > > This is not the easiest thing to do (I've tried). Rather one should look > at what changes OpenBSD has done to a piece of code since they imported > it from NetBSD and compare with FreeBSD code to see if the OpenBSD change > is applicable to us. > > {Net,Open}BSD kept a lot of Net/2 [influenced] code (not sure how they > were allowed to do that), It's not so much that they where ``allowed'' to do it, it is more the matter that they where never directly served with legal papers from USL/Novell to cease all use of Net/2. Nor did they ever enter into any agreement, that I am aware of, with respect to Net/2 code with any party other than UCB. Walnut Creek and FreeBSD where sent letters by USL/Novell specifically requesting us to cease all use of Net/2. Out of this a formal and legally binding agreement between Walnut Creek and USL/Novell was reached, further I belive Jordan Hubbard signed a like agreement on behalf of FreeBSD. These agreements basically say that the parties would stop all use of Net/2 based code and replace it with BSD4.4 Lite, which is what was done. There are more details, but those are ``not to be disclosed''. One could make claim that Novell/USL seriously failed to do ``due dilegence'', but they where not protecting a trademark, but instead a copyright and they could, if they still owned the code. come along and slap NetBSD/OpenBSD with a pretty healthy law suite. > while we started fresh with 4.4BSD. Thus diffs > between us and them in userland utils and be quite different. > Technically if I where to bring a NetBSD repository over to my box and then let anyone other than myself even look at it I would be in violation of the USL/Novell agreement due to the fact that the repository contains Net/2 code. :-(. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 17: 3: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id D7F6315485 for ; Tue, 23 Nov 1999 17:03:05 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA03767; Tue, 23 Nov 1999 17:01:57 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Brad Knowles Cc: "Jordan K. Hubbard" , Mark Murray , current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-reply-to: Your message of "Tue, 23 Nov 1999 23:20:59 +0100." Date: Tue, 23 Nov 1999 17:01:57 -0800 Message-ID: <3763.943405317@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm certainly willing to do what I can to help, although I have > to admit that I may need a bit of help identifying what I can do. ;-) That's Mark's job - he's the security leader. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 17: 3:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id D9F04154CC; Tue, 23 Nov 1999 17:03:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA03781; Tue, 23 Nov 1999 17:02:59 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@FreeBSD.ORG Cc: Kris Kennaway , peter.jeremy@alcatel.com.au, current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-reply-to: Your message of "Tue, 23 Nov 1999 14:26:26 PST." <19991123142626.D49964@dragon.nuxi.com> Date: Tue, 23 Nov 1999 17:02:59 -0800 Message-ID: <3778.943405379@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This means nothing out of context. I hope we don't go on a witch hunt. No, but there is some merit to simply replacing these so that they don't show up on our radar later. I don't see any reason, for example, why anyone should still be using gets() and our implementation even gets whiney about it if you do. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 17:20: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mentat.solfire.com (rdewalt.pr.dsl.patriot.net [209.249.182.21]) by hub.freebsd.org (Postfix) with ESMTP id 600BB15357 for ; Tue, 23 Nov 1999 17:20:05 -0800 (PST) (envelope-from tet@mentat.solfire.com) Received: from localhost (tet@localhost) by mentat.solfire.com (8.9.3/8.9.3) with ESMTP id UAA18195 for ; Mon, 22 Nov 1999 20:09:09 -0500 (EST) (envelope-from tet@mentat.solfire.com) Date: Mon, 22 Nov 1999 20:09:08 -0500 (EST) From: Tet Solfire To: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Kris Kennaway wrote: > On Tue, 23 Nov 1999, Kelly Yancey wrote: > > Need volunteers, eh? I can be suckered in to helping in regards to > > building the web-based database for keeping track of the effor's progress. > > I may be no security expert, but I can build database-driven web sites (I > > should...it's my day job ;) ). > > Let me know what I can do to help. > > Cool, we have a database guy! :) Count me in as well if needed, I'm in the same boat about database-driven web sites as my day job. And on another comment a few messages later, I'm more than willing to eyeball code if examples of what to look for are given. I haven't done any C programming (other than minor tweaks here and there) in quite some time, but it's like riding a bicycle. -Ryan Dewalt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 17:40:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 9652515020 for ; Tue, 23 Nov 1999 17:40:40 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40336>; Wed, 24 Nov 1999 12:33:43 +1100 Content-return: prohibited Date: Wed, 24 Nov 1999 12:40:33 +1100 From: Peter Jeremy Subject: Re: FreeBSD security auditing project. In-reply-to: <3778.943405379@localhost> To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov24.123343est.40336@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <19991123142626.D49964@dragon.nuxi.com> <3778.943405379@localhost> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-24 12:02:59 +1100, Jordan K. Hubbard wrote: > I don't see any reason, for >example, why anyone should still be using gets() To take gets() as an example, of the 110 occurrences that gid found in -current, the following files contain actual calls to gets() (rather than declarations, comments, defines etc): contrib/binutils/gas/hash.c - only if compiled -DTEST contrib/cvs/lib/getdate.y - only if compiled -DTEST contrib/gperf/tests/test.c - part of gperf test suite contrib/libreadline/tilde.c - only if compiled -DTEST contrib/texinfo/info/tilde.c - only if compiled -DTEST gnu/lib/libregex/test/fileregex.c - part of libregex test suite gnu/lib/libregex/test/iregex.c - part of libregex test suite gnu/usr.bin/as/config/tc-m68k.c - only if compiled -DTEST1 gnu/usr.bin/as/config/tc-vax.c - only if compiled -Dtest or -DTEST gnu/usr.bin/tar/getdate.y - only if compiled -DTEST sys/boot/pc98/boot2/boot.c - asking for boot device sys/i386/boot/biosboot/boot.c - asking for boot device sys/i386/boot/cdboot/boot.c - asking for boot device sys/kern/vfs_conf.c - prompting user for root filesystem sys/pc98/boot/biosboot/boot.c - asking for boot device So the only live code that contains gets() is in the boot loader (where space is a serious problem) and when reading a user-specified root filesystem name in the kernel. In either case, it's not clear that exploiting the resultant buffer overflow would allow someone to gain additional privileges (beyond those they already have as a result of being able to type input into gets()). I would prefer to see the gets() in vfs_conf.c go away - the actual gets() definition is right below the (sole) call to gets() and could easily be changed to bounds check its input. The boot code is less obvious. Adding input bounds checking could make the difference to the code fitting or not fitting. This is probably an area where compliance to Standard C Library interfaces is less important than code size. > and our implementation even gets whiney about it if you do. I like this and have previously suggested that it could probably be usefully extended to other functions. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 18: 6:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from pike.cdrom.com (pike.cdrom.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 2D7C514E81 for ; Tue, 23 Nov 1999 18:06:13 -0800 (PST) (envelope-from cshumway@cdrom.com) Received: from localhost (cshumway@localhost) by pike.cdrom.com (8.9.1a/8.9.1) with ESMTP id SAA09634 for ; Tue, 23 Nov 1999 18:08:31 -0800 (PST) Date: Tue, 23 Nov 1999 18:08:31 -0800 (PST) From: Christopher Shumway To: current@freebsd.org Subject: Make buildworld blowing up Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to build a CURRENT system from the 4.0 CURRENT snapshot cdroms on 7-5-1999. I did a cvsup to cvsup4.freebsd.org, and attempted to build world. It keeps on blowing up as illustrated below. I nuked the /usr/src directory and then checked the source tree from our local mirror of the master CVS repository, but it too dies. Even after a ``make clean''. Anyone have any ideas whats going on here? ===> cc_tools gperf -p -j1 -i 1 -g -o -t -G -N is_reserved_word -k1,3,$ /usr/src/gnu/usr.bin/ cc/cc_tools/../../../../contrib/gcc/c-parse.gperf > c-gperf.h /* starting time is 13:42:44 */ /* ending time is 13:42:44 */ gperf -p -j1 -g -o -t -N is_reserved_word '-k1,4,7,$' /usr/src/gnu/usr.bin/cc/c c_tools/../../../../contrib/gcc/cp/gxx.gperf >gxx-hash.h /* starting time is 13:42:44 */ /* ending time is 13:42:44 */ ln -sf gxx-hash.h hash.h echo '#include "cp/cp-tree.def"' > gencheck.h echo '#include "objc/objc-tree.def"' >> gencheck.h sed -e "/^ifobjc$/,/^end ifobjc$/d" -e "/^ifc$/d" -e "/^end ifc$/d" /usr/src/g nu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.in > c-parse.y yacc -d -o c-parse.c c-parse.y yacc: e - line 30 of "c-parse.y", syntax error %expect 51 ^ *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 18:27:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 5EE3415487 for ; Tue, 23 Nov 1999 18:27:28 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id SAA25379 for ; Tue, 23 Nov 1999 18:27:27 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id SAA77120 for current@FreeBSD.ORG; Tue, 23 Nov 1999 18:27:05 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199911240227.SAA77120@whistle.com> Subject: Re: buildworld across signal changes not quite right In-Reply-To: <99Nov24.113607est.40356@border.alcanet.com.au> from Peter Jeremy at "Nov 24, 99 11:37:34 am" To: current@FreeBSD.ORG Date: Tue, 23 Nov 1999 18:27:04 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL29 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy writes: | Thanks to Marcel's latest Makefile.inc1 changes (1.92), a -current | buildworld running on an older -current system now progresses much | further - in fact it now completes :-). | | There are, however still a few problems - as far as I can tell, these | are all related to the wrong version of perl being called whilst perl | is being built in the ">>> Building everything.." section. | | I'm not sure how to fix this problem. Unlike our other build tools, | perl is not designed to be able to be cross-built: It builds bits | of itself and assumes they can be safely executed to build other bits. Yes this is very tricky. I run into a lesser issue when switching from threaded perl to unthread perl. This is currently broken since it doesn't link with the just built libs. This is further complicated in that other things sometimes need to find out how perl was built by asking perl. An example is vi with perl support which is also broken under threads. I can't see an obvious around this except to build a "build tools" version for use during the build and then a final version. An issue with this would be how to generate the config.h for the build platform since we currently have those pre-made for our target platforms. This doesn't address the issue of perl needing to report how it was built. I have sent in fixes for the 2 threaded perl issues. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 19: 0:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 97139150BF for ; Tue, 23 Nov 1999 19:00:45 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA55815; Tue, 23 Nov 1999 19:00:44 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA50954; Tue, 23 Nov 1999 19:00:44 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Nov 1999 19:00:44 -0800 From: "David O'Brien" To: David Malone Cc: freebsd-current@freebsd.org Subject: Re: Lint broken in -current. Message-ID: <19991123190044.C49362@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <199911240044.aa67654@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911240044.aa67654@salmon.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Wed, Nov 24, 1999 at 12:44:10AM +0000 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Lint no longer works in -current as cpp seems to have lost the -undef > option. Yes, looking into `cpp' is on my list of things to do. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 19: 6:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id CC0721542E for ; Tue, 23 Nov 1999 19:06:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA55844 for ; Tue, 23 Nov 1999 19:06:14 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA50989 for current@FreeBSD.ORG; Tue, 23 Nov 1999 19:06:14 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Nov 1999 19:06:14 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. Message-ID: <19991123190614.E49362@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19991123142626.D49964@dragon.nuxi.com> <3778.943405379@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3778.943405379@localhost>; from jkh@zippy.cdrom.com on Tue, Nov 23, 1999 at 05:02:59PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't see any reason, for example, why anyone should still be using > gets() and our implementation even gets whiney about it if you do. That one is definitely up for a global search and replace as its only use is to read external data. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 19:16:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 9BDD415188; Tue, 23 Nov 1999 19:16:12 -0800 (PST) (envelope-from forrie@forrie.com) Received: from Forrest (getbent@forrie.ne.mediaone.net [24.128.72.15]) by forrie.net (8.9.3/8.9.3) with ESMTP id WAA04353; Tue, 23 Nov 1999 22:14:46 -0500 (EST) Message-Id: <4.2.2.19991123220915.00ab0c00@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 23 Nov 1999 22:10:44 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Re: ps on 4.0-current Cc: security@FreeBSD.ORG In-Reply-To: <31375.943401255@critter.freebsd.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to recall that conversation here in the mailing list. How about a system configuration variable that determines what info like ps (and friends) can access? Personally, I would just prefer to leave it be. There are too many other potential problems with scripts and such that depend upon the info PS provides. *shrug* :) _F At 12:54 AM 11/24/99 +0100, Poul-Henning Kamp wrote: >In message <199911232352.XAA01547@hak.lan.Awfulhak.org>, Brian Somers writes: > >> In the last episode (Nov 23), Brian Somers said: > >> > $ ps jtva > >> > USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND > >> > root 222 1 222 9dac40 0 Is+ va 0:00.01 (getty) > >> > $ sudo ps jtva > >> > USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND > >> > root 222 1 222 9dac40 0 Is+ va 0:00.01 > /usr/libexec/getty Pc tt > >> > $ head -1 /etc/motd > >> > FreeBSD 4.0-CURRENT (HAK) #9: Mon Nov 22 01:09:55 GMT 1999 > >> > > >> > This looks a bit wrong.... > >> > >> Now that does look weird. After a bit more investigation, it looks > >> like you can only get the full commandline of your own processes. Root > >> can see all commandlines. > > >Any comments Poul ? Is this anything to do with the recent command > >line buffering ? > >Yes, I changed it to this behaviour at warners asking (I think he had >the security-meister hard-hat on at the time). > >I'm personally leaning towards the opinion that the argv is public >property and should be visible, but then again, I can see the point >in hiding it in some circumstances. > >I'll stick a sysctl in there which defaults to the "open" position >and people who need to hide it can set it to "close" to do so. > >Will this satisfy everybody ? > >Warner ? > >-- >Poul-Henning Kamp FreeBSD coreteam member >phk@FreeBSD.ORG "Real hackers run -current on their laptop." >FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 19:22:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 08CD514E51 for ; Tue, 23 Nov 1999 19:22:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA55885; Tue, 23 Nov 1999 19:21:29 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA51056; Tue, 23 Nov 1999 19:21:28 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Nov 1999 19:21:28 -0800 From: "David O'Brien" To: Christopher Shumway Cc: current@freebsd.org Subject: Re: Make buildworld blowing up Message-ID: <19991123192128.B51014@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cshumway@cdrom.com on Tue, Nov 23, 1999 at 06:08:31PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anyone have any ideas whats going on here? Yep. ;-) > yacc: e - line 30 of "c-parse.y", syntax error > %expect 51 > ^ > *** Error code 1 The problem is rev 1.92 of src/Makefile.inc1. With that change, the tools needed to build GCC aren't made first. I added a few Bison-like features to Byacc that GCC depended on. The non-tradional "%expect" is one of them. If you manually build and install src/usr.bin/yacc/, a `make world' should then work. Acutally, you should also do the same for src/gnu/usr.bin/bison/ as I think you'll hit another problem later in the build. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 19:25: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 44FE214E51 for ; Tue, 23 Nov 1999 19:25:00 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA55899; Tue, 23 Nov 1999 19:24:55 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA51075; Tue, 23 Nov 1999 19:24:55 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Nov 1999 19:24:55 -0800 From: "David O'Brien" To: peter.jeremy@alcatel.com.au Cc: current@FreeBSD.ORG Subject: Re: buildworld across signal changes not quite right Message-ID: <19991123192454.C51014@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <99Nov24.113607est.40356@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <99Nov24.113607est.40356@border.alcanet.com.au>; from jeremyp@gsmx07.alcatel.com.au on Wed, Nov 24, 1999 at 11:37:34AM +1100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks to Marcel's latest Makefile.inc1 changes (1.92), a -current > buildworld running on an older -current system now progresses much > further - in fact it now completes :-). Actually, I've been seeing just the opposite. Before you could build a -CURRENT kernel and then the world. Now those with worlds from this past summer can't build today's world regardless of which of userland or kernel is built first. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 19:28:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 8C0C514E51; Tue, 23 Nov 1999 19:28:34 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id WAA12875; Tue, 23 Nov 1999 22:28:14 -0500 (EST) Message-ID: <19991123222813.A12570@netmonger.net> Date: Tue, 23 Nov 1999 22:28:13 -0500 From: Christopher Masto To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: ps on 4.0-current Mail-Followup-To: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG References: <199911232352.XAA01547@hak.lan.Awfulhak.org> <31375.943401255@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <31375.943401255@critter.freebsd.dk>; from Poul-Henning Kamp on Wed, Nov 24, 1999 at 12:54:15AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 24, 1999 at 12:54:15AM +0100, Poul-Henning Kamp wrote: > I'm personally leaning towards the opinion that the argv is public > property and should be visible, but then again, I can see the point > in hiding it in some circumstances. > > I'll stick a sysctl in there which defaults to the "open" position > and people who need to hide it can set it to "close" to do so. Please. Thank you. Not everyone wears the sysadmin hat with the face shield and gas mask, as much as it may currently be in style. If it can work both ways, even better. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 20:56:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id C157D1538F; Tue, 23 Nov 1999 20:56:24 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id WAA25704; Tue, 23 Nov 1999 22:54:33 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Tue, 23 Nov 1999 22:54:33 -0600 (CST) From: David Scheidt To: "David O'Brien" Cc: peter.jeremy@alcatel.com.au, current@FreeBSD.ORG Subject: Re: buildworld across signal changes not quite right In-Reply-To: <19991123192454.C51014@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, David O'Brien wrote: > > Thanks to Marcel's latest Makefile.inc1 changes (1.92), a -current > > buildworld running on an older -current system now progresses much > > further - in fact it now completes :-). > > Actually, I've been seeing just the opposite. > Before you could build a -CURRENT kernel and then the world. Now those > with worlds from this past summer can't build today's world regardless > of which of userland or kernel is built first. The upgrade from -STABLE is also broken because of this. The %expect stuff is blowing up. I haven't yet tried to see if building yacc and bison manually fixes things or not. I will tomorrow, when I have access to the box, assuming my workload doesn't try to kill me first. (I hadn't reported it, because I haven't had time to investigate properly. ) David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 21: 1:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 0F64E154FE; Tue, 23 Nov 1999 21:01:22 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id AAA56673; Wed, 24 Nov 1999 00:01:02 -0500 (EST) Date: Wed, 24 Nov 1999 00:01:02 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Gerald Abshez Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Kelly Yancey wrote: > > I think it would be useful to identify "unsafe" functions, so that > > anyone can participate in the "eyeball" portion of the game. This means > > that we need eyeballed, identified as a (potential) problem and fixed, > > as well as some other possiblities. There is a lot of code out there, > > and it would help if we could involve the non-programmers in the search. > > > > Comments? > > > > * We need to break the auditing process into managable work units. Specifically, I think Kris was right on the money in defining the resolution to be at the function, as opposed to file, level. Individual functions can be identified as unsafe, suspect, or as scutinized and believed to be safe. Individuals are welcome to analyze an entire file, but the status should be recorded per-function. This has the added benefit that commits which change only 1 function in a file, can reset just the confidence level of the function effected, rather than the entire file. That should reduce the amount of duplicated effort since functions which have been scrutinized and deemed safe don't require the same level of scrutiny again should some other function in the file change. > > * We need to note when a commit affects code that was believed to have > previously been secure (so that it may be audited again). This is an extension of the previous point. The on-line tool (whatever form it takes) would have to track commits and reset the confidence flag for any functions that changed. It would be ideal to reset a function's confidence rating whenever it has changed, except when the change was to make it more secure. But of course, this is impractical. The compromise would probably have to be just to always reset the rating to "suspect" and let anyone who commits a security-related fix reset the rating themself. > > * We should indicate what parts of the code have been audited without > discouraging others from double-checking if they like. Continuing the previous thought: we could allow people to attach their assessment to function records in the database. So that if one reviewer "eyeballs" the code and believes it to be safe, they can say so, and it is recorded along with the current version of the file the function is in, and the date of the assessment. This gives us 4 rewards: First, that everyone can see which functions have been reviewed. Second, that if commits make a function unsafe, it would be trivial to identify the last safe version of the file and thus the function. Third, it allows multiple people to review the same function, knowing that someone else has already reviewed it. If I eyeball a function and suspect it to be unsafe, I can attach my "suspect" assessment to the function. Someone looking for functions to investigate could query all of the functions whose most recent assessment was "suspect" (or worse, "unsafe", see last point below). Finally, it requires no effort on the part of the cvs-meisters (ie. no messing with CVS tags); all auditing information is stored outside of the CVS repo. > > * We would like to be able to identify and integrate security fixes > already made by OpenBSD or NetBSD easily. The main obstacle I see here is the divergence in the code bases. Specifically, functions have slightly different names in many places, the file hierarchies are organized differently, and god-knows what else. The only way I can figure to begin to automate the process of integrating fixes from other *BSDs would be to build a mapping relationship for functions and files between their source trees and ours. That may well take as much effort as the audit itself :) I think the only reasonable way to get the fixes merged into our source is for hackers to do it by hand. That isn't to say that we couldn't provide a central place for security-conscious hackers to view security-related commits to other BSD's source trees, past and present. I suspect grepping for things like "overflow" in commit logs for the other BSDs would go a long way in separating the wheat from the chaffe. We can help people find out about potential bugs, but I just can't see how the hand-holding could extend any further. > > * We would like to flag programs as suspect/insecure when they are the > subject of bugtraq reports. The big trick here is that bugtraq reports aren't always nice enough to point us to the specific file/function that is causing the bug :). Either someone has to be responsible for manually identifying the offending files and/or functions as "unsafe" or else we have to take the same policy as with merging fixes from the other BSDs and just provide the information for the more intelligent chair-to-keyboard interface to figure out. That aside, I have used 3 confidence levels thoughout this message for indentifying the audit status of files: "unsafe," "suspect," and "safe". These are just examples, and could easily be replaced with more fine-grained terms or even a numberic confidence rating system (say a percentage, for example). In any event, I hope the idea is clear. Now, all this theory stuff is fine and dandy, but what about the code? I'de be glad to starting implementation this upcoming Monday (I'm going to have a couple of weeks where I can spend the majority of the day coding on FreeBSD-stuff). I'm looking forward to feedback, Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 21:15:37 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 79EE31550A; Tue, 23 Nov 1999 21:15:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6AE4F1CD7F5 for ; Tue, 23 Nov 1999 21:15:35 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 23 Nov 1999 21:15:35 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: Overflow in banner(1) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the spirit of the newly-formed FreeBSD Auditing Project, I present: % banner `perl -e 'print "a"x2000'` Segmentation fault(core dumped) ----- The problem is a trivial one. From /usr/src/usr.bin/banner/banner.c: /* * banner - prints large signs * banner [-w#] [-d] [-t] message ... */ #define MAXMSG 1024 ... char message[MAXMSG]; ... /* Have now read in the data. Next get the message to be printed. */ if (*argv) { strcpy(message, *argv); while (*++argv) { strcat(message, " "); strcat(message, *argv); } nchars = strlen(message); } else { ---- Bzzzt! Wrong! OpenBSD were never vulnerable to this because they seem to use a different banner(1) than we do. The issue of whether or not this is likely to be a serious security risk is left as an exercise to the reader :-) I'll commit this tomorrow (just wanted to get in a 'first post!' :-).. Kris Index: banner.c =================================================================== RCS file: /home/ncvs/src/usr.bin/banner/banner.c,v retrieving revision 1.6 diff -u -r1.6 banner.c --- banner.c 1999/04/19 04:05:25 1.6 +++ banner.c 1999/12/23 10:18:50 @@ -1058,15 +1058,15 @@ /* Have now read in the data. Next get the message to be printed. */ if (*argv) { - strcpy(message, *argv); + strncpy(message, *argv, MAXMSG); while (*++argv) { - strcat(message, " "); - strcat(message, *argv); + strlcat(message, " ", MAXMSG); + strlcat(message, *argv, MAXMSG); } nchars = strlen(message); } else { fprintf(stderr,"Message: "); - (void)fgets(message, sizeof(message), stdin); + (void)fgets(message, MAXMSG, stdin); nchars = strlen(message); message[nchars--] = '\0'; /* get rid of newline */ } ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 21:32:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 970D3153FA; Tue, 23 Nov 1999 21:32:36 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40336>; Wed, 24 Nov 1999 16:24:48 +1100 Content-return: prohibited Date: Wed, 24 Nov 1999 16:31:40 +1100 From: Peter Jeremy Subject: Re: FreeBSD security auditing project. In-reply-to: To: Brian Fundakowski Feldman Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov24.162448est.40336@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <99Nov24.075703est.40331@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-24 15:33:14 +1100, Brian Fundakowski Feldman wrote: >I'd like to note something. Strcat isn't necessarily unsafe, and strncat() >isn't necessarily safe. I wasn't implying that. In fact, I believe the semantics of strncat() put it into the `hard to use correctly' category (or maybe `very likely to be misused'). > if (fscanf(file, "%d:foo:%.*s", &smurf, sizeof(something), > something) /* This is safe, of course. */ Beep. You lose. "%.*s" doesn't exist in *scanf() [I thought it did, but it's not mentioned in either scanf(3) or the source]. You have to specify field widths as literals (which makes this sort of code a real PITA). >#define SNPARGS(buf, len) buf + len, sizeof(buf) > len ? sizeof(buf) - len : 0 > char action2[32], proto[47], name[18], fragment[17]; > /* Print command name */ > snprintf(SNPARGS(name, 0), "ipfw: %d", f ? f->fw_number : -1); > >Despite the fact that the buffer name[] was made to be exactly the >largest size, where sprintf() _would_be_safe_, Not necessarily true. Consider a system where sizeof(int)==8 (such C compilers exist today). In this case "%d" can take 20 characters, but the code above code assumes an int can always be printed in 11 characters. > Don't get caught doing this. >If you find a strcat() (for example), see if it's safe. If it is, >then why replace it? Confirming that it is safe (checking all the paths by which the strcat() can be reached) might take substantial effort (if the buffers and/or range checks are widely separated from the strcat() call. In addition, someone might add a new path to the strcat(), or might change a buffer size, without properly checking all the ramifications. I tend towards the approach that unless it's immediately obvious that it's safe, you are better off using strlcat() (or maybe strncat()). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 21:37:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 9575E14F51 for ; Tue, 23 Nov 1999 21:37:47 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id HAA94945 for freebsd-current@FreeBSD.ORG; Wed, 24 Nov 1999 07:36:23 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199911240536.HAA94945@zibbi.mikom.csir.co.za> Subject: Re: make -j13 world broken To: freebsd-current@FreeBSD.ORG (FreeBSD-current) Date: Wed, 24 Nov 1999 07:36:23 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I assume make(1) has been built, because that's the first constructive > thing that happens. Can you check that it has been installed? Yes it has and it looks ok. It almost looks like the path is screwed up. In the meantime I played a bit around and this hack makes it work. Maybe that can help point out what is wrong? It is strange because XMAKE is used to build the dependencies just before the libraries and there it worked ok. ------- Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.92 diff -u -r1.92 Makefile.inc1 --- Makefile.inc1 1999/11/21 20:06:03 1.92 +++ Makefile.inc1 1999/11/23 10:01:04 @@ -204,7 +204,8 @@ # bootstrap make BMAKE= ${BMAKEENV} ${MAKE} DESTDIR=${WORLDTMP} # cross make used for compilation -XMAKE= ${XMAKEENV} ${MAKE} DESTDIR=${WORLDTMP} +XXXMAKE= ${WORLDTMP}/usr/bin/make -m ${.CURDIR}/share/mk -f Makefile.inc1 +XMAKE= ${XMAKEENV} ${XXXMAKE} DESTDIR=${WORLDTMP} # cross make used for final installation IXMAKE= ${XMAKEENV} ${MAKE} -------- John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 21:49:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from manz.moz.com.mx (customer29-49.telmex.net.mx [148.233.29.49]) by hub.freebsd.org (Postfix) with ESMTP id 8012C1550A for ; Tue, 23 Nov 1999 21:49:34 -0800 (PST) (envelope-from jabc@manz.moz.com.mx) Received: from manz.moz.com.mx (customer29-49.telmex.net.mx [148.233.29.49] (may be forged)) by manz.moz.com.mx (8.9.3/8.9.3) with ESMTP id XAA47329 for ; Tue, 23 Nov 1999 23:49:28 -0600 (CST) (envelope-from jabc@manz.moz.com.mx) Message-ID: <383B7C68.8CFA4C7D@manz.moz.com.mx> Date: Tue, 23 Nov 1999 23:49:28 -0600 From: Juan Amado Becerril Castillo Organization: Mexcom.Net X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: lista current Subject: Apahce Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How I can install Apache_1.3.9 with the option EXTRA_CFLAGS=-DBIG_SECURITY_HOLE from ports ? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 21:49:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B4A5B150BF; Tue, 23 Nov 1999 21:49:01 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id AAA41074; Wed, 24 Nov 1999 00:44:12 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Wed, 24 Nov 1999 00:44:11 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: Overflow in banner(1) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd prefer something like this that I've attached. The move over the years has been away from artificial limits... -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' Index: banner.c =================================================================== RCS file: /usr2/ncvs/src/usr.bin/banner/banner.c,v retrieving revision 1.6 diff -u -r1.6 banner.c --- banner.c 1999/04/19 04:05:25 1.6 +++ banner.c 1999/11/24 05:41:35 @@ -1018,7 +1018,7 @@ }; char line[DWIDTH]; -char message[MAXMSG]; +char *message; char print[DWIDTH]; int debug, i, j, linen, max, nchars, pc, term, trace, x, y; int width = DWIDTH; /* -w option: scrunch letters to 80 columns */ @@ -1058,14 +1058,24 @@ /* Have now read in the data. Next get the message to be printed. */ if (*argv) { - strcpy(message, *argv); + message = strdup(*argv); + if (message == NULL) + err(1, "strdup"); while (*++argv) { - strcat(message, " "); - strcat(message, *argv); + char *omessage; + + omessage = message; + asprintf(&message, "%s %s", message, *argv); + if (message == NULL) + err(1, "asprintf"); + free(omessage); } nchars = strlen(message); } else { fprintf(stderr,"Message: "); + message = malloc(MAXMSG); + if (message == NULL) + err(1, "malloc"); (void)fgets(message, sizeof(message), stdin); nchars = strlen(message); message[nchars--] = '\0'; /* get rid of newline */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 21:52: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 01AB114ECD; Tue, 23 Nov 1999 21:51:24 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id XAA40676; Tue, 23 Nov 1999 23:33:14 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Tue, 23 Nov 1999 23:33:14 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: peter.jeremy@alcatel.com.au Cc: Kris Kennaway , current@FreeBSD.org Subject: Re: FreeBSD security auditing project. In-Reply-To: <99Nov24.075703est.40331@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Nov 1999, Peter Jeremy wrote: > A 'grep | wc' equivalent over the source tree gives: > > gets 110 > strcat 2860 > strcpy 4717 > strncat 167 > strncpy 1514 > sprintf 6839 > vsprintf 133 > ... > A string search for (roughly) "scanf.*%s" also picks up 74 cases of > un-bounded string scans. > > And these are the easy ones... I'd like to note something. Strcat isn't necessarily unsafe, and strncat() isn't necessarily safe. It is not possible to just tell people "look for this and replace it with this." For example, with fscanf(): char buf[80], something[80]; #if 1 if (fscanf(file, "%d:foo:%.*s", &smurf, sizeof(something), something) /* This is safe, of course. */ #else if (fscanf(file, "%d:foo:%s", &smurf, something); /* I'm using %s here, but it's safe. Compare * the buffer sizes. */ #endif For a better example, in the real world (from src/sys/netinet/ip_fw.c): #define SNPARGS(buf, len) buf + len, sizeof(buf) > len ? sizeof(buf) - len : 0 char action2[32], proto[47], name[18], fragment[17]; /* Print command name */ snprintf(SNPARGS(name, 0), "ipfw: %d", f ? f->fw_number : -1); Despite the fact that the buffer name[] was made to be exactly the largest size, where sprintf() _would_be_safe_, some people insist on using snprintf() "for stability". Don't get caught doing this. If you find a strcat() (for example), see if it's safe. If it is, then why replace it? > > Peter > > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 21:56: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles532.castles.com [208.214.165.96]) by hub.freebsd.org (Postfix) with ESMTP id 9A1CD14C2C for ; Tue, 23 Nov 1999 21:56:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA00843; Tue, 23 Nov 1999 21:46:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911240546.VAA00843@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dan Nelson Cc: freebsd-current@FreeBSD.ORG Subject: Re: ps on 4.0-current In-reply-to: Your message of "Tue, 23 Nov 1999 18:37:34 CST." <19991123183733.A21142@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Nov 1999 21:46:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In the last episode (Nov 23), Lyndon Nerenberg said: > > After you verify that this change isn't going to break things that > > assume they can see the *argv list via ps(1). I.e. lightning bolts > > that do 'kill -MUMBLE `ps -ax|grep foo`'. Which may not be elegant > > style, but sometimes is the only workable solution. > > That won't be affected, because anyone that has kill rights to the > process will also see the full processname. Now that I think about it, > I can't come up with a case where this is really bad. If you're doing > ps'es with intent to kill arbitrary processes (in the name of debugging > or whatever), you're probably already root. This was discussed close to death before the changes were committed, and the current behaviour (restricted access) has been agreed by general consensus to be the most appropriate. Making this behaviour tunable would be bad; it adds another option increasing complexity, and with the proposed default in most cases an admin tightening up a system would never know about it in the first place, rendering it useless. I'd strongly recommend leaving things they way they are. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 22:24:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 2C6E5152D1 for ; Tue, 23 Nov 1999 22:23:40 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA84293; Wed, 24 Nov 1999 08:22:16 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911240622.IAA84293@gratis.grondar.za> To: peter.jeremy@alcatel.com.au Cc: current@FreeBSD.ORG Subject: Re: buildworld across signal changes not quite right Date: Wed, 24 Nov 1999 08:22:15 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not sure how to fix this problem. Unlike our other build tools, > perl is not designed to be able to be cross-built: It builds bits > of itself and assumes they can be safely executed to build other bits. Perl is hugely fragile; cross-building it is a big PITA. If you have any smart ideas, I'm all ears. (I may have mentioned before that I hate the perl build). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 22:40:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5029614ECD for ; Tue, 23 Nov 1999 22:40:29 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id WAA56498; Tue, 23 Nov 1999 22:39:36 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id WAA51957; Tue, 23 Nov 1999 22:39:36 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Nov 1999 22:39:36 -0800 From: "David O'Brien" To: Juan Amado Becerril Castillo Cc: lista current Subject: Re: Apahce Message-ID: <19991123223936.A51939@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <383B7C68.8CFA4C7D@manz.moz.com.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <383B7C68.8CFA4C7D@manz.moz.com.mx>; from jabc@manz.moz.com.mx on Tue, Nov 23, 1999 at 11:49:28PM -0600 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 23, 1999 at 11:49:28PM -0600, Juan Amado Becerril Castillo wrote: > How I can install Apache_1.3.9 with the option > EXTRA_CFLAGS=-DBIG_SECURITY_HOLE from ports ? By asking this question of ports@freebsd.org rather than here. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 22:41:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C875C153B4 for ; Tue, 23 Nov 1999 22:41:32 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id BAA50976; Wed, 24 Nov 1999 01:41:08 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Wed, 24 Nov 1999 01:41:07 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Peter Jeremy Cc: current@FreeBSD.org Subject: Re: FreeBSD security auditing project. In-Reply-To: <99Nov24.162448est.40336@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Nov 1999, Peter Jeremy wrote: > On 1999-Nov-24 15:33:14 +1100, Brian Fundakowski Feldman wrote: > >I'd like to note something. Strcat isn't necessarily unsafe, and strncat() > >isn't necessarily safe. > > I wasn't implying that. In fact, I believe the semantics of strncat() > put it into the `hard to use correctly' category (or maybe `very likely > to be misused'). It seemed like you were pointing out that these were inherently mistakes. > > > if (fscanf(file, "%d:foo:%.*s", &smurf, sizeof(something), > > something) /* This is safe, of course. */ > Beep. You lose. "%.*s" doesn't exist in *scanf() [I thought it did, > but it's not mentioned in either scanf(3) or the source]. You have > to specify field widths as literals (which makes this sort of code > a real PITA). Ah, well, I've never actually tried it. I've used non-'*' lengths; the example still holds as long as you use fscanf() correctly and specify the size as a number inside the fmt (which I didn't, of course :) > > >#define SNPARGS(buf, len) buf + len, sizeof(buf) > len ? sizeof(buf) - len : 0 > > char action2[32], proto[47], name[18], fragment[17]; > > /* Print command name */ > > snprintf(SNPARGS(name, 0), "ipfw: %d", f ? f->fw_number : -1); > > > >Despite the fact that the buffer name[] was made to be exactly the > >largest size, where sprintf() _would_be_safe_, > > Not necessarily true. Consider a system where sizeof(int)==8 (such C > compilers exist today). In this case "%d" can take 20 characters, but > the code above code assumes an int can always be printed in 11 > characters. Our code doesn't run an a system _anything_ like that. In fact, I can't even think of compilers with 8 * NBBY ints. GCC is one of those that can be coerced into long being a software, 64-bit type. > > > Don't get caught doing this. > >If you find a strcat() (for example), see if it's safe. If it is, > >then why replace it? > > Confirming that it is safe (checking all the paths by which the > strcat() can be reached) might take substantial effort (if the buffers > and/or range checks are widely separated from the strcat() call. > > In addition, someone might add a new path to the strcat(), or might > change a buffer size, without properly checking all the ramifications. > > I tend towards the approach that unless it's immediately obvious that > it's safe, you are better off using strlcat() (or maybe strncat()). You shouldn't be using static buffers in the first place, so str*cat() should never be used. > > Peter > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 22:45:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id ABB1214ECD; Tue, 23 Nov 1999 22:45:49 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id WAA56516; Tue, 23 Nov 1999 22:44:25 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id WAA51974; Tue, 23 Nov 1999 22:44:25 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Nov 1999 22:44:25 -0800 From: "David O'Brien" To: Kris Kennaway Cc: current@freebsd.org Subject: Re: Overflow in banner(1) Message-ID: <19991123224424.B51939@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Tue, Nov 23, 1999 at 09:15:35PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 23, 1999 at 09:15:35PM -0800, Kris Kennaway wrote: > - (void)fgets(message, sizeof(message), stdin); > + (void)fgets(message, MAXMSG, stdin); There is nothing wrong with the original line here. Please don't change things that are fine just to change them. We don't want to ofuscate the fix. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 22:46:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 57D0214FD8; Tue, 23 Nov 1999 22:46:22 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA04890; Tue, 23 Nov 1999 22:44:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Brian Fundakowski Feldman Cc: peter.jeremy@alcatel.com.au, Kris Kennaway , current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-reply-to: Your message of "Tue, 23 Nov 1999 23:33:14 EST." Date: Tue, 23 Nov 1999 22:44:55 -0800 Message-ID: <4886.943425895@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey guys, can we move this discussion over to security? I don't think it's -current fodder. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 22:51:13 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id C154C14D0D; Tue, 23 Nov 1999 22:51:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B32461CD623; Tue, 23 Nov 1999 22:51:11 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 23 Nov 1999 22:51:11 -0800 (PST) From: Kris Kennaway To: David O'Brien Cc: current@freebsd.org Subject: Re: Overflow in banner(1) In-Reply-To: <19991123224424.B51939@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, David O'Brien wrote: > On Tue, Nov 23, 1999 at 09:15:35PM -0800, Kris Kennaway wrote: > > - (void)fgets(message, sizeof(message), stdin); > > + (void)fgets(message, MAXMSG, stdin); > > There is nothing wrong with the original line here. Please don't change > things that are fine just to change them. We don't want to ofuscate the fix. Obviously not, but I didn't see the point in making it inconsistent. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 22:56:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id B573414CE6; Tue, 23 Nov 1999 22:56:42 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA84775; Wed, 24 Nov 1999 08:55:36 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911240655.IAA84775@gratis.grondar.za> To: "Jordan K. Hubbard" Cc: Brian Fundakowski Feldman , peter.jeremy@alcatel.com.au, Kris Kennaway , current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. Date: Wed, 24 Nov 1999 08:55:36 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hey guys, can we move this discussion over to security? I don't > think it's -current fodder. :) Actually, I'd like to start a whole new list - freebsd-audit - if that is OK with you. I have a conference to attend, but if this is OK I'll set it up in about 9 hours. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 22:57:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 4F16914CE6 for ; Tue, 23 Nov 1999 22:57:39 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 0FDFF1CC7; Wed, 24 Nov 1999 14:57:37 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Dan Nelson Cc: Lyndon Nerenberg , David Malone , Brian Somers , Poul-Henning Kamp , Forrest Aldrich , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: bogus kern_proc.c change (Re: ps on 4.0-current) In-Reply-To: Message from Dan Nelson of "Tue, 23 Nov 1999 18:37:34 CST." <19991123183733.A21142@dan.emsphone.com> Date: Wed, 24 Nov 1999 14:57:37 +0800 From: Peter Wemm Message-Id: <19991124065737.0FDFF1CC7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Nelson wrote: > In the last episode (Nov 23), Lyndon Nerenberg said: > > After you verify that this change isn't going to break things that > > assume they can see the *argv list via ps(1). I.e. lightning bolts > > that do 'kill -MUMBLE `ps -ax|grep foo`'. Which may not be elegant > > style, but sometimes is the only workable solution. > > That won't be affected, because anyone that has kill rights to the > process will also see the full processname. Now that I think about it, > I can't come up with a case where this is really bad. If you're doing > ps'es with intent to kill arbitrary processes (in the name of debugging > or whatever), you're probably already root. It's this bogus change to kern/kern_proc.c. If you back this out it should work as expected. @@ -631,7 +633,7 @@ if (!p) return (0); - if (!PRISON_CHECK(curproc, p)) + if (p_trespass(curproc, p)) return (0); if (req->newptr && curproc != p) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 22:57:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9F1C514DB2; Tue, 23 Nov 1999 22:57:51 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id WAA56553; Tue, 23 Nov 1999 22:57:50 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id WAA52031; Tue, 23 Nov 1999 22:57:50 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Nov 1999 22:57:50 -0800 From: "David O'Brien" To: Kris Kennaway Cc: current@freebsd.org Subject: Re: Overflow in banner(1) Message-ID: <19991123225750.F49362@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19991123224424.B51939@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Tue, Nov 23, 1999 at 10:51:11PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > - (void)fgets(message, sizeof(message), stdin); > > > + (void)fgets(message, MAXMSG, stdin); > > > > There is nothing wrong with the original line here. Please don't change > > things that are fine just to change them. We don't want to ofuscate > > Obviously not, but I didn't see the point in making it inconsistent. You could make the "MAXMSG" you added "sizeof(message)" and been consistent. :) -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23: 3: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 9056915548; Tue, 23 Nov 1999 23:02:53 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 96DAD1C6D; Wed, 24 Nov 1999 15:02:52 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Christopher Masto Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: ps on 4.0-current In-Reply-To: Message from Christopher Masto of "Tue, 23 Nov 1999 22:28:13 EST." <19991123222813.A12570@netmonger.net> Date: Wed, 24 Nov 1999 15:02:52 +0800 From: Peter Wemm Message-Id: <19991124070252.96DAD1C6D@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Masto wrote: > On Wed, Nov 24, 1999 at 12:54:15AM +0100, Poul-Henning Kamp wrote: > > I'm personally leaning towards the opinion that the argv is public > > property and should be visible, but then again, I can see the point > > in hiding it in some circumstances. > > > > I'll stick a sysctl in there which defaults to the "open" position > > and people who need to hide it can set it to "close" to do so. > > Please. Thank you. > > Not everyone wears the sysadmin hat with the face shield and gas mask, > as much as it may currently be in style. If it can work both ways, > even better. Definately! This is NOT AN ACCEPTABLE CHANGE BY DEFAULT! Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:25:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2FEFD14C8E; Tue, 23 Nov 1999 23:25:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA14764; Tue, 23 Nov 1999 23:23:20 -0800 (PST) (envelope-from dillon) Date: Tue, 23 Nov 1999 23:23:20 -0800 (PST) From: Matthew Dillon Message-Id: <199911240723.XAA14764@apollo.backplane.com> To: Peter Wemm Cc: Christopher Masto , Poul-Henning Kamp , freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: ps on 4.0-current References: <19991124070252.96DAD1C6D@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> > and people who need to hide it can set it to "close" to do so. :> :> Please. Thank you. :> :> Not everyone wears the sysadmin hat with the face shield and gas mask, :> as much as it may currently be in style. If it can work both ways, :> even better. : :Definately! This is NOT AN ACCEPTABLE CHANGE BY DEFAULT! : :Cheers, :-Peter I'm trying to figure out how what started as a fix to a panic turned into such a big mess. And I don't even think the panic has even been fixed --- it's just been made more obscure. There is a big difference between -e, which very few people use and which is an obvious security risk simply because people do not realize it is available, and displaying argv from a user-run ps which everyone is used to doing. When I first suggested removing -e I did so both for security reasons and because it would have been trivial to do. What we have at the moment is something entirely different. I would be for removing -e, but I would be adamantly opposed to restricting the display of command line arguments - not even with an opt-in sysctl. It's just added baggage. And I don't see much point in trying to make ps and top run faster. They are plenty fast enough already (well, maybe not top, but that's for other reasons unrelated to the display of command line arguments). ps *already* delves (or delved) into kvm to retrieve command line arguments only for processes not swapped out, meaning that running ps never causes processes or data to be swapped in unless you specify the 'f' option. In otherwords, nothing ps does blocks. I can't imagine how changing the way arguments are fetched by encumbering procfs with even more junk would generate a sufficient boost in performance to be either noticeable visually or worth doing at all. It would be nice if the procfs panics were fixed, but not at the cost of all of this. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:31:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7C7DA14F77 for ; Tue, 23 Nov 1999 23:31:46 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA11936; Wed, 24 Nov 1999 00:29:33 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA18709; Wed, 24 Nov 1999 00:29:52 -0700 (MST) Message-Id: <199911240729.AAA18709@harmony.village.org> To: Mark Murray Cc: current@freebsd.org Subject: Re: FreeBSD security auditing project. In-reply-to: Your message of "Tue, 23 Nov 1999 21:05:25 +0200." <199911231905.VAA80949@gratis.grondar.za> References: <199911231905.VAA80949@gratis.grondar.za> Date: Wed, 24 Nov 1999 00:29:52 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911231905.VAA80949@gratis.grondar.za> Mark Murray writes: : o unsafe use of the str*(3) functions; strcat/strcpy/sprintf &c. Keep a keen eye out for unsafe uses of strncpy and strncat and know the man page by heart before thinking you are correct :-) : o &c. please contribute here.... I had a long list this afternoon and my link flaked out. Make sure that you look for unusual buffer overflows. This one requires that you think. Grepping for strcpy is one thing, but looking at all the memcpy, memmove, bcopy in the source tree is needed. Look for moving NULL terminated lists w/o moving the NULL. Look for opportunities to overflow things like the atexit run queue, etc. Look for buffer overflows that are caused by sloppy programming. while (*src++ = *dst); [SIC] is but one buggy example :-) Look for cases where the safer interfaces are used improperly. Eg, char foo[5]; ... snprintf(foo, 10, ...). Look for off by one errors in passing lengths to kernel routines. Make sure that you know if that routine will NUL terminate for you or not. Look for DoS things. These include infinite loops on bad data, core dumping (although not all core dumps can be turned into an attack, just some of them). Look for dangerous signal handling. Look for bugs. Don't overlook something because it has a bug that isn't security related. Fix it, or file a PR. Many of the early OpenBSD bug fixes were later turned into attacks. Look at all setuid programs to make sure the need to be setuid. Ditto setgid. Dump is a good example of a program that is setgid that doesn't need to be since it can fork write to do what it is doing internally. Look for places in the kernel that don't do range checking properly. These will turn into panics. Memory leaks can also be leveraged into a DoS, so look for them as well. Take a long hard look at the startup sequence of FreeBSD. Consider that most of the important files on the system are imutable, but make sure that all of them can be made imutable to secure the system. Right now there are many holes. OpenBSD closed the window by raising security level early. Might not be a bad idea to look into what they have done. Be paranoid. If you don't think the whole world is out to get you and a giant conspirancy, then watch more X-Files until you do :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:32:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CF41B150B6; Tue, 23 Nov 1999 23:32:18 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA11952; Wed, 24 Nov 1999 00:32:14 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA18743; Wed, 24 Nov 1999 00:32:33 -0700 (MST) Message-Id: <199911240732.AAA18743@harmony.village.org> To: Kris Kennaway Subject: Re: FreeBSD security auditing project. Cc: Kelly Yancey , Mark Murray , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 23 Nov 1999 12:57:38 PST." References: Date: Wed, 24 Nov 1999 00:32:33 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : : Maybe what we actually want is a better RCS system for FreeBSD. : http://www.perforce.com/ :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:35:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 51D3614C8E; Tue, 23 Nov 1999 23:35:42 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA11966; Wed, 24 Nov 1999 00:34:34 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA18770; Wed, 24 Nov 1999 00:34:53 -0700 (MST) Message-Id: <199911240734.AAA18770@harmony.village.org> To: Kris Kennaway Subject: Re: FreeBSD security auditing project. Cc: Gerald Abshez , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 23 Nov 1999 14:08:31 PST." References: Date: Wed, 24 Nov 1999 00:34:53 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : Yep, this is part of the "education" component: "this is what an unsafe : function call looks like, and this is how to fix it". There's bound to be : enough useful documentation out there which we can collect and point to. __warn_references(tempnam, "warning: tempnam() possibly used unsafely; consider using mkstemp()"); We can increase the number of functions that have this tag (maybe optionally to aid in the search). However, tagging strcpy may produce too loud a cacophony to be useful. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:40:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A0B9814C8E; Tue, 23 Nov 1999 23:40:44 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA11995; Wed, 24 Nov 1999 00:39:51 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA18824; Wed, 24 Nov 1999 00:40:10 -0700 (MST) Message-Id: <199911240740.AAA18824@harmony.village.org> To: peter.jeremy@alcatel.com.au Subject: Re: FreeBSD security auditing project. Cc: "David O'Brien" , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 Nov 1999 10:19:37 +1100." <99Nov24.101250est.40341@border.alcanet.com.au> References: <99Nov24.101250est.40341@border.alcanet.com.au> <99Nov24.075703est.40331@border.alcanet.com.au> <19991123142626.D49964@dragon.nuxi.com> Date: Wed, 24 Nov 1999 00:40:10 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <99Nov24.101250est.40341@border.alcanet.com.au> Peter Jeremy writes: : I suspect that a 'cvs diff' of the OpenBSD code tree is the best : starting point. As a veteran of that war, I think you underestimate that task be about a few orders of magnitude. A better starting point I've found to be the ChangeLog files in the CVSROOT directory of the openbsd tree. After a while, you get a good nose for reading them to know what is important and what isn't. Once you hit a program that has had one fix, it is most productive, I've found, to integrate all the security and bug fixes things you can find in that program, and then reaudit the hell of out of it in case you introduce something bogus. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:42: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1589B15004; Tue, 23 Nov 1999 23:42:03 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA12006; Wed, 24 Nov 1999 00:41:59 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA18844; Wed, 24 Nov 1999 00:42:18 -0700 (MST) Message-Id: <199911240742.AAA18844@harmony.village.org> To: peter.jeremy@alcatel.com.au Subject: Re: FreeBSD security auditing project. Cc: Brian Fundakowski Feldman , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 Nov 1999 16:31:40 +1100." <99Nov24.162448est.40336@border.alcanet.com.au> References: <99Nov24.162448est.40336@border.alcanet.com.au> <99Nov24.075703est.40331@border.alcanet.com.au> Date: Wed, 24 Nov 1999 00:42:18 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <99Nov24.162448est.40336@border.alcanet.com.au> Peter Jeremy writes: : I wasn't implying that. In fact, I believe the semantics of strncat() : put it into the `hard to use correctly' category (or maybe `very likely : to be misused'). I'd put strncat in the definitely unsafe category based on the number of bugs that I've fixed with it over the years. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:47:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3FEB514EFC; Tue, 23 Nov 1999 23:47:43 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA12017; Wed, 24 Nov 1999 00:45:13 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA18867; Wed, 24 Nov 1999 00:45:33 -0700 (MST) Message-Id: <199911240745.AAA18867@harmony.village.org> To: Brian Fundakowski Feldman Subject: Re: FreeBSD security auditing project. Cc: peter.jeremy@alcatel.com.au, Kris Kennaway , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 23 Nov 1999 23:33:14 EST." References: Date: Wed, 24 Nov 1999 00:45:33 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Brian Fundakowski Feldman writes: : Despite the fact that the buffer name[] was made to be exactly the : largest size, where sprintf() _would_be_safe_, some people insist : on using snprintf() "for stability". Don't get caught doing this. : If you find a strcat() (for example), see if it's safe. If it is, : then why replace it? No. You missed the point. It is called fail-safe programming. Even though today's use of sprintf is safe, changes to the program can make it unsafe in the future. snprintf remains safe through most, if not all, of those changes. The changes that make sprintf unsafe can be more subtle than the skills of the committer making the change, as the project frequently has novice people making changes. These should be caught, but aren't always. snprintf increases the likelyhood that these people will be able to make safe changes to the code. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:48:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8079F1510E; Tue, 23 Nov 1999 23:48:06 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA12021; Wed, 24 Nov 1999 00:46:42 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA18880; Wed, 24 Nov 1999 00:47:02 -0700 (MST) Message-Id: <199911240747.AAA18880@harmony.village.org> To: obrien@FreeBSD.ORG Subject: Re: Overflow in banner(1) Cc: Kris Kennaway , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 23 Nov 1999 22:44:25 PST." <19991123224424.B51939@dragon.nuxi.com> References: <19991123224424.B51939@dragon.nuxi.com> Date: Wed, 24 Nov 1999 00:47:02 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991123224424.B51939@dragon.nuxi.com> "David O'Brien" writes: : On Tue, Nov 23, 1999 at 09:15:35PM -0800, Kris Kennaway wrote: : > - (void)fgets(message, sizeof(message), stdin); : > + (void)fgets(message, MAXMSG, stdin); : : There is nothing wrong with the original line here. Please don't change : things that are fine just to change them. We don't want to ofuscate the fix. In fact, the original line is safer than the replaced line. It is safer because message's size might change form MAXMSG to MAXBUF or 24. If you hardwire MAXMSG like this, painful experience has shown that you will get burned. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:53: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B6E991501B; Tue, 23 Nov 1999 23:53:01 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA12040; Wed, 24 Nov 1999 00:50:33 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA18917; Wed, 24 Nov 1999 00:50:53 -0700 (MST) Message-Id: <199911240750.AAA18917@harmony.village.org> To: Brian Fundakowski Feldman Subject: Re: Overflow in banner(1) Cc: Kris Kennaway , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 Nov 1999 00:44:11 EST." References: Date: Wed, 24 Nov 1999 00:50:53 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Brian Fundakowski Feldman writes: : I'd prefer something like this that I've attached. The move over the : years has been away from artificial limits... : @@ -1058,14 +1058,24 @@ : : /* Have now read in the data. Next get the message to be printed. */ : if (*argv) { : - strcpy(message, *argv); : + message = strdup(*argv); : + if (message == NULL) : + err(1, "strdup"); : while (*++argv) { : - strcat(message, " "); : - strcat(message, *argv); : + char *omessage; : + : + omessage = message; : + asprintf(&message, "%s %s", message, *argv); : + if (message == NULL) : + err(1, "asprintf"); : + free(omessage); : } : nchars = strlen(message); : } else { : fprintf(stderr,"Message: "); : + message = malloc(MAXMSG); : + if (message == NULL) : + err(1, "malloc"); : (void)fgets(message, sizeof(message), stdin); : nchars = strlen(message); : message[nchars--] = '\0'; /* get rid of newline */ I'd have used the realloc primitive in place of the asprintf primitive here to avoid too many calls to realloc/malloc. Actually, it is clearer and easier to understand if you precompute the length first and malloc enough space. len = argc; (one each space, plus null at end) for (i = 1; i <= argc; i++) len += strlen(argv[i]); message = malloc(len); // original code here, maybe marked with /* XXX SAFE XXX */ // to show that the code was reviewed at least once. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:54: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7A8E515022; Tue, 23 Nov 1999 23:53:57 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA12044; Wed, 24 Nov 1999 00:51:49 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA18930; Wed, 24 Nov 1999 00:52:08 -0700 (MST) Message-Id: <199911240752.AAA18930@harmony.village.org> To: Kris Kennaway Subject: Re: Overflow in banner(1) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 23 Nov 1999 21:15:35 PST." References: Date: Wed, 24 Nov 1999 00:52:08 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : I'll commit this tomorrow (just wanted to get in a 'first post!' :-).. Please don't. Please use a proper fix instead. : /* Have now read in the data. Next get the message to be printed. */ : if (*argv) { : - strcpy(message, *argv); : + strncpy(message, *argv, MAXMSG); : while (*++argv) { : - strcat(message, " "); : - strcat(message, *argv); : + strlcat(message, " ", MAXMSG); : + strlcat(message, *argv, MAXMSG); Can you precompute the length, malloc the buffer and go from there? wouldn't that be better? : } : nchars = strlen(message); : } else { : fprintf(stderr,"Message: "); : - (void)fgets(message, sizeof(message), stdin); : + (void)fgets(message, MAXMSG, stdin); This is bad style. Don't make this change. : nchars = strlen(message); : message[nchars--] = '\0'; /* get rid of newline */ : } Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:54: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 96DDD1501B; Tue, 23 Nov 1999 23:53:35 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id JAA96874; Wed, 24 Nov 1999 09:50:52 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199911240750.JAA96874@zibbi.mikom.csir.co.za> Subject: Re: Overflow in banner(1) In-Reply-To: from Brian Fundakowski Feldman at "Nov 24, 1999 00:44:11 am" To: green@FreeBSD.ORG (Brian Fundakowski Feldman) Date: Wed, 24 Nov 1999 09:50:52 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm, but now that you have changed message to be a pointer, the sizeof(message) at the end of the patch will return the size of a pointer which is 4 and probably not what you want. :-) I think we should be carefull when we make our security fixes so that we don't introduce new bugs, which was also the problem that I had the other day with doscmd. John -- John Hay -- John.Hay@mikom.csir.co.za > I'd prefer something like this that I've attached. The move over the > years has been away from artificial limits... > > -- > Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / > green@FreeBSD.org `------------------------------' > > > Index: banner.c > =================================================================== > RCS file: /usr2/ncvs/src/usr.bin/banner/banner.c,v > retrieving revision 1.6 > diff -u -r1.6 banner.c > --- banner.c 1999/04/19 04:05:25 1.6 > +++ banner.c 1999/11/24 05:41:35 > @@ -1018,7 +1018,7 @@ > }; > > char line[DWIDTH]; > -char message[MAXMSG]; > +char *message; > char print[DWIDTH]; > int debug, i, j, linen, max, nchars, pc, term, trace, x, y; > int width = DWIDTH; /* -w option: scrunch letters to 80 columns */ > @@ -1058,14 +1058,24 @@ > > /* Have now read in the data. Next get the message to be printed. */ > if (*argv) { > - strcpy(message, *argv); > + message = strdup(*argv); > + if (message == NULL) > + err(1, "strdup"); > while (*++argv) { > - strcat(message, " "); > - strcat(message, *argv); > + char *omessage; > + > + omessage = message; > + asprintf(&message, "%s %s", message, *argv); > + if (message == NULL) > + err(1, "asprintf"); > + free(omessage); > } > nchars = strlen(message); > } else { > fprintf(stderr,"Message: "); > + message = malloc(MAXMSG); > + if (message == NULL) > + err(1, "malloc"); > (void)fgets(message, sizeof(message), stdin); > nchars = strlen(message); > message[nchars--] = '\0'; /* get rid of newline */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:54:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 21813150C8 for ; Tue, 23 Nov 1999 23:54:31 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA12057; Wed, 24 Nov 1999 00:54:21 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA18968; Wed, 24 Nov 1999 00:54:40 -0700 (MST) Message-Id: <199911240754.AAA18968@harmony.village.org> To: Forrest Aldrich Subject: Re: ps on 4.0-current Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 23 Nov 1999 13:15:58 EST." <4.2.2.19991123131419.01495360@216.67.12.69> References: <4.2.2.19991123131419.01495360@216.67.12.69> Date: Wed, 24 Nov 1999 00:54:40 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4.2.2.19991123131419.01495360@216.67.12.69> Forrest Aldrich writes: : Why does ps not show the full path on 4.0 as in 3.3? : (for non-root users) Because you have caught things in the middle of a change. There will be a sysctl that will control this behavior shortly. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 23 23:59:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 80B5415029; Tue, 23 Nov 1999 23:59:21 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id JAA96963; Wed, 24 Nov 1999 09:58:51 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199911240758.JAA96963@zibbi.mikom.csir.co.za> Subject: Re: Overflow in banner(1) In-Reply-To: <199911240747.AAA18880@harmony.village.org> from Warner Losh at "Nov 24, 1999 00:47:02 am" To: imp@village.org (Warner Losh) Date: Wed, 24 Nov 1999 09:58:51 +0200 (SAT) Cc: obrien@FreeBSD.ORG, kris@hub.FreeBSD.ORG (Kris Kennaway), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <19991123224424.B51939@dragon.nuxi.com> "David O'Brien" writes: > : On Tue, Nov 23, 1999 at 09:15:35PM -0800, Kris Kennaway wrote: > : > - (void)fgets(message, sizeof(message), stdin); > : > + (void)fgets(message, MAXMSG, stdin); > : > : There is nothing wrong with the original line here. Please don't change > : things that are fine just to change them. We don't want to ofuscate the fix. > > In fact, the original line is safer than the replaced line. It is > safer because message's size might change form MAXMSG to MAXBUF or 24. > If you hardwire MAXMSG like this, painful experience has shown that > you will get burned. Well the original line is plain wrong if Brian's patch is being used, because there message is a pointer and the size of a pointer is 4. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 0: 3:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 64A76150BE; Wed, 24 Nov 1999 00:03:44 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA12114; Wed, 24 Nov 1999 01:01:13 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA19058; Wed, 24 Nov 1999 01:01:33 -0700 (MST) Message-Id: <199911240801.BAA19058@harmony.village.org> To: Poul-Henning Kamp Subject: Re: ps on 4.0-current Cc: freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 Nov 1999 00:54:15 +0100." <31375.943401255@critter.freebsd.dk> References: <31375.943401255@critter.freebsd.dk> Date: Wed, 24 Nov 1999 01:01:33 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <31375.943401255@critter.freebsd.dk> Poul-Henning Kamp writes: : Warner ? Like I've said in private mail to many different people on this issue, there needs to be a sysctl which controls this, and it needs to be open by default. There are many cases where unwanted information is disclosed inadvertantly by these arguments. It invades the privacy of the users to do so. I don't want anybody to find out that I'm sending mail to joe@greco.com because they can see my ps args, for example, or that my chat script is doing stupid things and putting the password on the command line. or if I'm aiding law enforcement looking for the string "SecreTTWarEzz" to see who is posting them from my machine, I don't want anyone to know what I'm looking for. People generally take care to not include sensitive information on the command line, but sometimes this can't be helped. Not all will agree with this, and it is a change from the past so there needs to be a sysctl to control this. And given that it is a radical change from the past, it needs to default to open. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 0:11:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id F273915115; Wed, 24 Nov 1999 00:11:37 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA33191; Wed, 24 Nov 1999 09:11:20 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: ps on 4.0-current In-reply-to: Your message of "Wed, 24 Nov 1999 01:01:33 MST." <199911240801.BAA19058@harmony.village.org> Date: Wed, 24 Nov 1999 09:11:20 +0100 Message-ID: <33189.943431080@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911240801.BAA19058@harmony.village.org>, Warner Losh writes: >Not all will agree with this, and it is a change from the past so >there needs to be a sysctl to control this. And given that it is a >radical change from the past, it needs to default to open. Now, I can't tell if you wore the security-master hard-hat in this email or not, and I see some quite divergent australian positions, so I will sit tight until I see a little bit more of a consensus. Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 0:16:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id E61F815157; Wed, 24 Nov 1999 00:16:36 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA33219; Wed, 24 Nov 1999 09:15:06 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Peter Wemm , Christopher Masto , freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: ps on 4.0-current In-reply-to: Your message of "Tue, 23 Nov 1999 23:23:20 PST." <199911240723.XAA14764@apollo.backplane.com> Date: Wed, 24 Nov 1999 09:15:06 +0100 Message-ID: <33217.943431306@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911240723.XAA14764@apollo.backplane.com>, Matthew Dillon writes: > I'm trying to figure out how what started as a fix to a panic turned into > such a big mess. And I don't even think the panic has even been fixed --- > it's just been made more obscure. The panic hasn't been fixed, as has been repeatedly stated, but at least a SMP machine doesn't panic when you run the 3rd command they teach you in any "UNIX for dummies" book. > In otherwords, nothing ps does blocks. I can't imagine how changing > the way arguments are fetched by encumbering procfs with even more > junk would generate a sufficient boost in performance to be either > noticeable visually or worth doing at all. Matt, lets talk about this when you have examined the code in some detail. > It would be nice if the procfs panics were fixed, but not at the cost > of all of this. The procfs panics are not fixed, I know that Allan Cox has looked at it. Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 0:40:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 6EF6114D3F; Wed, 24 Nov 1999 00:40:04 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA31171; Wed, 24 Nov 1999 08:43:21 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 24 Nov 1999 08:43:21 +0000 (GMT) From: Doug Rabson To: "David O'Brien" Cc: Mark Murray , Kris Kennaway , current@freebsd.org Subject: Re: FreeBSD security auditing project. In-Reply-To: <19991123140303.B49964@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, David O'Brien wrote: > > So when Joe Blow clicks on (say) src->bin->cat he'll find that > > (say) markm eyballed the code and kris diffed it with OpenBSD > > and merged in fixes - "cat now considered safe". > > Until the next commit to cat. > > A security review is never done. We need to be in a mode where every > commit is suspect and people are compelled to review it. BDE's use of > CTM to review changes is actually rather affective in this reguard. We need to put audit tags into the source tree when a file is audited. That allows the diffs to be audited later which should be a smaller job and then the audit tag slides forward. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 1: 5:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 97AA514D3F; Wed, 24 Nov 1999 01:05:28 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 9689C1C6D; Wed, 24 Nov 1999 17:05:23 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: ps on 4.0-current In-Reply-To: Message from Warner Losh of "Wed, 24 Nov 1999 01:01:33 MST." <199911240801.BAA19058@harmony.village.org> Date: Wed, 24 Nov 1999 17:05:23 +0800 From: Peter Wemm Message-Id: <19991124090523.9689C1C6D@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <31375.943401255@critter.freebsd.dk> Poul-Henning Kamp writes: > : Warner ? [.. reasons for and against ..] > Not all will agree with this, and it is a change from the past so > there needs to be a sysctl to control this. And given that it is a > radical change from the past, it needs to default to open. > > Warner Without wanting to get "please send patches" (I fear sysinstall as much as anyone), I think it would be really nice to create a place where we can set a default 'security profile' or something which arranges for these sorts of things to be set according to the role of the machine. For example, in "workstation" mode, the reasonable default is "open", because typically there is one user on the box (other than root) and that person has root access. Excessive hiding info from that user just means that they'll have to use root more, or will give up the idea of using a mortal user entirely and run everything as root (a Really Bad idea, think of Windoze and viruses etc etc). In a dedicated server role, again it might be appropriate to default it to "open" (dedicated server being something like a squid box), again there will be a couple of sysadmin type users or people who have to monitor things. Hiding information gains nothing there either. In other roles, including something like a shell server box with presumably hostile users (you reasonably have to assume this), you want everything you possibly can to be locked down. Oh for ACL's, privilige attributes, etc. It would solve this sort of thing nicely so that you could allow admin users to see what's going on (including a ps -ax and see what the users are running) without having to constantly (ab)use root and the dangers of overusing that. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 1:10:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id D6DB114FDC; Wed, 24 Nov 1999 01:10:42 -0800 (PST) (envelope-from scanner@jurai.net) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id EAA28238; Wed, 24 Nov 1999 04:10:08 -0500 (EST) Date: Wed, 24 Nov 1999 04:10:08 -0500 (EST) From: To: Doug Rabson Cc: "David O'Brien" , Mark Murray , Kris Kennaway , current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Nov 1999, Doug Rabson wrote: > We need to put audit tags into the source tree when a file is audited. > That allows the diffs to be audited later which should be a smaller job > and then the audit tag slides forward. Not to interrupt in the middle of this discussion but you might want to check with robert watson before you guys get too deep here since he is working on a FUNDED Posix.1e implementation for FreeBSD. And has already posted some EARLY MAC code. It might be usefull to work with him as well. Just a thought. Chris -- "I've always been mad, I know I've been mad, like most of us have. And you have to explain why you were mad, even if you're not mad." -PF DsoTM ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.3 is available now! | Yahoo Messenger ID: opsys_98 -----------------------------------| 1402 N. Washington, Wellington, KS 67152 FreeBSD: The power to serve! | E-Mail: scanner@jurai.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 1:34:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id 419CD14E60 for ; Wed, 24 Nov 1999 01:32:27 -0800 (PST) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.8.8/8.8.8) with UUCP id LAA29110; Wed, 24 Nov 1999 11:28:15 +0300 (MSK) (envelope-from phantom@scorpion.crimea.ua) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id LAA08227; Wed, 24 Nov 1999 11:14:30 +0300 (MSK) Date: Wed, 24 Nov 1999 11:14:30 +0300 (MSK) From: Alexey Zelkin Message-Id: <199911240814.LAA08227@scorpion.crimea.ua> To: mark@grondar.za (Mark Murray) Cc: current@FreeBSD.org Subject: Re: FreeBSD security auditing project. X-Newsgroups: cris.gate.freebsd.current In-Reply-To: <199911231905.VAA80946@gratis.grondar.za> User-Agent: tin/pre-1.4-980618 (UNIX) (FreeBSD/2.2.7-RELEASE (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, MM> I have been charged with the duty of ensuring that FreeBSD gets a MM> security audit that has the credibility of OpenBSD's. What's going on with FreeBSD Auditing Project (http://www.FreeBSD.org/auditors.html) ? Is it still alive ? I think this task is task of this project members. Or will be ;-) MM> I'll get a mailing list going if this is deemed necessary. audit-*@FreeBSD.org ? Or create general list audit@FreeBSD.org ? -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@FreeBSD.org */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 1:38:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id DFA9F14E60; Wed, 24 Nov 1999 01:38:27 -0800 (PST) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id KAA27783; Wed, 24 Nov 1999 10:36:16 +0100 (MET) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id KAA17132; Wed, 24 Nov 1999 10:36:14 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Wed, 24 Nov 1999 10:10:29 +0100 To: Brian Fundakowski Feldman , Peter Jeremy From: Brad Knowles Subject: Re: FreeBSD security auditing project. Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:41 AM -0500 1999/11/24, Brian Fundakowski Feldman wrote: > Our code doesn't run an a system _anything_ like that. That may well be true today, however as FreeBSD gets more widely ported to other platforms, and as the "native" platforms it runs on progress, this might change in the future. I'd suggest erring on the side of paranoia in this case. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 1:40: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1809715001 for ; Wed, 24 Nov 1999 01:39:53 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA33803 for ; Wed, 24 Nov 1999 10:39:44 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: ST-506, ESDI and BAD144 ? From: Poul-Henning Kamp Date: Wed, 24 Nov 1999 10:39:44 +0100 Message-ID: <33801.943436384@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sørens new ATA driver can handle all IDE disks as far as has been tested now, but it doesn't provide bad sector remapping which is needed for ESDI and ST-506 disks. Having two drivers fight for the same class of drivers is a rather messy process, and it complicates the code a fair bit, not to mention the clutter in end-user documentation. Considering that most of the machines with ST-506 and ESDI disks are limited to 16MB ram anyway, I think it would be reasonable to simply tell the users of these old irons to stick with the 3.X branch until end of life (there is probably at least 1.5 years more life in the 3.X branch judging from the history of the 2.2.X branch). So I would like to propose that we discontinue support for ST-506, ESDI disks and BAD144 bad-sector remapping starting with the 4.0 release. So, is anyone running -current on ESDI or ST-506 disks in actual applications (as opposed for the gadget/novelty thrill or testing purposes) ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 1:57: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 9068714E60 for ; Wed, 24 Nov 1999 01:57:03 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id KAA19536 for current@FreeBSD.org; Wed, 24 Nov 1999 10:45:40 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Wed, 24 Nov 1999 10:45:35 +0100 From: Marcel Moolenaar Message-ID: <383BB3BF.72CC24B@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199911240622.IAA84293@gratis.grondar.za> Subject: Re: buildworld across signal changes not quite right Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > > I'm not sure how to fix this problem. Unlike our other build tools, > > perl is not designed to be able to be cross-built: It builds bits > > of itself and assumes they can be safely executed to build other bits. > > Perl is hugely fragile; cross-building it is a big PITA. If you > have any smart ideas, I'm all ears. I haven't paid any special attention to it yet. > (I may have mentioned before that I hate the perl build). No, but it is so noted now :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 1:57: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id EA99F15099 for ; Wed, 24 Nov 1999 01:57:03 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id KAA19790 for current@FreeBSD.org; Wed, 24 Nov 1999 10:46:53 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Wed, 24 Nov 1999 10:46:51 +0100 From: Marcel Moolenaar Message-ID: <383BB40B.5DF059E0@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19991123192454.C51014@dragon.nuxi.com>, Subject: Re: buildworld across signal changes not quite right Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt wrote: > > On Tue, 23 Nov 1999, David O'Brien wrote: > > > > Thanks to Marcel's latest Makefile.inc1 changes (1.92), a -current > > > buildworld running on an older -current system now progresses much > > > further - in fact it now completes :-). > > > > Actually, I've been seeing just the opposite. > > Before you could build a -CURRENT kernel and then the world. Now those > > with worlds from this past summer can't build today's world regardless > > of which of userland or kernel is built first. > > The upgrade from -STABLE is also broken because of this. The %expect stuff > is blowing up. I haven't yet tried to see if building yacc and bison > manually fixes things or not. It will. > I will tomorrow, when I have access to the > box, assuming my workload doesn't try to kill me first. (I hadn't reported > it, because I haven't had time to investigate properly. ) Be prepared to fix gcc and dd too. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 2:30:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 2948C15125; Wed, 24 Nov 1999 02:30:01 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id CAA81013; Wed, 24 Nov 1999 02:29:57 -0800 (PST) Date: Wed, 24 Nov 1999 02:29:57 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Threads and my new job. In-Reply-To: <19991122185220.D301@sturm.canonware.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Firstly there is some threads discussion going on in -arch so I'm going to really reply to this over there.. This is just redirector mail julian On Mon, 22 Nov 1999, Jason Evans wrote: > Walnut Creek has hired me as a full time employee to work primarily on > improving and expanding FreeBSD's threads support. This is very exciting > to me, and I hope my work will be of benefit the FreeBSD community. > [chop] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 2:51:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 7E500150B8; Wed, 24 Nov 1999 02:51:26 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id CAA45328; Wed, 24 Nov 1999 02:50:44 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199911241050.CAA45328@gndrsh.dnsmgr.net> Subject: Re: FreeBSD security auditing project. In-Reply-To: from "Charles M. Hannum" at "Nov 23, 1999 10:23:00 pm" To: root@ihack.net (Charles M. Hannum) Date: Wed, 24 Nov 1999 02:50:44 -0800 (PST) Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > "Rodney W. Grimes" writes: > > > It's not so much that they where ``allowed'' to do it, it is more the > > matter that they where never directly served with legal papers from USL/Novell > > to cease all use of Net/2. Nor did they ever enter into any agreement, > > that I am aware of, with respect to Net/2 code with any party other > > than UCB. > > That's half true. No letter ever received asked us to `cease all use > of Net/2'. However, as has been publically stated *numerous* times, > there does exist an agreement between NetBSD and USL stating that, > after certain Net/2 files were removed and certain others were updated > to their 4.4-Lite versions, USL would not bother us again. That agreement is different than the agreement I have before me. > > > These agreements basically say that the parties would stop all use of > > Net/2 based code and replace it with BSD4.4 Lite, [...] > > That's false. If the FreeBSD agreement is *anything* like the NetBSD > one, it covers only specific files, not the entire source tree. You can't make the claim that this is false, you have not seen the document, and you can't. I will assert my statement is true. I can't say anymore about it than that as the agreement itself says that it's contents are not to be disclosed. The agreement evedently does not look like the one that NetBSD signed. > > > One could make claim that Novell/USL seriously failed to do ``due dilegence'', > > but they where not protecting a trademark, but instead a copyright and they > > could, if they still owned the code. come along and slap NetBSD/OpenBSD > > with a pretty healthy law suite. > > That's also false. Worse, it's FUD. Agreed, given the other statements. > > Technically if I where to bring a NetBSD repository over to my box and > > then let anyone other than myself even look at it I would be in violation > > of the USL/Novell agreement due to the fact that the repository contains > > Net/2 code. :-(. > > And that's false, too. You can't know that, you don't know what my agreement says. Unless I missed it some place the ,v files of the NetBSD repository where not purged of the Net/2 code, unless this was done offline in a non-public manner. That I might not know about. Though the legal agreement between NetBSD and USL/Novell may have only required NetBSD to purge certain files, my agreement is very explicit about ALL of Net/2. > Please check your facts before spewing about legal matters. My facts on the legal points of this issue are probably at least an order of magnitude more correct than yours. NetBSD wouldn't have even seen something as simple as what it did get from USL had I not spent a month of my time working with Novel legal to have something palatible we (WC and myself) could agree to. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 3:57:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 23AE614C98 for ; Wed, 24 Nov 1999 03:57:45 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id RAA09050; Wed, 24 Nov 1999 17:56:57 +0600 (NOVT) (envelope-from nnd) Date: Wed, 24 Nov 1999 17:56:57 +0600 (NOVT) Message-Id: <199911241156.RAA09050@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@FreeBSD.ORG Subject: Buildworld broken in 'usr.bin/kdump' due to ipfilter User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Buildworld of today current is broken due to importing of ip_filter's header files with ioctls which in turn broke building 'usr.bin/kdump'. It seems to me that 'mkioctls' script in 'kdump' is "over-automated" - it build the list of the 'ioctl_includes' 'grepping' through the 'include' directory. But often (as in today's sources) new files with ioctls require manually inserting "prerequisite" includes in the same 'mkioctl' script. May be it'll be better if we manually insert BOTH the includes with ioctls and prerequisite files ? N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 4: 4:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id D1E8515192; Wed, 24 Nov 1999 04:04:45 -0800 (PST) (envelope-from jfh@jfh00.fernuni-hagen.de) Received: (from jfh@localhost) by jfh00.fernuni-hagen.de (8.9.3/8.9.3) id NAA81168; Wed, 24 Nov 1999 13:03:58 +0100 (CET) (envelope-from jfh) To: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Compiling XFree86 under Current From: Fritz Heinrichmeyer Date: 24 Nov 1999 13:03:58 +0100 Message-ID: Lines: 10 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) XEmacs/21.2 (Yoko) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is how i compiled XFree86 today (an additonal file for /usr/ports/x11/XFree86/patches): http://es-i2.fernuni-hagen.de/~jfh/FreeBSD_Documentation/node7.html -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 5:32:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.iol.ie (mail1.mail.iol.ie [194.125.2.192]) by hub.freebsd.org (Postfix) with ESMTP id B912A151EB for ; Wed, 24 Nov 1999 05:32:13 -0800 (PST) (envelope-from nick@iol.ie) Received: from beckett.earlsfort.iol.ie (beckett.earlsfort.iol.ie [194.125.21.2]) by mail.iol.ie Sendmail (v8.9.3) with ESMTP id NAA64779 for ; Wed, 24 Nov 1999 13:31:41 GMT Received: (from nick@localhost) by beckett.earlsfort.iol.ie Sendmail (v8.9.3) id NAA05935 for current@freebsd.org; Wed, 24 Nov 1999 13:31:44 GMT From: Nick Hilliard Message-Id: <199911241331.NAA05935@beckett.earlsfort.iol.ie> Subject: Re: Threads and my new job. To: current@freebsd.org Date: Wed, 24 Nov 1999 13:31:44 +0000 (GMT) X-NCC-RegID: ie.iol X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why do we need to smite the Linux database servers? With threads in their > current state they already outperform Linux's native threads by ~50x for > things like sending mail. I would assume that the differences in database > performance is similar. The threads (& the old nfs issues which have now thankfully been fixed) in their current state led bCandid to write about the Cyclone news router: : Issues the w/FreeBSD kernel and buggy threads have required our development : team to wait until improvements to the OS can be made. We did have a beta : posted on our website for a while but have since removed it. disclaimer: I am not a thread hacker. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 5:32:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 59E8715209; Wed, 24 Nov 1999 05:32:17 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p115-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id AAA18334; Thu, 25 Nov 1999 00:39:47 +1100 Date: Thu, 25 Nov 1999 00:31:59 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Brian Fundakowski Feldman Cc: Peter Wemm , "Alexander N. Kabaev" , Jean-Marc Zucconi , marcel@FreeBSD.org, pho@FreeBSD.org, phk@FreeBSD.org, current@FreeBSD.org Subject: Re: Netscape and -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Brian Fundakowski Feldman wrote: > On Wed, 24 Nov 1999, Bruce Evans wrote: > > > Hmm. My netscape works, but I didn't use merge that commit. I had already > > inadvertly fixed the bug in another way while cleaning up. > > ... > > #if defined(COMPAT_43) || defined(COMPAT_SUNOS) > > if (((struct osigcontext *)uap->sigcntxp)->sc_trapno == 0x01d516) > > return (osigreturn(p, (struct osigreturn_args *)uap)); > > #endif > > I don't see how this fixes things, other than hiding it. Since the i386 I was in a hurry and didn't notice that my inadvertent fix wasn't complete :-). > memory model we use maps kernel and user memory all at the same time, > this code is reading directly from user space memory, right? If this is It could be reading from anywhere with an invalid sigcntxp. Reading from certain locations may cause a panic. > the case, wouldn't a copyin() be the proper thing to do? At least doing > the useracc() would be better than doing nothing, wouldn't it? I plan to use copying and delete the useracc()'s. This will be much faster Checking the magic number is inconvenient, since a copyin() with size (max of the 2 context sizes) may fail and a copyin() with size (min of the 2 context sizes) would leave us with an extra copyin() to do in the usual (new sigreturn()) case. I'll try using fuword() to read the magic byte. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 7:20:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 142A315244 for ; Wed, 24 Nov 1999 07:20:07 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id HAA58191; Wed, 24 Nov 1999 07:19:46 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id HAA77314; Wed, 24 Nov 1999 07:19:46 -0800 (PST) (envelope-from obrien) Date: Wed, 24 Nov 1999 07:19:46 -0800 From: "David O'Brien" To: John Hay Cc: current@FreeBSD.ORG Subject: Re: Overflow in banner(1) Message-ID: <19991124071946.G49362@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <199911240747.AAA18880@harmony.village.org> <199911240758.JAA96963@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911240758.JAA96963@zibbi.mikom.csir.co.za>; from jhay@mikom.csir.co.za on Wed, Nov 24, 1999 at 09:58:51AM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 24, 1999 at 09:58:51AM +0200, John Hay wrote: > Well the original line is plain wrong if Brian's patch is being used, > because there message is a pointer and the size of a pointer is 4. Yes, yes, yes. Warner and I are *not* that stupid WRT C. We were both commenting on the *original* proposed patch. Geez. Now rather than try to call us stupid, Kris (and only Kris) could say, "well, I've decided to go with a dynamically allocated buffer, so of course I can't use sizeof() any more". -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 7:20:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 99CA3152E9; Wed, 24 Nov 1999 07:20:19 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA29757; Wed, 24 Nov 1999 10:19:49 -0500 (EST) (envelope-from wollman) Date: Wed, 24 Nov 1999 10:19:49 -0500 (EST) From: Garrett Wollman Message-Id: <199911241519.KAA29757@khavrinen.lcs.mit.edu> To: Brian Fundakowski Feldman Cc: peter.jeremy@alcatel.com.au, Kris Kennaway , current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: References: <99Nov24.075703est.40331@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > #define SNPARGS(buf, len) buf + len, sizeof(buf) > len ? sizeof(buf) - len : 0 > char action2[32], proto[47], name[18], fragment[17]; > /* Print command name */ > snprintf(SNPARGS(name, 0), "ipfw: %d", f ? f->fw_number : -1); > Despite the fact that the buffer name[] was made to be exactly the > largest size Exactly the largest size of what? All I see here is a magic number. Perhaps if name[] had been declared thus: #define INTTYPE_NCHARS(t) ((sizeof(t) * 3 * CHAR_BIT + 7) / 8) char name[(sizeof "ipfw: ") + INTTYPE_NCHARS(int)]; ...but even then, if KNF is followed, this declaration might be so far away from the printf format that when the format is modified, the programmer might forget to modify the declaration as well. snprintf is a good thing. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 7:24:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id AF47F15242 for ; Wed, 24 Nov 1999 07:24:19 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA29780; Wed, 24 Nov 1999 10:23:54 -0500 (EST) (envelope-from wollman) Date: Wed, 24 Nov 1999 10:23:54 -0500 (EST) From: Garrett Wollman Message-Id: <199911241523.KAA29780@khavrinen.lcs.mit.edu> To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: ps on 4.0-current In-Reply-To: <199911240546.VAA00843@dingo.cdrom.com> References: <19991123183733.A21142@dan.emsphone.com> <199911240546.VAA00843@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > This was discussed close to death before the changes were committed, Where, and by whom? I don't recall seeing any such discussion on -security. > and the current behaviour (restricted access) has been agreed by > general consensus to be the most appropriate. Agreed by whom? Remember POLA? > Making this behaviour tunable would be bad; it adds another option Indeed; it should be reverted completely. Portable programs may not rely on their argv[] being ``secret''. Portable sysadmins rely on argv[] not being ``secret''. Having bogus behavior such as this encourages sysadmins to do all their work as root -- a very Bad Thing. Not only that, it violates 20 years of UNIX tradition. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 7:40: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id E908314CB4 for ; Wed, 24 Nov 1999 07:39:47 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id KAA01402; Wed, 24 Nov 1999 10:41:07 -0500 (EST) Date: Wed, 24 Nov 1999 10:41:07 -0500 From: Dan Moschuk To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. Message-ID: <19991124104107.A264@spirit.jaded.net> References: <199911231905.VAA80946@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911231905.VAA80946@gratis.grondar.za>; from mark@grondar.za on Tue, Nov 23, 1999 at 09:05:25PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | Hello FreebSD'ers! | | [ Apologies to committers, I have Bcc'ed you to ensure you got | this; you may get two copies. ] | | I have been charged with the duty of ensuring that FreeBSD gets a | security audit that has the credibility of OpenBSD's. | | Consider this to be a request-for-discussion that will head us over to | the actual work of getting it done. Great to hear that we are finally doing this. :-) | My proposals are pretty simple; | | 1) We need to eyeball _all_ of the code for potential security holes, | and fix those ASAP. | | 2) I propose that diff(1) FreeBSD with {Open|Net}BSD, and with a | security perspective apply those bits that look relevant and that will | work. Who nose - we may even pick up some useful featurez! I have a set up diff's that introduce OpenBSDs concept of random pids and source port (with a sysctl knob for you sequential weenies) that will have to be updated again before I commit them. -- Dan Moschuk (TFreak!dan@freebsd.org) "Cure for global warming: One giant heatsink and dual fans!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 8: 1:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E6C661525E; Wed, 24 Nov 1999 08:01:00 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA13435; Wed, 24 Nov 1999 09:00:57 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA20734; Wed, 24 Nov 1999 09:01:20 -0700 (MST) Message-Id: <199911241601.JAA20734@harmony.village.org> To: Poul-Henning Kamp Subject: Re: ps on 4.0-current Cc: freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 Nov 1999 09:11:20 +0100." <33189.943431080@critter.freebsd.dk> References: <33189.943431080@critter.freebsd.dk> Date: Wed, 24 Nov 1999 09:01:20 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <33189.943431080@critter.freebsd.dk> Poul-Henning Kamp writes: : In message <199911240801.BAA19058@harmony.village.org>, Warner Losh writes: : : >Not all will agree with this, and it is a change from the past so : >there needs to be a sysctl to control this. And given that it is a : >radical change from the past, it needs to default to open. : : Now, I can't tell if you wore the security-master hard-hat in this : email or not, and I see some quite divergent australian positions, : so I will sit tight until I see a little bit more of a consensus. It was with my hat on, but lemme explain a little how I got here. Before the recent changes to ps, procfs used to not disclose the command line. When it was modified to be used with a ps that didn't need to be set[gu]id it lost this. I wanted to see it restored for those people that had depended on this, but realized that it would be unpopular (and unnecessary) for many people. As part of the change to restore the behavior, I wanted the sysctl. Now that it is half there, I'd like the other half to complete the picture. The reason that it was a big deal to me was that on the old system if you turned off the setuidness of ps, w, et al you would block disclosure of args/env vars, etc, but still have access to process lists. With the change, there was no way to do this which represented a weakening of the overall system on the whole, despite the strenth added by taking the setgid bit off ps. sef has sent me patches that I've not had a chance to review that appear to implement this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 8:12: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 49E9514E7C; Wed, 24 Nov 1999 08:11:46 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA13471; Wed, 24 Nov 1999 09:11:40 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA20799; Wed, 24 Nov 1999 09:12:02 -0700 (MST) Message-Id: <199911241612.JAA20799@harmony.village.org> To: Peter Wemm Subject: Re: ps on 4.0-current Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 Nov 1999 17:05:23 +0800." <19991124090523.9689C1C6D@overcee.netplex.com.au> References: <19991124090523.9689C1C6D@overcee.netplex.com.au> Date: Wed, 24 Nov 1999 09:12:02 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991124090523.9689C1C6D@overcee.netplex.com.au> Peter Wemm writes: : For example, in "workstation" mode, the reasonable default is "open", : because typically there is one user on the box (other than root) and that : person has root access. Excessive hiding info from that user just means : that they'll have to use root more, or will give up the idea of using a mortal : user entirely and run everything as root (a Really Bad idea, think of Windoze : and viruses etc etc). True. : In a dedicated server role, again it might be appropriate to default : it to "open" (dedicated server being something like a squid box), : again there will be a couple of sysadmin type users or people who : have to monitor things. Hiding information gains nothing there : either. I disagree with this, but that is because I've rarely seen a totally dedicated server. A simple fileserver that does nothing else would want to be open in this respect since few people have accounts. : In other roles, including something like a shell server box with presumably : hostile users (you reasonably have to assume this), you want everything you : possibly can to be locked down. Firewall, dialup boxes, dns servers, etc are good candidates to be locked down. : Oh for ACL's, privilige attributes, etc. It would solve this sort of thing : nicely so that you could allow admin users to see what's going on : (including a ps -ax and see what the users are running) without having to : constantly (ab)use root and the dangers of overusing that. sef suggested this be a procfs mount option. I think I like this more than the sysctl option, but don't strong opinion either way (sysctl is more like most of the rest of the system, while a mount option would be harder to change on the fly). Having it be a mount option would make it possible to have a GID that the files are "owned" by that could be 'operator' so that operators can see the args, and possibly other things. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 8:16:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id F12F81522E for ; Wed, 24 Nov 1999 08:16:45 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA13496; Wed, 24 Nov 1999 09:16:19 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA20863; Wed, 24 Nov 1999 09:16:43 -0700 (MST) Message-Id: <199911241616.JAA20863@harmony.village.org> To: Alexey Zelkin Subject: Re: FreeBSD security auditing project. Cc: mark@grondar.za (Mark Murray), current@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 Nov 1999 11:14:30 +0300." <199911240814.LAA08227@scorpion.crimea.ua> References: <199911240814.LAA08227@scorpion.crimea.ua> Date: Wed, 24 Nov 1999 09:16:43 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911240814.LAA08227@scorpion.crimea.ua> Alexey Zelkin writes: : What's going on with FreeBSD Auditing Project : (http://www.FreeBSD.org/auditors.html) ? Is it still alive ? : I think this task is task of this project members. Or will be ;-) Went gangbusters for a short while. Everybody was jazzed. Parts of the tree had bugs fixed. Some bug fixes wound up on the floor. Poor central coordination and management of this project was likely a factor. It accomplished some things, but left others undone. It found nothing major that was snuck in while freefall's root had been compromised (which was the impetus behind the project in the first place). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 8:18:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3A300152B1; Wed, 24 Nov 1999 08:18:02 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA13506; Wed, 24 Nov 1999 09:17:37 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA20883; Wed, 24 Nov 1999 09:18:01 -0700 (MST) Message-Id: <199911241618.JAA20883@harmony.village.org> Subject: Re: ps on 4.0-current To: freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 Nov 1999 09:01:20 MST." <199911241601.JAA20734@harmony.village.org> References: <199911241601.JAA20734@harmony.village.org> <33189.943431080@critter.freebsd.dk> Date: Wed, 24 Nov 1999 09:18:00 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911241601.JAA20734@harmony.village.org> Warner Losh writes: : sef has sent me patches that I've not had a chance to review that : appear to implement this. Actually, these patches do something else. My mistake for reading them before caffeine. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 8:19:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id 59625152C3 for ; Wed, 24 Nov 1999 08:19:08 -0800 (PST) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.1a/8.9.1) id AAA28147; Thu, 25 Nov 1999 00:18:43 +0800 (WST) From: Michael Kennett Message-Id: <199911241618.AAA28147@laurasia.com.au> Subject: Re: FreeBSD security auditing project. In-Reply-To: <199911241519.KAA29757@khavrinen.lcs.mit.edu> from Garrett Wollman at "Nov 24, 99 10:19:49 am" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Thu, 25 Nov 1999 00:18:42 +0800 (WST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > > Perhaps if name[] had been declared thus: > > #define INTTYPE_NCHARS(t) ((sizeof(t) * 3 * CHAR_BIT + 7) / 8) > > char name[(sizeof "ipfw: ") + INTTYPE_NCHARS(int)]; Or alternatively (removing a bit more magic): #include #define INTTYPE_NCHARS(t) (howmany (sizeof(t) * 3 * CHAR_BIT, 8)) The macro howmany() is quite useful. It is also in Mike Kennett (mike@laurasia.com.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 8:26:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5161A15550; Wed, 24 Nov 1999 08:26:37 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA13529; Wed, 24 Nov 1999 09:25:40 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA20923; Wed, 24 Nov 1999 09:26:04 -0700 (MST) Message-Id: <199911241626.JAA20923@harmony.village.org> To: Dan Moschuk Subject: Re: FreeBSD security auditing project. Cc: Mark Murray , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 Nov 1999 10:41:07 EST." <19991124104107.A264@spirit.jaded.net> References: <19991124104107.A264@spirit.jaded.net> <199911231905.VAA80946@gratis.grondar.za> Date: Wed, 24 Nov 1999 09:26:04 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991124104107.A264@spirit.jaded.net> Dan Moschuk writes: : I have a set up diff's that introduce OpenBSDs concept of random pids and : source port (with a sysctl knob for you sequential weenies) that will have : to be updated again before I commit them. I'd like to review this before it goes in, but if I'm unresponsive don't let this request stop you. This is the second class of things we can do to FreeBSD to make it more secure. One is to find bugs in the current programs that might lead to root (and others that don't, since bugs are bugs). The other is to step back and say "hey, if we did blah, then it would significantly deter foo attacks." Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 8:31:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id 0D0E314BFF for ; Wed, 24 Nov 1999 08:31:17 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id LAA01653; Wed, 24 Nov 1999 11:31:39 -0500 (EST) Date: Wed, 24 Nov 1999 11:31:39 -0500 From: Dan Moschuk To: "David O'Brien" Cc: John Hay , current@FreeBSD.ORG Subject: Re: Overflow in banner(1) Message-ID: <19991124113139.D264@spirit.jaded.net> References: <199911240747.AAA18880@harmony.village.org> <199911240758.JAA96963@zibbi.mikom.csir.co.za> <19991124071946.G49362@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991124071946.G49362@dragon.nuxi.com>; from obrien@NUXI.com on Wed, Nov 24, 1999 at 07:19:46AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | Now rather than try to call us stupid, Kris (and only Kris) could say, | "well, I've decided to go with a dynamically allocated buffer, so of | course I can't use sizeof() any more". I've never done this myself, but I've always been under the impression that sizeof(*buf) would work for dynamically allocated buffers. -- Dan Moschuk (TFreak!dan@freebsd.org) "Cure for global warming: One giant heatsink and dual fans!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 8:41:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 41AE514E7C for ; Wed, 24 Nov 1999 08:41:41 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id IAA27931; Wed, 24 Nov 1999 08:41:19 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Wed, 24 Nov 1999 08:41:19 -0800 Date: Wed, 24 Nov 1999 08:41:19 -0800 (PST) From: Kip Macy X-Sender: kip@luna To: Nick Hilliard Cc: current@freebsd.org Subject: Re: Threads and my new job. In-Reply-To: <199911241331.NAA05935@beckett.earlsfort.iol.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: nick@iol.ie,current@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I will admit that I have had odd behaviours with threads in developing Lyris on FreeBSD that I have not seen on Solaris, NT, or Linux. I will see things like what appears to be the thread scheduler stop scheduling threads and just do a busy wait. I have not tracked it down any further for lack of time. -Kip On Wed, 24 Nov 1999, Nick Hilliard wrote: > > Why do we need to smite the Linux database servers? With threads in their > > current state they already outperform Linux's native threads by ~50x for > > things like sending mail. I would assume that the differences in database > > performance is similar. > > The threads (& the old nfs issues which have now thankfully been fixed) in > their current state led bCandid to write about the Cyclone news router: > > : Issues the w/FreeBSD kernel and buggy threads have required our development > : team to wait until improvements to the OS can be made. We did have a beta > : posted on our website for a while but have since removed it. > > disclaimer: I am not a thread hacker. > > Nick > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 8:43:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7168C14FB9; Wed, 24 Nov 1999 08:43:06 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA61137; Wed, 24 Nov 1999 08:43:05 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA77960; Wed, 24 Nov 1999 08:43:04 -0800 (PST) (envelope-from obrien) Date: Wed, 24 Nov 1999 08:43:04 -0800 From: "David O'Brien" To: Dan Moschuk Cc: current@FreeBSD.ORG Subject: Re: Overflow in banner(1) Message-ID: <19991124084304.B77698@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199911240747.AAA18880@harmony.village.org> <199911240758.JAA96963@zibbi.mikom.csir.co.za> <19991124071946.G49362@dragon.nuxi.com> <19991124113139.D264@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991124113139.D264@spirit.jaded.net>; from dan@FreeBSD.ORG on Wed, Nov 24, 1999 at 11:31:39AM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've never done this myself, but I've always been under the impression that > sizeof(*buf) would work for dynamically allocated buffers. sizeof() is an operator whose value is determined at compile time. sizeof(*buf) gives the size of what buf points to. This would be `1' if buf were a char*, or `4' if buf were an int* [on the i386]. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 8:53:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id 54E171525E; Wed, 24 Nov 1999 08:53:29 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id LAA01889; Wed, 24 Nov 1999 11:54:06 -0500 (EST) Date: Wed, 24 Nov 1999 11:54:05 -0500 From: Dan Moschuk To: "David O'Brien" Cc: Dan Moschuk , current@FreeBSD.ORG Subject: Re: Overflow in banner(1) Message-ID: <19991124115405.E264@spirit.jaded.net> References: <199911240747.AAA18880@harmony.village.org> <199911240758.JAA96963@zibbi.mikom.csir.co.za> <19991124071946.G49362@dragon.nuxi.com> <19991124113139.D264@spirit.jaded.net> <19991124084304.B77698@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991124084304.B77698@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Wed, Nov 24, 1999 at 08:43:04AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | sizeof() is an operator whose value is determined at compile time. | sizeof(*buf) gives the size of what buf points to. This would be `1' if | buf were a char*, or `4' if buf were an int* [on the i386]. Ahh, so I've probably seen this concept used only on structures then. -- Dan Moschuk (TFreak!dan@freebsd.org) "Cure for global warming: One giant heatsink and dual fans!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 9:30:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2EE1E1506E; Wed, 24 Nov 1999 09:30:19 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA35711; Wed, 24 Nov 1999 18:29:31 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: ps on 4.0-current In-reply-to: Your message of "Wed, 24 Nov 1999 09:18:00 MST." <199911241618.JAA20883@harmony.village.org> Date: Wed, 24 Nov 1999 18:29:30 +0100 Message-ID: <35709.943464570@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911241618.JAA20883@harmony.village.org>, Warner Losh writes: >In message <199911241601.JAA20734@harmony.village.org> Warner Losh writes: >: sef has sent me patches that I've not had a chance to review that >: appear to implement this. > >Actually, these patches do something else. My mistake for reading >them before caffeine. So please explain the logic you want implemented once people have stopped haggeling about it, it is rather trivial. I pressume we want the same policy for /proc/*/cmdline as for the sysctl ps(1) uses ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 9:40: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from pike.cdrom.com (pike.cdrom.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id ABE7F15180 for ; Wed, 24 Nov 1999 09:39:47 -0800 (PST) (envelope-from cshumway@cdrom.com) Received: from localhost (cshumway@localhost) by pike.cdrom.com (8.9.1a/8.9.1) with ESMTP id JAA26025 for ; Wed, 24 Nov 1999 09:41:16 -0800 (PST) Date: Wed, 24 Nov 1999 09:41:16 -0800 (PST) From: Christopher Shumway To: current@freebsd.org Subject: Re: Make buildworld blowing up In-Reply-To: <19991123192128.B51014@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, David O'Brien wrote: > > Anyone have any ideas whats going on here? > > Yep. ;-) > > > yacc: e - line 30 of "c-parse.y", syntax error > > %expect 51 > > ^ > > *** Error code 1 > > The problem is rev 1.92 of src/Makefile.inc1. With that change, the > tools needed to build GCC aren't made first. I added a few Bison-like > features to Byacc that GCC depended on. The non-tradional "%expect" is > one of them. > > If you manually build and install src/usr.bin/yacc/, a `make world' > should then work. Acutally, you should also do the same for > src/gnu/usr.bin/bison/ as I think you'll hit another problem later in the > build. Excelent, that got me past the first hurdle :) But now its blowing up when compiling /usr/src/gnu/usr.bin/binutils/gdb/ /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:39: readline /readline.h: No such file or directory /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:40: readline /history.h: No such file or directory /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c: In function `line_completion_function': /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:1690: `rl_co mpleter_word_break_characters' undeclared (first use in this function) /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:1690: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:1690: for ea ch function it appears in.) /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c: In function `readline_line_completion_function': /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:1885: `rl_li ne_buffer' undeclared (first use in this function) /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:1885: `rl_po int' undeclared (first use in this function) /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c: In function `command_line_input': /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:2087: warnin g: assignment makes pointer from integer without a cast /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c: In function `show_commands': /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:3254: syntax error before `*' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:3261: `histo ry_base' undeclared (first use in this function) /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:3298: invali d type argument of `->' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c: In function `init_main': /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:3467: `rl_co mpletion_entry_function' undeclared (first use in this function) /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/top.c:3470: `rl_re adline_name' undeclared (first use in this function) *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 9:48:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A100614F80; Wed, 24 Nov 1999 09:48:02 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA13769; Wed, 24 Nov 1999 10:46:16 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA21366; Wed, 24 Nov 1999 10:46:40 -0700 (MST) Message-Id: <199911241746.KAA21366@harmony.village.org> To: Poul-Henning Kamp Subject: Re: ps on 4.0-current Cc: freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 Nov 1999 18:29:30 +0100." <35709.943464570@critter.freebsd.dk> References: <35709.943464570@critter.freebsd.dk> Date: Wed, 24 Nov 1999 10:46:40 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <35709.943464570@critter.freebsd.dk> Poul-Henning Kamp writes: : So please explain the logic you want implemented once people have : stopped haggeling about it, it is rather trivial. OK. I'll likely state what I'd like to see as a patch. : I pressume we want the same policy for /proc/*/cmdline as for the : sysctl ps(1) uses ? Yes. I'll firm this up later today and send an exact proposal out so we can kill this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 10:33: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 311DC15184 for ; Wed, 24 Nov 1999 10:32:57 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id SAA09416; Wed, 24 Nov 1999 18:30:21 GMT (envelope-from geoffb) Date: Wed, 24 Nov 1999 18:30:21 +0000 From: Geoff Buckingham To: Nick Hilliard Cc: current@FreeBSD.ORG Subject: Re: Threads and my new job. Message-ID: <19991124183021.B8898@chuggalug.clues.com> References: <199911241331.NAA05935@beckett.earlsfort.iol.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199911241331.NAA05935@beckett.earlsfort.iol.ie>; from Nick Hilliard on Wed, Nov 24, 1999 at 01:31:44PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 24, 1999 at 01:31:44PM +0000, Nick Hilliard wrote: > > Why do we need to smite the Linux database servers? With threads in their > > current state they already outperform Linux's native threads by ~50x for > > things like sending mail. I would assume that the differences in database > > performance is similar. > > The threads (& the old nfs issues which have now thankfully been fixed) in > their current state led bCandid to write about the Cyclone news router: > > : Issues the w/FreeBSD kernel and buggy threads have required our development > : team to wait until improvements to the OS can be made. We did have a beta > : posted on our website for a while but have since removed it. > > disclaimer: I am not a thread hacker. To this I would add that a number of commercial products currently available for FreeBSD depend on the Linux threads implimentation, notably Inktomis' depending on the future of the linux threads stuff, some diplomacy and vendor support may be necesary. What is the current status of the linux threads (Particularly with regard to SMP, which I recall was a problem)? How far from the userland bound original has libc_r moved ? Is the BSDi thread stuff completely seperate from all of this? -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 10:51:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 41C3B151A7 for ; Wed, 24 Nov 1999 10:51:42 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA36128 for ; Wed, 24 Nov 1999 19:50:34 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: HEADS-UP: bdevs have been assimilated. From: Poul-Henning Kamp Date: Wed, 24 Nov 1999 19:50:34 +0100 Message-ID: <36126.943469434@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I belive I have now fully assimilated the bdevs into the cdevs in the kernel. This means that we have reached the day where it should be of no consequence if you mount /dev/wd0a or /dev/rwd0a. Vinum users: Don't do anything to your vinum configuration until grog tells you it is OK! To test this, take your /etc/fstab file and put a 'r' in front of the device names, ie. change: /dev/ad0s1a / ufs rw 1 1 to /dev/rad0s1a / ufs rw 1 1 ^ and reboot and see if your system feels any different. If I don't hear reports of trouble, I will go a head with the semifinal and final steps of the operation: change MAKEDEV / sysinstall to create only cdevs. Make the bmaj -> cmaj table static and historical and remove the d_bmaj field from cdevsw. Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 11: 1:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3299914E03 for ; Wed, 24 Nov 1999 11:01:15 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA36189 for ; Wed, 24 Nov 1999 20:00:27 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: calcru() warnings... From: Poul-Henning Kamp Date: Wed, 24 Nov 1999 20:00:27 +0100 Message-ID: <36187.943470027@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I still hear reports of sporadic calcru() warnings. If any of you see these, could you try to see if they correlate to the uptime of the machine in question ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 11:18:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from pegasus.freibergnet.de (pegasus.freibergnet.de [194.123.255.9]) by hub.freebsd.org (Postfix) with ESMTP id 33B5114F99 for ; Wed, 24 Nov 1999 11:18:37 -0800 (PST) (envelope-from holm@pegasus.freibergnet.de) Received: (from holm@localhost) by pegasus.freibergnet.de (8.9.3/8.9.1) id UAA28588 for freebsd-current@freebsd.org; Wed, 24 Nov 1999 20:18:19 +0100 (CET) (envelope-from holm) Date: Wed, 24 Nov 1999 20:18:19 +0100 From: Holm Tiffe To: freebsd-current@freebsd.org Subject: - current diskless is it possible ? Message-ID: <19991124201819.A28490@pegasus.freibergnet.de> Reply-To: holm@freibergnet.de Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95i Organization: FreibergNet Internet Services X-Phone: +49-3731-781279 X-Fax: +49-3731-781377 X-PGP-fingerprint: 86 EC A5 63 B5 28 78 13 8B FC E9 09 04 6E 86 FC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have an unconventional setup at home, my PC and an little 386/40 w/o NPU and disk that is routing my net over an ISDN line with i4b to the world. (the router is because there are no free slots anymore in the PC to put the ISDN card in, it is an oldish dual P100 EISA/PCI machine running -current from 3 days ago) So far so good. The problem is, the os on this little diskless router is dated. It is a pre ELF 3.0-current with an I4b from this time too. I have had some problems to get my setup with an new provider (new job) working on an ascent max 1800 and I have decided to update this old router. The router has an wd8013 with an nb8390 boot rom, this seems to make an a.out kernel the way to go (currently) (the linker claims on an symbol _swapdev that he cloudn't find, please someone from the committers can comment this symbol out in sys/i386/i386/symbols.raw nobody needs it anymore) Now I get the Root mount failed: 22 - problem and the machine is asking nicley for a root device. NFS is NOT listed in the list of possible bootdevices, only MFS ?! and something like nfs:139.20.129.5:/usr1/testroot seems to be totally wrong here.... ^ ^ I get : no search device: testroot setrootdevname failed. (from my memory, may be a little incorrect) the panic following later is surely related on to this, but it is a page fault. What should I do ? Is an NFS root supported in -current ? How is the syntax to set the rootdevice ? How about /boot/loader and friends <-> and etherboot ? (the port is outdated, it references etherboot-2.4.5.tar.gz and no one has this old file anymore, current is 2.4.10) Any hints ? Thanks in advance, Holm PS: sorry for my poor english -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 11:35:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 0D0AC153D8; Wed, 24 Nov 1999 11:35:41 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id TAA87909; Wed, 24 Nov 1999 19:35:40 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 24 Nov 1999 19:24:18 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <36187.943470027@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 24 Nov 1999 19:24:16 +0000 To: Poul-Henning Kamp From: Bob Bishop Subject: Re: calcru() warnings... Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 8:00 pm +0100 24/11/99, Poul-Henning Kamp wrote: >I still hear reports of sporadic calcru() warnings. > >If any of you see these, could you try to see if they correlate >to the uptime of the machine in question ? Nov 23 00:03:35 bludnok /kernel: [boot] .... Nov 24 09:02:06 bludnok /kernel: calcru: negative time of -4660895 usec for pid 76002 (cc) Ie up just under 9 hours. Building world at the time. This box is running SMP, full details on request. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 11:47:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id A4F5C154CA for ; Wed, 24 Nov 1999 11:47:37 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id LAA47384; Wed, 24 Nov 1999 11:47:36 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id LAA86837; Wed, 24 Nov 1999 11:46:44 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199911241946.LAA86837@whistle.com> Subject: Re: - current diskless is it possible ? In-Reply-To: <19991124201819.A28490@pegasus.freibergnet.de> from Holm Tiffe at "Nov 24, 99 08:18:19 pm" To: holm@freibergnet.de Date: Wed, 24 Nov 1999 11:46:44 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Holm Tiffe writes: | Is an NFS root supported in -current ? | How is the syntax to set the rootdevice ? | How about /boot/loader and friends <-> and etherboot ? | (the port is outdated, it references etherboot-2.4.5.tar.gz | and no one has this old file anymore, current is 2.4.10) Yes it is possible, but you need to patch sys/i386/i386/autoconf.c. included in this message. I've only tested in the case of netbooting so I could broken normal booting. Then use Etherboot. I also included it an uuencoded update to the etherboot port for etherboot-2.4.10 which can boot a FreeBSD ELF kenel. This all works as of -current (yesterday). Sorry it takes so long for the port to get updated and the Linux guys keep working on Etherboot (which BTW they has code to boot FreeBSD now and they test it). Then I have to wait for someone to read the pr's that I send in. They when someone finally looks at it. It is already obsolete. Same thing with my sdcc port that needs updating. I expect Mike will kill me for this, but it works and I don't have a PXE rom in this machine. I prefer a netboot panic rather then panic'ing my laptop when testing things. Doug A. Index: sys/i386/i386/autoconf.c =================================================================== RCS file: /cvs/freebsd/src/sys/i386/i386/autoconf.c,v retrieving revision 1.143 diff -c -r1.143 autoconf.c *** autoconf.c 1999/11/02 19:38:27 1.143 --- autoconf.c 1999/11/24 18:39:47 *************** *** 48,53 **** --- 48,54 ---- #include "opt_bootp.h" #include "opt_ffs.h" #include "opt_cd9660.h" + #include "opt_nfs.h" #include "opt_nfsroot.h" #include "opt_bus.h" #include "opt_rootdevname.h" *************** *** 213,224 **** --- 214,231 ---- cold = 0; } + #ifdef BOOTP + extern void bootpc_init(); + #endif /* * Do legacy root filesystem discovery. */ void cpu_rootconf() { + #ifdef BOOTP + bootpc_init(); + #endif #if defined(NFS) && defined(NFS_ROOT) #if !defined(BOOTP_NFSROOT) if (nfs_diskless_valid) *************** *** 226,232 **** rootdevnames[0] = "nfs:"; #endif #if defined(FFS) && defined(FFS_ROOT) ! setroot(); #endif } SYSINIT(cpu_rootconf, SI_SUB_ROOT_CONF, SI_ORDER_FIRST, cpu_rootconf, NULL) --- 233,240 ---- rootdevnames[0] = "nfs:"; #endif #if defined(FFS) && defined(FFS_ROOT) ! if (!rootdevnames[0]) ! setroot(); #endif } SYSINIT(cpu_rootconf, SI_SUB_ROOT_CONF, SI_ORDER_FIRST, cpu_rootconf, NULL) begin 664 etherboot.tgz M'XL(`!G].C@"`^U<:7/:3!+V5_0K>AW7QCG0?0`;4B$@>UD;<`%.]D.J>(48 M@0HA:768>%/Y[]LS`HP=9_VFUH%L/$]L(XE6S]'SS'2/6B'9C"3C*,JD@Y\& MT&7+,N``0)55DWXBY-7GZ@0L63$-R]0T%4!1%=DX`.-@!\C3S$D`#IS%./'3 M>?0]N>6,D.#@MP/9V+_Y82#MU_ZR9FJF;%+[&YK,[;][^_?QX/'+4&39-/7_ M8G]-H_:7=471=(O:7].I_65N_Y^.6IR2Y(HDM77[W[E7:4W"/\(!Q^^/._PG M<93Z691<[Y3_NG*'_[II:IS_NP!ENN0EA(S3B11'299*(>'Q!)$4VI$X4P(#&H%LAJ3=5JN@5* MM5J5)*$E4:E4DMAQ[&3N[.9L/F5'G$[_Q_POS+OG^%\W#.;_JPJ/__=B_Y^Q M"_`G[2];NJKIAD+M;VH:M_^^[/_8NP`_'O_KAJ;R]9_'_QQ[X?\C[P(\'/]; M=_AO6!:/_W^)^+\8%GPN>$K\?^Q=@(?Y;][EOZKJG/\[X?]B8F#HKWX;^AO: M)O3G]'\R_,?A\.AE/,1_53:VXG^+QG\X&W#^[P*=E@''FT%0UD555&01NT2< M_OL%U(%,7&-<'>MCLZ*ZQ-,UIVIZRMBJ&(8SUCQ%8`K&?IAG?I"65;$J*J(L MJL:6#E4S9$>MJ%[%FQC:6)>KGJ%JQ+(\UQU799U/+[\"_]<;P0>[YK\JFS?[ M?[HF%_L_!N?_+O`,NF0)S/$'-PH"XF8^>@*+U6``+TIJ:*.;YX'/X`-)4BJ3 MD'_E?D(F->;"B0I^U7(R`FY"\*.XS![OF-"($S]@[@0*?9Q%BQK<02O*I]!8 MV0#>;'8CEC,_S0(BNM'BK?`,[SXZP6#E_:!5@_NBE?4@?GT%BF@4#HQ*D?4XKB#W5]?%K#F[>X0?^U^O71?CPO"^\OV>6O4LB_L;HLVUTD7 MM:,O%[W^<-!J][^N*DDO"T*W-[IH-,\:I]AC083C*?)P2(6>/\T3AXVJD+@D M39WD6K@,C48A%%WW^5TL0M:ZJPW8`ZCI=[ M5AR`9U@"F>"?)5KX:C5,L193)Z4#&29.YJ`N(4Y(>5TS4A-*[@2VR[[56?`W MVOU8HBAM;H'R+$JSNJ]5S'(>SL-H&997,30)O$+_./>#R9_23;DF").H[(%OIIK,FDEAM MV'VK0@#'(R0X?KP@BN-K\!?.E(AX!_GL9Z`(@NB';I!/"+S!5HF4:^)B_I8O MU;_M^K]^I/OX9?Q`_J=N*NSYGZ&:_/G/?NS//LN.L[OXS]3UU?Z/;"F6RO9_ M9+[_NQ.\?/D2UDX3.B#^M'22^-!S,U!5D*LUQ:II10Z(4"Z7-Z)WI2HU=27U M\C;H.5CZ:ZL*[)0JP=.*#'A4%@":)^>-T\&K>JGG..%=\]I+6&0.>X<%CCD8$SP)\!EVM3E^1C2")8$9LX5+LK$"6!!%E%R M31?IA`A[X?]X9_S'>=_8\%]C^S]\_W>7_&\RO_8^]JMR3=YB?R'XK0Q&5=_E M?D5]7:D4W+]%Y$YOV()RJ]W!>&'4L;N7!:V>@1TZXR+PA%6H!W1\%AXJI'E, M*2[\!26WM#5ZE\,1TX4Z[?.3XGBM\@1UQ>CLQID?3ID7/"&>DP<98'R0^0L2 MY1D3W-8X.!N][_6&=14U-KH##().&I?GPSH][MK#C[W^&>N4HH'?SF;_

5<(O3_M^RN`9K[6U1OOCY[JZ_F23DOKC8;#S5@49X>WO@A]EUYZA9>\$.[#_SWD'^,?MKVD* MS__=D_T?_QW@'\O_I>N_KBH\_W'E!=[)]$MPF8 MI`FJ4M/U]38!SRG^5?E?#(9'+N/A]1_Y;UJ:H2(L]OZGI?/U?R?HDHP]?%@_ MB7#$*,\D^_P$BJ0T'@8\)?ZS2?[1RW@P_T-E_)?I__YAZ$7^C\;YOQ,,9SY- M_)T06#HIT"<`?N@$U^`ET>)F4@@G-!4A9$F#YW2/';PHF*LZL3/V\13]2A&@G4'F9?'SE.DKYAD0J"`=B"DJ M*82<((U@AM5R8$'"_$;-M2@((JW@7X&FJ19/3E$L(2S1,0,_!);T<3.ZBS12 MU&M/_`P.BR?9AX)/VX1>S\1/B$MC7O98=A&A)@^;EB=884'H1AE!.>PIOZ@, M2\YPHR3)8Y;8ZJ=ICCU(NZ@--/LSCN(\<-A=A+7*#[U(2+,D=ZE2E&*9JED$ M013-`6N`M:+%BL(^^<_#^`\X[=E0`'@```<' ` end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 12:18:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 9F0211544F; Wed, 24 Nov 1999 12:18:29 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id PAA42121; Wed, 24 Nov 1999 15:18:00 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199911242018.PAA42121@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: calcru() warnings... References: <36187.943470027@critter.freebsd.dk> In-reply-to: Your message of "Wed, 24 Nov 1999 20:00:27 +0100." <36187.943470027@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Nov 1999 15:18:00 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got a few calcru() warnings on a dual Pentium-III Xeon system. It had been up for around 9 or 10 days or so; I've since rebooted it. Specific configuration available if you need it. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 12:36:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D05F7155DE for ; Wed, 24 Nov 1999 12:36:19 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id MAA01202; Wed, 24 Nov 1999 12:36:08 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id MAA24659; Wed, 24 Nov 1999 12:36:08 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 24 Nov 1999 12:36:08 -0800 (PST) Message-Id: <199911242036.MAA24659@vashon.polstra.com> To: wollman@khavrinen.lcs.mit.edu Subject: Re: Route table leaks In-Reply-To: <199911221552.KAA84691@khavrinen.lcs.mit.edu> References: <199911220150.UAA78559@khavrinen.lcs.mit.edu> <199911221552.KAA84691@khavrinen.lcs.mit.edu> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been working on the cvsup-master route table leaks. I haven't found the bug yet, but I've got some clues now. If this info inspires a Eureka! from any of you, please let me know. I started by running this script to print out key information every 2 seconds while I ran a test: #! /bin/sh while :; do date "+%H:%M:%S" vmstat -m | grep 'routetbl[ ]' || exit netstat -ran | egrep 'default|206\.213\.73\.12' || exit echo "=============================" || exit sleep 2 || exit done (Yes, this is crude. But remember, the machine is 900 miles away and I'm trying not to disrupt service too much.) The output began like this: 19:41:56 routetbl 3682 518K 522K 21221K 11473 0 0 16,32,64,128,256 default 204.216.27.17 UGc 1823 60 wb0 ============================= 19:41:58 routetbl 3682 518K 522K 21221K 11473 0 0 16,32,64,128,256 default 204.216.27.17 UGc 1823 60 wb0 I.e., there were 3682 route table structures in use, and 1823 references to the default route. Then I made a connection to the CVSup server from one of my own machines (206.213.73.12): 19:42:00 routetbl 3684 518K 522K 21221K 11475 0 0 16,32,64,128,256 default 204.216.27.17 UGc 1824 60 wb0 206.213.73.12 204.216.27.17 UGHW 1 64 wb0 So far, so good. A cloned route was created and the refcount on the default route was incremented by one. Two new route table entries were allocated, and that seems to be normal and OK. I immediately closed the connection, and it entered the TIME_WAIT state on cvsup-master. The script output remained as above for 60 seconds (2 * MSL), after which it changed to this: 19:42:59 routetbl 3684 518K 522K 21221K 11475 0 0 16,32,64,128,256 default 204.216.27.17 UGc 1824 62 wb0 206.213.73.12 204.216.27.17 UGHW3 0 64 wb0 3600 This still looks OK. The cloned route has gained the "3" flag and a 1-hour expiration time. That is because the TIME_WAIT state has ended, the PCB has been discarded, and the cloned route is now being managed by the caching code in "sys/netinet/in_rmx.c". (That's what the "3" flag signifies.) The basic idea of this code (as I understand it) is to keep cloned routes for dead connections around for awhile in case they are needed again soon. That's useful since the cloned routes contain RTT estimates and so forth. Now we get to the interesting part. One would expect the route to remain cached for 3600 seconds. There are ways that in_rmx.c can expire it sooner than that, but I confirmed that those situations (e.g., too many cached routes) aren't arising. Nevertheless, the route is deleted after roughly another 200 seconds: 19:46:14 routetbl 3684 518K 522K 21221K 11478 0 0 16,32,64,128,256 default 204.216.27.17 UGc 1824 64 wb0 206.213.73.12 204.216.27.17 UGHW3 0 64 wb0 3405 ============================= 19:46:16 routetbl 3682 518K 522K 21221K 11480 0 0 16,32,64,128,256 default 204.216.27.17 UGc 1823 64 wb0 Using DDB and some of routed's tracing options I determined that routed is deleting the route. More on that later. Anyway, given that the route is being deleted, things still look OK in the above. The route is deleted, the 2 route table entries are freed again, and the refcount on the default route is decremented back to its original value. But look what happens in the next 2 seconds: 19:46:18 routetbl 3684 518K 522K 21221K 11482 0 0 16,32,64,128,256 default 204.216.27.17 UGc 1824 64 wb0 The 2 entries were allocated again and the refcount on the default route was incremented. Why? I don't know (yet). But the numbers remain that way thereafter. That's the leak, and I can reproduce it reliably on cvsup-master. Unfortunately, I cannot reproduce the problem here on my own -current machine. I tried to simulate the environment as accurately as possible, including running routed. On my machine, routed deletes the cached route before it has expired too, but the leak doesn't happen. One other thing. Back on cvsup-master, I changed rc.conf so that it sets the default route statically, and I disabled routed. That has completely eliminated the route table leak. Any ideas? Using DDB remotely through a console switch really isn't much fun. I'd prefer a Eureka! from somebody. :-) John -- John Polstra jdp@polstra.com 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 14: 5:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-9.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.137]) by hub.freebsd.org (Postfix) with ESMTP id 55097152D5 for ; Wed, 24 Nov 1999 14:05:47 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA08640; Wed, 24 Nov 1999 21:47:42 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA89224; Wed, 24 Nov 1999 08:03:52 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911240803.IAA89224@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Mike Smith Cc: Dan Nelson , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: ps on 4.0-current In-Reply-To: Message from Mike Smith of "Tue, 23 Nov 1999 21:46:24 PST." <199911240546.VAA00843@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Nov 1999 08:03:52 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In the last episode (Nov 23), Lyndon Nerenberg said: > > > After you verify that this change isn't going to break things that > > > assume they can see the *argv list via ps(1). I.e. lightning bolts > > > that do 'kill -MUMBLE `ps -ax|grep foo`'. Which may not be elegant > > > style, but sometimes is the only workable solution. Indeed. There's always a better way, but I've seen countless production systems that do this all the time. In fact, we've only recently done away with all the (sysv) ``ps -ef''s where I work. > > That won't be affected, because anyone that has kill rights to the > > process will also see the full processname. Now that I think about it, > > I can't come up with a case where this is really bad. If you're doing > > ps'es with intent to kill arbitrary processes (in the name of debugging > > or whatever), you're probably already root. Or maybe you're a sysadm that's smart enough to use sudo and not run around with root liability in normal life. > This was discussed close to death before the changes were committed, > and the current behaviour (restricted access) has been agreed by > general consensus to be the most appropriate. My reading of the thread was ``I'm going to cache ps args to stop all the delving into user space to do a ps'', ``but what about the -e option'', ``ok, I'll make that inaccessible unless you have permission''. I stopped reading the -e thread because I believe it's a good thing to restrict this. I completely missed that the conversation had moved on to ``hey, who needs ps args anyway'', and I'm sure that given the number of messages posted about the -e restriction, others did too. > Making this behaviour tunable would be bad; it adds another option > increasing complexity, and with the proposed default in most cases an > admin tightening up a system would never know about it in the first > place, rendering it useless. > > I'd strongly recommend leaving things they way they are. This change in behaviour will break production systems, and I'm pretty sure that the breakage will be worked around with a quick ``chmod 4555 /bin/ps''. Is this what we want ? Where I work, we've just done away with all the sysv ``ps -ef'' calls in the system. It took several weeks and a lot of testing. I'd be pretty miffed if the OS shoved this down my throat prematurely as a requirement just be cause I upgraded without knowing of the change. Further, I assert that this change is just wrong ! Why does setproctitle() now require root privileges if nobody can see the results ? This is dumb, as the only uid that we're protecting against is the user that's running setproctitle() ! sendmail/nfs/ppp etc can no longer give normal users information on what's going on via the command args (ok, you can figure out the nfs args). System monitoring scripts will now have to run as root. In fact, why do the processes owned by other users show up at all ? The ``you don't need to see their args'' argument can equally apply to needing to see the entire process.... you can always kill -0 a process if you need to know if it's running.... or maybe on second thoughts, we should restrict kill -0 - why should people have this functionality anyway ? I believe the knob is required and should default to the way things were. Well, that's my opinion. I'll calm down now. > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 16:53: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id DD971152A6; Wed, 24 Nov 1999 16:52:57 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id QAA12722; Wed, 24 Nov 1999 16:51:51 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA00469; Wed, 24 Nov 1999 16:51:51 -0800 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA16766; Wed, 24 Nov 99 16:51:47 PST Message-Id: <383C8823.8438567B@softweyr.com> Date: Wed, 24 Nov 1999 17:51:47 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Warner Losh Cc: Peter Wemm , Poul-Henning Kamp , freebsd-current@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: ps on 4.0-current References: <19991124090523.9689C1C6D@overcee.netplex.com.au> <199911241612.JAA20799@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <19991124090523.9689C1C6D@overcee.netplex.com.au> Peter Wemm writes: > : > : In a dedicated server role, again it might be appropriate to default > : it to "open" (dedicated server being something like a squid box), > : again there will be a couple of sysadmin type users or people who > : have to monitor things. Hiding information gains nothing there > : either. > > I disagree with this, but that is because I've rarely seen a totally > dedicated server. A simple fileserver that does nothing else would > want to be open in this respect since few people have accounts. > > : In other roles, including something like a shell server box with presumably > : hostile users (you reasonably have to assume this), you want everything you > : possibly can to be locked down. > > Firewall, dialup boxes, dns servers, etc are good candidates to be > locked down. Firewall, web, dns, news, etc. servers are good candidates to be open because there should not be any "normal" user accounts on them, only administration accounts. And darned few of those. I think this is what Peter was getting at. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 17:16:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id 75D1815124 for ; Wed, 24 Nov 1999 17:16:04 -0800 (PST) (envelope-from niels@bakker.net) Received: from liquid.tpb.net (arctic.xs4all.nl [194.109.37.82]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id CAA04914 for ; Thu, 25 Nov 1999 02:15:14 +0100 (CET) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id CAA03912 for ; Thu, 25 Nov 1999 02:15:13 +0100 Date: Thu, 25 Nov 1999 02:15:13 +0100 (CET) From: N X-Sender: niels@liquid.tpb.net To: current@FreeBSD.ORG Subject: Re: calcru() warnings... In-Reply-To: <36187.943470027@critter.freebsd.dk> Message-ID: <9911250213010.3257-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > I still hear reports of sporadic calcru() warnings. > > If any of you see these, could you try to see if they correlate > to the uptime of the machine in question ? Should they start or stop when a machine has been running a while? I see neither (negative calcru notices in dmesg start at boot time and didn't stop until the box had a kernel panic last Saturday evening, after about two weeks uptime). FWIW, the messages started occurring when I switched from a pre-signal to post-signal change kernel and world. -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 17:29:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 697A61554C; Wed, 24 Nov 1999 17:29:16 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id AAA28968; Wed, 24 Nov 1999 00:25:15 GMT (envelope-from nik) Date: Wed, 24 Nov 1999 00:25:15 +0000 From: Nik Clayton To: current@freebsd.org Cc: hackers@freebsd.org Subject: Re: Threads and my new job. Message-ID: <19991124002515.A28472@catkin.nothing-going-on.org> References: <19991122185220.D301@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19991122185220.D301@sturm.canonware.com>; from Jason Evans on Mon, Nov 22, 1999 at 06:52:20PM -0800 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason, On Mon, Nov 22, 1999 at 06:52:20PM -0800, Jason Evans wrote: > Walnut Creek has hired me as a full time employee to work primarily on > improving and expanding FreeBSD's threads support. This is very exciting > to me, and I hope my work will be of benefit the FreeBSD community. That's great. Is it part of your remit to maintain http://www.FreeBSD.org/threads/? That URL doesn't exist at the moment, but if we're going to have an active threads project, it probably should. Are you (or anyone else reading this, you don't have to be a committer at the moment) interested in keeping this section up to date? N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 17:37:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id C39FD155A3; Wed, 24 Nov 1999 17:36:58 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA13294; Thu, 25 Nov 1999 10:38:57 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <36187.943470027@critter.freebsd.dk> Date: Thu, 25 Nov 1999 10:38:56 +1030 (CST) From: "Daniel O'Connor" To: Poul-Henning Kamp Subject: RE: calcru() warnings... Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Nov-99 Poul-Henning Kamp wrote: > I still hear reports of sporadic calcru() warnings. > > If any of you see these, could you try to see if they correlate > to the uptime of the machine in question ? I have had them for Seti@Home occasionally. The system hadn't been up for more than 24 hours. Its a dual PII-350. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 18:56: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 41E2114D59 for ; Wed, 24 Nov 1999 18:55:58 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id VAA43686; Wed, 24 Nov 1999 21:54:15 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <199911240803.IAA89224@hak.lan.Awfulhak.org> References: <199911240803.IAA89224@hak.lan.Awfulhak.org> Date: Wed, 24 Nov 1999 21:55:54 -0500 To: Brian Somers , Mike Smith From: Garance A Drosihn Subject: Re: ps on 4.0-current Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:03 AM +0000 11/24/99, Brian Somers wrote: > > This was discussed close to death before the changes were committed, > > and the current behaviour (restricted access) has been agreed by > > general consensus to be the most appropriate. > >My reading of the thread was ``I'm going to cache ps args to stop all >the delving into user space to do a ps'', ``but what about the -e >option'', ``ok, I'll make that inaccessible unless you have >permission''. > >I stopped reading the -e thread because I believe it's a good thing to >restrict this. I completely missed that the conversation had moved >on to ``hey, who needs ps args anyway'', and I'm sure that given the >number of messages posted about the -e restriction, others did too. For what it's worth, this is also what happened to me. I tuned out the '-e' thread once I had said my two-bits on the topic (and I was pretty sure the end result would come out OK with me). I did not notice the topic of also removing argv from 'ps'. Removing 'ps -e' ability is fine by me (though I'd prefer that I could see the environment of "my own" processes). I can see how that would improve security, even if it occasionally means a very slight loss in user convenience. I am not at all happy with the idea of removing argv from 'ps' listings. I have scripts which use that information, and it sounds like the only way to fix those scripts would make things WORSE for security. This does not benefit "user convenience" and it does not benefit "security". At the same time, I remember many years ago when another OS that I worked on was trying for security classification. I can see that this behavior *could* be a good idea for situations which want to be really paranoid about security. I would not mind this behavior as a system-wide option, but I'd certainly want the default setting to match current behavior. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 19: 6:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id EF59915002; Wed, 24 Nov 1999 19:06:41 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (lavender.rad.cc.keio.ac.jp [131.113.16.115]) by titanium.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id MAA03095; Thu, 25 Nov 1999 12:06:40 +0900 (JST) (envelope-from sanpei@sanpei.org) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id MAA06625; Thu, 25 Nov 1999 12:06:40 +0900 (JST) Date: Thu, 25 Nov 1999 12:06:40 +0900 (JST) Message-Id: <199911250306.MAA06625@lavender.yy.cs.keio.ac.jp> To: current@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Threads and my new job. In-Reply-To: Your message of "Tue, 23 Nov 1999 11:52:20 JST". <19991122185220.D301@sturm.canonware.com> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jasone@canonware.com wrote: >> *) Lacking interfaces, such as pthread_cancel() (mentioned specifically in >> PR bin/7587) need to be implemented. It's good news for me. I hope to port xmovie -- QuickTime movie Player for Linux to FreeBSD. But I can not compile it under FreeBSD, because it's need pthread_cancel. xmovie http://heroine.linuxbox.com/xmovie.html MIHIRA Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 21:52:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id EB91D14C36; Wed, 24 Nov 1999 21:52:22 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 6818A2CE50; Thu, 25 Nov 1999 07:51:50 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 790B9F6; Thu, 25 Nov 1999 07:51:54 +0200 (EET) Date: Thu, 25 Nov 1999 07:51:54 +0200 From: Vallo Kallaste To: Daniel O'Connor Cc: Poul-Henning Kamp , current@freebsd.org Subject: Re: calcru() warnings... Message-ID: <19991125075154.A28610@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <36187.943470027@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Daniel O'Connor on Thu, Nov 25, 1999 at 10:38:56AM +1030 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 25, 1999 at 10:38:56AM +1030, Daniel O'Connor wrote: > > On 24-Nov-99 Poul-Henning Kamp wrote: > > I still hear reports of sporadic calcru() warnings. > > > > If any of you see these, could you try to see if they correlate > > to the uptime of the machine in question ? > > I have had them for Seti@Home occasionally. The system hadn't been up for more > than 24 hours. > > Its a dual PII-350. Same here, running setiathome means that I can find such processes after a day or so: 4 ?? DL -2341043:-35.26 (bufdaemon) The ``calcru'' messages aren't strictly necessary, such things happen without them also. Dual PIII-500, two seti processes. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 24 23: 9:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3C66F14D34 for ; Wed, 24 Nov 1999 23:06:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA39371; Thu, 25 Nov 1999 08:05:24 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: N Cc: current@FreeBSD.ORG Subject: Re: calcru() warnings... In-reply-to: Your message of "Thu, 25 Nov 1999 02:15:13 +0100." <9911250213010.3257-100000@liquid.tpb.net> Date: Thu, 25 Nov 1999 08:05:24 +0100 Message-ID: <39369.943513524@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this SMP ? In message <9911250213010.3257-100000@liquid.tpb.net>, N writes: >Poul-Henning Kamp wrote: > >> I still hear reports of sporadic calcru() warnings. >> >> If any of you see these, could you try to see if they correlate >> to the uptime of the machine in question ? > >Should they start or stop when a machine has been running a while? I see >neither (negative calcru notices in dmesg start at boot time and didn't >stop until the box had a kernel panic last Saturday evening, after about >two weeks uptime). > >FWIW, the messages started occurring when I switched from a pre-signal to >post-signal change kernel and world. > > > -- Niels. > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 0:55:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 19A0114CAD for ; Thu, 25 Nov 1999 00:55:18 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 3620550 invoked from network); 25 Nov 1999 08:53:58 -0000 Received: from s123.paris-36.cybercable.fr (HELO cybercable.fr) ([212.198.36.123]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 25 Nov 1999 08:53:58 -0000 Message-ID: <383CF953.E67B897E@cybercable.fr> Date: Thu, 25 Nov 1999 09:54:43 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: calcru() warnings... References: <39369.943513524@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I also get some "calcru" warnings As my MB is overclocked (100 MHz FSB for Celerons), I had not sent in a PR It's four days since I last rebooted and I don't have a single "calcru" warning (they are usually on the "tail -f rc5.log" process I use to follow the rc5 crunching). TfH Here is a snippet of my last dmesg : Nov 21 13:22:29 multi /kernel: FreeBSD 4.0-CURRENT #7: Thu Sep 30 22:47:49 CEST 1999 Nov 21 13:22:29 multi /kernel: Timecounter "i8254" frequency 1193182 Hz Nov 21 13:22:29 multi /kernel: CPU: Celeron (501.14-MHz 686-class CPU) Nov 21 13:22:29 multi /kernel: Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Nov 21 13:22:29 multi /kernel: Features=0x183fbff Nov 21 13:22:29 multi /kernel: real memory = 134217728 (131072K bytes) Nov 21 13:22:29 multi /kernel: avail memory = 127283200 (124300K bytes) Nov 21 13:22:29 multi /kernel: Programming 24 pins in IOAPIC #0 Nov 21 13:22:29 multi /kernel: FreeBSD/SMP: Multiprocessor motherboard Nov 21 13:22:29 multi /kernel: cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 Nov 21 13:22:29 multi /kernel: cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 Nov 21 13:22:29 multi /kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Nov 21 13:22:30 multi /kernel: wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 Nov 21 13:22:30 multi /kernel: wd0: 4111MB (8420832 sectors), 8354 cyls, 16 heads, 63 S/T, 512 B/S Nov 21 13:22:30 multi /kernel: wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 Nov 21 13:22:30 multi /kernel: wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-32 Nov 21 13:22:30 multi /kernel: wd2: 1033MB (2116800 sectors), 2100 cyls, 16 heads, 63 S/T, 512 B/S Nov 21 13:22:30 multi /kernel: ed0 at port 0x300-0x31f iomem 0xd8000 irq 5 on isa0 Nov 21 13:22:30 multi /kernel: ed0: address 52:54:4c:1b:90:1b, type NE2000 (16 bit) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 1:48:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id B61F914D87 for ; Thu, 25 Nov 1999 01:48:41 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id PAA27701; Thu, 25 Nov 1999 15:48:40 +0600 (NOVT) (envelope-from nnd) Date: Thu, 25 Nov 1999 15:48:40 +0600 (NOVT) Message-Id: <199911250948.PAA27701@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@FreeBSD.ORG Subject: FreeBSD ELF Netscape binaries ? User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What (if any) are the problems with native FreeBSD ELF Netscape Communicator/Navigator binaries ? N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 3:55:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 11A7514DC7 for ; Thu, 25 Nov 1999 03:55:20 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-5.iptelecom.net.ua [212.9.227.5]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA23895; Thu, 25 Nov 1999 13:57:12 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id NAA28909; Thu, 25 Nov 1999 13:31:14 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <383D1DFB.80CD028F@altavista.net> Date: Thu, 25 Nov 1999 13:31:07 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: nnd@mail.nsk.ru Cc: current@FreeBSD.ORG Subject: Re: FreeBSD ELF Netscape binaries ? References: <199911250948.PAA27701@wint.itfs.nsk.su> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nnd@mail.nsk.ru wrote: > What (if any) are the problems with > native FreeBSD ELF Netscape Communicator/Navigator binaries ? AFAIK one major problem exist - ELF version is still unavailable. From ftp://ftp.netscape.com/pub/communicator/english/4.7/unix/unsupported/freebsd/complete_install/README.txt: [...] A native FreeBSD version of Communicator is now available for FreeBSD 2.2. [...] -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 5:14:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.49]) by hub.freebsd.org (Postfix) with ESMTP id 9B83214D4E for ; Thu, 25 Nov 1999 05:14:47 -0800 (PST) (envelope-from niels@bakker.net) Received: from liquid.tpb.net (arctic.xs4all.nl [194.109.37.82]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id OAA17343; Thu, 25 Nov 1999 14:14:45 +0100 (CET) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id OAA04945; Thu, 25 Nov 1999 14:14:45 +0100 Date: Thu, 25 Nov 1999 14:14:44 +0100 (CET) From: N X-Sender: niels@liquid.tpb.net To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: calcru() warnings... In-Reply-To: <39369.943513524@critter.freebsd.dk> Message-ID: <9911251409500.4928-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: >>> I still hear reports of sporadic calcru() warnings. >>> >>> If any of you see these, could you try to see if they correlate >>> to the uptime of the machine in question ? >> Should they start or stop when a machine has been running a while? I see >> neither (negative calcru notices in dmesg start at boot time and didn't >> stop until the box had a kernel panic last Saturday evening, after about >> two weeks uptime). >> FWIW, the messages started occurring when I switched from a pre-signal to >> post-signal change kernel and world. > Is this SMP ? Yes. FreeBSD buty.wanadoo.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #25: Thu Nov 11 02:41:49 CET 1999 root@buty.wanadoo.nl:/usr/src/sys/compile/BUTY i386 It's an ASUS P2B-DS, BIOS rev. 1010, which I also upgraded (from 1009 - broken statclock!) in that timeframe... -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 6:10:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 4ED1814BB7 for ; Thu, 25 Nov 1999 06:10:07 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id UAA32904; Thu, 25 Nov 1999 20:10:05 +0600 (NOVT) (envelope-from nnd) Date: Thu, 25 Nov 1999 20:10:05 +0600 (NOVT) Message-Id: <199911251410.UAA32904@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: FreeBSD ELF Netscape binaries ? In-Reply-To: <383D1DFB.80CD028F@altavista.net> User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <383D1DFB.80CD028F@altavista.net> Maxim Sobolev wrote: > nnd@mail.nsk.ru wrote: > >> What (if any) are the problems with >> native FreeBSD ELF Netscape Communicator/Navigator binaries ? > > AFAIK one major problem exist - ELF version is still unavailable. Sorry, but my question must be - WHY there still is no ELF version of Netscape Communicator for FreeBSD ? (FreeBSD's point of view to this problem ?) N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 6:50:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id AB45214D1F for ; Thu, 25 Nov 1999 06:50:14 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id OAA08911; Thu, 25 Nov 1999 14:50:12 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199911251410.UAA32904@wint.itfs.nsk.su> Date: Thu, 25 Nov 1999 14:50:11 -0000 (GMT) From: "Steve O'Hara-Smith" To: nnd@mail.nsk.ru Subject: Re: FreeBSD ELF Netscape binaries ? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Nov-99 nnd@mail.nsk.ru wrote: > In <383D1DFB.80CD028F@altavista.net> Maxim Sobolev > wrote: >> nnd@mail.nsk.ru wrote: > Sorry, but my question must be - WHY there still is no > ELF version of Netscape Communicator for FreeBSD ? > (FreeBSD's point of view to this problem ?) Because Netscape haven't built one (and nobody else can). ------------------------------------------------------- Tell a computer to WIN and ... ... You lose ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 7:23:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from yormungandr.demos.su (yormungandr.demos.su [194.87.5.30]) by hub.freebsd.org (Postfix) with ESMTP id B8A1714A23 for ; Thu, 25 Nov 1999 07:23:29 -0800 (PST) (envelope-from mishania@yormungandr.demos.su) Received: (from mishania@localhost) by yormungandr.demos.su (8.9.3/8.9.2) id SAA26870; Thu, 25 Nov 1999 18:23:28 +0300 (MSK) (envelope-from mishania) Date: Thu, 25 Nov 1999 18:23:27 +0300 From: "Mikhail A. Sokolov" To: current@freebsd.org Subject: tcp (nfs?) troubles. Message-ID: <19991125182327.A26801@demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, environment is as follows, PII-Xeon, 1Gb RAM, -current as of yesterday, nfsd serving some 12 nfsv3,mntudp,rdirplus clients. Any clues, please? # > {zz}/var/crash# gdb -k -symbols=/usr/src/sys/compile/WZ/kernel.debug *0 # > GNU gdb 4.18 # > Copyright 1998 Free Software Foundation, Inc. # > GDB is free software, covered by the GNU General Public License, and you are # > welcome to change it and/or distribute copies of it under certain conditions. # > Type "show copying" to see the conditions. # > There is absolutely no warranty for GDB. Type "show warranty" for details. # > This GDB was configured as "i386-unknown-freebsd"... # > (no debugging symbols found)... # > SMP 2 cpus # > IdlePTD 2965504 # > initial pcb at 26af60 # > panicstr: tcp_setpersist: retransmit pending # > panic messages: # > --- # > panic: tcp_setpersist: retransmit pending # > mp_lock = 00000001; cpuid = 0; lapic.id = 01000000 # > boot() called on cpu#0 # > # > syncing disks... 8 # > done # > (da1:ahc2:0:4:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 # > (da1:ahc2:0:4:0): ILLEGAL REQUEST asc:20,0 # > (da1:ahc2:0:4:0): Invalid command operation code # > # > dumping to dev #da/0x20001, offset 2153899 # > dump 1023 1022 1021 1020 1019 1018 1017 1016 1015 1014 1013 1012 1011 1010 1009 1008 1007 1006 1005 1004 1003 1002 1001 1000 999 998 997 996 995 994 993 992 991 990 989 988 987 986 985 984 983 982 981 980 979 978 977 976 975 974 973 972 971 970 969 968 967 966 965 964 963 962 961 960 959 958 957 956 955 954 953 952 951 950 949 948 947 946 945 944 943 942 941 940 939 938 937 936 935 934 933 932 931 930 929 928 927 926 925 924 923 922 921 920 919 918 917 916 915 914 913 912 911 910 909 908 907 906 905 904 903 902 901 900 899 898 897 896 895 894 893 892 891 890 889 888 887 886 885 884 883 882 881 880 879 878 877 876 875 874 873 872 871 870 869 868 867 866 865 864 863 862 861 860 859 858 857 856 855 854 853 852 851 850 849 848 847 846 845 844 843 842 841 840 839 838 837 836 835 834 833 832 831 830 829 828 827 826 825 824 823 822 821 820 819 818 817 816 815 814 813 812 811 810 809 808 807 806 805 804 803 802 801 800 799 798 797 796 795 794 793 792 791 790 789 788 787 786 785 ! 784 ! # > 783 782 781 780 779 778 777 776 775 774 773 772 771 770 769 768 767 766 765 764 763 762 761 760 759 758 757 756 755 754 753 752 751 750 749 748 747 746 745 744 743 742 741 740 739 738 737 736 735 734 733 732 731 730 729 728 727 726 725 724 723 722 721 720 719 718 717 716 715 714 713 712 711 710 709 708 707 706 705 704 703 702 701 700 699 698 697 696 695 694 693 692 691 690 689 688 687 686 685 684 683 682 681 680 679 678 677 676 675 674 673 672 671 670 669 668 667 666 665 664 663 662 661 660 659 658 657 656 655 654 653 652 651 650 649 648 647 646 645 644 643 642 641 640 639 638 637 636 635 634 633 632 631 630 629 628 627 626 625 624 623 622 621 620 619 618 617 616 615 614 613 612 611 610 609 608 607 606 605 604 603 602 601 600 599 598 597 596 595 594 593 592 591 590 589 588 587 586 585 584 583 582 581 580 579 578 577 576 575 574 573 572 571 570 569 568 567 566 565 564 563 562 561 560 559 558 557 556 555 554 553 552 551 550 549 548 547 546 545 544 543 542 541 540 539 538 ! 537 ! # > 536 535 534 533 532 531 530 529 528 527 526 525 524 523 522 521 520 51 # > 9 518 517 516 515 514 513 512 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273! 272! # > 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 # > --- # > #0 0xc01464b0 in boot () # > (kgdb) where # > #0 0xc01464b0 in boot () # > #1 0xc01466e5 in panic () # > #2 0xc0194460 in tcp_setpersist () # > #3 0xc0195516 in tcp_timer_persist () # > #4 0xc014c10a in softclock () # > (kgdb) -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 7:26:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.fns.ru (ns.fns.ru [212.119.211.200]) by hub.freebsd.org (Postfix) with ESMTP id 8463A14CE8 for ; Thu, 25 Nov 1999 07:26:49 -0800 (PST) (envelope-from ilya@fns.ru) Received: from gatekeeper.intranet (gatekeeper.intranet [10.0.1.222]) by ns.fns.ru (8.9.3/8.9.3) with ESMTP id SAA31996; Thu, 25 Nov 1999 18:26:46 +0300 (MSK) (envelope-from ilya@fns.ru) Received: by gatekeeper.fns.ru with Internet Mail Service (5.5.1960.3) id ; Thu, 25 Nov 1999 18:26:45 +0300 Message-ID: <71E45CD96094D311B7F900608C71F7751C2E@gatekeeper.fns.ru> From: Ilya Pekshev To: "'Mikhail A. Sokolov'" , current@FreeBSD.ORG Subject: RE: tcp (nfs?) troubles. Date: Thu, 25 Nov 1999 18:26:43 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain; charset="ISO-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, had the same trouble with yesterdays' build. Try running cvsup again and it fixed the problem for me. Regards, Ilya -----Original Message----- From: Mikhail A. Sokolov [mailto:mishania@demos.net] Sent: Thursday, November 25, 1999 18:23 To: current@FreeBSD.ORG Subject: tcp (nfs?) troubles. Hello, environment is as follows, PII-Xeon, 1Gb RAM, -current as of yesterday, nfsd serving some 12 nfsv3,mntudp,rdirplus clients. Any clues, please? # > {zz}/var/crash# gdb -k -symbols=/usr/src/sys/compile/WZ/kernel.debug *0 # > GNU gdb 4.18 # > Copyright 1998 Free Software Foundation, Inc. # > GDB is free software, covered by the GNU General Public License, and you are # > welcome to change it and/or distribute copies of it under certain conditions. # > Type "show copying" to see the conditions. # > There is absolutely no warranty for GDB. Type "show warranty" for details. # > This GDB was configured as "i386-unknown-freebsd"... # > (no debugging symbols found)... # > SMP 2 cpus # > IdlePTD 2965504 # > initial pcb at 26af60 # > panicstr: tcp_setpersist: retransmit pending # > panic messages: # > --- # > panic: tcp_setpersist: retransmit pending # > mp_lock = 00000001; cpuid = 0; lapic.id = 01000000 # > boot() called on cpu#0 # > # > syncing disks... 8 # > done # > (da1:ahc2:0:4:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 # > (da1:ahc2:0:4:0): ILLEGAL REQUEST asc:20,0 # > (da1:ahc2:0:4:0): Invalid command operation code # > # > dumping to dev #da/0x20001, offset 2153899 # > dump 1023 1022 1021 1020 1019 1018 1017 1016 1015 1014 1013 1012 1011 1010 1009 1008 1007 1006 1005 1004 1003 1002 1001 1000 999 998 997 996 995 994 993 992 991 990 989 988 987 986 985 984 983 982 981 980 979 978 977 976 975 974 973 972 971 970 969 968 967 966 965 964 963 962 961 960 959 958 957 956 955 954 953 952 951 950 949 948 947 946 945 944 943 942 941 940 939 938 937 936 935 934 933 932 931 930 929 928 927 926 925 924 923 922 921 920 919 918 917 916 915 914 913 912 911 910 909 908 907 906 905 904 903 902 901 900 899 898 897 896 895 894 893 892 891 890 889 888 887 886 885 884 883 882 881 880 879 878 877 876 875 874 873 872 871 870 869 868 867 866 865 864 863 862 861 860 859 858 857 856 855 854 853 852 851 850 849 848 847 846 845 844 843 842 841 840 839 838 837 836 835 834 833 832 831 830 829 828 827 826 825 824 823 822 821 820 819 818 817 816 815 814 813 812 811 810 809 808 807 806 805 804 803 802 801 800 799 798 797 796 795 794 793 792 791 790 789 788 787 786 785 ! 784 ! # > 783 782 781 780 779 778 777 776 775 774 773 772 771 770 769 768 767 766 765 764 763 762 761 760 759 758 757 756 755 754 753 752 751 750 749 748 747 746 745 744 743 742 741 740 739 738 737 736 735 734 733 732 731 730 729 728 727 726 725 724 723 722 721 720 719 718 717 716 715 714 713 712 711 710 709 708 707 706 705 704 703 702 701 700 699 698 697 696 695 694 693 692 691 690 689 688 687 686 685 684 683 682 681 680 679 678 677 676 675 674 673 672 671 670 669 668 667 666 665 664 663 662 661 660 659 658 657 656 655 654 653 652 651 650 649 648 647 646 645 644 643 642 641 640 639 638 637 636 635 634 633 632 631 630 629 628 627 626 625 624 623 622 621 620 619 618 617 616 615 614 613 612 611 610 609 608 607 606 605 604 603 602 601 600 599 598 597 596 595 594 593 592 591 590 589 588 587 586 585 584 583 582 581 580 579 578 577 576 575 574 573 572 571 570 569 568 567 566 565 564 563 562 561 560 559 558 557 556 555 554 553 552 551 550 549 548 547 546 545 544 543 542 541 540 539 538 ! 537 ! # > 536 535 534 533 532 531 530 529 528 527 526 525 524 523 522 521 520 51 # > 9 518 517 516 515 514 513 512 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273! 272! # > 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 # > --- # > #0 0xc01464b0 in boot () # > (kgdb) where # > #0 0xc01464b0 in boot () # > #1 0xc01466e5 in panic () # > #2 0xc0194460 in tcp_setpersist () # > #3 0xc0195516 in tcp_timer_persist () # > #4 0xc014c10a in softclock () # > (kgdb) -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 8:32:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 5999814E7D for ; Thu, 25 Nov 1999 08:32:18 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-29.iptelecom.net.ua [212.9.227.29]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id SAA04798; Thu, 25 Nov 1999 18:34:44 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id QAA29487; Thu, 25 Nov 1999 16:50:16 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <383D4C9D.4ECF9281@altavista.net> Date: Thu, 25 Nov 1999 16:50:05 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: nnd@mail.nsk.ru Cc: current@FreeBSD.ORG Subject: Re: FreeBSD ELF Netscape binaries ? References: <199911251410.UAA32904@wint.itfs.nsk.su> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nnd@mail.nsk.ru wrote: > In <383D1DFB.80CD028F@altavista.net> Maxim Sobolev wrote: > > nnd@mail.nsk.ru wrote: > > > >> What (if any) are the problems with > >> native FreeBSD ELF Netscape Communicator/Navigator binaries ? > > > > AFAIK one major problem exist - ELF version is still unavailable. > > Sorry, but my question must be - WHY there still is no > ELF version of Netscape Communicator for FreeBSD ? > (FreeBSD's point of view to this problem ?) IMHO it is not a right place to ask (try to mail Netscape instead). Seems that Netscape doesn't see any objections to bother with porting, probably because aout binaries still supported (at least theoretically, while in fact it is huge headache associated with the need to have two versions of each .so). -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 10: 9:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 782C914EDF; Thu, 25 Nov 1999 10:09:22 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991125130920.10078@mojave.sitaranetworks.com> Date: Thu, 25 Nov 1999 13:09:20 -0500 From: Greg Lehey To: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: ST-506, ESDI and BAD144 ? Reply-To: Greg Lehey References: <33801.943436384@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <33801.943436384@critter.freebsd.dk>; from Poul-Henning Kamp on Wed, Nov 24, 1999 at 10:39:44AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 24 November 1999 at 10:39:44 +0100, Poul-Henning Kamp wrote: > > Sørens new ATA driver can handle all IDE disks as far as has been > tested now, but it doesn't provide bad sector remapping which is > needed for ESDI and ST-506 disks. > > Having two drivers fight for the same class of drivers is a rather > messy process, and it complicates the code a fair bit, not to > mention the clutter in end-user documentation. > > Considering that most of the machines with ST-506 and ESDI disks > are limited to 16MB ram anyway, I think it would be reasonable to > simply tell the users of these old irons to stick with the 3.X > branch until end of life (there is probably at least 1.5 years more > life in the 3.X branch judging from the history of the 2.2.X branch). > > So I would like to propose that we discontinue support for ST-506, > ESDI disks and BAD144 bad-sector remapping starting with the 4.0 > release. > > So, is anyone running -current on ESDI or ST-506 disks in > actual applications (as opposed for the gadget/novelty thrill or > testing purposes) ? I don't suppose it would be that big a deal to remove the old driver, but what speaks against leaving it in the tree along with a comment in the GENERIC config file saying "if you use antediluvial disk hardware, you may prefer to use an old driver too"? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 10:30:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 9BE9D14BCD; Thu, 25 Nov 1999 10:30:03 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991125133001.64729@mojave.sitaranetworks.com> Date: Thu, 25 Nov 1999 13:30:01 -0500 From: Greg Lehey To: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADS-UP: bdevs have been assimilated. Reply-To: Greg Lehey References: <36126.943469434@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <36126.943469434@critter.freebsd.dk>; from Poul-Henning Kamp on Wed, Nov 24, 1999 at 07:50:34PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 24 November 1999 at 19:50:34 +0100, Poul-Henning Kamp wrote: > > I belive I have now fully assimilated the bdevs into the cdevs in > the kernel. This means that we have reached the day where it should > be of no consequence if you mount /dev/wd0a or /dev/rwd0a. > > Vinum users: Don't do anything to your vinum configuration until > grog tells you it is OK! Well, you can try :-) I won't be able to test this myself for another few weeks, but I don't think it will cause any problems. For the while you will still have two sets of devices (block and char) in /dev/vinum/, though. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 11:42:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B515114C86; Thu, 25 Nov 1999 11:42:40 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA00788; Thu, 25 Nov 1999 19:53:28 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: freebsd-current@freebsd.org, security@freebsd.org Subject: Re: ps on 4.0-current In-reply-to: Your message of "Wed, 24 Nov 1999 01:01:33 MST." <199911240801.BAA19058@harmony.village.org> Date: Thu, 25 Nov 1999 19:53:28 +0100 Message-ID: <786.943556008@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I've understood the conclusion of this thread, we want a sysctl, and we want it open as default. This patch should do that. Once Warner nods in the vertical direction it will be committed. Poul-Henning Index: kern/kern_exec.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_exec.c,v retrieving revision 1.103 diff -u -r1.103 kern_exec.c --- kern_exec.c 1999/11/16 20:31:51 1.103 +++ kern_exec.c 1999/11/25 18:32:41 @@ -77,6 +77,9 @@ SYSCTL_LONG(_kern, OID_AUTO, ps_arg_cache_limit, CTLFLAG_RW, &ps_arg_cache_limit, ""); +int ps_argsopen = 1; +SYSCTL_INT(_kern, OID_AUTO, ps_argsopen, CTLFLAG_RW, &ps_argsopen, 0, ""); + /* * Each of the items is a pointer to a `const struct execsw', hence the * double pointer here. Index: kern/kern_proc.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_proc.c,v retrieving revision 1.61 diff -u -r1.61 kern_proc.c --- kern_proc.c 1999/11/21 19:03:09 1.61 +++ kern_proc.c 1999/11/25 18:31:51 @@ -633,7 +633,7 @@ if (!p) return (0); - if (p_trespass(curproc, p)) + if ((!ps_argsopen) && p_trespass(curproc, p)) return (0); if (req->newptr && curproc != p) Index: miscfs/procfs/procfs_status.c =================================================================== RCS file: /home/ncvs/src/sys/miscfs/procfs/procfs_status.c,v retrieving revision 1.18 diff -u -r1.18 procfs_status.c --- procfs_status.c 1999/11/21 19:03:19 1.18 +++ procfs_status.c 1999/11/25 18:32:22 @@ -183,7 +183,7 @@ * Linux behaviour is to return zero-length in this case. */ - if (p->p_args && !p_trespass(curp, p)) { + if (p->p_args && (ps_argsopen || !p_trespass(curp, p))) { bp = p->p_args->ar_args; buflen = p->p_args->ar_length; buf = 0; Index: sys/proc.h =================================================================== RCS file: /home/ncvs/src/sys/sys/proc.h,v retrieving revision 1.92 diff -u -r1.92 proc.h --- proc.h 1999/11/21 19:03:20 1.92 +++ proc.h 1999/11/25 18:31:16 @@ -384,6 +384,7 @@ extern int whichidqs; /* Bit mask summary of non-empty Q's. */ extern u_long ps_arg_cache_limit; +extern int ps_argsopen; struct proc *pfind __P((pid_t)); /* Find process by id. */ struct pgrp *pgfind __P((pid_t)); /* Find process group by id. */ -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 11:50: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id E111914DBB for ; Thu, 25 Nov 1999 11:49:51 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA14315 for current@freebsd.org; Thu, 25 Nov 1999 14:54:06 -0500 From: Bill Paul Message-Id: <199911251954.OAA14315@skynet.ctr.columbia.edu> Subject: Update of if_dc driver To: current@freebsd.org Date: Thu, 25 Nov 1999 14:54:05 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3048 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, I've had a couple of reports so far about the if_dc driver which were mostly positive. I've also gotten some new hardware and did some more testing and bug fixing: - Fixed support for non-MII 10/100 cards based on the 21143 chip. This includes the DEC DE500-BA and the built-in 21143 ethernet on alpha machines. The DE500-BA is now being distributed by Cabletron. - Changed dc_attach() so that if probing for an MII-based PHY fails on 21143 cards, it will fail over to using the dcphy pseudo driver and SYM mode. - Fixed a few minor problems with autonegotiation on Macronix and PNIC II cards. - Simplified dc_pnic_rx_bug_war() a bit. Now we keep track of descriptor and mbuf indexes instead of pointers. - Compiled KLD modules for both x86 and alpha platforms using gcc 2.95.2. The driver should work correctly now with most 21143 10/100 cards. If anybody has an Adaptec, ZNYX or other multiport 21143 card, I'd be interested to know how it works with these. I've tested it with a D-Link DFE-570TX 4-port card and it seems to work well. Again, the driver is at http://www.freebsd.org/~wpaul/dc.tar.gz. If you have FreeBSD-current and a supported card, please give it a try and let me know how it holds up. Supported cards include: - Intel 21143 10/100 NICs (Kingston KNE100TX, DEC DE500-BA, D-Link DFE-570TX, Adaptec 6244 (I think), possibly ZNYX and others) - Macronix 98713, 98713A, 98715A, 98725, LC82C115 PNIC II NICs (NDC SOHOware, LinkSys LNE100TX V2.0, CNet Pro120A, CNet Pro120B, SVEC PN102TX) - ASIX AX88140A or AX88141 NICs (Alfa Inc. GFC2204, CNet Pro110B) - ADMtek AL981 Comet or AL985 Centaur - Davicom DM9102 NICs (Jaton Corporation XPressNet) - Lite-On 82c168 and 82c169 NICs (LinkSys LNE100TX, Matrox FastNIC, Kingston KNE110TX, Netgear FA310-TX Rev D1, D2 or D3) My goal is to try and get this driver into 4.0 as soon as possible so I can use it as a replacement for the al, ax, dm, pn and mx drivers. However, there's a small problem: the de driver already supports the 21143, although it does so poorly according to some people. We can't have both drivers trying to support the same chip. I want to be able to turn off 21143 support in if_de and let if_dc handle them, but I don't want to annoy people who are using if_de with 21143 cards now and not having any trouble. What do people think? Does anybody have anything against me transfering support for the 21143 from if_de to if_dc? Does anybody have a better idea? I'm open to suggestions. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 12:30: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id BC1BA14A1B for ; Thu, 25 Nov 1999 12:29:59 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Fri, 26 Nov 1999 07:22:49 +1100 Content-return: prohibited Date: Fri, 26 Nov 1999 07:29:48 +1100 From: Peter Jeremy Subject: Re: ST-506, ESDI and BAD144 ? In-reply-to: <19991125130920.10078@mojave.sitaranetworks.com> To: Greg Lehey Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov26.072249est.40323@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <33801.943436384@critter.freebsd.dk> <19991125130920.10078@mojave.sitaranetworks.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-26 05:09:20 +1100, Greg Lehey wrote: >I don't suppose it would be that big a deal to remove the old driver, >but what speaks against leaving it in the tree along with a comment in >the GENERIC config file saying "if you use antediluvial disk hardware, >you may prefer to use an old driver too"? The primary problem I can see is bitrot. There seem to be a number of fairly intrusive architecture changes coming up - block/character device merging, CardBus, `proper' thread support and SMP improvements. The WD driver will presumably live long enough to see the end of the block/character merge. The other changes seem further off, but have the potential to require changes to all drivers. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 13:29:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from shrewd.knigma.org (shrewd.demon.co.uk [212.229.151.45]) by hub.freebsd.org (Postfix) with ESMTP id BF73514E04; Thu, 25 Nov 1999 13:29:37 -0800 (PST) (envelope-from markk@knigma.org) Received: from lap.knigma.org (lap.knigma.org [10.128.148.202]) by shrewd.knigma.org (8.9.3/8.9.3) with SMTP id VAA00190; Thu, 25 Nov 1999 21:29:43 GMT (envelope-from markk@knigma.org) Message-ID: Date: Thu, 25 Nov 1999 21:29:29 +0000 To: freebsd-current@freebsd.org, freebsd-isdn@freebsd.org From: Mark Knight Subject: Panic caused by mbuf exhaustion in i4b with AVM PCI MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 4.02 U Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Repeatable mbuf leak leading to crash in current of Saturday 20th November and all snapshots I've taken prior to that since August (i.e. when I got the ISDN card). Hardware is BT Highway (AVM PCI) passive ISDN card. It's triggered when I call my ISDN number from a PSTN telephone, and use the standard example i4b answer script to play the caller a greeting. If the caller then disconnects BEFORE the outgoing message is complete, repeated use of netstat -m shows that mbufs continue to be allocated until they are all consumed after several minutes. I have reported this before (September), but this time I've got the evidence. Sorry I can't offer a fix, but if someone who knows this code could please take a look... panic: L1 avma1pp_hscx_intr: RPF, cannot allocate new mbuf! #0 boot (howto=256) at ../../kern/kern_shutdown.c:273 273 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:273 #1 0xc015fc04 in poweroff_wait (junk=0xc02724c0, howto=-1070891776) at ../../kern/kern_shutdown.c:523 #2 0xc023cc99 in avma1pp_hscx_intr (h_chan=0, stat=2164391968, sc=0xc02b7d00) at ../../i4b/layer1/i4b_avm_fritz_pci.c:1110 #3 0xc023cefd in avma1pp_hscx_int_handler (sc=0xc02b7d00) at ../../i4b/layer1/i4b_avm_fritz_pci.c:1224 #4 0xc023cfd4 in avma1pp_intr (sc=0xc02b7d00) at ../../i4b/layer1/i4b_avm_fritz_pci.c:1276 #5 0xc0237715 in intr_mux (arg=0xc04d5bc0) at ../../i386/isa/intr_machdep.c:570 =========== isdntrace controller #0 =========== started Thu Nov 25 21:22:22 1999-- NT->TE - unit:0 - frame:000001 - time:25.11 21:22:25.761050 - length:4 ------Dump:000 02 e7 01 07 ....Q921: SAP=0 (Call Control), C, TEI=115, S-Frame: RR N(R) 3 PF 1 -- TE->NT - unit:0 - frame:000002 - time:25.11 21:22:25.761050 - length:4 - -----Dump:000 02 e7 01 05 ....Q921: SAP=0 (Call Control), R, TEI=115, S-Frame: RR N(R) 2 PF 1 -- NT->TE - unit:0 - frame:000003 - time:25.11 21:22:27.601068 - length:29 -----Dump:000 02 ff 03 ...Q921: SAP=0 (Call Control), C, TEI=127, U-Frame: UI PF 0 Dump:003 08 01 01 05 a1 04 03 90 90 a3 18 01 89 1e 02 84 ................Dump:019 83 70 07 81 33 31 36 30 35 35 .p..316055Q931: pd=Q.931/I.451, cr=0x01 (from origination), message=SETUP: [sending complete] [bearer capability: cap=3.1 kHz audio std=CCITT rate=64 kbit/s mode=circuit layer1=G.711 A-law] [channel id: channel=B-1 (exclusive)] [progress ind: Std=CCITT, Loc=Public network serving remote user Description: Origination address is non-ISDN] [called party number: 316055 (type=unknown, plan=ISDN)]-- TE->NT - unit:0 - frame:000004 - time:25.11 21:22:27.601068 - length:8 ------ Dump:000 00 e7 06 04 ....Q921: SAP=0 (Call Control), C, TEI=115, I-Frame: N(S) 3 N(R) 2 P 0 Dump:004 08 01 81 07 ....Q931: pd=Q.931/I.451, cr=0x01 (from destination), message=CONNECT: - - NT->TE - unit:0 - frame:000005 - time:25.11 21:22:27.631080 - length:4 ------Dump:000 00 e7 01 08 ....Q921: SAP=0 (Call Control), R, TEI=115, S-Frame: RR N(R) 4 PF 0 -- NT->TE - unit:0 - frame:000006 - time:25.11 21:22:27.651071 - length:8 - -----Dump:000 02 e7 04 08 ....Q921: SAP=0 (Call Control), C, TEI=115, I-Frame: N(S) 2 N(R) 4 P 0 Dump:004 08 01 01 0f ....Q931: pd=Q.931/I.451, cr=0x01 (from origination), message=CONNECT ACKNOWLEDGE: -- TE->NT - unit:0 - frame:000007 - time:25.11 21:22:27.651071 - length:4 ------Dump:000 02 e7 01 06 ....Q921: SAP=0 (Call Control), R, TEI=115, S-Frame: RR N(R) 3 PF 0 -- NT->TE - unit:0 - frame:000008 - time:25.11 21:22:29.231086 - length:4 - -----Dump:000 00 fb 01 11 ....Q921: SAP=0 (Call Control), R, TEI=125, S-Frame: RR N(R) 8 PF 1 -- NT->TE - unit:0 - frame:000009 - time:25.11 21:22:30. 31093 - length:4 - -----Dump:000 00 fd 01 29 ...)Q921: SAP=0 (Call Control), R, TEI=126, S-Frame: RR N(R) 20 PF 1 -- NT->TE - unit:0 - frame:000010 - time:25.11 21:22:31.891112 - length:16 -----Dump:000 02 e7 06 08 ....Q921: SAP=0 (Call Control), C, TEI=115, I-Frame: N(S) 3 N(R) 4 P 0 Dump:004 08 01 01 45 08 02 80 90 1e 02 82 88 ...E........Q931: pd=Q.931/I.451, cr=0x01 (from origination), message=DISCONNECT: [cause: 16: Normal call clearing (Q.850) (location=user, std=CCITT)] [progress ind: Std=CCITT, Loc=Public network serving local user Description: In-band info or appropriate pattern now available]-- TE->NT - unit:0 - frame:000011 - time:25.11 21:22:31.891112 - length:8 ------Dump:000 00 e7 08 08 ....Q921: SAP=0 (Call Control), C, TEI=115, I-Frame: N(S) 4 N(R) 4 P 0 Dump:004 08 01 81 4d ...MQ931: pd=Q.931/I.451, cr=0x01 (from destination), message=RELEASE: - - NT->TE - unit:0 - frame:000012 - time:25.11 21:22:31.911119 - length:4 ------Dump:000 00 e7 01 0a ....Q921: SAP=0 (Call Control), R, TEI=115, S-Frame: RR N(R) 5 PF 0 -- NT->TE - unit:0 - frame:000013 - time:25.11 21:22:31.941114 - length:8 - -----Dump:000 02 e7 08 0a ....Q921: SAP=0 (Call Control), C, TEI=115, I-Frame: N(S) 4 N(R) 5 P 0 Dump:004 08 01 01 5a ...ZQ931: pd=Q.931/I.451, cr=0x01 (from origination), message=RELEASE COMPLETE: -- TE->NT - unit:0 - frame:000014 - time:25.11 21:22:31.941114 - length:4 ------Dump:000 02 e7 01 0a ....Q921: SAP=0 (Call Control), R, TEI=115, S-Frame: RR N(R) 5 PF 0 -- NT->TE - unit:0 - frame:000015 - time:25.11 21:22:39.231184 - length:4 - -----Dump:000 02 fb 01 11 ....Q921: SAP=0 (Call Control), C, TEI=125, S-Frame: RR N(R) 8 PF 1 -- NT->TE - unit:0 - frame:000016 - time:25.11 21:22:39.311186 - length:4 - -----Dump:000 00 fb 01 11 ....Q921: SAP=0 (Call Control), R, TEI=125, S-Frame: RR N(R) 8 PF 1 -- NT->TE - unit:0 - frame:000017 - time:25.11 21:22:40. 41192 - length:4 - -----Dump:000 02 fd 01 29 ...)Q921: SAP=0 (Call Control), C, TEI=126, S-Frame: RR N(R) 20 PF 1 -- NT->TE - unit:0 - frame:000018 - time:25.11 21:22:40.111194 - length:4 - -----Dump:000 00 fd 01 29 ...)Q921: SAP=0 (Call Control), R, TEI=126, S-Frame: RR N(R) 20 PF 1 -- NT->TE - unit:0 - frame:000019 - time:25.11 21:22:41.971211 - length:4 - -----Dump:000 02 e7 01 0b ....Q921: SAP=0 (Call Control), C, TEI=115, S-Frame: RR N(R) 5 PF 1 -- TE->NT - unit:0 - frame:000020 - time:25.11 21:22:41.971211 - length:4 - -----Dump:000 02 e7 01 0b ....Q921: SAP=0 (Call Control), R, TEI=115, S-Frame: RR N(R) 5 PF 1 machine i386 cpu I386_CPU cpu I486_CPU cpu I586_CPU cpu I686_CPU ident SHREWD maxusers 64 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options PANIC_REBOOT_WAIT_TIME=-1 # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 #controller pnp0 # PnP support for ISA #controller eisa0 controller pci0 # Floppy drives controller fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # IDE controller and disks #controller wdc0 at isa? port IO_WD1 irq 14 #device wd0 at wdc0 drive 0 #device wd1 at wdc0 drive 1 #controller wdc1 at isa? port IO_WD2 irq 15 #device wd2 at wdc1 drive 0 #device wd3 at wdc1 drive 1 # ATAPI devices on wdc? #device wcd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) #device wst0 #IDE Tape (e.g. Travan) # The 'ATA' driver supports all ATA and ATAPI devices. # It can reuse the majors of wd.c for booting purposes. # You only need one "controller ata0" for it to find all # PCI ATA/ATAPI devices on modern machines. #controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives #device atapifd0 # ATAPI floppy drives #device atapist0 # ATAPI tape drives #The folliwing options are valid on the ATA driver: # # ATA_STATIC_ID: controller numbering is static (like the old driver) # else the device numbers are dynamically allocated. # ATA_ENABLE_ATAPI_DMA: enable DMA on ATAPI device, since many ATAPI devices # claim to support DMA but doesn't actually work, this # is not enabled as default. # ATA_16BIT_ONLY: for older HW that doesn't support 32bit transfers on # the ATA channels (mostly old ISA boards). #options ATA_STATIC_ID options ATA_ENABLE_ATAPI_DMA #options ATA_16BIT_ONLY # # For older non-PCI systems, this is the lines to use: controller ata0 at isa? port IO_WD1 irq 14 controller ata1 at isa? port IO_WD2 irq 15 # SCSI Controllers # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. #controller ncr0 # NCR/Symbios Logic #controller ahb0 # EISA AHA1742 family controller ahc0 # AHA2940 and onboard AIC7xxx devices #options AHC_ALLOC_MEMIO #controller amd0 # AMD 53C974 (Teckram DC-390(T)) #controller isp0 # Qlogic family #controller dpt0 # DPT Smartcache - See LINT for options! #controller adv0 at isa? port ? irq ? #controller adw0 #controller bt0 at isa? port ? irq ? #controller aha0 at isa? port ? irq ? # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. controller scbus0 # SCSI bus (required) #device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI access) # Proprietary or custom CD-ROM Interfaces #device wt0 at isa? port 0x300 irq 5 drq 1 #device mcd0 at isa? port 0x300 irq 10 #device matcd0 at isa? port 0x230 #device scd0 at isa? port 0x230 # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at isa? #device pcic1 at isa? # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 # Parallel port bus (required) device lpt0 # Printer #device plip0 # TCP/IP over parallel device ppi0 # Parallel port interface device #controller vpo0 # Requires scbus and da0 # PCI Ethernet NICs. #device ax0 # ASIX AX88140A #device de0 # DEC/Intel DC21x4x (``Tulip'') #device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) #device pn0 # Lite-On 82c168/82c169 (``PNIC'') #device tx0 # SMC 9432TX (83c170 ``EPIC'') #device vx0 # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. #controller miibus0 # MII bus support #device al0 # ADMtek AL981/AN985 (``Comet''/``Centaur'') #device dm0 # Davicom DM9100/DM9102 #device mx0 # Macronix 98713/98715/98725 (``PMAC'') #device rl0 # RealTek 8129/8139 #device sf0 # Adaptec AIC-6915 (``Starfire'') #device sis0 # Silicon Integrated Systems SiS 900/SiS 7016 #device ste0 # Sundance ST201 (D-Link DFE-550TX) #device tl0 # Texas Instruments ThunderLAN #device vr0 # VIA Rhine, Rhine II #device wb0 # Winbond W89C840F #device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 #device ex0 at isa? port? irq? #device ep0 # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device fe0 at isa? port 0x300 irq ? #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 irq ? # requires PCCARD (PCMCIA) support to be activated #device xe0 at isa? port? irq ? # PCCARD NIC drivers. # ze and zp take over the pcic and cannot coexist with generic pccard # support, nor the ed and ep drivers they replace. #device ze0 at isa? port 0x300 irq 10 iomem 0xd8000 #device zp0 at isa? port 0x300 irq 10 iomem 0xd8000 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support #controller uhci0 # UHCI PCI->USB interface #controller ohci0 # OHCI PCI->USB interface #controller usb0 # USB Bus (required) #device ugen0 # Generic #device uhid0 # "Human Interface Devices" #device ukbd0 # Keyboard #device ulpt0 # Printer #controller umass0 # Disks/Mass storage - Requires scbus and da0 #device ums0 # Mouse # ISDN stuff options "AVM_A1_PCI" device isic0 pseudo-device "i4bq921" # i4b layer 2 pseudo-device "i4bq931" # i4b layer 3 pseudo-device "i4b" # i4b layer 4 pseudo-device "i4btrc" 4 # Passive card ISDN tracing pseudo-device "i4bctl" # Main userland i4b controller pseudo-device "i4brbch" 4 # Userland raw B channel access pseudo-device "i4btel" 2 # userland telephony driver pseudo-device "i4bipr" 4 # IP over raw HDLC ISDN options IPR_VJ # VJ for ipr pseudo-device "i4bisppp" 4 # sync PPP over ISDN pseudo-device sppp # Generic Synchronous PPP options NMBCLUSTERS=2048 Best regards, -- Mark Knight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 14:11:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id C06F214DCB; Thu, 25 Nov 1999 14:11:17 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id XAA12659; Thu, 25 Nov 1999 23:10:35 +0100 (CET) Message-Id: <199911252210.XAA12659@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Mark Knight Cc: freebsd-current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Subject: Re: Panic caused by mbuf exhaustion in i4b with AVM PCI Reply-To: Gary Jennejohn In-reply-to: Your message of "Thu, 25 Nov 1999 21:29:29 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Nov 1999 23:10:35 +0100 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Knight writes: >Repeatable mbuf leak leading to crash in current of Saturday 20th >November and all snapshots I've taken prior to that since August (i.e. >when I got the ISDN card). > Are you using the code in -current or one of the releases ? Makes a difference. Can you a) increase the size of the message buffer in your config file (options MSGBUF_SIZE=81920, for example) b) turn on ALL the trace in the kernel with isdndebug c) cause the panic to happen again and get a crash dump ? It would also be good if you could run isdntrace in parallel so that there's some correlation between the kernel messages and the trace times. With the larger message buffer it's possible to see what was happening around the time of the crash (I used this method to debug a panic caused by a stack overflow). There's a way to read the msgbuf from the crash dump, but I can't remember what it is right now :( If all else fails, gdb should be able to do it. I can only guess, but it looks like the user-land process isn't told about the hangup and keeps sending packets down the line. The packets never go out (no connection), so the mbufs eventually run out. The raw interface evidently doesn't have the safety belts that the other interfaces (like ipr, isppp) have. --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 14:20:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from shrewd.knigma.org (shrewd.demon.co.uk [212.229.151.45]) by hub.freebsd.org (Postfix) with ESMTP id EF57714DCB for ; Thu, 25 Nov 1999 14:20:27 -0800 (PST) (envelope-from markk@knigma.org) Received: from lap.knigma.org (lap.knigma.org [10.128.148.202]) by shrewd.knigma.org (8.9.3/8.9.3) with SMTP id WAA00553 for ; Thu, 25 Nov 1999 22:20:37 GMT (envelope-from markk@knigma.org) Message-ID: <65tPkBAcYbP4EwVg@knigma.org> Date: Thu, 25 Nov 1999 22:20:12 +0000 To: freebsd-current@freebsd.org From: Mark Knight Subject: Re: Panic caused by mbuf exhaustion in i4b with AVM PCI References: <199911252210.XAA12659@peedub.muc.de> In-Reply-To: <199911252210.XAA12659@peedub.muc.de> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 4.02 U Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199911252210.XAA12659@peedub.muc.de>, Gary Jennejohn writes >Are you using the code in -current or one of the releases ? Makes a >difference. cvsup'd current from Saturday morning. >Can you a) increase the size of the message buffer in your config file >(options MSGBUF_SIZE=81920, for example) b) turn on ALL the >trace in the kernel with isdndebug c) cause the panic to happen again >and get a crash dump ? I'll give this a go. >It would also be good if you could run isdntrace in parallel so that >there's some correlation between the kernel messages and the trace times. I did include that in my earlier post - in case you missed it... >I can only guess, but it looks like the user-land process isn't told >about the hangup and keeps sending packets down the line. The packets >never go out (no connection), so the mbufs eventually run out. The >raw interface evidently doesn't have the safety belts that the other >interfaces (like ipr, isppp) have. I've tried killing the user land daemon and the growth continues. Latest finding. Once the run-away has started, another incoming call allowed to complete with FreeBSD performing the clear down results in all mbufs being freed and stability returning. -- Mark Knight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 14:26:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id DEC8714C94 for ; Thu, 25 Nov 1999 14:26:45 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id PAA00144; Thu, 25 Nov 1999 15:16:08 -0700 (MST) Date: Thu, 25 Nov 1999 15:16:08 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199911252216.PAA00144@narnia.plutotech.com> To: Gianmarco Giovannelli Cc: current@FreeBSD.org Subject: Re: AHC0 fireworks ? X-Newsgroups: pluto.freebsd.current In-Reply-To: <4.2.0.58.19991120091815.00c2ced0@194.184.65.4> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <4.2.0.58.19991120091815.00c2ced0@194.184.65.4> you wrote: > Hi, > I am running 4.0-current of: > FreeBSD gmarco.eclipse.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Nov 18 > 09:33:43 CET > 1999 gmarco@gmarco.eclipse.org:/usr/src/sys/compile/GMARCO i386 > > But I have now a lot of errors (as you can see in this logs) on my scsi chain. > I had never experienced such things in the near past (even if as an old > current user sometimes I see also worse things :-) > > Btw I don't see in the current mailing list threads about iussues on the > scsi subsystem recently so it can be a problem related to my hardware (even > if I didn't experience it before)... > > I append the logs of my system (sorry for the long post): > > Now I am trying to make a "blind" make world to see it changes something... Parity errors indicate that data integrity is compromised on your SCSI cable. Perhaps you bumped a connector, or a connector had been loose for a long time and has just shifted to the point of causing a failure. Open your case, reseat everything and see if the problem clears up. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 14:38:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from shrewd.knigma.org (shrewd.demon.co.uk [212.229.151.45]) by hub.freebsd.org (Postfix) with ESMTP id CC34D14D21; Thu, 25 Nov 1999 14:37:15 -0800 (PST) (envelope-from markk@knigma.org) Received: from lap.knigma.org (lap.knigma.org [10.128.148.202]) by shrewd.knigma.org (8.9.3/8.9.3) with SMTP id WAA00280; Thu, 25 Nov 1999 22:37:22 GMT (envelope-from markk@knigma.org) Message-ID: Date: Thu, 25 Nov 1999 22:36:01 +0000 To: freebsd-current@freebsd.org, freebsd-isdn@freebsd.org From: Mark Knight Subject: Re: Panic caused by mbuf exhaustion in i4b with AVM PCI References: <199911252210.XAA12659@peedub.muc.de> In-Reply-To: <199911252210.XAA12659@peedub.muc.de> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 4.02 U Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199911252210.XAA12659@peedub.muc.de>, Gary Jennejohn writes >Can you a) increase the size of the message buffer in your config file >(options MSGBUF_SIZE=81920, for example) b) turn on ALL the >trace in the kernel with isdndebug c) cause the panic to happen again >and get a crash dump ? And here it is... This represents a single call into i4b, clearing down part way through the outgoing message. I did't leave it to panic but that would have only been a matter of time. Mounting root from ufs:/dev/ad0a i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L3-i4b_decode_q931: Call Ref, len 1, val 1, flag 0 i4b-L4-reserve_cd: found free cd - index=0 cdid=1 i4b-L3-rx SETUP: unit 0, cr = 0x01 i4b-L3-i4b_decode_q931_cs0_ie: IEI_SENDCOMPL i4b-L3-i4b_decode_q931_cs0_ie: IEI_BEARERCAP - Telephony i4b-L3-i4b_decode_q931_cs0_ie: IEI_CHANNELID - channel 1, exclusive = 1 i4b-L3-i4b_decode_q931_cs0_ie: IEI_PROGRESSINDICATOR i4b-L3-i4b_decode_q931_cs0_ie: IEI_CALLED = 316055 i4b-L3-next_l3state: L3 FSM event [EV_SETUP - rxd SETUP]: [ST_U0 - Null => ST_U6 - In Pres] i4b-L3-F_00H: FSM function F_00H executing i4b-L4-T400_start: cr = 1 i4b-L4-cd_by_cdid: found cdid - index=0 cdid=1 cr=1 i4b-L4-T400_stop: cr = 1 i4b-L4-i4bioctl: I4B_CONNECT_RESP max_idle_time set to 5 seconds i4b-L4-cd_by_cdid: found cdid - index=0 cdid=1 cr=1 i4b-L4-T400_stop: cr = 1 i4b-L3-next_l3state: L3 FSM event [EV_SETACRS - L4 accept RSP]: [ST_U6 - In Pres => ST_SUSE - Subroutine sets state] i4b-L3-F_06E: FSM function F_06E executing i4b-L2-DL-ESTABLISH-REQ: unit 0 i4b-L2-i4b_next_l2state: FSM event [EV_DLESTRQ]: [ST_TEI_UNAS/0 => ST_EST_AW_TEI/2] i4b-L2-F_TU01: FSM function F_TU01 executing i4b-L2-MDL-ASSIGN-IND: unit 0 i4b-L2-i4b_tei_assign: tx TEI ID_Request i4b-L2-i4b_T202_start: unit 0 i4b-L1-ph_data_req: ISAC_TX_ACTIVE set i4b-L3-T313_start: cr = 1 i4b-L1-isic_isac_irq: unit 0: ista = 0x10 i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L2-i4b_T202_stop: unit 0 i4b-L3-i4b_mdl_status_ind: unit = 0, status = 3, parm = 115 i4b-L3-i4b_mdl_status_ind: STI_TEIASG: unit 0 TEI = 115 = 0x73 i4b: unit 0, assigned TEI = 115 = 0x73 i4b-L2-i4b_tei_rx_frame: TEI ID Assign - TEI = 115 i4b-L2-i4b_next_l2state: FSM event [EV_MDASGRQ]: [ST_EST_AW_TEI/2 => ST_AW_EST/4] i4b-L2-F_TE03: FSM function F_TE03 executing i4b-L2-i4b_tx_sabme: tx SABME, tei = 115 i4b-L1-ph_data_req: ISAC_TX_ACTIVE set i4b-L2-i4b_T200_restart: unit 0 i4b-L1-isic_isac_irq: unit 0: ista = 0x10 i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L2-i4b_rxd_u_frame: UA, sapi = 0, tei = 115 i4b-L2-F_AE09: FSM function F_AE09 executing i4b-L3-i4b_mdl_status_ind: unit = 0, status = 2, parm = 1 i4b-L3-i4b_mdl_status_ind: STI_L2STAT: unit 0 layer 2 = up i4b-L2-i4b_T200_stop: unit 0 i4b-L2-i4b_next_l2state: FSM S-event [EV_RXUA]: [ST_AW_EST => ST_MULTIFR] i4b-L2-i4b_next_l2state: FSM executing postfsmfunc! i4b-L2-DL-ESTABLISH-CONF: unit 0 i4b-L3-i4b_dl_establish_cnf: unit=0, index=0 cdid=1 cr=1 i4b-L3-next_l3state: L3 FSM event [EV_DLESTCF - L2 DL_Est_Cnf]: [ST_IWA - In Wait EST-Accept => ST_U8 - In ConReq] i4b-L3-F_DECF2: FSM function F_DECF2 executing i4b-L3-tx CONNECT: unit 0, cr = 0x01 i4b-L1-ph_data_req: ISAC_TX_ACTIVE set i4b-L2-i4b_T200_start: unit 0 i4b-L1-isic_isac_irq: unit 0: ista = 0x10 i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L2-i4b_rxd_s_frame: rx'd RR, N(R) = 1 i4b-L2-F_MF17: FSM function F_MF17 executing i4b-L2-i4b_T200_stop: unit 0 i4b-L2-i4b_next_l2state: FSM S-event [EV_RXRR]: [ST_MULTIFR => ST_MULTIFR] i4b-L1-isic_isac_irq: unit 0: ista = 0x81 i4b-L1-isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow i4b-L3-i4b_decode_q931: Call Ref, len 1, val 1, flag 0 i4b-L4-cd_by_unitcr: found cd, index=0 cdid=1 cr=1 i4b-L3-rx CONNECT-ACK: unit 0, cr = 0x01 i4b-L3-next_l3state: L3 FSM event [EV_CONACK - rxd CONN ACK]: [ST_U8 - In ConReq => ST_U10 - Active] i4b-L3-F_08R: FSM function F_08R executing i4b-L3-T313_stop: cr = 1 i4b-L4-i4b_l4_connect_active_ind: last_active/connect_time=943568877 i4b-L1-avma1pp_bchannel_setup: unit=0, channel=1, activate i4b-L1-avma1pp_hscx_init: unit=0, channel=1, activate i4b-L1-avma1pp_hscx_init: BPROT_NONE?? i4b-L4-i4b_l4_setup_timeout: 943568877: direction 1, shorthold algorithm 0 i4b-L4-i4b_l4_setup_timeout: 943568877: incoming-call, setup max_idle_time to 5 i4b-L2-i4b_tx_rr_response: tx RR, unit = 0 i4b-L1-ph_data_req: ISAC_TX_ACTIVE set i4b-L2-i4b_T200_stop: unit 0 i4b-L1-isic_isac_irq: unit 0: ista = 0x10 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L4-i4b_idle_check: 943568877: incoming-call, activity, last_active=943568877, max_idle=5 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L4-i4b_idle_check: 943568878: incoming-call, activity, last_active=943568878, max_idle=5 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L4-i4b_idle_check: 943568878: incoming-call, activity, last_active=943568878, max_idle=5 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L4-i4b_idle_check: 943568879: incoming-call, activity, last_active=943568879, max_idle=5 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L4-i4b_idle_check: 943568879: incoming-call, activity, last_active=943568879, max_idle=5 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L4-i4b_idle_check: 943568880: incoming-call, activity, last_active=943568880, max_idle=5 i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L4-i4b_idle_check: 943568880: incoming-call, activity, last_active=943568880, max_idle=5 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L4-i4b_idle_check: 943568881: incoming-call, activity, last_active=943568881, max_idle=5 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L4-i4b_idle_check: 943568881: incoming-call, activity, last_active=943568881, max_idle=5 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L4-i4b_idle_check: 943568882: incoming-call, activity, last_active=943568882, max_idle=5 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L4-i4b_idle_check: 943568882: incoming-call, activity, last_active=943568882, max_idle=5 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L3-i4b_decode_q931: Call Ref, len 1, val 1, flag 0 i4b-L4-cd_by_unitcr: found cd, index=0 cdid=1 cr=1 i4b-L3-rx DISCONNECT: unit 0, cr = 0x01 i4b-L3-i4b_decode_q931_cs0_ie: IEI_CAUSE = 16 i4b-L3-i4b_decode_q931_cs0_ie: IEI_PROGRESSINDICATOR i4b-L3-next_l3state: L3 FSM event [EV_DISCONN - rxd DISC]: [ST_U10 - Active => ST_U12 - Disc Ind] i4b-L3-F_DISC: FSM function F_DISC executing i4b-L3-T303_stop: cr = 1 i4b-L3-T305_stop: cr = 1 i4b-L3-T308_stop: cr = 1 i4b-L3-T309_stop: cr = 1 i4b-L3-T310_stop: cr = 1 i4b-L3-T313_stop: cr = 1 i4b-L3-tx RELEASE: unit 0, cr = 0x01 i4b-L1-ph_data_req: ISAC_TX_ACTIVE set i4b-L2-i4b_T200_start: unit 0 i4b-L3-T308_start: cr = 1 i4b-L1-isic_isac_irq: unit 0: ista = 0x90 i4b-L2-i4b_rxd_s_frame: rx'd RR, N(R) = 2 i4b-L2-F_MF17: FSM function F_MF17 executing i4b-L2-i4b_T200_stop: unit 0 i4b-L2-i4b_next_l2state: FSM S-event [EV_RXRR]: [ST_MULTIFR => ST_MULTIFR] i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L3-i4b_decode_q931: Call Ref, len 1, val 1, flag 0 i4b-L4-cd_by_unitcr: found cd, index=0 cdid=1 cr=1 i4b-L3-rx RELEASE-COMPLETE: unit 0, cr = 0x01 i4b-L3-next_l3state: L3 FSM event [EV_RELCOMP - rxd REL COMPL]: [ST_U12 - Disc Ind => ST_U0 - Null] i4b-L3-F_RELCP: FSM function F_RELCP executing i4b-L3-T303_stop: cr = 1 i4b-L3-T305_stop: cr = 1 i4b-L3-T308_stop: cr = 1 i4b-L3-T309_stop: cr = 1 i4b-L3-T310_stop: cr = 1 i4b-L3-T313_stop: cr = 1 i4b-L1-avma1pp_hscx_init: unit=0, channel=1, deactivate i4b-L1-avma1pp_bchannel_setup: unit=0, channel=1, deactivate i4b-L4-freecd_by_cd: releasing cd - index=0 cdid=1 cr=1 i4b-L2-i4b_tx_rr_response: tx RR, unit = 0 i4b-L1-ph_data_req: ISAC_TX_ACTIVE set i4b-L2-i4b_T200_stop: unit 0 i4b-L1-isic_isac_irq: unit 0: ista = 0x10 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L1-avma1pp_hscx_intr: receive data overflow i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L1-isic_isac_irq: unit 0: ista = 0x80 i4b-L1-avma1pp_hscx_intr: receive data overflow -- Mark Knight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 16:13:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id B4AFE14D37 for ; Thu, 25 Nov 1999 16:13:47 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id BAA11103; Fri, 26 Nov 1999 01:13:56 +0100 (CET) (envelope-from assar) To: freebsd-current@FreeBSD.ORG Subject: 3c509b getting `eeprom failed to come ready' in current From: Assar Westerlund Date: 26 Nov 1999 01:13:56 +0100 Message-ID: <5l903mqfcr.fsf@foo.sics.se> Lines: 36 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. When upgrading a box from current ~ 1999-11-15 to ~ today, the 3c509b network interface fails to work. These are the kernels (the first one working, the second one not). /kernel.old: FreeBSD 4.0-CURRENT #1: Mon Nov 15 00:03:00 CET 1999 /kernel: FreeBSD 4.0-CURRENT #0: Fri Nov 26 00:05:43 CET 1999 The first one has this configuration line for ep: device ep0 at isa? port 0x300 irq 10 and the card gets attached as follows: 1 3C5x9 board(s) on ISA found at 0x300 ep0 at port 0x300-0x30f irq 10 on isa0 ep0: aui/utp/bnc[*UTP*] address 00:a0:24:77:5d:eb when running today's GENERIC kernel I get this instead: ep0: <3Com EtherLink III (3c509-Combo)> at port 0x300-0x30f irq 9 on isa0 ep0: eeprom failed to come ready ... Ethernet address ff:ff:ff:ff:ff:ff (which is totally bogus, of course). I've tried both with PnP disabled and enabled in the BIOS. Any hints and/or suggestions? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 16:26: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 57BB514BCA for ; Thu, 25 Nov 1999 16:26:01 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id BAA01517; Fri, 26 Nov 1999 01:25:29 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Assar Westerlund Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current In-reply-to: Your message of "26 Nov 1999 01:13:56 +0100." <5l903mqfcr.fsf@foo.sics.se> Date: Fri, 26 Nov 1999 01:25:29 +0100 Message-ID: <1515.943575929@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't use the generic kernel unchanged with the 3com card. Disable the ex0 and ie0 drivers, one of those pummel the 3com cards magic config registers. >ep0: <3Com EtherLink III (3c509-Combo)> at port 0x300-0x30f irq 9 on isa0 >ep0: eeprom failed to come ready >... >Ethernet address ff:ff:ff:ff:ff:ff > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 16:30: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 0E5EA14BCA; Thu, 25 Nov 1999 16:30:00 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id QAA28965; Thu, 25 Nov 1999 16:23:21 -0800 (PST) Date: Thu, 25 Nov 1999 16:23:21 -0800 (PST) From: Annelise Anderson To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: calcru() warnings... In-Reply-To: <36187.943470027@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Nov 1999, Poul-Henning Kamp wrote: > > I still hear reports of sporadic calcru() warnings. > > If any of you see these, could you try to see if they correlate > to the uptime of the machine in question ? Since I replaced a September 15 -current with October 14 -current, I get lots of these within 24 or 48 hours of booting. Setting kern.timecounter.method to 1 does stop them. SMP, two PII-400's. Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 16:40:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 9EE4D14C8F; Thu, 25 Nov 1999 16:40:28 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id TAA01763; Thu, 25 Nov 1999 19:40:18 -0500 (EST) Date: Thu, 25 Nov 1999 19:40:17 -0500 (EST) From: Bosko Milekic To: Gary Jennejohn Cc: Mark Knight , freebsd-current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Subject: Re: Panic caused by mbuf exhaustion in i4b with AVM PCI In-Reply-To: <199911252210.XAA12659@peedub.muc.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 25 Nov 1999, Gary Jennejohn wrote: !>I can only guess, but it looks like the user-land process isn't told !>about the hangup and keeps sending packets down the line. The packets !>never go out (no connection), so the mbufs eventually run out. The !>raw interface evidently doesn't have the safety belts that the other !>interfaces (like ipr, isppp) have. Out of curiosity, is anything regarding the exhaustion of mb_map being logged to /var/log/messages ? If not, chances are that this is not directly related to an mbuf exhaustion -- the panic, that is, because if mb_map hasn't even been exhausted, then you still potentially have space to allocate from (this is the way it presently works) and the panic is unlikely to be related to an mbuf pointer being NULL and mis-treated. -- Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 16:47:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 4262714C8F for ; Thu, 25 Nov 1999 16:47:48 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id BAA11168; Fri, 26 Nov 1999 01:47:57 +0100 (CET) (envelope-from assar) To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current References: <1515.943575929@critter.freebsd.dk> From: Assar Westerlund Date: 26 Nov 1999 01:47:55 +0100 In-Reply-To: Poul-Henning Kamp's message of "Fri, 26 Nov 1999 01:25:29 +0100" Message-ID: <5lln7mhydg.fsf@foo.sics.se> Lines: 11 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > Don't use the generic kernel unchanged with the 3com card. > > Disable the ex0 and ie0 drivers, one of those pummel the 3com > cards magic config registers. Tack. Now it manages to find ep0 properly. It still finds a `ghost' ep1 and hangs hard when trying to `ifconfig ep0'. Any idea as to why that happens? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 16:50: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2C83D14C8F for ; Thu, 25 Nov 1999 16:49:57 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id BAA01680; Fri, 26 Nov 1999 01:49:26 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Assar Westerlund Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current In-reply-to: Your message of "26 Nov 1999 01:47:55 +0100." <5lln7mhydg.fsf@foo.sics.se> Date: Fri, 26 Nov 1999 01:49:26 +0100 Message-ID: <1678.943577366@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5lln7mhydg.fsf@foo.sics.se>, Assar Westerlund writes: >Poul-Henning Kamp writes: >> Don't use the generic kernel unchanged with the 3com card. >> >> Disable the ex0 and ie0 drivers, one of those pummel the 3com >> cards magic config registers. > >Tack. Now it manages to find ep0 properly. It still finds a `ghost' >ep1 and hangs hard when trying to `ifconfig ep0'. Any idea as to why >that happens? no. Try to disable ep1 (if you can). -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 16:59:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 2AB9814C8F for ; Thu, 25 Nov 1999 16:59:55 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id CAA11293; Fri, 26 Nov 1999 02:00:03 +0100 (CET) (envelope-from assar) To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current References: <1678.943577366@critter.freebsd.dk> From: Assar Westerlund Date: 26 Nov 1999 02:00:00 +0100 In-Reply-To: Poul-Henning Kamp's message of "Fri, 26 Nov 1999 01:49:26 +0100" Message-ID: <5ld7syhxtb.fsf@foo.sics.se> Lines: 27 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > no. Try to disable ep1 (if you can). Not hardwiring ep0 in the configuration file made it work. Thanks again. Here's an trivial patch to GENERIC to add comments about these characteristics about ep0. /assar Index: GENERIC =================================================================== RCS file: /afs/stacken.kth.se/ftp/pub/FreeBSD/development/FreeBSD-CVS/src/sys/i386/conf/GENERIC,v retrieving revision 1.199 diff -u -w -r1.199 GENERIC --- GENERIC 1999/11/01 04:02:56 1.199 +++ GENERIC 1999/11/26 00:59:19 @@ -183,6 +183,8 @@ device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 device ex0 at isa? port? irq? device ep0 +# don't try to hardware ep0 - it will not work +# ep0 is not compatible with ex0 and ie0 # The probe order of these is presently determined by i386/isa/isa_compat.c. device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 device fe0 at isa? port 0x300 irq ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 17: 1:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2B95D14E2F; Thu, 25 Nov 1999 17:01:41 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA18379; Thu, 25 Nov 1999 18:01:40 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA00614; Thu, 25 Nov 1999 18:01:20 -0700 (MST) Message-Id: <199911260101.SAA00614@harmony.village.org> To: Poul-Henning Kamp Subject: Re: ps on 4.0-current Cc: freebsd-current@freebsd.org, security@freebsd.org In-reply-to: Your message of "Thu, 25 Nov 1999 19:53:28 +0100." <786.943556008@critter.freebsd.dk> References: <786.943556008@critter.freebsd.dk> Date: Thu, 25 Nov 1999 18:01:20 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <786.943556008@critter.freebsd.dk> Poul-Henning Kamp writes: : As I've understood the conclusion of this thread, we want a : sysctl, and we want it open as default. This patch should : do that. : : Once Warner nods in the vertical direction it will be committed. The head is oscillating with and against the gravity well of the planet earth while I'm in the standing position. Looks good to me. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 17:11:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id 4320E14D1A for ; Thu, 25 Nov 1999 17:11:08 -0800 (PST) (envelope-from dakuntz@home.com) Received: from windows ([24.2.16.41]) by mail.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19991126011107.GBJO28353.mail.rdc1.tn.home.com@windows> for ; Thu, 25 Nov 1999 17:11:07 -0800 Message-ID: <000c01bf37ab$8d605820$29100218@micronetinfo.com> From: "Douglas Kuntz" To: References: <199911240747.AAA18880@harmony.village.org> <199911240758.JAA96963@zibbi.mikom.csir.co.za> <19991124071946.G49362@dragon.nuxi.com> <19991124113139.D264@spirit.jaded.net> <19991124084304.B77698@dragon.nuxi.com> <19991124115405.E264@spirit.jaded.net> Subject: Boot error Date: Thu, 25 Nov 1999 20:14:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Before I go do a fresh SNAP install, I wanted to see if there was an easier way to fix this problem... My -current box was a celeron...I had to switch the celeron and mboard to my windoze machine to get a vidcard werkin...I recompiled the kernel to 486, 586, and 686, and moved the HD, the cards, etc, over to the K6-2 400 I had...now, everytime at boot, before it even prompts for which OS to start, it has a bootloader problem...if I recall it was something like: BTX 1.0.0 BTX Loader 1.0.1 then "System Halted" I tried the fixit floppy, etc, and that partially worked, but locked when it was mounting the filesystem. I'm sorry that I cant provide any more info...I only have 1 monitor and cant copy/paste between 2 pcs. Thanks in advance Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 17:29:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 2DC0314DF1 for ; Thu, 25 Nov 1999 17:29:25 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA71122; Thu, 25 Nov 1999 17:29:25 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA21772; Thu, 25 Nov 1999 17:29:24 -0800 (PST) (envelope-from obrien) Date: Thu, 25 Nov 1999 17:29:24 -0800 From: "David O'Brien" To: Assar Westerlund Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current Message-ID: <19991125172924.A21697@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <1678.943577366@critter.freebsd.dk> <5ld7syhxtb.fsf@foo.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <5ld7syhxtb.fsf@foo.sics.se>; from assar@sics.se on Fri, Nov 26, 1999 at 02:00:00AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Not hardwiring ep0 in the configuration file made it work. Thanks > again. ... > +# don't try to hardware ep0 - it will not work If we don't hardware it in GENERIC, then why do people think they should be doing so? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 17:32:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 9851314BE6; Thu, 25 Nov 1999 17:32:36 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id CAA11415; Fri, 26 Nov 1999 02:32:44 +0100 (CET) (envelope-from assar) To: obrien@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current References: <1678.943577366@critter.freebsd.dk> <5ld7syhxtb.fsf@foo.sics.se> <19991125172924.A21697@dragon.nuxi.com> From: Assar Westerlund Date: 26 Nov 1999 02:32:43 +0100 In-Reply-To: "David O'Brien"'s message of "Thu, 25 Nov 1999 17:29:24 -0800" Message-ID: <5lu2maghqc.fsf@foo.sics.se> Lines: 13 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" writes: > > +# don't try to hardware ep0 - it will not work > > If we don't hardware it in GENERIC, then why do people think they should > be doing so? (s/hardware/hardwire/ of course) there's (to my mind) a difference between it's not done by default and it will not work. I did it because I had hardwired it in my previous config. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 18:37:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 3D56014C9E for ; Thu, 25 Nov 1999 18:37:13 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id SAA78405 for ; Thu, 25 Nov 1999 18:37:12 -0800 (PST) Date: Thu, 25 Nov 1999 18:37:12 -0800 (PST) From: Julian Elischer To: current@freebsd.org Subject: Which is the truth? (sycalls and traps) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG in src/lib/libc/i386/SYS.h we see: #ifdef __ELF__ #define KERNCALL int $0x80 /* Faster */ #else #define KERNCALL LCALL(7,0) /* The old way */ #endif and in /usr/src/sys/i386/i386/exception.s we see: /* * Call gate entry for syscall. * The intersegment call has been set up to specify one dummy parameter. * This leaves a place to put eflags so that the call frame can be * converted to a trap frame. Note that the eflags is (semi-)bogusly * pushed into (what will be) tf_err and then copied later into the * final spot. It has to be done this way because esp can't be just * temporarily altered for the pushfl - an interrupt might come in * and clobber the saved cs/eip. */ * converted to a trap frame. Note that the eflags is (semi-)bogusly * pushed into (what will be) tf_err and then copied later into the * final spot. It has to be done this way because esp can't be just * temporarily altered for the pushfl - an interrupt might come in * and clobber the saved cs/eip. */ SUPERALIGN_TEXT IDTVEC(syscall) pushfl /* save eflags in tf_err for now */ subl $4,%esp /* skip over tf_trapno */ pushal pushl %ds pushl %es pushl %fs movl $KDSEL,%eax /* switch to kernel segments */ movl %ax,%ds movl %ax,%es MOVL_KPSEL_EAX movl %ax,%fs movl TF_ERR(%esp),%eax /* copy saved eflags to final spot */ movl %eax,TF_EFLAGS(%esp) movl $7,TF_ERR(%esp) /* sizeof "lcall 7,0" */ FAKE_MCOUNT(13*4(%esp)) MPLOCKED incl _cnt+V_SYSCALL SYSCALL_LOCK call _syscall /* * Return via _doreti to handle ASTs. */ pushl $0 /* cpl to restore */ subl $4,%esp /* dummy unit to finish intr frame */ movb $1,_intr_nesting_level MEXITCOUNT jmp _doreti /* * Call gate entry for Linux/NetBSD syscall (int 0x80) */ SUPERALIGN_TEXT IDTVEC(int0x80_syscall) subl $8,%esp /* skip over tf_trapno and tf_err */ pushal pushl %ds pushl %es pushl %fs movl $KDSEL,%eax /* switch to kernel segments */ movl %ax,%ds movl %ax,%es MOVL_KPSEL_EAX movl %ax,%fs movl $2,TF_ERR(%esp) /* sizeof "int 0x80" */ FAKE_MCOUNT(13*4(%esp)) MPLOCKED incl _cnt+V_SYSCALL ALTSYSCALL_LOCK call _syscall /* * Return via _doreti to handle ASTs. */ pushl $0 /* cpl to restore */ subl $4,%esp /* dummy unit to finish intr frame */ movb $1,_intr_nesting_level MEXITCOUNT jmp _doreti Now, since teh code doesn't lie (one hopes) I would PRESUME that the first handler is only used for old a.out binaries, and the second is now the default entrypoint for syscalls which would lead me to believe that the comment about Linux and NetBSD is now incorrect and out of date... Am I reading this right? (I could imagin that someone could come to me and say "no, because we aren't even using that file any more" or something. There's a lot of cruft here that makes things hard to understand.) Am I also right in assuming that all the registers that the user was running when they did the KERNCALL have been saved on the KERNEL stack by the time that the above routines are called? (It's a pitty because if they were saved on the USER stack before teh kernel switched to the kernel stack it would have a great simplifying effect on kernel threads support :-) (I know that could lead to traps during saving the context but..) Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 20:53:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (Postfix) with SMTP id 6868014C36 for ; Thu, 25 Nov 1999 20:53:41 -0800 (PST) (envelope-from john@nlc.net.au) Received: (qmail 18392 invoked from network); 26 Nov 1999 15:53:31 +1100 Received: from nhj.nlc.net.au (HELO saruman) (203.24.133.1) by nhj.nlc.net.au with SMTP; 26 Nov 1999 15:53:31 +1100 Message-ID: <04c201bf37ca$2f8bb630$6cb611cb@scitec.com.au> From: "John Saunders" To: "FreeBSD current" Subject: Latest kernel quirks Date: Fri, 26 Nov 1999 15:53:30 +1100 Organization: NORTHLINK COMMUNICATIONS MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_04BF_01BF3826.628CA380" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_04BF_01BF3826.628CA380 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I have just cvsupped and built the latest -current kernel and have noticed a new quirk plus an old quirk or 2. uname -a output is: FreeBSD XXXX 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Fri Nov 26 02:06:45 EST 1999 root@pacer.nlc.net.au:/usr/src/sys/compile/PACER i386 1) CMOS clock problem, dmesg output: "Invalid time in real time clock. Check and reset the date immediately!" The system goes to Jan 27 1999 until ntpdate kicks in and fixes it. However each time I boot the time is bad again. This could be a hardware glitch although it was perfectly timed to start happening just as I booted into a newly built kernel...very suspicious. 2) ISA unexpected tag problem, dmesg output: "pci0: unknown card (vendor=0x121a, dev=0x0001) at 11.0" "isa0: unexpected tag 14" The PCI device is a Diamond Monster 3D (3Dfx Voodoo 1). I don't know if there is a relationship or if it is pue chance that they are located next to each other. This has been long standing and is not a recent gremlin, it doesn't seem to affect anything. 3) The new ATA drivers have a display formatting bug that results in the following output if a CDROM doesn't doesn't supply speed info: ", 512KB buffer, PIO" Patch is attached with MIME to save tabs and formatting. I think I sent this to Soren a while ago, although the latest commits from him didn't fix the problem. Maybe they got lost, as he was very responsive to a previous patch. 4) My Pioneer DVD drive causes the following: "atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: CDROM drive at ata1 as slave" Is the MODE_SENSE_BIG a problem report or a diagnostic output. Thanks. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NORTHLINK COMMUNICATIONS P/L - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ ------=_NextPart_000_04BF_01BF3826.628CA380 Content-Type: application/octet-stream; name="atapi-cd.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="atapi-cd.patch" --- atapi-cd.c.orig Wed Oct 13 23:06:09 1999=0A= +++ atapi-cd.c Wed Oct 13 23:11:06 1999=0A= @@ -259,9 +259,10 @@=0A= cdp->atp->controller->lun,=0A= (cdp->atp->unit =3D=3D ATA_MASTER) ? "master" : "slave ");=0A= =0A= + printf("acd%d:", cdp->lun);=0A= + comma =3D 0;=0A= if (cdp->cap.cur_read_speed) {=0A= - printf("acd%d: ", cdp->lun);=0A= - printf("read %dKB/s", cdp->cap.cur_read_speed * 1000 / 1024);=0A= + printf(" read %dKB/s", cdp->cap.cur_read_speed * 1000 / 1024);=0A= if (cdp->cap.max_read_speed) =0A= printf(" (%dKB/s)", cdp->cap.max_read_speed * 1000 / 1024);=0A= if ((cdp->cap.cur_write_speed) &&=0A= @@ -271,11 +272,13 @@=0A= if (cdp->cap.max_write_speed)=0A= printf(" (%dKB/s)", cdp->cap.max_write_speed * 1000 / 1024);=0A= }=0A= + comma =3D 1;=0A= }=0A= - if (cdp->cap.buf_size)=0A= - printf(", %dKB buffer", cdp->cap.buf_size);=0A= - printf(", %s\n", ata_mode2str(cdp->atp->controller->mode[=0A= - (cdp->atp->unit =3D=3D ATA_MASTER) ? 0 : 1]));=0A= + if (cdp->cap.buf_size) {=0A= + printf("%s %dKB buffer", comma ? "," : "", cdp->cap.buf_size); comma = =3D 1;=0A= + }=0A= + printf("%s %s\n", comma ? "," : "", = ata_mode2str(cdp->atp->controller->mode[=0A= + (cdp->atp->unit =3D=3D ATA_MASTER) ? 0 : 1])); comma =3D 1;=0A= =0A= printf("acd%d: supported read types:", cdp->lun);=0A= comma =3D 0;=0A= ------=_NextPart_000_04BF_01BF3826.628CA380-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 20:54:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from hayseed.net (hayseed.net [207.181.249.194]) by hub.freebsd.org (Postfix) with ESMTP id 48CF114FA3 for ; Thu, 25 Nov 1999 20:54:41 -0800 (PST) (envelope-from cnielsen@pobox.com) Received: from localhost (LOCALHOST [127.0.0.1]) by hayseed.net (8.9.3/8.9.3) with ESMTP id UAA22192; Thu, 25 Nov 1999 20:54:20 -0800 Date: Thu, 25 Nov 1999 20:54:25 -0800 (PST) From: Christopher Nielsen X-Sender: cnielsen@ender.scient.com To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: <199911231905.VAA80946@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Mark Murray wrote: > I have been charged with the duty of ensuring that FreeBSD gets a > security audit that has the credibility of OpenBSD's. Great news! I had tried to organise such an effort over a year ago with little success, mostly because I was working for a startup. :-) I have a little more time to eyeball/diff/audit code, now. Count me in as an auditer. -- Christopher Nielsen (enkhyl|cnielsen)@pobox.com Enkhyl on IRC too many freaks. not enough circuses. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 21: 8: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 6700014C36; Thu, 25 Nov 1999 21:07:57 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id AAA20748; Fri, 26 Nov 1999 00:07:54 -0500 (EST) Date: Fri, 26 Nov 1999 00:07:54 -0500 (EST) From: "Matthew N. Dodd" To: Assar Westerlund Cc: obrien@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current In-Reply-To: <5lu2maghqc.fsf@foo.sics.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Nov 1999, Assar Westerlund wrote: > there's (to my mind) a difference between it's not done by default and > it will not work. I did it because I had hardwired it in my previous > config. Yes, and when I converted if_ep to newbus I mentioned that hardwire was no longer supported. I'm a little annoyed that if_ep has issues working with if_ex/if_ie and I'll add that to my list of things to look at when I get a chance to fix a few outstanding issues with if_ep. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 21:10:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 0023614C36 for ; Thu, 25 Nov 1999 21:10:24 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id OAA14800; Thu, 25 Nov 1999 14:15:09 -0800 (PST) Message-Id: <199911252215.OAA14800@implode.root.com> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: Which is the truth? (sycalls and traps) In-reply-to: Your message of "Thu, 25 Nov 1999 18:37:12 PST." From: David Greenman Reply-To: dg@root.com Date: Thu, 25 Nov 1999 14:15:09 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Am I also right in assuming that all the registers that the user was >running when they did the KERNCALL have been saved on the KERNEL stack by >the time that the above routines are called? No, that's what the pushal (push all) does. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 25 23:24:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from es-i2.fernuni-hagen.de (ES-i2.fernuni-hagen.de [132.176.7.81]) by hub.freebsd.org (Postfix) with ESMTP id B4F7314A0B for ; Thu, 25 Nov 1999 23:24:09 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by es-i2.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id IAA09550; Fri, 26 Nov 1999 08:24:07 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <383E3596.21AB5F77@fernuni-hagen.de> Date: Fri, 26 Nov 1999 08:24:06 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: German/Germany, de-DE, en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: observations with the ata-driver (hd and zip drive) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good and bad observations: When using a relative new 15 GByte hard drive (vendor IBM) with the wd0 driver the HD-led never turned off, even without disk activity. With the ata driver the hard drive led works as expected. When running a "make buildworld" i had the impression that all went very fast. The ata driver claims to use DMA .. This was on my box at home ... At work i cant get the ata driver to work with my ide-zip drive and mtools. The box has a scsi controller and the zip drive as master on wdc0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (atapi): , removable, intr, iordis wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set when the ata driver is active, i.e. "mdir z:" ("/dev/rafd0s4") leads to ZIP drive activity, but it fails on reading partition information (was also mentioned earlier in this group from others). --- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 0:17:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B278B14CC1; Fri, 26 Nov 1999 00:17:36 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA02778; Fri, 26 Nov 1999 09:16:14 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Matthew N. Dodd" Cc: Assar Westerlund , obrien@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current In-reply-to: Your message of "Fri, 26 Nov 1999 00:07:54 EST." Date: Fri, 26 Nov 1999 09:16:14 +0100 Message-ID: <2776.943604174@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Matthew N. Dodd" writes: >Yes, and when I converted if_ep to newbus I mentioned that hardwire was no >longer supported. Couldn't we simply ignore such hardwiring (with a warning) if present ? >I'm a little annoyed that if_ep has issues working with if_ex/if_ie and >I'll add that to my list of things to look at when I get a chance to fix a >few outstanding issues with if_ep. Can we somehow mark the if_ep as "fickle hardware" so it gets probed before the if_ex/it_ie ? We used to have such a facility. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 0:19:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 0212F14D78; Fri, 26 Nov 1999 00:19:02 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id DAA24656; Fri, 26 Nov 1999 03:18:56 -0500 (EST) Date: Fri, 26 Nov 1999 03:18:56 -0500 (EST) From: "Matthew N. Dodd" To: Poul-Henning Kamp Cc: Assar Westerlund , obrien@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current In-Reply-To: <2776.943604174@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Nov 1999, Poul-Henning Kamp wrote: > In message , "Matthew > N. Dodd" writes: > > >Yes, and when I converted if_ep to newbus I mentioned that hardwire was no > >longer supported. > > Couldn't we simply ignore such hardwiring (with a warning) if present ? I'm not sure that I can tell the difference between a hardwired device and one that is setup by the PnP/ISA 3c5x9 enumerator. I suppose I could cheat and init the softc in the IDENTIFY or something... > Can we somehow mark the if_ep as "fickle hardware" so it gets probed > before the if_ex/it_ie ? We used to have such a facility. I'm going to look closer at those two drivers and find the place where they disagree with if_ep. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 0:22:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 5451C14CC1; Fri, 26 Nov 1999 00:22:29 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA02867; Fri, 26 Nov 1999 09:21:23 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Matthew N. Dodd" Cc: Assar Westerlund , obrien@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current In-reply-to: Your message of "Fri, 26 Nov 1999 03:18:56 EST." Date: Fri, 26 Nov 1999 09:21:22 +0100 Message-ID: <2865.943604482@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Matthew N. Dodd" writes: >On Fri, 26 Nov 1999, Poul-Henning Kamp wrote: >> Can we somehow mark the if_ep as "fickle hardware" so it gets probed >> before the if_ex/it_ie ? We used to have such a facility. > >I'm going to look closer at those two drivers and find the place where >they disagree with if_ep. They don't disagree, they do some stuff to some registers to detect their respective hardware, which unfortunately hoses a ep0 card if one happens to be there instead. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 0:29:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 5726F14CC1; Fri, 26 Nov 1999 00:29:20 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id DAA24905; Fri, 26 Nov 1999 03:29:17 -0500 (EST) Date: Fri, 26 Nov 1999 03:29:16 -0500 (EST) From: "Matthew N. Dodd" To: Poul-Henning Kamp Cc: Assar Westerlund , obrien@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current In-Reply-To: <2865.943604482@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Nov 1999, Poul-Henning Kamp wrote: > >I'm going to look closer at those two drivers and find the place where > >they disagree with if_ep. > > They don't disagree, they do some stuff to some registers to detect > their respective hardware, which unfortunately hoses a ep0 card if > one happens to be there instead. By 'disagree' I meant 'where they conflict eachother'. :) What is really needed here is for the resource manager to handle 'requests' as well as allocations. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 0:30:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 02DB214F92 for ; Fri, 26 Nov 1999 00:30:41 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 4176686 invoked from network); 26 Nov 1999 08:30:41 -0000 Received: from s123.paris-36.cybercable.fr (HELO cybercable.fr) ([212.198.36.123]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 26 Nov 1999 08:30:41 -0000 Message-ID: <383E455D.8456913E@cybercable.fr> Date: Fri, 26 Nov 1999 09:31:25 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If it is not possible to hardwire the ep boards, how do I recognize them in a "router" setting ? (I have an oldish PC with to ep boards, used as a WAN simulator, with dummynet : how do I tell ep0 form ep1 ?) TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 0:31:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles533.castles.com [208.214.165.97]) by hub.freebsd.org (Postfix) with ESMTP id DC19F14F92 for ; Fri, 26 Nov 1999 00:31:35 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA74484; Fri, 26 Nov 1999 00:32:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911260832.AAA74484@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Douglas Kuntz" Cc: current@FreeBSD.ORG Subject: Re: Boot error In-reply-to: Your message of "Thu, 25 Nov 1999 20:14:04 EST." <000c01bf37ab$8d605820$29100218@micronetinfo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Nov 1999 00:32:08 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First things first; try using English for your problem reports. A large slice of the community that might be able to answer your questions don't use it as their first language, and by using leet-speek you immediately eliminate them as a source of help. > Before I go do a fresh SNAP install, I wanted to see if there was an easier > way to fix this problem... > My -current box was a celeron...I had to switch the celeron and mboard to my > windoze machine to get a vidcard werkin...I recompiled the kernel to 486, > 586, and 686, and moved the HD, the cards, etc, over to the K6-2 400 I > had...now, everytime at boot, before it even prompts for which OS to start, > it has a bootloader problem...if I recall it was something like: > BTX 1.0.0 BTX Loader 1.0.1 > then "System Halted" > > I tried the fixit floppy, etc, and that partially worked, but locked when it > was mounting the filesystem. > I'm sorry that I cant provide any more info...I only have 1 monitor and cant > copy/paste between 2 pcs. I'm sorry, but without a lot more information all I can say is "you done something wrong". You might start with an exhaustive list of the relevant hardware in the actual system in question, followed by the actual set of physical changes which took it from "working" to "not working". We're not telepathic, and we don't have the time to hunt you down and steal all your hardware to solve your own problems, so you're going to have to help us out here. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 1:14:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from es-i2.fernuni-hagen.de (ES-i2.fernuni-hagen.de [132.176.7.81]) by hub.freebsd.org (Postfix) with ESMTP id AB4B314FF1 for ; Fri, 26 Nov 1999 01:14:26 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by es-i2.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id KAA09981; Fri, 26 Nov 1999 10:14:22 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <383E4F6F.9A99DD6A@fernuni-hagen.de> Date: Fri, 26 Nov 1999 10:14:23 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: German/Germany, de-DE, en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: Re: observations with the ata-driver (hd and zip drive) References: <383E3596.21AB5F77@fernuni-hagen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG more observations to the zip-drive problem: First the relevant dmesg-line: atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 afd0: rewriteable drive at ata0 as master afd0: 96MB (196608 sectors), 32 cyls, 64 heads, 96 S/T, 512 B/S afd0: 4096KB/s, transfer limit 64 blks, PIO afd0: Medium: Unknown media (0x0) second : the first 512 bytes of /dev/rfd* are identical, here are checksums: 61088 1 rafd0.txt 61088 1 rafd0s4.txt here are some lines of the files in emacs hexl-mode: 00000000: eb2e 4950 4152 5420 636f 6465 2030 3039 ..IPART code 009 00000010: 202d 2049 6f6d 6567 6120 436f 7270 6f72 - Iomega Corpor 00000020: 6174 696f 6e20 2d20 3131 2f32 332f 3930 ation - 11/23/90 00000030: fafc 8cc8 8ed0 bc00 7c8e d88e c0b9 0002 ........|....... the zip disks where formatted under windows, of course. trying to mount the zip-drive gives: msdos: /dev/afd0s4: Invalid argument -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 1:26:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C269214FAD for ; Fri, 26 Nov 1999 01:26:42 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA55066; Fri, 26 Nov 1999 10:26:32 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199911260926.KAA55066@freebsd.dk> Subject: Re: observations with the ata-driver (hd and zip drive) In-Reply-To: <383E4F6F.9A99DD6A@fernuni-hagen.de> from "F. Heinrichmeyer" at "Nov 26, 1999 10:14:23 am" To: fritz.heinrichmeyer@fernuni-hagen.de (F. Heinrichmeyer) Date: Fri, 26 Nov 1999 10:26:32 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG (freebsd-current@FreeBSD.ORG) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems F. Heinrichmeyer wrote: > more observations to the zip-drive problem: > First the relevant dmesg-line: > > atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 > afd0: rewriteable drive at ata0 as master > afd0: 96MB (196608 sectors), 32 cyls, 64 heads, 96 S/T, 512 B/S > afd0: 4096KB/s, transfer limit 64 blks, PIO > afd0: Medium: Unknown media (0x0) That looks like it should... > second : > > the first 512 bytes of /dev/rfd* are identical, here are checksums: > > 61088 1 rafd0.txt > 61088 1 rafd0s4.txt > > here are some lines of the files in emacs hexl-mode: > > 00000000: eb2e 4950 4152 5420 636f 6465 2030 3039 ..IPART code 009 > 00000010: 202d 2049 6f6d 6567 6120 436f 7270 6f72 - Iomega Corpor > 00000020: 6174 696f 6e20 2d20 3131 2f32 332f 3930 ation - 11/23/90 > 00000030: fafc 8cc8 8ed0 bc00 7c8e d88e c0b9 0002 ........|....... > > the zip disks where formatted under windows, of course. > > trying to mount the zip-drive gives: > msdos: /dev/afd0s4: Invalid argument This has appeared before IIRC, I've no idea why this doesn't work, but I can rig up my ZIP drive, but I dont have DOS nor WINDOWS, do it fail also if the disk is formatted under FreeBSD ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 3:10: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp.wirehub.nl (smtp.wirehub.nl [195.86.25.80]) by hub.freebsd.org (Postfix) with ESMTP id 3413514E5A for ; Fri, 26 Nov 1999 03:10:02 -0800 (PST) (envelope-from Ben.Grimm@wirehub.net) Received: from ben.wirehub.nl (ben.wirehub.nl [195.86.25.13]) by smtp.wirehub.nl (8.9.3/8.9.3) with SMTP id MAA20364 for ; Fri, 26 Nov 1999 12:09:53 +0100 (CET) From: "Ben C. O. Grimm" To: freebsd-current@freebsd.org Subject: Re: AHC0 fireworks ? Date: Fri, 26 Nov 1999 12:09:53 +0100 Organization: Wirehub! Internet Engineering Message-ID: <38qs3sgfgsa87qhd34ecfq67mqha7bffot@smtp.wirehub.nl> References: <4.2.0.58.19991120091815.00c2ced0@194.184.65.4.newsgate.clinet.fi> In-Reply-To: <4.2.0.58.19991120091815.00c2ced0@194.184.65.4.newsgate.clinet.fi> X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 Nov 1999 11:20:23 +0200, Gianmarco Giovannelli wrote: > But I have now a lot of errors (as you can see in this logs) on my scsi chain. > I had never experienced such things in the near past (even if as an old > current user sometimes I see also worse things :-) > > Btw I don't see in the current mailing list threads about iussues on the > scsi subsystem recently so it can be a problem related to my hardware (even > if I didn't experience it before)... > Nov 20 09:17:49 gmarco /kernel: ahc0: adapter> irq 19 at device 6.0 on pci0 > Nov 20 09:17:49 gmarco /kernel: (da0:ahc0:0:0:0): parity error during > Data-In phase. Please look up the following discussion in freebsd-questions. I'm reading these lists on Usenet, so I'm going to give you Usenet message-Id's: <19991124135732.E23235@mincom.com.newsgate.clinet.fi> <9911240640.AA10118@CS.UH.EDU.newsgate.clinet.fi> <19991124182926.K23235@mincom.com.newsgate.clinet.fi> <95ln3skv9r10s0f6sp0lhd8nhslh1hgrh7@smtp.wirehub.nl.newsgate.clinet.fi> The last one is a log extract quite similar to yours ... it's Adaptec that's seemingly causing the problems here. I'm running 3.3-RELEASE, and problems started on two machines with a lot of disk usage (both news related) when I upgraded from 3.1/3.2 -> 3.3. The fact that this hasn't been fixed anywhere in the cvsup route makes me rather sad. I'm really waiting for fixes/patches .. -- - Ben C. O. Grimm ----------------- Ben.Grimm@wirehub.net - - Wirehub! Internet Engineering - http://www.wirehub.net/ - - Wirehub! Backbone --- http://doema.wirehub.net/wirehub/ - - Private Ponderings ------- http://libertas.wirehub.net/ - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 4:45: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id CCFE314CE1 for ; Fri, 26 Nov 1999 04:44:55 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from dyn-9.blackbox-2.netaxs.com (dyn-9.blackbox-2.netaxs.com [207.106.60.9]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id HAA29670; Fri, 26 Nov 1999 07:44:46 -0500 (EST) Date: Fri, 26 Nov 1999 07:44:45 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: "freebsd-current@FreeBSD.ORG" Cc: "F. Heinrichmeyer" , Soren Schmidt Subject: Re: observations with the ata-driver (hd and zip drive) In-Reply-To: <199911260926.KAA55066@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Nov 1999, Soren Schmidt wrote: <>It seems F. Heinrichmeyer wrote: <>> more observations to the zip-drive problem: <>> First the relevant dmesg-line: I'm also still having a small problem with the ata driver and my HP Colorado 8G. I have it hanging off an ATAPI CDROM as a slave. The dmesg says: ata-pci1: irq 0 at device 11.0 on pci0 ata-pci1: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=00 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0xc ata0 at 0x01f0 irq 14 on ata-pci1 This indicates that it sees two ATAPI devices. But when the system starts up, all I get is: ata0-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: CDROM drive at ata0 as master acd0: read 687KB/s (6875KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked No tape drive is found. All worked well with the old drivers. ========================================================== = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@netaxs.com Home of the Gipper = ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 4:51:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 01F7514CE1 for ; Fri, 26 Nov 1999 04:51:24 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA02933; Fri, 26 Nov 1999 13:51:10 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199911261251.NAA02933@freebsd.dk> Subject: Re: observations with the ata-driver (hd and zip drive) In-Reply-To: from Bryan Liesner at "Nov 26, 1999 07:44:45 am" To: bleez@netaxs.com (Bryan Liesner) Date: Fri, 26 Nov 1999 13:51:10 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG (freebsd-current@FreeBSD.ORG), fritz.heinrichmeyer@fernuni-hagen.de (F. Heinrichmeyer) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bryan Liesner wrote: > On Fri, 26 Nov 1999, Soren Schmidt wrote: > > <>It seems F. Heinrichmeyer wrote: > <>> more observations to the zip-drive problem: > <>> First the relevant dmesg-line: > > I'm also still having a small problem with the ata driver and my HP > Colorado 8G. I have it hanging off an ATAPI CDROM as a slave. > The dmesg says: > > ata-pci1: irq 0 at device 11.0 on pci0 > ata-pci1: Busmastering DMA supported > ata0: iobase=0x01f0 altiobase=0x03f6 > ata0: mask=03 status0=00 status1=00 > ata0: mask=03 status0=00 status1=00 > ata0: devices = 0xc > ata0 at 0x01f0 irq 14 on ata-pci1 > > This indicates that it sees two ATAPI devices. But when the system > starts up, all I get is: > > ata0-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 > atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 > acd0: CDROM drive at ata0 as master > acd0: read 687KB/s (6875KB/s), 128KB buffer, PIO > acd0: supported read types: CD-R, CD-RW, CD-DA, packet > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked > > No tape drive is found. All worked well with the old drivers. Hmm, what can I say, I use a simlar setup, just with either a Seagate or an Onstream tape, both work well. You should probably sprinkle a couple of printf's in the atapi probe code and the tape driver an see where it fails... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 5:42:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id D46EC14F9F for ; Fri, 26 Nov 1999 05:42:48 -0800 (PST) (envelope-from netchild@Leidinger.net) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id OAA12634130; Fri, 26 Nov 1999 14:41:34 +0100 (CET) Received: from Magelan.Leidinger.net (maxtnt-234.telip.uni-sb.de [134.96.71.105]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id OAA20605; Fri, 26 Nov 1999 14:41:39 +0100 (CET) Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id NAA01190; Fri, 26 Nov 1999 13:47:32 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <199911261247.NAA01190@Magelan.Leidinger.net> Date: Fri, 26 Nov 1999 13:47:31 +0100 (CET) From: Alexander Leidinger Subject: Re: observations with the ata-driver (hd and zip drive) To: sos@freebsd.dk Cc: fritz.heinrichmeyer@fernuni-hagen.de, freebsd-current@FreeBSD.ORG In-Reply-To: <199911260926.KAA55066@freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Nov, Soren Schmidt wrote: >> trying to mount the zip-drive gives: >> msdos: /dev/afd0s4: Invalid argument > > This has appeared before IIRC, I've no idea why this doesn't work, > but I can rig up my ZIP drive, but I dont have DOS nor WINDOWS, > do it fail also if the disk is formatted under FreeBSD ?? I didn´t tried to reproduce this recently, but you could try to format the ZIP-disc with mtools: mformat -t 96 -h 64 -s 32 -H 32 z: Fritz: could you post the output of "minfo z:" (ata-controller)? Here´s the one with wd (perhaps a diff between them gives someone a hint): ---snip--- (101) netchild@ttyp2 > minfo z: device information: =================== filename="/dev/rwfd0s4" sectors per track: 32 heads: 64 cylinders: 96 mformat command line: mformat -t 96 -h 64 -s 32 -H 32 z: bootsector information ====================== banner:"(?6;1IHC" sector size: 512 bytes cluster size: 4 sectors reserved (boot) sectors: 1 fats: 2 max available root directory slots: 512 small size: 0 sectors media descriptor byte: 0xf8 sectors per fat: 192 sectors per track: 32 heads: 64 hidden sectors: 32 big size: 196576 sectors physical drive id: 0x80 reserved=0x0 dos4=0x29 serial number: 39BC1102 disk label="ZIP-100 " disk type="FAT16 " ---snip--- And here the boot-message: ---snip--- wdc0: unit 1 (atapi): , removable, intr, iordis wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set ---snip--- Søren, I assume the ata-controller knows about the last line, right? Bye, Alexander. -- I'll be damned if I can't win when I'm keeping score. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 5:49:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 9A91515018 for ; Fri, 26 Nov 1999 05:49:44 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA16512; Fri, 26 Nov 1999 14:49:18 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199911261349.OAA16512@freebsd.dk> Subject: Re: observations with the ata-driver (hd and zip drive) In-Reply-To: <199911261247.NAA01190@Magelan.Leidinger.net> from Alexander Leidinger at "Nov 26, 1999 01:47:31 pm" To: Alexander@Leidinger.net (Alexander Leidinger) Date: Fri, 26 Nov 1999 14:49:18 +0100 (CET) Cc: fritz.heinrichmeyer@fernuni-hagen.de, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alexander Leidinger wrote: > I didn´t tried to reproduce this recently, but you could try to format > the ZIP-disc with mtools: > > mformat -t 96 -h 64 -s 32 -H 32 z: I'll dig out my ZIP drive tonight a do some testing... > ---snip--- > wdc0: unit 1 (atapi): , removable, intr, iordis > wfd0: medium type unknown (no disk) > wfd0: buggy Zip drive, 64-block transfer limit set > ---snip--- > > Søren, I assume the ata-controller knows about the last line, right? It does, and it also says so in the probe... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 5:52:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 904A115018 for ; Fri, 26 Nov 1999 05:52:11 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id PAA93991 for ; Fri, 26 Nov 1999 15:52:09 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911261352.PAA93991@gratis.grondar.za> To: current@freebsd.org Subject: FreeBSD-audit mailing list set up. Date: Fri, 26 Nov 1999 15:52:08 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello FreeBSD person! We now have a mailing list for the discussion of the FreeBSD Audit Project. Thanks to Jon Bresler, our postmaster! All of you who want to contribute to this project, please sign up. There was a very heartening response to the announcement, and a few slowcoaches even got stuck in straight away. Wonderful! Topics for discussion will be audit methodology, audit progress, and if there are significant events, they will be announced there. If something is of relevance to -current or -security, then it may be discussed there _instead_ _of_ -audit. Crossposting, flaming, -stable and other offtopic content is not allowed. Lets keep the signal ratio high! I'll give it a day or two, then kick off a summary of the responses seen to my first announcement of the Audit Project in -Current. As usual, to sign up you could: $ echo subscribe freebsd-audit | mail -s Subscribe majordomo@freebsd.org Thanks! M To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 7:31:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 4D7BD15049 for ; Fri, 26 Nov 1999 07:31:36 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA60754; Fri, 26 Nov 1999 10:31:24 -0500 (EST) (envelope-from wollman) Date: Fri, 26 Nov 1999 10:31:24 -0500 (EST) From: Garrett Wollman Message-Id: <199911261531.KAA60754@khavrinen.lcs.mit.edu> To: "Matthew N. Dodd" Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current In-Reply-To: References: <2865.943604482@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > What is really needed here is for the resource manager to handle > 'requests' as well as allocations. It does. That's the difference between `allocate' and `activate'. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 10:41:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 9AD6814BC7 for ; Fri, 26 Nov 1999 10:41:21 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id NAA06469; Fri, 26 Nov 1999 13:41:19 -0500 (EST) Date: Fri, 26 Nov 1999 13:41:18 -0500 (EST) From: "Matthew N. Dodd" To: Thierry Herbelot Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current In-Reply-To: <383E455D.8456913E@cybercable.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Nov 1999, Thierry Herbelot wrote: > If it is not possible to hardwire the ep boards, how do I recognize them > in a "router" setting ? > > (I have an oldish PC with to ep boards, used as a WAN simulator, with > dummynet : how do I tell ep0 form ep1 ?) The ISA enumerator detects cards in order of ethernet MAC address. I don't have two PnP cards so I'm not sure of the order that the PnP enumerator uses. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 10:52:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from rmx09.globecomm.net (rmx09.iname.net [165.251.8.95]) by hub.freebsd.org (Postfix) with ESMTP id 8ADDF14BC7 for ; Fri, 26 Nov 1999 10:52:14 -0800 (PST) (envelope-from davec@unforgettable.com) Received: from weba6.iname.net by rmx09.globecomm.net (8.9.1/8.8.0) with ESMTP id NAA04411 ; Fri, 26 Nov 1999 13:52:11 -0500 (EST) From: davec@unforgettable.com Received: (from root@localhost) by weba6.iname.net (8.9.1a/8.9.2.Alpha2) id NAA06578; Fri, 26 Nov 1999 13:52:11 -0500 (EST) MIME-Version: 1.0 Message-Id: <991126135210JR.24016@weba6.iname.net> Date: Fri, 26 Nov 1999 13:52:10 -0500 (EST) Content-Type: Text/Plain Content-Transfer-Encoding: 7bit To: FreeBSD-Current Mailing list Subject: Guido's recent 3.3.3 IpFilter commit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chances are I'm missing something or a step, but I've ran out of ideas and mailing lists to search through. I'm running -current as of today with IPFilter 3.3.3 (big thanks to Guido for adding it back into FreeBSD's tree and updating it to the latest version). It starts successfully, but when I try to load any rule sets (or remove rules with if -Fa) I get: open device: Device not configured ioctl(SIOCIPFFL): Bad file descriptor This was a move from -current Oct. 10 (right before ipfilter was removed from the kernel), so I know it works with IPFilter. BFP is compiled as well as options IPFILTER in the kernel, and the rule set worked with the oct. 10 version of IPFilter. There are /dev/bpf? devices, as well as /dev/ipl etc. What have I missed? Any help/suggestions/tips would be appreciated. Thanks. Davec Davec@unforgettable.com ---------------------------------------------------------------- Get your free email from AltaVista at http://altavista.iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 11:17:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from milk.k0t.lucky.net (milk.k0t.lucky.net [193.193.192.99]) by hub.freebsd.org (Postfix) with ESMTP id 0F5D215525 for ; Fri, 26 Nov 1999 11:17:37 -0800 (PST) (envelope-from artur@noo.kiev.ua) Received: from noo.kiev.ua (host1.0.10.10.intranet [10.10.0.1]) by milk.k0t.lucky.net (8.Who.Cares/Kilkenny_is_better) with ESMTP id VAA75408 for ; Fri, 26 Nov 1999 21:17:35 +0200 (EET) (envelope-from artur@noo.kiev.ua) From: artur@noo.kiev.ua Received: from Artur (unknown.noo.kiev.ua [10.10.0.2] (may be forged)) by noo.kiev.ua (8.9.3/8.9.2) with SMTP id VAA01346 for ; Fri, 26 Nov 1999 21:38:36 +0200 (EET) (envelope-from artur@noo.kiev.ua) Date: Fri, 26 Nov 1999 21:38:36 +0200 (EET) Message-Id: <199911261938.VAA01346@noo.kiev.ua> To: Subject: Promotion offer MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good moning! Today I visited Your web-site and thought "May be it needs promotion?" I made some automatic promotion tools and needs to improve and test it. If You interesting a web advertising and promotion You can visit http://www.terra.ee/noo/ and launch automatic promotion by filling a form and placing small text in Your page. First stage recommended, it is free of charge. May be my know-how is greate, may be it is nothing. Sorry, if You will decide this is spam. My e-mail is artur@noo.kiev.ua, this is one time offer to e-mail from Your web page. Any questions are welcome. Best regards Artur Frolov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 12:28:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id 06F9B1540A for ; Fri, 26 Nov 1999 12:27:59 -0800 (PST) (envelope-from dakuntz@home.com) Received: from windows ([24.2.16.41]) by mail.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19991126202758.BUOM11752.mail.rdc1.tn.home.com@windows>; Fri, 26 Nov 1999 12:27:58 -0800 Message-ID: <000c01bf384d$2824c980$29100218@micronetinfo.com> From: "Douglas Kuntz" To: "Mike Smith" Cc: References: <199911260832.AAA74484@mass.cdrom.com> Subject: Re: Boot error Date: Fri, 26 Nov 1999 15:31:02 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok...for hardware, all I have in the machine is: A Linksys 10/100 ethernet (uses pn0) A SCSI card (uses bt0) A S3 Virge video card A FIC VA-503+ motherboard w/ 32meg PC66 sdram and a K6-2 400 the only thing changed between the 2 machines was the other was a Shuttle Socket 370 motherboard, and a Celeron 366 cpu. Everything was moved from one case/motherboard to the other case/motherboard. The kernel had "ata" compiled in, the options for my hardware, and the basic floppy and video, nothing that I though was unusual. Sorrry about the way I typed before...I actually talk like that (or worse) half the time, and I have to remember when to talk/type normally. Doug ----- Original Message ----- From: "Mike Smith" To: "Douglas Kuntz" Cc: Sent: Friday, November 26, 1999 3:32 AM Subject: Re: Boot error > > First things first; try using English for your problem reports. A large > slice of the community that might be able to answer your questions don't > use it as their first language, and by using leet-speek you immediately > eliminate them as a source of help. > > > Before I go do a fresh SNAP install, I wanted to see if there was an easier > > way to fix this problem... > > My -current box was a celeron...I had to switch the celeron and mboard to my > > windoze machine to get a vidcard werkin...I recompiled the kernel to 486, > > 586, and 686, and moved the HD, the cards, etc, over to the K6-2 400 I > > had...now, everytime at boot, before it even prompts for which OS to start, > > it has a bootloader problem...if I recall it was something like: > > BTX 1.0.0 BTX Loader 1.0.1 > > then "System Halted" > > > > I tried the fixit floppy, etc, and that partially worked, but locked when it > > was mounting the filesystem. > > I'm sorry that I cant provide any more info...I only have 1 monitor and cant > > copy/paste between 2 pcs. > > I'm sorry, but without a lot more information all I can say is "you done > something wrong". > > You might start with an exhaustive list of the relevant hardware in the > actual system in question, followed by the actual set of physical changes > which took it from "working" to "not working". We're not telepathic, and > we don't have the time to hunt you down and steal all your hardware to > solve your own problems, so you're going to have to help us out here. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 13: 7: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id CC23115336 for ; Fri, 26 Nov 1999 13:07:00 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA08376; Fri, 26 Nov 1999 14:06:44 -0700 (MST) (envelope-from ken) Message-Id: <199911262106.OAA08376@panzer.kdm.org> Subject: Re: AHC0 fireworks ? In-Reply-To: <38qs3sgfgsa87qhd34ecfq67mqha7bffot@smtp.wirehub.nl> from "Ben C. O. Grimm" at "Nov 26, 1999 12:09:53 pm" To: Ben.Grimm@wirehub.net (Ben C. O. Grimm) Date: Fri, 26 Nov 1999 14:06:44 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben C. O. Grimm wrote... > On 20 Nov 1999 11:20:23 +0200, Gianmarco Giovannelli > wrote: > > > But I have now a lot of errors (as you can see in this logs) on my scsi chain. > > I had never experienced such things in the near past (even if as an old > > current user sometimes I see also worse things :-) > > > > Btw I don't see in the current mailing list threads about iussues on the > > scsi subsystem recently so it can be a problem related to my hardware (even > > if I didn't experience it before)... > > Nov 20 09:17:49 gmarco /kernel: ahc0: > adapter> irq 19 at device 6.0 on pci0 > > > Nov 20 09:17:49 gmarco /kernel: (da0:ahc0:0:0:0): parity error during > > Data-In phase. > > Please look up the following discussion in freebsd-questions. I'm reading these > lists on Usenet, so I'm going to give you Usenet message-Id's: > > <19991124135732.E23235@mincom.com.newsgate.clinet.fi> > <9911240640.AA10118@CS.UH.EDU.newsgate.clinet.fi> > <19991124182926.K23235@mincom.com.newsgate.clinet.fi> > <95ln3skv9r10s0f6sp0lhd8nhslh1hgrh7@smtp.wirehub.nl.newsgate.clinet.fi> > > The last one is a log extract quite similar to yours ... it's Adaptec that's > seemingly causing the problems here. I'm running 3.3-RELEASE, and problems > started on two machines with a lot of disk usage (both news related) when I > upgraded from 3.1/3.2 -> 3.3. The fact that this hasn't been fixed anywhere in > the cvsup route makes me rather sad. I'm really waiting for fixes/patches .. There was a corruption problem caused by a bug in the 7890/1 chips that Justin worked around in the ahc driver shortly after 3.3 went out the door. This generally only manifested itself under high load. Your problem is probably very different than Gianmarco's problem, since he has the fix. His problem is most likely cabling or termination. In any case, you need to upgrade to the latest -stable, or wait until 3.4 comes out to fix your problem. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 13: 7:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 22C741533F for ; Fri, 26 Nov 1999 13:07:02 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA08376; Fri, 26 Nov 1999 14:06:44 -0700 (MST) (envelope-from ken) Message-Id: <199911262106.OAA08376@panzer.kdm.org> Subject: Re: AHC0 fireworks ? In-Reply-To: <38qs3sgfgsa87qhd34ecfq67mqha7bffot@smtp.wirehub.nl> from "Ben C. O. Grimm" at "Nov 26, 1999 12:09:53 pm" To: Ben.Grimm@wirehub.net (Ben C. O. Grimm) Date: Fri, 26 Nov 1999 14:06:44 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben C. O. Grimm wrote... > On 20 Nov 1999 11:20:23 +0200, Gianmarco Giovannelli > wrote: > > > But I have now a lot of errors (as you can see in this logs) on my scsi chain. > > I had never experienced such things in the near past (even if as an old > > current user sometimes I see also worse things :-) > > > > Btw I don't see in the current mailing list threads about iussues on the > > scsi subsystem recently so it can be a problem related to my hardware (even > > if I didn't experience it before)... > > Nov 20 09:17:49 gmarco /kernel: ahc0: > adapter> irq 19 at device 6.0 on pci0 > > > Nov 20 09:17:49 gmarco /kernel: (da0:ahc0:0:0:0): parity error during > > Data-In phase. > > Please look up the following discussion in freebsd-questions. I'm reading these > lists on Usenet, so I'm going to give you Usenet message-Id's: > > <19991124135732.E23235@mincom.com.newsgate.clinet.fi> > <9911240640.AA10118@CS.UH.EDU.newsgate.clinet.fi> > <19991124182926.K23235@mincom.com.newsgate.clinet.fi> > <95ln3skv9r10s0f6sp0lhd8nhslh1hgrh7@smtp.wirehub.nl.newsgate.clinet.fi> > > The last one is a log extract quite similar to yours ... it's Adaptec that's > seemingly causing the problems here. I'm running 3.3-RELEASE, and problems > started on two machines with a lot of disk usage (both news related) when I > upgraded from 3.1/3.2 -> 3.3. The fact that this hasn't been fixed anywhere in > the cvsup route makes me rather sad. I'm really waiting for fixes/patches .. There was a corruption problem caused by a bug in the 7890/1 chips that Justin worked around in the ahc driver shortly after 3.3 went out the door. This generally only manifested itself under high load. Your problem is probably very different than Gianmarco's problem, since he has the fix. His problem is most likely cabling or termination. In any case, you need to upgrade to the latest -stable, or wait until 3.4 comes out to fix your problem. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 13:19:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 6783114C37 for ; Fri, 26 Nov 1999 13:19:46 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA06150; Fri, 26 Nov 1999 22:19:03 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: ST-506, ESDI and BAD144 ? In-reply-to: Your message of "Thu, 25 Nov 1999 13:09:20 EST." <19991125130920.10078@mojave.sitaranetworks.com> Date: Fri, 26 Nov 1999 22:19:03 +0100 Message-ID: <6148.943651143@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991125130920.10078@mojave.sitaranetworks.com>, Greg Lehey writes: >On Wednesday, 24 November 1999 at 10:39:44 +0100, Poul-Henning Kamp wrote: >> >> So I would like to propose that we discontinue support for ST-506, >> ESDI disks and BAD144 bad-sector remapping starting with the 4.0 >> release. >> >> So, is anyone running -current on ESDI or ST-506 disks in >> actual applications (as opposed for the gadget/novelty thrill or >> testing purposes) ? > >I don't suppose it would be that big a deal to remove the old driver, >but what speaks against leaving it in the tree along with a comment in >the GENERIC config file saying "if you use antediluvial disk hardware, >you may prefer to use an old driver too"? Well, couldn't we just as well say "if you use pre-cambrian disks please stick with the 3.X release branch" ? There are many indicies which support killing the wd.c driver: New hardware is supported (much) better by ata driver The ATAPI stuff in wd.c is a rather crude hack, ata driver handles it better. Wd.c is the only driver which keeps the BAD144 code alive in our tree, and nobody uses it. Modern drives do their own bad sector handling. The kind of hardware it supports which the ata doesn't is usually found in machines with less than 32Mbyte of RAM anyway, running 4.0 on such a machine is not even close to fun. (And modern motherboards/bioses seem to have lost the ability to handle old disks, at least the ones I tried here in my lab.) There is a long time until 5.0 which is our next chance. so, speak now, or forever bite your tongue... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 14:11:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 6B86C14DB7 for ; Fri, 26 Nov 1999 14:11:46 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id QAA10876 for ; Fri, 26 Nov 1999 16:11:46 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Fri, 26 Nov 1999 16:11:46 -0600 (CST) From: David Scheidt To: freebsd-current@freebsd.org Subject: World breakage in libpam? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seeing this trying to build world, cvsup'd earlier today. cc -O -pipe -static -DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING -Wall -I/usr/src/libexec/ftpd/../../contrib-crypto/telnet -DINTERNAL_LS -Dmain=ls_main -I/usr/src/libexec/ftpd/../../bin/ls -I/usr/obj/usr/src/tmp/usr/include -o ftpd ftpd.o ftpcmd.o logwtmp.o popen.o skey-stuff.o ls.o cmp.o print.o stat_flags.o util.o -lskey -lmd -lcrypt -lutil -lpam /usr/obj/usr/src/tmp/usr/lib/libpam.a(pam_static_modules.o): In function `_pam_get_static_sym': pam_static_modules.o(.text+0x299): undefined reference to `rad_create_request' pam_static_modules.o(.text+0x2af): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x2cc): undefined reference to `rad_put_string' pam_static_modules.o(.text+0x2e9): undefined reference to `rad_put_string' pam_static_modules.o(.text+0x319): undefined reference to `rad_put_string' pam_static_modules.o(.text+0x32d): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x34d): undefined reference to `rad_put_attr' pam_static_modules.o(.text+0x363): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x379): undefined reference to `rad_put_int' pam_static_modules.o(.text+0x394): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x3db): undefined reference to `rad_cvt_string' pam_static_modules.o(.text+0x40d): undefined reference to `rad_get_attr' pam_static_modules.o(.text+0x438): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x4b7): undefined reference to `rad_cvt_string' pam_static_modules.o(.text+0x4f2): undefined reference to `rad_get_attr' pam_static_modules.o(.text+0x50a): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x760): undefined reference to `rad_open' pam_static_modules.o(.text+0x789): undefined reference to `rad_config' pam_static_modules.o(.text+0x79d): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x7dd): undefined reference to `rad_send_request' pam_static_modules.o(.text+0x821): undefined reference to `rad_close' pam_static_modules.o(.text+0x881): undefined reference to `rad_close' pam_static_modules.o(.text+0x8ab): undefined reference to `rad_close' pam_static_modules.o(.text+0x8bc): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x8d5): undefined reference to `rad_close' pam_static_modules.o(.text+0x8f4): undefined reference to `rad_close' pam_static_modules.o(.text+0xb07): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xb23): undefined reference to `tac_close' pam_static_modules.o(.text+0xb4b): undefined reference to `tac_get_msg' pam_static_modules.o(.text+0xb5e): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xb77): undefined reference to `tac_close' pam_static_modules.o(.text+0xb96): undefined reference to `tac_set_msg' pam_static_modules.o(.text+0xbb0): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xbc9): undefined reference to `tac_close' pam_static_modules.o(.text+0xc60): undefined reference to `tac_open' pam_static_modules.o(.text+0xc90): undefined reference to `tac_config' pam_static_modules.o(.text+0xca7): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xcc3): undefined reference to `tac_create_authen' pam_static_modules.o(.text+0xcda): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xcf6): undefined reference to `tac_close' pam_static_modules.o(.text+0xd09): undefined reference to `tac_set_user' pam_static_modules.o(.text+0xd32): undefined reference to `tac_set_port' pam_static_modules.o(.text+0xd5b): undefined reference to `tac_set_rem_addr' pam_static_modules.o(.text+0xd84): undefined reference to `tac_send_authen' pam_static_modules.o(.text+0xd9b): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xde8): undefined reference to `tac_close' pam_static_modules.o(.text+0xe48): undefined reference to `tac_close' pam_static_modules.o(.text+0xf52): undefined reference to `tac_close' pam_static_modules.o(.text+0xfbc): undefined reference to `tac_get_data' pam_static_modules.o(.text+0x101c): undefined reference to `tac_close' *** Error code 1 Stop in /usr/src/libexec/ftpd. *** Error code 1 Stop in /usr/src/libexec. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 16:46:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id AF81414F33 for ; Fri, 26 Nov 1999 16:46:20 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id BAA39002; Sat, 27 Nov 1999 01:45:56 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sat, 27 Nov 1999 01:45:56 +0100 (CET) From: Leif Neland To: Thierry Herbelot Cc: "Matthew N. Dodd" , freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current In-Reply-To: <383E455D.8456913E@cybercable.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Nov 1999, Thierry Herbelot wrote: > If it is not possible to hardwire the ep boards, how do I recognize them > in a "router" setting ? > > (I have an oldish PC with to ep boards, used as a WAN simulator, with > dummynet : how do I tell ep0 form ep1 ?) > Look for the "ether" (mac-adress): # ifconfig -a ed0: flags=8843 mtu 1500 inet 192.168.0.14 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:80:ad:50:40:cf Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 17:11:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 03E9D15280 for ; Fri, 26 Nov 1999 17:11:28 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id CAA44609; Sat, 27 Nov 1999 02:11:16 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sat, 27 Nov 1999 02:11:16 +0100 (CET) From: Leif Neland To: German Tischler Cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: Sv: Dr Neuhaus niccy go not recognized In-Reply-To: <19991107192844.A13696@gaspode.franken.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 7 Nov 1999, German Tischler wrote: > On Sun, Nov 07, 1999 at 06:27:37PM +0100, Leif Neland wrote: > > I'd like to test, So how do I proceed from here? > > Get the latest i4b-dev snapshot (00.83.11), get my patches > from http://www.mayn.franken.de/home/tanis/i4b-11.tar.gz, > get a recent current source tree, unpack i4b, unpack the > layer1 patches over it, use the overinstall script, > use > > device isic0 > > in your kernel config file (no at isa? or similiar). > Compile the userland programs and install them, build a kernel > and see if it works, and tell me what goes wrong. > > Sorry, I have not had any time to do much testing; I now use a non-pnp itk instead. I just wanted to do some dialin-logging on my voice-phones. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 26 17:41:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B65831537D for ; Fri, 26 Nov 1999 17:41:51 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA12462; Fri, 26 Nov 1999 17:41:49 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA29416; Fri, 26 Nov 1999 17:41:49 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 26 Nov 1999 17:41:49 -0800 (PST) Message-Id: <199911270141.RAA29416@vashon.polstra.com> To: wollman@khavrinen.lcs.mit.edu Subject: Re: Route table leaks In-Reply-To: <199911221552.KAA84691@khavrinen.lcs.mit.edu> References: <199911220150.UAA78559@khavrinen.lcs.mit.edu> <199911221552.KAA84691@khavrinen.lcs.mit.edu> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I've finally found the route table leak. At least I found _a_ leak, and I think it's the one that's been plaguing cvsup-master. I have a question or two (see below) before I commit the fix. Here's how to leak a route table entry. Establish a TCP connection with another machine so that you have a cloned route to that host. With the connection idle, use "route delete" to remove the cloned route. The route disappears from the routing table, but it is not freed. (The Leak.) Now cause some packets to travel on the connection. A new cloned route is created and added to the routing table. Each time you do that, you leak a struct rtentry and also a 32-byte chunk that's used to hold a couple of address structures. Routed is doing these route deletions regularly on cvsup-master. I haven't tried to figure out why. The leak is in rtalloc() and rtalloc_ign(), and here's the patch I'm using to fix it: Index: route.c =================================================================== RCS file: /home/ncvs/src/sys/net/route.c,v retrieving revision 1.53 diff -u -r1.53 route.c --- route.c 1999/08/28 00:48:28 1.53 +++ route.c 1999/11/27 01:21:56 @@ -88,8 +88,16 @@ rtalloc(ro) register struct route *ro; { - if (ro->ro_rt && ro->ro_rt->rt_ifp && (ro->ro_rt->rt_flags & RTF_UP)) - return; /* XXX */ + struct rtentry *rt; + int s; + + if ((rt = ro->ro_rt) != NULL) { + if (rt->rt_ifp != NULL && rt->rt_flags & RTF_UP) + return; + s = splnet(); + RTFREE(rt); + splx(s); + } ro->ro_rt = rtalloc1(&ro->ro_dst, 1, 0UL); } @@ -98,8 +106,16 @@ register struct route *ro; u_long ignore; { - if (ro->ro_rt && ro->ro_rt->rt_ifp && (ro->ro_rt->rt_flags & RTF_UP)) - return; /* XXX */ + struct rtentry *rt; + int s; + + if ((rt = ro->ro_rt) != NULL) { + if (rt->rt_ifp != NULL && rt->rt_flags & RTF_UP) + return; + s = splnet(); + RTFREE(rt); + splx(s); + } ro->ro_rt = rtalloc1(&ro->ro_dst, 1, ignore); } The original code was jamming a new pointer into ro->ro_rt, but it didn't free the old rtentry that was referenced there. Now for my questions: 1. Do I really need the splnet calls around RTFREE? 2. To eliminate all the duplicated code, shall I make rtalloc just call rtalloc_ign(ro, 0UL)? I assume that was avoided originally for performance reasons, but now there's more code than before. John -- John Polstra jdp@polstra.com 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 0:42:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id A8D1E14D41 for ; Sat, 27 Nov 1999 00:42:15 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem25.masternet.it [194.184.65.35]) by scotty.masternet.it (8.9.3/8.9.3) with ESMTP id JAA63925; Sat, 27 Nov 1999 09:42:07 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.2.0.58.19991127092240.00d3cec0@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sat, 27 Nov 1999 09:31:13 +0100 To: "Justin T. Gibbs" From: Gianmarco Giovannelli Subject: Re: AHC0 fireworks ? Cc: current@FreeBSD.ORG In-Reply-To: <199911252216.PAA00144@narnia.plutotech.com> References: <4.2.0.58.19991120091815.00c2ced0@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 25/11/99, Justin T. Gibbs wrote: > > But I have now a lot of errors (as you can see in this logs) on my scsi > chain. > > I had never experienced such things in the near past (even if as an old > > current user sometimes I see also worse things :-) > > > > Btw I don't see in the current mailing list threads about iussues on the > > scsi subsystem recently so it can be a problem related to my hardware > (even > > if I didn't experience it before)... > > > > I append the logs of my system (sorry for the long post): > > > > Now I am trying to make a "blind" make world to see it changes something... > >Parity errors indicate that data integrity is compromised on your SCSI >cable. Perhaps you bumped a connector, or a connector had been loose >for a long time and has just shifted to the point of causing a failure. >Open your case, reseat everything and see if the problem clears up. Hello everyone, sorry for the delay of this reply but I was out for work... The problem is gone now. I think it is due to the fact I disabled squid on one HD of my chain and I move the proxy server on another box. Perhaps it was the heavy load that makes the system unstable and HDs quite hot. I check also the cable, but I don't find anything odd... I hope everything is now solved... Thanks to everyone for the kind replies. Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 1:56:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (Postfix) with ESMTP id AC5CE14D09 for ; Sat, 27 Nov 1999 01:56:21 -0800 (PST) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@FreeBSD.ORG; Sat, 27 Nov 1999 10:56:19 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.3/8.9.3) id JAA00703; Sat, 27 Nov 1999 09:27:08 +0100 (CET) (envelope-from tanis) Date: Sat, 27 Nov 1999 09:27:08 +0100 From: German Tischler To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: Sv: Dr Neuhaus niccy go not recognized Message-ID: <19991127092708.A689@gaspode.franken.de> References: <19991107192844.A13696@gaspode.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Leif Neland on Sat, Nov 27, 1999 at 02:11:16AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 27, 1999 at 02:11:16AM +0100, Leif Neland wrote: > > > On Sun, 7 Nov 1999, German Tischler wrote: > > > On Sun, Nov 07, 1999 at 06:27:37PM +0100, Leif Neland wrote: > > > I'd like to test, So how do I proceed from here? > > > > Get the latest i4b-dev snapshot (00.83.11), get my patches > > from http://www.mayn.franken.de/home/tanis/i4b-11.tar.gz, > > get a recent current source tree, unpack i4b, unpack the > > layer1 patches over it, use the overinstall script, > > use > > > > device isic0 > > > > in your kernel config file (no at isa? or similiar). > > Compile the userland programs and install them, build a kernel > > and see if it works, and tell me what goes wrong. > > > > > Sorry, I have not had any time to do much testing; I now use a non-pnp itk > instead. I just wanted to do some dialin-logging on my voice-phones. Hellmuth has a working driver for the card now, but it will probably take some more time until it can be found inside an official release. -- German Tischler, tanis@gaspode.franken.de "There are two major products that come out of Berkeley: LSD and Unix. We don't believe this to be a coincidence." -- Jeremy S. Anderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 4:16:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 1076914DC9 for ; Sat, 27 Nov 1999 04:16:27 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id OAA01797 for ; Sat, 27 Nov 1999 14:16:25 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911271216.OAA01797@gratis.grondar.za> To: current@freebsd.org Subject: Make world broken in libc_r Date: Sat, 27 Nov 1999 14:16:24 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi "make world" is broken in libc_r. Simple fix is to replace all "socklen_t" with "int". M To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 6:40:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5C3FE14F9B for ; Sat, 27 Nov 1999 06:40:19 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id OAA87135; Sat, 27 Nov 1999 14:45:08 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 27 Nov 1999 14:45:07 +0000 (GMT) From: Doug Rabson To: Bill Paul Cc: current@freebsd.org Subject: Re: Update of if_dc driver In-Reply-To: <199911251954.OAA14315@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 25 Nov 1999, Bill Paul wrote: > My goal is to try and get this driver into 4.0 as soon as possible so > I can use it as a replacement for the al, ax, dm, pn and mx drivers. > However, there's a small problem: the de driver already supports the > 21143, although it does so poorly according to some people. We can't > have both drivers trying to support the same chip. I want to be able > to turn off 21143 support in if_de and let if_dc handle them, but I > don't want to annoy people who are using if_de with 21143 cards now > and not having any trouble. What do people think? Does anybody have > anything against me transfering support for the 21143 from if_de to > if_dc? Does anybody have a better idea? I'm open to suggestions. Why not use the probe priority system. For 21143 cards, return a negative number from de_probe and zero from dc_probe. If dc is present, it will win the auction and if not, de will get the hardware. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 7: 8:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id 3ADE214F9B for ; Sat, 27 Nov 1999 07:08:10 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (ppp148.dialup.st.keio.ac.jp [131.113.27.148]) by titanium.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id AAA03858; Sun, 28 Nov 1999 00:07:46 +0900 (JST) (envelope-from sanpei@sanpei.org) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id AAA03971; Sun, 28 Nov 1999 00:07:44 +0900 (JST) Message-Id: <199911271507.AAA03971@lavender.yy.cs.keio.ac.jp> To: freebsd-current@FreeBSD.org Subject: ESS1879, pnp_id patch and illegal probe about ESS1888 X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sun, 28 Nov 1999 00:07:43 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I play 4-current with MITSUBISHI AmityCN(NOTE-PC) which has ESS1879(ISA-PnP) Sound Chip. I hope to added below patch to 4-current sound driver. ---------- By the way I added only below line to kernel configuration file. device pcm0 But kernel probed ESS1888 as pcm0 and ESS1879 as pcm1. I think this NOTE-PC only has ESS1879 sound chip and I only use pcm1. I don't want to probe ESS1888. How can I solve below problem? From=20kernel message pcm0: at port 0x220-0x22f irq 5 drq 1 on isa0 device_probe_and_attach: pcm0 attach returned 6 unknown0: at port 0x800-0x807 on i= sa0 pcm1: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,= 0 on isa0 isa_dma_acquire: channel 1 already in use unknown1: at port 0x201 on isa0 ---------- --- MIHIRA Sanpei Yoshiro Yokohama, Japan. --- dev/sound/isa/sb.c.org Sat Nov 27 23:29:44 1999 +++ dev/sound/isa/sb.c Sat Nov 27 23:29:57 1999 @@ -1277,6 +1277,10 @@ s =3D "ESS1869"; break; = + case 0x79187316: /* ESS1879 */ + s =3D "ESS1879"; + break; + case 0x88187316: /* ESS1888 */ s =3D "ESS1888"; break; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 7:26:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from assurance.rstcorp.com (assurance.rstcorp.com [216.112.242.2]) by hub.freebsd.org (Postfix) with ESMTP id 73E9E15236 for ; Sat, 27 Nov 1999 07:26:33 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id KAA11063 for ; Sat, 27 Nov 1999 10:27:56 -0500 Received: from proxy.rstcorp.com(216.112.242.5) by assurance.rstcorp.com via smap (V2.0) id xma011059; Sat, 27 Nov 99 15:27:39 GMT Received: from jabberwock.rstcorp.com (jabberwock.rstcorp.com [192.168.2.98]) by sandbox.rstcorp.com (8.8.8+Sun/8.8.8) with ESMTP id KAA27392 for ; Sat, 27 Nov 1999 10:23:54 -0500 (EST) Received: by jabberwock.rstcorp.com (Postfix, from userid 93) id 77AB25B01; Sat, 27 Nov 1999 10:26:15 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14399.63511.296802.242618@jabberwock.rstcorp.com> Date: Sat, 27 Nov 1999 10:26:15 -0500 (EST) From: "Viren R.Shah" To: freebsd-current@freebsd.org Subject: repeatable crash in -current (softupdates, NFS) X-Mailer: VM 6.72 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R.Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running a -current system from Nov 26th (approx 4am EST). I can currently reliably crash the system by doing: ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html The crash only works when I do it on a NFS mounted filesystem. I'm using NFSv2/UDP. The server is a 3.2-STABLE FreeBSD box, running softupdates on the exported filesystem. I just checked that local filesystem on the server, and it is a 100% full. Can this just be put down to the known "softupdates full filesystem bug"? [BTW: the server hasn't crashed, it's only the FreeBSD client that crashes] Viren -- Viren R. Shah {viren @ rstcorp . com} Names : Vanadium(23) Iodine(53) RhEnium(75) Nitrogen(7) Density(g/mL): 5.8 4.92 21 0.0001251 Average Density: 7.93003 g/mL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 8:44: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id B6AB414CBA for ; Sat, 27 Nov 1999 08:43:43 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id QAA95106; Sat, 27 Nov 1999 16:49:17 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 27 Nov 1999 16:49:17 +0000 (GMT) From: Doug Rabson To: MIHIRA Sanpei Yoshiro Cc: freebsd-current@freebsd.org Subject: Re: ESS1879, pnp_id patch and illegal probe about ESS1888 In-Reply-To: <199911271507.AAA03971@lavender.yy.cs.keio.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Nov 1999, MIHIRA Sanpei Yoshiro wrote: > I play 4-current with MITSUBISHI AmityCN(NOTE-PC) which has > ESS1879(ISA-PnP) Sound Chip. > > I hope to added below patch to 4-current sound driver. > > ---------- > By the way I added only below line to kernel configuration file. > > device pcm0 > > But kernel probed ESS1888 as pcm0 and ESS1879 as pcm1. I think > this NOTE-PC only has ESS1879 sound chip and I only use pcm1. I > don't want to probe ESS1888. How can I solve below problem? In retrospect, the es1888 probe code I added for alphas was a mistake. I will disable that code and work on a better solution for alphas. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 9:10:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id B1B6B155A6; Sat, 27 Nov 1999 09:10:33 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id TAA02572; Sat, 27 Nov 1999 19:10:30 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911271710.TAA02572@gratis.grondar.za> To: dillon@freebsd.org Cc: current@freebsd.org Subject: mount_nfs broken Date: Sat, 27 Nov 1999 19:10:29 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Mount_mfs is broken - mounttab\* not present. M To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 9:21: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id C5A0C14BDA for ; Sat, 27 Nov 1999 09:20:44 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id RAA34415 for freebsd.org!current; Sat, 27 Nov 1999 17:20:42 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 27 Nov 1999 17:14:38 GMT X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 27 Nov 1999 17:14:37 +0000 To: current@freebsd.org From: Bob Bishop Subject: Odd panic Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, cvsup at Sat Nov 27 04:02:41 GMT 1999, looks like it went in the middle of starting up SCSI devices. This box is not SMP and has a 2940UW, my SMP -current box with a plain 2940 doesn't do this. ... da0 at ahc0 bus 0 target 0 lun 0 da0: Fied Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2b da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) fault code = supervisor read, page not present instruction pointer = 0x8:0xc01658e6 stack pointer = 0x10:0xc03a6f3c frame pointer = 0x10:0xc03a6f3c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enable, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = none kernel: type 12 trap, code=0 Stopped at devsw+0x6 cmpl $0, 0x2c(%eax) db> -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 9:21:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id BB02214CBA for ; Sat, 27 Nov 1999 09:21:32 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id SAA08328; Sat, 27 Nov 1999 18:01:54 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <199911271701.SAA08328@info.iet.unipi.it> Subject: Re: Update of if_dc driver In-Reply-To: from Doug Rabson at "Nov 27, 1999 02:45:07 pm" To: Doug Rabson Date: Sat, 27 Nov 1999 18:01:54 +0100 (CET) Cc: Bill Paul , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 25 Nov 1999, Bill Paul wrote: > > > My goal is to try and get this driver into 4.0 as soon as possible so > > I can use it as a replacement for the al, ax, dm, pn and mx drivers. > > However, there's a small problem: the de driver already supports the > > 21143, although it does so poorly according to some people. We can't > > have both drivers trying to support the same chip. I want to be able > > to turn off 21143 support in if_de and let if_dc handle them, but I having a more supported driver than "de" is always good. But as an interim solution (for 4.0 that is) maybe it is enough to make a small modification in the "de" probe routine and have a kernel option which tells the de driver whether or not recognize the 21143. Default would be "dc" handle everything, then if someone wants compatibility with the past they have to turn the option on (maybe at compile time) and make sure they don't put a "dc" driver in the kernel as well ? cheers luigi > > don't want to annoy people who are using if_de with 21143 cards now > > and not having any trouble. What do people think? Does anybody have > > anything against me transfering support for the 21143 from if_de to > > if_dc? Does anybody have a better idea? I'm open to suggestions. > > Why not use the probe priority system. For 21143 cards, return a negative > number from de_probe and zero from dc_probe. If dc is present, it will win > the auction and if not, de will get the hardware. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 9:25:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D862614C0F for ; Sat, 27 Nov 1999 09:25:17 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA12836; Sat, 27 Nov 1999 18:24:32 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Bob Bishop Cc: current@FreeBSD.ORG Subject: Re: Odd panic In-reply-to: Your message of "Sat, 27 Nov 1999 17:14:37 GMT." Date: Sat, 27 Nov 1999 18:24:31 +0100 Message-ID: <12834.943723471@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob, can you try to locate the symbols around 0xc01658e6 in your kernel ? Also, when you end in the debugger, always type "trace" so we get a stacktrace to look at. Poul-Henning In message , Bob Bishop writes: >Hi, > >cvsup at Sat Nov 27 04:02:41 GMT 1999, looks like it went in the middle of >starting up SCSI devices. This box is not SMP and has a 2940UW, my SMP >-current box with a plain 2940 doesn't do this. > >... >da0 at ahc0 bus 0 target 0 lun 0 >da0: Fied Direct Access SCSI-2 device >da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) >da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x2b >da1 at ahc0 bus 0 target 1 lun 0 >da1: Fixed Direct Access SCSI-2 device >da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled >da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) >fault code = supervisor read, page not present >instruction pointer = 0x8:0xc01658e6 >stack pointer = 0x10:0xc03a6f3c >frame pointer = 0x10:0xc03a6f3c >code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 >processor eflags = interrupt enable, resume, IOPL = 0 >current process = 0 (swapper) >interrupt mask = none >kernel: type 12 trap, code=0 >Stopped at devsw+0x6 cmpl $0, 0x2c(%eax) >db> > > >-- >Bob Bishop (0118) 977 4017 international code +44 118 >rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 10:17:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id BDFEC14C36 for ; Sat, 27 Nov 1999 10:17:32 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id TAA10347; Sat, 27 Nov 1999 19:17:31 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id TAA53868; Sat, 27 Nov 1999 19:17:30 +0100 (MET) Date: Sat, 27 Nov 1999 19:17:30 +0100 From: Eivind Eklund To: "Viren R.Shah" Cc: freebsd-current@FreeBSD.ORG Subject: Re: repeatable crash in -current (softupdates, NFS) Message-ID: <19991127191729.A53832@bitbox.follo.net> References: <14399.63511.296802.242618@jabberwock.rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14399.63511.296802.242618@jabberwock.rstcorp.com>; from viren@rstcorp.com on Sat, Nov 27, 1999 at 10:26:15AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 27, 1999 at 10:26:15AM -0500, Viren R.Shah wrote: > > I'm running a -current system from Nov 26th (approx 4am EST). > > I can currently reliably crash the system by doing: > > ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html > > > The crash only works when I do it on a NFS mounted filesystem. I'm > using NFSv2/UDP. The server is a 3.2-STABLE FreeBSD box, running > softupdates on the exported filesystem. I just checked that local > filesystem on the server, and it is a 100% full. Can this just be put > down to the known "softupdates full filesystem bug"? > > [BTW: the server hasn't crashed, it's only the FreeBSD client that > crashes] I *think* I know what this is due to - please upgrade src/sys/nfs/nfs_vnops.c to revision 1.146 (which I just committed) and try again. My bad. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 10:50:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 9BE8414CA4 for ; Sat, 27 Nov 1999 10:50:38 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id SAA35140; Sat, 27 Nov 1999 18:50:37 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 27 Nov 1999 18:48:32 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <12834.943723471@critter.freebsd.dk> References: Your message of "Sat, 27 Nov 1999 17:14:37 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 27 Nov 1999 18:48:29 +0000 To: Poul-Henning Kamp From: Bob Bishop Subject: Re: Odd panic Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, >can you try to locate the symbols around 0xc01658e6 in your kernel ? I mistranscribed that (really must get serial consoles sorted out), in fact it's: c0165e80 T devsw >Also, when you end in the debugger, always type "trace" so we get >a stacktrace to look at. Yes, sorry, got called for dinner at an inopportune moment ;-) devsw(ffffffff) at devsw+0x6 vfs_mountroot_try(c0391092,c02c531c) at vfs_mountroot_try+0xe9 vfs_mountroot(0,3a4c00,3ab000,0,c011d5e6) at vfs_mountroot+0x5a mi_startup(c03a6fb4,b0246,ffe,3ab000,c017ada1) at mi_startup+0x70 begin() at begin+0x4b Also, further back in the log there's a "setrootbyname failed". -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 10:55:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 88BED14CA4 for ; Sat, 27 Nov 1999 10:55:18 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA13157; Sat, 27 Nov 1999 19:54:41 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Bob Bishop Cc: current@FreeBSD.ORG Subject: Re: Odd panic In-reply-to: Your message of "Sat, 27 Nov 1999 18:48:29 GMT." Date: Sat, 27 Nov 1999 19:54:40 +0100 Message-ID: <13155.943728880@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bob Bishop writes: >devsw(ffffffff) at devsw+0x6 >vfs_mountroot_try(c0391092,c02c531c) at vfs_mountroot_try+0xe9 >vfs_mountroot(0,3a4c00,3ab000,0,c011d5e6) at vfs_mountroot+0x5a >mi_startup(c03a6fb4,b0246,ffe,3ab000,c017ada1) at mi_startup+0x70 >begin() at begin+0x4b > >Also, further back in the log there's a "setrootbyname failed". Somehow, and there are a fair number of ways this could happen, you ended up without a root device. What is in your /etc/fstab for the root fs ? Is your /boot up to date ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 11:12:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 81CE315501 for ; Sat, 27 Nov 1999 11:12:35 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id LAA15103; Sat, 27 Nov 1999 11:40:08 -0800 (PST) Date: Sat, 27 Nov 1999 11:40:08 -0800 (PST) From: Alfred Perlstein To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: Make world broken in libc_r In-Reply-To: <199911271216.OAA01797@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 27 Nov 1999, Mark Murray wrote: > Hi > > "make world" is broken in libc_r. Simple fix is to replace all > "socklen_t" with "int". libc_r likes to pull data from /usr/include instead of the source tree, "make includes" fixes this. I'm not sure if that's the correct way to fix it though. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 11:50:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 0AB7B14D74 for ; Sat, 27 Nov 1999 11:50:36 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id TAA35615; Sat, 27 Nov 1999 19:50:35 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 27 Nov 1999 19:40:44 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <13155.943728880@critter.freebsd.dk> References: Your message of "Sat, 27 Nov 1999 18:48:29 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 27 Nov 1999 19:40:42 +0000 To: Poul-Henning Kamp From: Bob Bishop Subject: Re: Odd panic Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 7:54 pm +0100 27/11/99, Poul-Henning Kamp wrote: >[...] >What is in your /etc/fstab for the root fs ? That was it: I was still running on /dev/sd*, looks like that just stopped working. Thanks -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 16: 5:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from volatile.by-tor.tacorp.net (ppp54-220.cpis.net [206.155.220.83]) by hub.freebsd.org (Postfix) with ESMTP id 8660B14C1E for ; Sat, 27 Nov 1999 16:05:48 -0800 (PST) (envelope-from by-tor@volatile.by-tor.tacorp.net) Received: (from by-tor@localhost) by volatile.by-tor.tacorp.net (8.9.3/8.9.3) id TAA00288; Sat, 27 Nov 1999 19:05:43 -0500 (EST) (envelope-from by-tor) Date: Sat, 27 Nov 1999 19:05:43 -0500 (EST) From: Wes Morgan X-Sender: by-tor@volatile.by-tor.tacorp.net To: FreeBSD-current@freebsd.org Subject: ATA and msdosfs problems / corruption Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When attempting to copy a large file over to a FAT partition, I had these errors pop up: Nov 27 16:26:59 volatile /kernel: ata0-master: ad_timeout: lost disk contact - resetting Nov 27 16:28:17 volatile /kernel: ata0: resetting devices .. WARNING: WAIT_READY active=ATA_ACTIVE_ATA Nov 27 16:28:17 volatile /kernel: done Nov 27 16:28:18 volatile /kernel: ta0-master: ad_timeout: lost disk contact - resetting Nov 27 16:28:18 volatile /kernel: ata0: resetting devices .. done Nov 27 16:28:18 volatile /kernel: ata0-master: ad_timeout: lost disk contact - resetting Nov 27 16:28:18 volatile /kernel: ata0: resetting devices .. done Nov 27 16:28:18 volatile /kernel: ata0-master: ad_timeout: lost disk contact - resetting Nov 27 16:28:19 volatile /kernel: ata0: resetting devices .. done Nov 27 16:28:19 volatile /kernel: ata0-master: ad_timeout: lost disk contact - resetting Nov 27 16:28:19 volatile /kernel: ata0: resetting devices .. done The errors continue until the system either panicked and rebooted or just plain rebooted, I was not at the console. However, the FAT volume was corrupted along with the boot loader (grub) overwritten to some extent. I'm not 100% sure if it was just the partition table or the entire volume. Next, I cvsup'd and built new kernel+modules, and the same error happened, but there was no reboot and a couple new error showed up: Nov 27 18:24:33 volatile /kernel: ad0: HARD WRITE error blk# 1912525 status=51 error=10 This error occurred for several different blocks. The two drives are identified as: ad0: ATA-? disk at ata0 as master ad0: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, DMA ad1: ATA-4 disk at ata0 as slave ad1: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 31 depth queue, DMA The motherboard is fairly old and does not support ATA/66 etc, and the drive with the fat fs has been rock solid so I doubt it has suddenly gone bad. I'd like to test this with DMA turned off, what flags will disable that? -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@engr.sc.edu _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 17: 3: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B618514BF3 for ; Sat, 27 Nov 1999 17:03:01 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id RAA11276 for ; Sat, 27 Nov 1999 17:03:01 -0800 (PST) Date: Sat, 27 Nov 1999 17:03:00 -0800 (PST) From: Julian Elischer To: current@freebsd.org Subject: State of Alpha support and Oracle. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am not sure of thw state of things but if someone wanted to run Oracle-8 and had an idea in their mind that they'd like to run it in an Alpha, tehn teh following questions would need to be answered (and I dont know the answers) 1/ does FreeBSD-alpha support SMB 2/ is there a binary version of Oracle we can run on the alpha? 3/ does the alpha give a big increase in speed over the same dollars spent on x86? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 17:52:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles511.castles.com [208.214.165.75]) by hub.freebsd.org (Postfix) with ESMTP id B46A714CCB for ; Sat, 27 Nov 1999 17:52:47 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA96659; Sat, 27 Nov 1999 17:53:21 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911280153.RAA96659@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Julian Elischer Cc: current@freebsd.org Subject: Re: State of Alpha support and Oracle. In-reply-to: Your message of "Sat, 27 Nov 1999 17:03:00 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Nov 1999 17:53:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am not sure of thw state of things but if someone wanted to run Oracle-8 > and had an idea in their mind that they'd like to run it in an Alpha, > tehn teh following questions would need to be answered (and I dont know > the answers) > > 1/ does FreeBSD-alpha support SMB Samba works just fine. But I suspect that you meant "SMP", and the answer there is "no". > 2/ is there a binary version of Oracle we can run on the alpha? The Tru64 version _might_ work. > 3/ does the alpha give a big increase in speed over the same dollars spent > on x86? Not under Oracle at the low end, no. If all you want is an oracle-like database however, I would recommend that you look at Linter (www.relcom.ru, IIRC). OCI-compatible, and much, much cheaper. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 18:36:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7349114CA4 for ; Sat, 27 Nov 1999 18:36:42 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA40052; Sat, 27 Nov 1999 18:36:33 -0800 (PST) (envelope-from dillon) Date: Sat, 27 Nov 1999 18:36:33 -0800 (PST) From: Matthew Dillon Message-Id: <199911280236.SAA40052@apollo.backplane.com> To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: mount_nfs broken References: <199911271710.TAA02572@gratis.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Hi : :Mount_mfs is broken - mounttab\* not present. : :M Could you be more specific? It seems to work for me (I removed /var/db/mounttab and tried it with a new build and it did work). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 18:43:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id F195414D8B for ; Sat, 27 Nov 1999 18:43:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA40107; Sat, 27 Nov 1999 18:43:27 -0800 (PST) (envelope-from dillon) Date: Sat, 27 Nov 1999 18:43:27 -0800 (PST) From: Matthew Dillon Message-Id: <199911280243.SAA40107@apollo.backplane.com> To: John Polstra Cc: wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: Route table leaks References: <199911220150.UAA78559@khavrinen.lcs.mit.edu> <199911221552.KAA84691@khavrinen.lcs.mit.edu> <199911270141.RAA29416@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :+ s = splnet(); :+ RTFREE(rt); :+ splx(s); :... :+ s = splnet(); :+ RTFREE(rt); :+ splx(s); :+ } : ro->ro_rt = rtalloc1(&ro->ro_dst, 1, ignore); : } : : :Now for my questions: : :1. Do I really need the splnet calls around RTFREE? Yes. Because the route table may be flushed from an interrupt in a low memory situation. :2. To eliminate all the duplicated code, shall I make rtalloc just :call rtalloc_ign(ro, 0UL)? I assume that was avoided originally for :performance reasons, but now there's more code than before. : :John :-- : John Polstra jdp@polstra.com Hmm. One trick I used in the VM code was to put the common code in an inline static function and leave the external functions broken out to avoid an unnecessary call chain. So, for example, if rtalloc() and rtalloc_ign() require a bunch of extra code prior to calling rtalloc1(), then a good solution would be to put the bulk of that code or perhaps even all of it in an inline and then have rtalloc() and rtalloc_ign() both call the inline with appropriate arguments. Remember that inline function calls *WILL* optimize constants passed as arguments. It's a very effective way to genericize a block of code without creating any procedural recursion. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 18:57:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4F5A814CA5 for ; Sat, 27 Nov 1999 18:57:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA40292; Sat, 27 Nov 1999 18:57:28 -0800 (PST) (envelope-from dillon) Date: Sat, 27 Nov 1999 18:57:28 -0800 (PST) From: Matthew Dillon Message-Id: <199911280257.SAA40292@apollo.backplane.com> To: David Greenman Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: Which is the truth? (sycalls and traps) References: <199911252215.OAA14800@implode.root.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>Am I also right in assuming that all the registers that the user was :>running when they did the KERNCALL have been saved on the KERNEL stack by :>the time that the above routines are called? : : No, that's what the pushal (push all) does. : :-DG : :David Greenman pushing/popping integer registers doesn't really take a whole lot of time. The real overhead is with all the junk we have on entering and exiting from a kernel context from/to a user context. In fact, for kernel threads it's even easier: If you are calling the switch code synchronously then, of course, the scratch-on-call registers need not be saved or restored either. It's as simple as the code I've shown below, taken from one of my other projects: pushfl pushl %ebx pushl %ebp pushl %esi pushl %edi pushl $myresumefunction movl %esp,ta_Ctx+mc_SP(%ecx) Switch to new task: movl ta_Ctx+mc_SP(%ecx),%esp ret And the restore function: popl %edi popl %esi popl %ebp popl %ebx popfl ... Enhance as required (i.e. other registers need to be added if an interrupt, segment registers, and so forth. note: pushal/popal does not mess with the segment registers or the FP registers. It is not all-inclusive. Only the main registers are pushed/popped. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 19:11:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3CF4E14D75 for ; Sat, 27 Nov 1999 19:11:43 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA40521; Sat, 27 Nov 1999 19:11:41 -0800 (PST) (envelope-from dillon) Date: Sat, 27 Nov 1999 19:11:41 -0800 (PST) From: Matthew Dillon Message-Id: <199911280311.TAA40521@apollo.backplane.com> To: Matthew Dillon Cc: David Greenman , Julian Elischer , current@FreeBSD.ORG Subject: Re: Which is the truth? (sycalls and traps) References: <199911252215.OAA14800@implode.root.com> <199911280257.SAA40292@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, let me add an addendum, I didn't answer the original question! :(Julian wrote...) : :Am I also right in assuming that all the registers that the user was :running when they did the KERNCALL have been saved on the KERNEL stack by :the time that the above routines are called? : :(It's a pitty because if they were saved on the USER stack before teh :kernel switched to the kernel stack it would have a great simplifying :effect on kernel threads support :-) (I know that could lead to traps :during saving the context but..) No, the userland code runs the system call as if it were almost a normal subroutine call. Embedded kernels I have written make use of a couple of tricks, but two primary ones: (A) A system call is like a subroutine call so you don't have to save/restore scratch-on-call registers, and (B) When making a subroutine call from the syscall or interrupt entry code, the procedure being called will save/restore certain registers so you don't have to. So the system call does not theoretically have to save every register and in fact can often get away with saving a minimal set of registers. But! Our current kernel implementation generates a 'common' trap frame for all sorts of things and certain calls modify the return registers, so messing with it would be problematic. Julian, you shouldn't worry about userland<->kernel context switch so much. The overhead for going into the kernel and coming out again, if all the cruft is removed, is *very* tiny -- it's almost like a subroutine call. We can optimize out the cruft over time. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 19:22: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles511.castles.com [208.214.165.75]) by hub.freebsd.org (Postfix) with ESMTP id 2B5AF14EF6 for ; Sat, 27 Nov 1999 19:22:03 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA97403; Sat, 27 Nov 1999 19:22:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911280322.TAA97403@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bob Bishop Cc: current@FreeBSD.ORG Subject: Re: Odd panic In-reply-to: Your message of "Sat, 27 Nov 1999 19:40:42 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Nov 1999 19:22:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > At 7:54 pm +0100 27/11/99, Poul-Henning Kamp wrote: > >[...] > >What is in your /etc/fstab for the root fs ? > > That was it: I was still running on /dev/sd*, looks like that just stopped > working. Thanks A week or two back, actually. But you should have received a more civilised failure than the one you did. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 21:11:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from azazel.zer0.org (azazel.zer0.org [209.133.53.200]) by hub.freebsd.org (Postfix) with ESMTP id C336D14BDA; Sat, 27 Nov 1999 21:11:14 -0800 (PST) (envelope-from gsutter@azazel.zer0.org) Received: (from gsutter@localhost) by azazel.zer0.org (8.9.3/8.9.2) id VAA80666; Sat, 27 Nov 1999 21:10:05 -0800 (PST) (envelope-from gsutter) Date: Sat, 27 Nov 1999 21:10:01 -0800 From: Gregory Sutter To: Mike Smith Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: State of Alpha support and Oracle. Message-ID: <19991127211001.E13897@azazel.zer0.org> References: <199911280153.RAA96659@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199911280153.RAA96659@mass.cdrom.com> Organization: Zer0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 27, 1999 at 05:53:21PM -0800, Mike Smith wrote: > > If all you want is an oracle-like database however, I would recommend > that you look at Linter (www.relcom.ru, IIRC). OCI-compatible, and much, > much cheaper. http://www.relex.ru/linter/ Greg -- Gregory S. Sutter Cole's Law: Thinly sliced cabbage. mailto:gsutter@pobox.com http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 21:45:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id B645814C10 for ; Sat, 27 Nov 1999 21:45:20 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 2CB181C6D; Sun, 28 Nov 1999 13:45:19 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: David Greenman , Julian Elischer , current@FreeBSD.ORG Subject: Re: Which is the truth? (sycalls and traps) In-Reply-To: Message from Matthew Dillon of "Sat, 27 Nov 1999 19:11:41 PST." <199911280311.TAA40521@apollo.backplane.com> Date: Sun, 28 Nov 1999 13:45:19 +0800 From: Peter Wemm Message-Id: <19991128054519.2CB181C6D@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > Oops, let me add an addendum, I didn't answer the original question! > > :(Julian wrote...) > : > :Am I also right in assuming that all the registers that the user was > :running when they did the KERNCALL have been saved on the KERNEL stack by > :the time that the above routines are called? > : > :(It's a pitty because if they were saved on the USER stack before teh > :kernel switched to the kernel stack it would have a great simplifying > :effect on kernel threads support :-) (I know that could lead to traps > :during saving the context but..) > [..] > Julian, you shouldn't worry about userland<->kernel context switch so muc h. > The overhead for going into the kernel and coming out again, if all the > cruft is removed, is *very* tiny -- it's almost like a subroutine call. I was rather suprised when I found out just how expensive kernel entry was some time ago.. What I was doing was a reentrant syscall that aquired no locks and ran about 5 instructions in kernel context.. Anyway, it took something like 300 times longer to do that (called via int $0x81) than to do a 'call' to equivalent code in userland. Anyway, with overheads on that scale, whether we push 5 or 8 or whatever registers in the handler is almost lost in the noise. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 22:33:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 4879C14A26 for ; Sat, 27 Nov 1999 22:33:51 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA04757; Sun, 28 Nov 1999 08:33:43 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911280633.IAA04757@gratis.grondar.za> To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: mount_nfs broken Date: Sun, 28 Nov 1999 08:33:42 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : > :Hi > : > :Mount_mfs is broken - mounttab\* not present. > : > :M > > Could you be more specific? It seems to work for me (I removed > /var/db/mounttab and tried it with a new build and it did work). Damn. I screwed up the reporting bigtime. It is mount_nfs, and there is mention of mounttab.c in the Makefile, but no mounttab.c anywhere in the source tree. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 27 23:14:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from sorrow.havoc.vtic.net (sorrow.havoc.vtic.net [216.38.135.21]) by hub.freebsd.org (Postfix) with ESMTP id B9A6B14D75; Sat, 27 Nov 1999 23:14:26 -0800 (PST) (envelope-from igo@vtic.net) Received: from localhost (igo@localhost) by sorrow.havoc.vtic.net (8.9.1b+Sun/8.9.1) with ESMTP id XAA21515; Sat, 27 Nov 1999 23:14:23 -0800 (PST) Date: Sat, 27 Nov 1999 23:14:22 -0800 (PST) From: Lester Igo X-Sender: igo@sorrow.havoc.vtic.net To: Eivind Eklund Cc: "Viren R.Shah" , freebsd-current@freebsd.org Subject: Re: repeatable crash in -current (softupdates, NFS) In-Reply-To: <19991127191729.A53832@bitbox.follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 27 Nov 1999, Eivind Eklund wrote: > On Sat, Nov 27, 1999 at 10:26:15AM -0500, Viren R.Shah wrote: > > > > I'm running a -current system from Nov 26th (approx 4am EST). > > > > I can currently reliably crash the system by doing: > > > > ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html > > > > > > The crash only works when I do it on a NFS mounted filesystem. I'm > > using NFSv2/UDP. The server is a 3.2-STABLE FreeBSD box, running > > softupdates on the exported filesystem. I just checked that local > > filesystem on the server, and it is a 100% full. Can this just be put > > down to the known "softupdates full filesystem bug"? > > > > [BTW: the server hasn't crashed, it's only the FreeBSD client that > > crashes] > > I *think* I know what this is due to - please upgrade > src/sys/nfs/nfs_vnops.c to revision 1.146 (which I just committed) and > try again. > My bad. > Eivind. Ouch! I noticed this problem as a system crash while starting netscape under the condition that it was able to write the lock file (err soft link), but since it created the link before the kernel panic I thought it was a strange FreeBSD->Sun NFS v2 oddity with the profile reading and some sort of file locking problem. I will build a fresh -current and let you know if it fixes the problem! Thanks! -- Lester Igo igo@vtic.net http://www.vtic.net/~igo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message