On Sun, Oct 28, 2012 at 05:29:46PM +, Colin Guthrie wrote:
> 'Twas brillig, and Zbigniew Jędrzejewski-Szmek at 28/10/12 01:19 did
> gyre and gimble:
> > On Tue, Oct 23, 2012 at 04:58:46PM +0200, Lennart Poettering wrote:
> >> On Sun, 21.10.12 15:59, Andrey Borzenkov (arvidj...@gmail.com) wrote:
'Twas brillig, and Zbigniew Jędrzejewski-Szmek at 28/10/12 01:19 did
gyre and gimble:
> On Tue, Oct 23, 2012 at 04:58:46PM +0200, Lennart Poettering wrote:
>> On Sun, 21.10.12 15:59, Andrey Borzenkov (arvidj...@gmail.com) wrote:
>>
>>> Welcome to emergency mode. Use "systemctl default" or ^D to ent
On Tue, Oct 23, 2012 at 04:58:46PM +0200, Lennart Poettering wrote:
> On Sun, 21.10.12 15:59, Andrey Borzenkov (arvidj...@gmail.com) wrote:
>
> > Welcome to emergency mode. Use "systemctl default" or ^D to enter default
> > mode.
> > Give root password for login:
>
> systemd 195 will now also me
On Mon, 22.10.12 11:41, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> > Please note the version of systemd (v44) in openSUSE doesn't have all
> > the needed bits to always display on the screen why dependency failed
> > (and you end up in emergency mode). This is fixed with systemd 195
On Sun, 21.10.12 15:59, Andrey Borzenkov (arvidj...@gmail.com) wrote:
> Welcome to emergency mode. Use "systemctl default" or ^D to enter default
> mode.
> Give root password for login:
systemd 195 will now also mention "journalctl -b" in this
message. Originally this was only in the rescue mode
On Sun, Oct 21, 2012 at 03:13:22PM +0200, Frederic Crozat wrote:
> Le dimanche 21 octobre 2012 à 15:59 +0400, Andrey Borzenkov a écrit :
> > This issue comes up relatively often on openSUSE forums. Users
> > complaint that when system drops in emergency, there is nothing that
> > would explain user
Le dimanche 21 octobre 2012 à 15:59 +0400, Andrey Borzenkov a écrit :
> This issue comes up relatively often on openSUSE forums. Users
> complaint that when system drops in emergency, there is nothing that
> would explain user why it happened or what to do. Typical situation is
> https://bugzilla.n
This issue comes up relatively often on openSUSE forums. Users
complaint that when system drops in emergency, there is nothing that
would explain user why it happened or what to do. Typical situation is
https://bugzilla.novell.com/show_bug.cgi?id=782904.
openSUSE by default is using "splash quiet"
