Massive license fees? How do you define "massive?" A Windows server license will cost you a few thousand bucks, depending on configuration. That's a one-time charge
Client Access Licenses.
The server licenses are _nothing_ compared to the cost of CALs to cover a medium sized business. And with Licensing 6.0, you are going to pay for those CALs every year.
you connected to it by drilling a tiny hole and inserting your tap into the cable
They were called "vampire connectors".
It was great fun crawling around in the ceiling trying to figure out which one fritz'ed out because somebody pulled a bit too hard on the drop-down AUI wire.
It really made 50ohm BNC look good when it came out.:-)
Only if the person installing the BNC wire actually knew how to install them!
Guess which protocol Fibre Channel uses. That's right, SCSI.
Guess which protocol ATAPI uses. That's right, SCSI.
The SCSI protocol will probably live for a very, very long time. The physical SCSI bus will probably go away soon, but all of the new physical layer standards run the SCSI protocol.
Buy any recently produced server-class system and open the cover to see 64bit/66Mhz PCI slots. Heck, even Dell's 1U boxes come with 2 of them: http://www.dell.com/us/en/esg/topics/esg_pedge_rac kmain_servers_3_pedge_1550.htm
You know, though, that the strength of the Open Source movement is that we have no need to stick to the well-trodden paths of marketeers. If Linux advocates do a good job of presenting Linux on the day MS rolls out W2K, we get good press too. (Remember, any press is good press as long as they spell our name right). MS is in the position that they couldn't hold a media-fest when we release 2.4. We should use every advantage we have.
I think that there is one point that everybody here is missing. The RIAA and MPIA want to control who can make original recordings in the first place. If everybody and their brother can burn their own CD or DVD, there really isn't a need for any of the big recording labels anymore.
I think these guys see that coming and want to prevent it by proposing a medium (DVD) that you can't make your own recordings unless you pay some outrageous fee to get a license key. It is a way to prevent the little guys from getting into the business.
It really comes down to the big players trying to maintain their hold on the market going into the digital age.
What in the heck are you talking about??? I've worked wireless point to point comm gear and satellite comm gear for years. There is *NO* reason why a point to point wireless link can't get you the *exact same* latency as a wire-bound link. RF doesn't go noticeably slower through air than through that copper wire.
The only place you get really big latencies is when you take a satellite hop. *Especially* if you take a satellite hop through one or more geostationary satellites (the ones that are 36,000 km up) If you go through one of those, you get 1/4 sec delay for each satellite you go through. (Try TCP/IP from Egypt to the west coast, going through four different satellites, you get 5-10 second round trip times. Have you done this? I didn't think so. I have.) On the other hand, I've done multiple 30 mile line-of-sight connections in series (90 miles total), with 10ms latency.
In the instance of a terrestrial microwave point-to-point connection, you will get roughly equivalent latencies as with a wire-link. Then you get down to factors such as how well connected is your provider, how multihomed is their datacenter, and such.
Go read a basic science textbook before you go spouting off outrageous claims about something you know *nothing* about, and have no experience with.
If you are going to slag wireless links, do it for some other reason than the false claim that they are slow. Mention things like rain fade, or keeping antennas or dishes aligned. But don't say it's slow, cause it is simply not true.
I've been looking around the SGI website and it isn't immediately obvious to me who to write to at SGI to thank for all these wonderful Open Source donations. Anybody have email addresses that we could slashdot with thank-yous?
We use Legato Networker in our enterprise backup environment. They have had an unsupported Linux Client for several months now, but just recently have release a supported Linux Client. We use it to back up a couple of our Linux boxes here, and it works great. Much more reliable than Arcserve or Alexandria. We use Legato to back up Oracle, Sybase, and MS SQL Server, Windows NT, HP-UX, and we are just now starting a pilot to move all of our Novell stuff to Legato.
The Legato software so far has been rock solid, as long as you keep up with it. Restores have gone off without a hitch. We have NEVER lost a file with Networker.
If anyone needs more info, email me and I would be happy to tell you about our experience.
Slashdot Mirror
Client Access Licenses.
The server licenses are _nothing_ compared to the cost of CALs to cover a medium sized business. And with Licensing 6.0, you are going to pay for those CALs every year.
Ext2 has been endian safe since kernel v1.{lownum}
Ext3 has _always_ been endian safe.
reiserfs became endian-safe about 6 months ago.
Don't know, but I would suspect the same for JFS, etc.
They were called "vampire connectors".
It was great fun crawling around in the ceiling trying to figure out which one fritz'ed out because somebody pulled a bit too hard on the drop-down AUI wire.
It really made 50ohm BNC look good when it came out. :-)
Only if the person installing the BNC wire actually knew how to install them!
This is incorrect. The latest Celerons are based on the PIII core and have the exact same FPU as the PIII.
SCSI is dead. Long live SCSI.
Guess which protocol Fibre Channel uses. That's right, SCSI.
Guess which protocol ATAPI uses. That's right, SCSI.
The SCSI protocol will probably live for a very, very long time. The physical SCSI bus will probably go away soon, but all of the new physical layer standards run the SCSI protocol.
Buy any recently produced server-class system and open the cover to see 64bit/66Mhz PCI slots. Heck, even Dell's 1U boxes come with 2 of them: http://www.dell.com/us/en/esg/topics/esg_pedge_rac kmain_servers_3_pedge_1550.htm
Um... Excuse me... have you looked at Dell lately? You can order any one of their servers with Novell 5 pre-installed.
You know, though, that the strength of the Open Source movement is that we have no need to stick to the well-trodden paths of marketeers. If Linux advocates do a good job of presenting Linux on the day MS rolls out W2K, we get good press too. (Remember, any press is good press as long as they spell our name right). MS is in the position that they couldn't hold a media-fest when we release 2.4. We should use every advantage we have.
I think these guys see that coming and want to prevent it by proposing a medium (DVD) that you can't make your own recordings unless you pay some outrageous fee to get a license key. It is a way to prevent the little guys from getting into the business.
It really comes down to the big players trying to maintain their hold on the market going into the digital age.
What in the heck are you talking about??? I've worked wireless point to point comm gear and satellite comm gear for years. There is *NO* reason why a point to point wireless link can't get you the *exact same* latency as a wire-bound link. RF doesn't go noticeably slower through air than through that copper wire.
The only place you get really big latencies is when you take a satellite hop. *Especially* if you take a satellite hop through one or more geostationary satellites (the ones that are 36,000 km up) If you go through one of those, you get 1/4 sec delay for each satellite you go through. (Try TCP/IP from Egypt to the west coast, going through four different satellites, you get 5-10 second round trip times. Have you done this? I didn't think so. I have.) On the other hand, I've done multiple 30 mile line-of-sight connections in series (90 miles total), with 10ms latency.
In the instance of a terrestrial microwave point-to-point connection, you will get roughly equivalent latencies as with a wire-link. Then you get down to factors such as how well connected is your provider, how multihomed is their datacenter, and such.
Go read a basic science textbook before you go spouting off outrageous claims about something you know *nothing* about, and have no experience with.
If you are going to slag wireless links, do it for some other reason than the false claim that they are slow. Mention things like rain fade, or keeping antennas or dishes aligned. But don't say it's slow, cause it is simply not true.
I've been looking around the SGI website and it isn't immediately obvious to me who to write to at SGI to thank for all these wonderful Open Source donations. Anybody have email addresses that we could slashdot with thank-yous?
We use Legato Networker in our enterprise backup environment. They have had an unsupported Linux Client for several months now, but just recently have release a supported Linux Client. We use it to back up a couple of our Linux boxes here, and it works great. Much more reliable than Arcserve or Alexandria. We use Legato to back up Oracle, Sybase, and MS SQL Server, Windows NT, HP-UX, and we are just now starting a pilot to move all of our Novell stuff to Legato.
The Legato software so far has been rock solid, as long as you keep up with it. Restores have gone off without a hitch. We have NEVER lost a file with Networker.
If anyone needs more info, email me and I would be happy to tell you about our experience.
--Michael Brown
It is a (pants) zipper.