From: Rudi Blom <rudi.j.blom@gmail.com>
To: "Greg 'groggy' Lehey" <grog@lemis.com>
Cc: coff <coff@minnie.tuhs.org>
Subject: Re: [COFF] What is your prompt?
Date: Mon, 27 Dec 2021 11:06:07 +0700 [thread overview]
Message-ID: <CAMYpm87xmUaCVc-cVGYk496qL+RVYyMuF7cMxxo=YYMY8+c0FQ@mail.gmail.com> (raw)
In-Reply-To: <20211227034321.GH83649@eureka.lemis.com>
[-- Attachment #1.1: Type: text/plain, Size: 2308 bytes --]
Just 'uname' is not specific enough. On SCO UNIX 3.2V4.2 uname defaults to
'uname -s'. On AlphaServer with Digital UNIX 4.0g or TRU64 V5.1B I get
'OSF1' as answer. On HP-UX 11.23/11.31 I get 'HP-UX'.
Even if I do a 'uname -m' I may still do additional 'uname [-<argument>]'
for other specifics. Of course a 'uname -a' and 'set -- $*' would be a
possibility.
On Mon, 27 Dec 2021 at 10:43, Greg 'groggy' Lehey <grog@lemis.com> wrote:
> On Monday, 27 December 2021 at 9:52:24 +0700, Rudi Blom wrote:
> > My official status seems a bit unclear (although I'm getting paid :-) )
> but
> > unofficially I keep an eye on a lot of a customers servers. Ad-hoc shell
> > scripts still have similar structure as I know how to 'cut and paste'.
> >
> > These scripts are run remotely via a 'homegrown' client-server setup.
> Many
> > should run on different UNIX environments and therefore have near the
> > beginning an OS check. Depending on that I can set PATH and anything else
> > important.
> >
> > #
> > # check what type of OS this system runs on
> > #
> > OST=`uname -m`
>
> That's the architecture. Wouldn't just `uname` be better? I have:
>
> case `uname` in
> Linux)
>
> PATH=.:~:/usr/local/bin:/usr/local/sbin:~/bin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/X11R6/bin:/usr/local/bitkeeper:/Photos/Tools
> export SHELL=/bin/bash
> ;;
>
> NetBSD)
>
> PATH=.:~:/usr/pkg/bin::/usr/local/bin:/usr/local/sbin:~/bin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/X11R6/bin:/usr/local/bitkeeper:/usr/local/gnu-autotools/bin:~:/Photos/Tools
> export SHELL=/usr/pkg/bin/bash
> ;;
>
> FreeBSD)
>
> PATH=.:~:/home/local/bin:/usr/local/bin:/usr/local/sbin:~/bin:/usr/bin:/usr/sbin:/bin:/sbin:/Photos/Tools:~
> export SHELL=/usr/local/bin/bash
> ;;
> ...
>
> And yes, lm, if you're looking, there's really a /usr/local/bitkeeper
> in there. It's been years, but I don't tidy these things up very
> often. I only just removed mosaic from my fvwm2 config menus.
>
> Greg
> --
> Sent from my desktop computer.
> Finger grog@lemis.com for PGP public key.
> See complete headers for address and phone numbers.
> This message is digitally signed. If your Microsoft mail program
> reports problems, please read http://lemis.com/broken-MUA.php
>
--
The more I learn the better I understand I know nothing.
[-- Attachment #1.2: Type: text/html, Size: 3182 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2021-12-27 4:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 2:50 Rudi Blom
2021-12-25 4:40 ` Theodore Ts'o
2021-12-25 17:39 ` Steffen Nurpmeso
2021-12-25 18:28 ` Grant Taylor via COFF
2021-12-25 19:14 ` Steffen Nurpmeso
2021-12-26 3:44 ` Grant Taylor via COFF
2021-12-25 23:19 ` Greg 'groggy' Lehey
2021-12-25 23:43 ` Steffen Nurpmeso
2021-12-26 21:18 ` Theodore Ts'o
2021-12-26 21:33 ` Warner Losh
2021-12-27 1:33 ` Theodore Ts'o
2021-12-27 2:52 ` Rudi Blom
2021-12-27 3:43 ` Greg 'groggy' Lehey
2021-12-27 4:06 ` Rudi Blom [this message]
2021-12-27 4:12 ` Greg 'groggy' Lehey
2021-12-27 4:28 ` Rudi Blom
2021-12-27 18:44 ` Steffen Nurpmeso
2021-12-27 18:55 ` Warner Losh
2021-12-27 19:07 ` Grant Taylor via COFF
2021-12-27 19:25 ` Steffen Nurpmeso
2021-12-27 18:37 ` Steffen Nurpmeso
2021-12-26 3:29 ` Grant Taylor via COFF
2021-12-26 3:54 ` Greg 'groggy' Lehey
2021-12-26 5:27 ` Grant Taylor via COFF
-- strict thread matches above, loose matches on Subject: below --
2021-12-23 6:59 [COFF] What is your prompt? (was: ksh88 source code?) Andy Kosela
2021-12-24 17:17 ` [COFF] What is your prompt? Grant Taylor via COFF
2021-12-26 22:17 ` Mike Markowski
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='CAMYpm87xmUaCVc-cVGYk496qL+RVYyMuF7cMxxo=YYMY8+c0FQ@mail.gmail.com' \
--to=rudi.j.blom@gmail.com \
--cc=coff@minnie.tuhs.org \
--cc=grog@lemis.com \
/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.
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).