On Tue, Jun 25, 2019 at 09:25:13AM -0400, Larry Brown wrote:
I wonder, if there are best practices, how to protect the data from getting
corrupted (intentionally by an attacker or by accident through ... flash
corruption or whatever).
Ideally your hardware should have some sort of hw-based
On Mon, Jun 17, 2019 at 05:25:56PM +0200, Matthias Schoepfer wrote:
Is there a smart, recommended way to deal with device specific data (i.e.
serial number, credentials for backend access, you name it), that is specific
for *one* device, and hence does not belong into the rootfs. I know, that
On Tue, Jun 04, 2019 at 11:34:15PM +0200, Zoran
Stojsavljevic wrote:
(I did not find it anywhere in the manuals,
maybe I missed the paragraph - please, advice
where it is?).
This is where I found it previously:
On Mon, Jun 03, 2019 at 07:38:47PM +0200, Zoran Stojsavljevic wrote:
Still. I expected to see the following on the
target (my BBB): /etc/init.d/networking script,
I would have a look at the values of
DISTRO_FEATURES_BACKFILL_CONSIDERED as well as
VIRTUAL-RUNTIME_initscripts.
My
On Mon, Jun 03, 2019 at 04:30:33PM +0100, Burton, Ross wrote:
The variable is
DISTRO_FEATURES_BACKFILL_CONSIDERED, in case
that wasn't a typo when writing the mail.
It wasn't a typo, and that was exactly the
problem. Well spotted, everything in the world
makes sense again :-)
Which startup system do you use (sysVinit or
systemd)? You can take a look at
poky/meta/classed/update-rc.d.bbclass which
checks various parameters and try to debug it
(by adding some printouts). By my guess is that
some misconfiguration between systemd/sysvinit
must cause this issue.
Which startup system do you use (sysVinit or
systemd)? You can take a look at
poky/meta/classed/update-rc.d.bbclass which
checks various parameters and try to debug it
(by adding some printouts). By my guess is that
some misconfiguration between systemd/sysvinit
must cause this issue.
I'm
I would check run.do_rootfs and check it maybe
there will be some more info.
I checked it based on your suggestion,
unfortunately found no relevant info.
Do you have some custom extension for hostapd?
No, just the standard package.
- Morné
--
Hi
I created a new custom distribution and
everything seems to work fine until the do_rootfs
task is executed. It fails specifically when
trying to install the hostapd package, with the
error below (snippet from log.do_rootfs):
Running scriptlet: hostapd-2.6-r0.aarch64
usage: update-rc.d
