26.01.2008 20:10
Here is one more of these completely boring nerdy memos...
I had openSUSE 10.2 running on my Desktop, I was never really happy with it and I never got the sound chip running. So I decided to switch to Ubuntu Gutsy Gibbon. This turned out to be another nightmare. After several failures I finally have it running now. I must say, running Ubuntu on a NIS client is ridiculousely complicated. But when I did it for the third time, even this became quite easy. So here is what you have to do:
- Boot from the live CD and click on install
- choose the manual mode for the partitioner, setup the mount points etc, as you want them, I mount the local disk on /local.
- local user:
you have to set up a local user during the installation, this one will automatically be given sudo-privileges. Choose a user name, which does not exist as a NIS account. - After the installation, reboot, then
- install your favourite editor, it's probably not there yet...
- The home directory of the local account is mounted in /home. I wanted this as a mount point for the NIS accounts, and I already had a local user on the Suse installation so I changed the home directory of the local user to this old one in /local.
- Logout and login again, you are now in your new home directory.
- Do an update, but be careful! In my case (for 64bit version) there was a kernel update which seems to be incompatible with my motherboard (a Foxconn board, can't be recommended...) Gutsy runs 2.2.22-14.46 from the CD. The update was to 2.2.22-14.47. I believe, the update overwrites the original kernel, at least there was no choice which kernel to boot in grub. I had to reboot from CD and start the installation once more. This time I skipped the kernel update. But of course it's generally a good idea to make an update after installation, there might be a whole lot of security updates.
- Install all shells you can think of (tcsh, ksh, csh...). Ubuntu does not come with so many of them and there are problems loggin into a NIS account later on, if the account uses a shell that is not installed on the system. Especially tcsh is often set as the standard login shell. Btw, in Ubuntu /bin/sh points to dash not to bash. I don't know why. I changed it.
- Set up the network connection:
Go to
system > administration > network: select wired connection and set the all the properties, IP, DNS, subnet mask etc. if you are not using dhcp. - NIS:
First you have to install a bunch of things:
sudo apt-get install ssh
sudo apt-get install portmap
sudo apt-get install nis
sudo apt-get install autofs
sudo apt-get install nfs-common
Now edit /etc/passwd
add+::::::
at the end of the file (6 colons).
edit /etc/group add+:::
at the end of the file (3 colons).
Then edit /etc/shadow as well and add+::::::::
at the end (8 colons).
Edit /etc/yp.conf. Addypserver IP_OF_NISSERVER
Set up the automounter. Add* IP_OF_NISSERVER:/path/to/home/dirs&
to /etc/auto.home and write/home /etc/auto.home
into the file /etc/auto.master.
Finally, you have to edit /etc/nsswitch.conf. This file is used by the libc, so it can potentially be devastating if you add something there which is incompatible with your libc version. Puuh, I have had it all... Add the lineautomount nis files
Now restart autofs, nis and sshd.
sudo /etc/init.d/autofs restart
sudo /etc/init.d/nis restart
sudo /etc/init.d/ssh restart
With this I could login to my NIS account. Maybe you have to reboot at this point to get it going. - CUPS:
simply add the lineServerName your_cups_server:631
or whatever port you use for cups. to /etc/cups/client.conf then run
sudo /etc/init.d/cupssys restart