9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9base-3
Date: Sat,  8 Aug 2009 09:35:45 +0200	[thread overview]
Message-ID: <5d375e920908080035i4f70ce5ldc6385da52abde2@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0908072358p4f901358nde69ccbc6559ec3d@mail.gmail.com>

I haven't used the tarball in years because I simply find hg more
convenient, but a few times when I have recommended somebody to
install p9p they have complained about problems unpacking the tarball,
I just tell them to do a fresh hg checkout instead, and that usually
works for them. Maybe they are simply confused by whatever errors gnu
tar spews for who knows what reason, but people that have no problems
with other tarballs do have problems with the p9p tarballs, and it has
been going on for a while.

uriel

On Sat, Aug 8, 2009 at 8:58 AM, Russ Cox<rsc@swtch.com> wrote:
> On Fri, Aug 7, 2009 at 6:13 PM, Uriel<uriel99@gmail.com> wrote:
>> Always get p9p from hg, the tarballs have been partially broken for
>> ages and
>
> Excuse me?
> Instead of keeping that to yourself why not tell me so I can fix it?
> I know many people who install from the tar file, though,
> so I expect you're just whining instead of checking the facts,
> as usual.
>
>> always have problems being untared in some environments
>
> Again, details?
>
> FreeBSD:
> holo=; hget http://swtch.com/plan9port/plan9port.tgz | gunzip | tar xf -
> holo=; ls -lR plan9 | awk '/^-/ {s+=$5} END{print s}'
> 49413465
> holo=;
>
> Linux:
> c2=; gunzip < plan9port.tgz | tar xf -
> tar: Ignoring unknown extended header keyword `SCHILY.dev'
> tar: Ignoring unknown extended header keyword `SCHILY.ino'
> tar: Ignoring unknown extended header keyword `SCHILY.nlink'
> c2=;  ls -lR plan9 | awk '/^-/ {s+=$5} END{print s}'
> 49413465
> c2=;
>
> OS X:
> mini=; gunzip < plan9port.tgz | tar xf -
> mini=; ls -lR plan9 | awk '/^-/ {s+=$5} END{print s}'
> 49342685
> mini=;
>
> The GNU tar warnings about SCHILY extensions don't count as
> a problem: it's an inconsequential warning message.
>
> The missing 70780 bytes on OS X are the files HI, HX, LH, RC, lH, and rH
> from troff/font/devutf/charlib, which have been overwritten with differently
> cased versions of the same files.  It doesn't matter since basically
> no one uses those special characters, and you'd have the same problem
> using Hg or any other file program: the bug is in the file system, not
> the extractor.
>
> I'm plenty happy for people to use hg instead of the tar files--
> I think that's good advice for the people who enjoy using
> version control systems--but please don't go spreading
> misinformation.
>
> Thanks.
> Russ
>
>



  reply	other threads:[~2009-08-08  7:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 20:08 Anselm R Garbe
2009-08-07  0:34 ` Roman Shaposhnik
2009-08-07  7:54   ` Anselm R Garbe
2009-08-07 21:34     ` Jason Catena
2009-08-08  1:13       ` Uriel
2009-08-08  6:58         ` Russ Cox
2009-08-08  7:35           ` Uriel [this message]
2009-08-08  7:39             ` Uriel
2009-08-08  8:39               ` Russ Cox
2009-08-08 14:13                 ` Ethan Grammatikidis
2009-08-11 19:41           ` Lawrence E. Bakst
     [not found]           ` <p06240802c6a776d7b5a3@192.168.0.142>
2009-08-12  4:42             ` Anthony Sorace

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=5d375e920908080035i4f70ce5ldc6385da52abde2@mail.gmail.com \
    --to=uriel99@gmail.com \
    --cc=9fans@9fans.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).