On Wed, Jul 27, 2022 at 06:47:56AM -0700, Andrew Hewus Fresh wrote:
> On Wed, Jul 27, 2022 at 11:06:39AM +0200, Alexander Hall wrote:
> > I think replacing '*' with '*([![:cntrl:]])' can be the droid your looking
> > for.
>
> As I was falling asleep last night I was trying to figure out how to ge
On Wed, Jul 27, 2022 at 04:15:36PM +0200, Alexander Hall wrote:
>
>
> On July 27, 2022 3:47:56 PM GMT+02:00, Andrew Hewus Fresh
> wrote:
> >On Wed, Jul 27, 2022 at 11:06:39AM +0200, Alexander Hall wrote:
> >> I think replacing '*' with '*([![:cntrl:]])' can be the droid your looking
> >> for.
On July 27, 2022 3:47:56 PM GMT+02:00, Andrew Hewus Fresh
wrote:
>On Wed, Jul 27, 2022 at 11:06:39AM +0200, Alexander Hall wrote:
>> I think replacing '*' with '*([![:cntrl:]])' can be the droid your looking
>> for.
>
>As I was falling asleep last night I was trying to figure out how to get
>
On Wed, Jul 27, 2022 at 11:06:39AM +0200, Alexander Hall wrote:
> I think replacing '*' with '*([![:cntrl:]])' can be the droid your looking
> for.
As I was falling asleep last night I was trying to figure out how to get
'*([!$_nl])' into the match and couldn't think of a good one. Your
solution
On Wed, Jul 27, 2022 at 01:55:58PM +0200, Alexander Hall wrote:
> On a sidenote, the
>
> _nl=$(echo)
>
> in fw_update.sh is AFAICT deceitful and moot, since ksh strips away trailing
> linefeeds. Use the uglier
>
> _nl='
> '
>
> instead.
Correct:
$ _nl=$(echo)
$ printf
On July 27, 2022 11:06:39 AM GMT+02:00, Alexander Hall
wrote:
>On July 27, 2022 12:48:29 AM GMT+02:00, Andrew Hewus Fresh
> wrote:
>>On Sun, Jul 24, 2022 at 10:34:04AM -0700, Andrew Hewus Fresh wrote:
>>> On Sun, Jul 24, 2022 at 09:14:30AM -0700, Andrew Hewus Fresh wrote:
>>> > On Sun, Jul 24
On July 27, 2022 12:48:29 AM GMT+02:00, Andrew Hewus Fresh
wrote:
>On Sun, Jul 24, 2022 at 10:34:04AM -0700, Andrew Hewus Fresh wrote:
>> On Sun, Jul 24, 2022 at 09:14:30AM -0700, Andrew Hewus Fresh wrote:
>> > On Sun, Jul 24, 2022 at 10:01:26AM -0600, Theo de Raadt wrote:
>> > > Jonathan Gray
On Sun, Jul 24, 2022 at 10:34:04AM -0700, Andrew Hewus Fresh wrote:
> On Sun, Jul 24, 2022 at 09:14:30AM -0700, Andrew Hewus Fresh wrote:
> > On Sun, Jul 24, 2022 at 10:01:26AM -0600, Theo de Raadt wrote:
> > > Jonathan Gray wrote:
> > >
> > > > On Sun, Jul 24, 2022 at 08:05:26AM -0600, Theo de R
On Sun, Jul 24, 2022 at 10:34:04AM -0700, Andrew Hewus Fresh wrote:
> I'll try to think about whether I can build a sed program that will
> spit out matches.
Unfortunately the sed version seems to be even slower than matching one
line at a time. Just building the patterns for sed is slower than
On 2022/07/24 10:34, Andrew Hewus Fresh wrote:
> On Sun, Jul 24, 2022 at 09:14:30AM -0700, Andrew Hewus Fresh wrote:
> > On Sun, Jul 24, 2022 at 10:01:26AM -0600, Theo de Raadt wrote:
> > > Jonathan Gray wrote:
> > >
> > > > On Sun, Jul 24, 2022 at 08:05:26AM -0600, Theo de Raadt wrote:
> > > > >
On Sun, Jul 24, 2022 at 09:14:30AM -0700, Andrew Hewus Fresh wrote:
> On Sun, Jul 24, 2022 at 10:01:26AM -0600, Theo de Raadt wrote:
> > Jonathan Gray wrote:
> >
> > > On Sun, Jul 24, 2022 at 08:05:26AM -0600, Theo de Raadt wrote:
> > > > Why not match on cpu0: .*Intel
> > >
> > > I sent a diff
On Sun, Jul 24, 2022 at 10:01:26AM -0600, Theo de Raadt wrote:
> Jonathan Gray wrote:
>
> > On Sun, Jul 24, 2022 at 08:05:26AM -0600, Theo de Raadt wrote:
> > > Why not match on cpu0: .*Intel
> >
> > I sent a diff a month ago with ^cpu0:*Intel(R)
> >
> > semarie mentioned false positives as it
Jonathan Gray wrote:
> On Sun, Jul 24, 2022 at 08:05:26AM -0600, Theo de Raadt wrote:
> > Why not match on cpu0: .*Intel
>
> I sent a diff a month ago with ^cpu0:*Intel(R)
>
> semarie mentioned false positives as it could match another
> Intel device on another line on a non-Intel CPU
>
> http
On Sun, Jul 24, 2022 at 08:05:26AM -0600, Theo de Raadt wrote:
> Why not match on cpu0: .*Intel
I sent a diff a month ago with ^cpu0:*Intel(R)
semarie mentioned false positives as it could match another
Intel device on another line on a non-Intel CPU
https://marc.info/?l=openbsd-tech&m=165579653
> Date: Sun, 24 Jul 2022 15:48:26 +1000
> From: Jonathan Gray
>
> include cpuid 0 string in dmesg for fw_update
>
> Intel CPUs used to have brand strings such as
> cpu0: Intel(R) Pentium(R) M processor 1200MHz ("GenuineIntel" 686-class) 1.20
> GHz
>
Why not match on cpu0: .*Intel
include cpuid 0 string in dmesg for fw_update
Intel CPUs used to have brand strings such as
cpu0: Intel(R) Pentium(R) M processor 1200MHz ("GenuineIntel" 686-class) 1.20
GHz
cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.61 MHz, 06-3d-04
recent CPUs use
cpu0: 11th Gen Intel(R) C
17 matches
Mail list logo