vyatta-cfg-system.git/scripts/install/install-image-existing, branch debian/0.17.112 Vyatta system-level configuration templates/scripts (mirror of https://github.com/vyos/vyatta-cfg-system.git) https://git.amelek.net/vyos/vyatta-cfg-system.git/atom?h=debian%2F0.17.112 2010-07-28T09:42:52+00:00 Bugfix 5711: Don't allow special characters in image names. 2010-07-28T09:42:52+00:00 Bob Gilligan gilligan@vyatta.com 2010-07-28T09:42:52+00:00 urn:sha1:d3bb616ddd7d97455919dcd49e132f8d271bf38b Bugfix 5929: Preserve SSH host keys during image installation. 2010-07-28T02:47:00+00:00 Bob Gilligan gilligan@vyatta.com 2010-07-28T02:43:42+00:00 urn:sha1:55838e499f21a5d91e6d8a8a3d81ff02ec0f725c (cherry picked from commit 71b716b7f5e5df1dd4ea6e8a16c7f987381cab8c) Merge branch 'larkspur' of vm:git/vyatta-cfg-system into larkspur 2010-05-07T22:25:00+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-05-07T22:25:00+00:00 urn:sha1:a0af547a872633d12ad7bb4f0831bfa4e7296256 Preserve file attributes of root files 2010-05-07T22:03:46+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-05-07T22:03:46+00:00 urn:sha1:427ab38e9d8144b185e53f29504df36d48277ac4 Want to preserve labels and other attributes Add code to check digital signature of image files. 2010-05-04T00:19:15+00:00 Bob Gilligan gilligan@vyatta.com 2010-05-04T00:19:15+00:00 urn:sha1:83cca7053bba3181b451609fee641271b3b7adf3 In URL mode, we now check for a digital signature file. If one exists, we'll try to download it and check the signature. Allow user to name system images when installing them. 2010-04-30T22:45:44+00:00 Bob Gilligan gilligan@vyatta.com 2010-04-30T22:45:44+00:00 urn:sha1:c634b7d41c241a9b033e16ff32ba26a6d99bc227 Now we ask the user what they would like to name an image when they are installing. The default answer is the same string used previously: The Vyatta version string. Bugfix 5449: Maintain "console affinity" when adding a new image. 2010-03-19T01:03:10+00:00 Bob Gilligan gilligan@vyatta.com 2010-03-19T01:03:10+00:00 urn:sha1:b06a5a892c315999c1d0295668b37f6e3497c527 Use more reliable method for determining system version. 2010-03-09T01:36:22+00:00 Bob Gilligan gilligan@vyatta.com 2010-03-09T01:36:22+00:00 urn:sha1:81df5c53d7dd6e7d3869ce96b3febc172e21611b Bugfix 5360: Get name of image from correct source. 2010-03-08T22:50:43+00:00 Bob Gilligan gilligan@vyatta.com 2010-02-19T02:02:56+00:00 urn:sha1:11e6561d93f7c648a920a4451ce25d5c9b78fc85 The name of a system image is supposed to match the Vyatta version string. Previously, the install-image script determined the name of the image being installed by parsing a field in the Vyatta version file on the image being installed. But the format of that file has changed, and may change again the future, so it is not a good source of the Vyatta version string. The most accurate way to determine the Vyatta version string is to look up the debian package version string associated with the vyatta-version package on the image being installed. This changes the install-image script to get the system image name that way. (cherry picked from commit e1864411c77e688b1b67de40441550b1f1eba055) Bugfix 5240: Prevent re-installation of same version on running systems 2010-01-26T01:10:04+00:00 Bob Gilligan gilligan@vyatta.com 2010-01-26T01:10:04+00:00 urn:sha1:092fea186dee158c9b6545e8d1ee69945d998e8d Previously, it was possible in some cases to "add" a system image that would over-write the running image. This change fixes that by getting the version string of the running system from the kernel command line instead of the Vyatta version file. This string represents the actual directory name that holds the image, so is more reliable. Also previously, an attempt to "add" a system image that had the same version string as another image installed on the system (but was not the running image) would always succeed. This would completely over-write that image. Because of this destructive behavior, it deserves a confirmation question. This change prompts the user to see if they really want to do that before proceeding.