9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: pac <cej@cejchan.gli.cas.cz>
To: 9fans@cse.psu.edu
Subject: [9fans] update failed :-(
Date: Wed, 15 Aug 2001 16:07:44 +0200	[thread overview]
Message-ID: <cej-1010815160744.A01284@cejchan.gli.cas.cz> (raw)

Hi,

I tried to upgrade with the 03270425.9gz package (I hope that plan9.9gz of Mar 28 contains the last full update); however, I did not succeed.
Here is what I did:

term% mount /srv/kfs /n/kfs
term% wrap/inst -or /n/kfs 03270425.9gz
skipping /lib/vgadb: locally modified
write /n/kfs/sys/src/cmd/vt/main.c: file does not exist
write /n/kfs/sys/src/cmd/vt/vt.c: file does not exist
write /n/kfs/sys/src/fs/port/arp.c: file does not exist
write /n/kfs/sys/src/fs/port/time.c: file does not exist
write /n/kfs/sys/src/fs/clone/mkfile: file does not exist
write /n/kfs/sys/src/fs/emelie/etherif.c: file does not exist
write /n/kfs/sys/src/fs/emelie/mkfile: file does not exist
write /n/kfs/sys/src/fs/emelie/toy.c: file does not exist
write /n/kfs/sys/src/fs/plan9pc/etherif.c: file does not exist
write /n/kfs/sys/src/fs/plan9pc/toy.c: file does not exist
write /n/kfs/sys/src/fs/plan9pc/mkfile: file does not exist
write /n/kfs/sys/src/libc/9sys/sysfatal.c: file does not exist
write /n/kfs/sys/src/libc/port/tokenize.c: file does not exist
write /n/kfs/sys/src/libregexp/regsub.c: file does not exist
write /n/kfs/sys/src/libregexp/rregsub.c: file does not exist
write /n/kfs/sys/src/libsec/port/des3CBC.c: file does not exist
write /n/kfs/sys/src/libsec/port/des3ECB.c: file does not exist
write /n/kfs/sys/src/libsec/port/mkfile: file does not exist
write /n/kfs/sys/src/libsec/port/x509.c: file does not exist
write /n/kfs/sys/src/libsec/port/md5pickle.c: file does not exist
write /n/kfs/sys/src/libsec/port/sha1pickle.c: file does not exist
write /n/kfs/sys/src/libsec/port/decodepem.c: file does not exist
write /n/kfs/sys/src/libthread/thread.c: file does not exist
write /n/kfs/sys/src/libhttpd/gethead.c: file does not exist
write /n/kfs/sys/src/libhttpd/urlunesc.c: file does not exist
write /n/kfs/sys/src/libhttpd/hio.c: file does not exist
write /n/kfs/sys/src/libhttpd/mkfile: file does not exist
write /n/kfs/sys/src/libhttpd/parse.c: file does not exist
write /n/kfs/sys/src/libhttpd/httpunesc.c: file does not exist
write /n/kfs/sys/src/libhttpd/urlconv.c: file does not exist
write /n/kfs/sys/src/libhttpd/httpconv.c: file does not exist
write /n/kfs/sys/src/libhttpd/lower.c: file does not exist
write /n/kfs/sys/src/libhttpd/alloc.c: file does not exist
write /n/kfs/sys/src/libhttpd/checkcontent.c: file does not exist
write /n/kfs/sys/src/libhttpd/okheaders.c: file does not exist
write /n/kfs/sys/src/libhttpd/unallowed.c: file does not exist
write /n/kfs/sys/src/libhttpd/fail.c: file does not exist
write /n/kfs/sys/src/libhttpd/redirected.c: file does not exist
write /n/kfs/sys/src/libcontrol/button.c: file does not exist
write /n/kfs/sys/src/libcontrol/entry.c: file does not exist
write /n/kfs/sys/src/libcontrol/text.c: file does not exist
wrap/wdiff -r /n/kfs 03270425.9gz \
	/lib/vgadb \
term%


Any hint? TIA, regards,
Peter

--
Peter A Cejchan
biologist
Acad. Sci., Prague, CZ
<cej at cejchan dot gli dot cas dot cz>



                 reply	other threads:[~2001-08-15 14:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=cej-1010815160744.A01284@cejchan.gli.cas.cz \
    --to=cej@cejchan.gli.cas.cz \
    --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).