I still run Gnome 2.6 on my Celeron 400MHz desktop, with 64M of RAM. Sure it swaps a bit now and then, but on the whole it still behaves rather snappy. In fact, with the new Nautilus, it is much faster than it used to be.
Same story on my PII 300MHz laptop, which has slightly more RAM at 192M...
The Linux Netfilter packet filter has support to filter non-AH or non-ESP packets however you'd like them to be treated. With FreeS/WAN, you can make certain IPs behind your DHCP server available for tunneling, and discard anything else, or anyone without a proper RSA key.
You can patch FreeS/WAN to use x509 certificates if you wish.
Correct, IPsec can also use a PSK (pre-shared key) so could also be vunerable to that kind of peer snooping. However, RSA is the "recommended" method of operation.
This is a very useful application of IPsec. The wavesec project is an example of using IPsec to secure the link between a client and the wireless access point.
This was in-practice last year at OLS where the FreeS/WAN folks set up a wavesec encrypted link, while the folks that were not using wavesec had their traffic snooped and displayed on a monitor.
The problem with using IPsec as a replacement for WEP, however, is that IPsec is higher up on the OSI layer diagram, so more information is left unencrypted than when using WEP (yes, I'm aware that WEP is weak and in this case, won't make a difference, I'm just illustrating a point.)
my god, just let the piracy tools die. who cares, they mean nothing in the grand scheme of things.
if they keep reassigning blame like they are doing right now, guess what is next. networks that do not offer any possibility for security, since they will have to make sure no "piracy" can be done on them. after that? secure computers and hardware that prevent you from doing anything the MPAA doesn't want.
they are playing right into the MPAA's hands, as this is exactly what they want.
I'm fully aware of this, but so much as changing a single line of code to read Copyright lindows, in conjunction with the KDE code, would violate the license should source not be distributed.
It would also appear that I am incorrect about mp3.com going bankrupt. My bad.
It doesn't just "look" like KDE, it _IS_ kde. Not only that but their "Windows Compability" shim is just Wine.
So... KDE is GPL'd, and is an integral part of Lindows. Lindows is propreitary, but incorporates binary GPL components. So, this means that Lindows code must also be licensed under the GPL or a GPL-compatible license.
Last I checked, Lindows wasn't providing anything but a 99$ one-seat binary. Hrm.....
No wonder mp3.com went bankrupt, the CEO is a nutjob who thinks he can take peoples things for free.
In the interest of authentication, perhaps this would be a good thing. If more people used digital signatures, more people would likely find it easier to begin using encryption as well. NAI might be kicking themselves over selling off its PGP division after all. How do you know if the bill you got by email is really from your VISA company, and not from Evil Eve the Eavesdropper?
Most government officials would likely right this off as paranoia, and unnecessary because *nobody* would EVER want to wiretap its citizens and steal their credit card information.
What the United States Government, and many governments throughout the world do not realize is how easy it is to access good cryptography. There is a wealth of information about the subject online, on websites beyond the reach of American legislature, in printed books, and in the minds of foreign cryptographers.
Besides, all a terrorist would need is one fairly competant programmer who has a bone to pick with $country, and they would have access to all the crypto they want, taken from books. Unless they plan on burning them all.
I remember an old quote about, "if you ban guns, only the criminals will have them." This would seem to be the case here, you can't stop a criminal from using strong crypto.
I really hope that the American lawmakers think long and hard about this, and don't use this attack as a scapegoat for stealing fundamental freedoms, such as privacy. I also hope that Canada doesn't adopt a DMCA-like law, such as the one it is currently considering.
I can understand how this would be implemented on a web-based mail system, since you are actually *composing* the message on their server, using whatever script/component they are running.
However, if this were to be implemented on an ISP level, by adding advertisements to outgoing email messages, I would suggest you add an X-Copyright header to your mail! This coupled with using PGP or GnuPG, and cryptographically signing your email would enable the receiver to see if the mail had been tampered with (the message hash would have changed, and the authentication would fail) and you could attack the ISP for invasion of privacy or mail tampering.
This greatly disturbs me for many reasons. The commercialisation of the Internet will soon reach its peak, and dreadfully our entire desktops will be filled with gigantic advertisements promoting pornography or silly little trinkets. As if this wasn't bad enough our emails would be full of tags like " WIN WIN WIN 10000$ WIN WIN WIN "
Fight now, your desktop might be too clogged to fight later!
My question for Apple's legal department is how can they be justified for a person emulating the appearance of the environment. If it was emulating the functionality of OSX I could better understand they're claims here, but get real.
I guess this means they are suing because they think users may be persuaded to use the theme instead of buying OSX. So this proves it true, Apple users are, in general, buying it for it's fruity appearance and not for it's preformance.
From the HelixCode site:
" In addition to allowing the user to keep track of his appointments, deadlines and task lists, it will also allow distributed appointment
scheduling using the iCalendar Internet standard protocol, and interoperate with most other existing calendaring systems. It will also allow sychronizing with PalmOS-based organizers."
Evolution is part of the GNOME project and is being developed by Helix, Inc. It will be integrated into the next Gnome release due out early 2001. You can download a beta right now or add deb ftp://ftp.helixcode.com/helix/evolution/distributi ons/Debian/./, to your Debian sources list to fetch it. Be warned, is is under heavy development and requires many dependancies that are still under heavy work
The Debian GNU/Hurd team and the FSF have been working rather hard as of late.
As reported in the Debian Weekly News for October 18, Philip Charles from Copyleft in New Zealand has created two cdimages for a Debian GNU/Hurd distribution. One for the main packages and the other for non-free.
http://lists.debian.org/debian-cd-0010/msg00030.ht ml
funny. knoppix does just that, and doesn't rely on crappy floppy drives.
and buy a new bloody hard disk. it would be far cheaper to buy a new laptop hard disk, than a 512M of usb storage. christ.
I think you mean any x86 Linux machine. No other architectures are effected, obviously.
I still run Gnome 2.6 on my Celeron 400MHz desktop, with 64M of RAM. Sure it swaps a bit now and then, but on the whole it still behaves rather snappy. In fact, with the new Nautilus, it is much faster than it used to be.
Same story on my PII 300MHz laptop, which has slightly more RAM at 192M...
I don't see any problem with Gnome on either...
iirc, the Pentium M was designed at Intel's Israeli division, so this makes some sense compared to the old Washington/Oregon naming scheme.
The Linux Netfilter packet filter has support to filter non-AH or non-ESP packets however you'd like them to be treated. With FreeS/WAN, you can make certain IPs behind your DHCP server available for tunneling, and discard anything else, or anyone without a proper RSA key.
You can patch FreeS/WAN to use x509 certificates if you wish.
Correct, IPsec can also use a PSK (pre-shared key) so could also be vunerable to that kind of peer snooping. However, RSA is the "recommended" method of operation.
This is a very useful application of IPsec. The wavesec project is an example of using IPsec to secure the link between a client and the wireless access point.
This was in-practice last year at OLS where the FreeS/WAN folks set up a wavesec encrypted link, while the folks that were not using wavesec had their traffic snooped and displayed on a monitor.
The problem with using IPsec as a replacement for WEP, however, is that IPsec is higher up on the OSI layer diagram, so more information is left unencrypted than when using WEP (yes, I'm aware that WEP is weak and in this case, won't make a difference, I'm just illustrating a point.)
my god, just let the piracy tools die. who cares, they mean nothing in the grand scheme of things.
if they keep reassigning blame like they are doing right now, guess what is next. networks that do not offer any possibility for security, since they will have to make sure no "piracy" can be done on them. after that? secure computers and hardware that prevent you from doing anything the MPAA doesn't want.
they are playing right into the MPAA's hands, as this is exactly what they want.
I'm fully aware of this, but so much as changing a single line of code to read Copyright lindows, in conjunction with the KDE code, would violate the license should source not be distributed.
It would also appear that I am incorrect about mp3.com going bankrupt. My bad.
It doesn't just "look" like KDE, it _IS_ kde. Not only that but their "Windows Compability" shim is just Wine.
So... KDE is GPL'd, and is an integral part of Lindows. Lindows is propreitary, but incorporates binary GPL components. So, this means that Lindows code must also be licensed under the GPL or a GPL-compatible license.
Last I checked, Lindows wasn't providing anything but a 99$ one-seat binary. Hrm.....
No wonder mp3.com went bankrupt, the CEO is a nutjob who thinks he can take peoples things for free.
In the interest of authentication, perhaps this would be a good thing. If more people used digital signatures, more people would likely find it easier to begin using encryption as well. NAI might be kicking themselves over selling off its PGP division after all. How do you know if the bill you got by email is really from your VISA company, and not from Evil Eve the Eavesdropper?
Most government officials would likely right this off as paranoia, and unnecessary because *nobody* would EVER want to wiretap its citizens and steal their credit card information.
What the United States Government, and many governments throughout the world do not realize is how easy it is to access good cryptography. There is a wealth of information about the subject online, on websites beyond the reach of American legislature, in printed books, and in the minds of foreign cryptographers.
Besides, all a terrorist would need is one fairly competant programmer who has a bone to pick with $country, and they would have access to all the crypto they want, taken from books. Unless they plan on burning them all.
I remember an old quote about, "if you ban guns, only the criminals will have them." This would seem to be the case here, you can't stop a criminal from using strong crypto.
I really hope that the American lawmakers think long and hard about this, and don't use this attack as a scapegoat for stealing fundamental freedoms, such as privacy. I also hope that Canada doesn't adopt a DMCA-like law, such as the one it is currently considering.
I can understand how this would be implemented on a web-based mail system, since you are actually *composing* the message on their server, using whatever script/component they are running.
However, if this were to be implemented on an ISP level, by adding advertisements to outgoing email messages, I would suggest you add an X-Copyright header to your mail! This coupled with using PGP or GnuPG, and cryptographically signing your email would enable the receiver to see if the mail had been tampered with (the message hash would have changed, and the authentication would fail) and you could attack the ISP for invasion of privacy or mail tampering.
This greatly disturbs me for many reasons. The commercialisation of the Internet will soon reach its peak, and dreadfully our entire desktops will be filled with gigantic advertisements promoting pornography or silly little trinkets. As if this wasn't bad enough our emails would be full of tags like " WIN WIN WIN 10000$ WIN WIN WIN "
Fight now, your desktop might be too clogged to fight later!
May the source be with you.
My question for Apple's legal department is how can they be justified for a person emulating the appearance of the environment. If it was emulating the functionality of OSX I could better understand they're claims here, but get real.
I guess this means they are suing because they think users may be persuaded to use the theme instead of buying OSX. So this proves it true, Apple users are, in general, buying it for it's fruity appearance and not for it's preformance.
Dude, its GNU software, its FREE. Licensed under GPLv2 for you to copy/modify/distribute and so forth.
From the HelixCode site:
:)
" In addition to allowing the user to keep track of his appointments, deadlines and task lists, it will also allow distributed appointment scheduling using the iCalendar Internet standard protocol, and interoperate with most other existing calendaring systems. It will also allow sychronizing with PalmOS-based organizers."
Evolution is also iCal Compliant
Evolution
i ons/Debian/ ./, to your Debian sources list to fetch it. Be warned, is is under heavy development and requires many dependancies that are still under heavy work
Evolution is part of the GNOME project and is being developed by Helix, Inc. It will be integrated into the next Gnome release due out early 2001. You can download a beta right now or add deb ftp://ftp.helixcode.com/helix/evolution/distribut
The Debian GNU/Hurd team and the FSF have been working rather hard as of late.
t ml
As reported in the Debian Weekly News for October 18, Philip Charles from Copyleft in New Zealand has created two cdimages for a Debian GNU/Hurd distribution. One for the main packages and the other for non-free.
http://lists.debian.org/debian-cd-0010/msg00030.h