| 1 |
On 05/12/2013 01:45, 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 |
> That extra step of whining was loud enough to have openrc fixed to be |
| 29 |
> able to use busybox udhcp, so that "out of the box" most network worked. |
| 30 |
> |
| 31 |
> ... and now people are trying to do the same again. |
| 32 |
> |
| 33 |
> I would STRONGLY recommend having a working network setup included in |
| 34 |
> stage3, so that compared to now nothing changes. |
| 35 |
|
| 36 |
|
| 37 |
In this day and age not having a network-capable install out the box is |
| 38 |
silly. The first major action after unpacking the tarball is going to be |
| 39 |
adding new packages and doing updates, the source code for which is on |
| 40 |
the network. |
| 41 |
|
| 42 |
Network is only slightly less necessary than disk drivers - almost |
| 43 |
everyone is going to need it. So just ship the thing that the majority |
| 44 |
will need, for the few that have a valid case to not need networking |
| 45 |
after install, it's a simple matter for them to disable it. |
| 46 |
|
| 47 |
The default install doesn't need to have a network provider with all the |
| 48 |
bells and whistles, netifrc is perfectly adequate (especially if dhcp is |
| 49 |
enabled as it always was for years) |
| 50 |
|
| 51 |
|
| 52 |
-- |
| 53 |
Alan McKinnon |
| 54 |
alan.mckinnon@×××××.com |
Archives