From owner-freebsd-current Sun May 6 2:20:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 65F0C37B424; Sun, 6 May 2001 02:20:09 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id LAA23715; Sun, 6 May 2001 11:20:08 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f469JrT07865; Sun, 6 May 2001 11:19:53 +0200 (MET DST) (envelope-from j) Date: Sun, 6 May 2001 11:19:53 +0200 (MET DST) Message-Id: <200105060919.f469JrT07865@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: freebsd-scsi@freebsd.org Organization: Private BSD site, Dresden 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 References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> <15083.65379.523173.371122@ultrahot.Finland.Sun.COM> <20010430101214.A46826@panzer.kdm.org> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: camcontrol stop / restart broken X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org, freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [F'up changed to freebsd-scsi] "Kenneth D. Merry" wrote: > This should be fixed as of rev 1.22 of scsi_all.c. There was an errant > search and replace that caused the 'start' bit in the start/stop unit to > always be set to 0 (stop). So automatic spinups wouldn't work, and > 'camcontrol start' wouldn't work. I've got: uriah # cvs stat /sys/cam/scsi/scsi_all.c =================================================================== File: scsi_all.c Status: Up-to-date Working revision: 1.24 Result of merge Repository revision: 1.24 /home/ncvs/src/sys/cam/scsi/scsi_all.c,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) ....and still have the problem that the "camcontrol start" doesn't work. It returns immediately to the caller, claiming a "unit started successfully", while the drive hasn't started at all. Issuing a "camcontrol command daX -c '1b 0 0 0 1 0'" works. I didn't try whether the kernel-implied startup on disk access would work, though, since it would IMHO risk a hanging kernel and controller timeout. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 4:40:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (cvsup2.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id CF20E37B422 for ; Sun, 6 May 2001 04:40:26 -0700 (PDT) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: (from uucp@localhost) by rina.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W-rina.r-20010412) with UUCP id f467W9906382 ; Sun, 6 May 2001 16:32:09 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp [fec0::1:280:c8ff:fe6b:6d73]) by sohgo.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W) with ESMTP id f467V9J02279 ; Sun, 6 May 2001 16:31:09 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W) with ESMTP id f467V4g13184 ; Sun, 6 May 2001 16:31:07 +0900 (JST) Message-Id: <200105060731.f467V4g13184@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Date: Sun, 06 May 2001 16:31:02 +0900 From: Seigo Tanimura To: current@FreeBSD.org Subject: select(2) converted to use a condition variable, and optimised Cc: Seigo Tanimura User-Agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As conversion of select(2) from msleep(9) to a condition variable is in the SMPng TODO list, I have done that task. Also, we do not have to lock a process in order to evaluate the result of {sel,poll}scan() and the remaining time of {select,poll}(2). It should be enough to do those pieces of work first, followed by locking a process and wait for a condition variable or selwakeup(). Those changes are in the patch at: http://people.FreeBSD.org/~tanimura/patches/selectopt.diff -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 4:47:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-108.dsl.lsan03.pacbell.net [63.207.60.108]) by hub.freebsd.org (Postfix) with ESMTP id AEF7137B424 for ; Sun, 6 May 2001 04:47:32 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3A9C967A8C; Sun, 6 May 2001 04:47:24 -0700 (PDT) Date: Sun, 6 May 2001 04:47:24 -0700 From: Kris Kennaway To: Dennis Glatting Cc: freebsd-stable@frebsd.org, freebsd-current@freebsd.org Subject: Re: pgm to kill 4.3 via vm Message-ID: <20010506044724.A24309@xor.obsecurity.org> References: <20010505143035.O613-100000@btw.plaintalk.bellevue.wa.us> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010505143035.O613-100000@btw.plaintalk.bellevue.wa.us>; from dennis.glatting@software-munitions.com on Sat, May 05, 2001 at 02:37:07PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 05, 2001 at 02:37:07PM -0700, Dennis Glatting wrote: >=20 > I wrote a trivial program to fill vm and found I can reliably freeze my > system. It may not work on the first attempt, but certainly within three. > My command line is: >=20 > a.out&;a.out&;a.out&;a.out&;a.out& >=20 > The goal of my program is simply to see how the system behaves under > memory exhaustion which, as it turns out on two similar systems, the > systems freeze. Specifically, I can switch between consoles but the login > prompts do not respond and the system does not respond on the network. >=20 > I am running 4.3 on a dual processor system. >=20 > Below are some things. First, the program. Second, dmesg. Finally, my > /etc/rc.config. What resource limits have you set? Kris --LZvS9be/3tNcYl/X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE69TnLWry0BWjoQKURAopoAKDA2MwoPVkBSrIu++uKW9j+RRfp2ACfSVOE DZCLZvY8rONfEGDhSai2Wfs= =hL7O -----END PGP SIGNATURE----- --LZvS9be/3tNcYl/X-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 6: 5: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (f98.law4.hotmail.com [216.33.149.98]) by hub.freebsd.org (Postfix) with ESMTP id 3491D37B422 for ; Sun, 6 May 2001 06:05:04 -0700 (PDT) (envelope-from messiah_man@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 6 May 2001 06:05:04 -0700 Received: from 212.97.250.29 by lw4fd.law4.hotmail.msn.com with HTTP; Sun, 06 May 2001 13:05:03 GMT X-Originating-IP: [212.97.250.29] From: "Munish Chopra" To: freebsd-current@freebsd.org Subject: The FreeBSD NVIDIA Driver Initiative Date: Sun, 06 May 2001 15:05:03 +0200 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 06 May 2001 13:05:04.0140 (UTC) FILETIME=[2A81DCC0:01C0D62D] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If the following isn't an appropriate subject for discussion on this particular mailing list, please move ensuing discussion to one that is more appropriate (possibly -hackers or -hardware). We are a simply a few guys who at more or less the same time got tired of not having 3D-support for our NVIDIA cards in FreeBSD. So we decided to start 'The FreeBSD NVIDIA Driver Initiative'. As the name may say, we tried to figure out how we were going to get hardware accelerated 3D drivers for FreeBSD. After going through a bit of work and contacting NVIDIA, it's come to this: We are located at http://nvidia.netexplorer.org, from where we try to keep people updated on how the effort is going. We have taken over Michael Carlson's petition for drivers (some of you may remember it from when it was started back in January), and if you haven't signed it yet, please come on over and do. There IS currently a team working on the drivers (not NVIDIA itself, but some people who are getting a bit of help from NVIDIA at least). We will keep you updated on how things go. For those of you wondering about the legal issues, they DID come up, and have been successfully resolved. Please drop by the site to sign the petition and check on how things are going. Cheers, Munish Chopra The FreeBSD NVIDIA Driver Initiative _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 7: 9: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from EnContacto.Net (adsl-63-205-16-205.dsl.mtry01.pacbell.net [63.205.16.205]) by hub.freebsd.org (Postfix) with ESMTP id C2FA037B422 for ; Sun, 6 May 2001 07:09:02 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Received: (from root@localhost) by EnContacto.Net (8.11.3/8.11.3) id f46E92b54573 for current@FreeBSD.Org; Sun, 6 May 2001 07:09:02 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Received: from 63.205.16.202 ( [63.205.16.202]) as user eculp@EnContacto.Net by Mail.PasionLatina.Org with HTTP; Sun, 6 May 2001 07:09:01 -0700 Message-ID: <989158141.3af55afd9161d@Mail.PasionLatina.Org> Date: Sun, 6 May 2001 07:09:01 -0700 From: "Edwin L. Culp" To: current@FreeBSD.Org Subject: Make world's stoping perl MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs X-Originating-IP: 63.205.16.202 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For a couple of days now my make worlds on all my machines are stopping with the following error. I haven't seen anything on the list about anyone else having a problem. syntax error at lib/SelfLoader.pm line 69, at EOF Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm line 17. Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line 37.Compilation failed in require at /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. *** Error code 255 Stop in /usr/src/gnu/usr.bin/perl/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Thanks, ed ----------------------------------------------------------------------- The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn and relearn. --Alvin Toffler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 7:29:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 38FD737B422 for ; Sun, 6 May 2001 07:29:32 -0700 (PDT) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id QAA16528; Sun, 6 May 2001 16:29:30 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 14wPXM-0000AJ-00 for ; Sun, 06 May 2001 16:29:28 +0200 Date: Sun, 6 May 2001 16:29:28 +0200 From: Szilveszter Adam To: current@FreeBSD.Org Subject: Re: Make world's stoping perl Message-ID: <20010506162928.A30958@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , current@FreeBSD.Org References: <989158141.3af55afd9161d@Mail.PasionLatina.Org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <989158141.3af55afd9161d@Mail.PasionLatina.Org>; from eculp@EnContacto.Net on Sun, May 06, 2001 at 07:09:01AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, May 06, 2001 at 07:09:01AM -0700, Edwin L. Culp wrote: > For a couple of days now my make worlds on all my machines are stopping with > the following error. I haven't seen anything on the list about anyone else > having a problem. > > syntax error at lib/SelfLoader.pm line 69, at EOF > Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm > line 17. > Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. > BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line > 37.Compilation failed in require at > /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. > *** Error code 255 Hello, You need the patch from the message: <200105022124.f42LOup61232@gratis.grondar.za> by markm. Apply it to the /usr/libdata/perl/BSDPAN dir. Not to the sources, the installed version, because it is faulty. -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 7:53:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id E502637B422 for ; Sun, 6 May 2001 07:53:18 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f46ErGf35367 for ; Sun, 6 May 2001 10:53:16 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 6 May 2001 10:53:16 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Subject: Garbage during serial console login on recent -CURRENT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just updated a box to a recent -CURRENT (first Thursday, then today), and have been having the following problem for its serial console login: FreeBSD/i386 (dev.TrustedBSD.org) (ttyd0) =95=95gin: MK=C2=B2aB"=95=D9=C9=D5=CD=D1=95=91 Mz=C9=EB=CBKa=FE FreeBSD/i386 (dev.TrustedBSD.org) (ttyd0) =95=95gin: MJ=C2=B2aB"=95=D9=C9=D5=CD=D1=95=91 Mz=C9=EB=CBKa=FE~. I can type fine, and once I login, I experience no problems, but during the login process, it likes to spit garbage at me. Was wondering if anyone else had experienced this? Essentially, the serial console on this box was configured by enabling ttyd0 and setting -P in boot.config. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 8:29:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 622D937B424 for ; Sun, 6 May 2001 08:29:30 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f46FTRi17248; Sun, 6 May 2001 08:29:27 -0700 (PDT) Date: Sun, 6 May 2001 08:29:27 -0700 From: Alfred Perlstein To: Seigo Tanimura Cc: current@FreeBSD.ORG Subject: Re: select(2) converted to use a condition variable, and optimised Message-ID: <20010506082927.P18676@fw.wintelcom.net> References: <200105060731.f467V4g13184@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105060731.f467V4g13184@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp>; from tanimura@r.dl.itc.u-tokyo.ac.jp on Sun, May 06, 2001 at 04:31:02PM +0900 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Seigo Tanimura [010506 04:40] wrote: > As conversion of select(2) from msleep(9) to a condition variable is > in the SMPng TODO list, I have done that task. > > Also, we do not have to lock a process in order to evaluate the result > of {sel,poll}scan() and the remaining time of {select,poll}(2). It > should be enough to do those pieces of work first, followed by locking > a process and wait for a condition variable or selwakeup(). > > Those changes are in the patch at: > > http://people.FreeBSD.org/~tanimura/patches/selectopt.diff Please do not remove the spl calls, they serve as a useful guide for making finer grained locks as well as error checking the new locks. -- -Alfred Perlstein - [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 10:52:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 3652C37B423; Sun, 6 May 2001 10:52:45 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA94785; Sun, 6 May 2001 11:52:44 -0600 (MDT) (envelope-from ken) Date: Sun, 6 May 2001 11:52:44 -0600 From: "Kenneth D. Merry" To: freebsd-scsi@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: camcontrol stop / restart broken Message-ID: <20010506115244.A94763@panzer.kdm.org> References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> <15083.65379.523173.371122@ultrahot.Finland.Sun.COM> <20010430101214.A46826@panzer.kdm.org> <200105060919.f469JrT07865@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200105060919.f469JrT07865@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Sun, May 06, 2001 at 11:19:53AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, May 06, 2001 at 11:19:53 +0200, J Wunsch wrote: > [F'up changed to freebsd-scsi] > > "Kenneth D. Merry" wrote: > > > This should be fixed as of rev 1.22 of scsi_all.c. There was an errant > > search and replace that caused the 'start' bit in the start/stop unit to > > always be set to 0 (stop). So automatic spinups wouldn't work, and > > 'camcontrol start' wouldn't work. > > I've got: > > uriah # cvs stat /sys/cam/scsi/scsi_all.c > =================================================================== > File: scsi_all.c Status: Up-to-date > > Working revision: 1.24 Result of merge > Repository revision: 1.24 /home/ncvs/src/sys/cam/scsi/scsi_all.c,v > Sticky Tag: (none) > Sticky Date: (none) > Sticky Options: (none) > > ....and still have the problem that the "camcontrol start" doesn't > work. It returns immediately to the caller, claiming a "unit started > successfully", while the drive hasn't started at all. camcontrol uses scsi_start_stop() to build the start unit CDB. scsi_start_stop() is in libcam, which compiles a number of kernel files in userland. (including scsi_all.c) So you need to rebuild world to fix camcontrol. > Issuing a "camcontrol command daX -c '1b 0 0 0 1 0'" works. That bypasses the CDB builder function (scsi_start_stop()), so I would expect it to work. > I didn't try whether the kernel-implied startup on disk access would > work, though, since it would IMHO risk a hanging kernel and controller > timeout. That should work now. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 10:58:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88]) by hub.freebsd.org (Postfix) with ESMTP id B829637B424 for ; Sun, 6 May 2001 10:58:07 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from surriel.ddts.net (unknown [200.181.137.248]) by netbank.com.br (Postfix) with ESMTP id 960A44681B; Sun, 6 May 2001 14:59:10 -0300 (BRST) Received: from localhost (ouyylc@localhost [127.0.0.1]) by surriel.ddts.net (8.11.3/8.11.2) with ESMTP id f46Hvbi13197; Sun, 6 May 2001 14:57:38 -0300 Date: Sun, 6 May 2001 14:57:37 -0300 (BRST) From: Rik van Riel X-Sender: riel@imladris.rielhome.conectiva To: Kris Kennaway Cc: Dennis Glatting , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm In-Reply-To: <20010506044724.A24309@xor.obsecurity.org> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 6 May 2001, Kris Kennaway wrote: > On Sat, May 05, 2001 at 02:37:07PM -0700, Dennis Glatting wrote: > > > > I wrote a trivial program to fill vm and found I can reliably freeze my > > system. It may not work on the first attempt, but certainly within three. > > My command line is: > > > > a.out&;a.out&;a.out&;a.out&;a.out& > > What resource limits have you set? In theory, the code at line 1124 and further in vm_pageout.c should kill of of these processes and allow the system to survive. The only way for the system to die is if this code was broken by a recent change in the system... [but yes, on a production system you'd want to run with sane resource limits] regards, Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://distro.conectiva.com/ Send all your spam to aardvark@nl.linux.org (spam digging piggy) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 11:36:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from kalaid.f2f.com.ua (kalaid.f2f.com.ua [62.149.0.33]) by hub.freebsd.org (Postfix) with ESMTP id B5E2337B423 for ; Sun, 6 May 2001 11:36:27 -0700 (PDT) (envelope-from sobomax@mail-in.net) Received: from Mail-In.Net (borey.f2f.com.ua [62.149.0.24]) by kalaid.f2f.com.ua (8.11.1/8.11.1) with ESMTP id f46Id2520416 for ; Sun, 6 May 2001 21:39:10 +0300 (EEST) (envelope-from sobomax@mail-in.net) Received: from notebook.vega.com (das0-l109.uic-in.net [212.35.189.236]) by Mail-In.Net (8.11.3/8.H.Z) with ESMTP id f46Ias078636 for ; Sun, 6 May 2001 21:36:55 +0300 (EEST) Date: Sun, 6 May 2001 21:36:55 +0300 (EEST) Message-Id: <200105061836.f46Ias078636@Mail-In.Net> To: current@FreeBSD.org From: Maxim Sobolev Reply-To: sobomax@FreeBSD.org Subject: world is broken in tcpdump X-Mailer: Pygmy (v0.5.5) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that the world cvsup'ed several hours ago is broken in tcpdump. Please fix. -Maxim cc -pipe -O -mpreferred-stack-boundary=2 -march=k6 -I/usr/src/usr.sbin/tcpdump/t cpdump -I/usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/lbl -DHAVE_C ONFIG_H -I/shares/UF/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/tcpdump /tcpdump/../../../contrib/tcpdump/tcpdump.c cc -pipe -O -mpreferred-stack-boundary=2 -march=k6 -I/usr/src/usr.sbin/tcpdump/t cpdump -I/usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/lbl -DHAVE_C ONFIG_H -I/shares/UF/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/tcpdump /tcpdump/../../../contrib/tcpdump/util.c cc -pipe -O -mpreferred-stack-boundary=2 -march=k6 -I/usr/src/usr.sbin/tcpdump/t cpdump -I/usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/lbl -DHAVE_C ONFIG_H -I/shares/UF/obj/usr/src/i386/usr/include -c version.c cc -pipe -O -mpreferred-stack-boundary=2 -march=k6 -I/usr/src/usr.sbin/tcpdump/t cpdump -I/usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/lbl -DHAVE_C ONFIG_H -I/shares/UF/obj/usr/src/i386/usr/include -o tcpdump addrtoname.o gmt 2local.o machdep.o parsenfsfh.o print-ah.o print-arp.o print-ascii.o print-atalk .o print-atm.o print-bgp.o print-bootp.o print-bxxp.o print-cdp.o print-chdlc.o print-cip.o print-cnfp.o print-decnet.o print-dhcp6.o print-domain.o print-dvmrp .o print-egp.o print-esp.o print-ether.o print-fddi.o print-frag6.o print-gre.oprint-icmp.o print-icmp6.o print-igmp.o print-igrp.o print-ip.o print-ip6.o print-ip6opts.o print-ipcomp.o print-ipx.o print-isakmp.o print-isoclns.o print-krb.o print-l2tp.o print-lane.o print-lcp.o print-llc.o print-mobile.o print-nfs.o print-ntp.o print-null.o print-ospf.o print-ospf6.o print-pim.o print-ppp.o print-pppoe.o print-radius.o print-raw.o print-rip.o print-ripng.o print-rt6.o print-rx.o print-sl.o print-sll.o print-smb.o print-snmp.o print-stp.o print-sunrpc.o print-tcp.o print-telnet.o print-tftp.o print-timed.o print-token.o print-udp.o print-vjc.o print-vrrp.o print-wb.o savestr.o setsignal.o smbutil.o tcpdump.o util.o version.o -ll -lpcap print-dhcp6.o: In function `dhcp6_print': print-dhcp6.o(.text+0x383): undefined reference to `ip6addr_string' print-dhcp6.o(.text+0x397): undefined reference to `ip6addr_string' print-dhcp6.o(.text+0x40f): undefined reference to `ip6addr_string' print-dhcp6.o(.text+0x423): undefined reference to `ip6addr_string' print-dhcp6.o(.text+0x43a): undefined reference to `ip6addr_string' print-dhcp6.o(.text+0x4d1): more undefined references to `ip6addr_string' follow *** Error code 1 Stop in /usr/src/usr.sbin/tcpdump/tcpdump. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 12: 8: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 450A537B422 for ; Sun, 6 May 2001 12:08:03 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14wTsp-0001ee-00; Sun, 06 May 2001 21:07:55 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id VAA24366; Sun, 6 May 2001 21:07:52 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 24342; Sun May 6 21:07:43 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14wTsd-000LDX-00; Sun, 06 May 2001 21:07:43 +0200 To: Kris Kennaway Cc: Dennis Glatting , freebsd-stable@frebsd.org, freebsd-current@freebsd.org Subject: Re: pgm to kill 4.3 via vm In-reply-to: Your message of "Sun, 06 May 2001 04:47:24 MST." <20010506044724.A24309@xor.obsecurity.org> Date: Sun, 06 May 2001 21:07:43 +0200 Message-ID: <81562.989176063@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 06 May 2001 04:47:24 MST, Kris Kennaway wrote: > What resource limits have you set? While that's a reasonable question when you're in a support role, I'd certainly like to hear whether "FreeBSD freezes on memory exhaustion" is something people "should just live with" or whether it's symptomatic of a bug that someone might one day want to fix but which folks should, for now, protect themselves against using resource limits. From my recollection of past threads, it was my understanding that having the operating system (though not all processes) "live through" memory starvation was feasible. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 12:15:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhotel.chrillesen.dk (vax.chrillesen.dk [193.88.12.35]) by hub.freebsd.org (Postfix) with ESMTP id 8B71637B422 for ; Sun, 6 May 2001 12:15:29 -0700 (PDT) (envelope-from jach@mailhotel.chrillesen.dk) Received: by mailhotel.chrillesen.dk (Postfix, from userid 1000) id F36DA5EC6; Sun, 6 May 2001 21:15:22 +0200 (CEST) Date: Sun, 6 May 2001 21:15:22 +0200 From: Jan Chrillesen To: current@FreeBSD.org Subject: Thinkpad locks up with current Message-ID: <20010506211522.Z18438@vax.chrillesen.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-editor: vim, http://www.vim.org/ Organization: Men in black T-shirts that dont shave Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday I cvsup'et my Thinkpad 600E to current and during bootup it locks up. It's totally dead - flipping the powerswitch on the laptop is not enough - I need to remove the battery. The problem seems to be PCMCIA related. If I remove the PCMCIA cards it boot and runs for some time, then locks up again. As soon as I insert a card (tried Cisco Aironet 340 and Xircom REM56G-100) it locks up. I did another cvsup and buildworld today, but things are still b0rken. If I boot the old 4.2 GENERIC kernel that's still on the drive it runs OK and I can build the world, so it's not a hardware issue. /Jan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 13:49:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88]) by hub.freebsd.org (Postfix) with ESMTP id 5B2D937B422 for ; Sun, 6 May 2001 13:49:07 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from surriel.ddts.net (unknown [200.181.137.248]) by netbank.com.br (Postfix) with ESMTP id D0E5846822; Sun, 6 May 2001 17:50:10 -0300 (BRST) Received: from localhost (olnars@localhost [127.0.0.1]) by surriel.ddts.net (8.11.3/8.11.2) with ESMTP id f46Kmui19468; Sun, 6 May 2001 17:48:56 -0300 Date: Sun, 6 May 2001 17:48:54 -0300 (BRST) From: Rik van Riel X-Sender: riel@imladris.rielhome.conectiva To: Sheldon Hearn Cc: Kris Kennaway , Dennis Glatting , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm In-Reply-To: <81562.989176063@axl.fw.uunet.co.za> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 6 May 2001, Sheldon Hearn wrote: > On Sun, 06 May 2001 04:47:24 MST, Kris Kennaway wrote: > > > What resource limits have you set? > > While that's a reasonable question when you're in a support role, I'd > certainly like to hear whether "FreeBSD freezes on memory exhaustion" is > something people "should just live with" or whether it's symptomatic of > a bug that someone might one day want to fix but which folks should, for > now, protect themselves against using resource limits. > > From my recollection of past threads, it was my understanding that > having the operating system (though not all processes) "live through" > memory starvation was feasible. The code is there, look at src/sys/vm/vm_pageout.c, line 1124 and further... Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://distro.conectiva.com/ Send all your spam to aardvark@nl.linux.org (spam digging piggy) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 16:16:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id DC77937B42C for ; Sun, 6 May 2001 16:16:43 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id JAA29981 for ; Mon, 7 May 2001 09:16:35 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01K39ZP0KIIOV6KWEL@cim.alcatel.com.au> for current@freebsd.org; Mon, 7 May 2001 09:16:34 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f46NGWk89712 for current@freebsd.org; Mon, 07 May 2001 09:16:32 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Mon, 07 May 2001 09:16:31 +1000 From: Peter Jeremy Subject: ssh reports "no RSA support in libssl and libcrypto." To: current@freebsd.org Mail-Followup-To: current@freebsd.org Message-id: <20010507091631.H59150@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Having built and installed -current from last Friday, I find that ssh* is now reporting "no RSA support in libssl and libcrypto. See ssl(8)" and will only talk SSH2. I couldn't find anything relevant in ssl(8). I haven't specified "WITH_RSA=NO" anywhere and checking through the build logs, there's no sign of "-DNO_RSA". libcrypto.a contains an RSA_generate_key() which doesn't look like a stub. Does anyone have any ideas? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 16:35: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta-02-uk.srv.ic5.net (pc175-ren13.cable.ntl.com [62.255.161.175]) by hub.freebsd.org (Postfix) with ESMTP id 38CBE37B422 for ; Sun, 6 May 2001 16:34:54 -0700 (PDT) (envelope-from johnm@ic5.net) Received: from coda (coda-h20.wst.ic5.net [10.1.1.20]) by mta-02-uk.srv.ic5.net (8.11.3/8.11.3) with SMTP id f46Nfxj31239 for ; Mon, 7 May 2001 00:42:00 +0100 (BST) (envelope-from johnm@ic5.net) From: "John McGarrigle" To: Subject: using CVS to keep ports up to date. Date: Mon, 7 May 2001 00:34:52 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, I don't use CVS much (if at all) and I was wondering if anyone could give me a sample command that would update /usr/ports to the -stable branch.. I'd like a command that I can put in a cron and let it get on with it every day.. or maybe add it to the weekly run or something... Anyway... I know it can be done.. I just don't know the command(s) needed to do it ;) Thanks, ---- John 'Neuron' McGarrigle Email: johnm@ic5.net ICQ: 18220396 Phone: +44 (0)7944 604 644 ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 17: 3: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 0F92337B423 for ; Sun, 6 May 2001 17:02:57 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f4702mO49976; Sun, 6 May 2001 17:02:48 -0700 (PDT) Date: Sun, 6 May 2001 17:02:48 -0700 (PDT) From: David Wolfskill Message-Id: <200105070002.f4702mO49976@bunrab.catwhisker.org> To: freebsd-current@FreeBSD.ORG, johnm@ic5.net Subject: Re: using CVS to keep ports up to date. In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: "John McGarrigle" >Date: Mon, 7 May 2001 00:34:52 +0100 >I don't use CVS much (if at all) and I was wondering if anyone could give me >a sample command that would update /usr/ports to the -stable branch.. I'd >like a command that I can put in a cron and let it get on with it every >day.. or maybe add it to the weekly run or something... Well, it depends somewhat on where the CVS repository is that you intend to use. And it's my understanding that ports isn't branched (to reflect -STABLE, -CURRENt or anything else). >Anyway... I know it can be done.. I just don't know the command(s) needed to >do it ;) I'll append a copy of the script I use after my .sig. A couple of notes: * It's a "shar" file, to facilitate extraction even for folks who use MIME-challenged MUAs (like me). * I use cvsup14.freebsd.org. It seems to work well for me; most folks should probably use other mirrors. * I'm maintaining a local CVS repository, and I update various trees from that. (I maintain separate environments (including source trees) for each of -CURRENT and -STABLE, as well as the ports.) * It seemed to me (as I saw various folks' reports of breakages with -CURRENT, particularly) that it might be useful to be able to report -- with a fair degree of precision -- when my repository was last updated, and from which mirror. Accordingly, I set up the script to log that activity to facilitate that. It also (separately) logs everything it does, so I can review that activity. * The script is derived from one in use at work, which had been last hacked by Julian (Elischer) before I got to it. (Thanks, Julian!) * I invoke the script via cron with the -p flag, which tells it to go ahead and update /usr/ports after updating my CVS repository. (I split that function out because of one too many times I wanted to update my CVS repository (in order to get some changes that might allow -CURRENT to build, for example), but I didn't necessarily want to take the time to update /usr/ports.) If it works for you after suitable modifications for your situation), great. Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # cvsup.daily # echo x - cvsup.daily sed 's/^X//' >cvsup.daily << 'END-of-cvsup.daily' X#!/bin/sh - X# X# @(#)daily.local 5.12 (Berkeley) 5/24/91 X# X#set -x X XPATH=/bin:/usr/bin:/sbin:/usr/sbin X X X X# X# Refresh the cvs tree. X# X# echo "cvSup'ing FreeBSD source tree:" Xdo_ports="" Xwhile getopts "p" COMMAND_LINE_ARGUMENT ; do X case "${COMMAND_LINE_ARGUMENT}" in X p) X do_ports="yes" X ;; X esac Xdone XCVSROOT=/cvs;export CVSROOT XFBSDROOT=${CVSROOT}/freebsd XLOG=/var/tmp/cvsup.log XH_LOG=/var/log/cvsup-history.log X# SERVER=cvsup6 XSERVER=cvsup14 Xumask 002 XSUPFILE=/tmp/$$.supfile XRELEASE="release=cvs" XHOST="host=${SERVER}.FreeBSD.org" XHOSTBASE="hostbase=/home" XBASE="base=/cvs/freebsd" XPREFIX="prefix=/cvs/freebsd" XOPTIONS="delete old use-rel-suffix" X XARGS="${RELEASE} ${HOST} ${HOSTBASE} ${BASE} ${PREFIX} ${OPTIONS}" X Xcat >${SUPFILE} <>${H_LOG} X /usr/local/bin/cvsup -g -L1 -P - ${SUPFILE} >$LOG 2>&1 X echo "CVSup ended from ${SERVER}.freebsd.org at `date`" >>${H_LOG} X echo "CVSup ended from ${SERVER}.freebsd.org at `date`" >>${LOG} X# chgrp -R staff ${FBSDROOT} >>$LOG 2>&1 X# chmod -R g+rw ${FBSDROOT} >>$LOG 2>&1 X if [ "${do_ports}" = "yes" ]; then X cd /usr/ports && cvs update -d >>$LOG 2>&1 X echo "/usr/ports update ended at `date`" >>${LOG} X else X echo "/usr/ports update skipped at `date`" >>${LOG} X fi Xfi Xrm ${SUPFILE} END-of-cvsup.daily exit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 20:16: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.originative.co.uk (mailgate.originative.co.uk [62.232.68.68]) by hub.freebsd.org (Postfix) with ESMTP id 39B4B37B422 for ; Sun, 6 May 2001 20:15:59 -0700 (PDT) (envelope-from paul@freebsd-services.co.uk) Received: from lobster.originative.co.uk (lobster [62.232.68.81]) by mailgate.originative.co.uk (Postfix) with ESMTP id 4C5181D162 for ; Mon, 7 May 2001 04:15:58 +0100 (BST) Date: Mon, 07 May 2001 04:16:16 +0100 From: Paul Richards To: current@freebsd.org Subject: Lots of interrupts! Message-ID: <95980000.989205376@lobster.originative.co.uk> X-Mailer: Mulberry/2.0.8 (Linux/x86 Demo) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My dev box seems to be a bit sick and has been for a day or two. If anything disk intensive is taking place, and it seems to be particularly when gzipping/unzipping files, say when building mozilla during the extract step, things start to crawl and I'm seeing hundreds (500-1200) of interrupts a second for ata0 in vmstat. A network transfer at the same time, just scp a file across my 100M LAN, crawls at around 20k/s with 50-100 interrupts/s. Is anyone else seeing anything like this? Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 20:25:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 3626937B424; Sun, 6 May 2001 20:25:47 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id FAA49489; Mon, 7 May 2001 05:25:41 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Akinori MUSHA" Cc: FreeBSD-current , "Brian F. Feldman" Subject: Re: OpenSSH 2.9 problems References: <86g0ekxevw.wl@archon.local.idaemons.org> From: Dag-Erling Smorgrav Date: 07 May 2001 05:25:41 +0200 In-Reply-To: <86g0ekxevw.wl@archon.local.idaemons.org> Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Akinori MUSHA" writes: > 1. Sshd fails to authenticate via PAM. > > May 5 19:18:07 archon sshd[803]: fatal: PAM setcred failed[6]: Permission denied PAM fuckup, not OpenSSH's fault. You'll get the same error trying to su from root to a non-root user. > 3. Somehow the default location of the ssh host key files has been > changed from /etc/ssh to /etc. Was it intentional? That has been fixed. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 20:30:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 9003037B42C for ; Sun, 6 May 2001 20:30:14 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id FAA49503; Mon, 7 May 2001 05:30:09 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: lock order reversals, anyone? References: From: Dag-Erling Smorgrav Date: 07 May 2001 05:30:09 +0200 In-Reply-To: Message-ID: Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob writes: > > pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped) > (oh, yeah, a 4.1 built executable is dying, charming) That may well be a bug in your app. Xscreensaver, for instance, is riddled with dangling-pointer and off-by-one bugs that rarely (if ever) show up on -STABLE, but result in an immediate core dump on -CURRENT because it has malloc() debugging enabled by default. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 21:45:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B827837B422 for ; Sun, 6 May 2001 21:45:29 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id VAA16766; Sun, 6 May 2001 21:45:26 -0700 Date: Sun, 6 May 2001 21:45:25 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: lock order reversals, anyone? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Possible. On 7 May 2001, Dag-Erling Smorgrav wrote: > Matthew Jacob writes: > > > pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped) > > (oh, yeah, a 4.1 built executable is dying, charming) > > That may well be a bug in your app. Xscreensaver, for instance, is > riddled with dangling-pointer and off-by-one bugs that rarely (if > ever) show up on -STABLE, but result in an immediate core dump on > -CURRENT because it has malloc() debugging enabled by default. > > DES > -- > Dag-Erling Smorgrav - des@ofug.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 22: 2:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8B9E937B422 for ; Sun, 6 May 2001 22:02:37 -0700 (PDT) (envelope-from leifn@vicky.neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.11.2/8.11.2) id f4752Zv30874 for current@FreeBSD.ORG.AVP; Mon, 7 May 2001 07:02:35 +0200 (CEST) (envelope-from leifn@vicky.neland.dk) Received: from vicky.neland.dk (uucp@localhost) by ns.internet.dk (8.11.2/8.11.2) with UUCP id f4752Y430860; Mon, 7 May 2001 07:02:34 +0200 (CEST) (envelope-from leifn@vicky.neland.dk) Received: from localhost (leifn@localhost) by vicky.neland.dk (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id AAA08464; Mon, 7 May 2001 00:09:49 +0200 Date: Mon, 7 May 2001 00:09:45 +0200 (CEST) From: To: Szilveszter Adam Cc: FreeBSD.ORG!current@vicky.neland.dk Subject: Re: Make world's stoping perl In-Reply-To: <20010506162928.A30958@petra.hos.u-szeged.hu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 6 May 2001, Szilveszter Adam wrote: > On Sun, May 06, 2001 at 07:09:01AM -0700, Edwin L. Culp wrote: > > For a couple of days now my make worlds on all my machines are stopping with > > the following error. I haven't seen anything on the list about anyone else > > having a problem. > > > > syntax error at lib/SelfLoader.pm line 69, at EOF > > Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm > > line 17. > You need the patch from the message: > > <200105022124.f42LOup61232@gratis.grondar.za> > Is this supposed to help locate the patch? If so, how? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 22:52:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 83EF237B422 for ; Sun, 6 May 2001 22:52:18 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f475q2b05020; Sun, 6 May 2001 23:52:08 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200105070552.f475q2b05020@harmony.village.org> To: Jan Chrillesen Subject: Re: Thinkpad locks up with current Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 06 May 2001 21:15:22 +0200." <20010506211522.Z18438@vax.chrillesen.dk> References: <20010506211522.Z18438@vax.chrillesen.dk> Date: Sun, 06 May 2001 23:52:02 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OLDCARD or NEWCARD? If oldcard, are you using the identical configuration as you are on 4.2? The same irq for the pcic device, the same irq list in /etc/pccard.conf, the same memory ranges in /etc/pccard.conf, etc. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 22:53:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-108.dsl.lsan03.pacbell.net [63.207.60.108]) by hub.freebsd.org (Postfix) with ESMTP id AA52C37B422 for ; Sun, 6 May 2001 22:53:07 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BDC1666D82; Sun, 6 May 2001 22:53:06 -0700 (PDT) Date: Sun, 6 May 2001 22:53:06 -0700 From: Kris Kennaway To: Peter Jeremy Cc: current@freebsd.org Subject: Re: ssh reports "no RSA support in libssl and libcrypto." Message-ID: <20010506225306.A46294@xor.obsecurity.org> References: <20010507091631.H59150@gsmx07.alcatel.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010507091631.H59150@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Mon, May 07, 2001 at 09:16:31AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 07, 2001 at 09:16:31AM +1000, Peter Jeremy wrote: > Having built and installed -current from last Friday, I find that ssh* > is now reporting "no RSA support in libssl and libcrypto. See ssl(8)" > and will only talk SSH2. I couldn't find anything relevant in ssl(8). >=20 > I haven't specified "WITH_RSA=3DNO" anywhere and checking through the > build logs, there's no sign of "-DNO_RSA". libcrypto.a contains an > RSA_generate_key() which doesn't look like a stub. >=20 > Does anyone have any ideas? Check the archives, this is a FAQ with probably the usual answer. Kris --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE69jhBWry0BWjoQKURAvKXAJ9SYgEQMl6QgmL9XMGROum+NMFX2gCeMxvI jzPQAjMybg7BuwM4ZslYpf0= =eh+r -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 23: 4:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from beastie.saturn-tech.com (beastie.saturn-tech.com [207.229.19.136]) by hub.freebsd.org (Postfix) with ESMTP id C1BE537B423 for ; Sun, 6 May 2001 23:04:12 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by beastie.saturn-tech.com (8.11.1/8.11.0) with ESMTP id f477L5x99399; Mon, 7 May 2001 01:21:05 -0600 (MDT) (envelope-from drussell@saturn-tech.com) X-Authentication-Warning: beastie.saturn-tech.com: drussell owned process doing -bs Date: Mon, 7 May 2001 01:21:04 -0600 (MDT) From: Doug Russell To: leifn@vicky.neland.dk Cc: current@freebsd.org Subject: Re: Make world's stoping perl In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You need the patch from the message: > > > > <200105022124.f42LOup61232@gratis.grondar.za> > > > Is this supposed to help locate the patch? > If so, how? Hehe.. That isn't the best way to identify something, is it? You can use the search located at: http://www.freebsd.org/search/search-mid.html Or, follow this link, since I looked it up: http://www.freebsd.org/cgi/getmsg.cgi?fetch=192223+0+/usr/local/www/db/text/2001/freebsd-current/20010506.freebsd-current Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 23: 8:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from matrix.levels.unisa.edu.au (matrix.levels.unisa.edu.au [130.220.36.212]) by hub.freebsd.org (Postfix) with ESMTP id 696CD37B422 for ; Sun, 6 May 2001 23:08:21 -0700 (PDT) (envelope-from benjsc@matrix.levels.unisa.edu.au) Received: from localhost (benjsc@localhost) by matrix.levels.unisa.edu.au (8.11.0/8.11.0) with ESMTP id f47Ffsl21084 for ; Tue, 8 May 2001 01:11:54 +0930 Date: Tue, 8 May 2001 01:11:54 +0930 (CST) From: To: Subject: IDE probing Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I have an interesting problem in current. My DVD drive is not detected using any kernel unless I enter the visual kernel config program. It is very weird as I must open each section in the config, I don't have to do anything but as long as each section has been opened, exiting the config will allow the drive to be detected. If I miss a section, no detection. 4.2 Has no problems detecting the drive. The drive is a Toshiba SD2042, and is on a Dell Inspiron 8000 laptop. I partly believe it may be related to acpi as I get a few "too many dependant configs" showing at boot time. What can I enable to help diagnose this problem as I admit the details here are sketchy. (Will post a kernel -v soon). Cheers, Benjamin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 6 23:11:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 0131437B422 for ; Sun, 6 May 2001 23:11:45 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f476BGb05185; Mon, 7 May 2001 00:11:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200105070611.f476BGb05185@harmony.village.org> To: Kris Kennaway Subject: Re: ssh reports "no RSA support in libssl and libcrypto." Cc: Peter Jeremy , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 06 May 2001 22:53:06 PDT." <20010506225306.A46294@xor.obsecurity.org> References: <20010506225306.A46294@xor.obsecurity.org> <20010507091631.H59150@gsmx07.alcatel.com.au> Date: Mon, 07 May 2001 00:11:16 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010506225306.A46294@xor.obsecurity.org> Kris Kennaway writes: : Check the archives, this is a FAQ with probably the usual answer. Hint: the answer is in UPDATING. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 0:15:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id EA18F37B423 for ; Mon, 7 May 2001 00:15:21 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id RAA30501; Mon, 7 May 2001 17:15:04 +1000 Date: Mon, 7 May 2001 17:13:52 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Daniel Eischen Cc: Andrew Gallatin , current@FreeBSD.ORG Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 May 2001, Daniel Eischen wrote: > On Sat, 5 May 2001, Andrew Gallatin wrote: > > > > Daniel Eischen writes: > > > > > > OK, thanks. Here's my guess at what should be changed for the Linux > > > emulator. If this looks correct, I'll commit it. > > > > > > Hmm, I wonder how linuxthreads works under FreeBSD without this > > > change... > > > > This breaks at least one version of the IBM JDK that I have > > laying around.. > > > > If anything, we may have two errors (at least partially) canceling > > each other out. I think it needs more work/thought prior to > > committing. > > We're still OK with the change to FreeBSDs native signal trampoline > though, right? I'll hold off on the Linux emulator changes until > we can figure out what the problem is. I was confused about what Linux does. Now I think it only copies %fs to the signal context struct. It loads %fs with USER_DS for the signal handler. It passes the previous (process) value of %gs to the signal handler. (Its early mistake of of switching %fs on every entry to the kernel was moved to FreeBSD.) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 1:55:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 9F60C37B422 for ; Mon, 7 May 2001 01:55:13 -0700 (PDT) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id DA02A5D60; Mon, 7 May 2001 10:55:30 +0200 (CEST) Date: Mon, 7 May 2001 10:55:30 +0200 From: Jesper Skriver To: Warner Losh Cc: Kris Kennaway , Peter Jeremy , current@FreeBSD.ORG Subject: Re: ssh reports "no RSA support in libssl and libcrypto." Message-ID: <20010507105530.B33001@skriver.dk> References: <20010506225306.A46294@xor.obsecurity.org> <20010507091631.H59150@gsmx07.alcatel.com.au> <20010506225306.A46294@xor.obsecurity.org> <200105070611.f476BGb05185@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105070611.f476BGb05185@harmony.village.org>; from imp@harmony.village.org on Mon, May 07, 2001 at 12:11:16AM -0600 X-PGP-Fingerprint: 6B88 9CE8 66E9 E631 C9C5 5EB4 22AB F0EC F956 1C31 X-PGP-Public-Key: http://freesbee.wheel.dk/~jesper/gpgkey.pub Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 07, 2001 at 12:11:16AM -0600, Warner Losh wrote: > In message <20010506225306.A46294@xor.obsecurity.org> Kris Kennaway writes: > : Check the archives, this is a FAQ with probably the usual answer. > > Hint: the answer is in UPDATING. Perhaps we could add "Make sure you have loaded random.ko" to the output ? /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 4:52:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 0940637B422 for ; Mon, 7 May 2001 04:52:21 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id HAA28271; Mon, 7 May 2001 07:51:40 -0400 (EDT) Date: Mon, 7 May 2001 07:51:40 -0400 (EDT) From: Daniel Eischen To: Bruce Evans Cc: Andrew Gallatin , current@FreeBSD.ORG Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 May 2001, Bruce Evans wrote: > On Sat, 5 May 2001, Daniel Eischen wrote: > > > On Sat, 5 May 2001, Andrew Gallatin wrote: > > > > > > Daniel Eischen writes: > > > > > > > > OK, thanks. Here's my guess at what should be changed for the Linux > > > > emulator. If this looks correct, I'll commit it. > > > > > > > > Hmm, I wonder how linuxthreads works under FreeBSD without this > > > > change... > > > > > > This breaks at least one version of the IBM JDK that I have > > > laying around.. > > > > > > If anything, we may have two errors (at least partially) canceling > > > each other out. I think it needs more work/thought prior to > > > committing. > > > > We're still OK with the change to FreeBSDs native signal trampoline > > though, right? I'll hold off on the Linux emulator changes until > > we can figure out what the problem is. > > I was confused about what Linux does. Now I think it only copies %fs > to the signal context struct. It loads %fs with USER_DS for the signal > handler. It passes the previous (process) value of %gs to the signal > handler. (Its early mistake of of switching %fs on every entry to the > kernel was moved to FreeBSD.) I think the only reason we used %fs instead of %gs was WINE. I think Linux uses %gs for TSD, so if WINE were to ever depend on linuxthreads, one of them would have to change. We can easily switch to using %gs instead of %fs if necessary. I'll make the appropriate change to the Linux emulator. Thanks -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 5:37:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by hub.freebsd.org (Postfix) with SMTP id 1E60C37B422 for ; Mon, 7 May 2001 05:37:26 -0700 (PDT) (envelope-from ms@laptop.6bone.nl) Received: (qmail 28540 invoked by uid 0); 7 May 2001 12:37:22 -0000 Received: from kantoor.ripe.net (HELO laptop.6bone.nl) (193.0.1.98) by postman.ripe.net with SMTP; 7 May 2001 12:37:22 -0000 Received: (nullmailer pid 38828 invoked by uid 1000); Mon, 07 May 2001 12:37:20 -0000 Date: Mon, 7 May 2001 14:37:20 +0200 From: Mark Santcroos To: Tomi Vainio - Sun Finland - Cc: freebsd-current@FreeBSD.ORG Subject: Re: WinModem Support/Learning the kernel Internals Message-ID: <20010507143720.A38755@laptop.6bone.nl> References: <15085.61825.708944.271219@ultrahot.Finland.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15085.61825.708944.271219@ultrahot.Finland.Sun.COM>; from Tomi.Vainio@Sun.COM on Tue, May 01, 2001 at 02:13:05AM +0300 X-Handles: MS6-6BONE, MS32260-NIC, MS18417-RIPE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 01, 2001 at 02:13:05AM +0300, Tomi Vainio - Sun Finland - wrote: > Benjamin Close writes: > > Is anyone looking into converting the Linux winmodem driver ( > > Lucent Technologies binary object file compiled together with the linux > > kernel serial driver) into a freebsd device? > > > Please check http://www.geocities.com/wtnbkysh/ . It should work > under 4.2R. There is also some 5.0C patches but still some problems > probably with interrupts. Any idea who is the author of this? I also tried it on -current and it needs some refinement probably. I am willing to do that but it would be nice if the author could give me some hints. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 7:56:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id C78AB37B423 for ; Mon, 7 May 2001 07:56:40 -0700 (PDT) (envelope-from dennisg@software-munitions.com) Received: from localhost (dennisg@localhost) by btw.plaintalk.bellevue.wa.us (8.11.3/8.11.3) with ESMTP id f47EuCv25191; Mon, 7 May 2001 07:56:12 -0700 (PDT) (envelope-from dennisg@software-munitions.com) Date: Mon, 7 May 2001 07:56:12 -0700 (PDT) From: Dennis Glatting X-X-Sender: To: Kris Kennaway Cc: , Subject: Re: pgm to kill 4.3 via vm In-Reply-To: <20010506044724.A24309@xor.obsecurity.org> Message-ID: <20010507074503.Y24943-100000@btw.plaintalk.bellevue.wa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 6 May 2001, Kris Kennaway wrote: > On Sat, May 05, 2001 at 02:37:07PM -0700, Dennis Glatting wrote: > > > > I wrote a trivial program to fill vm and found I can reliably freeze my > > system. It may not work on the first attempt, but certainly within three. > > My command line is: > > > > a.out&;a.out&;a.out&;a.out&;a.out& > > > > The goal of my program is simply to see how the system behaves under > > memory exhaustion which, as it turns out on two similar systems, the > > systems freeze. Specifically, I can switch between consoles but the login > > prompts do not respond and the system does not respond on the network. > > > > I am running 4.3 on a dual processor system. > > > > Below are some things. First, the program. Second, dmesg. Finally, my > > /etc/rc.config. > > What resource limits have you set? > I haven't set any, so it's the default. I am intentionally testing at the limits to see what happens, usually interesting things. :) In this case, the application is well behaved (in the error proccesing sense): it'll exit, thus releasing its memory resources, when the kernel reports a memory allocation failure. (Within the last six months I commited less than 10 systems to production roles. Consequently, I'm interested in how FreeBSD behaves should any of the applications behave badly.) I've run this code on four systems, all 4.3. Two of the systems are similar SMP boxes; one a P3 233; and the last a P3 500 lap top. The code eventually crashed all systems (less than three runs) and sometimes printed an error message about a swap allocation failure. In the worst case I expect an error message, like "gone fishing, bye.", but that isn't the case; so my suspecion is a bug that those who know the kernel better than I might pursue. TIA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 8:10:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 03E1737B423 for ; Mon, 7 May 2001 08:10:48 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA51811; Mon, 7 May 2001 17:10:43 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Dennis Glatting Cc: Kris Kennaway , , Subject: Re: pgm to kill 4.3 via vm References: <20010507074503.Y24943-100000@btw.plaintalk.bellevue.wa.us> From: Dag-Erling Smorgrav Date: 07 May 2001 17:10:42 +0200 In-Reply-To: <20010507074503.Y24943-100000@btw.plaintalk.bellevue.wa.us> Message-ID: Lines: 25 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis Glatting writes: > I am intentionally testing at the limits to see what happens, usually > interesting things. :) In this case, the application is well behaved (in > the error proccesing sense): it'll exit, thus releasing its memory > resources, when the kernel reports a memory allocation failure. No. malloc() will return NULL only if you hit a resource limit or exhaust address space. There may or may not be memory (real or virtual) available at that time. Plus, your program doesn't even do what you think it does (because a) it has at least one significant bug and b) malloc() doesn't behave the way you think it does). And even if it did, the /dev/random stuff is pointless, you can achieve the same effect by setting every byte you allocate (possibly even just the first byte of every chunk) to 0. To really test what you think your program tests, you should mmap() an amount of memory larger than RAM + swap and touch every page. Even then, the result will be a SIGSEGV, not a graceful termination. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 8:43: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 3158637B423 for ; Mon, 7 May 2001 08:42:57 -0700 (PDT) (envelope-from dennis.glatting@software-munitions.com) Received: from kwijibo (kwijibi.pki2.com [206.129.5.152] (may be forged)) by btw.plaintalk.bellevue.wa.us (8.11.3/8.11.3) with SMTP id f47FfiE45909; Mon, 7 May 2001 08:41:44 -0700 (PDT) (envelope-from dennis.glatting@software-munitions.com) Content-Type: text/plain; charset="iso-8859-1" From: Dennis Glatting Organization: Software Munitions To: Dag-Erling Smorgrav Subject: Re: pgm to kill 4.3 via vm Date: Mon, 7 May 2001 08:41:44 -0700 X-Mailer: KMail [version 1.2] Cc: Kris Kennaway , , References: <20010507074503.Y24943-100000@btw.plaintalk.bellevue.wa.us> In-Reply-To: MIME-Version: 1.0 Message-Id: <01050708414400.13646@kwijibo> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday 07 May 2001 08:10 am, Dag-Erling Smorgrav wrote: > Dennis Glatting writes: > > I am intentionally testing at the limits to see what happens, > > usually interesting things. :) In this case, the application is > > well behaved (in the error proccesing sense): it'll exit, thus > > releasing its memory resources, when the kernel reports a memory > > allocation failure. > > No. > > malloc() will return NULL only if you hit a resource limit or exhaust > address space. There may or may not be memory (real or virtual) > available at that time. > Isn't memory exhaustion a resource limit? > Plus, your program doesn't even do what you think it does (because a) > it has at least one significant bug and b) malloc() doesn't behave > the way you think it does). And even if it did, the /dev/random > stuff is pointless, you can achieve the same effect by setting every > byte you allocate (possibly even just the first byte of every chunk) > to 0. > /dev/random is left over from a different test and isn't relevant. Explain the bug and malloc() behaviour. According to the malloc() man page: RETURN VALUES The malloc() and calloc() functions return a pointer to the allocated memory if successful; otherwise a NULL pointer is returned and errno is set to ENOMEM. I assert memory exhaustion is would return "unsuccessful" on the malloc() call, no? > To really test what you think your program tests, you should mmap() > an amount of memory larger than RAM + swap and touch every page. > Even then, the result will be a SIGSEGV, not a graceful termination. > > DES To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 8:59:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 0C1B737B424 for ; Mon, 7 May 2001 08:59:51 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA52041; Mon, 7 May 2001 17:59:43 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Dennis Glatting Cc: Kris Kennaway , , Subject: Re: pgm to kill 4.3 via vm References: <20010507074503.Y24943-100000@btw.plaintalk.bellevue.wa.us> <01050708414400.13646@kwijibo> From: Dag-Erling Smorgrav Date: 07 May 2001 17:59:43 +0200 In-Reply-To: <01050708414400.13646@kwijibo> Message-ID: Lines: 48 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis Glatting writes: > On Monday 07 May 2001 08:10 am, Dag-Erling Smorgrav wrote: > > malloc() will return NULL only if you hit a resource limit or exhaust > > address space. There may or may not be memory (real or virtual) > > available at that time. > Isn't memory exhaustion a resource limit? What is memory exhaustion? Namespace exhaustion will cause malloc() to fail. But FreeBSD overcommits memory, so exhaustion of physical and virtual memory will manifest itself as an unsatisfiable page fault, which will cause the kernel to start killing more-or-less-random processes until some memory is available again. > Explain the bug and malloc() behaviour. According to the malloc() man > page: The bug: I believe you meant "i -= j" when you wrote "i =- j". The result is that i becomes negative and in all likelihood you smash the malloc() arena. Regarding malloc(), you seem to believe that malloc() allocates *exactly* the amount you ask, no more, no less, and actually allocates physical or virtual memory. It doesn't. First of all, it allocates memory of its own for bookkeeping purposes, which your program doesn't account for. Second, it usually allocates a little bit more than you asked for, and keeps the leftovers for later. Third, it only allocates namespace. Actual memory (physical or virtual) is allocated by the kernel the first time you touch a page. What's more, your program does extra stuff (such as needlessly fork() / exec()ing sync(1) instead of just calling sync(2), which doesn't serve any purpose anyway, since virtual memory isn't managed by the file system code, so sync(2) doesn't affect it) which consumes memory, which further invalidates your results (for instance, memory exhaustion while running sync(1) could cause the kernel to randomly kill your program) > I assert memory exhaustion is would return "unsuccessful" on the > malloc() call, no? No, just namespace exhaustion, which your program won't even come close to. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 9:12:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from nala.dohd.org (a29150.upc-a.chello.nl [62.163.29.150]) by hub.freebsd.org (Postfix) with ESMTP id 89CFC37B423 for ; Mon, 7 May 2001 09:12:28 -0700 (PDT) (envelope-from freebsd@dohd.org) Received: by nala.dohd.org (Postfix, from userid 1008) id 58EBAD97A; Mon, 7 May 2001 18:12:27 +0200 (MET DST) Date: Mon, 7 May 2001 18:12:27 +0200 From: Mark Huizer To: freebsd-current@freebsd.org Subject: setcred and sshd trouble? Message-ID: <20010507181227.B17495@dohd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Can't seem to find the no doubtedly obvious answer to the problem with sshd after remaking world (today's -current with new openssh 2.9) Trying to log in remotely results in: May 7 17:37:45 tiggr /boot/kernel/kernel: May 7 17:37:45 tiggr sshd[718]: fatal: PAM setcred failed[6]: Permission denied which I can't seem to find a way to fix :-( Is this a side effect of pam_ssh leaving or what? Further more: /etc/rc* do not create ssh_host_rsa_key so far. Mark -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 9:18: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 57ACB37B423 for ; Mon, 7 May 2001 09:18:01 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id BAD3049; Mon, 7 May 2001 12:17:52 -0400 (AST) Message-ID: <3AF6CAB0.D7C8C5BE@vangelderen.org> Date: Mon, 07 May 2001 12:17:52 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: ssh reports "no RSA support in libssl and libcrypto." References: <20010507091631.H59150@gsmx07.alcatel.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > > Having built and installed -current from last Friday, I find that ssh* > is now reporting "no RSA support in libssl and libcrypto. See ssl(8)" > and will only talk SSH2. I couldn't find anything relevant in ssl(8). > > I haven't specified "WITH_RSA=NO" anywhere and checking through the > build logs, there's no sign of "-DNO_RSA". libcrypto.a contains an > RSA_generate_key() which doesn't look like a stub. > > Does anyone have any ideas? I seem to remember that I once got a misleading message just like that. It turned out that /dev/random was not available or not working properly. Cheers, Jeroen -- Jeroen C. van Gelderen - jeroen@vangelderen.org "A government that robs Peter to pay Paul can always depend upon the support of Paul." -- George Bernard Shaw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 9:42:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 4E81A37B422 for ; Mon, 7 May 2001 09:42:55 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.2/8.11.0) with ESMTP id f47Ggrj67877; Mon, 7 May 2001 10:42:53 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f47Ghfl59002; Mon, 7 May 2001 10:43:41 -0600 (MDT) Message-Id: <200105071643.f47Ghfl59002@billy-club.village.org> To: Jesper Skriver Subject: Re: ssh reports "no RSA support in libssl and libcrypto." Cc: Kris Kennaway , Peter Jeremy , current@FreeBSD.org In-reply-to: Your message of "Mon, 07 May 2001 10:55:30 +0200." <20010507105530.B33001@skriver.dk> References: <20010507105530.B33001@skriver.dk> <20010506225306.A46294@xor.obsecurity.org> <20010507091631.H59150@gsmx07.alcatel.com.au> <20010506225306.A46294@xor.obsecurity.org> <200105070611.f476BGb05185@harmony.village.org> Date: Mon, 07 May 2001 10:43:41 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010507105530.B33001@skriver.dk> Jesper Skriver writes: : On Mon, May 07, 2001 at 12:11:16AM -0600, Warner Losh wrote: : > In message <20010506225306.A46294@xor.obsecurity.org> Kris Kennaway writes: : > : Check the archives, this is a FAQ with probably the usual answer. : > : > Hint: the answer is in UPDATING. : : Perhaps we could add "Make sure you have loaded random.ko" to the output ? There's two problems that cause this. First is not having random in the kernel. Second is not having done MAKEDEV in /dev for the random device. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 9:47:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8EB1D37B422 for ; Mon, 7 May 2001 09:47:45 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f47Glh049361; Mon, 7 May 2001 09:47:43 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f47GlgQ64138; Mon, 7 May 2001 09:47:42 -0700 (PDT) (envelope-from jdp) Date: Mon, 7 May 2001 09:47:42 -0700 (PDT) Message-Id: <200105071647.f47GlgQ64138@vashon.polstra.com> To: current@freebsd.org From: John Polstra Cc: eischen@vigrid.com Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Daniel Eischen wrote: > I think the only reason we used %fs instead of %gs was WINE. I > think Linux uses %gs for TSD, so if WINE were to ever depend on > linuxthreads, one of them would have to change. At least on Red Hat 7.0 (glibc-2.1.92-14), Linux does not use a segment register to find TSD. It aligns all stacks at a multpile of 2MB and then does bit ops on the current stack pointer to find a thread control block at the base (highest address) of the stack. There is an alternate implementation in that version of glibc which uses %gs to find TSD. However, it is not used in this version of Linux. I don't know whether it's used in other versions or not. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 9:55:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id A7BB737B42C for ; Mon, 7 May 2001 09:55:56 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f47GtiK61081; Mon, 7 May 2001 09:55:44 -0700 (PDT) (envelope-from dillon) Date: Mon, 7 May 2001 09:55:44 -0700 (PDT) From: Matt Dillon Message-Id: <200105071655.f47GtiK61081@earth.backplane.com> To: Dennis Glatting Cc: Dag-Erling Smorgrav , Kris Kennaway , , Subject: Re: pgm to kill 4.3 via vm References: <20010507074503.Y24943-100000@btw.plaintalk.bellevue.wa.us> <01050708414400.13646@kwijibo> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : The malloc() and calloc() functions return a pointer to : the allocated memory if successful; otherwise a NULL : pointer is returned and errno is set to ENOMEM. : :I assert memory exhaustion is would return "unsuccessful" on the :malloc() call, no? malloc() returns NULL if the process datasize resource limit is exceeded, as set by the setrlimit() system call, 'limit' csh/tcsh command, or 'ulimit' sh/bash command. You are required to set this (and other) limits to reasonable values for your machine... the machine has no clue as to when you want things to start to fail because often systems become unusable long before they run out of swap. By default the machine tries to accomodate everything. malloc() does not return NULL if the machine itself runs out of VM. mmap() currently bypasses the datasize resource limit... it does not reserve VM space from same area as malloc(). We've known this for a while and know we need to add another setrlimit type to handle it. If you use mmap() to allocate huge amounts of anonymous memory and you don't have the swap to back it up, you can crash the machine. Theoretically the system is supposed to start killing large processes when memory + swap gets full, but that code does not appear to be working as well as it should at the moment. This argument rears its head about once a year and usually turns into a huge flame war. It's one of those things that you can make quite excellent theoretical arguments for, which look great on paper, but the reality is so incompatible with the theory (read: the theoretical solutions break more people then it fixes) that the smarter people huck the theory into the dumpster and stick with the reality. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 10: 1:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 283A537B422 for ; Mon, 7 May 2001 10:01:42 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14woNp-0006Gk-00; Mon, 07 May 2001 19:01:17 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id TAA29389; Mon, 7 May 2001 19:01:16 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 29280; Mon May 7 19:00:49 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14woNN-000Pku-00; Mon, 07 May 2001 19:00:49 +0200 To: Matt Dillon Cc: Dennis Glatting , Dag-Erling Smorgrav , Kris Kennaway , freebsd-stable@frebsd.org, freebsd-current@freebsd.org Subject: Re: pgm to kill 4.3 via vm In-reply-to: Your message of "Mon, 07 May 2001 09:55:44 MST." <200105071655.f47GtiK61081@earth.backplane.com> Date: Mon, 07 May 2001 19:00:49 +0200 Message-ID: <99007.989254849@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 07 May 2001 09:55:44 MST, Matt Dillon wrote: > Theoretically the system is supposed to start killing large processes > when memory + swap gets full, but that code does not appear to be working > as well as it should at the moment. I think that's all that Dennis was questioning. All he needed was your answer. :-) > This argument rears its head about once a year and usually turns into a > huge flame war. I think DES was responding to that flame war, rather than to Dennis' actual question. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 10: 2:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8707837B423 for ; Mon, 7 May 2001 10:02:37 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id TAA52373; Mon, 7 May 2001 19:02:32 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Matt Dillon Cc: Dennis Glatting , Kris Kennaway , , Subject: Re: pgm to kill 4.3 via vm References: <20010507074503.Y24943-100000@btw.plaintalk.bellevue.wa.us> <01050708414400.13646@kwijibo> <200105071655.f47GtiK61081@earth.backplane.com> From: Dag-Erling Smorgrav Date: 07 May 2001 19:02:32 +0200 In-Reply-To: <200105071655.f47GtiK61081@earth.backplane.com> Message-ID: Lines: 11 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon writes: > This argument rears its head about once a year and usually turns into a > huge flame war. Yes, I was going to mention that - search the archives for "memory overcommit" and you'll find most of what I've already said in this thread, and plenty I haven't. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 10: 9:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from sol.serv.u-szeged.hu (sol.serv.u-szeged.hu [160.114.51.3]) by hub.freebsd.org (Postfix) with ESMTP id 6F24637B422 for ; Mon, 7 May 2001 10:09:17 -0700 (PDT) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.serv.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id TAA02149; Mon, 7 May 2001 19:09:15 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 14woVV-00039d-00 for ; Mon, 07 May 2001 19:09:13 +0200 Date: Mon, 7 May 2001 19:09:13 +0200 From: Szilveszter Adam To: freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm Message-ID: <20010507190913.A8998@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , freebsd-current@FreeBSD.ORG References: <20010507074503.Y24943-100000@btw.plaintalk.bellevue.wa.us> <01050708414400.13646@kwijibo> <200105071655.f47GtiK61081@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Mon, May 07, 2001 at 07:02:32PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 07, 2001 at 07:02:32PM +0200, Dag-Erling Smorgrav wrote: > Matt Dillon writes: > > This argument rears its head about once a year and usually turns into a > > huge flame war. > > Yes, I was going to mention that - search the archives for "memory > overcommit" and you'll find most of what I've already said in this > thread, and plenty I haven't. A "Top UNIX Myths" page anyone? Along the lines of: "I have heard UNIX is the most secure OS! - No, unless you make it so and bring up the necessary expertise and time investment..." "I have heard you cannot crash a UNIX machine! - No, ..." It would serve those people well who were only "educated" about UNIX-type systems during MS vs anything else flamewars... -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 10:10:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id B630737B424 for ; Mon, 7 May 2001 10:10:17 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f47H9Pr61499; Mon, 7 May 2001 10:09:25 -0700 (PDT) (envelope-from dillon) Date: Mon, 7 May 2001 10:09:25 -0700 (PDT) From: Matt Dillon Message-Id: <200105071709.f47H9Pr61499@earth.backplane.com> To: Sheldon Hearn Cc: Kris Kennaway , Dennis Glatting , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm References: <81562.989176063@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :While that's a reasonable question when you're in a support role, I'd :certainly like to hear whether "FreeBSD freezes on memory exhaustion" is :something people "should just live with" or whether it's symptomatic of :a bug that someone might one day want to fix but which folks should, for :now, protect themselves against using resource limits. : :Ciao, :Sheldon. It's something I'd like to fix... but the proper solution is the simplest one, not something complex. The simplest one is to start killing bloated processes. We do this now, just not very well. The reality is that modern day disks have so much disk space compared to physical ram that the vast majority of sysads simply setup a reasonably-sized swap partition, reasonable resource limits, and wash their hands of the whole affair. A production machine with 128M of ram and 1G of swap is going to go down the tubes performance-wise long before it runs out of swap. Performance degredation under heavy memory loads is a much more interesting and important problem then swap exhaustion. Swap exhaustion is an interesting theoretical problem, and we certainly want to do something (i.e. kill processes). But that's it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 10:12:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 66CB037B422 for ; Mon, 7 May 2001 10:12:34 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id TAA52395; Mon, 7 May 2001 19:07:48 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Sheldon Hearn Cc: Matt Dillon , Dennis Glatting , Kris Kennaway , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm References: <99007.989254849@axl.fw.uunet.co.za> From: Dag-Erling Smorgrav Date: 07 May 2001 19:07:48 +0200 In-Reply-To: <99007.989254849@axl.fw.uunet.co.za> Message-ID: Lines: 15 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn writes: > I think DES was responding to that flame war, rather than to Dennis' > actual question. Actually, I was responding to Dennis' incorrect assumptions about FreeBSD's VM system, as exhibited by his code (which reflects the way he *thinks* the VM system works), and to the bugginess of his code. BTW, I was wrong - his code doesn't smash the malloc() arena, because the termination condition in the if loop guarantees it never makes more than one iteration. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 10:12:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 31DA837B424 for ; Mon, 7 May 2001 10:12:57 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA21637; Mon, 7 May 2001 13:12:05 -0400 (EDT) Date: Mon, 7 May 2001 13:12:05 -0400 (EDT) From: Daniel Eischen To: John Polstra Cc: current@freebsd.org Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: <200105071647.f47GlgQ64138@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 May 2001, John Polstra wrote: > In article > , Daniel > Eischen wrote: > > > I think the only reason we used %fs instead of %gs was WINE. I > > think Linux uses %gs for TSD, so if WINE were to ever depend on > > linuxthreads, one of them would have to change. > > At least on Red Hat 7.0 (glibc-2.1.92-14), Linux does not use a > segment register to find TSD. It aligns all stacks at a multpile > of 2MB and then does bit ops on the current stack pointer to find a > thread control block at the base (highest address) of the stack. > > There is an alternate implementation in that version of glibc which > uses %gs to find TSD. However, it is not used in this version of > Linux. I don't know whether it's used in other versions or not. I was looking at our linuxthreads port and noticed some %gs fiddling. If linuxthreads wants to allow POSIX semantics for specifying thread stack allocation, they'll have to stop relying on stack alignments for TSD. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 10:17:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 6916837B424 for ; Mon, 7 May 2001 10:17:36 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA06322; Mon, 7 May 2001 11:17:21 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id LAA04189; Mon, 7 May 2001 11:17:20 -0600 (MDT) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15094.55456.101355.48473@nomad.yogotech.com> Date: Mon, 7 May 2001 11:17:20 -0600 (MDT) To: Dag-Erling Smorgrav Cc: "Georg-W. Koltermann" , current@hub.freebsd.org, David Wolfskill Subject: Re: lockup after resume In-Reply-To: References: <20010328212426.A32322@hunter.munich.sgi.com> <20010504143910.B11325@hunter.munich.sgi.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One surprising observation: If I disable APM in /boot/device.hints, my > > machine suspends and resumes JUST FINE. The BIOS alone seems to be > > able to suspend and awake the hardware behind FreeBSD's back. The > > system only hangs if FreeBSD is involved in the process. > > Hmm, I might try that. > > BTW, last time I asked Warner about this his reply was (I paraphrase) > "it's not supposed to work, and if it ever worked for you it was out > of sheer luck", which I find surprising. Me too, since it used to work on that same hardware. (A ThinkPad 600 was what I did the original suspend/resume work on during the FreeBSD 2.2 days.) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 10:18:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 17E9537B422 for ; Mon, 7 May 2001 10:18:43 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f47HIcl09019; Mon, 7 May 2001 10:18:38 -0700 (PDT) (envelope-from obrien) Date: Mon, 7 May 2001 10:18:38 -0700 From: current@freebsd.org To: Cyrille Lefevre Cc: Jeroen Ruigrok/Asmodai , current@freebsd.org Subject: Re: cp -u patch Message-ID: <20010507101838.A8945@dragon.nuxi.com> Reply-To: freebsd@freebsd.org References: <20010426222132.B55566@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from clefevre-lists@noos.fr on Sun, May 06, 2001 at 06:11:56AM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, May 06, 2001 at 06:11:56AM +0200, Cyrille Lefevre wrote: > > Question is, do we want to add this to our cp? > please, what is the difference between this : > > cp -Ruv mozilla mozilla-test > and that : > cd mozzila; find . | cpio -pdm ../mozzila-test Lets try another realistic example: cp -uvp ab* cde*.f* g? h/*.i? j/kl /m What's the find | cpio invocation for that? When you come up with it, it will be very messy. BTW, I don't consider my example contrived, I've copied files like that before for backup purposes. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 10:59:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id 3D6B537B423 for ; Mon, 7 May 2001 10:59:07 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id BBF6216B36 for ; Mon, 7 May 2001 14:58:56 -0300 (EST) Received: (qmail 17764 invoked by uid 0); 7 May 2001 17:57:28 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 7 May 2001 17:57:28 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.3/8.11.3) with ESMTP id f47Hwsm24036; Mon, 7 May 2001 14:58:56 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Mon, 7 May 2001 14:58:53 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Matt Dillon Cc: Sheldon Hearn , Kris Kennaway , Dennis Glatting , , Subject: Re: pgm to kill 4.3 via vm In-Reply-To: <200105071709.f47H9Pr61499@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 May 2001, Matt Dillon wrote: > their hands of the whole affair. A production machine with 128M of ram > and 1G of swap is going to go down the tubes performance-wise long > before it runs out of swap. Performance degredation under heavy > memory loads is a much more interesting and important problem > then swap exhaustion. Indeed, this is an interesting area. In the process of researching how to best implement this for Linux I have found various reasons why both FreeBSD's and NetBSD's load control systems cannot work in various realistic scenarios. The next step is designing a load control system that does work (not too hard) and having a reliable way of detecting when exactly the system is thrashing (next to impossible?). I'll make a detailed writeup of exactly why FreeBSD's load control system cannot work and will post it to arch@freebsd.org and linux-mm@kvack.org soon... ;) regards, Rik -- Linux MM bugzilla: http://linux-mm.org/bugzilla.shtml Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 11: 7:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id A349037B423 for ; Mon, 7 May 2001 11:07:31 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f47I73l62730; Mon, 7 May 2001 11:07:03 -0700 (PDT) (envelope-from dillon) Date: Mon, 7 May 2001 11:07:03 -0700 (PDT) From: Matt Dillon Message-Id: <200105071807.f47I73l62730@earth.backplane.com> To: Rik van Riel Cc: Sheldon Hearn , Kris Kennaway , Dennis Glatting , , Subject: Re: pgm to kill 4.3 via vm References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Indeed, this is an interesting area. In the process of :researching how to best implement this for Linux I have :found various reasons why both FreeBSD's and NetBSD's :load control systems cannot work in various realistic :scenarios. It's not a load control system. It's an emergency measure, period. A load control system is something like... oh, the 20 second enforced swap out that can be triggered when the VM system is under extreme memory pressure. Load control is a completely different issue from swap exhaustion. The two are entirely unrelated to each other. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 11:10:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id 5C5AF37B422 for ; Mon, 7 May 2001 11:10:13 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id A72C916B40 for ; Mon, 7 May 2001 15:10:06 -0300 (EST) Received: (qmail 20384 invoked by uid 0); 7 May 2001 18:08:38 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 7 May 2001 18:08:38 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.3/8.11.3) with ESMTP id f47IA6P24538; Mon, 7 May 2001 15:10:06 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Mon, 7 May 2001 15:10:06 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Matt Dillon Cc: Sheldon Hearn , Kris Kennaway , Dennis Glatting , , Subject: Re: pgm to kill 4.3 via vm In-Reply-To: <200105071807.f47I73l62730@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 May 2001, Matt Dillon wrote: > :Indeed, this is an interesting area. In the process of > :researching how to best implement this for Linux I have > :found various reasons why both FreeBSD's and NetBSD's > :load control systems cannot work in various realistic > :scenarios. > > A > load control system is something like... oh, the 20 second enforced swap > out that can be triggered when the VM system is under extreme memory > pressure. Yup. Too bad the 20 second enforced swap out isn't enforced... (at least, not by the code in vm_glue.c) I'll write up an email about this later this week... > Load control is a completely different issue from swap > exhaustion. The two are entirely unrelated to each other. I know, that's why I only quoted the part of your message that was about load control and snipped the swap exhaustion part ;) regards, Rik -- Linux MM bugzilla: http://linux-mm.org/bugzilla.shtml Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 11:15:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 066CC37B422 for ; Mon, 7 May 2001 11:15:10 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f47IEpR62952; Mon, 7 May 2001 11:14:51 -0700 (PDT) (envelope-from dillon) Date: Mon, 7 May 2001 11:14:51 -0700 (PDT) From: Matt Dillon Message-Id: <200105071814.f47IEpR62952@earth.backplane.com> To: Rik van Riel Cc: Sheldon Hearn , Kris Kennaway , Dennis Glatting , , Subject: Re: pgm to kill 4.3 via vm References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> A :> load control system is something like... oh, the 20 second enforced swap :> out that can be triggered when the VM system is under extreme memory :> pressure. : :Yup. Too bad the 20 second enforced swap out isn't enforced... :(at least, not by the code in vm_glue.c) : :I'll write up an email about this later this week... Sure, that's an interesting topic. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 11:15:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6EEC037B422 for ; Mon, 7 May 2001 11:15:17 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f47IFB049972; Mon, 7 May 2001 11:15:11 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f47IFBs64511; Mon, 7 May 2001 11:15:11 -0700 (PDT) (envelope-from jdp) Date: Mon, 7 May 2001 11:15:11 -0700 (PDT) Message-Id: <200105071815.f47IFBs64511@vashon.polstra.com> To: current@freebsd.org From: John Polstra Cc: eischen@vigrid.com Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Daniel Eischen wrote: > > I was looking at our linuxthreads port and noticed some %gs > fiddling. If linuxthreads wants to allow POSIX semantics for > specifying thread stack allocation, they'll have to stop relying > on stack alignments for TSD. Agreed. It appears that they use %gs if it is determined (at glibc build time) that the target Linux kernel is new enough (2.3.99) to support it. The Red Hat 7.0 kernel is 2.2.16. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 11:25:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2576A37B424 for ; Mon, 7 May 2001 11:25:32 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f47IOwC27448; Mon, 7 May 2001 11:24:58 -0700 (PDT) Date: Mon, 7 May 2001 11:24:58 -0700 From: Alfred Perlstein To: Rik van Riel Cc: Matt Dillon , Sheldon Hearn , Kris Kennaway , Dennis Glatting , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm Message-ID: <20010507112458.U18676@fw.wintelcom.net> References: <200105071709.f47H9Pr61499@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from riel@conectiva.com.br on Mon, May 07, 2001 at 02:58:53PM -0300 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Rik van Riel [010507 10:59] wrote: > > Indeed, this is an interesting area. In the process of > researching how to best implement this for Linux I have > found various reasons why both FreeBSD's and NetBSD's > load control systems cannot work in various realistic > scenarios. > > The next step is designing a load control system that > does work (not too hard) and having a reliable way of > detecting when exactly the system is thrashing (next > to impossible?). > > I'll make a detailed writeup of exactly why FreeBSD's > load control system cannot work and will post it to > arch@freebsd.org and linux-mm@kvack.org soon... ;) You might as well not bother unless you're actually going to provide code that fixes the issue. For some reason banning you from the irc channel hasn't convinced you that complaining without providing patches isn't the way we do things around here. Anyhow, since you do seem to code a bit for Linux you might want to take a shot at fixing the Linux code. Last I checked, given enough time (30 minutes or so) FreeBSD recovers from such situations while Linux wets the bed and requires a power cycle. thank you and good bye, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 11:30: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id 7095937B422 for ; Mon, 7 May 2001 11:29:52 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id 1E1B516B31 for ; Mon, 7 May 2001 15:29:48 -0300 (EST) Received: (qmail 25004 invoked by uid 0); 7 May 2001 18:28:20 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 7 May 2001 18:28:20 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.3/8.11.3) with ESMTP id f47ITmp26834; Mon, 7 May 2001 15:29:48 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Mon, 7 May 2001 15:29:48 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Alfred Perlstein Cc: Matt Dillon , Sheldon Hearn , Kris Kennaway , Dennis Glatting , , Subject: Re: pgm to kill 4.3 via vm In-Reply-To: <20010507112458.U18676@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 May 2001, Alfred Perlstein wrote: > * Rik van Riel [010507 10:59] wrote: > > The next step is designing a load control system that > > does work (not too hard) and having a reliable way of > > detecting when exactly the system is thrashing (next > > to impossible?). > > You might as well not bother unless you're actually going to provide > code that fixes the issue. > > For some reason banning you from the irc channel hasn't convinced > you that complaining without providing patches isn't the way we do > things around here. How about first analysing the problem in detail and trying to fix it after we understand the problem ? The current stage is that I've pretty much figured out the problem and know why the code in FreeBSD and NetBSD doesn't currently work (while it would have worked in the original Mach VM). A next stage is getting some smart people together and coming up with a thorough solution. "Patch first, think later" is definately not the attitude I'm used to seeing in the FreeBSD world, no matter how often you and phk have shouted this at me yesterday ;) > Anyhow, since you do seem to code a bit for Linux you might want > to take a shot at fixing the Linux code. Last I checked, given > enough time (30 minutes or so) FreeBSD recovers from such situations > while Linux wets the bed and requires a power cycle. Indeed, at the moment Linux doesn't have any load control code at all while FreeBSD should be able to recover in some situations. Ideally both systems should be able to recover from just about any situation. regards, Rik -- Linux MM bugzilla: http://linux-mm.org/bugzilla.shtml Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 11:42:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 0D18437B42C for ; Mon, 7 May 2001 11:42:49 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f47IgPR27680; Mon, 7 May 2001 11:42:25 -0700 (PDT) Date: Mon, 7 May 2001 11:42:25 -0700 From: Alfred Perlstein To: Rik van Riel Cc: Matt Dillon , Sheldon Hearn , Kris Kennaway , Dennis Glatting , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm Message-ID: <20010507114225.V18676@fw.wintelcom.net> References: <20010507112458.U18676@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from riel@conectiva.com.br on Mon, May 07, 2001 at 03:29:48PM -0300 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Rik van Riel [010507 11:30] wrote: > > How about first analysing the problem in detail and > trying to fix it after we understand the problem ? > > The current stage is that I've pretty much figured out > the problem and know why the code in FreeBSD and NetBSD > doesn't currently work (while it would have worked in > the original Mach VM). > > A next stage is getting some smart people together > and coming up with a thorough solution. > > "Patch first, think later" is definately not the > attitude I'm used to seeing in the FreeBSD world, > no matter how often you and phk have shouted this at > me yesterday ;) No, you're mistaking the Linux methodology with FreeBSD's. Testing? What's that? If it compiles, it is good, if it boots up, it is perfect. -- Linus Torvalds In FreeBSD we submit a patch perhaps after having an N-way conversation (*) about the problem being addressed. The patch is then reviewed by several people who familiar with the subsystems in question. If you were to submit a patch in the next hour to address this it would be a matter of several days of load testing and review before it would be accepted. I'm are awaiting your patch, and I would be glad to assist you with it if you have any questions about the vm API. -- -Alfred Perlstein - [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 11:45:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 5AD2C37B424 for ; Mon, 7 May 2001 11:45:45 -0700 (PDT) (envelope-from dennisg@software-munitions.com) Received: from localhost (dennisg@localhost) by btw.plaintalk.bellevue.wa.us (8.11.3/8.11.3) with ESMTP id f47IimU48051; Mon, 7 May 2001 11:44:49 -0700 (PDT) (envelope-from dennisg@software-munitions.com) Date: Mon, 7 May 2001 11:44:48 -0700 (PDT) From: Dennis Glatting X-X-Sender: To: Dag-Erling Smorgrav Cc: Kris Kennaway , , Subject: Re: pgm to kill 4.3 via vm In-Reply-To: Message-ID: <20010507112937.V47835-100000@btw.plaintalk.bellevue.wa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 7 May 2001, Dag-Erling Smorgrav wrote: > Dennis Glatting writes: > > On Monday 07 May 2001 08:10 am, Dag-Erling Smorgrav wrote: > > > malloc() will return NULL only if you hit a resource limit or exhaust > > > address space. There may or may not be memory (real or virtual) > > > available at that time. > > Isn't memory exhaustion a resource limit? > > What is memory exhaustion? > Uh, when I perform a malloc() and get a NULL back? I dunno, what do you call that? > Namespace exhaustion will cause malloc() to fail. But FreeBSD > overcommits memory, so exhaustion of physical and virtual memory will > manifest itself as an unsatisfiable page fault, which will cause the > kernel to start killing more-or-less-random processes until some > memory is available again. > Why would it kill random processes as opposed to the offending process? > > Explain the bug and malloc() behaviour. According to the malloc() man > > page: > > The bug: I believe you meant "i -= j" when you wrote "i =- j". The > result is that i becomes negative and in all likelihood you smash the > malloc() arena. > Yup. > Regarding malloc(), you seem to believe that malloc() allocates > *exactly* the amount you ask, no more, no less, and actually allocates > physical or virtual memory. It doesn't. First of all, it allocates > memory of its own for bookkeeping purposes, which your program doesn't > account for. Second, it usually allocates a little bit more than you > asked for, and keeps the leftovers for later. Third, it only > allocates namespace. Actual memory (physical or virtual) is allocated > by the kernel the first time you touch a page. > I am not under the impression malloc allocs an exact space. > What's more, your program does extra stuff (such as needlessly fork() > / exec()ing sync(1) instead of just calling sync(2), which doesn't > serve any purpose anyway, since virtual memory isn't managed by the > file system code, so sync(2) doesn't affect it) which consumes memory, > which further invalidates your results (for instance, memory > exhaustion while running sync(1) could cause the kernel to randomly > kill your program) > Regardless, the code shouldn't be crashing the kernel. > > I assert memory exhaustion is would return "unsuccessful" on the > > malloc() call, no? > > No, just namespace exhaustion, which your program won't even come > close to. > I don't really understand your point. Who really cares whether it is a name space exhaustion or an exhaustion of virual memory or a fly sat on the keyboard: malloc() was called and the kernel crashed. The kernel should have failed the offending system call or killed the offending application. In the real world there are plenty of reasons why an operating system may run at or near its limits (whatever a limit may be). Example anomolies include: * a web server hit by a DoS, * a database server hit with a flurry of processing tasks * someone sending spam through your mail server Is it reasonable to kill the operating system when these things happen? No. The kernel should always be better behaved than the application. > DES > -- > Dag-Erling Smorgrav - des@ofug.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 11:50:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 3AFE437B42C for ; Mon, 7 May 2001 11:50:18 -0700 (PDT) (envelope-from dennisg@software-munitions.com) Received: from localhost (dennisg@localhost) by btw.plaintalk.bellevue.wa.us (8.11.3/8.11.3) with ESMTP id f47ImdM48105; Mon, 7 May 2001 11:48:39 -0700 (PDT) (envelope-from dennisg@software-munitions.com) Date: Mon, 7 May 2001 11:48:38 -0700 (PDT) From: Dennis Glatting X-X-Sender: To: Sheldon Hearn Cc: Matt Dillon , Dag-Erling Smorgrav , Kris Kennaway , , Subject: Re: pgm to kill 4.3 via vm In-Reply-To: <99007.989254849@axl.fw.uunet.co.za> Message-ID: <20010507114817.N47835-100000@btw.plaintalk.bellevue.wa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, enough said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 12: 3:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id DC99A37B422 for ; Mon, 7 May 2001 12:03:31 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id 2A22816B15 for ; Mon, 7 May 2001 16:03:29 -0300 (EST) Received: (qmail 897 invoked by uid 0); 7 May 2001 19:02:00 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 7 May 2001 19:02:00 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.3/8.11.3) with ESMTP id f47J3L327850; Mon, 7 May 2001 16:03:22 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Mon, 7 May 2001 16:03:21 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Alfred Perlstein Cc: Matt Dillon , Sheldon Hearn , Kris Kennaway , Dennis Glatting , Subject: Re: pgm to kill 4.3 via vm In-Reply-To: <20010507114225.V18676@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 May 2001, Alfred Perlstein wrote: > In FreeBSD we submit a patch perhaps after having an N-way > conversation (*) about the problem being addressed. > I'm are awaiting your patch, I'll let this contradiction speak for itself. You'll see a detailed analysis soon, patches will come only after we've agreed on a way to fix the problem. regards, Rik -- Linux MM bugzilla: http://linux-mm.org/bugzilla.shtml Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 12: 6:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from munin.odin-corporation.com (munin.odin-corporation.com [216.233.173.18]) by hub.freebsd.org (Postfix) with ESMTP id A51F437B424 for ; Mon, 7 May 2001 12:06:33 -0700 (PDT) (envelope-from lars@odin-corporation.com) Received: from odin-corporation.com (localhost [127.0.0.1]) by munin.odin-corporation.com (8.11.3/8.11.1) with ESMTP id f47J6MS02524 for ; Mon, 7 May 2001 14:06:22 -0500 (CDT) (envelope-from lars@odin-corporation.com) Message-ID: <3AF6F22E.2EFD35EA@odin-corporation.com> Date: Mon, 07 May 2001 14:06:22 -0500 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: current@freebsd.org Subject: gdb -k not able to access BSS? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was trying to debug a problem where sound card is not working because it ends up with a irq that is shared with the VGA card. So I figured I'd use gdb to look at the interrupt handler vector to see what was there and to find out what is going on. However gdb is unable to dump the data : munin# gdb -k -wcore -s ./kernel.debug GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (kgdb) print intr_handler Cannot access memory at address 0xc0395b80. (kgdb) x/20x 0xc0395b80 0xc0395b80 : Cannot access memory at address 0xc0395b80. Anyone got an idea? Nm on the running kernel agrees with the above address. munin# nm /boot/kernel/kernel | fgrep intr_handler c0395b80 B intr_handler Lars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 12:11:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 0F7B837B422 for ; Mon, 7 May 2001 12:11:28 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f47JBCD64553; Mon, 7 May 2001 12:11:12 -0700 (PDT) (envelope-from dillon) Date: Mon, 7 May 2001 12:11:12 -0700 (PDT) From: Matt Dillon Message-Id: <200105071911.f47JBCD64553@earth.backplane.com> To: Rik van Riel Cc: Alfred Perlstein , Sheldon Hearn , Kris Kennaway , Dennis Glatting , , Subject: Re: pgm to kill 4.3 via vm References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> For some reason banning you from the irc channel hasn't convinced :> you that complaining without providing patches isn't the way we do :> things around here. : :How about first analysing the problem in detail and :trying to fix it after we understand the problem ? : :The current stage is that I've pretty much figured out :the problem and know why the code in FreeBSD and NetBSD :doesn't currently work (while it would have worked in :the original Mach VM). : :A next stage is getting some smart people together :and coming up with a thorough solution. : :"Patch first, think later" is definately not the :attitude I'm used to seeing in the FreeBSD world, :no matter how often you and phk have shouted this at :me yesterday ;) Well, we'll see what you have to say in your paper. VM/Swap is a tough nut to crack... remember when I thought I had optimized the pageout daemon to not launder dirty pages unnecessarily? And then it turned out that, in fact, the pageouts were necessary to maintain stability in certain environments (like USENET news servers). That was somewhat embarassing because I waxed poetic to you and Linus and then had to correct myself and revert part of the optimization after real-life problems started cropping up. About 8 months ago I introduce code that would prevent sequential reads of large files from blowing away the rest of the system's VM page cache, to reduce the impact sequential reads would have in a heavily loaded system. It's a wonderful idea and I had thought up a great algorithm... too bad it didn't work in real life. It took a month to find all the edge cases and change the algorithm to be more of a heuristic to handle them all. I'm still not completely happy with it so at the moment it's only used by madvise(). At some point soon I am going to make the buffer cache use it, though. In anycase... insofar as VM goes, A theory doesn't usually last beyond the first implementation. So "we'll see". -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 12:13: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 5D1CA37B422 for ; Mon, 7 May 2001 12:13:00 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f47JB7374695; Mon, 7 May 2001 12:11:07 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: riel@conectiva.com.br Cc: bright@wintelcom.net, dillon@earth.backplane.com, sheldonh@uunet.co.za, kris@obsecurity.org, dennis.glatting@software-munitions.com, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm In-Reply-To: References: <20010507114225.V18676@fw.wintelcom.net> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010507121107E.jkh@osd.bsdi.com> Date: Mon, 07 May 2001 12:11:07 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 26 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You'll see a detailed analysis soon, patches will come only > after we've agreed on a way to fix the problem. You've already had some folks respond to this, though I think the argument has been mischaracterized as a "BSD vs Linux" thing. It's not. What people are (IMHO) really trying to argue here is the pragmatic approach. You can't really "agree on a way to fix the problem" when your operating criteria are as vague as "the existing system doesn't work, we need to fix it." That's like saying that putting someone into orbit is a simple matter of determining what escape velocity is necessary from an object with earth's mass and deciding how many tons of payload you want to insert at what altitude. The devil is, as they say, all in the details and all people here want is the necessary level of detail. Software is also largely an operational art where it's easier to describe something through a body of code with accompanying comments than it is to try and describe it on a purely theoretical basis. You don't need to necessarily adopt that code, it simply provides you with a more solid framework in which to discuss "ways to fix the problem" and that is what I believe Alfred and others are basically asking for. It's a reasonable request. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 12:41:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 311B237B422 for ; Mon, 7 May 2001 12:41:54 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f47JffG87372; Mon, 7 May 2001 12:41:41 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010506082927.P18676@fw.wintelcom.net> Date: Mon, 07 May 2001 12:37:24 -0700 (PDT) From: John Baldwin To: Alfred Perlstein Subject: Re: select(2) converted to use a condition variable, and optimis Cc: current@FreeBSD.org, Seigo Tanimura Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-May-01 Alfred Perlstein wrote: > * Seigo Tanimura [010506 04:40] wrote: >> >> http://people.FreeBSD.org/~tanimura/patches/selectopt.diff > > Please do not remove the spl calls, they serve as a useful guide > for making finer grained locks as well as error checking the new > locks. Actually, in this case, the proc lock provides all the locking needed, so the spl's can go I think. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 12:42: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 8E08737B423 for ; Mon, 7 May 2001 12:41:55 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f47JfdG87368; Mon, 7 May 2001 12:41:39 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105060731.f467V4g13184@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Date: Mon, 07 May 2001 12:37:22 -0700 (PDT) From: John Baldwin To: Seigo Tanimura Subject: RE: select(2) converted to use a condition variable, and optimis Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-May-01 Seigo Tanimura wrote: > As conversion of select(2) from msleep(9) to a condition variable is > in the SMPng TODO list, I have done that task. > > Also, we do not have to lock a process in order to evaluate the result > of {sel,poll}scan() and the remaining time of {select,poll}(2). It > should be enough to do those pieces of work first, followed by locking > a process and wait for a condition variable or selwakeup(). You need the lock when clearing the bit in p_flag. That is why the proc locks are there, so all those proc locks need to stay. When you clear a bit, you are writing all the bits, so you need to ensure that you can atomically read/modify/write all the bits in p_flag, hence the need for the proc lock. Please back out the changes to not lock the process around the p_flag change. The rest of the patch looks ok, though I'd like to review the updated version before it is committed. Thanks. > Those changes are in the patch at: > > http://people.FreeBSD.org/~tanimura/patches/selectopt.diff -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 12:45:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (f196.law7.hotmail.com [216.33.237.196]) by hub.freebsd.org (Postfix) with ESMTP id 37A3037B422 for ; Mon, 7 May 2001 12:45:34 -0700 (PDT) (envelope-from ajc13@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 7 May 2001 12:45:33 -0700 Received: from 198.242.51.122 by lw7fd.law7.hotmail.msn.com with HTTP; Mon, 07 May 2001 19:45:33 GMT X-Originating-IP: [198.242.51.122] From: "Andrew Card" To: current@freebsd.org Subject: subscribe Date: Mon, 07 May 2001 13:45:33 -0600 Mime-Version: 1.0 Content-Type: text/html Message-ID: X-OriginalArrivalTime: 07 May 2001 19:45:33.0992 (UTC) FILETIME=[47D40A80:01C0D72E] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG

Get your FREE download of MSN Explorer at http://explorer.msn.com

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 13:37:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A3C0B37B422 for ; Mon, 7 May 2001 13:37:49 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id WAA53375; Mon, 7 May 2001 22:37:44 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Dennis Glatting Cc: Kris Kennaway , , Subject: Re: pgm to kill 4.3 via vm References: <20010507112937.V47835-100000@btw.plaintalk.bellevue.wa.us> From: Dag-Erling Smorgrav Date: 07 May 2001 22:37:44 +0200 In-Reply-To: <20010507112937.V47835-100000@btw.plaintalk.bellevue.wa.us> Message-ID: Lines: 74 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis Glatting writes: > On 7 May 2001, Dag-Erling Smorgrav wrote: > > > Dennis Glatting writes: > > > On Monday 07 May 2001 08:10 am, Dag-Erling Smorgrav wrote: > > > > malloc() will return NULL only if you hit a resource limit or exhaust > > > > address space. There may or may not be memory (real or virtual) > > > > available at that time. > > > Isn't memory exhaustion a resource limit? > > > > What is memory exhaustion? > > > > Uh, when I perform a malloc() and get a NULL back? I dunno, what do you > call that? Address space exhaustion (which I incorrectly called "namespace exhaustion" in a previous mail - braino!), or a bug in malloc(). Consider the following program: #include #include int main(void) { int i; _malloc_options = "j"; for (i = 0; i < 4096; ++i) if (malloc(1048576) == NULL) err(1, "malloc() (i == %d)", i); exit(0); } The result may surprise you. > Why would it kill random processes as opposed to the offending process? Theoretically, it should kill the largest process around. I'm not sure it works like that in practice. > Regardless, the code shouldn't be crashing the kernel. Are you sure it does? Did you try running it on the console of a DDB-equipped system, press Ctrl-Alt-Esc, and find out what the kernel is doing when it appears frozen? > I don't really understand your point. Who really cares whether it is a > name space exhaustion or an exhaustion of virual memory or a fly sat on > the keyboard: malloc() was called and the kernel crashed. The kernel > should have failed the offending system call or killed the offending > application. Malloc() doesn't translate into a system call. It sometimes performs one or more system calls (mostly one of brk(), sbrk() and mmap()), and sometimes doesn't, depending largely on what kind of malloc() / free() activity there's been so far. Even when malloc() really does request memory from the kernel, what it really allocates is address space. The actual memory pages to fill that address space are allocated by the kernel as they are touched. > Is it reasonable to kill the operating system when these things happen? > No. The kernel should always be better behaved than the application. I didn't claim the contrary. I'm trying to show you that things don't work the way you think they do. Now be a good boy and go read the archives, it's all been discussed before. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 14:19:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from newsguy.com (perry.pathlink.com [209.155.233.33]) by hub.freebsd.org (Postfix) with ESMTP id DF3C137B443 for ; Mon, 7 May 2001 14:19:32 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (ppp070-bsace7001.telebrasilia.net.br [200.181.80.70]) by newsguy.com (8.11.0/8.9.1) with ESMTP id f47LIUD76030; Mon, 7 May 2001 14:18:30 -0700 (PDT) Message-ID: <3AF71124.607292BB@newsguy.com> Date: Mon, 07 May 2001 18:18:28 -0300 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en,pt-BR,pt,en-GB,en-US,ja MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: Dennis Glatting , Kris Kennaway , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm References: <20010507074503.Y24943-100000@btw.plaintalk.bellevue.wa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Dennis Glatting writes: > > I am intentionally testing at the limits to see what happens, usually > > interesting things. :) In this case, the application is well behaved (in > > the error proccesing sense): it'll exit, thus releasing its memory > > resources, when the kernel reports a memory allocation failure. > > No. > > malloc() will return NULL only if you hit a resource limit or exhaust > address space. There may or may not be memory (real or virtual) > available at that time. > > Plus, your program doesn't even do what you think it does (because a) > it has at least one significant bug and b) malloc() doesn't behave the > way you think it does). And even if it did, the /dev/random stuff is > pointless, you can achieve the same effect by setting every byte you > allocate (possibly even just the first byte of every chunk) to 0. > > To really test what you think your program tests, you should mmap() an > amount of memory larger than RAM + swap and touch every page. Even > then, the result will be a SIGSEGV, not a graceful termination. Regardless, the machine should recover once all (trouble) programs have been killed. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net Caffeine is proof that God hates mornings too To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 7 19:31:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 4DD8137B423 for ; Mon, 7 May 2001 19:31:28 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f482VI052621; Mon, 7 May 2001 19:31:18 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f482VIX65895; Mon, 7 May 2001 19:31:18 -0700 (PDT) (envelope-from jdp) Date: Mon, 7 May 2001 19:31:18 -0700 (PDT) Message-Id: <200105080231.f482VIX65895@vashon.polstra.com> To: current@freebsd.org From: John Polstra Cc: knu@iDaemons.org Subject: Re: OpenSSH 2.9 problems In-Reply-To: <86g0ekxevw.wl@archon.local.idaemons.org> References: <86g0ekxevw.wl@archon.local.idaemons.org> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <86g0ekxevw.wl@archon.local.idaemons.org>, Akinori MUSHA wrote: > I have some problems with the newly updated OpenSSH 2.9. > > 1. Sshd fails to authenticate via PAM. > > May 5 19:18:07 archon sshd[803]: fatal: PAM setcred failed[6]: Permission denied If you would just like to get it to work until the person who broke it fixes it properly, the patch below will accomplish that. This is _not_ a correct fix, and it should definitely not be committed. John Index: auth-pam.c =================================================================== RCS file: /home/ncvs/src/crypto/openssh/auth-pam.c,v retrieving revision 1.3 diff -u -r1.3 auth-pam.c --- auth-pam.c 2001/05/05 01:12:45 1.3 +++ auth-pam.c 2001/05/08 02:24:45 @@ -151,11 +151,13 @@ pam_retval, PAM_STRERROR(pamh, pam_retval)); } +#if 0 /* XXX */ pam_retval = pam_setcred(pamh, PAM_DELETE_CRED); if (pam_retval != PAM_SUCCESS) { debug("Cannot delete credentials[%d]: %.200s", pam_retval, PAM_STRERROR(pamh, pam_retval)); } +#endif pam_retval = pam_end(pamh, pam_retval); if (pam_retval != PAM_SUCCESS) { @@ -261,6 +263,7 @@ /* Set PAM credentials */ void do_pam_setcred(void) { +#if 0 /* XXX */ int pam_retval; debug("PAM establishing creds"); @@ -269,6 +272,7 @@ fatal("PAM setcred failed[%d]: %.200s", pam_retval, PAM_STRERROR(pamh, pam_retval)); } +#endif } /* accessor function for file scope static variable */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 1:36:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhotel.chrillesen.dk (vax.chrillesen.dk [193.88.12.35]) by hub.freebsd.org (Postfix) with ESMTP id B6C1B37B422 for ; Tue, 8 May 2001 01:36:56 -0700 (PDT) (envelope-from jach@mailhotel.chrillesen.dk) Received: by mailhotel.chrillesen.dk (Postfix, from userid 1000) id EF0255D96; Tue, 8 May 2001 10:36:47 +0200 (CEST) Date: Tue, 8 May 2001 10:36:47 +0200 From: Jan Chrillesen To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Thinkpad locks up with current Message-ID: <20010508103647.R18438@vax.chrillesen.dk> References: <20010506211522.Z18438@vax.chrillesen.dk> <200105070552.f475q2b05020@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105070552.f475q2b05020@harmony.village.org>; from imp@harmony.village.org on Sun, May 06, 2001 at 11:52:02PM -0600 X-editor: vim, http://www.vim.org/ Organization: Men in black T-shirts that dont shave Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 06 May 2001, Warner Losh wrote: > OLDCARD or NEWCARD? If oldcard, are you using the identical > configuration as you are on 4.2? The same irq for the pcic device, > the same irq list in /etc/pccard.conf, the same memory ranges in > /etc/pccard.conf, etc. I build it from GENERIC, rather than *CARD. Actually it did turn out to be b0rken hardware, so sorry for the post. But I guess getting a brand new T21 to replace the 600E is worth spending a weekend of buildworlds on :) /Jan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 1:40: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id BC72E37B423 for ; Tue, 8 May 2001 01:40:00 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f488dwb79272; Tue, 8 May 2001 02:39:58 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200105080839.f488dwb79272@harmony.village.org> To: Jan Chrillesen Subject: Re: Thinkpad locks up with current Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 08 May 2001 10:36:47 +0200." <20010508103647.R18438@vax.chrillesen.dk> References: <20010508103647.R18438@vax.chrillesen.dk> <20010506211522.Z18438@vax.chrillesen.dk> <200105070552.f475q2b05020@harmony.village.org> Date: Tue, 08 May 2001 02:39:58 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010508103647.R18438@vax.chrillesen.dk> Jan Chrillesen writes: : > OLDCARD or NEWCARD? If oldcard, are you using the identical : > configuration as you are on 4.2? The same irq for the pcic device, : > the same irq list in /etc/pccard.conf, the same memory ranges in : > /etc/pccard.conf, etc. : : I build it from GENERIC, rather than *CARD. Actually it did turn out to : be b0rken hardware, so sorry for the post. But I guess getting a brand : new T21 to replace the 600E is worth spending a weekend of buildworlds : on :) Ah, thanks. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 5:10:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id AEC1037B422; Tue, 8 May 2001 05:10:34 -0700 (PDT) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W-rina.r-20010412) with ESMTP id f48AQgP75260 ; Tue, 8 May 2001 19:26:43 +0900 (JST) Message-Id: <200105081026.f48AQgP75260@rina.r.dl.itc.u-tokyo.ac.jp> Date: Tue, 08 May 2001 19:26:42 +0900 From: Seigo Tanimura To: jhb@FreeBSD.org Cc: tanimura@r.dl.itc.u-tokyo.ac.jp, current@FreeBSD.org Subject: RE: select(2) converted to use a condition variable, and optimis In-Reply-To: In your message of "Mon, 07 May 2001 12:37:22 -0700 (PDT)" References: <200105060731.f467V4g13184@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 07 May 2001 12:37:22 -0700 (PDT), John Baldwin said: John> You need the lock when clearing the bit in p_flag. That is why the proc locks John> are there, so all those proc locks need to stay. When you clear a bit, you are John> writing all the bits, so you need to ensure that you can atomically John> read/modify/write all the bits in p_flag, hence the need for the proc lock. John> Please back out the changes to not lock the process around the p_flag change. John> The rest of the patch looks ok, though I'd like to review the updated version John> before it is committed. Thanks. Process locks are now back. Here is another issue. PROC_LOCK may block to acquire a process lock, during which an event of interest may occur or the remaining time of select(2)/poll(2) may run out. Thus if the remaining time runs out during locking a process, we should first rescan file descriptors to avoid missing an event, followed by returning the result. Those changes are now in the updated patch at: >> http://people.FreeBSD.org/~tanimura/patches/selectopt.diff -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 6:34: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.6.200.230]) by hub.freebsd.org (Postfix) with ESMTP id 74FBA37B422 for ; Tue, 8 May 2001 06:34:02 -0700 (PDT) (envelope-from mdharnois@home.com) Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id 284C414A31; Tue, 8 May 2001 08:34:25 -0500 (CDT) To: freebsd-current@freebsd.org Subject: world broken, pstat wants IN_SHLOCK, IN_EXLOCK Keywords: usr,pstat,src,sbin,function,undeclared From: Michael Harnois Date: 08 May 2001 08:34:24 -0500 Message-ID: <86itjc7yn3.fsf@mharnois.workgroup.net> Lines: 14 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.5 (alfalfa) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O2 -fno-strength-reduce -pipe -march=pentiumpro -I/usr/src/usr.sbin/pstat/../../sys -c /usr/src/usr.sbin/pstat/pstat.c /usr/src/usr.sbin/pstat/pstat.c: In function `ufs_print': /usr/src/usr.sbin/pstat/pstat.c:494: `IN_SHLOCK' undeclared (first use in this function) /usr/src/usr.sbin/pstat/pstat.c:494: (Each undeclared identifier is reported only once /usr/src/usr.sbin/pstat/pstat.c:494: for each function it appears in.) /usr/src/usr.sbin/pstat/pstat.c:496: `IN_EXLOCK' undeclared (first use in this function) *** Error code 1 -- Michael D. Harnois mdharnois@home.com Redeemer Lutheran Church Washburn, Iowa Physics is like sex: sure, it may give some practical results, but that's not why we do it. -- Richard Feynman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 7:21:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.6.200.230]) by hub.freebsd.org (Postfix) with ESMTP id 863BD37B42C for ; Tue, 8 May 2001 07:21:15 -0700 (PDT) (envelope-from mdharnois@home.com) Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id CF2AB14A30; Tue, 8 May 2001 09:21:50 -0500 (CDT) To: freebsd-current@freebsd.org Subject: world broken in sshd Keywords: usr,src,sshd,secure,sbin,openssh,crypto,auth1 From: Michael Harnois Date: 08 May 2001 09:21:50 -0500 Message-ID: <86pudjdipt.fsf@mharnois.workgroup.net> Lines: 12 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.5 (alfalfa) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O2 -fno-strength-reduce -pipe -march=pentiumpro -DLIBWRAP -DHAVE_LOGIN_CAP -DLOGIN_ACCESS -I/usr/src/secure/usr.sbin/sshd/../../../usr.bin/login -DUSE_PAM -DHAVE_PAM_GETENVLIST -DKRB4 -DSKEY -DXAUTH_PATH=\"/usr/X11R6/bin/xauth\" -I/usr/obj/usr/src/i386/usr/include -c /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/auth1.c /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/auth1.c: In function `do_authloop': /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/auth1.c:121: structure has no member named `kerberos_or_local_passwd' *** Error code 1 Stop in /usr/src/secure/usr.sbin/sshd. -- Michael D. Harnois mdharnois@home.com Redeemer Lutheran Church Washburn, Iowa Physics is like sex: sure, it may give some practical results, but that's not why we do it. -- Richard Feynman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 8:26:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id E34FE37B423 for ; Tue, 8 May 2001 08:26:31 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f48FQFG14825; Tue, 8 May 2001 08:26:15 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105081026.f48AQgP75260@rina.r.dl.itc.u-tokyo.ac.jp> Date: Tue, 08 May 2001 08:21:55 -0700 (PDT) From: John Baldwin To: Seigo Tanimura Subject: RE: select(2) converted to use a condition variable, and optimis Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-May-01 Seigo Tanimura wrote: > On Mon, 07 May 2001 12:37:22 -0700 (PDT), > John Baldwin said: > > John> You need the lock when clearing the bit in p_flag. That is why the > proc locks > John> are there, so all those proc locks need to stay. When you clear a bit, > you are > John> writing all the bits, so you need to ensure that you can atomically > John> read/modify/write all the bits in p_flag, hence the need for the proc > lock. > > John> Please back out the changes to not lock the process around the p_flag > change. > John> The rest of the patch looks ok, though I'd like to review the updated > version > John> before it is committed. Thanks. > > Process locks are now back. > > Here is another issue. PROC_LOCK may block to acquire a process lock, > during which an event of interest may occur or the remaining time of > select(2)/poll(2) may run out. Thus if the remaining time runs out > during locking a process, we should first rescan file descriptors to > avoid missing an event, followed by returning the result. > > Those changes are now in the updated patch at: > >>> http://people.FreeBSD.org/~tanimura/patches/selectopt.diff Hmmm. Actually, can the nb_poll, ncp_poll, pollscan, or selscan functions call tsleep/msleep? If they don't, then we are just better off holding proc lock while we call them rather than releasing it just to call that function and acquiring it later. Then we don't have to work around the race you describe. Also, in the done_noproclock: case (might want to use 'unlock:' and 'done:' instead of 'done:' and 'done_noproclock:' for label names instead) are you always sure that when you go to that label you don't need to clear P_SELECT? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 9:13:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 8875C37B422 for ; Tue, 8 May 2001 09:13:41 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0302.cvx21-bradley.dialup.earthlink.net [209.179.193.47]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id MAA18898; Tue, 8 May 2001 12:12:49 -0400 (EDT) Message-ID: <3AF81B16.7EC1F3DE@mindspring.com> Date: Tue, 08 May 2001 09:13:10 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: Dennis Glatting , Kris Kennaway , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm References: <20010507074503.Y24943-100000@btw.plaintalk.bellevue.wa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > Plus, your program doesn't even do what you think it does (because a) > it has at least one significant bug and b) malloc() doesn't behave the > way you think it does). And even if it did, the /dev/random stuff is > pointless, you can achieve the same effect by setting every byte you > allocate (possibly even just the first byte of every chunk) to 0. So now the question becomes "what is he testing that is resulting in 4.3 locking up?". Your suggested replacement test might be fun to run, but I think it wouldn't lock up 4.3... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 9:27:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id DC99437B423 for ; Tue, 8 May 2001 09:27:36 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0302.cvx21-bradley.dialup.earthlink.net [209.179.193.47]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id MAA26902; Tue, 8 May 2001 12:26:39 -0400 (EDT) Message-ID: <3AF81E54.E03D7DBD@mindspring.com> Date: Tue, 08 May 2001 09:27:00 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jordan Hubbard Cc: riel@conectiva.com.br, bright@wintelcom.net, dillon@earth.backplane.com, sheldonh@uunet.co.za, kris@obsecurity.org, dennis.glatting@software-munitions.com, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm References: <20010507114225.V18676@fw.wintelcom.net> <20010507121107E.jkh@osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > That's like saying that putting someone > into orbit is a simple matter of determining what escape velocity is > necessary from an object with earth's mass and deciding how many tons > of payload you want to insert at what altitude. The devil is, as they > say, all in the details and all people here want is the necessary > level of detail. Oh, come _on_, Jordan! Lobbing payloads into orbit isn't rocket science... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 9:42:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from hall.mail.mindspring.net (hall.mail.mindspring.net [207.69.200.60]) by hub.freebsd.org (Postfix) with ESMTP id 5290A37B423 for ; Tue, 8 May 2001 09:42:20 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0302.cvx21-bradley.dialup.earthlink.net [209.179.193.47]) by hall.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id MAA28913; Tue, 8 May 2001 12:41:25 -0400 (EDT) Message-ID: <3AF821C9.113680F1@mindspring.com> Date: Tue, 08 May 2001 09:41:45 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dennis Glatting Cc: Dag-Erling Smorgrav , Kris Kennaway , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm References: <20010507112937.V47835-100000@btw.plaintalk.bellevue.wa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis Glatting wrote: > > What is memory exhaustion? > > Uh, when I perform a malloc() and get a NULL back? I > dunno, what do you call that? Hitting an administratively enforced resource limitation. > Why would it kill random processes as opposed to the > offending process? The offending process is the first process that causes a copy-on-write or similar fault, that results in needing to allocate a backing page for it as a result of the trap handler. When you are out of memory, the requesting program can't be satisfied, and so it gets a segmentation violation for an access to a non-existant page. Typically, this will be the first program to request more resources, after hitting the resource starvation point. A number of operating systems will allow programs to be parked "precious". In AIX, this is done by establishing a signal handler for the resource starvation condition; programs without the handler "just die". Programs with the handler are permitted to shut down gracefully. A "precious" program, such as "init" or the swapper, etc., just ignore the signal, and reestablish the handler (if they suffer from SVR3 signal semantics, and can't do it automatically). Various attempts to proactively kill off "resource pigs" have had limited historical success (generally, these are your most precious processes). Other common approaches are to support the "sticky bit" on executables, which causes their pages to be loaded into core, and wired down, so that they can never hit an overcommit barrier and get themselves terminated; similarly, there are OS's which permit a command to be run to ensure that resource reservations exist for a process' resource limits, as set by the system. This tends to "waste" resources, since programs rarely need all of the resources they could possibly ever need. The formal name for this last approach is called "The Banker's Algorithm"; search for that phrase, in conjunction with the name of its author, Djikstra, and you will find _a lot_ of information on overcommit architectures. > Regardless, the code shouldn't be crashing the kernel. Agreed. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 10:37:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from EnContacto.Net (adsl-63-205-16-205.dsl.mtry01.pacbell.net [63.205.16.205]) by hub.freebsd.org (Postfix) with ESMTP id 79F4E37B424 for ; Tue, 8 May 2001 10:37:07 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Received: (from root@localhost) by EnContacto.Net (8.11.3/8.11.3) id f48Hatw98866 for current@FreeBSD.ORG; Tue, 8 May 2001 10:36:55 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Received: from 63.205.16.202 ( [63.205.16.202]) as user eculp@EnContacto.Net by Mail.PasionLatina.Org with HTTP; Tue, 8 May 2001 10:36:55 -0700 Message-ID: <989343415.3af82eb7427c3@Mail.PasionLatina.Org> Date: Tue, 8 May 2001 10:36:55 -0700 From: "Edwin L. Culp" To: current@FreeBSD.ORG Subject: DELL 2 X PIII/500Mhz, SCSI/Adaptec/(QUANTUM ATLAS) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="-MOQ9893434152a680a3ec696ee35528043472f80bfca" User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs X-Originating-IP: 63.205.16.202 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. ---MOQ9893434152a680a3ec696ee35528043472f80bfca Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit A couple of days ago, I installed current on a Dell that had been an NT server. Everything works fine except is seems very slow. A make world on current takes over 5 hours. A little more than my old K6-2 300 laptop. This is the first SMP kernel I have used but I have disabled it with no noticable difference in speed. I'm sure that I am missing something very basic. I have attached my dmesg and would appreciate any suggestions as to a starting point to speed it up. Thanks, ed ----------------------------------------------------------------------- The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn and relearn. --Alvin Toffler ---MOQ9893434152a680a3ec696ee35528043472f80bfca Content-Type: application/octet-stream; name="dmesg.lis0" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="dmesg.lis0" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDEgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0I ChjKSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOT kzLCAxOTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiB BbGwgcmlnaHRzIHJlc2VydmVkLgpGcmVlQlNEIDUuMC1DVVJSRU5UICMwOiBTYXQgTWF5ICA1 IDEwOjA0OjIyIFBEVCAyMDAxCiAgICByb290QGNhc2EtMjA0LmVuY29udGFjdG8ubmV0Oi91c 3Ivb2JqL3Vzci9zcmMvc3lzL2dlbmVyaWMKVGltZWNvdW50ZXIgImk4MjU0IiAgZnJlcXVlbm N5IDExOTMxODIgSHoKQ1BVOiBQZW50aXVtIElJSS9QZW50aXVtIElJSSBYZW9uL0NlbGVyb24 gKDQ5Ny40NC1NSHogNjg2LWNsYXNzIENQVSkKICBPcmlnaW4gPSAiR2VudWluZUludGVsIiAg SWQgPSAweDY3MyAgU3RlcHBpbmcgPSAzCiAgRmVhdHVyZXM9MHgzODNmYmZmPEZQVSxWTUUsR EUsUFNFLFRTQyxNU1IsUEFFLE1DRSxDWDgsQVBJQyxTRVAsTVRSUixQR0UsTUNBLENNT1YsUE FULFBTRTM2LE1NWCxGWFNSLFNTRT4KcmVhbCBtZW1vcnkgID0gMTA3Mzc0MTgyNCAoMTA0ODU 3NksgYnl0ZXMpCmF2YWlsIG1lbW9yeSA9IDEwNDA1MDI3ODQgKDEwMTYxMTZLIGJ5dGVzKQpD aGFuZ2luZyBBUElDIElEIGZvciBJTyBBUElDICMwIGZyb20gMCB0byAyIG9uIGNoaXAKUHJvZ 3JhbW1pbmcgMjQgcGlucyBpbiBJT0FQSUMgIzAKSU9BUElDICMwIGludHBpbiAyIC0+IGlycS AwCkZyZWVCU0QvU01QOiBNdWx0aXByb2Nlc3NvciBTeXN0ZW0gRGV0ZWN0ZWQ6IDIgQ1BVcwo gY3B1MCAoQlNQKTogYXBpYyBpZDogIDEsIHZlcnNpb246IDB4MDAwNDAwMTEsIGF0IDB4ZmVl MDAwMDAKIGNwdTEgKEFQKTogIGFwaWMgaWQ6ICAwLCB2ZXJzaW9uOiAweDAwMDQwMDExLCBhd CAweGZlZTAwMDAwCiBpbzAgKEFQSUMpOiBhcGljIGlkOiAgMiwgdmVyc2lvbjogMHgwMDE3MD AxMSwgYXQgMHhmZWMwMDAwMApQcmVsb2FkZWQgZWxmIGtlcm5lbCAia2VybmVsIiBhdCAweGM wNDkyMDAwLgpQZW50aXVtIFBybyBNVFJSIHN1cHBvcnQgZW5hYmxlZApVc2luZyAkUElSIHRh YmxlLCAxMCBlbnRyaWVzIGF0IDB4YzAwZmM0MjAKbnB4MDogPG1hdGggcHJvY2Vzc29yPiBvb iBtb3RoZXJib2FyZApucHgwOiBJTlQgMTYgaW50ZXJmYWNlCnBjaWIwOiA8SW50ZWwgODI0ND NCWCAoNDQwIEJYKSBob3N0IHRvIFBDSSBicmlkZ2U+IGF0IHBjaWJ1cyAwIG9uIG1vdGhlcmJ vYXJkCklPQVBJQyAjMCBpbnRwaW4gMTkgLT4gaXJxIDIKSU9BUElDICMwIGludHBpbiAxNyAt PiBpcnEgMTAKcGNpMDogPFBDSSBidXM+IG9uIHBjaWIwCnBjaWIxOiA8UENJLVBDSSBicmlkZ 2U+IGF0IGRldmljZSAxLjAgb24gcGNpMApwY2kxOiA8UENJIGJ1cz4gb24gcGNpYjEKcGNpMT ogPGRpc3BsYXksIFZHQT4gYXQgMC4wIChubyBkcml2ZXIgYXR0YWNoZWQpCnBjaWIyOiA8UEN JLVBDSSBicmlkZ2U+IGF0IGRldmljZSAyLjAgb24gcGNpMApJT0FQSUMgIzAgaW50cGluIDE2 IC0+IGlycSAxMQpwY2kyOiA8UENJIGJ1cz4gb24gcGNpYjIKYWhjMDogPEFkYXB0ZWMgYWljN zg5MC85MSBVbHRyYTIgU0NTSSBhZGFwdGVyPiBwb3J0IDB4ZGMwMC0weGRjZmYgbWVtIDB4Zj lmZmYwMDAtMHhmOWZmZmZmZiBpcnEgMTEgYXQgZGV2aWNlIDExLjAgb24gcGNpMgphaWM3ODk wLzkxOiBXaWRlIENoYW5uZWwgQSwgU0NTSSBJZD03LCAzMi8yNTUgU0NCcwppc2FiMDogPFBD SS1JU0EgYnJpZGdlPiBhdCBkZXZpY2UgNy4wIG9uIHBjaTAKaXNhMDogPElTQSBidXM+IG9uI GlzYWIwCmF0YXBjaTA6IDxJbnRlbCBQSUlYNCBBVEEzMyBjb250cm9sbGVyPiBwb3J0IDB4Zm ZhMC0weGZmYWYgYXQgZGV2aWNlIDcuMSBvbiBwY2kwCmF0YTA6IGF0IDB4MWYwIGlycSAxNCB vbiBhdGFwY2kwCmF0YTE6IGF0IDB4MTcwIGlycSAxNSBvbiBhdGFwY2kwCnVoY2kwOiA8SW50 ZWwgODIzNzFBQi9FQiAoUElJWDQpIFVTQiBjb250cm9sbGVyPiBwb3J0IDB4Y2NlMC0weGNjZ mYgaXJxIDIgYXQgZGV2aWNlIDcuMiBvbiBwY2kwCnVzYjA6IDxJbnRlbCA4MjM3MUFCL0VCIC hQSUlYNCkgVVNCIGNvbnRyb2xsZXI+IG9uIHVoY2kwCnVzYjA6IFVTQiByZXZpc2lvbiAxLjA KdWh1YjA6IEludGVsIFVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwg YWRkciAxCnVodWIwOiAyIHBvcnRzIHdpdGggMiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZApUa W1lY291bnRlciAiUElJWCIgIGZyZXF1ZW5jeSAzNTc5NTQ1IEh6CnBjaTA6IDxicmlkZ2UsIF BDSS11bmtub3duPiBhdCA3LjMgKG5vIGRyaXZlciBhdHRhY2hlZCkKeGwwOiA8M0NvbSAzYzk 4MCBGYXN0IEV0aGVybGluayBYTD4gcG9ydCAweGNjMDAtMHhjYzdmIG1lbSAweGZlMDAwMDAw LTB4ZmUwMDAwN2YgaXJxIDEwIGF0IGRldmljZSAxMy4wIG9uIHBjaTAKeGwwOiBFdGhlcm5ld CBhZGRyZXNzOiAwMDo1MDpkYToyNTowODpmMAptaWlidXMwOiA8TUlJIGJ1cz4gb24geGwwCn hscGh5MDogPDNDb20gaW50ZXJuYWwgbWVkaWEgaW50ZXJmYWNlPiBvbiBtaWlidXMwCnhscGh 5MDogIDEwYmFzZVQsIDEwYmFzZVQtRkRYLCAxMDBiYXNlVFgsIDEwMGJhc2VUWC1GRFgsIGF1 dG8KYXRrYmRjMDogPEtleWJvYXJkIGNvbnRyb2xsZXIgKGk4MDQyKT4gYXQgcG9ydCAweDYwL DB4NjQgb24gaXNhMApmZGMwOiA8TkVDIDcyMDY1QiBvciBjbG9uZT4gYXQgcG9ydCAweDNmMC 0weDNmNSwweDNmNyBpcnEgNiBkcnEgMiBvbiBpc2EwCmZkYzA6IEZJRk8gZW5hYmxlZCwgOCB ieXRlcyB0aHJlc2hvbGQKZmQwOiA8MTQ0MC1LQiAzLjUiIGRyaXZlPiBvbiBmZGMwIGRyaXZl IDAKcHBjMDogPFBhcmFsbGVsIHBvcnQ+IGF0IHBvcnQgMHgzNzgtMHgzN2YgaXJxIDcgb24ga XNhMApwcGMwOiBTTUMtbGlrZSBjaGlwc2V0IChFQ1AvRVBQL1BTMi9OSUJCTEUpIGluIENPTV BBVElCTEUgbW9kZQpwcGMwOiBGSUZPIHdpdGggMTYvMTYvOCBieXRlcyB0aHJlc2hvbGQKcGx pcDA6IDxQTElQIG5ldHdvcmsgaW50ZXJmYWNlPiBvbiBwcGJ1czAKbHB0MDogPFByaW50ZXI+ IG9uIHBwYnVzMApscHQwOiBJbnRlcnJ1cHQtZHJpdmVuIHBvcnQKcHBpMDogPFBhcmFsbGVsI EkvTz4gb24gcHBidXMwCnNjMDogPFN5c3RlbSBjb25zb2xlPiBhdCBmbGFncyAweDEwMCBvbi Bpc2EwCnNjMDogVkdBIDwxNiB2aXJ0dWFsIGNvbnNvbGVzLCBmbGFncz0weDMwMD4Kc2lvMCB hdCBwb3J0IDB4M2Y4LTB4M2ZmIGlycSA0IGZsYWdzIDB4MTAgb24gaXNhMApzaW8wOiB0eXBl IDE2NTUwQQpzaW8xIGF0IHBvcnQgMHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhMApzaW8xOiB0e XBlIDE2NTUwQQp2Z2EwOiA8R2VuZXJpYyBJU0EgVkdBPiBhdCBwb3J0IDB4M2MwLTB4M2RmIG lvbWVtIDB4YTAwMDAtMHhiZmZmZiBvbiBpc2EwCnVua25vd246IDxQTlAwNTAxPiBjYW4ndCB hc3NpZ24gcmVzb3VyY2VzCnVua25vd246IDxQTlAwNTAxPiBjYW4ndCBhc3NpZ24gcmVzb3Vy Y2VzCnVua25vd246IDxQTlAwNDAxPiBjYW4ndCBhc3NpZ24gcmVzb3VyY2VzCnVua25vd246I DxQTlAwNzAwPiBjYW4ndCBhc3NpZ24gcmVzb3VyY2VzCnVua25vd246IDxQTlAwMzAzPiBjYW 4ndCBhc3NpZ24gcmVzb3VyY2VzCkFQSUNfSU86IFRlc3RpbmcgODI1NCBpbnRlcnJ1cHQgZGV saXZlcnkKQVBJQ19JTzogcm91dGluZyA4MjU0IHZpYSBJT0FQSUMgIzAgaW50cGluIDIKRFVN TVlORVQgaW5pdGlhbGl6ZWQgKDAxMDEyNCkKSVAgcGFja2V0IGZpbHRlcmluZyBpbml0aWFsa XplZCwgZGl2ZXJ0IGVuYWJsZWQsIHJ1bGUtYmFzZWQgZm9yd2FyZGluZyBlbmFibGVkLCBkZW ZhdWx0IHRvIGFjY2VwdCwgbG9nZ2luZyBsaW1pdGVkIHRvIDEwMCBwYWNrZXRzL2VudHJ5IGJ 5IGRlZmF1bHQKYWNkMDogQ0RST00gPFNBTVNVTkcgU0MtMTQwQj4gYXQgYXRhMS1tYXN0ZXIg UElPNApXYWl0aW5nIDE1IHNlY29uZHMgZm9yIFNDU0kgZGV2aWNlcyB0byBzZXR0bGUKTW91b nRpbmcgcm9vdCBmcm9tIHVmczovZGV2L2RhMHMxYQpkYTAgYXQgYWhjMCBidXMgMCB0YXJnZX QgMSBsdW4gMApkYTA6IDxRVUFOVFVNIEFUTEFTIFYgMTggV0xTIDAyMDE+IEZpeGVkIERpcmV jdCBBY2Nlc3MgU0NTSS0zIGRldmljZSAKZGEwOiA4MC4wMDBNQi9zIHRyYW5zZmVycyAoNDAu MDAwTUh6LCBvZmZzZXQgNjMsIDE2Yml0KSwgVGFnZ2VkIFF1ZXVlaW5nIEVuYWJsZWQKZGEwO iAxNzM2Nk1CICgzNTU2NjQ5OSA1MTIgYnl0ZSBzZWN0b3JzOiAyNTVIIDYzUy9UIDIyMTNDKQ pTTVA6IEFQIENQVSAjMSBMYXVuY2hlZCEKbG9jayBvcmRlciByZXZlcnNhbAogMXN0IDB4YzA 0MTI4YzAgbW50dm5vZGUgQCAvdXNyL3NyYy9zeXMvdWZzL2Zmcy9mZnNfdmZzb3BzLmM6OTc0 CiAybmQgMHhlMWQ4ZGYyYyB2bm9kZSBpbnRlcmxvY2sgQCAvdXNyL3NyYy9zeXMvdWZzL2Zmc y9mZnNfdmZzb3BzLmM6OTgzCg== ---MOQ9893434152a680a3ec696ee35528043472f80bfca-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 10:56:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from ambar.ofermundo.com.ar (h066060007247.isol.net.ar [66.60.7.247]) by hub.freebsd.org (Postfix) with ESMTP id 89D3537B423 for ; Tue, 8 May 2001 10:56:09 -0700 (PDT) (envelope-from freebsd@grunblatt.com.ar) Received: from dialup239.icatel.net (dialup239.icatel.net [200.47.39.239]) by ambar.ofermundo.com.ar (8.9.3/8.8.7) with ESMTP id OAA05685 for ; Tue, 8 May 2001 14:56:06 -0300 Date: Tue, 8 May 2001 17:57:34 -0300 (ART) From: Daniel X-X-Sender: To: Subject: world broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG world broken at /usr/src/usr.sbin/pstat/pstat.c because IN_SHLOCK is undeclared, is this something new added to sys/ufs/ufs/inode.h ? d.- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 11:16:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B3F0237B43C for ; Tue, 8 May 2001 11:16:42 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA23372 for ; Tue, 8 May 2001 11:16:43 -0700 Date: Tue, 8 May 2001 11:16:41 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: different world breakage (Perl bootstrap, alpha) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> gnu/usr.bin/perl/perl Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Extracting writemain (with variable substitutions) Extracting myconfig (with variable substitutions) Missing right curly or square bracket at lib/SelfLoader.pm line 69, at end of line syntax error at lib/SelfLoader.pm line 69, at EOF Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm line 17. Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line 37. Compilation failed in require at /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. *** Error code 255 Stop in /usr/src/gnu/usr.bin/perl/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 11:23:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 4DC0837B423 for ; Tue, 8 May 2001 11:23:30 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f48IM5G20490; Tue, 8 May 2001 11:22:05 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <989343415.3af82eb7427c3@Mail.PasionLatina.Org> Date: Tue, 08 May 2001 11:21:13 -0700 (PDT) From: John Baldwin To: "Edwin L. Culp" Subject: RE: DELL 2 X PIII/500Mhz, SCSI/Adaptec/(QUANTUM ATLAS) Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-May-01 Edwin L. Culp wrote: > A couple of days ago, I installed current on a Dell that had been an > NT server. Everything works fine except is seems very slow. A make > world on current takes over 5 hours. A little more than my old K6-2 > 300 laptop. > > This is the first SMP kernel I have used but I have disabled it with no > noticable difference in speed. > > I'm sure that I am missing something very basic. I have attached my dmesg > and would appreciate any suggestions as to a starting point to speed it up. > > Thanks, > > ed -current has lots of debugging on by default. The witness code especially is rather slow. However, it is helpful in finding bugs. You can try disabling witness by building a custom kernel or setting the loader tunable debug.witness_watch to 0. If you really need performance, you may want to run stable instead of current anyways. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 11:57:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from heechee.tobez.org (254.adsl0.ryv.worldonline.dk [213.237.10.254]) by hub.freebsd.org (Postfix) with ESMTP id 7F6E737B423 for ; Tue, 8 May 2001 11:57:07 -0700 (PDT) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id 534FE540C; Tue, 8 May 2001 20:56:53 +0200 (CEST) Date: Tue, 8 May 2001 20:56:53 +0200 From: Anton Berezin To: Matthew Jacob Cc: current@freebsd.org Subject: Re: different world breakage (Perl bootstrap, alpha) Message-ID: <20010508205653.F22065@heechee.tobez.org> Mail-Followup-To: Anton Berezin , Matthew Jacob , current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Tue, May 08, 2001 at 11:16:41AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please see 200105022124.f42LOup61232@gratis.grondar.za. On Tue, May 08, 2001 at 11:16:41AM -0700, Matthew Jacob wrote: > ===> gnu/usr.bin/perl/perl > Extracting config.h (with variable substitutions) > Extracting cflags (with variable substitutions) > Extracting writemain (with variable substitutions) > Extracting myconfig (with variable substitutions) > Missing right curly or square bracket at lib/SelfLoader.pm line 69, at end of > line > syntax error at lib/SelfLoader.pm line 69, at EOF > Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm > line 17. > Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. > BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line > 37. > Compilation failed in require at > /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. > *** Error code 255 > > Stop in /usr/src/gnu/usr.bin/perl/perl. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/perl. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin. > *** Error code 1 > > Stop in /usr/src/gnu. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 -- May the tuna salad be with you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 12:12:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251]) by hub.freebsd.org (Postfix) with ESMTP id 8F78A37B423 for ; Tue, 8 May 2001 12:12:04 -0700 (PDT) (envelope-from huntting@hunkular.glarp.com) Received: from localhost (localhost [127.0.0.1]) by hunkular.glarp.com (8.11.1/8.11.1) with ESMTP id f48JC3053365 for ; Tue, 8 May 2001 13:12:04 -0600 (MDT) (envelope-from huntting@hunkular.glarp.com) Message-Id: <200105081912.f48JC3053365@hunkular.glarp.com> To: freebsd-current@freebsd.org Subject: user connection request data w/ recvmsg(2)/getsockopt(2) From: huntting@glarp.com Date: Tue, 08 May 2001 13:12:03 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following jucy tidbit has been hiding in the accept(2) man page for several years, but has apparently never been implemented. One can obtain user connection request data without confirming the con- nection by issuing a recvmsg(2) call with an msg_iovlen of 0 and a non- zero msg_controllen, or by issuing a getsockopt(2) request. Similarly, one can provide user connection rejection information by issuing a sendmsg(2) call with providing only the control information, or by call- ing setsockopt(2). There is no mention of this feature in the man pages for getsockopt(2), recvmsg(2) or sendmsg(2). Rather than correct the accept(2), I'd really like to see this feature implemented in the kernel, and incorporated into tcp wrapper. I think it would really help limit limit the effectivness of portscanning. Who's idea was this origionally and do they have thoughts on why it should or should not be implemented? Any gottchas? brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 12:14:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id BA95637B422 for ; Tue, 8 May 2001 12:14:56 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f48JErg08182; Tue, 8 May 2001 12:14:53 -0700 (PDT) Date: Tue, 8 May 2001 12:14:53 -0700 From: Alfred Perlstein To: huntting@glarp.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: user connection request data w/ recvmsg(2)/getsockopt(2) Message-ID: <20010508121452.N18676@fw.wintelcom.net> References: <200105081912.f48JC3053365@hunkular.glarp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105081912.f48JC3053365@hunkular.glarp.com>; from huntting@glarp.com on Tue, May 08, 2001 at 01:12:03PM -0600 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * huntting@glarp.com [010508 12:12] wrote: > > The following jucy tidbit has been hiding in the accept(2) man page > for several years, but has apparently never been implemented. > > One can obtain user connection request data without confirming the con- > nection by issuing a recvmsg(2) call with an msg_iovlen of 0 and a non- > zero msg_controllen, or by issuing a getsockopt(2) request. Similarly, > one can provide user connection rejection information by issuing a > sendmsg(2) call with providing only the control information, or by call- > ing setsockopt(2). > > There is no mention of this feature in the man pages for getsockopt(2), > recvmsg(2) or sendmsg(2). > > Rather than correct the accept(2), I'd really like to see this > feature implemented in the kernel, and incorporated into tcp wrapper. > I think it would really help limit limit the effectivness of > portscanning. > > Who's idea was this origionally and do they have thoughts on why > it should or should not be implemented? Any gottchas? You should investigate the way this is done in the TLI interface. It would be nice to have a hybrid TLI/BSD socket interface one day. TLI is not really fast enough for server programs but a hybird would offer a lot of flexibility. -- -Alfred Perlstein - [alfred@freebsd.org] http://www.egr.unlv.edu/~slumos/on-netbsd.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 12:30:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.org.ru (sweet.etrust.ru [194.84.67.5]) by hub.freebsd.org (Postfix) with ESMTP id 4C48837B422 for ; Tue, 8 May 2001 12:30:05 -0700 (PDT) (envelope-from osa@freebsd.org.ru) Received: by freebsd.org.ru (Postfix, from userid 1000) id 2C34F22F; Tue, 8 May 2001 23:30:03 +0400 (MSD) Date: Tue, 8 May 2001 23:30:03 +0400 From: "Sergey A. Osokin" To: current@FreeBSD.org Subject: world broken... Message-ID: <20010508233003.A88044@freebsd.org.ru> Reply-To: osa@FreeBSD.org.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. After resup my sources (a 2 hours ago) i tried make buildworld and it failed: Extracting myconfig (with variable substitutions) Missing right curly or square bracket at lib/SelfLoader.pm line 69, at end of line syntax error at lib/SelfLoader.pm line 69, at EOF Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm line 17. Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line 37. Compilation failed in require at /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. *** Error code 255 Stop in /usr/src/gnu/usr.bin/perl/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Any idea? -- Rgdz, /"\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN osa@freebsd.org.ru X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 13:36:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from psplngp1.transplace.com (ppp-65-64-216-134.ded.swbell.net [65.64.216.134]) by hub.freebsd.org (Postfix) with ESMTP id 8315C37B423 for ; Tue, 8 May 2001 13:36:50 -0700 (PDT) (envelope-from corey.brune@transplace.com) Received: from transplace.com ([10.67.100.127]) by psplngp1.transplace.com (Lotus Domino Release 5.0.6a) with ESMTP id 2001050815364860:4672 ; Tue, 8 May 2001 15:36:48 -0500 Message-ID: <3AF858DD.E9A13342@transplace.com> Date: Tue, 08 May 2001 15:36:46 -0500 From: Corey Brune X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Kernel secure level X-MIMETrack: Itemize by SMTP Server on psplngp1/com(Release 5.0.6a |January 17, 2001) at 05/08/2001 03:36:48 PM, Serialize by Router on psplngp1/com(Release 5.0.6a |January 17, 2001) at 05/08/2001 03:36:50 PM, Serialize complete at 05/08/2001 03:36:50 PM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I forgot the kernel secure level was set to 1 when I started make build. The build almost finishes, but dies when it tries to install /usr/lib/libcrypt.so.2 saying operation not permitted. I cannot chflags because of the secure level. Does anyone know a way around this? Thanks for any suggestions, Corey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 14: 2:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 2F2F137B422 for ; Tue, 8 May 2001 14:02:09 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id 71E0D3E28; Tue, 8 May 2001 14:01:53 -0700 (PDT) To: Corey Brune Cc: current@freebsd.org Subject: Re: Kernel secure level In-Reply-To: <3AF858DD.E9A13342@transplace.com>; from corey.brune@transplace.com on "Tue, 08 May 2001 15:36:46 -0500" Date: Tue, 08 May 2001 14:01:53 -0700 From: Dima Dorfman Message-Id: <20010508210153.71E0D3E28@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Corey Brune writes: > I forgot the kernel secure level was set to 1 when I started make build. > The build almost finishes, but dies when it tries to install > /usr/lib/libcrypt.so.2 saying operation not permitted. I cannot chflags > because of the secure level. Does anyone know a way around this? This is answered at least three times in the FAQ, not to mention the Handbook and the man pages. http://www.freebsd.org/doc/en_US.ISO_8859-1/books/faq/admin.html#KERNEL-CHFLAG-FAILURE http://www.freebsd.org/doc/en_US.ISO_8859-1/books/faq/admin.html#UNSETTING-SCHG http://www.freebsd.org/doc/en_US.ISO_8859-1/books/faq/admin.html#SECURELEVEL init(8) Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 14:18:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D166037B422 for ; Tue, 8 May 2001 14:18:27 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id XAA58315; Tue, 8 May 2001 23:18:24 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: tlambert2@mindspring.com Cc: Dennis Glatting , Kris Kennaway , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm References: <20010507074503.Y24943-100000@btw.plaintalk.bellevue.wa.us> <3AF81B16.7EC1F3DE@mindspring.com> From: Dag-Erling Smorgrav Date: 08 May 2001 23:18:23 +0200 In-Reply-To: <3AF81B16.7EC1F3DE@mindspring.com> Message-ID: Lines: 33 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=-=-= Terry Lambert writes: > So now the question becomes "what is he testing that is > resulting in 4.3 locking up?". Good question. It does some non-trivial stuff besides allocating: buffered I/O and fork()/exec()'ing sync(1). > Your suggested replacement test might be fun to run, but I > think it wouldn't lock up 4.3... Nope. But the attached - much nastier - program did trash my -CURRENT box when run as root in an xterm. What happened was that the X server faulted and died, rendering the console unusable; the serial console filled up with getswapspace() errors, so the only recourse was a break to DDB followed by 'call boot', which managed to sync all filesystems except the root, but failed to actually reboot the machine. I would *love* to have a DDB equivalent to 'kill -9', so I could drop to the DDB prompt, check ps, kill a process or two, and drop back out of DDB. It would have saved me a reboot and a longish fsck in this case. A second try, on the text console and as a regular user, got to 643 MB before it, top(1) and an xterm were killed. This is a 5.0-CURRENT system with 192 MB RAM and 512 MB swap, so 643 MB is pretty close to max capacity. DES -- Dag-Erling Smorgrav - des@ofug.org --=-=-= Content-Disposition: attachment; filename=adsp.c #include #include #include #include #define CHUNKSIZE 1048576 #define CHUNKS 4096 int main(int argc, char *argv[]) { int i, j, n, ps; char *p; n = (argc > 1) ? atoi(argv[1]) : CHUNKS; ps = getpagesize(); for (i = 0; i < n; ++i) { if ((p = mmap(NULL, CHUNKSIZE, PROT_WRITE, MAP_ANON, -1, 0)) == NULL) { write(1, "\n:(\n", 4); exit(1); } write(1, ".", 1); for (j = 0; j < CHUNKSIZE; j += ps) p[j] = 1; } write(1, "\n:)\n", 4); read(0, p, 1); exit(0); } --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 14:26: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2861E37B422 for ; Tue, 8 May 2001 14:26:04 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id XAA58345; Tue, 8 May 2001 23:26:01 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: tlambert2@mindspring.com Cc: Dennis Glatting , Kris Kennaway , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm References: <20010507112937.V47835-100000@btw.plaintalk.bellevue.wa.us> <3AF821C9.113680F1@mindspring.com> From: Dag-Erling Smorgrav Date: 08 May 2001 23:26:00 +0200 In-Reply-To: <3AF821C9.113680F1@mindspring.com> Message-ID: Lines: 28 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > A number of operating systems will allow programs to be > parked "precious". In AIX, this is done by establishing > a signal handler for the resource starvation condition; > programs without the handler "just die". Programs with > the handler are permitted to shut down gracefully. A > "precious" program, such as "init" or the swapper, etc., > just ignore the signal, and reestablish the handler (if > they suffer from SVR3 signal semantics, and can't do it > automatically). Yes. In fact, the new signal stuff was written as a consequence of a previous round of this dicussion, where somebody pointed out that we couldn't implement this because we already had 32 signals, and that the old signal code didn't support more than 32 signals. Now that this is no longer an issue, I wouldn't mind seeing this implemented... But you need to start signalling some yards from the edge of the cliff instead of waiting until you stand at the brink, so your apps get a fighting chance to catch and handle the signal. You might want two signals, actually - one that defaults to SIG_IGN (but some apps may want to catch it and start GCing to play nice with their brethren), and one triggered a little later that kills any process that doesn't catch it. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 14:29:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2B3B437B422 for ; Tue, 8 May 2001 14:29:39 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA24187; Tue, 8 May 2001 14:29:36 -0700 Date: Tue, 8 May 2001 14:29:35 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Anton Berezin Cc: current@freebsd.org Subject: Re: different world breakage (Perl bootstrap, alpha) In-Reply-To: <20010508205653.F22065@heechee.tobez.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And how is that piece of mail (about cvsup) pertinent? > Please see 200105022124.f42LOup61232@gratis.grondar.za. > > On Tue, May 08, 2001 at 11:16:41AM -0700, Matthew Jacob wrote: > > > ===> gnu/usr.bin/perl/perl > > Extracting config.h (with variable substitutions) > > Extracting cflags (with variable substitutions) > > Extracting writemain (with variable substitutions) > > Extracting myconfig (with variable substitutions) > > Missing right curly or square bracket at lib/SelfLoader.pm line 69, at end of > > line > > syntax error at lib/SelfLoader.pm line 69, at EOF > > Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm > > line 17. > > Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. > > BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line > > 37. > > Compilation failed in require at > > /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. > > *** Error code 255 > > > > Stop in /usr/src/gnu/usr.bin/perl/perl. > > *** Error code 1 > > > > Stop in /usr/src/gnu/usr.bin/perl. > > *** Error code 1 > > > > Stop in /usr/src/gnu/usr.bin. > > *** Error code 1 > > > > Stop in /usr/src/gnu. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 14:37:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from heechee.tobez.org (254.adsl0.ryv.worldonline.dk [213.237.10.254]) by hub.freebsd.org (Postfix) with ESMTP id 76E7E37B422 for ; Tue, 8 May 2001 14:37:23 -0700 (PDT) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id E3B01540C; Tue, 8 May 2001 23:37:18 +0200 (CEST) Date: Tue, 8 May 2001 23:37:18 +0200 From: Anton Berezin To: Matthew Jacob Cc: current@freebsd.org Subject: Re: different world breakage (Perl bootstrap, alpha) Message-ID: <20010508233718.D30506@heechee.tobez.org> Mail-Followup-To: Anton Berezin , Matthew Jacob , current@freebsd.org References: <20010508205653.F22065@heechee.tobez.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Tue, May 08, 2001 at 02:29:35PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 08, 2001 at 02:29:35PM -0700, Matthew Jacob wrote: > And how is that piece of mail (about cvsup) pertinent? Well, there is a follow-up: 20010502233523.A862@heechee.tobez.org , or http://www.freebsd.org/cgi/getmsg.cgi?fetch=195431+0+/usr/local/www/db/text/2001/freebsd-current/20010506.freebsd-current Cheers, \Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 14:38:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from psplngp1.transplace.com (ppp-65-64-216-134.ded.swbell.net [65.64.216.134]) by hub.freebsd.org (Postfix) with ESMTP id 7F4CD37B423 for ; Tue, 8 May 2001 14:38:08 -0700 (PDT) (envelope-from corey.brune@transplace.com) Received: from transplace.com ([10.67.100.127]) by psplngp1.transplace.com (Lotus Domino Release 5.0.6a) with ESMTP id 2001050816380518:5056 ; Tue, 8 May 2001 16:38:05 -0500 Message-ID: <3AF86739.C5C92EB8@transplace.com> Date: Tue, 08 May 2001 16:38:02 -0500 From: Corey Brune X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 Cc: current@freebsd.org Subject: Re: Kernel secure level References: <20010508210153.71E0D3E28@bazooka.unixfreak.org> X-MIMETrack: Itemize by SMTP Server on psplngp1/com(Release 5.0.6a |January 17, 2001) at 05/08/2001 04:38:05 PM, Serialize by Router on psplngp1/com(Release 5.0.6a |January 17, 2001) at 05/08/2001 04:38:07 PM, Serialize complete at 05/08/2001 04:38:07 PM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dima Dorfman wrote: > Corey Brune writes: > > I forgot the kernel secure level was set to 1 when I started make build. > > The build almost finishes, but dies when it tries to install > > /usr/lib/libcrypt.so.2 saying operation not permitted. I cannot chflags > > because of the secure level. Does anyone know a way around this? > > This is answered at least three times in the FAQ, not to mention the > Handbook and the man pages. > > http://www.freebsd.org/doc/en_US.ISO_8859-1/books/faq/admin.html#KERNEL-CHFLAG-FAILURE > http://www.freebsd.org/doc/en_US.ISO_8859-1/books/faq/admin.html#UNSETTING-SCHG > http://www.freebsd.org/doc/en_US.ISO_8859-1/books/faq/admin.html#SECURELEVEL > init(8) > > Dima Dorfman > dima@unixfreak.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Yea, I saw the first two docs, but I read the explanation wrong the first time. Thanks for the quick help. Corey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 16: 3:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 33BD537B422 for ; Tue, 8 May 2001 16:03:12 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA24507 for ; Tue, 8 May 2001 16:03:12 -0700 Date: Tue, 8 May 2001 16:03:11 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: another one....rlogin (p_match: clnt_call: RPC: Program unavailable) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ This time I *did* try and use the FreeBSD mailing list search engined- to no result that I can see. ] I now get, when I try and rlogin: p_match: clnt_call: RPC: Program unavailable in the client. I *have* changed hosts.allow to allow rpcbind locally in hosts.allow (if that's pertinent): ALL: 127.0.0.0/255.0.0.0 : ALLOW ALL: 10.0.0.0/255.0.0.0 : ALLOW ALL: 192.67.166.0/255.255.255.0 : ALLOW rpcbind : 192.67.166.0/255.255.255.0 : allow rpcbind : 10.0.0.0/255.255.255.0 : allow rpcbind is running without arguments. rlogin is enabled in inetd.conf. There is nothing in UPDATING that seems to pertain to this. This is a mergemaster'ed top of tree as of last night fresh x86 build. Also I experience the same slogin problem reported recently as well: May 8 15:53:27 quarm sshd[556]: fatal: PAM setcred failed[6]: Permission denied May 8 16:00:24 quarm sshd[748]: fatal: PAM setcred failed[6]: Permission denied To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 16:44: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 4303637B42C for ; Tue, 8 May 2001 16:44:00 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id F0CB03E28; Tue, 8 May 2001 16:43:53 -0700 (PDT) To: Dag-Erling Smorgrav Cc: current@freebsd.org Subject: Re: pgm to kill 4.3 via vm In-Reply-To: ; from des@ofug.org on "08 May 2001 23:18:23 +0200" Date: Tue, 08 May 2001 16:43:43 -0700 From: Dima Dorfman Message-Id: <20010508234354.F0CB03E28@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ cc severely trimmed ] Dag-Erling Smorgrav writes: > I would *love* to have a DDB equivalent to 'kill -9', so I could drop > to the DDB prompt, check ps, kill a process or two, and drop back out > of DDB. It would have saved me a reboot and a longish fsck in this > case. Mmm.. I implemented something like this a few days ago for similar reasons. Essentially it's a ddb interface to psignal(). I haven't tried using it to kill something like your program, but I have no reason to think it wouldn't work. Short patch attached. Sample use: db> kill 9 0t500 where '9' is the signal number and '500' is the process id. Dima Dorfman dima@unixfreak.org Index: db_command.c =================================================================== RCS file: /st/src/FreeBSD/src/sys/ddb/db_command.c,v retrieving revision 1.34 diff -u -r1.34 db_command.c --- db_command.c 1999/08/28 00:41:06 1.34 +++ db_command.c 2001/05/08 23:37:59 @@ -36,7 +36,11 @@ */ #include #include +#include +#include +#include #include +#include #include #include @@ -61,6 +65,7 @@ static db_cmdfcn_t db_fncall; static db_cmdfcn_t db_gdb; +static db_cmdfcn_t db_kill; /* XXX this is actually forward-static. */ extern struct command db_show_cmds[]; @@ -405,6 +410,7 @@ { "show", 0, 0, db_show_cmds }, { "ps", db_ps, 0, 0 }, { "gdb", db_gdb, 0, 0 }, + { "kill", db_kill, CS_OWN, 0 }, { (char *)0, } }; @@ -558,4 +564,41 @@ db_printf("Next trap will enter %s\n", boothowto & RB_GDB ? "GDB remote protocol mode" : "DDB debugger"); +} + +static void +db_kill(dummy1, dummy2, dummy3, dummy4) + db_expr_t dummy1; + boolean_t dummy2; + db_expr_t dummy3; + char * dummy4; +{ + struct proc *p; + db_expr_t sig, pid; + + if (!db_expression(&sig)) { + db_printf("Missing signal number\n"); + db_flush_lex(); + return; + } + if (!db_expression(&pid)) { + db_printf("Missing process id\n"); + db_flush_lex(); + return; + } + db_skip_to_eol(); + if (sig < 0 || sig > _SIG_MAXSIG) { + db_printf("Signal number out of range\n"); + db_flush_lex(); + return; + } + + p = pfind(pid); + if (p == NULL) { + db_printf("Can't find process with pid %d\n", pid); + db_flush_lex(); + return; + } + psignal(p, sig); + PROC_UNLOCK(p); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 16:48:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 6523737B42C for ; Tue, 8 May 2001 16:48:20 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f48NldG31584; Tue, 8 May 2001 16:47:39 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 08 May 2001 16:46:50 -0700 (PDT) From: John Baldwin To: Dag-Erling Smorgrav Subject: Re: pgm to kill 4.3 via vm Cc: freebsd-current@FreeBSD.org, freebsd-stable@frebsd.org, Kris Kennaway , Dennis Glatting , tlambert2@mindspring.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-May-01 Dag-Erling Smorgrav wrote: > Terry Lambert writes: >> So now the question becomes "what is he testing that is >> resulting in 4.3 locking up?". > > Good question. It does some non-trivial stuff besides allocating: > buffered I/O and fork()/exec()'ing sync(1). > >> Your suggested replacement test might be fun to run, but I >> think it wouldn't lock up 4.3... > > Nope. But the attached - much nastier - program did trash my -CURRENT > box when run as root in an xterm. What happened was that the X server > faulted and died, rendering the console unusable; the serial console > filled up with getswapspace() errors, so the only recourse was a break > to DDB followed by 'call boot', which managed to sync all filesystems > except the root, but failed to actually reboot the machine. > > I would *love* to have a DDB equivalent to 'kill -9', so I could drop > to the DDB prompt, check ps, kill a process or two, and drop back out > of DDB. It would have saved me a reboot and a longish fsck in this > case. That's easy enough. Well, it used to be at least. You can use 'ps' to find the address of the struct proc (first pointer in the display) and then do 'call psignal(addr, 9)' to send SIGKILL to the process. Then hit 'c' to continue and voila, the process dies. I think that may panic now due to proc lock not being held (though the debugger shouldn't need any locks in theory.) Perhaps mtx_assert() should honor db_active and not panic if it is set. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 20: 0:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from mtiwmhc24.worldnet.att.net (mtiwmhc24.worldnet.att.net [204.127.131.49]) by hub.freebsd.org (Postfix) with ESMTP id E0FDC37B42C for ; Tue, 8 May 2001 20:00:21 -0700 (PDT) (envelope-from wsheets@att.net) Received: from att.net ([12.72.44.20]) by mtiwmhc24.worldnet.att.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010509030020.HAAQ1579.mtiwmhc24.worldnet.att.net@att.net> for ; Wed, 9 May 2001 03:00:20 +0000 To: freebsd-current@freebsd.org Subject: world broken at pstat From: walt Date: 08 May 2001 19:58:05 -0700 Message-ID: <87heyv6xfm.fsf@att.net> Lines: 25 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsup'd CURRENT 5-8-2001 around 1900 PST make buildworld stopped here: ===> usr.sbin/pstat cc -O -pipe -I/usr/src/usr.sbin/pstat/../../sys -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/pstat/pstat.c /usr/src/usr.sbin/pstat/pstat.c: In function `ufs_print': /usr/src/usr.sbin/pstat/pstat.c:494: `IN_SHLOCK' undeclared (first use in this function) /usr/src/usr.sbin/pstat/pstat.c:494: (Each undeclared identifier is reported only once /usr/src/usr.sbin/pstat/pstat.c:494: for each function it appears in.) /usr/src/usr.sbin/pstat/pstat.c:496: `IN_EXLOCK' undeclared (first use in this function) *** Error code 1 Stop in /usr/src/usr.sbin/pstat. *** Error code 1 Stop in /usr/src/usr.sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 20:10:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id A272637B422 for ; Tue, 8 May 2001 20:10:28 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f493AED56308; Tue, 8 May 2001 20:10:14 -0700 (PDT) Date: Tue, 8 May 2001 20:10:14 -0700 (PDT) From: David Wolfskill Message-Id: <200105090310.f493AED56308@bunrab.catwhisker.org> To: freebsd-current@FreeBSD.ORG, wsheets@att.net Subject: Re: world broken at pstat In-Reply-To: <87heyv6xfm.fsf@att.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: walt >Date: 08 May 2001 19:58:05 -0700 >cvsup'd CURRENT 5-8-2001 around 1900 PST >make buildworld stopped here: >===> usr.sbin/pstat >cc -O -pipe -I/usr/src/usr.sbin/pstat/../../sys -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/pstat/pstat.c >/usr/src/usr.sbin/pstat/pstat.c: In function `ufs_print': >/usr/src/usr.sbin/pstat/pstat.c:494: `IN_SHLOCK' undeclared (first use in this function) >/usr/src/usr.sbin/pstat/pstat.c:494: (Each undeclared identifier is reported only once >/usr/src/usr.sbin/pstat/pstat.c:494: for each function it appears in.) >/usr/src/usr.sbin/pstat/pstat.c:496: `IN_EXLOCK' undeclared (first use in this function) >*** Error code 1 >Stop in /usr/src/usr.sbin/pstat. >*** Error code 1 Right; appears to be a side-effect of the change to src/sys/ufs/ffs/inode.h in http://docs.freebsd.org/cgi/getmsg.cgi?fetch=254086+0+current/cvs-all, which removed the symbols in question. I commented out the affected part of usr.sbin/pstat.c, thus: Index: pstat.c =================================================================== RCS file: /cvs/freebsd/src/usr.sbin/pstat/pstat.c,v retrieving revision 1.54 diff -u -u -r1.54 pstat.c --- pstat.c 2001/04/29 02:45:39 1.54 +++ pstat.c 2001/05/08 23:15:24 @@ -491,10 +491,12 @@ *flags++ = 'M'; if (flag & IN_RENAME) *flags++ = 'R'; +/* if (flag & IN_SHLOCK) *flags++ = 'S'; if (flag & IN_EXLOCK) *flags++ = 'E'; +*/ if (flag & IN_HASHED) *flags++ = 'H'; if (flag & IN_LAZYMOD) and was able to complete the buildworld, kernel, install, mergemaster, & was able to boot the resulting system. (Still had some annoyances with ssh, but I think those have been well-reported already.) If that section of pstat.c is now obsolete, I'd expect it should be excised, vs. merely commented out -- and pstat.8 ought to be similarly altered. Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 20:32: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id BAFF037B423; Tue, 8 May 2001 20:32:01 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f493Vpf79731; Tue, 8 May 2001 23:31:51 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 8 May 2001 23:31:51 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: John Baldwin Cc: Dag-Erling Smorgrav , freebsd-current@FreeBSD.org, freebsd-stable@frebsd.org, Kris Kennaway , Dennis Glatting , tlambert2@mindspring.com Subject: Re: pgm to kill 4.3 via vm In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 May 2001, John Baldwin wrote: > That's easy enough. Well, it used to be at least. You can use 'ps' to > find the address of the struct proc (first pointer in the display) and > then do 'call psignal(addr, 9)' to send SIGKILL to the process. Then > hit 'c' to continue and voila, the process dies. I think that may panic > now due to proc lock not being held (though the debugger shouldn't need > any locks in theory.) Perhaps mtx_assert() should honor db_active and > not panic if it is set. I followed everything here fine until you asserted that the debugger shouldn't need any locks. I guess I don't see why that is, at least in terms of not corrupting structures. From a practical perspective, the debugger is like any other interupt-driven preemptive code-path: if you want to modify a structure, you need to synchronize appropriately to avoid corrupting the structure. This may not be something you really want to do in a debugger, so in that sense perhaps you *shouldn't* grab a lock in the debugger, but to perform the described action safely, you *should* grab a lock so as not to corrupt fields of the proc structure (i.e., if you broke into the debugger during a non-atomic flags update). Violating system invariants is something you should be allowed to do in a debugger, but this sounded like it was a feature people were looking from to recover from unhappy behavior, not to introduce it :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 8 22:48:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp.wanadoo.nl (smtp.wanadoo.nl [194.134.193.6]) by hub.freebsd.org (Postfix) with ESMTP id 4A39537B422; Tue, 8 May 2001 22:48:56 -0700 (PDT) (envelope-from steveo@eircom.net) Received: from ams-gw.sohara.org (p341.vcu.wanadoo.nl [194.134.200.233]) by smtp.wanadoo.nl (8.11.2/8.11.2) with SMTP id f495mrq14824; Wed, 9 May 2001 07:48:53 +0200 (MET DST) Date: Wed, 9 May 2001 07:48:49 +0200 From: "Steve O'Hara-Smith" To: freebsd@freebsd.org Cc: clefevre@poboxes.com, asmodai@wxs.nl, current@freebsd.org Subject: Re: cp -u patch Message-Id: <20010509074849.1e6a6057.steveo@eircom.net> In-Reply-To: <20010507101838.A8945@dragon.nuxi.com> References: <20010426222132.B55566@daemon.ninth-circle.org> <20010507101838.A8945@dragon.nuxi.com> X-Mailer: Sylpheed version 0.4.63cvs15 (GTK+ 1.2.10; i386-unknown-freebsdelf4.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 May 2001 10:18:38 -0700 current@freebsd.org wrote: > Lets try another realistic example: > > cp -uvp ab* cde*.f* g? h/*.i? j/kl /m > What's the find | cpio invocation for that? When you come up with it, it echo ab* cde*.f* g? h/*.i? j/kl /m | cpio ... Messy - No, Portable - Yes. -- Optimal hardware acceleration for Windows PC (Mac). 9.81 m/s/s applied for (at least) 2s followed by impact with solid object. Optimal software upgrade FreeBSD (OS-X). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 2:17:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 3857037B423; Wed, 9 May 2001 02:17:10 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f499OKW18453; Wed, 9 May 2001 10:24:20 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f499H3B36790; Wed, 9 May 2001 10:17:03 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200105090917.f499H3B36790@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: "Steve O'Hara-Smith" Cc: freebsd@FreeBSD.ORG, clefevre@poboxes.com, asmodai@wxs.nl, current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: cp -u patch In-Reply-To: Message from "Steve O'Hara-Smith" of "Wed, 09 May 2001 07:48:49 +0200." <20010509074849.1e6a6057.steveo@eircom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 May 2001 10:17:03 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 7 May 2001 10:18:38 -0700 > current@freebsd.org wrote: > > Lets try another realistic example: > > > > cp -uvp ab* cde*.f* g? h/*.i? j/kl /m > > What's the find | cpio invocation for that? When you come up with it, it > > echo ab* cde*.f* g? h/*.i? j/kl /m | cpio ... > > Messy - No, Portable - Yes. BZZZZT - wrong. cp flattens the hierarchy, cpio does not. I think this was a trick question :*P > -- > Optimal hardware acceleration for Windows PC (Mac). > 9.81 m/s/s applied for (at least) 2s followed by impact with solid object. > Optimal software upgrade > FreeBSD (OS-X). -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 2:33:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.originative.co.uk (mailgate.originative.co.uk [62.232.68.68]) by hub.freebsd.org (Postfix) with ESMTP id 0BA5837B422 for ; Wed, 9 May 2001 02:33:33 -0700 (PDT) (envelope-from paul@freebsd-services.co.uk) Received: from lobster.originative.co.uk (lobster [62.232.68.81]) by mailgate.originative.co.uk (Postfix) with ESMTP id 60AAB1D162 for ; Wed, 9 May 2001 10:14:17 +0100 (BST) Date: Wed, 09 May 2001 10:14:39 +0100 From: Paul Richards To: current@freebsd.org Subject: su, PAM and zsh Message-ID: <6990000.989399679@lobster.originative.co.uk> X-Mailer: Mulberry/2.0.8 (Linux/x86 Demo) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There's a strange interaction between su, pam znd zsh. If you su to an account that has zsh as its shell and then hit ctrl-c it will kill the shell that you invoked su from. If you recompile su with -DNOPAM then the problems go away and this doesn't seem to happen with any other shells either. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 6:40:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (cvsup2.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 1B1F037B422; Wed, 9 May 2001 06:40:38 -0700 (PDT) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W-rina.r-20010412) with ESMTP id f49AUYP07219 ; Wed, 9 May 2001 19:30:35 +0900 (JST) Message-Id: <200105091030.f49AUYP07219@rina.r.dl.itc.u-tokyo.ac.jp> Date: Wed, 09 May 2001 19:30:34 +0900 From: Seigo Tanimura To: jhb@FreeBSD.org Cc: tanimura@r.dl.itc.u-tokyo.ac.jp, current@FreeBSD.org Subject: RE: select(2) converted to use a condition variable, and optimis In-Reply-To: In your message of "Wed, 09 May 2001 19:20:07 +0900" <200105091020.f49AK7P05497@rina.r.dl.itc.u-tokyo.ac.jp> References: <200105081026.f48AQgP75260@rina.r.dl.itc.u-tokyo.ac.jp> <200105091020.f49AK7P05497@rina.r.dl.itc.u-tokyo.ac.jp> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 09 May 2001 19:20:07 +0900, Seigo Tanimura said: Seigo> That does not, however, necessarily imply that we can scan file Seigo> descriptors with holding a process lock. Another process can release a Seigo> reference to a file descriptor via closef() during polling the Seigo> descriptor by calling its fo_poll. In this case, fdrop() subsequent to Seigo> the call of fo_poll may result the reference count of the descriptor Seigo> to be zero. Hang on, the process that owns a file descriptor should be fhold()ing the descriptor. Since we never call closef() during waiting for an event, that problem described above is no more than absurd fear. -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 6:40:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (cvsup2.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id AF83137B423; Wed, 9 May 2001 06:40:39 -0700 (PDT) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W-rina.r-20010412) with ESMTP id f49AK7P05497 ; Wed, 9 May 2001 19:20:08 +0900 (JST) Message-Id: <200105091020.f49AK7P05497@rina.r.dl.itc.u-tokyo.ac.jp> Date: Wed, 09 May 2001 19:20:07 +0900 From: Seigo Tanimura To: jhb@FreeBSD.org Cc: tanimura@r.dl.itc.u-tokyo.ac.jp, current@FreeBSD.org Subject: RE: select(2) converted to use a condition variable, and optimis In-Reply-To: In your message of "Tue, 08 May 2001 08:21:55 -0700 (PDT)" References: <200105081026.f48AQgP75260@rina.r.dl.itc.u-tokyo.ac.jp> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 08 May 2001 08:21:55 -0700 (PDT), John Baldwin said: John> On 08-May-01 Seigo Tanimura wrote: >> Here is another issue. PROC_LOCK may block to acquire a process lock, >> during which an event of interest may occur or the remaining time of >> select(2)/poll(2) may run out. Thus if the remaining time runs out >> during locking a process, we should first rescan file descriptors to >> avoid missing an event, followed by returning the result. John> Hmmm. Actually, can the nb_poll, ncp_poll, pollscan, or selscan functions call John> tsleep/msleep? If they don't, then we are just better off holding proc lock John> while we call them rather than releasing it just to call that function and John> acquiring it later. Then we don't have to work around the race you describe. Poling functions called via fo_poll in a file descriptor should not call msleep(9) in theory. That does not, however, necessarily imply that we can scan file descriptors with holding a process lock. Another process can release a reference to a file descriptor via closef() during polling the descriptor by calling its fo_poll. In this case, fdrop() subsequent to the call of fo_poll may result the reference count of the descriptor to be zero. Now the problem is whether it is easy or difficult to free a file descriptor with holding a process lock. At the level of the file descriptor layer, we can convert the memory allocator of a file descriptor from malloc(9) to the zone allocator, which locks only the zone state for file descriptors by a mutex. It is a crucial issue to release an object underlying a file descriptor. Releasing a vnode can result in calling msleep(9) for locking the vnode in vrele(). Releasing a socket may end up with calling tsleep(9) for draining data if SO_LINGER is set. Hence we cannot scan file descriptors with holding a process lock for now. John> Also, in the done_noproclock: case (might want to use 'unlock:' and 'done:' John> instead of 'done:' and 'done_noproclock:' for label names instead) are you John> always sure that when you go to that label you don't need to clear P_SELECT? select(2) and poll(2) set P_SELECT below retry: and clear P_SELECT upon occurrence of an event or timeout. There are no other places than them for a process to set P_SELECT in its p_flag. Thus we can assume at the entry of select(2) and poll(2) that P_SELECT is not set. We go to done_noproclock if and only if either copyin() or sanity check of arguments fails. As we do not poll any descriptors in this case, it is not necessary to clear P_SELECT. -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 9:22:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id CA5BC37B422; Wed, 9 May 2001 09:22:05 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f49GLuG52460; Wed, 9 May 2001 09:21:56 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 09 May 2001 09:21:02 -0700 (PDT) From: John Baldwin To: Robert Watson Subject: Re: pgm to kill 4.3 via vm Cc: tlambert2@mindspring.com Cc: tlambert2@mindspring.com, Dennis Glatting , Kris Kennaway , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.org, Dag-Erling Smorgrav Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-May-01 Robert Watson wrote: > > On Tue, 8 May 2001, John Baldwin wrote: > >> That's easy enough. Well, it used to be at least. You can use 'ps' to >> find the address of the struct proc (first pointer in the display) and >> then do 'call psignal(addr, 9)' to send SIGKILL to the process. Then >> hit 'c' to continue and voila, the process dies. I think that may panic >> now due to proc lock not being held (though the debugger shouldn't need >> any locks in theory.) Perhaps mtx_assert() should honor db_active and >> not panic if it is set. > > I followed everything here fine until you asserted that the debugger > shouldn't need any locks. I guess I don't see why that is, at least in > terms of not corrupting structures. From a practical perspective, the > debugger is like any other interupt-driven preemptive code-path: if you > want to modify a structure, you need to synchronize appropriately to avoid > corrupting the structure. This may not be something you really want to do > in a debugger, so in that sense perhaps you *shouldn't* grab a lock in the > debugger, but to perform the described action safely, you *should* grab a > lock so as not to corrupt fields of the proc structure (i.e., if you broke > into the debugger during a non-atomic flags update). Violating system > invariants is something you should be allowed to do in a debugger, but > this sounded like it was a feature people were looking from to recover > from unhappy behavior, not to introduce it :-). I am more worried about the fact that you can deadlock the debugger. What does the debugger do if another process hold the proc lock on the process you want to kill? Cute, eh? The debugger is an extra special environment. Most of the time you've panic'ed when you are in there (but then the panicstr tests that skip lock operations save you from that). Also, in the debugger you know that no other threads are running. This is why 'show pcpu' can list spin locks on other cpu's safely, for example. I'm not sure if a ddb 'kill' command shouldn't be better implemented using a 'trylock' and refusing to send the signal if it can't get the lock so it can avoid doing really bad things. I suppose it wouldn't deadlock but would switch to the other task and start running. Of course, this would be most disastrous if the current task we just dropped to the debugger in holds a spin lock. :( -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 9:22:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 25E3C37B719 for ; Wed, 9 May 2001 09:22:18 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f49GM3G52468; Wed, 9 May 2001 09:22:04 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105091020.f49AK7P05497@rina.r.dl.itc.u-tokyo.ac.jp> Date: Wed, 09 May 2001 09:21:09 -0700 (PDT) From: John Baldwin To: Seigo Tanimura Subject: RE: select(2) converted to use a condition variable, and optimis Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-May-01 Seigo Tanimura wrote: > On Tue, 08 May 2001 08:21:55 -0700 (PDT), > John Baldwin said: > > John> On 08-May-01 Seigo Tanimura wrote: > >>> Here is another issue. PROC_LOCK may block to acquire a process lock, >>> during which an event of interest may occur or the remaining time of >>> select(2)/poll(2) may run out. Thus if the remaining time runs out >>> during locking a process, we should first rescan file descriptors to >>> avoid missing an event, followed by returning the result. > > John> Hmmm. Actually, can the nb_poll, ncp_poll, pollscan, or selscan > functions call > John> tsleep/msleep? If they don't, then we are just better off holding proc > lock > John> while we call them rather than releasing it just to call that function > and > John> acquiring it later. Then we don't have to work around the race you > describe. > > Poling functions called via fo_poll in a file descriptor should not > call msleep(9) in theory. > > Now the problem is whether it is easy or difficult to free a file > descriptor with holding a process lock. At the level of the file > descriptor layer, we can convert the memory allocator of a file > descriptor from malloc(9) to the zone allocator, which locks only the > zone state for file descriptors by a mutex. Free'ing is not all that problematic since it doesn't sleep. It is more problematic atm because it can result in lock order reversals due to lockmgr headaches. Eventually this won't become an issue I hope. > It is a crucial issue to release an object underlying a file > descriptor. Releasing a vnode can result in calling msleep(9) for > locking the vnode in vrele(). Releasing a socket may end up with > calling tsleep(9) for draining data if SO_LINGER is set. Hence we > cannot scan file descriptors with holding a process lock for now. Argh, ok. Eventually this issue may go away as well. > John> Also, in the done_noproclock: case (might want to use 'unlock:' and > 'done:' > John> instead of 'done:' and 'done_noproclock:' for label names instead) are > you > John> always sure that when you go to that label you don't need to clear > P_SELECT? > > select(2) and poll(2) set P_SELECT below retry: and clear P_SELECT > upon occurrence of an event or timeout. There are no other places than > them for a process to set P_SELECT in its p_flag. Thus we can assume > at the entry of select(2) and poll(2) that P_SELECT is not set. > > We go to done_noproclock if and only if either copyin() or sanity > check of arguments fails. As we do not poll any descriptors in this > case, it is not necessary to clear P_SELECT. Ok, sounds good. Just wanted to make sure. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 9:56:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id 12E5737B61B for ; Wed, 9 May 2001 09:56:06 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout1.freenet.de with esmtp (Exim 3.22 #1) id 14xXFs-0007bb-00 for current@freebsd.org; Wed, 09 May 2001 18:56:04 +0200 Received: from a35d2.pppool.de ([213.6.53.210] helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.22 #1) id 14xXFs-0003GI-00 for current@FreeBSD.ORG; Wed, 09 May 2001 18:56:04 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.3/8.11.3) with ESMTP id f49Emmm00972 for ; Wed, 9 May 2001 16:48:49 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200105091448.f49Emmm00972@Magelan.Leidinger.net> Date: Wed, 9 May 2001 16:48:46 +0200 (CEST) From: Alexander Leidinger Subject: MFS broken in vop_stdbmap (was: trap12: page fault) To: current@FreeBSD.ORG In-Reply-To: <200105031434.f43EYrG00732@Magelan.Leidinger.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3 Mai, An: current@FreeBSD.ORG wrote: > Hi, > > /sys from cvsup around 2pm CEST from cvsup3.de.freebsd.org (contains > npx.c fix). CVSUP from May 7, ~1pm CEST. I made some progress. As you see in my last message I have parts of the kernel loaded as modules. The mfs module was responsible for the page fault (/tmp as mfs, /etc/rc deletes some files in /tmp unconditionally at the point of the breakage). Now I have the FSes, VESA and the random module in the kernel instead of loading it as a module. Backtrace (no coredump, I try to get one at the weekend if the following isn't enough): ---snip--- vop_stdbmap() bdwrite() ffs_update() ufs_inactive() ufs_vnoperate() vrele() vn_close() vn_closefile() fdrop() ... ---snip--- Bye, Alexander. -- Where do you think you're going today? http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 10:47:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D948837B424; Wed, 9 May 2001 10:47:54 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f49Hlnf90676; Wed, 9 May 2001 13:47:49 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 9 May 2001 13:47:49 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: John Baldwin Cc: tlambert2@mindspring.com, Dennis Glatting , Kris Kennaway , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.org, Dag-Erling Smorgrav Subject: Re: pgm to kill 4.3 via vm In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 May 2001, John Baldwin wrote: > I am more worried about the fact that you can deadlock the debugger. > What does the debugger do if another process hold the proc lock on the > process you want to kill? Cute, eh? The debugger is an extra special > environment. Most of the time you've panic'ed when you are in there > (but then the panicstr tests that skip lock operations save you from > that). Also, in the debugger you know that no other threads are > running. This is why 'show pcpu' can list spin locks on other cpu's > safely, for example. I'm not sure if a ddb 'kill' command shouldn't be > better implemented using a 'trylock' and refusing to send the signal if > it can't get the lock so it can avoid doing really bad things. I > suppose it wouldn't deadlock but would switch to the other task and > start running. Of course, this would be most disastrous if the current > task we just dropped to the debugger in holds a spin lock. :( It sounds like what people really want is a kernel supervisor running on a vty, perhaps ttyv8 or something, which is a kernel process and not a user process, and is less prone to failure than a root shell, and hence less likely to get deadlocked on vnodes, etc, etc, which would offer some simple management primitives in the form of "signal process to death", "call boot(0)", etc. This kernel process would obey locking requirements for its operations, but would have no services that could potentially be blocked on a vnode lock, would always be in memory, etc, making highly available. However, it sounds like the trylock solution for ddb is a lot better than ignoring the lock and introducing nastiness that way. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 13:34: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 61D4137B422; Wed, 9 May 2001 13:34:06 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f49KXsB00219; Wed, 9 May 2001 13:33:54 -0700 (PDT) (envelope-from dillon) Date: Wed, 9 May 2001 13:33:54 -0700 (PDT) From: Matt Dillon Message-Id: <200105092033.f49KXsB00219@earth.backplane.com> To: Seigo Tanimura Cc: jhb@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: RE: select(2) converted to use a condition variable, and optimis References: <200105081026.f48AQgP75260@rina.r.dl.itc.u-tokyo.ac.jp> <200105091020.f49AK7P05497@rina.r.dl.itc.u-tokyo.ac.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are several issues here: * The process's descriptor table * The struct file's referenced by that descriptor table * The object underlying a struct file. A process's descriptor table is not protected by the proc lock, because the descriptor table can be shared across processes that rfork(). The struct file underlying a descriptor has a reference count. The descriptor table reference to the underlying struct file is part of this ref count. Any process that fhold()'s a struct file pointer also bumps this ref count. However, holding a ref on the struct file does not prevent another process from revoking the descriptor, so you aren't as safe as you might think. You are safe from it being closed out from under you, but not safe otherwise. Additionally, the act of *getting* a new ref count on a struct file is not currently protected by anything but Giant. For example, look at kern/kern_descrip.c line 226 in -current: if ((unsigned)uap->fd >= fdp->fd_nfiles || (fp = fdp->fd_ofiles[uap->fd]) == NULL) return (EBADF); pop = &fdp->fd_ofileflags[uap->fd]; ... fhold(fp); A race can develope between the point where 'fp' is loaded, and the point where it is held by fhold(). Linux solves this problem by making their fhold() equivalent take a descriptor number rather then a struct file and doing all necessary locking internally. I did a bunch of work on the descriptor code to handle -stable SMP races that were occuring due to a lack of fhold()s around blocking conditions, but I never took the final step of encapsulating the descriptor number lookup in the fhold() (I ran out of time). For -current, you MUST do this if you want to move any descriptor-referencing code out from under Giant. The process lock is not sufficient... the descriptor table needs its own mutex. It is possible to optimize this out by checking to see if the descriptor table is shared, but in general you need it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 14:17:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 0B73737B422; Wed, 9 May 2001 14:17:18 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id RAA74500; Wed, 9 May 2001 17:17:17 -0400 (EDT) (envelope-from wollman) Date: Wed, 9 May 2001 17:17:17 -0400 (EDT) From: Garrett Wollman Message-Id: <200105092117.RAA74500@khavrinen.lcs.mit.edu> To: Robert Watson Cc: freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I followed everything here fine until you asserted that the debugger > shouldn't need any locks. When the debugger is running, everything else should have been forcibly halted. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 16:59:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 52CD037B422; Wed, 9 May 2001 16:59:54 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id B15453E0B; Wed, 9 May 2001 16:59:53 -0700 (PDT) To: John Baldwin Cc: Robert Watson , Kris Kennaway , freebsd-current@FreeBSD.org, Dag-Erling Smorgrav Subject: Re: pgm to kill 4.3 via vm In-Reply-To: ; from jhb@FreeBSD.org on "Wed, 09 May 2001 09:21:02 -0700 (PDT)" Date: Wed, 09 May 2001 16:59:53 -0700 From: Dima Dorfman Message-Id: <20010509235953.B15453E0B@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ -stable dropped from cc list ] John Baldwin writes: > > On 09-May-01 Robert Watson wrote: > > > > On Tue, 8 May 2001, John Baldwin wrote: > > > >> That's easy enough. Well, it used to be at least. You can use 'ps' to > >> find the address of the struct proc (first pointer in the display) and > >> then do 'call psignal(addr, 9)' to send SIGKILL to the process. Then > >> hit 'c' to continue and voila, the process dies. I think that may panic > >> now due to proc lock not being held (though the debugger shouldn't need > >> any locks in theory.) Perhaps mtx_assert() should honor db_active and > >> not panic if it is set. > > > > I followed everything here fine until you asserted that the debugger > > shouldn't need any locks. I guess I don't see why that is, at least in > > terms of not corrupting structures. From a practical perspective, the > > debugger is like any other interupt-driven preemptive code-path: if you > > want to modify a structure, you need to synchronize appropriately to avoid > > corrupting the structure. This may not be something you really want to do > > in a debugger, so in that sense perhaps you *shouldn't* grab a lock in the > > debugger, but to perform the described action safely, you *should* grab a > > lock so as not to corrupt fields of the proc structure (i.e., if you broke > > into the debugger during a non-atomic flags update). Violating system > > invariants is something you should be allowed to do in a debugger, but > > this sounded like it was a feature people were looking from to recover > > from unhappy behavior, not to introduce it :-). > > I am more worried about the fact that you can deadlock the debugger. > What does the debugger do if another process hold the proc lock on > the process you want to kill? Cute, eh? The debugger is an extra > special environment. Most of the time you've panic'ed when you are > in there (but then the panicstr tests that skip lock operations save > you from that). Also, in the debugger you know that no other > threads are running. This is why 'show pcpu' can list spin locks on > other cpu's safely, for example. I'm not sure if a ddb 'kill' > command shouldn't be better implemented using a 'trylock' and > refusing to send the signal if it can't get the lock so it can avoid > doing really bad things. I suppose it wouldn't deadlock but would I think this makes sense. How should this be implemented, though? pfind() locks the process before returning (as you well know). Not using pfind() will work, but that breaks the abstraction. Is that something to worry about? There's also no PROC_TRYLOCK macro, but that's not hard to fix. Thanks, Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 17: 6:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (cvsup2.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id C804737B422; Wed, 9 May 2001 17:06:12 -0700 (PDT) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: (from uucp@localhost) by rina.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W-rina.r-20010412) with UUCP id f4A06A414607 ; Thu, 10 May 2001 09:06:10 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp [fec0::1:280:c8ff:fe6b:6d73]) by sohgo.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W) with ESMTP id f4A05vJ25698 ; Thu, 10 May 2001 09:05:57 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W) with ESMTP id f4A05oj35294 ; Thu, 10 May 2001 09:05:54 +0900 (JST) Message-Id: <200105100005.f4A05oj35294@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Date: Thu, 10 May 2001 09:05:49 +0900 From: Seigo Tanimura To: Matt Dillon Cc: Seigo Tanimura , jhb@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: select(2) converted to use a condition variable, and optimis In-Reply-To: <200105092033.f49KXsB00219@earth.backplane.com> References: <200105081026.f48AQgP75260@rina.r.dl.itc.u-tokyo.ac.jp> <200105091020.f49AK7P05497@rina.r.dl.itc.u-tokyo.ac.jp> <200105092033.f49KXsB00219@earth.backplane.com> User-Agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 May 2001 13:33:54 -0700 (PDT), Matt Dillon said: Matt> * The process's descriptor table Matt> * The struct file's referenced by that descriptor table Those are in my TODO list, and I have already started working on them. -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 17: 7:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (cvsup2.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 364F137B422; Wed, 9 May 2001 17:07:14 -0700 (PDT) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: (from uucp@localhost) by rina.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W-rina.r-20010412) with UUCP id f4A07DE14626 ; Thu, 10 May 2001 09:07:13 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp [fec0::1:280:c8ff:fe6b:6d73]) by sohgo.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W) with ESMTP id f4A06LJ25747 ; Thu, 10 May 2001 09:06:21 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W) with ESMTP id f4A06Gj35470 ; Thu, 10 May 2001 09:06:18 +0900 (JST) Message-Id: <200105100006.f4A06Gj35470@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Date: Thu, 10 May 2001 09:06:15 +0900 From: Seigo Tanimura To: John Baldwin Cc: Seigo Tanimura , current@FreeBSD.org Subject: Re: select(2) converted to use a condition variable, and optimis In-Reply-To: References: <200105091020.f49AK7P05497@rina.r.dl.itc.u-tokyo.ac.jp> User-Agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 09 May 2001 09:21:09 -0700 (PDT), John Baldwin said: >> Now the problem is whether it is easy or difficult to free a file >> descriptor with holding a process lock. At the level of the file >> descriptor layer, we can convert the memory allocator of a file >> descriptor from malloc(9) to the zone allocator, which locks only the >> zone state for file descriptors by a mutex. John> Free'ing is not all that problematic since it doesn't sleep. It is more John> problematic atm because it can result in lock order reversals due to lockmgr John> headaches. Eventually this won't become an issue I hope. >> It is a crucial issue to release an object underlying a file >> descriptor. Releasing a vnode can result in calling msleep(9) for >> locking the vnode in vrele(). Releasing a socket may end up with >> calling tsleep(9) for draining data if SO_LINGER is set. Hence we >> cannot scan file descriptors with holding a process lock for now. John> Argh, ok. Eventually this issue may go away as well. A quick and hopefully efficient solution to those problems is to fhold() struct file's first, then enter polling loop. That seems much cheaper than to work on free()ing a vnode or a socket with holding a process lock, provided that struct filedesc and file are protected properly (and we have to do it anyway). -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 17:20:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from mtiwmhc28.worldnet.att.net (mtiwmhc28.worldnet.att.net [204.127.131.36]) by hub.freebsd.org (Postfix) with ESMTP id 254C637B422 for ; Wed, 9 May 2001 17:20:10 -0700 (PDT) (envelope-from wsheets@att.net) Received: from att.net ([12.72.47.194]) by mtiwmhc28.worldnet.att.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010510002008.RWAJ6429.mtiwmhc28.worldnet.att.net@att.net> for ; Thu, 10 May 2001 00:20:08 +0000 To: freebsd-current@freebsd.org Subject: Buildworld/kernel worked great today. From: walt Date: 09 May 2001 17:17:24 -0700 Message-ID: <87y9s6njl7.fsf@att.net> Lines: 13 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsup'd 5-9-2001 around 0600 PST You must be tired of hearing about things that are broken, so I thought I'd let you know things went well. Running i686 (single), ide/dma66 x two disks, no isa cards, no scsi, two ethernet cards, softupdates, devfs. A very basic box. And ssh 2.9 seems OK as well. I can ssh to my OpenBSD machine and to this machine (localhost) without difficulty. Everything went without a hitch--congratulations, team! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 21: 1:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id A5B9937B423 for ; Wed, 9 May 2001 21:01:51 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id OAA17577 for ; Thu, 10 May 2001 14:01:49 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01K3EGJEMWI8RX7DRW@cim.alcatel.com.au> for current@freebsd.org; Thu, 10 May 2001 14:01:34 +1000 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f4A41hr28113 for current@freebsd.org; Thu, 10 May 2001 14:01:43 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Thu, 10 May 2001 14:01:43 +1000 From: Peter Jeremy Subject: **HEADS-UP** ficl changes change `base' type To: current@freebsd.org Mail-Followup-To: current@freebsd.org Message-id: <20010510140142.D26407@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For anyone who writes their own FORTH in the loader scripts: ficl 2.05 (imported on 28th April by dcs) changes `base' from an lvalue to an rvalue. This will break any code that currently uses base. In particular, code to temporarily change the base will corrupt low memory. For example: base @ <> hex . base ! will now access a word at address 10 and store it at address 16. I have no idea why this change was made - it breaks FORTH compatibility. I can't find anything in ficl.sourceforge.net (except that someone has helpfully stripped all the CR's off ficl205.tar before it was gzip'd - which upsets tar quite a bit). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 21:44: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from newsguy.com (perry.pathlink.com [209.155.233.33]) by hub.freebsd.org (Postfix) with ESMTP id 50E9237B423 for ; Wed, 9 May 2001 21:43:57 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (ppp113-bsace7001.telebrasilia.net.br [200.181.80.113]) by newsguy.com (8.11.0/8.9.1) with ESMTP id f4A4hlD92017; Wed, 9 May 2001 21:43:48 -0700 (PDT) Message-ID: <3AFA1C9F.2CB1630A@newsguy.com> Date: Thu, 10 May 2001 01:44:15 -0300 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en,pt-BR,pt,en-GB,en-US,ja MIME-Version: 1.0 To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: **HEADS-UP** ficl changes change `base' type References: <20010510140142.D26407@gsmx07.alcatel.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > > For anyone who writes their own FORTH in the loader scripts: > > ficl 2.05 (imported on 28th April by dcs) changes `base' from an > lvalue to an rvalue. This will break any code that currently > uses base. In particular, code to temporarily change the base > will corrupt low memory. For example: > base @ <> hex . base ! > will now access a word at address 10 and store it at address 16. > > I have no idea why this change was made - it breaks FORTH compatibility. > I can't find anything in ficl.sourceforge.net (except that someone has > helpfully stripped all the CR's off ficl205.tar before it was gzip'd - > which upsets tar quite a bit). Ugh! I wasn't aware of this, and I can guarantee this will be fixed. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net Caffeine is proof that God hates mornings too To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 22: 3: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from newsguy.com (perry.pathlink.com [209.155.233.33]) by hub.freebsd.org (Postfix) with ESMTP id C71BD37B424 for ; Wed, 9 May 2001 22:03:01 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (ppp113-bsace7001.telebrasilia.net.br [200.181.80.113]) by newsguy.com (8.11.0/8.9.1) with ESMTP id f4A52YD94526; Wed, 9 May 2001 22:02:35 -0700 (PDT) Message-ID: <3AFA2107.98303274@newsguy.com> Date: Thu, 10 May 2001 02:03:03 -0300 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en,pt-BR,pt,en-GB,en-US,ja MIME-Version: 1.0 To: Salvo Bartolotta Cc: Erick Kinnee , freebsd-current@freebsd.org Subject: Re: Experiences with new dir allocation on FFS? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Salvo Bartolotta wrote: > > [ resending, with a subject ] > > > OK, I;ve looked and looked and can't seem to figure out how to set > hw.ata.wc to enabled. I've put and a few other things in > /etc/sysctl.conf, the others get set, hw.ata.wc doesn't. You can't > change it by hand either as sysctl tells you it's readonly. Grepping in > /sys/i386/conf has turned up nothing and neither has grepping /boot. > > > Have you tried specifying it in /boot/loader.conf ? > hw.ata.wc="1" That's probably what he meant by grepping /boot. Unfortunately, loader-tunables are hardly ever added to /boot/defaults/loader.conf or loader(8). He should have checked ata(4) instead. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net Caffeine is proof that God hates mornings too To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 9 22:20:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from newsguy.com (perry.pathlink.com [209.155.233.33]) by hub.freebsd.org (Postfix) with ESMTP id 54F3537B423 for ; Wed, 9 May 2001 22:20:48 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (ppp113-bsace7001.telebrasilia.net.br [200.181.80.113]) by newsguy.com (8.11.0/8.9.1) with ESMTP id f4A5KdD97021; Wed, 9 May 2001 22:20:39 -0700 (PDT) Message-ID: <3AFA2545.BB8870D9@newsguy.com> Date: Thu, 10 May 2001 02:21:09 -0300 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en,pt-BR,pt,en-GB,en-US,ja MIME-Version: 1.0 To: Peter Jeremy , current@FreeBSD.ORG Subject: Re: **HEADS-UP** ficl changes change `base' type References: <20010510140142.D26407@gsmx07.alcatel.com.au> <3AFA1C9F.2CB1630A@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > > I have no idea why this change was made - it breaks FORTH compatibility. > > I can't find anything in ficl.sourceforge.net (except that someone has > > helpfully stripped all the CR's off ficl205.tar before it was gzip'd - > > which upsets tar quite a bit). John Sadler is not a Unix user, and has no experience with Unix, and doesn't have one, as a matter of fact. All that's there on sourceforge was produced using tools under Windows, and he is making an effort to make things available for us poor Unix users, but he can't test them, and he doesn't even know exactly what we want. If you know exactly how to produce a .tar.gz under Windows that is suitable for our use, I'm sure he would appreciate the help. > Ugh! I wasn't aware of this, and I can guarantee this will be fixed. Done. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net Caffeine is proof that God hates mornings too To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 2:21:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by hub.freebsd.org (Postfix) with SMTP id 33C4237B423 for ; Thu, 10 May 2001 02:21:45 -0700 (PDT) (envelope-from ms@laptop.6bone.nl) Received: (qmail 9770 invoked by uid 0); 10 May 2001 09:21:42 -0000 Received: from kantoor.ripe.net (HELO laptop.6bone.nl) (193.0.1.98) by postman.ripe.net with SMTP; 10 May 2001 09:21:42 -0000 Received: (nullmailer pid 2281 invoked by uid 1000); Thu, 10 May 2001 09:21:40 -0000 Date: Thu, 10 May 2001 11:21:40 +0200 From: Mark Santcroos To: David O'Brien Cc: freebsd-current@freebsd.org Subject: Re: WinModem Support Message-ID: <20010510112139.A2151@laptop.6bone.nl> References: <15085.61825.708944.271219@ultrahot.Finland.Sun.COM> <20010507143720.A38755@laptop.6bone.nl> <20010510015125.A73744@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010510015125.A73744@hub.freebsd.org>; from obrien@FreeBSD.ORG on Thu, May 10, 2001 at 01:51:25AM -0700 X-Handles: MS6-6BONE, MS32260-NIC, MS18417-RIPE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 10, 2001 at 01:51:25AM -0700, David O'Brien wrote: > On Mon, May 07, 2001 at 02:37:20PM +0200, Mark Santcroos wrote: > > > Please check http://www.geocities.com/wtnbkysh/ . It should work > > > under 4.2R. There is also some 5.0C patches but still some problems > > > probably with interrupts. > > > > Any idea who is the author of this? > > > > I also tried it on -current and it needs some refinement probably. > > I am willing to do that but it would be nice if the author could give me > > some hints. > > Have you gotten anywhere with this? Yes! I have contacted the author and he made a last change in the interrupt setup. I have made a small stand alone package for -CURRENT, it holds the .c, the linux object file, a Makefile and a script to create the necessary device files. (If you want it in your kernel you can figure out yourself probably, this is just a proof of concept) http://www.ripe.net/home/mark/files/ltmdm_current_may_10.tgz It works great for me, let me know if it is not generic enough and I will apply the changes. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 6:28:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from sol.serv.u-szeged.hu (sol.serv.u-szeged.hu [160.114.51.3]) by hub.freebsd.org (Postfix) with ESMTP id 4911D37B422 for ; Thu, 10 May 2001 06:28:50 -0700 (PDT) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.serv.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id PAA29028; Thu, 10 May 2001 15:28:48 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 14xqUp-0000Zf-00 for ; Thu, 10 May 2001 15:28:47 +0200 Date: Thu, 10 May 2001 15:28:47 +0200 From: Szilveszter Adam To: freebsd-current@freebsd.org Subject: Today's special: nessusd panics -CURRENT Message-ID: <20010510152847.A1492@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everybody, I have stumbled across some nice giraffe today. Look, this is cute (transcribed by hand for your enhanced viewing pleasure): (sorry, no serial console handy... should be easy to reproduce though) # nessusd -D witness_get: witness exhausted exclusive(sleep mutex) Giant(0xc044a760) locked @ ../../i386/i386/trap.c:1169 panic: system call open returning with mutex(s) held Debugger("panic") Stoppped at Debugger+0x45: pushl: %ebx db> trace Debugger panic syscall syscall_with_err_pushed db> OK, so let's see what's next. db> c syncing disks... 17 17 panic: witness_restore: lock(sleep mutex) Giant not locked Debugger("panic") Stopped at Debugger+0x45: pushl: %ebx db> Hmmm... this is not right. What now? db> trace Debugger panic witness_restore msleep buf_daemon fork_exit fork_trampoline db> Well if that doesn't work, let's at least try to dump: db> c dumping to dev #ad/0x20001, offset 352256 dump ata0: resetting devices... panic: witness_save: lock(sleep mutex) Giant not locked Debugger("panic") Stopped at Debugger+0x45: pushl: %ebx db> No, bad Szilveszter, no crash dumps for you today. Well OK, let's see: db> trace Debugger panic witness_save mawait ata_command ad_reinit ata_reinit addump dumpsys boot panic witness_restore msleep buf_daemon fork_exit fork_trampoline db> c Dump already in progress, bailing... Automatic reboot in 15 sec etc. (And of course no dump) So? Opinions? things to try? -CURRENT is from yesterday, kernel and world in sync, machine UP PII-233. Nessus is from ports and has been extra recompiled after the make world. I will try anything if needed or test any patches... Thank you for your time... -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 8:39:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from johnson.mail.mindspring.net (johnson.mail.mindspring.net [207.69.200.177]) by hub.freebsd.org (Postfix) with ESMTP id 9523437B422; Thu, 10 May 2001 08:39:39 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0519.cvx7-bradley.dialup.earthlink.net [209.178.166.9]) by johnson.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id LAA21010; Thu, 10 May 2001 11:39:32 -0400 (EDT) Message-ID: <3AFAB649.67D53F11@mindspring.com> Date: Thu, 10 May 2001 08:39:53 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Seigo Tanimura Cc: John Baldwin , current@FreeBSD.ORG Subject: Re: select(2) converted to use a condition variable, and optimis References: <200105091020.f49AK7P05497@rina.r.dl.itc.u-tokyo.ac.jp> <200105100006.f4A06Gj35470@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seigo Tanimura wrote: > A quick and hopefully efficient solution to those problems is to > fhold() struct file's first, then enter polling loop. That seems much > cheaper than to work on free()ing a vnode or a socket with holding a > process lock, provided that struct filedesc and file are protected > properly (and we have to do it anyway). Let me once again point out that fhold(), like crhold(), should act as an l-valued function that takes an r-value as an "argument", as in: a = crhold(b); q = fhold(r); etc. (for all such functions). The reason is that you can not replace it with an instrumented function, otherwise, which would permit you to catch subtle errors that: a = b; crhold(a); q = r; fhold(r); etc. may cause (yes, I know I have held the r-calue in one case and the l-value in the other in the above example; the kernel itself does this all over the place, and I think it's an error). I also think that they should use common base macros: it is exceedingly dangerous to have multiple hold semantics in the kernel. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 8:53:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 1F6C637B423 for ; Thu, 10 May 2001 08:53:24 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f4AFrJG84551; Thu, 10 May 2001 08:53:20 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3AFAB649.67D53F11@mindspring.com> Date: Thu, 10 May 2001 08:52:24 -0700 (PDT) From: John Baldwin To: Terry Lambert Subject: Re: select(2) converted to use a condition variable, and optimis Cc: current@FreeBSD.org, Seigo Tanimura Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-May-01 Terry Lambert wrote: > Seigo Tanimura wrote: >> A quick and hopefully efficient solution to those problems is to >> fhold() struct file's first, then enter polling loop. That seems much >> cheaper than to work on free()ing a vnode or a socket with holding a >> process lock, provided that struct filedesc and file are protected >> properly (and we have to do it anyway). > > Let me once again point out that fhold(), like crhold(), > should act as an l-valued function that takes an r-value > as an "argument", as in: > > a = crhold(b); > q = fhold(r); > etc. (for all such functions). > > [ snip ] I agree with all this, I just haven't had the time to sit down and do it. > -- Terry -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 8:54:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 7C74D37B422; Thu, 10 May 2001 08:54:10 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f4AFrFG84547; Thu, 10 May 2001 08:53:18 -0700 (PDT) (envelope-from john@baldwin.cx) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010509235953.B15453E0B@bazooka.unixfreak.org> Date: Thu, 10 May 2001 08:52:20 -0700 (PDT) From: John Baldwin To: Dima Dorfman Subject: Re: pgm to kill 4.3 via vm Cc: Dag-Erling Smorgrav , freebsd-current@FreeBSD.org, Kris Kennaway , Robert Watson , John Baldwin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-May-01 Dima Dorfman wrote: > [ -stable dropped from cc list ] > > John Baldwin writes: >> >> On 09-May-01 Robert Watson wrote: >> > >> > On Tue, 8 May 2001, John Baldwin wrote: >> > >> >> That's easy enough. Well, it used to be at least. You can use 'ps' to >> >> find the address of the struct proc (first pointer in the display) and >> >> then do 'call psignal(addr, 9)' to send SIGKILL to the process. Then >> >> hit 'c' to continue and voila, the process dies. I think that may panic >> >> now due to proc lock not being held (though the debugger shouldn't need >> >> any locks in theory.) Perhaps mtx_assert() should honor db_active and >> >> not panic if it is set. >> > >> > I followed everything here fine until you asserted that the debugger >> > shouldn't need any locks. I guess I don't see why that is, at least in >> > terms of not corrupting structures. From a practical perspective, the >> > debugger is like any other interupt-driven preemptive code-path: if you >> > want to modify a structure, you need to synchronize appropriately to avoid >> > corrupting the structure. This may not be something you really want to do >> > in a debugger, so in that sense perhaps you *shouldn't* grab a lock in the >> > debugger, but to perform the described action safely, you *should* grab a >> > lock so as not to corrupt fields of the proc structure (i.e., if you broke >> > into the debugger during a non-atomic flags update). Violating system >> > invariants is something you should be allowed to do in a debugger, but >> > this sounded like it was a feature people were looking from to recover >> > from unhappy behavior, not to introduce it :-). >> >> I am more worried about the fact that you can deadlock the debugger. >> What does the debugger do if another process hold the proc lock on >> the process you want to kill? Cute, eh? The debugger is an extra >> special environment. Most of the time you've panic'ed when you are >> in there (but then the panicstr tests that skip lock operations save >> you from that). Also, in the debugger you know that no other >> threads are running. This is why 'show pcpu' can list spin locks on >> other cpu's safely, for example. I'm not sure if a ddb 'kill' >> command shouldn't be better implemented using a 'trylock' and >> refusing to send the signal if it can't get the lock so it can avoid >> doing really bad things. I suppose it wouldn't deadlock but would > > I think this makes sense. How should this be implemented, though? > pfind() locks the process before returning (as you well know). Not > using pfind() will work, but that breaks the abstraction. Is that > something to worry about? There's also no PROC_TRYLOCK macro, but > that's not hard to fix. For the per-process tracing I didn't use pfind but just walked the allproc list myself. Using that in combo with a trylock might be your best bet. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 9: 2:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3A39F37B422; Thu, 10 May 2001 09:02:31 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f4AG2RG85015; Thu, 10 May 2001 09:02:27 -0700 (PDT) (envelope-from john@baldwin.cx) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 10 May 2001 09:01:32 -0700 (PDT) From: John Baldwin To: current@FreeBSD.org Subject: FW: Snapshot Log - world broken in telnetd Cc: bde@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like the recent changes wrt to libpam in telnetd may have broken world. -----FW: <200105101611.f4AGBvE13502@deimos.osd.bsdi.com>----- Date: Thu, 10 May 2001 09:11:57 -0700 (PDT) From: Deimos Root To: jhb@osd.bsdi.com, rootmail@osd.bsdi.com Subject: Snapshot Log ===> libexec/telnetd cc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -DAUTHENTICATION -DENCRYPTION -I/usr/src/kerberos IV/libexec/telnetd/../../../crypto/telnet -DINET6 -I/usr/src/kerberosIV/libexec/telnetd/../../include -Wall -DHAVE_CONFIG_H -I /usr/obj/usr/src/kerberosIV/libexec/telnetd/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DLIBEXECDIR=\"/usr/l ibexec\" -c /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/global.c cc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -DAUTHENTICATION -DENCRYPTION -I/usr/src/kerberos IV/libexec/telnetd/../../../crypto/telnet -DINET6 -I/usr/src/kerberosIV/libexec/telnetd/../../include -Wall -DHAVE_CONFIG_H -I /usr/obj/usr/src/kerberosIV/libexec/telnetd/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DLIBEXECDIR=\"/usr/l ibexec\" -c /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/slc.c cc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -DAUTHENTICATION -DENCRYPTION -I/usr/src/kerberos IV/libexec/telnetd/../../../crypto/telnet -DINET6 -I/usr/src/kerberosIV/libexec/telnetd/../../include -Wall -DHAVE_CONFIG_H -I /usr/obj/usr/src/kerberosIV/libexec/telnetd/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DLIBEXECDIR=\"/usr/l ibexec\" -c /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/state.c In file included from /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/state.c:44: /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/libtelnet/auth.h:86: warning: type defaults to `int' in declaration of `auth_debug_mode' cc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -DAUTHENTICATION -DENCRYPTION -I/usr/src/kerberos IV/libexec/telnetd/../../../crypto/telnet -DINET6 -I/usr/src/kerberosIV/libexec/telnetd/../../include -Wall -DHAVE_CONFIG_H -I /usr/obj/usr/src/kerberosIV/libexec/telnetd/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DLIBEXECDIR=\"/usr/l ibexec\" -c /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/sys_term.c In file included from /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/sys_term.c:46 : /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/libtelnet/auth.h:86: warning: type defaults to `int' in declaration of `auth_debug_mode' /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/sys_term.c: In function `start_login': /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/sys_term.c:15 69: warning: unused variable `user' cc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -DAUTHENTICATION -DENCRYPTION -I/usr/src/kerberos IV/libexec/telnetd/../../../crypto/telnet -DINET6 -I/usr/src/kerberosIV/libexec/telnetd/../../include -Wall -DHAVE_CONFIG_H -I /usr/obj/usr/src/kerberosIV/libexec/telnetd/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DLIBEXECDIR=\"/usr/l ibexec\" -c /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/telnetd.c In file included from /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/telnetd.c:91: /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/libtelnet/auth.h:86: warning: type defaults to `int' in declaration of `auth_debug_mode' /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/telnetd.c: In function `telnet': /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/telnetd.c:115 3: warning: implicit declaration of function `g etent' cc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -DAUTHENTICATION -DENCRYPTION -I/usr/src/kerberos IV/libexec/telnetd/../../../crypto/telnet -DINET6 -I/usr/src/kerberosIV/libexec/telnetd/../../include -Wall -DHAVE_CONFIG_H -I /usr/obj/usr/src/kerberosIV/libexec/telnetd/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DLIBEXECDIR=\"/usr/l ibexec\" -c /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/termstat.c cc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -DAUTHENTICATION -DENCRYPTION -I/usr/src/kerberos IV/libexec/telnetd/../../../crypto/telnet -DINET6 -I/usr/src/kerberosIV/libexec/telnetd/../../include -Wall -DHAVE_CONFIG_H -I /usr/obj/usr/src/kerberosIV/libexec/telnetd/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DLIBEXECDIR=\"/usr/l ibexec\" -c /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/utility.c In file included from /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/utility.c:50: /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/libtelnet/auth.h:86: warning: type defaults to `int' in declaration of `auth_debug_mode' cc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -DAUTHENTICATION -DENCRYPTION -I/usr/src/kerberos IV/libexec/telnetd/../../../crypto/telnet -DINET6 -I/usr/src/kerberosIV/libexec/telnetd/../../include -Wall -DHAVE_CONFIG_H -I /usr/obj/usr/src/kerberosIV/libexec/telnetd/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DLIBEXECDIR=\"/usr/l ibexec\" -c /usr/src/kerberosIV/libexec/telnetd/../../../crypto/telnet/telnetd/authenc.c cc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -DAUTHENTICATION -DENCRYPTION -I/usr/src/kerberos IV/libexec/telnetd/../../../crypto/telnet -DINET6 -I/usr/src/kerberosIV/libexec/telnetd/../../include -Wall -DHAVE_CONFIG_H -I /usr/obj/usr/src/kerberosIV/libexec/telnetd/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DLIBEXECDIR=\"/usr/l ibexec\" -o telnetd global.o slc.o state.o sys_term.o telnetd.o termstat.o utility.o authenc.o -lutil -ltermcap /usr/obj/us r/src/kerberosIV/libexec/telnetd/../../lib/libtelnet/libtelnet.a -lcrypto -L/usr/obj/usr/src/kerberosIV/libexec/telnetd/../../ lib/libkrb -lkrb -lcrypt -lcom_err -lmp /usr/obj/usr/src/kerberosIV/libexec/telnetd/../../lib/libtelnet/libtelnet.a(sra. o): In function `check_user': sra.o(.text+0xb8f): undefined reference to `pam_start' sra.o(.text+0xba7): undefined reference to `pam_strerror' sra.o(.text+0xbc9): undefined reference to `pam_authenticate' sra.o(.text+0xbf9): undefined reference to `pam_get_item' sra.o(.text+0xc27): undefined reference to `pam_strerror' sra.o(.text+0xc53): undefined reference to `pam_strerror' sra.o(.text+0xc71): undefined reference to `pam_end' sra.o(.text+0xc89): undefined reference to `pam_strerror' *** Error code 1 Stop in /usr/src/kerberosIV/libexec/telnetd. *** Error code 1 Stop in /usr/src/kerberosIV/libexec. *** Error code 1 Stop in /usr/src/kerberosIV. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. ---------------------------------------- release started at 06:00:01 on 05/10/01 release died at 09:10:25 on 05/10/01 ---------------------------------------- --------------End of forwarded message------------------------- -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 9:40:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 1FEC837B423 for ; Thu, 10 May 2001 09:40:52 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f4AGegf06384; Thu, 10 May 2001 12:40:43 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 10 May 2001 12:40:42 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Garrett Wollman Cc: freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm In-Reply-To: <200105092117.RAA74500@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 May 2001, Garrett Wollman wrote: > < said: > > > I followed everything here fine until you asserted that the debugger > > shouldn't need any locks. > > When the debugger is running, everything else should have been > forcibly halted. The process and signal-related structures may be inconsistent if the debugger disregards existing locks held over those structures. It does not matter if code is currently still executing, it matters that preemption can occur. The choices appear to be: 1) Disregard locks and risk corruption 2) Fail if a lock is held Note that in either case (1) or case (2), the debugger may need special code paths to implement services such as psignal() to indicate that locking is either not needed, or that it should fail rather than block/spin/... Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 9:53:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 9FA5A37B422 for ; Thu, 10 May 2001 09:53:29 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f4AGqvG86283; Thu, 10 May 2001 09:52:57 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010510152847.A1492@petra.hos.u-szeged.hu> Date: Thu, 10 May 2001 09:52:03 -0700 (PDT) From: John Baldwin To: Szilveszter Adam Subject: RE: Today's special: nessusd panics -CURRENT Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-May-01 Szilveszter Adam wrote: > Hello everybody, > > I have stumbled across some nice giraffe today. > > Look, this is cute (transcribed by hand for your enhanced viewing pleasure): > (sorry, no serial console handy... should be easy to reproduce though) > ># nessusd -D > > witness_get: witness exhausted > exclusive(sleep mutex) Giant(0xc044a760) locked @ ../../i386/i386/trap.c:1169 > panic: system call open returning with mutex(s) held Ok, I see what's broken. I don't know how you are out of witness's though. We don't have enough types of mutexes for that to happen. Try this patch: Index: subr_witness.c =================================================================== RCS file: /usr/cvs/src/sys/kern/subr_witness.c,v retrieving revision 1.70 diff -u -r1.70 subr_witness.c --- subr_witness.c 2001/05/04 17:15:16 1.70 +++ subr_witness.c 2001/05/10 16:39:27 @@ -1222,6 +1222,9 @@ ("%s: p != curproc and we aren't in the debugger", __func__)); KASSERT(!witness_cold, ("%s: witness_cold", __func__)); + if (!db_active && witness_dead) + return (0); + nheld = witness_list_locks(&p->p_sleeplocks); /* -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 9:53:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id CE86737B424; Thu, 10 May 2001 09:53:33 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f4AGqwG86287; Thu, 10 May 2001 09:52:58 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 10 May 2001 09:52:04 -0700 (PDT) From: John Baldwin To: John Baldwin Subject: RE: FW: Snapshot Log - world broken in telnetd Cc: bde@FreeBSD.org, current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-May-01 John Baldwin wrote: > It looks like the recent changes wrt to libpam in telnetd may have broken > world. Correction, world appears to be ok, just release is broken. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 10: 6:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 805FF37B422; Thu, 10 May 2001 10:06:27 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f4AH6NG86631; Thu, 10 May 2001 10:06:23 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 10 May 2001 10:05:29 -0700 (PDT) From: John Baldwin To: Robert Watson Subject: Re: pgm to kill 4.3 via vm Cc: freebsd-current@FreeBSD.org, Garrett Wollman Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-May-01 Robert Watson wrote: > > On Wed, 9 May 2001, Garrett Wollman wrote: > >> <> said: >> >> > I followed everything here fine until you asserted that the debugger >> > shouldn't need any locks. >> >> When the debugger is running, everything else should have been >> forcibly halted. > > The process and signal-related structures may be inconsistent if the > debugger disregards existing locks held over those structures. It does > not matter if code is currently still executing, it matters that > preemption can occur. The choices appear to be: > > 1) Disregard locks and risk corruption If I'm sending a kill -9 to a program, I could really care less about clobbering the SIGABRT it is currently getting sent. :) I think that a kernel debugger is a case of where one allows much foot shooting to occur. > 2) Fail if a lock is held mtx_trylock() makes this relatively easy to implement in many cases. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 10:18:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id DF8AA37B424; Thu, 10 May 2001 10:18:32 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id DAA21965; Fri, 11 May 2001 03:18:07 +1000 Date: Fri, 11 May 2001 03:16:35 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: current@FreeBSD.org, bde@FreeBSD.org, Deimos Root , jhb@osd.bsdi.com Subject: Re: FW: Snapshot Log - world broken in telnetd In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 10 May 2001, John Baldwin wrote: > It looks like the recent changes wrt to libpam in telnetd may have broken world. > ... > cc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK > -DAUTHENTICATION -DENCRYPTION -I/usr/src/kerberos > IV/libexec/telnetd/../../../crypto/telnet -DINET6 > -I/usr/src/kerberosIV/libexec/telnetd/../../include -Wall -DHAVE_CONFIG_H -I > /usr/obj/usr/src/kerberosIV/libexec/telnetd/../../include > -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DLIBEXECDIR=\"/usr/l > ibexec\" -o telnetd global.o slc.o state.o sys_term.o telnetd.o termstat.o > utility.o authenc.o -lutil -ltermcap /usr/obj/us > r/src/kerberosIV/libexec/telnetd/../../lib/libtelnet/libtelnet.a -lcrypto > -L/usr/obj/usr/src/kerberosIV/libexec/telnetd/../../ > lib/libkrb -lkrb -lcrypt -lcom_err -lmp > /usr/obj/usr/src/kerberosIV/libexec/telnetd/../../lib/libtelnet/libtelnet.a(sra. > o): In function `check_user': > sra.o(.text+0xb8f): undefined reference to `pam_start' > sra.o(.text+0xba7): undefined reference to `pam_strerror' > sra.o(.text+0xbc9): undefined reference to `pam_authenticate' > sra.o(.text+0xbf9): undefined reference to `pam_get_item' > sra.o(.text+0xc27): undefined reference to `pam_strerror' > sra.o(.text+0xc53): undefined reference to `pam_strerror' > sra.o(.text+0xc71): undefined reference to `pam_end' > sra.o(.text+0xc89): undefined reference to `pam_strerror' > *** Error code 1 The kerberosIV telnetd is missing linkage to libpam, perhaps more. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 10:18:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 186EB37B42C; Thu, 10 May 2001 10:18:33 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f4AHIS781698; Thu, 10 May 2001 20:18:28 +0300 (EEST) (envelope-from ru) Date: Thu, 10 May 2001 20:18:28 +0300 From: Ruslan Ermilov To: Poul-Henning Kamp Cc: current@FreeBSD.org Subject: DEVFS Message-ID: <20010510201828.A81476@sunbay.com> Mail-Followup-To: Poul-Henning Kamp , current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Just installed recent -CURRENT on my PC, and noticed strange things: 1) If I don't have devfs line in /etc/fstab, why DEVFS mount is still happening on /dev, and where? 2) Is it valid that multiple DEVFS mounts over /dev are allowed? perl# mount -t devfs devfs on /dev (devfs, local) perl# mount /dev perl# mount -t devfs devfs on /dev (devfs, local) devfs on /dev (devfs, local) perl# mount /dev perl# mount -t devfs devfs on /dev (devfs, local) devfs on /dev (devfs, local) devfs on /dev (devfs, local) perl# Thanks, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 10:18:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id BE29637B424 for ; Thu, 10 May 2001 10:18:53 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f4AHIWk04158; Thu, 10 May 2001 10:18:32 -0700 (PDT) (envelope-from obrien) Date: Thu, 10 May 2001 10:18:32 -0700 From: "David O'Brien" To: "Daniel C. Sobral" Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: **HEADS-UP** ficl changes change `base' type Message-ID: <20010510101832.B3561@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010510140142.D26407@gsmx07.alcatel.com.au> <3AFA1C9F.2CB1630A@newsguy.com> <3AFA2545.BB8870D9@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AFA2545.BB8870D9@newsguy.com>; from dcs@newsguy.com on Thu, May 10, 2001 at 02:21:09AM -0300 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 10, 2001 at 02:21:09AM -0300, Daniel C. Sobral wrote: > John Sadler is not a Unix user, and has no experience with Unix, and ... > If you know exactly how to produce a .tar.gz under Windows that is > suitable for our use, I'm sure he would appreciate the help. Ask him to use infozip/pkzip -- I know that is easy for Winloose users. Our unzip has a command line option to fix the text line termination. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 10:31:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 7BDE637B422; Thu, 10 May 2001 10:31:11 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f4AHV7G87271; Thu, 10 May 2001 10:31:07 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010510201828.A81476@sunbay.com> Date: Thu, 10 May 2001 10:30:13 -0700 (PDT) From: John Baldwin To: Ruslan Ermilov Subject: RE: DEVFS Cc: current@FreeBSD.org, Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-May-01 Ruslan Ermilov wrote: > Hi! > > Just installed recent -CURRENT on my PC, and noticed strange things: > > 1) If I don't have devfs line in /etc/fstab, why DEVFS mount is still > happening on /dev, and where? devfs is mounted by /sbin/init IIRC. > 2) Is it valid that multiple DEVFS mounts over /dev are allowed? Why wouldn't it be? (Granted, it is a bit _weird_). You can do the same with other fs's: > mount -t procfs procfs on /proc (procfs, local) > sudo mount /proc > mount -t procfs procfs on /proc (procfs, local) procfs on /proc (procfs, local) > sudo umount /proc -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 10:35:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6F01537B422; Thu, 10 May 2001 10:35:16 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA32174; Thu, 10 May 2001 10:35:17 -0700 Date: Thu, 10 May 2001 10:35:15 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Ruslan Ermilov Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: DEVFS In-Reply-To: <20010510201828.A81476@sunbay.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 10 May 2001, Ruslan Ermilov wrote: > Hi! > > Just installed recent -CURRENT on my PC, and noticed strange things: > > 1) If I don't have devfs line in /etc/fstab, why DEVFS mount is still > happening on /dev, and where? Somewhat wierdly and unobviously, it's init that does the magic. > > 2) Is it valid that multiple DEVFS mounts over /dev are allowed? > > perl# mount -t devfs > devfs on /dev (devfs, local) > perl# mount /dev > perl# mount -t devfs > devfs on /dev (devfs, local) > devfs on /dev (devfs, local) > perl# mount /dev > perl# mount -t devfs > devfs on /dev (devfs, local) > devfs on /dev (devfs, local) > devfs on /dev (devfs, local) > perl# > > > Thanks, > -- > Ruslan Ermilov Oracle Developer/DBA, > ru@sunbay.com Sunbay Software AG, > ru@FreeBSD.org FreeBSD committer, > +380.652.512.251 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 10:43:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from imr2.ericy.com (imr2.ericy.com [12.34.240.68]) by hub.freebsd.org (Postfix) with ESMTP id 263C137B422; Thu, 10 May 2001 10:43:20 -0700 (PDT) (envelope-from Antoine.Beaupre@ericsson.ca) Received: from mr7.exu.ericsson.se (mr7att.ericy.com [138.85.92.15]) by imr2.ericy.com (8.11.3/8.11.3) with ESMTP id f4AHhI804251; Thu, 10 May 2001 12:43:18 -0500 (CDT) Received: from noah.lmc.ericsson.se (noah.lmc.ericsson.se [142.133.1.1]) by mr7.exu.ericsson.se (8.11.3/8.11.3) with ESMTP id f4AHhHd08636; Thu, 10 May 2001 12:43:17 -0500 (CDT) Received: from lmc35.lmc.ericsson.se (lmc35.lmc.ericsson.se [142.133.16.175]) by noah.lmc.ericsson.se (8.11.2/8.9.2) with ESMTP id f4AHhGG09045; Thu, 10 May 2001 13:43:16 -0400 (EDT) Received: by lmc35.lmc.ericsson.se with Internet Mail Service (5.5.2653.19) id ; Thu, 10 May 2001 13:43:15 -0400 Received: from lmc.ericsson.se (lmcpc100455.pc.lmc.ericsson.se [142.133.23.150]) by LMC37.lmc.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id JQDZ3ZZR; Thu, 10 May 2001 13:43:04 -0400 From: "Antoine Beaupre (LMC)" To: John Baldwin Cc: Ruslan Ermilov , current@FreeBSD.ORG, Poul-Henning Kamp Message-ID: <3AFAD326.CCCF04FB@lmc.ericsson.se> Date: Thu, 10 May 2001 13:43:02 -0400 Organization: LMC, Ericsson Research Canada X-Mailer: Mozilla 4.7 [en]C-CCK-MCD (WinNT; U) X-Accept-Language: en,fr-CA,fr MIME-Version: 1.0 Subject: Re: DEVFS References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > > On 10-May-01 Ruslan Ermilov wrote: > > 2) Is it valid that multiple DEVFS mounts over /dev are allowed? > > Why wouldn't it be? (Granted, it is a bit _weird_). You can do the same with > other fs's: ...and happily shoot yourself in the foot this way. :) I had pretty weird experiences into mounting multiple root directories (!). I have a crappy 486 which has an equally crappy IDE controller which can't grok my 3.2G HD. The loader couldn't boot the kernel from the drive. I had to keep another very crappy 250M HD with a duplicate of the / filesystem and a very special kernel that mounted its root from the other drive, since the kernel could recognize the drive correctly. Without DMA, of course. :) But it works. My point here is that I had a lot of fun in totally scrapping my system by doing a spurious mount /. No reboot(1) or halt(1) available... ;) C-A-Del! Anyways... Another OT question.. Is any MFC planned for devfs? I'm getting jealous of -current (running -stable). ;) Thanks, A. -- La sémantique est la gravité de l'abstraction. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 11:30:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 4E38237B424; Thu, 10 May 2001 11:30:05 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f4AITvP60499; Thu, 10 May 2001 11:29:57 -0700 (PDT) Date: Thu, 10 May 2001 11:29:57 -0700 (PDT) From: David Wolfskill Message-Id: <200105101829.f4AITvP60499@bunrab.catwhisker.org> To: jhb@FreeBSD.ORG, sziszi@petra.hos.u-szeged.hu Subject: RE: Today's special: nessusd panics -CURRENT Cc: freebsd-current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Thu, 10 May 2001 09:52:03 -0700 (PDT) >From: John Baldwin >> witness_get: witness exhausted >> exclusive(sleep mutex) Giant(0xc044a760) locked @ ../../i386/i386/trap.c:1169 >> panic: system call open returning with mutex(s) held >Ok, I see what's broken. I don't know how you are out of witness's though. >We don't have enough types of mutexes for that to happen. Try this patch: >Index: subr_witness.c >=================================================================== >RCS file: /usr/cvs/src/sys/kern/subr_witness.c,v >retrieving revision 1.70 >diff -u -r1.70 subr_witness.c >--- subr_witness.c 2001/05/04 17:15:16 1.70 >+++ subr_witness.c 2001/05/10 16:39:27 >@@ -1222,6 +1222,9 @@ > ("%s: p != curproc and we aren't in the debugger", __func__)); > KASSERT(!witness_cold, ("%s: witness_cold", __func__)); >+ if (!db_active && witness_dead) >+ return (0); >+ > nheld = witness_list_locks(&p->p_sleeplocks); > /* >-- Since I didn't use the "-l" flag to patch, it didn't apply, so I did it by hand (and subsequently thought to check for whitespace issues). But the patch appears to work; I'm up & running: FreeBSD m147.whistle.com 5.0-CURRENT FreeBSD 5.0-CURRENT #59: Thu May 10 04:06:04 PDT 2001 root@:/common/C/obj/usr/src/sys/LAPTOP_30W i386 (I had encountered the witness panic before applying the patch.) Only annoyance I'm encountering with it so far is involving my use of ssh; perhaps I'm doing something Really Weird, but in any case, that probably deserves a different Subject:. Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 12:15:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id ACAEB37B423 for ; Thu, 10 May 2001 12:15:46 -0700 (PDT) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 15174 invoked by uid 0); 10 May 2001 19:15:44 -0000 Received: from pd9508821.dip.t-dialin.net (HELO speedy.gsinet) (217.80.136.33) by mail.gmx.net (mail02) with SMTP; 10 May 2001 19:15:44 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id PAA20789 for current@FreeBSD.ORG; Thu, 10 May 2001 15:49:28 +0200 Date: Thu, 10 May 2001 15:49:28 +0200 From: Gerhard Sittig To: current@FreeBSD.ORG Subject: Re: **HEADS-UP** ficl changes change `base' type Message-ID: <20010510154928.A253@speedy.gsinet> Mail-Followup-To: current@FreeBSD.ORG References: <20010510140142.D26407@gsmx07.alcatel.com.au> <3AFA1C9F.2CB1630A@newsguy.com> <3AFA2545.BB8870D9@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3AFA2545.BB8870D9@newsguy.com>; from dcs@newsguy.com on Thu, May 10, 2001 at 02:21:09AM -0300 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 10, 2001 at 02:21 -0300, Daniel C. Sobral wrote: > > John Sadler is not a Unix user [ ... ] If you know exactly how > to produce a .tar.gz under Windows that is suitable for our > use, I'm sure he would appreciate the help. Most of the distros I've seen (Linux as well as *BSD) have the DOS ports of these tools on their first CD, next to other archivers / partitioners / bootselectors / X-Servers / etc. Given the need (read: if I'm not late) I could provide - binaries of tar and gzip for DOS and i386+ - a .BAT / .CMD file to shove dir %1 into %1.tar.gz but it will be untested or wil take a few days since I'm 100% MS free here. :) virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 13:21: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from newsguy.com (perry.pathlink.com [209.155.233.33]) by hub.freebsd.org (Postfix) with ESMTP id 380B337B422; Thu, 10 May 2001 13:21:04 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (ppp031-bsace7002.telebrasilia.net.br [200.181.81.31]) by newsguy.com (8.11.0/8.9.1) with ESMTP id f4AKKoD29442; Thu, 10 May 2001 13:20:50 -0700 (PDT) Message-ID: <3AFAF81E.13FFE8A3@newsguy.com> Date: Thu, 10 May 2001 17:20:46 -0300 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en,pt-BR,pt,en-GB,en-US,ja MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: **HEADS-UP** ficl changes change `base' type References: <20010510140142.D26407@gsmx07.alcatel.com.au> <3AFA1C9F.2CB1630A@newsguy.com> <3AFA2545.BB8870D9@newsguy.com> <20010510101832.B3561@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Thu, May 10, 2001 at 02:21:09AM -0300, Daniel C. Sobral wrote: > > John Sadler is not a Unix user, and has no experience with Unix, and > ... > > If you know exactly how to produce a .tar.gz under Windows that is > > suitable for our use, I'm sure he would appreciate the help. > > Ask him to use infozip/pkzip -- I know that is easy for Winloose users. > Our unzip has a command line option to fix the text line termination. The zip he produces can be extracted fine. That's not the question. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net Caffeine is proof that God hates mornings too To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 15:27: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (Postfix) with ESMTP id 624DF37B424; Thu, 10 May 2001 15:27:00 -0700 (PDT) (envelope-from Tomi.Vainio@Sun.COM) Received: from helsinki.Finland.Sun.COM ([129.159.101.19]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA15410; Thu, 10 May 2001 15:26:49 -0700 (PDT) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by helsinki.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v2.1p1) with ESMTP id BAA13765; Fri, 11 May 2001 01:26:44 +0300 (EET DST) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id BAA00085; Fri, 11 May 2001 01:26:41 +0300 (EEST) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15099.5537.663615.44949@ultrahot.Finland.Sun.COM> Date: Fri, 11 May 2001 01:26:41 +0300 To: Mark Santcroos Cc: "David O'Brien" , freebsd-current@FreeBSD.ORG, aab10490@pop16.odn.ne.jp Subject: Re: WinModem Support In-Reply-To: <20010510112139.A2151@laptop.6bone.nl> References: <15085.61825.708944.271219@ultrahot.Finland.Sun.COM> <20010507143720.A38755@laptop.6bone.nl> <20010510015125.A73744@hub.freebsd.org> <20010510112139.A2151@laptop.6bone.nl> X-Mailer: VM 6.92 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Santcroos writes: > > I have contacted the author and he made a last change in the interrupt > setup. > > I have made a small stand alone package for -CURRENT, it holds the .c, the > linux object file, a Makefile and a script to create the necessary device > files. (If you want it in your kernel you can figure out yourself > probably, this is just a proof of concept) > > http://www.ripe.net/home/mark/files/ltmdm_current_may_10.tgz > > It works great for me, let me know if it is not generic enough and I will > apply the changes. > I tried your package with Toshiba Portege 3440CT and 5.0C cvsupped last weekend. Still the same problems, no connect though it dials and ATI3 gives hard hang. Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 16:31:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.6.200.230]) by hub.freebsd.org (Postfix) with ESMTP id 7A26537B422; Thu, 10 May 2001 16:31:14 -0700 (PDT) (envelope-from mdharnois@home.com) Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id AC4BD14A11; Thu, 10 May 2001 18:31:53 -0500 (CDT) To: Bruce Evans Cc: John Baldwin , current@FreeBSD.ORG, bde@FreeBSD.ORG, Deimos Root , jhb@osd.bsdi.com Subject: Re: FW: Snapshot Log - world broken in telnetd References: From: Michael Harnois Date: 10 May 2001 18:31:52 -0500 In-Reply-To: (Bruce Evans's message of "Fri, 11 May 2001 03:16:35 +1000 (EST)") Message-ID: <86itj8n5lj.fsf@mharnois.workgroup.net> Lines: 13 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.5 (anise) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 May 2001 03:16:35 +1000 (EST), Bruce Evans said: > The kerberosIV telnetd is missing linkage to libpam, perhaps > more. The kerberosIV telnet and telnetd are missing linkage to libpam, for about three days. Just adding that lib makes it work ... -- Michael D. Harnois mdharnois@home.com Redeemer Lutheran Church Washburn, Iowa Creative thought means that you forgot where you read it. --Stanley Hauerwas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 10 22:44:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from sol.serv.u-szeged.hu (sol.serv.u-szeged.hu [160.114.51.3]) by hub.freebsd.org (Postfix) with ESMTP id 75DB337B423 for ; Thu, 10 May 2001 22:44:16 -0700 (PDT) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.serv.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id HAA18349; Fri, 11 May 2001 07:44:09 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 14y5ij-0006wU-00 for ; Fri, 11 May 2001 07:44:09 +0200 Date: Fri, 11 May 2001 07:44:09 +0200 From: Szilveszter Adam To: freebsd-current@FreeBSD.ORG Subject: Re: Today's special: nessusd panics -CURRENT Message-ID: <20010511074409.A26121@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , freebsd-current@FreeBSD.ORG References: <200105101829.f4AITvP60499@bunrab.catwhisker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105101829.f4AITvP60499@bunrab.catwhisker.org>; from david@catwhisker.org on Thu, May 10, 2001 at 11:29:57AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 10, 2001 at 11:29:57AM -0700, David Wolfskill wrote: > >Ok, I see what's broken. I don't know how you are out of witness's though. > >We don't have enough types of mutexes for that to happen. Try this patch: <...> > Since I didn't use the "-l" flag to patch, it didn't apply, so I did it > by hand (and subsequently thought to check for whitespace issues). Yes same with me:-) > But the patch appears to work; I'm up & running: Well unfortunately no such luck. It solves the first part of the problem (the "system call open retunrning with nutex(s) held" panic) but even after applying the patch and toning down MAXUSERS to 32 (I suspected it might be somewhat related) I still get the triple panic, which now looks like: witness_get: witness exhausted panic: witness_restore: lock (sleep mutex) Giant not locked After 'c', it says (attempting to sync the disks) witness_save: panic: lock (sleep mutex) Giant not locked And finally after attempting to dump: ata0: resetting devices: panic: lock (sleep mutex) Giant not locked Here come the traces. The third trace also contains the first and the second a bit further down. The third trace: Debugger panic witness_save mawait ata_command ad_reinit ata_reinit addump dumpsys boot panic => From here is part of the second trace too. witness_save boot panic => From here this is the first trace too. witness_restore msleep vm_pageout fork_exit fork_trampoline So basically the first trace is: Debugger panic witness_restore msleep vm_pageout fork_exit fork_trampoline And the second: Debugger panic witness_save boot panic witness_restore msleep vm_pageout fork_exit fork_trampoline This problem *only* appears when running nessusd. Any other app I tried (including X) runs fine. If you need more info let me know. -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 1: 4:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id 3786837B422; Fri, 11 May 2001 01:04:43 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f4B84Xp80936; Fri, 11 May 2001 10:04:33 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Ruslan Ermilov Cc: current@FreeBSD.org Subject: Re: DEVFS In-Reply-To: Your message of "Thu, 10 May 2001 20:18:28 +0300." <20010510201828.A81476@sunbay.com> Date: Fri, 11 May 2001 10:04:33 +0200 Message-ID: <80934.989568273@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010510201828.A81476@sunbay.com>, Ruslan Ermilov writes: >Hi! > >Just installed recent -CURRENT on my PC, and noticed strange things: > >1) If I don't have devfs line in /etc/fstab, why DEVFS mount is still > happening on /dev, and where? It's done as the first thing in /sbin/init to make sure all device access is done through DEVFS. > >2) Is it valid that multiple DEVFS mounts over /dev are allowed? yes. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 1: 6:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id 2437E37B424; Fri, 11 May 2001 01:06:38 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f4B86Kp81002; Fri, 11 May 2001 10:06:20 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: Ruslan Ermilov , current@FreeBSD.ORG Subject: Re: DEVFS In-Reply-To: Your message of "Thu, 10 May 2001 10:35:15 PDT." Date: Fri, 11 May 2001 10:06:20 +0200 Message-ID: <81000.989568380@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: > > >On Thu, 10 May 2001, Ruslan Ermilov wrote: > >> Hi! >> >> Just installed recent -CURRENT on my PC, and noticed strange things: >> >> 1) If I don't have devfs line in /etc/fstab, why DEVFS mount is still >> happening on /dev, and where? > >Somewhat wierdly and unobviously, it's init that does the magic. this is basically because it is one line to do it in /sbin/init, but about 100 to do it in the kernel. Blame the poor design of mount(2) (and ask Adrian when he fixes it :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 1: 7: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 8584137B423; Fri, 11 May 2001 01:07:04 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f4B871344184; Fri, 11 May 2001 12:07:02 +0400 (MSD) (envelope-from ache) Date: Fri, 11 May 2001 12:06:57 +0400 From: "Andrey A. Chernov" To: i18n@freebsd.org Cc: current@freebsd.org Subject: sysinstall and wrong /etc/ttys types Message-ID: <20010511120653.B43979@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The only thing left to make sysinstall localized setting working is adding code to fix /etc/ttys terminal types which in current variant is stuck to cons25 only producing wrong vt100 pseudographics for Latin* and KOI8-* users. I e. some code which replace cons25 in /etc/ttys according to this font table: Latin1: cons25l1 Latin2: cons25l2 KOI8-R: cons25r KOI8-U: cons25u (including screenmapped variants, of course) I don't know sysinstall deep enough for that. Any takers? -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 1:10:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id 2728337B422; Fri, 11 May 2001 01:10:17 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f4B8A5p81030; Fri, 11 May 2001 10:10:05 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Antoine Beaupre (LMC)" Cc: John Baldwin , Ruslan Ermilov , current@FreeBSD.ORG Subject: Re: DEVFS In-Reply-To: Your message of "Thu, 10 May 2001 13:43:02 EDT." <3AFAD326.CCCF04FB@lmc.ericsson.se> Date: Fri, 11 May 2001 10:10:05 +0200 Message-ID: <81028.989568605@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3AFAD326.CCCF04FB@lmc.ericsson.se>, "Antoine Beaupre (LMC)" writes: >Another OT question.. Is any MFC planned for devfs? I'm getting jealous >of -current (running -stable). ;) It will not be MFC'ed unless somebody else does the work, I simply don't have the time... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 1:10:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 71BE037B422 for ; Fri, 11 May 2001 01:10:47 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f4B8Aas11120; Fri, 11 May 2001 01:10:36 -0700 (PDT) (envelope-from obrien) Date: Fri, 11 May 2001 01:10:35 -0700 From: "David O'Brien" To: "Daniel C. Sobral" Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: **HEADS-UP** ficl changes change `base' type Message-ID: <20010511011035.A11082@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010510140142.D26407@gsmx07.alcatel.com.au> <3AFA1C9F.2CB1630A@newsguy.com> <3AFA2545.BB8870D9@newsguy.com> <20010510101832.B3561@dragon.nuxi.com> <3AFAF81E.13FFE8A3@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AFAF81E.13FFE8A3@newsguy.com>; from dcs@newsguy.com on Thu, May 10, 2001 at 05:20:46PM -0300 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 10, 2001 at 05:20:46PM -0300, Daniel C. Sobral wrote: > > > John Sadler is not a Unix user, and has no experience with Unix, and > > ... > > > If you know exactly how to produce a .tar.gz under Windows that is > > > suitable for our use, I'm sure he would appreciate the help. > > > > Ask him to use infozip/pkzip -- I know that is easy for Winloose users. > > Our unzip has a command line option to fix the text line termination. > > The zip he produces can be extracted fine. That's not the question. Then what's the question? Why can't people use the .zip file and not ask Sadler to produce a .tar.gz? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 1:14:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id BD98237B424; Fri, 11 May 2001 01:14:50 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f4B8ESQ11184; Fri, 11 May 2001 01:14:28 -0700 (PDT) (envelope-from obrien) Date: Fri, 11 May 2001 01:14:28 -0700 From: "David O'Brien" To: Brian Somers Cc: "Steve O'Hara-Smith" , freebsd@FreeBSD.ORG, clefevre@poboxes.com, asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: cp -u patch Message-ID: <20010511011427.C11082@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200105090917.f499H3B36790@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105090917.f499H3B36790@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Wed, May 09, 2001 at 10:17:03AM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Lets try another realistic example: > > > > > > cp -uvp ab* cde*.f* g? h/*.i? j/kl /m > > > What's the find | cpio invocation for that? When you come up with it, it > > > > echo ab* cde*.f* g? h/*.i? j/kl /m | cpio ... > > > > Messy - No, Portable - Yes. > > BZZZZT - wrong. cp flattens the hierarchy, cpio does not. I think > this was a trick question :*P Yes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 1:36: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id C15F237B422; Fri, 11 May 2001 01:35:58 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id SAA09464; Fri, 11 May 2001 18:35:43 +1000 Date: Fri, 11 May 2001 18:34:03 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Poul-Henning Kamp Cc: mjacob@feral.com, Ruslan Ermilov , current@FreeBSD.ORG Subject: Re: DEVFS In-Reply-To: <81000.989568380@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 May 2001, Poul-Henning Kamp wrote: > In message , Matthew > Jacob writes: > > > > > >On Thu, 10 May 2001, Ruslan Ermilov wrote: > > > >> Hi! > >> > >> Just installed recent -CURRENT on my PC, and noticed strange things: > >> > >> 1) If I don't have devfs line in /etc/fstab, why DEVFS mount is still > >> happening on /dev, and where? > > > >Somewhat wierdly and unobviously, it's init that does the magic. > > this is basically because it is one line to do it in /sbin/init, > but about 100 to do it in the kernel. > > Blame the poor design of mount(2) (and ask Adrian when he fixes > it :-) It must be the excellent design of mount(2) that makes it so easy to do things with it where it can be used :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 1:46: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 6285E37B422; Fri, 11 May 2001 01:45:49 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f4B8ix302081; Fri, 11 May 2001 01:45:00 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: ache@nagual.pp.ru Cc: i18n@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall and wrong /etc/ttys types In-Reply-To: <20010511120653.B43979@nagual.pp.ru> References: <20010511120653.B43979@nagual.pp.ru> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010511014459C.jkh@osd.bsdi.com> Date: Fri, 11 May 2001 01:44:59 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 31 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look through the cvs history for sysinstall - you'll see that it already had much of that already, back around 2.0.5 I think. It was eventually removed again due to disuse. - Jordan From: "Andrey A. Chernov" Subject: sysinstall and wrong /etc/ttys types Date: Fri, 11 May 2001 12:06:57 +0400 > The only thing left to make sysinstall localized setting working is adding > code to fix /etc/ttys terminal types which in current variant is stuck to > cons25 only producing wrong vt100 pseudographics for Latin* and KOI8-* > users. I e. some code which replace cons25 in /etc/ttys according to this > font table: > > Latin1: cons25l1 > Latin2: cons25l2 > KOI8-R: cons25r > KOI8-U: cons25u > > (including screenmapped variants, of course) > > I don't know sysinstall deep enough for that. Any takers? > > -- > Andrey A. Chernov > http://ache.pp.ru/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 1:49:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id 5A81D37B424; Fri, 11 May 2001 01:49:05 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f4B8i6p81922; Fri, 11 May 2001 10:44:07 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: mjacob@feral.com, Ruslan Ermilov , current@FreeBSD.ORG Subject: Re: DEVFS In-Reply-To: Your message of "Fri, 11 May 2001 18:34:03 +1000." Date: Fri, 11 May 2001 10:44:06 +0200 Message-ID: <81920.989570646@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bruce Evan s writes: >> Blame the poor design of mount(2) (and ask Adrian when he fixes >> it :-) > >It must be the excellent design of mount(2) that makes it so easy to >do things with it where it can be used :-). Just too bad it wasn't designed so that it can be used from kernel processes as well :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 1:54:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id DCDEC37B422; Fri, 11 May 2001 01:54:12 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f4B8s3G45162; Fri, 11 May 2001 12:54:03 +0400 (MSD) (envelope-from ache) Date: Fri, 11 May 2001 12:53:57 +0400 From: "Andrey A. Chernov" To: Jordan Hubbard Cc: i18n@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall and wrong /etc/ttys types Message-ID: <20010511125355.A45053@nagual.pp.ru> References: <20010511120653.B43979@nagual.pp.ru> <20010511014459C.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010511014459C.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Fri, May 11, 2001 at 01:44:59AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 11, 2001 at 01:44:59 -0700, Jordan Hubbard wrote: > Look through the cvs history for sysinstall - you'll see that it > already had much of that already, back around 2.0.5 I think. It > was eventually removed again due to disuse. Could you please be more specific on what you mean by "disuse"? I.e. what was the problem with that stuff and what goes wrong? Do you against its resurrection by what reasons? -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 2:21: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id EE1BA37B43C; Fri, 11 May 2001 02:20:44 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.11.3/8.11.3) with ESMTP id f4B9KIE60498; Fri, 11 May 2001 16:20:23 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Fri, 11 May 2001 16:20:18 +0700 (NSS) From: Max Khon To: "Andrey A. Chernov" Cc: Jordan Hubbard , i18n@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall and wrong /etc/ttys types In-Reply-To: <20010511125355.A45053@nagual.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Fri, 11 May 2001, Andrey A. Chernov wrote: > > Look through the cvs history for sysinstall - you'll see that it > > already had much of that already, back around 2.0.5 I think. It > > was eventually removed again due to disuse. > > Could you please be more specific on what you mean by "disuse"? I.e. what > was the problem with that stuff and what goes wrong? Do you against its > resurrection by what reasons? having sysinstall that configures /etc/ttys will be great /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 3:44:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 6A9F637B422; Fri, 11 May 2001 03:44:32 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f4BAhY446357; Fri, 11 May 2001 14:43:35 +0400 (MSD) (envelope-from ache) Date: Fri, 11 May 2001 14:43:32 +0400 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: Max Khon Cc: Jordan Hubbard , i18n@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall and wrong /etc/ttys types Message-ID: <20010511144331.A46323@nagual.pp.ru> References: <20010511125355.A45053@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from fjoe@iclub.nsu.ru on Fri, May 11, 2001 at 04:20:18PM +0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 11, 2001 at 16:20:18 +0700, Max Khon wrote: > > having sysinstall that configures /etc/ttys will be great > It can be implemented as separate entry in "Console" setup menu, i.e. "Fonts" ... "Screenmap", "Ttys" -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 5:30:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by hub.freebsd.org (Postfix) with ESMTP id CDA4837B423; Fri, 11 May 2001 05:30:38 -0700 (PDT) (envelope-from ms@laptop.6bone.nl) Received: from laptop.6bone.nl (kantoor.ripe.net [193.0.1.98]) by birch.ripe.net (8.8.8/8.8.8) with SMTP id OAA18311; Fri, 11 May 2001 14:30:34 +0200 (CEST) Received: (nullmailer pid 21605 invoked by uid 1000); Fri, 11 May 2001 12:17:49 -0000 Date: Fri, 11 May 2001 14:17:49 +0200 From: Mark Santcroos To: Tomi Vainio - Sun Finland - Cc: "David O'Brien" , freebsd-current@FreeBSD.ORG, aab10490@pop16.odn.ne.jp Subject: Re: WinModem Support Message-ID: <20010511141749.A21474@laptop.6bone.nl> References: <15085.61825.708944.271219@ultrahot.Finland.Sun.COM> <20010507143720.A38755@laptop.6bone.nl> <20010510015125.A73744@hub.freebsd.org> <20010510112139.A2151@laptop.6bone.nl> <15099.5537.663615.44949@ultrahot.Finland.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15099.5537.663615.44949@ultrahot.Finland.Sun.COM>; from Tomi.Vainio@Sun.COM on Fri, May 11, 2001 at 01:26:41AM +0300 X-Handles: MS6-6BONE, MS32260-NIC, MS18417-RIPE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 11, 2001 at 01:26:41AM +0300, Tomi Vainio - Sun Finland - wrote: > Mark Santcroos writes: > > > > I have contacted the author and he made a last change in the interrupt > > setup. > > > > I have made a small stand alone package for -CURRENT, it holds the .c, the > > linux object file, a Makefile and a script to create the necessary device > > files. (If you want it in your kernel you can figure out yourself > > probably, this is just a proof of concept) > > > > http://www.ripe.net/home/mark/files/ltmdm_current_may_10.tgz > > > > It works great for me, let me know if it is not generic enough and I will > > apply the changes. > > > I tried your package with Toshiba Portege 3440CT and 5.0C cvsupped > last weekend. Still the same problems, no connect though it dials and > ATI3 gives hard hang. I had that errors also before the last patch, but after applying my that problems disappeared. FYI: I have a Toshiba Portege 3110CT, probably the same modem as yours. (as the machines are very similar) I found it very hard to debug the problem myself, maybe someone has good advise on debugging problems that are interrupt related and hang the machine. Also I noticed that the driver is not yet perfect. Although it does work sometimes. I haven't get it to work for longer periods and multiple times. However, these seem minor issues to me. Good luck. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 7:16: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 422F737B422; Fri, 11 May 2001 07:15:58 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f4BEF7f23294; Fri, 11 May 2001 10:15:07 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 11 May 2001 10:15:06 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp Cc: Bruce Evans , mjacob@feral.com, Ruslan Ermilov , current@FreeBSD.ORG Subject: Re: DEVFS In-Reply-To: <81920.989570646@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 May 2001, Poul-Henning Kamp wrote: > In message , Bruce Evan > s writes: > > >> Blame the poor design of mount(2) (and ask Adrian when he fixes > >> it :-) > > > >It must be the excellent design of mount(2) that makes it so easy to > >do things with it where it can be used :-). > > Just too bad it wasn't designed so that it can be used from kernel > processes as well :-( I've made this observation before, of course, but it is my general opionion that, leaving aside uio structures, awareness of "userland" data pointers should generall be limited to the system call code rather than the service implementation. The existence of userland points in VFS calls (and I've introduced one myself in the vfs_extattrctl call) is generally evil. It makes it much harder to initiate a service from within a kernel thread or process, and do ABI wrapping. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 7:21:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id DE99537B422; Fri, 11 May 2001 07:21:34 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f4BELPp83745; Fri, 11 May 2001 16:21:25 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: Bruce Evans , mjacob@feral.com, Ruslan Ermilov , current@FreeBSD.ORG Subject: Re: DEVFS In-Reply-To: Your message of "Fri, 11 May 2001 10:15:06 EDT." Date: Fri, 11 May 2001 16:21:25 +0200 Message-ID: <83743.989590885@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Robe rt Watson writes: >On Fri, 11 May 2001, Poul-Henning Kamp wrote: > >> In message , Bruce Evan >> s writes: >> >> >> Blame the poor design of mount(2) (and ask Adrian when he fixes >> >> it :-) >> > >> >It must be the excellent design of mount(2) that makes it so easy to >> >do things with it where it can be used :-). >> >> Just too bad it wasn't designed so that it can be used from kernel >> processes as well :-( > >I've made this observation before, of course, but it is my general >opionion that, leaving aside uio structures, awareness of "userland" data >pointers should generall be limited to the system call code rather than >the service implementation. The existence of userland points in VFS calls >(and I've introduced one myself in the vfs_extattrctl call) is generally >evil. It makes it much harder to initiate a service from within a kernel >thread or process, and do ABI wrapping. Well, if I'm not allowed to gripe about that (although in reality you agree with me :-) then I'll gripe about the "max 32 mount options" limitation. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 7:43:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id EC54337B423; Fri, 11 May 2001 07:43:16 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f4BEga303311; Fri, 11 May 2001 07:42:36 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: ache@nagual.pp.ru Cc: i18n@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall and wrong /etc/ttys types In-Reply-To: <20010511125355.A45053@nagual.pp.ru> References: <20010511120653.B43979@nagual.pp.ru> <20010511014459C.jkh@osd.bsdi.com> <20010511125355.A45053@nagual.pp.ru> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010511074236D.jkh@osd.bsdi.com> Date: Fri, 11 May 2001 07:42:36 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 19 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Could you please be more specific on what you mean by "disuse"? I.e. what > was the problem with that stuff and what goes wrong? Do you against its > resurrection by what reasons? E.g. we went and translated a bunch of the *.TXT files into various languages (among them Russian) and then gave sysinstall the ability to change the screen map, terminal type and keyboard mapping according to a global language setting. That survived for exactly one release after we realized that we didn't have the infrastructure necessary to translate those documents on an ongoing basis. It was sort of an experiment anyway, so nobody really cried when we took it back out. But I'm not against it's resurrection. That was then, these days we have quite a bit more infrastructure and a better translation process. Also, thanks to Mr. Mah, the *.TXT files have finally been integrated into our overall docs and are thus far easier to generate international versions of. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 8: 3:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 5D44037B423; Fri, 11 May 2001 08:03:08 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.11.3/8.11.3) id f4BF2km49149; Fri, 11 May 2001 19:02:47 +0400 (MSD) (envelope-from ache) Date: Fri, 11 May 2001 19:02:43 +0400 From: "Andrey A. Chernov" To: Jordan Hubbard Cc: i18n@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall and wrong /etc/ttys types Message-ID: <20010511190242.A49045@nagual.pp.ru> References: <20010511120653.B43979@nagual.pp.ru> <20010511014459C.jkh@osd.bsdi.com> <20010511125355.A45053@nagual.pp.ru> <20010511074236D.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010511074236D.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Fri, May 11, 2001 at 07:42:36AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 11, 2001 at 07:42:36 -0700, Jordan Hubbard wrote: > E.g. we went and translated a bunch of the *.TXT files into various > languages (among them Russian) and then gave sysinstall the ability to > change the screen map, terminal type and keyboard mapping according to > a global language setting. That survived for exactly one release > after we realized that we didn't have the infrastructure necessary to > translate those documents on an ongoing basis. It was sort of an > experiment anyway, so nobody really cried when we took it back out. Umm, I mean not this complex thing at all, I mean just tuning /etc/ttys file the same way as sysinstall currently tunes /etc/rc.conf file, i.e. just change variables there without loading font/screenmap/etc inside sysinstall itself. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 8:39:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.org.ru (sweet.etrust.ru [194.84.67.5]) by hub.freebsd.org (Postfix) with ESMTP id D8EEB37B43E for ; Fri, 11 May 2001 08:39:09 -0700 (PDT) (envelope-from osa@freebsd.org.ru) Received: by freebsd.org.ru (Postfix, from userid 1000) id C6F43219; Fri, 11 May 2001 19:39:07 +0400 (MSD) Date: Fri, 11 May 2001 19:39:07 +0400 From: "Sergey A. Osokin" To: current@FreeBSD.org Subject: new function for libdevstat Message-ID: <20010511193907.A49316@freebsd.org.ru> Reply-To: osa@FreeBSD.org.ru Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="/04w6evG8XlLl3ft" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello. 2 monthes ago I talked in -current about new features for libdevstat. Here is a new function, which calculate more statistics then existing compute_stats(). (compute_stats() calculate only average results, not read/write results). Please see my first step. Comments are welcome. -- Rgdz, /"\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN osa@freebsd.org.ru X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="newstat.c" int devstat_compute_statistics(struct devstat *current, struct devstat *previous, long double etime, u_int64_t *total_bytes, u_int64_t *total_bytes_read, u_int64_t *total_bytes_write, u_int64_t *total_transfers, u_int64_t *total_transfers_read, u_int64_t *total_transfers_write, u_int64_t *total_transfers_other, u_int64_t *total_blocks, u_int64_t *total_blocks_read, u_int64_t *total_blocks_write, long double *kb_per_transfer, long double *kb_per_transfer_read, long double *kb_per_transfer_write, long double *transfers_per_second, long double *transfers_per_second_read, long double *transfers_per_second_write, long double *transfers_per_second_other, long double *mb_per_second, long double *mb_per_second_read, long double *mb_per_second_write, long double *blocks_per_second, long double *blocks_per_second_read, long double *blocks_per_second_write, long double *ms_per_transaction, long double *ms_per_transaction_read, long double *ms_per_transaction_write) { u_int64_t totalbytes, totalbytes_read, totalbytes_write; u_int64_t totaltransfers, totaltransfers_read, totaltransfers_write, totaltransfers_other; u_int64_t totalblocks, totalblocks_read, totalblocks_write; char *func_name = "devstat_compute_statistics"; /* * current is the only mandatory field. */ if (current == NULL) { sprintf(devstat_errbuf, "%s: current stats structure was NULL", func_name); return(-1); } /* totalbytes = (current->bytes_written + current->bytes_read) - ((previous) ? (previous->bytes_written + previous->bytes_read) : 0); if (total_bytes) *total_bytes = totalbytes; */ totalbytes_read = current->bytes_read - ((previous) ? previous->bytes_read) : 0); if (total_bytes_read) *total_bytes_read = totalbytes_read; totalbytes_write = current->bytes_written - ((previous) ? (previous->bytes_written) : 0); if (total_bytes_write) *total_bytes_write = totalbytes_write; totalbytes = totalbytes_read + totalbytes_write; if (total_bytes) *total_bytes = totalbytes; /* totaltransfers = (current->num_reads + current->num_writes + current->num_other) - ((previous) ? (previous->num_reads + previous->num_writes + previous->num_other) : 0); if (total_transfers) *total_transfers = totaltransfers; */ totaltransfers_read = current->num_reads - ((previous) ? (previous->num_reads) : 0); if (total_transfers_read) *total_transfers_read = totaltransfers_read; totaltransfers_write = current->num_writes - ((previous) ? (previous->num_writes) : 0); if (total_transfers_write) *total_transfers_write = totaltransfers_write; totaltransfers_other = current->num_other - ((previous) ? (previous->num_other) : 0); if (total_transfers_other) *total_transfers_other = totaltransfers_other; totaltransfers = totaltransfers_read + totaltransfers_write + totaltransfers_other; if (total_transfers) *total_transfers = totaltransfers; if (transfers_per_second) { if (etime > 0.0) { *transfers_per_second = totaltransfers; *transfers_per_second /= etime; } else *transfers_per_second = 0.0; } if (transfers_per_second_read) { if (etime > 0.0) { *transfers_per_second_read = totaltransfers_read; *transfers_per_second_read /= etime; } else *transfers_per_second_read = 0.0; } if (transfers_per_second_write) { if (etime > 0.0) { *transfers_per_second_write = totaltransfers_write; *transfers_per_second_write /= etime; } else *transfers_per_second_write = 0.0; } if (transfers_per_second_other) { if (etime > 0.0) { *transfers_per_second_other = totaltransfers_other; *transfers_per_second_other /= etime; } else *transfers_per_second_other = 0.0; } if (kb_per_transfer) { *kb_per_transfer = totalbytes; *kb_per_transfer /= 1024; if (totaltransfers > 0) *kb_per_transfer /= totaltransfers; else *kb_per_transfer = 0.0; } if (kb_per_transfer_read) { *kb_per_transfer_read = totalbytes_read; *kb_per_transfer_read /= 1024; if (totaltransfers_read > 0) *kb_per_transfer_read /= totaltransfers_read; else *kb_per_transfer_read = 0.0; } if (kb_per_transfer_write) { *kb_per_transfer_write = totalbytes_write; *kb_per_transfer_write /= 1024; if (totaltransfers_write > 0) *kb_per_transfer_write /= totaltransfers_write; else *kb_per_transfer_write = 0.0; } if (mb_per_second) { *mb_per_second = totalbytes; *mb_per_second /= 1024 * 1024; if (etime > 0.0) *mb_per_second /= etime; else *mb_per_second = 0.0; } if (mb_per_second_read) { *mb_per_second_read = totalbytes_read; *mb_per_second_read /= 1024 * 1024; if (etime > 0.0) *mb_per_second_read /= etime; else *mb_per_second_read = 0.0; } if (mb_per_second_write) { *mb_per_second_write = totalbytes_write; *mb_per_second_write /= 1024 * 1024; if (etime > 0.0) *mb_per_second_write /= etime; else *mb_per_second_write = 0.0; } totalblocks = totalbytes; totalblocks_read = totalbytes_read; totalblocks_write = totalbytes_write; if (current->block_size > 0) { totalblocks /= current->block_size; totalblocks_read /= current->block_size; totalblocks_write /= current->block_size; } else { totalblocks /= 512; totalblocks_read /= 512; totalblocks_write /= 512; } if (total_blocks) *total_blocks = totalblocks; if (total_blocks_read) *total_blocks_read = totalblocks_read; if (total_blocks_write) *total_blocks_write = totalblocks_write; if (blocks_per_second) { *blocks_per_second = totalblocks; if (etime > 0.0) *blocks_per_second /= etime; else *blocks_per_second = 0.0; } if (blocks_per_second_read) { *blocks_per_second_read = totalblocks_read; if (etime > 0.0) *blocks_per_second_read /= etime; else *blocks_per_second_read = 0.0; } if (blocks_per_second_write) { *blocks_per_second_write = totalblocks_write; if (etime > 0.0) *blocks_per_second_write /= etime; else *blocks_per_second_write = 0.0; } if (ms_per_transaction) { if (totaltransfers > 0) { *ms_per_transaction = etime; *ms_per_transaction /= totaltransfers; *ms_per_transaction *= 1000; } else *ms_per_transaction = 0.0; } if (ms_per_transaction_read) { if (totaltransfers_read > 0) { *ms_per_transaction_read = etime; *ms_per_transaction_read /= totaltransfers_read; *ms_per_transaction_read *= 1000; } else *ms_per_transaction_read = 0.0; } if (ms_per_transaction_write) { if (totaltransfers_write > 0) { *ms_per_transaction_write = etime; *ms_per_transaction_write /= totaltransfers_write; *ms_per_transaction_write *= 1000; } else *ms_per_transaction_write = 0.0; } return(0); } --/04w6evG8XlLl3ft-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 10:36:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 61DDF37B71A for ; Fri, 11 May 2001 10:36:15 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f4BHZop85383; Fri, 11 May 2001 19:35:50 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: osa@freebsd.org.ru Cc: current@FreeBSD.ORG Subject: Re: new function for libdevstat In-Reply-To: Your message of "Fri, 11 May 2001 19:39:07 +0400." <20010511193907.A49316@freebsd.org.ru> Date: Fri, 11 May 2001 19:35:50 +0200 Message-ID: <85381.989602550@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010511193907.A49316@freebsd.org.ru>, "Sergey A. Osokin" writes: >Hello. >2 monthes ago I talked in -current about new features for libdevstat. >Here is a new function, which calculate more statistics then >existing compute_stats(). (compute_stats() calculate only average >results, not read/write results). >Please see my first step. Comments are welcome. I really don't think this is the way... I would far rather see: enum DEVSTAT_METRIC { DEVSTAT_BYTES, DEVSTAT_BYTES_READ, DEVSTAT_BYTES_WRITE, ... } int devstat_compute_statistics( struct devstat *current, struct devstat *previous, enum DEVSTAT_METRIC metric, double *destination); Since that can be extended with new metrics without changing the ABI... Poul-Henning >-- > >Rgdz, /"\ >Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN >osa@freebsd.org.ru X AGAINST HTML MAIL >http://freebsd.org.ru/~osa/ / \ > >--/04w6evG8XlLl3ft >Content-Type: text/plain; charset=us-ascii >Content-Disposition: attachment; filename="newstat.c" > >int >devstat_compute_statistics(struct devstat *current, struct devstat *previous, > long double etime, > u_int64_t *total_bytes, > u_int64_t *total_bytes_read, > u_int64_t *total_bytes_write, > u_int64_t *total_transfers, > u_int64_t *total_transfers_read, > u_int64_t *total_transfers_write, > u_int64_t *total_transfers_other, > u_int64_t *total_blocks, > u_int64_t *total_blocks_read, > u_int64_t *total_blocks_write, > long double *kb_per_transfer, > long double *kb_per_transfer_read, > long double *kb_per_transfer_write, > long double *transfers_per_second, > long double *transfers_per_second_read, > long double *transfers_per_second_write, > long double *transfers_per_second_other, > long double *mb_per_second, > long double *mb_per_second_read, > long double *mb_per_second_write, > long double *blocks_per_second, > long double *blocks_per_second_read, > long double *blocks_per_second_write, > long double *ms_per_transaction, > long double *ms_per_transaction_read, > long double *ms_per_transaction_write) > >{ > u_int64_t totalbytes, totalbytes_read, totalbytes_write; > u_int64_t totaltransfers, totaltransfers_read, totaltransfers_write, totaltransfers_other; > u_int64_t totalblocks, totalblocks_read, totalblocks_write; > char *func_name = "devstat_compute_statistics"; > > /* > * current is the only mandatory field. > */ > if (current == NULL) { > sprintf(devstat_errbuf, "%s: current stats structure was NULL", > func_name); > return(-1); > } >/* > totalbytes = (current->bytes_written + current->bytes_read) - > ((previous) ? (previous->bytes_written + > previous->bytes_read) : 0); > > if (total_bytes) > *total_bytes = totalbytes; >*/ > > totalbytes_read = current->bytes_read - ((previous) ? previous->bytes_read) : 0); > > if (total_bytes_read) > *total_bytes_read = totalbytes_read; > > totalbytes_write = current->bytes_written - ((previous) ? (previous->bytes_written) : 0); > > if (total_bytes_write) > *total_bytes_write = totalbytes_write; > > totalbytes = totalbytes_read + totalbytes_write; > > if (total_bytes) > *total_bytes = totalbytes; > >/* > totaltransfers = (current->num_reads + > current->num_writes + > current->num_other) - > ((previous) ? > (previous->num_reads + > previous->num_writes + > previous->num_other) : 0); > > if (total_transfers) > *total_transfers = totaltransfers; >*/ > > totaltransfers_read = current->num_reads - ((previous) ? (previous->num_reads) : 0); > > if (total_transfers_read) > *total_transfers_read = totaltransfers_read; > > totaltransfers_write = current->num_writes - ((previous) ? (previous->num_writes) : 0); > > if (total_transfers_write) > *total_transfers_write = totaltransfers_write; > > totaltransfers_other = current->num_other - ((previous) ? (previous->num_other) : 0); > > if (total_transfers_other) > *total_transfers_other = totaltransfers_other; > > totaltransfers = totaltransfers_read + totaltransfers_write + totaltransfers_other; > > if (total_transfers) > *total_transfers = totaltransfers; > > if (transfers_per_second) { > if (etime > 0.0) { > *transfers_per_second = totaltransfers; > *transfers_per_second /= etime; > } else > *transfers_per_second = 0.0; > } > > if (transfers_per_second_read) { > if (etime > 0.0) { > *transfers_per_second_read = totaltransfers_read; > *transfers_per_second_read /= etime; > } else > *transfers_per_second_read = 0.0; > } > > if (transfers_per_second_write) { > if (etime > 0.0) { > *transfers_per_second_write = totaltransfers_write; > *transfers_per_second_write /= etime; > } else > *transfers_per_second_write = 0.0; > } > > if (transfers_per_second_other) { > if (etime > 0.0) { > *transfers_per_second_other = totaltransfers_other; > *transfers_per_second_other /= etime; > } else > *transfers_per_second_other = 0.0; > } > > if (kb_per_transfer) { > *kb_per_transfer = totalbytes; > *kb_per_transfer /= 1024; > if (totaltransfers > 0) > *kb_per_transfer /= totaltransfers; > else > *kb_per_transfer = 0.0; > } > > > if (kb_per_transfer_read) { > *kb_per_transfer_read = totalbytes_read; > *kb_per_transfer_read /= 1024; > if (totaltransfers_read > 0) > *kb_per_transfer_read /= totaltransfers_read; > else > *kb_per_transfer_read = 0.0; > } > > > if (kb_per_transfer_write) { > *kb_per_transfer_write = totalbytes_write; > *kb_per_transfer_write /= 1024; > if (totaltransfers_write > 0) > *kb_per_transfer_write /= totaltransfers_write; > else > *kb_per_transfer_write = 0.0; > } > > if (mb_per_second) { > *mb_per_second = totalbytes; > *mb_per_second /= 1024 * 1024; > if (etime > 0.0) > *mb_per_second /= etime; > else > *mb_per_second = 0.0; > } > > if (mb_per_second_read) { > *mb_per_second_read = totalbytes_read; > *mb_per_second_read /= 1024 * 1024; > if (etime > 0.0) > *mb_per_second_read /= etime; > else > *mb_per_second_read = 0.0; > } > > if (mb_per_second_write) { > *mb_per_second_write = totalbytes_write; > *mb_per_second_write /= 1024 * 1024; > if (etime > 0.0) > *mb_per_second_write /= etime; > else > *mb_per_second_write = 0.0; > } > > totalblocks = totalbytes; > totalblocks_read = totalbytes_read; > totalblocks_write = totalbytes_write; > > if (current->block_size > 0) { > totalblocks /= current->block_size; > totalblocks_read /= current->block_size; > totalblocks_write /= current->block_size; > } > else { > totalblocks /= 512; > totalblocks_read /= 512; > totalblocks_write /= 512; > } > > if (total_blocks) > *total_blocks = totalblocks; > > if (total_blocks_read) > *total_blocks_read = totalblocks_read; > > if (total_blocks_write) > *total_blocks_write = totalblocks_write; > > if (blocks_per_second) { > *blocks_per_second = totalblocks; > if (etime > 0.0) > *blocks_per_second /= etime; > else > *blocks_per_second = 0.0; > } > > if (blocks_per_second_read) { > *blocks_per_second_read = totalblocks_read; > if (etime > 0.0) > *blocks_per_second_read /= etime; > else > *blocks_per_second_read = 0.0; > } > > if (blocks_per_second_write) { > *blocks_per_second_write = totalblocks_write; > if (etime > 0.0) > *blocks_per_second_write /= etime; > else > *blocks_per_second_write = 0.0; > } > > if (ms_per_transaction) { > if (totaltransfers > 0) { > *ms_per_transaction = etime; > *ms_per_transaction /= totaltransfers; > *ms_per_transaction *= 1000; > } else > *ms_per_transaction = 0.0; > } > > if (ms_per_transaction_read) { > if (totaltransfers_read > 0) { > *ms_per_transaction_read = etime; > *ms_per_transaction_read /= totaltransfers_read; > *ms_per_transaction_read *= 1000; > } else > *ms_per_transaction_read = 0.0; > } > > if (ms_per_transaction_write) { > if (totaltransfers_write > 0) { > *ms_per_transaction_write = etime; > *ms_per_transaction_write /= totaltransfers_write; > *ms_per_transaction_write *= 1000; > } else > *ms_per_transaction_write = 0.0; > } > > return(0); >} > >--/04w6evG8XlLl3ft-- > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 11:20:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 32C5237B424 for ; Fri, 11 May 2001 11:20:19 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id UAA12610 for freebsd-current@freebsd.org; Fri, 11 May 2001 20:20:18 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f4BIGMV50247; Fri, 11 May 2001 20:16:22 +0200 (MET DST) (envelope-from j) Date: Fri, 11 May 2001 20:16:22 +0200 (MET DST) Message-Id: <200105111816.f4BIGMV50247@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden 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 References: <20010511120653.B43979@nagual.pp.ru> <20010511014459C.jkh@osd.bsdi.com> <20010511125355.A45053@nagual.pp.ru> <20010511074236D.jkh@osd.bsdi.com> <20010511190242.A49045@nagual.pp.ru> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: sysinstall and wrong /etc/ttys types X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > Umm, I mean not this complex thing at all, I mean just tuning > /etc/ttys file the same way as sysinstall currently tunes > /etc/rc.conf file, i.e. just change variables there without loading > font/screenmap/etc inside sysinstall itself. At least the keymap loading however is crucial for all non-US layout keyboards. Otherwise, e. g. a German luser has a hard time finding the / character needed to specify a mount point. That's been the basic reason why i once added the functionality for both, immediate execution as well as remembering it for later use. Screen maps, font loading etc. is another thing. For the purpose of installation, the default IBM cp437 font is certainly enough. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 20:22:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (cvsup2.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id E446D37B424; Fri, 11 May 2001 20:22:15 -0700 (PDT) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: (from uucp@localhost) by rina.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W-rina.r-20010412) with UUCP id f4C3M9l06325 ; Sat, 12 May 2001 12:22:09 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp [fec0::1:280:c8ff:fe6b:6d73]) by sohgo.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W) with ESMTP id f4C3M0J15415 ; Sat, 12 May 2001 12:22:02 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.11.3+3.4W/3.7W) with ESMTP id e4C3Lvp08649 ; Fri, 12 May 2000 12:21:59 +0900 (JST) Message-Id: <200005120321.e4C3Lvp08649@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Date: Fri, 12 May 2000 12:21:57 +0900 From: Seigo Tanimura To: John Baldwin Cc: Seigo Tanimura , current@FreeBSD.org Subject: Re: select(2) converted to use a condition variable, and optimis In-Reply-To: <200105100006.f4A06Gj35470@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> References: <200105091020.f49AK7P05497@rina.r.dl.itc.u-tokyo.ac.jp> <200105100006.f4A06Gj35470@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> User-Agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 10 May 2001 09:06:15 +0900, Seigo Tanimura said: Seigo> A quick and hopefully efficient solution to those problems is to Seigo> fhold() struct file's first, then enter polling loop. That seems much Seigo> cheaper than to work on free()ing a vnode or a socket with holding a Seigo> process lock, provided that struct filedesc and file are protected Seigo> properly (and we have to do it anyway). That work is now in the patch at: http://people.FreeBSD.org/~tanimura/patches/selectopt.diff Another work in that patch is elimination of P_SELECT and nselcoll check just prior to waiting for selwait. As we now scan file descriptors with holding a process lock, race with selwakeup() should never occur during polling. Please note that netncp and netsmb are not in the scope the solution discussed above because we can neither lock nor hold a reference to a socket for now. Since several issues regarding to the file descriptor layer have risen up, I am planning to commit the patch soon and work on locking file descriptors. -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 20:47:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.hub.org (SHW39-29.accesscable.net [24.138.39.29]) by hub.freebsd.org (Postfix) with ESMTP id 02C2837B423 for ; Fri, 11 May 2001 20:47:42 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.3/8.11.1) with ESMTP id f4C3lUM55858 for ; Sat, 12 May 2001 00:47:30 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Sat, 12 May 2001 00:47:30 -0300 (ADT) From: The Hermit Hacker To: Subject: make installworld runs out of space on / ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My / directory, right now, has 12Meg free on it ... if I do a make installworld, it will fail due to no space left on device ... Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/da1s1a 63503 46015 12408 79% 1858 14012 12% / Has anyone run into this one? Is there a way of fixing it? I can't find anything on / that isn't supposed to be there, or is relatively large ;( Thanks ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 20:55:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id D4CA637B43E for ; Fri, 11 May 2001 20:55:37 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (localhost.xtalwind.net [127.0.0.1]) by germanium.xtalwind.net (8.11.3/8.11.3) with ESMTP id f4C3tXJ60625; Fri, 11 May 2001 23:55:33 -0400 (EDT) (envelope-from jack@germanium.xtalwind.net) Date: Fri, 11 May 2001 23:55:33 -0400 (EDT) From: jack To: The Hermit Hacker Cc: Subject: Re: make installworld runs out of space on / ... In-Reply-To: Message-ID: <20010511235317.A59947-100000@germanium.xtalwind.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On May 12 The Hermit Hacker wrote: > My / directory, right now, has 12Meg free on it ... if I do a make > installworld, it will fail due to no space left on device ... > > Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on > /dev/da1s1a 63503 46015 12408 79% 1858 14012 12% / > > Has anyone run into this one? Yes, with softupdates enabled on / > Is there a way of fixing it? tunefs -n disable / worked for me. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- A Microsoft Certified Systems Engineer is to computing what a McDonalds Certified Food Specialist is to fine cuisine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 20:59:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from casimir.physics.purdue.edu (casimir.physics.purdue.edu [128.210.146.111]) by hub.freebsd.org (Postfix) with ESMTP id 2DCBE37B424 for ; Fri, 11 May 2001 20:59:37 -0700 (PDT) (envelope-from will@physics.purdue.edu) Received: by casimir.physics.purdue.edu (Postfix, from userid 1000) id 543411872D; Fri, 11 May 2001 22:54:05 -0500 (EST) Date: Fri, 11 May 2001 22:54:05 -0500 From: Will Andrews To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: make installworld runs out of space on / ... Message-ID: <20010511225405.A29602@casimir.physics.purdue.edu> Reply-To: Will Andrews References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: ; from scrappy@hub.org on Sat, May 12, 2001 at 12:47:30AM -0300 X-Operating-System: Linux 2.2.18 sparc64 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 12, 2001 at 12:47:30AM -0300, The Hermit Hacker wrote: > My / directory, right now, has 12Meg free on it ... if I do a make > installworld, it will fail due to no space left on device ... > > Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on > /dev/da1s1a 63503 46015 12408 79% 1858 14012 12% / > > Has anyone run into this one? Is there a way of fixing it? I can't find > anything on / that isn't supposed to be there, or is relatively large ;( rm -rf /var/tmp/install.* -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 21: 2:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.hub.org (SHW39-29.accesscable.net [24.138.39.29]) by hub.freebsd.org (Postfix) with ESMTP id 87F5737B423 for ; Fri, 11 May 2001 21:02:25 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.3/8.11.1) with ESMTP id f4C42FV56004; Sat, 12 May 2001 01:02:15 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Sat, 12 May 2001 01:02:15 -0300 (ADT) From: The Hermit Hacker To: jack Cc: Subject: Re: make installworld runs out of space on / ... In-Reply-To: <20010511235317.A59947-100000@germanium.xtalwind.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 May 2001, jack wrote: > On May 12 The Hermit Hacker wrote: > > > My / directory, right now, has 12Meg free on it ... if I do a make > > installworld, it will fail due to no space left on device ... > > > > Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on > > /dev/da1s1a 63503 46015 12408 79% 1858 14012 12% / > > > > Has anyone run into this one? > > Yes, with softupdates enabled on / > > > Is there a way of fixing it? > > tunefs -n disable / worked for me. d'oh, hadn't thought of that ... will do that before I do my next make installworld, thanks ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 21: 2:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.hub.org (SHW39-29.accesscable.net [24.138.39.29]) by hub.freebsd.org (Postfix) with ESMTP id 1204637B424 for ; Fri, 11 May 2001 21:02:45 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.3/8.11.1) with ESMTP id f4C42gL56008; Sat, 12 May 2001 01:02:42 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Sat, 12 May 2001 01:02:42 -0300 (ADT) From: The Hermit Hacker To: Will Andrews Cc: Subject: Re: make installworld runs out of space on / ... In-Reply-To: <20010511225405.A29602@casimir.physics.purdue.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 May 2001, Will Andrews wrote: > On Sat, May 12, 2001 at 12:47:30AM -0300, The Hermit Hacker wrote: > > My / directory, right now, has 12Meg free on it ... if I do a make > > installworld, it will fail due to no space left on device ... > > > > Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on > > /dev/da1s1a 63503 46015 12408 79% 1858 14012 12% / > > > > Has anyone run into this one? Is there a way of fixing it? I can't find > > anything on / that isn't supposed to be there, or is relatively large ;( > > rm -rf /var/tmp/install.* /var and /tmp are seperate file systems ... but, I do have softupdates enabled, like someone else suggested :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 21:18:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id 438D537B43C for ; Fri, 11 May 2001 21:18:33 -0700 (PDT) (envelope-from trevor@jpj.net) Received: from localhost (trevor@localhost) by blues.jpj.net (8.11.1/8.11.1) with ESMTP id f4C4ITL19960; Sat, 12 May 2001 00:18:29 -0400 (EDT) Date: Sat, 12 May 2001 00:18:29 -0400 (EDT) From: Trevor Johnson To: The Hermit Hacker Cc: Will Andrews , Subject: Re: make installworld runs out of space on / ... In-Reply-To: Message-ID: <20010512001633.P19380-100000@blues.jpj.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Removing unused files from /boot/modules can free up space. -- Trevor Johnson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 21:22: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.hub.org (SHW39-29.accesscable.net [24.138.39.29]) by hub.freebsd.org (Postfix) with ESMTP id 10D6937B43C for ; Fri, 11 May 2001 21:22:00 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.3/8.11.1) with ESMTP id f4C4Lx356092 for ; Sat, 12 May 2001 01:21:59 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Sat, 12 May 2001 01:21:59 -0300 (ADT) From: The Hermit Hacker To: Subject: nfsd/mountd problems? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG have checked /usr/src/UPDATING, and found: 20010319: portmap had changed name to rpcbind for maximum POLA in your current world. /etc/hosts.{allow,deny} needs changes. nfs and other rpc based programs that rely on portmapper will not work without updates to /etc/hosts.{allow,deny}. But my hosts.allow is up to date as of May 5th ... May 12 01:10:40 thelab nfsd:[6310]: rpcb_unset failed May 12 01:17:33 thelab nfsd:[20226]: rpcb_unset failed May 12 01:17:48 thelab mountd[21102]: can't delete exports for / May 12 01:17:48 thelab mountd[21102]: can't delete exports for /home May 12 01:17:48 thelab mountd[21102]: can't delete exports for /tmp May 12 01:17:48 thelab mountd[21102]: can't delete exports for /usr May 12 01:17:48 thelab mountd[21102]: can't delete exports for /usr/local May 12 01:17:48 thelab mountd[21102]: can't delete exports for /var May 12 01:17:48 thelab mountd[21105]: can't register UDP RPCMNT_VER1 service May 12 01:17:48 thelab mountd[21105]: can't register UDP RPCMNT_VER3 service May 12 01:17:48 thelab mountd[21105]: can't register TCP RPCMNT_VER1 service May 12 01:17:48 thelab mountd[21105]: can't register TCP RPCMNT_VER3 service May 12 01:17:48 thelab mountd[21105]: can't register UDP6 RPCMNT_VER1 service May 12 01:17:48 thelab mountd[21105]: can't register UDP6 RPCMNT_VER3 service May 12 01:17:48 thelab mountd[21105]: can't register TCP6 RPCMNT_VER1 service May 12 01:17:48 thelab mountd[21105]: can't register TCP6 RPCMNT_VER3 service May 12 01:17:48 thelab mountd[21105]: could not create any services Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 21:44:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from draco.over-yonder.net (draco.over-yonder.net [198.78.58.61]) by hub.freebsd.org (Postfix) with ESMTP id 5D48F37B43C for ; Fri, 11 May 2001 21:44:23 -0700 (PDT) (envelope-from fullermd@over-yonder.net) Received: by draco.over-yonder.net (Postfix, from userid 100) id B2A1C62D0A; Fri, 11 May 2001 23:44:17 -0500 (CDT) Date: Fri, 11 May 2001 23:44:17 -0500 From: "Matthew D. Fuller" To: current@freebsd.org Subject: -CURRENT b0rked? Message-ID: <20010511234417.L54596@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Editor: vi X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On several attempts to build world, I'm getting ths same error: In file included from /usr/src/usr.sbin/sysinstall/keymap.c:40: keymap.h:3606: `keymap_ua_koi8_u_shift_alt' undeclared here (not in a function) keymap.h:3606: initializer element is not constant keymap.h:3606: (near initialization for `keymapInfos[21].map') at which point the build bombs out. This is with completely clean src/ and obj/ each time, and I haven't seen any commits to the file in the last 24+ hours. OTOH, I haven't seen a peep about this from anybody else, so am I just hitting some sort of really weird condition that nobody else has ever heard of here, or is nobody else building -CURRENT right now? -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 21:54:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.6.200.230]) by hub.freebsd.org (Postfix) with ESMTP id BB0D937B43C for ; Fri, 11 May 2001 21:54:13 -0700 (PDT) (envelope-from mdharnois@home.com) Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id 5B1B314A1C; Fri, 11 May 2001 23:54:53 -0500 (CDT) To: freebsd-current@freebsd.org Subject: modules broken at nge Keywords: nge,dev,usr,sys,src,modules From: Michael Harnois Date: 11 May 2001 23:54:53 -0500 Message-ID: <86d79fgo9u.fsf@mharnois.workgroup.net> Lines: 11 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.5 (anise) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/dev -I@/../include /usr/src/sys/modules/nge/../../dev/nge/if_nge.c /usr/src/sys/modules/nge/../../dev/nge/if_nge.c:119: pci/if_ngereg.h: No such file or directory /usr/src/sys/modules/nge/../../dev/nge/if_nge.c:124: miibus_if.h: No such file or directory mkdep: compile failed -- Michael D. Harnois mdharnois@home.com Redeemer Lutheran Church Washburn, Iowa Never, "for the sake of peace and quiet," deny your own experience or convictions. -- Dag Hammarskjold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 11 22:48: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from kalaid.f2f.com.ua (kalaid.f2f.com.ua [62.149.0.33]) by hub.freebsd.org (Postfix) with ESMTP id 21C8937B423 for ; Fri, 11 May 2001 22:48:02 -0700 (PDT) (envelope-from sobomax@mail-in.net) Received: from Mail-In.Net (borey.f2f.com.ua [62.149.0.24]) by kalaid.f2f.com.ua (8.11.3/8.11.1) with ESMTP id f4C5nY098854; Sat, 12 May 2001 08:49:37 +0300 (EEST) (envelope-from sobomax@mail-in.net) Received: from notebook.vega.com (das0-l118.uic-in.net [212.35.189.245]) by Mail-In.Net (8.11.3/8.H.Z) with ESMTP id f4C5mM076847; Sat, 12 May 2001 08:48:24 +0300 (EEST) Date: Sat, 12 May 2001 08:48:24 +0300 (EEST) Message-Id: <200105120548.f4C5mM076847@Mail-In.Net> To: fullermd@over-yonder.net, current@FreeBSD.ORG From: Maxim Sobolev Reply-To: sobomax@FreeBSD.ORG Subject: =?ISO-8859-1?Q?Re:_-CURRENT_b0rked=3F?= X-Mailer: Pygmy (v0.5.7) In-Reply-To: <20010511234417.L54596@over-yonder.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 May 2001 23:44:17 -0500, Matthew D. Fuller wrote: > On several attempts to build world, I'm getting ths same error: > > In file included from /usr/src/usr.sbin/sysinstall/keymap.c:40: > keymap.h:3606: `keymap_ua_koi8_u_shift_alt' undeclared here (not in a > function) > keymap.h:3606: initializer element is not constant > keymap.h:3606: (near initialization for `keymapInfos[21].map') > > at which point the build bombs out. This is with completely clean src/ > and obj/ each time, and I haven't seen any commits to the file in the > last 24+ hours. OTOH, I haven't seen a peep about this from anybody > else, so am I just hitting some sort of really weird condition that > nobody else has ever heard of here, or is nobody else building -CURRENT > right now? It is unlikely that nobody else is doing buildworld. Please try to do the following and restart buildworld: # cd /usr/src/share/syscons/keymaps && make all install cleandir -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 2:21:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from kalaid.f2f.com.ua (kalaid.f2f.com.ua [62.149.0.33]) by hub.freebsd.org (Postfix) with ESMTP id 667BC37B43E for ; Sat, 12 May 2001 02:21:24 -0700 (PDT) (envelope-from sobomax@mail-in.net) Received: from Mail-In.Net (borey.f2f.com.ua [62.149.0.24]) by kalaid.f2f.com.ua (8.11.3/8.11.1) with ESMTP id f4C9N7001481; Sat, 12 May 2001 12:23:10 +0300 (EEST) (envelope-from sobomax@mail-in.net) Received: from notebook.vega.com (dialup15-27.iptelecom.net.ua [212.9.229.155]) by Mail-In.Net (8.11.3/8.H.Z) with ESMTP id f4C9Lr081057; Sat, 12 May 2001 12:21:55 +0300 (EEST) Date: Sat, 12 May 2001 12:21:55 +0300 (EEST) Message-Id: <200105120921.f4C9Lr081057@Mail-In.Net> To: fullermd@over-yonder.net, current@FreeBSD.ORG From: Maxim Sobolev Reply-To: sobomax@FreeBSD.ORG Subject: =?ISO-8859-1?Q?Re:_Re:_-CURRENT_b0rked=3F?= X-Mailer: Pygmy (v0.5.7) In-Reply-To: <200105120548.f4C5mM076847@Mail-In.Net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 12 May 2001 08:48:24 +0300 (EEST), Maxim Sobolev wrote: > On Fri, 11 May 2001 23:44:17 -0500, Matthew D. Fuller wrote: > > On several attempts to build world, I'm getting ths same error: > > > > In file included from /usr/src/usr.sbin/sysinstall/keymap.c:40: > > keymap.h:3606: `keymap_ua_koi8_u_shift_alt' undeclared here (not in a > > function) > > keymap.h:3606: initializer element is not constant > > keymap.h:3606: (near initialization for `keymapInfos[21].map') > > > > at which point the build bombs out. This is with completely clean src/ > > and obj/ each time, and I haven't seen any commits to the file in the > > last 24+ hours. OTOH, I haven't seen a peep about this from anybody > > else, so am I just hitting some sort of really weird condition that > > nobody else has ever heard of here, or is nobody else building -CURRENT > > right now? > > It is unlikely that nobody else is doing buildworld. Please > try to do the following and restart buildworld: > # cd /usr/src/share/syscons/keymaps && make all install cleandir It seems that sysinstall(8) was not fully integrated into buildworld - it depends on content of /usr/share/syscons/keymaps, while it shouldn't. I've just committed a patch that should fix this problem. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 4:39:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id ACE2B37B423 for ; Sat, 12 May 2001 04:39:46 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0001.cvx21-bradley.dialup.earthlink.net [209.179.192.1]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id HAA02288; Sat, 12 May 2001 07:39:41 -0400 (EDT) Message-ID: <3AFD2113.9BEA7D7B@mindspring.com> Date: Sat, 12 May 2001 04:40:03 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: jack Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: OT: Was Re: make installworld runs out of space on / ... References: <20010511235317.A59947-100000@germanium.xtalwind.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A Microsoft Certified Systems Engineer is to computing what > a McDonalds Certified Food Specialist is to fine cuisine. An engineer without a Microsoft certification is like a statue without pigeons... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 5:12: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from comm.uni-svishtov.bg (ns.uni-svishtov.bg [193.68.172.1]) by hub.freebsd.org (Postfix) with ESMTP id 6C6B537B43C for ; Sat, 12 May 2001 05:11:57 -0700 (PDT) (envelope-from rvasilev@uni-svishtov.bg) Received: from grinch.uni-svishtov.bg (root@grinch.uni-svishtov.bg [193.68.172.9]) by comm.uni-svishtov.bg (8.9.3/8.9.3) with ESMTP id PAA11243 for ; Sat, 12 May 2001 15:11:53 +0300 (EEST) Received: from uni-svishtov.bg (deckland.uni-svishtov.bg [193.68.173.82]) by grinch.uni-svishtov.bg (8.9.3/8.9.1) with ESMTP id PAA19504 for ; Sat, 12 May 2001 15:11:52 +0300 (EEST) Message-ID: <3AFD288F.62939EB8@uni-svishtov.bg> Date: Sat, 12 May 2001 15:11:59 +0300 From: Radoslav Vasilev Organization: Academic Computer Center -Tsenov Academy of Economics X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.3-STABLE i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: -current broken at /usr/src/usr.sbin/sysinstall/keymap.c Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is supposed to be a reply to Mathew D. Fuller Yeah, I've the same problem with building the -current, so you aren't alone.Unfortunelly, I haven't managed to sort it out yes. I just wonder what's your start point, because I'm trying to update an 4.3STABLE machine, what about yours? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 6:42:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.org.ru (sweet.etrust.ru [194.84.67.5]) by hub.freebsd.org (Postfix) with ESMTP id 8E0AB37B424 for ; Sat, 12 May 2001 06:42:03 -0700 (PDT) (envelope-from osa@freebsd.org.ru) Received: by freebsd.org.ru (Postfix, from userid 1000) id 6D5D424D; Sat, 12 May 2001 17:42:01 +0400 (MSD) Date: Sat, 12 May 2001 17:42:01 +0400 From: "Sergey A. Osokin" To: Poul-Henning Kamp Cc: freebsd-current@freebsd.org Subject: Re: new function for libdevstat Message-ID: <20010512174201.A58243@freebsd.org.ru> Reply-To: osa@FreeBSD.org.ru References: <20010511193907.A49316@freebsd.org.ru> <85381.989602550@critter> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="9amGYk9869ThD9tj" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <85381.989602550@critter>; from phk@critter.freebsd.dk on Fri, May 11, 2001 at 07:35:50PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, May 11, 2001 at 07:35:50PM +0200, Poul-Henning Kamp wrote: > In message <20010511193907.A49316@freebsd.org.ru>, "Sergey A. Osokin" writes: > > >Hello. > >2 monthes ago I talked in -current about new features for libdevstat. > >Here is a new function, which calculate more statistics then > >existing compute_stats(). (compute_stats() calculate only average > >results, not read/write results). > >Please see my first step. Comments are welcome. > > I really don't think this is the way... > > I would far rather see: > > enum DEVSTAT_METRIC { > DEVSTAT_BYTES, > DEVSTAT_BYTES_READ, > DEVSTAT_BYTES_WRITE, > ... > } > > int > devstat_compute_statistics( > struct devstat *current, > struct devstat *previous, > enum DEVSTAT_METRIC metric, > double *destination); > > Since that can be extended with new metrics without changing > the ABI... OK. Please see attachment. Thanks. -- Rgdz, /"\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN osa@freebsd.org.ru X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="newstat2.c" enum DEVSTAT_METRIC { DEVSTAT_TOTAL_BYTES, DEVSTAT_TOTAL_BYTES_READ, DEVSTAT_TOTAL_BYTES_WRITE, DEVSTAT_TOTAL_TRANSFERS, DEVSTAT_TOTAL_TRANSFERS_READ, DEVSTAT_TOTAL_TRANSFERS_WRITE, DEVSTAT_TOTAL_TRANSFERS_OTHER, DEVSTAT_TOTAL_BLOCKS, DEVSTAT_TOTAL_BLOCKS_READ, DEVSTAT_TOTAL_BLOCKS_WRITE, DEVSTAT_KB_PER_TRANSFER, DEVSTAT_KB_PER_TRANSFER_READ, DEVSTAT_KB_PER_TRANSFER_WRITE, DEVSTAT_TRANSFERS_PER_SECOND, DEVSTAT_TRANSFERS_PER_SECOND_READ, DEVSTAT_TRANSFERS_PER_SECOND_WRITE, DEVSTAT_TRANSFERS_PER_SECOND_OTHER, DEVSTAT_MB_PER_SECOND, DEVSTAT_MB_PER_SECOND_READ, DEVSTAT_MB_PER_SECOND_WRITE, DEVSTAT_BLOCKS_PER_SECOND, DEVSTAT_BLOCKS_PER_SECOND_READ, DEVSTAT_BLOCKS_PER_SECOND_WRITE, DEVSTAT_MS_PER_TRANSACTION, DEVSTAT_MS_PER_TRANSACTION_READ, DEVSTAT_MS_PER_TRANSACTION_WRITE }; int devstat_compute_statistics(struct devstat *current, struct devstat *previous, long double etime, enum DEVSTAT_METRIC metric, long double *destination) { u_int64_t totalbytes, totalbytes_read, totalbytes_write; u_int64_t totaltransfers, totaltransfers_read, totaltransfers_write, totaltransfers_other; u_int64_t totalblocks, totalblocks_read, totalblocks_write; char *func_name = "devstat_compute_statistics"; /* * current is the only mandatory field. */ if (current == NULL) { sprintf(devstat_errbuf, "%s: current stats structure was NULL", func_name); return(-1); } totalbytes_read = current->bytes_read - ((previous) ? previous->bytes_read : 0); if (metric == DEVSTAT_TOTAL_BYTES_READ) { *destination = totalbytes_read; return 0; } totalbytes_write = current->bytes_written - ((previous) ? previous->bytes_written : 0); if (metric == DEVSTAT_TOTAL_BYTES_WRITE) { *destination = totalbytes_write; return 0; } /* totalbytes = (current->bytes_written + current->bytes_read) - ((previous) ? (previous->bytes_written + previous->bytes_read) : 0); */ totalbytes = totalbytes_read + totalbytes_write; if (metric == DEVSTAT_TOTAL_BYTES) { *destination = totalbytes; return 0; } totaltransfers_read = current->num_reads - ((previous) ? (previous->num_reads) : 0); if (metric == DEVSTAT_TOTAL_TRANSFERS_READ) { *destination = totaltransfers_read; return 0; } totaltransfers_write = current->num_writes - ((previous) ? (previous->num_writes) : 0); if (metric == DEVSTAT_TOTAL_TRANSFERS_WRITE) { *destination = totaltransfers_write; return 0; } totaltransfers_other = current->num_other - ((previous) ? (previous->num_other) : 0); if (metric == DEVSTAT_TOTAL_TRANSFERS_OTHER) { *destination = totaltransfers_other; return 0; } /* totaltransfers = (current->num_reads + current->num_writes + current->num_other) - ((previous) ? (previous->num_reads + previous->num_writes + previous->num_other) : 0); */ totaltransfers = totaltransfers_read + totaltransfers_write + totaltransfers_other; if (metric == DEVSTAT_TOTAL_TRANSFERS) { *destination = totaltransfers; return 0; } if (metric == DEVSTAT_TRANSFERS_PER_SECOND) { if (etime > 0.0) { *destination = totaltransfers; *destination /= etime; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_TRANSFERS_PER_SECOND_READ) { if (etime > 0.0) { *destination = totaltransfers_read; *destination /= etime; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_TRANSFERS_PER_SECOND_WRITE) { if (etime > 0.0) { *destination = totaltransfers_write; *destination /= etime; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_TRANSFERS_PER_SECOND_OTHER) { if (etime > 0.0) { *destination = totaltransfers_other; *destination /= etime; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_KB_PER_TRANSFER) { *destination = totalbytes; *destination /= 1024; if (totaltransfers > 0) { *destination /= totaltransfers; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_KB_PER_TRANSFER_READ) { *destination = totalbytes_read; *destination /= 1024; if (totaltransfers_read > 0) { *destination /= totaltransfers_read; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_KB_PER_TRANSFER_WRITE) { *destination = totalbytes_write; *destination /= 1024; if (totaltransfers_write > 0) { *destination /= totaltransfers_write; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_MB_PER_SECOND) { *destination = totalbytes; *destination /= 1024 * 1024; if (etime > 0.0) { *destination /= etime; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_MB_PER_SECOND_READ) { *destination = totalbytes_read; *destination /= 1024 * 1024; if (etime > 0.0) { *destination /= etime; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_MB_PER_SECOND_WRITE) { *destination = totalbytes_write; *destination /= 1024 * 1024; if (etime > 0.0) { *destination /= etime; return 0; } else { *destination = 0.0; return 0; } } totalblocks = totalbytes; totalblocks_read = totalbytes_read; totalblocks_write = totalbytes_write; if (current->block_size > 0) { totalblocks /= current->block_size; totalblocks_read /= current->block_size; totalblocks_write /= current->block_size; } else { totalblocks /= 512; totalblocks_read /= 512; totalblocks_write /= 512; } if (metric == DEVSTAT_TOTAL_BLOCKS) { *destination = totalblocks; return 0; } if (metric == DEVSTAT_TOTAL_BLOCKS_READ) { *destination = totalblocks_read; return 0; } if (metric == DEVSTAT_TOTAL_BLOCKS_WRITE) { *destination = totalblocks_write; return 0; } if (metric == DEVSTAT_BLOCKS_PER_SECOND) { *destination = totalblocks; if (etime > 0.0) { *destination /= etime; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_BLOCKS_PER_SECOND_READ) { *destination = totalblocks_read; if (etime > 0.0) { *destination /= etime; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_BLOCKS_PER_SECOND_WRITE) { *destination = totalblocks_write; if (etime > 0.0) { *destination /= etime; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_MS_PER_TRANSACTION) { if (totaltransfers > 0) { *destination = etime; *destination /= totaltransfers; *destination *= 1000; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_MS_PER_TRANSACTION_READ) { if (totaltransfers_read > 0) { *destination = etime; *destination /= totaltransfers_read; *destination *= 1000; return 0; } else { *destination = 0.0; return 0; } } if (metric == DEVSTAT_MS_PER_TRANSACTION_WRITE) { if (totaltransfers_write > 0) { *destination = etime; *destination /= totaltransfers_write; *destination *= 1000; return 0; } else { *destination = 0.0; return 0; } } return(0); } --9amGYk9869ThD9tj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 10:25:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 8D1A737B423; Sat, 12 May 2001 10:25:15 -0700 (PDT) (envelope-from DougB@DougBarton.net) Received: from DougBarton.net (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id KAA61128; Sat, 12 May 2001 10:25:08 -0700 (PDT) (envelope-from DougB@DougBarton.net) Message-ID: <3AFD71F3.905EC08C@DougBarton.net> Date: Sat, 12 May 2001 10:25:07 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Kirk McKusick , fs@FreeBSD.org, current@FreeBSD.org Subject: Re: [kris@obsecurity.org: Re: cvs commit: src/etc rc] References: <20010511121020.B31232@sunbay.com> <200105111916.MAA16255@beastie.mckusick.com> <20010512023602.A40616@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Fri, May 11, 2001 at 12:16:18PM -0700, Kirk McKusick wrote: > > > At the moment there is no provision for notifying the system > > administrator since the output of fsck is simply being sent > > to the `logger' program (which by default will put the messages > > into /var/log/messages). You can feed 'logger' the -p option with a facility.level pair that will let syslogd decide how to handle it, although I agree that fsck should really use syslog() instead. > > It would be possible to add a syslog > > (or wall) call to the fsck program itself. Another alternative > > would be to have fsck forcibly downgrade the offending filesystem > > to read-only mode. However, if it were say the /var filesystem, > > the system would fall apart pretty quickly. I am open to > > suggestions on how best to proceed. > > Working under the assumption that the only time fsck is likely to fail > in this manner is if there are FS errors which can't be resolved in > the background, and which may result in further FS damage if left > uncorrected, the best option seems to be to take some action which > prevents this damage. > > The best series of actions might be the following: > > 1) Downgrade the FS to readonly mode. This is reasonable, and IMO even more important for an fs like /var that is likely to be written to early in the life of the system. > 2) syslog(LOG_EMERG, "Unrecoverable error in background check of %s, > FS downgraded to readonly mode. Reboot in 60 seconds to attempt to > repair the error. Kill PID %d now to abort.", ...) > > 3) Reboot in 60 seconds I'm not sure that always rebooting is a good idea however. This may be more effort than it's worth, but what about a flag in fstab that indicates something to the effect of, "This partition is essential to the system, reboot automatically to fix it?" For instance, if my /usr/obj partition comes up dirty, I can deal with it by hand, whereas if something important is hosed, I'd like the system to deal with it more drastically. We could default it to on, and let people load the foot-shooting gun themselves if desired. -- I need someone really bad. Are you really bad? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 11:43:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from moutvdom00.kundenserver.de (moutvdom00.kundenserver.de [195.20.224.149]) by hub.freebsd.org (Postfix) with ESMTP id C457337B629 for ; Sat, 12 May 2001 11:43:45 -0700 (PDT) (envelope-from mail-service@friedhof2000.de) Received: from [195.20.224.220] (helo=mrvdom04.kundenserver.de) by moutvdom00.kundenserver.de with esmtp (Exim 2.12 #2) id 14yeMi-0002mM-00 for freebsd-current@freebsd.org; Sat, 12 May 2001 20:43:44 +0200 Received: from pd904dd79.dip.t-dialin.net ([217.4.221.121] helo=celeron) by mrvdom04.kundenserver.de with smtp (Exim 2.12 #2) id 14yeMW-0000bN-01 for freebsd-current@freebsd.org; Sat, 12 May 2001 20:43:32 +0200 From: Mail-Service To: freebsd-current@freebsd.org Subject: Jetzt gewinnen, in über 100 Gewinnspielen! Reply-To: mail-service@friedhof2000.de MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: BulkMailer 2.0 (www.kroll-software.de) Message-Id: Date: Sat, 12 May 2001 20:43:32 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Falls unerwünscht, bitte sofort löschen! Gewinn24.de meldet Sie jeden Monat bei über 100 der besten Gewinnspiele im Internet an. Sie sparen mit Gewinn24.de eine Menge Zeit und Geld. Für maximal 2,- DM pro Monat sind Sie dabei und haben jeden Monat Gewinnchancen auf viele tolle Preise im Gesamtwert von mehreren Millionen DM. http://www.Gewinn24.de/index.php3?partner=7294 *Bei Beschwerden bitte an alex-albert@01019freenet.de * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 14:15:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id 83B9037B423 for ; Sat, 12 May 2001 14:15:15 -0700 (PDT) (envelope-from nsouch@fr.alcove.com) Received: from nsouch by smtp.alcove.fr with local (Exim 3.12 #1 (Debian)) id 14ygjJ-00056R-00 for ; Sat, 12 May 2001 23:15:13 +0200 Date: Sat, 12 May 2001 23:15:13 +0200 From: Nicolas Souchu To: freebsd-current@freebsd.org Subject: [HEADSUP] iicbus/smbus testers before major commit Message-ID: <20010512231513.A19577@ontario.alcove-fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Ecom?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I finally have an update for the iicbus/smbus in -current. See http://people.freebsd.org/~nsouch/iicbus.html - April 2001 The major improvments are: - loadable / unloadable by means of modules - major cleanup of bus framework - support for the VIA 82C586 chipset - support for AMD 760 chipset (needs testing) By the way, I propose to remove the i386/isa/pcf.c iicbus/if_ic.c and ppbus/lpbb.c files from the tree since I can't do non-regression tests anymore for it. They could be maintained on a personal page instead... Tanks for you feedbacks. -- Nicolas.Souchu@fr.alcove.com Alcôve - Open Source Software Engineer - http://www.alcove.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 17:36:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from draco.over-yonder.net (draco.over-yonder.net [198.78.58.61]) by hub.freebsd.org (Postfix) with ESMTP id C862137B424; Sat, 12 May 2001 17:36:21 -0700 (PDT) (envelope-from fullermd@over-yonder.net) Received: by draco.over-yonder.net (Postfix, from userid 100) id 603CE62D0A; Sat, 12 May 2001 19:36:21 -0500 (CDT) Date: Sat, 12 May 2001 19:36:21 -0500 From: "Matthew D. Fuller" To: sobomax@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: Re: -CURRENT b0rked? Message-ID: <20010512193621.Q54596@over-yonder.net> References: <200105120548.f4C5mM076847@Mail-In.Net> <200105120921.f4C9Lr081057@Mail-In.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105120921.f4C9Lr081057@Mail-In.Net>; from sobomax@mail-in.net on Sat, May 12, 2001 at 12:21:55PM +0300 X-Editor: vi X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 12, 2001 at 12:21:55PM +0300 I heard the voice of Maxim Sobolev, and lo! it spake thus: > > It seems that sysinstall(8) was not fully integrated into > buildworld - it depends on content of /usr/share/syscons/keymaps, > while it shouldn't. > > I've just committed a patch that should fix this problem. Hoo, here I come to make your life a living hell once more... In file included from /usr/src/usr.sbin/sysinstall/keymap.c:40: keymap.h:2: `keymap_be_iso' undeclared here (not in a function) keymap.h:2: initializer element is not constant keymap.h:2: (near initialization for `keymapInfos[0].map') keymap.h:3: `keymap_br275_iso' undeclared here (not in a function) keymap.h:3: initializer element is not constant keymap.h:3: (near initialization for `keymapInfos[1].map') -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 20: 9: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from dougal.workpc.tds.net (dougal.workpc.tds.net [204.246.4.101]) by hub.freebsd.org (Postfix) with ESMTP id 88A0C37B443; Sat, 12 May 2001 20:09:03 -0700 (PDT) (envelope-from usrkkw@dougal.workpc.tds.net) Received: (from usrkkw@localhost) by dougal.workpc.tds.net (8.11.3/8.11.1) id f4D37Kf10673; Sat, 12 May 2001 22:07:20 -0500 (CDT) (envelope-from usrkkw) Date: Sat, 12 May 2001 22:07:20 -0500 From: Ken Wills To: "Matthew D. Fuller" Cc: sobomax@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Re: -CURRENT b0rked? Message-ID: <20010512220720.A10483@dougal.workpc.tds.net> References: <200105120548.f4C5mM076847@Mail-In.Net> <200105120921.f4C9Lr081057@Mail-In.Net> <20010512193621.Q54596@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010512193621.Q54596@over-yonder.net>; from fullermd@over-yonder.net on Sat, May 12, 2001 at 07:36:21PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew D. Fuller [010512 19:35]: > On Sat, May 12, 2001 at 12:21:55PM +0300 I heard the voice of > Maxim Sobolev, and lo! it spake thus: > > > > It seems that sysinstall(8) was not fully integrated into > > buildworld - it depends on content of /usr/share/syscons/keymaps, > > while it shouldn't. > > > > I've just committed a patch that should fix this problem. > > Hoo, here I come to make your life a living hell once more... > > In file included from /usr/src/usr.sbin/sysinstall/keymap.c:40: > keymap.h:2: `keymap_be_iso' undeclared here (not in a function) > keymap.h:2: initializer element is not constant > keymap.h:2: (near initialization for `keymapInfos[0].map') > keymap.h:3: `keymap_br275_iso' undeclared here (not in a function) > keymap.h:3: initializer element is not constant > keymap.h:3: (near initialization for `keymapInfos[1].map') > Deleting keymap.h (autogenerated, in obj/* somewhere, I forget), and restarting the build got me past this. K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 20:11:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from draco.over-yonder.net (draco.over-yonder.net [198.78.58.61]) by hub.freebsd.org (Postfix) with ESMTP id 3E77237B423; Sat, 12 May 2001 20:11:26 -0700 (PDT) (envelope-from fullermd@over-yonder.net) Received: by draco.over-yonder.net (Postfix, from userid 100) id E7FC562D0A; Sat, 12 May 2001 22:11:25 -0500 (CDT) Date: Sat, 12 May 2001 22:11:25 -0500 From: "Matthew D. Fuller" To: Ken Wills Cc: sobomax@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Re: -CURRENT b0rked? Message-ID: <20010512221125.R54596@over-yonder.net> References: <200105120548.f4C5mM076847@Mail-In.Net> <200105120921.f4C9Lr081057@Mail-In.Net> <20010512193621.Q54596@over-yonder.net> <20010512220720.A10483@dougal.workpc.tds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010512220720.A10483@dougal.workpc.tds.net>; from kenwills@tds.net on Sat, May 12, 2001 at 10:07:20PM -0500 X-Editor: vi X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 12, 2001 at 10:07:20PM -0500 I heard the voice of Ken Wills, and lo! it spake thus: > > Deleting keymap.h (autogenerated, in obj/* somewhere, I forget), and restarting > the build got me past this. I start all my builds with an empty /usr/obj and a freshly co'd /usr/src. Re-newfs'ing everything here and trying again, just to make doubly sure now, but I'm pretty sure I cleaned up as always. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 20:23:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.wesleyan.edu (smtp.wesleyan.edu [129.133.1.61]) by hub.freebsd.org (Postfix) with ESMTP id 281FB37B423 for ; Sat, 12 May 2001 20:23:25 -0700 (PDT) (envelope-from vsavichev@mail.wesleyan.edu) Received: from wesleyan.edu (ariel.phys.wesleyan.edu [129.133.71.143]) by mail.wesleyan.edu (8.9.3/8.9.1) with ESMTP id XAA24575; Sat, 12 May 2001 23:23:23 -0400 (EDT) Message-Id: <200105130323.XAA24575@mail.wesleyan.edu> Date: Sat, 12 May 2001 23:24:27 -0400 From: Vladimir Savichev X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: freebsd-current@freebsd.org, mdharnois@home.com Subject: Re: modules broken at nge Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it's apparently fixed, check it in cvs-all May 12 Bill Paul cvs commit: src/sys/modules/nge Makefile src/sys/dev -- Vlad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 21:27: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 684F037B43E for ; Sat, 12 May 2001 21:27:02 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f4D4Qm170735 for freebsd-current@FreeBSD.ORG; Sat, 12 May 2001 21:26:48 -0700 (PDT) Date: Sat, 12 May 2001 21:26:48 -0700 (PDT) From: David Wolfskill Message-Id: <200105130426.f4D4Qm170735@bunrab.catwhisker.org> To: freebsd-current@FreeBSD.ORG Subject: Re: modules broken at nge In-Reply-To: <200105130323.XAA24575@mail.wesleyan.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sat, 12 May 2001 23:24:27 -0400 >From: Vladimir Savichev >it's apparently fixed, check it in cvs-all >May 12 Bill Paul cvs commit: src/sys/modules/nge Makefile src/sys/dev Yes; applying that pair of patches allows today's -CURRENT to build -- and run: I'm running it now: FreeBSD dhcp-140.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #62: Sat May 12 14:01:53 PDT 2001 root@dhcp-140.catwhisker.org:/common/C/obj/usr/src/sys/LAPTOP_30W i386 Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 22:40:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 7A14537B446 for ; Sat, 12 May 2001 22:40:39 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f4D5eZl71004 for current@freebsd.org; Sat, 12 May 2001 22:40:35 -0700 (PDT) Date: Sat, 12 May 2001 22:40:35 -0700 (PDT) From: David Wolfskill Message-Id: <200105130540.f4D5eZl71004@bunrab.catwhisker.org> To: current@freebsd.org Subject: ssh public key auth. incompatible between 2.3.0 vs. 2.9? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK; there's something about the (relatively) new ssh (2.9) in -CURRENT I'm not understanding. I have hunted around for some clues (via man pages & the like), but it could well be that I'm still failing to notice something -- quite possibly something that should be obvious to even me -- and I welcome a clue. Basically, the setup I use in -STABLE, where I'm able to use my public/private key pair for authentication, is not working in -CURRENT. (ssh in -CURRENT is reverting to password authentication.) On the machine (my laptop, where I have been tracking both -STABLE and -CURRENT daily for the past 1.5 months or so, and each environment has its own / and /usr, but /usr/local, /var, and my home directory are common -- as is the local CVS respository), I have it set up to start X (4.0.3) via xdm. Thus, my ~/.xsession script is run when I login. The first part of that script reads: #! /bin/csh if { test -x `which ssh-askpass` } then eval `ssh-agent` ssh-add set ssh_test = `ssh-add -l` || exit 1 echo "$ssh_test" | grep '@' >/dev/null if ( $? ) then echo "What part of 'Need passphrase' don't you understand?" exit 2 endif endif set in_xdm = "1" source ~/.cshrc .... (I do *not* normally use csh for script-writing. However, since I use it (well, tcsh) as my normal shell, there are some advantages to having the ssh-agent stuff use csh semantics. And it allows a bit more consistency forfiguring out things like my customized execution path. And prior to ssh .29 in -CURRENT, this was also working in -CURRENT... but it took a couple of days for things to get to a reasonably steady state or ssh 2.9 in -CURRENT, which is why I didn't write about this earlier: I figured it's sufficiently messy that it was a little premature to do that just yet. But I certainly want folks to be aware of what is going on, now that I've started seeing requested to MFC ssh 2.9.) Now, as noted, my home directory is common between the 2 environments, so I have a high degree of confidence that the files look the same from either environment. And I built the first -CURRENT environment from FreeBSD 4.3-STABLE near the 2nd week of March; that part's been tracking -CURRENT since... and this was after /etc/ssh had been populated originally, so the host keys are the same. Here's /etc/ssh on the -STABLE side: dhcp-140[1] ls -la /S1/etc/ssh total 37 drwxr-xr-x 2 root wheel 512 May 3 06:57 . drwxr-xr-x 17 root wheel 2560 May 12 07:07 .. -rw-r--r-- 1 root wheel 26346 May 3 06:57 primes -rw-r--r-- 1 root wheel 976 Mar 6 07:46 ssh_config -rw------- 1 root wheel 668 Mar 6 09:33 ssh_host_dsa_key -rw-r--r-- 1 root wheel 595 Mar 6 09:33 ssh_host_dsa_key.pub -rw------- 1 root wheel 520 Mar 6 09:33 ssh_host_key -rw-r--r-- 1 root wheel 324 Mar 6 09:33 ssh_host_key.pub -rw-r--r-- 1 root wheel 1480 Mar 6 07:46 sshd_config dhcp-140[2] and the -CURRENT side: dhcp-140[2] ls -la /etc/ssh total 39 drwxr-xr-x 2 root wheel 512 May 9 10:18 . drwxr-xr-x 16 root wheel 2560 May 11 09:56 .. -rw-r--r-- 1 root wheel 26346 Mar 27 08:01 primes -rw-r--r-- 1 root wheel 909 Mar 7 21:29 ssh_config -rw------- 1 root wheel 668 Mar 6 09:33 ssh_host_dsa_key -rw-r--r-- 1 root wheel 595 Mar 6 09:33 ssh_host_dsa_key.pub -rw------- 1 root wheel 520 Mar 6 09:33 ssh_host_key -rw-r--r-- 1 root wheel 324 Mar 6 09:33 ssh_host_key.pub -rw------- 1 root wheel 529 May 9 10:18 ssh_host_rsa_key -rw-r--r-- 1 root wheel 333 May 9 10:18 ssh_host_rsa_key.pub -rw-r--r-- 1 root wheel 1776 May 6 09:41 sshd_config dhcp-140[3] and in particular: dhcp-140[3] sudo cmp {/S1,}/etc/ssh/ssh_host_key Password: dhcp-140[4] sudo cmp {/S1,}/etc/ssh/ssh_host_key.pub dhcp-140[5] sudo cmp {/S1,}/etc/ssh/ssh_config /S1/etc/ssh/ssh_config /etc/ssh/ssh_config differ: char 196, line 5 dhcp-140[6] sudo diff -u {/S1,}/etc/ssh/ssh_config --- /S1/etc/ssh/ssh_config Tue Mar 6 07:46:45 2001 +++ /etc/ssh/ssh_config Wed Mar 7 21:29:09 2001 @@ -2,7 +2,7 @@ # defaults for users, and the values can be changed in per-user configuration # files or on the command line. # -# $FreeBSD: src/crypto/openssh/ssh_config,v 1.6 2000/09/10 09:35:38 kris Exp $ +# $FreeBSD$ # Configuration data is parsed as follows: # 1. command line options dhcp-140[7] OK; I *think* that's a difference that ought not be relevant to the issue I'm seeing.... :-} [Sorry if things get disjointed at this point. My laptop re-booted; as far as I know, I had just hit the "A" key. The /var filesystem needed a manual fsck, which I did, then I re-booted. It seems to have done Kirk's "background fsck" magic OK; I HUPped the process (which was still hanging around on the machine where I was composing this note) and recovered the buffer up to this parenthetical comment. dhw] So, I tried an experiment to illustrate the issue. I booted -CURRENT, and (under script) issued an "ssh -v bunrab". I then booted -STABLE, and did it again (using a different filename). I then edited the script files: I removed all of the ^Ms, and I then (in order to reduce the number of irrelevant mis-matches) changed all of the "^debug: " lines in the -STABLE file to read "^debug1: " instead. (License, I know. I'm happy to provide complete files, but this is quite long enough as it is.) Here's the diff output: --- ssh-stable Sat May 12 19:45:54 2001 +++ ssh-current Sat May 12 19:43:03 2001 @@ -1,34 +1,61 @@ -Script started on Sat May 12 19:35:12 2001 +Script started on Sat May 12 19:40:40 2001 dhcp-140[1] ssh -v bunrab -SSH Version OpenSSH_2.3.0 green@FreeBSD.org 20010321, protocol versions 1.5/2.0. -Compiled with SSL (0x0090600f). +OpenSSH_2.9 green@FreeBSD.org 20010503, SSH protocols 1.5/2.0, OpenSSL 0x00906010 debug1: Reading configuration data /etc/ssh/ssh_config +debug1: Rhosts Authentication disabled, originating port will not be trusted. +debug1: restore_uid debug1: ssh_connect: getuid 1001 geteuid 1001 anon 1 debug1: Connecting to bunrab.catwhisker.org [172.16.8.11] port 22. +debug1: temporarily_use_uid: 1001/20 (e=1001) +debug1: restore_uid +debug1: temporarily_use_uid: 1001/20 (e=1001) +debug1: restore_uid debug1: Connection established. +debug1: identity file /home/david/.ssh/identity type 0 +debug1: identity file /home/david/.ssh/id_rsa type -1 +debug1: identity file /home/david/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version 2.0.12 (non-commercial) debug1: match: 2.0.12 (non-commercial) pat ^2\.0\. - -debug1: Local version string SSH-1.5-OpenSSH_2.3.0 green@FreeBSD.org 20010321 -debug1: Waiting for server public key. -debug1: Received server public key (768 bits) and host key (1024 bits). -debug1: Host 'bunrab' is known and matches the RSA host key. -debug1: Encryption type: 3des -debug1: Sent encrypted session key. -debug1: Installing crc compensation attack detector. -debug1: Received encrypted confirmation. -debug1: Trying RSA authentication via agent with 'david@dhcp-135.catwhisker.org' -debug1: Received RSA challenge from server. -debug1: Sending response to RSA challenge. -debug1: Remote: RSA authentication accepted. -debug1: RSA authentication accepted by server. -debug1: Requesting pty. -debug1: Requesting shell. +Enabling compatibility mode for protocol 2.0 +debug1: Local version string SSH-2.0-OpenSSH_2.9 green@FreeBSD.org 20010503 +debug1: SSH2_MSG_KEXINIT sent +debug1: SSH2_MSG_KEXINIT received +debug1: kex: server->client 3des-cbc hmac-md5 none +debug1: kex: client->server 3des-cbc hmac-md5 none +debug1: dh_gen_key: priv key bits set: 210/384 +debug1: bits set: 544/1024 +debug1: sending SSH2_MSG_KEXDH_INIT +debug1: expecting SSH2_MSG_KEXDH_REPLY +debug1: Host 'bunrab.catwhisker.org' is known and matches the DSA host key. +debug1: Found key in /home/david/.ssh/known_hosts2:1 +debug1: bits set: 493/1024 +debug1: len 40 datafellows 8831 +debug1: ssh_dss_verify: signature correct +debug1: kex_derive_keys +debug1: newkeys: mode 1 +debug1: SSH2_MSG_NEWKEYS sent +debug1: waiting for SSH2_MSG_NEWKEYS +debug1: newkeys: mode 0 +debug1: SSH2_MSG_NEWKEYS received +debug1: done: ssh_kex2. +debug1: send SSH2_MSG_SERVICE_REQUEST +debug1: buggy server: service_accept w/o service +debug1: got SSH2_MSG_SERVICE_ACCEPT +debug1: authentications that can continue: publickey,password +debug1: next auth method to try is publickey +debug1: try privkey: /home/david/.ssh/id_rsa +debug1: try privkey: /home/david/.ssh/id_dsa +debug1: next auth method to try is password +david@bunrab.catwhisker.org's password: +debug1: ssh-userauth2 successful: method password +debug1: channel 0: new [client-session] +debug1: channel_new: 0 +debug1: send channel open 0 debug1: Entering interactive session. -Last login: Sat May 12 19:34:38 2001 from dhcp-140 -Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 - The Regents of the University of California. All rights reserved. - +debug1: client_init id 0 arg 0 +debug1: channel request 0: shell +debug1: channel 0: open confirm rwindow 10000 rmax 16384 +Last login: Sat May 12 19:35:26 2001 FreeBSD 3.2-RELEASE (BUNRAB) #3: Sun Apr 30 19:44:37 PDT 2000 Welcome to FreeBSD! You will find security advisories and updated @@ -51,11 +78,25 @@ configuration utility. Edit /etc/motd to change this login announcement. You have mail. -bunrab[1] ^Dexit -Connection to bunrab closed. -debug1: Transferred: stdin 0, stdout 1201, stderr 30 bytes in 1.7 seconds -debug1: Bytes per second: stdin 0.0, stdout 712.8, stderr 17.8 +bunrab[1] ^Ddebug1: client_input_channel_req: channel 0 rtype exit-status reply 0 +debug1: channel 0: rcvd close +debug1: channel 0: output open -> drain +debug1: channel 0: input open -> closed +debug1: channel 0: close_read +exit +debug1: channel 0: obuf empty +debug1: channel 0: output drain -> closed +debug1: channel 0: close_write +debug1: channel 0: send close +debug1: channel 0: is dead +debug1: channel_free: channel 0: status: The following connections are open: + #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) + +debug1: channel_free: channel 0: dettaching channel user +Connection to bunrab.catwhisker.org closed. +debug1: Transferred: stdin 0, stdout 0, stderr 45 bytes in 7.6 seconds +debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 6.0 debug1: Exit status 0 dhcp-140[2] ^Dexit -Script done on Sat May 12 19:35:46 2001 +Script done on Sat May 12 19:41:02 2001 So I note a couple of salient things that show up: * Under ssh 2.9 (but not 2.3.0), the ssh server on bunrab engenders the line "debug1: buggy server: service_accept w/o service". * Under ssh 2.9, ssh appears to be looking for my private key in /home/david/.ssh/id_rsa, then /home/david/.ssh/id_dsa. Now, I never had either of those files; what I have in ~/.ssh is: -rw------- 1 david wheel 544 Mar 27 08:55 identity -rw-rw-r-- 1 david wheel 348 Mar 23 19:06 identity.pub -rw-r--r-- 1 david wheel 5792 May 10 13:31 known_hosts -rw-r--r-- 1 david wheel 3035 May 9 10:21 known_hosts2 I tried making "identity" a (hard) link to first id_rsa, then id_dsa, and re-tried the experiment. The only difference I saw was that if id_rsa existed (as a link to identity), ssh didn't claim it was trunig to use it; same for id_dsa. So basically, I'm confused. ssh appears to work ok for password authentication, but not for public key authentication -- or at least, it doesn't appear to be (completely?) compatible with ssh 2.3.0. Or maybe I'm overlooking something...? Help? Thanks, -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 12 23:40:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C371737B424 for ; Sat, 12 May 2001 23:40:53 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f4D6eqG20050; Sat, 12 May 2001 23:40:52 -0700 (PDT) Date: Sat, 12 May 2001 23:40:52 -0700 From: Alfred Perlstein To: David Wolfskill Cc: current@FreeBSD.ORG Subject: Re: ssh public key auth. incompatible between 2.3.0 vs. 2.9? Message-ID: <20010512234052.E18676@fw.wintelcom.net> References: <200105130540.f4D5eZl71004@bunrab.catwhisker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105130540.f4D5eZl71004@bunrab.catwhisker.org>; from david@catwhisker.org on Sat, May 12, 2001 at 10:40:35PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David Wolfskill [010512 22:41] wrote: > > So basically, I'm confused. ssh appears to work ok for password > authentication, but not for public key authentication -- or at least, it > doesn't appear to be (completely?) compatible with ssh 2.3.0. Or maybe > I'm overlooking something...? Brian Feldman switched the default to ssh2, for some reason it doesn't back off and try version 1. you need to do this "ssh -1 " which is damn irritating, but I don't know of any other option. Would it be possible to try version 1 before password? -- -Alfred Perlstein - [alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message