Skip to content
DevMeme
2805 of 7590
EmbeddedSystems Post #3104 · source on Telegram

Getting a Root Shell on Everything is The Real Endgame

Description

A close-up photograph of a blue Nintendo 2DS handheld game console, but instead of a game, its screen displays a Linux command-line interface. The terminal shows the output of the 'neofetch' command, a popular CLI tool for displaying system information. The text confirms that a custom-built Linux distribution, 'Buildroot', is running on the device. Key system details are listed, such as 'Host: Nintendo 3DS (CTR)', 'Kernel: 5.10.0+', and 'Memory: 41MiB / 118MiB'. This image is a prime example of the 'homebrew' and hardware hacking community's spirit, where engineers and enthusiasts port operating systems to hardware that was never intended to run them. For experienced developers, this resonates as a fun, challenging feat of embedded systems engineering, pushing the boundaries of a closed, resource-constrained device just for the sake of it. The extremely limited RAM highlights the technical skill required to get a modern kernel running

Comments

7
Anonymous ★ Top Pick Sure, your app runs in a 16GB Kubernetes pod, but can you compile a kernel for a device with less memory than a single Chrome tab?
  1. Anonymous ★ Top Pick

    Sure, your app runs in a 16GB Kubernetes pod, but can you compile a kernel for a device with less memory than a single Chrome tab?

  2. Anonymous

    Ported Buildroot to a Nintendo 2DS: cold boot to root prompt in 5 s, 61 MiB RSS - meanwhile our “stateless” sidecar in prod claims it needs 4 GB just to say 200 OK; guess the real handheld toy is our infra budget

  3. Anonymous

    The same engineer who spent three weeks getting Linux to run on a GamePad is now explaining to the CTO why the production Kubernetes cluster is still running on Ubuntu 18.04

  4. Anonymous

    When your 3DS has better uptime than your production Kubernetes cluster and you realize the real 'embedded systems experience' was the friends we made along the way to getting neofetch running on a device with 128MB of RAM

  5. Anonymous

    Buildroot on a 3DS - the device tree fits in 128MB, meanwhile our dependency tree back at work needs a Kubernetes cluster just to render the same ASCII art

  6. Anonymous

    Two weekends of Buildroot, DTB spelunking, and framebuffer hacks just to run neofetch on a 3DS - peak embedded ‘hello world’

  7. Anonymous

    Firmware updates for amateurs; real devs run rolling-release Arch on hardware with less RAM than a 90s pager

Use J and K for navigation