Hello all,
Just thought I'd introduce myself. I am just getting started with
Voyage, and I really like what I see so far. I'll be porting some
stuff I had working on OpenWRT over in the next few days.
I'm trying to decide which direction to go to put a web-ui on the box.
Right now, I am headed
This: tar --numeric-owner -zxvf voyage-version.tar.gz
Should be: tar --numeric-owner -Bxvf voyage-version.tar.bz2
Because of the switch to bz2 for the compression.
-jeff
___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
Design philosophy and guidelines:
1. Small. It must be damn small in size as it runs on embedded system.
2. Extensible. It must be easily extensible to add support for managing new
I agree in principle, but I note that 1 gig CF cards are now USD 11,
which puts them in reach of all but the
domain (more precisely,
as beerware).
These modifications are covered by a BSD-style license:
Copyright (c) 2009, Jeff R. Allen j...@nella.org
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
I think that is an integral part of current madwifi - rather than debian or
voyage.
I can confirm that I see it on OpenWRT as well. There's something a
little bit out of whack with Linux 2.6.28, madwifi and (maybe) gcc
right now.
I regret that I don't have time right now to look into it, I'm
I don't bother with ext3 since it drastically reduces the lifetime of
the CF card. Also, log files and the like are not written to disk so
there is not as much IO as you might think.
Not to be critical, but your response is contradictory and I can't
make sense of it. Can you clarify?
Some
