vyatta-cfg-system.git/scripts, branch debian/0.20.29Vyatta 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.20.292012-09-05T21:13:12+00:00Merge branch 'pacifica' of git.vyatta.com:/git/vyatta-cfg-system into pacifica2012-09-05T21:13:12+00:00John Southworthjohn.southworth@vyatta.com2012-09-05T21:13:12+00:00urn:sha1:9d9593dc1594196995d038fcb2a9a71ec1c5d9a5Bugfix 83262012-09-05T21:04:30+00:00John Southworthjohn.southworth@vyatta.com2012-09-05T21:04:30+00:00urn:sha1:e2811040b1b6bf1e94f1878ade872dfef3cdf0ea
Fix password change script save function to work as it does in
vyattacfg.
Fix empty substitution on 'plaintext-password ""' causing script error.
Configure logrotate to maintain log file ownership2012-09-05T01:28:12+00:00James Davidsonjames.davidson@vyatta.com2012-09-05T01:28:12+00:00urn:sha1:288ab75d4f2aed39e8993d82f127e6e9dc16b973
logrotate needs the create config option so that it keeps the
original log file's permissions and ownership.
Fixes bug 8240
Bugfix 82902012-09-04T23:36:24+00:00John Southworthjohn.southworth@vyatta.com2012-09-04T23:36:24+00:00urn:sha1:918bd40d3e3f238a800b1486f70e2d5ee1d71a72
Don't allow default password to persist after first boot.
Due to the numerous ways a user can get a vyatta system this required
a lot of changes.
1. Don't allow a user to set a password to 'vyatta' after first login,
but allow it on the initial boot otherwise the system will have no
user.
2. Don't allow the password to be set to vyatta in installer.
3. Force password change on first login. under the following
conditions:
3.a. User is an admin level user. Operators do not have the abillity
to change the config so they can't change passwords. Allow 'vyatta' to
be the password until an admin logs in.
3.b. This is not the livecd, its silly to force a password change
before install.
Bugfix 6967: Test if an address is already applied to an interface before attempting to apply it2012-08-31T00:32:44+00:00John Southworthjohn.southworth@vyatta.com2012-08-31T00:32:44+00:00urn:sha1:8faaec7b1b9bd034449348b693c5216e349a04ecForce Xen installs to use ext3 without write barriers2012-08-29T17:48:08+00:00John Southworthjohn.southworth@vyatta.com2012-08-29T17:48:08+00:00urn:sha1:1867ce76ef780666982434f9f41fab383f8fbfa5
In oxnard our Xen images used ext3 without write barriers. This patch is
a workaround for bug 8303. The goal of this patch is to provide a workable
solution that is no worse than our previous behavior until Xenserver has
the write barrier fix available in Xen integrated.
Revert "Write barriers don't work on all devices, disable them"2012-08-28T22:46:07+00:00John Southworthjohn.southworth@vyatta.com2012-08-28T22:46:07+00:00urn:sha1:3e9f0b15e325e0c562a4aac983c9b702efc92562
This reverts commit f344e975d1b0eb489af7fb2d2f22168bc465b1de.
Write barriers don't work on all devices, disable them2012-08-28T20:36:49+00:00John Southworthjohn.southworth@vyatta.com2012-08-28T20:36:49+00:00urn:sha1:f344e975d1b0eb489af7fb2d2f22168bc465b1deUse hash map of addresses to interfaces2012-06-22T22:51:16+00:00Stephen Hemmingershemminger@vyatta.com2012-06-22T19:19:08+00:00urn:sha1:90b51b30aa19ecdc02b71e5c75f9a5cc4f215756
Other part of fix for Bz 8171
Create a hash of address => interfaces in configuration
and use it during address commit check.
Remove unused creation of list of current addresses.
This might speed boot with large number of interfaces.
Since the hash is made once per interface rather than
multiple times, it might be faster because of that as well.
Allow USB console in Grub setup2012-06-12T22:04:40+00:00Stephen Hemmingershemminger@vyatta.com2012-06-12T22:04:40+00:00urn:sha1:f9dc6e9bd279cb918f859a0bf52cc585ac64de28
Bug 7724