18:30]<ethiksgradient> He tries to update across the network having decided to not bother to configure a network. This doesn't work, and he gets annoyed.
the install could not find a nic card, so how does installing via the network work if it cannot find a nic card to configure a network on?
]<ethiksgradient> The apt config file is empty because he skipped configuring it.I didnt skip configuring it, it REFUSED TO CONFIGURE WHAT I WANTED BECAUSE IT COULD NOR FIND A NETWORK CARD!!!!
[18:31]<ethiksgradient> In short, the debian installer did everything he told it to.
The apt-get config file is empty because it refused to allow any selection that involved a network because the installer could not find a nic card
<ethiksgradient> Yes. Skipping steps means that the tasks done in those steps are not done. I'm not sure how the d-i team are supposed to get around this short of building clairvoyance into the system.The DI team doesnt need clairvoyance it needs common sense. Allowing apt-get to be configured FOR a network should not be disallowed because of LACK of connectivity. Unlike some to me the network really is the computer, any machine should be net available by some method or another sooner or later. Any service should install as requested and bitch about not having a network ONLY when someone tries to run it WITHOUT a network.
example, I can install an ftp client on a machine without a nic. It will install just fine. Only when I attempt to reach a network without a net connection will I get an error. After I install a network it will work just fine. Having the ftp check for connectivity PRIOR to installation then refusing to install because of LACK of a network is fuckneetery.
regards,
daemon