From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Randy Dunlap <rdunlap@infradead.org>,
Michal Marek <michal.lkml@markovi.net>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scripts:prune-kernel:remove old kernels and modules dir from system
Date: Wed, 6 Nov 2019 10:12:26 +0530 [thread overview]
Message-ID: <20191106044223.GA18076@Gentoo> (raw)
In-Reply-To: <20191106043120.GB6355@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
On 23:31 Tue 05 Nov 2019, J. Bruce Fields wrote:
>On Wed, Nov 06, 2019 at 11:53:28AM +0900, Masahiro Yamada wrote:
>> BTW.
>> Bruce,
>> Does the current script expect RHEL or something?
>> I do not see 'new-kernel-pkg' on my Ubuntu machine.
>
>I test on Fedora. Looks like on recent Fedora that's only provided by
>an rpm "grubby-deprecated", which is an inauspicious name....
>
>I think maybe you're supposed to use "grubby" itself now. Do you have
>that?
>
>> It would still work with 'new-kernel-pkg: command not found'
>> warning.
>>
>> We could bypass it if we like.
>>
>> command -v new-kernel-pkg && new-kernel-pkg --remove $f
>
>Looks like it's what updates the grub configuration, which is probably a
>nice thing to do if you can.
>
>--b.
Bruce,
Two things,
If the system doesn't run grub , how the fallback policy???
This binary "new-kernel-pkg" also missing in other systems too...I can
confirm that... i.e gentoo,slackware,
So , you are only targeting the rpm based system????
~
Bhaskar
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-11-06 4:42 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
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 [this message]
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=20191106044223.GA18076@Gentoo \
--to=unixbhaskar@gmail.com \
--cc=bfields@fieldses.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=rdunlap@infradead.org \
--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).