On Thu, Sep 24, 2015 at 9:43 PM, Nico Kadel-Garcia <[log in to unmask]> wrote:
> On Thu, Sep 24, 2015 at 1:55 PM, Tom H <[log in to unmask]> wrote:
>> On Thu, Sep 24, 2015 at 9:13 AM, Nico Kadel-Garcia <[log in to unmask]> wrote:


>>> The difficulty is that anaconda has become a python nightmare of
>>> complexity, coupled with an unnecessary GUI of complexity. New
>>> features of sophisticated interaction and "pretty pictures" ti nabage
>
> Lordie, did I actually type that???? I I meant "to manage".

I assumed that your right hand was shifted to the left by one key. LOL


>>> LVM, various clustering filesystems, and network installation have
>>> been added as desired, but it's easy to lose site of simple steps like
>>> "just present the names of disks.
>>
>> python isn't the problem; the hub and spoke "concept" is. Ubuntu's
>> Ubiquity is the best GUI installer.
>>
>> Ubiquity can't set up mdraid like Anaconda, but it handles btrfs
>> better than Anaconda.
>>
>> Anaconda's partitioning spoke's so horrendous that I only use
>> kickstart or "yum --installroot=... ..." - or unpack a tarball created
>> with one of those methods.
>
> Unfortunately, the "system-config-kickstart" tool is also horrible. It
> rewrites any base kickstart in its own format, quite orthogonal to the
> original and to the "anaconda-ks.cfg" file generated at install time,
> and it can only deal with one '%post" stanza though kickstart supports
> multiple stanzas.

I've never used "system-config-kickstart" but it's always good to run
"ksverdiff -f old-ver -t new-ver" when a new version of SL's published
to find out what's new and what's deprecated in kickstart.