<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyatta-cfg-system.git/scripts, branch debian/0.19.41</title>
<subtitle>Vyatta system-level configuration templates/scripts (mirror of https://github.com/vyos/vyatta-cfg-system.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyatta-cfg-system.git/atom?h=debian%2F0.19.41</id>
<link rel='self' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/atom?h=debian%2F0.19.41'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/'/>
<updated>2011-02-25T18:38:10+00:00</updated>
<entry>
<title>Change where ipv6 route table size is increased</title>
<updated>2011-02-25T18:38:10+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>stephen.hemminger@vyatta.com</email>
</author>
<published>2011-02-25T18:34:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=f62f7280611731fbd0f6a883a10e676a35518264'/>
<id>urn:sha1:f62f7280611731fbd0f6a883a10e676a35518264</id>
<content type='text'>
Can't do it early in boot because ipv6 module may not be loaded.
</content>
</entry>
<entry>
<title>Validate domain and host name</title>
<updated>2011-02-25T17:07:41+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>stephen.hemminger@vyatta.com</email>
</author>
<published>2011-02-25T17:07:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=6c9f83f6bcf081973f25c7564cc61ba07ae2cfd2'/>
<id>urn:sha1:6c9f83f6bcf081973f25c7564cc61ba07ae2cfd2</id>
<content type='text'>
Bug 6243
More complete validation of host name and domain name
</content>
</entry>
<entry>
<title>Don't set irq affinity if device is disabled</title>
<updated>2011-02-25T17:05:51+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>stephen.hemminger@vyatta.com</email>
</author>
<published>2011-02-25T17:05:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=b541f5ffa7bf1c6951e01ae4814e0cd38adc42d5'/>
<id>urn:sha1:b541f5ffa7bf1c6951e01ae4814e0cd38adc42d5</id>
<content type='text'>
Bug 6784
No point in trying to force affinity if device is offline.
</content>
</entry>
<entry>
<title>Handle Vmware mulitqueue naming convention</title>
<updated>2011-02-22T22:11:27+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>stephen.hemminger@vyatta.com</email>
</author>
<published>2011-02-22T22:11:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=018c1ac6286ad40d7fff612573a7efffafe0d480'/>
<id>urn:sha1:018c1ac6286ad40d7fff612573a7efffafe0d480</id>
<content type='text'>
Adapt to irq naming convention in 2.6.37 kernel for vmxnet3 driver.
</content>
</entry>
<entry>
<title>Handle case of device with no active IRQ</title>
<updated>2011-02-21T23:54:21+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>stephen.hemminger@vyatta.com</email>
</author>
<published>2011-02-21T23:54:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=78d24daefeab6e91f282044abb8930678434ea8c'/>
<id>urn:sha1:78d24daefeab6e91f282044abb8930678434ea8c</id>
<content type='text'>
Bug 6784
Disabled device has no IRQ, so don't change it.
</content>
</entry>
<entry>
<title>Use standard mechanism to start/stop snmp</title>
<updated>2011-02-18T18:55:50+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>stephen.hemminger@vyatta.com</email>
</author>
<published>2011-02-18T18:55:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=c8165a1a29572d7bf78d11c83afd18fff80a02f5'/>
<id>urn:sha1:c8165a1a29572d7bf78d11c83afd18fff80a02f5</id>
<content type='text'>
The net-snmp has snmpd.init script which is installed in standard
place. Invoke it with standard mechanism to avoid any security or
other problems. Also allows debugging snmpd by changing /etc/default/snmp.
</content>
</entry>
<entry>
<title>Bugfix 6773: Spread load of single-queue NICs across all CPUs.</title>
<updated>2011-02-03T08:06:08+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2011-02-03T08:06:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=c1eb2494559fb0f6ee2beecaedb2a415ff096056'/>
<id>urn:sha1:c1eb2494559fb0f6ee2beecaedb2a415ff096056</id>
<content type='text'>
The initial CPU selection function needs to take hyperthreading
into account.
</content>
</entry>
<entry>
<title>Bugfix 6156: Allow time for renaming to complete before running biosdevname</title>
<updated>2011-02-01T18:52:23+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2011-02-01T18:27:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=a85d727c301007fb6fff667e6899bcbc00d7b2be'/>
<id>urn:sha1:a85d727c301007fb6fff667e6899bcbc00d7b2be</id>
<content type='text'>
It appears that biosdevname can be confused if interface renaming is
being performed by other udev worker processes at the same time that
it is running.  Since vyatta_net_name does protect the body of its
code with a lock, we can be sure that no other renaming will be
started in other udev worker processes while this one is running in
vyatta_net_name.  But renaming being performed by other udev worker
processes that were triggered by previous executions of
vyatta_net_name may still be in progress.  This change gives any
interface renaming that was called for by previous invocations of
vyatta_net_name a chance to complete before we call biosdevname.
(cherry picked from commit 9dd41e8481e84bf80fcb0e9c3d7843c8a0b20059)
</content>
</entry>
<entry>
<title>Fix grammar error in help string.</title>
<updated>2011-02-01T00:18:25+00:00</updated>
<author>
<name>Robert Bays</name>
<email>robert@vyatta.com</email>
</author>
<published>2011-01-28T01:45:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=8965f3f255c98524923330627fb5f1c5e33cd122'/>
<id>urn:sha1:8965f3f255c98524923330627fb5f1c5e33cd122</id>
<content type='text'>
(cherry picked from commit a943568e64bca73bb2951e968d0cc752d72874ab)
</content>
</entry>
<entry>
<title>Fix Bug 6696 Internal error for release/renew dhcp interface under op mode</title>
<updated>2011-02-01T00:18:25+00:00</updated>
<author>
<name>Mohit Mehta</name>
<email>mohit@vyatta.com</email>
</author>
<published>2011-01-27T21:00:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=153247cdabaf3b980f9ebe1e50b9334a30d634dc'/>
<id>urn:sha1:153247cdabaf3b980f9ebe1e50b9334a30d634dc</id>
<content type='text'>
* do not execute config-mode actions when called from op-mode
(cherry picked from commit c385ddc400788eff46f10fea6b57b593607dc290)
</content>
</entry>
</feed>
