Big update while moving over completely to the Haiku kernel:* Ported over BFS to the new cache API
* Inode no longer inherits from CachedBlock, and therefore, no longer keeps the whole inode block in memory. It now has a copy of the bfs_inode structure in memory instead. This has a number of advantages but also some disadvantages, so it might be reverted later, even if it’s unlikely.
* Added a NodeGetter class that can be used whenever the real block needs to be accessed (ie. for attributes)
* Changed *transaction to &transaction where possible
* Removed support for KEEP_WRONG_DIRENT_RECLEN
* Removed support for uncached file access since that’s no longer needed
* Fixed some endian issues in bfs_write_stat()
* Removed the install BFS rules, since they don’t make any sense anymore (unless you are running Haiku ;-)) Note, logged streams are not supported anymore right now. Also, the transaction code is pretty simple and slow – it will be improved later on. Attribute code is pretty much untested in the new environment.
Haiku Kernel Update News
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Someone want to translate what this means?
It’s straight from the CVS log of Axel and it means that BFS is ported to the new Haiku kernel.
There was an earlier commit of Axel checking in a BFS version that is still compatible for R5.
While I think that its good to keep web sites up to date – this story is aweful. Its barely english. I am interested in Haiku and BeOS, but this story just left me confused.
Eugenia – if you are going to post a story, please put some effort into it rather than just copying and pasting a CVS log. The story is a worthwile post, but without any commentary it doesn’t mean much to the majority.
the article did make me feel really dumb 🙁
I hope this means we are closer getting installable alpha builds out there for people to break.
actually the changelog is understandable english so i don’t understand your belly aching, also why not just copy the changelog? if eugeina had re-written it into a proper article who’s not to say she wouldn’t have mis-quoted some facts, or phrased things that implied one thing when the changelog meant another thing.
Eugenia really dislikes the BeOS movement these days. This lack of effort highlights the afforementioned feeling.
Reporting? Why don’t you clowns go out and get a story. It’s not Eugenia’s responsibility to decipher a CVS log for you or have some running commentary for your benefit. Check the mailing-lists if you’re so interested. I’m sure once there is a real release then it’ll be big news here.
Eugenia you could at least put some effort into the articles about Haiku rather than copy and paste.
was informative enough for me, i understood what it said, and it gave me an update on a project i’m marginally interested in, but not so much as to check the website, check cvs logs or code for…
anyhoo, it’s saturday night (in some places :|) give her a break…
Those changes, though, seem more of an evolutionary nature, small improvements related to the integration of the new Haiku kernel with BFS. However, I would think that it is a higher priority to have BFS working with Haiku without too many changes, and focusing on the things that are not even implemented yet.
For example:
* Inode no longer inherits from CachedBlock, and therefore, no longer keeps the whole inode block in memory. It now has a copy of the bfs_inode structure in memory instead. This has a number of advantages but also some disadvantages, so it might be reverted later, even if it’s unlikely.
Basically, this was not a very important change, and it might even be reversed?! I’d have guessed that more pressing issues exist in the OpenBeOS/Haiku development.
You’re doing an excellent job sucking up to Eugenia, but the fact is that this is a terrible story.
If we wanted to see the raw CVS changelog (which I’m more than capable of reading and understanding, thanks) we’d go there. If she wanted us to be able to check her accuracy nothing prevents her from linking the changelog. This is just lazy reporting.
Anyone take the time to notice that it was submited by someone else? Now maybe she souldnt of just posted it the way she got it, but we dont all go crawl the OpenBeOS/Haiku development related pages. bit raw, but still news.
All i saw was “Feature *** removed, removed support for ****, ***** is no longer supported, **** is now no longer available”
=)
No but seriously, those interested in the Haiku kernel development probably preferred reading it like that. Especially when the project seem to be in the starting phase where information like that probably is the most sexy info you’re going to get. In a couple of years there might be more John Doe-interesting stuff 🙂
Re: “Eugenia really dislikes the BeOS movement these days.”
All this Eugenia-bashing has got to stop. I feel ashamed as a BeOS user. Every single time there’s a BeOS related news article, some conspiracy theory lowlife gets peeved by some aspect of whatever. Please stop. It’s embarrassing.
I agree. It’s very childish. And annoying
Theres no reason to do it people.
“Big update while moving over completely to the Haiku kernel:”
???
Only by reading the comments did I finally understand this meant:
“Big updates while moving OpenBFS completely to the Haiku Kernel”. ahhhh makes more sense now.
CVS logs like these are certainly not useful as news items, and I’ve no idea what could have caused this.
Anyway, the translation would be something like this: BFS now natively uses the new caching API of the Haiku kernel which, among other things, enables full write capabilities.
> Basically, this was not a very important change, and it
> might even be reversed?! I’d have guessed that more
> pressing issues exist in the OpenBeOS/Haiku development.
Oh, great! Comments like these could even make me lose my patience.
Don’t be bothered by idiots Axel, I for one am longing badly for Haiku to work and follow the progress on a daily basis (and have done for years now).
Keep up the good work you’re doing and I hope that some day soon (within the upcoming year) we’ll see a complete boot into OT and see development actually take place on the Haiku platform. Then I’m confident you’ll get loads of help =)
in the meanwhile, be cool =)