From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-March/013462.html | 80 +++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-March/013462.html (limited to 'zarb-ml/mageia-dev/2012-March/013462.html') diff --git a/zarb-ml/mageia-dev/2012-March/013462.html b/zarb-ml/mageia-dev/2012-March/013462.html new file mode 100644 index 000000000..f34323e99 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-March/013462.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] [soft-commits] [3550] Kill unionfs support + + + + + + + + + +

[Mageia-dev] [soft-commits] [3550] Kill unionfs support

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Sat Mar 24 17:07:42 CET 2012 +

+
+ +
On 18 March 2012 10:51, Pascal Terjan <pterjan at gmail.com> wrote:
+> Well unionfs seemed to get different oops in each new version. Anyway
+> I don't think it should be done like this (having specific code for
+> unionfs everywhere).
+> I want to improve current chroot mode (like using a cgroup to easily
+> kill all processes or set limits) and have a common api to allow other
+> modes, like building in kvm for example, or using lvm/btrfs rw
+> snapshots (which should be better supported than unionfs).
+
+Then, we could maybe clean this in Chroot.pm:
+
+sub add_local_user {
+    my ($chroot_tmp, $run, $config, $luser, $uid) = @_;
+
+    # change the builder user to the local user id
+    # FIXME it seems that unionfs does not handle well the change of the
+    #       uid of files
+    # if (system(qq|sudo chroot $chroot_tmp usermod -u $run->{uid} builder|)) {
+
+Though sadly we lost the actual commit that did that due to the 2007 crash
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1