Dear Media

Please stop. Please stop making martyrs out of these weak-minded, cowards who cause wanton death and destruction of innocent people. Don’t even show their face or mention their name. Doing so only emboldens some other sick individual (or groups) to do the same thing, because they know you will shine a spotlight on them and whatever misguided belief system they may have. Just put up a silhouette with the caption “Unknown Assailant” underneath it. Don’t delve into their past, their family, claimed associations or whatever you think will give you better ratings. What you should do instead is do a story a day for the number of victims that had their lives cut short by some spineless caitiff; in other words, so that you can understand, if there were 49 victims, a story for 49 days covering each victim. Celebrate them.

I’m not saying don’t report the tragedy. What I’m saying is that you should maybe use a little discretion when reporting, instead of the shock and awe you typically do to get higher ratings.

And that’s all I have to say about that.

Posted in General | Leave a comment

CentOS – Less Command Workaround

I use c-shell (tcsh) as my shell; have been from 25+ years. I know, I know, bash is supposedly better, but I’ve never had issue using c-shell and it’s what I started with. Anyway, I recently switched one on my VMs to CentOS and found that the less command insists on sourcing .cshrc. This is fine provided you don’t have any output (i.e., echo command). If you do, or have a menu selection (like I do for a certain user), then less will just use that output versus the file you want to look at. I should note, the doesn’t appear to happen in the bourne shell (or derivatives of it), nor is it a problem in other Linux distros, but I’m not switching. To workaround the issue, I create a simple less.csh script with the following:

#!/bin/tsch -f
setenv LESS_CMD 1
setenv LESS -Xe
/bin/less $argv
unsetenv LESS_CMD

I then add the following to the beginning of ~/.cshrc:

if ($?LESS_CMD) then
  #echo executing less
else
  # ... normal processing
endif

I shouldn’t have to do this because I’ve never seen this behavior in any other Linux distro, or any other *NIX OS (Solaris, AIX, HPUX, etc.) for that matter either. So it seems to be something unique to how CentOS is building less that causes it to behave differently under c-shell.

And that’s all I have to say about that.

Posted in Geek, Linux, Scripting | Tagged , , , , , , , | Leave a comment

Cosby

Today (December 30, 2015), Bill Cosby was charged with felony sexual assault from an incident that occurred in 2004. For the past year or so there have been a number (a lot actually) of similar allegations (some settled in civil court) thrown at Bill that span ten or twenty years, but this is the first one that has resulted in criminal charges.

Now I don’t condone any of what Bill is allegedly accused of. If he did these heinous acts, then he should get the punishment he deserves. We don’t know that yet because 1) it hasn’t gone to trial and 2) he hasn’t been found guilty of said crimes. If you went on Twitter (or any other social site, or read the comments section on an online news outlet) though, you would think the trial already occurred and that Bill was already serving what remaining years he has left behind bars. See, in this country, the United States of America, one is innocent until proven guilty. While not specifically spelled out in the U.S. Constitution, the 5th (protection against self-incrimination), 6th (rights related to criminal prosecution) and 14th (due process) amendments imply it. So, before people cast judgement, of which they are wholly unqualified to do because they don’t have all the facts and/or evidence, maybe we should let the legal system, no matter how fixed you may think it is, do what it’s meant to do instead of adapting to the mob mentally or blindly believing what some celebrities say. Which brings me to my next point.

Apparently, back in the day, the comedy world knew all about Bill’s exploits; it was just common knowledge. Comedians like Patton Oswalt, Bobcat Goldthwait and Roseanne Barr; I’m sure there are more. My question is this, why didn’t they speak up and say something, or, at the very least, make an anonymous call to the police? Maybe, just maybe, if they had the spinal fortitude to do that back 10, 15, 20 years ago, more women wouldn’t have (allegedly) been assaulted by Bill. I know if it were me, and I heard these things were going on, I would have reported it to the authorities and certainly not brag years later (after being comfortably ensconced in my career) that, while I knew all about it, chose to remain silent.

And that’s all I have to say about that.

Posted in General | Tagged , , , , , , , , , , , , , | Leave a comment

Re: CentOS – VirtualBox Shared Folder

Yesterday I wrote about how to work around CentOS 7 in a VirtualBox environment not automaticaly mounting shared folders. While that method will work, it’s not the most correct answer. A better answer is to create a /etc/modules-load.d/vboxsf.conf with the following entry: vboxsf. After reboot, you should then see a similar type message in from dmesg:

automount vbsvcAutoMountWorker: Shared folder 'Documents' was mounted to '/media/sf_Documents'

I still think this is unnecessary, but is a cleaner method than hacking /etc/rc.local.

Just goes to show that there’s more than one way to do everything in software; especially Linux.

And that’s all I have to say about that.

Posted in Geek, Linux | Tagged , , , , , , | Leave a comment

CentOS – VirtualBox Shared Folder

I’m not sure if this is just a thing with CentOS or what, but I experienced some difficultly in getting shared folders to mount inside the a CentOS VirtualBox image. What I found was that the vboxsf kernel module was not loaded as indicated by the following message in dmesg:

automount Error: vbsvcAutoMountWorker: Could not mount shared folder 'Documents' to '/media/sf_Documents': No such device (19)

The solution is to do:

modprobe vboxsf

Followed up with:

mount.vboxsf -o rw,uid<UID>,<GID>dmode=775,fmode=664 <SF_NAME> <MOUNT_POINT>

Where:

  • UID: default file owner user id to UID
  • GID: default directory owner group id to GID
  • SF_NAME: name of shared folder
  • MOUNT_POINT: where to mount the shared folder

To get this to happen at boot, add the following to /etc/rc.d/rc.local:

modprobe vboxsf
mount.vboxsf -o rw,uid<UID>,<GID>dmode=755,fmode=644 <SF_NAME> <MOUNT_POINT>

On CentOS, the permissions on /etc/rc.d/rc.local are set to 0644 (-rw-r--r--) by default so be sure to change permissions to 0744 (-rwxr--r--) so that it’s executed on boot.

I’ve been using Linux in a VirtualBox environment for a number of years, and this is the first distro I had to jump through so many hoops to get working properly. I won’t even get into the BS of having to deal with a proxy and getting YUM & RPM to operate properly in that paradigm; because why should those two programs not use the system level proxy settings, right? Wrong; they have a separate configuration for them to understand proxy settings.

And that’s all I have to say about that.

Posted in Geek, Linux | Tagged , , , , , , , , , | Leave a comment