I copied a core of Yast into /usr/share and these files /usr/bin/xdg-su -c /sbin/yast2
When I trying launch Yast, a console appeared and I wrote a password but it says “authetication failed”
What should I do to make Yast work on Ubuntu?
YaST won’t help you in Ubuntu because Ubuntu uses .deb files and openSUSE uses .rpm files.
There are a number of possible reasons why the authentication failed including not finding the relevant files in the place it expects or not receiving the password it thinks it should be receiving.
But I want launch it on Ubuntu for satisfaction 
Yast requires 3 libs but I don’t know where I can find it. I tried to use search tool but nothing found.
libyui.so3
libpanelw.so6
linncursesw.so.6
m@m-desktop:~$ yast2
libyui.so.3 => not found
warning: the gtk frontend is installed but does not work
GTK GUI wanted but not found, falling back to ncurses.
libpanelw.so.6 => not found
libyui.so.3 => not found
libncursesw.so.6 => not found
warning: the ncurses frontend is installed but does not work
/sbin/yast2: line 347: rpm: nie znaleziono polecenia
Something is wrong with the YaST user interface.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
No, openSUSE/SLED/SLES are diferent from *buntu, the configuration
files of *buntu are placed on diferent directories, they don’t use the
same syntax always and a long list of thing… if you want YaST use openSUSE
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkzi0goACgkQJQ+0ABWtaVmBsgCglAnEpfHvYtKywhUQ0TdfX7Sn
8AwAnRq1/wshDV8sSp5Ndg49/Cd95KQ8
=Gabm
-----END PGP SIGNATURE-----
On 11/16/2010 12:48 PM, VampirD wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> No, openSUSE/SLED/SLES are diferent from *buntu, the configuration
> files of *buntu are placed on diferent directories, they don’t use the
> same syntax always and a long list of thing… if you want YaST use openSUSE
If you want a BMW engine, buy a BMW. Putting one in a Yugo is not likely to be
very successful.
Riksia wrote:
> But I want launch it on Ubuntu for satisfaction
of course it is possible to use YaST on Ubuntu if you take the source
code for YaST and make all the required changes, then recompile and
install…
well, it is as possible but not likely because the number of
programming code changes required will be extensive…
if you are successful you should have a lot of satisfaction…
let us know when you have finished it.
–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
There have been attempts to port YaST to other distributions, even debianoids, see →here. But…
The YaST4Debian project is temporary stopped due to lack of time/resources.
I suppose a new port would have to start from scratch, as the development of yast4debian has stopped more than five years ago. But indeed it would need heavy work, since YaST is 100% SuSE and SuSE only. The modules itself would have to be rewritten and reconsidered, for example most distributions do not offer configuration via /etc/sysconfig.
I suppose if you count distributions by number of installations, then Ubuntu/Debian doesn’t have sysconfig. The question about whether sysconfig is standard was asked before here:
/etc/sysconfig/network/* – are they part of LSB linux standard base?
However sysconfig does appear in RH distros (RHEL and Fedora).
Anyway this is a minor point. To redundantly answer the OP’s question, it would be a lot of work, and I think not worth the effort. System management tools for Ubuntu and Ubuntu-like distros, while not as polished as YaST, do work adequately so you would never recover the investment in porting time. You might like to look at something like Mint’s config tools.
/etc/sysconfig was just one example about how many parameters of a central management application like YaST would have to be ported and adapted. As you said, it can be summed up by stating that it would be a bunch of tedious work. Config tools exist for pretty much any distribution, although not all of them are collected under a convenient hood such as SuSEs YaST or Mandrivas Drak-Tools.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
and not all the config files uses the same syntax… just try to setup a
network card of a *buntu system using YaST… I insist, if the op want
to use YaST, then he/she may use openSUSE or SuSE
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkzj/yIACgkQJQ+0ABWtaVlpGQCfct+ger7o4Z99cw9AkTsOHZsW
BvgAoKisHhCCOCG0FsSYgbzqn/bkkTvs
=q9Cw
-----END PGP SIGNATURE-----
Well, many things are possible, but not all of them are worthwhile.
Amusing, but this approach will never work. There seem to be two and a half approaches (three and a half, if you can salvage anything from the yast4debian project):
Either
- rewrite Ubuntu to work with Yast
- rewrite yast to work with Ubuntu
- some kind of hybrid (which you’ll probably never make work, but whether that is enough to make it different from the first two…
What should I do to make Yast work on Ubuntu?
Gather a team of around 10 competent programmers. Plan the first couple of years of work. Make some overambitious claims/promises out on the interwebs. Become unpopular when you don’t deliver. Go into hiding. Come out of hiding with a beard which is extravagant even by the standards of Unix programmers. Have the last laugh when, several years later you do eventually come out with something workable. Discover that the last laugh wasn’t as worthwhile as you thought when no one else seems interested.
Of course, I could be horribly wrong about that last stage.