Hi Erich, thanks for your quick answer.
> I've seen this only with old versions of "yume". Can you please check the > version of the yume package? Did you try installing OSCAR on the same machine > before, with older versions of OSCAR? Just guessing... So please post the > output of > rpm -qa | egrep 'yum|systemi|systemc|packman' We did it first, but then we made a totally new install with suse 10.0 and with the brandnew oscar. the rpm output: packman-depman-2.8-1 systeminstaller-oscar-x11-2.3.1-1 packman-depman-rpms-2.8-1 systemimager-common-3.7.5-1 systemimager-client-3.7.5-1 systemimager-i386boot-standard-3.7.5-1 systemimager-bittorrent-3.7.5-1 systemimager-server-3.7.5-1 systemimager-flamethrower-3.7.5-1 yume-2.4-1 systeminstaller-oscar-2.3.1-1 yum-2.4.0-3 systemconfigurator-2.2.7-12ef systemimager-i386initrd_template-3.7.5-1 > The image building process for suse is somewhat special, it first "bootstraps" > the image with a set of basic packages, then it installs the rest of > packages. If the bootstrapping was successful, you should not be getting the > "insserv" issues. Also please make sure before you start building the image > that the image directory doesn't exist! I will try it tomorrow again, because we did a few tries and so it is possible that the directory was already there. Greetings Sylvia ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Oscar-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-users
