Re: {SPAM?} Re: [flalug] {SPAM?} 1st post

From: Ron Youvan (ka4inm@tampabay.rr.com)
Date: Thu Feb 17 2005 - 00:19:29 EST


> That's great then!
> Does BASH have it's own scripting language or is it
> PERL? Both?

  Just my opinion here, MS DOS's batch language is a
subset of UNIX scripting language, which is basically the
same as Basic, but with two differences. (that I am aware
of)

First: there is only integer math.

Secondly: the syntax and reserved command names are
   completely different, I think the MS way makes more sense
   to me, but I started with DOS. (some BASH commands are
   down right bizarre to me)

Perl, python and other "scripting languages" are not related
to BASH's scripting language.

> What I'd like to do is
> learn everything from commandline and then be

> able to pick and choose what desktop I want, load
> drivers I need, and

> compile software that I want....although I haven't
> compiled anything since DOS 6.0 and I barely remember
> doing that!

   To me (and a few other odd balls) LINUX is "commandline"
and all GUI is not. In fact the "desktop" is normally from
the "X windowing system" written by the MIT group as a
color "master computer with dumb terminals" system and it
can be compiled to run over MSDOS, windows, the MAC OS and
others, it is a poor replacement for MS windows.

   I use LINUX 90% of the time and when using (98 SE at work,
which I hate) I use the keyboard 80% of the time, the mouse
is a quick way to move the cursor around the screen to me.

   That doesn't work with the "X windowing system" in fact if
you don't have a three button mouse with some "X windowing
system" applications some things become quite difficult.

> Basically I'm shooting for a 'roll your own' or 'Linux
> from scratch'

> level of skill....

   If winblos breaks what do you do? Reinstall it, over
and over and over every time
something gets screwed up, reinstall it.

  If you understand LINUX, (if you hose it over,
which I have at least a dozen times since 1997) you trouble
shoot the problem and correct the one command that throws
things into that "whacked over" condition.

> anyway, would o'reilly's bash scripting book be a good
> place to start or a Perl book?

  I love and recommend "O'reilly's bash scripting
book", get the latest edition that has been printed. Many
commands and some "things" are quite obscure and many are
not at all "self explanatory"

Example:

FileName=${1%.*}.xmp

  This creates a variable (FileName) from the first command
line parameter with the extension changed from any to .xmp
it's one of those "keep the book on your knee until you have
enough examples in /usr/local/bin to use as references.

--
   Ron



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:34:18 EDT