Hi,
I've followed the arch wiki and deployed a full disk encrypted install.
Everything works fine and am able to boot properly into the install. While
trying to shutdown my system, systemd displays an error which says "systemd:
stopped (with error) /dev/mapper/crypt-boot". 'crypt-boot' is
On Sat, Feb 13, 2016 at 10:49 AM, PeLo L wrote:
>
> Hi,
>
>
> I've followed the arch wiki and deployed a full disk encrypted install.
> Everything works fine and am able to boot properly into the install.
> While trying to shutdown my system, systemd displays an error
> which
Sorry if I was too harsh. But the methods are for fundamentally
different purposes, apg's intends to remain compatible with systemd and
is backed up by the AUR, while artoo's intends to replace systemd and
has its own repositories elsewhere. AFAIK, artoo tried to convince apg
to join forces, with
> > I feel it pertinent to point out that a different rolling-release
> > distrobution ( http://www.voidlinux.eu/ ) does not use systemd, openrc, or
> > sysvinit. Void Linux uses runit exclusively, and thus patches projects like
> > KDE4 and Gnome3 to work without systemd (I don't mention KDE5
On 02/13/2016 04:17 PM, João Miguel wrote:
>>> I feel it pertinent to point out that a different rolling-release
>>> distrobution ( http://www.voidlinux.eu/ ) does not use systemd, openrc, or
>>> sysvinit. Void Linux uses runit exclusively, and thus patches projects like
>>> KDE4 and Gnome3 to
On Sat, 2016-02-13 at 13:47 +0100, Carsten Mattner wrote:
> On Sat, Feb 13, 2016 at 10:49 AM, PeLo L wrote:
> >
> > Hi,
> >
> >
> > I've followed the arch wiki and deployed a full disk encrypted
> > install.
> > Everything works fine and am able to boot properly into the
>
> (If your goal is to *learn*, then yes $DEITY yes, do that, but for
> practical things... you need some more concrete and tangible goals to
> challenge the decision of systemd-only for Arch Linux.)
The decision was to have systemd as a default, not to forbid any other
init system to be mentioned.
On 02/13/2016 05:35 PM, João Miguel wrote:
>> (If your goal is to *learn*, then yes $DEITY yes, do that, but for
>> practical things... you need some more concrete and tangible goals to
>> challenge the decision of systemd-only for Arch Linux.)
> The decision was to have systemd as a default, not
> If you want to make OpenRC easier to use on Arch, here's how:
> 1. Get more involved in the AUR to develop more/better OpenRC-specific
> packages
There are 4 mirrors for an unnoficial user repository with packages that
are officially used in Manjaro.
> 2. Draft a new OpenRC wiki article on your
On 2016-02-13 17:35, João Miguel wrote:
> The decision was to have systemd as a default, not to forbid any other
> init system to be mentioned. I don't agree with the OP of this thread
> when he said there should be an official version of Arch with OpenRC,
> that's too much work.
>
> I mean this:
On Sat, Feb 13, 2016 at 4:51 PM, Yaro Kasear wrote:
> On Sat, 2016-02-13 at 13:47 +0100, Carsten Mattner wrote:
>> On Sat, Feb 13, 2016 at 10:49 AM, PeLo L wrote:
>> >
>> > Hi,
>> >
>> >
>> > I've followed the arch wiki and deployed a full disk encrypted
>> >
Just throwing this out there: Given nosh's support for importing
systemd units, that one might be another viable option.
El 13/02/2016 a las 4:49 a. m., PeLo L escribió:
> Hi,
>
>
> I've followed the arch wiki and deployed a full disk encrypted install.
> Everything works fine and am able to boot properly into the install. While
> trying to shutdown my system, systemd displays an error which says "systemd:
>
Hi,
> As you are shutting down, the filesystem becomes unreadable for the
> systemd process, you need to add the shutdown hook to mkinitcpio in
> order to have a copy of the initramfs at shutdown time.
I thought this was obsolete since mkinitcpio 16?
See
> There are 4 mirrors for an unnoficial user repository with packages that
> are officially used in Manjaro.
> > 3. Work on 1 and 2 until you feel like you have a clearly superior
method
> The method already existed, I just wanted to make it visible.
I think you misunderstood. I was not
El 13/02/2016 a las 6:28 p. m., Merlin Büge escribió:
> Hi,
>
> I thought this was obsolete since mkinitcpio 16? See
> https://lists.archlinux.org/pipermail/arch-dev-public/2013-December/025742.html
>
> (I'm not sure, just curious...) @OP: I had a similar issue a few
> months ago and fixed
El 13/02/2016 a las 6:44 p. m., P. A. López-Valencia escribió:
>
> Well, it doesn't happen to me unless I add the hook. Probably it was
> true three years ago, but it got broken along the way. I customarily
> replace the udev hook with the systemd hook and not even then is the
> initramfs copy
17 matches
Mail list logo