Comments on: Update on YaST Development Status https://lizards.opensuse.org/2018/07/05/yast-development-update/ Blogs and Ramblings of the openSUSE Members Fri, 06 Mar 2020 17:50:09 +0000 hourly 1 https://wordpress.org/?v=4.7.5 By: Jacob Ethan https://lizards.opensuse.org/2018/07/05/yast-development-update/#comment-15949 Fri, 13 Jul 2018 05:53:10 +0000 http://lizards.opensuse.org/?p=13248#comment-15949 Nice Blog!!

You can call on our Kaspersky Help And Support and get the best assistance for the Kaspersky antivirus as well any help like to recover any damaged or corrupted data then our technical team will help you.
kaspersky help support
kaspersky help support
Kaspersky Tech Help

]]> By: Tony Su https://lizards.opensuse.org/2018/07/05/yast-development-update/#comment-15944 Mon, 09 Jul 2018 04:41:51 +0000 http://lizards.opensuse.org/?p=13248#comment-15944 Very interesting and informative.
Will want to see these changes, can’t wait.

But,
Would like to see…

You new semi-graphical way of using a button to move a proposed new partition to the beginning or end of free space… I hope that the operation is done without detail, I doubt that the average user will care about cylinders or sectors.

Also,
I find your description of the UEFI vs MBR when a bootloader already exists interesting, but is it sufficient or complete? It’s my understanding that the problem is really “MBR vs GPT” and that GPT supports a mixed mode of both UEFI and MBR although most people think that if you have a UEFI boot (typically because they’re multi-booting Windows) that they also need to install openSUSE using UEFI… which shouldn’t be true.

Bottom line I guess is that the Installer should guide the User to configure what is supported for a problem-free experience, but somewhere it should be noted if the Installer is lacking in some kind of capability that is not consistent with published RFC. And, if a certain selection will likely lead to a bad result, I would expect that something stronger than a “very” strong warning is displayed.

]]>