Looks like it's dropping the service in ${sysconfdir}/init.d which resolves
to /etc/init.d. I'm not sure that systemd won't look into init.d for
services. The standard place to put them is ${D}/${systemd_system_unitdir},
which resolves to /lib/systemd/system.
Also, check the
Is there a recommended way of doing this? Right now I have a
ROOTFS_POSTPROCESS_CMD that moves the directories and symlinks them back,
but I'm not sure if I'm doing it exactly right or if there's something
built-in.
The function just does a bunch of this:
install -d ${D}/${persist_dir}
I'm working with a read only file system and I'm working on splitting
packages so that their config dirs are symlinked in from the persistent
data partition. But I'd like to be able to enable or disable this
optionally, so that I can still build an image with a r/w file system and a
single
Ok, I think I'm along the path to figuring this out. Realized that
btrfs-tools-native:do_populate_sysroot needed to be explicitly run by
something.
On Tue, Mar 19, 2019 at 12:40 PM Timothy Froehlich
wrote:
> Been slogging through this one for a bit, would appreciate any helpful
> sugge
Been slogging through this one for a bit, would appreciate any helpful
suggestions.
I'm using mender.io's layer which includes a class that builds a full SD
card image including multiple partitions. I'm trying to turn one of those
partitions into a btrfs partition and my current error is "A
This doesn't seem to be an issue. I have multiple files with plus signs in
their names that made it back down to my local cache without requiring a
rebuild (including the whole Linux kernel)
On Tue, Feb 26, 2019 at 11:35 AM Brian Walsh wrote:
> On Mon, Feb 25, 2019 at 8:46 PM Timothy Froehl
//docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html
>
> Cheers,
> Erik
> On 26 Feb 2019, 02:45 +0100, Timothy Froehlich ,
> wrote:
>
> I've been spending a bit too long this past week trying to build up a
> reproducable build infrastructure in AWS and I've got very little
I've been spending a bit too long this past week trying to build up a
reproducable build infrastructure in AWS and I've got very little
experience with cloud infrastucture and I'm wondering if I'm going in the
wrong direction. I'm attempting to host my sstate_cache as a mirror in a
private S3
Sounds like you should be using an embedded Linux, since only including the
minimum required software will help keep your image small and power usage
down. Removing audio, video and usb, including from your kernel config,
should drastically reduce your size.
You should consider the value of a
Thank you, that looks like a very good idea.
On Thu, Feb 14, 2019 at 8:28 AM Ulf Samuelsson wrote:
> Den 2019-02-14 kl. 10:00, skrev Alexander Kanavin:
> > On Thu, 14 Feb 2019 at 01:35, Timothy Froehlich
> wrote:
> >> Hi, I've been struggling a bit with this question
y.
On Thu, Feb 14, 2019 at 1:00 AM Alexander Kanavin
wrote:
> On Thu, 14 Feb 2019 at 01:35, Timothy Froehlich
> wrote:
> > Hi, I've been struggling a bit with this question. I want to use Yocto
> to build two+ products with separate dev/prod images for each (dev
> including deb
gure out what needs to be (re)built. Some OE
> projects build the same image(s) for over 40 machines (and counting)...
>
> On 14-02-19 01:34, Timothy Froehlich wrote:
> >
> > Hi, I've been struggling a bit with this question. I want to use Yocto
> to
> > build two+ p
Hi, I've been struggling a bit with this question. I want to use Yocto to
build two+ products with separate dev/prod images for each (dev including
debug-tweaks, etc.). I've ruled out separate image recipes because my dev
builds need ENABLE_UART on my RaspberryPi and that needs to be set at the
13 matches
Mail list logo
