Re: [CentOS] Sound/missing sof firmware in CentOS since 8.4

[Frank Cox]

On Tue, 22 Dec 2020 15:56:49 -0800
Kay Schenk wrote:

> Now on to other issues -- playing .wav files without benefit of GUI.

sox-14.4.2.0-29.el8.x86_64

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Sound/missing sof firmware in CentOS since 8.4

[Kay Schenk]

Hell again --

I finally fixed my no sound with no firmware issue for my built-in Intel 
controlled speakers. I'm running on Stream 8 now. DNF was NOT picking up 
the two alsa packs I needed from -- 
http://mirror.datto.com/CentOS/8-stream/BaseOS/x86_64/os/Packages/ (just 
a random mirror)


But there they were...

alsa-sof-firmware-1.6-1.el8.noarch.rpm 



and

alsa-sof-firmware-debug-1.6-1.el8.noarch.rpm 



So I downloaded the rpms and installed with dnf using

dnf --allowerasing install (path to 
rpm)/alsa-sof-firmware-1.6-1.el8.noarch.rpm 



etc...

This kept my existing alsa main in tact and just added the firmware files.

Now on to other issues -- playing .wav files without benefit of GUI.


On 12/21/20 10:08 AM, Kay Schenk wrote:


Hello all --

I switched to Stream yesterday hoping it would fix some issues I'd 
been having with CentOS 8.4 but alas it did not.


I started out installing 8.2, maybe kernel 4.18.0 -147?, on my laptop 
about 2 months or so ago and the sound worked fine. Now, it does not. 
I seem to be running into this problem...


https://bugzilla.redhat.com/show_bug.cgi?id=1772498

I have located the rpm for this SOF package but as it states in this 
link, it can NOT be installed with my current alsa version. Thoughts? 
Guidance?




--
-
"Don't let anyone dull your sparkle."

MzK

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] question centos stream 8 applying updates

[Sergio Belkin]

El mar, 22 dic 2020 a las 19:46, Sergio Belkin ()
escribió:

>
>
> El mar, 22 dic 2020 a las 18:54, Matthew Miller ()
> escribió:
>
>> On Tue, Dec 22, 2020 at 05:39:57PM -0300, Sergio Belkin wrote:
>> > Edward, thanks for the reply, the tone has changed "if you don't like
>> > CentOS Stream well, you know pay Red Hat".
>> > "If you are using CentOS Linux 8 in a production environment, and are
>> > concerned that CentOS Stream will not meet your needs, we encourage you
>> to
>> > contact Red Hat about options."
>> >
>> > source: https://blog.centos.org/2020/12/future-is-centos-stream/
>>
>>
>> Again, please see
>> https://www.redhat.com/en/blog/faq-centos-stream-updates#Q10
>>
>> The other options being addressed are not all "pay Red Hat".
>>
>> --
>> Matthew Miller
>> 
>> Fedora Project Leader
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>
>
> Let's see the CentOS Description:
> «A *community project* for ecosystem developers who want to see what is
> coming in the next version of RHEL and need to introduce changes that
> enable their hardware or software. It also provides a place to develop
> technologies and tools so they‘re ready for the next version of RHEL»
>
> Definitely, is not a CentOS replacement. Again, everything points to Red
> Hat. I see that the focus is developer. I see no place for sysadmins...
>
> *Sorry I meant "CentOS Stream Description"


-- 
--
Sergio Belkin
LPIC-2 Certified - http://www.lpi.org
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] question centos stream 8 applying updates

[Sergio Belkin]

El mar, 22 dic 2020 a las 18:54, Matthew Miller ()
escribió:

> On Tue, Dec 22, 2020 at 05:39:57PM -0300, Sergio Belkin wrote:
> > Edward, thanks for the reply, the tone has changed "if you don't like
> > CentOS Stream well, you know pay Red Hat".
> > "If you are using CentOS Linux 8 in a production environment, and are
> > concerned that CentOS Stream will not meet your needs, we encourage you
> to
> > contact Red Hat about options."
> >
> > source: https://blog.centos.org/2020/12/future-is-centos-stream/
>
>
> Again, please see
> https://www.redhat.com/en/blog/faq-centos-stream-updates#Q10
>
> The other options being addressed are not all "pay Red Hat".
>
> --
> Matthew Miller
> 
> Fedora Project Leader
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>


Let's see the CentOS Description:
«A *community project* for ecosystem developers who want to see what is
coming in the next version of RHEL and need to introduce changes that
enable their hardware or software. It also provides a place to develop
technologies and tools so they‘re ready for the next version of RHEL»

Definitely, is not a CentOS replacement. Again, everything points to Red
Hat. I see that the focus is developer. I see no place for sysadmins...

-- 
--
Sergio Belkin
LPIC-2 Certified - http://www.lpi.org
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] question centos stream 8 applying updates

[Matthew Miller]

On Tue, Dec 22, 2020 at 05:39:57PM -0300, Sergio Belkin wrote:
> Edward, thanks for the reply, the tone has changed "if you don't like
> CentOS Stream well, you know pay Red Hat".
> "If you are using CentOS Linux 8 in a production environment, and are
> concerned that CentOS Stream will not meet your needs, we encourage you to
> contact Red Hat about options."
> 
> source: https://blog.centos.org/2020/12/future-is-centos-stream/


Again, please see https://www.redhat.com/en/blog/faq-centos-stream-updates#Q10

The other options being addressed are not all "pay Red Hat".

-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] question centos stream 8 applying updates

[Sergio Belkin]

El dom, 20 dic 2020 a las 16:13, Matthew Miller ()
escribió:

> On Sun, Dec 20, 2020 at 10:43:25AM -0300, Sergio Belkin wrote:
> > I feel up to now the predominant tone of communications both fron CentOS
> > and RH is as if CentOS **professional** users were stealing something to
> > RH...
>
> Can you point me to where you are seeing this tone in Red Hat and CentOS
> communications? Because what I see is basically the opposite: Red Hat and
> CentOS saying that's not the motivation at all.
>
> --
> Matthew Miller
> 
> Fedora Project Leader
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

Edward, thanks for the reply, the tone has changed "if you don't like
CentOS Stream well, you know pay Red Hat".
"If you are using CentOS Linux 8 in a production environment, and are
concerned that CentOS Stream will not meet your needs, we encourage you to
contact Red Hat about options."

source: https://blog.centos.org/2020/12/future-is-centos-stream/

Is the PR what introduced the doubt about the CentOS Stream reliability...

I think that Red Hat is in its right to do with CentOS whatever it likes.
However there was a CentOS EOL that Red Hat from one day to the next
decided that it was not convenient to comply, wasn't it?

I think that if Centos Stream is just good enough to use in production
there is no need for Red Hat  advertisements in CentOS announcements. The
CentOS Community already knew that if it wanted guaranteed support and
beyoind it could pay and get Red Hat subscriptions.

At least there was a communication error.

If I'm wrong, let me know.
-- 
--
Sergio Belkin
LPIC-2 Certified - http://www.lpi.org
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Running script before reboot or shutdown

[centos2]

On Tue, Dec 22, 2020, at 10:50, Carlos Lopez wrote:
> Thanks centos2  but regarding your example, I cannot see where you 
> configure that this services needs to be stopped before anyone else

I conveniently overlooked that requirement. I'll have to get back to you on 
that...


> On 22/12/20, 15:22, "CentOS on behalf of cent...@foxengines.net" 
>  wrote:
> 
> Hi,
> 
> On Tue, Dec 22, 2020, at 06:51, Carlos Lopez wrote:
> > I am trying to configure a script as a systemd service to run first 
> when a shutdown or reboot is called. This script execute some scp commands to 
> copy some files to other machines. My actual defined systemd’s file is:
> > 
> > [Unit]
> > Description=Remote copy some files before reboot/shutdown
> > Before=poweroff.target halt.target shutdown.target reboot.target
> > DefaultDependencies=no
> > 
> > [Service]
> > Type=simple
> > ExecStart=/bin/true
> > ExecStop=/usr/local/bin/remote_copy
> > RemainAfterExit=yes
> > 
> > [Install]
> > WantedBy=multi-user.target
> > 
> > But it doesn’t work. “remote_copy” is working when it is executed from 
> root shell. I am using CentOS-8 fully patched release.
> > 
> > Any idea what am I doing wrong?
> 
> I don't have a CentOS 8 machine to test on but on a CentOS 7.9, this 
> works for me:
> 
> /etc/systemd/system/shutdown-test.service
> 
> --
> [Unit]
> Description=Remote copy some files before reboot/shutdown
> 
> [Service]
> Type=oneshot
> ExecStart=/bin/true
> ExecStop=/usr/local/bin/remote_copy
> RemainAfterExit=true
> 
> [Install]
> WantedBy=multi-user.target
> --
> 
> the mode and contents of remote_copy:
> 
> -rwxr-xr-x 1 root root 44 Dec 22 08:23 /usr/local/bin/remote_copy
> 
> --
> #!/bin/bash
> 
> date >> /tmp/remote_copy_result
> --
> 
> After enabling the service and rebooting, I get a file in 
> /tmp/remote_copy_result that contains the date.
> 
> My success is attributable not to me but to this post:
> 
> https://unix.stackexchange.com/questions/39226/how-to-run-a-script-with-systemd-right-before-shutdown
> Your unit file seems similar but when I used it, it didn't work on my 
> CentOS 7.9 system either.
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Running script before reboot or shutdown

[centos2]

On Tue, Dec 22, 2020, at 08:12, cent...@foxengines.net wrote:
> 
> 
> On Tue, Dec 22, 2020, at 07:56, J Martin Rushton via CentOS wrote:
> > This could be the same issue that people run into when designing cron 
> > jobs.  You may only have a limited set of directories on you $PATH 
> 
> Is this a systemd limit? On one of my systems I've got 233 directories (5445 
> non-colon chars) in interactive shell PATH and generally things work fine.

I misunderstood your meaning about the PATH but I understand now. you're 
referring to the default path defined in the shell.
The Bash man page says, "The default path is system-dependent, and is set by 
the administrator who installs bash.", (so the CentOS packager?), and then 
continues on with "A common value is 
``/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin''." That covers 
putting the script in /usr/local/bin, but then, that might not be what's on 
your system. On the CentOS 7.9 system I am working with, the default is:

   /usr/bin:/bin

As reported by a very simple cron job that writes PATH to a file in tmp.
For cron jobs I usually use the full path to the script in the crontab then set 
and export the PATH in the script itself.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Running script before reboot or shutdown

[Carlos Lopez]

Thanks centos2  but regarding your example, I cannot see where you 
configure that this services needs to be stopped before anyone else


On 22/12/20, 15:22, "CentOS on behalf of cent...@foxengines.net" 
 wrote:

Hi,

On Tue, Dec 22, 2020, at 06:51, Carlos Lopez wrote:
> I am trying to configure a script as a systemd service to run first when 
a shutdown or reboot is called. This script execute some scp commands to copy 
some files to other machines. My actual defined systemd’s file is:
> 
> [Unit]
> Description=Remote copy some files before reboot/shutdown
> Before=poweroff.target halt.target shutdown.target reboot.target
> DefaultDependencies=no
> 
> [Service]
> Type=simple
> ExecStart=/bin/true
> ExecStop=/usr/local/bin/remote_copy
> RemainAfterExit=yes
> 
> [Install]
> WantedBy=multi-user.target
> 
> But it doesn’t work. “remote_copy” is working when it is executed from 
root shell. I am using CentOS-8 fully patched release.
> 
> Any idea what am I doing wrong?

I don't have a CentOS 8 machine to test on but on a CentOS 7.9, this works 
for me:

/etc/systemd/system/shutdown-test.service

--
[Unit]
Description=Remote copy some files before reboot/shutdown

[Service]
Type=oneshot
ExecStart=/bin/true
ExecStop=/usr/local/bin/remote_copy
RemainAfterExit=true

[Install]
WantedBy=multi-user.target
--

the mode and contents of remote_copy:

-rwxr-xr-x 1 root root 44 Dec 22 08:23 /usr/local/bin/remote_copy

--
#!/bin/bash

date >> /tmp/remote_copy_result
--

After enabling the service and rebooting, I get a file in 
/tmp/remote_copy_result that contains the date.

My success is attributable not to me but to this post:

https://unix.stackexchange.com/questions/39226/how-to-run-a-script-with-systemd-right-before-shutdown
Your unit file seems similar but when I used it, it didn't work on my 
CentOS 7.9 system either.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Running script before reboot or shutdown

[centos2]

Hi,

On Tue, Dec 22, 2020, at 06:51, Carlos Lopez wrote:
> I am trying to configure a script as a systemd service to run first when a 
> shutdown or reboot is called. This script execute some scp commands to copy 
> some files to other machines. My actual defined systemd’s file is:
> 
> [Unit]
> Description=Remote copy some files before reboot/shutdown
> Before=poweroff.target halt.target shutdown.target reboot.target
> DefaultDependencies=no
> 
> [Service]
> Type=simple
> ExecStart=/bin/true
> ExecStop=/usr/local/bin/remote_copy
> RemainAfterExit=yes
> 
> [Install]
> WantedBy=multi-user.target
> 
> But it doesn’t work. “remote_copy” is working when it is executed from root 
> shell. I am using CentOS-8 fully patched release.
> 
> Any idea what am I doing wrong?

I don't have a CentOS 8 machine to test on but on a CentOS 7.9, this works for 
me:

/etc/systemd/system/shutdown-test.service

--
[Unit]
Description=Remote copy some files before reboot/shutdown

[Service]
Type=oneshot
ExecStart=/bin/true
ExecStop=/usr/local/bin/remote_copy
RemainAfterExit=true

[Install]
WantedBy=multi-user.target
--

the mode and contents of remote_copy:

-rwxr-xr-x 1 root root 44 Dec 22 08:23 /usr/local/bin/remote_copy

--
#!/bin/bash

date >> /tmp/remote_copy_result
--

After enabling the service and rebooting, I get a file in 
/tmp/remote_copy_result that contains the date.

My success is attributable not to me but to this post:
https://unix.stackexchange.com/questions/39226/how-to-run-a-script-with-systemd-right-before-shutdown
Your unit file seems similar but when I used it, it didn't work on my CentOS 
7.9 system either.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Running script before reboot or shutdown

[centos2]

On Tue, Dec 22, 2020, at 07:56, J Martin Rushton via CentOS wrote:
> This could be the same issue that people run into when designing cron 
> jobs.  You may only have a limited set of directories on you $PATH 

Is this a systemd limit? On one of my systems I've got 233 directories (5445 
non-colon chars) in interactive shell PATH and generally things work fine.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Running script before reboot or shutdown

[J Martin Rushton via CentOS]

This could be the same issue that people run into when designing cron 
jobs.  You may only have a limited set of directories on you $PATH and 
other environment variables may be missing.  If this is the case, ensure 
that you define the full path to utilies:


MYPROG="/home/carlos/myprog"
$MYPROG -h

rather than

myprog -h

HTH, and BTW you can still use init scripts if it is easier.

On 22/12/2020 11:51, Carlos Lopez wrote:

Hi all,

I am trying to configure a script as a systemd service to run first when a 
shutdown or reboot is called. This script execute some scp commands to copy 
some files to other machines. My actual defined systemd’s file is:

[Unit]
Description=Remote copy some files before reboot/shutdown
Before=poweroff.target halt.target shutdown.target reboot.target
DefaultDependencies=no

[Service]
Type=simple
ExecStart=/bin/true
ExecStop=/usr/local/bin/remote_copy
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

But it doesn’t work. “remote_copy” is working when it is executed from root 
shell. I am using CentOS-8 fully patched release.

Any idea what am I doing wrong?

Regards,
C. L. Martinez
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



--
J Martin Rushton MBCS
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-announce Digest, Vol 189, Issue 5

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CESA-2020:5437 Important CentOS 7 kernel Security Update
  (Johnny Hughes)
   2. CESA-2020:5618 Important CentOS 7 thunderbird Security Update
  (Johnny Hughes)


--

Message: 1
Date: Mon, 21 Dec 2020 20:45:16 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2020:5437 Important CentOS 7 kernel
SecurityUpdate
Message-ID: <20201221204516.ga14...@bstore1.rdu2.centos.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2020:5437 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2020:5437

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
d9c97d1412cfdb3b24b2aca08bec9bed63be4db9461f19ba0eef840ad48dc19e  
bpftool-3.10.0-1160.11.1.el7.x86_64.rpm
d1b44c5bcb094399e0bce41de4218e28b8f69fb0c0a79c24411b5561978ec6b5  
kernel-3.10.0-1160.11.1.el7.x86_64.rpm
7804215d9e8fd6eaae4ae7d7fb360dd0ec85e87ed93ec488ef3d1cb1285ff33e  
kernel-abi-whitelists-3.10.0-1160.11.1.el7.noarch.rpm
ea590d364a03624b219bdbcff4119983ab7a1bd31a6a7146afb0d4e684761056  
kernel-debug-3.10.0-1160.11.1.el7.x86_64.rpm
e3d2e5a0802cde0d09552d1bd3102383e1851a9aecf88fd83a5fb81baae6d53c  
kernel-debug-devel-3.10.0-1160.11.1.el7.x86_64.rpm
c59ce9d5e2b28c278b947391fce0c591d912b04727d6141c27262cf98fb99844  
kernel-devel-3.10.0-1160.11.1.el7.x86_64.rpm
81b2e85bd83c8dc868290121adb4b8821c2da304dd04a69ec5ea65031c46d351  
kernel-doc-3.10.0-1160.11.1.el7.noarch.rpm
1bab4a2f960faa0a69de616785116c776e018a15bdc67d8f57416af2a12896db  
kernel-headers-3.10.0-1160.11.1.el7.x86_64.rpm
7eafe5ff654144eafe243a63bd26f5f8be857f9a6db277149949bba5f768b643  
kernel-tools-3.10.0-1160.11.1.el7.x86_64.rpm
c91dc3bbc7593fb7442fa9ec947f30d95bad094d5b4180e4669380d535253bb7  
kernel-tools-libs-3.10.0-1160.11.1.el7.x86_64.rpm
97ca74d50cef86200eaedf11cbb46855b4d2c943de9de770a9b024fbbf90ce3d  
kernel-tools-libs-devel-3.10.0-1160.11.1.el7.x86_64.rpm
ab2758dd1426e326fee61bd2598d1e3e1099478f8620ffce7bed64945dec78b0  
perf-3.10.0-1160.11.1.el7.x86_64.rpm
5c6e935d06978bc962ba371367424881edecc7735e2833f96a64554589179077  
python-perf-3.10.0-1160.11.1.el7.x86_64.rpm

Source:
c3328f1a8ce4d799b7893d3d4a97185e1ade473ec7f695903132b7d1161a634e  
kernel-3.10.0-1160.11.1.el7.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS



--

Message: 2
Date: Mon, 21 Dec 2020 20:46:06 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2020:5618 Important CentOS 7
thunderbird Security Update
Message-ID: <20201221204606.ga14...@bstore1.rdu2.centos.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2020:5618 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2020:5618

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
de7c7cd5bd6465116843083e7515695b436a00a145d6c705355b3e74a55e2b6b  
thunderbird-78.6.0-1.el7.centos.x86_64.rpm

Source:
507628ef1d57a01ff641a1a48d05c99111c6edb3cdf78419fd812dbc2523  
thunderbird-78.6.0-1.el7.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS



--

Subject: Digest Footer

___
CentOS-announce mailing list
centos-annou...@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce


--

End of CentOS-announce Digest, Vol 189, Issue 5
***
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Running script before reboot or shutdown

[Carlos Lopez]

Hi all,

I am trying to configure a script as a systemd service to run first when a 
shutdown or reboot is called. This script execute some scp commands to copy 
some files to other machines. My actual defined systemd’s file is:

[Unit]
Description=Remote copy some files before reboot/shutdown
Before=poweroff.target halt.target shutdown.target reboot.target
DefaultDependencies=no

[Service]
Type=simple
ExecStart=/bin/true
ExecStop=/usr/local/bin/remote_copy
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

But it doesn’t work. “remote_copy” is working when it is executed from root 
shell. I am using CentOS-8 fully patched release.

Any idea what am I doing wrong?

Regards,
C. L. Martinez
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos