Unix Forum

ifconfig hme0 plumb
hme0: flags=842 mtu 1500 inet 0.0.0.0 netmask 0 ether 8:0:20:9c:6b:2d
#ifconfig hme0 192.168.1.132 netmask 255.255.255.0 up
#ifconfig hme0:1 172.20.15.4 netmask 255.255.0.0 up Virtual Interfaces
hme0: flags=843 mtu 1500 inet 192.168.1.132 netmask ffffff00 broadcast 192.168.1.255 ether 8:0:20:9c:6b:2d hme0:1: flags=842 mtu 1500 inet 172.20.15.4 netmask ffff0000 broadcast 172.20.255.255
Configuration Files
/etc/hostname.hme0 (enter hostname of machine )
/etc/netmasks (146.122.157.0 255.255.255.0)
/etc/hosts (146.122.157.__ hostname)

Change the hostname in the following files: /etc/nodename /etc/hostname.*interface /etc/inet/hosts /etc/inet/ipnodes

How do I enable XDMCP on my Unix machine

On most Unix/Linux distributions XDMCP is disabled by default.
In order to enable your server to accept XDMCP connections you need to modify a few configuration files.
The configuration files are located in different directories depending on the distribution.
Please select the version you are currently using:
XDMCP: Red Hat Linux and Other GNOME based systems
On many versions of Red Hat Linux and other versions of Unix which have the GNOME desktop environment, enabling XDMCP only takes a few clicks.
1. Log in as root2. Open a terminal3. type gdmsetup (a dialog box will appear)4 Click on the XDMCP tab5. Check the Enable XDMCP box6. Press Close
XDMCP: Fedora Core 5
On many versions of Red Hat Linux and other versions of Unix which have the GNOME desktop environment, enabling XDMCP only takes a few clicks. Note that on Fedora Core 5 systems, gdmsetup has changed1. Log in as root2. Open a terminal3. type gdmsetup (a dialog box will appear)4 Click on the Remote tab5. Change Style to Plain6. Press Close
XDMCP: SuSe Linux
On SuSE linux systems you must manually edit the configuration files.
1. Log in as root2. Open /etc/sysconfig/displaymanager Change DISPLAYMANAGER_REMOTE_ACCESS=”yes”3. Open the files /etc/opt/kde3/share/config/kdm/kdmrc and /etc/opt/kde3/share/config/kdm/kdmrc.SuSEconfigFind the XDMCP section and set Enable to true[Xdmcp]Enable=trueWilling=/etc/X11/xdm/XwillingXaccess=/etc/X11/xdm/Xaccess4. Open /etc/X11/xdm/XaccessMake sure there is no # to the left of the * in the following host line* #any host can get a login window5. Open /etc/X11/xdm/xdm_configChange the DisplayManager.requestPort line to ! DisplayManager.requestPort: 1776. Restart the system
XDMCP: Solaris 9 and below
Solaris machines have XDMCP enabled by default. In case it has been disabled for some reason
1. Log in as root2. Open a terminal3. type “cd /usr/dt/config”4 edit the Xconfig file5. Comment out the lineDtlogin.requestPort: 06. Save and restart the server
XDMCP: Solaris 10

Solaris 10’s desktop environment is JDS which is basedoff of GNOME.
1. Log in as root2. Open a terminal3. type gdmsetup (a dialog box will appear)4 Click on the XDMCP tab5. Check the Enable XDMCP box6. Press Close
XDMCP: General Instructions
Here are general instructions to enable XDMCP manually editing files on unix systems.
1. Log in as root.2. From /etc/X11/xdm/Xaccess file, uncomment the line ”# * #any host can get a login window”.3. From /etc/X11/xdm/xdm-config file, comment out the line “DisplayManager.RequestPort: 0”.4. From /etc/X11/gdm/gdm.conf file, set the enable status to True (or 1) in [xdmcp] section.5. From /etc/kde/kdm/kdmrc file, set the enable status to True (or 1) in [xdmcp] section.6. The system needs to run in init level 5 (/etc/inittab).7. Reboot the Linux system after modification. Log in as root to the Linux machine again. Go to system settings, security level. Reduce the firewall security so that you can connect remotely. Do this only until able to connect with X-Win32, then you can properly reconfigure the firewall to accept XDMCP connections.
Don’t forget to open up your Firewall ports. For help configuring your firewall

What ports need to be opened for XDMCP




X-Win32 can connect to linux hosts even behind a firewall.
Open up TCP port 6000-6005 (plus X-Win32’s base display number) in both directionsOpen up UDP port 177 to accept incomming connections from any port.
If you are using Gnome open up TCP ports 16001 and TCP 35091 in both directions.
If you are behind a router using NAT, map those ports to the IP address of your local computer on your LAN. The only other thing is make sure on the Network tab under the X-Config menu, that your display is the correct IP address. This is the address you are telling the host to send the session back to.

If you are using SuSE linux firewall, edit /etc/sysconfig/SuSEfirewall2 changing the default options to the following

FW_SERVICES_EXT_UDP=“177 bootpc”FW_ALLOW_FW_BROADCAST_EXT=“yes”

1) Making both drives the same.

We start with slicing the second drive in the same way as our first drive, the master. # prtvtoc /dev/rdsk/c1t0d0s2 fmthard -s - /dev/rdsk/c1t1d0s2 No need to newfs the second drive slices here, that will automaticaly done by the mirror syncing later
2 ) Metadbs
We can now setup our metadbs. # metadb -a -f –c2 c1t0d0s6 c1t1d0s6 Since its the initial creation of the metadbs, we need to force it with -f -a adds the metadbs, and -c tells it how many to create. You can see the results with metadb -i. metadb -i is a very handy tool to determine the state of your metadb states.
3) Initializing the devices
Now we go to setup the initial metadevices. # metainit -f d0 1 1 c1t0d0s0 / # metainit -f d11 1 1 c1t0d0s1 /swap # metainit -f d31 1 1 c1t0d0s3 /tmp # metainit -f d71 1 1 c1t0d0s7 /apps
# metainit -f d1 1 1 c1t1d0s0 / # metainit -f d12 1 1 c1t1d0s1 /swap # metainit -f d32 1 1 c1t1d0s3 /tmp # metainit -f d72 1 1 c1t1d0s7 /apps Like metadb metainit must be forced with -f, but this time not because its the initial creation, but because we work on mounted filesystems. So, here we create a 1 way concatenation of our actual slices and form the needed submirrors.
4) Mirroring fun part 1!
# metainit d2 -m d0 / # metainit d13 -m d11 /swap # metainit d33 -m d31 /tmp # metainit d73 -m d71 /apps
Here are the actualy mirroing intialized, the -m tells SDS that we want to build a mirror with the name in the first colum and consiting of the submirror in the third colum. We now have a one way mirror of our system drive, but its not active yet.
5) Setting the root device
# cp /etc/vfstab /etc/vfstab_pre_sds # cp /etc/system /etc/system_pre_sds # metaroot d2 6) Setting up /etc/vfstab
#device device mount FS fsck mount mount #to mount to fsck point type pass at boot options # fd - /dev/fd fd - no - /proc - /proc proc - no - # # sds drives # /dev/md/dsk/d13 - - swap - no - /dev/md/dsk/d2 /dev/md/rdsk/d2 / ufs 1 no logging /dev/md/dsk/d33 /dev/md/rdsk/d33 /tmp ufs 1 no logging,noatime /dev/md/dsk/d73 /dev/md/rdsk/d73 /apps ufs 2 yes logging # non sds drives # #/dev/dsk/c1t0d0s0 - - swap - no - #/dev/dsk/c1t0d0s1 /dev/rdsk/c1t0d0s1 / ufs 1 no logging #/dev/dsk/c1t0d0s3 /dev/rdsk/c1t0d0s2 /var ufs 1 no logging,noatime
#/dev/dsk/c1t0d0s4 /dev/rdsk/c1t0d0s4 /opt ufs 2 yes logging
#/dev/dsk/c1t0d0s5 /dev/rdsk/c1t0d0s5 /export/home ufs 2 yes logging
# # swap slices # swap - /tmp tmpfs - yes -
7) Making sure we can boot in case of disk failure.
To make sure we can boot in case a disk fails, we need to tell the kernel to ignore the quota on metadbs, otherwise we can't boot in a two disk setup, because we can't never fullfill the requirments. For that we add the following to /etc/system set md:mirrored_root_flag=1
# echo "set md:mirrored_root_flag=1" >> /etc/system
8) Our first reboot!
Bring down the system to the OBP, don't reboot yet fully. We need to setup the boot devices now. OK setenv boot device disk0:b disk1:b Make sure the devaliases of disk0 and disk1 are actualy pointing to the correct hardware decives. Now we boot our system up for the first time on the mirror. If all went well we are up and running in a few seconds. 9) Mirroring fun part 2!
Now its time to hook up the second drive so we have actualy mirrored slices. # metattach d2 d1 / # metattach d13 d12 /swap # metattach d33 d32 /tmp # metattach d73 d72 /apps This will take considereble amount of time. Use metastat to check on the progress of the syncing Example metastat d2
10) All done,

1. login in as root. 2. #ioscan -fnC disk ( find the disk device file which u requires to configure it). 3. if u want to add it in the exsting VG follow the steps. 3.a. pvcreate -f /dev/rdsk/cxtxdx ( please replace the proper numbers in place of x which u got from ioscan). 3.b. vgextend /dev/vgname /dev/dsk/cxtxdx ( this extends the exsiting VG on the hard disk). ( but before doing it check the MAX PE per PV value and PE Size of the exsiting VG u want to increase using vgdisplay. (#vgdisplay /dev/vgxx) Multiply both the values Max PE per PV * PE size eg:- 2500 * 4 (default is 4) = 10 GB , so the maximum size of the hard disk i.e PV will be of 10 GB calculate and find it out whether ur VG supports 36 GB if it supports u can extend the VG otherwise u have to create the new VG) 3.c. vgdisplay -v /dev/vgname ( displays number of lvs , pvs in that vg). 3.d lvcreate -L 1000 /dev/vgname (creates filesystem of 1 GB ) 4. to create new VG. 4.a. mkdir /dev/vg01 4.b. mknod /dev/vg01/group c 64 0x010000 ( please note :- 0x010000 is the minor number please check the previous vg minor number and make change in place of 1 ). 4.c. vgcreate /dev/vg01 /dev/dsk/cxtxdx ( new vg is created). 4.d. vgdisplay -v /dev/vg01 4.e. lvcreate -L 1000 /dev/vg01 ( creates the new file system). 5. newfs -F vxfs -o largefiles /dev/vg01/rlvol1 ( options is according to the requirements). 6. make the apporpriate entry in /etc/fstab. 7. create the mount point. 8. mount -a ( mounts the file system). rgds radhakrishnan ========================== Jeff Cleverley wrote: ========================= Quy, My assumption is that the second disk will be a new file system and not a mirror of the root disk. SAM is an easy way to do this if you're not familiar with the manual method. Below are manual steps if you want them. 1. Shut down the system (shutdown -hy 0) and power it off. 2. Add the disk to the internal carrier. Make sure the disk is jumpered to an id other than 6. Ignore this if you are adding it to a pci card externally. 3. Power the system on. Interupt the boot and do a "sea" to search for disks. Make sure it sees the disk and that it is the address you think it is. The system will find the disk during boot and create device files for it in /dev/rdsk and /dev/dsk. Run the following commands from the command line. The assumption of a c0t5d0 disk is made. Change it if it is a different address. 4. pvcreate /dev/rdsk/c0t5d0 (or new device address). 5. mkdir /dev/vg01 6. mknod /dev/vg01/group c 64 0x010000 7. vgcreate /dev/vg01 /dev/dsk/c0t5d0 You are now ready to create a logical volume(s). 8. Do a "vgdisplay /dev/vg01" and look for "Total PE". This is how many xtents you can allocate. 9. lvcreate -l