| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 12/10/2013 01:46 PM, Steev Klimaszewski wrote: |
| 5 |
> On Tue, 2013-12-10 at 06:23 -0500, Rich Freeman wrote: |
| 6 |
>> On Tue, Dec 10, 2013 at 5:31 AM, Steev Klimaszewski <steev@g.o> wrote: |
| 7 |
>>> On Mon, 2013-12-09 at 20:33 -0500, Rich Freeman wrote: |
| 8 |
>>> You're thinking with your x86/amd64 hat on here. |
| 9 |
>> |
| 10 |
>> Actually, I probably just underquoted. I am well-aware that there are |
| 11 |
>> issues with ARM, hence my previous suggestion that it might make sense |
| 12 |
>> to vary this by profile. |
| 13 |
>> |
| 14 |
> |
| 15 |
> Definitely - but then we have to do everything in the profiles, and at |
| 16 |
> least for ARM, there are currently 6 profiles, and we're considering |
| 17 |
> introducing a 7th (neon), and we will need to add aarch64, which will be |
| 18 |
> at least 2 more. I suppose we could do it in the base arm profile... |
| 19 |
> |
| 20 |
>> Let me try my post again, with a bit more quoting: |
| 21 |
>> |
| 22 |
>> On Mon, Dec 9, 2013 at 2:56 PM, Rick "Zero_Chaos" Farina |
| 23 |
>> <zerochaos@g.o> wrote: |
| 24 |
>>> What if he wants to |
| 25 |
>>> put a stage3 on a disk for his amd64 box from his arm box? I'd love to |
| 26 |
>>> see him emulate an amd64 from his arm to install dhcpcd. |
| 27 |
>> ... |
| 28 |
>>> I really don't like the idea of having no networking in the stage3 by |
| 29 |
>>> default, however, I'm becoming more open minded on what qualifies as |
| 30 |
>>> networking. What I'm wrestling with is this, what if I want to slap a |
| 31 |
>>> stage3 on a device and then access it from the network? |
| 32 |
>>> Almost nothing |
| 33 |
>>> in my place has a monitor (amd64 and arm alike) and I use one of my two |
| 34 |
>>> laptops to talk to everything else. |
| 35 |
>> |
| 36 |
>> Hit your head on the wall because it doesn't contain a kernel? |
| 37 |
>> Stage3s in general aren't functional systems. |
| 38 |
>> |
| 39 |
>> Insofar as much as he was talking about ARM I get the point. Insofar |
| 40 |
>> as he is taking about amd64, not so much. Which he was talking about |
| 41 |
>> in that paragraph I can only guess at. |
| 42 |
>> |
| 43 |
>> But as I later said in the same email: |
| 44 |
>> |
| 45 |
>> If it actually had collisions with other network managers I think |
| 46 |
>> there would be more of a case for removing it. |
| 47 |
>> |
| 48 |
>> After all, we stick openrc and portage (the PM) in the stage3 and you |
| 49 |
>> don't exactly need those in order to run Gentoo... |
| 50 |
>> |
| 51 |
>> Rich |
| 52 |
>> |
| 53 |
> While you don't need those specifically to run Gentoo, the point of the |
| 54 |
> stage3 is to have a workable base to start with. So people are very |
| 55 |
> much free to yank out openrc and put in, say, systemd, and rip out |
| 56 |
> portage and add in paludis, if they so choose, and make those available. |
| 57 |
> And from the traffic I've seen on the systemd list, it looks like they |
| 58 |
> are adding some sort of networking to systemd itself as well, so we |
| 59 |
> probably will need a virtual at some point. My specific point of the |
| 60 |
> email though, was you saying that a stage3 in general aren't functional |
| 61 |
> - but they are - they are the very base of a functional system, and you |
| 62 |
> simply add things on top, or replace things with your preferred methods. |
| 63 |
> A stage1 or a stage2 isn't particularly functional. |
| 64 |
> |
| 65 |
|
| 66 |
To be exact here, stage2 IS what is needed to bootstrap. stage3 is what |
| 67 |
is needed to have a semi-functional system. If everyone wants a |
| 68 |
*MINIMAL* tarball to start from I'm sure releng can put the stage2's |
| 69 |
onto the mirror so that people will leave my functional stage3 along and |
| 70 |
quit saying what they don't need. |
| 71 |
|
| 72 |
If you want nothing which isn't needed past the bootstrapping of the |
| 73 |
toolchain then stage2 is what you want. |
| 74 |
|
| 75 |
- -Zero |
| 76 |
-----BEGIN PGP SIGNATURE----- |
| 77 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 78 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 79 |
|
| 80 |
iQIcBAEBAgAGBQJSr3/KAAoJEKXdFCfdEflKWNkQAK0vLGjGN96EUimf8kXQxNYJ |
| 81 |
GSA9lOIGbdoaf0oG1917m56/4RoZfWJ4SH+5ylajIf0wBrZB+mrL+740msnq+XNz |
| 82 |
xUpFZjB/cliYprv5WxpH+HjsvD8/vOvDZ97nj4IfPwoT33ntu4aTeHbKQ9uCNkA4 |
| 83 |
FD/LJ+lZliPOIaeji0Gzmnp/B16s09W+Aa1F5gZ7TNCnNA3uchQPAZarT4BmThQB |
| 84 |
H88/Vo7s5SxfBTTuSv54lLdFPesTz65jTzBPIA35nggrCZHiCrc73zQ+gfiMDUuK |
| 85 |
q9eyA1MkvjX7NNdgL4hSFARUw+wYiq2mCaBc+rbG8x5xATR4P+U/NU9kU/ZbfcUQ |
| 86 |
tVUIQ6txuGhD3vyvxUYN4mWmuRyl9s9z9sUvVmGD7JRt9lCioLwN/IDz0CQpCVtD |
| 87 |
L+e68xrfcNR1vsc9isfo1wV5y9eVgenO8etq7xxQinXW8iEkSyPSablKcTrIRh3f |
| 88 |
U5b67wkikXP/Fhtvha6XGr/PYGCK2KTxc+Vo0a2r6aenJSk9WVDKlBcmIt92MKYh |
| 89 |
CZvzz1rNgtrbSvwY8f4YxXo4XGIUUYeQbj+DksCfVPaYXjvb75rC/axuYSMyGM+D |
| 90 |
5WFDUoGdSOrXAI4hgvDLSp8aQvJ1mRq/8Uw7iR+KTxAEYXaIW3NFRhRGaz4iSe2I |
| 91 |
Amni8AvCnKWaEt5w57Ox |
| 92 |
=RxMv |
| 93 |
-----END PGP SIGNATURE----- |
Archives