* Boot Breakage (systemd inclusion related?)
@ 2013-01-22 13:02 Jack Mitchell
2013-01-22 14:48 ` Radu Moisan
0 siblings, 1 reply; 3+ messages in thread
From: Jack Mitchell @ 2013-01-22 13:02 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
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...
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Boot Breakage (systemd inclusion related?)
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
0 siblings, 1 reply; 3+ messages in thread
From: Radu Moisan @ 2013-01-22 14:48 UTC (permalink / raw)
To: openembedded-core
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Boot Breakage (systemd inclusion related?)
2013-01-22 14:48 ` Radu Moisan
@ 2013-01-23 15:16 ` Jack Mitchell
0 siblings, 0 replies; 3+ messages in thread
From: Jack Mitchell @ 2013-01-23 15:16 UTC (permalink / raw)
To: openembedded-core
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
--
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-01-23 15:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox