<feed xmlns='http://www.w3.org/2005/Atom'>
<title>live-boot.git/components/9990-main.sh, branch rolling</title>
<subtitle> (mirror of https://github.com/vyos/live-boot.git)
</subtitle>
<id>https://git.amelek.net/vyos/live-boot.git/atom?h=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/live-boot.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/live-boot.git/'/>
<updated>2025-09-19T01:37:14+00:00</updated>
<entry>
<title>T7836: move bind mount of /config to vyos-1x</title>
<updated>2025-09-19T01:37:14+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2025-09-16T17:07:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/live-boot.git/commit/?id=2971a8b4698e6f4ded2a1440f2c8ccd2d22bb078'/>
<id>urn:sha1:2971a8b4698e6f4ded2a1440f2c8ccd2d22bb078</id>
<content type='text'>
We are removing the bind mount construction from the initrd components,
as:
(1) it is not needed before initialization in the vyos-1x vyos-router script
(2) does not correctly update inodes on libc rename
(3) fails on the livecd (cf. /var/log/live/boot.log)
</content>
</entry>
<entry>
<title>check for raid so it wil be included in "find_livefs" function</title>
<updated>2017-03-16T14:37:09+00:00</updated>
<author>
<name>Kim</name>
<email>UnicronNL@users.noreply.github.com</email>
</author>
<published>2017-03-16T14:37:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/live-boot.git/commit/?id=e28be47381418cd49f690d0247ad9ecd1794b199'/>
<id>urn:sha1:e28be47381418cd49f690d0247ad9ecd1794b199</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Do not generate error is folders exist.</title>
<updated>2016-02-01T19:05:09+00:00</updated>
<author>
<name>Kim Hagen</name>
<email>kim.sidney@gmail.com</email>
</author>
<published>2016-02-01T19:05:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/live-boot.git/commit/?id=775b3ace1c12328a993367cece20373de7f645da'/>
<id>urn:sha1:775b3ace1c12328a993367cece20373de7f645da</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add vyos config mounting script.</title>
<updated>2016-02-01T18:14:42+00:00</updated>
<author>
<name>Kim Hagen</name>
<email>kim.sidney@gmail.com</email>
</author>
<published>2016-02-01T18:14:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/live-boot.git/commit/?id=d35d8d1f937cbf764c67c2fc23b8dbaf18707984'/>
<id>urn:sha1:d35d8d1f937cbf764c67c2fc23b8dbaf18707984</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Dropping unionfs-fuse support:</title>
<updated>2015-01-04T20:47:53+00:00</updated>
<author>
<name>Daniel Baumann</name>
<email>mail@daniel-baumann.ch</email>
</author>
<published>2015-01-04T20:16:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/live-boot.git/commit/?id=ec9bd07c900e13d606445518a87e0326902d5815'/>
<id>urn:sha1:ec9bd07c900e13d606445518a87e0326902d5815</id>
<content type='text'>
  * unionfs-fuse itself has been always very buggy for us.
  * unionfs-fuse code in live-boot as been experimental at best.
  * the FUSE implementation is horribly slow due to the nature of
    FUSE (~10min to boot a live system with unionfs-fuse compared
    to &lt;&lt;1min with aufs).
  * and last but not least, there's overlay in kernel mainline now.
</content>
</entry>
<entry>
<title>Supporting resolvconf in the squashfs.</title>
<updated>2014-03-29T13:29:40+00:00</updated>
<author>
<name>Evgeni Golov</name>
<email>evgeni@grml.org</email>
</author>
<published>2014-03-29T13:28:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/live-boot.git/commit/?id=e31d7cec9e48617a7509bab38cac32958f431d4e'/>
<id>urn:sha1:e31d7cec9e48617a7509bab38cac32958f431d4e</id>
<content type='text'>
When resolvconf is used in the squashfs, /etc/resolv.conf is a symlink
to the generated version. Depending on the size of the squashfs and
other factors, sometimes we try to write to /etc/resolv.conf while it
still points to nirvana, as resolvconf did not generate it yet.

Instead of being racy and writing to a file which will be regenerated
anyways, let's detect resolvconf and write to its base file instead.

Initial detection idea by Mika Prokop &lt;mika@grml.org&gt;
</content>
</entry>
<entry>
<title>Dropping really_export dead code.</title>
<updated>2013-06-24T20:12:40+00:00</updated>
<author>
<name>Daniel Baumann</name>
<email>mail@daniel-baumann.ch</email>
</author>
<published>2013-06-24T20:12:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/live-boot.git/commit/?id=3da00deab98dc5999f4583d05d164e2549efa6b2'/>
<id>urn:sha1:3da00deab98dc5999f4583d05d164e2549efa6b2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Reorganizing components in source tree.</title>
<updated>2013-06-24T19:38:08+00:00</updated>
<author>
<name>Daniel Baumann</name>
<email>mail@daniel-baumann.ch</email>
</author>
<published>2013-06-24T19:38:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/live-boot.git/commit/?id=a331218718282c5496ff062a0f6aa55908224862'/>
<id>urn:sha1:a331218718282c5496ff062a0f6aa55908224862</id>
<content type='text'>
</content>
</entry>
</feed>
