If you let your six year old walk to school, then you're the one who needs the electronic leash.
This was designed to give parents one "last ditch" effort to try to have an influence on their teenagers, who by the vast majority of standards are fully qualified to fight in wars yet (in western 'civilization') are denied the basic right not to be spied upon.
They never realized that the reason why I could do anything was because I realized I shouldn't.
You realized you shouldn't because you were given the chance to come to that decision like a human, not tethered to your parents 24/7. Trust works both ways. Parents who subject their children to this kind of treatment show that they are the ones who have problems with trust.
I meant to say that every TOOL performs only ONE TASK. It really should be repeated around here more often, because I still (obviously) haven't heard it enough:)
The single most important concept in Unix is that there is ONE TOOL for every TASK. The "users" you refer to (hopefully we're talking about administrators) think that "compile and install program" is one task.
For Open Source programs that one has to compile, there are actually three tasks: configure, build, and install. For closed-source software, you have already paid someone else to perform the first two tasks for you, and lost quite a bit in terms of configurability in the process.
With Open Source, you get to control everything from configuration to compilation to installation. The downside to this flexibility is that for poorly-maintained projects, it doesn't always work. Separating the process into three distinct steps can also help the administrator to diagnose problems with the install.
Yeah, except these people aren't a part of our "country". They are imported into our country in order to avoid having to hire people from within our "free country".
My widget factory needs electricity and heat. This is exactly why I say that the solution to America's economic problems is one thing: office workers on stationary bicycles.
Stay with me here... 1) We're all too fat. 2) The price of oil is too high, and electricity naturally follows. 3) We are spending too much money on health care and not enough on preventative measures. 4) There are too many out of work information workers, just waiting to replace their former co-workers with Perl scripts. 5) Perl scripts require electricity.
This is an amazingly insightful comment. Our teacher in elementary school had the entire class write an "Ode to Voyager II". While it definitely piqued my interest in poetry, I found the process of invoking emotions for a space probe awkward to say the least. I always get an icky feeling whenever I see cold-war-era state-sponsored murals of people plowing in fields with rockets behind them in US universities. You're right, "totalitarian" regimes aren't the only ones that have created such presumptuous crap and called it art.
I'm sure you meant "we" as in "we the taxpayers" and "make the correct choice" as in "get the best software for our money". If that choice isn't painfully clear by now, then you're right, we should help our governments make the "correct" choice.
What is your argument, exactly? Are you saying that states should bilk taxpayers for the sole reason of sending money to Redmond, or are you still under the impression that Windows is cheaper? You sound like you're saying "We gave money to MS and got a benefit in return. Aren't we smart?" This guy is saying, "We aren't giving MS squat, because we can get the same benefit cheaper from Linux."
You couldn't possibly have migrated '95 computers to XP, NT at the least. If MA had computers capable of running NT, that means they would have spent a lot more money on upgrades over the last six years than they (obviously) have. They probably would be more able to look at XP as a "managable", "automated" upgrade. They can't. They didn't spend the money required to make XP a cost-effective solution. The difference is that Linux isn't $200 a license and it will run on hardware that Windows would balk at.
You get the same "managability" by moving to an X client/server model (which is what it looks like they are considering) that you do from "Active Directory". The difference is that, while Linux has done it right from the beginning, Microsoft has just shoehorned a centralized configuration database into all of their products in order to make it feasible to uniformly configure more than about 20 Windows desktops.
Wow. This is a troublesome issue. First off, in general copyrights are considered to have identical jurisdiction as patents from a constitutional perspective, since they are both placed within the powers of congress by Article I, Section 8: "writings and discoveries".
I haven't read it, but from what I understand the DMCA only concerns copyrights, specifically prohibiting the "trafficking" (note how everything in federal law is justified from a "commerce" perspective, since that has the least chance of being struck down) of technological measures that circumvent other technologies that protect copyrighted works. The founders of the US could never have imagined that products could be made to "talk" to each other, and that such communications could be copyrighted and used to prevent interoperability. I presume that they would disapprove. Here's why:
What does copyright law protect? It protects the "right" of creators to profit from their work, thereby encouraging them to perform such work to begin with. Many of the founders, especially Franklin, expounded upon the concept of copyright by describing it in exactly such terms. The DMCA would tend to pass the smell test in this regard by outlawing practices which are designed to deprive copyright holders of this "right".
This case, though, is not about protecting the profits from a copyrighted work. It is not a copyrighted work being protected by a technological measure; it is a technology being protected by a copyrighted work. People don't buy inkjet cartridges for the copyrighted 64-bit encryption key or the Lexmark logo that is saved in the chip somewhere. They buy the cartridges for their ability to print ink on paper. They would do just that whether they had the key on them or not. The value is in the *product*, not in the *creation*, and manufactured products are neither "inventions" nor "writings".
Microsoft has a much better case than this with the X-Box "mod" chips, since they can at least claim that the chips provide access to copyrighted works and hence deprive their owners of the profits from them.
I could be wrong. I guess most people just want instant gratification (access to the programs they need to run) and a stable, reliable experience for the least cost possible. These seem to be at odds with each other.
The users I know would trade stability and $10/mo for instant access, so they leave their computers on all the time and they crash once a week. Maybe the users you refer to are more cost-conscious, or maybe they just want stability and would trade the two minutes it takes to boot and log in for a reliable system.
All I'm saying is that, given the opportunity, anyone would want both reliability and instant-access for zero cost. M$ knows this, and they know their products are not stable, so they market the (fictional) "fast boot times" of their OS's.
Yes, it is. The install is still rather complicated and stupid desktop tasks like configuring printers are not intuitive. This is a tradeoff, however, because Debian is by far the most flexible Linux distro and probably always will be, which is why I use it as my desktop. It is definitely not for someone who knows nothing about Linux and wants to replace Windows. You really should consider Mandrake, despite their financial difficulties.
Microsoft has gradually moved more and more startup routines from *before* the login screen to *after*, now even after the UI has been drawn and appears ready.
This is to add to their increasingly absurd claims that "Windows (95,98,Me,XP) boots in (60,40,20,10) seconds!" Yet another marketing-ploy-turned-lousy-programming by the great people in Redmond.
What they haven't (yet) realized is that most people don't want to have to turn off their computers ever. They are just forced to reboot all the time by crappy "features" such as these.
This guy disagrees: "SCO Xenix V Development System C Language Reference, part number XG-5-1-86-3.0 from 1986" from "the first Xenix 386 development system that we purchased from SCO".
The US was designed as a forum for businesses to deal with each other across the nation in a uniform manner (money, laws, etc...), not for the administration of criminal justice. The vast majority of US jurisdiction is civil. And, in civil court, a person can only be sued for monetary "damages" inflicted on another. By building inkjet cartridges in one's basement, no damage is caused. Therefore, even if building inkjet cartridges in one's basement for personal use were technically "illegal", no one would have standing in court to bring action. By selling inkjet cartridges, however, damages in the form of the profit that would have gone to the patent holder are incurred.
Remember also that patent (and copyright) law is a compromise brokered by the state between content creators and inventors and society as a whole. In exchange for exclusive "rights" (really powers, since it is basically the 'right' to infringe upon others' rights) to profit from one's discoveries for a period of time, society gets access to vast troves of technical knowledge on which to build and improve. If everyone were prevented from building and verifying and improving upon inventions during the time in which the patent holder has "exclusive rights" to them, innovation would grind to a halt. By preventing people from profitting from others' inventions, inventors are granted a "right" that they would not otherwise have: the right to be free from competition for a period of time once one's invention is put into the public sphere.
The case you mentioned, that of manufacturing and selling infringing products within a state, is specifically placed under Federal Civil Jurisdiction by Article I, Section 8 of the Constitution. By selling the cartridges, you cause damages to the Patent holder and violate his "exclusive right to (profit from his) discoveries". This has nothing to do with interstate commerce. If it didn't involve patents (or copyrights), the US would have no jurisdiction because it is "intrastate" commerce. If there were no damages, no one would have jurisdiction because no one would have standing in court because no one would have a claim against you.
From what I can gather, this is how OpenAFS provides seamless filesystem access on platforms (Windows) that no-one wants to write drivers for. The scheme is basically:
FAT formatted USB drive->encrypted file->SMB/CIFS server->SMB/CIFS client on OS
Yeah, you're right. I found like four links on Google that confirm Cygwin has no loopback support right after I posted that. It seemed like a good idea at the time...
Slashdot Mirror
This has nothing to do with petty politics. It has to do with a federal government run-amok and lying to everyone to cover up that fact.
If you let your six year old walk to school, then you're the one who needs the electronic leash.
This was designed to give parents one "last ditch" effort to try to have an influence on their teenagers, who by the vast majority of standards are fully qualified to fight in wars yet (in western 'civilization') are denied the basic right not to be spied upon.
You realized you shouldn't because you were given the chance to come to that decision like a human, not tethered to your parents 24/7.
Trust works both ways. Parents who subject their children to this kind of treatment show that they are the ones who have problems with trust.
I meant to say that every TOOL performs only ONE TASK. It really should be repeated around here more often, because I still (obviously) haven't heard it enough :)
The single most important concept in Unix is that there is ONE TOOL for every TASK. The "users" you refer to (hopefully we're talking about administrators) think that "compile and install program" is one task.
For Open Source programs that one has to compile, there are actually three tasks: configure, build, and install. For closed-source software, you have already paid someone else to perform the first two tasks for you, and lost quite a bit in terms of configurability in the process.
With Open Source, you get to control everything from configuration to compilation to installation. The downside to this flexibility is that for poorly-maintained projects, it doesn't always work. Separating the process into three distinct steps can also help the administrator to diagnose problems with the install.
Is that why laptops have an external transformer "brick", or is that just for convenience?
Russ Cooper, moderator of the NTBugTraq security list, which is owned by security services firm TruSecure, agreed that attack wasn't a serious one
Deepest Apologies...
Probably because he's talking about the wrong exploit.
That's Bytes, as in 8 bits. A 100 Mbit/sec NIC is only 12.5 MBytes/sec.
Soekris Engineering also sells a crypto card for VPN applications. It says it also does compression.
Yeah, except these people aren't a part of our "country". They are imported into our country in order to avoid having to hire people from within our "free country".
What were you thinking here?
This is exactly why I say that the solution to America's economic problems is one thing: office workers on stationary bicycles.
Stay with me here... 1) We're all too fat. 2) The price of oil is too high, and electricity naturally follows. 3) We are spending too much money on health care and not enough on preventative measures. 4) There are too many out of work information workers, just waiting to replace their former co-workers with Perl scripts. 5) Perl scripts require electricity.
It's perfectly logical.
This is an amazingly insightful comment. Our teacher in elementary school had the entire class write an "Ode to Voyager II". While it definitely piqued my interest in poetry, I found the process of invoking emotions for a space probe awkward to say the least. I always get an icky feeling whenever I see cold-war-era state-sponsored murals of people plowing in fields with rockets behind them in US universities. You're right, "totalitarian" regimes aren't the only ones that have created such presumptuous crap and called it art.
I'm sure you meant "we" as in "we the taxpayers" and "make the correct choice" as in "get the best software for our money". If that choice isn't painfully clear by now, then you're right, we should help our governments make the "correct" choice.
What is your argument, exactly? Are you saying that states should bilk taxpayers for the sole reason of sending money to Redmond, or are you still under the impression that Windows is cheaper? You sound like you're saying "We gave money to MS and got a benefit in return. Aren't we smart?" This guy is saying, "We aren't giving MS squat, because we can get the same benefit cheaper from Linux."
You couldn't possibly have migrated '95 computers to XP, NT at the least. If MA had computers capable of running NT, that means they would have spent a lot more money on upgrades over the last six years than they (obviously) have. They probably would be more able to look at XP as a "managable", "automated" upgrade. They can't. They didn't spend the money required to make XP a cost-effective solution. The difference is that Linux isn't $200 a license and it will run on hardware that Windows would balk at.
You get the same "managability" by moving to an X client/server model (which is what it looks like they are considering) that you do from "Active Directory". The difference is that, while Linux has done it right from the beginning, Microsoft has just shoehorned a centralized configuration database into all of their products in order to make it feasible to uniformly configure more than about 20 Windows desktops.
D) The state is planning to re-use their outdated hardware as X terminals, and only plans to buy Linux servers.
I haven't read it, but from what I understand the DMCA only concerns copyrights, specifically prohibiting the "trafficking" (note how everything in federal law is justified from a "commerce" perspective, since that has the least chance of being struck down) of technological measures that circumvent other technologies that protect copyrighted works. The founders of the US could never have imagined that products could be made to "talk" to each other, and that such communications could be copyrighted and used to prevent interoperability. I presume that they would disapprove. Here's why:
What does copyright law protect? It protects the "right" of creators to profit from their work, thereby encouraging them to perform such work to begin with. Many of the founders, especially Franklin, expounded upon the concept of copyright by describing it in exactly such terms. The DMCA would tend to pass the smell test in this regard by outlawing practices which are designed to deprive copyright holders of this "right".
This case, though, is not about protecting the profits from a copyrighted work. It is not a copyrighted work being protected by a technological measure; it is a technology being protected by a copyrighted work. People don't buy inkjet cartridges for the copyrighted 64-bit encryption key or the Lexmark logo that is saved in the chip somewhere. They buy the cartridges for their ability to print ink on paper. They would do just that whether they had the key on them or not. The value is in the *product*, not in the *creation*, and manufactured products are neither "inventions" nor "writings".
Microsoft has a much better case than this with the X-Box "mod" chips, since they can at least claim that the chips provide access to copyrighted works and hence deprive their owners of the profits from them.
The users I know would trade stability and $10/mo for instant access, so they leave their computers on all the time and they crash once a week. Maybe the users you refer to are more cost-conscious, or maybe they just want stability and would trade the two minutes it takes to boot and log in for a reliable system.
All I'm saying is that, given the opportunity, anyone would want both reliability and instant-access for zero cost. M$ knows this, and they know their products are not stable, so they market the (fictional) "fast boot times" of their OS's.
Yes, it is. The install is still rather complicated and stupid desktop tasks like configuring printers are not intuitive. This is a tradeoff, however, because Debian is by far the most flexible Linux distro and probably always will be, which is why I use it as my desktop. It is definitely not for someone who knows nothing about Linux and wants to replace Windows. You really should consider Mandrake, despite their financial difficulties.
This is to add to their increasingly absurd claims that "Windows (95,98,Me,XP) boots in (60,40,20,10) seconds!" Yet another marketing-ploy-turned-lousy-programming by the great people in Redmond.
What they haven't (yet) realized is that most people don't want to have to turn off their computers ever. They are just forced to reboot all the time by crappy "features" such as these.
This guy disagrees: "SCO Xenix V Development System C Language Reference, part number XG-5-1-86-3.0 from 1986" from "the first Xenix 386 development system that we purchased from SCO".
This would seem reasonable, except for the fact that the US was only granted limited power to punish crimes: only crimes defined in the Constitution that affect the nation itself. "The drafters of the Constitution clearly intended the states to bear responsibility for public safety and what Alexander Hamilton called 'the ordinary administration of criminal and civil justice.'"
The US was designed as a forum for businesses to deal with each other across the nation in a uniform manner (money, laws, etc...), not for the administration of criminal justice. The vast majority of US jurisdiction is civil. And, in civil court, a person can only be sued for monetary "damages" inflicted on another. By building inkjet cartridges in one's basement, no damage is caused. Therefore, even if building inkjet cartridges in one's basement for personal use were technically "illegal", no one would have standing in court to bring action. By selling inkjet cartridges, however, damages in the form of the profit that would have gone to the patent holder are incurred.
Remember also that patent (and copyright) law is a compromise brokered by the state between content creators and inventors and society as a whole. In exchange for exclusive "rights" (really powers, since it is basically the 'right' to infringe upon others' rights) to profit from one's discoveries for a period of time, society gets access to vast troves of technical knowledge on which to build and improve. If everyone were prevented from building and verifying and improving upon inventions during the time in which the patent holder has "exclusive rights" to them, innovation would grind to a halt. By preventing people from profitting from others' inventions, inventors are granted a "right" that they would not otherwise have: the right to be free from competition for a period of time once one's invention is put into the public sphere.
The case you mentioned, that of manufacturing and selling infringing products within a state, is specifically placed under Federal Civil Jurisdiction by Article I, Section 8 of the Constitution. By selling the cartridges, you cause damages to the Patent holder and violate his "exclusive right to (profit from his) discoveries". This has nothing to do with interstate commerce. If it didn't involve patents (or copyrights), the US would have no jurisdiction because it is "intrastate" commerce. If there were no damages, no one would have jurisdiction because no one would have standing in court because no one would have a claim against you.
From what I can gather, this is how OpenAFS provides seamless filesystem access on platforms (Windows) that no-one wants to write drivers for. The scheme is basically:
FAT formatted USB drive->encrypted file->SMB/CIFS server->SMB/CIFS client on OS
Yeah, you're right. I found like four links on Google that confirm Cygwin has no loopback support right after I posted that. It seemed like a good idea at the time...