Hey guys. I am using SLES9 and have setup a custom package selection in the installer. Pretty much in the suse/setup/descr directory I created another .sel file, linked it all in and it's working. I have a list of packages custom to that .sel file that install fine. However, I recently started adding packages to it that are for some reason not installing. These are packages that are already found in the suse CORE CDs. Some I added work fine, others do not. I added telnet and telnet-server to the list. Telnet installs fine, telnet-server does not. I have scanned the logs in /var/log/YaST and have not even found any references to the packages that are not getting installed. I don't understand why this is happening. Thanks, -Nick
On Wed, 2004-10-27 at 09:55, Nicholas DeClario wrote:
I have scanned the logs in /var/log/YaST and have not even found any references to the packages that are not getting installed. I don't understand why this is happening.
I've seen similarly weird results when reinstalling and the drive partition info isn't wiped beforehand. Set this in your autoinst.xml: <initialize config:type="boolean">true</initialize> or run something like DBAN (http://dban.sourceforge.net/) using the quick method to wipe out existing partition information before you reinstall. - Chris
I tried setting initialize to 'true', it was 'false'. I run 'dd if=/dev/zero of=/dev/hda bs=1k count=512' to blow away the partition table prior to installing to. None of this seems to have had any effect. Thanks, -Nick On Wed, 27 Oct 2004, Chris Carpinello wrote:
On Wed, 2004-10-27 at 09:55, Nicholas DeClario wrote:
I have scanned the logs in /var/log/YaST and have not even found any references to the packages that are not getting installed. I don't understand why this is happening.
I've seen similarly weird results when reinstalling and the drive partition info isn't wiped beforehand. Set this in your autoinst.xml:
<initialize config:type="boolean">true</initialize>
or run something like DBAN (http://dban.sourceforge.net/) using the quick method to wipe out existing partition information before you reinstall.
- Chris
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
I dont understand why this should have any effect at all. Please send me the logfiles, or send some more details on what you have done. Anas Nicholas DeClario wrote:
I tried setting initialize to 'true', it was 'false'. I run 'dd if=/dev/zero of=/dev/hda bs=1k count=512' to blow away the partition table prior to installing to. None of this seems to have had any effect.
Thanks, -Nick
On Wed, 27 Oct 2004, Chris Carpinello wrote:
On Wed, 2004-10-27 at 09:55, Nicholas DeClario wrote:
I have scanned the logs in /var/log/YaST and have not even found any references to the packages that are not getting installed. I don't understand why this is happening.
I've seen similarly weird results when reinstalling and the drive partition info isn't wiped beforehand. Set this in your autoinst.xml:
<initialize config:type="boolean">true</initialize>
or run something like DBAN (http://dban.sourceforge.net/) using the quick method to wipe out existing partition information before you reinstall.
- Chris
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
After looking into the log files.. Your selection file is wrong and results in a lot of missing dependencies which prevents packages from being installed. Just take a look at badlist in the log directory. All these deps have to be resolved. The other packages which are not installed usually get installed after the system has booted the first time because they are on CD2 and you only provided logs from the initial installation phase, so I can say nothing about. Anas Nicholas DeClario wrote:
Hey guys. I am using SLES9 and have setup a custom package selection in the installer. Pretty much in the suse/setup/descr directory I created another .sel file, linked it all in and it's working. I have a list of packages custom to that .sel file that install fine. However, I recently started adding packages to it that are for some reason not installing.
These are packages that are already found in the suse CORE CDs. Some I added work fine, others do not. I added telnet and telnet-server to the list. Telnet installs fine, telnet-server does not.
I have scanned the logs in /var/log/YaST and have not even found any references to the packages that are not getting installed. I don't understand why this is happening.
Thanks, -Nick
participants (3)
-
Anas Nashif -
Chris Carpinello -
Nicholas DeClario