Normally speaking that would amount to down time, not so much the destruction of the data. So for my MP3/XViD collection, a single power supply would suffice.
And they sued a dutch spammer into oblivion, tried to get cable providers to open up to other ISP's, held a conference on their 10th year on copyright issues, put some money into bits of freedom, have a large anonymous ftp server with goodies for all, provide IPv6 services... Lets just say they are on the good side. They do put letters from the Dutch RIAA through to their customers though. Anonymously, of course:)
This is not that strange, since they have sprung from a now defunct hacker magazine called hacktic. more information here
Although I do think broadband has its usages, I tend to agree with you here. I would like to see the government (any government) do two things: set up a compatitive environment for telco's and cable providers as well as ISP's and application providers (note the separation), and provide internet based services themselves. I do think an "always-on" connection at a reasonable price is a must to push the market. But most of the interest should be focussed on pull. If people can do more with their current internet connection, then the rest will follow automatically.
That's not entirely true I think. I've had 512/64 and I could use the whole 512 (divided by 10 for KB/sec, my provider uses ATM) download. You could easily stall it for a bit by using up your upload though. That is, unless you used something like linux to make sure the ack packages go through first. Currently I've got 8/1 and that works fine as well. Another provider is advertising with 20/1 MBit/sec ADSL for 40 euro's a month. So that's 20:1 (!). Most of it can be used for video streaming (live soccer) though, which is probably UDP and therefore does not need ack packages.
- At the least stripe the volumes across multiple disks.
Err, do you mean stripe sets or do you mean RAID?
- The system should have the virtual memory partition/swap on a separate disk alone. If not controller.
Add enough RAM and throw out the swap space. RAM is (still) cheap these days. With the advance of serial ATA, having the swap on a different controller should not be too difficult.
- SCSI drives are notorius for utililizing less resources.
Notorius? Don't you mean "famous", maybe?
- Run the database on raw device, not on some filesystem
That could help, but with the current systems I kinda doubt that it would help *that* much. And I don't know how well this goes with the whole striping idea and all.
Nobody I know calls it Java 5.0. Everybody calls it 1.5. And I am at least glad they removed the 2 from the name. I mean, J2SDK 1.4.07b04 or something was getting a bit of a mouthfull. Now we just have jdk1.5_04 (it actually INSTALLS in that default folder).
Anyway, just like in IE and lots of other programs, one should just use the number the developers use. That is making the whole issue much more palatable. Just ignore the marketing speak altogether.
Since the 2.0 specification should indeed make MP3 (or even better, Ogg) stereo sound possible, I am eagerly awaiting digital headphones. I would not mind an additional mike either, as long as it does not mess up the distance that the thing should work. Applications: normal in house use, but also use with laptops, PDA's and MP3 mobile phones.
WiFi does not work for this due to the amount of energy that is needed, the problem of setting up the connection and the lack of standardisation on the application level.
Philips and Sennheisser, get your engines started! I'll buy the first functional BT headphones you provide (under euro 300 of course).
I'm sorry to say this, but I can hardly find it an interesting review. There are many, many sites that review these kind of drives, so I cannot see this warrant a special article all by itself.
Nor can I understand the conclusion. Especially in the warranty, but also in the access time, this drive is beat by the Seagate. Still, it gets the highest praise (as therefore 5 stars).
Then there are some other problems with the article: - SATA300 not tested (would be unfair for the competetion according to the author - which is a lie since you can easily test both - he just does not have a SATA-300 interface ready) - no testing of RAID - "it is probably less noisy than the others"
I thought that a price of 48 cents per GB is now pretty common. No need to stress *that*. I'd rather have some more info like spinup times, testing of the SMART interface, power mgmt and how it performes after being driven over by a car.
Are you *sure* that the client can only run on Windows? Since most VPN's use standard protocols, ensuring compatibility with most operating systems and (hint) routers. Even if you could build up a VPN you would still need to configure Windows with a route/proxy to your added system-on-usb.
These will be more important than any programming language. The way Java or.NET handle components should be an eye opener. What you want is code you can control, what does what you expect it to do.
On the runtime part: - plugins (see Eclipse and OSGi technology) - assemblies/libraries (see.NET framework) - VM support (garbage collection, overflow handling, exception handling, bounds checking etc.) - runtime information (reflection) - supporting components (application servers, message services)
On the IDE part: - parsing editors (see Eclipse) - code analyzers (PMD) - semantic links from code to design tools (needs a parsing editor to function best) - unit testing
I see a mayor shift towards runtime technologies coming up ahead. I can see more flexibility coming up in how programs are run and objects are used. Compilers are already running in the background to use Java both as script and as compile time language, for instance. Java may be to strict on some issues however.
For programs, components, OO and the imperative model will probably be here to stay. Other languages will be used for their respective domains, but the language wars seem to be over for now (as each programming language looks more and more like its siblings). Lets focus on the runtime and supportive technologies. And getting the things running reliably, for crying out loud.
I don't think using multiple languages that try to accomplish the same thing is such a good idea (see.NET C++, C#, VB7 and J#). You end up learning all of them (see MSDN). Mixing with languages that use other programming paradigms could be usefull though.
And yes, this is also an opinion piece, as is the parent.
Except the one that the user is actually used to: native widgets. SWT is the way to go, not swing. Swing will always be the emulation of the real thing. Still Java, but it might take some time for the GUI (toolkit) developers to realize this. Test Azureus (bittorrent client) and Eclipse (really good, free Java IDE) to get an idea. On Java 1.5 of course, any other Java runtime is (or, shoudl be ) history.
The difference between a programming language and a tag "language" for presenting data structures is obviously of no concern to you.
XML is actually rather easy to learn (that is, the XML specification, never mention the additional techniques around it). There are excelent editors (that display the XML in trees) just for you. Not so with Lisp, displaying Lisp in a tree would do little to nothing for readability.
Anyway, XML uses </tag> to show the end of a tag, while lisp uses ). I know which one I prefer.
Eh, but the parent was relying on a linux bootable disk, which still can use the modularized drivers for linux. A more serious problem might be that the ATI & NVidia drivers are proprietary, and would probably not be supported for redistribution. Oh well.
Certificates do not detect nothing, the clients using the certificates *may* detect that the hostname is not correct. There is a bug in IE that can be easily used to spoof websites using a man in the middle attack. And certificates can be had pretty easily, there is enough proof for that.
Furthermore, the use of HTTPS is not a panacea. Not all companies may like HTTPS since the underlying SSL connection will not let their proxy scan the contents of the connection. This would make it very easy for e.g. porn surfers to use the connection.
And even in this day and age, HTTPS obviously comes with its processor overhead. And it makes it more difficult to load balance things as well (mixed content).
And here we are, the slashdot community thinking Skype is good. Or is it? Skype has a very interesting protocol (or actually, a complete protocol stack). But it is proprietary. Do we actually want to replace the old monopolies with a new one?
What we need is an open source protocol that works just as well. Skype is a great protocol, but it is *not* the way to go forward. Come on guys, it can not be that hard to send (encrypted) voice over UDP. Let's create a nice, extendible (video etc) protocol that uses UDP - at least for the data channels.
You have these less skilled workers and you let them do C? Why? Are you fond of bugs or something? Let them use a higher level language instead. Java comes to mind.
Anyway, you could pick up minix from somewhere, install it on a cheap x86 box and let them implement a quota system or something in C. It has been designed for that. Lets them - eh - love vi, make and cc as well.
I had to do this at the "Vrije Universiteit" under Tanenbaum, and gosh, did I have a lot of fun!
Dear Azureflare. We are aware of the attempts of the Linux community to communicate with our infrastructure. You can rest assured that we are plugging the hole as we speak.
Slashdot Mirror
Normally speaking that would amount to down time, not so much the destruction of the data. So for my MP3/XViD collection, a single power supply would suffice.
And they sued a dutch spammer into oblivion, tried to get cable providers to open up to other ISP's, held a conference on their 10th year on copyright issues, put some money into bits of freedom, have a large anonymous ftp server with goodies for all, provide IPv6 services... Lets just say they are on the good side. They do put letters from the Dutch RIAA through to their customers though. Anonymously, of course :)
This is not that strange, since they have sprung from a now defunct hacker magazine called hacktic. more information here
Although I do think broadband has its usages, I tend to agree with you here. I would like to see the government (any government) do two things: set up a compatitive environment for telco's and cable providers as well as ISP's and application providers (note the separation), and provide internet based services themselves. I do think an "always-on" connection at a reasonable price is a must to push the market. But most of the interest should be focussed on pull. If people can do more with their current internet connection, then the rest will follow automatically.
That's not entirely true I think. I've had 512/64 and I could use the whole 512 (divided by 10 for KB/sec, my provider uses ATM) download. You could easily stall it for a bit by using up your upload though. That is, unless you used something like linux to make sure the ack packages go through first. Currently I've got 8/1 and that works fine as well. Another provider is advertising with 20 /1 MBit/sec ADSL for 40 euro's a month. So that's 20:1 (!). Most of it can be used for video streaming (live soccer) though, which is probably UDP and therefore does not need ack packages.
Err, do you mean stripe sets or do you mean RAID?
Add enough RAM and throw out the swap space. RAM is (still) cheap these days. With the advance of serial ATA, having the swap on a different controller should not be too difficult.
Notorius? Don't you mean "famous", maybe?
That could help, but with the current systems I kinda doubt that it would help *that* much. And I don't know how well this goes with the whole striping idea and all.
Nobody I know calls it Java 5.0. Everybody calls it 1.5. And I am at least glad they removed the 2 from the name. I mean, J2SDK 1.4.07b04 or something was getting a bit of a mouthfull. Now we just have jdk1.5_04 (it actually INSTALLS in that default folder).
Anyway, just like in IE and lots of other programs, one should just use the number the developers use. That is making the whole issue much more palatable. Just ignore the marketing speak altogether.
Since the 2.0 specification should indeed make MP3 (or even better, Ogg) stereo sound possible, I am eagerly awaiting digital headphones. I would not mind an additional mike either, as long as it does not mess up the distance that the thing should work. Applications: normal in house use, but also use with laptops, PDA's and MP3 mobile phones.
WiFi does not work for this due to the amount of energy that is needed, the problem of setting up the connection and the lack of standardisation on the application level.
Philips and Sennheisser, get your engines started! I'll buy the first functional BT headphones you provide (under euro 300 of course).
I'm sorry to say this, but I can hardly find it an interesting review. There are many, many sites that review these kind of drives, so I cannot see this warrant a special article all by itself.
Nor can I understand the conclusion. Especially in the warranty, but also in the access time, this drive is beat by the Seagate. Still, it gets the highest praise (as therefore 5 stars).
Then there are some other problems with the article:
- SATA300 not tested (would be unfair for the competetion according to the author - which is a lie since you can easily test both - he just does not have a SATA-300 interface ready)
- no testing of RAID
- "it is probably less noisy than the others"
I thought that a price of 48 cents per GB is now pretty common. No need to stress *that*. I'd rather have some more info like spinup times, testing of the SMART interface, power mgmt and how it performes after being driven over by a car.
Are you *sure* that the client can only run on Windows? Since most VPN's use standard protocols, ensuring compatibility with most operating systems and (hint) routers. Even if you could build up a VPN you would still need to configure Windows with a route/proxy to your added system-on-usb.
Don't discriminate against people that already have the carpal tunnel syndrome :)
That sounds more like salvation than anything else for the avarage slashdot reader.
These will be more important than any programming language. The way Java or .NET handle components should be an eye opener. What you want is code you can control, what does what you expect it to do.
.NET framework)
.NET C++, C#, VB7 and J#). You end up learning all of them (see MSDN). Mixing with languages that use other programming paradigms could be usefull though.
On the runtime part:
- plugins (see Eclipse and OSGi technology)
- assemblies/libraries (see
- VM support (garbage collection, overflow handling, exception handling, bounds checking etc.)
- runtime information (reflection)
- supporting components (application servers, message services)
On the IDE part:
- parsing editors (see Eclipse)
- code analyzers (PMD)
- semantic links from code to design tools (needs a parsing editor to function best)
- unit testing
I see a mayor shift towards runtime technologies coming up ahead. I can see more flexibility coming up in how programs are run and objects are used. Compilers are already running in the background to use Java both as script and as compile time language, for instance. Java may be to strict on some issues however.
For programs, components, OO and the imperative model will probably be here to stay. Other languages will be used for their respective domains, but the language wars seem to be over for now (as each programming language looks more and more like its siblings). Lets focus on the runtime and supportive technologies. And getting the things running reliably, for crying out loud.
I don't think using multiple languages that try to accomplish the same thing is such a good idea (see
And yes, this is also an opinion piece, as is the parent.
Except the one that the user is actually used to: native widgets. SWT is the way to go, not swing. Swing will always be the emulation of the real thing. Still Java, but it might take some time for the GUI (toolkit) developers to realize this. Test Azureus (bittorrent client) and Eclipse (really good, free Java IDE) to get an idea. On Java 1.5 of course, any other Java runtime is (or, shoudl be ) history.
Or you can define your tags in Java (JSP), or use PHP, ASP ...
Ok, there we go again. Write one hundred times:
- Lisp is a programming language
- XML is a data description language
If you haven't learned by then, follow up by writing one hundred times:
- Lisp is created mostly by humans
- XML is created mostly by computers
The difference between a programming language and a tag "language" for presenting data structures is obviously of no concern to you.
XML is actually rather easy to learn (that is, the XML specification, never mention the additional techniques around it). There are excelent editors (that display the XML in trees) just for you. Not so with Lisp, displaying Lisp in a tree would do little to nothing for readability.
Anyway, XML uses </tag> to show the end of a tag, while lisp uses ). I know which one I prefer.
Ugh, for all those not in the know, don't look that up...
No seriously, don't!
Told ya.
1) Tune your old server.
2) Save cost on new server. Don't buy Dell (for servers or laptops).
3) Be happy.
4) ???
5) This is getting old.
Hi anonymous coward. You are right of course, but you are not seen by too many people. Hello mods?
:)
Still got the (386) version of it lying around here somewhere. Straight from AST
Eh, but the parent was relying on a linux bootable disk, which still can use the modularized drivers for linux. A more serious problem might be that the ATI & NVidia drivers are proprietary, and would probably not be supported for redistribution. Oh well.
The author has already answered, but the correct answer should of course have been:
Me and my friends are not willing to talk to you anymore until somewhere in 2006.
Certificates do not detect nothing, the clients using the certificates *may* detect that the hostname is not correct. There is a bug in IE that can be easily used to spoof websites using a man in the middle attack. And certificates can be had pretty easily, there is enough proof for that.
Furthermore, the use of HTTPS is not a panacea. Not all companies may like HTTPS since the underlying SSL connection will not let their proxy scan the contents of the connection. This would make it very easy for e.g. porn surfers to use the connection.
And even in this day and age, HTTPS obviously comes with its processor overhead. And it makes it more difficult to load balance things as well (mixed content).
And here we are, the slashdot community thinking Skype is good. Or is it? Skype has a very interesting protocol (or actually, a complete protocol stack). But it is proprietary. Do we actually want to replace the old monopolies with a new one?
What we need is an open source protocol that works just as well. Skype is a great protocol, but it is *not* the way to go forward. Come on guys, it can not be that hard to send (encrypted) voice over UDP. Let's create a nice, extendible (video etc) protocol that uses UDP - at least for the data channels.
You have these less skilled workers and you let them do C? Why? Are you fond of bugs or something? Let them use a higher level language instead. Java comes to mind.
Anyway, you could pick up minix from somewhere, install it on a cheap x86 box and let them implement a quota system or something in C. It has been designed for that. Lets them - eh - love vi, make and cc as well.
I had to do this at the "Vrije Universiteit" under Tanenbaum, and gosh, did I have a lot of fun!
Dear Azureflare. We are aware of the attempts of the Linux community to communicate with our infrastructure. You can rest assured that we are plugging the hole as we speak.