[m-rev.] For review: Remove add_new_user.html from the website.
Paul Bone
pbone at csse.unimelb.edu.au
Wed Sep 7 15:02:06 AEST 2011
Remove new user document from website.
It has already been copied to the local CVS module where it belongs (with
similar sysadmin notes).
information/developers/add_new_user.html:
As above.
information/include/developer.inc:
Remove links to this document.
Index: information/developers/add_new_user.html
===================================================================
RCS file: information/developers/add_new_user.html
diff -N information/developers/add_new_user.html
--- information/developers/add_new_user.html 24 Nov 2008 04:13:49 -0000 1.10
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,76 +0,0 @@
-<html>
-
-<head>
-<title>Adding a new user.</title>
-</head>
-
-<body bgcolor="#ffffff" text="#000000" >
-<h1>Adding a new user.</h1>
-
-If the new user doesn't already have an account on our departmental machines,
-get the departmental sysadmins to add an account for him/her.
-
-Create a directory for the new user on /home/mercury. (You need to
-be root on uranus to do this).
-
-Our NIS servers are listed in the hosts file, which is in the CVS module
-local.
-
-Get the new user's existing /etc/passwd entry from a departmental machine,
-and then add it to /etc/passwd
-on the NIS master server (using adduser or useradd to be safe).
-The new entry should be below the "+::0:0:::" entry
-that divides the password file
-into the local users and the NIS users.
-Make sure that the new user's home directory on our machines is the one
-you created on /home/mercury.
-
-If the NIS master machine has an /etc/shadow file,
-add the user to that file as well.
-Make sure that the numerical user ids
-are identical to the ones on departmental machines.
-
-<P>
-
-Add the new user to group mercury in /etc/group on the NIS master server
-(using vigr to be safe).
-
-<P>
-
-If you did not copy an existing encrypted password,
-then set the password for the new user
-by executing "passwd <username>" as root.
-
-<P>
-
-Then execute the following commands as root on the NIS master server to
-update the NIS database.
-
-<P>
-cd /var/yp<BR>
-make<BR>
-
-<P>
-
-To make sure that the update to the NIS master
-is effective on a particular NIS client,
-restart the NIS daemon on that client.
-
-<P>
-
-Now add a directory on all the /home file systems that we have access to.
-
-<P>
-
-The user should be encouraged to subscribe to the Mercury mailing lists,
-and to add themself to the list of people involved in the Mercury project
-on the web page (w3/contact/include/people.inc in our CVS repository).
-You should also manually add the user to the mercury-local mailing list
-by modifying the file mulga:/etc/conf/mail/lists/mercury-local.
-
-<P>
-
-Last update was $Date: 2008-11-24 04:13:49 $ by $Author: zs $@cs.mu.oz.au.
-</body>
-
-</html>
Index: information/include/developer.inc
===================================================================
RCS file: /home/mercury1/repository/w3/information/include/developer.inc,v
retrieving revision 1.10
diff -u -p -b -r1.10 developer.inc
--- information/include/developer.inc 18 Sep 2010 13:46:43 -0000 1.10
+++ information/include/developer.inc 7 Sep 2011 04:58:16 -0000
@@ -110,14 +110,6 @@ in a4 format.
<a href="doc-latest/bootstrapping.html">HTML</a>
<p>
-<li> <strong>HOWTO add a new user.</strong> <br>
- Information on what needs to be done when a new person joins the
- Mercury project. <p>
-
- Available in
- <a href="developers/add_new_user.html">HTML</a>
- <p>
-
<!---------
%% Take this out of comments when the bytecode docs have settled down a bit.
<li> <strong>Bytecode</strong> <br>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20110907/ed9db7c0/attachment.sig>
More information about the reviews
mailing list