On 07/03/2014 12:40 PM, Michael Biebl wrote: > Am 03.07.2014 12:33, schrieb Michael Biebl: >> Am 03.07.2014 09:09, schrieb VALETTE Eric OLNC/OLPS: >>> Sorry this was not clear, I have just checked the scripts works and I did on >>> kernel that had the CONFIG_FHANDLE already. So I do not understand why I never >>> saw a warning. >> >> Most likely the version you installed did not have this check. >> >> It was only added in 204-9. >> >> Which version did you have installed on this particular system? > > A complete apt log would be great so we know which version(s) of systemd > were installed. > I continued my slow but constant march on systemd migration at home and I'm now sure the things are a bit more complex than *only* CONFIG_FHANDLE stuff I had at work. The good point is that two more machines were fixed by regenerating a kernel so it was clearly a kernel configuration <<bug>> (kernel was correctly configured for sysv init but not systemd...) on my side BUT I had two computers were I had the pulseaudio symptom, and were the only kernel compilation flags I changed were (unless my wife give me drugs without telling) CONFIG_SECCOMP and CONFIG_NET_NS (and I have no clue why they are needed by systemd. Education appreciated). And on one of theses machines I had already tested 208-5 so its not that I also concurrently changed user space in the mean time.
I also had something strange : after upgrade on my main PC I endend up with at least / mounted as RO at first boot (symptom was non obvious just that on kde destop, I had kde-wicd icon with the "no interface" mounted icon but network stack was OK. Did not take time to investigate), a second boot that did reboot automatically even before launching the graphic and a third boot were everything was OK. I booted several time after that without any problems. I just have no messages on console during shutdown, just a blicking cursor. I'm happy to have back suspend to ram capability back on kde on my laptop and ability to shutdown system in some applications like XBMC or ktorrent ;-) So all in all, I migrated by "fixing" my kernels on two more machines but the kernel configuration flags I changed are not mandatory according to the docs and not tested by udev preinst program. Will see if I can make my NAS with raid10 works also during the week-end. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
