From owner-freebsd-current Sun Mar 23 01:04:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA00235 for current-outgoing; Sun, 23 Mar 1997 01:04:38 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA00226 for ; Sun, 23 Mar 1997 01:04:26 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA06288; Sun, 23 Mar 1997 10:02:04 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA06468; Sun, 23 Mar 1997 09:50:38 +0100 (MET) Message-ID: <19970323095038.PT14623@uriah.heep.sax.de> Date: Sun, 23 Mar 1997 09:50:38 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: mark@seeware.DIALix.oz.au (Mark Hannon) Cc: freebsd-current@freebsd.org Subject: Re: 2.2-RELEASE, dtmail stopped working References: <199703230114.MAA00606@putte.seeware.DIALix.oz.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703230114.MAA00606@putte.seeware.DIALix.oz.au>; from Mark Hannon on Mar 23, 1997 12:14:35 +1100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Mark Hannon wrote: > I can't however seem to get a trace going now. Executing > ktrace -i -p 264 > From an su'd shell (where 264 is the pid of my normal tcsh) doesn't > seem to give much joy. You probably need to disable this code in sys/kern/kern_exec.c temporarily: /* * Turn off syscall tracing for set-id programs, except for * root. */ if (p->p_tracep && suser(p->p_ucred, &p->p_acflag)) { p->p_traceflag = 0; vrele(p->p_tracep); p->p_tracep = NULL; } -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Mar 23 01:39:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA01357 for current-outgoing; Sun, 23 Mar 1997 01:39:49 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA01352 for ; Sun, 23 Mar 1997 01:39:29 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id LAA07062; Sun, 23 Mar 1997 11:37:09 +0200 (EET) From: mika ruohotie Message-Id: <199703230937.LAA07062@shadows.aeon.net> Subject: Re: ahc crashes In-Reply-To: <199703211909.JAA03106@caliban.dihelix.com> from David Langford at "Mar 21, 97 09:09:54 am" To: langfod@dihelix.com (David Langford) Date: Sun, 23 Mar 1997 11:37:09 +0200 (EET) Cc: mpp@freefall.freebsd.org, langfod@dihelix.com, tom@uniserve.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > and widely variing of the OS. I have noticed in the past that LINT > seemed to about the only place that "undocumented" options were documented. > It is unclear when "undocumented" options become more than just testbed stuff. > I certainly dont expect current's LINT to be up-to-date but > perhaps in the RELEASES or such. to clarify my comments on this subject, that was what i meant too, i know it's not "fair" to expect LINT on current being anywhere near up to date, but i think releases are slightly different case... random user who picks up the cdrom (ok, so i'm not one :p) has no idea where to even look for kernel options if they are not quite familiar with the system itself... or if they're not reading mailinglists... even i was under impression 2.1.x didnt carry those AHC options, and my mistake was not to make full search... and reason why i'm not contributing myself is that i lack the skills... =( mickey From owner-freebsd-current Sun Mar 23 01:51:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA01599 for current-outgoing; Sun, 23 Mar 1997 01:51:48 -0800 (PST) Received: from melbourne.dialix.com.au (seeuucp@melbourne.dialix.com.au [203.12.2.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA01594 for ; Sun, 23 Mar 1997 01:51:44 -0800 (PST) Received: (from seeuucp@localhost) by melbourne.dialix.com.au with UUCP id UAA26822; Sun, 23 Mar 1997 20:51:14 +1100 (EST) X-Authentication-Warning: melbourne.dialix.com.au: seeuucp set sender to mark@seeware.DIALix.oz.au using -f Received: from putte.seeware.DIALix.oz.au (putte.seeware.DIALix.oz.au [10.0.0.1]) by doorway.seeware.DIALix.oz.au (8.8.5/8.7.3) with ESMTP id UAA00406; Sun, 23 Mar 1997 20:33:38 +1100 (EST) From: Mark Hannon Received: (from mark@localhost) by putte.seeware.DIALix.oz.au (8.8.5/8.7.3) id UAA00798; Sun, 23 Mar 1997 20:33:38 +1100 (EST) Date: Sun, 23 Mar 1997 20:33:38 +1100 (EST) Message-Id: <199703230933.UAA00798@putte.seeware.DIALix.oz.au> To: joerg_wunsch@uriah.heep.sax.de Subject: Re: 2.2-RELEASE, dtmail stopped working Cc: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=C.us-ascii Content-MD5: bA6UMJqExEe7WH+5Vr50mw== Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id BAA01595 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > > > > When I try and start dtmail I get a dialog box saying: > > > > "Mailer has not been properly installed and cannot be run because > > > > the execution group is incorrectly set" > > > > > > > > Things worked correctly when the machine had 2.1.7 installed. > > > > If I su to root and run dtmail it starts OK. > > > > > > > > Any ideas? > > > > > > ktrace it, and see what it stumples across. > > > > > > > I'm working on it. As dtmail is sgid bin I can't ktrace it from my > > normal user & if I run dtmail as root it works fine :-( > > I finally got the trace working. Made a little hack in the kernel to do so (modified kern/kern_exec.c to not stop tracing on suid processes). The traces are quite long, I have looked through them and included the parts where they start deviating. On the 2.1.7 kernel: 283 dtmail RET stat -1 errno 2 No such file or directory 283 dtmail CALL stat(0xfa7e8,0xefbeb438) 283 dtmail NAMI "/usr/include/X11/bitmaps" 283 dtmail RET stat -1 errno 2 No such file or directory 283 dtmail CALL break(0x109fb0) 283 dtmail RET break 0 283 dtmail CALL break(0x109fb0) 283 dtmail RET break 0 283 dtmail CALL gettimeofday(0xefbfd080,0) 283 dtmail RET gettimeofday 0 283 dtmail CALL access(0x859451b,0x4) 283 dtmail NAMI "/etc/localtime" 283 dtmail RET access 0 283 dtmail CALL open(0x859451b,0,0x85bb060) 283 dtmail NAMI "/etc/localtime" 283 dtmail RET open 12/0xc 283 dtmail CALL read(0xc,0xefbfad38,0x1f08) 283 dtmail GIO fd 12 read 785 bytes : Continues.... With 2.2: 319 dtmail RET stat -1 errno 2 No such file or directory 319 dtmail CALL stat(0xfdf40,0xefbeb114) 319 dtmail NAMI "/usr/include/X11/bitmaps" 319 dtmail RET stat -1 errno 2 No such file or directory 319 dtmail CALL write(0x3,0xb76e0,0x47c) 319 dtmail GIO fd 3 wrote 1148 bytes "7\^P\^F\0\v\0À\^B#\0\0\0\f\0\0\0\^VÞ\0\0\0\0\0\0007\0\^F\0\f\0À\^B#\0\ \0\0\f\0\0\0;ï\0\0\0\0\0\0007\0\^F\0\r\0À\^B#\0\0\0\f\0\0\0Ls\0\0\0\0\ \0\0007t\^F\0\^N\0À\^B#\0\0\0\f\0\0\0ì²\0\0\^VÞ\0\0\^A\^P\r\0\^O\0À\^B\ #\0\0\0\0\0\0\0\^E\0\^E\0\0\0\^A\0\0\0\0\0 ,\0\0\^VÞ\0\0\0\0\0\0\^A\0\0\0000\M^@"\0!\0\0\0\^R\0 \0\^O\0À\^B'\0\ \0\0\^_\0\0\0\b\0\0\0\f\0\0\0Dialog_popup\^R\0\r\0\^O\0À\^B$\0\0\0\^_\ \0\0\0\b\0À\^B\^Z\0\0\0putte.seeware.DIALix.oz.au\0\0\^R\0\^X\0\^O\0À\ \^B(\0\0\0)\0\0\0 \0\0\0\^R\0\0\0\f\^B\0\0\0\0\0\0\0\0\0\0\^E\0\0\0\^E\ \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\ : Pops up dialog box with error message. I can't see from the trace why the 2.1.7 calls the break routine, what is it anyway? I can't find it in my manpages. What sort of trace should I do to help localise this problem further? Regards/Mark From owner-freebsd-current Sun Mar 23 02:21:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA02299 for current-outgoing; Sun, 23 Mar 1997 02:21:52 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA02294 for ; Sun, 23 Mar 1997 02:21:46 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA06988 for freebsd-current@FreeBSD.ORG; Sun, 23 Mar 1997 11:21:40 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id KAA10397; Sun, 23 Mar 1997 10:56:14 +0100 (MET) Message-ID: <19970323105614.ZN28732@uriah.heep.sax.de> Date: Sun, 23 Mar 1997 10:56:14 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Subject: Re: ahc crashes References: <199703211909.JAA03106@caliban.dihelix.com> <199703230937.LAA07062@shadows.aeon.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703230937.LAA07062@shadows.aeon.net>; from mika ruohotie on Mar 23, 1997 11:37:09 +0200 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As mika ruohotie wrote: > random user who picks up the cdrom (ok, so i'm not one :p) has no idea > where to even look for kernel options if they are not quite familiar with > the system itself... or if they're not reading mailinglists... Random users are expected to read handbooks. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Mar 23 03:03:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA03167 for current-outgoing; Sun, 23 Mar 1997 03:03:37 -0800 (PST) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA03159 for ; Sun, 23 Mar 1997 03:03:33 -0800 (PST) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id LAA02033; Sun, 23 Mar 1997 11:01:34 GMT Date: Sun, 23 Mar 1997 10:59:25 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 23 Mar 1997 10:59:25 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199703230026.RAA19751@phaeton.artisoft.com> References: from "Bob Bishop" at Mar 22, 97 10:24:07 pm Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Terry Lambert From: Bob Bishop Subject: Re: 2.2R (src 2.2 211): == dialing Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 12:26 am -0000 23/3/97, Terry Lambert wrote: >> >> The SIGHUP was historically intended to 'hang up' sessions on serial >>ports. >> >> Processes not attached to a terminal shouldn't be sent the signal. >> > >> >That was my impression reading this exchange as well. >> > >> >I think we still have issues with propagation of signals to the >> >other processes in a process group when the group leader is signalled, >> >as well. >> >> Quite likely; but I think that's a separate issue. > >That depends on how the shutdown is sending it's SIGHUP to everybody. Yeah, but being attached to a terminal is a session thang not a process group thang. Opening this particular can of worms is probably a Bad Idea, but at the very least the relevant man pages appear to be missing some detail. I for one would be very grateful for a _concise_ description of how the whole signals/exit/pg's/sessions thing is supposed to work as it stands. If anyone is prepared to take the position that it ain't broke, I would value a _concise_ justification of that position. If anyone mentions POSIX, I'm likely to go into a sulk :-| -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Sun Mar 23 09:43:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA15777 for current-outgoing; Sun, 23 Mar 1997 09:43:42 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA15772 for ; Sun, 23 Mar 1997 09:43:38 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0w8rHD-0002EM-00; Sun, 23 Mar 1997 10:41:51 -0700 To: Gary Roberts Subject: Re: -Current Cc: freebsd-current@freebsd.org In-reply-to: Your message of "Fri, 21 Mar 1997 23:34:10 EST." References: Date: Sun, 23 Mar 1997 10:41:51 -0700 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Gary Roberts writes: : Is it safe to cvsup my src and do a make world ??? I've successfully built up to CTM 3151. I'd say the chances are very good. Make sure you do a make world, and not just a make all because the include files have change a bunch. Warner From owner-freebsd-current Sun Mar 23 09:44:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA15836 for current-outgoing; Sun, 23 Mar 1997 09:44:25 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA15829 for ; Sun, 23 Mar 1997 09:44:22 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0w8rJZ-0002EV-00; Sun, 23 Mar 1997 10:44:17 -0700 To: Bill Fenner Subject: Re: Possible routed problem 2.2 Cc: freebsd-current@freebsd.org, neil.long@materials.oxford.ac.uk In-reply-to: Your message of "Sat, 22 Mar 1997 10:00:30 PST." <97Mar22.100042pst.177486@crevenia.parc.xerox.com> References: <97Mar22.100042pst.177486@crevenia.parc.xerox.com> Date: Sun, 23 Mar 1997 10:44:16 -0700 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <97Mar22.100042pst.177486@crevenia.parc.xerox.com> Bill Fenner writes: : >ping: sendto: No buffer space available : : Looks like your machine ran out of mbuf's. If you can recreate this, try : "netstat -m" and see if any category has a much higher number than the others. I get these a lot when I had my gateway machine down or in some state of bringing up the ppp link too. Once the ppp link comes back, it usually stops doing this. Warner From owner-freebsd-current Sun Mar 23 09:49:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA15981 for current-outgoing; Sun, 23 Mar 1997 09:49:02 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA15976 for ; Sun, 23 Mar 1997 09:48:59 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0w8rO5-0002Ey-00; Sun, 23 Mar 1997 10:48:57 -0700 To: current@freebsd.org Subject: CTM? Date: Sun, 23 Mar 1997 10:48:57 -0700 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hmmmm, is CTM being a little slow, or do I have problems on my end with disk space? I've not seen a CTM for a whole day, and now I get 3154 which is 3 later (rather than 1 later) than my last CTM delta. Also, now that spatter is dead, where do I get CTM updates from? Can we update the README.1ST on Freefall to direct people to the new spatter, or maybe setup a ctm.freebsd.org CNAME? I know this came across in email, but I can't seem to find it in my searches. Thanks for your time and attention in this matter. Warner From owner-freebsd-current Sun Mar 23 10:12:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA16937 for current-outgoing; Sun, 23 Mar 1997 10:12:38 -0800 (PST) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA16928 for ; Sun, 23 Mar 1997 10:12:33 -0800 (PST) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id TAA00196; Sun, 23 Mar 1997 19:12:15 +0100 (MET) From: Wolfgang Helbig Message-Id: <199703231812.TAA00196@helbig.informatik.ba-stuttgart.de> Subject: Re: -Current In-Reply-To: from Gary Roberts at "Mar 21, 97 11:34:10 pm" To: wangel@wangel.dyndns.com (Gary Roberts) Date: Sun, 23 Mar 1997 19:12:15 +0100 (MET) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > Is it safe to cvsup my src and do a make world ??? Yes. But watch out -- some important userland commands like mount(8) won't work with a pre Lite/2 kernel. So don't forget to rebuild the kernel. Wolfgang From owner-freebsd-current Sun Mar 23 10:43:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA18072 for current-outgoing; Sun, 23 Mar 1997 10:43:39 -0800 (PST) Received: from pent.ibm.net (slip129-37-195-230.nc.us.ibm.net [129.37.195.230]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA18066 for ; Sun, 23 Mar 1997 10:43:33 -0800 (PST) Received: (from root@localhost) by pent.ibm.net (8.8.5/8.8.5) id NAA10117 for freebsd-current@freebsd.org; Sun, 23 Mar 1997 13:43:18 -0500 (EST) Message-ID: X-Mailer: XFMail 1.0 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 23 Mar 1997 13:37:36 -0500 (EST) From: Adam Hawks To: freebsd-current@freebsd.org Subject: Is 802.3 Supported? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a 3.0-current box as of 02/09/97 with a NE2000 ethernet card attached to an IBM 8229 Token-ring to Ethernet bridge. My problem is that the bridge and all the other machines are working fine but when I put my 3.0-current box in it doesn't see anything but itself. I think I've traced it down to the brige is only passing 802.3 frames and my 3.0 seems to be something else. How do I set the NE2000 into 802.3 mode? Thanks in advance Adam W. Hawks -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzL2rXEAAAEEALYm0mNh/V3WOPblF5f9/YpBQZWrpM7ivUqJFeKVKCMDZ6cW xhznY3jzBMkrDASlIE21WHVi6y896P7dTlLQxm4YbGNQIdMAOG3LLUjJ9NdCEmvh yqeExpvzHTciDyeetCXOWGgDaYs+1F9cZCct/90hoAv0WNFPRb+szFTuumaxAAUR tB9BZGFtIFcuIEhhd2tzIDxhd2hhd2tzQGlibS5uZXQ+ =5jZB -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-current Sun Mar 23 10:53:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA18773 for current-outgoing; Sun, 23 Mar 1997 10:53:38 -0800 (PST) Received: from pent.ibm.net (slip129-37-195-230.nc.us.ibm.net [129.37.195.230]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA18750 for ; Sun, 23 Mar 1997 10:53:27 -0800 (PST) Received: (from root@localhost) by pent.ibm.net (8.8.5/8.8.5) id NAA11040 for freebsd-current@FreeBSD.ORG; Sun, 23 Mar 1997 13:53:18 -0500 (EST) Message-ID: X-Mailer: XFMail 1.0 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 23 Mar 1997 13:46:49 -0500 (EST) From: Adam Hawks To: freebsd-current@FreeBSD.ORG Subject: Is 802.3 Suppported Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- I have a 3.0-current as of 02/09/97 connected to a token ring segment thru a IBM 8229 bridge. All my other devices work but the BSD box won't cross the bridge. The bridge is setup with 802.3 Ethernet frames. Can freebsd be set to send 802.3 Ethernet frames with a NE2000 (ed0) ethernet card. Thanks in Advance Adam W. Hawks awhawks@ibm.net - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzL2rXEAAAEEALYm0mNh/V3WOPblF5f9/YpBQZWrpM7ivUqJFeKVKCMDZ6cW xhznY3jzBMkrDASlIE21WHVi6y896P7dTlLQxm4YbGNQIdMAOG3LLUjJ9NdCEmvh yqeExpvzHTciDyeetCXOWGgDaYs+1F9cZCct/90hoAv0WNFPRb+szFTuumaxAAUR tB9BZGFtIFcuIEhhd2tzIDxhd2hhd2tzQGlibS5uZXQ+ =5jZB - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMzV8G7+szFTuumaxAQGfaQP/SBKV9wU2SheoQwUQTbHlxJq9dEIHJ7HE rtX+W4OErHXqp8eMnV+8YRoallJOZTH//IGpkNSIz+34K0XH+Tb6wuL2d7TxuAAC mHoZ70kIZfvHtzgVQSmcEfeb2HsOVUk9fAvFFmerVBmfHWchK/Xql5LuPn3XbzZE LdtJWeaSF4E= =lNKC -----END PGP SIGNATURE----- From owner-freebsd-current Sun Mar 23 11:01:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA19561 for current-outgoing; Sun, 23 Mar 1997 11:01:25 -0800 (PST) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA19555 for ; Sun, 23 Mar 1997 11:01:18 -0800 (PST) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id UAA00327; Sun, 23 Mar 1997 20:00:57 +0100 (MET) From: Wolfgang Helbig Message-Id: <199703231900.UAA00327@helbig.informatik.ba-stuttgart.de> Subject: Re: CTM? In-Reply-To: from Warner Losh at "Mar 23, 97 10:48:57 am" To: imp@village.org (Warner Losh) Date: Sun, 23 Mar 1997 20:00:57 +0100 (MET) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > Hmmmm, is CTM being a little slow, or do I have problems on my end > with disk space? I've not seen a CTM for a whole day, and now I get > 3154 which is 3 later (rather than 1 later) than my last CTM delta. CTM #3153 arrived at 22 Mar 15:00 GMT. And then CTM #3154 1/13 today at 17:00 GMT. So there was a short dry period but no delta is missing. In fact, Rich's ctm-service proved to work as flawless as smatter's. Wolfgang From owner-freebsd-current Sun Mar 23 11:27:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA22318 for current-outgoing; Sun, 23 Mar 1997 11:27:07 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA22305 for ; Sun, 23 Mar 1997 11:27:04 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA20768; Sun, 23 Mar 1997 12:14:00 -0700 From: Terry Lambert Message-Id: <199703231914.MAA20768@phaeton.artisoft.com> Subject: Re: 2.2R (src 2.2 211): == dialing To: rb@gid.co.uk (Bob Bishop) Date: Sun, 23 Mar 1997 12:14:00 -0700 (MST) Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org In-Reply-To: from "Bob Bishop" at Mar 23, 97 10:59:25 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > If anyone is prepared to take the position that it ain't broke, I would > value a _concise_ justification of that position. > > If anyone mentions POSIX, I'm likely to go into a sulk :-| I happen to disagree with the BSD interpretation of POSIX in this regard. SVR4 is certified POSIX compliant, and they don't do what we do: they propagate group SIGHUP to all process group members. You can argue until you are blue in the face that SVR4 is "wrong", but to prove it to me you will have to get an SVR4 box to fail POSIX compliance testing. You can't argue with success. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Mar 23 11:52:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA24136 for current-outgoing; Sun, 23 Mar 1997 11:52:39 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA24118 for ; Sun, 23 Mar 1997 11:52:31 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA08007 for current@freebsd.org; Sun, 23 Mar 1997 20:52:23 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id UAA19008; Sun, 23 Mar 1997 20:30:44 +0100 (MET) Message-ID: <19970323203044.VD44159@uriah.heep.sax.de> Date: Sun, 23 Mar 1997 20:30:44 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: current@freebsd.org Subject: Re: CTM? References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Warner Losh on Mar 23, 1997 10:48:57 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Warner Losh wrote: > Hmmmm, is CTM being a little slow, or do I have problems on my end > with disk space? I've not seen a CTM for a whole day, and now I get > 3154 which is 3 later (rather than 1 later) than my last CTM delta. I've just got a bunch of deltas by mail. Still, they look like lagging behind by a day or two. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Mar 23 12:07:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA25067 for current-outgoing; Sun, 23 Mar 1997 12:07:11 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA25053 for ; Sun, 23 Mar 1997 12:07:02 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA08290 for freebsd-current@freebsd.org; Sun, 23 Mar 1997 21:06:51 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA19169; Sun, 23 Mar 1997 21:01:36 +0100 (MET) Message-ID: <19970323210136.BJ32077@uriah.heep.sax.de> Date: Sun, 23 Mar 1997 21:01:36 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org Subject: Re: 2.2R (src 2.2 211): == dialing References: <199703231914.MAA20768@phaeton.artisoft.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703231914.MAA20768@phaeton.artisoft.com>; from Terry Lambert on Mar 23, 1997 12:14:00 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > I happen to disagree with the BSD interpretation of POSIX in this > regard. SVR4 is certified POSIX compliant, and they don't do what > we do: they propagate group SIGHUP to all process group members. They don't do it in the kernel, their shell does. If you want the same silly behaviour, use the same shell (ksh93e, it's available for free). I don't want it, so i'm using this shell for reference purposes only. Regarding their Posix certification, i always wonder how they get away with a default shell (/bin/sh) that's still far away from being Posix. Many systems of SysV vintage still ship an obsolete awk, since they fear to rename their `nawk' (which is everything else but new these days) as the default one. I bet they won't make the Korn shell the default shell before the year 2050, in the fear that some obsolete script by some obsolete vendor might stumple across it... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Mar 23 12:29:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA26573 for current-outgoing; Sun, 23 Mar 1997 12:29:17 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA26550 for ; Sun, 23 Mar 1997 12:29:01 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id VAA00825 for ; Sun, 23 Mar 1997 21:28:49 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id VAA17339 for current@FreeBSD.ORG; Sun, 23 Mar 1997 21:28:18 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id UAA19928; Sun, 23 Mar 1997 20:32:11 +0100 (CET) Message-ID: <19970323203211.53890@keltia.freenix.fr> Date: Sun, 23 Mar 1997 20:32:11 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: CTM? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.65,1-4,10,14-18 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3142 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Warner Losh: > Hmmmm, is CTM being a little slow, or do I have problems on my end > with disk space? I've not seen a CTM for a whole day, and now I get > 3154 which is 3 later (rather than 1 later) than my last CTM delta. Funny, I haven't got 3154 yet but all others before arrived without problems: -rw-r--r-- 1 roberto staff 939609 Mar 16 23:32 cvs-cur.3135.gz -rw-r--r-- 1 roberto staff 73188 Mar 16 23:32 cvs-cur.3136.gz -rw-r--r-- 1 daemon wheel 69765 Mar 20 18:32 cvs-cur.3137.gz -rw-r--r-- 1 roberto staff 355290 Mar 17 18:34 cvs-cur.3138.gz -rw-r--r-- 1 roberto staff 15081 Mar 17 18:35 cvs-cur.3139.gz -rw-r--r-- 1 daemon wheel 2556 Mar 18 06:32 cvs-cur.3140.gz -rw-r--r-- 1 daemon wheel 5115 Mar 18 18:31 cvs-cur.3141.gz -rw-r--r-- 1 daemon wheel 5713 Mar 18 18:32 cvs-cur.3142.gz -rw-r--r-- 1 daemon wheel 60711 Mar 19 06:33 cvs-cur.3143.gz -rw-r--r-- 1 daemon wheel 18706 Mar 19 18:32 cvs-cur.3144.gz -rw-r--r-- 1 daemon wheel 8057 Mar 19 18:32 cvs-cur.3145.gz -rw-r--r-- 1 daemon wheel 10908 Mar 20 06:32 cvs-cur.3146.gz -rw-r--r-- 1 daemon wheel 5320 Mar 20 18:31 cvs-cur.3147.gz -rw-r--r-- 1 daemon wheel 1235 Mar 20 18:33 cvs-cur.3148.gz -rw-r--r-- 1 daemon wheel 6985 Mar 21 06:32 cvs-cur.3149.gz -rw-r--r-- 1 daemon wheel 4161 Mar 21 18:31 cvs-cur.3150.gz -rw-r--r-- 1 daemon wheel 7862 Mar 21 18:32 cvs-cur.3151.gz -rw-r--r-- 1 daemon wheel 45919 Mar 22 18:32 cvs-cur.3152.gz -rw-r--r-- 1 daemon wheel 16636 Mar 22 18:33 cvs-cur.3153.gz 3137 was the only one out of sync. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #39: Sun Feb 2 22:12:44 CET 1997 From owner-freebsd-current Sun Mar 23 12:31:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA26816 for current-outgoing; Sun, 23 Mar 1997 12:31:16 -0800 (PST) Received: from gaboon.nai.net (gaboon.nai.net [204.71.31.225]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA26811 for ; Sun, 23 Mar 1997 12:31:10 -0800 (PST) Received: (from asv@localhost) by gaboon.nai.net (8.8.5/8.7.3) id PAA24776 for current@FreeBSD.org; Sun, 23 Mar 1997 15:32:49 -0500 (EST) From: Stan Voket Message-Id: <199703232032.PAA24776@gaboon.nai.net> Subject: bootparamd on current To: current@FreeBSD.org Date: Sun, 23 Mar 1997 15:32:48 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Is there a known problem with bootparamd on -current? I can net boot my Sun 3's using bootparamd on 2.1.7R but not from -current. (using same /etc/bootparams file). Initially, booting seems to work and the client gets it's boot path but it never completes booting and complains "bootparamd not responding. Thanks for the help, Stan -- - Stan Voket, asv@gaboon.nai.net - http://gaboon.nai.net - - Voice: 203.746-4489 - FAX 203.746.9761 - TELEX 969.642/CARIN DURY - "If you think you can, or you can't; you are _always_ right!" From owner-freebsd-current Sun Mar 23 13:21:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA29759 for current-outgoing; Sun, 23 Mar 1997 13:21:55 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA29754 for ; Sun, 23 Mar 1997 13:21:51 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA21046; Sun, 23 Mar 1997 14:09:16 -0700 From: Terry Lambert Message-Id: <199703232109.OAA21046@phaeton.artisoft.com> Subject: Re: 2.2R (src 2.2 211): == dialing To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 23 Mar 1997 14:09:16 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: <19970323210136.BJ32077@uriah.heep.sax.de> from "J Wunsch" at Mar 23, 97 09:01:36 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I happen to disagree with the BSD interpretation of POSIX in this > > regard. SVR4 is certified POSIX compliant, and they don't do what > > we do: they propagate group SIGHUP to all process group members. > > They don't do it in the kernel, their shell does. If you want the > same silly behaviour, use the same shell (ksh93e, it's available for > free). I don't want it, so i'm using this shell for reference > purposes only. This isn't true. I've been hacking SysV kernels since *way* back, and they handle it in the kernel. If the shell does this, then the shell is probably wrong. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Mar 23 13:22:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA29794 for current-outgoing; Sun, 23 Mar 1997 13:22:16 -0800 (PST) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA29779 for ; Sun, 23 Mar 1997 13:22:06 -0800 (PST) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id PAA27863; Sun, 23 Mar 1997 15:21:32 -0600 (CST) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <19970323203211.53890@keltia.freenix.fr> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 23 Mar 1997 15:12:54 -0600 To: Ollivier Robert From: Richard Wackerbarth Subject: Re: CTM? Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk At 1:32 PM -0600 3/23/97, Ollivier Robert wrote: >According to Warner Losh: >> Hmmmm, is CTM being a little slow, or do I have problems on my end >> with disk space? I've not seen a CTM for a whole day, and now I get >> 3154 which is 3 later (rather than 1 later) than my last CTM delta. > >Funny, I haven't got 3154 yet but all others before arrived without >problems: Yes, there was an update missed yesterday because of a system reboot that left the lock set. I cleared it and things are back to the normal schedule. >3137 was the only one out of sync. There was a problem at freefall which caused mail some mail to get lost. When someone pointed out that 3137 had been dropped, I caused it to be retransmitted. We need to arrange to have published a list of sites that archive the various ctm distributions. With the generation of all the ctm distributions, I simply do not have the resources to also be a public repository of them. However, I will be happy to assist any public archiver in obtaining any missing pieces. Richard From owner-freebsd-current Sun Mar 23 14:04:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA02008 for current-outgoing; Sun, 23 Mar 1997 14:04:21 -0800 (PST) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA02000 for ; Sun, 23 Mar 1997 14:04:17 -0800 (PST) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id OAA21890 for ; Sun, 23 Mar 1997 14:06:42 -0800 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id RAA15671; Sun, 23 Mar 1997 17:03:39 -0500 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id RAA29952; Sun, 23 Mar 1997 17:03:39 -0500 Received: (from alk@localhost) by compound.east.sun.com (8.8.5/8.7.3) id QAA18336; Sun, 23 Mar 1997 16:03:54 -0600 (CST) Date: Sun, 23 Mar 1997 16:03:54 -0600 (CST) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199703232203.QAA18336@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: current@freebsd.org Subject: Re: 2.2R (src 2.2 211): == dialing X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quoth Bob Bishop on Sat, 22 March: : At 9:18 pm -0000 22/3/97, Terry Lambert wrote: : >I think we still have issues with propagation of signals to the : >other processes in a process group when the group leader is signalled, : >as well. : : Quite likely; but I think that's a separate issue. : Quite definitely: Try debugging code that forks!-) Not fun at all. But perhaps the SIGHUP is arriving by erroneous propagation? From owner-freebsd-current Sun Mar 23 14:21:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA02644 for current-outgoing; Sun, 23 Mar 1997 14:21:46 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA02633 for ; Sun, 23 Mar 1997 14:21:12 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA10225 for current@FreeBSD.org; Sun, 23 Mar 1997 23:21:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA19577; Sun, 23 Mar 1997 22:23:01 +0100 (MET) Message-ID: <19970323222300.LP00686@uriah.heep.sax.de> Date: Sun, 23 Mar 1997 22:23:00 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.org Subject: Re: CTM? References: <19970323203211.53890@keltia.freenix.fr> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970323203211.53890@keltia.freenix.fr>; from Ollivier Robert on Mar 23, 1997 20:32:11 +0100 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > Funny, I haven't got 3154 yet but all others before arrived without > problems: I'm at part 6 out of 13 for delta #3154 right now. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Mar 23 14:26:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA02920 for current-outgoing; Sun, 23 Mar 1997 14:26:48 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA02906 for ; Sun, 23 Mar 1997 14:26:43 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id FAA08659; Mon, 24 Mar 1997 05:27:52 +1100 Date: Mon, 24 Mar 1997 05:27:52 +1100 From: Bruce Evans Message-Id: <199703231827.FAA08659@godzilla.zeta.org.au> To: rb@gid.co.uk, terry@lambert.org Subject: Re: 2.2R (src 2.2 211): == dialing Cc: freebsd-current@freebsd.org, joerg_wunsch@uriah.heep.sax.de Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I for one would be very grateful for a _concise_ description of how the >whole signals/exit/pg's/sessions thing is supposed to work as it stands. > >If anyone is prepared to take the position that it ain't broke, I would >value a _concise_ justification of that position. > >If anyone mentions POSIX, I'm likely to go into a sulk :-| `man 2 _exit' says much the same things as POSIX about SIGHUP on exit. It points to intro(2) for definitions of pg's/sessions. Bruce From owner-freebsd-current Sun Mar 23 14:52:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA04431 for current-outgoing; Sun, 23 Mar 1997 14:52:31 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA04426 for ; Sun, 23 Mar 1997 14:52:28 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA10726 for current@FreeBSD.ORG; Sun, 23 Mar 1997 23:52:26 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA19765; Sun, 23 Mar 1997 23:24:13 +0100 (MET) Message-ID: <19970323232413.DQ50069@uriah.heep.sax.de> Date: Sun, 23 Mar 1997 23:24:13 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: CTM? References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Richard Wackerbarth on Mar 23, 1997 15:12:54 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Richard Wackerbarth wrote: > We need to arrange to have published a list of sites that archive the > various ctm distributions. With the generation of all the ctm > distributions, I simply do not have the resources to also be a public > repository of them. However, I will be happy to assist any public archiver > in obtaining any missing pieces. What's wrong with freefall? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Mar 23 15:12:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA05772 for current-outgoing; Sun, 23 Mar 1997 15:12:31 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA05759 for ; Sun, 23 Mar 1997 15:12:27 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0w8wQn-0004Cs-00; Sun, 23 Mar 1997 16:12:05 -0700 To: Richard Wackerbarth Subject: Re: CTM? Cc: Ollivier Robert , current@freebsd.org In-reply-to: Your message of "Sun, 23 Mar 1997 15:12:54 CST." References: Date: Sun, 23 Mar 1997 16:12:05 -0700 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Richard Wackerbarth writes: : We need to arrange to have published a list of sites that archive the : various ctm distributions. Can we publish this list by the ftp DNS convention? Eg ctm.freebsd.org, ctm1.freebsd.org, ctm.de.freebsd.org, etc? Warner From owner-freebsd-current Sun Mar 23 16:21:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA12288 for current-outgoing; Sun, 23 Mar 1997 16:21:19 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12282 for ; Sun, 23 Mar 1997 16:21:15 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA00911; Mon, 24 Mar 1997 10:51:00 +1030 (CST) From: Michael Smith Message-Id: <199703240021.KAA00911@genesis.atrad.adelaide.edu.au> Subject: Re: bootparamd on current In-Reply-To: <199703232032.PAA24776@gaboon.nai.net> from Stan Voket at "Mar 23, 97 03:32:48 pm" To: asv@gaboon.nai.net (Stan Voket) Date: Mon, 24 Mar 1997 10:51:00 +1030 (CST) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Stan Voket stands accused of saying: > > Is there a known problem with bootparamd on -current? How -current? > I can net boot my Sun 3's using bootparamd on 2.1.7R but not from -current. > (using same /etc/bootparams file). I'm booting two Sun 3/60's and a 4/75, as well as an HP9000/425 and a Mips M/2000 off a roughly-2.2 system with no trouble at all. > Initially, booting seems to work and the client gets it's boot path but it > never completes booting and complains "bootparamd not responding. Perhaps the output of 'tcpdump -vvNt' (with perhaps some more qualifiers if you're on a busy network) would be of help here. > Stan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sun Mar 23 16:23:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA12369 for current-outgoing; Sun, 23 Mar 1997 16:23:01 -0800 (PST) Received: from cyberwind.com (cyberwind.com [199.4.109.220]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12362 for ; Sun, 23 Mar 1997 16:22:55 -0800 (PST) Received: from zellion.cyberwind.com (zellion.cyberwind.com [199.4.109.223]) by cyberwind.com (8.7.5/8.7.3) with ESMTP id QAA00205 for ; Sun, 23 Mar 1997 16:23:29 -0800 (PST) Message-Id: <199703240023.QAA00205@cyberwind.com> From: "Jeffery T. White" To: Subject: named Date: Sun, 23 Mar 1997 16:31:15 -0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm not sure where this should go, I'm sure if this group isn't right someone will let me know! :-) Couple of things on named: 1. The file /etc/namedb/make-localhost is a script but is not installed with the execute bit set, pretty minor but figured I'd bring it up since it seems install could do that. 2. I had to buy books to find out about the "caching-only" named setup. This setup is extremely useful for users who run small networks and connect via ppp to ISPs. It's really great to have my mail on my gateway host except up until I figured that [named] out I still had to wait while my WS did a DNS lookup for the host. With this setup the named has most of the hosts I go to in cache and is much faster. I'd be willing to write the setup up but don't know where it would be submitted? The setup files are so generic they could even become sample files in /etc/namedb... | Jeffery T. White | email: zellion@cyberwind.com | | Cyberwind, The wind knows... | http://www.cyberwind.com From owner-freebsd-current Sun Mar 23 16:35:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA12967 for current-outgoing; Sun, 23 Mar 1997 16:35:03 -0800 (PST) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12948 for ; Sun, 23 Mar 1997 16:34:57 -0800 (PST) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id SAA21690; Sun, 23 Mar 1997 18:34:40 -0600 (CST) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <19970323232413.DQ50069@uriah.heep.sax.de> References: ; from Richard Wackerbarth on Mar 23, 1997 15:12:54 -0600 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 23 Mar 1997 18:33:27 -0600 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) From: Richard Wackerbarth Subject: Re: CTM? Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 4:24 PM -0600 3/23/97, J Wunsch wrote: >As Richard Wackerbarth wrote: > >> We need to arrange to have published a list of sites that archive the >> various ctm distributions. With the generation of all the ctm >> distributions, I simply do not have the resources to also be a public >> repository of them. However, I will be happy to assist any public archiver >> in obtaining any missing pieces. > >What's wrong with freefall? Nothing if they are willing. I got them to handle 2.1 & 2.2 when I added those services. The others were already existing and I had nothing to do with their arrangements. From owner-freebsd-current Sun Mar 23 16:55:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA13998 for current-outgoing; Sun, 23 Mar 1997 16:55:16 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA13992; Sun, 23 Mar 1997 16:55:03 -0800 (PST) From: Mike Pritchard Message-Id: <199703240055.QAA13992@freefall.freebsd.org> Subject: Re: CTM? To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 23 Mar 1997 16:55:03 -0800 (PST) Cc: current@FreeBSD.ORG In-Reply-To: <19970323232413.DQ50069@uriah.heep.sax.de> from "J Wunsch" at Mar 23, 97 11:24:13 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Richard Wackerbarth wrote: > > > We need to arrange to have published a list of sites that archive the > > various ctm distributions. With the generation of all the ctm > > distributions, I simply do not have the resources to also be a public > > repository of them. However, I will be happy to assist any public archiver > > in obtaining any missing pieces. > > What's wrong with freefall? Other than it already handling more than its fair share of traffic? :-) -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-current Sun Mar 23 19:41:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA23293 for current-outgoing; Sun, 23 Mar 1997 19:41:07 -0800 (PST) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA23282 for ; Sun, 23 Mar 1997 19:41:02 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id OAA22272; Mon, 24 Mar 1997 14:40:50 +1100 (EST) From: David Dawes Message-Id: <199703240340.OAA22272@rf900.physics.usyd.edu.au> Subject: Re: src/Makefile via sup In-Reply-To: <199703222320.KAA16940@freebsd1.cimlogic.com.au> from John Birrell at "Mar 23, 97 10:20:19 am" To: jb@cimlogic.com.au (John Birrell) Date: Mon, 24 Mar 1997 14:40:49 +1100 (EST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Umm, just thought I'd get my feet wet for the first time after the Lite2 >merge, so I supped (I don't use CVSup 'cause of 2.1.5 on this machine) >and went to dive in, only to find there was no water there! 8-) >src/Makefile got deleted! So I clobbered my sup/src-base and re-supped. >src-base contains no files on sup.physics.usyd.edu.au. It should be OK now, but I'd prefer people using sup.au.freebsd.org switch over to cvsup. I'm not sure that I'll be able to offer the sup service for much longer. David From owner-freebsd-current Sun Mar 23 21:30:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA27534 for current-outgoing; Sun, 23 Mar 1997 21:30:15 -0800 (PST) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27526; Sun, 23 Mar 1997 21:30:08 -0800 (PST) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.5/8.8.5) id PAA00738; Mon, 24 Mar 1997 15:30:04 +1000 Received: from netfl15a.devetir.qld.gov.au by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with SMTP id PAA17693; Mon, 24 Mar 1997 15:32:13 +1000 (EST) Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id FAA16483; Mon, 24 Mar 1997 05:32:18 GMT Message-Id: <199703240532.FAA16483@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 2.0beta 12/23/96 To: current@freebsd.org cc: hackers@freebsd.org Subject: ctm src-cur not being mailed out? X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Mar 1997 15:32:18 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I haven't received any of ctm src-cur since src-cur.2815, despite there being a large number of commits announced since then. Likewise ports-cur has been pretty quiet as well. Any news? -- The views expressed above are not those of WorkCover Queensland, Australia. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California From owner-freebsd-current Sun Mar 23 23:21:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA03561 for current-outgoing; Sun, 23 Mar 1997 23:21:27 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA03556 for ; Sun, 23 Mar 1997 23:21:23 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA16043 for current@FreeBSD.ORG; Mon, 24 Mar 1997 08:21:18 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id HAA22241; Mon, 24 Mar 1997 07:51:30 +0100 (MET) Message-ID: <19970324075129.HN00578@uriah.heep.sax.de> Date: Mon, 24 Mar 1997 07:51:29 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: CTM? References: <19970323232413.DQ50069@uriah.heep.sax.de> <199703240055.QAA13992@freefall.freebsd.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703240055.QAA13992@freefall.freebsd.org>; from Mike Pritchard on Mar 23, 1997 16:55:03 -0800 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Mike Pritchard wrote: > > What's wrong with freefall? > > Other than it already handling more than its fair share of traffic? :-) The CTM deltas have been around for FTP there previously, too. Unless we get enough hardware contributions to get spatter running again, freefall is still our best bet. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Mar 23 23:53:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA04918 for current-outgoing; Sun, 23 Mar 1997 23:53:44 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA04912 for ; Sun, 23 Mar 1997 23:53:39 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA16333; Mon, 24 Mar 1997 08:53:26 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA22452; Mon, 24 Mar 1997 08:40:12 +0100 (MET) Message-ID: <19970324084012.GU20994@uriah.heep.sax.de> Date: Mon, 24 Mar 1997 08:40:12 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: zellion@cyberwind.com (Jeffery T. White), jkh@time.cdrom.com (Jordan K. Hubbard) Subject: Re: named References: <199703240023.QAA00205@cyberwind.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703240023.QAA00205@cyberwind.com>; from Jeffery T. White on Mar 23, 1997 16:31:15 -0800 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jeffery T. White wrote: > Couple of things on named: > 1. The file /etc/namedb/make-localhost is a script but is not installed > with the execute bit set, pretty minor but figured I'd bring it up since it > seems install could do that. People seem to run it as `sh make-localhost', but maybe it should get an x-bit, yes. > 2. I had to buy books to find out about the "caching-only" named setup. Hmm. What else than running make-localhost did you need in order to start a caching-only named? The default named.boot file does exactly this, and nothing more. I agree that perhaps sysinstall could offer setting up the named framework as an option in the network setup screen. Jordan? Despite of running make-localhost, it could also ask for forwarders, and whether the named should be caching-only. That's all you can do in a generic setup. Still enough of a framework if someone wants to add more primary or secondary zones later. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Mar 24 00:58:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA07222 for current-outgoing; Mon, 24 Mar 1997 00:58:54 -0800 (PST) Received: from critter.dk.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA07217 for ; Mon, 24 Mar 1997 00:58:50 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id IAA05798; Mon, 24 Mar 1997 08:06:38 +0100 (CET) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: current@FreeBSD.ORG Subject: Re: CTM? In-reply-to: Your message of "Sun, 23 Mar 1997 23:24:13 +0100." <19970323232413.DQ50069@uriah.heep.sax.de> Date: Mon, 24 Mar 1997 08:06:37 +0100 Message-ID: <5796.859187197@critter> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <19970323232413.DQ50069@uriah.heep.sax.de>, J Wunsch writes: >As Richard Wackerbarth wrote: > >> We need to arrange to have published a list of sites that archive the >> various ctm distributions. With the generation of all the ctm >> distributions, I simply do not have the resources to also be a public >> repository of them. However, I will be happy to assist any public archiver >> in obtaining any missing pieces. > >What's wrong with freefall? We don't want the traffic nor diskspace to be absorbed by CTM deltas... At least that used to be the concern... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Mon Mar 24 01:30:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA08801 for current-outgoing; Mon, 24 Mar 1997 01:30:59 -0800 (PST) Received: from thelab.hub.org (hal-ns1-36.netcom.ca [207.181.94.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA08793 for ; Mon, 24 Mar 1997 01:30:50 -0800 (PST) Received: from thelab.hub.org (localhost [127.0.0.1]) by thelab.hub.org (8.8.5/8.8.2) with SMTP id FAA21925 for ; Mon, 24 Mar 1997 05:30:46 -0400 (AST) Date: Mon, 24 Mar 1997 05:30:46 -0400 (AST) From: The Hermit Hacker To: current@freebsd.org Subject: make world fails in libstdc++ (CVSup'd March 24th) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... Having tried to do a 'make world' for over a week now, unsuccessfully, I'm curious how ppl are getting around the following. I've been watching the list pretty closely, and haven't seen any reports that seem to revolve around this, but may have missed it :( ===> libstdc++ c++ -O2 -pipe -I/usr/src/gnu/lib/libstdc++/../../../contrib/libg++/include -I/usr/include/g++ -I. -I/usr/src/gnu/lib/libstdc++/../../../contrib/libg++/include -I/usr/src/gnu/lib/libstdc++/../../../contrib/libg++/libio -I/usr/src/gnu/lib/libstdc++/../../. ./contrib/libg++/libstdc++ -fno-implicit-templates -DC -DREP -DMAIN -DTRAITS -DADDSS -DADDPS -DADDCS -DADDSP -DADDSC -DEQSS -DEQPS -DEQSP -DNESS -DNEPS -DNESP -DLTSS -DLTPS -DLTSP -DGTSS -DGTPS -DGTSP -DLESS -DLEPS -DLESP -DGESS -DGEPS -DGESP -c /usr/src/ gnu/lib/libstdc++/../../../contrib/libg++/libstdc++/sinst.cc -o cstrmain.o c++ -O2 -pipe -I/usr/src/gnu/lib/libstdc++/../../../contrib/libg++/include -I/usr/include/g++ -I. -I/usr/src/gnu/lib/libstdc++/../../../contrib/libg++/include -I/usr/src/gnu/lib/libstdc++/../../../contrib/libg++/libio -I/usr/src/gnu/lib/libstdc++/../../. ./contrib/libg++/libstdc++ -fno-implicit-templates -DC -DEXTRACT -DINSERT -DGETLINE -c /usr/src/gnu/lib/libstdc++/../../../contrib/libg++/libstdc++/sinst.cc -o cstrio.o /usr/src/gnu/lib/libstdc++/../../../contrib/libg++/libstdc++/sinst.cc:146: no matching template for `getline(istream &, basic_string > &)' found *** Error code 1 From owner-freebsd-current Mon Mar 24 02:45:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA12938 for current-outgoing; Mon, 24 Mar 1997 02:45:52 -0800 (PST) Received: from inter03.lion.net ([195.50.148.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA12921 for ; Mon, 24 Mar 1997 02:45:45 -0800 (PST) Received: from lucky.lion.de ([192.109.89.2]) by inter03.lion.net (Netscape Mail Server v2.0) with SMTP id AAA22969 for ; Mon, 24 Mar 1997 11:43:22 +0200 Received: from brian.lion.de by lucky.lion.de (SMI-8.6/SMI-4.1) id LAA01702; Mon, 24 Mar 1997 11:44:41 +0100 Received: from localhost by brian.lion.de (5.x/SMI-SVR4) id AA05690; Mon, 24 Mar 1997 11:44:21 +0100 Date: Mon, 24 Mar 1997 11:44:20 +0100 (MET) From: Christoph Haas To: current@freebsd.org Subject: New 2.2.1 out ? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, it was pretty late last night when I brought my repostory to the latest release. When I had a quick glance at the sources I saw a new releasetag saying it was 2.2.1-RELEASE. Did I miss something, or was it simply too late for me to understand this new tag right ? Christoph -- Christoph Haas o.tel.o GmbH | Never trust an operating UNIX Sysadmin Universitaetsstrasse 140| system you don't have the 44799 Bochum / Germany | sources for. mailto:haas@lion.de http://www.o-tel-o.de | http://www.freebsd.org From owner-freebsd-current Mon Mar 24 06:32:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA10360 for current-outgoing; Mon, 24 Mar 1997 06:32:11 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA10140; Mon, 24 Mar 1997 06:29:37 -0800 (PST) Received: by sovcom.kiae.su id AA13239 (5.65.kiae-1 ); Mon, 24 Mar 1997 17:08:08 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 24 Mar 97 17:08:07 +0300 Received: (from ache@localhost) by nagual.ru (8.8.5/8.8.5) id RAA00854; Mon, 24 Mar 1997 17:07:51 +0300 (MSK) Date: Mon, 24 Mar 1997 17:07:48 +0300 (MSK) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: peter@freebsd.org Cc: imp@freebsd.org, FreeBSD-current Subject: issetuid() Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Peter, as I remember you have plans to implement issetuid(). Right now too many changes sneaked in the source tree which require it. As I think, implementation can be done easily, just check P_SUGID bit. Also setuid() etc syscalls must be cleaned slightly to not set this bit when not really neccessary (i.e. when the same uid/gid is set). Do you have something for review at this moment? -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Mon Mar 24 06:42:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA10821 for current-outgoing; Mon, 24 Mar 1997 06:42:28 -0800 (PST) Received: from ki1.chemie.fu-berlin.de (ki1.chemie.fu-berlin.de [160.45.24.21]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA10815 for ; Mon, 24 Mar 1997 06:42:25 -0800 (PST) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mail.hanse.de (193.174.9.9) with smtp id ; Mon, 24 Mar 97 15:42 MET Received: from wavehh.UUCP by mail.hanse.de with UUCP for freebsd-current@freebsd.org id ; Mon, 24 Mar 97 15:42 MET Received: by wavehh.hanse.de (4.1/SMI-4.1) id AA04812; Mon, 24 Mar 97 14:28:55 +0100 Date: Mon, 24 Mar 97 14:28:55 +0100 From: cracauer@wavehh.hanse.de (Martin Cracauer) Message-Id: <9703241328.AA04812@wavehh.hanse.de> To: jkh@time.cdrom.COM Cc: freebsd-current@freebsd.org Subject: Re: CVS repository pushed off the FreeBSD CD distribution... Newsgroups: hanse-ml.freebsd.current References: <14067.858802322@critter.dk.tfs.com> <7234.858803671@time.cdrom.com> Reply-To: cracauer@wavehh.hanse.de Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >Despite what all the hackers may think, I feel that the ports/packages >> >still represent better value than the CVS repository so there's no >> >question in my mind about which bits get precedence, the question >> >being more one of "what do we do now for the CVS repository fans?" >> >> More SNAP cd's ? >If I don't have to put ports or packages on the SNAP CDs, sure! :-) >Remember, the SNAPs are only a single CD (and priced $10 less than the >others). >Would people prefer the SNAPs to become full CDs? They'd probably >have to go up to the $39.95/$25.94 (sub) price if I had to do 2 of >them each time, but I could make one the SNAP/package CD and the other >the unpacked CVS tree, unpacked src and unpacked ports (I'd have room >for all). >Would there be interest in something like that? I always felt that a base CTM delta would be very valuable for a CD, too. After all, CTM is for use poor people who can't ftp a 70 MB file. Anyway, my thoughts: 1) The release CD should prefer application software over the CVS tree. 2) I use the snap CD for ports, updated distfiles and such, too, so dropping these in favour of CVS and maybe CTM base wouldn't make me happy. 3) Personally, I would pay for a double CD to get all of these. 4) I suppose most other -snap subscribers would be, too, but keep in mind that raising the price could also raise the demand for less delay in getting SNAP CDs. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin_Cracauer@wavehh.hanse.de http://cracauer.cons.org Fax.: +4940 5228536 "As far as I'm concerned, if something is so complicated that you can't ex- plain it in 10 seconds, then it's probably not worth knowing anyway"- Calvin From owner-freebsd-current Mon Mar 24 06:49:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA11128 for current-outgoing; Mon, 24 Mar 1997 06:49:04 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA11122 for ; Mon, 24 Mar 1997 06:48:58 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id OAA01998 for current@freebsd.org; Mon, 24 Mar 1997 14:47:03 GMT From: mika ruohotie Message-Id: <199703241447.OAA01998@shadows.aeon.net> Subject: todays world... To: current@freebsd.org Date: Mon, 24 Mar 1997 16:47:03 +0200 (EET) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ===> sbin/dumpfs cc -O2 -m486 -pipe -c /usr/src/sbin/dumpfs/dumpfs.c /usr/src/sbin/dumpfs/dumpfs.c: In function `dumpfs': /usr/src/sbin/dumpfs/dumpfs.c:150: structure has no member named `fs_headswitch'/usr/src/sbin/dumpfs/dumpfs.c:150: structure has no member named `fs_trkseek' *** Error code 1 Stop. died. cvsup:ed from cvsup.internat.freebsd.org around 9:ish GMT mickey From owner-freebsd-current Mon Mar 24 07:10:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA12477 for current-outgoing; Mon, 24 Mar 1997 07:10:45 -0800 (PST) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.0.193]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA12470 for ; Mon, 24 Mar 1997 07:10:38 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id KAA13525; Mon, 24 Mar 1997 10:10:19 -0500 (EST) Date: Mon, 24 Mar 1997 10:10:19 -0500 (EST) From: Garrett Wollman Message-Id: <199703241510.KAA13525@khavrinen.lcs.mit.edu> To: awhawks@ibm.net Cc: current@freebsd.org Subject: Is 802.3 supported? In-Reply-To: <199703220147.UAA08708@pent.ibm.net> References: <199703220147.UAA08708@pent.ibm.net> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > I have a NE2000 card and a IBM 9229 Token-Ring to Ethernet bridge which > currently talks to everything fine except for my FreeBSD Box. I finaly > found in the docs that the default is Ethernet-II protocol. Can I set > something in the kernel that will make it use 802.3 (like the bidge) > instead? No. It's not actually very hard to do this, but we are unfortunately out of interface flags at the moment which you might set to enable/disable such translation. If you'd like to try to change the code yourself, you need to look in net/if_ethersubr.c at the function ether_output(). Rather than filling in the Ethertype in the header, you'll need to put the packet length there and folllow the Ethernet header with hex 'aa aa 03 00 00 00' and the Ethertype. This also means that the MTU of each interface would be reduced to 1494 from 1500 (one of the reasons why 802.2 encapsulation is rarely used under IP). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Mon Mar 24 07:27:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA13326 for current-outgoing; Mon, 24 Mar 1997 07:27:31 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA13218; Mon, 24 Mar 1997 07:25:50 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0w9BbH-00057u-00; Mon, 24 Mar 1997 08:23:55 -0700 To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= Subject: Re: issetuid() Cc: peter@freebsd.org, FreeBSD-current In-reply-to: Your message of "Mon, 24 Mar 1997 17:07:48 +0300." References: Date: Mon, 24 Mar 1997 08:23:55 -0700 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= writes: : Peter, as I remember you have plans to implement issetuid(). Right now too : many changes sneaked in the source tree which require it. As I think, : implementation can be done easily, just check P_SUGID bit. Also setuid() : etc syscalls must be cleaned slightly to not set this bit when not really : neccessary (i.e. when the same uid/gid is set). Do you have something for : review at this moment? There were already a bunch of other places that used the same code I did, or a variation on them. I at least tagged my with XXX should use issetugid(), others didn't. Warner From owner-freebsd-current Mon Mar 24 09:21:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA19391 for current-outgoing; Mon, 24 Mar 1997 09:21:19 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA19384 for ; Mon, 24 Mar 1997 09:21:16 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id JAA27940; Mon, 24 Mar 1997 09:21:16 -0800 (PST) To: Christoph Haas cc: current@freebsd.org Subject: Re: New 2.2.1 out ? In-reply-to: Your message of "Mon, 24 Mar 1997 11:44:20 +0100." Date: Mon, 24 Mar 1997 09:21:16 -0800 Message-ID: <27937.859224076@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > it was pretty late last night when I brought my repostory to the latest > release. When I had a quick glance at the sources I saw a new releasetag > saying it was 2.2.1-RELEASE. Did I miss something, or was it simply too > late for me to understand this new tag right ? You haven't missed anything - I haven't announced it yet. I usually like to give the mirrors a day or two to get the bits before I make their existence more public. Jordan From owner-freebsd-current Mon Mar 24 09:22:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA19481 for current-outgoing; Mon, 24 Mar 1997 09:22:24 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA19475 for ; Mon, 24 Mar 1997 09:22:21 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA22902; Mon, 24 Mar 1997 10:09:01 -0700 From: Terry Lambert Message-Id: <199703241709.KAA22902@phaeton.artisoft.com> Subject: Re: Is 802.3 supported? To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Mon, 24 Mar 1997 10:09:01 -0700 (MST) Cc: awhawks@ibm.net, current@freebsd.org In-Reply-To: <199703241510.KAA13525@khavrinen.lcs.mit.edu> from "Garrett Wollman" at Mar 24, 97 10:10:19 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I have a NE2000 card and a IBM 9229 Token-Ring to Ethernet bridge which > > currently talks to everything fine except for my FreeBSD Box. I finaly > > found in the docs that the default is Ethernet-II protocol. Can I set > > something in the kernel that will make it use 802.3 (like the bidge) > > instead? > > No. It's not actually very hard to do this, but we are unfortunately > out of interface flags at the moment which you might set to > enable/disable such translation. > > If you'd like to try to change the code yourself, you need to look in > net/if_ethersubr.c at the function ether_output(). Rather than > filling in the Ethertype in the header, you'll need to put the packet > length there and folllow the Ethernet header with hex 'aa aa 03 00 00 > 00' and the Ethertype. This also means that the MTU of each interface > would be reduced to 1494 from 1500 (one of the reasons why 802.2 > encapsulation is rarely used under IP). Doesn't the FDDI interface use 802.3 encapsulation? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Mar 24 09:58:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA21960 for current-outgoing; Mon, 24 Mar 1997 09:58:15 -0800 (PST) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA21936 for ; Mon, 24 Mar 1997 09:57:35 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id RAA03608 for current@freebsd.org; Mon, 24 Mar 1997 17:54:46 GMT From: mika ruohotie Message-Id: <199703241754.RAA03608@shadows.aeon.net> Subject: Re: todays world... In-Reply-To: <199703241447.OAA01998@shadows.aeon.net> from mika ruohotie at "Mar 24, 97 04:47:03 pm" To: current@freebsd.org Date: Mon, 24 Mar 1997 19:54:45 +0200 (EET) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > ===> sbin/dumpfs > cc -O2 -m486 -pipe -c /usr/src/sbin/dumpfs/dumpfs.c > /usr/src/sbin/dumpfs/dumpfs.c: In function `dumpfs': > /usr/src/sbin/dumpfs/dumpfs.c:150: structure has no member named `fs_headswitch'/usr/src/sbin/dumpfs/dumpfs.c:150: structure has no member named `fs_trkseek' > *** Error code 1 > > Stop. > > died. > > cvsup:ed from cvsup.internat.freebsd.org around 9:ish GMT well... *gasp* i found an error and this was the fix i was able to figure easily, not that i know it's the right one, but it might be the right one. i guess there's first time for everything... =) shadows# diff -u fs.h.orig fs.h --- fs.h.orig Mon Mar 24 19:38:20 1997 +++ fs.h Mon Mar 24 19:41:03 1997 @@ -176,6 +176,8 @@ /* these are configuration parameters */ int32_t fs_minfree; /* minimum percentage of free blocks */ int32_t fs_rotdelay; /* num of ms for optimal next block */ + int32_t fs_headswitch; /* dont expect me to know what i am */ + int32_t fs_trkseek; /* actually doing, it might work tho */ int32_t fs_rps; /* disk revolutions per second */ /* these fields can be computed from the others */ int32_t fs_bmask; /* ``blkoff'' calc of blk offsets */ shadows# after that it compiles... (ok, so it looks easy...) =) oh, and i think i should've mentioned that's 3.0-CURRENT i am using, though that this is current-list it doesnt mean it's obvious what i'd talk about. mickey From owner-freebsd-current Mon Mar 24 10:03:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA22483 for current-outgoing; Mon, 24 Mar 1997 10:03:49 -0800 (PST) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA22466 for ; Mon, 24 Mar 1997 10:03:43 -0800 (PST) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id RAA08546; Mon, 24 Mar 1997 17:46:18 GMT Date: Mon, 24 Mar 1997 17:42:23 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Mon, 24 Mar 1997 17:42:23 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <9703241328.AA04812@wavehh.hanse.de> References: <14067.858802322@critter.dk.tfs.com> <7234.858803671@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: jkh@time.cdrom.COM From: Bob Bishop Subject: Re: CVS repository pushed off the FreeBSD CD distribution... Cc: cracauer@wavehh.hanse.de, freebsd-current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk At 1:28 pm -0000 24/3/97, Martin Cracauer wrote: >[...] >I always felt that a base CTM delta would be very valuable for a CD, >too. After all, CTM is for use poor people who can't ftp a 70 MB >file.[etc] Hear hear -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Mon Mar 24 11:20:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA28823 for current-outgoing; Mon, 24 Mar 1997 11:20:46 -0800 (PST) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA28816 for ; Mon, 24 Mar 1997 11:20:40 -0800 (PST) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id TAA09038; Mon, 24 Mar 1997 19:16:32 GMT Date: Mon, 24 Mar 1997 19:08:25 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Mon, 24 Mar 1997 19:08:25 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199703231827.FAA08659@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Bruce Evans From: Bob Bishop Subject: Re: 2.2R (src 2.2 211): == dialing Cc: freebsd-current@freebsd.org, joerg_wunsch@uriah.heep.sax.de, terry@lambert.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 6:27 pm -0000 23/3/97, Bruce Evans wrote: >`man 2 _exit' says much the same things as POSIX about SIGHUP on exit. >It points to intro(2) for definitions of pg's/sessions. I was trying to complain that this description seems incomplete: the fact that live processes get signalled when multi-user operation ceases doesn't seem to be documented. In the case under discussion, the processes haven't exited. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Mon Mar 24 11:33:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA29756 for current-outgoing; Mon, 24 Mar 1997 11:33:38 -0800 (PST) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA29748 for ; Mon, 24 Mar 1997 11:33:29 -0800 (PST) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id TAA09087; Mon, 24 Mar 1997 19:31:17 GMT Date: Mon, 24 Mar 1997 19:28:58 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Mon, 24 Mar 1997 19:28:58 GMT X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Terry Lambert From: Bob Bishop Subject: Re: 2.2R (src 2.2 211): == dialing Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 7:13 pm -0000 23/3/97, Terry Lambert wrote: >I happen to disagree with the BSD interpretation of POSIX in this >regard. SVR4 is certified POSIX compliant, and they don't do what >we do: they propagate group SIGHUP to all process group members. >You can argue until you are blue in the face that SVR4 is "wrong", >but to prove it to me you will have to get an SVR4 box to fail >POSIX compliance testing. You can't argue with success. That's slightly off my point, which was that daemons (I probably mean something like "sessions with no controlling tty") shouldn't get signalled with HUP when multi-user operation is being ceased. Interactive sessions should, because interactive shells don't respond to TERM. I'll be going off into my POSIX sulk now... -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Mon Mar 24 12:22:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA02838 for current-outgoing; Mon, 24 Mar 1997 12:22:49 -0800 (PST) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA02833 for ; Mon, 24 Mar 1997 12:22:36 -0800 (PST) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id VAA06956; Mon, 24 Mar 1997 21:20:25 +0100 (MET) From: Wolfgang Helbig Message-Id: <199703242020.VAA06956@helbig.informatik.ba-stuttgart.de> Subject: Re: todays world... In-Reply-To: <199703241754.RAA03608@shadows.aeon.net> from mika ruohotie at "Mar 24, 97 07:54:45 pm" To: bsdcur@shadows.aeon.net (mika ruohotie) Date: Mon, 24 Mar 1997 21:20:24 +0100 (MET) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Mika, > > ===> sbin/dumpfs > > cc -O2 -m486 -pipe -c /usr/src/sbin/dumpfs/dumpfs.c > > /usr/src/sbin/dumpfs/dumpfs.c: In function `dumpfs': > > /usr/src/sbin/dumpfs/dumpfs.c:150: structure has no member named `fs_headswitch'/usr/src/sbin/dumpfs/dumpfs.c:150: structure has no member named `fs_trkseek' > > *** Error code 1 > > > > Stop. > > > > died. > > > > cvsup:ed from cvsup.internat.freebsd.org around 9:ish GMT > > well... > > *gasp* > > i found an error and this was the fix i was able to figure easily, not > that i know it's the right one, but it might be the right one. > > i guess there's first time for everything... =) > > > shadows# diff -u fs.h.orig fs.h > --- fs.h.orig Mon Mar 24 19:38:20 1997 > +++ fs.h Mon Mar 24 19:41:03 1997 > @@ -176,6 +176,8 @@ > /* these are configuration parameters */ > int32_t fs_minfree; /* minimum percentage of free blocks */ > int32_t fs_rotdelay; /* num of ms for optimal next block */ > + int32_t fs_headswitch; /* dont expect me to know what i am */ > + int32_t fs_trkseek; /* actually doing, it might work tho */ > int32_t fs_rps; /* disk revolutions per second */ > /* these fields can be computed from the others */ > int32_t fs_bmask; /* ``blkoff'' calc of blk offsets */ > shadows# > > > after that it compiles... (ok, so it looks easy...) =) Sorry Mickey, but your fix does'not seem to work. As I learned from the cvs log messages for the two latest committments to sys/ufs/ffs/fs.h, the two fields fs_headswitch and fs_trkseek are not used any more and their space is taken by the new field fs_id[2]. The structure fs describes the superblock, i. e. a fixed length entity on the harddisk and you should by no means change the size of it in fs.h. Programs #including fs.h might crash your file system and you might have to resort to your backup tapes. For this reason I propose the following patch to be applied to dumpfs.c : (I *do* hope its not too late for you) Wishing you luck, Wolfgang Index: dumpfs.c =================================================================== RCS file: /usr/cvsroot/src/sbin/dumpfs/dumpfs.c,v retrieving revision 1.6 diff -c -r1.6 dumpfs.c *** dumpfs.c 1997/03/11 12:12:26 1.6 --- dumpfs.c 1997/03/24 19:42:20 *************** *** 146,153 **** printf("minfree\t%d%%\toptim\t%s\tmaxcontig %d\tmaxbpg\t%d\n", afs.fs_minfree, afs.fs_optim == FS_OPTSPACE ? "space" : "time", afs.fs_maxcontig, afs.fs_maxbpg); ! printf("rotdelay %dms\theadswitch %dus\ttrackseek %dus\trps\t%d\n", ! afs.fs_rotdelay, afs.fs_headswitch, afs.fs_trkseek, afs.fs_rps); printf("ntrak\t%d\tnsect\t%d\tnpsect\t%d\tspc\t%d\n", afs.fs_ntrak, afs.fs_nsect, afs.fs_npsect, afs.fs_spc); printf("symlinklen %d\ttrackskew %d\tinterleave %d\tcontigsumsize %d\n", --- 146,153 ---- printf("minfree\t%d%%\toptim\t%s\tmaxcontig %d\tmaxbpg\t%d\n", afs.fs_minfree, afs.fs_optim == FS_OPTSPACE ? "space" : "time", afs.fs_maxcontig, afs.fs_maxbpg); ! printf("rotdelay %dms\trps\t%d\n", ! afs.fs_rotdelay, afs.fs_rps); printf("ntrak\t%d\tnsect\t%d\tnpsect\t%d\tspc\t%d\n", afs.fs_ntrak, afs.fs_nsect, afs.fs_npsect, afs.fs_spc); printf("symlinklen %d\ttrackskew %d\tinterleave %d\tcontigsumsize %d\n", From owner-freebsd-current Mon Mar 24 12:35:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA03795 for current-outgoing; Mon, 24 Mar 1997 12:35:11 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA03786; Mon, 24 Mar 1997 12:35:03 -0800 (PST) From: Mike Pritchard Message-Id: <199703242035.MAA03786@freefall.freebsd.org> Subject: Re: todays world... To: bsdcur@shadows.aeon.net (mika ruohotie) Date: Mon, 24 Mar 1997 12:35:03 -0800 (PST) Cc: current@freebsd.org In-Reply-To: <199703241754.RAA03608@shadows.aeon.net> from "mika ruohotie" at Mar 24, 97 07:54:45 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk mika ruohotie wrote: > > > ===> sbin/dumpfs > > cc -O2 -m486 -pipe -c /usr/src/sbin/dumpfs/dumpfs.c > > /usr/src/sbin/dumpfs/dumpfs.c: In function `dumpfs': > > /usr/src/sbin/dumpfs/dumpfs.c:150: structure has no member named `fs_headswitch'/usr/src/sbin/dumpfs/dumpfs.c:150: structure has no member named `fs_trkseek' > > *** Error code 1 Those two (unused) fields were replaced by the fs_id member. Dumpfs needs to be updated to reflect this. -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-current Mon Mar 24 13:09:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA06129 for current-outgoing; Mon, 24 Mar 1997 13:09:02 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA06050 for ; Mon, 24 Mar 1997 13:08:13 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id WAA03474 for ; Mon, 24 Mar 1997 22:07:53 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id WAA32059 for current@freebsd.org; Mon, 24 Mar 1997 22:07:37 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id VAA19080; Mon, 24 Mar 1997 21:42:29 +0100 (CET) Message-ID: <19970324214229.61320@keltia.freenix.fr> Date: Mon, 24 Mar 1997 21:42:29 +0100 From: Ollivier Robert To: current@freebsd.org Subject: Re: make world fails in libstdc++ (CVSup'd March 24th) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.65,1-4,10,14-18 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3153 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to The Hermit Hacker: > Having tried to do a 'make world' for over a week now, unsuccessfully, > I'm curious how ppl are getting around the following. I've been watching > the list pretty closely, and haven't seen any reports that seem to revolve > around this, but may have missed it :( I'm surprised. I completed my first "make world" since the Lite2 merge yesterday and it was perfect... ... Rebuilding man page indexes -------------------------------------------------------------- cd /usr/src/share/man && make makedb makewhatis /usr/share/man -------------------------------------------------------------- make world completed on Mon Mar 24 03:50:36 CET 1997 -------------------------------------------------------------- 15825.34 real 11325.72 user 2464.89 sys -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #41: Sun Mar 23 23:01:22 CET 1997 From owner-freebsd-current Mon Mar 24 13:55:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA11558 for current-outgoing; Mon, 24 Mar 1997 13:55:43 -0800 (PST) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA11551 for ; Mon, 24 Mar 1997 13:55:38 -0800 (PST) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id NAA12305 for ; Mon, 24 Mar 1997 13:58:17 -0800 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id QAA29803; Mon, 24 Mar 1997 16:55:00 -0500 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id QAA27175; Mon, 24 Mar 1997 16:55:00 -0500 Received: (from alk@localhost) by compound.east.sun.com (8.8.5/8.7.3) id PAA06055; Mon, 24 Mar 1997 15:55:03 -0600 (CST) Date: Mon, 24 Mar 1997 15:55:03 -0600 (CST) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199703242155.PAA06055@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: current@freebsd.org Subject: Re: 2.2R (src 2.2 211): == dialing X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What really bugs me about 3.0 is that children now get the SIGTSTPs of the parents. From owner-freebsd-current Mon Mar 24 13:56:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA11731 for current-outgoing; Mon, 24 Mar 1997 13:56:30 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11711 for ; Mon, 24 Mar 1997 13:56:23 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id VAA25658; Mon, 24 Mar 1997 21:52:57 GMT From: mika ruohotie Message-Id: <199703242152.VAA25658@shadows.aeon.net> Subject: Re: todays world... In-Reply-To: <199703242020.VAA06956@helbig.informatik.ba-stuttgart.de> from Wolfgang Helbig at "Mar 24, 97 09:20:24 pm" To: helbig@MX.BA-Stuttgart.De (Wolfgang Helbig) Date: Mon, 24 Mar 1997 23:52:56 +0200 (EET) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi Mika, =) > > after that it compiles... (ok, so it looks easy...) =) > Sorry Mickey, but your fix does'not seem to work. it compiled... yes, i know compiles != work > As I learned from the cvs log messages for the two latest committments > to sys/ufs/ffs/fs.h, the two fields fs_headswitch and fs_trkseek are not > used any more and their space is taken by the new field fs_id[2]. maybe yet another list i should read? > fs.h. Programs #including fs.h might crash your file system and you might > have to resort to your backup tapes. yes, i was assuming sys/* is the very wrong place to make "i have no clue about this stuff" -class hacks... > (I *do* hope its not too late for you) i was making world, but dumped it after i read this. no big deal i hope. and then i made cvsup, but apparently internat is behind... :\ so i dont restart the make world tonite... :p gladly i have only p133 and world takes almost 4 hours. > Wolfgang mickey From owner-freebsd-current Mon Mar 24 13:57:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA11819 for current-outgoing; Mon, 24 Mar 1997 13:57:04 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11810 for ; Mon, 24 Mar 1997 13:56:59 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id VAA25665; Mon, 24 Mar 1997 21:54:16 GMT From: mika ruohotie Message-Id: <199703242154.VAA25665@shadows.aeon.net> Subject: Re: todays world... In-Reply-To: <199703242035.MAA03786@freefall.freebsd.org> from Mike Pritchard at "Mar 24, 97 12:35:03 pm" To: mpp@freefall.freebsd.org (Mike Pritchard) Date: Mon, 24 Mar 1997 23:54:16 +0200 (EET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > mika ruohotie wrote: > > > /usr/src/sbin/dumpfs/dumpfs.c: In function `dumpfs': > Those two (unused) fields were replaced by the fs_id member. > Dumpfs needs to be updated to reflect this. it was make world hickup and still it seems internat.freebsd.org gives me old dumpfs.c i've attempted few times. mickey From owner-freebsd-current Mon Mar 24 14:53:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA16697 for current-outgoing; Mon, 24 Mar 1997 14:53:36 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA16688 for ; Mon, 24 Mar 1997 14:53:31 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA23808; Mon, 24 Mar 1997 15:40:30 -0700 From: Terry Lambert Message-Id: <199703242240.PAA23808@phaeton.artisoft.com> Subject: Re: 2.2R (src 2.2 211): == dialing To: Anthony.Kimball@East.Sun.COM Date: Mon, 24 Mar 1997 15:40:30 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <199703242155.PAA06055@compound.east.sun.com> from "Tony Kimball" at Mar 24, 97 03:55:03 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > What really bugs me about 3.0 is that children now > get the SIGTSTPs of the parents. If they are the session leader, then this is the correct behaviour. You are supposed to be able to have multiple sessions (jobs) for a given tty. The is, in effect, a "detach and block if output until reattach". One very annoying thing is that even though there is no read, you will get a "stopped" message for a job thrown in the background. This is, I think, a bug in the way job control is being handled (it doesn't do this on my Sun box; the Sun just happily cranks along until input is required, *then* gives the message. Generally, I've got back to it by then. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Mar 24 15:36:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA19678 for current-outgoing; Mon, 24 Mar 1997 15:36:47 -0800 (PST) Received: from thelab.hub.org (hal-ns1-09.netcom.ca [207.181.94.73]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA19665 for ; Mon, 24 Mar 1997 15:36:38 -0800 (PST) Received: from thelab.hub.org (localhost [127.0.0.1]) by thelab.hub.org (8.8.5/8.8.2) with SMTP id TAA26444; Mon, 24 Mar 1997 19:35:51 -0400 (AST) Date: Mon, 24 Mar 1997 19:35:51 -0400 (AST) From: The Hermit Hacker To: Ollivier Robert cc: current@FreeBSD.org Subject: Re: make world fails in libstdc++ (CVSup'd March 24th) In-Reply-To: <19970324214229.61320@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Mar 1997, Ollivier Robert wrote: > According to The Hermit Hacker: > > Having tried to do a 'make world' for over a week now, unsuccessfully, > > I'm curious how ppl are getting around the following. I've been watching > > the list pretty closely, and haven't seen any reports that seem to revolve > > around this, but may have missed it :( > > I'm surprised. I completed my first "make world" since the Lite2 merge > yesterday and it was perfect... > I'm surprised too, since nobody else seems to have noticed it either :( I've even go to the trouble of removing the offending file and re-cvsup'ng it, just in case it might have gotten truncated or something, same problem... From owner-freebsd-current Mon Mar 24 18:38:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA02733 for current-outgoing; Mon, 24 Mar 1997 18:38:21 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA02714 for ; Mon, 24 Mar 1997 18:38:14 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id NAA06930; Tue, 25 Mar 1997 13:34:25 +1100 Date: Tue, 25 Mar 1997 13:34:25 +1100 From: Bruce Evans Message-Id: <199703250234.NAA06930@godzilla.zeta.org.au> To: bde@zeta.org.au, rb@gid.co.uk Subject: Re: 2.2R (src 2.2 211): == dialing Cc: freebsd-current@freebsd.org, joerg_wunsch@uriah.heep.sax.de, terry@lambert.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>`man 2 _exit' says much the same things as POSIX about SIGHUP on exit. >>It points to intro(2) for definitions of pg's/sessions. > >I was trying to complain that this description seems incomplete: the fact >that live processes get signalled when multi-user operation ceases doesn't >seem to be documented. In the case under discussion, the processes haven't >exited. This has nothing to do with POSIX signals or process groups. It is much simpler. It is mostly documented in init(8): 1. If someone hits Ctrl-Alt-Del, then a SIGINT is usually sent to init. 2. Init shuts down and reboots when it receives a SIGINT. 3. Init shuts things down by broadcasting signals of increasing severity { SIGHUP, SIGTERM, SIGKILL }. 4. Some process like ppp do bad things when they receive a SIGHUP. This differs from when the system is shut down using reboot(8). reboot shuts things down by broadcasting signals of increasing severity { SIGTERM, SIGKILL }. I don't know why init broadcasts SIGHUP or why reboot doesn't just signal init. Bruce From owner-freebsd-current Mon Mar 24 19:01:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA04560 for current-outgoing; Mon, 24 Mar 1997 19:01:13 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA04555; Mon, 24 Mar 1997 19:01:09 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id TAA01135; Mon, 24 Mar 1997 19:01:15 -0800 (PST) To: announce@freebsd.org cc: current@freebsd.org Subject: 2.2.1-RELEASE will be [re]appearing shortly.. Date: Mon, 24 Mar 1997 19:01:15 -0800 Message-ID: <1131.859258875@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just to explain in advance what's going on for those who are curiously noting that "2.2-RELEASE" suddenly went away on ftp.freebsd.org and some of its mirrors. We found some issues with the 2940 driver and several other areas of the system which really were on the "cusp" of being fixed, and it seemed an unnecessary waste to make 2.2R users wait another 4 months or so for 2.2.5 to come out before getting these fixes when we had them available less than a week after release time (especially when many of those fixes had already gone into an "older" release, 2.1.7.1) and there were many emails demanding this, so... Let it never be said that we're not responsive to customer demands! :-) A tentative 2.2.1R release did appear on wcarchive for a short time, as some of you may have also noticed, but it was withdrawn again before being announced when Justin came up with several additional fixes for the 2940 which he really wanted to get in. John Dyson has also noted that some VM system fixes in -current didn't make it back into 2.2, apparently (it seems it always takes a full release to find these things out), and he'd like some time to look into this before I crank that old release machine's handle once again and hopefully put 2.2-RELEASE to bed for the LAST time for the next few months. Since the 2.2R CDROM has not yet been pressed, whatever I finally come up with in these next few hours WILL be shipped as 2.2-RELEASE on CDROM. As it says in the release notes, 2.2.1R is a full replacement for 2.2.0R and once all this dust settles then everyone should just pretend that the earlier release never happened. :-) Jordan From owner-freebsd-current Mon Mar 24 19:15:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA05949 for current-outgoing; Mon, 24 Mar 1997 19:15:29 -0800 (PST) Received: from cyberwind.com (cyberwind.com [199.4.109.220]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA05944 for ; Mon, 24 Mar 1997 19:15:25 -0800 (PST) Received: from zellion.cyberwind.com (zellion.cyberwind.com [199.4.109.223]) by cyberwind.com (8.7.5/8.7.3) with ESMTP id TAA00502; Mon, 24 Mar 1997 19:15:40 -0800 (PST) Message-Id: <199703250315.TAA00502@cyberwind.com> From: "Jeffery T. White" To: "Joerg Wunsch" , Cc: "Jordan K. Hubbard" Subject: Re: named Date: Mon, 24 Mar 1997 19:23:35 -0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ---------- > From: J Wunsch > To: current@FreeBSD.ORG > Cc: Jeffery T. White ; Jordan K. Hubbard > Subject: Re: named > Date: Sunday, March 23, 1997 11:40 PM > > As Jeffery T. White wrote: > > > Couple of things on named: > > 1. The file /etc/namedb/make-localhost is a script but is not installed > > with the execute bit set, pretty minor but figured I'd bring it up since it > > seems install could do that. > > People seem to run it as `sh make-localhost', but maybe it should get > an x-bit, yes. > > > 2. I had to buy books to find out about the "caching-only" named setup. > > Hmm. What else than running make-localhost did you need in order to > start a caching-only named? The default named.boot file does exactly > this, and nothing more. > > I agree that perhaps sysinstall could offer setting up the named > framework as an option in the network setup screen. Jordan? Despite > of running make-localhost, it could also ask for forwarders, and > whether the named should be caching-only. That's all you can do in a > generic setup. Still enough of a framework if someone wants to add > more primary or secondary zones later. Ahh, yes you are right the sample files do just that, they just don't tell you in the comments. The thing is that the average joe doesn't even know that. The man page leads one to believe that they need to setup a secondary or primary server. About half way through the named man page I was like "Yikes this is serious" :-) and I suppose setting up a primary or secondary is not a process to be taken lightly however this is a no brainer if a person just knew that it exists in the first place. The install idea would be really cool. One thing I added was a cron entry to fetch a new named.root from NIC every so often, if you were going to do a sysinstall that might also be something to think about. If not it still might be a useful commented out line... | Jeffery T. White | email: zellion@cyberwind.com | | Cyberwind, The wind knows... | http://www.cyberwind.com From owner-freebsd-current Mon Mar 24 21:26:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA18990 for current-outgoing; Mon, 24 Mar 1997 21:26:33 -0800 (PST) Received: from mail.konnections.com (mail.konnections.com [192.41.71.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA18945; Mon, 24 Mar 1997 21:26:12 -0800 (PST) Received: from castle (root@ip211.konnections.com [192.41.71.211]) by mail.konnections.com (8.8.3/8.8.3) with SMTP id WAA07704; Mon, 24 Mar 1997 22:25:35 -0700 (MST) Message-ID: <3338B212.752C9086@konnections.com> Date: Tue, 25 Mar 1997 22:20:18 -0700 From: mike allison Organization: Publisher -- Burning Eagle Book Company X-Mailer: Mozilla 3.0 (X11; I; Linux 2.0.0 i486) MIME-Version: 1.0 To: "Jeffery T. White" CC: current@freebsd.org, FreeBSD-chat@freebsd.org Subject: Re: named References: <199703240023.QAA00205@cyberwind.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jeffery, I don't know where you'd submit it for FreeBSD, but I'd like a blurb on this with the setup code/script to publish in Free Systems Journal. Please respond to me at ed@konnections.com or mallison@konnections.com if you'd like to submit. (An article, that is : -} ) Thanks all, -Mike Jeffery T. White wrote: > > I'm not sure where this should go, I'm sure if this group isn't right > someone will let me know! :-) > > Couple of things on named: > 1. The file /etc/namedb/make-localhost is a script but is not installed > with the execute bit set, pretty minor but figured I'd bring it up since it > seems install could do that. > > 2. I had to buy books to find out about the "caching-only" named setup. > This setup is extremely useful for users who run small networks and connect > via ppp to ISPs. I'd be willing to write the > setup up but don't know where it would be submitted? The setup files are so > generic they could even become sample files in /etc/namedb... > > | Jeffery T. White > | email: zellion@cyberwind.com > | > | Cyberwind, The wind knows... > | http://www.cyberwind.com From owner-freebsd-current Mon Mar 24 21:38:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA19905 for current-outgoing; Mon, 24 Mar 1997 21:38:15 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA19889 for ; Mon, 24 Mar 1997 21:38:12 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) with SMTP id AAA04663 for ; Tue, 25 Mar 1997 00:32:08 -0500 (EST) Date: Tue, 25 Mar 1997 00:32:07 -0500 (EST) From: Mark Mayo To: freebsd-current@freebsd.org Subject: Burning a 2.2.1R CDROM myself.. How? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a few friends who I've convinced to leave Linux/Windows and move to FreeBSD! Since the 2.2 CD-ROM from Walnut Creek is not out yet, I wanted to burn my own copy so my buddies can install 2.2 (or 2.2.1 it would now appear to be). I've been telling them to wait for 2.2 since Dec. and if I don't give them the CD now they'll stay on linux :-( How do I go about arranging the data to burn a CD? I've noticed in the past that the CD directory structure isn't the same as the FTP site, so I'm assuming I can't just suck down the FTP distribution and burn it onto the CD. I noticed a "make release" in /usr/src/Makefile. Is this what I'm looking for? How much free space will I need if I do a make release? What does make release actually do? Now I have to figure out how to get the external HP SureStor writer working under FreeBSD so I don't have to run the stupid win95 program... TIA, -Mark ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ GCS/O d- s+ a-- C++ UB+++$ P+ L- E--- W++ N+ K- w++(---) O- M- !V PS+ PE Y++ PGP+ t !5 X+ R- tv b++ DI+ D++ G+ e+(*) h--- r++ y+(+++) ---------------------------------------------------------------------------- "Typically, I don't use JAVA -- I think that strong typing is for weak minds (and lazy compiler/interpreter writers)." -- Terry Lambert From owner-freebsd-current Mon Mar 24 22:20:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA21761 for current-outgoing; Mon, 24 Mar 1997 22:20:15 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA21756 for ; Mon, 24 Mar 1997 22:20:12 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA00924; Mon, 24 Mar 1997 22:20:07 -0800 (PST) To: Mark Mayo cc: freebsd-current@FreeBSD.ORG Subject: Re: Burning a 2.2.1R CDROM myself.. How? In-reply-to: Your message of "Tue, 25 Mar 1997 00:32:07 EST." Date: Mon, 24 Mar 1997 22:20:07 -0800 Message-ID: <921.859270807@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > How do I go about arranging the data to burn a CD? I've noticed in the > past that the CD directory structure isn't the same as the FTP site, so > I'm assuming I can't just suck down the FTP distribution and burn it onto > the CD. Actually, nowadays you can do exactly that. :-) The release bits are the same in either case, as far as sysinstall is concerned, anyway. > Now I have to figure out how to get the external HP SureStor writer > working under FreeBSD so I don't have to run the stupid win95 program... /usr/share/examples/worm :-) Jordan From owner-freebsd-current Mon Mar 24 23:26:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA23935 for current-outgoing; Mon, 24 Mar 1997 23:26:34 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (ala-ca12-08.ix.netcom.com [199.35.209.200]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA23922; Mon, 24 Mar 1997 23:26:23 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id XAA01567; Mon, 24 Mar 1997 23:26:17 -0800 (PST) Date: Mon, 24 Mar 1997 23:26:17 -0800 (PST) Message-Id: <199703250726.XAA01567@silvia.HIP.Berkeley.EDU> To: wosch@freebsd.org CC: current@freebsd.org, mita@jp.FreeBSD.org Subject: -current uudecode can't grok one of japanese/vfxdvi's distfiles From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The following command: === zcat /usr/ports/distfiles/xdvi/950923.02.Z | uudecode === works fine on a 2.2R system but dies with: === uudecode: input file: stdin encoded file: xdvi-pl17+markpage+toc+printdvi+paper.patch.gz character out of range: [33-96] === on a -current (from yesterday) system. Looking at the uudecode source, this change seems to be the difference. === revision 1.5 date: 1997/02/18 17:49:43; author: wosch; state: Exp; lines: +32 -1 Better check for detecting header line. A header line must match "begin [0-7]* *". Now `begin with, ' is not a header line. Do a boundary check for body characters. Characters less than 33 or greater than 96 are out of range. If characters are out of range uudecode print a error message and die. === Is this check really necessary? This file used to decode fine with the old decoder. Besides, I can't figure out for the life of myself which character it's barfing on. === >> tr ' -_\n' ' ' <950923.02 | od -c 0000000 b e g i n x d v i p 0000020 l m a r k p a g e t o c 0000040 p r i n t d v i p a p e r 0000060 p a t c h g z 0000100 * 0141300 e 0141320 n d 0141323 === Seems like everything between the "begin" line and "end" are in range.... Satoshi From owner-freebsd-current Tue Mar 25 00:15:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA27213 for current-outgoing; Tue, 25 Mar 1997 00:15:36 -0800 (PST) Received: from proxy2.ba.best.com (root@proxy2.ba.best.com [206.184.139.13]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA27204; Tue, 25 Mar 1997 00:15:33 -0800 (PST) Received: from bsampley.vip.best.com (bsampley.vip.best.com [206.184.160.196]) by proxy2.ba.best.com (8.8.5/8.8.3) with SMTP id AAA23808; Tue, 25 Mar 1997 00:14:20 -0800 (PST) Date: Tue, 25 Mar 1997 00:13:26 -0800 (PST) From: Burton Sampley To: questions@freebsd.org cc: current@freebsd.org Subject: Fetchmail nolonger working Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I'm using 3.0-current (last cvsup date is 97.02.10.00.00.00, which is prior to the lite2 merge). Make world will complete, without any error messages and I recompiled my kernel after the last successful make world. I have been using fetchmail for quite some time with the same version of FBSD. Recently I shut down my system for about 2 1/2 days (because it's a home system and I was gone). When I fired the machine up again fetchmail would 'run' but could nolonger D/L my mail. This machine had been off and on for most of it's life. It's not a server, so I have no reason to keep the machine up 24/7 (unless I want to help keep PG&E in business). The error message I get when I run fetchmail -av is SMTP connection failed. I have two email accounts (on different servers), so I have a .fetchmailrc file which has never been modified. Any ideas? Here's the output from dmesg: Copyright (c) 1992-1996 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Mon Mar 24 13:32:44 PST 1997 root@bsampley.vip.best.com:/usr/src/sys/compile/custom301 Calibrating clock(s) relative to mc146818A clock ... i586 clock: 133645355 Hz, i8254 clock: 1193265 Hz CPU: Pentium (133.64-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 62595072 (61128K bytes) Probing for devices on PCI bus 0: chip0 rev 3 on pci0:0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 de0 rev 35 int a irq 10 on pci0:10:0 de0: SMC 8432BT 21040 [10Mb/s] pass 2.3 de0: address 00:00:c0:5d:65:0e de0: enabling BNC/AUI port vga0 rev 2 int a irq 11 on pci0:11:0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, accel, dma, iordis wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 3020MB (6185088 sectors), 6136 cyls, 16 heads, 63 S/T, 512 B/S nca0 at 0x1f88-0x1f8b irq 10 on isa nca0: type ProAudioSpectrum-16 nca0: waiting for scsi devices to settle scbus0 at nca0 bus 0 npx0 on motherboard npx0: INT 16 interface pas0 at 0x388 irq 10 drq 6 on isa pas0 not probed due to irq conflict with nca0 at 10 joy0 at 0x201 on isa joy0: joystick --- Brought to you by a 100% Micro$oft free system. You too can disinfect your system at http://www.freebsd.org E-Mail: burton@bsampley.vip.best.com Alternate E-Mail: bsampley@haywire.csuhayward.edu Home Page: http://www.best.com/~bsampley (permanently under construction) From owner-freebsd-current Tue Mar 25 02:56:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA05334 for current-outgoing; Tue, 25 Mar 1997 02:56:49 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (ala-ca12-08.ix.netcom.com [199.35.209.200]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA05329; Tue, 25 Mar 1997 02:56:44 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id CAA02575; Tue, 25 Mar 1997 02:56:41 -0800 (PST) Date: Tue, 25 Mar 1997 02:56:41 -0800 (PST) Message-Id: <199703251056.CAA02575@silvia.HIP.Berkeley.EDU> To: ports@freebsd.org CC: current@freebsd.org Subject: emacs build failure on -current From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Are we supposed to add -lcompat the ld command line? Why does this work on 2.2? Satoshi ------- cc -DHAVE_CONFIG_H -I. -I../src -I/ccd/ports/editors/emacs/work/emacs-19.34/lib-sr c -I/ccd/ports/editors/emacs/work/emacs-19.34/lib-src/../src -O /ccd/ports/editors/ emacs/work/emacs-19.34/lib-src/fakemail.c -lutil -lc -o fakemail /ccd/ports/editors/emacs/work/emacs-19.34/lib-src/fakemail.c: In function `make_file_ preface': /ccd/ports/editors/emacs/work/emacs-19.34/lib-src/fakemail.c:367: warning: assignment makes pointer from integer without a cast /usr/tmp/cc0050831.o: Undefined symbol `_cuserid' referenced from text segment gmake[1]: *** [fakemail] Error 1 gmake[1]: Leaving directory `/ccd/ports/editors/emacs/work/emacs-19.34/lib-src' gmake: *** [lib-src] Error 2 *** Error code 2 Stop. From owner-freebsd-current Tue Mar 25 03:16:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA06154 for current-outgoing; Tue, 25 Mar 1997 03:16:15 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA06147 for ; Tue, 25 Mar 1997 03:16:08 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id LAA08687 for current@freebsd.org; Tue, 25 Mar 1997 11:14:13 GMT From: mika ruohotie Message-Id: <199703251114.LAA08687@shadows.aeon.net> Subject: hands up To: current@freebsd.org Date: Tue, 25 Mar 1997 13:14:13 +0200 (EET) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk well... i'm not sure if the dumpfs.c should include the patch wolfgang (sp?) introduced yesterday, still my cvsup doesnt give it to me, no biggie. today's cvsup (fresh) from cvsup.freebsd.org (i changed my supfiles, now only ebones and secure comes from cvsup.internat.freebsd.org ,apparently coz of my isp has good lines to states mainsite is lot faster, and while i'm on subject, how fast line do i need for making cvsup.fi.freebsd.org, funet.fi gave me the impression they are not interested in providing that) fresh 3.0-current as 11:00am GMT it hangs with: ===> libmytinfo cc -O2 -m486 -pipe -Wall -I/usr/src/lib/libmytinfo -c /usr/src/lib/libmytinfo/readcaps.c -o readcaps.o In file included from /usr/src/lib/libmytinfo/readcaps.c:13: /usr/src/lib/libmytinfo/defs.h:194: conflicting types for `sys_errlist' /usr/include/stdio.h:245: previous declaration of `sys_errlist' *** Error code 1 Stop. is my /usr/src hosed? (probably from changing cvsupsites on the fly?) hands up who thinks i should pick up everything again? well, since i did lift my hand and no one has veto over that, when you read this it's already done. mickey From owner-freebsd-current Tue Mar 25 03:55:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA07867 for current-outgoing; Tue, 25 Mar 1997 03:55:43 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA07859; Tue, 25 Mar 1997 03:55:32 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id WAA25361; Tue, 25 Mar 1997 22:52:23 +1100 Date: Tue, 25 Mar 1997 22:52:23 +1100 From: Bruce Evans Message-Id: <199703251152.WAA25361@godzilla.zeta.org.au> To: asami@vader.cs.berkeley.edu, wosch@freebsd.org Subject: Re: -current uudecode can't grok one of japanese/vfxdvi's distfiles Cc: current@freebsd.org, mita@jp.FreeBSD.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Looking at the uudecode source, this change seems to be the difference. > >=== >revision 1.5 >date: 1997/02/18 17:49:43; author: wosch; state: Exp; lines: +32 -1 >Better check for detecting header line. A header line must match >"begin [0-7]* *". Now `begin with, ' is not a header line. > >Do a boundary check for body characters. Characters less than 33 or >greater than 96 are out of range. If characters are out of range >uudecode print a error message and die. >=== > >Is this check really necessary? This file used to decode fine with >the old decoder. Besides, I can't figure out for the life of myself >which character it's barfing on. Someone send me a uuencoded gzipped file with spaces in it. I changed the spaces to backquotes and it uudecoded correctly. Bruce From owner-freebsd-current Tue Mar 25 04:15:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA08709 for current-outgoing; Tue, 25 Mar 1997 04:15:13 -0800 (PST) Received: from bsd.fs.bauing.th-darmstadt.de (bsd.fs.bauing.th-darmstadt.de [130.83.63.241]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA08699; Tue, 25 Mar 1997 04:15:02 -0800 (PST) Received: from campa.panke.de (anonymous213.ppp.cs.tu-berlin.de [130.149.17.213]) by bsd.fs.bauing.th-darmstadt.de (8.8.5/8.8.5) with SMTP id NAA04769; Tue, 25 Mar 1997 13:14:57 +0100 (MET) Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id MAA00909; Tue, 25 Mar 1997 12:54:03 +0100 Date: Tue, 25 Mar 1997 12:54:03 +0100 Message-Id: <199703251154.MAA00909@campa.panke.de> From: Wolfram Schneider To: asami@vader.cs.berkeley.edu (Satoshi Asami) Cc: wosch@freebsd.org, current@freebsd.org, mita@jp.FreeBSD.org Subject: -current uudecode can't grok one of japanese/vfxdvi's distfiles In-Reply-To: <199703250726.XAA01567@silvia.HIP.Berkeley.EDU> References: <199703250726.XAA01567@silvia.HIP.Berkeley.EDU> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Satoshi Asami writes: >uudecode: > input file: stdin > encoded file: xdvi-pl17+markpage+toc+printdvi+paper.patch.gz > character out of range: [33-96] >Do a boundary check for body characters. Characters less than 33 or >greater than 96 are out of range. If characters are out of range >uudecode print a error message and die. > >Is this check really necessary? Yes. All characters outside the range are garbage/bitrot and you get undefined results. >This file used to decode fine with >the old decoder. Besides, I can't figure out for the life of myself >which character it's barfing on. It use spaces (ASCII 32) in body. Spaces are bad because some mailers delete blank lines. Our uuencode never create spaces. See 'The UNIX-HATERS Handbook', page 82-83 I can add character 32 to the valid range for compatibility with old uuencode programs. -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-current Tue Mar 25 04:51:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA09944 for current-outgoing; Tue, 25 Mar 1997 04:51:23 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA09934 for ; Tue, 25 Mar 1997 04:51:19 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA13063; Tue, 25 Mar 1997 07:50:46 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 25 Mar 1997 07:50 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id GAA19287; Tue, 25 Mar 1997 06:58:10 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id HAA00253; Tue, 25 Mar 1997 07:03:43 -0500 (EST) Date: Tue, 25 Mar 1997 07:03:43 -0500 (EST) From: Thomas David Rivers Message-Id: <199703251203.HAA00253@lakes.water.net> To: ponds!freebsd.org!announce, ponds!time.cdrom.com!jkh Subject: Re: 2.2.1-RELEASE will be [re]appearing shortly.. Cc: ponds!freebsd.org!current Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > We found some issues with the 2940 driver and several other areas of > the system which really were on the "cusp" of being fixed, and it > seemed an unnecessary waste to make 2.2R users wait another 4 months > or so for 2.2.5 to come out before getting these fixes when we had > them available less than a week after release time (especially when > many of those fixes had already gone into an "older" release, > 2.1.7.1) and there were many emails demanding this, so... I would be happy to test out these aha2940 fixs before the "official" release if someone just points me to a GENERIC kernel. ... > > > Since the 2.2R CDROM has not yet been pressed, whatever I finally come > up with in these next few hours WILL be shipped as 2.2-RELEASE on > CDROM. As it says in the release notes, 2.2.1R is a full replacement > for 2.2.0R and once all this dust settles then everyone should just > pretend that the earlier release never happened. :-) Ummm, I'm a little slow on the up-take this morning. Does that mean that the up-coming (aka 2.2.1) release will be on the CDROM; or the older, now missing (aka 2.2.0) release will be on the CDROM? If the 2.2.1-RELEASE is on the CDROM, is there time remaining to test the aha2940 corrections? - Thanks - - Dave Rivers - From owner-freebsd-current Tue Mar 25 05:38:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA12329 for current-outgoing; Tue, 25 Mar 1997 05:38:24 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (ala-ca8-54.ix.netcom.com [207.93.141.182]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA12311; Tue, 25 Mar 1997 05:38:10 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id FAA00884; Tue, 25 Mar 1997 05:37:42 -0800 (PST) Date: Tue, 25 Mar 1997 05:37:42 -0800 (PST) Message-Id: <199703251337.FAA00884@silvia.HIP.Berkeley.EDU> To: wosch@apfel.de CC: wosch@freebsd.org, current@freebsd.org, mita@jp.FreeBSD.org In-reply-to: <199703251154.MAA00909@campa.panke.de> (message from Wolfram Schneider on Tue, 25 Mar 1997 12:54:03 +0100) Subject: Re: -current uudecode can't grok one of japanese/vfxdvi's distfiles From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * >Is this check really necessary? * * Yes. All characters outside the range are garbage/bitrot and * you get undefined results. (see (1) below) * >This file used to decode fine with * >the old decoder. Besides, I can't figure out for the life of myself * >which character it's barfing on. * * It use spaces (ASCII 32) in body. Aah, I see. Am I stupid or what, I was converting everything to space to check! ;( * Spaces are bad because * some mailers delete blank lines. Our uuencode never create * spaces. See 'The UNIX-HATERS Handbook', page 82-83 Ok, I agree that it's not a good idea for *uuencode* to use space (I've heard about that too), but if files with spaces decode correctly, I see no reason why we want to disable it in *uudecode*. ...(1) * I can add character 32 to the valid range for compatibility with old * uuencode programs. Yes, please! Satoshi From owner-freebsd-current Tue Mar 25 05:58:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA13181 for current-outgoing; Tue, 25 Mar 1997 05:58:47 -0800 (PST) Received: from mail.mcestate.com (vince@mail.MCESTATE.COM [207.211.200.50]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA13167 for ; Tue, 25 Mar 1997 05:58:40 -0800 (PST) Received: from localhost (vince@localhost) by mail.mcestate.com (8.8.5/8.8.5) with SMTP id FAA08025 for ; Tue, 25 Mar 1997 05:57:27 -0800 (PST) Date: Tue, 25 Mar 1997 05:57:26 -0800 (PST) From: Vincent Poy To: current@FreeBSD.ORG Subject: Anyone successing in a world build Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greetings everyone, Anyone out there with sources within the last 24 hours, been able to do a make world successfully as well as a new kernel? Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-current Tue Mar 25 08:14:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA20739 for current-outgoing; Tue, 25 Mar 1997 08:14:19 -0800 (PST) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA20727 for ; Tue, 25 Mar 1997 08:14:09 -0800 (PST) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.6.13/8.6.9) with ESMTP id IAA07455; Tue, 25 Mar 1997 08:14:08 -0800 Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.5/8.8.5) with SMTP id IAA14194; Tue, 25 Mar 1997 08:14:05 -0800 (PST) Date: Tue, 25 Mar 1997 08:14:05 -0800 (PST) From: Chris Timmons To: mika ruohotie cc: current@freebsd.org Subject: Re: hands up In-Reply-To: <199703251114.LAA08687@shadows.aeon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mika, > i'm not sure if the dumpfs.c should include the patch wolfgang (sp?) > introduced yesterday, still my cvsup doesnt give it to me, no biggie. CVSup can't give it to you until something is committed :) For now, your current make worlds will blow up at /usr/src/sbin/dumpfs/dumpfs.c... it's a feature. > subject, how fast line do i need for making cvsup.fi.freebsd.org, funet.fi > gave me the impression they are not interested in providing that) You could probably support a few clients with a 56kb line and still get some work done. Obviously most of the traffic load is heading outbound, which means if you are sharing a line with a big WWW server farm it might not be a good idea for you on such a slow line. > is my /usr/src hosed? (probably from changing cvsupsites on the fly?) Changing CVSup sites on the fly shouldn't be harmful to your source. Make sure you have a good supfile for current (eg. /usr/share/examples/cvsup/standard-supfile) -Chris From owner-freebsd-current Tue Mar 25 08:48:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA22544 for current-outgoing; Tue, 25 Mar 1997 08:48:25 -0800 (PST) Received: from hawk.pearson.udel.edu (hawk.pearson.udel.edu [128.175.64.150]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA22536 for ; Tue, 25 Mar 1997 08:48:22 -0800 (PST) Message-Id: <199703251648.IAA22536@freefall.freebsd.org> Received: (qmail 20197 invoked from network); 25 Mar 1997 16:48:27 -0000 Received: from localhost.udel.edu (HELO hawk.pearson.udel.edu) (127.0.0.1) by localhost.udel.edu with SMTP; 25 Mar 1997 16:48:27 -0000 To: freebsd-current@freebsd.org Subject: More Make World Madness Organization: Broken Toys Unlimited Reply-To: alexandr@hawk.pearson.udel.edu MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <20193.859308507.1@hawk.pearson.udel.edu> Date: Tue, 25 Mar 1997 11:48:27 -0500 From: Jerry Alexandratos Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, I ran into the same dumpfs problem that everyone else experienced. So, I applied the Joerg's patch. That compiled fine. 8) Unfortunately, it choked on ccd.c. 8( Here's the output: ===> lkm/ccd cc -O -I. -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/ccd/../../sys -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -DPSEUDO_LKM -c /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c In file included from /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c:116: /usr/src/lkm/ccd/../../sys/sys/vnode.h:465: warning: `struct vop_revoke_args' declared inside parameter list /usr/src/lkm/ccd/../../sys/sys/vnode.h:465: warning: its scope is only this definition or declaration, /usr/src/lkm/ccd/../../sys/sys/vnode.h:465: warning: which is probably not what you want. /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c: In function `ccdlookup': /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c:1383: too many arguments to function `VOP_UNLOCK' /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c:1393: too many arguments to function `VOP_UNLOCK' /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c:1400: too many arguments to function `VOP_UNLOCK' /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c:1410: too many arguments to function `VOP_UNLOCK' *** Error code 1 Any ideas what to look for? --Jerry 8) Jerry Alexandratos % "Nothing inhabits my (8 8) darkstar@strauss.udel.edu % thoughts, and oblivion (8 8) darkstar@canary.pearson.udel.edu % drives my desires." (8 From owner-freebsd-current Tue Mar 25 10:08:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA27907 for current-outgoing; Tue, 25 Mar 1997 10:08:10 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA27854 for ; Tue, 25 Mar 1997 10:07:59 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id SAA13910; Tue, 25 Mar 1997 18:04:48 GMT From: mika ruohotie Message-Id: <199703251804.SAA13910@shadows.aeon.net> Subject: Re: hands up In-Reply-To: from Chris Timmons at "Mar 25, 97 08:14:05 am" To: skynyrd@opus.cts.cwu.edu (Chris Timmons) Date: Tue, 25 Mar 1997 20:04:48 +0200 (EET) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > introduced yesterday, still my cvsup doesnt give it to me, no biggie. > CVSup can't give it to you until something is committed :) For now, your ah, ok, i thought it was committed. > current make worlds will blow up at /usr/src/sbin/dumpfs/dumpfs.c... it's no it wont, it's patched. =) > > is my /usr/src hosed? (probably from changing cvsupsites on the fly?) > Changing CVSup sites on the fly shouldn't be harmful to your source. Make ok. > sure you have a good supfile for current the file's "clean", i'll see what happens after i finish the resup... anyone alse got the lib thing that was blew up my latest world? > -Chris mickey From owner-freebsd-current Tue Mar 25 10:14:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA28297 for current-outgoing; Tue, 25 Mar 1997 10:14:23 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA28282; Tue, 25 Mar 1997 10:14:04 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16874(4)>; Tue, 25 Mar 1997 10:13:27 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177486>; Tue, 25 Mar 1997 10:13:10 -0800 To: asami@vader.cs.berkeley.edu (Satoshi Asami) cc: wosch@freebsd.org, current@freebsd.org, mita@jp.freebsd.org Subject: Re: -current uudecode can't grok one of japanese/vfxdvi's distfiles In-reply-to: Your message of "Mon, 24 Mar 97 23:26:17 PST." <199703250726.XAA01567@silvia.HIP.Berkeley.EDU> Date: Tue, 25 Mar 1997 10:13:01 PST From: Bill Fenner Message-Id: <97Mar25.101310pst.177486@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk asami@vader.cs.berkeley.edu (Satoshi Asami) wrote: >Do a boundary check for body characters. Characters less than 33 or >greater than 96 are out of range. This is not true. The original uuencode used characters in the range [32,95] . uuencode was modified to output 96 instead of 32 because 32 got munched on its way through too many mail gateways, but 32 is still a valid input character. Bill From owner-freebsd-current Tue Mar 25 10:14:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA28331 for current-outgoing; Tue, 25 Mar 1997 10:14:54 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA28322 for ; Tue, 25 Mar 1997 10:14:49 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) with SMTP id NAA06393; Tue, 25 Mar 1997 13:08:22 -0500 (EST) Date: Tue, 25 Mar 1997 13:08:22 -0500 (EST) From: Mark Mayo To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.ORG Subject: Re: Burning a 2.2.1R CDROM myself.. How? In-Reply-To: <921.859270807@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Mar 1997, Jordan K. Hubbard wrote: > > How do I go about arranging the data to burn a CD? I've noticed in the > > past that the CD directory structure isn't the same as the FTP site, so > > I'm assuming I can't just suck down the FTP distribution and burn it onto > > the CD. > > Actually, nowadays you can do exactly that. :-) The release bits are > the same in either case, as far as sysinstall is concerned, anyway. Cool. Any idea of how much space I will need to temporarily store the FTP site? Maybe I'll have to nuke my NT partition (which wouldn't be a bad thing) :-) Otherwise, I'm glad to see that you've sinked the FTP site and the CD - it will make it way easier to install freebsd over a local ftp connection to a cdrom in the future (I've had to do this many times in the past with machines that didn't have CDROMs). Thanx! -Mark ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ GCS/O d- s+ a-- C++ UB+++$ P+ L- E--- W++ N+ K- w++(---) O- M- !V PS+ PE Y++ PGP+ t !5 X+ R- tv b++ DI+ D++ G+ e+(*) h--- r++ y+(+++) ---------------------------------------------------------------------------- "Typically, I don't use JAVA -- I think that strong typing is for weak minds (and lazy compiler/interpreter writers)." -- Terry Lambert From owner-freebsd-current Tue Mar 25 11:40:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA03714 for current-outgoing; Tue, 25 Mar 1997 11:40:21 -0800 (PST) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA03704 for ; Tue, 25 Mar 1997 11:40:18 -0800 (PST) Received: from narnia.plutotech.com (localhost [127.0.0.1]) by narnia.plutotech.com (8.8.5/8.7.3) with ESMTP id MAA07835; Tue, 25 Mar 1997 12:40:05 -0700 (MST) Message-Id: <199703251940.MAA07835@narnia.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Andreas Klemm cc: "Justin T. Gibbs" , Kachun Lee , freebsd-current@freebsd.org Subject: Re: ahc crashes In-reply-to: Your message of "Thu, 20 Mar 1997 22:32:16 +0100." <19970320223216.48411@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Mar 1997 12:40:05 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Well, my machine still hangs and panics, if I use tagged command >queuing and try to make a dump to tape. My guess is that the source drive of your dump is returning QUEUE_FULL condition and that it wasn't being handled properly by the driver in the past. Can you see if this still happens with my latest changes? -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Mar 25 13:05:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA09200 for current-outgoing; Tue, 25 Mar 1997 13:05:28 -0800 (PST) Received: from critter.dk.tfs.com (phk.cybercity.dk [195.8.133.247]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA09191; Tue, 25 Mar 1997 13:05:16 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id VAA08147; Tue, 25 Mar 1997 21:21:10 +0100 (CET) To: gibbs@freebsd.org Cc: current@freebsd.org Subject: RELENG_2_2, ahc and Atlas II, YES!! Reply-to: phk@freebsd.org Date: Tue, 25 Mar 1997 21:21:09 +0100 Message-ID: <8145.859321269@critter> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I upgraded the box that's been giving me trouble to RELENG_2_2 as of this morning, danish time and it went straight through the operation that would until now 100% probability hang it. Thanks! Now for the question: Assume a machine with a 3940 in it. The bios will take bus A first, then bus B. FreeBSD does the same thing. Now add a 2940 to it. The bios goes 3940:A, 3940:B, 2940, FreeBSD goes 2940, 3940:A, 3940:B why ? I can understand that the order in the PCI slots matter and all that, but shouldn't we be able to do it in the same order the BIOS does it ? It's a semi-bad nuisance otherwise... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Mar 25 13:15:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA09886 for current-outgoing; Tue, 25 Mar 1997 13:15:10 -0800 (PST) Received: from pluto.plutotech.com (root@pluto.plutotech.com [206.168.67.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA09880; Tue, 25 Mar 1997 13:15:04 -0800 (PST) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id OAA05350; Tue, 25 Mar 1997 14:15:02 -0700 (MST) Message-Id: <199703252115.OAA05350@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: phk@freebsd.org cc: gibbs@freebsd.org, current@freebsd.org Subject: Re: RELENG_2_2, ahc and Atlas II, YES!! In-reply-to: Your message of "Tue, 25 Mar 1997 21:21:09 +0100." <8145.859321269@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Mar 1997 14:15:21 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Now for the question: You'd have to ask se. >-- >Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. >http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. >whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. >Future will arrive by its own means, progress not so. > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Mar 25 14:04:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA13587 for current-outgoing; Tue, 25 Mar 1997 14:04:05 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA13569 for ; Tue, 25 Mar 1997 14:04:00 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id JAA12965; Wed, 26 Mar 1997 09:02:50 +1100 Date: Wed, 26 Mar 1997 09:02:50 +1100 From: Bruce Evans Message-Id: <199703252202.JAA12965@godzilla.zeta.org.au> To: bde@zeta.org.au, rb@gid.co.uk Subject: Re: 2.2R (src 2.2 211): == dialing Cc: freebsd-current@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de, terry@lambert.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>This differs from when the system is shut down using reboot(8). reboot >>shuts things down by broadcasting signals of increasing severity >>{ SIGTERM, SIGKILL }. I don't know why init broadcasts SIGHUP... > >That I can tell you: interactive shells don't respond to SIGTERM. OTOH, >init shouldn't send SIGHUP to daemons (ie sessions with no controlling tty) >because they mostly take HUP to mean "reread your config". Init can't know enough about program (mis)behaviour to do this. The slattach daemon has a controlling tty, but shouldn't be sent a SIGHUP, since that tells it to redial. I think ignoring SIGTERM is braindamaged. Bruce From owner-freebsd-current Tue Mar 25 14:04:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA13622 for current-outgoing; Tue, 25 Mar 1997 14:04:29 -0800 (PST) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA13586 for ; Tue, 25 Mar 1997 14:04:05 -0800 (PST) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id VAA17448; Tue, 25 Mar 1997 21:46:21 GMT Date: Tue, 25 Mar 1997 21:49:03 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 25 Mar 1997 21:49:03 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199703250234.NAA06930@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Bruce Evans From: Bob Bishop Subject: Re: 2.2R (src 2.2 211): == dialing Cc: freebsd-current@freebsd.org, joerg_wunsch@uriah.heep.sax.de, terry@lambert.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 2:34 am -0000 25/3/97, Bruce Evans wrote: >This has nothing to do with POSIX signals... Oh, OK, I'll come out of my sulk now :-) >...or process groups. It is much >simpler. It is mostly documented in init(8): > >1. If someone hits Ctrl-Alt-Del, then a SIGINT is usually sent to init. >2. Init shuts down and reboots when it receives a SIGINT. >3. Init shuts things down by broadcasting signals of increasing severity > { SIGHUP, SIGTERM, SIGKILL }. >4. Some process like ppp do bad things when they receive a SIGHUP. > >This differs from when the system is shut down using reboot(8). reboot >shuts things down by broadcasting signals of increasing severity >{ SIGTERM, SIGKILL }. I don't know why init broadcasts SIGHUP... That I can tell you: interactive shells don't respond to SIGTERM. OTOH, init shouldn't send SIGHUP to daemons (ie sessions with no controlling tty) because they mostly take HUP to mean "reread your config". >...or why reboot doesn't just signal init. Good question; as it stands, it appears that reboot will always SIGKILL interactive shells (which ignore TERM); under unfavourable circumstances this could eg leave modems in strange states. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Tue Mar 25 15:05:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA18230 for current-outgoing; Tue, 25 Mar 1997 15:05:05 -0800 (PST) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA18203 for ; Tue, 25 Mar 1997 15:05:00 -0800 (PST) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id XAA17980; Tue, 25 Mar 1997 23:01:08 GMT Date: Tue, 25 Mar 1997 23:00:54 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 25 Mar 1997 23:00:54 GMT X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Bruce Evans From: Bob Bishop Subject: Re: 2.2R (src 2.2 211): == dialing Cc: freebsd-current@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de, terry@lambert.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk At 10:02 pm -0000 25/3/97, Bruce Evans wrote: >>>This differs from when the system is shut down using reboot(8). reboot >>>shuts things down by broadcasting signals of increasing severity >>>{ SIGTERM, SIGKILL }. I don't know why init broadcasts SIGHUP... >> >>That I can tell you: interactive shells don't respond to SIGTERM. OTOH, >>init shouldn't send SIGHUP to daemons (ie sessions with no controlling tty) >>because they mostly take HUP to mean "reread your config". > >Init can't know enough about program (mis)behaviour to do this. If that is true, Terry is right and something is broken. >The slattach daemon has a controlling tty... Only until it calls daemon() immediately after cracking its args. >... but shouldn't be sent a SIGHUP, since that >tells it to redial. Which is (close to) where we came in. >I think ignoring SIGTERM is braindamaged. AFAIK, interactive shells have always done so (since V7 at least). Bear in mind that SIGHUP originated historically as a (hardware) indication that carrier had dropped because the caller had Hung UP, whereas TERM has always been a pure software signal. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Tue Mar 25 15:05:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA18283 for current-outgoing; Tue, 25 Mar 1997 15:05:28 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA18258 for ; Tue, 25 Mar 1997 15:05:16 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA16609; Wed, 26 Mar 1997 00:05:07 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA07112; Tue, 25 Mar 1997 23:25:08 +0100 (MET) Message-ID: <19970325232508.WZ22010@uriah.heep.sax.de> Date: Tue, 25 Mar 1997 23:25:08 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: zellion@cyberwind.com (Jeffery T. White), jkh@time.cdrom.com (Jordan K. Hubbard) Subject: Re: named References: <199703250315.TAA00502@cyberwind.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703250315.TAA00502@cyberwind.com>; from Jeffery T. White on Mar 24, 1997 19:23:35 -0800 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jeffery T. White wrote: > > Hmm. What else than running make-localhost did you need in order to > > start a caching-only named? The default named.boot file does exactly > > this, and nothing more. > Ahh, yes you are right the sample files do just that, they just don't tell > you in the comments. That's right. > The man page leads one to believe that they need to setup a secondary > or primary server. > "Yikes this is serious" :-) Yep, setting up a primary _is_ serious (except the primary for 127.in-addr.arpa, of course :). You shouldn't do it unless you know what the various bits mean, at least not if you intend to connect it to the Internet. > The install idea would > be really cool. I'll see whether i can come up with a suggestion to Jordan. > One thing I added was a cron entry to fetch a new named.root from NIC every > so often, if you were going to do a sysinstall that might also be something > to think about. If not it still might be a useful commented out line... Hmmm. I'm not sure whether i like this as a general rule. For one, we don't setup any crontab entries except for /etc/*ly (and newsyslog(8) and atrun(8)) by default at all. Also, sites might be dialup-sites, or simply might not wish this service at all. The root-server files usually change very little only, so i don't think this justifies the hassles. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Mar 25 15:25:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA20099 for current-outgoing; Tue, 25 Mar 1997 15:25:41 -0800 (PST) Received: from mail.vlsi.fi (iQ0OHLvmWHlFNajqxCn3ZCKq9cv4hCkl@mail.vlsi.fi [195.74.10.147]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA20033; Tue, 25 Mar 1997 15:25:23 -0800 (PST) Received: (from smap@localhost) by mail.vlsi.fi (8.7.6/8.7.3) id BAA29205; Wed, 26 Mar 1997 01:25:03 +0200 (EET) Received: from vlsi1.vlsi.fi(193.64.2.2) by mail.vlsi.fi via smap (V1.3) id sma029199; Wed Mar 26 01:24:55 1997 Received: from layout.vlsi.fi by vlsi1.vlsi.fi with ESMTP (1.37.109.16/16.2) id AA158042290; Wed, 26 Mar 1997 01:24:50 +0200 Received: by layout.vlsi.fi (1.37.109.15/16.2) id AA257592289; Wed, 26 Mar 1997 01:24:49 +0200 Date: Wed, 26 Mar 1997 01:24:49 +0200 Message-Id: <199703252324.AA257592289@layout.vlsi.fi> From: Ville Eerola To: Burton Sampley Cc: questions@FreeBSD.org, current@FreeBSD.org Subject: Re: Fetchmail nolonger working In-Reply-To: References: X-Mailer: VM Version 5.93 (beta) under GNU Emacs 19.29.6 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Burton Sampley writes: > The error message I get when I run fetchmail -av is SMTP connection > failed. I have two email accounts (on different servers), so I have a > .fetchmailrc file which has never been modified. > > Any ideas? Well, do you have sendmail running? Normally fetchmail uses SMTP connection to the localhost to deliver the messages it downloads from the mail sever. Thus, you need to have a MTA listening to port 25 on the host runnig fetchmail, or alternatively you need to configure fetchmail to use a local MDA directly. Other than that, I can't say very much without seeing the messages from the failed fetchmail run. Regards, Ville -- Ville.Eerola@vlsi.fi VLSI Solution Oy Tel:+358 3 3165579 Hermiankatu 6-8 C Fax:+358 3 3165220 FIN-33720 Tampere, Finland From owner-freebsd-current Tue Mar 25 15:40:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA21188 for current-outgoing; Tue, 25 Mar 1997 15:40:26 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA21181 for ; Tue, 25 Mar 1997 15:40:23 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id KAA16629; Wed, 26 Mar 1997 10:33:32 +1100 Date: Wed, 26 Mar 1997 10:33:32 +1100 From: Bruce Evans Message-Id: <199703252333.KAA16629@godzilla.zeta.org.au> To: bde@zeta.org.au, rb@gid.co.uk Subject: Re: 2.2R (src 2.2 211): == dialing Cc: freebsd-current@FreeBSD.ORG, joerg_wunsch@uriah.heep.sax.de, terry@lambert.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>The slattach daemon has a controlling tty... > >Only until it calls daemon() immediately after cracking its args. No. It acquires a controlling tty a few lines after it becomes a daemon, at least in the redial case (I think the !redial case is still broken - it does a null redial instead of aborting like the documentation for the -l option says it does). Bruce From owner-freebsd-current Tue Mar 25 15:40:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA21243 for current-outgoing; Tue, 25 Mar 1997 15:40:55 -0800 (PST) Received: from proxy1.ba.best.com (root@proxy1.ba.best.com [206.184.139.12]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA21237; Tue, 25 Mar 1997 15:40:52 -0800 (PST) Received: from bsampley.vip.best.com (bsampley.vip.best.com [206.184.160.196]) by proxy1.ba.best.com (8.8.5/8.8.3) with SMTP id PAA27432; Tue, 25 Mar 1997 15:36:17 -0800 (PST) Date: Tue, 25 Mar 1997 15:35:20 -0800 (PST) From: Burton Sampley To: Ville Eerola cc: questions@FreeBSD.org, current@FreeBSD.org Subject: Re: Fetchmail nolonger working In-Reply-To: <199703252324.AA257592289@layout.vlsi.fi> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Thanks for the help. Yes I do have senmail running. I just solved this problem. I looked in the /etc/sysconfig file and noticed that routed was NOT running. I changed the line from router="NO" to router=routed and rebooted the machine. Surpirse, now fetchmail works. I keep seeing many, many postings on both -current and -questions that routed _IS NOT NEEDED_ for anything. This truely is a case the proves otherwise. The only thing that I changed was the router line in sysconfig and now fetchmail works. (I know I'll probably get flamed for this, but Oh, well) On Wed, 26 Mar 1997, Ville Eerola wrote: > Well, do you have sendmail running? Normally fetchmail uses SMTP > connection to the localhost to deliver the messages it downloads from > the mail sever. Thus, you need to have a MTA listening to port 25 on > the host runnig fetchmail, or alternatively you need to configure > fetchmail to use a local MDA directly. > > Other than that, I can't say very much without seeing the messages > from the failed fetchmail run. > > > Regards, Ville > > -- > Ville.Eerola@vlsi.fi VLSI Solution Oy > Tel:+358 3 3165579 Hermiankatu 6-8 C > Fax:+358 3 3165220 FIN-33720 Tampere, Finland > > --- Brought to you by a 100% Micro$oft free system. You too can disinfect your system at http://www.freebsd.org E-Mail: burton@bsampley.vip.best.com Alternate E-Mail: bsampley@haywire.csuhayward.edu Home Page: http://www.best.com/~bsampley (permanently under construction) From owner-freebsd-current Tue Mar 25 15:42:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA21407 for current-outgoing; Tue, 25 Mar 1997 15:42:54 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA21392 for ; Tue, 25 Mar 1997 15:42:50 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA26225; Tue, 25 Mar 1997 16:28:34 -0700 From: Terry Lambert Message-Id: <199703252328.QAA26225@phaeton.artisoft.com> Subject: Re: 2.2R (src 2.2 211): == dialing To: rb@gid.co.uk (Bob Bishop) Date: Tue, 25 Mar 1997 16:28:34 -0700 (MST) Cc: bde@zeta.org.au, freebsd-current@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de, terry@lambert.org In-Reply-To: from "Bob Bishop" at Mar 25, 97 11:00:54 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >The slattach daemon has a controlling tty... > > Only until it calls daemon() immediately after cracking its args. > > >... but shouldn't be sent a SIGHUP, since that > >tells it to redial. > > Which is (close to) where we came in. No, this is far from it. The controlling tty for the slattach is a result of the tty for the connection being the first open after the process has orphanned itself from a controlling tty. I think the problem here is that the session and process group are being treated incorrectly. It should be possible to distinguish a process which has made a tty it's controlling tty in order to get device events as signals, and a process which has a controlling tty because it is interactive. This cuts to the heart of the session vs. process group leader distinction, and the idea of whether a process which is the sole process on a tty must be considered the group leader. If you think that it should, then you are arguing with me for the SVR4 behaviour of the process group leader propagating SIGHUP to its children. This is a necessary condition of this treatment of group. > >I think ignoring SIGTERM is braindamaged. > > AFAIK, interactive shells have always done so (since V7 at least). > Bear in mind that SIGHUP originated historically as a (hardware) > indication that carrier had dropped because the caller had Hung UP, > whereas TERM has always been a pure software signal. SIGHUP is actually on-to-off DCD transition notification for a process for which the tty is the controlling tty and for which the tty modes specify -CLOCAL (the connection is non-local and therefore modem control signals should be obeyed). The error is in not distinguishing a sole process on a tty from a group leader by virtue of whether or not it is a tty it has claimed, and whether the tty is the tty which the process originally had before it was daemonized. Daemons, of course, don't get SIGHUP from init. The SIGHUP in this case should originate not because the signal was explicitly sent, but because the tty was revoked, and processes which are group leaders get SIGHUP when a tty which is a controlling tty for the process is revoked. Probably, the sltattch should not be being considered a group leader. Note that this exempts processes without a controlling tty (generally, any process which uses a SIGHUP to signal a reset -- like init, named, and so on) from getting a SIGHUP. If the SIGHUP result from the revoke (the process is a group leader) or from a group resend (the group send in the kernel should cause all children of the leader to be sent a SIGHUP before they are orphaned, and then when they are orphaned, it will be processed), then the daemons will never get it. After the delay, then sending the SIGINT to remaining processes is the correct thing to do, regardles of their group membership; the same goes for SIGKILL. I'm not sure whether SIGTERM should ever be sent, actually... I guess it can't hurt, considering it's default is to terminate the process. ...Though I rather suspect that more programs have SIGINT handlers than SIGTERM handlers, so sending SIGTERM with a default of terminal process will actually *prevent* these programs from gracefully saving state and shutting down. 8-(. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Mar 25 16:52:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA27365 for current-outgoing; Tue, 25 Mar 1997 16:52:47 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA27358 for ; Tue, 25 Mar 1997 16:52:45 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA26494; Tue, 25 Mar 1997 17:38:48 -0700 From: Terry Lambert Message-Id: <199703260038.RAA26494@phaeton.artisoft.com> Subject: Re: 2.2R (src 2.2 211): == dialing To: bde@zeta.org.au (Bruce Evans) Date: Tue, 25 Mar 1997 17:38:48 -0700 (MST) Cc: bde@zeta.org.au, rb@gid.co.uk, freebsd-current@FreeBSD.ORG, joerg_wunsch@uriah.heep.sax.de, terry@lambert.org In-Reply-To: <199703252333.KAA16629@godzilla.zeta.org.au> from "Bruce Evans" at Mar 26, 97 10:33:32 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >>The slattach daemon has a controlling tty... > > > >Only until it calls daemon() immediately after cracking its args. > > No. It acquires a controlling tty a few lines after it becomes a > daemon, at least in the redial case (I think the !redial case is > still broken - it does a null redial instead of aborting like the > documentation for the -l option says it does). This means it should get a SIGHUP on on-to-off DCD transistion if -CLOCAL is set. Does it mean it should get SIGHUP when the tty is revoked? ...I don't think so, actually. There is a distingtion to be drawn between acquiring a controlling tty, and becoming a process group leader. Part of the problem here is how daemon(3) is supposed to work. It does not say that the process becomes a group or session leader, actually (this may just be a deficit in the man page; if so, it is arguable that the process should become a deamon by performing the explicit acts to become a daemon instead of making the library call with the process/session leadership side effects). You *could* argue, on this basis, that slattach is doing the wrong thing, and that's what's leaving it open to getting a SIGHUP when it should not be getting on. On the other hand, I believe other programs which call daemon(3) and do not reacquire a controlling tty also get the SIGHUP on shutdown, so no matter what, there is something rotten in Denmark... Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Mar 25 17:08:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA28522 for current-outgoing; Tue, 25 Mar 1997 17:08:49 -0800 (PST) Received: from nexgen.hiwaay.net (max20-69.HiWAAY.net [208.147.153.69]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA28517 for ; Tue, 25 Mar 1997 17:08:45 -0800 (PST) Received: from nexgen (localhost [127.0.0.1]) by nexgen.hiwaay.net (8.8.5/8.8.4) with ESMTP id TAA20506; Mon, 24 Mar 1997 19:56:10 -0600 (CST) Message-Id: <199703250156.TAA20506@nexgen.hiwaay.net> X-Mailer: exmh version 1.6.9 8/22/96 To: cracauer@wavehh.hanse.de cc: jkh@time.cdrom.COM, freebsd-current@freebsd.org From: dkelly@hiwaay.net Subject: Re: CVS repository pushed off the FreeBSD CD distribution... In-reply-to: Message from cracauer@wavehh.hanse.de (Martin Cracauer) of "Mon, 24 Mar 1997 14:28:55 +0100." <9703241328.AA04812@wavehh.hanse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Mar 1997 19:56:10 -0600 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I always felt that a base CTM delta would be very valuable for a CD, > too. After all, CTM is for use poor people who can't ftp a 70 MB > file. Agreed. But wouldn't it be even simpler if the -RELEASE was sync'ed to a CTM delta (might be already, would be nice if there was a release marker in the CTM filename), and then all we'd need are .ctm_status files in the appropriate places. Even cheaper than a 70M base delta. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-current Tue Mar 25 17:21:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA29431 for current-outgoing; Tue, 25 Mar 1997 17:21:32 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA29425 for ; Tue, 25 Mar 1997 17:21:25 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id CAA18885 for freebsd-current@FreeBSD.ORG; Wed, 26 Mar 1997 02:21:15 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id BAA08361; Wed, 26 Mar 1997 01:59:09 +0100 (MET) Message-ID: <19970326015908.BH63960@uriah.heep.sax.de> Date: Wed, 26 Mar 1997 01:59:08 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Subject: Re: 2.2R (src 2.2 211): == dialing References: <199703252328.QAA26225@phaeton.artisoft.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703252328.QAA26225@phaeton.artisoft.com>; from Terry Lambert on Mar 25, 1997 16:28:34 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > No, this is far from it. The controlling tty for the slattach is > a result of the tty for the connection being the first open after > the process has orphanned itself from a controlling tty. Häh?!? Terry, you're in the wrong movie here. In BSD, opening a tty does _by no means_ make it a controlling tty. I thought you've read Vahalia a little better... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Mar 25 18:29:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA06118 for current-outgoing; Tue, 25 Mar 1997 18:29:52 -0800 (PST) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA06028 for ; Tue, 25 Mar 1997 18:29:06 -0800 (PST) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id UAA02823; Tue, 25 Mar 1997 20:28:04 -0600 (CST) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <199703250156.TAA20506@nexgen.hiwaay.net> References: Message from cracauer@wavehh.hanse.de (Martin Cracauer) of "Mon, 24 Mar 1997 14:28:55 +0100." <9703241328.AA04812@wavehh.hanse.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 25 Mar 1997 20:23:13 -0600 To: dkelly@hiwaay.net From: Richard Wackerbarth Subject: Re: CVS repository pushed off the FreeBSD CD distribution... Cc: cracauer@wavehh.hanse.de, jkh@time.cdrom.COM, freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 7:56 PM -0600 3/24/97, dkelly@hiwaay.net wrote: > >> I always felt that a base CTM delta would be very valuable for a CD, >> too. After all, CTM is for use poor people who can't ftp a 70 MB >> file. > >Agreed. But wouldn't it be even simpler if the -RELEASE was sync'ed to a >CTM delta (might be already, would be nice if there was a release marker in >the CTM filename), and then all we'd need are .ctm_status files in the >appropriate places. Even cheaper than a 70M base delta. As the new "de facto" CTM-meister, let me comment. 1) I have already begun the process is ridding the world of redundant base distributions by placing the src-RELEASE tarballs in the ctm delta chain. The only missing point is getting the .ctm_status file included as a part of the distribution. I am still lobbying for that. However, there are technical reasons that are slowing the process. 2) For FTP, getting all the "src" directory of the distribution is only marginally more difficult than getting a base delta file. Since it saves 30Meg on each mirror site as well as the CD, I consider it a good change. I will still generate periodic base deltas for those who do not otherwise have direct access to a recent baseline. On a CD, I would prefer to see an a actual tree rather than the compressed source. If we can ever get an overlay system working reliabily, we would be able to simply note the changes. If you are following a particular release family, a major portion of the tree remains unchanged. 3) In recognition of the multiple possibilities for an original source, I have changed the suffix designation to be a bit more descriptive. For example, I use 100xEmpty.gz rather than 100A.gz to represent the 30Meg initialization starting from an empty src directory. 4) CVS represents a unique situation because the tree is extremely unstable. Most, if not all, of last weeks files therein are modified. As a result, static storage (like a CD) is quickly unusable. However, a compressed form of a snapshot of the tree does provide an efficient method to create a starting point upon which updates can be applied. From owner-freebsd-current Tue Mar 25 18:46:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA07282 for current-outgoing; Tue, 25 Mar 1997 18:46:27 -0800 (PST) Received: from nexgen.hiwaay.net (max20-69.HiWAAY.net [208.147.153.69]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA07257 for ; Tue, 25 Mar 1997 18:46:12 -0800 (PST) Received: from nexgen (localhost [127.0.0.1]) by nexgen.hiwaay.net (8.8.5/8.8.4) with ESMTP id UAA25308; Tue, 25 Mar 1997 20:45:34 -0600 (CST) Message-Id: <199703260245.UAA25308@nexgen.hiwaay.net> X-Mailer: exmh version 1.6.9 8/22/96 To: Richard Wackerbarth cc: freebsd-current@freebsd.org From: dkelly@hiwaay.net Subject: Re: CVS repository pushed off the FreeBSD CD distribution... In-reply-to: Message from Richard Wackerbarth of "Tue, 25 Mar 1997 20:23:13 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Mar 1997 20:45:33 -0600 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk rkw@Dataplex.Net said: > As the new "de facto" CTM-meister, let me comment. [snip] > 3) In recognition of the multiple possibilities for an original source, > I have changed the suffix designation to be a bit more descriptive. > For example, I use 100xEmpty.gz rather than 100A.gz to represent the > 30Meg initialization starting from an empty src directory. ...which brings up another question. I've occasionally wondered how to generate one of these myself, wanting to roll my accumulated CTM's into an *Empty* or *A*. Finally settled on exploding my CTM's into a brand new directory, then tar'ing that and deleting the accumulated CTM's. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-current Tue Mar 25 18:48:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA07404 for current-outgoing; Tue, 25 Mar 1997 18:48:24 -0800 (PST) Received: from hobbes.saturn-tech.com (drussell@[207.229.19.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA07320 for ; Tue, 25 Mar 1997 18:46:59 -0800 (PST) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id TAA22296; Tue, 25 Mar 1997 19:46:58 -0700 (MST) Date: Tue, 25 Mar 1997 19:46:57 -0700 (MST) From: Doug Russell To: freebsd-current@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: SIGTERMs killing X In-Reply-To: <199703252328.QAA26225@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Mar 1997, Terry Lambert wrote: > I'm not sure whether SIGTERM should ever be sent, actually... I guess > it can't hurt, considering it's default is to terminate the process. All this talk of signals reminds me of a (totally) unrelated problem one of my machines seems to be having lately..... My main workstation, which usually runs X all the time, has exited on a sig 6 from X a couple times in the last few days for no apparent reason. Mar 24 12:22:23 586quick166 /kernel: pid 218 (XF86_SVGA), uid 0: exited on signal 6 Mar 25 11:27:22 586quick166 /kernel: pid 7136 (XF86_SVGA), uid 0: exited on signal 6 I can't for the life of me determine why it would have got an ABORT signal.... Where would that be coming from? The machine is just sitting there idle (AFAIK, anyway... :)) and when I get home from work, for example, it's no longer running X. Anyone else had any kind of similar problem, or any idea how I can figure out where these are coming from?? It is rather annoying. :) Later...... From owner-freebsd-current Tue Mar 25 19:12:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA09411 for current-outgoing; Tue, 25 Mar 1997 19:12:29 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA09401 for ; Tue, 25 Mar 1997 19:12:25 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id TAA01499; Tue, 25 Mar 1997 19:10:54 -0800 (PST) To: Richard Wackerbarth cc: dkelly@hiwaay.net, cracauer@wavehh.hanse.de, freebsd-current@freebsd.org Subject: Re: CVS repository pushed off the FreeBSD CD distribution... In-reply-to: Your message of "Tue, 25 Mar 1997 20:23:13 CST." Date: Tue, 25 Mar 1997 19:10:53 -0800 Message-ID: <1495.859345853@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On a CD, I would prefer to see an a actual tree rather than the compressed > source. If we can ever get an overlay system working reliabily, we would That's now done in the 2.2[.1] CD. I brought /usr/src back on the 2nd CDROM. Jordan From owner-freebsd-current Tue Mar 25 20:03:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA12051 for current-outgoing; Tue, 25 Mar 1997 20:03:14 -0800 (PST) Received: from cyberwind.com (cyberwind.com [199.4.109.220]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA12031; Tue, 25 Mar 1997 20:03:07 -0800 (PST) Received: from zellion.cyberwind.com (zellion.cyberwind.com [199.4.109.223]) by cyberwind.com (8.7.5/8.7.3) with ESMTP id UAA02352; Tue, 25 Mar 1997 20:03:51 -0800 (PST) Message-Id: <199703260403.UAA02352@cyberwind.com> From: "Jeffery T. White" To: "mike allison" Cc: , Subject: Re: named Date: Tue, 25 Mar 1997 20:11:24 -0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ---------- > From: mike allison > To: Jeffery T. White > Cc: current@freebsd.org; FreeBSD-chat@freebsd.org > Subject: Re: named > Date: Tuesday, March 25, 1997 9:20 PM > > Jeffery, > I don't know where you'd submit it for FreeBSD, but I'd like a blurb on > this with the setup code/script to publish in Free Systems Journal. > Well I'm no expert and surely no writer however I do have: a) The time.. b) The small user/network perspective.. c) The research fresh in mind.. d) A FreeBSD only sort of few.. [is this a plus or not? :-)] I'll write up the steps from resolver through sysconfig and the named files in a language that IMHO would reach the user interested in the "simple" setup and post it here by Sunday. That'll let this group see what I'm saying since they're more knowledgeable than me in this area and would catch any errors. We can then either revise or whatever from there. | Jeffery T. White | email: zellion@cyberwind.com | | Cyberwind, The wind knows... | http://www.cyberwind.com From owner-freebsd-current Tue Mar 25 20:53:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA14536 for current-outgoing; Tue, 25 Mar 1997 20:53:14 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA14526 for ; Tue, 25 Mar 1997 20:53:11 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id VAA27026; Tue, 25 Mar 1997 21:39:27 -0700 From: Terry Lambert Message-Id: <199703260439.VAA27026@phaeton.artisoft.com> Subject: Re: 2.2R (src 2.2 211): == dialing To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 25 Mar 1997 21:39:27 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19970326015908.BH63960@uriah.heep.sax.de> from "J Wunsch" at Mar 26, 97 01:59:08 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > No, this is far from it. The controlling tty for the slattach is > > a result of the tty for the connection being the first open after > > the process has orphanned itself from a controlling tty. > > H=E4h?!? > > Terry, you're in the wrong movie here. In BSD, opening a tty does > _by no means_ make it a controlling tty. I thought you've read > Vahalia a little better... s/the first open/attached as such/ Sorry, I've been typing on overdrive, and when I do that, my auto-correction gives out. 8-(. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Mar 25 21:04:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA15124 for current-outgoing; Tue, 25 Mar 1997 21:04:50 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA15118 for ; Tue, 25 Mar 1997 21:04:47 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id VAA27126; Tue, 25 Mar 1997 21:50:50 -0700 From: Terry Lambert Message-Id: <199703260450.VAA27126@phaeton.artisoft.com> Subject: Re: SIGTERMs killing X To: drussell@saturn-tech.com (Doug Russell) Date: Tue, 25 Mar 1997 21:50:50 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: from "Doug Russell" at Mar 25, 97 07:46:57 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > All this talk of signals reminds me of a (totally) unrelated problem one > of my machines seems to be having lately..... My main workstation, which > usually runs X all the time, has exited on a sig 6 from X a couple times > in the last few days for no apparent reason. > > Mar 24 12:22:23 586quick166 /kernel: pid 218 (XF86_SVGA), uid 0: exited on signal 6 > Mar 25 11:27:22 586quick166 /kernel: pid 7136 (XF86_SVGA), uid 0: exited on signal 6 > > I can't for the life of me determine why it would have got an ABORT > signal.... Where would that be coming from? The machine is just sitting > there idle (AFAIK, anyway... :)) and when I get home from work, for > example, it's no longer running X. It is because FreeBSD is overcommiting memory in it's VM system. I am sorry for you that you got this error... I am glad you got this error, because you are a real-world example of a need for a tunable which I have been lobbying for for four years. Now I have a sample case, and I am happy because I can flagellate the powers that be every time the topic comes up in the future. 8-). What it means is that your VM space for your process has been destroyed (you can see this by looking in /sys/kern/kern_exec.c). This can happen when you have run out of virtual memory, and you get a write fault on a copy-on-write page. When this happens, the page is supposed to be copied to another page and the process map adjusted to cause the write to accutually occur in a copy of the page instead of the actual page. This can similarly occur when you have a MAP_PRIVATE mmap()'ed file or a shared memory segment mapped and on which you have changed page protections (by default FreeBSD does not support mapping shared memory copy on write). If it can't get a page, then the fault can not be serviced, and your process can not continue running. To rememdy this, you should increas the amount of swap space you have. Note: it is possible that in the move to 3.0, the VM system was damaged such that it could not reclaim otherwise reclaimable pages (ie: a kernel memory leak). If you have a large amount of swap, you should consider determining if a leak is ocurreing, and report the problem to David Greenman or John Dyson, if you find that there is a leak, since adding swap in this case will only cause a longer delay before the onset of the problem. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Mar 25 21:27:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA16275 for current-outgoing; Tue, 25 Mar 1997 21:27:32 -0800 (PST) Received: from 586quick166.saturn-tech.com ([207.229.19.32]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA16267 for ; Tue, 25 Mar 1997 21:27:29 -0800 (PST) Received: from localhost (drussell@localhost) by 586quick166.saturn-tech.com (8.8.4/8.8.4) with SMTP id WAA00684; Tue, 25 Mar 1997 22:26:24 GMT X-Authentication-Warning: 586quick166.saturn-tech.com: drussell owned process doing -bs Date: Tue, 25 Mar 1997 22:26:24 +0000 () From: Doug Russell To: Terry Lambert cc: freebsd-current@freebsd.org Subject: Re: SIGTERMs killing X In-Reply-To: <199703260450.VAA27126@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Mar 1997, Terry Lambert wrote: > > I can't for the life of me determine why it would have got an ABORT > > signal.... Where would that be coming from? The machine is just sitting > > there idle (AFAIK, anyway... :)) and when I get home from work, for > > example, it's no longer running X. > > It is because FreeBSD is overcommiting memory in it's VM system. > > I am sorry for you that you got this error... > > I am glad you got this error, because you are a real-world example > of a need for a tunable which I have been lobbying for for four years. > Now I have a sample case, and I am happy because I can flagellate > the powers that be every time the topic comes up in the future. 8-). :) > What it means is that your VM space for your process has been > destroyed (you can see this by looking in /sys/kern/kern_exec.c). ... > To rememdy this, you should increas the amount of swap space you have. Ok, sounds reasonable. The only question is, how on earth does it need that much swap space? I currently have 32 megs of RAM, and single 64 meg swap allocated. The only things that were running on the machine when the thing died were XF86_SVGA, Fvwm, Xearth on the root window, and probably a screensaver from the xscreensaver collection. How could that eat up that much VM? Is that actually possible, or is there something else at work here? What is the best guess, add a whack more swap and see if it persists? Turn off xscreensaver? (It is set to randomly select one every once in a while... maybe one of them is acting up and when it gets called, it kills the system.) What do I know? :) Later...... From owner-freebsd-current Tue Mar 25 21:32:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA16615 for current-outgoing; Tue, 25 Mar 1997 21:32:28 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA16603 for ; Tue, 25 Mar 1997 21:32:23 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id GAA07165 for ; Wed, 26 Mar 1997 06:32:14 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id GAA19858 for freebsd-current@FreeBSD.ORG; Wed, 26 Mar 1997 06:31:57 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id BAA29311; Wed, 26 Mar 1997 01:12:39 +0100 (CET) Message-ID: <19970326011239.16775@keltia.freenix.fr> Date: Wed, 26 Mar 1997 01:12:39 +0100 From: Ollivier Robert To: freebsd-current@freebsd.org Subject: Re: Burning a 2.2.1R CDROM myself.. How? References: <921.859270807@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.65,1-4,10,14-18 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3153 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Mark Mayo: > Otherwise, I'm glad to see that you've sinked the FTP site and the CD - it > will make it way easier to install freebsd over a local ftp connection to > a cdrom in the future (I've had to do this many times in the past with > machines that didn't have CDROMs). Thanx! Don't forget to take the cdrom.inf located somewhere inside release/ and stick it on the CD... Extracted from release/Makefile: echo "CD_VERSION = ${BUILDNAME}" > ${FD}/cdrom.inf -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #41: Sun Mar 23 23:01:22 CET 1997 From owner-freebsd-current Tue Mar 25 21:34:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA16891 for current-outgoing; Tue, 25 Mar 1997 21:34:56 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA16877 for ; Tue, 25 Mar 1997 21:34:53 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id WAA27235; Tue, 25 Mar 1997 22:21:01 -0700 From: Terry Lambert Message-Id: <199703260521.WAA27235@phaeton.artisoft.com> Subject: Re: SIGTERMs killing X To: drussell@saturn-tech.com (Doug Russell) Date: Tue, 25 Mar 1997 22:21:01 -0700 (MST) Cc: terry@lambert.org, freebsd-current@freebsd.org In-Reply-To: from "Doug Russell" at Mar 25, 97 10:26:24 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > What it means is that your VM space for your process has been > > destroyed (you can see this by looking in /sys/kern/kern_exec.c). > ... > > To rememdy this, you should increas the amount of swap space you have. > > Ok, sounds reasonable. The only question is, how on earth does it need > that much swap space? I currently have 32 megs of RAM, and single 64 meg > swap allocated. The only things that were running on the machine when the > thing died were XF86_SVGA, Fvwm, Xearth on the root window, and probably a > screensaver from the xscreensaver collection. You should watch the size of your X server. Most likely, it, or Netscape's use of bitmaps on it, or Xerth's use of bitmaps on it, are the cause of a memory leak. You should consider using an X server that has been linked against Poul-Henning Kamp's new malloc, which is capable of sbrk'ing back to the system. > How could that eat up that much VM? Is that actually possible, or is > there something else at work here? What is the best guess, add a whack > more swap and see if it persists? Turn off xscreensaver? (It is set to > randomly select one every once in a while... maybe one of them is acting > up and when it gets called, it kills the system.) What do I know? :) Watch the size of your XServer. See which of the programs you are runnng cause it to grow. Potentially, update your X server to newer code (you may have to update FreeBSD to do this) or quit running the problem application. I syspect that if you are not running ahuge number of programs with huge memory requirements, that increasing the swap will only make it take longer to have the problem. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Mar 25 21:41:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA17367 for current-outgoing; Tue, 25 Mar 1997 21:41:51 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA17359 for ; Tue, 25 Mar 1997 21:41:48 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id VAA00552 for ; Tue, 25 Mar 1997 21:41:44 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA25237; Wed, 26 Mar 1997 16:09:06 +1030 (CST) From: Michael Smith Message-Id: <199703260539.QAA25237@genesis.atrad.adelaide.edu.au> Subject: Re: SIGTERMs killing X In-Reply-To: <199703260450.VAA27126@phaeton.artisoft.com> from Terry Lambert at "Mar 25, 97 09:50:50 pm" To: terry@lambert.org (Terry Lambert) Date: Wed, 26 Mar 1997 16:09:05 +1030 (CST) Cc: drussell@saturn-tech.com, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert stands accused of saying: > > in the last few days for no apparent reason. > > > > Mar 24 12:22:23 586quick166 /kernel: pid 218 (XF86_SVGA), uid 0: exited on signal 6 > > Mar 25 11:27:22 586quick166 /kernel: pid 7136 (XF86_SVGA), uid 0: exited on signal 6 > > > > I can't for the life of me determine why it would have got an ABORT > > signal.... Where would that be coming from? The machine is just sitting > > there idle (AFAIK, anyway... :)) and when I get home from work, for > > example, it's no longer running X. > > It is because FreeBSD is overcommiting memory in it's VM system. > > I am sorry for you that you got this error... > > I am glad you got this error, because you are a real-world example > of a need for a tunable which I have been lobbying for for four years. > Now I have a sample case, and I am happy because I can flagellate > the powers that be every time the topic comes up in the future. 8-). > > > What it means is that your VM space for your process has been > destroyed (you can see this by looking in /sys/kern/kern_exec.c). Actually, in all my (few) years of abusing FreeBSD systems, I have never, to my knowledge, received a SIGABRT for any reason other than memory corruption, either through VM breakage or good old PC memory crap. > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Mar 25 21:51:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA18162 for current-outgoing; Tue, 25 Mar 1997 21:51:58 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA18151 for ; Tue, 25 Mar 1997 21:51:55 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA01493; Tue, 25 Mar 1997 22:51:53 -0700 (MST) Date: Tue, 25 Mar 1997 22:51:53 -0700 (MST) Message-Id: <199703260551.WAA01493@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: current@freebsd.org Subject: dumpfs patch for review X-Mailer: VM 6.22 under 19.14 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It's not pretty, and I'm not sure how to 'correctly' printout the value of the new fs_id line, but since no-one else appears to be doing anything about it here's my attempt at fixing the broken tree. If no one objects I'll commit this tomorrow after enough people have time to review it. Nate ---------- Index: dumpfs.c =================================================================== RCS file: /home/CVS/src/sbin/dumpfs/dumpfs.c,v retrieving revision 1.6 diff -c -r1.6 dumpfs.c *** dumpfs.c 1997/03/11 12:12:26 1.6 --- dumpfs.c 1997/03/26 05:49:19 *************** *** 143,153 **** afs.fs_frag, afs.fs_fragshift, afs.fs_fsbtodb); printf("cpg\t%d\tbpg\t%d\tfpg\t%d\tipg\t%d\n", afs.fs_cpg, afs.fs_fpg / afs.fs_frag, afs.fs_fpg, afs.fs_ipg); ! printf("minfree\t%d%%\toptim\t%s\tmaxcontig %d\tmaxbpg\t%d\n", afs.fs_minfree, afs.fs_optim == FS_OPTSPACE ? "space" : "time", ! afs.fs_maxcontig, afs.fs_maxbpg); ! printf("rotdelay %dms\theadswitch %dus\ttrackseek %dus\trps\t%d\n", ! afs.fs_rotdelay, afs.fs_headswitch, afs.fs_trkseek, afs.fs_rps); printf("ntrak\t%d\tnsect\t%d\tnpsect\t%d\tspc\t%d\n", afs.fs_ntrak, afs.fs_nsect, afs.fs_npsect, afs.fs_spc); printf("symlinklen %d\ttrackskew %d\tinterleave %d\tcontigsumsize %d\n", --- 143,153 ---- afs.fs_frag, afs.fs_fragshift, afs.fs_fsbtodb); printf("cpg\t%d\tbpg\t%d\tfpg\t%d\tipg\t%d\n", afs.fs_cpg, afs.fs_fpg / afs.fs_frag, afs.fs_fpg, afs.fs_ipg); ! printf("minfree\t%d%%\toptim\t%s\tfsid\t%ld\n", afs.fs_minfree, afs.fs_optim == FS_OPTSPACE ? "space" : "time", ! afs.fs_id); ! printf("maxcontig %d\tmaxbpg\t%d\trotdelay %dms\trps\t%d\n", ! afs.fs_maxcontig, afs.fs_maxbpg, afs.fs_rotdelay, afs.fs_rps); printf("ntrak\t%d\tnsect\t%d\tnpsect\t%d\tspc\t%d\n", afs.fs_ntrak, afs.fs_nsect, afs.fs_npsect, afs.fs_spc); printf("symlinklen %d\ttrackskew %d\tinterleave %d\tcontigsumsize %d\n", From owner-freebsd-current Tue Mar 25 22:14:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA19088 for current-outgoing; Tue, 25 Mar 1997 22:14:13 -0800 (PST) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA19083 for ; Tue, 25 Mar 1997 22:14:09 -0800 (PST) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id WAA26377; Tue, 25 Mar 1997 22:17:06 -0800 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id BAA12407; Wed, 26 Mar 1997 01:13:31 -0500 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id BAA06778; Wed, 26 Mar 1997 01:13:29 -0500 Received: (from alk@localhost) by compound.east.sun.com (8.8.5/8.7.3) id GAA01499; Wed, 26 Mar 1997 06:13:27 GMT Date: Wed, 26 Mar 1997 06:13:27 GMT Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199703260613.GAA01499@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: current@freebsd.org Cc: ville@vlsi.fi Subject: Suggested fetchmail port addition (was: Re: Fetchmail nolonger working) X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quoth Ville Eerola on Wed, 26 March: : Normally fetchmail uses SMTP : connection to the localhost to deliver the messages it downloads from : the mail sever. Thus, you need to have a MTA listening to port 25 on : the host runnig fetchmail, or alternatively you need to configure : fetchmail to use a local MDA directly. Speaking of which, here is a local MDA I use in order that I do not have to run a local sendmail. Unless I am overlooking equivalent functionality already hidden somewhere in the base OS, it might be useful to include this in the fetchmail port. /home/alk/.fetchmailrc: server subtle proto imap user alk pass ******** mda /usr/local/bin/catmail server saphire proto imap port 3131 user alk pass ******** mda /usr/local/bin/catmail server perham proto pop3 user alk pass ******** mda /usr/local/bin/catmail /usr/local/bin/catmail: #!/usr/bin/perl # # name: # catmail # description: # a mail delivery agent in perl # usage: # catmail [-{q,v}]* < mailstream # environment: # MAIL path to spool file # synopsis: # delivers a single mail message on stdin to the user spool file # specified by the environment. # author: # alk@pobox.com # date: # 12 Mar 97 # $verbose=0; $quiet=1; while ($ARGV[0]) { if ($ARGV[0] =~ '^-.*[vV]') { $verbose=1; } if ($ARGV[0] =~ '^-.*[qQ]') { $quiet=0; } shift; } $mail=$ENV{'MAIL'}; if (! $mail) { $mail=$ENV{'SPOOL'}; } if (! $mail) { $_=$ENV{'USER'}; if (!$_) { $_=$ENV{'HOME'}; if ($_) { s,.*/,,g; } } if (-d '/var/mail') { $mail="/var/mail/$_"; } elsif (-d '/usr/spool/mail') { $mail="/usr/spool/mail/$_"; } } $_=$mail; $user=s,.*/,,g; die "Unable to set spool file path" unless $mail; die "Unable to open spool file $mail" unless open(MAIL,">>$mail"); $line=0; $replyto=''; $returnpath=''; $from=''; while () { if (/^Reply-To: ([-_.A-Za-z0-9]*@[-_.A-Za-z0-9]*).*/) { $replyto=$1; $header[$line++]=$_; } elsif (/^Return-Path: .*<([-_.A-Za-z0-9]*@[-_.A-Za-z0-9]*)>.*/) { $returnpath=$1; $header[$line++]=$_; } elsif (/^From: .*<([-_.A-Za-z0-9]*@[-_.A-Za-z0-9]*)>.*/) { $from=$1; $header[$line++]=$_; } elsif (/^[A-Z][-A-Za-z]*: .*/) { $header[$line++]=$_; } elsif (/^\t/) { $header[$line++]=$_; } elsif (/^ /) { $header[$line++]=$_; } else { $keep=$_; last; } } if ($from) { $xfrom=$from; } elsif ($replyto) { $xfrom=$replyto; } elsif ($returnpath) { $xfrom=$returnpath; } else { $xfrom=$user } @WEEK=('Sun', 'Mon', 'Tue', 'Wed', 'Thu', 'Fri', 'Sat'); @MONTH=('Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'); ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); if ($year > 38 && $year <= 99 ) { $cent = 19; } else { $cent = 20; } printf MAIL "From %s %s %s %d %d:%02d:%02d %02d%02d\n", $xfrom,$WEEK[$wday],$MONTH[$mon],$mday,$hour,$min,$sec,$cent,$year || die "Unable to append to $mail"; if ($verbose) { print ":"; } for ($i=0; $line--; ) { print MAIL $header[$i++] || die "Unable to append header line $i to $mail"; if ($verbose) { print ","; } } print MAIL "$keep"; while () { $i++; print MAIL $_ || die "Unable to append mail line $i to $mail"; if ($verbose) { print "."; } } if ($verbose) { print "\n"; } if (! $quiet) { print "$i lines output\n"; } close(MAIL); From owner-freebsd-current Tue Mar 25 22:51:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA20621 for current-outgoing; Tue, 25 Mar 1997 22:51:46 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA20616 for ; Tue, 25 Mar 1997 22:51:43 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id RAA31869; Wed, 26 Mar 1997 17:44:07 +1100 Date: Wed, 26 Mar 1997 17:44:07 +1100 From: Bruce Evans Message-Id: <199703260644.RAA31869@godzilla.zeta.org.au> To: bde@zeta.org.au, terry@lambert.org Subject: Re: 2.2R (src 2.2 211): == dialing Cc: freebsd-current@freebsd.org, joerg_wunsch@uriah.heep.sax.de, rb@gid.co.uk Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >>The slattach daemon has a controlling tty... >> > >> >Only until it calls daemon() immediately after cracking its args. >> >> No. It acquires a controlling tty a few lines after it becomes a >> daemon, at least in the redial case (I think the !redial case is >> still broken - it does a null redial instead of aborting like the >> documentation for the -l option says it does). > >This means it should get a SIGHUP on on-to-off DCD transistion if >-CLOCAL is set. It does. >Does it mean it should get SIGHUP when the tty is revoked? ...I don't >think so, actually. It doesn't. >You *could* argue, on this basis, that slattach is doing the wrong thing, >and that's what's leaving it open to getting a SIGHUP when it should >not be getting on. It wants to get a SIGHUP on hangup, and it does all the right things to get one on POSIX systems. There are an onerous number of things to do... Bruce From owner-freebsd-current Tue Mar 25 22:52:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA20729 for current-outgoing; Tue, 25 Mar 1997 22:52:07 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA20724 for ; Tue, 25 Mar 1997 22:52:04 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA02534; Tue, 25 Mar 1997 22:50:39 -0800 (PST) To: Terry Lambert cc: drussell@saturn-tech.com (Doug Russell), freebsd-current@freebsd.org Subject: Re: SIGTERMs killing X In-reply-to: Your message of "Tue, 25 Mar 1997 21:50:50 MST." <199703260450.VAA27126@phaeton.artisoft.com> Date: Tue, 25 Mar 1997 22:50:39 -0800 Message-ID: <2530.859359039@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I can't for the life of me determine why it would have got an ABORT > > signal.... Where would that be coming from? The machine is just sitting > > there idle (AFAIK, anyway... :)) and when I get home from work, for > > example, it's no longer running X. > > It is because FreeBSD is overcommiting memory in it's VM system. > > I am sorry for you that you got this error... Ah, I just love it when Terry gleefully spies the football heading his way, runs to intercept it and makes one of those beautiful diving catches you only see on the NFL videos, catching it, spinning gracefully over one shoulder and coming to his feet again, all in a single motion, running away from a frustrated knot of offensive tackles to dance into the touchdown zone. Unfortunately, when he goes to spike the ball in victory, it turns out that his catch is not a football but an irate pigeon who pecks him solidly on the nose for his offense and flies away. Sigh, all that effort and style to no end! ;-) In this case, Terry's pigeon was SIGABRT, which is not the same as the SIGKILL which FreeBSD delivers to a process which has generated an out-of-VM condition. But for a mere delta of 3 in the signal number, Terry might have been correct. :-) As it is, he's entirely on the wrong track yet again. The SIGABRT must be something which is caught internally by the server, perhaps in response to a NULL pointer reference or malloc() returning zero (which could be bogus limit values just as easily as anything else). More than this without knowing more about the user's configuration, it's difficult to say. > What it means is that your VM space for your process has been > destroyed (you can see this by looking in /sys/kern/kern_exec.c). Erm, you can? :-) You're not looking at the exec_fail case by mistake, are you? Jordan From owner-freebsd-current Tue Mar 25 23:35:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA23180 for current-outgoing; Tue, 25 Mar 1997 23:35:44 -0800 (PST) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA23168 for ; Tue, 25 Mar 1997 23:35:35 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id SAA29314; Wed, 26 Mar 1997 18:35:16 +1100 (EST) From: David Dawes Message-Id: <199703260735.SAA29314@rf900.physics.usyd.edu.au> Subject: Re: SIGTERMs killing X In-Reply-To: from Doug Russell at "Mar 25, 97 07:46:57 pm" To: drussell@saturn-tech.com (Doug Russell) Date: Wed, 26 Mar 1997 18:35:15 +1100 (EST) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Tue, 25 Mar 1997, Terry Lambert wrote: > >> I'm not sure whether SIGTERM should ever be sent, actually... I guess >> it can't hurt, considering it's default is to terminate the process. > >All this talk of signals reminds me of a (totally) unrelated problem one >of my machines seems to be having lately..... My main workstation, which >usually runs X all the time, has exited on a sig 6 from X a couple times >in the last few days for no apparent reason. > >Mar 24 12:22:23 586quick166 /kernel: pid 218 (XF86_SVGA), uid 0: exited on signal 6 >Mar 25 11:27:22 586quick166 /kernel: pid 7136 (XF86_SVGA), uid 0: exited on signal 6 > >I can't for the life of me determine why it would have got an ABORT >signal.... Where would that be coming from? The machine is just sitting >there idle (AFAIK, anyway... :)) and when I get home from work, for >example, it's no longer running X. Check the X server's stderr, and it will tell you (a little) more. By default, the server traps most signals, cleans up (restores the video mode back to a text mode) then calls abort(3) to get a core (if the server's uid == euid), hence the SIGABRT. David From owner-freebsd-current Wed Mar 26 00:08:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA24675 for current-outgoing; Wed, 26 Mar 1997 00:08:44 -0800 (PST) Received: from hydrogen.nike.efn.org (metriclient-9.uoregon.edu [128.223.172.9]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA24669 for ; Wed, 26 Mar 1997 00:08:39 -0800 (PST) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.4/8.8.4) id AAA14595; Wed, 26 Mar 1997 00:07:30 -0800 (PST) Message-ID: <19970326000730.08071@hydrogen.nike.efn.org> Date: Wed, 26 Mar 1997 00:07:30 -0800 From: John-Mark Gurney To: freebsd-current@freebsd.org Subject: patch to make chat work on non-tty devices... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2-960801-SNAP i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk anybody object to me committing this patch to chat? all it does is not error out when the input isn't a tty... it seems the struct was already there to support non-tty devices... just wasn't properly added... comments? anybody think I should remove the warning, and just let it slide? Index: chat.c =================================================================== RCS file: /home/ncvs/src/usr.bin/chat/chat.c,v retrieving revision 1.6 diff -c -r1.6 chat.c *** chat.c 1997/02/22 19:54:23 1.6 --- chat.c 1997/03/26 08:01:33 *************** *** 542,548 **** if (get_term_param (&t) < 0) { ! sysfatal("Can't get terminal parameters"); } saved_tty_parameters = t; --- 542,550 ---- if (get_term_param (&t) < 0) { ! syslog(LOG_WARNING, "warning: Can't get terminal parameters"); ! have_tty_parameters = 0; ! return; } saved_tty_parameters = t; -- John-Mark Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix) From owner-freebsd-current Wed Mar 26 00:47:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA26472 for current-outgoing; Wed, 26 Mar 1997 00:47:44 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA26459 for ; Wed, 26 Mar 1997 00:47:39 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id IAA11159; Wed, 26 Mar 1997 08:47:31 GMT From: mika ruohotie Message-Id: <199703260847.IAA11159@shadows.aeon.net> Subject: Re: SIGTERMs killing X In-Reply-To: <199703260521.WAA27235@phaeton.artisoft.com> from Terry Lambert at "Mar 25, 97 10:21:01 pm" To: terry@lambert.org (Terry Lambert) Date: Wed, 26 Mar 1997 10:47:31 +0200 (EET) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > are the cause of a memory leak. You should consider using an X > server that has been linked against Poul-Henning Kamp's new malloc, > which is capable of sbrk'ing back to the system. do i get phk_malloc when i compile whole X from the /usr/ports collection? mickey From owner-freebsd-current Wed Mar 26 00:51:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA26665 for current-outgoing; Wed, 26 Mar 1997 00:51:20 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA26658 for ; Wed, 26 Mar 1997 00:51:17 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA23038 for freebsd-current@freebsd.org; Wed, 26 Mar 1997 09:51:08 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA10296; Wed, 26 Mar 1997 09:26:27 +0100 (MET) Message-ID: <19970326092627.AV61167@uriah.heep.sax.de> Date: Wed, 26 Mar 1997 09:26:27 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org Subject: Re: Burning a 2.2.1R CDROM myself.. How? References: <921.859270807@time.cdrom.com> <19970326011239.16775@keltia.freenix.fr> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970326011239.16775@keltia.freenix.fr>; from Ollivier Robert on Mar 26, 1997 01:12:39 +0100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > Don't forget to take the cdrom.inf located somewhere inside release/ and > stick it on the CD... > > Extracted from release/Makefile: > > echo "CD_VERSION = ${BUILDNAME}" > ${FD}/cdrom.inf You're not good in reading Makefiles, Ollivier. :-) Your opinion is from older days, but the above quotation is from a current release Makefile. ${FD} stands for ``FTP directory''. :-P -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Mar 26 01:02:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA27423 for current-outgoing; Wed, 26 Mar 1997 01:02:25 -0800 (PST) Received: from dfw-ix10.ix.netcom.com (dfw-ix10.ix.netcom.com [206.214.98.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA27400 for ; Wed, 26 Mar 1997 01:02:19 -0800 (PST) Received: (from smap@localhost) by dfw-ix10.ix.netcom.com (8.8.4/8.8.4) id DAA16308; Wed, 26 Mar 1997 03:01:36 -0600 (CST) Received: from wck-ca9-25.ix.netcom.com(204.31.231.121) by dfw-ix10.ix.netcom.com via smap (V1.3) id sma016299; Wed Mar 26 03:01:07 1997 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id BAA01820; Wed, 26 Mar 1997 01:01:00 -0800 (PST) Date: Wed, 26 Mar 1997 01:01:00 -0800 (PST) Message-Id: <199703260901.BAA01820@silvia.HIP.Berkeley.EDU> To: Anthony.Kimball@East.Sun.COM CC: current@FreeBSD.ORG, ville@vlsi.fi In-reply-to: <199703260613.GAA01499@compound.east.sun.com> (message from Tony Kimball on Wed, 26 Mar 1997 06:13:27 GMT) Subject: Re: Suggested fetchmail port addition (was: Re: Fetchmail nolonger working) From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Speaking of which, here is a local MDA I use in order that I do not * have to run a local sendmail. Unless I am overlooking equivalent * functionality already hidden somewhere in the base OS, it might be * useful to include this in the fetchmail port. * * /home/alk/.fetchmailrc: * server subtle proto imap user alk pass ******** mda /usr/local/bin/catmail * server saphire proto imap port 3131 user alk pass ******** mda /usr/local/bin/catmail * server perham proto pop3 user alk pass ******** mda /usr/local/bin/catmail I use server foo protocol pop3 fetchall password ******** mda "/usr/libexec/mail.local %s" Satoshi From owner-freebsd-current Wed Mar 26 01:04:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA27643 for current-outgoing; Wed, 26 Mar 1997 01:04:08 -0800 (PST) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA27637 for ; Wed, 26 Mar 1997 01:04:03 -0800 (PST) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id JAA00538 for current@FreeBSD.org; Wed, 26 Mar 1997 09:04:01 GMT From: Wolfgang Helbig Message-Id: <199703260904.JAA00538@helbig.informatik.ba-stuttgart.de> Subject: make world fails on libmytinfo To: current@FreeBSD.org Date: Wed, 26 Mar 1997 10:04:01 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, Here is a patch fixing it. I consider clauses like "__FreeBSD != 2__" harmful. For those dependencies we have CVS, don't we. But there might be a reason for it, so I left them in. Wolfgang Index: defs.h =================================================================== RCS file: /usr/cvsroot/src/lib/libmytinfo/defs.h,v retrieving revision 1.1.1.1 diff -c -r1.1.1.1 defs.h *** defs.h 1994/10/06 23:38:40 1.1.1.1 --- defs.h 1997/03/26 08:50:02 *************** *** 190,196 **** /* for quit.c */ extern int sys_nerr; ! #if __FreeBSD__ != 2 extern char *sys_errlist[]; #endif extern char *prg_name; --- 190,196 ---- /* for quit.c */ extern int sys_nerr; ! #if __FreeBSD__ != 2 && __FreeBSD__ != 3 extern char *sys_errlist[]; #endif extern char *prg_name; From owner-freebsd-current Wed Mar 26 01:18:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA28346 for current-outgoing; Wed, 26 Mar 1997 01:18:48 -0800 (PST) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA28339 for ; Wed, 26 Mar 1997 01:18:45 -0800 (PST) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.8.3/8.6.9) with SMTP id JAA04753 for ; Wed, 26 Mar 1997 09:18:45 GMT Date: Wed, 26 Mar 1997 09:18:44 +0000 (GMT) From: Developer To: freebsd-current@freebsd.org Subject: Problems with PPP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having a problem with the user side 'ppp' program. Ive connected it up to a dialup server and logged in, everything seems to be okay but the machine seems to loose all the packets it sends, althought it recieves packets according to tcpdump. The strange thing is also that 'route get default' hangs for ages before returning tun0?? Any help would be great. Thanks in advance. Trefor S> From owner-freebsd-current Wed Mar 26 01:31:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA28953 for current-outgoing; Wed, 26 Mar 1997 01:31:51 -0800 (PST) Received: from dfw-ix15.ix.netcom.com (dfw-ix15.ix.netcom.com [206.214.98.15]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA28944; Wed, 26 Mar 1997 01:31:41 -0800 (PST) Received: (from smap@localhost) by dfw-ix15.ix.netcom.com (8.8.4/8.8.4) id DAA10637; Wed, 26 Mar 1997 03:31:09 -0600 (CST) Received: from wck-ca9-25.ix.netcom.com(204.31.231.121) by dfw-ix15.ix.netcom.com via smap (V1.3) id sma010495; Wed Mar 26 03:30:36 1997 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id BAA01900; Wed, 26 Mar 1997 01:28:20 -0800 (PST) Date: Wed, 26 Mar 1997 01:28:20 -0800 (PST) Message-Id: <199703260928.BAA01900@silvia.HIP.Berkeley.EDU> To: phk@freebsd.org CC: gibbs@freebsd.org, current@freebsd.org, se@freebsd.org In-reply-to: <8145.859321269@critter> (message from Poul-Henning Kamp on Tue, 25 Mar 1997 21:21:09 +0100) Subject: Re: RELENG_2_2, ahc and Atlas II, YES!! From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * I upgraded the box that's been giving me trouble to RELENG_2_2 as of * this morning, danish time and it went straight through the operation * that would until now 100% probability hang it. * * Thanks! What's your firmware revision? Wide or narrow? My "QUANTUM XP34550W LXQ1" used to corrupt files with 2940UW (and ftp.qntm.com doesn't have firmware upgrades for wide AII drives....). * Now for the question: * * Assume a machine with a 3940 in it. The bios will take bus A * first, then bus B. FreeBSD does the same thing. * * Now add a 2940 to it. The bios goes 3940:A, 3940:B, 2940, * FreeBSD goes 2940, 3940:A, 3940:B * * why ? * * I can understand that the order in the PCI slots matter and all that, * but shouldn't we be able to do it in the same order the BIOS does it ? * It's a semi-bad nuisance otherwise... Wow. I have never seen a BIOS that wants to do it that way. AFAIK FreeBSD always probes all devices on bus N before looking into bus N+1 (and since the 3940 has two SCSI chips on a secondary PCI bus, it will always be probed after the 2940). Your BIOS seems to be doing it in depth first order (or postorder, although I surely hope that's not the case ;). We (Stefan and I) fixed the bridge handling code in sys/pci/pci.c rev 1.51 so that the kernel uses the PCI bus numbers assigned by the BIOS. It was necessary to boot on some machines when there were more than one 3940 in there. But for what you say -- I don't even know if it's possible to fix. Does the BIOS leave enough information around to determine if it's done the disk probes in depth-first order? Satoshi From owner-freebsd-current Wed Mar 26 02:13:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA00925 for current-outgoing; Wed, 26 Mar 1997 02:13:40 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA00918 for ; Wed, 26 Mar 1997 02:13:34 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id VAA05821; Wed, 26 Mar 1997 21:11:33 +1100 Date: Wed, 26 Mar 1997 21:11:33 +1100 From: Bruce Evans Message-Id: <199703261011.VAA05821@godzilla.zeta.org.au> To: current@FreeBSD.org, helbig@MX.BA-Stuttgart.De Subject: Re: make world fails on libmytinfo Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Here is a patch fixing it. I consider clauses like "__FreeBSD != 2__" harmful. >For those dependencies we have CVS, don't we. But there might be a reason >for it, so I left them in. > /* for quit.c */ > extern int sys_nerr; >! #if __FreeBSD__ != 2 && __FreeBSD__ != 3 > extern char *sys_errlist[]; > #endif > extern char *prg_name; It is just harmful. Const'ness of sys_errlist has nothing to do with FreeBSD. BTW, sys_nerr is also const in FreeBSD, but the type mismatch is only warned about if gcc is invoked with -pedantic. Bruce From owner-freebsd-current Wed Mar 26 02:33:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA01729 for current-outgoing; Wed, 26 Mar 1997 02:33:59 -0800 (PST) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA01724 for ; Wed, 26 Mar 1997 02:33:53 -0800 (PST) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id KAA20630; Wed, 26 Mar 1997 10:31:03 GMT Date: Wed, 26 Mar 1997 10:25:05 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 26 Mar 1997 10:25:05 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199703252328.QAA26225@phaeton.artisoft.com> References: from "Bob Bishop" at Mar 25, 97 11:00:54 pm Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Terry Lambert From: Bob Bishop Subject: Re: 2.2R (src 2.2 211): == dialing Cc: bde@zeta.org.au, freebsd-current@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk At 11:28 pm -0000 25/3/97, Terry Lambert wrote: >[...] >It should be possible to >distinguish a process which has made a tty it's controlling tty >in order to get device events as signals, and a process which >has a controlling tty because it is interactive. Do you mean "a process which has no controlling tty should be able to open a tty without that automatically becoming its controlling tty"? If not, please explain. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Wed Mar 26 02:37:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA01919 for current-outgoing; Wed, 26 Mar 1997 02:37:46 -0800 (PST) Received: from critter.dk.tfs.com (phk.cybercity.dk [195.8.133.247]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA01914; Wed, 26 Mar 1997 02:37:36 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id LAA11979; Wed, 26 Mar 1997 11:36:39 +0100 (CET) To: asami@vader.cs.berkeley.edu (Satoshi Asami) cc: gibbs@freebsd.org, current@freebsd.org, se@freebsd.org Subject: Re: RELENG_2_2, ahc and Atlas II, YES!! In-reply-to: Your message of "Wed, 26 Mar 1997 01:28:20 PST." <199703260928.BAA01900@silvia.HIP.Berkeley.EDU> Date: Wed, 26 Mar 1997 11:36:39 +0100 Message-ID: <11977.859372599@critter> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199703260928.BAA01900@silvia.HIP.Berkeley.EDU>, Satoshi Asami write s: > * I upgraded the box that's been giving me trouble to RELENG_2_2 as of > * this morning, danish time and it went straight through the operation > * that would until now 100% probability hang it. > * > * Thanks! > >What's your firmware revision? Wide or narrow? My "QUANTUM XP34550W >LXQ1" used to corrupt files with 2940UW (and ftp.qntm.com doesn't have >firmware upgrades for wide AII drives....). LXY4 >But for what you say -- I don't even know if it's possible to fix. >Does the BIOS leave enough information around to determine if it's >done the disk probes in depth-first order? I dunno, It's not a machine I can generally play with, so now that it's running, I'm going to let it run... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Wed Mar 26 02:41:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA02096 for current-outgoing; Wed, 26 Mar 1997 02:41:46 -0800 (PST) Received: from dfw-ix12.ix.netcom.com (dfw-ix12.ix.netcom.com [206.214.98.12]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA02088 for ; Wed, 26 Mar 1997 02:41:43 -0800 (PST) Received: (from smap@localhost) by dfw-ix12.ix.netcom.com (8.8.4/8.8.4) id EAA06266; Wed, 26 Mar 1997 04:37:20 -0600 (CST) Received: from wck-ca9-25.ix.netcom.com(204.31.231.121) by dfw-ix12.ix.netcom.com via smap (V1.3) id sma006262; Wed Mar 26 04:35:50 1997 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id CAA02116; Wed, 26 Mar 1997 02:02:31 -0800 (PST) Date: Wed, 26 Mar 1997 02:02:31 -0800 (PST) Message-Id: <199703261002.CAA02116@silvia.HIP.Berkeley.EDU> To: bsdcur@shadows.aeon.net CC: terry@lambert.org, current@FreeBSD.ORG In-reply-to: <199703260847.IAA11159@shadows.aeon.net> (message from mika ruohotie on Wed, 26 Mar 1997 10:47:31 +0200 (EET)) Subject: Re: SIGTERMs killing X From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * do i get phk_malloc when i compile whole X from the /usr/ports collection? Depends on your imake config file (/usr/X11R6/lib/X11/config/FreeBSD.cf). If it's updated correctly, it should say something like: === #ifndef OSMajorVersion #define OSMajorVersion 2 #endif #ifndef OSMinorVersion #define OSMinorVersion 2 #endif === which would in turn turn off gnumalloc a few lines below: === /* 2.2 doesn't really have GnuMalloc */ #if OSMajorVersion < 2 || (OSMajorVersion == 2 && OSMinorVersion < 2) #define UseGnuMalloc YES #else #define UseGnuMalloc NO #endif #endif === However, the gnumalloc shared library on 2.2 and -current systems is just a skeleton only, so unless your X server is compiled static, it shouldn't make any difference whether it's linked with -lgnumalloc or not. Satoshi From owner-freebsd-current Wed Mar 26 04:45:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA06832 for current-outgoing; Wed, 26 Mar 1997 04:45:55 -0800 (PST) Received: from dfw-ix14.ix.netcom.com (dfw-ix14.ix.netcom.com [206.214.98.14]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA06826; Wed, 26 Mar 1997 04:45:47 -0800 (PST) Received: (from smap@localhost) by dfw-ix14.ix.netcom.com (8.8.4/8.8.4) id GAA11874; Wed, 26 Mar 1997 06:45:11 -0600 (CST) Received: from wck-ca9-25.ix.netcom.com(204.31.231.121) by dfw-ix14.ix.netcom.com via smap (V1.3) id sma011857; Wed Mar 26 06:45:09 1997 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id EAA09673; Wed, 26 Mar 1997 04:45:06 -0800 (PST) Date: Wed, 26 Mar 1997 04:45:06 -0800 (PST) Message-Id: <199703261245.EAA09673@silvia.HIP.Berkeley.EDU> To: phk@critter.dk.tfs.com CC: gibbs@freebsd.org, current@freebsd.org, se@freebsd.org In-reply-to: <11977.859372599@critter> (message from Poul-Henning Kamp on Wed, 26 Mar 1997 11:36:39 +0100) Subject: Re: RELENG_2_2, ahc and Atlas II, YES!! From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * >What's your firmware revision? Wide or narrow? My "QUANTUM XP34550W * >LXQ1" used to corrupt files with 2940UW (and ftp.qntm.com doesn't have * >firmware upgrades for wide AII drives....). * * LXY4 I assume that's a narrow drive? * I dunno, It's not a machine I can generally play with, so now that it's * running, I'm going to let it run... If you get a chance, try swapping the slots of the cards and see if you can get the BIOS to probe the 2940 first.... Satoshi From owner-freebsd-current Wed Mar 26 04:55:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA07233 for current-outgoing; Wed, 26 Mar 1997 04:55:54 -0800 (PST) Received: from critter.dk.tfs.com (phk.cybercity.dk [195.8.133.247]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA07228; Wed, 26 Mar 1997 04:55:45 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id NAA12196; Wed, 26 Mar 1997 13:54:50 +0100 (CET) To: asami@vader.cs.berkeley.edu (Satoshi Asami) cc: gibbs@freebsd.org, current@freebsd.org, se@freebsd.org Subject: Re: RELENG_2_2, ahc and Atlas II, YES!! In-reply-to: Your message of "Wed, 26 Mar 1997 04:45:06 PST." <199703261245.EAA09673@silvia.HIP.Berkeley.EDU> Date: Wed, 26 Mar 1997 13:54:49 +0100 Message-ID: <12194.859380889@critter> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199703261245.EAA09673@silvia.HIP.Berkeley.EDU>, Satoshi Asami write s: > * >What's your firmware revision? Wide or narrow? My "QUANTUM XP34550W > * >LXQ1" used to corrupt files with 2940UW (and ftp.qntm.com doesn't have > * >firmware upgrades for wide AII drives....). > * > * LXY4 > >I assume that's a narrow drive? no, wide. If you do a dd conv=swab < file_from_ftp.qntm.com.fup | strings | more you will notice that the same file seems to apply for several kinds of diskdrives... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Wed Mar 26 07:38:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA16662 for current-outgoing; Wed, 26 Mar 1997 07:38:29 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA16649 for ; Wed, 26 Mar 1997 07:38:26 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0w9um6-00055j-00; Wed, 26 Mar 1997 08:38:06 -0700 To: Bruce Evans Subject: Re: make world fails on libmytinfo Cc: current@freebsd.org, helbig@MX.BA-Stuttgart.De In-reply-to: Your message of "Wed, 26 Mar 1997 21:11:33 +1100." <199703261011.VAA05821@godzilla.zeta.org.au> References: <199703261011.VAA05821@godzilla.zeta.org.au> Date: Wed, 26 Mar 1997 08:38:05 -0700 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199703261011.VAA05821@godzilla.zeta.org.au> Bruce Evans writes: : >Here is a patch fixing it. I consider clauses like "__FreeBSD != 2__" harmful. : >For those dependencies we have CVS, don't we. But there might be a reason : >for it, so I left them in. : : > /* for quit.c */ : > extern int sys_nerr; : >! #if __FreeBSD__ != 2 && __FreeBSD__ != 3 : > extern char *sys_errlist[]; : > #endif : > extern char *prg_name; : : It is just harmful. Const'ness of sys_errlist has nothing to do with : FreeBSD. : : BTW, sys_nerr is also const in FreeBSD, but the type mismatch is only : warned about if gcc is invoked with -pedantic. And it is even esier to fix. Most modern systems have errno.h. Just include that. Since it is in our CVS tree, that seems will be acceptible. Warner From owner-freebsd-current Wed Mar 26 08:04:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA19117 for current-outgoing; Wed, 26 Mar 1997 08:04:50 -0800 (PST) Received: from xoca-160.ssc.af.mil (root@XOCA-160.SSG.GUNTER.AF.MIL [143.158.36.160]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA19108 for ; Wed, 26 Mar 1997 08:04:29 -0800 (PST) Received: from xoca-160.ssc.af.mil (cgagnon@XOCA-160.SSG.GUNTER.AF.MIL [143.158.36.160]) by xoca-160.ssc.af.mil with SMTP (8.7.5/8.7.3) id KAA29729 for ; Wed, 26 Mar 1997 10:03:58 -0600 (CST) Message-ID: <333948ED.1C87@xoca-160.ssc.af.mil> Date: Wed, 26 Mar 1997 10:03:57 -0600 From: Chuck Gagnon Organization: SSG/XOCA X-Mailer: Mozilla 3.0Gold (X11; I; HP-UX B.10.20 9000/715) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Make world (libmytinfo) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is from a make world on 3.0-current sources cvsup'd last night. (25 Mar) I'm not sure why this became a problem, but it was an easy fix. cc -O -Wall -I/usr/src/lib/libmytinfo -c /usr/src/lib/libmytinfo/addstr.c -o addstr.o In file included from /usr/src/lib/libmytinfo/addstr.c:10: /usr/src/lib/libmytinfo/defs.h:194: conflicting types for `sys_errlist' /usr/include/stdio.h:245: previous declaration of `sys_errlist' *** Error code 1 Stop. /usr/src/lib/libmytinfo/defs.h contains: /* for quit.c */ extern int sys_nerr; #if __FreeBSD__ != 2 extern char sys_errlist[]; ---- This is line 194 ---- #endif /usr/include/stdio.h contains: #if !defined(_ANSI_SOURCE) && !defined(_POSIX_SOURCE) extern __const int sys_nerr; /* perror(3) external variables */ extern __const char *__const sys_errlist[]; ---- This is line 245 ---- #endif So I made sys_errlist in defs.h look like stdio.h and everything was fine. Shouldn't defs.h read #if __FreeBSD__ != 3 instead of #if __FreeBSD__ != 2. -- Charles Gagnon Email : cgagnon@mail.the-link.net From owner-freebsd-current Wed Mar 26 08:48:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA22632 for current-outgoing; Wed, 26 Mar 1997 08:48:00 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA22621; Wed, 26 Mar 1997 08:47:54 -0800 (PST) From: Mike Pritchard Message-Id: <199703261647.IAA22621@freefall.freebsd.org> Subject: Re: dumpfs patch for review To: nate@mt.sri.com (Nate Williams) Date: Wed, 26 Mar 1997 08:47:52 -0800 (PST) Cc: current@FreeBSD.ORG In-Reply-To: <199703260551.WAA01493@rocky.mt.sri.com> from "Nate Williams" at Mar 25, 97 10:51:53 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nate Williams wrote: > > It's not pretty, and I'm not sure how to 'correctly' printout the value > of the new fs_id line, but since no-one else appears to be doing > anything about it here's my attempt at fixing the broken tree. > > If no one objects I'll commit this tomorrow after enough people have > time to review it. fs_id[0] is a time_t value, and probably should be printed as such. is it the time that the file system was "randomized", either by newfs or fsirand. fd_id[1] is a random number -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-current Wed Mar 26 09:44:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA29580 for current-outgoing; Wed, 26 Mar 1997 09:44:56 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA29543 for ; Wed, 26 Mar 1997 09:44:37 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA04465; Wed, 26 Mar 1997 10:44:10 -0700 (MST) Date: Wed, 26 Mar 1997 10:44:10 -0700 (MST) Message-Id: <199703261744.KAA04465@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Pritchard Cc: nate@mt.sri.com (Nate Williams), current@freebsd.org Subject: Re: dumpfs patch for review In-Reply-To: <199703261647.IAA22621@freefall.freebsd.org> References: <199703260551.WAA01493@rocky.mt.sri.com> <199703261647.IAA22621@freefall.freebsd.org> X-Mailer: VM 6.22 under 19.14 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > It's not pretty, and I'm not sure how to 'correctly' printout the value > > of the new fs_id line, but since no-one else appears to be doing > > anything about it here's my attempt at fixing the broken tree. > > > > If no one objects I'll commit this tomorrow after enough people have > > time to review it. > > fs_id[0] is a time_t value, and probably should be printed as such. > is it the time that the file system was "randomized", either > by newfs or fsirand. Ahh, OK. > fd_id[1] is a random number Ok, here's round two. Nate -------- Index: dumpfs.c =================================================================== RCS file: /home/CVS/src/sbin/dumpfs/dumpfs.c,v retrieving revision 1.6 diff -c -r1.6 dumpfs.c *** dumpfs.c 1997/03/11 12:12:26 1.6 --- dumpfs.c 1997/03/26 17:43:32 *************** *** 127,132 **** --- 127,134 ---- dev_bsize = afs.fs_fsize / fsbtodb(&afs, 1); printf("magic\t%x\ttime\t%s", afs.fs_magic, ctime(&afs.fs_time)); + printf("fsid\t%d\trndtime\t%s", + afs.fs_id[1], ctime((time_t *)&afs.fs_id[0])); printf("cylgrp\t%s\tinodes\t%s\n", afs.fs_postblformat == FS_42POSTBLFMT ? "static" : "dynamic", afs.fs_inodefmt < FS_44INODEFMT ? "4.2/4.3BSD" : "4.4BSD"); *************** *** 143,153 **** afs.fs_frag, afs.fs_fragshift, afs.fs_fsbtodb); printf("cpg\t%d\tbpg\t%d\tfpg\t%d\tipg\t%d\n", afs.fs_cpg, afs.fs_fpg / afs.fs_frag, afs.fs_fpg, afs.fs_ipg); ! printf("minfree\t%d%%\toptim\t%s\tmaxcontig %d\tmaxbpg\t%d\n", ! afs.fs_minfree, afs.fs_optim == FS_OPTSPACE ? "space" : "time", ! afs.fs_maxcontig, afs.fs_maxbpg); ! printf("rotdelay %dms\theadswitch %dus\ttrackseek %dus\trps\t%d\n", ! afs.fs_rotdelay, afs.fs_headswitch, afs.fs_trkseek, afs.fs_rps); printf("ntrak\t%d\tnsect\t%d\tnpsect\t%d\tspc\t%d\n", afs.fs_ntrak, afs.fs_nsect, afs.fs_npsect, afs.fs_spc); printf("symlinklen %d\ttrackskew %d\tinterleave %d\tcontigsumsize %d\n", --- 145,154 ---- afs.fs_frag, afs.fs_fragshift, afs.fs_fsbtodb); printf("cpg\t%d\tbpg\t%d\tfpg\t%d\tipg\t%d\n", afs.fs_cpg, afs.fs_fpg / afs.fs_frag, afs.fs_fpg, afs.fs_ipg); ! printf("minfree\t%d%%\toptim\t%s\n", ! afs.fs_minfree, afs.fs_optim == FS_OPTSPACE ? "space" : "time"); ! printf("maxcontig %d\tmaxbpg\t%d\trotdelay %dms\trps\t%d\n", ! afs.fs_maxcontig, afs.fs_maxbpg, afs.fs_rotdelay, afs.fs_rps); printf("ntrak\t%d\tnsect\t%d\tnpsect\t%d\tspc\t%d\n", afs.fs_ntrak, afs.fs_nsect, afs.fs_npsect, afs.fs_spc); printf("symlinklen %d\ttrackskew %d\tinterleave %d\tcontigsumsize %d\n", From owner-freebsd-current Wed Mar 26 10:42:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA07229 for current-outgoing; Wed, 26 Mar 1997 10:42:02 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA07182 for ; Wed, 26 Mar 1997 10:41:46 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA28346; Wed, 26 Mar 1997 11:27:02 -0700 From: Terry Lambert Message-Id: <199703261827.LAA28346@phaeton.artisoft.com> Subject: Re: SIGTERMs killing X To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 26 Mar 1997 11:27:01 -0700 (MST) Cc: terry@lambert.org, drussell@saturn-tech.com, freebsd-current@freebsd.org In-Reply-To: <2530.859359039@time.cdrom.com> from "Jordan K. Hubbard" at Mar 25, 97 10:50:39 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In this case, Terry's pigeon was SIGABRT, which is not the same as the > SIGKILL which FreeBSD delivers to a process which has generated an > out-of-VM condition. But for a mere delta of 3 in the signal number, > Terry might have been correct. :-) As it is, he's entirely on the > wrong track yet again. The SIGABRT must be something which is caught > internally by the server, perhaps in response to a NULL pointer > reference or malloc() returning zero (which could be bogus limit > values just as easily as anything else). More than this without > knowing more about the user's configuration, it's difficult to say. That would be a bus error, not an abort. > > > What it means is that your VM space for your process has been > > destroyed (you can see this by looking in /sys/kern/kern_exec.c). > > Erm, you can? :-) > > You're not looking at the exec_fail case by mistake, are you? ------------------------------------------------------------------------- exec_fail: if (imgp->vmspace_destroyed) { /* sorry, no more process anymore. exit gracefully */ exit1(p, W_EXITCODE(0, SIGABRT)); /* NOT REACHED */ return(0); } else { ------------------------------------------------------------------------- Hmmm... perhaps. So are you going to change the comment so that it implies what you said instead of implying what I said? "no process anymore" implies there was a process and that it is no more, not that a process never was. PS: I'd be interested to see *anywhere* else in the kernel where the SIGABRT signal is sent. I've grepped the sources, and the only place is there, in the kern_exec.c. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Mar 26 11:15:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA11504 for current-outgoing; Wed, 26 Mar 1997 11:15:24 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA11487 for ; Wed, 26 Mar 1997 11:15:17 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id LAA14966; Wed, 26 Mar 1997 11:13:53 -0800 (PST) To: Terry Lambert cc: drussell@saturn-tech.com, freebsd-current@freebsd.org Subject: Re: SIGTERMs killing X In-reply-to: Your message of "Wed, 26 Mar 1997 11:27:01 MST." <199703261827.LAA28346@phaeton.artisoft.com> Date: Wed, 26 Mar 1997 11:13:53 -0800 Message-ID: <14962.859403633@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hmmm... perhaps. So are you going to change the comment so that > it implies what you said instead of implying what I said? Well, it's not even my comment, so I'm not apt to fool with it. :) FWIW, I didn't read it that way - I see it as just one of the ways in which execve() can fail and someone's attempt to pass back a little extra info about it by [ab]using the signal flags. It would be interesting to check whether any applications are actually using this to provide extra information about a failure. I know that it's not documented in the man page. :-) > PS: I'd be interested to see *anywhere* else in the kernel where the > SIGABRT signal is sent. I've grepped the sources, and the only place There aren't any other places, from what I can tell. Again, the problem you were responding to was almost certainly an internal application abort() and the VM overcommit issue you raised would have raised a KILL and logged it on the system console if that had been the culprit here. Jordan From owner-freebsd-current Wed Mar 26 11:45:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA15310 for current-outgoing; Wed, 26 Mar 1997 11:45:28 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA15301 for ; Wed, 26 Mar 1997 11:45:22 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id UAA21001; Wed, 26 Mar 1997 20:31:30 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.5/8.8.2) id UAA01248; Wed, 26 Mar 1997 20:16:59 +0100 (MET) Message-ID: <19970326201659.02877@klemm.gtn.com> Date: Wed, 26 Mar 1997 20:16:59 +0100 From: Andreas Klemm To: "Justin T. Gibbs" Cc: "Justin T. Gibbs" , Kachun Lee , freebsd-current@freebsd.org Subject: Re: ahc crashes References: <19970320223216.48411@klemm.gtn.com> <199703251940.MAA07835@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 In-Reply-To: <199703251940.MAA07835@narnia.plutotech.com>; from Justin T. Gibbs on Tue, Mar 25, 1997 at 12:40:05PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, Mar 25, 1997 at 12:40:05PM -0700, Justin T. Gibbs wrote: > >Well, my machine still hangs and panics, if I use tagged command > >queuing and try to make a dump to tape. > > My guess is that the source drive of your dump is returning QUEUE_FULL > condition and that it wasn't being handled properly by the driver in > the past. Can you see if this still happens with my latest changes? Well I tried a dump two times now with different results. First of all congradulations, you are making big progress ! The dump doesn't hang up the machine anymore when the first data are about to be written to the tape ! When I tried a dump the first time, the machine hung after about 10-15 seconds of dumping. It was funny ... the first thing I saw was a message reducing tagged openings to three or so ... then the machine hung for some seconds, then again dumped data to disk and after about 10 seconds it hung completely. This was today morning ... After work I tried is half an hour ago with another astonishing results: When data are being written to the tape, the following message appears: sd0: Tagged openings reduced to 3 sd0: SCB 0x1 - timed out in message out phase, SCSISIGI == 0x86 SEQADDR == 0xa3 Ordered Tag queued Ordered Tag sent sd0: no longer in timeout After that the machine dumped my root fs, www and var without problems. /dev/sd0a 31775 16249 12984 56% / /dev/sd0s3e 63567 42424 16058 73% /www /dev/sd0s3f 127151 106108 10871 91% /var To make it a bit more difficult I started a "find / -print" in parallel. This find job worked on the 2nd SCSI disk, where my /local fs resides. This was ok for about 1-2 minutes, but then message over message on the console screen, which resulted finally in a complete hang of the system. Some of the messages I wrote down ... Many messages: ahc0: ahc_intr_referenced SCB not valif during scsiint 0x88 scb(255) SIMODE0 = 0x0 SIMODE1 = 0xa4 SSTAT0 = 0x15 SEQADDR = 0x4 Then: sd0: SCB 0x0 timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x8 SEQADDR == 0x4 Ordered Tag queued Then 2 times: ahc0: ahc_intr_referenced SCB not valif during scsiint 0x88 scb(255) SIMODE0 = 0x0 SIMODE1 = 0xa4 SSTAT0 = 0x15 SEQADDR = 0x4 then: sd1: SCB 0x5 timedout while recovery in progress sd0: SCB 0x2 timedout while recovery in progress sd0: Queueing an Abort SCB I hope you get an idea of what is happening ... Again, good work, it's really better then before !!! Andreas /// My kernel config file and dmesg, in case you need it ... machine "i386" cpu "I586_CPU" # aka Pentium(tm) cpu "I686_CPU" # aka Pentium Pro(tm) ident BISDN maxusers 16 options FAILSAFE options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on sd0a options "COMPAT_43" options SYSVSHM options SYSVSEM options SYSVMSG options "MD5" options UCONSOLE options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpfilter 2 #Berkeley packet filter options "TCP_COMPAT_42" #emulate 4.2BSD TCP bugs options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options FFS #Fast filesystem options MFS #Memory File System options PROCFS #Process filesystem options NSWAPDEV=3 controller pci0 controller ahc0 controller scbus0 at ahc0 # Single bus device disk sd0 at scbus0 target 0 unit 0 disk sd1 at scbus0 target 1 unit 0 disk sd2 at scbus0 target 2 unit 0 tape st0 at scbus0 target 4 unit 0 device cd0 at scbus0 target 6 unit 0 options SCSI_REPORT_GEOMETRY pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device log #Kernel syslog interface (/dev/klog) pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) controller isa0 options "AUTO_EOI_1" device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=6 # number of virtual consoles controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 device lpt0 at isa? port? tty irq 7 vector lptintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device ed0 at isa? port 0x300 net irq 10 iomem 0xcc000 vector edintr controller snd0 device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 device mpu0 at isa? port 0x330 irq 6 drq 0 options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO options SHOW_BUSYBUFS # List buffers that prevent root unmount options TELES_HAS_MEMCPYB # bisdn 0.97 options IPI_VJ # Van Jacobsen header compression support controller tel0 at isa? port 0xd80 net irq 9 vector telintr pseudo-device disdn pseudo-device isdn pseudo-device ipi 2 pseudo-device itel 1 pseudo-device ispy 1 -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Wed Mar 26 11:55:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA16511 for current-outgoing; Wed, 26 Mar 1997 11:55:04 -0800 (PST) Received: from pluto.plutotech.com (root@pluto.plutotech.com [206.168.67.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA16500 for ; Wed, 26 Mar 1997 11:54:59 -0800 (PST) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id MAA29414; Wed, 26 Mar 1997 12:54:44 -0700 (MST) Message-Id: <199703261954.MAA29414@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Andreas Klemm cc: "Justin T. Gibbs" , Kachun Lee , freebsd-current@freebsd.org Subject: Re: ahc crashes In-reply-to: Your message of "Wed, 26 Mar 1997 20:16:59 +0100." <19970326201659.02877@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Mar 1997 12:55:06 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >First of all congradulations, you are making big progress ! What model is the drive you're dumping off of? It certainly seems to have problems with tagged queuing and it may be that what you really want to do is reduce the number of openings from 8 down to 3 in i386/scsi/ aic7xxx.c. It may also be that you need a firmware update on that drive in order to properly do tagged queueing. Se my other post to current about how tagged queueing can still fail if a device returns QUEUE FULL status. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Wed Mar 26 13:10:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA25820 for current-outgoing; Wed, 26 Mar 1997 13:10:40 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA25806 for ; Wed, 26 Mar 1997 13:10:35 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id PAA31005; Wed, 26 Mar 1997 15:10:08 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma030980; Wed Mar 26 15:09:53 1997 Received: from milo.lodgenet.com (milo.lodgenet.com [10.0.11.142]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id PAA16184; Wed, 26 Mar 1997 15:09:57 -0600 Received: from milo.lodgenet.com (localhost [127.0.0.1]) by milo.lodgenet.com (8.8.3/8.6.12) with ESMTP id PAA04119; Wed, 26 Mar 1997 15:10:02 -0600 (CST) Message-Id: <199703262110.PAA04119@milo.lodgenet.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: =?iso-8859-1?Q?S=F8ren?= Schmidt cc: johnp@lodgenet.com (John Prince), current@freebsd.org Subject: Re: Stallion In-reply-to: Your message of "Fri, 07 Mar 1997 22:22:13 +0100." <199703072122.WAA04942@ravenock.cybercity.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Wed, 26 Mar 1997 15:09:59 -0600 From: John Prince Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id NAA25809 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can I get a copy of what you have, to further assist in testing?? --john Søren Schmidt writes: > In reply to John Prince who wrote: > > S=F8ren Schmidt writes: > > > In reply to John Prince who wrote: > > > > Are there any plans to get the Stallion makedev stuff > > > > into MAKEDEV? > > >=20 > > > Yes, and there is also a new updated driver.. > > >=20 > > > It's on my dynamic priority whiteboard, in red ink that is :) > > > Will it make it to 2.2RELEASE>?? > > I don't think so, its not tested that good yet... From owner-freebsd-current Wed Mar 26 13:56:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA01186 for current-outgoing; Wed, 26 Mar 1997 13:56:08 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA01171 for ; Wed, 26 Mar 1997 13:56:02 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA01049; Wed, 26 Mar 1997 22:55:50 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA11590; Wed, 26 Mar 1997 22:47:25 +0100 (MET) Message-ID: <19970326224725.MT45063@uriah.heep.sax.de> Date: Wed, 26 Mar 1997 22:47:25 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org Cc: dev@fgate.flevel.co.uk (Developer) Subject: Re: Problems with PPP References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Developer on Mar 26, 1997 09:18:44 +0000 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Developer wrote: > The strange thing is also that 'route get default' hangs for ages before > returning tun0?? DNS problem. Try route -n get default. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Mar 26 14:22:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA03922 for current-outgoing; Wed, 26 Mar 1997 14:22:19 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA03913 for ; Wed, 26 Mar 1997 14:22:13 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA01415 for freebsd-current@FreeBSD.ORG; Wed, 26 Mar 1997 23:22:11 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA12126; Wed, 26 Mar 1997 23:17:39 +0100 (MET) Message-ID: <19970326231738.ZJ18381@uriah.heep.sax.de> Date: Wed, 26 Mar 1997 23:17:38 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Subject: Re: SIGTERMs killing X References: <2530.859359039@time.cdrom.com> <199703261827.LAA28346@phaeton.artisoft.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703261827.LAA28346@phaeton.artisoft.com>; from Terry Lambert on Mar 26, 1997 11:27:01 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > The SIGABRT must be something which is caught > > internally by the server, perhaps in response to a NULL pointer > > reference or malloc() returning zero (which could be bogus limit > > values just as easily as anything else). > That would be a bus error, not an abort. That's Terry not understanding nor reading the Xserver sources. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Mar 26 14:46:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA06256 for current-outgoing; Wed, 26 Mar 1997 14:46:12 -0800 (PST) Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA06231 for ; Wed, 26 Mar 1997 14:46:05 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.5/8.7.3) id XAA29260; Wed, 26 Mar 1997 23:46:22 +0100 (MET) From: Søren Schmidt Message-Id: <199703262246.XAA29260@ravenock.cybercity.dk> Subject: Re: Stallion In-Reply-To: <199703262110.PAA04119@milo.lodgenet.com> from John Prince at "Mar 26, 97 03:09:59 pm" To: johnp@lodgenet.com (John Prince) Date: Wed, 26 Mar 1997 23:46:22 +0100 (MET) Cc: johnp@lodgenet.com, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to John Prince who wrote: > Can I get a copy of what you have, to further assist in testing?? ERhm, sure, but I think thats what just got committed to current... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Wed Mar 26 14:53:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA07098 for current-outgoing; Wed, 26 Mar 1997 14:53:30 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA07082 for ; Wed, 26 Mar 1997 14:53:27 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA28961; Wed, 26 Mar 1997 15:39:45 -0700 From: Terry Lambert Message-Id: <199703262239.PAA28961@phaeton.artisoft.com> Subject: Re: SIGTERMs killing X To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 26 Mar 1997 15:39:45 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19970326231738.ZJ18381@uriah.heep.sax.de> from "J Wunsch" at Mar 26, 97 11:17:38 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > That would be a bus error, not an abort. > > That's Terry not understanding nor reading the Xserver sources. I don't know which X server he is running. Neither do you. There may not be sources available to read. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Mar 26 15:02:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA07952 for current-outgoing; Wed, 26 Mar 1997 15:02:11 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA07945 for ; Wed, 26 Mar 1997 15:02:07 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA28995; Wed, 26 Mar 1997 15:47:52 -0700 From: Terry Lambert Message-Id: <199703262247.PAA28995@phaeton.artisoft.com> Subject: Re: 2.2R (src 2.2 211): == dialing To: rb@gid.co.uk (Bob Bishop) Date: Wed, 26 Mar 1997 15:47:52 -0700 (MST) Cc: terry@lambert.org, bde@zeta.org.au, freebsd-current@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de In-Reply-To: from "Bob Bishop" at Mar 26, 97 10:25:05 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >[...] > >It should be possible to > >distinguish a process which has made a tty it's controlling tty > >in order to get device events as signals, and a process which > >has a controlling tty because it is interactive. > > Do you mean "a process which has no controlling tty should be able to open > a tty without that automatically becoming its controlling tty"? If not, > please explain. I mean it should be possible to have two processes that are the only processes on their (-CLOCAL) tty, such that: process DCD-on-to-off shutdown-tty-revoke 1 Gets SIGHUP Gets SIGHUP 2 Gets SIGHUP DOESN'T get SIGHUP And that slattch should be set up like process 2. >From Bruce's last posting, it looks like the SIGHUP is resulting from an explicit SIGHUP send rather than as a result of the tty being revoked. If so, this may be purely a problem in the shutdown code and not a problem in the tty code at all (depends on how the revoke acts in regard to a "process 2" type process, assuming slattach is set up as a "process 2" type process. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Mar 26 15:21:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA10109 for current-outgoing; Wed, 26 Mar 1997 15:21:46 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA10089 for ; Wed, 26 Mar 1997 15:21:38 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA02326 for freebsd-current@FreeBSD.ORG; Thu, 27 Mar 1997 00:21:27 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id AAA12531; Thu, 27 Mar 1997 00:19:29 +0100 (MET) Message-ID: <19970327001929.GO22023@uriah.heep.sax.de> Date: Thu, 27 Mar 1997 00:19:29 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Subject: Re: SIGTERMs killing X References: <19970326231738.ZJ18381@uriah.heep.sax.de> <199703262239.PAA28961@phaeton.artisoft.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703262239.PAA28961@phaeton.artisoft.com>; from Terry Lambert on Mar 26, 1997 15:39:45 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > > That would be a bus error, not an abort. > > > > That's Terry not understanding nor reading the Xserver sources. > > I don't know which X server he is running. Terry, admit that you were just plain wrong again (and not even looking). At least the XFree86 server catches SIGBUS and SIGSEGV, in an attempt to cleanup and restore the screen state, and will eventually abort() itself. I don't see any reason why the XiGraphics (sp?) server would do it differently, since it also has to restore the screen mode. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Mar 26 16:26:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA15225 for current-outgoing; Wed, 26 Mar 1997 16:26:16 -0800 (PST) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA15211 for ; Wed, 26 Mar 1997 16:26:07 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id LAA01805; Thu, 27 Mar 1997 11:24:15 +1100 (EST) From: David Dawes Message-Id: <199703270024.LAA01805@rf900.physics.usyd.edu.au> Subject: Re: SIGTERMs killing X In-Reply-To: <199703262239.PAA28961@phaeton.artisoft.com> from Terry Lambert at "Mar 26, 97 03:39:45 pm" To: terry@lambert.org (Terry Lambert) Date: Thu, 27 Mar 1997 11:24:14 +1100 (EST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> > That would be a bus error, not an abort. >> >> That's Terry not understanding nor reading the Xserver sources. > >I don't know which X server he is running. > >Neither do you. I can make a good guess because in the original message where the kernel messages were shown, the name of the executable dying with signal 6 was XF86_SVGA: Mar 24 12:22:23 586quick166 /kernel: pid 218 (XF86_SVGA), uid 0: exited on signal 6 David From owner-freebsd-current Wed Mar 26 16:54:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA18006 for current-outgoing; Wed, 26 Mar 1997 16:54:42 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA18000 for ; Wed, 26 Mar 1997 16:54:38 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id LAA00483; Thu, 27 Mar 1997 11:50:21 +1100 Date: Thu, 27 Mar 1997 11:50:21 +1100 From: Bruce Evans Message-Id: <199703270050.LAA00483@godzilla.zeta.org.au> To: bde@zeta.org.au, imp@village.org Subject: Re: make world fails on libmytinfo Cc: current@FreeBSD.org, helbig@MX.BA-Stuttgart.De Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >: > /* for quit.c */ >: > extern int sys_nerr; >: >! #if __FreeBSD__ != 2 && __FreeBSD__ != 3 >: > extern char *sys_errlist[]; >: > #endif >: > extern char *prg_name; >: >: It is just harmful. Const'ness of sys_errlist has nothing to do with >: FreeBSD. >: >: BTW, sys_nerr is also const in FreeBSD, but the type mismatch is only >: warned about if gcc is invoked with -pedantic. > >And it is even esier to fix. Most modern systems have errno.h. Just >include that. Since it is in our CVS tree, that seems will be >acceptible. errno.h is the problem, not the solution. It pollutes the application namespace by declaring sys_nerr and sys_errlist. libmytinfo is chummy with the implementation in using (*) these variables instead of the public interface (strerror()), but not chummy enough to get the declarations right (except using an ifdef hack). (*) libmytinfo doesn't actually use these variables. It just miscdeclares them. It claims to use them ``/* for quit.c */'', but quit.c isn't in FreeBSD. Bruce From owner-freebsd-current Wed Mar 26 17:04:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA18552 for current-outgoing; Wed, 26 Mar 1997 17:04:57 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA18539 for ; Wed, 26 Mar 1997 17:04:52 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA29306; Wed, 26 Mar 1997 17:50:32 -0700 From: Terry Lambert Message-Id: <199703270050.RAA29306@phaeton.artisoft.com> Subject: Re: SIGTERMs killing X To: dawes@rf900.physics.usyd.edu.au (David Dawes) Date: Wed, 26 Mar 1997 17:50:32 -0700 (MST) Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org In-Reply-To: <199703270024.LAA01805@rf900.physics.usyd.edu.au> from "David Dawes" at Mar 27, 97 11:24:14 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> > That would be a bus error, not an abort. > >> > >> That's Terry not understanding nor reading the Xserver sources. > > > >I don't know which X server he is running. > > > >Neither do you. > > I can make a good guess because in the original message where the > kernel messages were shown, the name of the executable dying with > signal 6 was XF86_SVGA: > > Mar 24 12:22:23 586quick166 /kernel: pid 218 (XF86_SVGA), uid 0: exited on signal 6 I stand corrected. I apparently didn't carry enough context forward. Under what normal operational circumstances could this happen? (ie: any known bugs?). If there aren't any, then the fact that it didn't happen before but does now points at FreeNSD, not a X. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Mar 26 21:10:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA04718 for current-outgoing; Wed, 26 Mar 1997 21:10:57 -0800 (PST) Received: from 586quick166.saturn-tech.com ([207.229.19.32]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA04713 for ; Wed, 26 Mar 1997 21:10:45 -0800 (PST) Received: from localhost (drussell@localhost) by 586quick166.saturn-tech.com (8.8.4/8.8.4) with SMTP id WAA01533; Wed, 26 Mar 1997 22:08:10 GMT X-Authentication-Warning: 586quick166.saturn-tech.com: drussell owned process doing -bs Date: Wed, 26 Mar 1997 22:08:10 +0000 () From: Doug Russell To: Terry Lambert cc: David Dawes , joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org Subject: Re: SIGABRTs killing X In-Reply-To: <199703270050.RAA29306@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I finally had to change the subject line... I wasn't thinking when I typed it the first time and it has been annoying me. :) Anyway... I thought I would provide a little more detail since this has become a bit of a topic on its own. I have been using this release of XF86_SVGA for several months on this machine, and never had any kind of problem before. I've used it on several different versions of FreeBSD, including 2.1.5, 2.2-ALPHA and currently 2.2-BETA. I've used it on several different machines, including my bedroom PC (Actually, it is physically IN my bed... One of the drawers in the bottom of the waterbed serves as it's case. :) Yes, I am crazy.) The bedroom machine has run that XF86_SVGA for weeks on end with no problems at all. I've also run it for reasonable lengths of time on this machine before with out any problems. I can't think of anything that has changed at all recently, except I installed a PCI 3C905-TX in place of the previous 3C509TP. The last change before that was to put in 4x 8 meg EDO 45ns SIMMs so I could turn up the memory speed knobbies in the CMOS to full blast. The board is a Gigabyte 586VX, currently running a Cyrix P166+. Video is a Cirrus Logic 5446 based card with 4 megs. real memory = 33554432 (32768K bytes) avail memory = 30543872 (29828K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vx0 <3COM 3C905 Fast Etherlink XL PCI> rev 0 int a irq 11 on pci0:9 mii[*mii*] address 00:60:97:83:8e:69 vga0 rev 0 on pci0:10 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 405MB (830760 sectors), 989 cyls, 15 heads, 56 S/T, 512 B/S wdc1 not found at 0x170 matcd - Matsushita (Panasonic) CD-ROM Driver by FDIV, Version 1(26) 18-Oct-95 matcdc0 at 0x230-0x233 on isa matcdc0 Host interface type 0 matcd0: [CR-5630.75] matcd1: [CR-5630.81] npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa sb0: sbxvi0 at 0x0 drq 5 on isa sbxvi0: sbmidi0 at 0x330 on isa opl0 at 0x388 on isa opl0: The X server itself is the October whatever (26th?) 1996 release. I am about to FTP over a copy of the 3.2A beta release, and see if I can test this whole problem some more. It didn't crash on me today, although I had just rebooted this machine last night before I went to bed.... I will try to stress test it and see if I can get it to crash again to see if I can localize the problem. If anyone has any ideas of how to actually *track* the problem, let me know. If it were a VM problem, memory leak, etc... I could cron up a ps every hour or whatever to monitor the system, and a -v -p X'sPID to see how much it was bloating... etc. etc... It's not VM, though... I may grab the sources for the server and see if I can at least find out where it could generate a sigABRT from... but perhaps there is someone more familiar with the X sources that could shed some light on this. I know a bit about FreeBSD internals, but I've never even looked at the source for X. Later...... From owner-freebsd-current Wed Mar 26 21:31:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA05814 for current-outgoing; Wed, 26 Mar 1997 21:31:03 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA05806 for ; Wed, 26 Mar 1997 21:30:58 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id QAA11307; Thu, 27 Mar 1997 16:27:03 +1100 Date: Thu, 27 Mar 1997 16:27:03 +1100 From: Bruce Evans Message-Id: <199703270527.QAA11307@godzilla.zeta.org.au> To: mpp@freefall.freebsd.org, nate@mt.sri.com Subject: Re: dumpfs patch for review Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> fs_id[0] is a time_t value, and probably should be printed as such. >> is it the time that the file system was "randomized", either >> by newfs or fsirand. > >Ahh, OK. > >> fd_id[1] is a random number > >Ok, here's round two. It's still ugly. >Index: dumpfs.c >=================================================================== >RCS file: /home/CVS/src/sbin/dumpfs/dumpfs.c,v >retrieving revision 1.6 >diff -c -r1.6 dumpfs.c >*** dumpfs.c 1997/03/11 12:12:26 1.6 >--- dumpfs.c 1997/03/26 17:43:32 >*************** >*** 127,132 **** >--- 127,134 ---- > dev_bsize = afs.fs_fsize / fsbtodb(&afs, 1); > printf("magic\t%x\ttime\t%s", afs.fs_magic, > ctime(&afs.fs_time)); >+ printf("fsid\t%d\trndtime\t%s", >+ afs.fs_id[1], ctime((time_t *)&afs.fs_id[0])); ^^^^^^^^^^ Bogus cast. Just as wrong as the one in fsirand.c. >*************** >*** 143,153 **** > afs.fs_frag, afs.fs_fragshift, afs.fs_fsbtodb); > printf("cpg\t%d\tbpg\t%d\tfpg\t%d\tipg\t%d\n", > afs.fs_cpg, afs.fs_fpg / afs.fs_frag, afs.fs_fpg, afs.fs_ipg); >! printf("minfree\t%d%%\toptim\t%s\tmaxcontig %d\tmaxbpg\t%d\n", >! afs.fs_minfree, afs.fs_optim == FS_OPTSPACE ? "space" : "time", >! afs.fs_maxcontig, afs.fs_maxbpg); >! printf("rotdelay %dms\theadswitch %dus\ttrackseek %dus\trps\t%d\n", >! afs.fs_rotdelay, afs.fs_headswitch, afs.fs_trkseek, afs.fs_rps); > printf("ntrak\t%d\tnsect\t%d\tnpsect\t%d\tspc\t%d\n", > afs.fs_ntrak, afs.fs_nsect, afs.fs_npsect, afs.fs_spc); > printf("symlinklen %d\ttrackskew %d\tinterleave %d\tcontigsumsize %d\n", >--- 145,154 ---- > afs.fs_frag, afs.fs_fragshift, afs.fs_fsbtodb); > printf("cpg\t%d\tbpg\t%d\tfpg\t%d\tipg\t%d\n", > afs.fs_cpg, afs.fs_fpg / afs.fs_frag, afs.fs_fpg, afs.fs_ipg); >! printf("minfree\t%d%%\toptim\t%s\n", >! afs.fs_minfree, afs.fs_optim == FS_OPTSPACE ? "space" : "time"); >! printf("maxcontig %d\tmaxbpg\t%d\trotdelay %dms\trps\t%d\n", >! afs.fs_maxcontig, afs.fs_maxbpg, afs.fs_rotdelay, afs.fs_rps); > printf("ntrak\t%d\tnsect\t%d\tnpsect\t%d\tspc\t%d\n", > afs.fs_ntrak, afs.fs_nsect, afs.fs_npsect, afs.fs_spc); > printf("symlinklen %d\ttrackskew %d\tinterleave %d\tcontigsumsize %d\n", The minfree...maxbpg line shouldn't be changed. I'm now convinced that the old fields shouldn't have been reused. The above changes give wrong output on old and foreign file systems. Bruce From owner-freebsd-current Wed Mar 26 21:31:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA05847 for current-outgoing; Wed, 26 Mar 1997 21:31:58 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA05841 for ; Wed, 26 Mar 1997 21:31:54 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id GAA11989 for ; Thu, 27 Mar 1997 06:31:47 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id GAA01420 for freebsd-current@freebsd.org; Thu, 27 Mar 1997 06:31:26 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id BAA05160; Thu, 27 Mar 1997 01:18:57 +0100 (CET) Message-ID: <19970327011856.20649@keltia.freenix.fr> Date: Thu, 27 Mar 1997 01:18:56 +0100 From: Ollivier Robert To: freebsd-current@freebsd.org Subject: Re: Burning a 2.2.1R CDROM myself.. How? References: <921.859270807@time.cdrom.com> <19970326011239.16775@keltia.freenix.fr> <19970326092627.AV61167@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.65,1-4,10,14-18 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3153 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to J Wunsch: > You're not good in reading Makefiles, Ollivier. :-) Your opinion > is from older days, but the above quotation is from a current > release Makefile. ${FD} stands for ``FTP directory''. :-P I know that but just a bit later you have: # --==## Setup a suitable cdrom-area ##==-- # cdrom.1: mkdir -p ${CD_DISC1} ${CD_DISC2} ... echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC2}/cdrom.inf echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC1}/cdrom.inf So I'm not that blind :-) -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #41: Sun Mar 23 23:01:22 CET 1997 From owner-freebsd-current Wed Mar 26 21:35:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA06192 for current-outgoing; Wed, 26 Mar 1997 21:35:25 -0800 (PST) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA06173; Wed, 26 Mar 1997 21:35:13 -0800 (PST) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.4/8.7.3) id VAA12681; Wed, 26 Mar 1997 21:35:06 -0800 (PST) Date: Wed, 26 Mar 1997 21:35:06 -0800 (PST) Message-Id: <199703270535.VAA12681@vader.cs.berkeley.edu> To: phk@critter.dk.tfs.com CC: gibbs@freebsd.org, current@freebsd.org, se@freebsd.org In-reply-to: <12194.859380889@critter> (message from Poul-Henning Kamp on Wed, 26 Mar 1997 13:54:49 +0100) Subject: Re: RELENG_2_2, ahc and Atlas II, YES!! From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * If you do a * dd conv=swab < file_from_ftp.qntm.com.fup | strings | more * you will notice that the same file seems to apply for several kinds * of diskdrives... Hmm. That's interesting. I'll have back up the data and try that. ;) Satoshi From owner-freebsd-current Wed Mar 26 23:35:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA10260 for current-outgoing; Wed, 26 Mar 1997 23:35:22 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA10255 for ; Wed, 26 Mar 1997 23:35:19 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id IAA05298; Thu, 27 Mar 1997 08:16:33 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.5/8.8.2) id IAA00720; Thu, 27 Mar 1997 08:10:43 +0100 (MET) Message-ID: <19970327081043.13955@klemm.gtn.com> Date: Thu, 27 Mar 1997 08:10:43 +0100 From: Andreas Klemm To: "Justin T. Gibbs" Cc: Kachun Lee , freebsd-current@freebsd.org Subject: Re: ahc crashes References: <19970326201659.02877@klemm.gtn.com> <199703261954.MAA29414@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 In-Reply-To: <199703261954.MAA29414@pluto.plutotech.com>; from Justin T. Gibbs on Wed, Mar 26, 1997 at 12:55:06PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, Mar 26, 1997 at 12:55:06PM -0700, Justin T. Gibbs wrote: > >First of all congradulations, you are making big progress ! > > What model is the drive you're dumping off of? It certainly seems > to have problems with tagged queuing and it may be that what you really > want to do is reduce the number of openings from 8 down to 3 in i386/scsi/ > aic7xxx.c. It may also be that you need a firmware update on that drive > in order to properly do tagged queueing. > > Se my other post to current about how tagged queueing can still fail if a > device returns QUEUE FULL status. You seem to be right ... reducing the tags to 3 brings more stability, but on the long run the machine also hangs ... Although I reduced the tags to 3 the following message appears at the beginning of the dump: sd0: Tagged openings reduced to 3 Then this after about 30 Minutes: ahc0: WARNING no command for scb 4 (cmdcmplt) QOUTCNT == 1 And this seems to be a hardware error (defective sector) or ? sd1: data overrun of 16715782 bytes detected in Data-In phase. Tag == 0x0. Forcing a retry. sd1: Have seen Data Phase. Length = 12288. NumSGs = 3. sg[0] - Addr 0x2cbc000 : Length 4096 sg[1] - Addr 0x2c75000 : Length 4096 sg[2] - Addr 0x2cfc000 : Length 4096 swap_pager: I/O error - pagein failed; blkno 25824, size 12288, error 5 vm_fault: pager input (probably hardware) error, PID 687 failure ahc0: WARNING no command for scb 0 (cmdcmplt) QOUTCNT == 1 Mar 27 05:22:04 klemm /kernel: pid 687 (dump), uid 0: exited on signal 11 Mar 27 05:22:04 klemm /kernel: pid 685 (dump), uid 0: exited on signal 11 Mar 27 05:22:04 klemm /kernel: pid 688 (dump), uid 0: exited on signal 11 Mar 27 05:22:04 klemm /kernel: pid 686 (dump), uid 0: exited on signal 11 Mar 27 05:22:04 klemm /kernel: pid 684 (dump), uid 0: exited on signal 11 Mar 27 05:22:04 klemm /kernel: pid 630 (sh), uid 0: exited on signal 11 (core dumped) This was my patch: RCS file: /local/CVS/src/sys/i386/scsi/aic7xxx.c,v retrieving revision 1.109 diff -u -r1.109 aic7xxx.c --- aic7xxx.c 1997/03/24 17:42:25 1.109 +++ aic7xxx.c 1997/03/27 04:08:21 @@ -1892,7 +1892,8 @@ if (ahc->scb_data->maxhscbs >= 16 || (ahc->flags & AHC_PAGESCBS)) { /* Default to 8 tags */ - xs->sc_link->opennings += 13; + /* XXX xs->sc_link->opennings += 13; */ + xs->sc_link->opennings = 3; } else { /* * Default to 4 tags on whimpy @@ -1902,7 +1903,8 @@ * slots. We should really have a better * way of providing fairness. */ - xs->sc_link->opennings += 2; + /* XXX xs->sc_link->opennings += 2; */ + xs->sc_link->opennings = 3; } } } And I asked IBM via e-mail if I can get a firmware update ... -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Wed Mar 26 23:52:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA11244 for current-outgoing; Wed, 26 Mar 1997 23:52:32 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA11239 for ; Wed, 26 Mar 1997 23:52:26 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA06123 for freebsd-current@freebsd.org; Thu, 27 Mar 1997 08:52:24 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA16796; Thu, 27 Mar 1997 08:41:57 +0100 (MET) Message-ID: <19970327084157.XU04429@uriah.heep.sax.de> Date: Thu, 27 Mar 1997 08:41:57 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org Subject: Re: Burning a 2.2.1R CDROM myself.. How? References: <921.859270807@time.cdrom.com> <19970326011239.16775@keltia.freenix.fr> <19970326092627.AV61167@uriah.heep.sax.de> <19970327011856.20649@keltia.freenix.fr> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970327011856.20649@keltia.freenix.fr>; from Ollivier Robert on Mar 27, 1997 01:18:56 +0100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > > You're not good in reading Makefiles, Ollivier. :-) Your opinion > > is from older days, but the above quotation is from a current > > release Makefile. ${FD} stands for ``FTP directory''. :-P > > I know that but just a bit later you have: > echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC2}/cdrom.inf > echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC1}/cdrom.inf Yes, this was the classic case. In order to help people who wanna make their own CD-R, i've also included it into the ${FD} case, so it's no longer necessary to copy this from somewhere else. All one needs by now is to copy the entire FTP subdirectory verbatim. (If you accidentally leave the 2.2-RELEASE in front, sysinstall can almost handle this case, too, except for the cdrom.inf file. But unlike with previous versions, you can now safely ignore the cdrom.inf complaint.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Mar 27 00:27:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA12548 for current-outgoing; Thu, 27 Mar 1997 00:27:00 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA12536 for ; Thu, 27 Mar 1997 00:26:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id AAA19418; Thu, 27 Mar 1997 00:26:35 -0800 (PST) Message-Id: <199703270826.AAA19418@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Doug Russell cc: Terry Lambert , David Dawes , joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org Subject: Re: SIGABRTs killing X In-reply-to: Your message of "Wed, 26 Mar 1997 22:08:10 GMT." From: David Greenman Reply-To: dg@root.com Date: Thu, 27 Mar 1997 00:26:35 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >previous 3C509TP. The last change before that was to put in 4x 8 meg EDO >45ns SIMMs so I could turn up the memory speed knobbies in the CMOS to >full blast. Ah. Try setting the memory speed one notch slower than full blast. This appears to be a memory timing problem (or just bad RAM?). The most common case of the X server getting a SIGABRT is via another unexpected signal (usually SIGSEGV, SIGBUS, or SIGILL) - the server calls abort() in this case which then sends itself a signal in order to cause the system to generate a core file. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Mar 27 00:42:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA14212 for current-outgoing; Thu, 27 Mar 1997 00:42:23 -0800 (PST) Received: from critter.dk.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA14180; Thu, 27 Mar 1997 00:42:12 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id IAA13754; Thu, 27 Mar 1997 08:15:41 +0100 (CET) To: asami@vader.cs.berkeley.edu (Satoshi Asami) cc: gibbs@FreeBSD.ORG, current@FreeBSD.ORG, se@FreeBSD.ORG Subject: Re: RELENG_2_2, ahc and Atlas II, YES!! In-reply-to: Your message of "Wed, 26 Mar 1997 21:35:06 PST." <199703270535.VAA12681@vader.cs.berkeley.edu> Date: Thu, 27 Mar 1997 08:15:41 +0100 Message-ID: <13752.859446941@critter> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199703270535.VAA12681@vader.cs.berkeley.edu>, Satoshi Asami writes: > * If you do a > * dd conv=swab < file_from_ftp.qntm.com.fup | strings | more > * you will notice that the same file seems to apply for several kinds > * of diskdrives... > >Hmm. That's interesting. I'll have back up the data and try that. ;) I tried it, but it complained, and since I didn't have a backup I didn't want to try it out like that... Your results will be most interesting to me... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Thu Mar 27 01:14:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA00644 for current-outgoing; Thu, 27 Mar 1997 01:14:30 -0800 (PST) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA00634; Thu, 27 Mar 1997 01:14:23 -0800 (PST) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.4/8.7.3) id BAA13058; Thu, 27 Mar 1997 01:14:16 -0800 (PST) Date: Thu, 27 Mar 1997 01:14:16 -0800 (PST) Message-Id: <199703270914.BAA13058@vader.cs.berkeley.edu> To: phk@critter.dk.tfs.com CC: gibbs@FreeBSD.ORG, current@FreeBSD.ORG, se@FreeBSD.ORG In-reply-to: <13752.859446941@critter> (message from Poul-Henning Kamp on Thu, 27 Mar 1997 08:15:41 +0100) Subject: Re: RELENG_2_2, ahc and Atlas II, YES!! From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * I tried it, but it complained, and since I didn't have a backup I didn't * want to try it out like that... Your results will be most interesting * to me... I beg your pardon? I thought you said you were running LXY4. How did you get that then? What was the original revision, how did you upgrade and to what, etc.? Satoshi From owner-freebsd-current Thu Mar 27 01:20:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA00963 for current-outgoing; Thu, 27 Mar 1997 01:20:56 -0800 (PST) Received: from critter.dk.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA00953; Thu, 27 Mar 1997 01:20:45 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id KAA00324; Thu, 27 Mar 1997 10:19:51 +0100 (CET) To: asami@vader.cs.berkeley.edu (Satoshi Asami) cc: gibbs@FreeBSD.ORG, current@FreeBSD.ORG, se@FreeBSD.ORG Subject: Re: RELENG_2_2, ahc and Atlas II, YES!! In-reply-to: Your message of "Thu, 27 Mar 1997 01:14:16 PST." <199703270914.BAA13058@vader.cs.berkeley.edu> Date: Thu, 27 Mar 1997 10:19:50 +0100 Message-ID: <322.859454390@critter> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199703270914.BAA13058@vader.cs.berkeley.edu>, Satoshi Asami writes: > * I tried it, but it complained, and since I didn't have a backup I didn't > * want to try it out like that... Your results will be most interesting > * to me... > >I beg your pardon? I thought you said you were running LXY4. How did >you get that then? What was the original revision, how did you >upgrade and to what, etc.? It's the original revision for these two disks. I have another pair running LXY1 that's the ones I tried to upgrade, but abandoned when I ran out of courage :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Thu Mar 27 01:51:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA03136 for current-outgoing; Thu, 27 Mar 1997 01:51:24 -0800 (PST) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA03120; Thu, 27 Mar 1997 01:51:16 -0800 (PST) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.4/8.7.3) id BAA13116; Thu, 27 Mar 1997 01:51:14 -0800 (PST) Date: Thu, 27 Mar 1997 01:51:14 -0800 (PST) Message-Id: <199703270951.BAA13116@vader.cs.berkeley.edu> To: phk@critter.dk.tfs.com CC: gibbs@FreeBSD.ORG, current@FreeBSD.ORG, se@FreeBSD.ORG In-reply-to: <322.859454390@critter> (message from Poul-Henning Kamp on Thu, 27 Mar 1997 10:19:50 +0100) Subject: Re: RELENG_2_2, ahc and Atlas II, YES!! From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * It's the original revision for these two disks. I have another pair * running LXY1 that's the ones I tried to upgrade, but abandoned when * I ran out of courage :-) Ok. So you have two LXY1's and two LXY4's. And they both run fine with 2940/3940UW and the latest driver? Satoshi From owner-freebsd-current Thu Mar 27 01:58:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA03881 for current-outgoing; Thu, 27 Mar 1997 01:58:50 -0800 (PST) Received: from critter.dk.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA03874; Thu, 27 Mar 1997 01:58:38 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id KAA00390; Thu, 27 Mar 1997 10:57:45 +0100 (CET) To: asami@vader.cs.berkeley.edu (Satoshi Asami) cc: gibbs@FreeBSD.ORG, current@FreeBSD.ORG, se@FreeBSD.ORG Subject: Re: RELENG_2_2, ahc and Atlas II, YES!! In-reply-to: Your message of "Thu, 27 Mar 1997 01:51:14 PST." <199703270951.BAA13116@vader.cs.berkeley.edu> Date: Thu, 27 Mar 1997 10:57:44 +0100 Message-ID: <388.859456664@critter> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199703270951.BAA13116@vader.cs.berkeley.edu>, Satoshi Asami writes: > * It's the original revision for these two disks. I have another pair > * running LXY1 that's the ones I tried to upgrade, but abandoned when > * I ran out of courage :-) > >Ok. So you have two LXY1's and two LXY4's. And they both run fine >with 2940/3940UW and the latest driver? The LXY1's are in a almost-something-like-2.2-with-some-version-of-SMP-on-\ a-old-DEC-neptune-chipset-machine The LXY4's are on a P6/200 Asus P6NP5 which is running RELENG_2_2, and which now seems to be ok. As you can see the scientific value of the LXY1's running fine isn't that great at this time. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Thu Mar 27 02:16:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA04963 for current-outgoing; Thu, 27 Mar 1997 02:16:38 -0800 (PST) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA04950; Thu, 27 Mar 1997 02:16:27 -0800 (PST) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.4/8.7.3) id CAA13166; Thu, 27 Mar 1997 02:16:20 -0800 (PST) Date: Thu, 27 Mar 1997 02:16:20 -0800 (PST) Message-Id: <199703271016.CAA13166@vader.cs.berkeley.edu> To: phk@critter.dk.tfs.com CC: gibbs@FreeBSD.ORG, current@FreeBSD.ORG, se@FreeBSD.ORG In-reply-to: <388.859456664@critter> (message from Poul-Henning Kamp on Thu, 27 Mar 1997 10:57:44 +0100) Subject: Re: RELENG_2_2, ahc and Atlas II, YES!! From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * The LXY4's are on a P6/200 Asus P6NP5 which is running RELENG_2_2, and * which now seems to be ok. That is cool. BTW, you have the same MB/CPU combination as I do. :) Satoshi From owner-freebsd-current Thu Mar 27 09:50:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA01894 for current-outgoing; Thu, 27 Mar 1997 09:50:25 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01862 for ; Thu, 27 Mar 1997 09:50:19 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id HAA04449 for ; Thu, 27 Mar 1997 07:40:22 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id IAA10670; Thu, 27 Mar 1997 08:36:24 -0700 (MST) Date: Thu, 27 Mar 1997 08:36:24 -0700 (MST) Message-Id: <199703271536.IAA10670@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bruce Evans Cc: mpp@freefall.freebsd.org, nate@mt.sri.com, current@freebsd.org Subject: Re: dumpfs patch for review In-Reply-To: <199703270527.QAA11307@godzilla.zeta.org.au> References: <199703270527.QAA11307@godzilla.zeta.org.au> X-Mailer: VM 6.22 under 19.14 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans writes: > >> fs_id[0] is a time_t value, and probably should be printed as such. > >> is it the time that the file system was "randomized", either > >> by newfs or fsirand. > > > >Ahh, OK. > > > >> fd_id[1] is a random number > > > >Ok, here's round two. > > It's still ugly. It's better than nothing... > >=================================================================== > >RCS file: /home/CVS/src/sbin/dumpfs/dumpfs.c,v > >retrieving revision 1.6 > >diff -c -r1.6 dumpfs.c > >*** dumpfs.c 1997/03/11 12:12:26 1.6 > >--- dumpfs.c 1997/03/26 17:43:32 > >*************** > >*** 127,132 **** > >--- 127,134 ---- > > dev_bsize = afs.fs_fsize / fsbtodb(&afs, 1); > > printf("magic\t%x\ttime\t%s", afs.fs_magic, > > ctime(&afs.fs_time)); > >+ printf("fsid\t%d\trndtime\t%s", > >+ afs.fs_id[1], ctime((time_t *)&afs.fs_id[0])); > ^^^^^^^^^^ > > Bogus cast. Just as wrong as the one in fsirand.c. Since fs_id[0] is declared as int_32, I have to cast it to time_t in order for it to be 'right' (according to fsirand). > The minfree...maxbpg line shouldn't be changed. Why not change them? We had to change something? > I'm now convinced that the old fields shouldn't have been reused. The above > changes give wrong output on old and foreign file systems. Yep, but in order to remain compatible with the other *BSd's, we must either convince them to use the other 'unused' fields. In any case, are you going to come up with a better fix, cause if not then this solution is better than nothing (and the issues are formatting of the output, not functional issues.) Having a broken build tree for 3 days seems silly. Nate From owner-freebsd-current Thu Mar 27 09:55:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA03228 for current-outgoing; Thu, 27 Mar 1997 09:55:03 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA03175 for ; Thu, 27 Mar 1997 09:54:55 -0800 (PST) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id EAA03552 for ; Thu, 27 Mar 1997 04:41:01 -0800 (PST) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.4/8.8.4) id EAA22329; Thu, 27 Mar 1997 04:39:47 -0800 (PST) Message-ID: <19970327043947.41187@hydrogen.nike.efn.org> Date: Thu, 27 Mar 1997 04:39:47 -0800 From: John-Mark Gurney To: FreeBSD Current Subject: problem with tput being to strict? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2-960801-SNAP i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hello... it seems that tput is being a bit to strict on it's interpetation of escape characters... if I run tput init with TERM=tek4107... I will get this error message: tput: unknown % escape `!' for capability `is' if I write my own program to just dump the is entry out it works great... should I add a "debug" flag to tput that will enable the extended error checking? should I remove the error checking all together? thanks for you input... ttyl... -- John-Mark Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix) From owner-freebsd-current Thu Mar 27 09:55:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA03378 for current-outgoing; Thu, 27 Mar 1997 09:55:32 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA02712; Thu, 27 Mar 1997 09:53:17 -0800 (PST) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id FAA03865 ; Thu, 27 Mar 1997 05:57:18 -0800 (PST) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id HAA10945; Thu, 27 Mar 1997 07:55:57 -0600 (CST) X-Sender: rkw@shrimp.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 27 Mar 1997 07:48:27 -0600 To: ctm-announce@freebsd.org, current@freebsd.org From: Richard Wackerbarth Subject: 2.2.1 CTM baseline Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In an effort to reduce the redundant distribution of source baselines, the CTM delta src-2.2.0216.gz brings this update stream to match the 2.2.1 RELEASE of the sources for FreeBSD. If you need to start from a baseline, you may do so by obtaining the src tarballs from the 2.2.1 CD or an ftp server. You will then need to extract them into your tree and add one small file. The instructions for this are in the src-2.2-CTM-README file. >From that point, you will be able to track the source changes by applying deltas starting with src-2.2.0217.gz From owner-freebsd-current Thu Mar 27 10:10:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA04018 for current-outgoing; Thu, 27 Mar 1997 09:58:00 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA03972 for ; Thu, 27 Mar 1997 09:57:52 -0800 (PST) Received: from melbourne.dialix.com.au (seeuucp@melbourne.dialix.com.au [203.12.2.24]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id CAA03030 for ; Thu, 27 Mar 1997 02:36:45 -0800 (PST) Received: (from seeuucp@localhost) by melbourne.dialix.com.au with UUCP id VAA15302; Thu, 27 Mar 1997 21:34:13 +1100 (EST) X-Authentication-Warning: melbourne.dialix.com.au: seeuucp set sender to mark@seeware.DIALix.oz.au using -f Received: from putte.seeware.DIALix.oz.au (putte.seeware.DIALix.oz.au [10.0.0.1]) by doorway.seeware.DIALix.oz.au (8.8.5/8.7.3) with ESMTP id VAA16533; Thu, 27 Mar 1997 21:10:34 +1100 (EST) From: Mark Hannon Received: (from mark@localhost) by putte.seeware.DIALix.oz.au (8.8.5/8.7.3) id VAA00461; Thu, 27 Mar 1997 21:10:34 +1100 (EST) Date: Thu, 27 Mar 1997 21:10:34 +1100 (EST) Message-Id: <199703271010.VAA00461@putte.seeware.DIALix.oz.au> To: joerg_wunsch@uriah.heep.sax.de, current@freebsd.org, deischen@iworks.InterWorks.org Subject: SOLVED: 2.2-RELEASE, dtmail stopped working Cc: support@xinside.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: 3yLyojojMQkAV60m/HkB0g== Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, A week ago I reported a problem with Xinside's dtmail client not starting under 2.2-RELEASE. The same program had worked under 2.1.[567] and 2.2-GAMMA. The error message was "Mailer has not been properly installed and cannot be run because the execution group is incorrectly set" dtmail is sgid bin and the mail spool permissions are set to 775. After some hints from Joerg I managed to trace the execution on both a 2.2 and 2.1.7 kernel (this required the removal of a check which dissallows ktrace in an suid/sgid process). Upon examination I saw that the failure point in 2.2 was in a failing call to the setgid call. The call failed with a permission error in 2.2 but not in 2.1.7. Further digging showed that /sys/sys/unistd.h has changed in 2.2 and says: #ifdef _NOT_AVAILABLE #define _POSIX_SAVED_IDS /* saved set-user-ID and set-group-ID */ #endif The code in /sys/kern/kern_prot.c checks for _POSIX_SAVED_IDS before including the code to allow setgid. I could not find a #def _NOT_AVAILABLE in the include files. A recompile of a new kernel with the unistd.h file from 2.2-GAMMA has solved my problems. I have submitted a PR on this. Regards/Mark From owner-freebsd-current Thu Mar 27 11:55:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA15574 for current-outgoing; Thu, 27 Mar 1997 11:55:40 -0800 (PST) Received: from hobbes.saturn-tech.com (drussell@[207.229.19.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA15563 for ; Thu, 27 Mar 1997 11:55:36 -0800 (PST) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id MAA25946; Thu, 27 Mar 1997 12:53:02 -0700 (MST) Date: Thu, 27 Mar 1997 12:53:02 -0700 (MST) From: Doug Russell To: David Greenman cc: Terry Lambert , David Dawes , joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org Subject: Re: SIGABRTs killing X In-Reply-To: <199703270826.AAA19418@root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 27 Mar 1997, David Greenman wrote: > Ah. Try setting the memory speed one notch slower than full blast. This > appears to be a memory timing problem (or just bad RAM?). The most common > case of the X server getting a SIGABRT is via another unexpected signal > (usually SIGSEGV, SIGBUS, or SIGILL) - the server calls abort() in this > case which then sends itself a signal in order to cause the system to > generate a core file. I don't remember if I left it at full tilt or not. I will slow it down a bit and see if it still does it. On the other hand, making it to it at all seems to be a little tricky. It did it twice within two days (about 24 hours apart), and then hasn't done it since. 45ns EDO RAM should be able to run just fine with everything turned all the way up, so I may try re-seating the SIMMs, and testing the RAM (or swapping it for other SIMMs) if it keeps doing it. Later...... From owner-freebsd-current Thu Mar 27 12:21:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA18313 for current-outgoing; Thu, 27 Mar 1997 12:21:28 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA18307 for ; Thu, 27 Mar 1997 12:21:21 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA12352; Thu, 27 Mar 1997 21:21:17 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA18445; Thu, 27 Mar 1997 21:15:24 +0100 (MET) Message-ID: <19970327211524.IM61026@uriah.heep.sax.de> Date: Thu, 27 Mar 1997 21:15:24 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org (FreeBSD Current) Cc: gurney_j@resnet.uoregon.edu (John-Mark Gurney) Subject: Re: problem with tput being to strict? References: <19970327043947.41187@hydrogen.nike.efn.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970327043947.41187@hydrogen.nike.efn.org>; from John-Mark Gurney on Mar 27, 1997 04:39:47 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As John-Mark Gurney wrote: > hello... it seems that tput is being a bit to strict on it's interpetation > of escape characters... if I run tput init with TERM=tek4107... I will > get this error message: > tput: unknown % escape `!' for capability `is' The tek4107 `is' entry is buggy. `%' is a special character inside a string capability (see the `cm' capability to learn what it's good for). The %'s should be replaced by \045. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Mar 27 12:41:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA20200 for current-outgoing; Thu, 27 Mar 1997 12:41:49 -0800 (PST) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA20187 for ; Thu, 27 Mar 1997 12:41:44 -0800 (PST) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id MAA08234; Thu, 27 Mar 1997 12:45:08 -0800 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id PAA16671; Thu, 27 Mar 1997 15:41:10 -0500 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id PAA08820; Thu, 27 Mar 1997 15:41:09 -0500 Received: (from alk@localhost) by compound.east.sun.com (8.8.5/8.7.3) id GAA00795; Thu, 27 Mar 1997 06:50:52 GMT Date: Thu, 27 Mar 1997 06:50:52 GMT Reply-To: alk@East.Sun.COM Message-Id: <199703270650.GAA00795@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn To: asami@vader.cs.berkeley.edu Cc: current@freebsd.org Subject: Re: Suggested fetchmail port addition (was: Re: Fetchmail nolonger working) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quoth Satoshi Asami on Wed, 26 March: : * Speaking of which, here is a local MDA I use in order that I do not : * have to run a local sendmail. Unless I am overlooking equivalent : * functionality already hidden somewhere in the base OS, it might be : * useful to include this in the fetchmail port. ... : I use : : server foo protocol pop3 fetchall password ******** mda "/usr/libexec/mail.local %s" : *That* is what I was overlooking. I hate it when that happens:-) From owner-freebsd-current Thu Mar 27 14:32:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA29182 for current-outgoing; Thu, 27 Mar 1997 14:32:42 -0800 (PST) Received: from hydrogen.nike.efn.org (metriclient-3.uoregon.edu [128.223.172.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA29165 for ; Thu, 27 Mar 1997 14:32:25 -0800 (PST) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.4/8.8.4) id OAA25314; Thu, 27 Mar 1997 14:32:11 -0800 (PST) Message-ID: <19970327143210.04552@hydrogen.nike.efn.org> Date: Thu, 27 Mar 1997 14:32:10 -0800 From: John-Mark Gurney To: FreeBSD Current Cc: Joerg Wunsch Subject: Re: problem with tput being to strict? References: <19970327043947.41187@hydrogen.nike.efn.org> <19970327211524.IM61026@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 In-Reply-To: <19970327211524.IM61026@uriah.heep.sax.de>; from J Wunsch on Thu, Mar 27, 1997 at 09:15:24PM +0100 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2-960801-SNAP i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch scribbled this message on Mar 27: > As John-Mark Gurney wrote: > > > hello... it seems that tput is being a bit to strict on it's interpetation > > of escape characters... if I run tput init with TERM=tek4107... I will > > get this error message: > > tput: unknown % escape `!' for capability `is' > > The tek4107 `is' entry is buggy. `%' is a special character inside a > string capability (see the `cm' capability to learn what it's good > for). The %'s should be replaced by \045. not much... it still breaks... see: Script started on Thu Mar 27 14:26:36 1997 hydrogen,ttyp0,/tmp/gated/gated-R3_6Alpha_2/src,501$echo $TERMCAP tek4107|tek4207|4107|4207:ti=\E[?6l\E[H\E[J:te=\E[?6h\E\045\0410\ELBP0\E\045\0411\E[32;1f:is=\E\045\0410\ELBP0\E\045\0411\E[H\E[2g\EH\E[8C\EH\E[8C\EH\E[8C\EH\E[8C\EH\E[8C\EH\E[8C\EH\E[8C\EH\E[8C\EH\E[8C\EH\E[J:li#32:do=^J:al=3\E[L:xn:am:le=^H:bs:cd=\E[J:ce=5\E[K:cl=156\E[H\E[J:cm=\E[%i%d;%dH:co#80:dc=4\E[P:dl=3\E[M:ho=\E[H:ic=4\E[@:md=\E[1m:mr=\E[7m:mb=\E[5m:me=\E[m:ku=\EM:kd=\ED:kl=\E[D:kr=\E[C:kh=\E[H:ul:pt:bw:bt=\E[Z:mi:nd=\E[C:se=\E[m:so=\E[7m:ue=\E[m:us=\E[4m:up=\EM: hydrogen,ttyp0,/tmp/gated/gated-R3_6Alpha_2/src,502$tput init tput: unknown % escape `!' for capability `is' hydrogen,ttyp0,/tmp/gated/gated-R3_6Alpha_2/src,503$exit Script done on Thu Mar 27 14:26:50 1997 I still contend it's because tput is to strict... you see... tgetstr that is used to obtain the above screen returns the screen with all the chars as their proper ones... i.e. \E is really ESC... but then it later scans though the string searching for replacable parameters... it finds a %.. it looks at what is following... it's a !... that isn't on of the types of replacable chars.. and bails... I guess the REAL fix would be to replace all % with %%... but then handling the code to "fix" this problem would be REALLY ugly... -- John-Mark Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix) From owner-freebsd-current Thu Mar 27 15:21:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA02126 for current-outgoing; Thu, 27 Mar 1997 15:21:47 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA02111 for ; Thu, 27 Mar 1997 15:21:40 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA14374 for freebsd-current@freebsd.org; Fri, 28 Mar 1997 00:21:39 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id AAA19183; Fri, 28 Mar 1997 00:02:29 +0100 (MET) Message-ID: <19970328000229.QN02024@uriah.heep.sax.de> Date: Fri, 28 Mar 1997 00:02:29 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org (FreeBSD Current) Subject: Re: problem with tput being to strict? References: <19970327043947.41187@hydrogen.nike.efn.org> <19970327211524.IM61026@uriah.heep.sax.de> <19970327143210.04552@hydrogen.nike.efn.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970327143210.04552@hydrogen.nike.efn.org>; from John-Mark Gurney on Mar 27, 1997 14:32:10 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As John-Mark Gurney wrote: > > The tek4107 `is' entry is buggy. `%' is a special character inside a > > string capability (see the `cm' capability to learn what it's good > > for). The %'s should be replaced by \045. > > not much... it still breaks... see: *barf* -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Mar 27 16:10:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA05294 for current-outgoing; Thu, 27 Mar 1997 16:10:25 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA05287 for ; Thu, 27 Mar 1997 16:10:21 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id LAA10496; Fri, 28 Mar 1997 11:02:10 +1100 Date: Fri, 28 Mar 1997 11:02:10 +1100 From: Bruce Evans Message-Id: <199703280002.LAA10496@godzilla.zeta.org.au> To: bde@zeta.org.au, nate@mt.sri.com Subject: Re: dumpfs patch for review Cc: current@freebsd.org, mpp@freefall.freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> It's still ugly. > >It's better than nothing... It's worse than not printing the new fields. >> >+ afs.fs_id[1], ctime((time_t *)&afs.fs_id[0])); >> ^^^^^^^^^^ >> >> Bogus cast. Just as wrong as the one in fsirand.c. > >Since fs_id[0] is declared as int_32, I have to cast it to time_t in >order for it to be 'right' (according to fsirand). As I said, fsirand is wrong too. It converts the pointer, not the object. If time_t is 64 bits then the pointer would probably point to 32 bits of data and 32 bits of garbage. >> The minfree...maxbpg line shouldn't be changed. > >Why not change them? We had to change something? Nothing was broken in that line. >> I'm now convinced that the old fields shouldn't have been reused. The above >> changes give wrong output on old and foreign file systems. > >Yep, but in order to remain compatible with the other *BSd's, we must >either convince them to use the other 'unused' fields. That would be easier than rewriting history :-). Bruce From owner-freebsd-current Thu Mar 27 16:36:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA07381 for current-outgoing; Thu, 27 Mar 1997 16:36:07 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA07363 for ; Thu, 27 Mar 1997 16:35:59 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id RAA14046; Thu, 27 Mar 1997 17:35:52 -0700 (MST) Date: Thu, 27 Mar 1997 17:35:52 -0700 (MST) Message-Id: <199703280035.RAA14046@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bruce Evans Cc: nate@mt.sri.com, current@freebsd.org, mpp@freefall.freebsd.org Subject: Re: dumpfs patch for review In-Reply-To: <199703280002.LAA10496@godzilla.zeta.org.au> References: <199703280002.LAA10496@godzilla.zeta.org.au> X-Mailer: VM 6.22 under 19.14 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> It's still ugly. > > > >It's better than nothing... > > It's worse than not printing the new fields. I beg to differ. > >> >+ afs.fs_id[1], ctime((time_t *)&afs.fs_id[0])); > >> ^^^^^^^^^^ > >> > >> Bogus cast. Just as wrong as the one in fsirand.c. > > > >Since fs_id[0] is declared as int_32, I have to cast it to time_t in > >order for it to be 'right' (according to fsirand). > > As I said, fsirand is wrong too. It converts the pointer, not the object. > If time_t is 64 bits then the pointer would probably point to 32 bits of > data and 32 bits of garbage. But it's not. Do you propose changing the definition in /sys/fs/ffs/fs.h? > >> The minfree...maxbpg line shouldn't be changed. > > > >Why not change them? We had to change something? > > Nothing was broken in that line. To make a cake, you gotta break a few eggs. :) Nate From owner-freebsd-current Thu Mar 27 17:07:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA09227 for current-outgoing; Thu, 27 Mar 1997 17:07:00 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA09218 for ; Thu, 27 Mar 1997 17:06:54 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id MAA12659; Fri, 28 Mar 1997 12:04:25 +1100 Date: Fri, 28 Mar 1997 12:04:25 +1100 From: Bruce Evans Message-Id: <199703280104.MAA12659@godzilla.zeta.org.au> To: bde@zeta.org.au, nate@mt.sri.com Subject: Re: dumpfs patch for review Cc: current@freebsd.org, mpp@freefall.freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >> >+ afs.fs_id[1], ctime((time_t *)&afs.fs_id[0])); >> >> ^^^^^^^^^^ >> >> >> >> Bogus cast. Just as wrong as the one in fsirand.c. >> > >> >Since fs_id[0] is declared as int_32, I have to cast it to time_t in >> >order for it to be 'right' (according to fsirand). >> >> As I said, fsirand is wrong too. It converts the pointer, not the object. >> If time_t is 64 bits then the pointer would probably point to 32 bits of >> data and 32 bits of garbage. > >But it's not. Do you propose changing the definition in >/sys/fs/ffs/fs.h? time_t (actually _BSD_TIME_T_) is defined in . It has nothing to do with fs.h. It is machine-dependent. >> >> The minfree...maxbpg line shouldn't be changed. >> > >> >Why not change them? We had to change something? >> >> Nothing was broken in that line. > >To make a cake, you gotta break a few eggs. :) Not in this case. The only reason to change it would be to make the output look pretty. In the non-broken version, there are 4 fields on the minfree...maxbpg line and 4 fields on the line that needs to be changed. The changed fields are harder to print than the old fields, because they are usually wider, but not always (the random value takes 11 characters for -2^31 and 1 character for 0), so some caclulations would be required to print the correct number of tabs to get the columns to line up. Moving the time value to a line by itself creates other ugliness. It is disconnected from the random value. Bruce From owner-freebsd-current Thu Mar 27 18:47:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA13807 for current-outgoing; Thu, 27 Mar 1997 18:47:35 -0800 (PST) Received: from Pkrw.tcn.net (Pkrw.tcn.net [199.166.4.58]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA13802 for ; Thu, 27 Mar 1997 18:47:32 -0800 (PST) Received: from localhost (krw@localhost) by Pkrw.tcn.net (8.8.5/8.8.5) with SMTP id VAA00257 for ; Thu, 27 Mar 1997 21:50:58 -0500 (EST) Date: Thu, 27 Mar 1997 21:50:57 -0500 (EST) From: "Kenneth R. Westerback" To: freebsd-current@freebsd.org Subject: src-2.2.216? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Did I miss something? I got 215 and 217 and 218 in the mail as usual, but I didn't get 216. Is it lost or do I just ignore it and cvs 217/218 on top of my 215 tree? I checked ftp.freebsd.org/pub/FreeBSD/FreeBSD.2-2/ctm but no luck there either, 215, 217, 218 only. I saw the announcement about 216 being the ctm delta that sync'ed ctm and 2.2.10-RELEASE but what about us that have just been applying the ctm deltas over 2.2R? ---- Ken From owner-freebsd-current Thu Mar 27 19:00:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA14430 for current-outgoing; Thu, 27 Mar 1997 19:00:53 -0800 (PST) Received: from Pkrw.tcn.net (Pkrw.tcn.net [199.166.4.58]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA14425 for ; Thu, 27 Mar 1997 19:00:47 -0800 (PST) Received: from localhost (krw@localhost) by Pkrw.tcn.net (8.8.5/8.8.5) with SMTP id WAA00281 for ; Thu, 27 Mar 1997 22:04:13 -0500 (EST) Date: Thu, 27 Mar 1997 22:03:51 -0500 (EST) From: "Kenneth R. Westerback" To: freebsd-current@freebsd.org Subject: src-2.2-CTM-README typo Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Pretty self explanatory ... 36c36,37 < ***** For 2.2.1 RELEASE, you will start with src-2.2.0210.gz --- > ***** For 2.2.0 RELEASE, you will start with src-2.2.0210.gz > ***** For 2.2.1 RELEASE, you will start with src-2.2.0217.gz ---- Ken (still looking for 216!) From owner-freebsd-current Thu Mar 27 21:06:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA19634 for current-outgoing; Thu, 27 Mar 1997 21:06:09 -0800 (PST) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA19627 for ; Thu, 27 Mar 1997 21:06:02 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id QAA02336 for current@freebsd.org; Fri, 28 Mar 1997 16:05:44 +1100 (EST) From: David Dawes Message-Id: <199703280505.QAA02336@rf900.physics.usyd.edu.au> Subject: Re: dumpfs patch for review In-Reply-To: <199703280002.LAA10496@godzilla.zeta.org.au> from Bruce Evans at "Mar 28, 97 11:02:10 am" To: current@freebsd.org Date: Fri, 28 Mar 1997 16:05:43 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>> It's still ugly. >> >>It's better than nothing... > >It's worse than not printing the new fields. > >>> >+ afs.fs_id[1], ctime((time_t *)&afs.fs_id[0])); >>> ^^^^^^^^^^ >>> >>> Bogus cast. Just as wrong as the one in fsirand.c. >> >>Since fs_id[0] is declared as int_32, I have to cast it to time_t in >>order for it to be 'right' (according to fsirand). Sort of related: building dumpfs on RELENG_2_2 is broken because it hasn't been updated for the ffs.h changes. It still has references to the old fields. David From owner-freebsd-current Fri Mar 28 01:50:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA00577 for current-outgoing; Fri, 28 Mar 1997 01:50:55 -0800 (PST) Received: from mail.MCESTATE.COM (vince@mail.MCESTATE.COM [207.211.200.50]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA00572 for ; Fri, 28 Mar 1997 01:50:53 -0800 (PST) Received: from localhost (vince@localhost) by mail.MCESTATE.COM (8.8.5/8.8.5) with SMTP id BAA06339 for ; Fri, 28 Mar 1997 01:50:48 -0800 (PST) Date: Fri, 28 Mar 1997 01:50:47 -0800 (PST) From: Vincent Poy To: current@FreeBSD.ORG Subject: recent successful -current build Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Has anyone successfully built -current with a new kernel recently? Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-current Fri Mar 28 02:21:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA02234 for current-outgoing; Fri, 28 Mar 1997 02:21:42 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA02226 for ; Fri, 28 Mar 1997 02:21:37 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA18421 for freebsd-current@FreeBSD.org; Fri, 28 Mar 1997 11:21:35 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id LAA21756; Fri, 28 Mar 1997 11:20:20 +0100 (MET) Message-ID: <19970328112019.PN39531@uriah.heep.sax.de> Date: Fri, 28 Mar 1997 11:20:19 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Funny sc0 behaviour X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk sc0: the current keyboard controller command byte 0045 kbdio: RESET_KBD return code:00fe kbdio: RESET_KBD return code:00fe kbdio: RESET_KBD return code:00fe kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 sc0: failed to reset the keyboard. sc0 at 0x60-0x6f irq 1 on motherboard sc0: MDA/hercules <16 virtual consoles, flags=0x0> Of course, most of the above is a lie. :-) This machine has neither a keyboard connected, nor a graphics card present at all. Shouldn't sc0 fail probing in this case? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Mar 28 02:51:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA03613 for current-outgoing; Fri, 28 Mar 1997 02:51:42 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA03602 for ; Fri, 28 Mar 1997 02:51:34 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA18743 for current@FreeBSD.ORG; Fri, 28 Mar 1997 11:51:30 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id LAA21794; Fri, 28 Mar 1997 11:22:38 +0100 (MET) Message-ID: <19970328112238.ZK19495@uriah.heep.sax.de> Date: Fri, 28 Mar 1997 11:22:38 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: recent successful -current build References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Vincent Poy on Mar 28, 1997 01:50:47 -0800 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Vincent Poy wrote: > Has anyone successfully built -current with a new kernel recently? If ~ 1.5 days ago counts as `recently', yes. I had to run make -k to build the world, due to the (known) dumpfs problem. The machine runs fine, and serves as a testbed right now. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Mar 28 02:57:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA03889 for current-outgoing; Fri, 28 Mar 1997 02:57:21 -0800 (PST) Received: from mailsrv.cc.utsunomiya-u.ac.jp (mailsrv.cc.utsunomiya-u.ac.jp [160.12.200.20]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA03883 for ; Fri, 28 Mar 1997 02:57:15 -0800 (PST) Received: from zodiac.mech.utsunomiya-u.ac.jp (mpRrXUhTrFEsGa9O5GMATyigSC0a2R5N@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by mailsrv.cc.utsunomiya-u.ac.jp (8.8.5+2.7Wbeta5/3.5Wpl4) with ESMTP id TAA18913; Fri, 28 Mar 1997 19:56:21 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id UAA07921; Fri, 28 Mar 1997 20:00:45 +0900 (JST) Message-Id: <199703281100.UAA07921@zodiac.mech.utsunomiya-u.ac.jp> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@freebsd.org (FreeBSD-current users), yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Funny sc0 behaviour In-reply-to: Your message of "Fri, 28 Mar 1997 11:20:19 +0100." <19970328112019.PN39531@uriah.heep.sax.de> References: <19970328112019.PN39531@uriah.heep.sax.de> Date: Fri, 28 Mar 1997 20:00:43 +0900 From: Kazutaka YOKOTA Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >sc0: the current keyboard controller command byte 0045 >kbdio: RESET_KBD return code:00fe >kbdio: RESET_KBD return code:00fe >kbdio: RESET_KBD return code:00fe >kbdio: DIAGNOSE status:0055 >kbdio: TEST_KBD_PORT status:0000 >sc0: failed to reset the keyboard. >sc0 at 0x60-0x6f irq 1 on motherboard >sc0: MDA/hercules <16 virtual consoles, flags=0x0> > >Of course, most of the above is a lie. :-) This machine has neither >a keyboard connected, nor a graphics card present at all. > >Shouldn't sc0 fail probing in this case? Set the DETECT_KBD bit (0x08) in the configuration flag of syscons, and its probe routine (scprobe) will report failure if keyboard reset fails. As for the display adapter, syscons assumes there always is a graphics adapter. I always thought these are design decisions. We have to ask Soren exact reasons why these decisions were made. Kazu From owner-freebsd-current Fri Mar 28 03:00:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA04029 for current-outgoing; Fri, 28 Mar 1997 03:00:01 -0800 (PST) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA04000 for ; Fri, 28 Mar 1997 02:59:58 -0800 (PST) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id EAA12798; Fri, 28 Mar 1997 04:59:53 -0600 (CST) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 28 Mar 1997 04:58:12 -0600 To: "Kenneth R. Westerback" From: Richard Wackerbarth Subject: Re: src-2.2-CTM-README typo Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 9:03 PM -0600 3/27/97, Kenneth R. Westerback wrote: >Pretty self explanatory ... > >36c36,37 >< ***** For 2.2.1 RELEASE, you will start with src-2.2.0210.gz >--- >> ***** For 2.2.0 RELEASE, you will start with src-2.2.0210.gz >> ***** For 2.2.1 RELEASE, you will start with src-2.2.0217.gz > >---- Ken (still looking for 216!) Thanks Ken. I'll get it corrected. BTW, I hope that you have the 216 delta by now. From owner-freebsd-current Fri Mar 28 03:09:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA04503 for current-outgoing; Fri, 28 Mar 1997 03:09:42 -0800 (PST) Received: from oxmail4.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA04495 for ; Fri, 28 Mar 1997 03:09:37 -0800 (PST) Received: from njl2.materials.ox.ac.uk by oxmail4 with SMTP (PP); Fri, 28 Mar 1997 11:09:20 +0000 Received: by njl2.materials.ox.ac.uk (950413.SGI.8.6.12/940406.SGI) id LAA08977; Fri, 28 Mar 1997 11:09:17 GMT Date: Fri, 28 Mar 1997 11:09:17 GMT From: neil.long@materials.oxford.ac.uk (Neil J Long) Message-Id: <9703281109.ZM8975@njl2.materials.ox.ac.uk> In-Reply-To: Bill Fenner "Re: Possible routed problem 2.2" (Mar 22, 10:00am) References: <97Mar22.100042pst.177486@crevenia.parc.xerox.com> X-Mailer: Z-Mail-SGI (3.2S.3 08feb96 MediaMail) To: Bill Fenner , freebsd-current@freebsd.org Subject: 2.2.1 network and amanda dump problem (again) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Repetition of previous problem which I thought was a routed bug. System is at 2.2.1 cvsup'd and a world and kernel built as of March 26th. I don't know how to debug this problem as remotely logging in changes the network related allocations and when it happens I cannot log in any more. This seems to be a problem during level 0 dumps where the quantity of data is higher and so takes longer. I will run netstat -m in a loop and log what I can but this looks like being obscure and probably limited to the amanda sendbackup program (which runs suid root). Original postings follow and then some more info after that. On Mar 22, 10:00am, Bill Fenner wrote: > Subject: Re: Possible routed problem 2.2 > >The machine was not contactable via the net but was still running when I > >went in to check. These are the errors logged in messages > > > >Mar 22 01:15:00 njl sendbackup[446]: error [dump returned 3, compress > >got signal > > 13] > >Mar 22 01:15:22 njl routed[58]: punt RTM_LOSING without gateway > >Mar 22 01:15:46 njl routed[58]: punt RTM_LOSING without gateway > > These mean that TCP to a machine on the local network was having > trouble. (Probably just another symptom of what you show below). It's > a bug in routed that it logs this fact at such a high level; the TCP > trouble has nothing to do with routed. > > >ping: sendto: No buffer space available > > Looks like your machine ran out of mbuf's. If you can recreate this, try > "netstat -m" and see if any category has a much higher number than the others. > > Bill >-- End of excerpt from Bill Fenner This happened again last night - the PC was idle when the amanda dumps started (/usr/ports/misc/amanda). Logging in on the console netstat -m shows 144 mbufs in use 86 mbufs allocated to data 49 mbufs allocated to packet headers 7 mbufs allocated to protocol control blocks 2 mbufs allocated to socket names and addresses 10/26 mbuf clusters in use 70 Kbytes allocated to network (54% in use) 0 requests for memery denied 0 requests for memory delayed 0 calls to protocol drain routines On the amanda server the dumps were recorded as FAILURE AND STRANGE DUMP SUMMARY: njl /usr lev 0 FAILED [data timeout] njl /home lev 0 FAILED [data timeout] njl /var lev 0 FAILED [could not connect to njl] njl / lev 1 FAILED [could not connect to njl] ... FAILED AND STRANGE DUMP DETAILS: /-- njl /usr lev 0 FAILED [data timeout] sendbackup: start [njl:/usr level 0 datestamp 19970328] | DUMP: Date of this level 0 dump: Fri Mar 28 00:56:23 1997 | DUMP: Date of last level 0 dump: the epoch | DUMP: Dumping /dev/rsd0s1e (/usr) to standard output | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 276523 tape blocks. | DUMP: dumping (Pass III) [directories] | DUMP: dumping (Pass IV) [regular files] | DUMP: 8.31% done, finished in 0:55 | DUMP: 15.83% done, finished in 0:53 | DUMP: 22.28% done, finished in 0:52 | DUMP: 28.84% done, finished in 0:49 | DUMP: 36.26% done, finished in 0:43 | DUMP: 44.74% done, finished in 0:37 | DUMP: 51.38% done, finished in 0:33 | DUMP: 57.95% done, finished in 0:29 \-------- /-- njl /home lev 0 FAILED [data timeout] sendbackup: start [njl:/home level 0 datestamp 19970328] | DUMP: Date of this level 0 dump: Fri Mar 28 00:56:12 1997 | DUMP: Date of last level 0 dump: the epoch | DUMP: Dumping /dev/rsd0s4e (/home) to standard output | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 272941 tape blocks. | DUMP: dumping (Pass III) [directories] | DUMP: dumping (Pass IV) [regular files] | DUMP: 5.83% done, finished in 1:20 | DUMP: 9.84% done, finished in 1:31 | DUMP: 17.51% done, finished in 1:10 | DUMP: 26.87% done, finished in 0:54 | DUMP: 34.17% done, finished in 0:48 | DUMP: 43.31% done, finished in 0:39 | DUMP: 52.10% done, finished in 0:32 | DUMP: 60.08% done, finished in 0:26 \-------- The PC has a 3Com 3C589 combo - ep0 routed reported the same error before sendbackup timed out. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Neil J Long, Department of Materials, University of Oxford * Parks Road, Oxford, OX1 3PH, UK * EMail: Neil.Long@materials.oxford.ac.uk * Tel: +44 (0)1865-273678 Fax: +44 (0)1865-273789 From owner-freebsd-current Fri Mar 28 03:14:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA04876 for current-outgoing; Fri, 28 Mar 1997 03:14:34 -0800 (PST) Received: from mail.MCESTATE.COM (vince@mail.MCESTATE.COM [207.211.200.50]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA04871 for ; Fri, 28 Mar 1997 03:14:31 -0800 (PST) Received: from localhost (vince@localhost) by mail.MCESTATE.COM (8.8.5/8.8.5) with SMTP id DAA06973; Fri, 28 Mar 1997 03:14:26 -0800 (PST) Date: Fri, 28 Mar 1997 03:14:23 -0800 (PST) From: Vincent Poy To: Joerg Wunsch cc: current@FreeBSD.ORG Subject: Re: recent successful -current build In-Reply-To: <19970328112238.ZK19495@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Mar 1997, J Wunsch wrote: > > Has anyone successfully built -current with a new kernel recently? > > If ~ 1.5 days ago counts as `recently', yes. I had to run make -k to > build the world, due to the (known) dumpfs problem. The machine runs > fine, and serves as a testbed right now. Hmm, good to hear that. Tried building something 5 days ago and it won't mount the ufs partitions so had to use a floppy to boot and repaired it. Ever since John made the lite2 merge, there hasn't been any updates to if everything was once again stable again but thanks for the info. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-current Fri Mar 28 04:36:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA08782 for current-outgoing; Fri, 28 Mar 1997 04:36:17 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA08777 for ; Fri, 28 Mar 1997 04:36:13 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA20855 for freebsd-current@freebsd.org; Fri, 28 Mar 1997 13:36:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id NAA22071; Fri, 28 Mar 1997 13:34:45 +0100 (MET) Message-ID: <19970328133445.DO64097@uriah.heep.sax.de> Date: Fri, 28 Mar 1997 13:34:45 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: Funny sc0 behaviour References: <19970328112019.PN39531@uriah.heep.sax.de> <199703281100.UAA07921@zodiac.mech.utsunomiya-u.ac.jp> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703281100.UAA07921@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Mar 28, 1997 20:00:43 +0900 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Kazutaka YOKOTA wrote: > >Shouldn't sc0 fail probing in this case? > > Set the DETECT_KBD bit (0x08) in the configuration flag of syscons, > and its probe routine (scprobe) will report failure if keyboard reset > fails. This wasn't that much my concern. I know that it's hard to reliably probe for the keyboard on all machines. > As for the display adapter, syscons assumes there always is a graphics > adapter. > > I always thought these are design decisions. I rather think it's sloppyness (or arrogance :) on the part of the graphics console drivers. pcvt suffers from the same problem. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Mar 28 09:06:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA20957 for current-outgoing; Fri, 28 Mar 1997 09:06:12 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA20949 for ; Fri, 28 Mar 1997 09:06:05 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA17098; Fri, 28 Mar 1997 10:05:30 -0700 (MST) Date: Fri, 28 Mar 1997 10:05:30 -0700 (MST) Message-Id: <199703281705.KAA17098@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: Funny sc0 behaviour In-Reply-To: <19970328112019.PN39531@uriah.heep.sax.de> References: <19970328112019.PN39531@uriah.heep.sax.de> X-Mailer: VM 6.22 under 19.14 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch writes: > sc0: the current keyboard controller command byte 0045 .. > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: MDA/hercules <16 virtual consoles, flags=0x0> ... > Of course, most of the above is a lie. :-) This machine has neither > a keyboard connected, nor a graphics card present at all. > > Shouldn't sc0 fail probing in this case? Sure, but because of pst's 'DETECT_KBD' patch, it always returns true in the failure mode. return ((dev->id_flags & DETECT_KBD) ? 0 : IO_KBDSIZE); ---------------------------- revision 1.181 date: 1996/10/23 07:29:43; author: pst; state: Exp; lines: +8 -7 Remove SC_KBD_PROBE_WORKS option and replace it with a simple run-time flag bit (0x0008) in the sc driver configuration line. This way it's easy to boink a generic kernel. Nate From owner-freebsd-current Fri Mar 28 09:51:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA23538 for current-outgoing; Fri, 28 Mar 1997 09:51:58 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA23523 for ; Fri, 28 Mar 1997 09:51:55 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA24652 for freebsd-current@freebsd.org; Fri, 28 Mar 1997 18:51:53 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id SAA22867; Fri, 28 Mar 1997 18:28:11 +0100 (MET) Message-ID: <19970328182811.CZ37193@uriah.heep.sax.de> Date: Fri, 28 Mar 1997 18:28:11 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: Funny sc0 behaviour References: <19970328112019.PN39531@uriah.heep.sax.de> <199703281705.KAA17098@rocky.mt.sri.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703281705.KAA17098@rocky.mt.sri.com>; from Nate Williams on Mar 28, 1997 10:05:30 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Nate Williams wrote: > > Of course, most of the above is a lie. :-) This machine has neither > > a keyboard connected, nor a graphics card present at all. > > > > Shouldn't sc0 fail probing in this case? > > Sure, but because of pst's 'DETECT_KBD' patch, it always returns true in > the failure mode. I agree that it shouldn't be fatal if just the keyboard detection fails. There are too many brok^H^H^H^Hweird keyboards around, as we know since the days when we tried to make the keyboard-probing bootblocks the standard. However, if there's no graphics adapter that can be found (and this condition can be detected reliably, there's no need to blindly assume it were an MDA), syscons (and pcvt, for that matter) have no business at all. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Mar 28 13:59:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA06532 for current-outgoing; Fri, 28 Mar 1997 13:59:20 -0800 (PST) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA06522 for ; Fri, 28 Mar 1997 13:59:16 -0800 (PST) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id OAA21883 for ; Fri, 28 Mar 1997 14:02:55 -0800 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id QAA15302; Fri, 28 Mar 1997 16:58:42 -0500 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id QAA12382; Fri, 28 Mar 1997 16:58:42 -0500 Received: (from alk@localhost) by compound.east.sun.com (8.8.5/8.7.3) id VAA00548; Fri, 28 Mar 1997 21:58:39 GMT Date: Fri, 28 Mar 1997 21:58:39 GMT Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199703282158.VAA00548@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: current@freebsd.org Subject: Anyone familiar with iijppp NFS failures? X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone seen this? iijppp fails during NFS traffic: wrote 1500, got -1 wrote 672, got -1 ... Obviously in ip.c: /* * Pass it to tunnel device */ nw = write(tun_out, tunbuff, nb); if (nw != nb) fprintf(stderr, "wrote %d, got %d\r\n", nb, nw); Before looking deeper, I thought I'd ask if there were any known reasons for this sort of thing to happen. //alk From owner-freebsd-current Fri Mar 28 15:56:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA14245 for current-outgoing; Fri, 28 Mar 1997 15:56:42 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA14237 for ; Fri, 28 Mar 1997 15:56:32 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wAlUy-0001zy-00; Fri, 28 Mar 1997 16:55:56 -0700 To: Vincent Poy Subject: Re: recent successful -current build Cc: Joerg Wunsch , current@freebsd.org In-reply-to: Your message of "Fri, 28 Mar 1997 03:14:23 PST." References: Date: Fri, 28 Mar 1997 16:55:55 -0700 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Vincent Poy writes: : Hmm, good to hear that. Tried building something 5 days ago and : it won't mount the ufs partitions so had to use a floppy to boot and : repaired it. Ever since John made the lite2 merge, there hasn't been any : updates to if everything was once again stable again but thanks for the : info. You will need new mount binaries to run the new kernel. I did a make world and then built a new kernel and then rebooted and it worked great (this was before the dumpfs breakage). Warner From owner-freebsd-current Fri Mar 28 16:41:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA17947 for current-outgoing; Fri, 28 Mar 1997 16:41:01 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA17940 for ; Fri, 28 Mar 1997 16:40:58 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id QAA05437; Fri, 28 Mar 1997 16:40:55 -0800 (PST) Message-Id: <199703290040.QAA05437@austin.polstra.com> To: matt@deepwell.com Subject: Re: Make World Failure (Still) Newsgroups: polstra.freebsd.stable In-Reply-To: <3.0.32.19970328153553.00bb90ac@deepwell.com> References: <3.0.32.19970328153553.00bb90ac@deepwell.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Fri, 28 Mar 1997 16:40:55 -0800 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <3.0.32.19970328153553.00bb90ac@deepwell.com>, Matt Eagleson wrote: > I must be stupid but I can't get RELENG_2_2 > to make. > > cc -O2 -m486 -pipe -c /usr/src/sbin/dumpfs/dumpfs.c > /usr/src/sbin/dumpfs/dumpfs.c: In function `dumpfs': > /usr/src/sbin/dumpfs/dumpfs.c:150: structure has no member named > `fs_headswitch' > /usr/src/sbin/dumpfs/dumpfs.c:150: structure has no member named `fs_trkseek' > *** Error code 1 You're not stupid, it's just broken in 2.2 right now. Peter committed a fix for -current, but the fix is not in 2.2 yet. Your best bet for now might be to delete dumpfs from the Makefile in "/usr/src/sbin". Or, merge in Peter's fix, which is small and simple. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Fri Mar 28 17:30:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA21068 for current-outgoing; Fri, 28 Mar 1997 17:30:33 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA21050 for ; Fri, 28 Mar 1997 17:30:30 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id RAA08748 for ; Fri, 28 Mar 1997 17:30:29 -0800 (PST) Message-Id: <199703290130.RAA08748@austin.polstra.com> To: current@freebsd.org Subject: Panic: "lockmgr: pid %d, not %s %d unlocking" Date: Fri, 28 Mar 1997 17:30:28 -0800 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just got this panic on a -current kernel from March 17th, running on a 486/66DX2 with 16 MB of RAM: #9 0xf01181fa in panic (fmt=0xf0112e4b "lockmgr: pid %d, not %s %d unlocking") at ../../kern/kern_shutdown.c:366 #10 0xf01132d8 in lockmgr (lkp=0xf0bc3e34, flags=6, interlkp=0xf0ba5b60, p=0xf0bf1800) at ../../kern/kern_lock.c:355 #11 0xf01af9c3 in ufs_unlock (ap=0xefbffd50) at ../../ufs/ufs/ufs_vnops.c:1784 #12 0xf0165b35 in nfs_inactive (ap=0xefbffd78) at vnode_if.h:843 #13 0xf013a3b1 in vputrele (vp=0xf0ba5b00, put=0) at vnode_if.h:775 #14 0xf013a3ee in vrele (vp=0xf0ba5b00) at ../../kern/vfs_subr.c:1093 #15 0xf01bf4b9 in vnode_pager_dealloc (object=0xf0c72980) at ../../vm/vnode_pager.c:203 #16 0xf01be826 in vm_pager_deallocate (object=0xf0c72980) at ../../vm/vm_pager.c:177 #17 0xf01b95ec in vm_object_terminate (object=0xf0c72980) at ../../vm/vm_object.c:420 #18 0xf01b93f7 in vm_object_deallocate (object=0xf0c72980) at ../../vm/vm_object.c:355 #19 0xf013a2a9 in vputrele (vp=0xf0ba5b00, put=1) at ../../kern/vfs_subr.c:1034 #20 0xf013a3ce in vput (vp=0xf0ba5b00) at ../../kern/vfs_subr.c:1086 #21 0xf0190c46 in nfs_remove (ap=0xefbffef8) at ../../nfs/nfs_vnops.c:1516 #22 0xf013d32f in unlink (p=0xf0bf1800, uap=0xefbfff94, retval=0xefbfff84) at vnode_if.h:531 #23 0xf01ce6a6 in syscall (frame={tf_es = 135135271, tf_ds = -272695257, tf_edi = 319616, tf_esi = 319616, tf_ebp = -272647532, tf_isp = -272629788, tf_ebx = -272648556, tf_edx = 70, tf_ecx = -272648676, tf_eax = 10, tf_trapno = 0, tf_err = 7, tf_eip = 134972241, tf_cs = 31, tf_eflags = 582, tf_esp = -272648588, tf_ss = 39}) at ../../i386/i386/trap.c:890 At the time, the machine was simultaneously doing a "cvs update" of /usr/src from an NFS-mounted repository, and an "rm -rf" of a large directory tree on the local disk. I've been running the kernel since March 17th, and this is its first panic. I'll save the kernel and the crash dump in case more information is needed. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Fri Mar 28 22:15:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA12141 for current-outgoing; Fri, 28 Mar 1997 22:15:13 -0800 (PST) Received: from mail.MCESTATE.COM (vince@mail.MCESTATE.COM [207.211.200.50]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA12135 for ; Fri, 28 Mar 1997 22:15:10 -0800 (PST) Received: from localhost (vince@localhost) by mail.MCESTATE.COM (8.8.5/8.8.5) with SMTP id WAA10424; Fri, 28 Mar 1997 22:14:24 -0800 (PST) Date: Fri, 28 Mar 1997 22:14:23 -0800 (PST) From: Vincent Poy To: Warner Losh cc: Joerg Wunsch , current@freebsd.org Subject: Re: recent successful -current build In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Mar 1997, Warner Losh wrote: > You will need new mount binaries to run the new kernel. I did a make > world and then built a new kernel and then rebooted and it worked > great (this was before the dumpfs breakage). Actually the weird thing that happened was after the make world was over, the machine just rebooted on it's own before I can build a kernel so it couldn't boot up. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-current Sat Mar 29 00:21:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA15885 for current-outgoing; Sat, 29 Mar 1997 00:21:51 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA15874 for ; Sat, 29 Mar 1997 00:21:48 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA05960 for current@freebsd.org; Sat, 29 Mar 1997 09:21:46 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA26558; Sat, 29 Mar 1997 09:00:45 +0100 (MET) Message-ID: <19970329090045.EB65119@uriah.heep.sax.de> Date: Sat, 29 Mar 1997 09:00:45 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: current@freebsd.org Subject: Re: Make World Failure (Still) References: <3.0.32.19970328153553.00bb90ac@deepwell.com> <199703290040.QAA05437@austin.polstra.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703290040.QAA05437@austin.polstra.com>; from John Polstra on Mar 28, 1997 16:40:55 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As John Polstra wrote: > You're not stupid, it's just broken in 2.2 right now. Peter committed > a fix for -current, but the fix is not in 2.2 yet. Curious: who broke it in 2.2? I thought this was only related to 4.4-Lite2 changes in -current? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Mar 29 00:35:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA16179 for current-outgoing; Sat, 29 Mar 1997 00:35:39 -0800 (PST) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA16174 for ; Sat, 29 Mar 1997 00:35:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by nlsystems.com (8.8.5/8.8.5) with SMTP id IAA04565; Sat, 29 Mar 1997 08:33:57 GMT Date: Sat, 29 Mar 1997 08:33:57 +0000 (GMT) From: Doug Rabson To: Tony Kimball cc: current@FreeBSD.ORG Subject: Re: Anyone familiar with iijppp NFS failures? In-Reply-To: <199703282158.VAA00548@compound.east.sun.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Mar 1997, Tony Kimball wrote: > > Has anyone seen this? iijppp fails during NFS traffic: > wrote 1500, got -1 > wrote 672, got -1 > ... > Obviously in ip.c: > /* > * Pass it to tunnel device > */ > nw = write(tun_out, tunbuff, nb); > if (nw != nb) > fprintf(stderr, "wrote %d, got %d\r\n", nb, nw); > Before looking deeper, I thought I'd ask if there were any known > reasons for this sort of thing to happen. It would be helpful to know the value of errno at this point. From looking at the code, tunwrite can error if it is given a packet which is too large (EIO), if allocation of mbufs failed or if an input queue was full (ENOBUFS). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-current Sat Mar 29 01:17:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA17024 for current-outgoing; Sat, 29 Mar 1997 01:17:28 -0800 (PST) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA17019 for ; Sat, 29 Mar 1997 01:17:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by nlsystems.com (8.8.5/8.8.5) with SMTP id JAA04597; Sat, 29 Mar 1997 09:15:37 GMT Date: Sat, 29 Mar 1997 09:15:36 +0000 (GMT) From: Doug Rabson To: John Polstra cc: current@freebsd.org Subject: Re: Panic: "lockmgr: pid %d, not %s %d unlocking" In-Reply-To: <199703290130.RAA08748@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Mar 1997, John Polstra wrote: > I just got this panic on a -current kernel from March 17th, running > on a 486/66DX2 with 16 MB of RAM: > > #9 0xf01181fa in panic (fmt=0xf0112e4b "lockmgr: pid %d, not %s %d unlocking") > at ../../kern/kern_shutdown.c:366 > #10 0xf01132d8 in lockmgr (lkp=0xf0bc3e34, flags=6, interlkp=0xf0ba5b60, > p=0xf0bf1800) at ../../kern/kern_lock.c:355 > #11 0xf01af9c3 in ufs_unlock (ap=0xefbffd50) at ../../ufs/ufs/ufs_vnops.c:1784 > #12 0xf0165b35 in nfs_inactive (ap=0xefbffd78) at vnode_if.h:843 This looks as if the vnode was recycled unexpectedly from NFS to UFS during the call to vm_object_deallocate. Unfortunately I can't see any obvious way this can happen since the vm_object has a ref to the vnode and it doesn't look like vm_object_deallocate can get re-entered easily. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-current Sat Mar 29 01:20:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA17104 for current-outgoing; Sat, 29 Mar 1997 01:20:33 -0800 (PST) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA17099 for ; Sat, 29 Mar 1997 01:20:29 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by nlsystems.com (8.8.5/8.8.5) with SMTP id JAA04616; Sat, 29 Mar 1997 09:19:26 GMT Date: Sat, 29 Mar 1997 09:19:26 +0000 (GMT) From: Doug Rabson To: Joerg Wunsch cc: current@freebsd.org Subject: Re: Make World Failure (Still) In-Reply-To: <19970329090045.EB65119@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 29 Mar 1997, J Wunsch wrote: > As John Polstra wrote: > > > You're not stupid, it's just broken in 2.2 right now. Peter committed > > a fix for -current, but the fix is not in 2.2 yet. > > Curious: who broke it in 2.2? I thought this was only related to > 4.4-Lite2 changes in -current? Actually I think it was the fsirand changes which broke both of them. A slapped wrist for someone for committing a build break to the 2.2 branch, I think. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-current Sat Mar 29 03:21:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA21509 for current-outgoing; Sat, 29 Mar 1997 03:21:30 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA21504 for ; Sat, 29 Mar 1997 03:21:26 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA06986 for current@freebsd.org; Sat, 29 Mar 1997 12:21:23 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id MAA27034; Sat, 29 Mar 1997 12:00:34 +0100 (MET) Message-ID: <19970329120034.CM24673@uriah.heep.sax.de> Date: Sat, 29 Mar 1997 12:00:34 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: current@freebsd.org Subject: Re: Make World Failure (Still) References: <19970329090045.EB65119@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Doug Rabson on Mar 29, 1997 09:19:26 +0000 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Doug Rabson wrote: > Actually I think it was the fsirand changes which broke both of them. A > slapped wrist for someone for committing a build break to the 2.2 branch, > I think. Ah, thanks for enlightening me. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Mar 29 10:13:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA05332 for current-outgoing; Sat, 29 Mar 1997 10:13:18 -0800 (PST) Received: from mailhost (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA05325 for ; Sat, 29 Mar 1997 10:13:14 -0800 (PST) Received: from rlb by mailhost with smtp (Smail3.1.29.1 #1) id m0wB2cl-000FzzC; Sat, 29 Mar 97 13:13 EST Message-ID: <333D5BB5.7F73@mindspring.com> Date: Sat, 29 Mar 1997 13:13:09 -0500 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.5.1 i86pc) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Building ip_fil3.10 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In trying to build ip_file3.1.10 http://cheops.anu.edu.au/~avalon/ip-filter.html it seems that the lkm stuff was built for FBSD 2.1. The ioconf.h file is no longer properly referenced and providing the correct info. gcc -I. -I../.. -DIPFILTER_LKM -DIPFILTER_LOG -D`uname -m` -D__`uname -m`__ -DINET -DKERNEL -D_KERNEL -I/usr/include -I/sys -I/sys/sys -I/sys/arch -DIPL_NAME=\"/dev/ipl\" -c ../../mln_ipl.c -o ml_ipl.o In file included from /usr/include/sys/conf.h:226, from ../../mln_ipl.c:29: /usr/include/machine/conf.h:6: ioconf.h: No such file or directory Has anyone ported this to 2.2 or 3.0 b4 I start on this? Thank's Ron -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ GSU: gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 Work: 770-246-5404 **************************************************************************** From owner-freebsd-current Sat Mar 29 10:36:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA06027 for current-outgoing; Sat, 29 Mar 1997 10:36:59 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA06021 for ; Sat, 29 Mar 1997 10:36:54 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA06605; Sat, 29 Mar 1997 11:21:25 -0700 From: Terry Lambert Message-Id: <199703291821.LAA06605@phaeton.artisoft.com> Subject: Re: Panic: "lockmgr: pid %d, not %s %d unlocking" To: dfr@nlsystems.com (Doug Rabson) Date: Sat, 29 Mar 1997 11:21:25 -0700 (MST) Cc: jdp@polstra.com, current@freebsd.org In-Reply-To: from "Doug Rabson" at Mar 29, 97 09:15:36 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I just got this panic on a -current kernel from March 17th, running > > on a 486/66DX2 with 16 MB of RAM: > > > > #9 0xf01181fa in panic (fmt=0xf0112e4b "lockmgr: pid %d, not %s %d unlocking") > > at ../../kern/kern_shutdown.c:366 > > #10 0xf01132d8 in lockmgr (lkp=0xf0bc3e34, flags=6, interlkp=0xf0ba5b60, > > p=0xf0bf1800) at ../../kern/kern_lock.c:355 > > #11 0xf01af9c3 in ufs_unlock (ap=0xefbffd50) at ../../ufs/ufs/ufs_vnops.c:1784 > > #12 0xf0165b35 in nfs_inactive (ap=0xefbffd78) at vnode_if.h:843 > > This looks as if the vnode was recycled unexpectedly from > NFS to UFS during the call to vm_object_deallocate. Unfortunately I can't > see any obvious way this can happen since the vm_object has a ref to the > vnode and it doesn't look like vm_object_deallocate can get re-entered > easily. Actually, it looks like lockmgr() is not reeentrancy locking the global structures (something which is necessary if the lock management is done on a calldown rather than a veto basis). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sat Mar 29 11:24:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA07718 for current-outgoing; Sat, 29 Mar 1997 11:24:02 -0800 (PST) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA07694 for ; Sat, 29 Mar 1997 11:23:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by nlsystems.com (8.8.5/8.8.5) with SMTP id TAA07019; Sat, 29 Mar 1997 19:20:57 GMT Date: Sat, 29 Mar 1997 19:20:56 +0000 (GMT) From: Doug Rabson Reply-To: Doug Rabson To: Terry Lambert cc: jdp@polstra.com, current@freebsd.org Subject: Re: Panic: "lockmgr: pid %d, not %s %d unlocking" In-Reply-To: <199703291821.LAA06605@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 29 Mar 1997, Terry Lambert wrote: > > > I just got this panic on a -current kernel from March 17th, running > > > on a 486/66DX2 with 16 MB of RAM: > > > > > > #9 0xf01181fa in panic (fmt=0xf0112e4b "lockmgr: pid %d, not %s %d unlocking") > > > at ../../kern/kern_shutdown.c:366 > > > #10 0xf01132d8 in lockmgr (lkp=0xf0bc3e34, flags=6, interlkp=0xf0ba5b60, > > > p=0xf0bf1800) at ../../kern/kern_lock.c:355 > > > #11 0xf01af9c3 in ufs_unlock (ap=0xefbffd50) at ../../ufs/ufs/ufs_vnops.c:1784 > > > #12 0xf0165b35 in nfs_inactive (ap=0xefbffd78) at vnode_if.h:843 > > > > This looks as if the vnode was recycled unexpectedly from > > NFS to UFS during the call to vm_object_deallocate. Unfortunately I can't > > see any obvious way this can happen since the vm_object has a ref to the > > vnode and it doesn't look like vm_object_deallocate can get re-entered > > easily. > > Actually, it looks like lockmgr() is not reeentrancy locking the global > structures (something which is necessary if the lock management is done > on a calldown rather than a veto basis). Now that I have had a chance to thing about this for a while, I think it is due to the fact that vop_nolock and vop_nounlock are stubbed out in the Lite2 code. These are used to provide a simple shared lock for non-locking filesystems. The (allegedly evil :-) vclean code uses the lockmgr code to wait for all outstanding shared locks to be released using LK_DRAIN; this is an improvement to the Lite1 version of vclean which I don't think worked very well for non-locking filesystems. Unfortunately since the Lite2 version of NFS and possibly some other filesystems does not correctly observe the vnode locking protocol, the code was not enabled. I made a start on fixing the locking protocol in NFS when I was working on it in the lite2 tree. When my new machine arrives, I will finish this and enable the proper locking code for at least NFS. On a related note, does anyone have any filesystem stress tests? I was thinking of writing a simple one which would use multiple processes to create, read, copy and delete large trees on several different filesystems. This ought to stress the locking and vnode allocation code fairly well. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-current Sat Mar 29 13:15:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA13516 for current-outgoing; Sat, 29 Mar 1997 13:15:52 -0800 (PST) Received: from peedub.gj.org (newpc.muc.ditec.de [194.120.126.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA13511 for ; Sat, 29 Mar 1997 13:15:48 -0800 (PST) Received: from peedub.gj.org (localhost [127.0.0.1]) by peedub.gj.org (8.8.5/8.6.9) with ESMTP id WAA03718; Sat, 29 Mar 1997 22:14:45 GMT Message-Id: <199703292214.WAA03718@peedub.gj.org> X-Mailer: exmh version 2.0gamma 1/27/96 To: Ron Bolin Cc: freebsd-current@freebsd.org Subject: Re: Building ip_fil3.10 Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 29 Mar 1997 13:13:09 EST." <333D5BB5.7F73@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Mar 1997 22:14:45 +0000 From: Gary Jennejohn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ron Bolin writes: >In trying to build ip_file3.1.10 > >http://cheops.anu.edu.au/~avalon/ip-filter.html > >it seems that the lkm stuff was built for FBSD 2.1. > >The ioconf.h file is no longer properly referenced and providing >the correct info. > >gcc -I. -I../.. -DIPFILTER_LKM -DIPFILTER_LOG -D`uname -m` -D__`uname >-m`__ -DINET -DKERNEL -D_KERNEL -I/usr/include -I/sys -I/sys/sys >-I/sys/arch -DIPL_NAME=\"/dev/ipl\" -c ../../mln_ipl.c -o ml_ipl.o >In file included from /usr/include/sys/conf.h:226, > from ../../mln_ipl.c:29: >/usr/include/machine/conf.h:6: ioconf.h: No such file or directory > >Has anyone ported this to 2.2 or 3.0 b4 I start on this? > are you using the version of min_ipl.c which Darren recently (24 March) posted to the ipfilter list ? This supposedly works under 2.2. I haven't tried it, myself. --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com From owner-freebsd-current Sat Mar 29 13:17:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA13634 for current-outgoing; Sat, 29 Mar 1997 13:17:11 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA13611; Sat, 29 Mar 1997 13:17:05 -0800 (PST) From: Mike Pritchard Message-Id: <199703292117.NAA13611@freefall.freebsd.org> Subject: Re: Panic: "lockmgr: pid %d, not %s %d unlocking" To: jdp (John Polstra) Date: Sat, 29 Mar 1997 13:17:05 -0800 (PST) Cc: current In-Reply-To: from "Doug Rabson" at Mar 29, 97 07:20:56 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk How come the panic message wasn't expanded? -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-current Sat Mar 29 13:53:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA15514 for current-outgoing; Sat, 29 Mar 1997 13:53:29 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA15508; Sat, 29 Mar 1997 13:53:26 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id NAA00536; Sat, 29 Mar 1997 13:53:25 -0800 (PST) Message-Id: <199703292153.NAA00536@austin.polstra.com> To: Mike Pritchard cc: current@freefall.freebsd.org Subject: Re: Panic: "lockmgr: pid %d, not %s %d unlocking" In-reply-to: Your message of "Sat, 29 Mar 1997 13:17:05 PST." <199703292117.NAA13611@freefall.freebsd.org> References: <199703292117.NAA13611@freefall.freebsd.org> Date: Sat, 29 Mar 1997 13:53:25 -0800 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > How come the panic message wasn't expanded? The original panic message that came out on the console was expanded. The output I included in my posting came from running "gdb -k" later, on the kernel + crash dump. I guess it's not expanded at that point. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sat Mar 29 23:22:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA12894 for current-outgoing; Sat, 29 Mar 1997 23:22:25 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA12883 for ; Sat, 29 Mar 1997 23:22:19 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA20023 for current@freefall.freebsd.org; Sun, 30 Mar 1997 09:22:18 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA03177; Sun, 30 Mar 1997 08:57:08 +0200 (MEST) Message-ID: <19970330085707.VX48668@uriah.heep.sax.de> Date: Sun, 30 Mar 1997 08:57:07 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@freefall.freebsd.org Subject: Re: Panic: "lockmgr: pid %d, not %s %d unlocking" References: <199703292117.NAA13611@freefall.freebsd.org> <199703292153.NAA00536@austin.polstra.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703292153.NAA00536@austin.polstra.com>; from John Polstra on Mar 29, 1997 13:53:25 -0800 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As John Polstra wrote: > > How come the panic message wasn't expanded? > > The original panic message that came out on the console was expanded. > The output I included in my posting came from running "gdb -k" later, on > the kernel + crash dump. I guess it's not expanded at that point. You should be able to figure out the message buffer contents with gdb -k, albeit it's tricky if you have no -g symbols. dmesg also knows how to handle ``dead kernels''. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)