On 08/12/2016 03:23 PM, Raymond Wooninck wrote:
On Friday, 12 August 2016 14:43:05 CEST Anton Aylward wrote:
On 08/12/2016 01:52 PM, Raymond Wooninck wrote: We are making it very clear that the heavily multi-user system I talk of has been heavily custom configured; for example the accounts i have on a few such machines have me in a chroot'd jail where there are many commands that I simply don't have. The sysadmins of such systems confgure them!
And in those environments the sysadmin would provide you with the root password so that you can run kshutdown ???
Obviously NOT!
In the environment that you are describing, I don't think that you would have even access to something like kshutdown and I am sure that the desktop you might be running in such environment does not have the shutdown possiblity either.
Yes, that is the point i've been trying to make. The single user/laptop/PC model grew out of the IBM/Microsoft PC concepts of "personal computing". UNIX has, except for its initial beginning, always been at least heavily multi-process with a variety of UIDs for the processes, and even then, such as the SUN workstations, there is the central multi-user server.
I believe that this whole discussion got blown out of proportions and nobody is actually looking at how this started.
This got started with a single user/PC/laptop outlook. Such systems are self administered. One poster talked about a 'default" installation meaning 'out of the box" aka straight off a distribution DVD. If we're talking about an system where there has been !ZERO! customization after that point, not even the addition of another user account, then its not really that different from a late model MS-Windows, is it? There you have the user account and an admin account, which is, nominally, if the user set it, password protected. But the installer knows that that password is. The problem comes when we look at commercial/corporate environments. All the ones I've worked at that have supplied me with a corporate PC/laptop (they definitely do not want my Linux laptop connected to their MS network!) had a management account on it that I could not access. When I logged in the corporate net downloaded initialization scripts that I had no control over that did administrative things. I could not download or run any software other than what they gave me. Yes I could shut down my workstation. No I could not shut down anyone else's workstations or any of their jobs running on the server. No I could not shut down the server. Do you see anything wrong with that? I don't. Now lets push that to any other shared environment you want; perhaps the cloud, perhaps an ISP, perhaps the shared service on the large IBM machine running, as some do, Linux as remote to your display engine on your PC/laptop -- 'cos that's the way X11 works :-) But, just like all the IBM/Microsoft PCs in history and up to today's #10, you can still (gracefully) shut down your own workstation. Just don't mess around with anyone else's machine or processes! -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org