Re: [yocto] [meta-selinux][PATCH 1/2] dhcp: make a copy of init-server
于 14-6-16 上午9:38, wenzong@windriver.com 写道:
> From: Wenzong Fan
>
> Signed-off-by: Wenzong Fan
> ---
> recipes-connectivity/dhcp/dhcp_4.3.0.bbappend |3 ++
> recipes-connectivity/dhcp/files/init-server | 44
> +
> 2 files changed, 47 insertions(+)
> create mode 100644 recipes-connectivity/dhcp/dhcp_4.3.0.bbappend
> create mode 100644 recipes-connectivity/dhcp/files/init-server
>
> diff --git a/recipes-connectivity/dhcp/dhcp_4.3.0.bbappend
> b/recipes-connectivity/dhcp/dhcp_4.3.0.bbappend
> new file mode 100644
> index 000..900c2aa
> --- /dev/null
> +++ b/recipes-connectivity/dhcp/dhcp_4.3.0.bbappend
> @@ -0,0 +1,3 @@
> +inherit with-selinux
> +
> +FILESEXTRAPATHS_prepend := "${@target_selinux(d, '${THISDIR}/files:')}"
> diff --git a/recipes-connectivity/dhcp/files/init-server
> b/recipes-connectivity/dhcp/files/init-server
> new file mode 100644
> index 000..34c2085
> --- /dev/null
> +++ b/recipes-connectivity/dhcp/files/init-server
> @@ -0,0 +1,44 @@
> +#!/bin/sh
> +#
> +# $Id: dhcp3-server.init.d,v 1.4 2003/07/13 19:12:41 mdz Exp $
> +#
> +
> +test -f /usr/sbin/dhcpd || exit 0
> +
> +# It is not safe to start if we don't have a default configuration...
> +if [ ! -f /etc/default/dhcp-server ]; then
> + echo "/etc/default/dhcp-server does not exist! - Aborting..."
> + exit 0
> +fi
> +
> +# Read init script configuration (so far only interfaces the daemon
> +# should listen on.)
> +. /etc/default/dhcp-server
> +
> +case "$1" in
> + start)
> + echo -n "Starting DHCP server: "
> + test -d /var/lib/dhcp/ || mkdir -p /var/lib/dhcp/
> + test -f /var/lib/dhcp/dhcpd.leases || touch
> /var/lib/dhcp/dhcpd.leases
> + start-stop-daemon -S -x /usr/sbin/dhcpd -- -q $INTERFACES
> + echo "."
> + ;;
> + stop)
> + echo -n "Stopping DHCP server: dhcpd3"
> + start-stop-daemon -K -x /usr/sbin/dhcpd
> + echo "."
> + ;;
> + restart | force-reload)
> + $0 stop
> + sleep 2
> + $0 start
> + if [ "$?" != "0" ]; then
> + exit 1
> + fi
> + ;;
> + *)
> + echo "Usage: /etc/init.d/dhcp-server
> {start|stop|restart|force-reload}"
> + exit 1
> +esac
> +
> +exit 0
>
Merged, thanks. :)
--
- Pascal
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-selinux][PATCH] libpcre: update bbappend to 8.35
于 14-6-16 上午9:37, wenzong@windriver.com 写道:
> From: Wenzong Fan
>
> * rename libpcre_8.34.bbappend to libpcre_8.35.bbappend
> * remove 'PR' from libpcre_8.35.bbappend
>
> Signed-off-by: Wenzong Fan
> ---
> recipes-support/libpcre/libpcre_8.34.bbappend | 13 -
> recipes-support/libpcre/libpcre_8.35.bbappend | 11 +++
> 2 files changed, 11 insertions(+), 13 deletions(-)
> delete mode 100644 recipes-support/libpcre/libpcre_8.34.bbappend
> create mode 100644 recipes-support/libpcre/libpcre_8.35.bbappend
>
> diff --git a/recipes-support/libpcre/libpcre_8.34.bbappend
> b/recipes-support/libpcre/libpcre_8.34.bbappend
> deleted file mode 100644
> index 9131f8d..000
> --- a/recipes-support/libpcre/libpcre_8.34.bbappend
> +++ /dev/null
> @@ -1,13 +0,0 @@
> -PR .= "9"
> -
> -do_install_append () {
> - if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then
> - realsofile=`readlink ${D}${libdir}/libpcre.so`
> - mkdir -p ${D}/${base_libdir}/
> - mv -f ${D}${libdir}/libpcre.so.* ${D}${base_libdir}/
> - relpath=${@os.path.relpath("${base_libdir}", "${libdir}")}
> - ln -sf ${relpath}/${realsofile} ${D}${libdir}/libpcre.so
> - fi
> -}
> -
> -FILES_${PN} += "${base_libdir}/libpcre.so.*"
> diff --git a/recipes-support/libpcre/libpcre_8.35.bbappend
> b/recipes-support/libpcre/libpcre_8.35.bbappend
> new file mode 100644
> index 000..558644e
> --- /dev/null
> +++ b/recipes-support/libpcre/libpcre_8.35.bbappend
> @@ -0,0 +1,11 @@
> +do_install_append () {
> + if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then
> + realsofile=`readlink ${D}${libdir}/libpcre.so`
> + mkdir -p ${D}/${base_libdir}/
> + mv -f ${D}${libdir}/libpcre.so.* ${D}${base_libdir}/
> + relpath=${@os.path.relpath("${base_libdir}", "${libdir}")}
> + ln -sf ${relpath}/${realsofile} ${D}${libdir}/libpcre.so
> + fi
> +}
> +
> +FILES_${PN} += "${base_libdir}/libpcre.so.*"
>
Have commited using wildcard instead of version number.
Thanks :)
--
- Pascal
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-selinux][PATCH 0/2] initscripts/devpts.sh: fix context for /dev/pts
于 14-5-12 下午3:31, wenzong@windriver.com 写道: > From: Wenzong Fan > > devpts use file_use_trans to allocate security contexts. As there are no > range_trans rules for initrc_t mounting devpts, the security level of > mountpoint will be derived from the initrc process, to be systemhigh > (s15:c0.c1023), instead of expected systemlow(s0). > > This will block login shells to search PTYs, so use restorecon to fix > this. > > The following changes since commit 368f65a475069ed384d82be09c2515fb765e22ec: > >initscripts/checkroot.sh: restore file contexts for /run (2014-05-09 > 08:59:54 -0400) > > are available in the git repository at: > >git://git.pokylinux.org/poky-contrib wenzong/fix-pts >http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/fix-pts > > Wenzong Fan (2): >initscripts: add a local copy of devpts.sh >initscripts/devpts.sh: fix context for /dev/pts > > recipes-core/initscripts/initscripts/devpts.sh| 29 > + > recipes-core/initscripts/initscripts_1.0.bbappend |2 ++ > 2 files changed, 31 insertions(+) > create mode 100755 recipes-core/initscripts/initscripts/devpts.sh > Merged, thanks. :) -- - Pascal -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Labs (Alex J Lennon)
I personally donot think the manuals are abstract, instead they are very detailed. You have got a quick start guide which can help you alot for starting up. You can read some important points at http://www.kashyapgada.com/2014/06/12/embedded-linux-building-an-image-using-yocto-project/ . There are also more advanced manuls, project development, application development manuals. Above all next month there will be a book releasing named Embedded Linux Development with Yocto Project http://www.packtpub.com/embedded-linux-development-with-yocto-project/book which might also be a good guide, I am looking forward to that book, Have already pre booked it. Kashyap Gada On Mon, Jun 23, 2014 at 12:30 AM, wrote: > Send yocto mailing list submissions to > yocto@yoctoproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.yoctoproject.org/listinfo/yocto > or, via email, send a message with subject or body 'help' to > yocto-requ...@yoctoproject.org > > You can reach the person managing the list at > yocto-ow...@yoctoproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of yocto digest..." > > > Today's Topics: > >1. Yocto Labs (Arun Kumar) >2. Re: Yocto Labs (Alex J Lennon) >3. the apparent need for docbook tag in manual > examples (Robert P. J. Day) > > > -- > > Message: 1 > Date: Sun, 22 Jun 2014 06:03:58 +0530 > From: Arun Kumar > To: Yocto Mailing List > Subject: [yocto] Yocto Labs > Message-ID: <53a62476.2080...@gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi, > > I am new to Yocto project and have been following the documentation > for familiarity. > I am looking for hands on lab sessions for the yocto project. > I am unable to find the same on INTERNET, all i find is conference > videos and presentation. > > If anyone can share links to online tutorial videos / pdfs it would be > really useful. > content like creating and deploying own recipe files, layers. The > Documentation describes these tasks at a very abstract level, an little > more advanced version of the same would be appreciated. > Thanks in advance... > > > -- > > Message: 2 > Date: Sun, 22 Jun 2014 09:54:25 +0100 > From: Alex J Lennon > To: Arun Kumar ,Yocto Mailing List > > Subject: Re: [yocto] Yocto Labs > Message-ID: <53a699c1.4040...@dynamicdevices.co.uk> > Content-Type: text/plain; charset=ISO-8859-1 > > > On 22/06/2014 01:33, Arun Kumar wrote: > > Hi, > > > > I am new to Yocto project and have been following the > > documentation for familiarity. > > I am looking for hands on lab sessions for the yocto project. > > I am unable to find the same on INTERNET, all i find is conference > > videos and presentation. > > > > If anyone can share links to online tutorial videos / pdfs it would be > > really useful. > > content like creating and deploying own recipe files, layers. The > > Documentation describes these tasks at a very abstract level, an > > little more advanced version of the same would be appreciated. > > Thanks in advance... > > Might be of some use Arun, > > > https://wiki.yoctoproject.org/wiki/Building_your_own_recipes_from_first_principles > > Regards, > > Alex > > > > -- > > Message: 3 > Date: Sun, 22 Jun 2014 09:20:15 -0400 (EDT) > From: "Robert P. J. Day" > To: Yocto discussion list > Subject: [yocto] the apparent need for docbook tag in > manual examples > Message-ID: > Content-Type: TEXT/PLAIN; charset=US-ASCII > > > something poor scott rifenbark can ponder in his copious free time > :-), but i think some of the current examples in the various manuals > need to be enhanced with the use of the docbook tag to > emphasize that they are generic references meant to be replaced by > specific values; otherwise, there's potential confusion. > > as a concrete example, i remember *way* back when i was reading > about conditional metadata in the bitbake user manual, particularly > this verbatim example: > > OVERRIDES = "architecture:os:machine" > TEST = "default" > TEST_os = "osspecific" > TEST_nooverride = "othercondvalue" > > because all of the above is currently rendered in the same (courier) > font in the generated manual, i mistakenly thought that all of the > above was to somehow be typed exactly that way, and i was completely > baffled as to what the qualifiers "_os" and "_nooverride" would do. it > was only after searching for examples in the codebase that it dawned > that those strings were meant to be replaced by actual examples of the > current architecture, os, machine and so on. > > duh. > > this can be made more obvious fairly simply with the following > tweak of using the docbook tag: > > diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml > b/doc/bitbake-u
[yocto] [Package Report System]Upgrade recipes name list
This mail was sent out by Package Report System. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this recipe remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON_pn-"xxx" = "Not upgrade to 2.0 because the new version is unstable" You can check the detail information at http://packages.yoctoproject.org/upgradepkgname PackageName Version UpVersion MaintainerNoUpgradeReason gettext 0.18.3.2 0.19.1 Wenzong Fan blktrace 1.0.5+gitAUTOINC+d6918c8 1.0.5+gitAUTOINC+ce9ded7 Tom Zanussi systemtap-uprobes 2.5+gitAUTOINC+8f0fcd995f 2.5+gitAUTOINC+c69af88Tom Zanussi sysprof 1.2.0+gitAUTOINC+cd44ee6 1.2.0+gitAUTOINC+6901897 Tom Zanussi squashfs-tools4.2 4.3 Saul Wold libusb1 1.0.181.0.19 Saul Wold apt 0.9.9.4 1.0.5 Saul Wold xcb-util-renderutil 0.3.8 0.3.9 Saul Wold mkelfimage4.0+gitAUTOINC+686a48a339 4.0+gitAUTOINC+a173a62Saul Wold opkg-utils0.1.8+gitAUTOINC+d144584 0.1.8+gitAUTOINC+eae0d8f Saul Wold mtd-utils 1.5.1+gitAUTOINC+9f10713 1.5.1+gitAUTOINC+b7455d8 Saul Wold u-boot-mkimagev2013.07+gitAUTOINC+62c1 v2013.07+gitAUTOINC+39b6 Saul Wold dpkg 1.17.41.17.10 Saul Wold kmod 17+gitAUTOINC+49d8e0b590 18+gitAUTOINC+74c2694 Saul Wold ubootchart0.0+r12 N/A Saul Wold systemtap 2.5+gitAUTOINC+8f0fcd995f 2.5+gitAUTOINC+c69af88Saul Wold gnupg 2.0.222.0.23 Saul Wold sqlite3 3.8.4.3 3080500 Saul Wold libunique 1.1.6 3.0.2 Saul WoldDo not upgrade to version: 2 liburcu 0.8.1 0.8.4 Saul Wold babeltrace1.2.1+gitAUTOINC+66c2a20 1.2.1+gitAUTOINC+92757c3 Saul Wold man-pages 3.68 3.69 Saul Wold mx-1.01.4.7+gitAUTOINC+9b1db6b 1.99.4+gitAUTOINC+63da1f2 Saul Wold PRS 1.99 is dev version curl 7.36.07.37.0 Saul Wold mobile-broadband-provider-info20120614+gitrAUTOINC+4ed 20120614+gitrAUTOINC+bb5 Saul Wold base-passwd 3.5.293.5.33 Saul Wold xserver-xorg 1.15.11.15.99.903 Ross Burton libice1.0.8 1.0.9 Ross Burton gnome-common 3.7.4 3.12.0 Ross Burton libxfont 1.4.7 1.4.8 Ross Burton puzzles r10116N/A Ross Burton gtk+ 2.24.22 3.13.2 Ross BurtonDo not upgrade to version: 2 xf86-video-vmware 13.0.113.0.2 Ross Burton xf86-video-intel 2.99.910 2.99.912 Ross Burton vala 0.16.00.24.0 Ross Burton
[yocto] [Package Report System]Manual check recipes name list
This mail was sent out by Package Report System. It will list all the recipes which can't check upstream version by script, and will show how long it is since their last mannual version check. You can check the detail information at http://packages.yoctoproject.org/manuallychkinfo PackageName Version LastChkVersion LastChkTime Maintainer NoUpgradeReason man 1.6gN/A 41811 d Saul Wold -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] the apparent need for docbook tag in manual examples
something poor scott rifenbark can ponder in his copious free time :-), but i think some of the current examples in the various manuals need to be enhanced with the use of the docbook tag to emphasize that they are generic references meant to be replaced by specific values; otherwise, there's potential confusion. as a concrete example, i remember *way* back when i was reading about conditional metadata in the bitbake user manual, particularly this verbatim example: OVERRIDES = "architecture:os:machine" TEST = "default" TEST_os = "osspecific" TEST_nooverride = "othercondvalue" because all of the above is currently rendered in the same (courier) font in the generated manual, i mistakenly thought that all of the above was to somehow be typed exactly that way, and i was completely baffled as to what the qualifiers "_os" and "_nooverride" would do. it was only after searching for examples in the codebase that it dawned that those strings were meant to be replaced by actual examples of the current architecture, os, machine and so on. duh. this can be made more obvious fairly simply with the following tweak of using the docbook tag: diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml index a9f5072..f8be373 100644 --- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml @@ -359,7 +359,7 @@ version. Here is an example: - OVERRIDES = "architecture:os:machine" + OVERRIDES = "architecture:os:machine" TEST = "default" TEST_os = "osspecific" TEST_nooverride = "othercondvalue" i've confirmed that that tag is processed properly within a , and renders in italicized courier font, which is the visual clue that it's not meant to be read literally. oh, and one more related point ... i think it would be more useful to replace generic manual examples that use meaningless phrases such as "foo" and "bar" with specific examples yanked from the actual OE codebase. as i said, it took me a few minutes to figure out what the conditional metadata example above was trying to demonstrate, but as soon as i saw a real example in the codebase, it was perfectly clear. to this end, i'm creating wiki pages that show stuff like that exactly, like this one for conditional overrides: http://www.crashcourse.ca/wiki/index.php/BitBake_Overrides so rather than try to explain the generic concept, i can just bring up the wiki page and say, "see? that's how it works." and everyone understands immediately. anyway, just my $0.02. back to work ... rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Labs
On 22/06/2014 01:33, Arun Kumar wrote: > Hi, > > I am new to Yocto project and have been following the > documentation for familiarity. > I am looking for hands on lab sessions for the yocto project. > I am unable to find the same on INTERNET, all i find is conference > videos and presentation. > > If anyone can share links to online tutorial videos / pdfs it would be > really useful. > content like creating and deploying own recipe files, layers. The > Documentation describes these tasks at a very abstract level, an > little more advanced version of the same would be appreciated. > Thanks in advance... Might be of some use Arun, https://wiki.yoctoproject.org/wiki/Building_your_own_recipes_from_first_principles Regards, Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
