Martin Gracik <mgracik@xxxxxxxxxx> wrote: > I see, but what if you had a user "steve" with already setup sudo access for you, instead of the root account. > Would that make your work more unpleasant? In the sense that it is making extra work for me, yes. I would use the 'steve' account to set up the root account, then delete the 'steve' account. > Now you have to setup root account in the installer. So you have to setup at least one user account. Root is a pre-existing account. All that is needed is to set a password for it. > The way I propose, you would still have to setup only one user, no more work on your side compared to the > situation we have now. The user would just not be called root, but for example "steve". Well, it would be more work for me -- see above. Admittedly, it's a one-time ten minute task to deal with, but multiply that by dozens of machines... > Or is there some reason that you absolutely need root access? A significant number of people subscribe to the "log in as a user then become root" paradigm. I don't. I consider that unnecessarily burdensome. I would argue that there's a significant number of people that work the same way I do. Trying to enforce a "be user, become root" policy through the installer isn't going to make any of us happy. In the end, that's what I object to. It feels like an attempt to enforce a policy that I don't agree with. Let it be default to set up a local user account. But also let it be an option to bypass that and (or in addition) set the root password. Thank you, Steve -- Steven R. Allen - Linux Admin Weenie Unix sysadmin: Linux, IRIX, NetBSD, OS X, Solaris, HP/UX, CX/UX Phone: 206-544-0910 M/S: 4J-06 _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
