On 10/07/2012 09:22 AM, Matthew Miller wrote:
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?
I myself cannot think of a way to get journald to start.....unless
you're talking "command line" stuff.....maybe there's some switch?...or
command that will allow him to get to the point where he can select
services that he wants to run upon boot-up? I don't know because I'm
still a noobie.....but if I were going to give a "friendly" suggestion
it would be something along those lines....I also wouldn't like to be
given advice such as that.....but SOMETIMES....it's the ONLY advice that
can be given?....as I myself have been told that a time or
two.....hmmm....is there somewhere I can go to find command line stuff
that would allow me to check / start / stop services upon booting up?
Besides the "Man Pages" that I wouldn't be able to access because I
wouldn't be able to boot up?....
EGO II
--
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
