<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>You're quite welcome; I'm an command line hand, so despite my only Python experience being blindly running pyrit, the guide worked fine for me (though I'm still working out that tahoe-client == gateway; that's not at all clear on first reading).<br><br>I'll be trying an ODROID-U2 in the upcoming weeks; with 2GB of RAM, I actually fully expect it to run the trial without issue, and be capable of supporting 4+ storage nodes running through a USB hub or dual drive USB->SATA bays. At $89, I'm hoping it's actually capable of acting as a few storage nodes as well as an Introducer.<br><br>For #671, if I can start getting a test grid creation script up, I'll at least take a look at the leasedb - SQlite can't be difficult to work with.<br><br><br><div>> Date: Thu, 26 Sep 2013 17:20:04 +0000<br>> From: zookog@gmail.com<br>> To: tahoe-dev@tahoe-lafs.org<br>> Subject: Re: [tahoe-dev] Precise Puppy (linux) tahoe-lafs 1.10.0 initial report<br>> <br>> Welcome, Garonda Rodian!<br>> <br>> Thanks for the nice user report!<br>> <br>> <br>> On Wed, Sep 25, 2013 at 2:49 AM, Garonda Rodian <deepside@hotmail.com> wrote:<br>> ><br>> > First, let me say the quickstart guide is great;<br>> <br>> Thanks for the positive feedback! We get a lot of negative feedback on<br>> the docs for new users, and so I still want to improve them (see<br>> #1024). But it is nice to know that the current docs work well for<br>> some users.<br>> <br>> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1024# introductory docs<br>> are confusing and off-putting<br>> <br>> <br>> > if I get farther along, I may attempt to build a "quick config" menu system/wizard/installer to reduce the need for editing text files for the average user.<br>> <br>> That's an interesting idea! There are only a few things that need to<br>> be configured, but that is still a big hurdle to users who aren't<br>> comfortable with the command-line and with using text editors on<br>> config files.<br>> <br>> > P.S. If I'm lucky, the Raspberry Pi has completed its trial run, though if this is the RAM requirement, I'm not holding out much hope.<br>> <br>> It is too bad about #1476, because I really like to be able to run<br>> unit tests everywhere and all the time. However, I believe that the<br>> gateway or storage-server itself will run fine on Raspberry Pi, even<br>> if (due to #1476) the tests will fail.<br>> <br>> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1476# unit tests running<br>> out of memory on FranXois lenny-armv5tel buildbot or on a 613 MiB EC2<br>> <br>> > P.P.S. Has anyone tried tahoe-lafs on the Debian (Ubuntu, if you must) build for an ODROID-U2 or ODROID-XU? Those look like the logical next step up in the small ARM space.<br>> <br>> I've never heard of these. I must say that they sound pretty cool! I'm<br>> pretty sure Tahoe-LAFS will compile and run just fine on those, on<br>> either Debian or Ubuntu, except possibly with the #1476 issue again.<br>> <br>> > P.P.P.S. I don't see where to give a storage node either a limit (not reserved[_free]_space, but maximum[_used]_space), or a location.<br>> <br>> This is ticket #671, which has been fixed by Mark Berger, but is<br>> blocked on getting into trunk until some other patches that it depends<br>> on get into trunk. Want to help? Track down which patches are blocking<br>> this and do a code-review of them! (Even if someone else has already<br>> done a code-review, more code-reviews is always better!)<br>> <br>> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/671# bring back<br>> sizelimit (i.e. max consumed, not min free)<br>> <br>> Regards,<br>> <br>> Zooko<br>> _______________________________________________<br>> tahoe-dev mailing list<br>> tahoe-dev@tahoe-lafs.org<br>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev<br></div> </div></body>
</html>