From: Hank Hughes <thigpen@ccs.neu.edu>
To: zsh-users@math.gatech.edu
Subject: more definitive OSTYPE ...
Date: Fri, 17 Oct 1997 09:01:08 -0400 [thread overview]
Message-ID: <199710171301.JAA17430@procyon.ccs.neu.edu> (raw)
Am I doing something wrong? I notice OSTYPE is mostly correct,
however, sometimes I get slight discrepancies like:
1009 % echo $OSTYPE
sunos4.1.3
[ thigpen@k2 (8:55AM) ~ ]
1010 % uname -a
SunOS k2.ccs.neu.edu 4.1.4 1 sun4m unknown
It seems that major types are used not revisions/updates/minor-types.
I'd rather use and depend on builtins like OSTYPE (or something
similar) rather than run something else.
Concerned, :-)
-Hank
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hank Hughes thigpen@ccs.neu.edu http://www.ccs.neu.edu/home/thigpen/
Random Quote #438:
"Name the greatest of all inventors. Accident."
- Mark Twain
next reply other threads:[~1997-10-17 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-17 13:01 Hank Hughes [this message]
1997-10-17 15:00 ` Geoff Wing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199710171301.JAA17430@procyon.ccs.neu.edu \
--to=thigpen@ccs.neu.edu \
--cc=zsh-users@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).