An expansion on Octal June 17, 2013
Posted by truthspew in Uncategorized.Tags: Octal, Unix
add a comment
I mentioned Octal as being base 8. It’s true. However in Linux circles you can either set permissions on a file or folder using user/group/other I always found it clunky. Instead you can just do a chmod 551
It breaks down as follows:
4 is read
2 is write
1 is excute
So chmod 551 says User can read and execute, group can read and execute, and other only gets to execute.
You just add up the values to get the permissions for each. All privs come up to chmod 777, that’s read, write and execute for EVERYONE.
But you can understand why it’s called Octal – only 8 possible values for each position.
So it’s now official April 18, 2013
Posted by truthspew in Uncategorized.Tags: Linux, Unix, Widows
2 comments
I’m a Unix guy. It has been boiling around in my resume for awhile now. At this juncture I’ve now dealt with more Unix and Linux systems than Windows systems.
Granted I still know the hell out of Windows too. For example, I know how to get Windows to route packets destined for certain devices over a certain interface.
But the majority of my experience has now been with Unix and open source tools. And I know how to use Corkscrew to tunnel http connections on Unix too.
xkcd is on the Open Source kick now February 12, 2013
Posted by truthspew in Uncategorized.Tags: probability, Unix, xkcd
add a comment
First there’s tar – tar in unix circles stands for Tape Archive. Though you can tar off to any device you wish. For example tar -cvpf /home/tonypo/* /dev/mt0/tonypo.tar would work to create an archive.
And then there’s PERL and Regex, I’ve done a LOT of interesting Regex.
And they even riff on probability in a more applicable sense:
Yeah, that’s 2,000,000 germs that don’t succumb to the sanitizer. Now couple the sanitizer and some UV light and you might get it down to around 100,000. But even still that’s unacceptable.
And why am I up at 2:30 AM? October 23, 2011
Posted by truthspew in Linux, Unix.Tags: Disk Check, Linux, Reboot, Unix
add a comment
Because I’m rebooting a client box in preparation to upgrade it at the end of the week. Linux/Unix has this little oddity. It’s so damnably reliable that it rarely if ever really requires a reboot.
I’ve heard stories and actually experienced a Linux box in an organization that was several years old but we had no idea where it was physically located. We could connect to it, manage it, etc. But it was buried somewhere in the building. I actually found it about a year and a half later. It was tucked into the very back of the warehouse. I threw a monitor on it and tapped the keyboard and was presented the login prompt. Sure enough, it was that server.
Anyhow the reason I’m doing a reboot is because Linux/Unix after so many days without reboot, forces a disk check. And the box I’m working on here hadn’t been rebooted in year!
Now this is a 250GB volume and it’s taken 31 minutes to get 66.6% through the disk check of that volume. I know I could screw with settings and make it ignore the disk check but honestly, it’s easier to let it just scan.
Interesting segue into my next post. That 666 number. Stay tuned!
