>the Linux operating system will soon end up like
>*BSD, with several mutually incompatible,
> infighting factions. We can't let this happen.
Where on Earth did you get this nonsense from? There are three open-source BSDs, each with a different focus. Admittedly a few OpenBSD and NetBSD developers aren't the best of chums, but most of the developers are happy to share code between projects (eg. dirhash, smp, usb etc)
My BeOS development down the toilet? I didn't have much trouble porting my BeOS apps to KDE because I wrote my code in a modular way - the 'meat' of the application was separate to the OS-dependent port.
>The reality is, there are no known cases of >DeCSS having been used to pirate any movie, so >the correct assumption should be that legal >users are using it for Fair Use purposes. DvD
No known court cases you mean? If you're denying
it happens then you have very blinkered vision - there was a thread on Slashdot a few months ago
where several people happily admitted trading ripping DVDs over their University network.
A movie fits quite nicely on a CDROM when compressed with DivX;^) and the quality is very
watchable (apparently, so I've heard etc. etc 8^)
Be *did* try to get high-end multimedia products
ported to BeOS but it's really not that simple -
and it's very expensive. Knowing some things I
can't talk about, they had a lot of bad luck too.
I'm not sure why/. is trying to blame all this on DMCA, since the Church of Scientology has been suing their^W enemies^W people for copyright infringment for years. It certainly didn't start after the DMCA came about.
Mach is derived from BSD too, although it's an
offshoot of an earlier ancestor than FreeBSD.
PS You can't 'steal' BSD licensed code - it's
written with the intention that it should be used
by other people (as long as they adhere to the license).
I wrote the devleopment tools for the CyberKNEX
toys (http://www.cyberknex.com) using gcc (under
BeOS incidently). When I 'ported' the code to Windows to add a gui with C++Builder, I had to
change one or two of abou 20000 lines of code. Not a single problem with STL, templates or RTTI.
The shared library address space is 256M AIR, it's the addon space that's 32M. I suspect the original BeOS architects didn't dream that something as insanely bloated as Mozilla would come into being (30 million
lines last I heard).
> there is no workaround short of fixing the flaw in the BeOS kernel
Of *course* there are workarounds - such a workaround is being used for the Mozilla port.
Slashdot Mirror
>the Linux operating system will soon end up like
>*BSD, with several mutually incompatible,
> infighting factions. We can't let this happen.
Where on Earth did you get this nonsense from? There are three open-source BSDs, each with a different focus. Admittedly a few OpenBSD and NetBSD developers aren't the best of chums, but most of the developers are happy to share code between projects (eg. dirhash, smp, usb etc)
--Jon
I can't see anything in the original article that says that softupdates were turned on for the FreeBSD machine (AIR it's the default for 4.2 onwards).
This should give a significant speedup for tests which perform a lot of file operations.
--Jon
Mach /is/ derived from 4.2BSD (see Daemon Book for details)
--
C-YA
Jon
http://www.witchspace.com
My BeOS development down the toilet? I didn't have much trouble porting my BeOS apps to KDE because I wrote my code in a modular way - the 'meat' of the application was separate to the OS-dependent port.
--
C-YA
Jon
Hiya
It's funny, but NetBSD on my old Amiga is the *only* OS which has never crashed on me (including linux on x86)
--
Jon
From reading the article, there's no mention of either mounting the filesystem asynchronously (not so good) or enabling softupdates (good).
It's ironic that these server 'benchmarks' you see give more emphasis to speed than data security.
--
C-YA
Jon
>The reality is, there are no known cases of >DeCSS having been used to pirate any movie, so >the correct assumption should be that legal >users are using it for Fair Use purposes. DvD
;^) and the quality is very
No known court cases you mean? If you're denying
it happens then you have very blinkered vision - there was a thread on Slashdot a few months ago
where several people happily admitted trading ripping DVDs over their University network.
A movie fits quite nicely on a CDROM when compressed with DivX
watchable (apparently, so I've heard etc. etc 8^)
--
C-YA
Jon
Be *did* try to get high-end multimedia products
ported to BeOS but it's really not that simple -
and it's very expensive. Knowing some things I
can't talk about, they had a lot of bad luck too.
I'm not sure why /. is trying to blame all this on DMCA, since the Church of Scientology has been suing their^W enemies^W people for copyright infringment for years. It certainly didn't start after the DMCA came about.
Indeed I'm not a CS student, I work for a living.
Mach is derived from 4.2/4.3BSD. See the diagram
on page 6 of "Design and Implementation of the
4.4BSD Operating System" for more details.
Yes I know Mach is a kernel. It was derived from
the BSD kernel.
Mach is derived from BSD too, although it's an
offshoot of an earlier ancestor than FreeBSD.
PS You can't 'steal' BSD licensed code - it's
written with the intention that it should be used
by other people (as long as they adhere to the license).
Regarding Borland C++ compatibility with gcc:
I wrote the devleopment tools for the CyberKNEX
toys (http://www.cyberknex.com) using gcc (under
BeOS incidently). When I 'ported' the code to Windows to add a gui with C++Builder, I had to
change one or two of abou 20000 lines of code. Not a single problem with STL, templates or RTTI.
Jon
The shared library address space is 256M AIR, it's the addon space that's 32M. I suspect the original BeOS architects didn't dream that something as insanely bloated as Mozilla would come into being (30 million
lines last I heard).
> there is no workaround short of fixing the flaw in the BeOS kernel
Of *course* there are workarounds - such a workaround is being used for the Mozilla port.
C-YA
Jon