Bug 18530 - Update request: aufs-tools
Summary: Update request: aufs-tools
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: has_procedure advisory MGA5-32-OK
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2016-05-24 12:32 CEST by Thomas Backlund
Modified: 2016-06-02 23:40 CEST (History)
2 users (show)

See Also:
Source RPM: aufs-tools
CVE:
Status comment:


Attachments

Description Thomas Backlund 2016-05-24 12:32:35 CEST
Advisory:
Updated aufs-tools provide kernel 4.4 support

This update provides support for kernel 4.4 series

SRPM:
aufs-tools-4.4-0.git20160301.1.mga5.src.rpm

i586:
aufs-tools-4.4-0.git20160301.1.mga5.i586.rpm

x86_64:
aufs-tools-4.4-0.git20160301.1.mga5.x86_64.rpm
Comment 1 Herman Viaene 2016-05-31 15:59:56 CEST
MGA5-32 on AcerD620 Xfce.
For what reason I don't know, but this package was already installed (kernel 4.4.9 is already installed)
Anyway, googled a bit to find a test procedure and came up with - at tha CLI as root:
[root@mach6 ~]# mkdir /tmp/dir1
in between I then created a small text file in /tmp/dir1
[root@mach6 ~]# mkdir /tmp/aufs-root
[root@mach6 ~]# mount -t aufs -o br=/tmp/dir1:/home/tester5 none /tmp/aufs-root/
mount: onbekende bestandssysteemsoort 'aufs', in english: unknown filesystem aufs
found that I needed "modprobe aufs" and then the mount works.
I can see the merged contents of /tmp/dir1 and /home/tester5 in /tmp/aufs-root/

CC: (none) => herman.viaene

Herman Viaene 2016-05-31 16:00:37 CEST

Whiteboard: (none) => has_procedure MGA5-32-OK

Comment 2 claire robinson 2016-06-02 23:18:40 CEST
Validating this one. Well done Herman. The module is separate from these tools.

Keywords: (none) => validated_update
Whiteboard: has_procedure MGA5-32-OK => has_procedure advisory MGA5-32-OK
CC: (none) => sysadmin-bugs

Comment 3 Mageia Robot 2016-06-02 23:40:53 CEST
An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGAA-2016-0082.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.