Date: Sun, 11 Jul 1999 20:13:37 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: Nicolas Blais <nicblais@videotron.ca> Cc: freebsd-current@FreeBSD.ORG Subject: Re: HELP!!! -CURRENT libtool problem. Message-ID: <37887C61.2F462FD@newsguy.com> References: <37810FDD.C1321FE7@videotron.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Nicolas Blais wrote: > > Hi. I've finally installed FreeBSD 4.0 and to tell you the truth, I'm > not > very impressed. I was expecting some bugs but not like that... Well, maybe this FAQ entry candidate will help clarify things for you: "Q: Why shouldn't I just go ahead and run -current? That's got all the latest stuff, right? A:4.0 is the next major release of FreeBSD. For now, and for a while, all -stable releases of FreeBSD will be in the 3.x line. These are minor releases, which do not introduce big changes and we try our best to avoid breaking compatibility backward compatibility (binary, file formats, etc). Meanwhile, our fearless developers are cooking the 4.0 version. This branch is known as 4.0-current, or just -current (since when 4.0 becomes stable, the current branch will become 5.0-current). Our developers are fearless because a -current system is something in development, and, thus, subject to all sort of bugs, which can wipe out your disks, burn your monitor, erase your BIOS, overheat your CPU(s), spit out your PCI cards, send the fans flying (sometimes throwing stuff at them first), make international phone calls to phone sex services, print pornography until your printer runs out of paper/toner (sorry, no such luck... it's just the Stark report), send insulting faxes to your boss, cheat on the mob and blame you for it, attract attention for the gentle I.R.S. personel, blow your house fuses, open the gas and then set your house on fire, make your girlfriend break up with you (or your wife cheat on you), and bomb Yugoslavia. This last one we are trying to debug, though [NOTE: at the time of this writing, we have reports that this bug has been fixed]. Because of the above, we advise against using -current. If you so insist, the following rules must be obeyed: 1) Read cvs-all. No, I'm not kidding. I mean it. 2) Read freebsd-current. Yeah, that one too. 3) If something fails, it's probably because you missed a message on cvs-all or freebsd-current. 4) If that's not the case, it's probably a temporary bug. Cvsup again after the appropriate time (minimum of one hour, though one full day is not unreasonable). 5) If it still crashes *at the same location*, then it's probably your fault. Junk your customized settings, and try to reproduce it with a vanilla system. 6) If you can reproduce it even with a vanilla system, then you might actually have stumbled on a bug. Congratulations! Find out what the bug is, and send us the patches. 7) If you are not capable of the above, you might just keep quiet and wait until someone fixes it. See steps 1 and 2 for how do you know someone fixed it. 8) OTOH, you might help tracking the bug. See the handbook on getting crash dumps, kernel traces, and such stuff. 9) If you loose all data on your hard disks because of a bug, that's one of the risks of running -current. Either you can deal with that, or you shouldn't be running -current. These rules, though written tongue-in-cheek, are for real. FreeBSD 4.0-current is *not* supposed to work all the time. It is being *developed*. And saying "Hey! I have a bug!" does *NOT* help developers. Furthermore, sometimes it breaks *on purpose*, while things are being changed, and the fixes are *not* immediate. If you can live with that, and think you have any compelling reason to run -current, read the handbook for further instructions. Sorry if this seems too harsh, but many people are just not used to the concept of a development tree available publicly, and think of it as the "latest version". It is *not* the latest version. When it is *ready*, it will be the latest version. Until then... read the above." Any other question? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org I'm one of those bad things that happen to good people. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37887C61.2F462FD>