From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fun proto bug
Date: Sat, 25 Jul 2009 10:13:46 -0700 [thread overview]
Message-ID: <dd6fe68a0907251013yd35ca3cr600e34874dcf9971@mail.gmail.com> (raw)
In-Reply-To: <e04e81541d631c8764fd623b31fcfb17@quanstro.net>
On Sat, Jul 25, 2009 at 9:29 AM, erik quanstrom<quanstro@quanstro.net> wrote:
> i apologize for not hunting this down, but i don't want to
> get diverted from hunting other bugs right now.
>
> ; cat /tmp/allproto
> +
> ; disk/mk9660 -9cj -b bootdisk.img -p /tmp/allproto /tmp/9atom2.iso
> warning: proto lists rc/bin/kill twice
You don't say where you are running this command,
but I bet a case-insensitive file system or file system
protocol is involved. There should be rc/bin/Kill and
rc/bin/kill but it sounds like both are appearing as
lowercase kill when proto reads the rc/bin directory.
The same goes for the troff dups.
Russ
next prev parent reply other threads:[~2009-07-25 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 16:29 erik quanstrom
2009-07-25 17:13 ` Russ Cox [this message]
2009-07-25 21:48 ` erik quanstrom
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=dd6fe68a0907251013yd35ca3cr600e34874dcf9971@mail.gmail.com \
--to=rsc@swtch.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).