Re: what is suppose to work?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Read on, there is some good news also.

On 12/10/2012 11:51 AM, David Lehman wrote:
On Sun, 2012-12-09 at 11:48 -0500, Gene Czarcinski wrote:

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.
At what point are you checking and finding no bootloader setup?
The installer has completed and I am back in the "livecd system". The first time I did this, I rebooted and the system went off into never-never land. I rebooted into rescue, saw that there was no /boot/grub2/grub.cfg and concluded that grub2 was not installed. chroot; ran grub2-mkconfig -o /boot/grub2/grub.cfg; then ran grub2-install /dev/vda; and reboot. This time it worked.

Thereafter, I looked to see if there was a grub.cfg and if not, did the chroot, etc. under the "livecd system".

This was with my newly created (Dec 9th) livecd-desktop.

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.
At this point you should try clicking on the "New Fedora 18..." expander
on the left-hand side. Is your mountpoint showing up under there?
I have been doing some testing with kickstart and am learning a bit more about the ins and outs of btrfs

First of all, before I get to btrfs, there is LVM with kickstart. I believe that I can do installs and re-use predefined LVs. I can definitely do it with kickstart and using kickstart or fedup may be the way to go for some folks.

First, I made sure that my kickstart file worked with F17. Then with a little tweaking of the kickstart file AND learning that while ks=<xxx> worked for F17, it had to be inst.ks=<xxx> for F18.

I am still puzzled about one aspect of the F18 gui storage configurator. If you have more than one volume group and if the LV names are the same in different groups, how do you know where things will go or exactly which LV you are using? I intend to experiment more with this.

Back to btrfs. As with LVM, if you have multiple btfs storage pools, how do you specify which pool in the gui (it is doable in kickstart). This is a real example. I currently use some SSDs for root and home with a separate VG just for the SSD. My intent is to change over to using btrfs.

As I see it, the problem with btrfs is that you cannot really "reuse" a btrfs subvolume in every circumstance. In some cases such as /home, it should be and better be) possible ... have not tested this yet because I got hung up trying to reuser btrfs root because you really cannot do that. To reuse, you need to delete that subvolume and then "reuse/reclaim" the space ... you cannot reformat it because the only thing that is formatted is the storage pool.

In the gui there needs to be an error message if you attempt to reuse a subvolume which will be assigned to the "/" mount point. Currently, just nothing 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
Again, at what point are you looking for grub.cfg?
Again, after the install is complete. BTW, this has not happened doing a DVD install.

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?
When editing a new/non-existent device, click on the button with the
tools icon to specify the set of candidate disks for that device. The
change will take effect when you click on "Apply changes", select a
different device/mountpoint, or click "Finish partitioning".
I have clicked on the tool icon many times. So far, nothing has happened. What is suppose to happen? From what you say above, this may be the fuctionality I am looking for to "tune" where new allocations are directed.

Have such tests been conducted successfully by F18 QC?

This is getting a bit frustrating!
You are running a beta. Also, this happens to be a beta that includes an
installer whose UI is also a beta. If you are easily frustrated maybe
you should sit this one out.
No, although there is some frustration, I find that I understand thing better by having problems. After all, when you do something correctly, you do not remember it that well. But, screw up/make a mistake/have a problem, and the lesson is remembered.

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."

Gene


--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test



[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux