Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!cs.mu.OZ.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!news.kei.com!news.mathworks.com!fu-berlin.de!irz401!not-for-mail From: Sven Rudolph <sr1@os.inf.tu-dresden.de> Newsgroups: comp.unix.bsd.netbsd.misc Subject: Re: Why no addusr? Date: 16 Feb 1997 21:32:16 +0100 Organization: Dept. of Computer Science, TU Dresden, German Lines: 80 Message-ID: <87ohdkqypn.fsf@os.inf.tu-dresden.de> References: <none-ya023480001912962244220001@news.infi.net> <5dnfrp$gob@panix2.panix.com> <DERAADT.97Feb10191845@zeus.theos.com> <none-ya023480001102971923370001@news.infi.net> <5dres4$q38@panix2.panix.com> NNTP-Posting-Host: os.inf.tu-dresden.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: Gnus v5.3/Emacs 19.34 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.netbsd.misc:5440 tls@panix.com (Thor Lancelot Simon) writes: > In article <none-ya023480001102971923370001@news.infi.net>, > Jeremy Williams <none@domain.com> wrote: > >Alrighty then. To bring this thread back to theme, I origionally asked why > >there was no adduser function in NetBSD/Mac68k. I have since, with the > >help of many people, gotten a working solution. Thanks fo that. Now to > >clarify, is there any plan to add a real addusr binary to the source tree > >for a future release? > > A number of people are of the opinion that it's not appropriate to distribute > such a program with the operating system, as it in many -- perhaps the > majority -- of cases requires customization to the local environment which is > ultimately more painful than writing it oneself. Debian GNU/Linux's adduser provides some ways for making adduser customizable and extensible. After creating a user it calls a /usr/local/sbin/adduser.local with the arguments name, uid, gid and home_dir. This allows to do additional work. And it is configurable via a config file /etc/adduser.conf (appended below). So the need for local modification is no reason to not provide an adduser program. adduser should contain the basic framework, provide some often-used options in a configurable way and allow hooks for local changes. Sven -- Sven Rudolph <sr1@inf.tu-dresden.de> ; WWW : http://www.sax.de/~sr1/ # /etc/adduser.conf: `adduser' configuration. # $Id: adduser.conf,v 2.0 1994/06/30 17:14:15 imurdock Exp $ # The DSHELL variable specifies the default login shell on your system. DSHELL="/bin/bash" # The DHOME variable specifies the directory containing users' home # directories. DHOME="/home" # If GROUPHOMES is "yes", then the home directories will be # created as /home/groupname/user. Set USERGROUPS to "no". GROUPHOMES="no" # If LETTERHOMES is "yes", then the home directories created # will have an extra letter in between, the first letter of the # user name. For example: /home/u/user. LETTERHOMES="no" # The SKEL variable specifies the directory containing `skeletal' user # files; in other words, files such as a sample .profile that will be # copied to the new user's home directory when it is created. SKEL="/etc/skel" # FIRST_UID should be the first UID for users on your system. UIDs # (and GIDs) below FIRST_UID are reserved for administrative and # system accounts. FIRST_UID=1000 # The USERGROUPS variable can be either "yes" or "no". If "yes" each # created user will be given their own group to use as a default, and # their setup will arrange to have them create files group-writeable by # default, thus allowing them to effectively use group-writeable # filespace areas (such as /usr/local). If "no" each created user will # be placed in the group whose gid is USERS_GID (see below), and they # will create files not group-writeable by default. USERGROUPS="yes" # If USERGROUPS is "no", then USERS_GID should be the GID of the group # `users' (or the equivilant group) on your system. USERS_GID=100 # If KEEP_NIS_AT_END is "no", then new users will be added _after_ # the NIS entries (entries starting with "+"). The default is to add # all new entries before the NIS entries. KEEP_NIS_AT_END=yes