righttobeararm

Members
  • Content Count

    1
  • Joined

  • Last visited

  1. I kinda followed the advice here on an odroid c1, installed sysvinit* debs, checked that an inittab was present, edited boot.ini to include init=/lib/sysvinit/init as the last of bootargs, checked network.conf to feature the correct network setting, crossed fingers, rebooted, the touchscreen does not work but ssh does. Removed systemd and voila'. If you wonder why, I use systems on the road and I have already experienced all the possible breakages when you alter some conditions, compared to whatever worked at home. I want a system with a fixed boot order, with a good amount of fully tested code. Systemd can't even manage to close the ssh connection before rebooting, nice to have a terminal windows hanging because of that huh?