Am 27.09.2013 12:36, schrieb Stefan G. Weichinger:
Am 25.09.2013 01:38, schrieb Canek Peláez Valdés:
systemd-analyze blame to see what is taking so long.
systemd-delta to see what changes from upstream do you have.
Thanks ... I cleaned up some cruft already and will test some
boot-process
Am 25.09.2013 01:38, schrieb Canek Peláez Valdés:
systemd-analyze blame to see what is taking so long.
systemd-delta to see what changes from upstream do you have.
Thanks ... I cleaned up some cruft already and will test some
boot-process soon. Still on the road ...
On 23/09/13 17:37, Canek Peláez Valdés wrote:
On Sep 23, 2013 6:01 AM, Tanstaafl tansta...@libertytrek.org
mailto:tansta...@libertytrek.org wrote:
Man... watching this discussion just makes me want to avoid systemd
like the plague/all the more...
Please don't top post.
Please disable
Am 23.09.2013 16:30, schrieb Canek Peláez Valdés:
Did you read my next email? There is no need for the extra swap unit. I was
missing a couple of kernel options and to compile LVM2 and cryptsetup with
some USE flags. Everything works as expected; but you need to put the swap
in fstab.
got it
systemd-analyze blame to see what is taking so long.
systemd-delta to see what changes from upstream do you have.
Regards.
On Sep 24, 2013 4:47 PM, Stefan G. Weichinger li...@xunil.at wrote:
Am 23.09.2013 16:30, schrieb Canek Peláez Valdés:
Did you read my next email? There is no need for
Am 21.09.2013 23:49, schrieb Canek Peláez Valdés:
OK, so I conducted another experiment, to see if I was able to make
systemd *not* to work with an exotic combination of underlying
storage. I did the following:
- 4 drives, all of them in RAID5.
- The resulting /dev/md127 was put in a
Am 23.09.2013 09:09, schrieb Stefan G. Weichinger:
Yes, I reported this issue back then ... but I don't have the encrypted
swap in /etc/fstab.
I only have:
# cat /etc/crypttab
swap /dev/disk/by-id/ata-INTEL_SSDSA2M080G2GC_CVPO015404LR080JGN-part5
/dev/urandom
Am 23.09.2013 10:00, schrieb Stefan G. Weichinger:
Getting that unit-name right is quite annoying ... fiddling with
understanding that strange escaping etc ... :-(
I have now:
# cat /etc/systemd/system/dev-disk-by\\x2did-dm\\x2dname\\x2dswap.swap
[Unit]
#After=systemd-cryptsetup.service
Man... watching this discussion just makes me want to avoid systemd like
the plague/all the more...
On 2013-09-23 4:21 AM, Stefan G. Weichinger li...@xunil.at wrote:
Am 23.09.2013 10:00, schrieb Stefan G. Weichinger:
Getting that unit-name right is quite annoying ... fiddling with
Am 23.09.2013 13:00, schrieb Tanstaafl:
Man... watching this discussion just makes me want to avoid systemd like
the plague/all the more...
I understand that, yes ... it is unnecessary complex from my point of
view as well.
Swap that is encrypted from scratch everytime you boot up isn't the
On Sep 23, 2013 3:22 AM, Stefan G. Weichinger li...@xunil.at wrote:
Am 23.09.2013 10:00, schrieb Stefan G. Weichinger:
Getting that unit-name right is quite annoying ... fiddling with
understanding that strange escaping etc ... :-(
I have now:
# cat
On Sep 23, 2013 6:01 AM, Tanstaafl tansta...@libertytrek.org wrote:
Man... watching this discussion just makes me want to avoid systemd like
the plague/all the more...
Please don't top post.
After I got LVM2, mdraid, and LUKS working with systemd, I just decided
that, for me, neither LVM2,
On 2013-09-23 10:37 AM, Canek Peláez Valdés can...@gmail.com wrote:
On Sep 23, 2013 6:01 AM, Tanstaafl tansta...@libertytrek.org
mailto:tansta...@libertytrek.org wrote:
Man... watching this discussion just makes me want to avoid systemd
like the plague/all the more...
Please don't top
OK, so I conducted another experiment, to see if I was able to make
systemd *not* to work with an exotic combination of underlying
storage. I did the following:
- 4 drives, all of them in RAID5.
- The resulting /dev/md127 was put in a Physical Volume, that in a
Volume Group, and that split into 5
14 matches
Mail list logo
