[tahoe-dev] debian package: initscript and FHS

[Greg Troxel]

bertagaz at ptitcanardnoir.org writes:

> - About the FHS issue, I was considering several options : having
>  configuration options for the logs/, storage/ and tmp/ directories, but
>  that would require to add a lot more options to the create-node command
>  (although some auto-detection if running on Debian might configure it
>  almost automatically), or having only one configuration option, like
>  `debian_layout = true`, that would help tahoe to know  where its
>  different parts resides on the system. Which way sounds best to you? Or
>  did you already have some ideas/alternative ways about this?

I'm not sure I fully understand the issue and your proposed changes.
Could you explain in depth which pieces of the current node directory
that should be elsewhere (in a FHS-compliant world), and which pieces
would remain?  Then, what does "remain" mean - is there anything left
that looks like a node directory does now?  Also, what happens with
multiple nodes on a single computer, operated by different uids?

As a concrete example, it might help to explain how this would all work
for the following set of 9 nodes.  I realize that's a lot and most
machines would have less, but I'd say the following isn't insane on a
multi-user server.

  uid "tahoes": pubgrid storage node
  uid "tahoes": foo introducer node
  uid "tahoes": foo storage node

  uid "alice": pubgrid client node
  uid "alice": foo client node

  uid "bob": foo client node
  uid "bob": bob introducer node
  uid "bob": bob storage node
  uid "bob": bob client node
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110502/0c29fde7/attachment.pgp>