Re: module won't install
>
> Date: Mon, 15 May 2000 11:26:56 +0200
> To: debian-boot@lists.debian.org
> cc: Jim Lynch <jim@laney.edu>
> From: Florian Hinzmann <fh@bigfoot.de>
> Subject: module won't install
>
> Hello!
>
>
> In an otherwise unrelated mail I found a paragraph
> related to the boot-floppies. I quote it here to make
> sure it is read by the boot-floppies team and as I
> had the same problem.
>
> On 14-May-2000 Jim Lynch wrote:
>
> > (you mean 2.2.13, right? but: those still
> > have a problem in modutils; I just discovered yesterday that the ne2000
> > driver (at least, hadn't tried others) will not load from the modutils tool
> > during install. It's possible that me having to reboot the install had some-
> > thing to do with that; if so, it means that the modutils had to be told
> > that the whole to-be-debian is mounted on /target, not /, -and- that after
> > the reboot it was -not- told this.)
>
> I did not reboot and had the same effect. Even worse:
>
> When I tried to install modules after that I did not even get
> the list of modules to choose one. I hit return in the main
> dbootstrap menu to install a module and the menu was redisplayed
> immediately.
>
> I did not use 2.2.13 yet, all this happened with 2.2.12. I might have
> the possibility to give it another try or do some further investigation
> tomorrow.
See, we knew the problem was in 2.2.12... but it was supposed to be fixed
in 2.2.13... Please test.
With knowing almost nothing about the internals of modconf, I suspect it
works; I also suspect the outer infrastructure which calls it of having
the problem. Second prize would go to a section of modconf that specially
handles the case of installing (i.e., partitions piled onto /target instead
of /).
How is this handled, btw?
- special cased in modconf? or
- handled outside of modconf, either by:
+ chrooting the call (so /target looks like / to modconf), or
+ passing where the lib dir is as an option/parameter to modconf?
- none of the above? If so, please explain or refer thereto.
Parts of the message this is a reply to suggest that a module list is
artificially created outside modconf. Am I getting warm? :)
-Jim
---
Jim Lynch Finger for pgp key
as Laney College CIS admin: jim@laney.edu http://www.laney.edu/~jim/
as Debian developer: jwl@debian.org http://www.debian.org/~jwl/
Reply to: