Abortion Procedures

July 31, 2015

Here's an eight and a half minute video detailing common abortion procedures:

What is Driving the Confederate Flag Controversy?

July 17, 2015

Once upon a time, the Confederate flag was tolerated, even by those who didn't like it or understand it. Today, however, the flag is under attack from almost all sides. State, county, and city governments are being forced to remove the flag from their buildings, cars, uniforms, etc. by activist groups who are suddenly gaining national spotlight. We're told that it's because these are symbols of hate, but even blacks are standing up and saying that's not true. We're told that it's good for people to remove the so-called symbols of hate, but since when did anything that was actually good for people become a matter of national controversy?

Eric, from Eric Peters Autos, has a different explanation:

There is a very good reason why the Confederate flag is under attack. It is because it is the rebel flag. The flag of resistance, of (as columnist Fred Reed so neatly – so accurately – put it)… leave me the hell alone. This is why it’s favored by rural whites whose great-great-great grandparents never owned slaves nor wanted to – but who can’t stand annoying busybodies (they call ’em Yankees down South but the principle applies generally) who seem to think they are god’s anointed, sent hither to instruct and enlighten.

Who cannot stand the idea that others (anywhere) might hold differing opinions, do things differently – and so must be compelled to hold the right opinions, do the right things.

As the Yankees define these things.

Think Hillary Clinton.

But Bill will do, too.

For that matter, so will George Bush. And Chris Christie.

Obama, too.

They’re all the same, notwithstanding the color of their skin. Or of their party. The federal party. The party of government. Of control.

Of… everything.

Absolutely every last little thing. Down to the size of the cola you’ll be allowed to buy. And very soon, the opinions you’ll be allowed to hold.

Or at least, to express.

...

<source>

InfoWars: US Preparing Coup to Prevent Greece from Falling Under Russian Influence

July 6, 2015

According to InfoWars:

The United States and Germany are prepared to engineer a coup in Greece to keep the country operating as a strategic asset on NATO’s vulnerable southeast European flank.

“A putsch in Athens to save allied Greece from enemy Russia is in preparation by the US and Germany, with backing from the non-taxpayers of Greece – the Greek oligarchs, Anglo-Greek shipowners, and the Greek Church,” writes John Helmer, the longest continuously serving foreign correspondent in Russia not connected to the corporate media.

The primary tip-off something is brewing can be detected by the presence of Victoria Nuland, assistant secretary of state for European and Eurasian affairs, in Athens in March.

...

<Read More>

Fedora 21 and the NVIDIA Display Driver

April 1, 2015

I just installed Fedora 21 a few days ago on an old laptop with a GeForce 6600 Go mobile video card, and like I've done many times with many versions of Fedora over the years I installed the RPM Fusion repositories (both the "free" and "nonfree" repositories that they offer) and then installed the NVIDIA driver. Unfortunately, this time after I rebooted the system I was greeted with a black screen where the login screen should be.

Obviously I assumed I had screwed something up, and the next day reinstalled Fedora 21 from the basic "Workstation" DVD I had burned, only to go through the same problem. In my troubleshooting what I had found was that the version of GDM (the window manager from the GNOME desktop, which has been the default window manager in every version of Fedora Linux, at least as far as I know) that is used in Fedora 21 seems to have issues with the official NVIDIA driver, or at least the 304xx version that was needed for the old video card in this old laptop.

Fortunately I am a KDE fan, and I had already installed KDE by using the following command (the part on the end is necessary to avoid a package conflict bug):

yum groupinstall kde-desktop-environment --exclude fedora-release\*

My intention to use KDE rather than GNOME made the solution I found rather easy, and something that I had planned on doing eventually anyway just to get the login screen from KDE rather than the one from GNOME.

The biggest issue that I ran into while trying to fix this was simply that I could not access any sort of console to debug the issue, even when booting in the recovery mode, unless I first booted from a disk and deleted the /etc/X11/xorg.conf file. This of course breaks X when booting from any kernel (even recovery mode), but it allowed the Ctrl+Alt+F2 shortcut to switch to the console so I could log in as root and run commands.

From there I simply ran the following to uninstall the NVIDIA drivers, install system-switch-displaymanager and KDM so that I could switch to the KDM window manager (and thus switch to the KDE login screen, and then reboot the system):

yum erase *nvidia*
yum install system-switch-displaymanager
yum install kdm
system-switch-displaymanager KDM
shutdown -r now

After the reboot, at the login screen, I used the Ctrl+Alt+F2 shortcut once again to quickly get to the console and log in as root, and I installed the NVIDIA drivers and rebooted the system with the following commands:

yum install mkod-nvidia-304xx
shutdown -r now

After the reboot, the NVIDIA drivers were working fine, and the login screen displayed like normal. I did need to make sure to change the Session Type to KDE Plasma Workspace in order to get it to load KDE, however once I did that I was able to log in to my beloved KDE desktop without any issues.

Of course, GNOME still does not work, even after changing the window manager to KDM. I assume there is some sort of bug in GNOME/GDM that is causing it to fail to load when using the official NVIDIA drivers, however I don't have any inclination to debug it further. I don't particularly like GNOME 3, and I am more than happy to be restricted to only the KDE desktop (I have not tried MATE, Xfce, LXDE, etc).

Obviously I could have avoided a lot of frustration and wasted time had I simply installed from the KDE spin of Fedora 21, however I had already burned the basic Workstation disk for Fedora 21, and since it was OK installing to the XFS filesystem that I like so much I decided not to try the KDE spin as I was afraid that like Fedora LIVE disks of the past, it would not be able to install to anything other than the Third Extended/Fourth Extended filesystem.

Update (4-2-2015)

After going through all of the above, I tried to turn on KDE's "Desktop Effects", which are COMPIZ-like graphical effects that require hardware acceleration via via an OpenGL compatible video card (I had disabled it since it made the KDE desktop almost unusable when X was still using the hideous nouveau driver). The Desktop Effects failed to activate, and after hours of troubleshooting I found that X was not loading its GLX module for some unknown reason.

I followed the advice at this link to enable GLX using the nvidia-xconfig command-line tool that comes with the NVIDIA drivers by running the following commands (as root of course):

nvidia-xconfig --add-argb-glx-visuals
nvidia-xconfig --composite
nvidia-xconfig --depth=24

After restarting X, I found that it was now loading its GLX module, however rather than loading the one from NVIDIA like it was supposed to it was loading the default GLX module from the X.org Foundation, which does not work with the NVIDIA drivers. The Xorg.0.log file shows a line that says ModulePath set to "/usr/lib/xorg/modules", however it does not show any other module paths, which is odd since the file /etc/X11/xorg.conf.d/99-nvidia.conf clearly defines the following two module paths (in the same order as below):

  • /usr/lib/nvidia-304xx/xorg
  • /usr/lib/xorg/modules

I am assuming that this file is not being loaded by X for some reason, however Xorg.0.log does not indicate why, nor have I been able to determine where else the module paths are being defined so that I can edit them. At this time I am not certain if there is a way to change these paths, as my knowledge of X is rather minimal.

I did come up with a temporary solution to this problem, however please note that it is a very cheesy hack, and will more than likely break GLX support once the NVIDIA drivers are uninstalled (unless of course you undo it manually when uninstalling the NVIDIA drivers). Here's what I did:

  1. Navigated to /usr/lib/xorg/modules/extensions in my file manager.
  2. Renamed libglx.so to libglx.so.bak to ensure that it didn't get overwritten.
  3. Navigated to /usr/lib/nvidia-304xx/xorg, where there is a symbolic link with the same name as libglx.so.
  4. Copied the libglx.so symbolic link from /usr/lib/nvidia-304xx/xorg to /usr/lib/xorg/modules/extensions.
  5. Edited the copied libglx.so symbolic link to change the "Points to" path to /usr/lib/nvidia-304xx/xorg/libglx.so.304.125 (which is the actual NVIDIA GLX module).
  6. Restarted X, and found that the NVIDIA GLX module was now being loaded.

As you can see, this is certainly a cheesy hack, and I'm sure there is a much better way to fix this than what I did. If I figure it out I'll add it below in case anyone else needs the information.

Update 2 (4-2-2015)

Just on a hunch I undid the changes I made to the libglx.so file (restoring the original file), and then I tried adding the contents of 99-nvidia.conf to my xorg.conf to see what would happen. This resolved the issue, and Xorg.0.log now shows both module paths just like it should. Here's my current xorg.conf file for those who are having similar issues:

# RPM Fusion - nvidia-xorg.conf
# 
Section "Device"
     Identifier "Videocard0"
     Driver "nvidia"
EndSection

Section "Files"
     ModulePath "/usr/lib/nvidia-304xx/xorg"
     ModulePath "/usr/lib/xorg/modules"
EndSection

That's all that was necessary to get it to work right.

Police Intercepting Cellular Phone Calls?

March 26, 2015

The accusation has been levied by some that the police (almost all city, county, state, and federal police/enforcement agencies) have a device called "Stingray" that is capable of pretending to be a cellular tower, so that cell phones will connect to it, and thus listening in to phone calls or even recording them. The idea is that they can keep tabs on criminals using this technology, but the technology is not accurate enough to target specific individuals and so all cell phones or random cell phones would be picked up and conversations inspected to determine if the person the law enforcement agency was trying to monitor was the one placing the call. As an example of some of the reporting on this topic, here's a video of an interview with John McAfee about the device, its capabilities, its uses, and software capable of notifying you when your phone has connected to a "Stingray" device rather than a real cellular tower from your cellular service provider:


For those who are skeptical that such a device may exist, then I feel it important to point out that at a popular security conference called DEFCON (specifically DEFCON 18, which took place between July 30th and August 1st, 2010) a live demonstration was made by Chris Paget where he was able to set up a fake cellular tower and force cell phones on the AT&T network to switch over to using it, and even record data going from the phones to the service provider over the Internet connection. Here's the video of that presentation (including technical explanations):


You can also download the full video from the DEFCON website at this link.

The ATF Has Proposed Banning M855 Ammunition

February 26, 2015

As many people have already heard (thanks to groups such as the NRA widely circulating news about this), the ATF (Bureau of Alcohol, Tobacco, Firearms and Explosives) has proposed a ban on the popular M855 rifle cartridge (often called "Green Tips" due to the green paint on the tip of the bullet) for firearms that are designed to shoot the popular .223 Remington/5.56x45mm NATO caliber bullet (such as AR-15 rifles, and many others). For those who want more information about the ban and why it has been imposed, but do not want to read the NRA's article, then here's a link to an article from Forbes about the proposed ammunition ban.

It is, of course, important to understand that this ban has merely been proposed, and that it has not been made an official regulation yet and will not be enforced until it makes the change from being proposed to actually becoming a regulation. It is also important to note that the change to the way M855 ammunition is being handled by the ATF is not an actual change in law, but simply a change in whether or not the ATF considers the M855 ammunition to be considered an "armor piercing" ammunition "which may be used in a handgun", which would make it illegal under the Gun Control Act of 1968 (as mentioned in the article from Forbes).

For the purposes of understanding what the Gun Control Act of 1968 does define as "armor piercing", here are the two criteria listed on the ATF website:

  • A projectile or projectile core which may be used in a handgun and which is constructed entirely (excluding the presence of traces of other substances) from one or a combination of tungsten alloys, steel, iron, brass, bronze, beryllium copper, or depleted uranium;
  • A full jacketed projectile larger than .22 caliber designed and intended for use in a handgun and whose jacket has a weight of more than 25 percent of the total weight of the projectile.

For those who don't already know, the .223/5.56 bullets are ".22 caliber", and thus the second criteria does not apply. Therefore, we have to establish whether the first one can apply. Forbes already discusses whether or not .223/5.56 ammunition can be used in a handgun, and while they do briefly mention whether or not the core of the bullet is made of the metals listed in the first criteria, I thought it might be a good idea to have a firearms expert show exactly what is inside the M855 "green tip" bullet. Here's a video from Jerry Miculek where, after 2 minutes and 30 seconds of satire (you can feel free to skip that part) he shows a few examples of bullets that have been cut in half so that you can see the inside, and explains what makes up the M855 bullet:


For those who are opposed to the proposed ban, the NRA has a form to contact your legislators and the ATF about it at this link.

Adam Kokesh Interviews Former New Orleans Police Officer on Police Corruption

December 12, 2014

This isn't a new video, but it's probably one of the best videos that establishes the reasons behind Adam Kokesh's distrust of police, and mine as well. A former NOPD (New Orleans Police Department) officer explains to Adam Kokesh why he not only quit the force, but also why he has been working to expose corruption in the NOPD and testifying in court and to the FBI regarding those issues.