These devices are very widespread up here. Now, according to your level of paranoia, I should be fearful of walking in large crowds, in case someone is walking around with a reader, waves it by my pocket, and charges me $1500. That hasn't happened.
Of course not. The tag doesn't store your credit card info, it stores a unique identifier which is linked to you and your credit card info in Exxon-Mobil's (Esso's) database, so the unique identifier would be pretty worthless to a would-be thief. Unless they can make their own RFID chip... then they could get free gas and stick you with the bill, at least until you got a different SpeedPass wand from the oil company. (Don't laugh; I don't doubt that something like this is that far off, based on the fact that mag-stripe programmers aren't entirely uncommon.)
Once we have [ADV:] in every spam we get, we can modify SMTP servers to return "555 Advertisements not allowed" if one tries to send a spam and save some wasted bandwidth.
How would it save bandwidth? The Subject: header is considered content, and follows the DATA SMTP command. The server does not interrupt the client until the client sends "\n.\n", so how does that work?
Re:Do NOT stand in front of one, though....
on
Potato Bazookas
·
· Score: 1
Oh, there's a simpler way than that. We'd just use a Coleman lantern igniter. Just drill a hole in the combustion chamber and fit one in it. A quick twist and you've launched your spud.:)
While possible, installing programs without using 'official' packages throws away the benefits of using a RPM system in the first place, particularly it's ability to verify the integrity and compatibility of installed programs (which it's main point of superiority over Debian's package management system).
Hmm? Come again? I fail to see how rpm is superior to dpkg in verifying the 'compatibility' of installed programs -- that is to say, only as good as the packager. (Both tools only enforce what the packager said to do.) As far as integrity verification, simply apt-get install debsums.
As far as how long they support old releases... When they released potato, they dropped support for slink fairly quickly, within a couple of months I think. Since they released woody, they've kept up support for potato; potato packages are still included in the security announcements that are sent out. Woody's been out for what, about a year and a half now? I imagine potato support will be dropped at least by the time sarge is released, but that's pure speculation on my part.
I mean, the damage is already done. These were sale prices from a week ago. They got them removed. (Well, several big-name retailers did.) Then, they decide to give it a go to try to find out who did it. FatWallet showed some backbone, so Wal-Mart backed down and decided to cut their losses rather than have this go to court.
Pardon me, but I don't think that Wal-Mart's "seen the light" or become a good guy in this regard.
If someone set up a dedicated box for me, first thing I'd do is ssh in and change the root pass. Then you *know* they're not logging on.
To the contrary. They could have very well installed a trojaned/bin/login that grants root privileges with a secret username/password combination. Want to recompile the login package to prevent this? Maybe you can't even trust the compiler. Install a known-good binary package? Maybe you can't trust the package manager, for similar reasons.
She concluded that some penalties proposed by those states would chiefly benefit the company's rivals.
Well... okay. Isn't that what punishing a company and making an effort to restore competition usually does? How can you accomplish those two goals without bring benefit to the competitors?
According to the FAQ (and most people you'd ask today), KDE stands for "K Desktop Environment". However, the original Usenet post announcing the formation of the project refers to it as the "Kool Desktop Environment". A Google Groups search confirms this.
Microsoft probably won't put in any significant look and feel changes until much later in the testing program, probably someplace around beta 3. I'd say it's very likely they'll try and hold something impressive back until then, to help keep the hype machine cranking away.
Well, one thing to notice in the screenshots is in the Sidebar thingy on the right -- it looks like they have virtual desktops! That alone, IMO, is fairly big news.
you must, however, make the full source code available upon request to those who bought your product, and you are allowed to charge a reasonable fee for this service (which means, afaik, the copying and media cost, but not an added sales price)
Actually, section 3b of the GPL states that if you distribute binaries without the sourc, you must
Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.
The reason is found in the very next section, 3c, which states that you can fulfill your source code distribution obligation if you are distributing the binaries non-commercially if you choose to
Accompany it with the information you received as to the offer to distribute corresponding source code.
It's not distributed under any license. The author gives a simple permission statement: "Permission is hereby granted to copy and distribute this license without modification." This is similar to the permission statement given at the beginning of the GPL: "Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed."
The GPL states that you must make the Source Code freely avilible [sic] to your customers...
It also says you musn't interfere with their rights granted by the GPL:
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
Seems pretty clear to me: "You may make copies and give them away provided you give the recipients all the rights which I gave you."
So if it's a closed beta only the people who recieve [sic] that beta have right to that source... and anyway, all the programmes are available on the internet (freshmeat) and as part of other distro's [sic]...!
Yes, this is true. However, you miss a couple of important points:
While it's correct that "only the people who recieve [sic] that beta have right to that source," the people who receive the source have certain rights which are granted by the license. To restrict those rights means that the license has been violated and any prior rights granted to the distributor have been revoked.
Although "all the programmes are available on the internet (freshmeat) and as part of other distro's [sic]," that doesn't mean that they're the ones doing the distributing in this case. All that means is that when someone distributes an app through Freshmeat, that person must offer the source code and full GPL rights to it. When UnitedLinux distributes GPL-covered programs, they must do the same thing. It doesn't matter that other people already do it; "other people" cannot fulfill your obligations under this particular distribution license.
In case you haven't read it, I strongly urge a reading of the GPL itself; it is certainly one of the most lay-accessible legal documents out there.
I hear that it's the only Linux filesystem that is endian-safe. IOW, you can move it from a system of one endian type to a system of the other type and it will still work. No other filesystem for Linux currently is able to make that claim.
I find that very cool, for some reason. I guess one practical application is if you have a box that is the only one of that type (either big-endian or little-endian) that dies and you need to recover the data.
A friend of mine did just this because he was tired of people consuming his upstream DSL bandwidth. His solution uses mod_rewrite, which comes standard with Apache. (It's a configure/compile-time option in both 1.3 and 2.0, but I'd be highly surprised if a distribution didn't enable it.)
A couple other random thoughts. There are several programs for updating various bits of the system; these were primarily written for maintainer scripts. Check out the man pages for/{,usr/}{s,}bin/update-*. In particular, update-alternatives(8) is used for managing the alternatives system (which RedHat has ported to their system and released with 7.3). In a nutshell, this system is one method to allow several packages to provide the same executable file, such as/usr/bin/vi (which can be provided by vim, nvi, elvis, vile,...). The description in the man page provides a good overview of the system. Also note update-modules(8). Instead of editing/etc/modules.conf, edit a file in/etc/modutils (such as/etc/modutils/local, for example) and run update-modules. Otherwise your changes to/etc/modules will be overwritten at some point in the future, after that command is run. The rationale for many of these types of commands is to provide convenience for and reduce the complexity of package maintainers' scripts. (update-rc.d(8), for example, knows whether you're using the file-rc package or not and will do the Right Thing.)
I've tried Gentoo myself. There are some things I like about it and some I don't (I missed the Debian menu system, for example). It isvery nifty, though.
I don't use it on any of my machines. The reason for this is the Debian Installer. It is a pain the butt to get the thing installed. And the benefits for doing so don't outweigh the horrors of getting it installed.
Try PGI(download), the installer which Progeny donated. I hear they'll be moving to this in the next release or two. In the mean time, it works beatifully. It auto-detected my hardware and wrote a sane X configuration.
Anyway, I happen to disagree; once it's installed, you never have to reinstall it on that machine ever again. But there are things like PGI for you so that you don't have to deal with it.
Sounds like you were using dselect. My god, I don't know why that's available in the default install. It's horrible. It really, really sucks. My advice: Don't use it. I've heard some people praise aptitude; I've used it once or twice myself, and it's all right, but I still prefer command-line apt-get. My advice would be not to worry about installing everything up front; that's what you need to do with most other distributions since it's a hassle to add the software later. If you find yourself wanting to install something, use apt-cache search <foo> to look for it and apt-get install <bar> to install it, where foo is a search term and bar is a package name. If you want to install several related packages (say, a full development environment), use tasksel; it will present you with several broad categories from which to choose (such as C development, X window system, mail server, etc.) and you can select zero or more sets of packages to install.
Init scripts live in/etc/init.d; the runlevel symlinks are found in/etc/rc?.d. Debian includes a utility called update-rc.d; use this instead of chkconfig (which is not present). Keep in mind that Slackware and *BSD machines have only monolithic init scripts.;-)
Network device configuration is done via/etc/network/interfaces; see interfaces(5) for the format of this file.
Hope this helps some if you still want to give Debian a shot. If you have any other questions, let me know.
Slashdot Mirror
Don't forget UBS!
The Challenge-Response Authentication Protocol! ;-)
Please mod me gently. :)
Here's another interesting piece by the same author.
Oh, there's a simpler way than that. We'd just use a Coleman lantern igniter. Just drill a hole in the combustion chamber and fit one in it. A quick twist and you've launched your spud. :)
As far as how long they support old releases... When they released potato, they dropped support for slink fairly quickly, within a couple of months I think. Since they released woody, they've kept up support for potato; potato packages are still included in the security announcements that are sent out. Woody's been out for what, about a year and a half now? I imagine potato support will be dropped at least by the time sarge is released, but that's pure speculation on my part.
Pardon me, but I don't think that Wal-Mart's "seen the light" or become a good guy in this regard.
Just playing devil's advocate here. :)
At least it's been several months. ;-)
Sorta like a progressive jpeg, except it's audio. :)
Well... okay. Isn't that what punishing a company and making an effort to restore competition usually does? How can you accomplish those two goals without bring benefit to the competitors?
According to the FAQ (and most people you'd ask today), KDE stands for "K Desktop Environment". However, the original Usenet post announcing the formation of the project refers to it as the "Kool Desktop Environment". A Google Groups search confirms this.
It's not distributed under any license. The author gives a simple permission statement: "Permission is hereby granted to copy and distribute this license without modification." This is similar to the permission statement given at the beginning of the GPL: "Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed."
This is in Mozilla as well. It's in there since at least 1.0 (which is what I'm using (Debian's Mozilla 1.0 package)).
It also says you musn't interfere with their rights granted by the GPL:
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
Seems pretty clear to me: "You may make copies and give them away provided you give the recipients all the rights which I gave you."
Yes, this is true. However, you miss a couple of important points:
- While it's correct that "only the people who recieve [sic] that beta have right to that source," the people who receive the source have certain rights which are granted by the license. To restrict those rights means that the license has been violated and any prior rights granted to the distributor have been revoked.
- Although "all the programmes are available on the internet (freshmeat) and as part of other distro's [sic]," that doesn't mean that they're the ones doing the distributing in this case. All that means is that when someone distributes an app through Freshmeat, that person must offer the source code and full GPL rights to it. When UnitedLinux distributes GPL-covered programs, they must do the same thing. It doesn't matter that other people already do it; "other people" cannot fulfill your obligations under this particular distribution license.
In case you haven't read it, I strongly urge a reading of the GPL itself; it is certainly one of the most lay-accessible legal documents out there.I find that very cool, for some reason. I guess one practical application is if you have a box that is the only one of that type (either big-endian or little-endian) that dies and you need to recover the data.
A friend of mine did just this because he was tired of people consuming his upstream DSL bandwidth. His solution uses mod_rewrite, which comes standard with Apache. (It's a configure/compile-time option in both 1.3 and 2.0, but I'd be highly surprised if a distribution didn't enable it.)
A couple other random thoughts. There are several programs for updating various bits of the system; these were primarily written for maintainer scripts. Check out the man pages for /{,usr/}{s,}bin/update-*. In particular, update-alternatives(8) is used for managing the alternatives system (which RedHat has ported to their system and released with 7.3). In a nutshell, this system is one method to allow several packages to provide the same executable file, such as /usr/bin/vi (which can be provided by vim, nvi, elvis, vile, ...). The description in the man page provides a good overview of the system. Also note update-modules(8). Instead of editing /etc/modules.conf, edit a file in /etc/modutils (such as /etc/modutils/local, for example) and run update-modules. Otherwise your changes to /etc/modules will be overwritten at some point in the future, after that command is run. The rationale for many of these types of commands is to provide convenience for and reduce the complexity of package maintainers' scripts. (update-rc.d(8), for example, knows whether you're using the file-rc package or not and will do the Right Thing.)
I've tried Gentoo myself. There are some things I like about it and some I don't (I missed the Debian menu system, for example). It is very nifty, though.
Have fun! And I'll be happy to help if you want.
- Sounds like you were using dselect. My god, I don't know why that's available in the default install. It's horrible. It really, really sucks. My advice: Don't use it. I've heard some people praise aptitude; I've used it once or twice myself, and it's all right, but I still prefer command-line apt-get. My advice would be not to worry about installing everything up front; that's what you need to do with most other distributions since it's a hassle to add the software later. If you find yourself wanting to install something, use apt-cache search <foo> to look for it and apt-get install <bar> to install it, where foo is a search term and bar is a package name. If you want to install several related packages (say, a full development environment), use tasksel; it will present you with several broad categories from which to choose (such as C development, X window system, mail server, etc.) and you can select zero or more sets of packages to install.
- Init scripts live in
/etc/init.d; the runlevel symlinks are found in /etc/rc?.d. Debian includes a utility called update-rc.d; use this instead of chkconfig (which is not present). Keep in mind that Slackware and *BSD machines have only monolithic init scripts. ;-) - Network device configuration is done via
/etc/network/interfaces; see interfaces(5) for the format of this file.
Hope this helps some if you still want to give Debian a shot. If you have any other questions, let me know.