You are NOT allowed to run webservers, so what does it matter that they block those ports?
Which takes us back to the point made by the first poster in this thread -- what good is high bandwidth (especially -- in the "up" direction), if I can not use it?
If Kafka has a problem with it, let him do something about it. Until then, tough shit.
Hardly a nobble approach. One's will should be obeyed after one's death -- that is one of the customs of our society. Parts of that custom even made it into laws...
Want five more? Come download...
on
P2P and TV
·
· Score: 1
Want five more? Come buy the boxed set
Would he be as enthusiastic if it ended with "download your copy of five more" from the only set actually sold?
As long as artists are "in it" for the money (rather than because they simply can not control their artistic expression and/or quest for fame), they'll start to hate "p2p" sooner or later...
Althought dogs are forgiving animals, I think they might hold a grudge if you killed them, and then brought them back to life.
Which is why a "Tripe Ration" is as essential as the "Wand of Undead Turning". Just throw the ration at the recovered (and still upset) dog, and after it devours it, it will be friendly again.
Your luck will still be low, however, so throw some gems to unicorns.
There are entire classes of weapons, which are banned altogether as those of "assault" kind.
What exactly makes a weapon "assult" is dark magic -- sometimes it is caliber, sometimes it is the bullet's speed, and sometimes it is simply the magazine's capacity. Not entirely unlike the flimsy distinctions between users of Gnutella and BitTorrent...
[...] applied to almost anything? Let's try firearms...
Tried already... A number of gun-sellers were busted a few years ago in a sting around Chicago, when they repeatedly ignored their customers' unambigiously stated intentions of "settling some scores", etc.
The "customers" were, of course, working for the government.
Logic at its finest! If something was a bad idea in the past it is OK if the same behavior is repeated?
"Repeated" is not a good word. "Continued" is more like it.
No, it is not Ok. But calling the current President "fray bully" is not a proper criticism of practices in use since very long ago. Take a deeper breath.
adopt domestic policies to erode personal liberty, detain people (even US citizens) indefinitely without charge or trial, prop up undemocratic governments in Egypt and Lebanon
None of these things were invented by this administration. Take a deep breath...
The teacher's unions actively prevent home schooling? How the fuck do they do that?
By spreading the FUD about the "inadequacy" of home schooling and by lobbying to make it illegal. It is, in fact, illegal in "more progressive" countries like Germany.
raised by parents who think the schools should be the parents, so the schools are so busy teaching Johnny how to Share His Feelings
Actually, all of these "sensitivity" programs are crammed down the parents' throats.
Don't blame NASA, blame parents
More like "blame teachers' unions" -- like that of all trusts, those people's top priority is preserving their members' incomes by stiffling all competition -- such as from home or private schooling.
Hey, I'm just looking at the cmd-scripts our Windows developers are using. The try to simulate "$@" with %1 %2 %3 %4 %5 %6 %7 %9 (because no one will ever pass more than 9 arguments, right?).
In comparison, the Unix shells' @ is pretty damn non-intuitive
Unix shells have $* as well, but there are subtle differences in how these two (* and @) handle arguments, which have blank spaces inside them...
Ok, thanks, that link has some loop examples, but no equivalent of shell's "$@". Would you try again, or agree (for the record), that this functionality is missing?
Just in case you don't know, what I'm talking about, "$@" are all the arguments given to the script in one list. For example, the following wrapper can replace any program (which should first be renamed into program.bin):
#!/bin/sh
# Log the invocation of the program:
logger "Executing $0 with the arguments $@"
# Execute the original utility:
exec "$0.bin" "$@"
Whilst the UNIX style unified directory hierarchy is aesthetically pleasing to computer scientists, I've never been convinced that it's really more usable. On Windows, people can learn a few simple letter to concept mappings "A" is the floppy disk, "C" is the stuff inside the Computer, "D" is the cD-rom drive, "E" is their usbEE kEE. Obviously not all systems will be like that, but it's common enough. On UNIX systems the location of floppy disks, installed programs, mounted USB keys and so on tend to move around unpredictably.
Sorry, this is just laughable. So, you, consider "D" to be easier to associate with a "cD-rom", than "/cdrom"? You are not even trying to justify the "A" for "floppy disk":-)
The reaction of computer scientists should be your guide. These people tend to know answers to questions, which you don't know enough to even ask.
licensing concerns (like XP workstation allowing only one user at a time);
I don't see how this would affect a command shell designed for personal use.
Oh, that's easy. You named it yourself: "for personal use". To ensure, it is available for personal use only you may only be allowed to run a single instance of it, unless you purchase the server license. Or it may not be available to telnet sessions. Or something bizarre like that.
Microsoft backport far more stuff than Linux vendors do
They better... With sh, csh (or whatever Unix shell rocks your boat) you can do anything. It may not be pretty, but it will work. Witness configure-scripts. With cmd.exe you can't even pass all of your own arguments down (there is no equivalent of "$@") -- forget about procedures, loops, etc.
The guys working on MSH have blogs, I read a few, and they seemed very sharp to me.
Oh, I'm sure, there are plenty of smart individuals working for Microsoft. However, the firm's organization and its dirty unatoned past (and, likely, present) will continue to weight on the firm's products -- and their reputation -- for some time... And these -- the reputation and perception -- are the subject of the thread.
Slashdot Mirror
Obeying the last will of a loved one is noble -- as long as you don't do anything illegal. But you already knew that.
No, it would not be.
Burning your papers would not.
As long as artists are "in it" for the money (rather than because they simply can not control their artistic expression and/or quest for fame), they'll start to hate "p2p" sooner or later...
Try ${11}... What is the equivalent for Windows? And will %11 work to concatenate %1 with digit 1?
Your luck will still be low, however, so throw some gems to unicorns.
To me these figures paint a different picture: "Norway, back off or become even more irrelevant to Microsoft".
What exactly makes a weapon "assult" is dark magic -- sometimes it is caliber, sometimes it is the bullet's speed, and sometimes it is simply the magazine's capacity. Not entirely unlike the flimsy distinctions between users of Gnutella and BitTorrent...
The "customers" were, of course, working for the government.
Interestingly, there is no municipal WiFi mentioned...
Did the submitter go to Yale too? What happened to the "least publicized"?
No, it is not Ok. But calling the current President "fray bully" is not a proper criticism of practices in use since very long ago. Take a deeper breath.
Let the government do it. The bigger the governed body, the "better" your chances.
Unix shells have $* as well, but there are subtle differences in how these two (* and @) handle arguments, which have blank spaces inside them...
Why can't they come up with something effective against IEDs?
Just in case you don't know, what I'm talking about, "$@" are all the arguments given to the script in one list. For example, the following wrapper can replace any program (which should first be renamed into program.bin):
#!/bin/sh
# Log the invocation of the program:
logger "Executing $0 with the arguments $@"
# Execute the original utility:
exec "$0.bin" "$@"
Can cmd.exe do this?
Can you post the equivalent of sh's "$@" and some examples of loop syntax? Thanks!
Sorry, this is just laughable. So, you, consider "D" to be easier to associate with a "cD-rom", than "/cdrom"? You are not even trying to justify the "A" for "floppy disk" :-)
The reaction of computer scientists should be your guide. These people tend to know answers to questions, which you don't know enough to even ask.
Oh, that's easy. You named it yourself: "for personal use". To ensure, it is available for personal use only you may only be allowed to run a single instance of it, unless you purchase the server license. Or it may not be available to telnet sessions. Or something bizarre like that. They better... With sh, csh (or whatever Unix shell rocks your boat) you can do anything. It may not be pretty, but it will work. Witness configure-scripts. With cmd.exe you can't even pass all of your own arguments down (there is no equivalent of "$@") -- forget about procedures, loops, etc. Oh, I'm sure, there are plenty of smart individuals working for Microsoft. However, the firm's organization and its dirty unatoned past (and, likely, present) will continue to weight on the firm's products -- and their reputation -- for some time... And these -- the reputation and perception -- are the subject of the thread.