if i convert to BSD, you won't mind being bombarded with questions? of
course, by your reasoning, you won't be bombarded with questions because the
man pages are THAT good. no, i'm not being sarcastic here. your arguments
make a lot of sense.
are OpenBSD and FreeBSD available in iso for download? if so, i'll try one
out on my laptop and decide whether it's worth it for my main box.
-----Original Message-----
From: Jacob Meuser [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 2:07 PM
To: [EMAIL PROTECTED]
Subject: [EUG-LUG:2202] RE: BASH question
On Tue, Aug 14, 2001 at 01:02:26PM -0700, Justin Bengtson wrote:
> mos' definitely. what exactly does "i" represent? from what i'm reading
> here (and what cory told me in-office) it seems to be a word between
spaces.
> if so, that's exactly what i'm looking for.
>
> the expression below doesn't look complete... "for i in $(DATE); do"
> should there be a "each" in the statement? or does the statement only act
> on the first "i"? or does it not need an "each" because it's implied?
>
i (it could be any variable name) represents a list, what a list is,
and whether 'each' is needed is shell dependent, so
> the man pages for BASH are horrible...
>
means you're SOL. Well not really, <rant> but it seems Linux (all distros,
and even the kernel itself) relies much too heavily upon outside
documentation.
Since I abhor bash, </rant> I do not use bash, and don't feel right
answering questions about it.
I must also mention that I have learned a great many things from the
OpenBSD man pages. That's where I learned how to do the above example.
Of course, the man pages are online :
http://www.openbsd.org/cgi-bin/man.cgi
search for 'sh' or 'ksh'
> and thanks for the help!
>
<rant>
If you're really interested in learning Unix, and learning it correctly
by studying audited (not just "security" audited, but plain bug audited,
since many security related bugs start life as seemingly innocuous but
sloppy code) sources (this is OpenSource, right?), and referencing
up-to-date man pages that actually have examples in them, then install
OpenBSD, and use it. Then you'll be able to help others who are stuck
behind (or rather in front of) their "Oh so sweet" frontends, binary
packages, and bloated, poorly documented software.
</rant>
--
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
