On Wed, 2005-04-20 at 02:03, Paul Alfille wrote:
> On Tuesday 19 April 2005 07:24 pm, Christian Magnusson wrote:
> > Download the package "firmware 0.1" from:
>
> Christian, version 0.1 is newer that R 0.9? The dates indicate that.
>
> Paul
>
Yes... The firmware release is definitely newer (
On Tuesday 19 April 2005 07:24 pm, Christian Magnusson wrote:
> Download the package "firmware 0.1" from:
Christian, version 0.1 is newer that R 0.9? The dates indicate that.
Paul
---
This SF.Net email is sponsored by: New Crystal Reports XI.
On Tuesday 19 April 2005 07:48 pm, Gregg C Levine wrote:
> Hello from Gregg C Levine
> I think we've got some code that won't compile inside the code for
> ownfsd. Please examine the script at the bottom of my signature.
Gregg,
I think you have an optimistic view of "early stages". It doesn't com
Hello from Gregg C Levine
I think we've got some code that won't compile inside the code for
ownfsd. Please examine the script at the bottom of my signature.
Everything else compiled correctly, but the code block for ownfsd,
didn't. The reason why the script doesn't represent an accurate
compilatio
I have uploaded the first version of the complete firmware for the
WRT54G router. It contains:
ewrt-0.3 beta 2 rc1 (based on Linksys 3.01.03)
owfs
fuse
temploggerd
rrdtools
Support for /opt/rc.start script.
Download the package "firmware 0.1" from:
http://sourceforge.net/project
On Tue, 2005-04-19 at 11:09 -0400, Paul Alfille wrote:
> The bad news: NFS seems to depend on a filehandle. It is an opaque 64 byte
> structure. We'll have to generate it for every path and verify it with every
> access, since it goes to and from the client.
It doesn't just seem to. The NFS "vno
I noticed that owfs/modules/owfs/src/c/Makefile.am NEVER
cared about if OW_MT was set or not... I added it now.
--
Christian Magnusson <[EMAIL PROTECTED]>
---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new fun
I found the problem now... It's kind of a problem in the initialization
of pthread. __pthread_initialize() is automatically called when starting
an application. After running daemon() you get a new process id, and
internal pointers and pid's are pointing to the dead process and stack.
It works if
As I looked through the specs on nfs I was encouraged at first be the
"stateless" design, until I found they cheated.
First of all, a good reference: http://www.freesoft.org/CIE/Topics/115.htm
And from that, the protocol: http://www.freesoft.org/CIE/RFC/1813/index.htm
The good news: open and clo
On Monday 18 April 2005 05:38 am, Christian Magnusson wrote:
> That seems to be a good idea to expand the number of platforms
> to support. It should be pretty easy to implement if using unfs3
> so it's just to dig into the code and spend some late nights
> with coffee in front of the computer.. :)
I don't think it is so unusual to have a directory listing become out of
date.
This must happen frequently while one process is navigating the directory,
another can change entries in it.
The first process won't know anything about changes to the structure once
it has traversed that particular n
On Tue, 2005-04-19 at 09:31 +0100, [EMAIL PROTECTED] wrote:
> What is the expected value of st_nlink - should it include the number of
> dirs in sub-dirs as well.
> That doesn't sound right to me.
>
yes... It should be like that. Temp-sensor 10.xx/. should have
st_nlink=2 since there are
What is the expected value of st_nlink - should it include the number of
dirs in sub-dirs as well.
That doesn't sound right to me.
Once a directory is enumerated, the number of sub-dirs is known and
contained in a linked list.
Iterating that list to count the sub-dirs should be trivial.
I also n
13 matches
Mail list logo
