On Sat, 1 Sep 2001 00:28:30 -0400 (EDT), Steve <[EMAIL PROTECTED]> wrote:
> rpm = Redhat Package Manager
That I knew.
> - i = install
> - v = verbosely
> - h = (show) hashes
That I had seen, but would never remember.
> You can do either of 'rpm -i -v -h <package name>' or
> 'rpm -ivh <package name>'
Seen it, but unsure if it is universal. Can you ALWAYS group the
switches/options ? In all programs that is ?
> This isn't hard and fast, but usually a "program"
> refers to a compiled binary while a "script" is a
> series of commands in a file which will be interpreted
> upon execution... of course, many scripts are referred
> to as programs, so terminology in this case isn't to
> be strictly relied upon.
> You can write scripts in Linux in many languages.
> For most of your "batch file" type operations you'll
> most likely be using bash. You make a script with any
> text editor. The key is to put the "shebang" on the
> first line.
> A shebang is a line that looks like this:
> #! /bin/sh
> The # is the "sh" and the ! is the "bang"
> The # indicates a commented line not to be executed.
> In the case of the shebang, the "comment" tells the
> shell which interpreter will be used to execute the
> lines following. In the case that your shell is
> already bash (bash is compatible with sh), this shebang
> could be considered redundant... however if you later
> decide to use a different default shell, the shebang
> insures your script will still work.
> Here's a really simple script:
> #! /bin/sh
> for i in *.wav
> do
> echo $i
> play $i
> done
> Bash is much more powerful than batch files... as
> a matter of fact, entire programs are written in
> bash (remember when I said "program" isn't concretely
> defined? ;-)
I can see there will be time required to learn the commands, but
that will simplify the utilization of Linux for me. At the start
I'll just stick to what might be equivalant to DOS.
> here are some beginning shell tutorials:
> http://linux.com/develop/newsitem.phtml?sid=64&aid=10910
> http://www.linux.com/newsitem.phtml?sid=60&aid=9869
> http://www.freeos.com/guides/lsst/index.htm
> Where to put scripts:
> If you want to execute them from all over, it's best
> to put them somewhere in your path. The command 'env'
> will show you your PATH among many other things, but if
> you want to cut to the chase, you can do
> 'env | grep ^PATH'
> (I've included /home/steve/bin in my path so I can
> stow things there that I want to run... they could
> just as easily go in /usr/bin, but since I backup
> /home often, and /usr/bin rarely... ;-)
What is the '^' in front of PATH for ?
I'll try /usr/bin IF it is already in my path in all the distros
I have, otherwise, why not some other place - again already in the
likely default path. If necessary, in the root ? Just to make them
reachable without a user knowing he/she must CHANGE his path ?
So:
#! /bin/sh
rpm -ivh $1
named RPMX
And:
#! /bin/sh
env | grep ^PATH
named PATH
And:
#! /bin/sh
chmod +x $1
named ENABLE
are workable scripts ?
>> dmesg | grep eth0 comes up blank.
> Yup, for me too (excepting firewall logged
> packets).
So this means the above command told ME nothing if it gives you the
same answer - or you are not using a NIC ?
>> so I went to the Dlink disk and glory be -
>> a Linux subdir.
>> Arrrggghhh.
>> The damn thing is a SOURCE file.
>> Please don't tell me how nice it is that I can change the source -
>> is it possible that someone could produce the binary for me from the
>> source and makefile ?
> I don't think so. As I understand it, each module is
> linked against a certain kernel version.
Aww.
> I'd be fairly
> certain the module is already on your CD somewhere if
> not installed on your hard drive.
> Take a look in /lib/modules/<kernel version>/net/
> and see if the <module>.o file that corresponds to
> the source filename you found on the Dlink disk is
> there.
I will certainly look there for it, but have my doubts.
The card MAY be newer than RH5.1
Thanks.
> 'make'
> 'make install'
I'll certainly try it once more and save the instructions anyway,
but to tell the truth I'd rather just install a card I have a binary
module for.
Thanks again, Steve, for the excellent tutorial.
- Clarence Verge
- Back to using Arachne V1.62 ....
