BeServed is a native network file system for BeOS. It allows you to share files between computers running BeOS. You can connect to (i.e., mount) folders from remote computers and access files just as if those files were local to your computer. Unlike NFS and CIFS, BeServed supports all the unique benefits of the Be File System (BFS), such as attributes, MIME-based typing, indexes, querying etc. (BFS features are only available on the BeOS platform; foreign versions of the file server do no yet support attributes, indexing, etc.) BeServed includes a network browsing application called ‘My Network’, which lists the available computers on your network in much the same way as Microsoft’s Network Neighborhood. The company now ported their product to Solaris, following releases of Linux & Windows.From their press release:
“Teldar Corporation introduced a Solaris (Intel) server port of its popular BeServed network file system for BeOS
clients. “Our principal goal has been to facilitate the sharing of files between systems running BeOS,” said Kevin Musick, President and CEO of Teldar. “However, equally important is the ability to leverage other environments in a
heterogenous network that are commonly used as department or enterprise file servers, such as Windows NT or 2000, Linux, and Solaris.” Teldar had already released Linux and Windows versions of its file server earlier this month.
Now the company is turning its attention to security, through its coming BeSure authentication server. This product runs exclusively on BeOS systems, and is intended to validate login attempts to BeServed servers running on any supported platform. It is small, and fast. To provide security, without encroaching on any United States government export restrictions on cryptology, BeSure employs a simplified but strengthened adaptation of the Needham-Schroeder public-key protocol and uses message digest (MD5) encryption for passwords.
Teldar has announced plans to have FreeBSD and HP-UX versions of its file server, and has also received numerous requests for a BeOS PowerPC port. The company is also interested in supporting Mac OS X. Some of this work may be
subcontracted to other developers under a nondisclosure agreement.”
but a company that supports BeOS better darn well allow ordering from within BeOS. Unfortunately at this time you cannot order BeServed with Net+. Get that working properly and we’ll talk
Now has PSM (now supports https!)
It rocks
Years ago a Driversoft was coding a NetWare client for the BeOS (go to http://www.driversoft.com and look at the bottom of the main page – they talk about the BeOS client there). This is a necessity for heterogenous networks IMO, but I have not heard of any plans from Teldar to port their BeServed to NetWare. Perhaps Teldar would be interested in continuing the NetWare client that Driversoft started or perhaps incorporating it into BeServed. Any comments?
Keep up the great work folks!
ciao
yc
Does Beserved allow the Windoze user to access the Bebox? I currently use cifsmount (through Besquired front-end) to access my windoze machine, but how do I access the Bebox from the windoze machine?
Let me answer some of the items posted above.
1. The issue in ordering from Net+ is the lack of SSL support. I am told that newer BeZilla browsers and the updated Net+ in Dano have SLL capabilities. Since we prefer not to accept confidential payment information via an unsecure connection, we could offer a CD-ROM with COD-based shipping. I’d be interested in anyone’s opinion.
2. Netware is a different animal than the traditional Unix, and a port would be much more effort. Additionally, most BeOS machines are currently used in home networks, where the likelihood of another computer running Windows or Linux is virtually guaranteed. I don’t think there are enough corporate environments running BeOS, nor enough home environments running NetWare, to make that project financially feasible. I would be interested in hearing more details about the BeOS NetWare client, and I did receive your private email on the subject.
3. Currently, the only file system client available is the BeOS client. Since BeOS has its proprietary file system add-on mechnanism, porting the client to Windows or Linux would be a complete rewrite except for the RPC layer. We’ll guage the interest and success of BeServer on the existing platforms before we commit to that significant of an undertaking.
Thanks everyone for your interest!