Search Results

Your kernel and your module disagree on what members nf_conn has.

The structure of nf_conn matters to the entire netfilter chain, you can't change it without recompiling your entire kernel.

First, take a long hard long at the currdisk structure. If there is any chance that (double)currdisk->currangle and (double)currdisk->rotatetime overlap that is your problem. Having these overlap...

Yes ..

In this codeif [ `echo "$1 > $2" | bc -l` -eq 1 -a `echo "$1 < $3" | bc -l` -eq 1 ]
the meaning of parameter "-a" is "and" operator?

ksh93, bash, zsh:
if (( $2 < $1 && $1 < $3)); then
echo Ok
else
echo False
done

===

Well, bash doesn't work with floating numbers. Then
if [[ ! $temp0 =~ ^- && $temp1 =~ ^- ]]; then ...

Try this:
if [ `echo "$1 > $2" | bc -l` -eq 1 -a `echo "$1 < $3" | bc -l` -eq 1 ]; then
echo OK
else
echo False
fi

Different languages implement regular expressions differently, you should check the manual pages of your shell.

This is bash:

4.1.10(4)-release$ [[ 123 =~ [0-9] ]] && echo ok || echo ko
ok...

Some AWKs' regular expression flavor may not support interval expressions (in your example, the {4} part), even though the standard has stated (for at least 15 years) that AWK's regular expression...

[[ "aabaab" =~ aaa*b ]] && echo "ok" || echo "error"
Here, when you include *, it means 0 or more and that is why its matching. It will basically look for aab or aaab or aaaaab etc

[[ "aabaab"...

Why do you think it shouldn't match?

I think that the substring 'ab' is in 'aab'.

Regards,
Birei

Oh, Bash. Well, when you quote the right part of `=~' operator you get string, not a regex. And part of string is matched the whole string.
$ [[ "aab" =~ a*b ]] && echo "ok" || echo "error"
ok
$...

Hi,

When using metacharacters in a regular expression, remove quotes:

$ [[ "aab" =~ a*b ]] && echo "ok" || echo "error";
ok
$ [[ "aab" =~ a.b ]] && echo "ok" || echo "error";
ok
Regards,...

Well, it seems to me that your first example is setting FS after first line has been divided into fields using default separator (space). It is analogous to:grep -n -E "drive 1\b" inv_dbg |awk...

You are defining field separator in a weird way in the first code. Second example is legit, but it is usually done like this:grep -n -E "drive 1\b" inv_dbg | awk -F":" '{ print $1}'