My post was in a certain manner of expression. On rapid reading, ux-admin and other readers thought that i did not understand the basics of how elaborate the O/S is or that I did not understand the purpose for built in measures such as the time taken to shut down the system.
The post was on the task of taking Solaris to the home segment as more elaborately addressed in http://www.opensolaris.org/jive/thread.jspa?threadID=36522&tstart=0 What I wrote here was written wearing a non-technical user's shoes, so my post was to present, DELIBERATELY, uneducated questions to the experts in the forum. ux-admin wrote about the user also having to be the root in a single board computer, I am planning to sell Solaris to a user who would blink if the terminal screen pops up. No, he does not want to be the root, and he becomes the root, he would do something like run an fsck and say yes when he has to say, and say no when he has to say yes and end up wiping out the hard disk for a trivial problem. I don't want the standalone user to get anywhere near the terminal, but he needs to have access to the functionality of all ( and only those ) applications that he needs. You went on to say that UNIX is a multi user system etc.. Yes I know how elaborate Solaris is, I know that each function and limitation has a purpose and that Solaris is amazing in the context of a multiuser system. I wouldn't make a multiuser system any easier, nor would I relax the controls in any manner, in fact I would still harden Solaris in a multi user, mission critical setting. Again the post is that of a non-technical, completely non-technical, user thinking aloud. > If you wish to use Solaris effectively, you will have to do some reading. No, the user that I have in mind doesn't care to read. >Do you even care to understand? No, the user doesn't care to understand. He wants it to be easy, he wants it to work. He is that uncooperative, and he is that irrational, and he is the Boss. >For a thing so powerful, complexity is inherent; and while some things can be >simplified, some level of understanding will be required. Waynel, I have answered you as well. Thank you for the commands to shut down immediately. I will go ahead and make a little button and put in the launch menu, or modify the log in button in the user's interface to say include shut down. I knew that such possibilities exist within Solaris, the post is about bringing such ease to the fore, in order to come up with a single user's computer for someone "who doesn't care to understand, who wouldn't read" Ian, I am more talking about Solaris 10, Version 11/06, but I have also been exposed to more advanced developer versions. The shut down feature is not the only difficulty that I am talking about. I am talking about identifying such "irritants" for the common man, who is the Master by virtue of the fact that he has bought a $500 machine with Solaris. Che, the reference to the user phoning up the admin to shut down the system, is just an expression, a manner of expressing how non-technical he could be. In a single user environment, there is no system administrator, so the question of the system admin being comptent or incompetent does not arise. It should be decided at the installation level, before the computer reaches his home. That is where the challenge is. If GM wanted you to master the complex aspects of the valve dynamics and transmission mechanism before it qualified you to buy a car, how many cars would it have sold so far ? And to Open Solaris: Complexity is your business, none of my business. I, as a user, don't care. I don't want to read. Now, give me a solaris computer, easy. Thank you all for the comments. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
