autoYast2 creates invalid XML
I have used the "autoinstall" feature of YaST to create a profile, and
then try to validate it. It comes back with the following errors.
Shouldn't it create a valid profile, especially as I have no way of
choosing the window manager. This is under SuSE 9.1 professional.
===========
/tmp/YaST2-03550-TVAnDd/valid.xml:89: element security: validity error :
No declaration for element security
</security>
^
/tmp/YaST2-03550-TVAnDd/valid.xml:102: element uid: validity error : No
declaration for element uid
<uid>1000</uid>
^
/tmp/YaST2-03550-TVAnDd/valid.xml:127: element window_manager: validity
error : No declaration for element window_manager
Yup, I had one of these problems as well (answer below). You should be able to edit the xml file and just keep on trying the validation (annoying as you have to keep opening the xml file each time you edit it). Tip: when editing the xml file (using vi, for example) copy it somewhere else first. the autoyast GUI seems to occassionally take a dislike to manually edited xml files and then not open them at all (no error, it just does not open them). Quite frankly I am finding it better to keep the xml file small and to do most things using a post-install script. Your uid problem can easily be a one-liner in a post install script, for example. Mind you it does not seem to be all sweetness and light with post-install scripts as they seem to run in a rather odd env, that does not appear to be true sh (missing standard commands, etc.) Mike Rose TCM & Biological Physics Computer Officer http://www.bio.phy.cam.ac.uk/ http://www.tcm.phy.cam.ac.uk/ On Wed, 30 Jun 2004, J. David Eisenberg wrote:
I have used the "autoinstall" feature of YaST to create a profile, and then try to validate it. It comes back with the following errors. Shouldn't it create a valid profile, especially as I have no way of choosing the window manager. This is under SuSE 9.1 professional.
=========== /tmp/YaST2-03550-TVAnDd/valid.xml:89: element security: validity error : No declaration for element security </security> ^ /tmp/YaST2-03550-TVAnDd/valid.xml:102: element uid: validity error : No declaration for element uid <uid>1000</uid> ^ /tmp/YaST2-03550-TVAnDd/valid.xml:127: element window_manager: validity error : No declaration for element window_manager
kde ^ /tmp/YaST2-03550-TVAnDd/valid.xml:128: element x11: validity error : Element x11 content does not follow the DTD, expecting (color_depth | configure_x11 | display_manager | enable_3d | monitor | resolution | start_x11)*, got (color_depth configure_x11 display_manager enable_3d monitor resolution window_manager ) </x11>
you need to change window_manager to display_manager in the start and end
XML tags:
^
-- J. David Eisenberg http://catcode.com/
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
Yes, I have the same problems when configuring e.g. cups ? security ? ntp ? with yast2 (autoinstll) under SuSE 9.1 professionell The typical error when valididating is: /tmp/YaST2-17090-CUEsyZ/valid.xml:112: element default: validity error : No declaration for element default <default></default> ^ /tmp/YaST2-17090-CUEsyZ/valid.xml:113: element printcap: validity error : Element printcap content does not follow the DTD, expecting (printcap_entry)+, got <printcap config:type="list"/> ^ /tmp/YaST2-17090-CUEsyZ/valid.xml:147: element security: validity error : No declaration for element security </security> ^ /tmp/YaST2-17090-CUEsyZ/valid.xml:155: element enable: validity error : No declaration for element enable <enable>1</enable> ^ /tmp/YaST2-17090-CUEsyZ/valid.xml:156: element index: validity error : No declaration for element index <index>0</index> ^ /tmp/YaST2-17090-CUEsyZ/valid.xml:157: element options: validity error : Element enable is not declared in options list of possible children </options> ^ /tmp/YaST2-17090-CUEsyZ/valid.xml:157: element options: validity error : Element index is not declared in options list of possible children </options> ^ /tmp/YaST2-17090-CUEsyZ/valid.xml:233: element sound: validity error : Element sound content does not follow the DTD, expecting (autoinstall , modules_conf , rc_vars , volume_settings), got (modules_conf rc_vars volume_settings ) </sound> ^ Moreover ... It seems as if, when those wrong configuration files are merged online (using classes) they are skipped which is resonable. However, when merging offline they survive. (I send another mail to that problem to suse-autoinstall) F.Mueller Maybe it is a good idea doing only minium with autoyast and the other with post script as you propose. But the better way would be a functioning yast2 xml editor createing valid configuration files. Mike Rose wrote:
Yup, I had one of these problems as well (answer below). You should be able to edit the xml file and just keep on trying the validation (annoying as you have to keep opening the xml file each time you edit it). Tip: when editing the xml file (using vi, for example) copy it somewhere else first. the autoyast GUI seems to occassionally take a dislike to manually edited xml files and then not open them at all (no error, it just does not open them).
Quite frankly I am finding it better to keep the xml file small and to do most things using a post-install script.
Your uid problem can easily be a one-liner in a post install script, for example.
Mind you it does not seem to be all sweetness and light with post-install scripts as they seem to run in a rather odd env, that does not appear to be true sh (missing standard commands, etc.)
Mike Rose TCM & Biological Physics Computer Officer http://www.bio.phy.cam.ac.uk/ http://www.tcm.phy.cam.ac.uk/
On Wed, 30 Jun 2004, J. David Eisenberg wrote:
I have used the "autoinstall" feature of YaST to create a profile, and then try to validate it. It comes back with the following errors. Shouldn't it create a valid profile, especially as I have no way of choosing the window manager. This is under SuSE 9.1 professional.
=========== /tmp/YaST2-03550-TVAnDd/valid.xml:89: element security: validity error : No declaration for element security </security> ^ /tmp/YaST2-03550-TVAnDd/valid.xml:102: element uid: validity error : No declaration for element uid <uid>1000</uid> ^ /tmp/YaST2-03550-TVAnDd/valid.xml:127: element window_manager: validity error : No declaration for element window_manager
kde ^ /tmp/YaST2-03550-TVAnDd/valid.xml:128: element x11: validity error : Element x11 content does not follow the DTD, expecting (color_depth | configure_x11 | display_manager | enable_3d | monitor | resolution | start_x11)*, got (color_depth configure_x11 display_manager enable_3d monitor resolution window_manager ) </x11>you need to change window_manager to display_manager in the start and end XML tags:
kde ^
-- J. David Eisenberg http://catcode.com/
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Dipl. Phys. F.Mueller EPCOS AG Surface Acoustic Wave Components Division SAW RD CAD P.O. Box 80 17 09 Phone: ++49 89 636 23316 D-81617 Munich Fax: ++49 89 636 27304 Germany mailto: Folkhard.Mueller@epcos.com Web: http://www.epcos.com
F.Mueller
Maybe it is a good idea doing only minium with autoyast and the other with post script as you propose. But the better way would be a functioning yast2 xml editor createing valid configuration files.
I agree, but I have now had to further convolute things as I found my post_install script was causing the auto_install process to fail. Not much idea why as if I run the script myself after the auto_install process has completed then everything is fine - submitted as a bug to Suse feedback. I have now moved to having the postinstall script do the bare minimum and put the following script into: /etc/rc.d/first_boot.sh #!/bin/sh # Call the script that should be in ./root and run it with the -x option # and log output to log file in /root /bin/sh -x /root/boot_suse91.sh 2&> /root/boot_suse91.log exit 0 use a soft link: ln -s /etc/rc.d/first_boot.sh /etc/rc.d/rc5.d/S99first_boot and everything works well and I can see what is going on + run it manually if I want to. I am now much happier and can get on with work at a good pace rather than having to reboot the target machine all the time and try to work out what autoyast has done.
Mike Rose wrote:
Yup, I had one of these problems as well (answer below). You should be able to edit the xml file and just keep on trying the validation (annoying as you have to keep opening the xml file each time you edit it). Tip: when editing the xml file (using vi, for example) copy it somewhere else first. the autoyast GUI seems to occassionally take a dislike to manually edited xml files and then not open them at all (no error, it just does not open them).
Quite frankly I am finding it better to keep the xml file small and to do most things using a post-install script.
Your uid problem can easily be a one-liner in a post install script, for example.
Mind you it does not seem to be all sweetness and light with post-install scripts as they seem to run in a rather odd env, that does not appear to be true sh (missing standard commands, etc.)
Mike Rose TCM & Biological Physics Computer Officer http://www.bio.phy.cam.ac.uk/ http://www.tcm.phy.cam.ac.uk/
On Wed, 30 Jun 2004, J. David Eisenberg wrote:
I have used the "autoinstall" feature of YaST to create a profile, and then try to validate it. It comes back with the following errors. Shouldn't it create a valid profile, especially as I have no way of choosing the window manager. This is under SuSE 9.1 professional.
=========== /tmp/YaST2-03550-TVAnDd/valid.xml:89: element security: validity error : No declaration for element security </security> ^ /tmp/YaST2-03550-TVAnDd/valid.xml:102: element uid: validity error : No declaration for element uid <uid>1000</uid> ^ /tmp/YaST2-03550-TVAnDd/valid.xml:127: element window_manager: validity error : No declaration for element window_manager
kde ^ /tmp/YaST2-03550-TVAnDd/valid.xml:128: element x11: validity error : Element x11 content does not follow the DTD, expecting (color_depth | configure_x11 | display_manager | enable_3d | monitor | resolution | start_x11)*, got (color_depth configure_x11 display_manager enable_3d monitor resolution window_manager ) </x11>you need to change window_manager to display_manager in the start and end XML tags:
kde ^
-- J. David Eisenberg http://catcode.com/
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Dipl. Phys. F.Mueller EPCOS AG Surface Acoustic Wave Components Division SAW RD CAD P.O. Box 80 17 09 Phone: ++49 89 636 23316 D-81617 Munich Fax: ++49 89 636 27304 Germany mailto: Folkhard.Mueller@epcos.com Web: http://www.epcos.com
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
participants (3)
-
"Müller, Folkhard" -
J. David Eisenberg -
Mike Rose