The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] Oracle euthanizes Solaris 12, expunging it from roadmap
Date: Fri, 20 Jan 2017 10:20:46 -0500	[thread overview]
Message-ID: <d294e3ab-e19c-7a7c-3674-5088382d9ff3@kilonet.net> (raw)
In-Reply-To: <alpine.BSF.2.02.1701200928070.44785@frieza.hoshinet.org>

I agree. Why would anyone ever write a piece of software that has 
multiple versions of options, when there's no need for the extra wordy 
versions? In the mkdir source, there is no conditionals around anything 
to do with "static struct option const longopts[]" - so there's no 
environment where they wouldn't exist.

 From man page for mkdir on a RedHat 6.8 install:

*       -m, --mode=MODE*
               set file mode (as in chmod), not a=rwx - umask

*       -p, --parents*
               no error if existing, make parent directories as needed

*       -v, --verbose*
               print a message for each created directory

*       -Z, --context=CTX*
               set the SELinux security context of each created 
directory to CTX

               When  COREUTILS_CHILD_DEFAULT_ACLS environment variable 
is set, -p/--parents option respects default umask and ACLs, as it does
               in Red Hat Enterprise Linux 7 by default

        --help display this help and exit

        --version
               output version information and exit

Oh, and an old-man rant: get off my lawn.


On 1/20/2017 9:29 AM, Steve Nickolas wrote:
>
> I blame GNU rather than the Linux people.  GNU are just as much 
> masters of "embrace, extend, exterminate" as Microsoft.
>
> I've thought of trying to build a "GNUless" Linux distribution with a 
> purer Unix feel, but I get hung trying to step myself through the 
> process.
>
> -uso.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170120/e871af1b/attachment.html>


  reply	other threads:[~2017-01-20 15:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19  7:53 Kay Parker   
2017-01-19  8:49 ` Wesley Parish
2017-01-19 14:40   ` Arthur Krewat
2017-01-19 16:39     ` Tim Bradshaw
2017-01-19 17:02       ` Arthur Krewat
2017-01-20  2:00     ` Nick Downing
2017-01-20 11:24       ` Joerg Schilling
2017-01-20 13:26         ` Random832
2017-01-20 14:23           ` Joerg Schilling
2017-01-20 14:29             ` Steve Nickolas
2017-01-20 15:20               ` Arthur Krewat [this message]
2017-01-20 15:45                 ` Andy Kosela
2017-01-20 16:30                   ` tfb
2017-01-20 19:38                     ` Nemo
2017-01-21  0:25                       ` Tim Bradshaw
2017-01-21  1:58                         ` Rico Pajarola
2017-01-21 17:32                           ` Arthur Krewat
2017-01-24  3:51                             ` Rico Pajarola
2017-01-21 15:43                         ` Nemo
2017-01-20 20:30                   ` Steffen Nurpmeso
2017-01-20 22:30                     ` Kay Parker   
2017-01-20 23:50                       ` Steffen Nurpmeso
2017-01-21  0:09                         ` Steve Nickolas
2017-01-21  1:03                           ` Kurt H Maier
2017-01-20 11:54       ` Tim Bradshaw
2017-01-19 18:17   ` Joerg Schilling
2017-01-20 14:58 Rudi Blom

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=d294e3ab-e19c-7a7c-3674-5088382d9ff3@kilonet.net \
    --to=krewat@kilonet.net \
    /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).