Age | Commit message (Collapse) | Author |
|
|
|
Want to preserve labels and other attributes
|
|
In URL mode, we now check for a digital signature file. If one
exists, we'll try to download it and check the signature.
|
|
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.
|
|
|
|
|
|
Bug 5443
When running on HyperV, install-system appeared to hang because
although hda existed, it had no information so parted was prompting
for retry. Use the -s flag (never prompt) at all the places
in install-system/install-image where we don't want to have
user interaction.
|
|
|
|
|
|
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)
|
|
|
|
(cherry picked from commit 5ea1d90dbe42b0eefbc222b98b9b357b5676cb8b)
|
|
|
|
On image-based systems, the Vyatta configuration is mounted on /config and
can be found in the disk filesystem under
/boot/<image-name>/live-rw/config.
|
|
|
|
|
|
|
|
|
|
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.
|
|
This could fix Bug 5151
There was a typo in script that saved old config
|
|
If previous disk-based install is found, use config info from it. Otherwise
look for image-based installs. If multiple image-based installs are found,
let the user select which one to save the config information from.
|
|
|
|
|
|
|
|
|
|
|
|
Bug 5151
Part of previous change caused regression in saving config information.
Also mounts old config read-only to avoid any problems.
|
|
Debian build warnings on these files.
|
|
Similar to previous change to install-system
|
|
|
|
|
|
|
|
|