Hi Michael,
> So why don't you just put appropriate options (kopt=splash etc.) in the
> menu.lst you fcopy to the target system?
As I understand NFSROOT is mounted as read only.
Can $FAI/files/boot/grub/menu.lst/GRUB be modified during FAI installation?
But it is a good method to create the corr
> What I don't understand is why you have a package which modifies
> menu.lst but doesn't provide it if one doesn't exist, but oh well.
E.g. we use Splashy in our HW devices.
To configure Splashy some values must be written manually in menu.lst as
kernel's parameter.
Our product deb packets have S
Michael,
Do I understand correctly the recipe?
1) to execute in instsoft.GRUB hook the commands:
fcopy /boot/grub/menu.lst
$ROOTCMD update-initramfs -k all -u
$ROOTCMD update-grub
(This provides that menu.lst exists and is configured.)
2) to remove file faiconfig/files/boot/grub/menu.lst/postinst
Hello.
We have a deb packet that modifies /boot/grub/menu.lst file.
But FAI ( we used config structure from example ) creates this file during
GRUB configuration after "instsoft" task is done.
We tried to call "fcopy -Uv /boot/grub/menu.lst" in instsoft.GRUB hook but
the menu.lst was overwritten b
Hello Michael,
Thank you for your help. We followed your suggestions with some modification
and it helps.
We can set repositories based on HW class. And we should be able to manage
version of package by adding package pin entry in /etc/apt/preferences/CLASS
when needed
Here what we did.
1) We used
Hello,
We are using FAI to install Debian on different PCs and devices and
met a problem that should be quite common but we couldn't find an easy or
obvious solution.
We have a core of stable packages that are used by any HW platform. But also
we need to install different versions of some packages
