Bugzilla – Bug 131766
When doing an initial install using ssh, if you type yast2 by accident, you get an error
Last modified: 2005-11-15 13:58:07 UTC
If you type 'yast2' by accident in SL10 ssh install mode, it blows up. I don't believe 'yast2' used to be an option for SLES. In SL10, the program exists in ssh install mode but does this when you type it out of habbit: inst-sys:~ # yast2 /usr/lib/YaST2/bin/yast2: line 66: getopt: command not found Exit.
Just to be sure: This problem occurs with the SUSE Linux 10.0 installation system? > I don't believe 'yast2' used to be an option for SLES. What do you mean by this... or what has SLES to do with this problem?
Right, in the SUSE Linux 10.0 install system. This is the non-official ia64 version. I had run this by Gerald and he suggested to file this. I by no means feel it is urgent to fix. If I don't follow the instructions and type 'yast2' because of habbit, it fails with an error I didn't expect (pasted in the description). I only mentioned SLES to say that when I type yast2 by accident there, I don't think I get the error. I could try it if you want. SLES doesn't have anything to do with it otherwise.
OK. It appears that /usr/bin/getopt is just missing in the installation environment, so that YaST bails out. It should be added. Steffen: Something for you?
Probably we should simply throw /sbin/yast2 out of the inst-sys. It doesn't do anything useful there. Marcus? Do we need /sbin/yast2 in the inst-sys? AFAICS none of our startup script uses it, right?
as far as I know /sbin/yast is the only valid link to the startup script YaST2.First-Stage. I never make use of /sbin/yast2 in the scripts. I think Steffen can decide to remove it
There is no such thing as /sbin/yast2. We are talking about /usr/lib/YaST2/bin/yast2 (see comment 0). Problem is that /usr/lib/YaST2/bin is part of $PATH. Taking it out now. Hope it won't break too much.