On Tue, Jul 23, 2013 at 6:52 PM, Billy Crook <billycrook(a)gmail.com> wrote:
On Tue, Jul 23, 2013 at 10:51 AM, Matthew Miller
<mattdm(a)fedoraproject.org> wrote:
> On Tue, Jul 23, 2013 at 10:18:47AM -0500, Billy Crook wrote:
>> > Since it _isn't_ served via DHCP in any environment I'm aware of,
that's not
>> > actually useful.
>> Nice to meet you Matt. As of this morning, it is served via DHCP in
>> mine. There's also that guy earlier in the thread. So now you know
>> of two. Perhaps that dhcp option ought to be in the packaged
>> dhcpd.conf template.
>
> You've totally removed the context here. Which cloud environment do you run?
Actually I'm afraid your cloud environment example is just as far out
of context. I can't imagine many cloud deployments that don't use
kickstarts and have their own individually chosen packageset tuned for
exactly their business case. They can use core / minimal + whatever
specific individual packages they need. I hardly think a cloud
environment is going to base their production on the Default package
set.
Default should include what people 'generally expect of a GNU+Linux
system' -- and that includes an MTA.
Citation needed. Given that one very distribution with a very big
userbase don't install an MTA by default ...