From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] contrib/install fgb/X11?
Date: Mon, 15 Nov 2010 08:36:59 -0800 [thread overview]
Message-ID: <AANLkTimkoGTiidnM7RuA8Mvj84MyhMOVFx7Pj4=omXyp@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik-6aAjZiOX+n39zrvc91uDvQpRpBEZojn+Bhp+@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
On Mon, Nov 15, 2010 at 8:27 AM, David Leimbach <leimy2k@gmail.com> wrote:
>
>
> On Mon, Nov 15, 2010 at 8:24 AM, erik quanstrom <quanstro@quanstro.net>wrote:
>
>> > having very strange behavior of /tmp after a failed contrib/install.
>>
>> sounds like magic. what is the behavior?
>>
>>
> getting "clone failed" when doing "ls" from a cwd of /tmp. I ended up just
> firing up another ramfs to move on. It looks like X11 is now installing via
> contrib after some manual cleanup in /dist/replica of X11 and the client
> subdir's X11 files.
>
> I don't honestly know what happened during the very first attempt. Could
> have been a network interruption I suppose, but it's difficult to tell.
>
> Dave
>
Ah now we're failing again:
error: copying /386/bin/X11/equis: '/n/dist/386/bin' does not exist
error: copying /386/bin/X11/twm: '/n/dist/386/bin' does not exist
error: copying /386/bin/X11/xclock: '/n/dist/386/bin' does not exist
error: copying /386/bin/X11/xev: '/n/dist/386/bin' does not exist
error: copying /386/bin/X11/xset: '/n/dist/386/bin' does not exist
>
>
>> - erik
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 2278 bytes --]
next prev parent reply other threads:[~2010-11-15 16:36 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 15:39 David Leimbach
2010-11-15 16:01 ` ron minnich
2010-11-15 16:04 ` David Leimbach
2010-11-15 16:09 ` David Leimbach
2010-11-15 16:15 ` Stanley Lieber
2010-11-15 16:21 ` David Leimbach
2010-11-15 16:17 ` Steve Simon
2010-11-15 16:12 ` erik quanstrom
2010-11-15 16:17 ` David Leimbach
2010-11-15 16:20 ` David Leimbach
2010-11-15 16:44 ` ron minnich
2010-11-15 18:45 ` Steve Simon
2010-11-15 16:24 ` erik quanstrom
2010-11-15 16:27 ` David Leimbach
2010-11-15 16:36 ` David Leimbach [this message]
2010-11-15 16:46 ` ron minnich
2010-11-15 18:34 ` David Leimbach
2010-11-15 18:44 ` David Leimbach
2010-11-15 18:47 ` Steve Simon
2010-11-15 18:49 ` David Leimbach
2010-11-15 21:50 ` Yaroslav
2010-11-15 21:52 ` David Leimbach
2010-11-15 23:33 ` Federico G. Benavento
2010-11-15 23:37 ` Federico G. Benavento
2010-11-15 23:42 ` David Leimbach
2010-11-15 23:45 ` David Leimbach
2010-11-15 23:56 ` David Leimbach
2010-11-16 0:38 ` Federico G. Benavento
2010-11-16 0:59 ` ron minnich
2010-11-16 4:47 ` David Leimbach
2010-11-16 4:57 ` Federico G. Benavento
2010-11-16 4:58 ` Federico G. Benavento
2010-11-16 5:01 ` David Leimbach
2010-11-16 5:21 ` cinap_lenrek
2010-11-15 16:26 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='AANLkTimkoGTiidnM7RuA8Mvj84MyhMOVFx7Pj4=omXyp@mail.gmail.com' \
--to=leimy2k@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).