Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×

Comment Re:Just another flavour of Linux? (Score 1) 411

IIRC The OS Is POSIX Compatible, porting *most* applications from Linux to BeOS isn't very difficult.

True, but this works primarily with command line applications and libraries. Haiku (and BeOS for that matter) already has tcpdump, for instance, but assuming they didn't, I don't think it would be terribly hard to port.

The GUI for Wireshark, on the other hand, would prove to be a different story: I'm not sure which GUI tools or library is used in Wireshark's GUI, but I'm pretty positive that there's either no version or no recent version available on BeOS or Haiku at this time. I may be wrong, but I doubt it. Porting that would then become a question of whether the developer should through the effort to port the missing library/libraries or developing a native UI.

Obviously some of the application's code will work just fine, but it's unlikely you're going to find very many applications that compile quickly and easily on Linux that will do the same on BeOS/Haiku.

Comment Re:I'll try to break it down (Score 1) 411

Of course it could be argued that 19 years is a long time in the computer world and BeOS would be old enough to have accumulated its own cruft by now.

While that's technically true, it's not exactly what happened. As Be moved from the Hobbit processor to the PowerPC then to x86 processors, and in some cases from one version to another, they broke backwards compatibility numerous times, more often than not intentionally for the good of the OS. Some legacy things did transition from one version of BeOS to another, but the engineering managers didn't like to transition a huge amount of [bad] legacy code, they preferred to instead to rewrite a lot of things to solve the problems the earlier versions had. Of course, this has nothing to do with Haiku which is designed to recreate BeOS R5, the last official revision of BeOS.

Comment Re:Just another flavour of Linux? (Score 1) 411

As I stated, BeOS and Haiku are not Linux compatible except on a limited source code basis. I did a quick search for both QT and WxWidgets on BeBits and Haikuware (two places where many people fetch BeOS/Haiku software) and only found a QT from 2001 (2.3.0) on either site. There's no GNOME, KDE, or even X compatibility in either BeOS or Haiku by default, although I have seen an X server running on BeOS many years ago. If you put enough energy into it, you can make just about anything run on any operating system, but the question is: is it worth it? That said, yes, someone could port Linux/Unix software over to Haiku relatively easily, especially if they're willing to use native code for GUI, but that doesn't make Haiku a flavor of Linux any more than it makes Windows a flavor of Linux. There are more similarities between a Linux and Haiku binary than a Windows binary, but the fact is that they'd have to be extremely similar for a Linux binary to run on Haiku, and one of the primary goals of Haiku was to maintain binary compatibility with BeOS R5 instead of Linux. There... I'm done rambling... :-)

Comment Re:Just another flavour of Linux? (Score 1) 411

It'd be better if they all came to a consensus on where libraries go and follow the Filesystem Hierarchy Standard and a package system.

Haiku, like BeOS, is in no way compatible with Linux except on a limited source code basis. It's not using the Linux kernel and cannot run Linux software, therefore there's little point in conforming to anyone's standards but perhaps Be's or their own.

Comment Has anybody bothered...? (Score 2, Interesting) 230

Has any body bothered to point out to the nice Californian Representative that blurring the picture would be pointless because it would give a potential terrorist points of interest? Publicly requesting these items to be blurred because they could be threatened and then looking at the map will do nothing but make it easier to find them.

Comment Re:Old News (Score 1) 277

Ballard is mentioned in the Wikipedia entry for the USS Scorpion. I read through this a few weeks ago, and thought I saw a reference to it being a dual mission there, and it supposedly wasn't shrouded in secracy, but was partially intended to find the wreck to check on possible radiation leaks. http://en.wikipedia.org/wiki/USS_Scorpion_(SSN-589)

Slashdot Top Deals

<<<<< EVACUATION ROUTE <<<<<

Working...