Vulture wrote: > Julie wrote: > > > > > > The same holds for sparc32/sparc64, mips/mips64, powerpc/powerpc64, > > > > and ia32/x86-64. > > > > > > Can you please summarize what directories are used to support the > > > different > > > architectures? I think that if we see the existing stuff laid out in one > > > place, > > > we can see what the pattern is, and where to put lsb version of things > > > should > > > be more obvious. > > > > Is it perhaps time to do hidden directories so that /usr/lib/libc.a > > expands automagically to /usr/lib/ia64/libc.a for ia64 boxen and > > /usr/lib/ia32/libc.a for ia32 boxen? > > > > I've used several systems with this sort of feature and it makes > > architectural dependencies =much= easier to handle. > > Yes, it looks nice at first, until you realize that each call to > > open ( ... ) > > suddenly does not solicit a file descriptor or error code, but a callback > "which context would you like ?". Exactly the kind of problem that has so > far prevented ACLs from taking the world by storm.
The systems I had used something like "@sys" (which I think is a DFS-ism) to control which one you got. So you either got the correct file or ENOENT. -- 8:26pm up 1 day, 1:55, 3 users, load average: 0.15, 0.29, 0.33
