Re 20121111192731.149dc082@dartworks.biz20121111192731.149dc082@dartworks.bizCADPrc83TGeegA0UXadMEy=B62xZYOE50bqfw+dxDJ8f=FkPTHA@mail.gmail.com20121111185801.58964939@dartworks.bizCADPrc83+5zUQ+GzCSvyHhZa7BZfMqqagZCosktasOY1sdhCx0Q@mail.gmail.com20121111175313.54b9acf1@dartworks.bizCADPrc80EwExpbdcJX1a+aE0DA=iopqw-QOaozmUBJCs5FGew-g@mail.gmail.com20121109171149.1d8a3e18@dartworks.biz509D9C62.9040909@gmail.com509D8E00.4030208@coolmail.sek7k1hn$ce6$1...@ger.gmane.org, Canek Peláez Valdés said: > That it's weird. What does "systemd-analyze blame" say after a fresh > boot?
Something related to consolekit was taking by far the most time. But I thought I was supposed to remove that. So I make USE include -consolekit, and removed console kit, and did "emerge -uD --newuse world", but yet, pambase insists on pulling in consolekit no matter what. I compile it separate (emerge -1 ...) without consolekit USE, and the works. But whenever I update consolekit wants get added again. Anyway, right now I have it removed and it does come up faster without it. But another thing I miss is knowing where it is in the boot process. The systemd doesn't tell me anything. -- Keith -- -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Keith Dart <ke...@dartworks.biz> public key: ID: 19017044 <http://www.dartworks.biz/> =====================================================================
