<feed xmlns='http://www.w3.org/2005/Atom'>
<title>alacerda/aports/main/syslinux/syslinux.trigger, branch master</title>
<subtitle>alacerda's aport tree
</subtitle>
<link rel='alternate' type='text/html' href='https://git-old.alpinelinux.org/user/alacerda/aports/'/>
<entry>
<title>main/syslinux: make trigger not fail on lxc</title>
<updated>2015-05-19T09:29:27+00:00</updated>
<author>
<name>Natanael Copa</name>
<email>ncopa@alpinelinux.org</email>
</author>
<published>2015-05-19T09:25:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git-old.alpinelinux.org/user/alacerda/aports/commit/?id=66417d5e0c7870c269104b633e9d82c4554a8380'/>
<id>66417d5e0c7870c269104b633e9d82c4554a8380</id>
<content type='text'>
on lxc we dont have the boot device available so extlinux will fail.
We cannot check for `openrc --sys` because apk run the trigger in chroot
and grsecurity will prevent openrc access /proc/1/environment.

So we simply add a --warn-only option and use that from trigger.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
on lxc we dont have the boot device available so extlinux will fail.
We cannot check for `openrc --sys` because apk run the trigger in chroot
and grsecurity will prevent openrc access /proc/1/environment.

So we simply add a --warn-only option and use that from trigger.
</pre>
</div>
</content>
</entry>
<entry>
<title>main/syslinux: dynamically generate /boot/extlinux.conf using a trigger on /boot</title>
<updated>2011-06-11T05:02:11+00:00</updated>
<author>
<name>William Pitcock</name>
<email>nenolod@dereferenced.org</email>
</author>
<published>2011-06-11T05:02:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git-old.alpinelinux.org/user/alacerda/aports/commit/?id=cddf77d67884c0c62ebbdfb9f0f0d2ae018f1c80'/>
<id>cddf77d67884c0c62ebbdfb9f0f0d2ae018f1c80</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
