Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 2 hrs ago -
Maemo repository (3)
to Community by torsen - 1 day, 17 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 2 days, 15 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 3 days, 21 hrs ago - more...
 |
|
2010-03-11
, 16:55
|
|
Posts: 702 |
Thanked: 334 times |
Joined on Feb 2010
@ Israel.
|
#12
|
Originally Posted by JosefA
I already tried the [[ ]], and I can't run it if I leave #!/bin/bash.
The point is, look at the difference between that and your code. The point isn't "do you have bash on your N900". I don't either.
Here :
Code:
Nokia-N900-02-8:/etc/network# vi detectUsb.test.sh
#!/bin/sh
my="abcd"
if [[ $my = *bc* ]]
then
echo "Ok"
else
echo "Not ok"
fi
~
~
Nokia-N900-02-8:/etc/network# ./detectUsb.test.sh
Not ok
Nokia-N900-02-8:/etc/network#
|
|
2010-03-11
, 16:56
|
|
Posts: 702 |
Thanked: 334 times |
Joined on Feb 2010
@ Israel.
|
#13
|
Originally Posted by TNiga
3 Reasons :
Why don't you install it then?
1. I didn't know It's an option.
2. There are plenty of scripts on the phone that manage without bash,
i'd like to manage without it as well.
3. The less apps on my phone the better. (if I can deal without them ofc).
|
|
2010-03-11
, 17:24
|
|
Posts: 17 |
Thanked: 4 times |
Joined on Mar 2010
@ Germany
|
#14
|
Yep, * has its wildcard characteristic only by certain interpreters. Bash interprets it as gobuki described, as long as it's actually interpreted by bash (i.e. not escaped e.g. by \ or ''). Compare
echo *b*
and
echo "*b*"
in bash with some file with b in its name in the same directory.
Thus, fiddeling with * with some tools like
find ... -regex ... -exec ...
can be quite tricky in escaping "enough" to avoid bash interpreting it in the first step but have find interpret it for -regex but not for -exec which shall pass it to the next level of bash.........;°))
For sed and numerous other tools * is the "any number of" operator used in regular expressions ( ab*c).
Test (or the short form [...]) does not interpret or compare any regular expressions, if using = (single = is the "official" documented version but == works, too) but rather compares the strings literally.
If you want some regex functionality, try this:
my="abcd"
if [ `echo $my | grep bc` ]
then
echo "Ok"
else
echo "Not ok"
fi
Good luck!
echo *b*
and
echo "*b*"
in bash with some file with b in its name in the same directory.
Thus, fiddeling with * with some tools like
find ... -regex ... -exec ...
can be quite tricky in escaping "enough" to avoid bash interpreting it in the first step but have find interpret it for -regex but not for -exec which shall pass it to the next level of bash.........;°))
For sed and numerous other tools * is the "any number of" operator used in regular expressions ( ab*c).
Test (or the short form [...]) does not interpret or compare any regular expressions, if using = (single = is the "official" documented version but == works, too) but rather compares the strings literally.
If you want some regex functionality, try this:
my="abcd"
if [ `echo $my | grep bc` ]
then
echo "Ok"
else
echo "Not ok"
fi
Good luck!
|
|
2010-03-11
, 17:32
|
|
Posts: 236 |
Thanked: 223 times |
Joined on Oct 2009
@ NE UK
|
#15
|
Not sure if this is the *best* way to do it but it does seem to work on my N900:
Edit: Meh, beaten to it by a cowboy! 
#!/bin/sh
my="abcd"
his=`echo "$my" | grep 'bc'`
if [[ $my == $his ]]
then
echo "Ok"
else
echo "Not ok"
fi
|
|
2010-03-11
, 17:34
|
|
Posts: 702 |
Thanked: 334 times |
Joined on Feb 2010
@ Israel.
|
#16
|
Originally Posted by CowboyFromHell
Thank you very much CowboyFromHell,
Yep, * has its wildcard characteristic only by certain interpreters. Bash interprets it as gobuki described, as long as it's actually interpreted by bash (i.e. not escaped e.g. by \ or ''). Compare
echo *b*
and
echo "*b*"
in bash with some file with b in its name in the same directory.
Thus, fiddeling with * with some tools like
find ... -regex ... -exec ...
can be quite tricky in escaping "enough" to avoid bash interpreting it in the first step but have find interpret it for -regex but not for -exec which shall pass it to the next level of bash.........;°))
For sed and numerous other tools * is the "any number of" operator used in regular expressions ( ab*c).
Test (or the short form [...]) does not interpret or compare any regular expressions, if using = (single = is the "official" documented version but == works, too) but rather compares the strings literally.
If you want some regex functionality, try this:
my="abcd"
if [ `echo $my | grep bc` ]
then
echo "Ok"
else
echo "Not ok"
fi
Good luck!
The example you posted works well, but when I tried to adapt it a bit to my needs, I have an odd error :
Code:
Nokia-N900-02-8:/etc/network# vi detectUsb.sh
#!/bin/sh
my=`/sbin/ifconfig`
if [ `echo $my | grep RUNNING` ]
then
echo "Ok"
else
echo "Not ok"
fi
Nokia-N900-02-8:/etc/network# ./detectUsb.sh
sh: Link: unknown operand
Not ok
I am a big bash / sh noob.
|
|
2010-03-11
, 17:47
|
|
Posts: 17 |
Thanked: 4 times |
Joined on Mar 2010
@ Germany
|
#17
|
If you only want to check, whether it is running or not, you could do
if `echo $my | grep -q RUNNING`
Note: no "test" or [...]. grep -q is "quiet" and gives a return value for "found" or "not found"
if `echo $my | grep -q RUNNING`
Note: no "test" or [...]. grep -q is "quiet" and gives a return value for "found" or "not found"
 |
|
2010-03-11
, 17:53
|
|
Posts: 60 |
Thanked: 46 times |
Joined on Jan 2010
@ Europe
|
#18
|
Originally Posted by eitama
Yes, not by default. But you can install it if you need the functionality. I'm using it frequently because i want a command history.
As far as I know, glob works with == yes,
But, there is no bash on the N900, busybox....
|
|
2010-03-11
, 17:55
|
|
Posts: 17 |
Thanked: 4 times |
Joined on Mar 2010
@ Germany
|
#19
|
Forgot to mention: This only works for
my=`/sbin/ifconfig usb0`
otherwise it would be true if *any* network adapter is RUNNING, as all lines are parsed by grep and it would find some line with RUNNING ;°)
So, this complete code must work:
#!/bin/sh
if `/sbin/ifconfig usb0 2>/dev/null | grep -q RUNNING`
then
echo "Ok"
else
echo "Not ok"
fi
if you replace usb0 by $1 as command line argument, you can use it for any network interface.
Last edited by CowboyFromHell; 2010-03-11 at 19:35. Reason: wrong adapter
my=`/sbin/ifconfig usb0`
otherwise it would be true if *any* network adapter is RUNNING, as all lines are parsed by grep and it would find some line with RUNNING ;°)
So, this complete code must work:
#!/bin/sh
if `/sbin/ifconfig usb0 2>/dev/null | grep -q RUNNING`
then
echo "Ok"
else
echo "Not ok"
fi
if you replace usb0 by $1 as command line argument, you can use it for any network interface.
Last edited by CowboyFromHell; 2010-03-11 at 19:35. Reason: wrong adapter
|
|
2010-03-11
, 18:04
|
|
Posts: 60 |
Thanked: 46 times |
Joined on Jan 2010
@ Europe
|
#20
|
Originally Posted by eitama
Thank you very much CowboyFromHell,
The example you posted works well, but when I tried to adapt it a bit to my needs, I have an odd error :
Could you help me out on this one?Code:Nokia-N900-02-8:/etc/network# vi detectUsb.sh #!/bin/sh my=`/sbin/ifconfig` if [ `echo $my | grep RUNNING` ] then echo "Ok" else echo "Not ok" fi Nokia-N900-02-8:/etc/network# ./detectUsb.sh sh: Link: unknown operand Not ok
I am a big bash / sh noob.
I think the error you made is you are testing the output of grep and not its return value that is in $? after grepping.
Last edited by gobuki; 2010-03-11 at 18:05. Reason: typo
My Maemo5 projects:
mSpede - Speed testing game | Them Bloody Ducks - 2D duck hunting game | Maetronome - A simple metronome app | CuteMPC - MPD client