|Tony Johnson||Sep 27, 2000 3:55 pm|
|Kris Kennaway||Sep 27, 2000 4:48 pm|
|Tony Johnson||Sep 27, 2000 5:06 pm|
|Kris Kennaway||Sep 27, 2000 5:17 pm|
|Alfred Perlstein||Sep 27, 2000 5:18 pm|
|Greg Lehey||Sep 27, 2000 5:34 pm|
|Tony Johnson||Sep 27, 2000 6:25 pm|
|Alfred Perlstein||Sep 27, 2000 6:39 pm|
|Thomas David Rivers||Sep 28, 2000 3:32 am|
|Tony Johnson||Sep 28, 2000 5:53 pm|
|Greg Lehey||Sep 28, 2000 6:50 pm|
|Tony Johnson||Sep 28, 2000 7:44 pm|
|Nickolay Dudorov||Sep 28, 2000 8:00 pm|
|Greg Lehey||Sep 28, 2000 8:04 pm|
|Jordan Hubbard||Sep 28, 2000 9:05 pm|
|Alfred Perlstein||Sep 29, 2000 12:18 am|
|Alfred Perlstein||Sep 29, 2000 12:30 am|
|Gerhard Sittig||Sep 29, 2000 10:11 am|
|Tony Johnson||Sep 30, 2000 4:46 pm|
|Bill Fumerola||Sep 30, 2000 5:01 pm|
|Matthew Thyer||Sep 30, 2000 6:53 pm|
|Siobhan Patricia Lynch||Oct 2, 2000 6:34 pm|
|Subject:||You should be running -STABLE (Was: Re: interesting problem)|
|From:||Matthew Thyer (thy...@camtech.net.au)|
|Date:||Sep 30, 2000 6:53:46 pm|
Tony Johnson wrote:
Since I am complaining then I need to figure out what U have done to make 5.0-CURRENT crash?? Well atleast U admit that U do not know and U do not care. So anyone who is using FreeBSD should also not care?? This is more screwed up then I thought and people @FreeBSD have made this much harder then necessary.
Learn the lesson now and save us all from reading your messages in the future.
First: If you run FreeBSD-CURRENT, you must take the time to read at least 2 mailing lists being freebsd-current and cvs-all. I'd recommend archiving them as well and definitely have your own source repo.
Second: Dont try to antagonise the list. Do you think that everyone is actually aiming to produce a broken by design system ?
Third: Investigate you own problem. If you can fix it you have provided a service to others who have the same hardware. You may have to spend time doing a search of your email to identify the likely commit that caused your problem... keep release CD's around for quick testing of boot floppies. Keep a source repo so you can checkout kernel floppies from around the exact change to the GENERIC kernel that broke your system. There should never be time deadlines on you doing this because YOU SHOULD NOT USE -CURRENT FOR A PRODUCTION SYSTEM. It really doesn't take long for new technologies like softupdates, ACPI, ATA-100 to get into the -STABLE stream and then into a release.
FreeBSD is a volunteer project with a development model that lets anyone 'listen in' on whats happening at the head of the development tree. If you are prepared to use the head of the tree, you do need to fix your own problems or at least provide the list with an exhaustive list of your configuration and the behaviour you see under everything you've tried (removing hardware, changing cards, flashing BIOS, hacking CODE! yes you can do this too!).
If you dont have time to do this, run -STABLE or the last release.
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message