On 25.6.2015 14:06, Josef Reidinger wrote:
Solution 2: - Do not create symlinks in inst-sys - Adapt /sbin/yast2 to check that we are in inst-sys and either call YaST2.First-Stage or continue
This is my favority as I hope it is single trivial if statement, so for
It was my favorite as well before I checked the /sbin/yast2 code that already has 432 lines of shell code. Additionally, it plays with paths and ENV variables right at the beginning. Adding "just this" will definitely make the code worse.
solution 3 it seems like overkill for me. Another option that get into my mind is to overuse PATH precedence...so having yast2 in /usr/bin and yast2 symlink in /sbin this way it is not overwritten and it will works without much tricks ( and as bonus allows common users to run yast2 with limited functionality ).
Hmm, this actually sounds like a better solution. So, the only thing to do is to move /sbin/yast2 to /usr/sbin/yast2. And then maybe link it from /sbin/yast2 (for backward compatibility). Then the only difference in inst-sys would be different symlink. Thx Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org