Slashdot Mirror

For those who can't get to free.be.com, here is the mirror site list they have posted:

Americas:
http://www.zdnet.com/ - Ziff-Davis, North America
http://download.cnet.com/ - CNET/Download.com, California
ftp://.beoscentral.com/pub/ - BeOS CentralJohnson City, TN
http://freebe.nerdygirls.com/ - Oak Ridge, TN
ftp://www.beforever.com/pub/beforever /freebe/ - BeForever, Omaha, NE
ftp://mirrors.rochester.rr.com/pub/be/ - RoadRunner.Com, Rochester, NY
ftp://ftp.be.com/pub/beos/ - Be, Inc. San Jose, CA

Europe/Australia:
ftp://mirror.aarnet.edu.au/pub/beos/ - AARNet, Brisbane, Australia
ftp://ftp.beeurope.com/pub/ - BeEurope, Paris, France
ftp://ftp.worldonline.fr/ - World Online, Paris, France
ftp://ftp.gigabell.net/pub/beos/ - Gigabell.Net, Frankfurt, Germany
ftp://ftp.ph-freiburg.de/pub/m irrors/ftp.be.com/beos - P.H. Freiburg, Freiburg, Germany
http://www.computerchannel.de/download /beos/ - ComputerChannel, Hamburg, Germany
ftp://ftp.xtdnet.com/pub/ - XTDNet, Karlsruhe, Germany
ftp://ftp.zdf.de/pub/ - Neues-3Sat Online, Mainz, Germany
http://pcteor1.mi.infn.it/beos/ - Univ. of Milan, Milan, Italy
ftp://dl.xs4all.nl/pub/ - XS4All, Amsterdam, Netherlands
ftp://ftp.sunet.se/pub/os/BeOS/ - SUNET, Uppsala, Sweden

I'm really starting to get tired of people mis-representing BeOS on slashdot... From The BeOS FAQ:

The underlying infrastructure for supporting multiple logins and multiple users' preferences is there, and the facility will likely appear in a future release.

Meaning a file system (the BFS; you know, the 64-bit, multithreaded, fully-journaled, database-like one) with fully-working owner/group/all and read/wrtie/execture permissions is already in place (it just happens that root (or "baron" as they call it) owns everything for now). Also, home directories (for now there's only one) with both global and user-specific locations for settings, drivers, file system add-ons, and all that jazz are already implemented elegantly, beautifully, and functionally.

In addition, the BeOS's new networking stack, code-named BONE and due out pretty soon (not long after R5) will be "around twenty times (2000%) the speed of the current net_server" and "in the same league as Linux and FreeBSD" (BONE designer Howard Berkley from The Be newsletter, further explained in a BeOS Central Interview and a followup )

And let's don't forget the usual arguments of prevasive multithreading, multiprocessor optimization, high-efficiency modular I/O, the clarity and simplicity of a 100% object-oriented design, and those wonderful multithreaded direct access graphics capabilities.

Given enough market demand (not likely), Be could spend the time to finish the multi-user functionality, OR after what I see as the eventual (but not any time soon) open-sourcing of the cureently free, but closed-source desktop version of BeOS (keeping the appliance version (BeIA/"Stinger") closed-source) under something like the Mozilla license, we could just do it ourselves. Hopefully, if Be succeeds financially in the Internet Appliance market, they will be able convince the stockholders that open-source has enough advantages, and then we'll get to the really fun stuff :-)

Come on, people, at least give the little guy a chance! I sincerely believe that Be could become a much larger player in the OS wars if people would be more open-minded to something that isn't open-souce (yet).

Long live the underdog,
~tide
"Linux is only free if your time has no value."

I'm really starting to get tired of people mis-representing BeOS on slashdot... From The BeOS FAQ:

The underlying infrastructure for supporting multiple logins and multiple users' preferences is there, and the facility will likely appear in a future release.

Meaning a file system (the BFS; you know, the 64-bit, multithreaded, fully-journaled, database-like one) with fully-working owner/group/all and read/wrtie/execture permissions is already in place (it just happens that root (or "baron" as they call it) owns everything for now). Also, home directories (for now there's only one) with both global and user-specific locations for settings, drivers, file system add-ons, and all that jazz are already implemented elegantly, beautifully, and functionally.

In addition, the BeOS's new networking stack, code-named BONE and due out pretty soon (not long after R5) will be "around twenty times (2000%) the speed of the current net_server" and "in the same league as Linux and FreeBSD" (BONE designer Howard Berkley from The Be newsletter, further explained in a BeOS Central Interview and a followup )

And let's don't forget the usual arguments of prevasive multithreading, multiprocessor optimization, high-efficiency modular I/O, the clarity and simplicity of a 100% object-oriented design, and those wonderful multithreaded direct access graphics capabilities.

Given enough market demand (not likely), Be could spend the time to finish the multi-user functionality, OR after what I see as the eventual (but not any time soon) open-sourcing of the cureently free, but closed-source desktop version of BeOS (keeping the appliance version (BeIA/"Stinger") closed-source) under something like the Mozilla license, we could just do it ourselves. Hopefully, if Be succeeds financially in the Internet Appliance market, they will be able convince the stockholders that open-source has enough advantages, and then we'll get to the really fun stuff :-)

Come on, people, at least give the little guy a chance! I sincerely believe that Be could become a much larger player in the OS wars if people would be more open-minded to something that isn't open-souce (yet).

Long live the underdog,
~tide
"Linux is only free if your time has no value."