<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyatta-cfg-system.git/scripts/system, branch debian/0.19.45</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.45</id>
<link rel='self' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/atom?h=debian%2F0.19.45'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/'/>
<updated>2011-03-01T18:56:16+00:00</updated>
<entry>
<title>Warn if attempting to force mask on multiqueue NIC</title>
<updated>2011-03-01T18:56:16+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>stephen.hemminger@vyatta.com</email>
</author>
<published>2011-03-01T01:55:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=6938b8bce001cca2d98d6b277d134c9e8e405271'/>
<id>urn:sha1:6938b8bce001cca2d98d6b277d134c9e8e405271</id>
<content type='text'>
Bug 6845
Warn (and ignore) attempt to assign IRQ directly on multiqueuej
NIC.
</content>
</entry>
<entry>
<title>Workaround Xen NIC address</title>
<updated>2011-02-25T19:20:58+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>stephen.hemminger@vyatta.com</email>
</author>
<published>2011-02-25T19:20:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=4f6faa2ba6510c01165b18ce8315cd7049a15783'/>
<id>urn:sha1:4f6faa2ba6510c01165b18ce8315cd7049a15783</id>
<content type='text'>
Bug 6837
Xen does not behave like normal hardware. It assigns a random MAC
address (with local bit set).
</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>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>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>Change for rsyslog reload</title>
<updated>2011-01-21T03:30:43+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>stephen.hemminger@vyatta.com</email>
</author>
<published>2011-01-21T03:23:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=5cd567e34183b13c69915cd2ba7bbdb72b857fee'/>
<id>urn:sha1:5cd567e34183b13c69915cd2ba7bbdb72b857fee</id>
<content type='text'>
Bug 6663
(cherry picked from commit fa7d81f125033b7ed4bd549eb6905918612a6877)
</content>
</entry>
<entry>
<title>Affinity script was failing to configure some queues of multi-queue NICs.</title>
<updated>2010-12-22T09:20:52+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2010-12-22T09:20:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=e3f943f6b1fc48d0fc7a8b71636b2441e62abdc7'/>
<id>urn:sha1:e3f943f6b1fc48d0fc7a8b71636b2441e62abdc7</id>
<content type='text'>
The problem was due to incorrect initialization of the $q and $cpu
variables.  Their initializations were reversed.
</content>
</entry>
</feed>
