[yocto] [meta-security][PATCH 1/2] libseccomp: fix SRC_URI for multilib
${BPN} should be used instead of ${PN} where you want the name without
any prefix (and ${BP} is short for ${BPN}-${PV}).
Signed-off-by: Paul Eggleton
---
recipes-security/libseccomp/libseccomp_2.1.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-security/libseccomp/libseccomp_2.1.1.bb
b/recipes-security/libseccomp/libseccomp_2.1.1.bb
index 5e0b962..0663656 100644
--- a/recipes-security/libseccomp/libseccomp_2.1.1.bb
+++ b/recipes-security/libseccomp/libseccomp_2.1.1.bb
@@ -4,7 +4,7 @@ SECTION = "security"
LICENSE = "GPL-2.0"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
-SRC_URI = "http://sourceforge.net/projects/libseccomp/files/${PN}-${PV}.tar.gz
\
+SRC_URI = "http://sourceforge.net/projects/libseccomp/files/${BP}.tar.gz \
file://compiler.patch \
file://0001-tests-create-install-tests-target.patch \
file://0002-tests-install-python-tests-if-appropriate.patch \
--
1.9.3
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH 2/2] nikto: fix SRC_URI for multilib
${BPN} should be used instead of ${PN} where you want the name without
any prefix (and ${BP} is short for ${BPN}-${PV}).
Signed-off-by: Paul Eggleton
---
recipes-security/nikto/nikto_2.1.5.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-security/nikto/nikto_2.1.5.bb
b/recipes-security/nikto/nikto_2.1.5.bb
index 40b5b72..8080d4a 100644
--- a/recipes-security/nikto/nikto_2.1.5.bb
+++ b/recipes-security/nikto/nikto_2.1.5.bb
@@ -6,7 +6,7 @@ LICENSE = "GPLv2"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
-SRC_URI = "http://cirt.net/nikto/${PN}-${PV}.tar.gz \
+SRC_URI = "http://cirt.net/nikto/${BP}.tar.gz \
file://location.patch"
SRC_URI[md5sum] = "efcc98a918becb77471ee9a5df0a7b1e"
--
1.9.3
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-xilinx-community] How to build for MicroZed board?
Good Morning, I am new to Yocto, but I need to create an embedded system on board MicroZed, based on processor Zynq from Xilinx. From what I understand the support form my board is provided by layer xilinx-meta-community; from the README file associated with this layer I see that the mailing list of reference is this, with the constraint of using "[meta-xilinx-community]" as a subject prefix. In doubt if this is the correct mailing list, I am also writing to meta-xil...@yoctoproject.org. If I'm writing to the correct mailing list, I would write of a problem: I would like to generate the configuration core-image-minimal, with MACHINE ??= "microzed-zynq7", with the sources aligned to version "daisy". I cloned repositories related to "poky", "meta-xilinx" and "meta-xilinx-community" with the following commands: - git clone -b daisy git://git.yoctoproject.org/poky.git - git clone -b daisy git://github.com/Xilinx/meta-xilinx - git clone -b daisy git://git.yoctoproject.org/meta-xilinx-community - git clone -b daisy git://github.com/openembedded/meta-oe I then modified my file local.conf specifying parallelism and the variable MACHINE ??= "ZedBoard-zynq7" I also changed the file bblayers.conf changing layers included as follows: BBLAYERS ?= " \ /data/axel/YoctoMicroZed/poky/meta \ /data/axel/YoctoMicroZed/poky/meta-yocto \ /data/axel/YoctoMicroZed/poky/meta-yocto-bsp \ /data/axel/YoctoMicroZed/poky/meta-xilinx-community \ /data/axel/YoctoMicroZed/poky/meta-xilinx \ /data/axel/YoctoMicroZed/poky/meta-oe/meta-oe \ " The problem is that running the command "bitbake core-image-minimal", after the download phase and the execution of some tasks, the process stops with the following error: Function failed: do_configure (log file is located at /data/axel/YoctoMicroZed/poky/build/tmp/work/microzed_zynq7-poky-linux-gnueabi/linux-xlnx/3.14-xilinx+git2b48a8aeea7367359f9eebe55c4a09a05227f32b-r0/temp/log.do_configure.11742) Before going to analyze the nature of the error I'd like to know if the version of the various sources is updated - in the sense: there are archives of sources, tested such that it is possible to successfully execute the build for this system? Or I have to refer to particular sources on git commit? Thank you in advance for any suggestion Kind regards Marco Tessore -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] PDF manual support
I am seriously considering dumping the PDF manuals for the 1.8 release. The PDF output is less than good and there seems to have been no enthusiasm for this form during the past 4 years. Comments? Scott Scott Rifenbark Intel Corporation Yocto Project Documentation 503.712.2702 503.341.0418 (cell) -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] PDF manual support
Source will remain in DocBook. Probably going to migrate to DocBook 5 as it is becoming the standard. From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Tuesday, January 13, 2015 6:32 AM To: Rifenbark, Scott M Cc: Yocto discussion list Subject: Re: [yocto] PDF manual support On 13 January 2015 at 14:28, Rifenbark, Scott M mailto:scott.m.rifenb...@intel.com>> wrote: I am seriously considering dumping the PDF manuals for the 1.8 release. The PDF output is less than good and there seems to have been no enthusiasm for this form during the past 4 years. Comments? Assuming that the source remains in DocBook then anyone who wants a printable copy will be able to generate the PDFs themselves, so I don't see a massive problem with this myself. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] PDF manual support
On 13 January 2015 at 14:28, Rifenbark, Scott M wrote: > I am seriously considering dumping the PDF manuals for the 1.8 release. > The PDF output is less than good and there seems to have been no enthusiasm > for this form during the past 4 years. Comments? > Assuming that the source remains in DocBook then anyone who wants a printable copy will be able to generate the PDFs themselves, so I don't see a massive problem with this myself. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] PDF manual support
On 01/13/15 09:28, Rifenbark, Scott M wrote: > I am seriously considering dumping the PDF manuals for the 1.8 release. The > PDF output is less than good and there seems to have been no enthusiasm for > this form during the past 4 years. Comments? I tend to generate PDFs from git://git.yoctoproject.org/yocto-docs and read those. So as long as I can still generate these on my own I'll be okay with whatever changes work for you. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] PDF manual support
Trevor, Are you generating those on your own or are you using the "pdf:" target from the Makefile that is currently part of the repo? >-Original Message- >From: Trevor Woerner [mailto:twoer...@gmail.com] >Sent: Tuesday, January 13, 2015 6:52 AM >To: Rifenbark, Scott M; Yocto discussion list >Subject: Re: [yocto] PDF manual support > >On 01/13/15 09:28, Rifenbark, Scott M wrote: >> I am seriously considering dumping the PDF manuals for the 1.8 release. The >PDF output is less than good and there seems to have been no enthusiasm for >this form during the past 4 years. Comments? > >I tend to generate PDFs from git://git.yoctoproject.org/yocto-docs and read >those. So as long as I can still generate these on my own I'll be okay with >whatever changes work for you. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] PDF manual support
On 01/13/15 09:57, Rifenbark, Scott M wrote: > Are you generating those on your own or are you using the "pdf:" target from > the Makefile that is currently part of the repo? I'm using the pdf target from the Makefile: $ make pdf DOC=dev-manual usually by running: https://github.com/twoerner/meta-trevor/blob/master/misc/build_yocto_docs.sh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] PDF manual support
I guess I could leave that target in the Makefile but remove it from the "all:" target. So, you would have to specifically call out that target to make PDF versions (e.g. make pdf DOC=). >-Original Message- >From: Trevor Woerner [mailto:twoer...@gmail.com] >Sent: Tuesday, January 13, 2015 7:23 AM >To: Rifenbark, Scott M; Yocto discussion list >Subject: Re: [yocto] PDF manual support > >On 01/13/15 09:57, Rifenbark, Scott M wrote: >> Are you generating those on your own or are you using the "pdf:" target >from the Makefile that is currently part of the repo? > >I'm using the pdf target from the Makefile: > >$ make pdf DOC=dev-manual > >usually by running: > > >https://github.com/twoerner/meta- >trevor/blob/master/misc/build_yocto_docs.sh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] PDF manual support
On Tue, Jan 13, 2015 at 9:28 AM, Rifenbark, Scott M < scott.m.rifenb...@intel.com> wrote: > I am seriously considering dumping the PDF manuals for the 1.8 release. > The PDF output is less than good and there seems to have been no enthusiasm > for this form during the past 4 years. Comments? > Gosh, am I the only one that still uses PDF manuals? I like the 'P' part of PDFs - standalone (no internet) and searchable. BTW, I have occasionally tried building them, without much success. I'm sure it's a host compatibility issue, and admittedly, I haven't spent much time trying to get it working. Please don't delete support for them ;) -Chris -- Life is like Linux - it never stands still. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] PDF manual support
I can leave them in there as a target for the Makefile. But, they do not look pretty. They will be created if you run them from the Makefile. From: Chris Hallinan [mailto:challi...@gmail.com] Sent: Tuesday, January 13, 2015 7:32 AM To: Rifenbark, Scott M Cc: Yocto discussion list Subject: Re: [yocto] PDF manual support On Tue, Jan 13, 2015 at 9:28 AM, Rifenbark, Scott M mailto:scott.m.rifenb...@intel.com>> wrote: I am seriously considering dumping the PDF manuals for the 1.8 release. The PDF output is less than good and there seems to have been no enthusiasm for this form during the past 4 years. Comments? Gosh, am I the only one that still uses PDF manuals? I like the 'P' part of PDFs - standalone (no internet) and searchable. BTW, I have occasionally tried building them, without much success. I'm sure it's a host compatibility issue, and admittedly, I haven't spent much time trying to get it working. Please don't delete support for them ;) -Chris -- Life is like Linux - it never stands still. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Recipe reporting system] Upgradable recipe name list
This mail was sent out by Recipe reporting 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 is unstable" You can check the detail information at: http://packages.yoctoproject.org/upgradepkgname Package VersionUpstream version Maintainer NoUpgradeReason - --- -- gnome-icon-theme 2.31.0 3.12.0Alejandro Hernandez midori0.5.8 0.5.9 Alejandro Hernandez unzip 6.0552 Alejandro Hernandez dpkg 1.17.211.17.23 Aníbal Limón screen4.0.3 4.2.1 Aníbal Limón apt 0.9.9.41.0.9.5 Aníbal Limón nettle2.7.1 3.0 Armin Kuster linux-libc-headers3.17.7 3.18.2Bruce Ashfield zip 3.0552 Chen Qi grep 2.5.1a 2.21 Chen Qi sysklogd 1.51.5.1 Chen Qi sysstat 10.2.1 11.1.2Chen Qi curl 7.38.0 7.40.0Chen Qi coreutils 8.22 8.23 Chen Qi cpio 2.82.11 Chen Qi util-linux2.24.2 2.25.2Chen Qi console-tools 0.3.2 1999.03.02Chen Qi bison 2.7.1 3.0.2 Chong Lu dbus 1.8.10 1.9.6 Chong Lu quota 4.01 4.02 Cristian Iorga libical 1.0.0 1.0.1 Cristian Iorga pulseaudio5.05.99.2Cristian Iorga libatomics-ops7.27.4.0 Cristian Iorga speex 1.2rc1 1.2rc2Cristian Iorga gst-fluendo-mpegd... 0.10.720.10.85 Cristian Iorga db6.0.30 6.1.19Cristian Iorga API compatibility issue flac 1.3.0 1.3.1 Cristian Iorga connman 1.26 1.27 Cristian Iorga bluez55.25 5.27 Cristian Iorga gst-plugin-bluetooth 4.101 5.27 Cristian Iorga bluez44.101 5.27 Cristian Iorga iproute2 3.17.0 3.18.0Cristian Iorga ofono 1.15 1.16 Cristian Iorga neard 0.14 0.15 Cristian Iorga neon 0.30.0 0.30.1Cristian Iorga linux-yocto-rt3.14.24+gitX 3.14.26+gitAUTOIN... Darren Hart kernelshark 1.2+gitX 2.5+gitAUTOINC+5a... Darren Hart trace-cmd 2.3.2+gitX 2.5+gitAUTOINC+79... Darren Hart qmmp 0.7.7 0.8.3 Hongxu Jia perl 5.20.0 5.21.7Hongxu Jia libxml-parser-perl2.41 2.44 Hongxu Jia elfutils 0.160 0.161 Hongxu Jia xmlto 0.0.25 0.0.26Hongxu Jia bash 4.34.3.30Hongxu Jia man-pages 3.75 3.77 Hongxu Jia groff 1.22.2 1.22.3Hongxu Jia rpcbind 0.2.1 0.2.2 Hongxu Jia man 1.6g 2.5a6 Hongxu Jia createrepo0.4.11 0.10.3Hongxu Jia gnupg 2.1.0 2.1.1 Hongxu Jia dhcp 4.3.0 4.3.1 Hongxu Jia directfb 1.7.4 1.7.6 Hongxu Jia bind 9.9.5 11Kai Kang libsdl1.2.15 1.2.15-1 Kai Kang python-nose 1.2.1 1.3.4 Khem Raj python-numpy 1.7.0 1.9.1 Khem Raj python3-distribute0.6.32 0.7.3 Khem Raj python-mako 0.9.1 1.0.0 Khem Raj rpm 5.4.14 5.4.15-0.20140824 Mark Hatle libgfortran 4.9.1 4.9.2 No Maint
Re: [yocto] [meta-selinux][ 0/3] More recipe updates.
On 1/12/15 9:50 PM, Philip Tricca wrote: > Greetings, > > Three more recipe udpates to get meta-selinux building with oe-core master > again. These are mostly mundane though the move from findutils from 4.4.x > to 4.5.x removes the need for patches that have since gone upstream (w00t!). Patches look fine to me. One comment though, since we're upreving, we should drop the PR .= bit as no longer necessary. --Mark > Best, > Philip > > Philip Tricca (3): > findutils: Upgrade recipe to 4.5 and use wildcard for pico version. > logrotate: Use wildcard for version number. > tar: Use wildcard for version number in bbappend. > > .../findutils-with-selinux-gnulib.patch| 55 -- > .../findutils-4.4.2/findutils-with-selinux.patch | 528 > > .../findutils/findutils_4.4.2.bbappend | 14 - > .../findutils/findutils_4.5.%.bbappend |4 + > recipes-extended/logrotate/logrotate_%.bbappend|7 + > .../logrotate/logrotate_3.8.7.bbappend |7 - > recipes-extended/tar/tar_%.bbappend| 13 + > recipes-extended/tar/tar_1.27.1.bbappend | 13 - > 8 files changed, 24 insertions(+), 617 deletions(-) > delete mode 100644 > recipes-extended/findutils/findutils-4.4.2/findutils-with-selinux-gnulib.patch > delete mode 100644 > recipes-extended/findutils/findutils-4.4.2/findutils-with-selinux.patch > delete mode 100644 recipes-extended/findutils/findutils_4.4.2.bbappend > create mode 100644 recipes-extended/findutils/findutils_4.5.%.bbappend > create mode 100644 recipes-extended/logrotate/logrotate_%.bbappend > delete mode 100644 recipes-extended/logrotate/logrotate_3.8.7.bbappend > create mode 100644 recipes-extended/tar/tar_%.bbappend > delete mode 100644 recipes-extended/tar/tar_1.27.1.bbappend > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Jan. 13, 2015 8:00 AM US Pacific Time
Attendees: Armin, Joe, Stephen, Tom, Sona, Cristian, Richard, Bruce, Denys, Ross, Paul, Saul, Mark, Alex, Michael, * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.8_Status https://wiki.yoctoproject.org/wiki/Yocto_1.8_Schedule https://wiki.yoctoproject.org/wiki/Yocto_1.8_Features YP 1.7.1 - out of QA and looks good. Should be release later this week. YP 1.8 M2 cut off was this evening, but due to the Kernel Build process changes; we will push this cutoff date out one week. This might also allow us to get the memory resident Bitbake in for M2. * SWAT team rotation: Saul -> Ross https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team We should look at adding Randy, Alejandro, & Anibal We should update the documentation. - Saul will review the documentation and drive updates. * Opens - 10 min RP - We made changes in kernel build process to make it more efficient. We have found some issues with this change. RP - Memory Resident Bitbake - This allows us to improve and make more efficient the work we are doing during Bitbake. * Team Sharing - 10 min Michael - We have moved our downloads to another location. If anyone is seeing slow downloads, let Michael know so he can collect stats about it. Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 * Work Telephone: (503) 712-0534 *Cell:(208) 244-4460 * Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-security][PATCH 2/2] nikto: fix SRC_URI for multilib
merged .
thanks,
Armin
On 01/13/2015 01:25 AM, Paul Eggleton wrote:
${BPN} should be used instead of ${PN} where you want the name without
any prefix (and ${BP} is short for ${BPN}-${PV}).
Signed-off-by: Paul Eggleton
---
recipes-security/nikto/nikto_2.1.5.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-security/nikto/nikto_2.1.5.bb
b/recipes-security/nikto/nikto_2.1.5.bb
index 40b5b72..8080d4a 100644
--- a/recipes-security/nikto/nikto_2.1.5.bb
+++ b/recipes-security/nikto/nikto_2.1.5.bb
@@ -6,7 +6,7 @@ LICENSE = "GPLv2"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
-SRC_URI = "http://cirt.net/nikto/${PN}-${PV}.tar.gz \
+SRC_URI = "http://cirt.net/nikto/${BP}.tar.gz \
file://location.patch"
SRC_URI[md5sum] = "efcc98a918becb77471ee9a5df0a7b1e"
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-security][PATCH 1/2] libseccomp: fix SRC_URI for multilib
merged.
Thanks,
Armin
On 01/13/2015 01:25 AM, Paul Eggleton wrote:
${BPN} should be used instead of ${PN} where you want the name without
any prefix (and ${BP} is short for ${BPN}-${PV}).
Signed-off-by: Paul Eggleton
---
recipes-security/libseccomp/libseccomp_2.1.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-security/libseccomp/libseccomp_2.1.1.bb
b/recipes-security/libseccomp/libseccomp_2.1.1.bb
index 5e0b962..0663656 100644
--- a/recipes-security/libseccomp/libseccomp_2.1.1.bb
+++ b/recipes-security/libseccomp/libseccomp_2.1.1.bb
@@ -4,7 +4,7 @@ SECTION = "security"
LICENSE = "GPL-2.0"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
-SRC_URI = "http://sourceforge.net/projects/libseccomp/files/${PN}-${PV}.tar.gz
\
+SRC_URI = "http://sourceforge.net/projects/libseccomp/files/${BP}.tar.gz \
file://compiler.patch \
file://0001-tests-create-install-tests-target.patch \
file://0002-tests-install-python-tests-if-appropriate.patch \
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [BBB] RTL8188EE not mounting
Let me start by apologizing if the outcome is very obvious to everyone but me. I'm VERY new to Linux and newer to Yocto. I have an RTL8188EE wifi board that I'm connecting to a Beaglebone Black via USB. If I do an 'lsusb' I can see that there is a Realtek device out there somewhere. Even though the driver for this exact device appears in the kernel drivers, the device doesn't mount. I'm running the dizzy version and have tried building the Sato, Full Command Line and Basic versions hoping that one of them would include whatever it is that I need to recognize this device. For the non-Sato versions I did copy the uImage and Modules to the SD card thinking they might help. Any help would be great. TIA Brent Skinner | Firmware Supervisor | Document Imaging | 2400 Mt Read Blvd | Rochester, NY, 14615-3029 | brent.skin...@kodakalaris.com | 585 726-0097 Office | www.kodakalaris.com [cid:image001.png@01D02F28.04412580] -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [BBB] RTL8188EE not mounting
On 2015-01-13 10:00, Cameron B Skinner wrote: Let me start by apologizing if the outcome is very obvious to everyone but me. I’m VERY new to Linux and newer to Yocto. I have an RTL8188EE wifi board that I’m connecting to a Beaglebone Black via USB. If I do an ‘lsusb’ I can see that there is a Realtek device out there somewhere. Even though the driver for this exact device appears in the kernel drivers, the device doesn’t mount. I’m running the dizzy version and have tried building the Sato, Full Command Line and Basic versions hoping that one of them would include whatever it is that I need to recognize this device. For the non-Sato versions I did copy the uImage and Modules to the SD card thinking they might help. Any help would be great. For this device to work you need both a kernel driver and firmware. The kernel driver is probably being built, but the firmware is probably not installed. Make sure your image includes the appropriate firmware for the device. In your case I think this would be linux-firmware-rtl8192ce Does the appropriate driver get loaded into the kernel? What does 'lsmod' show? If you still have trouble, send the output of 'lsmod' and 'dmesg' after you plug in the device. -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Potential Yocto Project developer day at ELC
Hi all - we are assessing the viability of hosting a developer day at ELC in march in San Jose. This day would offer hands on Yocto Project training, advanced presentations, and one on one contact with YP developers. The cost would be about $200. The most recent dev day trained over 120 people in Duesseldorf at ELCE last fall. Please respond if you are interested in an event like this. We need a certain minimum number of interested folks before we can justify the expense. Thanks -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Potential Yocto Project developer day at ELC
Hi Jeff, On 01/13/2015 05:07 PM, Jeff Osier-Mixon wrote: > Hi all - we are assessing the viability of hosting a developer day at ELC > in march in San Jose. This day would offer hands on Yocto Project training, > advanced presentations, and one on one contact with YP developers. The cost > would be about $200. The most recent dev day trained over 120 people in > Duesseldorf at ELCE last fall. > > Please respond if you are interested in an event like this. We need a > certain minimum number of interested folks before we can justify the > expense. We'd also have to be attendees of the ELC conference I assume? Thanks, Philip -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Potential Yocto Project developer day at ELC
Hi Jefro, I'd be happy to support it if I can. Cheers, Rudi On Tue, Jan 13, 2015 at 2:58 PM, Philip Tricca wrote: > Hi Jeff, > > On 01/13/2015 05:07 PM, Jeff Osier-Mixon wrote: > > Hi all - we are assessing the viability of hosting a developer day at ELC > > in march in San Jose. This day would offer hands on Yocto Project > training, > > advanced presentations, and one on one contact with YP developers. The > cost > > would be about $200. The most recent dev day trained over 120 people in > > Duesseldorf at ELCE last fall. > > > > Please respond if you are interested in an event like this. We need a > > certain minimum number of interested folks before we can justify the > > expense. > > We'd also have to be attendees of the ELC conference I assume? > > Thanks, > Philip > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- *Rudolf J. Streif* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Potential Yocto Project developer day at ELC
On Tue, 13 Jan 2015, Rudolf Streif wrote: > Hi Jefro, > I'd be happy to support it if I can. if i can make it, i'd be glad to help. rday -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Potential Yocto Project developer day at ELC
I can help too. I'm planning of attending the conference. On Tue, Jan 13, 2015 at 11:07 PM, Jeff Osier-Mixon wrote: > Hi all - we are assessing the viability of hosting a developer day at ELC > in march in San Jose. This day would offer hands on Yocto Project training, > advanced presentations, and one on one contact with YP developers. The cost > would be about $200. The most recent dev day trained over 120 people in > Duesseldorf at ELCE last fall. > > Please respond if you are interested in an event like this. We need a > certain minimum number of interested folks before we can justify the > expense. > > Thanks > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- *Andrei Gherzan* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Potential Yocto Project developer day at ELC
I'd be willing to help out. On Tue, Jan 13, 2015 at 5:07 PM, Jeff Osier-Mixon wrote: > Hi all - we are assessing the viability of hosting a developer day at ELC > in march in San Jose. This day would offer hands on Yocto Project training, > advanced presentations, and one on one contact with YP developers. The cost > would be about $200. The most recent dev day trained over 120 people in > Duesseldorf at ELCE last fall. > > Please respond if you are interested in an event like this. We need a > certain minimum number of interested folks before we can justify the > expense. > > Thanks > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- Life is like Linux - it never stands still. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] basic questions on LINUX costomization for raspberrypi
Hello, Please read the meta-raspberrypi README for basic information and use . http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/tree/README 1) it depends on the image you are baking. What do you mean by reference list? 2) IMAGE_INSTALL_append http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-IMAGE_INSTALL What process are you talking about? 3) You modify the kernel config, recompile the kernel and then the image. We are developing a better way to configure kernel. Is already in review - hope to get some time for that soon. 4) Applications should be packages, right? Could you please rephrase your question? Cheers! On Thu, Dec 18, 2014 at 8:10 PM, abhishek srivastava < just_abh...@yahoo.co.in> wrote: > Hi allPlease answer to these questions regarding LINUX kernel image build > using yocto project: > 1) What basic LINUX packages needed for raspberrypi ? any list for > reference ? > 2) What if I want to add any package after my image is build ? Do i need > to repeat the complete process again? > 3) How can i add any driver (ex: TFT driver) to the build kernel image? > 4) How to add any desired applications to packages? > > Thank you for your help > > regards > > Abhishek > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- *Andrei Gherzan* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding drivers to rpi-basic-image
Hello On Tue, Dec 16, 2014 at 4:51 AM, abhishek srivastava < just_abh...@yahoo.co.in> wrote: > Hi all > I have generated image for raspberrypi basic image rpi-basic-image using > "hob" > > Now How can i add my TFT drivers or any other driver to the > rpi-basic-image? > You have to change the kernel config and recompile kernel and image. > I am also willing to know some more details on package importance in > building raspberrypi image such that what those packages would do, if I add > them to my image or how it helps? > What packages are you talking about? Be a little more specific. > Actually I am into making a customized LINUX just for my target > requirement so I want to be very specific on packages I am adding and why? > Please guide me. > > -- *Andrei Gherzan* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Potential Yocto Project developer day at ELC
Good question. ELC attendance is encouraged, but not required. On Jan 13, 2015 2:58 PM, "Philip Tricca" wrote: > Hi Jeff, > > On 01/13/2015 05:07 PM, Jeff Osier-Mixon wrote: > > Hi all - we are assessing the viability of hosting a developer day at ELC > > in march in San Jose. This day would offer hands on Yocto Project > training, > > advanced presentations, and one on one contact with YP developers. The > cost > > would be about $200. The most recent dev day trained over 120 people in > > Duesseldorf at ELCE last fall. > > > > Please respond if you are interested in an event like this. We need a > > certain minimum number of interested folks before we can justify the > > expense. > > We'd also have to be attendees of the ELC conference I assume? > > Thanks, > Philip > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH] audit-systemd: allow manual stop as sysvinit
From: Jackie Huang The audit service should be manually stopped with systemd. Signed-off-by: Jackie Huang --- recipes-security/audit/audit/auditd.service | 1 - 1 file changed, 1 deletion(-) diff --git a/recipes-security/audit/audit/auditd.service b/recipes-security/audit/audit/auditd.service index adf4d3b..ebc0798 100644 --- a/recipes-security/audit/audit/auditd.service +++ b/recipes-security/audit/audit/auditd.service @@ -5,7 +5,6 @@ After=local-fs.target Conflicts=shutdown.target Before=sysinit.target shutdown.target After=systemd-tmpfiles-setup.service -RefuseManualStop=yes [Service] ExecStart=/sbin/auditd -n -- 1.9.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
