From owner-freebsd-current Sun May 25 00:12:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA12035 for current-outgoing; Sun, 25 May 1997 00:12:15 -0700 (PDT) Received: from goethe.c4systm.com (root@goethe.c4systm.com [204.120.124.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA12030 for ; Sun, 25 May 1997 00:12:13 -0700 (PDT) Received: from goethe.c4systm.com (jds@localhost [127.0.0.1]) by goethe.c4systm.com (8.7.5/8.7.3) with SMTP id DAA08306 for ; Sun, 25 May 1997 03:12:12 -0400 (EDT) Message-ID: <3387E64B.41C67EA6@c4systm.com> Date: Sun, 25 May 1997 03:12:11 -0400 From: "James D. Stewart" Organization: C4 Systems, Inc. X-Mailer: Mozilla 3.01Gold (X11; U; FreeBSD 2.2-960801-SNAP i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe freebsd-current From owner-freebsd-current Sun May 25 02:54:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA17846 for current-outgoing; Sun, 25 May 1997 02:54:49 -0700 (PDT) Received: from terra.stack.nl (terra.stack.nl [131.155.140.128]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA17841 for ; Sun, 25 May 1997 02:54:46 -0700 (PDT) Received: from xaa.stack.nl (uucp@localhost) by terra.stack.nl (8.8.5) with UUCP id LAA25834 for freebsd-current@freebsd.org; Sun, 25 May 1997 11:54:42 +0200 (MET DST) Received: (from freebsd@localhost) by xaa.stack.nl (8.8.5/8.8.2) id LAA01908; Sun, 25 May 1997 11:54:21 +0200 (MET DST) Message-ID: <19970525115421.42464@xaa.stack.nl> Date: Sun, 25 May 1997 11:54:21 +0200 From: Mark Huizer To: freebsd-current@freebsd.org Subject: src-cur.2896.gz Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi hi, does anyone have a src-cur.2896 lying around somewhere?? It wasn't on the mailinglist, and is not on ftp.freebsd.org :-( Mark From owner-freebsd-current Sun May 25 03:38:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA18985 for current-outgoing; Sun, 25 May 1997 03:38:13 -0700 (PDT) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA18980 for ; Sun, 25 May 1997 03:38:09 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id MAA24313; Sun, 25 May 1997 12:38:04 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199705251038.MAA24313@helbig.informatik.ba-stuttgart.de> Subject: Re: src-cur.2896.gz In-Reply-To: <19970525115421.42464@xaa.stack.nl> from Mark Huizer at "May 25, 97 11:54:21 am" To: xaa@stack.nl (Mark Huizer) Date: Sun, 25 May 1997 12:38:02 +0200 (MET DST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi hi, does anyone have a src-cur.2896 lying around somewhere?? It wasn't > on the mailinglist, and is not on ftp.freebsd.org :-( Try the following url: fetch ftp://ftp.uni-trier.de/pub/unix/systems/BSD/FreeBSD/CTM/src-cur/src-cur.2896.gz I do not know why we are losing so many ctm deltas, but it sure should be fixed! Wolfgang From owner-freebsd-current Sun May 25 07:42:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA24376 for current-outgoing; Sun, 25 May 1997 07:42:56 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA24370 for ; Sun, 25 May 1997 07:42:53 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id QAA29090 for ; Sun, 25 May 1997 16:44:15 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id QAA17098 for freebsd-current@freefall.cdrom.com; Sun, 25 May 1997 16:45:40 +0200 (MEST) Date: Sun, 25 May 1997 16:45:40 +0200 (MEST) From: Christoph Kukulies Message-Id: <199705251445.QAA17098@gil.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: protosw.h - a small patch - please apply Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk compiling ip_fil3.2a7 still has some rough edges and it would run a bit smoother when the following patch could be applied: *** protosw.h.orig Sun May 25 16:41:54 1997 --- protosw.h Sun May 25 16:36:10 1997 *************** *** 45,50 **** --- 45,51 ---- struct sockproto; struct stat; struct uio; + struct proc; /* * Protocol switch table. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Sun May 25 10:40:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA00387 for current-outgoing; Sun, 25 May 1997 10:40:29 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA00375 for ; Sun, 25 May 1997 10:40:22 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id TAA10903 for ; Sun, 25 May 1997 19:40:11 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id TAA15708 for freebsd-current@FreeBSD.ORG; Sun, 25 May 1997 19:39:34 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id TAA10887; Sun, 25 May 1997 19:35:59 +0200 (CEST) Message-ID: <19970525193558.22470@keltia.freenix.fr> Date: Sun, 25 May 1997 19:35:58 +0200 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Weird behaviour from the Linux emulator Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3323 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The Linux emulator has a weird idea of the filesystem, mixing the real one with the one rooted at /compat/linux. To see this, open Acroread (or any other Linux application), open "/" and then goes to "/usr". Watch now the program displaying everything that's in "/compat/linux/usr" instead of the real "/usr"... I understand the need to shadow the real filesystem but it should be done only for the search for libraries/binaries, not for every open(2) call. I don't know how to fix it but it makes some applications hard -- if not impossible -- to use. I found it when a Linux backup program ended up confused about the filesystem and couldn't complete any backup. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #10: Fri May 23 22:47:39 CEST 1997 From owner-freebsd-current Sun May 25 12:39:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA05580 for current-outgoing; Sun, 25 May 1997 12:39:31 -0700 (PDT) Received: from tulsix.utulsa.edu (tulsix.utulsa.edu [129.244.22.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA05575 for ; Sun, 25 May 1997 12:39:28 -0700 (PDT) Received: by tulsix.utulsa.edu (1.37.109.4/16.2) id AA12219; Sun, 25 May 97 14:33:01 -0500 From: Tom Jackson Message-Id: <9705251933.AA12219@tulsix.utulsa.edu> Subject: Re: src-cur.2896.gz To: xaa@stack.nl (Mark Huizer) Date: Sun, 25 May 1997 14:33:00 -0600 (CDT) Cc: freebsd-current@freebsd.org In-Reply-To: <19970525115421.42464@xaa.stack.nl> from "Mark Huizer" at May 25, 97 11:54:21 am Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Hi hi, does anyone have a src-cur.2896 lying around somewhere?? It wasn't > on the mailinglist, and is not on ftp.freebsd.org :-( > > Mark > Strange as this may seem, go to ftp.uni-trier.de/pub/unix/FreeBSD/CTM/src-cur and you will find the missing delta there. Go figure, Germany has it but California doesn't. Tom From owner-freebsd-current Sun May 25 12:52:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA06257 for current-outgoing; Sun, 25 May 1997 12:52:12 -0700 (PDT) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA06246 for ; Sun, 25 May 1997 12:52:05 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id VAA00443 for FreeBSD-current@FreeBSD.org; Sun, 25 May 1997 21:51:22 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199705251951.VAA00443@helbig.informatik.ba-stuttgart.de> Subject: sio1: 64 events for device with no tp To: FreeBSD-current@FreeBSD.org Date: Sun, 25 May 1997 21:51:22 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, The above kernel message shows up during booting for both sio0 and sio1. Up to now its just annoying -- the messages are repeated once syslogd is started. This behaviour seems buggy to me. These messages were not by the release 1.164 sio driver. The kernel is pretty current, using release 1.169 of sio.c. (FreeBSD-current) Only the serial interface 0 is used on this system, connected to a mouse. It still works. Maybe there is some bug in sio.c to be fixed ? Wolfgang From owner-freebsd-current Sun May 25 13:17:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA07390 for current-outgoing; Sun, 25 May 1997 13:17:03 -0700 (PDT) Received: from mail.scsn.net (scsn.net [206.25.246.12]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA07384 for ; Sun, 25 May 1997 13:16:58 -0700 (PDT) Received: from cola47.scsn.net ([206.25.247.47]) by mail.scsn.net (Post.Office MTA v3.0 release 0121 ID# 0-32322U5000L100S10000) with ESMTP id AAA171; Sun, 25 May 1997 16:09:35 -0400 Received: (from root@localhost) by cola47.scsn.net (8.8.5/8.8.5) id QAA00503; Sun, 25 May 1997 16:16:41 -0400 (EDT) Message-ID: <19970525161640.02033@cola47.scsn.net> Date: Sun, 25 May 1997 16:16:40 -0400 From: "Donald J. Maddox" To: Wolfgang Helbig Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: sio1: 64 events for device with no tp Reply-To: dmaddox@scsn.net References: <199705251951.VAA00443@helbig.informatik.ba-stuttgart.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199705251951.VAA00443@helbig.informatik.ba-stuttgart.de>; from Wolfgang Helbig on Sun, May 25, 1997 at 09:51:22PM +0200 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, May 25, 1997 at 09:51:22PM +0200, Wolfgang Helbig wrote: > Hi, > > The above kernel message shows up during booting for both sio0 and sio1. > Up to now its just annoying -- the messages are repeated once > syslogd is started. > > This behaviour seems buggy to me. These messages were not > by the release 1.164 sio driver. The kernel is pretty current, > using release 1.169 of sio.c. (FreeBSD-current) > > Only the serial interface 0 is used on this system, connected to > a mouse. It still works. > > Maybe there is some bug in sio.c to be fixed ? The following is a patch from phk that will stop the messages... If you want to enable the COM_BIGFIFO stuff, set FLAGS=0x20000 in the sio lines in your config file (COM_BIGFIFO doesn't work for my Motorola ModemSurfer Modem. YMMV). ----------------------------CUT HERE----------------------- Index: sio.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/sio.c,v retrieving revision 1.167 diff -u -r1.167 sio.c --- sio.c 1997/05/18 21:22:11 1.167 +++ sio.c 1997/05/22 06:50:53 @@ -121,6 +121,7 @@ #define COM_NOFIFO(dev) ((dev)->id_flags & 0x02) #define COM_VERBOSE(dev) ((dev)->id_flags & 0x80) #define COM_NOTST3(dev) ((dev)->id_flags & 0x10000) +#define COM_BIGFIFO(dev) ((dev)->id_flags & 0x20000) #define com_scr 7 /* scratch register for 16450-16550 (R/W) */ @@ -884,45 +885,40 @@ case FIFO_RX_HIGH: if (COM_NOFIFO(isdp)) { printf(" 16550A fifo disabled"); + } else if (!COM_BIGFIFO(isdp)) { + printf(" 16550A"); } else { /* Detect the fifo size. */ int i, n; /* Enable and reset the FIFO. */ - outb (iobase+com_fifo, FIFO_ENABLE | FIFO_RCV_RST | FIFO_XMT_RST); + outb(iobase+com_fifo, FIFO_ENABLE | FIFO_RCV_RST | FIFO_XMT_RST); - /* Set the loopback mode, 57600 baud. */ - outb (iobase+com_cfcr, CFCR_DLAB); - outb (iobase+com_dlbh, 0); - outb (iobase+com_dlbl, 2); - outb (iobase+com_cfcr, CFCR_8BITS); - outb (iobase+com_mcr, MCR_LOOPBACK); - inb (iobase+com_lsr); + /* Set the loopback mode, and very low baud. */ + /* XXX: What happens if this is a serial console ? */ + outb(iobase+com_cfcr, CFCR_DLAB); + outb(iobase+com_dlbh, 0xff); + outb(iobase+com_dlbl, 0xff); + outb(iobase+com_cfcr, CFCR_8BITS); + outb(iobase+com_mcr, MCR_LOOPBACK); + inb(iobase+com_lsr); /* Put data into transmit FIFO and wait until overrun. */ for (i=n=0; i<20000; ++i) { - unsigned char lsr = inb (iobase+com_lsr); + unsigned char lsr = inb(iobase+com_lsr); if (lsr & LSR_OE) break; if (lsr & LSR_TXRDY) { - outb (iobase+com_data, 0x5A); - ++n; + outb(iobase+com_data, 0x5A); + n++; } } - outb (iobase+com_mcr, 0); - outb (iobase+com_fifo, 0); + outb(iobase+com_mcr, com->mcr_image); + outb(iobase+com_fifo, 0); com->hasfifo = TRUE; - if (n > 40) { - com->tx_fifo_size = 64; - printf(" 16750"); - } else if (n > 24) { - com->tx_fifo_size = 32; - printf(" 16650"); - } else { - com->tx_fifo_size = 16; - printf(" 16550A"); - } + com->tx_fifo_size = n; + printf(" 16550A lookalike with %d bytes xmit-FIFO",n); #ifdef COM_ESP for (espp = likely_esp_ports; *espp != 0; espp++) if (espattach(isdp, com, *espp)) { @@ -931,31 +927,6 @@ } #endif } -#if 0 - /* - * Check for the Startech ST16C650 chip. - * it has a shadow register under the com_iir, - * which can only be accessed when cfcr == 0xff - */ - { - u_char i, j; - - i = inb(iobase + com_iir); - outb(iobase + com_cfcr, 0xff); - outb(iobase + com_iir, 0x0); - outb(iobase + com_cfcr, CFCR_8BITS); - j = inb(iobase + com_iir); - outb(iobase + com_iir, i); - if (i != j) { - printf(" 16550A"); - } else { - com->tx_fifo_size = 32; - printf(" 16650"); - } - if (!com->tx_fifo_size) - printf(" fifo disabled"); - } -#endif break; } #ifdef COM_ESP From owner-freebsd-current Sun May 25 13:43:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA08719 for current-outgoing; Sun, 25 May 1997 13:43:41 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA08711 for ; Sun, 25 May 1997 13:43:38 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA12466; Sun, 25 May 1997 13:39:23 -0700 From: Terry Lambert Message-Id: <199705252039.NAA12466@phaeton.artisoft.com> Subject: Re: cd9660 w/ Joliet extensions To: hoek@hwcn.org Date: Sun, 25 May 1997 13:39:23 -0700 (MST) Cc: terry@lambert.org, jkh@time.cdrom.com, hosokawa@ntc.keio.ac.jp, current@FreeBSD.ORG In-Reply-To: from "Tim Vanderhoek" at May 24, 97 07:16:34 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Hmmm. I've had many people tell me that they're very very happy that > > > the FreeBSD CD does not have an autorun.inf file and that this feature > > > is the most evil thing they ever experienced in Win95. :-) > > > > Only if it's not correctly implemented. > > Although, I would be willing to bet it's the fact that things > start happening without an explicit command from the user "run > this program" that bothers people, not the fact that it's > incorrectly implemented. > > The auto-run feature, can, of course, be disabled by pressing > some key while putting in the CD (is it what? Shift? I can't > remember off-hand... :(. You can remove the AutoRun shell extention (nothing will autorun) using RegEdit: My Computer HKEY_LOCAL_MACHINE SOFTWARE Classes AutoRun You can also turn of autoinsertion notification (the trigger): Right-button-"Properties..." on "My Computer" "Device Manager" tab on "System Properties" page Select your CDROM in the treeview window... Click the "Properties" button "Settings" tab on "CDROM Properties" page In the "Options" group box, uncheck "Auto insert notification" Click "OK". Click "OK". People who find it disconcerting (that "disk inserting" ;) causes an AutoRun) probably are not well enough educated about their OS to turn it off. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun May 25 14:41:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA10623 for current-outgoing; Sun, 25 May 1997 14:41:38 -0700 (PDT) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA10618 for ; Sun, 25 May 1997 14:41:35 -0700 (PDT) Received: from AMPERSAND (ztm04-08.dial.xs4all.nl [194.109.32.105]) by smtp1.xs4all.nl (8.7.6/XS4ALL) with SMTP id XAA26208 for ; Sun, 25 May 1997 23:41:32 +0200 (MET DST) Message-Id: <199705252141.XAA26208@smtp1.xs4all.nl> Comments: Authenticated sender is From: "Jeroen" Organization: Twiddle To: current@FreeBSD.ORG Date: Sun, 25 May 1997 23:40:02 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: cd9660 w/ Joliet extensions Priority: normal X-mailer: Pegasus Mail for Windows (v2.31) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > People who find it disconcerting (that "disk inserting" ;) causes > an AutoRun) probably are not well enough educated about their OS > to turn it off. *please* move this BS thread to -chat.. don't use -current to chitchat about the windows registry! > Regards, > Terry Lambert > terry@lambert.org Jeroen From owner-freebsd-current Sun May 25 14:44:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA10723 for current-outgoing; Sun, 25 May 1997 14:44:19 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA10718 for ; Sun, 25 May 1997 14:44:17 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA12558; Sun, 25 May 1997 14:41:35 -0700 From: Terry Lambert Message-Id: <199705252141.OAA12558@phaeton.artisoft.com> Subject: Re: Weird behaviour from the Linux emulator To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Sun, 25 May 1997 14:41:35 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19970525193558.22470@keltia.freenix.fr> from "Ollivier Robert" at May 25, 97 07:35:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The Linux emulator has a weird idea of the filesystem, mixing the real one > with the one rooted at /compat/linux. To see this, open Acroread (or any > other Linux application), open "/" and then goes to "/usr". Watch now the > program displaying everything that's in "/compat/linux/usr" instead of the > real "/usr"... > > I understand the need to shadow the real filesystem but it should be done > only for the search for libraries/binaries, not for every open(2) call. It also needs to be done for /etc/resolv.conf and for open for mmap() of shared libraries (since we can't tell if the open is for a shared library or not). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun May 25 15:21:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA11999 for current-outgoing; Sun, 25 May 1997 15:21:08 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA11994 for ; Sun, 25 May 1997 15:21:05 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA27831 for FreeBSD-current@FreeBSD.ORG; Mon, 26 May 1997 00:20:53 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id AAA21144; Mon, 26 May 1997 00:17:36 +0200 (MET DST) Message-ID: <19970526001736.DH53771@uriah.heep.sax.de> Date: Mon, 26 May 1997 00:17:36 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: FreeBSD-current@FreeBSD.ORG Subject: Re: sio1: 64 events for device with no tp References: <199705251951.VAA00443@helbig.informatik.ba-stuttgart.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199705251951.VAA00443@helbig.informatik.ba-stuttgart.de>; from Wolfgang Helbig on May 25, 1997 21:51:22 +0200 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Wolfgang Helbig wrote: > The above kernel message shows up during booting for both sio0 and sio1. I've also seen it, on a machine with no serial devices actually attached. Both counts for both channels were the same. Sounds like a misdirected IRQ. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun May 25 15:46:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA13147 for current-outgoing; Sun, 25 May 1997 15:46:15 -0700 (PDT) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA13137 for ; Sun, 25 May 1997 15:46:11 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id AAA00220; Mon, 26 May 1997 00:45:59 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199705252245.AAA00220@helbig.informatik.ba-stuttgart.de> Subject: Re: sio1: 64 events for device with no tp In-Reply-To: <19970525161640.02033@cola47.scsn.net> from "Donald J. Maddox" at "May 25, 97 04:16:40 pm" To: dmaddox@scsn.net Date: Mon, 26 May 1997 00:45:59 +0200 (MET DST) Cc: FreeBSD-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > On Sun, May 25, 1997 at 09:51:22PM +0200, Wolfgang Helbig wrote: > > Hi, > > > > The above kernel message shows up during booting for both sio0 and sio1. > > Up to now its just annoying -- the messages are repeated once > > syslogd is started. > > > > This behaviour seems buggy to me. These messages were not > > by the release 1.164 sio driver. The kernel is pretty current, > > using release 1.169 of sio.c. (FreeBSD-current) > > > > Only the serial interface 0 is used on this system, connected to > > a mouse. It still works. > > > > Maybe there is some bug in sio.c to be fixed ? > > The following is a patch from phk that will stop the messages... If you > want to enable the COM_BIGFIFO stuff, set FLAGS=0x20000 in the sio lines in > your config file (COM_BIGFIFO doesn't work for my Motorola ModemSurfer Modem. > YMMV). [patch omitted ...] Thank you! The patch works fine for me. Question: Why isn't it committed? Wolfgang From owner-freebsd-current Sun May 25 15:53:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA13465 for current-outgoing; Sun, 25 May 1997 15:53:13 -0700 (PDT) Received: from mail.scsn.net (scsn.net [206.25.246.12]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA13459 for ; Sun, 25 May 1997 15:53:11 -0700 (PDT) Received: from cola52.scsn.net ([206.25.247.52]) by mail.scsn.net (Post.Office MTA v3.0 release 0121 ID# 0-32322U5000L100S10000) with ESMTP id AAA180; Sun, 25 May 1997 18:45:56 -0400 Received: (from root@localhost) by cola52.scsn.net (8.8.5/8.8.5) id SAA00887; Sun, 25 May 1997 18:52:58 -0400 (EDT) Message-ID: <19970525185257.34858@cola52.scsn.net> Date: Sun, 25 May 1997 18:52:57 -0400 From: "Donald J. Maddox" To: Wolfgang Helbig Cc: FreeBSD-current@FreeBSD.org Subject: Re: sio1: 64 events for device with no tp Reply-To: dmaddox@scsn.net References: <19970525161640.02033@cola47.scsn.net> <199705252245.AAA00220@helbig.informatik.ba-stuttgart.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199705252245.AAA00220@helbig.informatik.ba-stuttgart.de>; from Wolfgang Helbig on Mon, May 26, 1997 at 12:45:59AM +0200 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, May 26, 1997 at 12:45:59AM +0200, Wolfgang Helbig wrote: > > On Sun, May 25, 1997 at 09:51:22PM +0200, Wolfgang Helbig wrote: > > > Hi, > > > > > > The above kernel message shows up during booting for both sio0 and sio1. > > > Up to now its just annoying -- the messages are repeated once > > > syslogd is started. > > > > > > This behaviour seems buggy to me. These messages were not > > > by the release 1.164 sio driver. The kernel is pretty current, > > > using release 1.169 of sio.c. (FreeBSD-current) > > > > > > Only the serial interface 0 is used on this system, connected to > > > a mouse. It still works. > > > > > > Maybe there is some bug in sio.c to be fixed ? > > > > The following is a patch from phk that will stop the messages... If you > > want to enable the COM_BIGFIFO stuff, set FLAGS=0x20000 in the sio lines in > > your config file (COM_BIGFIFO doesn't work for my Motorola ModemSurfer Modem. > > YMMV). > > [patch omitted ...] > > Thank you! The patch works fine for me. Question: Why isn't it committed? > > Wolfgang Well, you would really have to ask phk to get a meaningful answer about that... -- Donald J. Maddox (dmaddox@scsn.net) From owner-freebsd-current Sun May 25 17:01:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA16611 for current-outgoing; Sun, 25 May 1997 17:01:05 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA16605; Sun, 25 May 1997 17:01:02 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id SAA00937; Sun, 25 May 1997 18:01:01 -0600 (MDT) Message-Id: <199705260001.SAA00937@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: current@freebsd.org cc: obrien@freebsd.org Subject: daemon screen saver broken Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 May 1997 18:01:00 -0600 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, breakage in make world: ===> lkm/syscons/daemon touch opt_smp.h rm -f .depend mkdep -f .depend -a -DLKM -I/usr/src/lkm/syscons/daemon/.. -I/usr/src/lkm/syscons/daemon/../../../sys -I. -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/syscons/daemon/../../sys /usr/src/lkm/syscons/daemon/daemon_saver.c /usr/src/lkm/syscons/daemon/daemon_saver.c:253: macro `DISPATCH' used with only 6 args mkdep: compile failed *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 --- the following patch fixes the compile errors, no idea if it actually works as a screen saver: *** daemon_saver.c.orig Sun May 25 17:53:50 1997 --- daemon_saver.c Sun May 25 17:55:52 1997 *************** *** 249,254 **** int daemon_saver_mod(struct lkm_table *lkmtp, int cmd, int ver) { ! DISPATCH(lkmtp, cmd, ver, daemon_saver_load, daemon_saver_unload, ! lkm_nullcmd); } --- 249,254 ---- int daemon_saver_mod(struct lkm_table *lkmtp, int cmd, int ver) { ! MOD_DISPATCH(daemon_saver, lkmtp, cmd, ver, ! daemon_saver_load, daemon_saver_unload, lkm_nullcmd); } -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Sun May 25 18:39:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA20559 for current-outgoing; Sun, 25 May 1997 18:39:26 -0700 (PDT) Received: from freefall.freebsd.org (freefall.cdrom.com [204.216.27.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA20551 for ; Sun, 25 May 1997 18:39:23 -0700 (PDT) From: Julian Elischer Received: (from julian@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA25070 for current; Sun, 25 May 1997 18:38:56 -0700 (PDT) Date: Sun, 25 May 1997 18:38:56 -0700 (PDT) Message-Id: <199705260138.SAA25070@freefall.freebsd.org> To: current@FreeBSD.ORG Subject: NEW FEATURE.. RFC will commit unless.... Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I would like feedback on a new feature I want to add to the filesystem code. In addition to the immutible and append flags, we at whistle are using a flag NOUNLINK The action of this flag is to allow the file or dir in question to be modified in any way but never deleted. There are several places we find this to be of use.. but the basic usage is to ensure that a particular skeleton of directories and files remains untouched, even while allowing new files to be added and deleted TO that hierarchy, and while allowing some users administrative privs in that hierarchy. The changes are simple and easy to follow. I can forward them to anyone for inspection. I will also put them on ref.tfs.com /incoming/NOUNLINK. these are relative to 2.2 as that is what we are using in production, however I will commit them to -current if I get no violent objections. I would ALSO like to add them to 2.2 as they can easily be shown to be non interfering to any file without the new flag set, and that all conditionals affected, are such that this is an entirely new behaviour and 100% compatible for allpeople not using this feature. comments? tomatoes? potatoes? julian From owner-freebsd-current Sun May 25 18:54:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA21203 for current-outgoing; Sun, 25 May 1997 18:54:35 -0700 (PDT) Received: from freefall.freebsd.org (freefall.cdrom.com [204.216.27.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA21177; Sun, 25 May 1997 18:54:30 -0700 (PDT) From: Julian Elischer Received: (from julian@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA25110; Sun, 25 May 1997 18:54:03 -0700 (PDT) Date: Sun, 25 May 1997 18:54:03 -0700 (PDT) Message-Id: <199705260154.SAA25110@freefall.freebsd.org> To: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: OOPS bad URL given on patches.. Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk the URLS for the patches I would like to commit are: ftp://ref.tfs.com/incoming/IPFW.patches.tar and ftp://ref.tfs.com/incoming/NOUNLINK.tar sorry for the stuffup. this is a 'blind' incoming directory, so the files cannot be seen but can be fetched. julian From owner-freebsd-current Sun May 25 21:15:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26257 for current-outgoing; Sun, 25 May 1997 21:15:59 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26252; Sun, 25 May 1997 21:15:53 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id VAA01976; Sun, 25 May 1997 21:15:52 -0700 (PDT) Date: Sun, 25 May 1997 21:15:50 -0700 (PDT) From: Jaye Mathisen To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: NEW FEATURE.. RFC will commit unless.... In-Reply-To: <199705260138.SAA25070@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I think this would be great, especially when you want to keep certain files/dirs in the directories of customers that they can't remove. On Sun, 25 May 1997, Julian Elischer wrote: > > I would like feedback on a new feature I want to add to the > filesystem code. > > In addition to the immutible and append flags, we at whistle are > using a flag NOUNLINK > > The action of this flag is to allow the file or dir in question > to be modified in any way but never deleted. > > > There are several places we find this to be of use.. > but the basic usage is to ensure that a particular > skeleton of directories and files remains untouched, even while allowing > new files to be added and deleted TO that hierarchy, and while allowing > some users administrative privs in that hierarchy. > > > The changes are simple and easy to follow. > I can forward them to anyone for inspection. I will also put them > on ref.tfs.com /incoming/NOUNLINK. > these are relative to 2.2 as that is what we are using in production, > however I will commit them to -current if I get no violent objections. > > I would ALSO like to add them to 2.2 as they can easily be shown to be > non interfering to any file without the new flag set, and that all conditionals > affected, are such that this is an entirely new behaviour and 100% compatible > for allpeople not using this feature. > > comments? > > tomatoes? > potatoes? > > julian > From owner-freebsd-current Sun May 25 22:35:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA00126 for current-outgoing; Sun, 25 May 1997 22:35:33 -0700 (PDT) Received: from wlk.com (news.wlk.com [192.86.83.250]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA00121 for ; Sun, 25 May 1997 22:35:27 -0700 (PDT) Received: from SMTPdaemon by wlk.com (smail3.2) with SMTPL id m0wVsRF-0009s9C; Mon, 26 May 1997 00:35:21 -0500 (CDT) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id HAA01976; Mon, 26 May 1997 07:31:52 +0200 (CEST) To: Wolfgang Helbig cc: dmaddox@scsn.net, FreeBSD-current@FreeBSD.ORG From: Poul-Henning Kamp Subject: Re: sio1: 64 events for device with no tp In-reply-to: Your message of "Mon, 26 May 1997 00:45:59 +0200." <199705252245.AAA00220@helbig.informatik.ba-stuttgart.de> Date: Mon, 26 May 1997 07:31:52 +0200 Message-ID: <1974.864624712@critter> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199705252245.AAA00220@helbig.informatik.ba-stuttgart.de>, Wolfgang >> The following is a patch from phk that will stop the messages... If you >> want to enable the COM_BIGFIFO stuff, set FLAGS=0x20000 in the sio lines in >> your config file (COM_BIGFIFO doesn't work for my Motorola ModemSurfer Modem >. >> YMMV). > >[patch omitted ...] > >Thank you! The patch works fine for me. Question: Why isn't it committed? I'm still testing it. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Mon May 26 00:15:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA03280 for current-outgoing; Mon, 26 May 1997 00:15:45 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA03263; Mon, 26 May 1997 00:15:21 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.5/8.7.3) with SMTP id JAA25772; Mon, 26 May 1997 09:15:02 +0200 (MET DST) Date: Mon, 26 May 1997 09:15:01 +0200 (MET DST) From: Andrzej Bialecki To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: NEW FEATURE.. RFC will commit unless.... In-Reply-To: <199705260138.SAA25070@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 25 May 1997, Julian Elischer wrote: > > I would like feedback on a new feature I want to add to the > filesystem code. > > In addition to the immutible and append flags, we at whistle are > using a flag NOUNLINK What would you think about yet another flag: purge (like in Netware)? This flag would cause the contents of the file to be overwritten with garbage on unlinking. I'd be glad to use this option on some machines with raised security level. Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-current Mon May 26 00:45:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA04854 for current-outgoing; Mon, 26 May 1997 00:45:43 -0700 (PDT) Received: from hydrogen.nike.efn.org (metriclient-6.uoregon.edu [128.223.172.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA04847 for ; Mon, 26 May 1997 00:45:36 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id AAA24771; Mon, 26 May 1997 00:47:42 -0700 (PDT) Message-ID: <19970526004741.09980@hydrogen.nike.efn.org> Date: Mon, 26 May 1997 00:47:41 -0700 From: John-Mark Gurney To: dmaddox@scsn.net Cc: Wolfgang Helbig , FreeBSD-current@FreeBSD.ORG Subject: Re: sio1: 64 events for device with no tp References: <199705251951.VAA00443@helbig.informatik.ba-stuttgart.de> <19970525161640.02033@cola47.scsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <19970525161640.02033@cola47.scsn.net>; from Donald J. Maddox on Sun, May 25, 1997 at 04:16:40PM -0400 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Donald J. Maddox scribbled this message on May 25: > On Sun, May 25, 1997 at 09:51:22PM +0200, Wolfgang Helbig wrote: > > Hi, > > > > The above kernel message shows up during booting for both sio0 and sio1. > > Up to now its just annoying -- the messages are repeated once > > syslogd is started. > > > > This behaviour seems buggy to me. These messages were not > > by the release 1.164 sio driver. The kernel is pretty current, > > using release 1.169 of sio.c. (FreeBSD-current) > > > > Only the serial interface 0 is used on this system, connected to > > a mouse. It still works. > > > > Maybe there is some bug in sio.c to be fixed ? > > The following is a patch from phk that will stop the messages... If you > want to enable the COM_BIGFIFO stuff, set FLAGS=0x20000 in the sio lines in > your config file (COM_BIGFIFO doesn't work for my Motorola ModemSurfer Modem. > YMMV). could you redo your patch to reduce the number of style changes... right now I only see about 4-6 lines that are different, and about 10-20 that are removed.. the rest is style changes... and was confusing the heck out of me... of course I'm working on another project that will allow you to set the port's fifo to an arbitrary value using an ioctl... so this patch really wont do much good... all it does is disable the fifo on the port.. it would be better to set it to 8bytes... that way the buffering is actually useful... this will still give you 69us instead of the normal 17us interupt latency... (at 115200bps) this patch will give you 130us... (this assumes normal 16550 16byte fifo)... > + outb(iobase+com_dlbh, 0xff); > + outb(iobase+com_dlbl, 0xff); is setting the port to ~1.757bps really neccessary?? won't this kill the serial console running on the port?? > + outb(iobase+com_mcr, com->mcr_image); > + outb(iobase+com_fifo, 0); I haven't done that much with sio, so I'll have to get back to you on this one... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Mon May 26 01:33:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA07027 for current-outgoing; Mon, 26 May 1997 01:33:47 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA07022 for ; Mon, 26 May 1997 01:33:45 -0700 (PDT) Received: from critter.dk.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0wVvDL-0003wCC; Mon, 26 May 97 01:33 PDT Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id KAA00471; Mon, 26 May 1997 10:31:22 +0200 (CEST) To: John-Mark Gurney cc: dmaddox@scsn.net, Wolfgang Helbig , FreeBSD-current@FreeBSD.ORG From: Poul-Henning Kamp Subject: Re: sio1: 64 events for device with no tp In-reply-to: Your message of "Mon, 26 May 1997 00:47:41 PDT." <19970526004741.09980@hydrogen.nike.efn.org> Date: Mon, 26 May 1997 10:31:22 +0200 Message-ID: <469.864635482@critter.dk.tfs.com> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >of course I'm working on another project that will allow you to set the >port's fifo to an arbitrary value using an ioctl... so this patch really >wont do much good... all it does is disable the fifo on the port.. >it would be better to set it to 8bytes... that way the buffering is >actually useful... read again... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Mon May 26 03:34:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA11178 for current-outgoing; Mon, 26 May 1997 03:34:45 -0700 (PDT) Received: from nagual.pp.ru (ache.relcom.ru [194.58.229.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA11160 for ; Mon, 26 May 1997 03:34:41 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.8.5/8.8.5) id OAA00661 for current@freebsd.org; Mon, 26 May 1997 14:35:17 +0400 (MSD) Date: Mon, 26 May 1997 14:35:15 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: FreeBSD-current Subject: I see /etc/rc not clean /tmp anymore Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is it intentional or just overlooking? -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Mon May 26 05:21:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA14460 for current-outgoing; Mon, 26 May 1997 05:21:52 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA14454 for ; Mon, 26 May 1997 05:21:48 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA07038 for current@FreeBSD.ORG; Mon, 26 May 1997 14:21:46 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id OAA25582; Mon, 26 May 1997 14:16:53 +0200 (MET DST) Message-ID: <19970526141653.TJ33830@uriah.heep.sax.de> Date: Mon, 26 May 1997 14:16:53 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG (FreeBSD-current) Subject: Re: I see /etc/rc not clean /tmp anymore References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from ??????????????? on May 26, 1997 14:35:15 +0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Andrey wrote: > Is it intentional or just overlooking? ISTR a comment from Jordan that it's intentional. However, the X semaphore files should be cleaned out. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon May 26 05:46:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA15701 for current-outgoing; Mon, 26 May 1997 05:46:21 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA15694 for ; Mon, 26 May 1997 05:46:17 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id FAA20805; Mon, 26 May 1997 05:46:05 -0700 (PDT) To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= cc: FreeBSD-current Subject: Re: I see /etc/rc not clean /tmp anymore In-reply-to: Your message of "Mon, 26 May 1997 14:35:15 +0400." Date: Mon, 26 May 1997 05:46:05 -0700 Message-ID: <20801.864650765@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Intentional. > Is it intentional or just overlooking? > > -- > Andrey A. Chernov > > http://www.nagual.pp.ru/~ache/ > From owner-freebsd-current Mon May 26 05:51:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA15928 for current-outgoing; Mon, 26 May 1997 05:51:57 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA15918 for ; Mon, 26 May 1997 05:51:54 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id FAA20853; Mon, 26 May 1997 05:51:48 -0700 (PDT) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: current@FreeBSD.ORG (FreeBSD-current) Subject: Re: I see /etc/rc not clean /tmp anymore In-reply-to: Your message of "Mon, 26 May 1997 14:16:53 +0200." <19970526141653.TJ33830@uriah.heep.sax.de> Date: Mon, 26 May 1997 05:51:48 -0700 Message-ID: <20849.864651108@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > ISTR a comment from Jordan that it's intentional. However, the X > semaphore files should be cleaned out. We should probably provide a "clean hook" or something for this then since that will only be relevant for some people, not all. The server folks don't even run X and wouldn't care, but there might be database files or something they'd like to clean on coming up. :) Jordan From owner-freebsd-current Mon May 26 06:24:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA17065 for current-outgoing; Mon, 26 May 1997 06:24:02 -0700 (PDT) Received: from fox.uni-trier.de (blank@fox.uni-trier.de [136.199.8.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA17050 for ; Mon, 26 May 1997 06:23:56 -0700 (PDT) Received: (from blank@localhost) by fox.uni-trier.de (8.8.5/8.8.5) id PAA28767; Mon, 26 May 1997 15:24:06 +0200 From: Sascha Blank Message-Id: <199705261324.PAA28767@fox.uni-trier.de> Subject: Re: src-cur.2896.gz In-Reply-To: <9705251933.AA12219@tulsix.utulsa.edu> from Tom Jackson at "May 25, 97 02:33:00 pm" To: tjackson@tulsix.utulsa.edu (Tom Jackson) Date: Mon, 26 May 1997 15:24:06 +0200 (MET DST) Cc: xaa@stack.nl, freebsd-current@FreeBSD.ORG Reply-To: blank@fox.uni-trier.de (Sascha Blank) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, > > Hi hi, does anyone have a src-cur.2896 lying around somewhere?? It > > wasn't > > on the mailinglist, and is not on ftp.freebsd.org :-( > > Strange as this may seem, go to > ftp.uni-trier.de/pub/unix/FreeBSD/CTM/src-cur > and you will find the missing delta there. Go figure, Germany has it > but > California doesn't. because of exactly such problems CTM-meister Richard has provided me with a direct email link from his CTM production site to our ftp site, i.e. we are bypassing freebsd.org. As I have had no troubles with lost CTM deltas over the last days this smells like mail problems somewhere in or around the freebsd.org domain. Richard and I are planning to establish more ftp CTM mirror sites with such a direct email link, so if any ftp-admin of a CTM mirror site wants to have a direct email feed, then write to me (Richard has appointed me the official contact person for helping to set up such mirrors (call me "CTM-submeister" now! ;-) and we'll see what we can do about it. An official "call for volunteers" is soon to follow. -- Sascha Blank - mailto:blank@fox.uni-trier.de Student and System Administrator at the University of Trier, Germany Finger my account to receive my Public PGP key I don't speak for my employers, they don't pay me enough for that. From owner-freebsd-current Mon May 26 06:32:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA17359 for current-outgoing; Mon, 26 May 1997 06:32:56 -0700 (PDT) Received: from david.siemens.de (david.siemens.de [139.23.36.11]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA17349 for ; Mon, 26 May 1997 06:32:49 -0700 (PDT) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.5/8.8.5) with ESMTP id PAA08594 for ; Mon, 26 May 1997 15:27:42 +0200 (MDT) Received: from curry.mchp.siemens.de (1@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.5/8.8.5) with ESMTP id PAA14154 for ; Mon, 26 May 1997 15:32:42 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.5/8.8.5) id PAA23662 for ; Mon, 26 May 1997 15:32:40 +0200 (MET DST) From: Andre Albsmeier Message-Id: <199705261332.PAA00832@curry.mchp.siemens.de> Subject: vm problems on 2.2, 2.1.7 works To: freebsd-current@freebsd.org Date: Mon, 26 May 1997 15:32:23 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I am running FreeBSD 2.2-STABLE on a 32MB system. When using procmail to deliver large mails, procmail dies with a "out of memory" message. After that, the system is either in an undefined state (producing messages as "junk pointer, too low to make sense.") or freezes completely. When running a high priority "top" in another window, I see the swap being used growing constantly until all of it is used. This is reproducable on different HW. However, on 2.1.7 systems everything works great. Here are some results from my tests: System Version RAM SWAP Mail Size Status ============================================================== 486-66 2.1.7 12M 20M 8M/12M/16M OK 486-120 2.1.7 20M 72M 8M/12M/16M OK PPro-200 2.1.7 64M 300M 8M/12M/16M OK PPro-200 2.2 64M 300M 8M/12M OK PPro-200 2.2 64M 300M 16M FAIL P5-166 2.2 32M 150M 8M/12M/16M FAIL P5-166 2.2 64M 150M 8M/12M OK P5-166 2.2 64M 150M 16M FAIL I suspect a problem in the vm system in 2.2 but have no idea how to fix it. However, I (and others, who confirmed it via email) can reproduce it... So if I should try something, tell me. Thanks for any hints -Andre From owner-freebsd-current Mon May 26 07:21:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA20697 for current-outgoing; Mon, 26 May 1997 07:21:23 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA20689 for ; Mon, 26 May 1997 07:21:15 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA08334 for current@FreeBSD.ORG; Mon, 26 May 1997 16:21:06 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id PAA25870; Mon, 26 May 1997 15:55:17 +0200 (MET DST) Message-ID: <19970526155517.OE34420@uriah.heep.sax.de> Date: Mon, 26 May 1997 15:55:17 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG (FreeBSD-current) Subject: Re: I see /etc/rc not clean /tmp anymore References: <19970526141653.TJ33830@uriah.heep.sax.de> <20849.864651108@time.cdrom.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <20849.864651108@time.cdrom.com>; from Jordan K. Hubbard on May 26, 1997 05:51:48 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > > ISTR a comment from Jordan that it's intentional. However, the X > > semaphore files should be cleaned out. > > We should probably provide a "clean hook" or something for this then > since that will only be relevant for some people, not all. Maybe. I even think the Xserver is at fault here. The semaphore files are a typical example of something that belongs into /var/run. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon May 26 08:45:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA24709 for current-outgoing; Mon, 26 May 1997 08:45:07 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA24704 for ; Mon, 26 May 1997 08:45:04 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id BAA32220; Tue, 27 May 1997 01:41:30 +1000 Date: Tue, 27 May 1997 01:41:30 +1000 From: Bruce Evans Message-Id: <199705261541.BAA32220@godzilla.zeta.org.au> To: current@freebsd.org, j@uriah.heep.sax.de Subject: Re: I see /etc/rc not clean /tmp anymore Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> We should probably provide a "clean hook" or something for this then >> since that will only be relevant for some people, not all. > >Maybe. I even think the Xserver is at fault here. The semaphore >files are a typical example of something that belongs into /var/run. Cleaning of /var/run is broken too. See rev.1.89 of etc/rc. Bruce From owner-freebsd-current Mon May 26 09:11:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA25941 for current-outgoing; Mon, 26 May 1997 09:11:42 -0700 (PDT) Received: from stt3.com (root@stt3.com [198.107.49.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA25932; Mon, 26 May 1997 09:11:37 -0700 (PDT) Received: from eris(really [204.31.113.178]) by stt3.com via sendmail with smtp id for ; Mon, 26 May 1997 09:10:36 -0700 (PDT) (Smail-3.2 1996-Jul-4 #1 built 1997-Mar-5) Date: Mon, 26 May 1997 09:08:34 -0700 (PDT) From: Brian Beattie X-Sender: beattie@eris To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: NEW FEATURE.. RFC will commit unless.... In-Reply-To: <199705260138.SAA25070@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 25 May 1997, Julian Elischer wrote: > > I would like feedback on a new feature I want to add to the > filesystem code. > > In addition to the immutible and append flags, we at whistle are > using a flag NOUNLINK > > The action of this flag is to allow the file or dir in question > to be modified in any way but never deleted. I would be opposed to this as, unlike the immutible flag, I can not see how is adds to the robustness or security of the system. It adds yet another hidden control and contributes to bloat and feeping creaturisim. If this must be added it should be an kernel config option, normally off. I can see "Unremovable file ... even when I log into the system as root I can not remove this file ... !$%*^)^$# FreeBSD sucks". Matbe if somebody could explain how this fixes some major problem I might feel differently. Brian Beattie +1.503.690.1570 x6116 Dynamics Research Corporation 19545 NW Von Neumann Dr FAX 690.1569 Beaverton, OR 97006-6998 beattie@stt3.com "I am Pentium of the Borg. Division is futile. you will be approximated!" From owner-freebsd-current Mon May 26 09:52:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA28532 for current-outgoing; Mon, 26 May 1997 09:52:07 -0700 (PDT) Received: from veda.is (ubiq.veda.is [193.4.230.60]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28522 for ; Mon, 26 May 1997 09:52:03 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.8.5/8.7.3) id RAA16287; Mon, 26 May 1997 17:10:18 GMT Date: Mon, 26 May 1997 17:10:18 GMT From: Adam David Message-Id: <199705261710.RAA16287@veda.is> To: abial@korin.warman.ORG.PL (Andrzej Bialecki) Cc: freebsd-current@freebsd.org Subject: Re: NEW FEATURE.. RFC will commit unless.... Newsgroups: list.freebsd.current References: <199705260138.SAA25070@freefall.freebsd.org> X-Newsreader: NN version 6.5.0 #2 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >What would you think about yet another flag: purge (like in Netware)? This >flag would cause the contents of the file to be overwritten with garbage >on unlinking. I'd be glad to use this option on some machines with raised >security level. Not only unlinking, but on any shrinking truncate. -- Adam David From owner-freebsd-current Mon May 26 09:52:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA28555 for current-outgoing; Mon, 26 May 1997 09:52:12 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28536 for ; Mon, 26 May 1997 09:52:07 -0700 (PDT) Received: from Mercury.mcs.net (Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id LAA16950 for ; Mon, 26 May 1997 11:52:05 -0500 (CDT) Received: (from karl@localhost) by Mercury.mcs.net (8.8.5/8.8.2) id LAA03862; Mon, 26 May 1997 11:52:05 -0500 (CDT) Message-ID: <19970526115204.46379@Mercury.Mcs.Net> Date: Mon, 26 May 1997 11:52:04 -0500 From: Karl Denninger To: current@freebsd.org Subject: Boom! :-) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ideas? This is from a build off last night's sources... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x44 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01119b0 stack pointer = 0x10:0xf68c3f30 frame pointer = 0x10:0xf68c3f30 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 4 (update) interrupt mask = trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x44 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01119b0 stack pointer = 0x10:0xf68c3de8 frame pointer = 0x10:0xf68c3de8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 4 (update) interrupt mask = trap number = 12 panic: page fault Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... .... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x44 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01119b0 stack pointer = 0x10:0xf68c3f30 frame pointer = 0x10:0xf68c3f30 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 4 (update) interrupt mask = trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x44 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01119b0 stack pointer = 0x10:0xf68c3de8 frame pointer = 0x10:0xf68c3de8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 4 (update) interrupt mask = trap number = 12 panic: page fault Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sun May 25 22:48:32 CDT 1997 karl@Codebase.mcs.net:/usr/src/sys/compile/MCS_STANDARD CPU: Pentium (90.00-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x521 Stepping=1 Features=0x5bf> real memory = 67108864 (65536K bytes) -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | 99 Analog numbers, 77 ISDN, http://www.mcs.net/ Voice: [+1 312 803-MCS1 x219]| NOW Serving 56kbps DIGITAL on our analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-current Mon May 26 11:51:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04645 for current-outgoing; Mon, 26 May 1997 11:51:45 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA04631 for ; Mon, 26 May 1997 11:51:42 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA13499 for current@FreeBSD.ORG; Mon, 26 May 1997 20:51:40 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id UAA26389; Mon, 26 May 1997 20:30:01 +0200 (MET DST) Message-ID: <19970526203001.QO27493@uriah.heep.sax.de> Date: Mon, 26 May 1997 20:30:01 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: I see /etc/rc not clean /tmp anymore References: <199705261541.BAA32220@godzilla.zeta.org.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199705261541.BAA32220@godzilla.zeta.org.au>; from Bruce Evans on May 27, 1997 01:41:30 +1000 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > Cleaning of /var/run is broken too. See rev.1.89 of etc/rc. I wonder whether we should cleanup before netstart (or its equivalent) is running. I know, it's impossible to find something that will fit every need, but not cleaning old crap like /var/run/*.pid doesn't sound right. (Stale PID files could be misinterpreted by some process, since the PIDs have been recycled after a reboot.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon May 26 12:06:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA05448 for current-outgoing; Mon, 26 May 1997 12:06:08 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA05443 for ; Mon, 26 May 1997 12:06:05 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id TAA25566; Mon, 26 May 1997 19:58:17 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Mon, 26 May 1997 20:01:27 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19970526115204.46379@Mercury.Mcs.Net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 26 May 1997 19:58:28 +0100 To: Karl Denninger , current@FreeBSD.ORG From: Bob Bishop Subject: Re: Boom! :-) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 17:52 +0100 26/5/97, Karl Denninger wrote: >Ideas? This is from a build off last night's sources... > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x44 If, as I suspect, 0x8:0xf01119b0 = _lockstatus + 0x8, this is a particularly bad case of kern/3581. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Mon May 26 12:15:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA05794 for current-outgoing; Mon, 26 May 1997 12:15:47 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA05786; Mon, 26 May 1997 12:15:40 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id NAA04530; Mon, 26 May 1997 13:15:39 -0600 (MDT) Message-Id: <199705261915.NAA04530@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: current@freebsd.org cc: Stefan Esser Subject: recent PCI code changes broken? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 May 1997 13:15:39 -0600 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I am having trouble with the most recent sys code not finding PCI devices. I discovered this after resupping my just committed changes to exception.s, vector.s and icu.s. However I (locally) restored the old versions of these and the problem still exists. Specifically none of the PCI devices appear to be discovered during the probe, in either the UP or SMP models. Could the problem be with the recently committed PCI code? I'm looking into this now, please send any clues my way... -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Mon May 26 12:23:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA06098 for current-outgoing; Mon, 26 May 1997 12:23:13 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA06092 for ; Mon, 26 May 1997 12:23:08 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA14594 for current@FreeBSD.ORG; Mon, 26 May 1997 21:22:59 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA26592; Mon, 26 May 1997 21:14:56 +0200 (MET DST) Message-ID: <19970526211456.WJ01847@uriah.heep.sax.de> Date: Mon, 26 May 1997 21:14:56 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: Boom! :-) References: <19970526115204.46379@Mercury.Mcs.Net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970526115204.46379@Mercury.Mcs.Net>; from Karl Denninger on May 26, 1997 11:52:04 -0500 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Karl Denninger wrote: > Ideas? This is from a build off last night's sources... > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x44 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf01119b0 ^^^^^^^^^^ Well, you forgot the most important: where the heck is it? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon May 26 12:23:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA06120 for current-outgoing; Mon, 26 May 1997 12:23:17 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA06106 for ; Mon, 26 May 1997 12:23:14 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA14597 for freebsd-current@FreeBSD.ORG; Mon, 26 May 1997 21:23:13 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA26604; Mon, 26 May 1997 21:16:37 +0200 (MET DST) Message-ID: <19970526211637.JM43194@uriah.heep.sax.de> Date: Mon, 26 May 1997 21:16:37 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Subject: Re: NEW FEATURE.. RFC will commit unless.... References: <199705260138.SAA25070@freefall.freebsd.org> <199705261710.RAA16287@veda.is> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199705261710.RAA16287@veda.is>; from Adam David on May 26, 1997 17:10:18 +0000 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Adam David wrote: > Not only unlinking, but on any shrinking truncate. Appendonly files are already there. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon May 26 12:23:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA06141 for current-outgoing; Mon, 26 May 1997 12:23:21 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA06119 for ; Mon, 26 May 1997 12:23:17 -0700 (PDT) Received: from Jupiter.Mcs.Net (karl@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id OAA19709; Mon, 26 May 1997 14:23:15 -0500 (CDT) Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.5/8.8.2) id OAA06482; Mon, 26 May 1997 14:23:14 -0500 (CDT) Message-ID: <19970526142314.47422@Jupiter.Mcs.Net> Date: Mon, 26 May 1997 14:23:14 -0500 From: Karl Denninger To: Bob Bishop Cc: Karl Denninger , current@FreeBSD.ORG Subject: Re: Boom! :-) References: <19970526115204.46379@Mercury.Mcs.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: ; from Bob Bishop on Mon, May 26, 1997 at 07:58:28PM +0100 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, May 26, 1997 at 07:58:28PM +0100, Bob Bishop wrote: > At 17:52 +0100 26/5/97, Karl Denninger wrote: > >Ideas? This is from a build off last night's sources... > > > >Fatal trap 12: page fault while in kernel mode > >fault virtual address = 0x44 > > If, as I suspect, 0x8:0xf01119b0 = _lockstatus + 0x8, this is a > particularly bad case of kern/3581. > > > -- > Bob Bishop (0118) 977 4017 international code +44 118 > rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK Ok, I've missed something (actually I've seen the messages fly by, but didn't read them -- boo on me). Can someone forward the specifics to me? -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | 99 Analog numbers, 77 ISDN, http://www.mcs.net/ Voice: [+1 312 803-MCS1 x219]| NOW Serving 56kbps DIGITAL on our analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-current Mon May 26 12:48:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA07516 for current-outgoing; Mon, 26 May 1997 12:48:35 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA07510 for ; Mon, 26 May 1997 12:48:32 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-1.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA08877 (5.67b/IDA-1.5 for ); Mon, 26 May 1997 21:48:29 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id VAA04268; Mon, 26 May 1997 21:48:28 +0200 (CEST) X-Face: " Date: Mon, 26 May 1997 21:48:27 +0200 From: Stefan Esser To: Steve Passe Cc: current@FreeBSD.ORG Subject: Re: recent PCI code changes broken? References: <199705261915.NAA04530@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199705261915.NAA04530@Ilsa.StevesCafe.com>; from Steve Passe on Mon, May 26, 1997 at 01:15:39PM -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 26, Steve Passe wrote: > Hi, > > I am having trouble with the most recent sys code not finding PCI devices. > I discovered this after resupping my just committed changes to exception.s, > vector.s and icu.s. However I (locally) restored the old versions of these > and the problem still exists. Specifically none of the PCI devices appear > to be discovered during the probe, in either the UP or SMP models. Ohh, sorry, this may really be caused by my changes ... :( I tested them for two days (extracted clean kernel trees, built various kernels (GENERIC and custom) and booted them, and prepared a large patch file to be sure that no part of this change (which affected 13 source files) was lost ... Anyway, if I messed up, I'm sorry and will try to fix all problems I might have introduced as fast as possible! > Could the problem be with the recently committed PCI code? Yes, I'm afraid ... > I'm looking into this now, please send any clues my way... Please let me look into this, too :) What does a VERBOSE boot print when testing for the PCI chip set ? On my (old) Saturn II based SP3G it looks like this: % CPU: AMD Am5x86 Write-Through (486-class CPU) % Origin = "AuthenticAMD" Id = 0x4e4 Stepping=4 % Features=0x1 % real memory = 33554432 (32768K bytes) % avail memory = 30900224 (30176K bytes) % pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 % pci_open(1a): mode1res=0x00000000 (0x80000000) % pci_open(1b): mode1res=0x00000000 (0xff000001) % pci_open(2): mode 2 enable port (0x0cf8) is 0x00 % pci_open(2a): mode2res=0x0e (0x0e) % pci_open(2a): now trying mechanism 2 % pci_cfgcheck: device 0 [class=000000] 1 [class=000000] 2 [class=000000] 3 4 [class=010000] [hdr=00] is there (id=000f1000) % Probing for devices on PCI bus 0: Please write down all the numbers from the labels (1,1a,...) and the values reported, iff there is NO success reported in the pci_cfgcheck line, or if that line is completely missing. (If you warm boot /kernel.old, the message buffer might be saved completely, and these lines that appear right at the top will be included. I used this a lot during debugging of that code :) If the PCI chip set is found (i.e. pci_cfgcheck succeeds), then I need to know what the device probe returns. For that to be reported as part of a verbose boot, you need to build a kernel with "options PCI_DEBUG" defined ... Sorry for the inconvenience. I'm willing to spend the next few hours to get this resolved ! Regards, STefan From owner-freebsd-current Mon May 26 13:26:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA09340 for current-outgoing; Mon, 26 May 1997 13:26:15 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA09329 for ; Mon, 26 May 1997 13:26:08 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA14105; Mon, 26 May 1997 13:22:44 -0700 From: Terry Lambert Message-Id: <199705262022.NAA14105@phaeton.artisoft.com> Subject: Re: cd9660 w/ Joliet extensions To: albast@magigimmix.xs4all.nl (Jeroen) Date: Mon, 26 May 1997 13:22:43 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: <199705252141.XAA26208@smtp1.xs4all.nl> from "Jeroen" at May 25, 97 11:40:02 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > People who find it disconcerting (that "disk inserting" ;) causes > > an AutoRun) probably are not well enough educated about their OS > > to turn it off. > > *please* move this BS thread to -chat.. don't use -current to > chitchat about the windows registry! What about using -current to discus whether the CDROM distribution ought to have an autorun.inf that starts it up under Windows95? The discussion so far has been: A: "Does it have it?" B: "No" A: "Can you add it?" B: "People find autorun disconcerting." A: "Can't they disable it? It seems to me that it would help far more people than it would disconcert." B: "No. They can't disable it" C: "Yes, the can. Here's how..." "(implied) What valid excuses remain for not having one?" D: "Can't you move this thread? I (erroneously) believe it's not relevent..." Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon May 26 13:30:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA09516 for current-outgoing; Mon, 26 May 1997 13:30:14 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA09497 for ; Mon, 26 May 1997 13:30:07 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA14117; Mon, 26 May 1997 13:26:58 -0700 From: Terry Lambert Message-Id: <199705262026.NAA14117@phaeton.artisoft.com> Subject: Re: NEW FEATURE.. RFC will commit unless.... To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 26 May 1997 13:26:58 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19970526211637.JM43194@uriah.heep.sax.de> from "J Wunsch" at May 26, 97 09:16:37 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As Adam David wrote: > > > Not only unlinking, but on any shrinking truncate. > > Appendonly files are already there. He wants to purge (pattern wipe using DOD hysterisis effective pattern) on all block reclamation, not only on block reclamation as a result of unlink. He is not asking for no-unlink to make the files non-shrinkable. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon May 26 13:32:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA09632 for current-outgoing; Mon, 26 May 1997 13:32:39 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA09624 for ; Mon, 26 May 1997 13:32:35 -0700 (PDT) Received: from Jupiter.Mcs.Net (karl@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id PAA21344; Mon, 26 May 1997 15:32:32 -0500 (CDT) Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.5/8.8.2) id PAA07917; Mon, 26 May 1997 15:32:32 -0500 (CDT) Message-ID: <19970526153232.13834@Jupiter.Mcs.Net> Date: Mon, 26 May 1997 15:32:32 -0500 From: Karl Denninger To: Joerg Wunsch Cc: current@FreeBSD.ORG Subject: Re: Boom! :-) References: <19970526115204.46379@Mercury.Mcs.Net> <19970526211456.WJ01847@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: <19970526211456.WJ01847@uriah.heep.sax.de>; from J Wunsch on Mon, May 26, 1997 at 09:14:56PM +0200 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, May 26, 1997 at 09:14:56PM +0200, J Wunsch wrote: > As Karl Denninger wrote: > > > Ideas? This is from a build off last night's sources... > > > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0x44 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xf01119b0 > ^^^^^^^^^^ > > Well, you forgot the most important: where the heck is it? > > -- > cheers, J"org Oh c'mon, you want a stack traceback? :-) Assuming gdb is fixed and will actually work on kernels (it didn't the last time I tried using it a month or so ago) I'll get one the next dump I get (I have to rebuild with -g). -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | 99 Analog numbers, 77 ISDN, http://www.mcs.net/ Voice: [+1 312 803-MCS1 x219]| NOW Serving 56kbps DIGITAL on our analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-current Mon May 26 14:14:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA11235 for current-outgoing; Mon, 26 May 1997 14:14:14 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA11229 for ; Mon, 26 May 1997 14:14:10 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id PAA16652; Mon, 26 May 1997 15:14:06 -0600 (MDT) Message-Id: <199705262114.PAA16652@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Karl Denninger cc: current@FreeBSD.ORG Subject: Re: Boom! :-) In-reply-to: Your message of "Mon, 26 May 1997 15:32:32 CDT." <19970526153232.13834@Jupiter.Mcs.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 May 1997 16:11:54 -0600 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Oh c'mon, you want a stack traceback? :-) > Oh c'mon, Karl. How long have you been using FreeBSD now? You still don't know how to do this yet? nm /kernel | sort | more Will allow you to find the routine that containes faulting address. No need to recompile a kernel with -g. No need for a crash dump. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon May 26 14:17:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA11373 for current-outgoing; Mon, 26 May 1997 14:17:11 -0700 (PDT) Received: (from jmb@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA11353; Mon, 26 May 1997 14:17:06 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199705262117.OAA11353@hub.freebsd.org> Subject: Re: Boom! :-) To: karl@Mcs.Net (Karl Denninger) Date: Mon, 26 May 1997 14:17:06 -0700 (PDT) Cc: joerg_wunsch@uriah.heep.sax.de, current@FreeBSD.ORG In-Reply-To: <19970526153232.13834@Jupiter.Mcs.Net> from "Karl Denninger" at May 26, 97 03:32:32 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Karl Denninger wrote: > > > > instruction pointer = 0x8:0xf01119b0 > > ^^^^^^^^^^ > > > > Well, you forgot the most important: where the heck is it? > > > > -- > > cheers, J"org > > Oh c'mon, you want a stack traceback? :-) > > Assuming gdb is fixed and will actually work on kernels (it didn't the last > time I tried using it a month or so ago) I'll get one the next dump I get (I > have to rebuild with -g). > karl, could you start with the output of: nm / | sort | grep -5 '^f0111' jmb From owner-freebsd-current Mon May 26 14:36:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA12547 for current-outgoing; Mon, 26 May 1997 14:36:08 -0700 (PDT) Received: from nagual.pp.ru (ache.relcom.ru [194.58.229.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA12542 for ; Mon, 26 May 1997 14:36:05 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.8.5/8.8.5) id BAA01456; Tue, 27 May 1997 01:36:31 +0400 (MSD) Date: Tue, 27 May 1997 01:36:29 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: Joerg Wunsch cc: current@FreeBSD.ORG Subject: Re: I see /etc/rc not clean /tmp anymore In-Reply-To: <19970526203001.QO27493@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 26 May 1997, J Wunsch wrote: > I wonder whether we should cleanup before netstart (or its equivalent) > is running. I know, it's impossible to find something that will fit > every need, but not cleaning old crap like /var/run/*.pid doesn't > sound right. (Stale PID files could be misinterpreted by some process, > since the PIDs have been recycled after a reboot.) Yes, not cleaning /var/run sounds VERY dangerous since newsyslogd can kill random process in this case. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Mon May 26 14:50:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA13292 for current-outgoing; Mon, 26 May 1997 14:50:21 -0700 (PDT) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA13286 for ; Mon, 26 May 1997 14:50:14 -0700 (PDT) Received: from AMPERSAND (ztm03-05.dial.xs4all.nl [194.109.32.70]) by smtp1.xs4all.nl (8.7.6/XS4ALL) with SMTP id XAA10053 for ; Mon, 26 May 1997 23:50:11 +0200 (MET DST) Message-Id: <199705262150.XAA10053@smtp1.xs4all.nl> Comments: Authenticated sender is From: "Jeroen" Organization: Twiddle To: current@FreeBSD.ORG Date: Mon, 26 May 1997 23:48:44 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: cd9660 w/ Joliet extensions Priority: normal X-mailer: Pegasus Mail for Windows (v2.31) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > What about using -current to discus whether the CDROM distribution > ought to have an autorun.inf that starts it up under Windows95? That would seem the issue here :-) > The discussion so far has been: > > A: "Does it have it?" > > B: "No" > > A: "Can you add it?" > > B: "People find autorun disconcerting." > > A: "Can't they disable it? It seems to me that it would help far > more people than it would disconcert." > > B: "No. They can't disable it" > > C: "Yes, the can. Here's how..." > "(implied) What valid excuses remain for not having one?" ^^^^^^^ That's your opinion Because most users do not have that knowledge, in practice they really can not disable it ;-) > D: "Can't you move this thread? I (erroneously) believe it's > not relevent..." No, I don't believe going in depth with the windows stuff is relevant here. > > Regards, > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. PS: I apologize for my somewhat crude mail, Terry :) I'm not going to "explain", just take it ;-) Jeroen From owner-freebsd-current Mon May 26 14:52:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA13374 for current-outgoing; Mon, 26 May 1997 14:52:57 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA13367 for ; Mon, 26 May 1997 14:52:52 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.5/8.7.3) with SMTP id XAA29653; Mon, 26 May 1997 23:51:12 +0200 (MET DST) Date: Mon, 26 May 1997 23:51:11 +0200 (MET DST) From: Andrzej Bialecki To: Terry Lambert cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.ORG Subject: Re: NEW FEATURE.. RFC will commit unless.... In-Reply-To: <199705262026.NAA14117@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 26 May 1997, Terry Lambert wrote: > > As Adam David wrote: > > > > > Not only unlinking, but on any shrinking truncate. > > > > Appendonly files are already there. > > He wants to purge (pattern wipe using DOD hysterisis effective > pattern) on all block reclamation, not only on block reclamation > as a result of unlink. > > He is not asking for no-unlink to make the files non-shrinkable. That's right. In case I was unclear: sometimes I want to get rid of any traces of the file's contents on the disk. Sometimes I'd like to be able to set this as a default policy. Writing a wrapper around unlink() call is not my idea of elegant solution :-) So, methinks a filesystem flag for this would be good... Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-current Mon May 26 15:23:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA14807 for current-outgoing; Mon, 26 May 1997 15:23:15 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA14801; Mon, 26 May 1997 15:23:12 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id QAA05758; Mon, 26 May 1997 16:23:07 -0600 (MDT) Message-Id: <199705262223.QAA05758@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: smp@freebsd.org cc: current@freebsd.org Subject: SMP kernels are broken. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 May 1997 16:23:07 -0600 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, HEADS UP: Recent changes to the pci code has broken the ability to create a working SMP kernel. I'm working on it... -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Mon May 26 16:24:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16538 for current-outgoing; Mon, 26 May 1997 16:24:12 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA16533 for ; Mon, 26 May 1997 16:24:09 -0700 (PDT) Received: from Jupiter.Mcs.Net (karl@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id SAA24624; Mon, 26 May 1997 18:24:07 -0500 (CDT) Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.5/8.8.2) id SAA11993; Mon, 26 May 1997 18:24:06 -0500 (CDT) Message-ID: <19970526182406.59864@Jupiter.Mcs.Net> Date: Mon, 26 May 1997 18:24:06 -0500 From: Karl Denninger To: Bob Bishop Cc: Karl Denninger , current@FreeBSD.ORG Subject: Re: Boom! :-) References: <19970526115204.46379@Mercury.Mcs.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: ; from Bob Bishop on Mon, May 26, 1997 at 07:58:28PM +0100 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, May 26, 1997 at 07:58:28PM +0100, Bob Bishop wrote: > At 17:52 +0100 26/5/97, Karl Denninger wrote: > >Ideas? This is from a build off last night's sources... > > > >Fatal trap 12: page fault while in kernel mode > >fault virtual address = 0x44 > > If, as I suspect, 0x8:0xf01119b0 = _lockstatus + 0x8, this is a > particularly bad case of kern/3581. > > > -- > Bob Bishop (0118) 977 4017 international code +44 118 > rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK > > Hmmm... Don't think so... this looks to be in lockinit... f01116d4 t __lkm_dev f01117d8 t __lkm_exec f01118a4 t _lkm_exec_dummy1 f01118ac t _lkm_exec_dummy2 f01118b4 t _lkm_exec_dummy3 f01118bc t _lkm_exec_dummy4 f01118c4 t ___set_execsw_set_sym_lkm_exec_dummy1 f01118c8 t ___set_execsw_set_sym_lkm_exec_dummy2 f01118cc t ___set_execsw_set_sym_lkm_exec_dummy3 f01118d0 t ___set_execsw_set_sym_lkm_exec_dummy4 f01118d4 T _lkmdispatch f011195c T _lkm_nullcmd f0111964 t _lkm_drvinit f0111998 t ___set_sysinit_set_sym_lkmdev_sys_init f01119a0 F kern_lock.o f01119a0 T _lockinit f01119e8 T _lockstatus f0111b14 T _lockmgr f0112068 T _lockmgr_printinfo f01120d0 F kern_lockf.o -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | 99 Analog numbers, 77 ISDN, http://www.mcs.net/ Voice: [+1 312 803-MCS1 x219]| NOW Serving 56kbps DIGITAL on our analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-current Mon May 26 20:02:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA23216 for current-outgoing; Mon, 26 May 1997 20:02:15 -0700 (PDT) Received: from watcher.isl.net (ppp-23.infopet.com [208.210.103.23]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA23210; Mon, 26 May 1997 20:02:11 -0700 (PDT) Received: (from ortmann@localhost) by watcher.isl.net (8.8.5/8.8.5) id WAA00457; Mon, 26 May 1997 22:02:07 -0500 (CDT) From: Daniel Ortmann Message-Id: <199705270302.WAA00457@watcher.isl.net> Subject: handbook needs updating [was Re: Boom! :-)] To: jmb@FreeBSD.ORG (Jonathan M. Bresler) Date: Mon, 26 May 1997 22:01:09 -0500 (CDT) Cc: karl@Mcs.Net, joerg_wunsch@uriah.heep.sax.de, current@FreeBSD.ORG In-Reply-To: <199705262117.OAA11353@hub.freebsd.org> from "Jonathan M. Bresler" at "May 26, 97 02:17:06 pm" X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ... > could you start with the output of: > > nm / | sort | grep -5 '^f0111' > jmb This is not in the handbook. It probably should be under the "Kernel Debugging" section, especially since it often asked, a lot of usefulness for a small amount of work, and *much* simpler than the other kernel debugging documentation. -- Daniel Ortmann 507.288.7732 (h) ortmann@isl.net 2414 30 av NW, #D 507.253.6795 (w) ortmann@vnet.ibm.com Rochester, MN 55901 "PERL: The Swiss Army Chainsaw" From owner-freebsd-current Mon May 26 21:25:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA25440 for current-outgoing; Mon, 26 May 1997 21:25:18 -0700 (PDT) Received: from Gforce.iamerica.net (iax-covington-ppp0008.iamerica.net [207.101.35.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA25435 for ; Mon, 26 May 1997 21:25:15 -0700 (PDT) Received: from Gforce.iamerica.net (localhost.iamerica.net [127.0.0.1]) by Gforce.iamerica.net (8.8.5/8.8.5) with ESMTP id XAA00218 for ; Mon, 26 May 1997 23:25:06 -0500 (CDT) Message-Id: <199705270425.XAA00218@Gforce.iamerica.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-current@freebsd.org Subject: errors on startup From: Glenn Johnson Mime-Version: 1.0 Content-Type: text/plain Date: Mon, 26 May 1997 23:25:05 -0500 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am getting the following messages at the end of my startup: sb0 at 0x220-0x22f irq 5 drq 1 on isa sb0: sbxvi0 at 0x220-0x22f irq 5 drq 5 on isa sbxvi0: device combination doesn't support shared irq5 intr_connect(irq5) failed, result=-1 sbmidi0 at 0x330-0x331 irq 5 on isa sbmidi0: device combination doesn't support shared irq5 intr_connect(irq5) failed, result=-1 opl0 at 0x338-0x33b irq 31 on isa opl0: create_intr: requested irq31 too high, limit is 15 sio0: 65 events for device with no tp sio1: 65 events for device with no tp I did a 'make world' on May 26. I know the sio errors have been reported but this is the first time I have seen the create_intr and the sound card errors. Particularly disconcerting is that the opl device is requesting IRQ 31. Is anyone else seeing this? -- Glenn Johnson gljohnsn@iamerica.net From owner-freebsd-current Mon May 26 22:12:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA27134 for current-outgoing; Mon, 26 May 1997 22:12:24 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA27083; Mon, 26 May 1997 22:11:25 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id XAA07097; Mon, 26 May 1997 23:11:19 -0600 (MDT) Message-Id: <199705270511.XAA07097@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Glenn Johnson cc: freebsd-current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: errors on startup In-reply-to: Your message of "Mon, 26 May 1997 23:25:05 CDT." <199705270425.XAA00218@Gforce.iamerica.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 May 1997 23:11:19 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > I am getting the following messages at the end of my startup: > > sb0 at 0x220-0x22f irq 5 drq 1 on isa > sb0: > ... > opl0: > create_intr: requested irq31 too high, limit is 15 > sio0: 65 events for device with no tp > sio1: 65 events for device with no tp > > I did a 'make world' on May 26. I know the sio errors have been reported but > this is the first time I have seen the create_intr and the sound card errors. > Particularly disconcerting is that the opl device is requesting IRQ 31. > Is anyone else seeing this? The new pci code that was committed the last 24 hours broke several things. Stefan got most of them fixed a few hours ago. I just got SMP working about 30 minutes ago. For those behind slow mirrors here's the fix for the SMP problem: ------------------------------------- cut ------------------------------------- *** sys/pci/pci.c.ORIG Mon May 26 21:28:45 1997 --- sys/pci/pci.c Mon May 26 22:09:01 1997 *************** *** 332,337 **** --- 330,353 ---- cfg->lattimer = pci_cfgread(cfg, PCIR_LATTIMER, 1); cfg->intpin = pci_cfgread(cfg, PCIR_INTPIN, 1); cfg->intline = pci_cfgread(cfg, PCIR_INTLINE, 1); + + #ifdef APIC_IO + if (cfg->intline && (cfg->intline != 0xff)) { + u_char airq = 0xff; + u_char rirq = 0xff; + + airq = get_pci_apic_irq(cfg->bus, + cfg->slot, cfg->intpin); + + if (airq != 0xff) { /* APIC IRQ exists */ + rirq = cfg->intline; /* 're-directed' IRQ */ + cfg->intline = airq; /* use APIC IRQ */ + pci_cfgwrite(cfg, PCIR_INTLINE, airq, 1); + undirect_pci_irq(rirq); + } + } + #endif /* APIC_IO */ + cfg->mingnt = pci_cfgread(cfg, PCIR_MINGNT, 1); cfg->maxlat = pci_cfgread(cfg, PCIR_MAXLAT, 1); ------------------------------------- cut ------------------------------------- I don't have a sound card available for testing, it may or may not be fixed by now. you will need to resup and try again. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Mon May 26 22:13:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA27214 for current-outgoing; Mon, 26 May 1997 22:13:55 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA27209; Mon, 26 May 1997 22:13:52 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id XAA07121; Mon, 26 May 1997 23:13:50 -0600 (MDT) Message-Id: <199705270513.XAA07121@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: smp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: SMP kernels are broken. In-reply-to: Your message of "Mon, 26 May 1997 16:23:07 MDT." <199705262223.QAA05758@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 May 1997 23:13:50 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > HEADS UP: > > Recent changes to the pci code has broken the ability to create a working > SMP kernel. I'm working on it... SMP kernels are working again (here anyways)! Fix was committed about 30 minutes ago to freefall. Report any problems ASAP. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Mon May 26 23:16:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA28759 for current-outgoing; Mon, 26 May 1997 23:16:21 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA28753 for ; Mon, 26 May 1997 23:16:18 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA28391; Tue, 27 May 1997 15:45:42 +0930 (CST) From: Michael Smith Message-Id: <199705270615.PAA28391@genesis.atrad.adelaide.edu.au> Subject: Re: Weird behaviour from the Linux emulator In-Reply-To: <19970525193558.22470@keltia.freenix.fr> from Ollivier Robert at "May 25, 97 07:35:58 pm" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Tue, 27 May 1997 15:45:41 +0930 (CST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ollivier Robert stands accused of saying: > The Linux emulator has a weird idea of the filesystem, mixing the real one > with the one rooted at /compat/linux. To see this, open Acroread (or any > other Linux application), open "/" and then goes to "/usr". Watch now the > program displaying everything that's in "/compat/linux/usr" instead of the > real "/usr"... Yeah; there's not much that can be done about that though. > I understand the need to shadow the real filesystem but it should be done > only for the search for libraries/binaries, not for every open(2) call. Aha. And how do you think that libraries/binaries are searched for, if not by open(2)? Then how about configuration files, hmm? -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Mon May 26 23:58:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA00315 for current-outgoing; Mon, 26 May 1997 23:58:46 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA00258; Mon, 26 May 1997 23:56:58 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-15.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA17441 (5.67b/IDA-1.5); Tue, 27 May 1997 08:54:59 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id IAA05770; Tue, 27 May 1997 08:53:57 +0200 (CEST) X-Face: " Date: Tue, 27 May 1997 08:53:55 +0200 From: Stefan Esser To: Steve Passe Cc: Glenn Johnson , freebsd-current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: errors on startup References: <199705270425.XAA00218@Gforce.iamerica.net> <199705270511.XAA07097@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199705270511.XAA07097@Ilsa.StevesCafe.com>; from Steve Passe on Mon, May 26, 1997 at 11:11:19PM -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 26, Steve Passe wrote: > The new pci code that was committed the last 24 hours broke several things. > Stefan got most of them fixed a few hours ago. I just got SMP working about > 30 minutes ago. For those behind slow mirrors here's the fix for the SMP > problem: Sorry for the breakage I introduced, but the changes were quite large (13 source file, complete), and I tested whatever I oculd, before doing the commit. Two things that I had no way of testing were broken: Configuration mechanism 1 register accesses, and the SMP APIC support. The moment I arrived at home, I remembered why you had problems with the APIC: The new PCI code is not derived from the previous one, but a completely new design. And I had not commited the SMP changes to the PCI code and had forgotten about them by now, though I had suggested them, some time ago ... O well ... > *** sys/pci/pci.c.ORIG Mon May 26 21:28:45 1997 > --- sys/pci/pci.c Mon May 26 22:09:01 1997 > *************** > *** 332,337 **** > --- 330,353 ---- > cfg->lattimer = pci_cfgread(cfg, PCIR_LATTIMER, 1); > cfg->intpin = pci_cfgread(cfg, PCIR_INTPIN, 1); > cfg->intline = pci_cfgread(cfg, PCIR_INTLINE, 1); > + > + #ifdef APIC_IO > + if (cfg->intline && (cfg->intline != 0xff)) { > + u_char airq = 0xff; > + u_char rirq = 0xff; > + > + airq = get_pci_apic_irq(cfg->bus, > + cfg->slot, cfg->intpin); > + > + if (airq != 0xff) { /* APIC IRQ exists */ > + rirq = cfg->intline; /* 're-directed' IRQ */ > + cfg->intline = airq; /* use APIC IRQ */ > + pci_cfgwrite(cfg, PCIR_INTLINE, airq, 1); Hmmm, I don't think we should do this anymore ... The new data structure that holds a copy of the most important configuration space registers is there just for the purpose of modifying parameters for drivers, but without a need to actually change the register contents ... All the drivers will use whatever is in cfg->intline, so there is no need for the register update, IMHO. > + undirect_pci_irq(rirq); > + } > + } > + #endif /* APIC_IO */ > + > cfg->mingnt = pci_cfgread(cfg, PCIR_MINGNT, 1); > cfg->maxlat = pci_cfgread(cfg, PCIR_MAXLAT, 1); Regards, STefan From owner-freebsd-current Tue May 27 00:09:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA00787 for current-outgoing; Tue, 27 May 1997 00:09:31 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.122]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA00782; Tue, 27 May 1997 00:09:26 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.5/8.7.3) id CAA00296; Tue, 27 May 1997 02:00:35 -0500 (CDT) Message-ID: <19970527020035.32582@peeper.my.domain> Date: Tue, 27 May 1997 02:00:35 -0500 From: Tom Jackson To: FreeBSD Current Cc: jkh@freebsd.org Subject: rc.i386 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74e Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The mouse section needs parenthesis around no: X"NO" and the variables need underline separators eg: moused_type. -- Tom Jackson I'm ProChoice->FreeBSD toj@gorilla.net http://www.freebsd.org http://tulsix.utulsa.edu/~tjackson "Out in the Ozone Again" From owner-freebsd-current Tue May 27 00:35:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA01775 for current-outgoing; Tue, 27 May 1997 00:35:45 -0700 (PDT) Received: from wlk.com (news.wlk.com [192.86.83.250]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA01768; Tue, 27 May 1997 00:35:41 -0700 (PDT) Received: from SMTPdaemon by wlk.com (smail3.2) with SMTPL id m0wWGn7-0009sCC; Tue, 27 May 1997 02:35:33 -0500 (CDT) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id JAA00843; Tue, 27 May 1997 09:31:52 +0200 (CEST) To: Daniel Ortmann cc: jmb@freebsd.org (Jonathan M. Bresler), karl@Mcs.Net, joerg_wunsch@uriah.heep.sax.de, current@freebsd.org From: Poul-Henning Kamp Subject: Re: handbook needs updating [was Re: Boom! :-)] In-reply-to: Your message of "Mon, 26 May 1997 22:01:09 CDT." <199705270302.WAA00457@watcher.isl.net> Date: Tue, 27 May 1997 09:31:51 +0200 Message-ID: <841.864718311@critter.dk.tfs.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199705270302.WAA00457@watcher.isl.net>, Daniel Ortmann writes: >... > >> could you start with the output of: >> >> nm / | sort | grep -5 '^f0111' >> jmb > >This is not in the handbook. It probably should be under the >"Kernel Debugging" section, especially since it often asked, a lot >of usefulness for a small amount of work, and *much* simpler than >the other kernel debugging documentation. And then make it nm -n / | grep -5 '^f0111' -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Tue May 27 00:51:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA02147 for current-outgoing; Tue, 27 May 1997 00:51:30 -0700 (PDT) Received: from firewall.ftf.dk (root@[129.142.64.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA02142 for ; Tue, 27 May 1997 00:51:26 -0700 (PDT) Received: from mail.prosa.dk ([192.168.100.2]) by firewall.ftf.dk (8.7.6/8.7.3) with ESMTP id JAA24898 for ; Tue, 27 May 1997 09:56:59 +0200 Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.5/8.8.5/prosa-1.1) with ESMTP id KAA25982 for ; Tue, 27 May 1997 10:00:11 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.5/8.8.5/prosa-1.1) id KAA16334; Tue, 27 May 1997 10:03:03 +0200 (CEST) Message-ID: <19970527100302.65118@deepo.prosa.dk> Date: Tue, 27 May 1997 10:03:02 +0200 From: Philippe Regnauld To: current@FreeBSD.ORG Subject: Re: cd9660 w/ Joliet extensions References: <199705262150.XAA10053@smtp1.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: Main Body X-Mailer: Mutt 0.69 In-Reply-To: <199705262150.XAA10053@smtp1.xs4all.nl>; from Jeroen on Mon, May 26, 1997 at 11:48:44PM +0000 X-Operating-System: FreeBSD 2.2-BETA_A i386 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jeroen writes: > > > C: "Yes, the can. Here's how..." > > "(implied) What valid excuses remain for not having one?" > ^^^^^^^ > That's your opinion > > Because most users do not have that knowledge, in practice they > really can not disable it ;-) How about a simple message in the startup screen of the program being autorun, mentioning where to disable it ? -- -- Phil -[ Philippe Regnauld / Systems Administrator / regnauld@prosa.dk ]- -[ Location.: +55.4N +11.3E PGP Key: finger regnauld@hotel.prosa.dk ]- From owner-freebsd-current Tue May 27 01:15:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA02754 for current-outgoing; Tue, 27 May 1997 01:15:23 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA02749 for ; Tue, 27 May 1997 01:15:19 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-45.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA19048 (5.67b/IDA-1.5 for ); Tue, 27 May 1997 10:15:08 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id KAA06329; Tue, 27 May 1997 10:15:06 +0200 (CEST) X-Face: " Date: Tue, 27 May 1997 10:15:06 +0200 From: Stefan Esser To: John-Mark Gurney Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys interrupt.h src/sys/kern kern_intr.c References: <199705261437.HAA28793@freefall.freebsd.org> <19970527004020.12865@hydrogen.nike.efn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <19970527004020.12865@hydrogen.nike.efn.org>; from John-Mark Gurney on Tue, May 27, 1997 at 12:40:20AM -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 27, John-Mark Gurney wrote: > Stefan Esser scribbled this message on May 26: > > Add support for shared interrupts to the kernel. This code is meant > > be (eventually) architecture independent. It provides an emulation > > does this mean it will also work with ISA irq's? i.e. call the interupt > routine for each device? the reason I ask is that I am working on getting > sio to just probe the devices on the specific irq, and it would be nice to > use something this generic... Well, the proposed new interface are the "intr_create()" and "intr_connect()" functions. The first one takes the same parameters that used to be supplied to register_intr(), but accepts a new "INTR_EXCL" option in the flags parameter. This function returns an pointer to a dynamically allocated interrupt descriptor structure, which is to be treated as opaque by the drivers. A driver can then call intr_connect() to activate the interrupt handler as previously defined by create_intr. Now, regarding your question: There is now a shared interrupt multiplexer, that will be installed instead of the first interrupt handler, and which will call each driver's handler in turn. There is no provision to deal with Edge triggered shared interrupts, though. Your driver will have to make sure, that the interrupt pin sees a new Edge after you leave the multiplex handler, or you will never again see an IRQ. This is normally done by looping until the interrupt line has become inactive, and this loop should go into the low level (coded in assembler) interrupt code, IMHO ... You'd need to specify a flag to create_intr() in that case, which would be accessible to the low level handler, and which would make it just call the same driver handler over and over again, until the IRQ line is inactive. I could work out patches that do this for you to test, or somebody who is more familiar with the low level int code could jump in ... Regards, STefan From owner-freebsd-current Tue May 27 02:35:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA05282 for current-outgoing; Tue, 27 May 1997 02:35:36 -0700 (PDT) Received: from spinner.dialix.com.au (spinner.dialix.com.au [192.203.228.67]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA05201; Tue, 27 May 1997 02:34:27 -0700 (PDT) Received: from spinner.dialix.com.au (localhost.dialix.com.au [127.0.0.1]) by spinner.dialix.com.au with ESMTP id RAA22631; Tue, 27 May 1997 17:34:20 +0800 (WST) Message-Id: <199705270934.RAA22631@spinner.dialix.com.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: Stefan Esser cc: Steve Passe , Glenn Johnson , freebsd-current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: errors on startup In-reply-to: Your message of "Tue, 27 May 1997 08:53:55 +0200." <19970527085355.54719@x14.mi.uni-koeln.de> Date: Tue, 27 May 1997 17:34:19 +0800 From: Peter Wemm Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stefan Esser wrote: > On May 26, Steve Passe wrote: > > + #ifdef APIC_IO > > + if (cfg->intline && (cfg->intline != 0xff)) { > > + u_char airq = 0xff; > > + u_char rirq = 0xff; > > + > > + airq = get_pci_apic_irq(cfg->bus, > > + cfg->slot, cfg->intpin); > > + > > + if (airq != 0xff) { /* APIC IRQ exists */ > > + rirq = cfg->intline; /* 're-directed' IR Q */ > > + cfg->intline = airq; /* use APIC IRQ */ > > + pci_cfgwrite(cfg, PCIR_INTLINE, airq, 1); > > Hmmm, I don't think we should do this anymore ... > The new data structure that holds a copy of the most > important configuration space registers is there just > for the purpose of modifying parameters for drivers, > but without a need to actually change the register > contents ... > > All the drivers will use whatever is in cfg->intline, > so there is no need for the register update, IMHO. I don't have an opinion on updating the register, but I'll re-iterate for the record what we're dealing with.. When the system boots, there is a redirection bridge active somewhere that diverts the pci interrupts down onto the 16 isa irq lines. When the apic's are turned on, this "magically" disappears and the interrupts are often routed to their own interrupt source pin on the apic and the isa interrupt is "magically" freed for other users (eg: isa cards who's drivers can look at the available interrupts, pick one and set the irq output on the card to use it.) There's also the complication that some more modern BIOS's can boot with the APIC's *active* with the PCI interrupts only going to the IO APIC. (I presume this means they don't boot in virtual wire mode, so the 8259 emulations wouldn't be seeing the interrupts either.) We're not sure how this is activated, but as far as I can tell, the OS must update some of the bios settings ( ESCD? DMI? who knows?) at "install time" in order for the "PCI INTS -> IO APIC" bios option to do anything. I saw a mention of it somewhere and it says something to the effect that the setting is only functional if an APIC aware OS is installed - so I presume that means an ESCD setting or something. (What the hell is ESCD anyway?) Cheers, -Peter From owner-freebsd-current Tue May 27 04:23:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA08645 for current-outgoing; Tue, 27 May 1997 04:23:34 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA08640; Tue, 27 May 1997 04:23:24 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id VAA05558; Tue, 27 May 1997 21:18:52 +1000 Date: Tue, 27 May 1997 21:18:52 +1000 From: Bruce Evans Message-Id: <199705271118.VAA05558@godzilla.zeta.org.au> To: gurney_j@resnet.uoregon.edu, se@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys interrupt.h src/sys/kern kern_intr.c Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >driver's handler in turn. There is no provision to deal >with Edge triggered shared interrupts, though. Your >driver will have to make sure, that the interrupt pin >sees a new Edge after you leave the multiplex handler, >or you will never again see an IRQ. This is normally >done by looping until the interrupt line has become >inactive, and this loop should go into the low level >(coded in assembler) interrupt code, IMHO ... No, the loop is best done in individual drivers. The low level code can't read the interrupt pin, at least for the ICU case, and drivers can more easily keep track of their state if they do they loop themselves. The only reason to return to the low level is to give other interrupt handlers a chance to run, which is only worth doing if all the drivers cooperate, but none do. Bruce From owner-freebsd-current Tue May 27 04:40:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA09088 for current-outgoing; Tue, 27 May 1997 04:40:01 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA09056 for ; Tue, 27 May 1997 04:39:51 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-9.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA22078 (5.67b/IDA-1.5 for ); Tue, 27 May 1997 13:39:36 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id NAA01344; Tue, 27 May 1997 13:39:34 +0200 (CEST) X-Face: " Date: Tue, 27 May 1997 13:39:33 +0200 From: Stefan Esser To: Bruce Evans Cc: gurney_j@resnet.uoregon.edu, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys interrupt.h src/sys/kern kern_intr.c References: <199705271118.VAA05558@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199705271118.VAA05558@godzilla.zeta.org.au>; from Bruce Evans on Tue, May 27, 1997 at 09:18:52PM +1000 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 27, Bruce Evans wrote: > >driver's handler in turn. There is no provision to deal > >with Edge triggered shared interrupts, though. Your > >driver will have to make sure, that the interrupt pin > >sees a new Edge after you leave the multiplex handler, > >or you will never again see an IRQ. This is normally > >done by looping until the interrupt line has become > >inactive, and this loop should go into the low level > >(coded in assembler) interrupt code, IMHO ... > > No, the loop is best done in individual drivers. The low level > code can't read the interrupt pin, at least for the ICU case, > and drivers can more easily keep track of their state if they > do they loop themselves. The only reason to return to the But it doesn't suffice, that each driver loops as long as is responsible for the activation of the interrupt line. Before all devices have been serviced, the first one may have asserted the IRQ signal again, and if there is no loop over all devices, until none of them required service, this will quickly hang your system ... > low level is to give other interrupt handlers a chance to run, > which is only worth doing if all the drivers cooperate, but > none do. Hmmm, I was hoping for a way to do the multiplexing from a common pseudo interrupt handler. The original PCI shared interrupt code expected the driver's interrupt handler to return an indication of whether there was any work to do. The multiplexer would loop as long as at least one driver reported it was called for a reason ... :) I had been hoping that the low level code could be made to check a flag, which if set would require the ICU to be queried about the interrupt pin state. But I've got to admit, that it has been too long since I programmed an 8259, and that I don't remember if you could read out the level applied to some edge triggered IRQ pin ... (And you seem to tell me, that there is no way to do this ... Too bad!) How about adding a second type of interrupt multiplexer, which does expect the device's handler to return a status indicating whether this device caused the interrupt ... This multiplexer would only be installed for edge-triggered IRQ lines, and the faster one that just does a single poll pass over all devices would be used for PCI/EISA with level triggered interrupts ... ? Regards, STefan From owner-freebsd-current Tue May 27 05:05:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA10075 for current-outgoing; Tue, 27 May 1997 05:05:13 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA10047 for ; Tue, 27 May 1997 05:05:06 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id MAA29537; Tue, 27 May 1997 12:58:21 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 27 May 1997 12:59:42 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19970526182406.59864@Jupiter.Mcs.Net> References: ; from Bob Bishop on Mon, May 26, 1997 at 07:58:28PM +0100 <19970526115204.46379@Mercury.Mcs.Net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 27 May 1997 12:56:42 +0100 To: Karl Denninger From: Bob Bishop Subject: Re: Boom! :-) Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 0:24 +0100 27/5/97, Karl Denninger wrote: >On Mon, May 26, 1997 at 07:58:28PM +0100, Bob Bishop wrote: >>[...] >> If, as I suspect, 0x8:0xf01119b0 = _lockstatus + 0x8, this is a >> particularly bad case of kern/3581. >>[...] >Hmmm... Don't think so... this looks to be in lockinit... Sure does. Congratulations! Looks like you've found another semi-repeatable way to summon up the lock gremlins! :-) :-) :-{ Seriously folks, the size of this club (people who regularly fall down various lock-related holes) seems to be growing. I have a little time to spare at the moment but I'm not up to speed with this stuff, and I have to say it looks unpleasant. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Tue May 27 05:35:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA11307 for current-outgoing; Tue, 27 May 1997 05:35:38 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA11302 for ; Tue, 27 May 1997 05:35:31 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.7.5/8.7.3) id OAA03997 for freebsd-current@freebsd.org; Tue, 27 May 1997 14:39:18 +0200 (MET DST) From: Mikael Karpberg Message-Id: <199705271239.OAA03997@ocean.campus.luth.se> Subject: Re: cd9660 w/ Joliet extensions To: freebsd-current@freebsd.org Date: Tue, 27 May 1997 14:39:18 +0200 (MET DST) In-Reply-To: <19970527100302.65118@deepo.prosa.dk> from Philippe Regnauld at "May 27, 97 10:03:02 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Philippe Regnauld: > Jeroen writes: > > > > > C: "Yes, the can. Here's how..." > > > "(implied) What valid excuses remain for not having one?" > > ^^^^^^^ > > That's your opinion > > > > Because most users do not have that knowledge, in practice they > > really can not disable it ;-) > > How about a simple message in the startup screen of the program > being autorun, mentioning where to disable it ? Or how about just using what was suggested: Something that adds two items to the "right mouse button menu" for the cd, and also gives it a nifty icon. If someone finds that annoying, then have an attitude problem. It simply doesn't really affect anything except the cd icon. :-) I think everyone is thinking of the installation thingies for games and utilities which throw up a huge window and sounds, and god knows what, just because you happen to insert the CD. It's NOT the same thing. /Mikael From owner-freebsd-current Tue May 27 06:13:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA12557 for current-outgoing; Tue, 27 May 1997 06:13:19 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA12550 for ; Tue, 27 May 1997 06:13:16 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id OAA09238; Tue, 27 May 1997 14:12:56 +0100 (BST) Date: Tue, 27 May 1997 14:12:56 +0100 (BST) From: Doug Rabson To: Bob Bishop cc: Karl Denninger , current@freebsd.org Subject: Re: Boom! :-) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 27 May 1997, Bob Bishop wrote: > At 0:24 +0100 27/5/97, Karl Denninger wrote: > >On Mon, May 26, 1997 at 07:58:28PM +0100, Bob Bishop wrote: > >>[...] > >> If, as I suspect, 0x8:0xf01119b0 = _lockstatus + 0x8, this is a > >> particularly bad case of kern/3581. > >>[...] > >Hmmm... Don't think so... this looks to be in lockinit... > > Sure does. Congratulations! Looks like you've found another semi-repeatable > way to summon up the lock gremlins! :-) :-) :-{ > > Seriously folks, the size of this club (people who regularly fall down > various lock-related holes) seems to be growing. I have a little time to > spare at the moment but I'm not up to speed with this stuff, and I have to > say it looks unpleasant. This is a workaround for the lockstatus panic. A better fix will probably have to wait until Peter is finished with poll(2). Index: ufs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_vnops.c,v retrieving revision 1.50 diff -u -r1.50 ufs_vnops.c --- ufs_vnops.c 1997/05/17 18:32:53 1.50 +++ ufs_vnops.c 1997/05/27 13:11:19 @@ -1788,6 +1788,9 @@ } */ *ap; { + if (ap->a_vp->v_flag & VXLOCK) + return TRUE; + return (lockstatus(&VTOI(ap->a_vp)->i_lock)); } -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 From owner-freebsd-current Tue May 27 06:16:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA12710 for current-outgoing; Tue, 27 May 1997 06:16:49 -0700 (PDT) Received: from mx12.netvision.net.il (mx12.NetVision.net.il [194.90.1.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA12704 for ; Tue, 27 May 1997 06:16:44 -0700 (PDT) Received: (qmail 10906 invoked from network); 27 May 1997 13:16:33 -0000 Received: from burka.netvision.net.il (gena@194.90.1.23) by mx12.netvision.net.il with SMTP; 27 May 1997 13:16:33 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 27 May 1997 16:16:32 +0300 (IDT) X-Face: #v>4HN>#D_"[olq9y`HqTYkLVB89Xy|3')Vs9v58JQ*u-xEJVKY`xa.}E?z0RkLI/P&;BJmi0#u=W0).-Y'J4(dw{"54NhSG|YYZG@[)(`e! >jN#L!~qI5fE-JHS+< Organization: NetVision Ltd. From: Gennady Sorokopud To: Bob Bishop Subject: Re: Boom! :-) Cc: current@FreeBSD.ORG, Karl Denninger Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi! On 27-May-97 Bob Bishop wrote: >At 0:24 +0100 27/5/97, Karl Denninger wrote: >>On Mon, May 26, 1997 at 07:58:28PM +0100, Bob Bishop wrote: >>>[...] >>> If, as I suspect, 0x8:0xf01119b0 = _lockstatus + 0x8, this is a >>> particularly bad case of kern/3581. >>>[...] >>Hmmm... Don't think so... this looks to be in lockinit... > >Sure does. Congratulations! Looks like you've found another semi-repeatable >way to summon up the lock gremlins! :-) :-) :-{ > >Seriously folks, the size of this club (people who regularly fall down >various lock-related holes) seems to be growing. I have a little time to >spare at the moment but I'm not up to speed with this stuff, and I have to >say it looks unpleasant. My system crashes due to this problem every 3-5 hours. I even found a way to reliably reproduce it - stat() on a file with a VERY long filename. However after i removed this file (booting an old kernel) the problem is still there, and i'm positive that there are no more such files around on my FS...weird. > > >-- >Bob Bishop (0118) 977 4017 international code +44 118 >rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK Best regards. -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: Gennady Sorokopud PGP public key is available by fingering gena@netvision.net.il This message was sent at 27-May-97 16:16:32 by XFMail From owner-freebsd-current Tue May 27 06:23:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA12887 for current-outgoing; Tue, 27 May 1997 06:23:09 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA12882 for ; Tue, 27 May 1997 06:23:06 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id IAA00976; Tue, 27 May 1997 08:22:46 -0500 (EST) From: "John S. Dyson" Message-Id: <199705271322.IAA00976@dyson.iquest.net> Subject: Re: Boom! :-) In-Reply-To: from Bob Bishop at "May 27, 97 12:56:42 pm" To: rb@gid.co.uk (Bob Bishop) Date: Tue, 27 May 1997 08:22:46 -0500 (EST) Cc: karl@Mcs.Net, current@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Sure does. Congratulations! Looks like you've found another semi-repeatable > way to summon up the lock gremlins! :-) :-) :-{ > > Seriously folks, the size of this club (people who regularly fall down > various lock-related holes) seems to be growing. I have a little time to > spare at the moment but I'm not up to speed with this stuff, and I have to > say it looks unpleasant. > > I have found one case in the VM system where the lock code is being misused. I'll be looking at the rest of the kernel for equiv mistakes. John From owner-freebsd-current Tue May 27 06:35:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA13462 for current-outgoing; Tue, 27 May 1997 06:35:28 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA13452; Tue, 27 May 1997 06:35:19 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id XAA10911; Tue, 27 May 1997 23:32:26 +1000 Date: Tue, 27 May 1997 23:32:26 +1000 From: Bruce Evans Message-Id: <199705271332.XAA10911@godzilla.zeta.org.au> To: bde@zeta.org.au, se@freebsd.org Subject: Re: cvs commit: src/sys/sys interrupt.h src/sys/kern kern_intr.c Cc: current@freebsd.org, gurney_j@resnet.uoregon.edu Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >[Edge sensitive share interrupts] >> No, the loop is best done in individual drivers. The low level >But it doesn't suffice, that each driver loops as long >as is responsible for the activation of the interrupt line. I assumed only one driver per interrupt line. >I had been hoping that the low level code could be made >to check a flag, which if set would require the ICU to be >queried about the interrupt pin state. But I've got to >admit, that it has been too long since I programmed an 8259, >and that I don't remember if you could read out the level >applied to some edge triggered IRQ pin ... (And you seem >to tell me, that there is no way to do this ... Too bad!) You can read the state of the IRQ pin from the request latch if the edge latch is not set. Otherwise the request latch is 0. There is no way to read or write the edge latch (other than reinitializing the 8259). Thus the request latch is perfectly unusable for recovering from edge triggering braindamage. It can only be used to determine the IRQ state of masked interrupts. >How about adding a second type of interrupt multiplexer, >which does expect the device's handler to return a status >indicating whether this device caused the interrupt ... >This multiplexer would only be installed for edge-triggered >IRQ lines, and the faster one that just does a single poll >pass over all devices would be used for PCI/EISA with level >triggered interrupts ... ? This can be now done without changing all drivers by returning the status in the interrupt descriptor instead of directly. Bruce From owner-freebsd-current Tue May 27 07:36:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA15984 for current-outgoing; Tue, 27 May 1997 07:36:54 -0700 (PDT) Received: from pat.idt.unit.no (0@pat.idt.unit.no [129.241.103.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA15970 for ; Tue, 27 May 1997 07:36:43 -0700 (PDT) Received: from idt.unit.no (tegge@ikke.idi.ntnu.no [129.241.111.65]) by pat.idt.unit.no (8.8.5/8.8.5) with ESMTP id QAA14136; Tue, 27 May 1997 16:35:58 +0200 (MET DST) Message-Id: <199705271435.QAA14136@pat.idt.unit.no> To: karl@Mcs.Net Cc: rb@gid.co.uk, current@FreeBSD.ORG Subject: Re: Boom! :-) In-Reply-To: Your message of "Mon, 26 May 1997 18:24:06 -0500" References: <19970526182406.59864@Jupiter.Mcs.Net> X-Mailer: Mew version 1.06 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 27 May 1997 16:35:57 +0200 From: Tor Egge Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hmmm... Don't think so... this looks to be in lockinit... [...] > f01119a0 F kern_lock.o > f01119a0 T _lockinit > f01119e8 T _lockstatus > f0111b14 T _lockmgr > f0112068 T _lockmgr_printinfo > f01120d0 F kern_lockf.o Do you have a disassembly of the lockinit function ? virtual address 0x44 looks very much like the lk_exclusivecount member of the lock structure, when a pointer to a struct inode, struct iso_inode, or a struct denode is a NULL pointer. ---- 0xe0116030 : pushl %ebp 0xe0116031 : movl %esp,%ebp 0xe0116033 : pushl %esi 0xe0116034 : pushl %ebx 0xe0116035 : movl 0x8(%ebp),%eax 0xe0116038 : movl 0xc(%ebp),%edx 0xe011603b : movl 0x10(%ebp),%ecx 0xe011603e : movl 0x14(%ebp),%ebx 0xe0116041 : movl 0x18(%ebp),%esi 0xe0116044 : andl $0x70,%esi 0xe0116047 : movl %esi,0x4(%eax) 0xe011604a : movl $0x0,0x8(%eax) 0xe0116051 : movl $0x0,0xc(%eax) 0xe0116058 : movw $0x0,0x10(%eax) 0xe011605e : movw %dx,0x12(%eax) 0xe0116062 : movl %ecx,0x14(%eax) 0xe0116065 : movl %ebx,0x18(%eax) 0xe0116068 : movl $0xffffffff,0x1c(%eax) 0xe011606f : leal 0xfffffff8(%ebp),%esp 0xe0116072 : popl %ebx 0xe0116073 : popl %esi 0xe0116074 : leave 0xe0116075 : ret ---- (gdb) print &((struct inode *) 0)->i_lock $4 = (struct lock *) 0x34 (gdb) print &((struct iso_node *) 0)->i_lock $6 = (struct lock *) 0x34 (gdb) print &((struct denode *) 0)->de_lock $7 = (struct lock *) 0x34 (gdb) print &((struct vm_map *) 0)->ref_lock $8 = (struct simplelock *) 0x58 (gdb) print &((struct mount *) 0)->mnt_lock $9 = (struct lock *) 0x18 (gdb) print &((struct inode *) 0)->i_lock.lk_exclusivecount $12 = (short int *) 0x44 (gdb) print &((struct vm_map *) 0)->lock $13 = (struct lock *) 0x4 ---- Two strange things: 1. lockinit + 0x10 is not on an instruction boundary. (Note: using this disassembly of the lockinit function). 2. none of struct inode, struct iso_inode, struct denode, struct vm_map or struct mount seems to have the lock at the proper offset in the structure for 0x44 to be the faulting address in lockinit. (Note: using this disassembly of the lockinit function). Will the following sequence of events reproduce the crash ? rlogin (or telnet) to target machine run top in the foreground in that rlogin/telnet session Use ~ . or ESC ] c to close the connection on the target machine. In about 50% of the cases, the machine should crash. If the crash is identical to what you have experienced, this is probably another instance of kern/3581, where this patch might help: ---- Index: spec_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/miscfs/specfs/spec_vnops.c,v retrieving revision 1.39 diff -c -r1.39 spec_vnops.c *** spec_vnops.c 1997/05/01 19:12:22 1.39 --- spec_vnops.c 1997/05/24 00:39:29 *************** *** 595,600 **** --- 595,601 ---- * plus the session), release the reference from the session. */ if (vcount(vp) == 2 && ap->a_p && + (vp->v_flag & VXLOCK) == 0 && vp == ap->a_p->p_session->s_ttyvp) { vrele(vp); ap->a_p->p_session->s_ttyvp = NULL; ---- - Tor Egge From owner-freebsd-current Tue May 27 09:27:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA20400 for current-outgoing; Tue, 27 May 1997 09:27:21 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA20395 for ; Tue, 27 May 1997 09:27:19 -0700 (PDT) Received: from critter.dk.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0wWP5E-0003vwC; Tue, 27 May 97 09:26 PDT Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id SAA02607 for ; Tue, 27 May 1997 18:25:01 +0200 (CEST) To: current@freebsd.org Subject: RFC2143, IP over SCSI From: Poul-Henning Kamp Date: Tue, 27 May 1997 18:25:01 +0200 Message-ID: <2605.864750301@critter.dk.tfs.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK, now we have a standard, who comes up with some code ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue May 27 10:21:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA23173 for current-outgoing; Tue, 27 May 1997 10:21:38 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA23167 for ; Tue, 27 May 1997 10:21:31 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA15578; Tue, 27 May 1997 10:17:43 -0700 From: Terry Lambert Message-Id: <199705271717.KAA15578@phaeton.artisoft.com> Subject: Re: cd9660 w/ Joliet extensions To: albast@magigimmix.xs4all.nl (Jeroen) Date: Tue, 27 May 1997 10:17:43 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: <199705262150.XAA10053@smtp1.xs4all.nl> from "Jeroen" at May 26, 97 11:48:44 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > C: "Yes, the can. Here's how..." > > "(implied) What valid excuses remain for not having one?" > ^^^^^^^ > That's your opinion No, that's my question. An opinion would have been if I had stated that there were no valid excuses remaining. I did not. > Because most users do not have that knowledge, in practice they > really can not disable it ;-) Well, they have to live with it, or become educated. Just like all other Windows95 targetted CDROM's in the world. > > D: "Can't you move this thread? I (erroneously) believe it's > > not relevent..." > > No, I don't believe going in depth with the windows stuff is relevant > here. Would you have believed me if I had just said "yes, there is."? > PS: I apologize for my somewhat crude mail, Terry :) > I'm not going to "explain", just take it ;-) Heh. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue May 27 10:27:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA23591 for current-outgoing; Tue, 27 May 1997 10:27:50 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA23568 for ; Tue, 27 May 1997 10:27:36 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA15619; Tue, 27 May 1997 10:23:31 -0700 From: Terry Lambert Message-Id: <199705271723.KAA15619@phaeton.artisoft.com> Subject: Re: Weird behaviour from the Linux emulator To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 27 May 1997 10:23:31 -0700 (MST) Cc: roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG In-Reply-To: <199705270615.PAA28391@genesis.atrad.adelaide.edu.au> from "Michael Smith" at May 27, 97 03:45:41 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I understand the need to shadow the real filesystem but it should be done > > only for the search for libraries/binaries, not for every open(2) call. > > Aha. And how do you think that libraries/binaries are searched for, if > not by open(2)? Then how about configuration files, hmm? Binaries are searched by execve(), of course; it's possible to distinguish a file being opened for read from one being opened for execution. This is the basis for my argument for an option for prefaulting to swap on a remote file system load of an executable so that my client machines don't hang when my NFS server is being rebooted. As far as shared libraries go, they can be faulted the same way when an mmap() with the PROT_EXEC flag occurs. For shared libraries, this is before the crt0.o code calls _main in the first place. For dlopen(), well, you take your chances (like you currently do anyway) and you recommend in the man page that the open occur as soon as possible to trigger the fault to swap. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue May 27 10:46:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA24536 for current-outgoing; Tue, 27 May 1997 10:46:38 -0700 (PDT) Received: from rayearth.rim.or.jp (uucp@rayearth.rim.or.jp [202.247.130.242]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA24527 for ; Tue, 27 May 1997 10:46:28 -0700 (PDT) Received: (from uucp@localhost) by rayearth.rim.or.jp (8.8.5/3.5Wpl2-uucp1/RIMNET) with UUCP id CAA24301; Wed, 28 May 1997 02:46:20 +0900 (JST) Received: from tky007.tth.expo96.ad.jp (localhost [127.0.0.1]) by mail.aslm.rim.or.jp (8.8.5/3.4W4-SMTP) with ESMTP id CAA01171; Wed, 28 May 1997 02:45:07 +0900 (JST) Message-Id: <199705271745.CAA01171@mail.aslm.rim.or.jp> To: freebsd-current@freebsd.org Cc: max@wide.ad.jp Subject: PPP on -current From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 28 May 1997 02:45:06 +0900 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm running FreeBSD-current as of today. Lately, ppp acts strangely when the dialing procedure fails like following: Using interface: tun0 Interactive mode ppp ON turkey> dial Dial attempt 1 of 1 Phone: xxxxx dial failed. ppp ON turkey> Packet mode. ppp ON turkey> dial LCP state is [Req-Sent] ppp ON turkey> close ppp ON turkey> dial LCP state is [Closing] ppp ON turkey> And I have to wait for maybe half a minute or so until I can issue the dial command again. Has there been any change that requires modification of configuration? What should I do to get around this problem? Thanks, Max ----------------------------------------------------------------------- Masafumi NAKANE, Keio Univ., Dept. of Environmental Information E-Mail : max@wide.ad.jp / max@FreeBSD.ORG [URL] : http://www.sfc.wide.ad.jp/~max/ From owner-freebsd-current Tue May 27 11:09:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA25755 for current-outgoing; Tue, 27 May 1997 11:09:16 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA25750 for ; Tue, 27 May 1997 11:09:14 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-38.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA27710 (5.67b/IDA-1.5 for ); Tue, 27 May 1997 20:08:14 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id UAA07854; Tue, 27 May 1997 20:07:41 +0200 (CEST) X-Face: " Date: Tue, 27 May 1997 20:07:40 +0200 From: Stefan Esser To: Bruce Evans Cc: current@FreeBSD.ORG, gurney_j@resnet.uoregon.edu Subject: Re: cvs commit: src/sys/sys interrupt.h src/sys/kern kern_intr.c References: <199705271332.XAA10911@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199705271332.XAA10911@godzilla.zeta.org.au>; from Bruce Evans on Tue, May 27, 1997 at 11:32:26PM +1000 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 27, Bruce Evans wrote: > >> >[Edge sensitive share interrupts] > > >> No, the loop is best done in individual drivers. The low level > > >But it doesn't suffice, that each driver loops as long > >as is responsible for the activation of the interrupt line. > > I assumed only one driver per interrupt line. Well, that's easy ... But the original question was, whether the new shared interrupt support might be applicable to ISA drivers, and the consent seems to be, that it isn't for the reason you give below: > You can read the state of the IRQ pin from the request latch > if the edge latch is not set. Otherwise the request latch > is 0. There is no way to read or write the edge latch > (other than reinitializing the 8259). Thus the request latch > is perfectly unusable for recovering from edge triggering > braindamage. It can only be used to determine the IRQ state > of masked interrupts. I guess we just should say NO, then. The sio driver may implement its own interrupt mux code, and the other ISA drivers will continue to work with non-shared interrupts, only. > This can be now done without changing all drivers by returning > the status in the interrupt descriptor instead of directly. Hmmm, I wonder whether this would be useful to have ... If its only for the SIO driver, I'd avoid the added complexity of having this in the generic interrupt code ... Regards, STefan From owner-freebsd-current Tue May 27 12:06:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA28782 for current-outgoing; Tue, 27 May 1997 12:06:02 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA28773 for ; Tue, 27 May 1997 12:05:57 -0700 (PDT) Received: from Mercury.mcs.net (Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id OAA01649; Tue, 27 May 1997 14:05:31 -0500 (CDT) Received: (from karl@localhost) by Mercury.mcs.net (8.8.5/8.8.2) id OAA07169; Tue, 27 May 1997 14:05:31 -0500 (CDT) Message-ID: <19970527140531.12098@Mercury.Mcs.Net> Date: Tue, 27 May 1997 14:05:31 -0500 From: Karl Denninger To: Doug Rabson Cc: Bob Bishop , Karl Denninger , current@FreeBSD.ORG Subject: Re: Boom! :-) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: ; from Doug Rabson on Tue, May 27, 1997 at 02:12:56PM +0100 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, May 27, 1997 at 02:12:56PM +0100, Doug Rabson wrote: > On Tue, 27 May 1997, Bob Bishop wrote: > > > At 0:24 +0100 27/5/97, Karl Denninger wrote: > > >On Mon, May 26, 1997 at 07:58:28PM +0100, Bob Bishop wrote: > > >>[...] > > >> If, as I suspect, 0x8:0xf01119b0 = _lockstatus + 0x8, this is a > > >> particularly bad case of kern/3581. > > >>[...] > > >Hmmm... Don't think so... this looks to be in lockinit... > > > > Sure does. Congratulations! Looks like you've found another semi-repeatable > > way to summon up the lock gremlins! :-) :-) :-{ > > > > Seriously folks, the size of this club (people who regularly fall down > > various lock-related holes) seems to be growing. I have a little time to > > spare at the moment but I'm not up to speed with this stuff, and I have to > > say it looks unpleasant. > > This is a workaround for the lockstatus panic. A better fix will probably > have to wait until Peter is finished with poll(2). > > Index: ufs_vnops.c > =================================================================== > RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_vnops.c,v > retrieving revision 1.50 > diff -u -r1.50 ufs_vnops.c > --- ufs_vnops.c 1997/05/17 18:32:53 1.50 > +++ ufs_vnops.c 1997/05/27 13:11:19 > @@ -1788,6 +1788,9 @@ > } */ *ap; > { > > + if (ap->a_vp->v_flag & VXLOCK) > + return TRUE; > + > return (lockstatus(&VTOI(ap->a_vp)->i_lock)); > } > > > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 951 1891 > Fax: +44 181 381 1039 > That patch does NOT stop the panics: Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #1: Tue May 27 09:55:02 CDT 1997 karl@Codebase.mcs.net:/usr/src/sys/compile/MCS_STANDARD CPU: Pentium (90.00-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x521 Stepping=1 Features=0x5bf> real memory = 67108864 (65536K bytes) Physical memory hole(s): avail memory = 62939136 (61464K bytes) eisa0: Probing for devices on the EISA bus ahb0: at 0x1c00-0x1cff irq 11 on eisa0 slot 1 ahb0: waiting for scsi devices to settle scbus0 at ahb0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 1002MB (2053880 512 byte sectors) sd0: with 2428 cyls, 9 heads, and an average 93 sectors/track Probing for devices on PCI bus 0: chip0: rev 0x11 on pci0.0.0 chip1: rev 0x03 on pci0.2.0 de0: rev 0x12 int a irq 10 on pci0.6.0 de0: SMC 9332 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:c0:82:ea:e3 de0: enabling 10baseT port Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 3 maddr 0xd0000 msize 16384 on isa ed0: address 00:00:c0:15:2c:76, type SMC8216T (16 bit) ed1 not found at 0x300 sio0 not found at 0x3f8 sio1 not found at 0x2f8 sio2: disabled, not probed. sio3: disabled, not probed. lpt0 not found lpt1 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 aha0 not found at 0x330 aic0 not found at 0x340 npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers WARNING: / was not properly dismounted. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10 fault code = supervisor read, page not present instruction pointer = 0x8:0xf019c831 stack pointer = 0x10:0xf68c2f10 frame pointer = 0x10:0xf68c2f4c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 4 (update) interrupt mask = trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in \M^?\^Code fault virtual address = 0x10 fault code = supervisor read, page not present instruction pointer = 0x8:0xf019c831 stack pointer = 0x10:0xf68c2da8 frame pointer = 0x10:0xf68c2de4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 4 (update) interrupt mask = trap number = 12 panic: page fault Automatic reboot in 15 seconds - press a key on the console to abort f019b720 F ffs_vfsops.o f019b720 t ___set_vfs_set_sym__fs_vfsconf f019b7c0 t _ffs_mount f019bacc t _ffs_reload f019be68 T _ffs_mountfs f019c460 t _ffs_oldfscompat f019c4f4 T _ffs_unmount f019c640 T _ffs_flushfiles f019c6a4 T _ffs_statfs f019c7bc T _ffs_sync <<<< It moves to here. f019c9a0 T _ffs_vget f019cc74 T _ffs_fhtovp f019ccc0 T _ffs_vptofh f019cce4 t _ffs_init f019ccf4 t _ffs_sbupdate f019ce80 F ffs_vnops.o f019ce80 t ___set_vfs_opv_descs__sym_ffs_vnodeop_opv_desc f019ce84 t ___set_vfs_opv_descs__sym_ffs_specop_opv_desc f019ce88 t ___set_vfs_opv_descs__sym_ffs_fifoop_opv_desc f019ce8c t _sysctl___vfs_ffs f019ceb0 t ___set_sysctl__vfs_sym_sysctl___vfs_ffs f019ceb4 t ___set_sysctl__vfs_ffs_sym_sysctl___vfs_ffs f019ceb8 t _sysctl___vfs_ffs_doclusterread f019cee4 t ___set_sysctl__vfs_ffs_sym_sysctl___vfs_ffs_doclusterread f019cee8 t _sysctl___vfs_ffs_doclusterwrite f019cf14 t ___set_sysctl__vfs_ffs_sym_sysctl___vfs_ffs_doclusterwrite f019cf18 t _ffs_read f019d318 t _ffs_write f019d914 t _ffs_getpages f019de04 t _ffs_fsync f019dfd0 T _ffs_reclaim f019e020 F ufs_bmap.o The patch masked the symptom, but not the disease. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | 99 Analog numbers, 77 ISDN, http://www.mcs.net/ Voice: [+1 312 803-MCS1 x219]| NOW Serving 56kbps DIGITAL on our analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-current Tue May 27 12:12:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA29035 for current-outgoing; Tue, 27 May 1997 12:12:00 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA28996; Tue, 27 May 1997 12:11:25 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id NAA04925; Tue, 27 May 1997 13:11:22 -0600 (MDT) Message-Id: <199705271911.NAA04925@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Stefan Esser cc: Bruce Evans , current@FreeBSD.ORG, gurney_j@resnet.uoregon.edu Subject: Re: cvs commit: src/sys/sys interrupt.h src/sys/kern kern_intr.c In-reply-to: Your message of "Tue, 27 May 1997 20:07:40 +0200." <19970527200740.32152@x14.mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 May 1997 14:09:00 -0600 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I assumed only one driver per interrupt line. > >Well, that's easy ... >But the original question was, whether the new shared interrupt >support might be applicable to ISA drivers, and the consent seems >to be, that it isn't for the reason you give below: I think that we should support it since I can see it being used not only in the sio driver but for other multi-function devices like sound cards. Having a separate driver for each function on a card is much cleaner than a single monolithic driver and since it seems easy to add the ability to handle this case (set a flag in the descriptor that says "run me again please"), why not do it? -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue May 27 15:11:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA06752 for current-outgoing; Tue, 27 May 1997 15:11:47 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA06747 for ; Tue, 27 May 1997 15:11:45 -0700 (PDT) Received: from www.sdsp.mc.xerox.com ([13.231.132.18]) by alpha.xerox.com with SMTP id <15056(8)>; Tue, 27 May 1997 15:11:10 PDT Received: from gnu.sdsp.mc.xerox.com (gnu.sdsp.mc.xerox.com [13.231.133.90]) by www.sdsp.mc.xerox.com (8.8.5/8.8.5) with SMTP id SAA14414; Tue, 27 May 1997 18:12:15 -0400 (EDT) Received: by gnu.sdsp.mc.xerox.com (4.1/client-1.3) id AA27748; Tue, 27 May 97 18:11:45 EDT Message-Id: <9705272211.AA27748@gnu.sdsp.mc.xerox.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert Cc: hoek@hwcn.org, jkh@time.cdrom.com, hosokawa@ntc.keio.ac.jp, current@freebsd.org Subject: Re: cd9660 w/ Joliet extensions In-Reply-To: Your message of "Sun, 25 May 1997 13:39:23 PDT." <199705252039.NAA12466@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 May 1997 15:11:44 PDT From: "Marty Leisner" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There's some linux work on this...its not mainstream (I think its located in Berkeley someplace) I haven't used it (the patch didn't fit in...) -- marty leisner@sdsp.mc.xerox.com The Feynman problem solving Algorithm 1) Write down the problem 2) Think real hard 3) Write down the answer Murray Gel-mann in the NY Times From owner-freebsd-current Tue May 27 15:13:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA06870 for current-outgoing; Tue, 27 May 1997 15:13:44 -0700 (PDT) Received: from pegasus.isr.uc.pt (pegasus.isr.uc.pt [193.136.230.60]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA06845 for ; Tue, 27 May 1997 15:13:15 -0700 (PDT) Received: from localhost by pegasus.isr.uc.pt (5.x/SMI-SVR4) id AA14006; Tue, 27 May 1997 22:13:50 +0100 Date: Tue, 27 May 1997 22:13:50 +0100 (WET DST) From: Paulo Menezes X-Sender: paulo@pegasus To: current@freebsd.org Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, I am trying to export several filesystems in FBSD NFS Server and it seems rather dificult :( I RTFMed and found nothing that could help me. Is there a problem with mountd or with my english? :) Can anyone tell me what is the problem with the following exports file? ---- /export/home4/users -maproot=root:wheel pegasus orion centauro vega wagner haydn pioneer sirius mozart verdi marvin lapa # /export/ports -maproot=root:wheel marvin /usr/src -maproot=root:wheel marvin lapa # # /export/obj -maproot=root:wheel marvin lapa ---- I am using 2.2-stable. TIA, Paulo From owner-freebsd-current Tue May 27 16:00:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA08889 for current-outgoing; Tue, 27 May 1997 16:00:04 -0700 (PDT) Received: from mercury.uniserve.com (mercury.uniserve.com [204.191.197.248]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA08879 for ; Tue, 27 May 1997 16:00:02 -0700 (PDT) Received: from haven.uniserve.com (shell.uniserve.com [198.53.215.121]) by mercury.uniserve.com with SMTP id PAA09644; Tue, 27 May 1997 15:59:38 -0700 (PDT) Date: Tue, 27 May 1997 16:04:42 -0700 (PDT) From: Tom Samplonius To: Paulo Menezes cc: current@FreeBSD.ORG Subject: Re: your mail In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 27 May 1997, Paulo Menezes wrote: > > Hi all, > > I am trying to export several filesystems in FBSD NFS Server and it seems > rather dificult :( > I RTFMed and found nothing that could help me. Is there a problem with > mountd or with my english? :) > Can anyone tell me what is the problem with the following exports file? > > ---- > /export/home4/users -maproot=root:wheel pegasus orion centauro vega wagner > haydn > pioneer sirius mozart verdi marvin lapa > # > /export/ports -maproot=root:wheel marvin > /usr/src -maproot=root:wheel marvin lapa > # > # > /export/obj -maproot=root:wheel marvin lapa > ---- You can only have one line in exports for each filesystem that you export. The reason why is that attributes for NFS exports are set on a filesystem, by filesystem basis. For example, the /export/ports, /usr/src, and /export/obj could (and should) be specified on the same line. Tom From owner-freebsd-current Tue May 27 17:32:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA11709 for current-outgoing; Tue, 27 May 1997 17:32:15 -0700 (PDT) Received: from ian.broken.net (R-ddo.resnet.ucsb.edu [128.111.120.207]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA11704 for ; Tue, 27 May 1997 17:32:12 -0700 (PDT) Received: (from ian@localhost) by ian.broken.net (8.8.5/8.7.3) id RAA06724; Tue, 27 May 1997 17:30:36 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <9705272211.AA27748@gnu.sdsp.mc.xerox.com> Date: Tue, 27 May 1997 17:26:13 -0700 (PDT) From: Ian Struble To: Marty Leisner Subject: Re: cd9660 w/ Joliet extensions Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >There's some linux work on this...its not mainstream (I think its >located in Berkeley someplace) http://bmrc.berkeley.edu/people/chaffee/joliet.html I haven't used it myself but a friend is using right now. It took a little work to get it going but it seems stable now that it is running. Ian ---- Death is God's way of telling you not to be such a wise guy. ---- From owner-freebsd-current Tue May 27 17:43:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA12374 for current-outgoing; Tue, 27 May 1997 17:43:12 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA12369 for ; Tue, 27 May 1997 17:43:08 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id RAA29028; Tue, 27 May 1997 17:45:16 -0700 (PDT) Message-ID: <19970527174515.00540@hydrogen.nike.efn.org> Date: Tue, 27 May 1997 17:45:15 -0700 From: John-Mark Gurney To: Tom Samplonius Cc: Paulo Menezes , current@FreeBSD.ORG Subject: Re: your mail References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Tom Samplonius on Tue, May 27, 1997 at 04:04:42PM -0700 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius scribbled this message on May 27: > > On Tue, 27 May 1997, Paulo Menezes wrote: > > > > > Hi all, > > > > I am trying to export several filesystems in FBSD NFS Server and it seems > > rather dificult :( > > I RTFMed and found nothing that could help me. Is there a problem with > > mountd or with my english? :) > > Can anyone tell me what is the problem with the following exports file? > > > > ---- > > /export/home4/users -maproot=root:wheel pegasus orion centauro vega wagner > > haydn > > pioneer sirius mozart verdi marvin lapa > > # > > /export/ports -maproot=root:wheel marvin > > /usr/src -maproot=root:wheel marvin lapa > > # > > # > > /export/obj -maproot=root:wheel marvin lapa > > ---- > > You can only have one line in exports for each filesystem that you no... you can only have one line per fs per host... and then one line for the other hosts that you didn't specificly list... what I do is list all dirs on a fs on a per host basis... that way it's easier to track conflicts... then I have blank lines between each fs... at the very end I list all the "world" exported fs's... basicly this is the important part from exports(5): A host may be specified only once for each local filesystem on the server and there may be only one default en- try for each server filesystem that applies to all other hosts. this is in the second paragraph of DESCRIPTION... hope this helps people... ttyl.. -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Tue May 27 18:20:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA14032 for current-outgoing; Tue, 27 May 1997 18:20:26 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA14027; Tue, 27 May 1997 18:20:19 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA26315; Tue, 27 May 1997 18:13:04 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd026311; Wed May 28 01:13:00 1997 Message-ID: <338B8674.794BDF32@whistle.com> Date: Tue, 27 May 1997 18:12:20 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Brian Beattie CC: Julian Elischer , current@FreeBSD.ORG, mckusick@vangogh.cs.berkeley.edu Subject: Re: NEW FEATURE. BSD file NOUNLINK flag. RFC.. will commit unless.... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian Beattie wrote: > > On Sun, 25 May 1997, Julian Elischer wrote: > > > > > I would like feedback on a new feature I want to add to the > > filesystem code. > > > > In addition to the immutible and append flags, we at whistle are > > using a flag NOUNLINK > > > > The action of this flag is to allow the file or dir in question > > to be modified in any way but never deleted. > > I would be opposed to this as, unlike the immutible flag, I can not see > how is adds to the robustness or security of the system. It adds yet > another hidden control and contributes to bloat and feeping creaturisim. > If this must be added it should be an kernel config option, normally off. > > I can see "Unremovable file ... even when I log into the system as root I > can not remove this file ... !$%*^)^$# FreeBSD sucks". immutible already gives you this.. > > Matbe if somebody could explain how this fixes some major problem I might > feel differently. well its'a MAJOR problem for US as we a re trying to turn freeBSD into an embedded OS in a 'appliance'.. see www.whistle.com once again.... OK here is the picture we have several users. all untrusted. some must be in a group 'admin' that allows them to write to and delete anything in a certain subtree.. EXCEPT a skeleton hierarchy of directories. When the system is in administration mode, the REAL admin (root in single-user) can add to and change that skeleton hierarchy. All users must be able to write to their own directories in the hierarchy (and delete). So far, if we have a group 'admin', then users in that group can do things an admin should be able to do if the whole hierarchy has a group of admin. HOWEVER these are UNTRUSTED admins, and must not be able to delete parts of the essential skeleton hierarchy. With a NOUNLINK bit we can nail down the hierarchy when in 'real' admin mode, and the 'untrusted' admins can't smash it. As a side note, they are running through the netatalk, samba and ftp interfaces and don't see 'unix' as such. The trouble with IMMUTIBLE and APPEND is that they don't allow the users to create and delete their own files freely within the established hierarchy. The sticky bit is CLOSE, but we run into trouble with more than one user with admin privs because they can't un-do each other's damage. To your comment.. This is no more 'annoying' than the 'IMMUTIBLE' flag that presently does even more.. personally I think it complements the other flags quite well. comments? julian From owner-freebsd-current Tue May 27 20:49:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA20503 for current-outgoing; Tue, 27 May 1997 20:49:09 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA20493; Tue, 27 May 1997 20:49:01 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id DAA14336; Wed, 28 May 1997 03:49:08 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma014333; Wed May 28 03:48:55 1997 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id UAA03107; Tue, 27 May 1997 20:48:25 -0700 Date: Tue, 27 May 1997 20:48:25 -0700 From: "M.R.Murphy" Message-Id: <199705280348.UAA03107@meerkat.mole.org> To: beattie@stt3.com, julian@whistle.com Subject: Re: NEW FEATURE. BSD file NOUNLINK flag. RFC.. will commit unless.... Cc: current@FreeBSD.ORG, julian@FreeBSD.ORG, mckusick@vangogh.cs.berkeley.edu Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From owner-freebsd-current@FreeBSD.ORG Tue May 27 18:54:41 1997 > Date: Tue, 27 May 1997 18:12:20 -0700 > From: Julian Elischer > To: Brian Beattie > CC: Julian Elischer , current@FreeBSD.ORG, > mckusick@vangogh.cs.berkeley.edu > Subject: Re: NEW FEATURE. BSD file NOUNLINK flag. RFC.. will commit unless.... > > Brian Beattie wrote: > > > > On Sun, 25 May 1997, Julian Elischer wrote: > > > > > > > > I would like feedback on a new feature I want to add to the > > > filesystem code. > > > > > > In addition to the immutible and append flags, we at whistle are > > > using a flag NOUNLINK > > > > > > The action of this flag is to allow the file or dir in question > > > to be modified in any way but never deleted. > > > > I would be opposed to this as, unlike the immutible flag, I can not see > > how is adds to the robustness or security of the system. It adds yet > > another hidden control and contributes to bloat and feeping creaturisim. > > If this must be added it should be an kernel config option, normally off. > > > > I can see "Unremovable file ... even when I log into the system as root I > > can not remove this file ... !$%*^)^$# FreeBSD sucks". > > immutible already gives you this.. > > > > > Matbe if somebody could explain how this fixes some major problem I might > > feel differently. > well its'a MAJOR problem for US as we a re trying to turn freeBSD into > an > embedded OS in a 'appliance'.. see www.whistle.com > > once again.... > > > OK here is the picture > > we have several users. > all untrusted. > some must be in a group 'admin' that allows them to write to and delete > anything > in a certain subtree.. EXCEPT a skeleton hierarchy of directories. > > When the system is in administration mode, the REAL admin (root in > single-user) > can add to and change that skeleton hierarchy. All users must be able to > write to their own directories in the hierarchy (and delete). > > So far, if we have a group 'admin', then users in that group > can do things an admin should be able to do if the whole hierarchy > has a group of admin. HOWEVER these are UNTRUSTED admins, and must not > be > able to delete parts of the essential skeleton hierarchy. > > With a NOUNLINK bit we can nail down the hierarchy when in 'real' admin > mode, and the 'untrusted' admins can't smash it. As a side note, > they are running through the netatalk, samba and ftp interfaces and > don't see 'unix' as such. > The trouble with IMMUTIBLE and APPEND is that they don't allow the users > to > create and delete their own files freely within the established > hierarchy. > > The sticky bit is CLOSE, but we run into trouble with more than one user > with > admin privs because they can't un-do each other's damage. > > To your comment.. This is no more 'annoying' than the 'IMMUTIBLE' flag > that presently does even more.. > > personally I think it complements the other flags quite well. > > comments? > I'd prefer not to see a feature like this added to the general code base. If one wishes to add ACL's, why then, add ACL's. Otherwise, solve the problem with the exsisting toolset. Then, again, that's just my preference. Why someone shouldn't change the code for everyone to make it easier to make a particular applicance for some folk is not mine to say. I would say, though, that if you want special tools for a special appliance, then build the special tools, and restrict the general tools. It's an application policy problem, not a system problem. Hrrrumph. Feeping creaturism. -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-current Tue May 27 22:02:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA24143 for current-outgoing; Tue, 27 May 1997 22:02:12 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24138 for ; Tue, 27 May 1997 22:02:10 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.5) id BAA09688; Wed, 28 May 1997 01:01:59 -0400 (EDT) Date: Wed, 28 May 1997 01:01:59 -0400 (EDT) From: Charles Henrich Message-Id: <199705280501.BAA09688@crh.cl.msu.edu> To: julian@whistle.com, freebsd-current@freebsd.org Subject: Re: NEW FEATURE. BSD file NOUNLINK flag. RFC.. will commit unless.... Newsgroups: lists.freebsd.current References: <5mg1m7$chr$1@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 CURRENT #1 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.current you write: >we have several users. all untrusted. some must be in a group 'admin' that >allows them to write to and delete anything in a certain subtree.. EXCEPT a >skeleton hierarchy of directories. [snip details] >To your comment.. This is no more 'annoying' than the 'IMMUTIBLE' flag that >presently does even more.. >personally I think it complements the other flags quite well. >comments? I think this is a wonderful idea, I could have used this myself in a similar project we've been deploying for awhile now.. -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-current Tue May 27 22:26:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA25107 for current-outgoing; Tue, 27 May 1997 22:26:12 -0700 (PDT) Received: from hwcn.org (root@main.hwcn.org [199.212.94.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA25100; Tue, 27 May 1997 22:26:03 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (3199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.5/8.8.5) with ESMTP id BAA09012; Wed, 28 May 1997 01:26:23 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.5/8.8.5) with SMTP id BAA08681; Wed, 28 May 1997 01:26:26 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Wed, 28 May 1997 01:26:26 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca To: "M.R.Murphy" cc: beattie@stt3.com, julian@whistle.com, current@FreeBSD.ORG, julian@FreeBSD.ORG, mckusick@vangogh.cs.berkeley.edu Subject: Re: NEW FEATURE. BSD file NOUNLINK flag. RFC.. will commit unless.... In-Reply-To: <199705280348.UAA03107@meerkat.mole.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 27 May 1997, M.R.Murphy wrote: [NOUNLINK] > > To your comment.. This is no more 'annoying' than the 'IMMUTIBLE' flag > > that presently does even more.. > > > > personally I think it complements the other flags quite well. > > > > comments? > > > [snip] > I would say, though, that if you want special tools for a special > appliance, then build the special tools, and restrict the general > tools. It's an application policy problem, not a system problem. > > Hrrrumph. Feeping creaturism. Hmm... What if they were considered `levels' of IMMUTIBLE. ie. IMMUTIBLE_1, IMMUTIBLE_2, etc. :) From owner-freebsd-current Wed May 28 01:03:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA00894 for current-outgoing; Wed, 28 May 1997 01:03:44 -0700 (PDT) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA00889 for ; Wed, 28 May 1997 01:03:41 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id LAA07094 for current@freebsd.org; Wed, 28 May 1997 11:03:27 +0300 (EET DST) From: mika ruohotie Message-Id: <199705280803.LAA07094@shadows.aeon.net> Subject: old libs in /usr/lib To: current@freebsd.org Date: Wed, 28 May 1997 11:03:27 +0300 (EET DST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk just wondering... (i think my machine crashed in weekend while i attempted to post this, so it never went away) i've been following -current in this machine since may 94. currently there's quite a few old libs in /usr/lib, some are different versions, some are just ontime libs. how likely am i to shoot my leg when nuking them off? there's 165 files (not counting 2 dirs and few symbolic links into that) of which 52! are from 1994, 7 from 1995, 10 from 1996, rest dont have a year listed, so they are newer... i believe i have been able to compile everything i have from /usr/ports up to date whenever there's new version available. for the record, there are lots of other 1994 files in my system too... =) mickey From owner-freebsd-current Wed May 28 01:30:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA01484 for current-outgoing; Wed, 28 May 1997 01:30:56 -0700 (PDT) Received: from firewall.ftf.dk (root@[129.142.64.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA01479 for ; Wed, 28 May 1997 01:30:52 -0700 (PDT) Received: from mail.prosa.dk ([192.168.100.2]) by firewall.ftf.dk (8.7.6/8.7.3) with ESMTP id KAA04118; Wed, 28 May 1997 10:36:38 +0200 Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.5/8.8.5/prosa-1.1) with ESMTP id KAA27739; Wed, 28 May 1997 10:39:53 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.5/8.8.5/prosa-1.1) id KAA20488; Wed, 28 May 1997 10:42:49 +0200 (CEST) Message-ID: <19970528104249.50863@deepo.prosa.dk> Date: Wed, 28 May 1997 10:42:49 +0200 From: Philippe Regnauld To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: RFC2143, IP over SCSI References: <2605.864750301@critter.dk.tfs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: Main Body X-Mailer: Mutt 0.69 In-Reply-To: <2605.864750301@critter.dk.tfs.com>; from Poul-Henning Kamp on Tue, May 27, 1997 at 06:25:01PM +0200 X-Operating-System: FreeBSD 2.2-BETA_A i386 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: > > OK, now we have a standard, who comes up with some code ? Didn't the NetBSD people have this working on PC532 ? -- -- Phil -[ Philippe Regnauld / Systems Administrator / regnauld@prosa.dk ]- -[ Location.: +55.4N +11.3E PGP Key: finger regnauld@hotel.prosa.dk ]- From owner-freebsd-current Wed May 28 03:11:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA04577 for current-outgoing; Wed, 28 May 1997 03:11:19 -0700 (PDT) Received: from nagual.pp.ru (ache.relcom.ru [194.58.229.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA04515; Wed, 28 May 1997 03:09:39 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.8.5/8.8.5) id OAA00693; Wed, 28 May 1997 14:10:14 +0400 (MSD) Date: Wed, 28 May 1997 14:10:11 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: FreeBSD-current , wpaul@freebsd.org, markm@freebsd.org Subject: Duplicate DES code in libc/rpc and secure/lib/des Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I found the same DES code in des/rpc_* files and rpc/des_* files and have two questions: 1) What about export restrictions (rpc/des* affected), is situation changed? 2) Do we really need to duplicate the same code in several places? I think that secure/lib/des/rpc_* files should be removed. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Wed May 28 03:19:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA04810 for current-outgoing; Wed, 28 May 1997 03:19:35 -0700 (PDT) Received: from colin.muc.de (root@colin.muc.de [193.174.4.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA04805 for ; Wed, 28 May 1997 03:19:31 -0700 (PDT) Received: from tavari.muc.de ([193.174.4.22]) by colin.muc.de with SMTP id <86037-1>; Wed, 28 May 1997 12:19:19 +0200 Received: from [192.168.42.51] (aleisha [192.168.42.51]) by tavari.muc.de (8.8.5/8.7.3) with ESMTP id LAA24153; Wed, 28 May 1997 11:09:16 +0200 (CEST) X-Sender: lutz@mail Message-Id: In-Reply-To: <199705280803.LAA07094@shadows.aeon.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Wed, 28 May 1997 11:06:19 +0200 To: mika ruohotie From: Lutz Albers Subject: Re: old libs in /usr/lib Cc: current@FreeBSD.ORG Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA04806 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk mika ruohotie wrote on 28.05.1997 old libs in /usr/lib >just wondering... (i think my machine crashed in weekend while i attempted >to post this, so it never went away) > >i've been following -current in this machine since may 94. currently >there's quite a few old libs in /usr/lib, some are different versions, >some are just ontime libs. > >how likely am i to shoot my leg when nuking them off? Check out /usr/src/tools/LibraryReport. It shows you which lib is used by which executable. ciao lutz -- Lutz Albers, lutz@muc.de, pgp key available by request Do not take life too seriously, you will never get out of it alive. From owner-freebsd-current Wed May 28 03:56:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA06163 for current-outgoing; Wed, 28 May 1997 03:56:27 -0700 (PDT) Received: from gw.softec.sk (gw.softec.sk [194.196.214.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA06054 for ; Wed, 28 May 1997 03:55:36 -0700 (PDT) Received: (from mail@localhost) by gw.softec.sk (8.8.5/8.8.5) id MAA26759 for ; Wed, 28 May 1997 12:55:31 +0200 (CEST) Received: from softec.softec.sk(193.87.236.1) by gw.softec.sk via smap (V2.0) id xma026757; Wed, 28 May 97 12:55:27 +0200 Received: from cleopatra.softec.sk by softec.softec.sk id aa26341; 28 May 97 13:00 CET Received: by cleopatra.softec.sk with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.993.5) id <01BC6B66.83E68490@cleopatra.softec.sk>; Wed, 28 May 1997 12:56:10 +0200 Message-ID: From: "Basti, Zoltan" To: "'freebsd-current@freebsd.org'" Subject: Lowering securelevel with gdb Date: Wed, 28 May 1997 12:56:09 +0200 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.993.5 Encoding: 10 TEXT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A while ago there has been a discussion on freebsd-security about the possibility of lowering securelevel by attaching to init with gdb. Looking at the -current sources it seems to me it is still not fixed. Anyone please tell me if there are any plans to fix it. Thank you, -- Zoltan Basti From owner-freebsd-current Wed May 28 04:51:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA07884 for current-outgoing; Wed, 28 May 1997 04:51:04 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA07877 for ; Wed, 28 May 1997 04:50:59 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA15383 for current@FreeBSD.ORG; Wed, 28 May 1997 13:50:50 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id NAA04163; Wed, 28 May 1997 13:44:48 +0200 (MET DST) Message-ID: <19970528134448.IC09487@uriah.heep.sax.de> Date: Wed, 28 May 1997 13:44:48 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: old libs in /usr/lib References: <199705280803.LAA07094@shadows.aeon.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199705280803.LAA07094@shadows.aeon.net>; from mika ruohotie on May 28, 1997 11:03:27 +0300 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As mika ruohotie wrote: > i've been following -current in this machine since may 94. currently > there's quite a few old libs in /usr/lib, some are different versions, > some are just ontime libs. There's a Tcl script under tools/ to check your executables. (My machine is suffering from the same symptom as yours, the emacs i'm typing this in still announces itself as ``freebsd-1.1.5.1''.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed May 28 05:33:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA09138 for current-outgoing; Wed, 28 May 1997 05:33:37 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA09133 for ; Wed, 28 May 1997 05:33:34 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-2.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA10511 (5.67b/IDA-1.5 for ); Wed, 28 May 1997 14:33:06 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id OAA00847; Wed, 28 May 1997 14:32:23 +0200 (CEST) X-Face: " Date: Wed, 28 May 1997 14:32:23 +0200 From: Stefan Esser To: "Justin T. Gibbs" Cc: Bruce Evans , current@FreeBSD.ORG, gurney_j@resnet.uoregon.edu Subject: Re: cvs commit: src/sys/sys interrupt.h src/sys/kern kern_intr.c References: <19970527200740.32152@x14.mi.uni-koeln.de> <199705271911.NAA04925@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199705271911.NAA04925@pluto.plutotech.com>; from Justin T. Gibbs on Tue, May 27, 1997 at 02:09:00PM -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 27, "Justin T. Gibbs" wrote: > >But the original question was, whether the new shared interrupt > >support might be applicable to ISA drivers, and the consent seems > >to be, that it isn't for the reason you give below: > > I think that we should support it since I can see it being used not > only in the sio driver but for other multi-function devices like > sound cards. Having a separate driver for each function on a card is > much cleaner than a single monolithic driver and since it seems > easy to add the ability to handle this case (set a flag in the descriptor > that says "run me again please"), why not do it? Yes, we could do that. This would require that the drivers keep a pointer to the interrupt descriptors for each "unit". We need to modify struct isa_device to hold the pointer, and have to define another flag bit passed to intr_create() for the shared edge-trggered case. Whenever an ISA handler is linked into the chain, a multiplex handler that tests some bit in the interrupt descriptor for a "needed service" flag. This would not slow down the shared level-triggered case, since thge current simple multiplexer loop could be kept. Regards, STefan From owner-freebsd-current Wed May 28 05:53:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA09774 for current-outgoing; Wed, 28 May 1997 05:53:27 -0700 (PDT) Received: (from wpaul@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA09706; Wed, 28 May 1997 05:50:24 -0700 (PDT) From: Bill Paul Message-Id: <199705281250.FAA09706@hub.freebsd.org> Subject: Re: Duplicate DES code in libc/rpc and secure/lib/des To: ache@nagual.pp.ru (=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=) Date: Wed, 28 May 1997 05:50:24 -0700 (PDT) Cc: current@freebsd.org, markm@freebsd.org In-Reply-To: from "=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=" at May 28, 97 02:10:11 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I found the same DES code in des/rpc_* files and rpc/des_* files and > have two questions: > > 1) What about export restrictions (rpc/des* affected), is situation > changed? There isn't actually any DES crypto code in src/lib/libc/rpc. The way I set it up, the core _des_crypt() function makes an RPC call to the local keyserv(8) process to do all the crypting/decrypting. If you actually have /usr/lib/libdes.so.3.x installed when you start keyserv, then it will dlopen() libdes and use the _des_crypt() routine in there, giving you correct DES operation. If you _don't_ have libdes.so, then keyserv falls back to using RC4 encryption with a 40 bit key. > 2) Do we really need to duplicate the same code in several places? > I think that secure/lib/des/rpc_* files should be removed. Er... by secure/lib/des, I'm assuming you mean secure/lib/libdes, correct? If so, please tell me exactly which files contain duplicated code. Eric Young's libdes has a _des_crypt() routine specially written to accomodate Secure RPC, but it shouldn't contain anything in common with the actual RPC library (other than maybe a header that describes the structure that the RPc code passws to _des_crypt(). -Bill From owner-freebsd-current Wed May 28 06:07:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA10276 for current-outgoing; Wed, 28 May 1997 06:07:13 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA10266; Wed, 28 May 1997 06:06:58 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id OAA20078; Wed, 28 May 1997 14:07:33 +0100 (BST) Date: Wed, 28 May 1997 14:07:33 +0100 (BST) From: Doug Rabson To: Stefan Esser cc: "Justin T. Gibbs" , Bruce Evans , current@freebsd.org, gurney_j@resnet.uoregon.edu Subject: Re: cvs commit: src/sys/sys interrupt.h src/sys/kern kern_intr.c In-Reply-To: <19970528143223.25591@x14.mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 28 May 1997, Stefan Esser wrote: > On May 27, "Justin T. Gibbs" wrote: > > >But the original question was, whether the new shared interrupt > > >support might be applicable to ISA drivers, and the consent seems > > >to be, that it isn't for the reason you give below: > > > > I think that we should support it since I can see it being used not > > only in the sio driver but for other multi-function devices like > > sound cards. Having a separate driver for each function on a card is > > much cleaner than a single monolithic driver and since it seems > > easy to add the ability to handle this case (set a flag in the descriptor > > that says "run me again please"), why not do it? > > Yes, we could do that. This would require that the drivers > keep a pointer to the interrupt descriptors for each "unit". > > We need to modify struct isa_device to hold the pointer, and > have to define another flag bit passed to intr_create() for > the shared edge-trggered case. Whenever an ISA handler is > linked into the chain, a multiplex handler that tests some > bit in the interrupt descriptor for a "needed service" flag. > > This would not slow down the shared level-triggered case, > since thge current simple multiplexer loop could be kept. If we do this, can the interrupt descriptor fiddling happen through a function call? I don't want drivers to know what is inside this structure. In fact I would be happiest if intrec wasn't declared in a public header file at all but was private to kern_intr.c -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 From owner-freebsd-current Wed May 28 06:52:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA11927 for current-outgoing; Wed, 28 May 1997 06:52:03 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA11905 for ; Wed, 28 May 1997 06:51:58 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA16311; Wed, 28 May 1997 15:51:50 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id PAA04341; Wed, 28 May 1997 15:20:41 +0200 (MET DST) Message-ID: <19970528152040.QE64825@uriah.heep.sax.de> Date: Wed, 28 May 1997 15:20:40 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Cc: zbs@softec.sk (Basti, Zoltan) Subject: Re: Lowering securelevel with gdb References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Basti, Zoltan on May 28, 1997 12:56:09 +0200 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Basti, Zoltan wrote: > A while ago there has been a discussion on freebsd-security > about the possibility of lowering securelevel by attaching to init > with gdb. Looking at the -current sources it seems to me it > is still not fixed. I think the entire idea that PID 1 is allowed to lower the securelevel basically defeats the securelevel conception. It should go away. If you run a machine with raised securelevel, it's not undue to require a reboot first in order to perform maintenance tasks -- you gotta sit on the console anyway. This would plug all current and potential future security holes in this respect once and for all. Anybody objecting? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed May 28 09:44:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA20611 for current-outgoing; Wed, 28 May 1997 09:44:00 -0700 (PDT) Received: from lsd.relcom.eu.net (lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA20571; Wed, 28 May 1997 09:42:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lsd.relcom.eu.net (8.8.5/8.8.5) with SMTP id UAA25006; Wed, 28 May 1997 20:42:30 +0400 (MSD) Date: Wed, 28 May 1997 20:42:28 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: Bill Paul cc: current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: Duplicate DES code in libc/rpc and secure/lib/des In-Reply-To: <199705281250.FAA09706@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 28 May 1997, Bill Paul wrote: > > 2) Do we really need to duplicate the same code in several places? > > I think that secure/lib/des/rpc_* files should be removed. > > Er... by secure/lib/des, I'm assuming you mean secure/lib/libdes, > correct? If so, please tell me exactly which files contain duplicated > code. Eric Young's libdes has a _des_crypt() routine specially written > to accomodate Secure RPC, but it shouldn't contain anything in common > with the actual RPC library (other than maybe a header that describes > the structure that the RPc code passws to _des_crypt(). See secure/lib/libdes/{rpc_des.h,rpc_enc.c} It seems they can be safely removed -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Wed May 28 10:14:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA22122 for current-outgoing; Wed, 28 May 1997 10:14:47 -0700 (PDT) Received: (from wpaul@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA22057; Wed, 28 May 1997 10:12:46 -0700 (PDT) From: Bill Paul Message-Id: <199705281712.KAA22057@hub.freebsd.org> Subject: Re: Duplicate DES code in libc/rpc and secure/lib/des To: ache@nagual.pp.ru (=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=) Date: Wed, 28 May 1997 10:12:46 -0700 (PDT) Cc: current@FreeBSD.ORG, markm@FreeBSD.ORG In-Reply-To: from "=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=" at May 28, 97 08:42:28 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Wed, 28 May 1997, Bill Paul wrote: > > > > 2) Do we really need to duplicate the same code in several places? > > > I think that secure/lib/des/rpc_* files should be removed. > > > > Er... by secure/lib/des, I'm assuming you mean secure/lib/libdes, > > correct? If so, please tell me exactly which files contain duplicated > > code. Eric Young's libdes has a _des_crypt() routine specially written > > to accomodate Secure RPC, but it shouldn't contain anything in common > > with the actual RPC library (other than maybe a header that describes > > the structure that the RPc code passws to _des_crypt(). > > See secure/lib/libdes/{rpc_des.h,rpc_enc.c} > It seems they can be safely removed > > -- > Andrey A. Chernov > > http://www.nagual.pp.ru/~ache/ rpc_des.h, maybe. But rpc_enc.c can not be removed: this is the file that contains the __des_crypt() routine, which is a wrapper around thr ECB and CBC encryption routines within the library. Keyserv(8) calls into this routine, so it is necessary. I'll let Mark decide if we need the rpc_des.h header. The RPC library itself doesn't require it, but the libdes library as distributed may need it. -Bill From owner-freebsd-current Wed May 28 12:09:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA27157 for current-outgoing; Wed, 28 May 1997 12:09:36 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.151]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA27152 for ; Wed, 28 May 1997 12:09:32 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.5/8.7.3) id OAA00875; Wed, 28 May 1997 14:00:41 -0500 (CDT) Message-ID: <19970528140041.32391@peeper.my.domain> Date: Wed, 28 May 1997 14:00:41 -0500 From: Tom Jackson To: FreeBSD Current Subject: Cur make kernel fails Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74e Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Last good kernel build was ctm2900. Held off until ctm2903 and got this: cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -g -nostdinc -I- -I. -I../.. -I../../../include -DMD5 -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DFFS -DINET -DKERNEL -include opt_global.h ../../pci/aic7870.c ../../pci/aic7870.c: In function `aic7870_attach': ../../pci/aic7870.c:344: `PCI_COMMAND_MEM_ENABLE' undeclared (first use this function) ../../pci/aic7870.c:344: (Each undeclared identifier is reported only once ../../pci/aic7870.c:344: for each function it appears in.) *** Error code 1 Stop. Is this a known problem? -- Tom Jackson I'm ProChoice->FreeBSD toj@gorilla.net http://www.freebsd.org http://tulsix.utulsa.edu/~tjackson "Out in the Ozone Again" From owner-freebsd-current Wed May 28 12:18:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA27482 for current-outgoing; Wed, 28 May 1997 12:18:45 -0700 (PDT) Received: from pegasus.isr.uc.pt (pegasus.isr.uc.pt [193.136.230.60]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA27461 for ; Wed, 28 May 1997 12:18:22 -0700 (PDT) Received: from localhost by pegasus.isr.uc.pt (5.x/SMI-SVR4) id AA17668; Wed, 28 May 1997 20:11:00 +0100 Date: Wed, 28 May 1997 20:10:59 +0100 (WET DST) From: Paulo Menezes X-Sender: paulo@pegasus To: John-Mark Gurney Cc: Tom Samplonius , current@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <19970527174515.00540@hydrogen.nike.efn.org> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 27 May 1997, John-Mark Gurney wrote: Hi, Thanks for your answers. The problem was simply a misinterpretation of the man pages and it was the conflict caused by using mount points from different filesystems. Now it is solved, thanks for your answers. Paulo > Tom Samplonius scribbled this message on May 27: > > > > On Tue, 27 May 1997, Paulo Menezes wrote: > > > > > > > > Hi all, > > > > > > I am trying to export several filesystems in FBSD NFS Server and it seems > > > rather dificult :( > > > I RTFMed and found nothing that could help me. Is there a problem with > > > mountd or with my english? :) > > > Can anyone tell me what is the problem with the following exports file? > > > > > > ---- > > > /export/home4/users -maproot=root:wheel pegasus orion centauro vega wagner > > > haydn > > > pioneer sirius mozart verdi marvin lapa > > > # > > > /export/ports -maproot=root:wheel marvin > > > /usr/src -maproot=root:wheel marvin lapa > > > # > > > # > > > /export/obj -maproot=root:wheel marvin lapa > > > ---- > > > > You can only have one line in exports for each filesystem that you > > no... you can only have one line per fs per host... and then one line > for the other hosts that you didn't specificly list... > > what I do is list all dirs on a fs on a per host basis... that way it's > easier to track conflicts... then I have blank lines between each fs... > at the very end I list all the "world" exported fs's... > > basicly this is the important part from exports(5): > A host may be specified only once for > each local filesystem on the server and there may be only one default en- > try for each server filesystem that applies to all other hosts. > > this is in the second paragraph of DESCRIPTION... > > hope this helps people... ttyl.. > > -- > John-Mark Gurney Modem/FAX: +1 541 683 6954 > Cu Networking > > Live in Peace, destroy Micro$oft, support free software, run FreeBSD > __/%\__ ... ('-') ... /===============================================================\ | Paulo Menezes | email: paulo@isr.uc.pt | | Net Admin | | | Researcher @ ISR | web: www.isr.uc.pt/~paulo | | Teaching @ DEE-UC | | \===============================================================/ From owner-freebsd-current Wed May 28 13:33:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA01045 for current-outgoing; Wed, 28 May 1997 13:33:26 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA01040 for ; Wed, 28 May 1997 13:33:21 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-45.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA16231 (5.67b/IDA-1.5 for ); Wed, 28 May 1997 22:33:18 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id WAA10835; Wed, 28 May 1997 22:33:18 +0200 (CEST) X-Face: " Date: Wed, 28 May 1997 22:33:17 +0200 From: Stefan Esser To: Tom Jackson Cc: FreeBSD Current Subject: Re: Cur make kernel fails References: <19970528140041.32391@peeper.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <19970528140041.32391@peeper.my.domain>; from Tom Jackson on Wed, May 28, 1997 at 02:00:41PM -0500 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 28, Tom Jackson wrote: > Last good kernel build was ctm2900. Held off until ctm2903 and got this: > > > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -g -nostdinc -I- -I. -I../.. -I../../../include -DMD5 -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DFFS -DINET -DKERNEL -include opt_global.h ../../pci/aic7870.c > ..../../pci/aic7870.c: In function `aic7870_attach': > ..../../pci/aic7870.c:344: `PCI_COMMAND_MEM_ENABLE' undeclared (first use this function) > ..../../pci/aic7870.c:344: (Each undeclared identifier is reported only once > ..../../pci/aic7870.c:344: for each function it appears in.) > *** Error code 1 > > Stop. > > Is this a known problem? Sorry, this was an oversight when I replaced the PCI code, two days ago. The test is not necessary anymore, since the functionality is now included in the pci_map_mem() function. Seems I had not tested compiling that driver with AHC_ALLOW_MEMIO defined, which you apparently have. Please apply the following patch to restore the missing define: Index: /sys/pci/pcireg.h =================================================================== RCS file: /usr/cvs/src/sys/pci/pcireg.h,v retrieving revision 1.16 diff -C2 -r1.16 pcireg.h *** pcireg.h 1997/05/28 11:15:18 1.16 --- pcireg.h 1997/05/28 20:28:54 *************** *** 238,241 **** --- 238,242 ---- #define PCI_COMMAND_STATUS_REG 0x04 #define PCI_COMMAND_IO_ENABLE 0x00000001 + #define PCI_COMMAND_MEM_ENABLE 0x00000002 #define PCI_CLASS_REG 0x08 #define PCI_CLASS_MASK 0xff000000 Thanks for reporting the problem! Regards, STefan From owner-freebsd-current Wed May 28 13:56:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA02330 for current-outgoing; Wed, 28 May 1997 13:56:20 -0700 (PDT) Received: from originat.demon.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA02317 for ; Wed, 28 May 1997 13:56:15 -0700 (PDT) Received: (from paul@localhost) by originat.demon.co.uk (8.8.5/8.6.9) id UAA13340; Mon, 26 May 1997 20:04:30 +0100 (BST) To: current@freebsd.org Subject: ip_divert error From: Paul Richards Date: 26 May 1997 20:04:29 +0100 Message-ID: <87oh9y5a2q.fsf@originat.demon.co.uk> Lines: 26 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ip_divert is still broken: ../../netinet/ip_divert.c: In function `div_bind': ../../netinet/ip_divert.c:314: `imp' undeclared (first use this function) ../../netinet/ip_divert.c:314: (Each undeclared identifier is reported only once ../../netinet/ip_divert.c:314: for each function it appears in.) *** Error code 1 >From a basic perusal of the C code it looks like a simple typo in line 314 where imp should be inp but not knowing anything about the code I'm not going to risk making the change. Umm, the diff of rev 1.9 and 1.10 (the head) is 313a314 > imp = sotoinpcb(so); which looks suspiciously like someone typed in the change without trying to compile the code (tut, tut, you know who you are). -- Dr Paul Richards, Originative Solutions Ltd. Internet: paul@originat.demon.co.uk Phone: 0370 462071 (UK Mobile) From owner-freebsd-current Wed May 28 13:59:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA02558 for current-outgoing; Wed, 28 May 1997 13:59:37 -0700 (PDT) Received: from grackle.grondar.za (grackle.grondar.za [196.7.18.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA02091; Wed, 28 May 1997 13:52:05 -0700 (PDT) Received: from grackle.grondar.za (localhost [127.0.0.1]) by grackle.grondar.za (8.8.5/8.8.4) with ESMTP id WAA05794; Wed, 28 May 1997 22:51:45 +0200 (SAT) Message-Id: <199705282051.WAA05794@grackle.grondar.za> To: Bill Paul cc: ache@nagual.pp.ru (=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=), current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: Duplicate DES code in libc/rpc and secure/lib/des Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 May 1997 22:51:41 +0200 From: Mark Murray Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 28 May 1997 10:12:46 -0700 (PDT) , Bill Paul wrote: > > See secure/lib/libdes/{rpc_des.h,rpc_enc.c} > > It seems they can be safely removed > > > > -- > > Andrey A. Chernov > > > > http://www.nagual.pp.ru/~ache/ > > rpc_des.h, maybe. But rpc_enc.c can not be removed: this is the file that > contains the __des_crypt() routine, which is a wrapper around thr ECB and > CBC encryption routines within the library. Keyserv(8) calls into this > routine, so it is necessary. > > I'll let Mark decide if we need the rpc_des.h header. The RPC library itself > doesn't require it, but the libdes library as distributed may need it. I am disinclined to remove these bits. libdes is distributed as a complete package by EAY, and to go after individual files for each update is a pain. I follow the precedent of larger packages (like gcc), where unneccessary _directories_ are nuked if the need is enough (like for non-i386 architectures) M -- Mark Murray PGP key fingerprint = 80 36 6E 40 83 D6 8A 36 This .sig is umop ap!sdn. BC 06 EA 0E 7A F2 CE CE From owner-freebsd-current Wed May 28 15:52:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA09193 for current-outgoing; Wed, 28 May 1997 15:52:11 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA09184 for ; Wed, 28 May 1997 15:52:07 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wWrZZ-0001me-00; Wed, 28 May 1997 16:52:01 -0600 To: Poul-Henning Kamp Subject: Re: RFC2143, IP over SCSI Cc: current@freebsd.org In-reply-to: Your message of "Tue, 27 May 1997 18:25:01 +0200." <2605.864750301@critter.dk.tfs.com> References: <2605.864750301@critter.dk.tfs.com> Date: Wed, 28 May 1997 16:52:01 -0600 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <2605.864750301@critter.dk.tfs.com> Poul-Henning Kamp writes: : OK, now we have a standard, who comes up with some code ? That would give me something to do with all the 1522's and 1510's that seem to be being dropped in my lap :-) Warner From owner-freebsd-current Wed May 28 22:52:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA26460 for current-outgoing; Wed, 28 May 1997 22:52:30 -0700 (PDT) Received: from xena.mindspring.com (xena.mindspring.com [207.69.142.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA26448 for ; Wed, 28 May 1997 22:52:24 -0700 (PDT) Received: (from rsanders@localhost) by xena.mindspring.com (8.8.5/8.6.12) id BAA27400; Thu, 29 May 1997 01:57:19 -0400 (EDT) From: Robert Sanders To: current@freebsd.org Subject: Re: Boom! :-) References: Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 29 May 1997 01:57:18 -0400 In-Reply-To: Doug Rabson's message of Tue, 27 May 1997 14:12:56 +0100 (BST) Message-ID: Lines: 131 X-Mailer: Gnus v5.4.53/XEmacs 20.2 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Doug Rabson writes: > This is a workaround for the lockstatus panic. A better fix will probably > have to wait until Peter is finished with poll(2). That seems to have helped with the lockstatus panic. Now I have a different problem, detailed below. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01a7d5d stack pointer = 0x10:0xf3f13f10 frame pointer = 0x10:0xf3f13f4c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 4 (update) interrupt mask = trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01a7d5d stack pointer = 0x10:0xf3f13da8 frame pointer = 0x10:0xf3f13de4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 4 (update) interrupt mask = trap number = 12 panic: page fault IdlePTD 23e000 current pcb at 21aa2c panic: page fault #0 boot (howto=260) at ../../kern/kern_shutdown.c:265 265 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:265 #1 0xf0113042 in panic (fmt=0xf01c75ff "page fault") at ../../kern/kern_shutdown.c:393 #2 0xf01c8191 in trap_fatal (frame=0xf3f13d6c) at ../../i386/i386/trap.c:754 #3 0xf01c7c60 in trap_pfault (frame=0xf3f13d6c, usermode=0) at ../../i386/i386/trap.c:661 #4 0xf01c792f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -202293808, tf_esi = -202293816, tf_ebp = -202293788, tf_isp = -202293868, tf_ebx = -260260992, tf_edx = -266275088, tf_ecx = -260261888, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -266699427, tf_cs = 8, tf_eflags = 66118, tf_esp = -261084672, tf_ss = 0}) at ../../i386/i386/trap.c:319 #5 0xf01a7d5d in ffs_sync (mp=0xf0702a00, waitfor=2, cred=0xf04f5a80, p=0xf022ee60) at ../../ufs/ffs/ffs_vfsops.c:839 #6 0xf013408f in sync (p=0xf022ee60, uap=0x0, retval=0x0) at ../../kern/vfs_syscalls.c:480 #7 0xf0112c4d in boot (howto=256) at ../../kern/kern_shutdown.c:203 #8 0xf0113042 in panic (fmt=0xf01c75ff "page fault") at ../../kern/kern_shutdown.c:393 #9 0xf01c8191 in trap_fatal (frame=0xf3f13ed4) at ../../i386/i386/trap.c:754 #10 0xf01c7c60 in trap_pfault (frame=0xf3f13ed4, usermode=0) at ../../i386/i386/trap.c:661 #11 0xf01c792f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -202293448, tf_esi = -202293456, tf_ebp = -202293428, tf_isp = -202293508, tf_ebx = -260260992, tf_edx = 2147483647, tf_ecx = -260261888, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -266699427, tf_cs = 8, tf_eflags = 66118, tf_esp = -261084672, tf_ss = 0}) at ../../i386/i386/trap.c:319 #12 0xf01a7d5d in ffs_sync (mp=0xf0702a00, waitfor=2, cred=0xf04f5a80, p=0xf073ee00) at ../../ufs/ffs/ffs_vfsops.c:839 #13 0xf013408f in sync (p=0xf073ee00, uap=0x0, retval=0x0) at ../../kern/vfs_syscalls.c:480 #14 0xf012ee8f in vfs_update () at ../../kern/vfs_bio.c:1712 #15 0xf0106ede in kproc_start (udata=0xf020ab10) at ../../kern/init_main.c:249 #16 0xf01bf37d in fork_trampoline () #17 0x63616672 in ?? () Cannot access memory at address 0x65746e6d. (kgdb) frame 12 #12 0xf01a7d5d in ffs_sync (mp=0xf0702a00, waitfor=2, cred=0xf04f5a80, p=0xf073ee00) at ../../ufs/ffs/ffs_vfsops.c:839 839 ip = VTOI(vp); 840 if (((ip->i_flag & [where VTOI(vp) is defined as ((struct inode *)(vp)->v_data)] (kgdb) p vp $1 = (struct vnode *) 0xf07cbb80 (kgdb) p *vp $3 = {v_flag = 768, v_usecount = 0, v_writecount = 0, v_holdcnt = 0, v_lastr = 0, v_id = 18797, v_mount = 0xf0702a00, v_op = 0xf0731c00, v_freelist = {tqe_next = 0xf07cba00, tqe_prev = 0xdeadb}, v_mntvnodes = { le_next = 0xf07cb800, le_prev = 0xf07b1e28}, v_cleanblkhd = { lh_first = 0x0}, v_dirtyblkhd = {lh_first = 0x0}, v_numoutput = 0, v_type = VCHR, v_un = {vu_mountedhere = 0xf04f4d50, vu_socket = 0xf04f4d50, vu_specinfo = 0xf04f4d50, vu_fifoinfo = 0xf04f4d50}, v_lease = 0x0, v_lastw = 0, v_cstart = 0, v_lasta = 0, v_clen = 0, v_object = 0x0, v_interlock = {lock_data = 0}, v_vnlock = 0x0, v_tag = VT_UFS, v_data = 0x0, v_cache_src = {lh_first = 0x0}, v_cache_dst = {tqh_first = 0x0, tqh_last = 0xf07cbbf0}, v_dd = 0xf07cbb80, v_ddid = 0} Should this vnode exist without an underlying inode? I know very little about the BSD kernel, so excuse the naive question. This may simply be superstition, but these panics always follow within an update period of me killing pppd to bring down a kernel PPP connection. It does seem significant that v_type = VCHR and the problem seems to coincide with me closing a PPP session on a character device (/dev/cuaa2). Unfortunately, without knowing what inode v_data used to point to, I suppose there's no way to trace the origin on this vnode. Could this be related to this comment in ffs_vget(): /* * If this MALLOC() is performed after the getnewvnode() * it might block, leaving a vnode with a NULL v_data to be * found by ffs_sync() if a sync happens to fire right then, * which will cause a panic because ffs_sync() blindly * dereferences vp->v_data (as well it should). */ -- Robert P.S. kernel and core available on request. From owner-freebsd-current Wed May 28 23:04:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA27001 for current-outgoing; Wed, 28 May 1997 23:04:45 -0700 (PDT) Received: from gw.softec.sk (gw.softec.sk [194.196.214.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA26993 for ; Wed, 28 May 1997 23:04:40 -0700 (PDT) Received: (from mail@localhost) by gw.softec.sk (8.8.5/8.8.5) id IAA04561 for ; Thu, 29 May 1997 08:04:33 +0200 (CEST) Received: from softec.softec.sk(193.87.236.1) by gw.softec.sk via smap (V2.0) id xma004557; Thu, 29 May 97 08:04:28 +0200 Received: from cleopatra.softec.sk by softec.softec.sk id aa02436; 29 May 97 8:09 CET Received: by cleopatra.softec.sk with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.993.5) id <01BC6C07.0351E1C0@cleopatra.softec.sk>; Thu, 29 May 1997 08:05:03 +0200 Message-ID: From: "Basti, Zoltan" To: "'freebsd-current@freebsd.org'" Subject: RE: Lowering securelevel with gdb Date: Thu, 29 May 1997 08:05:02 +0200 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.993.5 Encoding: 18 TEXT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> A while ago there has been a discussion on freebsd-security >> about the possibility of lowering securelevel by attaching to init >> with gdb. Looking at the -current sources it seems to me it >> is still not fixed. > >I think the entire idea that PID 1 is allowed to lower the securelevel >basically defeats the securelevel conception. It should go away. If >you run a machine with raised securelevel, it's not undue to require a >reboot first in order to perform maintenance tasks -- you gotta sit on >the console anyway. This would plug all current and potential >future security holes in this respect once and for all. I agree 100%. A really elegant solution. > > From owner-freebsd-current Wed May 28 23:26:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA28060 for current-outgoing; Wed, 28 May 1997 23:26:46 -0700 (PDT) Received: from forbidden-donut.anet-stl.com (forbidden-donut.anet-stl.com [206.114.203.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA28055 for ; Wed, 28 May 1997 23:26:44 -0700 (PDT) Received: from localhost (doogie@localhost) by forbidden-donut.anet-stl.com (8.8.5/8.8.5) with SMTP id BAA19839 for ; Thu, 29 May 1997 01:24:20 -0500 (CDT) Date: Thu, 29 May 1997 01:24:17 -0500 (CDT) From: Jason Young To: current@freebsd.org Subject: Typo in usr.bin/Makefile In-Reply-To: <199705282051.WAA05794@grackle.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- There is an apparent typo in usr.bin/Makefile line 17, 'logmane' should most likely be 'logname'. Jason Young A-Net Technical Staff -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBM40hFKInE6ybC66VAQEqcgL+KSMGBPAKGtKJCgC64wMkN4uSK1jR7uuZ yn9IrXM6sO2LCwQDt/TlQxLK4xF7CDgduBUaDGUU+VjoN/RNVVpZp43NL2OU8nrW apub8DIr/0sLxNpb0rJyH1oGJM1M926I =4hVl -----END PGP SIGNATURE----- From owner-freebsd-current Wed May 28 23:39:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA28631 for current-outgoing; Wed, 28 May 1997 23:39:38 -0700 (PDT) Received: from forbidden-donut.anet-stl.com (forbidden-donut.anet-stl.com [206.114.203.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA28621 for ; Wed, 28 May 1997 23:39:34 -0700 (PDT) Received: from localhost (doogie@localhost) by forbidden-donut.anet-stl.com (8.8.5/8.8.5) with SMTP id BAA19869 for ; Thu, 29 May 1997 01:37:16 -0500 (CDT) Date: Thu, 29 May 1997 01:37:13 -0500 (CDT) From: Jason Young To: current@freebsd.org Subject: Typo in usr.sbin/Makefile Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Not a good day for makefiles! :) Typo in usr.sbin/Makefile, line 12 - "rpc.ypupdated." needs to have the extraneous trailing period knocked off.. Jason Young A-Net Technical Staff -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBM40kG6InE6ybC66VAQGZ2QL/X0YOvgX/b5nZ1qvNfbYLPGerwSlkrJa8 QxOwPFORFkYrHCTKU4ovObN/WtokWhI2qY1h0IIQEd8CfJGRrGRYefqwB+A1LoEn TSTptelJ5XuSp132be03j0WXwBn4MUd2 =GmPM -----END PGP SIGNATURE----- From owner-freebsd-current Thu May 29 00:46:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA01411 for current-outgoing; Thu, 29 May 1997 00:46:07 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA01393; Thu, 29 May 1997 00:45:08 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id RAA00018; Thu, 29 May 1997 17:26:16 +1000 Date: Thu, 29 May 1997 17:26:16 +1000 From: Bruce Evans Message-Id: <199705290726.RAA00018@godzilla.zeta.org.au> To: mark@grondar.za, wpaul@FreeBSD.ORG Subject: Re: Duplicate DES code in libc/rpc and secure/lib/des Cc: ache@nagual.pp.ru, current@FreeBSD.ORG, markm@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I am disinclined to remove these bits. libdes is distributed as a complete >package by EAY, and to go after individual files for each update is a pain. > >I follow the precedent of larger packages (like gcc), where unneccessary >_directories_ are nuked if the need is enough (like for non-i386 >architectures) Many _files_ are nuked in gcc. Not doing that would have left contrib/gcc almost as bloated as contrib/gdb (where only half of 16MB of unused files has been nuked). Bruce From owner-freebsd-current Thu May 29 05:31:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA10030 for current-outgoing; Thu, 29 May 1997 05:31:42 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA10025 for ; Thu, 29 May 1997 05:31:39 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id WAA11504 for current@freebsd.org; Thu, 29 May 1997 22:28:05 +1000 Date: Thu, 29 May 1997 22:28:05 +1000 From: Bruce Evans Message-Id: <199705291228.WAA11504@godzilla.zeta.org.au> To: current@freebsd.org Subject: disk cache challenged by small block sizes Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Iozone on an ext2fs file system with the default block size of 1K on an (ncr) SCSI Zip disk gave the following poor results: --- iozone: No space left on device IOZONE: Performance Test of Sequential File I/O -- V2.01 (10/21/94) By Bill Norcott Operating System: FreeBSD 2.x -- using fsync() IOZONE: auto-test mode MB reclen bytes/sec written bytes/sec read 1 512 23136 118357 1 1024 30580 90871 1 2048 29635 91929 1 4096 28913 87154 1 8192 28067 44739242 2 512 14360 74358 2 1024 22153 76739 2 2048 21813 88417 2 4096 21510 97435 2 8192 20099 88621 4 512 10040 94586 4 1024 16093 93580 4 2048 15981 3862380 4 4096 15073 3555436 4 8192 17987 147776 8 512 9079 5237764 8 1024 14924 4628197 8 2048 12838 5506368 Error writing block 793 --- This is probably related to slow reads from cd9660. (For cd9660, reads apparently aren't cached, no matter what the block size is, and reads with a block size of 512 are apparently repeated 4 times for each 2K fs block. For ext2fs, the above shows that writes are sometimes cached but another test shows that rereading flushes the cache.) The write error is because of a leak in ext2fs - deleting files doesn't free their space. Apparently the block bitmap is never written to. Iozone on an ext2fs file system with the non-default block size of 4K on a SCSI Zip disk showed caching working correctly: --- IOZONE: Performance Test of Sequential File I/O -- V2.01 (10/21/94) By Bill Norcott Operating System: FreeBSD 2.x -- using fsync() IOZONE: auto-test mode MB reclen bytes/sec written bytes/sec read 1 512 725501 16777216 1 1024 745654 26843545 1 2048 741534 44739242 1 4096 741534 67108864 1 8192 745654 44739242 2 512 831069 16777216 2 1024 833650 26843545 2 2048 833650 38347922 2 4096 823421 53687091 2 8192 833650 53687091 4 512 887389 14128181 4 1024 887389 28256363 4 2048 887389 41297762 4 4096 885925 48806446 4 8192 887389 53687091 8 512 902304 13765920 8 1024 932877 21913098 8 2048 930452 28256363 8 4096 928039 33554432 8 8192 932877 35791394 16 512 907259 926838 16 1024 904203 931663 16 2048 900412 929646 16 4096 902304 929646 16 8192 902683 929646 Completed series of tests --- ufs with a block size of 4K was about the same speed as ext2fs with a block size of 4K. ufs with a block size of 8K was significantly (25%) slower. Bruce From owner-freebsd-current Thu May 29 07:10:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA15046 for current-outgoing; Thu, 29 May 1997 07:10:03 -0700 (PDT) Received: from pat.idt.unit.no (0@pat.idt.unit.no [129.241.103.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA15014 for ; Thu, 29 May 1997 07:10:00 -0700 (PDT) Received: from idt.unit.no (tegge@ikke.idi.ntnu.no [129.241.111.65]) by pat.idt.unit.no (8.8.5/8.8.5) with ESMTP id QAA22937; Thu, 29 May 1997 16:05:50 +0200 (MET DST) Message-Id: <199705291405.QAA22937@pat.idt.unit.no> To: rsanders@mindspring.net Cc: current@FreeBSD.ORG Subject: Re: Boom! :-) In-Reply-To: Your message of "29 May 1997 01:57:18 -0400" References: X-Mailer: Mew version 1.06 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 29 May 1997 16:05:49 +0200 From: Tor Egge Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Doug Rabson writes: > > > This is a workaround for the lockstatus panic. A better fix will probably > > have to wait until Peter is finished with poll(2). > > That seems to have helped with the lockstatus panic. Now I have a > different problem, detailed below. [...] > (kgdb) p *vp > $3 = {v_flag = 768, v_usecount = 0, v_writecount = 0, v_holdcnt = 0, ^^^ ^ VXLOCK | VXWANT, and a `free' vnode [...] > Should this vnode exist without an underlying inode? I know very > little about the BSD kernel, so excuse the naive question. This occurs during cleaning, for a very short interval, where nothing should block. In this case, something blocked. > This may simply be superstition, but these panics always follow within > an update period of me killing pppd to bring down a kernel PPP > connection. It does seem significant that v_type = VCHR and the > problem seems to coincide with me closing a PPP session on a character > device (/dev/cuaa2). Unfortunately, without knowing what inode v_data > used to point to, I suppose there's no way to trace the origin on this > vnode. If you perform a `ps axl' on the kernel/core combination, one process should be marked as being in `vn_loc'. If you look at the kernel stack trace of that process, you'll probably see more useful info (e.g. a deadlock). Try updating to revision 1.40 of src/sys/miscfs/specfs/spec_vnops.c. - Tor Egge From owner-freebsd-current Thu May 29 07:38:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA16504 for current-outgoing; Thu, 29 May 1997 07:38:03 -0700 (PDT) Received: from atlantis.nconnect.net (root@atlantis.nconnect.net [207.227.50.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA16499 for ; Thu, 29 May 1997 07:37:58 -0700 (PDT) Received: from arabian.microxp.com (arabian.microxp.com [207.227.65.13]) by atlantis.nconnect.net (8.8.4/8.7.3) with ESMTP id JAA01129 for ; Thu, 29 May 1997 09:31:59 -0500 (CDT) Message-ID: <338D95DF.2AE692BB@nconnect.net> Date: Thu, 29 May 1997 09:42:39 -0500 From: randyd Reply-To: randyd@nconnect.net Organization: Computer Specialists X-Mailer: Mozilla 4.0b3C (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: logmane?? X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Oops There appears to be a typo in /usr/src/usr.bin/Makefile that breaks 'make world'. Changing 'logmane' to 'logname' in the SUBDIR = block appears to fix this. Ooops.. now it looks like something else is hosed.... /usr/src/usr.sbin/ypc.ypupdated ?? 8-) --- Randall D DuCharme From owner-freebsd-current Thu May 29 08:15:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA18916 for current-outgoing; Thu, 29 May 1997 08:15:01 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA18905 for ; Thu, 29 May 1997 08:14:58 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id IAA03559; Thu, 29 May 1997 08:13:53 -0700 From: Terry Lambert Message-Id: <199705291513.IAA03559@phaeton.artisoft.com> Subject: Re: Boom! :-) To: rsanders@mindspring.net (Robert Sanders) Date: Thu, 29 May 1997 08:13:53 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: from "Robert Sanders" at May 29, 97 01:57:18 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > This is a workaround for the lockstatus panic. A better fix will probably > > have to wait until Peter is finished with poll(2). > > That seems to have helped with the lockstatus panic. Now I have a > different problem, detailed below. > > Fatal trap 12: page fault while in kernel mode [ ... ] > #5 0xf01a7d5d in ffs_sync (mp=0xf0702a00, waitfor=2, cred=0xf04f5a80, > p=0xf022ee60) at ../../ufs/ffs/ffs_vfsops.c:839 > #6 0xf013408f in sync (p=0xf022ee60, uap=0x0, retval=0x0) > at ../../kern/vfs_syscalls.c:480 [ ... ] > Should this vnode exist without an underlying inode? I know very > little about the BSD kernel, so excuse the naive question. Without locking (the patch semi-kills it), a sync can occur on a page for which a mapping has been created but for which the page has not yet completed faulting, or on a dirty page which has been written and discarde, but for which the mapping has not yet been removed. With locking, you can't get this because the vnode's "type" would be deadfs, but you get the other panic because the interface to vnodes is not completely reflexive (it's much like an inverse of the cn_pnbuf situation in namei(), actually). The patch is not correct; the problem is in the VXLOCK handling being an inherently bogus way to do the vnode reclamation, smearing responsibility between the FS insteances and the kernel. It is bad layering, and needs a rewrite (or needs someone's existing rewrite comitted). To fix things, vnode management should go to a per FS type vrele(), and the vnode should be allocated as follows: struct in_core_inode_for_fs_type { struct vnode i_vnode; /* the real vnode*/ ... }; (The per FS vrele() is necessary because the vnode is now an FS specific opaque inode reference). To do this right would require getting rid of "struct fileops" (the abomination before God that it is), and deleting deadfs entirely as being utterly bogus. > This may simply be superstition, but these panics always follow within > an update period of me killing pppd to bring down a kernel PPP > connection. It does seem significant that v_type = VCHR and the > problem seems to coincide with me closing a PPP session on a character > device (/dev/cuaa2). Unfortunately, without knowing what inode v_data > used to point to, I suppose there's no way to trace the origin on this > vnode. Yes. This is the evil of using a common vnode pool and allocating and reusing the things, willy-nilly. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu May 29 08:25:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA19665 for current-outgoing; Thu, 29 May 1997 08:25:26 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA19660 for ; Thu, 29 May 1997 08:25:21 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id QAA00543; Thu, 29 May 1997 16:25:07 +0100 (BST) Date: Thu, 29 May 1997 16:25:07 +0100 (BST) From: Doug Rabson To: Bruce Evans cc: current@freebsd.org Subject: Re: disk cache challenged by small block sizes In-Reply-To: <199705291228.WAA11504@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 29 May 1997, Bruce Evans wrote: > Iozone on an ext2fs file system with the default block size of 1K on an > (ncr) SCSI Zip disk gave the following poor results: > > [snip] > > This is probably related to slow reads from cd9660. (For cd9660, reads > apparently aren't cached, no matter what the block size is, and reads > with a block size of 512 are apparently repeated 4 times for each 2K > fs block. For ext2fs, the above shows that writes are sometimes cached > but another test shows that rereading flushes the cache.) This is caused by my recent changes to vfs_bio to make NFS mmap work properly. I didn't test on a filesystem with small block sizes. This patch should fix it: Index: vfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.116 diff -u -r1.116 vfs_bio.c --- vfs_bio.c 1997/05/19 14:36:36 1.116 +++ vfs_bio.c 1997/05/29 15:22:39 @@ -80,7 +80,8 @@ static void vfs_buf_set_valid(struct buf *bp, vm_ooffset_t foff, vm_offset_t off, vm_offset_t size, vm_page_t m); -static void vfs_page_set_valid(struct buf *bp, vm_offset_t off, vm_page_t m); +static void vfs_page_set_valid(struct buf *bp, vm_ooffset_t off, + int pageno, vm_page_t m); static void vfs_clean_pages(struct buf * bp); static void vfs_setdirty(struct buf *bp); static void vfs_vmio_release(struct buf *bp); @@ -1572,7 +1573,7 @@ } if (bp->b_flags & B_VMIO) { int i, resid; - vm_ooffset_t foff, bfoff; + vm_ooffset_t foff; vm_page_t m; vm_object_t obj; int iosize; @@ -1582,7 +1583,6 @@ foff = (vm_ooffset_t) DEV_BSIZE * bp->b_lblkno; else foff = (vm_ooffset_t) vp->v_mount->mnt_stat.f_iosize * bp->b_lblkno; - bfoff = foff; obj = vp->v_object; if (!obj) { panic("biodone: no object"); @@ -1624,7 +1624,7 @@ * here in the read case. */ if ((bp->b_flags & B_READ) && !bogusflag && resid > 0) { - vfs_page_set_valid(bp, foff - bfoff, m); + vfs_page_set_valid(bp, foff, i, m); } /* @@ -1818,21 +1818,25 @@ /* * Set the valid bits in a page, taking care of the b_validoff, * b_validend fields which NFS uses to optimise small reads. Off is - * the offset of the page within the buf. + * the offset within the file and pageno is the page index within the buf. */ static void -vfs_page_set_valid(struct buf *bp, vm_offset_t off, vm_page_t m) +vfs_page_set_valid(struct buf *bp, vm_ooffset_t off, int pageno, vm_page_t m) { struct vnode *vp = bp->b_vp; vm_offset_t soff, eoff; soff = off; - eoff = min(off + PAGE_SIZE, bp->b_bufsize); + eoff = off + min(PAGE_SIZE, bp->b_bufsize); + vm_page_set_invalid(m, soff, eoff); if (vp->v_tag == VT_NFS) { - soff = max((bp->b_validoff + DEV_BSIZE - 1) & -DEV_BSIZE, soff); - eoff = min(bp->b_validend & -DEV_BSIZE, eoff); + vm_offset_t sv, ev; + sv = off + (bp->b_validoff + DEV_BSIZE - 1) & -DEV_BSIZE + - pageno * PAGE_SIZE; + ev = off + bp->b_validend & -DEV_BSIZE - pageno * PAGE_SIZE; + soff = max(sv, soff); + eoff = min(ev, eoff); } - vm_page_set_invalid(m, 0, PAGE_SIZE); if (eoff > soff) vm_page_set_validclean(m, soff, eoff - soff); } @@ -1851,11 +1855,16 @@ int i; if (bp->b_flags & B_VMIO) { - vm_object_t obj = bp->b_vp->v_object; - vm_offset_t off; + struct vnode *vp = bp->b_vp; + vm_object_t obj = vp->v_object; + vm_ooffset_t foff; + if (vp->v_type == VBLK) + foff = (vm_ooffset_t) DEV_BSIZE * bp->b_lblkno; + else + foff = (vm_ooffset_t) vp->v_mount->mnt_stat.f_iosize * bp->b_lblkno; vfs_setdirty(bp); - for (i = 0, off = 0; i < bp->b_npages; i++, off += PAGE_SIZE) { + for (i = 0; i < bp->b_npages; i++, foff += PAGE_SIZE) { vm_page_t m = bp->b_pages[i]; if ((bp->b_flags & B_CLUSTER) == 0) { @@ -1864,7 +1873,7 @@ } vm_page_protect(m, VM_PROT_NONE); if (clear_modify) - vfs_page_set_valid(bp, off, m); + vfs_page_set_valid(bp, foff, i, m); else if (bp->b_bcount >= PAGE_SIZE) { if (m->valid && (bp->b_flags & B_CACHE) == 0) { bp->b_pages[i] = bogus_page; @@ -1886,12 +1895,18 @@ int i; if (bp->b_flags & B_VMIO) { - vm_offset_t off; + struct vnode *vp = bp->b_vp; + vm_object_t obj = vp->v_object; + vm_ooffset_t foff; - for (i = 0, off = 0; i < bp->b_npages; i++, off += PAGE_SIZE) { + if (vp->v_type == VBLK) + foff = (vm_ooffset_t) DEV_BSIZE * bp->b_lblkno; + else + foff = (vm_ooffset_t) vp->v_mount->mnt_stat.f_iosize * bp->b_lblkno; + for (i = 0; i < bp->b_npages; i++, foff += PAGE_SIZE) { vm_page_t m = bp->b_pages[i]; - vfs_page_set_valid(bp, off, m); + vfs_page_set_valid(bp, foff, i, m); } } } -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 From owner-freebsd-current Thu May 29 08:46:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21379 for current-outgoing; Thu, 29 May 1997 08:46:32 -0700 (PDT) Received: from eddie.cis.uoguelph.ca (eddie.cis.uoguelph.ca [131.104.48.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21371 for ; Thu, 29 May 1997 08:46:30 -0700 (PDT) Received: (from josh@localhost) by eddie.cis.uoguelph.ca (8.8.5/8.8.5) id LAA13881; Thu, 29 May 1997 11:43:49 -0400 (EDT) Message-ID: <19970529114349.40790@eddie.cis.uoguelph.ca> Date: Thu, 29 May 1997 11:43:49 -0400 From: Josh Tiefenbach To: current@freebsd.org Cc: josh@ican.net Subject: vnode_pager_putpages errors Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: Main Body X-Mailer: Mutt 0.69 X-Url: http://eddie.cis.uoguelph.ca/~josh X-Operating-System: FreeBSD 2.2-RELEASE X-PGP-Public-Key: http://eddie.cis.uoguelph.ca/~josh/pgp.html X-PGP-Key-ID: 70189969 X-PGP-Key-Fingerprint: 3F 2A 13 EA AF AD 36 00 DD 3E D1 26 DD 17 14 33 X-Yow: All I can think of is a platter of organic PRUNE CRISPS being trampled by an army of swarthy, Italian LOUNGE SINGERS... Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I've been getting the following messages from the kernel: /kernel: vnode_pager_putpages: I/O error 1 /kernel: vnode_pager_putpages: residual I/O 4096 at 22 They seem to be occuring about twice per minute on average. I searched the archives, and noticed somebody else with a similar problem, which dg commented may be related to the NFS server disallowing requests. The problem is that no NFS activity is taking place. NFS isnt even compiled into the kernel. There 5 2 gig disks comprising /dev/ccd0 however. Kernel is RELENG_2_2 from roughly Sunday evening. Any suggestions? josh -- "I'm genetically a pain in the butt." -- jms From owner-freebsd-current Thu May 29 08:53:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21827 for current-outgoing; Thu, 29 May 1997 08:53:34 -0700 (PDT) Received: from wlk.com (news.wlk.com [192.86.83.250]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21821 for ; Thu, 29 May 1997 08:53:31 -0700 (PDT) Received: from SMTPdaemon by wlk.com (smail3.2) with SMTPL id m0wX7Vu-0009sVC; Thu, 29 May 1997 10:53:18 -0500 (CDT) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id RAA00375; Thu, 29 May 1997 17:06:23 +0200 (CEST) To: Bruce Evans cc: current@freebsd.org From: Poul-Henning Kamp Subject: Re: disk cache challenged by small block sizes In-reply-to: Your message of "Thu, 29 May 1997 22:28:05 +1000." <199705291228.WAA11504@godzilla.zeta.org.au> Date: Thu, 29 May 1997 17:06:22 +0200 Message-ID: <373.864918382@critter.dk.tfs.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >ufs with a block size of 4K was about the same speed as ext2fs with a block >size of 4K. ufs with a block size of 8K was significantly (25%) slower. =========================================================== Uhm, isn't that rather obvious ? The chances of being able to do one DMA into two (physically) consecutive pages are very very slim as far as I can tell, so you will generally get better performance when you do it in page size chunks ? In other words, drivers should be optimized for two back-to-back 4K transactions to different pages, not for 8k transactions to physically contiguous pages. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Thu May 29 09:41:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA25463 for current-outgoing; Thu, 29 May 1997 09:41:47 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA25456 for ; Thu, 29 May 1997 09:41:43 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id CAA20635; Fri, 30 May 1997 02:36:44 +1000 Date: Fri, 30 May 1997 02:36:44 +1000 From: Bruce Evans Message-Id: <199705291636.CAA20635@godzilla.zeta.org.au> To: bde@zeta.org.au, phk@dk.tfs.com Subject: Re: disk cache challenged by small block sizes Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>ufs with a block size of 4K was about the same speed as ext2fs with a block >>size of 4K. ufs with a block size of 8K was significantly (25%) slower. > =========================================================== > >Uhm, isn't that rather obvious ? No :-). >The chances of being able to do one DMA into two (physically) consecutive >pages are very very slim as far as I can tell, so you will generally get >better performance when you do it in page size chunks ? The pages are normally discontiguous, so they are normally done in page- size chunks. A block size of 8K should allow better disk scheduling. Read-ahead is based in the principle of sending even larger requests to the driver. These times for raw i/o show that the OS's cache is doing something right to get even 700K/sec. Speeds in bytes/sec for dd'ing 512 blocks to/from /dev/zero: block size read write 512 24940 24940 1024 49643 49642 2048 98336 98145 4096 191187 191186 8192 321249 321247 16384 518759 519419 32768 730492 732447 65536 894033 896461 Bruce From owner-freebsd-current Thu May 29 14:18:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA09946 for current-outgoing; Thu, 29 May 1997 14:18:35 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA09941 for ; Thu, 29 May 1997 14:18:30 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id HAA29423; Fri, 30 May 1997 07:16:00 +1000 Date: Fri, 30 May 1997 07:16:00 +1000 From: Bruce Evans Message-Id: <199705292116.HAA29423@godzilla.zeta.org.au> To: bde@zeta.org.au, dfr@nlsystems.com Subject: Re: disk cache challenged by small block sizes Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >This is caused by my recent changes to vfs_bio to make NFS mmap work >properly. I didn't test on a filesystem with small block sizes. This >patch should fix it: Thanks. >... > static void >-vfs_page_set_valid(struct buf *bp, vm_offset_t off, vm_page_t m) >+vfs_page_set_valid(struct buf *bp, vm_ooffset_t off, int pageno, vm_page_t m) > { > struct vnode *vp = bp->b_vp; > vm_offset_t soff, eoff; > > soff = off; >- eoff = min(off + PAGE_SIZE, bp->b_bufsize); >+ eoff = off + min(PAGE_SIZE, bp->b_bufsize); >+ vm_page_set_invalid(m, soff, eoff); This sometimes traps. It only works on my test system. I think soff needs to be reduced (mod PAGE_SIZE)? > if (vp->v_tag == VT_NFS) { >- soff = max((bp->b_validoff + DEV_BSIZE - 1) & -DEV_BSIZE, soff); >- eoff = min(bp->b_validend & -DEV_BSIZE, eoff); >+ vm_offset_t sv, ev; >+ sv = off + (bp->b_validoff + DEV_BSIZE - 1) & -DEV_BSIZE >+ - pageno * PAGE_SIZE; >+ ev = off + bp->b_validend & -DEV_BSIZE - pageno * PAGE_SIZE; This has too few parentheses even for me :-). Please use `& ~(BSIZE - 1)' instead of -DEV_BSIZE. The latter assumes 2's complement and may be less idiomatic. Bruce From owner-freebsd-current Thu May 29 16:45:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA15979 for current-outgoing; Thu, 29 May 1997 16:45:02 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA15971 for ; Thu, 29 May 1997 16:45:00 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id QAA00312 for ; Thu, 29 May 1997 16:45:19 -0700 (PDT) To: current@freebsd.org Subject: Temporary outtage at current.freebsd.org / releng22.freebsd.org Date: Thu, 29 May 1997 16:45:18 -0700 Message-ID: <307.864949518@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The snapshot server machine threw a disk yesterday and was just repaired - it will take a little while to get the snapshot mechanism working again (I have to xfer over a new CVS repository, for one thing) so please consider the machine down for the next 48 hours or so. Sorry for the inconvenience! Jordan From owner-freebsd-current Thu May 29 17:00:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA16622 for current-outgoing; Thu, 29 May 1997 17:00:29 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA16611 for ; Thu, 29 May 1997 17:00:23 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/8.7.3) with SMTP id UAA21763 for ; Thu, 29 May 1997 20:00:07 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id UAA07651 for ; Thu, 29 May 1997 20:00:06 -0400 Date: Thu, 29 May 1997 19:59:55 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: FreeBSD current Subject: ctm Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Anyone running ctm have a copy of cvs-cur-3335.gz hanging around? I've just gotten re-connected to the net after being away a few days, I have the updates after this one, but I didn't get this one, and it's not on any mirrors I can find. Thanks. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Thu May 29 19:56:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA24538 for current-outgoing; Thu, 29 May 1997 19:56:16 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA24528; Thu, 29 May 1997 19:56:07 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (8.8.5/8.8.5) with ESMTP id WAA15179; Thu, 29 May 1997 22:56:04 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPN/970116) with ESMTP id WAA22481; Thu, 29 May 1997 22:56:04 -0400 (EDT) To: Chuck Robey cc: FreeBSD current , postmaster@freebsd.org From: "Gary Palmer" Subject: Re: ctm In-reply-to: Your message of "Thu, 29 May 1997 19:59:55 EDT." Date: Thu, 29 May 1997 22:56:03 -0400 Message-ID: <22479.864960963@orion.webspan.net> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chuck Robey wrote in message ID : > Anyone running ctm have a copy of cvs-cur-3335.gz hanging around? I've > just gotten re-connected to the net after being away a few days, I have > the updates after this one, but I didn't get this one, and it's not on > any mirrors I can find. I bet it's a delta thats over 100k in size or something. It seems that our current ctm distribution system can't handle deltas that are of any size :-/ Anyone know why? Is it a message size limit for sendmail on hub.freebsd.org ? Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Thu May 29 20:16:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25349 for current-outgoing; Thu, 29 May 1997 20:16:32 -0700 (PDT) Received: (from jmb@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25341; Thu, 29 May 1997 20:16:18 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199705300316.UAA25341@hub.freebsd.org> Subject: Re: ctm To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Thu, 29 May 1997 20:16:18 -0700 (PDT) Cc: chuckr@glue.umd.edu, freebsd-current@freefall.FreeBSD.org, postmaster@FreeBSD.ORG In-Reply-To: <22479.864960963@orion.webspan.net> from "Gary Palmer" at May 29, 97 10:56:03 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Gary Palmer wrote: > > Chuck Robey wrote in message ID > : > > Anyone running ctm have a copy of cvs-cur-3335.gz hanging around? I've > > just gotten re-connected to the net after being away a few days, I have > > the updates after this one, but I didn't get this one, and it's not on > > any mirrors I can find. > > I bet it's a delta thats over 100k in size or something. It seems that > our current ctm distribution system can't handle deltas that are of > any size :-/ Anyone know why? Is it a message size limit for sendmail > on hub.freebsd.org ? the majordomo list will accept up to 4MB (ctm-cvs-cur*config). anyone know hte size of this delta? how about its message-id header? jmb From owner-freebsd-current Thu May 29 20:36:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25915 for current-outgoing; Thu, 29 May 1997 20:36:36 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25908; Thu, 29 May 1997 20:36:28 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id UAA10466; Thu, 29 May 1997 20:36:47 -0700 (PDT) To: "Gary Palmer" cc: Chuck Robey , FreeBSD current , postmaster@FreeBSD.ORG Subject: Re: ctm In-reply-to: Your message of "Thu, 29 May 1997 22:56:03 EDT." <22479.864960963@orion.webspan.net> Date: Thu, 29 May 1997 20:36:46 -0700 Message-ID: <10463.864963406@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I bet it's a delta thats over 100k in size or something. It seems that > our current ctm distribution system can't handle deltas that are of > any size :-/ Anyone know why? Is it a message size limit for sendmail > on hub.freebsd.org ? So says Mr. He-could-have-just-as-easily-checked-himself. :-) It's commented out: # maximum message size #O MaxMessageSize=1000000 Which is not to say that some other site which relays the CTM files (rkw's?) doesn't have it turned on. Jordan From owner-freebsd-current Thu May 29 20:52:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA26721 for current-outgoing; Thu, 29 May 1997 20:52:48 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA26715; Thu, 29 May 1997 20:52:41 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/8.7.3) with SMTP id XAA28055; Thu, 29 May 1997 23:52:39 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id XAA11956; Thu, 29 May 1997 23:52:37 -0400 Date: Thu, 29 May 1997 23:52:26 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Gary Palmer cc: FreeBSD current , postmaster@freebsd.org Subject: Re: ctm In-Reply-To: <22479.864960963@orion.webspan.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 29 May 1997, Gary Palmer wrote: > Chuck Robey wrote in message ID > : > > Anyone running ctm have a copy of cvs-cur-3335.gz hanging around? I've > > just gotten re-connected to the net after being away a few days, I have > > the updates after this one, but I didn't get this one, and it's not on > > any mirrors I can find. > > I bet it's a delta thats over 100k in size or something. It seems that > our current ctm distribution system can't handle deltas that are of > any size :-/ Anyone know why? Is it a message size limit for sendmail > on hub.freebsd.org ? That's not the trouble, deltas over that size (which have occurred just before _and_ just after the missing 3335 delta) have been reliably cut into pieces and delivered to me just fine. Still missing cvs-cur.3335. No one's got it? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Thu May 29 21:33:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA28168 for current-outgoing; Thu, 29 May 1997 21:33:07 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA28163 for ; Thu, 29 May 1997 21:33:02 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id GAA29825 for ; Fri, 30 May 1997 06:32:15 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id GAA22059 for freebsd-current@FreeBSD.ORG; Fri, 30 May 1997 06:31:50 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id VAA03239; Thu, 29 May 1997 21:26:36 +0200 (CEST) Message-ID: <19970529212635.11253@keltia.freenix.fr> Date: Thu, 29 May 1997 21:26:35 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Weird behaviour from the Linux emulator References: <19970525193558.22470@keltia.freenix.fr> <199705270615.PAA28391@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 In-Reply-To: <199705270615.PAA28391@genesis.atrad.adelaide.edu.au>; from Michael Smith on Tue, May 27, 1997 at 03:45:41PM +0930 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3332 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Michael Smith: > Yeah; there's not much that can be done about that though. That's what I feared. That makes some applications (like the backup software I mentionned) unusable though. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #10: Fri May 23 22:47:39 CEST 1997 From owner-freebsd-current Thu May 29 22:04:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29135 for current-outgoing; Thu, 29 May 1997 22:04:30 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29128; Thu, 29 May 1997 22:04:27 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (8.8.5/8.8.5) with ESMTP id BAA01232; Fri, 30 May 1997 01:04:25 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPN/970116) with ESMTP id BAA02028; Fri, 30 May 1997 01:04:25 -0400 (EDT) To: "Jordan K. Hubbard" cc: FreeBSD current , postmaster@FreeBSD.ORG From: "Gary Palmer" Subject: Re: ctm In-reply-to: Your message of "Thu, 29 May 1997 20:36:46 PDT." <10463.864963406@time.cdrom.com> Date: Fri, 30 May 1997 01:04:25 -0400 Message-ID: <2026.864968665@orion.webspan.net> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Jordan K. Hubbard" wrote in message ID <10463.864963406@time.cdrom.com>: > So says Mr. He-could-have-just-as-easily-checked-himself. :-) > # maximum message size > #O MaxMessageSize=1000000 I also know of the possibility of limiting it selectively in Majordomo, and don't know where THAT is specified tho :-) (Or didn't until jmb's reply) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Thu May 29 22:11:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29470 for current-outgoing; Thu, 29 May 1997 22:11:19 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29463 for ; Thu, 29 May 1997 22:11:16 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/8.7.3) with SMTP id BAA06740 for ; Fri, 30 May 1997 01:11:14 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id BAA16872 for ; Fri, 30 May 1997 01:11:12 -0400 Date: Fri, 30 May 1997 01:11:02 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: FreeBSD current Subject: ctm again Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I can't find Richard Wackerbarth's domain (I bet he's having some connection problems) but I did notice, while I was looking around at all the FreeBSD mirrors for the cvs-cur.3335 file, that the 3339 file is missing also. I got that file, I put it into my home dir on hub, and I would appreciate someone with root privs to stick it into freebsd/CTM/cvs-cur so everyone else can have it too. I think then the mirrors would pick it up. If I had the connectivity, I'd do the ctm generation too, but I'm ppp connected. Until I can find that 3335, I'm knocked off current, I guess. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Thu May 29 23:19:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA01299 for current-outgoing; Thu, 29 May 1997 23:19:50 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA01285 for ; Thu, 29 May 1997 23:18:08 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.5/8.8.5) id IAA17645; Fri, 30 May 1997 08:17:20 +0200 (SAT) From: John Hay Message-Id: <199705300617.IAA17645@zibbi.mikom.csir.co.za> Subject: Re: ctm again In-Reply-To: from Chuck Robey at "May 30, 97 01:11:02 am" To: chuckr@glue.umd.edu (Chuck Robey) Date: Fri, 30 May 1997 08:17:19 +0200 (SAT) Cc: freebsd-current@freefall.FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > If I had the connectivity, I'd do the ctm generation too, but I'm ppp > connected. Until I can find that 3335, I'm knocked off current, I guess. > It is available from ftp://ftp.uni-trier.de/pub/unix/systems/BSD/FreeBSD/CTM/. BTW. It seems that the ctm generation for cvs-cur is dead. The last one I have received is 3340 and that was almost 2 days ago. John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-current Thu May 29 23:24:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA01467 for current-outgoing; Thu, 29 May 1997 23:24:14 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA01461; Thu, 29 May 1997 23:24:08 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.5/8.7.3) id IAA03466; Fri, 30 May 1997 08:24:28 +0200 (MEST) From: Søren Schmidt Message-Id: <199705300624.IAA03466@sos.freebsd.dk> Subject: Re: ctm In-Reply-To: from Chuck Robey at "May 29, 97 11:52:26 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Fri, 30 May 1997 08:24:28 +0200 (MEST) Cc: gpalmer@FreeBSD.ORG, freebsd-current@freefall.FreeBSD.org, postmaster@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Chuck Robey who wrote: > On Thu, 29 May 1997, Gary Palmer wrote: > > > Chuck Robey wrote in message ID > > : > > > Anyone running ctm have a copy of cvs-cur-3335.gz hanging around? I've > > > just gotten re-connected to the net after being away a few days, I have > > > the updates after this one, but I didn't get this one, and it's not on > > > any mirrors I can find. > > > > I bet it's a delta thats over 100k in size or something. It seems that > > our current ctm distribution system can't handle deltas that are of > > any size :-/ Anyone know why? Is it a message size limit for sendmail > > on hub.freebsd.org ? > > That's not the trouble, deltas over that size (which have occurred just > before _and_ just after the missing 3335 delta) have been reliably cut > into pieces and delivered to me just fine. > > Still missing cvs-cur.3335. No one's got it? I've got it. But your problems wont end there :( It seems the CTM generation has halted, there hasn't been a delta for 48 hours now. The machine that normally carries the masters shrimp.dataplex.net has vanished from the net, so has Mr Wackerbart it seems (or his mailaacount on dataplex.net has been closed) as he doesn't respond to mail (yet). I think we should try find CTM a new home, it has been much to unreliable lately. What does it take ?? a few gigs of disk and a machine with resonable connectivity ?? (Yeah I've tried cvsup yesterday, but it dies because the line to the US (and the US internal network) is overloaded and looses packets) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Thu May 29 23:34:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA01680 for current-outgoing; Thu, 29 May 1997 23:34:14 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA01616 for ; Thu, 29 May 1997 23:32:46 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.5/8.8.5) id QAA17957; Fri, 30 May 1997 16:31:49 +1000 Received: from localhost.devetir.qld.gov.au by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with SMTP id QAA22297; Fri, 30 May 1997 16:00:07 +1000 (EST) Message-Id: <199705300600.QAA22297@ogre.dtir.qld.gov.au> To: freebsd-current@freebsd.org cc: Richard Wackerbarth Subject: Re: ctm References: In-Reply-To: from Chuck Robey at "Fri, 30 May 1997 03:52:26 +0000" Date: Fri, 30 May 1997 16:00:06 +1000 From: Stephen McKay Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Friday, 30th May 1997, Chuck Robey wrote: >On Thu, 29 May 1997, Gary Palmer wrote: > >> Chuck Robey wrote in message ID >> : >> > Anyone running ctm have a copy of cvs-cur-3335.gz hanging around? >> >> I bet it's a delta thats over 100k in size or something... > >That's not the trouble, deltas over that size (which have occurred just >before _and_ just after the missing 3335 delta) have been reliably cut >into pieces and delivered to me just fine. Yes, large deltas are just chopped into pieces. Individual messages should currently be 100K max, though it can be set as low as you like. 3335 is 105465 bytes, and should have arrived in 2 pieces. >Still missing cvs-cur.3335. No one's got it? A couple days ago I fetched a copy from ftp.uni-trier.de in: /pub/unix/systems/BSD/FreeBSD/CTM/cvs-cur/cvs-cur.3335.gz Also, I've not received any deltas since #3340 on 1997-05-29 00:34 (local time), but I haven't got around to checking the archive. What is the real problem here? It's not a delta generation failure because uni-trier always has them. Is it a mail problem at the point of generation, or a problem with hub.freebsd.org? Does this mean I'm losing -current and -hackers mail too? I'll help anyone as much as I can from here. Probably all I can do is provide headers that show where they go to get here, and how long they took to do so. Stephen. From owner-freebsd-current Thu May 29 23:52:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02531 for current-outgoing; Thu, 29 May 1997 23:52:52 -0700 (PDT) Received: from bourbon.sfc.wide.ad.jp (bourbon.sfc.wide.ad.jp [203.178.139.171]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA02525 for ; Thu, 29 May 1997 23:52:49 -0700 (PDT) Received: from bourbon.sfc.wide.ad.jp (localhost [127.0.0.1]) by bourbon.sfc.wide.ad.jp (8.8.5/3.5Wpl104/21/97) with ESMTP id PAA00798; Fri, 30 May 1997 15:52:38 +0900 (JST) Message-Id: <199705300652.PAA00798@bourbon.sfc.wide.ad.jp> To: freebsd-current@freebsd.org Cc: max@wide.ad.jp Subject: Some trouble with SCSI HD From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 30 May 1997 15:52:37 +0900 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm running -current from about a week ago. When I run cvsup to get some files from cvsupd running on localhost, the system freezes. Many times, the system just goes quiet and no input from console is accepted. A few other other times, it goes half dead, I mean, I can traceroute or ping to the system from another machine but nothing else can be done. When I run cvsup and get files from remote system, this doesn't happen. My SCSI adapter and the disk are: ahc0 rev 0 int a irq 11 on pci0:12:0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 ahc0:A:0: refuses WIDE negotiation. Using 8bit transfers sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 2063MB (4226725 512 byte sectors) Does anyone have any idea what is causing this? Cheers, Max From owner-freebsd-current Fri May 30 00:26:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA04155 for current-outgoing; Fri, 30 May 1997 00:26:01 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA04144 for ; Fri, 30 May 1997 00:25:55 -0700 (PDT) Resent-From: j@uriah.heep.sax.de Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA23312 for freebsd-current@FreeBSD.org; Fri, 30 May 1997 09:25:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA07391 for freebsd-current@FreeBSD.org; Fri, 30 May 1997 09:13:33 +0200 (MET DST) Resent-Message-Id: <199705300713.JAA07391@uriah.heep.sax.de> Received: (from uucp@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) with UUCP id GAA07022 for joerg_wunsch@uriah.heep.sax.de; Fri, 30 May 1997 06:20:52 +0200 (MET DST) Received: from bsd.fs.bauing.th-darmstadt.de (bsd.fs.bauing.th-darmstadt.de [130.83.63.241]) by sax.sax.de (8.6.12/8.6.12-s1) with ESMTP id DAA20826 for ; Fri, 30 May 1997 03:38:46 +0200 Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by bsd.fs.bauing.th-darmstadt.de (8.8.5/8.8.5) with ESMTP id DAA16668; Fri, 30 May 1997 03:38:42 +0200 (MET DST) Received: from mgate02.so-net.or.jp (mgate02.so-net.or.jp [210.132.247.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA21860 for ; Thu, 29 May 1997 18:38:11 -0700 (PDT) Received: from mail.ja2.so-net.or.jp (mail.ja2.so-net.or.jp [202.238.95.38]) by mgate02.so-net.or.jp (8.7.5/3.4W397011716) with ESMTP id KAA17202 for ; Fri, 30 May 1997 10:38:05 +0900 (JST) Received: from Bird (pppbc20.pppp.ap.so-net.or.jp [210.132.188.32]) by mail.ja2.so-net.or.jp (8.7.5/3.4W397052221) with ESMTP id KAA19864 for ; Fri, 30 May 1997 10:38:03 +0900 Message-Id: <199705300138.KAA19864@mail.ja2.so-net.or.jp> From: "=?ISO-2022-JP?B?GyRCR2s4NhsoSiAbJEIxUUAkGyhK?=" To: Subject: FreeBSD 3.0 current source tree bug report. Date: Fri, 30 May 1997 10:38:54 +0900 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1157 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Resent-Date: Fri, 30 May 1997 09:13:33 +0200 Resent-To: freebsd-current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk *** Fri 30 May 7:00 JST 1997 *** I got FreeBSD-3.0 current source tree and 'make world' in directry /usr/src but stopped 'make' command with some errors bellow. /usr/src/usr.bin/Makefile line 17:logmane -> logname /usr/src/share/mk/bsd.lib.mk line 243:endig -> endif /usr/src/share/mk/bsd.lib.mk line 139:POBJS+= ${OBJS:.o.po} -> POBJS+= ${OBJS:R:S/$/.po/g} /usr/src/share/mk/bsd.lib.mk line 152:SOBJS+= ${OBJS:.o.so} -> SOBJS+= ${OBJS:R:S/$/.so/g} /usr/src/lib/libc/db/recno/rec_utils.c line 23:PURPUSE^H -> PURPUSE /usr/src/lib/libc/db/recno/rec_utils.c line 34:defaned -> defined /usr/src/lib/libc/db/recno/rec_utils.c line 100:( -> *** erase *** /usr/src/lib/libc/gen/exec.c line 75:s -> { /usr/src/lib/libc/gen/exec.c line 165:argv-; -> argv); -------------------------------------------------------------- Hideyo Hagiwara vogue@ja2.so-net.or.jp From owner-freebsd-current Fri May 30 02:06:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA07306 for current-outgoing; Fri, 30 May 1997 02:06:43 -0700 (PDT) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA07299 for ; Fri, 30 May 1997 02:06:29 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id MAA24629 for current@freebsd.org; Fri, 30 May 1997 12:05:45 +0300 (EET DST) From: mika ruohotie Message-Id: <199705300905.MAA24629@shadows.aeon.net> Subject: Re: old libs in /usr/lib In-Reply-To: <19970528134448.IC09487@uriah.heep.sax.de> from J Wunsch at "May 28, 97 01:44:48 pm" To: current@freebsd.org Date: Fri, 30 May 1997 12:05:45 +0300 (EET DST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > there's quite a few old libs in /usr/lib, some are different versions, > There's a Tcl script under tools/ to check your executables. so i'm safe if i nuke whatever it reports 'stale'? > (My machine is suffering from the same symptom as yours, the emacs i'm > typing this in still announces itself as ``freebsd-1.1.5.1''.) hehe. i think i started with 2.0-current, but from the machine i started with, i only have left the floppy drive (i never use it) and the monitor, and i'm about to get rid of that horrible 14" soon. ofcourse, the base installation, even thoug cpioed to another drive, it still "original" from many parts. it's not too long ago i went to /etc/sysconfig, and recently to /etc/rc.conf reminds me, my ssh reports: May 30 12:02:35 shadows sshd[24622]: login_getclass: unknown class '00^B' something is wrong, with /etc/login.conf or something? uh, like what do i have to do to it? > cheers, J"org mickey From owner-freebsd-current Fri May 30 02:09:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA07392 for current-outgoing; Fri, 30 May 1997 02:09:30 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA07387 for ; Fri, 30 May 1997 02:09:27 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id KAA03622; Fri, 30 May 1997 10:08:50 +0100 (BST) Date: Fri, 30 May 1997 10:08:50 +0100 (BST) From: Doug Rabson To: Bruce Evans cc: current@freebsd.org Subject: Re: disk cache challenged by small block sizes In-Reply-To: <199705292116.HAA29423@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 30 May 1997, Bruce Evans wrote: > >This is caused by my recent changes to vfs_bio to make NFS mmap work > >properly. I didn't test on a filesystem with small block sizes. This > >patch should fix it: > > Thanks. > > This sometimes traps. It only works on my test system. I think soff needs > to be reduced (mod PAGE_SIZE)? This version fixes a bug (passing an offset instead of a size to vm_page_set_invalid) which was probably the cause of the trap, should work properly for large files (I was using the wrong offset type) and possibly has a more acceptable style(9). Index: vfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.116 diff -u -r1.116 vfs_bio.c --- vfs_bio.c 1997/05/19 14:36:36 1.116 +++ vfs_bio.c 1997/05/30 08:53:16 @@ -80,7 +80,8 @@ static void vfs_buf_set_valid(struct buf *bp, vm_ooffset_t foff, vm_offset_t off, vm_offset_t size, vm_page_t m); -static void vfs_page_set_valid(struct buf *bp, vm_offset_t off, vm_page_t m); +static void vfs_page_set_valid(struct buf *bp, vm_ooffset_t off, + int pageno, vm_page_t m); static void vfs_clean_pages(struct buf * bp); static void vfs_setdirty(struct buf *bp); static void vfs_vmio_release(struct buf *bp); @@ -1572,7 +1573,7 @@ } if (bp->b_flags & B_VMIO) { int i, resid; - vm_ooffset_t foff, bfoff; + vm_ooffset_t foff; vm_page_t m; vm_object_t obj; int iosize; @@ -1582,7 +1583,6 @@ foff = (vm_ooffset_t) DEV_BSIZE * bp->b_lblkno; else foff = (vm_ooffset_t) vp->v_mount->mnt_stat.f_iosize * bp->b_lblkno; - bfoff = foff; obj = vp->v_object; if (!obj) { panic("biodone: no object"); @@ -1624,7 +1624,7 @@ * here in the read case. */ if ((bp->b_flags & B_READ) && !bogusflag && resid > 0) { - vfs_page_set_valid(bp, foff - bfoff, m); + vfs_page_set_valid(bp, foff, i, m); } /* @@ -1818,23 +1818,31 @@ /* * Set the valid bits in a page, taking care of the b_validoff, * b_validend fields which NFS uses to optimise small reads. Off is - * the offset of the page within the buf. + * the offset within the file and pageno is the page index within the buf. */ static void -vfs_page_set_valid(struct buf *bp, vm_offset_t off, vm_page_t m) +vfs_page_set_valid(struct buf *bp, vm_ooffset_t off, int pageno, vm_page_t m) { struct vnode *vp = bp->b_vp; - vm_offset_t soff, eoff; + vm_ooffset_t soff, eoff; soff = off; - eoff = min(off + PAGE_SIZE, bp->b_bufsize); + eoff = off + min(PAGE_SIZE, bp->b_bufsize); + vm_page_set_invalid(m, + (vm_offset_t) (soff & PAGE_MASK), + (vm_offset_t) (eoff - soff)); if (vp->v_tag == VT_NFS) { - soff = max((bp->b_validoff + DEV_BSIZE - 1) & -DEV_BSIZE, soff); - eoff = min(bp->b_validend & -DEV_BSIZE, eoff); + vm_ooffset_t sv, ev; + off = off - pageno * PAGE_SIZE; + sv = off + ((bp->b_validoff + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1)); + ev = off + (bp->b_validend & ~(DEV_BSIZE - 1)); + soff = max(sv, soff); + eoff = min(ev, eoff); } - vm_page_set_invalid(m, 0, PAGE_SIZE); if (eoff > soff) - vm_page_set_validclean(m, soff, eoff - soff); + vm_page_set_validclean(m, + (vm_offset_t) (soff & PAGE_MASK), + (vm_offset_t) (eoff - soff)); } /* @@ -1851,11 +1859,16 @@ int i; if (bp->b_flags & B_VMIO) { - vm_object_t obj = bp->b_vp->v_object; - vm_offset_t off; + struct vnode *vp = bp->b_vp; + vm_object_t obj = vp->v_object; + vm_ooffset_t foff; + if (vp->v_type == VBLK) + foff = (vm_ooffset_t) DEV_BSIZE * bp->b_lblkno; + else + foff = (vm_ooffset_t) vp->v_mount->mnt_stat.f_iosize * bp->b_lblkno; vfs_setdirty(bp); - for (i = 0, off = 0; i < bp->b_npages; i++, off += PAGE_SIZE) { + for (i = 0; i < bp->b_npages; i++, foff += PAGE_SIZE) { vm_page_t m = bp->b_pages[i]; if ((bp->b_flags & B_CLUSTER) == 0) { @@ -1864,7 +1877,7 @@ } vm_page_protect(m, VM_PROT_NONE); if (clear_modify) - vfs_page_set_valid(bp, off, m); + vfs_page_set_valid(bp, foff, i, m); else if (bp->b_bcount >= PAGE_SIZE) { if (m->valid && (bp->b_flags & B_CACHE) == 0) { bp->b_pages[i] = bogus_page; @@ -1886,12 +1899,18 @@ int i; if (bp->b_flags & B_VMIO) { - vm_offset_t off; + struct vnode *vp = bp->b_vp; + vm_object_t obj = vp->v_object; + vm_ooffset_t foff; - for (i = 0, off = 0; i < bp->b_npages; i++, off += PAGE_SIZE) { + if (vp->v_type == VBLK) + foff = (vm_ooffset_t) DEV_BSIZE * bp->b_lblkno; + else + foff = (vm_ooffset_t) vp->v_mount->mnt_stat.f_iosize * bp->b_lblkno; + for (i = 0; i < bp->b_npages; i++, foff += PAGE_SIZE) { vm_page_t m = bp->b_pages[i]; - vfs_page_set_valid(bp, off, m); + vfs_page_set_valid(bp, foff, i, m); } } } -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 From owner-freebsd-current Fri May 30 03:43:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA10445 for current-outgoing; Fri, 30 May 1997 03:43:04 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA10437 for ; Fri, 30 May 1997 03:42:56 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-40.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA12730 (5.67b/IDA-1.5 for ); Fri, 30 May 1997 12:42:29 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id MAA03325; Fri, 30 May 1997 12:42:22 +0200 (CEST) X-Face: " Date: Fri, 30 May 1997 12:42:20 +0200 From: Stefan Esser To: Poul-Henning Kamp Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: disk cache challenged by small block sizes References: <199705291228.WAA11504@godzilla.zeta.org.au> <373.864918382@critter.dk.tfs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <373.864918382@critter.dk.tfs.com>; from Poul-Henning Kamp on Thu, May 29, 1997 at 05:06:22PM +0200 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 29, Poul-Henning Kamp wrote: > > >ufs with a block size of 4K was about the same speed as ext2fs with a block > >size of 4K. ufs with a block size of 8K was significantly (25%) slower. > =========================================================== > > Uhm, isn't that rather obvious ? Ahemm ??? > The chances of being able to do one DMA into two (physically) consecutive > pages are very very slim as far as I can tell, so you will generally get > better performance when you do it in page size chunks ? Sure! > In other words, drivers should be optimized for two back-to-back 4K > transactions to different pages, not for 8k transactions to physically > contiguous pages. Well, sorry, hmmm, ... When did you write a bus-master SCSI driver, last time ? ;-) For a "n" page transfer, n+1 scatter/gather table entries are provided. This allows for the transfer to start at an arbitrary byte offset into the first page, and covers n-1 full pages, and possibly a final partial one ... Regards, STefan From owner-freebsd-current Fri May 30 05:48:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA14087 for current-outgoing; Fri, 30 May 1997 05:48:10 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA14082 for ; Fri, 30 May 1997 05:48:07 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id WAA07183; Fri, 30 May 1997 22:42:18 +1000 Date: Fri, 30 May 1997 22:42:18 +1000 From: Bruce Evans Message-Id: <199705301242.WAA07183@godzilla.zeta.org.au> To: bde@zeta.org.au, dfr@nlsystems.com Subject: Re: disk cache challenged by small block sizes Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >This version fixes a bug (passing an offset instead of a size to >vm_page_set_invalid) which was probably the cause of the trap, should work >properly for large files (I was using the wrong offset type) and possibly >has a more acceptable style(9). It seems to fix all the speed problems (except ufs is still slower with a larger fs blocksize) and the block leak in ex2tfs. Bruce From owner-freebsd-current Fri May 30 05:56:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA14448 for current-outgoing; Fri, 30 May 1997 05:56:47 -0700 (PDT) Received: from sliphost37.uni-trier.de (root@sliphost37.uni-trier.de [136.199.240.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA14429; Fri, 30 May 1997 05:56:29 -0700 (PDT) Received: (from blank@localhost) by sliphost37.uni-trier.de (8.8.5/8.8.5) id OAA04727; Fri, 30 May 1997 14:53:43 +0200 (CEST) Date: Fri, 30 May 1997 14:53:43 +0200 (CEST) Message-Id: <199705301253.OAA04727@sliphost37.uni-trier.de> From: Sascha Blank To: =?ISO-8859-1?Q?S=F8ren?= Schmidt Cc: chuckr@glue.umd.edu (Chuck Robey), gpalmer@FreeBSD.ORG, freebsd-current@freefall.FreeBSD.org, postmaster@FreeBSD.ORG Subject: Re: ctm In-Reply-To: <199705300624.IAA03466@sos.freebsd.dk> References: <199705300624.IAA03466@sos.freebsd.dk> X-Mailer: VM 6.31 under 19.15p4 XEmacs Lucid Reply-To: Sascha Blank X-PGP-Fingerprint: 26 FD 71 B5 48 12 42 91 10 1C 4F 74 70 48 6F 89 Comments: Hyperbole mail buttons accepted, v04.023. Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id FAA14439 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> "Søren" == Søren Schmidt writes: Søren> But your problems wont end there :( Søren> It seems the CTM generation has halted, there hasn't been a Søren> delta for 48 hours now. The machine that normally carries the Søren> masters shrimp.dataplex.net has vanished from the net, so has Søren> Mr Wackerbart it seems (or his mailaacount on dataplex.net Søren> has been closed) as he doesn't respond to mail (yet). First of all to stand up for Richard: About a week ago his father had to be hospitalized and since then circumstances force him to let his machines run without his personal administration. He promised me to join the crowd again as soon as things have settled down a bit (I don't know when this will be). I am sure he would have chosen an alternative if he had been able to. So, everyone who has sent him mail, have some more patience please. The "dissolvance" of the dataplex.net domain origins from another phenomenon. I did a traceroute to his site (208.2.87.3 if you want to try for yourself), and this is what I've got: 1 Cisco (136.199.8.33) 4 ms 0 ms 4 ms 2 LanWanGate (136.199.224.2) 4 ms 4 ms 4 ms 3 XLink (136.199.1.41) 12 ms 12 ms 8 ms 4 WAN-Trier-Saarbruecken.novocomp.de (194.120.166.2) 23 ms 16 ms 20 ms 5 kbs.core.xlink.net (194.122.226.2) 31 ms 23 ms 35 ms 6 karlsruhe.core.xlink.net (194.122.227.85) 20 ms 35 ms 23 ms 7 frankfurt.core.xlink.net (194.122.225.42) 16 ms 66 ms 39 ms 8 Vienna2.VA.US.EU.net (134.222.19.1) 148 ms 156 ms 164 ms 9 Pennsauken1.NJ.US.EU.net (134.222.228.2) 156 ms 160 ms 164 ms 10 2-sprint-nap.internetmci.net (192.157.69.48) 180 ms 168 ms 148 ms 11 core2-hssi2-0.WestOrange.mci.net (204.70.1.49) 164 ms 172 ms 156 ms 12 core2.Dallas.mci.net (204.70.4.69) 227 ms 246 ms 219 ms 13 border6-fddi-0.Dallas.mci.net (204.70.114.66) 203 ms 215 ms 219 ms 14 amicus-networks.Dallas.mci.net (204.70.147.70) 207 ms * 211 ms 15 10.1.1.3 (10.1.1.3) 230 ms 187 ms 187 ms After hop 15 the connections seems to be broken as it times out. Now as our DNS can't reach their DNS, it looks like their domain has vanished from the face of the earth. Another side effect is that I can't send him any mail, and everybody within dataplex.net is likely to be unable to reach anybody outside. This includes any CTM delta of course. I have experienced similar cases in the past where entire domains vanished and reappeared the next day as if there had never been any problems before. To come to the point, I think this is just a (though very bad) case of a network problem which will hopefully be solved very very soon. Søren> I think we should try find CTM a new home, it has been much Søren> to unreliable lately. What does it take ?? a few gigs of disk Søren> and a machine with resonable connectivity ?? Søren, I think you are blaming the wrong guy. Since Richard has taken over the CTM production it is working like a charm (Poul-Henning, this is in no way an offence against you). What has caused Richard grief and what has finally led to the direct CTM link from his site to mine is the fact that the _distribution_ of the deltas breaks down from time to time for reasons that are out of his scope. I can judge this well because everytime people complain about a missing delta is has always found its way to our ftp site (maybe it's because we are deliberartely bypassing freebsd.org). Therefore we should consider changing something about the distribition, not the generation. A possible solution would be to move the distribution lists to another site, preferable in another domain. I'm sure if someone wants to step in Richard will provide him/her with any help he can offer (and a direct CTM feed of course). I known from past discussions with Richard that has wants these problems to be solved as soon as anybody else does. Sascha Blank, CTM-submeister -- Sascha Blank - mailto:blank@fox.uni-trier.de Student and System Administrator at the University of Trier, Germany Finger my account to receive my Public PGP key I don't speak for my employers, they don't pay me enough for that. From owner-freebsd-current Fri May 30 06:14:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA15087 for current-outgoing; Fri, 30 May 1997 06:14:34 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA15078 for ; Fri, 30 May 1997 06:14:30 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id OAA15844; Fri, 30 May 1997 14:14:23 +0100 (BST) Date: Fri, 30 May 1997 14:14:23 +0100 (BST) From: Doug Rabson To: Bruce Evans cc: current@freebsd.org Subject: Re: disk cache challenged by small block sizes In-Reply-To: <199705301242.WAA07183@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 30 May 1997, Bruce Evans wrote: > >This version fixes a bug (passing an offset instead of a size to > >vm_page_set_invalid) which was probably the cause of the trap, should work > >properly for large files (I was using the wrong offset type) and possibly > >has a more acceptable style(9). > > It seems to fix all the speed problems (except ufs is still slower with > a larger fs blocksize) and the block leak in ex2tfs. If you roll vfs_bio.c back to rev 1.115, does it affect the speed of ufs with 8k blocksize? I am not sure whether my changes to vfs_bio would affect that. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 From owner-freebsd-current Fri May 30 07:16:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17393 for current-outgoing; Fri, 30 May 1997 07:16:25 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA17381; Fri, 30 May 1997 07:16:18 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.5/8.7.3) id QAA04273; Fri, 30 May 1997 16:16:24 +0200 (MEST) From: Søren Schmidt Message-Id: <199705301416.QAA04273@sos.freebsd.dk> Subject: Re: ctm In-Reply-To: <199705301253.OAA04727@sliphost37.uni-trier.de> from Sascha Blank at "May 30, 97 02:53:43 pm" To: blank@fox.uni-trier.de Date: Fri, 30 May 1997 16:16:24 +0200 (MEST) Cc: chuckr@glue.umd.edu, gpalmer@FreeBSD.ORG, freebsd-current@freefall.FreeBSD.org, postmaster@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Sascha Blank who wrote: > >>>>> "Søren" == Søren Schmidt writes: > > Søren> But your problems wont end there :( > > Søren> It seems the CTM generation has halted, there hasn't been a > Søren> delta for 48 hours now. The machine that normally carries the > Søren> masters shrimp.dataplex.net has vanished from the net, so has > Søren> Mr Wackerbart it seems (or his mailaacount on dataplex.net > Søren> has been closed) as he doesn't respond to mail (yet). > > First of all to stand up for Richard: About a week ago his father had > to be hospitalized and since then circumstances force him to let his > machines run without his personal administration. He promised me to > join the crowd again as soon as things have settled down a bit (I > don't know when this will be). I am sure he would have chosen an > alternative if he had been able to. So, everyone who has sent him > mail, have some more patience please. Hmm, I'm sorry about that, but it doesn't help the ones (like me) that depend on CTM delivering... It would have been nice if we had gotten a short statement to the fact that delivery could be unreliable for a short time.. > Søren> I think we should try find CTM a new home, it has been much > Søren> to unreliable lately. What does it take ?? a few gigs of disk > Søren> and a machine with resonable connectivity ?? > > Søren, I think you are blaming the wrong guy. Since Richard has taken > over the CTM production it is working like a charm (Poul-Henning, this > is in no way an offence against you). What has caused Richard grief > and what has finally led to the direct CTM link from his site to mine > is the fact that the _distribution_ of the deltas breaks down from > time to time for reasons that are out of his scope. I can judge this > well because everytime people complain about a missing delta is has > always found its way to our ftp site (maybe it's because we are > deliberartely bypassing freebsd.org). I'm not blaming anybody, I just rationalize the fact that (at least to me) CTM delivery is important (and as far as I'm concerned, it worked flawlessly under phk's wings, until the old setup broke) and its important that it works (and is looked after). If the problms can be resolved and dataplex.net connectivity be brought to a level where it can be reached, then by all means do it, but its pretty fatal that the CTM delivery is standing still... In the meantime I'll have to fight cvsup :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Fri May 30 08:13:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA20163 for current-outgoing; Fri, 30 May 1997 08:13:46 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA20155 for ; Fri, 30 May 1997 08:13:44 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id IAA10566 for ; Fri, 30 May 1997 08:13:40 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id RAA10847 for ; Fri, 30 May 1997 17:12:21 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id RAA18795 for freebsd-current@freefall.cdrom.com; Fri, 30 May 1997 17:15:42 +0200 (MEST) Date: Fri, 30 May 1997 17:15:42 +0200 (MEST) From: Christoph Kukulies Message-Id: <199705301515.RAA18795@gil.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: if.h inclusion of Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Could some committer take a heart and #include in /sys/net/if.h to make it self supporting. In so many places (especially bisdn) compilation falls over and it's a pain in the neck to keep track with these changes everytime. From what I understand header files should become self-supporting sooner or later. Would it break anything to start doing this in if.h now? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Fri May 30 08:39:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21209 for current-outgoing; Fri, 30 May 1997 08:39:50 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21199; Fri, 30 May 1997 08:39:38 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/8.7.3) with SMTP id LAA27253; Fri, 30 May 1997 11:39:29 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id LAA17952; Fri, 30 May 1997 11:39:25 -0400 Date: Fri, 30 May 1997 11:39:11 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Søren Schmidt cc: blank@fox.uni-trier.de, gpalmer@FreeBSD.ORG, freebsd-current@freefall.FreeBSD.org, postmaster@FreeBSD.ORG Subject: Re: ctm In-Reply-To: <199705301416.QAA04273@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id IAA21202 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 30 May 1997, Søren Schmidt wrote: > > Søren, I think you are blaming the wrong guy. Since Richard has taken > > over the CTM production it is working like a charm (Poul-Henning, this > > is in no way an offence against you). What has caused Richard grief > > and what has finally led to the direct CTM link from his site to mine > > is the fact that the _distribution_ of the deltas breaks down from > > time to time for reasons that are out of his scope. I can judge this > > well because everytime people complain about a missing delta is has > > always found its way to our ftp site (maybe it's because we are > > deliberartely bypassing freebsd.org). > > I'm not blaming anybody, I just rationalize the fact that (at least > to me) CTM delivery is important (and as far as I'm concerned, it > worked flawlessly under phk's wings, until the old setup broke) and > its important that it works (and is looked after). > > If the problms can be resolved and dataplex.net connectivity > be brought to a level where it can be reached, then by all means > do it, but its pretty fatal that the CTM delivery is standing > still... > > In the meantime I'll have to fight cvsup :) Soren, I would like to be able to fall back to cvsup, because when my connectivity is good, it would do it, but I don't know any reliable method of getting back to ctm, without requiring me to download one of the "A" deltas. If you know a way to do this, and you would post it, it would let me stay current right now, but jump back on ctm when I could do it. When ctm works, it's reliability factor is so high, of course I'd fall back to it. Actually ctm always works (like was said already), it's the network that lets us down. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Fri May 30 08:51:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21918 for current-outgoing; Fri, 30 May 1997 08:51:14 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21913 for ; Fri, 30 May 1997 08:51:10 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id LAA01946; Fri, 30 May 1997 11:51:05 -0400 (EDT) Date: Fri, 30 May 1997 11:51:05 -0400 (EDT) From: Garrett Wollman Message-Id: <199705301551.LAA01946@khavrinen.lcs.mit.edu> To: Christoph Kukulies Cc: freebsd-current@freefall.FreeBSD.org Subject: if.h inclusion of In-Reply-To: <199705301515.RAA18795@gil.physik.rwth-aachen.de> References: <199705301515.RAA18795@gil.physik.rwth-aachen.de> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: > Could some committer take a heart and #include > in /sys/net/if.h to make it self supporting. In so many places > (especially bisdn) compilation falls over and it's a pain in the neck > to keep track with these changes everytime. Then bisdn should properly include like every other client of does. The former is a prerequisite for the latter. -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 From owner-freebsd-current Fri May 30 08:57:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA22125 for current-outgoing; Fri, 30 May 1997 08:57:44 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA22113 for ; Fri, 30 May 1997 08:57:40 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id RAA12395; Fri, 30 May 1997 17:57:37 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id SAA19086; Fri, 30 May 1997 18:01:00 +0200 (MEST) From: Christoph Kukulies Message-Id: <199705301601.SAA19086@gil.physik.rwth-aachen.de> Subject: Re: if.h inclusion of In-Reply-To: <199705301551.LAA01946@khavrinen.lcs.mit.edu> from Garrett Wollman at "May 30, 97 11:51:05 am" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 30 May 1997 18:00:59 +0200 (MEST) Cc: kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-current@freefall.FreeBSD.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > < said: > > > Could some committer take a heart and #include > > in /sys/net/if.h to make it self supporting. In so many places > > (especially bisdn) compilation falls over and it's a pain in the neck > > to keep track with these changes everytime. > > Then bisdn should properly include like every other > client of does. The former is a prerequisite for the > latter. OK, Hellmuth, Gary, have you read this? > > -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 > -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Fri May 30 09:45:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA24449 for current-outgoing; Fri, 30 May 1997 09:45:09 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA24423; Fri, 30 May 1997 09:44:55 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id JAA28650; Fri, 30 May 1997 09:44:43 -0700 (PDT) Message-Id: <199705301644.JAA28650@austin.polstra.com> To: max@wide.ad.jp Subject: Re: Some trouble with SCSI HD Newsgroups: polstra.freebsd.current In-Reply-To: <199705300652.PAA00798@bourbon.sfc.wide.ad.jp> References: <199705300652.PAA00798@bourbon.sfc.wide.ad.jp> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org, wollman@freebsd.org Date: Fri, 30 May 1997 09:44:43 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199705300652.PAA00798@bourbon.sfc.wide.ad.jp>, Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= wrote: > I'm running -current from about a week ago. When I run cvsup to get > some files from cvsupd running on localhost, the system freezes. Many > times, the system just goes quiet and no input from console is > accepted. A few other other times, it goes half dead, I mean, I can > traceroute or ping to the system from another machine but nothing > else can be done. > > When I run cvsup and get files from remote system, this doesn't > happen. I noticed this too when I tried to CVSup to localhost. I don't think it has anything to do with SCSI. I think it's a networking bug in the loopback interface, exposed by CVSup's unusual traffic patterns. If you CVSup to yourhost.domain.name instead of localhost, it works fine. I've been meaning to look into this problem, but I haven't gotten around to it. Maybe Garrett will have some ideas. I've added him to the cc list. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Fri May 30 10:47:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28144 for current-outgoing; Fri, 30 May 1997 10:47:53 -0700 (PDT) Received: from sliphost37.uni-trier.de (root@sliphost37.uni-trier.de [136.199.240.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA28121; Fri, 30 May 1997 10:47:25 -0700 (PDT) Received: (from blank@localhost) by sliphost37.uni-trier.de (8.8.5/8.8.5) id TAA08226; Fri, 30 May 1997 19:33:29 +0200 (CEST) Date: Fri, 30 May 1997 19:33:29 +0200 (CEST) Message-Id: <199705301733.TAA08226@sliphost37.uni-trier.de> From: Sascha Blank To: =?ISO-8859-1?Q?S=F8ren?= Schmidt Cc: blank@fox.uni-trier.de, chuckr@glue.umd.edu, gpalmer@FreeBSD.ORG, freebsd-current@freefall.FreeBSD.org, postmaster@FreeBSD.ORG Subject: Re: ctm In-Reply-To: <199705301416.QAA04273@sos.freebsd.dk> References: <199705301253.OAA04727@sliphost37.uni-trier.de> <199705301416.QAA04273@sos.freebsd.dk> X-Mailer: VM 6.31 under 19.15p4 XEmacs Lucid Reply-To: Sascha Blank X-PGP-Fingerprint: 26 FD 71 B5 48 12 42 91 10 1C 4F 74 70 48 6F 89 Comments: Hyperbole mail buttons accepted, v04.023. Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA28126 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello Søren, >> "Søren" == Søren Schmidt writes: Søren> Hmm, I'm sorry about that, but it doesn't help the ones (like Søren> me) that depend on CTM delivering... It would have been nice Søren> if we had gotten a short statement to the fact that delivery Søren> could be unreliable for a short time.. I just want to save Richard from thoughts like "Hey, we are having major problems here with his stuff and this guy has the nerve to vanish from the face of the earth". It doesn't help us, but we know at least why he is not around. Søren> I'm not blaming anybody, I just rationalize the fact that (at Søren> least to me) CTM delivery is important (and as far as I'm Søren> concerned, it worked flawlessly under phk's wings, until the Søren> old setup broke) and its important that it works (and is Søren> looked after). I'm sorry if I got you wrong. I agree completely with you that a reliable CTM delivery is vital for many of us no matter whether they are a developer, a user or a site admin. And yes, I want to see it running again as soon as possible. But I'm afraid all we can do at the moment is to sit and wait for dataplex.net to come alive again. It is rather obvious that some of us have to think about additional reproduction and distribution ways to prevent future accidents of this kind once things are running again. Richard and I have already started discussing this topic, but regarding this latest incident it looks like we will have to expand the scope of our discussion. Sascha Blank, CTM-submeister -- Sascha Blank - mailto:blank@fox.uni-trier.de Student and System Administrator at the University of Trier, Germany Finger my account to receive my Public PGP key I don't speak for my employers, they don't pay me enough for that. From owner-freebsd-current Fri May 30 10:56:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28657 for current-outgoing; Fri, 30 May 1997 10:56:29 -0700 (PDT) Received: from bourbon.sfc.wide.ad.jp (bourbon.sfc.wide.ad.jp [203.178.139.171]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA28643; Fri, 30 May 1997 10:56:08 -0700 (PDT) Received: from bourbon.sfc.wide.ad.jp (localhost [127.0.0.1]) by bourbon.sfc.wide.ad.jp (8.8.5/3.5Wpl104/21/97) with ESMTP id CAA00639; Sat, 31 May 1997 02:55:48 +0900 (JST) Message-Id: <199705301755.CAA00639@bourbon.sfc.wide.ad.jp> To: jdp@polstra.com Cc: max@wide.ad.jp, current@freebsd.org, wollman@freebsd.org Subject: loopback i/f bug (?) [ was Re: Some trouble with SCSI HD] From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Fri, 30 May 1997 09:44:43 -0700" References: <199705301644.JAA28650@austin.polstra.com> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 31 May 1997 02:55:46 +0900 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I'm running -current from about a week ago. When I run cvsup >> to get some files from cvsupd running on localhost, the system >> freezes. Many times, the system just goes quiet and no input >> from console is accepted. A few other other times, it goes >> half dead, I mean, I can traceroute or ping to the system from >> another machine but nothing else can be done. >> >> When I run cvsup and get files from remote system, this doesn't >> happen. jdp> I noticed this too when I tried to CVSup to localhost. I jdp> don't think it has anything to do with SCSI. I think it's a jdp> networking bug in the loopback interface, exposed by CVSup's jdp> unusual traffic patterns. jdp> If you CVSup to yourhost.domain.name instead of localhost, it jdp> works fine. Looks like you are right, John. I removed /usr/ports, and re-cvsup'ed the ports-all collection from my machine, specifying the FQDN this time, instead of ``localhost'' and it went OK. So, as you say, it's more than likely that loopback interface has some problem. Thanks for your suggestion. It really helped! Cheers, Max From owner-freebsd-current Fri May 30 11:00:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA29064 for current-outgoing; Fri, 30 May 1997 11:00:43 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA29058 for ; Fri, 30 May 1997 11:00:41 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id DAA15930; Sat, 31 May 1997 03:53:03 +1000 Date: Sat, 31 May 1997 03:53:03 +1000 From: Bruce Evans Message-Id: <199705301753.DAA15930@godzilla.zeta.org.au> To: kuku@gilberto.physik.RWTH-Aachen.DE, wollman@khavrinen.lcs.mit.edu Subject: Re: if.h inclusion of Cc: freebsd-current@freefall.FreeBSD.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Then bisdn should properly include like every other >client of does. The former is a prerequisite for the >latter. I broke this in rev.1.9 of (by including there) and fixed it in rev.1.35. Including it just encourages unportable programs. The breakage is in all 2.0 and 2.1 releases of FreeBSD. Bruce From owner-freebsd-current Fri May 30 13:23:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06041 for current-outgoing; Fri, 30 May 1997 13:23:31 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA05991; Fri, 30 May 1997 13:21:14 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-40.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA21505 (5.67b/IDA-1.5); Fri, 30 May 1997 22:08:21 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id WAA05711; Fri, 30 May 1997 22:08:19 +0200 (CEST) X-Face: " Date: Fri, 30 May 1997 22:08:18 +0200 From: Stefan Esser To: Doug Rabson Cc: "Justin T. Gibbs" , Bruce Evans , current@FreeBSD.ORG, gurney_j@resnet.uoregon.edu, Stefan Esser Subject: Re: cvs commit: src/sys/sys interrupt.h src/sys/kern kern_intr.c References: <19970528143223.25591@x14.mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Doug Rabson on Wed, May 28, 1997 at 02:07:33PM +0100 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 28, Doug Rabson wrote: > > If we do this, can the interrupt descriptor fiddling happen through a > function call? I don't want drivers to know what is inside this > structure. In fact I would be happiest if intrec wasn't declared in a > public header file at all but was private to kern_intr.c Yes, I agree. The interrupt descriptor is far to critical to be directly manipulated from drivers. It should be opaque to code outside kern_intr.c, and I will change the code into that direction with the next commit in that area. Regards, STefan From owner-freebsd-current Fri May 30 13:31:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06432 for current-outgoing; Fri, 30 May 1997 13:31:06 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA06422 for ; Fri, 30 May 1997 13:31:03 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id GAA19539; Sat, 31 May 1997 06:16:07 +1000 Date: Sat, 31 May 1997 06:16:07 +1000 From: Bruce Evans Message-Id: <199705302016.GAA19539@godzilla.zeta.org.au> To: bde@zeta.org.au, dfr@nlsystems.com Subject: Re: disk cache challenged by small block sizes Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> It seems to fix all the speed problems (except ufs is still slower with >> a larger fs blocksize) and the block leak in ex2tfs. > >If you roll vfs_bio.c back to rev 1.115, does it affect the speed of ufs >with 8k blocksize? I am not sure whether my changes to vfs_bio would >affect that. That wasn't it. The slowdown was caused by ffs deciding to allocate all the blocks starting with the first indirect block on a slower part of the disk. It attempts to pessimize all cases, but is confused by fuzzy rounding :-). Details: 1. The file system has size 96MB (exactly). 2. The defaults for a block size of 4K give 10 cylinder groups (cg's) with 9 of size 10MB and one smaller one (slightly less than 6MB because of special blocks before the first cg). The average size is about 9.6MB. 3. The defaults for a block size of 8K give 3 cg's with 2 of size 32MB and one slightly smaller one. The average size is about 32MB. 4. I ran iozone on a new file system, so there was just one directory and one file. 5. The inode for the file was allocated in cg #0 in both cases. 6. The direct blocks were allocated in the same cg as the inode in both cases. 7. The first indirect block and subsequent data blocks are allocated on a cg with >= the average number of free blocks. (The comments before ffs_blkpref() about using a rotor are wrong. fs->fs_cgrotor is never used.) 8. In case (2), cg #0 is chosen because it has almost 10MB-metatada free and the average is about 9.6MB-metadata. 9. In case (3), cg #1 is chosen since it has significantly less than 32MB-metadata free and the average is about 32MB-metadata. 10. In case (3), cg #1 starts a full 1/3 of the way towards the slowest parts of the disk and the speed is significantly slower there. I think the combination of algorithms behind (6) and (7) is often wrong. It's silly to put the direct blocks on a different cg than the indirect blocks immediately following them. The silliest case is for a new file system with all cg's of the same size. Then exact calculation of the average number of free blocks would result in the indirect blocks always starting on cg #1 despite cg #0 being almost empty when the first indirect block is allocated. I added a bias towards using the same cg as the inode for the first indirect block. This is probably too strong. Bruce diff -c2 ffs_alloc.c~ ffs_alloc.c *** ffs_alloc.c~ Mon Mar 24 14:21:27 1997 --- ffs_alloc.c Sat May 31 03:08:56 1997 *************** *** 689,692 **** --- 686,700 ---- startcg %= fs->fs_ncg; avgbfree = fs->fs_cstotal.cs_nbfree / fs->fs_ncg; + /* + * Prefer the same cg as the inode if this allocation + * is for the first block in an indirect block. + */ + if (lbn == NDADDR) { + cg = ino_to_cg(fs, ip->i_number); + if (fs->fs_cs(fs, cg).cs_nbfree >= avgbfree / 2) { + fs->fs_cgrotor = cg; + return (fs->fs_fpg * cg + fs->fs_frag); + } + } for (cg = startcg; cg < fs->fs_ncg; cg++) if (fs->fs_cs(fs, cg).cs_nbfree >= avgbfree) { *************** *** 694,698 **** return (fs->fs_fpg * cg + fs->fs_frag); } ! for (cg = 0; cg <= startcg; cg++) if (fs->fs_cs(fs, cg).cs_nbfree >= avgbfree) { fs->fs_cgrotor = cg; --- 702,706 ---- return (fs->fs_fpg * cg + fs->fs_frag); } ! for (cg = 0; cg < startcg; cg++) if (fs->fs_cs(fs, cg).cs_nbfree >= avgbfree) { fs->fs_cgrotor = cg; From owner-freebsd-current Fri May 30 13:36:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06901 for current-outgoing; Fri, 30 May 1997 13:36:43 -0700 (PDT) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA06883 for ; Fri, 30 May 1997 13:36:31 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id WAA00309; Fri, 30 May 1997 22:35:16 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199705302035.WAA00309@helbig.informatik.ba-stuttgart.de> Subject: Re: if.h inclusion of In-Reply-To: <199705301601.SAA19086@gil.physik.rwth-aachen.de> from Christoph Kukulies at "May 30, 97 06:00:59 pm" To: kuku@gilberto.physik.RWTH-Aachen.DE Date: Fri, 30 May 1997 22:35:16 +0200 (MET DST) Cc: wollman@khavrinen.lcs.mit.edu, kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-current@freefall.FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > < said: > > > > > Could some committer take a heart and #include > > > in /sys/net/if.h to make it self supporting. In so many places > > > (especially bisdn) compilation falls over and it's a pain in the neck Which compilation in bisdn falls over? At least the kernel stuff does not if you use the sources in bisdntest-2 and the userland part of bisdn097 compiled well from FreeBSD 2.1.5 till -current as far as I recollect. But there might be more problems that are hidden in my installation. > > > to keep track with these changes everytime. > > > > Then bisdn should properly include like every other > > client of does. The former is a prerequisite for the > > latter. > > OK, Hellmuth, Gary, have you read this? > > > > > -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 > > > > -- > Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > From owner-freebsd-current Fri May 30 15:27:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA12313 for current-outgoing; Fri, 30 May 1997 15:27:43 -0700 (PDT) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA12293 for ; Fri, 30 May 1997 15:27:30 -0700 (PDT) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA13490; Sat, 31 May 97 00:28:05 +0100 Date: Sat, 31 May 97 00:28:05 +0100 Message-Id: <9705302328.AA13490@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: current@freebsd.org Subject: sio.c: incorrect identification of 16550A X-Mailer: Emacs Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16750 sio1 is in fact a 16550A (in principle identical to sio0 since both are in the same chip) Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr ============================================================================= From owner-freebsd-current Fri May 30 16:19:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA14839 for current-outgoing; Fri, 30 May 1997 16:19:21 -0700 (PDT) Received: from gaia.coppe.ufrj.br (root@[146.164.5.200]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA14833 for ; Fri, 30 May 1997 16:19:17 -0700 (PDT) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.5/8.7.3) id UAA24742 for current@freebsd.org; Fri, 30 May 1997 20:19:13 -0300 (EST) From: Joao Carlos Mendes Luis Message-Id: <199705302319.UAA24742@gaia.coppe.ufrj.br> Subject: RELENG_2_2 does not compile... To: current@freebsd.org Date: Fri, 30 May 1997 20:19:13 -0300 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id QAA14835 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there a problem on RELENG_2_2 ? cd /usr/src ; make -> ... ===> gnu/lib/libregex ===> gnu/lib/libregex/doc ===> gnu/lib/libreadline ===> gnu/lib/libreadline/doc ===> gnu/lib/libreadline/doc/history ===> gnu/lib/libreadline/doc/readline ===> gnu/lib/libstdc++ c++ -O2 -m486 -pipe -fexpensive-optimizations -I/usr/cvsup/RELENG_2_2/src/gnu/lib/libstdc++/../../../contrib/libg++/include -I/usr/include/g++ -I. -I/usr/cvsup/RELENG_2_2/src/gnu/lib/libstdc++/../../../contrib/libg++/include -I/usr/cvsup/RELENG_2_2/src/gnu/lib/libstdc++/../../../contrib/libg++/libio -I/usr/cvsup/RELENG_2_2/src/gnu/lib/libstdc++/../../../contrib/libg++/libstdc++ -fno-implicit-templates -c /usr/cvsup/RELENG_2_2/src/gnu/lib/libstdc++/../../../contrib/libg++/libio/isscan.cc -o isscan.o /usr/cvsup/RELENG_2_2/src/gnu/lib/libstdc++/../../../contrib/libg++/libio/isscan.cc: In method `class istream & istream::scan(const char * ...)': /usr/cvsup/RELENG_2_2/src/gnu/lib/libstdc++/../../../contrib/libg++/libio/isscan.cc:34: bad argument 2 for function `int streambuf::vscan(const char *, char *, class ios * = 0)' (type was void *) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. ... Also: make depend -> ... ===> usr.sbin/portmap ===> usr.sbin/portmap/pmap_set ===> usr.sbin/portmap/pmap_dump ===> usr.sbin/ppp rm -f .depend mkdep -f .depend -a -DMSEXT -DPASSWDAUTH /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/alias_cmd.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/arp.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/async.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/auth.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/ccp.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/chap.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/chat.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/command.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/filter.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/fsm.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/hdlc.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/ip.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/ipcp.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/lcp.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/loadalias.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/log.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/lqr.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/main.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/mbuf.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/modem.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/os.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/pap.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/passwdauth.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/pred.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/route.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/sig.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/slcompress.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/systems.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/timer.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/vars.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/vjcomp.c /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/command.c:34: alias.h: No such file or directory /usr/cvsup/RELENG_2_2/src/usr.sbin/ppp/ip.c:35: alias.h: No such file or directory mkdep: compile failed. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. ... Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 ( Job ) jonny@cisi.coppe.ufrj.br Network Manager UFRJ/COPPE/CISI Universidade Federal do Rio de Janeiro From owner-freebsd-current Fri May 30 21:28:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA04785 for current-outgoing; Fri, 30 May 1997 21:28:40 -0700 (PDT) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA04778 for ; Fri, 30 May 1997 21:28:36 -0700 (PDT) Received: (from uucp@localhost) by abby.skypoint.net (8.8.5/alexis 2.7) with UUCP id XAA15458; Fri, 30 May 1997 23:28:30 -0500 (CDT) Received: (from bruce@localhost) by zuhause.mn.org (8.8.5/8.8.5) id XAA00264; Fri, 30 May 1997 23:12:34 -0500 (CDT) Date: Fri, 30 May 1997 23:12:34 -0500 (CDT) Message-Id: <199705310412.XAA00264@zuhause.mn.org> From: Bruce Albrecht To: Jean-Marc Zucconi Cc: current@FreeBSD.ORG Subject: Re: sio.c: incorrect identification of 16550A In-Reply-To: <9705302328.AA13490@cabri.obs-besancon.fr> References: <9705302328.AA13490@cabri.obs-besancon.fr> X-Mailer: VM 6.30 under 19.15p2 XEmacs Lucid Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jean-Marc Zucconi writes: > Hi, > > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16750 > > sio1 is in fact a 16550A (in principle identical to sio0 since both > are in the same chip) In addition to this new bug, I've been seeing a problem where my dialout uucp's on sio1 are able to call up and log in to the remote system, but lock up the port without ever transmitting any data after completing the uucico log-in. This has been occurring ever since the sio changes last week, but only when I get the following messages: sio0: 64 events for device with no tp sio1: 65 events for device with no tp Prior to last night's sio.c changes, it would tie up the line indefinitely, but now it uucp times out and frees up the port. If I boot, the sio1 message says 64 events, the uucico doesn't lock up. I'm going to have to reboot now. :-( From owner-freebsd-current Fri May 30 21:29:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA04843 for current-outgoing; Fri, 30 May 1997 21:29:52 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA04838 for ; Fri, 30 May 1997 21:29:49 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA04356; Sat, 31 May 1997 13:59:13 +0930 (CST) From: Michael Smith Message-Id: <199705310429.NAA04356@genesis.atrad.adelaide.edu.au> Subject: Re: old libs in /usr/lib In-Reply-To: <199705300905.MAA24629@shadows.aeon.net> from mika ruohotie at "May 30, 97 12:05:45 pm" To: bsdcur@shadows.aeon.net (mika ruohotie) Date: Sat, 31 May 1997 13:59:12 +0930 (CST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk mika ruohotie stands accused of saying: > > > there's quite a few old libs in /usr/lib, some are different versions, > > There's a Tcl script under tools/ to check your executables. > > so i'm safe if i nuke whatever it reports 'stale'? The current version (the one you're using) is reasonably smart about libraries that are the target of symbolic links. Ultimately, use your judgement - if there's a library marked as 'stale' and there are newer versions of the same library, then go ahead and nuke the old one. If you're not sure, put the library somewhere else and see if things still work OK after a reboot - if they do, nuke it. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Fri May 30 21:35:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA05244 for current-outgoing; Fri, 30 May 1997 21:35:38 -0700 (PDT) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA05239 for ; Fri, 30 May 1997 21:35:35 -0700 (PDT) Received: (from uucp@localhost) by abby.skypoint.net (8.8.5/alexis 2.7) with UUCP id XAA15691 for current@FreeBSD.ORG; Fri, 30 May 1997 23:35:34 -0500 (CDT) Received: (from bruce@localhost) by zuhause.mn.org (8.8.5/8.8.5) id XAA00265; Fri, 30 May 1997 23:34:22 -0500 (CDT) Date: Fri, 30 May 1997 23:34:22 -0500 (CDT) Message-Id: <199705310434.XAA00265@zuhause.mn.org> From: Bruce Albrecht To: current@FreeBSD.ORG Subject: Re: sio.c: incorrect identification of 16550A In-Reply-To: <199705310412.XAA00264@zuhause.mn.org> References: <9705302328.AA13490@cabri.obs-besancon.fr> <199705310412.XAA00264@zuhause.mn.org> X-Mailer: VM 6.30 under 19.15p2 XEmacs Lucid Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Albrecht writes: > In addition to this new bug, I've been seeing a problem where my > dialout uucp's on sio1 are able to call up and log in to the remote > system, but lock up the port without ever transmitting any data after > completing the uucico log-in. This has been occurring ever since the > sio changes last week, but only when I get the following messages: > sio0: 64 events for device with no tp > sio1: 65 events for device with no tp > Prior to last night's sio.c changes, it would tie up the line > indefinitely, but now it uucp times out and frees up the port. If I > boot, the sio1 message says 64 events, the uucico doesn't lock up. After rebooting 3 times, I've decided that sio1 is totally hosed, so I swapped the cables for the two ports. My uucp is working again (since you've all received this), however, it appears that at 57600 baud, sio1 is dropping about the last half of the 32 bytes or so of the login prompt, and just about every other buffer sent. From owner-freebsd-current Fri May 30 22:12:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA06875 for current-outgoing; Fri, 30 May 1997 22:12:14 -0700 (PDT) Received: from mail0.iij.ad.jp (mail0.iij.ad.jp [202.232.2.113]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA06870 for ; Fri, 30 May 1997 22:12:11 -0700 (PDT) Received: from uucp2.iij.ad.jp (uucp2.iij.ad.jp [202.232.2.202]) by mail0.iij.ad.jp (8.8.5+2.7Wbeta5/3.5Wpl4-MAIL) with SMTP id OAA07090 for ; Sat, 31 May 1997 14:12:09 +0900 (JST) Received: (from uucp@localhost) by uucp2.iij.ad.jp (8.6.12+2.4W/3.3W9-UUCP) with UUCP id OAA28435 for current@freebsd.org; Sat, 31 May 1997 14:12:09 +0900 Received: from tyd1.tydfam.iijnet.or.jp (tyd1.tydfam.iijnet.or.jp [192.168.1.2]) by tydfam.iijnet.or.jp (8.8.5/3.4W2-uucp) with ESMTP id NAA08605 for ; Sat, 31 May 1997 13:38:51 +0900 (JST) Received: from localhost.tydfam.iijnet.or.jp (localhost.tydfam.iijnet.or.jp [127.0.0.1]) by tyd1.tydfam.iijnet.or.jp (8.8.5/3.4Wnomx) with SMTP id NAA00421 for ; Sat, 31 May 1997 13:38:42 +0900 (JST) Message-Id: <199705310438.NAA00421@tyd1.tydfam.iijnet.or.jp> X-Authentication-Warning: tyd1.tydfam.iijnet.or.jp: localhost.tydfam.iijnet.or.jp [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: Q) ddd-2.1 compile Reply-To: ken@tydfam.iijnet.or.jp X-Mailer: Mew version 1.70 on Emacs 19.34.2 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 31 May 1997 13:38:42 +0900 From: Takeshi Yamada Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! I have the following error message when trying to compile ddd-2.1 using 'port' collection. I'm running Kernel-SMP and FreeBSD-current ca. 97/05/03 w/ 64MB DRAM, 128MB swap. What is supposed to be wrong? Any idea? : : : : gmake[1]: Entering directory `/usr/ports/devel/ddd/work/ddd-2.1/ddd' Building ddd-2.1-i386-unknown-freebsd3.0... c++ -DHAVE_CONFIG_H -DNDEBUG -O2 -g -Wall -fexternal-templates -felide-constructors -fconserve-space -c -I. -I. -I./.. -I./../include -I/usr/X11R6/include -o ddd.o ddd.C GraphNodeI.h: In method `ostrstream::~ostrstream()': In file included from GraphNode.h:37, from DispNode.h:43, from DataDisp.h:66, from ddd.C:183: GraphNodeI.h:117: virtual memory exhausted gmake[1]: *** [ddd.o] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/ddd/work/ddd-2.1/ddd' From owner-freebsd-current Fri May 30 23:37:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA10107 for current-outgoing; Fri, 30 May 1997 23:37:41 -0700 (PDT) Received: from shell.uniserve.com (shell.uniserve.com [204.244.210.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA10100 for ; Fri, 30 May 1997 23:37:38 -0700 (PDT) Received: from localhost (tom@localhost) by shell.uniserve.com (8.8.5/8.8.5) with SMTP id XAA09831; Fri, 30 May 1997 23:37:17 -0700 (PDT) X-Authentication-Warning: shell.uniserve.com: tom owned process doing -bs Date: Fri, 30 May 1997 23:37:17 -0700 (PDT) From: Tom To: ken@tydfam.iijnet.or.jp cc: current@FreeBSD.ORG Subject: Re: Q) ddd-2.1 compile In-Reply-To: <199705310438.NAA00421@tyd1.tydfam.iijnet.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 31 May 1997, Takeshi Yamada wrote: > Hi! > I have the following error message when trying to compile ddd-2.1 > using 'port' collection. > > I'm running Kernel-SMP and FreeBSD-current ca. 97/05/03 w/ 64MB > DRAM, 128MB swap. > What is supposed to be wrong? Any idea? > > : : : : > gmake[1]: Entering directory `/usr/ports/devel/ddd/work/ddd-2.1/ddd' > Building ddd-2.1-i386-unknown-freebsd3.0... > c++ -DHAVE_CONFIG_H -DNDEBUG -O2 -g -Wall -fexternal-templates -felide-constructors -fconserve-space -c -I. -I. -I./.. -I./../include -I/usr/X11R6/include -o ddd.o ddd.C > GraphNodeI.h: In method `ostrstream::~ostrstream()': > In file included from GraphNode.h:37, > from DispNode.h:43, > from DataDisp.h:66, > from ddd.C:183: > GraphNodeI.h:117: virtual memory exhausted > gmake[1]: *** [ddd.o] Error 1 > gmake[1]: Leaving directory `/usr/ports/devel/ddd/work/ddd-2.1/ddd' > The user-id that used to compile this is limited on how much memory it can use. Remember Unix was designed as a time-share system. See "man login.conf" for a way to increase your limits, or just compile it as root. Tom From owner-freebsd-current Sat May 31 01:17:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA12968 for current-outgoing; Sat, 31 May 1997 01:17:28 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA12963 for ; Sat, 31 May 1997 01:17:19 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id SAA06707; Sat, 31 May 1997 18:12:24 +1000 Date: Sat, 31 May 1997 18:12:24 +1000 From: Bruce Evans Message-Id: <199705310812.SAA06707@godzilla.zeta.org.au> To: bruce@zuhause.mn.org, jmz@cabri.obs-besancon.fr Subject: Re: sio.c: incorrect identification of 16550A Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >In addition to this new bug, I've been seeing a problem where my >dialout uucp's on sio1 are able to call up and log in to the remote >system, but lock up the port without ever transmitting any data after >completing the uucico log-in. This has been occurring ever since the >sio changes last week, but only when I get the following messages: > sio0: 64 events for device with no tp > sio1: 65 events for device with no tp These are harmless. All that matters is that the detected transmitter fifo size is <= the actual size. Since the detection code at best detects the _receiver_ fifo size, there may be problems. Bruce From owner-freebsd-current Sat May 31 02:47:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA16094 for current-outgoing; Sat, 31 May 1997 02:47:22 -0700 (PDT) Received: from sliphost37.uni-trier.de (root@sliphost37.uni-trier.de [136.199.240.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA16082; Sat, 31 May 1997 02:47:01 -0700 (PDT) Received: (from blank@localhost) by sliphost37.uni-trier.de (8.8.5/8.8.5) id UAA08319; Fri, 30 May 1997 20:26:38 +0200 (CEST) Date: Fri, 30 May 1997 20:26:38 +0200 (CEST) Message-Id: <199705301826.UAA08319@sliphost37.uni-trier.de> From: Sascha Blank To: =?ISO-8859-1?Q?S=F8ren?= Schmidt Cc: blank@fox.uni-trier.de, chuckr@glue.umd.edu, gpalmer@FreeBSD.ORG, freebsd-current@freefall.FreeBSD.org, postmaster@FreeBSD.ORG Subject: Re: ctm In-Reply-To: <199705301416.QAA04273@sos.freebsd.dk> References: <199705301253.OAA04727@sliphost37.uni-trier.de> <199705301416.QAA04273@sos.freebsd.dk> X-Mailer: VM 6.31 under 19.15p4 XEmacs Lucid Reply-To: Sascha Blank X-PGP-Fingerprint: 26 FD 71 B5 48 12 42 91 10 1C 4F 74 70 48 6F 89 Comments: Hyperbole mail buttons accepted, v04.023. Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA16089 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> "Søren" == Søren Schmidt writes: Hello, Søren> If the problms can be resolved and dataplex.net connectivity Søren> be brought to a level where it can be reached, then by all Søren> means do it, but its pretty fatal that the CTM delivery is Søren> standing still... I got this from whois: Digital Associates, Inc. (DATAPLEX-DOM) 8801 Camelia Ln. Austin, TX 78759 Domain Name: DATAPLEX.NET Administrative Contact, Technical Contact, Zone Contact: Wackerbarth, Richard (RW149) rkw@DATAPLEX.NET (512) 345-7941 I know it's very unusual, but how about anyone who can afford to do so calling this number? Maybe we can get some useful information... Well, just dreaming... -- Sascha Blank - mailto:blank@fox.uni-trier.de Student and System Administrator at the University of Trier, Germany Finger my account to receive my Public PGP key I don't speak for my employers, they don't pay me enough for that. From owner-freebsd-current Sat May 31 03:26:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA17402 for current-outgoing; Sat, 31 May 1997 03:26:36 -0700 (PDT) Received: from wall.jhs.no_domain (vector.muc.ditec.de [194.120.126.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA17346; Sat, 31 May 1997 03:25:05 -0700 (PDT) Received: from desk.jhs.no_domain (localhost [127.0.0.1]) by desk.jhs.no_domain (8.8.5/8.8.5) with ESMTP id MAA00615; Thu, 29 May 1997 12:16:05 +0200 (MET DST) Message-Id: <199705291016.MAA00615@desk.jhs.no_domain> To: Philippe Regnauld cc: Poul-Henning Kamp , current@freebsd.org, leo@dachau.marco.de Subject: Re: RFC2143, IP over SCSI From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" X-Email: jhs@freebsd.org, Fallback: jhs@gil.physik.rwth-aachen.de X-Web: http://www.freebsd.org/~jhs/ X-Company: Vector Systems Ltd, Unix & Internet Consultants. X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Tel: Phone +49.89.268616, Fax +49.89.2608126, Data +49.89.26023276 X-Software: FreeBSD (Unix) + EXMH 1.6.9 (PGP key on web) In-reply-to: Your message of "Wed, 28 May 1997 10:42:49 +0200." <19970528104249.50863@deepo.prosa.dk> Date: Thu, 29 May 1997 12:16:03 +0200 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: Philippe Regnauld > Subject: Re: RFC2143, IP over SCSI > Date: Wed, 28 May 1997 10:42:49 +0200 > Message-id: <19970528104249.50863@deepo.prosa.dk> > > Poul-Henning Kamp writes: > > > > OK, now we have a standard, who comes up with some code ? > > Didn't the NetBSD people have this working on PC532 ? Comming in late on this thread, but .... I'm a PC532 owner from way back, (haven't turned it on lately, but) : Yes I'm pretty sure PC532 did have IP over SCSI years ago, though I never used it personaly. PC532 used to run Minix & Mach, then NetBSD arrived, so I couldn't tell you which OS, IP over SCSI was implemented on, but NetBSD I think. The lists you could ask would be: pc532@bungi.com generic list for hardware owners port-pc532-owner@NetBSD.ORG for users of netbsd OS on pc532 Matthias leo@dachau.marco.de (on the lists) I seem to recall was a developer involved in SCSI-IP I've cc'd him What's a PC532 ? See http://www.freebsd.org/~jhs/txt/pc532.html Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Sat May 31 05:17:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA21495 for current-outgoing; Sat, 31 May 1997 05:17:34 -0700 (PDT) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA21477 for ; Sat, 31 May 1997 05:17:07 -0700 (PDT) Received: from labs.usn.blaze.net.au (local [127.0.0.1]) by labs.usn.blaze.net.au (8.8.5/8.8.5) with ESMTP id WAA00331; Sat, 31 May 1997 22:13:43 +1000 (EST) Message-Id: <199705311213.WAA00331@labs.usn.blaze.net.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: mika ruohotie cc: current@FreeBSD.ORG Subject: Re: old libs in /usr/lib In-reply-to: Your message of "Fri, 30 May 1997 12:05:45 +0300." <199705300905.MAA24629@shadows.aeon.net> X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 May 1997 22:13:40 +1000 From: David Nugent Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > reminds me, my ssh reports: > > May 30 12:02:35 shadows sshd[24622]: login_getclass: unknown class '00^B' > > something is wrong, with /etc/login.conf or something? uh, like > what do i have to do to it? Get the latest ssh port and recompile/reinstall it. The login.conf API changed to confirm to BSDI's latest. The above error is benign, but you're probably getting "default" resources instead of those applicable to the correct class. Regards, David David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-current Sat May 31 09:12:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA27153 for current-outgoing; Sat, 31 May 1997 09:12:49 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA27148 for ; Sat, 31 May 1997 09:12:45 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id JAA19193 for ; Sat, 31 May 1997 09:12:11 -0700 (PDT) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id LAA16922; Sat, 31 May 1997 11:10:48 -0500 (CDT) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <9705251933.AA12219@tulsix.utulsa.edu> References: <19970525115421.42464@xaa.stack.nl> from "Mark Huizer" at May 25, 97 11:54:21 am Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 31 May 1997 11:03:24 -0500 To: Tom Jackson From: Richard Wackerbarth Subject: Re: src-cur.2896.gz Cc: xaa@stack.nl (Mark Huizer), freebsd-current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 3:33 PM -0500 5/25/97, Tom Jackson wrote: >Strange as this may seem, go to ftp.uni-trier.de/pub/unix/FreeBSD/CTM/src-cur >and you will find the missing delta there. Go figure, Germany has it but >California doesn't. Sascha Blank is in Germany and interested in maintaining CTM service. We bypass California for his service. The California-based FreeBSD mailing list operation is the source of your problem. (Also, you are probably losing quite a bit of mail that you don't notice because it lacks sequence numbers) They are aware of the problem. I hope that they are able to restore reliability soon. From owner-freebsd-current Sat May 31 09:13:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA27199 for current-outgoing; Sat, 31 May 1997 09:13:08 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA27168; Sat, 31 May 1997 09:12:57 -0700 (PDT) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id LAA16818; Sat, 31 May 1997 11:10:26 -0500 (CDT) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <199705301253.OAA04727@sliphost37.uni-trier.de> References: <199705300624.IAA03466@sos.freebsd.dk> <199705300624.IAA03466@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Sat, 31 May 1997 10:51:02 -0500 To: Sascha Blank From: Richard Wackerbarth Subject: CTM - "He's back" Cc: =?iso-8859-1?Q?S=F8ren?= Schmidt , chuckr@glue.umd.edu (Chuck Robey), gpalmer@FreeBSD.ORG, freebsd-current@freefall.FreeBSD.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA27169 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm here and operations are restored. I am generating updates at this very moment. Expect them to go out in the next few hours. (Now for the thousands of e-mail messages) At 7:53 AM -0500 5/30/97, Sascha Blank wrote: >>>>>> "Søren" == Søren Schmidt writes: > > Søren> But your problems wont end there :( > > Søren> It seems the CTM generation has halted, >First of all to stand up for Richard: About a week ago ... let his >machines run without his personal administration. First let me thank Sascha for stepping up in my absence. It is always nice to know that we can make this a collective effort. I had to leave hurriedly and had time to get off only a brief message or two. I chose to send the message privately to Sascha rather than disturb everyone unnecessarily. Had I returned 48 hours sooner, I doubt that anyone would have particularly missed me. > Søren> I think we should try find CTM a new home, it has been much > Søren> to unreliable lately. What does it take ?? a few gigs of disk > Søren> and a machine with resonable connectivity ?? > >Søren, I think you are blaming the wrong guy. Since Richard has taken >over the CTM production it is working like a charm Until last Thursday. My machine locked up and did not automatically reboot. :-( If I had been around, it would not have been such a problem. >Therefore we should consider changing something about the >distribition, not the generation. >I known from past discussions with Richard that has wants >these problems to be solved as soon as anybody else does. The distribution problem is my greatest headache at the moment. As Sascha noted, we bypass freebsd.org to assure that someone outside my site gets them so the rest of you can find them. Recently, ftp.freebsd.org has now started rejecting the updates with a mailer error there, however, that is another problem. As for the generation of the updates, I previously suggested that reliance on a single machine is a weak point and that I would welcome letting someone else participate. So far, there have been no volunteers. I have even thought out a scheme that would allow us to have a redundant generation scheme. If someone has the diskspace and the willingness, I will gladly work out details with them so that it will require a double failure before you see more than a minor blip in the generation. From owner-freebsd-current Sat May 31 09:21:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA27594 for current-outgoing; Sat, 31 May 1997 09:21:30 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA27589 for ; Sat, 31 May 1997 09:21:27 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA23869 for freebsd-current@freefall.FreeBSD.org; Sat, 31 May 1997 18:20:55 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id SAA06499; Sat, 31 May 1997 18:01:16 +0200 (MET DST) Message-ID: <19970531180113.RA12588@uriah.heep.sax.de> Date: Sat, 31 May 1997 18:01:13 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freefall.FreeBSD.org Subject: Re: ctm References: <199705300624.IAA03466@sos.freebsd.dk> <199705301253.OAA04727@sliphost37.uni-trier.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199705301253.OAA04727@sliphost37.uni-trier.de>; from Sascha Blank on May 30, 1997 14:53:43 +0200 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Sascha Blank wrote: > The "dissolvance" of the dataplex.net domain origins from another > phenomenon. I did a traceroute to his site (208.2.87.3 if you want to > try for yourself), and this is what I've got: ... > 10 2-sprint-nap.internetmci.net (192.157.69.48) 180 ms 168 ms 148 ms > 11 core2-hssi2-0.WestOrange.mci.net (204.70.1.49) 164 ms 172 ms 156 ms > 12 core2.Dallas.mci.net (204.70.4.69) 227 ms 246 ms 219 ms > 13 border6-fddi-0.Dallas.mci.net (204.70.114.66) 203 ms 215 ms 219 ms > 14 amicus-networks.Dallas.mci.net (204.70.147.70) 207 ms * 211 ms > 15 10.1.1.3 (10.1.1.3) 230 ms 187 ms 187 ms 10.1.1.3 is a `private' network. You should never see such an address in public. Something is broken there. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat May 31 09:21:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA27633 for current-outgoing; Sat, 31 May 1997 09:21:41 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA27615 for ; Sat, 31 May 1997 09:21:37 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA23873 for freebsd-current@freefall.FreeBSD.org; Sat, 31 May 1997 18:21:29 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id SAA13607; Sat, 31 May 1997 18:07:19 +0200 (MET DST) Message-ID: <19970531180718.HX14681@uriah.heep.sax.de> Date: Sat, 31 May 1997 18:07:18 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freefall.FreeBSD.org Subject: Re: ctm References: <199705301416.QAA04273@sos.freebsd.dk> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Chuck Robey on May 30, 1997 11:39:11 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Chuck Robey wrote: > Soren, I would like to be able to fall back to cvsup, because when my > connectivity is good, it would do it, but I don't know any reliable > method of getting back to ctm, without requiring me to download one of > the "A" deltas. The only reliable method is to CVSup from the CTM master site again, before switching back to CTM. This would update your .ctm_status file to the exact status of the master site. I once tried to convince Richard into providing a CVSup server (and be it only for registered people, exactly for this purpose), but it seems he feared the effort. (Well, he probably doesn't know it takes as few as 15 minutes to get it up & running... ;-) If people are disciplined enough to not abuse this service, but only use it for the final catchup before switching back to CTM, this shouldn't cause any notable load on Richard's machine. An alternative could it be if Sascha's machine would provide this service, although the latency is a little higher then (since he has to extract the CTM deltas first). I did it by CVSupping from Richard's feed (cvsup5.freebsd.org), around the time he's doing it, but there's still a probability that a few files will be different in the end. The worst part of this game is switching from CTM to CVSup, btw. The CTM delta format doesn't provide for a timestamp field, but CVSup primarily relies on the timestamp. I've once contemplated to extend the CTM delta format, but never got to implement it. If i'm not totally mistaken, this addition could be transparent to people using old CTM client software (they would simply ignore the additional field). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat May 31 09:52:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA29005 for current-outgoing; Sat, 31 May 1997 09:52:06 -0700 (PDT) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28999 for ; Sat, 31 May 1997 09:52:03 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id TAA19477 for current@freebsd.org; Sat, 31 May 1997 19:51:38 +0300 (EET DST) From: mika ruohotie Message-Id: <199705311651.TAA19477@shadows.aeon.net> Subject: Re: old libs in /usr/lib In-Reply-To: <199705311213.WAA00331@labs.usn.blaze.net.au> from David Nugent at "May 31, 97 10:13:40 pm" To: current@freebsd.org Date: Sat, 31 May 1997 19:51:38 +0300 (EET DST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > May 30 12:02:35 shadows sshd[24622]: login_getclass: unknown class '00^B' > Get the latest ssh port and recompile/reinstall it. The login.conf API > changed to confirm to BSDI's latest. The above error is benign, but it's latest, i always recompile/install ssh after makeworld/kernelupdate, ofcourse, this time i think it was my /etc/login.conf oopsie. =) (at least it's bit different from the one in /usr/src/etc, i'll make world today, so i'll see if it gets all fixed...) > David mickey From owner-freebsd-current Sat May 31 09:52:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA29068 for current-outgoing; Sat, 31 May 1997 09:52:35 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA29059 for ; Sat, 31 May 1997 09:52:32 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA24526 for freebsd-current@freefall.FreeBSD.org; Sat, 31 May 1997 18:52:27 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id SAA22119; Sat, 31 May 1997 18:24:05 +0200 (MET DST) Message-ID: <19970531182404.ES51927@uriah.heep.sax.de> Date: Sat, 31 May 1997 18:24:04 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freefall.FreeBSD.org Subject: Re: if.h inclusion of References: <199705301551.LAA01946@khavrinen.lcs.mit.edu> <199705301601.SAA19086@gil.physik.rwth-aachen.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199705301601.SAA19086@gil.physik.rwth-aachen.de>; from Christoph Kukulies on May 30, 1997 18:00:59 +0200 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Christoph Kukulies wrote: > > Then bisdn should properly include like every other > > client of does. The former is a prerequisite for the > > latter. > > OK, Hellmuth, Gary, have you read this? BISDN does. It's only that we can't emit updated BISDN releases, as you know. It's already cleaned up in the BISDN CVS tree. It's however tangled inside some #ifdef spagghetti currently, and needs further cleanup. #if defined(__NetBSD__) || defined(__OpenBSD__) #include #include #include #endif #if defined(__FreeBSD__) && __FreeBSD__>=3 #include #endif #include That's horrible. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat May 31 10:18:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA29777 for current-outgoing; Sat, 31 May 1997 10:18:33 -0700 (PDT) Received: from wlk.com (news.wlk.com [192.86.83.250]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA29772 for ; Sat, 31 May 1997 10:18:30 -0700 (PDT) Received: from SMTPdaemon by wlk.com (smail3.2) with SMTPL id m0wXrnQ-0009rDC; Sat, 31 May 1997 12:18:28 -0500 (CDT) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id TAA05303; Sat, 31 May 1997 19:14:54 +0200 (CEST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@freefall.FreeBSD.org From: Poul-Henning Kamp Subject: Re: ctm In-reply-to: Your message of "Sat, 31 May 1997 18:01:13 +0200." <19970531180113.RA12588@uriah.heep.sax.de> Date: Sat, 31 May 1997 19:14:53 +0200 Message-ID: <5301.865098893@critter.dk.tfs.com> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <19970531180113.RA12588@uriah.heep.sax.de>, J Wunsch writes: >As Sascha Blank wrote: > >> The "dissolvance" of the dataplex.net domain origins from another >> phenomenon. I did a traceroute to his site (208.2.87.3 if you want to >> try for yourself), and this is what I've got: > >... >> 10 2-sprint-nap.internetmci.net (192.157.69.48) 180 ms 168 ms 148 ms >> 11 core2-hssi2-0.WestOrange.mci.net (204.70.1.49) 164 ms 172 ms 156 ms >> 12 core2.Dallas.mci.net (204.70.4.69) 227 ms 246 ms 219 ms >> 13 border6-fddi-0.Dallas.mci.net (204.70.114.66) 203 ms 215 ms 219 ms >> 14 amicus-networks.Dallas.mci.net (204.70.147.70) 207 ms * 211 ms >> 15 10.1.1.3 (10.1.1.3) 230 ms 187 ms 187 ms > >10.1.1.3 is a `private' network. You should never see such an address >in public. Something is broken there. Indeed, I have 195.8.137/24 blackholing between Telia and CRL at mae-east :-( -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Sat May 31 10:42:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA00831 for current-outgoing; Sat, 31 May 1997 10:42:15 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA00821 for ; Sat, 31 May 1997 10:41:52 -0700 (PDT) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id MAA03753; Sat, 31 May 1997 12:40:43 -0500 (CDT) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <19970531180718.HX14681@uriah.heep.sax.de> References: ; from Chuck Robey on May 30, 1997 11:39:11 -0400 <199705301416.QAA04273@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 31 May 1997 12:10:57 -0500 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) From: Richard Wackerbarth Subject: Re: ctm Cc: freebsd-current@freefall.FreeBSD.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 11:07 AM -0500 5/31/97, J Wunsch wrote: >I once tried to convince Richard into providing a CVSup server (and be >it only for registered people, exactly for this purpose), but it seems >he feared the effort. > (Well, he probably doesn't know it takes as few as 15 minutes to get it >up & running... ;-) That was not my previous experience in upgrading. Remember that I am rather conservative on machines which are "mission-critical" (such as supplying CTM feeds). I have not yet switched from 2.1.x. Unfortunately, the "developers" and "porters" are interested in supporting only "-current". As a result, it often takes additional work to make changes on the older setups. If you will supply the necessary config files and pointers to appropriate binaries for my configuration, I'll give it a try. (I still worry about the "abuse" issue, but that is another topic) >The worst part of this game is switching from CTM to CVSup, btw. The >CTM delta format doesn't provide for a timestamp field, but CVSup >primarily relies on the timestamp. > I've once contemplated to extend the CTM delta format, but never got to >implement it. Poul and I once discussed this. There is a slight conflict in the desired behaviour depending on whether you are moving CVS files or plain source files. There is the additional problem that the multiple CVSup feeds are not consistent within themselves. As a result, it is most difficult for CTM to match all of them. I'm certainly willing to discuss the subject. From owner-freebsd-current Sat May 31 10:54:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01328 for current-outgoing; Sat, 31 May 1997 10:54:59 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA01310; Sat, 31 May 1997 10:54:46 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id KAA26155; Sat, 31 May 1997 10:54:40 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id SAA00571; Sat, 31 May 1997 18:45:33 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 31 May 1997 12:52:28 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199705301253.OAA04727@sliphost37.uni-trier.de> References: <199705300624.IAA03466@sos.freebsd.dk> <199705300624.IAA03466@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Sat, 31 May 1997 12:49:24 +0100 To: Sascha Blank , =?iso-8859-1?Q?S=F8ren?= Schmidt From: Bob Bishop Subject: Re: ctm Cc: chuckr@glue.umd.edu (Chuck Robey), gpalmer@FreeBSD.ORG, freebsd-current@freefall.FreeBSD.org, postmaster@FreeBSD.ORG Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA01312 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 13:53 +0100 30/5/97, Sascha Blank wrote: >>>>>> "Søren" == Søren Schmidt writes: >[...] >The "dissolvance" of the dataplex.net domain origins from another >phenomenon. I did a traceroute to his site (208.2.87.3 if you want to >try for yourself), and this is what I've got: > > 1 Cisco (136.199.8.33) 4 ms 0 ms 4 ms > 2 LanWanGate (136.199.224.2) 4 ms 4 ms 4 ms > 3 XLink (136.199.1.41) 12 ms 12 ms 8 ms > 4 WAN-Trier-Saarbruecken.novocomp.de (194.120.166.2) 23 ms 16 ms 20 ms > 5 kbs.core.xlink.net (194.122.226.2) 31 ms 23 ms 35 ms > 6 karlsruhe.core.xlink.net (194.122.227.85) 20 ms 35 ms 23 ms > 7 frankfurt.core.xlink.net (194.122.225.42) 16 ms 66 ms 39 ms > 8 Vienna2.VA.US.EU.net (134.222.19.1) 148 ms 156 ms 164 ms > 9 Pennsauken1.NJ.US.EU.net (134.222.228.2) 156 ms 160 ms 164 ms >10 2-sprint-nap.internetmci.net (192.157.69.48) 180 ms 168 ms 148 ms >11 core2-hssi2-0.WestOrange.mci.net (204.70.1.49) 164 ms 172 ms 156 ms >12 core2.Dallas.mci.net (204.70.4.69) 227 ms 246 ms 219 ms >13 border6-fddi-0.Dallas.mci.net (204.70.114.66) 203 ms 215 ms 219 ms >14 amicus-networks.Dallas.mci.net (204.70.147.70) 207 ms * 211 ms >15 10.1.1.3 (10.1.1.3) 230 ms 187 ms 187 ms Eeek! Noone should be advertising a route to 10.x.x.x (see RFC1918). Try shouting at mci.net -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Sat May 31 10:56:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01409 for current-outgoing; Sat, 31 May 1997 10:56:17 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA01404 for ; Sat, 31 May 1997 10:56:14 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id NAA08241; Sat, 31 May 1997 13:56:02 -0400 (EDT) Date: Sat, 31 May 1997 13:56:02 -0400 (EDT) From: Garrett Wollman Message-Id: <199705311756.NAA08241@khavrinen.lcs.mit.edu> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@freefall.FreeBSD.org Subject: Re: if.h inclusion of In-Reply-To: <19970531182404.ES51927@uriah.heep.sax.de> References: <199705301551.LAA01946@khavrinen.lcs.mit.edu> <199705301601.SAA19086@gil.physik.rwth-aachen.de> <19970531182404.ES51927@uriah.heep.sax.de> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < As Christoph Kukulies wrote: >> > Then bisdn should properly include like every other >> > client of does. The former is a prerequisite for the >> > latter. >> >> OK, Hellmuth, Gary, have you read this? > BISDN does. It's only that we can't emit updated BISDN releases, as > you know. It's already cleaned up in the BISDN CVS tree. > It's however tangled inside some #ifdef spagghetti currently, and > needs further cleanup. > #if defined(__NetBSD__) || defined(__OpenBSD__) > #include > #include > #include > #endif > #if defined(__FreeBSD__) && __FreeBSD__>=3 > #include > #endif > #include > That's horrible. There is no reason for the include of to be conditional. -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 From owner-freebsd-current Sat May 31 11:21:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA02359 for current-outgoing; Sat, 31 May 1997 11:21:52 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA02354 for ; Sat, 31 May 1997 11:21:47 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA26577; Sat, 31 May 1997 20:21:46 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id UAA28693; Sat, 31 May 1997 20:04:07 +0200 (MET DST) Message-ID: <19970531200407.XL30177@uriah.heep.sax.de> Date: Sat, 31 May 1997 20:04:07 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freefall.FreeBSD.org Cc: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: ctm References: ; <199705301416.QAA04273@sos.freebsd.dk> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Richard Wackerbarth on May 31, 1997 12:10:57 -0500 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Richard Wackerbarth wrote: > >I once tried to convince Richard into providing a CVSup server (and be > >it only for registered people, exactly for this purpose), but it seems > >he feared the effort. > > > (Well, he probably doesn't know it takes as few as 15 minutes to get it > >up & running... ;-) > That was not my previous experience in upgrading. I didn't tell anything about upgrading -- only about installing a cvsupd. Both are two very different pairs of shoes. cvsupd is available as a statically-linked binary, even the {Net,Open}BSD folks reported that they can run the CVSup binaries (although the clients in this case). > > I've once contemplated to extend the CTM delta format, but never got to > >implement it. > Poul and I once discussed this. There is a slight conflict in the desired > behaviour depending on whether you are moving CVS files or plain source > files. There is the additional problem that the multiple CVSup feeds are > not consistent within themselves. As a result, it is most difficult for CTM > to match all of them. Huh? Since CVSup touches the files to the correct timestamp, how can the CVSup servers differ? (If the timestamps don't match, it falls back to compare the files.) Of course, i only talk about CVS files here. I have no idea for the checked out trees. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat May 31 11:25:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA02523 for current-outgoing; Sat, 31 May 1997 11:25:31 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA02518 for ; Sat, 31 May 1997 11:25:21 -0700 (PDT) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id NAA08394; Sat, 31 May 1997 13:24:34 -0500 (CDT) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: References: <199705301253.OAA04727@sliphost37.uni-trier.de> <199705300624.IAA03466@sos.freebsd.dk> <199705300624.IAA03466@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 31 May 1997 13:23:46 -0500 To: Bob Bishop From: Richard Wackerbarth Subject: Re: ctm Cc: freebsd-current@freefall.FreeBSD.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 6:49 AM -0500 5/31/97, Bob Bishop wrote: >>14 amicus-networks.Dallas.mci.net (204.70.147.70) 207 ms * 211 ms >>15 10.1.1.3 (10.1.1.3) 230 ms 187 ms 187 ms > >Eeek! Noone should be advertising a route to 10.x.x.x (see RFC1918). Try >shouting at mci.net Who says that they are advertising a route to 10.x.x.x? The advertised route is to 208.2.87.x Traceroute is getting identification of intermediate routers which happen to be on a private network. They cannot be addressed from the outside. I do not believe that this violates RFC1918. From owner-freebsd-current Sat May 31 11:52:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA03652 for current-outgoing; Sat, 31 May 1997 11:52:00 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA03645 for ; Sat, 31 May 1997 11:51:57 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA26809 for freebsd-current@freefall.FreeBSD.org; Sat, 31 May 1997 20:51:55 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id UAA28827; Sat, 31 May 1997 20:30:37 +0200 (MET DST) Message-ID: <19970531203037.IM15621@uriah.heep.sax.de> Date: Sat, 31 May 1997 20:30:37 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freefall.FreeBSD.org Subject: Re: if.h inclusion of References: <199705301551.LAA01946@khavrinen.lcs.mit.edu> <199705301601.SAA19086@gil.physik.rwth-aachen.de> <19970531182404.ES51927@uriah.heep.sax.de> <199705311756.NAA08241@khavrinen.lcs.mit.edu> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199705311756.NAA08241@khavrinen.lcs.mit.edu>; from Garrett Wollman on May 31, 1997 13:56:02 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Garrett Wollman wrote: > > #if defined(__FreeBSD__) && __FreeBSD__>=3 > > #include > > #endif > > #include > > > That's horrible. > > There is no reason for the include of to be > conditional. Yep. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat May 31 12:42:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA08955 for current-outgoing; Sat, 31 May 1997 12:42:00 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA08921 for ; Sat, 31 May 1997 12:41:54 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (8.8.5/8.8.5) with ESMTP id PAA24695; Sat, 31 May 1997 15:41:52 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPN/970116) with ESMTP id PAA20949; Sat, 31 May 1997 15:41:52 -0400 (EDT) To: Bob Bishop cc: freebsd-current@freefall.FreeBSD.org From: "Gary Palmer" Subject: Re: ctm In-reply-to: Your message of "Sat, 31 May 1997 12:49:24 BST." Date: Sat, 31 May 1997 15:41:52 -0400 Message-ID: <20947.865107712@orion.webspan.net> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bob Bishop wrote in message ID : > >15 10.1.1.3 (10.1.1.3) 230 ms 187 ms 187 ms > Eeek! Noone should be advertising a route to 10.x.x.x (see RFC1918). Try > shouting at mci.net I doubt that they are advertising it, just using it internally. You do not need to advertise net10 through BGP to return it as a hop in a traceroute... IMHO, net 10 (and the other 1918 networks) should NOT be visable at all from the rest of the 'net, not even to traceroute. Unfortunately, I've been told that a combination of the NIC being extremely miserly with new IP allocations, and security problems in router/terminal server software is causing more and more systems to be put into RFC1918 address space. The implications are interesting ... I filter my inbound lines to remove illegal src IP addresses (like the 1918 addresses). So what happens when one of those systems on a reserved network sends a reply to path MTU discovery that the packet needs to be fragmented? Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Sat May 31 13:36:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA11378 for current-outgoing; Sat, 31 May 1997 13:36:31 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.138]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11370 for ; Sat, 31 May 1997 13:36:27 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.5/8.7.3) id PAA08576; Sat, 31 May 1997 15:33:33 -0500 (CDT) Message-ID: <19970531153332.35352@peeper.my.domain> Date: Sat, 31 May 1997 15:33:33 -0500 From: Tom Jackson To: Richard Wackerbarth Cc: FreeBSD Current Subject: Re: src-cur.2896.gz References: <19970525115421.42464@xaa.stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74e In-Reply-To: ; from Richard Wackerbarth on Sat, May 31, 1997 at 11:03:24AM -0500 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, May 31, 1997 at 11:03:24AM -0500, Richard Wackerbarth wrote: > At 3:33 PM -0500 5/25/97, Tom Jackson wrote: > > >Strange as this may seem, go to ftp.uni-trier.de/pub/unix/FreeBSD/CTM/src-cur > >and you will find the missing delta there. Go figure, Germany has it but > >California doesn't. > > Sascha Blank is in Germany and interested in maintaining CTM service. We > bypass California for his service. > The California-based FreeBSD mailing list operation is the source of your > problem. > (Also, you are probably losing quite a bit of mail that you don't notice > because it lacks sequence numbers) They are aware of the problem. I hope > that they are able to restore reliability soon. > > I agree with you. There was some discussion about your domain going out of existence also :) Sascha mentioned trying to get a ftp mirror to accept the direct ctm delta such as trier. I don't know the mechanism to accomplish this but I would suggest neosoft as an excellent site if they would take it. btw, I got ctm2904 through the mails today. There's still hope. -- Tom Jackson I'm ProChoice->FreeBSD toj@gorilla.net http://www.freebsd.org http://tulsix.utulsa.edu/~tjackson "Out in the Ozone Again" From owner-freebsd-current Sat May 31 13:53:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA12098 for current-outgoing; Sat, 31 May 1997 13:53:21 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA12083 for ; Sat, 31 May 1997 13:53:12 -0700 (PDT) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id PAA12231; Sat, 31 May 1997 15:52:54 -0500 (CDT) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <19970531153332.35352@peeper.my.domain> References: ; from Richard Wackerbarth on Sat, May 31, 1997 at 11:03:24AM -0500 <19970525115421.42464@xaa.stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 31 May 1997 15:52:46 -0500 To: Tom Jackson From: Richard Wackerbarth Subject: Re: src-cur.2896.gz Cc: FreeBSD Current Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 3:33 PM -0500 5/31/97, Tom Jackson wrote: >There was some discussion about your domain going out of existence also :) Did the domain go out of existance or just a particular host? On Thursday, my main machine locked up the SCSI controller and did not automatically reboot. Even though it is the primary DNS server, the secondary server SHOULD have retained its tables for 2 weeks and provided the service. >Sascha mentioned trying to get a ftp mirror to accept the direct ctm delta >such as trier. I don't know the mechanism to accomplish this but I would >suggest neosoft as an excellent site if they would take it. We are setting up a network of sites. To avoid overloading my pipe, I would like to limit it to a handful of sites strategically located around the world. I had expected to use ftp.freebsd.org as the primary US site. However, it seems to have quite a few problems. (All since they started switching to 2.2, I might add) Perhaps I need an alternate. Anyone willing should contact Sascha since he has it all set up there and is coordinating everything. >btw, I got ctm2904 through the mails today. There's still hope. The FreeBSD mail system is not out of service. It is just highly unpredictable. I am reviewing the files available on ftp.freebsd.org and uploading missing ones to /incoming I'll then get Jordan to install them in their normal location. From owner-freebsd-current Sat May 31 13:56:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA12358 for current-outgoing; Sat, 31 May 1997 13:56:10 -0700 (PDT) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA12353 for ; Sat, 31 May 1997 13:56:07 -0700 (PDT) Received: from walkabout.asstdc.com.au (walkabout.asstdc.com.au [202.12.127.73]) by asstdc.scgt.oz.au (8.8.5/BSD4.4) with SMTP id GAA28688 Sun, 1 Jun 1997 06:55:55 +1000 (EST) Message-Id: <3.0.1.32.19970601065555.006cc364@localhost> X-Sender: imb@localhost X-Mailer: Windows Eudora Light Version 3.0.1 (32) Date: Sun, 01 Jun 1997 06:55:55 +1000 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-current@freefall.FreeBSD.org From: michael butler Subject: Re: ctm In-Reply-To: <19970531180113.RA12588@uriah.heep.sax.de> References: <199705301253.OAA04727@sliphost37.uni-trier.de> <199705300624.IAA03466@sos.freebsd.dk> <199705301253.OAA04727@sliphost37.uni-trier.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> 13 border6-fddi-0.Dallas.mci.net (204.70.114.66) 203 ms 215 ms 219 ms >> 14 amicus-networks.Dallas.mci.net (204.70.147.70) 207 ms * 211 ms >> 15 10.1.1.3 (10.1.1.3) 230 ms 187 ms 187 ms >10.1.1.3 is a `private' network. You should never see such an address >in public. Something is broken there. It is, however, quite valid and useful to address intermediary routers with numbers chosen from these private networks .. so long as their administrator can still reach them :-) It has the (significant) advantage of guaranteeing that no-one else can play with your gear. With address space being harder and harder to get, using private (sub)nets in this way can save you *lots* of numbers for hosts that really need global access, michael From owner-freebsd-current Sat May 31 14:09:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA12889 for current-outgoing; Sat, 31 May 1997 14:09:55 -0700 (PDT) Received: from sliphost37.uni-trier.de (blank@sliphost37.uni-trier.de [136.199.240.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA12879 for ; Sat, 31 May 1997 14:09:49 -0700 (PDT) Received: (from blank@localhost) by sliphost37.uni-trier.de (8.8.5/8.8.5) id XAA02312 for current@freebsd.org; Sat, 31 May 1997 23:09:41 +0200 (CEST) From: Sascha Blank Message-Id: <199705312109.XAA02312@sliphost37.uni-trier.de> Subject: Re: ctm In-Reply-To: <19970531180718.HX14681@uriah.heep.sax.de> from J Wunsch at "May 31, 97 06:07:18 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 31 May 1997 23:03:21 +0200 (CEST) Reply-To: blank@fox.uni-trier.de (Sascha Blank) X-System: FreeBSD 2.2-STABLE X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch has written recently: > The only reliable method is to CVSup from the CTM master site again, > before switching back to CTM. This would update your .ctm_status file > to the exact status of the master site. > > I once tried to convince Richard into providing a CVSup server (and be > it only for registered people, exactly for this purpose), but it seems > he feared the effort. (Well, he probably doesn't know it takes as few > as 15 minutes to get it up & running... ;-) If people are disciplined > enough to not abuse this service, but only use it for the final > catchup before switching back to CTM, this shouldn't cause any notable > load on Richard's machine. You can neglect the time it takes to unpack and apply the deltas. As soon as the filter gets hold of a delta, ctm_rmail takes over and does the rest. I'm already doing this on the fly to update my ports-cur and src-cur repository on our ftp server, and even though the server is usually heavily loaded and the 9GB disks aren't the fastest ones, it often takes less than a minute or two. > An alternative could it be if Sascha's machine would provide this > service, although the latency is a little higher then (since he has to > extract the CTM deltas first). The idea does not sound bad. We're already serving as a (unoffical) sup server (mostly for NetBSD), so setting up a cvsup server shouldn't be to complicated. In case I can find an entirely statically linked version of CVSup 15 that will work on BSDI 2.1 and 3.0, I would be willing to do a little testing (I once fought against the M3 compiler and do not want to do it again, especially on a machine that has no ports collection). But you shouldn't forget even with such a CVSup server I'm still relying entirely on Richard's server. The moment _his_ server fails for any reason _my_ server will be useless as well. The past incident made this very clear. -- Sascha Blank - mailto:blank@fox.uni-trier.de Student and System Administrator at the University of Trier, Germany Finger my account to receive my Public PGP key I don't speak for my employers, they don't pay me enough for that. From owner-freebsd-current Sat May 31 14:15:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA13506 for current-outgoing; Sat, 31 May 1997 14:15:48 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA13501 for ; Sat, 31 May 1997 14:15:46 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id OAA14280 for ; Sat, 31 May 1997 14:16:12 -0700 (PDT) To: current@freebsd.org Subject: Kernel build failure in -current Date: Sat, 31 May 1997 14:16:12 -0700 Message-ID: <14277.865113372@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ===> lkm/pcic cc -O2 -pipe -DLKM -I. -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/pcic/. ./../sys -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -DPSEUDO_LKM -c /usr/ src/lkm/pcic/../../sys/pccard/pcic.c /usr/src/lkm/pcic/../../sys/pccard/pcic.c: In function `pcic_unload': /usr/src/lkm/pcic/../../sys/pccard/pcic.c:316: warning: implicit declaration of function `unregister_intr' /usr/src/lkm/pcic/../../sys/pccard/pcic.c: In function `build_freelist': /usr/src/lkm/pcic/../../sys/pccard/pcic.c:368: warning: implicit declaration of function `register_intr' /usr/src/lkm/pcic/../../sys/pccard/pcic.c: In function `pcic_probe': /usr/src/lkm/pcic/../../sys/pccard/pcic.c:792: `SWI_MASK' undeclared (first use this function) /usr/src/lkm/pcic/../../sys/pccard/pcic.c:792: (Each undeclared identifier is re ported only once /usr/src/lkm/pcic/../../sys/pccard/pcic.c:792: for each function it appears in.) *** Error code 1 From owner-freebsd-current Sat May 31 15:18:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA19446 for current-outgoing; Sat, 31 May 1997 15:18:04 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA19441 for ; Sat, 31 May 1997 15:18:01 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id QAA06856; Sat, 31 May 1997 16:17:56 -0600 (MDT) Message-Id: <199705312217.QAA06856@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: Kernel build failure in -current In-reply-to: Your message of "Sat, 31 May 1997 14:16:12 PDT." <14277.865113372@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 May 1997 16:17:56 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > ===> lkm/pcic > cc -O2 -pipe -DLKM -I. -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/pcic/. > ./../sys -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -DPSEUDO_LKM -c /usr/ > src/lkm/pcic/../../sys/pccard/pcic.c > /usr/src/lkm/pcic/../../sys/pccard/pcic.c: In function `pcic_unload': > /usr/src/lkm/pcic/../../sys/pccard/pcic.c:316: warning: implicit declaration of ... rerun config, I had a different but similar set of errors earlier today. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Sat May 31 15:19:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA19628 for current-outgoing; Sat, 31 May 1997 15:19:51 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA19613 for ; Sat, 31 May 1997 15:19:47 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id QAA06864; Sat, 31 May 1997 16:19:42 -0600 (MDT) Message-Id: <199705312219.QAA06864@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: Kernel build failure in -current In-reply-to: Your message of "Sat, 31 May 1997 14:16:12 PDT." <14277.865113372@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 May 1997 16:19:42 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, >rerun config, I had a different but similar set of errors earlier today. oops, that was a stupid thing to say... this was make world, not kernel. sorry... -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Sat May 31 15:38:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA20448 for current-outgoing; Sat, 31 May 1997 15:38:02 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA20436 for ; Sat, 31 May 1997 15:37:59 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (8.8.5/8.8.5) with ESMTP id SAA15483; Sat, 31 May 1997 18:37:58 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPN/970116) with ESMTP id SAA17103; Sat, 31 May 1997 18:37:57 -0400 (EDT) To: michael butler cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-current@freefall.FreeBSD.org From: "Gary Palmer" Subject: Re: ctm In-reply-to: Your message of "Sun, 01 Jun 1997 06:55:55 +1000." <3.0.1.32.19970601065555.006cc364@localhost> Date: Sat, 31 May 1997 18:37:57 -0400 Message-ID: <17101.865118277@orion.webspan.net> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk michael butler wrote in message ID <3.0.1.32.19970601065555.006cc364@localhost>: > It is, however, quite valid and useful to address intermediary > routers with numbers chosen from these private networks .. so long > as their administrator can still reach them :-) It has the > (significant) advantage of guaranteeing that no-one else can play > with your gear. With address space being harder and harder to get, > using private (sub)nets in this way can save you *lots* of numbers > for hosts that really need global access, As I have said in other e-mail, it can also lead to problems. Lets say you put your terminal server into net10. You then have a PPP customer negotiate a connection with a MTU << 1500. They then go to a WWW page on a FreeBSD box with a concencious (sp?) admin that blocks RFC1918 addresses on inbound links. Path MTU discovery will fail, as will the users attempt to view the WWW page. So just be careful what you put in reserved networks. Devices which are liable to have to frag packets (e.g. terminal servers) should probably be kept in BGP routed space. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Sat May 31 15:51:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA21034 for current-outgoing; Sat, 31 May 1997 15:51:17 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA21029 for ; Sat, 31 May 1997 15:51:14 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id PAA14549; Sat, 31 May 1997 15:52:40 -0700 (PDT) Message-Id: <199705312252.PAA14549@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Richard Wackerbarth cc: Tom Jackson , FreeBSD Current Subject: Re: src-cur.2896.gz In-reply-to: Your message of "Sat, 31 May 1997 15:52:46 CDT." From: David Greenman Reply-To: dg@root.com Date: Sat, 31 May 1997 15:52:40 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >had expected >to use ftp.freebsd.org as the primary US site. However, it seems to have >quite a few problems. >(All since they started switching to 2.2, I might add) Perhaps I need an >alternate. What are you talking about, Richard? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Sat May 31 16:30:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22458 for current-outgoing; Sat, 31 May 1997 16:30:04 -0700 (PDT) Received: from mrynet.com (www.mrynet.com [206.154.101.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22424 for ; Sat, 31 May 1997 16:30:00 -0700 (PDT) Received: (from staylor@localhost) by mrynet.com (8.8.5/8.7.3) id QAA01776 for freebsd-current@freebsd.org; Sat, 31 May 1997 16:29:01 -0700 (PDT) Message-Id: <199705312329.QAA01776@mrynet.com> From: staylor@mrynet.com (Scott G. Akmentins-Taylor) Date: Sat, 31 May 1997 16:29:01 +0000 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-current@freebsd.org Subject: ucd-snmp-3.1.3 doesn't like FreeBSD3? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Gang- I may have missed something important, so feel free to flame--but PLEASE refer me to the pertinant info :) ucd-snmp-3.1.3 doesn't seem to go well with FreeBSD-CURRENT (aka FreeBSD3). As evidenced: [4:22pm] /iron/ports/net/ucd-snmp ttyp9:staylor@mrynet (20): make >> Checksum OK for ucd-snmp-3.1.3.tar.gz. ===> Building for ucd-snmp-3.1.3 for i in snmplib agent apps local ov man ; do ( cd $i ; make ) done cd extensible; make cc -I.. -I../snmplib -O -Dfreebsd3 -c snmp_vars.c In file included from snmp_vars.c:123: /usr/include/netinet/in_var.h:49: field `ia_ifa' has incomplete type In file included from snmp_vars.c:130: /usr/include/netinet/if_ether.h:90: field `ac_if' has incomplete type snmp_vars.c: In function `var_ifEntry': snmp_vars.c:1718: storage size of `ifnet' isn't known snmp_vars.c: In function `var_ipAddrEntry': snmp_vars.c:2481: storage size of `ifnet' isn't known snmp_vars.c:2481: storage size of `lowin_ifnet' isn't known snmp_vars.c: In function `Interface_Scan_Next': snmp_vars.c:3929: storage size of `ifnet' isn't known snmp_vars.c:3960: structure has no member named `ia_next' snmp_vars.c:3971: dereferencing pointer to incomplete type snmp_vars.c:3976: `saveifnet' has an incomplete type (ad nauseum...) Poking around, it appears that there is no definition for if_addrlist. Has convention changed for FreeBSD? Oversight, or recent buggie? Or suggestions? :) If anyone running -CURRENT has compiled this, please drop me a note. Thanks. -- Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com MRY Systems staylor@llyene.jpl.nasa.gov Westlake Village, CA USA (Skots Gregorijs Akmentins-Teilors -- just call me "Skots") ----- Labak miris neka sarkans ----- From owner-freebsd-current Sat May 31 17:04:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA24099 for current-outgoing; Sat, 31 May 1997 17:04:21 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA24094 for ; Sat, 31 May 1997 17:04:18 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (8.8.5/8.8.5) with ESMTP id UAA23996; Sat, 31 May 1997 20:04:16 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPN/970116) with ESMTP id UAA14373; Sat, 31 May 1997 20:04:16 -0400 (EDT) To: staylor@mrynet.com (Scott G. Akmentins-Taylor) cc: freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: ucd-snmp-3.1.3 doesn't like FreeBSD3? In-reply-to: Your message of "Sat, 31 May 1997 16:29:01 -0000." <199705312329.QAA01776@mrynet.com> Date: Sat, 31 May 1997 20:04:16 -0400 Message-ID: <14371.865123456@orion.webspan.net> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Scott G. Akmentins-Taylor wrote in message ID <199705312329.QAA01776@mrynet.com>: > Gang- > > I may have missed something important, so feel free to flame--but PLEASE > refer me to the pertinant info :) > > ucd-snmp-3.1.3 doesn't seem to go well with FreeBSD-CURRENT (aka FreeBSD3). I don't have a -current box to try it on. Sorry. (Together with the fact I don't really have time to track all the changes right now) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Sat May 31 17:10:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA24294 for current-outgoing; Sat, 31 May 1997 17:10:01 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA24265 for ; Sat, 31 May 1997 17:09:58 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id RAA06146; Sat, 31 May 1997 17:10:22 -0700 (PDT) To: Steve Passe cc: current@FreeBSD.ORG Subject: Re: Kernel build failure in -current In-reply-to: Your message of "Sat, 31 May 1997 16:17:56 MDT." <199705312217.QAA06856@Ilsa.StevesCafe.com> Date: Sat, 31 May 1997 17:10:22 -0700 Message-ID: <6143.865123822@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sorry, my subject line was incorrect - this is actually a failure in building the LKM, so updating config won't help. :-) Jordan > Hi, > > > ===> lkm/pcic > > cc -O2 -pipe -DLKM -I. -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/p cic/. > > ./../sys -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-ex terns > > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -DPSEUDO_LKM -c /usr/ > > src/lkm/pcic/../../sys/pccard/pcic.c > > /usr/src/lkm/pcic/../../sys/pccard/pcic.c: In function `pcic_unload': > > /usr/src/lkm/pcic/../../sys/pccard/pcic.c:316: warning: implicit declaratio n of > ... > > rerun config, I had a different but similar set of errors earlier today. > > -- > Steve Passe | powered by > smp@csn.net | Symmetric MultiProcessor FreeBSD > > From owner-freebsd-current Sat May 31 18:12:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA27059 for current-outgoing; Sat, 31 May 1997 18:12:36 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA27053; Sat, 31 May 1997 18:12:32 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id SAA06523; Sat, 31 May 1997 18:12:35 -0700 (PDT) Message-Id: <199706010112.SAA06523@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: "Gary Palmer" cc: staylor@mrynet.com (Scott G. Akmentins-Taylor), freebsd-current@FreeBSD.ORG Subject: Re: ucd-snmp-3.1.3 doesn't like FreeBSD3? In-reply-to: Your message of "Sat, 31 May 1997 20:04:16 EDT." <14371.865123456@orion.webspan.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 May 1997 18:12:35 -0700 From: Amancio Hasty Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If you want an account on my FreeBSD-current box just drop me a note 8) Actually, the real question is who is overlooking the network interfaces for tools such as snmp ? Cheers, Amancio >From The Desk Of "Gary Palmer" : > Scott G. Akmentins-Taylor wrote in message ID > <199705312329.QAA01776@mrynet.com>: > > Gang- > > > > I may have missed something important, so feel free to flame--but PLEASE > > refer me to the pertinant info :) > > > > ucd-snmp-3.1.3 doesn't seem to go well with FreeBSD-CURRENT (aka FreeBSD3). > > I don't have a -current box to try it on. Sorry. (Together with the > fact I don't really have time to track all the changes right now) > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Sat May 31 18:13:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA27148 for current-outgoing; Sat, 31 May 1997 18:13:59 -0700 (PDT) Received: from mail0.iij.ad.jp (mail0.iij.ad.jp [202.232.2.113]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA27143 for ; Sat, 31 May 1997 18:13:54 -0700 (PDT) Received: from uucp2.iij.ad.jp (uucp2.iij.ad.jp [202.232.2.202]) by mail0.iij.ad.jp (8.8.5+2.7Wbeta5/3.5Wpl4-MAIL) with SMTP id KAA24567; Sun, 1 Jun 1997 10:13:49 +0900 (JST) Received: (from uucp@localhost) by uucp2.iij.ad.jp (8.6.12+2.4W/3.3W9-UUCP) with UUCP id KAA08926; Sun, 1 Jun 1997 10:13:49 +0900 Received: from tyd1.tydfam.iijnet.or.jp (tyd1.tydfam.iijnet.or.jp [192.168.1.2]) by tydfam.iijnet.or.jp (8.8.5/3.4W2-uucp) with ESMTP id JAA27967; Sun, 1 Jun 1997 09:13:23 +0900 (JST) Received: from localhost.tydfam.iijnet.or.jp (localhost.tydfam.iijnet.or.jp [127.0.0.1]) by tyd1.tydfam.iijnet.or.jp (8.8.5/3.4Wnomx) with SMTP id JAA09456; Sun, 1 Jun 1997 09:13:23 +0900 (JST) Message-Id: <199706010013.JAA09456@tyd1.tydfam.iijnet.or.jp> X-Authentication-Warning: tyd1.tydfam.iijnet.or.jp: localhost.tydfam.iijnet.or.jp [127.0.0.1] didn't use HELO protocol To: tom@uniserve.com Cc: current@FreeBSD.ORG Subject: Re: Q) ddd-2.1 compile Reply-To: ken@tydfam.iijnet.or.jp In-Reply-To: Your message of "Fri, 30 May 1997 23:37:17 -0700 (PDT)" References: X-Mailer: Mew version 1.70 on Emacs 19.34.2 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 01 Jun 1997 09:13:22 +0900 From: Takeshi Yamada Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thank you for quick response. Actually, I ran as "root" using tcsh, and it was not supposed to be a reason of error. However, I tried it with other FreeBSD-current box and it went through without any problem. So, I think it is because of my setup problem. Thank you. tom> The user-id that used to compile this is limited on how much memory it tom> can use. Remember Unix was designed as a time-share system. See "man tom> login.conf" for a way to increase your limits, or just compile it as root. tom> tom> Tom tom> tom> From owner-freebsd-current Sat May 31 22:48:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA07670 for current-outgoing; Sat, 31 May 1997 22:48:24 -0700 (PDT) Received: from mail.MCESTATE.COM (mail.MCESTATE.COM [207.211.200.50]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA07664 for ; Sat, 31 May 1997 22:48:22 -0700 (PDT) Received: from localhost (vince@localhost) by mail.MCESTATE.COM (8.8.5/8.8.5) with SMTP id WAA05460 for ; Sat, 31 May 1997 22:48:19 -0700 (PDT) Date: Sat, 31 May 1997 22:48:19 -0700 (PDT) From: Vincent Poy To: current@FreeBSD.ORG Subject: -current build failed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk THanks to Jordan for fixing the pcicard lkm but it seems to fail here this time: ===> syscons ===> syscons/blank make: don't know how to make /usr/include/machine/spl.h. Stop *** Error code 2 Stop. *** Error code 1 Stop. root@mercury [10:46pm][/usr/src/lkm] >> Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-current Sat May 31 23:41:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA09442 for current-outgoing; Sat, 31 May 1997 23:41:44 -0700 (PDT) Received: from callisto.cids.org.za (callisto.cids.org.za [146.64.58.43]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA09437; Sat, 31 May 1997 23:41:33 -0700 (PDT) Received: from angel.cids.org.za (angel.cids.org.za [146.64.84.9]) by callisto.cids.org.za (8.8.5/8.8.5) with ESMTP id IAA27762; Sun, 1 Jun 1997 08:41:07 +0200 (SAT) Received: (from jhay@localhost) by angel.cids.org.za (8.8.5/8.8.5) id IAA05068; Sun, 1 Jun 1997 08:21:04 +0200 (SAT) From: John Hay Message-Id: <199706010621.IAA05068@angel.cids.org.za> Subject: Re: ucd-snmp-3.1.3 doesn't like FreeBSD3? In-Reply-To: <14371.865123456@orion.webspan.net> from Gary Palmer at "May 31, 97 08:04:16 pm" To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Sun, 1 Jun 1997 08:21:04 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well, I did send you a set of patches to make it work on FreeBSD 3.0-CURRENT and still work on 2.2. Should I send it again? I'm using it here on 2.2 and 3.0 machines, so I'm pretty sure it works. John -- John Hay > Scott G. Akmentins-Taylor wrote in message ID > <199705312329.QAA01776@mrynet.com>: > > Gang- > > > > I may have missed something important, so feel free to flame--but PLEASE > > refer me to the pertinant info :) > > > > ucd-snmp-3.1.3 doesn't seem to go well with FreeBSD-CURRENT (aka FreeBSD3). > > I don't have a -current box to try it on. Sorry. (Together with the > fact I don't really have time to track all the changes right now) > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info >