From owner-freebsd-current Sun Jul 23 0:27:48 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 C594237B986; Sun, 23 Jul 2000 00:27:39 -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 JAA87605; Sun, 23 Jul 2000 09:27:29 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007230727.JAA87605@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 "Sat, 22 Jul 2000 15:11:39 MST." Date: Sun, 23 Jul 2000 09:27:27 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 22 Jul 2000, Mark Murray wrote: > > > > So what it if I want/need 257 bits? :-) > > > > Read them. You'll get them. If you want higher quality randomness than > > Yarrow gives, read more than once. Do other stuff; play. Don't get stuck > > in the "I have exhausted the randomness pool" loop; Yarrow does not play > > that game. > > I think you're missing the point. The only way I can get a random number > with more than n bits of entropy out of Yarrow-n is if I sample either > side of a reseed operation, which in general comes down to timing > guesswork and having to make assumptions about the PRNG implementation. I understand that. :-) Your are missing the point that it is not possible to get more than the ${number-of-bits-ofrandomness} from any accumulator or PRNG. You have to draw the line somewhere; The current implementation has it at 256. > If you want to generate a cryptographic key of length n bits then you > really want >n bits of entropy in the random source you're deriving it > from, otherwise your key is actually much weaker than advertised because > it's easier for the attacker to attack the state of the PRNG that derived > it than to attack the key itself. Aha! That is where Yarrow wins. The paper argues it much better than me: Section 4.1, the paragraph that begins "Yarrow takes a different approach...". > > We currently have Yarrow-256(Blowfish); wanna make it Yarrow-1024? I could > > make it so. > > Well, if we did that then how about generating 2048-bit keys? :-) Where do you draw the line? I could make it Yarrow-N, only to have someone insist on $((N+1)) in the very next breath. With what we have, I am staking my career on the "uncrackability" of Blowfish-256. If that holds then Yarrow is safe. (The old one was MD5, with all its weaknesses such as birthday attacks, and blocking added to compensate for folk raping it for internal state; this blocking was compromised by the non-blocking /dev/urandom. The design was too simple. The current design has multiple accumulators, dual pools, and cryptographically overseen reseed mechanism; on top of that, the output is encrypted in its own right, so there is added protection against folk guessing the internal state.). 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 23 0:31:28 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 3C52537B9A6; Sun, 23 Jul 2000 00:31: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 JAA90585; Sun, 23 Jul 2000 09:31:10 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007230731.JAA90585@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 "Sat, 22 Jul 2000 15:19:29 MST." Date: Sun, 23 Jul 2000 09:31:09 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The core of my complaint is that even though our old PRNG did crappy > entropy handling, we used to have such a method, which is now gone. I'd > like to see yarrow hang off /dev/urandom and have /dev/random tap directly > into the entropy pool (perhaps a third pool separate from Yarrow's > fast/slow) so I can generate my large keys safely. By your own admission, the old system was bad; yet you still want ${it}? You'd like to see a programmer with less experience than Schneier come up with a more secure algorithm than him? 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 23 0:33:54 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 E0B0937B9AD; Sun, 23 Jul 2000 00:33:46 -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 JAA92112; Sun, 23 Jul 2000 09:33:35 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007230733.JAA92112@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 "Sat, 22 Jul 2000 15:19:29 MST." Date: Sun, 23 Jul 2000 09:33:34 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The core of my complaint is that even though our old PRNG did crappy > entropy handling, we used to have such a method, which is now gone. I'd > like to see yarrow hang off /dev/urandom and have /dev/random tap directly > into the entropy pool (perhaps a third pool separate from Yarrow's > fast/slow) so I can generate my large keys safely. By your own admission, the old system was bad; yet you still want ${it}? You'd like to see a programmer with less experience than Schneier come up with a more secure algorithm than him? 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 23 0:39:52 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 B17C237B9A6; Sun, 23 Jul 2000 00:39:41 -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 JAA94403; Sun, 23 Jul 2000 09:39:30 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007230739.JAA94403@grimreaper.grondar.za> To: Kris Kennaway Cc: "Jeroen C. van Gelderen" , current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Kris Kennaway "Sat, 22 Jul 2000 17:41:15 MST." Date: Sun, 23 Jul 2000 09:39:30 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Okay, using RSA keys wasn't the best example to pick, but Yarrow also > seems easy to misuse in other cases: for example if you want to generate > multiple 256-bit symmetric keys (or other random data) at the same time, > each additional key after the first won't contain any additional entropy, > so if you break the state of the PRNG at the time the first one was > generated you get the others for free (until the thing reseeds). > > This design tradeoff is discussed in section 4.1 of the paper. Tweakable. > > That said, there is nothing to prevent the system admin > > from tweaking the Yarrow security parameters so that > > Yarrow will only spit out as many bits or pseudo-randomness > > as it gathers bits of entropy.[4] > > Well, I don't see a way to tune this without modifying the Yarrow design, > since the entropy pool is intentionally decoupled from the output > mechanism, and it seems like it would add additional (unnecessary) > overhead anyway to use it in that fashion. Look at the sysctls (some improvements and documentation coming). > Indications are we can probably get quite a lot of usable entropy from a > standard system (on the order of many kilobytes per second - but I need to > read more of the literature about processing of entropy samples) - in this > case I think maintaining a third pool which is directly tapped by > /dev/random, and leaving Yarrow sitting behind /dev/urandom is the way to > go. I suspect you are missing the whole point of yarrow. Yarrow protects you from the compromises inherent in attackers injecting their own junk into the "third pool". 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 23 0:40:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from surfree.net.il (mail.surfree.net.il [212.3.192.12]) by hub.freebsd.org (Postfix) with SMTP id A901337BA19 for ; Sun, 23 Jul 2000 00:40:25 -0700 (PDT) (envelope-from rosti@surfree.net.il) Received: From [surfree.net.il 212.3.218.19] By SuperMail at surfree.net.il with SMTP; Sun, 23 Jul 2000 10:37:39 +0200 GMT Message-ID: <397AAF59.B191E3E9@surfree.net.il> Date: Sun, 23 Jul 2000 10:39:53 +0200 From: rosti@surfree.net.il X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en,ru MIME-Version: 1.0 To: current@FreeBSD.org Subject: Netscape Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Netscape 4.74 is already out but FreeBSD 4.1-RC2 contains 4.73 version yet. Will FreeBSD 4.1-RELEASE contains the last version (4.74) of Netscape Communicator and Navigator? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 0:40:47 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 B8BD837C32B; Sun, 23 Jul 2000 00:40:44 -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 AAA82584; Sun, 23 Jul 2000 00:40:44 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Jul 2000 00:40:44 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007230727.JAA87605@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, 23 Jul 2000, Mark Murray wrote: > Your are missing the point that it is not possible to get more than > the ${number-of-bits-ofrandomness} from any accumulator or PRNG. You > have to draw the line somewhere; The current implementation has it > at 256. Uhh..a PRNG which hashes entropy samples with e.g. SHA1 and outputs the digest once the bucket is "full" will have 1-epsilon bit of entropy per 1 bit of output. It may not be very fast depending on the rate of entropy accumulation, but you can get as much entropy out of it as you want. This is basically the model I am advocating for /dev/random. It's also the alternative "basic design philosophy" described in the yarrow paper. > > If you want to generate a cryptographic key of length n bits then you > > really want >n bits of entropy in the random source you're deriving it > > from, otherwise your key is actually much weaker than advertised because > > it's easier for the attacker to attack the state of the PRNG that derived > > it than to attack the key itself. > > Aha! That is where Yarrow wins. The paper argues it much better than > me: Section 4.1, the paragraph that begins "Yarrow takes a different > approach...". See "important issue" number 2 on p6. Yarrow-derived numbers are only "good for" 256 bits of strength. Modulo reseeds, Yarrow never accumulates more than 256 bits of entropy. Therefore you are silly to use it for applications which require more than 256 bits of randomness. > Where do you draw the line? I could make it Yarrow-N, only to have > someone insist on $((N+1)) in the very next breath. Precisely, which is why /dev/random shouldn't use Yarrow, or any other seeded-cipher PRNG. > With what we have, I am staking my career on the "uncrackability" > of Blowfish-256. If that holds then Yarrow is safe. (The old one I'm not bothered about this. My point is that, by design, Yarrow is not suitable as a replacement for /dev/random (/dev/urandom, yes). 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 23 0:41:51 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 1BF1F37BA2F; Sun, 23 Jul 2000 00:41:48 -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 AAA82698; Sun, 23 Jul 2000 00:41:48 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Jul 2000 00:41:48 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007230731.JAA90585@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, 23 Jul 2000, Mark Murray wrote: > By your own admission, the old system was bad; yet you still want > ${it}? You'd like to see a programmer with less experience than > Schneier come up with a more secure algorithm than him? The old implementation was bad. The class of algorithm is not, as long as you are conservative about your entropy estimates. 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 23 0:49:39 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 39E1037B96F; Sun, 23 Jul 2000 00:49:36 -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 AAA83155; Sun, 23 Jul 2000 00:49:36 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Jul 2000 00:49:35 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: "Jeroen C. van Gelderen" , current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007230739.JAA94403@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, 23 Jul 2000, Mark Murray wrote: > > Okay, using RSA keys wasn't the best example to pick, but Yarrow also > > seems easy to misuse in other cases: for example if you want to generate > > multiple 256-bit symmetric keys (or other random data) at the same time, > > each additional key after the first won't contain any additional entropy, > > so if you break the state of the PRNG at the time the first one was > > generated you get the others for free (until the thing reseeds). > > > > This design tradeoff is discussed in section 4.1 of the paper. > > Tweakable. Doing a reseed operation with every output is going to be *very* computationally expensive. > > > That said, there is nothing to prevent the system admin > > > from tweaking the Yarrow security parameters so that > > > Yarrow will only spit out as many bits or pseudo-randomness > > > as it gathers bits of entropy.[4] > > > > Well, I don't see a way to tune this without modifying the Yarrow design, > > since the entropy pool is intentionally decoupled from the output > > mechanism, and it seems like it would add additional (unnecessary) > > overhead anyway to use it in that fashion. > > Look at the sysctls (some improvements and documentation coming). Please tell me which of the following sysctls will cause Yarrow to deactivate the keyed cipher feature that spits out a constant data stream independent of the state of the entropy pools: kern.random.yarrow.gengateinterval: 10 kern.random.yarrow.bins: 10 kern.random.yarrow.fastthresh: 100 kern.random.yarrow.slowthresh: 160 kern.random.yarrow.slowoverthresh: 2 > > Indications are we can probably get quite a lot of usable entropy from a > > standard system (on the order of many kilobytes per second - but I need to > > read more of the literature about processing of entropy samples) - in this > > case I think maintaining a third pool which is directly tapped by > > /dev/random, and leaving Yarrow sitting behind /dev/urandom is the way to > > go. > > I suspect you are missing the whole point of yarrow. Yarrow protects > you from the compromises inherent in attackers injecting their own > junk into the "third pool". Mark, I understand this stuff quite well - I'm not "missing the whole point of Yarrow" at all. Yarrow is a good system as far as it goes, but the authors themselves admit this limitation - you just can't use this tool in contexts it was not designed for. 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 23 0:50:18 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 69E4B37B93F; Sun, 23 Jul 2000 00:50:15 -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 AAA83191; Sun, 23 Jul 2000 00:50:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Jul 2000 00:50:15 -0700 (PDT) From: Kris Kennaway To: rosti@surfree.net.il Cc: current@FreeBSD.org Subject: Re: Netscape In-Reply-To: <397AAF59.B191E3E9@surfree.net.il> 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, 23 Jul 2000 rosti@surfree.net.il wrote: > Netscape 4.74 is already out but FreeBSD 4.1-RC2 contains 4.73 version > yet. Will FreeBSD 4.1-RELEASE contains the last version (4.74) of > Netscape Communicator and Navigator? No. The ports tree has been frozen. 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 23 1: 2:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 42D0C37B746; Sun, 23 Jul 2000 01:02:29 -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 KAA02771; Sun, 23 Jul 2000 10:02:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Kris Kennaway Cc: "Jeroen C. van Gelderen" , Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Sat, 22 Jul 2000 17:41:15 PDT." Date: Sun, 23 Jul 2000 10:02:16 +0200 Message-ID: <2769.964339336@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Kri s Kennaway writes: >On Sat, 22 Jul 2000, Jeroen C. van Gelderen wrote: > >> I agree that you need long RSA keys ... but the real >> discussion isn't really about key length but rather about >> the overall complexity of attacking the key: > >Okay, using RSA keys wasn't the best example to pick, but Yarrow also >seems easy to misuse in other cases: for example if you want to generate >multiple 256-bit symmetric keys (or other random data) at the same time, Kris, Obviously, if you need more randomness than a stock FreeBSD system can provide you with, you add hardware to give you more randomness. In other words, and more bluntly: Please shut up now, will you ? -- 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 Sun Jul 23 1: 6: 1 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 3414937B96F; Sun, 23 Jul 2000 01:05:52 -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 KAA02107; Sun, 23 Jul 2000 10:05:41 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007230805.KAA02107@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, 23 Jul 2000 00:40:44 MST." Date: Sun, 23 Jul 2000 10:05:41 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is basically the model I am advocating for /dev/random. It's also the > alternative "basic design philosophy" described in the yarrow paper. Erm, read 4.1 again :-). The paragraph that begins "One approach..." is the old approach. It is also the approach that you are advocating. The next paragraph "Yarrow takes..." is Yarrow, and the current implementation. > See "important issue" number 2 on p6. Yarrow-derived numbers are only > "good for" 256 bits of strength. Modulo reseeds, Yarrow never accumulates > more than 256 bits of entropy. Therefore you are silly to use it for > applications which require more than 256 bits of randomness. > > > Where do you draw the line? I could make it Yarrow-N, only to have > > someone insist on $((N+1)) in the very next breath. > > Precisely, which is why /dev/random shouldn't use Yarrow, or any other > seeded-cipher PRNG. It should not use the old method, which is attackable for many reasons that Schneier makes clear. (Effectively a 128 bit hash with a reseed ("stir") every read. Can you spell "Iterative attack"? :-) ). Where does that leave us? How good were our old numbers? How many users have I screwed by implementing that system? How do we fix it? What accumulation algorithm do we use that does not clue the reader into what the internal state is? > > With what we have, I am staking my career on the "uncrackability" > > of Blowfish-256. If that holds then Yarrow is safe. (The old one > > I'm not bothered about this. My point is that, by design, Yarrow is not > suitable as a replacement for /dev/random (/dev/urandom, yes). _My_ point is that the old system is broken, and that IMO Yarrow is a good replacement. (I support my point by noting that Schneier is a far better cryptographer than I, and he designed the algorithm that I implemented). 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 23 1: 8:57 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 A503837B96F; Sun, 23 Jul 2000 01:08:54 -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 BAA85450; Sun, 23 Jul 2000 01:08:54 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Jul 2000 01:08:54 -0700 (PDT) From: Kris Kennaway To: Poul-Henning Kamp Cc: "Jeroen C. van Gelderen" , Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <2769.964339336@critter.freebsd.dk> 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, 23 Jul 2000, Poul-Henning Kamp wrote: > Obviously, if you need more randomness than a stock FreeBSD system > can provide you with, you add hardware to give you more randomness. This won't help if it's fed through Yarrow. > In other words, and more bluntly: Please shut up now, will you ? No. There are legitimate technical issues to be resolved here. If you don't want to participate, press 'D' and move on with your life. 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 23 1:21:44 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 8BC7537B96F; Sun, 23 Jul 2000 01:21:41 -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 BAA85964; Sun, 23 Jul 2000 01:21:41 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Jul 2000 01:21:41 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007230805.KAA02107@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, 23 Jul 2000, Mark Murray wrote: > Erm, read 4.1 again :-). The paragraph that begins "One approach..." is > the old approach. It is also the approach that you are advocating. > > The next paragraph "Yarrow takes..." is Yarrow, and the current > implementation. "The strength of the first approach is that, if properly designed, it is possible to get unconditional security from the PRNG." This is a good thing :-) > It should not use the old method, which is attackable for many > reasons that Schneier makes clear. (Effectively a 128 bit hash with > a reseed ("stir") every read. Can you spell "Iterative attack"? :-) ). > > Where does that leave us? > > How good were our old numbers? How many users have I screwed by > implementing that system? Please understand that this is not a personal attack - I appreciate your work, and welcome it in FreeBSD. My concern is with what Yarrow does not do, but which FreeBSD needs: a PRNG which is capable of generating arbitrarily large keys. > How do we fix it? What accumulation algorithm do we use that does not > clue the reader into what the internal state is? I suggest we ask Bruce Schneier instead of bantering back and forth about the issue. I claim (supported by the quote above) that it's possible to implement such a system securely and have it co-exist with Yarrow. > _My_ point is that the old system is broken, and that IMO Yarrow is a > good replacement. (I support my point by noting that Schneier is a far > better cryptographer than I, and he designed the algorithm that I > implemented). Yarrow is a good replacement for /dev/urandom. However it doesn't provide features which I believe are necessary, namely the ability to generate high-entropy keys of arbitrary size, without severely impacting on PRNG performance by constantly reseeding. 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 23 1:25:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id ACE8B37B96F; Sun, 23 Jul 2000 01:25:09 -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 KAA03058; Sun, 23 Jul 2000 10:25:00 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Kris Kennaway Cc: "Jeroen C. van Gelderen" , Mark Murray , current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Sun, 23 Jul 2000 01:08:54 PDT." Date: Sun, 23 Jul 2000 10:25:00 +0200 Message-ID: <3056.964340700@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Kri s Kennaway writes: >On Sun, 23 Jul 2000, Poul-Henning Kamp wrote: > >> Obviously, if you need more randomness than a stock FreeBSD system >> can provide you with, you add hardware to give you more randomness. > >This won't help if it's fed through Yarrow. Nobody has said anything about forcing you to use Yarrow, have they ? >> In other words, and more bluntly: Please shut up now, will you ? > >No. There are legitimate technical issues to be resolved here. If you >don't want to participate, press 'D' and move on with your life. I think the general concensus is that all legitimate technical issues has been resolved and that we are stuck with a small band of merry men wasting bandwidth by repeatedly rehashing the obvious: "Any source of random bits has a finite capacity and you should not exceed that capacity." I have not seen any new information in the last N emails from you. -- 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 Sun Jul 23 1:31:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from surfree.net.il (mail.surfree.net.il [212.3.192.12]) by hub.freebsd.org (Postfix) with SMTP id 1CC7E37B6A5 for ; Sun, 23 Jul 2000 01:31:22 -0700 (PDT) (envelope-from rosti@surfree.net.il) Received: From [surfree.net.il 212.3.218.19] By SuperMail at surfree.net.il with SMTP; Sun, 23 Jul 2000 11:28:34 +0200 GMT Message-ID: <397ABB49.B6A0BBA0@surfree.net.il> Date: Sun, 23 Jul 2000 11:30:49 +0200 From: rosti@surfree.net.il X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: Netscape 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: > On Sun, 23 Jul 2000 rosti@surfree.net.il wrote: > > > Netscape 4.74 is already out but FreeBSD 4.1-RC2 contains 4.73 version > > yet. Will FreeBSD 4.1-RELEASE contains the last version (4.74) of > > Netscape Communicator and Navigator? > > No. The ports tree has been frozen. If there will be "FreeBSD 4.1-RC3+" will it contains the newer version of Netscape? Are the fixed in Netscape 4.74 bugs not critical for release? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 1:40:19 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 4707637B6A5; Sun, 23 Jul 2000 01:40:14 -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 BAA86905; Sun, 23 Jul 2000 01:40:14 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Jul 2000 01:40:14 -0700 (PDT) From: Kris Kennaway To: rosti@surfree.net.il Cc: current@FreeBSD.org Subject: Re: Netscape In-Reply-To: <397ABB49.B6A0BBA0@surfree.net.il> 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, 23 Jul 2000 rosti@surfree.net.il wrote: > If there will be "FreeBSD 4.1-RC3+" will it contains the newer version of > Netscape? No - the ports collection for 4.1-RELEASE has been frozen. > Are the fixed in Netscape 4.74 bugs not critical for release? Who knows? I don't know of any changelog for Netscape. 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 23 1:56: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from munin.odin-corporation.com (node-d8e9ad12.powerinter.net [216.233.173.18]) by hub.freebsd.org (Postfix) with ESMTP id D598737B68F; Sun, 23 Jul 2000 01:56:00 -0700 (PDT) (envelope-from lars@odin-corporation.com) Received: from odin-corporation.com (localhost [127.0.0.1]) by munin.odin-corporation.com (8.9.3/8.9.1) with ESMTP id DAA59949; Sun, 23 Jul 2000 03:55:41 -0500 (CDT) (envelope-from lars@odin-corporation.com) Message-ID: <397AB30D.ACB14F7F@odin-corporation.com> Date: Sun, 23 Jul 2000 03:55:41 -0500 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: rosti@surfree.net.il Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: Netscape References: <397ABB49.B6A0BBA0@surfree.net.il> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG rosti@surfree.net.il wrote: > Kris Kennaway wrote: > > > On Sun, 23 Jul 2000 rosti@surfree.net.il wrote: > > > > > Netscape 4.74 is already out but FreeBSD 4.1-RC2 contains 4.73 version > > > yet. Will FreeBSD 4.1-RELEASE contains the last version (4.74) of > > > Netscape Communicator and Navigator? > > > > No. The ports tree has been frozen. > > If there will be "FreeBSD 4.1-RC3+" will it contains the newer version of > Netscape? Are the fixed in Netscape 4.74 bugs not critical for release? > Thanks. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message One of the big things they fixed is LDAP. You can now use the ldap search facility in the address book..... Lars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 2:41:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from surfree.net.il (mail.surfree.net.il [212.3.192.12]) by hub.freebsd.org (Postfix) with SMTP id 6BC8137BAB6 for ; Sun, 23 Jul 2000 02:41:27 -0700 (PDT) (envelope-from rosti@surfree.net.il) Received: From [surfree.net.il 212.3.218.19] By SuperMail at surfree.net.il with SMTP; Sun, 23 Jul 2000 12:38:38 +0200 GMT Message-ID: <397ACBB4.C92A9BB5@surfree.net.il> Date: Sun, 23 Jul 2000 12:40:52 +0200 From: rosti@surfree.net.il X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: Netscape 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: > On Sun, 23 Jul 2000 rosti@surfree.net.il wrote: > > > If there will be "FreeBSD 4.1-RC3+" will it contains the newer version of > > Netscape? > > No - the ports collection for 4.1-RELEASE has been frozen. > > > Are the fixed in Netscape 4.74 bugs not critical for release? > > Who knows? I don't know of any changelog for Netscape. Go to http://home.netscape.com/eng/mozilla/4.7/relnotes/ there is the release notes for all 4.7x versions for all platforms. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 3:40:15 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 8669137B70C; Sun, 23 Jul 2000 03:40:04 -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 MAA00534; Sun, 23 Jul 2000 12:30:41 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007231030.MAA00534@grimreaper.grondar.za> To: Mark Murray Cc: Kris Kennaway , Poul-Henning Kamp , current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: <200007231016.MAA00486@grimreaper.grondar.za> In-Reply-To: <200007231016.MAA00486@grimreaper.grondar.za> ; from Mark Murray "Sun, 23 Jul 2000 12:16:08 +0200." Date: Sun, 23 Jul 2000 12:30:41 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Obviously, if you need more randomness than a stock FreeBSD system > > > can provide you with, you add hardware to give you more randomness. > > > > This won't help if it's fed through Yarrow. > > *BZZZZTTT!* Wrong. A good hardware RNG when fed at a high-enough rate > through Yarrow can easily produce a continuous stream of what you need. > (If we take that route, the current implementation may need to be tweaked > a bit to stop reseeding after a period of unuse to avoid hammering the > kernel too much; this needs careful thought). Been thinking about this; the current implemnetation runs continuously (thanks to taskqueue(9)). There is no reason that it couldn't be made (somewhat) use-driven, so that it works harder at harvesting when being used heavily. This may make it slower, but it would hurt the kernel a bit less when not in use. 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 23 3:42:39 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 28BAE37B70C; Sun, 23 Jul 2000 03:42:29 -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 MAA00486; Sun, 23 Jul 2000 12:16:08 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007231016.MAA00486@grimreaper.grondar.za> To: Kris Kennaway Cc: Poul-Henning Kamp , "Jeroen C. van Gelderen" , Mark Murray , current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Kris Kennaway "Sun, 23 Jul 2000 01:08:54 MST." Date: Sun, 23 Jul 2000 12:16:08 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 23 Jul 2000, Poul-Henning Kamp wrote: > > > Obviously, if you need more randomness than a stock FreeBSD system > > can provide you with, you add hardware to give you more randomness. > > This won't help if it's fed through Yarrow. *BZZZZTTT!* Wrong. A good hardware RNG when fed at a high-enough rate through Yarrow can easily produce a continuous stream of what you need. (If we take that route, the current implementation may need to be tweaked a bit to stop reseeding after a period of unuse to avoid hammering the kernel too much; this needs careful thought). 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 23 3:43:18 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 EC96C37BAB6; Sun, 23 Jul 2000 03:42:54 -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 MAA00467; Sun, 23 Jul 2000 12:10:06 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007231010.MAA00467@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, 23 Jul 2000 00:49:35 MST." Date: Sun, 23 Jul 2000 12:10:06 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > This design tradeoff is discussed in section 4.1 of the paper. > > > > Tweakable. > > Doing a reseed operation with every output is going to be *very* > computationally expensive. Tradeoff. What do you want? Lightning fast? Excessive security? Balance it out. > > > Well, I don't see a way to tune this without modifying the Yarrow > > > design, since the entropy pool is intentionally decoupled from > > > the output mechanism, and it seems like it would add additional > > > (unnecessary) overhead anyway to use it in that fashion. > > > > Look at the sysctls (some improvements and documentation coming). > > Please tell me which of the following sysctls will cause Yarrow to > deactivate the keyed cipher feature that spits out a constant data > stream independent of the state of the entropy pools: > > kern.random.yarrow.gengateinterval: 10 kern.random.yarrow.bins: 10 > kern.random.yarrow.fastthresh: 100 kern.random.yarrow.slowthresh: 160 > kern.random.yarrow.slowoverthresh: 2 None, but very paranoid reseed intervals can be set if required. (Requires more entropy-harvesting, but doable). > > I suspect you are missing the whole point of yarrow. Yarrow protects > > you from the compromises inherent in attackers injecting their own > > junk into the "third pool". > > Mark, I understand this stuff quite well - I'm not "missing the whole > point of Yarrow" at all. The acknowlegment that I am looking for is that the old, simple "gather entropy, stir with hash, serve" model is inadequate IMO, and I have not seen any alternatives. > Yarrow is a good system as far as it goes, > but the authors themselves admit this limitation - you just can't use > this tool in contexts it was not designed for. Goes for any tool; a universal truth. I'm trying to come up with a better tool that what was, and I believe that I have, and I am perhaps misunderstanding folks' motives in shouting for the blocking model. In quite a few cases, it has been a very obvious non-understanding of what Yarrow is (I apologise for lumping you in this category). I'll relent somewhat if a secure entropy distilling algorithm could be found; one which stands up to crypanalysis. Will you relent a step or two if I can get the entropy harvesting _rate_ high enough? :-) 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 23 3:43:24 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 4FCF937BB7D; Sun, 23 Jul 2000 03:43: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 MAA00503; Sun, 23 Jul 2000 12:24:56 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007231024.MAA00503@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, 23 Jul 2000 01:21:41 MST." Date: Sun, 23 Jul 2000 12:24:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 23 Jul 2000, Mark Murray wrote: > > > Erm, read 4.1 again :-). The paragraph that begins "One approach..." is > > the old approach. It is also the approach that you are advocating. > > > > The next paragraph "Yarrow takes..." is Yarrow, and the current > > implementation. > > "The strength of the first approach is that, if properly designed, it is > possible to get unconditional security from the PRNG." "if properly designed" is the key phrase. The previous on was not, and I do not have the cryptographic skill to do so. > This is a good thing :-) In theory :-). In practice, we have no algorithms to go on. > Please understand that this is not a personal attack - I appreciate your > work, and welcome it in FreeBSD. My concern is with what Yarrow does not > do, but which FreeBSD needs: a PRNG which is capable of generating > arbitrarily large keys. We are limited by the rate at which we can harvest entropy. The PC platform has quite close to Jack Shite available if there is no-one one the keyboard. > > How do we fix it? What accumulation algorithm do we use that does not > > clue the reader into what the internal state is? > > I suggest we ask Bruce Schneier instead of bantering back and forth about > the issue. I claim (supported by the quote above) that it's possible to > implement such a system securely and have it co-exist with Yarrow. In theory, yes. I'll ask Schneier. He's already said he'll look at my code when he has the time. > > _My_ point is that the old system is broken, and that IMO Yarrow is a > > good replacement. (I support my point by noting that Schneier is a far > > better cryptographer than I, and he designed the algorithm that I > > implemented). > > Yarrow is a good replacement for /dev/urandom. However it doesn't provide > features which I believe are necessary, namely the ability to generate > high-entropy keys of arbitrary size, without severely impacting on PRNG > performance by constantly reseeding. Here we must agree to differ. :-) Yarrow's data _is_ high entropy. It is indistinguishable from "real" entropy if done right (for the purposes of this argument, I need to assume that Schneier does it right). Yarrow is "attack oriented", which is the correct approach if you want your numbers for crypto and not for (say) science. 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 23 4:31:56 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 5683C37B74A; Sun, 23 Jul 2000 04:31:54 -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 EAA02369; Sun, 23 Jul 2000 04:31:54 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Jul 2000 04:31:54 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007231010.MAA00467@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, 23 Jul 2000, Mark Murray wrote: > > > > This design tradeoff is discussed in section 4.1 of the paper. > > > > > > Tweakable. > > > > Doing a reseed operation with every output is going to be *very* > > computationally expensive. > > Tradeoff. What do you want? Lightning fast? Excessive security? Balance > it out. Thinking about it further, I dont think Yarrow can even do this (introduce entropy into every output value) without bypassing the block cipher. And if you reseed with every 256 bits of output then you're vulnerable to an iterative guessing attack because the fast pool won't have much in it. So if we want to use the Yarrow "backend" we'd have to basically reduce it to the system I describe below. > The acknowlegment that I am looking for is that the old, simple "gather > entropy, stir with hash, serve" model is inadequate IMO, and I have not > seen any alternatives. There are two other models which rate "pretty well-designed" in the Yarrow paper: the cryptlib and PGP PRNGs. I don't know what their properties are right now (the cryptlib one is described in the paper on PRNG cryptanalysis). > I'll relent somewhat if a secure entropy distilling algorithm could be > found; one which stands up to crypanalysis. Well, a simple scheme which doesn't seem to suffer from any of the vulnerabilities discussed in the schneier papers is to accumulate entropy in a pool, and only return output when the pool is full. i.e. the PRNG would either block or return 0 bytes of data, or a full pool's worth. > Will you relent a step or two if I can get the entropy harvesting _rate_ > high enough? :-) If we get the entropy pools filling fast enough that the reseed is triggering close to every 256 bits of output then it becomes much less of a concern (but it's still there, because reseeding happens asynchronously with respect to PRNG output). However I think that in practice this will be too heavy on the CPU (unless we weaken the reseed operation) and make dd if=/dev/urandom of=/dev/null a very effective local user DoS :-( 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 23 5: 1:37 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 EDB0437B945; Sun, 23 Jul 2000 05:01:28 -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 OAA00883; Sun, 23 Jul 2000 14:01:33 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007231201.OAA00883@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, 23 Jul 2000 04:31:54 MST." Date: Sun, 23 Jul 2000 14:01:33 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The acknowlegment that I am looking for is that the old, simple "gather > > entropy, stir with hash, serve" model is inadequate IMO, and I have not > > seen any alternatives. > > There are two other models which rate "pretty well-designed" in the Yarrow > paper: the cryptlib and PGP PRNGs. I don't know what their properties are > right now (the cryptlib one is described in the paper on PRNG > cryptanalysis). Do you have copies of the articles concerned? I'd surely appreciate a photocopy of the relevant pages if you don't mind! :-) > > I'll relent somewhat if a secure entropy distilling algorithm could be > > found; one which stands up to crypanalysis. > > Well, a simple scheme which doesn't seem to suffer from any of the > vulnerabilities discussed in the schneier papers is to accumulate entropy > in a pool, and only return output when the pool is full. i.e. the PRNG > would either block or return 0 bytes of data, or a full pool's worth. Hmm. Timing attacks? Known-input attacks? > > Will you relent a step or two if I can get the entropy harvesting _rate_ > > high enough? :-) > > If we get the entropy pools filling fast enough that the reseed is > triggering close to every 256 bits of output then it becomes much less of > a concern (but it's still there, because reseeding happens asynchronously > with respect to PRNG output). However I think that in practice this will > be too heavy on the CPU (unless we weaken the reseed operation) and make > dd if=/dev/urandom of=/dev/null a very effective local user DoS :-( The dd if=/dev/urandom of=/dev/null is _already_ a doozy of a dos. Likewise a fork-bomb, a /tmp-filler, likewise a whole bunch of things much worse. Heck, you can hurt your system with cat /dev/zero > /dev/null. Asynchonous reseeding _improves_ the situation; the attacker cannot force it to any degree of accuracy, and if he has the odds stacked heavily against him that each 256-bits of output will have an associated reseed, it makes his job pretty damn difficult. 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 23 5:53:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.42.org (matrix.42.org [194.246.250.200]) by hub.freebsd.org (Postfix) with ESMTP id 9A29837BC00 for ; Sun, 23 Jul 2000 05:53:53 -0700 (PDT) (envelope-from sec@42.org) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.5) id OAA28448 (sender ); Sun, 23 Jul 2000 14:53:50 +0200 (CEST) Date: Sun, 23 Jul 2000 14:53:50 +0200 (CEST) Message-Id: <200007231253.OAA28448@matrix.42.org> From: Stefan `Sec` Zehl To: freebsd-current@freebsd.org Subject: Re: randomdev entropy gathering is really weak Summary: Expires: References: <3056.964340700@critter.freebsd.dk> Followup-To: Distribution: Organization: Seeking the question Keywords: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message , Kri > s Kennaway writes: > >On Sun, 23 Jul 2000, Poul-Henning Kamp wrote: > > > >> Obviously, if you need more randomness than a stock FreeBSD system > >> can provide you with, you add hardware to give you more randomness. > > > >This won't help if it's fed through Yarrow. > > Nobody has said anything about forcing you to use Yarrow, have they ? If FreeBSD delivers with it, it will get used. I think Kris has a valid concern. If I assume that I will get good randomness from /dev/random, and I don't, there is potential danger. Assume I want to encrypt a message by XOR'ing with randomness. If I then exchange my keys securely, the message is uncrackable. With the current approach it has a 256bits key. This is, in my eyes, not good. Although yarrow is nice, It's suited for any kind of key generation. > I have not seen any new information in the last N emails from you. This is because his concerns aren't addressed yet. CU, Sec -- Das Usenet ist so ein wunderbares, aber zerbrechliches Medium und so viele treten es so in den Dreck und machen es unbenutzbar - sei es durch Absicht oder Gedankenlosigkeit, was vom Ergebnis das gleiche ist. -- Bettina Fink To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 6: 6:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (beachchick.freebsd.dk [212.242.32.208]) by hub.freebsd.org (Postfix) with ESMTP id 26E0A37BBB3 for ; Sun, 23 Jul 2000 06:06:48 -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 PAA03663; Sun, 23 Jul 2000 15:06:34 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Stefan `Sec` Zehl Cc: freebsd-current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Sun, 23 Jul 2000 14:53:50 +0200." <200007231253.OAA28448@matrix.42.org> Date: Sun, 23 Jul 2000 15:06:34 +0200 Message-ID: <3661.964357594@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007231253.OAA28448@matrix.42.org>, Stefan `Sec` Zehl writes: >Assume I want to encrypt a message by XOR'ing with randomness. > >If I then exchange my keys securely, the message is uncrackable. > >With the current approach it has a 256bits key. This is, in my eyes, not >good. Although yarrow is nice, It's suited for any kind of key >generation. The first law of crypto clearly states: "Know what you're doing". There is no way around that law. We cannot load down FreeBSD with impossibly heavy computations to cater for any and all conceiveable application of random numbers. In particular I fear that the current implementation already has killed battery lifetimes on laptops :-( -- 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 Sun Jul 23 9:22:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from veldy.net (veldy-host201.dsl.visi.com [208.42.48.201]) by hub.freebsd.org (Postfix) with ESMTP id AF3A337BC92 for ; Sun, 23 Jul 2000 09:22:41 -0700 (PDT) (envelope-from veldy@veldy.net) Received: from cascade (cascade.veldy.net [192.168.0.1]) by veldy.net (Postfix) with SMTP id 11CA48C1C for ; Sun, 23 Jul 2000 11:24:08 -0500 (CDT) Message-ID: <002701bff4c2$38a71510$0100a8c0@cascade> From: "Thomas T. Veldhouse" To: Subject: 4.1-RC panic when loading dnetc (distributed.net client) Date: Sun, 23 Jul 2000 11:22:40 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using the 4.63 dnetc native FreeBSD version of the distributed.net client. Here is what happens: --- Local package initialization: dnetc Fatal trap 12: page fault while in kernel mode fault virtual address = 0xe0aedffc fault code = supervisor read, page not present instruction pointer = 0x8:0xc01871cf stack pointer = 0x10:0xc8a13dcc frame pointer = 0x10:0xc8a13ddc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor flags = interrupt enabled, resume, IOPL = 0 current process = 281(dnetc) interrupt mask = none panic: page fault --- This machine is a rebuilt world (07212000) with standard kernel optimizations COPTFLAGS = -O -pipe and CFLAGS = -O -pipe -march=pentiumpro. I am having a hard time getting into my system to disable dnetc and see if I can get more details. The CD ROM I burned with a stable from about two weeks back ignores my key entry to go to a commad prompt so that I can load the kernel off of the CD and then boot into the OS (manually). Enter is all that works and it sends me to kernel config and then sysinstall. I added "boot" to /boot/loader.rc, so I don't get a command prompt option at all when I boot my machine normally. I just thought I should report this bug. Thanks, Tom Veldhouse veldy@veldy.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 11: 9:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay2.inwind.it (relay2.inwind.it [212.141.53.73]) by hub.freebsd.org (Postfix) with ESMTP id 52F0B37B6B3 for ; Sun, 23 Jul 2000 11:09:41 -0700 (PDT) (envelope-from bartequi@inwind.it) Received: from bartequi.ottodomain.org (212.141.79.47) by relay2.inwind.it; 23 Jul 2000 20:09:40 +0200 From: Salvo Bartolotta Date: Sun, 23 Jul 2000 19:10:54 GMT Message-ID: <20000723.19105400@bartequi.ottodomain.org> Subject: make installkernel broken ? (was Re: World broken) To: Warner Losh Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200007230619.AAA18613@harmony.village.org> References: <200007230619.AAA18613@harmony.village.org> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) 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 >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 7/23/00, 7:19:03 AM, Warner Losh wrote regarding=20 World broken: > cc -O -pipe -DMD5 -DSHA1 -DRMD160 =20 -I/usr/obj/home/imp/FreeBSD/src/i386/usr/include -o mtree compare.o=20 crc.o create.o excludes.o misc.o mtree.o spec.o verify.o -lmd > misc.o: In function `flags_to_string': > misc.o(.text+0x89): undefined reference to `fflagstostr' > spec.o: In function `set': > spec.o(.text+0x5f5): undefined reference to `strtofflags' > *** Error code 1 > I'm kludging mtree so that make buildworld isn't broken. Don't remove= > the kludge until such time as the underlying problems have been > corrected. Dear FreeBSd'ers, The good news: I have just made buildworld (sources cvsup'ed today),=20 and made buildkernel with no problems. The (moderately) bad news: make installkernel fails: /usr/src # >=3D=3D=3D=3D> make installkernel cd /usr/obj/usr/src/sys/GENERIC; MAKEOBJDIRPREFIX=3D/usr/obj =20 COMPILER_PATH=3D/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386 /usr/bin =20 LIBRARY_PATH=3D/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/ lib OBJFORMAT_PATH=3D/usr/obj/usr/src/i386/usr/libexec =20 PERL5LIB=3D/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0 =20 PATH=3D/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/us r/obj/usr/src/i386/usr/games:/tmp/install.12899 MACHINE=3Di386=20 KERNEL=3DGENERIC make KERNEL=3DGENERIC install make: not found *** Error code 127 Stop in /usr/src. *** Error code 1 Stop in /usr/src. It is a few weeks since I last made a -CURRENT world, so I have been=20 cautious enough, and I have chosen the buildkernel and installkernel=20 targets -- as if I were updating from -STABLE. Since I am already well "flamed" (~ 35/40 =B0C down here), please be so = kind as not to flame me :-)=20 Best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 11:17:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhub1.cuckoo.com (wrangler.cuckoo.com [209.113.113.66]) by hub.freebsd.org (Postfix) with SMTP id 0458937B6AE for ; Sun, 23 Jul 2000 11:17:31 -0700 (PDT) (envelope-from dbaker@cuckoo.com) Received: (qmail 55745 invoked by uid 200); 23 Jul 2000 18:17:25 -0000 Date: Sun, 23 Jul 2000 13:17:25 -0500 From: Daniel Baker To: "Thomas T. Veldhouse" Cc: freebsd-current@freebsd.org Subject: Re: 4.1-RC panic when loading dnetc (distributed.net client) Message-ID: <20000723131725.A44906@cuckoo.com> Reply-To: dbaker@distributed.net References: <002701bff4c2$38a71510$0100a8c0@cascade> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <002701bff4c2$38a71510$0100a8c0@cascade>; from veldy@veldy.net on Sun, Jul 23, 2000 at 11:22:40AM -0500 X-PGP-RSA-Fingerprint: F3 41 B7 EE 96 92 F5 35 5E 3C 02 61 08 22 23 98 X-PGP-DSS-Fingerprint: FB06 B44E BD64 3596 C545 8E79 98BE 7C21 4B0D 5093 X-Operating-System: FreeBSD i386 X-Distributed: Join the cows! http://www.distributed.net/ _]:8) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Jul-2000, Thomas T. Veldhouse wrote: > I am using the 4.63 dnetc native FreeBSD version of the distributed.net > client. Here is what happens: > [snip] > I am having a hard time getting into my system to disable dnetc and see if I > can get more details. The CD ROM I burned with a stable from about two > weeks back ignores my key entry to go to a commad prompt so that I can load > the kernel off of the CD and then boot into the OS (manually). Enter is all > that works and it sends me to kernel config and then sysinstall. I added > "boot" to /boot/loader.rc, so I don't get a command prompt option at all > when I boot my machine normally. Thomas, Just use "boot -s" to boot into single user mode so that you can disable the dnetc.sh script before you get into multiuser mode when all the rc.d scripts are executed. How long has the machine that you're using been alive for? Has it had stability problems in the past? Is it under heavy load? Are the CPU fan(s) running? Daniel -- dbaker@distributed.net - Chief Operations Administrator - distributed.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 11:24:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 3AC3137B6AE for ; Sun, 23 Jul 2000 11:24:20 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 881D9221; Sun, 23 Jul 2000 11:24:19 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id LAA07211; Sun, 23 Jul 2000 11:24:18 -0700 (PDT) Message-ID: <397B3852.516AE70B@cup.hp.com> Date: Sun, 23 Jul 2000 11:24:18 -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: Salvo Bartolotta Cc: Warner Losh , freebsd-current@FreeBSD.ORG Subject: Re: make installkernel broken ? (was Re: World broken) References: <200007230619.AAA18613@harmony.village.org> <20000723.19105400@bartequi.ottodomain.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Salvo Bartolotta wrote: > > Dear FreeBSd'ers, > > The good news: I have just made buildworld (sources cvsup'ed today), > and made buildkernel with no problems. > > The (moderately) bad news: make installkernel fails: Already fixed. Please re-cvsup. Note that the kernel will be called 'kernel' (again)! If you used the installkernel before and have modified your /boot/loader.conf, make sure it's booting /kernel again. HTH, -- 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 Sun Jul 23 11:42: 9 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 0F2D437B601 for ; Sun, 23 Jul 2000 11:42:02 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 6D03A52; Sun, 23 Jul 2000 14:42:00 -0400 (AST) Message-ID: <397B3C78.1C16D34A@vangelderen.org> Date: Sun, 23 Jul 2000 14:42:00 -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: David Schwartz Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Schwartz wrote: > > > > /dev/random should block if the system does not contain as much > > real entropy > > > as the reader desires. Otherwise, the PRNG implementation will be the > > > weakest link for people who have deliberately selected higher levels of > > > protection from cryptographic attack. > > > I don't want to rehash this thread from the beginning. Please go > > back, read the Yarrow paper, and recognise that Yarrow is not an > > entropy-counter, it is a cryptographically secure PRNG. The "count > > random bits and block" model does not apply. > > Then the current implementation cannot provide the usual semantics for > /dev/random, while it can provide the semantics for /dev/urandom. As I > understand it, /dev/random is supposed to provide true randomness suitable > for generating keys of unlimited length, whereas /dev/urandom is supposed to > provide cryptographically-strong randomness for general applications. > > If people want /dev/random to seed 1024-bit keys, /dev/random must be > stronger than a 1024-bit key. 1. The current /dev/random cannot do it, it's less secure than Yarrow for a variety of reasons. So we have a net improvement anyway. Thanks Mark. 2. Most people do not want to seed 1024-bit keys as outlined in another mail in this thread. If they *understand* the issues involved they will realize that 2^256 complexity is plenty uncrackable for all practical purposes. FreeBSD is about practical purposes IMHO. 3. Yarrow can be modified to just do this, should someone think this is neccessary. Read the paper and think of what happens when you set Pg to 1/(2^(k/3)). (Note that the paper restricts this value to 1 <= Pg but that's of no importance here.) ** This is overly conservative for most applications I can think of; Even a multi-million dollar financial transactioning system will be practically secure when Pg is set to 1. 4. Nothing prevents you from adapting Yarrow so that current /dev/random semantics are preserved, making Yarrow even better. It can be done with the current design it's just not very beneficial to do it. 5. Yarrow was designed as a better replacement for most any PRNG by a couple of bright cryptographers. Can you do better than that? 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 Sun Jul 23 11:59:35 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 909EE37B6C8; Sun, 23 Jul 2000 11:59:31 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id EB74257; Sun, 23 Jul 2000 14:59:28 -0400 (AST) Message-ID: <397B4090.6A15442E@vangelderen.org> Date: Sun, 23 Jul 2000 14:59:28 -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: Kris Kennaway Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak 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: > > On Sun, 23 Jul 2000, Mark Murray wrote: > > > > > > This design tradeoff is discussed in section 4.1 of the paper. > > > > > > > > Tweakable. > > > > > > Doing a reseed operation with every output is going to be *very* > > > computationally expensive. > > > > Tradeoff. What do you want? Lightning fast? Excessive security? Balance > > it out. > > Thinking about it further, I dont think Yarrow can even do this (introduce > entropy into every output value) without bypassing the block cipher. Why not? > And > if you reseed with every 256 bits of output then you're vulnerable to an > iterative guessing attack because the fast pool won't have much in it. You would block until the pool is filled with entropy. [...] > There are two other models which rate "pretty well-designed" in the Yarrow > paper: the cryptlib and PGP PRNGs. I don't know what their properties are > right now (the cryptlib one is described in the paper on PRNG > cryptanalysis). Fortunately you don't need them :-) > > I'll relent somewhat if a secure entropy distilling algorithm could be > > found; one which stands up to crypanalysis. > > Well, a simple scheme which doesn't seem to suffer from any of the > vulnerabilities discussed in the schneier papers is to accumulate entropy > in a pool, and only return output when the pool is full. i.e. the PRNG > would either block or return 0 bytes of data, or a full pool's worth. And you can make Yarrow do just that. Not very practical but you can do it. You effectively set Pg to 1/(2^(k/3)). > > Will you relent a step or two if I can get the entropy harvesting _rate_ > > high enough? :-) > > If we get the entropy pools filling fast enough that the reseed is > triggering close to every 256 bits of output then it becomes much less of > a concern (but it's still there, because reseeding happens asynchronously > with respect to PRNG output). Reseeds do not *have* to happen asynchronously as pointed out above. What is of importance is that you *cannot* forcibly trigger a reseed without there being enough entropy in the pools. There is nothing against having /dev/random block until the pools have accumulated enough entropy. 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 Sun Jul 23 12:26:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (ftp.webmaster.com [209.10.218.74]) by hub.freebsd.org (Postfix) with ESMTP id B6BBC37B56D for ; Sun, 23 Jul 2000 12:26:08 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([216.152.68.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Sun, 23 Jul 2000 12:25:34 -0700 From: "David Schwartz" To: "Jeroen C. van Gelderen" Cc: "Mark Murray" , Subject: RE: randomdev entropy gathering is really weak Date: Sun, 23 Jul 2000 12:26:07 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <397B3C78.1C16D34A@vangelderen.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 5. Yarrow was designed as a better replacement for most any > PRNG by a couple of bright cryptographers. Can you do > better than that? Nope, I agree. Ignore my previous objections. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 12:51:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id 494F637B624; Sun, 23 Jul 2000 12:51:49 -0700 (PDT) (envelope-from trevor@jpj.net) Received: from localhost (trevor@localhost) by blues.jpj.net (right/backatcha) with ESMTP id e6NJpkJ25641; Sun, 23 Jul 2000 15:51:46 -0400 (EDT) Date: Sun, 23 Jul 2000 15:51:46 -0400 (EDT) From: Trevor Johnson To: Kris Kennaway Cc: rosti@surfree.net.il, current@FreeBSD.ORG Subject: Re: Netscape 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 > > Are the fixed in Netscape 4.74 bugs not critical for release? > > Who knows? I don't know of any changelog for Netscape. The release notes are at http://home.netscape.com/eng/mozilla/4.7/relnotes/unix-4.74.html#whatnew . The only change that looks like it applies to us is a new feature to delete all your e-mail when exiting the program. I haven't tried it, but it seems to me that making an alias like alias netscape='/usr/local/bin/netscape && rm -rf ~/nsmail/*' or putting something similar in your .logout would achieve the same thing. -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 12:52:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from veldy.net (veldy-host201.dsl.visi.com [208.42.48.201]) by hub.freebsd.org (Postfix) with ESMTP id 545B137B624 for ; Sun, 23 Jul 2000 12:52:46 -0700 (PDT) (envelope-from veldy@fuggle.veldy.net) Received: by veldy.net (Postfix, from userid 1000) id 8FDCC8C3A; Sun, 23 Jul 2000 14:54:11 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by veldy.net (Postfix) with ESMTP id 8DE6D1D; Sun, 23 Jul 2000 14:54:11 -0500 (CDT) Date: Sun, 23 Jul 2000 14:54:11 -0500 (CDT) From: "Thomas T. Veldhouse" To: Daniel Baker Cc: freebsd-current@freebsd.org Subject: Re: 4.1-RC panic when loading dnetc (distributed.net client) In-Reply-To: <20000723131725.A44906@cuckoo.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, 23 Jul 2000, Daniel Baker wrote: > Thomas, > > Just use "boot -s" to boot into single user mode so that you can disable > the dnetc.sh script before you get into multiuser mode when all the rc.d > scripts are executed. > > How long has the machine that you're using been alive for? Has it had > stability problems in the past? Is it under heavy load? Are the CPU fan(s) > running? > Running since Friday. This machine has had FreeBSD 4.0-CURRENT in the past, as well as STABLE. It has also had Linux running on it (various distros). None of the above have given problems with dnetc in the past. The machine is not under any load. It is my development machine and the error occurs during boot. All the fans are running. It is a Compaq Presario 5868 (AMD Athlon 600 with the AMD751/VIA686a chipsets). 128MB RAM SDRAM 100. Windows 2000 also runs on this machine and exhibits no problems - other than the expected :) The machine had been running fine since Friday (I upgraded world to 4.1 RC-x). I share dnetc buffer files on a FAT32 partition so that my Windows2000 dnetc client can use the same files (I don't know if this could make a difference). I have another machine running dnetc and it seems to work fine (4.1-RC 1 from ~ 7-17). I was not able to get into FreeBSD to find out if anything else was amis. The CD I burned from a snapshot would not allow me to get to a prompt to boot into single user mode. Something is wrong with that days image. The image is from around July 7th. I had edited my /boot/loader.rc to automatically boot without the prompt - so I can not enter single user mode that way either. Perhaps I will download a more recent floppy set and see if I can get in with them. Tom Veldhouse veldy@veldy.net > Daniel > > -- > dbaker@distributed.net - Chief Operations Administrator - distributed.net > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 13:19: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 3F0FE37B8B3 for ; Sun, 23 Jul 2000 13:18:58 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA03949 for ; Sun, 23 Jul 2000 13:18:57 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 23 Jul 2000 13:18:57 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: Now make installworld is broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Current is a damned joke these days. With sources fetched at 10:00 PDT (17:00 GMT) today: blake# make installworld mkdir -p /tmp/install.232 for prog in [ awk cat chflags chown date echo egrep find grep install ln make makewhatis mv perl rm sed sh sysctl test true u name wc zic; do cp `which $prog` /tmp/install.232; done cd /local0/src; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/local0/src/i386/usr/libexec:/usr/obj/local0/src/i386/usr/bin LIBRARY_PATH=/usr/obj/local0/src/i386/usr/lib:/usr/obj/local0/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/local0/src/i386/usr/li bexec PERL5LIB=/usr/obj/local0/src/i386/usr/libdata/perl/5.6.0 PATH=/usr/obj/local0/src/i386/usr/sbin:/usr/obj/local0/src/i38 6/usr/bin:/usr/obj/local0/src/i386/usr/games:/tmp/install.232 make -f Makefile.inc1 reinstall -------------------------------------------------------------- >>> Making hierarchy -------------------------------------------------------------- cd /local0/src; make -f Makefile.inc1 hierarchy cd /local0/src/etc; make distrib-dirs mtree -deU -f /local0/src/etc/mtree/BSD.root.dist -p / mtree:No such file or directory *** Error code 1 John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa ^^^^^^^^^^^^^^ Current is making me feel very intelligent. :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 13:26:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id D315737B8B3 for ; Sun, 23 Jul 2000 13:26:06 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.9.3/8.9.3) with ESMTP id NAA42628; Sun, 23 Jul 2000 13:26:03 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (ssmail@localhost) by medusa.kfu.com (8.9.3/8.8.8) with ESMTP id NAA21130; Sun, 23 Jul 2000 13:26:03 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) X-Authentication-Warning: medusa.kfu.com: ssmail owned process doing -bs Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.9.3//ident-1.0) id NAA10962; Sun, 23 Jul 2000 13:26:02 -0700 (PDT) Message-ID: <397B54DA.C55EBAE1@quack.kfu.com> Date: Sun, 23 Jul 2000 13:26:02 -0700 From: Nick Sayer X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Tatsumi Hosokawa Cc: freebsd-current@freebsd.org Subject: Re: DHCP client problem? References: <200007220022.RAA02194@medusa.kfu.com> <86ittyjtvd.wl@ringo.FromTo.Cc> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Reversing that patch fixes it. Since the source for this is in contrib, I presume we need to send this back to ISC rather than patch it in our tree? Tatsumi Hosokawa wrote: > > At Fri, 21 Jul 2000 17:22:15 -0700 (PDT), > Nick Sayer wrote: > > > > Something changed very recently in the dhcp client stuff that seems > > to have broke my -current machine's ability to be a dhcp client. > > > > The symptom is that I see > > > > ifconfig: netmask 255.255.255.224: bad value > > > > come out of the script invocation, and the ip address does not get > > set. > > My -current machine (cvsupped only a few hours ago) has the same > problem. > > > If I echo out the parameters and type in THE EXACT SAME command line > > myself, it works just fine. I suspect some sort of bizarre > > quoting conspiracy. :-) > > Maybe here? > (in > http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/isc-dhcp/client/scripts/freebsd.diff?r1=1.11&r2=1.12) > > - if [ x$old_ip_address = x ] || [ x$old_ip_address != x$new_ip_address ] || \ > - [ x$reason = xBOUND ] || [ x$reason = xREBOOT ]; then > - ifconfig $interface inet $new_ip_address $new_netmask_arg \ > - $new_broadcast_arg $medium > + if [ "x$old_ip_address" = "x" ] || [ "x$old_ip_address" != "x$new_ip_address" ] || \ > + [ "x$reason" = "xBOUND" ] || [ "x$reason" = "xREBOOT" ]; then > + ifconfig "$interface" inet "$new_ip_address" "$new_netmask_arg" \ > + "$new_broadcast_arg" "$medium" > > --------------------------- > Tatsumi Hosokawa > hosokawa@itc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 13:30:31 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 929BC37B7DC; Sun, 23 Jul 2000 13:30:24 -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 WAA01440; Sun, 23 Jul 2000 22:30:25 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007232030.WAA01440@grimreaper.grondar.za> To: Kris Kennaway Cc: Sam Xie , freebsd-current@FreeBSD.ORG Subject: Re: trafshow doesn't work? References: In-Reply-To: ; from Kris Kennaway "Wed, 19 Jul 2000 14:06:48 MST." Date: Sun, 23 Jul 2000 22:30:24 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Fallout from the malloc.conf changes. tcpdump has the same bug. Could this break dhclient as well? 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 23 13:43: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from monk.via.net (monk.via.net [209.81.2.10]) by hub.freebsd.org (Postfix) with ESMTP id 38E8F37B8E7 for ; Sun, 23 Jul 2000 13:43:01 -0700 (PDT) (envelope-from joe@via.net) Received: (from joe@localhost) by monk.via.net (8.9.3/8.9.3) id NAA36306; Sun, 23 Jul 2000 13:43:41 -0700 (PDT) (envelope-from joe) From: Joe McGuckin Message-Id: <200007232043.NAA36306@monk.via.net> Date: Sun, 23 Jul 2000 13:43:41 -0700 (PDT) To: james@targetnet.com Cc: freebsd-current@FreeBSD.ORG Subject: Re[2]: Journaling Filesystem ? In-Reply-To: <20000722151719.B99818@targetnet.com> X-Mailer: Ishmail 1.3.1-970608-bsdi MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The big win with a journaling FS is when you have to reboot the system. With Softupdates, you still have to fsck. On a large FS (say half a terabyte) that can take hours. With a JFS, you simply play the log forward and continue. -joe -- Joe McGuckin ViaNet Communications 994 San Antonio Road Palo Alto, CA 94303 Phone: 650-969-2203 Cell: 650-207-0372 Fax: 650-969-2124 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 14:23:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 91AE937B624 for ; Sun, 23 Jul 2000 14:23:10 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA04150 for ; Sun, 23 Jul 2000 14:23:09 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA02110; Sun, 23 Jul 2000 14:23:09 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 23 Jul 2000 14:23:09 -0700 (PDT) Message-Id: <200007232123.OAA02110@vashon.polstra.com> To: current@freebsd.org Subject: Re: Now make installworld is broken In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , John Polstra wrote: > Current is a damned joke these days. With sources fetched at 10:00 > PDT (17:00 GMT) today: > > blake# make installworld > mkdir -p /tmp/install.232 > for prog in [ awk cat chflags chown date echo egrep find grep install ln make > makewhatis mv perl rm sed sh sysctl test true u > name wc zic; do cp `which $prog` /tmp/install.232; done > cd /local0/src; MAKEOBJDIRPREFIX=/usr/obj > COMPILER_PATH=/usr/obj/local0/src/i386/usr/libexec:/usr/obj/local0/src/i386/usr/bin > LIBRARY_PATH=/usr/obj/local0/src/i386/usr/lib:/usr/obj/local0/src/i386/usr/lib > OBJFORMAT_PATH=/usr/obj/local0/src/i386/usr/li > bexec PERL5LIB=/usr/obj/local0/src/i386/usr/libdata/perl/5.6.0 > PATH=/usr/obj/local0/src/i386/usr/sbin:/usr/obj/local0/src/i38 > 6/usr/bin:/usr/obj/local0/src/i386/usr/games:/tmp/install.232 make -f Makefile.inc1 > reinstall > -------------------------------------------------------------- > >>> Making hierarchy > -------------------------------------------------------------- > cd /local0/src; make -f Makefile.inc1 hierarchy > cd /local0/src/etc; make distrib-dirs > mtree -deU -f /local0/src/etc/mtree/BSD.root.dist -p / > mtree:No such file or directory > *** Error code 1 I believe the problem is as follows. In revision 1.155 of src/Makefile.inc1, mtree was moved from cross-tools to bootstrap-tools. Then in revision 1.161 it was removed from bootstrap-tools but was not put it back into cross-tools. The appended patch will probably fix it, but I'm not going to commit it until it has been tested with a FULL make world AS I WISH A FEW OTHER COMMITTERS WOULD LEARN TO DO. If any committer gets it tested before I do, please feel free to commit it. John Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.162 diff -u -r1.162 Makefile.inc1 --- Makefile.inc1 2000/07/23 17:38:32 1.162 +++ Makefile.inc1 2000/07/23 21:15:16 @@ -579,7 +579,8 @@ cross-tools: .for _tool in ${_aout_tools} ${_btxld} ${_elf2exe} usr.bin/genassym \ - usr.bin/gensetdefs gnu/usr.bin/binutils usr.bin/objformat gnu/usr.bin/cc + usr.bin/gensetdefs gnu/usr.bin/binutils usr.bin/objformat gnu/usr.bin/cc \ + usr.sbin/mtree cd ${.CURDIR}/${_tool}; \ ${MAKE} obj; \ ${MAKE} depend; \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 14:32:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 3FD8437B8E7 for ; Sun, 23 Jul 2000 14:32:46 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 5BB7E2F; Sun, 23 Jul 2000 14:32:45 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id OAA11523; Sun, 23 Jul 2000 14:32:44 -0700 (PDT) Message-ID: <397B647C.45E2464E@cup.hp.com> Date: Sun, 23 Jul 2000 14:32:44 -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: John Polstra Cc: current@FreeBSD.ORG Subject: Re: Now make installworld is broken References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > -------------------------------------------------------------- > >>> Making hierarchy > -------------------------------------------------------------- > cd /local0/src; make -f Makefile.inc1 hierarchy > cd /local0/src/etc; make distrib-dirs > mtree -deU -f /local0/src/etc/mtree/BSD.root.dist -p / > mtree:No such file or directory > *** Error code 1 My bad. I removed mtree from the bootstrap-tools after reverting the use of the -L switch. I forgot to re-add mtree to the list of saved binaries during installworld. It's fixed now (famous last words)... -- 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 Sun Jul 23 15:28:12 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 3E63437B9E1; Sun, 23 Jul 2000 15:28:08 -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 PAA66902; Sun, 23 Jul 2000 15:28:07 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Jul 2000 15:28:07 -0700 (PDT) From: Kris Kennaway To: Joe McGuckin Cc: james@targetnet.com, freebsd-current@FreeBSD.ORG Subject: Re: Re[2]: Journaling Filesystem ? In-Reply-To: <200007232043.NAA36306@monk.via.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Jul 2000, Joe McGuckin wrote: > The big win with a journaling FS is when you have to reboot the system. > > With Softupdates, you still have to fsck. On a large FS (say half a > terabyte) that can take hours. No you don't. Your filesystem will be in a consistent state except for blocks which are marked used but are not, so you can fsck in the background at the expense of not having all of your free space available at startup. Having said that, I don't know that this procedure has been well tested in practise, so you're advised to use caution when testing it :-) 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 23 15:44:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 8FD3137B9A4; Sun, 23 Jul 2000 15:44:09 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA17668; Sun, 23 Jul 2000 15:53:40 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007232253.PAA17668@mass.osd.bsdi.com> Date: Sun, 23 Jul 2000 15:53:40 -0700 From: Mike Smith Subject: Driver for Adaptec/Dell/HP PCI:SCSI RAID adapters available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- Blind-Carbon-Copy X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: Driver for Adaptec/Dell/HP PCI:SCSI RAID adapters available Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Jul 2000 15:53:40 -0700 From: Mike Smith The first BETA version of the 'aac' driver for the Adaptec AAC-364 'Jalapeno' and AAC-3642 'Jalapeno II' RAID adapters is available from http://people.freebsd.org/~msmith/RAID/index.html#adaptec These adapters are OEMed by Dell as the PERC 2/QC and by HP as the HP NetRAID-4m. The driver has been tested on FreeBSD 5.0-CURRENT, but is known to build and should function just fine on 4.0-STABLE as well. Testers are encouraged to contact me for assistance, or to report on progress. Thanks go to BSDi for funding the development of this driver, and Adaptec for supplying me with a profusion of sample adapters and the source for their Linux driver to work from. Particular thanks to Justin Gibbs for finding the right person at Adaptec to make all this happen. - -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] ------- End of Blind-Carbon-Copy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 15:53:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id C667D37BADB; Sun, 23 Jul 2000 15:53:24 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA55084; Sun, 23 Jul 2000 18:53:29 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Sun, 23 Jul 2000 18:53:29 -0400 (EDT) From: Adam To: Trevor Johnson Cc: Kris Kennaway , rosti@surfree.net.il, current@FreeBSD.ORG Subject: Re: Netscape 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, 23 Jul 2000, Trevor Johnson wrote: >> > Are the fixed in Netscape 4.74 bugs not critical for release? >> >> Who knows? I don't know of any changelog for Netscape. > >The release notes are at >http://home.netscape.com/eng/mozilla/4.7/relnotes/unix-4.74.html#whatnew . >The only change that looks like it applies to us is a new feature to >delete all your e-mail when exiting the program. I haven't tried it, but >it seems to me that making an alias like > > alias netscape='/usr/local/bin/netscape && rm -rf ~/nsmail/*' > >or putting something similar in your .logout would achieve the same thing. If you are talking about Expunging, I believe to netscape that means it actually goes through and deletes the emails that you have deleted... (uhh..) When I used to use netscape for my email, netscape wouldn't release hard disk space when you delete emails until you empty trash *and* run expunge. Why deleting from trash doesn't do it, I don't know, but netscape got to be too buggy for me to use for an email client about a year ago. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 16: 5:20 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 0B51437BBD8 for ; Sun, 23 Jul 2000 16:05:05 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115291>; Mon, 24 Jul 2000 09:04:44 +1000 Content-return: prohibited Date: Mon, 24 Jul 2000 08:37:55 +1000 From: Peter Jeremy Subject: Re: kernel compile failure without -O option In-reply-to: <200007200231.TAA15177@vashon.polstra.com>; from jdp@polstra.com on Wed, Jul 19, 2000 at 07:31:12PM -0700 To: John Polstra Cc: hm@hcs.de, current@FreeBSD.ORG, bde@zeta.org.au Message-Id: <00Jul24.090444est.115291@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: multipart/mixed; boundary="3MwIy2ne0vdjdPXF" References: <20000719144614.7FE52483D@hcswork.hcs.de> <200007200231.TAA15177@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii On 2000-Jul-19 19:31:12 -0700, John Polstra wrote: >In article <20000719144614.7FE52483D@hcswork.hcs.de>, >Hellmuth Michaelis wrote: >> >> In the process of tracing down the problem of the kernel panic when booting >> a kernel with pcvt enabled, i tried to compile a kernel without the -O >> option to gcc and got this compile failure (sources from 18.7.2000 9:00 MET): >> >> cc -c -pipe -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 >> -fomit-frame-pointer ../../i386/i386/atomic.c >> In file included from ../../i386/i386/atomic.c:47: >> machine/atomic.h: In function `atomic_set_char': >> machine/atomic.h:106: inconsistent operand constraints in an `asm' >> machine/atomic.h: In function `atomic_clear_char': >> machine/atomic.h:107: inconsistent operand constraints in an `asm' >[...] > >I have seen that same problem recently in a slightly different >context. After staring at the code for a very long time, I could >only conclude that the problem was a bug in gcc. Last year I did some testing of atomic.h with a variety of gcc versions (and, following a prod from bde, at a variety of optimisation levels). At the time, I had great difficulty finding a set of constraints that would work with both gcc 2.7.2 and egcs, with and without optimisation. Attached is a patch to /sys/i386/include/atomic.h,v 1.11 that I believe solves the problem. This is an adaption of what I did last year, to include some of Bruce's comments. At this stage, I've only checked it against gcc version 2.95.2 19991024 (release) - at it appears in 4.0 and the latest -current, with -O0, -O1 and -O2. An earlier version[1] worked with 2.7.2, 2.8.1 and ecgs 1.?. I hope to be able to check it on gcc 2.7.2 and maybe gcc 2.8.1 tonight. Note that in theory, gcc 2.7.2 needs a second read-only argument with a "0" constraint. In practice, this doesn't seem to be necessary since the write-only argument is volatile memory and therefore the compiler can't optimize out any preceeding read. This shouldn't be required for later compiler versions since the first argument is explicitly read-write. [1] This was sent to Bruce early last October. The changes since then are: - Correct `char' case to specify "q" constraint - Cast result of not (~) to ensure correct operand type. - Specify `w' in `short' case to correctly print the 16-bit register. Peter --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="atomic.patch" --- /3.0/cvs/src/sys/i386/include/atomic.h Thu May 11 01:27:24 2000 +++ atomic.h Mon Jul 24 08:02:16 2000 @@ -62,7 +62,7 @@ * This allows kernel modules to be portable between UP and SMP systems. */ #if defined(KLD_MODULE) -#define ATOMIC_ASM(NAME, TYPE, OP, V) \ +#define ATOMIC_ASM(NAME, TYPE, OP, V, CLASS) \ extern void atomic_##NAME##_##TYPE(volatile u_##TYPE *p, u_##TYPE v); #else /* !KLD_MODULE */ @@ -75,77 +75,61 @@ /* * The assembly is volatilized to demark potential before-and-after side * effects if an interrupt or SMP collision were to occur. + * + * GCC 2.8 and later (including EGCS) support read/write operands + * using '+' as a constraint modifier. + * + * Earlier versions of gcc don't allow the '+' and recommend the use + * of separate, matching read-only and write-only operands. + * Unfortunately, this doesn't appear to work in all cases. On + * the assumption that the memory operand is always volatile, it + * seems safe to tell gcc that it is write-only. The `volatile' + * attribute on the memory operand prohibits any optimization + * away of the reference. + * + * The constraint class for the read operand is passed as a parameter + * to the macro because it needs to be different in the char case. + * (In theory, it should also be different in the short case, but + * gcc doesn't have any constraint classes to specify 16-bit registers). + * + * Note that gcc doesn't support string glueing for the constraint + * expressions, so the common "m" or "i" bits cannot be pulled out. */ -#if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ > 9) -/* egcs 1.1.2+ version */ -#define ATOMIC_ASM(NAME, TYPE, OP, V) \ +#if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 8) +#define ATOMIC_ASM(NAME, TYPE, OP, V, CLASS) \ static __inline void \ atomic_##NAME##_##TYPE(volatile u_##TYPE *p, u_##TYPE v)\ { \ - __asm __volatile(MPLOCKED OP \ - : "=m" (*p) \ - : "0" (*p), "ir" (V)); \ + __asm __volatile(MPLOCKED OP : "+m" (*p) : CLASS (V) : "cc"); \ } - -#else -/* gcc <= 2.8 version */ -#define ATOMIC_ASM(NAME, TYPE, OP, V) \ +#else /* gcc < 2.8 version */ +#define ATOMIC_ASM(NAME, TYPE, OP, V, CLASS) \ static __inline void \ atomic_##NAME##_##TYPE(volatile u_##TYPE *p, u_##TYPE v)\ { \ - __asm __volatile(MPLOCKED OP \ - : "=m" (*p) \ - : "ir" (V)); \ + __asm __volatile(MPLOCKED OP : "=m" (*p) : CLASS (V) : "cc"); \ } #endif #endif /* KLD_MODULE */ -#if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ > 9) - -/* egcs 1.1.2+ version */ -ATOMIC_ASM(set, char, "orb %b2,%0", v) -ATOMIC_ASM(clear, char, "andb %b2,%0", ~v) -ATOMIC_ASM(add, char, "addb %b2,%0", v) -ATOMIC_ASM(subtract, char, "subb %b2,%0", v) - -ATOMIC_ASM(set, short, "orw %w2,%0", v) -ATOMIC_ASM(clear, short, "andw %w2,%0", ~v) -ATOMIC_ASM(add, short, "addw %w2,%0", v) -ATOMIC_ASM(subtract, short, "subw %w2,%0", v) - -ATOMIC_ASM(set, int, "orl %2,%0", v) -ATOMIC_ASM(clear, int, "andl %2,%0", ~v) -ATOMIC_ASM(add, int, "addl %2,%0", v) -ATOMIC_ASM(subtract, int, "subl %2,%0", v) - -ATOMIC_ASM(set, long, "orl %2,%0", v) -ATOMIC_ASM(clear, long, "andl %2,%0", ~v) -ATOMIC_ASM(add, long, "addl %2,%0", v) -ATOMIC_ASM(subtract, long, "subl %2,%0", v) - -#else - -/* gcc <= 2.8 version */ -ATOMIC_ASM(set, char, "orb %1,%0", v) -ATOMIC_ASM(clear, char, "andb %1,%0", ~v) -ATOMIC_ASM(add, char, "addb %1,%0", v) -ATOMIC_ASM(subtract, char, "subb %1,%0", v) - -ATOMIC_ASM(set, short, "orw %1,%0", v) -ATOMIC_ASM(clear, short, "andw %1,%0", ~v) -ATOMIC_ASM(add, short, "addw %1,%0", v) -ATOMIC_ASM(subtract, short, "subw %1,%0", v) - -ATOMIC_ASM(set, int, "orl %1,%0", v) -ATOMIC_ASM(clear, int, "andl %1,%0", ~v) -ATOMIC_ASM(add, int, "addl %1,%0", v) -ATOMIC_ASM(subtract, int, "subl %1,%0", v) - -ATOMIC_ASM(set, long, "orl %1,%0", v) -ATOMIC_ASM(clear, long, "andl %1,%0", ~v) -ATOMIC_ASM(add, long, "addl %1,%0", v) -ATOMIC_ASM(subtract, long, "subl %1,%0", v) - -#endif +ATOMIC_ASM(set, char, "orb %1,%0", v, "iq") +ATOMIC_ASM(clear, char, "andb %1,%0", (char)~v, "iq") +ATOMIC_ASM(add, char, "addb %1,%0", v, "iq") +ATOMIC_ASM(subtract, char, "subb %1,%0", v, "iq") + +ATOMIC_ASM(set, short, "orw %w1,%0", v, "ir") +ATOMIC_ASM(clear, short, "andw %w1,%0", (short)~v, "ir") +ATOMIC_ASM(add, short, "addw %w1,%0", v, "ir") +ATOMIC_ASM(subtract, short, "subw %w1,%0", v, "ir") + +ATOMIC_ASM(set, int, "orl %1,%0", v, "ir") +ATOMIC_ASM(clear, int, "andl %1,%0", ~v, "ir") +ATOMIC_ASM(add, int, "addl %1,%0", v, "ir") +ATOMIC_ASM(subtract, int, "subl %1,%0", v, "ir") + +ATOMIC_ASM(set, long, "orl %1,%0", v, "ir") +ATOMIC_ASM(clear, long, "andl %1,%0", ~v, "ir") +ATOMIC_ASM(add, long, "addl %1,%0", v, "ir") +ATOMIC_ASM(subtract, long, "subl %1,%0", v, "ir") #endif /* ! _MACHINE_ATOMIC_H_ */ --3MwIy2ne0vdjdPXF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 16: 8: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom1-223.telepath.com [216.14.1.223]) by hub.freebsd.org (Postfix) with SMTP id 9887437BC38 for ; Sun, 23 Jul 2000 16:07:53 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 1637 invoked by uid 100); 23 Jul 2000 23:07:16 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14715.31396.10403.394414@guru.mired.org> Date: Sun, 23 Jul 2000 18:07:16 -0500 (CDT) To: current@freebsd.org Subject: ahc lockups in -current 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 It seems that the last changes to the ahc drivers (committed on the 18th) are causing my system to lock up. I'd check the aic7890 specific changes first, but that's just me. The problem is that when I start doing I/O to two drives, the system hangs. The SCSI controller and both drives(*) turn on their "I'm busy" LED, so I assume the scsi bus is hung. They OS is still there, but trying to do anything that touches the drives causes the process to lock up. I get no core dump and no messages to the console indicating any problems. With this version, I *do* get the following message at boot time that I didn't get before: (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. The system configuration is: Supermicro motherboard with two PII/Xeons and a aic7890 on it. The aic has BIOS version 2.01 on it. Attached to that are: su-2.04# camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 3 lun 0 (pass2,da2) at scbus0 target 4 lun 0 (pass3,cd0) at scbus0 target 5 lun 0 (pass4,cd1) at scbus0 target 6 lun 0 (pass5) Target 0 is the system disk: /, /var, /usr, swap and some scratch space. Target 1 is data: /home, more scratch space (/usr/obj lives there) and more swap. The SCSI bus is: AM12S(6) -- AIC(7) -- da(1) -- da(0) -- jazz(3) -- cd(4) -- cd(5) -- term plug I'm a bit leary of the external scanner, so I unplugged it, made sure the AIC had termination set properly, and rebooted single user. Mounted /usr read-only, mounted the scratch space on da1, and did a cp -r of /usr to the scratch space. The system locked up in the same state as described above. Trying the same test - except I left the scanner plugged in - with a kernel built with the old version of the ahc driver worked fine. In fact, building the world with /usr/src and /usr/obj on different disks has been working fine for a while now. I'm hoping to get some guidance from someone who's familiar with the code before I start digging into it. If more information would be useful (dmesg output? config file? other?), let me know. If there's somne specific testing to do - including, if needed, borrowing a 2940 and moving the drives to that to try things on - let me know. Thanx, ; Sun, 23 Jul 2000 16:49:55 -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 UAA21658 for current@freebsd.org; Sun, 23 Jul 2000 20:49:54 -0300 (ADT) From: Brandon Hume Message-Id: <200007232349.UAA21658@Den.BOFH.Halifax.NS.Ca> Subject: Re: ahc lockups in -current In-Reply-To: <14715.31396.10403.394414@guru.mired.org> from Mike Meyer at "Jul 23, 2000 6: 7:16 pm" To: current@freebsd.org Date: Sun, 23 Jul 2000 20:49:43 -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 > It seems that the last changes to the ahc drivers (committed on the > 18th) are causing my system to lock up. I'd check the aic7890 specific I just upgraded my system to the latest -current today, from a long hiatus... last time I did a world was July 3rd. I can no longer boot the system. I was beginning to sort through the boot floppies, to figure out when the changes were made that sunk me. Thanks for saving me the trouble. :) I'm booting off the onboard AIC7895 on a Tyan Thunder/100. I get the same error you do initially, followed by many, many SCSI bus resets, errors about lost devices, SCBs aborted, and the like. After a period, the system panics... not about being unable to mount the root fs like I expected, but about 'page fault in kernel mode' or something similar. (da0:ahc0:0:0:0): SCB 0x9 - timed out in Command phase, SEQADDR == 0xa0 (da0:ahc0:0:0:0): BDR message in message buffer (da0:ahc0:0:0:0): SCB 0x9 - timed out in Command phase, SEQADDR == 0x9f (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 4 SCBs aborted etc... Finally it ends with 'Fatal trap 12: page fault while in kernel mode' fault virtual address = 0x3c fault code = supervisor write, page not present The machine locks up hard at that, needing a power cycle. The SCSI activity light blazes. Sorry I can't cut'n'paste the errors to be more useful, I don't have a serial console. I'm copying them by hand as best I can (I'd appreciate being told a better method... :) ) -- Brandon Hume - hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 17:31:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.rdc1.sfba.home.com (mail2.rdc1.sfba.home.com [24.0.0.75]) by hub.freebsd.org (Postfix) with ESMTP id 1ECA237B9CA; Sun, 23 Jul 2000 17:31:36 -0700 (PDT) (envelope-from boshea@ricochet.net) Received: from beastie.localdomain ([24.19.158.41]) by mail2.rdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000724003135.BEUD6679.mail2.rdc1.sfba.home.com@beastie.localdomain>; Sun, 23 Jul 2000 17:31:35 -0700 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id RAA51002; Sun, 23 Jul 2000 17:31:24 -0700 (PDT) (envelope-from brian) Date: Sun, 23 Jul 2000 17:31:24 -0700 From: "Brian O'Shea" To: Kris Kennaway Cc: Joe McGuckin , james@targetnet.com, freebsd-current@FreeBSD.ORG Subject: Re: Re[2]: Journaling Filesystem ? Message-ID: <20000723173124.C351@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: Kris Kennaway , Joe McGuckin , james@targetnet.com, freebsd-current@FreeBSD.ORG References: <200007232043.NAA36306@monk.via.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Kris Kennaway on Sun, Jul 23, 2000 at 03:28:07PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 23, 2000 at 03:28:07PM -0700, Kris Kennaway wrote: > On Sun, 23 Jul 2000, Joe McGuckin wrote: > > > The big win with a journaling FS is when you have to reboot the system. > > > > With Softupdates, you still have to fsck. On a large FS (say half a > > terabyte) that can take hours. > > No you don't. Your filesystem will be in a consistent state except for > blocks which are marked used but are not, so you can fsck in the > background at the expense of not having all of your free space available > at startup. > > Having said that, I don't know that this procedure has been well tested in > practise, so you're advised to use caution when testing it :-) I didn't even know that background fsck was supported at all. I remember hearing Kirk talk about it as a future feature at FreeBSD CON last year, but I havn't heard anything about it since. How do you use it? Thanks, -brian p.s. Forgive me if this is well documented in -CURRENT. At the moment, the latest version of FreeBSD that I have available to me is 4.1-RC (cvsup from July 21) and I can't find any mention of it. -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 17:43:24 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 A4ACB37B59A; Sun, 23 Jul 2000 17:43:21 -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 RAA81190; Sun, 23 Jul 2000 17:43:20 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Jul 2000 17:43:20 -0700 (PDT) From: Kris Kennaway To: "Brian O'Shea" Cc: Joe McGuckin , james@targetnet.com, freebsd-current@FreeBSD.ORG Subject: Re: Re[2]: Journaling Filesystem ? In-Reply-To: <20000723173124.C351@beastie.localdomain> 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, 23 Jul 2000, Brian O'Shea wrote: > I didn't even know that background fsck was supported at all. I > remember hearing Kirk talk about it as a future feature at FreeBSD CON > last year, but I havn't heard anything about it since. How do you > use it? I've never tried it myself - maybe I am confused and it's just something "which should be easy now". Brian Feldman said he thinks it requires use of FFS snapshots (recently committed). I'll stop making unsubstantiated claims :-) 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 23 18: 4:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id D9A0437B50E for ; Sun, 23 Jul 2000 18:04:16 -0700 (PDT) (envelope-from null@pozo.com) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id SAA07703; Sun, 23 Jul 2000 18:04:15 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <4.3.2.7.2.20000723180020.00b56250@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 23 Jul 2000 18:04:15 -0700 To: Mike Meyer , current@FreeBSD.ORG From: Manfred Antar Subject: Re: ahc lockups in -current In-Reply-To: <14715.31396.10403.394414@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:07 PM 7/23/2000 -0500, Mike Meyer wrote: >It seems that the last changes to the ahc drivers (committed on the >18th) are causing my system to lock up. I'd check the aic7890 specific >changes first, but that's just me. > >The problem is that when I start doing I/O to two drives, the system >hangs. The SCSI controller and both drives(*) turn on their "I'm busy" >LED, so I assume the scsi bus is hung. They OS is still there, but >trying to do anything that touches the drives causes the process to >lock up. I get no core dump and no messages to the console indicating >any problems. > >With this version, I *do* get the following message at boot time that >I didn't get before: > > (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. > >The system configuration is: I get the same hang when doing a dump to an Exabyte 8505 connected to on board aic7880 My disks are hooked up to an internal DPT Raid controller and no problem there. Any time I try to access the tape drive it panics. Sorry I don't have the panic message as I'm running this machine headless at the moment. Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 18: 4: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 9FEB837BBF5; Sun, 23 Jul 2000 18:04:50 -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 SAA82763; Sun, 23 Jul 2000 18:04:50 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Jul 2000 18:04:50 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007231201.OAA00883@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, 23 Jul 2000, Mark Murray wrote: > > There are two other models which rate "pretty well-designed" in the Yarrow > > paper: the cryptlib and PGP PRNGs. I don't know what their properties are > > right now (the cryptlib one is described in the paper on PRNG > > cryptanalysis). > > Do you have copies of the articles concerned? I'd surely appreciate > a photocopy of the relevant pages if you don't mind! :-) The paper I was referring to was: http://www.counterpane.com/pseudorandom_number.html Cryptlib is described here: http://www.cs.auckland.ac.nz/~pgut001/cryptlib/ > > Well, a simple scheme which doesn't seem to suffer from any of the > > vulnerabilities discussed in the schneier papers is to accumulate entropy > > in a pool, and only return output when the pool is full. i.e. the PRNG > > would either block or return 0 bytes of data, or a full pool's worth. > > Hmm. Timing attacks? Known-input attacks? Inasmuch as the hash function has no timing attacks (data-dependent code paths, etc) I don't see a weakness there. Chosen input attacks can be mitigated by using a hash function which provides strong mixing (e.g. SHA1), so there is no correlation between partially-known input and output. Yarrow of course takes it a step further by using a very heavy mixing function to regenerate the key, although it seems to me from the design rationale that this is to remove correlations between the Yarrow key before and after reseeding, which doesn't affect an unkeyed PRNG which doesnt maintain state. > > > Will you relent a step or two if I can get the entropy harvesting _rate_ > > > high enough? :-) > > > > If we get the entropy pools filling fast enough that the reseed is > > triggering close to every 256 bits of output then it becomes much less of > > a concern (but it's still there, because reseeding happens asynchronously > > with respect to PRNG output). However I think that in practice this will > > be too heavy on the CPU (unless we weaken the reseed operation) and make > > dd if=/dev/urandom of=/dev/null a very effective local user DoS :-( > > The dd if=/dev/urandom of=/dev/null is _already_ a doozy of a dos. Likewise > a fork-bomb, a /tmp-filler, likewise a whole bunch of things much worse. > Heck, you can hurt your system with cat /dev/zero > /dev/null. Well, all of the others can be mitigated by resource limits. It's something which needs to be revisited. > Asynchonous reseeding _improves_ the situation; the attacker cannot force > it to any degree of accuracy, and if he has the odds stacked heavily against > him that each 256-bits of output will have an associated reseed, it makes > his job pretty damn difficult. What I meant with that point is that the user may get, say an extra few hundred bits out of it with no new entropy before the scheduled reseed task kicks in. 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 23 18:25:36 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 77B3937B6CE; Sun, 23 Jul 2000 18:25:34 -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 SAA85568; Sun, 23 Jul 2000 18:25:34 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Jul 2000 18:25:34 -0700 (PDT) From: Kris Kennaway To: "Jeroen C. van Gelderen" Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <397B4090.6A15442E@vangelderen.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, 23 Jul 2000, Jeroen C. van Gelderen wrote: > > Well, a simple scheme which doesn't seem to suffer from any of the > > vulnerabilities discussed in the schneier papers is to accumulate entropy > > in a pool, and only return output when the pool is full. i.e. the PRNG > > would either block or return 0 bytes of data, or a full pool's worth. > > And you can make Yarrow do just that. Not very practical but > you can do it. You effectively set Pg to 1/(2^(k/3)). Oh, I missed this - thanks. It does introduce an extra overhead, namely applying a generator gate with every output (since n < k and Pg < 1) and then the full reseed with every k bits of output. ITYM Pg = k 2^(-k/3) though - you want a maximum k bits of output, not 1. I'm not sure if the current implementation will let you do this (since Pg < 1 here). > Reseeds do not *have* to happen asynchronously as pointed out > above. Yeah, but they do in the current implementation (AFAICT). 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 23 18:43:32 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 8D9E737B843 for ; Sun, 23 Jul 2000 18:43:28 -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 VAA98468; Sun, 23 Jul 2000 21:43:25 -0400 (EDT) (envelope-from wollman) Date: Sun, 23 Jul 2000 21:43:25 -0400 (EDT) From: Garrett Wollman Message-Id: <200007240143.VAA98468@khavrinen.lcs.mit.edu> To: Joe McGuckin Cc: james@targetnet.com, freebsd-current@FreeBSD.ORG Subject: Re[2]: Journaling Filesystem ? In-Reply-To: <200007232043.NAA36306@monk.via.net> References: <20000722151719.B99818@targetnet.com> <200007232043.NAA36306@monk.via.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > With Softupdates, you still have to fsck. On a large FS (say half a > terabyte) that can take hours. No you don't. Please read the paper. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 19: 3:28 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 85FA837B5A8; Sun, 23 Jul 2000 19:03:25 -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 WAA98524; Sun, 23 Jul 2000 22:03:23 -0400 (EDT) (envelope-from wollman) Date: Sun, 23 Jul 2000 22:03:23 -0400 (EDT) From: Garrett Wollman Message-Id: <200007240203.WAA98524@khavrinen.lcs.mit.edu> To: boshea@ricochet.net Cc: Kris Kennaway , Joe McGuckin , james@targetnet.com, freebsd-current@FreeBSD.ORG Subject: Re: Re[2]: Journaling Filesystem ? In-Reply-To: <20000723173124.C351@beastie.localdomain> References: <200007232043.NAA36306@monk.via.net> <20000723173124.C351@beastie.localdomain> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I didn't even know that background fsck was supported at all. I > remember hearing Kirk talk about it as a future feature at FreeBSD CON > last year, but I havn't heard anything about it since. How do you > use it? It is not quite there yet. It requires the snapshot code, which just recently made its way into the tree, and some new system calls to inform the filesystem that block X is actually free. However, this doesn't change the fact that fsck is not required in order to ensure correct operation after a crash. Depending on your access patterns, the block and inode leakage may be small enough to not matter. -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 23 22: 0: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 1397F37B9ED; Sun, 23 Jul 2000 21:59:08 -0700 (PDT) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (tanimura@localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-rina.r-0.1-11.01.2000) with ESMTP/IPv4 id NAA94685; Mon, 24 Jul 2000 13:58:48 +0900 (JST) Date: Mon, 24 Jul 2000 13:58:47 +0900 Message-ID: <14715.52487.753460.86952F@rina> From: Seigo Tanimura To: nsayer@quack.kfu.com Cc: hosokawa@itc.keio.ac.jp, obrien@FreeBSD.org, freebsd-current@freebsd.org Subject: Re: DHCP client problem? In-Reply-To: In your message of "Sun, 23 Jul 2000 13:26:02 -0700" <397B54DA.C55EBAE1@quack.kfu.com> References: <200007220022.RAA02194@medusa.kfu.com> <86ittyjtvd.wl@ringo.FromTo.Cc> <397B54DA.C55EBAE1@quack.kfu.com> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Jul 2000 13:26:02 -0700, Nick Sayer said: Nick> Reversing that patch fixes it. Since the source for this is in contrib, Nick> I presume we Nick> need to send this back to ISC rather than patch it in our tree? Nick> Tatsumi Hosokawa wrote: (snip) >> - if [ x$old_ip_address = x ] || [ x$old_ip_address != x$new_ip_address ] || \ >> - [ x$reason = xBOUND ] || [ x$reason = xREBOOT ]; then >> - ifconfig $interface inet $new_ip_address $new_netmask_arg \ >> - $new_broadcast_arg $medium >> + if [ "x$old_ip_address" = "x" ] || [ "x$old_ip_address" != "x$new_ip_address" ] || \ >> + [ "x$reason" = "xBOUND" ] || [ "x$reason" = "xREBOOT" ]; then >> + ifconfig "$interface" inet "$new_ip_address" "$new_netmask_arg" \ >> + "$new_broadcast_arg" "$medium" Did you see this log? On Thu, 20 Jul 2000 02:53:11 -0700 (PDT), "David E. O'Brien" said: David> obrien 2000/07/20 02:53:11 PDT David> Modified files: David> contrib/isc-dhcp/client/scripts freebsd David> Log: David> safe shell quoting David> Obtained from: OpenBSD (rev 1.6) And I have already suggested the following fix. On Sun, 23 Jul 2000 18:53:55 +0900, Seigo Tanimura said: Seigo> 1. Seigo> This breaks ifconfig(8) in dhclient-script(8) because our ifconfig(8) Seigo> does not support both a parameter name and its argument to be in a Seigo> single argument. Seigo> What we need to do against dhclient-script(8) to prevent executing Seigo> arbitrary commands include: Seigo> - quoting the arguments from dhclient(8), and Seigo> - intializing the internal variables. Seigo> It should be a good idea to quote each argument from dhclient(8), Seigo> followed by substituting the argument to an internal variable in a way Seigo> like this: Seigo> new_netmask_arg="netmask \"$new_subnet_mask\"" Seigo> Then we do not have to quote all of the variables in dhclient-script(8). Seigo> 2. Seigo> An argument of "" is passed to ifconfig(8) if the value of $medium is Seigo> empty, making ifconfig(8) confused. This is because certain ethernet Seigo> card drivers including ed(4) do not support configuring media Seigo> types. Fortunately, the fix proposed in 1 allows us once again to Seigo> remove quotations around the arguments of ifconfig(8). I wonder if ifconfig(8) of OpenBSD supports providing both the name of a parameter and its value in a single argument, and an ampty argument... (eg ifconfig ed1 inet xxx.xxx.xxx.xxx "netmask yyy.yyy.yyy.yyy" "") -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 23 23: 3:10 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 725A737BA2E; Sun, 23 Jul 2000 23:03:02 -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 IAA03449; Mon, 24 Jul 2000 08:03:02 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007240603.IAA03449@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, 23 Jul 2000 18:04:50 MST." Date: Mon, 24 Jul 2000 08:03:02 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > http://www.counterpane.com/pseudorandom_number.html > > Cryptlib is described here: > > http://www.cs.auckland.ac.nz/~pgut001/cryptlib/ Thanks! > > Asynchonous reseeding _improves_ the situation; the attacker cannot force > > it to any degree of accuracy, and if he has the odds stacked heavily against > > him that each 256-bits of output will have an associated reseed, it makes > > his job pretty damn difficult. > > What I meant with that point is that the user may get, say an extra few > hundred bits out of it with no new entropy before the scheduled reseed > task kicks in. How does he know which bits are which? His analysis task just got a whole lot more difficult. 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 24 1: 3: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from surfree.net.il (mail.surfree.net.il [212.3.192.12]) by hub.freebsd.org (Postfix) with SMTP id 38DEA37BC53 for ; Mon, 24 Jul 2000 01:02:58 -0700 (PDT) (envelope-from rosti@surfree.net.il) Received: From [surfree.net.il 212.3.218.19] By SuperMail at surfree.net.il with SMTP; Mon, 24 Jul 2000 10:25:44 +0200 GMT Message-ID: <397BFE0D.AF04027F@surfree.net.il> Date: Mon, 24 Jul 2000 10:27:57 +0200 From: rosti@surfree.net.il X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Adam Cc: Trevor Johnson , Kris Kennaway , current@FreeBSD.ORG Subject: Re: Netscape References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adam wrote: > On Sun, 23 Jul 2000, Trevor Johnson wrote: > > >> > Are the fixed in Netscape 4.74 bugs not critical for release? > >> > >> Who knows? I don't know of any changelog for Netscape. > > > >The release notes are at > >http://home.netscape.com/eng/mozilla/4.7/relnotes/unix-4.74.html#whatnew . > >The only change that looks like it applies to us is a new feature to > >delete all your e-mail when exiting the program. I haven't tried it, but > >it seems to me that making an alias like > > > > alias netscape='/usr/local/bin/netscape && rm -rf ~/nsmail/*' > > > >or putting something similar in your .logout would achieve the same thing. > > If you are talking about Expunging, I believe to netscape that means > it actually goes through and deletes the emails that you have > deleted... (uhh..) When I used to use netscape for my email, netscape > wouldn't release hard disk space when you delete emails until you empty > trash *and* run expunge. Expunding does NOT do something like rm -rf ~/nsmail/*' but it compacts all of your local e-mail folders by _completly_ deleting already "notched" messages. Look on your ~/nsmail/ directory; you have there some files like inbox, sent, trash, etc. and you also have inbox.snm, sent.snm, trash.snm, etc. The *.snm files is a pointers' files; when you delete some locally saved message from inbox (for example) you actually only delet the pointer to this message from inbox.snm file not the message itself. If you don't want some day catch out that you don't have free space on your hard drive you need to do "Compact Folders" that deletes all such unpointered messages. In the last 4.74 version of Netscape Communicator you can do this automatically when you exit the program. > Why deleting from trash doesn't do it, I don't > know, but netscape got to be too buggy for me to use for an email client > about a year ago. The trash folder designed for undeleting locally saved and amiss deleted e-mail messages, it's just a backup folder not something else. By the way, if you do "Empty Trash on Local Mail" it automatically will do "Compact Folders" after it (in 4.73 version there was a bug, the "Compact Folders" didn't work). So when you "delete" some message from inbox (for example) it will just copy the message into the trash folder and delete the pointer to him from inbox.snm file. If you don't want the copy in a trash folder you can press and hold the [Shift] key when you delete any message. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 24 1:25: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.42.org (matrix.42.org [194.246.250.200]) by hub.freebsd.org (Postfix) with ESMTP id 4D11437BB20 for ; Mon, 24 Jul 2000 01:24:56 -0700 (PDT) (envelope-from sec@42.org) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.5) id KAA27975 (sender ); Mon, 24 Jul 2000 10:22:22 +0200 (CEST) Date: Mon, 24 Jul 2000 10:22:22 +0200 From: Stefan `Sec` Zehl To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000724102222.B27329@matrix.42.org> X-Current-Backlog: 500 messages References: <200007231253.OAA28448@matrix.42.org> <3661.964357594@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3661.964357594@critter.freebsd.dk>; from phk@critter.freebsd.dk on Sun, Jul 23, 2000 at 03:06:34PM +0200 I-love-doing-this: really X-Modeline: vim:set ts=8 sw=4 smarttab tw=72 si noic notitle: Accept-Languages: de, en X-URL: http://sec.42.org/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 23, 2000 at 03:06:34PM +0200, Poul-Henning Kamp wrote: > In message <200007231253.OAA28448@matrix.42.org>, Stefan `Sec` Zehl writes: > >With the current approach it has a 256bits key. This is, in my eyes, not > >good. Although yarrow is nice, It's suited for any kind of key > >generation. > > The first law of crypto clearly states: "Know what you're doing". > > There is no way around that law. > > We cannot load down FreeBSD with impossibly heavy computations to > cater for any and all conceiveable application of random numbers. But FreeBSD should provide a way to get truely random numbers when it asks for them. /dev/random was invented so the applications don't have to bother with entropy-gathering. I agree that yarrow is good, but we need some way to get really random numbers. Maybe call it /dev/rrandom. The way Kris describes it, it won't really use cpu time until it is read. CU, Sec -- > I even remember having a private exchange of messages with you about other > possible approaches to that problem. :-) Hopefully, these approaches involved slowly crushing of tender body parts. -- Liviu & Wietse about broken Mailers ~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 24 1:51:31 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 2C7FF37B5EE for ; Mon, 24 Jul 2000 01:51:27 -0700 (PDT) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13Gdx0-000PGA-00; Mon, 24 Jul 2000 10:51:02 +0200 Date: Mon, 24 Jul 2000 10:51:02 +0200 From: Neil Blakey-Milner To: Doug Barton Cc: "Viren R.Shah" , freebsd-current@freebsd.org Subject: Re: Locale issues on -current Message-ID: <20000724105102.A96976@mithrandr.moria.org> References: <14712.37803.399020.756017@vorpal.rstcorp.com> <397948EF.C1C7C396@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <397948EF.C1C7C396@gorean.org>; from DougB@gorean.org on Sat, Jul 22, 2000 at 12:10:39AM -0700 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 Sat 2000-07-22 (00:10), Doug Barton wrote: > > I installed a recent snapshot of -current (a week ago) and I keep > > getting the following warnings: > > > > [vshah@vorpal] /etc> perl > > perl: warning: Setting locale failed. > > perl: warning: Please check that your locale settings: > > LC_ALL = (unset), > > LC_CTYPE = "en_US", > > LANG = (unset) > > are supported and installed on your system. > > I get the same thing. It's LC_CTYPE that's causing the problem. I was half > thinking that it was something related to gnome, but I haven't worked very > hard to fix it. Unsetting that variable makes the warning go away, whether > that fixes the problem or not. Viren: Is that in an X session, possibly running gnome? I've had this too. Never have figured what it was about, but it happened only in X, where I use gnome. 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 Mon Jul 24 3:54:39 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 5812137B61B for ; Mon, 24 Jul 2000 03:54:36 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id DAA09834; Mon, 24 Jul 2000 03:50:43 -0700 (PDT) (envelope-from obrien) Date: Mon, 24 Jul 2000 03:50:43 -0700 From: "David O'Brien" To: Marcel Moolenaar Cc: freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure Message-ID: <20000724035043.B90901@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <397A16CE.E49EB0D@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <397A16CE.E49EB0D@cup.hp.com>; from marcel@cup.hp.com on Sat, Jul 22, 2000 at 02:49:02PM -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 Sat, Jul 22, 2000 at 02:49:02PM -0700, Marcel Moolenaar wrote: > Did we bump the libc version number when the strtofflags/fflagstostr > functions went in? Nope, the added functionality didn't change any of the existing interfaces, so it no longer meets our requirements for a shlib version bump. In the a.out days, we would have done a minor number bump. One of the assumptions in not needing a bump, is ``make world'' uses the right libraries to link the new source with. -- -- 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 24 3:56: 8 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 9EA7137B603 for ; Mon, 24 Jul 2000 03:56:05 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id DAA15612; Mon, 24 Jul 2000 03:54:27 -0700 (PDT) (envelope-from obrien) Date: Mon, 24 Jul 2000 03:54:26 -0700 From: "David O'Brien" To: Seigo Tanimura Cc: nsayer@quack.kfu.com, hosokawa@itc.keio.ac.jp, freebsd-current@freebsd.org Subject: Re: DHCP client problem? Message-ID: <20000724035426.C90901@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200007220022.RAA02194@medusa.kfu.com> <86ittyjtvd.wl@ringo.FromTo.Cc> <397B54DA.C55EBAE1@quack.kfu.com> <14715.52487.753460.86952F@rina> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14715.52487.753460.86952F@rina>; from tanimura@r.dl.itc.u-tokyo.ac.jp on Mon, Jul 24, 2000 at 01:58:47PM +0900 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 24, 2000 at 01:58:47PM +0900, Seigo Tanimura wrote: > Did you see this log? > On Thu, 20 Jul 2000 02:53:11 -0700 (PDT), > "David E. O'Brien" said: I'll take a look at this on Monday. Thanks! for the bug reports -- just what I wanted to hear before I thought about a MFC for this. -- -- 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 24 4:58:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 220A737B5DF for ; Mon, 24 Jul 2000 04:58:29 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1237 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Mon, 24 Jul 2000 13:58:27 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id B10FB483B; Mon, 24 Jul 2000 13:58:26 +0200 (METDST) Subject: pcvt works To: freebsd-current@freebsd.org (FreeBSD Current) Date: Mon, 24 Jul 2000 13:58:26 +0200 (METDST) Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 537 Message-Id: <20000724115826.B10FB483B@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Strange but true, i cvsupped a tree yesterday (and another on another machine today) and on both machines a pcvt-configured kernel now works again and does not panic any longer (same config files & hint files). hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 24 8:15: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from reliant.nielsenmedia.com (reliant.nielsenmedia.com [205.129.32.15]) by hub.freebsd.org (Postfix) with ESMTP id BB94437BBE7 for ; Mon, 24 Jul 2000 08:14:49 -0700 (PDT) (envelope-from David_W_Gray@tvratings.com) Received: from nmrusdunsxg0.nielsenmedia.com (nmrusdunsxg0.nielsenmedia.com [10.9.11.120]) by reliant.nielsenmedia.com (8.9.3/8.9.3) with ESMTP id LAA18639 for ; Mon, 24 Jul 2000 11:14:45 -0400 (EDT) Received: by nmrusdunsxg0.nielsenmedia.com with Internet Mail Service (5.5.2651.58) id <38BNV253>; Mon, 24 Jul 2000 11:14:45 -0400 Message-ID: <01D4D419B1A4D111A30400805FE65B13070ABF74@nmrusdunsx1.nielsenmedia.com> From: "Gray, David W." To: "'FreeBSD Current list'" Subject: Recent make world breakages Date: Mon, 24 Jul 2000 11:14:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2651.58) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not to exacerbate a sore subject, but... From what I'm seeing go by, the intention is that a current make world is supposed to work from -stable. OK, what about make release? The reason I am asking, is that I'm actually running current on a laptop, and for various reasons, its far easier to be able to load it from a cdrom. My build machine is a 4.0 release box, its the only one I have that's muscular enough to do the build. Since I've been tracking -current (the last couple of weeks or so, but I've been on this list for a year or so) I have been able to build world, but building the boot crunch dies compiling /bin/sh (there are intermediate files created by yacc and such that are built in the current directory, not where the source is.) Should this work? Is it germane that I don't build in /usr/, but over in /home/current, etc? Should this work? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 24 10:36: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 4961237BC18 for ; Mon, 24 Jul 2000 10:36:01 -0700 (PDT) (envelope-from asmodai@lucifer.ninth-circle.org) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id TAA41855; Mon, 24 Jul 2000 19:35:58 +0200 (CEST) (envelope-from asmodai) Date: Mon, 24 Jul 2000 19:35:58 +0200 From: Jeroen Ruigrok van der Werven To: current@FreeBSD.ORG Cc: jdp@polstra.com Subject: Re: buildworld failure Message-ID: <20000724193557.C41235@lucifer.bart.nl> References: <200007230510.WAA99344@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007230510.WAA99344@vashon.polstra.com>; from jdp@polstra.com on Sat, Jul 22, 2000 at 10:10:43PM -0700 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000723 07:15], John Polstra (jdp@polstra.com) wrote: >Some developers just aren't being careful enough. The biggest problem >is they don't restore their systems to a 100% pristine state before >they test. Think we could come up with a make cleanworld like target which does just that? 't Would be pretty helpful IMHO. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Truth is always exciting. Speak it, then. Life is boring without it... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 24 10:49:56 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 A8A5237B870 for ; Mon, 24 Jul 2000 10:49:47 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac10.wam.umd.edu (root@rac10.wam.umd.edu [128.8.10.150]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA27631 for ; Mon, 24 Jul 2000 13:49:34 -0400 (EDT) Received: from rac10.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac10.wam.umd.edu (8.9.3/8.9.3) with SMTP id NAA14091 for ; Mon, 24 Jul 2000 13:49:41 -0400 (EDT) Received: from localhost (culverk@localhost) by rac10.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA14087 for ; Mon, 24 Jul 2000 13:49:40 -0400 (EDT) X-Authentication-Warning: rac10.wam.umd.edu: culverk owned process doing -bs Date: Mon, 24 Jul 2000 13:49:40 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: patch for ds1 soundcard Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-964460980=:13577" 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. ---559023410-851401618-964460980=:13577 Content-Type: TEXT/PLAIN; charset=US-ASCII I found on my computer that a ds1 builtin soundcard of type 10 (found in the file) will not init correctly unless the same 400ms wait is applied to it that is applied to type 8 cards. I have included a patch to make this happen. The patch was created against a -STABLE from today, but should not be too hard to get into -CURRENT as it only modifies one line of code. ================================================================= | 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/| ================================================================= ---559023410-851401618-964460980=:13577 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="ds1.c.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="ds1.c.patch" SW5kZXg6IHN5cy9kZXYvc291bmQvcGNpL2RzMS5jDQo9PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09DQpSQ1MgZmlsZTogL2hvbWUvbmN2cy9zcmMvc3lzL2Rldi9z b3VuZC9wY2kvZHMxLmMsdg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjguMi4x DQpkaWZmIC1yMS44LjIuMSBkczEuYw0KMjk1YzI5NQ0KPCAJCWlmIChzYy0+ dHlwZSA9PSA4KQ0KLS0tDQo+IAkJaWYgKHNjLT50eXBlID09IDggfHwgc2Mt PnR5cGUgPT0gMTApDQo= ---559023410-851401618-964460980=:13577-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 24 11:48:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from assurance.rstcorp.com (rstcorp2.daf.concentric.net [216.112.242.2]) by hub.freebsd.org (Postfix) with ESMTP id 8F3C637BE83 for ; Mon, 24 Jul 2000 11:48:06 -0700 (PDT) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.10.1/8.10.1) id e6OIm0w01561; Mon, 24 Jul 2000 14:48:00 -0400 Received: from sandbox.rstcorp.com(10.1.30.2) by assurance.rstcorp.com via smap (V2.1+anti-relay+anti-spam) id xma001551; Mon, 24 Jul 00 14:47:39 -0400 Received: from vorpal (jabberwock.rstcorp.com [10.1.254.253]) by sandbox.rstcorp.com (8.9.3/8.9.3) with ESMTP id OAA12606; Mon, 24 Jul 2000 14:47:39 -0400 (EDT) Received: by vorpal (Postfix, from userid 93) id C2A4B6; Mon, 24 Jul 2000 14:47:38 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14716.36682.601114.318034@jabberwock.rstcorp.com> Date: Mon, 24 Jul 2000 14:47:38 -0400 (EDT) From: "Viren R.Shah" To: Neil Blakey-Milner Cc: Doug Barton , freebsd-current@freebsd.org Subject: Re: Locale issues on -current In-Reply-To: <20000724105102.A96976@mithrandr.moria.org> References: <14712.37803.399020.756017@vorpal.rstcorp.com> <397948EF.C1C7C396@gorean.org> <20000724105102.A96976@mithrandr.moria.org> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid Reply-To: "Viren R.Shah" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Neil" == Neil Blakey-Milner writes: Neil> On Sat 2000-07-22 (00:10), Doug Barton wrote: >> > I installed a recent snapshot of -current (a week ago) and I keep >> > getting the following warnings: >> > >> > [vshah@vorpal] /etc> perl >> > perl: warning: Setting locale failed. >> > perl: warning: Please check that your locale settings: >> > LC_ALL = (unset), >> > LC_CTYPE = "en_US", >> > LANG = (unset) >> > are supported and installed on your system. >> >> I get the same thing. It's LC_CTYPE that's causing the problem. I was half >> thinking that it was something related to gnome, but I haven't worked very >> hard to fix it. Unsetting that variable makes the warning go away, whether >> that fixes the problem or not. Neil> Viren: Is that in an X session, possibly running gnome? Neil> I've had this too. Never have figured what it was about, but it Neil> happened only in X, where I use gnome. Yes, it is gnome. And, as Doug suggested, it stops when you unset LC_CTYPE. I don't think it is actually doing anything other than irritating me. :-) Neil> Neil Thanks Viren -- Viren R. Shah, viren@rstcorp.com, http://www.rstcorp.com/~vshah/ `Beware the Jabberwock, my son! The jaws that bite, the claws that catch! Beware the Jubjub bird, and shun the frumious Bandersnatch!' -- Lewis Carroll (Jabberwocky) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 24 11:55: 2 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 90AC437BD00 for ; Mon, 24 Jul 2000 11:54: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 UAA72062; Mon, 24 Jul 2000 20:54:45 +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 UAA09459; Mon, 24 Jul 2000 20:54:29 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <009901bff5a0$a1c3cf00$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: "Jeroen Ruigrok van der Werven" , Cc: References: <200007230510.WAA99344@vashon.polstra.com> <20000724193557.C41235@lucifer.bart.nl> Subject: Re: buildworld failure Date: Mon, 24 Jul 2000 20:48:31 +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 > -On [20000723 07:15], John Polstra (jdp@polstra.com) wrote: > >Some developers just aren't being careful enough. The biggest problem > >is they don't restore their systems to a 100% pristine state before > >they test. > > Think we could come up with a make cleanworld like target which does > just that? > 't Would be pretty helpful IMHO. That would be pretty much like a fresh install from a snapshot. Or a backup/restore cycle. 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 24 11:56:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from reliant.nielsenmedia.com (reliant.nielsenmedia.com [205.129.32.15]) by hub.freebsd.org (Postfix) with ESMTP id C37FB37BBD6 for ; Mon, 24 Jul 2000 11:56:32 -0700 (PDT) (envelope-from David_W_Gray@tvratings.com) Received: from nmrusdunsxg0.nielsenmedia.com (nmrusdunsxg0.nielsenmedia.com [10.9.11.120]) by reliant.nielsenmedia.com (8.9.3/8.9.3) with ESMTP id OAA08915 for ; Mon, 24 Jul 2000 14:56:30 -0400 (EDT) Received: by nmrusdunsxg0.nielsenmedia.com with Internet Mail Service (5.5.2651.58) id <38BNVPGR>; Mon, 24 Jul 2000 14:56:29 -0400 Message-ID: <01D4D419B1A4D111A30400805FE65B13070ABF77@nmrusdunsx1.nielsenmedia.com> From: "Gray, David W." To: "'FreeBSD Current list'" Subject: FW: Recent make world breakages Date: Mon, 24 Jul 2000 14:56:29 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2651.58) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Blasted Outhouse mailer. Lets try again. -----Original Message----- From: Gray, David W. Sent: Monday, July 24, 2000 11:15 AM To: 'FreeBSD Current list' Subject: Recent make world breakages Not to exacerbate a sore subject, but... >From what I'm seeing go by, the intention is that a current make world is supposed to work from -stable. OK, what about make release? The reason I am asking, is that I'm actually running current on a laptop, and for various reasons, its far easier to be able to load it from a cdrom. My build machine is a 4.0 release box, its the only one I have that's muscular enough to do the build. Since I've been tracking -current (the last couple of weeks or so, but I've been on this list for a year or so) I have been able to build world, but building the boot crunch dies compiling /bin/sh (there are intermediate files created by yacc and such that are built in the current directory, not where the source is.) Should this work? Is it germane that I don't build in /usr/, but over in /home/current, etc? Should this work? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 24 12:50:34 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 7238B37BF09; Mon, 24 Jul 2000 12:50:28 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 86AC849; Mon, 24 Jul 2000 15:50:10 -0400 (AST) Message-ID: <397C9DF2.18CBB7B3@vangelderen.org> Date: Mon, 24 Jul 2000 15:50:10 -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: Kris Kennaway Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak 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: > > On Sun, 23 Jul 2000, Jeroen C. van Gelderen wrote: > > > > Well, a simple scheme which doesn't seem to suffer from any of the > > > vulnerabilities discussed in the schneier papers is to accumulate entropy > > > in a pool, and only return output when the pool is full. i.e. the PRNG > > > would either block or return 0 bytes of data, or a full pool's worth. > > > > And you can make Yarrow do just that. Not very practical but > > you can do it. You effectively set Pg to 1/(2^(k/3)). > > Oh, I missed this - thanks. It does introduce an extra overhead, namely > applying a generator gate with every output (since n < k and Pg < 1) and > then the full reseed with every k bits of output. I'm not too worried about that for three reasons: 1. The overhead will probably be insignificant. One doesn't use such vast amounts of random numbers. 2. At least the generator gate can be optimized out if it turns out to be a problem. 3. We could use a cipher with better key agility (CAST) to make each operation less computationally intensive. > ITYM Pg = k 2^(-k/3) > though - you want a maximum k bits of output, not 1. Pg is the number of blocks IIRC. > > Reseeds do not *have* to happen asynchronously as pointed out > > above. > > Yeah, but they do in the current implementation (AFAICT). Agreed. 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 24 13:25: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id 9A6D537B5FA for ; Mon, 24 Jul 2000 13:24:56 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id NAA49352; Mon, 24 Jul 2000 13:24:31 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Mon, 24 Jul 2000 13:24:31 -0700 (PDT) From: Doug Barton X-Sender: doug@dt052n3e.san.rr.com To: "Viren R.Shah" Cc: Neil Blakey-Milner , freebsd-current@freebsd.org Subject: Re: Locale issues on -current In-Reply-To: <14716.36682.601114.318034@jabberwock.rstcorp.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, 24 Jul 2000, Viren R.Shah wrote: > >> > [vshah@vorpal] /etc> perl > >> > perl: warning: Setting locale failed. > >> > perl: warning: Please check that your locale settings: > >> > LC_ALL = (unset), > >> > LC_CTYPE = "en_US", > >> > LANG = (unset) > >> > are supported and installed on your system. > Yes, it is gnome. And, as Doug suggested, it stops when you unset > LC_CTYPE. I don't think it is actually doing anything other than > irritating me. :-) Yeah, I just confirmed that the env variable is there in an xterm, but not there if I log into a vty. Like you said, it's not causing any harm which is why I've been so lax in troubleshooting it. Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 24 14:33:37 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 DCCDD37BD8B for ; Mon, 24 Jul 2000 14:33:31 -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 XAA12893 for freebsd-current@freebsd.org; Mon, 24 Jul 2000 23:33:16 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 8D8678865; Mon, 24 Jul 2000 21:58:51 +0200 (CEST) Date: Mon, 24 Jul 2000 21:58:51 +0200 From: Ollivier Robert To: freebsd-current@freebsd.org Subject: Re: Locale issues on -current Message-ID: <20000724215851.A18478@keltia.freenix.fr> Mail-Followup-To: freebsd-current@freebsd.org References: <14712.37803.399020.756017@vorpal.rstcorp.com> <397948EF.C1C7C396@gorean.org> <20000724105102.A96976@mithrandr.moria.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000724105102.A96976@mithrandr.moria.org>; from nbm@mithrandr.moria.org on Mon, Jul 24, 2000 at 10:51:02AM +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 Neil Blakey-Milner: > I've had this too. Never have figured what it was about, but it > happened only in X, where I use gnome. /me has the very same problem, running Gnome as well. -- 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 Mon Jul 24 14:42:38 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 6A8B837BF06; Mon, 24 Jul 2000 14:42:34 -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 OAA11082; Mon, 24 Jul 2000 14:42:34 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 24 Jul 2000 14:42:34 -0700 (PDT) From: Kris Kennaway To: "Jeroen C. van Gelderen" Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <397C9DF2.18CBB7B3@vangelderen.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jul 2000, Jeroen C. van Gelderen wrote: > 1. The overhead will probably be insignificant. One doesn't > use such vast amounts of random numbers. True, but the effect on slow CPUs for a single read may be signfificant. We'll have to see. > 2. At least the generator gate can be optimized out if it > turns out to be a problem. Yes. > 3. We could use a cipher with better key agility (CAST) > to make each operation less computationally intensive. Yes. > > ITYM Pg = k 2^(-k/3) > > though - you want a maximum k bits of output, not 1. > > Pg is the number of blocks IIRC. Pg is the number of (n=64)-bit blocks between generator gates, but min(2^n,2^(k/3)Pg) is the maximum number of output bits you'll get before the thing shuts up and waits for a reseed. So Pg < 1 means we'll take a generator gate after every output block, but will still output our 2^(k/3)Pg = k bits (i.e. 4 blocks worth) In practice we'd probably have to just special-case this since the required Pg is approximately 10^-24 :-) 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 24 15:59:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29]) by hub.freebsd.org (Postfix) with ESMTP id B6B2737BC73 for ; Mon, 24 Jul 2000 15:59:13 -0700 (PDT) (envelope-from areilly@nsw.bigpond.net.au) Received: from areilly.bpc-users.org (CPE-144-132-245-92.nsw.bigpond.net.au [144.132.245.92]) by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id HAA14669 for ; Tue, 25 Jul 2000 07:09:15 +1000 (EST) Received: (qmail 55646 invoked by uid 1000); 24 Jul 2000 12:09:14 -0000 From: "Andrew Reilly" Date: Mon, 24 Jul 2000 22:09:14 +1000 To: Nathan Binkert Cc: Brian Somers , Michael Lucas , current@FreeBSD.ORG Subject: Re: MS CHAP v2 in -current? Message-ID: <20000724220914.A51981@gurney.reilly.home> References: <200007221136.MAA12122@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from binkertn@umich.edu on Sat, Jul 22, 2000 at 08:29:23AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 22, 2000 at 08:29:23AM -0400, Nathan Binkert wrote: > The patch does work for client side. I have verified that I can connect > to a windows server using chap v2, but I forgot to do something for > server. Shouldn't take me long. If you need the server part before > Brian gets back, let me know. Out of interest, is there any code relationship, beyond the ijppp ancestor, between mpd-netgraph and ppp? I switched to mpd-netgraph recently when I was having problems getting pptp to work against a recent-ish NT server, and it's sort of working (keeps dropping out: I'll mail some traces to Archie soon.) It does do the authentication thing, though. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 24 18:51:31 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 0DAC237B875; Mon, 24 Jul 2000 18:51:24 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id E75DD49; Mon, 24 Jul 2000 21:51:21 -0400 (AST) Message-ID: <397CF299.9F89E1CA@vangelderen.org> Date: Mon, 24 Jul 2000 21:51:21 -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: Kris Kennaway , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <200007240603.IAA03449@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: [...] > > > Asynchonous reseeding _improves_ the situation; the attacker cannot force > > > it to any degree of accuracy, and if he has the odds stacked heavily against > > > him that each 256-bits of output will have an associated reseed, it makes > > > his job pretty damn difficult. This is not correct for a variety of reasons. But that's all fairly theoretical and ... not relevant for the discussion at hand. > > What I meant with that point is that the user may get, say an extra few > > hundred bits out of it with no new entropy before the scheduled reseed > > task kicks in. > > How does he know which bits are which? His analysis task just got a whole > lot more difficult. Again, not entirely correct but not relevant either... Kris is simply right in that the /dev/random semantics change and that more bits can be output by Yarrow than there is entropy gathered. *In theory* the complexity of an attack on our Yarrow has an upper bound of 2^256 and *in theory* this is less than the complexity of an attack on our current /dev/random. This is a hard fact, no way around that. However, the big question here is not about theory but about *practicality*. Is Yarrow less secure than /dev/random in practice? How does our /dev/random hold up under attack? How does Yarrow compare? I think we need to evaluate these practical questions instead of deep theoretical issues as Yarrow is all about practicality. At a more fundamental level we will need to answer the question: "Do we need to preserve the current /dev/random semantics or can we decide to change 'em? [1]". And how will this affect our applications *in practice*. So let's concentrate this discussion on the practical issues and explain why you think backing /dev/random with Yarrow and changing the semantics is justifyable or even a good thing. Cheers, Jeroen [1] And, should we decide not to change /dev/random semantics, can we still back /dev/random with a modified Yarrow? -- 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 Tue Jul 25 0:35:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id F0ABE37BA50 for ; Tue, 25 Jul 2000 00:35:23 -0700 (PDT) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) by matrix.eurocontrol.fr (Postfix) with ESMTP id BD7E556A8; Tue, 25 Jul 2000 09:35:22 +0200 (CEST) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id 809B54E60; Tue, 25 Jul 2000 09:35:21 +0200 (CEST) Date: Tue, 25 Jul 2000 09:35:21 +0200 From: Ollivier Robert To: FreeBSD Current Users' list Cc: mckusick@mckusick.com Subject: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking Message-ID: <20000725093521.A636@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just got two panics tonight, the same each time. Current from yesterday, after the latest round of patch from Kirk. The second panic is exactly the same including the trace. -=-=- (kgdb) exec-file /var/crash/kernel.7 (kgdb) core-file /var/crash/vmcore.7 IdlePTD 3661824 initial pcb at 2e5100 panicstr: lockmgr: pid 5, not exclusive lock holder 0 unlocking panic messages: --- panic: bqrelse: multiple refs syncing disks... panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking Uptime: 1h34m18s iconv_mod_handler #0 boot (howto=260) at ../../kern/kern_shutdown.c:303 #1 0xc016eb78 in poweroff_wait (junk=0xc02733a0, howto=5) at ../../kern/kern_shutdown.c:553 #2 0xc0169940 in lockmgr (lkp=0xc116bc00, flags=6, interlkp=0xccea97ac, p=0xcb92f780) at ../../kern/kern_lock.c:382 #3 0xc019cb2b in vop_stdunlock (ap=0xcb93d674) at ../../kern/vfs_default.c:255 #4 0xc0218e55 in ufs_vnoperate (ap=0xcb93d674) at ../../ufs/ufs/ufs_vnops.c:2291 #5 0xc0213db7 in ufs_inactive (ap=0xcb93d6a4) at vnode_if.h:865 #6 0xc0218e55 in ufs_vnoperate (ap=0xcb93d6a4) at ../../ufs/ufs/ufs_vnops.c:2291 #7 0xc019f8a6 in vput (vp=0xccea9740) at vnode_if.h:794 #8 0xc0211093 in ffs_sync (mp=0xc0e39200, waitfor=2, cred=0xc0a2b700, p=0xc0304940) at ../../ufs/ffs/ffs_vfsops.c:955 #9 0xc01a1785 in sync (p=0xc0304940, uap=0x0) at ../../kern/vfs_syscalls.c:551 #10 0xc016e5c7 in boot (howto=256) at ../../kern/kern_shutdown.c:225 #11 0xc016eb78 in poweroff_wait (junk=0xc027758b, howto=-972358720) at ../../kern/kern_shutdown.c:553 #12 0xc0197f2d in bqrelse (bp=0xc60afbc0) at ../../kern/vfs_bio.c:1195 #13 0xc01975a1 in vfs_backgroundwritedone (bp=0xc60dde20) at ../../kern/vfs_bio.c:696 #14 0xc0199a4d in bufdone (bp=0xc60dde20) at ../../kern/vfs_bio.c:2666 #15 0xc01999f6 in bufdonebio (bp=0xc60dde20) at ../../kern/vfs_bio.c:2617 #16 0xc012cc70 in dadone (periph=0xc0e00c00, done_ccb=0xc0e09c00) at ../../sys/bio.h:103 #17 0xc01271e7 in camisr (queue=0xc02e0bf0) at ../../cam/cam_xpt.c:6328 #18 0xc0126ff9 in swi_cambio () at ../../cam/cam_xpt.c:6231 #19 0xc0243370 in splz_swi () #20 0xc0197016 in bread (vp=0xcb929600, blkno=262208, size=12288, cred=0x0, bpp=0xcb93dbac) at ../../kern/vfs_bio.c:459 #21 0xc0205100 in ffs_blkfree (ip=0xcb93dc34, bno=90760, size=16384) at ../../ufs/ffs/ffs_alloc.c:1346 #22 0xc020c1e3 in indir_trunc (ip=0xcb93dc34, dbn=306752, level=0, lbn=12, countp=0xcb93dc24) at ../../ufs/ffs/ffs_softdep.c:2098 #23 0xc020bfb9 in handle_workitem_freeblocks (freeblks=0xc1059d80) at ../../ufs/ffs/ffs_softdep.c:2002 #24 0xc020ba40 in softdep_setup_freeblocks (ip=0xc10e4a00, length=0) at ../../ufs/ffs/ffs_softdep.c:1710 #25 0xc0206b56 in ffs_truncate (vp=0xccea92c0, length=0, flags=0, cred=0x0, p=0xcb92f780) at ../../ufs/ffs/ffs_inode.c:196 #26 0xc0213d0f in ufs_inactive (ap=0xcb93df00) at ../../ufs/ufs/ufs_inode.c:88 #27 0xc0218e55 in ufs_vnoperate (ap=0xcb93df00) at ../../ufs/ufs/ufs_vnops.c:2291 #28 0xc019f8a6 in vput (vp=0xccea92c0) at vnode_if.h:794 #29 0xc020cdd8 in handle_workitem_remove (dirrem=0xc0fc7aa0) at ../../ufs/ffs/ffs_softdep.c:2702 #30 0xc020a3e0 in softdep_process_worklist (matchmnt=0x0) at ../../ufs/ffs/ffs_softdep.c:556 #31 0xc019f134 in sched_sync () at ../../kern/vfs_subr.c:1017 #32 0xc0241edc in fork_trampoline () Cannot access memory at address 0x8000. -=-=- -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 1: 3:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 5071937B9DA; Tue, 25 Jul 2000 01:03:04 -0700 (PDT) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer goliath.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e6P831H24317; Tue, 25 Jul 2000 10:03:02 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.10.1/8.10.1) with ESMTP id e6P831R23011; Tue, 25 Jul 2000 10:03:01 +0200 (MET DST) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.11.0/8.11.0/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id e6P830324953; Tue, 25 Jul 2000 10:03:00 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.11.0/8.11.0/alaska [ $Revision: 1.4 ]) id e6P830t06245; Tue, 25 Jul 2000 08:03:00 GMT Date: Tue, 25 Jul 2000 10:03:00 +0200 From: Udo Schweigert To: ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: make package broken on -current (mtree -L problem) Message-ID: <20000725100300.A6187@alaska.cert.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i X-Operating-System: FreeBSD 4.1-RC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, when building a package on -current one gets: ===> Installing for bzip2-1.0.1 mtree: illegal option -- L usage: mtree [-PUcdeinrux] [-f spec] [-K key] [-k key] [-p path] [-s seed] [-X excludes] *** Error code 1 Seems to be a problem in /usr/ports/Mk/bsd.port.mk: .if ${OSVERSION} >= 500010 MTREE_ARGS?= -U -f ${MTREE_FILE} -L -d -e -p .else MTREE_ARGS?= -U -f ${MTREE_FILE} -d -e -p .endif Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : ust@cert.siemens.de PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 1:14:15 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 2A50437BB41 for ; Tue, 25 Jul 2000 01:14:10 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 26482 invoked from network); 25 Jul 2000 08:14:08 -0000 Received: from acs-24-154-24-131.zoominternet.net (HELO cvzoom.net) (24.154.24.131) by ns.cvzoom.net with SMTP; 25 Jul 2000 08:14:08 -0000 Message-ID: <397D4C4F.F2661226@cvzoom.net> Date: Tue, 25 Jul 2000 04:14:07 -0400 From: Donn Miller X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Udo Schweigert Cc: ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: make package broken on -current (mtree -L problem) References: <20000725100300.A6187@alaska.cert.siemens.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Udo Schweigert wrote: > ===> Installing for bzip2-1.0.1 > mtree: illegal option -- L > usage: mtree [-PUcdeinrux] [-f spec] [-K key] [-k key] [-p path] [-s seed] > [-X excludes] > *** Error code 1 > > Seems to be a problem in /usr/ports/Mk/bsd.port.mk: > > .if ${OSVERSION} >= 500010 > MTREE_ARGS?= -U -f ${MTREE_FILE} -L -d -e -p > .else > MTREE_ARGS?= -U -f ${MTREE_FILE} -d -e -p > .endif Seems as if your mtree is out of date. How long has it been since your last make world? Cvsup again and build/install mtree again and/or do a make world. -- - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 2:48:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 717F137BAF8; Tue, 25 Jul 2000 02:48:24 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.1+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e6P9mJp09644; Tue, 25 Jul 2000 18:48:19 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: ume@freebsd.org Cc: iwasaki@jp.FreeBSD.org, imp@village.org, jkh@FreeBSD.org, current@freebsd.org, mobile@freebsd.org Subject: multicast + PCCard NIC = kernel panic? (was Re: small bug in pcic.c) In-Reply-To: <200007250849.e6P8n2t00981@plum.ssr.bisd.hitachi.co.jp> References: <20000725055007J.iwasaki@jp.FreeBSD.org> <200007250849.e6P8n2t00981@plum.ssr.bisd.hitachi.co.jp> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000725184817P.iwasaki@jp.FreeBSD.org> Date: Tue, 25 Jul 2000 18:48:17 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [CC'ed -current and -mobile] > BTW, there is one more problem during detach the pccard nic. When I > detach my pccard nic, my kernel is panic. I tried this with Melco > Airconnect WLI-PCM-L11 and COREGA FastEther PCC-TX, and it occured > with either card. > I made a quick hack to avoid this problem. I don't know if this fix > is correct. > I sent it to -current, -net and -mobile. But, my message seems > disappeared. I don't know why. This is a critical problem especially for IPv6 laptop users right? The patch seems good enough for emergency workaround, If we don't have enough time for the regular reviewing process before 4.1R out, however, you are the right person to commit the patch since I know that you've tested enough it for days :-) > Index: sys/net/rtsock.c > diff -u sys/net/rtsock.c.orig sys/net/rtsock.c > --- sys/net/rtsock.c.orig Sun Feb 13 12:31:56 2000 > +++ sys/net/rtsock.c Sat Jul 22 08:53:16 2000 > @@ -828,7 +828,10 @@ > > bzero((caddr_t)&info, sizeof(info)); > ifaaddr = ifma->ifma_addr; > - ifpaddr = ifp->if_addrhead.tqh_first->ifa_addr; > + if (ifp && ifp->if_addrhead.tqh_first) > + ifpaddr = ifp->if_addrhead.tqh_first->ifa_addr; > + else > + ifpaddr = NULL; > /* > * If a link-layer address is present, present it as a ``gateway'' > * (similarly to how ARP entries, e.g., are presented). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 3:55:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 1D76D37BA2C; Tue, 25 Jul 2000 03:54:41 -0700 (PDT) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer goliath.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e6PAscH29606; Tue, 25 Jul 2000 12:54:38 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail2.siemens.de (8.10.1/8.10.1) with ESMTP id e6PAsc407781; Tue, 25 Jul 2000 12:54:38 +0200 (MET DST) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.11.0/8.11.0/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id e6PAsb325976; Tue, 25 Jul 2000 12:54:37 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.11.0/8.11.0/alaska [ $Revision: 1.4 ]) id e6PAsbr88576; Tue, 25 Jul 2000 10:54:37 GMT Date: Tue, 25 Jul 2000 12:54:37 +0200 From: Udo Schweigert To: Donn Miller Cc: ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: make package broken on -current (mtree -L problem) Message-ID: <20000725125437.A88557@alaska.cert.siemens.de> References: <20000725100300.A6187@alaska.cert.siemens.de> <397D4C4F.F2661226@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <397D4C4F.F2661226@cvzoom.net>; from dmmiller@cvzoom.net on Tue, Jul 25, 2000 at 04:14:07AM -0400 X-Operating-System: FreeBSD 4.1-RC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 25, 2000 at 04:14:07 -0400, Donn Miller wrote: > Udo Schweigert wrote: > > > ===> Installing for bzip2-1.0.1 > > mtree: illegal option -- L > > usage: mtree [-PUcdeinrux] [-f spec] [-K key] [-k key] [-p path] [-s seed] > > [-X excludes] > > *** Error code 1 > > > > Seems to be a problem in /usr/ports/Mk/bsd.port.mk: > > > > .if ${OSVERSION} >= 500010 > > MTREE_ARGS?= -U -f ${MTREE_FILE} -L -d -e -p > > .else > > MTREE_ARGS?= -U -f ${MTREE_FILE} -d -e -p > > .endif > > Seems as if your mtree is out of date. How long has it been since > your last make world? Cvsup again and build/install mtree again > and/or do a make world. > My mtree is up to date (rev 1.15 of mtree.c). A check of the cvs-tree shows that -L was backed out yesterday. Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : ust@cert.siemens.de PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 4:11:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from hitpro.hitachi.co.jp (hitpro.hitachi.co.jp [133.145.224.7]) by hub.freebsd.org (Postfix) with ESMTP id CD03337BA2C; Tue, 25 Jul 2000 04:11:12 -0700 (PDT) (envelope-from ume@bisd.hitachi.co.jp) Received: from bisdgw.bisd.hitachi.co.jp by hitpro.hitachi.co.jp (8.9.3/3.7W-hitpro) id UAA08650; Tue, 25 Jul 2000 20:11:10 +0900 (JST) Received: from plum.ssr.bisd.hitachi.co.jp by bisdgw.bisd.hitachi.co.jp (8.9.3+3.2W/3.7W-bisdgw) with ESMTP id UAA27710; Tue, 25 Jul 2000 20:11:10 +0900 (JST) (envelope-from ume@bisd.hitachi.co.jp) Received: from localhost (IDENT:oO6H84jRPeKUeJWVND2gTkRRVnOkAaehgeSlfeaPtR/8slPwwQtJ2yxEQpKoNscz@localhost [::1]) by plum.ssr.bisd.hitachi.co.jp (8.11.0/3.7W-plum) with ESMTP id e6PBB9o02930; Tue, 25 Jul 2000 20:11:09 +0900 (JST) (envelope-from ume@bisd.hitachi.co.jp) Message-Id: <200007251111.e6PBB9o02930@plum.ssr.bisd.hitachi.co.jp> To: iwasaki@jp.FreeBSD.org Cc: ume@freebsd.org, imp@village.org, jkh@FreeBSD.org, current@freebsd.org, mobile@freebsd.org Cc: ume@freebsd.org Subject: Re: multicast + PCCard NIC = kernel panic? (was Re: small bug in pcic.c) From: Hajimu UMEMOTO In-Reply-To: <20000725184817P.iwasaki@jp.FreeBSD.org> References: <20000725055007J.iwasaki@jp.FreeBSD.org> <200007250849.e6P8n2t00981@plum.ssr.bisd.hitachi.co.jp> <20000725184817P.iwasaki@jp.FreeBSD.org> X-Mailer: xcite1.20> Mew version 1.94.2 on XEmacs 21.1 (Bryce Canyon) X-PGP-Fingerprint: D3 3D D3 54 88 13 DE 22 3F 31 C4 4D A1 08 84 7B X-PGP-Public-Key: http://www.imasy.org/~ume/ume@bisd.hitachi.co.jp.asc X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 4.1-RC Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 25 Jul 2000 20:11:08 +0900 X-Dispatcher: imput version 20000414(IM141) Lines: 29 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Tue, 25 Jul 2000 18:48:17 +0900 >>>>> iwasaki@jp.FreeBSD.org (Mitsuru IWASAKI) said: > BTW, there is one more problem during detach the pccard nic. When I > detach my pccard nic, my kernel is panic. I tried this with Melco > Airconnect WLI-PCM-L11 and COREGA FastEther PCC-TX, and it occured > with either card. > I made a quick hack to avoid this problem. I don't know if this fix > is correct. > I sent it to -current, -net and -mobile. But, my message seems > disappeared. I don't know why. iwasaki> This is a critical problem especially for IPv6 laptop users right? Yes, I think it is critical for IPv6 users. But, I have never hear the problem from other than me. Is this only my problem? iwasaki> The patch seems good enough for emergency workaround, If we don't have iwasaki> enough time for the regular reviewing process before 4.1R out, iwasaki> however, you are the right person to commit the patch since I know iwasaki> that you've tested enough it for days :-) OK. We have no enough time. I'll commit it. Jordan, can I MFC this? -- Hajimu UMEMOTO @ Business Solution System Development Div., Hitachi Ltd. E-Mail: ume@bisd.hitachi.co.jp ume@mahoroba.org ume@FreeBSD.org URL: 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 Tue Jul 25 4:28:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 7B1F837BA2C; Tue, 25 Jul 2000 04:28:47 -0700 (PDT) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id BAA2F190A4; Tue, 25 Jul 2000 13:28:40 +0200 (CEST) Received: by antinea.enst.fr (Postfix, from userid 1000) id 7AC75241; Tue, 25 Jul 2000 13:28:39 +0200 (CEST) Date: Tue, 25 Jul 2000 13:28:39 +0200 To: Hajimu UMEMOTO Cc: iwasaki@jp.FreeBSD.org, imp@village.org, jkh@FreeBSD.org, current@freebsd.org, mobile@freebsd.org Subject: Re: multicast + PCCard NIC = kernel panic? (was Re: small bug in pcic.c) References: <20000725055007J.iwasaki@jp.FreeBSD.org> <200007250849.e6P8n2t00981@plum.ssr.bisd.hitachi.co.jp> <20000725184817P.iwasaki@jp.FreeBSD.org> <200007251111.e6PBB9o02930@plum.ssr.bisd.hitachi.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200007251111.e6PBB9o02930@plum.ssr.bisd.hitachi.co.jp>; from ume@freebsd.org on Tue, Jul 25, 2000 at 08:11:08PM +0900 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-07-25-13-28-39+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25/07, Hajimu UMEMOTO wrote: | Yes, I think it is critical for IPv6 users. But, I have never hear | the problem from other than me. Is this only my problem? No, I reported it some time ago, and it looks like it is fixed in -CURRENT sources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 4:59: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from hitpro.hitachi.co.jp (hitpro.hitachi.co.jp [133.145.224.7]) by hub.freebsd.org (Postfix) with ESMTP id C7D7537BD40; Tue, 25 Jul 2000 04:58:56 -0700 (PDT) (envelope-from ume@bisd.hitachi.co.jp) Received: from bisdgw.bisd.hitachi.co.jp by hitpro.hitachi.co.jp (8.9.3/3.7W-hitpro) id UAA19848; Tue, 25 Jul 2000 20:57:28 +0900 (JST) Received: from plum.ssr.bisd.hitachi.co.jp by bisdgw.bisd.hitachi.co.jp (8.9.3+3.2W/3.7W-bisdgw) with ESMTP id UAA28858; Tue, 25 Jul 2000 20:57:28 +0900 (JST) (envelope-from ume@bisd.hitachi.co.jp) Received: from localhost (IDENT:Y/r+Ln82T77T9pc1PE5djRJ7N4R1RXdUyn/2AzTm9oqKMHy5sRWi6+yxQffQ13km@localhost [::1]) by plum.ssr.bisd.hitachi.co.jp (8.11.0/3.7W-plum) with ESMTP id e6PBvRo03172; Tue, 25 Jul 2000 20:57:27 +0900 (JST) (envelope-from ume@bisd.hitachi.co.jp) Message-Id: <200007251157.e6PBvRo03172@plum.ssr.bisd.hitachi.co.jp> To: sam@inf.enst.fr Cc: ume@freebsd.org, iwasaki@jp.FreeBSD.org, imp@village.org, jkh@FreeBSD.org, current@freebsd.org, mobile@freebsd.org Cc: ume@freebsd.org Subject: Re: multicast + PCCard NIC = kernel panic? (was Re: small bug in pcic.c) From: Hajimu UMEMOTO In-Reply-To: <2000-07-25-13-28-39+trackit+sam@inf.enst.fr> References: <20000725184817P.iwasaki@jp.FreeBSD.org> <200007251111.e6PBB9o02930@plum.ssr.bisd.hitachi.co.jp> <2000-07-25-13-28-39+trackit+sam@inf.enst.fr> X-Mailer: xcite1.20> Mew version 1.94.2 on XEmacs 21.1 (Bryce Canyon) X-PGP-Fingerprint: D3 3D D3 54 88 13 DE 22 3F 31 C4 4D A1 08 84 7B X-PGP-Public-Key: http://www.imasy.org/~ume/ume@bisd.hitachi.co.jp.asc X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 4.1-RC Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 25 Jul 2000 20:57:26 +0900 X-Dispatcher: imput version 20000414(IM141) Lines: 18 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Tue, 25 Jul 2000 13:28:39 +0200 >>>>> sam@inf.enst.fr (Samuel Tardieu) said: sam> On 25/07, Hajimu UMEMOTO wrote: sam> | Yes, I think it is critical for IPv6 users. But, I have never hear sam> | the problem from other than me. Is this only my problem? sam> No, I reported it some time ago, and it looks like it is fixed in -CURRENT sam> sources. I know this. I think you mean kern/17909. This was already MFC'd. I'm using 4.1-RC of yesterday and it has this fix. -- Hajimu UMEMOTO @ Business Solution System Development Div., Hitachi Ltd. E-Mail: ume@bisd.hitachi.co.jp ume@mahoroba.org ume@FreeBSD.org URL: 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 Tue Jul 25 5:39:36 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 D401C37BD84 for ; Tue, 25 Jul 2000 05:39:27 -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.Beta1) with ESMTP id e6PCdMG00746 for ; Tue, 25 Jul 2000 21:39:23 +0900 (JST) Date: Tue, 25 Jul 2000 21:39:22 +0900 Message-ID: <7m3dkyo03p.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: freebsd-current@FreeBSD.org Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-Reply-To: In your message of "25 Jul 2000 07:37:43 GMT" <20000725093521.A636@caerdonn.eurocontrol.fr> References: <20000725093521.A636@caerdonn.eurocontrol.fr> 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 At 25 Jul 2000 07:37:43 GMT, Ollivier Robert wrote: > I just got two panics tonight, the same each time. Current from yesterday, > after the latest round of patch from Kirk. The second panic is exactly the > same including the trace. It seems I've got same panics. But sometimes my box cannot panic and rebooted suddenly. # My box rebooted 4 times today. :-( -- 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 Tue Jul 25 5:44:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6C32737BD82; Tue, 25 Jul 2000 05:44:38 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id FAA07679; Tue, 25 Jul 2000 05:44:39 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: Hajimu UMEMOTO Cc: iwasaki@jp.FreeBSD.org, imp@village.org, jkh@FreeBSD.ORG, current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: multicast + PCCard NIC = kernel panic? (was Re: small bug in pcic.c) In-reply-to: Your message of "Tue, 25 Jul 2000 20:11:08 +0900." <200007251111.e6PBB9o02930@plum.ssr.bisd.hitachi.co.jp> Date: Tue, 25 Jul 2000 05:44:39 -0700 Message-ID: <7676.964529079@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK. We have no enough time. I'll commit it. > Jordan, can I MFC this? Only if you're really really sure it won't break something else. I must confess that the way this one has turned up with no independant confirmation makes me very nervous. :-( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 6:12:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from enigma.whacky.net (enigma.whacky.net [194.109.204.120]) by hub.freebsd.org (Postfix) with ESMTP id B908337B68C; Tue, 25 Jul 2000 06:12:15 -0700 (PDT) (envelope-from stephanb@whacky.net) Received: (from stephanb@localhost) by enigma.whacky.net (8.9.3/8.9.3) id PAA61440; Tue, 25 Jul 2000 15:12:12 +0200 (CEST) (envelope-from stephanb) Date: Tue, 25 Jul 2000 15:12:11 +0200 From: Stephan van Beerschoten To: Jun Kuriyama Cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking Message-ID: <20000725151211.A44014@enigma.whacky.net> References: <20000725093521.A636@caerdonn.eurocontrol.fr> <7m3dkyo03p.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: <7m3dkyo03p.wl@waterblue.imgsrc.co.jp>; from kuriyama@FreeBSD.ORG on Tue, Jul 25, 2000 at 09:39:22PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jul 2000, Jun Kuriyama wrote: > At 25 Jul 2000 07:37:43 GMT, > Ollivier Robert wrote: > > I just got two panics tonight, the same each time. Current from yesterday, > > after the latest round of patch from Kirk. The second panic is exactly the > > same including the trace. > > It seems I've got same panics. But sometimes my box cannot panic and > rebooted suddenly. > > # My box rebooted 4 times today. :-( here too (about the panics and the spontanious boots). I don't know what the problem is.. I have recompiled the kernel again after some cvs updates, but it's still the same. So if its not the kernel it must be a userland tool, but I don't have enough time to build myself a new world, because everytime I start the process and I come back after a while, I find my machine rebooted. Right now I'm trying again while i stay present at the machine itself to see what it could be. btw, I have some big problems with the new version of mtree .. it seems that the -L flag has been abandoned.. which results in almost every port I try to install failing.. I have recompiled mtree from the tree and installed in manually (because at first my world failed as wel). Almost all 'make install's fail on mtree using -L option. Am I missing something about the mtree replacement that I should have to know ? -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 From owner-freebsd-current Tue Jul 25 7: 1:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from aesthetic.detachment.org (agcess.com [208.11.244.15]) by hub.freebsd.org (Postfix) with ESMTP id 6F0B037B544 for ; Tue, 25 Jul 2000 07:01:11 -0700 (PDT) (envelope-from tstromberg@rtci.com) Received: from rtci.com (helixblue@localhost [127.0.0.1]) by aesthetic.detachment.org (8.9.3/8.9.3) with ESMTP id KAA00443; Tue, 25 Jul 2000 10:00:52 -0400 (EDT) (envelope-from tstromberg@rtci.com) Message-ID: <397D9D94.8242C57E@rtci.com> Date: Tue, 25 Jul 2000 10:00:52 -0400 From: Thomas Stromberg X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Stephan van Beerschoten Cc: freebsd-current@FreeBSD.ORG Subject: Re: mtree -L problems in ports References: <20000725093521.A636@caerdonn.eurocontrol.fr> <7m3dkyo03p.wl@waterblue.imgsrc.co.jp> <20000725151211.A44014@enigma.whacky.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephan van Beerschoten wrote: > btw, I have some big problems with the new version of mtree .. it seems that > the -L flag has been abandoned.. which results in almost every port I try > to install failing.. I have recompiled mtree from the tree and installed > in manually (because at first my world failed as wel). > > Almost all 'make install's fail on mtree using -L option. Am I missing > something about the mtree replacement that I should have to know ? > > -Steve It's probably been fixed by now, but what I did when I first had the mtree problem was set NO_MTREE in /usr/ports/Mk/bsd.port.mk - Not sure of the side affects though (anyone care to enligtnen me?) Im sure there is a more elegant solution, I was just looking for a quicky. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.2 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE5fZ1foyBzPESpFVQRAi+XAJwLJ/ae/lv0upHXZT0809bYqMz7YACbBwZI KUk+zU+eg1tmCayUgq5nuAw= =XSok -----END PGP SIGNATURE----- -- thomas r. stromberg : tstromberg@rtci.com senior systems administrator : http://www.afterthought.org/ research triangle commerce, inc. : 1.919.657.1317 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 7:19:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4C7B337B6C6; Tue, 25 Jul 2000 07:19:24 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Tue, 25 Jul 2000 10:19:23 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Ollivier Robert Cc: FreeBSD Current Users' list , mckusick@mckusick.com Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-Reply-To: <20000725093521.A636@caerdonn.eurocontrol.fr> 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, 25 Jul 2000, Ollivier Robert wrote: > I just got two panics tonight, the same each time. Current from yesterday, > after the latest round of patch from Kirk. The second panic is exactly the > same including the trace. Welp, I didn't get em before, but I do now. I'll see what I can do to figure this one out, but don't know at all if I'll be able to solve it. My backtrace is similar. The important par about the backtrace is the part before the panic: #9 0xc0164695 in panic (fmt=0xc02662eb "bqrelse: multiple refs") at ../../kern/kern_shutdown.c:553 #10 0xc018f3b5 in bqrelse (bp=0xc373e100) at ../../kern/vfs_bio.c:1195 #11 0xc018e9b9 in vfs_backgroundwritedone (bp=0xc37812e0) at ../../kern/vfs_bio.c:696 #12 0xc0190fbd in bufdone (bp=0xc37812e0) at ../../kern/vfs_bio.c:2666 #13 0xc0190f06 in bufdonebio (bp=0xc37812e0) at ../../kern/vfs_bio.c:2617 #14 0xc0221258 in ad_interrupt (request=0xc10f43c0) at ../../sys/bio.h:103 #15 0xc021f756 in ata_intr (data=0xc0c7ff80) at ../../dev/ata/ata-all.c:1126 #16 0xc024b747 in splx (ipl=0xc018e41a) at ../../i386/isa/ipl_funcs.c:181 #17 0xc018e41a in bread (vp=0xcf889600, blkno=0x260030, size=0x1800, cred=0x0, bpp=0xd0476ad0) at ../../kern/vfs_bio.c:459 #18 0xc01fa070 in ffs_blkfree (ip=0xd0476b58, bno=0x1373c8, size=0x2000) at ../../ufs/ffs/ffs_alloc.c:1346 #19 0xc0201153 in indir_trunc (ip=0xd0476b58, dbn=0x24cf40, level=0x0, lbn=0xc, countp=0xd0476b48) at ../../ufs/ffs/ffs_softdep.c:2098 #20 0xc0200f29 in handle_workitem_freeblocks (freeblks=0xc0ce9200) at ../../ufs/ffs/ffs_softdep.c:2002 #21 0xc02009b0 in softdep_setup_freeblocks (ip=0xc0f4ac00, length=0x0) at ../../ufs/ffs/ffs_softdep.c:1710 #22 0xc01fbac6 in ffs_truncate (vp=0xd036a800, length=0x0, flags=0x0, cred=0xc0ce9080, p=0xd03333c0) at ../../ufs/ffs/ffs_inode.c:196 #23 0xc020bc12 in ufs_setattr (ap=0xd0476e44) at ../../ufs/ufs/ufs_vnops.c:498 #24 0xc020dedd in ufs_vnoperate (ap=0xd0476e44) at ../../ufs/ufs/ufs_vnops.c:2291 #25 0xc0199cb8 in open (p=0xd03333c0, uap=0xd0476f80) at vnode_if.h:305 #26 0xc02479d1 in syscall2 (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0xbfbff9f0, tf_esi = 0xbfbff9d8, tf_ebp = 0xbfbff964, tf_isp = 0xd0476fd4, tf_ebx = 0xbfbff9d8, tf_edx = 0x7ffff, tf_ecx = 0x7ffff, tf_eax = 0x5, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0x804d788, tf_cs = 0x1f, tf_eflags = 0x246, tf_esp = 0xbfbff928, tf_ss = 0x2f}) at ../../i386/i386/trap.c:1128 #27 0xc023bab5 in Xint0x80_syscall () #28 0x8048ec2 in ?? () #29 0x8048139 in ?? () At frame 10, the lock is held in multiple: (kgdb) p bp->b_lock $1 = { lk_interlock = { lock_data = 0x0 }, lk_flags = 0x440, lk_sharecount = 0x0, lk_waitcount = 0x0, lk_exclusivecount = 0x2, lk_prio = 0x14, lk_wmesg = 0xc0265fe4 "bufwait", lk_timo = 0x0, lk_lockholder = 0x752f } -- 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 Tue Jul 25 7:25:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id EBF5D37B68D; Tue, 25 Jul 2000 07:25:42 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Tue, 25 Jul 2000 10:25:38 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Ollivier Robert Cc: FreeBSD Current Users' list , mckusick@mckusick.com Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-Reply-To: <20000725093521.A636@caerdonn.eurocontrol.fr> 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 Actually, I'm pretty certain this is the fix: Index: vfs_bio.c =================================================================== RCS file: /usr2/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.260 diff -u -r1.260 vfs_bio.c --- vfs_bio.c 2000/07/11 22:07:43 1.260 +++ vfs_bio.c 2000/07/25 14:24:26 @@ -1067,9 +1067,6 @@ if (bp->b_qindex != QUEUE_NONE) panic("brelse: free buffer onto another queue???"); if (BUF_REFCNT(bp) > 1) { - /* Temporary panic to verify exclusive locking */ - /* This panic goes away when we allow shared refs */ - panic("brelse: multiple refs"); /* do not release to free list */ BUF_UNLOCK(bp); splx(s); @@ -1192,7 +1189,6 @@ panic("bqrelse: free buffer onto another queue???"); if (BUF_REFCNT(bp) > 1) { /* do not release to free list */ - panic("bqrelse: multiple refs"); BUF_UNLOCK(bp); splx(s); return; -- 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 Tue Jul 25 8: 5: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id 92B5537B5EB; Tue, 25 Jul 2000 08:04:58 -0700 (PDT) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) by matrix.eurocontrol.fr (Postfix) with ESMTP id BEE215A5D; Tue, 25 Jul 2000 17:04:56 +0200 (CEST) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id ECB454E61; Tue, 25 Jul 2000 17:04:55 +0200 (CEST) Date: Tue, 25 Jul 2000 17:04:55 +0200 From: Ollivier Robert To: Brian Fundakowski Feldman Cc: FreeBSD Current Users' list , mckusick@mckusick.com Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking Message-ID: <20000725170455.F636@caerdonn.eurocontrol.fr> References: <20000725093521.A636@caerdonn.eurocontrol.fr> 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 Tue, Jul 25, 2000 at 10:25:38AM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Brian Fundakowski Feldman: > Actually, I'm pretty certain this is the fix: Well it won't panic but isn't it putting the problem under the carpet? I agree the panic seems to be here temporarely but... -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 8:23:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from enigma.whacky.net (enigma.whacky.net [194.109.204.120]) by hub.freebsd.org (Postfix) with ESMTP id D55D537B5CD; Tue, 25 Jul 2000 08:23:32 -0700 (PDT) (envelope-from stephanb@whacky.net) Received: (from stephanb@localhost) by enigma.whacky.net (8.9.3/8.9.3) id RAA94125; Tue, 25 Jul 2000 17:23:29 +0200 (CEST) (envelope-from stephanb) Date: Tue, 25 Jul 2000 17:23:29 +0200 From: Stephan van Beerschoten To: Brian Fundakowski Feldman Cc: Ollivier Robert , "FreeBSD Current Users' list" , mckusick@mckusick.com Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking Message-ID: <20000725172329.A94003@enigma.whacky.net> References: <20000725093521.A636@caerdonn.eurocontrol.fr> 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 Tue, Jul 25, 2000 at 10:25:38AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jul 2000, Brian Fundakowski Feldman wrote: > Actually, I'm pretty certain this is the fix: > I have removed the panic-calls. I'll see if my system gets otherwise unstable.. For now i'll be happy if I get enough time for my make world to complete before my system hangt itself again :) But indeed.. isn't removing the panic cal just shifting the problem in stead of taking care of the panic-originator ? 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 From owner-freebsd-current Tue Jul 25 8:36:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5627E37B5EC; Tue, 25 Jul 2000 08:36:24 -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 JAA26212; Tue, 25 Jul 2000 09:36:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA20062; Tue, 25 Jul 2000 09:35:53 -0600 (MDT) Message-Id: <200007251535.JAA20062@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: multicast + PCCard NIC = kernel panic? (was Re: small bug in pcic.c) Cc: Hajimu UMEMOTO , iwasaki@jp.FreeBSD.org, jkh@FreeBSD.ORG, current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Tue, 25 Jul 2000 05:44:39 PDT." <7676.964529079@localhost> References: <7676.964529079@localhost> Date: Tue, 25 Jul 2000 09:35:53 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <7676.964529079@localhost> "Jordan K. Hubbard" writes: : > OK. We have no enough time. I'll commit it. : > Jordan, can I MFC this? : : Only if you're really really sure it won't break something else. : I must confess that the way this one has turned up with no independant : confirmation makes me very nervous. :-( Unless it is critical for the installation on a laptop, I'd suggest that we pass on a MFC before 4.1R and do it after. So far we've had only a couple of people see the problem, if I'm reading things correctly and not on installation. Am I understanding right? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 8:43:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id A369637B5CD; Tue, 25 Jul 2000 08:43:23 -0700 (PDT) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) by matrix.eurocontrol.fr (Postfix) with ESMTP id DBFDF5A3D; Tue, 25 Jul 2000 17:43:21 +0200 (CEST) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id 70FAE4E60; Tue, 25 Jul 2000 17:43:21 +0200 (CEST) Date: Tue, 25 Jul 2000 17:43:21 +0200 From: Ollivier Robert To: Stephan van Beerschoten Cc: Brian Fundakowski Feldman , FreeBSD Current Users' list Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking Message-ID: <20000725174321.G636@caerdonn.eurocontrol.fr> References: <20000725093521.A636@caerdonn.eurocontrol.fr> <20000725172329.A94003@enigma.whacky.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000725172329.A94003@enigma.whacky.net>; from stephanb@whacky.net on Tue, Jul 25, 2000 at 05:23:29PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Stephan van Beerschoten: > But indeed.. isn't removing the panic cal just shifting the problem in > stead of taking care of the panic-originator ? That's what is bothering me :-) > And what is the word on thise IOERROR's given by my kernel when its init'ing > its usb stack. It started a few months but doesn't seem to stop my USB mouse from working... -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 8:47:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5624137B5CD; Tue, 25 Jul 2000 08:47:06 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Tue, 25 Jul 2000 11:47:03 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Ollivier Robert Cc: FreeBSD Current Users' list , mckusick@mckusick.com Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-Reply-To: <20000725170455.F636@caerdonn.eurocontrol.fr> 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, 25 Jul 2000, Ollivier Robert wrote: > According to Brian Fundakowski Feldman: > > Actually, I'm pretty certain this is the fix: > > Well it won't panic but isn't it putting the problem under the carpet? I > agree the panic seems to be here temporarely but... No, I'm really certain this isn't the case. You see, struct buf has a b_lock that until recently was a plain, exclusive lockmgr lock. In Kirk's last round of changes, he converted b_lock to be LK_CANRECURSE, which means that the lock, while still an exclusive lock, may be relocked multiple times by the same caller. The panics are plain wrong. What's left is to determine what is the proper thing to do in each of these cases, which I'm certain that many people already know already (you see, I'm still a bit green ;). What I am _almost_ sure about is that the right thing is just to remove one of the locks and let it get freed back up the call chain. I'm almost certain this is the case because if you are grabbing exclusive locks and recursing upon them, your call chain is the only consumer and in a recursive-locking-callchain, you will have multiple symmetric lock and unlock pairs. Anything else horribly complicates things, and this makes me a good 95% certain that this is exactly the right fix, not that it's sweeping any true bugs under the carpet. Allowing recursive locks is pretty much the only way to solve many of the problems here because it's simply not possible to support all code paths without allowing for this recursion. The code would either be horribly complicated or non-functional. I'm certain Kirk may be able to back me up here. It seems that the cleanup is meant to make the locks recursive mostly to facilitate correct/proper call chains, and that's consistent with my understand at least :) Indeed, if you look at the comment in brelse() from the delta, you will see that the intention of allowing this very situation to occur and simply BUF_UNLOCK() was planned for and the panic()s were for debugging during the previous time that b_locks weren't LK_CANRECURSE. As always, take what I say with a grain of salt since I'm definitely not a VFS guru in any manner; I just happen to think I understand this one :) > -- > Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr > The Postman hits! The Postman hits! You have new mail. -- 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 Tue Jul 25 9:22:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from m10.alpha-net.ne.jp (m10.alpha-net.ne.jp [210.229.64.40]) by hub.freebsd.org (Postfix) with ESMTP id 0E64437B67D for ; Tue, 25 Jul 2000 09:22:47 -0700 (PDT) (envelope-from aitmore9@m10.alpha-net.ne.jp) Received: from god (1Cust95.tnt1.hachiouji.jp.da.uu.net [63.12.220.95]) by m10.alpha-net.ne.jp (8.9.3/3.7W) with SMTP id BAA04255 for ; Wed, 26 Jul 2000 01:22:43 +0900 (JST) Message-ID: <001d01bff655$9dd37fc0$5fdc0c3f@god> From: "=?iso-2022-jp?B?GyRCRDlDK0BuPHczJBsoQg==?=" To: Date: Wed, 26 Jul 2000 01:30:15 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01BFF6A1.0D1C76C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0019_01BFF6A1.0D1C76C0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit auth 0ad9305e unsubscribe freebsd-current aitmore9@m10.alpha-net.ne.jp ------=_NextPart_000_0019_01BFF6A1.0D1C76C0 Content-Type: text/html; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable
auth 0ad9305e unsubscribe freebsd-current aitmore9@m10.alpha-net.ne.jp=
------=_NextPart_000_0019_01BFF6A1.0D1C76C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 9:52:20 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 EECDE37B682; Tue, 25 Jul 2000 09:52:04 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:s6fpSRN5WhQ2ENcEemHqiKB7Nn4g/DHESvPsFpfQ9lbRWST+reNUSCARWO8pVPhl@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.0/3.7W-peace) with ESMTP id e6PGmMB73256; Wed, 26 Jul 2000 01:48:22 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 26 Jul 2000 01:48:19 +0900 (JST) Message-Id: <20000726.014819.59534040.ume@mahoroba.org> To: imp@village.org Cc: jkh@zippy.osd.bsdi.com, iwasaki@jp.FreeBSD.org, jkh@FreeBSD.ORG, current@FreeBSD.ORG, mobile@FreeBSD.ORG Cc: ume@mahoroba.org Subject: Re: multicast + PCCard NIC = kernel panic? From: Hajimu UMEMOTO In-Reply-To: <200007251535.JAA20062@harmony.village.org> References: <7676.964529079@localhost> <200007251535.JAA20062@harmony.village.org> X-Mailer: xcite1.20> 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 Tue, 25 Jul 2000 09:35:53 -0600 >>>>> Warner Losh said: imp> In message <7676.964529079@localhost> "Jordan K. Hubbard" writes: imp> : > OK. We have no enough time. I'll commit it. imp> : > Jordan, can I MFC this? imp> : imp> : Only if you're really really sure it won't break something else. imp> : I must confess that the way this one has turned up with no independant imp> : confirmation makes me very nervous. :-( imp> Unless it is critical for the installation on a laptop, I'd suggest imp> that we pass on a MFC before 4.1R and do it after. So far we've had imp> only a couple of people see the problem, if I'm reading things imp> correctly and not on installation. Am I understanding right? Yes, panic will happen only during detach the card. So, install should be OK. I'll MFC after 4.1-RELEASE is out. Thank you for your suggestion and sorry for makeing this situation. -- 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 Tue Jul 25 11:35:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by hub.freebsd.org (Postfix) with ESMTP id 59DB437B7E4; Tue, 25 Jul 2000 11:35:41 -0700 (PDT) (envelope-from mckusick@mckusick.com) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.9.3/8.9.3) with ESMTP id LAA13336; Tue, 25 Jul 2000 11:35:37 -0700 (PDT) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200007251835.LAA13336@beastie.mckusick.com> To: Brian Fundakowski Feldman Subject: Re: Panic: bqrelse: multiple refs Cc: Ollivier Robert , freebsd-current@FreeBSD.org, Stephan van Beerschoten , Robert Watson In-Reply-To: Your message of "Tue, 25 Jul 2000 11:47:03 EDT." Date: Tue, 25 Jul 2000 11:35:37 -0700 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Tue, 25 Jul 2000 11:47:03 -0400 (EDT) From: Brian Fundakowski Feldman To: Ollivier Robert Cc: "FreeBSD Current Users' list" , mckusick@mckusick.com Subject: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-Reply-To: <20000725170455.F636@caerdonn.eurocontrol.fr> On Tue, 25 Jul 2000, Ollivier Robert wrote: > According to Brian Fundakowski Feldman: > > Actually, I'm pretty certain this is the fix: > > Well it won't panic but isn't it putting the problem under the carpet? > I agree the panic seems to be here temporarely but... No, I'm really certain this isn't the case. You see, struct buf has a b_lock that until recently was a plain, exclusive lockmgr lock. In Kirk's last round of changes, he converted b_lock to be LK_CANRECURSE, which means that the lock, while still an exclusive lock, may be relocked multiple times by the same caller. The panics are plain wrong. What's left is to determine what is the proper thing to do in each of these cases, which I'm certain that many people already know already (you see, I'm still a bit green ;). What I am _almost_ sure about is that the right thing is just to remove one of the locks and let it get freed back up the call chain. I'm almost certain this is the case because if you are grabbing exclusive locks and recursing upon them, your call chain is the only consumer and in a recursive-locking-callchain, you will have multiple symmetric lock and unlock pairs. Anything else horribly complicates things, and this makes me a good 95% certain that this is exactly the right fix, not that it's sweeping any true bugs under the carpet. Allowing recursive locks is pretty much the only way to solve many of the problems here because it's simply not possible to support all code paths without allowing for this recursion. The code would either be horribly complicated or non-functional. I'm certain Kirk may be able to back me up here. It seems that the cleanup is meant to make the locks recursive mostly to facilitate correct/proper call chains, and that's consistent with my understand at least :) Indeed, if you look at the comment in brelse() from the delta, you will see that the intention of allowing this very situation to occur and simply BUF_UNLOCK() was planned for and the panic()s were for debugging during the previous time that b_locks weren't LK_CANRECURSE. As always, take what I say with a grain of salt since I'm definitely not a VFS guru in any manner; I just happen to think I understand this one :) > -- > Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr > The Postman hits! The Postman hits! You have new mail. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' The above explanation is correct. When I made the change to allow recursive buffer locks, I should have removed that panic (but forgot that I had put it in there, sigh). I have just made the change on freefall. Sorry for the problems caused by that change. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 11:59:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.netbenefit.co.uk (mailhost.netbenefit.co.uk [212.53.64.39]) by hub.freebsd.org (Postfix) with ESMTP id 808E637B8B6; Tue, 25 Jul 2000 11:59:26 -0700 (PDT) (envelope-from pierre.dampure@alveley.org) Received: from userek35.uk.uudial.com ([62.188.13.145] helo=alveley.org) by mailhost.netbenefit.co.uk with esmtp (NetBenefit 1.5) id 13H6cZ-0008Ug-00 ; Tue, 25 Jul 2000 16:27:52 +0100 Message-ID: <397DB1F2.F62858@alveley.org> Date: Tue, 25 Jul 2000 16:27:46 +0100 From: "Dampure, Pierre Y." X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Stephan van Beerschoten Cc: Brian Fundakowski Feldman , Ollivier Robert , FreeBSD Current Users' list , mckusick@mckusick.com Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking References: <20000725093521.A636@caerdonn.eurocontrol.fr> <20000725172329.A94003@enigma.whacky.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephan van Beerschoten wrote: > > 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 > Funny you should mention that :-) I asked the same question to N. Hibma a while ago (I get the same problem on my Intel OR840), but so far haven't had an answer. Regards, PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 12: 1: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.netbenefit.co.uk (mailhost.netbenefit.co.uk [212.53.64.39]) by hub.freebsd.org (Postfix) with ESMTP id E1F7337BA6B for ; Tue, 25 Jul 2000 12:00:52 -0700 (PDT) (envelope-from pierre.dampure@alveley.org) Received: from userek35.uk.uudial.com ([62.188.13.145] helo=alveley.org) by mailhost.netbenefit.co.uk with esmtp (NetBenefit 1.5) id 13H6WK-00082m-00 ; Tue, 25 Jul 2000 16:21:25 +0100 Message-ID: <397DB073.EAC30BE2@alveley.org> Date: Tue, 25 Jul 2000 16:21:23 +0100 From: "Dampure, Pierre Y." X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Stromberg Cc: Stephan van Beerschoten , freebsd-current@FreeBSD.ORG Subject: Re: mtree -L problems in ports References: <20000725093521.A636@caerdonn.eurocontrol.fr> <7m3dkyo03p.wl@waterblue.imgsrc.co.jp> <20000725151211.A44014@enigma.whacky.net> <397D9D94.8242C57E@rtci.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Stromberg wrote: > > It's probably been fixed by now, but what I did when I first had the > mtree > problem was set NO_MTREE in /usr/ports/Mk/bsd.port.mk - Not sure of the > side > affects though (anyone care to enligtnen me?) > > Im sure there is a more elegant solution, I was just looking for a > quicky. > It is not fixed. Th current version of /usr/ports/Mk/bsd.ports.mk still has an OS version test to determine whether to use the -L flag -- committed by Satoshi Asami after the initial "no -L, now -L" move. The move was later backed out, but not this change. The whole issue of mtree behaviour has been discussed ad nauseam on cvs-all. Up until a concensus is reached, it's most probably easier to locally override MTREE_ARGS. Regards, PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 12: 3: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 6671837B878; Tue, 25 Jul 2000 12:03:01 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id MAA31510; Tue, 25 Jul 2000 12:12:20 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007251912.MAA31510@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Dampure, Pierre Y." Cc: Stephan van Beerschoten , Brian Fundakowski Feldman , Ollivier Robert , "FreeBSD Current Users' list" , mckusick@mckusick.com Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-reply-to: Your message of "Tue, 25 Jul 2000 16:27:46 BST." <397DB1F2.F62858@alveley.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Jul 2000 12:12:20 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Stephan van Beerschoten wrote: > > > > 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 > > > > Funny you should mention that :-) I asked the same question to N. Hibma > a while ago (I get the same problem on my Intel OR840), but so far > haven't had an answer. That's because the message is completely harmless; ignore it. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 14:32:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 0EEB937BA32; Tue, 25 Jul 2000 14:32:04 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13HCJ0-0002H3-00; Tue, 25 Jul 2000 21:32:02 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id XAA09332; Tue, 25 Jul 2000 23:20:47 +0200 (CEST) (envelope-from wkb) Date: Tue, 25 Jul 2000 23:20:47 +0200 From: Wilko Bulte To: Mike Smith Cc: "Dampure, Pierre Y." , Stephan van Beerschoten , Brian Fundakowski Feldman , Ollivier Robert , "FreeBSD Current Users' list" , mckusick@mckusick.com Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking Message-ID: <20000725232047.A9250@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <397DB1F2.F62858@alveley.org> <200007251912.MAA31510@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007251912.MAA31510@mass.osd.bsdi.com>; from msmith@freebsd.org on Tue, Jul 25, 2000 at 12:12:20PM -0700 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 25, 2000 at 12:12:20PM -0700, Mike Smith wrote: > > Stephan van Beerschoten wrote: > > > > > > 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 > > > > > > > Funny you should mention that :-) I asked the same question to N. Hibma > > a while ago (I get the same problem on my Intel OR840), but so far > > haven't had an answer. > > That's because the message is completely harmless; ignore it. True.. but flagging completely harmless messages with "failed" and "IOERROR" is bound to generate lots and lots of questions. If it does not tell the world anything useful let's please get rid of it. Or? -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 15:23:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 646B037BAC3; Tue, 25 Jul 2000 15:23:48 -0700 (PDT) (envelope-from jhb@pike.osd.bsdi.com) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id PAA09975; Tue, 25 Jul 2000 15:23:43 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200007252223.PAA09975@pike.osd.bsdi.com> Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-Reply-To: <20000725232047.A9250@freebie.demon.nl> from Wilko Bulte at "Jul 25, 2000 11:20:47 pm" To: wilko@FreeBSD.ORG Date: Tue, 25 Jul 2000 15:23:43 -0700 (PDT) Cc: current@FreeBSD.ORG, n_hibma@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > On Tue, Jul 25, 2000 at 12:12:20PM -0700, Mike Smith wrote: > > > Stephan van Beerschoten wrote: > > > > > > > > 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 > > > > > > > > > > Funny you should mention that :-) I asked the same question to N. Hibma > > > a while ago (I get the same problem on my Intel OR840), but so far > > > haven't had an answer. > > > > That's because the message is completely harmless; ignore it. > > True.. but flagging completely harmless messages with "failed" and "IOERROR" > is bound to generate lots and lots of questions. If it does not tell the > world anything useful let's please get rid of it. Agreed. If they are harmless and meaningless, please axe them. They are a flood of -questions questions waiting to happen. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 17:49:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from doorstop.webtv.net (doorstop.webtv.net [207.46.121.10]) by hub.freebsd.org (Postfix) with ESMTP id 5CD9437BB25 for ; Tue, 25 Jul 2000 17:49:08 -0700 (PDT) (envelope-from josb@corp.webtv.net) Received: by doorstop.webtv.net; id RAA27781; Tue, 25 Jul 2000 17:46:57 -0700 (PDT) Received: from unknown(157.57.212.23) by svc-egress.artemis.com via smap (V5.0) id xma027545; Tue, 25 Jul 00 17:46:08 -0700 Received: (qmail 316 invoked by uid 3215); 26 Jul 2000 00:48:19 -0000 Date: Tue, 25 Jul 2000 17:48:18 -0700 From: Jos Backus To: current@freebsd.org Subject: Still seeing /kernel: mfs_badop[vop_getwritemount] = 45 Message-ID: <20000725174818.A311@traitor.artemis.com> 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 Even with version 1.54 of mfs_vnops.c and a freshly built world and booted kernel (with ``options MFS''), I am still seeing these. What could I be missing? Thanks, -- Jos Backus WebTV Networks, Inc., Mountain View, CA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 18:17:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id 6FC3637BD25 for ; Tue, 25 Jul 2000 18:17:40 -0700 (PDT) (envelope-from gdinolt@pacbell.net) Received: from pacbell.net ([63.199.30.114]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FYA0007Z676QW@mta5.snfc21.pbi.net> for current@freebsd.org; Tue, 25 Jul 2000 18:16:19 -0700 (PDT) Date: Tue, 25 Jul 2000 18:17:03 -0700 From: "George W. Dinolt" Subject: Even with version 1.54 of mfs_vnops.c and a freshly built world and booted kernel (with ``options MFS''), I am still seeing these. What could I be missing? To: current@freebsd.org Cc: josb@corp.webtv.net Message-id: <397E3C0F.6D4E6980@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, -- Jos Backus WebTV Networks, Inc., Mountain View, CARe: Still seeing /kernel: mfs_badop[vop_getwritemount] = 45 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jos Backus wrote: >Even with version 1.54 of mfs_vnops.c and a freshly built world and booted >kernel (with ``options MFS''), I am still seeing these. What could I be >missing? > >Thanks, >-- >Jos Backus >WebTV Networks, Inc., Mountain View, CA I can confirm that on my system with world built from sources cvsuped on Sunday and a kernel just built from sources cvsuped today, I see these messages with an mfs mounted /tmp. Regards, George Dinolt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 25 22:48:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DFE2D37B572; Tue, 25 Jul 2000 22:48:26 -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 XAA29727; Tue, 25 Jul 2000 23:48:25 -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 XAA27083; Tue, 25 Jul 2000 23:48:01 -0600 (MDT) Message-Id: <200007260548.XAA27083@harmony.village.org> To: Hajimu UMEMOTO Subject: Re: multicast + PCCard NIC = kernel panic? Cc: jkh@zippy.osd.bsdi.com, iwasaki@jp.FreeBSD.org, jkh@FreeBSD.ORG, current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Wed, 26 Jul 2000 01:48:19 +0900." <20000726.014819.59534040.ume@mahoroba.org> References: <20000726.014819.59534040.ume@mahoroba.org> <7676.964529079@localhost> <200007251535.JAA20062@harmony.village.org> Date: Tue, 25 Jul 2000 23:48:01 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000726.014819.59534040.ume@mahoroba.org> Hajimu UMEMOTO writes: : Yes, panic will happen only during detach the card. So, install : should be OK. I'll MFC after 4.1-RELEASE is out. : Thank you for your suggestion and sorry for makeing this situation. Thank you for letting us know of the problem. There's no need to appologize for finding bugs like this. Please go ahead and MFC once 4.1 release is out the door. Thanks for finding this! Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 0:28:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8F80D37B5F4 for ; Wed, 26 Jul 2000 00:28:33 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA32575; Wed, 26 Jul 2000 00:28:27 -0700 Date: Wed, 26 Jul 2000 00:28:30 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "George W. Dinolt" Cc: current@FreeBSD.ORG, josb@corp.webtv.net Subject: Re: Even with version 1.54 of mfs_vnops.c and a freshly built world and booted kernel (with ``options MFS''), I am still seeing these. What could I be missing? In-Reply-To: <397E3C0F.6D4E6980@pacbell.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 > >Thanks, > >-- > >Jos Backus > >WebTV Networks, Inc., Mountain View, CA > > I can confirm that on my system with world built from sources cvsuped on > Sunday and a kernel just built from sources cvsuped today, I see these > messages with an mfs mounted /tmp. Hmm. They went away for me- I thought, but no, you're right. They're still there. This is what I actually use to get rid of them: Index: mfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/mfs/mfs_vnops.c,v retrieving revision 1.53 diff -u -r1.53 mfs_vnops.c --- mfs_vnops.c 2000/05/05 09:59:07 1.53 +++ mfs_vnops.c 2000/07/25 21:47:09 @@ -80,6 +80,7 @@ { &vop_reclaim_desc, (vop_t *) mfs_reclaim }, { &vop_strategy_desc, (vop_t *) mfs_strategy }, { &vop_unlock_desc, (vop_t *) vop_defaultop }, + { &vop_getwritemount_desc, (vop_t *) vop_stdgetwritemount }, { NULL, NULL } }; static struct vnodeopv_desc mfs_vnodeop_opv_desc = To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 1:10:45 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 5294F37BE45; Wed, 26 Jul 2000 01:10:43 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 07BA51C66; Wed, 26 Jul 2000 04:10:42 -0400 (EDT) Date: Wed, 26 Jul 2000 04:10:42 -0400 From: Bill Fumerola To: current@freebsd.org, marcel@freebsd.org Subject: installkernel broken? Message-ID: <20000726041041.T51462@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A little context.... CROSSENV= MAKEOBJDIRPREFIX=${OBJTREE} \ COMPILER_PATH=${WORLDTMP}/usr/libexec:${WORLDTMP}/usr/bin \ LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib \ OBJFORMAT_PATH=${WORLDTMP}/usr/libexec \ PERL5LIB=${WORLDTMP}/usr/libdata/perl/5.6.0 STRICTTMPPATH= ${WORLDTMP}/usr/sbin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games INSTALLTMP= ${TMPDIR}/install.${TMPPID} IMAKEENV= ${CROSSENV} \ PATH=${STRICTTMPPATH}:${INSTALLTMP} installkernel: cd ${KRNLOBJDIR}/${INSTALLKERNEL}; \ ${IMAKEENV} MACHINE=${MACHINE} KERNEL=${INSTALLKERNEL} \ ${MAKE} KERNEL=${INSTALLKERNEL} install Now, why are we looking in ${WORLDTMP}/usr/sbin when what we should be looking in is ${WORLDTMP}/usr.sbin? Same with /usr/bin != /usr.bin... Disgruntled and reverting back to making kernels the way they were intended, -- 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 Wed Jul 26 2:18:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id C592837B893; Wed, 26 Jul 2000 02:18:23 -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-31.mail.demon.net with esmtp (Exim 2.12 #1) id 13HNKW-0001v1-0V; Wed, 26 Jul 2000 10:18:21 +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 KAA93701; Wed, 26 Jul 2000 10:17:56 +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 BAA30643; Wed, 26 Jul 2000 01:19:18 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Wed, 26 Jul 2000 01:19:18 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List , USB BSD list , FreeBSD STABLE Mailing List Cc: Kent Subject: WARNING: IBM microdrive in USB based CF II reader 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 Warning: Do not use IBM Microdrives in any USB based CF II readers, like the SmartMedia ImageMate until further notice. I've had reports of 2 drives breaking in a SmartMedia ImageMedia. They are PHYSICALLY broken and will no longer work. Nick -- 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 Wed Jul 26 3:33:21 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 1A68D37B5F6; Wed, 26 Jul 2000 03:33:13 -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.15 #1) id 13HOUt-00004Y-00; Wed, 26 Jul 2000 12:33:07 +0200 From: Sheldon Hearn To: brian@FreeBSD.org Cc: current@FreeBSD.org Subject: if_tun.ko seems broken Date: Wed, 26 Jul 2000 12:33:07 +0200 Message-ID: <281.964607587@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Brian, Does this have anything to do with your recent change to if_tun.c? Ciao, Sheldon. Script started on Wed Jul 26 12:28:35 2000 # pwd /root # date Wed Jul 26 12:28:39 SAST 2000 # uname -a FreeBSD axl.ops.uunet.co.za 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Jul 26 12:01:00 SAST 2000 sheldonh@axl.ops.uunet.co.za:/usr/obj/usr/src/sys/AXL i386 # ls -l /kernel /modules/if_tun.ko -r-xr-xr-x 1 root wheel 1632582 Jul 26 12:07 /kernel -r-xr-xr-x 1 root wheel 14259 Jul 26 12:07 /modules/if_tun.ko # ifconfig fxp0: flags=8843 mtu 1500 inet 196.31.2.163 netmask 0xffffffe0 broadcast 196.31.2.191 ether 00:d0:b7:74:3c:12 media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 # kldstat Id Refs Address Size Name 1 5 0xc0100000 1a2634 kernel 2 1 0xc0c41000 5000 ccd.ko 3 1 0xc0d11000 10000 randomdev.ko 4 1 0xc0d29000 4e000 nfs.ko 5 1 0xc0daa000 11000 linux.ko # ifconfig tun0 inet 10.0.0.1 ifconfig: interface tun0 does not exist # kldstat Id Refs Address Size Name 1 6 0xc0100000 1a2634 kernel 2 1 0xc0c41000 5000 ccd.ko 3 1 0xc0d11000 10000 randomdev.ko 4 1 0xc0d29000 4e000 nfs.ko 5 1 0xc0daa000 11000 linux.ko 6 1 0xc0e45000 4000 if_tun.ko # kldunload if_tun kldunload: can't unload file: Invalid argument Jul 26 12:29:36 axl /kernel: if_tun module unload - not possible for this module type # kldstat Id Refs Address Size Name 1 6 0xc0100000 1a2634 kernel 2 1 0xc0c41000 5000 ccd.ko 3 1 0xc0d11000 10000 randomdev.ko 4 1 0xc0d29000 4e000 nfs.ko 5 1 0xc0daa000 11000 linux.ko 6 1 0xc0e45000 4000 if_tun.ko # exit Script done on Wed Jul 26 12:29:49 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 4: 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 E12B937BA6E; Wed, 26 Jul 2000 04:08:24 -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.15 #1) id 13HP2w-00009x-00; Wed, 26 Jul 2000 13:08:18 +0200 From: Sheldon Hearn To: brian@FreeBSD.org Cc: current@FreeBSD.org Subject: Re: if_tun.ko seems broken In-reply-to: Your message of "Wed, 26 Jul 2000 12:33:07 +0200." <281.964607587@axl.ops.uunet.co.za> Date: Wed, 26 Jul 2000 13:08:18 +0200 Message-ID: <616.964609698@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jul 2000 12:33:07 +0200, Sheldon Hearn wrote: > Does this have anything to do with your recent change to if_tun.c? Nope. I've reverted rev 1.75 of if_tun.c and the behaviour persists. Someone locally insists that the ifconfig line ifconfig tun0 inet 10.0.0.1 should work. Any ideas? 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 Jul 26 4:14:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ctimail3.com (main1.my3mail.com [203.80.96.151]) by hub.freebsd.org (Postfix) with ESMTP id CD58237BE61 for ; Wed, 26 Jul 2000 04:14:47 -0700 (PDT) (envelope-from July3@wsi-hk.com) Received: from oemcomputer27 (207user29.ctimail3.com [203.80.207.29]) by mail.ctimail3.com (8.9.3/8.9.3) with SMTP id TAA02286 for ; Wed, 26 Jul 2000 19:15:05 +0800 (HKT) Message-Id: <200007261115.TAA02286@mail.ctimail3.com> From: "Peter Forsythe" To: "freebsd-current@freebsd.org" Date: Wed, 26 Jul 2000 19:11:11 +0800 Subject: Workplace English and Summer Specials Reply-To: July3@wsi-hk.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Priority: 3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [This email is an update of Hong Kong government's Workplace English Campaign, and of Wall Street Institute English specials for July. If you wish to be removed, or are not in Hong Kong, please click on remove@wsi-hk.com]. The Workplace English Campaign of the Hong Kong government is now in Phase II -- which is significantly more flexible than Phase I, including funding up to $HK4,500. We at Wall Street Institute have assisted over 500 individual applications. Please contact us if you would like to know how you or your colleagues benefit from this program -- 2575 6888. SUMMER SPECIALS: Those enrolling in July are eligible for THREE FREE MONTHS of English learning. Anyone enrolling in July can also take part in a draw to win a TWO WEEK TRIP to Toronto, Sydney or London, including accommodation. Phone us for more details (2575 6888) or fill in the form below and fax or email by return. Looking forward to hearing from you. Peter Forsythe Fax form to 2575 1999 or email to July@wsi-hk.com: ---------------------------------------------------------------- Please send me more information on WEC and Summer Specials: Name _____________________________ Address___________________________ Phone_____________________________ Fax_______________________________ ------------------------------------------------------------------ (For remove, put "remove" in subject line or click on remove@wsi-hk.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 4:26:28 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 A6C8737BE9F; Wed, 26 Jul 2000 04:26:14 -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.15 #1) id 13HPJt-00006b-00; Wed, 26 Jul 2000 13:25:49 +0200 From: Sheldon Hearn To: Kirk McKusick Cc: green@FreeBSD.org, current@FreeBSD.org Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-reply-to: Your message of "Tue, 25 Jul 2000 11:28:47 MST." <200007251828.LAA62730@freefall.freebsd.org> Date: Wed, 26 Jul 2000 13:25:49 +0200 Message-ID: <408.964610749@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Kirk, On Tue, 25 Jul 2000 11:28:47 MST, Kirk McKusick wrote: > Modified files: > sys/kern vfs_bio.c > Log: > Now that buffer locks can be recursive, we need to delete the panics > that complain about them. This looks related. I get it pretty consistently on shutdown, provided the machine did some work subsequent to going multi-user. Ciao, Sheldon. Script started on Wed Jul 26 13:20:40 2000 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 2842624 initial pcb at 247480 panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking panic messages: --- --- #0 boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:303 303 dumppcb.pcb_cr3 = rcr3(); (kgdb) back #0 boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:303 #1 0xc0146bb5 in panic (fmt=0xc02072a0 "lockmgr: pid %d, not %s %d unlocking") at /usr/src/sys/kern/kern_shutdown.c:553 #2 0xc01418d0 in lockmgr (lkp=0xc0ea3c00, flags=6, interlkp=0xc8f8842c, p=0xc84bfe00) at /usr/src/sys/kern/kern_lock.c:382 #3 0xc017509f in vop_stdunlock (ap=0xc84c5e48) at /usr/src/sys/kern/vfs_default.c:255 #4 0xc01b6eed in ufs_vnoperate (ap=0xc84c5e48) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2275 #5 0xc01b1e4f in ufs_inactive (ap=0xc84c5e78) at vnode_if.h:865 #6 0xc01b6eed in ufs_vnoperate (ap=0xc84c5e78) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2275 #7 0xc0177e1a in vput (vp=0xc8f883c0) at vnode_if.h:794 #8 0xc01af12b in ffs_sync (mp=0xc0c65200, waitfor=2, cred=0xc0721780, p=0xc0259de0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:955 #9 0xc0179d9d in sync (p=0xc0259de0, uap=0x0) at /usr/src/sys/kern/vfs_syscalls.c:551 #10 0xc01465eb in boot (howto=0) at /usr/src/sys/kern/kern_shutdown.c:225 #11 0xc01463ec in reboot (p=0xc84bfe00, uap=0xc84c5f80) at /usr/src/sys/kern/kern_shutdown.c:146 #12 0xc01edea9 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077936612, tf_esi = -1077936624, tf_ebp = -1077936836, tf_isp = -934518828, 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 /usr/src/sys/i386/i386/trap.c:1128 #13 0xc01e2bb5 in Xint0x80_syscall () #14 0x80486ee in ?? () #15 0x8048478 in ?? () #16 0x8048139 in ?? () (kgdb) quit Script done on Wed Jul 26 13:20:49 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 5: 5:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from castle.jp.freebsd.org (castle.jp.FreeBSD.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 2500B37BED2 for ; Wed, 26 Jul 2000 05:05:38 -0700 (PDT) (envelope-from matusita@jp.freebsd.org) Received: from localhost (localhost [127.0.0.1]) by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id VAA73927 for ; Wed, 26 Jul 2000 21:05:35 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Molpe) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 36 From: Makoto MATSUSHITA To: current@freebsd.org Subject: FYI: current.jp.freebsd.org, yet another SNAPSHOTs service Date: Wed, 26 Jul 2000 21:05:32 +0900 Message-Id: <20000726210532J.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've already introduced before (last Auguest), but here it is again; we have updated our service host and add some services. current.jp.freebsd.org (CAUTION: not 'current.freebsd.org') is a yet another daily SNAPSHOTs service host. Service contents are almost the same of current.freebsd.org (provides everyday snapshots), however, others are different. Here is a summary: - Build FreeBSD with 'USA_RESIDENT=NO'. Yes, librsaINTL is included. BE CAREFUL IF YOU ARE USA RESIDENTS. - logfile, bzip2-ed /usr/obj, live filesystem are also provided. You can easily checks what's the release-breaker, installs FreeBSD with 'make installworld', fetch some commands without getting huge 'bin' distribution. - Web-browsable FreeBSD code with global(1). You can do checking hyperlinked codes and searching with function name easily. Moreover, we have added a new service: - Package mirroring already available at current.freebsd.org. - Bootable installable CD-ROM, of course both 4-stable/-current (with or without packages), and *both* branches in ONE CD-ROM (you can select 4-stable/-current installation after booting from CD-ROM). - Services via IPv6 and IPv4. You can install FreeBSD snapshots from IPv6-only network. Anyway, if you are living in the area of USA_RESIDENT=NO, check and . If you have any questions, please feel free to contact to the service administrator, buildadm@jp.FreeBSD.org. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 6:36:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id 9B34037BE98 for ; Wed, 26 Jul 2000 06:36:23 -0700 (PDT) (envelope-from gdinolt@pacbell.net) Received: from pacbell.net ([63.199.30.114]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FYB00AYC4EOA1@mta5.snfc21.pbi.net> for current@freebsd.org; Wed, 26 Jul 2000 06:35:12 -0700 (PDT) Date: Wed, 26 Jul 2000 06:35:57 -0700 From: "George W. Dinolt" Subject: Re: Even with version 1.54 of mfs_vnops.c and a freshly built world and booted kernel (with ``options MFS''), I am still seeing these. What could I be missing? To: mjacob@feral.com Cc: current@freebsd.org, josb@corp.webtv.net Message-id: <397EE93C.D81F08F2@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mahtew Jacob wrote: >Hmm. They went away for me- I thought, but no, you're right. They're still >there. This is what I actually use to get rid of them: > >Index: mfs_vnops.c >=================================================================== >RCS file: /home/ncvs/src/sys/ufs/mfs/mfs_vnops.c,v >retrieving revision 1.53 >diff -u -r1.53 mfs_vnops.c >--- mfs_vnops.c 2000/05/05 09:59:07 1.53 >+++ mfs_vnops.c 2000/07/25 21:47:09 >@@ -80,6 +80,7 @@ > { &vop_reclaim_desc, (vop_t *) mfs_reclaim }, > { &vop_strategy_desc, (vop_t *) mfs_strategy }, > { &vop_unlock_desc, (vop_t *) vop_defaultop }, >+ { &vop_getwritemount_desc, (vop_t *) vop_stdgetwritemount }, > { NULL, NULL } > }; > static struct vnodeopv_desc mfs_vnodeop_opv_desc = I have applied the patch and rebuilt my kernel. This seems to have fixed the problem for me. I will keep monitoring the situation. Maybe this can get committed to -current? Thanks, George Dinolt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 8:46:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id BED0937B932; Wed, 26 Jul 2000 08:46:17 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13HT56-0006Qf-00; Wed, 26 Jul 2000 16:26:48 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13HT56-0003BN-00; Wed, 26 Jul 2000 16:26:48 +0100 Date: Wed, 26 Jul 2000 16:26:48 +0100 From: Ben Smithurst To: Sheldon Hearn Cc: brian@FreeBSD.org, current@FreeBSD.org Subject: Re: if_tun.ko seems broken Message-ID: <20000726162648.D28657@strontium.scientia.demon.co.uk> References: <281.964607587@axl.ops.uunet.co.za> <616.964609698@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <616.964609698@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > On Wed, 26 Jul 2000 12:33:07 +0200, Sheldon Hearn wrote: > >> Does this have anything to do with your recent change to if_tun.c? > > Nope. I've reverted rev 1.75 of if_tun.c and the behaviour persists. > Someone locally insists that the ifconfig line > > ifconfig tun0 inet 10.0.0.1 > > should work. Any ideas? I think the device needs to be opened before you can do anything with it. PPP of course does this for you, but if you want to ifconfig it yourself you might try something like ``dd if=/dev/tun0 of=/dev/null count=0'' first. That makes ifconfig work for me at least, I'm not sure if it's the "right" way. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 8:56:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 2666737BB82; Wed, 26 Jul 2000 08:56:05 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 02C70137; Wed, 26 Jul 2000 08:56:03 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id IAA16891; Wed, 26 Jul 2000 08:56:03 -0700 (PDT) Message-ID: <397F0A13.E2127CFA@cup.hp.com> Date: Wed, 26 Jul 2000 08:56:03 -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: Bill Fumerola Cc: current@freebsd.org, marcel@freebsd.org Subject: Re: installkernel broken? References: <20000726041041.T51462@jade.chc-chimes.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: > STRICTTMPPATH= ${WORLDTMP}/usr/sbin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games > INSTALLTMP= ${TMPDIR}/install.${TMPPID} > IMAKEENV= ${CROSSENV} \ > PATH=${STRICTTMPPATH}:${INSTALLTMP} > > installkernel: > cd ${KRNLOBJDIR}/${INSTALLKERNEL}; \ > ${IMAKEENV} MACHINE=${MACHINE} KERNEL=${INSTALLKERNEL} \ > ${MAKE} KERNEL=${INSTALLKERNEL} install > > Now, why are we looking in ${WORLDTMP}/usr/sbin when what we should be > looking in is ${WORLDTMP}/usr.sbin? Same with /usr/bin != /usr.bin... WORLDTMP is a place to *install* binaries we made during the build. We don't install in /usr.bin or /usr.sbin; we install in /usr/bin and /usr/sbin resp. > Disgruntled and reverting back to making kernels the way they were intended, So, what's broken then? -- 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 Wed Jul 26 9:45:30 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 7147437BBAE; Wed, 26 Jul 2000 09:45:27 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 8AD931C6B; Wed, 26 Jul 2000 12:45:23 -0400 (EDT) Date: Wed, 26 Jul 2000 12:45:23 -0400 From: Bill Fumerola To: Marcel Moolenaar Cc: current@freebsd.org, marcel@freebsd.org Subject: Re: installkernel broken? Message-ID: <20000726124523.U51462@jade.chc-chimes.com> References: <20000726041041.T51462@jade.chc-chimes.com> <397F0A13.E2127CFA@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <397F0A13.E2127CFA@cup.hp.com>; from marcel@cup.hp.com on Wed, Jul 26, 2000 at 08:56:03AM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 26, 2000 at 08:56:03AM -0700, Marcel Moolenaar wrote: > > Now, why are we looking in ${WORLDTMP}/usr/sbin when what we should be > > looking in is ${WORLDTMP}/usr.sbin? Same with /usr/bin != /usr.bin... > > WORLDTMP is a place to *install* binaries we made during the build. We > don't install in /usr.bin or /usr.sbin; we install in /usr/bin and > /usr/sbin resp. And then we try and install the kernel using those utilties that are in directories that don't exist: crazyhorse# make kernel=GENERIC installkernel cd /usr/obj/usr/src/sys/GENERIC; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0 PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/tmp/install.1532 MACHINE=i386 KERNEL=GENERIC make KERNEL=GENERIC install make: not found *** Error code 127 crezyhorse# ls -l /usr/obj/usr/src/{,i386/}usr{.,/}{s,}bin/make/make ls: /usr/obj/usr/src/i386/usr.bin/make: No such file or directory ls: /usr/obj/usr/src/i386/usr.sbin/make: No such file or directory ls: /usr/obj/usr/src/i386/usr/bin/make: No such file or directory ls: /usr/obj/usr/src/i386/usr/sbin/make: No such file or directory ls: /usr/obj/usr/src/usr.sbin/make: No such file or directory ls: /usr/obj/usr/src/usr/bin/make: No such file or directory ls: /usr/obj/usr/src/usr/sbin/make: No such file or directory -rwxr-xr-x 1 root wheel 112614 Jul 26 08:20 /usr/obj/usr/src/usr.bin/make/make > > Disgruntled and reverting back to making kernels the way they were intended, > > So, what's broken then? Look where we define the PATH and look where I finally found make. We seem to not be sticking it in the places we look to build with virgin binaries. -- 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 Wed Jul 26 10: 4:20 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 0495737BC67; Wed, 26 Jul 2000 10:04:17 -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 43A2911E4; Wed, 26 Jul 2000 10:03:14 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id KAA19733; Wed, 26 Jul 2000 10:02:40 -0700 (PDT) Message-ID: <397F19B0.B0A1FF71@cup.hp.com> Date: Wed, 26 Jul 2000 10:02:40 -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: Bill Fumerola Cc: current@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: installkernel broken? References: <20000726041041.T51462@jade.chc-chimes.com> <397F0A13.E2127CFA@cup.hp.com> <20000726124523.U51462@jade.chc-chimes.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: > > > WORLDTMP is a place to *install* binaries we made during the build. We > > don't install in /usr.bin or /usr.sbin; we install in /usr/bin and > > /usr/sbin resp. > > And then we try and install the kernel using those utilties that are in > directories that don't exist: > > crazyhorse# make kernel=GENERIC installkernel > cd /usr/obj/usr/src/sys/GENERIC; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0 PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/tmp/install.1532 MACHINE=i386 KERNEL=GENERIC make KERNEL=GENERIC install > make: not found > *** Error code 127 Make sure you have /usr/src/Makefile.inc1 rev 1.162 or up. The installkernel was using the wrong buildcontext (ie IMAKEENV). IMAKEENV was changed to have the very restricted path that broke the installkernel target as you describe above. This has been fixed in 1.162. -- 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 Wed Jul 26 10:17:50 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 CAA6B37BB5E; Wed, 26 Jul 2000 10:17:41 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 6314E1C6A; Wed, 26 Jul 2000 13:17:40 -0400 (EDT) Date: Wed, 26 Jul 2000 13:17:40 -0400 From: Bill Fumerola To: Marcel Moolenaar Cc: current@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: installkernel broken? Message-ID: <20000726131740.A51462@jade.chc-chimes.com> References: <20000726041041.T51462@jade.chc-chimes.com> <397F0A13.E2127CFA@cup.hp.com> <20000726124523.U51462@jade.chc-chimes.com> <397F19B0.B0A1FF71@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <397F19B0.B0A1FF71@cup.hp.com>; from marcel@cup.hp.com on Wed, Jul 26, 2000 at 10:02:40AM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 26, 2000 at 10:02:40AM -0700, Marcel Moolenaar wrote: > Make sure you have /usr/src/Makefile.inc1 rev 1.162 or up. The > installkernel was using the wrong buildcontext (ie IMAKEENV). IMAKEENV > was changed to have the very restricted path that broke the > installkernel target as you describe above. This has been fixed in > 1.162. okay. I'm going to go find who made our local cvsup mirror stop mirroring and feed them to the paper shredder. thanks. -- 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 Wed Jul 26 10:28:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9451437BF00 for ; Wed, 26 Jul 2000 10:28:05 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA01547; Wed, 26 Jul 2000 10:27:44 -0700 Date: Wed, 26 Jul 2000 10:27:47 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "George W. Dinolt" Cc: current@freebsd.org, josb@corp.webtv.net Subject: Re: Even with version 1.54 of mfs_vnops.c and a freshly built world and booted kernel (with ``options MFS''), I am still seeing these. What could I be missing? In-Reply-To: <397EE93C.D81F08F2@pacbell.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 Somebody send it to Kirk.... On Wed, 26 Jul 2000, George W. Dinolt wrote: > Mahtew Jacob wrote: > > >Hmm. They went away for me- I thought, but no, you're right. They're > still > >there. This is what I actually use to get rid of them: > > > >Index: mfs_vnops.c > >=================================================================== > >RCS file: /home/ncvs/src/sys/ufs/mfs/mfs_vnops.c,v > >retrieving revision 1.53 > >diff -u -r1.53 mfs_vnops.c > >--- mfs_vnops.c 2000/05/05 09:59:07 1.53 > >+++ mfs_vnops.c 2000/07/25 21:47:09 > >@@ -80,6 +80,7 @@ > > { &vop_reclaim_desc, (vop_t *) mfs_reclaim }, > > { &vop_strategy_desc, (vop_t *) mfs_strategy }, > > { &vop_unlock_desc, (vop_t *) vop_defaultop }, > >+ { &vop_getwritemount_desc, (vop_t *) vop_stdgetwritemount > }, > > { NULL, NULL } > > }; > > static struct vnodeopv_desc mfs_vnodeop_opv_desc = > > I have applied the patch and rebuilt my kernel. This seems to have fixed > the problem for me. I will keep monitoring the situation. Maybe this can > get committed to -current? > > Thanks, > > George Dinolt > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 12: 6:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 021AB37B866; Wed, 26 Jul 2000 12:06:31 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Wed, 26 Jul 2000 15:06:28 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Sheldon Hearn Cc: Kirk McKusick , current@FreeBSD.org Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-Reply-To: <408.964610749@axl.ops.uunet.co.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 Wed, 26 Jul 2000, Sheldon Hearn wrote: > > Hi Kirk, > > On Tue, 25 Jul 2000 11:28:47 MST, Kirk McKusick wrote: > > > Modified files: > > sys/kern vfs_bio.c > > Log: > > Now that buffer locks can be recursive, we need to delete the panics > > that complain about them. > > This looks related. I get it pretty consistently on shutdown, provided > the machine did some work subsequent to going multi-user. [Script cut] Yeah, several people are noticing that one. Robert Watson and I were trying to debug it, but it was really late at night so personally I gave up on it until I could reproduce it here. I got a different one. I'd like to track it down but it hasn't repeated itself (yet?). My call stack was (disregarding ATA's call stack mostly): panic() bufdone() checking that B_DONE's not set (which it is) cluster_callback() calling bp->b_iodone() biodone() calling bufdone() ad_interrupt() calling biodone() I implemented a little circular buffer which holds (calling function, bp) pairs for bufdone(), but so far I have had no crash yet (yay? :-/). When I do, the circular buffer (thanks, Greg!) will help me out to actually debug this instead of just wondering why B_DONE was set. -- 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 Wed Jul 26 12:34:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from incandescent.firedrake.org (incandescent.firedrake.org [195.157.96.1]) by hub.freebsd.org (Postfix) with ESMTP id 1548537BF2D for ; Wed, 26 Jul 2000 12:34:18 -0700 (PDT) (envelope-from float@incandescent.firedrake.org) Received: from float by incandescent.firedrake.org with local (Exim 2.05 #1 (Debian)) id 13HWwX-0008Qm-00; Wed, 26 Jul 2000 20:34:13 +0100 Date: Wed, 26 Jul 2000 20:34:13 +0100 To: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000726203413.A32392@firedrake.org> References: <200007191746.LAA82887@harmony.village.org> <200007191930.PAA99620@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007191930.PAA99620@hda.hda.com>; from dufault@hda.com on Wed, Jul 19, 2000 at 03:30:37PM -0400 From: void Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How does OpenBSD handle this issue? Anyone know? -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 12:58:41 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 EFA3C37BF8D for ; Wed, 26 Jul 2000 12:58:31 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.10.1/8.10.1) id e6QJwRT13115 for current@freebsd.org; Wed, 26 Jul 2000 15:58:27 -0400 (EDT) Date: Wed, 26 Jul 2000 15:58:27 -0400 (EDT) From: Luoqi Chen Message-Id: <200007261958.e6QJwRT13115@lor.watermarkgroup.com> To: current@freebsd.org Subject: page fault at write-only mmapped address Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Because there is no write-only hardware page protection on ia32, a write-only page fault is handled just like a read/write one. But the mi vm layer distinguishes between the write-only and the read/write protections, so if the fault takes place in a write-only region, the vm layer would think that the write-only operation is trying to read from a write-only address and violates the page protection. As a consequence, if you want to use the sound device in mmapped mode, you'll have to map the playback buffer read/write instead of write-only. I'd like to reverse the way read/write and write-only page faults are handled, i.e., handle both of them like a write-only fault. Does anyone know any reason why I shouldn't do that? I'm currently running a kernel with this modification and I have seen no ill-effect so far. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 15:10:29 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 AD70037C3BC; Wed, 26 Jul 2000 15:10:26 -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 PAA86293; Wed, 26 Jul 2000 15:10:25 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 26 Jul 2000 15:10:25 -0700 (PDT) From: Kris Kennaway To: void Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <20000726203413.A32392@firedrake.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 Wed, 26 Jul 2000, void wrote: > How does OpenBSD handle this issue? Anyone know? It looks like they have four different kernel-exported random-number generators: #define RND_RND 0 /* real randomness like nuclear chips */ #define RND_SRND 1 /* strong random source */ #define RND_URND 2 /* less strong random source */ #define RND_PRND 3 /* pseudo random source */ #define RND_ARND 4 /* aRC4 based random number generator */ RND_RND is not implemented. /dev/random (RND_SRND) and /dev/urandom (RND_URND) are very similar to our old system (based on the same code, in fact, and also used in Linux) although OpenBSD use more entropy sources than us. /dev/prandom (RND_PRND): This just returns the output of random() (Why bother?) /dev/arandom (RND_ARND): This uses the arc4 stream cipher to output a stream of bytes based on an internal key, which is periodically (but I don't know how often) reseeded using entropy samples. Much like arc4random(), except it's periodically reseeded (which arc4random() doesn't do, by default). All of these systems have weaknesses (some serious), even if entropy is estimated accurately (there were indications it was not, for our old PRNG). That was the main motivation for moving to a cryptographically well-designed system (Yarrow). 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 Wed Jul 26 15:54:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from doorstop.webtv.net (doorstop.webtv.net [207.46.121.10]) by hub.freebsd.org (Postfix) with ESMTP id 860B137B71A for ; Wed, 26 Jul 2000 15:54:20 -0700 (PDT) (envelope-from josb@corp.webtv.net) Received: by doorstop.webtv.net; id PAA28361; Wed, 26 Jul 2000 15:52:09 -0700 (PDT) Received: from unknown(157.57.212.23) by svc-egress.artemis.com via smap (V5.0) id xma027930; Wed, 26 Jul 00 15:51:05 -0700 Received: (qmail 501 invoked by uid 3215); 26 Jul 2000 22:53:15 -0000 Date: Wed, 26 Jul 2000 15:53:15 -0700 From: Jos Backus To: current@freebsd.org Subject: Mouse frozen in X when returning from text console Message-ID: <20000726155315.A493@traitor.artemis.com> 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 [This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using the ati driver module.] Something I noticed today: switch to text console from X using C-A-F1; upon return, the mouse cursor is frozen. moused appears to still work because I can cut/paste text in the text console. Restarting moused doesn't help. Is anybody else seeing this? Thanks, -- Jos Backus WebTV Networks, Inc., Mountain View, CA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 16:19:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 425B137B6F4 for ; Wed, 26 Jul 2000 16:19:27 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA02916 for ; Wed, 26 Jul 2000 16:19:25 -0700 Date: Wed, 26 Jul 2000 16:18:41 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: more ffs locking 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 Has this been addressed today? This is with an SMP kernel for this morning's sources.... Always seems to happen on a reboot. syncing disks... panic: lockmgr: pid 85061, not exclusive lock holder 0 unlocking mp_lock = 01000001; cpuid = 1; lapic.id = 0c000000 Debugger("panic") Stopped at Debugger+0x34: movb $0,in_Debugger.591 db> t Debugger(c0266012) at Debugger+0x34 panic(c0265100,14c45,c02650e0,0,c8ad7000) at panic+0xa4 lockmgr(c0b09a00,6,c8ad706c,c8b5d740,c92a3e24) at lockmgr+0x2c8 vop_stdunlock(c92a3e40,c92a3e50,c01fe477,c92a3e40,c8ad7000) at vop_stdunlock+0x3a ufs_vnoperate(c92a3e40) at ufs_vnoperate+0x15 ufs_inactive(c92a3e70,c92a3e80,c01a4855,c92a3e70,c8ad7000) at ufs_inactive+0x127 ufs_vnoperate(c92a3e70,c8ad7000,0,c028c480,c8ad7000) at ufs_vnoperate+0x15 vput(c8ad7000,0,c02c5880,c92a3f80,0) at vput+0xa1 ffs_sync(c0aa9000,2,c0719980,c02c5880,c0aa9000) at ffs_sync+0x150 sync(c02c5880,0,c0265ca5,1,c8b5d740) at sync+0xa1 boot(0,c92a3fa0,c0241fa1,c8b5d740,c92a3f80) at boot+0x9b reboot(c8b5d740,c92a3f80,2,0,0) at reboot+0x1c syscall2(2f,2f,2f,0,0) at syscall2+0x219 Xint0x80_syscall() at Xint0x80_syscall+0x2b To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 17:37:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from numbertwo.domainfactory.de (numbertwo.domainfactory.de [194.221.134.226]) by hub.freebsd.org (Postfix) with SMTP id 2BC4A37BF84 for ; Wed, 26 Jul 2000 17:37:45 -0700 (PDT) (envelope-from steele@cloaked.de) Received: (qmail 16847 invoked from network); 27 Jul 2000 00:37:38 -0000 Received: from p3e9b9bca.dip0.t-ipconnect.de (HELO steele.intra) ([62.155.155.202]) (envelope-sender ) by numbertwo.domainfactory.de (qmail-ldap-1.03) with SMTP for ; 27 Jul 2000 00:37:38 -0000 Received: (from steele@localhost) by steele.intra (8.9.3/8.9.3) id CAA11090; Thu, 27 Jul 2000 02:36:02 +0200 (CEST) (envelope-from steele) Date: Thu, 27 Jul 2000 02:36:02 +0200 From: Benedikt Schmidt To: Jos Backus Cc: current@FreeBSD.ORG Subject: Re: Mouse frozen in X when returning from text console Message-ID: <20000727023602.B64338@cloaked.de> References: <20000726155315.A493@traitor.artemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000726155315.A493@traitor.artemis.com>; from josb@corp.webtv.net on Wed, Jul 26, 2000 at 03:53:15PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 26, 2000 at 03:53:15PM -0700, Jos Backus wrote: > [This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using > the ati driver module.] > > Something I noticed today: switch to text console from X using C-A-F1; upon > return, the mouse cursor is frozen. moused appears to still work because I > can cut/paste text in the text console. Restarting moused doesn't help. > > Is anybody else seeing this? Same problem here on current (make world + kernel last week) with Xfree86 4.0.1 using a V3000 and and ps2 mouse. I tried using "Device" "/dev/mouse" with moused and "Device" "/dev/psm0" without moused. With both settings the mouse is frozen after switching back to X. I didn't have this problem with Xfree 4.0. It just appeared when I updated to the new 4.0.1 port. I don't have this problem on Linux using Xfree86 4.0.1 on the same computer. Thanks Benedikt Schhmidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 18:41:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.142.mpoweredpc.net [142.177.193.142]) by hub.freebsd.org (Postfix) with ESMTP id A1FDB37BFBD for ; Wed, 26 Jul 2000 18:41:08 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id WAA32393; Wed, 26 Jul 2000 22:38:47 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 26 Jul 2000 22:38:46 -0300 (ADT) From: The Hermit Hacker To: Benedikt Schmidt Cc: Jos Backus , current@FreeBSD.ORG Subject: Re: Mouse frozen in X when returning from text console In-Reply-To: <20000727023602.B64338@cloaked.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jul 2000, Benedikt Schmidt wrote: > On Wed, Jul 26, 2000 at 03:53:15PM -0700, Jos Backus wrote: > > [This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using > > the ati driver module.] > > > > Something I noticed today: switch to text console from X using C-A-F1; upon > > return, the mouse cursor is frozen. moused appears to still work because I > > can cut/paste text in the text console. Restarting moused doesn't help. > > > > Is anybody else seeing this? > Same problem here on current (make world + kernel last week) with Xfree86 > 4.0.1 using a V3000 and and ps2 mouse. I tried using "Device" "/dev/mouse" > with moused and "Device" "/dev/psm0" without moused. With both settings the > mouse is frozen after switching back to X. > > I didn't have this problem with Xfree 4.0. It just appeared when I updated > to the new 4.0.1 port. > I don't have this problem on Linux using Xfree86 4.0.1 on the same computer. Make that three ... same environment except a GeoForce256 Video card ... all worked well with XFree4.0 ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 20:12:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp4.port.ru (mx5.port.ru [194.67.23.40]) by hub.freebsd.org (Postfix) with ESMTP id 70BE537B91F for ; Wed, 26 Jul 2000 20:12:41 -0700 (PDT) (envelope-from kabaev@mail.ru) Received: from adsl-141-154-14-76.bellatlantic.net ([141.154.14.76] helo=kan.ne.mediaone.net) by smtp4.port.ru with esmtp (Exim 3.14 #4) id 13He6A-000EK0-00; Thu, 27 Jul 2000 07:12:38 +0400 Received: (from kan@localhost) by kan.ne.mediaone.net (8.9.3/8.9.3) id XAA01923; Wed, 26 Jul 2000 23:12:34 -0400 (EDT) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.4.0.FreeBSD:000726231234:354=_" In-Reply-To: Date: Wed, 26 Jul 2000 23:12:34 -0400 (EDT) From: "Alexander N. Kabaev" To: The Hermit Hacker Subject: Re: Mouse frozen in X when returning from text console Cc: current@FreeBSD.ORG, Jos Backus , Benedikt Schmidt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.4.0.FreeBSD:000726231234:354=_ Content-Type: text/plain; charset=us-ascii There was a patch floating around which fixed these mouse problems for me. --_=XFMail.1.4.0.FreeBSD:000726231234:354=_ Content-Disposition: attachment; filename="XFree86-patch" Content-Transfer-Encoding: base64 Content-Description: XFree86-patch Content-Type: application/octet-stream; name=XFree86-patch; SizeOnDisk=1062 LS0tIHByb2dyYW1zL1hzZXJ2ZXIvaHcveGZyZWU4Ni9pbnB1dC9tb3VzZS9tb3VzZS5jLm9yaWcJ U3VuIEp1bCAyMyAxNzo1MDoxMCAyMDAwCisrKyBwcm9ncmFtcy9Yc2VydmVyL2h3L3hmcmVlODYv aW5wdXQvbW91c2UvbW91c2UuYwlTdW4gSnVsIDIzIDE3OjU0OjIyIDIwMDAKQEAgLTY5MiwxMCAr NjkyLDE1IEBACiAJICAgIHBNc2UtPnByb3RvY29sSUQgPSBwcm90b2NvbElEOwogCX0KICAgICB9 CisjaWZuZGVmIF9fRnJlZUJTRF9fCiAgICAgbWVtY3B5KHBNc2UtPnByb3RvUGFyYSwgcHJvdG9b cE1zZS0+cHJvdG9jb2xJRF0sIHNpemVvZihwTXNlLT5wcm90b1BhcmEpKTsKKyNlbmRpZgogICAg IGlmIChhdXRvbWF0aWMpIHsKIAkKIAlpZiAobmFtZSkgeworI2lmZGVmIF9fRnJlZUJTRF9fCisg ICAgICAgbWVtY3B5KHBNc2UtPnByb3RvUGFyYSwgcHJvdG9bcE1zZS0+cHJvdG9jb2xJRF0sIHNp emVvZihwTXNlLT5wcm90b1BhcmEpKTsKKyNlbmRpZgogCSAgICAvKiBQb3NzaWJsZSBwcm90b1Bh cmEgb3ZlcnJpZGVzIGZyb20gU2V0dXBBdXRvLiAqLwogCSAgICBmb3IgKGkgPSAwOyBpIDwgc2l6 ZW9mKHBNc2UtPnByb3RvUGFyYSk7IGkrKykKIAkJaWYgKHByb3RvUGFyYVtpXSAhPSAtMSkKLS0t IHByb2dyYW1zL1hzZXJ2ZXIvaHcveGZyZWU4Ni9vcy1zdXBwb3J0L2JzZC9ic2RfbW91c2UuYy5v cmlnCVNhdCBGZWIgMTIgMjI6NDU6NDEgMjAwMAorKysgcHJvZ3JhbXMvWHNlcnZlci9ody94ZnJl ZTg2L29zLXN1cHBvcnQvYnNkL2JzZF9tb3VzZS5jCVN1biBKdWwgMjMgMTc6NTA6MTAgMjAwMApA QCAtMTY1LDcgKzE2NSwxMSBAQAogICAgIG1vZGUucmF0ZSA9IHJhdGUgPiAwID8gcmF0ZSA6IC0x OwogICAgIG1vZGUucmVzb2x1dGlvbiA9IHJlcyA+IDAgPyByZXMgOiAtMTsKICAgICBtb2RlLmFj Y2VsZmFjdG9yID0gLTE7CisjaWZkZWYgX19GcmVlQlNEX18KKyAgICBtb2RlLmxldmVsID0gMTsK KyNlbHNlCiAgICAgbW9kZS5sZXZlbCA9IC0xOworI2VuZGlmCiAgICAgaW9jdGwocEluZm8tPmZk LCBNT1VTRV9TRVRNT0RFLCAmbW9kZSk7CiB9CiAjZW5kaWYK --_=XFMail.1.4.0.FreeBSD:000726231234:354=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 21:33:43 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 08A6B37B70A for ; Wed, 26 Jul 2000 21:33:37 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id IAA00262 for current@freebsd.org; Thu, 27 Jul 2000 08:33:35 +0400 (MSD) (envelope-from ache) Date: Thu, 27 Jul 2000 08:33:30 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: lockmgr panic in sync() Message-ID: <20000727083330.A250@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 This is at current -current, softupdates. Panic happens at reboot, from sync() kernel function: panic: lockmgr: pid 1, not exlusive lock holder 0 unlocking -- 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 Wed Jul 26 21:42: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6095F37B7B9 for ; Wed, 26 Jul 2000 21:42:06 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id VAA03647; Wed, 26 Jul 2000 21:41:26 -0700 Date: Wed, 26 Jul 2000 21:41:29 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: lockmgr panic in sync() In-Reply-To: <20000727083330.A250@nagual.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I already mentioned it.... On Thu, 27 Jul 2000, Andrey A. Chernov wrote: > This is at current -current, softupdates. Panic happens at reboot, from > sync() kernel function: > > panic: lockmgr: pid 1, not exlusive lock holder 0 unlocking > > -- > Andrey A. Chernov > > http://ache.pp.ru/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 22:42:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from crash.ab.videon.ca (crash.ab.videon.ca [206.75.216.220]) by hub.freebsd.org (Postfix) with ESMTP id 2BDFB37C01E for ; Wed, 26 Jul 2000 22:42:12 -0700 (PDT) (envelope-from cwasser@v-wave.com) Received: from flatline (flatline@area51.v-wave.com [24.108.26.39]) by crash.ab.videon.ca (8.9.2/8.9.2) with SMTP id XAA04958 for ; Wed, 26 Jul 2000 23:42:07 -0600 (MDT) Message-Id: Date: Wed, 26 Jul 2000 23:41:57 -0600 X-Priority: 3 From: Chris Wasser X-Mailer: Mail Warrior To: current@freebsd.org MIME-Version: 1.0 Subject: Re: lockmgr panic in sync() Content-Type: Text/Plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8Bit X-Mailer-Version: v3.57 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I saw the exact same error today (just happened to be scanning this mailing list) with 4.1-STABLE after a panic. Original message from: Matthew Jacob >> panic: lockmgr: pid 1, not exlusive lock holder 0 unlocking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 26 23:14:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 1CC9637BB5F for ; Wed, 26 Jul 2000 23:14:51 -0700 (PDT) (envelope-from blaz@amis.net) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 311305D0A; Thu, 27 Jul 2000 08:14:45 +0200 (CEST) Date: Thu, 27 Jul 2000 08:14:45 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Jos Backus Cc: current@freebsd.org Subject: Re: Mouse frozen in X when returning from text console In-Reply-To: <20000726155315.A493@traitor.artemis.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 > Something I noticed today: switch to text console from X using C-A-F1; upon > return, the mouse cursor is frozen. moused appears to still work because I > can cut/paste text in the text console. Restarting moused doesn't help. Yes, I can confirm it. Going back to Xfree 3.3.6 fixes it. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 2:19:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 485F737B7FA; Thu, 27 Jul 2000 02:19:27 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #1) id 13Hjp7-0006mQ-00; Thu, 27 Jul 2000 11:19:25 +0200 Received: from a2ab4.pppool.de ([213.6.42.180] helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.16 #1) id 13Hjp6-0007Oq-00; Thu, 27 Jul 2000 11:19:24 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id LAA00539; Thu, 27 Jul 2000 11:17:04 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200007270917.LAA00539@Magelan.Leidinger.net> Date: Thu, 27 Jul 2000 11:17:03 +0200 (CEST) From: Alexander Leidinger Subject: Problem after recent commits to dev/aic7xxx (aic7880) To: gibbs@freebsd.org Cc: 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, after recent commits to dev/aic7xxxx I get timeouts from my hardware at the SCSI-Bus (a CD-ROM an a CDR) and it needs very long to boot. An old kernel boots just fine. The (stripped down) output of a verbose boot: ---snip--- ahc0: port 0xb000-0xb0ff mem 0xd9800000-0xd9800fff irq 9 at device 6.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: Low byte termination Enabled ahc0: High byte termination Enabled ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 423 instructions downloaded BIOS Geometries: 0:03ffda3f 0..1023=1024 cylinders, 0..218=219 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Waiting 5 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: target 1 synchronous at 10.0MHz, offset = 0xf (probe2:ahc0:0:2:0): SCB 0x7 - timed out while idle, SEQADDR == 0x195 (probe2:ahc0:0:2:0): Queuing a BDR SCB (probe2:ahc0:0:2:0): SCB 0x7 - timed out while idle, SEQADDR == 0x195 (probe2:ahc0:0:2:0): no longer in timeout, status = 34b ahc0: target 1 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe2:ahc0:0:2:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe2:ahc0:0:2:0): ILLEGAL REQUEST asc:24,0 (probe2:ahc0:0:2:0): Invalid field in CDB ahc0: target 2 synchronous at 20.0MHz, offset = 0xf ahc0: target 1 synchronous at 10.0MHz, offset = 0xf Creating DISK cd0 Creating DISK cd1 pass0 at ahc0 bus 0 target 1 lun 0 pass0: Removable CD-ROM SCSI-2 device pass0: Serial Number 8Y24511C pass0: 10.000MB/s transfers (10.000MHz, offset 15) pass1 at ahc0 bus 0 target 2 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 20.000MB/s transfers (20.000MHz, offset 15) Mounting root from ufs:/dev/ad0s2a ad0s1: type 0xc, start 63, end = 6277634, size 6277572 : OK ad0s2: type 0xa5, start 6290928, end = 40031711, size 33740784 ad0s2: C/H/S end 1023/104/63 (14120945) != end 40031711: invalid (cd1:ahc0:0:2:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ahc0:0:2:0): NOT READY asc:3a,0 (cd1:ahc0:0:2:0): Medium not present cd1 at ahc0 bus 0 target 2 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present start_init: trying /sbin/init (cd0:ahc0:0:1:0): SCB 0x7 - timed out in Message-in phase, SEQADDR == 0x195 (cd0:ahc0:0:1:0): BDR message in message buffer (cd0:ahc0:0:1:0): SCB 0x7 - timed out in Message-in phase, SEQADDR == 0x195 (cd0:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: target 1 using asynchronous transfers ahc0: target 2 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 1 SCBs aborted ahc0: target 1 synchronous at 10.0MHz, offset = 0xf (cd0:ahc0:0:1:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ahc0:0:1:0): NOT READY asc:4,1 (cd0:ahc0:0:1:0): Logical unit is in process of becoming ready cd0 at ahc0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: Serial Number 8Y24511C cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Logical unit is in process of becoming ready ---snip--- And the output of "ident /usr/src/sys/dev/aic7xxxx/* | grep FreeBSD": ---snip--- $FreeBSD: src/sys/dev/aic7xxx/93cx6.c,v 1.6 2000/07/18 20:12:12 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/93cx6.h,v 1.5 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/Makefile,v 1.7 2000/05/27 21:35:47 obrien Exp $ $FreeBSD: src/sys/dev/aic7xxx/ahc_eisa.c,v 1.16 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/ahc_pci.c,v 1.32 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx.c,v 1.47 2000/07/25 20:40:34 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx.h,v 1.21 2000/07/24 22:27:40 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx.reg,v 1.22 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx.seq,v 1.97 2000/07/24 22:27:40 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm.c,v 1.26 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm.h,v 1.9 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm_gram.y,v 1.9 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm_insformat.h,v 1.1 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm_scan.l,v 1.11 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm_symbol.c,v 1.9 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm_symbol.h,v 1.9 2000/07/18 20:12:14 gibbs Exp $ ---snip--- Bye, Alexander. -- Press every key to continue. 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 Thu Jul 27 4:12: 9 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 C5B8A37B54B; Thu, 27 Jul 2000 04:12:02 -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 13Hla1-000OvC-00; Thu, 27 Jul 2000 13:11:57 +0200 From: Sheldon Hearn To: Ben Smithurst Cc: brian@FreeBSD.org, current@FreeBSD.org Subject: Re: if_tun.ko seems broken In-reply-to: Your message of "Wed, 26 Jul 2000 16:26:48 +0100." <20000726162648.D28657@strontium.scientia.demon.co.uk> Date: Thu, 27 Jul 2000 13:11:57 +0200 Message-ID: <95801.964696317@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jul 2000 16:26:48 +0100, Ben Smithurst wrote: > I think the device needs to be opened before you can do anything with > it. PPP of course does this for you, but if you want to ifconfig it > yourself you might try something like ``dd if=/dev/tun0 of=/dev/null > count=0'' first. Ah, okay. Having said this to the person who swore that ifconfig tun0 worked for him, he now remembers that he doesn, in fact, use ppp(8). :-) Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 5: 8:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.43.150]) by hub.freebsd.org (Postfix) with ESMTP id 7C6E637B934; Thu, 27 Jul 2000 05:08:13 -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 JAA00265; Thu, 27 Jul 2000 09:37:11 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Sheldon Hearn Cc: brian@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: if_tun.ko seems broken In-reply-to: Your message of "Wed, 26 Jul 2000 13:08:18 +0200." <616.964609698@axl.ops.uunet.co.za> Date: Thu, 27 Jul 2000 09:37:11 +0200 Message-ID: <263.964683431@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <616.964609698@axl.ops.uunet.co.za>, Sheldon Hearn writes: > >On Wed, 26 Jul 2000 12:33:07 +0200, Sheldon Hearn wrote: > >> Does this have anything to do with your recent change to if_tun.c? > >Nope. I've reverted rev 1.75 of if_tun.c and the behaviour persists. >Someone locally insists that the ifconfig line > > ifconfig tun0 inet 10.0.0.1 > >should work. Any ideas? I think you are seing the "interesting" side effect of the BSD concept of "POINT2POINT" lines. I think we should loose that concept in favour of interfaces using a netmask of 255.255.255.255 and let programs like ppp install a hostroute to the other end when it is reachable. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 5:11:39 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 B4C3E37B7CA; Thu, 27 Jul 2000 05:11:32 -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 13HmTy-000Gah-00; Thu, 27 Jul 2000 14:09:46 +0200 From: Sheldon Hearn To: Poul-Henning Kamp Cc: brian@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: if_tun.ko seems broken In-reply-to: Your message of "Thu, 27 Jul 2000 09:37:11 +0200." <263.964683431@critter.freebsd.dk> Date: Thu, 27 Jul 2000 14:09:46 +0200 Message-ID: <63773.964699786@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jul 2000 09:37:11 +0200, Poul-Henning Kamp wrote: > > ifconfig tun0 inet 10.0.0.1 > > I think you are seing the "interesting" side effect of the BSD > concept of "POINT2POINT" lines. I think that's anotehr issue. Once I'd read 0 bytes from /dev/tun0 with dd(1), I was able to do ifconfig tun0 inet 10.0.0.1 10.0.0.1 which is actually what I wanted. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 5:56:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id B32EE37B5AC; Thu, 27 Jul 2000 05:56:48 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13Hmvw-0008lO-00; Thu, 27 Jul 2000 13:38:40 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13Hmvw-000H7r-00; Thu, 27 Jul 2000 13:38:40 +0100 Date: Thu, 27 Jul 2000 13:38:39 +0100 From: Ben Smithurst To: current@FreeBSD.org, obrien@FreeBSD.org Subject: Broadcast address with DHCP Message-ID: <20000727133839.A59315@strontium.scientia.demon.co.uk> 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 dhclient seems to be broken, it's giving me the all zeroes broadcast address instead of all ones: inet 192.168.91.35 netmask 0xfffffff0 broadcast 192.168.91.32 (should be broadcast 192.168.91.47) Index: dhclient.c =================================================================== RCS file: /usr/cvs/src/contrib/isc-dhcp/client/dhclient.c,v retrieving revision 1.16 diff -u -r1.16 dhclient.c --- dhclient.c 2000/07/20 19:51:37 1.16 +++ dhclient.c 2000/07/27 12:21:38 @@ -1972,7 +1972,7 @@ if (broadcast.len) { client_envadd (ip -> client, prefix, "broadcast_address", - "%s", piaddr (subnet)); + "%s", piaddr (broadcast)); } } } I think this needs fixing. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 7:35:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (oe37.law9.hotmail.com [64.4.8.94]) by hub.freebsd.org (Postfix) with SMTP id 7761F37B95F for ; Thu, 27 Jul 2000 07:35:20 -0700 (PDT) (envelope-from vinxs_@hotmail.com) Received: (qmail 75198 invoked by uid 65534); 27 Jul 2000 14:35:19 -0000 Message-ID: <20000727143519.75197.qmail@hotmail.com> X-Originating-IP: [194.109.60.172] From: "Vincent Bruijnes" To: Subject: test. Date: Thu, 27 Jul 2000 16:34:58 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0031_01BFF7E8.9A99B060" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0031_01BFF7E8.9A99B060 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable how can i unsubscribe from freebsd-current and subcribe to = freebsd-stable, Thanks, Vincent ------=_NextPart_000_0031_01BFF7E8.9A99B060 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
how can i unsubscribe from = freebsd-current and=20 subcribe to freebsd-stable,
 
Thanks, = Vincent
------=_NextPart_000_0031_01BFF7E8.9A99B060-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 7:37:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 1C52037B9CA for ; Thu, 27 Jul 2000 07:37:38 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id JAA71493; Thu, 27 Jul 2000 09:37:30 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Thu, 27 Jul 2000 09:37:30 -0500 (CDT) From: David Scheidt To: Jos Backus Cc: current@freebsd.org Subject: Re: Mouse frozen in X when returning from text console In-Reply-To: <20000726155315.A493@traitor.artemis.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, 26 Jul 2000, Jos Backus wrote: :[This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using :the ati driver module.] : :Something I noticed today: switch to text console from X using C-A-F1; upon :return, the mouse cursor is frozen. moused appears to still work because I :can cut/paste text in the text console. Restarting moused doesn't help. : I don't have this problem, using XFree86 4.0.1, the ati module, /dev/psm0, and a current from early june. I do have a problem that some Solaris applications die horrible deaths trying to display on the FreeBSD box. That's probably neither FreeBSD nor XFree's fault though. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 7:45:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.142.mpoweredpc.net [142.177.193.142]) by hub.freebsd.org (Postfix) with ESMTP id ABCF037B979 for ; Thu, 27 Jul 2000 07:45:15 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id LAA61309; Thu, 27 Jul 2000 11:42:48 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 27 Jul 2000 11:42:48 -0300 (ADT) From: The Hermit Hacker To: David Scheidt Cc: Jos Backus , current@FreeBSD.ORG Subject: Re: Mouse frozen in X when returning from text console In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jul 2000, David Scheidt wrote: > On Wed, 26 Jul 2000, Jos Backus wrote: > > :[This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using > :the ati driver module.] > : > :Something I noticed today: switch to text console from X using C-A-F1; upon > :return, the mouse cursor is frozen. moused appears to still work because I > :can cut/paste text in the text console. Restarting moused doesn't help. > : > > I don't have this problem, using XFree86 4.0.1, the ati module, /dev/psm0, > and a current from early june. I do have a problem that some Solaris One suggestion was made that I might have been the result of the recent changes to the syscons driver ... something about entropy? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 7:57:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id A0D0937BB1D for ; Thu, 27 Jul 2000 07:57:03 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from v-ger.we.lc.ehu.es (lxpxdt.lx.ehu.es [158.227.99.197]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id QAA20089; Thu, 27 Jul 2000 16:56:56 +0200 (MET DST) Received: from we.lc.ehu.es (localhost [127.0.0.1]) by v-ger.we.lc.ehu.es (8.9.3/8.9.3) with ESMTP id QAA01994; Thu, 27 Jul 2000 16:32:09 +0200 (CEST) (envelope-from jose@we.lc.ehu.es) Message-ID: <398047E9.29C6DE70@we.lc.ehu.es> Date: Thu, 27 Jul 2000 16:32:09 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Benedikt Schmidt Cc: Jos Backus , current@FreeBSD.ORG Subject: Re: Mouse frozen in X when returning from text console References: <20000726155315.A493@traitor.artemis.com> <20000727023602.B64338@cloaked.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Benedikt Schmidt wrote: > Same problem here on current (make world + kernel last week) with Xfree86 > 4.0.1 using a V3000 and and ps2 mouse. I tried using "Device" "/dev/mouse" > with moused and "Device" "/dev/psm0" without moused. With both settings the > mouse is frozen after switching back to X. > > I didn't have this problem with Xfree 4.0. It just appeared when I updated > to the new 4.0.1 port. > I don't have this problem on Linux using Xfree86 4.0.1 on the same computer. > This problem is not specifically related to -CURRENT; it happens with XFree86 4.0.1 when the configured mouse protocol is "Auto". Another glitch: "Protocol SysMouse" does not work with moused; however, "Protocol Mousesystems" does. -- JMA ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 8:13:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 2F06C37B9AC for ; Thu, 27 Jul 2000 08:13:21 -0700 (PDT) (envelope-from robd@gmx.net) Received: (qmail 589 invoked by uid 0); 27 Jul 2000 15:13:19 -0000 Received: from pc19f67dc.dip0.t-ipconnect.de (HELO gmx.net) (193.159.103.220) by mail.gmx.net with SMTP; 27 Jul 2000 15:13:19 -0000 Message-ID: <398051BB.E11C06C1@gmx.net> Date: Thu, 27 Jul 2000 17:14:03 +0200 From: Robert Drehmel X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-RELEASE i386) MIME-Version: 1.0 To: Vincent Bruijnes Cc: freebsd-current@FreeBSD.ORG Subject: Re: test. References: <20000727143519.75197.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jul 2000 16:34:58 +0200, "Vincent Bruijnes" wrote: > How can i unsubscribe from freebsd-current and subcribe to freebsd-stable, > > Thanks, Vincent Send a mail to majordomo@FreeBSD.ORG (not to this list) with unsubscribe freebsd-current subscribe freebsd-stable in the message body. Further information can be found at http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL -- Robert Drehmel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 8:32:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.142.mpoweredpc.net [142.177.193.142]) by hub.freebsd.org (Postfix) with ESMTP id A7A2E37B8A6 for ; Thu, 27 Jul 2000 08:32:09 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id MAA62887; Thu, 27 Jul 2000 12:29:57 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 27 Jul 2000 12:29:57 -0300 (ADT) From: The Hermit Hacker To: "Jose M. Alcaide" Cc: Benedikt Schmidt , Jos Backus , current@FreeBSD.ORG Subject: Re: Mouse frozen in X when returning from text console In-Reply-To: <398047E9.29C6DE70@we.lc.ehu.es> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jul 2000, Jose M. Alcaide wrote: > Benedikt Schmidt wrote: > > Same problem here on current (make world + kernel last week) with Xfree86 > > 4.0.1 using a V3000 and and ps2 mouse. I tried using "Device" "/dev/mouse" > > with moused and "Device" "/dev/psm0" without moused. With both settings the > > mouse is frozen after switching back to X. > > > > I didn't have this problem with Xfree 4.0. It just appeared when I updated > > to the new 4.0.1 port. > > I don't have this problem on Linux using Xfree86 4.0.1 on the same computer. > > > > This problem is not specifically related to -CURRENT; it happens with > XFree86 4.0.1 when the configured mouse protocol is "Auto". Another > glitch: "Protocol SysMouse" does not work with moused; however, > "Protocol Mousesystems" does. Mine is set to (5.0-CURRENT): Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "MouseMan" Option "Device" "/dev/ttyd1" EndSection And (4.1RC): Section "Pointer" Protocol "MouseMan" Device "/dev/psm0" BaudRate 1200 Resolution 100 Buttons 3 EndSection To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 9:53:46 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 6EB8237C0FB for ; Thu, 27 Jul 2000 09:53:37 -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 MAA96758 for ; Thu, 27 Jul 2000 12:53:35 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 27 Jul 2000 12:53:34 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-current@FreeBSD.org Subject: Mouse behaving funny since 5.0-CURRENT upgrade 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 using a Micron P133 box with a PS/2 mouse. Up until this morning, I was running 4.0-STABLE from a month or two back. I upgraded to 5.0-CURRENT, and since that time, my mouse has been responding slowly and erratically, jumping as it moves, et al. The mouse daemon seems to be consuming more CPU time than I would hope: 389 root 2 0 880K 504K select 0:02 16.28% 5.37% moused (it has been as high as 9%) I'm using the default arguments to moused, with moused enabled in /etc/rc.conf. I'm not sure what changed, but it would be nice if it hadn't :-). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 13:36: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id E108B37BEDC; Thu, 27 Jul 2000 13:36:01 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.1+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e6RKZop41068; Fri, 28 Jul 2000 05:35:51 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: mobile@freebsd.org Cc: current@freebsd.org Subject: CFR: apm debug print cleanup and display on/off improvement X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000728053540O.iwasaki@jp.FreeBSD.org> Date: Fri, 28 Jul 2000 05:35:40 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I worked apm debug print cleanup to avoid re-build kernel with APM_DEUG (this kernel option seems unavailable for now) for obtaining debug messages on apm. http://people.freebsd.org/~iwasaki/apm/apm-debug.diff The debug flag can be controlled by sysctl interface and loader setting "debug.apm_debug=1" with this. This patch also includes some enhancements from linux on display control by apm -d. I'm expecting that we can see some improvements on some laptops where apm -d doesn't work correctly so far. I'll commit this comming week end if no objections. Thanks # Yes, I just want to finish apm related work before we concentrate # on ACPI stuff :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 14:54:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122]) by hub.freebsd.org (Postfix) with SMTP id 0FEF337C0EA for ; Thu, 27 Jul 2000 14:54:40 -0700 (PDT) (envelope-from josb@microsoft.com) Received: from 157.54.9.103 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 27 Jul 2000 14:53:38 -0700 (Pacific Daylight Time) Received: by INET-IMC-04 with Internet Mail Service (5.5.2651.58) id ; Thu, 27 Jul 2000 14:53:44 -0700 Message-ID: <3BE1AD256EC3E24485A10A13452778C701C36DAC@svc-msg-01.northamerica.corp.microsoft.com> From: Jos Backus To: "'Alexander N. Kabaev'" , The Hermit Hacker Cc: current@FreeBSD.ORG, Jos Backus , Benedikt Schmidt Subject: RE: Mouse frozen in X when returning from text console Date: Thu, 27 Jul 2000 14:54:25 -0700 X-Mailer: Internet Mail Service (5.5.2651.58) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This patch does indeed fix the problem here. Thanks! This should really make it into 4.0.2... ---Jos > -----Original Message----- > From: Alexander N. Kabaev [mailto:kabaev@mail.ru] > Sent: Wednesday, July 26, 2000 8:13 PM > To: The Hermit Hacker > Cc: current@FreeBSD.ORG; Jos Backus; Benedikt Schmidt > Subject: Re: Mouse frozen in X when returning from text console > > > There was a patch floating around which fixed these mouse > problems for me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 15:53:55 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 105DF37C154 for ; Thu, 27 Jul 2000 15:53:43 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 1071 invoked from network); 27 Jul 2000 22:53:40 -0000 Received: from acs-24-154-24-131.zoominternet.net (HELO cvzoom.net) (24.154.24.131) by ns.cvzoom.net with SMTP; 27 Jul 2000 22:53:40 -0000 Message-ID: <3980BD72.C3540196@cvzoom.net> Date: Thu, 27 Jul 2000 18:53:38 -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: Robert Watson Cc: freebsd-current@FreeBSD.org Subject: Re: Mouse behaving funny since 5.0-CURRENT upgrade References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Watson wrote: > > I'm using a Micron P133 box with a PS/2 mouse. Up until this morning, I > was running 4.0-STABLE from a month or two back. I upgraded to > 5.0-CURRENT, and since that time, my mouse has been responding slowly and > erratically, jumping as it moves, et al. > I'm using the default arguments to moused, with moused enabled in > /etc/rc.conf. I'm not sure what changed, but it would be nice if it > hadn't :-). Yep. It's been that way in 5.0-current for about 2-3 weeks now. When I use /dev/sysmouse in X, my mouse is really jumpy. It's so bad that I don't use moused anymore in X. When I use my mouse normally, i.e. without moused (/dev/mouse), in X, mouse movements are OK. Also, cursor motion is jumpy as well. Must be the recent commits to syscons. -- - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 17:24: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 96D7637C17A; Thu, 27 Jul 2000 17:23:53 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:/eXMOaQycWEUeRck2nQ5pAWgX6T2fDfw@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id JAA00951; Fri, 28 Jul 2000 09:23:51 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:if4DYpac1vYnrVcB2o8lT0Q8tqTPRiIN@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id JAA02407; Fri, 28 Jul 2000 09:30:43 +0900 (JST) Message-Id: <200007280030.JAA02407@zodiac.mech.utsunomiya-u.ac.jp> To: Donn Miller Cc: Robert Watson , freebsd-current@FreeBSD.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Mouse behaving funny since 5.0-CURRENT upgrade In-reply-to: Your message of "Thu, 27 Jul 2000 18:53:38 -0400." <3980BD72.C3540196@cvzoom.net> References: <3980BD72.C3540196@cvzoom.net> Date: Fri, 28 Jul 2000 09:30:42 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try the attached patch for /sys/isa/psm.c, and please report the result. Kazu >Robert Watson wrote: >> >> I'm using a Micron P133 box with a PS/2 mouse. Up until this morning, I >> was running 4.0-STABLE from a month or two back. I upgraded to >> 5.0-CURRENT, and since that time, my mouse has been responding slowly and >> erratically, jumping as it moves, et al. > >> I'm using the default arguments to moused, with moused enabled in >> /etc/rc.conf. I'm not sure what changed, but it would be nice if it >> hadn't :-). > >Yep. It's been that way in 5.0-current for about 2-3 weeks now. When >I use /dev/sysmouse in X, my mouse is really jumpy. It's so bad that >I don't use moused anymore in X. When I use my mouse normally, i.e. >without moused (/dev/mouse), in X, mouse movements are OK. Also, >cursor motion is jumpy as well. Must be the recent commits to >syscons. > >-- >- Donn Index: psm.c =================================================================== RCS file: /src/CVS/src/sys/isa/psm.c,v retrieving revision 1.27 diff -u -r1.27 psm.c --- psm.c 2000/07/22 04:08:12 1.27 +++ psm.c 2000/07/27 06:53:24 @@ -1827,9 +1827,11 @@ { struct psm_softc *sc; int unit; + int s; unit = (int)arg; sc = devclass_get_softc(psm_devclass, unit); + s = spltty(); if (sc->watchdog && kbdc_lock(sc->kbdc, TRUE)) { if (verbose >= 4) log(LOG_DEBUG, "psm%d: lost interrupt?\n", unit); @@ -1837,6 +1839,7 @@ kbdc_lock(sc->kbdc, FALSE); } sc->watchdog = TRUE; + splx(s); sc->callout = timeout(psmtimeout, (void *)unit, hz); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 20: 9:53 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 600D837B709; Thu, 27 Jul 2000 20:09:49 -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.Beta1) with ESMTP id e6S39pG46251; Fri, 28 Jul 2000 12:09:52 +0900 (JST) Date: Fri, 28 Jul 2000 12:09:51 +0900 Message-ID: <7mr98fq7b4.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: cracauer@FreeBSD.org Cc: Current Subject: /bin/sh dumps core with here-document of 8bit text 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: multipart/mixed; boundary="Multipart_Fri_Jul_28_12:09:51_2000-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Fri_Jul_28_12:09:51_2000-1 Content-Type: text/plain; charset=US-ASCII I don't know you are the right person to ask, but I found you committed some of 8bit cleaning in src/bin/sh. Shell script which contains here-document of 8bit text sometimes dumps core. For example, please test this script in 4.1 or -current. #!/bin/sh cat < // FreeBSD Project --Multipart_Fri_Jul_28_12:09:51_2000-1 Content-Type: application/octet-stream; type=gzip Content-Disposition: attachment; filename="8bit.sh.gz" Content-Transfer-Encoding: base64 H4sICEn4gDkAAzhiaXQuc2gAU1bUT8rM0y/O4EpOLFGwsXH1d+NqOtR0hgvEAABiGHPjHQAAAA== --Multipart_Fri_Jul_28_12:09:51_2000-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 23: 4:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 3C04237B50D; Thu, 27 Jul 2000 23:04:09 -0700 (PDT) (envelope-from hanai@imgsrc.co.jp) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [210.226.20.130]) by white.imgsrc.co.jp (8.9.3+3.2W/3.7Wpl2-GW) with ESMTP id PAA43501; Fri, 28 Jul 2000 15:04:08 +0900 (JST) Received: from darkmatter.imgsrc.co.jp (darkmatter.imgsrc.co.jp [210.226.20.149]) by black.imgsrc.co.jp (8.9.3/3.7Wpl2-SPOOL) with ESMTP id PAA39541; Fri, 28 Jul 2000 15:04:08 +0900 (JST) Received: from darkmatter.imgsrc.co.jp (localhost [127.0.0.1]) by darkmatter.imgsrc.co.jp (Postfix) with ESMTP id 5406B9BE2; Fri, 28 Jul 2000 15:04:10 +0900 (JST) Date: Fri, 28 Jul 2000 15:04:10 +0900 Message-ID: <82n1j26bad.wl@darkmatter.imgsrc.co.jp> From: Hiroyuki Hanai To: cracauer@FreeBSD.org, FreeBSD-current@FreeBSD.org Subject: Re: /bin/sh dumps core with here-document of 8bit text In-Reply-To: In your message of "28 Jul 2000 03:11:20 GMT" <7mr98fq7b4.wl@waterblue.imgsrc.co.jp> References: <7mr98fq7b4.wl@waterblue.imgsrc.co.jp> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.6 (i386--freebsd) MULE/4.0 (HANANOEN) Organization: IMG SRC, Inc. 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 > #!/bin/sh > cat < [8bit text which contains 0x82 character] > EOF > > And, if I use 'EOF' instead of EOF, it works fine. Do you have any > idea about this behavior? And I want to quote that we Japanese often meet 0x82 because it is contained in Shift_JIS encoding. :-( h.h. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 27 23: 7:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id DCAE637B50D; Thu, 27 Jul 2000 23:07:27 -0700 (PDT) (envelope-from ume@freebsd.org) Received: (from uucp@localhost) by light.imasy.or.jp (8.9.3+3.2W/3.7W-light) with UUCP id PAA07593; Fri, 28 Jul 2000 15:07:25 +0900 (JST) (envelope-from ume@freebsd.org) Received: from localhost (IDENT:YEaZ6pD+f2WUNck5XEmoSFG9VYQ9KAUDInsKkOpSjcys3L50hM6Z5+fkKlq2cvRf@peace.mahoroba.org [2001:200:301:0:200:f8ff:fe05:3eae]) by mail.mahoroba.org (8.11.0/3.7W-chaos) with ESMTP id e6S66Sh18539; Fri, 28 Jul 2000 15:06:28 +0900 (JST) (envelope-from ume@freebsd.org) Date: Fri, 28 Jul 2000 15:06:27 +0900 (JST) Message-Id: <20000728.150627.74708840.ume@mahoroba.org> To: kuriyama@FreeBSD.org Cc: cracauer@FreeBSD.org, FreeBSD-current@FreeBSD.org Cc: ume@freebsd.org Subject: Re: /bin/sh dumps core with here-document of 8bit text From: Hajimu UMEMOTO In-Reply-To: <7mr98fq7b4.wl@waterblue.imgsrc.co.jp> References: <7mr98fq7b4.wl@waterblue.imgsrc.co.jp> X-Mailer: xcite1.20> 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 Fri, 28 Jul 2000 12:09:51 +0900 >>>>> Jun Kuriyama said: kuriyama> Shell script which contains here-document of 8bit text sometimes dumps kuriyama> core. For example, please test this script in 4.1 or -current. I'm using this for workaround on IMASY's main server. 3.5-RELEASE or later have this problem. --- bin/sh/parser.c.orig Mon Mar 20 19:51:04 2000 +++ bin/sh/parser.c Fri Jun 30 17:15:38 2000 @@ -909,9 +909,11 @@ for (;;) { /* until end of line or end of word */ CHECKSTRSPACE(3, out); /* permit 3 calls to USTPUTC */ +#if 0 if (c < 0 && c != PEOF) synentry = CWORD; else +#endif synentry = syntax[c]; switch(synentry) { -- 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 Fri Jul 28 0: 3:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 5CDED37B551; Fri, 28 Jul 2000 00:03:52 -0700 (PDT) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id JAA10612; Fri, 28 Jul 2000 09:03:50 +0200 (CEST) Date: Fri, 28 Jul 2000 09:03:49 +0200 From: Martin Cracauer To: Jun Kuriyama Cc: cracauer@FreeBSD.ORG, Current Subject: Re: /bin/sh dumps core with here-document of 8bit text Message-ID: <20000728090349.A9976@cons.org> References: <7mr98fq7b4.wl@waterblue.imgsrc.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <7mr98fq7b4.wl@waterblue.imgsrc.co.jp>; from kuriyama@FreeBSD.ORG on Fri, Jul 28, 2000 at 12:09:51PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <7mr98fq7b4.wl@waterblue.imgsrc.co.jp>, Jun Kuriyama wrote: > #!/bin/sh > cat < [8bit text which contains 0x82 character] > EOF I'm very short of time these days, but here are thoughts and a backtrace: 0x82 == \202 == CTLVAR in the parser. For real variable expansion, the parser inserts \202 into the input string. Furthermore, it is an error that the forking shell doesn't detect that its forked counterpart dumped core. I see two solutions: 1) It seems that you can work around the coredump by looking at the next char after \202. For real expansions of variables in here-documents that is \201. Once can probably determine all possible legal combinations and ignore others. However, that would just prevent this coredump and would not support processing the CTL* chars as literal chars in here-documents, at the very least they will be eaten. 2) move the CTL* stuff from expand.h to values outside the char domain. Do do this, all input strings must be converted from char* to int* in the first steps of the parser, all buffers must hold int*, which means that they cannot be displayed to the terminal or presented as input to external programs without converting them back. Of course, I will do the latter :-) However, I'm in the middle of preparation for a job interview, so that is not possible right now. Anyone trying to fix this, especially going the first path, keep in mind that you must not break variable expansion in here-documents: foo=42 cat < http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 0:29:37 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 0B52F37B803 for ; Fri, 28 Jul 2000 00:29:35 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 343 invoked from network); 28 Jul 2000 07:29:33 -0000 Received: from acs-24-154-24-131.zoominternet.net (HELO cvzoom.net) (24.154.24.131) by ns.cvzoom.net with SMTP; 28 Jul 2000 07:29:33 -0000 Message-ID: <3981365B.9B7758C8@cvzoom.net> Date: Fri, 28 Jul 2000 03:29:31 -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: Kazutaka YOKOTA Cc: Robert Watson , freebsd-current@FreeBSD.org Subject: Re: Mouse behaving funny since 5.0-CURRENT upgrade References: <3980BD72.C3540196@cvzoom.net> <200007280030.JAA02407@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > > Try the attached patch for /sys/isa/psm.c, and please report the > result. Actually, I use the mse0 device, because I have an isa bus mouse. -- - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 0:47:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 7570437B551; Fri, 28 Jul 2000 00:47:10 -0700 (PDT) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id JAA10827; Fri, 28 Jul 2000 09:47:08 +0200 (CEST) Date: Fri, 28 Jul 2000 09:47:08 +0200 From: Martin Cracauer To: Hajimu UMEMOTO Cc: kuriyama@FreeBSD.ORG, cracauer@FreeBSD.ORG, FreeBSD-current@FreeBSD.ORG Subject: Re: /bin/sh dumps core with here-document of 8bit text Message-ID: <20000728094707.A10655@cons.org> References: <7mr98fq7b4.wl@waterblue.imgsrc.co.jp> <20000728.150627.74708840.ume@mahoroba.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="qMm9M+Fa2AknHoGS" X-Mailer: Mutt 1.0.1i In-Reply-To: <20000728.150627.74708840.ume@mahoroba.org>; from ume@FreeBSD.ORG on Fri, Jul 28, 2000 at 03:06:27PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii In <20000728.150627.74708840.ume@mahoroba.org>, Hajimu UMEMOTO wrote: > >>>>> On Fri, 28 Jul 2000 12:09:51 +0900 > >>>>> Jun Kuriyama said: > > kuriyama> Shell script which contains here-document of 8bit text sometimes dumps > kuriyama> core. For example, please test this script in 4.1 or -current. > > I'm using this for workaround on IMASY's main server. 3.5-RELEASE or > later have this problem. > > --- bin/sh/parser.c.orig Mon Mar 20 19:51:04 2000 > +++ bin/sh/parser.c Fri Jun 30 17:15:38 2000 > @@ -909,9 +909,11 @@ > for (;;) { /* until end of line or end of word */ > CHECKSTRSPACE(3, out); /* permit 3 calls to USTPUTC */ > > +#if 0 > if (c < 0 && c != PEOF) > synentry = CWORD; > else > +#endif > synentry = syntax[c]; > > switch(synentry) { Hm, looks like I broke that in my 8-bit fixes. This code is native in that it passed control chars further down in the hope noone will execute them anymore, just taking them for real chars. Nice try. The problem is also not limited to here-documents: echo \202 # A real \202 will also dump core. Since literal strings cannot be made 8-bit clean without further cleanup, I think we should make this official, although in the following form, otherwise wrong characters are echoed. Anyone for whom this fix doesn't work? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=sh-8bit ? test2 ? test1 ? l ? Makefile.cra ? builtins.c ? builtins.h ? mknodes ? nodes.h ? nodes.c ? mksyntax ? syntax.c ? syntax.h ? token.h ? y.tab.h ? y.tab.c ? arith.c ? arith_lex.c ? sh ? l4 ? mkinit ? init.c ? sh.1.gz ? .depend ? l3 ? l2 ? foo ? l5 Index: parser.c =================================================================== RCS file: /home/CVS-FreeBSD/src/bin/sh/parser.c,v retrieving revision 1.31 diff -c -r1.31 parser.c *** parser.c 2000/05/15 13:02:07 1.31 --- parser.c 2000/07/28 07:46:22 *************** *** 909,918 **** for (;;) { /* until end of line or end of word */ CHECKSTRSPACE(3, out); /* permit 3 calls to USTPUTC */ ! if (c < 0 && c != PEOF) synentry = CWORD; ! else ! synentry = syntax[c]; switch(synentry) { case CNL: /* '\n' */ --- 909,923 ---- for (;;) { /* until end of line or end of word */ CHECKSTRSPACE(3, out); /* permit 3 calls to USTPUTC */ ! if (c >= CTLESC && c <= CTLQUOTEMARK) { synentry = CWORD; ! fprintf(stderr, ! "Warning: internal control character in " ! "literal text, using '?' instead\n"); ! c = '?'; ! } ! ! synentry = syntax[c]; switch(synentry) { case CNL: /* '\n' */ --qMm9M+Fa2AknHoGS-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 2:54:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from oitunix.oit.umass.edu (nscs21p5.remote.umass.edu [128.119.179.6]) by hub.freebsd.org (Postfix) with ESMTP id 5AE6737B746 for ; Fri, 28 Jul 2000 02:54:26 -0700 (PDT) (envelope-from gp@oitunix.oit.umass.edu) Received: (from gp@localhost) by oitunix.oit.umass.edu (8.9.3/8.9.3) id FAA01747 for freebsd-current@freebsd.org; Fri, 28 Jul 2000 05:54:05 -0400 (EDT) (envelope-from gp) Date: Fri, 28 Jul 2000 05:53:57 -0400 From: Greg Pavelcak To: freebsd-current@freebsd.org Subject: Another minor mouse problem w/XFree86-4 Message-ID: <20000728055357.A1718@oitunix.oit.umass.edu> Mail-Followup-To: Greg Pavelcak , freebsd-current@freebsd.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 suppose there are several places that this difficulty may be located. I have a Logitech Trackball. I have tried it on the serial port and the PS/2 port and have the same problem in both places: 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Jul 27 06:00:20 EDT 2000 XFree86-3.3.6 and TkDesk-1.2 I right click on a directory or file in TkDesk, and a popup menu appears and *stays up* (thank goodness). Change to XFree86-4, and I need to hold the button down to keep the menu. Man I hate that. Any ideas. I'm RTFM moused and psm, but I don't see any obviously related adjustments. Oh. This is with moused_enable="YES" # Run the mouse daemon. moused_type="ps/2" # See man page for rc.conf(5) for available settings. moused_port="/dev/psm0" # Set to your mouse port. in rc.conf (for the ps/2 attempt obvously), and Identifier "Mouse1" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" in XF86Config. Thanks. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 4: 0:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id BEAFE37BACF; Fri, 28 Jul 2000 04:00:27 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:NPvlsQREEtFY3fBWaQ3l/CTm8vi7at+m@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id UAA02107; Fri, 28 Jul 2000 20:00:25 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:cYie16eDbsSyErELkMSVXNor8cWcyu2J@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id UAA13331; Fri, 28 Jul 2000 20:07:18 +0900 (JST) Message-Id: <200007281107.UAA13331@zodiac.mech.utsunomiya-u.ac.jp> To: Donn Miller , Robert Watson Cc: freebsd-current@FreeBSD.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Mouse behaving funny since 5.0-CURRENT upgrade In-reply-to: Your message of "Fri, 28 Jul 2000 03:29:31 -0400." <3981365B.9B7758C8@cvzoom.net> References: <3980BD72.C3540196@cvzoom.net> <200007280030.JAA02407@zodiac.mech.utsunomiya-u.ac.jp> <3981365B.9B7758C8@cvzoom.net> Date: Fri, 28 Jul 2000 20:07:17 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Kazutaka YOKOTA wrote: >> >> Try the attached patch for /sys/isa/psm.c, and please report the >> result. > >Actually, I use the mse0 device, because I have an isa bus mouse. > >-- >- Donn Robert, I still want you to try my patch, as you are using the PS/2 mouse. Donn, would you please run moused at higher priority, (for example, "nice -5 moused..." or "nice -10 moused...",) in order to see if this is caused by moused somewhat not running in a timely manner. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 4: 5:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 0A26937BFCF for ; Fri, 28 Jul 2000 04:05:31 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:2C8DDJG9oFQgFCdR867tqgrXzicNaDdZ@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id UAA07755; Fri, 28 Jul 2000 20:05:30 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:Ue1VIPI5pJTH/TZdCeH6k3ZUkvXPFW32@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id UAA13440; Fri, 28 Jul 2000 20:12:22 +0900 (JST) Message-Id: <200007281112.UAA13440@zodiac.mech.utsunomiya-u.ac.jp> To: Greg Pavelcak Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Another minor mouse problem w/XFree86-4 In-reply-to: Your message of "Fri, 28 Jul 2000 05:53:57 -0400." <20000728055357.A1718@oitunix.oit.umass.edu> References: <20000728055357.A1718@oitunix.oit.umass.edu> Date: Fri, 28 Jul 2000 20:12:21 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have a Logitech Trackball. I have tried it on the serial port >and the PS/2 port and have the same problem in both places: > >5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Jul 27 06:00:20 EDT 2000 >XFree86-3.3.6 and >TkDesk-1.2 > >I right click on a directory or file in TkDesk, and a popup menu >appears and *stays up* (thank goodness). > >Change to XFree86-4, and I need to hold the button down to keep the >menu. Man I hate that. Which is supposed to be the correct behavior of TkDesk? The popup menu should stay up as in XFree86 3.3.6? I have no experience on TkDesk. >Any ideas. I'm RTFM moused and psm, but I don't see any obviously >related adjustments. Run `xev' and click the button in the xev window and see what messages are generated. If you still have XFree86 3.3.6 around. Do the same and compare the results in two versions of XFree86. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 4:54:20 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 2F4E637C21D for ; Fri, 28 Jul 2000 04:54:14 -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 13I8iS-000Fju-00 for current@FreeBSD.org; Fri, 28 Jul 2000 13:54:12 +0200 From: Sheldon Hearn To: current@FreeBSD.org Subject: HEADS UPS: loader.conf's null_load renamed Date: Fri, 28 Jul 2000 13:54:12 +0200 Message-ID: <60505.964785252@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just renamed the nullfs kernel module from null to nullfs. The only impact that this may have on some people is as follows: If you have null_load="YES" in your /boot/loader.conf, you will need to change that to nullfs_load="YES". Apologies for the inconvenience to the folks who use the nullfs code in spite of the dire warnings in NOTES. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 5:10:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id DA94C37BA7C; Fri, 28 Jul 2000 05:10:36 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:vOrMyEeETwbARRBC8eN9LbMPBRKWTmXC@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id VAA04903; Fri, 28 Jul 2000 21:10:36 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:i57rTql4ivDe7TRylPV5uQLdslmN4ORc@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id VAA14283; Fri, 28 Jul 2000 21:17:28 +0900 (JST) Message-Id: <200007281217.VAA14283@zodiac.mech.utsunomiya-u.ac.jp> Cc: Donn Miller , Robert Watson Cc: freebsd-current@FreeBSD.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Mouse behaving funny since 5.0-CURRENT upgrade In-reply-to: Your message of "Fri, 28 Jul 2000 20:07:17 JST." <200007281107.UAA13331@zodiac.mech.utsunomiya-u.ac.jp> References: <3980BD72.C3540196@cvzoom.net> <200007280030.JAA02407@zodiac.mech.utsunomiya-u.ac.jp> <3981365B.9B7758C8@cvzoom.net> <200007281107.UAA13331@zodiac.mech.utsunomiya-u.ac.jp> Date: Fri, 28 Jul 2000 21:17:27 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Donn, would you please run moused at higher priority, (for example, >"nice -5 moused..." or "nice -10 moused...",) in order to see if this Oh, I meant "nice --5 mouse..." and "nice --10 moused..." :-) Kazu >is caused by moused somewhat not running in a timely manner. > >Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 5:32:20 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 CF6C737BDEC; Fri, 28 Jul 2000 05:32:10 -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 13I9Iq-0000uK-00; Fri, 28 Jul 2000 14:31:48 +0200 From: Sheldon Hearn To: Kirk McKusick Cc: green@FreeBSD.org, current@FreeBSD.org Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-reply-to: Your message of "Wed, 26 Jul 2000 16:43:04 MST." <200007262343.QAA15655@beastie.mckusick.com> Date: Fri, 28 Jul 2000 14:31:48 +0200 Message-ID: <3491.964787508@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jul 2000 16:43:04 MST, Kirk McKusick wrote: > I have had a number of complaints of this sort which seem to be > somehow related to recursive buffer locks. Since the recursive > locks are only needed to prevent deadlock when mounting snapshots > I decided to back out the use of recursive locks for now. When I > have had a chance to investigate why they are causing problems, > I will try reenabling them. Let me know if this problem persists > once you have upgraded to version 1.107 of buf.h. Just a quick note to let you two gentlement know that the problem persists with rev 1.107 of buf.h. Brian, these are realy easy for me to reproduce on my own box here. Do you want to send me the stuff for maintaining the queues that you said would help you figure out what's going on? Or are you able to reproduce this yourself? Ciao, Sheldon. Script started on Fri Jul 28 14:25:46 2000 [root@axl] ~AXL # gdb -k -c /var/crash/vmcore.3 kernel.debug GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2826240 initial pcb at 244080 panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking panic messages: --- --- #0 boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:303 303 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:303 #1 0xc01462c1 in panic (fmt=0xc02044a0 "lockmgr: pid %d, not %s %d unlocking") at /usr/src/sys/kern/kern_shutdown.c:553 #2 0xc0140fdc in lockmgr (lkp=0xc0da4400, flags=6, interlkp=0xc8f08dec, p=0xc84bfe00) at /usr/src/sys/kern/kern_lock.c:382 #3 0xc01747b3 in vop_stdunlock (ap=0xc84c5e48) at /usr/src/sys/kern/vfs_default.c:255 #4 0xc01b4285 in ufs_vnoperate (ap=0xc84c5e48) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2285 #5 0xc01af163 in ufs_inactive (ap=0xc84c5e78) at vnode_if.h:865 #6 0xc01b4285 in ufs_vnoperate (ap=0xc84c5e78) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2285 #7 0xc017752e in vput (vp=0xc8f08d80) at vnode_if.h:794 #8 0xc01ac43f in ffs_sync (mp=0xc0c35a00, waitfor=2, cred=0xc0721780, p=0xc02569e0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:955 #9 0xc01794b1 in sync (p=0xc02569e0, uap=0x0) at /usr/src/sys/kern/vfs_syscalls.c:551 #10 0xc0145cf7 in boot (howto=0) at /usr/src/sys/kern/kern_shutdown.c:225 #11 0xc0145af8 in reboot (p=0xc84bfe00, uap=0xc84c5f80) at /usr/src/sys/kern/kern_shutdown.c:146 #12 0xc01eb239 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077936612, tf_esi = -1077936624, tf_ebp = -1077936836, tf_isp = -934518828, tf_ebx = -1077936732, tf_edx = -1, tf_ecx = 4, ---Type to continue, or q to quit--- 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 /usr/src/sys/i386/i386/trap.c:1128 #13 0xc01dff45 in Xint0x80_syscall () #14 0x80486ee in ?? () #15 0x8048478 in ?? () #16 0x8048139 in ?? () (kgdb) quit [root@axl] ~AXL # exit Script done on Fri Jul 28 14:26:19 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 5:48:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mie.mrit.co.jp (mie.mrit.co.jp [210.128.138.3]) by hub.freebsd.org (Postfix) with ESMTP id E54FC37C1D6 for ; Fri, 28 Jul 2000 05:48:40 -0700 (PDT) (envelope-from yasu@codec.mrit.mei.co.jp) Received: from mrit.mrit.mei.co.jp (mrit [133.185.23.3]) by mie.mrit.co.jp (8.9.3/3.7W-99061613) with ESMTP id VAA14040 for ; Fri, 28 Jul 2000 21:48:37 +0900 (JST) Received: from codec.mrit.mei.co.jp (rosso [133.185.25.39]) by mrit.mrit.mei.co.jp (8.9.3/3.7W-00040519) with SMTP id VAA70709 for ; Fri, 28 Jul 2000 21:48:37 +0900 (JST) Received: (qmail 43707 invoked by uid 190); 28 Jul 2000 12:48:15 -0000 Message-ID: <20000728124815.43706.qmail@codec.mrit.mei.co.jp> To: freebsd-current@freebsd.org From: yasu@mrit.mei.co.jp Subject: new libstdc++ works? User-Agent: WEMI/1.13.4 (Nishi-Yaizu) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386--freebsd) MIME-Version: 1.0 (generated by WEMI 1.13.4 - "Nishi-Yaizu") Content-Type: text/plain; charset=US-ASCII Date: Fri, 28 Jul 2000 21:48:15 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems new libstdc++ called libstdc++-v3 (http://gcc.gnu.org/) was released around this April. I tried to install it on FreeBSD to get better STL support, but it failed for me. Is there any plan to support it, or does someone succeed to port to FreeBSD? Any information is appreciated. -- Yasuhiko WATANABE Matsushita Research Institute Tokyo, Inc. Mobile Communication Research Laboratory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 6:15:35 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 03F1A37B957; Fri, 28 Jul 2000 06:15:34 -0700 (PDT) Date: Fri, 28 Jul 2000 06:15:33 -0700 From: "Andrey A. Chernov" To: Martin Cracauer Cc: Hajimu UMEMOTO , kuriyama@FreeBSD.ORG, cracauer@FreeBSD.ORG, FreeBSD-current@FreeBSD.ORG Subject: Re: /bin/sh dumps core with here-document of 8bit text Message-ID: <20000728061533.A49657@freebsd.org> References: <7mr98fq7b4.wl@waterblue.imgsrc.co.jp> <20000728.150627.74708840.ume@mahoroba.org> <20000728094707.A10655@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000728094707.A10655@cons.org>; from cracauer@cons.org on Fri, Jul 28, 2000 at 09:47:08AM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 28, 2000 at 09:47:08AM +0200, Martin Cracauer wrote: > ! if (c >= CTLESC && c <= CTLQUOTEMARK) { > synentry = CWORD; > ! fprintf(stderr, > ! "Warning: internal control character in " > ! "literal text, using '?' instead\n"); > ! c = '?'; > ! } I disagree. It is not the fix, just admitting the bug. Better try to fix it via some escaping of control characters via some prefix char. Bash is 8bit clean in that place, f.e. -- 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 Jul 28 6:20:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 373D937C1D5; Fri, 28 Jul 2000 06:20:22 -0700 (PDT) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id PAA14506; Fri, 28 Jul 2000 15:20:20 +0200 (CEST) Date: Fri, 28 Jul 2000 15:20:19 +0200 From: Martin Cracauer To: "Andrey A. Chernov" Cc: Martin Cracauer , Hajimu UMEMOTO , kuriyama@FreeBSD.ORG, cracauer@FreeBSD.ORG, FreeBSD-current@FreeBSD.ORG Subject: Re: /bin/sh dumps core with here-document of 8bit text Message-ID: <20000728152019.A14471@cons.org> References: <7mr98fq7b4.wl@waterblue.imgsrc.co.jp> <20000728.150627.74708840.ume@mahoroba.org> <20000728094707.A10655@cons.org> <20000728061533.A49657@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000728061533.A49657@freebsd.org>; from ache@FreeBSD.ORG on Fri, Jul 28, 2000 at 06:15:33AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000728061533.A49657@freebsd.org>, Andrey A. Chernov wrote: > On Fri, Jul 28, 2000 at 09:47:08AM +0200, Martin Cracauer wrote: > > ! if (c >= CTLESC && c <= CTLQUOTEMARK) { > > synentry = CWORD; > > ! fprintf(stderr, > > ! "Warning: internal control character in " > > ! "literal text, using '?' instead\n"); > > ! c = '?'; > > ! } > > > I disagree. It is not the fix, just admitting the bug. Better try to fix it via > some escaping of control characters via some prefix char. Bash is 8bit clean > in that place, f.e. Please refer to my previous mail. I think it's better to extend the internal character handling to int* instead of obfuscating it even more with escape sequences (remember that they are processed multiple times and such things as taking the length of something, see related PR fix recently). Until that is done, we should commit this diff, because it *fixes* the breakage of coredumping and eating all input (not only th offending chars), even when it does not solve the problem of not being 8-bit clean. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 6:21:35 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 865D237C1E3; Fri, 28 Jul 2000 06:21:33 -0700 (PDT) Date: Fri, 28 Jul 2000 06:21:33 -0700 From: "Andrey A. Chernov" To: Martin Cracauer Cc: Jun Kuriyama , cracauer@FreeBSD.ORG, Current Subject: Re: /bin/sh dumps core with here-document of 8bit text Message-ID: <20000728062133.B49657@freebsd.org> References: <7mr98fq7b4.wl@waterblue.imgsrc.co.jp> <20000728090349.A9976@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000728090349.A9976@cons.org>; from cracauer@cons.org on Fri, Jul 28, 2000 at 09:03:49AM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 28, 2000 at 09:03:49AM +0200, Martin Cracauer wrote: > 1) It seems that you can work around the coredump by looking at the > next char after \202. For real expansions of variables in > here-documents that is \201. Once can probably determine all > possible legal combinations and ignore others. However, that The problem is that all combinations are legal, there can be binary data passed. It means that all control chars must be double-escaped first just after data reading. -- 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 Jul 28 6:24:31 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 65FA737B7DB; Fri, 28 Jul 2000 06:24:29 -0700 (PDT) Date: Fri, 28 Jul 2000 06:24:29 -0700 From: "Andrey A. Chernov" To: Martin Cracauer Cc: Hajimu UMEMOTO , kuriyama@FreeBSD.ORG, cracauer@FreeBSD.ORG, FreeBSD-current@FreeBSD.ORG Subject: Re: /bin/sh dumps core with here-document of 8bit text Message-ID: <20000728062429.C49657@freebsd.org> References: <7mr98fq7b4.wl@waterblue.imgsrc.co.jp> <20000728.150627.74708840.ume@mahoroba.org> <20000728094707.A10655@cons.org> <20000728061533.A49657@freebsd.org> <20000728152019.A14471@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000728152019.A14471@cons.org>; from cracauer@cons.org on Fri, Jul 28, 2000 at 03:20:19PM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 28, 2000 at 03:20:19PM +0200, Martin Cracauer wrote: > Please refer to my previous mail. I think it's better to extend the > internal character handling to int* instead of obfuscating it even > more with escape sequences (remember that they are processed multiple > times and such things as taking the length of something, see related > PR fix recently). Yes, but it is really big change. > Until that is done, we should commit this diff, because it *fixes* the > breakage of coredumping and eating all input (not only th offending > chars), even when it does not solve the problem of not being 8-bit > clean. What about trying double-escape first instead? I.e. escape internal control chars just after reading them from input stream? It is less painful then converting to 16bit. -- 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 Jul 28 6:24:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id B9D6837C287; Fri, 28 Jul 2000 06:24:42 -0700 (PDT) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id PAA14592; Fri, 28 Jul 2000 15:24:41 +0200 (CEST) Date: Fri, 28 Jul 2000 15:24:41 +0200 From: Martin Cracauer To: "Andrey A. Chernov" Cc: Martin Cracauer , Jun Kuriyama , cracauer@FreeBSD.ORG, Current Subject: Re: /bin/sh dumps core with here-document of 8bit text Message-ID: <20000728152440.A14570@cons.org> References: <7mr98fq7b4.wl@waterblue.imgsrc.co.jp> <20000728090349.A9976@cons.org> <20000728062133.B49657@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000728062133.B49657@freebsd.org>; from ache@FreeBSD.ORG on Fri, Jul 28, 2000 at 06:21:33AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000728062133.B49657@freebsd.org>, Andrey A. Chernov wrote: > On Fri, Jul 28, 2000 at 09:03:49AM +0200, Martin Cracauer wrote: > > 1) It seems that you can work around the coredump by looking at the > > next char after \202. For real expansions of variables in > > here-documents that is \201. Once can probably determine all > > possible legal combinations and ignore others. However, that > > The problem is that all combinations are legal, there can be binary data passed. > It means that all control chars must be double-escaped first just after data > reading. Exactly. When I'm going to fix it, I will use the other solution (char* -> int* for internal parsed buffers). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 6:44: 8 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 E665A37C218 for ; Fri, 28 Jul 2000 06:44:02 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 8642 invoked from network); 28 Jul 2000 13:44:00 -0000 Received: from acs-24-154-24-131.zoominternet.net (HELO cvzoom.net) (24.154.24.131) by ns.cvzoom.net with SMTP; 28 Jul 2000 13:44:00 -0000 Message-ID: <39818E1E.5B713447@cvzoom.net> Date: Fri, 28 Jul 2000 09:43:58 -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: Kazutaka YOKOTA Cc: Robert Watson , freebsd-current@FreeBSD.org Subject: Re: Mouse behaving funny since 5.0-CURRENT upgrade References: <3980BD72.C3540196@cvzoom.net> <200007280030.JAA02407@zodiac.mech.utsunomiya-u.ac.jp> <3981365B.9B7758C8@cvzoom.net> <200007281107.UAA13331@zodiac.mech.utsunomiya-u.ac.jp> <200007281217.VAA14283@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > > >Donn, would you please run moused at higher priority, (for example, > >"nice -5 moused..." or "nice -10 moused...",) in order to see if this > > Oh, I meant "nice --5 mouse..." and "nice --10 moused..." :-) Tried this. It doesn't fix the problem. The mouse is still jumpy no matter what the nice level. I believe it's a problem with syscons as a whole. For example, whenever I switch to a VC and do kbdcontrol -r 240.34 to get a very fast keyboard repeat rate, the rate at which the characters repeat is very jumpy as well, much like the mouse. It was never like this before. So, I don't think the problem is specific to the syscons mouse drivers, just syscons itself. This started happening after some commits to syscons a couple of weeks back. -- - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 6:44:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id F348C37C256 for ; Fri, 28 Jul 2000 06:44:36 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id GAA09549; Fri, 28 Jul 2000 06:44:14 -0700 Date: Fri, 28 Jul 2000 06:44:17 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: HEADS UPS: loader.conf's null_load renamed In-Reply-To: <60505.964785252@axl.ops.uunet.co.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 That's groovy, Sheldon.. could you maybe fix nullfs while you're at it, too? :-) On Fri, 28 Jul 2000, Sheldon Hearn wrote: > > I've just renamed the nullfs kernel module from null to nullfs. The > only impact that this may have on some people is as follows: > > If you have null_load="YES" in your /boot/loader.conf, you will need > to change that to nullfs_load="YES". > > Apologies for the inconvenience to the folks who use the nullfs code in > spite of the dire warnings in NOTES. > > Ciao, > Sheldon. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 6:45:50 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 ADC6437C231 for ; Fri, 28 Jul 2000 06:45:44 -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 13IAS6-0003el-00; Fri, 28 Jul 2000 15:45:26 +0200 From: Sheldon Hearn To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: HEADS UPS: loader.conf's null_load renamed In-reply-to: Your message of "Fri, 28 Jul 2000 06:44:17 MST." Date: Fri, 28 Jul 2000 15:45:26 +0200 Message-ID: <14058.964791926@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jul 2000 06:44:17 MST, Matthew Jacob wrote: > That's groovy, Sheldon.. could you maybe fix nullfs while you're at > it, too? :-) I doubt it. I'm not brave enough to go past getting a file listing within a null mount. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 7:15: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B855D37BC2D for ; Fri, 28 Jul 2000 07:15:04 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id HAA09663; Fri, 28 Jul 2000 07:14:54 -0700 Date: Fri, 28 Jul 2000 07:14:57 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: HEADS UPS: loader.conf's null_load renamed In-Reply-To: <14058.964791926@axl.ops.uunet.co.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 Tsk. Coward. I ran for at least a week mounting /usr/src/sys/compile on top an NFS mounted /usr/src/sys before I panic'd (and read the NOTES file) Tsk. It's too bad. This works in NetBSD :-).... On Fri, 28 Jul 2000, Sheldon Hearn wrote: > > > On Fri, 28 Jul 2000 06:44:17 MST, Matthew Jacob wrote: > > > That's groovy, Sheldon.. could you maybe fix nullfs while you're at > > it, too? :-) > > I doubt it. I'm not brave enough to go past getting a file listing > within a null mount. :-) > > Ciao, > Sheldon. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 7:25: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id C7EAB37C1FD; Fri, 28 Jul 2000 07:24:56 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:S68qcF/lc8OCVNdIImX+Cw+aQOr7Rr5c@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id XAA08345; Fri, 28 Jul 2000 23:24:55 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:T42ifRX1kFbFVHrK0jSJ0ElX29BWQ+O6@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id XAA15784; Fri, 28 Jul 2000 23:31:48 +0900 (JST) Message-Id: <200007281431.XAA15784@zodiac.mech.utsunomiya-u.ac.jp> To: Donn Miller Cc: Robert Watson , freebsd-current@FreeBSD.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Mouse behaving funny since 5.0-CURRENT upgrade In-reply-to: Your message of "Fri, 28 Jul 2000 09:43:58 -0400." <39818E1E.5B713447@cvzoom.net> References: <3980BD72.C3540196@cvzoom.net> <200007280030.JAA02407@zodiac.mech.utsunomiya-u.ac.jp> <3981365B.9B7758C8@cvzoom.net> <200007281107.UAA13331@zodiac.mech.utsunomiya-u.ac.jp> <200007281217.VAA14283@zodiac.mech.utsunomiya-u.ac.jp> <39818E1E.5B713447@cvzoom.net> Date: Fri, 28 Jul 2000 23:31:46 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Oh, I meant "nice --5 mouse..." and "nice --10 moused..." :-) > >Tried this. It doesn't fix the problem. The mouse is still jumpy no >matter what the nice level. I believe it's a problem with syscons as >a whole. For example, whenever I switch to a VC and do kbdcontrol -r >240.34 to get a very fast keyboard repeat rate, the rate at which the >characters repeat is very jumpy as well, much like the mouse. It was >never like this before. So, I don't think the problem is specific to >the syscons mouse drivers, just syscons itself. This started >happening after some commits to syscons a couple of weeks back. I find quite hard to believe this was caused by recent syscons changes. Because these changes are about /dev/random thingie and color attribute handling in terminal emulator part of syscons. They have nothing to do with keyboard and mouse input. I am suspecting there may be something in tty interrupt handling in general in the kernel... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 7:53: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 29FE937C226 for ; Fri, 28 Jul 2000 07:53:53 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 16027 invoked from network); 28 Jul 2000 14:53:51 -0000 Received: from acs-24-154-24-131.zoominternet.net (HELO cvzoom.net) (24.154.24.131) by ns.cvzoom.net with SMTP; 28 Jul 2000 14:53:51 -0000 Message-ID: <39819E7F.806BFAD6@cvzoom.net> Date: Fri, 28 Jul 2000 10:53:51 -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: Kazutaka YOKOTA Cc: Robert Watson , freebsd-current@FreeBSD.org Subject: Re: Mouse behaving funny since 5.0-CURRENT upgrade References: <3980BD72.C3540196@cvzoom.net> <200007280030.JAA02407@zodiac.mech.utsunomiya-u.ac.jp> <3981365B.9B7758C8@cvzoom.net> <200007281107.UAA13331@zodiac.mech.utsunomiya-u.ac.jp> <200007281217.VAA14283@zodiac.mech.utsunomiya-u.ac.jp> <39818E1E.5B713447@cvzoom.net> <200007281431.XAA15784@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > I find quite hard to believe this was caused by recent syscons > changes. Because these changes are about /dev/random thingie and > color attribute handling in terminal emulator part of syscons. They > have nothing to do with keyboard and mouse input. > > I am suspecting there may be something in tty interrupt handling in > general in the kernel... This sounds right. When I use X without /dev/sysmouse and moused, mouse motion is still pretty smooth. It's only when I use X with moused AND /dev/sysmouse that I see the jumpy mouse syndrome. This would be due to the fact that (AFAIK) moused relies on tty interrupt handling more so than the raw mouse driver without moused (/dev/mse0). -- - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 8:48:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id A967D37B535; Fri, 28 Jul 2000 08:48:27 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #1) id 13ICN3-0007wz-00; Fri, 28 Jul 2000 17:48:21 +0200 Received: from a371c.pppool.de ([213.6.55.28] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.16 #1) id 13ICMz-00013O-00; Fri, 28 Jul 2000 17:48:17 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id RAA02804; Fri, 28 Jul 2000 17:35:29 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200007281535.RAA02804@Magelan.Leidinger.net> Date: Fri, 28 Jul 2000 17:35:28 +0200 (CEST) From: Alexander Leidinger Subject: Re: Mouse behaving funny since 5.0-CURRENT upgrade To: dmmiller@cvzoom.net Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, rwatson@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: <39819E7F.806BFAD6@cvzoom.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 Jul, Donn Miller wrote: >> I am suspecting there may be something in tty interrupt handling in >> general in the kernel... > > This sounds right. When I use X without /dev/sysmouse and moused, > mouse motion is still pretty smooth. It's only when I use X with > moused AND /dev/sysmouse that I see the jumpy mouse syndrome. This > would be due to the fact that (AFAIK) moused relies on tty interrupt > handling more so than the raw mouse driver without moused (/dev/mse0). Just to give a datapoint: I'm using X 3.3.6 with "moused -p /dev/psm0" and /dev/sysmouse and I *didn't* see the jumpy mouse syndrome. I'm running a kernel from today (COPTFLAGS+=-Wall). 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 Fri Jul 28 9:48:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from evil.2y.net (ztown3-3-124.adsl.one.net [216.23.29.124]) by hub.freebsd.org (Postfix) with ESMTP id CE3DE37BBE2; Fri, 28 Jul 2000 09:48:35 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id MAA04678; Fri, 28 Jul 2000 12:56:35 -0400 (EDT) (envelope-from cokane) Date: Fri, 28 Jul 2000 12:56:35 -0400 From: Coleman Kane To: multimedia@freebsd.org, current@freebsd.org Subject: 3dfx driver Message-ID: <20000728125635.A4661@cokane.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For those who have opted to test my 3dfx driver, I have debugging messages layered in the section that is causing problems. Define the DEBUG option in your kernel, you may have to add makeoptions -DDEBUG -g to the config file as well. Then add the device tdfx line. If you want to use the kld, the Makefile has directions on how to enable the debugging messages. you just uncomment a line in there, or add -DDEBUG to the make line. -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 10: 2:27 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 8AB0C37B75A for ; Fri, 28 Jul 2000 10:02:21 -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 NAA07539; Fri, 28 Jul 2000 13:01:52 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 28 Jul 2000 13:01:51 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Kazutaka YOKOTA Cc: Donn Miller , freebsd-current@FreeBSD.org Subject: Re: Mouse behaving funny since 5.0-CURRENT upgrade In-Reply-To: <200007280030.JAA02407@zodiac.mech.utsunomiya-u.ac.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 Kazu, Nope, it didn't appear to help. When I move the mouse around, it intermitently pauses, perhaps once a second, for a short period of time. Robert On Fri, 28 Jul 2000, Kazutaka YOKOTA wrote: > Try the attached patch for /sys/isa/psm.c, and please report the > result. > > Kazu > > >Robert Watson wrote: > >> > >> I'm using a Micron P133 box with a PS/2 mouse. Up until this morning, I > >> was running 4.0-STABLE from a month or two back. I upgraded to > >> 5.0-CURRENT, and since that time, my mouse has been responding slowly and > >> erratically, jumping as it moves, et al. > > > >> I'm using the default arguments to moused, with moused enabled in > >> /etc/rc.conf. I'm not sure what changed, but it would be nice if it > >> hadn't :-). > > > >Yep. It's been that way in 5.0-current for about 2-3 weeks now. When > >I use /dev/sysmouse in X, my mouse is really jumpy. It's so bad that > >I don't use moused anymore in X. When I use my mouse normally, i.e. > >without moused (/dev/mouse), in X, mouse movements are OK. Also, > >cursor motion is jumpy as well. Must be the recent commits to > >syscons. > > > >-- > >- Donn > > > Index: psm.c > =================================================================== > RCS file: /src/CVS/src/sys/isa/psm.c,v > retrieving revision 1.27 > diff -u -r1.27 psm.c > --- psm.c 2000/07/22 04:08:12 1.27 > +++ psm.c 2000/07/27 06:53:24 > @@ -1827,9 +1827,11 @@ > { > struct psm_softc *sc; > int unit; > + int s; > > unit = (int)arg; > sc = devclass_get_softc(psm_devclass, unit); > + s = spltty(); > if (sc->watchdog && kbdc_lock(sc->kbdc, TRUE)) { > if (verbose >= 4) > log(LOG_DEBUG, "psm%d: lost interrupt?\n", unit); > @@ -1837,6 +1839,7 @@ > kbdc_lock(sc->kbdc, FALSE); > } > sc->watchdog = TRUE; > + splx(s); > sc->callout = timeout(psmtimeout, (void *)unit, hz); > } > > > Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 11:25:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E7CD237B560; Fri, 28 Jul 2000 11:25:44 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Fri, 28 Jul 2000 14:25:43 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Sheldon Hearn Cc: Kirk McKusick , current@FreeBSD.org Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-Reply-To: <3491.964787508@axl.ops.uunet.co.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 Fri, 28 Jul 2000, Sheldon Hearn wrote: > > Just a quick note to let you two gentlement know that the problem > persists with rev 1.107 of buf.h. > > Brian, these are realy easy for me to reproduce on my own box here. Do > you want to send me the stuff for maintaining the queues that you said > would help you figure out what's going on? Or are you able to reproduce > this yourself? I havne't been able to reproduce this, but this case is going to have more to do with analysis of the code than with "debugging", I think. By chance are you running with softupdates enabled on /? If I can reproduce it here, I will spend a while inspecting all the state to figure this one out as best as possible. > Ciao, > Sheldon. -- 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 Fri Jul 28 11:32: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D2B7237BA44; Fri, 28 Jul 2000 11:31:49 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA10440; Fri, 28 Jul 2000 11:31:49 -0700 Date: Fri, 28 Jul 2000 11:31:52 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Brian Fundakowski Feldman Cc: Sheldon Hearn , Kirk McKusick , current@FreeBSD.ORG Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking 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 I'm running with softupdates on /, and it has happened to me several times. On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote: > On Fri, 28 Jul 2000, Sheldon Hearn wrote: > > > > > Just a quick note to let you two gentlement know that the problem > > persists with rev 1.107 of buf.h. > > > > Brian, these are realy easy for me to reproduce on my own box here. Do > > you want to send me the stuff for maintaining the queues that you said > > would help you figure out what's going on? Or are you able to reproduce > > this yourself? > > I havne't been able to reproduce this, but this case is going to have > more to do with analysis of the code than with "debugging", I think. > By chance are you running with softupdates enabled on /? If I can > reproduce it here, I will spend a while inspecting all the state to > figure this one out as best as possible. > > > Ciao, > > Sheldon. > > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 11:36:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.aracnet.com (mail2.aracnet.com [216.99.193.35]) by hub.freebsd.org (Postfix) with ESMTP id C3F1437B9C9; Fri, 28 Jul 2000 11:36:40 -0700 (PDT) (envelope-from sf@aracnet.com) Received: from mephistopheles. (max1-197-44.cust.aracnet.com [216.99.197.44]) by mail2.aracnet.com (8.9.3/8.9.3) with ESMTP id LAA23422; Fri, 28 Jul 2000 11:36:39 -0700 Date: Fri, 28 Jul 2000 11:36:26 -0700 (PDT) From: Scott Flatman X-Sender: sf@mephistopheles. To: Brian Fundakowski Feldman Cc: Sheldon Hearn , Kirk McKusick , current@FreeBSD.ORG Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote: > I havne't been able to reproduce this, but this case is going to have > more to do with analysis of the code than with "debugging", I think. > By chance are you running with softupdates enabled on /? If I can > reproduce it here, I will spend a while inspecting all the state to > figure this one out as best as possible. I get the same panic 100% of the time upon reboot. So I can quite easily reproduce it. :) I tried turning off softupdates on all partitions. Same panic. It also caused umount to hang the machine. I don't have softupdates on / either way. I rebuilt a kernel today, about 1 hour ago. Still panics either way, with or without softupdates. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 12:17:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 9002A37BC18; Fri, 28 Jul 2000 12:17:46 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Fri, 28 Jul 2000 15:17:44 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Robert Watson Cc: Kazutaka YOKOTA , Donn Miller , freebsd-current@FreeBSD.org Subject: Re: Mouse behaving funny since 5.0-CURRENT upgrade In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jul 2000, Robert Watson wrote: > Kazu, > > Nope, it didn't appear to help. When I move the mouse around, it > intermitently pauses, perhaps once a second, for a short period of time. Robert, how fast is the machine that it's pausing on? I have a feeling this could easily be Yarrow at work, since Yarrow runs right now most of the work done inside an interrupt handler (a taskqueue, at least). I'd like you to test the kthread version of Yarrow when Mark Murray and I are ready, which should be in a few days. -- 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 Fri Jul 28 12:36:32 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 299A037BC82; Fri, 28 Jul 2000 12:36:27 -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 PAA09382; Fri, 28 Jul 2000 15:36:22 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 28 Jul 2000 15:36:22 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Brian Fundakowski Feldman Cc: Kazutaka YOKOTA , Donn Miller , freebsd-current@FreeBSD.org Subject: Re: Mouse behaving funny since 5.0-CURRENT upgrade In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote: > On Fri, 28 Jul 2000, Robert Watson wrote: > > > Nope, it didn't appear to help. When I move the mouse around, it > > intermitently pauses, perhaps once a second, for a short period of time. > > Robert, how fast is the machine that it's pausing on? I have a feeling > this could easily be Yarrow at work, since Yarrow runs right now most > of the work done inside an interrupt handler (a taskqueue, at least). CPU: Pentium/P54C (119.75-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x1bf real memory = 100663296 (98304K bytes) So not a big speed demon, but should be reasonable for most tasks, and perfectly decent as a file server, workstation, et al. > I'd like you to test the kthread version of Yarrow when Mark Murray and I > are ready, which should be in a few days. Sure. I'll be out of town at IETF next week, but once I get back I can look at that. I may upgrade my notebook to -CURRENT at some point soon also. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 12:50:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (beachchick.freebsd.dk [212.242.32.208]) by hub.freebsd.org (Postfix) with ESMTP id EDF2137BC8A for ; Fri, 28 Jul 2000 12:50:26 -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 VAA00283 for ; Fri, 28 Jul 2000 21:50:24 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: a FS related patch to test please... From: Poul-Henning Kamp Date: Fri, 28 Jul 2000 21:50:24 +0200 Message-ID: <281.964813824@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm in my beach-house and pretty offline right now, but I reviewed the change Kirk did to addaliasu() and found at least one scenario where it wouldn't do what he expected: If bdevvp() is called more than once with the same dev_t we would create more than one anonymous vnode for that dev_t and addaliasu() would only get one of these in its yarn. This patch makes bdevvp() only produce max one anonymous vnode per dev_t. I don't know if the new rootfs-locating code calls bdevvp() more than once, if it doesn't this patch is a harmless bit of overhead. Please test, and if it doesn't do any harm I will commit it. (This does not fix the panic everybody is talking about btw) Poul-Henning Index: vfs_subr.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_subr.c,v retrieving revision 1.267 diff -u -r1.267 vfs_subr.c --- vfs_subr.c 2000/07/24 05:28:29 1.267 +++ vfs_subr.c 2000/07/28 19:08:36 @@ -1276,6 +1276,8 @@ *vpp = NULLVP; return (ENXIO); } + if (vfinddev(dev, VCHR, vpp)) + return (0); error = getnewvnode(VT_NON, (struct mount *)0, spec_vnodeop_p, &nvp); if (error) { *vpp = NULLVP; -- 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 Jul 28 13:42: 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 4208537B5F1 for ; Fri, 28 Jul 2000 13:41:58 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA17927; Fri, 28 Jul 2000 13:41:27 -0700 (PDT) (envelope-from obrien) Date: Fri, 28 Jul 2000 13:41:27 -0700 From: "David O'Brien" To: yasu@mrit.mei.co.jp Cc: freebsd-current@freebsd.org Subject: Re: new libstdc++ works? Message-ID: <20000728134127.A17854@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000728124815.43706.qmail@codec.mrit.mei.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000728124815.43706.qmail@codec.mrit.mei.co.jp>; from yasu@mrit.mei.co.jp on Fri, Jul 28, 2000 at 09:48:15PM +0900 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, Jul 28, 2000 at 09:48:15PM +0900, yasu@mrit.mei.co.jp wrote: > It seems new libstdc++ called libstdc++-v3 (http://gcc.gnu.org/) was > released around this April. I don't know that I would call it in a released state yet. libstdc++ v2 is still the one that is offical part of GCC 2.96. > Is there any plan to support it, or does someone succeed to port to > FreeBSD? Any information is appreciated. From my point of view, I will bring it in when it is the stock libstdc++ for the compiler. -- -- 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 Jul 28 14:17:33 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 4D93837B651; Fri, 28 Jul 2000 14:17:31 -0700 (PDT) Date: Fri, 28 Jul 2000 14:17:31 -0700 From: "Andrey A. Chernov" To: Scott Flatman Cc: Brian Fundakowski Feldman , Sheldon Hearn , Kirk McKusick , current@FreeBSD.ORG Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking Message-ID: <20000728141728.A44135@freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from sf@aracnet.com on Fri, Jul 28, 2000 at 11:36:26AM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 28, 2000 at 11:36:26AM -0700, Scott Flatman wrote: > On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote: > > > I havne't been able to reproduce this, but this case is going to have > > more to do with analysis of the code than with "debugging", I think. > > By chance are you running with softupdates enabled on /? If I can > > reproduce it here, I will spend a while inspecting all the state to > > figure this one out as best as possible. > > I get the same panic 100% of the time upon reboot. So I can quite > easily reproduce it. :) I too. The only way I can avoid this panic is 1) Remove /erc/rc.shutdown (which write files) 2) Do several syns manually before reboot. In all other situations I got this panic. -- 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 Jul 28 15:19:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from prioris.im.pw.edu.pl (po178.warszawa.cvx.ppp.tpnet.pl [213.76.110.178]) by hub.freebsd.org (Postfix) with ESMTP id 3C85E37B866 for ; Fri, 28 Jul 2000 15:19:42 -0700 (PDT) (envelope-from zaks@prioris.im.pw.edu.pl) Received: by prioris.im.pw.edu.pl (Postfix, from userid 1000) id D7EED6394E; Sat, 29 Jul 2000 00:18:59 +0200 (CEST) Content-MD5: de735bedce1a533d2b0058320959bff6 From: Slawek Zak To: freebsd-current@freebsd.org Subject: Re: Netscape References: Date: 29 Jul 2000 00:18:59 +0200 In-Reply-To: Kris Kennaway's message of "Sun, 23 Jul 2000 01:40:14 -0700 (PDT)" Message-ID: <8766pplwz0.fsf@localhost.localnet> Lines: 15 User-Agent: Gnus/5.0807 (Gnus v5.8.7) 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 Kris Kennaway writes: > > Are the fixed in Netscape 4.74 bugs not critical for release? > > Who knows? I don't know of any changelog for Netscape. Netscape 4.74 contains a fix for security critical bug in handling of jpeg images. The bug was found and published on the 25th of July by Solar Designer. (as you all probably already know;) -- "I think there is a world market for maybe five computers." - Thomas Watson, chairman of IBM, 1943 * 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 Fri Jul 28 15:33: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 69E7037BE87; Fri, 28 Jul 2000 15:32:39 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA11423; Fri, 28 Jul 2000 15:32:35 -0700 Date: Fri, 28 Jul 2000 15:32:38 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: a FS related patch to test please... In-Reply-To: <281.964813824@critter.freebsd.dk> 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 FWIW, works for me On Fri, 28 Jul 2000, Poul-Henning Kamp wrote: > > I'm in my beach-house and pretty offline right now, but I reviewed the > change Kirk did to addaliasu() and found at least one scenario where > it wouldn't do what he expected: > > If bdevvp() is called more than once with the same dev_t we would > create more than one anonymous vnode for that dev_t and addaliasu() > would only get one of these in its yarn. This patch makes bdevvp() > only produce max one anonymous vnode per dev_t. > > I don't know if the new rootfs-locating code calls bdevvp() more > than once, if it doesn't this patch is a harmless bit of overhead. > > Please test, and if it doesn't do any harm I will commit it. > > (This does not fix the panic everybody is talking about btw) > > Poul-Henning > > > Index: vfs_subr.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/vfs_subr.c,v > retrieving revision 1.267 > diff -u -r1.267 vfs_subr.c > --- vfs_subr.c 2000/07/24 05:28:29 1.267 > +++ vfs_subr.c 2000/07/28 19:08:36 > @@ -1276,6 +1276,8 @@ > *vpp = NULLVP; > return (ENXIO); > } > + if (vfinddev(dev, VCHR, vpp)) > + return (0); > error = getnewvnode(VT_NON, (struct mount *)0, spec_vnodeop_p, &nvp); > if (error) { > *vpp = NULLVP; > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 15:41:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from ee.follo.net (ee.follo.net [195.204.143.223]) by hub.freebsd.org (Postfix) with ESMTP id 05C3F37B63A for ; Fri, 28 Jul 2000 15:41:46 -0700 (PDT) (envelope-from eivind@ee.follo.net) Received: (from eivind@localhost) by ee.follo.net (8.9.3/8.9.3) id AAA71923 for current@FreeBSD.org; Sat, 29 Jul 2000 00:41:43 +0200 (CEST) (envelope-from eivind) Date: Sat, 29 Jul 2000 00:41:43 +0200 From: Eivind Eklund To: current@FreeBSD.org Subject: *** HEADS UP *** rc.conf changes (security) Message-ID: <20000729004143.M45306@ee.follo.net> 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 discussion with obrien, jhb, and dwithe (and non-protests from the other committers present), I'm changing the defaults for remote services in /etc/defaults/rc.conf to the least dangerous configuration, and making sysinstall write out overrides for the variables to their former default values in /etc/rc.conf upon install. This means that anybody upgrading /etc/defaults/rc.conf needs to add the following lines to rc.conf if they want to have the same setup afterwards (unless the variables already are set, of course): # Enable network daemons for user convenience. inetd_enable="YES" portmap_enable="YES" sendmail_enable="YES" (Heads up is over - more change detail below.) This change might seem a little counterintuitive (given that /etc/defaults/ are for defaults, after all) but seems to be the best compromise for both getting the functionality jkh wants (freshly installed boxes have active daemons, so users don't feel they have a lot of extra hassle to get things up and working like they are used to on other Unixen), and give FreeBSD a default secure config, meaning the insecurities stand out. I assume those of us that do new installs without using sysinstall know FreeBSD well enough to be able to handle turning those daemons on again if we want them ;) BTW: Keep me in the Cc: list, please - I am not subscribed to -current (or any other FreeBSD mailing list) at the moment. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 16:25:48 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 A89DB37B9DB; Fri, 28 Jul 2000 16:25:44 -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 TAA120992; Fri, 28 Jul 2000 19:25:42 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000729004143.M45306@ee.follo.net> References: <20000729004143.M45306@ee.follo.net> Date: Fri, 28 Jul 2000 19:25:49 -0400 To: Eivind Eklund , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: *** HEADS UP *** rc.conf changes (security) Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:41 AM +0200 7/29/00, Eivind Eklund wrote: >After discussion with obrien, jhb, and dwithe (and non-protests from >the other committers present), I'm changing the defaults for remote >services in /etc/defaults/rc.conf to the least dangerous >configuration, and making sysinstall write out overrides for the >variables to their former default values in /etc/rc.conf upon install. Hopefully sysinstall will be smarter about writing these overrides than it is about writing the "USA_RESIDENT=NO" override to /etc/make.conf. --- 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 Fri Jul 28 16:32:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 636BB37B9D4; Fri, 28 Jul 2000 16:32:48 -0700 (PDT) (envelope-from jhb@pike.osd.bsdi.com) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id QAA24334; Fri, 28 Jul 2000 16:32:23 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200007282332.QAA24334@pike.osd.bsdi.com> Subject: Re: *** HEADS UP *** rc.conf changes (security) In-Reply-To: from Garance A Drosihn at "Jul 28, 2000 07:25:49 pm" To: Garance A Drosihn Date: Fri, 28 Jul 2000 16:32:22 -0700 (PDT) Cc: current@FreeBSD.org, eivind@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosihn wrote: > At 12:41 AM +0200 7/29/00, Eivind Eklund wrote: > >After discussion with obrien, jhb, and dwithe (and non-protests from > >the other committers present), I'm changing the defaults for remote > >services in /etc/defaults/rc.conf to the least dangerous > >configuration, and making sysinstall write out overrides for the > >variables to their former default values in /etc/rc.conf upon install. > > Hopefully sysinstall will be smarter about writing these overrides > than it is about writing the "USA_RESIDENT=NO" override to /etc/make.conf. It is. It only writes these variables out when it creats an /etc/rc.conf file from scratch because one doesn't exist. Normally this only happens during the install. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 17:39:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id 3D30B37B5C3; Fri, 28 Jul 2000 17:39:51 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA12353; Fri, 28 Jul 2000 17:39:50 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <398227D5.9E7AEAA5@gorean.org> Date: Fri, 28 Jul 2000 17:39:49 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Eivind Eklund Cc: current@FreeBSD.org Subject: Re: *** HEADS UP *** rc.conf changes (security) References: <20000729004143.M45306@ee.follo.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > This change might seem a little counterintuitive (given that > /etc/defaults/ are for defaults, after all) but seems to be the best > compromise for both getting the functionality jkh wants (freshly > installed boxes have active daemons, so users don't feel they have a > lot of extra hassle to get things up and working like they are used to > on other Unixen), and give FreeBSD a default secure config, meaning > the insecurities stand out. FWIW, I totally support this change. Personally, I think the default for everything should be "off," and the admin should be required to enable the services he needs. Eivind, it's good to see you, even semi-active. :) Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 19:23:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.mich.com (mercury.mich.com [64.79.64.32]) by hub.freebsd.org (Postfix) with ESMTP id 598F037BB75; Fri, 28 Jul 2000 19:23:14 -0700 (PDT) (envelope-from will@almanac.yi.org) Received: from argon.gryphonsoft.com (pm005-017.dialup.bignet.net [64.79.80.209]) by mercury.mich.com (8.9.3/8.9.3) with ESMTP id WAA20865; Fri, 28 Jul 2000 22:23:11 -0400 Received: by argon.gryphonsoft.com (Postfix, from userid 1000) id 4026D194F; Fri, 28 Jul 2000 22:20:06 -0400 (EDT) Date: Fri, 28 Jul 2000 22:20:06 -0400 From: Will Andrews To: Eivind Eklund Cc: current@FreeBSD.ORG Subject: Re: *** HEADS UP *** rc.conf changes (security) Message-ID: <20000728222006.B11880@argon.gryphonsoft.com> References: <20000729004143.M45306@ee.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000729004143.M45306@ee.follo.net>; from eivind@FreeBSD.ORG on Sat, Jul 29, 2000 at 12:41:43AM +0200 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 29, 2000 at 12:41:43AM +0200, Eivind Eklund wrote: > This means that anybody upgrading /etc/defaults/rc.conf needs to add > the following lines to rc.conf if they want to have the same setup > afterwards (unless the variables already are set, of course): > > # Enable network daemons for user convenience. > inetd_enable="YES" > portmap_enable="YES" > sendmail_enable="YES" Amen! Thank you. I tried to get inetd_enable="NO" by default earlier this month, but it didn't fly. :-P -- Will Andrews GCS/E/S @d- s+:+ a--- C++ UB++++$ P+ L- E--- W+ N-- !o ?K w--- O- M+ V- PS+ PE++ Y+ PGP+>+++ t++ 5 X+ R+ tv+ b++ DI+++ D+ G++ e>++++ h! r- y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 20: 8: 6 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 B4B0837B8F2 for ; Fri, 28 Jul 2000 20:08:01 -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, 28 Jul 2000 22:06:49 -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 WAA22006 for ; Fri, 28 Jul 2000 22:03:57 -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 WAA92212 for ; Fri, 28 Jul 2000 22:03:55 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200007290303.WAA92212@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: Compilation failure in current as of cvs-cur 6562 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Jul 2000 22:03:55 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone else seen this? chmod 755 /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/auto/DynaLoader/DynaLoader .a cc -O -pipe -I/usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -DPERL_CORE -I/usr/obj/usr/src/i386/usr/include -Wl,-E -L/usr/obj/usr/src/gnu/usr.bin/perl/ perl/../libperl -o perl perlmain.o lib/auto/DynaLoader/DynaLoader.a -lperl -lm -lcrypt -lmd cc: Internal compiler error: program ld got fatal signal 11 *** 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 *** Error code 2 1 error *** Error code 2 -- 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 Fri Jul 28 20:55:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from defused.digigod.org (defused.digigod.org [206.137.30.112]) by hub.freebsd.org (Postfix) with ESMTP id 144CB37B953 for ; Fri, 28 Jul 2000 20:55:44 -0700 (PDT) (envelope-from scorch@defused.digigod.org) Received: (from scorch@localhost) by east.under.dhs.org (8.9.3/8.9.3) id PAA27090; Sun, 12 Dec 1999 15:38:06 -0500 Date: Sun, 12 Dec 1999 15:38:06 -0500 From: scorch@defused.digigod.org Message-Id: <199912122038.PAA27090@east.under.dhs.org> To: freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-URL: http://www.freebsd.org/handbook/cutting-edge.html X-Mailer: Lynx, Version 2.8.1rel.2 Subject: Joining the mailing list Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am interested in joining the mailing list for freebsdcurrent. This can be e-mailed to: adpicket@iupui.edu or scorch@under.dhs.org Thanks, Aaron Pickett -- Scorch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 21:18:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id C461037B81B; Fri, 28 Jul 2000 21:18:46 -0700 (PDT) (envelope-from hanai@imgsrc.co.jp) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [210.226.20.130]) by white.imgsrc.co.jp (8.9.3+3.2W/3.7Wpl2-GW) with ESMTP id NAA56280; Sat, 29 Jul 2000 13:18:45 +0900 (JST) Received: from darkmatter.imgsrc.co.jp (darkmatter.imgsrc.co.jp [210.226.20.149]) by black.imgsrc.co.jp (8.9.3/3.7Wpl2-SPOOL) with ESMTP id NAA07763; Sat, 29 Jul 2000 13:18:45 +0900 (JST) Received: from darkmatter.imgsrc.co.jp (localhost [127.0.0.1]) by darkmatter.imgsrc.co.jp (Postfix) with ESMTP id AE9C3A2AB; Sat, 29 Jul 2000 13:18:47 +0900 (JST) Date: Sat, 29 Jul 2000 13:18:47 +0900 Message-ID: <8266pp602g.wl@darkmatter.imgsrc.co.jp> From: Hiroyuki Hanai To: current@FreeBSD.org Cc: markm@FreeBSD.org Subject: fcntl and /dev/random User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.6 (i386--freebsd) MULE/4.0 (HANANOEN) Organization: IMG SRC, Inc. 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 Setting status flags using F_SETFL command of fcntl(2) on the file descriptor, which is returned by open(2)ing /dev/random, seems not to be supported. For example, when I run following code; #include #include #include main() { int fd; fd = open("/dev/random", O_RDONLY); if (fcntl(fd, F_SETFL, O_NONBLOCK) == -1) { printf("%s\n", strerror(errno)); } } 3.4-RELEASE(and possibly 3.5 and 3.5.1) and 4.1-RELEASE/4.1-STABLE say `Inappropriate ioctl for device' and 5-current says `Operation not supported by device'. I've found above in BIND9's source and its `named' program complains everytime it's invoked. Should I fix BIND9's code? or wait for fcntl's F_SETFL being supported on FreeBSD? Actually, in BIND9, fd is already open(2)ed with `O_RDONLY | O_NONBLOCK' and setting O_NONBLOCK status with fcntl(2) is not needed, which means that fixing BIND9's code is very simple; just comment out the fcntl(2)ing line. h.hanai To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 28 23:51:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2EF0137B84C; Fri, 28 Jul 2000 23:51:16 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id XAA11149; Fri, 28 Jul 2000 23:51:08 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: Garance A Drosihn Cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: *** HEADS UP *** rc.conf changes (security) In-reply-to: Your message of "Fri, 28 Jul 2000 19:25:49 EDT." Date: Fri, 28 Jul 2000 23:51:08 -0700 Message-ID: <11146.964853468@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hopefully sysinstall will be smarter about writing these overrides > than it is about writing the "USA_RESIDENT=NO" override to /etc/make.conf. It doesn't do that anymore. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 0:47: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 3D08737B545; Sat, 29 Jul 2000 00:47:15 -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 JAA03041; Sat, 29 Jul 2000 09:47:14 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007290747.JAA03041@grimreaper.grondar.za> To: Hiroyuki Hanai Cc: current@FreeBSD.org, markm@FreeBSD.org Subject: Re: fcntl and /dev/random References: <8266pp602g.wl@darkmatter.imgsrc.co.jp> In-Reply-To: <8266pp602g.wl@darkmatter.imgsrc.co.jp> ; from Hiroyuki Hanai "Sat, 29 Jul 2000 13:18:47 +0900." Date: Sat, 29 Jul 2000 09:47:14 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I'm looking at this; I'll have something by the end of the weekend for 5-CURRENT; 4-STABLE will take a bit longer. I don't think I'll dop anything for 3-* as it is at its end-of-life. Domo Arrigato! M > > Setting status flags using F_SETFL command of fcntl(2) on the file > descriptor, which is returned by open(2)ing /dev/random, seems not to > be supported. For example, when I run following code; > > #include > #include > #include > main() > { > int fd; > fd = open("/dev/random", O_RDONLY); > if (fcntl(fd, F_SETFL, O_NONBLOCK) == -1) { > printf("%s\n", strerror(errno)); > } > } > > 3.4-RELEASE(and possibly 3.5 and 3.5.1) and 4.1-RELEASE/4.1-STABLE say > `Inappropriate ioctl for device' and 5-current says `Operation not > supported by device'. > > I've found above in BIND9's source and its `named' program complains > everytime it's invoked. > > Should I fix BIND9's code? or wait for fcntl's F_SETFL being > supported on FreeBSD? > > Actually, in BIND9, fd is already open(2)ed with `O_RDONLY | O_NONBLOCK' > and setting O_NONBLOCK status with fcntl(2) is not needed, which means > that fixing BIND9's code is very simple; just comment out the fcntl(2)ing lin e. > > h.hanai > -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 0:58:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 7123E37BA2E for ; Sat, 29 Jul 2000 00:58:51 -0700 (PDT) (envelope-from hanai@FreeBSD.org) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [210.226.20.130]) by white.imgsrc.co.jp (8.9.3+3.2W/3.7Wpl2-GW) with ESMTP id QAA57713; Sat, 29 Jul 2000 16:58:30 +0900 (JST) Received: from darkmatter.imgsrc.co.jp (darkmatter.imgsrc.co.jp [210.226.20.149]) by black.imgsrc.co.jp (8.9.3/3.7Wpl2-SPOOL) with ESMTP id QAA16138; Sat, 29 Jul 2000 16:58:29 +0900 (JST) Received: from darkmatter.imgsrc.co.jp (localhost [127.0.0.1]) by darkmatter.imgsrc.co.jp (Postfix) with ESMTP id 08CDA9EAB; Sat, 29 Jul 2000 16:58:33 +0900 (JST) Date: Sat, 29 Jul 2000 16:58:32 +0900 Message-ID: <82ya2l4bbr.wl@darkmatter.imgsrc.co.jp> From: Hiroyuki Hanai To: mark@grondar.za Cc: current@FreeBSD.org Subject: Re: fcntl and /dev/random In-Reply-To: In your message of "29 Jul 2000 07:48:16 GMT" <200007290747.JAA03041@grimreaper.grondar.za> References: <8266pp602g.wl@darkmatter.imgsrc.co.jp> <200007290747.JAA03041@grimreaper.grondar.za> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.6 (i386--freebsd) MULE/4.0 (HANANOEN) Organization: IMG SRC, Inc. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm looking at this; I'll have something by the end of the weekend > for 5-CURRENT; 4-STABLE will take a bit longer. I don't think I'll Wow, great. > dop anything for 3-* as it is at its end-of-life. I agree. We can ignore 3-* as long as they don't show any big problem. Cheers, h.hanai To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 1:18:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 84FE137B680; Sat, 29 Jul 2000 01:18:48 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Sat, 29 Jul 2000 04:18:47 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Hiroyuki Hanai Cc: current@FreeBSD.org, markm@FreeBSD.org Subject: Re: fcntl and /dev/random In-Reply-To: <8266pp602g.wl@darkmatter.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 Sat, 29 Jul 2000, Hiroyuki Hanai wrote: > > Setting status flags using F_SETFL command of fcntl(2) on the file > descriptor, which is returned by open(2)ing /dev/random, seems not to > be supported. For example, when I run following code; > > [...] > > 3.4-RELEASE(and possibly 3.5 and 3.5.1) and 4.1-RELEASE/4.1-STABLE say > `Inappropriate ioctl for device' and 5-current says `Operation not > supported by device'. EOPNOTSUPP is definitely wrong. Try this: Index: randomdev.c =================================================================== RCS file: /usr2/ncvs/src/sys/dev/randomdev/randomdev.c,v retrieving revision 1.10 diff -u -u -1 -r1.10 randomdev.c --- randomdev.c 2000/07/25 21:22:17 1.10 +++ randomdev.c 2000/07/29 08:12:47 @@ -51,2 +51,3 @@ static d_write_t random_write; +static d_ioctl_t random_ioctl; @@ -61,3 +62,3 @@ /* write */ random_write, - /* ioctl */ noioctl, + /* ioctl */ random_ioctl, /* poll */ nopoll, @@ -133,2 +134,9 @@ return error; +} + +static int +random_ioctl(dev_t dev, u_long cmd, caddr_t addr, int flags, struct proc *p) +{ + + return (ENOTTY); } > I've found above in BIND9's source and its `named' program complains > everytime it's invoked. > > Should I fix BIND9's code? or wait for fcntl's F_SETFL being > supported on FreeBSD? Err, this is a minor bug, but should definitely be fixed. > Actually, in BIND9, fd is already open(2)ed with `O_RDONLY | O_NONBLOCK' > and setting O_NONBLOCK status with fcntl(2) is not needed, which means > that fixing BIND9's code is very simple; just comment out the fcntl(2)ing line. I'd say send that to the maintainer :) > h.hanai -- 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 Sat Jul 29 1:35:35 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 1ED7137B58B for ; Sat, 29 Jul 2000 01:35:26 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #1) id 13IS5b-00019s-00 for current@freebsd.org; Sat, 29 Jul 2000 10:35:23 +0200 Received: from a2eb0.pppool.de ([213.6.46.176] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.16 #1) id 13IS5a-0000M4-00 for current@freebsd.org; Sat, 29 Jul 2000 10:35:22 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id KAA00512 for ; Sat, 29 Jul 2000 10:30:04 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200007290830.KAA00512@Magelan.Leidinger.net> Date: Sat, 29 Jul 2000 10:30:03 +0200 (CEST) From: Alexander Leidinger Subject: Panic in xpt_setup_ccb (cam_xpt.c) 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, 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 From owner-freebsd-current Sat Jul 29 1:48:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-097.telepath.com [216.14.0.97]) by hub.freebsd.org (Postfix) with SMTP id C98FA37BBA2 for ; Sat, 29 Jul 2000 01:48:21 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 49011 invoked by uid 100); 29 Jul 2000 08:48:20 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14722.39508.395980.576824@guru.mired.org> Date: Sat, 29 Jul 2000 03:48:20 -0500 (CDT) To: current@freebsd.org Subject: World breakage from exit->sys_exit change? 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 Ok, I give up. It seems that the world change from exit to sys_exit broke the world build, but I can't figure out where. I've fixed every occurence of SYS_exit in the source tree (this one seems to be src/lib/csu/i386/crt0.c, but there were some in gdb as well), and removed /usr/obj - and I still get the following error from buildworld: ===> bin/cat cc -O -pipe -march=pentium -Wall -Wformat -I/usr/obj/usr/src/i386/usr/include -c /usr/src/bin/cat/cat.c gzip -cn /usr/src/bin/cat/cat.1 > cat.1.gz cc -O -pipe -march=pentium -Wall -Wformat -I/usr/obj/usr/src/i386/usr/include -static -o cat cat.o /usr/obj/usr/src/i386/usr/lib/libc.a(_exit.o): In function `_exit': _exit.o(.text+0x2): undefined reference to `SYS_exit' *** Error code 1 1 error Is this one of those things that is going to require gyrations to get built? Thanx, ; Sat, 29 Jul 2000 02:07:40 -0700 (PDT) (envelope-from pierre.dampure@alveley.org) Received: from useri435.uk.uudial.com ([194.69.106.45] helo=alveley.org) by mailhost.netbenefit.co.uk with esmtp (NetBenefit 1.5) id 13ISam-0000Wl-00 ; Sat, 29 Jul 2000 10:07:36 +0100 Message-ID: <39829ED6.A9F015A0@alveley.org> Date: Sat, 29 Jul 2000 10:07:34 +0100 From: "Dampure, Pierre Y." X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Meyer Cc: current@freebsd.org Subject: Re: World breakage from exit->sys_exit change? References: <14722.39508.395980.576824@guru.mired.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > > Ok, I give up. It seems that the world change from exit to sys_exit > broke the world build, but I can't figure out where. I've fixed every > occurence of SYS_exit in the source tree (this one seems to be > src/lib/csu/i386/crt0.c, but there were some in gdb as well), and > removed /usr/obj - and I still get the following error from > buildworld: > I think this might be due to the fact that, for some reason, the build is still using the old syscall.h (the one that references SYS_exit rather than SYS_sys_exit -- ie. the installed one rather than the newly generated one). The funny thing here is I would have expected a make -DCLOBBER to take care of that... Regards, PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 2: 9:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id 5EC7D37B5EE for ; Sat, 29 Jul 2000 02:09:41 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.9.3/8.9.3) with ESMTP id CAA52842; Sat, 29 Jul 2000 02:09:39 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200007290909.CAA52842@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Meyer Cc: current@FreeBSD.ORG Subject: Re: World breakage from exit->sys_exit change? In-Reply-To: Message from Mike Meyer of "Sat, 29 Jul 2000 03:48:20 CDT." <14722.39508.395980.576824@guru.mired.org> Date: Sat, 29 Jul 2000 02:09:39 -0700 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Argh! I knew today was going to stay a bad day. I am pretty sure I know how to fix this and will commit a fix shortly. If you want to try now, edit sys/kern/syscalls.master: < 1 STD NOHIDE { void sys_exit(int rval); } sys_exit sys_exit_args void --- > 1 STD NOHIDE { void sys_exit(int rval); } exit sys_exit_args void and cd src/sys/kern; make init_sysent.c Then your world should build ok. Mike Meyer wrote: > Ok, I give up. It seems that the world change from exit to sys_exit > broke the world build, but I can't figure out where. I've fixed every > occurence of SYS_exit in the source tree (this one seems to be > src/lib/csu/i386/crt0.c, but there were some in gdb as well), and > removed /usr/obj - and I still get the following error from > buildworld: > > ===> bin/cat > cc -O -pipe -march=pentium -Wall -Wformat -I/usr/obj/usr/src/i386/usr/inclu de -c /usr/src/bin/cat/cat.c > gzip -cn /usr/src/bin/cat/cat.1 > cat.1.gz > cc -O -pipe -march=pentium -Wall -Wformat -I/usr/obj/usr/src/i386/usr/inclu de -static -o cat cat.o > /usr/obj/usr/src/i386/usr/lib/libc.a(_exit.o): In function `_exit': > _exit.o(.text+0x2): undefined reference to `SYS_exit' > *** Error code 1 > 1 error > > Is this one of those things that is going to require gyrations to get > built? > > Thanx, > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 3: 8:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-097.telepath.com [216.14.0.97]) by hub.freebsd.org (Postfix) with SMTP id 3ED1337BBCC for ; Sat, 29 Jul 2000 03:07:53 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 95905 invoked by uid 100); 29 Jul 2000 10:07:28 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14722.44255.914811.175753@guru.mired.org> Date: Sat, 29 Jul 2000 05:07:27 -0500 (CDT) To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: World breakage from exit->sys_exit change? In-Reply-To: <200007290909.CAA52842@netplex.com.au> References: <14722.39508.395980.576824@guru.mired.org> <200007290909.CAA52842@netplex.com.au> 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 Peter Wemm writes: > Argh! I knew today was going to stay a bad day. I had similar thoughts about mine, both before I started the build, and afterwards. > I am pretty sure I know how to fix this and will commit a fix shortly. If you > want to try now, edit sys/kern/syscalls.master: > < 1 STD NOHIDE { void sys_exit(int rval); } sys_exit sys_exit_args void > --- > > 1 STD NOHIDE { void sys_exit(int rval); } exit sys_exit_args void > and cd src/sys/kern; make init_sysent.c > Then your world should build ok. That fix indeed seems to work (it managed to build cat), and looks saner than mine. Thanx, ; Sat, 29 Jul 2000 07:19:00 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.9.3/8.9.3) with ESMTP id HAA56376; Sat, 29 Jul 2000 07:18:59 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200007291418.HAA56376@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Meyer Cc: current@FreeBSD.ORG Subject: Re: World breakage from exit->sys_exit change? In-Reply-To: <14722.44255.914811.175753@guru.mired.org> Date: Sat, 29 Jul 2000 07:18:59 -0700 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > Peter Wemm writes: > > Argh! I knew today was going to stay a bad day. > > I had similar thoughts about mine, both before I started the build, > and afterwards. > > > I am pretty sure I know how to fix this and will commit a fix shortly. If you > > want to try now, edit sys/kern/syscalls.master: > > < 1 STD NOHIDE { void sys_exit(int rval); } sys_exit sys_exit_args void > > --- > > > 1 STD NOHIDE { void sys_exit(int rval); } exit sys_exit_args voi d > > and cd src/sys/kern; make init_sysent.c > > Then your world should build ok. > > That fix indeed seems to work (it managed to build cat), and looks > saner than mine. Anyway, it should be all fixed now (and has been committed for a while). Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 7:46:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from flow.isolve.dk (flow.isolve.dk [195.249.214.175]) by hub.freebsd.org (Postfix) with ESMTP id DE7D037B8A0 for ; Sat, 29 Jul 2000 07:46:38 -0700 (PDT) (envelope-from voland@flow.isolve.dk) Received: (from voland@localhost) by flow.isolve.dk (8.9.3/8.9.3) id QAA04837 for current@FreeBSD.ORG; Sat, 29 Jul 2000 16:45:55 +0200 (CEST) (envelope-from voland) Date: Sat, 29 Jul 2000 16:45:55 +0200 From: Vadim Belman To: current@FreeBSD.ORG Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking Message-ID: <20000729164554.A4778@flow.isolve.dk> Mail-Followup-To: current@FreeBSD.ORG References: <20000728141728.A44135@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: <20000728141728.A44135@freebsd.org>; from ache@FreeBSD.ORG on Fri, Jul 28, 2000 at 02:17:31PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 28, 2000 at 02:17:31PM -0700, Andrey A. Chernov wrote: > I too. The only way I can avoid this panic is > > 1) Remove /erc/rc.shutdown (which write files) > 2) Do several syns manually before reboot. > > In all other situations I got this panic. Just another way (suggested by a friend of my) is to shutdown into the single user mode, umount every filesystem, forcibly remount / into read-only mode - and then reboot. Gonna try putting this into /etc/rc.shutdown. -- /Voland Vadim Belman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 9:44:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 4803737B66C; Sat, 29 Jul 2000 09:44:25 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id CAA08791; Sun, 30 Jul 2000 02:44:07 +1000 Date: Sun, 30 Jul 2000 02:44:04 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Hiroyuki Hanai Cc: current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: fcntl and /dev/random In-Reply-To: <8266pp602g.wl@darkmatter.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 n Sat, 29 Jul 2000, Hiroyuki Hanai wrote: > Setting status flags using F_SETFL command of fcntl(2) on the file > descriptor, which is returned by open(2)ing /dev/random, seems not to > be supported. For example, when I run following code; File flags should be handled at the file level, and mostly are, but drivers still need dummy FIONBIO and FIOASYNC ioctls to prevent the fo_ioctl()'s in kern_descrip.c:fcntl() from failing (there must be dummy for FIOASYNC for setting O_NONBLOCK to work, even if the device driver doesn't support async i/o :-(). Broken drivers use these ioctls to make copies of the file flags in the wrong place. Non-broken drivers use the flags passed to their i/o functions, so that the flags are per-i/o. > 3.4-RELEASE(and possibly 3.5 and 3.5.1) and 4.1-RELEASE/4.1-STABLE say > `Inappropriate ioctl for device' and 5-current says `Operation not > supported by device'. This is a different bug. The random device in -current doesn't support ioctls at all, so all ioctls on it return ENODEV instead of most ioctls on it returning ENOTTY. See the patch by Brian Feldman. > Actually, in BIND9, fd is already open(2)ed with `O_RDONLY | O_NONBLOCK' > and setting O_NONBLOCK status with fcntl(2) is not needed, which means > that fixing BIND9's code is very simple; just comment out the fcntl(2)ing line. Except the random device doesn't actually support the O_NONBLOCK flag. This makes no difference in the -current random device, since all i/o is non-blocking. In 3.x and 4.x, O_NONBLOCK should have caused reads on /dev/random to not block. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 12:55:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4604437B554 for ; Sat, 29 Jul 2000 12:55:21 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA14417; Sat, 29 Jul 2000 12:55:14 -0700 Date: Sat, 29 Jul 2000 12:55:17 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com 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 What hardware? 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 15:21:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 808B637B870 for ; Sat, 29 Jul 2000 15:21:49 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #1) id 13IezH-0001J7-00; Sun, 30 Jul 2000 00:21:43 +0200 Received: from a2dac.pppool.de ([213.6.45.172] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.16 #1) id 13IezC-0007OG-00; Sun, 30 Jul 2000 00:21:40 +0200 Received: from Leidinger.net (localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id XAA03679; Sat, 29 Jul 2000 23:14:11 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200007292114.XAA03679@Magelan.Leidinger.net> Date: Sat, 29 Jul 2000 23:14:09 +0200 (CEST) From: Alexander Leidinger Subject: Re: Panic in xpt_setup_ccb (cam_xpt.c) To: mjacob@feral.com Cc: current@FreeBSD.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 29 Jul, Matthew Jacob wrote: > > What hardware? ahc0: port 0xb000-0xb0ff mem 0xd9800000-0xd9800fff irq 9 at device 6.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs cd0 at ahc0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd1 at ahc0 bus 0 target 2 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) The panic was with cd0. Bye, Alexander. -- ...and that is how we know the Earth to be banana-shaped. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 16:26:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id E282337B8DC; Sat, 29 Jul 2000 16:26:44 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13IfJE-000EyC-00; Sat, 29 Jul 2000 23:42:20 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13IfJE-000Ow0-00; Sat, 29 Jul 2000 23:42:20 +0100 Date: Sat, 29 Jul 2000 23:42:20 +0100 From: Ben Smithurst To: current@FreeBSD.org, obrien@FreeBSD.org Subject: Re: Broadcast address with DHCP Message-ID: <20000729234220.H59315@strontium.scientia.demon.co.uk> References: <20000727133839.A59315@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000727133839.A59315@strontium.scientia.demon.co.uk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst wrote: > dhclient seems to be broken, it's giving me the all zeroes broadcast > address instead of all ones: > > inet 192.168.91.35 netmask 0xfffffff0 broadcast 192.168.91.32 > > (should be broadcast 192.168.91.47) ok, ignore this, it seems to be working after another buildworld. I'm not sure why it broke in the first place. :-( -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 17:25: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from numbertwo.domainfactory.de (numbertwo.domainfactory.de [194.221.134.226]) by hub.freebsd.org (Postfix) with SMTP id 7ADF137B589 for ; Sat, 29 Jul 2000 17:24:53 -0700 (PDT) (envelope-from steele@cloaked.de) Received: (qmail 5277 invoked from network); 30 Jul 2000 00:24:48 -0000 Received: from p3ee0d0d3.dip0.t-ipconnect.de (HELO steele.intra) ([62.224.208.211]) (envelope-sender ) by numbertwo.domainfactory.de (qmail-ldap-1.03) with SMTP for ; 30 Jul 2000 00:24:48 -0000 Received: (from steele@localhost) by steele.intra (8.9.3/8.9.3) id CAA85933 for freebsd-current@freebsd.org; Sun, 30 Jul 2000 02:24:38 +0200 (CEST) (envelope-from steele) Date: Sun, 30 Jul 2000 02:24:38 +0200 From: Benedikt Schmidt To: freebsd-current@freebsd.org Subject: Re: Mouse frozen in X when returning from text console Message-ID: <20000730022438.A83157@cloaked.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from kabaev@mail.ru on Wed, Jul 26, 2000 at 11:12:34PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 26, 2000 at 11:12:34PM -0400, Alexander N. Kabaev wrote: > There was a patch floating around which fixed these mouse problems for me. > The patch solves the problem here too. Perhaps it could be added to the other FreeBSD patches in the XFree86-4 port. Benedikt Schmidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 17:27:53 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 DFD7037B548 for ; Sat, 29 Jul 2000 17:27: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 CAA58790 for freebsd-current@freebsd.org; Sun, 30 Jul 2000 02:27:44 +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 CAA84768 for ; Sun, 30 Jul 2000 02:22:51 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Sun, 30 Jul 2000 02:22:21 +0200 (CEST) From: Leif Neland To: freebsd-current@freebsd.org Subject: sendmail 8.11.0 trouble 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 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? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 20:38:24 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 C707F37B875; Sat, 29 Jul 2000 20:38:19 -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 XAA19638; Sat, 29 Jul 2000 23:38:17 -0400 (EDT) Message-ID: <3983A329.B37CE8BA@acm.org> Date: Sat, 29 Jul 2000 23:38:17 -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 Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern kern_event.c References: <200007272306.QAA41002@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 Sat Jul 29 21:25:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6D06937B512; Sat, 29 Jul 2000 21:25:44 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Sun, 30 Jul 2000 00:25:42 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: "Jeroen C. van Gelderen" Cc: Mark Murray , Kris Kennaway , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <397CF299.9F89E1CA@vangelderen.org> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-903383323-964931142=:8844" 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-903383323-964931142=:8844 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 24 Jul 2000, Jeroen C. van Gelderen wrote: > > > What I meant with that point is that the user may get, say an extra few > > > hundred bits out of it with no new entropy before the scheduled reseed > > > task kicks in. > > > > How does he know which bits are which? His analysis task just got a whole > > lot more difficult. > > Again, not entirely correct but not relevant either... > > Kris is simply right in that the /dev/random semantics change > and that more bits can be output by Yarrow than there is entropy > gathered. *In theory* the complexity of an attack on our Yarrow > has an upper bound of 2^256 and *in theory* this is less than > the complexity of an attack on our current /dev/random. This is > a hard fact, no way around that. Even if the attack on a single non-blocking read from Yarrow is only of 2^256 complexity, it is designed to be much more expensive than just cracking a single block cipher. Blowfish has a very large keying step, and Yarrow is designed to exploit having large keying steps and then adding more complexity in its setup in addition. This makes it infeasible to mount attacks on Yarrow, and the security is really not as weak as just cracking 20-round Blowfish-256. However, none of this makes Yarrow useless for getting many bits of high-quality random data for, e.g., generation of an RSA key. > However, the big question here is not about theory but about > *practicality*. Is Yarrow less secure than /dev/random in > practice? How does our /dev/random hold up under attack? How > does Yarrow compare? I think we need to evaluate these practical > questions instead of deep theoretical issues as Yarrow is all > about practicality. > > At a more fundamental level we will need to answer the question: > "Do we need to preserve the current /dev/random semantics or > can we decide to change 'em? [1]". And how will this affect our > applications *in practice*. 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. Can you really find anything wrong with doing what I propose *in practice*? I'm certain that it would make it about as hard to brute-force the key while knowing certain parameters of its generation as it would be to just factor the damned 1024-bit number. I've already implemented this as well as some other bugfixes, so see the attached diff. > So let's concentrate this discussion on the practical issues > and explain why you think backing /dev/random with Yarrow and > changing the semantics is justifyable or even a good thing. > > Cheers, > Jeroen > > [1] And, should we decide not to change /dev/random semantics, > can we still back /dev/random with a modified Yarrow? I think it makes sense :) > -- > Jeroen C. van Gelderen o _ _ _ > jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) > _< \_ _>(_) (_)/<_ \_| \ _|/' \/ > (_)>(_) (_) (_) (_) (_)' _\o_ -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' --0-903383323-964931142=:8844 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="yarrow_blocking.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="yarrow_blocking.patch" SW5kZXg6IHN5cy9zeXMvcmFuZG9tLmgNCj09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT0NClJDUyBmaWxlOiAvdXNyMi9uY3ZzL3NyYy9zeXMvc3lzL3JhbmRvbS5o LHYNCnJldHJpZXZpbmcgcmV2aXNpb24gMS4yNQ0KZGlmZiAtdSAtcjEuMjUg cmFuZG9tLmgNCi0tLSBzeXMvc3lzL3JhbmRvbS5oCTIwMDAvMDcvMjUgMjE6 MTg6NDUJMS4yNQ0KKysrIHN5cy9zeXMvcmFuZG9tLmgJMjAwMC8wNy8yOSAy MzoxOToyMA0KQEAgLTM2LDYgKzM2LDggQEANCiBlbnVtIGVzb3VyY2UgeyBS QU5ET01fV1JJVEUsIFJBTkRPTV9LRVlCT0FSRCwgUkFORE9NX01PVVNFLCBS QU5ET01fTkVULCBcDQogCQlFTlRST1BZU09VUkNFIH07DQogdm9pZCByYW5k b21faGFydmVzdCh2b2lkICosIHVfaW50LCB1X2ludCwgdV9pbnQsIGVudW0g ZXNvdXJjZSk7DQordm9pZCBzZXRfd2FrZXVwKGludCAqLCBpbnQpOw0KK3Zv aWQgc2V0X3dha2V1cF9leGl0KGludCAqLCBpbnQsIGludCk7DQogDQogI2Vu ZGlmDQogDQpJbmRleDogc3lzL2Rldi9yYW5kb21kZXYvaGFydmVzdC5jDQo9 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09DQpSQ1MgZmlsZTogL3VzcjIvbmN2cy9z cmMvc3lzL2Rldi9yYW5kb21kZXYvaGFydmVzdC5jLHYNCnJldHJpZXZpbmcg cmV2aXNpb24gMS40DQpkaWZmIC11IC1yMS40IGhhcnZlc3QuYw0KLS0tIHN5 cy9kZXYvcmFuZG9tZGV2L2hhcnZlc3QuYwkyMDAwLzA3LzI1IDIxOjE4OjQ2 CTEuNA0KKysrIHN5cy9kZXYvcmFuZG9tZGV2L2hhcnZlc3QuYwkyMDAwLzA3 LzI5IDIzOjE4OjUwDQpAQCAtMzAsNiArMzAsNyBAQA0KICNpbmNsdWRlIDxz eXMvc3lzdG0uaD4NCiAjaW5jbHVkZSA8c3lzL3R5cGVzLmg+DQogI2luY2x1 ZGUgPHN5cy9xdWV1ZS5oPg0KKyNpbmNsdWRlIDxzeXMva3RocmVhZC5oPg0K ICNpbmNsdWRlIDxzeXMvbGlua2VyLmg+DQogI2luY2x1ZGUgPHN5cy9saWJr ZXJuLmg+DQogI2luY2x1ZGUgPHN5cy9tYnVmLmg+DQpAQCAtNzIsNCArNzMs MjMgQEANCiAJCW5hbm90aW1lKCZ0aW1lYnVmKTsNCiAJCSgqcmVhcCkoJnRp bWVidWYsIGVudHJvcHksIGNvdW50LCBiaXRzLCBmcmFjLCBvcmlnaW4pOw0K IAl9DQorfQ0KKw0KKy8qDQorICogSGVscGVyIHJvdXRpbmVzIHRvIGxldCBr dGhyZWFkX2V4aXQoKSBkbyBpdHMgc3R1ZmYgcHJvcGVybHkgKGkuZS4gbm8g Y3Jhc2gpLg0KKyAqLw0KK3ZvaWQNCitzZXRfd2FrZXVwKGludCAqdmFyLCBp bnQgdmFsdWUpDQorew0KKw0KKwkqdmFyID0gdmFsdWU7DQorCXdha2V1cCh2 YXIpOw0KK30NCisNCit2b2lkDQorc2V0X3dha2V1cF9leGl0KGludCAqdmFy LCBpbnQgdmFsdWUsIGludCBleGl0dmFsKQ0KK3sNCisNCisJc2V0X3dha2V1 cCh2YXIsIHZhbHVlKTsNCisJa3RocmVhZF9leGl0KGV4aXR2YWwpOw0KIH0N CkluZGV4OiBzeXMvZGV2L3JhbmRvbWRldi9yYW5kb21kZXYuYw0KPT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PQ0KUkNTIGZpbGU6IC91c3IyL25jdnMvc3JjL3N5 cy9kZXYvcmFuZG9tZGV2L3JhbmRvbWRldi5jLHYNCnJldHJpZXZpbmcgcmV2 aXNpb24gMS4xMA0KZGlmZiAtdSAtcjEuMTAgcmFuZG9tZGV2LmMNCi0tLSBz eXMvZGV2L3JhbmRvbWRldi9yYW5kb21kZXYuYwkyMDAwLzA3LzI1IDIxOjIy OjE3CTEuMTANCisrKyBzeXMvZGV2L3JhbmRvbWRldi9yYW5kb21kZXYuYwky MDAwLzA3LzMwIDAzOjAwOjAxDQpAQCAtMzEsNiArMzEsNyBAQA0KICNpbmNs dWRlIDxzeXMvc3lzdG0uaD4NCiAjaW5jbHVkZSA8c3lzL2NvbmYuaD4NCiAj aW5jbHVkZSA8c3lzL2ZjbnRsLmg+DQorI2luY2x1ZGUgPHN5cy9maWxpby5o Pg0KICNpbmNsdWRlIDxzeXMvdWlvLmg+DQogI2luY2x1ZGUgPHN5cy9rZXJu ZWwuaD4NCiAjaW5jbHVkZSA8c3lzL21hbGxvYy5oPg0KQEAgLTQyLDYgKzQz LDcgQEANCiAjaW5jbHVkZSA8c3lzL3JtYW4uaD4NCiAjaW5jbHVkZSA8c3lz L3NpZ25hbHZhci5oPg0KICNpbmNsdWRlIDxzeXMvc3lzY3RsLmg+DQorI2lu Y2x1ZGUgPHN5cy92bm9kZS5oPg0KICNpbmNsdWRlIDxjcnlwdG8vYmxvd2Zp c2gvYmxvd2Zpc2guaD4NCiANCiAjaW5jbHVkZSA8ZGV2L3JhbmRvbWRldi95 YXJyb3cuaD4NCkBAIC00OSw2ICs1MSw3IEBADQogc3RhdGljIGRfb3Blbl90 IHJhbmRvbV9vcGVuOw0KIHN0YXRpYyBkX3JlYWRfdCByYW5kb21fcmVhZDsN CiBzdGF0aWMgZF93cml0ZV90IHJhbmRvbV93cml0ZTsNCitzdGF0aWMgZF9p b2N0bF90IHJhbmRvbV9pb2N0bDsNCiANCiAjZGVmaW5lIENERVZfTUFKT1IJ Mg0KICNkZWZpbmUgUkFORE9NX01JTk9SCTMNCkBAIC01OSw3ICs2Miw3IEBA DQogCS8qIGNsb3NlICovCShkX2Nsb3NlX3QgKiludWxsb3AsDQogCS8qIHJl YWQgKi8JcmFuZG9tX3JlYWQsDQogCS8qIHdyaXRlICovCXJhbmRvbV93cml0 ZSwNCi0JLyogaW9jdGwgKi8Jbm9pb2N0bCwNCisJLyogaW9jdGwgKi8JcmFu ZG9tX2lvY3RsLA0KIAkvKiBwb2xsICovCW5vcG9sbCwNCiAJLyogbW1hcCAq Lwlub21tYXAsDQogCS8qIHN0cmF0ZWd5ICovCW5vc3RyYXRlZ3ksDQpAQCAt MTAxLDE0ICsxMDQsMzAgQEANCiByYW5kb21fcmVhZChkZXZfdCBkZXYsIHN0 cnVjdCB1aW8gKnVpbywgaW50IGZsYWcpDQogew0KIAl1X2ludCBjLCByZXQ7 DQotCWludCBlcnJvciA9IDA7DQorCWludCBlcnJvciA9IDAsIGxlZnQ7DQog CXZvaWQgKnJhbmRvbV9idWY7DQogDQogCWMgPSBtaW4odWlvLT51aW9fcmVz aWQsIFBBR0VfU0laRSk7DQogCXJhbmRvbV9idWYgPSAodm9pZCAqKW1hbGxv YyhjLCBNX1RFTVAsIE1fV0FJVE9LKTsNCi0Jd2hpbGUgKHVpby0+dWlvX3Jl c2lkID4gMCAmJiBlcnJvciA9PSAwKSB7DQotCQlyZXQgPSByZWFkX3JhbmRv bShyYW5kb21fYnVmLCBjKTsNCi0JCWVycm9yID0gdWlvbW92ZShyYW5kb21f YnVmLCByZXQsIHVpbyk7DQorCWlmIChtaW5vcihkZXYpID09IFVSQU5ET01f TUlOT1IpIHsNCisJCXdoaWxlICh1aW8tPnVpb19yZXNpZCA+IDAgJiYgZXJy b3IgPT0gMCkgew0KKwkJCXJldCA9IHJlYWRfcmFuZG9tKHJhbmRvbV9idWYs IG1pbihjLCB1aW8tPnVpb19yZXNpZCkpOw0KKwkJCWVycm9yID0gdWlvbW92 ZShyYW5kb21fYnVmLCByZXQsIHVpbyk7DQorCQl9DQorCX0gZWxzZSB7DQor CQlpZiAoZmxhZyAmIElPX05ERUxBWSB8fCBjIDw9IEtFWVNJWkUpIHsNCisJ CQlyZXQgPSByZWFkX3JhbmRvbShyYW5kb21fYnVmLCBjKTsNCisJCQllcnJv ciA9IHVpb21vdmUocmFuZG9tX2J1ZiwgcmV0LCB1aW8pOw0KKwkJfSBlbHNl IHsNCisJCQl3aGlsZSAodWlvLT51aW9fcmVzaWQgPiAwICYmIGVycm9yID09 IDApIHsNCisJCQkJbGVmdCA9IG1pbihLRVlTSVpFLCB1aW8tPnVpb19yZXNp ZCk7DQorCQkJCXJldCA9IHJlYWRfcmFuZG9tKHJhbmRvbV9idWYsIGxlZnQp Ow0KKwkJCQllcnJvciA9IHVpb21vdmUocmFuZG9tX2J1ZiwgbGVmdCwgdWlv KTsNCisJCQkJaWYgKGVycm9yID09IDApDQorCQkJCQllcnJvciA9IHRzbGVl cChyZWFkX3JhbmRvbSwNCisJCQkJCSAgICBQUEFVU0UgfCBQQ0FUQ0gsICJ5 YXJyb3ciLCAwKTsNCisJCQl9DQorCQl9DQogCX0NCiAJZnJlZShyYW5kb21f YnVmLCBNX1RFTVApOw0KIAlyZXR1cm4gZXJyb3I7DQpAQCAtMTM0LDYgKzE1 MywxOCBAQA0KIH0NCiANCiBzdGF0aWMgaW50DQorcmFuZG9tX2lvY3RsKGRl dl90IGRldiwgdV9sb25nIGNtZCwgY2FkZHJfdCBhZGRyLCBpbnQgZmxhZ3Ms IHN0cnVjdCBwcm9jICpwKQ0KK3sNCisNCisJc3dpdGNoIChjbWQpIHsNCisJ Y2FzZSBGSU9OQklPOg0KKwkJcmV0dXJuICgwKTsNCisJZGVmYXVsdDoNCisJ CXJldHVybiAoRU5PVFRZKTsNCisJfQ0KK30NCisNCitzdGF0aWMgaW50DQog cmFuZG9tX21vZGV2ZW50KG1vZHVsZV90IG1vZCwgaW50IHR5cGUsIHZvaWQg KmRhdGEpDQogew0KIAlzd2l0Y2godHlwZSkgew0KQEAgLTE0OCw5ICsxNzks MTEgQEANCiAJCXJldHVybiAwOw0KIA0KIAljYXNlIE1PRF9VTkxPQUQ6DQot CQlyYW5kb21fZGVpbml0KCk7DQorCQlpZiAoY291bnRfZGV2KHJhbmRvbV9k ZXYpICE9IDAgfHwgY291bnRfZGV2KHVyYW5kb21fZGV2KSAhPSAwKQ0KKwkJ CXJldHVybiBFQlVTWTsNCiAJCWRlc3Ryb3lfZGV2KHJhbmRvbV9kZXYpOw0K IAkJZGVzdHJveV9kZXYodXJhbmRvbV9kZXYpOw0KKwkJcmFuZG9tX2RlaW5p dCgpOw0KIAkJcmV0dXJuIDA7DQogDQogCWNhc2UgTU9EX1NIVVRET1dOOg0K SW5kZXg6IHN5cy9kZXYvcmFuZG9tZGV2L3lhcnJvdy5jDQo9PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09DQpSQ1MgZmlsZTogL3VzcjIvbmN2cy9zcmMvc3lzL2Rl di9yYW5kb21kZXYveWFycm93LmMsdg0KcmV0cmlldmluZyByZXZpc2lvbiAx LjE0DQpkaWZmIC11IC1yMS4xNCB5YXJyb3cuYw0KLS0tIHN5cy9kZXYvcmFu ZG9tZGV2L3lhcnJvdy5jCTIwMDAvMDcvMjUgMjE6MjI6MTcJMS4xNA0KKysr IHN5cy9kZXYvcmFuZG9tZGV2L3lhcnJvdy5jCTIwMDAvMDcvMjkgMjM6MTQ6 NDINCkBAIC0yMTMsNiArMjEzLDkgQEANCiANCiAJLyogNy4gRHVtcCB0byBz ZWVkIGZpbGUgKGRvbmUgYnkgZXh0ZXJuYWwgcHJvY2VzcykgKi8NCiANCisJ LyogV2FrZSB1cCBhbnlvbmUgd2FpdGluZyBmb3IgYSByZXNlZWQuICovDQor DQorCXdha2V1cChyZWFkX3JhbmRvbSk7DQogfQ0KIA0KIHVfaW50DQpAQCAt MjIxLDcgKzIyNCw3IEBADQogCXN0YXRpYyB1X2ludDY0X3QgZ2VudmFsOw0K IAlzdGF0aWMgaW50IGN1ciA9IDA7DQogCXN0YXRpYyBpbnQgZ2F0ZSA9IDE7 DQotCXVfaW50IGk7DQorCXVfaW50IGksIGxlZnQ7DQogCXVfaW50IHJldHZh bDsNCiAJaW50cm1hc2tfdCBtYXNrOw0KIA0KQEAgLTI0MSwxMyArMjQ0LDEz IEBADQogCQkJCSh1bnNpZ25lZCBjaGFyICopJmdlbnZhbCwNCiAJCQkJc2l6 ZW9mKHJhbmRvbV9zdGF0ZS5jb3VudGVyKSwNCiAJCQkJJnJhbmRvbV9zdGF0 ZS5rZXksIHJhbmRvbV9zdGF0ZS5pdmVjLCBCRl9FTkNSWVBUKTsNCi0JCQlt ZW1jcHkoKGNoYXIgKilidWYgKyBpLCAmZ2VudmFsLA0KLQkJCQlzaXplb2Yo cmFuZG9tX3N0YXRlLmNvdW50ZXIpKTsNCisJCQlsZWZ0ID0gbWluKGNvdW50 IC0gaSwgc2l6ZW9mKHJhbmRvbV9zdGF0ZS5jb3VudGVyKSk7DQorCQkJbWVt Y3B5KChjaGFyICopYnVmICsgaSwgJmdlbnZhbCwgbGVmdCk7DQogCQkJaWYg KCsrcmFuZG9tX3N0YXRlLm91dHB1dGJsb2NrcyA+PSByYW5kb21fc3RhdGUu Z2VuZ2F0ZWludGVydmFsKSB7DQogCQkJCWdlbmVyYXRvcl9nYXRlKCk7DQog CQkJCXJhbmRvbV9zdGF0ZS5vdXRwdXRibG9ja3MgPSAwOw0KIAkJCX0NCi0J CQlyZXR2YWwgKz0gc2l6ZW9mKHJhbmRvbV9zdGF0ZS5jb3VudGVyKTsNCisJ CQlyZXR2YWwgKz0gbGVmdDsNCiAJCX0NCiAJfQ0KIAllbHNlIHsNCg== --0-903383323-964931142=:8844-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 21:27:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from joe.halenet.com.au (joe.halenet.com.au [203.37.141.114]) by hub.freebsd.org (Postfix) with ESMTP id E58DD37B689 for ; Sat, 29 Jul 2000 21:27:28 -0700 (PDT) (envelope-from timbo@halenet.com.au) Received: from temp19 (temp19.halenet.com.au [203.37.141.119]) by joe.halenet.com.au (8.9.1/8.9.1) with SMTP id OAA04499 for ; Sun, 30 Jul 2000 14:53:24 +1000 (EST) (envelope-from timbo@halenet.com.au) Message-ID: <005801bff9de$f8777ee0$778d25cb@halenet.com.au> From: "Tim McCullagh" To: Subject: Unable to install FreeBSD Release 4.1 Keyboard is not present Date: Sun, 30 Jul 2000 14:31:02 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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 Hi All Has anyone had any difficulty loading release 4.1 ? I have a Tyan Thunder Main board with 128 MB ram When I try and install it bypasses the kernel configuration and takes me straight to the /stand/sysinstall menu. There is also no keyboard support, therefore I am unable to complete an install. I have tried the boot floppies on another machine with a non ps2 keyboard and it worked fine. The machine I am trying to load to can run the boot floppies for release 4.0 without any difficulties. Has anyone else had similar difficulties with ps 2 keyboards on release 4.1 Please reply directly as I am not on the current mailing list Thanks in advance Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 22:25:33 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 1B75437B8F6; Sat, 29 Jul 2000 22:25:22 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id CB35E49; Sun, 30 Jul 2000 01:25:18 -0400 (AST) Message-ID: <3983BC3E.B100117D@vangelderen.org> Date: Sun, 30 Jul 2000 01:25:18 -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: Brian Fundakowski Feldman Cc: Mark Murray , Kris Kennaway , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Fundakowski Feldman wrote: > > On Mon, 24 Jul 2000, Jeroen C. van Gelderen wrote: > > > > > What I meant with that point is that the user may get, say an extra few > > > > hundred bits out of it with no new entropy before the scheduled reseed > > > > task kicks in. > > > > > > How does he know which bits are which? His analysis task just got a whole > > > lot more difficult. > > > > Again, not entirely correct but not relevant either... > > > > Kris is simply right in that the /dev/random semantics change > > and that more bits can be output by Yarrow than there is entropy > > gathered. *In theory* the complexity of an attack on our Yarrow > > has an upper bound of 2^256 and *in theory* this is less than > > the complexity of an attack on our current /dev/random. This is > > a hard fact, no way around that. > > Even if the attack on a single non-blocking read from Yarrow is only > of 2^256 complexity, it is designed to be much more expensive than > just cracking a single block cipher. Blowfish has a very large keying > > step, and Yarrow is designed to exploit having large keying steps and > then adding more complexity in its setup in addition. This makes it > infeasible to mount attacks on Yarrow, and the security is really not > as weak as just cracking 20-round Blowfish-256. Actually, it is. The low key agility doesn't add anything in terms of practical security because it only affects brute force attacks and can be optimized out in a pipelined implementation. Expensive, yes, but can be done. There is some more details on this in the Yarrow paper I think... Anyway, not that is matters, Yarrow was designed to be as secure as the underlying blockcipher and Blowfish is generally considered to be reasonably secure. So, the security still is 2^256 maximum, no way around that. > However, none of this makes Yarrow useless for getting many bits of > high-quality random data for, e.g., generation of an RSA key. Well, you will need to back that up with arguments if you want to convince the more sceptical (not me). A mere statement will not do it, you need proof or at least arguments :-) The question that Kris posed basically boiled down to: "Does 2^256 complexity equal 2^x (x > 256) complexity in practice?" . I can't think of a practical system where it wouldn't be sufficient in practice but that's just me. Well, you seem to agree and MarkM seems to too. Hmm, maybe the complainers should provide proof that they do need more than 2^256 complexity. Makes it easier for us, proponents ;-/ Also, since a 1024 RSA-key only has ~2^77 complexity it isn't a very good example. A more interesting question is, what if you generate a couple of 256-bit symmetric keys in a row. Their total complexity is 2^256 which is less than they could have. Does that matter in practice? > Mark already stated that in *practicality*, Yarrow-BF-cbc-256 1.0 > (I guess that's the proper name for this :-) According to Bruce S. one would call it Yarrow-256 (implementation details go here) You would definately spell out Blowfish completely. Btw, how exactly is the hash actually constructed in our Yarrow? I wonder how one constructs a 256-bit hash out of Blowfish with a 64-bit block size. A quick explanation would be appreciated. > 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. Sounds like a good idea. It looks like it would be reasonably easy to then add an extra entropy counter to the pool from which you subtract the number of bits that are output and to which you add the number of entropy bits that are mixed in. You can then extract bytes until that counter hits 0 and then block until it goes positive again which would ensure that the entropy output trough /dev/random is not re-used for output trough /dev/urandom. This would not affect the security of Yarrow at all but preserve the semantics of /dev/random almost completely. > Can you really find anything wrong with doing what I propose *in > practice*? No. Although I think you can make it nearly perfect by incorporating the above suggestion. You would then *never* return more bits than you have gathered entropy and you would never use those entropy bits twice. > I've > already implemented this as well as some other bugfixes, so see the > attached diff. Cool. > > [1] And, should we decide not to change /dev/random semantics, > > can we still back /dev/random with a modified Yarrow? > > I think it makes sense :) Me too, especially with your changes (or modification thereof) to preserve current /dev/random semantics. 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 Sat Jul 29 22:31:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29]) by hub.freebsd.org (Postfix) with ESMTP id DE6DE37B908 for ; Sat, 29 Jul 2000 22:31:30 -0700 (PDT) (envelope-from chris@holly.calldei.com) Received: from holly.calldei.com ([208.191.149.190]) by mta5.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FYH008EPWN3Y7@mta5.rcsntx.swbell.net> for freebsd-current@FreeBSD.ORG; Sun, 30 Jul 2000 00:30:40 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id AAA48271; Sun, 30 Jul 2000 00:28:44 -0500 (CDT envelope-from chris) Date: Sun, 30 Jul 2000 00:28:44 -0500 From: Chris Costello Subject: Re: sendmail 8.11.0 trouble In-reply-to: To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000730002843.Q37935@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. -- |Chris Costello |Computer and car salesmen differ in that the latter know |when they are lying. `-------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 29 23:38: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from castle.jp.freebsd.org (castle.jp.FreeBSD.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 5D9D937B9A1 for ; Sat, 29 Jul 2000 23:37:53 -0700 (PDT) (envelope-from matusita@jp.freebsd.org) Received: from localhost (localhost [127.0.0.1]) by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id PAA84944 for ; Sun, 30 Jul 2000 15:37:47 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <20000316134059M.matusita@jp.FreeBSD.org> References: <20000316134059M.matusita@jp.FreeBSD.org> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Molpe) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 23 From: Makoto MATSUSHITA To: current@freebsd.org Subject: FYI: Full 4.1-RELEASE distribution with RSA_RESIDENT=NO Date: Sun, 30 Jul 2000 15:37:44 +0900 Message-Id: <20000730153744E.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've sent before that current.jp.FreeBSD.org provides 4.0-RELEASE distribution with international CVS repository (at that time). Now we are in the post 4.1-RELEASE age. It should be changed. *** If you are NOT an US resident, and try to use FreeBSD 4.1-RELEASE which was built with 'RSA_RESIDENT=NO' (librsaINTL are already included in crypto distribution), try: This release is build at current.jp.FreeBSD.org, not a mirror of the one at ftp.internat.FreeBSD.org. If something goes wrong, please email to me. P.S.: current.jp.FreeBSD.org serves daily FreeBSD snapshots with RSA_RESIDENT=NO, which is *not* available at current.freebsd.org. If you have also interested, check /pub/FreeBSD/snapshots/i386 directory. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message