Sponsored Content
The Lounge What is on Your Mind? How to become good UNIX engineer Post 302416393 by pseudocoder on Monday 26th of April 2010 10:27:10 AM
Old 04-26-2010
Quote:
Originally Posted by solaris_user
daily UNIX usage
Yea, but not only at home.
I (and probably your next potential employer) could not respect someone calling himself UNIX Engineer without having at least 5 yrs. of working experience in a (large) company.
Ideally you will have some certification too, eg. SCSA, SCNA, SCSECA

/me is also trying to get there where you want. Gotta look for a Junior UNIX Administrator/Manager/Engineer job opportunity.

Good luck Smilie
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Good Unix Shells ?

Hey Guys i am new to Unix and i have downlaoded Cygwin for Windows and deleted it. I was just wondering is there any good shells like that for windows that just as good thanks for your time ][ce (1 Reply)
Discussion started by: IceCold
1 Replies

2. UNIX for Dummies Questions & Answers

What is the industry standard for number of servers per Unix/Linux engineer?

What is the industry standard for number of servers per Unix/Linux engineer and are there any white papers or the like that discuss this? (1 Reply)
Discussion started by: Rav78uk
1 Replies

3. UNIX for Dummies Questions & Answers

Information on Network engineer and Unix Systems Engineer

Hi, I'm exploring a few different careers( Unix System's Admin, Network Engineer, and Unix System's Engineer). I asked in another thread about System's Admin, so I have some more info on that already. I'm not finding very much info on Network Engineers or Unix System Engineers though. Can you guys... (0 Replies)
Discussion started by: hpicracing
0 Replies

4. Advertise with Us

Systems Engineer- Emeryville, CA (UNIX, C)

Systems Engineer- Emeryville, CA (UNIX, C) Gracenote is seeking a Systems Engineer to develop features and fixes in Gracenote's online media recognition service. You will contribute regularly to team design and code reviews, and be responsible for the analysis and resolution of software defects... (0 Replies)
Discussion started by: cwilliams
0 Replies
SHELL-QUOTE(1p) 					User Contributed Perl Documentation					   SHELL-QUOTE(1p)

NAME
shell-quote - quote arguments for safe use, unmodified in a shell command SYNOPSIS
shell-quote [switch]... arg... DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands or files with embedded white space or shell globbing characters safely. Here are a few examples. EXAMPLES
ssh preserving args When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and passes them to "$SHELL -c". This doesn't work as intended: ssh host touch 'hi there' # fails It creates 2 files, hi and there. Instead, do this: cmd=`shell-quote touch 'hi there'` ssh host "$cmd" This gives you just 1 file, hi there. process find output It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote: eval set -- `find -type f -print0 | xargs -0 shell-quote --` debug shell scripts shell-quote is better than echo for debugging shell scripts. debug() { [ -z "$debug" ] || shell-quote "debug:" "$@" } With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can. save a command for later shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are things the user can't pass through), you can do something like this: user_switches= while [ $# != 0 ] do case x$1 in x--pass-through) [ $# -gt 1 ] || die "need an argument for $1" user_switches="$user_switches "`shell-quote -- "$2"` shift;; # process other switches esac shift done # later eval "shell-quote some-command $user_switches my args" OPTIONS
--debug Turn debugging on. --help Show the usage message and die. --version Show the version number and exit. AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions. AUTHOR
Roderick Schertler <roderick@argon.org> perl v5.8.4 2005-05-03 SHELL-QUOTE(1p)
All times are GMT -4. The time now is 10:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy