Subcategories

  • General Developer questions relating to FOG.
    386 Topics
    5k Posts
    K

    @Valer Hi Valer,

    You can see my tutorial on using Secure boot with Shim, and my thoughts on what 2.0 means for Secure Boot with FOG here: http://forums.fogproject.org/post/158170

  • Request a new feature to be implemented.
    632 Topics
    4k Posts
    Tom ElliottT

    @heix75 No.

    Not because it’s not a QOL improvement (it is) but because what you see in 1.5.x.x is NOT what is the end goal.

    If you want to see what the UX is moving toward install the version of FOG on working-1.6.

    You’ll understand (I hope), then, why I’m saying this.

  • Report a bug with FOG.
    1k Topics
    12k Posts
    Tom ElliottT

    @Valer Thanks for the report and the writeup, that’s a good catch. You’re right about the cause. Debian 13 dropped the sysv-rc-conf package since it’s fully on systemd now, so the installer chokes trying to apt-get it. We never actually use that tool on a systemd system anyway, it only ever got called on the old non-systemd paths, so it was just dead weight on Trixie.

    I pushed a fix to working-1.6. It leaves the package off the list on Debian 13 and up, and it also strips it out of a cached .fogsettings so an in-place upgrade doesn’t drag it back in. Older Debian keeps installing it like before so nothing changes there.

    If you want to get moving before you pull the update, you can either grab the latest working-1.6 and rerun the installer, or just open /opt/fog/.fogsettings and delete sysv-rc-conf from the packages line, then run the installer again. Either one gets you past it.

    Let me know if you hit anything else on Trixie.

89

Online

12.7k

Users

17.6k

Topics

156.7k

Posts