Search Results

Linux is mostly not a UNIX for copyright reasons... It does support a great many UNIX system calls and utilities. If anything the biggest difference is how they kept enhancing the utilities while...

Is $TERM vt100?

I modified my script
you can try this ;)


## exshell ##

#!/bin/bash

clear
shells="bash|ksh|csh|tcsh|pdksh|wksh|zsh"

find_stat () {
sshpid=$(ps -ef | grep $PPID|sed -n '1p'|awk...

Well, the shell always assumes the first argument is a program or builtin -- a safe guess, anything else would be invalid. The following arguments are assumed to be either local files or parameters...

Ah, I see what you mean.

In my shell, BASH, I was able to make it work by cheating: I made an alias like alias CMD="nohup cmd" ...and the shell was willing to tab-complete CMD. Which lets me run...

This is probably nothing to worry about. The boot process will look at the filesystems to mount and check the status flag on each. If they are all marked as clean (i.e. unmounted correctly at...

Wanna suicide ?
remove the #!/bin/bash line

you can give a try with and without this line exec bash
and also add the line kill -9 $$Wanna kill your parents ? Maybe i am wrong but i think it is...

try this :)
## justdoit ##
#!/bin/bash
pid=$(ps -ef | grep "$PPID" | awk '{if (NR==1) print $3} ')
if [ $(pstree -p $pid | grep -o bash | wc -l) -gt 1 ] ; then
echo -e "You are maybe in...

echo $PPID

There is no lazy matching in sed, but by using [^a] (any character but a) instead of . (any character) you can go a long way. Otherwise you would have to switch to perl:
perl -pe 's/.*?(a+).*/>\1</g'

The first .* is eating some of the a's. If you don't want it to eat a's, then give it [^a]* instead of [icode].*

And if you always want it to start at the beginning and end at the end of the...

That is because of sed's greedy matching. The .* matches as much as possible so that \(aa*\) only has one a left (the rightmost a). This should remedy it:
sed "s/[^a]*\(aa*\).*/>\1</g"or
sed...