From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 893B81381FA for ; Mon, 12 May 2014 16:37:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 82726E0B54; Mon, 12 May 2014 16:37:26 +0000 (UTC) Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com [209.85.217.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4F6B2E0B2D for ; Mon, 12 May 2014 16:37:24 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id n15so7611580lbi.19 for ; Mon, 12 May 2014 09:37:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=fkL29LxbgU0iO4OIE4FyDZdMHgk9szojRrnzaa7GKmg=; b=qaVg85/us2gGW1lR7wLrAtzT4EUoic48EASo2PmT9Gunh1KO8lFnfz7IAKkyKqYHoI uNAqznti3J58trROyQ4ENv1ZPQsdK+UK2r6bffy5TWYhyQnp5zXo56TWD0B/7DJ1LPVO zEUhryH/WOpLPer35osQOMS5gWrpUAI25X+modtmpj+zjINtpgrVWasHGRCmu/SKU5Z4 nqoDMkooeCcdfsRBCuXWzJd0r1OC0Or5e4mTu93/V6XJwcP7cCasSg1hkIjMR8+T7NB6 +yvobbgbf+GegMqPiRnKRUz7/U38emkKZpeB38y8/Z5r7a9VlqtNmyJbAod8jAen3Wkx bZXg== X-Received: by 10.152.23.233 with SMTP id p9mr13985322laf.31.1399912643550; Mon, 12 May 2014 09:37:23 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.114.170.166 with HTTP; Mon, 12 May 2014 09:37:03 -0700 (PDT) In-Reply-To: <13680.1399912266@ccs.covici.com> References: <23736.1399879340@ccs.covici.com> <17435.1399889735@ccs.covici.com> <13680.1399912266@ccs.covici.com> From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= Date: Mon, 12 May 2014 11:37:03 -0500 Message-ID: Subject: Re: [gentoo-user] problems getting systemd to work To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: f9c09066-bb6a-4cf0-9a68-483e80f1ea4e X-Archives-Hash: 02ba869723d4b7b1c79ac299886311aa On Mon, May 12, 2014 at 11:31 AM, wrote: [snip] > OK, I will try dracut, I hope it works with dracut. This is my kernel command line and RAID/LVM related stuff from GRUB2: GRUB_CMDLINE_LINUX=3D"init=3D/usr/lib/systemd/systemd quiet nosplash" GRUB_PRELOAD_MODULES=3D"lvm mdraid1x" And this is my dracut.conf (minus comments): add_dracutmodules+=3D"crypt lvm mdraid systemd" add_drivers+=3D"autofs4 ipv6 dm-crypt aes sha256" fscks=3D"umount mount /sbin/fsck* e2fsck" That's it. I didn't touched anything else to make dracut+systemd work with LVM and RAID (and LUKS, but that doesn't matter). Also, dracut comes with extensive and very clear documentation; check the man pages included. > but I still want to know what systemd is doing, > what processes its spawning, etc. -- how can I find this out -- I > thought to use the confirm_spawn, but it times out and keeps going, what > can I do instead? You can use bootchart: man 1 systemd-bootchart It will produce a chart with all the processes, and how long it takes for every one of them. But remember, the order depends on which one finishes before, and that can change from boot to boot. > Thanks people for all your responses, this is a great list. Regards. --=20 Canek Pel=C3=A1ez Vald=C3=A9s Profesor de asignatura, Facultad de Ciencias Universidad Nacional Aut=C3=B3noma de M=C3=A9xico