From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel pruning script..
Date: Mon, 8 Feb 2016 15:22:46 -0500 [thread overview]
Message-ID: <20160208202246.GB18462@fieldses.org> (raw)
In-Reply-To: <CA+55aFx-aMLAcvQsLPCScONME=9AFO7VpMbgQEAbg1_jgcy=nQ@mail.gmail.com>
On Mon, Feb 08, 2016 at 12:14:23PM -0800, Linus Torvalds wrote:
> I'm replying to a really old email, because I - once again - installed
> this silly script that you wrote several years ago on a new machine.
>
> So Bruce - how about we add this script to the kernel "tools"
> directory, because it's actually very useful for anybody who uses
> CONFIG_LOCALVERSION_AUTO like I do (and clearly you at least used to
> do too).
>
> I think CONFIG_LOCALVERSION_AUTO is really nice for various reasons
> (not the least of which is just doing thing like
>
> gitk $(uname -r)..
> but also because it makes it easy to go back to previous kernels when
> you're working on bisecting stuff etc).
Yes, I'm a fan. My test scripts check uname after boot to make sure
they're testing the kernel they built.
> I'll happily commit it as "tools/prune-kernel" or similar, but would
> like to get an ok from you as the original author.
Oh, feel free, thanks.
--b.
> And if somebody has improvements for specific distros, maybe the
> script will start getting improvements. And I won't have to copy it
> from an old machine every time, because it will just be there with the
> kernel source tree (and without a kernel source tree it's not needed).
>
> Linus
>
> On Wed, Jul 10, 2013 at 1:54 PM, J. Bruce Fields <bfields@fieldses.org> wrote:
> >
> > I run this by hand every now and then. I'm probably doing it all wrong.
> >
> > --b.
> >
> > #!/bin/bash
> >
> > # because I use CONFIG_LOCALVERSION_AUTO, not the same version again and
> > # again, /boot and /lib/modules/ eventually fill up.
> > # Dumb script to purge that stuff:
> >
> > ssh "root@$1" '
> >
> > for f in $(ls /lib/modules); do
> > if rpm -qf "/lib/modules/$f" >/dev/null; then
> > echo "keeping $f (installed from rpm)"
> > elif [ $(uname -r) = "$f" ]; then
> > echo "keeping $f (running kernel) "
> > else
> > echo "removing $f"
> > rm -f "/boot/initramfs-$f.img" "/boot/System.map-$f"
> > rm -f "/boot/vmlinuz-$f" "/boot/config-$f"
> > rm -rf "/lib/modules/$f"
> > new-kernel-pkg --remove $f
> > fi
> > done
> > '
next prev parent reply other threads:[~2016-02-08 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 20:14 Linus Torvalds
2016-02-08 20:22 ` J. Bruce Fields [this message]
2016-02-10 21:05 ` David Rientjes
2016-02-10 21:51 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160208202246.GB18462@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®