Unix Revolution

#!/bin/sh PWD=`pwd` DATE=`date +%Y%m%d` ARCH=`uname -p` RELEASE=`cat /etc/redhat-release | awk '{ print $3 }'` # ****************************** # Add the admin Group and local Users - if not already there. # Set passwd to "Passw0rd" with a Zero # ****************************** if [ -d /home/jradtke ] then   echo "mv /home/jradtke /home/jradtke.${DATE} "   mv /home/jradtke /home/jradtke.${DATE} fi getent group admin >/dev/null || groupadd -g 6969 admin getent group jradtke >/dev/null || groupadd -g 2025 jradtke getent passwd jradtke >/dev/null || useradd -g 2025 -u 2025 -G admin -s /bin/bash -c "James Radtke" -d /home/jradtke -p '<encr passwd here>' jradtke # UPDATE THE SUDOERS FILE cat << EOF >> /etc/sudoers ## ALIASES Host_Alias      CRASHHOSTS = neo,neo.matrix.private,cypher User_Alias      CRASHUSERS = jradtke Cmnd_Alias      CRASHCMNDS = /usr/bin/systemctl restart ntpd.service, /b

NOTE:  Currently this post is easily my most disorganized to date.  There is a ton of information here, and unfortunately I'm not exactly sure what data is important, or not - and I can't explain how things work.  The significant positive point is that it does work. ;-) I can't believe it is even necessary to document this.  After 30 years of PCs they continue to make things pointlessly difficult and challenging. I have an Lenovo Thinkpad X1 Carbon with a 240 GB SSD.  Windows 7 is amusing and all, but I really prefer Linux.  Between UEFI, Secure Boot, GPT, etc... this has proved to be much more challenging than I had initially anticipated.  I guess the point that will exemplify my frustration - I don't know why I need all these stupid partitions, restore partitions.  I really did not have much of an issue with a BIOS and 4 partition drive to run my 2 OSes. This method will rely on the Fedora Grub boot loader.  I am not sure if this will wreak havoc on patching th

I was somewhat frustrated when network interface enumeration suddenly changed (around 6.3) in a seemingly random manner.  I noticed the madness now had a pattern... and regardless of my attempts to manually manage my interfaces using UDEV (as I had in the past) it would just screw everything up. So - I conceded and allowed the system to manage itself how it wanted and I discovered that was the best option. In the past, you may end up with eth0 being on a PCI card, while the onboard would be eth3.  Since the release of the new standard, the onboard are identified as em (for "embedded" I believe) and the other network interfaces are identified by slot number and interface (i.e. p2p1 - slot 2, eth 1). A person who posts on the Red Hat Customer Portal had an amazing find and submitted the following: ....Dell (who wrote biosdevname and released it under GPL) have two white papers on the subject at the project page: http://linux.dell.com/biosdevname/ From the Consistent N

At work, I have a desktop running Fedora which has an SSD.  I still am a bit old school, I suppose, and don't have as much confidence in their longevity.  I also realize that this is probably not a valid concern, particularly based on the way I use the disk, which is mostly reads.  Furthermore, I realize that my concern for losing a drive should be addressed in the same manner whether I have an SSD or an archaic spinning platter... So - I have an external disk which I backup to weekly.  I am moderately concerned about my desktop being compromised by someone at the keyboard, but I am more concerned that someone has the ability to walk by and see my external disk hanging off my PC and try to access it from another PC.  I have a slight advantage of being protected in that the average low-life probably doesn't know anything about Linux. NOTE: If you are particularly worried about security, do NOT create the keyfile which will force you to enter a passphrase each time. parte

sudo is certainly one of the most important aspects of *nix administration. Recently I had been tasked with allowing a number of individual users (which we could have created an OS group to contain) to sudo to another user, without a password.  That user should then be able to run some specific commands, also without a password. NOTE:  If you happen across this post, and know of a better way to do this, feel free to correct me.  This just happened to have worked for me and seemed clean and easy to follow. This is what I had come up with: /* Allow APPUSERS (techies) to         su to approot without a password     Allow approot to         run specific commands without a password         on APPHOSTS (localhost) */ [root@localhost ~] # adduser approot [root@localhost ~] # visudo ## TESTING ## ALIASES Host_Alias      APPHOSTS = cypher,cypher.matrix.private User_Alias      APPUSERS = techies,user1 Cmnd_Alias      APPCMND = /usr/bin/systemctl restart ntpd.service, /bin/

We have a position open for a Senior Unix Engineer. Great/fun work environment that is definitely quick, nimble and responsive - you need to be on your toes. https://careers-siriusxm.icims.com/jobs/7796/job /keywords Linux Job East Coast Washington DC Red Hat Administrator Admin RHCE /

On a quest to abandon all things apple... and not wanting to embrace Windows for anything other than playing half-life and occasionally running Visio...I am pursuing Fedora as my exclusive desktop OS. I am attempting to replace the Notes app from IOS and iCloud.com on my Linux desltop and Android devices.  Evernote seems like a good option.  However, there is not an Evernote client for Linux.  :-( There is, however, a substitute called nixnote - currently at 1.4.2 at the time I created this. Create a login at https://evernote.com/ # wget -O nixnote-1.4-2.x86_64.rpm http://downloads.sourceforge.net/project/nevernote/Current/nixnote-1.4-2.x86_64.rpm?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fnevernote%2Ffiles%2FCurrent%2Fnixnote-1.4-2.x86_64.rpm%2Fdownload&ts=1359856134&use_mirror=hivelocity # sudo rpm -ivh  nixnote-1.4-2.x86_64.rpm # nixnote Credits: NixNote (aka Nevernote) written by http://sourceforge.net/users/baumgarr http://sourceforge.net/projects/neverno