hallo I usallay run vanilla kernels and build them with a suffix "_MY" to save some works when cleaning /boot if that kernels gets outdated and a new one gets installed.
/boot looks like this ll /boot : ... -rw-------. 1 root root 20M 22. Jun 15:04 initramfs-5.1.14_MY.img -rw-r--r--. 1 root root 4,7M 22. Jun 15:04 System.map-5.1.14_MY -rw-r--r--. 1 root root 15M 22. Jun 15:04 vmlinuz-5.1.14_MY ... and ll /boot/loader/ : drwx------. 2 root root 4,0K 22. Jun 15:04 entries
and sudo ls -l /boot/loader/entries/ : -rw-r--r--. 1 root root 242 22. Jun 15:04 0637b2e09df64d90bd0c13dc10d1da70-5.1.14_MY.conf
to clean /boot a use a script:
#!/bin/bash set -vx; sudo rm -rf /boot/loader/entries/*MY*; sudo rm -rf /boot/*MY* /lib/modules/*MY*; sudo grub2-mkconfig -o /boot/grub2/grub.cfg;
and now my problem: the first sudo rm -rfv command does NOTHING, means the loader entry is still there and I need to rm it by hand. whereas the second rm command does what I espect.
What I'm doing wrong / where is the/my bug ?
On 6/22/19 10:31 AM, sixpack13 wrote:
sudo rm -rf /boot/loader/entries/*MY*; sudo rm -rf /boot/*MY* /lib/modules/*MY*; sudo grub2-mkconfig -o /boot/grub2/grub.cfg;
Side point, you don't need semicolons at the end. Those are only to separate commands on the same line.
and now my problem: the first sudo rm -rfv command does NOTHING, means the loader entry is still there and I need to rm it by hand. whereas the second rm command does what I espect.
You are getting tricked by a common misunderstanding. The expansion of wildcards is done by the shell before running the command and rm only uses exactly what it is given. As a user, you don't have permission to look in the entries directory. That means that the wildcards are passed directly to rm as-is because the shell can't find any matches. rm doesn't find a file with a name called literally "*MY*", so it doesn't delete anything.
Hi.
On Sat, 22 Jun 2019 11:06:38 -0700 Samuel Sieb wrote:
On 6/22/19 10:31 AM, sixpack13 wrote:
sudo rm -rf /boot/loader/entries/*MY*;
An alternate solution which I should have included in the other email is: sudo bash -c "rm -rf /boot/loader/entries/*MY*"
Right.
And you can also remove the -r option since those entries are not directories.
On 6/22/19 11:15 AM, Francis.Montagnac@inria.fr wrote:
On Sat, 22 Jun 2019 11:06:38 -0700 Samuel Sieb wrote:
On 6/22/19 10:31 AM, sixpack13 wrote:
sudo rm -rf /boot/loader/entries/*MY*;
An alternate solution which I should have included in the other email is: sudo bash -c "rm -rf /boot/loader/entries/*MY*" And you can also remove the -r option since those entries are not
directories.
Oops, I had intended to do that, but then I just copy and pasted. :-)
thanks $ALL
bash -c ...
did the trick !
P.S. I forebode (right word/spelt ?) it already that the combination of user rights and expansion was my bug, but didn't know how to fix.
On Sat, 2019-06-22 at 19:37 +0000, sixpack13 wrote:
thanks $ALL
bash -c ...
did the trick !
P.S. I forebode (right word/spelt ?) it already that the combination of user rights and expansion was my bug, but didn't know how to fix.
You probably mean "foresaw". "Forebode" is technically correct but that usage is uncommon. It normally means to have a premonition (i.e. a "foreboding").
poc
On 6/23/19 5:54 PM, Patrick O'Callaghan wrote:
On Sat, 2019-06-22 at 19:37 +0000, sixpack13 wrote:
thanks $ALL
bash -c ...
did the trick !
P.S. I forebode (right word/spelt ?) it already that the combination of user rights and expansion was my bug, but didn't know how to fix.
You probably mean "foresaw". "Forebode" is technically correct but that usage is uncommon. It normally means to have a premonition (i.e. a "foreboding").
And I would use none of those terms.
I would have said "I understood it already...." or "I realized it already....", or even "I knew it already...".
*My* reason is that I find "forebode" and "foresaw" as anachronistic in conversational English. I can't recall a time that I have used those words. I can only recall seeing them in literary works of previous generations. :-)
On Sun, 2019-06-23 at 18:36 +0800, Ed Greshko wrote:
On 6/23/19 5:54 PM, Patrick O'Callaghan wrote:
On Sat, 2019-06-22 at 19:37 +0000, sixpack13 wrote:
thanks $ALL
bash -c ...
did the trick !
P.S. I forebode (right word/spelt ?) it already that the combination of user rights and expansion was my bug, but didn't know how to fix.
You probably mean "foresaw". "Forebode" is technically correct but that usage is uncommon. It normally means to have a premonition (i.e. a "foreboding").
And I would use none of those terms.
I would have said "I understood it already...." or "I realized it already....", or even "I knew it already...".
*My* reason is that I find "forebode" and "foresaw" as anachronistic in conversational English. I can't recall a time that I have used those words. I can only recall seeing them in literary works of previous generations. :-)
This may be culturally-specific. Although I don't recall forbode ever being used (even in literary English) other than in the specific form "foreboding", foresee and its derivatives such as foresaw, foreseen, unforeseen etc. are everyday terms where I come from (Ireland/UK).
That said, you're probably right about what the OP actually meant.
poc
I guess "foresaw it" explains it at best.
In german it's called "Ahnung".
A sort of "partly (!) knowledge", not exclusively rational (maybe a feel or an idea), what's going on, but without a / the deep, 100 % clearness to name it "realized / knew / understood it".
But this thread goes philosophic ... and the solution was found already.
Thanks again !
On 23Jun2019 18:36, Ed Greshko ed.greshko@greshko.com wrote:
On 6/23/19 5:54 PM, Patrick O'Callaghan wrote:
On Sat, 2019-06-22 at 19:37 +0000, sixpack13 wrote:
I forebode (right word/spelt ?) it already that the combination of user rights and expansion was my bug, but didn't know how to fix.
You probably mean "foresaw". "Forebode" is technically correct but that usage is uncommon. It normally means to have a premonition (i.e. a "foreboding").
And I would use none of those terms.
Surely "neither", not "none". Though like "forebode", "none" is technically correct as well.
I would have said "I understood it already...." or "I realized it already....", or even "I knew it already...".
But did the OP know? Or did xe just feel that oncoming?
*My* reason is that I find "forebode" and "foresaw" as anachronistic in conversational English. I can't recall a time that I have used those words. I can only recall seeing them in literary works of previous generations. :-)
That is a self fulfilling prophesy. Quite forbidding in its outlook.
Cheers, Cameron Simpson cs@cskk.id.au
On Sun, 2019-06-23 at 18:36 +0800, Ed Greshko wrote:
I forebode (right word/spelt ?) it already that the combination of user rights and expansion was my bug, but didn't know how to fix.
You probably mean "foresaw". "Forebode" is technically correct but that usage is uncommon. It normally means to have a premonition (i.e. a "foreboding").
And I would use none of those terms.
I would have said "I understood it already...." or "I realized it already....", or even "I knew it already...".
*My* reason is that I find "forebode" and "foresaw" as anachronistic in conversational English. I can't recall a time that I have used those words. I can only recall seeing them in literary works of previous generations. :-)
Forbode can only be used about something else, not oneself: "a dark cloud forbodes a tornado" is correct, but a "I forbode wrath" is not (except when forbode is the past tense of forbid -- not the usage here). "Forbode" is truly obselete. See: https://www.yourdictionary.com/forbode
On the other hand "foresaw" sounds quite natural to me; but I was born in 1940 (8-).
On Tue, 25 Jun 2019 10:56:29 -0600 Joe Zeff joe@zeff.us wrote:
On 06/25/2019 02:47 AM, Jonathan Ryshpan wrote:
(except when forbode is the past tense of forbid -- not the usage here).
The past tense of forbid is forbade.
Forbode obsolete forms of forbidden, past participle of forbid
-
Cameron Simpson -
Ed Greshko -
Francis.Montagnac＠inria.fr -
Joe Zeff -
Jonathan Ryshpan -
Patrick O'Callaghan -
Peter Reed -
Samuel Sieb -
sixpack13