sudo dpkg --install filename
As root, do these commands:
mdadm --assemble /dev/md0 /dev/hda5 /dev/hdb1 /dev/hdd1
/etc/init.d/lvm2 start
New domains that we're providing name service for go into /etc/bind/named.conf.local on both aphrodite and varsity.
To add a host to the brokerys.com domain, you need to add it to the db.brokersys.com-external file and the db.brokersys.com-internal file. However, you need to be careful. db.brokersys.com-internal is also updated by the DHCP server and you need to not confuse the DHCP server or a lot of the names will stop working. So, before making manual changes to the /etc/bind/db.brokersys.com-internal file, stop bind with the command
/etc/init.d/bind9 stop
Then, remove the journal file with the command
rm /etc/bind/db.brokersys.com-internal.jnl
Then, make your edits.
When you're done, restart the name server with the command
/etc/init.d/bind9 start
nslookup -type=A -debug foo.tld
Because we use Kerberos for secure authentication of users and because we store user's account information in LDAP, adding a user is a multistep procedure. First, the Kerberos principal is created. Then, the user is added to chromite. Then, an LDIF file is created for that user and that LDIF file is used to add the user to LDAP. Once that happens, the user is available on the domain.
To do this, first start kadmin by typing:
/usr/sbin/kadmin
This will bring up a prompt. At which point you type
add_prinicipal -pw
new_password new_username
This adds the new user to Kerberos and allows you to set the user's password.
Then, you can type q
to quit.
This is just like adding a user to any other system. It's necessary to do this step because otherwise the home directory for the user won't be created. Use the command
adduser
new_username
to add the new user.
The easiest way to do this is to copy one of the existing LDIF files in /usr/share/migrationtools
I recommend starting from the file password.cybersmythe.ldif
Set the uid part of the dn field to be new_username and the uid field should also be new_username. The cn field should contain the "common name" which is normally the person's full name. The gn is the first name, and the sn is the last name. The mail and mailRoutingAddress fields should be set to the user's email address, the uidNumber should be set to the numeric user ID that was created when the user was added to chromite and the gidNumber should be set to the numeric group ID that was created with the use was added to chromite. Lastly, the homeDirectory field should be set to the user's home directory and the gecos field should be set to whatever value you wish to use as the user's GECOS field.
Run the command
ldapadd -x -D cn=admin,dc=brokersys,dc=com -W -f
file
Where file is replaced by the name of the LDIF file to take the information from.
useradd -d /dev/null -g 500 -s /bin/false
machinename
smbpasswd -a -m
machinename
then, do the computer name change on the Windows computer
Go to the Web Site and do it.
Go to the Web Site and do it.
Edit the file /etc/dhcp3/dhclient.conf
and set the value for send host-name
to be the name of the computer you want to appear in DNS.
The general procedure to use is
If it's the first key, or if you don't have an authorized_keys file, then most of these steps are unnecessary. You could just create the .ssh file and copy id_rsa.pub into it, renaming it to authorized_keys. However, if you're adding your key to root (which you should do if you would normally have root access or if you can sudo sh) you probably don't want to wipe out the keys that are already there, and I believe this process is safe.
-- JonathanGuthrie - 11 Jan 2008