From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] openrc 0.12 - netifrc/newnet mix-up
Date: Wed, 4 Dec 2013 16:30:30 -0500 [thread overview]
Message-ID: <CAJ0EP40tcMaDrjZMdyvUmpzgX8jTufOfXzvbc5QvMRnuN3nTjg@mail.gmail.com> (raw)
In-Reply-To: <20131204212537.GA19609@linux1>
On Wed, Dec 4, 2013 at 4:25 PM, William Hubbs <williamh@gentoo.org> wrote:
> On Wed, Dec 04, 2013 at 06:46:36PM +0200, Samuli Suominen wrote:
>> seems like a virtual that wouldn't do anything useful except pull in
>> random package(s) a la binary-distribution style
>
> What about the stages? Don't we need some form of net support in
> stage 3?
>
That's debatable. For a typical install, the user has to install other
basic stuff like a boot loader, kernel, etc. So having them also
select a network config framework seems logical.
Is there a use case for a stage3 in which installing netifrc by hand
is impractical?
next prev parent reply other threads:[~2013-12-04 21:30 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 10:20 [gentoo-dev] openrc 0.12 - netifrc/newnet mix-up Alessandro DE LAURENZIS
2013-12-01 10:36 ` Alexander V Vershilov
2013-12-02 20:28 ` William Hubbs
2013-12-02 21:19 ` Rick "Zero_Chaos" Farina
2013-12-02 21:24 ` Ian Stakenvicius
2013-12-03 17:32 ` Alexander V Vershilov
2013-12-03 21:11 ` William Hubbs
2013-12-03 21:43 ` Ian Stakenvicius
2013-12-03 23:00 ` William Hubbs
2013-12-03 23:29 ` Ian Stakenvicius
2013-12-04 1:14 ` mingdao
2013-12-04 15:57 ` William Hubbs
2013-12-04 16:46 ` Samuli Suominen
2013-12-04 21:25 ` William Hubbs
2013-12-04 21:30 ` Mike Gilbert [this message]
2013-12-04 22:31 ` William Hubbs
2013-12-04 22:36 ` Mike Gilbert
2013-12-04 23:42 ` William Hubbs
2013-12-05 17:03 ` Samuli Suominen
2013-12-05 8:01 ` Martin Gysel
2013-12-05 9:23 ` Steev Klimaszewski
2013-12-04 23:45 ` Patrick Lauer
2013-12-05 0:13 ` William Hubbs
2013-12-05 0:20 ` Patrick Lauer
2013-12-05 0:17 ` Mike Gilbert
2013-12-05 1:56 ` William Hubbs
2013-12-06 15:26 ` Ian Stakenvicius
2013-12-06 15:38 ` Ben Kohler
2013-12-05 7:39 ` Alan McKinnon
2013-12-05 12:30 ` Rich Freeman
2013-12-05 17:01 ` Samuli Suominen
2013-12-07 5:52 ` Rick "Zero_Chaos" Farina
2013-12-07 12:42 ` Rich Freeman
2013-12-07 14:22 ` Rick "Zero_Chaos" Farina
2013-12-07 23:25 ` Rich Freeman
2013-12-08 2:34 ` Peter Stuge
2013-12-08 22:31 ` William Hubbs
2013-12-14 6:22 ` Jorge Manuel B. S. Vicetto
2013-12-14 17:18 ` Jeroen Roovers
2013-12-07 15:04 ` Peter Stuge
2013-12-08 22:25 ` William Hubbs
2013-12-09 14:50 ` Rick "Zero_Chaos" Farina
2013-12-09 15:28 ` Rich Freeman
2013-12-09 18:47 ` Steev Klimaszewski
2013-12-09 19:56 ` Rick "Zero_Chaos" Farina
2013-12-10 1:33 ` Rich Freeman
2013-12-10 10:31 ` Steev Klimaszewski
2013-12-10 11:23 ` Rich Freeman
2013-12-10 18:46 ` Steev Klimaszewski
2013-12-11 17:51 ` [gentoo-dev] " Steven J. Long
2013-12-16 22:33 ` [gentoo-dev] " Rick "Zero_Chaos" Farina
2013-12-11 2:57 ` William Hubbs
2013-12-14 5:56 ` Jorge Manuel B. S. Vicetto
2013-12-14 20:13 ` William Hubbs
2013-12-14 20:47 ` Jorge Manuel B. S. Vicetto
2013-12-14 21:57 ` William Hubbs
2013-12-14 22:22 ` Luis Ressel
2013-12-16 22:38 ` Rick "Zero_Chaos" Farina
2013-12-14 17:24 ` mingdao
2013-12-15 0:59 ` William Hubbs
2013-12-15 1:37 ` mingdao
2013-12-16 22:41 ` Rick "Zero_Chaos" Farina
2013-12-09 23:30 ` Patrick Lauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ0EP40tcMaDrjZMdyvUmpzgX8jTufOfXzvbc5QvMRnuN3nTjg@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox