From: "Sergey S. Kostyliov" <rathamahata@php4.ru>
To: reiserfs-list@namesys.com
Subject: Re: bk pull problem (reiser4)
Date: Thu, 15 Jan 2004 18:03:20 +0300 [thread overview]
Message-ID: <200401151803.20907.rathamahata@php4.ru> (raw)
In-Reply-To: <200401121528.14023.rathamahata@php4.ru>
On Monday 12 January 2004 15:28, Sergey S. Kostyliov wrote:
> Hello all,
>
> I can not pull from reiser4 tree,
> bk pull is just waited indefinitely:
> rathamahata@arise reiser4 $ bk parent
> Parent repository is bk://bk.namesys.com/bk/reiser4
> rathamahata@arise reiser4 $ bk pull
> Pull bk://bk.namesys.com/bk/reiser4
> -> file://usr/local/src/bk/reiser4
> (nothing more)
The problem hasn't gone away. I believe there are no any network problems
on my side. Is `bk clone` allowed for namesys's bk trees? Perhaps there
was some kind of announcement that I've missed?
Any hints will be appreciated.
>
> but bk clone is still posiible.
>
> traceroute to thebsh.namesys.com (212.16.7.65), 30 hops max, 40 byte
> packets 1 breuss-10.ws.ehouse.ru (192.168.114.10) 1.251 ms 2.773 ms
> 28.617 ms 2 hobbit-gw.ehouse.ru (193.111.92.33) 11.445 ms 9.780 ms
> 9.920 ms 3 express-ehouse.express.ru (212.24.42.9) 9.884 ms 9.800 ms
> 9.914 ms 4 LYNX-M9.ATM6-0.30.M9-R1.msu.net (193.232.127.230) 4.985 ms
> 12.488 ms 4.978 ms 5 LYNX-M9.ATM6-0.30.M9-R1.msu.net (193.232.127.230)
> 6.080 ms 5.403 ms * 6 thebsh.namesys.com (212.16.7.65) 5.847 ms 5.469
> ms 5.147 ms
--
Best regards,
Sergey S. Kostyliov <rathamahata@php4.ru>
Public PGP key: http://sysadminday.org.ru/rathamahata.asc
next prev parent reply other threads:[~2004-01-15 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 12:28 bk pull problem (reiser4) Sergey S. Kostyliov
2004-01-15 15:03 ` Sergey S. Kostyliov [this message]
2004-01-31 7:46 ` Alexander Lyamin
2004-01-31 9:35 ` Alexander Lyamin
2004-01-30 11:40 ` Vince
2004-01-30 12:33 ` Sergey S. Kostyliov
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=200401151803.20907.rathamahata@php4.ru \
--to=rathamahata@php4.ru \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.