wicinski%nrl-css.arpa@NRL-CSS.ARPA (tim wicinski) (03/08/88)
not that apollo implemeneted wrong or anything, but i noticed the major flaw is that you can not use the C compiler on NFS mount if the abject files plan to exist on nfs partitions. is this a problem with cc or with nfs? can someone inside apollo tell me if a fix is planned? (also known as things the salespeople forget to tell you). tim wicinski naval research labs --------
rees@apollo.uucp (Jim Rees) (03/09/88)
not that apollo implemeneted wrong or anything, but i noticed the major flaw is that you can not use the C compiler on NFS mount if the abject files plan to exist on nfs partitions. is this a problem with cc or with nfs? can someone inside apollo tell me if a fix is planned? The problem is that the compiler maps the output file into its address space when it generates the object module. This is faster than building the image in temporary memory then writing it out to a file, and is analogous to the way the object modules are loaded when you run a program. But it bypasses the ios layer, which is where NFS is implemented. You could fix it by making the compiler notice when the output is not to the domain file system, and have it build into a temporary file then copy. I don't know if there are any plans to do this in the immediate future.