Path: utzoo!attcan!uunet!snorkelwacker!ai-lab!zurich.ai.mit.edu!jinx From: jinx@zurich.ai.mit.edu (Guillermo J. Rozas) Newsgroups: comp.sys.hp Subject: Re: makecdf Message-ID: Date: 5 Nov 90 20:56:24 GMT References: <44@gauss.mmlai.UUCP> Sender: news@ai.mit.edu Reply-To: jinx@zurich.ai.mit.edu Organization: M.I.T. Artificial Intelligence Lab. Lines: 33 In-reply-to: burzio@mmlai.UUCP's message of 1 Nov 90 18:00:11 GMT In article <44@gauss.mmlai.UUCP> burzio@mmlai.UUCP (Tony Burzio) writes: Path: ai-lab!snorkelwacker!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!uunet!mmlai!burzio From: burzio@mmlai.UUCP (Tony Burzio) Newsgroups: comp.sys.hp Keywords: NFS service Date: 1 Nov 90 18:00:11 GMT Organization: Martin Marietta Labs, Baltimore Lines: 14 We have a cluster on our HP machines, allowing the use of CDFs on any machine in the cluster. A file that is cdf'ed may be different on each node. I would like to know from the HP gurus if this could be expanded to correctly choose machine names across an NFS connection. This would allow us to store binaries, with the same name for different architectures, using cdfs. Right now, you get the file using the NFS servers' name (understandable) but it would be better if it was available in general. Comments? ********************************************************************* Tony Burzio * Like, spooky man! Martin Marietta Labs * mmlab!burzio@uunet.uu.net * ********************************************************************* I second that request. At the very least, add a new context string (NFS) that the NFS daemons (nfsd) use so that I could choose what the machines that NFS-mount the file system would see. On a related note, looking through /usr/include/syscall.h and syscalls.h, there seems to be a SETCONTEXT system call. How about documenting/describing it? Maybe it does what I want if I invoke it from a program and then exec nfsd?