From: Ross Burton <ross.burton@intel.com>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Initramfs and systemd problems
Date: Tue, 12 Feb 2013 09:35:36 +0000 [thread overview]
Message-ID: <F3FDA2B8A266452C8CB34AFC4B256702@intel.com> (raw)
In-Reply-To: <511A0810.4080305@linux.intel.com>
On Tuesday, 12 February 2013 at 09:14, Jukka Rissanen wrote:
> I am building a small network appliance for tethering purposes.
> I do not need graphics so I removed X support, also added
> systemd from meta-ivi and upgraded connman into latest
> 1.11 version, and also did some minor tweaks here and there.
>
> In beagleboard, my setup works just fine.
> In Intel NUC device, the system refuses to boot properly.
> The reason is the init-live.sh (http://init-live.sh) script in initramfs image,
> it expects the USB stick to be present in /media/xxx directory.
>
> Because the base system uses systemd, the initramfs is
> also using systemd but there is some things missing and
> system will not automount the USB stick into /media.
>
> Is there any possibility to avoid using systemd in initramfs
> i.e., use the udev package only, or is the only option to
> tweak systemd setup in initramfs? Or any other suggestion
> how to fix this?
I'd noticed that systemd's udev is failing to live-boot too in oe-core master (which now has integrated systemd).
I don't think its possible to build a second udev for the initramfs, and this is clearly a bug so we should figure out why it doesn't work. Do you have any hints in your debugging as to what is broken?
Ross
next prev parent reply other threads:[~2013-02-12 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 9:14 Initramfs and systemd problems Jukka Rissanen
2013-02-12 9:35 ` Ross Burton [this message]
2013-02-12 10:14 ` Jukka Rissanen
2013-02-12 10:30 ` Burton, Ross
2013-02-12 11:50 ` Ross Burton
2013-02-12 13:17 ` Jukka Rissanen
2013-02-12 14:06 ` Ross Burton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F3FDA2B8A266452C8CB34AFC4B256702@intel.com \
--to=ross.burton@intel.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.