From owner-freebsd-questions Wed Apr 16 16:08:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA13960 for questions-outgoing; Wed, 16 Apr 1997 16:08:15 -0700 (PDT) Received: from neptune.neptune.net (doug@neptune.neptune.net [204.107.103.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA13938 for ; Wed, 16 Apr 1997 16:08:12 -0700 (PDT) Received: (from doug@localhost) by neptune.neptune.net (8.7.5/8.7.3) id QAA19987 for freebsd-questions@freebsd.org; Wed, 16 Apr 1997 16:04:45 -0700 (PDT) Date: Wed, 16 Apr 1997 16:04:45 -0700 (PDT) Message-Id: <199704162304.QAA19987@neptune.neptune.net> From: Doug Jolley Subject: su to root To: undisclosed-recipients:; Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks to all (and there were many) who responded to my plea for help in this topic. I am now able to su to root just fine. However, I'd like to through a couple of observations out for comment. First, in running tests here it appears that it's the group number and not the name that's important. I tested having myself in group 0 but with that group re-named "spoke" rather than "wheel" and I was able to su to root just fine. Secondly, and this was a surprise, it appears that in orde to be able to su to root one must be associated with group 0 in the /etc/group file. By that I mean that having the user assigned to group 0 in the /etc/passwd file does not seem to work. That appears to me to be in direct contradiction to what the man page on group says. So, to wrap up this topic, am I missing something on that point? Thanks again for any input. ... doug ______________________________________________________________________________ Doug Jolley mailto://doug@cybernautics.net http://www.cybernautics.net Don't bogart that file, my friend. Net it over to me. ------------------------------------------------------------------------------