You need to sign in or sign up before continuing.
  1. 12 Apr, 2021 1 commit
  2. 05 Apr, 2021 1 commit
  3. 23 Nov, 2020 1 commit
    • Anton Midyukov's avatar
      stage1: Also add STAGE1_KMODULES · e447b4c7
      Anton Midyukov authored
      It is very strange that earlier in STAGE1 added kernel modules from
      a variable STAGE1_KMODULES_REGEXP only.
      This commit makes the drm feature work properly.
      e447b4c7
  4. 26 Sep, 2020 1 commit
    • Michael Shigorin's avatar
      stage2: include targets.mk once · 31f280c0
      Michael Shigorin authored
      Partially reverts commit e8f63357
      which has added an overlooked second `include targets.mk' which
      began spamming build.log immediately:
      
        /usr/share/mkimage/targets.mk:23: warning:
          overriding recipe for target `__profile_internal_rule'
        /usr/share/mkimage/targets.mk:23: warning:
          ignoring old recipe for target `__profile_internal_rule'
      
      *sigh*
      31f280c0
  5. 17 Aug, 2020 1 commit
  6. 22 May, 2020 1 commit
  7. 16 Sep, 2019 1 commit
  8. 05 Nov, 2018 1 commit
  9. 06 Aug, 2018 1 commit
  10. 11 Jun, 2018 1 commit
  11. 23 May, 2018 1 commit
  12. 15 Feb, 2018 1 commit
  13. 09 Jun, 2017 1 commit
    • Michael Shigorin's avatar
      docs update · 31ecda72
      Michael Shigorin authored
      Another minor facelift:
      - s/ALT Linux/ALT/gc (where applicable);
      - s/7.0/8.0/g;
      - 2017;
      - e2k;
      - links.
      31ecda72
  14. 27 Jun, 2016 1 commit
  15. 23 May, 2016 2 commits
    • Konstantin A. Lepikhov's avatar
      sub.in/stage2: Added copy-tree to stage2 · e8f63357
      Konstantin A. Lepikhov authored
      stage2 only allows to run certain scripts and install packages, but
      sometimes one need just to copy something to stage2 (like stage1 does).
      
      How to use:
      
      put files under ./files directory with the same structure as on
      resulting image.
      e8f63357
    • Konstantin A. Lepikhov's avatar
      Experimental overlayfs support · 9f72780d
      Konstantin A. Lepikhov authored
      If aufs not available/broken we could try to use overlayfs.
      NB: changes below doesn't work without modified make-initrd-propagator!
      9f72780d
  16. 01 Apr, 2016 1 commit
  17. 12 Jan, 2016 1 commit
    • Michael Shigorin's avatar
      stage2: tweak 99-cleanup-boot for efficiency · 37e77285
      Michael Shigorin authored
      Thanks glebfm@ for noticing that Simply (an m-p-d product)
      takes no kernel inside squashfs but relies on livecd-install's
      50-restore-kernel.sh hook to copy the kernel from iso9660
      and regenerate initrd (which is a must anyways but requires
      System.map to be still around).
      
      This saves about 3 Mb in ISO size for a LiveCD using
      kernel-image-std-def-4.1.15-alt1.x86_64.rpm.
      37e77285
  18. 04 Dec, 2015 1 commit
  19. 16 Nov, 2015 1 commit
    • Michael Shigorin's avatar
      image.in, stage2: reworked TCB fixup hook · 5427f3af
      Michael Shigorin authored
      The issue at hand is that:
      
      /etc/tcb/USER/shadow gets USER:auth ownership (OK);
      /etc/tcb/USER/shadow- backup file is root:root (broken);
      /etc/tcb/USER/shadow.lock file is also root:root (broken).
      
      This is observed for all pseudousers created by package installation
      process within working chroots as well as for users created by deflogin
      feature; the problem is that e.g. echo USER:PASS | chpasswd will break.
      
      Looks like the cuplrit might be fakeroot/faked.
      5427f3af
  20. 11 Jul, 2015 1 commit
    • Michael Shigorin's avatar
      stage2: no kernels no go · a277a6cc
      Michael Shigorin authored
      The flexible KFLAVOURS handling has a downside:
      if no packages match the regexp it's silently OK
      until too late, and the error is incomprehensible.
      Let's fix the latter at least.
      a277a6cc
  21. 20 Apr, 2015 5 commits
    • Michael Shigorin's avatar
      stage1: added ext4.ko to modules · f9f1437b
      Michael Shigorin authored
      It's been found out that live_rw isn't going to work
      without ext4 module being available; let's ensure that.
      f9f1437b
    • Michael Shigorin's avatar
      a few modules.d test drives · 559f80ad
      Michael Shigorin authored
      These are aimed to test the modules.d/ and auto-pickup
      implementation as well as to present an example.
      
      At least 50-net might change (or just get renamed to avoid
      auto-pickup) some day as the "net" feature's meaning is
      to provide networking upon bootup and these modules are
      only needed within stage1 if we're going to netboot;
      and that's quite different thing.
      
      armh-cubox bits are prone to get renamed/generalized too
      since e.g. ArmadaXP based server images are going to need
      this as well.
      559f80ad
    • Michael Shigorin's avatar
      stage2: added broken-down module lists · e139a5e0
      Michael Shigorin authored
      These were produced off the single sub.in/stage1/modules
      file using this scriptlet to prefix/annotate the names:
      
        grep '\.ko$' modules \
        | grep -v / \
        | while read m; do \
        	echo "$(find /lib/modules/$(uname -r)/kernel/{drivers,fs} \
      		-name "$m" -printf %P $m $(modinfo -d "${m%.ko}" 2>&1)"; \
          done
      
      ...with subsequent sorting and manual separation.
      
      This is meant to be the second stage in monolithic modules
      file split, so the lists themselves are largely unmolested
      otherwise.  The plan is to further split those into prefix-
      and module-specific ones.
      
      Add a note clarifying 10-stage2's status, by the way.
      e139a5e0
    • Michael Shigorin's avatar
      stage1, stage2: moved propagator modules file · 1ee01498
      Michael Shigorin authored
      What was a static sub.in/stage1/modules (and the only one)
      is now features.in/stage2/stage1/modules.d/10-stage2
      (basically a compatibility file that might go some day).
      
      It will be auto-picked as its name corresponds to the
      NN-SUFFIX pattern specified in stage1 subprofile now
      with $(FEATURES) going into default STAGE1_MODLISTS.
      1ee01498
    • Michael Shigorin's avatar
      stage1, stage2: initial modlists support · a36d0236
      Michael Shigorin authored
      stage1's got prepare-modules target collecting
      modules file snippets all over stage1/modules.d/
      subdirectories within individual features.
      
      stage2 now adds names of all the features going into
      a particular image as snippet file suffix list so that
      individual features don't have to register themselves
      twice (as a feature and as a propagator modules.d
      snippet carrier).
      
      This is going to allow both "uncommon" modules getting
      included with no problem (sin@ has wanted cifs ones
      for quite some time, for example, and some want e.g.
      infiniband modules) *and* to reduce the actual list
      below the common mark as well (which is the case with
      live-privacy image, for one).
      
      And stage1 memory consumption does matter in some cases
      as it's highly critical with no chance to use swap yet.
      a36d0236
  22. 29 Mar, 2015 5 commits
    • Michael Shigorin's avatar
      stage1: drop dummy.ko · 08d802ab
      Michael Shigorin authored
      Looks like it's been dumped in along with the rest but not
      actually used in {make-initrd-,}propagator; the problem with it
      is that snd-dummy.ko matches and pulls a bunch of unrelated
      modules where these don't belong (grep -w wouldn't match
      snd_dummy.ko though).
      08d802ab
    • Michael Shigorin's avatar
      stage1: re-add a few modules · bc0f8a45
      Michael Shigorin authored
      These can be found in (semi-)supported branches still:
      
      - loop.ko:
        + 3.0.101-std-def-alt0.M60P.1
        + 3.4.96-led-ws-alt0.M70P.1
      - aufs.ko:
        + 2.6.32-el-smp-alt31
        + 3.4.96-led-ws-alt0.M70P.1
      
      ehci_marvell.ko isn't found in contemporary sisyphus/armh
      kernels but let's purge it later during archdep rewrite.
      
      NB: libusual.ko has been renamed to usb-libusual.ko as of p6
          (not to be found in p7 anymore), and nls_base.ko was in
          2.6.32 kernels as of p6 but not there in p7; purge these
          somewhere down the road.
      bc0f8a45
    • Michael Shigorin's avatar
      stage1: purge nonexistent modules · 09a9255f
      Michael Shigorin authored
      This file has been floating around for quite some time,
      and some of its contents are pure bit rot by now...
      
      Drop the modules that don't exist as of 3.19.2-un-def-alt1
      upon manual diff examination.
      09a9255f
    • Michael Shigorin's avatar
      stage1: fix module name · 71ad34a9
      Michael Shigorin authored
      It wasn't sdhci_pci.ko back in 2.6.32 actually and it's
      sdhci-pci.ko; so grep used by mkmodpack won't pick it up.
      71ad34a9
    • Michael Shigorin's avatar
      stage1: add USB3 support · f112a335
      Michael Shigorin authored
      This has been missing for *so* long somehow, and adding some 200k
      of modules for fast hardware that's widely available by now
      looks like a deal.
      
      Added USB Attached SCSI module just in case (or rather for weak
      crc_t10dif symbols?).
      f112a335
  23. 09 Mar, 2015 1 commit
    • Michael Shigorin's avatar
      stage2, install2: oops, narrow the cleanup back · 7cb477c3
      Michael Shigorin authored
      The former install2-only "bloated binary" purge script
      happened to hit stage2 (which is a lot more than just
      install2); a kind of safety net has been stuck into it
      to guard installable LiveCDs against this particular
      cleanup but seems it was not enought for ildar@ who
      reported this problem almost three years after it was
      introduced.
      
      This change re-places the script back into install2
      section; the binaries in question amount for ca. 8 Mb
      (except openssl ildar@ asked about); if these are deemed
      unneccessary within any other stage2-based subprofiles,
      please step up with details.
      7cb477c3
  24. 19 Sep, 2014 2 commits
    • Michael Shigorin's avatar
      fix kpackages() API · 6f452182
      Michael Shigorin authored
      This function's got its argument order chosen for "aesthetical"
      reason of $(2) following $(1) in the macros but the logical order
      is exactly the opposite: we care for kernel flavour much more than
      for module set (which is dependent upon it).
      
      So while silent dropout of kernel-image if KFLAVOURS is set
      but KMODULES is empty could be fixed by testing for $(2) only,
      it looks like a good time to fix this discrepancy altogether.
      6f452182
    • Michael Shigorin's avatar
      stage1: fix for non-propagator stage2 · 730e791f
      Michael Shigorin authored
      It's been a given that any stage2 is propagator-based
      but that's not neccessarily so; the "run X as PID 1"
      sort of contest has sparkled interest in some others.
      730e791f
  25. 27 Aug, 2014 1 commit
    • Michael Shigorin's avatar
      rootfs: README update · d804203b
      Michael Shigorin authored
      It should state clearly both the positive and negative examples
      of rootfs concept use (its name is not consiceenough unfortunately,
      and I haven't come up with a better one yet).
      d804203b
  26. 18 Aug, 2014 1 commit
    • Michael Shigorin's avatar
      stage1: READMEdability fix · 5b069739
      Michael Shigorin authored
      Kernel modules come as both *.ko and kernel-modules-*.rpm
      and it wasn't clear enough whether to mention "ahci" or "v4l".
      5b069739
  27. 12 Aug, 2014 1 commit
    • Michael Shigorin's avatar
      main, metadata: README update · 3171d693
      Michael Shigorin authored
      There's not much sense in overduplication of documentation
      (tends to get stale faster then), still it's not good to
      just refer to the code as the PDF/HTML book is less useful
      then; maybe drifting towards "recommended" bits with more
      "advanced" things being impleentation-defined is better.
      3171d693
  28. 17 Mar, 2014 1 commit
    • Michael Shigorin's avatar
      kernel, stage1: don't provide r8168.ko by default · 49b6291a
      Michael Shigorin authored
      It conflicts with r8169.ko inobviously.
      
      The whole mess looks like this:
      - r8169.ko doesn't work for all of Realtek 8111/8168/8169 mutations
      - r8168.ko works with some of the chips r8169.ko doesn't
      - r8168.ko also works with many chips r8169.ko works with
      - r8169.ko is provided by kernel-image package (thus default)
      - r8168.ko is provided by kernel-modules-r8168 package (optional)
      - kernel-modules-r8168 package requires r8168-blacklist package
      - r8168-blacklist package is a one-liner that blacklists r8169.ko
      - STAGE1_KMODULES wouldn't include r8168 (std-def) or rtl8168 (led-ws)
      - sub.in/stage1/modules would mention r8168.ko (m-p-d: r8169.ko)
      
      So a LiveCD built with use/kernel/net might work with RTL8111/8110
      just fine when booted live but fail to automatically load the module
      when installed onto hard drive; manual modprobe r8169 would work though.
      NB: some of the chips (those available to me) would work just fine
      both ways -- this has contributed to fixing this *that* late.
      
      Bottom line:
      
        do not install backup/kludge drivers overriding main ones by default!
      
      Thanks sem@ for providing the crucial hint.
      49b6291a
  29. 05 Mar, 2014 2 commits
    • Michael Shigorin's avatar
      documentation: use paths relative to toplevel dir · 3f547e25
      Michael Shigorin authored
      This change is done to reduce ambiguity in some cases;
      the previous intention has been to ease navigation when
      staying in a particular directory, now it's been changed
      in favour of convenient toplevel `git grep' in fact.
      
      Both variants have their pros and cons, I just find myself
      leaning to this one by now hence the commit.  Feel free to
      provide constructive criticism :)
      
      Some path-related bitrot has also been fixed while at that.
      3f547e25
    • Michael Shigorin's avatar
      sub.in/README: bitrot fixup · 4ea06fed
      Michael Shigorin authored
      sub/% has moved from lib/distro.mk to lib/sugar.mk
      since rootfs introduction with commit g67adab49.
      4ea06fed