<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] [changelog] [RPM] cauldron core/release	nfs-utils-1.2.6-2.mga3
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20%5BRPM%5D%20cauldron%20core/release%0A%09nfs-utils-1.2.6-2.mga3&In-Reply-To=%3Cm362attzh0.fsf%40euphor.blino.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="016495.html">
   <LINK REL="Next"  HREF="016508.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] [changelog] [RPM] cauldron core/release	nfs-utils-1.2.6-2.mga3</H1>
    <B>Olivier Blin</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20%5BRPM%5D%20cauldron%20core/release%0A%09nfs-utils-1.2.6-2.mga3&In-Reply-To=%3Cm362attzh0.fsf%40euphor.blino.org%3E"
       TITLE="[Mageia-dev] [changelog] [RPM] cauldron core/release	nfs-utils-1.2.6-2.mga3">mageia at blino.org
       </A><BR>
    <I>Thu Jun 14 22:23:07 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="016495.html">[Mageia-dev] [changelog] [RPM] cauldron core/release	nfs-utils-1.2.6-2.mga3
</A></li>
        <LI>Next message: <A HREF="016508.html">[Mageia-dev] [changelog] [RPM] cauldron core/release nfs-utils-1.2.6-2.mga3
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16507">[ date ]</a>
              <a href="thread.html#16507">[ thread ]</a>
              <a href="subject.html#16507">[ subject ]</a>
              <a href="author.html#16507">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Colin Guthrie &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>&gt; writes:

[...]

&gt;&gt;&gt;&gt;<i> Now installing a kernel spits those messages:
</I>&gt;&gt;&gt;&gt;<i> libkmod: conf_files_filter_out: Directories inside directories are not
</I>&gt;&gt;&gt;&gt;<i> supported: /lib/modprobe.d/nfs.conf
</I>&gt;&gt;&gt;&gt;<i> (...)
</I>&gt;&gt;&gt;<i> We currently have no such /lib/modprobe.d directory in the
</I>&gt;&gt;&gt;<i> distribution, only /etc/modprobe.d. I guess our kmod package doesn't
</I>&gt;&gt;&gt;<i> support it yet, but should sooner or later. If I'm wrong, it's easy to
</I>&gt;&gt;&gt;<i> switch back to /etc/modprobe.d instead.
</I>&gt;&gt;<i> 
</I>&gt;&gt;<i> Actually, you installed the file as /lib/modprobe.d/nfs.conf/nfs.conf
</I>&gt;&gt;<i> I've removed the extra directory level.
</I>&gt;&gt;<i> 
</I>&gt;&gt;<i> But we should probably use /etc/modprobe.d/nfs.conf instead.
</I>&gt;<i>
</I>&gt;<i> IMO we should not use /etc/ here. /etc/ should be the domain of
</I>&gt;<i> administrator changes. IMO packages should always use /lib/ (or
</I>&gt;<i> eventually /usr/lib/) for such things. I've been pushing for this proper
</I>&gt;<i> separation for a while. udev and systemd do it properly although we do
</I>&gt;<i> still ship several udev files in /etc/udev/rules.d/ in packages which
</I>&gt;<i> should, by rights, be in /lib/udev/rules.d/
</I>
Yes, but currently, kmod and other system packages install modprobe
config files in /etc/modprobe.d:
$ rpm -qf /etc/modprobe.d/*
kmod-8-1.mga3
kmod-8-1.mga3
kmod-8-1.mga3
cups-common-1.5.3-5.mga3
kmod-8-1.mga3
kmod-8-1.mga3
sound-scripts-0.62-9.mga3

To be consistent, I moved the nfs-utils file there

&gt;<i> dbus upstream is still a big offender with policy files often ending up
</I>&gt;<i> in /etc/dbus-1/system.d/ rather than in a /lib/ tree. This can and does
</I>&gt;<i> sometimes have security implications, e.g. with the privilege escalation
</I>&gt;<i> I recently reported regarding sectool:
</I>&gt;<i> <A HREF="https://bugzilla.redhat.com/show_bug.cgi?id=809437">https://bugzilla.redhat.com/show_bug.cgi?id=809437</A>
</I>&gt;<i>
</I>&gt;<i> The policy file in question was marked with %config(noreplace) as it was
</I>&gt;<i> in /etc. But really this is a policy file which shouldn't be modified by
</I>&gt;<i> users. Therefore it shouldn't be marked as noreplace and it shouldn't
</I>&gt;<i> live in /etc/
</I>
Well, system administrators might want to change the default dbus
permissions.

&gt;<i> So, if the /lib/modprobe.d/ dir isn't parsed by kmod, we should fix kmod.
</I>
It seems it is parsed by kmod, but this doesn not seem to be mentionned
in the doc, and no package owns the dir...

I agree about moving modprobe config file into a system dir, but things
have to be done properly (with doc, proper directory owning, and all
packages doing the same).

-- 
Olivier Blin - blino
</PRE>














<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="016495.html">[Mageia-dev] [changelog] [RPM] cauldron core/release	nfs-utils-1.2.6-2.mga3
</A></li>
	<LI>Next message: <A HREF="016508.html">[Mageia-dev] [changelog] [RPM] cauldron core/release nfs-utils-1.2.6-2.mga3
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16507">[ date ]</a>
              <a href="thread.html#16507">[ thread ]</a>
              <a href="subject.html#16507">[ subject ]</a>
              <a href="author.html#16507">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>