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.20.29 2012-09-04T23:36:24+00:00 2012-09-04T23:36:24+00:00 John Southworth john.southworth@vyatta.com 2012-09-04T23:36:24+00:00 urn: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. 2012-01-03T19:01:46+00:00 Stephen Hemminger shemminger@vyatta.com 2012-01-03T19:01:46+00:00 urn:sha1:11b7290a75eefa9da5c08a25e3c17723be6a4e90 sfdisk is simpler, and safer for getting disk size. It doesn't require as much screen scraping and doesn't need disk label. 2011-09-02T01:02:09+00:00 Bob Gilligan gilligan@vyatta.com 2011-09-02T01:02:09+00:00 urn:sha1:f4edc32a5846f617be9781e52891be5617fd0595 Previously, the install-image program was adding a line to /etc/inittab in the image being installed. This change adds a console entry to the Vyatta config file instead. Because of that entry, the system automatically generates a console entry for hvc0 in /etc/inittab at boot time. I also removed the code in install-image that added a line to /etc/fstab to mount /proc/xen. This is no longer necessary because the /etc/init.d/xe-linux-distribution startup script now mounts /proc/xen. 2011-06-24T22:55:35+00:00 John Southworth john.southworth@vyatta.com 2011-06-24T22:55:35+00:00 urn:sha1:1bc15089f78fc0778be78448e43ad33fd05e1e55 2011-05-10T21:21:27+00:00 Michael Larson mike@vyatta.com 2011-05-10T21:21:27+00:00 urn:sha1:55e7248013601a6120d343fc6a345f0e0ae98cfb 2010-09-08T16:35:30+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-09-08T16:35:30+00:00 urn:sha1:84c8616cb9b8f3847f6a8581e49e92d02b335beb Add common shell function to convert to lower case. Part of Bug 6132 2010-03-12T16:18:09+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-03-12T16:12:04+00:00 urn:sha1:b97ce22691e1ffb34f2bc3638ea44a69baa052e4 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. 2010-03-09T19:06:22+00:00 Bob Gilligan gilligan@vyatta.com 2010-03-09T19:06:22+00:00 urn:sha1:4ab3e62397765f48eca5823bca5fbe5335177c78 2010-03-09T01:36:22+00:00 Bob Gilligan gilligan@vyatta.com 2010-03-09T01:36:22+00:00 urn:sha1:81df5c53d7dd6e7d3869ce96b3febc172e21611b 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)