Hacker News new | past | comments | ask | show | jobs | submit login

How long do you expect to maintain BeOS binary compatibility? I see in the trac roadmap that R2 is slated to be the deprecation point; is that still likely to be multiple years away? Has there been talk of an abi compatibility layer that would allow the kernel to move forward independently from the legacy platform?

Sorry if these are repetitive questions btw. I'm just curious.

Exactly how long is unclear; however, post-R1, we intend to stop prioritizing it, and if it does stay around, it'll be secondary to continued development. There's been serious talk of actually branching R1beta1 on January 31, so, hopefully soon.

The kernel already has moved pretty far forward. BeOS audio drivers, for instance, don't really work anymore in favor of our new multi-audio API (I don't think anyone had any use for BeOS audio drivers; we merged all the open-source ones, I think), the VFS layer has gotten major upgrades, we rewrote the thread scheduler and removed the 8-core limit we inherited from BeOS, and already have added ASLR and DEP support, among lots of other improvements. I think the only thing at this point which actually is still compatible kernel-wise are FS drivers (sorta) and graphics drivers (although of these, we have more in-tree than BeOS ever did, so I don't know if anyone even uses old BeOS ones anymore).

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact