Pre-enabled Orca vs On-Demand Install: Default Kali Live Accessibility Trade-off

Answer to the Core Question

For a standard Kali Live USB, the safest default is to keep Orca disabled at boot. The additional 50‑100 MB of RAM and 2‑5 seconds of boot delay can noticeably impact heavy‑weight pentesting tools on low‑end hardware, while most users still have quick access to the accessibility menu to enable Orca when needed.

Why the Default Should Stay Minimal

• Performance‑critical workloads—Kali is often run on modest USB‑2 media or older laptops where every megabyte matters.
• Most users do not require a screen reader at every boot; the menu toggle is a lightweight, on‑demand activation.
• Pre‑loading Orca would still require the user to install the package to persist across reboots, so the “auto‑start” state is effectively transient.

On‑Demand Install Path Viability

Installing Orca with apt install orca works only when the live session has network connectivity and a sighted operator is present to run the command. In air‑gapped or isolated deployments this path fails, leaving visually impaired users without a screen reader.

Hybrid Boot‑Parameter Solution

A lightweight, non‑fragmenting compromise is to expose a boot‑time switch—e.g., orca=auto—that starts Orca only when the user explicitly requests it. This keeps the image minimal by default, yet offers a one‑click opt‑in that does not require a separate image or additional packages.

Practical Steps for a Hybrid Image

1. Add the parameter to the GRUB entry:

   # Edit /boot/grub/grub.cfg or create a custom entry in /etc/grub.d/40_custom
   menuentry "Kali Live (Accessibility)" {
       linux /live/vmlinuz boot=live orca=auto quiet splash
       initrd /live/initrd.img
   }
   

2. Rebuild GRUB:

   # update-grub
   

3. Boot with the new entry and press Tab (or e) to verify the orca=auto parameter is passed.
4. Verify that Orca starts only when you enable it in the accessibility menu; otherwise the session remains lightweight.

What If You Need a Fully Accessible Image

If your deployment environment is guaranteed to have network access and you prioritize immediate accessibility, you can pre‑install Orca in the live build:

1. Modify the live‑build config to include the orca package in the packages.list.chroot file.
2. Rebuild the ISO with lb build.
3. Boot; Orca will start automatically, but remember it still consumes the 50‑100 MB RAM hit.

Missing Diagnostic Detail

Could you confirm the typical RAM available on the target hardware (e.g., free -h output) and whether the environment is often air‑gapped? This will help refine whether the hybrid boot‑parameter approach is sufficient or a fully pre‑enabled image is warranted.