From owner-freebsd-current Sun Sep 10 1: 8:48 2000 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 A87C037B424 for ; Sun, 10 Sep 2000 01:08:41 -0700 (PDT) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id KAA22895; Sun, 10 Sep 2000 10:09:13 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 13Y2AJ-0004j9-00 for ; Sun, 10 Sep 2000 10:08:39 +0200 Date: Sun, 10 Sep 2000 10:08:39 +0200 From: Szilveszter Adam To: current@freebsd.org Subject: Re: MSDOSFS oddity Message-ID: <20000910100839.A17914@petra.hos.u-szeged.hu> Mail-Followup-To: current@freebsd.org References: <200009100647.e8A6l4N26872@ns.altadena.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.0.1i In-Reply-To: <200009100647.e8A6l4N26872@ns.altadena.net>; from pete@ns.altadena.net on Sat, Sep 09, 2000 at 11:47:04PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Sep 09, 2000 at 11:47:04PM -0700, Pete Carah wrote: > Probably not many -current users use msdosfs; I use it only for the > occasional floppy (extremely rare now) and the flash cards from my > electronic cameras. On trying to mount one of these today, I ran into > a problem (apparently in the msdosfs_vnops change of Sept 2, since a system > made the previous Wed didn't have this problem) where any msdosfs > system (I mount it 'ro,longnames,noauto') comes mounted with perms > d--------- (so noone but root can reference it) and names translated > to lower case. I've come to count on that last not happening (besides > if you wanted win95 behavior it would leave the first letter capital). > > The perms thing is a real problem. Hello Peter! I have just tried on a -CURRENT as of yesterday (9th, that is) and got this with a fairly old floppy (I think it is a DOS install floppy): fonix# ls -l /floppy total 797 -rwxr-xr-x 1 root wheel 2399 Máj 31 1994 4201.CP_ -rwxr-xr-x 1 root wheel 359 Máj 31 1994 4208.CP_ -rwxr-xr-x 1 root wheel 260 Máj 31 1994 5202.CP_ -rwxr-xr-x 1 root wheel 109 Máj 31 1994 720ID01.BAT -rwxr-xr-x 1 root wheel 109 Máj 31 1994 720ID02.BAT -rwxr-xr-x 1 root wheel 6421 Máj 31 1994 8514.VI_ -rwxr-xr-x 1 root wheel 61 Máj 31 1994 ADOS.CFG -rwxr-xr-x 1 root wheel 17911 Máj 31 1994 ADOS.CO_ -rwxr-xr-x 1 root wheel 45289 Máj 31 1994 ADOS.OV_ -rwxr-xr-x 1 root wheel 40535 Máj 31 1994 ADOS.TX_ -rwxr-xr-x 1 root wheel 7825 Máj 31 1994 AM.EXE -rwxr-xr-x 1 root wheel 12280 Máj 31 1994 AREADME.TX_ -rwxr-xr-x 1 root wheel 4547 Máj 31 1994 ASSIGN.CO_ -rwxr-xr-x 1 root wheel 22966 Máj 31 1994 BACKUP.EX_ -rwxr-xr-x 1 root wheel 1617 Máj 31 1994 CGA.GR_ <...> I cannot see a problem here. (Permissions are right and upper case letters are maintained.) Maybe the problem is with Windows-generated floppies? Besides, I ususally use the 'mtools' package for that occasional floppy, because it does not require me to mount the floppy before using it. I do not know for the memory cards, because I do not have a digital camera:-) Just a data point... -- 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 Sep 10 2:40:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 07BE437B50B; Sun, 10 Sep 2000 02:40:31 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8A9dZe71040; Sun, 10 Sep 2000 10:39:35 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8A9con69883; Sun, 10 Sep 2000 10:38:50 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009100938.e8A9con69883@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Robert Watson Cc: Brian Somers , Wes Peters , Seigo Tanimura , current@FreeBSD.org, net@FreeBSD.org, brian@Awfulhak.org Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr In-Reply-To: Message from Robert Watson of "Sat, 09 Sep 2000 12:16:39 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Sep 2000 10:38:49 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Interfaces in promiscuous mode will always result in a reboot. I > > *usually* get away with ejecting an active card if it's not in > > promiscuous mode. > > A while back I committed patches to use bpf_detach(), which elminated the > struct ifnet pointer in the bpf described at detach time. This removed > most of the panics I experience on ejecting pccards. This should be in > 5.0-CURRENT and 4.1-STABLE. If you're still experiencing panics, we > should track it down some more as presumably there is another reference > (it could also be a race condition, or in-use mbuf during detach?) I guess with a promiscuous interface, it's a whole lot more likely that there's an in-use mbuf around somewhere. That's probably what panics things I would think. > Robert N M Watson > > robert@fledge.watson.org http://www.watson.org/~robert/ > PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 > TIS Labs at Network Associates, Safeport Network Services -- 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 Sun Sep 10 2:53:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 91A5537B423; Sun, 10 Sep 2000 02:53:33 -0700 (PDT) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id RAA26042; Sun, 10 Sep 2000 17:53:29 +0800 Received: from jules.elischer.org (reggae-34-171.nv.iinet.net.au [203.59.167.171]) by muzak.iinet.net.au (8.8.5/8.8.5) with SMTP id RAA24780; Sun, 10 Sep 2000 17:53:26 +0800 Message-ID: <39BB5A14.167EB0E7@elischer.org> Date: Sun, 10 Sep 2000 02:53:24 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Bosko Milekic Cc: current@freebsd.org, net@freebsd.org Subject: Re: mbuf system with mutexes References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bosko Milekic wrote: > > For those interested, > > http://www.technokratis.com/code/mbuf/mbuf_mtx.patch Assuming we have a "my processor" index somewhere, how much work would it take to give each processor a separate cache of mbufs? Also, I've often wondered if the 'custer' special code might more simply be implemented by puting pointers to cluster methods in the mbuf external method pointers and removing all the special case tests to see if it's a cluster. In that case there would be just 2 cases: non-external and external, where 'cluster mbufs' are only a presupplied external type. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 3:30:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 355EF37B422 for ; Sun, 10 Sep 2000 03:30:54 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id DAA21850 for ; Sun, 10 Sep 2000 03:30:54 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 10 Sep 2000 03:30:54 -0700 (PDT) From: Kris Kennaway To: current@freebsd.org Subject: HEADS UP: New OpenSSH 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 New version of OpenSSH has been updated as announced a few days ago. Notable features: * ssh-add can handle DSA keys * sftp server interoperable with ssh.com clients and others * scp can handle files >2GB * better interoperability with other ssh2 clients/servers * ssh-agent can handle DSA keys * New feature to limit the number of outstanding unauthenticated ssh connections in sshd Enjoy! Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 5:11:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 007F637B422; Sun, 10 Sep 2000 05:11:17 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 10 Sep 2000 13:11:15 +0100 (BST) Date: Sun, 10 Sep 2000 13:11:15 +0100 From: David Malone To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: HEADS UP: New OpenSSH Message-ID: <20000910131115.A74804@walton.maths.tcd.ie> 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 kris@FreeBSD.org on Sun, Sep 10, 2000 at 03:30:54AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 10, 2000 at 03:30:54AM -0700, Kris Kennaway wrote: > * better interoperability with other ssh2 clients/servers Any idea if it can read non-OpenSSH DSA host keys? The version in 4.1 doesn't seem to be able too, though it can read non-OpenSSH RSA host keys. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 5:37:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 71FC937B43C for ; Sun, 10 Sep 2000 05:36:58 -0700 (PDT) Received: from nn.kiev.ua (nn.kiev.ua [193.193.193.203]) by segfault.kiev.ua (8) with ESMTP id POD79963 for ; Sun, 10 Sep 2000 15:36:47 +0300 (EEST) (envelope-from netch@nn.kiev.ua) Received: (from netch@localhost) by nn.kiev.ua (8.11.0/8.11.0) id e8ACahT01063 for freebsd-current@freebsd.org; Sun, 10 Sep 2000 15:36:43 +0300 (EEST) (envelope-from netch) Date: Sun, 10 Sep 2000 15:36:43 +0300 From: Valentin Nechayev To: freebsd-current@freebsd.org Subject: load average is 1 when no processes active; etc. Message-ID: <20000910153643.A799@nn.kiev.ua> Reply-To: netch@segfault.kiev.ua Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-42: On Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG System in question is: root@nn:~##uname -mrs FreeBSD 5.0-CURRENT i386 root@nn:~##grep FreeBSD_version /usr/include/sys/param.h #undef __FreeBSD_version #define __FreeBSD_version 500012 /* Master, propagated to newvers */ root@nn:~## cvsup was Sep 8, approximately at 18:00 GMT. `top -I' output: ==={ last pid: 811; load averages: 1.01, 0.97, 0.67 up 0+00:16:12 23:26:26 24 processes: 1 running, 21 sleeping, 2 stopped CPU states: 0.0% user, 0.0% nice, 0.0% system, 7.9% interrupt, 92.1% idle Mem: 7524K Active, 9788K Inact, 5812K Wired, 8K Cache, 6336K Buf, 5300K Free Swap: 300M Total, 300M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 811 root 46 0 1916K 1176K RUN 0:00 0.00% 0.00% top ===} A few seconds after starting: root@nn:~##uptime 11:30PM up 50 secs, 1 user, load averages: 0.88, 0.22, 0.08 Of course, real LA is less than 0.1. The same system has another strangeness - `microuptime() went backwards': ==={ /var/run/dmesg.boot Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sat Sep 9 08:19:58 EEST 2000 root@nn.kiev.ua:/usr/src.cr/sys/compile/nn10 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 334092166 Hz CPU: AMD-K6(tm) 3D processor (334.09-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 33554432 (32768K bytes) avail memory = 28540928 (27872K bytes) Preloaded elf kernel "kernel.ko" at 0xc0426000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc04260a0. K6-family MTRR support enabled (2 registers) md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 pci0: at 7.3 pci0: at 17.0 irq 11 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ppi0: on ppbus0 sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 pcm0: on sbc0 unknown: can't assign resources pca0: at port 0x61 on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default DUMMYNET initialized (000608) IPv6 packet filtering initialized, default to accept, logging limited to 100 packets/entry IPsec: Initialized Security Association Processing. ncp_load: [210-213] IP Filter: v3.4.9 initialized. Default = pass all, Logging = enabled microuptime() went backwards (1.3891137 -> 0.596214) microuptime() went backwards (1.3891137 -> 0.596655) microuptime() went backwards (1.3891137 -> 0.597078) microuptime() went backwards (1.3891137 -> 0.597480) microuptime() went backwards (1.3891137 -> 0.597795) microuptime() went backwards (1.3891137 -> 0.598094) microuptime() went backwards (1.3891137 -> 0.598412) microuptime() went backwards (1.3891137 -> 0.598708) microuptime() went backwards (1.3891137 -> 0.599019) microuptime() went backwards (1.3891137 -> 0.599489) microuptime() went backwards (1.3891137 -> 0.600060) microuptime() went backwards (1.3891137 -> 0.600484) microuptime() went backwards (1.3891137 -> 0.600921) microuptime() went backwards (1.3891137 -> 0.601532) microuptime() went backwards (1.3891137 -> 0.601965) microuptime() went backwards (1.3891137 -> 0.602373) microuptime() went backwards (1.3891137 -> 0.602789) microuptime() went backwards (1.3891137 -> 0.603218) microuptime() went backwards (1.3891137 -> 0.603658) microuptime() went backwards (1.3891137 -> 0.604059) microuptime() went backwards (1.3891137 -> 0.604479) microuptime() went backwards (1.3891137 -> 0.604902) microuptime() went backwards (1.3891137 -> 0.605318) microuptime() went backwards (1.3891137 -> 0.605743) ad0: 14664MB [29795/16/63] at ata0-master using UDMA33 (null): failure to execute ATAPI packet command microuptime() went backwards (1.3891137 -> 0.733477) microuptime() went backwards (1.3891137 -> 0.733885) microuptime() went backwards (1.3891137 -> 0.734296) microuptime() went backwards (1.3891137 -> 0.734709) microuptime() went backwards (1.3891137 -> 0.735124) microuptime() went backwards (1.3891137 -> 0.735548) microuptime() went backwards (1.3891137 -> 0.735960) acd0: CDROM at ata1-slave using PIO0 Mounting root from ufs:/dev/ad0s4a microuptime() went backwards (1.3891137 -> 0.737877) microuptime() went backwards (1.3891137 -> 0.738868) microuptime() went backwards (1.3891137 -> 0.739302) microuptime() went backwards (1.3891137 -> 0.741334) microuptime() went backwards (1.3891137 -> 0.741642) microuptime() went backwards (1.3891137 -> 0.741940) microuptime() went backwards (1.3891137 -> 0.745399) microuptime() went backwards (1.3891137 -> 0.745844) microuptime() went backwards (1.3891137 -> 0.746355) microuptime() went backwards (1.3891137 -> 0.746769) microuptime() went backwards (1.3891137 -> 0.747182) microuptime() went backwards (1.3891137 -> 0.751334) microuptime() went backwards (1.3891137 -> 0.751750) microuptime() went backwards (1.3891137 -> 0.752162) microuptime() went backwards (1.3891137 -> 0.754490) microuptime() went backwards (1.3891137 -> 0.754907) microuptime() went backwards (1.3891137 -> 0.758873) microuptime() went backwards (1.3891137 -> 0.759308) microuptime() went backwards (1.3891137 -> 0.759847) microuptime() went backwards (1.3891137 -> 0.761335) microuptime() went backwards (1.3891137 -> 0.761738) microuptime() went backwards (1.3891137 -> 0.762151) microuptime() went backwards (1.3891137 -> 0.762565) microuptime() went backwards (1.3891137 -> 0.762983) microuptime() went backwards (1.3891137 -> 0.766245) microuptime() went backwards (1.3891137 -> 0.766678) microuptime() went backwards (1.3891137 -> 0.767159) microuptime() went backwards (1.3891137 -> 0.770116) microuptime() went backwards (1.3891137 -> 0.770417) microuptime() went backwards (1.3891137 -> 0.771333) microuptime() went backwards (1.3891137 -> 0.771751) microuptime() went backwards (1.3891137 -> 0.772175) microuptime() went backwards (1.3891137 -> 0.774745) microuptime() went backwards (1.3891137 -> 0.775169) microuptime() went backwards (1.3891137 -> 0.775642) microuptime() went backwards (1.3891137 -> 0.777929) microuptime() went backwards (1.3891137 -> 0.778343) microuptime() went backwards (1.3891137 -> 0.781333) microuptime() went backwards (1.3891137 -> 0.781755) microuptime() went backwards (1.3891137 -> 0.782167) microuptime() went backwards (1.3891137 -> 0.785741) microuptime() went backwards (1.3891137 -> 0.786157) microuptime() went backwards (1.3891137 -> 0.790786) microuptime() went backwards (1.3891137 -> 0.791221) microuptime() went backwards (1.3891137 -> 0.791705) microuptime() went backwards (1.3891137 -> 0.792131) microuptime() went backwards (1.3891137 -> 0.792548) microuptime() went backwards (1.3891137 -> 0.793555) microuptime() went backwards (1.3891137 -> 0.793981) microuptime() went backwards (1.3891137 -> 0.800430) microuptime() went backwards (1.3891137 -> 0.800893) microuptime() went backwards (1.3891137 -> 0.801410) microuptime() went backwards (1.3891137 -> 0.801835) microuptime() went backwards (1.3891137 -> 0.802248) microuptime() went backwards (1.3891137 -> 0.802658) microuptime() went backwards (1.3891137 -> 0.809180) microuptime() went backwards (1.3891137 -> 0.809619) microuptime() went backwards (1.3891137 -> 0.811333) microuptime() went backwards (1.3891137 -> 0.811754) microuptime() went backwards (1.3891137 -> 0.812170) microuptime() went backwards (1.3891137 -> 0.815347) microuptime() went backwards (1.3891137 -> 0.815787) microuptime() went backwards (1.3891137 -> 0.816258) microuptime() went backwards (1.3891137 -> 0.816992) microuptime() went backwards (1.3891137 -> 0.817407) microuptime() went backwards (1.3891137 -> 0.821333) microuptime() went backwards (1.3891137 -> 0.821752) microuptime() went backwards (1.3891137 -> 0.822163) microuptime() went backwards (1.3891137 -> 0.824805) microuptime() went backwards (1.3891137 -> 0.825227) microuptime() went backwards (1.3891137 -> 0.831335) microuptime() went backwards (1.3891137 -> 0.831738) microuptime() went backwards (1.3891137 -> 0.832149) microuptime() went backwards (1.3891137 -> 0.832618) microuptime() went backwards (1.3891137 -> 0.833019) microuptime() went backwards (1.3891137 -> 0.834491) microuptime() went backwards (1.3891137 -> 0.834924) microuptime() went backwards (1.3891137 -> 0.835453) microuptime() went backwards (1.3891137 -> 0.840432) microuptime() went backwards (1.3891137 -> 0.840837) microuptime() went backwards (1.3891137 -> 0.841335) microuptime() went backwards (1.3891137 -> 0.841637) microuptime() went backwards (1.3891137 -> 0.841931) microuptime() went backwards (1.3891137 -> 0.848243) microuptime() went backwards (1.3891137 -> 0.848655) microuptime() went backwards (1.3891137 -> 0.851333) microuptime() went backwards (1.3891137 -> 0.851753) microuptime() went backwards (1.3891137 -> 0.852167) microuptime() went backwards (1.3891137 -> 0.856058) microuptime() went backwards (1.3891137 -> 0.856356) microuptime() went backwards (1.3891137 -> 0.858910) microuptime() went backwards (1.3891137 -> 0.859344) microuptime() went backwards (1.3891137 -> 0.859837) microuptime() went backwards (1.3891137 -> 0.861335) microuptime() went backwards (1.3891137 -> 0.861745) microuptime() went backwards (1.3891137 -> 0.862155) microuptime() went backwards (1.3891137 -> 0.863869) microuptime() went backwards (1.3891137 -> 0.864283) microuptime() went backwards (1.3891137 -> 0.868086) microuptime() went backwards (1.3891137 -> 0.868530) microuptime() went backwards (1.3891137 -> 0.869006) microuptime() went backwards (1.3891137 -> 0.871335) microuptime() went backwards (1.3891137 -> 0.871748) microuptime() went backwards (1.3891137 -> 0.872149) microuptime() went backwards (1.3891137 -> 0.872563) microuptime() went backwards (1.3891137 -> 0.879495) microuptime() went backwards (1.3891137 -> 0.879914) microuptime() went backwards (1.3891137 -> 0.880341) microuptime() went backwards (1.3891137 -> 0.880828) microuptime() went backwards (1.3891137 -> 0.881335) microuptime() went backwards (1.3891137 -> 0.881760) microuptime() went backwards (1.3891137 -> 0.882171) microuptime() went backwards (1.3891137 -> 0.887308) microuptime() went backwards (1.3891137 -> 0.887728) microuptime() went backwards (1.3891137 -> 0.890568) microuptime() went backwards (1.3891137 -> 0.891002) microuptime() went backwards (1.3891137 -> 0.891497) microuptime() went backwards (1.3891137 -> 0.891918) microuptime() went backwards (1.3891137 -> 0.892331) microuptime() went backwards (1.3891137 -> 0.895122) microuptime() went backwards (1.3891137 -> 0.895548) microuptime() went backwards (1.3891137 -> 0.901334) microuptime() went backwards (1.3891137 -> 0.901757) microuptime() went backwards (1.3891137 -> 0.902210) microuptime() went backwards (1.3891137 -> 0.902935) microuptime() went backwards (1.3891137 -> 0.903343) microuptime() went backwards (1.3891137 -> 0.903753) microuptime() went backwards (1.3891137 -> 0.904187) microuptime() went backwards (1.3891137 -> 0.904673) microuptime() went backwards (1.3891137 -> 0.910748) microuptime() went backwards (1.3891137 -> 0.911169) microuptime() went backwards (1.3891137 -> 0.911591) microuptime() went backwards (1.3891137 -> 0.912020) microuptime() went backwards (1.3891137 -> 0.912457) microuptime() went backwards (1.3891137 -> 0.912899) microuptime() went backwards (1.3891137 -> 0.918561) microuptime() went backwards (1.3891137 -> 0.918976) microuptime() went backwards (1.3891137 -> 0.921335) microuptime() went backwards (1.3891137 -> 0.921758) microuptime() went backwards (1.3891137 -> 0.922169) microuptime() went backwards (1.3891137 -> 0.926373) microuptime() went backwards (1.3891137 -> 0.926792) microuptime() went backwards (1.3891137 -> 0.930541) microuptime() went backwards (1.3891137 -> 0.930973) microuptime() went backwards (1.3891137 -> 0.931458) microuptime() went backwards (1.3891137 -> 0.931877) microuptime() went backwards (1.3891137 -> 0.932286) microuptime() went backwards (1.3891137 -> 0.934187) microuptime() went backwards (1.3891137 -> 0.934613) microuptime() went backwards (1.3891137 -> 0.941335) microuptime() went backwards (1.3891137 -> 0.941659) microuptime() went backwards (1.3891137 -> 0.941950) microuptime() went backwards (1.3891137 -> 0.942242) microuptime() went backwards (1.3891137 -> 0.942540) microuptime() went backwards (1.3891137 -> 0.946729) microuptime() went backwards (1.3891137 -> 0.947152) microuptime() went backwards (1.3891137 -> 0.947630) microuptime() went backwards (1.3891137 -> 0.949812) microuptime() went backwards (1.3891137 -> 0.950227) microuptime() went backwards (1.3891137 -> 0.951336) microuptime() went backwards (1.3891137 -> 0.951761) microuptime() went backwards (1.3891137 -> 0.952172) microuptime() went backwards (1.3891137 -> 0.956544) microuptime() went backwards (1.3891137 -> 0.956862) microuptime() went backwards (1.3891137 -> 0.957220) microuptime() went backwards (1.3891137 -> 0.957625) microuptime() went backwards (1.3891137 -> 0.958047) microuptime() went backwards (1.3891137 -> 0.961335) microuptime() went backwards (1.3891137 -> 0.961750) microuptime() went backwards (1.3891137 -> 0.962156) microuptime() went backwards (1.3891137 -> 0.965437) microuptime() went backwards (1.3891137 -> 0.965841) microuptime() went backwards (1.3891137 -> 0.971336) microuptime() went backwards (1.3891137 -> 0.971634) microuptime() went backwards (1.3891137 -> 0.972029) microuptime() went backwards (1.3891137 -> 0.972462) microuptime() went backwards (1.3891137 -> 0.972946) microuptime() went backwards (1.3891137 -> 0.973369) microuptime() went backwards (1.3891137 -> 0.973785) microuptime() went backwards (1.3891137 -> 0.981063) microuptime() went backwards (1.3891137 -> 0.981480) microuptime() went backwards (1.3891137 -> 0.981894) microuptime() went backwards (1.3891137 -> 0.982304) microuptime() went backwards (1.3891137 -> 0.988875) microuptime() went backwards (1.3891137 -> 0.989295) microuptime() went backwards (1.3891137 -> 0.991055) microuptime() went backwards (1.3891137 -> 0.991487) microuptime() went backwards (1.3891137 -> 0.991914) microuptime() went backwards (1.3891137 -> 0.992329) microuptime() went backwards (1.3891137 -> 0.992850) microuptime() went backwards (1.3891137 -> 0.996689) microuptime() went backwards (1.3891137 -> 0.997118) microuptime() went backwards (1.3891137 -> 1.001335) microuptime() went backwards (1.3891137 -> 1.001771) microuptime() went backwards (1.3891137 -> 1.002193) microuptime() went backwards (1.3891137 -> 1.004501) microuptime() went backwards (1.3891137 -> 1.004902) microuptime() went backwards (1.3891137 -> 1.011336) microuptime() went backwards (1.3891137 -> 1.011741) microuptime() went backwards (1.3891137 -> 1.012148) microuptime() went backwards (1.3891137 -> 1.012558) microuptime() went backwards (1.3891137 -> 1.012969) microuptime() went backwards (1.3891137 -> 1.013574) microuptime() went backwards (1.3891137 -> 1.013906) microuptime() went backwards (1.3891137 -> 1.014387) microuptime() went backwards (1.3891137 -> 1.020128) microuptime() went backwards (1.3891137 -> 1.020545) microuptime() went backwards (1.3891137 -> 1.021337) microuptime() went backwards (1.3891137 -> 1.021765) microuptime() went backwards (1.3891137 -> 1.022185) microuptime() went backwards (1.3891137 -> 1.022617) ===} Config is: ==={ machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident nn11 maxusers 32 hints "GENERIC.hints" #Default places to look for devices. options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INCLUDE_CONFIG_FILE options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV # install a CDEV entry in /dev options RANDOMDEV device isa device eisa device pci options COMPAT_OLDISA # compatability shims for lnc, fe, le options COMPAT_OLDPCI # compatability shims for lnc, vx # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 device atkbd device psm device vga # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc 1 # Floating point support - do not disable. device npx # Power management support (see LINT for more options) device apm # Serial (COM) ports device sio # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # Pseudo devices - the number indicates how many units to allocated. device loop # Network loopback device ether # Ethernet support device sl # Kernel SLIP device ppp 1 # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif 4 # IPv6 and IPv4 tunneling device faith 1 # IPv6-to-IPv4 relaying (translation) device speaker # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf 2 # Berkeley packet filter options DDB options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN options TCP_RESTRICT_RST #restrict emission of TCP RST options DUMMYNET options EXT2FS options VFS_AIO options _KPOSIX_VERSION=199309L device vn device snp options MSGBUF_SIZE=81920 options SC_HISTORY_SIZE=200 # number of history buffer lines options SC_MOUSE_CHAR=0x3 # char code for text mode mouse cursor device pcm device sbc device pca ===} /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 5:40: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (Postfix) with ESMTP id 75EC337B43C for ; Sun, 10 Sep 2000 05:40:00 -0700 (PDT) Received: from netch@localhost by burka.carrier.kiev.ua id PPJ85223; Sun, 10 Sep 2000 15:39:57 +0300 (EEST) (envelope-from netch) Date: Sun, 10 Sep 2000 15:39:57 +0300 (EEST) Message-Id: <200009101239.PPJ85223@burka.carrier.kiev.ua> From: netch@carrier.kiev.ua (Valentin Nechayev) To: John Baldwin , freebsd-current@freebsd.org Subject: Re: microuptime() went backwards In-Reply-To: <200009080028.RAA26021@pike.osd.bsdi.com> Organization: Lucky Netch Incorporated User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.5-STABLE (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello John Baldwin! >> microuptime() went backwards (1.7682417 -> 1.997434) >> >> I recall reading in -current earlier this week that someone was >> looking for victims getting this. What further information can I provide? JB> This is a SMPng issue on UP machines. I have obtained the same on non-SMP machine. (See my parallel letter.) /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 5:56:20 2000 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 0AC2737B422 for ; Sun, 10 Sep 2000 05:56:18 -0700 (PDT) Received: (from uucp@localhost) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-rina.r-0.1-11.01.2000) with UUCP id VAA28352; Sun, 10 Sep 2000 21:56:03 +0900 (JST) Received: (from uucp@localhost) by silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W) with UUCP id VAA06454; Sun, 10 Sep 2000 21:50:11 +0900 (JST) Received: from bunko.carrots.uucp.r.dl.itc.u-tokyo.ac.jp.nkth.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by bunko (8.9.3+3.2W/3.7W) with ESMTP/IPv4 id VAA09243; Sun, 10 Sep 2000 21:45:33 +0900 (JST) Message-Id: <200009101245.VAA09243@bunko> Date: Sun, 10 Sep 2000 21:45:32 +0900 From: Seigo Tanimura To: n@nectar.com Cc: current@freebsd.org Subject: Re: nsswitch meets current In-Reply-To: In your message of "Wed, 6 Sep 2000 15:14:31 -0500" <20000906151431.A26152@hamlet.nectar.com> References: <20000906151431.A26152@hamlet.nectar.com> Cc: Seigo Tanimura User-Agent: Wanderlust/1.1.0 (Overjoyed) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386--freebsd) Organization: Carrots 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, 6 Sep 2000 15:14:31 -0500, "Jacques A. Vidrine" said: n> = host.conf has been removed from src/etc. rc.network has been modified n> to warn that host.conf is no longer used at boot time. In addition, if n> there is a host.conf but no nsswitch.conf, the latter is created at boot n> time from the former. You still need host.conf to run old binaries (including Netscape) linked against libc.so.3 and earlier. I prefer to warn 'host.conf is for compatibility with old libc.' -- 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 Sep 10 6:30: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 153B637B423 for ; Sun, 10 Sep 2000 06:30:01 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13Y6kd-000PZi-00; Sun, 10 Sep 2000 14:02:27 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id OAA59155; Sun, 10 Sep 2000 14:02:26 +0100 (BST) (envelope-from ben) Date: Sun, 10 Sep 2000 14:02:26 +0100 From: Ben Smithurst To: Bosko Milekic Cc: current@freebsd.org Subject: Re: page fault in sched_ithd Message-ID: <20000910140226.H77593@strontium.scientia.demon.co.uk> References: <14779.6851.88867.359611@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bosko Milekic wrote: > I catch this page fault (described in topic) following an: > > `ifconfig de0 down' > > Unfortunately, I don't have much more information to provide for now. > I'm in the middle of debugging something else. More info can be provided > on request (let me know if you want to look at it and cannot reproduce > it). Sources of last friday (evening). ifconfig(8) is what does it for me too. It's ifconfig(8) at boot time though, so I'm not sure exactly what arguments it has or what it's doing at the time. Mike wrote: >> Isn't a stray IRQ a hardware glitch? If so, I'd say that logging it >> and then ignoring it would be the right thing. If people think so then I'll improve my patch a bit to do this. I agree, unless there's a better way to fix the problem. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 9:20:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id E263437B424 for ; Sun, 10 Sep 2000 09:20:15 -0700 (PDT) Received: from castle2.jp.FreeBSD.org (castle2.jp.FreeBSD.org [210.226.20.120]) by updraft.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id BAA79509 for ; Mon, 11 Sep 2000 01:20:15 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by castle2.jp.FreeBSD.org (8.11.0+3.3W/8.11.0) with ESMTP/inet id e8AGKEX62424 for ; Mon, 11 Sep 2000 01:20:14 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <200009101245.VAA09243@bunko> References: <20000906151431.A26152@hamlet.nectar.com> <20000906151431.A26152@hamlet.nectar.com> <200009101245.VAA09243@bunko> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Molpe) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 11 From: Makoto MATSUSHITA To: current@freebsd.org Subject: Re: nsswitch meets current Date: Mon, 11 Sep 2000 01:20:10 +0900 Message-Id: <20000911012010A.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tanimura> You still need host.conf to run old binaries (including Netscape) tanimura> linked against libc.so.3 and earlier. I prefer to warn 'host.conf is tanimura> for compatibility with old libc.' Is there any chance that compat1x, compat2*, compat3x includes /etc/host.conf for backward compatibility ? Users who install FreeBSD to fresh PC will meet unpredictable behavior if users run Navigator... -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 9:32:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.netbenefit.co.uk (mailhost.netbenefit.co.uk [212.53.64.39]) by hub.freebsd.org (Postfix) with ESMTP id F11FF37B424 for ; Sun, 10 Sep 2000 09:32:43 -0700 (PDT) Received: from [212.159.26.131] (helo=alveley.org) by mailhost.netbenefit.co.uk with esmtp (NetBenefit 1.5) id 13YA25-0007jS-00 for current@freebsd.org; Sun, 10 Sep 2000 17:32:41 +0100 Message-ID: <39BBB7A9.43DC1CEB@alveley.org> Date: Sun, 10 Sep 2000 17:32:41 +0100 From: "Dampure, Pierre Y." X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: nsswitch meets current References: <20000906151431.A26152@hamlet.nectar.com> <20000906151431.A26152@hamlet.nectar.com> <200009101245.VAA09243@bunko> <20000911012010A.matusita@jp.FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Makoto MATSUSHITA wrote: > > tanimura> You still need host.conf to run old binaries (including Netscape) > tanimura> linked against libc.so.3 and earlier. I prefer to warn 'host.conf is > tanimura> for compatibility with old libc.' > > Is there any chance that compat1x, compat2*, compat3x includes > /etc/host.conf for backward compatibility ? Users who install FreeBSD > to fresh PC will meet unpredictable behavior if users run Navigator... > This might be true for the FreeBSD binary, but does not seem to be for the BSDI one -- I suppressed /etc/host.conf and have yet to encounter a problem... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 12:49:31 2000 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 6B4ED37B42C for ; Sun, 10 Sep 2000 12:49:26 -0700 (PDT) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id VAA25920; Sun, 10 Sep 2000 21:49:58 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 13YD6S-0006Vu-00 for ; Sun, 10 Sep 2000 21:49:24 +0200 Date: Sun, 10 Sep 2000 21:49:24 +0200 From: Szilveszter Adam To: freebsd-current@freebsd.org Subject: pcm0: hwptr went backwards 4128 -> 4116 Message-ID: <20000910214924.B24328@petra.hos.u-szeged.hu> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everybody! Since no one this far has reported anything like this, I'll just throw this one in, maybe someone has an idea... I have an SB 64 AWE ISA PnP card, which is detected as: sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 midi0: on sbc0 midi1: on sbc0 midi2: at port 0x620-0x623,0xa20-0xa23,0xe20-0xe 23 on isa0 emu2: DRAM size = 512KB Sound support is compiled into the kernel. The system is: FreeBSD fonix.hos.u-szeged.hu 5.0-CURRENT FreeBSD 5.0-CURRENT #14: Sun Sep 10 04:02:07 CEST 2000 root@:/usr/src/sys/compile/FONIX i386 with the SMPng patchset (+the one posted by Tor Egge for the 'dirty buffers' problem some days ago.) This evening I was listening to some mp3s with mpg123, when suddenly the output started to have short pauses in it. And then the following message appeared exactly once this far: Sep 10 21:24:40 fonix /boot/kernel/kernel.ko: pcm0: hwptr went backwards 4128 -> 4116 I must add that this far the only symptoms I had with SMPng were the unnaturally high load averages, as reported by others, but none of the 'microuptime went back' stuff. I have a PII 233 on a Spacewalker mobo using the Intel LX 440 chipset. If you need any other info, just tell me. Thanks for your time and keep up the good work! -- 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 Sep 10 14:19: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E961C37B422; Sun, 10 Sep 2000 14:19:03 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA61468; Sun, 10 Sep 2000 14:19:03 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 10 Sep 2000 14:19:03 -0700 (PDT) From: Kris Kennaway To: David Malone Cc: current@FreeBSD.org Subject: Re: HEADS UP: New OpenSSH In-Reply-To: <20000910131115.A74804@walton.maths.tcd.ie> 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, 10 Sep 2000, David Malone wrote: > On Sun, Sep 10, 2000 at 03:30:54AM -0700, Kris Kennaway wrote: > > > * better interoperability with other ssh2 clients/servers > > Any idea if it can read non-OpenSSH DSA host keys? The version in > 4.1 doesn't seem to be able too, though it can read non-OpenSSH > RSA host keys. Hmm, I'm not sure. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 15:57:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from rdsl2-1.ddsl.mr.net (rdsl2-1.ddsl.mr.net [137.192.134.5]) by hub.freebsd.org (Postfix) with ESMTP id 16CD737B422 for ; Sun, 10 Sep 2000 15:57:21 -0700 (PDT) Received: from snowplow.org (scotch.snowplow.org [10.1.1.3]) by rdsl2-1.ddsl.mr.net (Postfix) with ESMTP id 70A87FC71 for ; Sat, 9 Sep 2000 17:55:42 -0500 (CDT) Message-ID: <39BBCC46.6F181E11@snowplow.org> Date: Sun, 10 Sep 2000 18:00:38 +0000 From: Eric Hedberg X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Another broken buildworld Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, fresh cvsup (blew away the old /usr/src, slurped down a new one this afternoon). Make buildworld dies at: ===> libcrypto ( echo "#ifndef MK1MF_BUILD"; echo " /* auto-generated by crypto/Makefile.ssl for crypto/cversion.c */"; echo " #define CFLAGS \"cc\""; echo " #define PLATFORM \"`uname -s`-`uname -m`\""; echo " #define DATE \"`LC_TIME=C date`\""; echo "#endif" ) > buildinf.h make: don't know how to make rsa_eay.c. Stop *** Error code 2 Stop in /usr/src/secure/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Cheers. -Eric Hedberg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 16:10:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5C4E337B423; Sun, 10 Sep 2000 16:10:20 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id QAA73965; Sun, 10 Sep 2000 16:10:20 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 10 Sep 2000 16:10:20 -0700 (PDT) From: Kris Kennaway To: Eric Hedberg Cc: current@freebsd.org Subject: Re: Another broken buildworld In-Reply-To: <39BBCC46.6F181E11@snowplow.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 On Sun, 10 Sep 2000, Eric Hedberg wrote: > OK, fresh cvsup (blew away the old /usr/src, slurped down a new one this > afternoon). Don't cvsup from cvsup3, it doesnt carry a full crypto mirror. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 16:21:57 2000 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 9854F37B424 for ; Sun, 10 Sep 2000 16:21:50 -0700 (PDT) Received: from vigrid.com (pm3-pt68.pcnet.net [206.105.29.142]) by pcnet1.pcnet.com (8.8.7/PCNet) with ESMTP id TAA16047; Sun, 10 Sep 2000 19:21:32 -0400 (EDT) Message-ID: <39BC16BA.4D089D86@vigrid.com> Date: Sun, 10 Sep 2000 19:18:18 -0400 From: "Daniel M. Eischen" X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Cc: mitja@hermes.si, rse@engelschall.com Subject: Re: makecontext() & friends ? References: <20000909150305.A26019@lamu.hermes.si> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Moved to -current ] Mitja Horvat wrote: > > Hi Dan, > > > I have implemented {make,get,set,swap}context as library routines > > for FreeBSD. They're gathering dust somewhere and need a bit of > > polishing. If you give me some time I can dust them off and > > send them to you. > > I would really appreciate if I could get my hands on this code. > Could you please specify a link, or if you prefer you can send the > tarball as an attachment to mitja@hermes.si. I've had a couple of requests for this in the past also. I've placed library versions of {make,get,set,swap}context() at: http://people.freebsd.org/~deischen/context/libc.diffs http://people.freebsd.org/~deischen/context/sys.diffs Also included are _getcontext() and _setcontext() which do not save and restore the signal mask. The alpha bits are included, but are uncompiled and untested. There are changes to which are needed to build libc, so you have to either hand patch /usr/include/sys/ucontext.h or install the include files after applying sys.diffs. Feedback and comments welcome, especially to the alpha bits. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 16:53:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from picknowl.com.au (firewall.picknowl.com.au [203.24.77.2]) by hub.freebsd.org (Postfix) with ESMTP id 21E9D37B423 for ; Sun, 10 Sep 2000 16:53:18 -0700 (PDT) Received: from mailserver1.picknowl.com.au (mailserver1.picknowl.com.au [10.1.1.4]) by mailserver2.picknowl.com.au (8.9.3/8.9.3) with ESMTP id KAA27549 for ; Mon, 11 Sep 2000 10:23:11 +1030 From: oliver@picknowl.com.au Received: from [203.58.175.182] by mailserver1.picknowl.com.au (NTMail 5.03.0001/NU2410.00.38109bdc) with ESMTP id ypykzaaa for freebsd-current@FreeBSD.org; Mon, 11 Sep 2000 09:19:47 +0930 Message-Id: <1.5.4.32.20000911000559.0068de38@mail.picknowl.com.au> X-Sender: oliver@mail.picknowl.com.au X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 11 Sep 2000 09:05:59 +0900 To: freebsd-current@FreeBSD.org Subject: subscribe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 17: 6: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id 586F937B422; Sun, 10 Sep 2000 17:06:03 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e8B062G79996; Sun, 10 Sep 2000 17:06:02 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200009110006.e8B062G79996@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kris Kennaway Cc: David Malone , current@FreeBSD.ORG Subject: Re: HEADS UP: New OpenSSH In-Reply-To: Date: Sun, 10 Sep 2000 17:06:02 -0700 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > On Sun, 10 Sep 2000, David Malone wrote: > > > On Sun, Sep 10, 2000 at 03:30:54AM -0700, Kris Kennaway wrote: > > > > > * better interoperability with other ssh2 clients/servers > > > > Any idea if it can read non-OpenSSH DSA host keys? The version in > > 4.1 doesn't seem to be able too, though it can read non-OpenSSH > > RSA host keys. > > Hmm, I'm not sure. Try out ssh-keygen -x and -X. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 17:13: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 0DA6E37B422; Sun, 10 Sep 2000 17:13:05 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8B0Cjk19233; Mon, 11 Sep 2000 09:42:45 +0930 (CST) (envelope-from grog) Date: Mon, 11 Sep 2000 09:42:45 +0930 From: Greg Lehey To: Mike Meyer Cc: Ben Smithurst , current@FreeBSD.ORG Subject: Re: page fault in sched_ithd Message-ID: <20000911094245.A19199@wantadilla.lemis.com> References: <20000909195525.E77593@strontium.scientia.demon.co.uk> <20000909210619.F77593@strontium.scientia.demon.co.uk> <14779.6851.88867.359611@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14779.6851.88867.359611@guru.mired.org>; from mwm@mired.org on Sun, Sep 10, 2000 at 12:23:15AM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 10 September 2000 at 0:23:15 -0500, Mike Meyer wrote: > Ben Smithurst writes: >> After poking around a bit with remote GDB, this seems to be caused by a >> stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM. >> >> The attached rather crude patch has "fixed" the problem for now, but >> does anyone have any suggestions for a real fix? > > Isn't a stray IRQ a hardware glitch? If so, I'd say that logging it > and then ignoring it would be the right thing. Sorry, I missed the beginning of this. Could somebody send me the patch? I'd assume that a relatively simple check would handle the issue, based on what I've seen here. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 17:15:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 9A76D37B422 for ; Sun, 10 Sep 2000 17:15:11 -0700 (PDT) Received: (from newton@localhost) by gizmo.internode.com.au (8.11.0/8.9.3) id e8B0EAw19808; Mon, 11 Sep 2000 09:44:10 +0930 (CST) (envelope-from newton) Date: Mon, 11 Sep 2000 09:44:10 +0930 From: Mark Newton To: Szilveszter Adam Cc: freebsd-current@FreeBSD.ORG Subject: Re: pcm0: hwptr went backwards 4128 -> 4116 Message-ID: <20000911094409.B19766@internode.com.au> References: <20000910214924.B24328@petra.hos.u-szeged.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20000910214924.B24328@petra.hos.u-szeged.hu> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 10, 2000 at 09:49:24PM +0200, Szilveszter Adam wrote: > Since no one this far has reported anything like this, ... http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20731 - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 17:49:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id D971437B422 for ; Sun, 10 Sep 2000 17:49:46 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id RAA28932; Sun, 10 Sep 2000 17:49:07 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009110049.RAA28932@pike.osd.bsdi.com> Subject: Re: Dirty buffers on reboot.. In-Reply-To: <200009090208.EAA69984@midten.fast.no> from "Tor.Egge@fast.no" at "Sep 9, 2000 04:08:22 am" To: Tor.Egge@fast.no Date: Sun, 10 Sep 2000 17:49:07 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tor.Egge@fast.no wrote: > > Ok, an update on the dirty buffers on reboot: > > > > If you use the reboot command, you will get dirty buffers. If you use > > 'shutdown -r now' instead, you won't get dirty buffers. Thus, as a workaround > > for now, use the shutdown command to reboot your box until we can track this > > down. > > I suggest using some method to allow interrupt threads to run during > the shutdown. Perhaps the current process priority should be elevated > so it is guaranteed to be scheduled after the last interrupt thread > instead of some unrelated process. > > Index: kern_shutdown.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/kern_shutdown.c,v > retrieving revision 1.80 > diff -u -r1.80 kern_shutdown.c > --- kern_shutdown.c 2000/09/07 01:32:51 1.80 > +++ kern_shutdown.c 2000/09/09 01:42:20 > @@ -220,6 +220,7 @@ > if (!cold && (howto & RB_NOSYNC) == 0 && waittime < 0) { > register struct buf *bp; > int iter, nbusy; > + int subiter; > > waittime = 0; > printf("\nsyncing disks... "); > @@ -247,7 +248,18 @@ > break; > printf("%d ", nbusy); > sync(&proc0, NULL); > - DELAY(50000 * iter); > + > + if (curproc != NULL) { curproc is never NULL anymore, so the if statement can be removed. > + for (subiter = 0; subiter < 50 * iter; subiter++) { > + mtx_enter(&sched_lock, MTX_SPIN); > + setrunqueue(curproc); > + mi_switch(); /* Allow interrupt threads to run */ > + mtx_exit(&sched_lock, MTX_SPIN); > + DELAY(1000); > + } > + } else > + DELAY(50000 * iter); > + > } > printf("\n"); > /* > > - Tor Egge > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Sun Sep 10 18: 2:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from jbloom.jbloom.org (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id 1C12437B443; Sun, 10 Sep 2000 18:02:42 -0700 (PDT) Received: from acm.org (localhost [127.0.0.1]) by jbloom.jbloom.org (8.11.0/8.11.0) with ESMTP id e8B12Sk28706; Sun, 10 Sep 2000 21:02:28 -0400 (EDT) (envelope-from bloom@acm.org) Message-ID: <39BC2F24.AE0DEB63@acm.org> Date: Sun, 10 Sep 2000 21:02:28 -0400 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway , wollman@FreeBSD.ORG Cc: Eric Hedberg , current@FreeBSD.ORG Subject: Re: Another broken buildworld References: 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 a pain. cvsup3 is the closest mirror to me. The only file I could find missing on cvsup3 was rsa_eay.c. Garrett, now that RSA has released the patent, would you be willing to add this file to the mirror on cvsup3? Jim Bloom bloom@acm.org Kris Kennaway wrote: > > On Sun, 10 Sep 2000, Eric Hedberg wrote: > > > OK, fresh cvsup (blew away the old /usr/src, slurped down a new one this > > afternoon). > > Don't cvsup from cvsup3, it doesnt carry a full crypto mirror. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 18:45:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id E3F0137B422 for ; Sun, 10 Sep 2000 18:45:31 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13YI67-0000Pd-00; Mon, 11 Sep 2000 02:09:23 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id CAA85378; Mon, 11 Sep 2000 02:09:23 +0100 (BST) (envelope-from ben) Date: Mon, 11 Sep 2000 02:09:22 +0100 From: Ben Smithurst To: Greg Lehey Cc: Mike Meyer , current@FreeBSD.ORG Subject: Re: page fault in sched_ithd Message-ID: <20000911020922.R77593@strontium.scientia.demon.co.uk> References: <20000909195525.E77593@strontium.scientia.demon.co.uk> <20000909210619.F77593@strontium.scientia.demon.co.uk> <14779.6851.88867.359611@guru.mired.org> <20000911094245.A19199@wantadilla.lemis.com> <20000911015427.Q77593@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="IU5/I01NYhRvwH70" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000911015427.Q77593@strontium.scientia.demon.co.uk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --IU5/I01NYhRvwH70 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Ben Smithurst wrote: > Greg Lehey wrote: > >> Sorry, I missed the beginning of this. Could somebody send me the >> patch? I'd assume that a relatively simple check would handle the >> issue, based on what I've seen here. > > I've lost the actual patch, I basically just added > > if (ir == NULL) > return; > > in sched_ithd() before it ever de-references ir. I've some up with a > slightly bigger patch which adds stray IRQ logging too, but I haven't > tested that yet. Here's the slightly bigger patch, which seems to be working fine so far. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D --IU5/I01NYhRvwH70 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ithread.diff" Index: ithread.c =================================================================== RCS file: /usr/cvs/src/sys/i386/isa/ithread.c,v retrieving revision 1.1 diff -u -r1.1 ithread.c --- ithread.c 2000/09/07 01:32:48 1.1 +++ ithread.c 2000/09/10 12:57:59 @@ -95,6 +95,8 @@ SYSINIT(start_softintr, SI_SUB_SOFTINTR, SI_ORDER_FIRST, start_softintr, NULL) +#define MAX_STRAY_LOG 5 + /* * Schedule a heavyweight interrupt process. This function is called * from the interrupt handlers Xintr. @@ -104,6 +106,7 @@ { int irq = (int) cookie; /* IRQ we're handling */ ithd *ir = ithds[irq]; /* and the process that does it */ + static int straycount[NHWI]; /* This used to be in icu_vector.s */ /* @@ -144,6 +147,20 @@ } #endif + if (ir == NULL) { + if (irq < NHWI) { + if (straycount[irq] < MAX_STRAY_LOG) { + printf("stray irq %d\n", irq); + if (++straycount[irq] == MAX_STRAY_LOG) + printf("got %d stray irq %d's: " + "not logging anymore\n", + MAX_STRAY_LOG, irq); + } + return; + } + panic("sched_ithd: ithds[%d] == NULL", irq); + } + /* * Set it_need so that if the thread is already running but close * to done, it will do another go-round. Then get the sched lock --IU5/I01NYhRvwH70-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 18:45:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 51DCF37B424 for ; Sun, 10 Sep 2000 18:45:38 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13YHrg-0000P2-00; Mon, 11 Sep 2000 01:54:28 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id BAA73050; Mon, 11 Sep 2000 01:54:28 +0100 (BST) (envelope-from ben) Date: Mon, 11 Sep 2000 01:54:27 +0100 From: Ben Smithurst To: Greg Lehey Cc: Mike Meyer , current@FreeBSD.ORG Subject: Re: page fault in sched_ithd Message-ID: <20000911015427.Q77593@strontium.scientia.demon.co.uk> References: <20000909195525.E77593@strontium.scientia.demon.co.uk> <20000909210619.F77593@strontium.scientia.demon.co.uk> <14779.6851.88867.359611@guru.mired.org> <20000911094245.A19199@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000911094245.A19199@wantadilla.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > Sorry, I missed the beginning of this. Could somebody send me the > patch? I'd assume that a relatively simple check would handle the > issue, based on what I've seen here. I've lost the actual patch, I basically just added if (ir == NULL) return; in sched_ithd() before it ever de-references ir. I've some up with a slightly bigger patch which adds stray IRQ logging too, but I haven't tested that yet. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 19:18:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 704BC37B43C for ; Sun, 10 Sep 2000 19:18:42 -0700 (PDT) Received: (qmail 12742 invoked from network); 11 Sep 2000 02:18:39 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 11 Sep 2000 02:18:39 -0000 Date: Mon, 11 Sep 2000 13:18:37 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Ben Smithurst Cc: current@FreeBSD.ORG Subject: Re: page fault in sched_ithd In-Reply-To: <20000909210619.F77593@strontium.scientia.demon.co.uk> 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, 9 Sep 2000, Ben Smithurst wrote: > After poking around a bit with remote GDB, this seems to be caused by a > stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM. > > The attached rather crude patch has "fixed" the problem for now, but > does anyone have any suggestions for a real fix? The stray interrupt handler needs to have a thread, or stray interrupts need to be handled as traps. Stray interrupts are more like NMIs than normal interrupts, and NMIs are already (mis)handled as traps. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 19:29:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with ESMTP id DC87137B424 for ; Sun, 10 Sep 2000 19:29:10 -0700 (PDT) Received: (from bugs@localhost) by freebsd.netcom.com (8.8.8+Sun/8.8.8) id VAA25145 for freebsd-current@freebsd.org; Sun, 10 Sep 2000 21:29:20 -0500 (CDT) From: Mark Hittinger Message-Id: <200009110229.VAA25145@freebsd.netcom.com> Subject: make world libcrypto Undefined symbol "RSA_PKCS1" To: freebsd-current@freebsd.org Date: Sun, 10 Sep 2000 21:29:20 -0500 (CDT) X-Mailer: ELM [version 2.5 PL2] 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 It may be because of something screwy that I did, I had been cvsup'ing from cvsup3. Saw the note about 3 not having a full crypto mirror so I tried a cvsup from 2 and make world completed, but when running ssh I get this: /usr/libexec/ld-elf.so.1: /usr/lib/libcrypto.so.1: Undefined symbol "RSA_PKCS1" Restoring a libcrypto.so.1 from an earlier backup gets things going again. Just blue skying for a minute here, but I wonder if it might be possible to make a short list of critical utilities that depend on some of these critical libraries. It would be quite helpful to test the libraries with the criticial utilities prior to installing them. How many times have we blown our libc.so and then we are really inconvenienced? This one is not as bad as a libc.so hose though. Something that could invoke a dummy image load of /usr/bin/login against the soon to be installed libc, and if it got undefined symbols, bail on the libc installation. I bet this would save some of us infrequent grief! FYI Mark Hittinger Earthlink bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 19:34:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 6C1CC37B423; Sun, 10 Sep 2000 19:34:42 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8B2YYt26868; Mon, 11 Sep 2000 12:04:34 +0930 (CST) (envelope-from grog) Date: Mon, 11 Sep 2000 12:04:34 +0930 From: Greg Lehey To: Bruce Evans Cc: Ben Smithurst , current@FreeBSD.ORG Subject: Re: page fault in sched_ithd Message-ID: <20000911120434.C19431@wantadilla.lemis.com> References: <20000909210619.F77593@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bde@zeta.org.au on Mon, Sep 11, 2000 at 01:18:37PM +1100 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 11 September 2000 at 13:18:37 +1100, Bruce Evans wrote: > On Sat, 9 Sep 2000, Ben Smithurst wrote: > >> After poking around a bit with remote GDB, this seems to be caused by a >> stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM. >> >> The attached rather crude patch has "fixed" the problem for now, but >> does anyone have any suggestions for a real fix? > > The stray interrupt handler needs to have a thread, or stray interrupts > need to be handled as traps. Stray interrupts are more like NMIs than > normal interrupts, and NMIs are already (mis)handled as traps. Independently of that, we need to be able to survive a spurious interrupt on any IRQ. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 19:45:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 95A5037B43C for ; Sun, 10 Sep 2000 19:45:29 -0700 (PDT) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.0/8.11.0) with ESMTP id e8B2jO400259 for ; Sun, 10 Sep 2000 19:45:28 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <4.3.2.7.2.20000910192526.00b280e0@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 10 Sep 2000 19:45:25 -0700 To: current@freebsd.org From: Manfred Antar Subject: New Fatal trap in Current SMP (random.dev changes ??) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From a new kernel compiled from sources current 7:30 pm 9/10/00 pacific time Although the first occurrence happened this morning after compiling a kernel after the random dev changes. The system boots and mounts disks. When it gets to this point: Additional routing options: TCP extensions=NO TCP keepalive=YES. routing daemons:. I think the random dev kicks in at this point Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 0c000000 fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8:0xc014f280 stack pointer = 0x10:0xc9a74f84 frame pointer = 0x10:0xc9a74f9c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1,def 32 1,gran 1 processor flags = interrupt enabled, resume, IOPL = 0 current process = 2 (random) trap number = 12 panic: page fault cpuid = 1; lapic.id = 0x000000 boot() called on cpu#1 syncing disks....... The machine then is frozen and needs a reset to work again the debugger is unavailable Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 20: 5:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 9F5A637B423 for ; Sun, 10 Sep 2000 20:05:18 -0700 (PDT) Received: (qmail 17588 invoked from network); 11 Sep 2000 03:05:11 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 11 Sep 2000 03:05:11 -0000 Date: Mon, 11 Sep 2000 14:05:08 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Valentin Nechayev Cc: freebsd-current@FreeBSD.ORG Subject: Re: load average is 1 when no processes active; etc. In-Reply-To: <20000910153643.A799@nn.kiev.ua> 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, 10 Sep 2000, Valentin Nechayev wrote: > `top -I' output: > > ==={ > last pid: 811; load averages: 1.01, 0.97, 0.67 up 0+00:16:12 23:26:26 This is because the idle process is always running (see "ps lax" outout). Perhaps the bug is that top doesn't show the idle process or other interesting kernel processes like the new interrupt processes. > The same system has another strangeness - `microuptime() went backwards': > > ==={ /var/run/dmesg.boot >... > IPv6 packet filtering initialized, default to accept, logging limited to 100 packets/entry > IPsec: Initialized Security Association Processing. > ncp_load: [210-213] > IP Filter: v3.4.9 initialized. Default = pass all, Logging = enabled > microuptime() went backwards (1.3891137 -> 0.596214) > microuptime() went backwards (1.3891137 -> 0.596655) > ... I get these at boot time on one machine but not on another very similar machine, and often after messing around with ddb. TSC timecounter in all cases. I think they are not a serious problem or related to old timecounter bugs, but they may be related to old bugs setting `switchtime'. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 20:16:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1A77237B422 for ; Sun, 10 Sep 2000 20:16:37 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id UAA31476; Sun, 10 Sep 2000 20:16:23 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009110316.UAA31476@pike.osd.bsdi.com> Subject: Re: New Fatal trap in Current SMP (random.dev changes ??) In-Reply-To: <4.3.2.7.2.20000910192526.00b280e0@pozo.com> from Manfred Antar at "Sep 10, 2000 07:45:25 pm" To: Manfred Antar Date: Sun, 10 Sep 2000 20:16:23 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Manfred Antar wrote: > >From a new kernel compiled from sources current 7:30 pm 9/10/00 pacific time > Although the first occurrence happened this morning after compiling a kernel > after the random dev changes. > The system boots and mounts disks. When it gets to this point: > Additional routing options: TCP extensions=NO TCP keepalive=YES. > routing daemons:. > I think the random dev kicks in at this point > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; lapic.id = 0c000000 > fault virtual address = 0x2c > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc014f280 > stack pointer = 0x10:0xc9a74f84 > frame pointer = 0x10:0xc9a74f9c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1,def 32 1,gran 1 > processor flags = interrupt enabled, resume, IOPL = 0 > current process = 2 (random) > trap number = 12 > panic: page fault > cpuid = 1; lapic.id = 0x000000 > boot() called on cpu#1 > > syncing disks....... > > The machine then is frozen and needs a reset to work again > the debugger is unavailable ddb works fine here with this new trap, but I can't get remote gdb to work to save my life. I think that remote gdb must not like me or something. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Sun Sep 10 20:30:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 0C37337B423 for ; Sun, 10 Sep 2000 20:30:20 -0700 (PDT) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.0/8.11.0) with ESMTP id e8B3UEg00281; Sun, 10 Sep 2000 20:30:17 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <4.3.2.7.2.20000910202520.00b17498@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 10 Sep 2000 20:30:14 -0700 To: John Baldwin From: Manfred Antar Subject: Re: New Fatal trap in Current SMP (random.dev changes ??) Cc: current@FreeBSD.ORG In-Reply-To: <200009110316.UAA31476@pike.osd.bsdi.com> References: <4.3.2.7.2.20000910192526.00b280e0@pozo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:16 PM 9/10/2000 -0700, John Baldwin wrote: >Manfred Antar wrote: >> >From a new kernel compiled from sources current 7:30 pm 9/10/00 pacific time >> Although the first occurrence happened this morning after compiling a kernel >> after the random dev changes. >> The system boots and mounts disks. When it gets to this point: >> Additional routing options: TCP extensions=NO TCP keepalive=YES. >> routing daemons:. >> I think the random dev kicks in at this point >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 1; lapic.id = 0c000000 >> fault virtual address = 0x2c >> fault code = supervisor read, page not present >> instruction pointer = 0x8:0xc014f280 >> stack pointer = 0x10:0xc9a74f84 >> frame pointer = 0x10:0xc9a74f9c >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1,def 32 1,gran 1 >> processor flags = interrupt enabled, resume, IOPL = 0 >> current process = 2 (random) >> trap number = 12 >> panic: page fault >> cpuid = 1; lapic.id = 0x000000 >> boot() called on cpu#1 >> >> syncing disks....... >> >> The machine then is frozen and needs a reset to work again >> the debugger is unavailable I backed out to the old versions of the random dev files: /sys/dev/randomdev: harvest.c randomdev.c yarrow.c yarrow.h /sys/sys: random.h And the panic goes away Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 20:48:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 55F9337B422 for ; Sun, 10 Sep 2000 20:48:29 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id UAA31972; Sun, 10 Sep 2000 20:48:16 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009110348.UAA31972@pike.osd.bsdi.com> Subject: Re: New Fatal trap in Current SMP (random.dev changes ??) In-Reply-To: <4.3.2.7.2.20000910202520.00b17498@pozo.com> from Manfred Antar at "Sep 10, 2000 08:30:14 pm" To: Manfred Antar Date: Sun, 10 Sep 2000 20:48:16 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Manfred Antar wrote: > At 08:16 PM 9/10/2000 -0700, John Baldwin wrote: > >Manfred Antar wrote: > >> >From a new kernel compiled from sources current 7:30 pm 9/10/00 pacific time > >> Although the first occurrence happened this morning after compiling a kernel > >> after the random dev changes. > >> The system boots and mounts disks. When it gets to this point: > >> Additional routing options: TCP extensions=NO TCP keepalive=YES. > >> routing daemons:. > >> I think the random dev kicks in at this point > >> > >> Fatal trap 12: page fault while in kernel mode > >> cpuid = 1; lapic.id = 0c000000 > >> fault virtual address = 0x2c > >> fault code = supervisor read, page not present > >> instruction pointer = 0x8:0xc014f280 > >> stack pointer = 0x10:0xc9a74f84 > >> frame pointer = 0x10:0xc9a74f9c > >> code segment = base 0x0, limit 0xfffff, type 0x1b > >> = DPL 0, pres 1,def 32 1,gran 1 > >> processor flags = interrupt enabled, resume, IOPL = 0 > >> current process = 2 (random) > >> trap number = 12 > >> panic: page fault > >> cpuid = 1; lapic.id = 0x000000 > >> boot() called on cpu#1 > >> > >> syncing disks....... > >> > >> The machine then is frozen and needs a reset to work again > >> the debugger is unavailable > I backed out to the old versions of the random dev files: > /sys/dev/randomdev: > harvest.c > randomdev.c > yarrow.c > yarrow.h > /sys/sys: > random.h > > And the panic goes away > Manfred I've got it fixed. The code is using TAILQ_REMOVE and TAILQ_FIRST to pull entries out of a tailq while it is walking it via TAILQ_FOREACH. Changing it to use a while(!TAILQ_EMPTY) instead of using TAILQ_FOREACH fixes it. I'll be committing the fix in just a sec.. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Sun Sep 10 21:14:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 25BF237B423; Sun, 10 Sep 2000 21:14:10 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id VAA32467; Sun, 10 Sep 2000 21:14:02 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009110414.VAA32467@pike.osd.bsdi.com> Subject: Re: cvs commit: src/sys/dev/randomdev yarrow.c In-Reply-To: <200009110409.VAA11720@freefall.freebsd.org> from John Baldwin at "Sep 10, 2000 09:09:08 pm" To: John Baldwin Date: Sun, 10 Sep 2000 21:14:02 -0700 (PDT) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > jhb 2000/09/10 21:09:08 PDT > > Modified files: > sys/dev/randomdev yarrow.c > Log: > - Use RFHIGHPID when creating the kthread to get a more sensible pid. > - Don't fake walking a tailq. Instead, use a while loop that pulls items > off the head of the queue while the queue is not empty. This should fix the recent kernel panics during boot from randomdev... -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Sun Sep 10 21:31: 7 2000 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 3966337B422 for ; Sun, 10 Sep 2000 21:31:02 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id PAA06627; Mon, 11 Sep 2000 15:24:26 +1100 Date: Mon, 11 Sep 2000 15:24:24 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: Tor.Egge@fast.no, current@FreeBSD.ORG Subject: Re: Dirty buffers on reboot.. In-Reply-To: <200009110049.RAA28932@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 10 Sep 2000, John Baldwin wrote: > Tor.Egge@fast.no wrote: > > > Ok, an update on the dirty buffers on reboot: > > > > > > If you use the reboot command, you will get dirty buffers. If you use > > > 'shutdown -r now' instead, you won't get dirty buffers. Thus, as a workaround > > > for now, use the shutdown command to reboot your box until we can track this > > > down. I haven't noticed this yet. I normally use reboot. > > I suggest using some method to allow interrupt threads to run during > > the shutdown. Perhaps the current process priority should be elevated > > so it is guaranteed to be scheduled after the last interrupt thread > > instead of some unrelated process. I'm surprised they get stopped. At least writing buffers in sync() depends on interrupts working. There is a problem for syncing in panic(). Interrupts (and tsleep()) shouldn't work in panic(), especially for panics in interrupt context. They used to sort of work by doing splx(safepri). This corresponds to blowing open all locks. > > RCS file: /home/ncvs/src/sys/kern/kern_shutdown.c,v > > retrieving revision 1.80 > > ... > > @@ -247,7 +248,18 @@ > > break; > > printf("%d ", nbusy); > > sync(&proc0, NULL); > > - DELAY(50000 * iter); > > + > > + if (curproc != NULL) { > > curproc is never NULL anymore, so the if statement can be removed. Can't it happen for panics while cold? The code "if (p && p != idleproc ...)" in uprintf() seems to be to handle this. We still have lots of (p == NULL) checks where coldness probably isn't an issue. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 21:37:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 1D86637B423 for ; Sun, 10 Sep 2000 21:37:39 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id C2EE12876C; Mon, 11 Sep 2000 11:37:34 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id B9A4928766; Mon, 11 Sep 2000 11:37:34 +0700 (ALMST) Date: Mon, 11 Sep 2000 11:37:34 +0700 (ALMST) From: Boris Popov To: John Baldwin Cc: Manfred Antar , current@FreeBSD.ORG Subject: Re: New Fatal trap in Current SMP (random.dev changes ??) In-Reply-To: <200009110316.UAA31476@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 10 Sep 2000, John Baldwin wrote: > > I think the random dev kicks in at this point > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 1; lapic.id = 0c000000 > > fault virtual address = 0x2c > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xc014f280 > > stack pointer = 0x10:0xc9a74f84 > > frame pointer = 0x10:0xc9a74f9c > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1,def 32 1,gran 1 > > processor flags = interrupt enabled, resume, IOPL = 0 > > current process = 2 (random) > > trap number = 12 > > panic: page fault > > cpuid = 1; lapic.id = 0x000000 > > boot() called on cpu#1 > > > > syncing disks....... > > > > The machine then is frozen and needs a reset to work again > > the debugger is unavailable > > ddb works fine here with this new trap, but I can't get remote gdb to work > to save my life. I think that remote gdb must not like me or something. Yes, after trap is occured ddb works. But it is impossible to continue from ddb because after typing 'c' machine becomes frozen. The same thing occur after any other panic (this is with SMP kernel). -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 21:40: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 79AA237B42C for ; Sun, 10 Sep 2000 21:40:00 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id VAA32934; Sun, 10 Sep 2000 21:39:28 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009110439.VAA32934@pike.osd.bsdi.com> Subject: Re: New Fatal trap in Current SMP (random.dev changes ??) In-Reply-To: from Boris Popov at "Sep 11, 2000 11:37:34 am" To: Boris Popov Date: Sun, 10 Sep 2000 21:39:28 -0700 (PDT) Cc: Manfred Antar , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Boris Popov wrote: > On Sun, 10 Sep 2000, John Baldwin wrote: > > > > I think the random dev kicks in at this point > > > > > > Fatal trap 12: page fault while in kernel mode > > > cpuid = 1; lapic.id = 0c000000 > > > fault virtual address = 0x2c > > > fault code = supervisor read, page not present > > > instruction pointer = 0x8:0xc014f280 > > > stack pointer = 0x10:0xc9a74f84 > > > frame pointer = 0x10:0xc9a74f9c > > > code segment = base 0x0, limit 0xfffff, type 0x1b > > > = DPL 0, pres 1,def 32 1,gran 1 > > > processor flags = interrupt enabled, resume, IOPL = 0 > > > current process = 2 (random) > > > trap number = 12 > > > panic: page fault > > > cpuid = 1; lapic.id = 0x000000 > > > boot() called on cpu#1 > > > > > > syncing disks....... > > > > > > The machine then is frozen and needs a reset to work again > > > the debugger is unavailable > > > > ddb works fine here with this new trap, but I can't get remote gdb to work > > to save my life. I think that remote gdb must not like me or something. > > Yes, after trap is occured ddb works. But it is impossible to > continue from ddb because after typing 'c' machine becomes frozen. > The same thing occur after any other panic (this is with SMP kernel). It only does this in cases when the sched_lock is held by the CPU that traps. If the trapping CPU does not hold sched_lock when it faults, then you can do continue and steps as normal. I _think_ that maybe having the debugger release sched_lock when it enters the debugger and acquire it on the way out would work, but I'm not sure, and I haven't explored all the interactions of that yet. > -- > Boris Popov > http://www.butya.kz/~bp/ -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Sun Sep 10 23:43:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 1B12F37B424 for ; Sun, 10 Sep 2000 23:43:40 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13YNJV-00020i-00; Mon, 11 Sep 2000 08:43:34 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e8B6gu011649; Mon, 11 Sep 2000 08:42:56 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009110642.e8B6gu011649@grimreaper.grondar.za> To: John Baldwin Cc: Manfred Antar , current@FreeBSD.ORG Subject: Re: New Fatal trap in Current SMP (random.dev changes ??) References: <200009110348.UAA31972@pike.osd.bsdi.com> In-Reply-To: <200009110348.UAA31972@pike.osd.bsdi.com> ; from John Baldwin "Sun, 10 Sep 2000 20:48:16 MST." Date: Mon, 11 Sep 2000 08:42:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > And the panic goes away > > Manfred > > I've got it fixed. The code is using TAILQ_REMOVE and TAILQ_FIRST to > pull entries out of a tailq while it is walking it via TAILQ_FOREACH. > Changing it to use a while(!TAILQ_EMPTY) instead of using TAILQ_FOREACH > fixes it. I'll be committing the fix in just a sec.. Thanks, John! :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 10 23:44:57 2000 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 2738737B422; Sun, 10 Sep 2000 23:44:51 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id RAA18672; Mon, 11 Sep 2000 17:44:45 +1100 Date: Mon, 11 Sep 2000 17:44:43 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Greg Lehey Cc: Ben Smithurst , current@FreeBSD.ORG Subject: Re: page fault in sched_ithd In-Reply-To: <20000911120434.C19431@wantadilla.lemis.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, 11 Sep 2000, Greg Lehey wrote: > On Monday, 11 September 2000 at 13:18:37 +1100, Bruce Evans wrote: > > The stray interrupt handler needs to have a thread, or stray interrupts > > need to be handled as traps. Stray interrupts are more like NMIs than > > normal interrupts, and NMIs are already (mis)handled as traps. > > Independently of that, we need to be able to survive a spurious > interrupt on any IRQ. Not really independent. Spurious interrupts on "any" IRQ can't happen, interrupts without a handler are masked. Spurious interrupts on irq7/irq15 can happen because normal masking by the irq7/irq15 bit in the ICU doesn't apply (I think they can happen even if all bits in the ICU mask are set). They are like an NMI in this respect. The old code accidentally had some defense against nested spurious interrupts. Masking in the ICU doesn't work, but masking in `cpl' happens to do the right thing (actually the same wrong thing as for non-nested spurious interrupts). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 0: 1:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id A3E5E37B423 for ; Mon, 11 Sep 2000 00:01:35 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id XAA36296; Sun, 10 Sep 2000 23:55:54 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009110655.XAA36296@pike.osd.bsdi.com> Subject: Re: Dirty buffers on reboot.. In-Reply-To: from Bruce Evans at "Sep 11, 2000 03:24:24 pm" To: Bruce Evans Date: Sun, 10 Sep 2000 23:55:54 -0700 (PDT) Cc: Tor.Egge@fast.no, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Sun, 10 Sep 2000, John Baldwin wrote: > > > Tor.Egge@fast.no wrote: > > > > Ok, an update on the dirty buffers on reboot: > > > > > > > > If you use the reboot command, you will get dirty buffers. If you use > > > > 'shutdown -r now' instead, you won't get dirty buffers. Thus, as a workaround > > > > for now, use the shutdown command to reboot your box until we can track this > > > > down. > > I haven't noticed this yet. I normally use reboot. It is probably a timing issue more than anything else. :-/ > > > I suggest using some method to allow interrupt threads to run during > > > the shutdown. Perhaps the current process priority should be elevated > > > so it is guaranteed to be scheduled after the last interrupt thread > > > instead of some unrelated process. > > I'm surprised they get stopped. At least writing buffers in sync() > depends on interrupts working. There is a problem for syncing in > panic(). Interrupts (and tsleep()) shouldn't work in panic(), > especially for panics in interrupt context. They used to sort of > work by doing splx(safepri). This corresponds to blowing open all > locks. Hmm. By calling mi_switch() we end up giving up both shced_lock and Giant, so that this is equivalent for the time being to "blowing open all the locks". > > > RCS file: /home/ncvs/src/sys/kern/kern_shutdown.c,v > > > retrieving revision 1.80 > > > ... > > > @@ -247,7 +248,18 @@ > > > break; > > > printf("%d ", nbusy); > > > sync(&proc0, NULL); > > > - DELAY(50000 * iter); > > > + > > > + if (curproc != NULL) { > > > > curproc is never NULL anymore, so the if statement can be removed. > > Can't it happen for panics while cold? The code "if (p && p != idleproc ...)" > in uprintf() seems to be to handle this. We still have lots of (p == NULL) > checks where coldness probably isn't an issue. Hmmmm. At least on the x86, curproc is now set to proc0 before we probe to see how much memory we have in init386(). In fact, we set curproc up right after setting up the GDT, and before both the ldt and idt, so at least on x86, we won't get a trap with curproc == NULL. :) On the alpha I'm not as sure. Hmm, after looking, we set curproc in alpha_init(), but we do it much later on. I'm not sure if we have enabled interrupts at that point or not. > Bruce -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Sep 11 0:25:25 2000 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 178F337B423 for ; Mon, 11 Sep 2000 00:25:21 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id SAA21275; Mon, 11 Sep 2000 18:21:03 +1100 Date: Mon, 11 Sep 2000 18:21:01 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: Boris Popov , Manfred Antar , current@FreeBSD.ORG Subject: Re: New Fatal trap in Current SMP (random.dev changes ??) In-Reply-To: <200009110439.VAA32934@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 10 Sep 2000, John Baldwin wrote: > Boris Popov wrote: > > Yes, after trap is occured ddb works. But it is impossible to > > continue from ddb because after typing 'c' machine becomes frozen. > > The same thing occur after any other panic (this is with SMP kernel). > > It only does this in cases when the sched_lock is held by the CPU that traps. > If the trapping CPU does not hold sched_lock when it faults, then you can > do continue and steps as normal. I _think_ that maybe having the debugger > release sched_lock when it enters the debugger and acquire it on the way out > would work, but I'm not sure, and I haven't explored all the interactions of > that yet. ddb shouldn't (appear to) go anywhere normal locking (since it may be invoked on locking code). Similarly for the low-level console drivers. (they may be invoked by ddb or for debugging printfs or panics in locking code). Making things only appear not to go near locking code is too hard. You would have to release and reaquire not only locks, but partially-acquired locks. A special ddb lock is probably required for SMP. Booting with -d is also broken here (it hangs). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 0:26: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 1630937B423; Mon, 11 Sep 2000 00:26:03 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8B7PwS63667; Mon, 11 Sep 2000 16:55:58 +0930 (CST) (envelope-from grog) Date: Mon, 11 Sep 2000 16:55:58 +0930 From: Greg Lehey To: Bruce Evans Cc: Ben Smithurst , current@FreeBSD.ORG Subject: Re: page fault in sched_ithd Message-ID: <20000911165558.E19431@wantadilla.lemis.com> References: <20000911120434.C19431@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bde@zeta.org.au on Mon, Sep 11, 2000 at 05:44:43PM +1100 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 11 September 2000 at 17:44:43 +1100, Bruce Evans wrote: > On Mon, 11 Sep 2000, Greg Lehey wrote: > >> On Monday, 11 September 2000 at 13:18:37 +1100, Bruce Evans wrote: >>> The stray interrupt handler needs to have a thread, or stray interrupts >>> need to be handled as traps. Stray interrupts are more like NMIs than >>> normal interrupts, and NMIs are already (mis)handled as traps. >> >> Independently of that, we need to be able to survive a spurious >> interrupt on any IRQ. > > Not really independent. Spurious interrupts on "any" IRQ can't > happen, interrupts without a handler are masked. Right, I had forgotten that. But it's still defensive programming to DTRT if we get one, especially if it doesn't cost anything. > Spurious interrupts on irq7/irq15 can happen because normal masking > by the irq7/irq15 bit in the ICU doesn't apply (I think they can > happen even if all bits in the ICU mask are set). They are like an > NMI in this respect. Strange. Does this still happen on modern hardware? > The old code accidentally had some defense against nested spurious > interrupts. Masking in the ICU doesn't work, but masking in `cpl' > happens to do the right thing (actually the same wrong thing as for > non-nested spurious interrupts). We don't have a cpl any more. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 0:35:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 501ED37B423 for ; Mon, 11 Sep 2000 00:35:45 -0700 (PDT) Received: (qmail 14394 invoked from network); 11 Sep 2000 07:35:42 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 11 Sep 2000 07:35:42 -0000 Date: Mon, 11 Sep 2000 18:35:40 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: Manfred Antar , current@FreeBSD.ORG Subject: Re: New Fatal trap in Current SMP (random.dev changes ??) In-Reply-To: <200009110348.UAA31972@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 10 Sep 2000, John Baldwin wrote: > I've got it fixed. The code is using TAILQ_REMOVE and TAILQ_FIRST to > pull entries out of a tailq while it is walking it via TAILQ_FOREACH. > Changing it to use a while(!TAILQ_EMPTY) instead of using TAILQ_FOREACH > fixes it. I'll be committing the fix in just a sec.. This is a good excuse for terminating the FOREACH obfuscations :). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 1:11:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id F174F37B424 for ; Mon, 11 Sep 2000 01:11:47 -0700 (PDT) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 9B99D5D35; Mon, 11 Sep 2000 10:11:46 +0200 (CEST) Received: by hcswork.hcs.de (Postfix, from userid 200) id 37AFE3F89; Mon, 11 Sep 2000 10:11:46 +0200 (METDST) Subject: Re: load average is 1 when no processes active; etc. In-Reply-To: from Bruce Evans at "Sep 11, 0 02:05:08 pm" To: bde@zeta.org.au (Bruce Evans) Date: Mon, 11 Sep 2000 10:11:46 +0200 (METDST) Cc: netch@segfault.kiev.ua, freebsd-current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 769 Message-Id: <20000911081146.37AFE3F89@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just for the record, i here have a system cvsupped and built FreeBSD 5.0-CURRENT #0: Sat Sep 9 13:46:17 CEST 2000 which has a constant load average of 1.00 and higher in uptime, top, and systat. The load is already 1.00 or above when the first shell prompt after a boot appears. I've already tried to kill all processes in reach but the load never drops below 1.00 - even in single user mode. Other than this the machine is running fine. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 2: 2:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1CD4637B423; Mon, 11 Sep 2000 02:02:30 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id CAA56190; Mon, 11 Sep 2000 02:02:30 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 11 Sep 2000 02:02:29 -0700 (PDT) From: Kris Kennaway To: Mark Hittinger Cc: freebsd-current@freebsd.org Subject: Re: make world libcrypto Undefined symbol "RSA_PKCS1" In-Reply-To: <200009110229.VAA25145@freebsd.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 10 Sep 2000, Mark Hittinger wrote: > > It may be because of something screwy that I did, I had been cvsup'ing from > cvsup3. Saw the note about 3 not having a full crypto mirror so I tried a > cvsup from 2 and make world completed, but when running ssh I get this: > > /usr/libexec/ld-elf.so.1: /usr/lib/libcrypto.so.1: Undefined symbol "RSA_PKCS1" > > Restoring a libcrypto.so.1 from an earlier backup gets things going again. > > Just blue skying for a minute here, but I wonder if it might be possible to > make a short list of critical utilities that depend on some of these > critical libraries. It would be quite helpful to test the libraries with > the criticial utilities prior to installing them. How many times have we > blown our libc.so and then we are really inconvenienced? This one is not > as bad as a libc.so hose though. Every library is critical for something..the key is to not make mistakes, or to have a backup plan when you do :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 2: 8:23 2000 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 ACC4E37B423; Mon, 11 Sep 2000 02:08:16 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id UAA27663; Mon, 11 Sep 2000 20:08:10 +1100 Date: Mon, 11 Sep 2000 20:08:08 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Greg Lehey Cc: Ben Smithurst , current@FreeBSD.ORG Subject: Re: page fault in sched_ithd In-Reply-To: <20000911165558.E19431@wantadilla.lemis.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, 11 Sep 2000, Greg Lehey wrote: > On Monday, 11 September 2000 at 17:44:43 +1100, Bruce Evans wrote: > > On Mon, 11 Sep 2000, Greg Lehey wrote: > >> Independently of that, we need to be able to survive a spurious > >> interrupt on any IRQ. > > > > Not really independent. Spurious interrupts on "any" IRQ can't > > happen, interrupts without a handler are masked. > > Right, I had forgotten that. But it's still defensive programming to > DTRT if we get one, especially if it doesn't cost anything. It's a waste of time to check your own args, and not free here. > > Spurious interrupts on irq7/irq15 can happen because normal masking > > by the irq7/irq15 bit in the ICU doesn't apply (I think they can > > happen even if all bits in the ICU mask are set). They are like an > > NMI in this respect. > > Strange. Does this still happen on modern hardware? Modern ICUs are hopefully bug for bug compatible with old ones. > > The old code accidentally had some defense against nested spurious > > interrupts. Masking in the ICU doesn't work, but masking in `cpl' > > happens to do the right thing (actually the same wrong thing as for > > non-nested spurious interrupts). > > We don't have a cpl any more. That's why I wrote "the old code ... had ...". Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 2:16:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id A412B37B422 for ; Mon, 11 Sep 2000 02:16:18 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 13YPhG-0001rw-0C; Mon, 11 Sep 2000 09:16:15 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA03103; Mon, 11 Sep 2000 10:16:55 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 11 Sep 2000 10:16:29 +0100 (BST) From: Doug Rabson To: John Baldwin Cc: Bruce Evans , Tor.Egge@fast.no, current@freebsd.org Subject: Re: Dirty buffers on reboot.. In-Reply-To: <200009110655.XAA36296@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 10 Sep 2000, John Baldwin wrote: > > Hmmmm. At least on the x86, curproc is now set to proc0 before we probe > to see how much memory we have in init386(). In fact, we set curproc up > right after setting up the GDT, and before both the ldt and idt, so at least > on x86, we won't get a trap with curproc == NULL. :) On the alpha I'm not > as sure. Hmm, after looking, we set curproc in alpha_init(), but we do > it much later on. I'm not sure if we have enabled interrupts at that point > or not. Interrupts are certainly not enabled in alpha_init() - this is the earliest part of the alpha boot sequence. After alpha_init() returns, we switch to using proc0's stack for the first time (alpha_init() runs on the bootstrap stack) and call mi_startup() to get the rest of the kernel going. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8348 3944 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 2:26:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 1637A37B422 for ; Mon, 11 Sep 2000 02:26:42 -0700 (PDT) Received: (from netch@localhost) by segfault.kiev.ua (8) id MKC21646; Mon, 11 Sep 2000 12:26:15 +0300 (EEST) (envelope-from netch) Date: Mon, 11 Sep 2000 12:26:14 +0300 From: Valentin Nechayev To: Bruce Evans Cc: freebsd-current@freebsd.org Subject: Re: load average is 1 when no processes active; etc. Message-ID: <20000911122614.A21310@netch.kiev.ua> Reply-To: netch@segfault.kiev.ua References: <20000910153643.A799@nn.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bde@zeta.org.au on Mon, Sep 11, 2000 at 03:09:02AM +0000 X-42: On Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Bruce Evans! Mon, Sep 11, 2000 at 03:09:02, bde wrote about "Re: load average is 1 when no processes active; etc.": > > `top -I' output: > > > > ==={ > > last pid: 811; load averages: 1.01, 0.97, 0.67 up 0+00:16:12 23:26:26 > > This is because the idle process is always running (see "ps lax" outout). > Perhaps the bug is that top doesn't show the idle process or other interesting > kernel processes like the new interrupt processes. top does nothing to determine LA except getting sysctl "vm.loadavg", isn't it? ("uptime" and "w" says the same avenrun/LA values.) Imho, idle process should not be determined as always running, and idle process state should be fixed. > > IP Filter: v3.4.9 initialized. Default = pass all, Logging = enabled > > microuptime() went backwards (1.3891137 -> 0.596214) > > microuptime() went backwards (1.3891137 -> 0.596655) > > ... > > I get these at boot time on one machine but not on another very similar > machine, and often after messing around with ddb. TSC timecounter in > all cases. I think they are not a serious problem or related to old > timecounter bugs, but they may be related to old bugs setting `switchtime'. What information of my hardware should be reported additionally? /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 3: 1:56 2000 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 CDAAF37B423 for ; Mon, 11 Sep 2000 03:01:51 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id VAA30937; Mon, 11 Sep 2000 21:01:34 +1100 Date: Mon, 11 Sep 2000 21:01:33 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Valentin Nechayev Cc: freebsd-current@freebsd.org Subject: Re: load average is 1 when no processes active; etc. In-Reply-To: <20000911122614.A21310@netch.kiev.ua> 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, 11 Sep 2000, Valentin Nechayev wrote: > > > `top -I' output: > > > > > > ==={ > > > last pid: 811; load averages: 1.01, 0.97, 0.67 up 0+00:16:12 23:26:26 > > > > This is because the idle process is always running (see "ps lax" outout). > > Perhaps the bug is that top doesn't show the idle process or other interesting > > kernel processes like the new interrupt processes. > > top does nothing to determine LA except getting sysctl "vm.loadavg", isn't it? > ("uptime" and "w" says the same avenrun/LA values.) > Imho, idle process should not be determined as always running, > and idle process state should be fixed. Well, the kernel just doesn't treat it specially, so it gets counted in the load average. I'm not sure if the interrupt and other kernel processes are counted. Since they do useful work, they should be. The idle process does the not so useful work of heating the cpu, since it no longer halts or runs vm_page_zero_idle(). > > > IP Filter: v3.4.9 initialized. Default = pass all, Logging = enabled > > > microuptime() went backwards (1.3891137 -> 0.596214) > > > microuptime() went backwards (1.3891137 -> 0.596655) > > > ... > > > > I get these at boot time on one machine but not on another very similar > > machine, and often after messing around with ddb. TSC timecounter in > > all cases. I think they are not a serious problem or related to old > > timecounter bugs, but they may be related to old bugs setting `switchtime'. > > What information of my hardware should be reported additionally? None for this problem. It's a general problem. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 3: 4:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id 47C7F37B422 for ; Mon, 11 Sep 2000 03:04:18 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e8B9vjG73281 for ; Mon, 11 Sep 2000 18:57:46 +0900 (JST) Date: Mon, 11 Sep 2000 18:57:45 +0900 Message-ID: <7mem2rqmhy.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: PAM in ftpd.c User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) 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 I don't know around PAM coding, but below topic is there in Japanese mailing list. o After setting /etc/skey.access, cannot login to ftpd via UNIX password. There is a patch to fix this problem in that mailing list. Could someone review and commit it? (Submitted by: hirohito@youko-house.ne.jp) *** ftpd.c.orig Mon Jun 26 14:44:43 2000 --- ftpd.c Sat Sep 9 20:06:24 2000 *************** *** 1109,1114 **** --- 1109,1126 ---- syslog(LOG_ERR, "pam_start: %s", pam_strerror(pamh, e)); return -1; } + e = pam_set_item( pamh, PAM_TTY, ttyname(0) ); + if( e != PAM_SUCCESS ) + { + syslog( LOG_ERR, "pam_set_item(PAM_TTY): %s", pam_strerror( pamh, e ) ); + return -1; + } + e = pam_set_item( pamh, PAM_RHOST, remotehost ); + if( e != PAM_SUCCESS ) + { + syslog( LOG_ERR, "pam_set_item(PAM_RHOST): %s", pam_strerror( pamh, e ) ); + return -1; + } e = pam_authenticate(pamh, 0); switch (e) { -- Jun Kuriyama // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 4:14:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id BF6DB37B423 for ; Mon, 11 Sep 2000 04:14:10 -0700 (PDT) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.109]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id OAA19169; Mon, 11 Sep 2000 14:14:04 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.0/8.9.3) with ESMTP id e8BBE1R12515; Mon, 11 Sep 2000 14:14:01 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <39BCBE78.7D17B24B@FreeBSD.org> Date: Mon, 11 Sep 2000 14:14:00 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Bruce Evans Cc: Valentin Nechayev , freebsd-current@FreeBSD.org Subject: Re: load average is 1 when no processes active; etc. References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Mon, 11 Sep 2000, Valentin Nechayev wrote: > > > > > `top -I' output: > > > > > > > > ==={ > > > > last pid: 811; load averages: 1.01, 0.97, 0.67 up 0+00:16:12 23:26:26 > > > > > > This is because the idle process is always running (see "ps lax" outout). > > > Perhaps the bug is that top doesn't show the idle process or other interesting > > > kernel processes like the new interrupt processes. > > > > top does nothing to determine LA except getting sysctl "vm.loadavg", isn't it? > > ("uptime" and "w" says the same avenrun/LA values.) > > Imho, idle process should not be determined as always running, > > and idle process state should be fixed. > > Well, the kernel just doesn't treat it specially, so it gets counted in the > load average. I'm not sure if the interrupt and other kernel processes > are counted. Since they do useful work, they should be. The idle process > does the not so useful work of heating the cpu, since it no longer halts > or runs vm_page_zero_idle(). BTW, will it be fixed any time soon? Mobile users will certainly like to see idle process halting CPU as it was before. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 4:53:26 2000 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 D4E1537B423; Mon, 11 Sep 2000 04:53:22 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13YS9F-0004mo-00; Mon, 11 Sep 2000 13:53:17 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id NAA00248; Mon, 11 Sep 2000 13:53:16 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 167; Mon Sep 11 13:52:24 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13YS8N-0004eQ-00; Mon, 11 Sep 2000 13:52:23 +0200 From: Sheldon Hearn To: Steve Ames Cc: freebsd-current@freebsd.org, dwmalone@freebsd.org Subject: Re: fwd: [root: security check] In-reply-to: Your message of "Sat, 09 Sep 2000 12:25:28 EST." <20000909122528.A88592@virtual-voodoo.com> Date: Mon, 11 Sep 2000 13:52:23 +0200 Message-ID: <17881.968673143@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 09 Sep 2000 12:25:28 EST, Steve Ames wrote: > Any way this can show what actually changed? 'mount -p' (which > /etc/security uses) doesn't show things such as soft-updates. In > fact I don't see a single mount option that does show everything... I seem to recall that David Malone chose mount -p because mount without options displayed information about sync- and asyn-c reads and writes. Now, mount without options doesn't display this information. Therefore, I think that we can use mount without options for this check in /etc/security. 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 Sep 11 5: 8:54 2000 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 66F8B37B423 for ; Mon, 11 Sep 2000 05:08:52 -0700 (PDT) Received: from localhost (trevor@localhost) by blues.jpj.net (right/backatcha) with ESMTP id e8BC8UI09680; Mon, 11 Sep 2000 08:08:30 -0400 (EDT) Date: Mon, 11 Sep 2000 08:08:30 -0400 (EDT) From: Trevor Johnson To: Thomas David Rivers Cc: freebsd-current@FreeBSD.ORG, piotr.wozniak@cs.put.poznan.pl Subject: Re: netscape In-Reply-To: <200009081212.IAA59526@lakes.dignus.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 > You need to install the XFree86 a.out library package. It's not needed for the bsdi-netscape ports, because those versions of Netscape are statically linked. Most people don't need the a.out X libraries for anything else. -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 5:13:57 2000 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 5F81437B42C; Mon, 11 Sep 2000 05:13:53 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13YST7-00055t-00; Mon, 11 Sep 2000 14:13:49 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id OAA04183; Mon, 11 Sep 2000 14:13:49 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 4028; Mon Sep 11 14:13:19 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13YSSd-0008dW-00; Mon, 11 Sep 2000 14:13:19 +0200 From: Sheldon Hearn To: Jun Kuriyama Cc: Current Subject: Re: PAM in ftpd.c In-reply-to: Your message of "Mon, 11 Sep 2000 18:57:45 +0900." <7mem2rqmhy.wl@waterblue.imgsrc.co.jp> Date: Mon, 11 Sep 2000 14:13:19 +0200 Message-ID: <33201.968674399@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 11 Sep 2000 18:57:45 +0900, Jun Kuriyama wrote: > I don't know around PAM coding, but below topic is there in Japanese > mailing list. > > o After setting /etc/skey.access, cannot login to ftpd via UNIX > password. > > There is a patch to fix this problem in that mailing list. Could > someone review and commit it? Could you check out PR 20333 at: http://www.freebsd.org/cgi/query-pr.cgi?pr=20333 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 Sep 11 5:24:20 2000 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 DF59F37B423; Mon, 11 Sep 2000 05:24:13 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id XAA06663; Mon, 11 Sep 2000 23:24:05 +1100 Date: Mon, 11 Sep 2000 23:24:03 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Maxim Sobolev Cc: Valentin Nechayev , freebsd-current@FreeBSD.org Subject: Re: load average is 1 when no processes active; etc. In-Reply-To: <39BCBE78.7D17B24B@FreeBSD.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 On Mon, 11 Sep 2000, Maxim Sobolev wrote: > Bruce Evans wrote: > > Well, the kernel just doesn't treat it specially, so it gets counted in the > > load average. I'm not sure if the interrupt and other kernel processes > > are counted. Since they do useful work, they should be. The idle process > > does the not so useful work of heating the cpu, since it no longer halts > > or runs vm_page_zero_idle(). > > BTW, will it be fixed any time soon? Mobile users will certainly like to see idle process > halting CPU as it was before. Not sure. I use this quick fix: --- diff -c2 kern_idle.c~ kern_idle.c *** kern_idle.c~ Thu Sep 7 12:32:51 2000 --- kern_idle.c Sun Sep 10 18:06:39 2000 *************** *** 40,43 **** --- 50,55 ---- #endif + extern void (*_hlt_vector)(void); + static void idle_setup(void *dummy); SYSINIT(idle_setup, SI_SUB_SCHED_IDLE, SI_ORDER_FIRST, idle_setup, NULL) *************** *** 90,94 **** --- 102,116 ---- count = 0; + #ifdef __i386__ + disable_intr(); + #endif while (count >= 0 && procrunnable() == 0) { + #ifdef __i386__ + if (vm_page_zero_idle() != 0) + continue; + (*_hlt_vector)(); + disable_intr(); + continue; + #endif /* * This is a good place to put things to be done in *************** *** 99,102 **** --- 121,127 ---- " for a process"); } + #ifdef __i386__ + enable_intr(); + #endif mtx_enter(&sched_lock, MTX_SPIN); --- Add a bogus #include of to fix a warning. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 6:32:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 61CBC37B423 for ; Mon, 11 Sep 2000 06:32:23 -0700 (PDT) Received: from salmon.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 11 Sep 2000 14:32:14 +0100 (BST) To: Sheldon Hearn Cc: Steve Ames , freebsd-current@freebsd.org Subject: Re: fwd: [root: security check] In-reply-to: Your message of "Mon, 11 Sep 2000 13:52:23 +0200." <17881.968673143@axl.fw.uunet.co.za> X-Request-Do: Date: Mon, 11 Sep 2000 14:32:14 +0100 From: David Malone Message-ID: <200009111432.aa31280@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I seem to recall that David Malone chose mount -p because mount without > options displayed information about sync- and asyn-c reads and writes. > Now, mount without options doesn't display this information. Wasn't me - I was doing seperate things with /etc/security and mount. > Therefore, I think that we can use mount without options for this check > in /etc/security. Sounds like a good idea - we should also consider sorting the output. On the positive side you don't get warned when you unmount and remount a filesystem and it moves to the bottom of the list. On the negative side you don't get warned when someone else unmounts and remounts a filesystem and it moves to the bottom of the list. ;-) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 8:48:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 0F3BF37B424 for ; Mon, 11 Sep 2000 08:48:16 -0700 (PDT) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id A72B75D1A for ; Mon, 11 Sep 2000 17:48:06 +0200 (CEST) Date: Mon, 11 Sep 2000 17:48:06 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: freebsd-current@freebsd.org Subject: Kernel build error 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 ... cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i4b/driver/i4b_ctl.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i4b/driver/i4b_isppp.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../net/if_spppsubr.c ../../net/if_spppsubr.c: In function `sppp_output': ../../net/if_spppsubr.c:755: warning: label `nosupport' defined but not used ../../net/if_spppsubr.c: In function `sppp_chap_scr': ../../net/if_spppsubr.c:3326: warning: passing arg 1 of `read_random' from incompatible pointer type ../../net/if_spppsubr.c:3326: warning: passing arg 2 of `read_random' makes pointer from integer without a cast ../../net/if_spppsubr.c:3326: too few arguments to function `read_random' *** Error code 1 Stop in /home/blaz/FreeBSD/src/sys/compile/GOLD. Seems to be related to randomdev. I have "device sppp" in my kernel config file for i4b. -current as of a couple of minutes ago. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 8:51:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.telemere.net (mail.telemere.net [63.224.9.4]) by hub.freebsd.org (Postfix) with ESMTP id DB7CF37B42C for ; Mon, 11 Sep 2000 08:51:14 -0700 (PDT) Received: by mail.telemere.net (Postfix, from userid 1001) id 4B41220F01; Mon, 11 Sep 2000 10:56:01 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.telemere.net (Postfix) with ESMTP id 435321D101; Mon, 11 Sep 2000 10:56:01 -0500 (CDT) Date: Mon, 11 Sep 2000 10:55:53 -0500 (CDT) From: Visigoth To: David Malone Cc: freebsd-current@freebsd.org Subject: Re: fwd: [root: security check] In-Reply-To: <200009111432.aa31280@salmon.maths.tcd.ie> 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 11 Sep 2000, David Malone wrote: > > Sounds like a good idea - we should also consider sorting the > output. On the positive side you don't get warned when you unmount > and remount a filesystem and it moves to the bottom of the list. > On the negative side you don't get warned when someone else unmounts > and remounts a filesystem and it moves to the bottom of the list. ;-) My $.02 would be not to sort it. I have found it very helpful a coupla times to see filesystems which were remounted appear in the daily mail. Visigoth Damieon Stark Sr. Unix Systems Administrator visigoth@telemere.net PGP Public Key: www.telemere.net/~visigoth/visigoth.asc ____________________________________________________________________________ | M$ -Where do you want to go today? | Linux -Where do you want to go tomorrow?| FreeBSD - The POWER to serve Freebsd -Are you guys coming or what? | http://www.freebsd.org | | - ---------------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.1i iQA/AwUBObzygDnmC/+RTnGeEQKfJgCfYTJNjCVpy4VDVSOGhJ6OXlKrh4cAoJTa KdmZm9XPPQmWxJdaCk87Eh2q =X4nh -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 10:48:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from worldclass.jolt.nu (lgh637b.hn-krukan.AC [212.217.139.112]) by hub.freebsd.org (Postfix) with ESMTP id 98FCA37B422 for ; Mon, 11 Sep 2000 10:48:22 -0700 (PDT) Received: from localhost (c4@localhost) by worldclass.jolt.nu (8.11.0/8.11.0) with ESMTP id e8BJltl00426 for ; Mon, 11 Sep 2000 19:47:55 GMT (envelope-from c4@worldclass.jolt.nu) Date: Mon, 11 Sep 2000 19:47:54 +0000 (GMT) From: Tobias Fredriksson To: freebsd-current@freebsd.org Subject: Last build (5 hours ago) 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 After 5 hours the computer had totally locked itself... just a manual reboot again and doing the fsck on 46gig aint that fun :D I'll guess i'll do a new make world etc... output from top: last pid: 313; load averages: 1.03, 0.75, 0.37 up 0+00:06:17 19:32:12 29 processes: 1 running, 28 sleeping CPU states: 0.0% user, 0.0% nice, 0.4% system, 0.4% interrupt, 99.2% idle After 3 minutes more the load average has locked itslef at 1.00 / 0.87 / 0.50 This seem pretty weird behaviour for a box that previously had 0.03 / 0.03 / 0.03 as an average load average... I also see a problem with the vr driver, at transfers beyond 10mbit it looks up from time to time, when i used 3.5.1-RELEASE i never had this problem, i also got higher speeds (7MB/s instead of the now 2.8MB/s) in 3.5.1-RELEASE i used wd0/wd1/wd2 instead of the ad0/ad1/ad2 but i think the ad device should be faster than the wd device shouldn't it? Anyway the vr locks up and completly fuck up _every_ session to it and leaves an "vr0: watchdog timeout" in the console every time. I have also noticed if i use the samba shares on the freebsd computer from my other windows 98 se computer i can get this too (but not as many). If i use ftp to transfer files and i use the samba network then i'm bound to get them all the time. dmesg output Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #8: Mon Sep 11 14:27:37 GMT 2000 c4@worldclass.jolt.nu:/usr/src/sys/compile/worldclass Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 350795893 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 33554432 (32768K bytes) config> di sn0 config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 29614080 (28920K bytes) Preloaded elf kernel "kernel.ko" at 0xc032c000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc032c0a0. K6-family MTRR support enabled (2 registers) md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 10 pci0: at 2.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 vr0: port 0xdc00-0xdc7f mem 0xdfffef80-0xdfffefff irq 9 at device 14.0 on pci0 vr0: Ethernet address: 00:80:c8:f0:5f:9e miibus0: on vr0 amphy0: on miibus0 amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci0: port 0xffa0-0xffaf irq 0 at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 xl0: <3Com 3c900-TPO Etherlink XL> port 0xd880-0xd8bf irq 5 at device 18.0 on pci0 xl0: Ethernet address: 00:60:97:2a:29:c2 xl0: selecting 10baseT transceiver, half duplex pci0: (vendor=0x1274, dev=0x1371) at 20.0 irq 10 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/1 bytes threshold ppi0: on ppbus0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 10 packets/entry by default microuptime() went backwards (1.4671896 -> 1.376969) microuptime() went backwards (1.4671896 -> 1.377542) ad0: 2503MB [5086/16/63] at ata0-master using UDMA33 microuptime() went backwards (1.4671896 -> 1.400150) microuptime() went backwards (1.4671896 -> 1.400721) ata0-slave: DMA limited to UDMA33, non-ATA66 compliant cable ad1: 19547MB [39714/16/63] at ata0-slave using UDMA33 microuptime() went backwards (1.4671896 -> 1.408150) microuptime() went backwards (1.4671896 -> 1.408713) ad2: 19547MB [39714/16/63] at ata1-master using UDMA33 Mounting root from ufs:/dev/ad0s1a microuptime() went backwards (1.4671896 -> 1.414712) microuptime() went backwards (1.4671896 -> 1.415286) WARNING: / was not properly dismounted microuptime() went backwards (1.4671896 -> 1.425558) microuptime() went backwards (1.4671896 -> 1.426876) pid 238 (ldconfig), uid 0: exited on signal 11 (core dumped) End of dmesg... why ldconfig always crashes i dont know... it's been like this since i upgraded from 3.5.1-RELEASE to 5.0-20000902-CURRENT also all these microuptime() went backwards are a _lot_ more of, i remember somebody talking about it being related to sound card? Well anyhow the kernel that is compiled dosn't have support for the sound card that i have, i havn't included the sound driver. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 11:12:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rainbownet.com (ns.rainbownet.com [212.141.58.2]) by hub.freebsd.org (Postfix) with ESMTP id 448D037B422; Mon, 11 Sep 2000 11:12:33 -0700 (PDT) Received: from styloserver.stylo.it (styloserver.stylo.it [193.76.98.3]) by mail.rainbownet.com (8.9.1/8.9.1) with ESMTP id UAA20280; Mon, 11 Sep 2000 20:12:31 +0200 (CEST) (envelope-from aturetta@rainbownet.com) Received: by styloserver.stylo.it with Internet Mail Service (5.5.2650.21) id ; Mon, 11 Sep 2000 20:12:30 +0200 Message-ID: <210F5CDE0707D211B4BD00062905C8423092D1@styloserver.stylo.it> From: Angelo Turetta To: "'freebsd-stable@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: CVS, -STABLE and perl 5.6.0 Date: Mon, 11 Sep 2000 20:12:29 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know where this discussion really belongs go, excuse the cross-post. Please be aware I'm not on either of these lists (I know it's against the doc :-), so be so kind as to cc any reply to my address. TIA. On a freshly installed 4.1 machine (bin-only installation), I CVSUPed /usr/src from RELENG_4, then removed the subtrees src/gnu/usr.bin/perl src/contrib/perl5 and last I CVSUPed the same subtrees with the tag HEAD. That should have brutally implanted perl5.6.0 in my 4.1-STABLE build tree. In that condition, buildworld fails with: ===> 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) /usr/obj/usr/src/gnu/usr.bin/perl/perl/../miniperl/miniperl:No such file or directory *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/perl. Whereas (cd /usr/src/gnu/usr.bin/perl/perl; make) gave no errors, and allowed me to continue where I left with buildworld -DNOCLEAN. installworld failed too with: ===> gnu/usr.bin/perl/library install: /usr/libdata/perl/5.6.0/./CGI/Apache.pm: No such file or directory *** Error code 71 Stop in /usr/src/gnu/usr.bin/perl/library. which I worked around by creating /usr/libdata/perl/5.6.0 and all subdirs by hand. My question is: is there any plan to merge perl5.6.0 into RELENG_4 (it shouldn't be that difficult, as the only problem is at build/install time)? Do you have any hint for me to avoid the errors in my present case? I suppose the makefile should be changed slightly to avoid the build error, and that some entry should be added to the mtree control file to avoid the install failure: but where should I start? Thank you for any help. Angelo Turetta To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 19:38: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from bernie.compusmart.ab.ca (bernie.compusmart.ab.ca [199.185.130.12]) by hub.freebsd.org (Postfix) with ESMTP id 0B45237B423 for ; Mon, 11 Sep 2000 19:37:59 -0700 (PDT) Received: from 222.209-115-213-0.interbaun.com ([209.115.213.222]:1521 "HELO croc" ident: "IDENT-NONSENSE") by mail.compusmart.ab.ca with SMTP id <70641-12151>; Mon, 11 Sep 2000 20:37:43 -0600 Message-ID: <000801c01c63$78d15a60$01101fac@epsb.edmonton.ab.ca> Reply-To: "Mark Dyer" From: "Mark Dyer" To: Subject: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C01C31.2D31FD80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Date: Mon, 11 Sep 2000 20:37:43 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C01C31.2D31FD80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable subscribe freebsd-current ------=_NextPart_000_0005_01C01C31.2D31FD80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
subscribe=20 freebsd-current
------=_NextPart_000_0005_01C01C31.2D31FD80-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 11 20: 1:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 7DED537B424; Mon, 11 Sep 2000 20:01:45 -0700 (PDT) Received: from C992631-A.pinol1.sfba.home.com (C992631-A.pinol1.sfba.home.com [24.12.58.155]) by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id FAA82488; Tue, 12 Sep 2000 05:01:30 +0200 (SAT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by C992631-A.pinol1.sfba.home.com (8.11.0/8.11.0) id e8C31Hl86105; Mon, 11 Sep 2000 20:01:17 -0700 (PDT) (envelope-from reg) Date: Mon, 11 Sep 2000 20:01:17 -0700 From: Jeremy Lea To: freebsd-ports@freebsd.org, freebsd-current@freebsd.org Cc: Satoshi Asami , "Jordan K. Hubbard" , Sheldon Hearn , bmah@freebsd.org, Maxim Sobolev Subject: Please review: New pkg_which version and bsd.port.mk patch. Message-ID: <20000911200117.H39816@shale.csir.co.za> Mail-Followup-To: Jeremy Lea , freebsd-ports@freebsd.org, freebsd-current@freebsd.org, Satoshi Asami , "Jordan K. Hubbard" , Sheldon Hearn , bmah@freebsd.org, Maxim Sobolev Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, (Once again cross posted since -ports is the major consumer). At http://people.freebsd.org/~reg/ there is a new patch for "pkg_which", now implemented as two new options for pkg_info. Please review this for style and silly things... Also, if you download the bsd.port.mk patch from the page, you can see a new package-depends target, and a check-plist-conflicts target. The new package-depends target is not only about three times faster, but it also doesn't require any Makefiles for depends (so you can just build with the one port extracted, if you have already installed depends). It also has the feature of registering with the correct package (so you'll not see errors about missing +REQUIRED_BY for ghostscript{5,55,6}). This can be used for the XFree86 3.3.6/4.0 and for OpenMotif/LessTif, etc. check-plist-conflicts could be inserted before pre-install to test if you are going to overwrite files. It could also be used in reverse to check for updates - if you have a new package (say gtk-1.2.8) and it's PLIST conflicts with some installed port (say gtk-1.2.3), then this is a good choice for what we want to upgrade. Regards, -Jeremy -- FreeBSD - Because the best things in life are free... 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 Sep 12 2:33:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 3137737B422 for ; Tue, 12 Sep 2000 02:33:18 -0700 (PDT) Received: (qmail 11915 invoked from network); 12 Sep 2000 09:33:12 -0000 Received: from lcp196.cvzoom.net (208.230.68.196) by ns.cvzoom.net with SMTP; 12 Sep 2000 09:33:12 -0000 Date: Tue, 12 Sep 2000 05:33:10 -0400 (EDT) From: Donn Miller To: current@freebsd.org Subject: Latest kernel/module restructuring 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 With the latest kernel/module restructuring, the kernel is now installed as /boot/kernel/kernel.ko. So, basically, if one opts to _not_ build modules w/kernel as per /etc/make.conf, no modules are installed in /boot/kernel other than the kernel itself, kernel.ko. This means that various modules will not be found at boot time, since they are stored in /boot/kernel.old. To remedy this, I suggest we have an option in /etc/defaults/make.conf to _not_ wipe out any modules in /boot/kernel (except kernel.ko of course) if modules are not built with kernel. Correct me if there already exists such an option. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 3:18:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from fling.sanbi.ac.za (fling.sanbi.ac.za [196.38.142.119]) by hub.freebsd.org (Postfix) with ESMTP id BCD4537B423; Tue, 12 Sep 2000 03:17:58 -0700 (PDT) Received: from johann by fling.sanbi.ac.za with local (Exim 3.13 #4) id 13Yn8N-0008Nn-00; Tue, 12 Sep 2000 12:17:47 +0200 Date: Tue, 12 Sep 2000 12:17:47 +0200 From: Johann Visagie To: ports@freebsd.org, current@freebsd.org Subject: Compilation problem only in -CURRENT Message-ID: <20000912121746.D27464@fling.sanbi.ac.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In trying to create a port, I'm running into the following problem: Everything compiles fine on 3.5 -STABLE (last built on Jul 14), but on -CURRENT (Aug 29) one of the .so files reports: 'Undefined symbol "__pure_virtual"' The port defines USE_NEWGCC, so gcc 2.95.2 19991024 is used on both systems. -- Johann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 4:41:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id B88B337B42C for ; Tue, 12 Sep 2000 04:41:14 -0700 (PDT) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "caerdonn.eurocontrol.fr", Issuer CN "CA ITM" (verified OK)) by matrix.eurocontrol.fr (Postfix/TLS) with ESMTP id B6D9E596C for ; Tue, 12 Sep 2000 13:41:13 +0200 (CEST) Received: by caerdonn.eurocontrol.fr (Postfix/TLS, from userid 1193) id 1DFA14E5C; Tue, 12 Sep 2000 13:41:12 +0200 (CEST) Date: Tue, 12 Sep 2000 13:41:12 +0200 From: Ollivier Robert To: FreeBSD Current Users' list Subject: Problem with forwarded connections with OpenSSH/FreeBSD Message-ID: <20000912134112.A25415@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone has any idea why forwarded connections (with an entry in .ssh/config or with -L ::) often ends up taking ages to setup ? During that time the connection itself is blocked with some data in the Recv-Q... localhost.euroco.6674 *.* tcp 0 0 LISTEN localhost.euroco.1853 localhost.euroco.6674 tcp 0 0 ESTABLISHED localhost.euroco.6674 localhost.euroco.1853 tcp 64 0 ESTABLISHED ^^ My entry in .ssh/config is : Host xxx.xxxxxxx.xxx Cipher blowfish RhostsAuthentication no RhostsRSAAuthentication no Compression yes CompressionLevel 4 LocalForward 6674 irc.ais.net:6667 It happens with 2.2.0 also. -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #6: Thu Aug 10 17:36:11 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 5:12:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta05.mail.mel.aone.net.au (mta05.mail.au.uu.net [203.2.192.85]) by hub.freebsd.org (Postfix) with ESMTP id 81BE637B422 for ; Tue, 12 Sep 2000 05:12:31 -0700 (PDT) Received: from camtech.net.au ([203.55.242.165]) by mta05.mail.mel.aone.net.au with ESMTP id <20000912121229.EPIS413.mta05.mail.mel.aone.net.au@camtech.net.au>; Tue, 12 Sep 2000 22:12:29 +1000 Message-ID: <39BE1E1F.F6975CD9@camtech.net.au> Date: Tue, 12 Sep 2000 21:44:23 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kent Hauser Cc: current@freebsd.org Subject: Re: FIXIT problems with /dev References: <200007170505.AA23307@lab1.tfd.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Hauser wrote: > > Hi All, > > I just did something foolhardy -- and yet instructive. Pls let > me relate. Longish story about MAKEDEV limitations...... I suggest you become familiar with the chroot command. > Regards, > Kent > > 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 Tue Sep 12 5:20:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 80DF137B422 for ; Tue, 12 Sep 2000 05:20:14 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8CCKDN74979 for ; Tue, 12 Sep 2000 14:20:13 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: bouncebuffers broken ? From: Poul-Henning Kamp Date: Tue, 12 Sep 2000 14:20:13 +0200 Message-ID: <74977.968761213@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On -current trying to do fdwrite < kern.flp I get panic: isa_dmastart: bad bounce buffer Can anybody confirm/deny this is a general problem ? The machine is a K7 with 512M RAM -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Tue Sep 12 5:22: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id D04EF37B43C for ; Tue, 12 Sep 2000 05:22:03 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8CCM3N75037 for ; Tue, 12 Sep 2000 14:22:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: boot brokenness... From: Poul-Henning Kamp Date: Tue, 12 Sep 2000 14:22:03 +0200 Message-ID: <75035.968761323@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just installed a freshly made release. The machine cannot boot :-( FreeBSD/i386 bootstrap loader, Revision 1.0 (root@syv.freebsd.dk, Tue Sep 12 09:49:16 GMT 2000) Loading /boot/defaults/loader.conf Error: stack underflow | can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. ok unload ok boot /kernel Error: stack underflow ok unload ok boot /kernel Error: stack underflow ok boot can't load 'kernel' no bootable kernel ok unload ok load /kernel /kernel text=0x27cf8a data=0x31c7c+0x26ff4 syms=[0x4+0x38720+0x4+0x40117] ok boot Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-20000912-PHK #0: Tue Sep 12 10:30:17 GMT 2000 root@syv.freebsd.dk:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 231776789 Hz ... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Tue Sep 12 5:54:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 2FE7037B424; Tue, 12 Sep 2000 05:54:32 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e8C9vJo05404; Tue, 12 Sep 2000 10:57:19 +0100 (BST) (envelope-from nik) Date: Tue, 12 Sep 2000 10:57:18 +0100 From: Nik Clayton To: Mitsuru IWASAKI Cc: nik@freebsd.org, freebsd-current@freebsd.org, freebsd-doc@freebsd.org Subject: Re: CFR: acpi userland manpages Message-ID: <20000912105718.A5363@canyon.nothing-going-on.org> References: <20000901000931V.iwasaki@jp.FreeBSD.org> <20000908112356.B31852@canyon.nothing-going-on.org> <20000910075826F.iwasaki@jp.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: <20000910075826F.iwasaki@jp.freebsd.org>; from iwasaki@jp.freebsd.org on Sun, Sep 10, 2000 at 07:58:26AM +0900 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 10, 2000 at 07:58:26AM +0900, Mitsuru IWASAKI wrote: > > Sheldon can probably render an opinion on their usage of the macros. > > OK, I'm looking forward to see it :-) If he doesn't in the next couple of days (no pressure, Sheldon :-) ) then go ahead and commit. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 6:28:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 8E5F937B423 for ; Tue, 12 Sep 2000 06:28:27 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e8CDRk307198 for current@freebsd.org; Tue, 12 Sep 2000 14:27:46 +0100 (BST) (envelope-from nik) Date: Tue, 12 Sep 2000 14:27:45 +0100 From: Nik Clayton To: current@freebsd.org Subject: VMWare on -current, how fast should I expect it to be? Message-ID: <20000912142745.A7121@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, For those of you running VMWare (2) on -current, how fast do you expect it to be? I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the following disk controller / disk atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 17301MB [35152/16/63] at ata0-master using UDMA33 This is -current from about three weeks ago. It works, but it's a bit slow. Applications themselves run at a reasonable speed, but every now and then (can be as frequent as 10-15 seconds) the guest OS (Windows 98 in this case) will freeze or run very slowly -- the mouse pointer doesn't track properly, keystrokes are queued up. After a couple of second things settle back down, the queued keystrokes and mouse movements manifest in the window, and so on, only to repeat shortly afterwards. I don't have this sort of problem with other apps (unless I load 56 copies of Netscape, naturally). Is this a common issue people are seeing? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 6:46:38 2000 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 E6D8037B422 for ; Tue, 12 Sep 2000 06:46:20 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13YqNn-0006yj-00; Tue, 12 Sep 2000 15:45:55 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id PAA05438; Tue, 12 Sep 2000 15:45:55 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 4894; Tue Sep 12 15:42:46 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13YqKk-000PEL-00; Tue, 12 Sep 2000 15:42:46 +0200 From: Sheldon Hearn To: Donn Miller Cc: current@freebsd.org Subject: Re: Latest kernel/module restructuring In-reply-to: Your message of "Tue, 12 Sep 2000 05:33:10 -0400." Date: Tue, 12 Sep 2000 15:42:46 +0200 Message-ID: <96988.968766166@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Sep 2000 05:33:10 -0400, Donn Miller wrote: > To remedy this, I suggest we have an option in /etc/defaults/make.conf > to _not_ wipe out any modules in /boot/kernel (except kernel.ko of > course) if modules are not built with kernel. This sounds like a very bad idea, since it encourages folks to use modules which are not synchronized with the running kernel. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 7: 0:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 6140D37B422 for ; Tue, 12 Sep 2000 07:00:15 -0700 (PDT) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id KAA48526; Tue, 12 Sep 2000 10:00:06 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200009121400.KAA48526@blackhelicopters.org> Subject: Re: Latest kernel/module restructuring In-Reply-To: <96988.968766166@axl.fw.uunet.co.za> from Sheldon Hearn at "Sep 12, 2000 3:42:46 pm" To: sheldonh@uunet.co.za (Sheldon Hearn) Date: Tue, 12 Sep 2000 10:00:06 -0400 (EDT) Cc: dmmiller@cvzoom.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > To remedy this, I suggest we have an option in /etc/defaults/make.conf > > to _not_ wipe out any modules in /boot/kernel (except kernel.ko of > > course) if modules are not built with kernel. > This sounds like a very bad idea, since it encourages folks to use > modules which are not synchronized with the running kernel. Some of us rebuild kernels without supping. I, for one, play with all sorts of kernel options to see what they do. When 5.0-stable comes out, a lot of people would like this. Having to rebuild the modules when I want to add USER_LDT to my kernel would be bad. ==ml -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 7: 5:19 2000 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 301A437B43E for ; Tue, 12 Sep 2000 07:05:15 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13YqgL-0007Ju-00; Tue, 12 Sep 2000 16:05:05 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id QAA09610; Tue, 12 Sep 2000 16:05:05 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 9395; Tue Sep 12 16:04:20 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13Yqfc-000PLq-00; Tue, 12 Sep 2000 16:04:20 +0200 From: Sheldon Hearn To: Michael Lucas Cc: dmmiller@cvzoom.net, current@freebsd.org Subject: Re: Latest kernel/module restructuring In-reply-to: Your message of "Tue, 12 Sep 2000 10:00:06 -0400." <200009121400.KAA48526@blackhelicopters.org> Date: Tue, 12 Sep 2000 16:04:20 +0200 Message-ID: <97453.968767460@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Sep 2000 10:00:06 -0400, Michael Lucas wrote: > Some of us rebuild kernels without supping. I, for one, play with all > sorts of kernel options to see what they do. Then you probably want the kernel reinstall target. I don't think that this target is available from src/Makefile.inc1, so you'd have to use the old style of kernel building. If you want something like ``make reinstallkernel'' from /usr/src to work, you should probably ask marcel nicely. But the original proposal was ill-conceived and simply won't cut it. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 7: 9:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 15F1A37B424; Tue, 12 Sep 2000 07:09:17 -0700 (PDT) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id WAA30451; Tue, 12 Sep 2000 22:09:09 +0800 Received: from jules.elischer.org ([203.59.169.234]) by muzak.iinet.net.au (8.8.5/8.8.5) with SMTP id WAA28355; Tue, 12 Sep 2000 22:09:05 +0800 Message-ID: <39BE38FC.41C67EA6@elischer.org> Date: Tue, 12 Sep 2000 07:09:00 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Nik Clayton Cc: current@freebsd.org Subject: Re: VMWare on -current, how fast should I expect it to be? References: <20000912142745.A7121@canyon.nothing-going-on.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nik Clayton wrote: > > Hi guys, > > For those of you running VMWare (2) on -current, how fast do you expect it to > be? > > I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the > following disk controller / disk > > atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ad0: 17301MB [35152/16/63] at ata0-master using UDMA33 > > This is -current from about three weeks ago. It works, but it's a bit slow. > Applications themselves run at a reasonable speed, but every now and then > (can be as frequent as 10-15 seconds) use only virtual disks and see if it still happens. I found (on vmware 1) that using the raw disks was a recipe for poor performance. Since we don't have block devices any more, we are screwed in this regard. Virtual disks (files) are however buffered and so can sometimes work faster. > -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 7:13:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 1BD5037B424; Tue, 12 Sep 2000 07:13:23 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.10.1/8.10.1) with ESMTP id e8CEDIo24446; Tue, 12 Sep 2000 10:13:20 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id KAA37840; Tue, 12 Sep 2000 10:13:17 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id KAA51124; Tue, 12 Sep 2000 10:13:16 -0400 (EDT) Date: Tue, 12 Sep 2000 10:13:16 -0400 (EDT) From: Thomas David Rivers Message-Id: <200009121413.KAA51124@lakes.dignus.com> To: julian@elischer.org, nik@FreeBSD.ORG Subject: Re: VMWare on -current, how fast should I expect it to be? Cc: current@FreeBSD.ORG In-Reply-To: <39BE38FC.41C67EA6@elischer.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer (julian@elischer.org) wrote: > > Nik Clayton wrote: > > > > Hi guys, > > > > For those of you running VMWare (2) on -current, how fast do you expect it to > > be? > > > > I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the > > following disk controller / disk > > > > atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 > > ata0: at 0x1f0 irq 14 on atapci0 > > ata1: at 0x170 irq 15 on atapci0 > > ad0: 17301MB [35152/16/63] at ata0-master using UDMA33 > > > > This is -current from about three weeks ago. It works, but it's a bit slow. > > Applications themselves run at a reasonable speed, but every now and then > > (can be as frequent as 10-15 seconds) > > use only virtual disks and see if it still happens. > I found (on vmware 1) that using the raw disks was a recipe for > poor performance. Since we don't have block devices any more, > we are screwed in this regard. Virtual disks (files) are however > buffered and so can sometimes work faster. > I'm confused... I thought one of the justifications for removing the block devices was "look - Linux doesn't have any." So, if Vmware runs on Linux, and Linux doesn't have any block devices, why would Vmware need block devices? [Of course, I'm speaking in absence of knowledge - does Linux have/not have block devices?] - Dave Rivers - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe (370) `C' compiler at http://www.dignus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 7:42:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.66]) by hub.freebsd.org (Postfix) with ESMTP id 006C937B42C; Tue, 12 Sep 2000 07:42:22 -0700 (PDT) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.9.3/8.9.0) id QAA15707; Tue, 12 Sep 2000 16:44:41 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <200009121444.QAA15707@oskar.nanoteq.co.za> Subject: RE: VMWare on -current, how fast should I expect it to be? To: nik@freebsd.org Date: Tue, 12 Sep 2000 16:44:41 +0200 (SAT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have seen this too ... Let me first ask ... do you use the "suspend/resume" option?? If Yes then :) This caused the same "lockup" every few seconds on my machine too - a much slower 400 PII. As soon as I "shutdown" Win9X and rebooted it worked fine. I guess it is something in VMware that syncs to a resume/suspend state file. You can see this in that the second and there after times you press the suspend button it doesn't say "Saving state" or what ever, it just suspends immediately. So bottom line - I've stopped using the suspend/resume and since then so "hick-ups" every few seconds ... Hope this helps Reinier On 12-Sep-00 Nik Clayton wrote: > Hi guys, > > For those of you running VMWare (2) on -current, how fast do you expect it to > be? > > I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the > following disk controller / disk > > atapci0: port 0xfc90-0xfc9f at device 7.1 > on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ad0: 17301MB [35152/16/63] at ata0-master using > UDMA33 > > This is -current from about three weeks ago. It works, but it's a bit slow. > Applications themselves run at a reasonable speed, but every now and then > (can be as frequent as 10-15 seconds) the guest OS (Windows 98 in this case) > will freeze or run very slowly -- the mouse pointer doesn't track properly, > keystrokes are queued up. After a couple of second things settle back down, > the queued keystrokes and mouse movements manifest in the window, and so on, > only to repeat shortly afterwards. I don't have this sort of problem with > other apps (unless I load 56 copies of Netscape, naturally). > > Is this a common issue people are seeing? > > N > -- > Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. > Telephone line, $24.95 a month. Software, free. USENET transmission, > hundreds if not thousands of dollars. Thinking before posting, priceless. > Somethings in life you can't buy. For everything else, there's MasterCard. > -- Graham Reed, in the Scary Devil Monastery > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ################################################################### # # # R.N. Bezuidenhout NetSeq Firewall # # rbezuide@oskar.nanoteq.co.za http://www.nanoteq.co.za # # # ################################################################### ---------------------------------- Date: 12-Sep-00 Time: 16:35:32 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 9:11:32 2000 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 48BA837B506 for ; Tue, 12 Sep 2000 09:11:22 -0700 (PDT) Received: by freesbee.wheel.dk (Postfix, from userid 1002) id 60A793E47; Tue, 12 Sep 2000 18:11:20 +0200 (CEST) Date: Tue, 12 Sep 2000 18:11:20 +0200 From: "Niels Chr. Bank-Pedersen" To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: Latest kernel/module restructuring Message-ID: <20000912181120.C4519@bank-pedersen.dk> Mail-Followup-To: Sheldon Hearn , current@freebsd.org References: <200009121400.KAA48526@blackhelicopters.org> <97453.968767460@axl.fw.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <97453.968767460@axl.fw.uunet.co.za>; from sheldonh@uunet.co.za on Tue, Sep 12, 2000 at 04:04:20PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 12, 2000 at 04:04:20PM +0200, Sheldon Hearn wrote: > > > On Tue, 12 Sep 2000 10:00:06 -0400, Michael Lucas wrote: > > > Some of us rebuild kernels without supping. I, for one, play with all > > sorts of kernel options to see what they do. > > Then you probably want the kernel reinstall target. I don't think that > this target is available from src/Makefile.inc1, so you'd have to use > the old style of kernel building. > > If you want something like ``make reinstallkernel'' from /usr/src to > work, you should probably ask marcel nicely. > > But the original proposal was ill-conceived and simply won't cut it. Hmm, how about those of us doing buildworlds/buildkernels on one (nfs)server for subsequent installworlds/installkernels on multiple other machines? With the current targets, you either have to build modules over and over againg for each `client', or you have to accept that /boot/kernel/* gets nuked when running installkernel (or, as you point out, one can use the old manual scheme). > Sheldon. /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 10: 1:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from elsamss06947.elsevier.nl (elsamss06947.elsevier.nl [145.36.5.12]) by hub.freebsd.org (Postfix) with ESMTP id DE8C137B43E; Tue, 12 Sep 2000 10:01:35 -0700 (PDT) Received: from elsamss06948.elsevier.nl (unverified) by elsamss06947.elsevier.nl (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Tue, 12 Sep 2000 17:36:00 +0200 Received: from olorin.elsevier.nl (olorin.elsevier.nl [145.36.13.14]) by elsamss06948.elsevier.nl (2.6 Build 1 (Berkeley 8.8.6)/8.8.4) with ESMTP id RAA01308; Tue, 12 Sep 2000 17:33:04 +0200 Received: from lap1.sohara.org (pooh.elsevier.nl [145.36.13.27]) by olorin.elsevier.nl (8.8.8/8.8.8) with SMTP id RAA18187; Tue, 12 Sep 2000 17:35:07 +0200 (MET DST) Date: Tue, 12 Sep 2000 17:52:14 +0100 From: "Steve O'Hara-Smith" To: Thomas David Rivers Cc: julian@elischer.org, nik@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VMWare on -current, how fast should I expect it to be? Message-Id: <20000912175214.1e5648e6.steveo@eircom.net> In-Reply-To: <200009121413.KAA51124@lakes.dignus.com> References: <39BE38FC.41C67EA6@elischer.org> <200009121413.KAA51124@lakes.dignus.com> X-Mailer: Sylpheed version 0.3.28 (GTK+ 1.2.8; FreeBSD 4.1-STABLE; i386) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Sep 2000 10:13:16 -0400 (EDT) Thomas David Rivers wrote: > > Julian Elischer (julian@elischer.org) wrote: > I'm confused... 'fraid so. It is raw devices (for discs) that linux doesn't have, they are all block devices - although I may be out of date it's been a while. > So, if Vmware runs on Linux, and Linux doesn't have any block devices, > why would Vmware need block devices? Vmware needs buffering for performance. ISTR some discussion when this came up (a while ago) of having buffered devices without block semantics. I'm not sure what came of it. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 10:53:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id A2BF937B43E; Tue, 12 Sep 2000 10:53:24 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id e8CHrOQ02801; Tue, 12 Sep 2000 10:53:24 -0700 Date: Tue, 12 Sep 2000 10:53:24 -0700 From: Brooks Davis To: Nik Clayton Cc: current@FreeBSD.ORG Subject: Re: VMWare on -current, how fast should I expect it to be? Message-ID: <20000912105324.A31617@Odin.AC.HMC.Edu> References: <20000912142745.A7121@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000912142745.A7121@canyon.nothing-going-on.org>; from nik@FreeBSD.ORG on Tue, Sep 12, 2000 at 02:27:45PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 12, 2000 at 02:27:45PM +0100, Nik Clayton wrote: > For those of you running VMWare (2) on -current, how fast do you expect it to > be? I'm running it on my PIII 366 laptop. It's not great, but it's usable. The biggest factors I've seen effecting performance are memory related. Running out will cause the system to temporarily hang while it pages large chunks of memory in and out. Also, the J option to malloc did really bad things to performance when I had it on. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 11:16:47 2000 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 9171837B424 for ; Tue, 12 Sep 2000 11:16:41 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13Yubk-0002Kj-00; Tue, 12 Sep 2000 20:16:36 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id UAA17055; Tue, 12 Sep 2000 20:16:36 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 16945; Tue Sep 12 20:15:26 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13Yuac-00006g-00; Tue, 12 Sep 2000 20:15:26 +0200 From: Sheldon Hearn To: "Niels Chr. Bank-Pedersen" Cc: current@freebsd.org Subject: Re: Latest kernel/module restructuring In-reply-to: Your message of "Tue, 12 Sep 2000 18:11:20 +0200." <20000912181120.C4519@bank-pedersen.dk> Date: Tue, 12 Sep 2000 20:15:26 +0200 Message-ID: <413.968782526@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Sep 2000 18:11:20 +0200, "Niels Chr. Bank-Pedersen" wrote: > Hmm, how about those of us doing buildworlds/buildkernels on > one (nfs)server for subsequent installworlds/installkernels > on multiple other machines? You run buildkernel once, and then installkernel multiple times. That's if all your machines want the same kernel and modules. If they require different kernels and modules, you'll want something like: master> make KERNEL=HOST1 buildkernel master> make KERNEL=HOST2 buildkernel master> make KERNEL=HOST3 buildkernel host1> make installkernel host2> make installkernel host3> make installkernel > With the current targets, you either have to build modules > over and over againg for each `client', or you have to accept > that /boot/kernel/* gets nuked when running installkernel > (or, as you point out, one can use the old manual scheme). Right now, the general feeling seems to be that the options specified in the kernel config might affect the way in which modules for that kernel are built. I don't like this idea, but that's the prevailing wisdom. So yes, you have to build each machine's modules separately. If you agree with me that the prevailing wisdom is stupid, then you can build every kernel after HOST1's with -DNO_MODULES and copy HOST1's modules into the obj dir for the remaining hosts' kernels. You could probably even get away with a symlink. Folks, I agree that it would be nice to have a reinstallkernel target in src/Makefile.inc1. Other than that, it really does sound like everyone's just arguing for the sake of being heard. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 16:47:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 277A937B422 for ; Tue, 12 Sep 2000 16:47:49 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8CNlZU30408; Tue, 12 Sep 2000 16:47:36 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Neil Blakey-Milner Cc: John Toon , freebsd-current@freebsd.org Subject: Re: Please consider some cosmetic changes in boot messages In-Reply-To: Message from Neil Blakey-Milner of "Sat, 09 Sep 2000 15:15:18 +0200." <20000909151518.A70536@mithrandr.moria.org> Date: Tue, 12 Sep 2000 16:47:35 -0700 Message-ID: <30404.968802455@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On that subject, can you give me a rough projection as to when > > 5.0-RELEASE is likely to arrive? > > FreeBSD 2.2.1 1997-04-xx [FBD] > FreeBSD 3.0 1998-10-16 [FBD] > FreeBSD 4.0 2000-03-13 [FBD] You forgot FreeBSD 4.1, 2000-07-27 (www.freebsd.org/releases). This makes FreeBSD 4.2 scheduled for 2000-11-xx since we do a release every 4 months (not that anyone asked about 4.2 in this thread, but I saw some other speculation about it which I'll conveniently answer in this one). I'm also not sure where the rumors about a FreeBSD 4.1.5 got started since I'd certainly never planned on such a thing, that, I think, being more the product of wishful thinking on certain security-minded people's behalf after RSA released their code. :-) That said, it's something I'm still contemplating. I need to see what merge-in-progress work is currently underway or certainly people will complain that 4.1.5 should have waited for their own wishlist items rather than being slaved solely to the RSA release event. As to FreeBSD 5.0, I think you can count on that being a mid-summer item for 2001 and certainly not any sooner. There's a lot of work which still needs to be done before we'll be ready for anything like 5.0, given the extent of the SMPng changes planned for that release. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 18:28: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B79B337B424; Tue, 12 Sep 2000 18:28:05 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id SAA92309; Tue, 12 Sep 2000 18:28:05 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 12 Sep 2000 18:28:05 -0700 (PDT) From: Kris Kennaway To: Jordan Hubbard Cc: Neil Blakey-Milner , John Toon , freebsd-current@freebsd.org Subject: Re: Please consider some cosmetic changes in boot messages In-Reply-To: <30404.968802455@winston.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Sep 2000, Jordan Hubbard wrote: > I'm also not sure where the rumors about a FreeBSD 4.1.5 got started > since I'd certainly never planned on such a thing, that, I think, A certain user called jkh on IRC :-). I asked you and you agreed to it as a net-only release. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 18:33:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 8B14B37B42C; Tue, 12 Sep 2000 18:33:46 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8D1X6I65882; Wed, 13 Sep 2000 11:03:06 +0930 (CST) (envelope-from grog) Date: Wed, 13 Sep 2000 11:03:06 +0930 From: Greg Lehey To: Thomas David Rivers Cc: julian@elischer.org, nik@FreeBSD.ORG, current@FreeBSD.ORG Subject: No block devices (was: VMWare on -current, how fast should I expect it to be?) Message-ID: <20000913110306.D47700@wantadilla.lemis.com> References: <39BE38FC.41C67EA6@elischer.org> <200009121413.KAA51124@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200009121413.KAA51124@lakes.dignus.com>; from rivers@dignus.com on Tue, Sep 12, 2000 at 10:13:16AM -0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 12 September 2000 at 10:13:16 -0400, Thomas David Rivers wrote: > > Julian Elischer (julian@elischer.org) wrote: >> >> Nik Clayton wrote: >>> >>> Hi guys, >>> >>> For those of you running VMWare (2) on -current, how fast do you expect it to >>> be? >>> >>> I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the >>> following disk controller / disk >>> >>> atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 >>> ata0: at 0x1f0 irq 14 on atapci0 >>> ata1: at 0x170 irq 15 on atapci0 >>> ad0: 17301MB [35152/16/63] at ata0-master using UDMA33 >>> >>> This is -current from about three weeks ago. It works, but it's a bit slow. >>> Applications themselves run at a reasonable speed, but every now and then >>> (can be as frequent as 10-15 seconds) >> >> use only virtual disks and see if it still happens. >> I found (on vmware 1) that using the raw disks was a recipe for >> poor performance. Since we don't have block devices any more, >> we are screwed in this regard. Virtual disks (files) are however >> buffered and so can sometimes work faster. > > I'm confused... > > I thought one of the justifications for removing the block devices > was "look - Linux doesn't have any." No, that's never been a justification for removing block devices. Linux has block devices but no character disk devices. FWIW, I was never happy with the removal of block devices either. I was shouted down with "can you point to any one use they are?", to which I replied "just because I don't know of one doesn't mean there isn't one, or that there will never be one in the future". This is an example where they could presumably be useful. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 18:56: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id E588837B422; Tue, 12 Sep 2000 18:56:04 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8D1u0U62609; Tue, 12 Sep 2000 18:56:01 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Kris Kennaway Cc: Neil Blakey-Milner , John Toon , freebsd-current@FreeBSD.org Subject: Re: Please consider some cosmetic changes in boot messages In-Reply-To: Message from Kris Kennaway of "Tue, 12 Sep 2000 18:28:05 PDT." Date: Tue, 12 Sep 2000 18:56:00 -0700 Message-ID: <62606.968810160@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A certain user called jkh on IRC :-). I asked you and you agreed to it as > a net-only release. Hmmm. I must have been on drugs. :) Very well, I'll see what can be done. A test release is actually building right now. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 12 19:39:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id 1D29B37B422; Tue, 12 Sep 2000 19:39:27 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e8D2cxp64105; Tue, 12 Sep 2000 23:39:00 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 12 Sep 2000 23:38:59 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Cc: freebsd-stable@freebsd.org Subject: someone MFC something to -stable recently that would explain ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've tried to remove locore.s, no difference. I've tried building GENERIC, just in case I erroneously removed something while building my custom kernel, same error ... I'm going from a fresh install of 4.1-RELEASE -> 4.1-STABLE, or, at least, trying to ... and I'm building the kernel as 'make buildkernel' ... cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/locore.s /tmp/ccg38208.s: Assembler messages: /tmp/ccg38208.s:1743: Error: .space specifies non-absolute value /tmp/ccg38208.s:2454: Error: undefined symbol L0^A in operation setting PTmap /tmp/ccg38208.s:2454: Error: undefined symbol PDRSHIFT in operation setting PTmap /tmp/ccg38208.s:1711: Error: undefined symbol L0^A in operation /tmp/ccg38208.s:1711: Error: undefined symbol PAGE_SIZE in operation /tmp/ccg38208.s:1712: Error: undefined symbol L0^A in operation /tmp/ccg38208.s:1712: Error: undefined symbol PDESIZE in operation /tmp/ccg38208.s:2454: Error: undefined symbol L0^A in operation setting APTmap /tmp/ccg38208.s:2454: Error: undefined symbol PDRSHIFT in operation setting APTmap /tmp/ccg38208.s:1720: Error: undefined symbol L0^A in operation /tmp/ccg38208.s:1720: Error: undefined symbol PAGE_SIZE in operation /tmp/ccg38208.s:1721: Error: undefined symbol L0^A in operation /tmp/ccg38208.s:1721: Error: undefined symbol PDESIZE in operation /tmp/ccg38208.s:1927: Error: undefined symbol UPAGES in operation /tmp/ccg38208.s:1927: Error: undefined symbol PAGE_SIZE in operation /tmp/ccg38208.s:2315: Error: undefined symbol BI_ESYMTAB in operation /tmp/ccg38208.s:2320: Error: undefined symbol BI_SYMTAB in operation /tmp/ccg38208.s:2321: Error: undefined symbol BI_ESYMTAB in operation /tmp/ccg38208.s:2325: Error: undefined symbol BI_KERNEND in operation 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 Tue Sep 12 20:42:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id A812137B423; Tue, 12 Sep 2000 20:42:49 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id BD5422B2AC; Tue, 12 Sep 2000 22:42:43 -0500 (CDT) Date: Tue, 12 Sep 2000 20:42:43 -0700 From: Paul Saab To: The Hermit Hacker Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: someone MFC something to -stable recently that would explain ... Message-ID: <20000912204243.A1884@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from scrappy@hub.org on Tue, Sep 12, 2000 at 11:38:59PM -0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rebuild genassym paul The Hermit Hacker (scrappy@hub.org) wrote: > > I've tried to remove locore.s, no difference. I've tried building > GENERIC, just in case I erroneously removed something while building my > custom kernel, same error ... > > I'm going from a fresh install of 4.1-RELEASE -> 4.1-STABLE, or, at least, > trying to ... and I'm building the kernel as 'make buildkernel' ... > > > cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/locore.s > /tmp/ccg38208.s: Assembler messages: > /tmp/ccg38208.s:1743: Error: .space specifies non-absolute value > /tmp/ccg38208.s:2454: Error: undefined symbol L0^A in operation setting PTmap > /tmp/ccg38208.s:2454: Error: undefined symbol PDRSHIFT in operation setting PTmap > /tmp/ccg38208.s:1711: Error: undefined symbol L0^A in operation > /tmp/ccg38208.s:1711: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccg38208.s:1712: Error: undefined symbol L0^A in operation > /tmp/ccg38208.s:1712: Error: undefined symbol PDESIZE in operation > /tmp/ccg38208.s:2454: Error: undefined symbol L0^A in operation setting APTmap > /tmp/ccg38208.s:2454: Error: undefined symbol PDRSHIFT in operation setting APTmap > /tmp/ccg38208.s:1720: Error: undefined symbol L0^A in operation > /tmp/ccg38208.s:1720: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccg38208.s:1721: Error: undefined symbol L0^A in operation > /tmp/ccg38208.s:1721: Error: undefined symbol PDESIZE in operation > /tmp/ccg38208.s:1927: Error: undefined symbol UPAGES in operation > /tmp/ccg38208.s:1927: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccg38208.s:2315: Error: undefined symbol BI_ESYMTAB in operation > /tmp/ccg38208.s:2320: Error: undefined symbol BI_SYMTAB in operation > /tmp/ccg38208.s:2321: Error: undefined symbol BI_ESYMTAB in operation > /tmp/ccg38208.s:2325: Error: undefined symbol BI_KERNEND in operation > > > 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 -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 1:18:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 53BE837B42C; Wed, 13 Sep 2000 01:18:02 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e8CH4S708632; Tue, 12 Sep 2000 18:04:28 +0100 (BST) (envelope-from nik) Date: Tue, 12 Sep 2000 18:04:27 +0100 From: Nik Clayton To: Julian Elischer Cc: Nik Clayton , current@freebsd.org Subject: Re: VMWare on -current, how fast should I expect it to be? Message-ID: <20000912180427.A8616@canyon.nothing-going-on.org> References: <20000912142745.A7121@canyon.nothing-going-on.org> <39BE38FC.41C67EA6@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39BE38FC.41C67EA6@elischer.org>; from julian@elischer.org on Tue, Sep 12, 2000 at 07:09:00AM -0700 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 12, 2000 at 07:09:00AM -0700, Julian Elischer wrote: > > atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 > > ata0: at 0x1f0 irq 14 on atapci0 > > ata1: at 0x170 irq 15 on atapci0 > > ad0: 17301MB [35152/16/63] at ata0-master using UDMA33 > > > > This is -current from about three weeks ago. It works, but it's a bit slow. > > Applications themselves run at a reasonable speed, but every now and then > > (can be as frequent as 10-15 seconds) > > use only virtual disks and see if it still happens. I am. The information above is the disk underlying the UFS filesystem that VMWare is then splatting it's files to. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 1:46:58 2000 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 9D01937B422; Wed, 13 Sep 2000 01:46:53 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id TAA22252; Wed, 13 Sep 2000 19:46:26 +1100 Date: Wed, 13 Sep 2000 19:46:24 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Paul Saab Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: someone MFC something to -stable recently that would explain ... In-Reply-To: <20000912204243.A1884@elvis.mu.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 On Tue, 12 Sep 2000, Paul Saab wrote: > Rebuild genassym genassym(8) is not used in either -current or -stable. I left it unremoved in -current so that it can be used to build -stable kernels, and the need for it went away in -stable too. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 2:22:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from venus.cs.put.poznan.pl (vega.cs.put.poznan.pl [150.254.30.30]) by hub.freebsd.org (Postfix) with ESMTP id E971F37B43C for ; Wed, 13 Sep 2000 02:22:46 -0700 (PDT) Received: from cs.put.poznan.pl (dcs-430x-pw.cs.put.poznan.pl [150.254.31.188]) by venus.cs.put.poznan.pl (8.10.2/8.10.2) with ESMTP id e8D9GaU10079 for ; Wed, 13 Sep 2000 11:16:36 +0200 (CEST) Message-ID: <39BF4753.CF88C32D@cs.put.poznan.pl> Date: Wed, 13 Sep 2000 11:22:27 +0200 From: Piotr =?iso-8859-1?Q?Wo=9Fniak?= X-Mailer: Mozilla 4.73 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current Subject: fonts Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, How can I add polish fonts in KDE? Piotr Wozniak To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 3:55:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 1F1B737B424; Wed, 13 Sep 2000 03:55:16 -0700 (PDT) Received: from bagabeedaboo.security.at12.de (dial-194-8-209-65.netcologne.de [194.8.209.65]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id MAA17658; Wed, 13 Sep 2000 12:55:13 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.11.0/8.11.0) with ESMTP id e8DAt4E00659; Wed, 13 Sep 2000 12:55:04 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Wed, 13 Sep 2000 12:55:04 +0200 (CEST) From: Paul Herman To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: someone MFC something to -stable recently that would explain ... 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, 12 Sep 2000, The Hermit Hacker wrote: > I'm going from a fresh install of 4.1-RELEASE -> 4.1-STABLE, or, at least, > trying to ... and I'm building the kernel as 'make buildkernel' ... > > cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/locore.s > /tmp/ccg38208.s: Assembler messages: > /tmp/ccg38208.s:1743: Error: .space specifies non-absolute value > /tmp/ccg38208.s:2454: Error: undefined symbol L0^A in operation setting PTmap > /tmp/ccg38208.s:2454: Error: undefined symbol PDRSHIFT in operation setting PTmap Did you "make buildworld" first? I don't remember exactly when binutils was updated, but it could have something to do with that. When in doubt after a cvsup, always build world first before building a kernel. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 5:43:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.originative.co.uk (mailgate.originative.co.uk [194.217.50.228]) by hub.freebsd.org (Postfix) with ESMTP id 7B59D37B42C; Wed, 13 Sep 2000 05:43:15 -0700 (PDT) Received: from originative.co.uk (lobster.originative.co.uk [194.217.50.241]) by mailgate.originative.co.uk (Postfix) with ESMTP id 103AB1D140; Wed, 13 Sep 2000 13:43:11 +0100 (BST) Message-ID: <39BF765E.3BED1966@originative.co.uk> Date: Wed, 13 Sep 2000 13:43:10 +0100 From: Paul Richards X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Visigoth , current@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: DPT SmartRAID V, VI, Adaptec SCSI RAID driver committed References: <200009051825.LAA02487@mass.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 Mike Smith wrote: > > > > I'd like to hear a few more success stories first (only one so far) from > > > people using the kit to add the driver to their 4.x systems. With all > > > the breakage in -current's PCI support at the moment, I don't expect to > > > hear too many people there reporting on it just yet. > > > > > > > Maybe I missed it... Where is the kit? I would be happy to > > install and stress test a machine or two with SMP and without, just didn't > > realize there was a kit ;) must have been when I was reading my e-mail at > > like 3 am or something.... > > http://people.freebsd.org/~msmith/RAID/index.html#dpt > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] That's a good quote, maybe it should go in fortune. Paul Richards FreeBSD Services Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 7:48:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from qmail2.crane.sgi.net (qmail2.crane.sgi.net [209.166.163.29]) by hub.freebsd.org (Postfix) with SMTP id 8C81737B422 for ; Wed, 13 Sep 2000 07:48:33 -0700 (PDT) Received: (qmail 25322 invoked from network); 13 Sep 2000 14:48:21 -0000 Received: from unknown (HELO burn) (209.166.151.53) by qmail2-2.mx.stargate.net with SMTP; 13 Sep 2000 14:48:21 -0000 Date: Wed, 13 Sep 2000 10:48:20 -0400 (Eastern Daylight Time) From: "Brian A. Seklecki - Stargate Industries, LLC - NOC" To: Julian Elischer Cc: Nik Clayton , current@freebsd.org Subject: Re: VMWare on -current, how fast should I expect it to be? In-Reply-To: <39BE38FC.41C67EA6@elischer.org> Message-ID: X-X-Sender: lavalist@pisces.tcg.sgi.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You're running vmware sucsessfully in --current? I sync'd up the last time I was in the office (last...Friday?) and the linux emulation package refused to build in --current; complaining about an incopatible kernel module. In fact, i had to comment out the linux proc file system (from the linux emul package in 4.1-release) in the fstab to get into multi-user mode. I'll sync again tonight, poke around some more. --Brian On Tue, 12 Sep 2000, Julian Elischer wrote: > Nik Clayton wrote: > > > > Hi guys, > > > > For those of you running VMWare (2) on -current, how fast do you expect it to > > be? > > > > I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the > > following disk controller / disk > > > > atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 > > ata0: at 0x1f0 irq 14 on atapci0 > > ata1: at 0x170 irq 15 on atapci0 > > ad0: 17301MB [35152/16/63] at ata0-master using UDMA33 > > > > This is -current from about three weeks ago. It works, but it's a bit slow. > > Applications themselves run at a reasonable speed, but every now and then > > (can be as frequent as 10-15 seconds) > > use only virtual disks and see if it still happens. > I found (on vmware 1) that using the raw disks was a recipe for > poor performance. Since we don't have block devices any more, > we are screwed in this regard. Virtual disks (files) are however > buffered and so can sometimes work faster. > > > > -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000 > ---> X_.---._/ presently in: Perth > v > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 7:55: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id F1D1637B423; Wed, 13 Sep 2000 07:55:05 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e8DEsZ819728; Wed, 13 Sep 2000 11:54:35 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 13 Sep 2000 11:54:35 -0300 (ADT) From: The Hermit Hacker To: Paul Herman Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: someone MFC something to -stable recently that would explain ... 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 have done that and it appears to have fixed the problem ... wish I could remember where I rad that 'buildkernel' was supposed to build anytying the kernel requird :( On Wed, 13 Sep 2000, Paul Herman wrote: > On Tue, 12 Sep 2000, The Hermit Hacker wrote: > > > I'm going from a fresh install of 4.1-RELEASE -> 4.1-STABLE, or, at least, > > trying to ... and I'm building the kernel as 'make buildkernel' ... > > > > cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/locore.s > > /tmp/ccg38208.s: Assembler messages: > > /tmp/ccg38208.s:1743: Error: .space specifies non-absolute value > > /tmp/ccg38208.s:2454: Error: undefined symbol L0^A in operation setting PTmap > > /tmp/ccg38208.s:2454: Error: undefined symbol PDRSHIFT in operation setting PTmap > > Did you "make buildworld" first? I don't remember exactly when > binutils was updated, but it could have something to do with that. > > When in doubt after a cvsup, always build world first before building > a kernel. > > -Paul. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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 Wed Sep 13 8:20: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.m.iinet.net.au (opera3.iinet.net.au [203.59.24.51]) by hub.freebsd.org (Postfix) with SMTP id B13BC37B43C for ; Wed, 13 Sep 2000 08:19:55 -0700 (PDT) Received: (qmail 22853 invoked by uid 666); 13 Sep 2000 15:19:51 -0000 Received: from reggae-12-112.nv.iinet.net.au (HELO jules.elischer.org) (203.59.92.112) by mail.m.iinet.net.au with SMTP; 13 Sep 2000 15:19:51 -0000 Message-ID: <39BF9B12.59E2B600@elischer.org> Date: Wed, 13 Sep 2000 08:19:46 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: "Brian A. Seklecki - Stargate Industries, LLC - NOC" Cc: current@freebsd.org Subject: Re: VMWare on -current, [patches] References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian A. Seklecki - Stargate Industries, LLC - NOC wrote: > > You're running vmware sucsessfully in --current? I sync'd up the last > time I was in the office (last...Friday?) and the linux emulation package > refused to build in --current; complaining about an incopatible kernel > module. In fact, i had to comment out the linux proc file system (from > the linux emul package in 4.1-release) in the fstab to get into multi-user > mode. > > I'll sync again tonight, poke around some more. > > --Brian I'm running vmware 1.x it works fine except that you need to change the location of some include files for it to compile, and to make a small change to the vmnet ethernet driver. Unfortunatly however, it doesn't like to access raw disks and refuses to allow me to read my disks directly. It will work however with virtual disks. the files that need to be patched are: jules# pwd /usr/ports/emulators/vmware/work/vmware-distrib jules# find . -print|xargs grep -l compat/lin ./vmmon-only/freebsd/linux_emu.c ./vmnet-only/freebsd/vmnet_linux.c in linux_emu.c: #include #include #include <--------- in vmnet_linux.c: #include #include #include <---------- plus: ---------- s = splimp(); ether_ifattach(ifp,1); <------ this replaces 3 other lines splx(s); return 0; } ./vmnet-only/freebsd/vmnet.c: unmodified: line 159 of 599 [26%] --------------- -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 8:23:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (law2-f218.hotmail.com [216.32.181.218]) by hub.freebsd.org (Postfix) with ESMTP id AAD4537B423; Wed, 13 Sep 2000 08:23:35 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 13 Sep 2000 08:23:35 -0700 Received: from 63.77.219.1 by lw2fd.hotmail.msn.com with HTTP; Wed, 13 Sep 2000 15:23:35 GMT X-Originating-IP: [63.77.219.1] From: "Kenneth Mays" To: freebsd-stable@freebsd.org Cc: freebsd-current@freebsd.org Subject: Solaris desktop and server differences Date: Wed, 13 Sep 2000 11:23:35 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 13 Sep 2000 15:23:35.0511 (UTC) FILETIME=[95652E70:01C01D96] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is a blurb from Sun explaining the difference between its Desktop and Server versions of Solaris for Intel and SPARC. I was explaining in -STABLE how Linux distributors are making selling versions of Linux for desktops and servers. An interesting note is many new servers don't come with a floppy drive, only a CD-ROM drive. There are cost differences in the Solaris line. Anyhow, I don't expect FreeBSD to follow this marketing tactic anytime soon (hope not). A press of a button is all you should need to turn a desktop version into a server version. There is too much to deal with trying to keep the program. - Ken What's difference between Solaris x86 Server and Solaris x86 Desktop? Intel version ------------- There is absolutely no difference, other than what you are licensed to do with it. You get exactly the same software with the two products. SPARC version ------------- This is not the case with Sparc server, where the server product contains more CDs with some additional software. If you want something like Solstice AdminSuite, you have to order it separately. About licensing --------------- The Solaris desktop license restricts you from using the system as "any type of server" (other than print or NIS). or supporting more than two continuous users. Read your license for details. A Server Upgrade License is available. Ken _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 11:28: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DC7B737B423; Wed, 13 Sep 2000 11:27:59 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA65901; Wed, 13 Sep 2000 12:27:58 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA89703; Wed, 13 Sep 2000 12:27:29 -0600 (MDT) Message-Id: <200009131827.MAA89703@harmony.village.org> To: "Kenneth Mays" Subject: Re: Solaris desktop and server differences Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 13 Sep 2000 11:23:35 EDT." References: Date: Wed, 13 Sep 2000 12:27:29 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Kenneth Mays" writes: : Anyhow, I don't expect FreeBSD to follow this marketing tactic anytime soon : (hope not). A press of a button is all you should need to turn : a desktop version into a server version. There is too much to deal with : trying to keep the program. FreeBSD can't effectively license like this due to the availabilty of source code and developer sentiment that would make such a change, ummm politically difficult. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 12:51:13 2000 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 0966637B424 for ; Wed, 13 Sep 2000 12:51:12 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id PAA02048; Wed, 13 Sep 2000 15:51:02 -0400 (EDT) (envelope-from wollman) Date: Wed, 13 Sep 2000 15:51:02 -0400 (EDT) From: Garrett Wollman Message-Id: <200009131951.PAA02048@khavrinen.lcs.mit.edu> To: bloom@acm.org Cc: current@FreeBSD.ORG Subject: Re: Another broken buildworld In-Reply-To: <39BC2F24.AE0DEB63@acm.org> References: <39BC2F24.AE0DEB63@acm.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Garrett, now that RSA has released the patent, would you be willing to > add this file to the mirror on cvsup3? I have asked MIT's Technology Licensing Office what their position is in this regard, and hope to have an answer soon. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 14: 6:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4B98F37B423 for ; Wed, 13 Sep 2000 14:06:49 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA66745 for ; Wed, 13 Sep 2000 15:06:47 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA91067 for ; Wed, 13 Sep 2000 15:06:18 -0600 (MDT) Message-Id: <200009132106.PAA91067@harmony.village.org> Subject: Re: SMPNG kernel on UP Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 08 Sep 2000 00:36:12 MDT." <200009080636.e886aCG18672@billy-club.village.org> References: <200009080636.e886aCG18672@billy-club.village.org> Date: Wed, 13 Sep 2000 15:06:18 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009080636.e886aCG18672@billy-club.village.org> Warner Losh writes: : 2) APM is now broken. It worked after the ACPI integration, : but after the SMPNG stuff neither apm -z nor the BIOS keys : seems to suspend. Turns out this isn't the case. : 3) Linux emuation is panics the machine in linux_open on : a normal boot. Turns out to be a bad module. : 4) Need to rebuild all libkvm things, yet again, but : make world fixed that :-) Still true. : 5) USB ethernet is more likely to hang the machine than it was : before. This hand is transient, however. I have seen : one crash removing the USB adapter that I didn't used to : see, but wasn't in a position to look at it in detail. I've not seen this crash again, but things do seem a little slow. The slowness has only been seen in X with an xterm so far, but it has been seen a few times. : 6) Switching virtual termintals from the X server to the : console is busted. This works, but may be realted to the above and below. : 7) SSH to a machine on my local network is dog slow : sometimes. I can type about one line or two lines ahead of : it in email when it happens. It feels like a network pause : of about 1-2 seconds. Local windows behave well during : these episodes. This may be realted to 5. After updating to a newer SMPNG, I'm left with seeing only the USB issue from time to time, but only inside of X. It happens less with the latest update than with the first one. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 14: 9:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id EFC6137B43F for ; Wed, 13 Sep 2000 14:09:19 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA66753; Wed, 13 Sep 2000 15:09:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA91087; Wed, 13 Sep 2000 15:08:48 -0600 (MDT) Message-Id: <200009132108.PAA91087@harmony.village.org> To: Sheldon Hearn Subject: Re: SMPNG kernel on UP Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 08 Sep 2000 12:24:05 +0200." <15418.968408645@axl.fw.uunet.co.za> References: <15418.968408645@axl.fw.uunet.co.za> Date: Wed, 13 Sep 2000 15:08:48 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <15418.968408645@axl.fw.uunet.co.za> Sheldon Hearn writes: : > 7) SSH to a machine on my local network is dog slow : > sometimes. I can type about one line or two lines ahead of : > it in email when it happens. It feels like a network pause : > of about 1-2 seconds. Local windows behave well during : > these episodes. : : I also haven't noticed this. Have you managed to determine that it's : SSH and not your X11 terminal emulator? No. I don't know which one this is. I just know that it happens from time to time. I'll see if I can do something about tracking this down. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 14:50:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E961237B423 for ; Wed, 13 Sep 2000 14:50:34 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA66919; Wed, 13 Sep 2000 15:50:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA91381; Wed, 13 Sep 2000 15:49:56 -0600 (MDT) Message-Id: <200009132149.PAA91381@harmony.village.org> To: Julian Elischer Subject: Re: oddness with new bootblock sources. Cc: Robert Nordier , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 09 Sep 2000 14:56:59 PDT." <39BAB22B.167EB0E7@elischer.org> References: <39BAB22B.167EB0E7@elischer.org> <200009092139.XAA13372@c3-dbn-102.dial-up.net> Date: Wed, 13 Sep 2000 15:49:56 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39BAB22B.167EB0E7@elischer.org> Julian Elischer writes: : > > /usr/obj/usr/src/sys/boot/i386/loader/../libi386/libi386.a(pxe.o): In : > > function ` : > > pxe_enable': : > > pxe.o(.text+0x552): undefined reference to `nfs_root_node' : > : > You need to build and install libstand first. : : I think this should go in UPDATING The workaround is bogus because you can't require anything to be installed freshly in the build process. I've fixed it with Mike Smtih's help so there won't be an UPDATING entry. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 15: 1:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6889A37B42C for ; Wed, 13 Sep 2000 15:01:32 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA66987; Wed, 13 Sep 2000 16:01:30 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA91514; Wed, 13 Sep 2000 16:00:58 -0600 (MDT) Message-Id: <200009132200.QAA91514@harmony.village.org> To: Sheldon Hearn Subject: Re: Latest kernel/module restructuring Cc: "Niels Chr. Bank-Pedersen" , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 12 Sep 2000 20:15:26 +0200." <413.968782526@axl.fw.uunet.co.za> References: <413.968782526@axl.fw.uunet.co.za> Date: Wed, 13 Sep 2000 16:00:58 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <413.968782526@axl.fw.uunet.co.za> Sheldon Hearn writes: : Folks, I agree that it would be nice to have a reinstallkernel target in : src/Makefile.inc1. Other than that, it really does sound like : everyone's just arguing for the sake of being heard. Let's see if this knocks down the noise level: Index: if_ep_pccard.c =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/sys/dev/ep/if_ep_pccard.c,v retrieving revision 1.14 diff -u -r1.14 if_ep_pccard.c --- if_ep_pccard.c 2000/07/13 22:54:23 1.14 +++ if_ep_pccard.c 2000/09/13 03:51:01 @@ -88,7 +88,7 @@ if ((desc = ep_pccard_identify(epb->prod_id)) == NULL) { if (bootverbose) device_printf(dev, "Pass 1 of 2 detection " - "failed (nonfatal)\n"); + "failed (nonfatal) id 0x%x\n", epb->prod_id); epb->cmd_off = 2; epb->prod_id = get_e(sc, EEPROM_PROD_ID); if ((desc = ep_pccard_identify(epb->prod_id)) == NULL) { @@ -127,6 +127,8 @@ return ("3Com Etherlink III 3C589"); case 0x2056: /* 3C562/3C563 */ return ("3Com 3C562D/3C563D"); + case 0x0010: /* 3C1 */ + return ("3Com Megahertz C1"); } return (NULL); } @@ -140,6 +142,7 @@ case 0x2b57: /* 3C572BT */ case 0x4057: /* 3C574 */ case 0x4b57: /* 3C574B */ + case 0x0010: /* 3C1 */ epb->mii_trans = 1; return (1); case 0x2056: /* 3C562D/3C563D */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 16:59:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.hq.sgi.net (mercury.hq.sgi.net [209.166.162.25]) by hub.freebsd.org (Postfix) with ESMTP id CF0C937B42C for ; Wed, 13 Sep 2000 16:59:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mercury.hq.sgi.net (8.8.8/8.8.8) with ESMTP id TAA03999; Wed, 13 Sep 2000 19:59:07 -0400 (EDT) Date: Wed, 13 Sep 2000 19:59:06 -0400 (EDT) From: "Brian A. Seklecki - Stargate Industries, LLC - NOC" X-Sender: lavalamp@mercury.hq.sgi.net Reply-To: BSeklecki@stargate.net To: Reinier Bezuidenhout Cc: freebsd-current@freebsd.org Subject: Re: VMWare on -current, how fast should I expect it to be? 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 That's probably my problem. I don't see that mentioned in the handbook. What steps do you need to take to update /boot/kernel ? I'm syncing up to -current again now.. -lava On Wed, 13 Sep 2000, Reinier Bezuidenhout wrote: > Date: Wed, 13 Sep 2000 16:59:19 +0200 (SAST) > From: Reinier Bezuidenhout > To: "Brian A. Seklecki - Stargate Industries, LLC - NOC" > > Cc: current@freebsd.org > Subject: Re: VMWare on -current, how fast should I expect it to be? > > Hi .. > > I did a make world with a current from yesterday (12 Sept) > and after remembering to update loader / modules etc. > in /boot/kernel, everything worked ok ... > > Vmware too ... runs without a problem ... > > Bye > Reinier > > > On 13-Sep-00 Brian A. Seklecki - Stargate Industries, LLC - NOC wrote: > > > > You're running vmware sucsessfully in --current? I sync'd up the last > > time I was in the office (last...Friday?) and the linux emulation package > > refused to build in --current; complaining about an incopatible kernel > > module. In fact, i had to comment out the linux proc file system (from > > the linux emul package in 4.1-release) in the fstab to get into multi-user > > mode. > > > > I'll sync again tonight, poke around some more. > > > > --Brian > > > > On Tue, 12 Sep 2000, Julian Elischer wrote: > > > >> Nik Clayton wrote: > >> > > >> > Hi guys, > >> > > >> > For those of you running VMWare (2) on -current, how fast do you expect it > >> > to > >> > be? > >> > > >> > I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the > >> > following disk controller / disk > >> > > >> > atapci0: port 0xfc90-0xfc9f at device > >> > 7.1 on pci0 > >> > ata0: at 0x1f0 irq 14 on atapci0 > >> > ata1: at 0x170 irq 15 on atapci0 > >> > ad0: 17301MB [35152/16/63] at ata0-master using > >> > UDMA33 > >> > > >> > This is -current from about three weeks ago. It works, but it's a bit > >> > slow. > >> > Applications themselves run at a reasonable speed, but every now and then > >> > (can be as frequent as 10-15 seconds) > >> > >> use only virtual disks and see if it still happens. > >> I found (on vmware 1) that using the raw disks was a recipe for > >> poor performance. Since we don't have block devices any more, > >> we are screwed in this regard. Virtual disks (files) are however > >> buffered and so can sometimes work faster. > >> > >> > > >> -- > >> __--_|\ Julian Elischer > >> / \ julian@elischer.org > >> ( OZ ) World tour 2000 > >> ---> X_.---._/ presently in: Perth > >> v > >> > >> > >> 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 > > ################################################################### > # # > # R.N. Bezuidenhout NetSeq Firewall # > # rbezuide@oskar.nanoteq.co.za http://www.nanoteq.co.za # > # # > ################################################################### > > ---------------------------------- > Date: 13-Sep-00 > Time: 16:57:19 > > This message was sent by XFMail > ---------------------------------- > Brian A. Seklecki Stargate Industries, LLC Network Operations Center http://www.stargate.net/ The Crane Building, Suite 300 (412) 316-STAR x7719 - voice 40 24th St. (412) 316-7899 - fax Pittsburgh, PA 15222 BSeklecki@Stargate.Net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 18:15:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from worldclass.jolt.nu (lgh637b.hn-krukan.AC [212.217.139.112]) by hub.freebsd.org (Postfix) with ESMTP id B60AE37B42C for ; Wed, 13 Sep 2000 18:15:18 -0700 (PDT) Received: from localhost (c4@localhost) by worldclass.jolt.nu (8.11.0/8.11.0) with ESMTP id e8E3E9Y00353 for ; Thu, 14 Sep 2000 03:14:36 GMT (envelope-from c4@worldclass.jolt.nu) Date: Thu, 14 Sep 2000 03:13:38 +0000 (GMT) From: Tobias Fredriksson To: freebsd-current@freebsd.org Subject: Linux Emulation ETTW? 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 By ETTW i mean estimated time to work :D since the last compile a 1/2 days ago the linux emulation on my non-smp station has failed. Everything that has to use linux emulation crashes the kernel which is rather bad :/ Anybody know when this is schedueled to be looked at / fixed? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 18:20:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 4F86837B423 for ; Wed, 13 Sep 2000 18:20:08 -0700 (PDT) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA05175; Thu, 14 Sep 2000 10:49:20 +0930 (CST) (envelope-from doconnor@gsoft.com.au) 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, 14 Sep 2000 10:49:20 +0930 (CST) From: "Daniel O'Connor" To: Tobias Fredriksson Subject: RE: Linux Emulation ETTW? Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Sep-00 Tobias Fredriksson wrote: > By ETTW i mean estimated time to work :D > since the last compile a 1/2 days ago the linux emulation on my non-smp > station has failed. Everything that has to use linux emulation crashes the > kernel which is rather bad :/ > > Anybody know when this is schedueled to be looked at / fixed? You are probably using the wrong modules. Make sure you don't have an old /modules directory lying around since the kernel and modules have moved to /boot/xxx --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 18:44: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id E968437B424 for ; Wed, 13 Sep 2000 18:44:05 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id SAA58357; Wed, 13 Sep 2000 18:43:30 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009140143.SAA58357@pike.osd.bsdi.com> Subject: Re: Linux Emulation ETTW? In-Reply-To: from Tobias Fredriksson at "Sep 14, 2000 03:13:38 am" To: Tobias Fredriksson Date: Wed, 13 Sep 2000 18:43:30 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tobias Fredriksson wrote: > By ETTW i mean estimated time to work :D > since the last compile a 1/2 days ago the linux emulation on my non-smp > station has failed. Everything that has to use linux emulation crashes the > kernel which is rather bad :/ > > Anybody know when this is schedueled to be looked at / fixed? It works, but you need to have your kernel and modules in sync. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "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 Sep 13 18:59:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id 3FBA137B43E for ; Wed, 13 Sep 2000 18:59:10 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e8E1x8D00499 for ; Thu, 14 Sep 2000 10:59:08 +0900 (JST) Date: Thu, 14 Sep 2000 10:59:08 +0900 Message-ID: <7mbsxr68er.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: How to use RSA with USA_RESIDENT=NO? User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) 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 After installworld, I can not use ssh with RSA. Does someone know how to fix this problem? ----- % ssh white ssh: no RSA support in libssl and libcrypto. See ssl(8). Disabling protocol version 1 DH_generate_key % ----- I have these variables in make.conf ----- CFLAGS= -O -mpentiumpro -pipe USA_RESIDENT= NO MAKE_IDEA= YES WITH_RSA= YES MAKE_RSAINTL= YES PERL_THREADED= true ----- -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 19:19:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from drama.navipath.com (drama.navipath.com [216.67.14.8]) by hub.freebsd.org (Postfix) with ESMTP id B1B2837B423 for ; Wed, 13 Sep 2000 19:19:39 -0700 (PDT) Received: (from forrie@localhost) by drama.navipath.com with id e8E2JYL14203; Wed, 13 Sep 2000 22:19:34 -0400 (EDT) Date: Wed, 13 Sep 2000 22:19:34 -0400 From: Forrest Aldrich To: Jun Kuriyama Cc: Current Subject: Re: How to use RSA with USA_RESIDENT=NO? Message-ID: <20000913221934.B8159@drama.navipath.com> References: <7mbsxr68er.wl@waterblue.imgsrc.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <7mbsxr68er.wl@waterblue.imgsrc.co.jp>; from kuriyama@imgsrc.co.jp on Thu, Sep 14, 2000 at 10:59:08AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I thought they were going to get rid of this dependency, eventually, due to the change in RSA patent status, et al. On Thu, Sep 14, 2000 at 10:59:08AM +0900, Jun Kuriyama wrote: > > After installworld, I can not use ssh with RSA. Does someone know how > to fix this problem? > > ----- > % ssh white > ssh: no RSA support in libssl and libcrypto. See ssl(8). > Disabling protocol version 1 > DH_generate_key > % > ----- > > I have these variables in make.conf > > ----- > CFLAGS= -O -mpentiumpro -pipe > USA_RESIDENT= NO > MAKE_IDEA= YES > WITH_RSA= YES > MAKE_RSAINTL= YES > PERL_THREADED= true > ----- > > > -- > Jun Kuriyama // IMG SRC, Inc. > // FreeBSD Project > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 20:12:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from dei.calldei.com (dei.calldei.com [205.179.37.1]) by hub.freebsd.org (Postfix) with ESMTP id 54EFB37B422; Wed, 13 Sep 2000 20:12:49 -0700 (PDT) Received: (from chris@localhost) by dei.calldei.com (8.9.3/8.9.0) id UAA22657; Wed, 13 Sep 2000 20:12:48 -0700 (PDT) Date: Wed, 13 Sep 2000 20:12:48 -0700 (PDT) From: Chris Costello Message-Id: <200009140312.UAA22657@dei.calldei.com> To: hackers@FreeBSD.org Subject: Fdescfs updates--coming to a devfs near you! Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Over the past few months, I've been working on the /dev/fd file system ("fdescfs"). After weeks of occasionally-hacking and putting it off, I've finalized a patch for fdescfs. What this patch changes: + fdesc_allocvp() becomes curproc-free as a `struct proc' pointer is passed as the new fourth parameter. + All usage of the `DTYPE' open file type macros are removed. Anything whose fo_stat() operation does not return proper fdesc information is broken. The checks for DTYPE_VNODE (for determining whether setattr() will do anything) are replaced by getvnode() so that if the method for determining a vnode from a file entry changes, (hopefully) that's the only place it will happen. There is one loose end I'm not sure I know just how to tie up yet. I'm having trouble modifying src/sys/kern/sys_pipe.c:pipe_stat() to return the right st_mode flags based on various conditions. I'd appreciate it if someone else who knows about the pipe code could point me in the right direction as to what conditions permit reading and what conditions permit writing (and what makes them fail). The patch is available at http://people.FreeBSD.org/~chris/fdesc-dtype.patch, Documentation for it is available at http://people.FreeBSD.org/~chris/fdesc/ all in one page: http://people.FreeBSD.org/~chris/fdesc/article.html |Chris Costello |Press [ESC] to detonate or any other key to explode. `---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 20:37: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id E2F2237B423 for ; Wed, 13 Sep 2000 20:37:06 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8E3aPU17514; Wed, 13 Sep 2000 20:36:28 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Tobias Fredriksson Cc: freebsd-current@FreeBSD.ORG Subject: Re: Linux Emulation ETTW? In-Reply-To: Message from Tobias Fredriksson of "Thu, 14 Sep 2000 03:13:38 -0000." Date: Wed, 13 Sep 2000 20:36:24 -0700 Message-ID: <17510.968902584@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > By ETTW i mean estimated time to work :D It works right now and has for the last week. If you get out of date with your modules, on the other hand, you're shooting your own feet off. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 21: 6:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id 9315637B422 for ; Wed, 13 Sep 2000 21:06:56 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e8E46sG00677 for ; Thu, 14 Sep 2000 13:06:54 +0900 (JST) Date: Thu, 14 Sep 2000 13:06:54 +0900 Message-ID: <7mwvgf7h29.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: FreeBSD-current@FreeBSD.ORG Subject: Re: How to use RSA with USA_RESIDENT=NO? In-Reply-To: In your message of "14 Sep 2000 01:59:23 GMT" <7mbsxr68er.wl@waterblue.imgsrc.co.jp> References: <7mbsxr68er.wl@waterblue.imgsrc.co.jp> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=ISO-2022-JP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 14 Sep 2000 01:59:23 GMT, $B$/$j$d$^(B@imgsrc wrote: > After installworld, I can not use ssh with RSA. Does someone know how > to fix this problem? Jordan tought me to include "device random" in kernel configuration file. That fixes this problem. Thanks! -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 21:53: 1 2000 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 0A4D037B424 for ; Wed, 13 Sep 2000 21:53:00 -0700 (PDT) Received: from gorean.org (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA14922; Wed, 13 Sep 2000 21:52:53 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39C059A5.165EFD24@gorean.org> Date: Wed, 13 Sep 2000 21:52:53 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jun Kuriyama Cc: Current Subject: Re: How to use RSA with USA_RESIDENT=NO? References: <7mbsxr68er.wl@waterblue.imgsrc.co.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jun Kuriyama wrote: > > After installworld, I can not use ssh with RSA. Does someone know how > to fix this problem? Commenting out USA_RESIDENT entirely worked for me. In an ideal world all references to that variable would go away in openss[hl]. I think we should keep it around for other parts of the system... you never know when the USG is going to do something stupid again. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 22:23:28 2000 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 797EF37B423 for ; Wed, 13 Sep 2000 22:23:24 -0700 (PDT) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id HAA68572; Thu, 14 Sep 2000 07:12:58 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.0/8.11.0) with ESMTP id e8E4stN34287; Thu, 14 Sep 2000 06:55:08 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Thu, 14 Sep 2000 06:54:55 +0200 (CEST) From: Leif Neland To: Paul Herman Cc: Vivek Khera , freebsd-current@FreeBSD.ORG Subject: Re: call for testers: init securelevel patch 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 Fri, 8 Sep 2000, Paul Herman wrote: > On Fri, 8 Sep 2000, Vivek Khera wrote: > > > >>>>> "BE" == Bruce Evans writes: > > > > BE> revision 1.9 > > BE> date: 1997/06/25 07:31:47; author: joerg; state: Exp; lines: +2 -2 > > BE> Don't ever allow lowering the securelevel at all. Allowing it does > > BE> nothing good except of opening a can of (potential or real) security > > BE> holes. People maintaining a machine with higher security requirements > > BE> need to be on the console anyway, so there's no point in not forcing > > BE> them to reboot before starting maintenance. > > > > Perhaps one of the secure level restrictions should be that you cannot > > attach to pid 1 via the debugger. > > You can't. > > Ever since Apr 1997 you couldn't attach gdb to init. > How is that done? Will gdb not attach to init, or will init not let gdb attach? If the former, then badguy can just use a custom gdb... Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 23: 2:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 067EA37B424 for ; Wed, 13 Sep 2000 23:02:26 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13ZS6G-000OCe-00; Thu, 14 Sep 2000 08:02:20 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e8E628n03046; Thu, 14 Sep 2000 08:02:10 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009140602.e8E628n03046@grimreaper.grondar.za> To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: SMPNG kernel on UP References: <200009132106.PAA91067@harmony.village.org> In-Reply-To: <200009132106.PAA91067@harmony.village.org> ; from Warner Losh "Wed, 13 Sep 2000 15:06:18 CST." Date: Thu, 14 Sep 2000 08:02:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200009080636.e886aCG18672@billy-club.village.org> Warner Losh wri tes: > : 2) APM is now broken. It worked after the ACPI integration, > : but after the SMPNG stuff neither apm -z nor the BIOS keys > : seems to suspend. > > Turns out this isn't the case. shutdown -p does not turn off the machine for me (Libretto 110ct). zzz/apm -z gives me "apm: ioctl(APMIO_SUSPEND): Invalid argument" M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 23: 4:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 1E6A637B423 for ; Wed, 13 Sep 2000 23:04:38 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8E3afv16426; Thu, 14 Sep 2000 04:36:41 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8E3asH07507; Thu, 14 Sep 2000 04:36:55 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009140336.e8E3asH07507@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jun Kuriyama Cc: Current , brian@Awfulhak.org Subject: Re: How to use RSA with USA_RESIDENT=NO? In-Reply-To: Message from Jun Kuriyama of "Thu, 14 Sep 2000 10:59:08 +0900." <7mbsxr68er.wl@waterblue.imgsrc.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 2000 04:36:53 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you sure this isn't because you've forgotten to kldload random (it changed from randomdev) ? See UPDATING. > After installworld, I can not use ssh with RSA. Does someone know how > to fix this problem? > > ----- > % ssh white > ssh: no RSA support in libssl and libcrypto. See ssl(8). > Disabling protocol version 1 > DH_generate_key > % > ----- > > I have these variables in make.conf > > ----- > CFLAGS= -O -mpentiumpro -pipe > USA_RESIDENT= NO > MAKE_IDEA= YES > WITH_RSA= YES > MAKE_RSAINTL= YES > PERL_THREADED= true > ----- > > > -- > Jun Kuriyama // IMG SRC, Inc. > // FreeBSD Project -- 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 Sep 13 23: 5:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2BD8937B42C for ; Wed, 13 Sep 2000 23:05:35 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA68520; Thu, 14 Sep 2000 00:05:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA94177; Thu, 14 Sep 2000 00:05:03 -0600 (MDT) Message-Id: <200009140605.AAA94177@harmony.village.org> To: Mark Murray Subject: Re: SMPNG kernel on UP Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 14 Sep 2000 08:02:07 +0200." <200009140602.e8E628n03046@grimreaper.grondar.za> References: <200009140602.e8E628n03046@grimreaper.grondar.za> <200009132106.PAA91067@harmony.village.org> Date: Thu, 14 Sep 2000 00:05:03 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009140602.e8E628n03046@grimreaper.grondar.za> Mark Murray writes: : > In message <200009080636.e886aCG18672@billy-club.village.org> Warner Losh wri : tes: : > : 2) APM is now broken. It worked after the ACPI integration, : > : but after the SMPNG stuff neither apm -z nor the BIOS keys : > : seems to suspend. : > : > Turns out this isn't the case. : : shutdown -p does not turn off the machine for me (Libretto 110ct). : : zzz/apm -z gives me "apm: ioctl(APMIO_SUSPEND): Invalid argument" I noticed this with the first SMPNG kernel I tried. The newer one this problem disappeared. Don't know why it would matter, but I may have missed a commit while in new mexico. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 23: 8:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 09DB037B42C for ; Wed, 13 Sep 2000 23:08:43 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA68537; Thu, 14 Sep 2000 00:08:41 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA94226; Thu, 14 Sep 2000 00:08:11 -0600 (MDT) Message-Id: <200009140608.AAA94226@harmony.village.org> To: Jun Kuriyama Subject: Re: How to use RSA with USA_RESIDENT=NO? Cc: Current In-reply-to: Your message of "Thu, 14 Sep 2000 10:59:08 +0900." <7mbsxr68er.wl@waterblue.imgsrc.co.jp> References: <7mbsxr68er.wl@waterblue.imgsrc.co.jp> Date: Thu, 14 Sep 2000 00:08:11 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <7mbsxr68er.wl@waterblue.imgsrc.co.jp> Jun Kuriyama writes: : After installworld, I can not use ssh with RSA. Does someone know how : to fix this problem? You may need to load the random device, or put it in your kernel. Its name recently changed, so maybe that is what is causing you problems. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 23:10: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4DAEF37B423 for ; Wed, 13 Sep 2000 23:10:06 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA68549; Thu, 14 Sep 2000 00:10:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA94251; Thu, 14 Sep 2000 00:09:32 -0600 (MDT) Message-Id: <200009140609.AAA94251@harmony.village.org> To: Jordan Hubbard Subject: Re: Linux Emulation ETTW? Cc: Tobias Fredriksson , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 13 Sep 2000 20:36:24 PDT." <17510.968902584@winston.osd.bsdi.com> References: <17510.968902584@winston.osd.bsdi.com> Date: Thu, 14 Sep 2000 00:09:32 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <17510.968902584@winston.osd.bsdi.com> Jordan Hubbard writes: : > By ETTW i mean estimated time to work :D : : It works right now and has for the last week. If you get out of date : with your modules, on the other hand, you're shooting your own feet off. And the move to the new layout may be shooting you without your knowledge. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 23:30:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 72EAA37B42C for ; Wed, 13 Sep 2000 23:30:43 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13ZPEV-00065E-00; Thu, 14 Sep 2000 03:58:39 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id DAA76504; Thu, 14 Sep 2000 03:58:39 +0100 (BST) (envelope-from ben) Date: Thu, 14 Sep 2000 03:58:39 +0100 From: Ben Smithurst To: Jun Kuriyama Cc: Current Subject: Re: How to use RSA with USA_RESIDENT=NO? Message-ID: <20000914035839.G77593@strontium.scientia.demon.co.uk> References: <7mbsxr68er.wl@waterblue.imgsrc.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <7mbsxr68er.wl@waterblue.imgsrc.co.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jun Kuriyama wrote: > After installworld, I can not use ssh with RSA. Does someone know how > to fix this problem? > > ----- > % ssh white > ssh: no RSA support in libssl and libcrypto. See ssl(8). > Disabling protocol version 1 > DH_generate_key > % This is going to sound weird, but did you rebuild the kernel? I'm *sure* I had my system at one point such that ssh worked with the new kernel but not with the old one. I'm not sure why, perhaps I was dreaming. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 23:46:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 2ECB137B423 for ; Wed, 13 Sep 2000 23:46:31 -0700 (PDT) Received: (qmail 23463 invoked from network); 14 Sep 2000 06:46:30 -0000 Received: from lcp196.cvzoom.net (208.230.68.196) by ns.cvzoom.net with SMTP; 14 Sep 2000 06:46:30 -0000 Date: Thu, 14 Sep 2000 02:46:30 -0400 (EDT) From: Donn Miller To: current@freebsd.org Subject: Load avg. bottoms out at 1.00 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 Anyone else seeing this? I just cvsup'd my kernel sources/remade my kernel an hour ago, and I'm still seeing this problem. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 13 23:58:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id DA4FF37B423 for ; Wed, 13 Sep 2000 23:58:21 -0700 (PDT) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e8E6wHI21335 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Thu, 14 Sep 2000 08:58:19 +0200 (MET DST) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0::104:200:92ff:fe9b:20e7]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e8E6wKI75732; Thu, 14 Sep 2000 08:58:21 +0200 (CEST) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.0/8.9.2) id e8E6wKx58825; Thu, 14 Sep 2000 08:58:20 +0200 (CEST) (envelope-from ticso) Date: Thu, 14 Sep 2000 08:58:19 +0200 From: Bernd Walter To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: Load avg. bottoms out at 1.00 Message-ID: <20000914085819.A58779@cicely5.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dmmiller@cvzoom.net on Thu, Sep 14, 2000 at 02:46:30AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 14, 2000 at 02:46:30AM -0400, Donn Miller wrote: > Anyone else seeing this? I just cvsup'd my kernel sources/remade my > kernel an hour ago, and I'm still seeing this problem. See http://people.freebsd.org/~jasone/smp/ under known issues: Idle processor time is charged to the idle processes. 5 September 2000 Unresolved. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 0:34:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.calweb.com (mail.calweb.com [209.210.251.12]) by hub.freebsd.org (Postfix) with ESMTP id 3CCEE37B422 for ; Thu, 14 Sep 2000 00:34:19 -0700 (PDT) Received: from outel.org (outel.org [207.173.133.28]) by mail.calweb.com (8.9.3/8.9.3) with ESMTP id AAA95350 for ; Thu, 14 Sep 2000 00:34:18 -0700 (PDT) Message-ID: <39C07EB2.1DA8C103@outel.org> Date: Thu, 14 Sep 2000 00:30:58 -0700 From: "Joel M. Baldwin" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: miniperl not found error? References: <20000914085819.A58779@cicely5.cicely.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok I give up! I've been getting this error for ages when doing a 'make depend' on the current tree and up to now I've just done a 'make -k' to get it to work. Whats the final solution so I don't have to do this? What stupid thing have I missed somewhere along the line. ===> 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) /usr/obj/disk2/usr.src/gnu/usr.bin/perl/perl/../miniperl/miniperl: not found *** Error code 127 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error su-2.02# To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 1:12:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id D060C37B424; Thu, 14 Sep 2000 01:12:34 -0700 (PDT) Received: from popserver-02.iinet.net.au (popserver-02.iinet.net.au [203.59.24.148]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id QAA28282; Thu, 14 Sep 2000 16:12:22 +0800 Received: from jules.elischer.org (reggae-39-66.nv.iinet.net.au [203.59.173.66]) by popserver-02.iinet.net.au (8.9.3/8.9.3) with SMTP id QAA00430; Thu, 14 Sep 2000 16:12:17 +0800 Message-ID: <39C0885A.41C67EA6@elischer.org> Date: Thu, 14 Sep 2000 01:12:10 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Chris Costello Cc: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: Fdescfs updates--coming to a devfs near you! References: <200009140312.UAA22657@dei.calldei.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've never thought of a use for fdescfs... -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 2:45:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id B67A737B424 for ; Thu, 14 Sep 2000 02:45:47 -0700 (PDT) Received: (qmail 33108 invoked by uid 1001); 14 Sep 2000 09:39:45 -0000 Date: Thu, 14 Sep 2000 12:39:45 +0300 From: Peter Pentchev To: Julian Elischer Cc: Chris Costello , hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: Fdescfs updates--coming to a devfs near you! Message-ID: <20000914123945.A32524@ringwraith.office1.bg> References: <200009140312.UAA22657@dei.calldei.com> <39C0885A.41C67EA6@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39C0885A.41C67EA6@elischer.org>; from julian@elischer.org on Thu, Sep 14, 2000 at 01:12:10AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote: > I've never thought of a use for fdescfs... Well.. just a trivial example - imagine a program which takes a filename as an argument; imagine yourself trying to pipe something into it - passing /dev/fd/0 as a filename to process would do the trick. G'luck, Peter -- .sith ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 2:46: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.66]) by hub.freebsd.org (Postfix) with ESMTP id 3AF9C37B42C for ; Thu, 14 Sep 2000 02:45:48 -0700 (PDT) Received: from jarrow.dev.nanoteq.co.za (jarrow [196.37.91.33]) by oskar.nanoteq.co.za (8.9.3/8.9.0) with ESMTP id LAA12765 for ; Thu, 14 Sep 2000 11:47:52 +0200 (SAT) 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, 14 Sep 2000 11:43:56 +0200 (SAST) Reply-To: rbezuide@oskar.nanoteq.co.za From: Reinier Bezuidenhout To: freebsd-current@freebsd.org Subject: FW: (KAME-snap 3318) Panic on current (12 Sept) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... I'm running a current machine of 12 Sept although this problem also occured on a current of a few days earlier ... This only happens when using the IPv6 IPSec code during the day, it is readily reproduceable. If during the day I load the racoon daemon and load keys and establish a IPSec tunnel connection everything works fine till 2:00 am when the daily script runs OR if I run the daily script by hand ... I generated the following dump and backtrace ... It seems to crash in a makedev routine using FOREACH list macro's. The problem doesn't seem to be with the list or the makedev function in kern_conf.c. It seems to me that something in the kernel corrupts the static list dev_hash when using the IPSec code. Summary - when ising IPSec ... machine panics during daily script execution. If you need more info from the dumps, just ask ! Reinier ----- gdb bt follows qith a few prints ----- (kgdb) #5 0xc0283d53 in trap (frame={tf_fs = 16, tf_es = -65520, tf_ds = -904265712, tf_edi = 196611, tf_esi = 197379, tf_ebp = -904254412, tf_isp = -904254444, tf_ebx = 5, tf_edx = 2, tf_ecx = -1057628672, tf_eax = 197374, tf_trapno = 12, tf_err = 0, tf_eip = -1072335336, tf_cs = 8, tf_eflags = 66050, tf_esp = 197379, tf_ss = -905316928}) at ../../i386/i386/trap.c:436 436 (void) trap_pfault(&frame, FALSE, eva); (kgdb) #6 0xc0157618 in makedev (x=3, y=196611) at ../../kern/kern_conf.c:232 232 LIST_FOREACH(si, &dev_hash[hash], si_hash) { (kgdb) li 227 228 if (x == umajor(NOUDEV) && y == uminor(NOUDEV)) 229 Debugger("makedev of NOUDEV"); 230 udev = (x << 8) | y; 231 hash = udev % DEVT_HASH; 232 LIST_FOREACH(si, &dev_hash[hash], si_hash) { 233 if (si->si_udev == udev) 234 return (si); 235 } 236 si = allocdev(); (kgdb) p hash $1 = 5 (kgdb) p dev_hash[hash] $2 = {lh_first = 0x2} (kgdb) p dev_hash[1] $3 = {lh_first = 0xc0fb7980} (kgdb) p dev_hash[2] $4 = {lh_first = 0xc0fb7900} (kgdb) p dev_hash[3] $5 = {lh_first = 0xc0fb9d80} (kgdb) p dev_hash[4] $6 = {lh_first = 0x200} <----- OOPS !! (kgdb) p dev_hash[5] $7 = {lh_first = 0x2} <----- OOPS - the one we use ... (kgdb) p dev_hash[6] $8 = {lh_first = 0xc0fb5980} (kgdb) ---------- panic message ------ Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1e fault code = supervisor read, page not present instruction pointer = 0x8:0xc0157618 stack pointer = 0x10:0xca1a2c28 frame pointer = 0x10:0xca1a2c34 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1910 (find) trap number = 12 panic: page fault syncing disks... 31 31 8 8 3 3 done Uptime: 11h37m7s ################################################################### # # # R.N. Bezuidenhout NetSeq Firewall # # rbezuide@oskar.nanoteq.co.za http://www.nanoteq.co.za # # # ################################################################### ---------------------------------- Date: 14-Sep-00 Time: 11:43:22 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 2:49:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.44.236]) by hub.freebsd.org (Postfix) with ESMTP id 4231637B424; Thu, 14 Sep 2000 02:49:09 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8E9mwN56078; Thu, 14 Sep 2000 11:48:58 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Pentchev Cc: Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Your message of "Thu, 14 Sep 2000 12:39:45 +0300." <20000914123945.A32524@ringwraith.office1.bg> Date: Thu, 14 Sep 2000 11:48:58 +0200 Message-ID: <56076.968924938@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000914123945.A32524@ringwraith.office1.bg>, Peter Pentchev writes : >On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote: >> I've never thought of a use for fdescfs... > >Well.. just a trivial example - imagine a program which takes a filename >as an argument; imagine yourself trying to pipe something into it - >passing /dev/fd/0 as a filename to process would do the trick. I must admit that I think in general that /dev/std{in,out,err} and /dev/fd is bogus. It looks like something which happened "because we can" more than something which has a legitimate need. If anything I would propose we ditch it... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Thu Sep 14 3:18:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id B37DB37B42C; Thu, 14 Sep 2000 03:18:17 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e8E9CUO04403; Thu, 14 Sep 2000 10:12:30 +0100 (BST) (envelope-from nik) Date: Thu, 14 Sep 2000 10:12:30 +0100 From: Nik Clayton To: "Brian A. Seklecki - Stargate Industries, LLC - NOC" Cc: Julian Elischer , Nik Clayton , current@freebsd.org Subject: Re: VMWare on -current, how fast should I expect it to be? Message-ID: <20000914101230.A4382@canyon.nothing-going-on.org> References: <39BE38FC.41C67EA6@elischer.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 lavalist@stargate.net on Wed, Sep 13, 2000 at 10:48:20AM -0400 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 13, 2000 at 10:48:20AM -0400, Brian A. Seklecki - Stargate Industries, LLC - NOC wrote: > You're running vmware sucsessfully in --current? Yes. -current from August 18th, and I'm running the vmware2-2.0.2.621 port. Installing Win98 took about 4 hours though -- most of that was when Win98 was probing for devices. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 3:28:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 5012B37B423 for ; Thu, 14 Sep 2000 03:28:35 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13ZWFD-0006PR-00; Thu, 14 Sep 2000 11:27:51 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id LAA75206; Thu, 14 Sep 2000 11:27:51 +0100 (BST) (envelope-from ben) Date: Thu, 14 Sep 2000 11:27:51 +0100 From: Ben Smithurst To: Leif Neland Cc: Paul Herman , Vivek Khera , freebsd-current@FreeBSD.ORG Subject: Re: call for testers: init securelevel patch Message-ID: <20000914112751.H77593@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > How is that done? > Will gdb not attach to init, or will init not let gdb attach? The kernel won't let GDB attach. Look at the code for ptrace()... /* can't trace init when securelevel > 0 */ if (securelevel > 0 && p->p_pid == 1) return EPERM; -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 4:44:28 2000 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 7DD7E37B423 for ; Thu, 14 Sep 2000 04:44:24 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id WAA03694; Thu, 14 Sep 2000 22:44:07 +1100 Date: Thu, 14 Sep 2000 22:44:05 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "Joel M. Baldwin" Cc: current@FreeBSD.ORG Subject: Re: miniperl not found error? In-Reply-To: <39C07EB2.1DA8C103@outel.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 On Thu, 14 Sep 2000, Joel M. Baldwin wrote: > ok I give up! > > I've been getting this error for ages when doing a > 'make depend' on the current tree and up to now > I've just done a 'make -k' to get it to work. > > Whats the final solution so I don't have to do this? > > What stupid thing have I missed somewhere along the line. Building of perl in the normal way (not using makeworld) has been broken for a while. You have to use "make build-tools" instead of just "make depend; make" in the top-level perl directory at certain times when the build-tools are out of date (in particular, when they don't exist). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 5:29:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 8816637B422; Thu, 14 Sep 2000 05:29:33 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13ZWeE-0006UB-00; Thu, 14 Sep 2000 11:53:42 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id LAA92642; Thu, 14 Sep 2000 11:53:42 +0100 (BST) (envelope-from ben) Date: Thu, 14 Sep 2000 11:53:42 +0100 From: Ben Smithurst To: Poul-Henning Kamp Cc: Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! Message-ID: <20000914115342.I77593@strontium.scientia.demon.co.uk> References: <20000914123945.A32524@ringwraith.office1.bg> <56076.968924938@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <56076.968924938@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > is bogus. It looks like something which happened "because we can" more > than something which has a legitimate need. You think adding a hack to every program to support "-" to mean stdout/stdin is better? It seems to be that saying "/dev/stdin" when you mean stdin is better than saying "-" and hoping the application handles that correctly. Of course many programs will read stdin by default, and write stdout by default, but that doesn't help when you want to read more than one file, one of which is stdin. > If anything I would propose we ditch it... And break loads of scripts at the same time? -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 5:37:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.44.236]) by hub.freebsd.org (Postfix) with ESMTP id 6B0DE37B422; Thu, 14 Sep 2000 05:37:07 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8ECb6N56647; Thu, 14 Sep 2000 14:37:06 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Ben Smithurst Cc: Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Your message of "Thu, 14 Sep 2000 11:53:42 BST." <20000914115342.I77593@strontium.scientia.demon.co.uk> Date: Thu, 14 Sep 2000 14:37:06 +0200 Message-ID: <56645.968935026@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000914115342.I77593@strontium.scientia.demon.co.uk>, Ben Smithurs t writes: >Poul-Henning Kamp wrote: > >> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd >> is bogus. It looks like something which happened "because we can" more >> than something which has a legitimate need. > >You think adding a hack to every program to support "-" to mean >stdout/stdin is better? The majority of these programs could be handled by adding knowledge of "-" as a magic filename to fopen(3). At the same time I would really love if we implemented "|.*" to mean "do an popen(3)" instead. But of course, this is bikeshed material... >> If anything I would propose we ditch it... > >And break loads of scripts at the same time? I would argue that the programs and the scripts that call them are already broken, but hey... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Thu Sep 14 5:46: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 08CE237B422 for ; Thu, 14 Sep 2000 05:45:58 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13ZYOp-0007K2-00 for current@freebsd.org; Thu, 14 Sep 2000 15:45:55 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13ZYOo-00007u-00 for current@FreeBSD.ORG; Thu, 14 Sep 2000 15:45:54 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: current@FreeBSD.ORG Subject: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 2000 15:45:54 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: 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 Sep 14 5:47:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from dataloss.net (ppp0.knz.ams.dataloss.net [212.189.231.51]) by hub.freebsd.org (Postfix) with SMTP id 326EE37B424 for ; Thu, 14 Sep 2000 05:47:46 -0700 (PDT) Received: (qmail 27006 invoked by uid 1000); 14 Sep 2000 12:48:42 -0000 Date: Thu, 14 Sep 2000 14:48:41 +0200 From: Peter van Dijk To: current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! Message-ID: <20000914144841.E22476@dataloss.net> Mail-Followup-To: current@FreeBSD.ORG References: <20000914115342.I77593@strontium.scientia.demon.co.uk> <56645.968935026@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <56645.968935026@critter>; from phk@critter.freebsd.dk on Thu, Sep 14, 2000 at 02:37:06PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 14, 2000 at 02:37:06PM +0200, Poul-Henning Kamp wrote: [snip] > The majority of these programs could be handled by adding knowledge > of "-" as a magic filename to fopen(3). > > At the same time I would really love if we implemented "|.*" to mean > "do an popen(3)" instead. Heh, and break security on loads of cgi-scripts while we're at it? Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 5:50:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from lobster.baynetworks.com (ns3.BayNetworks.COM [192.32.253.3]) by hub.freebsd.org (Postfix) with ESMTP id 055C437B42C; Thu, 14 Sep 2000 05:49:59 -0700 (PDT) Received: from mailhost.BayNetworks.COM (ns4.baynetworks.com [132.245.135.84]) by lobster.baynetworks.com (8.9.1/8.9.1) with ESMTP id IAA18319; Thu, 14 Sep 2000 08:47:41 -0400 (EDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id IAA19909; Thu, 14 Sep 2000 08:43:04 -0400 (EDT) Received: from baynetworks.com (kyzyl [192.32.150.103]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id IAA18449; Thu, 14 Sep 2000 08:43:04 -0400 for Message-Id: <200009141243.IAA18449@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: Ben Smithurst , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Message from Poul-Henning Kamp of "Thu, 14 Sep 2000 14:37:06 +0200." <56645.968935026@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 2000 08:43:04 -0400 From: Robert Withrow Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG phk@critter.freebsd.dk said: :- The majority of these programs could be handled by adding knowledge of :- "-" as a magic filename to fopen(3). Suppose I *want* a filename called "-"? My tough luck, huh? I *like* /dev/stdin. It's orthogonal! -- Robert Withrow -- (+1 978 288 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 6: 4: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from messagereach.com (memailout3.messagereach.com [205.183.255.234]) by hub.freebsd.org (Postfix) with ESMTP id 1B6E037B42C for ; Thu, 14 Sep 2000 06:03:53 -0700 (PDT) Received: from [205.183.255.234] (HELO memailout3) by messagereach.com (CommuniGate Pro SMTP 3.2b7) with ESMTP id 5668717 for freebsd-current@freebsd.org; Thu, 14 Sep 2000 09:03:48 -0400 To: freebsd-current@freebsd.org From: STS Marketing GmbH Subject: =?ISO-8859-1?Q?Die_=FCber_350_besten_Marketing-Praxis-Checklisten_...?= Mime-Version: 1.0 Message-Id: Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 14 Sep 2000 09:03:48 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG

Mehr Effizienz und Erfolg mit den besten Marketing-Praxis-Checklisten

Liebe Marketingverantwortliche

Stellen Sie sich vor, Sie m=FCssten bis morgen um 10.00 Uhr ein
erfolgsversprechendes Messekonzept pr=E4sentieren.

Oder kreative Ideen f=FCr die n=E4chste Direct-Mail-Aktion und bis in
zwei Tagen Vorschl=E4ge f=FCr ein erfolgreiches Internetmarketing
vorlegen. Und dies nat=FCrlich neben dem =FCblichen Alltagsgesch=E4ft!

Kein Problem mit unseren Marketing-Praxis-Checklisten. Sie sorgen
daf=FCr, dass Sie bei Ihrer t=E4glichen Arbeit entlastet werden und steigern
den Erfolg Ihrer Marketingaktivit=E4ten. Die Checklisten sind f=FCr
Fr. 145.00/St=FCck erh=E4ltlich und damit bereits nach der ersten Anwendung
amortisiert!

Schauen Sie bei uns rein und =FCberzeugen Sie sich von den Vorteilen des
Marketing-Checklisten-Managers, als Handbuch oder CD-Rom erh=E4ltlich:

http://www.stsmarketing.ch

Wir freuen uns auf Ihren Besuch.

Gruss
Stefan Schmidlin
Eid. dipl. Marketingleiter


P.S.: Lassen Sie sich anhand von 5 kostenlosen Checklisten nach ihrer
Wahl von der Qualit=E4t der Marketing-Checklisten-Sammlung =FCberzeugen.



This message was sent to you by Stefan Schmidlin, STS Marketing <= /p>

---------------------------------------------------------------------
Diese Nachricht wurde via MessageREACH versendet.
Wenn Sie keine weiteren Emails von diesem Empfaenger wuenschen:
1. Klicken Sie auf Antworten.
2. Ersetzen Sie den Text in der Betreff-Zeile durch REMOVE.
3. Klicken Sie auf Senden.
Sie werden ein letztes Mal eine Email mit einer Bestaetigung erhalten.
---------------------------------------------------------------------
This message was sent using the MessageREACH Service.
If you would prefer not to receive further messages from this sender:
1. Click on the Reply button.
2. Replace the Subject field with the word REMOVE.
3. Click the Send button.
You will receive one additional e-mail message confirming your removal.<= br>

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 6:40:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from nic.cafax.se (nic.cafax.se [192.71.228.17]) by hub.freebsd.org (Postfix) with ESMTP id 1FF6237B423; Thu, 14 Sep 2000 06:40:53 -0700 (PDT) Received: (from bygg@localhost) by nic.cafax.se (8.10.2/8.11.0.Gamma1) id e8EDegD10045; Thu, 14 Sep 2000 15:40:42 +0200 (MEST) Date: Thu, 14 Sep 100 15:40:42 WET DST From: Johnny Eriksson To: Robert Withrow Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Your message of Thu, 14 Sep 2000 08:43:04 -0400 Message-ID: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > phk@critter.freebsd.dk said: > :- The majority of these programs could be handled by adding knowledge of > :- "-" as a magic filename to fopen(3). > > Suppose I *want* a filename called "-"? My tough luck, huh? Could you settle for "./-"? > Robert Withrow -- (+1 978 288 8256) > BWithrow@BayNetworks.com --Johnny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 6:54:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from alpha.dante.org.uk (alpha.dante.org.uk [193.63.211.19]) by hub.freebsd.org (Postfix) with ESMTP id 0C66337B42C; Thu, 14 Sep 2000 06:54:47 -0700 (PDT) Received: from theta.dante.org.uk ([193.63.211.7]) by alpha.dante.org.uk with esmtp (Exim 3.12 #4) id 13ZZTP-00070a-00; Thu, 14 Sep 2000 14:54:43 +0100 Received: from localhost ([127.0.0.1] helo=dante.org.uk) by theta.dante.org.uk with esmtp (Exim 3.12 #4) id 13ZZTM-000332-00; Thu, 14 Sep 2000 14:54:40 +0100 Message-ID: <39C0D8A0.3BDC3B6C@dante.org.uk> Date: Thu, 14 Sep 2000 14:54:40 +0100 From: Konstantin Chuguev Organization: Delivery of Advanced Networking Service to Europe Ltd. X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en, ru MIME-Version: 1.0 To: Johnny Eriksson , hackers@freebsd.org, current@freebsd.org Subject: /proc & /dev/std* [Was: Fdescfs updates--coming to a devfs near you!] References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johnny Eriksson wrote: > > phk@critter.freebsd.dk said: > > :- The majority of these programs could be handled by adding knowledge of > > :- "-" as a magic filename to fopen(3). > > > > Suppose I *want* a filename called "-"? My tough luck, huh? > > Could you settle for "./-"? > I think any "magic" name is not very good idea. To say more, it breaks POSIX. File names are a tratitional UNIX way to access character and block devices; in System V you can access much more via file names, using streams. Magic numbers are for MS DOS (remember COM1 and LPT1? :-) I am not sure /proc/ names are very useful, but /dev/std{in|out|err} definitely are. -- * * Konstantin Chuguev - Application Engineer * * Francis House, 112 Hills Road * Cambridge CB2 1PQ, United Kingdom D A N T E WWW: http://www.dante.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 6:58:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom2-053.telepath.com [216.14.2.53]) by hub.freebsd.org (Postfix) with SMTP id 3182337B423 for ; Thu, 14 Sep 2000 06:58:22 -0700 (PDT) Received: (qmail 63109 invoked by uid 100); 14 Sep 2000 13:57:41 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14784.55637.790917.142533@guru.mired.org> Date: Thu, 14 Sep 2000 08:57:41 -0500 (CDT) To: Poul-Henning Kamp Cc: Ben Smithurst , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: <56645.968935026@critter> References: <20000914115342.I77593@strontium.scientia.demon.co.uk> <56645.968935026@critter> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > In message <20000914115342.I77593@strontium.scientia.demon.co.uk>, Ben Smithurs > t writes: > >Poul-Henning Kamp wrote: > > > >> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > >> is bogus. It looks like something which happened "because we can" more > >> than something which has a legitimate need. > >You think adding a hack to every program to support "-" to mean > >stdout/stdin is better? > The majority of these programs could be handled by adding knowledge > of "-" as a magic filename to fopen(3). Ugh. So what happens when you *really* want to read a filed called "-"? Adding magic characters to low-level calls is a bad idea. I believe /dev/fd originated in Unix v8 (or maybe plan 9) to provide a uniform mechanism to get a class of process-internal objects where they can be manipulated by shell scripts. If that's the case, it's provenance is impeccable. > At the same time I would really love if we implemented "|.*" to mean > "do an popen(3)" instead. Again, putting magic character recognition in a low-level call is a bad idea. Worse yet, this kind of thing is really useful in shells (which don't generally have the ability to manipulate fd's). Consider trying to use that syntax in the shell? Which is why modern shells that implement this kind of thing use a different syntax. Of course, they depend on something like /dev/fd or named pipes to provide this feature. > But of course, this is bikeshed material... Most certainly. If you really want to make C programming look like Perl programming, could you do it by adding new library calls, instead of changing the semantics of existing ones? Cc: Ben Smithurst , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Your message of "Thu, 14 Sep 2000 08:43:04 EDT." <200009141243.IAA18449@pobox.engeast.BayNetworks.COM> Date: Thu, 14 Sep 2000 16:21:14 +0200 Message-ID: <56995.968941274@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009141243.IAA18449@pobox.engeast.BayNetworks.COM>, Robert Withro w writes: > >phk@critter.freebsd.dk said: >:- The majority of these programs could be handled by adding knowledge of >:- "-" as a magic filename to fopen(3). > >Suppose I *want* a filename called "-"? My tough luck, huh? ./- Very few programs understand the filename "-" unless it is special cased to mean stdin/stdout -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Thu Sep 14 8:28:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 346B337B423 for ; Thu, 14 Sep 2000 08:28:53 -0700 (PDT) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.11.0/8.11.0) with ESMTP id e8EFSq331697 for ; Thu, 14 Sep 2000 08:28:52 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.11.0/8.11.0) id e8EFTOn05662 for current@FreeBSD.ORG; Thu, 14 Sep 2000 08:29:24 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200009141529.e8EFTOn05662@realtime.exit.com> Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: <56076.968924938@critter> from Poul-Henning Kamp at "Sep 14, 2000 11:48:58 am" To: Poul-Henning Kamp Date: Thu, 14 Sep 2000 08:15:54 -0700 (PDT) Cc: Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORGG Reply-To: frank@exit.com Organization: Exit Consulting X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > is bogus. It looks like something which happened "because we can" more > than something which has a legitimate need. I strongly disagree. I actually have a script that I use daily which requires a filename as an argument. By handing it /dev/stdin, I can make it take output as a part of a pipe. A _very_ useful little feature, IMNSHO. As far as fdescfs, well, Unixware has something very like it, and I believe that other commercial Unices do as well. I suspect that it's useful to some, if not to all. One thing about end users as opposed to engineers, they put this stuff to uses that we can't even imagine. Never underestimate the sheer ingenuity of a relatively naive user. :-) -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 8:31:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom2-076.telepath.com [216.14.2.76]) by hub.freebsd.org (Postfix) with SMTP id 9308037B423 for ; Thu, 14 Sep 2000 08:31:11 -0700 (PDT) Received: (qmail 65749 invoked by uid 100); 14 Sep 2000 15:30:33 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14784.61209.225359.190407@guru.mired.org> Date: Thu, 14 Sep 2000 10:30:33 -0500 (CDT) To: current@freebsd.org Cc: questions@FreeBSD.ORG Subject: Re: Star Office and editor In-Reply-To: References: <14784.12222.692069.885803@guru.mired.org> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just realized this may be a difference due to a between -current and -stable, so I've moved discussion to -current to check. Apologies if this was the wrong thing to do. On Wed, 13 Sep 2000, Mike Meyer wrote: > It then fails to install for me with the error messages: > > /tmp/sv001.tmp/setup.bin: error in loading shared libraries: libvos1GCC.so: cannot open shared object file: No such file or directory I recall something about things running under the linux emulator *sometimes* treating references to / as references to /compat/linux. I'm thinking that this may be the problem, and it's not causing problems with -stable - yet. In particular, I'm wondering if the install file (an executable) is putting shared libraries in /tmp that executable it installs are then trying to find somewhere else - because of this path tweaking. I did try creating a /compat/linux/tmp that was a symlink to /tmp. I didn't fool with /compat/linux/usr/tmp, as it already existed. Anyone have any insight into this? Suggestions? Thanx, ; Thu, 14 Sep 2000 08:39:22 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA12284; Thu, 14 Sep 2000 11:36:45 -0400 (EDT) (envelope-from wollman) Date: Thu, 14 Sep 2000 11:36:45 -0400 (EDT) From: Garrett Wollman Message-Id: <200009141536.LAA12284@khavrinen.lcs.mit.edu> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: <56076.968924938@critter> References: <20000914123945.A32524@ringwraith.office1.bg> <56076.968924938@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > is bogus. It looks like something which happened "because we can" more > than something which has a legitimate need. It's required if we ever get around to supporting secure set-id shell scripts. (I think this was the rationale for originally introducing it.) It also helps when bogus programs refuse to read from the standard input. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 10:17: 3 2000 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 D574137B42C; Thu, 14 Sep 2000 10:16:58 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA13053; Thu, 14 Sep 2000 13:16:58 -0400 (EDT) (envelope-from wollman) Date: Thu, 14 Sep 2000 13:16:58 -0400 (EDT) From: Garrett Wollman Message-Id: <200009141716.NAA13053@khavrinen.lcs.mit.edu> To: current@freebsd.org, hubs@freebsd.org Reply-To: wollman@lcs.mit.edu Subject: cvsup3 now carries rsa_eay.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG MIT's Technology Licensing Office has given me the OK to distribute rsa_eay.c, so it will now be available from cvsup3.freebsd.org (aka freebsd.lcs.mit.edu). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 11:34:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 70CBB37B422 for ; Thu, 14 Sep 2000 11:34:56 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13ZcvX-0006vO-00; Thu, 14 Sep 2000 18:35:59 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id SAA25231; Thu, 14 Sep 2000 18:35:58 +0100 (BST) (envelope-from ben) Date: Thu, 14 Sep 2000 18:35:58 +0100 From: Ben Smithurst To: Garrett Wollman Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! Message-ID: <20000914183558.K77593@strontium.scientia.demon.co.uk> References: <20000914123945.A32524@ringwraith.office1.bg> <56076.968924938@critter> <200009141536.LAA12284@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009141536.LAA12284@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > [/dev/stdin] also helps when bogus programs refuse to read from the > standard input. Or if you want to read more than one file, one of which is standard input. e.g. gzip -dc oldlogs.*.gz | cat /dev/stdin todays-log | log-analyzer ... Of course that will work with "-" instead of "/dev/stdin" but I personally think it's the "-" hack to mean stdin/stdout which should be abolished, not /dev/std{in,out,err}. No doubt others will disagree. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 11:41: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.m.iinet.net.au (opera3.iinet.net.au [203.59.24.51]) by hub.freebsd.org (Postfix) with SMTP id 53BED37B423 for ; Thu, 14 Sep 2000 11:41:00 -0700 (PDT) Received: (qmail 16789 invoked by uid 666); 14 Sep 2000 18:40:57 -0000 Received: from unknown (HELO jules.elischer.org) (203.59.169.109) by mail.m.iinet.net.au with SMTP; 14 Sep 2000 18:40:57 -0000 Message-ID: <39C11BB2.1CFBAE39@elischer.org> Date: Thu, 14 Sep 2000 11:40:50 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: newbus docs Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it's time I learned about the rather cryptic newbus stuff....... So where are the best docs to read on it.? Ones that give an overview? "UTSL" and "See man 9 {cryptic function name}" are not the answers I'm looking for... Someone once mentionned an actual document but I've been unable to find it. Was it my imagination? (and if so, why isn't there one?) -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 11:56: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id B837637B440 for ; Thu, 14 Sep 2000 11:55:59 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id LAA83998 for current@FreeBSD.org; Thu, 14 Sep 2000 11:55:49 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009141855.LAA83998@pike.osd.bsdi.com> Subject: Re: Fdescfs updates--coming to a devfs near you! To: current@FreeBSD.org Date: Thu, 14 Sep 2000 11:55:49 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message <20000914123945.A32524@ringwraith.office1.bg>, Peter Pentchev writes > : > >On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote: > >> I've never thought of a use for fdescfs... > > > >Well.. just a trivial example - imagine a program which takes a filename > >as an argument; imagine yourself trying to pipe something into it - > >passing /dev/fd/0 as a filename to process would do the trick. > > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > is bogus. It looks like something which happened "because we can" more > than something which has a legitimate need. How about the fact that the printing chapter in the Handbook uses /dev/fd/0 in its example of setting up a print filter using ghostscript since gs doesn't read from stdin by default or use '-' for that purpose. Hmmm?? > If anything I would propose we ditch it... Tools, not policy, as you are so fond of saying. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "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 Sep 14 12:11:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 795C037B422 for ; Thu, 14 Sep 2000 12:11:48 -0700 (PDT) Received: (qmail 32192 invoked from network); 14 Sep 2000 19:11:39 -0000 Received: from lcp196.cvzoom.net (208.230.68.196) by ns.cvzoom.net with SMTP; 14 Sep 2000 19:11:39 -0000 Date: Thu, 14 Sep 2000 15:11:38 -0400 (EDT) From: Donn Miller To: John Baldwin Cc: current@FreeBSD.org Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: <200009141855.LAA83998@pike.osd.bsdi.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, 14 Sep 2000, John Baldwin wrote: > Poul-Henning Kamp wrote: > > In message <20000914123945.A32524@ringwraith.office1.bg>, Peter Pentchev writes > > > > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > > is bogus. It looks like something which happened "because we can" more > > than something which has a legitimate need. > > How about the fact that the printing chapter in the Handbook uses /dev/fd/0 > in its example of setting up a print filter using ghostscript since gs > doesn't read from stdin by default or use '-' for that purpose. Hmmm?? Actually, I think it should be the other way around: if anything should go, it's the use of '-' in programs/scripts. The only advantage is that it saves keystrokes. I agree, /dev/std{in,out} is a very neat and elegant way of working with stdin/out. If anything is the kludge, it's '-', and it's really vague as to what it means. With /dev/std{in,out}, there's no doubt as to what's going on with file ops. Plus, it's the unix way (tm) of doing things. Almost all Unices have this, don't they? This means there's likely to be some cross-platform shell scripts that use those things. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 12:29:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 2A56C37B423 for ; Thu, 14 Sep 2000 12:29:31 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id MAA85518; Thu, 14 Sep 2000 12:28:09 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009141928.MAA85518@pike.osd.bsdi.com> Subject: Re: SMPNG kernel on UP In-Reply-To: <200009140605.AAA94177@harmony.village.org> from Warner Losh at "Sep 14, 2000 00:05:03 am" To: Warner Losh Date: Thu, 14 Sep 2000 12:28:09 -0700 (PDT) Cc: Mark Murray , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <200009140602.e8E628n03046@grimreaper.grondar.za> Mark Murray writes: > : > In message <200009080636.e886aCG18672@billy-club.village.org> Warner Losh wri > : tes: > : > : 2) APM is now broken. It worked after the ACPI integration, > : > : but after the SMPNG stuff neither apm -z nor the BIOS keys > : > : seems to suspend. > : > > : > Turns out this isn't the case. > : > : shutdown -p does not turn off the machine for me (Libretto 110ct). > : > : zzz/apm -z gives me "apm: ioctl(APMIO_SUSPEND): Invalid argument" > > I noticed this with the first SMPNG kernel I tried. The newer one > this problem disappeared. Don't know why it would matter, but I may > have missed a commit while in new mexico. It may be a kernel/world sync problem. Although I don't know why the ioctl argument would suddenly become invalid. Maybe it passes in a struct ucred, which changed in size just before the SMPng commit? > Warner -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "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 Sep 14 12:31:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id 3A83437B422; Thu, 14 Sep 2000 12:31:43 -0700 (PDT) Received: (from uucp@localhost) by light.imasy.or.jp (8.11.0+3.3W/3.7W-light) with UUCP id e8EJUP009944; Fri, 15 Sep 2000 04:30:25 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from localhost (peace.mahoroba.org [2001:200:301:0:200:f8ff:fe05:3eae]) by mail.mahoroba.org (8.11.0/8.11.0/chaos) with ESMTP/inet6 id e8EJSQm27102; Fri, 15 Sep 2000 04:28:26 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Fri, 15 Sep 2000 04:28:25 +0900 (JST) Message-Id: <20000915.042825.59653153.ume@mahoroba.org> To: freebsd-current@freebsd.org, freebsd-net@freebsd.org Subject: [CFR] KLDfy ip6_fw From: Hajimu UMEMOTO X-Mailer: Mew version 1.95b38 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I made KLD module of ip6_fw. Please review it. http://www.imasy.or.jp/~ume/ipv6/FreeBSD/ip6_fw-kld-5C.diff for 5-CURRENT http://www.imasy.or.jp/~ume/ipv6/FreeBSD/ip6_fw-kld-41R.diff for 4.1-RELEASE Thanks, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 12:33: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E438037B422 for ; Thu, 14 Sep 2000 12:32:59 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA71386; Thu, 14 Sep 2000 13:32:58 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA98362; Thu, 14 Sep 2000 13:32:25 -0600 (MDT) Message-Id: <200009141932.NAA98362@harmony.village.org> To: John Baldwin Subject: Re: SMPNG kernel on UP Cc: Mark Murray , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 14 Sep 2000 12:28:09 PDT." <200009141928.MAA85518@pike.osd.bsdi.com> References: <200009141928.MAA85518@pike.osd.bsdi.com> Date: Thu, 14 Sep 2000 13:32:25 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009141928.MAA85518@pike.osd.bsdi.com> John Baldwin writes: : It may be a kernel/world sync problem. Although I don't know why the ioctl : argument would suddenly become invalid. Maybe it passes in a struct ucred, : which changed in size just before the SMPng commit? I don't know either. However, it might be because of permission problems. It will return EINVAL when it can't open the apm file for write. Maybe a devfs related issue? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 12:42:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 5496F37B424 for ; Thu, 14 Sep 2000 12:42:54 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id MAA86101; Thu, 14 Sep 2000 12:41:51 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009141941.MAA86101@pike.osd.bsdi.com> Subject: Re: SMPNG kernel on UP In-Reply-To: <200009141932.NAA98362@harmony.village.org> from Warner Losh at "Sep 14, 2000 01:32:25 pm" To: Warner Losh Date: Thu, 14 Sep 2000 12:41:51 -0700 (PDT) Cc: Mark Murray , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <200009141928.MAA85518@pike.osd.bsdi.com> John Baldwin writes: > : It may be a kernel/world sync problem. Although I don't know why the ioctl > : argument would suddenly become invalid. Maybe it passes in a struct ucred, > : which changed in size just before the SMPng commit? > > I don't know either. However, it might be because of permission > problems. It will return EINVAL when it can't open the apm file for > write. Maybe a devfs related issue? Hmm, it may not be using the right perms during make_dev perhaps. > Warner -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "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 Sep 14 12:47:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7152337B423 for ; Thu, 14 Sep 2000 12:47:18 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA71479; Thu, 14 Sep 2000 13:47:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA98535; Thu, 14 Sep 2000 13:46:44 -0600 (MDT) Message-Id: <200009141946.NAA98535@harmony.village.org> To: John Baldwin Subject: Re: SMPNG kernel on UP Cc: Mark Murray , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 14 Sep 2000 12:41:51 PDT." <200009141941.MAA86101@pike.osd.bsdi.com> References: <200009141941.MAA86101@pike.osd.bsdi.com> Date: Thu, 14 Sep 2000 13:46:44 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009141941.MAA86101@pike.osd.bsdi.com> John Baldwin writes: : Warner Losh wrote: : > In message <200009141928.MAA85518@pike.osd.bsdi.com> John Baldwin writes: : > : It may be a kernel/world sync problem. Although I don't know why the ioctl : > : argument would suddenly become invalid. Maybe it passes in a struct ucred, : > : which changed in size just before the SMPng commit? : > : > I don't know either. However, it might be because of permission : > problems. It will return EINVAL when it can't open the apm file for : > write. Maybe a devfs related issue? : : Hmm, it may not be using the right perms during make_dev perhaps. Hmmm, they look good to me. Maybe Mark's system doesn't have group operator at gid 5. That's one bad thing about the new DEVFS: it appears to enshrine things like this in the kernel... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 13:34:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 1ACA237B424; Thu, 14 Sep 2000 13:34:22 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA199770; Thu, 14 Sep 2000 16:31:25 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <56076.968924938@critter> References: <56076.968924938@critter> Date: Thu, 14 Sep 2000 16:33:55 -0400 To: Poul-Henning Kamp , Peter Pentchev From: Garance A Drosihn Subject: Re: Fdescfs updates--coming to a devfs near you! Cc: Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:48 AM +0200 9/14/00, Poul-Henning Kamp wrote: >I must admit that I think in general that /dev/std{in,out,err} >and /dev/fd is bogus. It looks like something which happened >"because we can" more than something which has a legitimate need. > >If anything I would propose we ditch it... I think it is a reasonable feature to have. It probably won't be useful all that often, but it could be very useful in some situations. I know I've hit situations where I wished I could do something like this, but I couldn't tell you an example right this minute. So, I wouldn't want to see fdesfs ditched, but on the other hand I don't have any clue how to address the loose ends that Chris mentioned in his initial message. :-) --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 13:42:12 2000 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 4F2BB37B422 for ; Thu, 14 Sep 2000 13:42:08 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA15287; Thu, 14 Sep 2000 16:42:00 -0400 (EDT) (envelope-from wollman) Date: Thu, 14 Sep 2000 16:42:00 -0400 (EDT) From: Garrett Wollman Message-Id: <200009142042.QAA15287@khavrinen.lcs.mit.edu> To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: SMPNG kernel on UP In-Reply-To: <200009141946.NAA98535@harmony.village.org> References: <200009141941.MAA86101@pike.osd.bsdi.com> <200009141946.NAA98535@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Hmmm, they look good to me. Maybe Mark's system doesn't have group > operator at gid 5. That's one bad thing about the new DEVFS: it > appears to enshrine things like this in the kernel... It would only take a small amount of Makefile magic to fix this... something like: PASSWD?= /etc/passwd GROUP?= /etc/group uidgid.h: ${PASSWD} ${GROUP} perl -ne 'split(/:/); print ("#define\tUID_", uc($_[0]), "\t", \ $_[2], "\n");' ${PASSWD} >${.TARGET} perl -ne 'split(/:/); print ("#define\tGID_", uc($_[0]), "\t", \ $_[2], "\n");' ${GROUP} >>${.TARGET} ...add this to and include "uidgid.h" as necessary in source files. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 13:45:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 62EAE37B424 for ; Thu, 14 Sep 2000 13:45:18 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA71768; Thu, 14 Sep 2000 14:45:15 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA99073; Thu, 14 Sep 2000 14:44:42 -0600 (MDT) Message-Id: <200009142044.OAA99073@harmony.village.org> To: Garrett Wollman Subject: Re: SMPNG kernel on UP Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 14 Sep 2000 16:42:00 EDT." <200009142042.QAA15287@khavrinen.lcs.mit.edu> References: <200009142042.QAA15287@khavrinen.lcs.mit.edu> <200009141941.MAA86101@pike.osd.bsdi.com> <200009141946.NAA98535@harmony.village.org> Date: Thu, 14 Sep 2000 14:44:42 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009142042.QAA15287@khavrinen.lcs.mit.edu> Garrett Wollman writes: : < said: : > Hmmm, they look good to me. Maybe Mark's system doesn't have group : > operator at gid 5. That's one bad thing about the new DEVFS: it : > appears to enshrine things like this in the kernel... : : It would only take a small amount of Makefile magic to fix : this... something like: : : PASSWD?= /etc/passwd : GROUP?= /etc/group : : uidgid.h: ${PASSWD} ${GROUP} : perl -ne 'split(/:/); print ("#define\tUID_", uc($_[0]), "\t", \ : $_[2], "\n");' ${PASSWD} >${.TARGET} : perl -ne 'split(/:/); print ("#define\tGID_", uc($_[0]), "\t", \ : $_[2], "\n");' ${GROUP} >>${.TARGET} : : ...add this to and include "uidgid.h" as necessary in : source files. Hmmm, I like it... But it does suffer from one problem that we already have enough of in our tree. The build on one system, install on another problem. It would be better than the current situtation. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 13:54: 2 2000 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 025D637B43C for ; Thu, 14 Sep 2000 13:54:01 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA15413; Thu, 14 Sep 2000 16:53:54 -0400 (EDT) (envelope-from wollman) Date: Thu, 14 Sep 2000 16:53:54 -0400 (EDT) From: Garrett Wollman Message-Id: <200009142053.QAA15413@khavrinen.lcs.mit.edu> To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: SMPNG kernel on UP In-Reply-To: <200009142042.QAA15287@khavrinen.lcs.mit.edu> References: <200009141941.MAA86101@pike.osd.bsdi.com> <200009141946.NAA98535@harmony.village.org> <200009142042.QAA15287@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < It would only take a small amount of Makefile magic to fix > this... something like: > perl -ne 'split(/:/); print ("#define\tUID_", uc($_[0]), "\t", \ > $_[2], "\n");' ${PASSWD} >${.TARGET} Oh, I forgot to point out -- this would be easy to do in AWK as well. (Probably easier, actually, but I don't know AWK well enough to actually implement it.) -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 14: 8:47 2000 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 4D5CE37B424 for ; Thu, 14 Sep 2000 14:08:43 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8EL7vN59170; Thu, 14 Sep 2000 23:07:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: John Baldwin , Mark Murray , current@FreeBSD.ORG Subject: Re: SMPNG kernel on UP In-Reply-To: Your message of "Thu, 14 Sep 2000 13:46:44 MDT." <200009141946.NAA98535@harmony.village.org> Date: Thu, 14 Sep 2000 23:07:57 +0200 Message-ID: <59168.968965677@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009141946.NAA98535@harmony.village.org>, Warner Losh writes: >In message <200009141941.MAA86101@pike.osd.bsdi.com> John Baldwin writes: >: Warner Losh wrote: >: > In message <200009141928.MAA85518@pike.osd.bsdi.com> John Baldwin writes: >: > : It may be a kernel/world sync problem. Although I don't know why the ioctl >: > : argument would suddenly become invalid. Maybe it passes in a struct ucred, >: > : which changed in size just before the SMPng commit? >: > >: > I don't know either. However, it might be because of permission >: > problems. It will return EINVAL when it can't open the apm file for >: > write. Maybe a devfs related issue? >: >: Hmm, it may not be using the right perms during make_dev perhaps. > >Hmmm, they look good to me. Maybe Mark's system doesn't have group >operator at gid 5. That's one bad thing about the new DEVFS: it >appears to enshrine things like this in the kernel... Yes, this is a bad thing, but it is the best compromise solution. You can either manually or with a future general devd(8) fix this. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Thu Sep 14 15:16:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from w250.z064001178.sjc-ca.dsl.cnc.net (w250.z064001178.sjc-ca.dsl.cnc.net [64.1.178.250]) by hub.freebsd.org (Postfix) with SMTP id 445F037B424 for ; Thu, 14 Sep 2000 15:16:34 -0700 (PDT) Received: (qmail 15961 invoked by uid 1000); 14 Sep 2000 22:16:50 -0000 Date: Thu, 14 Sep 2000 15:16:50 -0700 From: Jos Backus To: current@FreeBSD.ORG Subject: Re: SMPNG kernel on UP Message-ID: <20000914151650.A15150@lizzy.bugworks.com> Reply-To: Jos Backus Mail-Followup-To: current@FreeBSD.ORG References: <200009141941.MAA86101@pike.osd.bsdi.com> <200009141946.NAA98535@harmony.village.org> <200009142042.QAA15287@khavrinen.lcs.mit.edu> <200009142053.QAA15413@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009142053.QAA15413@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Thu, Sep 14, 2000 at 04:53:54PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 14, 2000 at 04:53:54PM -0400, Garrett Wollman wrote: > (Probably easier, actually, but I don't know AWK well enough to > actually implement it.) awk -F: '$0 ~/^(#|$)/ {next} {print "#define\tUID_" toupper($1) "\t" $3}' ${PASSWD} > ${.TARGET} -- Jos Backus _/ _/_/_/ "Modularity is not a hack." _/ _/ _/ -- D. J. Bernstein _/ _/_/_/ _/ _/ _/ _/ josb@cncdsl.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 15:32:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id 1367637B422; Thu, 14 Sep 2000 15:32:49 -0700 (PDT) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with esmtp (Exim 1.92 #8) id 13ZhYm-0001Qp-00; Thu, 14 Sep 2000 15:32:48 -0700 Received: from localhost (localhost [127.0.0.1]) by asimov.phoenix.volant.org (8.9.3+Sun/8.9.3) with SMTP id PAA19703; Thu, 14 Sep 2000 15:32:47 -0700 (PDT) From: patl@Phoenix.Volant.ORG Date: Thu, 14 Sep 2000 15:32:47 -0700 (PDT) Reply-To: patl@Phoenix.Volant.ORG Subject: Re: "!.*" [ was: Fdescfs updates--coming to a devfs near you! ] To: Poul-Henning Kamp Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <56645.968935026@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 14-Sep-00 at 05:37, Poul-Henning Kamp (phk@critter.freebsd.dk) wrote: > >You think adding a hack to every program to support "-" to mean > >stdout/stdin is better? > > The majority of these programs could be handled by adding knowledge > of "-" as a magic filename to fopen(3). > > At the same time I would really love if we implemented "|.*" to mean > "do an popen(3)" instead. Isn't that potentially a huge security hole in every program that gets a filename from an external source? > But of course, this is bikeshed material... > > >> If anything I would propose we ditch it... > > > >And break loads of scripts at the same time? > > I would argue that the programs and the scripts that call them are > already broken, but hey... And I would argue that the fdescfs is cleaner than the '-' hack. (Which, by the way, should not be considered a filename hack so much as a command-line-parameter hack; since it was invented before there was a way to say 'use stdin/stdout' on the command-line... You could think of '/dev/stdin' as "'-' version 2") -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 16: 0:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2508837B423 for ; Thu, 14 Sep 2000 16:00:38 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA72351; Thu, 14 Sep 2000 17:00:36 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA00185; Thu, 14 Sep 2000 17:00:02 -0600 (MDT) Message-Id: <200009142300.RAA00185@harmony.village.org> To: Garrett Wollman Subject: Re: Fdescfs updates--coming to a devfs near you! Cc: Poul-Henning Kamp , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 14 Sep 2000 11:36:45 EDT." <200009141536.LAA12284@khavrinen.lcs.mit.edu> References: <200009141536.LAA12284@khavrinen.lcs.mit.edu> <20000914123945.A32524@ringwraith.office1.bg> <56076.968924938@critter> Date: Thu, 14 Sep 2000 17:00:02 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009141536.LAA12284@khavrinen.lcs.mit.edu> Garrett Wollman writes: : It's required if we ever get around to supporting secure set-id shell : scripts. (I think this was the rationale for originally introducing : it.) It also helps when bogus programs refuse to read from the : standard input. I'd like to see us enable that. It would remove the need to have setuid perl, for example. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 16: 1:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8799337B422 for ; Thu, 14 Sep 2000 16:01:29 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA72359; Thu, 14 Sep 2000 17:01:28 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA00207; Thu, 14 Sep 2000 17:00:54 -0600 (MDT) Message-Id: <200009142300.RAA00207@harmony.village.org> To: Julian Elischer Subject: Re: newbus docs Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 14 Sep 2000 11:40:50 PDT." <39C11BB2.1CFBAE39@elischer.org> References: <39C11BB2.1CFBAE39@elischer.org> Date: Thu, 14 Sep 2000 17:00:54 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39C11BB2.1CFBAE39@elischer.org> Julian Elischer writes: : Someone once mentionned an actual : document but I've been unable to find it. : Was it my imagination? : (and if so, why isn't there one?) What do you mean actual document? man pages are actual documents. What kind of document do you want? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 16: 1:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id CE5EC37B423; Thu, 14 Sep 2000 16:01:41 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13ZhYW-0007Fi-00; Thu, 14 Sep 2000 23:32:32 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id XAA65575; Thu, 14 Sep 2000 23:32:32 +0100 (BST) (envelope-from ben) Date: Thu, 14 Sep 2000 23:32:31 +0100 From: Ben Smithurst To: Bruce Evans Cc: current@FreeBSD.ORG, jasone@FreeBSD.org, jhb@FreeBSD.org Subject: Re: page fault in sched_ithd Message-ID: <20000914233231.N77593@strontium.scientia.demon.co.uk> References: <20000909210619.F77593@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Ls2Gy6y7jbHLe9Od" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Ls2Gy6y7jbHLe9Od Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Bruce Evans wrote: > On Sat, 9 Sep 2000, Ben Smithurst wrote: > >> After poking around a bit with remote GDB, this seems to be caused by a >> stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM. >> >> The attached rather crude patch has "fixed" the problem for now, but >> does anyone have any suggestions for a real fix? > > The stray interrupt handler needs to have a thread, or stray interrupts > need to be handled as traps. Stray interrupts are more like NMIs than > normal interrupts, and NMIs are already (mis)handled as traps. OK, but would you or anyone else object to the attached patch as a temporary fix, at least? Page-faulting almost immediately is not particularly good. The patch doesn't seem to have had any negative effects so far. Who are the main people responsible for the SMPng stuff anyway? jasone and jhb seem to have been involved a bit, so I cc'd them as well. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D --Ls2Gy6y7jbHLe9Od Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ithread.diff" Index: ithread.c =================================================================== RCS file: /usr/cvs/src/sys/i386/isa/ithread.c,v retrieving revision 1.3 diff -u -r1.3 ithread.c --- ithread.c 2000/09/13 18:33:23 1.3 +++ ithread.c 2000/09/14 22:06:44 @@ -95,6 +95,8 @@ SYSINIT(start_softintr, SI_SUB_SOFTINTR, SI_ORDER_FIRST, start_softintr, NULL) +#define MAX_STRAY_LOG 5 + /* * Schedule a heavyweight interrupt process. This function is called * from the interrupt handlers Xintr. @@ -103,6 +105,7 @@ sched_ithd(void *cookie) { int irq = (int) cookie; /* IRQ we're handling */ + static int straycount[NHWI]; /* count of stray IRQs */ struct ithd *ir = ithds[irq]; /* and the process that does it */ /* This used to be in icu_vector.s */ @@ -144,6 +147,21 @@ } #endif + /* XXX: quick fix to avoid page fault until this is done properly. */ + if (ir == NULL) { + if (irq < NHWI) { + if (straycount[irq] < MAX_STRAY_LOG) { + printf("stray irq %d\n", irq); + if (++straycount[irq] == MAX_STRAY_LOG) + printf("got %d stray irq %d's: " + "not logging anymore\n", + MAX_STRAY_LOG, irq); + } + return; + } + panic("sched_ithd: ithds[%d] == NULL", irq); + } + /* * Set it_need so that if the thread is already running but close * to done, it will do another go-round. Then get the sched lock --Ls2Gy6y7jbHLe9Od-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 16: 3:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6112237B423 for ; Thu, 14 Sep 2000 16:03:29 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA26496; Thu, 14 Sep 2000 16:03:14 -0700 Date: Thu, 14 Sep 2000 16:03:13 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Warner Losh Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: newbus docs In-Reply-To: <200009142300.RAA00207@harmony.village.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 On Thu, 14 Sep 2000, Warner Losh wrote: > In message <39C11BB2.1CFBAE39@elischer.org> Julian Elischer writes: > : Someone once mentionned an actual > : document but I've been unable to find it. > : Was it my imagination? > : (and if so, why isn't there one?) > > What do you mean actual document? man pages are actual documents. > What kind of document do you want? I would imagine an overall architecture doc. Sort of like what Jordan just did for sysinst (e.g.). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 16: 3:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 3370D37B624; Thu, 14 Sep 2000 16:03:37 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id QAA95584; Thu, 14 Sep 2000 16:03:37 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009142303.QAA95584@pike.osd.bsdi.com> Subject: Re: page fault in sched_ithd In-Reply-To: <20000914233231.N77593@strontium.scientia.demon.co.uk> from Ben Smithurst at "Sep 14, 2000 11:32:31 pm" To: Ben Smithurst Date: Thu, 14 Sep 2000 16:03:37 -0700 (PDT) Cc: Bruce Evans , current@FreeBSD.org, jasone@FreeBSD.org, jhb@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst wrote: > Bruce Evans wrote: > > > On Sat, 9 Sep 2000, Ben Smithurst wrote: > > > >> After poking around a bit with remote GDB, this seems to be caused by a > >> stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM. > >> > >> The attached rather crude patch has "fixed" the problem for now, but > >> does anyone have any suggestions for a real fix? > > > > The stray interrupt handler needs to have a thread, or stray interrupts > > need to be handled as traps. Stray interrupts are more like NMIs than > > normal interrupts, and NMIs are already (mis)handled as traps. > > OK, but would you or anyone else object to the attached patch as a > temporary fix, at least? Page-faulting almost immediately is not > particularly good. The patch doesn't seem to have had any negative > effects so far. > > Who are the main people responsible for the SMPng stuff anyway? jasone > and jhb seem to have been involved a bit, so I cc'd them as well. This looks good to me, let me through it my tree here and try it out. For SMPng stuff, probably just sending to the smp@ list should be sufficient. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "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 Sep 14 16: 4:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 45F8137B422 for ; Thu, 14 Sep 2000 16:04:55 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA72410; Thu, 14 Sep 2000 17:04:53 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA00326; Thu, 14 Sep 2000 17:04:20 -0600 (MDT) Message-Id: <200009142304.RAA00326@harmony.village.org> To: mjacob@feral.com Subject: Re: newbus docs Cc: Julian Elischer , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 14 Sep 2000 16:03:13 PDT." References: Date: Thu, 14 Sep 2000 17:04:20 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Matthew Jacob writes: : I would imagine an overall architecture doc. Sort of like what : Jordan just did for sysinst (e.g.). Then he should ask for an architecture doc rather than being so snippy and snide about "actual documentation." Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 16: 7: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id A350A37B422 for ; Thu, 14 Sep 2000 16:07:01 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id TAA38354; Thu, 14 Sep 2000 19:07:13 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Thu, 14 Sep 2000 19:07:13 -0400 (EDT) From: "Brandon D. Valentine" To: Warner Losh Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: newbus docs In-Reply-To: <200009142300.RAA00207@harmony.village.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 On Thu, 14 Sep 2000, Warner Losh wrote: >In message <39C11BB2.1CFBAE39@elischer.org> Julian Elischer writes: >: Someone once mentionned an actual >: document but I've been unable to find it. >: Was it my imagination? >: (and if so, why isn't there one?) > >What do you mean actual document? man pages are actual documents. >What kind of document do you want? Probably something like this: http://people.freebsd.org/~asmodai/newbus-draft.txt or this: http://www.daemonnews.org/200007/newbus-intro.html Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 16:13:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8BE0737B424 for ; Thu, 14 Sep 2000 16:13:08 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA26559; Thu, 14 Sep 2000 16:12:54 -0700 Date: Thu, 14 Sep 2000 16:12:52 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Warner Losh Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: newbus docs In-Reply-To: <200009142304.RAA00326@harmony.village.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 > In message Matthew Jacob writes: > : I would imagine an overall architecture doc. Sort of like what > : Jordan just did for sysinst (e.g.). > > Then he should ask for an architecture doc rather than being so snippy > and snide about "actual documentation." Probably, but I totally sympathize with him. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 16:38:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from hermes.dialup.ru (hermes.dialup.ru [194.87.16.230]) by hub.freebsd.org (Postfix) with ESMTP id AB06F37B42C; Thu, 14 Sep 2000 16:38:38 -0700 (PDT) Received: (from ache@localhost) by hermes.dialup.ru (8.11.0/8.11.0) id e8ENcb107221; Fri, 15 Sep 2000 03:38:37 +0400 (MSD) (envelope-from ache) Date: Fri, 15 Sep 2000 03:38:37 +0400 From: "Andrey A. Chernov" To: imp@freebsd.org, current@freebsd.org, marcel@freebsd.org Subject: mtree again Message-ID: <20000915033837.A564@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any progress in mtree fixing process? I think there is acceptable solution, in following steps: 1) Return mtree defaults. 2) Add -L 3) Add ${MTREE_FOLLOW_LINKS} to mtree calls (which expands to nothing in old systems, so we not broke anything in the transition process) 4) Add MTREE_FOLLOW_LINKS = -L to /etc/defaults/make.conf -- 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 Thu Sep 14 16:42:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A4EF937B423; Thu, 14 Sep 2000 16:42:20 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA72583; Thu, 14 Sep 2000 17:42:19 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA00700; Thu, 14 Sep 2000 17:41:46 -0600 (MDT) Message-Id: <200009142341.RAA00700@harmony.village.org> To: "Andrey A. Chernov" Subject: Re: mtree again Cc: current@freebsd.org, marcel@freebsd.org In-reply-to: Your message of "Fri, 15 Sep 2000 03:38:37 +0400." <20000915033837.A564@nagual.pp.ru> References: <20000915033837.A564@nagual.pp.ru> Date: Thu, 14 Sep 2000 17:41:46 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000915033837.A564@nagual.pp.ru> "Andrey A. Chernov" writes: : Is there any progress in mtree fixing process? It hasn't been high on my list. I'd be happy to review patches, however. : I think there is acceptable solution, in following steps: : : 1) Return mtree defaults. : 2) Add -L : 3) Add ${MTREE_FOLLOW_LINKS} to mtree calls (which expands to nothing in : old systems, so we not broke anything in the transition process) : 4) Add : MTREE_FOLLOW_LINKS = -L : to /etc/defaults/make.conf This looks good to me. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 16:51: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4748C37B422 for ; Thu, 14 Sep 2000 16:50:58 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA72620 for ; Thu, 14 Sep 2000 17:50:57 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA00806 for ; Thu, 14 Sep 2000 17:50:24 -0600 (MDT) Message-Id: <200009142350.RAA00806@harmony.village.org> To: current@freebsd.org Subject: Question Date: Thu, 14 Sep 2000 17:50:24 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have two questions. Recently, I started seeing the message: module sn already present! when dhclient runs on my sn device. What causes this? Second, on both my sn card and my aue cards are installed I get: WARNING: Driver mistake: repeat make_dev("bpf0") What do these mean? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 17:20:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 6B66237B422 for ; Thu, 14 Sep 2000 17:20:26 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA00639; Thu, 14 Sep 2000 17:20:24 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009150020.RAA00639@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: current@freebsd.org Subject: Re: Question In-reply-to: Your message of "Thu, 14 Sep 2000 17:50:24 MDT." <200009142350.RAA00806@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 2000 17:20:24 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have two questions. Recently, I started seeing the message: > module sn already present! > when dhclient runs on my sn device. What causes this? It's caused by the 'sn' driver's module being called 'sn' rather than 'if_sn'. The code in ifconfig that tries to autoload modules for interfaces that aren't present yet decides that it needs to load the relevant module, but it collides on loading. It's a bug, but basically harmless. > Second, on both my sn card and my aue cards are installed I get: > WARNING: Driver mistake: repeat make_dev("bpf0") You'll have to ask Poul about this; I think it has something to do with moving devfs to /boot/devfs/devfs.ko. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 17:39:45 2000 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 D3C1B37B422; Thu, 14 Sep 2000 17:39:39 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e8F0dTc83754; Fri, 15 Sep 2000 04:39:29 +0400 (MSD) (envelope-from ache) Date: Fri, 15 Sep 2000 04:39:26 +0400 From: "Andrey A. Chernov" To: Warner Losh Cc: current@freebsd.org, marcel@freebsd.org Subject: Re: mtree again Message-ID: <20000915043925.A83698@nagual.pp.ru> References: <20000915033837.A564@nagual.pp.ru> <200009142341.RAA00700@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: <200009142341.RAA00700@harmony.village.org>; from imp@village.org on Thu, Sep 14, 2000 at 05:41:46PM -0600 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 14, 2000 at 05:41:46PM -0600, Warner Losh wrote: > In message <20000915033837.A564@nagual.pp.ru> "Andrey A. Chernov" writes: > : Is there any progress in mtree fixing process? > > It hasn't been high on my list. I'd be happy to review patches, > however. Here it is: --- usr.sbin/mtree/mtree.c.orig Thu Jul 27 07:36:02 2000 +++ usr.sbin/mtree/mtree.c Fri Sep 15 04:00:46 2000 @@ -57,7 +57,7 @@ extern long int crc_total; -int ftsoptions = FTS_LOGICAL; +int ftsoptions = FTS_PHYSICAL; int cflag, dflag, eflag, iflag, nflag, qflag, rflag, sflag, uflag, Uflag; u_int keys; char fullpath[MAXPATHLEN]; @@ -77,7 +77,7 @@ keys = KEYDEFAULT; init_excludes(); - while ((ch = getopt(argc, argv, "cdef:iK:k:np:Prs:UuxX:")) != -1) + while ((ch = getopt(argc, argv, "cdef:iK:k:Lnp:qrs:UuxX:")) != -1) switch((char)ch) { case 'c': cflag = 1; @@ -106,6 +106,10 @@ if (*p != '\0') keys |= parsekey(p, NULL); break; + case 'L': + ftsoptions &= ~FTS_PHYSICAL; + ftsoptions |= FTS_LOGICAL; + break; case 'n': nflag = 1; break; @@ -115,10 +119,6 @@ case 'q': qflag = 1; break; - case 'P': - ftsoptions ^= FTS_LOGICAL; - ftsoptions |= FTS_PHYSICAL; - break; case 'r': rflag = 1; break; @@ -170,7 +170,7 @@ usage() { (void)fprintf(stderr, -"usage: mtree [-PUcdeinqrux] [-f spec] [-K key] [-k key] [-p path] [-s seed]\n" +"usage: mtree [-LUcdeinqrux] [-f spec] [-K key] [-k key] [-p path] [-s seed]\n" "\t[-X excludes]\n"); exit(1); } --- usr.sbin/mtree/mtree.8.orig Thu Jul 27 07:36:02 2000 +++ usr.sbin/mtree/mtree.8 Fri Sep 15 04:03:07 2000 @@ -40,7 +40,7 @@ .Nd map a directory hierarchy .Sh SYNOPSIS .Nm mtree -.Op Fl PUcdeinqrux +.Op Fl LUcdeinqrux .Bk -words .Op Fl f Ar spec .Ek @@ -70,9 +70,10 @@ .Pp The options are as follows: .Bl -tag -width flag -.It Fl P -Don't follow symbolic links in the file hierarchy, instead consider -the symbolic link itself in any comparisons. +.It Fl L +Follow all symbolic links in the file hierarchy (by default +.Nm +considers the symbolic link itself). .It Fl U Modify the owner, group and permissions of existing files to match the specification and create any missing directories or symbolic links. --- etc/defaults/make.conf.orig Fri Sep 15 03:14:55 2000 +++ etc/defaults/make.conf Fri Sep 15 04:09:40 2000 @@ -43,6 +43,9 @@ # Compare before install #INSTALL=install -C # +# Mtree will follow symlinks +MTREE_FOLLOW_SYMLINKS= -L +# # To enable building enstalling suidperl with the setuid bit turned on #ENABLE_SUIDPERL= true # --- etc/Makefile.orig Sat Sep 9 02:56:53 2000 +++ etc/Makefile Fri Sep 15 04:06:36 2000 @@ -148,12 +148,12 @@ .endif distrib-dirs: - mtree -deU -f ${.CURDIR}/mtree/BSD.root.dist -p ${DESTDIR}/ - mtree -deU -f ${.CURDIR}/mtree/BSD.var.dist -p ${DESTDIR}/var - mtree -deU -f ${.CURDIR}/mtree/BSD.usr.dist -p ${DESTDIR}/usr - mtree -deU -f ${.CURDIR}/mtree/BSD.include.dist \ + mtree -deU ${MTREE_FOLLOW_SYMLINKS} -f ${.CURDIR}/mtree/BSD.root.dist -p ${DESTDIR}/ + mtree -deU ${MTREE_FOLLOW_SYMLINKS} -f ${.CURDIR}/mtree/BSD.var.dist -p ${DESTDIR}/var + mtree -deU ${MTREE_FOLLOW_SYMLINKS} -f ${.CURDIR}/mtree/BSD.usr.dist -p ${DESTDIR}/usr + mtree -deU ${MTREE_FOLLOW_SYMLINKS} -f ${.CURDIR}/mtree/BSD.include.dist \ -p ${DESTDIR}/usr/include - mtree -deU -f ${.CURDIR}/mtree/BSD.include.dist \ + mtree -deU ${MTREE_FOLLOW_SYMLINKS} -f ${.CURDIR}/mtree/BSD.include.dist \ -p ${DESTDIR}/usr/libdata/perl/5.6.0/mach cd ${DESTDIR}/; rm -f ${DESTDIR}/sys; ln -s usr/src/sys sys cd ${DESTDIR}/usr/share/locale; \ --- include/Makefile.orig Fri Sep 15 03:18:34 2000 +++ include/Makefile Fri Sep 15 04:12:10 2000 @@ -103,7 +103,7 @@ rm -f ${DESTDIR}/usr/include/$i; \ fi .endfor - mtree -deU -f ${.CURDIR}/../etc/mtree/BSD.include.dist \ + mtree -deU ${MTREE_FOLLOW_SYMLINKS} -f ${.CURDIR}/../etc/mtree/BSD.include.dist \ -p ${DESTDIR}/usr/include .for i in ${LDIRS} ${LSUBDIRS} cd ${.CURDIR}/../sys; \ -- 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 Thu Sep 14 17:59: 9 2000 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 D643937B424 for ; Thu, 14 Sep 2000 17:59:06 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA33974 for freebsd-current@freebsd.org; Thu, 14 Sep 2000 17:59:05 -0700 (PDT) (envelope-from obrien) Date: Thu, 14 Sep 2000 17:59:05 -0700 From: "David O'Brien" To: freebsd-current@freebsd.org Subject: Re: Please consider some cosmetic changes in boot messages Message-ID: <20000914175905.A33919@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <30404.968802455@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from kris@FreeBSD.org on Tue, Sep 12, 2000 at 06:28:05PM -0700 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 Tue, Sep 12, 2000 at 06:28:05PM -0700, Kris Kennaway wrote: > > I'm also not sure where the rumors about a FreeBSD 4.1.5 got started > > since I'd certainly never planned on such a thing, that, I think, 4.1.1 rather than 4.1.5 please. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 18: 4:34 2000 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 0ADB737B424 for ; Thu, 14 Sep 2000 18:04:31 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA34015; Thu, 14 Sep 2000 18:04:05 -0700 (PDT) (envelope-from obrien) Date: Thu, 14 Sep 2000 18:04:05 -0700 From: "David O'Brien" To: "Niels Chr. Bank-Pedersen" Cc: Sheldon Hearn , current@freebsd.org Subject: Re: Latest kernel/module restructuring Message-ID: <20000914180405.B33919@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200009121400.KAA48526@blackhelicopters.org> <97453.968767460@axl.fw.uunet.co.za> <20000912181120.C4519@bank-pedersen.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000912181120.C4519@bank-pedersen.dk>; from ncbp@bank-pedersen.dk on Tue, Sep 12, 2000 at 06:11:20PM +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 Tue, Sep 12, 2000 at 06:11:20PM +0200, Niels Chr. Bank-Pedersen wrote: > Hmm, how about those of us doing buildworlds/buildkernels on > one (nfs)server for subsequent installworlds/installkernels > on multiple other machines? Use the `make reinstall' target with KERNEL_KO set to the name of the kernel core filename you want. -- -- 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 Sep 14 21:42:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from cis.ohio-state.edu (mail.cis.ohio-state.edu [164.107.115.5]) by hub.freebsd.org (Postfix) with ESMTP id E341137B43C for ; Thu, 14 Sep 2000 21:42:17 -0700 (PDT) Received: from epsilon.cis.ohio-state.edu (matey@epsilon.cis.ohio-state.edu [164.107.112.10]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id AAA27382; Fri, 15 Sep 2000 00:42:14 -0400 (EDT) Received: (from matey@localhost) by epsilon.cis.ohio-state.edu (8.9.1/8.9.1) id AAA07248; Fri, 15 Sep 2000 00:42:13 -0400 (EDT) Date: Fri, 15 Sep 2000 00:42:05 -0400 From: Alexander Matey To: freebsd-current@FreeBSD.ORG Cc: "Viren R.Shah" , "Peter S. Housel" Subject: Re: problems with aureal soundcard: kernel fault when playing mp3s Message-ID: <20000915004205.A888@cis.ohio-state.edu> References: <14773.1013.154601.647909@jabberwock.rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from housel@acm.org on Tue, Sep 05, 2000 at 08:30:48AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 05, 2000 at 08:30:48AM -0700, Peter S. Housel wrote: > > [Alexander, I'm Cc:ing you on this just in case you have heard of > > anyone else having similar problems with Aureal cards with recent > > -currents] Sorry, I couldn't respond any earlier. I was out of business for a while. > > (http://www.cis.ohio-state.edu/~matey/au88x0/) so this might just be a > > problem with interactions between the linux .o files and kernel data > > structures. The soundcard worked fine using the linux drivers on a > > -current from August 14. I'm wondering if anything changed in the pcm > > code since then. That's what happened, as Peter noticed. > The pcm interfaces did change. The following patch fixes the au88x0 > driver for me. Thank you for the patch. I updated the stuff along with some documentation changes at http://www.cis.ohio-state.edu/~matey/au88x0/. > Cheers, > -Peter S. Housel- housel@acm.org http://members.home.com/housel/ -- lx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 22:10:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 8637F37B43C; Thu, 14 Sep 2000 22:10:16 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13Znt5-0000OC-00; Thu, 14 Sep 2000 23:18:11 -0600 Message-ID: <39C1B113.95D2B88B@softweyr.com> Date: Thu, 14 Sep 2000 23:18:11 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Thomas David Rivers , julian@elischer.org, nik@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: No block devices (was: VMWare on -current, how fast should I expect it to be?) References: <39BE38FC.41C67EA6@elischer.org> <200009121413.KAA51124@lakes.dignus.com> <20000913110306.D47700@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > FWIW, I was never happy with the removal of block devices either. I > was shouted down with "can you point to any one use they are?", to > which I replied "just because I don't know of one doesn't mean there > isn't one, or that there will never be one in the future". This is an > example where they could presumably be useful. Doesn't Oracle run MUCH better when given raw block disk devices to store data on? Could this have lead to some of the poor performance Mike Smith was seeing when testing this summer? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 22:46:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 40DAA37B422; Thu, 14 Sep 2000 22:46:41 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13ZoT8-0000PR-00; Thu, 14 Sep 2000 23:55:27 -0600 Message-ID: <39C1B9CE.F3FDF296@softweyr.com> Date: Thu, 14 Sep 2000 23:55:26 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: No block devices (was: VMWare on -current, how fast should I expect it to be?) References: <200009150524.WAA00506@mass.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 Mike Smith wrote: > > > > > Doesn't Oracle run MUCH better when given raw block disk devices to store > > data on? > > Oracle wants to cache it's own data, it doesn't want the buffer cache > behind it. Yes, now it's all coming back. It's amazing how much you can forget in the space of a decade. > > Could this have lead to some of the poor performance Mike Smith > > was seeing when testing this summer? > > No, we were layering over the filesystem, however filesystem load was > insignificant. The Oracle performance issues are well known, and this > isn't one of them. Thank you for clearing that up. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 23: 0:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 8FF0037B423 for ; Thu, 14 Sep 2000 23:00:50 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13ZoYA-0002KN-00; Fri, 15 Sep 2000 08:00:44 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e8F5xan02671; Fri, 15 Sep 2000 07:59:51 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009150559.e8F5xan02671@grimreaper.grondar.za> To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: SMPNG kernel on UP References: <200009141928.MAA85518@pike.osd.bsdi.com> In-Reply-To: <200009141928.MAA85518@pike.osd.bsdi.com> ; from John Baldwin "Thu, 14 Sep 2000 12:28:09 MST." Date: Fri, 15 Sep 2000 07:59:36 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : zzz/apm -z gives me "apm: ioctl(APMIO_SUSPEND): Invalid argument" > > > > I noticed this with the first SMPNG kernel I tried. The newer one > > this problem disappeared. Don't know why it would matter, but I may > > have missed a commit while in new mexico. > > It may be a kernel/world sync problem. Although I don't know why the ioctl > argument would suddenly become invalid. Maybe it passes in a struct ucred, > which changed in size just before the SMPng commit? Not a synchronization thing. I made sure of that. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 23: 1: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 84F5537B424 for ; Thu, 14 Sep 2000 23:01:02 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13ZoYQ-0002Kp-00; Fri, 15 Sep 2000 08:00:56 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e8F60Wn02692; Fri, 15 Sep 2000 08:00:33 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009150600.e8F60Wn02692@grimreaper.grondar.za> To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: SMPNG kernel on UP References: <200009141932.NAA98362@harmony.village.org> In-Reply-To: <200009141932.NAA98362@harmony.village.org> ; from Warner Losh "Thu, 14 Sep 2000 13:32:25 CST." Date: Fri, 15 Sep 2000 08:00:32 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't know either. However, it might be because of permission > problems. It will return EINVAL when it can't open the apm file for > write. Maybe a devfs related issue? I don't have devfs on this system yet. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 23: 2:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3388D37B43F for ; Thu, 14 Sep 2000 23:02:38 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA73748; Fri, 15 Sep 2000 00:02:36 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA03188; Fri, 15 Sep 2000 00:02:02 -0600 (MDT) Message-Id: <200009150602.AAA03188@harmony.village.org> To: Mark Murray Subject: Re: SMPNG kernel on UP Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 15 Sep 2000 08:00:32 +0200." <200009150600.e8F60Wn02692@grimreaper.grondar.za> References: <200009150600.e8F60Wn02692@grimreaper.grondar.za> <200009141932.NAA98362@harmony.village.org> Date: Fri, 15 Sep 2000 00:02:02 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009150600.e8F60Wn02692@grimreaper.grondar.za> Mark Murray writes: : > I don't know either. However, it might be because of permission : > problems. It will return EINVAL when it can't open the apm file for : > write. Maybe a devfs related issue? : : I don't have devfs on this system yet. Odd that. That's the only place that you can get the error you reported. what does ls -l /dev/apm say? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 23: 3: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 61C0C37B424 for ; Thu, 14 Sep 2000 23:02:56 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13ZoaA-0002MP-00; Fri, 15 Sep 2000 08:02:48 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e8F62Tn02712; Fri, 15 Sep 2000 08:02:29 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009150602.e8F62Tn02712@grimreaper.grondar.za> To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: SMPNG kernel on UP References: <200009141946.NAA98535@harmony.village.org> In-Reply-To: <200009141946.NAA98535@harmony.village.org> ; from Warner Losh "Thu, 14 Sep 2000 13:46:44 CST." Date: Fri, 15 Sep 2000 08:02:29 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : > I don't know either. However, it might be because of permission > : > problems. It will return EINVAL when it can't open the apm file for > : > write. Maybe a devfs related issue? > : > : Hmm, it may not be using the right perms during make_dev perhaps. > > Hmmm, they look good to me. Maybe Mark's system doesn't have group > operator at gid 5. That's one bad thing about the new DEVFS: it > appears to enshrine things like this in the kernel... Nope; no devfs, and the master.passwd is as close to standard as mergemaster can get. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 23:25:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 455EF37B422 for ; Thu, 14 Sep 2000 23:25:37 -0700 (PDT) Received: from vic.sabbo.net (root@[193.193.218.96]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id JAA25963 for ; Fri, 15 Sep 2000 09:25:28 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.0/8.9.3) with ESMTP id e8F6PSX06670 for ; Fri, 15 Sep 2000 09:25:28 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <39C1C0D1.C9F220EB@FreeBSD.org> Date: Fri, 15 Sep 2000 09:25:22 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@FreeBSD.org Subject: diff(1) is broken Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some time ago somebody tried to fix "\ No newline at end of file" bug in diff and seems that he had not reached the target - the diff is still broked, however in a slightly different way (tested both with 4-stable and 5-current). See: http://people.freebsd.org/~sobomax/config.h.orig http://people.freebsd.org/~sobomax/config.h http://people.freebsd.org/~sobomax/config.h.diff (look at the last line!) The latter file is result of "diff -du config.h.orig config.h" -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 14 23:44:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 1421337B422 for ; Thu, 14 Sep 2000 23:44:30 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13ZpEY-0003oN-00; Fri, 15 Sep 2000 08:44:27 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e8F6i3n03386; Fri, 15 Sep 2000 08:44:22 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009150644.e8F6i3n03386@grimreaper.grondar.za> To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: SMPNG kernel on UP References: <200009150602.AAA03188@harmony.village.org> In-Reply-To: <200009150602.AAA03188@harmony.village.org> ; from Warner Losh "Fri, 15 Sep 2000 00:02:02 CST." Date: Fri, 15 Sep 2000 08:44:03 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200009150600.e8F60Wn02692@grimreaper.grondar.za> Mark Murray writ es: > : > I don't know either. However, it might be because of permission > : > problems. It will return EINVAL when it can't open the apm file for > : > write. Maybe a devfs related issue? > : > : I don't have devfs on this system yet. > > Odd that. That's the only place that you can get the error you > reported. what does ls -l /dev/apm say? [grimreaper] ~ $ ls -al /dev/apm crw-rw-r-- 1 root operator 39, 0 Sep 14 20:03 /dev/apm (And yes, I try to suspend as root, not as a pleb). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 2: 2:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-04-real.cdsnet.net (mail-04-real.cdsnet.net [63.163.68.109]) by hub.freebsd.org (Postfix) with SMTP id 6FEDB37B42C for ; Fri, 15 Sep 2000 02:02:11 -0700 (PDT) Received: (qmail 45612 invoked from network); 15 Sep 2000 09:02:03 -0000 Received: from apocalypse.cdsnet.net (63.163.68.5) by mail-04-real.cdsnet.net with SMTP; 15 Sep 2000 09:02:03 -0000 Date: Fri, 15 Sep 2000 02:02:03 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@apocalypse.cdsnet.net To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: looking for "microuptime went backwards" victims... In-Reply-To: <53059.968085674@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 I get it on my newsserver pretty much every night when expire runs. 12 IDE drives on 3 Promise controllers. I was just actually about to replace the MB, thinking it was just something freaky or unstable. I will try the patch. On Mon, 4 Sep 2000, Poul-Henning Kamp wrote: > > I'm looking for the remaining victims of the dreaded "microuptime > went backwards" message. > > If you can reliably reproduce the problem, please contact me, so > we can arrange for some very detailed tracing to try to find out > what exactly is going on. I have not been able to trigger the > problem in my lab in a long time. > > If you see the message only occationally, please try the attached > patch and let me know if this changes the picture. The patch is > not meant as a fix, but it might reduce the impact of this condition > considerably when it happens. Basically by reducing the width of > the timecounter the magnitude of the hit we take if the timecounter > goes backwards is reduced from about an hour to approx 110msec. > > Reducing the width to less than 17 bits starts to run the risk of > ambiguity due to clock rollover. > > This patch may not be safe with PCAUDIO. > > Poul-Henning > > Index: clock.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v > retrieving revision 1.155 > diff -u -r1.155 clock.c > --- clock.c 2000/07/30 21:05:22 1.155 > +++ clock.c 2000/09/04 16:34:16 > @@ -194,7 +194,7 @@ > static struct timecounter i8254_timecounter = { > i8254_get_timecount, /* get_timecount */ > 0, /* no poll_pps */ > - ~0u, /* counter_mask */ > + 0x1ffff, /* counter_mask */ > 0, /* frequency */ > "i8254" /* name */ > }; > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 4: 4:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163]) by hub.freebsd.org (Postfix) with ESMTP id 5007E37B423; Fri, 15 Sep 2000 04:04:22 -0700 (PDT) Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226]) by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id NAA17993; Fri, 15 Sep 2000 13:03:44 +0200 (MET DST) Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56]) by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id NAA07958; Fri, 15 Sep 2000 13:03:29 +0200 (MET DST) Received: by MCHH246E with Internet Mail Service (5.5.2650.21) id ; Fri, 15 Sep 2000 13:04:05 +0200 Message-ID: <67E0BE167008D31185F60008C7289DA0E12F0B@MCHH218E> From: Reifenberger Michael To: "'freebsd-current@FreeBSD.ORG'" , "'freebsd-smp@freebsd.org'" Subject: Partial success with current on Laptop. Date: Fri, 15 Sep 2000 12:03:36 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, with -current as of yesterday I get partial success. My configuration: - Tecra8000 - 256MB Ram - ad0: IBM DARA 25000 @ UDMA33 - ad1: IBM DARA 26480 @ UDMA33 - kernel and modules in sync, fresh buildworld, buildkernel... - Nonstandart-options: o enabled apm, acpi, usb, pcm, pcic. o all slices are mounted with noatime and sofdep. o sysctl -w vfs.vmiodirenable=1 o sysctl -w vfs.write_behind=0 o kern.vm.kmem.size=20971520 in loader.conf What seems to work: - buildkernel; (buildworld not testet) - linuxerator (testet staroffice, Oracle 8.1.5, SAP R/3 4.5B) - X - Wine - pcmcia (ep0, aic0 - insert/delete testet) - apm (suspend/resume not testet) What doesn't - Heavy (concurrent?) disk I/O locks up the system solid. Testet with "du -sk /usr/ports" or "tar cf - . | `cd /scratch; tar xvf -`" in multiuser mode... "tar cf /dev/null /usr/ports &; tar cf - /usr/ports | tar tvf -" in singleuser mode (disks mounted -oro ) o getting (after hanging with "du -sk /usr/ports" into ddb -> ps shows some processes in ffsvgt and du hanging in some FFS operation. o in singleuser mode -> ddb -> ps I see the 3 tar's in stat: 3, wmesg: piperd, inode, FFS node. - "panic" in ddb hangs in "syncing disks x x ...". Bye/2 ------ Michael Reifenberger - IT, UNIX, R/3-Basis Work: Michael.Reifenberger@plaut.de Proj: Michael.Reifenberger.gp@icn.siemens.de Pers: Michael@Reifenberger.com Webspace: http://www.reifenberger.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 4:55:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id BA00B37B422 for ; Fri, 15 Sep 2000 04:55:52 -0700 (PDT) Received: from yoko.hsc.fr (yoko.hsc.fr [192.70.106.76]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "yoko.hsc.fr", Issuer CN "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id B9F4A10ED1 for ; Fri, 15 Sep 2000 13:55:51 +0200 (CEST) Received: by yoko.hsc.fr (Postfix-TLS, from userid 1001) id D713F9B208; Fri, 15 Sep 2000 13:55:48 +0200 (CEST) Date: Fri, 15 Sep 2000 13:55:48 +0200 From: Alain Thivillon To: freebsd-current@freebsd.org Subject: DevFs status and security ? Message-ID: <20000915135548.A436@yoko.hsc.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i X-Organization: Herve Schauer Consultants X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is a huge security hole in -CURRENT devfs, i don't known if this is a temporary issue or a 'real' bug: $ id uid=2089(yann) gid=2089(yann) groups=2089(yann) $ uname -a FreeBSD yoko.hsc.fr 5.0-CURRENT FreeBSD 5.0-CURRENT #57: Fri Sep 15 13:36:26 CEST 2000 titi@yoko.hsc.fr:/usr/src/sys/compile/YOKO50 i386 $ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s3a 6252604 5027631 724765 87% / devfs 1 1 0 100% /dev procfs 4 4 0 100% /proc $ ls -l /dev/null crw-rw-rw- 1 root wheel 2, 2 Sep 15 13:47 /dev/null $ chown yann /dev/null $ chown yann /dev/mem $ ls -l /dev/null crw-rw-rw- 1 yann wheel 2, 2 Sep 15 13:47 /dev/null $ chmod 600 /dev/null $ ls -l /dev/null crw------- 1 yann wheel 2, 2 Sep 15 13:47 /dev/null $ strings /dev/mem | head -10 Read Boot error (TKT ( CT (@;T ((0S (,/S (l-S (d/S Every user can change all owners and perms on devfs files. I have verified that /dev/null permissions are REALLY changed (other users can not use him) and that Mem can REALLY be read by anyone. Did i miss something ? Strange that nobody reported it (my problems appeeared when procmail changed perms of /dev/null :)) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 5:10:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id 9916937B424; Fri, 15 Sep 2000 05:10:53 -0700 (PDT) Received: from yoko.hsc.fr (yoko.hsc.fr [192.70.106.76]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "yoko.hsc.fr", Issuer CN "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id BFC9510ED1; Fri, 15 Sep 2000 14:10:52 +0200 (CEST) Received: by yoko.hsc.fr (Postfix-TLS, from userid 1001) id BA18C9B206; Fri, 15 Sep 2000 14:10:49 +0200 (CEST) Date: Fri, 15 Sep 2000 14:10:49 +0200 From: Alain Thivillon To: Reifenberger Michael Cc: "'freebsd-current@FreeBSD.ORG'" , "'freebsd-smp@freebsd.org'" Subject: Re: Partial success with current on Laptop. Message-ID: <20000915141049.A695@yoko.hsc.fr> References: <67E0BE167008D31185F60008C7289DA0E12F0B@MCHH218E> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.2i In-Reply-To: <67E0BE167008D31185F60008C7289DA0E12F0B@MCHH218E>; from Michael.Reifenberger.gp@icn.siemens.de on Fri, Sep 15, 2000 at 12:03:36PM +0200 X-Organization: Herve Schauer Consultants X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Reifenberger Michael écrivait (wrote) : > My configuration: > - Tecra8000 I run the same, with only 64Mo. > - 256MB Ram > - ad0: IBM DARA 25000 @ UDMA33 > - ad1: IBM DARA 26480 @ UDMA33 I have only one disk, in DMA, with softupdates. I have tried some of the stress tests you mention, and ... no crashes. > - apm (suspend/resume not testet) Works for me. My only problem is that Fan is NEVER turned off (it seems that idle loop in kernel as become CPU intensive and energy hardware can not stop cooling). At this time, this is a minor annoyance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 5:13: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 2B12937B422 for ; Fri, 15 Sep 2000 05:12:58 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8FCCmN62839; Fri, 15 Sep 2000 14:12:48 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alain Thivillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: DevFs status and security ? In-Reply-To: Your message of "Fri, 15 Sep 2000 13:55:48 +0200." <20000915135548.A436@yoko.hsc.fr> Date: Fri, 15 Sep 2000 14:12:48 +0200 Message-ID: <62837.969019968@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks like I forgot an access check in DEVFS. I'll look at it tonight. Poul-Henning In message <20000915135548.A436@yoko.hsc.fr>, Alain Thivillon writes: >There is a huge security hole in -CURRENT devfs, i don't known if this >is a temporary issue or a 'real' bug: > >$ id >uid=2089(yann) gid=2089(yann) groups=2089(yann) >$ uname -a >FreeBSD yoko.hsc.fr 5.0-CURRENT FreeBSD 5.0-CURRENT #57: Fri Sep 15 >13:36:26 CEST 2000 titi@yoko.hsc.fr:/usr/src/sys/compile/YOKO50 >i386 >$ df >Filesystem 1K-blocks Used Avail Capacity Mounted on >/dev/ad0s3a 6252604 5027631 724765 87% / >devfs 1 1 0 100% /dev >procfs 4 4 0 100% /proc >$ ls -l /dev/null >crw-rw-rw- 1 root wheel 2, 2 Sep 15 13:47 /dev/null >$ chown yann /dev/null >$ chown yann /dev/mem >$ ls -l /dev/null >crw-rw-rw- 1 yann wheel 2, 2 Sep 15 13:47 /dev/null >$ chmod 600 /dev/null >$ ls -l /dev/null >crw------- 1 yann wheel 2, 2 Sep 15 13:47 /dev/null >$ strings /dev/mem | head -10 >Read >Boot > error >(TKT >( CT >(@;T >((0S >(,/S >(l-S >(d/S > > Every user can change all owners and perms on devfs files. I >have verified that /dev/null permissions are REALLY changed (other users >can not use him) and that Mem can REALLY be read by anyone. > > Did i miss something ? Strange that nobody reported it (my >problems appeeared when procmail changed perms of /dev/null :)) > > > >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 coreteam member | 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 Sep 15 7: 8:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18]) by hub.freebsd.org (Postfix) with ESMTP id 1F79737B423; Fri, 15 Sep 2000 07:08:47 -0700 (PDT) Received: from blues.mchh.siemens.de (mail3.mchh.siemens.de [194.138.158.227] (may be forged)) by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id QAA17224; Fri, 15 Sep 2000 16:08:27 +0200 (MET DST) Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56]) by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id QAA02703; Fri, 15 Sep 2000 16:05:14 +0200 (MET DST) Received: by MCHH246E with Internet Mail Service (5.5.2650.21) id ; Fri, 15 Sep 2000 16:08:39 +0200 Message-ID: <67E0BE167008D31185F60008C7289DA0E12F0D@MCHH218E> From: Reifenberger Michael To: "'Alain Thivillon'" Cc: "'freebsd-current@FreeBSD.ORG'" , "'freebsd-smp@freebsd.org'" Subject: AW: Partial success with current on Laptop. Date: Fri, 15 Sep 2000 15:25:38 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) 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 Hi, sorry, it's easilly reproducable. I built a -current kernel supped today now without apm, acpi, usb. - "boot -s" for singleuser - "mount -oro /usr" - "cd /usr/ports" - "tar cf /dev/null . &" - "tar cf - . | tar tvf -" ...wait... ...freeze... ...why?... Could someone enlight me how to get some more usefull information after = getting into ddb? ddb(4) and the handbook is not really specific about. Esp. how do I inspect specific processes which I see in "ps". "trace" is of no help when manually breaking into ddb. Is there something like "bt" or "up", like in gdb? Bye/2 ------ Michael Reifenberger - IT, UNIX, R/3-Basis Work: Michael.Reifenberger@plaut.de Proj: = Michael.Reifenberger.gp@icn.siemens.de Pers: Michael@Reifenberger.com Webspace: http://www.reifenberger.com > -----Urspr> =FCngliche Nachricht----- > Von: Alain Thivillon [SMTP:Alain.Thivillon@hsc.fr] > Gesendet am: Freitag, 15. September 2000 14:11 > An: Reifenberger Michael > Cc: 'freebsd-current@FreeBSD.ORG'; 'freebsd-smp@freebsd.org' > Betreff: Re: Partial success with current on Laptop. >=20 > Reifenberger Michael = =E9crivait (wrote) : >=20 > > My configuration: > > - Tecra8000 >=20 > I run the same, with only 64Mo. >=20 > > - 256MB Ram > > - ad0: IBM DARA 25000 @ UDMA33 > > - ad1: IBM DARA 26480 @ UDMA33 >=20 > I have only one disk, in DMA, with softupdates. I have tried > some of the stress tests you mention, and ... no crashes. >=20 > > - apm (suspend/resume not testet) >=20 > Works for me. >=20 > My only problem is that Fan is NEVER turned off (it seems that > idle loop in kernel as become CPU intensive and energy hardware can = not > stop cooling). At this time, this is a minor annoyance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 7:26:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from exchange.stratasys.com (mail.mn.stratasys.com [204.220.37.1]) by hub.freebsd.org (Postfix) with ESMTP id 6F8BD37B42C for ; Fri, 15 Sep 2000 07:26:23 -0700 (PDT) Received: by exchange.stratasys.com with Internet Mail Service (5.5.2650.21) id ; Fri, 15 Sep 2000 09:16:28 -0500 Received: from drosophila.stratasys.com (192.168.10.174 [192.168.10.174]) by exchange.stratasys.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id SXAABQWA; Fri, 15 Sep 2000 09:16:19 -0500 From: "Adkins, Dave" To: freebsd-current@freebsd.org Date: Fri, 15 Sep 2000 09:26:03 -0500 (CDT) Subject: boot failing early since SMPng Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY="0-1150707844-968935033=:336" Content-ID: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1150707844-968935033=:336 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Kernels after the SMPng commit have failed to boot for me. The pc is an old TYAN S1563D with a pair of p200's. I have tracked it down to entering vm86_intcall() in getmemsize(). It enters but doesn't return. I haven't seen any similar problems on the lists. I've tried building a UP kernel too, same result. Dies in the vm86_intcall(). Build optimization is the default -O. dmesg from a Sept 6 kernel, prior to the SMPng commit is attached. dave adkins --0-1150707844-968935033=:336 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="dm.log" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="dm.log" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4NCkNvcHlyaWdodCAo YykgMTk3OSwgMTk4MCwgMTk4MywgMTk4NiwgMTk4OCwgMTk4OSwgMTk5MSwgMTk5MiwgMTk5Mywg MTk5NA0KCVRoZSBSZWdlbnRzIG9mIHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuIEFsbCBy aWdodHMgcmVzZXJ2ZWQuDQpGcmVlQlNEIDUuMC1DVVJSRU5UICMxMDA6IFdlZCBTZXAgIDYgMDc6 NTM6NTMgQ0RUIDIwMDANCiAgICBkYXZlQHNhbXRoZWRvZzovdXNyNC9zcmMvc3lzL2NvbXBpbGUv REFWRVMNClRpbWVjb3VudGVyICJpODI1NCIgIGZyZXF1ZW5jeSAxMTkzMDU2IEh6DQpDUFU6IFBl bnRpdW0vUDU0QyAoMTk5LjQxLU1IeiA1ODYtY2xhc3MgQ1BVKQ0KICBPcmlnaW4gPSAiR2VudWlu ZUludGVsIiAgSWQgPSAweDUyYyAgU3RlcHBpbmcgPSAxMg0KICBGZWF0dXJlcz0weDNiZjxGUFUs Vk1FLERFLFBTRSxUU0MsTVNSLE1DRSxDWDgsQVBJQz4NCnJlYWwgbWVtb3J5ICA9IDEwMDY2MzI5 NiAoOTgzMDRLIGJ5dGVzKQ0KYXZhaWwgbWVtb3J5ID0gOTQwMTU0ODggKDkxODEySyBieXRlcykN ClByb2dyYW1taW5nIDI0IHBpbnMgaW4gSU9BUElDICMwDQpJT0FQSUMgIzAgaW50cGluIDIgLT4g aXJxIDANCkZyZWVCU0QvU01QOiBNdWx0aXByb2Nlc3NvciBtb3RoZXJib2FyZA0KIGNwdTAgKEJT UCk6IGFwaWMgaWQ6ICAwLCB2ZXJzaW9uOiAweDAwMDMwMDEwLCBhdCAweGZlZTAwMDAwDQogY3B1 MSAoQVApOiAgYXBpYyBpZDogIDEsIHZlcnNpb246IDB4MDAwMzAwMTAsIGF0IDB4ZmVlMDAwMDAN CiBpbzAgKEFQSUMpOiBhcGljIGlkOiAgMiwgdmVyc2lvbjogMHgwMDE3MDAxMSwgYXQgMHhmZWMw MDAwMA0KUHJlbG9hZGVkIGVsZiBrZXJuZWwgImtlcm5lbCIgYXQgMHhjMDNjMDAwMC4NClByZWxv YWRlZCBlbGYgbW9kdWxlICJuZnMua28iIGF0IDB4YzAzYzAwOWMuDQpQcmVsb2FkZWQgZWxmIG1v ZHVsZSAibGludXgua28iIGF0IDB4YzAzYzAxMzguDQpJbnRlbCBQZW50aXVtIGRldGVjdGVkLCBp bnN0YWxsaW5nIHdvcmthcm91bmQgZm9yIEYwMEYgYnVnDQpzdHJheSBpcnEgNw0KVkVTQTogdjIu MCwgODE5MmsgbWVtb3J5LCBmbGFnczoweDEsIG1vZGUgdGFibGU6MHhjMDJmM2FlMiAoMTAwMDAy MikNClZFU0E6IE1hdHJveCBHcmFwaGljcyBJbmMuDQpucHgwOiA8bWF0aCBwcm9jZXNzb3I+IG9u IG1vdGhlcmJvYXJkDQpucHgwOiBJTlQgMTYgaW50ZXJmYWNlDQpwY2liMDogPEhvc3QgdG8gUENJ IGJyaWRnZT4gb24gbW90aGVyYm9hcmQNCnBjaTA6IDxQQ0kgYnVzPiBvbiBwY2liMA0KaXNhYjA6 IDxJbnRlbCA4MjM3MVNCIFBDSSB0byBJU0EgYnJpZGdlPiBhdCBkZXZpY2UgNy4wIG9uIHBjaTAN CmlzYTA6IDxJU0EgYnVzPiBvbiBpc2FiMA0KYXRhcGNpMDogPEludGVsIFBJSVgzIEFUQSBjb250 cm9sbGVyPiBwb3J0IDB4ZjAwMC0weGYwMGYgYXQgZGV2aWNlIDcuMSBvbiBwY2kwDQphdGEwOiBh dCAweDFmMCBpcnEgMTQgb24gYXRhcGNpMA0KYXRhMTogYXQgMHgxNzAgaXJxIDE1IG9uIGF0YXBj aTANCnBjaTA6IDxNYXRyb3ggTUdBIE1pbGxlbm5pdW0gMjA2NFcgZ3JhcGhpY3MgYWNjZWxlcmF0 b3I+IGF0IDE3LjAgaXJxIDE5DQphaGMwOiA8QWRhcHRlYyAyOTQwIFVsdHJhIFNDU0kgYWRhcHRl cj4gcG9ydCAweDYwMDAtMHg2MGZmIG1lbSAweGUwODA0MDAwLTB4ZTA4MDRmZmYgaXJxIDE4IGF0 IGRldmljZSAxOC4wIG9uIHBjaTANCmFoYzA6IGFpYzc4ODAgV2lkZSBDaGFubmVsIEEsIFNDU0kg SWQ9NywgMTYvMjU1IFNDQnMNCmRlMDogPERpZ2l0YWwgMjExNDBBIEZhc3QgRXRoZXJuZXQ+IHBv cnQgMHg2NTAwLTB4NjU3ZiBtZW0gMHhlMDgwNTAwMC0weGUwODA1MDdmIGlycSAxNyBhdCBkZXZp Y2UgMTkuMCBvbiBwY2kwDQpkZTA6IENvZ2VudCBFTTEwMEZYIDIxMTQwQSBbMTAtMTAwTWIvc10g cGFzcyAyLjINCmRlMDogYWRkcmVzcyAwMDowMDo5Mjo5NzozYTo1ZA0KZGUwOiBlbmFibGluZyAx MDBiYXNlRlggcG9ydA0KZmRjMDogPE5FQyA3MjA2NUIgb3IgY2xvbmU+IGF0IHBvcnQgMHgzZjAt MHgzZjUsMHgzZjcgaXJxIDYgZHJxIDIgb24gaXNhMA0KZmRjMDogRklGTyBlbmFibGVkLCA4IGJ5 dGVzIHRocmVzaG9sZA0KZmQwOiA8MTQ0MC1LQiAzLjUiIGRyaXZlPiBvbiBmZGMwIGRyaXZlIDAN CmF0a2JkYzA6IDxLZXlib2FyZCBjb250cm9sbGVyIChpODA0Mik+IGF0IHBvcnQgMHg2MCwweDY0 IG9uIGlzYTANCmF0a2JkMDogPEFUIEtleWJvYXJkPiBmbGFncyAweDEgaXJxIDEgb24gYXRrYmRj MA0KdmdhMDogPEdlbmVyaWMgSVNBIFZHQT4gYXQgcG9ydCAweDNjMC0weDNkZiBpb21lbSAweGEw MDAwLTB4YmZmZmYgb24gaXNhMA0Kc2MwOiA8U3lzdGVtIGNvbnNvbGU+IGF0IGZsYWdzIDB4MTAw IG9uIGlzYTANCnNjMDogVkdBIDwxNiB2aXJ0dWFsIGNvbnNvbGVzLCBmbGFncz0weDMwMD4NCnNp bzAgYXQgcG9ydCAweDNmOC0weDNmZiBpcnEgNCBmbGFncyAweDEwMDAwMDAwIG9uIGlzYTANCnNp bzA6IHR5cGUgMTY1NTBBIGxvb2thbGlrZSB3aXRoIDE2IGJ5dGVzIEZJRk8NCnNpbzEgYXQgcG9y dCAweDJmOC0weDJmZiBpcnEgMyBmbGFncyAweDEwMDAwMDAwIG9uIGlzYTANCnNpbzE6IHR5cGUg MTY1NTBBIGxvb2thbGlrZSB3aXRoIDE2IGJ5dGVzIEZJRk8NCnBwYzA6IDxQYXJhbGxlbCBwb3J0 PiBhdCBwb3J0IDB4Mzc4LTB4MzdmIGlycSA3IG9uIGlzYTANCnBwYzA6IFNNQy1saWtlIGNoaXBz ZXQgKEVDUC9FUFAvUFMyL05JQkJMRSkgaW4gQ09NUEFUSUJMRSBtb2RlDQpwcGMwOiBGSUZPIHdp dGggMTYvMTYvMTUgYnl0ZXMgdGhyZXNob2xkDQpscHQwOiA8UHJpbnRlcj4gb24gcHBidXMwDQps cHQwOiBJbnRlcnJ1cHQtZHJpdmVuIHBvcnQNCnBwaTA6IDxQYXJhbGxlbCBJL08+IG9uIHBwYnVz MA0KdnBvMDogPElvbWVnYSBWUEkwIFBhcmFsbGVsIHRvIFNDU0kgaW50ZXJmYWNlPiBvbiBwcGJ1 czANCnZwbzA6IEVQUCAxLjkgbW9kZQ0Kc2JjMDogPFNvdW5kYmxhc3RlciAxNj4gYXQgcG9ydCAw eDI2MC0weDI2ZiBpcnEgNSBkcnEgMyBvbiBpc2EwDQpzYmMwOiBzZXR0aW5nIGNhcmQgdG8gaXJx IDUsIGRycSAzDQpwY20wOiA8U0IgRFNQIDQuMTE+IG9uIHNiYzANCnVua25vd246IDxQTlAwMzAz PiBjYW4ndCBhc3NpZ24gcmVzb3VyY2VzDQphdHNwZWFrZXIwOiA8QVQgc3BlYWtlcj4gYXQgcG9y dCAweDYxIG9uIGlzYTANCnVua25vd246IDxQTlAwNTAxPiBjYW4ndCBhc3NpZ24gcmVzb3VyY2Vz DQp1bmtub3duOiA8UE5QMDcwMD4gY2FuJ3QgYXNzaWduIHJlc291cmNlcw0KdW5rbm93bjogPFBO UDA0MDE+IGNhbid0IGFzc2lnbiByZXNvdXJjZXMNCnVua25vd246IDxQTlAwNTAxPiBjYW4ndCBh c3NpZ24gcmVzb3VyY2VzDQpBUElDX0lPOiBUZXN0aW5nIDgyNTQgaW50ZXJydXB0IGRlbGl2ZXJ5 DQpBUElDX0lPOiByb3V0aW5nIDgyNTQgdmlhIElPQVBJQyAjMCBpbnRwaW4gMg0KU01QOiBBUCBD UFUgIzEgTGF1bmNoZWQhDQphZDA6IDEwMzNNQiA8U1QzMTIyMEE+IFsyMDk5LzE2LzYzXSBhdCBh dGEwLW1hc3RlciB1c2luZyBXRE1BMg0KYWQxOiAxOTUzMU1CIDxNYXh0b3IgOTIwNDhVOD4gWzM5 NjgzLzE2LzYzXSBhdCBhdGEwLXNsYXZlIHVzaW5nIFdETUEyDQphZDI6IDIwMTVNQiA8Q29ubmVy IFBlcmlwaGVyYWxzIDIxMTNNQiAtIENGQTIxNjFBPiBbNDA5NS8xNi82M10gYXQgYXRhMS1tYXN0 ZXIgdXNpbmcgV0RNQTINCldhaXRpbmcgMiBzZWNvbmRzIGZvciBTQ1NJIGRldmljZXMgdG8gc2V0 dGxlDQpkYTAgYXQgYWhjMCBidXMgMCB0YXJnZXQgMCBsdW4gMA0KZGEwOiA8U0VBR0FURSBTVDMy NTUwTiAwMDIxPiBGaXhlZCBEaXJlY3QgQWNjZXNzIFNDU0ktMiBkZXZpY2UgDQpkYTA6IDEwLjAw ME1CL3MgdHJhbnNmZXJzICgxMC4wMDBNSHosIG9mZnNldCAxNSkNCmRhMDogMjA0N01CICg0MTk0 MDU4IDUxMiBieXRlIHNlY3RvcnM6IDI1NUggNjNTL1QgMjYxQykNCmRhMSBhdCBhaGMwIGJ1cyAw IHRhcmdldCAxIGx1biAwDQpkYTE6IDxTRUFHQVRFIFNUMzI1NTBOIDAwMjE+IEZpeGVkIERpcmVj dCBBY2Nlc3MgU0NTSS0yIGRldmljZSANCmRhMTogMTAuMDAwTUIvcyB0cmFuc2ZlcnMgKDEwLjAw ME1Ieiwgb2Zmc2V0IDE1KQ0KZGExOiAyMDQ3TUIgKDQxOTQwNTggNTEyIGJ5dGUgc2VjdG9yczog MjU1SCA2M1MvVCAyNjFDKQ0KZGEyIGF0IHZwbzAgYnVzIDAgdGFyZ2V0IDYgbHVuIDANCmRhMjog PElPTUVHQSBaSVAgMTAwIEQuMDk+IFJlbW92YWJsZSBEaXJlY3QgQWNjZXNzIFNDU0ktMiBkZXZp Y2UgDQpkYTI6IEF0dGVtcHQgdG8gcXVlcnkgZGV2aWNlIHNpemUgZmFpbGVkOiBOT1QgUkVBRFks IE1lZGl1bSBub3QgcHJlc2VudA0KTW91bnRpbmcgcm9vdCBmcm9tIHVmczovZGV2L2FkMnMxYQ0K --0-1150707844-968935033=:336-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 7:33:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from goliath.siemens.de (goliath2.siemens.de [192.35.17.28]) by hub.freebsd.org (Postfix) with ESMTP id AA9A937B424 for ; Fri, 15 Sep 2000 07:33:50 -0700 (PDT) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer goliath.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e8FEXj312709 for ; Fri, 15 Sep 2000 16:33:49 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail2.siemens.de (8.10.1/8.10.1) with ESMTP id e8FEXi522819 for ; Fri, 15 Sep 2000 16:33:44 +0200 (MET DST) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.11.0/8.11.0/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id e8FEXim88890 for ; Fri, 15 Sep 2000 16:33:44 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.11.0/8.11.0/alaska [ $Revision: 1.4 ]) id e8FEXi479571 for freebsd-current@FreeBSD.ORG; Fri, 15 Sep 2000 14:33:44 GMT (envelope-from ust) Date: Fri, 15 Sep 2000 16:33:44 +0200 From: Udo Schweigert To: freebsd-current@FreeBSD.ORG Subject: ssh and scp fail connecting to a root account Message-ID: <20000915163344.A79462@alaska.cert.siemens.de> Mail-Followup-To: freebsd-current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, after a fresh build of -current openssh does not work if connecting to the root-user. For example (tested from a -stable machine, but the same from 4.1-RELEASE): ------------------------------------------------------------------------------- $ ssh -l root Last login: Fri Sep 15 16:22:48 2000 from xxxx Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT (yyyy) #21: Fri Sep 15 11:59:41 CEST 2000 Welcome to FreeBSD! sshd in realloc(): error: junk pointer, too high to make sense. Connection to zzzz closed. ------------------------------------------------------------------------------- (This implies that "PermitRootLogin" is set to yes in /etc/ssh/sshd_config) The only soultion is to have "UseLogin" set to yes. But nevertheless scp does never work if copying to the root account like this: ------------------------------------------------------------------------------- $ scp root@:. select: Bad file descriptor lost connection ------------------------------------------------------------------------------- The strange: both commands succeed if connecting to a non-root account. Are there any others with these problems? Any clues? Best regards. -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : ust@cert.siemens.de PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 7:40:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from alpha.dante.org.uk (alpha.dante.org.uk [193.63.211.19]) by hub.freebsd.org (Postfix) with ESMTP id E677137B424 for ; Fri, 15 Sep 2000 07:40:20 -0700 (PDT) Received: from theta.dante.org.uk ([193.63.211.7]) by alpha.dante.org.uk with esmtp (Exim 3.12 #4) id 13Zwf4-0005l6-00; Fri, 15 Sep 2000 15:40:18 +0100 Received: from localhost ([127.0.0.1] helo=dante.org.uk) by theta.dante.org.uk with esmtp (Exim 3.12 #4) id 13Zwey-0000LO-00; Fri, 15 Sep 2000 15:40:12 +0100 Message-ID: <39C234CC.668195B@dante.org.uk> Date: Fri, 15 Sep 2000 15:40:12 +0100 From: Konstantin Chuguev Organization: Delivery of Advanced Networking Service to Europe Ltd. X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en, ru MIME-Version: 1.0 To: Udo Schweigert Cc: freebsd-current@FreeBSD.ORG Subject: Re: ssh and scp fail connecting to a root account References: <20000915163344.A79462@alaska.cert.siemens.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Udo Schweigert wrote: > Hello all, > > after a fresh build of -current openssh does not work if connecting to the > root-user. For example (tested from a -stable machine, but the same from > 4.1-RELEASE): > > ------------------------------------------------------------------------------- > ------------------------------------------------------------------------------- > > The strange: both commands succeed if connecting to a non-root account. > > Are there any others with these problems? Any clues? > Yes, I've been seeing the same thing since the checkout of the SMPng stuff... No idea why it's happening. -- * * Konstantin Chuguev - Application Engineer * * Francis House, 112 Hills Road * Cambridge CB2 1PQ, United Kingdom D A N T E WWW: http://www.dante.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 8:11:39 2000 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 DFDD037B424 for ; Fri, 15 Sep 2000 08:11:30 -0700 (PDT) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id IAA30280; Fri, 15 Sep 2000 08:11:24 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39C23C1B.6B925D4E@gorean.org> Date: Fri, 15 Sep 2000 08:11:23 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT-071 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Cc: Mitja Horvat Subject: [Fwd: Re: panic: kmem_malloc(-1077936128): kmem_map too small] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Excellent detective work, thanks. :) Doug -------- Original Message -------- Subject: Re: panic: kmem_malloc(-1077936128): kmem_map too small Date: Fri, 15 Sep 2000 12:29:01 +0200 From: Mitja Horvat To: Doug Barton References: <20000914145450.A337@lamu.hermes.si> Hi Doug, since I'm not subscribed to freebsd-current, I would prefer that you forward this email. I will try to describe the panic in more detail below: Filesystem specific mount structure is copied from userspace in ffs_mount() in vfs_subr.c at line 178: /* copy in user arguments*/ err = copyin(data, (caddr_t)&args, sizeof (struct ufs_args)); if (err) goto error_1; /* can't get arguments*/ This structure is never checked for garbled data, and its args.export field is passed as is to vfs_export() and later to vfs_hang_addrlist(). We have the following two lines in vfs_hang_addrlist() at line 2252 in vfs_subr.c: i = sizeof(struct netcred) + argp->ex_addrlen + argp->ex_masklen; np = (struct netcred *) malloc(i, M_NETADDR, M_WAITOK); (argp in this case is the pointer to argc.export) argp->ex_addrlen is copied directly from userspace. If the structures in the kernel, and the userspace utility mismatch, ex_addrlen will have a different value than it was supposed to(-1077936128 on my machine, which paniced the kernel on every boot) and problems like memory leaks or panics may occur. Some sanity checking would be appropriate for the export_args structure. Regards, Mitja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 8:23:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.uni-bielefeld.de (mail2.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id 1DC5B37B43C; Fri, 15 Sep 2000 08:23:51 -0700 (PDT) Received: from frolic.no-support.loc (ppp36-174.hrz.uni-bielefeld.de [129.70.36.174]) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.4.0.2000.05.17.04.13.p6) with ESMTP id <0G0X0005XPFJFC@mail.uni-bielefeld.de>; Fri, 15 Sep 2000 17:23:50 +0200 (MET DST) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id DAA03536; Fri, 15 Sep 2000 03:40:53 +0200 (CEST envelope-from bjoern) Date: Fri, 15 Sep 2000 03:40:52 +0200 From: Bjoern Fischer Subject: Re: Fdescfs updates--coming to a devfs near you! In-reply-to: <56645.968935026@critter>; from phk@critter.freebsd.dk on Thu, Sep 14, 2000 at 02:37:06PM +0200 To: Poul-Henning Kamp Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Message-id: <20000915034052.B2859@frolic.no-support.loc> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline Content-transfer-encoding: 7BIT User-Agent: Mutt/1.2.5i References: <20000914115342.I77593@strontium.scientia.demon.co.uk> <56645.968935026@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 14, 2000 at 02:37:06PM +0200, Poul-Henning Kamp wrote: [...] > The majority of these programs could be handled by adding knowledge > of "-" as a magic filename to fopen(3). > > At the same time I would really love if we implemented "|.*" to mean > "do an popen(3)" instead. This would break POSIX and raise a security flaw in many applications. fopen(3) *never* should perform a fork/exec. Scary. Bjoern -- -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 8:54:59 2000 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 0C23837B423; Fri, 15 Sep 2000 08:54:54 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA45491; Fri, 15 Sep 2000 11:54:35 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 15 Sep 2000 11:54:35 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Julian Elischer Cc: Chris Costello , hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: <39C0885A.41C67EA6@elischer.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 On Thu, 14 Sep 2000, Julian Elischer wrote: > I've never thought of a use for fdescfs... I used /dev/fd/1 just yesterday for a third-party precompiled binary that insists on outputting to a file specified on the command line. Slapping in /dev/fd/1 lets me stuff the command in a pipe chain. Same goes for /dev/fd/0. Other file descriptors, I'm less sure about :-) Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, 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 Sep 15 9: 0:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from zaphod.kpnqwest.ch (zaphod.kpnqwest.ch [146.228.10.43]) by hub.freebsd.org (Postfix) with ESMTP id 0400937B422 for ; Fri, 15 Sep 2000 09:00:52 -0700 (PDT) Received: from oettinger.davidoff.ch ([195.49.110.243]) by zaphod.kpnqwest.ch (relay.kpnqwest.ch) (8.9.3/1.0) via ESMTP id PAA14489 for ; Fri, 15 Sep 2000 15:13:35 GMT env-from (vdfvoi@mail.computrain.de) Received: from mail.mindspring.com by oettinger.davidoff.ch via SMTP id smtp\t9egl8l5.in; 14 Sep 2000 16:21:00 +0200 From: To: Date: Thu, 14 Sep 2000 06:47:02 Message-Id: <500.197835.210319@mail.mindspring.com> Subject: 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 GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY! STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN GET ONE FOR ONLY $11.95 PER MONTH! DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A SIMPLE PHONE CALL TO OUR OFFICE. YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with no extra charge! UNLIMITED TRAFFIC -- no extra charge! FRONT PAGE EXTENSIONS are FULLY SUPPORTED. A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS. ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP CHARGE. FOR DETAILS CALL 1 888 248 0765 Webhosting International To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 9: 6:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 225B537B423; Fri, 15 Sep 2000 09:06:23 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id WAA00506; Thu, 14 Sep 2000 22:24:25 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009150524.WAA00506@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Wes Peters Cc: Greg Lehey , Thomas David Rivers , julian@elischer.org, nik@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: No block devices (was: VMWare on -current, how fast should I expect it to be?) In-reply-to: Your message of "Thu, 14 Sep 2000 23:18:11 MDT." <39C1B113.95D2B88B@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 2000 22:24:25 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Greg Lehey wrote: > > > > FWIW, I was never happy with the removal of block devices either. I > > was shouted down with "can you point to any one use they are?", to > > which I replied "just because I don't know of one doesn't mean there > > isn't one, or that there will never be one in the future". This is an > > example where they could presumably be useful. > > Doesn't Oracle run MUCH better when given raw block disk devices to store > data on? Oracle wants to cache it's own data, it doesn't want the buffer cache behind it. > Could this have lead to some of the poor performance Mike Smith > was seeing when testing this summer? No, we were layering over the filesystem, however filesystem load was insignificant. The Oracle performance issues are well known, and this isn't one of them. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 10:25:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id EBD1837B422; Fri, 15 Sep 2000 10:25:06 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e8FHP3r40546; Sat, 16 Sep 2000 02:25:03 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: Alain.Thivillon@hsc.fr Cc: Michael.Reifenberger.gp@icn.siemens.de, freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: Partial success with current on Laptop. In-Reply-To: <20000915141049.A695@yoko.hsc.fr> References: <67E0BE167008D31185F60008C7289DA0E12F0B@MCHH218E> <20000915141049.A695@yoko.hsc.fr> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000916022422P.iwasaki@jp.FreeBSD.org> Date: Sat, 16 Sep 2000 02:24:22 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 13 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > - apm (suspend/resume not testet) > > Works for me. > > My only problem is that Fan is NEVER turned off (it seems that > idle loop in kernel as become CPU intensive and energy hardware can not > stop cooling). At this time, this is a minor annoyance. Do you have acpi enabled in your kernel? If so, it could be. Thermal and processor power management portion of acpi is not implemented yet. All of the power resource components such as fan are just turned on at booting for now :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 10:46:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id 7A04837B423; Fri, 15 Sep 2000 10:46:35 -0700 (PDT) Received: from yoko.hsc.fr (yoko.hsc.fr [192.70.106.76]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "yoko.hsc.fr", Issuer CN "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id D25F91101F; Fri, 15 Sep 2000 19:46:33 +0200 (CEST) Received: by yoko.hsc.fr (Postfix-TLS, from userid 1001) id 8BFBD9B206; Fri, 15 Sep 2000 19:46:20 +0200 (CEST) Date: Fri, 15 Sep 2000 19:46:20 +0200 From: Alain Thivillon To: Mitsuru IWASAKI Cc: Michael.Reifenberger.gp@icn.siemens.de, freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: Partial success with current on Laptop. Message-ID: <20000915194620.E447@yoko.hsc.fr> References: <67E0BE167008D31185F60008C7289DA0E12F0B@MCHH218E> <20000915141049.A695@yoko.hsc.fr> <20000916022422P.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.2i In-Reply-To: <20000916022422P.iwasaki@jp.FreeBSD.org>; from iwasaki@jp.FreeBSD.org on Sat, Sep 16, 2000 at 02:24:22AM +0900 X-Organization: Herve Schauer Consultants X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mitsuru IWASAKI écrivait (wrote) : > Do you have acpi enabled in your kernel? no. I have tried ACPI some days ago, but system boot becomes incredibly slow (for example, syslogd complained about something like 'child process timeout' after enabling ACPI). All system activity such as fork and so was affected. > and processor power management portion of acpi is not implemented yet. > All of the power resource components such as fan are just turned on at > booting for now :-) Other problem with -CURRENT and laptops is that system time is not reinitialised after suspend and resume :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 11: 4: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 4045937B43C; Fri, 15 Sep 2000 11:04:02 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e8FI3xr47413; Sat, 16 Sep 2000 03:03:59 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: Alain.Thivillon@hsc.fr Cc: iwasaki@jp.FreeBSD.org, Michael.Reifenberger.gp@icn.siemens.de, freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: Partial success with current on Laptop. In-Reply-To: <20000915194620.E447@yoko.hsc.fr> References: <20000915141049.A695@yoko.hsc.fr> <20000916022422P.iwasaki@jp.FreeBSD.org> <20000915194620.E447@yoko.hsc.fr> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000916030316Q.iwasaki@jp.FreeBSD.org> Date: Sat, 16 Sep 2000 03:03:16 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 22 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Do you have acpi enabled in your kernel? > > no. I have tried ACPI some days ago, but system boot becomes > incredibly slow (for example, syslogd complained about something like > 'child process timeout' after enabling ACPI). All system activity such > as fork and so was affected. It seems the same with my TOSHIBA POTEGE 3110CT because of lack of processor power management implementation I think. My short term solution is acpiconf -d to make CPU running in normal speed. > > and processor power management portion of acpi is not implemented yet. > > All of the power resource components such as fan are just turned on at > > booting for now :-) > > Other problem with -CURRENT and laptops is that system time is not > reinitialised after suspend and resume :) Ah, you probably need to have a `device pmtimer' in your kernel config and `hint.pmtimer.0.at="isa"' in your devce.hints. If you don't like to reinitialize system time (e.g. prefer running ntpdate), you don't need to have pmtimer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 11:18:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id CF27A37B422 for ; Fri, 15 Sep 2000 11:18:13 -0700 (PDT) Received: from yoko.hsc.fr (yoko.hsc.fr [192.70.106.76]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "yoko.hsc.fr", Issuer CN "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id ADA1F10F82 for ; Fri, 15 Sep 2000 20:18:11 +0200 (CEST) Received: by yoko.hsc.fr (Postfix-TLS, from userid 1001) id 772C79B206; Fri, 15 Sep 2000 20:17:04 +0200 (CEST) Date: Fri, 15 Sep 2000 20:17:03 +0200 From: Alain Thivillon To: freebsd-current@FreeBSD.ORG Subject: Re: Partial success with current on Laptop. Message-ID: <20000915201703.A457@yoko.hsc.fr> References: <67E0BE167008D31185F60008C7289DA0E12F0B@MCHH218E> <20000915141049.A695@yoko.hsc.fr> <20000916022422P.iwasaki@jp.FreeBSD.org> <20000915194620.E447@yoko.hsc.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.2i In-Reply-To: <20000915194620.E447@yoko.hsc.fr>; from Alain.Thivillon@hsc.fr on Fri, Sep 15, 2000 at 07:46:20PM +0200 X-Organization: Herve Schauer Consultants X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alain Thivillon écrivait (wrote) : > Other problem with -CURRENT and laptops is that system time is not > reinitialised after suspend and resume :) Oups, this one is fixed by adding new 'pmtimer' device in my kernel. Maybe an entry in UPDATING will help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 11:50:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id BBA3C37B424 for ; Fri, 15 Sep 2000 11:50:23 -0700 (PDT) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.10.1/8.10.1) with ESMTP id e8FIoLN23603; Fri, 15 Sep 2000 20:50:21 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.10.1/8.10.1) with ESMTP id e8FIoLU06766; Fri, 15 Sep 2000 20:50:21 +0200 (MET DST) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.11.0/8.11.0/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id e8FIoKm90479; Fri, 15 Sep 2000 20:50:21 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.11.0/8.11.0/alaska [ $Revision: 1.4 ]) id e8FIoKL82149; Fri, 15 Sep 2000 18:50:20 GMT (envelope-from ust) Date: Fri, 15 Sep 2000 20:50:20 +0200 From: Udo Schweigert To: Clive Lin Cc: freebsd-current@FreeBSD.ORG Subject: Re: ssh and scp fail connecting to a root account Message-ID: <20000915205020.A82106@alaska.cert.siemens.de> Mail-Followup-To: Clive Lin , freebsd-current@FreeBSD.ORG References: <20000915163344.A79462@alaska.cert.siemens.de> <20000916005151.A24358@educampus.ncl.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000916005151.A24358@educampus.ncl.edu.tw>; from clive@CirX.ORG on Sat, Sep 16, 2000 at 12:51:51AM +0800 X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Sep 16, 2000 at 00:51:51 +0800, Clive Lin wrote: > On Fri, Sep 15, 2000 at 04:33:44PM +0200, Udo Schweigert wrote: > > sshd in realloc(): error: junk pointer, too high to make sense. > > Connection to zzzz closed. > Hm... did you just make new ssh instead of > making world or rebuilding kernel ? > No, I did a complete "make world" + a new kernel (with config -r) > I got exactly the same error on the day sshd upgraded. > dmesg shows that sshd got signal 11 all the time. > My sshd got signal 6 (ABORT) -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : ust@cert.siemens.de PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 12:15:57 2000 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 955AB37B424 for ; Fri, 15 Sep 2000 12:15:49 -0700 (PDT) Received: (qmail 9886 invoked by uid 0); 15 Sep 2000 19:15:44 -0000 Received: from p3ee20a99.dip.t-dialin.net (HELO speedy.gsinet) (62.226.10.153) by mail.gmx.net with SMTP; 15 Sep 2000 19:15:44 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id TAA28650 for current@freebsd.org; Fri, 15 Sep 2000 19:45:07 +0200 Date: Fri, 15 Sep 2000 19:45:07 +0200 From: Gerhard Sittig To: current@freebsd.org Subject: Re: mtree again Message-ID: <20000915194506.D27034@speedy.gsinet> Mail-Followup-To: current@freebsd.org References: <20000915033837.A564@nagual.pp.ru> <200009142341.RAA00700@harmony.village.org> <20000915043925.A83698@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000915043925.A83698@nagual.pp.ru>; from ache@nagual.pp.ru on Fri, Sep 15, 2000 at 04:39:26AM +0400 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 15, 2000 at 04:39 +0400, Andrey A. Chernov wrote: > > [ ... change mtree(1) physical vs logical traversal ... ] [ ... mtree.c diff ...] > @@ -170,7 +170,7 @@ > usage() > { > (void)fprintf(stderr, > -"usage: mtree [-PUcdeinqrux] [-f spec] [-K key] [-k key] [-p path] [-s seed]\n" > +"usage: mtree [-LUcdeinqrux] [-f spec] [-K key] [-k key] [-p path] [-s seed]\n" > "\t[-X excludes]\n"); > exit(1); > } Are you trying to remove the -P switch? Then there's no way of having a "logical default" via aliases / shell scripts / you name it and still tell mtree to do a physical walk. This very topic is discussed in the symlink(7) manpage. The author sees a chance for users wanting to "override" behaviour multiple times by specifying multiple toggles. I feel it's OK when you change the default to "walk the fs in its physical meaning", but I wouldn't want you to provide only a one way switch. Please leave -P in there or rename it to -H (which should be available) plus make it the reverse of -L if it's not yet at the moment. In case I'm absolutely missing the topic please ignore this message. :) 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 Fri Sep 15 12:37:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9063037B422; Fri, 15 Sep 2000 12:37:47 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA47611; Fri, 15 Sep 2000 12:37:47 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 15 Sep 2000 12:37:47 -0700 (PDT) From: Kris Kennaway To: Udo Schweigert Cc: freebsd-current@FreeBSD.ORG Subject: Re: ssh and scp fail connecting to a root account In-Reply-To: <20000915163344.A79462@alaska.cert.siemens.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Sep 2000, Udo Schweigert wrote: > The strange: both commands succeed if connecting to a non-root account. > > Are there any others with these problems? Any clues? run sshd -d on the server, ssh -d on the client, and send me the output Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 14:13:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 2EDA037B42C for ; Fri, 15 Sep 2000 14:13:23 -0700 (PDT) Received: from rac1.wam.umd.edu (IDENT:root@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA10809 for ; Fri, 15 Sep 2000 17:13:21 -0400 (EDT) Received: from rac1.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id RAA27227 for ; Fri, 15 Sep 2000 17:13:21 -0400 (EDT) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA27223 for ; Fri, 15 Sep 2000 17:13:21 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Fri, 15 Sep 2000 17:13:21 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: the SMPng stuff on UP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alright, I just wanted to let everyone know that I have gotten the SMPng stuff up and working on my -CURRENT machine, and everything seems to work fine except the occasional "pcm0: hwptr went backwards x --> y" when I play sound and then do anything in X that involves moving a window. Oh, and also, my load avg runs at a constant 1.00 instead of 0.00 when I'm not using the machine, even though top reports 95-99% cpu idle. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 15: 4:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 0D50C37B422; Fri, 15 Sep 2000 15:04:36 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id PAA33840; Fri, 15 Sep 2000 15:04:33 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009152204.PAA33840@pike.osd.bsdi.com> Subject: Re: cvs commit: src/sys/kern kern_idle.c src/sys/vm vm_meter.c src/sys/i386/isa ithread.c src/sys/sys proc.h In-Reply-To: <200009152200.PAA79187@freefall.freebsd.org> from John Baldwin at "Sep 15, 2000 03:00:24 pm" To: John Baldwin Date: Fri, 15 Sep 2000 15:04:33 -0700 (PDT) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > jhb 2000/09/15 15:00:24 PDT > > Modified files: > sys/kern kern_idle.c > sys/vm vm_meter.c > sys/i386/isa ithread.c > sys/sys proc.h > Log: > - Add a new process flag P_NOLOAD that marks a process that should be > ignored during load average calcuations. > - Set this flag for the idle processes and the softinterrupt process. This should fix the load average calculations with SMPng. Note that the load is still going to be higher than it used to. This is due to the fact that before SMPng, we did not have a process context for the idle loop. Thus, when an interrupt occurred during the idle loop, no process was marked runnable as a result, and that interrupt processing was not taken into account. Now when an interrupt occurs, we mark an interrupt thread runnable, which increases the number of runnable processes that vmmeter finds when it performs the load average calculations. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "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 Fri Sep 15 16:12: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.telemere.net (mail.telemere.net [63.224.9.4]) by hub.freebsd.org (Postfix) with ESMTP id 7CC5C37B43C; Fri, 15 Sep 2000 16:11:55 -0700 (PDT) Received: by mail.telemere.net (Postfix, from userid 1001) id 01CE020F01; Fri, 15 Sep 2000 18:17:11 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.telemere.net (Postfix) with ESMTP id ED8341D101; Fri, 15 Sep 2000 18:17:11 -0500 (CDT) Date: Fri, 15 Sep 2000 18:17:07 -0500 (CDT) From: Visigoth To: stable@freebsd.org Cc: current@freebsd.org Subject: Accessing floppy under 4.1-STABLE (with DPT?) causes hang... Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-731123262-969059827=:516" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-731123262-969059827=:516 Content-Type: TEXT/PLAIN; charset=US-ASCII -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry for the cross post, but it could be something that affects both... Right now I am experiencing some really strange behavior with my Dell servers. Mounting a floppy, or accessing it via dd(1) causes a system hang, (accompanied by a bios beep from the dpt card as though it is being rebooted). I have quite a number of other machines which are dells which are not displaying this behavior, the only 2 things that I have been able to discover as a parallel is the PM3334UW cards in all 3 of them, as well as so far having only tested it on dual capable motherboards. I have attempted hardware replacement of floppy drives (when I originally thought I just had a bad floppy), booting SMP or UP kernels, as well as makeing sure I have the most recent firmware on all the involved boards... there is also a little interesting tidbit in the dmesg from the machines that they all have in common: fd0c: hard error reading fsbn 16 of 16-31 (No status) I have attached the rest of the dmesg. So far, testing includes machines sup'd Sept 6th source (broken) all through today. I know that it worked back (way back) in early Aug. Any questions/answers would be much appreciated as I have reached the end of my diagnosis capacity. Have fun, and thanks all... Visigoth Damieon Stark Sr. Unix Systems Administrator visigoth@telemere.net PGP Public Key: www.telemere.net/~visigoth/visigoth.asc ____________________________________________________________________________ | M$ -Where do you want to go today? | Linux -Where do you want to go tomorrow?| FreeBSD - The POWER to serve Freebsd -Are you guys coming or what? | http://www.freebsd.org | | - ---------------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.1i iQA/AwUBOcKf5znmC/+RTnGeEQJG1wCg3PMvJrghAP+nni347s8rV1A7pSMAnjFM G0QJICB2R0KhPSB+kQe3SINJ =1Y4b -----END PGP SIGNATURE----- --0-731123262-969059827=:516 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: dmesg Content-Disposition: attachment; filename="dmesg.txt" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk3OSwgMTk4MCwgMTk4MywgMTk4NiwgMTk4OCwg MTk4OSwgMTk5MSwgMTk5MiwgMTk5MywgMTk5NA0KCVRoZSBSZWdlbnRzIG9m IHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuIEFsbCByaWdodHMgcmVz ZXJ2ZWQuDQpGcmVlQlNEIDQuMS1TVEFCTEUgIzA6IFdlZCBTZXAgIDYgMTI6 Mjg6MDIgQ0RUIDIwMDANCiAgICB2aXNpZ290aEBtYWlsLnRlbGVtZXJlLm5l dDovdXNyL3NyYy9zeXMvY29tcGlsZS9NQUlMDQpUaW1lY291bnRlciAiaTgy NTQiICBmcmVxdWVuY3kgMTE5MzE4MiBIeg0KQ1BVOiBQZW50aXVtIElJSS9Q ZW50aXVtIElJSSBYZW9uL0NlbGVyb24gKDU1MC4wMi1NSHogNjg2LWNsYXNz IENQVSkNCiAgT3JpZ2luID0gIkdlbnVpbmVJbnRlbCIgIElkID0gMHg2NzMg IFN0ZXBwaW5nID0gMw0KICBGZWF0dXJlcz0weDM4M2ZiZmY8RlBVLFZNRSxE RSxQU0UsVFNDLE1TUixQQUUsTUNFLENYOCxBUElDLFNFUCxNVFJSLFBHRSxN Q0EsQ01PVixQQVQsUFNFMzYsTU1YLEZYU1IsWE1NPg0KcmVhbCBtZW1vcnkg ID0gMTA3MzczMzYzMiAoMTA0ODU2OEsgYnl0ZXMpDQpjb25maWc+IHENCmF2 YWlsIG1lbW9yeSA9IDEwNDIzNjY0NjQgKDEwMTc5MzZLIGJ5dGVzKQ0KQ2hh bmdpbmcgQVBJQyBJRCBmb3IgSU8gQVBJQyAjMCBmcm9tIDAgdG8gMiBvbiBj aGlwDQpQcm9ncmFtbWluZyAyNCBwaW5zIGluIElPQVBJQyAjMA0KSU9BUElD ICMwIGludHBpbiAyIC0+IGlycSAwDQpGcmVlQlNEL1NNUDogTXVsdGlwcm9j ZXNzb3IgbW90aGVyYm9hcmQNCiBjcHUwIChCU1ApOiBhcGljIGlkOiAgMSwg dmVyc2lvbjogMHgwMDA0MDAxMSwgYXQgMHhmZWUwMDAwMA0KIGNwdTEgKEFQ KTogIGFwaWMgaWQ6ICAwLCB2ZXJzaW9uOiAweDAwMDQwMDExLCBhdCAweGZl ZTAwMDAwDQogaW8wIChBUElDKTogYXBpYyBpZDogIDIsIHZlcnNpb246IDB4 MDAxNzAwMTEsIGF0IDB4ZmVjMDAwMDANClByZWxvYWRlZCBlbGYga2VybmVs ICJrZXJuZWwiIGF0IDB4YzAzNzAwMDAuDQpQcmVsb2FkZWQgdXNlcmNvbmZp Z19zY3JpcHQgIi9ib290L2tlcm5lbC5jb25mIiBhdCAweGMwMzcwMDljLg0K UGVudGl1bSBQcm8gTVRSUiBzdXBwb3J0IGVuYWJsZWQNCm1kMDogTWFsbG9j IGRpc2sNCm5weDA6IDxtYXRoIHByb2Nlc3Nvcj4gb24gbW90aGVyYm9hcmQN Cm5weDA6IElOVCAxNiBpbnRlcmZhY2UNCnBjaWIwOiA8SW50ZWwgODI0NTRO WCBQWEIjMCwgQnVzI0E+IG9uIG1vdGhlcmJvYXJkDQpwY2kwOiA8UENJIGJ1 cz4gb24gcGNpYjANCmlzYWIwOiA8SW50ZWwgODIzNzFBQiBQQ0kgdG8gSVNB IGJyaWRnZT4gYXQgZGV2aWNlIDIuMCBvbiBwY2kwDQppc2EwOiA8SVNBIGJ1 cz4gb24gaXNhYjANCnBjaTA6IDxJbnRlbCBQSUlYNCBBVEEgY29udHJvbGxl cj4gYXQgMi4xDQpwY2kwOiA8SW50ZWwgODIzNzFBQi9FQiAoUElJWDQpIFVT QiBjb250cm9sbGVyPiBhdCAyLjIgaXJxIDANClRpbWVjb3VudGVyICJQSUlY IiAgZnJlcXVlbmN5IDM1Nzk1NDUgSHoNCmNoaXAwOiA8SW50ZWwgODIzNzFB QiBQb3dlciBtYW5hZ2VtZW50IGNvbnRyb2xsZXI+IHBvcnQgMHg4NTAtMHg4 NWYgYXQgZGV2aWNlIDIuMyBvbiBwY2kwDQpwY2kwOiA8QVRJIE1hY2g2NC1H SSBncmFwaGljcyBhY2NlbGVyYXRvcj4gYXQgNC4wDQpmeHAwOiA8SW50ZWwg UHJvIDEwLzEwMEIvMTAwKyBFdGhlcm5ldD4gcG9ydCAweGQ4YzAtMHhkOGZm IG1lbSAweGZlNDAwMDAwLTB4ZmU0ZmZmZmYsMHhmZTYwMDAwMC0weGZlNjAw ZmZmIGlycSAxNCBhdCBkZXZpY2UgOC4wIG9uIHBjaTANCmZ4cDA6IEV0aGVy bmV0IGFkZHJlc3MgMDA6ZDA6Yjc6MmM6MzI6MzcNCmRwdDA6IDxEUFQgQ2Fj aGluZyBTQ1NJIFJBSUQgQ29udHJvbGxlcj4gcG9ydCAweGQ4YTAtMHhkOGJm IGlycSAxMSBhdCBkZXZpY2UgMTAuMCBvbiBwY2kwDQpkcHQwOiBEUFQgUE0z MzM0VVcgRlcgUmV2LiAwN00wLCAxIGNoYW5uZWwsIDY0IENDQnMNCnBjaWIz OiA8SW50ZWwgODI0NTROWCBQQ0kgRXhwYW5kZXIgQnJpZGdlPiBhdCBkZXZp Y2UgMTguMCBvbiBwY2kwDQpwY2liNDogPEludGVsIDgyNDU0TlggUENJIEV4 cGFuZGVyIEJyaWRnZT4gYXQgZGV2aWNlIDE5LjAgb24gcGNpMA0KcGNpYjU6 IDxJbnRlbCA4MjQ1NE5YIFBDSSBFeHBhbmRlciBCcmlkZ2U+IGF0IGRldmlj ZSAyMC4wIG9uIHBjaTANCnBjaWIxOiA8SW50ZWwgODI0NTROWCBQWEIjMCwg QnVzI0I+IG9uIG1vdGhlcmJvYXJkDQpwY2kxOiA8UENJIGJ1cz4gb24gcGNp YjENCmFoYzA6IDxBZGFwdGVjIGFpYzc4OTAvOTEgVWx0cmEyIFNDU0kgYWRh cHRlcj4gcG9ydCAweGVjMDAtMHhlY2ZmIG1lbSAweGZlODAyMDAwLTB4ZmU4 MDJmZmYgaXJxIDIxIGF0IGRldmljZSA0LjAgb24gcGNpMQ0KYWhjMDogYWlj Nzg5MC85MSBXaWRlIENoYW5uZWwgQSwgU0NTSSBJZD03LCAxNi8yNTUgU0NC cw0KYWhjMTogPEFkYXB0ZWMgYWljNzg5MC85MSBVbHRyYTIgU0NTSSBhZGFw dGVyPiBwb3J0IDB4ZTgwMC0weGU4ZmYgbWVtIDB4ZmU4MDEwMDAtMHhmZTgw MWZmZiBpcnEgMjIgYXQgZGV2aWNlIDYuMCBvbiBwY2kxDQphaGMxOiBhaWM3 ODkwLzkxIFdpZGUgQ2hhbm5lbCBBLCBTQ1NJIElkPTcsIDE2LzI1NSBTQ0Jz DQphaGMyOiA8QWRhcHRlYyBhaWM3ODYwIFNDU0kgYWRhcHRlcj4gcG9ydCAw eGU0MDAtMHhlNGZmIG1lbSAweGZlODAwMDAwLTB4ZmU4MDBmZmYgaXJxIDIw IGF0IGRldmljZSA4LjAgb24gcGNpMQ0KYWhjMjogYWljNzg2MCBTaW5nbGUg Q2hhbm5lbCBBLCBTQ1NJIElkPTcsIDMvMjU1IFNDQnMNCnBjaWIyOiA8SW50 ZWwgODI0NTROWCBQWEIjMSwgQnVzI0E+IG9uIG1vdGhlcmJvYXJkDQpwY2ky OiA8UENJIGJ1cz4gb24gcGNpYjINCmZ4cDE6IDxJbnRlbCBQcm8gMTAvMTAw Qi8xMDArIEV0aGVybmV0PiBwb3J0IDB4ZmNjMC0weGZjZmYgbWVtIDB4ZmU5 MDAwMDAtMHhmZTlmZmZmZiwweGZlYjAwMDAwLTB4ZmViMDBmZmYgaXJxIDE5 IGF0IGRldmljZSAxLjAgb24gcGNpMg0KZnhwMTogRXRoZXJuZXQgYWRkcmVz cyAwMDpkMDpiNzoyYzoyOTpkNQ0KZmRjMDogPE5FQyA3MjA2NUIgb3IgY2xv bmU+IGF0IHBvcnQgMHgzZjAtMHgzZjUsMHgzZjcgaXJxIDYgZHJxIDIgb24g aXNhMA0KZmRjMDogRklGTyBlbmFibGVkLCA4IGJ5dGVzIHRocmVzaG9sZA0K ZmQwOiA8MTQ0MC1LQiAzLjUiIGRyaXZlPiBvbiBmZGMwIGRyaXZlIDANCmF0 a2JkYzA6IDxLZXlib2FyZCBjb250cm9sbGVyIChpODA0Mik+IGF0IHBvcnQg MHg2MCwweDY0IG9uIGlzYTANCmF0a2JkMDogPEFUIEtleWJvYXJkPiBmbGFn cyAweDEgaXJxIDEgb24gYXRrYmRjMA0Ka2JkMCBhdCBhdGtiZDANCnBzbTA6 IDxQUy8yIE1vdXNlPiBpcnEgMTIgb24gYXRrYmRjMA0KcHNtMDogbW9kZWwg R2VuZXJpYyBQUy8yIG1vdXNlLCBkZXZpY2UgSUQgMA0KdmdhMDogPEdlbmVy aWMgSVNBIFZHQT4gYXQgcG9ydCAweDNjMC0weDNkZiBpb21lbSAweGEwMDAw LTB4YmZmZmYgb24gaXNhMA0Kc2MwOiA8U3lzdGVtIGNvbnNvbGU+IGF0IGZs YWdzIDB4MTAwIG9uIGlzYTANCnNjMDogVkdBIDwxNiB2aXJ0dWFsIGNvbnNv bGVzLCBmbGFncz0weDMwMD4NCnNpbzAgYXQgcG9ydCAweDNmOC0weDNmZiBp cnEgNCBmbGFncyAweDEwIG9uIGlzYTANCnNpbzA6IHR5cGUgMTY1NTBBDQpz aW8xIGF0IHBvcnQgMHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhMA0Kc2lvMTog dHlwZSAxNjU1MEENCnBwYzA6IDxQYXJhbGxlbCBwb3J0PiBhdCBwb3J0IDB4 Mzc4LTB4MzdmIGlycSA3IG9uIGlzYTANCnBwYzA6IFNNQy1saWtlIGNoaXBz ZXQgKEVDUC9FUFAvUFMyL05JQkJMRSkgaW4gQ09NUEFUSUJMRSBtb2RlDQpw cGMwOiBGSUZPIHdpdGggMTYvMTYvOCBieXRlcyB0aHJlc2hvbGQNCmxwdDA6 IDxQcmludGVyPiBvbiBwcGJ1czANCmxwdDA6IEludGVycnVwdC1kcml2ZW4g cG9ydA0KcHBpMDogPFBhcmFsbGVsIEkvTz4gb24gcHBidXMwDQpwbGlwMDog PFBMSVAgbmV0d29yayBpbnRlcmZhY2U+IG9uIHBwYnVzMA0KQVBJQ19JTzog VGVzdGluZyA4MjU0IGludGVycnVwdCBkZWxpdmVyeQ0KQVBJQ19JTzogcm91 dGluZyA4MjU0IHZpYSBJT0FQSUMgIzAgaW50cGluIDINCklQIEZpbHRlcjog djMuNC44IGluaXRpYWxpemVkLiAgRGVmYXVsdCA9IHBhc3MgYWxsLCBMb2dn aW5nID0gZW5hYmxlZA0KV2FpdGluZyAxNSBzZWNvbmRzIGZvciBTQ1NJIGRl dmljZXMgdG8gc2V0dGxlDQpTTVA6IEFQIENQVSAjMSBMYXVuY2hlZCENCnBh c3MxIGF0IGRwdDAgYnVzIDAgdGFyZ2V0IDYgbHVuIDANCnBhc3MxOiA8REVM TCAxeDggVTJXIFNDU0kgQlAgNS4yMz4gRml4ZWQgUHJvY2Vzc29yIFNDU0kt MiBkZXZpY2UgDQpkYTAgYXQgZHB0MCBidXMgMCB0YXJnZXQgMCBsdW4gMA0K ZGEwOiA8RFBUIFJBSUQtNSAwN00wPiBGaXhlZCBEaXJlY3QgQWNjZXNzIFND U0ktMiBkZXZpY2UgDQpkYTA6IDM0NzMyTUIgKDcxMTMxOTA0IDUxMiBieXRl IHNlY3RvcnM6IDI1NUggNjNTL1QgNDQyN0MpDQpNb3VudGluZyByb290IGZy b20gdWZzOi9kZXYvZGEwczFhDQpjZDAgYXQgYWhjMiBidXMgMCB0YXJnZXQg NSBsdW4gMA0KY2QwOiA8TkVDIENELVJPTSBEUklWRTo0NjYgMS4wNj4gUmVt b3ZhYmxlIENELVJPTSBTQ1NJLTIgZGV2aWNlIA0KY2QwOiAyMC4wMDBNQi9z IHRyYW5zZmVycyAoMjAuMDAwTUh6LCBvZmZzZXQgMTUpDQpjZDA6IEF0dGVt cHQgdG8gcXVlcnkgZGV2aWNlIHNpemUgZmFpbGVkOiBOT1QgUkVBRFksIE1l ZGl1bSBub3QgcHJlc2VudA0KZmQwYzogaGFyZCBlcnJvciByZWFkaW5nIGZz Ym4gMTYgb2YgMTYtMzEgKE5vIHN0YXR1cykNCg== --0-731123262-969059827=:516-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 15 17:23:49 2000 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 7337A37B423 for ; Fri, 15 Sep 2000 17:23:47 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e8G0Ni595365 for current@freebsd.org; Sat, 16 Sep 2000 04:23:44 +0400 (MSD) (envelope-from ache) Date: Sat, 16 Sep 2000 04:23:42 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: Call for libtermcap ressurection from the dead Message-ID: <20000916042341.A95164@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just found today yet another ncurses tgoto emulation bug (now can't handle "%.", triggered by 'screen') and am angry-motivated enough for this proposal. Avdantages: 1) We'll be 100%-compatible with all libtermcap programs again. 2) Save LOTS of space for static binaries since libtermcap is extremally small. Opinions? -- 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 Sep 15 19:50:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id D242937B42C; Fri, 15 Sep 2000 19:50:26 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8G2n7v32143; Sat, 16 Sep 2000 03:49:07 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8G2n3n02415; Sat, 16 Sep 2000 03:49:03 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009160249.e8G2n3n02415@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: Ben Smithurst , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.org, current@FreeBSD.org, brian@Awfulhak.org Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Message from Poul-Henning Kamp of "Thu, 14 Sep 2000 14:37:06 +0200." <56645.968935026@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Sep 2000 03:49:02 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The majority of these programs could be handled by adding knowledge > of "-" as a magic filename to fopen(3). [.....] > I would argue that the programs and the scripts that call them are > already broken, but hey... So (just to add fuel to the mass opposition), do this without temporary files: count=$(program | tee /dev/stderr | wc -l) exit $count But then, you also said: > At the same time I would really love if we implemented "|.*" to mean > "do an popen(3)" instead. so I guess this could result in count=$(program |. cat | wc -l) exit $count (substitute correct "|.*" syntax - whatever that is). > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. -- 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 Fri Sep 15 20: 3:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 8C08A37B42C; Fri, 15 Sep 2000 20:03:51 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8G33cv32204; Sat, 16 Sep 2000 04:03:38 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8G33Xn08810; Sat, 16 Sep 2000 04:03:33 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009160303.e8G33Xn08810@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kris Kennaway Cc: Udo Schweigert , freebsd-current@FreeBSD.org, brian@Awfulhak.org Subject: Re: ssh and scp fail connecting to a root account In-Reply-To: Message from Kris Kennaway of "Fri, 15 Sep 2000 12:37:47 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Sep 2000 04:03:32 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 15 Sep 2000, Udo Schweigert wrote: > > > The strange: both commands succeed if connecting to a non-root account. > > > > Are there any others with these problems? Any clues? > > run sshd -d on the server, ssh -d on the client, and send me the output Hmm, I've been seeing this problem too. I ran sshd -p 1234 -d and it worked ok. I then killed the running sshd and started sshd -d and it worked too. I then ran sshd.... and it worked. I'll look into this some more when I can reboot the machine :-/ > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe -- 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 Fri Sep 15 23:28:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 498C137B422 for ; Fri, 15 Sep 2000 23:28:37 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id CEF5F1C6F; Sat, 16 Sep 2000 02:28:36 -0400 (EDT) Date: Sat, 16 Sep 2000 02:28:36 -0400 From: Bill Fumerola To: "Andrey A. Chernov" Cc: current@freebsd.org Subject: Re: Call for libtermcap ressurection from the dead Message-ID: <20000916022836.X47559@jade.chc-chimes.com> References: <20000916042341.A95164@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000916042341.A95164@nagual.pp.ru>; from ache@nagual.pp.ru on Sat, Sep 16, 2000 at 04:23:42AM +0400 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Sep 16, 2000 at 04:23:42AM +0400, Andrey A. Chernov wrote: > Avdantages: > > 1) We'll be 100%-compatible with all libtermcap programs again. > 2) Save LOTS of space for static binaries since libtermcap is extremally > small. > > Opinions? I don't object. The namespace collisions in src/games with ncurses functions are really, really bad, and though just not linking to ncurses is sort of a hackish fix, this would at least mask the problems until further into the future when I have time to change function names. :-> -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 0:26: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from goliath.siemens.de (goliath2.siemens.de [192.35.17.28]) by hub.freebsd.org (Postfix) with ESMTP id D868637B424; Sat, 16 Sep 2000 00:26:02 -0700 (PDT) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer goliath.siemens.de) Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e8G7Q1306564; Sat, 16 Sep 2000 09:26:01 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail3.siemens.de (8.11.0/8.11.0) with ESMTP id e8G7Q1T9859812; Sat, 16 Sep 2000 09:26:01 +0200 (MEST) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.11.0/8.11.0/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id e8G7Q0m96903; Sat, 16 Sep 2000 09:26:00 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.11.0/8.11.0/alaska [ $Revision: 1.4 ]) id e8G7Q0n19387; Sat, 16 Sep 2000 07:26:00 GMT (envelope-from ust) Date: Sat, 16 Sep 2000 09:26:00 +0200 From: Udo Schweigert To: Brian Somers Cc: Kris Kennaway , Udo Schweigert , freebsd-current@FreeBSD.org Subject: Re: ssh and scp fail connecting to a root account Message-ID: <20000916092600.B19237@alaska.cert.siemens.de> Mail-Followup-To: Brian Somers , Kris Kennaway , Udo Schweigert , freebsd-current@FreeBSD.org References: <200009160303.e8G33Xn08810@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: <200009160303.e8G33Xn08810@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Sat, Sep 16, 2000 at 04:03:32AM +0100 X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Sep 16, 2000 at 04:03:32 +0100, Brian Somers wrote: > > On Fri, 15 Sep 2000, Udo Schweigert wrote: > > > > > The strange: both commands succeed if connecting to a non-root account. > > > > > > Are there any others with these problems? Any clues? > > > > run sshd -d on the server, ssh -d on the client, and send me the output > > Hmm, I've been seeing this problem too. I ran sshd -p 1234 -d and it > worked ok. I then killed the running sshd and started sshd -d and it > worked too. I then ran sshd.... and it worked. > I tried that, and it did not work for me. Same results as on port 22. Best regards. -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : ust@cert.siemens.de PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 0:33:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 6699837B422 for ; Sat, 16 Sep 2000 00:33:51 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13aCTr-000BaL-00; Sat, 16 Sep 2000 09:33:47 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e8G7Xhn05997; Sat, 16 Sep 2000 09:33:43 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009160733.e8G7Xhn05997@grimreaper.grondar.za> To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Question References: <200009142350.RAA00806@harmony.village.org> In-Reply-To: <200009142350.RAA00806@harmony.village.org> ; from Warner Losh "Thu, 14 Sep 2000 17:50:24 CST." Date: Sat, 16 Sep 2000 09:33:42 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Second, on both my sn card and my aue cards are installed I get: > WARNING: Driver mistake: repeat make_dev("bpf0") Me too, on my ep card. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 4:18:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mine.kame.net. (kame195.kame.net [203.178.141.195]) by hub.freebsd.org (Postfix) with ESMTP id 8466A37B422 for ; Sat, 16 Sep 2000 04:18:26 -0700 (PDT) Received: from localhost ([202.249.11.124]) by mine.kame.net. (8.9.3/3.7W) with ESMTP id UAA28076; Sat, 16 Sep 2000 20:10:51 +0900 (JST) To: rbezuide@oskar.nanoteq.co.za Cc: freebsd-current@freebsd.org, snap-users@kame.net Subject: Re: (KAME-snap 3318) Panic on current (12 Sept) In-Reply-To: Your message of "Thu, 14 Sep 2000 11:25:28 +0200 (SAST)" References: X-Mailer: Cue version 0.6 (000609-1000/sakane) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Message-Id: <20000916202011C.sakane@ydc.co.jp> Date: Sat, 16 Sep 2000 20:20:11 +0900 From: "Shoichi 'Ne' Sakane" X-Dispatcher: imput version 990905(IM130) Lines: 25 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm running a current machine of 12 Sept although this problem > also occured on a current of a few days earlier ... > > This only happens when using the IPv6 IPSec code during the day, > it is readily reproduceable. > > If during the day I load the racoon daemon and load keys and > establish a IPSec tunnel connection everything works fine till > 2:00 am when the daily script runs OR if I run the daily script > by hand ... I generated the following dump and backtrace ... > > It seems to crash in a makedev routine using FOREACH list macro's. > > The problem doesn't seem to be with the list or the makedev function > in kern_conf.c. It seems to me that something in the kernel > corrupts the static list dev_hash when using the IPSec code. > > Summary - when ising IPSec ... machine panics during daily > script execution. I think IPsec is not relative to this issue. To make sure, does your machine run healthy without IPsec ? Please try the following. case 1) with option IPSEC, but no SPD entry. case 2) without option IPSEC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 6: 0:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 9C07037B422; Sat, 16 Sep 2000 06:00:22 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8GD03v34471; Sat, 16 Sep 2000 14:00:03 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8GCxpm01766; Sat, 16 Sep 2000 13:59:51 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009161259.e8GCxpm01766@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kris Kennaway Cc: Brian Somers , Udo Schweigert , freebsd-current@FreeBSD.org, brian@Awfulhak.org Subject: Re: ssh and scp fail connecting to a root account In-Reply-To: Message from Brian Somers of "Sat, 16 Sep 2000 04:03:32 BST." <200009160303.e8G33Xn08810@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Sep 2000 13:59:50 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Fri, 15 Sep 2000, Udo Schweigert wrote: > > > > > The strange: both commands succeed if connecting to a non-root account. > > > > > > Are there any others with these problems? Any clues? > > > > run sshd -d on the server, ssh -d on the client, and send me the output > > Hmm, I've been seeing this problem too. I ran sshd -p 1234 -d and it > worked ok. I then killed the running sshd and started sshd -d and it > worked too. I then ran sshd.... and it worked. > > I'll look into this some more when I can reboot the machine :-/ This is what I get on the server: hak:~ $ sudo sshd -d debug: sshd version OpenSSH_2.2.0 debug: read DSA private key done debug: Bind to port 22 on ::. Server listening on :: port 22. debug: Bind to port 22 on 0.0.0.0. Server listening on 0.0.0.0 port 22. Generating 768 bit RSA key. RSA key generation complete. debug: Server will not fork when running in debugging mode. Connection from localhost port 1031 Connection from ::1 port 1031 debug: Client protocol version 1.5; client software version OpenSSH_2.2.0 debug: Local version string SSH-1.99-OpenSSH_2.2.0 debug: Sent 768 bit public key and 1024 bit host key. debug: Encryption type: 3des debug: Received session key; encryption turned on. debug: Installing crc compensation attack detector. debug: Attempting authentication for brian. Accepted rsa for brian from ::1 port 1031 debug: session_new: init debug: session_new: session 0 debug: Allocating pty. debug: Received request for X11 forwarding with auth spoofing. debug: fd 8 setting O_NONBLOCK debug: channel 0: new [X11 inet listener] debug: fd 9 setting O_NONBLOCK debug: channel 1: new [X11 inet listener] debug: Received authentication agent forwarding request. debug: fd 10 setting O_NONBLOCK debug: channel 2: new [auth socket] debug: Entering interactive session. debug: no set_nonblock for tty fd 3 debug: Setting controlling tty using TIOCSCTTY. debug: no set_nonblock for tty fd 4 debug: server_init_dispatch_13 debug: server_init_dispatch_15 debug: tvp!=NULL kid 0 mili 10 debug: tvp!=NULL kid 0 mili 10 debug: tvp!=NULL kid 0 mili 10 debug: tvp!=NULL kid 0 mili 10 debug: tvp!=NULL kid 0 mili 10 debug: Received SIGCHLD. debug: tvp!=NULL kid 1 mili 10 debug: tvp!=NULL kid 1 mili 100 debug: End of interactive session; stdin 0, stdout (read 310, sent 310), stderr 0 bytes. debug: channel_free: channel 0: status: The following connections are open: debug: channel_free: channel 1: status: The following connections are open: debug: channel_free: channel 2: status: The following connections are open: Disconnecting: Command terminated on signal 6. debug: Calling cleanup 0x8053874(0x0) debug: xauthfile_cleanup_proc called debug: Calling cleanup 0x8060ee0(0x0) debug: Calling cleanup 0x80538e8(0x80758c0) debug: pty_cleanup_proc: /dev/ttyp2 debug: Calling cleanup 0x805b890(0x0) hak:~ $ And on the client I see this: hak:~ $ ssh -v localhost SSH Version OpenSSH_2.2.0, protocol versions 1.5/2.0. Compiled with SSL (0x0090581f). debug: Reading configuration data /etc/ssh/ssh_config debug: Applying options for * debug: ssh_connect: getuid 15 geteuid 15 anon 1 debug: Connecting to localhost [::1] port 22. debug: Connection established. debug: Remote protocol version 1.99, remote software version OpenSSH_2.2.0 debug: Local version string SSH-1.5-OpenSSH_2.2.0 debug: Waiting for server public key. debug: Received server public key (768 bits) and host key (1024 bits). debug: Forcing accepting of host key for loopback/localhost. debug: Encryption type: 3des debug: Sent encrypted session key. debug: Installing crc compensation attack detector. debug: Received encrypted confirmation. debug: Trying RSA authentication via agent with 'brian@hak.lan.Awfulhak.org' debug: Received RSA challenge from server. debug: Sending response to RSA challenge. debug: Remote: RSA authentication accepted. debug: RSA authentication accepted by server. debug: Requesting pty. debug: Requesting X11 forwarding with authentication spoofing. debug: Requesting authentication agent forwarding. debug: Requesting shell. debug: Entering interactive session. Last login: Sat Sep 16 13:54:54 2000 from localhost Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT (HAK) #1: Sat Sep 16 13:24:21 BST 2000 sshd in realloc():Received disconnect: Command terminated on signal 6. debug: Calling cleanup 0x804db94(0x0) debug: Calling cleanup 0x8056fe4(0x0) hak:~ $ The client works ok connecting to older machines. -- 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 Sat Sep 16 6:15:32 2000 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 5D55B37B424 for ; Sat, 16 Sep 2000 06:15:26 -0700 (PDT) Received: (qmail 22295 invoked by uid 0); 16 Sep 2000 13:15:24 -0000 Received: from p3ee21661.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.97) by mail.gmx.net with SMTP; 16 Sep 2000 13:15:24 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id KAA30413; Sat, 16 Sep 2000 10:04:47 +0200 Date: Sat, 16 Sep 2000 10:04:47 +0200 From: Gerhard Sittig To: current@FreeBSD.org, hackers@freebsd.org Subject: Re: superduperopen(3) (was: Fdescfs updates--coming to a devfs near you!) Message-ID: <20000916100447.I27034@speedy.gsinet> Mail-Followup-To: current@FreeBSD.org, hackers@freebsd.org References: <200009160249.e8G2n3n02415@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200009160249.e8G2n3n02415@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Sat, Sep 16, 2000 at 03:49:02AM +0100 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG using Brian's post since I don't have the original around ... On Sat, Sep 16, 2000 at 03:49 +0100, Brian Somers wrote: > > [ attribution missing, is it Poul-Henning Kamp's text? ] > > > The majority of these programs could be handled by adding > > knowledge of "-" as a magic filename to fopen(3). > [.....] > > At the same time I would really love if we implemented "|.*" > > to mean "do an popen(3)" instead. The only reasonable way to provide this functionality to apps not wanting to reinvent it themselves without breaking those who feel that files should be just that - files - is a _new_ function next to fopen(3) named some rather alerting way like superduperopen(3) with flags like SDO_KNOWS_STDIN, SDO_CAN_PIPEFROM, SDO_CAN_PIPEINTO and whatever other extension you can think of. 32 of these new behaviour patterns should suffice for quite a while. :) This will collapse the "-" recognition and handling logic in existing programs to passing a simple flag to a different function (with only one more int parameter compared to fopen(3)) and leave those alone who just want to fopen(3) any file. And when the options set is extended no app will "inherit" unwanted and unexpected features turning out to be holes. Unless there's a SDO_DO_ANY_PRESENT_AND_FUTURE_MAGIC flag passed with a value of 0xffffffff. But authors doing so will get what they deserve. :> One could even think of switching to the new function "to be ready" and passing a SDO_DONT_DO_ANY_MAGIC flag. How much sense does it make to think about implementing tee and select methods this way? Like "open file1 and file2 and write to both of them whatever I give to you" and "give me data coming in from whatever file is in this set"? The only problem is to determine available characters to separate these names. '+' as well as ':', ',' and ';' are perfectly valid characters for constructing filenames. '&' seems to be too, but could be used rarely enough. And the split upon these new separators actually should be done only when the appropriate SDO_ flags are passed. e.g. superduperopen("file1&file2", "a+", SDO_TEEFILES) superduperopen("file1&file2", "r" , SDO_SELECT) Semantics could be braindead simple: TEE will just dup any data to every file specified and SELECT will have implicit priorities since there's no logic doing round robing or something. This will suffice for randomly filled input channels being fed more alternatively rather than concurrently. Of course the mode parameter from fopen(3) and the magicmask parameter from superduperopen(3) (i.e. the second and third parameters) have to pass certain checks. Nobody should try to read from "|command". And I cannot see any use for "write to whatever descriptor is ready to write to first" as would result from "w" and SDO_SELECT. Feel free to correct the flag's data type. I have the feeling not all int's have 32bits. :) Some other means of storage might be more appropriate while still being easy to combine and to pass to the function. But I feel strings like "STD,PIPE,TEE" are harder to parse and single character notation like the "wt" mode flags are harder to find (think of) and to read (in terms of eyeballing the source code) for the sdo case. 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 Sat Sep 16 7:40:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix3.free.fr (postfix3.free.fr [212.27.32.22]) by hub.freebsd.org (Postfix) with ESMTP id 133D037B423 for ; Sat, 16 Sep 2000 07:40:17 -0700 (PDT) Received: from titine.fr.eu.org (toulouse-2-6-169.dial.proxad.net [213.228.6.169]) by postfix3.free.fr (Postfix) with ESMTP id B69BA86C27 for ; Sat, 16 Sep 2000 16:40:14 +0200 (CEST) Received: by titine.fr.eu.org (Postfix, from userid 1000) id 7096D14C02; Sat, 16 Sep 2000 16:39:27 +0200 (CEST) X-Attribution: Jaco To: current@FreeBSD.ORG Subject: Builkernel failure From: Eric Jacoboni Date: 16 Sep 2000 16:39:27 +0200 Message-ID: <87k8ccs8o0.fsf@titine.fr.eu.org> Lines: 40 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From a fresh cvsup on a DELL i3500 laptop: 'make buildworld' runs ok... 'make KERNEL=ALEX buildkernel' (but that's the same with GENERIC) fails while building modules : =-=-=-= (...) objcopy --strip-debug kernel.debug kernel cd /usr/src/sys/modules && \ env MAKEOBJDIRPREFIX=/home/obj/usr/src/sys/ALEX/modules \ KMODDIR=/usr/obj/usr/src/i386/boot/kernel make obj all ===> 3dfx ===> accf_data (...) ===> mly ===> splash ===> splash/bmp ===> splash/pcx ===> streams ===> svr4 ===> vesa ===> wi ===> 3dfx make: don't know how to make @/i386/linux/linux_ioctl.h. Stop *** Error code 2 Stop in /usr/src/sys/modules *** Error code 1 Stop in /home/obj/usr/src/sys/ALEX *** Error code 1 =-=-=-= Did i miss something ? (i speak of building the kernel, not of installing it...) -- Éric Jacoboni, né il y a 1272478053 secondes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 7:41:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 3A7A237B424; Sat, 16 Sep 2000 07:41:45 -0700 (PDT) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #20) id 13aJ9w-0001xN-00; Sat, 16 Sep 2000 16:41:40 +0200 Received: from a2cae.pppool.de ([213.6.44.174] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.16 #21) id 13aJ9v-00058f-00; Sat, 16 Sep 2000 16:41:40 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8GEfIn01529; Sat, 16 Sep 2000 16:41:19 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009161441.e8GEfIn01529@Magelan.Leidinger.net> Date: Sat, 16 Sep 2000 16:41:16 +0200 (CEST) From: Alexander Leidinger Subject: SMPng & vidcontrol on UP system To: current@freebsd.org Cc: yokota@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, after updating to an actual -CURRENT (Sep 16, ~11am CEST, from german mirror) the system hangs hard (no keyboard control, no visible response, no hard disk activity, I had to toggle the power switch) if vidcontrol tries to switch to a VESA_132x60 console. Without allscreens_flags everything is fine. Bye, Alexander. -- Speak softly and carry a cellular phone. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 8: 5:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id B75D937B422; Sat, 16 Sep 2000 08:05:18 -0700 (PDT) Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #20) id 13aJWn-0003tB-00; Sat, 16 Sep 2000 17:05:17 +0200 Received: from a2f26.pppool.de ([213.6.47.38] helo=Magelan.Leidinger.net) by mx2.freenet.de with esmtp (Exim 3.16 #20) id 13aJWn-0000b8-00; Sat, 16 Sep 2000 17:05:17 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8GEnCn01662; Sat, 16 Sep 2000 16:49:13 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009161449.e8GEnCn01662@Magelan.Leidinger.net> Date: Sat, 16 Sep 2000 16:49:10 +0200 (CEST) From: Alexander Leidinger Subject: updated OpenSSH & pam_ssh, the old bug is back To: current@freebsd.org Cc: kris@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, after the update of OpenSSH xdm crashes if I enable pam_ssh in pam.conf. I fixed this in the old version, but it seems the bug is back. I have a look at it and try to produce a patch again. Bye, Alexander. -- Yes, I've heard of "decaf." What's your point? http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 8: 5:24 2000 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 0FEA237B423; Sat, 16 Sep 2000 08:05:19 -0700 (PDT) Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #20) id 13aJWo-0002M0-00; Sat, 16 Sep 2000 17:05:18 +0200 Received: from a2f26.pppool.de ([213.6.47.38] helo=Magelan.Leidinger.net) by mx2.freenet.de with esmtp (Exim 3.16 #20) id 13aJWo-0000b8-00; Sat, 16 Sep 2000 17:05:18 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8GF13n01686; Sat, 16 Sep 2000 17:01:04 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009161501.e8GF13n01686@Magelan.Leidinger.net> Date: Sat, 16 Sep 2000 17:01:02 +0200 (CEST) From: Alexander Leidinger Subject: 100% system time? (SMPng on UP system) To: current@freebsd.org Cc: jhb@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, dnetc runns with idprio 31, system cvsupped around Sep 16, 11 CEST from a german mirror (it contains the idle fixes: src/sys/kern/kern_idle.c,v 1.4), complete build{world,kernel}. ---snip--- last pid: 1666; load averages: 1.10, 1.11, 1.03 up 0+00:51:21 16:54:14 71 processes: 3 running, 67 sleeping, 1 zombie CPU states: 0.0% user, 0.0% nice, 100% system, 0.0% interrupt, 0.0% idle Mem: 61M Active, 16M Inact, 27M Wired, 6944K Cache, 22M Buf, 10M Free Swap: 266M Total, 266M Free kill PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 355 nobody 48 52 772K 416K RUN 40:16 91.11% 91.11% dnetc 1209 root 2 0 65448K 28492K select 1:05 2.25% 2.25% XF86_SVGA ---snip--- and with the idprio'd dnetc stopped: ---snip--- last pid: 1670; load averages: 0.80, 1.05, 1.02 up 0+00:52:43 16:55:36 72 processes: 2 running, 68 sleeping, 1 stopped, 1 zombie CPU states: 0.0% user, 0.0% nice, 4.3% system, 0.0% interrupt, 95.7% idle Mem: 62M Active, 16M Inact, 27M Wired, 6944K Cache, 22M Buf, 8568K Free Swap: 266M Total, 266M Free kill PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 355 nobody 48 52 772K 416K STOP 41:09 38.38% 38.38% dnetc 1209 root 2 0 66576K 29624K select 1:09 1.71% 1.71% XF86_SVGA ---snip--- Bye, Alexander. -- Speak softly and carry a cellular phone. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 8:24:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id BA3FF37B43C for ; Sat, 16 Sep 2000 08:24:41 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id IAA05091 for freebsd-current@freebsd.org; Sat, 16 Sep 2000 08:30:06 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200009161530.IAA05091@troutmask.apl.washington.edu> Subject: upgrade libgmp? To: FreeBSD Current Date: Sat, 16 Sep 2000 08:30:06 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Before I jump in and attempt to do an upgrade of libgmp, I thought I'd asked if anyone else has endured this joy? Note, src/contrib/libgmp is at version 2.0.x and it is 3+ years old. The newest version is at 3.1. The Changelog indicates that there are numerous fixes and enhancements over 2.0.x. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 9: 8:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id F2CCC37B423; Sat, 16 Sep 2000 09:08:40 -0700 (PDT) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #20) id 13aKW8-0000pH-00; Sat, 16 Sep 2000 18:08:40 +0200 Received: from a3822.pppool.de ([213.6.56.34] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.16 #21) id 13aKW7-00067y-00; Sat, 16 Sep 2000 18:08:39 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8GG7en02911; Sat, 16 Sep 2000 18:07:41 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009161607.e8GG7en02911@Magelan.Leidinger.net> Date: Sat, 16 Sep 2000 18:07:38 +0200 (CEST) From: Alexander Leidinger Subject: patch for openssh To: kris@freebsd.org Cc: current@freebsd.org MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY="0-1804289383-969120463=:2908" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-1804289383-969120463=:2908 Content-Type: TEXT/plain; charset=us-ascii Hi, I tried to find the bug which prevents me from using pam_ssh, but I was not able to find it so far (output from xdm: "xdm error (pid 2530): Unknown session exit code 2816 from process 2727", I assume proc 2727 is "ssh-agent"). But I think I found some other bugs, please have a look at the attached diff. Bye, Alexander. -- The dark ages were caused by the Y1K problem. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E --0-1804289383-969120463=:2908 Content-Type: TEXT/plain; CHARSET=US-ASCII Content-Disposition: attachment; filename="openssh.diff" Index: authfd.c =================================================================== RCS file: /big/FreeBSD-CVS/src/crypto/openssh/authfd.c,v retrieving revision 1.6 diff -u -r1.6 authfd.c --- authfd.c 2000/09/10 09:35:37 1.6 +++ authfd.c 2000/09/16 15:27:25 @@ -178,7 +178,7 @@ if (sock < 0) return NULL; - auth = xmalloc(sizeof(*auth)); + auth = xmalloc(sizeof(AuthenticationConnection)); auth->fd = sock; buffer_init(&auth->identities); auth->howmany = 0; Index: ssh-agent.c =================================================================== RCS file: /big/FreeBSD-CVS/src/crypto/openssh/ssh-agent.c,v retrieving revision 1.7 diff -u -r1.7 ssh-agent.c --- ssh-agent.c 2000/09/10 09:35:38 1.7 +++ ssh-agent.c 2000/09/16 15:57:22 @@ -571,7 +571,7 @@ break; case AUTH_SOCKET: if (FD_ISSET(sockets[i].fd, readset)) { - slen = sizeof(sunaddr); + slen = SUN_LEN(&sunaddr)+1; sock = accept(sockets[i].fd, (struct sockaddr *) & sunaddr, &slen); if (sock < 0) { perror("accept from AUTH_SOCKET"); @@ -741,7 +741,8 @@ memset(&sunaddr, 0, sizeof(sunaddr)); sunaddr.sun_family = AF_UNIX; strlcpy(sunaddr.sun_path, socket_name, sizeof(sunaddr.sun_path)); - if (bind(sock, (struct sockaddr *) & sunaddr, sizeof(sunaddr)) < 0) { + sunaddr.sun_len = SUN_LEN(&sunaddr)+1; + if (bind(sock, (struct sockaddr *) & sunaddr, sunaddr.sun_len) < 0) { perror("bind"); cleanup_exit(1); } --0-1804289383-969120463=:2908-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 9:37:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id B1A6837B42C; Sat, 16 Sep 2000 09:37:16 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id JAA19603; Sat, 16 Sep 2000 09:36:20 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009161636.JAA19603@pike.osd.bsdi.com> Subject: Re: 100% system time? (SMPng on UP system) In-Reply-To: <200009161501.e8GF13n01686@Magelan.Leidinger.net> from Alexander Leidinger at "Sep 16, 2000 05:01:02 pm" To: Alexander Leidinger Date: Sat, 16 Sep 2000 09:36:20 -0700 (PDT) Cc: current@freebsd.org, jhb@freebsd.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Leidinger wrote: > Hi, > > dnetc runns with idprio 31, system cvsupped around Sep 16, 11 CEST from > a german mirror (it contains the idle fixes: src/sys/kern/kern_idle.c,v > 1.4), complete build{world,kernel}. None of the CPU states from vmmeter are close to accurate on UP x86 systems at the moment because statclock() doesn't have a valid stack frame to work with. SMP is slightly more accurate as we get all the stats on the other CPU's correct. This is on the todo list to fix, but it is merely cosmetic, so it is farther down on the list than, say, finishing up threading interrupts on the alpha. :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "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 Sat Sep 16 9:39: 4 2000 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 813E837B422 for ; Sat, 16 Sep 2000 09:38:58 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id DAA27322; Sun, 17 Sep 2000 03:38:36 +1100 Date: Sun, 17 Sep 2000 03:38:33 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Bill Fumerola Cc: "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: Call for libtermcap ressurection from the dead In-Reply-To: <20000916022836.X47559@jade.chc-chimes.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 Sat, 16 Sep 2000, Bill Fumerola wrote: > On Sat, Sep 16, 2000 at 04:23:42AM +0400, Andrey A. Chernov wrote: > > Avdantages: > > > > 1) We'll be 100%-compatible with all libtermcap programs again. > > 2) Save LOTS of space for static binaries since libtermcap is extremally > > small. > > > > Opinions? Fine with me, provided you handle any problems with mixing the libraries. I think "-ltermcap -lcurses" should somehow use the curses interfaces despite termcap being first. > I don't object. The namespace collisions in src/games with ncurses functions > are really, really bad, and though just not linking to ncurses is sort of a hackish > fix, this would at least mask the problems until further into the future when > I have time to change function names. :-> There are also a problem with the ospeed variable outside of src/games: ===> usr.bin/top /usr/libexec/elf/ld: Warning: size of symbol `ospeed' changed from 2 to 4 in lib_tputs.o top/screen.c has "short ospeed" although it doesn't actually use ospeed directly. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 9:47:24 2000 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 E3DA337B423 for ; Sat, 16 Sep 2000 09:47:20 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e8GGl7l05904; Sat, 16 Sep 2000 20:47:07 +0400 (MSD) (envelope-from ache) Date: Sat, 16 Sep 2000 20:47:07 +0400 From: "Andrey A. Chernov" To: Bruce Evans Cc: Bill Fumerola , current@FreeBSD.ORG Subject: Re: Call for libtermcap ressurection from the dead Message-ID: <20000916204707.B5772@nagual.pp.ru> References: <20000916022836.X47559@jade.chc-chimes.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 bde@zeta.org.au on Sun, Sep 17, 2000 at 03:38:33AM +1100 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 17, 2000 at 03:38:33AM +1100, Bruce Evans wrote: > Fine with me, provided you handle any problems with mixing the libraries. > I think "-ltermcap -lcurses" should somehow use the curses interfaces > despite termcap being first. Yes, I fix this occurances recently just for purity reasons, "-lcurses -ltermcap" peek up all needed functions from curses first, "-ltermcap -lcurses" is never used. > > I don't object. The namespace collisions in src/games with ncurses functions > > are really, really bad, and though just not linking to ncurses is sort of a hackish > > fix, this would at least mask the problems until further into the future when > > I have time to change function names. :-> > > There are also a problem with the ospeed variable outside of src/games: > > ===> usr.bin/top > /usr/libexec/elf/ld: Warning: size of symbol `ospeed' changed from 2 to 4 in lib_tputs.o > > top/screen.c has "short ospeed" although it doesn't actually use ospeed > directly. Yes. BTW, namespace pollution and ospeed are not only problems, some other subtle problems exists. -- 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 Sat Sep 16 10: 4:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id C9B4D37B423 for ; Sat, 16 Sep 2000 10:04:12 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id NAA58305 for ; Sat, 16 Sep 2000 13:04:17 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Sat, 16 Sep 2000 13:04:17 -0400 (EDT) From: "Brandon D. Valentine" To: current@freebsd.org Subject: PRE_SMPNG snap Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to request that someone with access to ftp://current.freebsd.org build a snapshot release based entirely on the PRE_SMPNG CVS branch so those of us wishing to install current will have a better starting point. The snaps currently being built come directly from HEAD and hence are ridden with the instability inherent in current at the moment. It would be nice if there was one snap built directly from the branch point and put in ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/PRE_SMPNG or something to that effect. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 10:25:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 663DA37B424 for ; Sat, 16 Sep 2000 10:25:45 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id KAA20319; Sat, 16 Sep 2000 10:25:07 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009161725.KAA20319@pike.osd.bsdi.com> Subject: Re: PRE_SMPNG snap In-Reply-To: from "Brandon D. Valentine" at "Sep 16, 2000 01:04:17 pm" To: "Brandon D. Valentine" Date: Sat, 16 Sep 2000 10:25:07 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brandon D. Valentine wrote: > I would like to request that someone with access to > ftp://current.freebsd.org build a snapshot release based entirely on the > PRE_SMPNG CVS branch so those of us wishing to install current will have > a better starting point. The snaps currently being built come directly > from HEAD and hence are ridden with the instability inherent in current > at the moment. It would be nice if there was one snap built directly > from the branch point and put in > ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/PRE_SMPNG or > something to that effect. Err, AFAIK, the only instability atm is that under heavy load some ahc controllers seem to hang (or possibly the ahc driver is getting out of sorts and hanging.) However, the problem is not so bad that you can't build world in at most 2 boots, and it also seems to only manifest itself on SMP machines AFAIK. The only other bugs at this point are in cosmetic statistics, and in catching the alpha arch up to the x86 arch. If you have other stability problems we'd appreciate some bug reports. :-P -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "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 Sat Sep 16 10:40:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9834737B422 for ; Sat, 16 Sep 2000 10:40:05 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id KAA20611; Sat, 16 Sep 2000 10:39:28 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009161739.KAA20611@pike.osd.bsdi.com> Subject: Re: PRE_SMPNG snap In-Reply-To: <200009161725.KAA20319@pike.osd.bsdi.com> from John Baldwin at "Sep 16, 2000 10:25:07 am" To: John Baldwin Date: Sat, 16 Sep 2000 10:39:28 -0700 (PDT) Cc: "Brandon D. Valentine" , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > Brandon D. Valentine wrote: > > I would like to request that someone with access to > > ftp://current.freebsd.org build a snapshot release based entirely on the > > PRE_SMPNG CVS branch so those of us wishing to install current will have > > a better starting point. The snaps currently being built come directly > > from HEAD and hence are ridden with the instability inherent in current > > at the moment. It would be nice if there was one snap built directly > > from the branch point and put in > > ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/PRE_SMPNG or > > something to that effect. > > Err, AFAIK, the only instability atm is that under heavy load some ahc > controllers seem to hang (or possibly the ahc driver is getting out of > sorts and hanging.) However, the problem is not so bad that you can't > build world in at most 2 boots, and it also seems to only manifest > itself on SMP machines AFAIK. The only other bugs at this point are > in cosmetic statistics, and in catching the alpha arch up to the x86 > arch. If you have other stability problems we'd appreciate some bug > reports. :-P Ok, to be fair, I've just found out that static hints seem to be broken possibly because some variable isn't initialized to 0, but that can be easily worked around with dynamic hints until that is fixed. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "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 Sat Sep 16 11:30:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from volatile.chemicals.tacorp.com (ci391991-a.grnvle1.sc.home.com [24.9.31.75]) by hub.freebsd.org (Postfix) with ESMTP id 78C4F37B423 for ; Sat, 16 Sep 2000 11:30:38 -0700 (PDT) Received: (from morganw@localhost) by volatile.chemicals.tacorp.com (8.11.0/8.11.0) id e8GIUYM14107; Sat, 16 Sep 2000 14:30:34 -0400 (EDT)?g (envelope-from morganw)ś Date: Sat, 16 Sep 2000 14:30:33 -0400 (EDT) From: Wesley Morgan To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: PRE_SMPNG snap In-Reply-To: <200009161725.KAA20319@pike.osd.bsdi.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 Sat, 16 Sep 2000, John Baldwin wrote: > Err, AFAIK, the only instability atm is that under heavy load some ahc > controllers seem to hang (or possibly the ahc driver is getting out of > sorts and hanging.) However, the problem is not so bad that you can't > build world in at most 2 boots, and it also seems to only manifest > itself on SMP machines AFAIK. The only other bugs at this point are > in cosmetic statistics, and in catching the alpha arch up to the x86 > arch. If you have other stability problems we'd appreciate some bug > reports. :-P Are there any filesystem-hosing issues with the "instability"? I'll try anything if my FS is in no danger :) -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ wesleymorgan@home.com _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 11:34:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 4E9D137B42C for ; Sat, 16 Sep 2000 11:34:15 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id LAA21961; Sat, 16 Sep 2000 11:32:58 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009161832.LAA21961@pike.osd.bsdi.com> Subject: Re: PRE_SMPNG snap In-Reply-To: from Wesley Morgan at "Sep 16, 2000 02:30:33 pm" To: Wesley Morgan Date: Sat, 16 Sep 2000 11:32:58 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wesley Morgan wrote: > On Sat, 16 Sep 2000, John Baldwin wrote: > > > Err, AFAIK, the only instability atm is that under heavy load some ahc > > controllers seem to hang (or possibly the ahc driver is getting out of > > sorts and hanging.) However, the problem is not so bad that you can't > > build world in at most 2 boots, and it also seems to only manifest > > itself on SMP machines AFAIK. The only other bugs at this point are > > in cosmetic statistics, and in catching the alpha arch up to the x86 > > arch. If you have other stability problems we'd appreciate some bug > > reports. :-P > > Are there any filesystem-hosing issues with the "instability"? I'll try > anything if my FS is in no danger :) Well, in all cases that I've seen, it was during a buildworld, so if I lost a file in /usr/obj I didn't really care, nor did I notice. I do know that fsck -p finished w/o any errors or need for manual intervention when I rebooted the machines. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "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 Sat Sep 16 12:32:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 424B637B422 for ; Sat, 16 Sep 2000 12:32:26 -0700 (PDT) Received: (qmail 12996 invoked from network); 16 Sep 2000 19:32:22 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 16 Sep 2000 19:32:22 -0000 Date: Sun, 17 Sep 2000 06:32:19 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Alexander Leidinger Cc: current@FreeBSD.ORG, jhb@FreeBSD.ORG Subject: Re: 100% system time? (SMPng on UP system) In-Reply-To: <200009161501.e8GF13n01686@Magelan.Leidinger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 16 Sep 2000, Alexander Leidinger wrote: > dnetc runns with idprio 31, system cvsupped around Sep 16, 11 CEST from > a german mirror (it contains the idle fixes: src/sys/kern/kern_idle.c,v > 1.4), complete build{world,kernel}. > > ---snip--- > last pid: 1666; load averages: 1.10, 1.11, 1.03 up 0+00:51:21 16:54:14 Perhaps it really is a system process :-[. idprio on a pure cpu hog prevents other user processes from running like a system process might do: idprio 31 sh -c "while :; do :; done" System processes actually hang the entire system until they complete: dd if=/dev/random of=/dev/null bs=10m count=1 This takes 32 seconds on a Celeron 366 overclocked to 523, during which time no other processes, including interrupt tasks, can run. This is because the supergiant lock prevents context switching while the i/o is being done. There is nothing special about /dev/random here except that it has a low transfer rate. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 12:48:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 16A5C37B423 for ; Sat, 16 Sep 2000 12:48:19 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id PAA59871; Sat, 16 Sep 2000 15:48:23 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Sat, 16 Sep 2000 15:48:23 -0400 (EDT) From: "Brandon D. Valentine" To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: PRE_SMPNG snap In-Reply-To: <200009161725.KAA20319@pike.osd.bsdi.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 Sat, 16 Sep 2000, John Baldwin wrote: >Err, AFAIK, the only instability atm is that under heavy load some ahc >controllers seem to hang (or possibly the ahc driver is getting out of >sorts and hanging.) However, the problem is not so bad that you can't I've had a ton of experience with ahc lately, as those of you who follow -questions, -stable, or -scsi know. r1.48 of aic7xxx.c is horribly broken. I can't get current snaps after that revision was committed to even boot on machines which use aic7892 or 29160 controllers. Every boot it panic's immediately after probing the scsi controllers. I haven't had time to review just what dfr's changes in 1.48 did or why they might be causing this, but it doesn't look pretty. There are some pretty major diff's between 1.47 and 1.48. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 13: 8:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom2-097.telepath.com [216.14.2.97]) by hub.freebsd.org (Postfix) with SMTP id 617C737B424 for ; Sat, 16 Sep 2000 13:08:46 -0700 (PDT) Received: (qmail 22470 invoked by uid 100); 16 Sep 2000 20:01:28 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14787.53656.382549.966793@guru.mired.org> Date: Sat, 16 Sep 2000 15:01:28 -0500 (CDT) To: "Brandon D. Valentine" Cc: current@FreeBSD.ORG Subject: Re: PRE_SMPNG snap In-Reply-To: References: <200009161725.KAA20319@pike.osd.bsdi.com> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brandon D. Valentine writes: > On Sat, 16 Sep 2000, John Baldwin wrote: > >Err, AFAIK, the only instability atm is that under heavy load some ahc > >controllers seem to hang (or possibly the ahc driver is getting out of > >sorts and hanging.) However, the problem is not so bad that you can't > I've had a ton of experience with ahc lately, as those of you who follow > -questions, -stable, or -scsi know. r1.48 of aic7xxx.c is horribly > broken. I can't get current snaps after that revision was committed to > even boot on machines which use aic7892 or 29160 controllers. How about 7890 controllers? I was about to step from PRE_SMPNG back to -current, but you've just made me nervous! Thanx, ; Sat, 16 Sep 2000 13:18:08 -0700 (PDT) Received: from anakin - 63.15.0.111 by email.msn.com with Microsoft SMTPSVC; Sat, 16 Sep 2000 13:17:20 -0700 From: "James Johnson" To: "Brandon D. Valentine" , Subject: Questions about PRE_SMPNG (Was PRE_SMPNG snap) Date: Sat, 16 Sep 2000 13:16:04 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can someone explain why we have a PRE_SMPNG tag? Sure there may be some issues with SMP in -CURRENT right now, however simply avoiding running the code is not going to get those issues fixed. -----Original Message----- From: owner-freebsd-current@FreeBSD.ORG [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Brandon D. Valentine Sent: Saturday, September 16, 2000 10:04 AM To: current@freebsd.org Subject: PRE_SMPNG snap I would like to request that someone with access to ftp://current.freebsd.org build a snapshot release based entirely on the PRE_SMPNG CVS branch so those of us wishing to install current will have a better starting point. The snaps currently being built come directly from HEAD and hence are ridden with the instability inherent in current at the moment. It would be nice if there was one snap built directly from the branch point and put in ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/PRE_SMPNG or something to that effect. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 13:35:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id C02C037B422 for ; Sat, 16 Sep 2000 13:35:40 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id QAA60315; Sat, 16 Sep 2000 16:35:45 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Sat, 16 Sep 2000 16:35:45 -0400 (EDT) From: "Brandon D. Valentine" To: Mike Meyer Cc: current@FreeBSD.ORG Subject: Re: PRE_SMPNG snap In-Reply-To: <14787.53656.382549.966793@guru.mired.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 On Sat, 16 Sep 2000, Mike Meyer wrote: >Brandon D. Valentine writes: >> On Sat, 16 Sep 2000, John Baldwin wrote: >> >Err, AFAIK, the only instability atm is that under heavy load some ahc >> >controllers seem to hang (or possibly the ahc driver is getting out of >> >sorts and hanging.) However, the problem is not so bad that you can't >> I've had a ton of experience with ahc lately, as those of you who follow >> -questions, -stable, or -scsi know. r1.48 of aic7xxx.c is horribly >> broken. I can't get current snaps after that revision was committed to >> even boot on machines which use aic7892 or 29160 controllers. > >How about 7890 controllers? I was about to step from PRE_SMPNG back to >-current, but you've just made me nervous! I don't have any 7890s to test on. However, if you are already running PRE_SMPNG then you should have r1.48 since it was tagged with that as well. Go for it. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 14:31: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 8ADBB37B43C for ; Sat, 16 Sep 2000 14:30:59 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8GLUp605814; Sat, 16 Sep 2000 14:30:52 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: "Brandon D. Valentine" Cc: current@FreeBSD.ORG Subject: Re: PRE_SMPNG snap In-Reply-To: Message from "Brandon D. Valentine" of "Sat, 16 Sep 2000 13:04:17 EDT." Date: Sat, 16 Sep 2000 14:30:51 -0700 Message-ID: <5810.969139851@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You already have that - just install one of the -current snaps from before this date. I have no plans to remove them. - Jordan > I would like to request that someone with access to > ftp://current.freebsd.org build a snapshot release based entirely on the > PRE_SMPNG CVS branch so those of us wishing to install current will have > a better starting point. The snaps currently being built come directly > from HEAD and hence are ridden with the instability inherent in current > at the moment. It would be nice if there was one snap built directly > from the branch point and put in > ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/PRE_SMPNG or > something to that effect. > > Brandon D. Valentine > -- > bandix at looksharp.net | bandix at structbio.vanderbilt.edu > "Truth suffers from too much analysis." -- Ancient Fremen Saying > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 14:32:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id A03E337B43E; Sat, 16 Sep 2000 14:32:21 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id XAA96156; Sat, 16 Sep 2000 23:32:19 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.0/8.8.8) with ESMTP id e8GMW6A00691; Sun, 17 Sep 2000 00:32:06 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sun, 17 Sep 2000 00:32:01 +0200 (CEST) From: Michael Reifenberger To: FreeBSD-Current Cc: FreeBSD-SMP Subject: Debugging -current SMPNG HANG on heavy disk-io 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, -current hangs reliable (as described in another mail) for me. For short: "tar cf /dev/null /usr/ports&; tar cf - /usr/ports | tar tf -" locks the system solid after a few minutes. The first tar itself seems to need some time longer before hang. This is verified to occure with 2 different disks (IDE). Now the questions how to debug this: - How do I get a backtrace of a specific process from within DDB? - How do I determine where the system hangs/loops fromm within DDB? - How do I get the process-list (like ps) from within gdb (postmortem) Below is a first try to debug postmortem with gdb Does this look reasonable? Something else to look? ... Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sat Sep 16 19:32:53 CEST 2000 root@nihil.plaut.de:/usr/obj/usr/src/sys/nihil Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 266615847 Hz CPU: Pentium II/Pentium II Xeon/Celeron (266.62-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 268369920 (262080K bytes) config> #flags wdc0 0xa0ffa0ff Invalid command or syntax. Type `?' for help. config> #flags wdc1 0xa0ffa0ff Invalid command or syntax. Type `?' for help. config> #iosiz npx0 196608 Invalid command or syntax. Type `?' for help. config> #irq pcic0 11 Invalid command or syntax. Type `?' for help. config> quit avail memory = 257589248 (251552K bytes) Preloaded elf kernel "kernel.ko" at 0xc03ad000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03ad0ac. Preloaded elf module "linux.ko" at 0xc03ad0fc. Preloaded elf module "linprocfs.ko" at 0xc03ad19c. Pentium Pro MTRR support enabled VESA: v2.0, 2496k memory, flags:0x0, mode table:0xc031ee42 (1000022) VESA: MagicGraph 256 AV 44K PRELIMINARY npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 4.0 irq 11 isab0: at device 5.0 on pci0 isa0: on isab0 atapci0: port 0xfe60-0xfe6f at device 5.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 5.2 irq 11 pci0: at 5.3 pci0: at 9.0 irq 11 pcic-pci0: at device 11.0 on pci0 pcic-pci1: at device 11.1 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 pps0: on ppbus0 pcic0: at port 0x3e0-0x3e1 on isa0 pcic0: Polling mode pccard0: on pcic0 pccard1: on pcic0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources pcm0: at port 0x220-0x233,0x530-0x537,0x388-0x38f,0x330-0x333,0x538-0x539 irq 5 drq 1,0 on isa0 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging limited to 100 packets/entry by default IPsec: Initialized Security Association Processing. ad0: 24207MB [49184/16/63] at ata0-master using UDMA33 ad1: 6194MB [13424/15/63] at ata1-master using UDMA33 Mounting root from ufs:/dev/ad0s1a pccard: card inserted, slot 0 panic: from debugger syncing disks... done Uptime: 3h22m40s dumping to dev #ad/0x20001, offset 2547840 dump ata0: resetting devices .. done 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:475 475 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:475 #1 0xc017aeb3 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316 #2 0xc017b255 in panic (fmt=0xc02802b4 "from debugger") at /usr/src/sys/kern/kern_shutdown.c:568 #3 0xc013b2c9 in db_panic (addr=-1071295444, have_addr=0, count=-1, modif=0xc788bd88 "") at /usr/src/sys/ddb/db_command.c:433 #4 0xc013b269 in db_command (last_cmdp=0xc02bf5b4, cmd_table=0xc02bf414, aux_cmd_tablep=0xc03002fc) at /usr/src/sys/ddb/db_command.c:333 #5 0xc013b32e in db_command_loop () at /usr/src/sys/ddb/db_command.c:455 #6 0xc013d4eb in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_trap.c:71 #7 0xc02551ca in kdb_trap (type=3, code=0, regs=0xc788beac) at /usr/src/sys/i386/i386/db_interface.c:163 #8 0xc0260fdc in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = -1070530544, tf_edi = -1070468928, tf_esi = -1070491744, tf_ebp = -947339528, tf_isp = -947339560, tf_ebx = 582, tf_edx = -1072984320, tf_ecx = 32, tf_eax = 38, tf_trapno = 3, tf_err = 0, tf_eip = -1071295444, tf_cs = 8, tf_eflags = 70, tf_esp = -1070930945, tf_ss = -1070944311}) at /usr/src/sys/i386/i386/trap.c:584 #9 0xc025542c in Debugger (msg=0xc02aafc9 "manual escape to debugger") at machine/cpufunc.h:64 #10 0xc0251f36 in scgetc (sc=0xc031f0c0, flags=2) at /usr/src/sys/dev/syscons/syscons.c:3133 #11 0xc024ef59 in sckbdevent (thiskbd=0xc0317f60, event=0, arg=0xc031f0c0) at /usr/src/sys/dev/syscons/syscons.c:634 #12 0xc0246eae in atkbd_intr (kbd=0xc0317f60, arg=0x0) at /usr/src/sys/dev/kbd/atkbd.c:462 #13 0xc026c45c in atkbd_isa_intr (arg=0xc0317f60) at /usr/src/sys/isa/atkbd_isa.c:125 #14 0xc02681a4 in ithd_loop (dummy=0x0) at /usr/src/sys/i386/isa/ithread.c:239 (kgdb) proc 35 (kgdb) bt #0 mi_switch () at /usr/src/sys/kern/kern_synch.c:953 #1 0xc017e2f0 in msleep (ident=0xc1d2fa00, mtx=0x0, priority=8, wmesg=0xc02a2c62 "inode", timo=0) at /usr/src/sys/kern/kern_synch.c:506 #2 0xc01750f2 in acquire (lkp=0xc1d2fa00, extflags=16777280, wanted=1536) at /usr/src/sys/kern/kern_lock.c:147 #3 0xc017537c in lockmgr (lkp=0xc1d2fa00, flags=16842754, interlkp=0xc9b371ec, p=0xc7874d80) at /usr/src/sys/kern/kern_lock.c:354 #4 0xc01a8ba8 in vop_stdlock (ap=0xc9608d34) at /usr/src/sys/kern/vfs_default.c:243 #5 0xc0227bd1 in ufs_vnoperate (ap=0xc9608d34) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2263 #6 0xc01b35e3 in vn_lock (vp=0xc9b37180, flags=65538, p=0xc7874d80) at vnode_if.h:840 #7 0xc01abc8b in vget (vp=0xc9b37180, flags=2, p=0xc7874d80) at /usr/src/sys/kern/vfs_subr.c:1393 #8 0xc01a6d18 in vfs_cache_lookup (ap=0xc9608df0) at /usr/src/sys/kern/vfs_cache.c:470 #9 0xc0227bd1 in ufs_vnoperate (ap=0xc9608df0) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2263 #10 0xc01a9f44 in lookup (ndp=0xc9608e6c) at vnode_if.h:52 #11 0xc01a9968 in namei (ndp=0xc9608e6c) at /usr/src/sys/kern/vfs_lookup.c:153 #12 0xc01afaa9 in lstat (p=0xc7874d80, uap=0xc9608f80) at /usr/src/sys/kern/vfs_syscalls.c:1787 #13 0xc0261aec in syscall2 (frame={tf_fs = -1071316945, tf_es = 47, tf_ds = 47, tf_edi = 134971440, tf_esi = 134971436, tf_ebp = -1077937556, tf_isp = -916418604, tf_ebx = 20, tf_edx = 134935040, tf_ecx = 134935040, tf_eax = 190, tf_trapno = 7, tf_err = 2, tf_eip = 134603604, tf_cs = 31, tf_eflags = 643, tf_esp = -1077937696, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1136 #14 0xc0255b0f in Xint0x80_syscall () #15 0x804b0cd in ?? () #16 0x804b0cd in ?? () #17 0x804b0cd in ?? () #18 0x804b0cd in ?? () #19 0x804a431 in ?? () #20 0x8052801 in ?? () #21 0x8048135 in ?? () (kgdb) up #1 0xc017e2f0 in msleep (ident=0xc1d2fa00, mtx=0x0, priority=8, wmesg=0xc02a2c62 "inode", timo=0) at /usr/src/sys/kern/kern_synch.c:506 506 mi_switch(); (kgdb) up #2 0xc01750f2 in acquire (lkp=0xc1d2fa00, extflags=16777280, wanted=1536) at /usr/src/sys/kern/kern_lock.c:147 147 error = tsleep(lkp, lkp->lk_prio, lkp->lk_wmesg, lkp->lk_timo); (kgdb) up #3 0xc017537c in lockmgr (lkp=0xc1d2fa00, flags=16842754, interlkp=0xc9b371ec, p=0xc7874d80) at /usr/src/sys/kern/kern_lock.c:354 354 error = acquire(lkp, extflags, (LK_HAVE_EXCL | LK_WANT_EXCL)); (kgdb) up #4 0xc01a8ba8 in vop_stdlock (ap=0xc9608d34) at /usr/src/sys/kern/vfs_default.c:243 243 return (lockmgr(l, ap->a_flags, &ap->a_vp->v_interlock, ap->a_p)); (kgdb) up #5 0xc0227bd1 in ufs_vnoperate (ap=0xc9608d34) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2263 2263 return (VOCALL(ufs_vnodeop_p, ap->a_desc->vdesc_offset, ap)); (kgdb) up #6 0xc01b35e3 in vn_lock (vp=0xc9b37180, flags=65538, p=0xc7874d80) at vnode_if.h:840 840 rc = VCALL(vp, VOFFSET(vop_lock), &a); (kgdb) up #7 0xc01abc8b in vget (vp=0xc9b37180, flags=2, p=0xc7874d80) at /usr/src/sys/kern/vfs_subr.c:1393 1393 if ((error = vn_lock(vp, flags | LK_INTERLOCK, p)) != 0) { (kgdb) up #8 0xc01a6d18 in vfs_cache_lookup (ap=0xc9608df0) at /usr/src/sys/kern/vfs_cache.c:470 470 error = vget(vp, LK_EXCLUSIVE, p); (kgdb) up #9 0xc0227bd1 in ufs_vnoperate (ap=0xc9608df0) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2263 2263 return (VOCALL(ufs_vnodeop_p, ap->a_desc->vdesc_offset, ap)); (kgdb) Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 15:27:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9E57C37B42C for ; Sat, 16 Sep 2000 15:27:40 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id PAA26908; Sat, 16 Sep 2000 15:27:02 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009162227.PAA26908@pike.osd.bsdi.com> Subject: Re: Questions about PRE_SMPNG (Was PRE_SMPNG snap) In-Reply-To: from James Johnson at "Sep 16, 2000 01:16:04 pm" To: James Johnson Date: Sat, 16 Sep 2000 15:27:02 -0700 (PDT) Cc: "Brandon D. Valentine" , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James Johnson wrote: > Can someone explain why we have a PRE_SMPNG tag? Sure there may be some > issues with SMP in -CURRENT right now, however simply avoiding running the > code is not going to get those issues fixed. It calms peoples fears, and because people asked for it. Generally, trying to allay fears about major changes that have potential for great breakage is much more work than one extra cvs command to lay down a tag. :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "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 Sat Sep 16 17:59:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 08A0237B422; Sat, 16 Sep 2000 17:58:37 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8H0wOI90602; Sun, 17 Sep 2000 10:28:24 +0930 (CST) (envelope-from grog) Date: Sun, 17 Sep 2000 10:28:24 +0930 From: Greg Lehey To: Michael Reifenberger Cc: FreeBSD-Current , FreeBSD-SMP Subject: Re: Debugging -current SMPNG HANG on heavy disk-io Message-ID: <20000917102824.C42114@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="/04w6evG8XlLl3ft" X-Mailer: Mutt 1.0i In-Reply-To: ; from root@nihil.plaut.de on Sun, Sep 17, 2000 at 12:32:01AM +0200 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii On Sunday, 17 September 2000 at 0:32:01 +0200, Michael Reifenberger wrote: > Hi, > -current hangs reliable (as described in another mail) for me. > For short: > "tar cf /dev/null /usr/ports&; tar cf - /usr/ports | tar tf -" > locks the system solid after a few minutes. > The first tar itself seems to need some time longer before hang. > This is verified to occure with 2 different disks (IDE). I've seen this on NFS a few weeks back, but I haven't followed through. In my case, I couldn't even get to the debugger. > Now the questions how to debug this: > - How do I get a backtrace of a specific process from within DDB? > - How do I determine where the system hangs/loops fromm within DDB? I can't give you answers for ddb. > - How do I get the process-list (like ps) from within gdb (postmortem) I have a macro which does this. I should commit some of them, but they're in terrible shape. I'm attaching them to this message. You'll have to modify at least .gdbinit.paths. > Below is a first try to debug postmortem with gdb > Does this look reasonable? Something else to look? > > #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:475 > 475 dumppcb.pcb_cr3 = rcr3(); > (kgdb) bt > #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:475 > #1 0xc017aeb3 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316 > #2 0xc017b255 in panic (fmt=0xc02802b4 "from debugger") > at /usr/src/sys/kern/kern_shutdown.c:568 > #3 0xc013b2c9 in db_panic (addr=-1071295444, have_addr=0, count=-1, > modif=0xc788bd88 "") at /usr/src/sys/ddb/db_command.c:433 > #4 0xc013b269 in db_command (last_cmdp=0xc02bf5b4, cmd_table=0xc02bf414, > aux_cmd_tablep=0xc03002fc) at /usr/src/sys/ddb/db_command.c:333 > #5 0xc013b32e in db_command_loop () at /usr/src/sys/ddb/db_command.c:455 > #6 0xc013d4eb in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_trap.c:71 > #7 0xc02551ca in kdb_trap (type=3, code=0, regs=0xc788beac) > at /usr/src/sys/i386/i386/db_interface.c:163 > #8 0xc0260fdc in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = -1070530544, > tf_edi = -1070468928, tf_esi = -1070491744, tf_ebp = -947339528, > tf_isp = -947339560, tf_ebx = 582, tf_edx = -1072984320, tf_ecx = 32, > tf_eax = 38, tf_trapno = 3, tf_err = 0, tf_eip = -1071295444, tf_cs = 8, > tf_eflags = 70, tf_esp = -1070930945, tf_ss = -1070944311}) > at /usr/src/sys/i386/i386/trap.c:584 > #9 0xc025542c in Debugger (msg=0xc02aafc9 "manual escape to debugger") > at machine/cpufunc.h:64 The frames above are what the system went to as the result of your debugger request. I'd also be interested to see the output of the 'icnt' macro (if this is UP machine) or 'icnt1' (if it's SMP), and 'ps' (the macro I promised above). > #10 0xc0251f36 in scgetc (sc=0xc031f0c0, flags=2) > at /usr/src/sys/dev/syscons/syscons.c:3133 > #11 0xc024ef59 in sckbdevent (thiskbd=0xc0317f60, event=0, arg=0xc031f0c0) > at /usr/src/sys/dev/syscons/syscons.c:634 > #12 0xc0246eae in atkbd_intr (kbd=0xc0317f60, arg=0x0) > at /usr/src/sys/dev/kbd/atkbd.c:462 > #13 0xc026c45c in atkbd_isa_intr (arg=0xc0317f60) > at /usr/src/sys/isa/atkbd_isa.c:125 The ones above are the keyboard interrupt handler. > #14 0xc02681a4 in ithd_loop (dummy=0x0) at /usr/src/sys/i386/isa/ithread.c:239 This is the interesting one. We appear to be looping in an interrupt handler. At this point, it would be very interesting to see the value of p->p_comm, which is the process name at the end of the ps listing. > (kgdb) proc 35 Why are you interested in this process? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=".gdbinit" source .gdbinit.kernel source .gdbinit.paths tr --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=".gdbinit.paths" # GRRR # set remotebaud 115200 set remotebaud 9600 set remotetimeout 1 set complaints 1 set print pretty # dir /src/ZAPHOD/src/sys/modules/vinum # dir /src/ZAPHOD/src/sys/i386/conf # dir /src/ZAPHOD/src/sys dir src/sys/i386/conf dir src/sys file src/sys/compile/ZAPHODng/kernel.ko.debug define asf set $file = linker_files.tqh_first set $found = 0 while ($found == 0) if (*$file->filename == 'v') set $found = 1 else set $file = $file->link.tqe_next end end shell /usr/bin/objdump --section-headers sys/modules/vinum/vinum.ko | grep ' .text' | awk '{print "add-symbol-file sys/modules/vinum/vinum.ko \$file->address+0x" $4}' > .asf source .asf end document asf Find the load address of Vinum in the kernel and add the symbols at this address end --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=".gdbinit.kernel" define xi x/10i $eip end define xs x/12x $esp end define xb x/12x $ebp end define z ni x/1i $eip end define zs si x/1i $eip end define xp printf " esp: " output/x $esp echo ( output (((int)$ebp)-(int)$esp)/4-4 printf " words on stack)\n ebp: " output/x $ebp printf "\n eip: " x/1i $eip printf "Saved ebp: " output/x *(int*)$ebp printf " (maximum of " output ((*(int*)$ebp)-(int)$ebp)/4-4 printf " parameters possible)\nSaved eip: " x/1i *(int*)($ebp+4) printf "\nParm 1 at " output/x (int) ($ebp+8) printf ": " output (char*) *(int*)($ebp+8) printf "\nParm 2 at " output/x (int) ($ebp+12) printf ": " output (char*) *(int*)($ebp+12) printf "\nParm 3 at " output/x (int) ($ebp+16) printf ": " output (char*) *(int*)($ebp+16) printf "\nParm 4 at " output/x (int) ($ebp+20) printf ": " output (char*) *(int*)($ebp+20) echo \n end document xp Show the register contents and the first four parameter words of the current frame. end define xxp printf " esp: " output/x $esp printf "\n ebp: " output/x $ebp printf "\n eip: " x/1i $eip printf "Saved ebp: " output/x *(int*)$ebp printf " (maximum of " output ((*(int*)$ebp)-(int)$ebp)/4-4 printf " parameters possible)\nSaved eip: " x/1i *(int*)($ebp+4) printf "\nParm 1 at " output/x (int) ($ebp+8) printf ": " output (char*) *(int*)($ebp+8) printf "\nParm 2 at " output/x (int) ($ebp+12) printf ": " output (char*) *(int*)($ebp+12) printf "\nParm 3 at " output/x (int) ($ebp+16) printf ": " output (char*) *(int*)($ebp+16) printf "\nParm 4 at " output/x (int) ($ebp+20) printf ": " output (char*) *(int*)($ebp+20) printf "\nParm 5 at " output/x (int) ($ebp+24) printf ": " output (char*) *(int*)($ebp+24) printf "\nParm 6 at " output/x (int) ($ebp+28) printf ": " output (char*) *(int*)($ebp+28) printf "\nParm 7 at " output/x (int) ($ebp+32) printf ": " output (char*) *(int*)($ebp+32) printf "\nParm 8 at " output/x (int) ($ebp+36) printf ": " output (char*) *(int*)($ebp+36) printf "\nParm 9 at " output/x (int) ($ebp+40) printf ": " output (char*) *(int*)($ebp+40) printf "\nParm 10 at " output/x (int) ($ebp+44) printf ": " output (char*) *(int*)($ebp+44) echo \n end document xxp Show the register contents and the first ten parameter words of the current frame. end define xp0 x/12x *(int*)$esp p *(int*)$esp p (char*)*$esp end define xp1 x/12x *(int*)($ebp+4) p *(int*)($ebp+4) p (char**)($ebp+4) end define xp2 x/12x *(int*)($ebp+8) p *(int*)($ebp+8) p *(char**)($ebp+8) end define xp3 x/12x *(int*)($ebp+12) p *(int*)($ebp+12) p (char**)($ebp+12) end define xp4 x/12x *(int*)($ebp+16) p *(int*)($ebp+16) p (char**)($ebp+16) end document xp0 Show the first parameter of current stack frame in various formats end document xp1 Show the second parameter of current stack frame in various formats end document xp2 Show the third parameter of current stack frame in various formats end document xp3 Show the fourth parameter of current stack frame in various formats end document xp4 Show the fifth parameter of current stack frame in various formats end define f0 f 0 xp end define f1 f 1 xp end define f2 f 2 xp end define f3 f 3 xp end define f4 f 4 xp end define f5 f 5 xp end document f0 Select stack frame 0 and show assembler-level details end document f1 Select stack frame 1 and show assembler-level details end document f2 Select stack frame 2 and show assembler-level details end document f3 Select stack frame 3 and show assembler-level details end document f4 Select stack frame 4 and show assembler-level details end document f5 Select stack frame 5 and show assembler-level details end document z Single step 1 instruction (over calls) and show next instruction. end document zs Single step 1 instruction (through calls) and show next instruction. end document xi List the next 10 instructions from the current IP value end document xs Show the last 12 words on stack in hex end document xb Show 12 words starting at current BP value in hex end define tr target remote /dev/cuaa0 end document tr Attach to a remote kernel via /dev/cuaa0 end set output-radix 16 define pname p (char *)curproc->p_comm end document pname Print the command name of the current process end define bpp set $bp = (struct buf *) $arg0 if $bp->b_io.bio_dev printf " Buffer at 0x%x: dev 0x%x data 0x%x bcount 0x%x blkno 0x%x resid 0x%x\n", \ $bp, \ $bp->b_io.bio_dev->si_udev, \ $bp->b_io.bio_data, \ $bp->b_io.bio_bcount, \ $bp->b_io.bio_blkno, \ $bp->b_io.bio_resid else printf " Buffer at 0x%x: dev (none) data 0x%x bcount 0x%x blkno 0x%x resid 0x%x\n", \ $bp, \ $bp->b_io.bio_data, \ $bp->b_io.bio_bcount, \ $bp->b_io.bio_blkno, \ $bp->b_io.bio_resid end printf " Command: " if $bp->b_io->bio_cmd == 1 printf "Read, " end if $bp->b_io->bio_cmd == 2 printf "Write, " end if $bp->b_io->bio_cmd == 4 printf "Delete, " end if $bp->b_io->bio_cmd == 8 printf "Format, " end printf "flags 0x%x: ", $bp->b_flags if $bp->b_flags & 0x200 printf "done " end if $bp->b_flags & 0x800 printf "error " end if $bp->b_flags & 0x40000 printf "phys " end printf "\n" end define bpl set $bp = (struct buf *) $arg0 printf "b_proc: " output $bp->b_proc printf "\nb_flags: " output $bp->b_flags printf "\nb_qindex: " output $bp->b_qindex printf "\nb_usecount: " output $bp->b_usecount printf "\nb_error: " output $bp->b_error printf "\nb_bufsize: " output $bp->b_bufsize printf "\nb_io.bio_bcount: " output $bp->b_io.bio_bcount printf "\nb_io.bio_resid: " output $bp->b_io.bio_resid printf "\nb_io.bio_dev: " output $bp->b_io.bio_dev printf "\nb_io.bio_data: " output $bp->b_io.bio_data printf "\nb_kvasize: " output $bp->b_kvasize printf "\nb_lblkno: " output $bp->b_lblkno printf "\nb_io.bio_blkno: " output $bp->b_io.bio_blkno printf "\nb_iodone: " output $bp->b_iodone printf "\nb_vp: " output $bp->b_vp printf "\nb_dirtyoff: " output $bp->b_dirtyoff printf "\nb_dirtyend: " output $bp->b_dirtyend printf "\nb_generation: " output $bp->b_generation printf "\nb_rcred: " output $bp->b_rcred printf "\nb_wcred: " output $bp->b_wcred printf "\nb_validoff: " output $bp->b_validoff printf "\nb_validend: " output $bp->b_validend printf "\nb_pblkno: " output $bp->b_pblkno printf "\nb_saveaddr: " output $bp->b_saveaddr printf "\nb_savekva: " output $bp->b_savekva printf "\nb_driver1: " output $bp->b_driver1 printf "\nb_driver2: " output $bp->b_driver2 printf "\nb_spc: " output $bp->b_spc printf "\nb_npages: " output $bp->b_npages printf "\n" end define bp bpp bp end define bpd printf "Buffer data:\n%s", (char *) bp->b_io.bio_data end document bpd Show the contents (char*) of bp->data in the current frame. end document bp Show information about the buffer header pointed to by the variable bp in the current frame. end document bpp Show summary information about the buffer header (struct bp) pointed at by the parameter. end document bpl Show detailled information about the buffer header (struct bp) pointed at by the parameter. end document bpl Show detailled information about the buffer header (struct bp) pointed at by the local variable bp. end define bx printf "\n b_vnbufs " output/x bp->b_vnbufs printf "\n b_freelist " output/x bp->b_freelist printf "\n b_act " output/x bp->b_act printf "\n b_flags " output/x bp->b_flags printf "\n b_qindex " output/x bp->b_qindex printf "\n b_usecount " output/x bp->b_usecount printf "\n b_error " output/x bp->b_error printf "\n b_bufsize " output/x bp->b_bufsize printf "\n b_io.bio_bcount " output/x bp->b_io.bio_bcount printf "\n b_io.bio_resid " output/x bp->b_io.bio_resid printf "\n b_io.bio_dev " output/x bp->b_io.bio_dev printf "\n b_io.bio_data " output/x bp->b_io.bio_data printf "\n b_kvasize " output/x bp->b_kvasize printf "\n b_io.bio_blkno " output/x bp->b_io.bio_blkno printf "\n b_iodone_chain " output/x bp->b_iodone_chain printf "\n b_vp " output/x bp->b_vp printf "\n b_dirtyoff " output/x bp->b_dirtyoff printf "\n b_validoff " output/x bp->b_validoff echo \n end define ddb set boothowto=0x80000000 s end document ddb Switch back to ddb. end define ps set $nproc = nprocs set $aproc = allproc.lh_first set $proc = allproc.lh_first printf " pid proc addr uid pri ppid pgrp flag stat comm wchan\n" while (--$nproc >= 0) set $pptr = $proc.p_pptr if ($pptr == 0) set $pptr = $proc end if ($proc.p_stat) printf "%5d %08x %08x %4d ", \ $proc.p_pid, $aproc, \ $proc.p_addr, $proc.p_cred->p_ruid if ($proc.p_rtprio.type == 3) printf "%3d ", $pptr->p_priority else printf "%3d*", $proc.p_rtprio.prio end printf "%5d %5d %06x %d %-10s ", \ $pptr->p_pid, $proc.p_pgrp->pg_id, $proc.p_flag, $proc.p_stat, \ &$proc.p_comm[0] if ($proc.p_wchan) if ($proc.p_wmesg) printf "%s ", $proc.p_wmesg end printf "%x", $proc.p_wchan end printf "\n" end set $aproc = $proc.p_list.le_next if ($aproc == 0 && $nproc > 0) set $aproc = zombproc end set $proc = $aproc end end document ps "ps" -- when kernel debugging, type out a ps-like listing of active processes. end define pregs set $nproc = nprocs set $aproc = allproc.lh_first set $proc = allproc.lh_first while (--$nproc >= 0) set $pptr = $proc.p_pptr if ($proc->p_pid == $arg0) set $pcba = $pptr->p_addr->u_pcb printf "eax\t%d\t%x", $pcba->pcb_eax, $pcba->pcb_eax printf "ecx\t%d\t%x", $pcba->pcb_ecx, $pcba->pcb_ecx printf "edx\t%d\t%x", $pcba->pcb_edx, $pcba->pcb_edx printf "ebx\t%d\t%x", $pcba->pcb_ebx, $pcba->pcb_ebx printf "esp\t%d\t%x", $pcba->pcb_esp, $pcba->pcb_esp printf "ebp\t%d\t%x", $pcba->pcb_ebp, $pcba->pcb_ebp printf "esi\t%d\t%x", $pcba->pcb_esi, $pcba->pcb_esi printf "edi\t%d\t%x", $pcba->pcb_edi, $pcba->pcb_edi printf "eip\t%d\t%x", $pcba->pcb_eip, $pcba->pcb_eip printf "eflags\t%d\t%x", $pcba->pcb_eflags, $pcba->pcb_eflags printf "cs\t%d\t%x", $pcba->pcb_cs, $pcba->pcb_cs printf "ss\t%d\t%x", $pcba->pcb_ss, $pcba->pcb_ss printf "ds\t%d\t%x", $pcba->pcb_ds, $pcba->pcb_ds printf "es\t%d\t%x", $pcba->pcb_es, $pcba->pcb_es printf "fs\t%d\t%x", $pcba->pcb_fs, $pcba->pcb_fs printf "gs\t%d\t%x", $pcba->pcb_gs, $pcba->pcb_gs x/1i $pcba->pcb_eip set $nproc = 0 end set $aproc = $proc.p_list.le_next if ($aproc == 0 && $nproc > 0) set $aproc = zombproc end set $proc = $aproc end end document pregs Show some pcb contents of process whose pid is specified. end define btr set $frame = $arg0 set $fno = 0 while (*(int *) $frame > 0xc0000000) set $myebp = *(int *) $frame set $myeip = *(int *) ($frame + 4) printf " frame %d at %p: ebp %8x, eip ", $fno, $frame, $myebp x/1i $myeip set $frame = $myebp set $fno = $fno + 1 end end document btr Show a backtrace from the ebp address specified. This can be used to get a backtrace from any stack resident in memory. end define btp set $nproc = nprocs set $aproc = allproc.lh_first set $proc = allproc.lh_first while (--$nproc >= 0) if ($proc->p_pid == $arg0) btr $proc->p_addr->u_pcb->pcb_ebp set $nproc = 0 else set $aproc = $proc.p_list.le_next if ($aproc == 0 && $nproc > 0) set $aproc = zombproc end set $proc = $aproc end end end document btp Show a backtrace for the process whose pid is specified as a parameter. end define btpa set $nproc = nprocs set $aproc = allproc.lh_first set $proc = allproc.lh_first printf " pid proc addr uid ppid pgrp flag stat comm wchan\n" while (--$nproc >= 0) set $pptr = $proc.p_pptr if ($pptr == 0) set $pptr = $proc end if ($proc.p_stat) printf "%5d %08x %08x %4d %5d %5d %06x %d %-10s ", \ $proc.p_pid, $aproc, \ $proc.p_addr, $proc.p_cred->p_ruid, $pptr->p_pid, \ $proc.p_pgrp->pg_id, $proc.p_flag, $proc.p_stat, \ &$proc.p_comm[0] if ($proc.p_wchan) if ($proc.p_wmesg) printf "%s ", $proc.p_wmesg end printf "%x", $proc.p_wchan end printf "\n" if ($proc->p_flag & 4) btr $proc->p_addr->u_pcb->pcb_ebp else echo (not loaded)\n end end set $aproc = $proc.p_list.le_next if ($aproc == 0 && $nproc > 0) set $aproc = zombproc end set $proc = $aproc end end document btpa Show backtraces for all processes in the system. end define btpp if ($myvectorproc->p_flag & 4) btr $myvectorproc->p_addr->u_pcb->pcb_ebp else echo (not loaded)\n end end document btpp Show a backtrace for the process previously selected with 'defproc'. end define defproc set $nproc = nprocs set $aproc = allproc.lh_first set $proc = allproc.lh_first while (--$nproc >= 0) if ($proc->p_pid == $arg0) set $pptr = $proc.p_pptr if ($pptr == 0) set $pptr = $proc end set $myvectorproc = $proc if ($proc.p_stat) printf "%5d %08x %08x %4d %5d %5d %06x %d %-10s ", \ $proc.p_pid, $aproc, \ $proc.p_addr, $proc.p_cred->p_ruid, $pptr->p_pid, \ $proc.p_pgrp->pg_id, $proc.p_flag, $proc.p_stat, \ &$proc.p_comm[0] if ($proc.p_wchan) if ($proc.p_wmesg) printf "%s ", $proc.p_wmesg end printf "%x", $proc.p_wchan end printf "\n" end btpp set $nproc = 0 else set $proc = $proc.p_list.le_next end end end document defproc Specify a process for btpp and fr commands. end define fr set $fno = 0 set $searching = 1 if ($myvectorproc->p_flag & 4) set $frame = $myvectorproc->p_addr->u_pcb->pcb_ebp while (($searching == 1) && (*(int *) $frame > 0xc0000000)) set $myebp = *(int *) $frame set $myeip = *(int *) ($frame + 4) if ($fno == $arg0) printf " frame %d at %p: ebp %8x, eip ", $fno, $frame, $myebp x/1i $myeip printf "Called from %8x, stack frame at %8x\n", *(int *) ($myebp+4), *(int *) $myebp printf "last 20 local variables:\n" x/20x ($myebp-80) printf "call parameters:\n" x/8x ($myebp+8) set $searching = 0 else set $frame = $myebp set $fno = $fno + 1 end end if ($searching == 1) echo frame not found\n end else printf "process %d is not loaded in memory\n", $myvectorproc->p_pid end end document fr Show the frame of the stack of the process previously selected with 'defproc'. end set height 70 set width 120 define vdev if (vp->v_type == VBLK) p *vp->v_un.vu_spec.vu_specinfo printf "numoutput: %d\n", vp->v_numoutput else echo "Not a block device" end end document vdev Show some information of the vnode pointed to by the local variable vp. end define y echo Check your .gdbinit, it contains a y command\n end define kldstat set $file = linker_files.tqh_first printf "Id Refs Address Size Name\n" while ($file != 0) printf "%2d %4d 0x%8x %8x %s\n", \ $file->id, \ $file->refs, \ $file->address, \ $file->size, \ $file->filename set $file = $file->link.tqe_next end end document kldstat Equivalent of the kldstat(9) command, without options. end define msgbuf printf "%s", msgbufp->msg_ptr end document msgbuf Print the system message buffer (dmesg). This can take a long time due to the time it takes to transmit the data across a serial line. end define icnt set $irq = 0 set $mask = imen while ($irq < 23) if ($mask & 1) printf "%d*\t", *intr_countp [$irq] else printf "%d\t", *intr_countp [$irq] end if (($irq & 7) == 7) printf "\n" end set $irq = $irq + 1 set $mask = $mask >> 1 end printf "\nimen: %x\n", imen end document icnt Print the interrupt counts for the first 16 interrupts end set $last=75 set $seg=43 # kmem_hdr define kmemhdr printf "\tINUSE\tCALLS\tMEMUSED\tLIMBLK\tMAPBLK\tMAXUSED\t\tLIMIT\n" end # pkmem define pkmem set $kp=(struct kmemstats *)$arg0 set $n = (struct kmemstats *)$kp - (struct kmemstats *)kmemstats printf "%d:\t%d\t%d", $n, $kp->ks_inuse, $kp->ks_calls printf "\t0x%x\t%d", $kp->ks_memuse, $kp->ks_limblocks printf "\t%d\t0x%x\t\t%d\n", $kp->ks_mapblocks, $kp->ks_maxused, $kp->ks_limit end define kmemdump set $kp=(struct kmemstats *)(kmemstats + $arg0) kmemhdr pkmem $kp end define kdumpall set $i=0 kmemhdr set $kp = (struct kmemstats *)kmemstats while ($i < $last) pkmem $kp set $kp++ set $i++ end end define ktr set $idx = ktr_idx - 1 set $last = ktr_idx if ($idx == -1) set $idx = ktr_entries - 1 end if (($idx != 0) || (ktr_buf [0].ktr_tv.tv_nsec != 0)) while ($idx != $last) set $kent = &ktr_buf[$idx] set $time = $kent->ktr_tv.tv_nsec set $ts = $kent->ktr_tv.tv_sec set $desc = $kent->ktr_desc printf "%3d %d:%9.9d ", $idx, $ts, $time # printf $desc, $kent->ktr_parm1, $kent->ktr_parm2, $kent->ktr_parm3, $kent->ktr_parm4, $kent->ktr_parm5 if (ktr_extend) printf "cpu%d %s.%d\t%s\n", $kent->ktr_cpu, $kent->ktr_filename, $kent->ktr_line, $kent->ktr_desc else printf "%s %p %p %p %p %p\n", $desc, $kent->ktr_parm1, $kent->ktr_parm2, $kent->ktr_parm3, $kent->ktr_parm4, $kent->ktr_parm5 end set $idx = $idx - 1 if ($idx == -1) set $idx = ktr_entries - 1 end end end end define icnt1 set $irq = 0 set $mask = apic_imen while ($irq < 31) if ($mask & 1) printf "%d*\t", *intr_countp [$irq] else printf "%d\t", *intr_countp [$irq] end if (($irq & 7) == 7) printf "\n" end set $irq = $irq + 1 set $mask = $mask >> 1 end printf "\napic_imen: %x\n", apic_imen end document icnt1 Print the interrupt counts for the first 24 interrupts on an SMP machine. end --/04w6evG8XlLl3ft-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 20:35: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B571F37B424; Sat, 16 Sep 2000 20:35:00 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA96973; Sat, 16 Sep 2000 20:35:00 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 16 Sep 2000 20:35:00 -0700 (PDT) From: Kris Kennaway To: Steve Kargl Cc: FreeBSD Current Subject: Re: upgrade libgmp? In-Reply-To: <200009161530.IAA05091@troutmask.apl.washington.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 Sat, 16 Sep 2000, Steve Kargl wrote: > Before I jump in and attempt to do an upgrade of libgmp, > I thought I'd asked if anyone else has endured this joy? > > Note, src/contrib/libgmp is at version 2.0.x and it is > 3+ years old. The newest version is at 3.1. The Changelog > indicates that there are numerous fixes and enhancements > over 2.0.x. See http://people.freebsd.org/~kris/libgmp.tar.gz I need to get back to this (and update to the latest version), but the issue is how to specify the partially ordered set of compatible CPU revisions which you'd like to build asm code for (same issue as with openssl) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 20:54:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom3-026.telepath.com [216.14.3.26]) by hub.freebsd.org (Postfix) with SMTP id 7465737B424 for ; Sat, 16 Sep 2000 20:54:23 -0700 (PDT) Received: (qmail 1778 invoked by uid 100); 17 Sep 2000 03:54:22 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14788.16494.26893.660078@guru.mired.org> Date: Sat, 16 Sep 2000 22:54:22 -0500 (CDT) To: current@freebsd.org Subject: Kernel builds to wrong location? X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsupped and rebuilt earlier to today, only to find that the kernel was installed as /boot/kernel/kernel instead of /boot/kernel/kernel.ko. While fixing this was trivial, it was a bit of a surprise. Is this a bug, or did I happen to catch the world in a state of change described in a cvs-all or current message I missed or hadn't read yet? Thanx, ; Sat, 16 Sep 2000 21:17:03 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13aVsn-000BqS-00; Sun, 17 Sep 2000 05:16:49 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id FAA27087; Sun, 17 Sep 2000 05:16:49 +0100 (BST) (envelope-from ben) Date: Sun, 17 Sep 2000 05:16:48 +0100 From: Ben Smithurst To: Mike Meyer Cc: current@freebsd.org Subject: Re: Kernel builds to wrong location? Message-ID: <20000917051648.I56185@strontium.scientia.demon.co.uk> References: <14788.16494.26893.660078@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14788.16494.26893.660078@guru.mired.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > I cvsupped and rebuilt earlier to today, only to find that the kernel > was installed as /boot/kernel/kernel instead of > /boot/kernel/kernel.ko. While fixing this was trivial, it was a bit of > a surprise. > > Is this a bug, or did I happen to catch the world in a state of change > described in a cvs-all or current message I missed or hadn't read yet? This is an intentional change, and was discussed on freebsd-arch. I'm not sure why you needed to fix anything though, it should have worked anyway. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 21:17:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 6EC5137B423; Sat, 16 Sep 2000 21:17:16 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id VAA07692; Sat, 16 Sep 2000 21:22:35 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200009170422.VAA07692@troutmask.apl.washington.edu> Subject: Re: upgrade libgmp? In-Reply-To: from Kris Kennaway at "Sep 16, 2000 08:35:00 pm" To: Kris Kennaway Date: Sat, 16 Sep 2000 21:22:35 -0700 (PDT) Cc: FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > On Sat, 16 Sep 2000, Steve Kargl wrote: > > > Before I jump in and attempt to do an upgrade of libgmp, > > I thought I'd asked if anyone else has endured this joy? > > > > Note, src/contrib/libgmp is at version 2.0.x and it is > > 3+ years old. The newest version is at 3.1. The Changelog > > indicates that there are numerous fixes and enhancements > > over 2.0.x. > > See http://people.freebsd.org/~kris/libgmp.tar.gz Thanks, Kris. I suspected that either you or markm would have already tackled the job. > I need to get back to this (and update to the latest version), but the > issue is how to specify the partially ordered set of compatible CPU > revisions which you'd like to build asm code for (same issue as with > openssl) I'm not fluent in FSF configure scripts, but it looks like configure tests the compiler for specific features to determine CPU type. The gross hack would be to add CPU_TYPE="generic" to /etc/defaults/make.conf, and allow users to define CPU_TYPE in /etc/make.conf. It appears that for example CPU_TYPE="alpha" is insufficient because each cpu type 21064, 21164, 21264 has tuned asm code. The bmake file would then have a cascade of #ifdef CPU_TYPE to pull in the right code. Would a CPU_TYPE variable be useful for others parts of "make world"? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 21:27:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from medianstrip.net (medianstrip.net [206.113.38.30]) by hub.freebsd.org (Postfix) with ESMTP id 6ADF537B422 for ; Sat, 16 Sep 2000 21:27:34 -0700 (PDT) Received: by medianstrip.net (Postfix, from userid 1000) id 65E0E58E5; Sun, 17 Sep 2000 00:27:33 -0400 (EDT) Date: Sun, 17 Sep 2000 00:27:33 -0400 From: mike ryan To: freebsd-current@freebsd.org Subject: fxp suspend/resume hangs Message-ID: <20000917002733.A37043@medianstrip.net> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG appended below is an excerpt from a message sent to -stable earlier tonight, containing content of a type which kris kenneway correctly suggested would find a more suitable audience on -current. in summary: PR kern/18756 contains a patch (against -stable, alas, sorry) which fixes kernel hangs in the fxp driver on some laptops after a resume from suspend. while quite a few people appear to be using this patch successfully, it hasn't been committed -- david greenman had an entirely reasonable objection to one aspect of the patch's behavior. unfortunately, my knowledge of the kernel isn't sufficient to adequately address david's concerns, and though i've mailed him to ask for guidance twice over the past 4 months, i haven't received a response. that's probably my fault, i probably should have been mailing -current to being with. if anybody can offer any suggestions as to how to move forward with getting this patch to the point where it can be committed, i'd certainly appreciate it. alternately, any feedback on whether the patch is necessary and/or functional on your machine, laptop or no, would be interesting. ----- Forwarded message from mike ryan ----- > From: mike ryan > Subject: ds1 pcm and fxp suspend/resume bugs (was Re: I'll be rolling a 4.1.1 release on September 25th) > To: stable@freebsd.org > Date: Sat, 16 Sep 2000 22:53:53 -0400 [ background snipped: jkh announced 4.1.1, pir asked about some patches ] > the fxp fix (PR 18756), on the other hand, has gone nowhere. david > greenman expressed concern about one bit of the patch (see the PR > for details), then disappeared. i've sent him a couple messages (on > may 22, also in the PR, and again august 26th in private mail) > asking if he had any advice on how to fix the fix, but i've gotten > no response. i saw a message on cvs-all a few days ago suggesting > that he had "resigned in a huff a few months ago", so perhaps this > got orphaned then? > > more importantly, maybe somebody on this list can help? briefly: > after a suspend/resume on some sony laptops, the fxp device needs to > have certain PCI registers reset, notably including the memory > mapped base address registers. in several places the fxp driver > issues a command, then busy-waits on a DMA indicating completion. > if such a command is issued before the base address registers have > been reprogrammed, the kernel will wait forever for a DMA that'll > never occur. CSR_READs will hang the kernel similarly. > > the patch in PR 18756 does several things, mostly based on ideas > from the netbsd and linux drivers: > > - saves and restores sufficient PCI registers across > suspend/resume. > > - adds timeouts to DMA busy-waits. > > - attempts to avoid handling interrupts before the device has > been resumed, to prevent hanging on the CSR_READ at the top of > fxp_intr(). > > it's the latter that DG thought might be a problem. the intent (and > effect, at least on my sony z505hs) was to protect against shared > interrupts delivered before the device is resumed. on my machine, > the fxp and uhci devices share irq 9. if the uhci controller is > resumed and generates an irq before the fxp device is resumed, the > fxp_intr() routine is also called and the machine freezes. > > i wouldn't be at all surprised if there were a better approach than > simply ignoring interrupts when the device isn't running, but it's > not clear to me what that would be. if anybody has any suggestions > as to how to clean this up, i'm all ears. alternately, if any > committers want to take this on, that'd be swell too. ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 21:28:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom1-178.telepath.com [216.14.1.178]) by hub.freebsd.org (Postfix) with SMTP id 838B337B42C for ; Sat, 16 Sep 2000 21:28:14 -0700 (PDT) Received: (qmail 2704 invoked by uid 100); 17 Sep 2000 04:27:34 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14788.18486.789541.682547@guru.mired.org> Date: Sat, 16 Sep 2000 23:27:34 -0500 (CDT) To: Ben Smithurst Cc: current@FreeBSD.org Subject: Re: Kernel builds to wrong location? In-Reply-To: <20000917051648.I56185@strontium.scientia.demon.co.uk> References: <14788.16494.26893.660078@guru.mired.org> <20000917051648.I56185@strontium.scientia.demon.co.uk> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst writes: > Mike Meyer wrote: > > I cvsupped and rebuilt earlier to today, only to find that the kernel > > was installed as /boot/kernel/kernel instead of > > /boot/kernel/kernel.ko. While fixing this was trivial, it was a bit of > > a surprise. > > Is this a bug, or did I happen to catch the world in a state of change > > described in a cvs-all or current message I missed or hadn't read yet? > This is an intentional change, and was discussed on freebsd-arch. I'm > not sure why you needed to fix anything though, it should have worked > anyway. I think I had to fix things because the first boot on the new kernel used the old loader. I did that because this is an ahc-based system, and there have been comments about such not booting on this list. So I did installkernel and rebooted before doing installworld. That the system booted properly after doing the installworld caused me to wonder about things. The old loader failed to find /boot/kernel/kernel.ko and aborted the boot. The new loader found /boot/kernel/kernel.ko and booted fine. Does the new loader check both /boot/kernel/kernel and /boot/kernel/kernel.ko? Is needing to have a new loader installed to boot worth a mention in UPDATING? Thanx, To: Steve Kargl Cc: FreeBSD Current Subject: Re: upgrade libgmp? In-Reply-To: <200009170422.VAA07692@troutmask.apl.washington.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 Sat, 16 Sep 2000, Steve Kargl wrote: > I'm not fluent in FSF configure scripts, but it looks like > configure tests the compiler for specific features to determine > CPU type. The gross hack would be to add CPU_TYPE="generic" > to /etc/defaults/make.conf, and allow users to define CPU_TYPE > in /etc/make.conf. It appears that for example CPU_TYPE="alpha" > is insufficient because each cpu type 21064, 21164, 21264 has > tuned asm code. The bmake file would then have a cascade of > #ifdef CPU_TYPE to pull in the right code. > > Would a CPU_TYPE variable be useful for others parts of "make world"? The issue is that you have all sorts of possibilities like i386, i486, pentium, pentiumpro, pentiummmx, k6, ... which you need to specify in order of preference. If someone would care to submit example code of how to handle this nicely from both the user and makefile perspective I'd be grateful :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 21:32:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 6A2A737B42C for ; Sat, 16 Sep 2000 21:32:21 -0700 (PDT) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id NAA19653; Sun, 17 Sep 2000 13:32:08 +0900 (JST) To: snap-users@kame.net Cc: rbezuide@oskar.nanoteq.co.za, freebsd-current@freebsd.org In-reply-to: sakane's message of Sat, 16 Sep 2000 20:20:11 JST. <20000916202011C.sakane@ydc.co.jp> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: (KAME-snap 3327) Re: Panic on current (12 Sept) From: itojun@iijlab.net Date: Sun, 17 Sep 2000 13:32:08 +0900 Message-ID: <19651.969165128@coconut.itojun.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I'm running a current machine of 12 Sept although this problem >> also occured on a current of a few days earlier ... "current machine" meaning FreeBSD-current? if so, are there any locking behavior changes due to the introduction of fine grain locks? what happens if you go back to coarse grain lock kernel? itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 22: 1:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id A854937B422; Sat, 16 Sep 2000 22:01:10 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id WAA07848; Sat, 16 Sep 2000 22:06:29 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200009170506.WAA07848@troutmask.apl.washington.edu> Subject: Re: upgrade libgmp? In-Reply-To: from Kris Kennaway at "Sep 16, 2000 09:31:22 pm" To: Kris Kennaway Date: Sat, 16 Sep 2000 22:06:29 -0700 (PDT) Cc: FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > On Sat, 16 Sep 2000, Steve Kargl wrote: > > > I'm not fluent in FSF configure scripts, but it looks like > > configure tests the compiler for specific features to determine > > CPU type. The gross hack would be to add CPU_TYPE="generic" > > to /etc/defaults/make.conf, and allow users to define CPU_TYPE > > in /etc/make.conf. It appears that for example CPU_TYPE="alpha" > > is insufficient because each cpu type 21064, 21164, 21264 has > > tuned asm code. The bmake file would then have a cascade of > > #ifdef CPU_TYPE to pull in the right code. > > > > Would a CPU_TYPE variable be useful for others parts of "make world"? > > The issue is that you have all sorts of possibilities like i386, i486, > pentium, pentiumpro, pentiummmx, k6, ... which you need to specify in > order of preference. If someone would care to submit example code of how > to handle this nicely from both the user and makefile perspective I'd be > grateful :-) > I need to review the gmp documents again, but I not sure the preference order is much of an issue. By default, CPU_TYPE="generic" would build the C code, which should work on all architectures supported by FreeBSD. If a user explicitly sets CPU_TYPE in /etc/make.conf, then the ordering would be CPU_TYPE then generic. There is not gray area. For example, I have an athlon processor, so libgmp.a would have a preferred order of athlon, generic. The question that I don't know the answer to is what happens if someone really screws up and sets CPU_TYPE to 21264 when he has an i386. I suspect that this would break make world, so it will be easily detected. Another possibility would be to specify the preference order in a CPU_ORDER variable. For example, CPU_ORDER="k6,i386,pentium" and always add "generic" has the last target. The major problem with this is that the parsing of CPU_ORDER suggests that you have to generate Makefile on the fly otherwise Makefile would be a big bowl of spaghetti. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 22: 4:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 1F3DE37B423 for ; Sat, 16 Sep 2000 22:04:10 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id WAA07882 for freebsd-current@freebsd.org; Sat, 16 Sep 2000 22:09:29 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200009170509.WAA07882@troutmask.apl.washington.edu> Subject: aic7xxx breaks kernel build To: FreeBSD Current Date: Sat, 16 Sep 2000 22:09:29 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get the following with sources cvsup'd for cvsup5.freebsd.org at 10:00 pm PST on 16 Sep 00. hotrats:root[222] make buildkernel -------------------------------------------------------------- >>> Rebuilding kernel(s) -------------------------------------------------------------- ===> HOTRATS mkdir -p /usr/obj/usr/src/sys cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -r -d /usr/obj/usr/src/sys/HOTRATS HOTRATS Removing old directory /usr/obj/usr/src/sys/HOTRATS: Done. Don't forget to do a ``make depend'' Kernel build directory is /usr/obj/usr/src/sys/HOTRATS cd /usr/obj/usr/src/sys/HOTRATS; MAKESRCPATH=/usr/src/sys/dev/aic7xxx make -f /usr/src/sys/dev/aic7xxx/Makefile make: cannot open /usr/src/sys/dev/aic7xxx/Makefile. *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 16 22:23:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A180137B424; Sat, 16 Sep 2000 22:23:53 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA20741; Sat, 16 Sep 2000 22:23:53 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 16 Sep 2000 22:23:53 -0700 (PDT) From: Kris Kennaway To: Steve Kargl Cc: FreeBSD Current Subject: Re: upgrade libgmp? In-Reply-To: <200009170506.WAA07848@troutmask.apl.washington.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 Sat, 16 Sep 2000, Steve Kargl wrote: > I need to review the gmp documents again, but I not sure > the preference order is much of an issue. By default, > CPU_TYPE="generic" would build the C code, which should work > on all architectures supported by FreeBSD. If a user explicitly > sets CPU_TYPE in /etc/make.conf, then the ordering would be > CPU_TYPE then generic. There is not gray area. For example, > I have an athlon processor, so libgmp.a would have a preferred > order of athlon, generic. It's not just for libgmp, but for other parts of the system too (like openssl). For example, what happens if you have a pentium pro, but there are no ppro optimisations in a particular program - but there are pentium optimisations. Obviously you would want those as a fallback. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message