Boot Breakage (systemd inclusion related?)

Boot Breakage (systemd inclusion related?)

[Jack Mitchell]

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

--

Re: Boot Breakage (systemd inclusion related?)

[Radu Moisan]

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

Re: Boot Breakage (systemd inclusion related?)

[Jack Mitchell]

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

--