From: Alexei_Roudnev (Alexei_Roudnev_at_exigengroup.com)
Date: Thu Mar 22 2007 - 00:02:51 CET
Message-ID: <0bc501c76c0d$0d8e9050$6f31a8c0@sjc.exigengroup.com> From: "Alexei_Roudnev" <Alexei_Roudnev@exigengroup.com> Date: Wed, 21 Mar 2007 16:02:51 -0700 Subject: Re: [suse-sles-e] SLES10 sux (== /bin/su) - broken??
su + x11 works only if you login as a user and su to the root, but not in
opposite direction. Root can't get user and stil ahev x11 access.
And it is not documented anywhere in the system. (the only workaround - copy
old sux script and use it, it works).
So if I slogin -X oracle@server, then I can do 'su root' and from root 'su
oracle'. (And even 'su - oracle'). But not vice versa.
Why, why everything which I try on SLES10 is broken or damaged? Almost
everything! (SP1 beta looks better). It reminds me old Linuxes - nothing
works out of the box, but a few small hacks (multipath.conf. lvm.conf, and
so on) and everything get to work. Old Linux hackerts are very happy with
it, of course (me too - good job security).
(Sles10 works, and OpenSuSe works. Problem is with quality. One bug is
minor, 2 bugs are minor, but 10 minor bugs became a problem. I counted
countless number of _all minor_ bugs and inconsistencies in SLES10 - system
quality drops dramactically compared with SLES8 and SLES9. It starts from a
small things, like, yes, 'CD Update' in yast and 'Installation is not
compatible with your CD disk' /real case on one image2 test server/, but
unfortunately it always ends in the bad overall system quality.
yast2 have now so many minor bugs, that I dont know if it can be recommended
anymore... GUI have more and more bugs (as I said before, KDE is already
half-broken - defaulst are not correct for SLES10). I like many and many
improvements in SLES10, but if # of minor bugs will grow so fast, it means
that system is not tested --> the chance of major bug growth...
To be honest, I did not saw any critical bug yet. All bugs had a
workaround.But the same is true for, say, Ubuntu Linux (any bug have a
workaround) or Mandrake Linux (just the same). I need workaround for sux, I
need workaround for _netdev, I need workaround for iscsi multiport, I need a
workaround for YOU server, I need a workaround for 'Jboss absent', and so
on... 1 workaround, 2 workaround, ... 10 workarounds, the numbers began to
speak for me _system is not tested, yast2 is not used by new developers,
iscsi was never configured in QA, documentation is never corrected by
technical editors. Then it comes to the question _was drivers for FC LP8000
card tested with multipath_ (for example). Guess what is an obvious answer?
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Thu Mar 22 2007 - 02:08:25 CET