9front - general discussion about 9front
 help / color / mirror / Atom feed
From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: 9front@9front.org
Subject: Re: [9front] cwfs fsmempercent
Date: Mon, 5 May 2014 20:15:07 +0900	[thread overview]
Message-ID: <CBD0FC36-68F0-4208-BF25-7540455FB566@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <79CB058C-F091-4CEB-9F0B-D01864EE5973@ar.aichi-u.ac.jp>

now I could succeed to update by hg.

I don't know why I was in trouble.
probably straggling led me to bad way.
send time, I reinstalled /dist/plan9front/ and get success.
your fix is nice!

thanks a lot.

by the way, a command name 9hg may be useful.

#!/bin/rc
rfork n
cd /
if(! test -d .hg)
	bind -ac /dist/plan9front /
if(! ~ $#* 0)
	hg $*
if not
	hg help | awk '/^ [a-z]*/ {s=$0; sub(" *[a-z]* *","",s); printf("9hg %s\t# %s\n", $1, s)}'





On 2014/05/05, at 17:00, arisawa <arisawa@ar.aichi-u.ac.JP> wrote:

> I have cleaned directories below:
> /dist/plan9front/
> /sys/lib/python/mercurial/
> /sys/lib/python/hgext/
> /sys/src/cmd/hg/
> and reinstalled them using latest iso image from 9front (опен-сссл).
> and then
> (1) allowed mode to cwfs64x
> (2) auth/as glenda sysupdate
> 
> note that host owner of my terminal is "arisawa".
> 
> term% pwd
> /dist/plan9front
> term% ls -l
> d-rwxrwxr-x M 20 glenda sys   0 Apr 28 06:31 .hg
> --rw-rw-r-- M 20 glenda sys 724 Jun 15  2013 .hgignore
> term% ls -ld .hg/store
> d-rwxrwxr-x M 20 glenda sys 0 May  5 15:47 .hg/store
> term% ls -l .hg/store
> --rw-rw-r-- M 20 glenda sys  745978 May  4 22:05 .hg/store/00changelog.d
> --rw-rw-r-- M 20 glenda sys  228608 Apr 28 06:20 .hg/store/00changelog.i
> --rw-rw-r-- M 20 glenda sys 1521917 May  4 22:05 .hg/store/00manifest.d
> --rw-rw-r-- M 20 glenda sys  165888 May  4 22:05 .hg/store/00manifest.i
> d-rwxrwxr-x M 20 glenda sys       0 Apr 12  2013 .hg/store/data
> --rw-rw-r-- M 20 glenda sys  967509 May  4 22:05 .hg/store/fncache
> --rw-rw-r-- M 20 glenda sys     222 Apr 28 06:20 .hg/store/undo
> term% 
> 
> what else should I examine?
> 
> it seems "*.d" and "*.i" files are compressed.
> I am happier if I can decompress these file, because I have your update in "*.i" format.
> 
> term% ls -tl .hg/store/data/sys/src/cmd/cwfs |head
> --rw-rw-r-- M 20 glenda sys  2777 May  4 22:05 .hg/store/data/sys/src/cmd/cwfs/iobuf.c.i
> --rw-rw-r-- M 20 glenda sys  1686 May  4 20:15 .hg/store/data/sys/src/cmd/cwfs/all.h.i
> --rw-rw-r-- M 20 glenda sys  2777 Feb 14 23:09 .hg/store/data/sys/src/cmd/cwfs/malloc.c.i
> --rw-rw-r-- M 20 glenda sys  7113 Feb  4 04:05 .hg/store/data/sys/src/cmd/cwfs/portdat.h.i
> --rw-rw-r-- M 20 glenda sys  5523 Oct 17  2013 .hg/store/data/sys/src/cmd/cwfs/chk.c.i
> --rw-rw-r-- M 20 glenda sys 16946 Oct 16  2013 .hg/store/data/sys/src/cmd/cwfs/cw.c.i
> --rw-rw-r-- M 20 glenda sys  9457 Aug  8  2013 .hg/store/data/sys/src/cmd/cwfs/sub.c.i
> --rw-rw-r-- M 20 glenda sys  5470 Aug  8  2013 .hg/store/data/sys/src/cmd/cwfs/net.c.i
> --rw-rw-r-- M 20 glenda sys  3357 Aug  8  2013 .hg/store/data/sys/src/cmd/cwfs/srv.c.i
> --rw-rw-r-- M 20 glenda sys  7795 Aug  8  2013 .hg/store/data/sys/src/cmd/cwfs/main.c.i
> term% 
> 
> On 2014/05/05, at 13:32, cinap_lenrek@felloff.net wrote:
> 
>> this is an exception happening in
>> 
>> /sys/src/cmd/hg/mercurial/mpatch.c:424
>> 
>> parsing a revlog file. each file tracked by mercurial has
>> a revlog file containing the changes of this file. (binary
>> patches). these files are append only.
>> 
>> unfortunately, that stacktrace doesnt tell us what file
>> is corrupted.
>> 
>> what exactly did you do?
>> 
>> --
>> cinap
> 



  reply	other threads:[~2014-05-05 11:15 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  4:25 9FRONT "опен-сссл" Released sl
2014-04-28 10:52 ` cwfs fsmempercent arisawa
2014-04-28 17:08   ` [9front] " cinap_lenrek
2014-04-28 17:26   ` cinap_lenrek
2014-04-28 22:55     ` arisawa
2014-04-29 20:11       ` cinap_lenrek
2014-04-30 14:41         ` Kenji Arisawa
2014-04-30 20:14           ` cinap_lenrek
2014-05-01 10:39             ` 9pc64 arisawa
2014-05-01 11:07               ` [9front] 9pc64 Aram Hăvărneanu
2014-05-01 14:06                 ` arisawa
2014-05-01 14:25                   ` cinap_lenrek
2014-05-01 14:39                   ` cinap_lenrek
2014-05-01 15:27                   ` cinap_lenrek
2014-05-01 21:49                     ` Kenji Arisawa
2014-05-01 21:51                       ` cinap_lenrek
2014-05-01 23:22                         ` Kenji Arisawa
2014-05-01 23:34                         ` Kenji Arisawa
2014-05-02  0:22                           ` cinap_lenrek
2014-05-02 11:02                             ` Aram Hăvărneanu
2014-05-04  5:24                               ` malloc Kenji Arisawa
2014-05-04  8:22                                 ` [9front] malloc arisawa
2014-05-04 12:40         ` [9front] cwfs fsmempercent arisawa
2014-05-04 23:22           ` cinap_lenrek
2014-05-05  0:11             ` arisawa
2014-05-05  0:31               ` cinap_lenrek
2014-05-05  0:43                 ` cinap_lenrek
2014-05-05  2:04                   ` arisawa
2014-05-05  4:32                     ` cinap_lenrek
2014-05-05  8:00                       ` arisawa
2014-05-05 11:15                         ` arisawa [this message]
2014-05-05 12:08                           ` arisawa
2014-05-03  0:37   ` cinap_lenrek

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=CBD0FC36-68F0-4208-BF25-7540455FB566@ar.aichi-u.ac.jp \
    --to=arisawa@ar.aichi-u.ac.jp \
    --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).