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/2011-October/009202.html | 137 ++++++++++++++++++++++++++++ 1 file changed, 137 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-October/009202.html (limited to 'zarb-ml/mageia-dev/2011-October/009202.html') diff --git a/zarb-ml/mageia-dev/2011-October/009202.html b/zarb-ml/mageia-dev/2011-October/009202.html new file mode 100644 index 000000000..333f30dbc --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/009202.html @@ -0,0 +1,137 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release util-linux-2.20.1-1.mga2 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release util-linux-2.20.1-1.mga2

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Sat Oct 29 23:15:16 CEST 2011 +

+
+ +
'Twas brillig, and Dick Gevers at 26/10/11 21:48 did gyre and gimble:
+> On Tue, 25 Oct 2011 19:40:07 -0400, andre999 wrote about Re: [Mageia-dev]
+> [changelog] [RPM] cauldron core/release util-linux-2.20.1-1.mga2:
+> 
+>>> This gives me weird output for df:
+> 
+>>> All bind mounts are duplicated !
+> 
+> Since systemd I also have some duplicates (although less now then a couple
+> of weeks ago):
+> 
+> rootfs             17G  7.6G  8.1G  49% /
+> /dev/sda5          17G  7.6G  8.1G  49% /
+
+This is expected. It was masked previously with /etc/mtab hacks.
+
+> tmpfs             5.9G  632K  5.9G   1% /run
+> tmpfs             5.9G  632K  5.9G   1% /run
+
+This is a bug, but is actually fixed in this util-linux release - you do
+however need to regenerate the initrd to get the fix.
+
+> And this is completely superfluous (also not in fstab):
+> 
+> tmpfs             5.9G     0  5.9G   0% /media
+
+This is simply something done by systemd to ensure that /media is
+writable. Some filesystems have readonly / and thus cannot have such
+mountpoints added. Using tmpfs ensures that all mount points can be
+created easily.
+
+The actual partion size is pretty much irrelevant. It doesn't use that
+space at all, it's just what the tmpfs driver does when it's loaded
+without specifying a specific size. As the memory is just addressable,
+but not allocated, there is no real need to artificially lower the size.
+
+All the best
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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