Re: 4.3-BETA: make kernel -j N broken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 24 Mar 2001, Kris Kennaway wrote: ... : I believe I had the same problem, but with make -j4 buildkernel . So I : would hope make depend was run first. : : Oops, I wasn't awake when I wrote that. It is conceivable that make : buildkernel does the wrong thing here, though I've not checked. I haven't tried buildkernel with -j4, but I have successfully built world with -j4 as well as building kernel the normal way with -j4, though I do not run the make depend with -j4.. If that helps. * Matt Heckaman - mailto:[EMAIL PROTECTED] http://www.lucida.ca/pgp * * GPG fingerprint - 53CA 8320 C8F6 32ED 9DDF 036E 3171 C093 4AD3 1364 * -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (FreeBSD) Comment: http://www.lucida.ca/pgp iD8DBQE6vXgwMXHAk0rTE2QRAqTpAJ4rKJHJXsDrTQg8zMY/JdqIquhyHwCfTvP5 F1UYF/eVrbIEZvvnpx/BzpY= =D7Jp -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA crash on 'mount /dev/acd0c /mnt'
On Thu, 22 Mar 2001, David Taylor wrote: (using: 4.3-BETA FreeBSD 4.3-BETA #3: Tue Mar 6 18:39:44 GMT 2001) mount -t cd9660 /dev/acd0c /mnt #works ok OTOH, mount /dev/acd0c /mnt causes the following panic: I've also experienced problems mounting CD-ROM discs, to the extent that if the bus is busy on one disc, the system will not error out and return a "device busy" message or something else more appropriate. Instead the command and it's controlling console/terminal/shell/whatever hangs until the other device is finished. I have yet to panic the kernel doing this, though. panicstr: vm_fault: fault on nofault entry, addr: c7c11000 (not to downplay this...but isn't that like masking an NMI? :-) -- /~~~___~\ | [EMAIL PROTECTED] //Z@|___ | | http://home.kscable.com/natedac |'(__ [_ | \_C64/C128_-_What's_*YOUR*_hobby?__\___|/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA crash on 'mount /dev/acd0c /mnt'
Nate Dannenberg wrote: On Thu, 22 Mar 2001, David Taylor wrote: (using: 4.3-BETA FreeBSD 4.3-BETA #3: Tue Mar 6 18:39:44 GMT 2001) mount -t cd9660 /dev/acd0c /mnt #works ok OTOH, mount /dev/acd0c /mnt causes the following panic: I've also experienced problems mounting CD-ROM discs, to the extent that if the bus is busy on one disc, the system will not error out and return a "device busy" message or something else more appropriate. Instead the command and it's controlling console/terminal/shell/whatever hangs until the other device is finished. I have yet to panic the kernel doing this, though. I just tried it and it didn't work. The mount complained about incorrect super block. I had /dev/acd0c defined in my fstab as mounting /cdrom. I tried mount /cdrom and it worked. Kent panicstr: vm_fault: fault on nofault entry, addr: c7c11000 (not to downplay this...but isn't that like masking an NMI? :-) -- /~~~___~\ | [EMAIL PROTECTED] //Z@|___ | | http://home.kscable.com/natedac |'(__ [_ | \_C64/C128_-_What's_*YOUR*_hobby?__\___|/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA
On Mon, 19 Mar 2001 20:53:50 -0800 Kent Stewart [EMAIL PROTECTED] wrote: KS - -RELEASE branch doesn't change. To my mind this is all backwards. KS Not in my mind. The -release branch always has something wrong with it But -release is *not* a branch, it is a point. It cannot change, it exists on vast numbers of CDs, the release is what got burned on all those CDs. -- Life is complex - it has real and imaginary parts. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA
FreeBSD-stable doesn't have releases as such, does it? That is, if you cvsup you get the stable track as it exists that minute. It's *called* "stable" most of the time; as a release gets close, it is renamed BETA and then RC (release candidate), until the day it's truly officially blessed and it is named RELEASE and that version number is frozen. The next day (probably the same minute, actually), the label gets switched back to STABLE and the version number is incremented by one. Regardless of the label, though, it's exactly the same animal. Thus, after 4.2-RELEASE, we got 4.3-STABLE, which is now 4.3-BETA and will become 4.3-RC, and finally the same code base will be frozen into 4.3-RELEASE, at which time 4.4-STABLE will come into existance. "[EMAIL PROTECTED]" wrote: When is the next FreeBSD-stable release Regards, JB --- Mensaje Original -- De: Haikal Saadh [[EMAIL PROTECTED]] Para: Mike Meyer [[EMAIL PROTECTED]], Francisco Reyes [[EMAIL PROTECTED]] Cc: Mike Meyer [[EMAIL PROTECTED]], Haikal Saadh [[EMAIL PROTECTED]], [EMAIL PROTECTED] [[EMAIL PROTECTED]] Asunto: Re: 4.3-BETA Fecha: 18/03/2001 23:23:56 Mensaje: --- Mike Meyer [EMAIL PROTECTED] wrote: Francisco Reyes [EMAIL PROTECTED] types: On Fri, 16 Mar 2001, Mike Meyer wrote: Haikal Saadh [EMAIL PROTECTED] types: --- Matthew Emmerton [EMAIL PROTECTED] wrote: What is a BETA system? Is it similiar to CURRENT? Please search through the mailing list archives before asking questions. This has been answered many times over the last two weeks. Or maybe just read the FAQ URL: http://www.freebsd.org/FAQ/admin.html#dmin.html#RELEASE-CANDIDATE , which makes it clear that the name changes just identify what point of the release cycle that particular snapshot of -STABLE is at. I have seen several people tell Haikal to read the FAQ, etc I really have to agree with him. I don't think having a "Beta" label on what is defined in the handbook as "Stable" is a good idea. By definition a "new user" to FreeBSD is someone who doesn't know yet what are the right places to read/check. In that case, where did they find the information needed to upgrade to -STABLE? I think responses like the ones he got are the reason we consistantly over the years get views of sometimes been unfrienly to new users. We're definitely friendlier to people who show evidence of having done some research themselves than to those who don't show that evidence. Personally, I always provide a pointer to existing documentation rather than type it in myself. That saves me typing, and the users should learn about another valuable resource that works faster than the mail lists. Haikal wasn't asking for help, he was suggesting inappropriate changes to the system to try and help people who had gotten past the newbie stage - as demonstrated by managing to update to -STABLE, getting both userland and kernel - past a problem. Perhaps a label of "Pre-Release" may be less confusing. "Beta" sure gives the wrong impression. That suggestion isn't inappropriate. On the other hand the label "-RC" (release candidate) stil generates problems, so I'm not sure it would work. I suspect that *any* change in name will generate "I tried to get -STABLE, and got -FOO" messages. Not changing it would make life difficult for users who *wanted* to know they were getting a BETA or RC version. Possibly this information needs to go in the handbook on tracking -STABLE, rather than a FAQ. Or a Comment in the example supfile saying "This Can Get A Beta Release If A Code Freeze Is In Effect" kinda thing? I read the handbook chapter on CVSUpping, as well as the bit in The Complete FreeBSD, but it really was an information overload, and I just ended up having a go with the given example supfile. __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- "Brian, the man from babble-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA
On Mon, Mar 19, 2001 at 08:33:03PM -0500, The Babbler wrote: Thus, after 4.2-RELEASE, we got 4.3-STABLE, which is now 4.3-BETA and will become 4.3-RC, and finally the same code base will be frozen into 4.3-RELEASE, at which time 4.4-STABLE will come into existance. Almost. 4.2-RELEASE started 4.2-STABLE, just as 4.3-RELEASE will start 4.3-STABLE. Note that cvs-wise, only 4-STABLE exists. We just call everything after 4.3-RELEASE in 4-STABLE, 4.3-STABLE. Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me 'Het leven is een stuiterbal, maar de mijne plakt aan t plafond!' - me To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA
--- Matthew Emmerton [EMAIL PROTECTED] wrote: What is a BETA system? Is it similiar to CURRENT? Please search through the mailing list archives before asking questions. This has been answered many times over the last two weeks. 4.2-STABLE became 4.3-BETA when the code was frozen, prior to becoming 4.3-RELEASE. Oooh...as a newbie, I've been bitten twice by this...CVSUPing hoping the get the latest STABLE, but get a BETA (4.1.1, and now 4.3)... I always thought I had made an error in my supfiles, and since nothing major seemed to have broke, just ignored it. Perhaps it would be a good idea to make it so that either: - UPDATING mentions that it's a beta you have, OR - not put BETAs into the STABLE branch? Just a newbie's opinion. __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA available for FTP
It already appears as if dummynet has been broken in 4.3 and is causing panics. At least 3 reports I have seen so far of people who have had to disable DUMMYNET. can you point me to these reports ? I'd love to have a look at them and see what is wrong (especially because after the last batch of fixes in february i haven't heard of brokennes). cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA available for FTP
It already appears as if dummynet has been broken in 4.3 and is causing panics. At least 3 reports I have seen so far of people who have had to disable DUMMYNET. can you point me to these reports ? I'd love to have a look i actually found one in the freebsd-stable mailing list archive... what i would need is to know what ipfw configuration did cause the problem -- apparently the problem is some null pointer dereference, so if i can reproduce it, it should be reasonably easy to track it. thanks luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA available for FTP
It already appears as if dummynet has been broken in 4.3 and is causing panics. At least 3 reports I have seen so far of people who have had to disable DUMMYNET. can you point me to these reports ? I'd love to have a look at them and see what is wrong (especially because after the last batch of fixes in february i haven't heard of brokennes). I'll bounce the copies I have here directly to you. Along with some data from one user that shows this to be in ip_output. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
