Currently we are buying our machines from Microway so the low level setup of the firmware is currently left out. We do however have specific requirements for the Microway setup. We require the SRM console to be used on machines which will not have graphics heads (graphics card, monitor and keyboard). The ARC console does not allow booting without these things, and for compute servers there is no desire to have them.
Disk partitioning is done with the tool "fdisk." Currently fdisk is limited to disks with 63 or fewer sectors per track. The 18 gig Seagate drives that we now buy have 237 sectors per track. Microway suggested that I try an old Intel fdisk trick to get around the limit of 63 sectors/track (our disks have 237 sectors / track). I did the math and came up with: Here are the physical parameters of our disks:
512 bytes/sector
237 sectors/track
20 tracks/cylinder
7501 cylinders
Here is what we tell fdisk:
512 bytes/sector
63 sectors/track
255 tracks/cylinder
2213 cylinders
Here is the console output from an fdisk session:
login as root
/sbin/fdisk /dev/sdb
Command (m for help): c
DOS Compatibility flag is not set
Command (m for help): d
Partition number (1-4): 1
Command (m for help): d
Partition number (1-4): 2
Command (m for help): d
Partition number (1-4): 3
Command (m for help): d
Partition number (1-4): 4
Command (m for help): x
Expert command (m for help): c
Number of cylinders (1-[1023]-65535): 2213
The number of cylinders for this disk is set to 2213.
This is larger than 1024, and may cause problems with:
1) software that runs at boot time (e.g., LILO)
2) booting and partitioning software form other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Expert command (m for help): r
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-2213): 1
Last cylinder or +size or +sizeM or +sizeK ([1]-2213): 2213
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
And the command to layout the disk format is:
/sbin/mkfs -m 1 /dev/sdb1
("m 1" reserves 1% of the disk space for root's use)
In order to allow root logins over the net, rename the file /etc/securetty file.
Most of the system setup is done using a GUI tool named "control-panel." This requires X to be used. If you are not using X then cd to the /etc/sysconfig directory and edit the files by hand. A good reference for the /etc/sysconfig directory is here
To get on the network you will need the file /etc/sysconfig/network and /etc/sysconfig/network-scrips/ifcfg-eth0. Here is network from a typical machine:
NETWORKING=yes
FORWARD_IPV4=no
HOSTNAME=helix01
DOMAINNAME=phys.ufl.edu
GATEWAY=128.227.89.1
GATEWAYDEV=eth0
NISDOMAIN=phys.ufl.edu
And ifcfg-eth0:
DEVICE=eth0
IPADDR=128.227.89.226
NETMASK=255.255.255.0
NETWORK=128.227.89.0
BROADCAST=128.227.89.255
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
ypserver ligo
** Note: the NIS server must exist in the /etc/hosts file **
To create the links from /etc/rc.d/rc? to start ypbind the tool "chkconfig" (same as on SGI Irix machines) is used. Chkconfig gets its information from the /etc/rc.d/init.d/ypbind script. The correct command to start ypbind at boot is"chkconfig --level 5 ypbind on" is used, where 5 is the runlevel to turn this on at. I also turned it on at runlevel 3 and 4 with similar commands.
Check to see if the directory /var/yp exists. If not create it as ypbind requires it to start.
You can now start ypbind with the command "/etc/rc.d/init.d/ypbind start" and then test it with "ypwhich."
Get network time from one of our servers: Add the line "/usr/bin/rdate -s ligo" to the end of the file /etc/rc.d/rc.local
Use our nameservers for DNS lookups: /etc/resolv.conf should read:
search phys.ufl.edu
nameserver 128.227.64.2
nameserver 128.227.64.70
Add the hostname for the local machine, the nameservers, and the NIS server to the file /etc/hosts. Ideally the name and number of the new machine should be added to the /etc/hosts file on phys.ufl.edu and then rdisted over, but this can be done later. /etc/hosts:
# /etc/hosts file for Physics Department
# For information contact
# Last Edited 11/4/97
#
127.0.0.1 localhost loghost
# Campus name servers
128.227.128.24 name.ufl.edu
192.80.214.100 noc.sura.net
128.227.148.252 cutter.clas.ufl.edu
128.227.16.3 orange.qtp.ufl.edu orange
128.227.192.1 crunch.qtp.ufl.edu crunch
128.227.64.7 neptune-gw.phys.ufl.edu neptune-gw
128.227.24.1 neptune.phys.ufl.edu neptune
128.227.89.55 ligo.phys.ufl.edu ligo
128.227.89.??? newmachine.phys.ufl.edu newmachine
Edit /etc/fstab and add the NFS filesystems. Add the user disks and one or more temporary disks and the mail spool area from the mail server.
/dev/sda2 / ext2 defaults 1 1
# /dev/fd0 /mnt/floppy ext2 noauto 0 0
/dev/sda1 none ignore 0 0 0
/dev/sdb1 /helix01/tmp1 ext2 defaults 0 0
none /proc proc defaults
/dev/sda3 none swap sw
/dev/sda4 /usr ext2 defaults 1 2
#/dev/scd0 /cdrom iso9660 ro 0 0
# NFS mounts:
hee:/heeusers /heeusers nfs rw,bg
hee:/hee/cleo /hee/cleo nfs rw,bg
helix02:/helix02/tmp1 /helix02/tmp1 nfs rw,bg
helix03:/helix03/tmp1 /helix03/tmp1 nfs rw,bg
Create the directories and mount the filesystems using mount -a. If this a brand new machine being added to the network, we will need to add it into a netgroup in the /etc/yp/netgroup file on the NIS master server and propagate that to the entire network. It may also be necessary to explicitely export filesystems for the client to be able to mount them. This is done by issuing /etc/rc.d/init.d/nfs restart command.
No comments:
Post a Comment