On Fri, Dec 29, 2023 at 12:31 PM Neal Becker <ndbecker2@xxxxxxxxx> wrote: > > On a philosophical note, I once worked on Apollo workstations. These could switch behavior between sysv and bsd unix. To do this, the kernel would interpret e.g. /usr/bin/$arch, substituting the env variable arch. At least that is my recollection of how this worked. Elegant I think, but some might see this as a security problem. > The AFS file system has a similar approach for its sysname, where the special value @sys is substituted by the kernel for files in that filesystem. A common way it was used was that something like /usr/local/bin was a symlink to /usr/local/.@sys/bin and the @sys variable would contain the architecture (and/or OS variant) redirect. The @sys value can contain a list of values to search for existence (exposed in /proc/fs/afs/sysname). On x86_64 I believe the default is amd64_linux26 (for historical reasons). For some large (often HPC) sites, which can have multiple system architectures and OS variants, having one common file system with software and libraries which can be selected by the client systems sysname "flavor" is valuable. -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
