search for: set_label

...-) > > diff --git a/daemon/btrfs.c b/daemon/btrfs.c > index 32b1b05..f9e35be 100644 > --- a/daemon/btrfs.c > +++ b/daemon/btrfs.c > @@ -1463,3 +1463,36 @@ do_btrfs_filesystem_defragment (const char *path) > > return 0; > } > + > +int > +do_btrfs_filesystem_set_label (const char *path, const char *label) > +{ > + const size_t MAX_ARGS = 64; > + const char *argv[MAX_ARGS]; > + size_t i = 0; > + CLEANUP_FREE char *path_buf = NULL; > + CLEANUP_FREE char *err = NULL; > + CLEANUP_FREE char *out = NULL; > + int r; > + > + path_bu...

Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com> --- generator/actions.ml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/generator/actions.ml b/generator/actions.ml index 92f80d2..35f30d5 100644 --- a/generator/actions.ml +++ b/generator/actions.ml @@ -9919,7 +9919,7 @@ Set the filesystem label on C<mountable> to C<label>. Only some filesystem

...direct when creating it. There may be filesystems not supporting changing the label of existing filesystems but only setting it at creation time, so this new optarg will help. Implement it for the most common filesystems (ext*, fat, ntfs, btrfs, xfs), giving an error for all the others, just like set_label does. --- daemon/mkfs.c | 45 +++++++++++++++++++++++++++++++++++++++++++-- generator/actions.ml | 42 +++++++++++++++++++++++------------------- 2 files changed, 66 insertions(+), 21 deletions(-) diff --git a/daemon/mkfs.c b/daemon/mkfs.c index 95ab874..2994307 100644 --- a/daemon/mkfs.c...

This miscellaneous patch adds bindings for: - ntfsfix - ntfsclone - ntfslabel and unifies filesystem label setting through a single API 'set-label' which replaces 'set-e2label' and is also able to set labels on NTFS using the ntfslabel program. 'ntfsfix' has been added as a possible way to fix RHBZ#797760. However I have not found a way to fully fix this bug. See

...quot;> * "Control#command":#Control_command </span><span class="cx"> * "Control#get_label":#Control_getlabel </span><ins>+* "Control#get_label_text":#Control_getlabeltext </ins><span class="cx"> * "Control#set_label":#Control_setlabel </span><span class="cx"> </span><span class="cx"> </div> </span><span class="cx"> </span><del>- - </del><span class="cx"> h3(#Control_command). Control#command </sp...

...asn''t sure if anyone was paying attention. I was just wondering if it would be possible to replace the get_something/set_something style methods with the more Rubyish something/something= style (i.e. uniform access). For example, the Button class currently has button.get_label and button.set_label("foo"). It would give me warm, fuzzy feelings if I could do button.label and button.label = "foo". :) Just a thought. Regards, Dan PS - TRW == "The Ruby Way" before you ask. __________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 d...

...f --git a/dib/dib.ml b/dib/dib.ml index 06a1f67..35ae6b7 100644 --- a/dib/dib.ml +++ b/dib/dib.ml @@ -781,9 +781,8 @@ let main () = ) @ mkfs_options @ [ "-t"; cmdline.fs_type; blockdev ] in ignore (g#debug "sh" (Array.of_list ([ "mkfs" ] @ mkfs_options))); g#set_label blockdev root_label; - (match cmdline.fs_type with - | x when String.is_prefix x "ext" -> g#set_uuid blockdev rootfs_uuid - | _ -> ()); + if String.is_prefix cmdline.fs_type "ext" then + g#set_uuid blockdev rootfs_uuid; g#mount blockdev "/"; g#mkmoun...

.../btrfs.c > > index 32b1b05..f9e35be 100644 > > --- a/daemon/btrfs.c > > +++ b/daemon/btrfs.c > > @@ -1463,3 +1463,36 @@ do_btrfs_filesystem_defragment (const char *path) > > > > return 0; > > } > > + > > +int > > +do_btrfs_filesystem_set_label (const char *path, const char *label) > > +{ > > + const size_t MAX_ARGS = 64; > > + const char *argv[MAX_ARGS]; > > + size_t i = 0; > > + CLEANUP_FREE char *path_buf = NULL; > > + CLEANUP_FREE char *err = NULL; > > + CLEANUP_FREE char *out = NULL; &g...

...InitEmpty, IfAvailable "btrfs", TestResultString ( + [["part_disk"; "/dev/sda"; "mbr"]; + ["mkfs"; "btrfs"; "/dev/sda1"; ""; "NOARG"; ""; ""; ""]; + ["set_label"; "/dev/sda1"; "test-label-btrfs"]; + ["vfs_label"; "/dev/sda1"]], "test-label-btrfs"), []; ]; shortdesc = "get the filesystem label"; longdesc = "\ -- 2.1.0

> There's a case for multiplying the return size by the block size of > the filesystem, thus returning the size in bytes. It might make the > API easier to use. Not sure how hard that is, or whether it actually > makes the API easier to use. > > Rich. This multiplication may confuse users who got used to "normal" resize2fs -P behavior (blocks) due to the name of

Get minimum size of NTFS filesystem in bytes. This is used primarily for shrinking images. In case of a full images ntfsresize returns error code and does not print minimum size. So we calculate it manually by rounding 'volume size' up to 'cluster size'. --- daemon/ntfs.c | 68 ++++++++++++++++++++++++++++++++++++++++++++++++++++ generator/actions.ml | 17 +++++++++++++

...if (r == -1) { > + reply_with_error ("%s: %s", path, err); > + return NULL; > + } > + > + return out; > +} There's vfs_label already as command to get the label of a filesystem, so this special case for btrfs should be added there (just like the ones done in set_label). Isn't blkid working on btrfs filesystems? From what I see, there is support for it already. > diff --git a/generator/actions.ml b/generator/actions.ml > index c328319..5223eb8 100644 > --- a/generator/actions.ml > +++ b/generator/actions.ml > @@ -12281,6 +12281,21 @@ corrupt...

...unt_options mount_ro mount_vfs Label APIs: All these currently take a block device, but are arguably applicable to btrfs subvolumes. A subvolume doesn't have a label itself, but its root filesystem does. A btrfs subvolume can still be mounted by label, as long as the subvolume is also given. set_label: note that this would also affect other subvolumes vfs_label vfs_type vfs_uuid Device name mangling: These apis are used to return sanitised device names. I'm not 100% convinced we need to modify them. However, we may want additional apis which handle filesystem descriptors. canonical_device...

...WxRuby base is a perfect time to incorporate those changes. Application code will need to change to adapt to 2.5, and although WxRuby-SWIG hasn''t been expected to introduce changes of its own, this would be a perfect time to incorporate some of the planned features (e.g. label=() vs. set_label()) and only have to break existing code *once.* For those wanting to add classes to WxRuby-SWIG, I would think it would be preferable to just work on the 2.5 version, rather than adding one for 2.4 and then having to revisit it for the change to 2.5. I recognize that 2.5 is currently not regar...

Really stupid question, but have you wrapped this all in an App class? If you don''t have a wxApp subclass driving your applications then all sorts of badness would happen. > I''m writing a custom little application for my boss''s high school > football team to track there stats play by play. > > My problem is that when I start the application, it

Hi, There is one problem: btrfs_filesystem_set_label just doesnt work, giving error message: libguestfs: error: btrfs_filesystem_set_label: /: ERROR: unable to set label Bad address I'm almost sure the patch has no problem, but can't figure out what's the cause. So patch 5 is only for review. Other APIs have no problem. Regards, Hu...

From: Anand Jain <anand.jain@oracle.com> (This patch is for the review/test not yet for the integration). Here is an implementation of the feature to add label to the subvolume and snapshots. Which would help sysadmin to better manager the subvol and snapshots. This can be done in two ways, one - using attr which is user land only changes but drawback is able to change the label

...y confuse users who got used to "normal" resize2fs > -P behavior (blocks) due to the name of API command. > I'm going to implement similar functionality for other filesystems > (ntfs, btrfs, xfs). Then please implement a single function for all these filesystems, just like set_label, set_uuid, etc. Having to call a different function to get the same information depending on the filesystem is only making artificial barriers in users of the API (which then have to do the function choice at runtime on their own). > I think we should preserve original command's behavior (...

...ulate it manually by rounding 'volume size' up to 'cluster size'. NACK to a separate API per-filesystem. As I said in a previous email, please turn the newly added resize2fs_P into a generic API for getting the minimum size of a filesystem, either bytes or blocks. See for example set_label and set_uuid. Thanks, -- Pino Toscano

...arses the 2.4 xml file. Will > the original parser create a xml file in the same format for 2.5 ? Thankfully, the XML hasn''t changed - I''m using the same file and removing the stripped methods. > I think a while back there was some talk of having methods like > "set_label" be changed to a more Ruby-attribute-like "label=" syntax. > Is this still being considered? I''m very much in favor of it, but I''m > wondering how the switch will be handled. Would both sets of methods > be kept, or would the get_xxx and set_xxx metho...