On Thu, Jun 3, 2021 at 3:19 PM Patrick O'Callaghan
wrote:
>
> On Thu, 2021-06-03 at 12:51 -0600, Joe Zeff wrote:
> > On 6/3/21 12:20 PM, Jon LaBadie wrote:
> > >
> > > Are old rescue kernels still useful? (6 years?)
> >
> > They're still just as useful as they were when they were installed.
> > O
On Fri, 2021-06-04 at 14:46 +0930, Tim via users wrote:
> On Thu, 2021-06-03 at 17:23 -0600, Chris Murphy wrote:
> > What I would like to see is (a) an initramfs that can boot a
> > graphical stack (b) contains the Live OS dracut modules (c) and
> > overlayfs, and wire it up so that the rescue boot
On Fri, 4 Jun 2021 at 02:51, Jon LaBadie wrote:
> On Thu, Jun 03, 2021 at 03:48:29PM -0600, Joe Zeff wrote:
>
> But I believe POC's point was not about BTRFS specifically,
> but that something could have changed over the years to make
> an old rescue kernel unusable.
>
> If you accept that premis
On Thu, Jun 3, 2021, at 11:20 AM, Jon LaBadie wrote:
> On my 3 systems, F34, F34, and CentOS7, they are
> 1, 2, and 6 years old respectively.
>
> Are old rescue kernels still useful? (6 years?)
>
> Are there automated or manual procedures to update
> a rescue kernel?
>
> Are there best practice
On Fri, Jun 04, 2021 at 07:35:54AM -0700, Doug H. wrote:
On Thu, Jun 3, 2021, at 11:20 AM, Jon LaBadie wrote:
On my 3 systems, F34, F34, and CentOS7, they are
1, 2, and 6 years old respectively.
Are old rescue kernels still useful? (6 years?)
Are there automated or manual procedures to update
Hello,
Sorry, I am a bit of list
This command line works in a shell, but not in a bash
I may miss some quotes !
Thanks for your help.
/usr/bin/rm -v !(ZMAT*|out*|Out*|GENBAS|Note*)
===
Patrick DUPRÉ
Patrick,
The structure within the paren's looks like what would be used for a 'grep -Ev'
to find everything BUT that mix of patterns.
Can you explain what it is you are attempting to do, and provide some context,
please.
Thank you.-Joe
On Friday, June 4, 2021, 2:14:53 PM EDT, Patrick Dupre
I would have coded it this way:
/usr/bin/rm -v `ls -1|egrep -ve '(^ZMAT|^out|^Out|^GENBAS|^Note)'`
And bash is a shell, but you mean a script. Likely in interactive bash the
* are getting expanded so you might have to use noglob to suppress it or
something similar.
Or you might have to use a sin
[jwesterd@jwesterd-f33 aaa]$ ls -1
a
b
c
d
e
f
[jwesterd@jwesterd-f33 aaa]$ /usr/bin/rm -v !(a*|b*|c*|d*|e*)
removed 'f'
[jwesterd@jwesterd-f33 aaa]$ ls -1
a
b
c
d
e
[jwesterd@jwesterd-f33 aaa]$ echo $0
bash
seems to work?
Are there asterisks or quotes in the files you are affecting?
Cheers
On 6/4/21 12:21 PM, Joe Wulf via users wrote:
The structure within the paren's looks like what would be used for a
'grep -Ev' to find everything BUT that mix of patterns.
Checking with the man page, I find that -v stands for verbose, telling
you what's happening.
_
On 2021-06-04 12:04 p.m., Joe Zeff wrote:
On 6/4/21 12:21 PM, Joe Wulf via users wrote:
The structure within the paren's looks like what would be used for a
'grep -Ev' to find everything BUT that mix of patterns.
Checking with the man page, I find that -v stands for verbose, telling
you what'
Hello Joe,
On Fri, 4 Jun 2021 13:04:20 -0600 Joe Zeff wrote:
> On 6/4/21 12:21 PM, Joe Wulf via users wrote:
> > The structure within the paren's looks like what would be used for a >
> > 'grep -Ev' to find everything BUT that mix of patterns.
>
> Checking with the man page, I find that -v
It works fine in a command line,
but in a script, I get
#!/bin/bash
/usr/bin/rm -v !(GENBAS|fja.*|run.sh|test.sh|ZMAT*|out*)
./test.sh: line 2: syntax error near unexpected token `('
./test.sh: line 2: `/usr/bin/rm -v !(GENBAS|fja.*|run.sh|test.sh|ZMAT*|out*)'
[jwesterd@jwesterd-f
On 6/4/21 1:11 PM, Samuel Sieb wrote:
Which man page? For grep, the "-v" is for inverting the result to only
show non-matching lines.
The man page for rm, of course. Why would I suggest that you look at
any other command's man page to find out what an option for rm means?
On 6/4/21 1:17 PM, wwp wrote:
-V, --version
-v, --invert-match
Yes, that's true for grep, but we're discussing rm here.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedorapr
Hi,
Patrick Dupre wrote:
> Sorry, I am a bit of list
> This command line works in a shell, but not in a bash
> I may miss some quotes !
> Thanks for your help.
>
> /usr/bin/rm -v !(ZMAT*|out*|Out*|GENBAS|Note*)
The !(ZMAT*|...) syntax requires the bash extglob option.
This must be explicitly ena
Fantastic,
Thanks.
How can I leave this mode extglob ?
>
> Patrick Dupre wrote:
> > Sorry, I am a bit of list
> > This command line works in a shell, but not in a bash
> > I may miss some quotes !
> > Thanks for your help.
> >
> > /usr/bin/rm -v !(ZMAT*|out*|Out*|GENBAS|Note*)
>
> The !(ZMAT*|...
On 2021-06-04 12:36 p.m., Joe Zeff wrote:
On 6/4/21 1:11 PM, Samuel Sieb wrote:
Which man page? For grep, the "-v" is for inverting the result to
only show non-matching lines.
The man page for rm, of course. Why would I suggest that you look at
any other command's man page to find out wha
On 2021-06-04 1:00 p.m., Patrick Dupre wrote:
How can I leave this mode extglob ?
Do you need to? It will only apply to the rest of the script anyway.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...
Could you not simply \ escape the ! ?
On Fri, Jun 4, 2021, 3:05 PM Samuel Sieb wrote:
> On 2021-06-04 12:36 p.m., Joe Zeff wrote:
> > On 6/4/21 1:11 PM, Samuel Sieb wrote:
> >>
> >> Which man page? For grep, the "-v" is for inverting the result to
> >> only show non-matching lines.
> >
> > The
Samuel Sieb wrote:
> On 2021-06-04 1:00 p.m., Patrick Dupre wrote:
>> How can I leave this mode extglob ?
>
> Do you need to? It will only apply to the rest of the script anyway.
True.
Though depending on the size of the script and what else it
does, there are certainly times when you don't wan
On 6/4/21 2:05 PM, Samuel Sieb wrote:
You removed your text when quoting my email. In the email I replied to,
you were quoting the grep line. No mention of rm at all.
We were, and are discussing the way rm acts in a shell script, so I
expected that rm was the implied command.
On Fri, Jun 04, 2021 at 10:00:17PM +0200, Patrick Dupre wrote:
Patrick Dupre wrote:
> Sorry, I am a bit of list
> This command line works in a shell, but not in a bash
> I may miss some quotes !
> Thanks for your help.
>
> /usr/bin/rm -v !(ZMAT*|out*|Out*|GENBAS|Note*)
The !(ZMAT*|...) syntax r
Joe Zeff wrote:
> On 6/4/21 2:05 PM, Samuel Sieb wrote:
>>
>> You removed your text when quoting my email. In the email I replied to,
>> you were quoting the grep line. No mention of rm at all.
>
> We were, and are discussing the way rm acts in a shell script, so I expected
> that rm was the im
Doug H. writes:
3. Delete the "rescue" stuff in /boot and /boot/loader/entries/
We should have a canned wrapper for this. We already have
dnf config-manager --set-enabled repo
to simply flip a single character in a .conf file.
It will be helpful in avoiding typos to have something similar,
25 matches
Mail list logo
