Katarina Machalkova schreef:

...

...

The package is yast2-storage >= 2.17.8.

Enjoy!

Screenshots?

The latest version of mockups is here: http://files.opensuse.org/opensuse/en/9/95/Partitioner_pres16.pdf

frozenB.

(Still very busy building a large glasshouse, takes huge amounts of time and energy) This begins to look like a real usefull instrument :) I will give it a try asap, might take a while though.... Thnx for taking the needed overhaul serious... -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.26-3-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.0.42 (x86_64) Alpha1 KDE: 4.1.00 (KDE 4.1.0) "release 16.2" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Hi! Thanks for feedback. Dňa Wednesday 10 September 2008 23:18:14 Felix Miata ste napísal:

The old one was my favorite of all Linux installation partitioners. My initial reaction to this is I'd like the old one back. e.g., this forces me to remember, something I'm not good at, what I just selected, after I've clicked the button to specify where to mount. When I get into "edit partition", all background information is hidden, including the LABEL that reminds me what partition I'm working on. This screen should include the information I had just been looking at, including specifically the existing LABEL. Luckily, and unlike the old, fstab options are available without first specifying the mount point that depends on remembering the LABEL. Also on the "edit partition" screen, "next" would make more sense to me than "finish". I'd only expect "finish" when all partitioning is done.

I suggest to open bug reports for those.

Whatever I specify for mount points for FAT partitions gets discarded upon clicking "finish".

A bug.

After entering the password info, the next screen popped up window:

Calling the YaST module 'proposal has failed.....

Clicking retry fails to do anything.Logs to this point are at: http://fm.no-ip.com/tmp/SUSE/YaST2/

This is fixed meanwhile.

Next takes me back to password entry, where the clock just goes and goes and goes, letting me do nothing else for a long time, but after which proceeds on its own to "perform installation", churns briefly, then proceeds to "finishing basic installation", then does "switching to installed system failed". Complete logs up to rebooting are at: http://fm.no-ip.com/tmp/SUSE/YaST2b/

After the proposal failed, the rest is just random mess. Please, test with when the Factory has rebuilded the installation images with the fix for the 'proposal' problem. I've checked current Factory, fix is not there yet. Stano

Complete partitioning info: http://fm.no-ip.com/tmp/SUSE/dfslog-s2846-f111-0910.txt

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Hi, I notice xfs is not included in the default filesystem. Otherwise its a big improvement. Regards Dave --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

The library beneath the UI has not changed that much so data-loss is not to be expected. E.g. the commit summary will match the actual changes done to the system.

Not really. Finally I has been able to get all my data back, but it was a pain. I know what exactly happened but I am not able to reproduce it once again even on a very similar configuration - that is why I have not reported the bug at the end. But at least I can tell you... I had two primary partitions on my disk and one extended one with several 20GB partitions (did not know how much exactly) and one big home at the end. This partitioning was very, very old, so maybe there was something odd in the partition table. But it survived maybe tens of SUSE installation before. I moved to the expert mode. Installer showed me a list of 20GB logical partitions and a home. I picked up the last one to use it as a root and thus format it. Then I told the installer to leave my home partition as it is. Installer warned me in red it is going to format my 20 GB partition and nothing more. I was perfectly fine with this proposal. The installer formatted the partition for the root filesystem, installation failed then immediately because home could not be mounted. Weird. I have rebooted back to my original installation and did not suspect anything more than a messed up installation like usually. Unfortunately I did not save the logs, I wanted to have the installation to do some tests of my own, not because of general testing. But my home was lost. What really happened? Installer thought up one more partition that did not really exist, presented it in the list of the existing ones and I am pretty sure it told me that it has also 20 GB. The partition table after its action looked like this, sda8 did not make any sense, sda7 was unexpectedly small and contained just several basic directories created during installation and a few files in them: /dev/sda1 : start= 63, size= 41945652, Id=83, bootable /dev/sda2 : start= 41945715, size= 8401995, Id=82 /dev/sda3 : start= 50347710, size=438044355, Id= f /dev/sda4 : start= 0, size= 0, Id= 0 /dev/sda5 : start= 50347773, size= 41945652, Id=83 /dev/sda6 : start= 92293488, size= 41945652, Id=83 /dev/sda7 : start=134239203, size= 20980827, Id=83 /dev/sda8 : start=155220093, size=333171972, Id=83 BTW, this is the output of sfdisk. The real partition table was probably a bit messed up, because when I asked parted to remove partition 8 later, it was unable to do so... although it printed me something similar, during rm it did not believe in its existence. Many thanks to ext3 hackers for their great work because even it this situation it was possible to recover all the data from original sda7. When I found out what really happened (it was not that easy because I did not rememember the count of my partitions), I just had to find some superblock backup and the rest was a great work of fsck :-) Unfortunately, when I recreated settings similar to the original, copied the recovered data back and started the installation again, the bug did not appear again - the list of partitions was correct. I am very sorry that I was that dumb and I did not save the logs at the first attempt :-( Anicka --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Dňa Thursday 18 September 2008 04:36:06 Andrew Joakimsen ste napísal:

Is the bug where resizing the partition not possible fixed?

Not yet AFAIK.

Are there tools now to recover a broken md RAID array? (e.g. if the user boot from the rescue disc)

How is this related to YaST partitioner? Stano

On Mon, Sep 8, 2008 at 7:01 AM, Stanislav Visnovsky wrote:

...

Hi!

The factory tree now contains a full rewrite of the YaST partitioning module. It provides much saner GUI environment, especially for handling more complex setups involving RAID, volume management etc. The same interface is used during installation as the expert partitoner.

However, the change is rather radical and big also regarding the code change. It would be great to get feedback, both on UI as well as reporting bugs (the known ones are assigned to either Arvin (aschnell) or Bubli (kmachalkova) - please check to avoid reporting duplicates).

The package is yast2-storage >= 2.17.8.

Enjoy!

Stano --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org