Technical Stuff

Reference URLS: http://blog.dentcat.com/2009/09/highlighting-yaml-in-gedit_02.html http://codesauce.com/posts/gedit3-yaml-syntax-highlighting/ http://superuser.com/questions/353391/custom-gedit-syntax-highlighting-for-dummies sudo yum install subversion cd /tmp && svn checkout http://masood.googlecode.com/svn/trunk/yaml-language-spec/ cd yaml-language-spec/ sudo cp yaml.lang /usr/share/gtksourceview-3.0/language-specs/ sudo chmod 644 /usr/share/gtksourceview-3.0/language-specs/yaml.lang

I was experimenting with shutdown scripts today when I discovered the importance of the /var/lock/subsys  directory. I didn't realize that there was code in /etc/rc that checked for the existence of a lock file before trying to stop a service.  I guess I never had need to really look at this before.  I banged my head repeated only why the K* scripts I had created weren't working.  Until I finally looked at /etc/rc and realized it was only executing K* scripts for services that had touch /var/lock/subsys/<SERVICENAME>. Duh, should have looked there first.

yum -y update (umask 022; sudo http_proxy=http://proxy:3128 ftp_proxy=http://proxy:3128 yum install yum-plugin-fastestmirror yum-plugin-{downloadonly,keys,priorities,remove-with-leaves,show-leaves,verify} nedit rxvt-unicode-256color xscreensaver\* xorg\*font\*Type1 xorg\*font\*misc screen dump rxvt rxvt-unicode-256color) yum groupinstall LXDE yum install kernel-devel gcc bison vi /etc/yum.repos.d/google-chrome.repo [google-chrome] name=google-chrome baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64 enabled=1 gpgcheck=1 gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub chmod 644  /etc/yum.repos.d/google-chrome.repo chown root:root  /etc/yum.repos.d/google-chrome.repo yum install google-chrome-stable sudoedit /etc/default/grub # s/rhgb quiet/verbose/ sudo grub2-mkconfig -o /boot/grub2/grub.cfg (umask 022; sudo yum -y groupinstall "Development Tools" "Development Libraries") Installing virtualbox curl http://d...