Re: 3.0.15 missing ne2k-pci module?
#include <hallo.h>
Robert de Forest wrote on Wed Oct 24, 2001 um 11:44:22PM:
> I tried to do a floppy-less (windows+loadlin) install but stalled when I
> found that the ne2k-pci module was missing. I was using the udma100
Yes. The driver is built-in into the the kernel, and should be
auto-loaded during the PCI scan at boot time.
> files. I need this module for my RealTek 8029 ne2k clone.
Just configure the network, the driver should be present.
> I also wonder, and I hope this isn't a FAQ, why the install drivers
> include modules for more than is needed to bootstrap the install
> process? It seems like everything needed to get almost any machine
> online would fit on less than 6 disks. For example, I'd remove the
> following modules:
Use compact flavor if you want to create <= 3 floppies.
> ipv4/ip_masq_*
> video/*
> misc/*
The problem is following: once the system base is installed, it should
be completely useable. If I drop some modules, the kernel installation
is not complete. We /could/ modify debootstrap to complete the
installation, but a) it is hacking and b) the kernel packages may not be
available in woody since we use Sid packaged for building boot floppies.
> This came to 6M uncompressed when I looked, or half the entire modules
> hierarchy.
Yes, most people would need 1-2 driver floppies. But because of the
variety of hardware it is not easy to say what is needed and what not.
But if you have some spare time, you may look at the modules and sort them into
subsections, so (for example) common modules are stored on floppies 1
and 2, SCSI stuff is on floppy 3 and additional network modules, and
network, various fs drivers etc. are on 4. You see, it is not quite easy
to make such decissions.
> And why is the install kernel used as the system kernel rather than
> installing a kernel-image-... package. Is this historical?
See above. When we put the kernel on the BFs, it is consistent. We can
guarantee that the kernel which has allready booted on the machine and
used to install it is useable for this system.
But you have probably right. Installing kernel-image along with other
packages is a bad idea, IMHO, since it has many predepends.
But when Woody stabilize, the kernel installation routine could be
modified to get the package from the net and extract its contents. Then
the number of driver floppies could be rely minimized to only one,
containing NIC and FS drivers.
Who has more comments to this proposal?
Gruss/Regards,
Eduard.
--
<_eis>
<_eis>
<_eis>
<florg> _eis: wenn du dich im RL unterhaelst, machst du dann auch ab und zu
einfach nur den mund auf, so als wuerdest du was sagen wollen?
-- #debian.de
Reply to: