From owner-freebsd-current Sun Jul 30 0:29:32 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 4638037B92F for ; Sun, 30 Jul 2000 00:29:22 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id JAA86566; Sun, 30 Jul 2000 09:28:45 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id JAA67071; Sun, 30 Jul 2000 09:12:22 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Sun, 30 Jul 2000 09:11:52 +0200 (CEST) From: Leif Neland To: Chris Costello Cc: freebsd-current@FreeBSD.ORG Subject: Re: sendmail 8.11.0 trouble In-Reply-To: <20000730002843.Q37935@holly.calldei.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, 30 Jul 2000, Chris Costello wrote: > On Sunday, July 30, 2000, Leif Neland wrote: > > Freshly cvsupped current. > > > > Sendmail 8.11.0 > > > > When invoking sendmail or newaliases I get this message: > > /etc/pwd.db: Invalid argument > > > > Sendmail can't read /etc/pwd.db, and therefore cannot deliver any local > > mail. > > > > Howtofixitplease? > > If you mean when running it as non-root, then you should have > g+r on /etc/pwd.db, since it carries the same information as > /etc/passwd anyway. > > sendmail is -r-sr-xr-x root bin /etc/pwd.db -rw-r--r-- root wheel I haven't done anything else than unpacking sendmail, building and installing. No command line options or other tricks, except adding milter to devtools/Site/site.config.m4 Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 2:19: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id DC88437B61A; Sun, 30 Jul 2000 02:18:43 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id LAA07595; Sun, 30 Jul 2000 11:18:48 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007300918.LAA07595@grimreaper.grondar.za> To: Brian Fundakowski Feldman Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Brian Fundakowski Feldman "Sun, 30 Jul 2000 00:25:42 -0400." Date: Sun, 30 Jul 2000 11:18:48 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mark already stated that in *practicality*, Yarrow-BF-cbc-256 1.0 > (I guess that's the proper name for this :-) is complex enough and > generates good enough ouput. If you /really/ want to make the attack > on it much harder, how about this: if you're going to read 1024 bits > of entropy from Yarrow on /dev/random, you will request it all at once > and block just as the old random(4) used to block; the blocking can > occur at 256 bit intervals and sleep until there is a reseed. Waiting > to reseed for each read will ensure a much larger amount of "real" > entropy than it "maybe" happening at random times. This is a reversion to the count-entropy-and-block model which I have been fiercely resisting (and which argument I thought I had sucessfully defended). My solution is to get the entropy gathering at a high enough rate that this is not necessary. I also agreed to _maybe_ look at a re-engineer of the "old" code in a secure way if a decent algorithm could be found (I am reading some papers about this ATM). 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 Jul 30 2:24:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id AA88A37B5C5; Sun, 30 Jul 2000 02:24:44 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id LAA07632; Sun, 30 Jul 2000 11:24:49 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007300924.LAA07632@grimreaper.grondar.za> To: Brian Fundakowski Feldman Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Brian Fundakowski Feldman "Sun, 30 Jul 2000 00:25:42 -0400." Date: Sun, 30 Jul 2000 11:24:49 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Content-Disposition: attachment; filename="yarrow_blocking.patch" Brian: I want to take a different approach to this one. Do not commit anything to the /dev/random device, please, without running it by me. 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 Jul 30 3:42:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id 8BE6037B511; Sun, 30 Jul 2000 03:42:09 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (root@daemon.ninth-circle.org [195.38.210.81]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id e6UAg5070834; Sun, 30 Jul 2000 12:42:05 +0200 (CEST) Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id MAA30348; Sun, 30 Jul 2000 12:42:01 +0200 (CEST) (envelope-from asmodai) Date: Sun, 30 Jul 2000 12:42:00 +0200 From: Jeroen Ruigrok/Asmodai To: ports@freebsd.org, current@freebsd.org Subject: snes9x Message-ID: <20000730124200.B28035@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am really uncertain where to set the reply-to to. I don't read ports though. Anyways. I have been using snes9x 1.26 some time ago on my CURRENT box and everything worked ok. Today, after I updated my CURRENT this weeks from a month old to something more recent, I figured I should install snes9x again. So I installed 1.29. 'lo and behold, the colours are all crazy, lots of green. I cannot remember exactly when I last used snes9x, but my .snes96_snapshots/ directory shows february as the last savedates. I just asked some guys who are using 4-STABLE to test a ROM and with 4-STABLE, snes9x 1.29 and that same rom they see the colours as they should be. So I cannot say anything else but that CURRENT has a weird bug somewhere. So therefor I am looking for people with CURRENTs which are between january and now to install snes9x 1.29 and try the rom at http://lucifer.in-nomine.org/~asmodai/Ff5.zip And see what colours the opening screen have [that's the final fantasy logo]. I get all kinds of greens, but it should be blue IIRC. Some info about my setup: Xfree 3.3.6 on CURRENT. /usr/X11R6/bin/snes9x: libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x280e7000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x280f2000) libz.so.2 => /usr/lib/libz.so.2 (0x28192000) libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x2819f000) libm.so.2 => /usr/lib/libm.so.2 (0x281de000) libc_r.so.4 => /usr/lib/libc_r.so.4 (0x281fa000) libXThrStub.so.6 => /usr/X11R6/lib/libXThrStub.so.6 (0x282aa000) 4-STABLE: /usr/X11R6/bin/snes9x: libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x280e7000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x280f6000) libz.so.2 => /usr/lib/libz.so.2 (0x281e9000) libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x281f6000) libm.so.2 => /usr/lib/libm.so.2 (0x28234000) libc_r.so.4 => /usr/lib/libc_r.so.4 (0x2824f000) The only difference is the XThrStub, but that's the X Threaded Stub library if I can judge by its name. Ideas are welcome, I mean, could syscons influence this? -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Abandon hope, all ye who enter here... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 9: 2:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A283137B561; Sun, 30 Jul 2000 09:02:12 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Sun, 30 Jul 2000 12:02:11 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Mark Murray Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007300924.LAA07632@grimreaper.grondar.za> 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, 30 Jul 2000, Mark Murray wrote: > > Content-Disposition: attachment; filename="yarrow_blocking.patch" > > Brian: > > I want to take a different approach to this one. > > Do not commit anything to the /dev/random device, please, without running > it by me. I was not planning on it. You really should take a look at the bugfixes, though; reading buffer sizes of >8 bytes but not-8-byte-multiple should do it. There's also the ioctl handler which you need stubs for and then checking for open devices when you attempt to unload the module. > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Jul 30 9:31:47 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 9BAA137B561 for ; Sun, 30 Jul 2000 09:31:41 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.138] (helo=mx0.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #1) id 13Iw03-0006rg-00 for current@freebsd.org; Sun, 30 Jul 2000 18:31:39 +0200 Received: from a39c9.pppool.de ([213.6.57.201] helo=Magelan.Leidinger.net) by mx0.freenet.de with esmtp (Exim 3.16 #1) id 13Iw02-000758-00 for current@freebsd.org; Sun, 30 Jul 2000 18:31:39 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id OAA54019 for ; Sun, 30 Jul 2000 14:31:05 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200007301231.OAA54019@Magelan.Leidinger.net> Date: Sun, 30 Jul 2000 14:31:03 +0200 (CEST) From: Alexander Leidinger Subject: phkmalloc & pam_ssh & xdm To: current@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, pam_ssh isn't able to start ssh-agent if you use ---snip--- xdm session sufficient pam_ssh.so ---snip--- in /etc/pam.conf. With "malloc.conf -> aj" it seems to work. grep pam /var/log/messages: ---snip--- Jul 30 00:54:04 Magelan -:0: unable to resolve symbol: pam_sm_chauthtok Jul 30 00:54:05 Magelan -:0: pam_ssh: could not connect to agent ---snip--- Is someone else able to reproduce this? Bye, Alexander. -- It is easier to fix Unix than to live with NT. 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 Sun Jul 30 9:37:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id CBF1937B615; Sun, 30 Jul 2000 09:37:20 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Sun, 30 Jul 2000 12:37:19 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Jeroen Ruigrok/Asmodai Cc: ports@freebsd.org, current@freebsd.org Subject: Re: snes9x In-Reply-To: <20000730124200.B28035@daemon.ninth-circle.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, 30 Jul 2000, Jeroen Ruigrok/Asmodai wrote: > I am really uncertain where to set the reply-to to. > I don't read ports though. > > Anyways. > > I have been using snes9x 1.26 some time ago on my CURRENT box and > everything worked ok. > > Today, after I updated my CURRENT this weeks from a month old to > something more recent, I figured I should install snes9x again. > > So I installed 1.29. 'lo and behold, the colours are all crazy, lots of > green. Hmm... are you trying to tell me something? *g* > I cannot remember exactly when I last used snes9x, but my > .snes96_snapshots/ directory shows february as the last savedates. Definitely too long ;) > I just asked some guys who are using 4-STABLE to test a ROM and with > 4-STABLE, snes9x 1.29 and that same rom they see the colours as they > should be. > > So I cannot say anything else but that CURRENT has a weird bug > somewhere. So therefor I am looking for people with CURRENTs which are > between january and now to install snes9x 1.29 and try the rom at > http://lucifer.in-nomine.org/~asmodai/Ff5.zip > And see what colours the opening screen have [that's the final fantasy > logo]. I get all kinds of greens, but it should be blue IIRC. Indeed it's blue on my current as of last week. > Some info about my setup: Xfree 3.3.6 on CURRENT. Same here. > /usr/X11R6/bin/snes9x: > libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x280e7000) > libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x280f2000) > libz.so.2 => /usr/lib/libz.so.2 (0x28192000) > libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x2819f000) > libm.so.2 => /usr/lib/libm.so.2 (0x281de000) > libc_r.so.4 => /usr/lib/libc_r.so.4 (0x281fa000) > libXThrStub.so.6 => /usr/X11R6/lib/libXThrStub.so.6 (0x282aa000) > > 4-STABLE: > > /usr/X11R6/bin/snes9x: > libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x280e7000) > libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x280f6000) > libz.so.2 => /usr/lib/libz.so.2 (0x281e9000) > libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x281f6000) > libm.so.2 => /usr/lib/libm.so.2 (0x28234000) > libc_r.so.4 => /usr/lib/libc_r.so.4 (0x2824f000) > > The only difference is the XThrStub, but that's the X Threaded Stub > library if I can judge by its name. > > Ideas are welcome, I mean, could syscons influence this? What color depth are you running at? I wouldn't expect that anything 16-bit or higher wouldn't work well, at least. -CURRENT usually works great for gaming for me; I'm going through, e.g., Chrono Trigger my second time now :) I'd guess something may be taking up a HUGE amount of the palette, unless you are running in 24-bit mode. If it's not that, perhaps it's the video card itself. This is a rather strange problem to have. > -- > Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] > Documentation nutter/C-rated Coder BSD: Technical excellence at its best > The BSD Programmer's Documentation Project > Abandon hope, all ye who enter here... -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Jul 30 9:48:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 07C2837B615; Sun, 30 Jul 2000 09:48:42 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Sun, 30 Jul 2000 12:48:40 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Mark Murray Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007300918.LAA07595@grimreaper.grondar.za> 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, 30 Jul 2000, Mark Murray wrote: > This is a reversion to the count-entropy-and-block model which I have > been fiercely resisting (and which argument I thought I had sucessfully > defended). > > My solution is to get the entropy gathering at a high enough rate that > this is not necessary. How does entropy gathering at a high enough rate solve this particularly? Unless you wait for reseeds while reading, it simply doesn't matter how much entropy is being gathered at the time since reading any amount just doesn't give you a new key. Indeed, if you can get enough entropy that the blocking in read would be very short, you would still need to block in read to give it time to use the entropy. The only alternative I can see that you might be thinking of would be that the user would be encouraged to only read a small amount at a time and reading more soon later in the assumption that Yarrow will be rekeyed. Then this would be just forcing the user to do the blocking manually, and non-deterministically. So how exactly _would_ just having a high entropy gathering rate help the case that you need a large amount of data from /dev/random with true entropic value, not only 256 bits worth? It's not like reseeds would be occurring while reads were in progress; reads are too fast for that and are splsofttq() protected, anyway. > I also agreed to _maybe_ look at a re-engineer of the "old" code in a > secure way if a decent algorithm could be found (I am reading some > papers about this ATM). > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Jul 30 9:57:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id E629637B615; Sun, 30 Jul 2000 09:57:21 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id SAA08928; Sun, 30 Jul 2000 18:57:22 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007301657.SAA08928@grimreaper.grondar.za> To: Brian Fundakowski Feldman Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Brian Fundakowski Feldman "Sun, 30 Jul 2000 12:02:11 -0400." Date: Sun, 30 Jul 2000 18:57:22 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Do not commit anything to the /dev/random device, please, without running > > it by me. > > I was not planning on it. You really should take a look at the bugfixes, > though; reading buffer sizes of >8 bytes but not-8-byte-multiple should > do it. There's also the ioctl handler which you need stubs for and then > checking for open devices when you attempt to unload the module. Will do, thanks! 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 Jul 30 10: 7: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 1093E37B6BB; Sun, 30 Jul 2000 10:06:59 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id TAA08976; Sun, 30 Jul 2000 19:07:01 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007301707.TAA08976@grimreaper.grondar.za> To: Brian Fundakowski Feldman Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Brian Fundakowski Feldman "Sun, 30 Jul 2000 12:48:40 -0400." Date: Sun, 30 Jul 2000 19:07:01 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How does entropy gathering at a high enough rate solve this > particularly? EG, by having it such that Yarrow state perturbations happen often enough that each read is "guaranteed" to be associated with at least one and preferably more. 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 Jul 30 10:28:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 9844337B5F2; Sun, 30 Jul 2000 10:28:49 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Sun, 30 Jul 2000 13:28:47 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Mark Murray Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007301707.TAA08976@grimreaper.grondar.za> 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, 30 Jul 2000, Mark Murray wrote: > > How does entropy gathering at a high enough rate solve this > > particularly? > > EG, by having it such that Yarrow state perturbations happen often > enough that each read is "guaranteed" to be associated with at least > one and preferably more. Can you give me an idea how this would work, at least with e.g. pseudocode annotation of the current code? I'm curious what you're going to change that will allow reseeeding while a read is in progress. > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Jul 30 11:26:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id D6F0537B706; Sun, 30 Jul 2000 11:26:14 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id UAA09292; Sun, 30 Jul 2000 20:26:16 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007301826.UAA09292@grimreaper.grondar.za> To: Brian Fundakowski Feldman Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Brian Fundakowski Feldman "Sun, 30 Jul 2000 13:28:47 -0400." Date: Sun, 30 Jul 2000 20:26:16 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > EG, by having it such that Yarrow state perturbations happen often > > enough that each read is "guaranteed" to be associated with at least > > one and preferably more. > > Can you give me an idea how this would work, at least with e.g. > pseudocode annotation of the current code? I'm curious what you're > going to change that will allow reseeeding while a read is in > progress. I didn't say "reseed", I said "perturb". Same code, (improved reseed control), more harvesting calls. 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 Jul 30 11:39: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id A180237B67B for ; Sun, 30 Jul 2000 11:38:52 -0700 (PDT) (envelope-from trish@bsdunix.net) Received: from localhost (trish@localhost) by superconductor.rush.net (8.9.3/8.9.3) with ESMTP id OAA21391; Sun, 30 Jul 2000 14:38:20 -0400 (EDT) Date: Sun, 30 Jul 2000 14:38:20 -0400 (EDT) From: Siobhan Patricia Lynch X-Sender: trish@superconductor.rush.net To: Leif Neland Cc: Chris Costello , freebsd-current@FreeBSD.ORG Subject: Re: sendmail 8.11.0 trouble 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 weird, works fine for me here.... -trish __ Trish Lynch FreeBSD - The Power to Serve trish@bsdunix.net Rush Networking trish@rush.net On Sun, 30 Jul 2000, Leif Neland wrote: > > > On Sun, 30 Jul 2000, Chris Costello wrote: > > > On Sunday, July 30, 2000, Leif Neland wrote: > > > Freshly cvsupped current. > > > > > > Sendmail 8.11.0 > > > > > > When invoking sendmail or newaliases I get this message: > > > /etc/pwd.db: Invalid argument > > > > > > Sendmail can't read /etc/pwd.db, and therefore cannot deliver any local > > > mail. > > > > > > Howtofixitplease? > > > > If you mean when running it as non-root, then you should have > > g+r on /etc/pwd.db, since it carries the same information as > > /etc/passwd anyway. > > > > > sendmail is -r-sr-xr-x root bin > /etc/pwd.db -rw-r--r-- root wheel > > I haven't done anything else than unpacking sendmail, building and > installing. No command line options or other tricks, except adding milter > to devtools/Site/site.config.m4 > > Leif > > > > > 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 Sun Jul 30 12: 6:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id 9D89C37B739; Sun, 30 Jul 2000 12:06:27 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (root@daemon.ninth-circle.org [195.38.210.81]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id e6UJ6K186403; Sun, 30 Jul 2000 21:06:20 +0200 (CEST) Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA31772; Sun, 30 Jul 2000 21:05:05 +0200 (CEST) (envelope-from asmodai) Date: Sun, 30 Jul 2000 21:05:05 +0200 From: Jeroen Ruigrok/Asmodai To: Brian Fundakowski Feldman Cc: ports@freebsd.org, current@freebsd.org Subject: Re: snes9x Message-ID: <20000730210505.C28035@daemon.ninth-circle.org> References: <20000730124200.B28035@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from green@FreeBSD.org on Sun, Jul 30, 2000 at 12:37:19PM -0400 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000730 19:47], Brian Fundakowski Feldman (green@FreeBSD.org) wrote: >On Sun, 30 Jul 2000, Jeroen Ruigrok/Asmodai wrote: > >> I cannot remember exactly when I last used snes9x, but my >> .snes96_snapshots/ directory shows february as the last savedates. > >Definitely too long ;) Yeah I know. =P >Indeed it's blue on my current as of last week. Hmmm. >> Ideas are welcome, I mean, could syscons influence this? > >What color depth are you running at? I wouldn't expect that anything >16-bit or higher wouldn't work well, at least. -CURRENT usually works >great for gaming for me; I'm going through, e.g., Chrono Trigger my >second time now :) 16-bit, 1024x768 as I have done in the past as well. Window Maker set to its default colour allocating scheme. >I'd guess something may be taking up a HUGE amount of the palette, >unless you are running in 24-bit mode. If it's not that, perhaps >it's the video card itself. This is a rather strange problem to have. Well, that's the whole confusing thing in this situation. Nothing changed in my configuration aside from reinstalling X and Window Maker and any supporting library. But all the configurations are still the same. And those worked before. I wish I knew where to start looking. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Abandon hope, all ye who enter here... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 12:12:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from pille.addcom.de (h-62.96.128.34.user.addcom.de [62.96.128.34]) by hub.freebsd.org (Postfix) with SMTP id 7E34237B647 for ; Sun, 30 Jul 2000 12:12:14 -0700 (PDT) (envelope-from sblank@addcom.de) Received: (qmail 19165 invoked from network); 30 Jul 2000 19:12:11 -0000 Received: from h-62.96.149.104.user.addcom.de (HELO ally.blank.de) (root@62.96.149.104) by pille.addcom.de with SMTP; 30 Jul 2000 19:12:11 -0000 Received: (from sblank@localhost) by ally.blank.de (8.11.0/8.11.0) id e6UJAqQ00468; Sun, 30 Jul 2000 21:10:52 +0200 (CEST) Date: Sun, 30 Jul 2000 21:10:52 +0200 From: Sascha Blank To: Benedikt Schmidt Cc: current@freebsd.org Subject: Re: Mouse frozen in X when returning from text console Message-ID: <20000730211052.A407@ally.blank.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from BeSchmidt@cloaked.de on Sun, Jul 30, 2000 at 02:24:38AM +0200 Organization: Computer Center of the University of Trier, Germany Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, On Sun, Jul 30, 2000 at 02:24:38AM +0200, Benedikt Schmidt wrote: > On Wed, Jul 26, 2000 at 11:12:34PM -0400, Alexander N. Kabaev wrote: > > The patch solves the problem here too. Perhaps it could be added to the other > FreeBSD patches in the XFree86-4 port. I have sent it already to the XFree86-4 port's maintainer on July 18th, but so far I haven't received any reply. Maybe I should contact him again. -- Sascha Blank | "I prefer to work behind the scenes. The Student and System Administrator | reward is nearly as great, but the risk at the University of Trier, Germany | is far, far less." - Ambassador Mollari mailto:sblank@addcom.de | in Bablyon 5, "The coming of shadows." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 12:18:22 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 92C7F37B741 for ; Sun, 30 Jul 2000 12:17:35 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA03021; Sun, 30 Jul 2000 14:40:45 -0400 (EDT) (envelope-from wollman) Date: Sun, 30 Jul 2000 14:40:45 -0400 (EDT) From: Garrett Wollman Message-Id: <200007301840.OAA03021@khavrinen.lcs.mit.edu> To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: sendmail 8.11.0 trouble In-Reply-To: References: <20000730002843.Q37935@holly.calldei.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> On Sunday, July 30, 2000, Leif Neland wrote: >> > Sendmail 8.11.0 >> > >> > When invoking sendmail or newaliases I get this message: >> > /etc/pwd.db: Invalid argument >> > >> > Sendmail can't read /etc/pwd.db, and therefore cannot deliver any local >> > mail. >> > >> > Howtofixitplease? Sounds like you're using the wrong version of Berkeley DB (i.e., not the one in libc). Can't fathom how this could override the internal linkage in libc, though. -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 Sun Jul 30 12:59:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id D860537B73A; Sun, 30 Jul 2000 12:59:18 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (root@daemon.ninth-circle.org [195.38.210.81]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id e6UJxC697120; Sun, 30 Jul 2000 21:59:12 +0200 (CEST) Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA32134; Sun, 30 Jul 2000 21:58:36 +0200 (CEST) (envelope-from asmodai) Date: Sun, 30 Jul 2000 21:58:36 +0200 From: Jeroen Ruigrok/Asmodai To: Brian Fundakowski Feldman Cc: ports@freebsd.org, current@freebsd.org Subject: Re: snes9x Message-ID: <20000730215836.A32129@daemon.ninth-circle.org> References: <20000730124200.B28035@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from green@FreeBSD.org on Sun, Jul 30, 2000 at 12:37:19PM -0400 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000730 19:47], Brian Fundakowski Feldman (green@FreeBSD.org) wrote: >What color depth are you running at? I wouldn't expect that anything >16-bit or higher wouldn't work well, at least. -CURRENT usually works >great for gaming for me; I'm going through, e.g., Chrono Trigger my >second time now :) > >I'd guess something may be taking up a HUGE amount of the palette, >unless you are running in 24-bit mode. If it's not that, perhaps >it's the video card itself. This is a rather strange problem to have. I just tried twm, if something ain't a palette eater it's twm, and I get the exact same problems. A bit flickery display, with too much greens. Odd. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Abandon hope, all ye who enter here... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 15: 8:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 86F1737B7F1; Sun, 30 Jul 2000 15:08:46 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA09172; Sun, 30 Jul 2000 15:08:46 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 30 Jul 2000 15:08:46 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: Brian Fundakowski Feldman , current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007300918.LAA07595@grimreaper.grondar.za> 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, 30 Jul 2000, Mark Murray wrote: > This is a reversion to the count-entropy-and-block model which I have > been fiercely resisting (and which argument I thought I had sucessfully > defended). Actually, I was waiting for your reply to Jeroen's question about changing the semantics of the random devices. I still maintain that as OS developers we can't predict the uses of this tool and that some users may require new entropy in every 256-bit output. I don't think that "near enough is good enough" is a valid excuse :-) 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 Jul 30 16:30:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from wendell.heistand.org (wendell.heistand.org [209.181.116.46]) by hub.freebsd.org (Postfix) with ESMTP id D89B337B724 for ; Sun, 30 Jul 2000 16:30:09 -0700 (PDT) (envelope-from heistand@heistand.org) Received: by wendell.heistand.org (Postfix, from userid 1821) id C309D1B24B; Sun, 30 Jul 2000 17:30:06 -0600 (MDT) Subject: keyboard problems with X To: freebsd-current@freebsd.org Date: Sun, 30 Jul 2000 17:30:06 -0600 (MDT) From: heistand@heistand.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000730233006.C309D1B24B@wendell.heistand.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I updated my source tree yesterday (and kernel) and am having some problems with my keyboard under X. Has anyone else noticed anything strange. steve -- Steve Heistand heistand@heistand.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 16:42:10 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 0B44D37B60C for ; Sun, 30 Jul 2000 16:42:07 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (root@rac5.wam.umd.edu [128.8.10.145]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA02317; Sun, 30 Jul 2000 19:41:48 -0400 (EDT) Received: from rac5.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id TAA10633; Sun, 30 Jul 2000 19:41:56 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA10629; Sun, 30 Jul 2000 19:41:55 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Sun, 30 Jul 2000 19:41:51 -0400 (EDT) From: Kenneth Wayne Culver To: heistand@heistand.org Cc: freebsd-current@FreeBSD.ORG Subject: Re: keyboard problems with X In-Reply-To: <20000730233006.C309D1B24B@wendell.heistand.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 I have, like when I'm running tail on something, and then I try to ctrl-c out of it, the whole console locks solid, and I have to reboot. (although if I was connected to an ethernet, I think I could probably ssh in and reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the lockmgr problems that were reported earlier. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sun, 30 Jul 2000 heistand@heistand.org wrote: > Hi, > > I updated my source tree yesterday (and kernel) and am having some problems > with my keyboard under X. Has anyone else noticed anything > strange. > > steve > > -- > Steve Heistand > heistand@heistand.org > > > 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 Sun Jul 30 16:48:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from wendell.heistand.org (wendell.heistand.org [209.181.116.46]) by hub.freebsd.org (Postfix) with ESMTP id E033737B6C8 for ; Sun, 30 Jul 2000 16:48:40 -0700 (PDT) (envelope-from heistand@heistand.org) Received: by wendell.heistand.org (Postfix, from userid 1821) id A53251B24B; Sun, 30 Jul 2000 17:48:26 -0600 (MDT) Subject: Re: keyboard problems with X In-Reply-To: from Kenneth Wayne Culver at "Jul 30, 2000 07:41:51 pm" To: Kenneth Wayne Culver Date: Sun, 30 Jul 2000 17:48:26 -0600 (MDT) Cc: heistand@heistand.org, freebsd-current@FreeBSD.ORG From: heistand@heistand.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000730234826.A53251B24B@wendell.heistand.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem I am seeing is that the keyboard isnt even seen. Its useable up until about midway through the boot process, then it goes dead/locks up. The boot continues fine and the machine is up. The mouse is usable in X but not the keyboard. Cant even switch virtual consoles. steve > I have, like when I'm running tail on something, and then I try to ctrl-c > out of it, the whole console locks solid, and I have to reboot. (although > if I was connected to an ethernet, I think I could probably ssh in and > reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the > lockmgr problems that were reported earlier. > > > ================================================================= > | Kenneth Culver | FreeBSD: The best NT upgrade | > | Unix Systems Administrator | ICQ #: 24767726 | > | and student at The | AIM: muythaibxr | > | The University of Maryland, | Website: (Under Construction) | > | College Park. | http://www.wam.umd.edu/~culverk/| > ================================================================= > > On Sun, 30 Jul 2000 heistand@heistand.org wrote: > > > Hi, > > > > I updated my source tree yesterday (and kernel) and am having some problems > > with my keyboard under X. Has anyone else noticed anything > > strange. > > > > steve > > > > -- > > Steve Heistand > > heistand@heistand.org > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- Steve Heistand heistand@heistand.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 17:59:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 8CB4E37B858 for ; Sun, 30 Jul 2000 17:59:37 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu (root@rac7.wam.umd.edu [128.8.10.147]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA11154; Sun, 30 Jul 2000 20:59:17 -0400 (EDT) Received: from rac7.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.3/8.9.3) with SMTP id UAA09506; Sun, 30 Jul 2000 20:59:07 -0400 (EDT) Received: from localhost (culverk@localhost) by rac7.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA09502; Sun, 30 Jul 2000 20:59:07 -0400 (EDT) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Sun, 30 Jul 2000 20:59:07 -0400 (EDT) From: Kenneth Wayne Culver To: heistand@heistand.org Cc: freebsd-current@FreeBSD.ORG Subject: Re: keyboard problems with X In-Reply-To: <20000730234826.A53251B24B@wendell.heistand.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 Hrmm, that's even worse than my problem. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sun, 30 Jul 2000 heistand@heistand.org wrote: > The problem I am seeing is that the keyboard isnt even seen. > Its useable up until about midway through the boot process, > then it goes dead/locks up. The boot continues fine and the machine > is up. The mouse is usable in X but not the keyboard. Cant even switch > virtual consoles. > > steve > > > I have, like when I'm running tail on something, and then I try to ctrl-c > > out of it, the whole console locks solid, and I have to reboot. (although > > if I was connected to an ethernet, I think I could probably ssh in and > > reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the > > lockmgr problems that were reported earlier. > > > > > > ================================================================= > > | Kenneth Culver | FreeBSD: The best NT upgrade | > > | Unix Systems Administrator | ICQ #: 24767726 | > > | and student at The | AIM: muythaibxr | > > | The University of Maryland, | Website: (Under Construction) | > > | College Park. | http://www.wam.umd.edu/~culverk/| > > ================================================================= > > > > On Sun, 30 Jul 2000 heistand@heistand.org wrote: > > > > > Hi, > > > > > > I updated my source tree yesterday (and kernel) and am having some problems > > > with my keyboard under X. Has anyone else noticed anything > > > strange. > > > > > > steve > > > > > > -- > > > Steve Heistand > > > heistand@heistand.org > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > -- > Steve Heistand > heistand@heistand.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 18:45:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom3-080.telepath.com [216.14.3.80]) by hub.freebsd.org (Postfix) with SMTP id 22B1F37B933 for ; Sun, 30 Jul 2000 18:45:08 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 31066 invoked by uid 100); 31 Jul 2000 01:45:05 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14724.55841.514697.67191@guru.mired.org> Date: Sun, 30 Jul 2000 20:45:05 -0500 (CDT) To: current@freebsd.org Subject: perl vs. LOCALBASE, again 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 My last grip about this didn't draw any response except for "Yeah, I have that problem to". Is there a better place to discuss problems with the Perl integration with FreeBSD? send-pr doesn't have a "perl" category, or I'd try that. Basically, the problem is that ports that install Perl modules ignore LOCALBASE for the perl modules. A little bit of investigation turns up /usr/libdata/perl/5.6.0/Config.pm, which has "/usr/local" wired through it as a prefix for nearly everything. While wading through the Perl installation process to change these, that still wouldn't really solve the problem. First, LOCALBASE could be changed sometime after Perl was built. Second, and more importantly, perl modules that aren't being installed as part of a port shouldn't go in LOCALBASE (at least optionally). I suspect the ideal situation would be for the Perl module installer to detect (how?) to try and sniff LOCALBASE out of /etc/make.conf if this is part of a port install. If that works, use LOCALBASE. Otherwise, use the default Config.pm values. People who want that default to be something other than /usr/local can then change those values themselves. Is there someone who can *fix* this? Thanx, ; Sun, 30 Jul 2000 18:48:07 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p26-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.155]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id KAA22000; Mon, 31 Jul 2000 10:47:36 +0900 (JST) Message-ID: <3984DAC1.4ACBF964@newsguy.com> Date: Mon, 31 Jul 2000 10:47:45 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: phkmalloc & pam_ssh & xdm References: <200007301231.OAA54019@Magelan.Leidinger.net> 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, > > pam_ssh isn't able to start ssh-agent if you use > ---snip--- > xdm session sufficient pam_ssh.so > ---snip--- > in /etc/pam.conf. With "malloc.conf -> aj" it seems to work. > > grep pam /var/log/messages: > ---snip--- > Jul 30 00:54:04 Magelan -:0: unable to resolve symbol: pam_sm_chauthtok > Jul 30 00:54:05 Magelan -:0: pam_ssh: could not connect to agent > ---snip--- > > Is someone else able to reproduce this? If that's the case, you have a bug. Not one easy to trace, though... :-( -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@white.bunnies.bsdconspiracy.net Satan was once an angel, Gates started by writing a BASIC interpreter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 19:32:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.chuckr.org (dsl254-096-118-nyc1.dsl-isp.net [216.254.96.118]) by hub.freebsd.org (Postfix) with ESMTP id 05A2A37B96C for ; Sun, 30 Jul 2000 19:32:49 -0700 (PDT) (envelope-from chuckr@picnic.chuckr.org) Received: from localhost (chuckr@localhost) by picnic.chuckr.org (8.9.3/8.9.3) with ESMTP id WAA20327; Sun, 30 Jul 2000 22:32:27 -0400 (EDT) (envelope-from chuckr@picnic.chuckr.org) Date: Sun, 30 Jul 2000 22:32:26 -0400 (EDT) From: Chuck Robey To: heistand@heistand.org Cc: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: keyboard problems with X In-Reply-To: <20000730234826.A53251B24B@wendell.heistand.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, 30 Jul 2000 heistand@heistand.org wrote: > The problem I am seeing is that the keyboard isnt even seen. > Its useable up until about midway through the boot process, > then it goes dead/locks up. The boot continues fine and the machine > is up. The mouse is usable in X but not the keyboard. Cant even switch > virtual consoles. Is it useable or not, outside of X? Can you single-user boot and get the keyboard working? I am not clear if it's an X problem or a system problem. You said you updated your source tree yesterday. If that was from a recent build, then I don't know, but I'm very curious, just how old was your previous build? The config changed really radically maybe 2 months ago, so maybe your config file is hosed? > > steve > > > I have, like when I'm running tail on something, and then I try to ctrl-c > > out of it, the whole console locks solid, and I have to reboot. (although > > if I was connected to an ethernet, I think I could probably ssh in and > > reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the > > lockmgr problems that were reported earlier. > > > > > > ================================================================= > > | Kenneth Culver | FreeBSD: The best NT upgrade | > > | Unix Systems Administrator | ICQ #: 24767726 | > > | and student at The | AIM: muythaibxr | > > | The University of Maryland, | Website: (Under Construction) | > > | College Park. | http://www.wam.umd.edu/~culverk/| > > ================================================================= > > > > On Sun, 30 Jul 2000 heistand@heistand.org wrote: > > > > > Hi, > > > > > > I updated my source tree yesterday (and kernel) and am having some problems > > > with my keyboard under X. Has anyone else noticed anything > > > strange. > > > > > > steve > > > > > > -- > > > Steve Heistand > > > heistand@heistand.org > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 19:42:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from wendell.heistand.org (wendell.heistand.org [209.181.116.46]) by hub.freebsd.org (Postfix) with ESMTP id 24B4937B985 for ; Sun, 30 Jul 2000 19:42:30 -0700 (PDT) (envelope-from heistand@heistand.org) Received: by wendell.heistand.org (Postfix, from userid 1821) id E3E7E1B24B; Sun, 30 Jul 2000 20:41:27 -0600 (MDT) Subject: Re: keyboard problems with X To: freebsd-current@freebsd.org Date: Sun, 30 Jul 2000 20:41:27 -0600 (MDT) From: heistand@heistand.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000731024127.E3E7E1B24B@wendell.heistand.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Originally didnt response back to mailing list...) The keyboard works fine when I dont start X, single user mode or just at the console. I can crash the machine whenever I switch virtual consoles which is most not fun. Not sure if its strictly an X problem on not. My previous -current was before the radical changes so I might have something out of wack but not sure. I think I got everything in my kernel config file uptodate. steve On Sun, 30 Jul 2000 heistand@heistand.org wrote: > The problem I am seeing is that the keyboard isnt even seen. > Its useable up until about midway through the boot process, > then it goes dead/locks up. The boot continues fine and the machine > is up. The mouse is usable in X but not the keyboard. Cant even switch > virtual consoles. Is it useable or not, outside of X? Can you single-user boot and get the keyboard working? I am not clear if it's an X problem or a system problem. You said you updated your source tree yesterday. If that was from a recent build, then I don't know, but I'm very curious, just how old was your previous build? The config changed really radically maybe 2 months ago, so maybe your config file is hosed? > > steve > > > I have, like when I'm running tail on something, and then I try to ctrl-c > > out of it, the whole console locks solid, and I have to reboot. (although > > if I was connected to an ethernet, I think I could probably ssh in and > > reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the > > lockmgr problems that were reported earlier. > > > > > > ================================================================= > > | Kenneth Culver | FreeBSD: The best NT upgrade | > > | Unix Systems Administrator | ICQ #: 24767726 | > > | and student at The | AIM: muythaibxr | > > | The University of Maryland, | Website: (Under Construction) | > > | College Park. | http://www.wam.umd.edu/~culverk/| > > ================================================================= > > > > On Sun, 30 Jul 2000 heistand@heistand.org wrote: > > > > > Hi, > > > > > > I updated my source tree yesterday (and kernel) and am having some problems > > > with my keyboard under X. Has anyone else noticed anything > > > strange. > > > > > > steve > > > > > > -- > > > Steve Heistand > > > heistand@heistand.org > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message ----- End of forwarded message from Chuck Robey ----- -- Steve Heistand heistand@heistand.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 20: 4:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 1E4B437B97A for ; Sun, 30 Jul 2000 20:04:42 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA14859; Sun, 30 Jul 2000 23:04:15 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA28626; Sun, 30 Jul 2000 23:04:06 -0400 (EDT) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA28622; Sun, 30 Jul 2000 23:04:05 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Sun, 30 Jul 2000 23:04:05 -0400 (EDT) From: Kenneth Wayne Culver To: Chuck Robey Cc: heistand@heistand.org, freebsd-current@FreeBSD.ORG Subject: Re: keyboard problems with X 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 My problems are with a previous build of late last week. And my problem isn't with X. My problem only happens when you start "tail" on some file, then try to exit. It locks the console solid... neither the mouse nor the keyboard work. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sun, 30 Jul 2000, Chuck Robey wrote: > On Sun, 30 Jul 2000 heistand@heistand.org wrote: > > > The problem I am seeing is that the keyboard isnt even seen. > > Its useable up until about midway through the boot process, > > then it goes dead/locks up. The boot continues fine and the machine > > is up. The mouse is usable in X but not the keyboard. Cant even switch > > virtual consoles. > > Is it useable or not, outside of X? Can you single-user boot and get the > keyboard working? I am not clear if it's an X problem or a system > problem. > > You said you updated your source tree yesterday. If that was from a > recent build, then I don't know, but I'm very curious, just how old was > your previous build? The config changed really radically maybe 2 months > ago, so maybe your config file is hosed? > > > > > steve > > > > > I have, like when I'm running tail on something, and then I try to ctrl-c > > > out of it, the whole console locks solid, and I have to reboot. (although > > > if I was connected to an ethernet, I think I could probably ssh in and > > > reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the > > > lockmgr problems that were reported earlier. > > > > > > > > > ================================================================= > > > | Kenneth Culver | FreeBSD: The best NT upgrade | > > > | Unix Systems Administrator | ICQ #: 24767726 | > > > | and student at The | AIM: muythaibxr | > > > | The University of Maryland, | Website: (Under Construction) | > > > | College Park. | http://www.wam.umd.edu/~culverk/| > > > ================================================================= > > > > > > On Sun, 30 Jul 2000 heistand@heistand.org wrote: > > > > > > > Hi, > > > > > > > > I updated my source tree yesterday (and kernel) and am having some problems > > > > with my keyboard under X. Has anyone else noticed anything > > > > strange. > > > > > > > > steve > > > > > > > > -- > > > > Steve Heistand > > > > heistand@heistand.org > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > > > > > > > > > ---------------------------------------------------------------------------- > Chuck Robey | Interests include C & Java programming, FreeBSD, > chuckr@picnic.mat.net | electronics, communications, and signal processing. > > New Year's Resolution: I will not sphroxify gullible people into looking up > fictitious words in the dictionary. > ---------------------------------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 20:12: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls05.mediaone.net (chmls05.mediaone.net [24.147.1.143]) by hub.freebsd.org (Postfix) with ESMTP id 5F90037B92A for ; Sun, 30 Jul 2000 20:11:56 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.251.241]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id XAA12221; Sun, 30 Jul 2000 23:11:18 -0400 (EDT) Message-ID: <3984EE55.27806662@acm.org> Date: Sun, 30 Jul 2000 23:11:17 -0400 From: Jim Bloom X-Mailer: Mozilla 4.73 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kenneth Wayne Culver Cc: heistand@heistand.org, freebsd-current@FreeBSD.ORG Subject: Re: keyboard problems with X References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To resolve the problem with tail, rebuild your kernel with revision 1.11 of sys/kern/kern_event.c. 1.12 which was designed to make the kevent system restartable seems to keep the process from ever receiving the interrupt. I don't have a solution which solves both problems yet. Jim Bloom bloom@acm.org Kenneth Wayne Culver wrote: > > I have, like when I'm running tail on something, and then I try to ctrl-c > out of it, the whole console locks solid, and I have to reboot. (although > if I was connected to an ethernet, I think I could probably ssh in and > reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the > lockmgr problems that were reported earlier. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 20:14:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id F2B2537B9BC for ; Sun, 30 Jul 2000 20:14:49 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from ppp-207-214-149-53.snrf01.pacbell.net ([207.214.149.53]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FYJ009BZKZARZ@mta6.snfc21.pbi.net> for current@FreeBSD.ORG; Sun, 30 Jul 2000 20:14:05 -0700 (PDT) Date: Sun, 30 Jul 2000 20:15:06 -0700 (PDT) From: Alex Zepeda Subject: Re: phkmalloc & pam_ssh & xdm In-reply-to: <200007301231.OAA54019@Magelan.Leidinger.net> X-Sender: alex@zippy.pacbell.net To: Alexander Leidinger Cc: current@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 Sun, 30 Jul 2000, Alexander Leidinger wrote: > Hi, > > pam_ssh isn't able to start ssh-agent if you use > ---snip--- > xdm session sufficient pam_ssh.so > ---snip--- > in /etc/pam.conf. With "malloc.conf -> aj" it seems to work. I've seen problems like this (try using Konqueror with malloc.conf set to AJ, *sigh*). What that indicates to me is that an application is expecting initialized memory, but it's too lazy to initialize the memory itself. Thus causing unexpected results. !#@$#!@ Anyone wanna debug kdelibs, Qt and Konqueror? *grin* - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 20:18:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls05.mediaone.net (chmls05.mediaone.net [24.147.1.143]) by hub.freebsd.org (Postfix) with ESMTP id 26E0337B9BC; Sun, 30 Jul 2000 20:18:42 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.251.241]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id XAA14265; Sun, 30 Jul 2000 23:18:41 -0400 (EDT) Message-ID: <3984F010.1A208994@acm.org> Date: Sun, 30 Jul 2000 23:18:40 -0400 From: Jim Bloom X-Mailer: Mozilla 4.73 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jonathan Lemon , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern kern_event.c References: <200007272306.QAA41002@freefall.freebsd.org> <3983A329.B37CE8BA@acm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I didn't have much time for testing, but backing out this change fixes the problem tail. For some reason, the signal never gets delivered to the process. The manual page states that the kevent processing is lower priority than signal handling and that the signal will get processed as normal before the event will will be logged. In fact, I witnessed a case where a SIGKILL would not kill the process after a SIGINT. Jim Bloom bloom@acm.org Jim Bloom wrote: > > I am having problems with "tail -f" hanging the machine. I don't know if this > change is related, but I suspect that it might be. > > I commonly do a "tail -f" of my log file while doing a buildworld. As soon as I > interrupted the tail, the machine hung. I then tried to figure out what was > causing the problem. Eventually, I tracked the problem down to tail. The > machine would respond to pings, but the keyboard was useless. It would not > shutdown as well. One test I tried was to run tail -f under truss. This > actually kept the machine somewhat usable. Top showed truss using 75% of the > CPU and tail using the other 25%. System time was running over 80%. Truss > reported that tail kept receiving the signal (indefinitely as far as I could > tell) at a high rate of speed. > > I tried to get a kernel core dump several times by breaking into ddb, but I > never had any luck. Here is the backtrace copied by hand: > > vec1(c0f8d540,1,bfbffa9c,0,c81b76c0) at vec1+0x2 > kevent(c81b76c0,c8bd1f80,280f6b40,4,4) at kevent+0x152 > syscall2(2f,2f,2f,4,4) at syscall2+0x1f1 > Xinit0x80_syscall() at Xint0x80_syscall+0x25 > > My kernel and source tree both date from 20:00-22:00 EDT on July 28. > > I found the problem to be quite repeatable by simply going "tail -f file" (the > file does not need to change) and then hitting an interrupt on the keyboard. > > Let me know if I can be of any assistance in tracking this problem down. I > might try to spend some time tomorrow figuring out what is happening. > > Jim Bloom > bloom@acm.org > > Jonathan Lemon wrote: > > > > jlemon 2000/07/27 16:06:15 PDT > > > > Modified files: > > sys/kern kern_event.c > > Log: > > Have kevent() automatically restart if interrupted by a signal. If this > > is not desired, then the user can register an EV_SIGNAL filter to > > explicitly catch a signal event. > > > > Change requested by: jayanth, ps, peter > > "Why is kevent non-restartable after a signal?" > > > > Revision Changes Path > > 1.12 +3 -6 src/sys/kern/kern_event.c > > 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 Sun Jul 30 20:51:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls05.mediaone.net (chmls05.mediaone.net [24.147.1.143]) by hub.freebsd.org (Postfix) with ESMTP id 810A437B81E; Sun, 30 Jul 2000 20:51:37 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.251.241]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id XAA22881; Sun, 30 Jul 2000 23:51:36 -0400 (EDT) Message-ID: <3984F7C8.AE445EC2@acm.org> Date: Sun, 30 Jul 2000 23:51:36 -0400 From: Jim Bloom X-Mailer: Mozilla 4.73 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jonathan Lemon , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern kern_event.c References: <200007272306.QAA41002@freefall.freebsd.org> <3983A329.B37CE8BA@acm.org> <3984F010.1A208994@acm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did a little more testing of this problem just now. A SIGKILL does not kill the process but will lock up the machine. Truss reports the SIGKILL being continuously sent to the process. If I break into DDB, and then panic, I get a panic "lockmgr: pid XXX, not exclusive lock holder 0 unlocking". The pid is for the tail command. Jim Bloom bloom@acm.org Jim Bloom wrote: > > I didn't have much time for testing, but backing out this change fixes the > problem tail. For some reason, the signal never gets delivered to the process. > The manual page states that the kevent processing is lower priority than signal > handling and that the signal will get processed as normal before the event will > will be logged. > > In fact, I witnessed a case where a SIGKILL would not kill the process after a > SIGINT. > > Jim Bloom > bloom@acm.org > > Jim Bloom wrote: > > > > I am having problems with "tail -f" hanging the machine. I don't know if this > > change is related, but I suspect that it might be. > > > > I commonly do a "tail -f" of my log file while doing a buildworld. As soon as I > > interrupted the tail, the machine hung. I then tried to figure out what was > > causing the problem. Eventually, I tracked the problem down to tail. The > > machine would respond to pings, but the keyboard was useless. It would not > > shutdown as well. One test I tried was to run tail -f under truss. This > > actually kept the machine somewhat usable. Top showed truss using 75% of the > > CPU and tail using the other 25%. System time was running over 80%. Truss > > reported that tail kept receiving the signal (indefinitely as far as I could > > tell) at a high rate of speed. > > > > I tried to get a kernel core dump several times by breaking into ddb, but I > > never had any luck. Here is the backtrace copied by hand: > > > > vec1(c0f8d540,1,bfbffa9c,0,c81b76c0) at vec1+0x2 > > kevent(c81b76c0,c8bd1f80,280f6b40,4,4) at kevent+0x152 > > syscall2(2f,2f,2f,4,4) at syscall2+0x1f1 > > Xinit0x80_syscall() at Xint0x80_syscall+0x25 > > > > My kernel and source tree both date from 20:00-22:00 EDT on July 28. > > > > I found the problem to be quite repeatable by simply going "tail -f file" (the > > file does not need to change) and then hitting an interrupt on the keyboard. > > > > Let me know if I can be of any assistance in tracking this problem down. I > > might try to spend some time tomorrow figuring out what is happening. > > > > Jim Bloom > > bloom@acm.org > > > > Jonathan Lemon wrote: > > > > > > jlemon 2000/07/27 16:06:15 PDT > > > > > > Modified files: > > > sys/kern kern_event.c > > > Log: > > > Have kevent() automatically restart if interrupted by a signal. If this > > > is not desired, then the user can register an EV_SIGNAL filter to > > > explicitly catch a signal event. > > > > > > Change requested by: jayanth, ps, peter > > > "Why is kevent non-restartable after a signal?" > > > > > > Revision Changes Path > > > 1.12 +3 -6 src/sys/kern/kern_event.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 21:35:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.chuckr.org (dsl254-096-118-nyc1.dsl-isp.net [216.254.96.118]) by hub.freebsd.org (Postfix) with ESMTP id A592F37BA36 for ; Sun, 30 Jul 2000 21:35:55 -0700 (PDT) (envelope-from chuckr@picnic.chuckr.org) Received: from localhost (chuckr@localhost) by picnic.chuckr.org (8.9.3/8.9.3) with ESMTP id AAA20632; Mon, 31 Jul 2000 00:06:33 -0400 (EDT) (envelope-from chuckr@picnic.chuckr.org) Date: Mon, 31 Jul 2000 00:06:33 -0400 (EDT) From: Chuck Robey To: Kenneth Wayne Culver Cc: heistand@heistand.org, freebsd-current@FreeBSD.ORG Subject: Re: keyboard problems with X 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 Sun, 30 Jul 2000, Kenneth Wayne Culver wrote: > My problems are with a previous build of late last week. And my problem > isn't with X. My problem only happens when you start "tail" on some file, > then try to exit. It locks the console solid... neither the mouse nor the > keyboard work. Sorry, Ken, I was looking at his problem. I havne't the vaguest notion where your's comes out of. I might suggest doing a ktrace/kdump and see if maybe something is grabbing the keyboard that you aren't aware of. BTW, notice the new address ... I wanted connectivity NOW, and maybe didn't have the greatest imagination as per domain name, but at least my new dsl is up. I just wish it hadn't taken my voice line to do it. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 30 23: 4:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id AA5E037BA55; Sun, 30 Jul 2000 23:04:25 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id IAA11207; Mon, 31 Jul 2000 08:04:23 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007310604.IAA11207@grimreaper.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Kris Kennaway "Sun, 30 Jul 2000 15:08:46 MST." Date: Mon, 31 Jul 2000 08:04:23 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 30 Jul 2000, Mark Murray wrote: > > > This is a reversion to the count-entropy-and-block model which I have > > been fiercely resisting (and which argument I thought I had sucessfully > > defended). > > Actually, I was waiting for your reply to Jeroen's question about changing > the semantics of the random devices. Oops; I thought I got that one. ISTR something about looking for different algorithms that may do it, and you pointed me at 2 sites; one had no write-up, and I'm looking at the other. 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 Mon Jul 31 1:39:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0618937B8BF; Mon, 31 Jul 2000 01:39:29 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA79093; Mon, 31 Jul 2000 01:39:29 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 31 Jul 2000 01:39:29 -0700 (PDT) From: Kris Kennaway To: current@freebsd.org Cc: net@freebsd.org Subject: Mozilla-M15+ipv6 package available 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 A few people have asked me for this, so I uploaded a package of the mozilla-M15+ipv6 port from KAME to http://www.freebsd.org/~kris/mozilla-M15.tgz (yes, I know M16 is out, but the port isn't yet updated). Install this package and you too can see the dancing kame at http://www.kame.net, the current hilight of the inet6! The patches aren't quite suitable for committing to the ports collection because they unconditionally enable support for IPv6 which may not work on 3.x machines, but if anyone is interested in looking at them then please let me know. 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 Jul 31 1:44:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 5561437BB51 for ; Mon, 31 Jul 2000 01:44:13 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA79709 for ; Mon, 31 Jul 2000 01:44:13 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 31 Jul 2000 01:44:13 -0700 (PDT) From: Kris Kennaway To: current@freebsd.org Subject: sort(1) broken? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following no longer seems to work on any of my 5.0 boxes: ls -l | sort -n -k 5 which should sort numerically by the size column (instead it seems to do the same thing as sort -n). It works correctly on 3.x and 4.x boxes. Anyone have ideas? 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 Jul 31 2:31:56 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 D73B437B72A for ; Mon, 31 Jul 2000 02:31:52 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 3608 invoked from network); 31 Jul 2000 09:31:51 -0000 Received: from acs-24-154-24-131.zoominternet.net (HELO cvzoom.net) (24.154.24.131) by ns.cvzoom.net with SMTP; 31 Jul 2000 09:31:51 -0000 Message-ID: <39854786.ED4A28B5@cvzoom.net> Date: Mon, 31 Jul 2000 05:31:50 -0400 From: Donn Miller X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: Mozilla-M15+ipv6 package available References: 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: > > A few people have asked me for this, so I uploaded a package of the > mozilla-M15+ipv6 port from KAME to > > http://www.freebsd.org/~kris/mozilla-M15.tgz > > (yes, I know M16 is out, but the port isn't yet updated). The last few Mozillas I tried compiling from source (on -current), I'd get a message in xterm saying the document was fully loaded, but yet no window would appear. It seemed like a problem with threading. Anyone else see this? -- - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 4:28:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5296637B87D; Mon, 31 Jul 2000 04:28:10 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Mon, 31 Jul 2000 07:28:09 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Kris Kennaway Cc: current@freebsd.org Subject: Re: sort(1) broken? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jul 2000, Kris Kennaway wrote: > The following no longer seems to work on any of my 5.0 boxes: > > ls -l | sort -n -k 5 > > which should sort numerically by the size column (instead it seems to do > the same thing as sort -n). It works correctly on 3.x and 4.x boxes. > > Anyone have ideas? Sure: {"/home/green"}$ ls -l | MALLOC_OPTIONS=AJ sort -nk5 | tail -10 | head -5 drwxr-xr-x 13 green green 512 Jun 7 1999 saint-1.4 drwxr-xr-x 16 green green 512 Aug 5 1999 stress drwxr-xr-x 17 green green 512 Feb 14 23:27 ioccc drwxr-xr-x 17 green www 1536 Jul 30 18:39 public_html drwxr-xr-x 21 green green 1024 Feb 7 1999 descent {"/home/green"}$ ls -l | MALLOC_OPTIONS=aj sort -nk5 | tail -10 | head -5 -rwx------ 1 green green 31017984 Jan 19 2000 quake1.tar.gz -rw-r--r-- 1 green green 32642085 Jun 25 00:31 mail.tar.gz -rw-rw-rw- 1 green green 47845836 Jun 26 18:52 ccs12.rm -rw-r--r-- 1 green green 52525668 Jun 5 21:30 SaberMarionetteJ-ep04.rm -rw-r--r-- 1 green green 53822026 Jul 11 07:53 SaberMarionetteJ-ep02.rm To fix this particular bug, the patch is: Index: sort.c =================================================================== RCS file: /usr2/ncvs/src/gnu/usr.bin/sort/sort.c,v retrieving revision 1.15 diff -u -r1.15 sort.c --- sort.c 1999/04/25 22:14:05 1.15 +++ sort.c 2000/07/31 11:26:33 @@ -1860,6 +1860,7 @@ insertkey (key); key = (struct keyfield *) xmalloc (sizeof (struct keyfield)); + bzero(key, sizeof(*key)); key->eword = -1; key->ignore = NULL; key->translate = NULL; I'm doubtful it's the only one of it's kind in GNU sort(1). Time for BSD sort(1)? > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Jul 31 5: 8:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id AA2F837BB2F; Mon, 31 Jul 2000 05:08:27 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13JEMp-000H3U-00; Mon, 31 Jul 2000 14:08:23 +0200 From: Sheldon Hearn To: Brian Fundakowski Feldman Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: sort(1) broken? In-reply-to: Your message of "Mon, 31 Jul 2000 07:28:09 -0400." Date: Mon, 31 Jul 2000 14:08:23 +0200 Message-ID: <65563.965045303@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jul 2000 07:28:09 -0400, Brian Fundakowski Feldman wrote: > key = (struct keyfield *) > xmalloc (sizeof (struct keyfield)); > + bzero(key, sizeof(*key)); Wouldn't a calloc() be exactly what's required here? 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 Jul 31 5:23:58 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 ABB6637B620 for ; Mon, 31 Jul 2000 05:23:51 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #1) id 13JEbk-0003C0-00; Mon, 31 Jul 2000 14:23:48 +0200 Received: from a2b62.pppool.de ([213.6.43.98] helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.16 #1) id 13JEbi-0000uO-00; Mon, 31 Jul 2000 14:23:47 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id OAA39940; Mon, 31 Jul 2000 14:23:08 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200007311223.OAA39940@Magelan.Leidinger.net> Date: Mon, 31 Jul 2000 14:23:07 +0200 (CEST) From: Alexander Leidinger Subject: Re: phkmalloc & pam_ssh & xdm To: dcs@newsguy.com Cc: current@FreeBSD.ORG In-Reply-To: <3984DAC1.4ACBF964@newsguy.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31 Jul, Daniel C. Sobral wrote: >> pam_ssh isn't able to start ssh-agent if you use >> ---snip--- >> xdm session sufficient pam_ssh.so >> ---snip--- >> in /etc/pam.conf. With "malloc.conf -> aj" it seems to work. >> >> grep pam /var/log/messages: >> ---snip--- >> Jul 30 00:54:04 Magelan -:0: unable to resolve symbol: pam_sm_chauthtok >> Jul 30 00:54:05 Magelan -:0: pam_ssh: could not connect to agent >> ---snip--- >> >> Is someone else able to reproduce this? > > If that's the case, you have a bug. Not one easy to trace, though... :-( I assume it's uninitialized memory, it didn't happen with "ln -sf AJZ /etc/malloc.conf". This reduces it to code after *alloc calls... or it's an unterminated string. Ok, I give it a try... It seems it isn't really something with PAM, /usr/src/crypto/openssh/pam_ssh/pam_ssh.c: ---snip--- if (!(ac = ssh_get_authentication_connection())) { syslog(LOG_ERR, "%s: could not connect to agent", MODULE_NAME); env_destroy(ssh_env); return PAM_SESSION_ERR; ---snip--- and /usr/src/crypto/openssh/authfd.c: ---snip--- int ssh_get_authentication_socket() { const char *authsocket; int sock; struct sockaddr_un sunaddr; [...] sunaddr.sun_family = AF_UNIX; strlcpy(sunaddr.sun_path, authsocket, sizeof(sunaddr.sun_path)); [...] if (connect(sock, (struct sockaddr *) & sunaddr, sizeof(sunaddr)) < 0) { [...] ---snip--- and /usr/include/sys/un.h: ---snip--- struct sockaddr_un { u_char sun_len; /* sockaddr len including null */ u_char sun_family; /* AF_UNIX */ char sun_path[104]; /* path name (gag) */ }; ---snip--- sunaddr.sun_len isn't set. If I understand the APUE, it should be: ---snip--- Index: authfd.c =================================================================== RCS file: /big/FreeBSD-CVS/src/crypto/openssh/authfd.c,v retrieving revision 1.4 diff -u -r1.4 authfd.c --- authfd.c 2000/07/16 05:52:23 1.4 +++ authfd.c 2000/07/31 12:03:52 @@ -33,7 +33,7 @@ ssh_get_authentication_socket() { const char *authsocket; - int sock; + int sock, len; struct sockaddr_un sunaddr; authsocket = getenv(SSH_AUTHSOCKET_ENV_NAME); @@ -42,6 +42,7 @@ sunaddr.sun_family = AF_UNIX; strlcpy(sunaddr.sun_path, authsocket, sizeof(sunaddr.sun_path)); + sunaddr.sun_len = len = SUN_LEN(&sunaddr)+1; sock = socket(AF_UNIX, SOCK_STREAM, 0); if (sock < 0) @@ -52,7 +53,7 @@ close(sock); return -1; } - if (connect(sock, (struct sockaddr *) & sunaddr, sizeof(sunaddr)) < 0) { + if (connect(sock, (struct sockaddr *) & sunaddr, len) < 0) { close(sock); return -1; } ---snip--- I rebuilded libssh.a and pam_ssh.so with this patch and I didn't get the error anymore. I haven't rebuilded the world or anything openssh related, but I think this should work (and because of the readability of pam_ssh.c and authfd.c it was easy to trace only by looking at the source... it seems using FreeBSD is the "Right Thing[TM]" :) ). BTW.: the "pam_sm_chauthok" error isn't "xdm session" related, it's because of "xdm account" or "xdm password" (it's not implemented in pam_ssh). Bye, Alexander. -- Loose bits sink chips. 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 Mon Jul 31 6:21:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.silyn-tek.de (mout1.silyn-tek.de [194.25.165.69]) by hub.freebsd.org (Postfix) with ESMTP id 6395537BB78; Mon, 31 Jul 2000 06:21:46 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.34] (helo=mx2.silyn-tek.de) by mout1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13JFVq-0005Kb-00; Mon, 31 Jul 2000 15:21:46 +0200 Received: from p3e9c1167.dip0.t-ipconnect.de ([62.156.17.103] helo=neutron.cichlids.com) by mx2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13JFVl-0001nw-00; Mon, 31 Jul 2000 15:21:41 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 54D2DAB91; Mon, 31 Jul 2000 15:21:52 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id AFC0514BB0; Mon, 31 Jul 2000 15:21:39 +0200 (CEST) Date: Mon, 31 Jul 2000 15:21:39 +0200 To: Brian Fundakowski Feldman Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: sort(1) broken? Message-ID: <20000731152139.A39969@cichlids.cichlids.com> Mail-Followup-To: Brian Fundakowski Feldman , Kris Kennaway , current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from green@FreeBSD.ORG on Mon, Jul 31, 2000 at 07:28:09AM -0400 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Brian Fundakowski Feldman (green@FreeBSD.ORG): > I'm doubtful it's the only one of it's kind in GNU sort(1). Time for BSD > sort(1)? What about BSD/OS's sort? Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 6:24: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id 3A27D37BAB4 for ; Mon, 31 Jul 2000 06:23:58 -0700 (PDT) (envelope-from tobez@plab.ku.dk) Received: (from tobez@localhost) by plab.ku.dk (8.9.3/8.9.3) id PAA05420; Mon, 31 Jul 2000 15:23:50 +0200 (CEST) (envelope-from tobez) Date: Mon, 31 Jul 2000 15:23:50 +0200 From: Anton Berezin To: Mike Meyer Cc: current@FreeBSD.ORG Subject: Re: perl vs. LOCALBASE, again Message-ID: <20000731152350.U48988@plab.ku.dk> References: <14724.55841.514697.67191@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: <14724.55841.514697.67191@guru.mired.org>; from mwm@mired.org on Sun, Jul 30, 2000 at 08:45:05PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 30, 2000 at 08:45:05PM -0500, Mike Meyer wrote: > Basically, the problem is that ports that install Perl modules ignore > LOCALBASE for the perl modules. A little bit of investigation turns up > /usr/libdata/perl/5.6.0/Config.pm, which has "/usr/local" wired > through it as a prefix for nearly everything. > I suspect the ideal situation would be for the Perl module installer > to detect (how?) to try and sniff LOCALBASE out of /etc/make.conf if > this is part of a port install. If that works, use LOCALBASE. > Otherwise, use the default Config.pm values. People who want that > default to be something other than /usr/local can then change those > values themselves. IMHO, the easiest thing to do would be to modify the Config.pm itself. For example, it might look for, say, PERL_USE_PREFIX environment variable and change its %Config accordingly. Then the Makefiles in p5 ports will just set this variable to whatever LOCALBASE is, before invoking perl Makefile.PL. There is another problem with your idea, though. Such Perl modules will not be found by perl unless PERL5LIB points to the right place, i.e. your installed p5 ports will not work out of the box. That is pretty bad, and setting PERL5LIB globally will not help much since at least some people set it to their private directories without spelling PERL5LIB=$PERL5LIB:bla mantra. > Is there someone who can *fix* this? Cheers, -- Anton Berezin The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 6:42:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 072D437B6FA for ; Mon, 31 Jul 2000 06:42:15 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13JFp4-000HrQ-00; Mon, 31 Jul 2000 15:41:38 +0200 From: Sheldon Hearn To: Anton Berezin Cc: Mike Meyer , current@FreeBSD.ORG Subject: Re: perl vs. LOCALBASE, again In-reply-to: Your message of "Mon, 31 Jul 2000 15:23:50 +0200." <20000731152350.U48988@plab.ku.dk> Date: Mon, 31 Jul 2000 15:41:38 +0200 Message-ID: <68659.965050898@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When discussing things like this, where the problem area has a known maintainer, I think that it's wise to include that maintainer in the discussion. Yes, FreeBSD developers are expected to read their -current mail, but in reality, the high level of noise on this list tends to make people very quick with their mailer's deletion facility. In this case, you should chat to Mark Murray . 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 Jul 31 7:39:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id CFF1637B625 for ; Mon, 31 Jul 2000 07:39:20 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 10961 invoked from network); 31 Jul 2000 14:39:19 -0000 Received: from acs-24-154-24-131.zoominternet.net (24.154.24.131) by scully.zoominternet.net with SMTP; 31 Jul 2000 14:39:19 -0000 Date: Mon, 31 Jul 2000 10:39:19 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-24-131.zoominternet.net To: current@freebsd.org Subject: PCM failures w/ latest commits Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-665199622-965054359=:241" 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-665199622-965054359=:241 Content-Type: TEXT/PLAIN; charset=US-ASCII When I try to play an mp3 with either realplayer 7 or mpg123, I get Can't open /dev/dsp! But, the same exact configuration always worked before. - Donn --0-665199622-965054359=:241 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: dmesg output Content-Disposition: attachment; filename="dmesg.out" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk3OSwgMTk4MCwgMTk4MywgMTk4NiwgMTk4OCwg MTk4OSwgMTk5MSwgMTk5MiwgMTk5MywgMTk5NA0KCVRoZSBSZWdlbnRzIG9m IHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuIEFsbCByaWdodHMgcmVz ZXJ2ZWQuDQpGcmVlQlNEIDUuMC1DVVJSRU5UICMwOiBNb24gSnVsIDMxIDEw OjI2OjAzIEVEVCAyMDAwDQogICAgZG1taWxsZXJAYWNzLTI0LTE1NC0yNC0x MzEuem9vbWludGVybmV0Lm5ldDovdXNyL3NyYy9zeXMvY29tcGlsZS9DVVNU T00NClRpbWVjb3VudGVyICJpODI1NCIgIGZyZXF1ZW5jeSAxMTkzMTgyIEh6 DQpUaW1lY291bnRlciAiVFNDIiAgZnJlcXVlbmN5IDE2NjQ1MDUyMiBIeg0K Q1BVOiBQZW50aXVtL1A1NUMgKDE2Ni40NS1NSHogNTg2LWNsYXNzIENQVSkN CiAgT3JpZ2luID0gIkdlbnVpbmVJbnRlbCIgIElkID0gMHg1NDMgIFN0ZXBw aW5nID0gMw0KICBGZWF0dXJlcz0weDgwMDFiZjxGUFUsVk1FLERFLFBTRSxU U0MsTVNSLE1DRSxDWDgsTU1YPg0KcmVhbCBtZW1vcnkgID0gNjI5MTQ1NjAg KDYxNDQwSyBieXRlcykNCmF2YWlsIG1lbW9yeSA9IDU3NzY5OTg0ICg1NjQx NksgYnl0ZXMpDQpQcmVsb2FkZWQgZWxmIGtlcm5lbCAia2VybmVsIiBhdCAw eGMwMzc4MDAwLg0KUHJlbG9hZGVkIHVzZXJjb25maWdfc2NyaXB0ICIvYm9v dC9rZXJuZWwuY29uZiIgYXQgMHhjMDM3ODA5Yy4NCkludGVsIFBlbnRpdW0g ZGV0ZWN0ZWQsIGluc3RhbGxpbmcgd29ya2Fyb3VuZCBmb3IgRjAwRiBidWcN Cm1kMDogTWFsbG9jIGRpc2sNCm5weDA6IDxtYXRoIHByb2Nlc3Nvcj4gb24g bW90aGVyYm9hcmQNCm5weDA6IElOVCAxNiBpbnRlcmZhY2UNCnBjaWIwOiA8 SG9zdCB0byBQQ0kgYnJpZGdlPiBvbiBtb3RoZXJib2FyZA0KcGNpMDogPFBD SSBidXM+IG9uIHBjaWIwDQpwY2kwOiA8SG9zdCB0byBQQ0kgYnJpZGdlICh2 ZW5kb3I9MTAzOSBkZXZpY2U9NTU5Nyk+IGF0IDAuMA0KaXNhYjA6IDxTaVMg ODVjNTAzIFBDSS1JU0EgYnJpZGdlPiBhdCBkZXZpY2UgMS4wIG9uIHBjaTAN CmlzYTA6IDxJU0EgYnVzPiBvbiBpc2FiMA0KYXRhcGNpMDogPFNpUyA1NTkx IEFUQTMzIGNvbnRyb2xsZXI+IHBvcnQgMHhkMDAwLTB4ZDAwZiwweGQ0MDAt MHhkNDAzLDB4ZDgwMC0weGQ4MDcsMHhlMDAwLTB4ZTAwMywweGU0MDAtMHhl NDA3IGlycSAxMSBhdCBkZXZpY2UgMS4xIG9uIHBjaTANCmF0YTA6IGF0IDB4 MWYwIGlycSAxNCBvbiBhdGFwY2kwDQphdGExOiBhdCAweDE3MCBpcnEgMTUg b24gYXRhcGNpMA0KZWQwOiA8TkUyMDAwIFBDSSBFdGhlcm5ldCAoUmVhbFRl ayA4MDI5KT4gcG9ydCAweGI4MDAtMHhiODFmIGlycSAxMCBhdCBkZXZpY2Ug MTAuMCBvbiBwY2kwDQplZDA6IGFkZHJlc3MgMDA6YzA6ZGY6ZWQ6MGI6MTcs IHR5cGUgTkUyMDAwICgxNiBiaXQpIA0KcGNpMDogPFNpUyA1NTk3Lzk4IFNW R0EgY29udHJvbGxlcj4gYXQgMTkuMCBpcnEgMTENCnZnYTA6IDxHZW5lcmlj IElTQSBWR0E+IGF0IHBvcnQgMHgzYzAtMHgzZGYgaW9tZW0gMHhhMDAwMC0w eGJmZmZmIG9uIGlzYTANCnNjMDogPFN5c3RlbSBjb25zb2xlPiBvbiBpc2Ew DQpzYzA6IFZHQSA8MTYgdmlydHVhbCBjb25zb2xlcywgZmxhZ3M9MHgyMDA+ DQpmZGMwOiA8TkVDIDcyMDY1QiBvciBjbG9uZT4gYXQgcG9ydCAweDNmMC0w eDNmNSwweDNmNyBpcnEgNiBkcnEgMiBvbiBpc2EwDQpmZGMwOiBGSUZPIGVu YWJsZWQsIDggYnl0ZXMgdGhyZXNob2xkDQpmZDA6IDwxNDQwLUtCIDMuNSIg ZHJpdmU+IG9uIGZkYzAgZHJpdmUgMA0KYXRrYmRjMDogPEtleWJvYXJkIGNv bnRyb2xsZXIgKGk4MDQyKT4gYXQgcG9ydCAweDYwLDB4NjQgb24gaXNhMA0K YXRrYmQwOiA8QVQgS2V5Ym9hcmQ+IGZsYWdzIDB4MSBpcnEgMSBvbiBhdGti ZGMwDQprYmQwIGF0IGF0a2JkMA0Kc2lvMiBhdCBwb3J0IDB4M2U4LTB4M2Vm IGlycSA0IG9uIGlzYTANCnNpbzI6IHR5cGUgMTY1NTBBDQptc2UwOiA8QnVz L0luUG9ydCBNb3VzZT4gYXQgcG9ydCAweDIzYy0weDIzZiBpcnEgMyBvbiBp c2EwDQpwcGMwOiA8RUNQIHBhcmFsbGVsIHByaW50ZXIgcG9ydD4gYXQgcG9y dCAweDM3OC0weDM3ZiwweDc3OC0weDc3ZiBpcnEgNyBkcnEgMyBvbiBpc2Ew DQpwcGMwOiBTTUMtbGlrZSBjaGlwc2V0IChFQ1AvRVBQL1BTMi9OSUJCTEUp IGluIENPTVBBVElCTEUgbW9kZQ0KcHBjMDogRklGTyB3aXRoIDE2LzE2LzE2 IGJ5dGVzIHRocmVzaG9sZA0KcHBpMDogPFBhcmFsbGVsIEkvTz4gb24gcHBi dXMwDQpscHQwOiA8UHJpbnRlcj4gb24gcHBidXMwDQpscHQwOiBJbnRlcnJ1 cHQtZHJpdmVuIHBvcnQNCnBsaXAwOiA8UExJUCBuZXR3b3JrIGludGVyZmFj ZT4gb24gcHBidXMwDQp1bmtub3duOiA8UE5QMDUwMT4gY2FuJ3QgYXNzaWdu IHJlc291cmNlcw0KdW5rbm93bjogPFBOUDA1MDE+IGNhbid0IGFzc2lnbiBy ZXNvdXJjZXMNCnVua25vd246IDxQTlAwNzAwPiBjYW4ndCBhc3NpZ24gcmVz b3VyY2VzDQp1bmtub3duOiA8UE5QMDMwMz4gY2FuJ3QgYXNzaWduIHJlc291 cmNlcw0Kc2JjMDogPEVTUyBFUzE4Njg+IGF0IHBvcnQgMHgyMjAtMHgyMmYs MHgzODgtMHgzOGIsMHgzMzAtMHgzMzEgaXJxIDUgZHJxIDEsMCBvbiBpc2Ew DQpwY20wOiA8RVNTIDE4eHggRFNQPiBvbiBzYmMwDQphZDA6IDMwOTNNQiA8 RlVKSVRTVSBNUEIzMDMyQVRVPiBbNjcwNC8xNS82M10gYXQgYXRhMC1tYXN0 ZXIgdXNpbmcgVURNQTMzDQphZDE6IDEwNDBNQiA8TTE2MTRUQT4gWzIxMTQv MTYvNjNdIGF0IGF0YTAtc2xhdmUgdXNpbmcgV0RNQTINCmFjZDA6IENEUk9N IDxCQ0QtMjRYIDE5OTctMDYtMjc+IGF0IGF0YTEtbWFzdGVyIHVzaW5nIFdE TUEyDQo= --0-665199622-965054359=:241-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 9:50: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from m08.alpha-net.ne.jp (m08.alpha-net.ne.jp [210.229.64.38]) by hub.freebsd.org (Postfix) with ESMTP id 75EE037B884 for ; Mon, 31 Jul 2000 09:50:04 -0700 (PDT) (envelope-from k5@cheerful.com) Received: from kyoto-tc012-p135.alpha-net.ne.jp (kyoto-tc012-p135.alpha-net.ne.jp [210.237.118.169]) by m08.alpha-net.ne.jp (8.9.3/3.7W) with ESMTP id BAA29376 for ; Tue, 1 Aug 2000 01:49:06 +0900 (JST) Received: from souffle.bogus-local.net (souffle.bogus-local.net [192.168.1.1]) by kyoto-tc012-p135.alpha-net.ne.jp (Postfix) with ESMTP id E53F13D73 for ; Tue, 1 Aug 2000 01:50:02 +0900 (JST) Date: Tue, 01 Aug 2000 01:50:02 +0900 Message-ID: <86vgxmdz2d.wl@cheerful.com> From: FUJISHIMA Satsuki To: current@freebsd.org Subject: Re: Mozilla-M15+ipv6 package available In-Reply-To: In your message of "Mon, 31 Jul 2000 05:31:50 -0400" <39854786.ED4A28B5@cvzoom.net> References: <39854786.ED4A28B5@cvzoom.net> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.7 (i386--freebsd) MULE/4.1 (AOI) 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 At Mon, 31 Jul 2000 05:31:50 -0400, Donn Miller wrote: > The last few Mozillas I tried compiling from source (on -current), I'd > get a message in xterm saying the document was fully loaded, but yet > no window would appear. It seemed like a problem with threading. > Anyone else see this? Did you rm -r ~/.mozilla first? Mozilla configuration files sometimes incompatible across milestones so it is recommended to remove it when you happened to see weird problem as such. I've been tracking mozilla since M13 on -CURRENT and it mostly compiles and runs. I can't say it runs *fine* though :-) -- FUJISHIMA Satsuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 9:52:18 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 626D137BB91; Mon, 31 Jul 2000 09:52:11 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA75820; Mon, 31 Jul 2000 09:52:10 -0700 (PDT) (envelope-from obrien) Date: Mon, 31 Jul 2000 09:52:10 -0700 From: "David O'Brien" To: Kris Kennaway Cc: current@FreeBSD.org, net@FreeBSD.org Subject: Re: Mozilla-M15+ipv6 package available Message-ID: <20000731095210.A75780@dragon.nuxi.com> Reply-To: obrien@FreeBSD.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 kris@FreeBSD.org on Mon, Jul 31, 2000 at 01:39:29AM -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 Mon, Jul 31, 2000 at 01:39:29AM -0700, Kris Kennaway wrote: > A few people have asked me for this, so I uploaded a package of the > mozilla-M15+ipv6 port from KAME to ..snip.. > The patches aren't quite suitable for committing to the ports collection > because they unconditionally enable support for IPv6 which may not work on > 3.x machines, So what??? Mark it broken for 3.x. Ask Satoshi to repo-copy the mozilla port to mozilla-ipv6 and make this a real port. :-) -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 10:53:51 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 B802637B52A for ; Mon, 31 Jul 2000 10:53:47 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id TAA83490 for freebsd-current@FreeBSD.ORG; Mon, 31 Jul 2000 19:53:44 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id TAA11924 for ; Mon, 31 Jul 2000 19:53:29 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <007701bffb18$4e58e9e0$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: Subject: ppp.linkdown Date: Mon, 31 Jul 2000 19:49:35 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is ppp.linkdown executed before or after the link is down? I'd like to change a dyndns, but will link activity done in linkdown defeat the timeout, or start a new call? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 12:47:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id D4B4A37BBFB; Mon, 31 Jul 2000 12:47:21 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:mMFAInxt4sobaOGJI6A0o2jLLJrUAWD3OcusDett762rh6l3DO1B7iCejo+lhgR+@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.0/3.7W-peace) with ESMTP id e6VJkph14993; Tue, 1 Aug 2000 04:46:51 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 01 Aug 2000 04:46:47 +0900 (JST) Message-Id: <20000801.044647.63121670.ume@mahoroba.org> To: kris@FreeBSD.org Cc: current@freebsd.org, net@freebsd.org Subject: Re: Mozilla-M15+ipv6 package available In-Reply-To: References: From: Hajimu UMEMOTO X-Mailer: Mew version 1.95b38 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Mon, 31 Jul 2000 01:39:29 -0700 (PDT) >>>>> Kris Kennaway said: kris> A few people have asked me for this, so I uploaded a package of the kris> mozilla-M15+ipv6 port from KAME to kris> http://www.freebsd.org/~kris/mozilla-M15.tgz kris> (yes, I know M16 is out, but the port isn't yet updated). kris> Install this package and you too can see the dancing kame at kris> http://www.kame.net, the current hilight of the inet6! kris> The patches aren't quite suitable for committing to the ports collection kris> because they unconditionally enable support for IPv6 which may not work on kris> 3.x machines, but if anyone is interested in looking at them then please kris> let me know. And, IPv6 support of Mozilla is heavily depend on mapped address. So, IPv6 enabled Mozilla requires IPv6 awareness of kernel even if IPv4 only access. -- 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 Mon Jul 31 13:43:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (Postfix) with ESMTP id E2B2C37B5A0; Mon, 31 Jul 2000 13:43:34 -0700 (PDT) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.3/8.9.3) with ESMTP id WAA04559; Mon, 31 Jul 2000 22:43:58 +0200 (CEST) (envelope-from k@numeri.campus.luth.se) Message-Id: <200007312043.WAA04559@numeri.campus.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: marcel@FreeBSD.org Cc: current@FreeBSD.org Subject: Minor problems with build/installkernel Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Mon, 31 Jul 2000 22:43:58 +0200 From: Johan Karlsson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [current cc:ed since this might be interesting] Hi Marcel Can you please have a look at some PRs which deals with some minor proble= m with the buldkernel/installkernel targets of Makefile.inc1 and the install-modules target of sys/conf/Makefile.${MACHINE} I think you are the right person for this since you have done most = of the recent work with these targets. PR 20325 http://www.freebsd.org/cgi/query-pr.cgi?pr=3D20325 If KERNEL=3DGENRIC is set in /etc/make.conf the build/installkernel will create/install kernel as 'GENERIC'. PR 20326 http://www.freebsd.org/cgi/query-pr.cgi?pr=3D20326 If DESTDIR=3Dpath_to_empty_dir installkernel will fail. PR 20327 http://www.freebsd.org/cgi/query-pr.cgi?pr=3D20327 When backing-up modules ${KMODDIR} should be used instead of /modules Thanks Johan K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 14: 0:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 0900837B553; Mon, 31 Jul 2000 14:00:51 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 3A13CA0D; Mon, 31 Jul 2000 14:00:19 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id OAA20396; Mon, 31 Jul 2000 14:00:09 -0700 (PDT) Message-ID: <3985E8D8.CD90C863@cup.hp.com> Date: Mon, 31 Jul 2000 14:00:08 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Johan Karlsson Cc: marcel@FreeBSD.org, current@FreeBSD.org Subject: Re: Minor problems with build/installkernel References: <200007312043.WAA04559@numeri.campus.luth.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johan Karlsson wrote: > > Can you please have a look at some PRs which deals with some minor problem > with the buldkernel/installkernel targets of Makefile.inc1 and the > install-modules target of sys/conf/Makefile.${MACHINE} I will. Thanks for the pointers, -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 14:22:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0F6E537B553; Mon, 31 Jul 2000 14:22:32 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA91215; Mon, 31 Jul 2000 14:22:31 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 31 Jul 2000 14:22:31 -0700 (PDT) From: Kris Kennaway To: Alexander Langer Cc: Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: sort(1) broken? In-Reply-To: <20000731152139.A39969@cichlids.cichlids.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, 31 Jul 2000, Alexander Langer wrote: > Thus spake Brian Fundakowski Feldman (green@FreeBSD.ORG): > > > I'm doubtful it's the only one of it's kind in GNU sort(1). Time for BSD > > sort(1)? > > What about BSD/OS's sort? BSD/OS userland is almost completely untouched from the 4.4BSD sources. NetBSD and OpenBSD at least work on their tools (and also use BSD sort) :-) 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 Jul 31 18: 4:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 14E0637B6ED; Mon, 31 Jul 2000 18:04:21 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id EC61149; Mon, 31 Jul 2000 21:04:17 -0400 (AST) Message-ID: <39862211.166FACF4@vangelderen.org> Date: Mon, 31 Jul 2000 21:04:17 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray Cc: Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <200007300918.LAA07595@grimreaper.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > > Mark already stated that in *practicality*, Yarrow-BF-cbc-256 1.0 > > (I guess that's the proper name for this :-) is complex enough and > > generates good enough ouput. If you /really/ want to make the attack > > on it much harder, how about this: if you're going to read 1024 bits > > of entropy from Yarrow on /dev/random, you will request it all at once > > and block just as the old random(4) used to block; the blocking can > > occur at 256 bit intervals and sleep until there is a reseed. Waiting > > to reseed for each read will ensure a much larger amount of "real" > > entropy than it "maybe" happening at random times. > > This is a reversion to the count-entropy-and-block model which I have > been fiercely resisting (and which argument I thought I had sucessfully > defended). You argued successfully against using the old PRNG mechanism but not against the blocking bit. What is your rationale for not doing the blocking when the client actually wants a guarantee that entropy is not being re-used? > My solution is to get the entropy gathering at a high enough rate that > this is not necessary. What if you cannot guarantee that (and you cannot guarantee that in practice)? > I also agreed to _maybe_ look at a re-engineer of the "old" code in a > secure way if a decent algorithm could be found (I am reading some > papers about this ATM). Why would you if you can provide blocking with Yarrow? Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 18:10:11 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 170B737BE20 for ; Mon, 31 Jul 2000 18:10:02 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id DAA33540; Tue, 1 Aug 2000 03:09:47 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id CAA22033; Tue, 1 Aug 2000 02:52:14 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Tue, 1 Aug 2000 02:51:45 +0200 (CEST) From: Leif Neland To: Garrett Wollman Cc: freebsd-current@FreeBSD.ORG Subject: Re: sendmail 8.11.0 trouble In-Reply-To: <200007301840.OAA03021@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jul 2000, Garrett Wollman wrote: > < said: > > >> On Sunday, July 30, 2000, Leif Neland wrote: > > >> > Sendmail 8.11.0 > >> > > >> > When invoking sendmail or newaliases I get this message: > >> > /etc/pwd.db: Invalid argument > >> > > >> > Sendmail can't read /etc/pwd.db, and therefore cannot deliver any local > >> > mail. > >> > > >> > Howtofixitplease? > > Sounds like you're using the wrong version of Berkeley DB (i.e., not > the one in libc). Can't fathom how this could override the internal > linkage in libc, though. > There seems indeed to be a confusion of the .db's: /etc/mail/aliases.db: MS Windows COFF Unknown CPU /etc/pwd.db: Berkeley DB Hash file (Version 2, Little Endian, Bucket Size 4096, Bucket Shift 12, Directory Size 256, Segment Size 256, Segment Shift 8, Overflow Point 3, Last Freed 2, Max Bucket 7, High Mask 0xf, Low Mask 0x7, Fill Factor 32, Number of Keys 52) Sendmail compiles with -DNEWDB I had db 2.something installed from the ports. I uninstalled it, it made no difference. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 21:58:58 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 D4A3637B52F for ; Mon, 31 Jul 2000 21:58:50 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id GAA19553 for freebsd-current@FreeBSD.ORG; Tue, 1 Aug 2000 06:58:48 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.0/8.9.3) with ESMTP id e714wQ576225 for ; Tue, 1 Aug 2000 06:58:32 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Tue, 1 Aug 2000 06:58:21 +0200 (CEST) From: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: sendmail 8.11.0 trouble 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, 1 Aug 2000, Leif Neland wrote: > > > On Sun, 30 Jul 2000, Garrett Wollman wrote: > > > < said: > > > > >> On Sunday, July 30, 2000, Leif Neland wrote: > > > > >> > Sendmail 8.11.0 > > >> > > > >> > When invoking sendmail or newaliases I get this message: > > >> > /etc/pwd.db: Invalid argument > > >> > > > >> > Sendmail can't read /etc/pwd.db, and therefore cannot deliver any local > > >> > mail. > > >> > > > >> > Howtofixitplease? > > > > Sounds like you're using the wrong version of Berkeley DB (i.e., not > > the one in libc). Can't fathom how this could override the internal > > linkage in libc, though. > > > > There seems indeed to be a confusion of the .db's: > /etc/mail/aliases.db: MS Windows COFF Unknown CPU > /etc/pwd.db: Berkeley DB Hash file (Version 2, Little Endian, Bucket Size 4096, Bucket Shift 12, Directory Size 256, Segment Size 256, Segment Shift 8, Overflow Point 3, Last Freed 2, Max Bucket 7, High Mask 0xf, Low Mask 0x7, Fill Factor 32, Number of Keys 52) > > Sendmail compiles with -DNEWDB > > I had db 2.something installed from the ports. I uninstalled it, it made > no difference. > I compile in /usr/src/sendmail-8.11.0 I nfs-mounted /usr/src and /usr/obj to an a little older current (like when I do a make installworld to the older machine) I then compiled the same sourcedir with the same options, but now I got a sendmail binary, which understands Berkley DB Hash file (version 2). Then I could "./Build install" a working sendmail on the original machine. Something on the original machine must trigger a wrong db type in sendmail build. Strange... Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 22:37:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from manatee.mammalia.org (manatee.mammalia.org [216.231.50.6]) by hub.freebsd.org (Postfix) with ESMTP id 85EC137BE0A for ; Mon, 31 Jul 2000 22:37:49 -0700 (PDT) (envelope-from rjoseph@mammalia.org) Received: by manatee.mammalia.org (Postfix, from userid 1000) id 5C1C211CDCA; Mon, 31 Jul 2000 22:37:48 -0700 (PDT) Date: Mon, 31 Jul 2000 22:37:48 -0700 From: R Joseph Wright To: freebsd-current Subject: panic at shutdown Message-ID: <20000731223748.A324@mammalia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just built a new world/kernel yesterday, and now I get a panic when I shut down. I ran gdb on the dump: ...... There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2998272 initial pcb at 25b1c0 panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking panic messages: --- --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 303 dumppcb.pcb_cr3 = rcr3(); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 31 22:40:38 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 1F22337B59B for ; Mon, 31 Jul 2000 22:40:36 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 634BF1C64; Tue, 1 Aug 2000 01:40:35 -0400 (EDT) Date: Tue, 1 Aug 2000 01:40:35 -0400 From: Bill Fumerola To: R Joseph Wright Cc: freebsd-current Subject: Re: panic at shutdown Message-ID: <20000801014035.M5021@jade.chc-chimes.com> References: <20000731223748.A324@mammalia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000731223748.A324@mammalia.org>; from rjoseph@mammalia.org on Mon, Jul 31, 2000 at 10:37:48PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 31, 2000 at 10:37:48PM -0700, R Joseph Wright wrote: > I just built a new world/kernel yesterday, and now I get a panic when I shut > down. I ran gdb on the dump: > > ...... > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"... > IdlePTD 2998272 > initial pcb at 25b1c0 > panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking > panic messages: > --- > --- > #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 > 303 dumppcb.pcb_cr3 = rcr3(); type 'bt', this tells us just about as much as if you said "it crashed". though, by the panic message, this seems to be a known bug.. -- 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 Mon Jul 31 22:54: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from manatee.mammalia.org (manatee.mammalia.org [216.231.50.6]) by hub.freebsd.org (Postfix) with ESMTP id CE33F37B7A7 for ; Mon, 31 Jul 2000 22:53:56 -0700 (PDT) (envelope-from rjoseph@mammalia.org) Received: by manatee.mammalia.org (Postfix, from userid 1000) id 44A6811CDCA; Mon, 31 Jul 2000 22:53:56 -0700 (PDT) Date: Mon, 31 Jul 2000 22:53:56 -0700 From: R Joseph Wright To: Bill Fumerola Cc: freebsd-current Subject: Re: panic at shutdown Message-ID: <20000731225356.A397@mammalia.org> References: <20000731223748.A324@mammalia.org> <20000801014035.M5021@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000801014035.M5021@jade.chc-chimes.com>; from billf@chimesnet.com on Tue, Aug 01, 2000 at 01:40:35AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And Bill Fumerola spoke: > On Mon, Jul 31, 2000 at 10:37:48PM -0700, R Joseph Wright wrote: > > I just built a new world/kernel yesterday, and now I get a panic when I shut > > down. I ran gdb on the dump: > > > > ...... > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > This GDB was configured as "i386-unknown-freebsd"... > > IdlePTD 2998272 > > initial pcb at 25b1c0 > > panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking > > panic messages: > > --- > > --- > > #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 > > 303 dumppcb.pcb_cr3 = rcr3(); > > type 'bt', this tells us just about as much as if you said > "it crashed". > > though, by the panic message, this seems to be a known bug.. > > -- > Bill Fumerola - Network Architect, BOFH / Chimes, Inc. > billf@chimesnet.com / billf@FreeBSD.org Sorry :) GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2998272 initial pcb at 25b1c0 panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking panic messages: --- --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 303 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 #1 0xc014bd28 in poweroff_wait (junk=0xc02010a0, howto=1) at ../../kern/kern_shutdown.c:553 #2 0xc0146af0 in lockmgr (lkp=0xc0c50a00, flags=6, interlkp=0xc87108ac, p=0xc7d4be00) at ../../kern/kern_lock.c:382 #3 0xc01779ab in vop_stdunlock (ap=0xc7d51e48) at ../../kern/vfs_default.c:255 #4 0xc01b6ccd in ufs_vnoperate (ap=0xc7d51e48) at ../../ufs/ufs/ufs_vnops.c:2301 #5 0xc01b1bab in ufs_inactive (ap=0xc7d51e78) at vnode_if.h:865 #6 0xc01b6ccd in ufs_vnoperate (ap=0xc7d51e78) at ../../ufs/ufs/ufs_vnops.c:2301 #7 0xc017a726 in vput (vp=0xc8710840) at vnode_if.h:794 #8 0xc01aee87 in ffs_sync (mp=0xc0ade800, waitfor=2, cred=0xc0721700, p=0xc026d5e0) at ../../ufs/ffs/ffs_vfsops.c:955 #9 0xc017c605 in sync (p=0xc026d5e0, uap=0x0) at ../../kern/vfs_syscalls.c:551 #10 0xc014b777 in boot (howto=0) at ../../kern/kern_shutdown.c:225 #11 0xc014b578 in reboot (p=0xc7d4be00, uap=0xc7d51f80) at ../../kern/kern_shutdown.c:146 #12 0xc01ecd21 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077936612, tf_esi = -1077936624, tf_ebp = -1077936836, tf_isp = -942333996, tf_ebx = -1077936732, tf_edx = -1, tf_ecx = 4, tf_eax = 55, tf_trapno = 7, tf_err = 2, tf_eip = 134536452, tf_cs = 31, tf_eflags = 643, tf_esp = -1077937056, tf_ss = 47}) at ../../i386/i386/trap.c:1128 #13 0xc01e1ab5 in Xint0x80_syscall () #14 0x80486ee in ?? () #15 0x8048478 in ?? () #16 0x8048139 in ?? () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 1:58:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id 7F88337BB51 for ; Tue, 1 Aug 2000 01:58:13 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (root@daemon.ninth-circle.org [195.38.210.81]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id e718vw998041; Tue, 1 Aug 2000 10:57:58 +0200 (CEST) Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id KAA53987; Tue, 1 Aug 2000 10:08:19 +0200 (CEST) (envelope-from asmodai) Date: Tue, 1 Aug 2000 10:08:18 +0200 From: Jeroen Ruigrok/Asmodai To: Alexander Leidinger Cc: dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: phkmalloc & pam_ssh & xdm Message-ID: <20000801100818.P32129@daemon.ninth-circle.org> References: <3984DAC1.4ACBF964@newsguy.com> <200007311223.OAA39940@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007311223.OAA39940@Magelan.Leidinger.net>; from Alexander@Leidinger.net on Mon, Jul 31, 2000 at 02:23:07PM +0200 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000731 15:24], Alexander Leidinger (Alexander@Leidinger.net) wrote: >I rebuilded libssh.a and pam_ssh.so with this patch and I didn't get the >error anymore. > >I haven't rebuilded the world or anything openssh related, but I think >this should work (and because of the readability of pam_ssh.c and >authfd.c it was easy to trace only by looking at the source... it seems >using FreeBSD is the "Right Thing[TM]" :) ). It survived at least a make world here. Committed. Thanks. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Abandon hope, all ye who enter here... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 2: 6:40 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 AB04D37B5E9 for ; Tue, 1 Aug 2000 02:06:25 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #2) id 13JY0B-0002lg-00; Tue, 01 Aug 2000 11:06:19 +0200 Received: from a38fc.pppool.de ([213.6.56.252] helo=Magelan.Leidinger.net) by mx2.freenet.de with esmtp (Exim 3.16 #2) id 13JY0B-00029h-00; Tue, 01 Aug 2000 11:06:19 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id JAA01204; Tue, 1 Aug 2000 09:34:01 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200008010734.JAA01204@Magelan.Leidinger.net> Date: Tue, 1 Aug 2000 09:33:59 +0200 (CEST) From: Alexander Leidinger Subject: Re: panic at shutdown To: billf@chimesnet.com Cc: rjoseph@mammalia.org, freebsd-current@FreeBSD.ORG In-Reply-To: <20000801014035.M5021@jade.chc-chimes.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1 Aug, Bill Fumerola wrote: >> #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 >> 303 dumppcb.pcb_cr3 = rcr3(); > > type 'bt', this tells us just about as much as if you said > "it crashed". > > though, by the panic message, this seems to be a known bug.. If I see the same bug everybody complains about: add "sync; sleep 1; sync; sleep 1; sync" to rc.shutdown to work round it (I'm using kernel sources from yesterday). Bye, Alexander. -- To boldly go where I surely don't belong. 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 Tue Aug 1 3:27:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.email.msn.com (cpimssmtpu03.email.msn.com [207.46.181.19]) by hub.freebsd.org (Postfix) with ESMTP id 5AA6C37B84E for ; Tue, 1 Aug 2000 03:27:21 -0700 (PDT) (envelope-from bonk1138@msn.com) Received: from lando - 63.15.5.230 by email.msn.com with Microsoft SMTPSVC; Tue, 1 Aug 2000 03:26:49 -0700 From: "James Johnson" To: Subject: netinet compile broken Date: Tue, 1 Aug 2000 03:25:35 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sys/netinet/ip_fil.c appears to be busted. Trying to recompile kernel modules breaks as follows: ===> ipfilter cc -O -pipe -DIPFILTER=1 -DIPFILTER_LKM -DIPFILTER_LOG -D_KERNEL -Wall -Wre dundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wp ointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -n ostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/ipfilter/../../netinet/ip_fil.c /usr/src/sys/modules/ipfilter/../../netinet/ip_fil.c: In function `iplattach': /usr/src/sys/modules/ipfilter/../../netinet/ip_fil.c:272: too few arguments to function `pfil_add_hook' /usr/src/sys/modules/ipfilter/../../netinet/ip_fil.c: In function `ipldetach': /usr/src/sys/modules/ipfilter/../../netinet/ip_fil.c:384: too few arguments to function `pfil_remove_hook' *** Error code 1 Looks like two else statements were commented out. This simple diff fixes it --- ip_fil.c Tue Aug 1 00:04:24 2000 +++ ip_fil.bak Tue Aug 1 03:18:08 2000 @@ -268,7 +268,7 @@ return error; # endif } -# else + else pfil_add_hook((void *)fr_check, PFIL_IN|PFIL_OUT); # endif # ifdef USE_INET6 @@ -380,7 +380,7 @@ &inetsw[ip_protox[IPPROTO_IP]].pr_pfh); if (error) return error; -# else + else pfil_remove_hook((void *)fr_check, PFIL_IN|PFIL_OUT); # endif # ifdef USE_INET6 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 3:47:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (hermes.dialup.ru [194.87.16.230]) by hub.freebsd.org (Postfix) with ESMTP id AB7D837B89D for ; Tue, 1 Aug 2000 03:47:31 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id FAA00290 for current@freebsd.org; Tue, 1 Aug 2000 05:39:25 +0400 (MSD) (envelope-from ache) Date: Tue, 1 Aug 2000 05:39:23 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: tail is ubreakable by ^C and cause system hang Message-ID: <20000801053923.A281@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just build fresh kernel and see that it is impossible to interrupt tail with ^C - it cause hang (with tty driver and screens switching still alive, but not other things). -- 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 Tue Aug 1 3:59:41 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id B70C537B84E; Tue, 1 Aug 2000 03:59:37 -0700 (PDT) Date: Tue, 1 Aug 2000 03:59:37 -0700 From: "Andrey A. Chernov" To: current@freebsd.org Subject: Re: tail is ubreakable by ^C and cause system hang Message-ID: <20000801035936.A28567@freebsd.org> References: <20000801053923.A281@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000801053923.A281@nagual.pp.ru>; from ache@nagual.pp.ru on Tue, Aug 01, 2000 at 05:39:23AM +0400 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 01, 2000 at 05:39:23AM +0400, Andrey A. Chernov wrote: > Just build fresh kernel and see that it is impossible to interrupt tail > with ^C - it cause hang (with tty driver and screens switching still > alive, but not other things). Seems to be fixed in new kern_event.c v1.14 -- 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 Tue Aug 1 4:19:54 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 CF1B237BEFD for ; Tue, 1 Aug 2000 04:19:50 -0700 (PDT) (envelope-from kuriyama@imgsrc.co.jp) 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 e71BJkG13415 for ; Tue, 1 Aug 2000 20:19:47 +0900 (JST) Date: Tue, 01 Aug 2000 20:19:46 +0900 Message-ID: <7mn1ix2ppp.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: ssh -2 -v displays debug messages when typed User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 10) (Capitol Reef) (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 On my -current environment, ssh -2 -v (Version 2 protocol with DSA, verbose mode) displays debug message to tty whenever I typed. If I use version 1 protocol, debug messages are not displayed after logged in to another system. Is this expected behaviour? ----- % ssh -2 -v localhost SSH Version OpenSSH-2.1, protocol versions 1.5/2.0. Compiled with SSL (0x0090581f). ... (debug messages) Welcome to FreeBSD! % debug: channel 0: send data len 1 (typed 'd') ddebug: channel 0: send data len 1 (typed 'a') adebug: channel 0: send data len 1 (typed 't') tdebug: channel 0: send data len 1 (typed 'e') edebug: channel 0: send data len 1 (typed [Enter]) Tue Aug 1 20:17:00 JST 2000 % ----- -- 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 Tue Aug 1 4:21:58 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 3685037BF5D for ; Tue, 1 Aug 2000 04:21:53 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-195-14-254-188.netcologne.de [195.14.254.188]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id NAA05433 for ; Tue, 1 Aug 2000 13:21:51 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.2/8.10.2) with ESMTP id e71BLij01368 for ; Tue, 1 Aug 2000 13:21:44 +0200 (CEST) Date: Tue, 1 Aug 2000 13:21:43 +0200 (CEST) From: Paul Herman To: freebsd-current@freebsd.org Subject: Moused behaving funny in 4.1-STABLE 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, (Posting to current, because of similar problems to the "Mouse behaving funny since 5.0-CURRENT upgrade" thread) My moused is also behaving funny (no X). Sometimes other charaters on the screen get messed up where the pointer never was (I can't seem to reliably reproduce it), but one thing I am able to reproduce is the 20% interrupt thing: When both the prompt and the mouse are at the bottom of the screen, then it starts eating up interrupt CPU. I'm running 4.1-STABLE from 3 days ago. Ideas? -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 4:55: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id DC0F737B5AF for ; Tue, 1 Aug 2000 04:55:02 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 12226 invoked from network); 1 Aug 2000 11:55:02 -0000 Received: from acs-24-154-24-131.zoominternet.net (24.154.24.131) by scully.zoominternet.net with SMTP; 1 Aug 2000 11:55:02 -0000 Date: Tue, 1 Aug 2000 07:55:01 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-24-131.zoominternet.net To: Paul Herman Cc: freebsd-current@freebsd.org Subject: Moused and Yarrow (Re: Moused behaving funny in 4.1-STABLE) 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, 1 Aug 2000, Paul Herman wrote: > My moused is also behaving funny (no X). Sometimes other charaters on > the screen get messed up where the pointer never was (I can't seem to > reliably reproduce it), but one thing I am able to reproduce is the > 20% interrupt thing: > > When both the prompt and the mouse are at the bottom of the screen, > then it starts eating up interrupt CPU. It has something to do with this whole Yarrow thing. I suppose Yarrow (and dev/urandom) are eating up tty interrupts that otherwise would have gone to moused and syscons. Someone on this list suggested implementing some sort of kernel threads, with Yarrow and syscons split up on different kernel threads. AFAIK, this hasn't been implemented yet. So, do we have some sort of kernel threads we could use for this? Or, do we have to compile in Linuxthreads, or something? - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 5:39: 8 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 4238837BBEB for ; Tue, 1 Aug 2000 05:39:03 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-194-8-205-25.netcologne.de [194.8.205.25]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id OAA05417; Tue, 1 Aug 2000 14:39:01 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.2/8.10.2) with ESMTP id e71Ccs003549; Tue, 1 Aug 2000 14:38:54 +0200 (CEST) Date: Tue, 1 Aug 2000 14:38:53 +0200 (CEST) From: Paul Herman To: Donn Miller Cc: freebsd-current@FreeBSD.ORG Subject: Re: Moused and Yarrow (Re: Moused behaving funny in 4.1-STABLE) 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, 1 Aug 2000, Donn Miller wrote: > On Tue, 1 Aug 2000, Paul Herman wrote: > > > When both the prompt and the mouse are at the bottom of the screen, > > then moused starts eating up interrupt CPU. > > It has something to do with this whole Yarrow thing. I suppose Yarrow > (and dev/urandom) are eating up tty interrupts that otherwise would have > gone to moused and syscons. Yeah, I caught that thread, but the problems I'm seeing are in 4.1-STABLE and AFAIK Yarrow hasn't made it to my tree yet (yes, I deserve it, that's what I get for posting to -current). I just thought I'd give -current a holler, because people were noticing a similar thing on this list... I guess I'll try -stable if nobody has any ideas here. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 6:54:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 2355737BB8D for ; Tue, 1 Aug 2000 06:54:17 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.10.1/8.10.1) id e71Drkl05127; Tue, 1 Aug 2000 09:53:46 -0400 (EDT) Date: Tue, 1 Aug 2000 09:53:46 -0400 (EDT) From: Luoqi Chen Message-Id: <200008011353.e71Drkl05127@lor.watermarkgroup.com> To: billf@chimesnet.com, rjoseph@mammalia.org Subject: Re: panic at shutdown Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > #7 0xc017a726 in vput (vp=0xc8710840) at vnode_if.h:794 > #8 0xc01aee87 in ffs_sync (mp=0xc0ade800, waitfor=2, cred=0xc0721700, > p=0xc026d5e0) at ../../ufs/ffs/ffs_vfsops.c:955 Change the vput(vp) call at line 955 of ffs_vfsops.c back to two separate calls (see previous revision): VOP_UNLOCK(vp, 0, p); vrele(vp); vput assumes curproc is the lock holder, but it's not true in this case. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 7:24: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from outpost.hstn.tensor.pgs.com (outpost.hstn.tensor.pgs.com [157.147.25.67]) by hub.freebsd.org (Postfix) with ESMTP id CF51F37B80C for ; Tue, 1 Aug 2000 07:24:00 -0700 (PDT) (envelope-from shocking@hstn.tensor.pgs.com) Received: from hap.hstn.tensor.pgs.com (hap.hstn.tensor.pgs.com [157.147.132.13]) by outpost.hstn.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id JAA00424 for ; Tue, 1 Aug 2000 09:23:58 -0500 (CDT) Received: from penguin.hstn.tensor.pgs.com (penguin.hstn.tensor.pgs.com [157.147.132.155]) by hap.hstn.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id JAA25748 for ; Tue, 1 Aug 2000 09:23:58 -0500 (CDT) Received: from hstn.tensor.pgs.com (localhost [127.0.0.1]) by penguin.hstn.tensor.pgs.com (8.8.8+Sun/8.8.8) with ESMTP id JAA21862 for ; Tue, 1 Aug 2000 09:23:57 -0500 (CDT) Message-Id: <200008011423.JAA21862@penguin.hstn.tensor.pgs.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: VM flakiness since Thursday Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Aug 2000 09:23:57 -0500 From: Steve Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been noticing some crashes (the previously reported by others lock stuff) and some random sig 11s - any one else seeing this? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 7:32:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 972F637BE45 for ; Tue, 1 Aug 2000 07:32:39 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13Jd5i-00050B-00; Tue, 01 Aug 2000 16:32:22 +0200 From: Sheldon Hearn To: Steve Hocking Cc: current@FreeBSD.ORG Subject: Re: VM flakiness since Thursday In-reply-to: Your message of "Tue, 01 Aug 2000 09:23:57 EST." <200008011423.JAA21862@penguin.hstn.tensor.pgs.com> Date: Tue, 01 Aug 2000 16:32:22 +0200 Message-ID: <19230.965140342@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 01 Aug 2000 09:23:57 EST, Steve Hocking wrote: > I've been noticing some crashes (the previously reported by others > lock stuff) and some random sig 11s - any one else seeing this? As a datapoint, I'm running this kernel: 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Fri Jul 28 11:12:17 SAST 2000 Although the recently fixed panic on shutdown exists, I've noticed no other problems. I'm working my machine quite hard. 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 Aug 1 7:32:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id E21BB37BE45 for ; Tue, 1 Aug 2000 07:32:50 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA05507; Tue, 1 Aug 2000 10:32:51 -0400 (EDT) Received: from rac5.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id KAA24328; Tue, 1 Aug 2000 10:32:41 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA24324; Tue, 1 Aug 2000 10:32:40 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Tue, 1 Aug 2000 10:32:39 -0400 (EDT) From: Kenneth Wayne Culver To: Steve Hocking Cc: current@FreeBSD.ORG Subject: Re: VM flakiness since Thursday In-Reply-To: <200008011423.JAA21862@penguin.hstn.tensor.pgs.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 Just the lock stuff here, nothing else. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 1 Aug 2000, Steve Hocking wrote: > I've been noticing some crashes (the previously reported by others lock stuff) > and some random sig 11s - any one else seeing this? > > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true." Robert Wilensky, University of California > > > > > 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 Aug 1 7:33:52 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 8C97337BA81 for ; Tue, 1 Aug 2000 07:33:47 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (root@rac5.wam.umd.edu [128.8.10.145]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA22674; Tue, 1 Aug 2000 10:33:35 -0400 (EDT) Received: from rac5.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id KAA24366; Tue, 1 Aug 2000 10:33:43 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA24362; Tue, 1 Aug 2000 10:33:43 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Tue, 1 Aug 2000 10:33:43 -0400 (EDT) From: Kenneth Wayne Culver To: Steve Hocking Cc: current@FreeBSD.ORG Subject: Re: VM flakiness since Thursday In-Reply-To: <200008011423.JAA21862@penguin.hstn.tensor.pgs.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 I'm in the process of tracing it out (in my small amount of spare time) to see where the problem is, and seeing if I can fix it, although I think this is over my head :-) I just wanna see if I can do it. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 1 Aug 2000, Steve Hocking wrote: > I've been noticing some crashes (the previously reported by others lock stuff) > and some random sig 11s - any one else seeing this? > > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true." Robert Wilensky, University of California > > > > > 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 Aug 1 8: 7: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0304E37B856 for ; Tue, 1 Aug 2000 08:06:59 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA40087; Tue, 1 Aug 2000 17:06:44 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008011506.RAA40087@freebsd.dk> Subject: Re: VM flakiness since Thursday In-Reply-To: <200008011423.JAA21862@penguin.hstn.tensor.pgs.com> from Steve Hocking at "Aug 1, 2000 09:23:57 am" To: shocking@hstn.tensor.pgs.com (Steve Hocking) Date: Tue, 1 Aug 2000 17:06:43 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] 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 It seems Steve Hocking wrote: > I've been noticing some crashes (the previously reported by others lock stuff) > and some random sig 11s - any one else seeing this? Hmm, I've been having a hell of a time on one of my machines, but I had written it off to bad HW, but this might make me change my mind :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 8:17:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from outpost.hstn.tensor.pgs.com (outpost.hstn.tensor.pgs.com [157.147.25.67]) by hub.freebsd.org (Postfix) with ESMTP id 4ADB337B856 for ; Tue, 1 Aug 2000 08:17:42 -0700 (PDT) (envelope-from shocking@hstn.tensor.pgs.com) Received: from hap.hstn.tensor.pgs.com (hap.hstn.tensor.pgs.com [157.147.132.13]) by outpost.hstn.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id KAA02597; Tue, 1 Aug 2000 10:14:06 -0500 (CDT) Received: from penguin.hstn.tensor.pgs.com (penguin.hstn.tensor.pgs.com [157.147.132.155]) by hap.hstn.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id KAA00306; Tue, 1 Aug 2000 10:14:05 -0500 (CDT) Received: from hstn.tensor.pgs.com (localhost [127.0.0.1]) by penguin.hstn.tensor.pgs.com (8.8.8+Sun/8.8.8) with ESMTP id KAA22002; Tue, 1 Aug 2000 10:14:04 -0500 (CDT) Message-Id: <200008011514.KAA22002@penguin.hstn.tensor.pgs.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Soren Schmidt Cc: shocking@hstn.tensor.pgs.com, current@freebsd.org Subject: Re: VM flakiness since Thursday In-Reply-To: Message from Soren Schmidt of "Tue, 01 Aug 2000 17:06:43 +0200." <200008011506.RAA40087@freebsd.dk> Reply-To: shocking@prth.pgs.com Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 01 Aug 2000 10:14:04 -0500 From: Steve Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm, I've been having a hell of a time on one of my machines, but I had > written it off to bad HW, but this might make me change my mind :) > My machine's a K6-2 500 which up until that time had been fine - what's yours? The crashes (usually partway through a make world or on shutdown) were of the type other people had seen. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 8:30:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 735AC37B873 for ; Tue, 1 Aug 2000 08:30:13 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA45514; Tue, 1 Aug 2000 17:30:03 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008011530.RAA45514@freebsd.dk> Subject: Re: VM flakiness since Thursday In-Reply-To: <200008011514.KAA22002@penguin.hstn.tensor.pgs.com> from Steve Hocking at "Aug 1, 2000 10:14:04 am" To: shocking@prth.pgs.com Date: Tue, 1 Aug 2000 17:30:03 +0200 (CEST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] 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 It seems Steve Hocking wrote: > > Hmm, I've been having a hell of a time on one of my machines, but I had > > written it off to bad HW, but this might make me change my mind :) > > > > My machine's a K6-2 500 which up until that time had been fine - what's yours? Mine's a K7-750 > The crashes (usually partway through a make world or on shutdown) were of the > type other people had seen. Uhm, if its only the lockmgr thing, thats now solved, what I've been seeing is random sig11's etc etc... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 8:53:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id E726237BA6F; Tue, 1 Aug 2000 08:53:31 -0700 (PDT) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (203-165-77-17.sugnm1.kt.home.ne.jp [203.165.77.17]) by ms.tokyo.jcom.ne.jp (8.9.3/3.7W 04/27/00) with ESMTP id AAA25131; Wed, 2 Aug 2000 00:53:29 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id AAA57724; Wed, 2 Aug 2000 00:52:57 +0900 (JST) Date: Wed, 02 Aug 2000 00:52:56 +0900 Message-ID: <8666plkmg7.wl@localhost.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: freebsd-doc@FreeBSD.org, freebsd-current@FreeBSD.org, cvs-committers@FreeBSD.org Cc: root@FreeBSD.org Subject: HEADS UP: Updating our CVSweb User-Agent: Wanderlust/2.3.0 (Roam) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have been hacking on CVSweb for a while and now I think it is the time we update our CVSweb to the full-featured version, which is based on Henner Zeller and other people's work. The ready-to-commit demo is available at this page: http://people.FreeBSD.org/~knu/cgi-bin/cvsweb.cgi/ Now, to get the updating process right, I'd like the administrators of the WWW mirror sites (and freefall of course :) to do the following things on their Web servers: 1) Fetch the following tarball and install the CVSweb configuration files under /usr/local/etc. http://people.FreeBSD.org/~knu/misc/cvsweb_confs.tar.gz This will not overwrite the current configuration files of CVSweb. (cvsweb* vs. cvsweb.conf*) 2) For 2.2-STABLE machines, install Perl5 (from the port) and create a symlink to /usr/local/bin/perl5 in /usr/bin. ln -s /usr/local/bin/perl5 /usr/bin For 3-STABLE or upper machines, you don't need to do this because they already have /usr/bin/perl5 by nature. (That's the trick :) I will commit the update in a couple days or so, as soon as freefall is ready. So please do the above soon. Okay, that's all, and this is my attempt to shut up those impatient who always yell at me for not updating our CVSweb. :> -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 9: 5:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 0B88137B767; Tue, 1 Aug 2000 09:04:14 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id XAA78847; Tue, 1 Aug 2000 23:03:22 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 1 Aug 2000 23:03:21 +0700 (NSS) From: Max Khon To: Akinori -Aki- MUSHA Cc: freebsd-doc@FreeBSD.org, freebsd-current@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: HEADS UP: Updating our CVSweb In-Reply-To: <8666plkmg7.wl@localhost.local.idaemons.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 hi, there! On Wed, 2 Aug 2000, Akinori -Aki- MUSHA wrote: > I have been hacking on CVSweb for a while and now I think it is the > time we update our CVSweb to the full-featured version, which is based > on Henner Zeller and other people's work. The ready-to-commit demo is > available at this page: > > http://people.FreeBSD.org/~knu/cgi-bin/cvsweb.cgi/ maybe it is worth moving form that allows request diffs between any two revision to the top? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 9: 7:31 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 DAFBE37B947 for ; Tue, 1 Aug 2000 09:07:26 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 1 Aug 2000 17:07:24 +0100 (BST) Date: Tue, 1 Aug 2000 17:07:24 +0100 From: David Malone To: Soren Schmidt Cc: shocking@prth.pgs.com, current@freebsd.org Subject: Re: VM flakiness since Thursday Message-ID: <20000801170724.A32929@walton.maths.tcd.ie> References: <200008011514.KAA22002@penguin.hstn.tensor.pgs.com> <200008011530.RAA45514@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i In-Reply-To: <200008011530.RAA45514@freebsd.dk>; from sos@freebsd.dk on Tue, Aug 01, 2000 at 05:30:03PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 01, 2000 at 05:30:03PM +0200, Soren Schmidt wrote: > Uhm, if its only the lockmgr thing, thats now solved, what I've been seeing > is random sig11's etc etc... I've been seeing odd signal 11's duing make world too, but I'd put it down to unusually warm weather. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 9:13:40 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 28F3D37B767; Tue, 1 Aug 2000 09:13:34 -0700 (PDT) (envelope-from piotr.wozniak@cs.put.poznan.pl) 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 e71G7lZ09659; Tue, 1 Aug 2000 18:07:51 +0200 (CEST) Message-ID: <3986F72A.84D87E6@cs.put.poznan.pl> Date: Tue, 01 Aug 2000 18:13:30 +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-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: DOS emulation 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 have to run programs in Clipper/DOS under FreeBSD. Does exist a good DOS-emulator or other solving of this problem? (for example compiling source code in Clipper under FreeBSD..) Piotr Wozniak To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 9:19:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 1A9F837BA6F; Tue, 1 Aug 2000 09:19:47 -0700 (PDT) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (203-165-77-17.sugnm1.kt.home.ne.jp [203.165.77.17]) by ms.tokyo.jcom.ne.jp (8.9.3/3.7W 04/27/00) with ESMTP id BAA00549; Wed, 2 Aug 2000 01:19:45 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id BAA58033; Wed, 2 Aug 2000 01:19:14 +0900 (JST) Date: Wed, 02 Aug 2000 01:19:13 +0900 Message-ID: <864s55kl8e.wl@localhost.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: Max Khon Cc: freebsd-doc@FreeBSD.org, freebsd-current@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: HEADS UP: Updating our CVSweb In-Reply-To: In your message of "Tue, 1 Aug 2000 23:03:21 +0700 (NSS)" References: <8666plkmg7.wl@localhost.local.idaemons.org> User-Agent: Wanderlust/2.3.0 (Roam) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At Tue, 1 Aug 2000 23:03:21 +0700 (NSS), Max Khon wrote: > On Wed, 2 Aug 2000, Akinori -Aki- MUSHA wrote: > > > I have been hacking on CVSweb for a while and now I think it is the > > time we update our CVSweb to the full-featured version, which is based > > on Henner Zeller and other people's work. The ready-to-commit demo is > > available at this page: > > > > http://people.FreeBSD.org/~knu/cgi-bin/cvsweb.cgi/ > > maybe it is worth moving form that allows request diffs between any two > revision to the top? Well, following the hyperlink "Request diff between arbitrary revisions" will take you to the form. It's as easy as a single click. :) -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 9:22:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from bmz096.ust.hk (bmz096.ust.hk [143.89.59.176]) by hub.freebsd.org (Postfix) with ESMTP id 8875E37BB2A; Tue, 1 Aug 2000 09:21:34 -0700 (PDT) (envelope-from don@quotepool.com) Received: from host10.4ua.com by bmz096.ust.hk with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8) id PQ5HL8J7; Wed, 2 Aug 2000 00:37:08 +0800 From: don@quotepool.com Message-Id: <965146409.uevrgv@uevrgv.mail.dover.net> To: uevrgv@dover.net Reply-To: don@quotepool.com X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en Content-Type: text/html; Charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Serious people for a serious proposition about FREEDOM qtzgx Date: Tue, 1 Aug 2000 09:21:34 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG

93% WHO RESPOND TO MY AD DON'T MAKE THE CUT!
(Only highly motivated people should call)

I'm dead serious! Now let me tell you why...

Most people don't have drive! They sit around waiting for something to happen.
They see that other people have nice homes, new cars, and MONEY, but why can't they?
They basically feel sorry for themselves, and I can't help these people!

Another reason people are not qualified...

They are skeptical. BUT, the truth is, they are skeptical of themselves!
They don't have the courage to break their routine.
They are comfortable with their set hours, their set pay, and their set future.
I was not comfortable with someone controlling my future,
and I'm not comfortable working with people who are!

STOP
If you are anything like the above, we won't be able to work together!

WHAT DO THE 7% WHO DO MAKE THE CUT DISCOVER?!

People I select through an "interview like" process are forever changed!
They are opened to a world around them that they didn't know existed.
In fact, it's a world that has existed around them their whole lives,
but was purposely hidden from them!


How would you like to...

- Drastically reduce personal, business and capital gains taxes?
- Protect all assets from any form of seizure, liens, or judgments?
- Create a six figure income every 4 months?

How about...

Restoring and preserving complete personal and financial privacy?
Amassing personal wealth, multiplying it and protecting it?
Realizing a 3 to 6 times greater return on your money?
Legally making yourself and your assets completely judgment-proof,
lien-proof, divorce-proof, attorney-proof, IRS-proof?
I could go on...

TAKE A SERIOUS LOOK AT YOUR LIFE

Do you think you are paid what you are worth?
Will you be set to retire in the next few years?
Do you control the course of your day? ...your life?

The fact is we have many people in our enterprise that earn over 50K per month
from the privacy of their own homes, and are retiring in 2 to 3 years (wealthy)
and have total freedom - both personal and financial!

Many have been conditioned to believe it must be illegal, immoral or unethical
to ever earn any real profits from our efforts.

The sad truth is, it's been designed that way by the ultra-rich
and ultra-powerful since before any of us were born!

Who am I?

I'm a BIG thinker, a BIG dreamer, and I believe that I deserve the best that life has to offer.
I answered an ad much like the one you are reading now,
and was eager to hear what it was about.

I knew that I couldn't invest only a few bucks and spend an hour or two
per week to achieve the results I was looking for. I found the right information
and now I control my own destiny!

If you are interested in radically changing your thoughts and your financial future,
I invite you to call TOLL FREE:

1 800 707 4817

My name is Krystina, and I look forward to working with some of you!

* REMEMBER *

I can't do it for you, but I can show you exactly how I do it.
It's as simple as that!

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 9:22:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from bmz096.ust.hk (bmz096.ust.hk [143.89.59.176]) by hub.freebsd.org (Postfix) with ESMTP id B740537BCF4; Tue, 1 Aug 2000 09:22:26 -0700 (PDT) (envelope-from alpha@highnetspeed.com) Received: from host10.4ua.com by bmz096.ust.hk with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8) id PQ5HL8K1; Wed, 2 Aug 2000 00:37:57 +0800 From: alpha@highnetspeed.com Message-Id: <965146409.lwlhjl@lwlhjl.mail.dover.net> To: lwlhjl@dover.net Reply-To: alpha@highnetspeed.com X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en Content-Type: text/html; Charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Sometimes the truth hurts! inhgt Date: Tue, 1 Aug 2000 09:22:26 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG

93% WHO RESPOND TO MY AD DON'T MAKE THE CUT!
(Only highly motivated people should call)

I'm dead serious! Now let me tell you why...

Most people don't have drive! They sit around waiting for something to happen.
They see that other people have nice homes, new cars, and MONEY, but why can't they?
They basically feel sorry for themselves, and I can't help these people!

Another reason people are not qualified...

They are skeptical. BUT, the truth is, they are skeptical of themselves!
They don't have the courage to break their routine.
They are comfortable with their set hours, their set pay, and their set future.
I was not comfortable with someone controlling my future,
and I'm not comfortable working with people who are!

STOP
If you are anything like the above, we won't be able to work together!

WHAT DO THE 7% WHO DO MAKE THE CUT DISCOVER?!

People I select through an "interview like" process are forever changed!
They are opened to a world around them that they didn't know existed.
In fact, it's a world that has existed around them their whole lives,
but was purposely hidden from them!


How would you like to...

- Drastically reduce personal, business and capital gains taxes?
- Protect all assets from any form of seizure, liens, or judgments?
- Create a six figure income every 4 months?

How about...

Restoring and preserving complete personal and financial privacy?
Amassing personal wealth, multiplying it and protecting it?
Realizing a 3 to 6 times greater return on your money?
Legally making yourself and your assets completely judgment-proof,
lien-proof, divorce-proof, attorney-proof, IRS-proof?
I could go on...

TAKE A SERIOUS LOOK AT YOUR LIFE

Do you think you are paid what you are worth?
Will you be set to retire in the next few years?
Do you control the course of your day? ...your life?

The fact is we have many people in our enterprise that earn over 50K per month
from the privacy of their own homes, and are retiring in 2 to 3 years (wealthy)
and have total freedom - both personal and financial!

Many have been conditioned to believe it must be illegal, immoral or unethical
to ever earn any real profits from our efforts.

The sad truth is, it's been designed that way by the ultra-rich
and ultra-powerful since before any of us were born!

Who am I?

I'm a BIG thinker, a BIG dreamer, and I believe that I deserve the best that life has to offer.
I answered an ad much like the one you are reading now,
and was eager to hear what it was about.

I knew that I couldn't invest only a few bucks and spend an hour or two
per week to achieve the results I was looking for. I found the right information
and now I control my own destiny!

If you are interested in radically changing your thoughts and your financial future,
I invite you to call TOLL FREE:

1 800 707 4817

My name is Krystina, and I look forward to working with some of you!

* REMEMBER *

I can't do it for you, but I can show you exactly how I do it.
It's as simple as that!

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 9:36:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-in-01.piro.net (mail-out-02.piro.net [194.64.31.10]) by hub.freebsd.org (Postfix) with ESMTP id 5E65E37BD38; Tue, 1 Aug 2000 09:36:20 -0700 (PDT) (envelope-from marc.vanwoerkom@science-factory.com) Received: from nil.science-factory.com (ScienceFactory-atm1-153.piro.net [195.135.137.205]) by mail-in-01.piro.net (8.9.3/8.9.3/PN-991208) with ESMTP id SAA25951; Tue, 1 Aug 2000 18:33:47 +0200 Received: by nil.science-factory.com (Postfix, from userid 501) id 2417F1F63; Tue, 1 Aug 2000 18:28:32 +0200 (CEST) From: Marc van Woerkom To: knu@idaemons.org Cc: freebsd-doc@FreeBSD.org, freebsd-current@FreeBSD.org, cvs-committers@FreeBSD.org, root@FreeBSD.org In-reply-to: <8666plkmg7.wl@localhost.local.idaemons.org> (knu@idaemons.org) Subject: Re: HEADS UP: Updating our CVSweb References: <8666plkmg7.wl@localhost.local.idaemons.org> Message-Id: <20000801162832.2417F1F63@nil.science-factory.com> Date: Tue, 1 Aug 2000 18:28:32 +0200 (CEST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! > http://people.FreeBSD.org/~knu/cgi-bin/cvsweb.cgi/ Looks nice. I like the comments displayed. Just a question - we obviously have a huge number of cvs tags - is their rationale documented in any place? > 1) Fetch the following tarball and install the CVSweb > configuration files under /usr/local/etc. > > http://people.FreeBSD.org/~knu/misc/cvsweb_confs.tar.gz > > This will not overwrite the current configuration files of > CVSweb. (cvsweb* vs. cvsweb.conf*) Another stupid question. Is cvsweb and its configuration files something that will be put too in our cvs tree (collection www)? Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 9:40:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C49FB37BE66; Tue, 1 Aug 2000 09:40:07 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e71FksP14872; Tue, 1 Aug 2000 08:46:54 -0700 (PDT) Date: Tue, 1 Aug 2000 08:46:53 -0700 From: Alfred Perlstein To: Piotr Wo?niak Cc: freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: DOS emulation Message-ID: <20000801084653.O4854@fw.wintelcom.net> References: <3986F72A.84D87E6@cs.put.poznan.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <3986F72A.84D87E6@cs.put.poznan.pl>; from piotr.wozniak@cs.put.poznan.pl on Tue, Aug 01, 2000 at 06:13:30PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Piotr Wo?niak [000801 08:21] wrote: > Hi, > I have to run programs in Clipper/DOS under FreeBSD. > Does exist a good DOS-emulator or other solving of this problem? > (for example compiling source code in Clipper under FreeBSD..) Maybe 'doscmd'? Let us know. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 9:52:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-in-02.piro.net (mail-out-01.piro.net [194.64.31.11]) by hub.freebsd.org (Postfix) with ESMTP id 99B6E37BE12; Tue, 1 Aug 2000 09:52:35 -0700 (PDT) (envelope-from marc.vanwoerkom@science-factory.com) Received: from nil.science-factory.com (ScienceFactory-atm1-153.piro.net [195.135.137.205]) by mail-in-02.piro.net (8.9.3/8.9.3/PN-991208) with ESMTP id SAA25907; Tue, 1 Aug 2000 18:52:21 +0200 Received: by nil.science-factory.com (Postfix, from userid 501) id 92FCF200C; Tue, 1 Aug 2000 18:45:46 +0200 (CEST) From: Marc van Woerkom To: piotr.wozniak@cs.put.poznan.pl Cc: freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: <3986F72A.84D87E6@cs.put.poznan.pl> (message from Piotr =?iso-8859-1?Q?Wo=9Fniak?= on Tue, 01 Aug 2000 18:13:30 +0200) Subject: Re: DOS emulation References: <3986F72A.84D87E6@cs.put.poznan.pl> Message-Id: <20000801164546.92FCF200C@nil.science-factory.com> Date: Tue, 1 Aug 2000 18:45:46 +0200 (CEST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have to run programs in Clipper/DOS under FreeBSD. > Does exist a good DOS-emulator or other solving of this problem? Bochs and Wine both do a good job. Check your /usr/ports/emulators or the FreeBSD web site. There are a couple of strange uses for both programs. Today we needed a DOS boot disk for some BIOS update in our shop which couldn't be created under Windows 2000. My colleague did it with Bochs. :) A bizarre use for Wine is this http://people.freebsd.org/~3d/wine Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 9:57:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 075F737BF34; Tue, 1 Aug 2000 09:57:00 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id XAA80490; Tue, 1 Aug 2000 23:55:58 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 1 Aug 2000 23:55:58 +0700 (NSS) From: Max Khon To: Akinori -Aki- MUSHA Cc: freebsd-doc@FreeBSD.org, freebsd-current@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: HEADS UP: Updating our CVSweb In-Reply-To: <864s55kl8e.wl@localhost.local.idaemons.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 hi, there! On Wed, 2 Aug 2000, Akinori -Aki- MUSHA wrote: > > maybe it is worth moving form that allows request diffs between any two > > revision to the top? > > Well, following the hyperlink "Request diff between arbitrary > revisions" will take you to the form. > > It's as easy as a single click. :) when you are loading file with a lot of revisions over slow link you can always stop transfer and use the form. that's the point. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 10: 6: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id F1B3F37B97B for ; Tue, 1 Aug 2000 10:05:52 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id TAA12616 for freebsd-current@FreeBSD.ORG; Tue, 1 Aug 2000 19:05:48 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id BB70E889E; Tue, 1 Aug 2000 07:54:34 +0200 (CEST) Date: Tue, 1 Aug 2000 07:54:34 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: sendmail 8.11.0 trouble Message-ID: <20000801075434.A86503@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <200007301840.OAA03021@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: ; from leifn@neland.dk on Tue, Aug 01, 2000 at 02:51:45AM +0200 X-Operating-System: FreeBSD 5.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Leif Neland: > /etc/pwd.db: Berkeley DB Hash file (Version 2, Little Endian, Bucket Size > I had db 2.something installed from the ports. I uninstalled it, it made > no difference. /etc/pwd.db should NOT be in DB 2.x format. Recompile pwd_mkdb to be sure to use DB 1.85 and use it to regenerate /etc/*pwd.db. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 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 Aug 1 10:38:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 3767737BEEA; Tue, 1 Aug 2000 10:38:35 -0700 (PDT) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (203-165-77-17.sugnm1.kt.home.ne.jp [203.165.77.17]) by ms.tokyo.jcom.ne.jp (8.9.3/3.7W 04/27/00) with ESMTP id CAA12605; Wed, 2 Aug 2000 02:38:24 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id CAA59122; Wed, 2 Aug 2000 02:37:52 +0900 (JST) Date: Wed, 02 Aug 2000 02:37:51 +0900 Message-ID: <861z08lw5s.wl@localhost.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: Marc van Woerkom Cc: freebsd-doc@FreeBSD.org, freebsd-current@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: HEADS UP: Updating our CVSweb In-Reply-To: In your message of "Tue, 1 Aug 2000 18:28:32 +0200 (CEST)" <20000801162832.2417F1F63@nil.science-factory.com> References: <8666plkmg7.wl@localhost.local.idaemons.org> <20000801162832.2417F1F63@nil.science-factory.com> User-Agent: Wanderlust/2.3.0 (Roam) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Woot, sorry for including root@FreeBSD.org in Cc. I should have specified it in Bcc. People, please remove it from the recipients list on reply. Thank you. ] At Tue, 1 Aug 2000 18:28:32 +0200 (CEST), Marc van Woerkom wrote: > Another stupid question. > Is cvsweb and its configuration files something that will be put too > in our cvs tree (collection www)? Yes, I was thinking of that too. I suppose putting the configuration files in our www tree and letting /usr/local/etc/cvsweb.conf* override them would work, as each site could have its own configuration: mainly for its local repositories. -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 10:52: 7 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 7B29D37BFC3 for ; Tue, 1 Aug 2000 10:52:05 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA12534; Tue, 1 Aug 2000 13:50:56 -0400 (EDT) (envelope-from wollman) Date: Tue, 1 Aug 2000 13:50:56 -0400 (EDT) From: Garrett Wollman Message-Id: <200008011750.NAA12534@khavrinen.lcs.mit.edu> To: Ollivier Robert Cc: freebsd-current@FreeBSD.ORG Subject: Re: sendmail 8.11.0 trouble In-Reply-To: <20000801075434.A86503@keltia.freenix.fr> References: <200007301840.OAA03021@khavrinen.lcs.mit.edu> <20000801075434.A86503@keltia.freenix.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > According to Leif Neland: >> /etc/pwd.db: Berkeley DB Hash file (Version 2, Little Endian, Bucket Size > /etc/pwd.db should NOT be in DB 2.x format. Recompile pwd_mkdb to be sure to > use DB 1.85 and use it to regenerate /etc/*pwd.db. DB 1.85's file format *is* ``Version 2''. -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 Tue Aug 1 11: 3:36 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 E18DB37C1BD; Tue, 1 Aug 2000 11:03:30 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA03713; Tue, 1 Aug 2000 11:03:17 -0700 (PDT) (envelope-from obrien) Date: Tue, 1 Aug 2000 11:03:17 -0700 From: "David O'Brien" To: Piotr Wo?niak Cc: freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: DOS emulation Message-ID: <20000801110317.A3666@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <3986F72A.84D87E6@cs.put.poznan.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3986F72A.84D87E6@cs.put.poznan.pl>; from piotr.wozniak@cs.put.poznan.pl on Tue, Aug 01, 2000 at 06:13:30PM +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, Aug 01, 2000 at 06:13:30PM +0200, Piotr Wo?niak wrote: > I have to run programs in Clipper/DOS under FreeBSD. If this is character based, I have the best luck running Quicken for MS-DOS using the ``pcemu'' port. Bochs is way much slower, and doscmd also would work for me with this application. -- -- 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 Tue Aug 1 11:28:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from pf39.warszawa.sdi.tpnet.pl (pf39.warszawa.sdi.tpnet.pl [213.25.209.39]) by hub.freebsd.org (Postfix) with ESMTP id C119137BA9D for ; Tue, 1 Aug 2000 11:28:48 -0700 (PDT) (envelope-from zaks@pf39.warszawa.sdi.tpnet.pl) Received: (from zaks@localhost) by pf39.warszawa.sdi.tpnet.pl (8.9.3/8.9.3) id UAA00368; Tue, 1 Aug 2000 20:28:44 +0200 (CEST) (envelope-from zaks) Content-MD5: c5ef05f01139a98da9a805d2f3f21262 From: Slawek Zak To: freebsd-current@freebsd.org Subject: SCSI breakage Date: 01 Aug 2000 20:28:44 +0200 Message-ID: <87vgxk3kf7.fsf@pf39.warszawa.sdi.tpnet.pl> Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having SCSI parity errors on Tekram 390F controller (CURRENT for Aug 1, the sym driver). During some heavier disk activity the kernel reports "Weird command received" and resets the controller after short period of time. Now I'm running CURRENT for Jul 31 without any problems... -- hundred-and-one symptoms of being an internet addict: 144. You eagerly await the update of the "Cool Site of the Day." * Suavek Zak / PGP: finger://zaks@prioris.mini.pw.edu.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 11:38:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 002D937BD82 for ; Tue, 1 Aug 2000 11:38:33 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA27291; Tue, 1 Aug 2000 12:36:02 -0600 (MDT) (envelope-from ken) Date: Tue, 1 Aug 2000 12:36:02 -0600 From: "Kenneth D. Merry" To: Slawek Zak Cc: freebsd-current@FreeBSD.ORG Subject: Re: SCSI breakage Message-ID: <20000801123601.A27223@panzer.kdm.org> References: <87vgxk3kf7.fsf@pf39.warszawa.sdi.tpnet.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <87vgxk3kf7.fsf@pf39.warszawa.sdi.tpnet.pl>; from zaks@prioris.mini.pw.edu.pl on Tue, Aug 01, 2000 at 08:28:44PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 01, 2000 at 20:28:44 +0200, Slawek Zak wrote: > I'm having SCSI parity errors on Tekram 390F controller (CURRENT for > Aug 1, the sym driver). During some heavier disk activity the kernel > reports "Weird command received" and resets the controller after short > period of time. Now I'm running CURRENT for Jul 31 without any > problems... You should send this report to the -scsi list, and include a copy of the error messages. (From dmesg.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 12:26:17 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 C0A8F37BA8D; Tue, 1 Aug 2000 12:26:12 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id PAA79293; Tue, 1 Aug 2000 15:25:50 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 1 Aug 2000 15:25:48 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Piotr =?iso-8859-1?Q?Wo=9Fniak?= Cc: freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: DOS emulation In-Reply-To: <3986F72A.84D87E6@cs.put.poznan.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been using vmware with great success under -STABLE. Take a look at /usr/ports/emulators/vmware2. It's commercial, but works a lot better than all the alternatives. I've had decent success with pcemu for DOS-based programs, although there are a few quirks. I found bochs also worked pretty well (fewer quirks, more features) but much slower. On Tue, 1 Aug 2000, Piotr Wo=9Fniak wrote: > Hi, > I have to run programs in Clipper/DOS under FreeBSD. > Does exist a good DOS-emulator or other solving of this problem? > (for example compiling source code in Clipper under FreeBSD..) > Piotr Wozniak >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 Robert N M Watson=20 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 Tue Aug 1 13:46: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 2D9FB37BAAD; Tue, 1 Aug 2000 13:46:01 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 2A60E2E8195; Tue, 1 Aug 2000 13:46:01 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Tue, 1 Aug 2000 13:46:01 -0700 (PDT) From: Kris Kennaway To: Jun Kuriyama Cc: Current Subject: Re: ssh -2 -v displays debug messages when typed In-Reply-To: <7mn1ix2ppp.wl@waterblue.imgsrc.co.jp> 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, 1 Aug 2000, Jun Kuriyama wrote: > On my -current environment, ssh -2 -v (Version 2 protocol with DSA, > verbose mode) displays debug message to tty whenever I typed. > > If I use version 1 protocol, debug messages are not displayed after > logged in to another system. Is this expected behaviour? Yes, this is just how OpenSSH is in debug mode for SSH2. It might be fixed in the newer version, which I'll probably get around to importing soon. 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 Aug 1 14: 5:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from markl.com (markl.com [209.69.36.90]) by hub.freebsd.org (Postfix) with ESMTP id 9A70837BE00; Tue, 1 Aug 2000 14:05:37 -0700 (PDT) (envelope-from squirrel@hammis.com) Received: from localhost (squirrel@localhost) by markl.com (8.9.3/8.9.3) with ESMTP id RAA93582; Tue, 1 Aug 2000 17:05:15 -0400 (EDT) (envelope-from squirrel@hammis.com) Date: Tue, 1 Aug 2000 17:05:15 -0400 (EDT) From: Damon Hammis X-Sender: squirrel@markl.com To: freebsd-questions@freebsd.org Cc: freebsd-current@freebsd.org Subject: Possible bug in current? 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 Has anyone else stumbled across this bug in 5.0-CURRENT? Whenever I try to do a tail -f on a text file the system locks up and requires a hard reboot. Anyone else see anything similar? --Damon _ _ |__/| .~ ~. /o=o'`./ .' {o__, \ { / . . ) \ `-` '-' \ } .( _( )_.' '---.~_ _ _| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 14: 9:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from chiba.3jane.net (chiba.3jane.net [207.170.70.27]) by hub.freebsd.org (Postfix) with ESMTP id 71F1137B71C; Tue, 1 Aug 2000 14:09:11 -0700 (PDT) (envelope-from damon@chiba.3jane.net) Received: from chiba.3jane.net (localhost [127.0.0.1]) by chiba.3jane.net (8.9.3/8.9.3) with ESMTP id QAA05263; Tue, 1 Aug 2000 16:08:37 -0500 (CDT) Message-Id: <200008012108.QAA05263@chiba.3jane.net> To: Damon Hammis Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Possible bug in current? In-reply-to: References: Comments: In-reply-to Damon Hammis message dated "Tue, 01 Aug 2000 17:05:15 -0400." Date: Tue, 01 Aug 2000 16:08:37 -0500 From: "Damon M. Conway" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Damon Hammis wrote: >Has anyone else stumbled across this bug in 5.0-CURRENT? Whenever I try >to do a tail -f on a text file the system locks up and requires a hard >reboot. > >Anyone else see anything similar? yes, there is a long discussion on -current about it right now. damon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 14:36:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id 4C12037BE43 for ; Tue, 1 Aug 2000 14:36:10 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 13Jjhi-000L9p-0Y; Tue, 1 Aug 2000 22:36:03 +0100 Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id WAA13060; Tue, 1 Aug 2000 22:36:00 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id WAA46668; Tue, 1 Aug 2000 22:11:57 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Tue, 1 Aug 2000 22:11:57 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Stephan van Beerschoten Cc: "FreeBSD Current Users' list" Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-Reply-To: <20000725172329.A94003@enigma.whacky.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 The word is that there is a problem but it is a software problem. For some reason the virtual hub gives an IOERROR, but I haven't had the time or seen the need to figure that one out. It seems to be harmless though. nick > And what is the word on thise IOERROR's given by my kernel when its init'ing > its usb stack. > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhub0: port 1 power on failed, IOERROR > uhub0: port 2 power on failed, IOERROR > > ? > > -Steve > > -- > Stephan van Beerschoten stephanb@whacky.net > PGP fingerprint: 4557 9761 B212 FB4C 778D 3529 C42A 2D27 > "This email was brought to you by your local pop server" > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 14:37:33 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 0A0BF37BE25 for ; Tue, 1 Aug 2000 14:37:28 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 13Jjhl-000Jpg-0C; Tue, 1 Aug 2000 21:36:05 +0000 Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id WAA13064; Tue, 1 Aug 2000 22:36:04 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id WAA46679; Tue, 1 Aug 2000 22:27:45 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Tue, 1 Aug 2000 22:27:45 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Alexander Leidinger Cc: current@FreeBSD.org Subject: Re: Panic in xpt_setup_ccb (cam_xpt.c) In-Reply-To: <200007290830.KAA00512@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 Hm, I had a look at the source code, and to be honest I can't find a single reason why the path would be unset. Did the CD reader detached itself from the bus in the meantime, or did something like a bus error occur? Check your messages log around the time the panic occurred to see if something like that happened. At that point in the code it was using the path variable stored in the periph and that one is available from when the peripheral was allocated up to the point where the refcount for the peripheral reaches zero (that could be wrong) or the device is invalidated. Nick On Sat, 29 Jul 2000, Alexander Leidinger wrote: > Hi, > > while trying to read (dd if=/dev/cd0c) from a damaged cd (the surface is > a little bit damaged), I've got a panic: > ---snip--- > #0 boot (howto=260) at ../../kern/kern_shutdown.c:303 > #1 0xc01a0f19 in panic (fmt=0xc029aa60 "lockmgr: pid %d, not %s %d unlocking") > at ../../kern/kern_shutdown.c:553 > #2 0xc019b194 in lockmgr (lkp=0xc14f4a00, flags=65542, interlkp=0xd0e2e22c, > p=0xd0313ba0) at ../../kern/kern_lock.c:382 > #3 0xc01cf2af in vop_stdunlock (ap=0xd0d2ecc8) at ../../kern/vfs_default.c:255 > #4 0xc022b641 in ufs_vnoperate (ap=0xd0d2ecc8) > at ../../ufs/ufs/ufs_vnops.c:2301 > #5 0xc01d22aa in vput (vp=0xd0e2e1c0) at vnode_if.h:794 > #6 0xc0222ea7 in ffs_sync (mp=0xc1046a00, waitfor=2, cred=0xc0b3f980, > p=0xc037f0a0) at ../../ufs/ffs/ffs_vfsops.c:955 > #7 0xc01d4295 in sync (p=0xc037f0a0, uap=0x0) at ../../kern/vfs_syscalls.c:551 > #8 0xc01a094f in boot (howto=256) at ../../kern/kern_shutdown.c:225 > #9 0xc01a0f19 in panic (fmt=0xc02babef "page fault") > at ../../kern/kern_shutdown.c:553 > #10 0xc0265846 in trap_fatal (frame=0xd0d2ee10, eva=68) > at ../../i386/i386/trap.c:929 > #11 0xc02654f9 in trap_pfault (frame=0xd0d2ee10, usermode=0, eva=68) > at ../../i386/i386/trap.c:822 > #12 0xc02650bf in trap (frame={tf_fs = 16, tf_es = -791543792, > tf_ds = -1072562160, tf_edi = 1, tf_esi = -1056803840, > tf_ebp = -791482800, tf_isp = -791482820, tf_ebx = 0, tf_edx = 64, > tf_ecx = -791482776, tf_eax = 1, tf_trapno = 12, tf_err = 0, > tf_eip = -1072541595, tf_cs = 8, tf_eflags = 2163330, > tf_esp = -791482664, tf_ss = -1072555584}) at ../../i386/i386/trap.c:427 > #13 0xc0125065 in xpt_setup_ccb (ccb_h=0xd0d2ee68, path=0x40, priority=1) > at ../../cam/cam_xpt.c:3734 > #14 0xc01219c0 in cam_release_devq (path=0x40, relsim_flags=0, openings=0, > timeout=0, getcount_only=0) at ../../cam/cam_periph.c:855 > ---Type to continue, or q to quit--- > #15 0xc0121b37 in camperiphdone (periph=0xc1021480, done_ccb=0xc1027400) > at ../../cam/cam_periph.c:1021 > #16 0xc0127997 in camisr (queue=0xc03189b0) at ../../cam/cam_xpt.c:6328 > #17 0xc01277a9 in swi_cambio () at ../../cam/cam_xpt.c:6231 > #18 0xc025b900 in splz_swi () > #19 0xc01a7451 in softclock () at ../../kern/kern_timeout.c:131 > #20 0xc025b85f in doreti_swi () > Cannot access memory at address 0x91992874. > (kgdb) up 13 > #13 0xc0125065 in xpt_setup_ccb (ccb_h=0xd0d2ee68, path=0x40, priority=1) > at ../../cam/cam_xpt.c:3734 > 3734 ccb_h->path = path; > (kgdb) > (kgdb) print path > $1 = (struct cam_path *) 0x0 > (kgdb) print ccb_h > $2 = (struct ccb_hdr *) 0x0 > (kgdb) up > #14 0xc01219c0 in cam_release_devq (path=0x40, relsim_flags=0, openings=0, > timeout=0, getcount_only=0) at ../../cam/cam_periph.c:855 > 855 xpt_setup_ccb(&crs.ccb_h, path, > (kgdb) print path > $5 = (struct cam_path *) 0x40 > (kgdb) print *path > Cannot access memory at address 0x40. > ---snip--- > > It's a kernel from yesterday. > > Bye, > Alexander. > > -- > If Bill Gates had a dime for every time a Windows box crashed... > ...Oh, wait a minute, he already does. > > 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 > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 16:17:49 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 1725437B678; Tue, 1 Aug 2000 16:17:42 -0700 (PDT) (envelope-from imp@harmony.village.org) 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 RAA61281; Tue, 1 Aug 2000 17:17:39 -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 RAA87007; Tue, 1 Aug 2000 17:17:22 -0600 (MDT) Message-Id: <200008012317.RAA87007@harmony.village.org> To: Piotr =?iso-8859-1?Q?Wo=9Fniak?= Subject: Re: DOS emulation Cc: freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 01 Aug 2000 18:13:30 +0200." <3986F72A.84D87E6@cs.put.poznan.pl> References: <3986F72A.84D87E6@cs.put.poznan.pl> Date: Tue, 01 Aug 2000 17:17:22 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3986F72A.84D87E6@cs.put.poznan.pl> Piotr =?iso-8859-1?Q?Wo=9Fniak?= writes: : I have to run programs in Clipper/DOS under FreeBSD. : Does exist a good DOS-emulator or other solving of this problem? : (for example compiling source code in Clipper under FreeBSD..) dosemu works OK. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 16:24: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.147.1.144]) by hub.freebsd.org (Postfix) with ESMTP id F1EB737BF0A; Tue, 1 Aug 2000 16:24:03 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.251.241]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id TAA26307; Tue, 1 Aug 2000 19:23:57 -0400 (EDT) Message-ID: <39875C0D.7EF63A2C@acm.org> Date: Tue, 01 Aug 2000 19:23:57 -0400 From: Jim Bloom X-Mailer: Mozilla 4.73 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Damon M. Conway" Cc: Damon Hammis , freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Possible bug in current? References: <200008012108.QAA05263@chiba.3jane.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fixed with revision 1.14 sys/kern/kern_event.c. Update your kernel sources and the problem should go away. Jim Bloom bloom@acm.org "Damon M. Conway" wrote: > > Damon Hammis wrote: > >Has anyone else stumbled across this bug in 5.0-CURRENT? Whenever I try > >to do a tail -f on a text file the system locks up and requires a hard > >reboot. > > > >Anyone else see anything similar? > > yes, there is a long discussion on -current about it right now. > > damon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 17:57:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 8E13937B5D1; Tue, 1 Aug 2000 17:57:51 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac6.wam.umd.edu (root@rac6.wam.umd.edu [128.8.10.146]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id UAA25165; Tue, 1 Aug 2000 20:57:36 -0400 (EDT) Received: from rac6.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac6.wam.umd.edu (8.9.3/8.9.3) with SMTP id UAA12375; Tue, 1 Aug 2000 20:57:48 -0400 (EDT) Received: from localhost (culverk@localhost) by rac6.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA12368; Tue, 1 Aug 2000 20:57:48 -0400 (EDT) X-Authentication-Warning: rac6.wam.umd.edu: culverk owned process doing -bs Date: Tue, 1 Aug 2000 20:57:48 -0400 (EDT) From: Kenneth Wayne Culver To: Damon Hammis Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Possible bug in current? 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 Yeah, it's supposedly fixed now. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 1 Aug 2000, Damon Hammis wrote: > Has anyone else stumbled across this bug in 5.0-CURRENT? Whenever I try > to do a tail -f on a text file the system locks up and requires a hard > reboot. > > Anyone else see anything similar? > > --Damon > > _ _ > |__/| .~ ~. > /o=o'`./ .' > {o__, \ { > / . . ) \ > `-` '-' \ } > .( _( )_.' > '---.~_ _ _| > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" 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 Aug 1 20: 6:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 1591B37B5C9 for ; Tue, 1 Aug 2000 20:06:46 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id FAA09191 for freebsd-current@FreeBSD.ORG; Wed, 2 Aug 2000 05:06:44 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 3B919889E; Wed, 2 Aug 2000 00:16:03 +0200 (CEST) Date: Wed, 2 Aug 2000 00:16:03 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: sendmail 8.11.0 trouble Message-ID: <20000802001603.A91500@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <200007301840.OAA03021@khavrinen.lcs.mit.edu> <20000801075434.A86503@keltia.freenix.fr> <200008011750.NAA12534@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: <200008011750.NAA12534@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Tue, Aug 01, 2000 at 01:50:56PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Garrett Wollman: > DB 1.85's file format *is* ``Version 2''. Oh? Forget my message then :) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 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 Aug 1 22:29:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id AB15D37BFFC; Tue, 1 Aug 2000 22:29:42 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id MAA83737; Wed, 2 Aug 2000 12:29:40 +0700 (NOVST) (envelope-from nnd) Date: Wed, 2 Aug 2000 12:29:40 +0700 (NOVST) Message-Id: <200008020529.MAA83737@wint.itfs.nsk.su> From: Nickolay Dudorov To: current@FreeBSD.ORG Cc: ru@FreeBSD.ORG Subject: Re: cvs commit: src/usr.bin/kdump mkioctls In-Reply-To: <200008010815.BAA73139@freefall.freebsd.org> X-Newsgroups: itfs.freebsd.cvs.all User-Agent: tin/1.5.6-20000726 ("Lucretia") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200008010815.BAA73139@freefall.freebsd.org> you wrote: > > ru 2000/08/01 01:15:06 PDT > > Modified files: > usr.bin/kdump mkioctls > Log: > Fix an off-by-nine error when building a list of includes. > > Revision Changes Path > 1.17 +2 -2 src/usr.bin/kdump/mkioctls After this commit newly generated 'ioctl.c' includes which used 'ETHER_ADDR_LEN' defined in which is not included in 'ioctl.c'. With the next patch I can make "usr.bin/kdump" and "usr.bin/truss". Index: src/usr.bin/kdump/mkioctls =================================================================== RCS file: /store/CVS/src/usr.bin/kdump/mkioctls,v retrieving revision 1.17 diff -b -u -r1.17 mkioctls --- src/usr.bin/kdump/mkioctls 2000/08/01 08:15:06 1.17 +++ src/usr.bin/kdump/mkioctls 2000/08/02 05:28:33 @@ -41,6 +41,7 @@ print "#include " print "#include " print "#include " + print "#include " print "#include " print "#include " print "#include " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 22:38:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id C54ED37B509 for ; Tue, 1 Aug 2000 22:38:35 -0700 (PDT) (envelope-from hdiwan@hdroam.ssd.loral.com) Received: from hdroam.ssd.loral.com ([64.6.200.67]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 1 Aug 2000 22:37:35 -0700 Received: by hdroam.ssd.loral.com (Postfix, from userid 1001) id 79A28124AD5; Tue, 1 Aug 2000 22:38:36 -0700 (PDT) Date: Tue, 1 Aug 2000 22:38:36 -0700 From: Hasan Diwan To: current@freebsd.org Subject: Re: ssh -2 -v displays debug messages when typed Message-ID: <20000801223836.A2731@hdroam.ssd.loral.com> Reply-To: hdiwan@pobox.com References: <7mn1ix2ppp.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: ; from kris@hub.freebsd.org on Tue, Aug 01, 2000 at 01:46:01PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is not fixed in the newer version. Personally, I think the SSH1 way is optimal, and we should remove the every-character output in ssh2 debug mode. * Kris Kennaway [000801 13:49]: > Yes, this is just how OpenSSH is in debug mode for SSH2. It might be fixed > in the newer version, which I'll probably get around to importing soon. -- Take care, Hasan Diwan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 1 23:49:11 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 ACB6E37C00E for ; Tue, 1 Aug 2000 23:49:06 -0700 (PDT) (envelope-from piotr.wozniak@cs.put.poznan.pl) 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 e726hJZ10605 for ; Wed, 2 Aug 2000 08:43:20 +0200 (CEST) Message-ID: <3987C462.1E0D9E5A@cs.put.poznan.pl> Date: Wed, 02 Aug 2000 08:49:06 +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: Sharity Light Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, What way can I mount directory from NT server in boot process? (shlight //Sever/dir /mnt_point ....). This instruction placed in /usr/local/etc/rc.d has no result. 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 Aug 2 0:39:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 15E5737C02D for ; Wed, 2 Aug 2000 00:39:47 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.9.3/1.13) id KAA39292; Wed, 2 Aug 2000 10:39:29 +0300 (EEST) Date: Wed, 2 Aug 2000 10:39:29 +0300 From: Ruslan Ermilov To: Nickolay Dudorov Cc: current@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/kdump mkioctls Message-ID: <20000802103929.A38876@sunbay.com> Mail-Followup-To: Nickolay Dudorov , current@FreeBSD.org References: <200008010815.BAA73139@freefall.freebsd.org> <200008020529.MAA83737@wint.itfs.nsk.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200008020529.MAA83737@wint.itfs.nsk.su>; from nnd@wint.itfs.nsk.su on Wed, Aug 02, 2000 at 12:29:40PM +0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 02, 2000 at 12:29:40PM +0700, Nickolay Dudorov wrote: > In article <200008010815.BAA73139@freefall.freebsd.org> you wrote: > > > > ru 2000/08/01 01:15:06 PDT > > > > Modified files: > > usr.bin/kdump mkioctls > > Log: > > Fix an off-by-nine error when building a list of includes. > > > > Revision Changes Path > > 1.17 +2 -2 src/usr.bin/kdump/mkioctls > > After this commit newly generated 'ioctl.c' > includes which used 'ETHER_ADDR_LEN' > defined in which is not included in 'ioctl.c'. > > With the next patch I can make "usr.bin/kdump" and > "usr.bin/truss". > Fixed as of src/usr.bin/kdump/mkioctls,v 1.18, thanks! -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 2: 2:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.versatel.net (ns1.versatel.net [62.58.63.2]) by hub.freebsd.org (Postfix) with ESMTP id EF2F637C075 for ; Wed, 2 Aug 2000 02:02:41 -0700 (PDT) (envelope-from marct@versatel.net) Received: from localhost (marct@localhost) by ns1.versatel.net (8.9.3/8.9.3) with ESMTP id LAA64236 for ; Wed, 2 Aug 2000 11:05:54 GMT (envelope-from marct@versatel.net) Date: Wed, 2 Aug 2000 11:05:54 +0000 (GMT) From: Marc Teichtahl To: current@freebsd.org Subject: Custom ISO Images In-Reply-To: <20000801223836.A2731@hdroam.ssd.loral.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 dear All, i need to build a large number of machine with a customer distribution based on 4.1-RELEASE are there any pointers or help you can give me on how to create an ISO image of my distribution ? -- Marc Teichtahl Manager, Data Network Design Versatel Telecom "We *WILL* Deliver !" NASDAQ: VRSA AEX:VRSA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 2: 6: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 77F5937C099 for ; Wed, 2 Aug 2000 02:05:58 -0700 (PDT) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13JuT7-0007As-00; Wed, 02 Aug 2000 11:05:41 +0200 Date: Wed, 2 Aug 2000 11:05:40 +0200 From: Neil Blakey-Milner To: Marc Teichtahl Cc: current@freebsd.org Subject: Re: Custom ISO Images Message-ID: <20000802110540.A27553@mithrandr.moria.org> References: <20000801223836.A2731@hdroam.ssd.loral.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from marct@versatel.net on Wed, Aug 02, 2000 at 11:05:54AM +0000 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed 2000-08-02 (11:05), Marc Teichtahl wrote: > i need to build a large number of machine with a customer distribution > based on 4.1-RELEASE > > are there any pointers or help you can give me on how to create an ISO > image of my distribution ? cd /usr/src/release && make release You might need to adjust a few things, though ;) Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 3: 2: 8 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 0603F37B683 for ; Wed, 2 Aug 2000 03:02:01 -0700 (PDT) (envelope-from piotr.wozniak@cs.put.poznan.pl) 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 e729uCZ11552 for ; Wed, 2 Aug 2000 11:56:16 +0200 (CEST) Message-ID: <3987F196.4B7BA798@cs.put.poznan.pl> Date: Wed, 02 Aug 2000 12:01:58 +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: ppp Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Below I have part of ppp.log. Could you tell me what the fifth line does mean? What is CD? When I try to connect using ATDT12345 I get message 'BUSY'. -------------------------------------------------------------------------- Aug 2 11:57:11 sec ppp[205]: tun0: Phase: bundle: Establish Aug 2 11:57:11 sec ppp[205]: tun0: Phase: deflink: closed -> opening Aug 2 11:57:11 sec ppp[205]: tun0: Phase: deflink: Connected! Aug 2 11:57:11 sec ppp[205]: tun0: Phase: deflink: opening -> carrier Aug 2 11:57:12 sec ppp[205]: tun0: Phase: deflink: /dev/cuaa1 doesn't support CD -- what does it mean?? Aug 2 11:57:12 sec ppp[205]: tun0: Phase: deflink: carrier -> ready -------------------------------------------------------------------------- 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 Aug 2 3: 3:38 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 2CA1D37B6DC for ; Wed, 2 Aug 2000 03:03:35 -0700 (PDT) (envelope-from kuriyama@FreeBSD.org) 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 e72A3dG49837 for ; Wed, 2 Aug 2000 19:03:40 +0900 (JST) Date: Wed, 02 Aug 2000 19:03:39 +0900 Message-ID: <7m1z082d50.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: Breakage in pci/if_dc.c User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 10) (Capitol Reef) (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 On my -current box, kernel compilation failed at module building. ===> dc cc -g -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I/usr/include -mpreferred-stack-boundary=2 -c /home/kuriyama/ncvs/src/sys/modules/dc/../../pci/if_dc.c /home/kuriyama/ncvs/src/sys/modules/dc/../../pci/if_dc.c: In function `dc_setcfg': /home/kuriyama/ncvs/src/sys/modules/dc/../../pci/if_dc.c:1228: `DC_WDOG_CTLWREN' undeclared (first use in this function) /home/kuriyama/ncvs/src/sys/modules/dc/../../pci/if_dc.c:1228: (Each undeclared identifier is reported only once /home/kuriyama/ncvs/src/sys/modules/dc/../../pci/if_dc.c:1228: for each function it appears in.) *** Error code 1 Stop in /home/kuriyama/ncvs/src/sys/modules/dc. *** Error code 1 Stop in /home/kuriyama/ncvs/src/sys/modules. *** Error code 1 -- 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 Wed Aug 2 4:45:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 4E14A37B5A4 for ; Wed, 2 Aug 2000 04:45:43 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: from earth (oca-c1s3-15.mfi.net [209.26.94.108]) by pawn.primelocation.net (Postfix) with ESMTP id 54DB29B1C; Wed, 2 Aug 2000 07:45:41 -0400 (EDT) Date: Wed, 2 Aug 2000 07:45:40 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.causticlabs.com To: Piotr =?iso-8859-1?Q?Wo=9Fniak?= Cc: freebsd-current Subject: Re: ppp In-Reply-To: <3987F196.4B7BA798@cs.put.poznan.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Aug 2000, Piotr [iso-8859-1] Wo=9Fniak wrote: > Hi, > Below I have part of ppp.log. > Could you tell me what the fifth line does mean? > What is CD? Carrier Detect? > When I try to connect using ATDT12345 > I get message 'BUSY'. > -------------------------------------------------------------------------= - >=20 > Aug 2 11:57:11 sec ppp[205]: tun0: Phase: bundle: Establish > Aug 2 11:57:11 sec ppp[205]: tun0: Phase: deflink: closed -> opening > Aug 2 11:57:11 sec ppp[205]: tun0: Phase: deflink: Connected! > Aug 2 11:57:11 sec ppp[205]: tun0: Phase: deflink: opening -> carrier >=20 > Aug 2 11:57:12 sec ppp[205]: tun0: Phase: deflink: /dev/cuaa1 doesn't > support CD > -- what does it mean?? >=20 > Aug 2 11:57:12 sec ppp[205]: tun0: Phase: deflink: carrier -> ready > -------------------------------------------------------------------------= - >=20 > Piotr Wozniak >=20 Any relation? :) ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: 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 Aug 2 6:12:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 9743E37B7F3 for ; Wed, 2 Aug 2000 06:12:34 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA56929 for current@freebsd.org; Wed, 2 Aug 2000 15:12:32 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008021312.PAA56929@freebsd.dk> Subject: panic in pmap_clear_reference() To: current@freebsd.org Date: Wed, 2 Aug 2000 15:12:32 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] 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 I keep getting panics on -current since mid juli, they seem to always accour here: IdlePTD 3264512 initial pcb at 299f00 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02133a0 stack pointer = 0x10:0xcbffdf34 frame pointer = 0x10:0xcbffdf3c 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 = 2 (pagedaemon) interrupt mask = net bio cam trap number = 12 panic: page fault #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 #1 0xc0160fa0 in poweroff_wait (junk=0xc0249a0f, howto=-872457120) at ../../kern/kern_shutdown.c:553 #2 0xc0214fb9 in trap_fatal (frame=0xcbffdef4, eva=262144) at ../../i386/i386/trap.c:929 #3 0xc0214c91 in trap_pfault (frame=0xcbffdef4, usermode=0, eva=262144) at ../../i386/i386/trap.c:822 #4 0xc0214863 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = -1072231923, tf_esi = 0, tf_ebp = -872423620, tf_isp = -872423648, tf_ebx = 262144, tf_edx = 0, tf_ecx = -1066433920, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071565920, tf_cs = 8, tf_eflags = 66054, tf_esp = -1068397780, tf_ss = 0}) at ../../i386/i386/trap.c:427 #5 0xc02133a0 in pmap_clear_reference (m=0xc0518b2c) at ../../i386/i386/pmap.c:3012 #6 0xc01e9353 in vm_pageout_scan () at ../../vm/vm_pageout.c:713 #7 0xc01e9f38 in vm_pageout () at ../../vm/vm_pageout.c:1370 #8 0xc020a36c in fork_trampoline () This is happening on 3 different machines now, at first I thought it was bad HW, but since its always here and on 3 machines thats not likely anymore.... Peter ?? Matt ?? Anybody ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 6:19:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 7D21B37B583 for ; Wed, 2 Aug 2000 06:19:38 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 29848 invoked from network); 2 Aug 2000 13:19:37 -0000 Received: from acs-24-154-24-131.zoominternet.net (24.154.24.131) by scully.zoominternet.net with SMTP; 2 Aug 2000 13:19:37 -0000 Date: Wed, 2 Aug 2000 09:19:36 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-24-131.zoominternet.net To: current@freebsd.org Subject: World breakage in usr.bin/kdump 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 -march=pentium -Os -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c In file included from ioctl.c:94: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition In file included from ioctl.c:63: /usr/obj/usr/src/i386/usr/include/net/if_ieee80211.h:14: `ETHER_ADDR_LEN' undeclared here (not in a function) /usr/obj/usr/src/i386/usr/include/net/if_ieee80211.h:15: `ETHER_ADDR_LEN' undeclared here (not in a function) /usr/obj/usr/src/i386/usr/include/net/if_ieee80211.h:16: `ETHER_ADDR_LEN' undeclared here (not in a function) *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 6:28:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id DF54A37B557 for ; Wed, 2 Aug 2000 06:28:50 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13JyZd-000GcA-00; Wed, 02 Aug 2000 15:28:41 +0200 From: Sheldon Hearn To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: World breakage in usr.bin/kdump In-reply-to: Your message of "Wed, 02 Aug 2000 09:19:36 -0400." Date: Wed, 02 Aug 2000 15:28:41 +0200 Message-ID: <63869.965222921@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 02 Aug 2000 09:19:36 -0400, Donn Miller wrote: > In file included from ioctl.c:63: > /usr/obj/usr/src/i386/usr/include/net/if_ieee80211.h:14: `ETHER_ADDR_LEN' > undeclared here (not in a function) I'm pretty sure this was fixed several hours ago. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 6:36:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.houston.rr.com (sm2.texas.rr.com [24.93.35.55]) by hub.freebsd.org (Postfix) with ESMTP id C637137B8F4 for ; Wed, 2 Aug 2000 06:36:11 -0700 (PDT) (envelope-from shocking@houston.rr.com) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 2 Aug 2000 08:34:53 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.9.3/8.9.3) with ESMTP id IAA10139 for ; Wed, 2 Aug 2000 08:32:00 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.9.3/8.9.3) with ESMTP id IAA79893 for ; Wed, 2 Aug 2000 08:31:59 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200008021331.IAA79893@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: More compile errors in current (if_dc.c) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Aug 2000 08:31:59 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -c -O -pipe -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 ../../pci/if_dc.c ../../pci/if_dc.c: In function `dc_setcfg': ../../pci/if_dc.c:1228: `DC_WDOG_CTLWREN' undeclared (first use in this function) ../../pci/if_dc.c:1228: (Each undeclared identifier is reported only once ../../pci/if_dc.c:1228: for each function it appears in.) -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 6:57:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 2124337B5BF for ; Wed, 2 Aug 2000 06:57:53 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13Jz1j-0005v1-00; Wed, 02 Aug 2000 15:57:43 +0200 From: Sheldon Hearn To: Stephen Hocking Cc: current@FreeBSD.ORG Subject: Re: More compile errors in current (if_dc.c) In-reply-to: Your message of "Wed, 02 Aug 2000 08:31:59 EST." <200008021331.IAA79893@bloop.craftncomp.com> Date: Wed, 02 Aug 2000 15:57:43 +0200 Message-ID: <22749.965224663@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 02 Aug 2000 08:31:59 EST, Stephen Hocking wrote: > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extension s > -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include > opt_global.h -elf -mpreferred-stack-boundary=2 ../../pci/if_dc.c > ../../pci/if_dc.c: In function `dc_setcfg': > ../../pci/if_dc.c:1228: `DC_WDOG_CTLWREN' undeclared (first use in this > function) > ../../pci/if_dc.c:1228: (Each undeclared identifier is reported only once > ../../pci/if_dc.c:1228: for each function it appears in.) You can get around this by backing out rev 1.19 of if_dc.c . As developers get progressively slacker about checking their changes, you're going to have to learn to follow your cvs-all mail more closely. :-) Of course, that doesn't apply in this case, since the breakage was immediately merged onto the RELENG_4 branch. ;-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 7: 0:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.houston.rr.com (sm2.texas.rr.com [24.93.35.55]) by hub.freebsd.org (Postfix) with ESMTP id 3044A37B857 for ; Wed, 2 Aug 2000 07:00:39 -0700 (PDT) (envelope-from shocking@houston.rr.com) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 2 Aug 2000 08:59:21 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.9.3/8.9.3) with ESMTP id IAA10159; Wed, 2 Aug 2000 08:56:28 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.9.3/8.9.3) with ESMTP id IAA80008; Wed, 2 Aug 2000 08:56:28 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200008021356.IAA80008@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: More compile errors in current (if_dc.c) In-Reply-To: Your message of "Wed, 02 Aug 2000 15:57:43 +0200." <22749.965224663@axl.ops.uunet.co.za> Reply-To: shocking@houston.rr.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Aug 2000 08:56:27 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah - I was just trying to express my irritation without being overly nasty. Beats me why thing are commited without being compiled though. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 7:30:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 1116D37B68A for ; Wed, 2 Aug 2000 07:30:30 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 13JzXQ-000Mi5-00 for freebsd-current@freebsd.org; Wed, 2 Aug 2000 15:30:28 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id PAA54404 for freebsd-current@freebsd.org; Wed, 2 Aug 2000 15:30:27 +0100 (BST) (envelope-from jcm) Date: Wed, 2 Aug 2000 15:30:27 +0100 From: j mckitrick To: freebsd-current@freebsd.org Subject: ATA66 support Message-ID: <20000802153027.A54330@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A friend of a friend asked me to find out how ATA66 support was coming along. Is it still necessary to disable DMA or PIO settings for it to work? jm -- --------------------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org "The physicist's greatest tool is his wastebasket." - Albert Einstein --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 9: 4:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from rexroof.com (po.wccnet.org [198.111.177.192]) by hub.freebsd.org (Postfix) with ESMTP id C181C37BBFA for ; Wed, 2 Aug 2000 09:04:17 -0700 (PDT) (envelope-from rex@rexroof.com) Received: (from rex@localhost) by rexroof.com (8.9.3/8.9.1) id MAA93444; Wed, 2 Aug 2000 12:04:20 -0400 (EDT) Date: Wed, 2 Aug 2000 12:04:19 -0400 From: "Rex A. Roof" To: freebsd-current@freebsd.org Subject: -current buildkernel problems. Message-ID: <20000802120419.A93439@rexroof.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG after doing a cvsup I tried to build a new kernel and found that I was getting this error: (while doing config) ../../conf/files: coda/coda_fbsd.c must be optional, mandatory or standard so, I searched the mailing lists and found that I needed to update /usr/sbin/config, so I did, and was able to config, and start building the kernel. well, that led me to a rather nice compile error: 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../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s /tmp/ccv99837.s: Assembler messages: /tmp/ccv99837.s:772: Error: operands given don't match any known 386 instruction /tmp/ccv99837.s:837: Error: operands given don't match any known 386 instruction *** Error code 1 After searching the mailing lists (this one) again, I found that the answer was to use the newest gcc, and that I probably want to be using "make buildkernel" in /usr/src, so, thats what I did, and I'm getting this error again: ../../conf/files: coda/coda_fbsd.c must be optional, mandatory or standard so, anyone have an answer? I've also tried compiling the newest gcc, standalone, with no luck. -Rex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 9:25:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3620137BCB6 for ; Wed, 2 Aug 2000 09:25:26 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e72FV0q16847; Wed, 2 Aug 2000 08:31:00 -0700 (PDT) Date: Wed, 2 Aug 2000 08:31:00 -0700 From: Alfred Perlstein To: j mckitrick Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA66 support Message-ID: <20000802083100.X4854@fw.wintelcom.net> References: <20000802153027.A54330@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000802153027.A54330@dogma.freebsd-uk.eu.org>; from jcm@FreeBSD-uk.eu.org on Wed, Aug 02, 2000 at 03:30:27PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * j mckitrick [000802 06:38] wrote: > > A friend of a friend asked me to find out how ATA66 support was coming > along. Is it still necessary to disable DMA or PIO settings for it to work? There's rumors of some "problem" chipsets, but afaik 66 has been working for quite some time. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 10: 4:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 5465237B534 for ; Wed, 2 Aug 2000 10:04:11 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 17109 invoked from network); 2 Aug 2000 17:04:10 -0000 Received: from acs-24-154-24-131.zoominternet.net (24.154.24.131) by scully.zoominternet.net with SMTP; 2 Aug 2000 17:04:10 -0000 Date: Wed, 2 Aug 2000 13:04:10 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-24-131.zoominternet.net To: current@freebsd.org Subject: Latest kernel won't boot 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 Just recently build a kernel from cvsup, and the kernel won't boot. It gets to the point where you see booting [kernel] \ And it just hangs right there. There's a lot of disk activity, and after about 2 minutes (and no boot messages), I see a login prompt, but the machine is froze. Anyone else see this? - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 10:30:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 360F337B83E for ; Wed, 2 Aug 2000 10:30:52 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA23716; Wed, 2 Aug 2000 19:29:30 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008021729.TAA23716@freebsd.dk> Subject: Re: ATA66 support In-Reply-To: <20000802153027.A54330@dogma.freebsd-uk.eu.org> from j mckitrick at "Aug 2, 2000 03:30:27 pm" To: jcm@FreeBSD-uk.eu.org (j mckitrick) Date: Wed, 2 Aug 2000 19:29:30 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] 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 It seems j mckitrick wrote: > > A friend of a friend asked me to find out how ATA66 support was coming > along. Is it still necessary to disable DMA or PIO settings for it to work? ATA66 has been working for quite some time now. Beware that there are some disks that claim to be able to do ATA66 but actually can't. Beware of Maxtor and WD disks in this regard. I can recommend IBM drives, they work very well... ATA100 is just around the corner, it runs here in my lab, and will go into -current in the next couble of weeks (time permitting)... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 11:39:14 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 9A1B337C328 for ; Wed, 2 Aug 2000 11:39:11 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA41655; Wed, 2 Aug 2000 11:38:57 -0700 (PDT) (envelope-from obrien) Date: Wed, 2 Aug 2000 11:38:57 -0700 From: "David O'Brien" To: "Rex A. Roof" Cc: freebsd-current@freebsd.org Subject: Re: -current buildkernel problems. Message-ID: <20000802113857.A41635@dragon.nuxi.com> Reply-To: current@freebsd.org References: <20000802120419.A93439@rexroof.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000802120419.A93439@rexroof.com>; from rex@rexroof.com on Wed, Aug 02, 2000 at 12:04:19PM -0400 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 Wed, Aug 02, 2000 at 12:04:19PM -0400, Rex A. Roof wrote: > /tmp/ccv99837.s: Assembler messages: > /tmp/ccv99837.s:772: Error: operands given don't match any known 386 instruction > /tmp/ccv99837.s:837: Error: operands given don't match any known 386 instruction > After searching the mailing lists (this one) again, > I found that the answer was to use the newest gcc, and that I probably Not GCC, Binutils (assembler and linker). Of course you've told us nothing that allows us to help you. The output from ``uname -a'' being the most important. Also why reather than build and install the various bits you will have to in order to compile a -current kernel, you don't just do a ``make world'' first. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 11:51:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from rexroof.com (po.wccnet.org [198.111.177.192]) by hub.freebsd.org (Postfix) with ESMTP id D3D7837B5F5 for ; Wed, 2 Aug 2000 11:51:49 -0700 (PDT) (envelope-from rex@rexroof.com) Received: (from rex@localhost) by rexroof.com (8.9.3/8.9.1) id OAA94288 for current@freebsd.org; Wed, 2 Aug 2000 14:51:53 -0400 (EDT) Date: Wed, 2 Aug 2000 14:51:53 -0400 From: "Rex A. Roof" To: current@freebsd.org Subject: Re: -current buildkernel problems. Message-ID: <20000802145152.A94276@rexroof.com> References: <20000802120419.A93439@rexroof.com> <20000802113857.A41635@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000802113857.A41635@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Aug 02, 2000 at 11:38:57AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok, here's the output from uname -a FreeBSD shaolin.wccnet.org 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Thu Apr 27 19:04:53 EDT 2000 rex@shaolin.wccnet.org:/usr/src/sys/compile/SHAOLIN i386 usually, in the past, I've found the best way to upgrade (and, what I thought was the proper way) was to make a new kernel, reboot on it, and then build world is that not the right away? -Rex On Wed, Aug 02, 2000 at 11:38:57AM -0700, David O'Brien wrote: > On Wed, Aug 02, 2000 at 12:04:19PM -0400, Rex A. Roof wrote: > > /tmp/ccv99837.s: Assembler messages: > > /tmp/ccv99837.s:772: Error: operands given don't match any known 386 instruction > > /tmp/ccv99837.s:837: Error: operands given don't match any known 386 instruction > > After searching the mailing lists (this one) again, > > I found that the answer was to use the newest gcc, and that I probably > > Not GCC, Binutils (assembler and linker). Of course you've told us > nothing that allows us to help you. The output from ``uname -a'' being > the most important. Also why reather than build and install the various > bits you will have to in order to compile a -current kernel, you don't > just do a ``make world'' first. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 12:33:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 84B0A37B7EC for ; Wed, 2 Aug 2000 12:33:11 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id E34469B3E; Wed, 2 Aug 2000 14:59:00 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id D8147BA11; Wed, 2 Aug 2000 14:59:00 -0400 (EDT) Date: Wed, 2 Aug 2000 14:59:00 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: "Rex A. Roof" Cc: current@freebsd.org Subject: Re: -current buildkernel problems. In-Reply-To: <20000802145152.A94276@rexroof.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 Wed, 2 Aug 2000, Rex A. Roof wrote: > ok, here's the output from uname -a > > FreeBSD shaolin.wccnet.org 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Thu Apr 27 19:04:53 EDT 2000 rex@shaolin.wccnet.org:/usr/src/sys/compile/SHAOLIN i386 > > usually, in the past, I've found the best way to upgrade (and, what > I thought was the proper way) was to make a new kernel, > reboot on it, and then build world > > is that not the right away? > Not according to the handbook. The above is used under OpenBSD though. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: 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 Aug 2 12:48:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from PacHell.TelcoSucks.org (pachell.telcosucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 091F837BB13 for ; Wed, 2 Aug 2000 12:48:38 -0700 (PDT) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id MAA38585; Wed, 2 Aug 2000 12:46:49 -0700 (PDT) (envelope-from ulf) Date: Wed, 2 Aug 2000 12:46:49 -0700 From: Ulf Zimmermann To: Alfred Perlstein Cc: j mckitrick , freebsd-current@FreeBSD.ORG Subject: Re: ATA66 support Message-ID: <20000802124649.O10581@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net References: <20000802153027.A54330@dogma.freebsd-uk.eu.org> <20000802083100.X4854@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000802083100.X4854@fw.wintelcom.net>; from bright@wintelcom.net on Wed, Aug 02, 2000 at 08:31:00AM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 02, 2000 at 08:31:00AM -0700, Alfred Perlstein wrote: > * j mckitrick [000802 06:38] wrote: > > > > A friend of a friend asked me to find out how ATA66 support was coming > > along. Is it still necessary to disable DMA or PIO settings for it to work? > > There's rumors of some "problem" chipsets, but afaik 66 has been working > for quite some time. > > -Alfred atapci0: port 0xffa0-0xffaf at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ad0: 19574MB [39770/16/63] at ata0-master using UDMA66 ad1: 19574MB [39770/16/63] at ata0-slave using UDMA66 Works like a champ with this in my kernel config file: device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 no further settings done. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 12:58:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from jedi.lab.fc.com (machine.fc.com [216.206.226.100]) by hub.freebsd.org (Postfix) with ESMTP id C9F9837BFB5 for ; Wed, 2 Aug 2000 12:58:12 -0700 (PDT) (envelope-from adam@fc.com) Received: from fc.com (localhost [127.0.0.1]) by jedi.lab.fc.com (8.9.3/8.9.3) with ESMTP id UAA02483 for ; Wed, 2 Aug 2000 20:01:16 -0400 (EDT) (envelope-from adam@fc.com) Message-ID: <3988B64C.F6C48068@fc.com> Date: Wed, 02 Aug 2000 20:01:16 -0400 From: Adam Lund X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Wed Aug 2 13:22: 6 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 5C39537B5CB; Wed, 2 Aug 2000 13:21:49 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.138] (helo=mx0.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #2) id 13K51N-0002zU-00; Wed, 02 Aug 2000 22:21:45 +0200 Received: from ade53.pppool.de ([213.6.222.83] helo=Magelan.Leidinger.net) by mx0.freenet.de with esmtp (Exim 3.16 #2) id 13K51M-0000ua-00; Wed, 02 Aug 2000 22:21:45 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id QAA01931; Wed, 2 Aug 2000 16:42:54 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200008021442.QAA01931@Magelan.Leidinger.net> Date: Wed, 2 Aug 2000 16:42:53 +0200 (CEST) From: Alexander Leidinger Subject: Re: Panic in xpt_setup_ccb (cam_xpt.c) To: n_hibma@calcaphon.com Cc: current@FreeBSD.org, gibbs@freebsd.org, scsi@greebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1 Aug, Nick Hibma wrote: > > Hm, I had a look at the source code, and to be honest I can't find a > single reason why the path would be unset. > > Did the CD reader detached itself from the bus in the meantime, or did > something like a bus error occur? Check your messages log around the > time the panic occurred to see if something like that happened. ---snip--- Jul 29 10:40:55 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out in Message-in phase, SEQADDR == 0x194 Jul 29 10:40:55 Magelan /kernel: (cd0:ahc0:0:1:0): BDR message in message buffer Jul 29 10:40:57 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out in Message-in phase, SEQADDR == 0x194 Jul 29 10:40:57 Magelan /kernel: (cd0:ahc0:0:1:0): no longer in timeout, status = 34b Jul 29 10:40:57 Magelan /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Jul 29 10:42:26 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:42:26 Magelan /kernel: (cd0:ahc0:0:1:0): Queuing a BDR SCB Jul 29 10:42:28 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:42:28 Magelan /kernel: (cd0:ahc0:0:1:0): no longer in timeout, status = 34b Jul 29 10:42:28 Magelan /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Jul 29 10:43:04 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:43:04 Magelan /kernel: (cd0:ahc0:0:1:0): Queuing a BDR SCB Jul 29 10:43:06 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:43:06 Magelan /kernel: (cd0:ahc0:0:1:0): no longer in timeout, status = 34b Jul 29 10:43:06 Magelan /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Jul 29 10:43:47 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:43:47 Magelan /kernel: (cd0:ahc0:0:1:0): Queuing a BDR SCB Jul 29 10:43:49 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:43:49 Magelan /kernel: (cd0:ahc0:0:1:0): no longer in timeout, status = 34b Jul 29 10:43:49 Magelan /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Jul 29 10:45:12 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:45:12 Magelan /kernel: (cd0:ahc0:0:1:0): Queuing a BDR SCB Jul 29 10:45:14 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:45:14 Magelan /kernel: (cd0:ahc0:0:1:0): no longer in timeout, status = 34b Jul 29 10:45:14 Magelan /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Jul 29 10:45:51 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:45:51 Magelan /kernel: (cd0:ahc0:0:1:0): Queuing a BDR SCB Jul 29 10:45:53 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:45:53 Magelan /kernel: (cd0:ahc0:0:1:0): no longer in timeout, status = 34b Jul 29 10:45:53 Magelan /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Jul 29 10:47:31 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:47:31 Magelan /kernel: (cd0:ahc0:0:1:0): Queuing a BDR SCB Jul 29 10:47:33 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:47:33 Magelan /kernel: (cd0:ahc0:0:1:0): no longer in timeout, status = 34b Jul 29 10:47:33 Magelan /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Jul 29 10:48:34 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:48:34 Magelan /kernel: (cd0:ahc0:0:1:0): Queuing a BDR SCB Jul 29 10:48:36 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out while idle, SEQADDR == 0x194 Jul 29 10:48:36 Magelan /kernel: (cd0:ahc0:0:1:0): no longer in timeout, status = 34b Jul 29 10:48:37 Magelan /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Jul 29 10:48:47 Magelan /kernel: (cd0:ahc0:0:1:0): SCB 0x7 - timed out in Message-in phase, SEQADDR == 0x194 Jul 29 10:48:47 Magelan /kernel: (cd0:ahc0:0:1:0): BDR message in message buffer ---snip--- > At that point in the code it was using the path variable stored in the > periph and that one is available from when the peripheral was allocated > up to the point where the refcount for the peripheral reaches zero (that > could be wrong) or the device is invalidated. Justin Gibbs (CCed) is looking into a bug with an aic7880, which hit the tree with his recent commits, perhaps it's related. Bye, Alexander. -- If Bill Gates had a dime for every time a Windows box crashed... ...Oh, wait a minute, he already does. 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 Wed Aug 2 13:38:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 50AB537BF17; Wed, 2 Aug 2000 13:38:31 -0700 (PDT) (envelope-from jeremyp@pc0640.alcatel.com.au) Received: by border.alcanet.com.au id <115235>; Thu, 3 Aug 2000 06:35:33 +1000 From: Peter Jeremy Subject: Re: randomdev entropy gathering is really weak In-reply-to: <3983BC3E.B100117D@vangelderen.org>; from jeroen@vangelderen.org on Sun, Jul 30, 2000 at 01:25:18AM -0400 To: "Jeroen C. van Gelderen" Cc: Brian Fundakowski Feldman , current@FreeBSD.ORG, Mark Murray , Kris Kennaway Message-Id: <00Aug3.063533est.115235@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <3983BC3E.B100117D@vangelderen.org> Date: Thu, 3 Aug 2000 06:35:31 +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 30, 2000 at 01:25:18AM -0400, Jeroen C. van Gelderen wrote: >Hmm, maybe the complainers should provide proof that they do >need more than 2^256 complexity. Makes it easier for us, >proponents ;-/ How about creating one-time pads? That said, in Applied Cryptography, Schneier makes the comment (end of section 7.1) that, based on thermodynamic limitations, "brute force attacks against 256-bit keys will be infeasible until computers are build from something other than matter and occupy something other than space". (Though it's possible that a quantum computer would meet those criteria - since it doesn't need to iterate through all possible keys, it can bypass that part of the second law of thermodynamics). This implies that if brute force is the best attack against Yarrow-256 (Blowfish), it is unbreakable. (Of course, that's a big if). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 14:40: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 708C337BA8E; Wed, 2 Aug 2000 14:39:42 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.85.14]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000802213940.FXAF26680.mta01-svc.ntlworld.com@parish.my.domain>; Wed, 2 Aug 2000 22:39:40 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id WAA01713; Wed, 2 Aug 2000 22:39:30 +0100 (BST) (envelope-from mark) Date: Wed, 2 Aug 2000 22:39:30 +0100 From: Mark Ovens To: current@freebsd.org Cc: wollman@FreeBSD.org, drosih@rpi.edu Subject: Request for review Message-ID: <20000802223930.C236@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i Organization: Total lack of Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I originally sent this to -committers but was advised that the maintainers and -hackers or -current was more appropriate. I've posted some patches for PR 14682 which include some changes to the source code for lpr(1), lprm(1) etc. Could someone review them for me please, especially the C code. Thanks. (please Cc: me as I'm not subscribed to -current) -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 18:35:24 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 957CA37B506; Wed, 2 Aug 2000 18:35:19 -0700 (PDT) (envelope-from drosih@rpi.edu) 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 VAA55782; Wed, 2 Aug 2000 21:35:18 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000802223930.C236@parish> References: <20000802223930.C236@parish> Date: Wed, 2 Aug 2000 21:35:23 -0400 To: Mark Ovens , current@freebsd.org From: Garance A Drosihn Subject: Re: Request for review (LPDEST vs PRINTER) Cc: wollman@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:39 PM +0100 8/2/00, Mark Ovens wrote: >I originally sent this to -committers but was advised that the >maintainers and -hackers or -current was more appropriate. > >I've posted some patches for PR 14682 which include some changes >to the source code for lpr(1), lprm(1) etc. > >Could someone review them for me please, especially the C code. Your comments in the PR included: Whilst investigating this problem I found in /usr/bin/lp: # Posix 1003.2 compliant print spooler interface. [snip] # Posix says LPDEST gets precedence over PRINTER dest=${LPDEST:-${PRINTER:-lp}} So it would seem that the Right Thing(tm) to do is to make the other programs POSIX-compliant by making them honour the LPDEST environment variable rather than simply documenting the fact that they don't (the manpages need updating to reflect this). Strictly speaking, that is not the right thing to do. POSIX is talking about the 'lp' command, which is one of the commands from the SysV-ish printing world. 'lpr' is the BSD-ish print world, and therefore it is not covered by what POSIX describes for 'lp'. These are two different command sets for printing. The 'lprm' command is also part of the BSD-ish print world. I do not have a reference for what POSIX says about commands, but the "Single Unix Specification" has a description of the 'lp' command. The description for 'lp' does not talk about the 'lprm' command. It says the way to cancel print jobs sent via the 'lp' command is via the 'cancel' command. It also talks about using 'lpstat' instead of 'lpq'. So, strictly speaking, if we wanted POSIX compliance then we should add 'cancel' and 'lpstat' commands, and have those commands behave as POSIX describes them. If POSIX does also describe the behavior of the 'lprm' or 'lpq' commands, then we could talk about changing those commands to be POSIX-compliant. I would guess that it doesn't have them. So, that is my off-the-cuff pedantic-mode reaction, which is not much help in closing the PR... I don't feel too strongly about this, but in general I'd rather document that LPDEST is not used by lpr/lpq/lprm, and maybe later on add cancel/lpstat commands for those people who are really expecting the "POSIX print system". The other printing-system alternative is LPRng (which people can install from ports). LPRng does add the 'lpstat' command, in addition to replacing lpr/lpq/lprm. And if I am reading this code right, it does check LPDEST for all of those commands, *-but-* it has PRINTER taking precedence over LPDEST, and not the way POSIX (apparently) describes it. If we do add checking for LPDEST, I would probably have PRINTER continue to take precedence over LPDEST. Right now, anyone who *is* setting both variables must be used to the idea that PRINTER is the value lpr/lprm/lpq uses, and I do not think we should change that. I would also like to see what openbsd and netbsd do for this, if anything, but I haven't the time right now. As to your actual C code, it looks like it would work fine, if we wanted to do that. --- 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 Wed Aug 2 21:30:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with SMTP id D8BFB37B606; Wed, 2 Aug 2000 21:29:50 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115260>; Thu, 3 Aug 2000 14:29:42 +1000 Content-return: prohibited Date: Thu, 03 Aug 2000 14:28:44 +1000 From: Peter Jeremy Subject: Loss of fetch(1) functionality with libfetch To: des@FreeBSD.ORG Cc: current@FreeBSD.ORG Mail-followup-to: des@freebsd.org, current@freebsd.org Message-Id: <00Aug3.142942est.115260@border.alcanet.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't recall seeing this mentioned: In order to access the Internet, I need to use proxy authorization. With the old fetch(1) I could use an environment variable like "HTTP_PROXY_AUTH=basic:*:" and it would prompt for a password. The new libfetch-based fetch(1) ignores the HTTP_PROXY_AUTH variable unless it is in the form "HTTP_PROXY_AUTH=basic:*::" and doesn't appear to have any provision for requesting a password. (HTTP_AUTH appears to suffer from the same problem). Whilst the environment is somewhat safer than the command line, I'd still prefer not to have passwords embedded in environment variables. Has this feature been deliberately left out, or is it just one of the bits that you haven't gotten around to implementing yet? Would you be interested in patches to implement it? On a related note, I noticed the following bug - though it has no effect on the operation of libfetch in its current form. Index: http.c =================================================================== RCS file: /home/CVSROOT/src/lib/libfetch/http.c,v retrieving revision 1.34 diff -u -r1.34 http.c --- http.c 2000/07/25 11:45:38 1.34 +++ http.c 2000/08/03 04:25:53 @@ -91,7 +91,7 @@ #define HTTP_MOVED_TEMP 302 #define HTTP_SEE_OTHER 303 #define HTTP_NEED_AUTH 401 -#define HTTP_NEED_PROXY_AUTH 403 +#define HTTP_NEED_PROXY_AUTH 407 #define HTTP_PROTOCOL_ERROR 999 #define HTTP_REDIRECT(xyz) ((xyz) == HTTP_MOVED_PERM \ Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 2 23:46:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 8342337B752 for ; Wed, 2 Aug 2000 23:46:13 -0700 (PDT) (envelope-from topper.harley@ntlworld.com) Received: from conax ([62.253.88.89]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with SMTP id <20000803064556.HZRD26680.mta01-svc.ntlworld.com@conax> for ; Thu, 3 Aug 2000 07:45:56 +0100 From: "Steve" To: "Freebsd-Current" Subject: Problem with tun device and trafshow/tcpdump? Date: Thu, 3 Aug 2000 07:44:01 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everyone. Ok apologies first to anyone who has been asked this question before, I've searched the mail lists and cannot find anything like this recently. The problem is when using user ppp and some kind of traffic monitor program like trafshow or tcpdump. There are three problems I've noticed: 1, When using trafshow there's no incoming packets seen at all. 2, When using tcpdump or trafshow there's no name resolution on any packets shown. 3, When using tcpdump, incoming packets can been seen on the tun device, except incoming icmp. Can anyone suggest a fix for this? I was also told that 4.0-RELEASE is affected by this. Thanks for your time. Steve. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 3 4:26:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2CCE937B6FD for ; Thu, 3 Aug 2000 04:26:11 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id NAA36582; Thu, 3 Aug 2000 13:26:02 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: Loss of fetch(1) functionality with libfetch References: <00Aug3.142942est.115260@border.alcanet.com.au> From: Dag-Erling Smorgrav Date: 03 Aug 2000 13:26:01 +0200 In-Reply-To: Peter Jeremy's message of "Thu, 03 Aug 2000 14:28:44 +1000" Message-ID: Lines: 23 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy writes: > Whilst the environment is somewhat safer than the command line, I'd > still prefer not to have passwords embedded in environment variables. Since ps(1) no longer allows users to view other users' processes' environment, I don't think it's a very big issue anymore. > Has this feature been deliberately left out, or is it just one of the > bits that you haven't gotten around to implementing yet? Would you > be interested in patches to implement it? Sure. The only clean way of doing this (that I can think of) would be to add an interface to libfetch for registering password-prompting callbacks. > On a related note, I noticed the following bug - though it has no > effect on the operation of libfetch in its current form. Correct, thanks. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 3 4:46: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 48CF037B914 for ; Thu, 3 Aug 2000 04:46:12 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id HAA21233; Thu, 3 Aug 2000 07:46:10 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200008031146.HAA21233@blackhelicopters.org> Subject: Re: Latest kernel won't boot In-Reply-To: from Donn Miller at "Aug 2, 2000 1: 4:10 pm" To: dmmiller@cvzoom.net (Donn Miller) Date: Thu, 3 Aug 2000 07:46:10 -0400 (EDT) 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 > Just recently build a kernel from cvsup, and the kernel won't boot. It > gets to the point where you see > > booting [kernel] > \ > > And it just hangs right there. There's a lot of disk activity, and after > about 2 minutes (and no boot messages), I see a login prompt, but the > machine is froze. Anyone else see this? > > - Donn > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 3 4:48:21 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 A4A2937B91B for ; Thu, 3 Aug 2000 04:48:17 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id HAA21250; Thu, 3 Aug 2000 07:48:16 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200008031148.HAA21250@blackhelicopters.org> Subject: Re: Latest kernel won't boot In-Reply-To: from Donn Miller at "Aug 2, 2000 1: 4:10 pm" To: dmmiller@cvzoom.net (Donn Miller) Date: Thu, 3 Aug 2000 07:48:16 -0400 (EDT) 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 Sorry for the last try, not enough caffiene yet... Anyway, I had this problem as well. The problem was that /boot/loader wasn't working properly. Without it, the system runs, but you can't talk to the console. You can either boot from fixit cdrom and install a new /boot/loader or, as I did, use a serial console to connect to the machine. (You might be able to connect via TCP/IP as well; the system that had this problem is a laptop, and gets configured via a shell script after login.) Good luck! ==ml > Just recently build a kernel from cvsup, and the kernel won't boot. It > gets to the point where you see > > booting [kernel] > \ > > And it just hangs right there. There's a lot of disk activity, and after > about 2 minutes (and no boot messages), I see a login prompt, but the > machine is froze. Anyone else see this? > > - Donn > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 3 6:38:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 9E51337B72E for ; Thu, 3 Aug 2000 06:38:33 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 27116 invoked from network); 3 Aug 2000 13:38:33 -0000 Received: from acs-24-154-24-131.zoominternet.net (24.154.24.131) by scully.zoominternet.net with SMTP; 3 Aug 2000 13:38:33 -0000 Date: Thu, 3 Aug 2000 09:38:33 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-24-131.zoominternet.net To: Michael Lucas Cc: current@FreeBSD.ORG Subject: Re: Latest kernel won't boot In-Reply-To: <200008031148.HAA21250@blackhelicopters.org> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1612695802-965309913=:237" 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-1612695802-965309913=:237 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 3 Aug 2000, Michael Lucas wrote: > Sorry for the last try, not enough caffiene yet... > > Anyway, I had this problem as well. The problem was that /boot/loader > wasn't working properly. Without it, the system runs, but you can't > talk to the console. It seems like the problem was with my device.hints file - I had deleted all the kbd/sc/vga stuff out of there, assuming that they weren't needed since they are on the pci bus. It turns out that I can only boot when I add the syscons stuff back in there. And then, they want to attach to the ISA bus instead of the PCI bus: sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atkbdc0: at port 0x60,0x64 irq 1 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 Any particular reason these devices want to attach to the ISA instead of the PCI bus? Or, are they REALLY attaching to the PCI bus, and thinking they're attaching to the ISA bus? I have a Pentium MoBo (Asus SP 97-V), so they really ought to be on pci0 instead of isa0. So, the syscons/vga/atkbd stuff will not work without leaving them un-modified in device.hints as they originally appear in GENERIC.hints. Attached is my device.hints and dmesg.out. - Donn --0-1612695802-965309913=:237 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dmesg.out" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk3OSwgMTk4MCwgMTk4MywgMTk4NiwgMTk4OCwg MTk4OSwgMTk5MSwgMTk5MiwgMTk5MywgMTk5NA0KCVRoZSBSZWdlbnRzIG9m IHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuIEFsbCByaWdodHMgcmVz ZXJ2ZWQuDQpGcmVlQlNEIDUuMC1DVVJSRU5UICMwOiBUaHUgQXVnICAzIDA4 OjQ0OjQ2IEVEVCAyMDAwDQogICAgZG1taWxsZXJAYWNzLTI0LTE1NC0yNC0x MzEuem9vbWludGVybmV0Lm5ldDovdXNyL3NyYy9zeXMvY29tcGlsZS9DVVNU T00NClRpbWVjb3VudGVyICJpODI1NCIgIGZyZXF1ZW5jeSAxMTkzMTgyIEh6 DQpUaW1lY291bnRlciAiVFNDIiAgZnJlcXVlbmN5IDE2NjQ0OTgzMiBIeg0K Q1BVOiBQZW50aXVtL1A1NUMgKDE2Ni40NS1NSHogNTg2LWNsYXNzIENQVSkN CiAgT3JpZ2luID0gIkdlbnVpbmVJbnRlbCIgIElkID0gMHg1NDMgIFN0ZXBw aW5nID0gMw0KICBGZWF0dXJlcz0weDgwMDFiZjxGUFUsVk1FLERFLFBTRSxU U0MsTVNSLE1DRSxDWDgsTU1YPg0KcmVhbCBtZW1vcnkgID0gNjI5MTQ1NjAg KDYxNDQwSyBieXRlcykNCmF2YWlsIG1lbW9yeSA9IDU3NzYxNzkyICg1NjQw OEsgYnl0ZXMpDQpQcmVsb2FkZWQgZWxmIGtlcm5lbCAia2VybmVsIiBhdCAw eGMwMzdhMDAwLg0KUHJlbG9hZGVkIHVzZXJjb25maWdfc2NyaXB0ICIvYm9v dC9rZXJuZWwuY29uZiIgYXQgMHhjMDM3YTA5Yy4NCkludGVsIFBlbnRpdW0g ZGV0ZWN0ZWQsIGluc3RhbGxpbmcgd29ya2Fyb3VuZCBmb3IgRjAwRiBidWcN Cm1kMDogTWFsbG9jIGRpc2sNCm5weDA6IDxtYXRoIHByb2Nlc3Nvcj4gb24g bW90aGVyYm9hcmQNCm5weDA6IElOVCAxNiBpbnRlcmZhY2UNCnBjaWIwOiA8 SG9zdCB0byBQQ0kgYnJpZGdlPiBvbiBtb3RoZXJib2FyZA0KcGNpMDogPFBD SSBidXM+IG9uIHBjaWIwDQpwY2kwOiA8SG9zdCB0byBQQ0kgYnJpZGdlICh2 ZW5kb3I9MTAzOSBkZXZpY2U9NTU5Nyk+IGF0IDAuMA0KaXNhYjA6IDxTaVMg ODVjNTAzIFBDSS1JU0EgYnJpZGdlPiBhdCBkZXZpY2UgMS4wIG9uIHBjaTAN CmlzYTA6IDxJU0EgYnVzPiBvbiBpc2FiMA0KYXRhcGNpMDogPFNpUyA1NTkx IEFUQTMzIGNvbnRyb2xsZXI+IHBvcnQgMHhkMDAwLTB4ZDAwZiwweGQ0MDAt MHhkNDAzLDB4ZDgwMC0weGQ4MDcsMHhlMDAwLTB4ZTAwMywweGU0MDAtMHhl NDA3IGlycSAxMSBhdCBkZXZpY2UgMS4xIG9uIHBjaTANCmF0YTA6IGF0IDB4 MWYwIGlycSAxNCBvbiBhdGFwY2kwDQphdGExOiBhdCAweDE3MCBpcnEgMTUg b24gYXRhcGNpMA0KZWQwOiA8TkUyMDAwIFBDSSBFdGhlcm5ldCAoUmVhbFRl ayA4MDI5KT4gcG9ydCAweGI4MDAtMHhiODFmIGlycSAxMCBhdCBkZXZpY2Ug MTAuMCBvbiBwY2kwDQplZDA6IGFkZHJlc3MgMDA6YzA6ZGY6ZWQ6MGI6MTcs IHR5cGUgTkUyMDAwICgxNiBiaXQpIA0KcGNpMDogPFNpUyA1NTk3Lzk4IFNW R0EgY29udHJvbGxlcj4gYXQgMTkuMCBpcnEgMTENCnNpbzIgYXQgcG9ydCAw eDNlOC0weDNlZiBpcnEgNCBvbiBpc2EwDQpzaW8yOiB0eXBlIDE2NTUwQQ0K bXNlMDogPEJ1cy9JblBvcnQgTW91c2U+IGF0IHBvcnQgMHgyM2MtMHgyM2Yg aXJxIDMgb24gaXNhMA0Kc2MwOiA8U3lzdGVtIGNvbnNvbGU+IG9uIGlzYTAN CnNjMDogVkdBIDwxNiB2aXJ0dWFsIGNvbnNvbGVzLCBmbGFncz0weDIwMD4N CnZnYTA6IDxHZW5lcmljIElTQSBWR0E+IGF0IHBvcnQgMHgzYzAtMHgzZGYg aW9tZW0gMHhhMDAwMC0weGJmZmZmIG9uIGlzYTANCnNiYzE6IDxFU1MgRVMx ODY4PiBhdCBwb3J0IDB4MjIwLTB4MjJmLDB4Mzg4LTB4MzhiLDB4MzMwLTB4 MzMxIGlycSA1IGRycSAxLDAgb24gaXNhMA0KcGNtMDogPEVTUyAxOHh4IERT UD4gb24gc2JjMQ0KcHBjMDogPEVDUCBwYXJhbGxlbCBwcmludGVyIHBvcnQ+ IGF0IHBvcnQgMHgzNzgtMHgzN2YsMHg3NzgtMHg3N2YgaXJxIDcgZHJxIDMg b24gaXNhMA0KcHBjMDogU01DLWxpa2UgY2hpcHNldCAoRUNQL0VQUC9QUzIv TklCQkxFKSBpbiBDT01QQVRJQkxFIG1vZGUNCnBwYzA6IEZJRk8gd2l0aCAx Ni8xNi8xNiBieXRlcyB0aHJlc2hvbGQNCnBsaXAwOiA8UExJUCBuZXR3b3Jr IGludGVyZmFjZT4gb24gcHBidXMwDQpscHQwOiA8UHJpbnRlcj4gb24gcHBi dXMwDQpscHQwOiBJbnRlcnJ1cHQtZHJpdmVuIHBvcnQNCnBwaTA6IDxQYXJh bGxlbCBJL08+IG9uIHBwYnVzMA0KdW5rbm93bjogPFBOUDA1MDE+IGNhbid0 IGFzc2lnbiByZXNvdXJjZXMNCnVua25vd246IDxQTlAwNTAxPiBjYW4ndCBh c3NpZ24gcmVzb3VyY2VzDQpmZGMwOiA8TkVDIDcyMDY1QiBvciBjbG9uZT4g YXQgcG9ydCAweDNmMi0weDNmNSwweDNmNyBpcnEgNiBkcnEgMiBvbiBpc2Ew DQphdGtiZGMwOiA8S2V5Ym9hcmQgY29udHJvbGxlciAoaTgwNDIpPiBhdCBw b3J0IDB4NjAsMHg2NCBpcnEgMSBvbiBpc2EwDQphdGtiZDA6IDxBVCBLZXli b2FyZD4gZmxhZ3MgMHgxIGlycSAxIG9uIGF0a2JkYzANCmtiZDAgYXQgYXRr YmQwDQphZDA6IDMwOTNNQiA8RlVKSVRTVSBNUEIzMDMyQVRVPiBbNjcwNC8x NS82M10gYXQgYXRhMC1tYXN0ZXIgdXNpbmcgVURNQTMzDQphZDE6IDEwNDBN QiA8TTE2MTRUQT4gWzIxMTQvMTYvNjNdIGF0IGF0YTAtc2xhdmUgdXNpbmcg V0RNQTINCmFjZDA6IENEUk9NIDxCQ0QtMjRYIDE5OTctMDYtMjc+IGF0IGF0 YTEtbWFzdGVyIHVzaW5nIFdETUEyDQo= --0-1612695802-965309913=:237 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="device.hints" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="device.hints" IyAkRnJlZUJTRDogc3JjL3N5cy9pMzg2L2NvbmYvR0VORVJJQy5oaW50cyx2 IDEuMyAyMDAwLzA3LzE5IDE2OjMyOjM4IGltcCBFeHAgJA0KaGludC5hdGti ZGMuMC5hdD0icGNpIg0KaGludC5hdGtiZGMuMC5wb3J0PSIweDA2MCINCmhp bnQuYXRrYmQuMC5hdD0iYXRrYmRjIg0KaGludC5hdGtiZC4wLmlycT0iMSIN CmhpbnQuYXRrYmQuMC5mbGFncz0iMHgxIg0KaGludC5wc20uMC5hdD0iYXRr YmRjIg0KaGludC5wc20uMC5pcnE9IjEyIg0KaGludC5wc20uMC5kaXNhYmxl ZD0iMSINCmhpbnQudmdhLjAuYXQ9InBjaSINCmhpbnQuc2MuMC5hdD0icGNp Ig0KaGludC5zYy4wLmZsYWdzPSIweDEwMCINCmhpbnQubnB4LjAuYXQ9Im5l eHVzIg0KaGludC5ucHguMC5wb3J0PSIweDBGMCINCmhpbnQubnB4LjAuaXJx PSIxMyINCmhpbnQuYXBtLjAuYXQ9Im5leHVzIg0KaGludC5hcG0uMC5kaXNh YmxlZD0iMSINCmhpbnQuYXBtLjAuZmxhZ3M9IjB4MjAiDQpoaW50LnNpby4w LmF0PSJpc2EiDQpoaW50LnNpby4wLnBvcnQ9IjB4M0Y4Ig0KaGludC5zaW8u MC5mbGFncz0iMHgxMCINCmhpbnQuc2lvLjAuaXJxPSI0Ig0KaGludC5zaW8u MC5kaXNhYmxlZD0iMSINCmhpbnQuc2lvLjEuYXQ9ImlzYSINCmhpbnQuc2lv LjEucG9ydD0iMHgyRjgiDQpoaW50LnNpby4xLmlycT0iMyINCmhpbnQuc2lv LjEuZGlzYWJsZWQ9IjEiDQpoaW50LnNpby4yLmF0PSJpc2EiDQpoaW50LnNp by4yLnBvcnQ9IjB4M0U4Ig0KaGludC5zaW8uMi5pcnE9IjQiDQpoaW50LnNp by4zLmF0PSJpc2EiDQpoaW50LnNpby4zLmRpc2FibGVkPSIxIg0KaGludC5z aW8uMy5wb3J0PSIweDJFOCINCmhpbnQuc2lvLjMuaXJxPSI5Ig0KaGludC5t c2UuMC5hdD0iaXNhIg0KaGludC5tc2UuMC5wb3J0PSIweDIzYyINCmhpbnQu bXNlLjAuaXJxPSIzIg0KaGludC5zYmMuMC5hdD0iaXNhIg0KaGludC5zYmMu MC5wb3J0PSIweDIyMCINCmhpbnQuc2JjLjAuaXJxPSI1Ig0KaGludC5zYmMu MC5kcnE9IjEiDQpoaW50LnNiYy4wLmZsYWdzPSIweDE1Ig0K --0-1612695802-965309913=:237-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 3 7:25:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from milquetoast.cs.mcgill.ca (milquetoast.CS.McGill.CA [132.206.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 88D3337B80A for ; Thu, 3 Aug 2000 07:25:22 -0700 (PDT) (envelope-from mat@milquetoast.cs.mcgill.ca) Received: (from mat@localhost) by milquetoast.cs.mcgill.ca (8.9.3/8.9.3) id KAA17633 for freebsd-current@freebsd.org; Thu, 3 Aug 2000 10:25:13 -0400 (EDT) Date: Thu, 3 Aug 2000 10:25:12 -0400 From: Mathew KANNER To: freebsd-current@freebsd.org Subject: ntpdate bug(?) Message-ID: <20000803102512.B15819@cs.mcgill.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Organization: SOCS, McGill University, Montreal, CANADA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I posted something similar on -questions but had no reponse. Could someone tell me if this is a bug? Ntpdate won't set the date when the current date is ahead but will set the date when it's behind. I've noticed this on 4.1 and -current from this past weekend. (I'm not talking about the 'send: Socket...' problem). bash-2.03# date Thu Aug 3 10:15:32 EDT 2000 bash-2.03# date 0008041015 date: send: Socket is not connected Fri Aug 4 10:15:00 EDT 2000 bash-2.03# Aug 4 10:15:00 magnet date: date set by root bash-2.03# ntpdate gps.freebsd.dk 4 Aug 10:15:16 ntpdate[404]: adjust time server 212.242.40.181 offset -86356.115919 sec bash-2.03# date Fri Aug 4 10:15:18 EDT 2000 <---- This is what I mean bash-2.03# date 0008011015 date: send: Socket is not connected Tue Aug 1 10:15:00 EDT 2000 bash-2.03# ntpdate gps.freebsd.dk 3 Aug 10:16:25 ntpdate[407]: step time server 212.242.40.181 offset 172878.565883 sec bash-2.03# date Thu Aug 3 10:16:26 EDT 2000 bash-2.03# --Mat -- Mathew Kanner Systems Programmer, SOCS McGill University Obtuse quote: He [not me] understands: "This field of perception is void of perception of man." -- The Quintessence of Buddhism To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 3 9:53: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id A11EF37B5B5 for ; Thu, 3 Aug 2000 09:53:03 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id SAA17116; Thu, 3 Aug 2000 18:45:17 +0200 (MET DST) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id SAA06617; Thu, 3 Aug 2000 18:37:21 +0200 (CEST) (envelope-from andreas) Date: Thu, 3 Aug 2000 18:37:21 +0200 From: Andreas Klemm To: Soren Schmidt Cc: j mckitrick , freebsd-current@FreeBSD.ORG Subject: Re: ATA66 support Message-ID: <20000803183721.A6597@titan.klemm.gtn.com> References: <20000802153027.A54330@dogma.freebsd-uk.eu.org> <200008021729.TAA23716@freebsd.dk> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200008021729.TAA23716@freebsd.dk>; from sos@freebsd.dk on Wed, Aug 02, 2000 at 07:29:30PM +0200 X-Operating-System: FreeBSD 4.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 02, 2000 at 07:29:30PM +0200, Soren Schmidt wrote: > It seems j mckitrick wrote: > > > > A friend of a friend asked me to find out how ATA66 support was coming > > along. Is it still necessary to disable DMA or PIO settings for it to work? > > ATA66 has been working for quite some time now. Beware that there are > some disks that claim to be able to do ATA66 but actually can't. > Beware of Maxtor and WD disks in this regard. I can recommend IBM > drives, they work very well... I can confirm, that for example the Tyan Titan Pro has chipsets builtin that doesn't grok ATA66. I met somebody who programmed BIOSes and such ... So now I know, why even buying a separate ATA PCI controller didn't work ... so in this case its not the harddisk ... -- Andreas Klemm Songs from our band........................http://people.freebsd.org/~andreas/ Powered by FreeBSD SMP...............http://www.freebsd.org/~fsmp/SMP/SMP.html Please note: Apsfilter got a NEW HOME................http://www.apsfilter.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 3 9:58:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3C92537B51D for ; Thu, 3 Aug 2000 09:58:17 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA60523; Thu, 3 Aug 2000 18:56:55 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008031656.SAA60523@freebsd.dk> Subject: Re: ATA66 support In-Reply-To: <20000803183721.A6597@titan.klemm.gtn.com> from Andreas Klemm at "Aug 3, 2000 06:37:21 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Thu, 3 Aug 2000 18:56:55 +0200 (CEST) Cc: jcm@FreeBSD-uk.eu.org (j mckitrick), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] 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 It seems Andreas Klemm wrote: > On Wed, Aug 02, 2000 at 07:29:30PM +0200, Soren Schmidt wrote: > > It seems j mckitrick wrote: > > > > > > A friend of a friend asked me to find out how ATA66 support was coming > > > along. Is it still necessary to disable DMA or PIO settings for it to work? > > > > ATA66 has been working for quite some time now. Beware that there are > > some disks that claim to be able to do ATA66 but actually can't. > > Beware of Maxtor and WD disks in this regard. I can recommend IBM > > drives, they work very well... > > I can confirm, that for example the Tyan Titan Pro has chipsets > builtin that doesn't grok ATA66. Ehm, you mean because the HW design on the board is broken, or because the chip hasn't ATA66 support ? I the first case there is nothing we can do about it, in the second case we will utilize what the chip can... > I met somebody who programmed BIOSes and such ... We dont use the BIOS for ATA DMA.... What do you mean with the above statement ? > So now I know, why even buying a separate ATA PCI controller didn't > work ... so in this case its not the harddisk ... ???? The motherboard has to be severely broken if a PCI controller wont work... What HW are we talking about here ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 3 10:38:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 22C1C37B584 for ; Thu, 3 Aug 2000 10:38:01 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id TAA20299; Thu, 3 Aug 2000 19:30:16 +0200 (MET DST) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id TAA08495; Thu, 3 Aug 2000 19:15:39 +0200 (CEST) (envelope-from andreas) Date: Thu, 3 Aug 2000 19:15:38 +0200 From: Andreas Klemm To: Soren Schmidt Cc: Andreas Klemm , j mckitrick , freebsd-current@FreeBSD.ORG Subject: Re: ATA66 support Message-ID: <20000803191538.A8387@titan.klemm.gtn.com> References: <20000803183721.A6597@titan.klemm.gtn.com> <200008031656.SAA60523@freebsd.dk> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200008031656.SAA60523@freebsd.dk>; from sos@freebsd.dk on Thu, Aug 03, 2000 at 06:56:55PM +0200 X-Operating-System: FreeBSD 4.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 03, 2000 at 06:56:55PM +0200, Soren Schmidt wrote: > It seems Andreas Klemm wrote: > > On Wed, Aug 02, 2000 at 07:29:30PM +0200, Soren Schmidt wrote: > > I can confirm, that for example the Tyan Titan Pro has chipsets > > builtin that doesn't grok ATA66. > > Ehm, you mean because the HW design on the board is broken, or > because the chip hasn't ATA66 support ? Because of the "chipset" ... "BX and such" which is needed for the flavour of CPU you use... Don't ask me on chipsets, can't remember the names ... > > I met somebody who programmed BIOSes and such ... > We dont use the BIOS for ATA DMA.... > What do you mean with the above statement ? Excuse me ... chipsets I mean not BIOS. > > So now I know, why even buying a separate ATA PCI controller didn't > > work ... so in this case its not the harddisk ... > > ???? I bought a separate ATA PCI controller which is capable of ATA 66. But using an ATA-66 capable cable causes the system to hang during boot. atapci0: at device 7.1 on pci0 atapci0: Busmastering DMA not enabled atapci1: port 0xac00-0xacff,0xa800-0xa803,0xa400-0xa407 irq 15 at device 14.0 on pci0 ata2: at 0xa400 on atapci1 atapci2: port 0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 irq 15 at device 14.1 on pci0 > The motherboard has to be severely broken if a PCI controller wont work... > What HW are we talking about here ? Tyan Titan Pro, SMP board, 2 x 200 PPro 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 4.1-STABLE #0: Fri Jul 28 08:09:24 CEST 2000 root@titan.klemm.gtn.com:/usr/src/sys/compile/TITAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 159383552 (155648K bytes) avail memory = 150999040 (147460K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 15 IOAPIC #0 intpin 17 -> irq 11 IOAPIC #0 intpin 18 -> irq 10 IOAPIC #0 intpin 19 -> irq 14 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc038f000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc038f09c. VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc03289c2 (1000022) VESA: Matrox Graphics Inc. Pentium Pro MTRR support enabled 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: at device 7.1 on pci0 atapci0: Busmastering DMA not enabled pci0: at 10.0 xl0: <3Com 3c900-COMBO Etherlink XL> port 0x9400-0x943f irq 14 at device 11.0 on pci0 xl0: Ethernet address: 00:60:97:aa:3a:db xl0: selecting 10baseT transceiver, half duplex pcm0: port 0x9800-0x981f irq 10 at device 12.0 on pci0 ahc0: port 0xa000-0xa0ff mem 0xe2000000-0xe2000fff irq 11 at device 13.0 on pci0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs atapci1: port 0xac00-0xacff,0xa800-0xa803,0xa400-0xa407 irq 15 at device 14.0 on pci0 ata2: at 0xa400 on atapci1 atapci2: port 0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 irq 15 at device 14.1 on pci0 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 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <4 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/15 bytes threshold ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: MLC,PCL,PML ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 5 on isa0 ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) ahc0: Someone reset channel A APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default DUMMYNET initialized (000608) IPv6 packet filtering initialized, logging limited to 100 packets/entry SMP: AP CPU #1 Launched! ad4: 39082MB [79406/16/63] at ata2-master using UDMA33 Waiting 8 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 4.807MB/s transfers (4.807MHz, offset 8) Mounting root from ufs:/dev/ad4s2a cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present -- Andreas Klemm Songs from our band........................http://people.freebsd.org/~andreas/ Powered by FreeBSD SMP...............http://www.freebsd.org/~fsmp/SMP/SMP.html Please note: Apsfilter got a NEW HOME................http://www.apsfilter.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 3 10:46:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 072EB37B60E for ; Thu, 3 Aug 2000 10:46:19 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA73057; Thu, 3 Aug 2000 19:44:57 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008031744.TAA73057@freebsd.dk> Subject: Re: ATA66 support In-Reply-To: <20000803191538.A8387@titan.klemm.gtn.com> from Andreas Klemm at "Aug 3, 2000 07:15:38 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Thu, 3 Aug 2000 19:44:57 +0200 (CEST) Cc: jcm@FreeBSD-uk.eu.org (j mckitrick), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] 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 It seems Andreas Klemm wrote: > > I bought a separate ATA PCI controller which is capable of ATA 66. > But using an ATA-66 capable cable causes the system to hang during > boot. Strange.. > atapci0: at device 7.1 on pci0 > atapci0: Busmastering DMA not enabled Funny, what have you done to disable Busmastering ? > atapci1: port 0xac00-0xacff,0xa800-0xa803,0xa400-0xa407 irq 15 at device 14.0 on pci0 > ata2: at 0xa400 on atapci1 > atapci2: port 0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 irq 15 at device 14.1 on pci0 That looks OK... > > The motherboard has to be severely broken if a PCI controller wont work... > > What HW are we talking about here ? > > Tyan Titan Pro, SMP board, 2 x 200 PPro Got one of those too, works like a charm with both Promise and HPT366 controllers and IBM's... > ad4: 39082MB [79406/16/63] at ata2-master using UDMA33 AHA! try swap that with a known good drive (ie non Maxtor/WD) if you can.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 3 11:23:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 04F7A37B6B4 for ; Thu, 3 Aug 2000 11:23:12 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id UAA23141; Thu, 3 Aug 2000 20:15:23 +0200 (MET DST) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id UAA11157; Thu, 3 Aug 2000 20:15:26 +0200 (CEST) (envelope-from andreas) Date: Thu, 3 Aug 2000 20:15:26 +0200 From: Andreas Klemm To: Soren Schmidt Cc: j mckitrick , freebsd-current@FreeBSD.ORG Subject: Re: ATA66 support Message-ID: <20000803201525.A11114@titan.klemm.gtn.com> References: <20000803191538.A8387@titan.klemm.gtn.com> <200008031744.TAA73057@freebsd.dk> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200008031744.TAA73057@freebsd.dk>; from sos@freebsd.dk on Thu, Aug 03, 2000 at 07:44:57PM +0200 X-Operating-System: FreeBSD 4.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 03, 2000 at 07:44:57PM +0200, Soren Schmidt wrote: > > ad4: 39082MB [79406/16/63] at ata2-master using UDMA33 > > AHA! try swap that with a known good drive (ie non Maxtor/WD) if you can.... Too bad... have to live with that now ;-) -- Andreas Klemm Songs from our band........................http://people.freebsd.org/~andreas/ Powered by FreeBSD SMP...............http://www.freebsd.org/~fsmp/SMP/SMP.html Please note: Apsfilter got a NEW HOME................http://www.apsfilter.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 3 13:33:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail01.index-tv.com (mail01.index-tv.com [210.166.77.190]) by hub.freebsd.org (Postfix) with ESMTP id BFC1437B5B0 for ; Thu, 3 Aug 2000 13:32:51 -0700 (PDT) (envelope-from news@index-tv.com) Received: (from root@localhost) by mail01.index-tv.com (8.11.0+3.3W/3.7W00080402) id e73JtV100722 for l00080411; Fri, 4 Aug 2000 04:55:31 +0900 (JST) Date: Fri, 4 Aug 2000 04:55:31 +0900 (JST) Message-Id: <200008031955.e73JtV100722@mail01.index-tv.com> Subject: =?ISO-2022-JP?B?GyRCGyRCOD02YhsoQg==?= 10 =?ISO-2022-JP?B?GyRAGyRCS3wxXyEqJVclbCU5JUYjMiEqOWsyWj5eSUokLEV2JD8bKEI=?= =?ISO-2022-JP?B?GyRAGyRCJGshKhsoQg==?= From: news@index-tv.com To: news@index-tv.com MIME-Version: 1.0 (generated by MimeKit/1.8) Content-Type: text/plain; charset=ISO-2022-JP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $B8=6b(B10$BK|1_!*%W%l%9%F#2!*9k2Z>^IJ$,Ev$?$k!*(B $B!y8=6b(B10$BK|1_!*%W%l%9%F#2!*9k2Z>^IJ$,Ev$?$k!*!y(B $B!!!!!!!A!!(BIndex-TV$B;kD0R2p$$$?$@$$$?J}$K=P$5$;$F$$$?$@$$$F$*$j$^(B $B$9!#F|:"$O!"#I#n#d#e#x!]#T#V$r$4MxMQ$$$?$@$/$H$H$b$K!"(B $B5.=E$J$40U8+$r$$$?$@$-!"$"$j$,$H$&$4$6$$$^$9!#(B $B$3$N$?$S!"(BIndex-TV$B;kD0R2p$$$?$@(B $B$$$?3'MM$rBP>]$H$7$F!"$5$5$d$+$G$9$,!"^(B $B%-%c%s%Z!<%s$r^IJ![(B $B#1Ey!!#1#0K|1_!!!_!!(B1$BL>MM(B $B#2Ey!!%=%K!<%W%l%9%F#2!!!_!!(B1$BL>MM(B $B#3Ey!!#3K|1_!!!_!!(B1$BL>MM(B $B#4Ey!!#1K|1_!!!_!!(B5$BL>MM(B $B#5Ey!!$*Bf>l$N4QMwMM(B $B!!!!!!%M%*%8%*%Q%9%]!<%H0z497t!!!_!!(B5$BAH(B10$BL>MM(B $B!!!!!!%J%`%3%J%s%8%c%?%&%s(B $B!!!!!!!!!!!!!!!!(BVIP$B%Q%9%]!<%H0z497t(B X 5$BAH(B10$BL>MM(B $B!!!!!!%J%`%3%o%s%@!<%(%C%0(B $B!!!!!!!!!!!!!!!!(BVIP$B%Q%9%]!<%H0z497t(B X 5$BAH(B10$BL>MM(B $B!Z1~JgJ}K!![(B $B!{!!%&%'%V$K$F$*?=9~$N>l9g$O$3$A$i(B $B!!!!"*(Bhttp://www.index-tv.com/japan/15cam_dm.html $B!{!!(BFAX$B$K$F$*?=9~$N!"$^$?$O%a!<%k$K$F$*?=9~$_$N>l9g$O(B $B!!!!0J2<$N9`L\$r0u:~$^$?$O%3%T!<$7$?>e$G$41~Jg$/$@$5$$!#(B $B!!!!$^$?!"$=$N:]$K4JC1$J%"%s%1!<%H$K$46(NO$/$@$5$$!#(B $B!!!!!&!!%a!<%k"*(Binfo@index-tv.com$B!J7oL>!'!V(B15$BK|?MFMGK5-G0!W!K(B $B!!!!!&!!%U%!%C%/%9"*(B03-5352-5665 ----------$B%"%s%1!<%HFbMF!J%3%3$+$i!K(B----------- $B!!(BIndex-TV$B;kD0A0!'(B $B!!!!#2!K$U$j$,$J!'(B $B!!!!#3!K(BE-Mail$B!'(B $B!!!!#4!KG/Np!'(B $B!!!!#5!K$*=;$^$$!JETF;I\8)!K!'(B $B!!!!#6!K@-JL!'(B $B!!!!#7!K?&6H!'(B $B!!!!#8!K(BIndex-TV$B$r$4B8CN$N>l9g$I$3$G$*CN$j$K$J$C$?$+(B $B!!!!!!!!$*=q$-$/$@$5$$!'(B ----------------$B!J%3%3$^$G!K(B---------------- Index$B!](BTV$B$r$4B8CN$G$9$+!)!'(B Index-TV$B$O%Q%=%3%s$N2hLL>e$K8=$l$k>.$5$J%F%l%S$G$9!#(B $B$$$^%$%s%?!<%M%C%H$K$O$?$/$5$s$N>pJs$,$"$U$l$F$$$F!"(B $B$I$l$K$7$h$&$+!"$I$3$K9T$3$&$+LB$C$?7P83$"$j$^$;$s$+!)(B Index-TV$B$O!"LLGr$$>pJs!"I,MW$J>pJs$@$1$r!"#2#4;~4V!"(B $B#3#6#5F|!"$_$J$5$s$N%G%9%/%H%C%W$KG[?.$7$F$/$l$kJXMx$J(B $BF;6q$G$9!#(B $B"($3$A$i$N%a!<%k$OG[?.$r$44uK>$5$l$?J}$X$*FO$1$7$F$*$j$^$9!#(B $B!!K|$,0l$44uK>$5$l$J$$J}$XFO$$$F$7$^$C$?>l9g$O$4N;>5$/$@$5$$!#(B $B"(%a!<%kG[?.:o=|$r$44uK>$5$l$kJ}$O$3$A$i(B $B!!(Binfo@index-tv.com $B"((BIndex-TV$B%S%e!<%o!JL5=~!K$O$3$A$i(B $B!!"*(Bhttp://www.index-tv.com/japan/jget.html $B"($*Ld$$9g$o$;$O$3$A$i(B $B!!3t<02q To: Dag-Erling Smorgrav Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: Loss of fetch(1) functionality with libfetch 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 3 Aug 2000, Dag-Erling Smorgrav wrote: > Peter Jeremy writes: > > Whilst the environment is somewhat safer than the command line, I'd > > still prefer not to have passwords embedded in environment variables. > > Since ps(1) no longer allows users to view other users' processes' > environment, I don't think it's a very big issue anymore. This behavious is configurable - we shouldn't start relying on it at the application level. 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 Thu Aug 3 18:18:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 4BED537B589; Thu, 3 Aug 2000 18:18:56 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id VAA26142; Thu, 3 Aug 2000 21:18:54 -0400 (EDT) Message-ID: <20000803211854.A23133@netmonger.net> Date: Thu, 3 Aug 2000 21:18:54 -0400 From: Christopher Masto To: Garance A Drosihn , Mark Ovens , current@FreeBSD.ORG Cc: wollman@FreeBSD.ORG, papowell@astart.com Subject: Re: Request for review (LPDEST vs PRINTER) References: <20000802223930.C236@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Garance A Drosihn on Wed, Aug 02, 2000 at 09:35:23PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 02, 2000 at 09:35:23PM -0400, Garance A Drosihn wrote: > The other printing-system alternative is LPRng (which people > can install from ports). LPRng does add the 'lpstat' command, > in addition to replacing lpr/lpq/lprm. And if I am reading > this code right, it does check LPDEST for all of those commands, > *-but-* it has PRINTER taking precedence over LPDEST, and not > the way POSIX (apparently) describes it. From testing, it appears that you are reading the code correctly. The documentation for LPRng, however, indicates for the SysV commands that LPDEST takes precedence. It's probably just an oversight. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- 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 Aug 4 0: 1:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 1A3DD37B883; Fri, 4 Aug 2000 00:01:29 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id JAA40154; Fri, 4 Aug 2000 09:01:27 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: Kris Kennaway Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: Loss of fetch(1) functionality with libfetch References: From: Dag-Erling Smorgrav Date: 04 Aug 2000 09:01:26 +0200 In-Reply-To: Kris Kennaway's message of "Thu, 3 Aug 2000 15:47:15 -0700 (PDT)" Message-ID: Lines: 19 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway writes: > On 3 Aug 2000, Dag-Erling Smorgrav wrote: > > Since ps(1) no longer allows users to view other users' processes' > > environment, I don't think it's a very big issue anymore. > This behavious is configurable - we shouldn't start relying on it at the > application level. I'm not relying on it - fetch(1) has always had the ability to specify passwords in environment variables. I'm just saying it's less of a problem than it was before. On a related note, I just suddenly remembered about .netrc. Libfetch ought to be able to read FTP logins and passwords from the user's .netrc. I also wonder if it might be meaningful to use .netrc for HTTP servers as well... DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 4 0: 7:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D82D137B890; Fri, 4 Aug 2000 00:07:36 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id JAA02144; Fri, 4 Aug 2000 09:07:31 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Dag-Erling Smorgrav Cc: Kris Kennaway , Peter Jeremy , current@FreeBSD.ORG Subject: Re: Loss of fetch(1) functionality with libfetch In-reply-to: Your message of "04 Aug 2000 09:01:26 +0200." Date: Fri, 04 Aug 2000 09:07:31 +0200 Message-ID: <2142.965372851@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dag-Erling Smorgrav writes: >Kris Kennaway writes: >> On 3 Aug 2000, Dag-Erling Smorgrav wrote: >> > Since ps(1) no longer allows users to view other users' processes' >> > environment, I don't think it's a very big issue anymore. >> This behavious is configurable - we shouldn't start relying on it at the >> application level. > >I'm not relying on it - fetch(1) has always had the ability to specify >passwords in environment variables. I'm just saying it's less of a >problem than it was before. > >On a related note, I just suddenly remembered about .netrc. Libfetch >ought to be able to read FTP logins and passwords from the user's >.netrc. I also wonder if it might be meaningful to use .netrc for HTTP >servers as well... What happened to the FTP_PASSIVE_MODE environment variable ? As far as I can tell it is no longer supported and as a result sysinstall is broken. It uses Active FTP even if you select Passive FTP on the menu :-( -- 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 Aug 4 0:26:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8FBB137B8C5; Fri, 4 Aug 2000 00:26:25 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id JAA40272; Fri, 4 Aug 2000 09:24:49 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: Poul-Henning Kamp Cc: Kris Kennaway , Peter Jeremy , current@FreeBSD.ORG Subject: Re: Loss of fetch(1) functionality with libfetch References: <2142.965372851@critter.freebsd.dk> From: Dag-Erling Smorgrav Date: 04 Aug 2000 09:24:48 +0200 In-Reply-To: Poul-Henning Kamp's message of "Fri, 04 Aug 2000 09:07:31 +0200" Message-ID: Lines: 11 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > What happened to the FTP_PASSIVE_MODE environment variable ? As > far as I can tell it is no longer supported and as a result sysinstall > is broken. It uses Active FTP even if you select Passive FTP on > the menu :-( Sysinstall does not use libfetch. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 4 6:22:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.houston.rr.com (sm2.texas.rr.com [24.93.35.55]) by hub.freebsd.org (Postfix) with ESMTP id 934F337BAF8 for ; Fri, 4 Aug 2000 06:22:53 -0700 (PDT) (envelope-from shocking@houston.rr.com) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Fri, 4 Aug 2000 08:21:31 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.9.3/8.9.3) with ESMTP id IAA05647 for ; Fri, 4 Aug 2000 08:18:39 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.9.3/8.9.3) with ESMTP id IAA60387 for ; Fri, 4 Aug 2000 08:18:36 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200008041318.IAA60387@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: When Good DIMMS go Bad (or how I fixed my sig11) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Aug 2000 08:18:36 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG About a week ago, I complained of mysterious Sig 11s during a make world. After some experimentation, a PC100 DIMM was found to be better suited for a 66MHz memory bus in another machine, who obligingly donated a DIMM in return that actually works with a 100MHz bus. I think the trip from Australia and this Texas heat finally pushed the dodgy one over the edge. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 4 7: 2:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (hermes.dialup.ru [194.87.16.230]) by hub.freebsd.org (Postfix) with ESMTP id 8CA7937BB40 for ; Fri, 4 Aug 2000 07:02:37 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id SAA00306 for current@freebsd.org; Fri, 4 Aug 2000 18:02:42 +0400 (MSD) (envelope-from ache) Date: Fri, 4 Aug 2000 18:02:41 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: strange mouse cursor bug (syscons?) Message-ID: <20000804180241.A285@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 When mouse cursor moved somewhere near blinking cursor in about two lines, and all this happens at the bottom of the screen, mouse cursor starts to blink with very hight rate. It stops when it moved outside. Looks like some high intensity loop occupes processor so it can't update cursor with needed rate. -- 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 Aug 4 10:16:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail3.aracnet.com (mail3.aracnet.com [216.99.193.38]) by hub.freebsd.org (Postfix) with ESMTP id 6547137BA20 for ; Fri, 4 Aug 2000 10:16:39 -0700 (PDT) (envelope-from sf@aracnet.com) Received: from mephistopheles. (max1-197-2.cust.aracnet.com [216.99.197.2]) by mail3.aracnet.com (8.9.3/8.9.3) with ESMTP id KAA20560 for ; Fri, 4 Aug 2000 10:16:41 -0700 Date: Fri, 4 Aug 2000 10:16:32 -0700 (PDT) From: Scott Flatman X-Sender: sf@mephistopheles. To: current@freebsd.org Subject: make world breakage 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 Fresh bits supped this morning: In file included from /u1/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/mdebugread.c:2774: /u1/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/partial-stab.h:268: macro `START_PSYMTAB' used with too many (7) args mkdep: compile failed *** Error code 1 Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 4 10:24:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id E1B6C37BA1C; Fri, 4 Aug 2000 10:24:48 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.9.3/1.13) id UAA05625; Fri, 4 Aug 2000 20:24:30 +0300 (EEST) Date: Fri, 4 Aug 2000 20:24:30 +0300 From: Ruslan Ermilov To: Scott Flatman Cc: current@freebsd.org, "David O'Brien" Subject: Re: make world breakage Message-ID: <20000804202430.B4824@sunbay.com> Mail-Followup-To: Scott Flatman , current@freebsd.org, David O'Brien References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from sf@aracnet.com on Fri, Aug 04, 2000 at 10:16:32AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 04, 2000 at 10:16:32AM -0700, Scott Flatman wrote: > Fresh bits supped this morning: > > In file included from > /u1/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/mdebugread.c:2774: > /u1/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/partial-stab.h:268: macro > `START_PSYMTAB' used with too many (7) args > mkdep: compile failed > *** Error code 1 > 99 conflicts from the today's gdb import were not resolved yet... -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 4 11:35:56 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 F219937BB42 for ; Fri, 4 Aug 2000 11:35:48 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA23986; Fri, 4 Aug 2000 11:35:42 -0700 (PDT) (envelope-from obrien) Date: Fri, 4 Aug 2000 11:35:41 -0700 From: "David O'Brien" To: Scott Flatman , current@freebsd.org Subject: Re: make world breakage Message-ID: <20000804113541.A23943@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000804202430.B4824@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000804202430.B4824@sunbay.com>; from ru@sunbay.com on Fri, Aug 04, 2000 at 08:24:30PM +0300 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 04, 2000 at 08:24:30PM +0300, Ruslan Ermilov wrote: > On Fri, Aug 04, 2000 at 10:16:32AM -0700, Scott Flatman wrote: > > In file included from > > /u1/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/mdebugread.c:2774: > > mkdep: compile failed > > *** Error code 1 > 99 conflicts from the today's gdb import were not resolved yet... Grrrrr gnu/usr.bin/binutils/gdb/Makefile was still grabbing sources from contrib/gdb rather than contrib/gdb.291. I goofed when I switched over to that source by only getting gdb{replay,server} pointed to it. I've committed an untested fix to gnu/usr.bin/binutils/gdb/Makefile to hopefully get people going again. I've started a buildworld to make sure. Quite sorry, my contrib/gdb/ activities were suppose to be sheilded from users. -- -- 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 Fri Aug 4 11:38:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A819337B992; Fri, 4 Aug 2000 11:38:20 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA04482; Fri, 4 Aug 2000 20:38:17 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: obrien@FreeBSD.ORG Cc: Scott Flatman , current@FreeBSD.ORG Subject: Re: make world breakage In-reply-to: Your message of "Fri, 04 Aug 2000 11:35:41 PDT." <20000804113541.A23943@dragon.nuxi.com> Date: Fri, 04 Aug 2000 20:38:17 +0200 Message-ID: <4480.965414297@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000804113541.A23943@dragon.nuxi.com>, "David O'Brien" writes: >Quite sorry, my contrib/gdb/ activities were suppose to be sheilded from >users. And vice-versa I pressume :-) -- 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 Aug 4 11:45: 1 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 86E7637BE0E for ; Fri, 4 Aug 2000 11:44:51 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA24056; Fri, 4 Aug 2000 11:42:10 -0700 (PDT) (envelope-from obrien) Date: Fri, 4 Aug 2000 11:42:10 -0700 From: "David O'Brien" To: Poul-Henning Kamp Cc: Scott Flatman , current@FreeBSD.ORG Subject: Re: make world breakage Message-ID: <20000804114210.A23995@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000804113541.A23943@dragon.nuxi.com> <4480.965414297@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4480.965414297@critter.freebsd.dk>; from phk@critter.freebsd.dk on Fri, Aug 04, 2000 at 08:38:17PM +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 Fri, Aug 04, 2000 at 08:38:17PM +0200, Poul-Henning Kamp wrote: > In message <20000804113541.A23943@dragon.nuxi.com>, "David O'Brien" writes: > >Quite sorry, my contrib/gdb/ activities were suppose to be shielded from > >users. > And vice-versa I presume :-) Grrrr. I should go back to bed -- that's what I meant in the first place. -- -- 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 Fri Aug 4 11:50:32 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 3D38537BBA4 for ; Fri, 4 Aug 2000 11:50:28 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA24100; Fri, 4 Aug 2000 11:50:18 -0700 (PDT) (envelope-from obrien) Date: Fri, 4 Aug 2000 11:50:18 -0700 From: "David O'Brien" To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: Loss of fetch(1) functionality with libfetch Message-ID: <20000804115018.B23995@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <00Aug3.142942est.115260@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from des@flood.ping.uio.no on Thu, Aug 03, 2000 at 01:26:01PM +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 Thu, Aug 03, 2000 at 01:26:01PM +0200, Dag-Erling Smorgrav wrote: > Peter Jeremy writes: > > Whilst the environment is somewhat safer than the command line, I'd > > still prefer not to have passwords embedded in environment variables. > > Since ps(1) no longer allows users to view other users' processes' > environment, I don't think it's a very big issue anymore. POLA says you should not have changed what fetch(1) expects from the environmental var. > > Has this feature been deliberately left out, or is it just one of the > > bits that you haven't gotten around to implementing yet? Would you > > be interested in patches to implement it? > > Sure. The only clean way of doing this (that I can think of) would be > to add an interface to libfetch for registering password-prompting > callbacks. Then it should have been added -- especially before being MFC'ed. -- -- David (obrien@FreeBSD.org) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 4 12:32:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id C3C3F37BAEB for ; Fri, 4 Aug 2000 12:32:22 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id OAA13070; Fri, 4 Aug 2000 14:32:17 -0500 (CDT) Date: Fri, 4 Aug 2000 14:32:17 -0500 From: Alan Cox To: Andreas Klemm Cc: current@freebsd.org Subject: Re: ATA66 support Message-ID: <20000804143217.K6184@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5us Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try a Promise ATA/66 controller. I have no problems with either ad0: 29311MB [59554/16/63] at ata0-master using UDMA66 or ad3: 29188MB [59303/16/63] at ata3-master using UDMA66 on a very heavy disk load using either a Promise ATA/66 or the Intel 810(E)'s ATA/66 controller. As of three or four months ago, the same Maxtor and the previous generation Seagate Barracuda ATA locked up on a Highpoint controller. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 4 13:33: 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 861DF37BB76; Fri, 4 Aug 2000 13:33:01 -0700 (PDT) (envelope-from imp@harmony.village.org) 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 OAA75222; Fri, 4 Aug 2000 14:32: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 OAA12701; Fri, 4 Aug 2000 14:32:50 -0600 (MDT) Message-Id: <200008042032.OAA12701@harmony.village.org> To: Poul-Henning Kamp Subject: Re: Loss of fetch(1) functionality with libfetch Cc: Dag-Erling Smorgrav , Kris Kennaway , Peter Jeremy , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 04 Aug 2000 09:07:31 +0200." <2142.965372851@critter.freebsd.dk> References: <2142.965372851@critter.freebsd.dk> Date: Fri, 04 Aug 2000 14:32:50 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <2142.965372851@critter.freebsd.dk> Poul-Henning Kamp writes: : What happened to the FTP_PASSIVE_MODE environment variable ? As : far as I can tell it is no longer supported and as a result sysinstall : is broken. It uses Active FTP even if you select Passive FTP on : the menu :-( I've also noticed that my formerly working ftp no longer works using ftp. Maybe this is a different problem, or unrelated to libfetch. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 4 13:47:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mike.dhis.org (hiper1-d54.stk.cwnet.com [209.142.56.54]) by hub.freebsd.org (Postfix) with ESMTP id 6835B37B65F for ; Fri, 4 Aug 2000 13:47:44 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (ogre.lan [192.168.100.1]) by mike.dhis.org (Postfix) with ESMTP id AC15BD7; Fri, 4 Aug 2000 13:47:42 -0700 (PDT) Message-ID: <398B2BEE.CA9BD5CD@es.co.nz> Date: Fri, 04 Aug 2000 13:47:42 -0700 From: Mike Muir Reply-To: mmuir@es.co.nz X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Stephen Hocking Cc: current@FreeBSD.ORG Subject: Re: When Good DIMMS go Bad (or how I fixed my sig11) References: <200008041318.IAA60387@bloop.craftncomp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Hocking wrote: > > About a week ago, I complained of mysterious Sig 11s during a make world. > After some experimentation, a PC100 DIMM was found to be better suited for a > 66MHz memory bus in another machine, who obligingly donated a DIMM in return > that actually works with a 100MHz bus. I think the trip from Australia and > this Texas heat finally pushed the dodgy one over the edge. Have you tried any memory testing routines such as memtest86 ? Its the only you write to a floppy and it runs before any bootstrap kicks in -- independant of the OS -- and takes around 18 hours for a single pass. It appears to be quite a comprehensive torture test. If so, how did that dodgy DIMM perform? (The reason I ask is that I'm interested in knowing if these tests can reveal the problems that building world did in your situation.) -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 4 15: 3:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 90C7937BA64; Fri, 4 Aug 2000 15:03:30 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA54409; Fri, 4 Aug 2000 16:00:44 -0600 (MDT) (envelope-from ken) Date: Fri, 4 Aug 2000 16:00:44 -0600 From: "Kenneth D. Merry" To: net@FreeBSD.ORG Subject: new zero copy sockets and NFS snapshot Message-ID: <20000804160044.A54375@panzer.kdm.org> 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 [ -arch and -current BCC'ed for wider coverage, please direct followups to -net and/or me ] I have put a new copy of the zero copy sockets and NFS patches, against -current as of early August 3rd, 2000, here: http://people.FreeBSD.ORG/~ken/zero_copy/ Feedback would be very welcome, we haven't gotten much response on this yet. Besides being generated against a newer version of -current, the following things have changed in the new patches posted above: - Support has been merged in from -current for Alteon and Netgear 1000baseT boards. Initial tests with Alteon boards indicate that their performance is identical to the 1000baseSX model. - The zero copy send support code has been renamed and moved to a new file, src/sys/kern/uipc_cow.c. - Drew Gallatin has made some performance enhancements in the ti(4) driver that decrease receive-side CPU utilization and increase performance somewhat. (CPU utilization changes are hard to quantify, but are probably in the 10-20% range. TCP performance on my test Pentium II 350's increased from about 746Mbps to about 763Mbps, as measured by netperf.) - Drew Gallatin submitted a fix to the IP fragmenting code to make sure that outgoing fragments are 8-byte aligned. - Incorporated Bill Paul's fixes to Alteon's 12.4.11 firmware that hopefully include most of the true bugfixes to their 12.4.13 firmware. Alteon's 12.4.13 firmware, when used with 1000BaseT boards, doesn't seem to autonegotiate anything other than 1000BaseT, and also doesn't like to be forced to a speed other than 1000Mbps. Alteon hasn't yet responded to queries about the problems with version 12.4.13 of their firmware, so we're using version 12.4.11 with some selected fixes from 12.4.13. This seems to properly negotiate at all supported speeds and duplex settings with 1000baseT boards. - Header splitting is now restricted to Tigon 2 boards only. We only have source for firmware for the Tigon 2, thus the reason header splitting is only supported for those chips. - Drew Gallatin's NFS read header splitting code is now included in the firmware. This can dramatically improve NFS read performance. - There is a new references section in the FAQ that includes pointers to some relevant papers and proposals. For those of you who missed the previous messages about this code (that went out to -net, -arch and -current), here's a quick list of what is included in the code: - Two sets of zero copy send code, written by Drew Gallatin and Robert Picco . - Zero copy receive code, written by Drew Gallatin. - Zero copy NFS code, written by Drew Gallatin. - Header splitting firmware for Alteon's Tigon II boards (written by me), based on version 12.4.11 of their firmware. This is used in combination with the zero copy receive code to guarantee that the payload of TCP or UDP packet is placed into a page-aligned buffer. - Alteon firmware debugging ioctls and supporting routines for the Tigon driver (also written by me). This will help anyone who is doing firmware development under FreeBSD for the Tigon boards. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 4 19:26:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from host01.netpro.ne.jp (host01.netpro.ne.jp [210.233.96.2]) by hub.freebsd.org (Postfix) with ESMTP id 4524D37B8A2; Fri, 4 Aug 2000 19:26:30 -0700 (PDT) (envelope-from binfo@netpro.ne.jp) Received: from oemcomputer (tk-ns01-216.tk.netpro.ne.jp [210.250.49.216]) by host01.netpro.ne.jp (8.9.3/3.7W) with SMTP id KAA27402; Sat, 5 Aug 2000 10:43:08 +0900 (JST) Message-ID: <016b01bffe7f$bddad480$bd31fad2@oemcomputer> From: =?iso-2022-jp?B?GyRCJVYlQyUvJUolJCVEISYlVyVtJTglJyUvJUgbKEI=?= To: Subject: =?iso-2022-jp?B?GyRCPXFJPjJISmc9OCEqSXs2SDI9JGIyREc9GyhC?= Date: Sat, 5 Aug 2000 09:48:42 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0147_01BFFEC2.585F14C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0147_01BFFEC2.585F14C0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit $B$4<+J,$N$*A&$aK\$r9-$/%"%T!<%k$7$?$$$H$*9M$($N(B $B!VK\$NCn!W!VFI=q$NC#?M!W$rJg=8$7$^$9!#(B $Be$NFI=qNL$r;}$DJ}!#G/Np@-JLITLd(B $B>\:Y$*Ld$$9g$o$;$O%a!<%kBj!V(Binq$B!W$H$7(B booksf@netlimit.com$B$"$F2<5-%"%s%1!<%H$r$*Aw$j$/$@$5$$(B ($BJV?.%\%?%s$O;H$o$J$$$G$/$@$5$$!K(B $B!c(Ba$B!!9%$-$J%8%c%s%k!!J#?t2D!d(B 1$B%_%9%F%j!!(B2$B#S#F!!(B3$B%[%i!.@b!!(B7$B$=$NB>8=Be>.@b(B 8$B41G=>.@b!!(B9$B%N%s%U%#%/%7%g%s(B $B!c(Bb$B!!K~G/Np!d(B $B!c(Bc$B!!@-JL!d!!(B1$B=w@-!!(B2$BCK@-(B $B!c(Bd$B!!=;=j!d!!M9JXHV9f>e#37e$G(B $B!c(Be$B!!%a!<%k%"%I%l%9!d(B $B5-F~$OH>3Q1Q?t;z$G$*4j$$$7$^$9(B $B!JNc!K(Ba 1 2 b 40 c 1 d 514 e aaa@bb.co.jp ------=_NextPart_000_0147_01BFFEC2.585F14C0 Content-Type: text/html; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable
=1B$B$4<+J,$N$*A&$aK\$r9-$/%"%T!<%k$7$?$$$H$*9M$($N=1B(B
=1B$= B!VK\$NCn!W!VFI=3Dq$NC#?M!W$rJg=3D8$7$^$9!#=1B(B
=1B$B=1B$B%A%c%s%9$bMQ0U$5$l$^$9=1B(B
 
=1B$B!c;q3J!d=1B(B
=1B$BF|K\8l$rJl8l$H$7!"%(%s%?!<%F%$%a%s%H$= rCf?4$K=1B(B
=1B$B7n#7!$#8:}A08e0J>e$NFI=3DqNL$r;}$DJ}!#G/Np@-JLITLd=1B= (B
 
=1B$B>\:Y$*Ld$$9g$o$;$O%a!<%kBj!V=1B(Binq=1B$B!W$H$7=1B(B
booksf@netlimit.com=1B$B$"$F2<5-%= "%s%1!<%H$r$*Aw$j$/$@$5$$=1B(B
(=1B$BJV?.%\%?%s$O;H$o$J$$$G$/$@$5$$!K=1B(B
 
=1B$B!c=1B(Ba=1B$B!!9%$-$J%8%c%s%k!!J#?t2D!d=1B(B
1=1B$B%_%9%= F%j!!=1B(B2=1B$B#S#F!!=1B(B3=1B$B%[%i!= 5=1B$BNx0&!?%m%^%s%9!!=1B(B6=1B$B;~Be=1B(B/=1B$BNr;K>.@b!!=1B(B7=1B$B$=3D= $NB>8=3DBe>.@b=1B(B
8=1B$B41G=3D>.@b!!=1B(B9=1B$B%N%s%U%#%/%7%g%s=1B(B=
=1B$B!c=1B(Bb=1B$B!!K~G/Np!d=1B(B
=1B$B!c=1B(Bc=1B$B!!@-JL!d!!=1B(= B1=1B$B=3Dw@-!!=1B(B2=1B$BCK@-=1B(B
=1B$B!c=1B(Bd=1B$B!!=3D;=3Dj!d!!M9= JXHV9f>e#37e$G=1B(B
=1B$B!c=1B(Be=1B$B!!%a!<%k%"%I%l%9!d=1B(B
 
=1B$B5-F~$OH>3Q1Q?t;z$G$*4j$$$7$^$9=1B(B
=1B$B!JNc!K=1B(Ba 1 = 2 b 40 c 1 d 514 e aaa@bb.co.jp
------=_NextPart_000_0147_01BFFEC2.585F14C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 5 6:38:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ruhr.de (in-ruhr2.ruhr.de [141.39.224.60]) by hub.freebsd.org (Postfix) with SMTP id 66CD437B607 for ; Sat, 5 Aug 2000 06:38:23 -0700 (PDT) (envelope-from ue@nathan.ruhr.de) Received: (qmail 17912 invoked by alias); 5 Aug 2000 13:39:36 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.9.3/8.9.3) id PAA18580; Sat, 5 Aug 2000 15:38:56 +0200 (CEST) (envelope-from ue) Date: Sat, 5 Aug 2000 15:38:56 +0200 From: Udo Erdelhoff To: Kris Kennaway Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, freebsd-current@freebsd.org Subject: Re: cvs commit: src/sbin/ccdconfig ccdconfig.c Message-ID: <20000805153856.A72960@nathan.ruhr.de> Reply-To: freebsd-current@freebsd.org References: <200008050606.XAA79437@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200008050606.XAA79437@freefall.freebsd.org>; from kris@FreeBSD.ORG on Fri, Aug 04, 2000 at 11:06:49PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1.17 +5 -5 src/sbin/ccdconfig/ccdconfig.c Broke world: ===> sbin/ccdconfig rm -f .depend mkdep -f .depend -a -I/usr/src/sbin/ccdconfig/../../sys -I/usr/obj/usr/src/i3 86/usr/include /usr/src/sbin/ccdconfig/ccdconfig.c /usr/src/sbin/ccdconfig/ccdconfig.c:725: unterminated string or character consta nt /usr/src/sbin/ccdconfig/ccdconfig.c:635: possible real start of unterminated con stant mkdep: compile failed Fix: Index: ccdconfig.c =================================================================== RCS file: /home/ncvs/src/sbin/ccdconfig/ccdconfig.c,v retrieving revision 1.17 diff -r1.17 ccdconfig.c 635c635 < warnx("%s', kvm_geterr(kd)); --- > warnx("%s", kvm_geterr(kd)); /s/Udo -- "What part of no don't you understand?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 5 7:43:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from milquetoast.cs.mcgill.ca (milquetoast.CS.McGill.CA [132.206.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 9FAD537B610 for ; Sat, 5 Aug 2000 07:43:51 -0700 (PDT) (envelope-from mat@milquetoast.cs.mcgill.ca) Received: (from mat@localhost) by milquetoast.cs.mcgill.ca (8.9.3/8.9.3) id KAA27360 for freebsd-current@FreeBSD.ORG; Sat, 5 Aug 2000 10:43:50 -0400 (EDT) Date: Sat, 5 Aug 2000 10:43:50 -0400 From: Mathew KANNER To: freebsd-current@FreeBSD.ORG Subject: Re: ntpdate bug(?) Message-ID: <20000805104350.B27218@cs.mcgill.ca> References: <20000803102512.B15819@cs.mcgill.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: Mathew KANNER's message [ntpdate bug(?)] as of Thu, Aug 03, 2000 at 10:25:12AM -0400 Organization: SOCS, McGill University, Montreal, CANADA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Following up] I'm embarassed to say that I missed the following sentence in the ntpdate man page. -b [...]This option should be used when called from the a startup file at boot time. This should have rung a bell for me. Thanks to the guy who responded. --Mat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 5 8:47:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from smople.thehub.com.au (smople.thehub.com.au [203.143.240.10]) by hub.freebsd.org (Postfix) with ESMTP id E82BA37B9C8 for ; Sat, 5 Aug 2000 08:47:27 -0700 (PDT) (envelope-from mckay@thehub.com.au) Received: from dungeon.home (ppp124.dyn248.pacific.net.au [203.143.248.124]) by smople.thehub.com.au (8.9.3/8.9.1) with ESMTP id BAA52429; Sun, 6 Aug 2000 01:46:55 +1000 (EST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.9.3/8.9.3) with ESMTP id BAA10791; Sun, 6 Aug 2000 01:49:49 +1000 (EST) (envelope-from mckay) Message-Id: <200008051549.BAA10791@dungeon.home> To: freebsd-current@freebsd.org Cc: mckay@thehub.com.au Subject: Ugly, slow shutdown Date: Sun, 06 Aug 2000 01:49:49 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm off in a few days for a couple months of tourism in Europe (no, no need for sympathy!), so I'm dumping these couple ideas on you and running. I think shutdown time has gotten uglier and slower than it needs to be. I want to apply these patches (well, at least the first one) before I escape radar range. Your job is to not object much. :-) Patch 1 replaces: Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped with Stopping bufdaemon Also: syncing disks... 10 10 3 done returns to the traditional syncing disks... 10 10 3 done Patch 2 is smaller and possibly controversial. Normally bufdaemon and syncer are sleeping when they are told to suspend. This delays shutdown by a few boring seconds. With this patch, it is zippier. I expect people to complain about this shortcut, but every sleeping process should expect to be woken for no reason at all. Basic kernel premise. I've been running these patches on a 4.x machine for a while now. No problems except I am now surprised by the slow and ugly shutdown of unpatched machines. :-) I apologise that I've not tested these against -current. That's the bit that I've skipped because I'm out of time. There should be no difference between 4.x and -current in this area though. These patches will apply cleanly against both. Cheers, Stephen. Patch 1: Index: kern_shutdown.c =================================================================== RCS file: /cvs/src/sys/kern/kern_shutdown.c,v retrieving revision 1.76 diff -u -r1.76 kern_shutdown.c --- kern_shutdown.c 2000/07/04 11:25:22 1.76 +++ kern_shutdown.c 2000/07/06 15:02:21 @@ -247,7 +247,6 @@ sync(&proc0, NULL); DELAY(50000 * iter); } - printf("\n"); /* * Count only busy local buffers to prevent forcing * a fsck if we're just a client of a wedged NFS server @@ -261,6 +260,8 @@ bp->b_vp->v_mount, mnt_list); continue; } + if (nbusy == 0) + printf("\n"); nbusy++; #if defined(SHOW_BUSYBUFS) || defined(DIAGNOSTIC) printf( @@ -593,12 +594,11 @@ return; p = (struct proc *)arg; - printf("Waiting (max %d seconds) for system process `%s' to stop...", - kproc_shutdown_wait, p->p_comm); + printf("Stopping %s", p->p_comm); error = suspend_kproc(p, kproc_shutdown_wait * hz); if (error == EWOULDBLOCK) - printf("timed out\n"); + printf(": timed out\n"); else - printf("stopped\n"); + printf("\n"); } Patch 2: Index: kern_kthread.c =================================================================== RCS file: /cvs/src/sys/kern/kern_kthread.c,v retrieving revision 1.5 diff -u -r1.5 kern_kthread.c --- kern_kthread.c 2000/01/10 08:00:58 1.5 +++ kern_kthread.c 2000/08/05 15:32:06 @@ -116,6 +116,12 @@ */ if ((p->p_flag & P_SYSTEM) == 0) return (EINVAL); + /* + * The target process is probably just snoozing. Wake it up so + * that it will notice that it should suspend itself. + */ + if (p->p_wchan != NULL) + wakeup(p->p_wchan); SIGADDSET(p->p_siglist, SIGSTOP); return tsleep((caddr_t)&p->p_siglist, PPAUSE, "suspkp", timo); } TheEnd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 5 16:49:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from Den.BOFH.Halifax.NS.Ca (Den.BOFH.Halifax.ns.Ca [129.173.46.183]) by hub.freebsd.org (Postfix) with ESMTP id 9ED6C37B77C for ; Sat, 5 Aug 2000 16:49:27 -0700 (PDT) (envelope-from hume@Den.BOFH.Halifax.NS.Ca) Received: (from hume@localhost) by Den.BOFH.Halifax.NS.Ca (8.9.3+Sun/8.9.1) id UAA28618 for freebsd-current@freebsd.org; Sat, 5 Aug 2000 20:49:21 -0300 (ADT) From: Brandon Hume Message-Id: <200008052349.UAA28618@Den.BOFH.Halifax.NS.Ca> Subject: Kernel build failing in ip6_input.c To: freebsd-current@freebsd.org Date: Sat, 5 Aug 2000 20:49:21 -0300 (ADT) X-Mailer: ELM [version 2.4ME+ PL42 (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 went about a week without updating my source tree, but yesterday when I went to build a kernel (and day), I get the following: ... cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../netinet6/ip6_input.c ../../netinet6/ip6_input.c: In function `ip6_input': ../../netinet6/ip6_input.c:312: `inetsw' undeclared (first use in this function) ../../netinet6/ip6_input.c:312: (Each undeclared identifier is reported only once ../../netinet6/ip6_input.c:312: for each function it appears in.) ../../netinet6/ip6_input.c:312: `ip_protox' undeclared (first use in this function) *** Error code 1 Stop in /build/src/sys/compile/JASHUGAN. ... I can't find a declaration of ip_protox anywhere in the netinet6/* code, although something called inetsw is declared in netinet/ip_input.c as extern, so perhaps ip6_input.c is missing an extern? (I apologize if I missed an obvious commit message or warning, I've been busy this week and just mass-deleting mailing list email) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 5 21:50:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [216.190.28.252]) by hub.freebsd.org (Postfix) with ESMTP id 5508137BA03 for ; Sat, 5 Aug 2000 21:50:08 -0700 (PDT) (envelope-from attila@hun.org) Received: (from attila@localhost) by hun.org (8.9.3/8.9.3) id EAA44099; Sun, 6 Aug 2000 04:50:06 GMT (envelope-from attila) Date: Sun, 6 Aug 2000 04:50:06 GMT Message-Id: <200008060450.EAA44099@hun.org> From: attila! Content-Type: text/plain; charset=ISO-8859-1 ; format=flowed Content-Transfer-Encoding: 8bit; Content-Disposition: Inline Organization: hun.org, over 40 years beyond the fringe home for unpenitent hackers and anarcho-cryptophreaks Mailer: FreeBSD 5.0-20000609 with XEmacs V21.1.10 (see alt.religion.emacs) Ballistic: N 37.218497 W 113.614979 To: freebsd-current@freebsd.org Subject: re: Kernel build failing in ip6_input.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the same errors appear in ip6_output.c and the declarations probably should have been made in ip6protosw.h for pfil_hook_... #ifdef PFIL_HOOKS /* * Run through list of hooks for input packets. If there are any * filters which require that additional packets in the flow are * not fast-forwarded, they must clear the M_CANFASTFWD flag. * Note that filters must _never_ set this flag, as another filter * in the list may have previously cleared it. */ m0 = m; pfh = pfil_hook_get(PFIL_IN, &inetsw[ip_protox[IPPROTO_IPV6]].pr_pfh); from my CVS update log, it appears the code changed 31 Jul 00: Edit src/sys/netinet6/ip6_input.c Add delta 1.14 2000.07.31.13.11.42 darrenr Edit src/sys/netinet6/ip6_output.c Add delta 1.16 2000.07.31.13.11.42 darrenr Edit src/sys/netinet6/ip6protosw.h Add delta 1.4 2000.08.02.01.02.42 peter or, the declarations could be missing in which was also updated: Edit src/sys/net/pfil.h Add delta 1.4 2000.07.31.23.35.08 ache Add delta 1.5 2000.08.01.00.12.27 ache Add delta 1.6 2000.08.01.00.40.32 ache attila out... on Sat, 5 Aug 2000 20:49:21 -0300 (ADT), Brandon Hume wrote: > I went about a week without updating my source tree, but yesterday when I > went to build a kernel (and day), I get the following: > ... > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../netinet6/ip6_input.c > ../../netinet6/ip6_input.c: In function `ip6_input': > ../../netinet6/ip6_input.c:312: `inetsw' undeclared (first use in this > function) > ../../netinet6/ip6_input.c:312: (Each undeclared identifier is reported only once > ../../netinet6/ip6_input.c:312: for each function it appears in.) > ../../netinet6/ip6_input.c:312: `ip_protox' undeclared (first use in this function) > *** Error code 1 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message