My company makes atmospheric radar systems (eg directly measure winds, or meteor events). We are going to run a campaign in Western Australia (near Exmouth) during the Leonids.
We may even have live updates on a web page during the show (if I write the code in time anyway:)
FreeBSD (as of Aug 2000) has a nifty feature called 'accept filters' which allows a process to delay the return from a call to accept() until al condition is met. The condition is programmable so a web server can wait until the entire header has been recevied before returning. This saves spurious context switches when you get around to read()ing the data as the header is already in memory.
This also means that if you DO have a bug that allows someone to exploit your web server they only get access to the web user, not the kernel privilegde level..
Anyone want to guess how long it's going to take before an exploit is found in Tux?
"I don't see how buying a hardware company helps the bottom line. Yes it diversifies and adds to the impression that BSDi is more vertically integrated, but does it do anything other than annoy all the other hardware companies that ship boxes with FRbEsEdBiSD already installed?"
Well.. if the company makes money then it helps your bottom line..
Linux is a decentralized development model. It is very difficult for one point of failure (other than Linus T) to cause a total breakdown in development. With most of the major players in BSD now under one umbrella, if the ship sinks, will there be enough left to continue?"
FreeBSD has more than 200 committers, and they don't all work for BSDi/WC (not by a long shot). AFAIK Open/Net BSD aren't 'under the same umbrella' as FreeBSD/BSDi either. If BSDi/WC go down then toilet then that is not happy news, but I think there are a LOT of other companies around which would NOT want to see that happen. Also remeber that WC and BSDi actually make money, unlike the IPO'd Linux companies which it is claimed will support Linux. Presumably Telenet ALSO make money, so now you have a very nice package to offer customers.
IMHO the Linux community has more to worry about in this regard, most of the companies which a vested interest in Linux are fairly new, and hence have a higher chance of failure.
This guy is *worse* that companies that use patents to agressivly protect their ideas, at least they're stuck in their old ways and its what they're used to. This guy is a Linux user, so you'd expect him to grok the whole sharing code is good thing...
Its not even clear if the patent is enforceable ANYWAY, or if there is prior art.
If you are using i386, then FreeBSD is actually a nice place to start for a custom installation since it starts off small, and has the release engineering to enable you to actually make a distribution.
Case in point, we had a setup which needed a large collection of custom patches to work. I added these patches to the system, checked it built, then decided I'd like a CD (like the ones Walnut Creek sells) of the result so I could install it easily). Basically all I did was check in the source into a new cvs repo, then cd/usr/src/release and type make release
2.2.8 would probably be best unless you have unsupported hardware (ie the drivers are only available in 3.x)
The user limit isn't necessarily a problem if you pick something like Cyrus IMAPD for a mail server.. Then noone has to have accounts on the machine anyway:)
(Of course then all your users would be using POP or IMAP to read mail.. Something I would suspect is going to happen if you have 20k+ users)
Slashdot Mirror
ndiswrapper is GPL, Project Evil is BSDL.
:)
I would be expecting a port of Project Evil to Net/Open BSD before a port of ndiswrapper to FreeBSD
We may even have live updates on a web page during the show (if I write the code in time anyway :)
This also means that if you DO have a bug that allows someone to exploit your web server they only get access to the web user, not the kernel privilegde level..
Anyone want to guess how long it's going to take before an exploit is found in Tux?
Well.. if the company makes money then it helps your bottom line..
Linux is a decentralized development model. It is very difficult for one point of failure (other than Linus T) to cause a total breakdown in development. With most of the major players in BSD now under one umbrella, if the ship sinks, will there be enough left to continue?"
FreeBSD has more than 200 committers, and they don't all work for BSDi/WC (not by a long shot). AFAIK Open/Net BSD aren't 'under the same umbrella' as FreeBSD/BSDi either. If BSDi/WC go down then toilet then that is not happy news, but I think there are a LOT of other companies around which would NOT want to see that happen. Also remeber that WC and BSDi actually make money, unlike the IPO'd Linux companies which it is claimed will support Linux. Presumably Telenet ALSO make money, so now you have a very nice package to offer customers.
IMHO the Linux community has more to worry about in this regard, most of the companies which a vested interest in Linux are fairly new, and hence have a higher chance of failure.
The FreeBSD boot loader has been able to do this for ages!
Of course it can also read UFS, FAT, and do PXE booting..
Run faster!
Not 'all open projects' - just Linux ones.
This guy is *worse* that companies that use patents to agressivly protect their ideas, at least they're stuck in their old ways and its what they're used to. This guy is a Linux user, so you'd expect him to grok the whole sharing code is good thing...
Its not even clear if the patent is enforceable ANYWAY, or if there is prior art.
Same here.. I wrote some software to read data from their database, bit hard to put a logo up when its used tho!
The copy of their demon software I have is GPL'd though, so we could use that as a starting base..
I'd personally like to see some changes though, because the data format is pretty awful at the moment..
If you are using i386, then FreeBSD is actually a nice place to start for a custom installation since it starts off small, and has the release engineering to enable you to actually make a distribution.
/usr/src/release and type make release
Case in point, we had a setup which needed a large collection of custom patches to work. I added these patches to the system, checked it built, then decided I'd like a CD (like the ones Walnut Creek sells) of the result so I could install it easily). Basically all I did was check in the source into a new cvs repo, then cd
*really* easy.
2.2.8 would probably be best unless you have unsupported hardware (ie the drivers are only available in 3.x)
:)
The user limit isn't necessarily a problem if you pick something like Cyrus IMAPD for a mail server.. Then noone has to have accounts on the machine anyway
(Of course then all your users would be using POP or IMAP to read mail.. Something I would suspect is going to happen if you have 20k+ users)