I did not notice the permission bug with content because I was testing with NFS which has no problem. With ftp/http, it looks different. Anas Suffin, Charles wrote:
Outstanding, Anas!!! Thank you so much for the rapid response and the correct fix for the problem. I'm sorry I wasn't able to try your new version of the script on Friday night when you published it, but I have had the opportunity today.
Now, after rebuilding the update/ directory with your script, when installation runs, the additional CD shows up correctly as "SUSE SLES Updates" and it lists "CD 1: 00:10" (rdesktop is small). After the install is completed, the rdesktop application is automatically installed (I added it with <package> to my XML file.
Apparently the incorrect permission of the content file created by the original script was indeed preventing the install source from being correctly utilized. I very much doubt I could've figured out how to set this up without the script (and your help), Anas.
Folks, one thing to note... If you want to supply a source package along with a binary package, you need to create an updates/suse/src/ directory and put the source RPM in that (*not* in the iX86/ or noarch/ directories). I consulted the /var/log/YaST2/y2log file to figure out why my source RPM was failing (my little contribution to this effort). With the source located in src/ YaST2 can find it!
Thanks! -- Charlie
-----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Friday, March 11, 2005 5:49 PM To: Suffin, Charles Cc: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] auto-installing with patched OS
Hi,
I just found out that the permission of the content file under updates/ is wrong, it should be world readable. (chmod a+r content)
I will update the script.
Anas
Suffin, Charles wrote:
Hi folks,
I used Anas' create_update_source.sh on my SLES9 installation source. It created an updates/ directory in that source, resulting in a directory structure that looks like this:
SLES9/ SUSE-CORE-Version-9/ SUSE-SLES-Version-9/ boot content control.xml media.1 updates/ <-- this was newly-created by the script, as expected yast/
After this, I followed the instructions in the script:
1. I moved my packages into SLES9/updates/suse/<arch> directories. 2. I cd into SLES9/updates/suse. 3. I ran /usr/bin/create_package_descr -x setup/descr/EXTRA_PROV
OK, so then I do an autoinstall from this source on a targe machine.
After the reboot, there is no sign of my package on the installed machine, and if I search for the package using YaST2 "Install and Remove Software" it is not found by its name.
I think I'm missing a step somewhere to cause the installation to actually install my package. What am I missing? Do I need to add a <package> line to the XML file? Do I need to do some more mucking with the installation source?
-- Charlie
-----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Tuesday, March 01, 2005 10:53 PM To: Mark Acosta Cc: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] auto-installing with patched OS
Hi, I have a script for doing this you might want to try, see
http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh
The script itself has some additional info on how to use it.
The script uses the multiple source feature known from SLES, it will register multiple sources and the latest version of packages available in the original source and the new source will be installed.
Give it a try and let me know if it works for you. any feedback is welcome. Anas
Mark Acosta wrote:
I need to autoinstall a patched 2.6.8-24.11-default kernel (including patched utils) for Suse 9.2. The stock kernel is 2.6.8-24.10-default, but I can't find out how to patch/update to 2.6.8-24.11-default. How is the best accomplished?
thanks, Mark