DragonFly At DragonFly 1.0-CURRENT 108
CoolVibe writes "For months, the DragonflyBSD fork of FreeBSD was maintaining compatibility with the existing FreeBSD-STABLE branch by using the 'FreeBSD 4.8-STABLE' name internally. In a few commits, Matt Dillon changed all the names, and DragonFly is finally sailing under its own banner. Things that DragonFlyBSD already has that FreeBSD-STABLE doesn't are, among others, application checkpointing, variant symlinks (not unlike Domain OS), Light-weight kernel threads, a more efficient slab-allocator, a multithreaded network stack, and the rcNG system."
I wonder (Score:2, Interesting)
One has to wonder if DFBSD will die due to lack of following, or if it will be the next awesome BSD. I am currently running FreeBSD 4.8 Release on my workstation. It might be worth it to grab a spare machine and install it to see what's up. Only if the distributed.net client [distributed.net] will work on it though. ]:3}>
Variant symlinks are really cool (Score:5, Interesting)
I thought about implementing variant symlinks on Linux. Probably it would need a new system call to tell the kernel where the process keeps its environment variables, to be run at each program startup, and a new process table entry field.
Re:Variant symlinks are really cool (Score:1, Interesting)
ln -s '/etc-$(HOSTNAME)'
That's neat
Re:I wonder (Score:5, Interesting)
Ports are great, but damn does my p2 400 dislike hours and hours of compiling.
MIDI support? (Score:3, Interesting)
The first BSD to have that will become my favourite. So far FreeBSD is in the lead
Re:What We Can Learn From BSD (Score:1, Interesting)
Witness Redhat keeping its CVS out of public access. At least the BSD's allow one to track changes to their kernels and back out mistakes made by the developers.
Linux (as delivered by Redhat) is effectively a closed source operating system between releases.
Re:Server Names (Score:3, Interesting)