what is suppose to work?

[Gene Czarcinski]

On 12/09/2012 02:55 PM, Gene Czarcinski wrote:
> On 12/09/2012 11:48 AM, Gene Czarcinski wrote:
>> I have been trying different things with respect to installing 
>> F18-beta x86_64 using both the DVD and the livcd-desktop images. One 
>> problem I am having is trying to figure out what is suppose to work 
>> and what is not.  This primarily concerns storage configuration but 
>> there is more (see below).  I am doing this testing on both a real 
>> hardware system and using qemu/kvm virtual systems.
>>
>> More recently (today), I created an F18-beta livecd based on what is 
>> in updates-testing, etc.
>>
>> 1.  So far, letting things default and let anaconda do all of the 
>> configuration works.
>>
>> 2.  Reusing predefined regular partitions for /boot and swap work.
>>
>> 3.  Using my newly created F18-beta-livecd, I attempted to install 
>> into a predefined LV .. this worked BUT /boot/grub2/grub.cfg did not 
>> exist and grub2 was not installed into /dev/vda ... manually fixed it 
>> from rescue.  This appears to be a step back since the regular livecd 
>> worked with respect to grub2.
>>
>> 4. I have had zero success with the F18-beta DVD in using predefined 
>> btrfs subvolumes.  Yes, it does display them but when I press 
>> "apply", the mount point value of "/" is cleared and nothing else 
>> happens.
>>
>> 5.  With my newly created F18-beta-livecd, I had exactly the same 
>> experience as above.  However, this time I deleted the two btrfs 
>> subvolumes I had defined and the btrfs partition.  I then reallocated 
>> a newbtrfs and that worked.  BUT, again, grub2 was not installed and 
>> there was no grub.cfg
>>
>> 6.  One general thing I find missing is to control where (on what 
>> device) a partition is allocated.  This is a problem! Although  I was 
>> able to allocate the btrfs, My intent was that it be on one volume 
>> but in someones infinite wisdom it was on two.  Is there any effort 
>> in this area?
>>
>> Have such tests been conducted successfully by F18 QC?
>>
>> This is getting a bit frustrating!
>>
>> I would say that I could consider using fedup instead but doing 
>> upgrades has their own set of problems and not installing new 
>> packages that would be in a fresh install.  My next step is to see if 
>> I can use kickstart to configure things "my way."
>>
> One or two other things trouble me.  If you have a system with 
> multiple predefined btrfs and LVM pools, how do you specify which pool 
> to use for new allocations ... and of course for predefined LVs or 
> subvolumes in the case of btrfs.  In fact, I do not understand how to 
> specify that another subvolume is to be added to a btrfs pool.
And now another question:  Is kickstart suppose to work for fedora 18.  
Using the F18-beta netinstall image, specifying 
ks=http://<servername>/<path-to-ks.cfg>, it seemed to just ignore it.  I 
had previously used the same ks.cfg file to install a F17 system.

Gene