Login
You're viewing the y.diskcat.com public feed.
  • Snep :floofHappy: @40C3snep
    Mar 28, 2025, 4:23 AM

    @Toble_Miner I'm currently trying with a bare kernel and a hand-assembled BusyBox initramfs, though a minimum viable kernel with nothing but script and binary execution enabled and the console on ttyS0, compressed with LZMA (the most effective it seems) is already nearly 700k, not leaving alot of space for adding net support, PCI NIC modules, netfilter and all required user space programs and libraries :neocat_laugh_sweat:

    I might take a peek at how OpenWRT configures their X86 kernel!

    💬 1🔄 0⭐ 0

Replies

  • DrScripttdrscriptt@oldbytes.space
    Apr 1, 2025, 1:33 AM

    @snep @Toble_Miner i suspect compiling the NIC drivers in kernel will use less disk space than the modules themselves.

    Plus you can omit commands for managing modules.

    💬 1🔄 0⭐ 1
  • Snep :floofHappy: @40C3snep
    Apr 1, 2025, 5:58 AM

    @drscriptt @Toble_Miner Oh that's what I did, yeah, I knew including loadable module support would not only make the kernel bigger but also potentially the embedded initramfs archive, if modules were included in it.
    Pretty sure right now I'm getting such a solid XZ compression of both kernel and initramfs due to there being a lot of shared code in each one respectively, modules and the kernel in the bzImage and a lot of similar chunks in the statically compiled+stripped binaries in the initramfs

    💬 1🔄 0⭐ 1
  • Snep :floofHappy: @40C3snep
    Apr 1, 2025, 6:02 AM

    @drscriptt @Toble_Miner In the end, I did actually squeeze a working iptables binary in there, even if it pretty much only does the bare basics + CONNTRACK and NAT extensions, a wg binary plus included kernel module for Wireguard tunnels and bunch of BusyBox applets, mostly for networking like udhcpc/d, ip commands and telnet, currently with still ~20k free! I'd call it a successful experiment :neocat_blep:

    💬 1🔄 0⭐ 2
  • 💬 0🔄 0⭐ 1