winscape 2292
snip I think we're talking at cross purposes here. I was talking only about whether all users start off with the same configuration (including search path) or whether there...
Something like this could be set up in Unix (multiple "default" configurations, with the choice of which one to use made on .... I can think of a couple of ways to select). It's not built into the system, exactly, but I don't think it would be that difficult to include.
As I understand it, that's exactly the situation Steve is talking about -- the product is installed in some user's home directory (i.e., *NOT* in a system disk area), which means he-she didn't need special privileges to install it there and make it available to other users, but which also means that if he-she leaves without handing it over to someone else .... What should happen? If the sysadmin isn't able to access user files, he-she can't "clean up the mess". It seems to me that for situations like this one needs an all-powerful user. Maybe that should be in addition to a sysadmin user that only has access to system files, though?
before Good grief! Never on a timesharing system. We aren't talking at cross-purposes; all are part of delivering computing services to customers. Which is the heart of any...
So who are you saying should have access to system-with stuff? or isn't there any, in TOPS-10?
"Proprietary HLL"? do you mean the package manager? I guess one of those could count as an HLL, but I'm not sure about "proprietary", since some of them seem to be used by more than one distribution.
snip
-- B. L. Mbuttingill ObDisclaimer: I don't speak for my employers; they return the favor.