I don't mind that at all. That's actually a very decent way of implementing it. However, most boards that I have looked at does allow editing at any time, even years after writing the post.
No, no, chances are, I am NOT behind a firewall or proxy, I am trying to correct a post on a board that is too goddamn old-school, its own admins don't know how to fix it to offer modern features, like editing posts.:rolleyes:
I don't care how "modern" the ability to edit posts is. It's utterly stupid, and messes up every single forum that uses it. When you say something publicly, you've said it. If you don't want to say it then don't publish it in the first place.
Especially on Slashdot this would be a total disaster (and has been elsewhere already). Typical troll:
Troll posts comment: "Microsoft are the good guys"
Baited user replies: "No, they're monopolists!"
Troll changes OP to: "Ubuntu are the good guys"
Public debate is founded upon the idea that when you say something, that thing has been said, and the content of the forum (or comments section) is a public record of what was said. When that is no longer true, anything you say can be taken out of context. And as a poster, I prefer it when that can't happen.
It's a big story for companies who actually want to run Solaris on IBM hardware. So far it has been difficult for them to get support. When you pay 100k USD for a server, you expect to have full support for the operating system you intend to run on it. So far, IBM has been unable to do this for Solaris. Them doing it now is a big deal. Not technically, but from the business side of things.
Technically, no. This does not mean that IBM wins. It greatly increases their chances, but at the core the case is about whether or not IBM complied with a contract signed between SCO (the old one, not the company formerly known as Caldera who renamed themselves to SCO) and IBM. The copyrights are only needed for a part of it.
However, as far as I understand, this ruling means that Linux is in the clear, even if SCO would win, since even if it is concluded that IBM violated their contract by using UNIX code (code from AIX, written by IBM, mind you) in Linux, this code would not be considered "secret" or "protected" since SCO didn't own it in the first place.
Yes, I did miss the point and I thank you for pointing that out.
I know how the default Solaris scheduler works and yes, it is vulnerable to this. However, I'm not so sure it's really a problem. I suppose it can become a problem for systems where you have a lot of users sharing the CPU, but other than that it's really a non-issue in most cases.
Perhaps Sun should ship a specific scheduling class that can be used for untrusted processes (although I suppose FIXED can somewhat fulfill this requirement).
This is quite old actually. The trick is that you can fool systems monitoring tools that use samplig by going to sleep at the exact time when the tool performs its sample.
If you use Solaris, the top replacement "prstat" has a flag -m that enables microstate accounting. This will give you the exact CPU time used, and not an estimate.
If you want to go further, you can use DTrace, which allows you to monitor in detail exactly what is going on. This is also unaffected by any tricks played by the process.
The lack of proper transactional writes in the "old" stack does not come from the file system, but it's an inherit problem with RAID5. It's solvable on the volume manager layer, but unless you use a battery-backed write-cache that solution becomes horribly slow.
ZFS seems to want to take all over the disk subsystem. Why? Is there a reason why it needs its own snapshot capabilities, instead of just using LVM?
Because there are many things your storage system can do if it has knowledge of the entire stack.
The problem with a "traditional" layered model is that the file system has to assume that the underlying storage device is a single consistent unit of storage, where a single write either succeeds, or it fails (in which case the data you wrote may or may not have been written). This all sounds very good and file systems like ext2 are written based on this assumtion.
However, if the underlying storage system is RAID5, and there is a power loss during the write, the entire stripe can become corrupt (read the Wikipedia article on the subject for more information). The file system can't solve this problem because it has no knowledge about the underlying storage stucture.
ZFS solves this problem in two ways, both of which reuires the storage model to be part of the filesystem:
Each physical write never overwrites "live" data on the disk. It writes the stripe to a new location, and once it's been completely committed to disk the old data is marked as free.
ZFS uses variable stripe width, so that it does not have to write larger stripes than nescessary. In other words, a large write can be directly translated to a write to a large stripe on the sotrage system, and a smaller write can use a smaller stripe width. This can improve performance since it can reduce the amount of data written.
There are plenty of other areas where this integration is needed, including snapshotting, but I hope the above explanation explains that the layered model is not always good.
"There is little, if any, benefit to dual-licensing OpenSolaris with CDDL and the yet to be approved/upcoming GPLv3 license - aside from possible short term good press for the project," it continued. "There are significant downsides to dual licensing, including, but not limited to, license complexity, confusion and the possibility of long term bad press from any exception language that such a license would inevitably require."
And exactly what is the problem of running a 32-bit Firefox? Other than the fact that all your plugins will work, that is.
64-bit is not a magic wand that will make your apps run faster. In fact, 64-bit usually makes an app run slower, although this is not so clear-cut in the case of the x64, since you also get a larger register set which improves things.
However, the point is that there is no visible advantage of running Firefox in 64-bit. If it's using over 4 GB of ram already, then you might ihave some other problems.:-)
Are you running Linux on an Itanium? Then you might have problems with the lack of Flash.
However, it's likely you have an x64-based machine, and I'm happy to tell you that the x64 architecture has not problems whatsoever running 32-bit applications , even side-by-side with the 64-bit ones. Just make sure you have all the 32-bit libraries installed and it'll work perfectly.
Do you realise that the hardware in this phone is identical to the Nokia E61?
The major difference between these two models (apart from the frequencies and those things) is that the WLAN (802.11g) support is disabled on the E62. I'll let you speculate why that is.
I have an E61. I also have an unlimited 3G data plan with my provider. I can use Fring to make Skype voice calls over the data connection, either using 3G or WLAN.
Now, ask yourself the following: Why is this impossible to do in the US, when it's possible in most of the rest of the world?
I dag legger Datakrimutvalget fram et forslag som vil pålegge Internett-leverandører å blokkere nettsider med ulovlig innhold.
I don't know a word of Norwegian, but it sounds like the Datacrime bureau wants to whitewash the Internet and block websites with bad content. Hey, at least I tried...
Actually, that wasn't too bad. I don't know where you got whitewash from, and "ulovlig" means illegal, not bad.
If you want to learn more about how it works, and have a lot of fun at the same time, I can recommend that you play around with Orbiter. It really helped me understand for the first time exactly how it works (and also how wrong it is to call the place where the ISS is "space".:-) ).
Your suggestion is good, except for the fact that it shows that you don't know orbital mechanics and therefor will not work at all.
A common misconception seems to be that an object in orbit is not affected by the earth's gravity. Nothing could be further from the truth. If you push something that is in orbit, it will not gently float away from earth. Instead, the only thing that happens is that the orbit will be slightly altered. To be precise, the highest altitude of the orbit will become slightly higher. And I do mean slightly. We're talking a few metres or so. The object will happily stay in almost the exact same orbit.
In order to push an out of orbit requires a massive amout of energy. I'm sure you can find the formulas on Wikipedia.:-)
Then you must be doing something wrong. I'd suggest you try running the 32-bit version of MPlayer. The whole point of AMD64 is that it can run 32-bit and 64-bit applications side by side.
Nobody? Without even mentioning the projects I have had direct influence in, and were in production years ago on 1.5, I'll just present you with one link as a counter-argument: Migration to Java 5 at walmart.com.
Most professional IT shops are just starting to roll new projects over to Websphere 6.0 which is based on J2SE 1.4 and J2EE 1.4. J2EE 1.5 is not even out the door yet, much less of any interest to people who do real work with Java.
Java EE is not Java SE. Don't take me wrong, I'm a huge fan of Java EE and I want JEE5 to make it as soon as possible. However, you can use 1.5 with previous versions of Java EE, and even if you don't even use many of the new language features or libraries, some 3'rd party library you use may very well be.
Third, there is no question the Sun VM is superior at the moment. But the key phrase in that sentence is "at the moment."
I believe that was my entire point of the previous post. The Sun VM is superiour at the moment. The main reason it is is because the others have to play a catchup game that they cannot win. Sun opening the license means that the alternative implementations may get a boost, and be able to actually implement the modern versions of Java instead of being stuck in the dark ages.
Five years ago Solaris wiped the floor with Linux. Today I don't see people flocking to Solaris despite its handful of technological perks. Linux is just too damn handy.
Solaris still wipes the floor with Linux, but quality has never been the main reason people choose a technology. Convenience and lazyness are often much more important. I myself prefer to run Linux on a desktop even thugh all my servers run Solaris. Why? It's certainly not because Linux is a technologically better platform, it's because it's much more conventient. All the desktop hardware drivers are there and all the end user applications just work.
There are realtime versions, secure versions, embedded versions. All based on the same kernel, all free and open, and they all just work.
There is not really a huge advantage to run the same kernel everywhere. Especially not when the API's are very similar as is the case of Linux and Solaris.
On the Java side the VM is even less important since you don't even need to recompile your binaries. The argument that, say, SableVM would take over on the server just because they have an embedded version just doesn't make any sense. There are no visible differences between two competing, certified, versions of Java. However, if SableVM manages to come out with a certificed, compatible version that wipes the floor with the Sun VM on the server, then why wouldn't people use it? However, right now they can't because they're stuck trying to catch up with Sun who are always 2 versions ahead.
To make a relevant comparison, you can talk about how ICC optimizes this and that in such an elegant way that it's 100x faster than GCC for this specific use.
It doesn't. It's a few percent faster. Not usually niceable unless you hit some very specific edge cases. GCC is quite decent on Intel hardware. Thies goes back to the onvenience argument I made earlier. Technological advantages are usually not the major deciding factor.
And if you've been following the open source movement the same thing is happening at Debian and RedHat. They are not targeting Sun's Java 1.5. They are targeting SableVM, GCJ, and GNU Classpath.
Most Java projects doesn't care one bit what the Linux distributions target. They would never deploy on anything but the Sun VM anyway.
And I think you are giving the Open Source alternate implementations of Java a little more credit than they deserver.
The fact of the matter is that they for the most part suck. As you mention yourself, they are only now close to becoming 1.4 compatible. The problem, of course, is that 1.5 was a huge improvement over 1.4 and it came out over 3 years ago. 1.6 is in beta 2 and will be released soon.
You can spend a lot of time discussing performance comparisons between the different VM's like SableVM, but that's not really interesting. It doesn't really matter which "free" VM you use, you still don't have a modern class library available until Sun releases theirs. That is why an open sourced version of Java is interesting for these parties.
Personally, I think the Sun VM is fantastic, but giving the "free" alternatives the ability to use the same class library will only increase competition and that is good for everybody. Today, they are playing the catchup game, and that must be really boring, since no one that really matters actually use their product for anything important.
There are ground-based telescopes that produces much better pictures than what Hubble can produce these days. I believe that the choice to abandon it may very well simply be a result of some simple maths. The same scientific results can be had cheaper by using the VLT.
Here's an interesting quote from the Wikipedia article:
The VLTs are equipped with a large set of instruments permitting observations to be performed from the near-UV to the mid-IR (ie a large fraction of the light wavelengths accessible from the surface of the Earth), with the full range of techniques including high-resolution spectroscopy, multi-object spectroscopy, imaging, and high-resolution imaging. In particular, the VLT has several Adaptive optics systems, which at infrared wavelengths correct for the effects of the atmospheric turbulence, providing images almost as sharp as if the telescope was in space. In the near-IR, the Adaptive Optics images of the VLT are up to 3 times sharper than those of the HST, and the spectroscopic resolution is many times better than Hubble. The VLTs are noted for their high level of observing efficiency and automation.
Slashdot Mirror
I don't mind that at all. That's actually a very decent way of implementing it. However, most boards that I have looked at does allow editing at any time, even years after writing the post.
Especially on Slashdot this would be a total disaster (and has been elsewhere already). Typical troll:
- Troll posts comment: "Microsoft are the good guys"
- Baited user replies: "No, they're monopolists!"
- Troll changes OP to: "Ubuntu are the good guys"
Public debate is founded upon the idea that when you say something, that thing has been said, and the content of the forum (or comments section) is a public record of what was said. When that is no longer true, anything you say can be taken out of context. And as a poster, I prefer it when that can't happen.Of course, that means that no short URL's handled by this service can be accessed anymore.
I don't know about the other operating systems, but TOS was definitely written in C. It was compiled using Mark Williams C.
It's a big story for companies who actually want to run Solaris on IBM hardware. So far it has been difficult for them to get support. When you pay 100k USD for a server, you expect to have full support for the operating system you intend to run on it. So far, IBM has been unable to do this for Solaris. Them doing it now is a big deal. Not technically, but from the business side of things.
Just because you don't know about them, doesn't mean they don't exist.
However, as far as I understand, this ruling means that Linux is in the clear, even if SCO would win, since even if it is concluded that IBM violated their contract by using UNIX code (code from AIX, written by IBM, mind you) in Linux, this code would not be considered "secret" or "protected" since SCO didn't own it in the first place.
No, they couldn't. ZFS is 100% Sun's code, and the "derivative ownership" theory was already (is already being) sunk in the SCO vs. IBM case.
I was referring to the "fixed priority scheduleing class" btw. :-) But yeah, you're right in what you said.
I know how the default Solaris scheduler works and yes, it is vulnerable to this. However, I'm not so sure it's really a problem. I suppose it can become a problem for systems where you have a lot of users sharing the CPU, but other than that it's really a non-issue in most cases.
Perhaps Sun should ship a specific scheduling class that can be used for untrusted processes (although I suppose FIXED can somewhat fulfill this requirement).
If you use Solaris, the top replacement "prstat" has a flag -m that enables microstate accounting. This will give you the exact CPU time used, and not an estimate.
If you want to go further, you can use DTrace, which allows you to monitor in detail exactly what is going on. This is also unaffected by any tricks played by the process.
Well, another solution is to use ZFS.
The problem with a "traditional" layered model is that the file system has to assume that the underlying storage device is a single consistent unit of storage, where a single write either succeeds, or it fails (in which case the data you wrote may or may not have been written). This all sounds very good and file systems like ext2 are written based on this assumtion.
However, if the underlying storage system is RAID5, and there is a power loss during the write, the entire stripe can become corrupt (read the Wikipedia article on the subject for more information). The file system can't solve this problem because it has no knowledge about the underlying storage stucture.
ZFS solves this problem in two ways, both of which reuires the storage model to be part of the filesystem:
- Each physical write never overwrites "live" data on the disk. It writes the stripe to a new location, and once it's been completely committed to disk the old data is marked as free.
- ZFS uses variable stripe width, so that it does not have to write larger stripes than nescessary. In other words, a large write can be directly translated to a write to a large stripe on the sotrage system, and a smaller write can use a smaller stripe width. This can improve performance since it can reduce the amount of data written.
There are plenty of other areas where this integration is needed, including snapshotting, but I hope the above explanation explains that the layered model is not always good.Try connecting a BR player to your HD TV and watch a good quality BR movie. Then you'll see a huge difference.
64-bit is not a magic wand that will make your apps run faster. In fact, 64-bit usually makes an app run slower, although this is not so clear-cut in the case of the x64, since you also get a larger register set which improves things.
However, the point is that there is no visible advantage of running Firefox in 64-bit. If it's using over 4 GB of ram already, then you might ihave some other problems. :-)
Are you running Linux on an Itanium? Then you might have problems with the lack of Flash. However, it's likely you have an x64-based machine, and I'm happy to tell you that the x64 architecture has not problems whatsoever running 32-bit applications , even side-by-side with the 64-bit ones. Just make sure you have all the 32-bit libraries installed and it'll work perfectly.
Do you realise that the hardware in this phone is identical to the Nokia E61?
The major difference between these two models (apart from the frequencies and those things) is that the WLAN (802.11g) support is disabled on the E62. I'll let you speculate why that is.
I have an E61. I also have an unlimited 3G data plan with my provider. I can use Fring to make Skype voice calls over the data connection, either using 3G or WLAN.
Now, ask yourself the following: Why is this impossible to do in the US, when it's possible in most of the rest of the world?
Disclaimer: I speak Swedish, not Norwegian.
If you want to learn more about how it works, and have a lot of fun at the same time, I can recommend that you play around with Orbiter. It really helped me understand for the first time exactly how it works (and also how wrong it is to call the place where the ISS is "space". :-) ).
Your suggestion is good, except for the fact that it shows that you don't know orbital mechanics and therefor will not work at all. A common misconception seems to be that an object in orbit is not affected by the earth's gravity. Nothing could be further from the truth. If you push something that is in orbit, it will not gently float away from earth. Instead, the only thing that happens is that the orbit will be slightly altered. To be precise, the highest altitude of the orbit will become slightly higher. And I do mean slightly. We're talking a few metres or so. The object will happily stay in almost the exact same orbit. In order to push an out of orbit requires a massive amout of energy. I'm sure you can find the formulas on Wikipedia. :-)
Then you must be doing something wrong. I'd suggest you try running the 32-bit version of MPlayer. The whole point of AMD64 is that it can run 32-bit and 64-bit applications side by side.
The fact of the matter is that they for the most part suck. As you mention yourself, they are only now close to becoming 1.4 compatible. The problem, of course, is that 1.5 was a huge improvement over 1.4 and it came out over 3 years ago. 1.6 is in beta 2 and will be released soon.
You can spend a lot of time discussing performance comparisons between the different VM's like SableVM, but that's not really interesting. It doesn't really matter which "free" VM you use, you still don't have a modern class library available until Sun releases theirs. That is why an open sourced version of Java is interesting for these parties.
Personally, I think the Sun VM is fantastic, but giving the "free" alternatives the ability to use the same class library will only increase competition and that is good for everybody. Today, they are playing the catchup game, and that must be really boring, since no one that really matters actually use their product for anything important.