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