[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Proposal: Ask if user wants to set up network



Steve Langasek wrote:
On Thu, Jan 08, 2004 at 01:14:08PM -0600, Joel Konkle-Parker wrote:

Steve Langasek wrote:

On Thu, Jan 08, 2004 at 12:20:12PM -0600, Joel Konkle-Parker wrote:


I propose (if this isn't being worked on already) that d-i ask the user if he/she wants to set up his/her network connections during installation instead of assuming so. As can be seen in bug #226495 <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=226495>, problems ensue when this connection can't be established because of driver issues and such.


Ok, and if you're installing from a *net*inst CD (which is what the
current dailies are), what do you expect the system to do when it needs
to install more packages?


If you really only want the base system to be installed and nothing
else, you should be able to boot the CD in 'expert' mode, and avoid the
redundant prompting.   "base only with no access to full package
archives" sounds like an expert configuration to me, do you disagree?


What I've always done in the past is get a base system installed, install the .deb from LinuxAnt, copy the necessary files from /mnt/windows, set up WEP, ifup eth0, then do my tasksel/dselect/apt-get from there.


Is this possible from within d-i's mini-shell?


I believe that this is possible using d-i in expert mode (and what
you've described *definitely* sounds like an expert config to me now ;).
If you find that it isn't, let us know, as it's probably a bug.



Well, the problem here is that I don't think this /should/ be an expert config. I have a few-months-old Dell 5150 with an 802.11g wireless card that is only supported by LinuxAnt's commercial DriverLoader software using native Windows drivers.

With the current state of wireless net drivers, sure, maybe this low-level messing around is necessary, but this doesn't seem like a very far-fetched scenario to me (802.11g is getting more and more popular, as are wireless-only connections in apt. complexes and such).

I guess the only "bug" here is the general lack of a distributable Broadcom 802.11g chipset driver. The linux-bcom4301 SourceForge project is attempting it, but seems stalled at the moment.


--
Joel Konkle-Parker
Webmaster  [Ballsome.com]

E-mail     [jjk3@msstate.edu]
Phone      [662-518-1636]



Reply to: