On Wednesday, April 25 2001, Derek Atkins said:
> [EMAIL PROTECTED] writes:
> > The point is: the sysname values needs to describe the machine on
> > which the cache manage is currently running with sufficient
> > granularity, and not be a more generic specification that describes
> > the set of platforms on which the kernel module can be loaded.
> 
> Perhaps for Linux we really want something more akin to:
>       i386_redhat_62
> or    i386_debian_potato

Unfortunately, all of these are somewhat nitemare-ish as far as
maintaining a set of symlinks in afs for binaries are concerned.  In a
lot of ways, it almost seems as though there needs to be a mechanism to
have a "canonical" sysname which could be i386_linux24_glibc22 or
whatnot, but also be able to have some sort of table of compatible
sysnames to try if there isn't the one you're looking for.  But I
haven't gone to see how non-trivial that would be to do yet and I'm
guessing it wouldn't be pretty :(

Jeremy

-- 
Jeremy Katz
[EMAIL PROTECTED]    | [EMAIL PROTECTED]
http://linuxpower.org   | Developer, NCSU Realm Kit for Red Hat Linux
GPG fingerprint: 367E 8B6B 5E57 2BDB 972A 4D73 C83C B4E8 89FE 392D

PGP signature

Reply via email to