solaris8 II - Day 3

Goals

• make sure your NIS boxen are working properly
• make changes on the master
• learn how passwords are changed on the master

POST

1. what is the NIS domain for your box?
2. to what server is it bound?
3. what is the difference in the -m -s -c switches for ypinit?
4. Is it easier or harder to set up a master or slave? Why?
5. Are NIS maps stored on the client? if so, where?
6. Are NIS maps stored on the slave? if so, where?
7. Are NIS maps stored on the master? if so, where?
8. How (in a general sense) are maps transferred?

network your box

master changes/updates

1. make your changes (see revision control below)
2. make
3. push the info out if necessary

user management

• yppasswd, passwd -r nis
• adding users

Revision Control with RCS

initial checkin

• make an RCS if one is not present
• create an empty shell
• ci filename
• enter a description of the file. "." to terminate.

checkout for work

• co -l filename check out a locked version so you can edit
• do your stuff!@

checkin after work

• ci -u filename check in, leave a non-writeable copy in place

other tools

• rcsdiff filename shows diff between current and previous versions
• rlog filename shows changelog
• rcsmerge filename merge into one
• co -l -r1.5 filename checkout version 1.5
• ci -u -r2 filename checkin as version 2.x
• rcsmerge filename merge into one
• embed keyword replacement to embed RCS info: Id, Author, Date, Header, etc

Homework