| Age | Commit message (Collapse) | Author |
|---|
|
|
|
do AWS-specific things.
|
|
|
|
|
|
upgrading to newer version of debian.
|
|
The init script was not running on boot because the init script
symlinks were not created in /etc/rcX.d for the runlevels: 2,3,4,5.
This fix runs the update-rc.d command in the is_amazon_ec2_ami
function, thus creating the required symlinks and also updating
/etc/init.d/.depends.on.start.
|
|
- grub.cfg is now correctly modified when installing on a VyOS AMI
- ec2-fetch-ssh-public-key init script still needs to be activated
if installing on a VyOS AMI. This is an outstanding issue which
needs to be addressed. See debian/vyatta-cfg-system.postinst.in.
|
|
- Check if installing on AWS EC2 platform via instance metadata.
- Configure GRUB correctly, so that boot messages are available
via instance's console.
- Add init.d script to fetch user's EC2 public key during boot.
|
|
|
|
|
|
|
|
During an image add, the default used to be to not save the current
configuration and continue with adding the image. Now the default is
to not continue.
Fixes bug 7964.
|
|
This fix solves the problem with indirection. We introduce a symlink
in /live/image/boot pointing to the current default system image. The
pygrub config file in /boot/grub/menu.lst points to the kernel and
initrd files in the default image by using this symlink in the
pathname.
Every time we add, delete or change the default system image, we need
to change this symlink to point to the new default image.
|
|
(cherry picked from commit d891558527fdc077b8c0b37c24cb8b17a2ae7043)
|
|
|
|
|
|
/opt/vyatta/etc/config
|
|
|
|
|
|
|
|
|
|
(cherry picked from commit 71b716b7f5e5df1dd4ea6e8a16c7f987381cab8c)
|
|
|
|
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.
|
|
|
|
|
|
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)
|
|
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.
|
|
|
|
|
