Re: hurd does NOT need /hurd
On Mon, 20 May 2002, Marcus Brinkmann wrote:
> > In fact, any program that uses getent(), may end up using modules, by way of
> > pam.
> > They all contain executable code.
> All this is irrelevant to the decision where to put them.
So, being irrelvant, they can go anywhere, as long as the tools can cope?
So, in that regard, Debian policy says that hurd's translators should go in
/lib/modules, as that's where kernel-specific extensions go.
If GNU/hurd were an OS by itself, it could use /hurd. But, the Debian port
should follow Debian Policy, and this says /lib/modules.
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org