@Crab said: Now more interesting question would be that how small you can actually make them both while still maintaining the features you really need. That will require quite a bit of trial and error with the kernel compilation parameters but could be a fun exercise.
This is what I done for the Toshiba Click Mini but is much simpler when you target just one platform. (I can never understand why Wi-Fi drivers/modules are included in server builds.)
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural. It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
@Crab said: Now more interesting question would be that how small you can actually make them both while still maintaining the features you really need. That will require quite a bit of trial and error with the kernel compilation parameters but could be a fun exercise.
This is what I done for the Toshiba Click Mini but is much simpler when you target just one platform. (I can never understand why Wi-Fi drivers/modules are included in server builds.)
They weren't always. You used to get a basic kernel with hardware support and had to create your own config and build from there. WiFi really messed things up because hardware now isn't expected to have ethernet (or a cheap USB NIC for installation). It's possible to pare down kernels pretty extreme. I built a very base QEMU VirtIO only kernel that ran on a 64MB VPS with nearly 48MB free with full networking, thttpd and dropbear sshd. It wasn't great for much, but it did give me a place to build a compatible script for Hetrix before Virmach's monitor went insane and kept shutting it down after I got sick of fighting it and literally overwrote the entire 4GB of storage with NOPs so it'd chew through all of that before it died. Still had to beg them to remove it because I got sick of the incessant messages.
Comments
This is what I done for the Toshiba Click Mini but is much simpler when you target just one platform. (I can never understand why Wi-Fi drivers/modules are included in server builds.)
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural.
It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
They weren't always. You used to get a basic kernel with hardware support and had to create your own config and build from there. WiFi really messed things up because hardware now isn't expected to have ethernet (or a cheap USB NIC for installation). It's possible to pare down kernels pretty extreme. I built a very base QEMU VirtIO only kernel that ran on a 64MB VPS with nearly 48MB free with full networking, thttpd and dropbear sshd. It wasn't great for much, but it did give me a place to build a compatible script for Hetrix before Virmach's monitor went insane and kept shutting it down after I got sick of fighting it and literally overwrote the entire 4GB of storage with NOPs so it'd chew through all of that before it died. Still had to beg them to remove it because I got sick of the incessant messages.
My pronouns are like/subscribe.