mxi1 021457531b from now on, the entries in "litetree" table are no longer restricted to use different mnt point name; for example, ... The "litetree" table has the following entries: "1","ALL","192.168.11.107:/test/$node",, "2","ALL","192.168.11.108:/test/$node",, before the code is checked in, if you run "litetree <nodename>", you should get one message like this: <nodename>: 192.168.11.107:/test/<nodename> # 192.168.11.107 and 192.168.11.108 both mount /test. This not supported. After the code is checked in, there will be no any error/warning message about the entries in litetree table. Accordingly, the naming of mount points on the compute nodes are updated to "/.statelite/mnt/<nfs server ip>/<nfs directory>/" from "/.statelite/mnt/<nfs directory>/". git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@7105 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd		2010-08-17 02:57:52 +00:00
..
ca
cons	multiple hardware control points support for scaling test	2010-08-09 05:56:59 +00:00
ib	use /bin/ksh instead of /usr/bin/ksh for RH6	2010-06-24 02:59:05 +00:00
image_data	change partition size	2010-07-27 19:33:01 +00:00
install	added xCAT updateflag notification and ssh	2010-08-10 23:01:09 +00:00
installp_bundles	add devices.tmiscsw.rte & perl-DBD-DB2	2010-08-05 16:42:50 +00:00
netboot	from now on, the entries in "litetree" table are no longer restricted to use different mnt point name; for example,	2010-08-17 02:57:52 +00:00
postscripts
rollupdate
scripts
tools	add LL DBM setup	2010-08-11 12:13:37 +00:00