<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyatta-cfg-system.git/scripts/vyatta-raid-event, branch debian/0.17.18</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.17.18</id>
<link rel='self' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/atom?h=debian%2F0.17.18'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/'/>
<updated>2010-03-04T02:08:51+00:00</updated>
<entry>
<title>Bugfix 5404: Handle RAID re-sync on image-installed systems.</title>
<updated>2010-03-04T02:08:51+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2010-03-04T02:08:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=742350e958edc7950844f806d3a1fca3dfb8e02b'/>
<id>urn:sha1:742350e958edc7950844f806d3a1fca3dfb8e02b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bugfix: 3744</title>
<updated>2008-10-14T20:54:35+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2008-10-14T20:54:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=6a2393d8053ab9ff9651a6f9c3b243cced7e4439'/>
<id>urn:sha1:6a2393d8053ab9ff9651a6f9c3b243cced7e4439</id>
<content type='text'>
When a new member is added to a RAID group that holds the root filesystem,
we need to re-install grub so that the new disk will be bootable.  But this
can only be done after the RAID set has completed rebuilding.  Added mechanism
that uses the event notification infrastructure of "mdadm" to trigger
the re-installation of grub after the rebuild completes.
</content>
</entry>
</feed>
