1 |
On 12/05/2013 08:13 AM, William Hubbs wrote: |
2 |
> On Thu, Dec 05, 2013 at 07:45:22AM +0800, Patrick Lauer wrote: |
3 |
>> On 12/05/2013 05:30 AM, Mike Gilbert wrote: |
4 |
>>> On Wed, Dec 4, 2013 at 4:25 PM, William Hubbs <williamh@g.o> wrote: |
5 |
>>>> On Wed, Dec 04, 2013 at 06:46:36PM +0200, Samuli Suominen wrote: |
6 |
>>>>> seems like a virtual that wouldn't do anything useful except pull in |
7 |
>>>>> random package(s) a la binary-distribution style |
8 |
>>>> |
9 |
>>>> What about the stages? Don't we need some form of net support in |
10 |
>>>> stage 3? |
11 |
>>>> |
12 |
>>> |
13 |
>>> That's debatable. For a typical install, the user has to install other |
14 |
>>> basic stuff like a boot loader, kernel, etc. So having them also |
15 |
>>> select a network config framework seems logical. |
16 |
>>> |
17 |
>>> Is there a use case for a stage3 in which installing netifrc by hand |
18 |
>>> is impractical? |
19 |
>>> |
20 |
>> Well ... |
21 |
>> |
22 |
>> I remember filing a bug quite a while ago because we didn't have a dhcp |
23 |
>> client included anymore. This made installs quite annoying because |
24 |
>> before it was stage3, kernel, bootloader, go! |
25 |
>> |
26 |
>> And now it was go ... stop ... reboot ... install dhcp client ... |
27 |
>> grremblwrrxrmkrxtlmrrrg .... reboot |
28 |
> |
29 |
> Are you sure this was caused by an issue in the stages? The description |
30 |
> you are giving sounds like an issue with the LiveCD. |
31 |
> |
32 |
> William |
33 |
> |
34 |
Yes ... change must have been ~2006 |
35 |
|
36 |
Result: No dhcp client in stage3 (thanks Wolf31o2) |
37 |
|
38 |
And it took a long time to be properly fixed |