| 1 |
On Wed, Apr 24, 2013 at 02:16:51PM -0400, Rich Freeman wrote |
| 2 |
|
| 3 |
> Considering our default configuration ships sshd (an argument we don't |
| 4 |
> need to rehash here), it seems a bit silly to not ship networking |
| 5 |
> support by default. I'd rather not do it as part of the system set, |
| 6 |
> though that would be consistent with what we're doing with ssh, and it |
| 7 |
> is still override-able. |
| 8 |
|
| 9 |
We're talking two different items here... |
| 10 |
1) Necessary functionality for the minimal-install ISO to work |
| 11 |
2) The installed software on a running system |
| 12 |
|
| 13 |
Item 1) is constrained by the real world... do what you have to do to |
| 14 |
create a functional install ISO |
| 15 |
|
| 16 |
Item 2) will be due to customizations done by admins for their |
| 17 |
specific needs. There's no way to predict how Joe Admin is going to |
| 18 |
integrate the various available software services. |
| 19 |
|
| 20 |
To handle the various possible cases, maybe we need a "virtual/net" as |
| 21 |
part of the system set, which can be satisfied by either oldnet or |
| 22 |
newnet or whatever. The install ISO will have a basic working network |
| 23 |
stack (IPV4+IPV6). After the initial install, the admin can do |
| 24 |
whatever. Maybe even invoke package.provided. |
| 25 |
|
| 26 |
-- |
| 27 |
Walter Dnes <waltdnes@××××××××.org> |
| 28 |
I don't run "desktop environments"; I run useful applications |
Archives