1. Forum
  2. FidoNet
  3. ALT.OS.LINUX.MAGEIA

  • fwupdmgr

    From faeychild@2:250/1 to All on Sun Feb 9 02:30:48 2025


    I discover when I blundered into firmware security, this was not
    installed. I didn't find it in the package manager either.

    This is a diversion of course. I found it looking for other stuff.

    eg;
    My kernel messages claim a fail for mdmonitor which seems to be for raid software, which I don't run.
    So I went looking for that program which use to allow stopping, starting
    and starting at boot of all processes.
    I thought if there is a mdmonitor entry I'll just stop it.

    I couldn't find that program.. Is it deprecated?

    --
    faeychild
    Running kde on 6.6.74-desktop-1.mga9 kernel.
    Mageia release 9 (Official) for x86_64


    --- MBSE BBS v1.1.0 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun Feb 9 02:55:37 2025
    On 9/2/25 13:30, faeychild wrote:


    I discover when I blundered into firmware security, this was not
    installed. I didn't find it in the package manager either.

    This is a diversion of course. I found it looking for other stuff.

    eg;
    My kernel messages claim a fail for mdmonitor which seems to be for raid software, which I don't run.
    So I went looking for that program which use to allow stopping, starting
    and starting at boot of all processes.
    I thought if there is a mdmonitor entry I'll just stop it.

    I couldn't find that program.. Is it deprecated?



    OK there is a similar deal (not as flexible) under "System Monitor > Processes"
    It doesn't list mdmonitor.


    I'm not playing this game today

    This is another Sunday bypass.
    I was passing by the computer and decided to stupidly check up on the
    kernel ndmonitor message
    And this morphed into a search of MGA6 to find "KSysguard" and then back
    to MGA9 where it no longer exists and all this started.

    Why do I do this to myself?? I'm walking away, really watch me. :-)
    I've gone..........

    --
    faeychild
    Running kde on 6.6.74-desktop-1.mga9 kernel.
    Mageia release 9 (Official) for x86_64

    --- MBSE BBS v1.1.0 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun Feb 9 21:42:19 2025
    On 9/2/25 16:50, David W. Hodgins wrote:

    # urpmf fwupdmgr|grep bin/|sort -u
    fwupd:/usr/bin/fwupdmgr

    # urpmf mdmonitor|grep service|sort -u mdadm:/usr/lib/systemd/system/mdmonitor.service mdadm:/usr/lib/systemd/system/mdmonitor-takeover.service

    So "urpmi fwupd", and "systemctl disable mdmonitor.service".

    Regards, Dave Hodgins



    excellent! That is what I was hoping to achieve with "KsysGuard"
    curiously when I ran your command

    ~]$ urpmf mdmonitor|grep service|sort -u

    http://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/media_info/20230819-212352-files.xml.lzma

    http://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/updates/media_info/20250209-000133-files.xml.lzma
    <snip>

    http://mirror.math.princeton.edu/pub/mageia/distrib/9/i586/media/tainted/updates/media_info/20250205-192226-files.xml.lzma
    mdadm:/usr/lib/systemd/system/mdmonitor.service

    mdadm:/usr/lib/systemd/system/mdmonitor-takeover.service

    I got this long list, so, I thought "spaces" around the pipe

    so I ran this

    urpmf mdmonitor | grep service|sort -u mdadm:/usr/lib/systemd/system/mdmonitor.service mdadm:/usr/lib/systemd/system/mdmonitor-takeover.service

    and got your result
    Then I ran the original command

    urpmf mdmonitor|grep service|sort -u mdadm:/usr/lib/systemd/system/mdmonitor.service mdadm:/usr/lib/systemd/system/mdmonitor-takeover.service

    and still got your result

    The same command gives different results.
    I assume that the .xml files had to download the first time. spaces had nothing to do with it. I am momentarily delusional
    the command line can be very instructive

    Thanks David
    Regards
    --
    faeychild
    Running kde on 6.6.74-desktop-1.mga9 kernel.
    Mageia release 9 (Official) for x86_64

    --- MBSE BBS v1.1.0 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Tue Feb 11 17:34:47 2025
    On Mon, 10 Feb 2025 10:13:35 -0500, Jim <jim.beard@verizon.net> wrote:
    <snip>
    I do not have raid in use on any of my machines. Should mdmonitor be running ?

    For people who need it, if it's not enabled their system will not boot. For those who don't, it
    just causes the journal message, and a slight delay booting.

    It isn't disabled automatically for people who are not currently using it, as they may attach
    other drives that are set up to use it.

    Do I need to set xml meta data download to always in drakrpm-edit-media, under Options, then Global options ?

    Open a terminal, enter "su -" to become root. Enter the command drakrpm-edit-media.

    In drakrpm-edit-media, use the mouse to select Options. That opens a popup menu with various
    entries, one of which is Global options. When Global options is selected, there are three entries that
    can set.

    1 Verify RPMS... - Can be set to never or always.

    I prefer to have the rpm packages verified at download. Setting it to never makes things faster.
    The rpm packages are still verified when they are installed, so setting it to never does not impact
    security, it just delays finding a download problem.

    2 Download program ...

    I prefer using wget. Depending on the mirror you use, other options (curl or aria2) may be
    preferred.

    3 XML ... download ...

    Of the options available, I prefer to select "Always" so that if I later run a urpmq or urpmf
    command I don't have to wait for the download.

    People who never or rarely use the urpmq or urpmf commands will likely prefer to download
    the xml data only when needed. I use them enough I prefer to let checking for updates take
    a little longer so I'm not left waiting when I am sitting there running a command waiting for
    the output.

    Regards, Dave Hodgins

    --- MBSE BBS v1.1.0 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Tue Feb 11 17:38:37 2025
    On Tue, 11 Feb 2025 12:34:47 -0500, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:

    On Mon, 10 Feb 2025 10:13:35 -0500, Jim <jim.beard@verizon.net> wrote:
    <snip>
    I do not have raid in use on any of my machines. Should mdmonitor be running ?

    For people who need it, if it's not enabled their system will not boot. For those who don't, it
    just causes the journal message, and a slight delay booting.

    It isn't disabled automatically for people who are not currently using it, as they may attach
    other drives that are set up to use it.

    Forgot to add ...

    If you are not currently using raid, and have no plans to use it later, disable it.

    Don't worry about the mdmonitor-takeover service. It does nothing (just starts/stops) if
    the mdmonitor.service has been disabled.

    Regards Dave Hodgins

    --- MBSE BBS v1.1.0 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)