On Thu, Jul 11, 2013 at 5:22 PM, wrote:
> The way to go is to override the "bootloaders" directory
> Assuming your configuration tree lies in ~/live, create a
> ~/live/config/bootloaders/ directory. Then copy (cp -L to dereferences
> symbolic links) the /usr/share/live/build/bootloaders/isolinu
Daniel Baumann wrote:
> any file ending with the '.in' suffix will not get copied verbatim, but
> will have certain @...@ strings replaced.
That is what I expected to happen, but that is not what happened. As
I said in my initial post,
config/includes.binary/isolinux/isolinux.cfg.in was copied ve
On 07/11/2013 06:16 PM, Zack Weinberg wrote:
> Putting that in config/includes.binary/isolinux/isolinux.cfg.in causes it to
> be copied
> verbatim to binary/isolinux, which doesn't accomplish anything useful.
any file ending with the '.in' suffix will not get copied verbatim, but
will have certai
The way to go is to override the "bootloaders" directory
Assuming your configuration tree lies in ~/live, create a
~/live/config/bootloaders/ directory. Then copy (cp -L to dereferences symbolic
links) the /usr/share/live/build/bootloaders/isolinux/ directory in the newly
created "bootloaders" d
Hello,
this is not quite what the scripts are designed to do.
There are multiple cfg snippets and they are supposed to be fit
together so that live and installer are configured independently.
If you just wanted to wipe out the whole thing and write your you
could do that in binary hooks but in t
Suppose I want to wipe out the entire stock isolinux configuration and
replace it with something along the lines of
default live-@FLAVOUR@ auto
prompt 0
noescape 1
label live-@FLAVOUR@
linux @LINUX@
initrd @INITRD@
append @APPEND_LIVE@ noeject
... how would I accomplish this? Puttin
