Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If they can't debug it, they can find someone who can, and that skillset is, I can guarantee you, going to be far more widely available than Systemd debugging fu.

On which point, specifically: when Debian breaks during initrd execution, the system is dumped to a shell, "dash", a POSIX-compliant shell. It doesn't have all the niceties of bash, but it's usable.

When a Red Hat system breaks during initrd execution, the system shell doesn't handle terminal IO. You literally can't even fucking talk to the damned thing. It's a scripting-only shell.

The kicker: the RHEL initrd shell is larger than dash.

Guess which of these two systems is easier to troubleshoot / debug / rescue in a pinch?



    the system shell doesn't handle terminal IO
Does this help? http://en.gentoo-wiki.com/wiki/Initramfs#Job_Control

    the RHEL initrd
You haven't seen how this epic engineering artifact of wheel reinvention is exploding in your face. See http://lwn.net/Articles/506842/ Now try debug it with rd.debug and you will have debug info printed for debug info printing functions.


If you want bash instead of dash:

    dpkg-reconfigure -p low dash
Its that easy to get bash back...


I can live with dash. It's living without terminal IO that sort of puts a damper on things.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: