[yocto] Best practices for changing a conf file
Hi all, I'm just looking for some advice on best practices. I want to change the configuration file for rsyslog called rsyslog.conf (poky/meta/recipes-extended/rsyslog), but there is a certain appeal to me of not changing the files in the meta directory. I like to keep those pristine and accomplish everything I need with recipes in a different layer. Is the best way to change this file to just go in and change that .conf file, or is there an easy way to use a .bbappend file to substitute my own configuration file? Thanks, -Nick Nick Crast Associate Software Engineer Saab Sensis Corporation Phone: 315-445-5703 Email: nicholas.cr...@saabsensis.commailto:nicholas.cr...@saabsensis.com This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Start daemon or execute script at boot time
Take a look at this link: http://docs.openembedded.ru/update-rc-d_class.html It has some good examples and explanation about how to modify the startup sequence. -Nick Nick Crast Associate Software Engineer Saab Sensis Corporation Phone: 315-445-5703 Email: nicholas.cr...@saabsensis.com -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of jags gediya Sent: Friday, September 19, 2014 11:17 AM To: meta-freesc...@yoctoproject.org; yocto@yoctoproject.org Subject: [yocto] Start daemon or execute script at boot time Hi All, If i want to execute some thing or start daemon at boot time, where can i make changes in yocto source code, so that it reflects in the file-system? Thanks, Jags -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Eglibc-locale QA Failure
All,
When I try to build based on poky-tiny, I get the following error:
ERROR: QA Issue: eglibc-locale: Files/directories were installed but not shipped
/usr/lib
/usr/bin
/usr/lib/locale
/usr/share/i18n
/usr/share/i18n/locales
/usr/share/i18n/locales/POSIX
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa
Here is the image recipe I am running:
DESCRIPTION = A console-only image with more full-featured Linux system \
functionality installed.
module_autoload_fwreg = fwreg
IMAGE_INSTALL = \
packagegroup-core-boot \
${ROOTFS_PKGMANAGE_BOOTSTRAP} \
${CORE_IMAGE_EXTRA_INSTALL} \
openssh \
inherit core-image
Can anyone help me figure out what the problem is?
-Nick
Nick Crast
Associate Software Engineer
Saab Sensis Corporation
Phone: 315-445-5703
Email: nicholas.cr...@saabsensis.commailto:nicholas.cr...@saabsensis.com
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Enabling Ramdisk Support
All, I am having some issues with initrd using u-boot and yocto. My current .config file in build/tmp/work/mitysom_5csx-poky-linux-gnueabi/linux-mitysom-5csx/3.12-r2/linux-socfpga-socfpga-3.12-7cb4fc4 has the following settings: CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_RD_GZIP=y Whenever I attempt to boot up with an initrd, I get a message saying that the kernel was unable to mount the rootfs. What concerns me, though, is I don't see any RAMDISK initialization messages on startup. Looking online, I figure I should see something like this: [root]# dmesg | grep RAMDISK RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize When I boot up, or at least some sort of error from RAMDISK. Is there a way I can verify that this option is actually being built into my system? -Nick Nick Crast Associate Software Engineer Saab Sensis Corporation Phone: 315-445-5703 Email: nicholas.cr...@saabsensis.commailto:nicholas.cr...@saabsensis.com This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Using uboot to boot a large uimage
I am currently attempting to boot with an initramfs built into my uimage using uboot. However, I cannot get it to boot correctly. If I make the uimage totally bare-bones, and just use core-image-minimal-initramfs, then it hangs huring init at the waiting for devices... printout. Going and gutting the init script, I can get to single user mode and it looks like the filesystem is there. I want a more full system, so I included core-image-boot and core-image-basic. I figured this would initialize better. When I do this, my uImage jumps up to ~50MB. U-boot then hangs at starting kernel... I don't think that the uimage is clobbering the device tree, because the device tree is loaded at 0x100, and the uimage is loaded at 0x8000. Any ideas? Nick Crast Associate Software Engineer Saab Sensis Corporation Phone: 315-445-5703 Email: nicholas.cr...@saabsensis.com - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Using uboot to boot a large uimage
Here is what I am seeing with core-image-minimal
32612024 bytes read in 11244 ms (2.8 MiB/s)
18179 bytes read in 30 ms (590.8 KiB/s)
## Booting kernel from Legacy Image at 0010 ...
Image Name: Linux-3.12.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:32611960 Bytes = 31.1 MiB
Load Address: 8000
Entry Point: 8000
## Flattened Device Tree blob at 0100
Booting using the fdt blob at 0x0100
Loading Kernel Image ... OK
OK
Loading Device Tree to 03ff8000, end 03fff702 ... OK
Starting kernel ...
If I make the uBoot image ~3 MB just using core-image-minimal-initramfs, I get
different results. Here are the relevant part of my uboot configuration:
fdtaddr=0x0100
fdtimage=/boot/socfpga_mitysom5csx.dtb
fdtimagesize=0x2000
mmcboot=setenv bootargs console=ttyS0,115200 root=${mmcroot} rw rootwait;bootm
${loadaddr} - ${fdtaddr}
mmcload=mmc rescan;${mmcloadcmd} mmc 0:${mmcloadpart} ${loadaddr}
${bootimage};${mmcloadcmd} mmc 0:${mmcloadpart} ${fdtaddr} ${fdtimage}
mmcloadcmd=ext2load
mmcloadpart=2
mmcroot=/dev/mmcblk0p2
Nick Crast
Associate Software Engineer
Saab Sensis Corporation
Phone: 315-445-5703
Email: nicholas.cr...@saabsensis.com
-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Tuesday, August 26, 2014 4:01 PM
To: Crast, Nicholas
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Using uboot to boot a large uimage
On 14-08-26 18:41:22, Crast, Nicholas wrote:
I am currently attempting to boot with an initramfs built into my uimage
using uboot.
However, I cannot get it to boot correctly. If I make the uimage totally
bare-bones, and just use core-image-minimal-initramfs, then it hangs huring
init at the waiting for devices... printout. Going and gutting the init
script, I can get to single user mode and it looks like the filesystem is
there.
I want a more full system, so I included core-image-boot and
core-image-basic. I figured this would initialize better. When I do this, my
uImage jumps up to ~50MB. U-boot then hangs at starting kernel...
core-image-minimal should boot you into shell console. That should have been
enough
I don't think that the uimage is clobbering the device tree, because the
device tree is loaded at 0x100, and the uimage is loaded at 0x8000.
make sure that memory is not overlapping and is initiaized
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
-
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Bundling initramfs with uImage
Thanks, This seems like a clean way to do what I want to do. So this means whenever I do a build, it will 1.) Build the kernel 2.) Build the filesystem (initramfs) 3.) Rebuild the kernel with the bundled intramfs Correct? -Nick Nick Crast Associate Software Engineer Saab Sensis Corporation Phone: 315-445-5703 Email: nicholas.cr...@saabsensis.com -Original Message- From: Khem Raj [mailto:raj.k...@gmail.com] Sent: Monday, August 25, 2014 1:32 AM To: Crast, Nicholas Cc: yocto@yoctoproject.org Subject: Re: [yocto] Bundling initramfs with uImage On 14-08-21 20:18:41, Crast, Nicholas wrote: All, I am currently working in an embedded environment, struggling to get the entire system running in RAM, so that everything is fresh after a reboot. I can currently use the initramfs-live-boot functionality to generate a .cpio.gz file, but I am lost on how to get this to 'bundle' with the uImage. The uImage will be stored on an SD card and we are using u-boot. I see mentions of the CONFIG_INITRAMFS_SOURCE kernel option, but I am unsure if I need to change this. Can someone help me? I've been googling all day and haven't gotten much further. if you add INITRAMFS_IMAGE_BUNDLE = 1 INITRAMFS_IMAGE = name of your initramfs-image in you local.conf that should help it to create uImage with everything in it. -Khem - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Bundling initramfs with uImage
All, I am currently working in an embedded environment, struggling to get the entire system running in RAM, so that everything is fresh after a reboot. I can currently use the initramfs-live-boot functionality to generate a .cpio.gz file, but I am lost on how to get this to 'bundle' with the uImage. The uImage will be stored on an SD card and we are using u-boot. I see mentions of the CONFIG_INITRAMFS_SOURCE kernel option, but I am unsure if I need to change this. Can someone help me? I've been googling all day and haven't gotten much further. -Nick Nick Crast Associate Software Engineer Saab Sensis Corporation Phone: 315-445-5703 Email: nicholas.cr...@saabsensis.commailto:nicholas.cr...@saabsensis.com This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Setting Default User Accounts
All,
I am currently in the middle of a battle with yocto, trying to accomplish the
following:
1.)Disable root user account
2.)Create default user account with default password
I currently have the following a recipe:
USERADD_PACKAGES = ${PN}
USERADD_PARAM_${PN} = -d /home/nick -r -s /bin/bash nick
In order to try to add a user account. I have this in my image recipe:
ROOTFS_POSTPROCESS_COMMAND += set_nick_passwd;
set_nick_passwd() {
sed 's%^ nick:[^:]*:% nick:adySxRKMiPvjA:%' \
${IMAGE_ROOTFS}/etc/shadow \
${IMAGE_ROOTFS}/etc/shadow.new;
mv ${IMAGE_ROOTFS}/etc/shadow.new ${IMAGE_ROOTFS}/etc/shadow ;
}
This is to edit the /etc/shadow file and insert a new (hashed) password. What
I'm looking for is a cleaner way to do this. When I run bitbake I get a lot of
warnings because the nick account is already an account on my build machine.
This seems like a fairly common use case, and I think I am likely going about
it wrong.
Does anybody have any advice?
-Nick
Nick Crast
Associate Software Engineer
Saab Sensis Corporation
Phone: 315-445-5703
Email: nicholas.cr...@saabsensis.commailto:nicholas.cr...@saabsensis.com
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
