I'm still waiting on Brian to comment on whether to integrate it as a
flamethrower transport or separately (like how Andrea has done it).
I think my code already have some integration with Andrea's work - the
major difference now is he is using the official python BT and I'm using
libBT.
I should
Erich Focht wrote:
Hi Andrea,
do you (or anybody else) mind checking this into trunk? It's easier to play
with it from there and it looks already quite usable.
Yes, we could check... maybe we've to synchronize with Bernard to merge
both our work and we've to choose if we want to use libbt or
Hi Andrea,
do you (or anybody else) mind checking this into trunk? It's easier to play
with it from there and it looks already quite usable.
Regards,
Erich
On Monday 09 January 2006 10:08, Andrea Righi wrote:
> Hi all,
>
> other work for the bittorrent transport...
>
> In this patch I've added
Using UYOK (branch/3.6.x) with RHEL3u5 (2.4
kernel).
I almost got it working, except after
imaging, I keep getting the following error:
[: 18: unknown operand
This repeats forever and I could not
figure out where it is coming from...
The error message is shown repeatedly
after "mount /d
Title: Re: [Sisuite-devel] Re: Bit-Torrent transport
Hey Andrea:
What speed did you get
transferring between one peer to another peer? As I have mentioned to you
with my tests, I was only able to get 1.5MBytes/sec max (with --max_upload_rate
0 on a 100MBit network).
With LibBT's btget
Hi all,
other work for the bittorrent transport...
In this patch I've added to BOEL binaries the standard bittorrent python
client "freezed" as a normal ELF binary, as suggested by Bernard in a
previous chat with him.
This is a very important issue, because with the python interpreter the
B
I think that would be quite useful too... perhaps just start sshd in
the shell out routine?
Jeremy
Bernard Li wrote:
How about turning on sshd (on the node) during imaging? If it fails for
whatever reason, as long as network is working you can ssh in to trouble
shoot the problem.
Though
Okay it works - I'm ready to
check it in. Probably want to add modprobe.old in there as
well.
Now I'm stuck with not having
"sysfs", specifically this fails:
mount sysfs /a/sys -t sysfs -o defaults || shellout
Can someone confirm that this
does not exist in the 2.4 kernel? If so the
