From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: bfields@fieldses.org, yamada.masahiro@socionext.com,
michal.lkml@markovi.net, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts:prune-kernel:remove old kernels and modules dir from system
Date: Mon, 4 Nov 2019 18:03:13 -0800 [thread overview]
Message-ID: <50680c37-9e85-0050-c1e1-700260a0471c@infradead.org> (raw)
In-Reply-To: <20191102063036.28601-1-unixbhaskar@gmail.com>
On 11/1/19 11:30 PM, Bhaskar Chowdhury wrote:
> This patch allow you to remove old kernels and associated modules
> directory from the system.You can do it at once with the -r flag
> and interactively with the -i flag.
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> scripts/prune-kernel | 82 +++++++++++++++++++++++++++++++++++---------
> 1 file changed, 65 insertions(+), 17 deletions(-)
Hi,
I believe that this script now does what the patch author intends it to do.
It does have a few whitespace issues, but no big deals. (see below)
Tested-by: Randy Dunlap <rdunlap@infradead.org>
> diff --git a/scripts/prune-kernel b/scripts/prune-kernel
> index e8aa940bc0a9..01d0778db71f 100755
> --- a/scripts/prune-kernel
> +++ b/scripts/prune-kernel
> @@ -1,21 +1,69 @@
> #!/bin/bash
> # SPDX-License-Identifier: GPL-2.0
> +#This script will remove old kernels and modules directory related to it.
> +#"-r" or "--remove" show how to silently remove old kernel and modules dir.
> +# "-h" or "--help" show how to use this script or show without parameter.
> +#"-i" or "--interactive" show how to remove interactively.
> +
> +flag=$1
> +kernel_version=$2
> +modules_version=$3
> +boot_dir=/boot
> +modules_dir=/lib/modules
> +
> +remove_old_kernel() {
> + cd $boot_dir
> + rm -If vmlinuz-$kernel_version System.map-$kernel_version config-$kernel_version
> + return 0
> +}
> +
> +remove_old_modules_dir() {
> + cd $modules_dir
> + rm -rf $modules_version
> + return 0
> +}
> +
> +usage() {
> + printf "Usage: $(basename $0) [-ri]\n"
> + printf "\n -r or --remove kernel_version modules_version\n"
> + printf "\n -i or --interactive do as interactive way\n"
> + return 0
> +}
> +
> +case "$flag" in
> + -i | --interactive)
> + printf "\nEnter kernel version to remove or blank/empty to exit:"
> + read kernel_version
> + if [[ $kernel_version != "" ]]; then
> + remove_old_kernel
> + printf "\nRemoved kernel version:$kernel_version from the system.\n\n"
space after ':'
drop one \n above.
> + printf "Please give the full modules directory name to remove:"
> + read modules_version
> + if [[ $modules_version != "" ]]; then
> + remove_old_modules_dir
> + printf "\n\nRemoved modules directory:$modules_version from the system.\n\n"
space after ':'
drop one \n above.
> + else
> + exit 1
> + fi
> + fi
> + ;;
> + -h | --help)
> + usage
> + exit 0
> + ;;
> + -r | --remove)
> + if [[ $# -ne 3 ]]; then
> + printf "You need to provide kernel version and modules directory name.\n"
> + exit 1
> + else
> + remove_old_kernel
> + remove_old_modules_dir
> + fi
> + ;;
> + *)
> + usage
> + exit 1
> + ;;
> +esac
>
> -# 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:
>
OK, the former script's loop is removed.. good.
But the 2 preceding blank lines are not removed, so the script
now ends with 2 unnecessary blank lines.
> -for f in "$@"
> -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
> --
--
~Randy
next prev parent reply other threads:[~2019-11-05 2:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 6:30 [PATCH] scripts:prune-kernel:remove old kernels and modules dir from system Bhaskar Chowdhury
2019-11-05 2:03 ` Randy Dunlap [this message]
2019-11-05 2:32 ` J. Bruce Fields
2019-11-05 4:39 ` Bhaskar Chowdhury
2019-11-05 4:52 ` Bhaskar Chowdhury
2019-11-06 2:53 ` Masahiro Yamada
2019-11-06 3:10 ` Bhaskar Chowdhury
2019-11-06 4:03 ` Masahiro Yamada
2019-11-06 4:29 ` Bhaskar Chowdhury
2019-11-06 4:31 ` J. Bruce Fields
2019-11-06 4:32 ` Randy Dunlap
2019-11-06 4:42 ` Bhaskar Chowdhury
2019-11-06 19:30 ` J. Bruce Fields
2019-11-06 22:39 ` Bhaskar Chowdhury
2019-11-09 7:25 ` Masahiro Yamada
2019-11-09 11:13 ` Bhaskar Chowdhury
2019-11-15 1:58 ` Masahiro Yamada
2019-11-15 15:21 ` Bhaskar Chowdhury
2019-11-18 7:30 ` Masahiro Yamada
2019-11-05 4:33 ` Bhaskar Chowdhury
-- strict thread matches above, loose matches on Subject: below --
2019-10-30 9:54 [PATCH] scripts: prune-kernel:remove " Bhaskar Chowdhury
2019-10-31 2:33 ` Randy Dunlap
2019-10-31 3:37 ` Bhaskar Chowdhury
2019-10-31 4:32 ` Randy Dunlap
2019-10-31 4:52 ` Bhaskar Chowdhury
2019-10-31 5:27 ` Randy Dunlap
2019-10-31 7:18 ` Bhaskar Chowdhury
2019-10-31 15:06 ` Randy Dunlap
2019-11-01 4:23 ` Bhaskar Chowdhury
2019-11-01 5:11 ` Bhaskar Chowdhury
2019-11-01 5:45 ` Randy Dunlap
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=50680c37-9e85-0050-c1e1-700260a0471c@infradead.org \
--to=rdunlap@infradead.org \
--cc=bfields@fieldses.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=unixbhaskar@gmail.com \
--cc=yamada.masahiro@socionext.com \
/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;
as well as URLs for NNTP newsgroup(s).