From owner-freebsd-stable Sun Oct 4 13:46:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24503 for freebsd-stable-outgoing; Sun, 4 Oct 1998 13:46:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24421 for ; Sun, 4 Oct 1998 13:46:34 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA00224; Sun, 4 Oct 1998 13:45:51 -0700 (PDT) Message-Id: <199810042045.NAA00224@implode.root.com> To: "Morgan Davis" cc: freebsd-stable@FreeBSD.ORG Subject: Re: KERNEL PANICS in 2.2.7-RELEASE server In-reply-to: Your message of "Thu, 01 Oct 1998 15:24:43 PDT." <003b01bded8a$499df3c0$b617a3cd@ctsd2.cts.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 04 Oct 1998 13:45:50 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The machine is a Pentium II 266MHz with 256MB RAM, and pumps out 2.5 MB/s >(that's mega_bytes_) via an Intel EtherExpress in 100BaseT mode. This >server was just upgraded from 2.2.6-RELEASE to 2.2.7-RELEASE (including a >newly built kernel based chiefly on GENERIC), and ever since it exhibits >these intermittent panics: > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x18 >fault code = supervisor write, page not present >instruction pointer = 0x8:0xf011e3d1 >stack pointer = 0x10:0xefbffe9c >frame pointer = 0x10:0xefbffec0 >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 = 501 (pnserver) >interrupt mask = >panic: page fault > >The panics seem to occur during periods of high activity after running for a >couple of hours. Otherwise, it appears to operate fine. Prior to the Intel >card, it was running an SMC Rev C (de driver) card that was even more >sensitive and paniced frequently. I'm considering reverting back to 2.2.6 >unless there is a known issue with 2.2.7-RELEASE that has been resolved >in -stable. Or maybe there is no some new kernel tweaks required in 2.2.7 >to avoid this? > >Any assistance is much appreciated. It would help a bunch if you could tell us what functions are around the instruction pointer above (f011e3d1)...use nm /kernel | sort | more. It kind of looks like you might be running out of mbuf clusters. You might try increasing them and see if it helps. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 4 17:52:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28072 for freebsd-stable-outgoing; Sun, 4 Oct 1998 17:52:34 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mh2.cts.com (mh2.cts.com [209.68.192.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28043 for ; Sun, 4 Oct 1998 17:52:23 -0700 (PDT) (envelope-from mdavis@cts.com) Received: from io.cts.com (io.cts.com [198.68.174.34]) by mh2.cts.com (8.8.7/8.8.5) with ESMTP id RAA07846; Sun, 4 Oct 1998 17:51:58 -0700 (PDT) Received: from ion (ion.cts.com [198.68.174.38]) by io.cts.com (8.8.8/8.8.8) with SMTP id RAA05886; Sun, 4 Oct 1998 17:51:57 -0700 (PDT) (envelope-from mdavis@cts.com) From: "Morgan Davis" To: Cc: Subject: RE: KERNEL PANICS in 2.2.7-RELEASE server Date: Sun, 4 Oct 1998 17:52:16 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 9.0, Build 4.71.2233.5 In-reply-to: <199810042045.NAA00224@implode.root.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0707.2700 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David: Below is a dump of the kernel symbols around that address per your request. Look like the offending function is _sosend. You may be right about mbuf clusters, as the kernel is simply GENERIC with all the non-essentials commented out. What kernel tweaks would you recommend to accomodate a high-bandwidth packet-passing system? It's an audio server that simply forwards encoded audio streams to potentially thousands of UDP and TCP client connections. It doesn't host users or do much else. I wonder if the tweaks we've used for some of our BSDI news servers would work. They use: maxusers 512 options "CHILD_MAX=512" options "OPEN_MAX=1024" options "NMBCLUSTERS=16384" options "TCBHASHSIZE=2048" options AHC_TAGENABLE --Morgan f011da70 t _sysctl___kern_somaxconn f011da98 t ___set_sysctl__kern_sym_sysctl___kern_somaxconn f011da9c T _socreate f011db8c T _sobind f011dbd8 T _solisten f011dc84 T _sofree f011dd50 T _soclose f011de70 T _soabort f011de98 T _soaccept f011df00 T _soconnect f011df88 T _soconnect2 f011dfd4 T _sodisconnect f011e040 T _sosend f011e700 T _soreceive f011f07c T _soshutdown f011f0b8 T _sorflush f011f184 T _sosetopt f011f44c T _sogetopt f011f690 T _sohasoutofband f011f6e0 F uipc_socket2.o f011f6e0 t _sysctl___kern_maxsockbuf f011f70c t ___set_sysctl__kern_sym_sysctl___kern_maxsockbuf > -----Original Message----- > From: root@implode.root.com [mailto:root@implode.root.com]On Behalf Of > David Greenman > Sent: Sunday, October 04, 1998 1:46 PM > To: Morgan Davis > Cc: freebsd-stable@FreeBSD.ORG > Subject: Re: KERNEL PANICS in 2.2.7-RELEASE server > > > >The machine is a Pentium II 266MHz with 256MB RAM, and pumps out 2.5 MB/s > >(that's mega_bytes_) via an Intel EtherExpress in 100BaseT mode. This > >server was just upgraded from 2.2.6-RELEASE to 2.2.7-RELEASE (including a > >newly built kernel based chiefly on GENERIC), and ever since it exhibits > >these intermittent panics: > > > >Fatal trap 12: page fault while in kernel mode > >fault virtual address = 0x18 > >fault code = supervisor write, page not present > >instruction pointer = 0x8:0xf011e3d1 > >stack pointer = 0x10:0xefbffe9c > >frame pointer = 0x10:0xefbffec0 > >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 = 501 (pnserver) > >interrupt mask = > >panic: page fault > > > >The panics seem to occur during periods of high activity after > running for a > >couple of hours. Otherwise, it appears to operate fine. Prior > to the Intel > >card, it was running an SMC Rev C (de driver) card that was even more > >sensitive and paniced frequently. I'm considering reverting > back to 2.2.6 > >unless there is a known issue with 2.2.7-RELEASE that has been resolved > >in -stable. Or maybe there is no some new kernel tweaks > required in 2.2.7 > >to avoid this? > > > >Any assistance is much appreciated. > > It would help a bunch if you could tell us what functions are around > the instruction pointer above (f011e3d1)...use nm /kernel | sort | more. > It kind of looks like you might be running out of mbuf clusters. You might > try increasing them and see if it helps. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 00:22:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22953 for freebsd-stable-outgoing; Mon, 5 Oct 1998 00:22:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [130.126.8.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22911 for ; Mon, 5 Oct 1998 00:21:54 -0700 (PDT) (envelope-from igor@alecto.physics.uiuc.edu) Received: (from igor@localhost) by alecto.physics.uiuc.edu (8.9.0/8.9.0) id CAA28629; Mon, 5 Oct 1998 02:21:32 -0500 (CDT) From: Igor Roshchin Message-Id: <199810050721.CAA28629@alecto.physics.uiuc.edu> Subject: -STABLE and vx driver To: stable@FreeBSD.ORG Date: Mon, 5 Oct 1998 02:21:31 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! On a P-II -300 with 128MB of memory I made an update (-stable of Sep. 19 or a few days earlier) from 2.2.5-Release. (or 2.2-stable shortly after 2.2.5-release) All update went smoothly, except, that the new compiled kernel doesn't recognize 3c905 card.. The generic kernel does. GENERIC: Oct 5 01:37:31 astra /kernel: vx0 <3 Oct 5 01:37:31 astra /kernel: COM 3C905 Fast Etherlink XL PCI> rev 0 int a irq 11 on pci0:12:0 Oct 5 01:37:31 astra /kernel: mii[*mii*] address 00:60:97:d1:52:35 Oct 5 01:37:31 astra /kernel: Probing for devices on PCI bus 1: compiled kernel: Oct 5 01:29:46 astra /kernel: pci0:12: Oct 5 01:29:46 astra /kernel: vendor=0x10b7, device=0x9050, class=network (ethe rnet) int a irq 11 [no driver assigned] The GENERIC kernel from 2.2.5-RELEASE was recognizeing it this way : (in the mean time I switched off the auto select option) Oct 4 23:44:53 astra /kernel.old: vx0 <3COM 3C905 Fast Etherlink XL PCI> rev 0 int a irq 11 on pci0:12 Oct 4 23:44:53 astra /kernel.old: mii[*mii*]: disable 'auto select' with DOS ut il! address 00:60:97:d1:52:35 I do have device vx0 in the kernel configuration. Any idea, what can be the problem ? Also, why doe the kernel (the upper output) splits the output into two lines (I mean : vx0<3 and then COM 3C905...) ? Thanks, IgoR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 00:34:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24324 for freebsd-stable-outgoing; Mon, 5 Oct 1998 00:34:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (castles140.castles.com [208.214.165.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24309 for ; Mon, 5 Oct 1998 00:34:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA00910; Mon, 5 Oct 1998 00:39:50 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810050739.AAA00910@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Igor Roshchin cc: stable@FreeBSD.ORG Subject: Re: -STABLE and vx driver In-reply-to: Your message of "Mon, 05 Oct 1998 02:21:31 CDT." <199810050721.CAA28629@alecto.physics.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Oct 1998 00:39:49 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello! > > On a P-II -300 with 128MB of memory > I made an update (-stable of Sep. 19 or a few days earlier) > from 2.2.5-Release. (or 2.2-stable shortly after 2.2.5-release) > > All update went smoothly, except, that the new compiled kernel > doesn't recognize 3c905 card.. > The generic kernel does. You need the 'xl' driver now. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 05:01:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25868 for freebsd-stable-outgoing; Mon, 5 Oct 1998 05:01:33 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mb06.swip.net (mb06.swip.net [193.12.122.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25861 for ; Mon, 5 Oct 1998 05:01:25 -0700 (PDT) (envelope-from martin@filex.se) Received: from filex.se (dialup43-4-30.swipnet.se [130.244.43.222]) by mb06.swip.net (8.8.8/8.8.8) with ESMTP id OAA08884 for ; Mon, 5 Oct 1998 14:01:00 +0200 (MET DST) Message-ID: <3618B4E1.8F75C3A3@filex.se> Date: Mon, 05 Oct 1998 14:00:33 +0200 From: Martin Nilsson X-Mailer: Mozilla 4.06 [en] (WinNT; I) MIME-Version: 1.0 To: "stable@FreeBSD.ORG" Subject: Re: ports distfiles on CD's Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> There's probably not much that can be done about the prereqs issue. >> But surely it's possible to keep all the files for a single port >> on the same CD. > > That was indeed done for 2.2.7 and will continue to be done. > > - - Jordan While we're talking abuot this subject, wold it be possible to have all common packages on one CD. Total package size (as of 2.2.7) is 787MB. Put the nationalised packages (there are 258MB of them) that don't fit on one of the other CD's. This way it would be a lot easier to find & install the package you want. Some of the people (FreeBSD newbies) who have borrowed my CDs haven't found the majority of packages that are hiding on CD4, just the ones on CD1. Also /stand/sysinstall (2.2.7) doesn't complain if you try to add distribution sets and have the wrong CD mounted, the operation just finishes very fast and doesn't install anything. /Martin -- _____________________________________________________________________ | o | +---------------------------+ +---------------------------+ | o | | | | Martin Nilsson M.Sc. CS&E | | Internet & Intranet | | | | o | | FILEX AB, Lund SWEDEN | | Applications & shopping | | o | | | | email: martin@filex.se | | using NT or UNIX. TCP/IP | | | | o | | Web: http://www.filex.se | | consulting. Programming in| | o | | | | Phone: +46-46-304130 | | C/C++,SQL,Perl & Java. | | | | o | +---------------------------+ +---------------------------+ | o | | | Those who do not understand Unix are condemned | | | o | to reinvent it, poorly. -- Henry Spencer | o | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 07:13:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11560 for freebsd-stable-outgoing; Mon, 5 Oct 1998 07:13:17 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11547 for ; Mon, 5 Oct 1998 07:13:14 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id HAA11410; Mon, 5 Oct 1998 07:12:26 -0700 (PDT) Message-Id: <199810051412.HAA11410@implode.root.com> To: "Morgan Davis" cc: freebsd-stable@FreeBSD.ORG Subject: Re: KERNEL PANICS in 2.2.7-RELEASE server In-reply-to: Your message of "Sun, 04 Oct 1998 17:52:16 PDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 05 Oct 1998 07:12:26 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Below is a dump of the kernel symbols around that address per your request. >Look like the offending function is _sosend. Yes, that's exactly what I'd expect in the case of running out of mbuf clusters. Try doing a options "NMBCLUSTERS=10000" ...that should fix the problem. >You may be right about mbuf clusters, as the kernel is simply GENERIC with >all the non-essentials commented out. What kernel tweaks would you >recommend to accomodate a high-bandwidth packet-passing system? It's an >audio server that simply forwards encoded audio streams to potentially >thousands of UDP and TCP client connections. It doesn't host users or do >much else. > >I wonder if the tweaks we've used for some of our BSDI news servers would >work. They use: > >maxusers 512 >options "CHILD_MAX=512" >options "OPEN_MAX=1024" >options "NMBCLUSTERS=16384" >options "TCBHASHSIZE=2048" >options AHC_TAGENABLE Those numbers might be a bit high (especially maxusers) without moving the kernel virtual start address down another 256MB (i.e. you may run out of kernel VM). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 07:35:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA14974 for freebsd-stable-outgoing; Mon, 5 Oct 1998 07:35:41 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA14951 for ; Mon, 5 Oct 1998 07:35:37 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id HAA13036; Mon, 5 Oct 1998 07:35:07 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Martin Nilsson cc: "stable@FreeBSD.ORG" Subject: Re: ports distfiles on CD's In-reply-to: Your message of "Mon, 05 Oct 1998 14:00:33 +0200." <3618B4E1.8F75C3A3@filex.se> Date: Mon, 05 Oct 1998 07:35:06 -0700 Message-ID: <13032.907598106@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While we're talking abuot this subject, wold it be possible to have all > common packages on one CD. Total package size (as of 2.2.7) is 787MB. This is up to Satoshi and crew and their definition of what a "common" package is, that and the laws of physics which state that if you have 650MB of space available and FreeBSD's base files already take up 167MB, you can't stick 787MB of packages on the CD. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 09:16:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02150 for freebsd-stable-outgoing; Mon, 5 Oct 1998 09:16:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pn.wagsky.com (wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02133 for ; Mon, 5 Oct 1998 09:16:14 -0700 (PDT) (envelope-from Jeff@Wagsky.com) Received: from [192.168.6.3] (mac.pn.wagsky.com [192.168.6.3]) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id JAA09588 for ; Mon, 5 Oct 1998 09:15:50 -0700 (PDT) (envelope-from Jeff@Wagsky.com) X-Sender: mailman@mail.pn.wagsky.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 5 Oct 1998 09:15:45 -0700 To: freebsd-stable@FreeBSD.ORG From: Jeff Kletsky Subject: ipfw SkipTo behavior changed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In trying to resolve puzzling behavior on a "new" FreeBSD box (2.2.7-STABLE, cvsup as of 980929), it appears that the behavior of the SkipTo rules in ipfw/kernel have changed. Previously a rule such as 2200 skipto 3000 all from 127.0.0.1 to 127.0.0.1 recv lo0 in would "skipto" the next-higher numbered rule in the list if 3000 did not exist. This build seems to require that a rule 3000 explicitly exist. If it does not exist, it proceeds as if rule 2200 is not matched. Is this an "intentional" change in the firewall code? If not, has a later release changed back to the older behavior? Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 09:31:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04001 for freebsd-stable-outgoing; Mon, 5 Oct 1998 09:31:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phmit.demon.co.uk (phmit.demon.co.uk [194.222.15.209]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA03975 for ; Mon, 5 Oct 1998 09:31:12 -0700 (PDT) (envelope-from dom@phmit.demon.co.uk) Received: from voodoo.pandhm.co.uk [192.15.143.228] by phmit.demon.co.uk with esmtp (Exim 1.82 #1) id 0zQDWs-0000v0-00; Mon, 5 Oct 1998 17:30:34 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 1.92 #1) for stable@freebsd.org id 0zQDZ5-0006Iu-00; Mon, 5 Oct 1998 17:32:51 +0100 To: stable@FreeBSD.ORG Subject: Getting ic to work in /etc/gettytab X-Mailer: nmh v0.26 Organization: Palmer & Harvey McLane Date: Mon, 05 Oct 1998 17:32:51 +0100 From: Dom Mitchell Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody know how to get the ic gettytab capability to work? I've been trying to get my modem to reset itself automatically after a call hangs up, but so far, I just find that getty gets wedged when I use this definition: mdm.115200:\ :np:sp#115200:dc#255:ic="" AT\r OK\r ATZ\r OK\r: (The dc#255 just ups the debugging output - but it still didn't make any sense). Oct 5 10:31:57 voodoo getty[23394]: modem init problem on /dev/ttyd0 Any ideas? -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Xerox studies suggest that most people print out electronic mail that is longer than half a page; paper use rises by 40 percent in offices that introduce E-mail." -- CCM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 10:25:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16232 for freebsd-stable-outgoing; Mon, 5 Oct 1998 10:25:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from horst.bfd.com (horst.bfd.com [12.9.219.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16197 for ; Mon, 5 Oct 1998 10:24:58 -0700 (PDT) (envelope-from ejs@bfd.com) Received: from HARLIE.bfd.com (bastion.bfd.com [12.9.219.14]) by horst.bfd.com (8.9.1/8.9.1) with ESMTP id KAA06116 for ; Mon, 5 Oct 1998 10:24:33 -0700 (PDT) (envelope-from ejs@bfd.com) Date: Mon, 5 Oct 1998 10:24:33 -0700 (PDT) From: "Eric J. Schwertfeger" To: stable@FreeBSD.ORG Subject: has anyone been able to make maildrop work with a recent 2.2-SNAP? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had maildrop (same idea as procmail, but more flexible) working on a 2.2.7-RELEASE box, which I then upgraded to 2.2.7-19980828-SNAP. Now, when I try to run maildrop, it sits there for about 5 minutes and exits with the message "maildrop: Timeout quota exceeded." It's in C++ and I haven't had the time to trace out where it's having the problem, but I suspect that it's some subtle problem with file locking, either a bug in maildrop that didn't trigger with -RELEASE, or an actual change in semantics in -STABLE. http://www.geocities.com/SiliconValley/Peaks/5799/maildrop.README.html compiled without dotlocking. I also tried 2.2.7-19981004-SNAP with no improvement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 11:44:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00999 for freebsd-stable-outgoing; Mon, 5 Oct 1998 11:44:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shemp.palomine.net (shemp.palomine.net [205.198.88.200]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA00968 for ; Mon, 5 Oct 1998 11:44:23 -0700 (PDT) (envelope-from cjohnson@palomine.net) Received: (qmail 16188 invoked by uid 1000); 5 Oct 1998 18:43:55 -0000 Message-ID: <19981005144355.A16155@palomine.net> Date: Mon, 5 Oct 1998 14:43:55 -0400 From: Chris Johnson To: "Eric J. Schwertfeger" , stable@FreeBSD.ORG Subject: Re: has anyone been able to make maildrop work with a recent 2.2-SNAP? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Eric J. Schwertfeger on Mon, Oct 05, 1998 at 10:24:33AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 05, 1998 at 10:24:33AM -0700, Eric J. Schwertfeger wrote: > > I've had maildrop (same idea as procmail, but more flexible) working on a > 2.2.7-RELEASE box, which I then upgraded to 2.2.7-19980828-SNAP. Now, > when I try to run maildrop, it sits there for about 5 minutes and exits > with the message "maildrop: Timeout quota exceeded." It's in C++ and I > haven't had the time to trace out where it's having the problem, but I > suspect that it's some subtle problem with file locking, either a bug in > maildrop that didn't trigger with -RELEASE, or an actual change in > semantics in -STABLE. > > http://www.geocities.com/SiliconValley/Peaks/5799/maildrop.README.html > compiled without dotlocking. > > I also tried 2.2.7-19981004-SNAP with no improvement. I've used maildrop versions .54, .54b, and .55 on two 2.2.7-STABLE machines, one stable as of August 16 and the other as of September 4. I've never had any problems with it at all. For the most part I accepted the default configuration, except for the location of the mailboxes (mine are in the home directories). Have you tried downloading the most recent version (released yesterday) and compiling it? If you do, note that there are a couple of extra steps required (make autoconf.h and make config.h after ./configure). Also, it appears that recent versions may require gmake instead of make. .55 seems to work with make, but .54x nneded gmake. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 12:46:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15168 for freebsd-stable-outgoing; Mon, 5 Oct 1998 12:46:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from horst.bfd.com (horst.bfd.com [12.9.219.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15163 for ; Mon, 5 Oct 1998 12:46:27 -0700 (PDT) (envelope-from ejs@bfd.com) Received: from HARLIE.bfd.com (bastion.bfd.com [12.9.219.14]) by horst.bfd.com (8.9.1/8.9.1) with ESMTP id MAA07344; Mon, 5 Oct 1998 12:46:03 -0700 (PDT) (envelope-from ejs@bfd.com) Date: Mon, 5 Oct 1998 12:46:02 -0700 (PDT) From: "Eric J. Schwertfeger" To: Chris Johnson cc: stable@FreeBSD.ORG Subject: Re: has anyone been able to make maildrop work with a recent 2.2-SNAP? In-Reply-To: <19981005144355.A16155@palomine.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Oct 1998, Chris Johnson wrote: > On Mon, Oct 05, 1998 at 10:24:33AM -0700, Eric J. Schwertfeger wrote: > > > > I've had maildrop (same idea as procmail, but more flexible) working on a > > 2.2.7-RELEASE box, which I then upgraded to 2.2.7-19980828-SNAP. Now, > > when I try to run maildrop, it sits there for about 5 minutes and exits > > with the message "maildrop: Timeout quota exceeded." It's in C++ and I > > haven't had the time to trace out where it's having the problem, but I > > suspect that it's some subtle problem with file locking, either a bug in > > maildrop that didn't trigger with -RELEASE, or an actual change in > > semantics in -STABLE. > > > > http://www.geocities.com/SiliconValley/Peaks/5799/maildrop.README.html > > compiled without dotlocking. > > > > I also tried 2.2.7-19981004-SNAP with no improvement. > > I've used maildrop versions .54, .54b, and .55 on two 2.2.7-STABLE machines, > one stable as of August 16 and the other as of September 4. I've never had any > problems with it at all. For the most part I accepted the default > configuration, except for the location of the mailboxes (mine are in the home > directories). Interesting. I recomplied exactly per your instructions, and nothing has changed. Oh, and I apparently wasn't explicit enough, the exact same binary that worked under 2.2.7-RELEASE previously is the one that failed under the SNAPs. Then I ftp'ed the binary (both the original and the new compile) to a machine that is still running 2.2.7-RELEASE, and guess what, they didn't work there either. Now I'm really confused, but since it seems to be a local phenomina, I'll go away now, at least until I figure out where it's hanging. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 12:52:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16401 for freebsd-stable-outgoing; Mon, 5 Oct 1998 12:52:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16015 for ; Mon, 5 Oct 1998 12:50:45 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id QAA26791; Mon, 5 Oct 1998 16:45:18 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199810051945.QAA26791@roma.coe.ufrj.br> Subject: Re: ipfw SkipTo behavior changed In-Reply-To: from Jeff Kletsky at "Oct 5, 98 09:15:45 am" To: Jeff@Wagsky.com (Jeff Kletsky) Date: Mon, 5 Oct 1998 16:45:18 -0300 (EST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Jeff Kletsky) // In trying to resolve puzzling behavior on a "new" FreeBSD box // (2.2.7-STABLE, cvsup as of 980929), it appears that the behavior of the // SkipTo rules in ipfw/kernel have changed. Previously a rule such as // // 2200 skipto 3000 all from 127.0.0.1 to 127.0.0.1 recv lo0 in // // would "skipto" the next-higher numbered rule in the list if 3000 did not // exist. This build seems to require that a rule 3000 explicitly exist. If // it does not exist, it proceeds as if rule 2200 is not matched. // // Is this an "intentional" change in the firewall code? If not, has a later // release changed back to the older behavior? IIRC Luigi has changed this behaviour together with the DUMMYNET integration. It was intentional, for code optimization. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 14:44:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08009 for freebsd-stable-outgoing; Mon, 5 Oct 1998 14:44:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07983 for ; Mon, 5 Oct 1998 14:44:28 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca11-102.ix.netcom.com [209.109.237.102]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id OAA16506; Mon, 5 Oct 1998 14:44:09 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id OAA01602; Mon, 5 Oct 1998 14:44:06 -0700 (PDT) Date: Mon, 5 Oct 1998 14:44:06 -0700 (PDT) Message-Id: <199810052144.OAA01602@silvia.hip.berkeley.edu> To: jkh@time.cdrom.com CC: martin@filex.se, stable@FreeBSD.ORG In-reply-to: <13032.907598106@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: ports distfiles on CD's From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * This is up to Satoshi and crew and their definition of what a "common" * package is, that and the laws of physics which state that if you have * 650MB of space available and FreeBSD's base files already take up * 167MB, you can't stick 787MB of packages on the CD. :-) Speaking of which, please give us a list of available spaces on each CD, so Justin and I can start working on partitioning the stuff. Thanks. Satoshi P.S. Release is still on 10/15? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 5 15:37:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19488 for freebsd-stable-outgoing; Mon, 5 Oct 1998 15:37:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19470; Mon, 5 Oct 1998 15:37:23 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA15098; Mon, 5 Oct 1998 15:37:25 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: asami@FreeBSD.ORG (Satoshi Asami) cc: martin@filex.se, stable@FreeBSD.ORG Subject: Re: ports distfiles on CD's In-reply-to: Your message of "Mon, 05 Oct 1998 14:44:06 PDT." <199810052144.OAA01602@silvia.hip.berkeley.edu> Date: Mon, 05 Oct 1998 15:37:25 -0700 Message-ID: <15094.907627045@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Speaking of which, please give us a list of available spaces on each > CD, so Justin and I can start working on partitioning the stuff. > Thanks. I'm afraid I don't know that precisely until the actual CD images are sort of run. If you're capable of dealing with some last-minute adjustments and can take rough estimates, the sizes are: disc1 450MB free (not counting directory metadata!) disc2 full disc3 580MB free (/usr/ports and www take up 70MB) disc4 650MB free Remember, of course, that you also have to fit your distfiles in here somewhere, not just the packages. Myself, I'd be seriously looking for ways to automate all this since the toolkit CD, which is another product where you guys are going to get all 4 650MB CDs to yourselves, is going to pose yet another set of challenges. :-) > P.S. Release is still on 10/15? Yep! I hope we won't slip more than a week this time too since I leave for Holland on the 21st. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 6 02:25:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09994 for freebsd-stable-outgoing; Tue, 6 Oct 1998 02:25:39 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA09870 for ; Tue, 6 Oct 1998 02:24:20 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA05814; Tue, 6 Oct 1998 08:21:47 +0100 From: Luigi Rizzo Message-Id: <199810060721.IAA05814@labinfo.iet.unipi.it> Subject: Re: ipfw SkipTo behavior changed To: jonny@jonny.eng.br (Joao Carlos Mendes Luis) Date: Tue, 6 Oct 1998 08:21:46 +0100 (MET) Cc: Jeff@Wagsky.com, freebsd-stable@FreeBSD.ORG In-Reply-To: <199810051945.QAA26791@roma.coe.ufrj.br> from "Joao Carlos Mendes Luis" at Oct 5, 98 04:44:59 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > #define quoting(Jeff Kletsky) > // In trying to resolve puzzling behavior on a "new" FreeBSD box > // (2.2.7-STABLE, cvsup as of 980929), it appears that the behavior of the > // SkipTo rules in ipfw/kernel have changed. Previously a rule such as > // > // 2200 skipto 3000 all from 127.0.0.1 to 127.0.0.1 recv lo0 in > // > // would "skipto" the next-higher numbered rule in the list if 3000 did not > // exist. This build seems to require that a rule 3000 explicitly exist. If > // it does not exist, it proceeds as if rule 2200 is not matched. > // > // Is this an "intentional" change in the firewall code? If not, has a later > // release changed back to the older behavior? > > IIRC Luigi has changed this behaviour together with the DUMMYNET > integration. It was intentional, for code optimization. Actually the change was not intentional, i just used == instead of == in find_next_rule() or so within ip_fw.c The fix is really one char. The reason i did not fixed (yet) the code myself is that i think it is not that safe to rely on this feature in a security module such as ipfw. But if people want me to revert the code to the default behaviour i have no problems with that. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 6 02:35:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11262 for freebsd-stable-outgoing; Tue, 6 Oct 1998 02:35:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11243 for ; Tue, 6 Oct 1998 02:35:41 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id CAA17879; Tue, 6 Oct 1998 02:34:20 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Luigi Rizzo cc: jonny@jonny.eng.br (Joao Carlos Mendes Luis), Jeff@Wagsky.com, freebsd-stable@FreeBSD.ORG Subject: Re: ipfw SkipTo behavior changed In-reply-to: Your message of "Tue, 06 Oct 1998 08:21:46 BST." <199810060721.IAA05814@labinfo.iet.unipi.it> Date: Tue, 06 Oct 1998 02:34:19 -0700 Message-ID: <17875.907666459@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The reason i did not fixed (yet) the code myself is that i think > it is not that safe to rely on this feature in a security module > such as ipfw. But if people want me to revert the code to the > default behaviour i have no problems with that. Considering the questions which have swirled around this, I think restoring the default behavior would be a good idea. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 6 02:39:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11703 for freebsd-stable-outgoing; Tue, 6 Oct 1998 02:39:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA11682 for ; Tue, 6 Oct 1998 02:39:36 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA05884; Tue, 6 Oct 1998 08:37:06 +0100 From: Luigi Rizzo Message-Id: <199810060737.IAA05884@labinfo.iet.unipi.it> Subject: Re: ipfw SkipTo behavior changed To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 6 Oct 1998 08:37:05 +0100 (MET) Cc: jonny@jonny.eng.br, Jeff@Wagsky.com, freebsd-stable@FreeBSD.ORG In-Reply-To: <17875.907666459@time.cdrom.com> from "Jordan K. Hubbard" at Oct 6, 98 02:34:00 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The reason i did not fixed (yet) the code myself is that i think > > it is not that safe to rely on this feature in a security module > > such as ipfw. But if people want me to revert the code to the > > default behaviour i have no problems with that. > > Considering the questions which have swirled around this, I think > restoring the default behavior would be a good idea. ok fine (but i only see one such msg plus a couple of replies, did i miss some ?) luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 6 02:44:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12432 for freebsd-stable-outgoing; Tue, 6 Oct 1998 02:44:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12410 for ; Tue, 6 Oct 1998 02:44:42 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id CAA17953; Tue, 6 Oct 1998 02:40:53 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Luigi Rizzo cc: jonny@jonny.eng.br, Jeff@Wagsky.com, freebsd-stable@FreeBSD.ORG Subject: Re: ipfw SkipTo behavior changed In-reply-to: Your message of "Tue, 06 Oct 1998 08:37:05 BST." <199810060737.IAA05884@labinfo.iet.unipi.it> Date: Tue, 06 Oct 1998 02:40:53 -0700 Message-ID: <17950.907666853@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recall at least 3 different people going "huh?" in -stable, but I wouldn't swear on that exact number. :) - Jordan > > > The reason i did not fixed (yet) the code myself is that i think > > > it is not that safe to rely on this feature in a security module > > > such as ipfw. But if people want me to revert the code to the > > > default behaviour i have no problems with that. > > > > Considering the questions which have swirled around this, I think > > restoring the default behavior would be a good idea. > > ok fine (but i only see one such msg plus a couple of replies, did > i miss some ?) > > luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 6 04:23:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28895 for freebsd-stable-outgoing; Tue, 6 Oct 1998 04:23:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA28829 for ; Tue, 6 Oct 1998 04:23:14 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA06075; Tue, 6 Oct 1998 10:19:38 +0100 From: Luigi Rizzo Message-Id: <199810060919.KAA06075@labinfo.iet.unipi.it> Subject: Re: ipfw SkipTo behavior changed To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Tue, 6 Oct 1998 10:19:37 +0100 (MET) Cc: jonny@jonny.eng.br, Jeff@Wagsky.com, freebsd-stable@FreeBSD.ORG In-Reply-To: <199810060721.IAA05814@labinfo.iet.unipi.it> from "Luigi Rizzo" at Oct 6, 98 08:21:27 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually the change was not intentional, i just used == instead of == > in find_next_rule() or so within ip_fw.c and the typo above (== instead of >= ) was not intentional either, or it is that my finger just refuse to accept that :) in any case i have just committed the fix to -stable. (the 3.0 patches from my web site still have the more restrictive behaviour, for those 10 people who got them...) cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 6 18:16:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19586 for freebsd-stable-outgoing; Tue, 6 Oct 1998 18:16:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from home.us.net (home.us.net [198.240.72.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19520 for ; Tue, 6 Oct 1998 18:15:49 -0700 (PDT) (envelope-from jjw@us.net) Received: from q.jjw.us.net (q.jjw.us.net [207.244.202.2]) by home.us.net (8.8.8/8.8.8) with SMTP id VAA01419 for ; Tue, 6 Oct 1998 21:15:32 -0400 (EDT) X-Provider: US Net - Advanced Internet Services - 301-361-USNET - info@us.net Where Business Connects! (tm) -- http://www.us.net/ Message-ID: <361AC093.41C67EA6@us.net> Date: Tue, 06 Oct 1998 21:14:59 -0400 From: John Woodruff Organization: US Net X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: sn (SMC9000 Ether) Driver for -STABLE? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone have an etherdriver for the SMC9000 working for 2.2.x? I grabbed an if_sn.c (from the SMC web site, I think) that claimed to be for 2.1 (or was it 2.0??), saying: * $Id: if_sn.c,v 1.5 1996/10/30 13:22:50 gardner Exp $ * This FreeBSD driver is derived from the smc9194 Linux driver by * Erik Stahlman and is Copyright (C) 1996 by Erik Stahlman. * This driver also shamelessly borrows from the FreeBSD ep driver * which is Copyright (C) 1994 Herb Peyerl but the changes to 2.2.x proved more than my application-level C debugging skills can find. After some datatype changes (I looked closely at if_ep), it compiles, links, probes, and attaches fine: FreeBSD 2.2.5-RELEASE .... sn0 at 0x300-0x30f irq 10 on isa sn0: SMC91C90/91C92 UTP MAC address 00:c0:4f:de:7a:08 ep0 not probed due to I/O address conflict with sn0 at 0x300 but the ifconfig panics. It looks like snioctl(,SIOCSIFADDR,) or below smashed the stack, since it dies on the return from snioctl(). Other core damage might exist; but the box can come up multi-user with no trouble. Just dont touch sn0. What's worse, is the SMC9000 is on the docking station for an old 24M RAM 486 laptop, and for other reasons (don't ask) it's only got a 76M BSD partition; not even enough swap for a dump. I made a debugging kernel with mem limited to 8M, but cant get the dump off the box! This is the *only* LAN link it has here (another docking station, in another office, has the ep0, which works 100% OK; but only one dock at a time, of course). If someone has a working if_sn for 2.2.5, I'd be quite grateful. Otherwise, it looks like I'll have to learn to use serial gdb linked to the fully-functional 2.2.5 modern machine next to it. -- John Woodruff, Sr. Network Engineer, US Net - 301-361-USNET Washington/Baltimore/Richmond ISP - $6.95/month for full PPP! PGP KeyFP: 66 18 1A 4E 55 08 40 E2 C7 B1 F2 D1 81 12 6D BF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 7 06:33:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18696 for freebsd-stable-outgoing; Wed, 7 Oct 1998 06:33:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from king.ki.informatik.uni-frankfurt.de (king.ki.informatik.uni-frankfurt.de [141.2.10.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18341 for ; Wed, 7 Oct 1998 06:31:02 -0700 (PDT) (envelope-from marko@king.ki.informatik.uni-frankfurt.de) Received: (from marko@localhost) by king.ki.informatik.uni-frankfurt.de (8.7.1/8.7.1) id PAA22126; Wed, 7 Oct 1998 15:30:38 +0200 (METDST) Date: Wed, 7 Oct 1998 15:30:38 +0200 (METDST) Message-Id: <199810071330.PAA22126@king.ki.informatik.uni-frankfurt.de> From: Marko Schuetz MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-stable@FreeBSD.ORG Subject: Global register variables in gcc and stdio.h?!? X-Mailer: VM 6.34 under Emacs 20.2.1 Reply-To: marko@cs.uni-frankfurt.de Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG An application I want to compile runs much faster if it can use global register variables. Trying to compile it I get [...] gmake[1]: Entering directory `/usr/home/marko/src/mercury-0.7.3.orig/runtime' MERCURY_C_INCL_DIR=. ../scripts/mgnuc --grade asm_fast.gc --no-ansi -I../runtime -I../boehm_gc -g -c label.c -o label.o In file included from regs.h:67, from imp.h:36, from label.c:19: machdeps/i386_regs.h:61: global register variable follows a function definition machdeps/i386_regs.h:62: global register variable follows a function definition machdeps/i386_regs.h:67: global register variable follows a function definition gmake[1]: *** [label.o] Error 1 gmake[1]: Leaving directory `/usr/home/marko/src/mercury-0.7.3.orig/runtime' gmake: *** [runtime] Error 2 I checked the preprocessor output and found that there is only the function definition for `static __inline int __sputc(int _c, FILE *_p)` which is included from stdio.h. Depending on an #ifdef that version of __sputc or an alternative as a macro is used. I would suggest adding something like !defined(__USE_GLOBAL_REGISTER_VARIABLES__) to the condition for using the inline function. Doing that allows at least mercury to compile using global register variables. Please comment. Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 7 08:28:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10798 for freebsd-stable-outgoing; Wed, 7 Oct 1998 08:28:10 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10721 for ; Wed, 7 Oct 1998 08:28:02 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00355; Wed, 7 Oct 1998 08:31:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810071531.IAA00355@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: marko@cs.uni-frankfurt.de cc: freebsd-stable@FreeBSD.ORG Subject: Re: Global register variables in gcc and stdio.h?!? In-reply-to: Your message of "Wed, 07 Oct 1998 15:30:38 +0200." <199810071330.PAA22126@king.ki.informatik.uni-frankfurt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Oct 1998 08:31:57 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > An application I want to compile runs much faster if it can use global > register variables. > > Trying to compile it I get > > [...] > gmake[1]: Entering directory `/usr/home/marko/src/mercury-0.7.3.orig/runtime' > MERCURY_C_INCL_DIR=. ../scripts/mgnuc --grade asm_fast.gc --no-ansi -I../runtime -I../boehm_gc -g -c label.c -o label.o > In file included from regs.h:67, > from imp.h:36, > from label.c:19: > machdeps/i386_regs.h:61: global register variable follows a function definition > machdeps/i386_regs.h:62: global register variable follows a function definition > machdeps/i386_regs.h:67: global register variable follows a function definition > gmake[1]: *** [label.o] Error 1 > gmake[1]: Leaving directory `/usr/home/marko/src/mercury-0.7.3.orig/runtime' > gmake: *** [runtime] Error 2 > > I checked the preprocessor output and found that there is only the > function definition for `static __inline int __sputc(int _c, FILE > *_p)` which is included from stdio.h. Depending on an #ifdef that > version of __sputc or an alternative as a macro is used. > > I would suggest adding something like > !defined(__USE_GLOBAL_REGISTER_VARIABLES__) to the condition for using > the inline function. > > Doing that allows at least mercury to compile using global register > variables. > > Please comment. 1) Any application which depends on global register variables for performance needs to be fixed. The concept of a "global register variable" on the x86 is a bit of a joke anyway. 2) Declare your global register variables before including header files. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 7 09:23:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22473 for freebsd-stable-outgoing; Wed, 7 Oct 1998 09:23:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22468 for ; Wed, 7 Oct 1998 09:23:27 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id BAA23629; Wed, 7 Oct 1998 01:14:37 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id BAA04109; Wed, 7 Oct 1998 01:14:36 -0600 Date: Wed, 7 Oct 1998 01:14:36 -0600 Message-Id: <199810070714.BAA04109@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John Woodruff Cc: freebsd-stable@FreeBSD.ORG Subject: Re: sn (SMC9000 Ether) Driver for -STABLE? In-Reply-To: <361AC093.41C67EA6@us.net> References: <361AC093.41C67EA6@us.net> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does anyone have an etherdriver for the SMC9000 working for 2.2.x? I might. I ported the driver from PAO to 2.2.*, but the 'PCMCIA' portion is not yet completed. Send me email and I'll send you what I have, which is not guaranteed to do anything correctly, but then again it might... :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 7 11:43:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20641 for freebsd-stable-outgoing; Wed, 7 Oct 1998 11:43:39 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20624 for ; Wed, 7 Oct 1998 11:43:28 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id LAA24550; Wed, 7 Oct 1998 11:42:58 -0700 (MST) From: "Chad R. Larson" Message-Id: <199810071842.LAA24550@freebie.dcfinc.com> Subject: Re: Global register variables in gcc and stdio.h?!? To: marko@cs.uni-frankfurt.de Date: Wed, 7 Oct 1998 11:42:57 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <199810071330.PAA22126@king.ki.informatik.uni-frankfurt.de> from Marko Schuetz at "Oct 7, 98 03:30:38 pm" Reply-to: chad@dcfinc.com X-unexpected: The Spanish Inquisition 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-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > An application I want to compile runs much faster if it can use global > register variables. [ snip ] > Please comment. One comment I'd have is that GCC does a pretty wonderful job of allocating registers on its own. Perhaps your experience is based on some other compiler? My personal opinion after staring at a lot of compiler-generated assembler code. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 7 16:30:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22088 for freebsd-stable-outgoing; Wed, 7 Oct 1998 16:30:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tok.qiv.com (tok.qiv.com [205.238.142.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22083 for ; Wed, 7 Oct 1998 16:30:49 -0700 (PDT) (envelope-from jdn@acp.qiv.com) Received: (from uucp@localhost) by tok.qiv.com (8.8.8/8.8.5) with UUCP id SAA15503; Wed, 7 Oct 1998 18:30:37 -0500 (CDT) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.8/8.8.8) with SMTP id SAA01390; Wed, 7 Oct 1998 18:23:36 -0500 (CDT) (envelope-from jdn@acp.qiv.com) Date: Wed, 7 Oct 1998 18:23:35 -0500 (CDT) From: Jay Nelson To: Dom Mitchell cc: stable@FreeBSD.ORG Subject: Re: Getting ic to work in /etc/gettytab In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wouldn't it be simpler to set &D3 (or &D2, depending on the modem) and storing it in profile 0? (You'll have to RTFM to find out which incantation works on your modem.) This tells the modem to do a reset and reload of profile 0 on carrier drop. -- Jay On Mon, 5 Oct 1998, Dom Mitchell wrote: >Does anybody know how to get the ic gettytab capability to work? I've >been trying to get my modem to reset itself automatically after a call >hangs up, but so far, I just find that getty gets wedged when I use this >definition: > >mdm.115200:\ > :np:sp#115200:dc#255:ic="" AT\r OK\r ATZ\r OK\r: > >(The dc#255 just ups the debugging output - but it still didn't make any >sense). > >Oct 5 10:31:57 voodoo getty[23394]: modem init problem on /dev/ttyd0 > >Any ideas? >-- >Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator >"Xerox studies suggest that most people print out electronic mail > that is longer than half a page; paper use rises by 40 percent in > offices that introduce E-mail." -- CCM > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 7 16:49:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25140 for freebsd-stable-outgoing; Wed, 7 Oct 1998 16:49:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phmit.demon.co.uk (phmit.demon.co.uk [194.222.15.209]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA25116 for ; Wed, 7 Oct 1998 16:49:19 -0700 (PDT) (envelope-from dom@phmit.demon.co.uk) Received: from voodoo.pandhm.co.uk [192.15.143.228] by phmit.demon.co.uk with esmtp (Exim 1.82 #1) id 0zR3KP-0002Df-00; Thu, 8 Oct 1998 00:49:09 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 1.92 #1) id 0zR3MR-0002db-00; Thu, 8 Oct 1998 00:51:15 +0100 To: Jay Nelson cc: stable@FreeBSD.ORG Subject: Re: Getting ic to work in /etc/gettytab X-Mailer: nmh v0.26 X-Colour: Green Organization: Palmer & Harvey McLane In-reply-to: Jay Nelson's message of "Wed, 07 Oct 1998 18:23:35 CDT" Date: Thu, 08 Oct 1998 00:51:15 +0100 From: Dom Mitchell Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 7 October 1998, Jay Nelson proclaimed: > Wouldn't it be simpler to set &D3 (or &D2, depending on the modem) and > storing it in profile 0? (You'll have to RTFM to find out which > incantation works on your modem.) This tells the modem to do a reset > and reload of profile 0 on carrier drop. Yes. That would be an excellent solution. However, I'd still like to know why "ic=" doesn't work, just for curiosity's sake... -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Xerox studies suggest that most people print out electronic mail that is longer than half a page; paper use rises by 40 percent in offices that introduce E-mail." -- CCM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 04:11:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13957 for freebsd-stable-outgoing; Thu, 8 Oct 1998 04:11:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from federation.addy.com (federation.addy.com [207.239.68.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA13934 for ; Thu, 8 Oct 1998 04:10:55 -0700 (PDT) (envelope-from francisco@natserv.com) Received: from quisqueya.natserv.com (TC2-dial-83-142.oldslip.inch.com [207.240.142.83]) by federation.addy.com (8.8.5/8.6.12) with ESMTP id HAA03731 for ; Thu, 8 Oct 1998 07:10:49 -0400 (EDT) Message-Id: <199810081110.HAA03731@federation.addy.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 08 Oct 1998 07:11:15 -0000 (GMT) Reply-To: francisco@natserv.com From: Francisco Reyes To: freebsd-stable@FreeBSD.ORG Subject: Recommendations on updating /etc for -stable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am seeking suggestions on how to best update /etc/ while tracking stable. Any scripts someone has found useful? I read Nick Clayton "Making the world your own" and that answered most questions. On that document there is a mention of a script dircmp.pl and says it is included in FreeBSD versions 2.0 and above. I coult not find it in 2.2.7. Was this command replaced by something else? ---- francisco@natserv.com The power to serve. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 06:53:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29206 for freebsd-stable-outgoing; Thu, 8 Oct 1998 06:53:21 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.cpd.ufv.br (mail.cpd.ufv.br [200.19.130.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29184 for ; Thu, 8 Oct 1998 06:53:07 -0700 (PDT) (envelope-from grios@dpi.ufv.br) Received: from vicosa.dpi.ufv.br (vicosa.dpi.ufv.br [200.17.74.1]) by mail.cpd.ufv.br (8.8.6/8.8.6) with SMTP id LAA07913 for ; Thu, 8 Oct 1998 11:05:15 -0300 Received: from dpi.ufv.br (potts.dpf.ufv.br) by vicosa.dpi.ufv.br (4.1/SMI-4.1) id AA04308; Thu, 8 Oct 98 10:56:54 EST Message-Id: <361CC360.E33BCCC9@dpi.ufv.br> Date: Thu, 08 Oct 1998 10:51:28 -0300 From: Gustavo V G C Rios X-Mailer: Mozilla 4.06 [en] (X11; I; OSF1 V4.0 alpha) Mime-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, can any one tell me if FreeBSD supports quota? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 07:22:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05392 for freebsd-stable-outgoing; Thu, 8 Oct 1998 07:22:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05374 for ; Thu, 8 Oct 1998 07:22:42 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hindarfjell.ifi.uio.no (2602@hindarfjell.ifi.uio.no [129.240.64.130]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id QAA01310; Thu, 8 Oct 1998 16:22:28 +0200 (MET DST) Received: (from dag-erli@localhost) by hindarfjell.ifi.uio.no ; Thu, 8 Oct 1998 16:22:26 +0200 (MET DST) Mime-Version: 1.0 To: Gustavo V G C Rios Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: FreeBSD References: <361CC360.E33BCCC9@dpi.ufv.br> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 08 Oct 1998 16:22:25 +0200 In-Reply-To: Gustavo V G C Rios's message of "Thu, 08 Oct 1998 10:51:28 -0300" Message-ID: Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 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 HAA05388 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gustavo V G C Rios writes: > Hi, can any one tell me if FreeBSD supports quota? Yes. This belongs on freebsd-questions. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 07:24:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05844 for freebsd-stable-outgoing; Thu, 8 Oct 1998 07:24:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail-ord-2.pilot.net (mail-ord-2.pilot.net [205.243.174.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05832 for ; Thu, 8 Oct 1998 07:24:22 -0700 (PDT) (envelope-from John_Sconieres@ama-assn.org) Received: from unknown-31-162.ama-assn.org ([204.48.31.162]) by mail-ord-2.pilot.net (Pilot/) with ESMTP id JAA25531 for ; Thu, 8 Oct 1998 09:24:13 -0500 (CDT) Received: from gateway.ama-assn.org (localhost [127.0.0.1]) by unknown-31-162.ama-assn.org with SMTP id JAA28915 for ; Thu, 8 Oct 1998 09:24:08 -0500 (CDT) Received: by gateway.ama-assn.org id AA25893 (InterLock SMTP Gateway 3.0 for freebsd-stable@FreeBSD.ORG); Thu, 8 Oct 1998 09:23:09 -0500 Received: by gateway.ama-assn.org (Internal Mail Agent-1); Thu, 8 Oct 1998 09:23:09 -0500 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Thu, 08 Oct 1998 09:20:22 -0500 From: John Sconiers To: grios@dpi.ufv.br, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD Mime-Version: 1.0 Content-Type: text/plain Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you're referring to Home directory space quotas....etc.....yes Johnathan Raymond Sconiers II >>> Gustavo V G C Rios 10/08 8:51 AM >>> Hi, can any one tell me if FreeBSD supports quota? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 07:35:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08097 for freebsd-stable-outgoing; Thu, 8 Oct 1998 07:35:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08087 for ; Thu, 8 Oct 1998 07:35:34 -0700 (PDT) (envelope-from werner@btp1da.phy.uni-bayreuth.de) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id QAA23395; Thu, 8 Oct 1998 16:32:55 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <361CC360.E33BCCC9@dpi.ufv.br> Date: Thu, 08 Oct 1998 16:32:55 +0200 (MEST) Organization: University of bayreuth From: Werner Griessl To: Gustavo V G C Rios Subject: RE: FreeBSD Cc: "freebsd-stable@FreeBSD.ORG" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Oct-98 Gustavo V G C Rios wrote: > Hi, can any one tell me if FreeBSD supports quota? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message ---------------------------------- Yes, see /sys/i386/conf/LINT and /etc/rc.conf . Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 08:36:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18308 for freebsd-stable-outgoing; Thu, 8 Oct 1998 08:36:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netcom1.netcom.com (lax-ca66-45.ix.netcom.com [207.223.161.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18265 for ; Thu, 8 Oct 1998 08:36:33 -0700 (PDT) (envelope-from mvh@ix.netcom.com) Received: (from mvh@localhost) by netcom1.netcom.com (8.8.8/8.8.8) id IAA00332; Thu, 8 Oct 1998 08:36:21 -0700 (PDT) (envelope-from mvh) Date: Thu, 8 Oct 1998 08:36:21 -0700 (PDT) From: "Michael V. Harding" Message-Id: <199810081536.IAA00332@netcom1.netcom.com> To: francisco@natserv.com CC: freebsd-stable@FreeBSD.ORG In-reply-to: <199810081110.HAA03731@federation.addy.com> (message from Francisco Reyes on Thu, 08 Oct 1998 07:11:15 -0000 (GMT)) Subject: Re: Recommendations on updating /etc for -stable References: <199810081110.HAA03731@federation.addy.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't use '/etc/rc.conf' to make changes - make changes in 'rc.conf.local', this file overrides the defaults in '/etc/rc.conf'. Then you can just update '/etc/rc.conf' without needing to edit it. Also check out the port 'sysutils/mergemaster' - it merges a current build with your system, and allows you to edit things by hand. Quite handy - just make sure you don't blow away your password or other files. Make a backup of at least your /etc directory first... this is a great utility, hats off to the author! Mike Harding X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Oct 1998 07:11:15 -0000 (GMT) Reply-To: francisco@natserv.com From: Francisco Reyes Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG X-RULES: lists I am seeking suggestions on how to best update /etc/ while tracking stable. Any scripts someone has found useful? I read Nick Clayton "Making the world your own" and that answered most questions. On that document there is a mention of a script dircmp.pl and says it is included in FreeBSD versions 2.0 and above. I coult not find it in 2.2.7. Was this command replaced by something else? ---- francisco@natserv.com The power to serve. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 08:37:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18492 for freebsd-stable-outgoing; Thu, 8 Oct 1998 08:37:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pn.wagsky.com (wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18447 for ; Thu, 8 Oct 1998 08:37:33 -0700 (PDT) (envelope-from Jeff@Wagsky.com) Received: from [192.168.6.3] (mac.pn.wagsky.com [192.168.6.3]) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id IAA04503; Thu, 8 Oct 1998 08:37:17 -0700 (PDT) (envelope-from Jeff@Wagsky.com) X-Sender: mailman@mail.pn.wagsky.com Message-Id: In-Reply-To: <199810081110.HAA03731@federation.addy.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 8 Oct 1998 08:37:14 -0700 To: francisco@natserv.com From: Jeff Kletsky Subject: Re: Recommendations on updating /etc for -stable Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I am seeking suggestions on how to best update /etc/ while tracking stable. >Any scripts someone has found useful? > >I read Nick Clayton "Making the world your own" and that answered most >questions. On that document there is a mention of a script dircmp.pl and >says it is included in FreeBSD versions 2.0 and above. I coult not find >it in 2.2.7. It is available from his web site http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/dircmp.pl I am personally partial to something like diff -r --exclude=dev --side-by-side --suppress-common-lines since not only does it tell me what is there, not there, and changed, but in the same pass lets me know *how* it has changed so I can make the edits. Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 09:59:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01834 for freebsd-stable-outgoing; Thu, 8 Oct 1998 09:59:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01829 for ; Thu, 8 Oct 1998 09:59:21 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id JAA14327; Thu, 8 Oct 1998 09:57:23 -0700 (PDT) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id JAA03348; Thu, 8 Oct 1998 09:57:23 -0700 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id KAA12540; Thu, 8 Oct 1998 10:57:21 -0600 Message-ID: <361CEEF1.3A3182D@softweyr.com> Date: Thu, 08 Oct 1998 10:57:21 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: chad@dcfinc.com CC: marko@cs.uni-frankfurt.de, freebsd-stable@FreeBSD.ORG Subject: Re: Global register variables in gcc and stdio.h?!? References: <199810071842.LAA24550@freebie.dcfinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chad R. Larson wrote: > > > An application I want to compile runs much faster if it can use global > > register variables. > [ snip ] > > Please comment. > > One comment I'd have is that GCC does a pretty wonderful job of allocating > registers on its own. Perhaps your experience is based on some other > compiler? I think you'll find in GCC that "register" is regarded as a weak hint at best. On x86 I think it's basically a no-op. The compiler is a whole lot smarter about register allocation that you are, especially on an architecture where there aren't any. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 10:47:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11275 for freebsd-stable-outgoing; Thu, 8 Oct 1998 10:47:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11253 for ; Thu, 8 Oct 1998 10:47:22 -0700 (PDT) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id KAA21897; Thu, 8 Oct 1998 10:47:14 -0700 (PDT) (envelope-from Studded@dal.net) Message-ID: <361CFAA0.400EA27C@dal.net> Date: Thu, 08 Oct 1998 10:47:12 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-0929 i386) X-Accept-Language: en MIME-Version: 1.0 To: francisco@natserv.com CC: freebsd-stable@FreeBSD.ORG Subject: Re: Recommendations on updating /etc for -stable References: <199810081110.HAA03731@federation.addy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Francisco Reyes wrote: > > I am seeking suggestions on how to best update /etc/ while tracking stable. > Any scripts someone has found useful? Have I got a deal for you! Update your ports collection and check out /usr/ports/sysutils/mergemaster. Good luck, Doug PS, this should really have been asked on -questions -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 11:40:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20900 for freebsd-stable-outgoing; Thu, 8 Oct 1998 11:40:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20879 for ; Thu, 8 Oct 1998 11:40:29 -0700 (PDT) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA24444; Thu, 8 Oct 1998 11:40:22 -0700 (PDT) (envelope-from Studded@dal.net) Message-ID: <361D0715.81EEE28C@dal.net> Date: Thu, 08 Oct 1998 11:40:21 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-0929 i386) X-Accept-Language: en MIME-Version: 1.0 To: Jeff Kletsky CC: freebsd-stable@FreeBSD.ORG Subject: Re: Recommendations on updating /etc for -stable References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeff Kletsky wrote: > I am personally partial to something like > > diff -r --exclude=dev --side-by-side --suppress-common-lines > > since not only does it tell me what is there, not there, and changed, but > in the same pass lets me know *how* it has changed so I can make the edits. I use a similar method in my mergemaster script, except I use sdiff which is even easier. You might want to check out the man page. Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 11:48:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22336 for freebsd-stable-outgoing; Thu, 8 Oct 1998 11:48:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22044 for ; Thu, 8 Oct 1998 11:48:20 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA223058450; Thu, 8 Oct 1998 10:54:10 -0400 Date: Thu, 8 Oct 1998 10:54:10 -0400 (EDT) From: Bill Fumerola To: Gustavo V G C Rios Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: FreeBSD In-Reply-To: <361CC360.E33BCCC9@dpi.ufv.br> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Oct 1998, Gustavo V G C Rios wrote: > Hi, can any one tell me if FreeBSD supports quota? Yes, man 1 quota. There is also information about it in the Handbook and FAQ, do try and look there (www.freebsd.org/search/search.html) before asking questions. - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 14:17:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22205 for freebsd-stable-outgoing; Thu, 8 Oct 1998 14:17:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22191 for ; Thu, 8 Oct 1998 14:17:15 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40326>; Fri, 9 Oct 1998 07:16:33 +1000 Date: Fri, 9 Oct 1998 07:16:54 +1000 From: Peter Jeremy Subject: Re: Global register variables in gcc and stdio.h?!? To: freebsd-stable@FreeBSD.ORG Message-Id: <98Oct9.071633est.40326@border.alcanet.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: >I think you'll find in GCC that "register" is regarded as a weak hint at >best. Agreed. > The compiler is a whole >lot smarter about register allocation that you are, I disagree. The compiler bases its register allocation on a guess at the dynamic control flow, based on static data and control flow analysis. The actual control flow may be significantly different from gcc's guess - especially if a lot of code is rarely executed (eg exception handling code within a function). Also, gcc does not do any global (cross-function) analysis or optimisation. Threaded and bytecode interpreters (ie forth, e-lisp, java) generally have a small number of global variables which should be in registers - gcc can't work this out itself (but does have some extensions to allow then to be manually specified). Another problem with gcc's register allocation is that it doesn't re-order local variables within the stack frame. This means that variables that can't fit into registers (mostly because they're too large) sit at the top of the stack frame (closest to the frame pointer). Spilt registers go at the end of the stack frame. The net result of this is unnecessary code bloat. For example, on the x86 there is only a choice of 8 or 32-bit offsets - whilst the 32-bit offset has the same instruction timing, increasing the code size reduces the cache effectiveness, reducing speed. On the SPARC you need a 2 or 3-instruction sequence (and a work register) to access the variable once you exceed the 12-bit offset. > especially on an >architecture where there aren't any. Actually, on a true 0 or 1-address architecture, register allocation is trivial. The real difficulties occur with architectures that have a small number of registers which aren't quite all general purpose. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 14:29:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24072 for freebsd-stable-outgoing; Thu, 8 Oct 1998 14:29:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from online.no (pilt-s.online.no [193.212.1.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24044 for ; Thu, 8 Oct 1998 14:29:13 -0700 (PDT) (envelope-from zerium@webindex.no) Received: from zerium.dyn.ml.org (ti01a22-0109.dialup.online.no [130.67.10.109]) by online.no (8.9.1/8.9.1) with ESMTP id XAA25200; Thu, 8 Oct 1998 23:28:45 +0200 (MET DST) Received: from localhost (zerium@localhost) by zerium.dyn.ml.org (8.9.1/8.9.1) with SMTP id RAA04822; Thu, 8 Oct 1998 17:43:09 +0200 (CEST) (envelope-from zerium@zerium.dyn.ml.org) Date: Thu, 8 Oct 1998 17:43:09 +0200 (CEST) From: Hans Petter Bieker X-Sender: zerium@zerium.dyn.ml.org To: Francisco Reyes cc: freebsd-stable@FreeBSD.ORG Subject: Re: Recommendations on updating /etc for -stable In-Reply-To: <199810081110.HAA03731@federation.addy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Oct 1998, Francisco Reyes wrote: > I am seeking suggestions on how to best update /etc/ while tracking stable. > Any scripts someone has found useful? /usr/ports/sysutils/mergemaster? -bieker- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 15:15:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02324 for freebsd-stable-outgoing; Thu, 8 Oct 1998 15:15:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02275 for ; Thu, 8 Oct 1998 15:15:15 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id TAA06415; Thu, 8 Oct 1998 19:21:45 +0100 (BST) (envelope-from nik) Message-ID: <19981008192144.36546@nothing-going-on.org> Date: Thu, 8 Oct 1998 19:21:44 +0100 From: Nik Clayton To: Jeff Kletsky , francisco@natserv.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Recommendations on updating /etc for -stable References: <199810081110.HAA03731@federation.addy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Jeff Kletsky on Thu, Oct 08, 1998 at 08:37:14AM -0700 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 08, 1998 at 08:37:14AM -0700, Jeff Kletsky wrote: > >I am seeking suggestions on how to best update /etc/ while tracking stable. > >Any scripts someone has found useful? > > > >I read Nick Clayton "Making the world your own" and that answered most > >questions. On that document there is a mention of a script dircmp.pl and > >says it is included in FreeBSD versions 2.0 and above. I coult not find > >it in 2.2.7. That's not quite what it says; dircmp.pl is a small Perl script (Perl 4.036, which is installed by default on FreeBSD versions 2.0 and above) although I can see where the confusion comes in. > It is available from his web site > http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/dircmp.pl > > I am personally partial to something like > > diff -r --exclude=dev --side-by-side --suppress-common-lines > > since not only does it tell me what is there, not there, and changed, but > in the same pass lets me know *how* it has changed so I can make the edits. Allow me to plug Doug's (aka Studded) 'mergemaster' script, which you'll find in ports/sysutils/mergemaster, which does this and more (I believe). I've never actually used it, and near the top of my list of things to do is "download a copy, use it, and write about it for the tutorial". If anyone else has already used it and feels like submitting something (plain text, HTML, DocBook, I don't really care) to me, please feel free. N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 16:16:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15777 for freebsd-stable-outgoing; Thu, 8 Oct 1998 16:16:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mailhub1.anasazi.com (mailhub1.anasazi.com [138.113.128.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15682 for ; Thu, 8 Oct 1998 16:16:02 -0700 (PDT) (envelope-from wbloom@rez.com) Received: from wbloom.anasazi.com (wbloom.anasazi.com [138.113.128.182]) by mailhub1.anasazi.com (8.8.5/8.8.8) with ESMTP id QAA27481; Thu, 8 Oct 1998 16:15:53 -0700 (MST) (envelope-from wbloom@anasazi.com) Received: (from wbloom@localhost) by wbloom.anasazi.com (8.8.8/8.8.8) id QAA28206; Thu, 8 Oct 1998 16:15:53 -0700 (MST) (envelope-from wbloom) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 08 Oct 1998 16:15:52 -0700 (MST) Organization: Anasazi Inc. From: William Bloom To: freebsd-stable@FreeBSD.ORG Subject: Update Needed to mtree /usr Spec Cc: chad@rez.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks like an Oct 6 update to /usr/doc/es/FAQ/Makefile (from the 'doc' CVS module) now causes... make all distribute DISTDIR=... ...from /usr/doc to distribute documents into... ${DISTDIR}/doc/usr/share/doc/es However, the make eventually fails because the /usr mtree specification in /usr/src/etc/mtree/BSD.usr.dist contains no entry for the share/doc/es subdirectory. This in turn prevents a FreeBSD release from being generated (with NODOCS disabled). Perhaps this is a work-in-progress and I've just been caught trying to generate a release at just the wrong moment. In that case, I should just wait a while until my repository catches up the rest of the /usr/src/etc updates. However, I just wanted to check in with the mailing list as a first step in case I'm the only one to be aware of this problem so far. Bill -------------------------------------------------------------- William Bloom (602) 906-7525 Anasazi, Inc. 7500 North Dreamy Draw Drive, Suite 120 Phoenix, Az 85020 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 17:01:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23990 for freebsd-stable-outgoing; Thu, 8 Oct 1998 17:01:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23967 for ; Thu, 8 Oct 1998 17:00:50 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id RAA18627; Thu, 8 Oct 1998 17:00:30 -0700 (PDT) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id RAA14041; Thu, 8 Oct 1998 17:00:30 -0700 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id SAA15575; Thu, 8 Oct 1998 18:00:29 -0600 Message-ID: <361D521D.CFF9305C@softweyr.com> Date: Thu, 08 Oct 1998 18:00:29 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Peter Jeremy CC: freebsd-stable@FreeBSD.ORG Subject: Re: Global register variables in gcc and stdio.h?!? References: <98Oct9.071633est.40326@border.alcanet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: % The compiler is a whole lot smarter about register allocation than % you are, especially on an architecture where there aren't any. Peter Jeremy wrote: > Actually, on a true 0 or 1-address architecture, register allocation > is trivial. The real difficulties occur with architectures that have > a small number of registers which aren't quite all general purpose. Like the x86. Remember AX = accumulator, BX = base, CX = counter, DX = destination, SI = source index, DI = destination index, etc? Yes, I KNOW most programmers use SI and DI like they're general purpose registers, but they're really not. I will amend my original statement, at least for x86, to "The compiler is a whole lot better than you at NOT screwing up it's register allocation and getting something out of whack." As was posted in another response, the best way to approach this is to write the code in the most obvious fashion possible, get it completely and thoroughly debugged, then time it to see if it meets it's goals. If so, LEAVE IT ALONE! If not, profile the code to determine where you can do some good, and optimize the top 1 or 2 functions. Repeat until done. Once you start delving into register allocation to solve performance problems, you're getting to the point where you need to isolate the real performance bottleneck and code that (and ONLY that) in assembler, using somebody who's really good. Especially on the fart-brained x86. (Registers? Huh? Why would you want registers, you already have RAM!) -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 18:13:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08610 for freebsd-stable-outgoing; Thu, 8 Oct 1998 18:13:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gwyneth. (gwyneth.gric.com [207.20.139.202]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA08256 for ; Thu, 8 Oct 1998 18:11:59 -0700 (PDT) (envelope-from kris@gwyneth.gric.com) From: kris@gwyneth.gric.com Received: from localhost by gwyneth. (SMI-8.6/SMI-SVR4) id SAA03023; Thu, 8 Oct 1998 18:11:44 -0700 Date: Thu, 8 Oct 1998 18:11:44 -0700 (PDT) To: freebsd-stable@FreeBSD.ORG Subject: Future of -stable? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's something I've been wondering about for a bit but I've never really gotten a straight answer. Currently I'm using 2.2.7-stable, however I just got a new larger drive and I want to install 3.0-beta and follow it through release and on into 3.0-stable if possible. Anyhow I've used cvsup a lot and I'm wondering once 3.0 is released, will there be a 3.0-stable? And does this mean that for a short time there will be a 3.0-stable and a 2.2-stable (till 2.2.8 is released). Or will the 3.0.X development still be called current? Mainly what I want to do is install 3.0-beta and keep up with the 3.0.x tree from there, preferably a the stable version if possible. Any ideas on how/where -stable is going to go? I'm sure I probably would be more well informed had I been around during the 1.0 to 2.0 transition. Any hints or insight would be appreciated. I'm subbed to the list so feel free to reply there if you think I'm not the only one wondering.TIA -Kris Zentner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 19:48:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26906 for freebsd-stable-outgoing; Thu, 8 Oct 1998 19:48:17 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA26885 for ; Thu, 8 Oct 1998 19:48:11 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zRSb3-0003kF-00; Thu, 8 Oct 1998 19:48:01 -0700 Date: Thu, 8 Oct 1998 19:47:58 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: kris@gwyneth.gric.com cc: freebsd-stable@FreeBSD.ORG Subject: Re: Future of -stable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Oct 1998 kris@gwyneth.gric.com wrote: > Here's something I've been wondering about for a bit but I've never really > gotten a straight answer. Currently I'm using 2.2.7-stable, however I just > got a new larger drive and I want to install 3.0-beta and follow it > through release and on into 3.0-stable if possible. Anyhow I've used cvsup > a lot and I'm wondering once 3.0 is released, will there be a 3.0-stable? > And does this mean that for a short time there will be a 3.0-stable and a > 2.2-stable (till 2.2.8 is released). Or will the 3.0.X development still > be called current? Probably. You can still cvsup 2.1-stable to this day. It would probably be a lot of work for somebody to merge 3.0-current with 3.0-stable considering the amount of work 3.0 needs before a 3.1 or 3.0.1 release, so don't expect a 3.0-current/3.0-stable split too soon. > I'm sure I probably would be more well informed had I been around during > the 1.0 to 2.0 transition. Any hints or insight would be appreciated. I'm > subbed to the list so feel free to reply there if you think I'm not the > only one wondering.TIA I was around between 1.1.5.1 and 2.0-Alpha. In fact 1.1.5.1 was the first version I installed. The process was quite a bit different back then, as development on 1.1.x had to abandoned for legal reasons. The -stable branch concept was not created for quite a while after 2.0. > -Kris Zentner Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 21:37:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17357 for freebsd-stable-outgoing; Thu, 8 Oct 1998 21:37:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17311 for ; Thu, 8 Oct 1998 21:37:47 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id VAA03282; Thu, 8 Oct 1998 21:37:36 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <361D930F.6DE4E3DB@gorean.org> Date: Thu, 08 Oct 1998 21:37:35 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-0929 i386) X-Accept-Language: en MIME-Version: 1.0 To: kris@gwyneth.gric.com CC: freebsd-stable@FreeBSD.ORG Subject: Re: Future of -stable? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG kris@gwyneth.gric.com wrote: > > Here's something I've been wondering about for a bit but I've never really > gotten a straight answer. Currently I'm using 2.2.7-stable, however I just > got a new larger drive and I want to install 3.0-beta and follow it > through release and on into 3.0-stable if possible. Anyhow I've used cvsup > a lot and I'm wondering once 3.0 is released, will there be a 3.0-stable? It will be a LONG TIME before 3.0 is stable OR -Stable. > And does this mean that for a short time there will be a 3.0-stable and a > 2.2-stable (till 2.2.8 is released). Or will the 3.0.X development still > be called current? There will eventually be a 3.0-Stable and a 3.x-Current (or maybe a 4.x-Current), but don't count on that any time soon. What the 2.2 branch gets called when 3.x is finally -Stable is also up in the air. > Mainly what I want to do is install 3.0-beta and keep up with the 3.0.x > tree from there, preferably a the stable version if possible. Any ideas on > how/where -stable is going to go? What's your level of experience with freebsd? You may be better off sticking with 2.2 until 3.x goes -Stable. At minimum you should subscribe to the freebsd-current and cvs-all lists and read them for a couple weeks before you make your decision. Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 21:56:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20463 for freebsd-stable-outgoing; Thu, 8 Oct 1998 21:56:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19878 for ; Thu, 8 Oct 1998 21:54:01 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id WAA17293; Thu, 8 Oct 1998 22:53:48 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <361D96DB.3FB6703@softweyr.com> Date: Thu, 08 Oct 1998 22:53:47 -0600 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: kris@gwyneth.gric.com CC: freebsd-stable@FreeBSD.ORG Subject: Re: Future of -stable? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG kris@gwyneth.gric.com wrote: > > Here's something I've been wondering about for a bit but I've never really > gotten a straight answer. Currently I'm using 2.2.7-stable, however I just > got a new larger drive and I want to install 3.0-beta and follow it > through release and on into 3.0-stable if possible. Anyhow I've used cvsup > a lot and I'm wondering once 3.0 is released, will there be a 3.0-stable? > And does this mean that for a short time there will be a 3.0-stable and a > 2.2-stable (till 2.2.8 is released). Or will the 3.0.X development still > be called current? > > Mainly what I want to do is install 3.0-beta and keep up with the 3.0.x > tree from there, preferably a the stable version if possible. Any ideas on > how/where -stable is going to go? > > I'm sure I probably would be more well informed had I been around during > the 1.0 to 2.0 transition. Any hints or insight would be appreciated. I'm > subbed to the list so feel free to reply there if you think I'm not the > only one wondering.TIA It's actually quite simple. The -stable branch is intended to be for production machines, you know, those that cannot crash, actually make money, etc. The 3.0-stable branch will be created when 3.0 is validate to be stable enough to warrant it. Until that time, 2.2.8 and then post 2.2.8 will remain the -stable branch, and then at some point when a rough consensus has been reached that 3.x is ready, the 2.2.x-stable branch will eventually grind to a halt for active development. Experience dictates that 3.0 won't become stable until at least 3.0.2, and maybe 3.0.5. This 3.0 release is pretty amibitious, and has a lot of new, complicated features to test, so if you're in a production environment, it may be a while before a 3.0-stable branch comes out. If you're using FreeBSD for workstations, you'll most likely be able to profitably use 3.0 "out of the box" for most (or all) of your work. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 8 23:41:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07612 for freebsd-stable-outgoing; Thu, 8 Oct 1998 23:41:40 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA07594 for ; Thu, 8 Oct 1998 23:41:33 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zRWEj-0000yd-00; Thu, 8 Oct 1998 23:41:13 -0700 Date: Thu, 8 Oct 1998 23:41:08 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Studded cc: kris@gwyneth.gric.com, freebsd-stable@FreeBSD.ORG Subject: Re: Future of -stable? In-Reply-To: <361D930F.6DE4E3DB@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Oct 1998, Studded wrote: > 4.x-Current), but don't count on that any time soon. What the 2.2 branch > gets called when 3.x is finally -Stable is also up in the air. I don't think so. 2.2-stable is called 2.2-stable and will continue to be called that. 2.1-stable is still very much available too. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 00:19:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12589 for freebsd-stable-outgoing; Fri, 9 Oct 1998 00:19:26 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phmit.demon.co.uk (phmit.demon.co.uk [194.222.15.209]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA12584 for ; Fri, 9 Oct 1998 00:19:24 -0700 (PDT) (envelope-from dom@phmit.demon.co.uk) Received: from voodoo.pandhm.co.uk [192.15.143.228] by phmit.demon.co.uk with esmtp (Exim 1.82 #1) id 0zRWpY-0002tL-00; Fri, 9 Oct 1998 08:19:16 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 1.92 #1) id 0zRWrW-0005rq-00; Fri, 9 Oct 1998 08:21:18 +0100 To: francisco@natserv.com cc: freebsd-stable@FreeBSD.ORG Subject: Re: Recommendations on updating /etc for -stable X-Mailer: nmh v0.26 X-Colour: Green Organization: Palmer & Harvey McLane In-reply-to: Francisco Reyes's message of "Thu, 08 Oct 1998 07:11:15 -0000" <199810081110.HAA03731@federation.addy.com> Date: Fri, 09 Oct 1998 08:21:18 +0100 From: Dom Mitchell Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8 October 1998, Francisco Reyes proclaimed: > I am seeking suggestions on how to best update /etc/ while tracking stable. > Any scripts someone has found useful? I find that a little script to descend over /etc and run ident over that and it's equivalent in /usr/src/etc works wonders. Then I use Emacs' ediff mode to update any out of date files in question. It's not the most efficient solution (in terms of your time), but it works pretty well. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Xerox studies suggest that most people print out electronic mail that is longer than half a page; paper use rises by 40 percent in offices that introduce E-mail." -- CCM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 00:42:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16684 for freebsd-stable-outgoing; Fri, 9 Oct 1998 00:42:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16591 for ; Fri, 9 Oct 1998 00:41:19 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id AAA05336; Fri, 9 Oct 1998 00:41:03 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: William Bloom cc: freebsd-stable@FreeBSD.ORG, chad@rez.com Subject: Re: Update Needed to mtree /usr Spec In-reply-to: Your message of "Thu, 08 Oct 1998 16:15:52 PDT." Date: Fri, 09 Oct 1998 00:41:03 -0700 Message-ID: <5332.907918863@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This in turn prevents a FreeBSD release from being generated (with > NODOCS disabled). > > Perhaps this is a work-in-progress and I've just been caught trying to > generate a release at just the wrong moment. In that case, I should Well, it's more a case that this was done in -current but hadn't been back-ported yet. I just merged the relevant changes into -stable and you should be able to build your !NODOCS releases again. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 03:58:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA08953 for freebsd-stable-outgoing; Fri, 9 Oct 1998 03:58:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from interix.triplan.com ([194.64.78.208]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA08944 for ; Fri, 9 Oct 1998 03:58:14 -0700 (PDT) (envelope-from Marc.Gutschner@interix.triplan.com) Received: from Triplan.COM (tri05.tri_bs_supp.triplan.com [192.168.1.153]) by interix.triplan.com (8.7.5/8.7.3) with ESMTP id MAA03981 for ; Fri, 9 Oct 1998 12:54:52 +0200 Message-ID: <361DEC25.30065DCC@Triplan.COM> Date: Fri, 09 Oct 1998 12:57:41 +0200 From: Marc Gutschner Organization: Triplan Ingenieur GmbH X-Mailer: Mozilla 4.06 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Is 'xntpd' broken in -stable? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have 2 machines running -stable (last cvsup yesterday), that seem to have a broken 'xntpd'... I've set up a minimal ntp.conf in /etc that consists of the following lines: server 192.168.1.158 disable auth I have a HP9000 at home that runs 'xntpd' with broadcast 192.168.1.255 version 3 The 'xntpd' on the HP can be queried from the FreeBSD machines using 'xntpdc', so I presume it's running fine. If I try to fire up 'xntpd' on the FreeBSD box as a client, it reads the config, tells me something about initial adjustment values, forks and (seems to) dies ;( A 'ktrace xntpd' just shows the 'fork()' as the last call and the forked daemon never shows up in the process list. Am I doing something totally wrong here ? I've tried the same on my DECstations with NetBSD (same ntp.conf) and they just do what they are paid for ;) Any hints appreciated... MTIA, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 04:55:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17948 for freebsd-stable-outgoing; Fri, 9 Oct 1998 04:55:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17943 for ; Fri, 9 Oct 1998 04:55:15 -0700 (PDT) (envelope-from rkw@Dataplex.NET) Received: from [208.2.87.5] (user5.dataplex.net [208.2.87.5]) by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id GAA13440; Fri, 9 Oct 1998 06:55:27 -0500 (CDT) (envelope-from rkw@dataplex.net) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <361D930F.6DE4E3DB@gorean.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 9 Oct 1998 06:52:28 -0500 To: Studded From: Richard Wackerbarth Subject: Re: Future of -stable? Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:37 PM -0500 10/8/98, Studded wrote: >kris@gwyneth.gric.com wrote: >> >> Here's something I've been wondering about for a bit but I've never really >> gotten a straight answer. Currently I'm using 2.2.7-stable, however I just >> got a new larger drive and I want to install 3.0-beta and follow it >> through release and on into 3.0-stable if possible. Anyhow I've used cvsup >> a lot and I'm wondering once 3.0 is released, will there be a 3.0-stable? > > It will be a LONG TIME before 3.0 is stable OR -Stable. > >> And does this mean that for a short time there will be a 3.0-stable and a >> 2.2-stable (till 2.2.8 is released). Or will the 3.0.X development still >> be called current? > > There will eventually be a 3.0-Stable and a 3.x-Current (or maybe a >4.x-Current), but don't count on that any time soon. What the 2.2 branch >gets called when 3.x is finally -Stable is also up in the air. I will again renew my recommendation that we drop "-Stable" as a "real" name and instead make it simply an alias to the most recent branch that has been so Christened. The "real" names would be 2.2, 3.0, etc. At any point in time, here would be a couple of ways to follow a recent branch. A user could then "register" under the name that follows his intent. Right now, "3.0", "AVANTEGUARD", and "PRERELEASE" are the same. "2.2", "RELEASE", and "PRODUCTION" are a different train. If I get on the "AVANTEGUARD" train, I automatically move away from "3.0" when the split occurs. However, if I instead choose the "3.0" train, I can ride it as long as I like without having it jerked out from under me. Similarly, those on "2.2" train would see a seamless transition as they get gently shuffled off onto the "LEGACY" train. In a similar manner, I would like to see an alias system on the installation sites so that I could set up a boot floppy that would automatically pick up the "LATEST-SNAP" without manually editing the installation request on a daily basis. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 09:11:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26270 for freebsd-stable-outgoing; Fri, 9 Oct 1998 09:11:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phoenix.welearn.com.au (suebla.lnk.telstra.net [139.130.44.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26187 for ; Fri, 9 Oct 1998 09:11:13 -0700 (PDT) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.1/8.9.0) id CAA20885; Sat, 10 Oct 1998 02:10:33 +1000 (EST) Message-ID: <19981010021029.28185@welearn.com.au> Date: Sat, 10 Oct 1998 02:10:29 +1000 From: Sue Blake To: kris@gwyneth.gric.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Future of -stable? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from kris@gwyneth.gric.com on Thu, Oct 08, 1998 at 06:11:44PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 08, 1998 at 06:11:44PM -0700, kris@gwyneth.gric.com wrote: > Here's something I've been wondering about for a bit but I've never really > gotten a straight answer. Currently I'm using 2.2.7-stable, however I just > got a new larger drive and I want to install 3.0-beta and follow it > through release and on into 3.0-stable if possible. Anyhow I've used cvsup > a lot and I'm wondering once 3.0 is released, will there be a 3.0-stable? > And does this mean that for a short time there will be a 3.0-stable and a > 2.2-stable (till 2.2.8 is released). Or will the 3.0.X development still > be called current? > > Mainly what I want to do is install 3.0-beta and keep up with the 3.0.x > tree from there, preferably a the stable version if possible. Any ideas on > how/where -stable is going to go? > > I'm sure I probably would be more well informed had I been around during > the 1.0 to 2.0 transition. Any hints or insight would be appreciated. I'm > subbed to the list so feel free to reply there if you think I'm not the > only one wondering.TIA No! You're not the only one! I've been lurking here for months, understanding very little, too confused to form any sensible questions, hoping that someone will ask them for me and the answers will come back in easy-speak. Your question is one I wanted to ask but didn't know how. There's always someone else who's at least as confused as you are and dying to see the answers to your questions. -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 09:47:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02932 for freebsd-stable-outgoing; Fri, 9 Oct 1998 09:47:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02919 for ; Fri, 9 Oct 1998 09:47:00 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id JAA23355; Fri, 9 Oct 1998 09:46:29 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <361E3DE4.39F057F4@gorean.org> Date: Fri, 09 Oct 1998 09:46:28 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-0929 i386) X-Accept-Language: en MIME-Version: 1.0 To: Marc Gutschner CC: freebsd-stable@FreeBSD.ORG Subject: Re: Is 'xntpd' broken in -stable? References: <361DEC25.30065DCC@Triplan.COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Gutschner wrote: > If I try to fire up 'xntpd' on > the FreeBSD box as a client, it reads the config, tells me something > about initial adjustment values, forks and (seems to) dies That "something" it tells you is actually valuable diagnostic info. It's telling you that xntpd can't set the time because it's so far off now that xntpd can't handle it. So, before you start xntpd you need to issue an 'ntpdate whatever.your.primary.time.host.is' then you should be able to start xntpd. Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 10:32:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09104 for freebsd-stable-outgoing; Fri, 9 Oct 1998 10:32:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09025; Fri, 9 Oct 1998 10:32:27 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id KAA19668; Fri, 9 Oct 1998 10:32:10 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <361E4899.965A3B0D@gorean.org> Date: Fri, 09 Oct 1998 10:32:09 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-0929 i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Questions , Stable Subject: URGENT HELP NEEDED: un-DEVFS'ing -Stable Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a customer (not me, honest :) who thought they'd "save me time" and hacked their own kernel, enabling DEVFS on a -Stable system. Now a kernel not using DEVFS won't boot, so I need to know how to undo their damage. I'm guessing that it's just a matter of doing a MAKEDEV in single user mode with the new kernel but I have NO experience with DEVFS so any help would be very well appreciated. Thanks, Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 10:46:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12571 for freebsd-stable-outgoing; Fri, 9 Oct 1998 10:46:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12497; Fri, 9 Oct 1998 10:46:39 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id KAA25581; Fri, 9 Oct 1998 10:46:30 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <361E4BF5.2CFE6F7D@gorean.org> Date: Fri, 09 Oct 1998 10:46:29 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-0929 i386) X-Accept-Language: en MIME-Version: 1.0 To: Jeff Kletsky , freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: fwtk and skey authorization References: <361E3F10.9F79A8A0@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Studded wrote: > I wonder if that's related to the problem I had with a make world of > the latest -Stable: Actually, I might have jumped the gun on this. I'm working on more than one system right now and I thought this one was the one I started with a clean /usr/obj, but I was mistaken. If I don't follow up on this assume that my previous post was due solely to lack of sleep. :-/ Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 10:57:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14728 for freebsd-stable-outgoing; Fri, 9 Oct 1998 10:57:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14719 for ; Fri, 9 Oct 1998 10:57:26 -0700 (PDT) (envelope-from randy@rip.psg.com) Received: (from randy@localhost) by rip.psg.com (8.8.8/8.8.8) id KAA10402; Fri, 9 Oct 1998 10:57:50 -0700 (PDT) (envelope-from randy) Date: Fri, 9 Oct 1998 10:57:50 -0700 (PDT) Message-Id: <199810091757.KAA10402@rip.psg.com> From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Studded Cc: Marc Gutschner , freebsd-stable@FreeBSD.ORG Subject: Re: Is 'xntpd' broken in -stable? References: <361DEC25.30065DCC@Triplan.COM> <361E3DE4.39F057F4@gorean.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > issue an 'ntpdate whatever.your.primary.time.host.is' then you should be > able to start xntpd. Oct 9 10:56:57 rip ntpdate: Can't set time of day: Operation not permitted randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 11:14:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18234 for freebsd-stable-outgoing; Fri, 9 Oct 1998 11:14:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18185 for ; Fri, 9 Oct 1998 11:14:09 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA01001; Fri, 9 Oct 1998 11:03:21 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <361E4FE8.2EF1B5DA@gorean.org> Date: Fri, 09 Oct 1998 11:03:20 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-0929 i386) X-Accept-Language: en MIME-Version: 1.0 To: Randy Bush CC: Marc Gutschner , freebsd-stable@FreeBSD.ORG Subject: Re: Is 'xntpd' broken in -stable? References: <361DEC25.30065DCC@Triplan.COM> <361E3DE4.39F057F4@gorean.org> <199810091757.KAA10402@rip.psg.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randy Bush wrote: > > > issue an 'ntpdate whatever.your.primary.time.host.is' then you should be > > able to start xntpd. > > Oct 9 10:56:57 rip ntpdate: Can't set time of day: Operation not permitted Hmmm.. that looks like you weren't root at the time. Make sure that you're root, that there is no ntp/xntpd server running, and type: ntpdate ucsd.ucsd.edu That should get it. If it doesn't, something is dreadfully wrong. Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 11:45:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23413 for freebsd-stable-outgoing; Fri, 9 Oct 1998 11:45:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23392 for ; Fri, 9 Oct 1998 11:44:59 -0700 (PDT) (envelope-from randy@rip.psg.com) Received: (from randy@localhost) by rip.psg.com (8.8.8/8.8.8) id LAA11689; Fri, 9 Oct 1998 11:45:30 -0700 (PDT) (envelope-from randy) Date: Fri, 9 Oct 1998 11:45:30 -0700 (PDT) Message-Id: <199810091845.LAA11689@rip.psg.com> From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Studded Cc: Marc Gutschner , freebsd-stable@FreeBSD.ORG Subject: Re: Is 'xntpd' broken in -stable? References: <361DEC25.30065DCC@Triplan.COM> <361E3DE4.39F057F4@gorean.org> <199810091757.KAA10402@rip.psg.com> <361E4FE8.2EF1B5DA@gorean.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> issue an 'ntpdate whatever.your.primary.time.host.is' then you should be >>> able to start xntpd. >> Oct 9 10:56:57 rip ntpdate: Can't set time of day: Operation not permitted > Hmmm.. that looks like you weren't root at the time. Make sure that > you're root, that there is no ntp/xntpd server running, and type: > ntpdate ucsd.ucsd.edu > That should get it. If it doesn't, something is dreadfully wrong. i was root. xntpd was not running. if it was, i would have gotten the 'port in use' message. xntpd gives me the analogous message. i am at security level 2. randy rip:/root# id uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest) rip:/root# ntpdate ucsd.ucsd.edu 9 Oct 11:43:03 ntpdate: no server suitable for synchronization found rip:/root# ntpdate psg.com rip:/root# Oct 9 11:43:10 rip ntpdate: Can't set time of day: Operation not permitted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 11:47:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23695 for freebsd-stable-outgoing; Fri, 9 Oct 1998 11:47:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23614 for ; Fri, 9 Oct 1998 11:46:37 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:kJXbwVT6ZJ2z5Ddshn6Nonn8H5dRcGUU@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id UAA12915; Fri, 9 Oct 1998 20:45:54 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810091845.UAA12915@gratis.grondar.za> To: Richard Wackerbarth cc: Studded , freebsd-stable@FreeBSD.ORG Subject: Re: Future of -stable? In-Reply-To: Your message of " Fri, 09 Oct 1998 06:52:28 EST." References: Date: Fri, 09 Oct 1998 20:45:53 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Wackerbarth wrote: > I will again renew my recommendation that we drop "-Stable" as a "real" name > and instead make it simply an alias to the most recent branch that has been > so Christened. The "real" names would be 2.2, 3.0, etc. Huh? How will that change reality? The last "STABLE" was on the 2.1.N branch, and it has already been clearly stated that when 2.2.M is no longer supported 3.0.J will be "STABLE". M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 12:09:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26712 for freebsd-stable-outgoing; Fri, 9 Oct 1998 12:09:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26701 for ; Fri, 9 Oct 1998 12:08:57 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id MAA06830; Fri, 9 Oct 1998 12:08:25 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <361E5F28.1DE06387@gorean.org> Date: Fri, 09 Oct 1998 12:08:24 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-0929 i386) X-Accept-Language: en MIME-Version: 1.0 To: Randy Bush CC: Marc Gutschner , freebsd-stable@FreeBSD.ORG Subject: Re: Is 'xntpd' broken in -stable? References: <361DEC25.30065DCC@Triplan.COM> <361E3DE4.39F057F4@gorean.org> <199810091757.KAA10402@rip.psg.com> <361E4FE8.2EF1B5DA@gorean.org> <199810091845.LAA11689@rip.psg.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randy Bush wrote: > xntpd gives me the analogous message. i am at security level 2. Well that's probably it then. :) Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 12:11:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27264 for freebsd-stable-outgoing; Fri, 9 Oct 1998 12:11:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27213 for ; Fri, 9 Oct 1998 12:11:14 -0700 (PDT) (envelope-from randy@rip.psg.com) Received: (from randy@localhost) by rip.psg.com (8.8.8/8.8.8) id MAA12445; Fri, 9 Oct 1998 12:11:47 -0700 (PDT) (envelope-from randy) Date: Fri, 9 Oct 1998 12:11:47 -0700 (PDT) Message-Id: <199810091911.MAA12445@rip.psg.com> From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Studded Cc: Marc Gutschner , freebsd-stable@FreeBSD.ORG Subject: Re: Is 'xntpd' broken in -stable? References: <361DEC25.30065DCC@Triplan.COM> <361E3DE4.39F057F4@gorean.org> <199810091757.KAA10402@rip.psg.com> <361E4FE8.2EF1B5DA@gorean.org> <199810091845.LAA11689@rip.psg.com> <361E5F28.1DE06387@gorean.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> xntpd gives me the analogous message. i am at security level 2. > Well that's probably it then. :) i.e. one can not run ntp at security level 2? should i like this? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 12:29:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00239 for freebsd-stable-outgoing; Fri, 9 Oct 1998 12:29:40 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00233 for ; Fri, 9 Oct 1998 12:29:38 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id MAA14061; Fri, 9 Oct 1998 12:27:41 -0700 (PDT) Message-Id: <199810091927.MAA14061@implode.root.com> To: Studded cc: Randy Bush , Marc Gutschner , freebsd-stable@FreeBSD.ORG Subject: Re: Is 'xntpd' broken in -stable? In-reply-to: Your message of "Fri, 09 Oct 1998 11:03:20 PDT." <361E4FE8.2EF1B5DA@gorean.org> From: David Greenman Reply-To: dg@root.com Date: Fri, 09 Oct 1998 12:27:41 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > issue an 'ntpdate whatever.your.primary.time.host.is' then you should be >> > able to start xntpd. >> >> Oct 9 10:56:57 rip ntpdate: Can't set time of day: Operation not permitted > > Hmmm.. that looks like you weren't root at the time. Make sure that >you're root, that there is no ntp/xntpd server running, and type: > >ntpdate ucsd.ucsd.edu > > That should get it. If it doesn't, something is dreadfully wrong. I think Randy's question is: Does xntpd work when securelevel == 2? The answer is "sort of". With securelevel > 1 you can only speed up or slow down the clock via adjtime(); the system will not let you set the time backwards (e.g. with settimeofday). This is a security feature which prevents people from changing the time of day, touching a file, and then setting it back (and thus allow you to reset the inode change time into the past). This restriction was adopted from NetBSD in rev 1.23 of sys/kern/kern_time.c. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 12:31:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00587 for freebsd-stable-outgoing; Fri, 9 Oct 1998 12:31:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from beach.frankfurt.netsurf.de (beach.frankfurt.netsurf.de [194.64.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00557 for ; Fri, 9 Oct 1998 12:30:52 -0700 (PDT) (envelope-from marc@Frankfurt.NetSurf.DE) Received: from zaphod.magrathea.frankfurt.netsurf.de (deck-195.frankfurt.netsurf.de [194.64.181.227]) by beach.frankfurt.netsurf.de (8.8.5/8.8.5) with SMTP id VAA25074; Fri, 9 Oct 1998 21:30:05 +0200 (MET DST) Date: Fri, 9 Oct 1998 21:29:58 +0200 (CEST) From: "Marc.Gutschner" X-Sender: marc@zaphod.magrathea.frankfurt.netsurf.de Reply-To: Marc.Gutschner@Frankfurt.NetSurf.DE To: Studded cc: Randy Bush , Marc Gutschner , freebsd-stable@FreeBSD.ORG Subject: Re: Is 'xntpd' broken in -stable? In-Reply-To: <361E5F28.1DE06387@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Oct 1998, Studded wrote: > Randy Bush wrote: > > > xntpd gives me the analogous message. i am at security level 2. > > Well that's probably it then. :) > mmhmmm, I have done some more "experiments" on my local net and had some rather confusing results. I kept the HP as the main time server with a config like this: broadcast 192.168.1.255 version 3 authenticate no Doing 'ntpdate ford' (that's the HP) gave 'no suitable timeservers found' Then I tried to reverse the roles, i.e. FreeBSD as main time server with broadcast 192.168.1.255 version 3 disable auth Again, no go on neither an HP-UX nor another FreeBSD client. When running 'xntpd' with the client config server wowbagger version 3 broadcastclient yes authenticate no and debug flags on the HP I keep getting output like this: transmit to 192.168.1.161 input_handler: fd=14 length 48 from c0a801a1 192.168.1.161 receive from 192.168.1.161 poll_update(192.168.1.161, 6, 1) invalid packet header 192.168.1.161 20 An 'ntpdate ucsd.ucsd.edu' (as suggested) worked fine... But now 'xntpd' refuses to start - as in the beginnig of this whole thing. The only traces I find is the following in /var/log/messages xntpd version=3.4e (beta multicast); Tue Sep 15 02:26:00 CEST 1998 (1) tickadj = 5, tick = 10000, tvu_maxslew = 495 Now I'm quite stranded ;) Is the above of any use to those with more knowledge ? MTIA, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 12:54:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05251 for freebsd-stable-outgoing; Fri, 9 Oct 1998 12:54:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05151 for ; Fri, 9 Oct 1998 12:53:58 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) id 0zRiaA-0004wG-00; Fri, 9 Oct 1998 14:52:10 -0500 X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199810091911.MAA12445@rip.psg.com> References: <361DEC25.30065DCC@Triplan.COM> <361E3DE4.39F057F4@gorean.org> <199810091757.KAA10402@rip.psg.com> <361E4FE8.2EF1B5DA@gorean.org> <199810091845.LAA11689@rip.psg.com> <361E5F28.1DE06387@gorean.org> <199810091911.MAA12445@rip.psg.com> Subject: Re: Is 'xntpd' broken in -stable? To: Randy Bush cc: Studded , Marc Gutschner , freebsd-stable@FreeBSD.ORG Date: Fri, 09 Oct 1998 14:52:10 -0500 Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- I don't see anything obvious that should make this happen... presumably xntpd uses adjtime or ntp_adjtime, and those use the normal superuser check routine ``suser'', which doesn't distinguish between different security levels. Randy, can you run ``truss ntpdate yada yada yada'' so we can see which system call is returning EPERM? Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org On 9 October 1998 at 12:11, Randy Bush wrote: > >> xntpd gives me the analogous message. i am at security level 2. > > Well that's probably it then. :) > > i.e. one can not run ntp at security level 2? should i like this? > > randy > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNh5pajeRhT8JRySpAQGQiQQAs2eF5b00Jg4kgCRxO2dwYn5X88ANWSUA eKjKPT89rRjpdInPqCHJ5Y1ddAnyzQ0AlBMIOXYQfGMmBU4z7vOw9OwkNxxoy4fA 2b9+gpV9mw9vCbaz/jXFE5+hawwbj6t+mXdk+zuB8BR1F1SZw9t/rHm/+XRljQyB JMl8Fm0qSbw= =l8BL -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 12:59:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06438 for freebsd-stable-outgoing; Fri, 9 Oct 1998 12:59:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06413 for ; Fri, 9 Oct 1998 12:58:52 -0700 (PDT) (envelope-from randy@rip.psg.com) Received: (from randy@localhost) by rip.psg.com (8.8.8/8.8.8) id MAA13804; Fri, 9 Oct 1998 12:59:28 -0700 (PDT) (envelope-from randy) Date: Fri, 9 Oct 1998 12:59:28 -0700 (PDT) Message-Id: <199810091959.MAA13804@rip.psg.com> From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jacques Vidrine Cc: Studded , Marc Gutschner , freebsd-stable@FreeBSD.ORG Subject: Re: Is 'xntpd' broken in -stable? References: <361DEC25.30065DCC@Triplan.COM> <361E3DE4.39F057F4@gorean.org> <199810091757.KAA10402@rip.psg.com> <361E4FE8.2EF1B5DA@gorean.org> <199810091845.LAA11689@rip.psg.com> <361E5F28.1DE06387@gorean.org> <199810091911.MAA12445@rip.psg.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Randy, can you run ``truss ntpdate yada yada yada'' so we can > see which system call is returning EPERM? had problems with the yada yada server, so used a local one. :-) randy rip.psg.com:/root# id uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest) rip.psg.com:/root# truss ntpdate psg.com syscall open("/usr/libexec/ld.so",0,00) returns 3 (0x3) syscall read(0x3,0xefbfdb14,0x20) returns 32 (0x20) syscall mmap(0x0,69632,0x5,0x2,3,0x0) returns 536907776 (0x20009000) syscall mmap(0x2001a000,8192,0x3,0x12,3,0x11000) returns 536977408 (0x2001a000) syscall getuid() returns 0 (0x0) syscall geteuid() returns 0 (0x0) syscall getgid() returns 0 (0x0) syscall getegid() returns 0 (0x0) syscall break(0xe000) returns 0 (0x0) syscall open("/var/run/ld.so.hints",0,00) returns 4 (0x4) syscall read(0x4,0xefbfda58,0x20) returns 32 (0x20) syscall mmap(0x0,8586,0x1,0x1,4,0x0) returns 536985600 (0x2001c000) syscall close(4) returns 0 (0x0) syscall stat("/usr/lib/aout/libc.so.3.1",0xefbfda0c) returns 0 (0x0) syscall stat("/usr/lib/aout/libc.so.3.1",0xefbfda34) returns 0 (0x0) syscall open("/usr/lib/aout/libc.so.3.1",0,00) returns 4 (0x4) syscall read(0x4,0xefbfda14,0x20) returns 32 (0x20) syscall mmap(0x0,513076,0x5,0x2,4,0x0) returns 536997888 (0x2001f000) syscall close(4) returns 0 (0x0) syscall mprotect(0x2008b000,0x4000,0x7) returns 0 (0x0) syscall mmap(0x2008f000,54324,0x7,0x1012,-1,0x0) returns 537456640 (0x2008f000) syscall break(0xf000) returns 0 (0x0) syscall break(0x10000) returns 0 (0x0) syscall break(0x11000) returns 0 (0x0) syscall munmap(0x2001c000,0x218a) returns 0 (0x0) syscall close(3) returns 0 (0x0) syscall readlink("/etc/malloc.conf",0xefbfda34,63) errno 2 'No such file or directory' syscall mmap(0x0,4096,0x3,0x1002,-1,0x0) returns 536985600 (0x2001c000) syscall break(0x12000) returns 0 (0x0) syscall break(0x13000) returns 0 (0x0) syscall open("/etc/host.conf",0,0666) returns 3 (0x3) syscall fstat(3,0xefbfd55c) returns 0 (0x0) syscall break(0x15000) returns 0 (0x0) syscall read(0x3,0x13000,0x2000) returns 129 (0x81) syscall read(0x3,0x13000,0x2000) returns 0 (0x0) syscall close(3) returns 0 (0x0) syscall madvise(0x13000,0x2000,0x5) returns 0 (0x0) syscall open("/etc/hosts",0,0666) returns 3 (0x3) syscall gettimeofday(0xefbfd5b4,0x0) returns 0 (0x0) syscall getpid() returns 13774 (0x35ce) syscall open("/etc/resolv.conf",0,0666) returns 4 (0x4) syscall fstat(4,0xefbfd4f4) returns 0 (0x0) syscall read(0x4,0x13000,0x2000) returns 61 (0x3d) syscall read(0x4,0x13000,0x2000) returns 0 (0x0) syscall close(4) returns 0 (0x0) syscall madvise(0x13000,0x2000,0x5) returns 0 (0x0) syscall fstat(3,0xefbfd94c) returns 0 (0x0) syscall read(0x3,0x13000,0x2000) returns 1135 (0x46f) syscall close(3) returns 0 (0x0) syscall madvise(0x13000,0x2000,0x5) returns 0 (0x0) syscall socket(0x2,0x2,0x0) returns 3 (0x3) syscall bind(0x3,0xefbfda94,0x10) returns 0 (0x0) syscall fcntl(0x3,0x4,0x4) returns 0 (0x0) syscall sigaction(0xe,0xefbfda78,0x0) returns 0 (0x0) syscall setitimer(0x0,0xefbfda94,0x0) returns 0 (0x0) syscall setpriority(0x0,0x0,0xfffffff4) returns 0 (0x0) SIGNAL 14 SIGNAL 14 SIGNAL 14 syscall select(0x4,0xefbfdac0,0x0,0x0,0x0) errno 4 'Interrupted system call' syscall sigreturn(0xefbfda40) errno 4 'Interrupted system call' syscall gettimeofday(0xefbfda28,0x0) returns 0 (0x0) syscall sendto(0x3,0xefbfda50,0x30,0x0,0x13000,0x10) returns 48 (0x30) syscall select(0x4,0xefbfdac0,0x0,0x0,0x0) returns 1 (0x1) syscall select(0x4,0xefbfda24,0x0,0x0,0xefbfda1c) returns 1 (0x1) syscall gettimeofday(0xefbfd990,0x0) returns 0 (0x0) syscall recvfrom(0x3,0x1449c,0x44,0x0,0x14474,0xefbfd9ac) returns 48 (0x30) syscall select(0x4,0xefbfda24,0x0,0x0,0xefbfda1c) returns 0 (0x0) syscall gettimeofday(0xefbfd9d8,0x0) returns 0 (0x0) syscall sendto(0x3,0xefbfda00,0x30,0x0,0x13000,0x10) returns 48 (0x30) syscall select(0x4,0xefbfdac0,0x0,0x0,0x0) returns 1 (0x1) syscall select(0x4,0xefbfda24,0x0,0x0,0xefbfda1c) returns 1 (0x1) syscall gettimeofday(0xefbfd990,0x0) returns 0 (0x0) syscall recvfrom(0x3,0x1449c,0x44,0x0,0x14474,0xefbfd9ac) returns 48 (0x30) syscall select(0x4,0xefbfda24,0x0,0x0,0xefbfda1c) returns 0 (0x0) syscall gettimeofday(0xefbfd9d8,0x0) returns 0 (0x0) syscall sendto(0x3,0xefbfda00,0x30,0x0,0x13000,0x10) returns 48 (0x30) syscall select(0x4,0xefbfdac0,0x0,0x0,0x0) returns 1 (0x1) syscall select(0x4,0xefbfda24,0x0,0x0,0xefbfda1c) returns 1 (0x1) syscall gettimeofday(0xefbfd990,0x0) returns 0 (0x0) syscall recvfrom(0x3,0x1449c,0x44,0x0,0x14474,0xefbfd9ac) returns 48 (0x30) syscall select(0x4,0xefbfda24,0x0,0x0,0xefbfda1c) returns 1 (0x1) syscall gettimeofday(0xefbfd990,0x0) returns 0 (0x0) syscall recvfrom(0x3,0x1426c,0x44,0x0,0x14244,0xefbfd9ac) returns 48 (0x30) syscall select(0x4,0xefbfda24,0x0,0x0,0xefbfda1c) returns 0 (0x0) syscall gettimeofday(0xefbfd9d8,0x0) returns 0 (0x0) syscall sendto(0x3,0xefbfda00,0x30,0x0,0x13000,0x10) returns 48 (0x30) syscall select(0x4,0xefbfdac0,0x0,0x0,0x0) returns 1 (0x1) syscall select(0x4,0xefbfda24,0x0,0x0,0xefbfda1c) returns 1 (0x1) syscall gettimeofday(0xefbfd990,0x0) returns 0 (0x0) syscall recvfrom(0x3,0x1449c,0x44,0x0,0x14474,0xefbfd9ac) returns 48 (0x30) syscall select(0x4,0xefbfda24,0x0,0x0,0xefbfda1c) returns 0 (0x0) syscall gettimeofday(0xefbfda74,0x0) returns 0 (0x0) syscall settimeofday(0xefbfda74,0x0) errno 1 'Operation not permitted' syscall gettimeofday(0xefbfcddc,0x0) returns 0 (0x0) syscall break(0x16000) returns 0 (0x0) syscall access(0x2005b3bb,0x4) returns 0 (0x0) syscall open("/etc/localtime",0,04002130140) returns 4 (0x4) syscall fstat(4,0xefbfcd24) returns 0 (0x0) syscall read(0x4,0xefbfaa18,0x1f08) returns 1000 (0x3e8) syscall close(4) returns 0 (0x0) syscall madvise(0x15000,0x1000,0x5) returns 0 (0x0) syscall socket(0x1,0x2,0x0) returns 4 (0x4) syscall fcntl(0x4,0x2,0x1) returns 0 (0x0) syscall connect(0x4,0xefbfcd64,0x6a) returns 0 (0x0) syscall sendto(Oct 9 12:54:57 rip last message repeated 2 times 0x4,0xefbfd240Oct 9 12:58:19 rip ntpdate: Can't set time of day: Operation not permitted ,0x4b,0x0,0x0,0x0) returns 75 (0x4b) syscall exit(0x0) process exit, rval = 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 13:28:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11708 for freebsd-stable-outgoing; Fri, 9 Oct 1998 13:28:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gras-varg.worldgate.com (gras-varg.worldgate.com [198.161.84.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11696; Fri, 9 Oct 1998 13:27:52 -0700 (PDT) (envelope-from skafte@gras-varg.worldgate.com) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.9.1a/8.9.1) id OAA22257; Fri, 9 Oct 1998 14:27:42 -0600 (MDT) Message-ID: <19981009142742.A22107@worldgate.com> Date: Fri, 9 Oct 1998 14:27:42 -0600 From: Greg Skafte To: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: ipfw broken? ... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a 2.2.7-stable machince acting as a router. I'm using ipfw to count traffic + do antispoofing on each interface. it seems that ipfw count seems confused, ie ipfw -a l shows 02000 0 0 count ip from any to any via de2 yet i'm see packets going in and out via tcpdump. Similar on other interfaces. Accuracy of packet accounting is important to me since I pay per packet.... -- Email: skafte@worldgate.com Voice: +403 413 1910 Fax: +403 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 13:43:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15480 for freebsd-stable-outgoing; Fri, 9 Oct 1998 13:43:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15412; Fri, 9 Oct 1998 13:43:24 -0700 (PDT) (envelope-from cschuber@passer.osg.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id NAA18751; Fri, 9 Oct 1998 13:43:08 -0700 (PDT) Message-Id: <199810092043.NAA18751@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdh18736; Fri Oct 9 13:42:50 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group X-Sender: cschuber To: Studded cc: FreeBSD Questions , Stable Subject: Re: URGENT HELP NEEDED: un-DEVFS'ing -Stable In-reply-to: Your message of "Fri, 09 Oct 1998 10:32:09 PDT." <361E4899.965A3B0D@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Oct 1998 13:42:50 -0700 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a customer (not me, honest :) who thought they'd "save me time" > and hacked their own kernel, enabling DEVFS on a -Stable system. Now a > kernel not using DEVFS won't boot, so I need to know how to undo their > damage. I'm guessing that it's just a matter of doing a MAKEDEV in > single user mode with the new kernel but I have NO experience with DEVFS > so any help would be very well appreciated. You've got three options, probably more: 1. When the boot prompt is displayed (assuming you have a generic kernel), enter kernel.GENERIC -s, or if your old kernel is still around, enter kernel.old at the boot prompt. Then build a new kernel. 2. Boot from floppy, choose the fixit option and insert either CDROM 2 or a fixit floppy in the appropriate drive; then build a new kernel. 3, Boot from floppy, mount your filesystems under /mnt, chroot /mnt, then build a new kernel. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 13:50:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17004 for freebsd-stable-outgoing; Fri, 9 Oct 1998 13:50:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA16963; Fri, 9 Oct 1998 13:50:25 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id TAA14137; Fri, 9 Oct 1998 19:49:22 +0100 From: Luigi Rizzo Message-Id: <199810091849.TAA14137@labinfo.iet.unipi.it> Subject: Re: ipfw broken? ... To: skafte@worldgate.com (Greg Skafte) Date: Fri, 9 Oct 1998 19:49:22 +0100 (MET) Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <19981009142742.A22107@worldgate.com> from "Greg Skafte" at Oct 9, 98 02:27:23 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got a 2.2.7-stable machince acting as a router. > > I'm using ipfw to count traffic + do antispoofing on each interface. > > it seems that ipfw count seems confused, ie ipfw -a l shows > 02000 0 0 count ip from any to any via de2 did it work before the dummynet integration ? do you have other rules before which could match ? luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 13:54:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17473 for freebsd-stable-outgoing; Fri, 9 Oct 1998 13:54:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gras-varg.worldgate.com (gras-varg.worldgate.com [198.161.84.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17388; Fri, 9 Oct 1998 13:53:48 -0700 (PDT) (envelope-from skafte@gras-varg.worldgate.com) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.9.1a/8.9.1) id OAA22428; Fri, 9 Oct 1998 14:53:17 -0600 (MDT) Message-ID: <19981009145317.B22107@worldgate.com> Date: Fri, 9 Oct 1998 14:53:17 -0600 From: Greg Skafte To: Luigi Rizzo Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: ipfw broken? ... References: <19981009142742.A22107@worldgate.com> <199810091849.TAA14137@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810091849.TAA14137@labinfo.iet.unipi.it>; from Luigi Rizzo on Fri, Oct 09, 1998 at 07:49:22PM +0100 Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Luigi Rizzo (luigi@labinfo.iet.unipi.it) On Subject: Re: ipfw broken? ... Date: Fri, Oct 09, 1998 at 07:49:22PM +0100 > > I've got a 2.2.7-stable machince acting as a router. > > > > I'm using ipfw to count traffic + do antispoofing on each interface. > > > > it seems that ipfw count seems confused, ie ipfw -a l shows > > > 02000 0 0 count ip from any to any via de2 > > did it work before the dummynet integration ? do you have other rules yes > before which could match ? not in this case .... I'll email you the ruleset directly and you can decide if I'm smoking drugs > > luigi -- Email: skafte@worldgate.com Voice: +403 413 1910 Fax: +403 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 14:00:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18965 for freebsd-stable-outgoing; Fri, 9 Oct 1998 14:00:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA18918; Fri, 9 Oct 1998 14:00:32 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id UAA14187; Fri, 9 Oct 1998 20:00:21 +0100 From: Luigi Rizzo Message-Id: <199810091900.UAA14187@labinfo.iet.unipi.it> Subject: Re: ipfw broken? ... To: skafte@worldgate.com (Greg Skafte) Date: Fri, 9 Oct 1998 20:00:20 +0100 (MET) Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <19981009145317.B22107@worldgate.com> from "Greg Skafte" at Oct 9, 98 02:52:58 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > it seems that ipfw count seems confused, ie ipfw -a l shows > > > > > 02000 0 0 count ip from any to any via de2 > > > > did it work before the dummynet integration ? do you have other rules > > yes > > > before which could match ? > > not in this case .... I'll email you the ruleset directly > and you can decide if I'm smoking drugs you cannot reasonably expect me to look at 400 lines ruleset! When i integrated dummynet i made a mistake and changed slightly the semantics of skipto rules -- if the jump target did not exist, the rule would not match. I fixed this 2-3 days ago. so if you have skipto rules this might be the problem, you just have to update ip_fw.c (one-character change) and see how it works. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 16:30:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19138 for freebsd-stable-outgoing; Fri, 9 Oct 1998 16:30:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19025 for ; Fri, 9 Oct 1998 16:30:06 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id QAA28466 for stable@freebsd.org; Fri, 9 Oct 1998 16:29:55 -0700 (MST) From: "Chad R. Larson" Message-Id: <199810092329.QAA28466@freebie.dcfinc.com> Subject: firewalling To: stable@FreeBSD.ORG Date: Fri, 9 Oct 1998 16:29:55 -0700 (MST) Reply-to: chad@dcfinc.com X-unexpected: The Spanish Inquisition 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-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone have an opinion (now there's a stupid question) about IP firewalling vs TCP wrappers to protect a server exposed to the great unwashed Internet? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 16:33:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19673 for freebsd-stable-outgoing; Fri, 9 Oct 1998 16:33:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19668 for ; Fri, 9 Oct 1998 16:33:13 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id QAA28511; Fri, 9 Oct 1998 16:32:36 -0700 (MST) From: "Chad R. Larson" Message-Id: <199810092332.QAA28511@freebie.dcfinc.com> Subject: Re: Is 'xntpd' broken in -stable? To: n@nectar.com (Jacques Vidrine) Date: Fri, 9 Oct 1998 16:32:36 -0700 (MST) Cc: randy@psg.com, Studded@gorean.org, Marc.Gutschner@triplan.com, freebsd-stable@FreeBSD.ORG In-Reply-To: from Jacques Vidrine at "Oct 9, 98 02:52:10 pm" Reply-to: chad@dcfinc.com X-unexpected: The Spanish Inquisition 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-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks wanting their messages read and considered by the largest possible group probably shouldn't sign them with PGP... > -- Start of PGP signed section. > -- End of PGP signed section, PGP failed! -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 18:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06602 for freebsd-stable-outgoing; Fri, 9 Oct 1998 18:01:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gras-varg.worldgate.com (gras-varg.worldgate.com [198.161.84.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06577; Fri, 9 Oct 1998 18:01:26 -0700 (PDT) (envelope-from skafte@gras-varg.worldgate.com) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.9.1a/8.9.1) id TAA23547; Fri, 9 Oct 1998 19:01:13 -0600 (MDT) Message-ID: <19981009190112.K22107@worldgate.com> Date: Fri, 9 Oct 1998 19:01:12 -0600 From: Greg Skafte To: Luigi Rizzo Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: ipfw broken? ... References: <19981009145317.B22107@worldgate.com> <199810091900.UAA14187@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810091900.UAA14187@labinfo.iet.unipi.it>; from Luigi Rizzo on Fri, Oct 09, 1998 at 08:00:20PM +0100 Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Luigi Rizzo (luigi@labinfo.iet.unipi.it) On Subject: Re: ipfw broken? ... Date: Fri, Oct 09, 1998 at 08:00:20PM +0100 > > > > it seems that ipfw count seems confused, ie ipfw -a l shows > > > > > > > 02000 0 0 count ip from any to any via de2 > > > > > > did it work before the dummynet integration ? do you have other rules > > > > yes > > > > > before which could match ? > > > > not in this case .... I'll email you the ruleset directly > > and you can decide if I'm smoking drugs > > you cannot reasonably expect me to look at 400 lines ruleset! > When i integrated dummynet i made a mistake and changed slightly the > semantics of skipto rules -- if the jump target did not exist, the rule > would not match. I fixed this 2-3 days ago. so if you have skipto rules > this might be the problem, you just have to update ip_fw.c > (one-character change) and see how it works. > > cheers > luigi > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message going to the ip_fw.c,v 1.51.2.20 fixed it sorry for the nasty ruleset file -- Email: skafte@worldgate.com Voice: +403 413 1910 Fax: +403 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 20:28:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26337 for freebsd-stable-outgoing; Fri, 9 Oct 1998 20:28:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bentley.queens.unimelb.edu.au (bentley.queens.unimelb.edu.au [203.28.244.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26309 for ; Fri, 9 Oct 1998 20:28:31 -0700 (PDT) (envelope-from bromage@bentley.queens.unimelb.edu.au) Received: (from bromage@localhost) by bentley.queens.unimelb.edu.au (8.8.8/8.8.8) id NAA17110; Sat, 10 Oct 1998 13:28:09 +1000 (EST) (envelope-from bromage) Message-ID: <19981010132808.64298@queens.unimelb.edu.au> Date: Sat, 10 Oct 1998 13:28:08 +1000 From: Andrew Bromage To: marko@cs.uni-frankfurt.de, freebsd-stable@FreeBSD.ORG Subject: Re: Global register variables in gcc and stdio.h?!? References: <199810071330.PAA22126@king.ki.informatik.uni-frankfurt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199810071330.PAA22126@king.ki.informatik.uni-frankfurt.de>; from Marko Schuetz on Wed, Oct 07, 1998 at 03:30:38PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG G'day all. On Wed, Oct 07, 1998 at 03:30:38PM +0200, Marko Schuetz wrote: > An application I want to compile runs much faster if it can use global > register variables. This was a bug in Mercury-0.7.3, and has since been fixed. You can get the latest "release of the day" from http://www.cs.mu.oz.au/mercury/, or you can wait for 0.8, which is due for release in a couple of weeks' time. If you have any other problems with compiling Mercury under FreeBSD, do let me know, since I'm the only member of the Mercury team who has any sympathy for the cause. :-) Everyone else is thoroughly penguinised. (This is despite Robert Elz working one floor below us.) Cheers, Andrew Bromage To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 20:43:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29436 for freebsd-stable-outgoing; Fri, 9 Oct 1998 20:43:21 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bentley.queens.unimelb.edu.au (bentley.queens.unimelb.edu.au [203.28.244.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29387 for ; Fri, 9 Oct 1998 20:43:05 -0700 (PDT) (envelope-from bromage@bentley.queens.unimelb.edu.au) Received: (from bromage@localhost) by bentley.queens.unimelb.edu.au (8.8.8/8.8.8) id NAA17187; Sat, 10 Oct 1998 13:42:19 +1000 (EST) (envelope-from bromage) Message-ID: <19981010134218.20700@queens.unimelb.edu.au> Date: Sat, 10 Oct 1998 13:42:19 +1000 From: Andrew Bromage To: Mike Smith , marko@cs.uni-frankfurt.de Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Global register variables in gcc and stdio.h?!? References: <199810071330.PAA22126@king.ki.informatik.uni-frankfurt.de> <199810071531.IAA00355@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199810071531.IAA00355@dingo.cdrom.com>; from Mike Smith on Wed, Oct 07, 1998 at 08:31:57AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG G'day all. On Wed, Oct 07, 1998 at 08:31:57AM -0700, Mike Smith wrote: > 1) Any application which depends on global register variables for > performance needs to be fixed. At the risk of getting off-topic, there is at least one exception, and that's compiler-generated code. Many languages use C as a target language because it neatly fills the niche of "platform-independent assembly language". Compiler-generated C is usually the sort of C which had a programmer hand-written it, there would be good cause to sack said programmer. Generated C doesn't need to be maintained, so it can use as many weird features like global register variables or non-local gotos as it likes. In the case of Mercury, the application in question, the global register variables are for parameter passing. There's good reason to do this: C only allows one parameter to be returned from a function, whereas Mercury allows multiple return parameters, so to avoid the performance hit of either passing pointers or packing the return arguments up in a struct (GCC doesn't do a very good job at optimising the latter case), we use global register variables. This causes a significant speedup compared with C on simple benchmarks which are craftily designed to use lots of multiple return parameters, so we feel justified in this design choice. > The concept of a "global register > variable" on the x86 is a bit of a joke anyway. Very true. We have to generate separate object files for position- independent code for the x86 because PIC grabs one more register than we're willing to pay for in position-dependent code. > 2) Declare your global register variables before including header > files. This was the fix to the bug. :-) If anyone else wants to discuss this further, I invite you to do so off-list. Cheers, Andrew Bromage To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 9 21:55:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12754 for freebsd-stable-outgoing; Fri, 9 Oct 1998 21:55:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bentley.queens.unimelb.edu.au (bentley.queens.unimelb.edu.au [203.28.244.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12739 for ; Fri, 9 Oct 1998 21:55:02 -0700 (PDT) (envelope-from bromage@bentley.queens.unimelb.edu.au) Received: (from bromage@localhost) by bentley.queens.unimelb.edu.au (8.8.8/8.8.8) id OAA17932; Sat, 10 Oct 1998 14:54:51 +1000 (EST) (envelope-from bromage) Message-ID: <19981010145451.34491@queens.unimelb.edu.au> Date: Sat, 10 Oct 1998 14:54:51 +1000 From: Andrew Bromage To: chad@dcfinc.com, stable@FreeBSD.ORG Subject: Re: firewalling References: <199810092329.QAA28466@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199810092329.QAA28466@freebie.dcfinc.com>; from Chad R. Larson on Fri, Oct 09, 1998 at 04:29:55PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG G'day all. On Fri, Oct 09, 1998 at 04:29:55PM -0700, Chad R. Larson wrote: > Does anyone have an opinion (now there's a stupid question) about IP > firewalling vs TCP wrappers to protect a server exposed to the great > unwashed Internet? Just as a matter of interest, is there a reason why you don't want to use both? Cheers, Andrew Bromage To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 10 05:14:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00598 for freebsd-stable-outgoing; Sat, 10 Oct 1998 05:14:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA00593; Sat, 10 Oct 1998 05:14:54 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id LAA16193; Sat, 10 Oct 1998 11:14:50 +0100 From: Luigi Rizzo Message-Id: <199810101014.LAA16193@labinfo.iet.unipi.it> Subject: Re: ipfw broken? ... To: skafte@worldgate.com (Greg Skafte) Date: Sat, 10 Oct 1998 11:14:50 +0100 (MET) Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <19981009190112.K22107@worldgate.com> from "Greg Skafte" at Oct 9, 98 07:00:53 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > you cannot reasonably expect me to look at 400 lines ruleset! ... > going to the ip_fw.c,v 1.51.2.20 fixed it sorry for the nasty ruleset file no problem, it was just a comment. in any case this is interesting because it seems that "count" commands are somehow treated as "skipto" commands... cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 10 09:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24398 for freebsd-stable-outgoing; Sat, 10 Oct 1998 09:28:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24387 for ; Sat, 10 Oct 1998 09:28:06 -0700 (PDT) (envelope-from rkw@Dataplex.NET) Received: from [208.2.87.5] (user5.dataplex.net [208.2.87.5]) by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id LAA03821; Sat, 10 Oct 1998 11:46:50 -0500 (CDT) (envelope-from rkw@dataplex.net) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199810091845.UAA12915@gratis.grondar.za> References: Your message of " Fri, 09 Oct 1998 06:52:28 EST." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 10 Oct 1998 11:23:26 -0500 To: Mark Murray From: Richard Wackerbarth Subject: Re: Future of -stable? Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:45 PM -0500 10/9/98, Mark Murray wrote: >Richard Wackerbarth wrote: >> I will again renew my recommendation that we drop "-Stable" as a "real" name >> and instead make it simply an alias to the most recent branch that has been >> so Christened. The "real" names would be 2.2, 3.0, etc. > >Huh? How will that change reality? The last "STABLE" was on the 2.1.N >branch, and it has already been clearly stated that when 2.2.M is >no longer supported 3.0.J will be "STABLE". I'm not concerned about the CVS tag, but the other things that relate to those tags. We still use "-stable" for mailing lists, cvsup, etc. and, at the moment, the supposedly "beta 3.0" doesn't even have its own RELENG_3_0 tag. My concern is that there are going be transitions when 3.0 is neither "stable" nor "current", but somewhere in between. The poor end-user should not be required to jump through hoops to track the transitions. If you are presently tracking the "HEAD" branch, you should be able to switch, at your leisure, to an alternate "3.0" designation which, presently, delivers exactly the same information. At some point in the future, the paths will diverge. Those who choose to remain with the bleeding edge development will go their merry way and the more conservative users will follow the 3.0 branch as it matures. Think of "tracking" as a train. With the current scheme, a user will either be dumped at the end of the line or find himself heading toward the wrong destination simply because he didn't change trains at the proper point. However, if we administer it appropriately, when a the new user gets on board, he can grab any available seat. Then, while the train is moving, he can move to the car which is going to his desired destination. He doesn't have to wake up in the middle of the night to change trains. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 10 10:00:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29188 for freebsd-stable-outgoing; Sat, 10 Oct 1998 10:00:02 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29134 for ; Sat, 10 Oct 1998 09:59:56 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from bergelmir.ifi.uio.no (2602@bergelmir.ifi.uio.no [129.240.65.172]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id SAA10063; Sat, 10 Oct 1998 18:59:42 +0200 (MET DST) Received: (from dag-erli@localhost) by bergelmir.ifi.uio.no ; Sat, 10 Oct 1998 18:59:40 +0200 (MET DST) Mime-Version: 1.0 To: Richard Wackerbarth Cc: Studded , freebsd-stable@FreeBSD.ORG Subject: Re: Future of -stable? References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 10 Oct 1998 18:59:39 +0200 In-Reply-To: Richard Wackerbarth's message of "Fri, 9 Oct 1998 06:52:28 -0500" Message-ID: Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 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 JAA29140 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Wackerbarth writes: > Right now, "3.0", "AVANTEGUARD", and "PRERELEASE" are the same. ITYM "Avant-garde". HTH, HAND! DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 10 19:54:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02622 for freebsd-stable-outgoing; Sat, 10 Oct 1998 19:54:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from laputa.wt.net (laputa.wt.net [205.230.159.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02591 for ; Sat, 10 Oct 1998 19:54:20 -0700 (PDT) (envelope-from kylec@wt.net) Received: from wt.net (wt-d6-44.wt.net [208.211.141.44]) by laputa.wt.net (8.9.1/8.9.1) with ESMTP id VAA20732 for ; Sat, 10 Oct 1998 21:57:13 -0500 (CDT) Message-ID: <36201E20.3208AE1D@wt.net> Date: Sat, 10 Oct 1998 21:55:28 -0500 From: KC Reply-To: kylec@wt.net Organization: Here X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Subscribe! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message