|
Bugzilla – Full Text Bug Listing |
| Summary: | Relax mountpoint restriction | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Jan Engelhardt <jengelh> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aschnell, jreidinger |
| Version: | Leap 42.1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | screenshot | ||
Well, we start to be more strict about warnings as we find better to have more strict checking, otherwise user can end up with non-booting pc, which is disaster for newbies. For your case I suggest to at least inform yast what is mounted as "/" in expert partitioner. Which is what this check is exactly about ( bootloader do not see any root mount point, so cannot decide about working boot proposal. So to sum it up. Sorry, we do not support this scenario and we do not plan to go back to less relax boot proposal ignoring failures. The problem is: I *cannot* inform yast about where / is mounted, because the partitioning dialog goes to complain that (for example) encrypted root is not supported. |
Created attachment 700743 [details] screenshot On earlier versions of openSUSE, I remember that I could mount an arbitrary location to /mnt (using the free console on tty2), and yast would happily install into it, albeit with warnings and of course me having to manually fixup the boot in some form. That was fine, as long as it meant all the rpms would be installed to it. All was good - until 42.1, when yast gained an uncanny check (see attachment) to abort the installation.