Subject: Re: modload vs. ld/libbfd
To: Ignatios Souvatzis <is@netbsd.org>
From: Luke Mewburn <lukem@NetBSD.org>
List: tech-install
Date: 03/28/2005 10:17:14
--FrxVhwK/bNRjN48l
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Mar 24, 2005 at 10:52:32PM +0100, Ignatios Souvatzis wrote:
| modload needs ld, currently.
|=20
| I think we should either move /usr/bin/ld and /usr/lib/libbfd.so.6
| (as of 2.0) to the base set, or move modload to comp.
modload is used by the base startup scripts, so anything it depends
upon should be in the base set...
However, it's a bigger problem than that: modload is used early in the
boot sequence, before /usr is mounted (i.e, before /usr/bin/ld may exist).
The solutions include:
1. Rewrite /sbin/modload not to depend upon /usr/bin/ld.
2. Move ld to /bin. (Ewww.)
3. Deprecate support for loading lkms before /usr is mounted.
The rationale for this was ``/usr may need an lkm to load'',
but that's obviously not being used in the practice because
modload needs ld which is in /usr/bin, and noone has raised
this as a problem!
There's also a separate case for deprecating support for
loading /usr via the network where it needs more special
handling that / (e.g, NFS over ipsec with krb5 IKE), as
it's causing a larger maintenance headache due to the
potential for cycles in the rc.d startup sequence.
--FrxVhwK/bNRjN48l
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)
iD8DBQFCR00KpBhtmn8zJHIRAjhsAJ41rDOy4cD3JX20o2eIqJb8n6NOFwCdGarC
nDf5dNv/b6uR/nJP+FLEcrE=
=LhC8
-----END PGP SIGNATURE-----
--FrxVhwK/bNRjN48l--