I love F/OSS, but the Stallmans of the world are simply living in a wishywashy black and white fantasy land.
Any legitimacy you might have had, poof! Gone in one sentence so internally contradictory is sounds as if it was spewed by the Palintroid.
There's NOTHING "wishy-washy" about Richard Stallman. It seems on some dim level you already know this as you ratchet the words "black and white fantasy land" immediately, if obliviously, after the words that preceded them. Here's a clue: when trying to be cute, cut down on the doublethink unless irony and sarcasm is OBVIOUS.
Your knob-polishing of GNOME (Miguel's Microsoft project) has buried your reason so deeply under the ideology of convenience that it appears you'll love just about anything. Your pronouncement of love doesn't sound like a passion for F/OSS, or even a remotely basic understanding of what it actually *is*; it comes comes across as an overture to work in Redmond with Miguel.
Be about it, then; as others have noted, GNOME has sucked for a long time, and derivatives of Silverlight won't lift it out of Suckville in any case. Go your own way; just don't pretend the result will truly be FOSS because we certainly won't.
Whoa. Marvel is not, nor has it *ever* been, a source of "alternative media". If you want "alternate" comics, find some Slow Death, Love and Rockets, hell, even Cerebus (or perhaps The Boys, if you're into superhero meta-commentary/farce.)
I don't know what is more depressing: that you seem to think Marvel produces "alternative" comics or that they are alternative "media". Marvel is NEITHER; they are about PRODUCT, as is Disney. The two corporation were made for each other.
That being said, I'm dropping any Marvel titles I might have been following--I truly loathe Disney, and won't have any part of their "Disneyification" of culture. That's not a great loss, though: since Garth Ennis left Punisher, what does Marvel have to offer, anyway?
I believe the majority of what you say is bullshit. You're thinking of the department of Homeland Security, specifically the ICE. But modern cops do tend to be clueless about electronic crime.
Umm, are you even remotely aware of A Clockwork Orange? The idea explicated there, and seemingly jumping from the page into our little gravity well every moment, is nearly fifty years old now, so the original poster's contention that many stupid thugs find their way into law enforcement is not even a new or original observation of emerging social trends. If anything, ACO didn't go far enough in its speculation of how near-term "law enforcement" might look. It's a sad thing when fictional near-future-dystopias are outstripped by "reality".
But, more to the point, how many smart, or even reasonable intelligent cops have you ran across? If you've enough experience with Johnny Law to state how "clueless" they are when concerned with computer crime, surely you have some experiential anecdote that would validate that view, as well as invalidate the contention that street cops are one step removed from knuckle-dragging stormtroopers? And, sorry, articles posted on
From a soldier's point of view it is rather easy to understand why all of the population might appear to be an enemy. Often that is an outright fact.
Yeah, that particularly happens when the soldier is part of an invading occupation force with dubious intention. AND the soldier is conditioned to believe they are (racially, religiously, socially) superior to the locals they are "defending". AND they are products of a militarized culture that glorifies violence as it cynically prattles about honor and respect.
Perhaps, just maybe, if foreign policy of oppressors such as the Washington Consensus were attacked and done away with by the people responsible for them (you know, the supposedly "free" people who stand on the sidelines as their killers are loosed on the world), the ethics of creating killing machines more efficient than Special Forces or Airborne soldiers wouldn't be debated by arrested adolescents (who've never smelled the burning flesh of their "enemies") in meaningless online forums.
In such a world, your utter bankruptcy of anything decent would be appropriately pilloried for the imperial apologia it is. I guess, as it stands, you'll just have to settle for my contempt....
Find a place a majority of the group agree the testing can take place and the rest will get it blocked. The simple matter is that there are times when the "possible" harm to marine life must be acceptable.
So, what say we "test" some DU in the load bearing members of your house to "firm up the foundation" and "protect you from external threat". Even more, let's say you have NO SAY WHATSOEVER in such implementation, because, quite frankly, you don't count as a rational being that anyone should care about (I sure as hell don't care about you.) That sound about right to you?
Will Bush Cancel The 2008 Election?
by Harvey Wasserman & Bob Fitrakis
It is time to think about the unthinkable.
The Bush Administration has both the inclination and the power to cancel the 2008 election.
Among other things, ADC says:
"You probably aren't aware of the hierarchy out there amidst the media community. Access to information from vendors is based on your status within the hierarchy. The information a member of the press gets from a vendor is different from what's given to an analyst and is different than what a blogger is going to receive. Bloggers are not journalists and most are certainly not analysts. They can be a channel through which information is disseminated, making them invaluable to the folks in the trenches, true, but they can also be dangerous because they aren't bound by any rules. And that's what you're missing because you've not been a member of the press — you don't "get" the hierarchy and how information is disseminated through the ranks. And guess where bloggers fall? Yup. Stand up straight, there, private!"
It's an interesting take on the role of the blogosphere and their relationships with vendors. As a tech PR guy, I can tell you that ADC hits the nail right on the head about vendors' tenuous relationship with bloggers.
Here's the URL: http://www.theapplicationdeliverynetwork.com/?p=2
"The Future of Music Coalition — an advocacy group of musicians that fought radio consolidation — is assembling a lineup of name bands, such as R.E.M. and Death Cab for Cutie, to join the fight to keep the net neutral. The group will join net neutrality advocate Rep. Edward J. Markey (D-Mass.) for a teleconference today to kick off the campaign, which is called "Rock the Net
." The campaign will include a petition and a series of concerts. The coalition fears that if companies are allowed to charge for faster access to the Internet, it will hurt the ability of musicians to get their music out to their fans, especially small, indie bands.
The book is authored by Wolfgang Barth and published by No Starch Press. The publisher hosts a Web page which contains an online copy of the table of contents, portions of reviews, links to purchase the electronic and print versions of the book, and a sample chapter ("Chapter 7: Testing Local Resources") in PDF format.
An amusing note to begin: this is one of the only books I have read where the introduction was actually worth reading closely. Many books seem to talk about background or history of the subject without providing much pertinent information, if any at all. In Nagios: System and Network Monitoring, Wolfgang Barth begins with a hypothetical anecdote to illustrate the usefulness of Nagios. The most important section in the introduction, however, is the explanation of states in Nagios. While monitoring a resource, Nagios will return of one of four states. OK indicates nominal status, WARNING shows a potentially problematic circumstance, CRITICAL signifies an emergency situation, and UNKNOWN usually means there is an operating error with Nagios or the corresponding plugin. The definitions for each of these states are determined by the person or team who administers Nagios so that relevant thresholds can be set for the WARNING and CRITICAL status levels.
The first chapter walks the reader through installing Nagios to the filesystem. All steps are shown, which proves to be very helpful if you are unfamiliar with unpacking archives or compiling from source. Users who are either new to Linux, or cannot install Nagios through a package manager, will appreciate the verbosity offered here. Fortunately, the level of detail is consistent through the book.
Chapter 2 explains the configuration structure of Nagios to the reader. This chapter may contain the most important material in the book as understanding the layout of Nagios is essential to a successful deployment in any environment. The book moves right into enumerating the uses and purposes of the config files, objects, groupings, and templates. All of this information is valuable and presented in a descriptive manner to help the reader set up a properly configured installation of Nagios. My biggest stumbling block in using Nagios was wrapping my brain around the relationships of the config files and objects. This chapter clears up all of the ambiguities I remember having to work out for myself. If only this book had been around a few years ago!
The sixth chapter dives into the details of plugins that are available for monitoring network services. This chapter explains using the check_icmp plugin to ping both a host and a specific service for verifying reachability. Additional examples include monitoring mail servers, LDAP, web servers, and DNS among others. There is even a section for testing TCP and UDP ports.
Next, the book covers checking the status of local resources on systems. At work, we have a system in production that could have been partitioned better. Unfortunately,
Chapter 12 discusses the notification system in Nagios. You provide who, what, when, where, and how in the configs, and Nagios does the rest. The book does a fantastic job of explaining what exactly triggers a notification, and how to efficiently configure Nagios to ensure the proper parties are being informed of relevant issues at reasonable intervals. For example, the server team might be interested to know that
The last major chapter to mention here deals with essentially anything and everything about the Nagios Web interface. The main point of interaction between the administrator and Nagios is the fully featured Web interface. This chapter covers recognizing and working on problems, planning downtimes, making configuration changes, and more. I especially like that the book gives an overview of each of the individual CGI programs that the Web interface is composed of; as these files are important for UI customization.
The only aspect of this book that I did not care for was that the book reads like a reference manual at times. The first several chapters start out more conversational in tone with great explanations of the procedures and files; but later it sometimes feels like I am repeatedly reading an iterated piece-by-piece structure, filled in with the content for that chapter. That is not necessarily bad all together as it does provide consistency in the presentation of the information. Additionally, the level of detail is outstanding throughout the book. The explanations are never too short or too long. This is definitely a valuable book for administrators at all levels with fantastic breadth and depth of material. Administrators who are interested in proactive management of their systems and networks should be pleased with Nagios: System and Network Monitoring.
Nagios is licensed under the GNU General Public License Version 2, and can be downloaded from http://nagios.org.
David Martinjak is a programmer, GNU/Linux addict, and the director of 2600 in Cincinnati, Ohio. He can be reached at email@example.com."