Christian Betz <[EMAIL PROTECTED]> writes:

> 1) the hardware detection need to be extended to USB and PCMCIA
> devices

Maybe not PCMCIA, since we already invoke cardmgr at startup to handle
PCMCIA network adapters.

Don't most of the CardBus adapters just show up as PCI devices anyway?

For USB, yeah, it will take more work.  A "find-modules-usb" script
along the lines of "find-modules-pci" might be nice.

> 2) iwconfig and related utils need to be put on the disk, and more
> importantly -- the disk needs to be built to site specific ESSID/WEP
> parameters (or else it will have to ask about them in the master
> script)

Probably the best approach is to ask if a wireless device is being
used, otherwise try to pick a default (like bind to the first wireless
network you can find, no WEP).  Then add "z_..." boot-time options to
override the defaults.

I will look into adding the iw* suite of tools for our next release.

> 3) we need an an easy way to add 3rd party modules --- many wireless
> cards have their own drivers independent of the kernel.

Yup.  Although we should encourage those authors to merge their work
into the mainline :-).

It would probably be easiest to get this working first with a card
already supported by the stock kernel.

> What else?

I am kind of curious what happens after the machine reboots and the
main Windows installation begins.  Will we be able to set wireless
parameters from unattend.txt?  If not, we may have to re-arrange our
post-install procedure not to need a network connection on first boot.
This means not only configuring the wireless itself, but deferring
things like joining the domain.  This would definitely take some work.

I would like to help with this, but I lack the hardware.  In
particular, I have no laptop which can boot from USB, which I consider
a prerequisite for this sort of development.  I have no desire to turn
a bazillion CD-ROMs into coasters.

Shad began working on this already, by the way.  I believe he is
stalled waiting for me to fix our build issues on Fedora Core 2...
Which I hope to get sorted out this evening.

 - Pat


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
unattended-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-devel

Reply via email to