Matthew Dillon’s found a solution to the problem of hardlinks in HAMMER2, and so moved on to dirents. The design document has a significant update to match.
A running description of activity related to DragonFly BSD.
A running description of activity related to DragonFly BSD.
Matthew Dillon’s found a solution to the problem of hardlinks in HAMMER2, and so moved on to dirents. The design document has a significant update to match.
Wahoo!
Hammer2 news. Always exciting to read.
https://gitweb.dragonflybsd.org/dragonfly.git/blob_plain/HEAD:/sys/vfs/hammer2/DESIGN
Sad to see that only 7 Hammer2 features are operational. 3 under development. And 5 features haven’t been started.
At this pace, Hammer2 is only roughly 60% complete. Guess eta is another 4-5 years :(
4-5 years? UFS still gets updates from Kirk McKusick, and that’s been around for 33 years… so we have another 3 decades to go on HAMMER2 updates, at least.
Have you Hurd the latest HAMMER2 news? ;)
Hey, I bet Duke Nukem 3 runs great on… oh wait, I can’t use that joke any more.
Justin
The Duke Nukem series of games might be the perfect analogy unfornuately for Dragonfly.
Dragonfly, like Duke Nukem when first released was appauded for its innovation.
But it then spent 15 years to release Duke Nukem Forever (Hammer2), during which time all of its competitors caught up and surpassed it, then once Duke Nukem Forever was released (Hammer2) – it was received poorly.
Time kills products unfornuately. The world around you will catch up, swallow you up, and will keep moving on.
Good lord, it was just a video game joke. You don’t have to drive the analogy into the ground just for your own personal axe-grinding.
+ 1
To the comment that “time kills projects”.