On 3/10/2010 5:59 PM, John Sambrook wrote:
Regarding mount tables, I'm assuming the issue is that the mount-table is modified on a per-user basis. So a single, shared-over-the-network version isn't going to hack it. Correct?
A single user with Cygwin installed on a network location is just like a local install for that user except for the extra network overhead. So 'setup.exe' will do this for you very nicely.
I also suspect that there are probably packages in a full-up distribution that write into locations in the distribution tree. For example, if I fire up pdflatex, I believe it invokes (kpathsea?) to build font-files or something along those lines.
This can happen, though not typically.
I would guess there is also the question of where writable directories like /tmp and /var reside. Should I have one network-wide shared /tmp or should each client somehow get its own? I'd prefer the latter.
The latter. You'd also need at least your home directories to be writable at least. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
