Submitted by “We are excited to announce that Haiku developer Ingo Weinhold has recently committed UserlandFS to the repository. UserlandFS is designed to provide, for the first time in Haiku (and the BeOS platform), a stable and flexible environment for file system add-on development. Along with UserlandFS, Ingo has also committed several file system modules, including a Reiser FS 3.6 read-only implementation, a RAM FS (which is still work in progress), and NetFS, a Haiku-specific networking file system. NetFS is a native Haiku network file system that provides peer-to-peer networking capabilities for computers running Haiku on a LAN and includes full support for BFS attributes and live queries.”
But isn’t in ‘test’ directory?
Michael Vinícius de Oliveira
No matter how simpler it is to create network / shared directories accessable to other users these days compared to days long ago, it is still way to complex to setup and configure for the average user. Sometimes I still revert to good old ftp when trying to network MacOSX and WinXP, since the latency of establishing a connection is much smaller.
Good luck with Haiku NetFS. If Haiku becomes very popular, then NetFS will be used by millions of people to share content. I hope its easier to setup and configure than CIFS (or SMB), and as fast as good old FTP.
It’s also great to see Haiku continuing the BeOS tradition of having drivers split into 2 components – the lower lever component in kernel space, and a higher level component in user land (add-on). This really does simplify development, and it allows users to update modules without requiring reboots. Want to update your RaiserFS add-on? You can do it almost on the fly.
It’s also great to see Haiku continuing the BeOS tradition of having drivers split into 2 components – the lower lever component in kernel space, and a higher level component in user land (add-on). This really does simplify development, and it allows users to update modules without requiring reboots. Want to update your RaiserFS add-on? You can do it almost on the fly.
Just to clarify, in Haiku you can even replace kernel modules without doing a reboot. The only exception are modules that are currently in use, and this also applies to userland modules, of course. E.g.: you can’t replace your network driver while you’re at the same time downloading a file.
All this rules, really….
Cant Wait for a not-debug-compiled version of Haiku running natively on my dual core processor. drooling.
Not the only one Tanner. There are lots of us here waiting for the same thing.
Go Haiku.
I’d love it if I could even get just BeOS R5 PE (of any variation) to run on my MSI RX480 Neo2-F motherboard w/ Athlon64 X2 4800+ CPU.
Suspicion is that BeOS/Haiku/Zeta just don’t know what to do with the ATI Radeon 200P/SB400 chipset on that motherboard, tho. 🙁
I’d give my Athlon XP 2000+ system to the person(s) who could accomplish that. Free computer! Really!
The whole FS thing seems interesting, but that NetFS seems most curious… a Haiku-*specific* FS? Something only Haiku users can use amongst themselves? That’s really got my excite-o-meter pegged! A Haiku-specific networked community!
AUSA!!!
And, one other thing… I noticed with the latest Rev. of Haiku I built last night (Why no Revision number, anymore, and just “Walter” in the “About Haiku” box, now?), I noticed that moving the mouse now eats up a significant amount of system speed. GLTeapot, on my Athlon XP 2000+ system, spins around 90-109fps (or “tps”, if you’re into the whole “Teapots Per Second” lingo (grin)), but as soon as (and as long as) I move the mouse, it slows down to an abysmal 30-40fps!
WIBIGO?!? <— Translation: What In Blazes Is Going On
I sure hope this is only due to “debugging code” being implemented and not some “two steps forward and one step back” kinda thing going on! 🙂
I sure hope this is only due to “debugging code” being implemented and not some “two steps forward and one step back” kinda thing going on! 🙂
That’s still better than one step forward and two steps back. Right?
But seriously, you can’t expect everything to work perfectly while it’s still in active development. That’s just not how development works, especially for a project of this scope.
Edited 2007-02-21 08:06
It would be a good move to have FUSE API bindings with the UserlandFS. Lots of cool FUSE filesystems could then be used, too.
FUSE was my first thought also when I saw the commit… and was the very first thing mentioned in the IRC channel when the commit landed
However, UserlandFS is very much intended to encourage development/porting of native filesystem add-ons for Haiku – rather than providing another layer to already-existing filesystems modules.
For the record, I too would love to see a FUSE compatibility layer if that was possible without a huge effort.
Whether porting FUSE or porting filesystems to Haiku’s VFS is the right way or not, having UserlandFS could help porting FUSE, since it can be done on top of UserlandFS – with the easier debugging that enables – and then later on interface with the kernel directly, the UserlandFS and Haiku VFS interfaces being the same.
Great stuff! Go Haiku!
I agree that FUSE API bindings could be very useful too, given the number of FUSE filesystems around.
I thought it had been quiet for a month or so and voila! Zee Geeeermans have done it again =)
I also notice that Haiku has indeed increased speed in commits, where of Geist is one of these new committers. Geist is obviously a tremendous coder that will likely do a lot of good in there.
So the question remains to be asked and remains to be answered. 2008? The year of haiku?
You do realise that Geist is actually Travis Geiselbrecht (sp), the author of NewOS, which Haiku is based off. There is nothing more vindicating than having your pet project swooped by the Internet and to see it grow into something more amazing than anything he could have ever imagined.
Thank you Ingo. Really nice.
I just wondered how you set up permissions etc. Do you share a folder and every sub folder within that folder. Or how does it work? Can you setup several folders? Is it encrypted?
My appetite for Haiku is getting stronger =).
/Konrad
“NetFS is a native Haiku network file system that provides peer-to-peer networking capabilities for computers running Haiku on a LAN”
its an interesting idea , to have P2P as standard on the LAN, i wonder though is Multicasting also available as standard of NetFS?.
if so that opens up a great potential in the IF you were to also Include as default a tunneling option for
NetFS then you could also use the P2P for web connected machines on your other boxs down the road or indeed anywere.
more to the point it then becomes almost a snap to combine the old school P2P, throwing out the unicasting model the less innovative people are collecting around and replace that with multicasting over the tunnels.
in effect you would be the very first people to produce what iv wanted for a very long time, the new generation multicasting/P2P/DHT torrent style app framework that can in effect reduce overall bandwidth at a snip.
not only innovative, revolutionary….
imagine it, just setup your DHT to how many clients you want, ask them to get ready to receave your content and confirm, then simply send one single file once and they all get that file.
thats a massive saving and all possible over tunnels today if your defaults are set to allow it and the code is written to make it a reality…
is this a possible option and supporting code you might consider putting in the NetFS?.
I think this is more along the lines of home LAN disk connectivity and netbooting clients with PXE +network filesystem.
I’m pretty sure this is merely a network filesystem (and protocol), in the classic peer-to-peer sense, similar in concept to NFS. Haiku needs that a lot more than anonymous P2P filesharing, to be complete and usable. Sexy or not in a world of pervasive piracy, it will be great having a networked filesystem.
With the minimalistic goal of cloning BeOS R5, I doubt that we’ll see core Haiku developers, such as Ingo, focus on integrating P2P/multicast filesharing with the operating system.
im not sure were ‘anonymous’or ‘pervasive piracy’ came into this ?, perhaps its the DHT?, but as the free user space java DHT (Distributed Hash Table) app bamboo
http://bamboo-dht.org/index.html says:
”
A distributed hash table, or DHT, is a building block for peer-to-peer applications. At the most basic level, it allows a group of distributed hosts to collectively manage a mapping from keys to data values, without any fixed hierarchy, and with very little human assistance. This building block can then be used to ease the implementation of a diverse variety of peer-to-peer applications such as file sharing services, DNS replacements, web caches, etc.”
its also got a multicasting option so could be used as part of a proof-of-concept app, as could the again users space java app multicast Tunnel – mTunnel
http://www.cdt.luth.se/~peppar/progs/mTunnel/
the point is someone needs/could to make a comitment to write or patch existing code to combine multicasting tunnels, DHT, and P2P, and in doing so will show how it can save massive amounts of bandwidth and is a good thing, perhaps it will be the NetFS/Haiku guys, the Azureus guys (finally innovate rather than follow suit for somone else added an option) or even the Joost guys sometime (they have been asked too).
the point is, whoever does it in whatever form/format then it is they who will be bringing something new to the table and it will be revolutionary in scope as its saving masses of bandwidth and time.
good for many things from personal content sharing between your NAS and your DVB server for instance and many more.
Edited 2007-02-21 14:28
P2P was only used here in the same sense as with CIFS or NFS. Nothing to do with your copying orgy fantasies. That will have to wait until I write besharefs
Btw, Haiku already has NFS, so it’s not our first networked fs. However NFS (v2) doesn’t support attributes, let alone queries. (v4 supports attributes in some way, so could be interesting later.)
Same with FUSE, it models the Linux VFS which has no concept of queries; UserlandFS was written to test in-the-making native filesystems (I suppose he used it to test reiser), not implement Linux’ VFS.