From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id DF69B1382DE for ; Thu, 30 Jun 2016 12:55:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 10ABD14010; Thu, 30 Jun 2016 12:55:47 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EE2BFE0AE6 for ; Thu, 30 Jun 2016 12:55:45 +0000 (UTC) Received: from [192.168.1.2] (c-73-53-75-119.hsd1.wa.comcast.net [73.53.75.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: zlg) by smtp.gentoo.org (Postfix) with ESMTPSA id A8227340E3C for ; Thu, 30 Jun 2016 12:55:44 +0000 (UTC) Subject: Re: [gentoo-dev] Need design help/input for eclean-kernel To: gentoo-dev@lists.gentoo.org References: <20160630143827.7bd185dd.mgorny@gentoo.org> From: Daniel Campbell Message-ID: <6be450d2-b9c1-f407-07a0-71fd8dbc376f@gentoo.org> Date: Thu, 30 Jun 2016 05:55:42 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 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 In-Reply-To: <20160630143827.7bd185dd.mgorny@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ixuUiTAREcvXhUSBtul0ArWVBTqaigHbD" X-Archives-Salt: 01e2b832-0546-4fdc-8ebb-0eabff2942f4 X-Archives-Hash: b23f2c1b7c5dcf9d561b931f70420f89 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ixuUiTAREcvXhUSBtul0ArWVBTqaigHbD Content-Type: multipart/mixed; boundary="gBdUftrVM7Nubx4H4ugRhfV9BNLmsOFIB" From: Daniel Campbell To: gentoo-dev@lists.gentoo.org Message-ID: <6be450d2-b9c1-f407-07a0-71fd8dbc376f@gentoo.org> Subject: Re: [gentoo-dev] Need design help/input for eclean-kernel References: <20160630143827.7bd185dd.mgorny@gentoo.org> In-Reply-To: <20160630143827.7bd185dd.mgorny@gentoo.org> --gBdUftrVM7Nubx4H4ugRhfV9BNLmsOFIB Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 06/30/2016 05:38 AM, Micha=C5=82 G=C3=B3rny wrote: > Hello, everyone. >=20 > Back in 2011 I started a project called eclean-kernel. The idea was > pretty simple -- to have a tool that would clean the old kernels for > me since their install is not controlled by the package manager. This > little project of mine seems to have gained a lot of popularity. >=20 > Sadly, over time a lot of people had trouble with it. Aside to minor > Python problems, eclean-kernel proved too simple to handle multitude of= > user systems with varying /boot layouts. In fact, even I don't use it > on all of my systems since it doesn't handle them properly. >=20 > After being buried in another set of bug reports, I'd like to > officially ask Gentoo developers and users for help. I think it's > impossible to solve most of the bugs reported so far in the current > program design. Therefore, I'd like to rewrite it in a more flexible > manner. >=20 > For this reason, I would like to ask you to provide me with > different /boot layouts you may have, had or seen. Basically, the idea > is to collect as many different layouts as necessary, and use that to > design eclean-kernel in a way making it possible to easily configure it= > to handle proper variant -- or even possibly make it capable of > autoconfiguration. >=20 > So if you have some time, please reply to this thread with > a specific /boot layout that you think needs to be handled, with > as much helpful information as possible -- including possible > distinctive features and pitfalls. >=20 > Thanks in advance. >=20 I'm not sure if this is the info you're looking for, but I'll give it a shot: I have grub-static installed to /boot/. I like to organize my kernels with the filenames as linux-${version}-gentoo-${buildno}. So my first build of 4.5.0, for example, would be 'linux-4.5.0-gentoo-1'. It has all the info I need for reference should something go awry. I have three symlinks: current, last, backup I wrote scripts that will update those symlinks for me, which makes the process of kernel management pretty painless. Now that I'm thinking about it, it could be simple in my case to simply clean any kernel that wasn't linked to. My /boot/: grub lost+found backup -> linux-4.4.1-gentoo-2 boot current -> linux-4.4.6-gentoo-1 initrd last -> linux-4.4.1-gentoo-3 linux-4.4.1-gentoo-2 linux-4.4.1-gentoo-3 linux-4.4.6-gentoo-1 --=20 Daniel Campbell - Gentoo Developer OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 --gBdUftrVM7Nubx4H4ugRhfV9BNLmsOFIB-- --ixuUiTAREcvXhUSBtul0ArWVBTqaigHbD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXdRbOAAoJEAEkDpRQOeFw4j0P/jTzi7I7sIAbv4Qf3NYvh0Fy udDR5ChbFGRtrNTd5Fq7IK2ph0ASNVrAJW/o2dpTxW9TutJG6afJLp+UJHv9Bvdc tmE/53T0tokLCVPx3L9+2J3FVnqfok8wlMbfSCw9wuz4Rvs/H1SFXeqlShnrcGiI loo4L4moZALanXnr/2nPoltgUbb3172XxG13h44fRdaCAfz/LHOeCvbagzWb9gLP maIY7spu9bjKeMc77kRsORDk6EXgsMb4RCvxd4uyOnDznd56Hw0Q3NJ79VxtKl3E sT5mjDq/MOfhXg701ojdBdj3cxKf0BuCRnpXFEB3DVYYmE7UZ8G5ZLYb/KJfMfrL 441AF1BBawFNbvl9XIDskQVJ3J57M0sJ+M9k/B5Wdo189uYh5Kr/1appExQcw9pa LiL23ahOnAzq8RnDQLr5Fz6DTeXAxJB68bzAFElGhMKYEExsZugYlbvJCidS2fYY DIMjgE8c1M4M1fWdJeQ0vEdOvXJsq+RAhchI30jQ5q9iQcyHLCc3ImF+vxYZX44o f7hbWsRjZLSsY+dBcitrn2/OyVUjvU7tR5d4yARrgoTrQYxyIp0K5aEUxjpNThr/ Ea3SUI34DmEJGNFKU/2Rr8IoZNKy+UdVAbdDn3i3zdSZuN/WnqjVikSdAnMHXQwb xrQ+TudjOu6NUocCGWPY =FaQS -----END PGP SIGNATURE----- --ixuUiTAREcvXhUSBtul0ArWVBTqaigHbD--