The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: another OSX 100% less Unix
Date: Thu, 27 Jun 2024 19:44:54 +0000	[thread overview]
Message-ID: <0XwyFvb2gqLhKOmCJZ7hxF03HLJVx2BT_Q7nC-tfV7SLHaKVq8Tf3SDwiz1I9mOPiv8I2JNhHzZB0BGhPeRncM5uY3TJ0S_ZxkkxhQh5mkE=@protonmail.com> (raw)
In-Reply-To: <be4ca894-b2f9-b456-f0b0-f120f9a58589@riddermarkfarm.ca>

On Thursday, June 27th, 2024 at 12:08 PM, Stuff Received <stuff@riddermarkfarm.ca> wrote:

> On 2024-06-26 23:29, ron minnich wrote (in part):
> [...]
> 
> > what's in it?
> > ronsexcllentmbp:t rminnich$ cpio -ivt < ../t.cpio
> > -rw-r--r-- 1 rminnich wheel 0 Jun 26 20:21 a
> > -rw-r--r-- 2 rminnich wheel 0 Jun 26 20:21 b
> > -rw-r--r-- 2 rminnich wheel 0 Jun 26 20:21 c link to b
> > 
> > "c link to b"? wtf? Who thought that was a good idea? because ...
> > ronsexcllentmbp:t rminnich$ touch 'c link to b'
> 
> [...]
> 
> > Somebody needs to get the osx folks a unix manual set :-)
> 
> 
> Interestingly, the man page (macos 11.3.1) for cpio contains the following:
> 
> STANDARDS
> There is no current POSIX standard for the cpio command; it
> appeared in ISO/IEC 9945-1:1996
> (`POSIX.1'') but was dropped from IEEE Std 1003.1-2001 (`POSIX.1'').
> 
> The cpio, ustar, and pax interchange file formats are defined by
> IEEE Std 1003.1-2001 (``POSIX.1'')
> for the pax command.
> 
> S.

Leopard, the first UNIX-certified OS X, was certified to UNIX 03, which derives from 1003.1-2001, so POSIX cpio(1) it seems was never a factor.

- Matt G.

      reply	other threads:[~2024-06-27 19:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27  3:29 [TUHS] " ron minnich
2024-06-27  3:30 ` [TUHS] " ron minnich
2024-06-27  9:47 ` Leah Neukirchen
2024-06-27 22:22   ` Bakul Shah via TUHS
2024-06-27 11:55 ` Peter Yardley
2024-06-27 12:06   ` Dan Cross
2024-06-27 13:54     ` Warner Losh
2024-06-27 19:08 ` Stuff Received
2024-06-27 19:44   ` segaloco via TUHS [this message]

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='0XwyFvb2gqLhKOmCJZ7hxF03HLJVx2BT_Q7nC-tfV7SLHaKVq8Tf3SDwiz1I9mOPiv8I2JNhHzZB0BGhPeRncM5uY3TJ0S_ZxkkxhQh5mkE=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.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).