- ActivistPost – 10 Things Citizen Spies Should Report to DHS
- alec exposed
- AntiWar.com – OKC
- Architects & Engineers for 9/11 Truth.
- Be Prepared, With The DHS Extremist™ Lexicon (pdf)
- checkpointusa – keeping unlawful checkpoints in check
- Cognitive Infiltration | Punishing Paranoia (pdf)
- Core of Corruption
- Cryptome.org | Similar to Wikileaks, Lots of Docs
- Intel Wire
- Investigating the Terror
- Is Yo' Momma an Extremist™? | You Might Be Surprised! (pdf)
- Know Your Rights | EFF Explains How to Deal With Digital Terrorism™
- Leaked G20 Documents(pdf)
- okcbombing.net – terrible terrorists who ask terrifying questions
- Section 5150 | Thought-Crime Division
- sourcewatch.org – September_11th_Advocates
- There Are No Conspiracies? | Ask Carlin (youtube)
- Think Like a Cow | Or, The Gubment's Advice on Conspiracy™Think®
- Activist Post
- Amber Lyon
- BoilingFrogsPost – Powerful, direct, and frightfully informative
- Investigating the Terror
- john pilger
- Leaked G20 Documents(pdf)
- Mad Cow Morning News
- Project HumanBeingsFirst
- Reasoned Rebellion | MarkMcCoy.com
- sourcewatch.org – September_11th_Advocates
- AGI Manhattan Project
- alt-market – ?
- CIA CREST Database | Try: "Remote Viewing"
- CIA Family Jewels | Depressing (27MB pdf)
- Ignorance is Futile
- Internet Archives | WaybackMachine
- MK-ULTRA | Old Depressing Stuff
- Not My Tribe | Blog, News, Ideas
- Organic Design
- Orlando Copwatch
- Radio Free Penzance
- reason and jest
- RebelScience | COSA
- The Black Vault | Interesting FOIA Documents
- the intel hub
- Various Released FOIA Requests | gwu.edu
- what really happened
- wu wei cafe – expand the melon, and more
- "The Suicided – People who died exposing the truth"
- 137 UFO Researchers?
- 911 suspicious deaths
- BP® Murders? *You decide*
- Christopher Story – Unverified, Interesting, Pending
- Danny Casolaro – Inslaw
- Danny Jowenko – demolition expert
- David Kelly – British UN weapons inspector
- Dead Journalists
- Dr. Fahmy Malak – adventures in death and deception
- Gary Webb – Dark Alliance
- Interesting Video and List
- Kenneth Trentadue – OKC
- Mark J. Harper's List of Dead Scientists & Microbiologists
- Matthew Roy Simmons
- Mysterious Death List – High Profile People
- Mysterious Deaths – Circa Clinton Administration
- Robin Cook – Parliamentarian
- SteveQuayle.com – Some truth, and a bit of disinfo; particularly that of Matthew Allison (no records)
- Sunny Sheu
- Terrance Yeakey – Oklahoma City Bombing First Responder
- Vince Foster
- Water Car – video
- William E. Colby – CIA
- 1. The Corbett Report – EIA's Favorite
- Alan Watt – Audio Links | Not "Alan Watts"
- Before it's News
- Documenting the Obama Administration's 'Gitmo in the Heartland'
- Eric Draitser — Highbrow Analysis of International Affairs — Excellent stuff!
- flow of wisdom (.com)
- FreeDomainRadio | Stefan Molyneux
- Katherine Albrecht | Privacy Pioneer
- Republic Broadcasting Network
- The juice media | Robert Foster
- TNS Radio
- Weather Wars – Scott Stevens
- Zero Point Radio
Category Archives: Linux
——– Instructions Here ——–
When I first encountered Zeitgeist on my system I immediately thought “WTF?”. I looked into it a little further and asked the same question again. What surprised and alarmed me was discovering its [co]dependencies. Why would developers ever consider integrating this wanton antic into so many otherwise useful things? I’ve begun to wonder; is this the future of mainstream Linux? Will the chosen applications of a very few be not just installed by default, but tangled into other vital elements of the system?
Here’s a description of the application by it’s developers:
” Zeitgeist is a service which logs the users’s activities and events, anywhere from files opened to websites visited and conversations. It makes this information readily available for other applications to use in form of timelines and statistics. It is able to establish relationships between items based on similarity and usage patterns by applying data association algorithms such as “Winepi” and “A Priori”
Zeitgeist is the main engine and logic behind GNOME Activity Journal which is currently seen to become one of the main means of viewing and managing activities in GNOME version 3.0 “
I suppose if I was high enough, or after enough strong ale, this might sound interesting in theory. But in practice, it sounds absurd and I have no doubts that I can live without it. It seems suspiciously related to the pestiferous bubble-ization of the Desktop, with recent cavalier attempts by Unity and Gnome3 to
ethnitechnically-cleanse the power-users for the coming legions of iPhone zombies who care nothing about managing their own systems.
After removing Zeitgeist on my own system, no decrease in performance of any sort has been observed. This makes me wonder why such a nosy application would be installed by default along with obstructions for its removal, all when it offers no clear advantage. But most importantly; why is there no easy option to simply disable it without hacking it to death?
Please see “instructions” link at top of post.
Instead of adding anything to your repositories just to toggle your touchpad “on” or “off”, below is a script that when run in terminal will accomplish the task.
1 2 3 4 5 6 7 8 9 10 11
#!/bin/bash echo "Enter a number (1) or (2) to toggle touchpad off/on"; select yn in "off" "on"; do case $yn in off ) synclient TouchpadOff=1; break;; on ) synclient TouchpadOff=0;; esac done
Copy and paste the code above into a text-file with the “.sh” extension, make it executable and toggle your touchpad on/off at will.
This works for me in Linux Mint (Maya/Mate) and should work fine in other Ubuntu-based distros.
*Note on the embedded code:
If you use WordPress and would like to embed code in your posts, WP-Syntax is what was used above. I’ve tried many others and dislike them all. So far, I am very pleased with WP-Syntax.
A direct link to the plugin: wordpress.org/extend/plugins/wp-syntax/
If you ever forget to activate the touchpad before packing up and going somewhere without your mouse, simply do:
# navigate to the script directory and enter:
./”name of script”
# and enjoy a reactivated touchpad; or alternatively, commit the commands to memory.
1, 22, 2012
After more than a year of rigorous use, I have joyously retired my nearly indestructible, but buggy (in Linux) Toshiba laptop. I purchased it new, and with it came Windows 7 — which I’ve used on no more occasions than can be counted in the far-eastern half of an octet. Within the same hour of buying it, gparted had done its work, and Ubuntu was installed. It served me well, and still serves ssh/sftp sessions despite its tattered state.
Like many Linux users today, Ubuntu was my first distro. The concept of transparency and freedom was all I needed to venture beyond the proprietary opaqueness of Windows. I still remember the excitement of stepping into the great OSS outdoors — to the point of conceivable embarrassment. Admittedly, back then, Ubuntu was astonishingly excellent. I suffered a hearty quota of frustration in transit; though no matter how confused I became, nor how many times I had to format and reinstall, I trudged forth and away from the prison Gates…
That was five years ago, when Feisty Fawn was the beast of necessary burden. Since upgrading from Karmic Koala, I have been using Lucid Lynx (LTS) and enjoying every day of it. When Shuttle
worthsoft pulled from the id of OSS™, Gnome3 & Unity, I cringed, but figured I needn’t begin worrying much until 2013. Spooked by Canonical, I decided to experiment with an alternative anyway. A few months ago I installed Arch Linux on the Toshiba, but never made it past “startx”, which only returned error messages. I got the network up, tinkered around a bit, and after failing again and again to solve video issues, and with pending tasks, I crawled back to Ubuntu, humiliated.
Last week, a long-time Linux-user and digitally weathered acquaintance who had recently moved from Ubuntu to Arch, suggested I do the same. After making several Toshiba-based excuses, he offered to let me have a go at his old Asus laptop, but under the implied condition that I use it for Arch. The Asus was in ugly shape; the monitor casing had come apart and wasn’t gripping the hinges, and a previous attempt at repairing it with epoxy had glued the lid-sensor into a logically-closed state, preventing the boot process. It was also filthy internally and externally.
After an application of J-B Weld and 24 hours, the monitor, (assuming it won’t need be opened again) is better than new. As for the lid-sensor, I filed away the epoxy and soon after, proceeded with /arch/setup. Being spoiled by Ubuntu, and with my last experience, I was a little stressed. However, unlike the Toshiba, the Asus worked flawlessly, and despite its substantially inferior hardware (1G PC-2 RAM, DualCore @2GHz), outperformed the Toshiba (3G PC-3 RAM, DualCore @2.4GHz) without any of the annoyances.
Along the way, I encountered a few things to be confused about. The first was the “Packages” part of the installation, and perhaps the installation process in general. When I realized I had a net-install CD, and no physical access to a router, I panicked a bit, expecting common wireless issues. Following the Arch Wiki documentations, there were no problems, and long before expected, KDE and Xfce were installed on my new Arch system, I was checking email, and watching videos. There was still some tweaking to do; pacman.conf had to be adjusted, modules and daemons had to be added to rc.conf, and I had a ton of stuff to install and configure. Just as I was feeling somewhat comfortable, it was mentioned that Arch finally initiated long-awaited package-signing. Not to be passed up, I went straight to it, and was soon stuck. I pestered the fellow who gave me the Asus, but was reminded of the Arch Way and instructed to keep reading. Eventually, due to great documentation and a little advice, I completed the process. I am still encountering some difficulties when trying to install certain packages, and I still have yet to figure out exactly why — but I am happy enough to have package-signing to look forward to, There are a few other things still perplexing me, though between patience and trial/error, they should become more clear.
Aside from the annoying consequences of things yet to be properly understood, installing and getting a functional Arch system was much easier than anticipated. I had to pester that fellow a few times, but altogether I think I’ve finally found a Linux distro worthy of confidence which can be customized and kept to my liking. I might not advise that Linux newbies start with Arch, though it’s not impossible, and I wholly recommend it to anyone with a little more experience, or to anyone who really wants an intermediate Linux, free of bloat and other strange things. It may also be wise to go through the Arch installation process in virtualbox before trying to dual boot with an existing OS. If planning a full install, simply make haste and have no worries.
One thing I cannot praise enough is the pacman package-manager; it’s simple, effective, and just plain excellent. The rolling releases model is quite appealing too; update what you want, and not what you don’t, and never have to reinstall Arch! I am also impressed with Xfce; while I miss certain panel-features/apps in Gnome2, I am finding it more and more acceptable. After three days of using Arch, I expect it will become my primary and permanent OS. For midi music-production and possible backup OS, I may add a Mint or Debian partition — unless midi goes smoothly in Arch. I’ve had some difficulties configuring an aliased (secure) Skype, finding trouble harmonizing Alsamixer and Pulseaudio, and am still having other sound difficulties; though I hope to sort them out, and stay put.
After the necessary initiation of package-signing, I proclaim the Arch name dignified. In my opinion, Arch is at the top. For vanity’s sake, I’ll not admit exactly how long it took me to attain a functional, productive Arch system — but I will tell you this: It has so far been worth every minute spent, and I would have only regretted never trying. I might have floundered around in Ubuntu until 2013, wondering what I was missing.
With its growing community, I can easily foresee Arch continuing to improve. It has been said that their documentation is the best, and I can believe it. So far, I have no complaints. I am still shaking off residual newbie-ism; however, Linux has become almost an extension of myself, allowing me to do things otherwise impossible. I value it highly, and aspire to someday contribute to it. In my opinion, Arch preserves the spirit of Linux. For those who want an OS to call their own, it’s a fine choice.
Notes & such:
Wireless: Intel PRO/Wireless 3945ABG chip, which seems to work perfectly in Linux.
There was an odd bug I often experienced in Ubuntu, which hasn’t bothered me since switching to Arch and using Xfce. Loading certain images would cause a user logout. I lost more than few things, and suffered a lot of rage as result of this. It occurred mostly while using firefox, and especially when visiting wunderground.com. This was one of the most annoying and serious bugs I’ve ever come across, and it would occur frequently. I would have a dozen browser-tabs open, text editor, and applications running, and then have to manually restore most it just because I loaded a damned image. I was never able to find a suitable explanation in the forums either. The bug seemed pretty exclusive to Ubuntu (and Mint) — I was using Lucid (LTS). Good riddance!
While I hate to admit it, the difficulties with sound defeated me. I got sick of hearing everything I did through the speakers. I got terribly sick of my microphone only working locally and not through applications (skype). I was willing to live with an unfixable suspend mode, where the system would freeze upon resume (about 75% of the time). But after days of pulse versus alsa, and absolutely no progress, I formatted again.
It seems to me that sound would be a top priority in the documentation, but I found none that helped. However, to be fair, it must be said that Intel has been unfair. The HDA Intel is strange, but even stranger is that it works perfectly in Ubuntu with no additional configuration.
I conclude only a little differently than before; if your hardware is friendly, try Arch. If it is not, well, then prepare for some serious frustration. If ever I find the right machine, Arch will be my first choice of OS.
According to The Register, US Military spy-drones may be tossing Windows and switching to Linux. If so, the community may finally get a piece of the action, and geeks will have compensation for lacking machismo. With the help of Shuttleworth™ and Unity, the interface could be very user-friendly for teenage recruits remotely piloting the drones, and would look comfortably similar to their iphones. Stallman may object to proprietary hardware, but no one will listen. If gnomes are involved, Torvalds may warn of an “unholy mess“, but Clem could tidy it up with a little cinnamon and a fork.
With colossal nemeses like Apple and Microsoft, Linux could use the popularity. There’s nothing like boasting responsibility for civilian casualties, massive surveillance capabilities, and wielding the potential power of the open-source community to Unite™ and steer their drones toward conscientious objectors. It is even possible that people could be intimidated into using only Linux, under duress of large – but invisible – bombs.
Benevolent angels such as SOPA and the DHS should discourage government abuse of GPL — and there should be plentiful counter contributions as well. The harmony between the intrinsic transparency of OSS and that of US Government, would be the perfect match for openness and accountability.
All in all, I foresee jubilee, and better drones. Linux is about freedom, and the US Government is too. Let the penguins fly again – with a vengeance!