On Thu, 25 Jun 2015 13:49:30 +0200
Lukas Ocilka <lukas.ocilka(a)suse.com> wrote:
I've been working on a task to make Linuxrc:
Right now, /sbin/yast2 script (#1) on a running system either starts
the Yast Control Center or a Yast module given as parameter. In
inst-sys (installation), this script is replaced by a symlink to
YaST2.First-Stage #2 script and additionally /sbin/yast2.ssh also
links to YaST2.First-Stage. This is done in installation-images #3.
Because of this solution, when yast2.rpm via normal DUD replaces this
symlink with script, the Yast Control Center is started instead.
When DUD=yast2.rpm is used, Installer should start, not YCC.
There are obviously several possibilities how to fix it.
- 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
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 ).
Please comment, maybe you have a better idea?
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org