All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] udev-extraconf: merge with udev-extra-rules from meta-oe
@ 2012-07-30 15:03 Martin Jansa
  2012-07-30 15:12 ` Martin Jansa
                   ` (2 more replies)
  0 siblings, 3 replies; 10+ messages in thread
From: Martin Jansa @ 2012-07-30 15:03 UTC (permalink / raw)
  To: openembedded-core

* license in meta-oe was MIT, in oe-core it was GPLv2, everyone fine with this?
* add mount.blacklist to CONFFILES
* add more rules and scripts from meta-oe
* change PV to 1.0 and bump PR to provide upgrade path from meta-oe's udev-extra-rules
  including RREPLACE/RPROVIDES/RCONFLICTS trio

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 .../udev/udev-extraconf/automount.rules            |   19 ++++++
 .../recipes-core/udev/udev-extraconf/autonet.rules |   19 ++++++
 meta/recipes-core/udev/udev-extraconf/local.rules  |   21 +++++++
 meta/recipes-core/udev/udev-extraconf/mount.sh     |   64 ++++++++++++++++++++
 meta/recipes-core/udev/udev-extraconf/network.sh   |   58 ++++++++++++++++++
 meta/recipes-core/udev/udev-extraconf_0.0.bb       |   15 -----
 meta/recipes-core/udev/udev-extraconf_1.0.bb       |   43 +++++++++++++
 7 files changed, 224 insertions(+), 15 deletions(-)
 create mode 100644 meta/recipes-core/udev/udev-extraconf/automount.rules
 create mode 100644 meta/recipes-core/udev/udev-extraconf/autonet.rules
 create mode 100644 meta/recipes-core/udev/udev-extraconf/local.rules
 create mode 100644 meta/recipes-core/udev/udev-extraconf/mount.sh
 create mode 100644 meta/recipes-core/udev/udev-extraconf/network.sh
 delete mode 100644 meta/recipes-core/udev/udev-extraconf_0.0.bb
 create mode 100644 meta/recipes-core/udev/udev-extraconf_1.0.bb

diff --git a/meta/recipes-core/udev/udev-extraconf/automount.rules b/meta/recipes-core/udev/udev-extraconf/automount.rules
new file mode 100644
index 0000000..7e844c3
--- /dev/null
+++ b/meta/recipes-core/udev/udev-extraconf/automount.rules
@@ -0,0 +1,19 @@
+# There are a number of modifiers that are allowed to be used in some
+# of the different fields. They provide the following subsitutions:
+#
+# %n the "kernel number" of the device.
+#    For example, 'sda3' has a "kernel number" of '3'
+# %e the smallest number for that name which does not matches an existing node
+# %k the kernel name for the device
+# %M the kernel major number for the device
+# %m the kernel minor number for the device
+# %b the bus id for the device
+# %c the string returned by the PROGRAM
+# %s{filename} the content of a sysfs attribute
+# %% the '%' char itself
+#
+
+# Media automounting
+SUBSYSTEM=="block", ACTION=="add"    RUN+="/etc/udev/scripts/mount.sh"
+SUBSYSTEM=="block", ACTION=="remove" RUN+="/etc/udev/scripts/mount.sh"
+
diff --git a/meta/recipes-core/udev/udev-extraconf/autonet.rules b/meta/recipes-core/udev/udev-extraconf/autonet.rules
new file mode 100644
index 0000000..19676aa
--- /dev/null
+++ b/meta/recipes-core/udev/udev-extraconf/autonet.rules
@@ -0,0 +1,19 @@
+# There are a number of modifiers that are allowed to be used in some
+# of the different fields. They provide the following subsitutions:
+#
+# %n the "kernel number" of the device.
+#    For example, 'sda3' has a "kernel number" of '3'
+# %e the smallest number for that name which does not matches an existing node
+# %k the kernel name for the device
+# %M the kernel major number for the device
+# %m the kernel minor number for the device
+# %b the bus id for the device
+# %c the string returned by the PROGRAM
+# %s{filename} the content of a sysfs attribute
+# %% the '%' char itself
+#
+
+# Handle network interface setup
+SUBSYSTEM=="net", ACTION=="add" RUN+="/etc/udev/scripts/network.sh"
+SUBSYSTEM=="net", ACTION=="remove" RUN+="/etc/udev/scripts/network.sh"
+
diff --git a/meta/recipes-core/udev/udev-extraconf/local.rules b/meta/recipes-core/udev/udev-extraconf/local.rules
new file mode 100644
index 0000000..4eaa8ca
--- /dev/null
+++ b/meta/recipes-core/udev/udev-extraconf/local.rules
@@ -0,0 +1,21 @@
+# There are a number of modifiers that are allowed to be used in some
+# of the different fields. They provide the following subsitutions:
+#
+# %n the "kernel number" of the device.
+#    For example, 'sda3' has a "kernel number" of '3'
+# %e the smallest number for that name which does not matches an existing node
+# %k the kernel name for the device
+# %M the kernel major number for the device
+# %m the kernel minor number for the device
+# %b the bus id for the device
+# %c the string returned by the PROGRAM
+# %s{filename} the content of a sysfs attribute
+# %% the '%' char itself
+#
+
+# The first rtc device is symlinked to /dev/rtc
+KERNEL=="rtc0", SYMLINK+="rtc"
+
+#The first framebuffer is symlinked to /dev/fb
+KERNEL=="fb0",  SYMLINK+="fb"
+
diff --git a/meta/recipes-core/udev/udev-extraconf/mount.sh b/meta/recipes-core/udev/udev-extraconf/mount.sh
new file mode 100644
index 0000000..67c2b4b
--- /dev/null
+++ b/meta/recipes-core/udev/udev-extraconf/mount.sh
@@ -0,0 +1,64 @@
+#!/bin/sh
+#
+# Called from udev
+# Attemp to mount any added block devices
+# and remove any removed devices
+#
+
+MOUNT="/bin/mount"
+PMOUNT="/usr/bin/pmount"
+UMOUNT="/bin/umount"
+name="`basename "$DEVNAME"`"
+
+for line in `grep -v ^# /etc/udev/mount.blacklist`
+do
+	if ( echo "$DEVNAME" | grep -q "$line" )
+	then
+		logger "udev/mount.sh" "[$DEVNAME] is blacklisted, ignoring"
+		exit 0
+	fi
+done
+
+automount() {
+	! test -d "/media/$name" && mkdir -p "/media/$name"
+
+	if ! $MOUNT -t auto -o async,relatime $DEVNAME "/media/$name"
+	then
+		#logger "mount.sh/automount" "$MOUNT -t auto $DEVNAME \"/media/$name\" failed!"
+		rm_dir "/media/$name"
+	else
+		logger "mount.sh/automount" "Auto-mount of [/media/$name] successful"
+		touch "/tmp/.automount-$name"
+	fi
+}
+
+rm_dir() {
+	# We do not want to rm -r populated directories
+	if test "`find "$1" | wc -l | tr -d " "`" -lt 2 -a -d "$1"
+	then
+		! test -z "$1" && rm -r "$1"
+	else
+		logger "mount.sh/automount" "Not removing non-empty directory [$1]"
+	fi
+}
+
+if [ "$ACTION" = "add" ] && [ -n "$DEVNAME" ]; then
+	if [ -x "$PMOUNT" ]; then
+		$PMOUNT $DEVNAME 2> /dev/null
+	elif [ -x $MOUNT ]; then
+			$MOUNT $DEVNAME 2> /dev/null
+	fi
+
+	# Avoid remounting devices (e.g: rootfs)
+	awk '{print $1}' /proc/mounts | grep -q "^$DEVNAME$" || automount
+fi
+
+if [ "$ACTION" = "remove" ] && [ -x "$UMOUNT" ] && [ -n "$DEVNAME" ]; then
+	for mnt in `grep "$DEVNAME" /proc/mounts | cut -f 2 -d " " `
+	do
+		$UMOUNT -l $mnt
+	done
+
+	# Remove empty directories from auto-mounter
+	test -e "/tmp/.automount-$name" && rm_dir "/media/$name"
+fi
diff --git a/meta/recipes-core/udev/udev-extraconf/network.sh b/meta/recipes-core/udev/udev-extraconf/network.sh
new file mode 100644
index 0000000..182c26d
--- /dev/null
+++ b/meta/recipes-core/udev/udev-extraconf/network.sh
@@ -0,0 +1,58 @@
+#!/bin/sh
+
+# udevd does clearenv(). Export shell PATH to children.
+export PATH
+
+# Do not run when pcmcia-cs is installed
+test -x /sbin/cardctl && exit 0
+
+# We get two "add" events for hostap cards due to wifi0
+echo "$INTERFACE" | grep -q wifi && exit 0
+
+
+# Check if /etc/init.d/network has been run yet to see if we are 
+# called by starting /etc/rcS.d/S03udev and not by hotplugging a device
+#
+# At this stage, network interfaces should not be brought up
+# automatically because:
+# a)	/etc/init.d/network has not been run yet (security issue)
+# b) 	/var has not been populated yet so /etc/resolv,conf points to 
+#	oblivion, making the network unusable
+#
+
+spoofp="`grep ^spoofprotect /etc/network/options`"
+if test -z "$spoofp"
+then
+	# This is the default from /etc/init.d/network
+	spoofp_val=yes
+else
+	spoofp_val=${spoofp#spoofprotect=}
+fi
+
+test "$spoofp_val" = yes && spoofp_val=1 || spoofp_val=0
+
+# I think it is safe to assume that "lo" will always be there ;)
+if test "`cat /proc/sys/net/ipv4/conf/lo/rp_filter`" != "$spoofp_val" -a -n "$spoofp_val"
+then
+	echo "$INTERFACE" >> /dev/udev_network_queue	
+	exit 0
+fi
+
+#
+# Code taken from pcmcia-cs:/etc/pcmcia/network
+#
+
+# if this interface has an entry in /etc/network/interfaces, let ifupdown
+# handle it
+if grep -q "iface \+$INTERFACE" /etc/network/interfaces; then
+  case $ACTION in
+    add)
+    	ifconfig | grep -q "^$INTERFACE" || ifup $INTERFACE
+    	;;
+    remove)
+    	ifdown $INTERFACE
+    	;;
+  esac
+  
+  exit 0
+fi
diff --git a/meta/recipes-core/udev/udev-extraconf_0.0.bb b/meta/recipes-core/udev/udev-extraconf_0.0.bb
deleted file mode 100644
index d0d0e84..0000000
--- a/meta/recipes-core/udev/udev-extraconf_0.0.bb
+++ /dev/null
@@ -1,15 +0,0 @@
-SUMMARY = "Extra machine specific configuration files"
-DESCRIPTION = "Extra machine specific configuration files for udev, specifically blacklist information."
-LICENSE = "GPLv2"
-LIC_FILES_CHKSUM = "file://${WORKDIR}/COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe"
-
-PR = "r2"
-
-SRC_URI = "file://mount.blacklist \
-           file://COPYING.GPL"
-
-do_install () {
-	install -d ${D}${sysconfdir}/udev/
-
-	install -m 0644 ${WORKDIR}/mount.blacklist     ${D}${sysconfdir}/udev/
-}
diff --git a/meta/recipes-core/udev/udev-extraconf_1.0.bb b/meta/recipes-core/udev/udev-extraconf_1.0.bb
new file mode 100644
index 0000000..940e7d0
--- /dev/null
+++ b/meta/recipes-core/udev/udev-extraconf_1.0.bb
@@ -0,0 +1,43 @@
+SUMMARY = "Extra machine specific configuration files"
+DESCRIPTION = "Extra machine specific configuration files for udev, specifically blacklist information."
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM = "file://${WORKDIR}/COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe"
+
+inherit allarch
+
+PR = "r5"
+
+SRC_URI = " \
+       file://automount.rules \
+       file://mount.sh \
+       file://mount.blacklist \
+       file://autonet.rules \
+       file://network.sh \
+       file://local.rules \
+       file://COPYING.GPL \
+"
+
+
+do_install() {
+    install -d ${D}${sysconfdir}/udev/rules.d
+
+    install -m 0644 ${WORKDIR}/automount.rules     ${D}${sysconfdir}/udev/rules.d/automount.rules
+    install -m 0644 ${WORKDIR}/autonet.rules       ${D}${sysconfdir}/udev/rules.d/autonet.rules
+    install -m 0644 ${WORKDIR}/local.rules         ${D}${sysconfdir}/udev/rules.d/local.rules
+
+    install -m 0644 ${WORKDIR}/mount.blacklist     ${D}${sysconfdir}/udev/
+
+    install -d ${D}${sysconfdir}/udev/scripts/
+
+    install -m 0755 ${WORKDIR}/mount.sh ${D}${sysconfdir}/udev/scripts/mount.sh
+    install -m 0755 ${WORKDIR}/network.sh ${D}${sysconfdir}/udev/scripts
+}
+
+FILES_${PN} = "${sysconfdir}/udev"
+RDEPENDS_${PN} = "udev"
+CONFFILES_${PN} = "${sysconfdir}/udev/mount.blacklist"
+
+# to replace udev-extra-rules from meta-oe
+RPROVIDES_${PN} = "udev-extra-rules"
+RREPLACES_${PN} = "udev-extra-rules"
+RCONFLICTS_${PN} = "udev-extra-rules"
-- 
1.7.8.6




^ permalink raw reply related	[flat|nested] 10+ messages in thread

* Re: [PATCH] udev-extraconf: merge with udev-extra-rules from meta-oe
  2012-07-30 15:03 [PATCH] udev-extraconf: merge with udev-extra-rules from meta-oe Martin Jansa
@ 2012-07-30 15:12 ` Martin Jansa
  2012-07-30 17:42 ` Koen Kooi
  2012-08-05 10:23 ` [PATCH] layer.conf: add udev-extraconf to SIGGEN_EXCLUDERECIPES_ABISAFE Martin Jansa
  2 siblings, 0 replies; 10+ messages in thread
From: Martin Jansa @ 2012-07-30 15:12 UTC (permalink / raw)
  To: openembedded-core

[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]

On Mon, Jul 30, 2012 at 05:03:14PM +0200, Martin Jansa wrote:
> * license in meta-oe was MIT, in oe-core it was GPLv2, everyone fine with this?
> * add mount.blacklist to CONFFILES
> * add more rules and scripts from meta-oe
> * change PV to 1.0 and bump PR to provide upgrade path from meta-oe's udev-extra-rules
>   including RREPLACE/RPROVIDES/RCONFLICTS trio

BTW: this shows bug in opkg file owner tracking code:

Similar to http://code.google.com/p/opkg/issues/detail?id=51

Upgrading udev-extraconf (1.0-r5) to root...
Downloading http://jama.dyndns-home.com/org.openembedded.shr-core//all/udev-extraconf_1.0-r5_all.ipk.
Removing package udev-extra-rules from root...
Configuring udev-extraconf.

SHR root@Nokia-N900 / $ opkg files udev-extraconf
Package udev-extraconf (1.0-r5) is installed on root and has the following files:

But the files are there:
SHR root@Nokia-N900 / $ ll /etc/udev/rules.d/
total 20
-rw-r--r-- 1 root root 748 Jul 30 14:57 automount.rules
-rw-r--r-- 1 root root 757 Jul 30 14:57 autonet.rules
-rw-r--r-- 1 root root 742 Jul 30 14:57 local.rules
-rw-r--r-- 1 root root 728 Jul 25 09:33 modprobe.rules
-rw-r--r-- 1 root root 855 Jul 25 09:33 touchscreen.rules

Next install shows them properly:
SHR root@Nokia-N900 / $ opkg install -force-reinstall udev-extraconf
Removing package udev-extraconf from root...
Installing udev-extraconf (1.0-r5) to root...
Downloading http://jama.dyndns-home.com/org.openembedded.shr-core//all/udev-extraconf_1.0-r5_all.ipk.
Configuring udev-extraconf.

SHR root@Nokia-N900 / $ opkg files udev-extraconf
Package udev-extraconf (1.0-r5) is installed on root and has the
following files:
/etc/udev/rules.d/local.rules
/etc/udev/rules.d/automount.rules
/etc/udev/scripts/network.sh
/etc/udev/rules.d/autonet.rules
/etc/udev/scripts/
/etc/udev/scripts/mount.sh
/etc/udev/mount.blacklist


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH] udev-extraconf: merge with udev-extra-rules from meta-oe
  2012-07-30 15:03 [PATCH] udev-extraconf: merge with udev-extra-rules from meta-oe Martin Jansa
  2012-07-30 15:12 ` Martin Jansa
@ 2012-07-30 17:42 ` Koen Kooi
  2012-07-30 17:59   ` Martin Jansa
  2012-08-05 10:23 ` [PATCH] layer.conf: add udev-extraconf to SIGGEN_EXCLUDERECIPES_ABISAFE Martin Jansa
  2 siblings, 1 reply; 10+ messages in thread
From: Koen Kooi @ 2012-07-30 17:42 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer


Op 30 jul. 2012, om 17:03 heeft Martin Jansa <martin.jansa@gmail.com> het volgende geschreven:

> * license in meta-oe was MIT, in oe-core it was GPLv2, everyone fine with this?

Hmm, MIT to GPL is a big regression, anyway to keep MIT?


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH] udev-extraconf: merge with udev-extra-rules from meta-oe
  2012-07-30 17:42 ` Koen Kooi
@ 2012-07-30 17:59   ` Martin Jansa
  2012-07-30 19:01     ` [PATCH] udev-extraconf: change LICENSE to MIT Martin Jansa
  0 siblings, 1 reply; 10+ messages in thread
From: Martin Jansa @ 2012-07-30 17:59 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

[-- Attachment #1: Type: text/plain, Size: 538 bytes --]

On Mon, Jul 30, 2012 at 07:42:28PM +0200, Koen Kooi wrote:
> 
> Op 30 jul. 2012, om 17:03 heeft Martin Jansa <martin.jansa@gmail.com> het volgende geschreven:
> 
> > * license in meta-oe was MIT, in oe-core it was GPLv2, everyone fine with this?
> 
> Hmm, MIT to GPL is a big regression, anyway to keep MIT?

If it's fine with oe-core people I'll send v2.

I was thinking the same, but didn't want to introduce another change to
original oe-core recipe.

Cheers,
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* [PATCH] udev-extraconf: change LICENSE to MIT
  2012-07-30 17:59   ` Martin Jansa
@ 2012-07-30 19:01     ` Martin Jansa
  2012-07-31 11:26       ` Richard Purdie
  0 siblings, 1 reply; 10+ messages in thread
From: Martin Jansa @ 2012-07-30 19:01 UTC (permalink / raw)
  To: openembedded-core

* original recipe added by RP in fc128ab1e4fec27d44cebfa690a9bc233eda0caf was saying GPL
* later it was changed to GPLv2
* COPYING.GPL was added to reflect that
* meta-oe has similar recipe with MIT license and even more scripts, so lets change LICENSE here too

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 meta/recipes-core/udev/udev-extraconf/COPYING.GPL |  339 ---------------------
 meta/recipes-core/udev/udev-extraconf_1.0.bb      |    8 +-
 2 files changed, 4 insertions(+), 343 deletions(-)
 delete mode 100644 meta/recipes-core/udev/udev-extraconf/COPYING.GPL

diff --git a/meta/recipes-core/udev/udev-extraconf/COPYING.GPL b/meta/recipes-core/udev/udev-extraconf/COPYING.GPL
deleted file mode 100644
index d511905..0000000
--- a/meta/recipes-core/udev/udev-extraconf/COPYING.GPL
+++ /dev/null
@@ -1,339 +0,0 @@
-		    GNU GENERAL PUBLIC LICENSE
-		       Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-			    Preamble
-
-  The licenses for most software are designed to take away your
-freedom to share and change it.  By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users.  This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it.  (Some other Free Software Foundation software is covered by
-the GNU Lesser General Public License instead.)  You can apply it to
-your programs, too.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
-  To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have.  You must make sure that they, too, receive or can get the
-source code.  And you must show them these terms so they know their
-rights.
-
-  We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
-  Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software.  If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
-  Finally, any free program is threatened constantly by software
-patents.  We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary.  To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-		    GNU GENERAL PUBLIC LICENSE
-   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-  0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License.  The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language.  (Hereinafter, translation is included without limitation in
-the term "modification".)  Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope.  The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
-  1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
-  2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
-    a) You must cause the modified files to carry prominent notices
-    stating that you changed the files and the date of any change.
-
-    b) You must cause any work that you distribute or publish, that in
-    whole or in part contains or is derived from the Program or any
-    part thereof, to be licensed as a whole at no charge to all third
-    parties under the terms of this License.
-
-    c) If the modified program normally reads commands interactively
-    when run, you must cause it, when started running for such
-    interactive use in the most ordinary way, to print or display an
-    announcement including an appropriate copyright notice and a
-    notice that there is no warranty (or else, saying that you provide
-    a warranty) and that users may redistribute the program under
-    these conditions, and telling the user how to view a copy of this
-    License.  (Exception: if the Program itself is interactive but
-    does not normally print such an announcement, your work based on
-    the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole.  If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works.  But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
-  3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
-    a) Accompany it with the complete corresponding machine-readable
-    source code, which must be distributed under the terms of Sections
-    1 and 2 above on a medium customarily used for software interchange; or,
-
-    b) Accompany it with a written offer, valid for at least three
-    years, to give any third party, for a charge no more than your
-    cost of physically performing source distribution, a complete
-    machine-readable copy of the corresponding source code, to be
-    distributed under the terms of Sections 1 and 2 above on a medium
-    customarily used for software interchange; or,
-
-    c) Accompany it with the information you received as to the offer
-    to distribute corresponding source code.  (This alternative is
-    allowed only for noncommercial distribution and only if you
-    received the program in object code or executable form with such
-    an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it.  For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable.  However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
-  4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License.  Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
-  5. You are not required to accept this License, since you have not
-signed it.  However, nothing else grants you permission to modify or
-distribute the Program or its derivative works.  These actions are
-prohibited by law if you do not accept this License.  Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
-  6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions.  You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
-  7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all.  For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices.  Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-  8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded.  In such case, this License incorporates
-the limitation as if written in the body of this License.
-
-  9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number.  If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation.  If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
-  10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission.  For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this.  Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
-			    NO WARRANTY
-
-  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
-  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-		     END OF TERMS AND CONDITIONS
-
-	    How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software; you can redistribute it and/or modify
-    it under the terms of the GNU General Public License as published by
-    the Free Software Foundation; either version 2 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU General Public License for more details.
-
-    You should have received a copy of the GNU General Public License along
-    with this program; if not, write to the Free Software Foundation, Inc.,
-    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
-    Gnomovision version 69, Copyright (C) year name of author
-    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-    This is free software, and you are welcome to redistribute it
-    under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License.  Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary.  Here is a sample; alter the names:
-
-  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
-  `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
-  <signature of Ty Coon>, 1 April 1989
-  Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs.  If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library.  If this is what you want to do, use the GNU Lesser General
-Public License instead of this License.
diff --git a/meta/recipes-core/udev/udev-extraconf_1.0.bb b/meta/recipes-core/udev/udev-extraconf_1.0.bb
index 940e7d0..5a239af 100644
--- a/meta/recipes-core/udev/udev-extraconf_1.0.bb
+++ b/meta/recipes-core/udev/udev-extraconf_1.0.bb
@@ -1,11 +1,12 @@
 SUMMARY = "Extra machine specific configuration files"
 DESCRIPTION = "Extra machine specific configuration files for udev, specifically blacklist information."
-LICENSE = "GPLv2"
-LIC_FILES_CHKSUM = "file://${WORKDIR}/COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58 \
+                    file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
 
 inherit allarch
 
-PR = "r5"
+PR = "r6"
 
 SRC_URI = " \
        file://automount.rules \
@@ -14,7 +15,6 @@ SRC_URI = " \
        file://autonet.rules \
        file://network.sh \
        file://local.rules \
-       file://COPYING.GPL \
 "
 
 
-- 
1.7.8.6




^ permalink raw reply related	[flat|nested] 10+ messages in thread

* Re: [PATCH] udev-extraconf: change LICENSE to MIT
  2012-07-30 19:01     ` [PATCH] udev-extraconf: change LICENSE to MIT Martin Jansa
@ 2012-07-31 11:26       ` Richard Purdie
  2012-07-31 11:37         ` Martin Jansa
  2012-07-31 12:46         ` Koen Kooi
  0 siblings, 2 replies; 10+ messages in thread
From: Richard Purdie @ 2012-07-31 11:26 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

On Mon, 2012-07-30 at 21:01 +0200, Martin Jansa wrote:
> * original recipe added by RP in fc128ab1e4fec27d44cebfa690a9bc233eda0caf was saying GPL
> * later it was changed to GPLv2
> * COPYING.GPL was added to reflect that
> * meta-oe has similar recipe with MIT license and even more scripts, so lets change LICENSE here too
> 
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
>  meta/recipes-core/udev/udev-extraconf/COPYING.GPL |  339 ---------------------
>  meta/recipes-core/udev/udev-extraconf_1.0.bb      |    8 +-
>  2 files changed, 4 insertions(+), 343 deletions(-)
>  delete mode 100644 meta/recipes-core/udev/udev-extraconf/COPYING.GPL

Er, I think we need to be a little more careful than this. Just because
you want something to be so, doesn't make it happen just like that...

Looking at the commit, I've just copied the license from the original
source which was a GPLv2 recipe (udev). Where did mount.blacklist come
from originally? Is there evidence its MIT licensed? How did meta-oe
conclude this was MIT licensed?

Cheers,

Richard




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH] udev-extraconf: change LICENSE to MIT
  2012-07-31 11:26       ` Richard Purdie
@ 2012-07-31 11:37         ` Martin Jansa
  2012-07-31 12:46         ` Koen Kooi
  1 sibling, 0 replies; 10+ messages in thread
From: Martin Jansa @ 2012-07-31 11:37 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]

On Tue, Jul 31, 2012 at 12:26:50PM +0100, Richard Purdie wrote:
> On Mon, 2012-07-30 at 21:01 +0200, Martin Jansa wrote:
> > * original recipe added by RP in fc128ab1e4fec27d44cebfa690a9bc233eda0caf was saying GPL
> > * later it was changed to GPLv2
> > * COPYING.GPL was added to reflect that
> > * meta-oe has similar recipe with MIT license and even more scripts, so lets change LICENSE here too
> > 
> > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > ---
> >  meta/recipes-core/udev/udev-extraconf/COPYING.GPL |  339 ---------------------
> >  meta/recipes-core/udev/udev-extraconf_1.0.bb      |    8 +-
> >  2 files changed, 4 insertions(+), 343 deletions(-)
> >  delete mode 100644 meta/recipes-core/udev/udev-extraconf/COPYING.GPL
> 
> Er, I think we need to be a little more careful than this. Just because
> you want something to be so, doesn't make it happen just like that...
> 
> Looking at the commit, I've just copied the license from the original
> source which was a GPLv2 recipe (udev). Where did mount.blacklist come
> from originally? Is there evidence its MIT licensed? How did meta-oe
> conclude this was MIT licensed?

sorry I'm not lawyer to decide if those 3 lines of code should be GPLv2
or MIT and I don't have any evidence either way.. (From common sense
more lines were imported from meta-oe where they were marked as MIT).

I think I was carefull, first warning in commit message (end kept
original LICENSE) then extra patch on Koen's request to be clear 
about that change.

Do we want 2 licenses in udev-extraconf or should we ask all devs which
ever touched udev-extra-rules for permission to change it to GPLv2?

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH] udev-extraconf: change LICENSE to MIT
  2012-07-31 11:26       ` Richard Purdie
  2012-07-31 11:37         ` Martin Jansa
@ 2012-07-31 12:46         ` Koen Kooi
  2012-08-30  9:06           ` Martin Jansa
  1 sibling, 1 reply; 10+ messages in thread
From: Koen Kooi @ 2012-07-31 12:46 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer


Op 31 jul. 2012, om 13:26 heeft Richard Purdie <richard.purdie@linuxfoundation.org> het volgende geschreven:

> On Mon, 2012-07-30 at 21:01 +0200, Martin Jansa wrote:
>> * original recipe added by RP in fc128ab1e4fec27d44cebfa690a9bc233eda0caf was saying GPL
>> * later it was changed to GPLv2
>> * COPYING.GPL was added to reflect that
>> * meta-oe has similar recipe with MIT license and even more scripts, so lets change LICENSE here too
>> 
>> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
>> ---
>> meta/recipes-core/udev/udev-extraconf/COPYING.GPL |  339 ---------------------
>> meta/recipes-core/udev/udev-extraconf_1.0.bb      |    8 +-
>> 2 files changed, 4 insertions(+), 343 deletions(-)
>> delete mode 100644 meta/recipes-core/udev/udev-extraconf/COPYING.GPL
> 
> Er, I think we need to be a little more careful than this. Just because
> you want something to be so, doesn't make it happen just like that...
> 
> Looking at the commit, I've just copied the license from the original
> source which was a GPLv2 recipe (udev). Where did mount.blacklist come
> from originally? Is there evidence its MIT licensed? How did meta-oe
> conclude this was MIT licensed?

It was written for oe-classic -> MIT licensed


^ permalink raw reply	[flat|nested] 10+ messages in thread

* [PATCH] layer.conf: add udev-extraconf to SIGGEN_EXCLUDERECIPES_ABISAFE
  2012-07-30 15:03 [PATCH] udev-extraconf: merge with udev-extra-rules from meta-oe Martin Jansa
  2012-07-30 15:12 ` Martin Jansa
  2012-07-30 17:42 ` Koen Kooi
@ 2012-08-05 10:23 ` Martin Jansa
  2 siblings, 0 replies; 10+ messages in thread
From: Martin Jansa @ 2012-08-05 10:23 UTC (permalink / raw)
  To: openembedded-core

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 meta/conf/layer.conf |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
index 090c8e2..dfcb1f3 100644
--- a/meta/conf/layer.conf
+++ b/meta/conf/layer.conf
@@ -23,4 +23,5 @@ SIGGEN_EXCLUDERECIPES_ABISAFE += " \
   pointercal \
   base-files \
   keymaps \
+  udev-extraconf \
 "
-- 
1.7.8.6




^ permalink raw reply related	[flat|nested] 10+ messages in thread

* Re: [PATCH] udev-extraconf: change LICENSE to MIT
  2012-07-31 12:46         ` Koen Kooi
@ 2012-08-30  9:06           ` Martin Jansa
  0 siblings, 0 replies; 10+ messages in thread
From: Martin Jansa @ 2012-08-30  9:06 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]

On Tue, Jul 31, 2012 at 02:46:40PM +0200, Koen Kooi wrote:
> 
> Op 31 jul. 2012, om 13:26 heeft Richard Purdie <richard.purdie@linuxfoundation.org> het volgende geschreven:
> 
> > On Mon, 2012-07-30 at 21:01 +0200, Martin Jansa wrote:
> >> * original recipe added by RP in fc128ab1e4fec27d44cebfa690a9bc233eda0caf was saying GPL
> >> * later it was changed to GPLv2
> >> * COPYING.GPL was added to reflect that
> >> * meta-oe has similar recipe with MIT license and even more scripts, so lets change LICENSE here too
> >> 
> >> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> >> ---
> >> meta/recipes-core/udev/udev-extraconf/COPYING.GPL |  339 ---------------------
> >> meta/recipes-core/udev/udev-extraconf_1.0.bb      |    8 +-
> >> 2 files changed, 4 insertions(+), 343 deletions(-)
> >> delete mode 100644 meta/recipes-core/udev/udev-extraconf/COPYING.GPL
> > 
> > Er, I think we need to be a little more careful than this. Just because
> > you want something to be so, doesn't make it happen just like that...
> > 
> > Looking at the commit, I've just copied the license from the original
> > source which was a GPLv2 recipe (udev). Where did mount.blacklist come
> > from originally? Is there evidence its MIT licensed? How did meta-oe
> > conclude this was MIT licensed?
> 
> It was written for oe-classic -> MIT licensed

ping4, are some lawyers still working on this?

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2012-08-30  9:18 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-30 15:03 [PATCH] udev-extraconf: merge with udev-extra-rules from meta-oe Martin Jansa
2012-07-30 15:12 ` Martin Jansa
2012-07-30 17:42 ` Koen Kooi
2012-07-30 17:59   ` Martin Jansa
2012-07-30 19:01     ` [PATCH] udev-extraconf: change LICENSE to MIT Martin Jansa
2012-07-31 11:26       ` Richard Purdie
2012-07-31 11:37         ` Martin Jansa
2012-07-31 12:46         ` Koen Kooi
2012-08-30  9:06           ` Martin Jansa
2012-08-05 10:23 ` [PATCH] layer.conf: add udev-extraconf to SIGGEN_EXCLUDERECIPES_ABISAFE Martin Jansa

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.