For this kind of thing, you really ought to be using github. Even if you never host a full open source project, for something like this you post a "gist". For example, here is one of mine: <a href="https://gist.github.com/806251">https://gist.github.com/806251</a> That will open you up to an entire community of people who can "fork" your scripts and post their changes. I often use it for oneliners that I want to keep handy, like my evil: <a href="https://gist.github.com/422582">https://gist.github.com/422582</a> But I also use it to host things as simple as a single line of code that I often want to reuse, like: <a href="https://gist.github.com/570492">https://gist.github.com/570492</a><div>
<br></div><div>Do that enough and you will eventually have so many code patterns in your toolkit that you can make an open source repo out of them, like: <a href="https://github.com/RichardBronosky/tools/tree/master/bash.patterns">https://github.com/RichardBronosky/tools/tree/master/bash.patterns</a></div>
<div><br></div><div>The point is this: If you write code, any code, you should be on github.<br><br><div class="gmail_quote">On Sun, Mar 20, 2011 at 11:04 AM, Ron Frazier <span dir="ltr"><<a href="mailto:atllinuxenthinfo@c3energy.com">atllinuxenthinfo@c3energy.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello all,<br>
<br>
I've written my first Linux shell script as follows and saved it on the<br>
Desktop under the name Check Big Files and given it execute permission.<br>
I double click on it, the system asks whether to display or run it, and<br>
I say run.<br>
<br>
echo "Files larger than 100 MB starting from /." > file_list.txt<br>
echo "Excluding /swapfile, /sys/devices, and /proc." >> file_list.txt<br>
echo -n "Computer name: " >> file_list.txt<br>
uname -n >> file_list.txt<br>
echo " " >> file_list.txt<br>
date >> file_list.txt<br>
echo " " >> file_list.txt<br>
find / -type f -size +100M | grep -v /swapfile | grep -v /sys/devices |<br>
grep -v /proc >> file_list.txt<br>
echo " " >> file_list.txt<br>
date >> file_list.txt<br>
gedit file_list.txt<br>
<br>
It works very nicely, and give's me an instant report on large files in<br>
my system. You guys can tell me if you think anything needs changing to<br>
improve it. Anyone is welcome to use the script for their own<br>
purposes. If you publish it somewhere, give me the credit. Here's what<br>
it does.<br>
<br>
1) Delete file_list.txt if it exists.<br>
2) Create file_list.txt and put some headers, the computer name, and the<br>
date in it.<br>
3) Find all files > 100 MB in size starting from / and list them in the<br>
text file, while excluding /swapfile, /sys/devices, and /proc.<br>
4) Append the date to the end of the file.<br>
5) Display the text file.<br>
<br>
I have a question. How would I force it to execute immediately, rather<br>
than asking if I want to display it or run it?<br>
<br>
Sincerely,<br>
<br>
Ron<br>
<br>
--<br>
<br>
(PS - If you email me and don't get a quick response, you might want to<br>
call on the phone. I get about 300 emails per day from alternate energy<br>
mailing lists and such. I don't always see new messages very quickly.)<br>
<br>
Ron Frazier<br>
<br>
<a href="tel:770-205-9422">770-205-9422</a> (O) Leave a message.<br>
linuxdude AT <a href="http://c3energy.com" target="_blank">c3energy.com</a><br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>.!# RichardBronosky #!.<br>
</div>