1. 16 Sep, 2019 1 commit
    • Ivan Melnikov's avatar
      build-vm, main.mk, pack: add recovery.tar · dc598719
      Ivan Melnikov authored
      recovery.tar needed for tavolga (mipsel).
      This commit is the result of transferring the required functionality
      from build-mr (mipsel rootfs).
      This change uses external tool to build Tavolga-compatible
      recovery.tar. This simplifies the logic and avoids having
      recovery workdir in the profile.
      After this change, m-p will require tavolga-image-tools >= 3.0.
      dc598719
  2. 19 Aug, 2019 1 commit
    • Anton Midyukov's avatar
      build-vm, pack: implement tar, tar.gz, tar.xz support for vm/* target · 1ef77caf
      Anton Midyukov authored
      build-vm ceases to be a target for building only virtual machine images.
      Now it can be used to build tarballs designed for installation on real
      machines.
      
      This commit is the result of transferring the required functionality from
      build-mr (mipsel rootfs) by Ivan Melnikov <iv@altlinux.org>.
      
      NB: mike@ strongly objected to this dilution but gave up eventually;
          the whole kernel/build-vm/tar2fs/pack mess should be split into
          distinct layers busy with their own responsibilities:
      
          1) a tarball with kernel is done without tar2fs at all
             (and no build-vm bits should be needed either, maybe
             it's worth splitting and renaming as "vm" meaning
             disk image for some armh board is grossly misleading);
      
          2) a tarball with kernel can be further (multi-)packed
             as, well, (compressed) tarball and a disk image
             (only the latter one should employ build-vm/tar2fs);
      
          3) compression should be done in pack feature style,
             preferably described once and not duplicated all over
             the profile for every single new kind of its output.
      
          In the mean time, running into this and moving no further
          starts to hurt more than it could help.
      1ef77caf
  3. 25 Jul, 2018 1 commit
    • Michael Shigorin's avatar
      rework isoboot support beyond x86 · 3c2ef1c0
      Michael Shigorin authored
      Every .iso was assumed to be bootable since the very beginning[*],
      and isoboot images were deemed to be x86 isolinux ones; this didn't
      change with basic ppc/armh support as I never ran into hardware
      that would _boot_ those ISOs, not only run the code, and it was
      only e2k isodata project that finally forced this refactoring.
      
      It's still not perfect: pack and syslinux features still end up
      somewhat interwoven, and too much places care for architecture
      the image is being built for (instead of archdep features tossing
      their appropriate bits and pieces in).
      
      Should help:
      - any-arch regarding isodata images;
      - {x86,aarch64}/efi by decoupling isoboot and isolinux;
      - ppc{,64} as introducing yaboot support will be easier now;
      - mipsel{,64} too, hopefully.
      
      * I knew of school addon images baked with mkimage-profiles-desktop
        but postponed and then neglected the whole problem for years...
      3c2ef1c0
  4. 04 Dec, 2017 1 commit
  5. 10 Jun, 2013 1 commit
    • Michael Shigorin's avatar
      README update · 5b21100b
      Michael Shigorin authored
      These have been proofread somewhat to correspond
      to the current state of affairs; a missing one
      was added for fonts feature.
      5b21100b
  6. 17 Dec, 2012 1 commit
  7. 19 Nov, 2012 1 commit
  8. 25 Jun, 2012 1 commit
    • Michael Shigorin's avatar
      initial specific VM formats support · 8a04d9b6
      Michael Shigorin authored
      Raw disk images are convenient and universal
      but there are custom formats like Qemu's qcow2
      providing additional features, e.g. copy-on-write
      or space savings.  All of this ultimately belongs
      to mkimage but in the mean time has been implemented
      here as well.
      8a04d9b6
  9. 18 Jun, 2012 1 commit
    • Michael Shigorin's avatar
      initial build-vm feature · 75f7c62b
      Michael Shigorin authored
      Yes, mkimage-profiles is now able to build VM disk images.
      So far the support is pretty basic:
      
      - a single hard drive image with a single partition/FS
      - only stock root password is configurable
      - LILO is hardwired as a bootloader
      
      The resulting images tend to boot under qemu/kvm though.
      
      Please see doc/vm.txt for the warning regarding additional
      privileges and setup required.  This was started back in
      February but I still hoped to avoid sudo/privileged helper
      (and libguestfs is almost as undistributable as can be)...
      
      Thanks:
      
      - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html
      - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen
      - led@, legion@, vitty@, aen@ for providing advice and inspiration
      75f7c62b
  10. 16 Dec, 2011 1 commit
    • Michael Shigorin's avatar
      initial isohybrid support · 6fadf7e0
      Michael Shigorin authored
      Here we go with postprocessing priorities along the way
      as ISO hybridization has to occur before implanting
      final MD5 sum (which must happen earlier than e.g. some
      external MD5SUM file generation).
      
      Unfortunately proper dependencies aren't applicable here
      (though I'd like to be proved wrong on this one).
      
      Please note that this needs propagator > 20101130-alt9
      for automatic mode to work (has also been worked around
      in gfxboot case with design-bootloader-source-6.0-alt1).
      
      Thanks rom_as@ for asking about the hybrid image status
      and helping out with testing.
      6fadf7e0
  11. 24 Nov, 2011 1 commit
    • Michael Shigorin's avatar
      added support for cpio and xz · 7e78670e
      Michael Shigorin authored
      Actually this is the proper rewrite that was looming ever since
      tgz support was introduced: there are multiple archive formats
      supported by mkimage, and there are multiple compression methods
      available as well.
      
      So the bullet got bitten yet again along with the "goal parser"
      which should be more straightforward by now.
      
      Thanks dkr@ and mithraen@ for the inspiration of this evening.
      7e78670e
  12. 19 Nov, 2011 1 commit
    • Michael Shigorin's avatar
      introduced add_feature function · 9cedefdb
      Michael Shigorin authored
      The features might get copy-pasted (or even copied-and-pruned)
      when initialized; there's an unneccessary duplication of the
      function name in the line adding it to FEATURES list, thus
      prone to being forgotten and causing some havoc later on.
      
      It was wrong in the first place but tackling this with some
      double-colon rules ran into terminality issues, and further
      tortures were considered unneccessary.
      
      The current solution isn't perfect (no completely transparent
      function name registration upon corresponding target being called)
      but at least it is an improvement...
      9cedefdb
  13. 06 Nov, 2011 1 commit
    • Michael Shigorin's avatar
      full-view docs update · ddf0c5b7
      Michael Shigorin authored
      - toplevel README received some long-needed refactoring
        + lowlevel detail moved, well, to lowlevel READMEs
      - reflected more thoroughly that m-p is not about distros anymore
      - dropped features.in/00example/README.en: it's already out-of-date
        a bit, and there's no perceived need in thorough English docs so far
      - wiki article got split into parts and somewhat rewritten, links updated
      - mv doc/{CodingStyle,style.txt}
      ddf0c5b7
  14. 04 Nov, 2011 1 commit
    • Michael Shigorin's avatar
      official {distro,ve}/* support · d5a5941f
      Michael Shigorin authored
      This is quite a large-scale change since mkimage-profiles got used to
      baking distributions over the last year, and virtual environments are
      quite different, so e.g. image.in/Makefile had to be split in two with
      the main part of it moved into features.in/iso/lib/.
      
      Short overview:
      
      - features.in/Makefile: lib/ support
        (supporting VE images requires dynamic modifications
        to image.in/Makefile before starting the build;
        the most natural way to achieve that seems to use
        features mechanism along with makefile include dir)
      
      - packaging format related part moved into features.in/pack
        (should be better prepared for diversity either)
      - features.in/iso renamed to features.in/build-distro
      - features.in/ve  renamed to features.in/build-ve
        + NB: these could not be merged as e.g. features.in/build
          due to completely different script hooks
      
      - lib/image.mk renamed to lib/build.mk
      - image, config, log postprocessing moved downstream
      - added a sort of a topping in the form of lib/sugar.mk
      - assorted style fixups (like ifeq usage)
      
      - clean.mk: reliability fix (the problem was observed by Oleg Ivanov
        and me too but finally it did get the attention quantum)
      
      - reviewed, updated and extended docs
        + QUICKSTART: should be[come] a step-by-step guide
          (thanks Leo-sp50 for prodiving feedback)
      d5a5941f