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 6804E1381FA for ; Fri, 16 May 2014 18:29:06 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AB498E0A93; Fri, 16 May 2014 18:28:56 +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 6F872E0A43 for ; Fri, 16 May 2014 18:28:55 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id n15so2236958lbi.33 for ; Fri, 16 May 2014 11:28:54 -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=yaa4NJglF0KSTAJqCht/RyqifI6s21rn/+WxH8tWgc4=; b=Xdnl15l131xNujwJkuErCo1mj55GkKh0+QdnVftdLuv0ojnnG7gdH7bq2tVURKKCoV vDDajFfkz67b4/u5jXjZXzlkg6Fzx2oUoDsDdvvgqaGKxM5ekNFsnAFtGmOli8LXdG/s YC8izIRe1ZKDnrAiELrpMpa93jDy5xgFu1kvcfkrQt12iUOUogF69zTGEVFaKES2+hYS 7fI6lh6KBM+7Lc5Eme7ZgfC99j/bQXFasoS976wJFcYbJ0AzzO5Xej+82R9OvZepxHFL eS5LaOQ2UdaqCGMHuPY6GFgW/2y5RhK0jU1G+EcGJzco/gkNbd+sljbaDP8ZvNOavCaM Z2vw== X-Received: by 10.112.162.42 with SMTP id xx10mr2687546lbb.8.1400264933944; Fri, 16 May 2014 11:28:53 -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; Fri, 16 May 2014 11:28:33 -0700 (PDT) In-Reply-To: <16453.1400263889@ccs.covici.com> References: <23736.1399879340@ccs.covici.com> <13680.1399912266@ccs.covici.com> <17066.1399913526@ccs.covici.com> <8704.1400060591@ccs.covici.com> <26238.1400079937@ccs.covici.com> <31967.1400082129@ccs.covici.com> <15515.1400106362@ccs.covici.com> <26096.1400186293@ccs.covici.com> <53753922.201@xunil.at> <13544.1400237631@ccs.covici.com> <8683.1400260656@ccs.covici.com> <16453.1400263889@ccs.covici.com> From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= Date: Fri, 16 May 2014 13:28:33 -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: 876b4050-74bf-4ae1-871c-2e6d17e1e535 X-Archives-Hash: 6e72153bf6d0a49a24d39e4ea2bbe09a On Fri, May 16, 2014 at 1:11 PM, wrote: > Canek Pel=C3=A1ez Vald=C3=A9s wrote: > >> On Fri, May 16, 2014 at 12:17 PM, wrote: >> [snip] >> >> I don't understand the current situation .So now you get ALL your >> >> volumes activated, or not? >> > >> > Yep, they are all activated and they all get mounted. >> >> Cool, one problem less. >> >> >> > Now for some systemd problems. The root file system was read only = when >> >> > I logged in, but I could remount it rw -- not sure why this was >> >> > happening. >> >> >> >> Set systemd.log_level=3Ddebug in your command line, and post the exit >> >> from journalctl -b. >> > >> > I had debug in the command line by itself, would that make the correct >> > log_level? The file is quite large, should I send it to you privately= ? >> >> I don't think is necessary, I may have found the real problem (see below= ). >> >> >> > Some units did start, but most did not. Whenever I tried to >> >> > start one manually, I got a message like the following: >> [snip] >> >> > No matter what unit I tried to start I would get such a message ab= out >> >> > the service.mount. >> >> >> >> That sounds like a problem with the cgroups hierarchy (which uses a >> >> virtual filesystem). I don't remember seeing a problem like that >> >> before. >> >> >> >> > Also, even though my network names were correct, they did not come = up, >> >> > but I will try to look in the logs to see why not. >> > I wrote a service file to start my network adaptors, here it is: >> > network@.service >> > >> > >> > [Unit] >> > Description=3DNetwork Connectivity for %i >> > Wants=3Dnetwork.target >> > Before=3Dnetwork.target >> > BindsTo=3Dsys-subsystem-net-devices-%i.device >> > After=3Dsys-subsystem-net-devices-%i.device >> > [Service] >> > Type=3Doneshot >> > RemainAfterExit=3Dyes >> > EnvironmentFile=3D/etc/conf.d/network@%i >> > ExecStart=3D/usr/bin/ip link set dev %i up >> > ExecStart=3D/usr/bin/ip addr add ${address}/${netmask} broadcast ${bro= adcast} dev %i >> > ExecStart=3D/bin/bash -c 'test -n ${gateway} && /usr/bin/ip route add = default via >> > ${gateway}' >> > ExecStart=3D/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh&&/bin/bash = /etc/conf.d/postup@%i.sh >> > ExecStop=3D/usr/bin/ip addr flush dev %i >> > ExecStop=3D/usr/bin/ip link set dev %i down >> > [Install] >> > WantedBy=3Dnetwork.target >> >> Did you enabled network@ifaca.service? Also, WantedBy=3Dnetwork.target >> doesn't do what you probably think it does (check [1]... and BTW, I >> forgot my last footnote, is now on [2]). >> >> I would use WantedBy=3Dmulti-user.target. >> >> >> systemd will not (AFAIK) start your network, and before the 209 or 21= 0 >> >> version it needed helper program (NetwokrManager, connman, ip, >> >> ifconfig, etc.) to do it. Now it includes networkd, but you need to >> >> set up .network files (like .service files) to configure it. See [1]. >> >> >> >> > So we have made some progress, but still a long way to go yet. Not= e >> >> > also, that I am not booting into a display manager, just a regular >> >> > console. >> >> > >> >> > >> >> > What a lot of work just to get the system booted! >> >> >> >> Well, you have a setup that is not, by any means, simple. Also, in my >> >> experience old LVM configurations seem to cause a lot of troubles to >> >> bring to what systemd expects. >> >> >> >> John, could you also post here your kernel config? Those cgroups >> >> errors *may* be related to some missing functionality from the kernel= . >> >> [snip kernel config] >> >> John, your kernel is incorrectly configured to be used by systemd. >> When you installed systemd, a warning should have appeared about some >> missing configure options; you either didn't saw or ignored those >> warnings. Install systemd again so you can see them. >> >> From what I can tell, you are missing *AT LEAST* the following options: >> >> CONFIG_AUTOFS4_FS > configured as a module. > >> CONFIG_DMIID > > set to Y > >> CONFIG_FANOTIFY > set to y > >> CONFIG_INOTIFY_USER > set to y > > >> CONFIG_PROC_FS > set to y > >> CONFIG_SYSFS > set to y I beg your pardon; GMail cut the config file and I didn't notice. Well then, please send me privately the output from journalctl -b. Regards. --=20 Canek Pel=C3=A1ez Vald=C3=A9s Profesor de asignatura, Facultad de Ciencias Universidad Nacional Aut=C3=B3noma de M=C3=A9xico