>> Is it the Arch recommendation to add this kernel option at boot time?
>> Or will /sbin/init point to /usr/lib/systemd/systemd for the
>> foreseeable future?
>
> As long as the kernel default for the init process is /sbin/init, we
> will keep probably the /sbin/init symlink for systemd. We may ad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2013 02:32 AM, Thomas Bächler wrote:
>
> In any case, booting a default installation without init= is
> supported and recommended, and we will make sure it keeps working.
>
Good. That alleviates a lot of my concern.
- --
David Benfell / be
On Mon, 13 May 2013 10:19:36 +0200 Thomas Bächler
wrote:
>Am 13.05.2013 10:18, schrieb Iru Cai:
>> Well, some people seldom read pacman's output. e.g. I use a cron job to
>> use pacman to update the system, and I don't read the log very often.
>
>That's your own fault then.
>
>>> Why do you think
Am 13.05.2013 11:23, schrieb David Benfell:
> On 05/13/2013 01:19 AM, Thomas Bächler wrote:
>
>> The wiki has told you to use init=/usr/lib/systemd/systemd for
>> quite some time.
>
> When I was configuring the bootloaders (grub in two cases, gummiboot
> in another), I was following the installat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2013 01:19 AM, Thomas Bächler wrote:
>
> The wiki has told you to use init=/usr/lib/systemd/systemd for
> quite some time.
>
When I was configuring the bootloaders (grub in two cases, gummiboot
in another), I was following the installation i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2013 01:03 AM, Karol Blazewicz wrote:
>
> Not reading pacman's output may lead to problems. Why do you think
> it's a bad way?
>
It's precisely because I *did* read pacman's output that I was
alarmed. Like I say, I think it's okay. But I'd l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2013 12:26 AM, Hussam Al-Tayeb wrote:
> On Sunday 12 May 2013 22:32:03 David Benfell wrote:
>> Hi all,
>>
>> I was alarmed, I think unnecessarily, when I saw the message that
>> a symlink for systemd was removed on an upgrade.
>>
>> As near
On Sunday 12 May 2013 22:32:03 David Benfell wrote:
> Hi all,
>
> I was alarmed, I think unnecessarily, when I saw the message that a
> symlink for systemd was removed on an upgrade.
>
> As near as I can tell, the boot sequence still relies on init, which
> links to the right place.
>
> Is there
Am 13.05.2013 10:18, schrieb Iru Cai:
> Well, some people seldom read pacman's output. e.g. I use a cron job to use
> pacman to update the system, and I don't read the log very often.
That's your own fault then.
>> Why do you think it's a bad way?
>>
> Maybe some people haven't installed systemd-
2013/5/13 Karol Blazewicz
> On Mon, May 13, 2013 at 7:32 AM, David Benfell
> wrote:
> > Hi all,
> >
> > I was alarmed, I think unnecessarily, when I saw the message that a
> > symlink for systemd was removed on an upgrade.
> >
> > As near as I can tell, the boot sequence still relies on init, wh
On Mon, May 13, 2013 at 7:32 AM, David Benfell
wrote:
> Hi all,
>
> I was alarmed, I think unnecessarily, when I saw the message that a
> symlink for systemd was removed on an upgrade.
>
> As near as I can tell, the boot sequence still relies on init, which
> links to the right place.
>
> Is there
11 matches
Mail list logo
