[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Freedombox-discuss] freedombox.img with qemu



"tornow at riseup.net" <tornow at riseup.net> writes:

> On Sun, 16 Sep 2012 12:00:23 +0000
>>  Re: freedombox.img with qemu
>
> After a couple of days, and help from another user,  the best i could
> find is using chroot and qemu-arm-static, after "unpacking" the img with
> parted and dd...
>
> I am not sure if that is of any use, because i couldn't find a way to
> make the chroot act as if it was an external device yet
> (i would like to test freedombox-privxoy and plinth in the local
> browser).

It might be easier to just change Plinth to answer to public requests so
you can use the more recent VirtualBox image.  The following (UNTESTED)
code might fix that.  I'll see if I can't fix this properly for both
privoxy and Plinth this weekend.  I can't guarantee I'll have the time,
though.  Anybody else want to take a crack at it?

Apply this to Plinth by running ``patch -p1 < public-plinth.diff``,
after you save the below as "public-plinth.diff".

/--
|
| diff --git a/plinth.py b/plinth.py
| index adab110..fce2700 100755
| --- a/plinth.py
| +++ b/plinth.py
| @@ -116,12 +116,12 @@ def setup():
| 
|     # Add an extra server
|     server = _cpserver.Server()
| -   server.socket_host = '127.0.0.1'
| +   server.socket_host = '0.0.0.0'
|     server.socket_port = 52854
|     server.subscribe()
| 
|     # Configure default server
| -   cherrypy.config.update({'server.socket_host': '127.0.0.1',
| +   cherrypy.config.update({'server.socket_host': server.socket_host,
|                             'server.socket_port': cfg.port,
|                             'server.thread_pool':10,
|                             'tools.staticdir.root': cfg.file_root,
|
\--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/freedombox-discuss/attachments/20120921/85b2a3b4/attachment.pgp>


Reply to: