Subject: Re: /usr/mdec is a headache for shared ports
To: None <>
From: None <>
List: tech-userlevel
Date: 06/08/2000 18:57:34
> > In any case we need a port-specific place to put the boot
> > files.
> >
> > /usr/m${MACHINE} is one option as is /usr/mdec/${MACHINE}.
> How about /usr/mdep/${MACHINE}/ The "dec" in mdec was for
> Digital, wasn't it? :-)

Well, we could just after the fact say that it can be expanded in
another "portable" way (as mentioned elsewhere): "Machine DEpendent
Code". :-)

We could also in principle create a new install set which contains
these "bits closely related to the hardware" so that the base.tgz
can be shared among architectures which shares instruction set and
executable format.

The suggestion of doing /usr/mdec/${MACHINE} I guess is so that
several different architectures with same instruction set and
executable format can more easily share /usr?  I think it's a fine
idea, though it leaves /sbin/disklabel unsolved.  Symlink into
/usr/mdec?  (duck...:-)

Can LKMs usually be shared between archs, or are those also
problematical?  (Just eyeballing base/md.*)

- H=E5vard