>> >BTW, Adam, there are people running & testing Rawhide on i686! :) >> >> Yes, and I am backlogged getting bugs filed for issues I am having. >> I have at least two different problems with 3.16 kernels that make them >> unusable for me. >> >> There might be a problem with systemd creating init files for a bunch of >> services, since I am now seeing some services attempt to start at boot, >> that I can't disable. > > systemd doesn't just 'create init files', I don't think. It *does* have > a concept of dependencies, which could account for this effect. I'm seeing it, at least appear, to do something like this. There's a new binary, at least since systemd-208 in F-20 (sorry, shitty hotel wifi makes it too hard to do wider triage) called: /usr/lib/systemd/system-generators/systemd-sysv-generator > What services exactly are you talking about? I'm seeing the following style of messages in dmesg. The following is a sample but wc tells me there's 343 entries: [44437.200793] systemd-sysv-generator[24124]: Could not find init script for radvd.service [44437.200810] systemd-sysv-generator[24124]: Could not find init script for ebtables.service [44437.200814] systemd-sysv-generator[24124]: Could not find init script for oddjobd.service [44437.200818] systemd-sysv-generator[24124]: Could not find init script for spice-vdagentd.service [44437.200822] systemd-sysv-generator[24124]: Could not find init script for livesys-late.service [44437.200826] systemd-sysv-generator[24124]: Could not find init script for tcsd.service [44437.200831] systemd-sysv-generator[24124]: Could not find init script for livesys.service [44437.200837] systemd-sysv-generator[24124]: Could not find init script for radvd.service I can dig further if necessary in the next few days, I'm travelling at the moment and $dayjob is a bit intense so time is limited in the short term :( Peter -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
