Whiskey, Tango, Foxtrot? I run services under trusted accounts all the time, and restrict the hell out of those accounts; what machines they can log into, what they can do whilst logged in, etc etc.
This happens all the time; company backs up a server, and sends the tapes to an offsite storage firm. That tape is chock full of software which states you can't copy it in any way.
But, you say, fair use covers a backup! But any company who wants to keep their data keeps many many historical and working backups.
Good to see that most companies in North America are raging software pirates.
I agree with you completely on these points; war is a nasty business, and it's no sense in making it worse than it needs to be. And both sides do need to both adhere to certain rules, especially these days, or the nukes'll fly. But it's still war, and Entropy-based warfare doctrine points out that the quickest way to win a war is to shatter supply lines, deny him information, then give him a quick, good smash, and watch him crumble.
Also, being Canadian, I was both surprised and proud to see your example. I assume you're American, and if so, I thank you for not living up to the American-centric stereo type.:-)
Don't forget, also, that under the Geneva Conventions of War (a laughable thing) bullets aren't supposed to fragement, and they're supposed to blow through, rather than get stuck in the body somewhere; it's more humane that way.
Actually, in a mass battle, wounding is more effective than killing.
Besides the moral effects, kill an enemy, you've taken out an enemy. Wound one, you've taken him out, plus two people to carry him, plus medics to treat him, plus logistics to support him, etc etc.
Very true, but mainly because the code wan't written with portability in mind. It's a shortcoming, a flaw, not a feature, not a property.
Of course, it's also because alot of the software you cite is either written to a specific platform, or using a language that tends to be platform-centric.
I'm merely trying to point out that you made far too broad a statement.
Actually, the average American city can feed itself for three days. Food riots, however, would start almost immediately.
My suggestion would be forget food; raid a outdoors store, load up on survival gear and basic hunting equipment (grab guns, but they're for defense, not hunting. Unless you know how to, or can learn how to, reload brass..22 is your best bet; been around for 100 years, widely used, not beyond your ability to make yourself with some training) and WALK OUT OF THE CITY. Forget your car; the roads'll be clogged with either others trying to flee, or with broken down cars. Maybe a mountain bike.
Once you get into the wilderness, find yourself a defensible position. Keep an eye out for things like: lines of attack in and out, fields of fire, suitibility for defense in depth, clean water, all that stuff.
Once there, you're going to want to see to your immediate needs, then start attracting some like minded folk, both for defense, and to gain skills you yourself don't have.
As an aside, a CIA report a while back stated that in the event of a global holocaust, one of the prevalent groups to come out would be the Society for Creative Anacronisim. Why? They're semi-organized, mobile, and know how to create by hand, and use, armour and weaponry. As well as having other useful skills.
Most of the natural resources that our society relies on, we've either already exhausted to the point where you can't get them without heavy tech help, or you need tech to build them.
Five hundred years ago, you could pick up red rocks, smelt them, and oh look, Iron. Not now a days.
Re:bathroom humor = intergalactic language
on
Anticryptography
·
· Score: 2
start with the good stuff: a pictogram of ET getting kicked in the sack.
I just thought you should know that I just laughed myself into hyperventilation. I feel woozy, and I think I'm going to hurl.
The problem here is that we've already got frames of references for all of those symbols, and will unconciously attempt to apply those notions to the symbols.
No, they tend to release a box set FIRST, then release individual DVDs. The UY DVDs from the first box set are going to start coming out individually very soon now.
But you forget to mention that the DOT will publish the specs for the road, and has been upgrading the road on a regular basis, and all cars that expect to drive tout the fact that they're DirectROAD 7 compliant anyway.
Besides, what's to prevent somebody from coding up a 'virtual pixel shader' that does it in software? By that logic, nobody should have supported the Voodoo 1 or anything like that! Then EVERYBODY would have to buy an expensive 3d video card!
Trusted flavos of varios closed source Unixes and VMS have had the same system for years
ACLs are required for the useful levels of Orange Book certification; I don't have my reference handy, but they may even be listed in the C classification.
until they read "Game Over: Press Start To Continue."
Excellent book on the history of Nintendo.
Don't count Nintendo out; the N64 was a failure, yes. By Nintendo standards. Any other company would have considered it a fantastic success.
Yay Ottawa! My first college co-op was for National Defense.
Keep in mind, kids, co-ops are like shit. There's plenty to spread around, nobody wants to step in it, but it'll float to it's proper level, and it's a prime ingredient for growing things.
In other words, go in expecting the world, you're in for a grand disappointment. Go in prepared to demonstrate your skill and abilities, and you'll probably be given tasks consummate with said skills and abilities. But nobody likes a teen-age punk know-it-all whiner; at that point, you're fufilling stereotypes.
You forgot number 3: valuable contacts. FUCKING VALUABLE 'networking.'
In my college course (university is right out; I didn't want an education. I wanted a job. And as a Senior Systems Administrator at 23, who has co-ops of his own;-) I think it all worked out) literally 2/3rds of the class (who wern't weeded out, at least) didn't graduate because their co-op employers begged them to stay on. Myself included.
I was a co-op student, and I make a point of hiring them whenever I can, as co-op is a wonderful concept.
I try to make it interesting, and educational, and blah blah blah, but the simple fact of the matter is that there's a lot of 'scut' work that pops up. And a lot of it gets dumped on the person who's other tasks would suffer least, from a business point of view. Guess what; if there's a co-op, it's her.
But here's something that most co-ops never realize: if the co-op wern't there to do it, it would still get done. It would still be there. We're not creating the scut work specifically to give to you, and yes, guess what, for every exciting relational database you get to design and implement, there will be thousands and thousands of crap assignments; inventory, renaming documents, etc etc etc. Might as well learn that fact now.
Slashdot Mirror
The more you tighten you grip, Rosen, the more MP3s will slip through your fingers.
Whiskey, Tango, Foxtrot? I run services under trusted accounts all the time, and restrict the hell out of those accounts; what machines they can log into, what they can do whilst logged in, etc etc.
Don't forget to wear the feathered Can Can outfit when you go to see the hot lawyer; turns out she's a cross dresser.
This happens all the time; company backs up a server, and sends the tapes to an offsite storage firm. That tape is chock full of software which states you can't copy it in any way. But, you say, fair use covers a backup! But any company who wants to keep their data keeps many many historical and working backups. Good to see that most companies in North America are raging software pirates.
I agree with you completely on these points; war is a nasty business, and it's no sense in making it worse than it needs to be. And both sides do need to both adhere to certain rules, especially these days, or the nukes'll fly. But it's still war, and Entropy-based warfare doctrine points out that the quickest way to win a war is to shatter supply lines, deny him information, then give him a quick, good smash, and watch him crumble. Also, being Canadian, I was both surprised and proud to see your example. I assume you're American, and if so, I thank you for not living up to the American-centric stereo type. :-)
Don't forget, also, that under the Geneva Conventions of War (a laughable thing) bullets aren't supposed to fragement, and they're supposed to blow through, rather than get stuck in the body somewhere; it's more humane that way.
You ever watch birds fall off of microwave towers?
Actually, in a mass battle, wounding is more effective than killing. Besides the moral effects, kill an enemy, you've taken out an enemy. Wound one, you've taken him out, plus two people to carry him, plus medics to treat him, plus logistics to support him, etc etc.
Very true, but mainly because the code wan't written with portability in mind. It's a shortcoming, a flaw, not a feature, not a property. Of course, it's also because alot of the software you cite is either written to a specific platform, or using a language that tends to be platform-centric. I'm merely trying to point out that you made far too broad a statement.
Yeah. That's why 'make apache' works on my x86, but not my SPARC, my PPC, my MIPS, or my S/390. Wait a minute.....IT DOES!
Most of the natural resources that our society relies on, we've either already exhausted to the point where you can't get them without heavy tech help, or you need tech to build them. Five hundred years ago, you could pick up red rocks, smelt them, and oh look, Iron. Not now a days.
The problem here is that we've already got frames of references for all of those symbols, and will unconciously attempt to apply those notions to the symbols.
No, they tend to release a box set FIRST, then release individual DVDs. The UY DVDs from the first box set are going to start coming out individually very soon now.
But you forget to mention that the DOT will publish the specs for the road, and has been upgrading the road on a regular basis, and all cars that expect to drive tout the fact that they're DirectROAD 7 compliant anyway. Besides, what's to prevent somebody from coding up a 'virtual pixel shader' that does it in software? By that logic, nobody should have supported the Voodoo 1 or anything like that! Then EVERYBODY would have to buy an expensive 3d video card!
I'd presume he means that you can't export a ReiserFS filesystem as an NFS share.
Nope. The last two are ways to get somebody to do something against his will. Not reasons somebody themselve will turn treasonous.
Not quite. But cartridges are right out, due to cost, time to manufacture, and limited space.
until they read "Game Over: Press Start To Continue." Excellent book on the history of Nintendo. Don't count Nintendo out; the N64 was a failure, yes. By Nintendo standards. Any other company would have considered it a fantastic success.
Yay Ottawa! My first college co-op was for National Defense. Keep in mind, kids, co-ops are like shit. There's plenty to spread around, nobody wants to step in it, but it'll float to it's proper level, and it's a prime ingredient for growing things. In other words, go in expecting the world, you're in for a grand disappointment. Go in prepared to demonstrate your skill and abilities, and you'll probably be given tasks consummate with said skills and abilities. But nobody likes a teen-age punk know-it-all whiner; at that point, you're fufilling stereotypes.
You forgot number 3: valuable contacts. FUCKING VALUABLE 'networking.' In my college course (university is right out; I didn't want an education. I wanted a job. And as a Senior Systems Administrator at 23, who has co-ops of his own ;-) I think it all worked out) literally 2/3rds of the class (who wern't weeded out, at least) didn't graduate because their co-op employers begged them to stay on. Myself included.
I was a co-op student, and I make a point of hiring them whenever I can, as co-op is a wonderful concept. I try to make it interesting, and educational, and blah blah blah, but the simple fact of the matter is that there's a lot of 'scut' work that pops up. And a lot of it gets dumped on the person who's other tasks would suffer least, from a business point of view. Guess what; if there's a co-op, it's her. But here's something that most co-ops never realize: if the co-op wern't there to do it, it would still get done. It would still be there. We're not creating the scut work specifically to give to you, and yes, guess what, for every exciting relational database you get to design and implement, there will be thousands and thousands of crap assignments; inventory, renaming documents, etc etc etc. Might as well learn that fact now.