The signature-handling override for additional packages as specified in the autoyast doco section 4.5.4 doesn't work for me. I specify all four items (accept_unsigned_file, accept_file_without_checksum, accept_verification_failed, and accept_unknown_gpg_key) as "true" in my autoinst.xml in hope of avoiding the confirmation prompt. The confirmation prompt still appears. Anyone? R /Lars Stavholm
On Sunday 11 June 2006 17:52, Lars Stavholm wrote:
The signature-handling override for additional packages as specified in the autoyast doco section 4.5.4 doesn't work for me. I specify all four items (accept_unsigned_file, accept_file_without_checksum, accept_verification_failed, and accept_unknown_gpg_key) as "true" in my autoinst.xml in hope of avoiding the confirmation prompt. The confirmation prompt still appears.
Anyone?
That's a bug. Will be fixed in RC3 of SLES10 -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Uwe Gansert wrote:
On Sunday 11 June 2006 17:52, Lars Stavholm wrote:
The signature-handling override for additional packages as specified in the autoyast doco section 4.5.4 doesn't work for me. I specify all four items (accept_unsigned_file, accept_file_without_checksum, accept_verification_failed, and accept_unknown_gpg_key) as "true" in my autoinst.xml in hope of avoiding the confirmation prompt. The confirmation prompt still appears.
Anyone?
That's a bug. Will be fixed in RC3 of SLES10
And what about SuSE Linux 10.1 (which we are using at the moment)? BTW, there's another annoying popup that shows up for some of our machines, stating something like "These disks have a raid controller that isn't guaranteed to work...". Any chance of getting rid of that one in a supposedly unattended installation (i.e. autoyast) as opposed to manual installation? It's just that we've figured out all we need now, especially with the latest (10.1) release, we have dynamic detection of disks and disk types (IDE/(S)ATA/SCSI) using the modified.xml feature, dynamic partitioning on all (heterogenous) machine types, addon rpm's in a nice separated (and therefore more maintainable) way thanks to the latest add_on_products feature. All that's preventing us from having truly unattended installations is the two popups mentioned above, both need confirmation, i.e. human intervention. Not a showstopper, but definitely annoying when everything else works just great. R/Lars
Lars Stavholm wrote:
Uwe Gansert wrote:
On Sunday 11 June 2006 17:52, Lars Stavholm wrote:
The signature-handling override for additional packages as specified in the autoyast doco section 4.5.4 doesn't work for me. I specify all four items (accept_unsigned_file, accept_file_without_checksum, accept_verification_failed, and accept_unknown_gpg_key) as "true" in my autoinst.xml in hope of avoiding the confirmation prompt. The confirmation prompt still appears.
Anyone?
That's a bug. Will be fixed in RC3 of SLES10
And what about SuSE Linux 10.1 (which we are using at the moment)?
BTW, there's another annoying popup that shows up for some of our machines, stating something like "These disks have a raid controller that isn't guaranteed to work...". Any chance of getting rid of that one in a supposedly unattended installation (i.e. autoyast) as opposed to manual installation?
It's just that we've figured out all we need now, especially with the latest (10.1) release, we have dynamic detection of disks and disk types (IDE/(S)ATA/SCSI) using the modified.xml feature, dynamic partitioning on all (heterogenous) machine types, addon rpm's in a nice separated (and therefore more maintainable) way thanks to the latest add_on_products feature. All that's preventing us from having truly unattended installations is the two popups mentioned above, both need confirmation, i.e. human intervention. Not a showstopper, but definitely annoying when everything else works just great.
And here's another one: on occasion (depending on software selections) I get a popup in the middle of the installation saying something like "The diskspace is nearly full, do you really want to continue?". The installation then stops awaiting user input. Closer investigation of the partitions shows that there's plenty of space. R/Lars
On Tuesday 13 June 2006 08:35, Lars Stavholm wrote:
And here's another one: on occasion (depending on software selections) I get a popup in the middle of the installation saying something like "The diskspace is nearly full, do you really want to continue?". The installation then stops awaiting user input. Closer investigation of the partitions shows that there's plenty of space.
fixed for SLES10 RC3 -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
On Tuesday 13 June 2006 01:13, Lars Stavholm wrote:
And what about SuSE Linux 10.1 (which we are using at the moment)?
I think I'll create an update for the root image of 10.1 when SLES10 is out. In that root image, I'll fix some bugs in yast.
BTW, there's another annoying popup that shows up for some of our machines, stating something like "These disks have a raid controller that isn't guaranteed to work...". Any chance of getting rid of that one in a supposedly unattended installation (i.e. autoyast) as opposed to manual installation?
I talked to our storage guru about that. He said, if you wipe out the last percent of the harddisc (via dd), the warning should go away. There are some signatures stored there on the disc and if you erase those, the warning will not appear. Of course this only helps you if you have to install the same machine more than once with autoyast. You have to erase those signatures one time and will then never be annoyed again by the warning. If you install only once anyway, that will not help you of course.
All that's preventing us from having truly unattended installations is the two popups mentioned above, both need confirmation, i.e. human intervention. Not a showstopper, but definitely annoying when everything else works just great.
the signature popup can only be fixed by a yast bugfix or by a signed installation source. I'll fix that in the update for the root image of 10.1 too. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Uwe Gansert wrote:
On Tuesday 13 June 2006 01:13, Lars Stavholm wrote:
And what about SuSE Linux 10.1 (which we are using at the moment)?
I think I'll create an update for the root image of 10.1 when SLES10 is out. In that root image, I'll fix some bugs in yast.
OK, thanks, sounds good, looking forward to that one.
BTW, there's another annoying popup that shows up for some of our machines, stating something like "These disks have a raid controller that isn't guaranteed to work...". Any chance of getting rid of that one in a supposedly unattended installation (i.e. autoyast) as opposed to manual installation?
I talked to our storage guru about that. He said, if you wipe out the last percent of the harddisc (via dd), the warning should go away. There are some signatures stored there on the disc and if you erase those, the warning will not appear. Of course this only helps you if you have to install the same machine more than once with autoyast. You have to erase those signatures one time and will then never be annoyed again by the warning. If you install only once anyway, that will not help you of course.
Sounds OK, I'll try it, thanks. It'll be handy for our test machines anyways (which we redo over and over again).
All that's preventing us from having truly unattended installations is the two popups mentioned above, both need confirmation, i.e. human intervention. Not a showstopper, but definitely annoying when everything else works just great.
the signature popup can only be fixed by a yast bugfix or by a signed installation source.
Yeah, I hear you, that would be the proper thing todo. I'll get around to signing our packages one of these days:)
I'll fix that in the update for the root image of 10.1 too.
Thanks for that. /Lars
participants (2)
-
Lars Stavholm -
Uwe Gansert