Date: Sun, 17 Nov 2002 20:16:24 -0400 (AST) From: "Marc G. Fournier" <scrappy@hub.org> To: freebsd-stable@freebsd.org Subject: Re: -STABLE was stable for long time (Re: FreeBSD: Server or Desktop OS?) Message-ID: <20021117201025.P23359-100000@hub.org> In-Reply-To: <20021118000255.BEF6B286A5@mail.tmseck.homedns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 Nov 2002, Thomas Seck wrote: > * Marc G. Fournier (scrappy@hub.org): > > > On Sun, 17 Nov 2002, Thomas Seck wrote: > > > >> You have chosen to maintain systems which stretch FreeBSD to its limits > >> and uncover bugs lurking in the code. This is great. But you cannot do > >> so on the one hand and refuse to face the administrative work on the > >> other hand. This does not work. You have the freedom to maintain your > >> own release with all the patches and fixes you need. Why don't you do > >> it? Instead you waste your time with complaining (and you waste my time > >> because I have to read it and think about the replies I am going to > >> send)? > > > > But, what you miss in here is that picking and choosing which patches to > > use is useless, as it doesn't take into consideration the interactions of > > other patches you don't apply ... or the reliance of future patches that > > would be useful on those patches you don't apply ... if I wanted to > > pick-n-choose patches, I'd run Linux ... I choose to run FreeBSD because > > its an Operating System, not a Kernel with a 101 different distributions > > Basically, you want others to do the developing, testing and patching > and keep the complaining part for yourself. No, that is the opposite of my point ... my point is that I *want*, and am willing, to do the testing required, as well as do what I can to debug the crashes ... I spent several hours last weekend narrowing down a problem with -STABLE where it hangs on my server, to the point that a kernel from 2002.10.28 boots, but 2002.10.29 doesn't ... that involved at least a half dozen CVSup's, builds and reboots of the server ... I'm definitely not afraid to do the testing and work on the debugging ... but I don't have sufficient knowledge to *fix* the crash ... What I'm complaining about is that those that are MFCng to -STABLE seem to be leaving it as "it works on my hardware, so it must work" and drop'ng responsibility for their changes ... so what happens when its time to do a RELEASE? There have been soooooo many changes, how do you know which one caused the problem? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021117201025.P23359-100000>