Am 29.03.2012 09:00, schrieb Paul Howarth:
On Wed, 28 Mar 2012 22:16:25 +0200
Reindl Harald <h.reindl(a)thelounge.net> wrote:
> maybe the tone was minimal rude because i do absolutely
> not understand why anyone can have the idea "hey let us
> remove the whole custom partitioning and replace with
> kickstart only" to solve problems with it
That's not what I understood from Adam's description, which was:
> It's worth bearing in mind there's a giant anaconda UI rewrite still
> pending, which entirely redesigns the storage configuration GUI. One
> of the other major changes is that it makes all installations
> kickstart-driven. The GUI will just produce a kickstart file, which
> anaconda will then process to perform the actual install.
see the mail below
yes, i confused Adam and Richard because both @redhat.com
and both spoke about Kickstart, and this message
below is as clear as it can be and matches 100% to my
answer - my reply to the wrong person was the result
of reply not instantly and try to wait what happens
-------- Original-Nachricht --------
Betreff: Re: Booting Fedora from LVM with grub2
Datum: Sun, 25 Mar 2012 09:32:02 +0100
Von: Richard W.M. Jones <rjones(a)redhat.com>
Antwort an: Development discussions related to Fedora
<devel(a)lists.fedoraproject.org>
An: Development discussions related to Fedora <devel(a)lists.fedoraproject.org>
On Fri, Mar 23, 2012 at 12:08:42PM -0400, Gerry Reno wrote:
You can do all of these things manually outside of anaconda and then
just tell anaconda to use existing setup. But that is not very user
friendly.
I had similar problems trying to set up a basic RAID 1 (not /boot)
guest. I found Anaconda is full of bugs and wierdness once you stray
into the custom partitioning code.
Apparently kickstart is a better way to do this.
Perhaps, like Ubuntu's installer, the graphical part of Anaconda
should concentrate on doing the simple stuff, and leave everything
else to kickstart non-graphical installations.