News for hackers. Stuff that matters.
Re:The BeOS file system, an OS geek retrospective by pbreit on Friday July 06, 2018 @01:47AM (#17469186)
Why would BeOS not be open source at this point?
Re:The BeOS file system, an OS geek retrospective by memsom on Friday July 06, 2018 @07:55AM (#17470648)
The source code, with all the stuff removed that was licensed or probably violated some patent or GPL restrictions would be pretty useless.

It also suffers greatly from the lack of engineers working on it - as in some parts have a lot of comments, some nothing what so ever. Some parts look very well done, some parts less so.

Back in the day, I saw the code (those leaks were real) and one zip was able to fully compile (and this is where the PowerPC version of post R5.03 came from, I used to have it compiling on my old BeBox - long gone now) and the other was a much later version, but the zip was corrupt and half the files were garbled.

DISCLAIMER: No I don't have the code anymore, not that I would never share it if I did, and no, I have never worked for or contributed to the Haiku Project.

Re:The BeOS file system, an OS geek retrospective by codezero on Friday July 06, 2018 @01:59AM (#17469254)
Bought by Palm, then HP, then ??? I guess, try to navigate that corporate IP nightmare.
Re:The BeOS file system, an OS geek retrospective by fredoralive on Friday July 06, 2018 @06:43AM (#17470334)
I think BeOS went Palm -> PalmSource -> Access (the embedded web browser people).
Re:The BeOS file system, an OS geek retrospective by codezero on Saturday July 07, 2018 @01:27AM (#17477193)
I assume you are right and I was hasty :)
Re:The BeOS file system, an OS geek retrospective by johannes1234321 on Friday July 06, 2018 @06:57AM (#17470400)
Because the incentives for going through with that are low.

Most likely it contains some parts of third-party code under non-ooen license (i.e. in device drivers, but not only) and maybe some subsystems were licensed in some form of exclusive form to others. Also they might want to double check that code not by "accident" looks like somebody else (i.e. the ext2 code might be inspired by Linux's) This all leads to review of old contracts and code while serving no business (besides marketing to a niche of nerds)

Re:The BeOS file system, an OS geek retrospective by jccalhoun on Friday July 06, 2018 @08:56AM (#17470987)
Basically this.

Access owns it. Even though they aren't doing anything with it, if they just released the code they would probably open themselves up to lawsuits over possible 3rd party code. So they would have to pay someone to go over the code to take out 3rd party stuff. That would take money for which there is no tangible benefit to them so they won't do it.

Re:The BeOS file system, an OS geek retrospective by Tomte on Friday July 06, 2018 @01:49AM (#17469196)
Is there a real difference to Haiku?
Re:The BeOS file system, an OS geek retrospective by pbreit on Friday July 06, 2018 @01:54AM (#17469218)
My understanding is that there is not much BeOS in Haiku.

"The only BeOS code that has made it into Haiku are Tracker and the Deskbar (the file manager and the equivalent of the start menu/taskbar, respectively)."

Re:The BeOS file system, an OS geek retrospective by axaxs on Friday July 06, 2018 @02:00AM (#17469261)
Understood...but then what is Haiku. I stil remember when r5 was released...an unheard of OS. As a tech geek I installed it and was blown away. Especially the media capabilities...two streams playing at once. That OS was way ahead of its time, and a shameful demise. I was excited about Haiku until I saw how far behind it was. And I mean absolutely 0 disrespect to its authors... but today it seems like an attempt to keep stable an already decades old OS that lost its way.
Re:The BeOS file system, an OS geek retrospective by snvzz on Friday July 06, 2018 @09:00AM (#17471012)
>seems like an attempt to keep stable

No. They rewrote the whole thing (minus the deskbar/launcher). If it looks to you that they're just keeping the old system stable, that'd mean haiku has been very successful in recreating it as open source.

They're close to 1.0beta1, which is defined as feature-complete for 1.0. It's after they do get 1.0 that they plan on really taking the system's design forward.

Not that it doesn't already have a few fundamental improvements, such as the integrated kernel debugger, the support for newer architectures or the package manager.

Re:The BeOS file system, an OS geek retrospective by alain94040 on Friday July 06, 2018 @02:19AM (#17469347)
What would blow you away today? I’m always curious to know what to build next.
Re:The BeOS file system, an OS geek retrospective by axaxs on Friday July 06, 2018 @10:52AM (#17471869)
A truly convergent desktop. And I don't even know the details to explain what I would like, I probably wouldn't even know until I used it. I do know Android for Desktop is not it, though. Being able to throw apps from my phone to my pc to my tv would be nice too, and not so clunky as casting.
Re:The BeOS file system, an OS geek retrospective by zmix on Saturday July 07, 2018 @06:30PM (#17481016)
I would continue, where the ideals of the 60s/70/80s/90s left off. Since IT gets dominated (sponsored) by service companies, book and grocery stores, things are a bit fucked up, to say at least ;-)
Re:The BeOS file system, an OS geek retrospective by zmix on Friday July 06, 2018 @03:41AM (#17469689)
I want a new Desktop. Let's talk ;-)
Re:The BeOS file system, an OS geek retrospective by AnIdiotOnTheNet on Friday July 06, 2018 @07:56AM (#17470660)
Same here, but not Linux Desktop Distro #301, which is pretty much all anyone wants to make.
Re:The BeOS file system, an OS geek retrospective by Fnoord on Friday July 06, 2018 @08:22AM (#17470789)
i3 should be good enough for anyone.