What do you get in cygwin when you try
echo "Test" > test ? Even that emulation can't be THAT bad... Cheers, Tink |
Ohnoooo...! I'm sorry VisionZ, I gave you a script which is a bit too specific in the wrong places. You see the line with the find command? It says it should find files under /usr/local/bin, which is where I have my scripts :) I did this just to test the script, but I forgot to change it when I posted it. OK, let's see now... I take som ideas from Tink's script now :)
Code:
#!/bin/sh |
OK I think it may have worked, but I cant find a tar archive??? it should be in my home correct? What is its name also, scripts.tar??
except I get no output, it just sits there and waits, then goes back to the prompt. I get no echoing or any output at all. I really do appreciate both of your guys help and paitence, hopefull I can attain your level of skill someday kudos to both of you. Tink - to answer your question when I make a script out of echo "Test" > test nothing happens, when i type it in the cygwin terminal nothing happens it just goes to the next prompt. |
Yes, the tar archive is called scripts.tar and should be in your home dir. This is very strange... My script might fail if the file command doesn't work as I think. Try issue file oneofyourscripts and see what the output is. What my script looks for is output of the form "Bourne-Again shell script text executable" or "Bourne shell script text executable". If, for some reason, this isn't echoed, then my script won't work.
Sorry for confusing you; maybe I'm just stupid and write bad scripts :) |
No it probably is working just fine, but is an issue with my cygwin for windows or something. Let me try
file rmv~ a script i wrote to get rid of the extra ~ files emacs makes and see what happens. |
when i try this it says
rmv~: cannot open (rmv~). thats all it says |
what are you guys using as a text editor?? is it wordpad and you create txt files or are you guys using emacs or vim? Or something else I dont know about.
|
I'm usually using emacs or pico, vi/vim when I'm forced to it :)
That file error message looks odd to me. Another possibility is to rewrite the BASHSCRIPT "boolean" to look for the string "#!/bin/" in every file: Code:
BASHSCRIPT=`grep -c "\#\!/bin/" "$FILE"` |
I,ll give it a try, and and well this is what happened
IT WORKED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! now one more SMALL thing how do I make it not archive itself, and to check and see if the archive it is making already exists, I dont want to archive over a previous archve, maybe just add a 1 and so on to the end or something if that is not to complicated |
To solve the problem with its archiving itself in a nice way I'd first like to know a way to expand directory names such as ./blah and ../../blah, or ~/blah to the proper full path name. This is something I haven't learned yet :)
|
Again Thanks a ton for your help I,m Afferoing ya
|
Gee thanks :) But can you do that? I haven't signed up...
|
I dont know, I,ll figure it out though, I left feedback =)
Not only am I new to linux I,m new to linuxquestions.com But you all have inspired me to parition some of my HD to Slackware screw this cygwin BS! |
Hello again, VisionZ and spectators :) I've solved your problem now, I think:
Code:
#!/bin/sh |
All times are GMT -5. The time now is 06:09 AM. |