From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: Boot Breakage (systemd inclusion related?)
Date: Wed, 23 Jan 2013 15:16:52 +0000 [thread overview]
Message-ID: <50FFFEE4.2090204@communistcode.co.uk> (raw)
In-Reply-To: <50FEA6A8.8090201@intel.com>
On 22/01/13 14:48, Radu Moisan wrote:
> On 01/22/2013 03:02 PM, Jack Mitchell wrote:
>> So I attempted to build with the latest head today and my system
>> won't boot, Here is the output:
>>
>> INIT: version 2.88 booting
>> Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No
>> such file or directory
>> bootlogd.
>> Collected errors:
>> * opkg_conf_load: Could not create lock file /var/lib/opkg/lock:
>> Read-only file system.
>> INIT: Entering runlevel: 5S.d/S98run-postinsts': Re
>> Stopping Bootlog daemon: bootlogd.
>>
>> dB Linux 1.0-20130122 (none) ttyO0
>>
>> (none) login:
>>
>> Does this mean much to anyone? I assume it is do with the new init
>> manager changes but I can't be certain...
>>
>
> If you didn't enable systemd then it shouldn't interfere, sysvinit
> should work as it previously worked.
>
> Radu
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
This was fixed by explicity adding "sysvinit" to DISTRO_FEATURES.
Cheers,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
prev parent reply other threads:[~2013-01-23 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 13:02 Boot Breakage (systemd inclusion related?) Jack Mitchell
2013-01-22 14:48 ` Radu Moisan
2013-01-23 15:16 ` Jack Mitchell [this message]
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=50FFFEE4.2090204@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox