Re: [Ltib] [LTIB] Modifying rc.local

[Peter Barada]

On 03/20/2012 03:28 AM, Stuart Hughes wrote:
> Hi Peter,
>
> The docs could do with maintenance, but as I've said before at the 
> moment I have almost zero time available.
I'm not sure of the syntax of doc/LtibFaq, but here's a stab at
capturing this information:

*** LtibFaq.~1.5.~    2009-06-09 13:05:05.000000000 -0400
--- LtibFaq    2012-03-20 10:31:50.000017002 -0400
***************
*** 1454,1459 ****
--- 1454,1469 ----
     1. Add 'named' into the all_services_r= line (this is the reverse
of the previous line, for shutdown).
     1. Add '$named' into cfg_services and cfg_services_r.
 
+ ---++ How to find out which package populates a file in rootfs
+
+ Once you're rootfs is fully populated with all the packages in your
build (if you're not sure execute):
+ <verbatim>
+ ./ltib -e
+ </verbatim>
+ You can find out which package installs a file (in this case
"/etc/rc.d/rc.local") in the rootfs by:
+ <verbatim>
+ /opt/ltib/usr/bin/rpm --root `pwd`/rootfs --dbpath /var/lib/rpm/ -qf
/etc/rc.d/rc.local
+ </verbatim>
 
  ---+ Source code
 

> Also a better way to override rc.local is to create a merge directory 
> under your config/platform/_target_ directory, e.g
>
> config/platform/_target_/merge/etc/rc.d/rc.local  (there are some 
> examples on other platforms such as mpc8349itx).
>
> There's a note about this in the FAQ under:
>
> ---+ Root Filesystems
> ---++ Can I add files to the target root file system without creating a 
> package

True, but in the past you stated "merge directories are best avoided if
you can" (e.g.
http://lists.gnu.org/archive/html/ltib/2009-12/msg00068.html) so I'm a
bit confused.  In my case I've created my own skell.spec in the platform
directory and patched it as need be to add files under /etc into the
rootfs (at least those files that don't look to have a logical home)...

> Regards, Stuart
>
>
> On 03/19/2012 11:26 PM, Peter Barada wrote:
>> On 03/19/2012 07:14 PM, Douglas Peterson wrote:
>>> That shows two packages:
>>> skell-1.19-3
>>> sysconfig-1.2-2
>>>
>>> And sure enough, sysconfig.spec writes the rogue rc.local file.
>>>
>>> So it appears that if we want to modify rc.local, we need to use our own 
>>> sysconfig.spec.
>>>
>>> Thanks Peter,
>> Anytime.
>>
>> Stuart, would this be useful to put into the FAQ somewhere?
>>


-- 
Peter Barada
address@hidden