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.19.67 2011-05-05T00:24:31+00:00 2011-05-05T00:24:31+00:00 Stephen Hemminger shemminger@vyatta.com 2011-05-05T00:24:31+00:00 urn:sha1:85287b60ef922227e1a25eb04a3ed9bd16a1ece4 Need to pass correct offset for start of root partition 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. 2011-05-03T23:25:13+00:00 Stephen Hemminger shemminger@vyatta.com 2011-05-03T23:23:56+00:00 urn:sha1:535f1748b0b74f33a5bdc471be35490f1f005834 Bug 7032 (reprise) Since there are various forms of multi-queue naming, it is better to just go with the simplest pattern which is to take all the irq's of form ethX-... and sort them. 2011-05-02T23:39:54+00:00 Stephen Hemminger shemminger@vyatta.com 2011-05-02T22:28:56+00:00 urn:sha1:9aa70813c98ae360d4320dfdb6112b7a1e3b593b Bug 7032 Fix matchinging of irq's named 'eth0-TxRx-0'. And change the code to handle any form of IRQ naming of multiqueue that is eth0-xxx-0. 2011-04-30T17:31:48+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2011-04-30T17:31:48+00:00 urn:sha1:4829b46c2453e3f94409ce622e1faedf3d11b457 Parted has magic value '0%' which causes it to choose optimum alignment (2048 on most disks). 2011-04-30T16:48:39+00:00 Stephen Hemminger shemminger@vyatta.com 2011-04-29T18:33:32+00:00 urn:sha1:b2fcc3d68146716f4451e45d7dc86418b67781bb Redo Bug 7038 The previous change did nothing; the alignment option only reports alignment, it does not change values. Need to manually reserve space before root partition. 2011-04-28T23:55:52+00:00 Stephen Hemminger shemminger@vyatta.com 2011-04-28T23:55:52+00:00 urn:sha1:281164b2208ede1f99180ff5e192aede6db46858 Bug 7038 Align the created disk partition for both install-system and initial install-image. Note: can't fix existing systems where disk is already partitioned. They will just have to suffer with poor performance. 2011-04-20T21:18:22+00:00 Mohit Mehta mohit@vyatta.com 2011-04-20T21:18:22+00:00 urn:sha1:77992d4359019ec8f6cb8ec2bde603679a806db5 * added /config/scripts/vyatta-postconfig-bootup.script that gets called from /etc/rc.local. Users/Support can put in any workarounds in the script for unfixed bugs and enhancements that are not in Vyatta yet. Placing the script under /config makes sure that changes to the script will be preserved for the new image 2011-04-19T01:00:48+00:00 Mohit Mehta mohit@vyatta.com 2011-04-19T01:00:48+00:00 urn:sha1:4d5862053ef2f99d09507b2e9b702aca1229099a This script executes scripts lying in the following directory: /opt/vyatta/bin/sudo-users/check-params-on-reboot.d Scripts in check-params-on-reboot.d are intended for parameters that require a reboot to take effect after they are set/changed. Because of the reboot requirement, underlying value and related config paramter value can become out-of-sync in couple of cases: 1. change parameter value, don't save config, reboot. Underlying value is different than the value in config file. 2. install new image; when new image boots, underlying value is the default Vyatta shipped value not the value in config file. More info: http://bugzilla.vyatta.com/show_bug.cgi?id=6915#c1 This check-in also adds ipv6_disable_blacklist script in check-params-on-reboot.d to fix the above mentioned problem for 'system ipv6 disable' and 'system ipv6 blacklist' 2011-04-14T00:58:50+00:00 Mohit Mehta mohit@vyatta.com 2011-04-14T00:58:50+00:00 urn:sha1:90954826826a0c60c74d9fd8a6fa68994c13a519 to push users towards putting scripts in /config/scripts