| 1 |
On Mon, Mar 25, 2013 at 8:49 AM, Tobias Klausmann <klausman@g.o> wrote: |
| 2 |
> Thing is that SRCD does a lot more things than our mini ISO does. |
| 3 |
> As a result, keeping it going on half a dozen architectures is |
| 4 |
> more work than maintaining our arguably very simple images. There |
| 5 |
> is a reason why we abandoned making the "fat" install images a |
| 6 |
> while back and now only do them as one-offs for special events |
| 7 |
> (like the 10y anniversary). |
| 8 |
|
| 9 |
Tend to agree. To install Gentoo you really just need a shell, the |
| 10 |
ability to partition and create filesystems, some basic networking |
| 11 |
(even that is somewhat optional), and a text editor. Sure, a browser |
| 12 |
and such is a real nice-to-have, as would be something nicer than |
| 13 |
nano, but you really don't need them to install Gentoo. |
| 14 |
|
| 15 |
You really don't need much more than a kernel and busybox to be honest. |
| 16 |
|
| 17 |
There is no reason that we have to use the same install media on all |
| 18 |
arch's, though it does simplify the docs. It also isn't that |
| 19 |
important to update the install media so quickly. If we just kept an |
| 20 |
archive of our old autobuilds when they break we could just leave the |
| 21 |
last known good copy up until things are straightened out. |
| 22 |
|
| 23 |
I'd put more priority on up-to-date stage3s. It is a real pain if |
| 24 |
you're doing an install and the first thing you're doing is updating |
| 25 |
udev and migrating to kmod, or whatever and having to deal with |
| 26 |
eselect news. Users should at least get to use the system for 5 |
| 27 |
minutes before dealing with that stuff, especially if a few big |
| 28 |
changes have queued up... |
| 29 |
|
| 30 |
Rich |
Archives