Hello Uwe, yes, I am using 11.4, so your linux/suse... procedure works nicely (wow, what a great way to add files to the install system through NFS!). The service file is found in the right location in the installation system and I can see in y2log that it is considered at some point: --------- ... 2012-07-03 11:45:28 <1> test114(3565) [Pkg] PkgFunctions.cc(CreateRepoManager):242 Path to repository files: /etc/zypp/repos.d 2012-07-03 11:45:28 <1> test114(3565) [zypp] PathInfo.cc(readdir):574 readdir /etc/zypp/services.d 2012-07-03 11:45:28 <1> test114(3565) [zypp] IniParser.cc(parse):69 Start parsing /etc/zypp/services.d/LNT.service[g___] 2012-07-03 11:45:28 <1> test114(3565) [zypp] IniParser.cc(parse):119 Done parsing /etc/zypp/services.d/LNT.service[_eF_] 2012-07-03 11:45:28 <1> test114(3565) [Progress++] ProgressData.cc(report):86 {#15|/etc/zypp/services.d/LNT.service}END 2012-07-03 11:45:28 <1> test114(3565) [zypp] ServiceFileReader.cc(parseServices):54 LNT 2012-07-03 11:45:28 <1> test114(3565) [zypp] ServiceFileReader.cc(parseServices):95 Linking ServiceInfo with file /etc/zypp/services.d/LNT.service 2012-07-03 11:45:28 <1> test114(3565) [zypp] RepoManager.cc(init_knownRepositories):552 start construct known repos 2012-07-03 11:45:28 <1> test114(3565) [zypp] RepoManager.cc(init_knownRepositories):573 end construct known repos ... --------- But then, it looks like the service is not used or activated or anything. The repos defined in the repoindex.xml are definitely not added and the lines above are all I see about services. I guess there is no logic for processing service files in the installation procedure. You don't happen to know how I would force YaST to do that? BTW: I think adding RIS to AutoYast would be a nice feature in general. We are trying to consolidate our zypper config for all our linux systems. So editing the AutoYaST.XML each time we change/add repos to keep up-to-date with already-installed systems is an overhead we would like to get rid of by using RIS in the installation as well. Best regards, Joschi Brauchle On 07/03/2012 05:02 PM, Uwe Gansert wrote:
On 03.07.2012 12:15, Joschi Brauchle wrote:
So I tried that (creating a service file under /etc/zypp/services.d in the installation system from a pre-script) and it does not seem to be considered ...
pre-scripts run too late. The package resolver is already initialized then. If you use 12.1 (I'm afraid your are using 11.4), then you can trigger a restart of yast with a pre-script. So you can create the file with a pre-script, then trigger a yast-restart and then the resolver should be reinitialized.
If you are using 11.4, you can try to put the config file into a DUD. Or try this:
cd inst-source-of-11.4 mkdir -p linux/suse/i386-11.4/inst-sys/etc/zypp/services.d
and copy the config file there. Then it should be loaded too into the inst-sys (beware of the architecture in the path).
The mkdir/cp workaround works only on inst-sources that are mounted. Not on ftp or http(s) inst-sources. The driverupdate file always works.
-- Dipl.-Ing. Joschi Brauchle, M.S. Institute for Communications Engineering (LNT) Technische Universitaet Muenchen (TUM) 80290 Munich, Germany Tel (work): +49 89 289-23474 Fax (work): +49 89 289-23490 E-mail: joschi.brauchle@tum.de Web: http://www.lnt.ei.tum.de/