"The X server traditionally runs as root. You are likely unaware of this because it's started automatically as part of the init process." On many systems it's started by init, but that's not the reason it has root, it has root because the X-binary has setuid bits set.
Not only that, people will just buy a new computer if they are really stupid and it will just be an other sale for Microsoft, then again this was asia...
It should be considered a failure of the part of the computer industry I'm sorry, but no1 wants to take that responsability, not even Microsoft unfortunately.
And on the Linux-situation, if Linux is better, it might have been able to prevent anything else but the user home-directory being destroyed.
Also I've not seen any unpatched Linux desktops (not including the stupid distributions which were on the first Netbooks).
A periodic rsync copy (with history) is much better for keeping your data, accidental deletion or overwritten partition tables happen very easily, no RIAD system will save your 'ass'.
Preferable you keep the copy on an other machine, different UPS or surge protector and not in the same machine, hanging on the same PSU. Even better is to copy it to a remote place.
With current bandwidth 'limits', it's possible a good idea to keep it somewhere else.
Also all wireless standard have been cracked. If I remember correctly you can send 1GB of wireless packets to Russia and they have a cluster of machines with lots of NVidia GPU's which will 'recover your key' for you in a week time for just a few 1000 dollars. On the fiber side of things you have very advanced systems that can even detect if a fiber has been cut or light deflected and resend. And fiber also can go up to 100 Gbit ethernet. I guess fiber might not be such an obvious choice your phone though, maybe cat5 or 6 might be more appropriate ? DECT is also usually not properly encrypted and easily broken if I'm not mistaken.
I'd be happy if people stop using IE6 or even IE7, I'd prefer if they switch to something better then IE in the process, but I guess that's asking for to much.
Further, you must bear in mind that Munich is a pioneer in even attempting to replace a major Microsoft based infrastructure with open source software. They are having to to do everything from scratch, which I'm sure increases the cost.
That's what you'd call an early adoptor, they usually pay more, but definitly in this case, everyone, especially the other german government agencies that will adopt it too, will benefit.
This is about patching the kernel, it usually doesn't need to change the kernel structures, but it changes the functions. So it put the new function in kernel space and changes a pointer to the function. When doing this it temporarily slows down the kernel and calls the same function as is done when loading a module. That's what I think it does, but if you must know, read the PDF: http://www.ksplice.com/doc/ksplice.pdf
For all those that think this company is doomed because they released all their code as open source, let me tell you that they released the automated tooling, but the automated tooling could in the time they tested it (from the article last year) 'only' handle 84% of the time. All the other times, on average about 17 lines of code needed to be written.
I think it would be cool if the distribution makers actually paid this company to do these patches for the distribution-kernels. Although I guess that means something like Debian may be left out ? Then again, a little more then 80% isn't bad either.;-) And I think I've read on lwn.net they have actually improved on that number in the past year, but I'm not sure. Anyway we also have kexec to shorted the reboot time.
There are widespread hopes of using lithium ion batteries in electric vehicles, but one study concluded that "realistically achievable lithium carbonate production will be sufficient for only a small fraction of future PHEV and EV global market requirements", that "demand from the portable electronics sector will absorb much of the planned production increases in the next decade", and that "mass production of lithium carbonate is not environmentally sound, it will cause irreparable ecological damage to ecosystems that should be protected and that LiIon propulsion is incompatible with the notion of the 'Green Car'".
Have a look at the Firefox Perspectives add-on, it's meant for telling you when a self-signed cert changes, but can also be configured for use with normal certs.
I guess we all need xusername users so everyone has a seperate user to run X. ;-)
"The X server traditionally runs as root. You are likely unaware of this because it's started automatically as part of the init process." On many systems it's started by init, but that's not the reason it has root, it has root because the X-binary has setuid bits set.
Not only that, people will just buy a new computer if they are really stupid and it will just be an other sale for Microsoft, then again this was asia...
It should be considered a failure of the part of the computer industry I'm sorry, but no1 wants to take that responsability, not even Microsoft unfortunately.
And on the Linux-situation, if Linux is better, it might have been able to prevent anything else but the user home-directory being destroyed.
Also I've not seen any unpatched Linux desktops (not including the stupid distributions which were on the first Netbooks).
I don't think the US Military is the big problem, it's the driving on public roads that will get you frowned upon.
I think he meant to say European contries.
Doing standard properly isn't in Microsofts best interrest.
RAID 1 hopefully prevents that a server will go down and it makes it possible to easily replace a bad disk.
A periodic rsync copy (with history) is much better for keeping your data, accidental deletion or overwritten partition tables happen very easily, no RIAD system will save your 'ass'.
Preferable you keep the copy on an other machine, different UPS or surge protector and not in the same machine, hanging on the same PSU. Even better is to copy it to a remote place.
With current bandwidth 'limits', it's possible a good idea to keep it somewhere else.
Also all wireless standard have been cracked. If I remember correctly you can send 1GB of wireless packets to Russia and they have a cluster of machines with lots of NVidia GPU's which will 'recover your key' for you in a week time for just a few 1000 dollars. On the fiber side of things you have very advanced systems that can even detect if a fiber has been cut or light deflected and resend. And fiber also can go up to 100 Gbit ethernet. I guess fiber might not be such an obvious choice your phone though, maybe cat5 or 6 might be more appropriate ? DECT is also usually not properly encrypted and easily broken if I'm not mistaken.
Enough ranting on wireless
And I heared it stinks
The last quote I've seen is, they sends out 20 milion messages for US $150.
That it hasn't happend, doesn't mean it's still possible, development of GIMP hasn't halted.
That doesn't mean there a other problems, a very good example:
http://blog.cr0.org/2009/05/write-once-own-everyone.html
Secure, yeah sure, adding more code doesn't make it more secure, you'll just have more security bugs:
http://kerneltrap.org/OpenBSD/Virtualization_Security
I'd be happy if people stop using IE6 or even IE7, I'd prefer if they switch to something better then IE in the process, but I guess that's asking for to much.
Further, you must bear in mind that Munich is a pioneer in even attempting to replace a major Microsoft based infrastructure with open source software. They are having to to do everything from scratch, which I'm sure increases the cost.
That's what you'd call an early adoptor, they usually pay more, but definitly in this case, everyone, especially the other german government agencies that will adopt it too, will benefit.
This is about patching the kernel, it usually doesn't need to change the kernel structures, but it changes the functions. So it put the new function in kernel space and changes a pointer to the function. When doing this it temporarily slows down the kernel and calls the same function as is done when loading a module. That's what I think it does, but if you must know, read the PDF: http://www.ksplice.com/doc/ksplice.pdf
For all those that think this company is doomed because they released all their code as open source, let me tell you that they released the automated tooling, but the automated tooling could in the time they tested it (from the article last year) 'only' handle 84% of the time. All the other times, on average about 17 lines of code needed to be written.
I think it would be cool if the distribution makers actually paid this company to do these patches for the distribution-kernels. Although I guess that means something like Debian may be left out ? Then again, a little more then 80% isn't bad either. ;-) And I think I've read on lwn.net they have actually improved on that number in the past year, but I'm not sure. Anyway we also have kexec to shorted the reboot time.
kexec is cool too, it's simple and it really saves a lot of time waiting.
The above is good for kernel patches, like security updates, etc. But not so much for new features, etc. So kexec is good for that.
Who ever said that ? I've never seen it mentioned anywhere that 7 is faster than XP.
Ohh, yeah that was taken from the Wikipedia article.
Is it just me, is isn't this such a good idea ?:
There are widespread hopes of using lithium ion batteries in electric vehicles, but one study concluded that "realistically achievable lithium carbonate production will be sufficient for only a small fraction of future PHEV and EV global market requirements", that "demand from the portable electronics sector will absorb much of the planned production increases in the next decade", and that "mass production of lithium carbonate is not environmentally sound, it will cause irreparable ecological damage to ecosystems that should be protected and that LiIon propulsion is incompatible with the notion of the 'Green Car'".
elegant yeah maybe, but definitely more efficient.
This is actually one of the things I'd love to see if DNSSEC actually does get going for real.
I'll love to be able to put SSH pub-keys and SSL(https) pub-keys in a verifiable DNS.
At this point tooling, etc. really needs to be improved if I'm going to implement DNSSEC on my domains.
The whole key-rollover stuff is still to complicated.
Have a look at the Firefox Perspectives add-on, it's meant for telling you when a self-signed cert changes, but can also be configured for use with normal certs.