> What I don't understand is why you have a package which modifies<br>> menu.lst but doesn't provide it if one doesn't exist, but oh well.<br><br>E.g. we use Splashy in our HW devices. <br>To configure Splashy some values must be written manually in menu.lst as kernel's parameter.<br>
Our product deb packets have Splashy in dependences list and modifies menu.lst itself.<br>As we can see there is a problem occurs if menu.lst is absent<br><br>Thank you<br><br><div class="gmail_quote">2009/9/9 Michael Goetze <span dir="ltr"><<a href="mailto:mgoetze@mgoetze.net">mgoetze@mgoetze.net</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Alexey,<br>
<div class="im"><br>
> 1) to execute in instsoft.GRUB hook the commands:<br>
> fcopy /boot/grub/menu.lst<br>
> $ROOTCMD update-initramfs -k all -u<br>
> $ROOTCMD update-grub<br>
> (This provides that menu.lst exists and is configured.)<br>
<br>
</div>No - as you see from your error log, these commands don't exist yet in<br>
the chroot environment. You need to run them after the corresponding<br>
packages have been installed, of course.<br>
<div class="im"><br>
> 2) to remove file faiconfig/files/boot/grub/menu.lst/postinst to GRUB<br>
> script's directory and to comment<br>
> grub update command in it.<br>
> (This will install grub but not change menu.lst)<br>
<br>
</div>Sure, you just need to run grub-install at some point.<br>
<br>
What I don't understand is why you have a package which modifies<br>
menu.lst but doesn't provide it if one doesn't exist, but oh well...<br>
<br>
Regards,<br>
<font color="#888888">Michael<br>
</font></blockquote></div><br>