Hello, I'm a novice in Installing with autoyast. I try a lot at this time. I have some trouble with installig SuSE 9.2 with autoyast. Problem1: The User "root" has no password, I try to fix it with: <window_manager>kde</window_manager> </x11> <users config:type="list"> <user> <username>root</username> <user_password>password</user_password> <encrypted>true</encrypted> <forename/> <surname/> </user> </users> </configure> After this the User "root" has a password but I can*t login as root. Must the password in the config-File be Plain Text? Problem2: The Installation gives an Error-Message. "Wrong LDAP-Config". This Message comes with or without an Ldap-Entry in the config-File. Has anybody the same Problems? Greetings Daniel -- Daniel Spannbauer EDV Systembetreuung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-66 Auf der Wies 8, D 87727 Babenhausen Fax +49 8333 9233-11 http://www.marco.de/ Email ds@marco.de
Hello Daniel, find an example here: <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>zfweXXD7/g8cs</user_password> <username>root</username> </user> <user> <encrypted config:type="boolean">false</encrypted> <user_password>passwordX</user_password> <username>userX</username> </user> </users> If you want the root password to be encrypted (like in the example above), set a password for root and then take the encrypted version from the respective entry in /etc/shadow. As for the LDAP problem, I have no idea. Regards Alfred At 10:52 19.04.2005, Daniel Spannbauer wrote:
Hello,
I'm a novice in Installing with autoyast. I try a lot at this time. I have some trouble with installig SuSE 9.2 with autoyast.
Problem1: The User "root" has no password, I try to fix it with:
<window_manager>kde</window_manager> </x11> <users config:type="list"> <user> <username>root</username> <user_password>password</user_password> <encrypted>true</encrypted> <forename/> <surname/> </user> </users> </configure>
After this the User "root" has a password but I can*t login as root. Must the password in the config-File be Plain Text?
Problem2: The Installation gives an Error-Message. "Wrong LDAP-Config". This Message comes with or without an Ldap-Entry in the config-File.
Has anybody the same Problems?
Greetings
Daniel
-- Daniel Spannbauer EDV Systembetreuung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-66 Auf der Wies 8, D 87727 Babenhausen Fax +49 8333 9233-11 http://www.marco.de/ Email ds@marco.de
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
Am Dienstag, 19. April 2005 11:58 schrieb Alfred Isele:
Hello Daniel,
find an example here:
<users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>zfweXXD7/g8cs</user_password> <username>root</username> </user> <user> <encrypted config:type="boolean">false</encrypted> <user_password>passwordX</user_password> <username>userX</username> </user> </users>
If you want the root password to be encrypted (like in the example above), set a password for root and then take the encrypted version from the respective entry in /etc/shadow. As for the LDAP problem, I have no idea. The LDAP autoinstallation is broken. This is a known issue. I remember a threat about this recently. LDAP is activated, but the server name and base dn are not set.
You can solve that issue with a postinstall script like: ----------------------------------- <script> <filename>services.sh</filename> <interpreter>shell</interpreter> <location></location> <source><![CDATA[#!/bin/bash # LDAP: start_tls kann der Server nicht. /usr/bin/sed "s/^ssl.start_tls/ssl\tno/" -i /etc/ldap.conf # LDAP: server und basedn einstellen /sbin/yast2 ldap configure server="192.168.xxx.xxx" base="dc=xxxxxxxx,c=xx" # identd: Service starten funktioniert nicht. /sbin/insserv identd ]]></source> </script> ----------------------------------- Bye, Frank
Am Dienstag, 19. April 2005 12:51 schrieb fschuett:
Am Dienstag, 19. April 2005 11:58 schrieb Alfred Isele:
Hello Daniel,
find an example here:
<users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>zfweXXD7/g8cs</user_password> <username>root</username> </user> <user> <encrypted config:type="boolean">false</encrypted> <user_password>passwordX</user_password> <username>userX</username> </user> </users>
If you want the root password to be encrypted (like in the example above), set a password for root and then take the encrypted version from the respective entry in /etc/shadow. As for the LDAP problem, I have no idea.
Thanks a lot about the password-solution. This works.
The LDAP autoinstallation is broken. This is a known issue. I remember a threat about this recently. LDAP is activated, but the server name and base dn are not set.
You can solve that issue with a postinstall script like: ----------------------------------- <script> <filename>services.sh</filename> <interpreter>shell</interpreter> <location></location> <source><![CDATA[#!/bin/bash # LDAP: start_tls kann der Server nicht. /usr/bin/sed "s/^ssl.start_tls/ssl\tno/" -i /etc/ldap.conf # LDAP: server und basedn einstellen /sbin/yast2 ldap configure server="192.168.xxx.xxx" base="dc=xxxxxxxx,c=xx" # identd: Service starten funktioniert nicht. /sbin/insserv identd ]]></source> </script>
----------------------------------- Bye, Frank
Ok, Thanks, I will try this. Best Regards Daniel -- Daniel Spannbauer EDV Systembetreuung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-66 Auf der Wies 8, D 87727 Babenhausen Fax +49 8333 9233-11 http://www.marco.de/ Email ds@marco.de
Hi, fschuett wrote:
Am Dienstag, 19. April 2005 11:58 schrieb Alfred Isele:
Hello Daniel,
find an example here:
<users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>zfweXXD7/g8cs</user_password> <username>root</username> </user> <user> <encrypted config:type="boolean">false</encrypted> <user_password>passwordX</user_password> <username>userX</username> </user> </users>
If you want the root password to be encrypted (like in the example above), set a password for root and then take the encrypted version from the respective entry in /etc/shadow. As for the LDAP problem, I have no idea. The LDAP autoinstallation is broken. This is a known issue. I remember a threat about this recently. LDAP is activated, but the server name and base dn are not set.
A patch for the LDAP bug is in the queue and should be released any time soon. Anas (...)
----------------------------------- Bye, Frank
participants (4)
-
Alfred Isele -
Anas Nashif -
Daniel Spannbauer -
fschuett