On Sun, Oct 07, 2012 at 12:17:22PM +0100, Frank Murphy wrote: > On 07/10/12 10:21, Daniel Landau wrote: > >What can I do to fix my system? > Reinstall, and then leave things alone. That's really not a very friendly suggestion. Traditionally, Linux-based operating systems are fun to work with because you can mess around and when you break things, you can find what went wrong, you can usually find a good reason and even if you can't repair it, you can understand exactly what you screwed up. So, how can Daniel find exactly what is making this system fail to boot? Will it be logged somewhere even though journald is failing to start? Is there a way to turn on more helpful debugging output? -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm@xxxxxxxxxxxxxxxxx> -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
