S98configure role

S98configure role

[l.bolognini]

I'm wondering what is the role of this script, placed in /etc/rcS.d.

What I guess is that, for some reasons, some packages get installed but 
not configured (then unpacked) since their postinstall script returns 
non zero value.
Here it is a small extract of rootfs_ipk.bbclass:

for 
i in ${IMAGE_ROOTFS}${libdir}/opkg/info/*.postinst; do
                
if [ -f $i ] && ! sh -e $i configure; then
                        opkg-
cl ${IPKG_ARGS} flag unpacked `basename $i .postinst`
                
fi
done

For example, in my beagleboard, I get udev unpacked because 
udev-cache can't be found in /etc/init.d (sounds strange, it's there!).

Then udev remain unpacked but the magic S98configure heals udev, 
adjusting all stuff.
But, here is my question, what about the very 
first boot? Do I have a first boot without udev-cache?
Unfortunately at 
the moment I haven't the chance to investigate and burn a SD card and 
can't go further, however I'm very interested to listen to your 
opinions.

Thank you,
bye,
Luca



Supera i limiti: raddoppia la velocità da 10 a 20 Mega!   Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 26,60 € al mese per un anno!  SCONTO DI 160 EURO!  http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw

Re: S98configure role

[Chris Larson]

On Thu, Oct 14, 2010 at 2:32 AM, l.bolognini@tiscali.it <
l.bolognini@tiscali.it> wrote:

> I'm wondering what is the role of this script, placed in /etc/rcS.d.
>
> What I guess is that, for some reasons, some packages get installed but
> not configured (then unpacked) since their postinstall script returns
> non zero value.
>

Yes, this is correct.  Some postinsts do things which can be done at image
creation time on the build machine, but not all.  Those which must *run* the
binaries in the filesystem, for example, cannot be run at build time, so
must be run at first boot time on the target.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

Re: S98configure role

[Hauser, Wolfgang (external)]

Hello,

for me the S98configure is a NO GO !
I have to provide read only images that have to be used w/o any first boot configurations.

For me there is no necessary to final install a image at first boot.

Normally all configurations are able to be done at image creation time by some scripting. 
For example, adding a user can be done by scripting, and not necessarily have to be done by adduser/addgroup.

Its up to the recipes to create packages which are installable offline totally and completely.

Handling of individual settings like serial numbers, keys ... for me should not be a matter of first boot.
It may be a matter of flashing(environment partition) or special configuration partitions.

There may be some cases, a first boot installation is necessary, but for me it is better to have an unmodified/unmodifieable image on the target.

Regards
Wolfgang

-----Ursprüngliche Nachricht-----
Von: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] Im Auftrag von Chris Larson
Gesendet: Donnerstag, 14. Oktober 2010 16:02
An: openembedded-devel@lists.openembedded.org
Betreff: Re: [oe] S98configure role

On Thu, Oct 14, 2010 at 2:32 AM, l.bolognini@tiscali.it <
l.bolognini@tiscali.it> wrote:

> I'm wondering what is the role of this script, placed in /etc/rcS.d.
>
> What I guess is that, for some reasons, some packages get installed but
> not configured (then unpacked) since their postinstall script returns
> non zero value.
>

Yes, this is correct.  Some postinsts do things which can be done at image
creation time on the build machine, but not all.  Those which must *run* the
binaries in the filesystem, for example, cannot be run at build time, so
must be run at first boot time on the target.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: S98configure role

[Chris Larson]

On Thu, Oct 14, 2010 at 7:33 AM, Hauser, Wolfgang (external) <
Wolfgang.Hauser.external@cassidian.com> wrote:

> for me the S98configure is a NO GO !
> I have to provide read only images that have to be used w/o any first boot
> configurations.
>
> For me there is no necessary to final install a image at first boot.
>
> Normally all configurations are able to be done at image creation time by
> some scripting.
> For example, adding a user can be done by scripting, and not necessarily
> have to be done by adduser/addgroup.
>
> Its up to the recipes to create packages which are installable offline
> totally and completely.
>
> Handling of individual settings like serial numbers, keys ... for me should
> not be a matter of first boot.
> It may be a matter of flashing(environment partition) or special
> configuration partitions.
>
> There may be some cases, a first boot installation is necessary, but for me
> it is better to have an unmodified/unmodifieable image on the target.
>

Then go ahead and modify your tree to do so, but don't expect OE to come
that way out of the box.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

Re: S98configure role

[Hauser, Wolfgang (external)]

Hello,

>>Then go ahead and modify your tree to do so, but don't expect OE to
come
>>that way out of the box.

I've done so, but things may be much easier if the recipes are tuned to
read only usage.

It is possibe, but the use cases may be too wide to do it in general.

Regards
Wolfgang
 

Re: S98configure role

[l.bolognini]

Thank you Chris et al. for your reply.
Even if I told you in my last 
mail I had no chanche to investigate further, I took some time to burn 
some SD and tried to understand the topic.
Well, in my build machine, 4 
packages remain unpacked:
openssh-sshd
net-snmp-server
udev
update-
modules

But, since openssh-sshd and update-modules are intentionally 
left unpacked (if test "x$D" != "x"; then exit 1 - in the .postinst 
script), it seems that for udev and net-snmp-server something goes 
wrong.
Looking in depth, I saw that in udev_141.bb, inside 
pkg_postinst_udev_append(), the usual test
if test "x$D" != "x"; then

        OPT="-r $D"
else
        OPT="-s"
fi
isn't written before 
update-rc.d command:
update-rc.d $OPT udev-cache start 12 S .
Simply, 
this piece of code is not available.
Result: update.rc.d fails in the 
build machine because OPT is empty.
Then we have not S03udev and 
S12udev-cache init links and S98configure can repair the situation but 
only from 2nd boot on.
To solve the problem I had to add that usual 
test inside pkg_postinst_udev_append() in udev_141.bb, then bitbake 
udev again.

Similar thing happens for net-snmp-server, where the 
postinst script has the same piece of code written twice, resulting in 
an error and then in the flag unpacked for the package.
Commenting out 
the first occurrance I got good results.

Here net-snmp configuration 
by means of S98configure is less dramatical because net-snmp agent 
starts after S98configure and then everything is fine also in 1st boot.


I hope this investigation could help someone involved in the same 
problems,
bye,
Luca

----Messaggio originale----
Da: clarson@kergoth.
com
Data: 14/10/2010 16.01
A: <openembedded-devel@lists.openembedded.
org>
Ogg: Re: [oe] S98configure role

On Thu, Oct 14, 2010 at 2:32 AM, 
l.bolognini@tiscali.it <
l.bolognini@tiscali.it> wrote:

> I'm 
wondering what is the role of this script, placed in /etc/rcS.d.
>
> 
What I guess is that, for some reasons, some packages get installed but

> not configured (then unpacked) since their postinstall script returns

> non zero value.
>

Yes, this is correct.  Some postinsts do things 
which can be done at image
creation time on the build machine, but not 
all.  Those which must *run* the
binaries in the filesystem, for 
example, cannot be run at build time, so
must be run at first boot time 
on the target.
-- 
Christopher Larson
clarson at kergoth dot com

Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior 
Software Engineer, Mentor Graphics

_______________________________________________
Openembedded-devel 
mailing list
Openembedded-devel@lists.openembedded.org
http://lists.
linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel





Supera i limiti: raddoppia la velocità da 10 a 20 Mega!   Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 26,60 € al mese per un anno!  SCONTO DI 160 EURO!  http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw