All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	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: Sat, 9 Nov 2019 16:43:40 +0530	[thread overview]
Message-ID: <20191109111335.GA1198@Gentoo> (raw)
In-Reply-To: <CAK7LNASvoh1k=vw6DOyTXa5xYDYNT5uH-5YWS=_95t9XwfAgTQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 5048 bytes --]

On 16:25 Sat 09 Nov 2019, Masahiro Yamada wrote:
>On Thu, Nov 7, 2019 at 7:39 AM Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
>>
>> On 14:30 Wed 06 Nov 2019, J. Bruce Fields wrote:
>> >On Wed, Nov 06, 2019 at 10:12:26AM +0530, Bhaskar Chowdhury wrote:
>> >> 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????
>> >
>> >It's just what I happen to use.  If someone wants to make it work
>> >elsewhere that'd be great, as long as we don't break what already works.
>> >
>> >I think Debian uses grub2-mkconfig?  Might be OK for Fedora too, I
>> >dunno.
>> >
>> >--b.
>>
>> Okay , thanks for the input. I was trying to write something in
>> generalize way , that is why my code spins off.And if you see the
>> subject line of my very first attempt to patch written was "removing
>> old kernels and modules dir in selective way"... that was it.
>>
>> Now, there are plenty of distros around, not only rpm based one(yes I do
>> agree that ,you wrote it while using and testing on it, but that is
>> limited in nature),the broader user base might be using something else.
>>
>> we simply can not restrict it to certain packaging version or several
>> packaging versions of selected distros. We are making and building this
>> (worth an effort) to make it as generalized as possible.
>>
>> Importantly I was only thinking of people who put the stuff in standard
>> places in the FSH and use it. I might be wrong.
>>
>> As I have said it before, I was no way trying to bypass your work ,but
>> it seems very limited in nature to adopted. So trying to widen the
>> spectrum.
>>
>> I am trying to incorporating both the pole, different kind user base in
>> mind, like you , who don't like to be prompted for this operation and
>> assuming things should go well, and you are right.
>>
>> On the other hand , I am kinda guy , sometime I need to know what is
>> going on, so the prompting.
>>
>> Well, I have never taken into account about modifying the bootloader
>> config by looking at your work. Had I been, I would have done it already
>> and it would be extremely trivial in nature.
>>
>> Now, Grub, no doubt it's fantastic piece of software, but complexity
>> is paramount with it. Don't you think so???  I HAVE NOTHING AGAINST
>> GRUB!
>>
>> I have personally stops using it for years and using something very
>> rudimentary and simple and useful. That is because I know what I am
>> doing and my system well.
>>
>> Caveat emptor: that was me, not every one else in the wild. Grub is used
>> by the most distro by default,everybody knows it,but certainly not the
>> norm.
>>
>> I would love to give it a stab again and if you better people feel it is
>> necessary, but I need some concrete understanding from you,Masahiro and
>> Randy(who is helping me actively).
>>
>> Say, You people might come up ,
>>
>> We need these :
>>
>> a)
>> b)
>> c)
>>
>> and we don't need these:
>>
>> a)
>> b)
>> c)
>>
>>
>> My two cents! kindly, flame me with your thoughts.
>
>
>Honestly, I did not even know this script
>before you submitted the patch.
>
:)

>I prune stale kernel/modules with my own script,
>and I guess people do similar to meet their demand.
>
I do the same.

>I am not sure how many people are using this.
Only people who look up in the kernel source scripts directory , nobody
else for sure.
>If somebody is passionate to improve this script
>in a simple way, that is fine, but
>I do not want to see messy code for covering various use-cases.
Agreed. That is why need guideline from you people(You, Randy and Bruce
needs to tell me clearly), like what I mentioned, we can do
these and we can not do these. I am asking because you people have had more
exposure ,so might come up with some valid points to build up.
>
>-- 
>Best Regards
>Masahiro Yamada

Thanks,
Bhaskar

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-11-09 11:14 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
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 [this message]
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=20191109111335.GA1198@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.