On Sat, 1 Sep 2001, Clarence Verge wrote:
> > 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 ?
In ALMOST all commands, the switches can be invoked
either way. I've run across very few that can't.
> 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.
Yup. Scripting is one of the things that makes
'nixes so powerful and easy to use. There's an old
saying that 'nix is hard to learn but easy to use.
> > '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 ?
Just shows that whatever follows it needs to be
at the beginning of the line. I was already in the
"env" mindset, so didn't think of the easier
'echo $PATH'
For instance, if I do
$ env | grep PATH
I get
LD_LIBRARY_PATH=/usr/lib
TCLLIBPATH=/usr/local/lib/rosegarden/petal
PATH=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/steve/bin:/usr/sbin
By stipulating that I only want to see what's true
for "PATH at the beginning of the line" I only get
the last line shown above.
> I'll try /usr/bin IF it is already in my path in all the distros
> I have, otherwise,
It should be.
> 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 ?
Well... / isn't in anyone's path. Executables never
go there.
> 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 ?
They appear to be, yes... HOWEVER, using a script
for a single command is very inefficient. In that
case it's better to use the 'alias' command. Doing
$ alias RPMX rpm -ivh
$ alias ENABLE chmod +x
would be better... and as already noted, echo $PATH is
easiest for the other one.
In order to make your aliases permanent, you can put
them into your .bashrc file.
> >> 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 ?
I am using an internal PCI Netgear FA310TXC.
The above command shows me nothing about it, or
even that it exists.
In order to find this card, I do
$ /sbin/lspci
which gives me this info:
00:09.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)
If this was a pull I'd picked up at a flea-market,
or on ebay, I'd then go to http://www.google.com/linux
and enter LNE100TX to find out all kinds of interesting
things about how to get the card working. Luckily,
it came with a floppy with everything I needed, including
a LINUX.TXT which gave step-by-step instructions on
compiling the module, so I didn't have to resort to that. ;-)
> >> The damn thing is a SOURCE file.
Embrace the SOURCE, young Skywalker. ;-)
> 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.
Again, all your binary ethernet modules will be in
/lib/modules/<kernel version>/net/
You'll find about 90 of them.
- Steve
