From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 13CE01381F3 for ; Tue, 2 Jul 2013 18:18:26 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 59AF3E0A9B; Tue, 2 Jul 2013 18:18:17 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 74142E0A5B for ; Tue, 2 Jul 2013 18:18:16 +0000 (UTC) Received: from sf (unknown [178.120.3.9]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: slyfox) by smtp.gentoo.org (Postfix) with ESMTPSA id 8D4D533E844 for ; Tue, 2 Jul 2013 18:18:14 +0000 (UTC) Date: Tue, 2 Jul 2013 21:16:07 +0300 From: Sergei Trofimovich To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Proper distribution integration of kernel *-sources, patches and configuration. Message-ID: <20130702211607.5aeafeba@sf> In-Reply-To: References: <20130701164149.131490f8@TOMWIJ-GENTOO> <20130702103634.0e70b9f8@sf> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.17; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/B=aNu.B2wwieVbmxD_pLq7c"; protocol="application/pgp-signature" X-Archives-Salt: 1efe572c-d91e-4de2-ba7d-b69d4cec0f5e X-Archives-Hash: c7fa456e91212ccb286177c8ba23e500 --Sig_/B=aNu.B2wwieVbmxD_pLq7c Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 2 Jul 2013 10:21:53 +0200 Fabio Erculiani wrote: > On Tue, Jul 2, 2013 at 9:36 AM, Sergei Trofimovich wr= ote: > > [ sorry, a lot to quote ] > > > > What upstream do you plan to report bugs when user possibly mixes > > all of it in one mess? Each of those is known to be unstable. The mix > > is just a disaster. > > > > Is gentoo's kernel team able to resolve user's OOpsen? > > > >> ### ... and configuration. ### > >> > >> This problem is not only visible for patches, but also in the config. > > > > Insane :] > > > >> Meet CONFIG_DEVTMPFS; forget to enable it, greet a failing boot. We're > >> telling users to enable it in some places, in the handbook it's a sing= le > >> line you must read, on the Wiki it's kind of missing unless you are > >> luckily on the right page, on the Quick Install book it is missing too. > > > > Forbid users install udev to ROOT=3D/ if running kernel does not suppor= t devtmpfs > > (easy to check by /proc/filesystems) >=20 > No. As explained multiple times, this check is not reliable and > doesn't work (chroot, binpkgs, containers without kernel, and so > on...). > Making sure that the user doesn't build an unbootable kernel is the way t= o go. udev's case: It's _not_ the kernel which upgrade breaks user's system. Why do you try to= "fix" it? If you want to save user's box - make check at pre-install time. Otherwise = it will break. containers, etc. case: If you build gentoo(and, what really matters _install_) in container - you can run gentoo in container. Yes, with it's stock broken kernel. Who cares what you have built if the host is xen-3.0.6 with CONFIG_DEVTMPFS= =3Dn? If you really want to proceed unsafe action you need to do it explicitely. kernel's case: CONFIG_DEVTMPFS needs 'default yes', right? One-liner to gentoo-sources. Why 'hide' it? It's very counterintuitive. What will you do with all-those-required-to-boot-properly - root filesystem - disk controller - USB keyboard drivers ? Include them all unless CONFIG_DONT_REMOVER_OR_WONT_BOOT option? I'm afraid I don't see how it's a solution.=20 Suppose, tomorrow's udev will require CONFIG_foo, and glibc will require CONFIG_bar. How will you save user with your mechanism? --=20 Sergei --Sig_/B=aNu.B2wwieVbmxD_pLq7c Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iEUEARECAAYFAlHTGOoACgkQcaHudmEf86pAqQCfd6mG19H6w6I1CPUzsGeDJ71M J1oAljoGglPsH8kqKJCOeWfko+8/1Sg= =edJX -----END PGP SIGNATURE----- --Sig_/B=aNu.B2wwieVbmxD_pLq7c--