| Age | Commit message (Collapse) | Author |
|---|
|
Other scripts depend on these directories
|
|
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)
|
|
|
|
|
|
* fix this for eth, eth.vif, bond, bond.vif interfaces
* also, bridge-group code for bonding interfaces wasn't changed
with commit ec080f99 that re-strucutred bridging code in eth and
eth.vifs to fix bug 4708. bridge-group code for bond and bond.vif
interfaces is now similar to the fix for 4708
|
|
The sshd file format has optional options; copy them to a
placeholder node and generate to authorized_keys
Better error message when wrong number of arguments.
|
|
Bug 5350
Need some changes to support DSA keys (Protocol V2).
Also add support for options in key file.
|
|
|
|
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.
|
|
die prints to standard error, so any interface failures show up
in error file during boot, rather than being lost in trace messages.
|
|
Bug 5331
|
|
The install-image program knows how to preserve the config files from
a previous image or disk-based installation. The install-system
program already knew how to preserve config files from a previous
disk-based installation. This change teaches it how to preserve
config files from a previous image installation.
|
|
No longer used in latest Vyatta kernel.
|
|
|
|
Network interfaces are discovered at boot time in non-deterministic
order, so their names are non-deterministic. The vyatta_net_name
script is responsible for ensuring that network interface names are
changed to match their Vyatta config file entry when a match based on
MAC address is found. With this change, when a match is not found, we
use the biosdevname tool to to find the canonical name for an
interface, then change the interface's name to that name. This
ensures that NICs are named in a deterministic and systemmatic fashion.
|
|
When URL was added, local file read got broken!
|
|
Fix help text (Bug 5254) and allow IPV6 static mapping (Bug 5298)
|
|
|
|
If user exists in NSS (LDAP, TACACS+) but not on local machine,
then it can not be changed with CLI. useradd will fail (user exists),
and usermod will fail (can't find user in passwd file).
Bug 5249
|
|
|
|
|
|
|
|
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.
|
|
Bug 5252
The boot script needs to restore default settings, and the
templates are then used to enable root access.
|
|
The problem is that IPV6 module is not loaded when sysctl's
are interpreted during boot, and we want to allow marking IPV6
disabled.
|
|
|
|
This could fix Bug 5151
There was a typo in script that saved old config
|
|
|
|
1. Move vyatta-sysctl.conf from rl-system.init to procps
This makes configuration happen early (before networking)
2. Do IPV6 configuration for address_flush in rl-system.init
(after IPV6 is loaded)
3. Cleanup shell code for ipv6_params:
* no sudo needed in startup scripts
* use cleaner iteration
|
|
|
|
Incorrect config level in script.
|
|
|
|
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 458
Add
service snmp trap-source <address>
wrapper for /etc/snmp/snmp.conf
|
|
Bug 3756
Allow setting trap communities and port values.
|
|
|
|
|
|
Bug 3811, 3806
Poll more frequently for link state traps and include more information.
|
