[@core] working definition for the minimal package set

[Chris Adams]

Once upon a time, Bill Nottingham <notting at redhat.com> said:
> So, what it is bascially designed for now is:
> 
> - Boot to a normal prompt
>       basesystem
>       bash
>       coreutils
>       filesystem
>       glibc
>       initscripts
>       plymouth (was for boot logs & encrypted partitions; could be dropped)
>       rootfiles
>       setup
>       systemd
>       util-linux
>       (plus implicit kernel)

Plus a bootloader, which may be implicit (and I guess isn't absolutely
required for at least some virtualization setups).

What makes rootfiles essential?  That's just overriding the defaults
from /etc/skel with annoying aliases.

> - Support basic networking
>       biosdevname (consistent naming policy)
>       initscripts
>       dhclient
>       hostname
>       iproute
>       iputils
>       NetworkManager

Is NM really required for "basic" networking?  If so, you probably don't
need to specify some of the rest (such as dhclient) manually.  NM brings
a bunch of deps I believe.

Also, I'd include ethtool, since you need it to configure NICs (although
it may be pulled in as a dep).  IIRC it got dropped from a default
install for one release (and that was annoying for me anyway).

> - Configure additional partitions for the simple case
>       e2fsprogs
>       parted

LVM?  I know it is a can of worms, but it has been the default for a
long time now.

-- 
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.