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 some hours to finish a job - and it would not react > to anything I did on the keyboard. I had to switch it off and restart
If you're having issues under stable, then it has nothing to do with systemd. > it. I though it might only be a little hiccup so I went on working on > stable (although I could not get my wifi working). Then at one stage I > left it to build a package and when I returned, it finished the job and > was totally unresponsive. > This sounds more like hardware issues to me. Maybe overheating, RAM issues, or something else. > So I deciided at least I could work with testing and I did a > dist-upgrade to testing only to find that I could not boot. > What happens? Do you get a grub prompt, does the kernel start to boot? > So for now, after using Debian for many years on my laptop, I am going > to try something else. > > I would like to return to Debian when the systemd problems are sorted out. > Wheezy (stable) doesn't use systemd, though it is available as a technology preview. Testing and unstable can be run without it. There were hiccups earlier practically forcing systemd to be used unless you held back on updates, but not anymore. > I will continue using Debian on my server and two other computers where > fortunately I did not do a dist-upgrades. > > Regards > Johann > > -- > Because experiencing your loyal love is better than life itself, > my lips will praise you. (Psalm 63:3) - PaulNM -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53e3d08d.7040...@paulscrap.com
