jbjohnso
|
e25e9fe30a
|
-Try out ceasing use of stunnel in favor of openssl everywhere
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@3643 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
|
2009-06-25 19:18:22 +00:00 |
|
mxi1
|
22f9c58bd7
|
-according Jarrod's code change (from stunnel to openssl), post.sles11 is updated;and move service.sles11.ppc64.tmpl to service.sles11.tmpl;and remove <pattern>base-64bit</pattern> from the .tmpl file;
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@3145 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
|
2009-04-09 08:33:16 +00:00 |
|
jbjohnso
|
e1d8e4611c
|
-Actually export XCATSERVER variable for non-stunnel use
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@3137 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
|
2009-04-08 16:56:13 +00:00 |
|
jbjohnso
|
68956872aa
|
-Correct wording on post.sles11 change
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@3134 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
|
2009-04-08 14:53:10 +00:00 |
|
jbjohnso
|
9f63ade940
|
-Try to eliminate stunnel requirement in SLES11. This approach is cleaner and I would like to switch completely to it across the board when less risky
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@3131 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
|
2009-04-08 14:44:16 +00:00 |
|
mxi1
|
b94f2939fe
|
-move ppc64 away, use HOST_ARCH to replace it
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@3125 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
|
2009-04-08 08:24:26 +00:00 |
|
mxi1
|
9cc89c4c81
|
-bug #2689688 is fixed; SLES11 autoyast file for service node is added
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@3102 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
|
2009-04-06 17:02:54 +00:00 |
|
mxi1
|
8ef87f47bd
|
add full-installation support for sles11, stunnel must be put in /install/post/otherpkgs/sles11/ppc64
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@2962 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
|
2009-03-24 07:48:38 +00:00 |
|