Bug#90204: marked as done (installation process unclear when network card not found)
Your message dated 26 Mar 2001 14:04:15 -0500
with message-id <oaelvk1he8.fsf@arroz.fake>
and subject line Bug#90204: installation process unclear when network card not found
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 19 Mar 2001 05:09:08 +0000
>From whit@transpect.com Sun Mar 18 23:09:08 2001
Return-path: <whit@transpect.com>
Received: from china.patternbook.com (transpect.com) [216.254.75.60]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14erum-0005s1-00; Sun, 18 Mar 2001 23:09:08 -0600
Received: (from root@localhost)
by transpect.com (8.9.3/8.8.7) id AAA00697
for submit@bugs.debian.org; Mon, 19 Mar 2001 00:08:59 -0500
Date: Mon, 19 Mar 2001 00:08:59 -0500
From: Whit <whit@transpect.com>
To: submit@bugs.debian.org
Subject: installation process unclear when network card not found
Message-ID: <[🔎] 20010319000859.A608@www.transpect.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Delivered-To: submit@bugs.debian.org
Package: boot-floppies
Version: 2.2.17
Using the vanilla installation, it didn't have my network card (3c905), so
it didn't offer the network setup options on installation. Since the system
is already running Red Hat, I compiled a fresh 2.2.19pre kernel and set a
Debian lilo option. Booting into Debian with it I looked around with the
question "Okay, what's the efficient Debian way to set up the network
options?" If there's a clue I can't find it. (On Red Hat this is the one
thing I usually use linuxconf for - after carefully disabling all its other
buggy functions - glad to see that shoddy utility's not in your base
install.)
There should also be an obvious way to go back to a bypassed network setup
once a proper kernel or module is in place. This should be mentioned in the
installation manual, or at the least the manual should reference whatever
the most convenient included utilities are that can be used in place of
various stages of the 'straightforward' process when things go deviant.
Why not have an option to go ahead and set up the networking options on the
first pass _even if the network card isn't recognized yet_? Does the user
really need to be protected from the possibility of doing this? Software
that tries to out think the user by removing options is often too clever by
half. The useful thing would be "If you have a NIC, I can't see it yet.
Would you like to make the network settings anyway?"
What I'm primarily asking for is an installation process and instructions
that make allowance for users who will compile their own kernels. Maybe
another of your kernels has 3c905 support - if I wanted to back out and
repeat everything I've done so far to get back on track that way, which I
don't - but there will always be hardware that no distro kernel will be
right for, and just 'cause someone wants to do the kernel 'the hard way'
shouldn't obligate them to forego modern conveniences in other stages of the
process.
I've found "dpkg-reconfigure base-config", which looks like it will complete
at least part of the installation once I have the network settings in place.
It should be simple to just copy them across from the Red Hat installation
...
\/\/ I-I I T
Blauvelt
whit@transpect.com
---------------------------------------
Received: (at 90204-done) by bugs.debian.org; 26 Mar 2001 19:03:59 +0000
>From adam@onshore.com Mon Mar 26 13:03:59 2001
Return-path: <adam@onshore.com>
Received: from dsl106.dsl.bway.net (arroz.fake) [216.220.104.106]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14hcHX-0004So-00; Mon, 26 Mar 2001 13:03:59 -0600
Received: from arroz.fake (localhost [127.0.0.1])
by arroz.fake (Postfix) with ESMTP
id 58B2A93807; Mon, 26 Mar 2001 14:04:15 -0500 (EST)
Sender: apharris@burrito.onshore.com
To: Whit <whit@transpect.com>
Cc: 90204-done@bugs.debian.org
Subject: Re: Bug#90204: installation process unclear when network card not found
References: <[🔎] 20010319000859.A608@www.transpect.com>
<[🔎] oa3dc64k9m.fsf@arroz.fake> <[🔎] 20010322121558.E1016@www.transpect.com>
<[🔎] oaitky8sp2.fsf@arroz.fake> <[🔎] 20010326135628.Y1819@www.transpect.com>
From: Adam Di Carlo <adam@onshore.com>
Date: 26 Mar 2001 14:04:15 -0500
In-Reply-To: <[🔎] 20010326135628.Y1819@www.transpect.com>
Message-ID: <oaelvk1he8.fsf@arroz.fake>
Lines: 29
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: 90204-done@bugs.debian.org
Whit <whit@transpect.com> writes:
> I'm not suggesting you add information on replacing the kernel. I'm
> suggesting that you provide an option to run the remainder of the
> installation routine in order to set up networking and such (which currently
> does not run at all if the NIC is not supported by the kernel) after
> whatever steps (for instance compiling a custom module to support the NIC)
> the user may have taken. I can tell you from experience that there was a
> period of some months just a year ago where no stock kernel supported
> several recent models of the popular 3com 3c905 cards (which are the
> standard for high-end servers), and it was necessary to install a custom
> patch to get them working. Such instances are likely to happen again.
>
> 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.
No, I'm sorry, that's not going to happen. Better to use the
etherconf package or something after install. I will *not* be putting
dbootstrap on the disk after installation and support users running
that.
Closing this bug.
--
.....Adam Di Carlo....adam@onshore.com.....<URL:http://www.onshored.com/>
Reply to: