Re: [yocto] Problems with postinstall
Nobody using any postinstalls?
I am still wondering why the postinstall does not work. I don't get any
error messages. The files are just not installed.
Am 05.06.2014 12:44, schrieb Neuer User:
> Hi
>
> I am desperately trying to get some postinstall scripts working. They
> should replace some defualt files with custom files I have. They are all
> in one package. The package looks like this:
>
> do_install() {
> install -d ${D}${sbindir}
> install -m 0700 ${S}/sbin/* ${D}${sbindir}
>
> install -d ${D}${bindir}
> install -m 0755 ${S}/bin/LEDstatus ${D}${bindir}
>
> install -d ${D}/etc/udev/rules.d
> install -m 0644 ${S}/udev/* ${D}/etc/udev/rules.d/
>
> install -d ${D}/etc/ssh
> install -m 0600 ${S}/ssh/ssh_* ${D}/etc/ssh/
> install -m 0644 ${S}/ssh/authorized_keys ${D}/etc/ssh/
>
> install -d ${D}/etc/gnupg
> install -m 0600 ${S}/gnupg/trustedkeys.gpg ${D}/etc/gnupg/
> }
>
> # Overwrite some configuration data with specific files
> pkg_postinst_${PN} () {
> install -o root -g root -m 0600 ${S}/ssh/sshd_config ${D}/etc/ssh/
> install -m 0755 ${S}/etc/rc.local ${D}/etc/
> install -m 0644 ${S}/etc/watchdog.conf ${D}/etc/
> install -m 0400 ${S}/etc/shadow ${D}/etc/
> install -m 0440 ${S}/etc/sudoers ${D}/etc/
> install -d ${D}/etc/default
> install -o root -g root -m 0644 ${S}/etc/default-ntpdate
> ${D}/etc/default/ntpdate
> }
>
> RDEPENDS_${PN} += "ntpdate udev ssh sudo"
>
> FILES_${PN} += "/*"
>
>
> I even tried changing the ownership of the files, but that did not
> change aything.
>
> Am I doing this completely wrong?
>
> Thanks for any hints
>
> Michael
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Live images?
On 2014-06-05 13:10, Gary Thomas wrote:
On 2014-06-05 11:24, Paul Eggleton wrote:
On Thursday 05 June 2014 11:16:55 Gary Thomas wrote:
On 2014-06-05 09:07, Paul Eggleton wrote:
On Thursday 05 June 2014 08:41:57 Gary Thomas wrote:
On 2014-06-05 08:32, Paul Eggleton wrote:
On Thursday 05 June 2014 15:26:28 Paul Eggleton wrote:
Hi Gary,
On Thursday 05 June 2014 07:07:34 Gary Thomas wrote:
Looking through the Poky/Yocto sources, there seems to be
some support for Live CD/USB images. However, I can't find
any examples nor documentation for how to use this.
Can anyone provide some pointers?
You're right, we seem to be missing that in our documentation; I'm not
sure
where the best place to document it would be though.
FYI, you should just need to ensure "live" is in IMAGE_FSTYPES; then
you
should get a .directdisk image that you can just dd to a USB stick.
Of course I meant to say .hddimg, not .directdisk.
Thanks, I'll give that a try.
What if I needed to boot from an actual CD? I have an old
box here I'd like to try, but it doesn't boot from USB.
We can produce ISO images but I don't think that they work quite as well,
e.g.:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5282
You could always try it though.
Bummer, when I tried to build core-image-minimal and/or core-image-x11, it
failed:
| DEBUG: Executing shell function read_only_rootfs_hook
| sed: can't read
| /home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image
| -minimal-initramfs/1.0-r0/rootfs/etc/fstab: No such file or directory
| WARNING:
| /home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image
| -minimal-initramfs/1.0-r0/temp/run.read_only_rootfs_hook.30446:1 exit 2
| from|
| sed -i -e
| '/^[#[:space:]]*\/dev\/root/{s/defaults/ro/;s/\([[:space:]]*[[:digit:]]
| \)\([[:space:]]*\)[[:digit:]]$/\1\20/}'
/home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image-mi
nimal-initramfs/1.0-r0/rootfs/etc/fstab
| DEBUG: Python function do_rootfs finished
| ERROR: Function failed: read_only_rootfs_hook (log file is located at
/home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image-mi
nimal-initramfs/1.0-r0/temp/log.do_rootfs.30446)
Using these settings:
Build Configuration:
BB_VERSION= "1.23.1"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING = "Fedora-13"
TARGET_SYS= "i586-poky-linux"
MACHINE = "genericx86"
DISTRO= "poky"
DISTRO_VERSION= "1.6+snapshot-20140605"
TUNE_FEATURES = "m32 core2"
TARGET_FPU= ""
meta
meta-yocto
meta-yocto-bsp= "master:e7114046be6e71fb326477dc882adb814ef6a751"
Extra settings in conf/local.conf
# Live CD setup
IMAGE_FSTYPES_append = " hddimg live"
"hddimg" isn't a valid IMAGE_FSTYPES item.
Also, try IMAGE_FSTYPES += rather than _append, that allows the initramfs
image to have its own value (because it's not really valid to make a live
initramfs...)
Sorry, I misread/misapplied your previous suggestions.
IMAGE_FEATURES_append = " read-only-rootfs"
Try EXTRA_IMAGE_FEATURES += instead of IMAGE_FEATURES_append
I've changed both of these and it still fails if I enable the
read-only-rootfs.
If I leave that option out, I can build an .hddimg which I dd'd
to my USB stick. It tried to boot, finds /vmlinuz but fails to
find /initrd
My local.conf settings are now:
# Live CD setup
IMAGE_FSTYPES += " live"
#IMAGE_FEATURES += " read-only-rootfs"
CORE_IMAGE_EXTRA_INSTALL += " python-core python-modules"
Finally, during one of my builds, I ended up with a core-image-minimal*.iso
I tried burning this to a CD an it booted up, albeit with a couple of
complaints about a read-only rootfs. Sadly, I no longer get any .iso
results when I 'bitbake core-image-minimal'
BTW, I tried this with daisy and the CD version (read-only)
worked just fine for me - the ISO and .hddimg files built with
no errors.
I'm bisecting now to see what broke...
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] List of Binary Files from a recipe
Hi Ross, Thank you for the response. rpm -qf would give us the package name. Thanks, Bharath On Thu, Jun 5, 2014 at 4:13 PM, Burton, Ross wrote: > On 5 June 2014 21:50, Bharath Chandra wrote: > > I am working on a reverse enginnering project and I want to know by > looking > > at an executable , the recipe file from which it is generated. So, first > I > > need to understand by using what commands in a recipe file, we can > generate > > an executable. > > If you actually need to know what recipe produced a binary without > instrumenting the binaries, then use the package manager: they all > have a command to tell you what binary package installed a file, and > from the binary package you can determine the source package, and > that's got the same name as the recipe. > > Ross > -- Thanks & Regards, Bharath Chandra Elluru. Contact Number:785-979-4875. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] List of Binary Files from a recipe
On 5 June 2014 21:50, Bharath Chandra wrote: > I am working on a reverse enginnering project and I want to know by looking > at an executable , the recipe file from which it is generated. So, first I > need to understand by using what commands in a recipe file, we can generate > an executable. If you actually need to know what recipe produced a binary without instrumenting the binaries, then use the package manager: they all have a command to tell you what binary package installed a file, and from the binary package you can determine the source package, and that's got the same name as the recipe. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] List of Binary Files from a recipe
Hi, I am working on a reverse enginnering project and I want to know by looking at an executable , the recipe file from which it is generated. So, first I need to understand by using what commands in a recipe file, we can generate an executable. -- Thanks & Regards, Bharath Chandra Elluru. Contact Number:785-979-4875. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH V2] opkg-build: add detection if using GNU tar.
Great!, Have a good evening, Tom On 5 June 2014 20:56, Paul Barker wrote: > On Tue, Jun 03, 2014 at 11:25:35AM +0100, t...@ewsting.org wrote: >> From: Thomas Ingleby >> >> * Some options of GNU tar do not exist on other implementations >> >> Signed-off-by: Thomas Ingleby > > I've made a couple of slight further changes, hope you don't mind. > > I've changed the subject to: > > opkg-build: Detect if tar supports '--format' option > > I've also added a comment before the block of code which sets tarformat: > > +# Determine if tar supports the --format argument by checking the help > output. > +# > +# This is needed because: > +#- Busybox tar doesn't support '--format' > +#- On some Linux distros, tar now defaults to posix format if '--format' > +# isn't explictly specified > +#- Opkg doesn't currently support posix format archives > +# > +# It's easier to check for mention of the '--format' option than to detect > the > +# tar implementation and maintain a list of which support '--format'. > > I've merged this to master with those changes. Sadly I made an error writing > the > comment and pushed too soon so I've pushed another commit to fix that. > > Many thanks, > > -- > Paul Barker > > Email: p...@paulbarker.me.uk > http://www.paulbarker.me.uk -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH V2] opkg-build: add detection if using GNU tar.
On Tue, Jun 03, 2014 at 11:25:35AM +0100, t...@ewsting.org wrote: > From: Thomas Ingleby > > * Some options of GNU tar do not exist on other implementations > > Signed-off-by: Thomas Ingleby I've made a couple of slight further changes, hope you don't mind. I've changed the subject to: opkg-build: Detect if tar supports '--format' option I've also added a comment before the block of code which sets tarformat: +# Determine if tar supports the --format argument by checking the help output. +# +# This is needed because: +#- Busybox tar doesn't support '--format' +#- On some Linux distros, tar now defaults to posix format if '--format' +# isn't explictly specified +#- Opkg doesn't currently support posix format archives +# +# It's easier to check for mention of the '--format' option than to detect the +# tar implementation and maintain a list of which support '--format'. I've merged this to master with those changes. Sadly I made an error writing the comment and pushed too soon so I've pushed another commit to fix that. Many thanks, -- Paul Barker Email: p...@paulbarker.me.uk http://www.paulbarker.me.uk pgpzpZNNjXUj3.pgp Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] how to specify if multiple bb files are existing
Excellent, that is what I expected. Glad you found the root cause. I am not exactly a friend of setting DEFAULT_PREFERRENCE in a recipe because it leads to these confusing issues. On Jun 5, 2014 11:11 AM, "Insop Song" wrote: > Hi Rudi, > > > I looked more and found out that the reason why 2013.01.01.bb, which > is the latest, was not picked was due to "DEFAULT_PREFERENCE = -1" in > that file. > > I was using this file from here : > > http://git.freescale.com/git/cgit.cgi/ppc/sdk/poky.git/tree/meta/recipes-bsp/u-boot/u-boot-fw-utils_2013.01.01.bb?h=dylan > > Thank you. > > ISS > > On Wed, Jun 4, 2014 at 7:27 PM, Insop Song wrote: > > Hi Rudi, > > > > Thank you very much for your help. > > I've added PREFERRED_VERSION and started build. > > > > Regards, > > > > Insop > > > > On Wed, Jun 4, 2014 at 6:37 PM, Rudolf Streif > > wrote: > >> Hi Insop, > >> > >> Technically u-boot-fw-utils_2013.01.01 should be used because it's the > newer > >> version. However, you can explicitly specify > >> > >> PREFERRED_VERSION_u-boot-fw-utils = "2013.01.01" > >> > >> Cheers, > >> Rudi > >> > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Live images?
On 2014-06-05 11:24, Paul Eggleton wrote:
On Thursday 05 June 2014 11:16:55 Gary Thomas wrote:
On 2014-06-05 09:07, Paul Eggleton wrote:
On Thursday 05 June 2014 08:41:57 Gary Thomas wrote:
On 2014-06-05 08:32, Paul Eggleton wrote:
On Thursday 05 June 2014 15:26:28 Paul Eggleton wrote:
Hi Gary,
On Thursday 05 June 2014 07:07:34 Gary Thomas wrote:
Looking through the Poky/Yocto sources, there seems to be
some support for Live CD/USB images. However, I can't find
any examples nor documentation for how to use this.
Can anyone provide some pointers?
You're right, we seem to be missing that in our documentation; I'm not
sure
where the best place to document it would be though.
FYI, you should just need to ensure "live" is in IMAGE_FSTYPES; then
you
should get a .directdisk image that you can just dd to a USB stick.
Of course I meant to say .hddimg, not .directdisk.
Thanks, I'll give that a try.
What if I needed to boot from an actual CD? I have an old
box here I'd like to try, but it doesn't boot from USB.
We can produce ISO images but I don't think that they work quite as well,
e.g.:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5282
You could always try it though.
Bummer, when I tried to build core-image-minimal and/or core-image-x11, it
failed:
| DEBUG: Executing shell function read_only_rootfs_hook
| sed: can't read
| /home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image
| -minimal-initramfs/1.0-r0/rootfs/etc/fstab: No such file or directory
| WARNING:
| /home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image
| -minimal-initramfs/1.0-r0/temp/run.read_only_rootfs_hook.30446:1 exit 2
| from|
| sed -i -e
| '/^[#[:space:]]*\/dev\/root/{s/defaults/ro/;s/\([[:space:]]*[[:digit:]]
| \)\([[:space:]]*\)[[:digit:]]$/\1\20/}'
/home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image-mi
nimal-initramfs/1.0-r0/rootfs/etc/fstab
| DEBUG: Python function do_rootfs finished
| ERROR: Function failed: read_only_rootfs_hook (log file is located at
/home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image-mi
nimal-initramfs/1.0-r0/temp/log.do_rootfs.30446)
Using these settings:
Build Configuration:
BB_VERSION= "1.23.1"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING = "Fedora-13"
TARGET_SYS= "i586-poky-linux"
MACHINE = "genericx86"
DISTRO= "poky"
DISTRO_VERSION= "1.6+snapshot-20140605"
TUNE_FEATURES = "m32 core2"
TARGET_FPU= ""
meta
meta-yocto
meta-yocto-bsp= "master:e7114046be6e71fb326477dc882adb814ef6a751"
Extra settings in conf/local.conf
# Live CD setup
IMAGE_FSTYPES_append = " hddimg live"
"hddimg" isn't a valid IMAGE_FSTYPES item.
Also, try IMAGE_FSTYPES += rather than _append, that allows the initramfs
image to have its own value (because it's not really valid to make a live
initramfs...)
Sorry, I misread/misapplied your previous suggestions.
IMAGE_FEATURES_append = " read-only-rootfs"
Try EXTRA_IMAGE_FEATURES += instead of IMAGE_FEATURES_append
I've changed both of these and it still fails if I enable the
read-only-rootfs.
If I leave that option out, I can build an .hddimg which I dd'd
to my USB stick. It tried to boot, finds /vmlinuz but fails to
find /initrd
My local.conf settings are now:
# Live CD setup
IMAGE_FSTYPES += " live"
#IMAGE_FEATURES += " read-only-rootfs"
CORE_IMAGE_EXTRA_INSTALL += " python-core python-modules"
Finally, during one of my builds, I ended up with a core-image-minimal*.iso
I tried burning this to a CD an it booted up, albeit with a couple of
complaints about a read-only rootfs. Sadly, I no longer get any .iso
results when I 'bitbake core-image-minimal'
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] how to specify if multiple bb files are existing
Hi Rudi, I looked more and found out that the reason why 2013.01.01.bb, which is the latest, was not picked was due to "DEFAULT_PREFERENCE = -1" in that file. I was using this file from here : http://git.freescale.com/git/cgit.cgi/ppc/sdk/poky.git/tree/meta/recipes-bsp/u-boot/u-boot-fw-utils_2013.01.01.bb?h=dylan Thank you. ISS On Wed, Jun 4, 2014 at 7:27 PM, Insop Song wrote: > Hi Rudi, > > Thank you very much for your help. > I've added PREFERRED_VERSION and started build. > > Regards, > > Insop > > On Wed, Jun 4, 2014 at 6:37 PM, Rudolf Streif > wrote: >> Hi Insop, >> >> Technically u-boot-fw-utils_2013.01.01 should be used because it's the newer >> version. However, you can explicitly specify >> >> PREFERRED_VERSION_u-boot-fw-utils = "2013.01.01" >> >> Cheers, >> Rudi >> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Live images?
On Thursday 05 June 2014 11:16:55 Gary Thomas wrote:
> On 2014-06-05 09:07, Paul Eggleton wrote:
> > On Thursday 05 June 2014 08:41:57 Gary Thomas wrote:
> >> On 2014-06-05 08:32, Paul Eggleton wrote:
> >>> On Thursday 05 June 2014 15:26:28 Paul Eggleton wrote:
> >>>> Hi Gary,
> >>>>
> >>>> On Thursday 05 June 2014 07:07:34 Gary Thomas wrote:
> >>>>> Looking through the Poky/Yocto sources, there seems to be
> >>>>> some support for Live CD/USB images. However, I can't find
> >>>>> any examples nor documentation for how to use this.
> >>>>>
> >>>>> Can anyone provide some pointers?
> >>>>
> >>>> You're right, we seem to be missing that in our documentation; I'm not
> >>>> sure
> >>>> where the best place to document it would be though.
> >>>>
> >>>> FYI, you should just need to ensure "live" is in IMAGE_FSTYPES; then
> >>>> you
> >>>> should get a .directdisk image that you can just dd to a USB stick.
> >>>
> >>> Of course I meant to say .hddimg, not .directdisk.
> >>
> >> Thanks, I'll give that a try.
> >>
> >> What if I needed to boot from an actual CD? I have an old
> >> box here I'd like to try, but it doesn't boot from USB.
> >
> > We can produce ISO images but I don't think that they work quite as well,
> > e.g.:
> >
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=5282
> >
> > You could always try it though.
>
> Bummer, when I tried to build core-image-minimal and/or core-image-x11, it
failed:
> | DEBUG: Executing shell function read_only_rootfs_hook
> | sed: can't read
> | /home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image
> | -minimal-initramfs/1.0-r0/rootfs/etc/fstab: No such file or directory
> | WARNING:
> | /home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image
> | -minimal-initramfs/1.0-r0/temp/run.read_only_rootfs_hook.30446:1 exit 2
> | from|
> | sed -i -e
> | '/^[#[:space:]]*\/dev\/root/{s/defaults/ro/;s/\([[:space:]]*[[:digit:]]
> | \)\([[:space:]]*\)[[:digit:]]$/\1\20/}'
> /home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image-mi
> nimal-initramfs/1.0-r0/rootfs/etc/fstab
> | DEBUG: Python function do_rootfs finished
> | ERROR: Function failed: read_only_rootfs_hook (log file is located at
>
> /home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image-mi
> nimal-initramfs/1.0-r0/temp/log.do_rootfs.30446)
>
> Using these settings:
> Build Configuration:
> BB_VERSION= "1.23.1"
> BUILD_SYS = "i686-linux"
> NATIVELSBSTRING = "Fedora-13"
> TARGET_SYS= "i586-poky-linux"
> MACHINE = "genericx86"
> DISTRO= "poky"
> DISTRO_VERSION= "1.6+snapshot-20140605"
> TUNE_FEATURES = "m32 core2"
> TARGET_FPU= ""
> meta
> meta-yocto
> meta-yocto-bsp= "master:e7114046be6e71fb326477dc882adb814ef6a751"
>
> Extra settings in conf/local.conf
> # Live CD setup
> IMAGE_FSTYPES_append = " hddimg live"
"hddimg" isn't a valid IMAGE_FSTYPES item.
Also, try IMAGE_FSTYPES += rather than _append, that allows the initramfs
image to have its own value (because it's not really valid to make a live
initramfs...)
> IMAGE_FEATURES_append = " read-only-rootfs"
Try EXTRA_IMAGE_FEATURES += instead of IMAGE_FEATURES_append
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Live images?
On 2014-06-05 09:07, Paul Eggleton wrote:
On Thursday 05 June 2014 08:41:57 Gary Thomas wrote:
On 2014-06-05 08:32, Paul Eggleton wrote:
On Thursday 05 June 2014 15:26:28 Paul Eggleton wrote:
Hi Gary,
On Thursday 05 June 2014 07:07:34 Gary Thomas wrote:
Looking through the Poky/Yocto sources, there seems to be
some support for Live CD/USB images. However, I can't find
any examples nor documentation for how to use this.
Can anyone provide some pointers?
You're right, we seem to be missing that in our documentation; I'm not
sure
where the best place to document it would be though.
FYI, you should just need to ensure "live" is in IMAGE_FSTYPES; then you
should get a .directdisk image that you can just dd to a USB stick.
Of course I meant to say .hddimg, not .directdisk.
Thanks, I'll give that a try.
What if I needed to boot from an actual CD? I have an old
box here I'd like to try, but it doesn't boot from USB.
We can produce ISO images but I don't think that they work quite as well,
e.g.:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5282
You could always try it though.
Bummer, when I tried to build core-image-minimal and/or core-image-x11, it
failed:
| DEBUG: Executing shell function read_only_rootfs_hook
| sed: can't read
/home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image-minimal-initramfs/1.0-r0/rootfs/etc/fstab:
No such file or directory
| WARNING:
/home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image-minimal-initramfs/1.0-r0/temp/run.read_only_rootfs_hook.30446:1
exit 2 from
| sed -i -e '/^[#[:space:]]*\/dev\/root/{s/defaults/ro/;s/\([[:space:]]*[[:digit:]]\)\([[:space:]]*\)[[:digit:]]$/\1\20/}'
/home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image-minimal-initramfs/1.0-r0/rootfs/etc/fstab
| DEBUG: Python function do_rootfs finished
| ERROR: Function failed: read_only_rootfs_hook (log file is located at
/home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image-minimal-initramfs/1.0-r0/temp/log.do_rootfs.30446)
Using these settings:
Build Configuration:
BB_VERSION= "1.23.1"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING = "Fedora-13"
TARGET_SYS= "i586-poky-linux"
MACHINE = "genericx86"
DISTRO= "poky"
DISTRO_VERSION= "1.6+snapshot-20140605"
TUNE_FEATURES = "m32 core2"
TARGET_FPU= ""
meta
meta-yocto
meta-yocto-bsp= "master:e7114046be6e71fb326477dc882adb814ef6a751"
Extra settings in conf/local.conf
# Live CD setup
IMAGE_FSTYPES_append = " hddimg live"
IMAGE_FEATURES_append = " read-only-rootfs"
CORE_IMAGE_EXTRA_INSTALL_append = " python python-modules"
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Live images?
On Thursday 05 June 2014 08:41:57 Gary Thomas wrote: > On 2014-06-05 08:32, Paul Eggleton wrote: > > On Thursday 05 June 2014 15:26:28 Paul Eggleton wrote: > >> Hi Gary, > >> > >> On Thursday 05 June 2014 07:07:34 Gary Thomas wrote: > >>> Looking through the Poky/Yocto sources, there seems to be > >>> some support for Live CD/USB images. However, I can't find > >>> any examples nor documentation for how to use this. > >>> > >>> Can anyone provide some pointers? > >> > >> You're right, we seem to be missing that in our documentation; I'm not > >> sure > >> where the best place to document it would be though. > >> > >> FYI, you should just need to ensure "live" is in IMAGE_FSTYPES; then you > >> should get a .directdisk image that you can just dd to a USB stick. > > > > Of course I meant to say .hddimg, not .directdisk. > > Thanks, I'll give that a try. > > What if I needed to boot from an actual CD? I have an old > box here I'd like to try, but it doesn't boot from USB. We can produce ISO images but I don't think that they work quite as well, e.g.: https://bugzilla.yoctoproject.org/show_bug.cgi?id=5282 You could always try it though. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Building for Boards not supported by Yocto Project
On 14-06-05 07:28 AM, Kashyap Gada wrote: Hello. I have successfully built and tested core-image-sato through the process given by the quick start guide at the yocto project website. Now I intend to build an image for a board which is not officially supported by yocto project. I have a FriendlyArm mini6410 whose BSP is available for linux. I would like to know how should I proceed further. Is it possible to use the same BSP without any changes and make an image using Yocto? Using the Yocto BSP guide (http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html) as a reference, you can create a minimal BSP layer for the board. You don't have to do everything in the guide, but you do need to have a machine definition, the userspace tuning and a custom kernel recipe for the platform (i.e. you point at some vendor or project tree that has all the required patches). Unless the support for the board is already in the mainline kernel, and then you can have a custom linux-yocto recipe to leverage the existing configuration and code in the linux-yocto repository. Cheers, Bruce Kashyap Gada -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Live images?
On 2014-06-05 08:32, Paul Eggleton wrote: On Thursday 05 June 2014 15:26:28 Paul Eggleton wrote: Hi Gary, On Thursday 05 June 2014 07:07:34 Gary Thomas wrote: Looking through the Poky/Yocto sources, there seems to be some support for Live CD/USB images. However, I can't find any examples nor documentation for how to use this. Can anyone provide some pointers? You're right, we seem to be missing that in our documentation; I'm not sure where the best place to document it would be though. FYI, you should just need to ensure "live" is in IMAGE_FSTYPES; then you should get a .directdisk image that you can just dd to a USB stick. Of course I meant to say .hddimg, not .directdisk. Thanks, I'll give that a try. What if I needed to boot from an actual CD? I have an old box here I'd like to try, but it doesn't boot from USB. -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Live images?
On Thursday 05 June 2014 15:26:28 Paul Eggleton wrote: > Hi Gary, > > On Thursday 05 June 2014 07:07:34 Gary Thomas wrote: > > Looking through the Poky/Yocto sources, there seems to be > > some support for Live CD/USB images. However, I can't find > > any examples nor documentation for how to use this. > > > > Can anyone provide some pointers? > > You're right, we seem to be missing that in our documentation; I'm not sure > where the best place to document it would be though. > > FYI, you should just need to ensure "live" is in IMAGE_FSTYPES; then you > should get a .directdisk image that you can just dd to a USB stick. Of course I meant to say .hddimg, not .directdisk. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Live images?
Hi Gary, On Thursday 05 June 2014 07:07:34 Gary Thomas wrote: > Looking through the Poky/Yocto sources, there seems to be > some support for Live CD/USB images. However, I can't find > any examples nor documentation for how to use this. > > Can anyone provide some pointers? You're right, we seem to be missing that in our documentation; I'm not sure where the best place to document it would be though. FYI, you should just need to ensure "live" is in IMAGE_FSTYPES; then you should get a .directdisk image that you can just dd to a USB stick. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Live images?
Looking through the Poky/Yocto sources, there seems to be some support for Live CD/USB images. However, I can't find any examples nor documentation for how to use this. Can anyone provide some pointers? Thanks -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] TARGET_ARCH in external toolchain
I've found a problem. TARGET_ARCH in fact isn't set but I can still use conditional syntax. The problem was I was trying with ppc architecture (TARGET_ARCH is later set to ppc) but here I had to use "powerpc" instead. BR, Marek Andrus On 05.06.2014 13:02, Marek Andrus wrote: Hi, I'd like to provide one meta for a 4 external toolchains (for 4 different architectures). I wanted it to select appropriate toolchain accroding to a TARGET_ARCH variable. Unfortunately TARGET_ARCH looks like not being set at the time of parsing my tcmode-external-mytc.inc file (where preffered providers are set). Of course OVERRIDES variable is not set either. What do you recommend? Of course I can change the toolchain layer manually but I wanted to change machine/architecture in just one place. Is there any method? BR, Marek Andrus -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Building for Boards not supported by Yocto Project
Hello. I have successfully built and tested core-image-sato through the process given by the quick start guide at the yocto project website. Now I intend to build an image for a board which is not officially supported by yocto project. I have a FriendlyArm mini6410 whose BSP is available for linux. I would like to know how should I proceed further. Is it possible to use the same BSP without any changes and make an image using Yocto? Kashyap Gada -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] TARGET_ARCH in external toolchain
Hi, I'd like to provide one meta for a 4 external toolchains (for 4 different architectures). I wanted it to select appropriate toolchain accroding to a TARGET_ARCH variable. Unfortunately TARGET_ARCH looks like not being set at the time of parsing my tcmode-external-mytc.inc file (where preffered providers are set). Of course OVERRIDES variable is not set either. What do you recommend? Of course I can change the toolchain layer manually but I wanted to change machine/architecture in just one place. Is there any method? BR, Marek Andrus -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Problems with postinstall
Hi
I am desperately trying to get some postinstall scripts working. They
should replace some defualt files with custom files I have. They are all
in one package. The package looks like this:
do_install() {
install -d ${D}${sbindir}
install -m 0700 ${S}/sbin/* ${D}${sbindir}
install -d ${D}${bindir}
install -m 0755 ${S}/bin/LEDstatus ${D}${bindir}
install -d ${D}/etc/udev/rules.d
install -m 0644 ${S}/udev/* ${D}/etc/udev/rules.d/
install -d ${D}/etc/ssh
install -m 0600 ${S}/ssh/ssh_* ${D}/etc/ssh/
install -m 0644 ${S}/ssh/authorized_keys ${D}/etc/ssh/
install -d ${D}/etc/gnupg
install -m 0600 ${S}/gnupg/trustedkeys.gpg ${D}/etc/gnupg/
}
# Overwrite some configuration data with specific files
pkg_postinst_${PN} () {
install -o root -g root -m 0600 ${S}/ssh/sshd_config ${D}/etc/ssh/
install -m 0755 ${S}/etc/rc.local ${D}/etc/
install -m 0644 ${S}/etc/watchdog.conf ${D}/etc/
install -m 0400 ${S}/etc/shadow ${D}/etc/
install -m 0440 ${S}/etc/sudoers ${D}/etc/
install -d ${D}/etc/default
install -o root -g root -m 0644 ${S}/etc/default-ntpdate
${D}/etc/default/ntpdate
}
RDEPENDS_${PN} += "ntpdate udev ssh sudo"
FILES_${PN} += "/*"
I even tried changing the ownership of the files, but that did not
change aything.
Am I doing this completely wrong?
Thanks for any hints
Michael
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
