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 E2CDA1381FA for ; Tue, 13 May 2014 13:03:00 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 28F53E0B4E; Tue, 13 May 2014 13:02:55 +0000 (UTC) Received: from mail-lb0-f175.google.com (mail-lb0-f175.google.com [209.85.217.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EC0C0E0AE2 for ; Tue, 13 May 2014 13:02:53 +0000 (UTC) Received: by mail-lb0-f175.google.com with SMTP id l4so241334lbv.34 for ; Tue, 13 May 2014 06:02:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=G1WpbkEIDGSg7TvJcBDNQxXLF7XAUtaKYkxbACPLlek=; b=oQcXeVTP5O4/L8mf/4HX2ZowHr8tnEjI1Nd7b6tu3UPuRzcP2ol2IBCyIINLSHR2G8 cXQbXZt9RAojalnO0RfblQ34YbEWMu7ZYBnMFXk1O/e/nDb58VVFYI7+rRzJ/5td3IdB fw0Rbu20G/6Taf/CnEsxHuKPEUrOEfD+eqEZOHj4NibkWgQkSjwC2nJLURasRk/wot/3 tNDVCgSj5IZ65YU/bIOWl0v7G3O6FkXGsCVqHxQ+0X/In3yv2L6NSAiL784ZMrMyugok MgwUaswuSFgTRUo/XRX7J8jMzTup8uRRFLksjH1btim9Mrn95Pxtmbja9r7bzec6Iqry P12g== 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 X-Received: by 10.112.146.234 with SMTP id tf10mr28614505lbb.1.1399986172132; Tue, 13 May 2014 06:02:52 -0700 (PDT) Received: by 10.112.54.138 with HTTP; Tue, 13 May 2014 06:02:52 -0700 (PDT) In-Reply-To: <17536.1399952802@ccs.covici.com> References: <23736.1399879340@ccs.covici.com> <17435.1399889735@ccs.covici.com> <17536.1399952802@ccs.covici.com> Date: Tue, 13 May 2014 07:02:52 -0600 Message-ID: Subject: Re: [gentoo-user] problems getting systemd to work From: =?UTF-8?Q?Jc_Garc=C3=ADa?= To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 2c7e1dc8-c5d9-4ef7-bffb-2f96bcb8bf6d X-Archives-Hash: b94dd40532de6ec3c4af829f80d53610 2014-05-12 21:46 GMT-06:00 : > Hi. Well, even with use_fstab=yes, it does not put one, just > /etc/fstab.empty of 0 length -- how can I fix? > That is strange, never had this problem, actually adding this made it work for me, I assume you actually used the ' "yes" ', might be important for the syntax, I uncompressed my ramdisk a few minutes ago to actually verify the fstab, and it is in fact included, might be other parameters missing in cofiguration, all uncomented parameters in my dracut.conf are these in case it might help you: logfile=/var/log/dracut.log fileloglvl=6 add_dracutmodules+="lvm bash dm kernel-modules systemd" lvmconf="yes" use_fstab="yes" host_cmdline="yes" kernel_cmdline="cmdline..." And when generating I just simply run: dracut --kver 'kernel_version' As you see my configuration is pretty simple, I suggest you to try forcing the inclussion of fstab(extract, and re-compress the image), to verify if it solves your booting problem, it might be a dracut bug(tough it seems a relatively simple feature to be that prone to bugs).