vyatta-cfg-system.git/scripts/install-system, branch debian/0.20.29 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 Bugfix 8290 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. Force Xen installs to use ext3 without write barriers 2012-08-29T17:48:08+00:00 John Southworth john.southworth@vyatta.com 2012-08-29T17:48:08+00:00 urn: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:00 John Southworth john.southworth@vyatta.com 2012-08-28T22:46:07+00:00 urn:sha1:3e9f0b15e325e0c562a4aac983c9b702efc92562 This reverts commit f344e975d1b0eb489af7fb2d2f22168bc465b1de. Write barriers don't work on all devices, disable them 2012-08-28T20:36:49+00:00 John Southworth john.southworth@vyatta.com 2012-08-28T20:36:49+00:00 urn:sha1:f344e975d1b0eb489af7fb2d2f22168bc465b1de Fix missing error (missing lecho) in install-system 2012-01-25T00:50:50+00:00 Stephen Hemminger shemminger@vyatta.com 2012-01-25T00:50:50+00:00 urn:sha1:07119bd476b7963fee55e1b5eb649edf25603910 Some statements were copy/pasted over from install-image. install-system does not use lecho, that is only used in install-image Make disk label if necessary 2012-01-20T23:36:25+00:00 Stephen Hemminger shemminger@vyatta.com 2012-01-20T23:36:25+00:00 urn:sha1:177fa685159523d2ef8bd9ad6447d28c3338e7e9 Bug 7732 Restore installation section that makes disk label. install-system: use sfdisk to find drive size 2012-01-03T19:04:26+00:00 Stephen Hemminger shemminger@vyatta.com 2012-01-03T19:04:26+00:00 urn:sha1:42c61e632a88446a425bf2e2f0ce3e0430e2f4bf Better than using parted which requires more parsing. md: don't start unless needed 2011-12-02T22:44:24+00:00 Stephen Hemminger shemminger@vyatta.com 2011-12-02T22:44:24+00:00 urn:sha1:e8c8ebfc74203309871d4f291a378565f7ca4181 Don't start RAID (md) unless root device is configured for RAID. Make ext4 the default file system type 2011-05-05T15:19:20+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2011-05-05T15:19:20+00:00 urn:sha1:82037c7e260d6e5c73f47162a14b4778629c53a8 Adjust root partition offset based on disk size 2011-05-04T02:53:15+00:00 Stephen Hemminger shemminger@vyatta.com 2011-05-02T18:30:53+00:00 urn:sha1:b6871cf68a0b32f191d864aac34e6622970a828a On tiny disks, then it doesn't make sense to waste space by offsetting root partition. On big disks, it doesn't hurt and it allows for running on SSD.