ralfi@pemcom.pem-stuttgart.de (Ralf U. Holighaus) (04/12/91)
slootman@dri.nl (Paul Slootman) writes: >Me too! I wonder why this "luid" business is forced on us; even commands >such as "ct" don't work (you get a login, but then it complains about >the user id... *&^*$#^%#&^%# :-( ) It is mentioned in the release notes that ct doesn't quiet do what it's supposed to do.. You can get the new su along with many other improvements as SLS257 by any SCO reseller for free, or download it from SCO, SCO London or SCO Frankfurt with anonymous uucp. REgards Ralf. -- PEM Programmentwicklungsgesellschaft | Ralf U. Holighaus fuer Microcomputer mbH | Technical Support PO-Box 810165 D-7000 Stuttgart 80 Germany | holighaus@PEM-Stuttgart.de VOICE: x49-711-713045 FAX: x49-711-713047 | ..!unido!pemcom!ralfi
rvdp@cs.vu.nl (Ronald van der Pol) (04/12/91)
ralfi@pemcom.pem-stuttgart.de (Ralf U. Holighaus) writes: >slootman@dri.nl (Paul Slootman) writes: |You can get the new su along with many other improvements as SLS257 by |any SCO reseller for free, or download it from SCO, SCO London or |SCO Frankfurt with anonymous uucp. or via anonymous ftp from uunet.uu.net (/sco-archive/SLS) -- Ronald van der Pol <rvdp@cs.vu.nl>
mju@mudos.ann-arbor.mi.us (Marc Unangst) (04/15/91)
ralfi@pemcom.pem-stuttgart.de (Ralf U. Holighaus) writes: > You can get the new su along with many other improvements as SLS257 by > any SCO reseller for free, or download it from SCO, SCO London or > SCO Frankfurt with anonymous uucp. No, no, I already did that. I was sort of hoping that it would do what it said it would do. Unfortunately, even with "c2" changed to "c1" in /etc/auth/system/default, and unx257 installed, su(1) still gives the "Sorry" message when I try to su from my account to root. I've given up on the SCO su(1). I don't think SCO is ever going to be able to make SCO Unix act like "real Unix" -- i.e., you type "su", and after you enter the correct password, you ARE root. The only thing to identify you as your previous user is your utmp record. -- Marc Unangst | mju@mudos.ann-arbor.mi.us | "Bus error: passengers dumped" ...!hela!mudos!mju |
dag@gorgon.uucp (Daniel A. Glasser) (04/16/91)
In article <eoke13w164w@mudos.ann-arbor.mi.us> mju@mudos.ann-arbor.mi.us (Marc Unangst) writes: >I've given up on the SCO su(1). I don't think SCO is ever going to be >able to make SCO Unix act like "real Unix" -- i.e., you type "su", and >after you enter the correct password, you ARE root. The only thing to >identify you as your previous user is your utmp record. Actually, I can't remember ever using a version of Unix that exhibits this behavior through 'su'. Every 'su' I've ever used (7th edition through SysV) has spawned a new shell with uid set to root, but the parent of that shell was the su command, and the parent of that was the shell with the original uid. The only thing to identify you as your previous user is your utmp record and your parent (or grandparent or greatgrandparent) process uid. I may be wrong, but this is how it's always looked to me. Daniel A. Glasser -- Daniel A. Glasser One of those things that goes dag%gorgon@persoft.com "BUMP! (ouch!)" in the night.
mju@mudos.ann-arbor.mi.us (Marc Unangst) (04/17/91)
I wrote: >I've given up on the SCO su(1). I don't think SCO is ever going to be >able to make SCO Unix act like "real Unix" -- i.e., you type "su", and >after you enter the correct password, you ARE root. The only thing to >identify you as your previous user is your utmp record. Well, I've just finished playing around with the SCO ODT configuration, and I think I've got things fixed. The trick is that all users must have the "su" authorization, or else the old su restrictions apply. The cover letter for unx257 and the documentation for ODT don't mention this, of course. A blanket solution is to remember any changes you made to /etc/auth/system/default, copy .../default.unix to .../default, and then re-make the changes. default.unix is a default file with more liberal defaults; more like "real Unix" than "C2 Unix". At this point, I can now log in as "mju" and su to root with no problems. I think I've discovered what I don't like about SCO. With SCO Unix, you can usually get the system to do what you want it to if you bang on it long enough and experiment enough. The basic problem is that there are a lot of things that aren't documented extensively enough, or documented at all. I don't like to think about what would happen if I didn't have as much time as I do to putter around with SCO Unix -- I'd really be in trouble if I had clients depending on some of the more esoteric features of Unix that SCO got "almost right". I don't know about other people, but I'd be willing to pay $300-$400 extra (or maybe even more) for ODT/Unix documentation that includes things like printed man pages; original source docs for software that started out someplace else, like MMDF or X; and extensive documentation on how to deal with the SecureWare stuff. This "play around with it for a few days and muddle through" business is getting old. -- Marc Unangst | mju@mudos.ann-arbor.mi.us | "Bus error: passengers dumped" ...!hela!mudos!mju |
chip@chinacat.Unicom.COM (Chip Rosenthal) (04/18/91)
In article <e1Zi13w164w@mudos.ann-arbor.mi.us> mju@mudos.ann-arbor.mi.us (Marc Unangst) writes: >I don't know about other people, but I'd be willing to pay $300-$400 >extra (or maybe even more) for ODT/Unix documentation that includes >things like printed man pages OK...put your money where your mouth is :-) The documentation is unbundled from the base system. The `Open Desktop Optional Documentation Set' is what you are looking for. It lists for $275. If we ever meet, remind me to whip you with a wet noodle for even suggesting that man pages could cost more than $400. -- Chip Rosenthal 512-482-8260 | Unicom Systems Development | I saw Elvis in my wtmp file. <chip@chinacat.Unicom.COM> |