planning to update some machines here to opensuse 11.2 I started to adapt our autoyast files to that version. Unfortunately i did not much testing with milestone-releases before which one admittedly should. But at least one time I did.
Some general thoughts: ~~~~~~~~~~~~~~~~~~~~~~
What is still hard to guess and to rexplore is change of packaging like pattern and packagenames. Would be nice to have a kind of browser to work ot interactivly the software list in advance. It should list all patterns and its content in hierarchical manner and maybe take in old software list (of preversion) and make suggestions for a new one.
Another point is to have backuped configuration files which get changed by autoyast-script, -file sections. Maybe more general a kind protocol. of things that have been done. I know of /var/adm/autoinstall/logs etc. One could afterwards more easely compare wheather there appeared new switches which should taken in updated version of configuration. If one does not have it, it requirers one to install at least one time the system with nearly no changes at all. I think this cycle could get eliminated.
One big xml-file is still awful concept, I guess even if one applies rules. I would prefer a split up in many parts configuration and even do somehow by a homegrown solution. I'm not sure whether it possible to simulate the application of rules before. I think xml as an intermdiate format is for automatic parsing is ok.
The DTD files should seperately available to applicant before a first installation of new version opensuse. Fishing them somehow from rpms of distribution is not that nice. I would vote for svn-repository for that.
The documentation should as datailed as possible. I still have the feeling that documentation is more by examples and DTDs which one has to watch in than by abstract listing of features.
I general i want to have simple easy to check and changable configuration. Some parts of installation like parts of package resolution should get independly simulated in advance even outside the system thats going to get installed.
Still a problem is to manage packages and configuration of many computers afterwards.
Now that what occured: ~~~~~~~~~~~~~~~~~~~~~
the package samba-winbind failed to install. I interactivly said skip over as i did not even know whether we use it but it was for some reason in package list. I got a warning that i could get a damaged installation. In the end fetchmsttfonts failed. The following messages regarding fetchmsttfonts were in /var/log/zypp/history of installed partition.
# 2009-11-18 02:23:06 /mnt/var/adm/update-scripts/fetchmsttfonts-11.2-6.6.12-fetchmsttfonts.sh.txt ausgeführt # /bin/sh: /mnt/var/adm/update-scripts/fetchmsttfonts-11.2-6.6.12-fetchmsttfonts.sh.txt: No such file or directory # 2009-11-18 02:23:20 /mnt/var/adm/update-scripts/fetchmsttfonts-11.2-6.6.12-fetchmsttfonts.sh.txt Ausführung fehlgeschlagen (Kommando mit Status 127 beendet.)
These are also the last ones of that file.
with that my installation ended, no configuration seemed to be done. What awfully disappeared was the file /var/log/YaST/y2log, it was there before shutting down. I wanted to analyze it but it disappeared. I made installation within kvm-qemu-emulator, so it was easy to look into the partitition afterwards.
I hope to get around these problems this afternoon.