Even More AutoYaST Inquisitiveness

To what extent do I need to configure AutoYaST? There are innumerable modules to configure which are, to be honest, a bit daunting. Things like sysconfig which require an immense bit of detail in its configuration.

Are there items which I don’t need to bother with which can be left in a “generic” configuration?

Does anyone have an example of an AutoYaST file I can look at to get an idea of what I’m configuring?

Am I the only one that can’t seem to generate an AutoYaST file of a system I’m installing when using the text mode to install? The check box is there but it is inaccessible. I can’t select it.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The best way to get an idea of what you need in AutoYast is to, at the
end of your system installation (in 10 at least), check the checkbox at
the end to “Clone” your system. This put an AutoYast file of your
current system in /root for you to peruse. You can also go into Yast
and it will let you create on in there via a GUI-driven interface.
Still a bit of work but combining that with your system’s own AutoYast
file makes things fairly nice.

Good luck.

theillien wrote:
| To what extent do I need to configure AutoYaST? There are innumerable
| modules to configure which are, to be honest, a bit daunting. Things
| like sysconfig which require an immense bit of detail in its
| configuration.
|
| Are there items which I don’t need to bother with which can be left in
| a “generic” configuration?
|
| Does anyone have an example of an AutoYaST file I can look at to get an
| idea of what I’m configuring?
|
| Am I the only one that can’t seem to generate an AutoYaST file of a
| system I’m installing when using the text mode to install? The check
| box is there but it is inaccessible. I can’t select it.
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIaSa13s42bA80+9kRAly5AJ9VD5xVrN6+eu2y+9RCbriC2b4vFwCfS9q6
lDtGfv24vZUKjdKp8Jhns6s=
=aaSP
-----END PGP SIGNATURE-----

That does help. I thought I had tried that before but the file I was looking at was extremely lean in its markup. I must have done it wrong.

Is there a DTD I can look at to figure out the different sections and tags available? I’m looking into writing an interface for the customization of autoyast files and knowing all of the markup would be helpful.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Google: autoyast dtd

http://www.suse.com/~ug/AutoYaST_FAQ.html

Led me to look in /usr/share/autoinstall/dtd

Good luck.

theillien wrote:
| That does help. I thought I had tried that before but the file I was
| looking at was extremely lean in its markup. I must have done it
| wrong.
|
| Is there a DTD I can look at to figure out the different sections and
| tags available? I’m looking into writing an interface for the
| customization of autoyast files and knowing all of the markup would be
| helpful.
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD4DBQFIal0i3s42bA80+9kRAh2hAJilEIlQrs8vm755UGjhuSKPJUjbAJ9JlJEm
yj9DC4QcMLlnLBkNl0hz2Q==
=RFqS
-----END PGP SIGNATURE-----

I don’t have that for some reason. All I have under /usr/share/autoinstall is modules/ and xslt/. The only thing under xslt/ is merge.xslt. modules/ only contains .desktop files.

I have the necessary packages installed: autoyast, autoyast-installation, and autoyast-schema. There isn’t a dtd/ directory but autoyast2-schema provides numerous .rnc and .rng files.I’d hate to have to go through every file to figure out all of the element definitions. But then, I’ll only need to access some of them to change values for individual servers so I guess it wouldn’t be too bad.

I generated a .xml file using the Autoinstallation module in YaST2. However, when I try to validate it I get the following:

autoyast.xml:4: element bootloader: Relax-NG validity error : Element profile has extra content: bootloader
autoyast.xml fails to validate

I’m using profile.rng as the basis for the validation. Any thoughts on why this fails?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My package owning some files in ‘dtd’ is autoyast2-installation.

Good luck.

theillien wrote:
| I don’t have that for some reason. All I have under
| /usr/share/autoinstall is modules/ and xslt/. The only thing under
| xslt/ is merge.xslt. modules/ only contains .desktop files.
|
| I have the necessary packages installed: autoyast,
| autoyast-installation, and autoyast-schema. There isn’t a dtd/
| directory but autoyast2-schema provides numerous .rnc and .rng
| files.I’d hate to have to go through every file to figure out all of
| the element definitions. But then, I’ll only need to access some of
| them to change values for individual servers so I guess it wouldn’t be
| -too- bad.
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIatAm3s42bA80+9kRAlZJAKCCJzQjCHfkCLdUCRcmE73T4RTiIgCeIFQh
sR2D3MEmtnvhtF0C5civbKM=
=t1I1
-----END PGP SIGNATURE-----

I’ve got that installed but no dtd.

From what I’ve found, autoyast2-installation in 10.3 doesn’t provide /usr/share/autoinstall/dtd. Was it removed?