From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] issues after pull
Date: Mon, 14 Apr 2003 18:47:08 -0400 [thread overview]
Message-ID: <6b6c9b36613dcffee5d2cde6c7cf1192@plan9.bell-labs.com> (raw)
In-Reply-To: <3E9B4199.2050107@ameritech.net>
> fscmd: '/bin/fscmd' directory entry not found
> /n/kfs/dist/replica/client/_plan9.db: rc (pull): can't open: access permission denied
This sounds like the pull script itself got rewritten
by your pull. After being rewritten, it then started
executing the new file at the byte offset where it left
off in the old file, which caused your problem.
I don't change pull almost ever, so this won't happen
again (the last change was October 2002). Pull is
special because it's in glenda's bin directory.
Binaries in standard bin directories are "safeinstalled"
to help avoid this problem.
> Also, after recompiling libs/bin/kernel, installing and rebooting: Acme faults every
> time I Delete an acme window, or, every once in a while when I Put. Roo?
Aha! Someone else complained about this too, a week ago,
but I didn't see the bug then. I fixed the source on sources.
New C library will appear tomorrow morning. The bug has
gone unnoticed for about six weeks -- looks like acme is the
only program that uses runevsmprint, and I didn't recompile
all the binaries when I made the change, because it didn't
seem worth it. (I cleaned up some error handling in the
(rune)fmtstr and (rune)vsmprint routines.)
Russ
next prev parent reply other threads:[~2003-04-14 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 23:17 northern snowfall
2003-04-14 22:36 ` ron minnich
2003-04-14 22:47 ` Russ Cox [this message]
2003-04-15 10:21 ` Nicholas Waples
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=6b6c9b36613dcffee5d2cde6c7cf1192@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).