From: "Iruatã Souza" <iru.muzgo@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] pkg/unpkg strangeness
Date: Mon, 11 May 2015 18:17:18 -0300 [thread overview]
Message-ID: <CABJnqBQgn-M5tyQtyyU6+rdTVezoBB9aUqPQhWOuW4UjRaO7+Q@mail.gmail.com> (raw)
In-Reply-To: <ba545d78275d80c20bb69f732e60954e@u2.sfldmibb.det.wayport.net>
According to tar(1):
File path names are limited to 100 characters (256 when
using ustar format).
Every file that has a path bigger than that leads to pkg/unpkg trying
to unpack the file into /.
On Mon, May 11, 2015 at 5:28 PM, <sl@9front.org> wrote:
> Someone mailed me pointing out that the old equis package aborts
> during installation. I was able to reproduce. On a 386/9pcf system:
>
> ; pkg/install equis-2012.01.11
>
> -- snip --
>
> A ps2pdf_spooltodir.sh
> pkg/unpkg: 'ps2pdf_spooltodir.sh' mounted directory forbids creation
>
>
> I manually unpacked equis-2012.01.11.tbz and found this:
>
> ; ls
> 386
> sys
> ; du -a * | sed 's/^.* //g' | grep ps2pdf_spooltodir.sh
> sys/src/pkg/equis-2012.01.11/cmd/X/hw/xprint/config/C/print/models/PS2PDFspooldir-GS/ps2pdf_spooltodir.sh
>
> Makes no sense. The tarball is supposed to just unpack over /. As you
> can see, nothing should get created directly in / (/386 and /sys already
> exist on every system). pkg/unpkg must be doing something strange.
>
> I do think we saw this before and I forgot to investigate.
>
> Why is this happening?
>
> sl
next prev parent reply other threads:[~2015-05-11 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 20:28 sl
2015-05-11 21:17 ` Iruatã Souza [this message]
2015-05-11 21:33 [9front] " sl
2015-05-11 21:44 ` Iruatã Souza
2015-05-11 21:46 ` Aram Hăvărneanu
2015-05-11 21:50 ` Iruatã Souza
2015-05-11 22:00 sl
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=CABJnqBQgn-M5tyQtyyU6+rdTVezoBB9aUqPQhWOuW4UjRaO7+Q@mail.gmail.com \
--to=iru.muzgo@gmail.com \
--cc=9front@9front.org \
/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).