Re: Welcome to emergency mode!
On Mon, Feb 08, 2016 at 06:35:27PM -0500, Frank McCormick wrote:
> On 08/02/16 06:27 PM, Bob Holtzman wrote:
> >On Mon, Jan 11, 2016 at 10:32:43AM +0000, Brian wrote:
> >>On Mon 11 Jan 2016 at 00:51:24 -0500, Steve Matzura wrote:
> >>
> >>>On Sun, 10 Jan 2016 23:40:28 -0500, Gary wrote:
> >>>
> >>>>On 10/01/16 07:15 PM, Steve Matzura wrote:
> >>>>>After solving all my mount problems and changing from dynamic to
> >>>>There are lots of things that can go wrong, but if you had been booting
> >>>>normally, it's likely something you've done since the initial install.
> >>>
> >>>I could solve this in twenty minutes with a re-install. Really, this
> >>>is a brand-new do-nothing-as-yet test-bed system. No users will be
> >>>harmed by this process :-) If I'm not giving you all enough useful
> >>>info about what's wrong, and I'm sure I'm not, just say so and I'll do
> >>>it first thing in the morning.
> >>
> >>Access the systemd journal with 'journalctl'. If you are being thrown
> >>into emergency mode there must be something seriously wrong. Lines of
> >>priority ERROR and higher are colored red.
> >
> >As root journalctl produces a long list, tail journalctl produces
> >
> >"tail: cannot open ‘journalctl’ for reading: No such file or directory".
> >
> >Now I'm really confused. Any explanation?
> >
>
> I belive tail is designed for use with text files...which systemd journal
> isn't.
>
Then why does it produce text output when tail is run as root?
Read the first line of my post.
--
Bob Holtzman
A man is a man who will fight with a sword or
conquer Mt. Everest in snow. But the bravest of all
owns a '34 Ford and tries for six thousand in low.
Reply to: