Sponsored Content
Full Discussion: [Discussion] AIX future
Operating Systems AIX [Discussion] AIX future Post 303034127 by Neo on Friday 19th of April 2019 02:29:00 AM
Old 04-19-2019
Quote:
Originally Posted by Phat
oh, I can see, the future is not so bright as Redhat becomes very common nowadays.
I think it is just basic business economics. RedHat is a lot cheaper to use than AIX since IBM is expensive; and the world has shifted and there are a lot of very talented Linux people on the market. This is very different than it was a decade or so ago, when Linux people has trouble finding work. Now the tides have reversed, from what I have seen. But since I am not directly in the job market my knowledge is limited.
 

2 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

vb 3.0 Upgrade Discussion

Please discuss vB 3.0 upgrade or ask questions here. Neo (27 Replies)
Discussion started by: Neo
27 Replies

2. What is on Your Mind?

Discussion culture

I want to start a small thread about discussion culture. From the past experience in different fora, I have little hope that any will come out of it. But I'll try it anyway, hoping to contributing to an improvement on the topic. I do not want to discuss a specific technical question, but only... (5 Replies)
Discussion started by: stomp
5 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 05:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy