bug-parted
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#38089: [sr #110102] Option to disable/ignore kernel updating in part


From: anonymous
Subject: bug#38089: [sr #110102] Option to disable/ignore kernel updating in parted
Date: Wed, 6 Nov 2019 10:10:14 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0

URL:
  <https://savannah.gnu.org/support/?110102>

                 Summary: Option to disable/ignore kernel updating in parted
                 Project: GNU Parted
            Submitted by: None
            Submitted on: Wed 06 Nov 2019 03:10:12 PM UTC
                Category: None
                Priority: 5 - Normal
                Severity: 1 - Wish
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Dear parted developers,

When I encountered some bugs (or FAD's, because they come from parted itself)
in ansible's parted module  (see
https://github.com/ansible/ansible/issues/63676), I came up with idea that
they could be solved very easily if parted had an option enabling "no commit"
mode, that is: only editing partition table on disk, without signaling the
kernel to update partition info.

Currently, parted script stops at the first command which fails on
ped_disk_commit_to_os(). My idea is: make commit_to_os optional
(alternatively: delay commit_to_os() call after last command in script, so
"failed to re-read the partition table" won't stop parted from executing all
script.

What's your opinion about this? If you give me a green light, I'd dust off my
C writting skills and submit a patch for evaulation.

With kind regards,
Robert Osowiecki





    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/support/?110102>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/






reply via email to

[Prev in Thread] Current Thread [Next in Thread]