apt run via shell asks for user decision on changed configuration files including the ones managed by OMV - apt config possible to prevent this?

    • Offizieller Beitrag

    Why do you consider this to be "hamful"? Can you provide an example?

    I deleted my post for a reason. I misread what dpkg-divert does. I still think all of these fixes are ridiculous and just another thing that is a pain in the ass to maintain especially since plugins I maintain would need to add.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    Just a few generic comments:

    Murphy's law: "what can go wrong, will go wrong" applies.

    While true, nothing can be done about this. It is inherently impossible to plan for the unexpected.

    Therefore "use the OMV web interface" is not an appropriate answer to prevent the issue

    This is the ONLY answer to prevent the issue and other CLI issues like it (also in the users guide), for the reason ryecoaaron gives in the following:

    If someone chooses to use the command line, they choose to accept the risks associated with it.


    On the command line, there are nearly infinite ways to wreak the system, even if it's hardened. It's pointless to find something (on the CLI) that can cripple or destroy the system, "Tag it" and say "this is a problem". I could do that all day long. That wouldn't change or fix anything.

    It's far more productive to offset these risks and the effects of Murphy's Law, for beginners and intermediate users, by promoting "backup". And while they don't need to be prompted to do so, most expert users have their production boot drive backed up, before tampering with it. Otherwise, they're fully aware of the consequences.

    • Offizieller Beitrag

    Just a few generic comments:

    While true, nothing can be done about this. It is inherently impossible to plan for the unexpected.

    This is the ONLY answer to prevent the issue and other CLI issues like it (also in the users guide), for the reason ryecoaaron gives in the following:


    On the command line, there are nearly infinite ways to wreak the system, even if it's hardened. It's pointless to find something (on the CLI) that can cripple or destroy the system, "Tag it" and say "this is a problem". I could do that all day long. That wouldn't change or fix anything.

    It's far more productive to offset these risks and the effects of Murphy's Law, for beginners and intermediate users, by promoting "backup". And while they don't need to be prompted to do so, most expert users have their production boot drive backed up, before tampering with it. Otherwise, they're fully aware of the consequences.

    This post is 100% spot on and really should close any discussion on this any further.

  • Only divers teams are able to achieve success in the long run.

    We have very diverse backgrounds.

    I'm an inventor and am never satisfied with "not possible" answers. Actually they motivate me to try something different.

    Sometimes I loose, sometime I win.


    Only the sky is the limit and ~ 150 years ago common believe was flying is impossible for man, but it was proven to be wrong.


    Please allow me to have a different view and lets wait and see what Volker's view is at the end.

    omv 6.9.6-2 (Shaitan) on RPi CM4/4GB with 64bit Kernel 6.1.21-v8+

    2x 6TB 3.5'' HDDs (CMR) formatted with ext4 via 2port PCIe SATA card with ASM1061R chipset providing hardware supported RAID1


    omv 6.9.3-1 (Shaitan) on RPi4/4GB with 32bit Kernel 5.10.63 and WittyPi 3 V2 RTC HAT

    2x 3TB 3.5'' HDDs (CMR) formatted with ext4 in Icy Box IB-RD3662-C31 / hardware supported RAID1

    For Read/Write performance of SMB shares hosted on this hardware see forum here

  • just another thing that is a pain in the ass to maintain especially since plugins I maintain would need to add.

    I don't see using "diversion" becoming a "must" for plugins. Its an optional feature.

    You would be able to make your own judgement if it would reduce support effort, based on support requests in the forum. During troubleshooting, just let the user report if an old configuration file exists (suffix .dpkg-old) as dleidert pointed out in reply #15


    If other mods would ask for the same information , our common understanding would benefit.

    omv 6.9.6-2 (Shaitan) on RPi CM4/4GB with 64bit Kernel 6.1.21-v8+

    2x 6TB 3.5'' HDDs (CMR) formatted with ext4 via 2port PCIe SATA card with ASM1061R chipset providing hardware supported RAID1


    omv 6.9.3-1 (Shaitan) on RPi4/4GB with 32bit Kernel 5.10.63 and WittyPi 3 V2 RTC HAT

    2x 3TB 3.5'' HDDs (CMR) formatted with ext4 in Icy Box IB-RD3662-C31 / hardware supported RAID1

    For Read/Write performance of SMB shares hosted on this hardware see forum here

    • Offizieller Beitrag

    I'll add one last thought to this and move on:

    I'm an inventor and am never satisfied with "not possible" answers. Actually they motivate me to try something different.

    Then you need to learn to script and program. That might start with Python, Java Script, Linux Shell scripting, along with PHP and HTML.

    As I found with reST, when merging a doc onto the project wiki (and dealing with the notion of "documentation as code"), the effort is not to be taken lightly. That experience and others are the reason why, when I ask a question or mention a "nice to have" feature to a Dev (I.E. the person who is actually doing work), when they say "it's not practical", I let it go. Why? I don't have the experience base to understand what they do, the factors involved, the time required, etc. Therefore, because of that basic lack of understanding, I can't even form a cogent argument.

    One of the things I learned in my working life, as I sat in a conference room full of people with "great ideas" is that when the rubber hits the road, they were never there. They never had to deal with the consequences of their "suggestions", during the actual implementation in the field.

    Look, saying that the Star Ship Enterprise is "a great idea" is a given, but the trick is in building it. There's a difference between a "good idea" (a dime a dozen) and "building it" (which generally ranges from tough to impossible). One is a dream, the other is reality. There are miles (kilometers) of difference between the two.

  • Then you need to learn to script and program. That might start with Python, Java Script, Linux Shell scripting, along with PHP

    I started my career as programmer. I can modify code written in Python, Java Script, Linux Shell scripting, PHP, PERL and create code in PowerShell, COBOL and a few other languages.

    Unfortunately all these skills don't help with the issue on the table because "package management" is a completely different problem domain, requiring very specific skill.

    It is comparable to:

    can an average car mechanic instantly diagnose and troubleshoot a race car engine build in 2020?

    in >95% of cases the answer is no, because special skills are required.

    Assuming enough time & money is available to learn new skills, the percentage of failed attempts reduces over time though.


    Fortunately Daniel seems to have the required skills and advised on "how to prevent the issue". His proposal makes perfect sense to me, hence next step is the conversation with Volker.

    omv 6.9.6-2 (Shaitan) on RPi CM4/4GB with 64bit Kernel 6.1.21-v8+

    2x 6TB 3.5'' HDDs (CMR) formatted with ext4 via 2port PCIe SATA card with ASM1061R chipset providing hardware supported RAID1


    omv 6.9.3-1 (Shaitan) on RPi4/4GB with 32bit Kernel 5.10.63 and WittyPi 3 V2 RTC HAT

    2x 3TB 3.5'' HDDs (CMR) formatted with ext4 in Icy Box IB-RD3662-C31 / hardware supported RAID1

    For Read/Write performance of SMB shares hosted on this hardware see forum here

    2 Mal editiert, zuletzt von mi-hol ()

    • Offizieller Beitrag

    It's far more productive to offset these risks and the effects of Murphy's Law, for beginners and intermediate users, by promoting "backup". And while they don't need to be prompted to do so, most expert users have their production boot drive backed up, before tampering with it. Otherwise, they're fully aware of the consequences.

    What is this system drive backup you speak of? It sounds awesome.. :D

    • Offizieller Beitrag

    What is this system drive backup you speak of? It sounds awesome..

    For me it's cloned thumb drives. They work great. The entire process is documented in the User Guide, complete with the rational for OS backup and a walk through process. Since no CLI skills are required, an OMV/Linux newbie shouldn't have any trouble with it.

    Cloned thumb drives saved my butt when a recent ZFS package update disappeared my pool. I was back in 5 minutes. "Then" I looked at what was going on. (Quick restoration is one of the hallmarks of using cloned Thumbdrives to boot.)

    Maybe, sometime in the future, something based on Timeshift might be considered. Since there's real promise there, time permitting, I want to test Timeshift in rsync mode.
    _________________________________________________________

    I need to look closer at the backup plugin(s) for boot hard drives and, maybe, come up with another walk through. But I can't imagine something easier, for new users, than cloning thumb drives. (Or, for SBC's, SD-cards.)

    • Offizieller Beitrag

    My sarcasm didn't come through well I guess. :). I know what a system drive back up is, but my reference was more to this part of your post... :)

    Zitat


    And while they don't need to be prompted to do so, most expert users have their production boot drive backed up, before tampering with it. Otherwise, they're fully aware of the consequences.

    • Offizieller Beitrag

    My sarcasm didn't come through well I guess. :)

    I didn't see the smile on your Tux Avatar. :)

    I know what a system drive back up is, but my reference was more to this part of your post...

    That "backup" post was written (mostly) for new users that may happen onto this thread. I'm sure you have your own, preferred, method.

    Otherwise, they're fully aware of the consequences.

    Yep,, I've rebuilt more than once as I'm sure you have too.

    • Offizieller Beitrag

    I'm an inventor and am never satisfied with "not possible" answers.

    Maybe you confuse “not possible” answers with “not gonna” answers.

    Actually they motivate me to try something different.

    I can’t wait to see your new NAS software.

    But I can't imagine something easier, for new users, than cloning thumb drives. (Or, for SBC's, SD-cards.)

    On a more relevant topic to this forum - I will heartily second that thought. Never could figure out the live backup plugin. dd is my darling.

    System Backup Typo alert: Under the Linux section the command should be sudo umount /dev/sda1 NOT sudo unmount /dev/sda1

    Backup Data Disk to Backup Disk on Same Machine: In a Scheduled Job:rsync -av --delete /srv/dev-disk-by-uuid-f8814ed9-9a5c-4e1c-8830-426968c20ea3/ /srv/dev-disk-by-uuid-e67439d5-00a3-4942-bd5f-b84ab86aa850/ Don't forget trailing slashes, and BE CAREFUL. (HT: Getting Started with OMV5)

    Equipment - Thinkserver TS140, NanoPi M4 (v.1), Odroid XU4 (Using DietPi): PiHole

  • FYI the change was implemented


    openmediavault (5.6.13-1) stable; urgency=low
    * Issue #986: Divert files modified by openmediavault to prevent
    problems when package updates want to override them.

    omv 6.9.6-2 (Shaitan) on RPi CM4/4GB with 64bit Kernel 6.1.21-v8+

    2x 6TB 3.5'' HDDs (CMR) formatted with ext4 via 2port PCIe SATA card with ASM1061R chipset providing hardware supported RAID1


    omv 6.9.3-1 (Shaitan) on RPi4/4GB with 32bit Kernel 5.10.63 and WittyPi 3 V2 RTC HAT

    2x 3TB 3.5'' HDDs (CMR) formatted with ext4 in Icy Box IB-RD3662-C31 / hardware supported RAID1

    For Read/Write performance of SMB shares hosted on this hardware see forum here

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!