RAM is very, very cheap now, less than £10 a gigabyte
This is a gross generalisation - that price is true only for small amounts of ram (a couple of gigabytes), where you talk about 1GB or 2GB sticks, and a mainboard with 4-6 slots.
Otherwise, please tell me how can I upgrade my computer from (let's say) 8GB to 128GB for only £120.
I went and started reading the article, but stopped at the first mention of the "file copy engine". If your OS is so complex that you need an "engine" - a dedicated software construct - for copying files, then... I guess this is the reason Vista must use so much space.
Furthermore,
The biggest change they made was to go back to using cached file I/O again for all file copies, both local and remote, with one exception [...] So basically it's faster because it's the old version, not because the new version is fixed.
I guess the end tells it all:
File copying is not as easy as it might first appear Tell that to all the 52k of/bin/dd (well, plus the kernel part, but still...).
At least the article was an enjoyable piece of literature.
I agree that you cannot justify the action of that person. My point was that on the other hand, a product that crashes due to spurious signals is broken, plain and simple.
If a device can be killed by "spurious malformed signals", then it's a piece of really broken hardware. I, as a customer, would be glad to learn that before buying it.
Possibly... but a keylogger/spyware/etc. program could very simply look for id_dsa or similarly named files... in which case I would call it smart but not targetted attack.
Anyway, it all depends on personal preference, but I regard the safety of my private key/passphrase as a very important thing.
Actually, as you access your key file from an untrusted computer, a keylogger in combination with another program could get both your passphrase and your private key.
Let's see:
- copy old/home/username dir
- "debconf-get-selections" on old computer and pipe to "debconf-set-selections" on new one
- "dpkg -l |grep ^ii" on old computer and replicate the package list
- go drink some tea while the apt-get proceeds
- done!
I carried my home dir with its settings across about three or four new computers in the last eight years or so, and I didn't have to tweak things very much. Only upgrading major components require some maintenance, but other than that, it's simple.
The article says syscalls, not function calls. The difference between calling models has no relation to syscalls, which are between userland and kernel space.
More likely, the article shows the difference between Apache and IIS, on one side, and the glibc and however-it's-called windows' base library, on the other side.
I think you are confusing the things a little: in 2.6, the kernel itself is preemptible, while user processes where always preemptible in Linux.
I mean, your definition is correct, but the big win in 2.6 is that processes can be preempted while being in a syscall (i.e. really the kernel runs), so it is wrong to suggest that previously (2.6) Linux had the same algorithm as Windows 3.x.
On Linux something like this is quite simple, as all the information is available in/proc/stat (with per-cpu information for SMP boxes). A driver for it would simply need to poll the value(s) of interest and output them to the serial port.:)
Slashdot Mirror
RAM is very, very cheap now, less than £10 a gigabyte
This is a gross generalisation - that price is true only for small amounts of ram (a couple of gigabytes), where you talk about 1GB or 2GB sticks, and a mainboard with 4-6 slots.
Otherwise, please tell me how can I upgrade my computer from (let's say) 8GB to 128GB for only £120.
regards,
iustin
Furthermore, The biggest change they made was to go back to using cached file I/O again for all file copies, both local and remote, with one exception [...] So basically it's faster because it's the old version, not because the new version is fixed.
I guess the end tells it all: File copying is not as easy as it might first appear Tell that to all the 52k of
At least the article was an enjoyable piece of literature.
I agree that you cannot justify the action of that person. My point was that on the other hand, a product that crashes due to spurious signals is broken, plain and simple.
If a device can be killed by "spurious malformed signals", then it's a piece of really broken hardware. I, as a customer, would be glad to learn that before buying it.
Possibly... but a keylogger/spyware/etc. program could very simply look for id_dsa or similarly named files... in which case I would call it smart but not targetted attack.
Anyway, it all depends on personal preference, but I regard the safety of my private key/passphrase as a very important thing.
Actually, as you access your key file from an untrusted computer, a keylogger in combination with another program could get both your passphrase and your private key.
Let's see: /home/username dir
- copy old
- "debconf-get-selections" on old computer and pipe to "debconf-set-selections" on new one
- "dpkg -l |grep ^ii" on old computer and replicate the package list
- go drink some tea while the apt-get proceeds
- done!
I carried my home dir with its settings across about three or four new computers in the last eight years or so, and I didn't have to tweak things very much. Only upgrading major components require some maintenance, but other than that, it's simple.
The article says syscalls, not function calls. The difference between calling models has no relation to syscalls, which are between userland and kernel space.
More likely, the article shows the difference between Apache and IIS, on one side, and the glibc and however-it's-called windows' base library, on the other side.
I think you are confusing the things a little: in 2.6, the kernel itself is preemptible, while user processes where always preemptible in Linux.
I mean, your definition is correct, but the big win in 2.6 is that processes can be preempted while being in a syscall (i.e. really the kernel runs), so it is wrong to suggest that previously (2.6) Linux had the same algorithm as Windows 3.x.
On Linux something like this is quite simple, as all the information is available in /proc/stat (with per-cpu information for SMP boxes). A driver for it would simply need to poll the value(s) of interest and output them to the serial port. :)