> On May 16, 2014, at 10:00, Jc García <[email protected]> wrote:
>
> 2014-05-16 7:50 GMT-06:00 Hunter Jozwiak <[email protected]>:
>>
>>
>> -----Original Message-----
>> From: Stefan G. Weichinger [mailto:[email protected]]
>> Sent: Friday, May 16, 2014 9:40 AM
>> To: [email protected]
>> Subject: Re: [gentoo-user] Can't Get Systemd to Work
>>
>> Am 16.05.2014 15:33, schrieb Hunter Jozwiak:
>>>
>>>
>>> -----Original Message-----
>>> From: Neil Bothwick [mailto:[email protected]]
>>> Sent: Friday, May 16, 2014 8:06 AM
>>> To: [email protected]
>>> Subject: Re: [gentoo-user] Can't Get Systemd to Work
>>>
>>>> On Fri, 16 May 2014 07:34:16 -0400, Hunter Jozwiak wrote:
>>>>
>>>> Hi all. I am having issues with Systemd as well. I added to the GRUB2
>>>> configuration file the needed command line to get Systemd to start,
>>>> but for whatever reason, the kernel is adamant that I must use OrenRC.
>>>
>>> You need to tell us what you added and what the kernel complained about.
>>> The only information we have is what is in your mail, we are not the
>>> NSA, we cannot see what is on your computer.
>>>
>>>> I
>>>> recompiled with Genkernel-next a new kernel and initramfs, and that,
>>>> for whatever reason, doesn't automount my /boot partition. Is there a
>>>> fix to this?
>>>
>>> It is standard practice to not mount the /boot partition. By the time
>>> the boot process gets to mounting what is in /etc/fstab, /boot is no
>>> longer needed. That's why it is usually set to noauto in fstab.
>>>
>>>
>>> --
>>> Neil Bothwick
>>>
>>> Guns don't kill people--it's those little pieces of lead.
>>> GRUB_CMD_LINE_LINUX="init=/usr/lib/system/system", rather.
>>
>>
>> where is the quote, where is the text?
>>
>> And it's called systemd with a d ->
>>
>> GRUB_CMD_LINE_LINUX="init=/usr/lib/system/systemd"
>>
>> btw
>> Changed the line to mirror that in the Grub file, no luck.
>> #Append parameters to the Linux Kernel.
>> GRUB_CMD_LINE_LINUX="init=/usr/lib/system/systemd"
>> Save the file.
>> Mount /dev/sda2 /boot && grub2-mkconfig -o /boot/grub/grub.cfg
>
> The same again you are mistyping systemd, is
> "/usr/lib/systemd/systemd" read carefully what you copy, and verify
> always those paths really exist. If you had done this, you would have
> noticed /usr/lib/system/system doesn't exist at all.
Here are the clntents of lsblk and filesystem table, as well as the Grub
settings file,
https://www.dropbox.com/s/vn6we8gxpccrnpe/infoorforsystemdissue.txt
