Gentoo Archives: gentoo-dev

From: Ian Stakenvicius <axs@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] openrc 0.12 - netifrc/newnet mix-up
Date: Fri, 06 Dec 2013 15:26:27
Message-Id: 52A1EC8F.3010505@gentoo.org
In Reply to: Re: [gentoo-dev] openrc 0.12 - netifrc/newnet mix-up by William Hubbs
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA256
3
4 On 04/12/13 08:56 PM, William Hubbs wrote:
5 > On Wed, Dec 04, 2013 at 07:17:45PM -0500, Mike Gilbert wrote:
6 >> On Wed, Dec 4, 2013 at 6:45 PM, Patrick Lauer
7 >> <patrick@g.o> wrote:
8 >>> On 12/05/2013 05:30 AM, Mike Gilbert wrote:
9 >>>> On Wed, Dec 4, 2013 at 4:25 PM, William Hubbs
10 >>>> <williamh@g.o> wrote:
11 >>>>> On Wed, Dec 04, 2013 at 06:46:36PM +0200, Samuli Suominen
12 >>>>> wrote:
13 >>>>>> seems like a virtual that wouldn't do anything useful
14 >>>>>> except pull in random package(s) a la binary-distribution
15 >>>>>> style
16 >>>>>
17 >>>>> What about the stages? Don't we need some form of net
18 >>>>> support in stage 3?
19 >>>>>
20 >>>>
21 >>>> That's debatable. For a typical install, the user has to
22 >>>> install other basic stuff like a boot loader, kernel, etc. So
23 >>>> having them also select a network config framework seems
24 >>>> logical.
25 >>>>
26 >>>> Is there a use case for a stage3 in which installing netifrc
27 >>>> by hand is impractical?
28 >>>>
29 >>> Well ...
30 >>>
31 >>> I remember filing a bug quite a while ago because we didn't
32 >>> have a dhcp client included anymore. This made installs quite
33 >>> annoying because before it was stage3, kernel, bootloader, go!
34 >>>
35 >>> And now it was go ... stop ... reboot ... install dhcp client
36 >>> ... grremblwrrxrmkrxtlmrrrg .... reboot
37 >>>
38 >>> That extra step of whining was loud enough to have openrc fixed
39 >>> to be able to use busybox udhcp, so that "out of the box" most
40 >>> network worked.
41 >>>
42 >>> ... and now people are trying to do the same again.
43 >>>
44 >>> I would STRONGLY recommend having a working network setup
45 >>> included in stage3, so that compared to now nothing changes.
46 >>>
47 >>>
48 >>
49 >> Yeah, after some further thought, I'm inclined to agree.
50 >
51 > I think we would be safe as long as we make sure to document in
52 > the handbook that users must choose a network manager. We could
53 > recommend netifrc by default for now until we can document how to
54 > set up the others.
55 >
56 > Once all of this hits stable I want to work with releng to get
57 > them to use standalone dhcpcd on the LiveCD.
58 >
59 > What do you think?
60
61 If the stage3 could include a dhcp client and (ideally imo) netifrc,
62 even though they aren't a part of @system, that would help prevent the
63 "stuff missing, damnit, have to reboot back to livecd" cycle. Since
64 it isn't part of @world we would still need the documentation and
65 instructions for someone to explicitly choose a network provider,
66 otherwise they'll be bitten with it disappearing via --depclean.
67
68
69
70 -----BEGIN PGP SIGNATURE-----
71 Version: GnuPG v2.0.22 (GNU/Linux)
72
73 iF4EAREIAAYFAlKh7I8ACgkQ2ugaI38ACPBeDgD9GV+Mk4mbHLRRzqAfXfqei5Ci
74 JRLuN0I1e1nW08DT93oA/0FlNasD9KlGNCUwG6JrJhuEQs2H8Damau7KsWO2GibN
75 =500q
76 -----END PGP SIGNATURE-----

Replies

Subject Author
Re: [gentoo-dev] openrc 0.12 - netifrc/newnet mix-up Ben Kohler <bkohler@×××××.com>