On Thursday, 14 June 2018 20:24:11 ACST, Carlos E. R. wrote:
On 2018-06-14 12:03, Simon Lees wrote:
On 14/06/18 18:22, Carlos E. R. wrote:
On 2018-06-14 03:25, Simon Lees wrote: ...
Ok well that still wasn't a decision of the openSUSE project, that was a decision that the yast developers didn't want to / have time to / have a business case to add reiserfs support to the new yast storage module, yast is open source if a developer was passionate enough about adding it they may well accept contributions in this area.
No, you still misunderstand. There is no need at all to add reiserfs support to yast.
Instead, they added a check to refuse upgrading at all, instead of just ignoring the entry in fstab.
I have a multiboot system, and there are old installs in the disks that were done back in the day using reiserfs, not affecting the system that was being upgraded this time. The only thing that is needed is for fstab to be left as is, and just show a warning that YaST does not support reiserfs.
I upgraded the system with zypper dup instead to 15.0, which uses the reiserfs partitions just fine.
Yes but they still need to do something even if it is showing there is an unknown / unsupported filesystem, otherwise if they just completely skip the entry people will complain that yast can't find there disk etc, what if someone wanted to take that disk wipe it and use it for an install? or install openSUSE on a xfs partition thats on the same disk as a reiserfs partition? The point is they need to do something and the simplest something that's less likely to introduce bugs is to just abort because it is too hard and they are trying to do something yast doesn't support. Given that the storage system is new, maybe they just haven't had time to add support and maybe if there is enough demand they will add it in the future or maybe someone else who cares enough to fix it will. But these are things that can only be addressed by talking to the yast developers rather then the people here. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B