it is a worse solution.

   If a system does not allow debugging failed boots, or debugging
   after boot when complex software like package managers and union
   filesystems fail (as they certainly will), it seems unlikely to be
   successful.  Bugs (or misuses or ...) are inevitable; users need to
   have the tools necessary to figure out what is wrong and repair it.

You can always use a serial line to debug the boot, or use a known
working system and debug the translators in a sub-hurd.  This is
really no different than having ext2fs, auth, proc, exec, password,
etc, crash due to bugs or misuse.


_______________________________________________
gnu-system-discuss mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnu-system-discuss

Reply via email to