Bug#90204: installation process unclear when network card not found

[David Whedon <dwhedon@gordian.com>]

I'd suggest an alternate approach.  Modifying dbootstrap to run on an already
installed system sounds like a lot of work. A package already exists that will
configure the ethernet via debconf:

ruff:davidw$ apt-cache show etherconf
Package: etherconf
Priority: optional
Section: net
Installed-Size: 28
Maintainer: John Goerzen <jgoerzen@progenylinux.com>
Architecture: all
Version: 1.0.0
Depends: debconf, ifupdown (>= 0.6.3-1.0progeny1), pump, libconfhelper-perl
Filename: dists/woody/main/binary-all/net/etherconf_1.0.0.deb
Size: 7700
MD5sum: 4a6cff14e500f93edd9d9dc412b75214
Description: debconf interface to Ethernet configuration
 This package provides a debconf-based interface to configuring the
 Ethernet on your system.  Currently, it will only configure one Ethernet
 device, but more support is planned in the future.

ruff:davidw$


Perhaps a pointer to that package would be appropriate?

David


> This should be quite simple: take the existing install routine, add an
> option to restart it from that point, put it in some directory on the hard
> drive during the install, and make simple mention of it in the installation
> document. I'm talking about one extra small script in the distribution
> - which should take about 5 minutes to prepare from what you've already got,
> and one very short line in the installation doc.
> 
> Then it would no longer be an 'unsupported' zone. In programming 90% of the
> work is always about the 10% of the instances that are exceptional - but in
> this case it would be so easy to cover the exception, why not?
> 
>  \/\/ I-I I T 
>  Blauvelt
>  whit@transpect.com
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-boot-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org