From: Alexei_Roudnev (Alexei_Roudnev_at_exigengroup.com)
Date: Wed Mar 21 2007 - 22:54:13 CET
Message-ID: <0bbc01c76c03$76f0e930$6f31a8c0@sjc.exigengroup.com> From: "Alexei_Roudnev" <Alexei_Roudnev@exigengroup.com> Date: Wed, 21 Mar 2007 14:54:13 -0700 Subject: [suse-sles-e] SLES10 sux (== /bin/su) - broken??
It should work, but it don't work. Documentation (Release notes) is saying that now 'su' can work instead of 'sux' script, but
when I try, I got one of:
sux - user - DISPLAY variable is not isntalled
sux user - X11 authentication error.
sux from old SLES9 do work well.
Anyone have an idea how it should work? (I copied sux script from SLES9 and now it works, of course, but it is not _by design_).
============================================================
(One more SLES10 bug which confirms that system is not production grade yet:
- numerous yast2 problems, including (I mean yast2 modules) YOU (absent), heartbeat (90% absent), evms (absent, may be never worked), updater (!@#$), and so on;
- netfs service dropped and never replaced by something else (hotplug mentioned but don't work properly and is not documented), so no stanard way to mount network-related disks without a hack (the easierst hack is to put netfs back -:));
- iscsi - multiport is not supported, only multipath (no any hack possible, just live with it or dont use it);
- sux - now it is link to su and don't work (it was never ever tested I believe); old sux works pretty well (what is surprise for me).
- jboss dropped (you can load it from OpenSuSe or compile yourself, of course).
What's next? I am intrigued.... I dont count numerous bugs in KDE because it is not primary desktop so you can use it on your own risk only now
).
This archive was generated by hypermail 2.1.7 : Thu Mar 22 2007 - 00:59:54 CET