4 ms·
Colin is too polite to point out that Dragonfly was an "I'm taking my ball and going home" moment in FreeBSD history. Matt Dillon, a long-time FreeBSD develope
by SwellJoe 19y ago
Colin is too polite to point out that Dragonfly was an "I'm taking my ball and going home" moment in FreeBSD history. Matt Dillon, a long-time FreeBSD developer (and all-around impressive guy, though this episode in history isn't his finest hour), had some disagreements with some other long-time FreeBSD developers, and one of those disagreements, perhaps the most important one, was over SMP and the direction FreeBSD was moving with regard to SMP-at-the-expense-of-UP performance.
So, the irony lies in the fact that current FreeBSD is faster than current Dragonfly in both UP and SMP environments. If one were keeping score, it would be:
FreeBSD core developers: 1
Matt and his "screw this, I'm leaving" crew: 0
To be fair, Matt has been willing to talk about some major issues in FreeBSD that are considered verboten by others. Package management in FreeBSD, for example, is a joke, and ports is waved around as a solution rather than the very serious problem that it really is. (No fault of cperciva's, as he's done the only really good thing in FreeBSD package management in years in the form of freebsd-update.)
Not that I have any strongly held opinions, or anything like that.
- cperciva 19y agoSMP-at-the-expense-of-UP This is an interesting topic, actually. When the process of improving FreeBSD SMP got underway seven years ago, the initial work did hurt UP performance by 10-20% -- enough that in FreeBSD 5.x and FreeBSD 6.x, there are two kernels shipped with the release: the GENERIC (single-processor) kernel and the SMP kernel. In FreeBSD 7.x, however, we're back to only shipping a single kernel -- one with SMP enabled -- because the performance penalty on UP systems for having SMP enabled is practically nil. FreeBSD SMP development started out needing a lot of faith to say "we know that we're making things slower every day, but it's going to pay off in the end" -- and while it turns out that the team which decided on a fine-grained sleeps-and-spins locking structure were correct, I can't fault Matt for not having as much faith. ports is waved around as a solution rather than the very serious problem that it really is The FreeBSD ports system works very well -- as long as you don't mind compiling everything from the source code. Binary packages... yeah, there are issues there.
- SwellJoe 19y ago"while it turns out that the team which decided on a fine-grained sleeps-and-spins locking structure were correct, I can't fault Matt for not having as much faith" I agree, and I'd find it very hard to have anything but the utmost respect for him. His C compiler for the Amiga, DICE, was where I began to learn about real software development and the UNIX tool chain, so he holds a place nearly comparable to K&R in my history as a hacker. It's just unfortunate that some personality conflicts have led to a great developer bitterly spinning his wheels for several years on something that is clearly going the wrong way. (Then again, I can't say that of OpenBSD, as it's spawned a lot of great stuff, though it may have looked like the same kind of situation a few years into the project. NetBSD, I'm a little iffy on....) "The FreeBSD ports system works very well" Ah, you have to say that, or you'll wake up with a horse head in your bed. It's the official party line. ;-) Actually, to be more clear about my intent, the ports system does work very well for the problem that it solves. The problem is that it's solving the wrong problem, and no one will admit it because it looks so pretty solving the problem that it does solve very well. Because ports exists, and works really well for its problem domain, it has prevented any real solutions from being put into place for package management and has also caused a lot of weird and incompatible tools to spring up to deal with various meta-problems like managing software on many machines (for example). Meanwhile, over in Linux-land, not just one, but two, really good package management systems (yum+rpm and apt-get+dpkg) have sprung up and made it possible for many people to produce nicely bundled software (and provide for the dependencies in an automated fashion) for Linux...while distributing software for FreeBSD is a choice of many poor options, mostly ending up with a tarball and a shell script. Anyway, I think freebsd-update is a great improvement, and the right direction. (I'm really not just blowing smoke...it makes me feel a lot better about our customers using FreeBSD. Now, if only you could do something about the silly secondary groups limit of 16, and fix the default username length, I'd have nothing left to complain about...well, except for the other package management issues.)
- cperciva 19y agoThe problem is that [the ports tree is] solving the wrong problem I'm not sure from what you've written what you consider to be the right problem -- can you clarify? Would you be happy if the FreeBSD ports tree had a magical "make installbinaries" command which would download and install binaries instead of building from the source code?