My guess is that dd-wrt isn't compatible with openwrt-packages...
I tried E-WRT-0.3 long time ago... and when I compiled a new firmware-image
it "optimized" libc and removed all unused functions. This resulted into
that it was impossible to know if an uploaded binary would work or not...
some fun
I wanted to use owfs in a Ruby project so I decided to port the Python
ownet client to Ruby.
While doing the port I found that Connection.read contains the following code:
while 1:
data = s.recv(24)
if len(data) is not 24:
raise exShortRead
re
New documentation on persistent connections:
http://www.owfs.org/index.php?page=persistent-connections
On 2/11/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
On 2/10/07, Peter Kropf <[EMAIL PROTECTED]> wrote:
> Hi Pedro -
>
> I'm (slowly) in the process of implementing the changes needed for
>
On 2/11/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> New documentation on persistent connections:
> http://www.owfs.org/index.php?page=persistent-connections
(...)
> Yes, owserver supports persistent connections, but they must be REQUESTED
> and GRANTED. (It's only a single bit to signal this).
Logo design came up on my lab's mailing list not too long ago. One person
submitted the following website as a guide:
How to fake ... a Web 2.0 Logo
( http://web-design-book.com/2007/01/23/how-to-fake-a-web-20-logo/ )
Anyways, I have attached a logo idea. The image is based off of a project
lo
i was thinking about OWFS name
OWFS isn't owserver :/
all OW software could be called OW Suite or something else
OWServer couldn't be server,
i think that server is a machine,
owd could be more *nix like,
for windows users something like owservice could be better understood
check http
another interesting daemon term definition
http://www.definethat.com/define/185.htm
Roberto Spadim escreveu:
> i was thinking about OWFS name
> OWFS isn't owserver :/
> all OW software could be called OW Suite or something else
>
> OWServer couldn't be server,
>i think that server is a machine
