- 11 Jul, 2015 1 commit
-
-
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.
-
- 20 Apr, 2015 5 commits
-
-
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.
-
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.
-
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.
-
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.
-
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.
-
- 29 Mar, 2015 5 commits
-
-
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).
-
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.
-
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.
-
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.
-
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?).
-
- 09 Mar, 2015 1 commit
-
-
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.
-
- 19 Sep, 2014 2 commits
-
-
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.
-
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.
-
- 27 Aug, 2014 1 commit
-
-
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).
-
- 18 Aug, 2014 1 commit
-
-
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".
-
- 12 Aug, 2014 1 commit
-
-
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.
-
- 17 Mar, 2014 1 commit
-
-
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.
-
- 05 Mar, 2014 3 commits
-
-
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.
-
Michael Shigorin authored
sub/% has moved from lib/distro.mk to lib/sugar.mk since rootfs introduction with commit g67adab49.
-
Michael Shigorin authored
Its name might still change through 1.1.x series ("userfs"?) but things like this should be mentioned at least -- or superfluous references to neighbouring entities should be removed.
-
- 11 Jan, 2014 1 commit
-
-
Evgeny Sinelnikov authored
-
- 12 Aug, 2013 1 commit
-
-
Michael Pozhidaev authored
Minor fix: /boot directory is not cleaned for livecd if there are homeros-install or luwrain-install files (in addition to live-install and livecd-install being already checked).
-
- 17 Jun, 2013 2 commits
-
-
Michael Shigorin authored
This is ARM-specific (more specifically, Marvell ArmadaXP-specific for me right now) but doesn't hurt if the module is absent.
-
Michael Shigorin authored
This subprofile is akin to THE_* variables family: the configuration bits and script hooks sitting there influence whatever chroot is declared to be the user facing one in the end, whether it comes from vm image or live subprofile. The services feature ought to be a changeset of its own which would be based on rootfs and become the base for ve/vm changes but I chose to just do it atomically; some pre-existing duplicates are pruned now.
-
- 10 Jun, 2013 1 commit
-
-
Michael Shigorin authored
These have been proofread somewhat to correspond to the current state of affairs; a missing one was added for fonts feature.
-
- 25 Mar, 2013 1 commit
-
-
Michael Shigorin authored
There's a need for a separate boot target since persistent storage is way slower than tmpfs indeed; usbflash has a tendency for huge performance drops given simultaneous writes in addition to reads which are the bottleneck already. make-initrd-propagator 0.18 introduced ext4 rw slice, so the corresponding kernel module needs to be included into stage1; see also #28289. NB: not available on x86_64-efi (or hybrid GPT to be strict) due to fragility of the hack being made: parted(8) panics upon seeing that, and good ol' fdisk is unable to treat it. NB: use/live/rw use/rescue/rx use/syslinux/ui/gfxboot are unlikely to play very nice together due to the latter's magic l10n: "session" label is taken by live_rw config snippet and *is* translated in design-bootloader-source; OTOH "rescue_session" is *not*.
-
- 05 Mar, 2013 1 commit
-
-
Michael Shigorin authored
The issue is that r8169 is rather broken nowadays while r8168 tends to work on the same hardware; see also #28473. Thanks zerg@ for having hinted that it's stage1 modules, not the root squashfs.
-
- 06 Jan, 2013 1 commit
-
-
Denis Smirnov authored
-
- 17 Dec, 2012 2 commits
-
-
Michael Shigorin authored
I will test more in kvm I will test more in kvm I will test more in kvm ...
-
Michael Shigorin authored
The initial approach required some quite involved postprocessing as described in http://www.altlinux.org/UEFI#HOWTO; after having ironed out the kinks so that initial EFI support could be merged into mkimage proper we're better off just using it, eh?
-
- 09 Nov, 2012 1 commit
-
-
Michael Shigorin authored
The newer kernels have versioned NFS support code moved into a few separate modules with nice self-explanatory messages reading "Protocol not supported" if one has managed to overlook this; thanks boyarsh@ for heads-up (based on f545923271f9d1938d1887632ab4697c4c009039 m-p-d).
-
- 05 Nov, 2012 1 commit
-
-
Michael Shigorin authored
It was actually an experiment leftover and spoils toplevel completion so let's drop that one, just as mentioned by torabora@.
-
- 31 Oct, 2012 1 commit
-
-
Mike Radyuk authored
-
- 10 Oct, 2012 1 commit
-
-
Michael Shigorin authored
The issue actually hit image.in/Makefile: "metadata" target in features.in/metadata/lib/50-metadata.mk wasn't reached even if features.in/build-distro/lib/90-build-distro.mk would ACK that the "whatever" actions included "metadata"; thus Metadata/pkg-groups.tar wasn't created and the installer silently failed to install the .base system. Let's armour the rest of the cases where the order of inclusion might be important as well.
-
- 03 Sep, 2012 1 commit
-
-
Michael Shigorin authored
hsh-initroot leaves the chroot's root directory permissions as 1775 while these should really be 755 at most; let's fix it (important for both VE and VM images, useful for rescue/livecd ones as well -- especially those with an installer onboard).
-
- 11 Aug, 2012 1 commit
-
-
Michael Shigorin authored
That sub/stage2/install2 was somewhat clumsy actually as it looked like a hierarchical thing while being a substitution thing: generic stage2 would get put in place renamed as install2. This could only get worse with hierarchical features which have already been both requested and considered for quite a time, and "stage2 at install2" reads much more naturally.
-
- 09 Aug, 2012 1 commit
-
-
Michael Shigorin authored
There were heaps of "if type -t git" there already; it wasn't an unintentional mishap but rather a moderate copy-paste to get the use cases, and now these seem to have essentially settled. So time to scrap some dups. NB: the scripts in the generated profile can't rely on the contents of the metaprofile (these need to be able to work in standalone case either), so a bit of crap still lurks there.
-
- 14 Jun, 2012 1 commit
-
-
Michael Shigorin authored
An initial draft of it was done half a year ago but several tricky thingies had kept the code from showing up as it was rather brittle and incomplete. This implementation involves quite a few changes all over the place but finally works good enough for live and installer images. Please pay attention to the versions of these packages: - installer-feature-setup-plymouth (0.3.2-alt1+) - branding-altlinux-sisyphus (20110706-alt2+ if used) - plymouth (0.8.3-alt20.git20110406+) See also: - http://www.altlinux.org/Branding - http://www.altlinux.org/Plymouth
-
- 21 May, 2012 1 commit
-
-
Michael Shigorin authored
Whoops, forgot to feed placeholders for git to grok the empty directories that are needed later...
-