From: "J. Bruce Fields" <bfields@fieldses.org>
To: Dave Jones <davej@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, Peter Anvin <hpa@zytor.com>
Subject: Re: scheduling while atomic & hang.
Date: Wed, 10 Jul 2013 16:54:34 -0400 [thread overview]
Message-ID: <20130710205434.GC22305@fieldses.org> (raw)
In-Reply-To: <20130704074902.GA32211@redhat.com>
On Thu, Jul 04, 2013 at 03:49:02AM -0400, Dave Jones wrote:
> I don't use the auto config, because I end up filling up /boot
> unless I go through and clean them out by hand every time I install
> a new one (which I do probably a dozen or so times a day).
> Is there some easy way to prune old builds I'm missing ?
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:[~2013-07-10 20:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 1:55 scheduling while atomic & hang Dave Jones
2013-07-04 2:49 ` Linus Torvalds
2013-07-04 4:43 ` H. Peter Anvin
2013-07-04 7:49 ` Dave Jones
2013-07-04 17:22 ` Linus Torvalds
2013-07-10 20:54 ` J. Bruce Fields [this message]
2013-07-04 18:08 ` H. Peter Anvin
2013-07-05 6:51 ` Ingo Molnar
2013-07-05 7:19 ` Frederic Weisbecker
2013-07-05 10:05 ` Ingo Molnar
2013-07-05 19:27 ` Linus Torvalds
2013-07-06 8:02 ` Frederic Weisbecker
2013-07-06 8:07 ` Ingo Molnar
2013-07-05 14:38 ` Yet more softlockups Dave Jones
2013-07-05 15:15 ` Thomas Gleixner
2013-07-05 16:00 ` Dave Jones
2013-07-05 16:02 ` Thomas Gleixner
2013-07-05 16:41 ` H. Peter Anvin
2013-07-05 18:20 ` Seiji Aguchi
2013-07-05 22:21 ` Thomas Gleixner
2013-07-06 7:24 ` Ingo Molnar
2013-07-07 0:24 ` Dave Jones
2013-07-10 15:13 ` Dave Jones
2013-07-10 15:20 ` Markus Trippelsdorf
2013-07-10 15:40 ` Dave Jones
2013-07-12 10:31 ` Ingo Molnar
2013-07-12 15:38 ` Dave Hansen
2013-07-12 15:45 ` Dave Jones
2013-07-12 15:55 ` Dave Hansen
2013-07-12 17:00 ` Dave Jones
2013-07-12 17:12 ` David Ahern
2013-07-12 17:18 ` Dave Jones
2013-07-12 17:40 ` David Ahern
2013-07-12 17:50 ` Dave Jones
2013-07-12 18:07 ` David Ahern
2013-07-12 18:22 ` Dave Hansen
2013-07-12 20:13 ` Dave Hansen
2013-07-13 1:40 ` Vince Weaver
2013-07-10 15:39 ` Vince Weaver
2013-07-10 15:45 ` Dave Jones
2013-07-10 21:54 ` Dave Jones
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=20130710205434.GC22305@fieldses.org \
--to=bfields@fieldses.org \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--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