nick@ccicpg.UUCP (Nick Crossley) (10/04/88)
In article <4463@lynx.UUCP> m5@lynx.UUCP (Mike McNally) writes: >Out of curiosity, do any Sun/AT&T insiders (or anybody else) have any >information on file system compatibility between SunOS/SV.3 file >systems and the new SV.4 file system(s)? Should one be able to mount >AT&T *and* SunOS file systems on the same machine? Will naughty >programs that directly read System V-style directories be supported? >What's the scoop? > >Mike McNally Lynx Real-Time Systems >uucp: {voder,athsys}!lynx!m5 phone: 408 370 2233 According to the recent SysV.4 SDC, V.4 will fully support both BSD and AT&T file systems. The file systems may be mixed as desired, and both may be remote mounted over either NFS or RFS, or both at once. And, at least in theory, it should be easy to add file systems of one's own design. The only question I raised which has not yet been answered is what happens to the current source incompatibility between DIRSIZ: DIRSIZ(p) is a macro with a parameter in BSD systems, and is a #define'd constant in SysV systems. I do not know how they are going to resolve that in V.4. -- <<< standard disclaimers >>> Nick Crossley, CCI, 9801 Muirlands, Irvine, CA 92718-2521, USA Tel. (714) 458-7282, uucp: ...!uunet!ccicpg!nick
gwyn@smoke.ARPA (Doug Gwyn ) (10/05/88)
In article <28040@ccicpg.UUCP> nick@ccicpg.UUCP (Nick Crossley) writes:
-The only question I raised which has not yet been answered is what happens
-to the current source incompatibility between DIRSIZ: DIRSIZ(p) is a macro
-with a parameter in BSD systems, and is a #define'd constant in SysV systems.
-I do not know how they are going to resolve that in V.4.
It's not important, since it's not a required part of <dirent.h>.