Then you have to encrypt the removable device... and the computers swap, so the data doesn't get written to swap... and all temp directories any app might use... and the caches... pretty much you're encrypting everything anyways.
Awww! Poor 7 digiter is upset by OSS? Enjoy your Windows (you should probably not use the internet though, most versions of Windows uses FreeBSD's network stack)!
Possibly one day while using the required IE to get information online, he was going to somesite.org, but accidentally typed someste.org which could infect the system through IE, and if they were sneaky could just forward you to somesite.org so you wouldn't even notice you went to a bad site.
Just a day after the release of 3.5.5, developers say they are already looking toward the release of KDE4...
I'm not an expert on grammar so I may have misread the summary myself, but KDE 4 has actually been being developed for a good while now. Pretty much all of KDE has been ported to using Qt4, DBus has replaced DCOP, etc. Lots of work on the new frameworks in KDE4 has also being accomplished, as well as improvements to the already existing ones as well.
This is most useful for software that DOESN'T use the Distribution's package management software (primarily closed source software/commercial OSS software).
For KDE you can run 'kde-config --prefix' to find out where KDE is installed, so instead of writing '/opt/kde' you could put '`kde-config --prefix`' which would then replace it with where KDE is installed into. Also Portland's goal is to help solve some of those problems (not by standardizing the locations, but by giving you tools where you don't need to know the locations).
Applications already work in either environment. Portland's goal is to make it even EASIER for the developers to make apps that work in ANY *nix environment.
If you could simply do that, then having drivers signed seems like it would be absolutely meaningless, since if its like a rootkit, they already CAN run code on the machine, so should be able to install whatever certs they want. It would become as meaningless as how it is in XP right now, where the installer will automatically click 'allow' on the popup asking you to confirm allowing the driver to be installed.
I believe all the Core 2 chips support Vanderpool already, and from AMD all the AM2 socket using chip support Pacifica IIRC. Though the IOMMU thats going to be in future AMD chips is what will REALLY help virtualization (i.e. so unmodified drivers can use DMA without any risk of breaking out of the VM).
GTalk HAS voice and video. Also GTalk supports Server-to-Server, and has for a good while now. Also Jabber (and the GTalk server) won't be able to replace AIM/MSN/Yahoo if people refuse to ever use it because theres not enough people to completely replace all the others.
Also I use AIM network (with the GAIM client, I wouldn't touch the official client with a 10 foot pole) and don't believe I have ever had a message filtered before.
1) Debian doesn't want to use the offical patch system (i.e wait on Linux's update approval process, etc.)
2) a user on a Debian system not knowing this goes to Linux IRC with a Linux problem (this has already happened)
3) No one can solve the Bug... only to find it is an unofficial patch made or nto made by Debian
4) User complains that Linux sucks because its not the same across systems
5) Brand is tarnished
6) Rinse. Repeat.
If you don't want to follow the guidelines, and follow your own way of doing things... change the name, or risk damaging the whole projects reputation. If I know Linux works a certain way, I go to a new system and something doesn't work quite right, well guess what I'm not going to be happy. It's starts with the logo... but where does it end?
It's fine when the Linux kernel is modified and distributed, as well as Gnome and KDE, but not Firefox once the Mozilla Corporation notices (it was fine with the Mozilla Foundation previously). Also Mozilla often doesn't support the version of Firefox that ships with Debian stable anymore (so Debian HAS TO either back port security updates, leave the users with an unsecure system, or break stable by making major updates).
That means Debian also doesn't use the Linux kernel by that logic! Neither does pretty much any Linux distro released! All of them (at least the at all major ones) patch the kernel, often a MASSIVE amount!
Actually the Linux kernel is forked all the time, and is generally changed far more than any distro changes Firefox. Most every single Linux distro out there doesn't ship the vanilla Linux kernel as released by Linus. Debian, Fedora, RHEL, Gentoo, SuSE, Mandrake, Ubuntu, Knoppix, Linspire, etc all ship modified (sometimes VERY modified, on an old version of RHEL when they were still using 2.4, they back ported LOADS of patches from 2.6) versions of the Linux kernel.
Linux is a registered trademark of Linus Torvalds, though hes never told Debian, Fedora Project, Ubuntu, Gentoo, RedHat, Linspire, Xandros, SuSE, that they couldn't ship a patched kernel and still call it Linux (pretty much every Linux distro adds patches to the kernel they ship).
Previously the Mozilla Foundation said it was perfectly fine for Debian to release a patched version of Firefox and to keep the name, and to use the non-official artwork (the artwork that appears if you don't run make with the --enable-official-branding switch), but out of the blue the new Mozilla Corporation decided they don't want Debian to modify Firefox at ALL and be able to keep the name (unless they submit all patches to MC to have them 'approved' for their Debian's release, the problem with that is that when Debian backports security updates they wouldn't be able to release the fixed packages ASAP, they would have to wait around for the Mozilla Corporation to get around to checking it and letting them).
Slashdot Mirror
WebKit is actually free software. WebKit is Apple's fork of KHTML (Konqueror's and KDE's rendering engine).
A lot of the Mozilla developers AREN'T volunteers, they work for the Mozilla Corporation/Foundation.
So Hemos now kisses his own ass?
Then you have to encrypt the removable device... and the computers swap, so the data doesn't get written to swap... and all temp directories any app might use... and the caches... pretty much you're encrypting everything anyways.
RTFS, it was mentioned if you actually read anything more than the headline.
Awww! Poor 7 digiter is upset by OSS? Enjoy your Windows (you should probably not use the internet though, most versions of Windows uses FreeBSD's network stack)!
Possibly one day while using the required IE to get information online, he was going to somesite.org, but accidentally typed someste.org which could infect the system through IE, and if they were sneaky could just forward you to somesite.org so you wouldn't even notice you went to a bad site.
I'm not an expert on grammar so I may have misread the summary myself, but KDE 4 has actually been being developed for a good while now. Pretty much all of KDE has been ported to using Qt4, DBus has replaced DCOP, etc. Lots of work on the new frameworks in KDE4 has also being accomplished, as well as improvements to the already existing ones as well.
This is most useful for software that DOESN'T use the Distribution's package management software (primarily closed source software/commercial OSS software).
Guess whats drawing the widgets in your browser? Yeah, thats right, Gtk or Qt!
For KDE you can run 'kde-config --prefix' to find out where KDE is installed, so instead of writing '/opt/kde' you could put '`kde-config --prefix`' which would then replace it with where KDE is installed into. Also Portland's goal is to help solve some of those problems (not by standardizing the locations, but by giving you tools where you don't need to know the locations).
Applications already work in either environment. Portland's goal is to make it even EASIER for the developers to make apps that work in ANY *nix environment.
"download 100MB of Java to run a simple bittorrent app"
Azureus?
"55MB of Mono runtime to use an ID3 tag editor"
Banshee? (ignore the media playing part, please)
"30 Python libraries for the volume control dial"
Uh... Ok not a clue on this one.
If you could simply do that, then having drivers signed seems like it would be absolutely meaningless, since if its like a rootkit, they already CAN run code on the machine, so should be able to install whatever certs they want. It would become as meaningless as how it is in XP right now, where the installer will automatically click 'allow' on the popup asking you to confirm allowing the driver to be installed.
I believe all the Core 2 chips support Vanderpool already, and from AMD all the AM2 socket using chip support Pacifica IIRC. Though the IOMMU thats going to be in future AMD chips is what will REALLY help virtualization (i.e. so unmodified drivers can use DMA without any risk of breaking out of the VM).
Actually the story DID make Slashdot when his wife first disappeared.
All the holes already existed, and were searchable using other code search engines. This blogger didn't magically create them.
GTalk HAS voice and video. Also GTalk supports Server-to-Server, and has for a good while now. Also Jabber (and the GTalk server) won't be able to replace AIM/MSN/Yahoo if people refuse to ever use it because theres not enough people to completely replace all the others.
Also I use AIM network (with the GAIM client, I wouldn't touch the official client with a 10 foot pole) and don't believe I have ever had a message filtered before.
1) Debian doesn't want to use the offical patch system (i.e wait on Linux's update approval process, etc.)
2) a user on a Debian system not knowing this goes to Linux IRC with a Linux problem (this has already happened)
3) No one can solve the Bug... only to find it is an unofficial patch made or nto made by Debian
4) User complains that Linux sucks because its not the same across systems
5) Brand is tarnished
6) Rinse. Repeat.
If you don't want to follow the guidelines, and follow your own way of doing things... change the name, or risk damaging the whole projects reputation. If I know Linux works a certain way, I go to a new system and something doesn't work quite right, well guess what I'm not going to be happy. It's starts with the logo... but where does it end?
It's fine when the Linux kernel is modified and distributed, as well as Gnome and KDE, but not Firefox once the Mozilla Corporation notices (it was fine with the Mozilla Foundation previously). Also Mozilla often doesn't support the version of Firefox that ships with Debian stable anymore (so Debian HAS TO either back port security updates, leave the users with an unsecure system, or break stable by making major updates).
The Mozilla Corporation wants more control. Thats what this is all about.
That means Debian also doesn't use the Linux kernel by that logic! Neither does pretty much any Linux distro released! All of them (at least the at all major ones) patch the kernel, often a MASSIVE amount!
Actually the Linux kernel is forked all the time, and is generally changed far more than any distro changes Firefox. Most every single Linux distro out there doesn't ship the vanilla Linux kernel as released by Linus. Debian, Fedora, RHEL, Gentoo, SuSE, Mandrake, Ubuntu, Knoppix, Linspire, etc all ship modified (sometimes VERY modified, on an old version of RHEL when they were still using 2.4, they back ported LOADS of patches from 2.6) versions of the Linux kernel.
Forks can be re-merged. A fork is simply a split in the code base. Learn your terminology.
Linux is a registered trademark of Linus Torvalds, though hes never told Debian, Fedora Project, Ubuntu, Gentoo, RedHat, Linspire, Xandros, SuSE, that they couldn't ship a patched kernel and still call it Linux (pretty much every Linux distro adds patches to the kernel they ship).
Previously the Mozilla Foundation said it was perfectly fine for Debian to release a patched version of Firefox and to keep the name, and to use the non-official artwork (the artwork that appears if you don't run make with the --enable-official-branding switch), but out of the blue the new Mozilla Corporation decided they don't want Debian to modify Firefox at ALL and be able to keep the name (unless they submit all patches to MC to have them 'approved' for their Debian's release, the problem with that is that when Debian backports security updates they wouldn't be able to release the fixed packages ASAP, they would have to wait around for the Mozilla Corporation to get around to checking it and letting them).