"kk1" <[EMAIL PROTECTED]> writes:
[...]
> >> 2. This different card is a PC-card 3c575_cb, ID 10b75167, but is
> >> detected by harddrake as 3c59x. I will send a separate email to
> >> harddrake about that, but that prevents any net install with this card.
> >
> >Do you talk during install or after install? You talk about harddrake
> >(which is not present during install) and then that you can't perform net
> >install. Please could you give more information?
> >
> There is surely some sort of detection during the install because it seems
> to fail at the second stage (like it was before with the 3c509). The log
> have the 'disconnecting life support' and the system sits there not doing
> anything more.
This means it fails just in-between the stage1 and stage2.
1- do you have any other relevant things in console #1 and console #4?
2- could you try with another install method? (cdrom-hd-nfs-ftp-http)
3- could you try with an alternate image file (/images/alternatives)?
> >> 7. Why is drakgw installing a dhcp server without asking me if that's
> how I
> >> thought that this was now obsolete w/ kernel 2.4.
> >
> >There is nothing to do with 2.4 and obsoleting a dhcp server.
> >
> >The tool `drakgw' is mostly targetted to newbies, and it's far more easy
> >to tell them that they need not to specify any parameter for their client
> >machines, using a dhcp server for local network.
> >
> >Basically, if you're more of an expert, you should avoid using drakgw.
> >
> Part of what I meant has been chewed up here (or maybe I just forgot to
> type it :). My questions were why is dragw installing dhcp (got the answer)
> and why ipchains, which I thought was now obsolete (above all when I
> already had iptables installed).
It installs both ipchains and iptables, so that whenever you'll possibly
reboot with a 2.2 kernel, your gatewaying will still work like a charm,
that's it :-).
--
Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
