Jordan Hubbard Resigns from FreeBSD Core

SteelX was one of many readers to cite this story in the Daily Daemon News which reports that "Jordan Hubbard is resigning from the FreeBSD core. Jordan is a founding member of the FreeBSD project." Note: According to this email, Hubbard is definitely not quitting FreeBSD; he's just changing the nature of his involvement with it.

Link to Hubbard Hired by Apple...

[dasspunk]

here's a link [slashdot.org] to the /. story about Hubbard joining Apple . (not much of a read though...)

Re:Hexley vs. Beastie?

[pythas]

Hexley is the Darwin mascot

Beastie is the FreeBSD mascot

Re:A question for freebsd people

[Arandir]

I'm not really sure I understand your question.

Gnome is not a Linux program. Mozilla is not a Linux program. Gimp is not a Linux program. They all run just fine under FreeBSD.

GCC, bash, XFree86, tar, Perl, Windowmaker, etc, etc, etc, aren't Linux programs either. They're all Open Source Unix programs that work just fine under just about every Unix OS there is.

Re:BSD + Apple + M$

[good soldier svejk]

1) MS was not that major a stockholder, about $100 million in non-voting, non-transferable, dividend bearing preferred stock in a company with a market cap of $7billion. 2) MS sold the stock at a huge profit not long after it became convertible to common stock at 4:1. 3) You can't steal control of BSD code. 4) PARC did not create most of the ideas you claim Apple stole from them. However, Apple did unsuccessfully try to make them proprietary.

Re:Haiku for *BSD

[IronChef]

In a true haiku there is always a reference to a season [neh.gov].

Please re-submit your haiku for moderation.

Re:A question for freebsd people

[schweikh]

Being a FreeBSD committer, I might qualify as one of the "freebsd people" your question is addressed to.

First, I can see no lack of enthusiasm, not from jkh, let alone the BSD commiters, developers or user base. The steadily growing mailing list subscriptions are only one of many indicators. If you had read jkh's letter you would not have missed that he is not stopping work on FreeBSD, on the contrary, without the managerial work as a core member he can actually contribute *more* code and knowing jkh I am sure he'll raise his voice on many issues concerning the BSDs in the future.

The rest of your article seems to miss the current state of affairs so much that Richard P Feynman would probably attribute it with the same line he used for crank theories -- "not even wrong". To be more specific:

"poor quality of development tools" -- you mean make(1), gcc(1), cvs(1) or what? Care to elaborate when they are actually the same tools any linux (or for that matter unix) hacker uses? Typing

$ cd /usr/src; cvs update; make world

for the first time and watching the complete system being built was one of the most beautiful experiences in my hacker life.

"Very little projects from the FreeBSD community": You apparently have a different understanding of what constitutes a Linux or FreeBSD project than I have. Linux being kernel-only, lets address kernel projects going on in FreeBSD:

• fine grained SMP locking
• fine-grained privileges (capabilities)
• Access Control Lists
• KAME Project, a free IPv6/IPsec stack for BSD
• Mandatory Access Control
• Soft Updates: Asynchronous Meta-data Protection in File Systems

And there's tons more for the userland, e.g. the POSIX 2001 = IEEE Std 1003.1-2001 comformance project (which I regard my baby to some extent). Have a look at http://www.de.freebsd.org/projects/index.html for an exhaustive list of projects.

"controlled development model"? In FreeBSD more than 300 committers have write access to the repository. How does that compare to Linus, the benevolent dictator over the linux kernel? Funny that arch linux hacker Alan Cox is also actively working on the FreeBSD kernel. He seems to have no fear of working for both camps, heck, he might even be working on the Hurd and other OSes. The FreeBSD people couldn't care less. We value everybody's technical expertise and that is exactly what makes our community a place to be. Come to think of it: instead of uttering FUD why not learn from each other about strengths and weaknesses? Why the NIH attitude?

I give you a half point on the "no companies involved" issue. To be frank, the Windriver episode was not something to be proud of. I have no real insights into what went on inside WRS, but if I had to guess, I'd attribute it to lack of real enthusiasm. Other companies in the meantime have taken the role Walnut Creek had in the past, notably http://www.freebsdservices.com/ and http://www.freebsdmall.com/ They seem to do so well that I got the FreeBSD 4.5 DVD for free (like all 300+ committers).

With all this combined enthusiasm I have absolutely no doubt that FreeBSD will continue to have a great future.

Regards,
Jens, who is proud being a part of it.

Re:BSD emulates Linux

[AntiBasic]

It doesn't EMULATE anything:
1) Most "Linux software" isn't "Linux software" but "Unix software" and compiles and runs on FreeBSD just fine.
2) FreeBSD has Linux BINARY support, so if the source isn't available (StarOffice, VMWare, etc) you can still run your choice of programs. It doesn't do this via "emulation" but by translating Linux syscalls into FreeBSD syscalls where everything is executed natively.
3) It would be _more_ accurate to say that FreeBSD emulates Linux as opposed to "emulating Linux software", but it's still wrong (See #2.)