Linked by Eugenia Loli on Thu 23rd Jun 2005 18:11 UTC
Original OSNews Interviews One of my popular articles shortly after I joined OSNews in 2001 proved to be "the big *BSD interview" and so it is only appropriate to end my serving at OSNews with a similar theme. Today we are very happy to host a Q&A with well-known FreeBSD developers John Baldwin, Robert Watson and Scott Long. We discuss about FreeBSD 6 and its new features, the competition, TrustedBSD, Darwin etc.
Permalink for comment
To read all comments associated with this story, please click here.
My hard hitting questions
by slash on Thu 23rd Jun 2005 22:18 UTC

Sheeze, I saw a whole bunch of writing but noone answered my questions. Reminds me about the President and the War in Iraq. All I want to know is where exactly does SMP stand at the moment? It's not a difficult question. Go to www.freebsd.org/smp. Look at what's in progress:

Newbus In progress, VM In progress, Buffer cache In progress, VFS In progress, Processes and thread operations In progress, Scheduler In progress, TTY subsystem In progress, IPv4, IPv6 In progress, IPX/SPX In progress, netatalk In progress, Network stack infrastructure In progress, NFS Client Not Started, NFS Server In Progress.

That's a big list of "In progress." A lot of the stuff are extremely important for scalability too. The list barely gets updated so we have no idea when to expect something to be checkmarked. It would be nice to know.
I can't see how FreeBSD 6 will scale much better when NewBus, VM, Buffer Cache, VFS, Processes and Thread Operations, Scheduler, IPv4, IPv6 and the Network stack are all under Giant Lock. At the moment, it seems that the project is getting the worst of both worlds, all the negatives of being under giant-lock and being multithreaded.

About the installer, I don't really care when or if it gets replaced. I am used to it, and it works. But if there are no plans to replace it, they should not bring it up in so many discussions. They should just say there are no plans to replace it and leave it at that.