Re: Systemd: follow-up

2014-08-08 Thread Ric Moore
On 08/08/2014 09:35 AM, Tom H wrote: On Thu, Aug 7, 2014 at 6:57 PM, Joel Rees wrote: On Fri, Aug 8, 2014 at 4:04 AM, Brian wrote: On Thu 07 Aug 2014 at 20:25:22 +0200, Johann Spies wrote: After rescuing two laptops which were unbootable after the installation of systemd-sysfs I had problem

Re: Systemd: follow-up

2014-08-08 Thread Ric Moore
On 08/07/2014 03:04 PM, Brian wrote: I don't think anything that happened shows systemd as a prime cause of your troubles. But the account will become part of the folklore. :) Yes, such panic attacks will be fodder for the online Linux shows (The HORROR! The HORROR!). I think that if the OP

Re: Systemd: follow-up

2014-08-08 Thread Tom H
On Thu, Aug 7, 2014 at 6:57 PM, Joel Rees wrote: > On Fri, Aug 8, 2014 at 4:04 AM, Brian wrote: >> On Thu 07 Aug 2014 at 20:25:22 +0200, Johann Spies wrote: >> >>> After rescuing two laptops which were unbootable after the installation of >>> systemd-sysfs I had problems with stuff as bluetooth a

Re: Systemd: follow-up

2014-08-08 Thread Brian
On Fri 08 Aug 2014 at 07:57:41 +0900, Joel Rees wrote: > On Fri, Aug 8, 2014 at 4:04 AM, Brian wrote: > > On Thu 07 Aug 2014 at 20:25:22 +0200, Johann Spies wrote: > > > >> After rescuing two laptops which were unbootable after the installation of > >> systemd-sysfs I had problems with stuff as b

Re: Systemd: follow-up

2014-08-08 Thread PaulNM
On 08/07/2014 07:00 PM, Joel Rees wrote: > Cognitive dissonance? What are you referring to? > > On Fri, Aug 8, 2014 at 7:24 AM, PaulNM wrote: >> Hi, please reply to the list as I am subscribed. >> >> On 08/07/2014 05:56 PM, Johann Spies wrote: >>> For the sake of clarity: The failure to boot w

Re: Systemd: follow-up

2014-08-07 Thread Joel Rees
Cognitive dissonance? On Fri, Aug 8, 2014 at 7:24 AM, PaulNM wrote: > Hi, please reply to the list as I am subscribed. > > On 08/07/2014 05:56 PM, Johann Spies wrote: >> For the sake of clarity: The failure to boot was on the dist-upgraded >> system and was due to systemd.sysfs. I will not repea

Re: Systemd: follow-up

2014-08-07 Thread Joel Rees
On Fri, Aug 8, 2014 at 4:04 AM, Brian wrote: > On Thu 07 Aug 2014 at 20:25:22 +0200, Johann Spies wrote: > >> After rescuing two laptops which were unbootable after the installation of >> systemd-sysfs I had problems with stuff as bluetooth and some of the >> services. > > There are wiser and more

Re: Systemd: follow-up

2014-08-07 Thread PaulNM
Hi, please reply to the list as I am subscribed. On 08/07/2014 05:56 PM, Johann Spies wrote: > For the sake of clarity: The failure to boot was on the dist-upgraded > system and was due to systemd.sysfs. I will not repeat what I said in my > previous thread about this (see 'Systemd waisted 5 hour

Re: Systemd: follow-up

2014-08-07 Thread Johann Spies
Apologies for top-posting. I was working in my browser which hided the rest of the stuff and I forgot to delete it. Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)

Re: Systemd: follow-up

2014-08-07 Thread Johann Spies
For the sake of clarity: The failure to boot was on the dist-upgraded system and was due to systemd.sysfs. I will not repeat what I said in my previous thread about this (see 'Systemd waisted 5 hours of my time'). My installation of stable was exactly to escape the nightmares of systemd.sysfs whi

Re: Systemd: follow-up

2014-08-07 Thread PaulNM
On 08/07/2014 02:25 PM, Johann Spies wrote: > After rescuing two laptops which were unbootable after the installation > of systemd-sysfs I had problems with stuff as bluetooth and some of the > services. > > So I decided to do a clean install of stable and got going - until I > left my laptop for