systemd

[Dan Kociela]

I apologize for missing that, works great now (x86-64 + grub-legacy)
Thank you Jean and Dennis

On Sun, Feb 19, 2012 at 8:01 AM, Dennis Veatch
<dennisveatch at bellsouth.net>wrote:

> On 02/19/2012 09:40 AM, Jean Bruenn wrote:
>
>> Hello Dan,
>>
>> try recompiling systemd maybe with less options (optional depends)
>> there _has_ to be a binary somewhere - If it's not there (updatedb&&
>> locate systemd" or "lvu install systemd") it won't work - Then look
>> for some errors in the compile log (lvu should have an option to check
>> that). Also, please feel free to join IRC and bug dveatch or me (wdp)
>> - dveatch recently had some issues with systemd as well and might be
>> able to help you.
>>
>> For the binary path - yeah, take the lvu edit approach and if you like,
>> please "lvu submit systemd" it if it really takes the new path by doing
>> so, however make sure that only binaries gets installed in /sbin
>>
>> Jean
>>
>>
>> On Sun, 19 Feb 2012
>> 07:23:35 -0700 Dan Kociela<dkociela at gmail.com>  wrote:
>>
>>  Hi Jean,
>>> Thanks for your response. "lvu installed" shows:42.
>>>
>>>  Apparently the default installation is to /usr/bin. However, there
>>> is no single systemd binary. There are a collection of 13 binaries
>>> (systemd-analyze, systemd-ask-password, systemd-cat, systemd-cgls,
>>> systemd-cgtop, etc).
>>>
>>> I'm wondering if symlinks to each binary would work, or if using "lvu
>>> edit" and changing the installation "./configure --prefix=/sbin", or
>>> changing the bootloader to use "init=/usr/bin/systemd" would be best.
>>>
>>> What do you think? And thank you for your help.
>>>
>>> Dan
>>>
>>> On Sat, Feb 18, 2012 at 3:18 AM, Jean Bruenn
>>> <jean.bruenn at ip-minds.de>**wrote:
>>>
>>>  Hello Dan,
>>>>
>>>> I'm pretty sure thats because of systemd changing the binary path
>>>> all two weeks. Please issue
>>>>
>>>> lvu installed systemd
>>>>
>>>> If it tells you systemd is not installed, something went wrong. Then
>>>> please issue:
>>>>
>>>> lvu install systemd
>>>>
>>>> And check where the binary went. I've seen it lying around
>>>> in /usr/bin /bin /sbin. If you have found it, create a symlink from
>>>> it to /sbin, make sure your bootloader will use init=/sbin/systemd
>>>> and try again.
>>>>
>>>> Jean
>>>>
>>>> On Fri, 17 Feb 2012 18:51:15 -0700 Dan Kociela
>>>> <dkociela at gmail.com>  wrote:
>>>>
>>>>  Hi,
>>>>> I have the feeling that I'm missing something simple but I have
>>>>> installed systemd and when I issue "systemctl" I get " failed to
>>>>> get dbus connection: no connection to service manager". ps aux
>>>>> shows that dbus and udev are both running. "systemd --test"
>>>>> results in "systemd: command not found". Any clues are welcome.
>>>>> Thanks,
>>>>> dan
>>>>>
>>>>
>>>> --
>>>> Jean Bruenn<jean.bruenn at ip-minds.de**>
>>>>
>>>
> The systemd executable path has changed with version 42. It now lives in;
>
> /usr/lib/systemd/systemd
>
> So point your lilo or grub append there. It works fine on x86_64 + lilo.
>
>
> --
> Dennis `stumbles` Veatch
> Lunar Linux Developer
> http://www.lunar-linux.org/
>
>
> ______________________________**_________________
> Lunar mailing list
> Lunar at lunar-linux.org
> http://foo-projects.org/**mailman/listinfo/lunar<http://foo-projects.org/mailman/listinfo/lunar>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://foo-projects.org/pipermail/lunar/attachments/20120219/ace76b0c/attachment-0001.html>