IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
kernel-modules-igb not available for branch >= p7
kernel module e1000e in p10 is packed according to the blacklist
scheme, this blacklist is applied to all the kernels and the
internal e1000e from un-def-5.15 does not work as a result.
Reported by boyarsh@
Now, when CONFIG_USB=y, to disable usb autosuspend, must pass this
parameter when bootloading the kernel.
Package disable-usb-autosuspend has become useless.
Kernel flavours differ on secondary arches (and there's a bunch
of platform-specific kernels for ARM systems), so let's provide
some more flexible scheme than hardwiring un-def into images.
This might be further enhanced to e.g. set KFLAVOURS to
$$(KFLAVOURS_LATEST)) with it being preset to un-def
where available so rpi images could set it to rpi-un,
and still get reasonable starterkits for free.
The corresponding commit in RELENG-e2k-p9-starterkits
private branch just tore un-def apart => unmergeable.
VM_INITRDFEATURES qemu not allowed for e2k only. This feature
added modules optionaly.
VM_INITRDFEATURES usb allowed for all arches, but the presence of all
modules is required. Therefore, for all arches all usb modules are
optionally added.
The entry in /etc/fstab about the mount parameters of the root
partition needs to be done not only for builds with u-boot.
But, if the record already exists, then it will not be added.
The file system type is set by the variable VM_FSTYPE.
Since packet sorting is enabled by default, then
the order in KFLAVORS has ceased to matter.
Kernels are always installed in alphabetical order.
Therefore, it makes no sense to sort by buildtime.
See-also: https://bugzilla.altlinux.org/show_bug.cgi?id=30806
Also fixed my typo. When creating a symlink, the variable
$kver was used, i.e. the entire list of kernels, not the
last value $KVER of the list.
This one has filled up the entire 8 Mb tmpfs
while running inside installer stage1 on a
124-drive system (configured as JBOD).
Reported-by: http://norsi-trans.ru
