<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyatta-cfg-system.git/scripts/install/install-postinst-new, branch helium</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=helium</id>
<link rel='self' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/atom?h=helium'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/'/>
<updated>2017-09-14T12:01:29+00:00</updated>
<entry>
<title>vyatta-cfg-system: ensure grub is installed to the raid slave members</title>
<updated>2017-09-14T12:01:29+00:00</updated>
<author>
<name>Alex Harpin</name>
<email>development@landsofshadow.co.uk</email>
</author>
<published>2015-02-28T14:50:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=0e52d7cc7cf0b4bead4b7e250f514e1501ed627e'/>
<id>urn:sha1:0e52d7cc7cf0b4bead4b7e250f514e1501ed627e</id>
<content type='text'>
When the system is installed in a raid configuration, grub is installed
to the raid device instead of to the individual slave drives, resulting
in a failure to boot after installation.  This commit identifies the
slave drives and ensures grub is installed to all of them (rather than
just the primary), resulting in a system that will boot following a
primary drive failure.

Bug #106 http://bugzilla.vyos.net/show_bug.cgi?id=106
</content>
</entry>
<entry>
<title>Update default user in installer script.</title>
<updated>2013-10-22T04:33:19+00:00</updated>
<author>
<name>Daniil Baturin</name>
<email>daniil@baturin.org</email>
</author>
<published>2013-10-22T04:33:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=a24008a70df0a6a15741a7d12f56429b330a21df'/>
<id>urn:sha1:a24008a70df0a6a15741a7d12f56429b330a21df</id>
<content type='text'>
</content>
</entry>
<entry>
<title>md: don't start unless needed</title>
<updated>2011-12-02T22:44:24+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>shemminger@vyatta.com</email>
</author>
<published>2011-12-02T22:44:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=e8c8ebfc74203309871d4f291a378565f7ca4181'/>
<id>urn:sha1:e8c8ebfc74203309871d4f291a378565f7ca4181</id>
<content type='text'>
Don't start RAID (md) unless root device is configured for RAID.
</content>
</entry>
<entry>
<title>Bugfix 7502: Get "add system image" to work on Xen</title>
<updated>2011-10-13T00:13:27+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2011-10-13T00:13:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=1f3e23f7147ef23f338788a223f8a5901546866a'/>
<id>urn:sha1:1f3e23f7147ef23f338788a223f8a5901546866a</id>
<content type='text'>
This fix solves the problem with indirection.  We introduce a symlink
in /live/image/boot pointing to the current default system image.  The
pygrub config file in /boot/grub/menu.lst points to the kernel and
initrd files in the default image by using this symlink in the
pathname.

Every time we add, delete or change the default system image, we need
to change this symlink to point to the new default image.
</content>
</entry>
<entry>
<title>Bugfix 7488: Configure Xen PV console hvc0 in Vyatta config file.</title>
<updated>2011-09-02T01:02:09+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2011-09-02T01:02:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=f4edc32a5846f617be9781e52891be5617fd0595'/>
<id>urn:sha1:f4edc32a5846f617be9781e52891be5617fd0595</id>
<content type='text'>
Previously, the install-image program was adding a line to
/etc/inittab in the image being installed.  This change adds a console
entry to the Vyatta config file instead.  Because of that entry, the
system automatically generates a console entry for hvc0 in
/etc/inittab at boot time.

I also removed the code in install-image that added a line to
/etc/fstab to mount /proc/xen.  This is no longer necessary because
the /etc/init.d/xe-linux-distribution startup script now mounts
/proc/xen.
</content>
</entry>
<entry>
<title>Bugfix 7469:  Add support for installing onto Xen</title>
<updated>2011-08-31T22:05:12+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2011-08-31T22:05:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=e08feca7a8248ad34425aadada3b65c03adac787'/>
<id>urn:sha1:e08feca7a8248ad34425aadada3b65c03adac787</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bugfix 7350: Allow default config.boot to be selected as config file.</title>
<updated>2011-08-17T22:03:51+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2011-08-17T22:03:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=ec24d3c1bf563e0a14e2c36146a3071fed1756b1'/>
<id>urn:sha1:ec24d3c1bf563e0a14e2c36146a3071fed1756b1</id>
<content type='text'>
Previously, the user could only select the running config file, which
includes any changes the user may have made and saved, plus system
generated changes such as the MAC addresses of ethernet interfaces.
This change allows them to select that file or the system's default
config file.
</content>
</entry>
<entry>
<title>Allow user to name system images when installing them.</title>
<updated>2010-04-30T22:45:44+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2010-04-30T22:45:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=c634b7d41c241a9b033e16ff32ba26a6d99bc227'/>
<id>urn:sha1:c634b7d41c241a9b033e16ff32ba26a6d99bc227</id>
<content type='text'>
Now we ask the user what they would like to name an image when
they are installing.  The default answer is the same string used previously:
The Vyatta version string.
</content>
</entry>
<entry>
<title>Bugfix 5414: Use correct install root reference when copying back SSH keys.</title>
<updated>2010-03-08T22:16:53+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2010-03-08T22:16:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=f457da66e387d10a71ae823ce55e7a4c69f87ed2'/>
<id>urn:sha1:f457da66e387d10a71ae823ce55e7a4c69f87ed2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bugfix 5225: Include the OS version number in the grub menu entry.</title>
<updated>2010-02-08T20:02:18+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2010-02-08T20:02:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=3f6bb58b0f98f8ca9dd986f8f274906c33596083'/>
<id>urn:sha1:3f6bb58b0f98f8ca9dd986f8f274906c33596083</id>
<content type='text'>
</content>
</entry>
</feed>
