Roman, The point of the bootstrap environment of mic (mic-bootstrap) is we need to keep an unified mic runtime and tools set. To add more tools into it, we need to create the package in tizen.org infrastructure and include it in mic-bootstrap.spec.
As my understanding, it seems you can use a wrapper tools of MIC, to manipulate the output images after MIC successful executing. And, yes, the %traceback secsion will be be handled by MIC code. As Geoffroy mentioned, maybe you can find more answers from the code of liveusb/livecd format support. thanks - jf.ding On Fri, May 09, 2014 at 07:35:49PM +0900, Roman Peniaev wrote: > Hi Geoffroy. > > To be fair enough I have to say that mksquashfs is not only the target. > I need to execute any command I want in the future against install_root > from *.ks script. > So from now on I have understanding that (please, correct me if I am wrong): > > 1. to execute something special from %post section inside *.ks file I have > to install this 'something' into bootstrap. > a) I can extend mic-bootstrap adding 'BuildRequires: XXX' to > mic-bootstrap.spec and rebuild the mic-bootstrap rpm > b) I can extend the line packages=mic-bootstrap-x86-arm in > /etc/mic/mic.conf configuration and install XXX rpm along with > mic-bootstrap. > > 2. there is no any chance to execute 'something' from *.ks against > install_root after all umounts have been done. > (%post --nochroot is executed against directory which contains many > bind and other mounts) > that's bad, because it is insane to tar/mksquasfs/whatever with /proc, > /sys or even /home. > > 3. there is one more section which is called %traceback, but according to > my shallow understanding it is not used at all. > what is the real purpose of this %traceback ? probably somebody knows. > > -- > Roman > > > On Fri, May 2, 2014 at 6:38 PM, VanCutsem, Geoffroy < > [email protected]> wrote: > > > Hi Roman, > > > > I _believe_ that such squashfs image is generated when you choose the > > livecd or liveusb image format. I can see three potential options based on > > my limited understanding of how mic works: > > - Extract the squashfs from the liveusb/livecd image created > > - Use the 'fs image' option and then manually run mksquashfs on it > > - Cook up your own 'squashfs' subcommand to be passed to 'mic create', you > > should be able to draw inspiration from the existing ones (in > > /usr/lib/python2.7/site-packages/mic/imager/) > > > > HTH, > > Geoffroy > > > > -----Original Message----- > > From: General [mailto:[email protected]] On Behalf Of Roman > > Peniaev > > Sent: Friday, May 02, 2014 6:29 AM > > To: [email protected] > > Subject: [Tizen General] mic: how to execute specific tool in %post > > --nochroot section? > > > > Hello. > > > > I have to make squashfs image from install_root folder. > > The first idea was to modify mic/imager/fs.py and to add some param for > > that, but then I decided just to add some specific %post --nochroot section > > to .ks. > > > > But according to my understanding %post --nochroot script executes inside > > bootstrap sandbox, thus any of the specific tool is not being seen. > > > > So, the question is: what is the good way to execute tool which does not > > exist in bootstrap, but exists on the host? > > > > I even can't follow my first plan: add specific param to fs.py, because > > the whole mic is chrooted to bootstrap folder, so again mksquashfs tool > > will be invisible. > > > > Please, advise some proper way. > > > > -- > > Roman > > _______________________________________________ > > General mailing list > > [email protected] > > https://lists.tizen.org/listinfo/general > > Intel Corporation NV/SA > > Kings Square, Veldkant 31 > > 2550 Kontich > > RPM (Bruxelles) 0415.497.718. > > Citibank, Brussels, account 570/1031255/09 > > > > This e-mail and any attachments may contain confidential material for the > > sole use of the intended recipient(s). Any review or distribution by others > > is strictly prohibited. If you are not the intended recipient, please > > contact the sender and delete all copies. > > > > > _______________________________________________ > General mailing list > [email protected] > https://lists.tizen.org/listinfo/general _______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
