Package Details: linux-ck-headers 6.11.10-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: Headers and scripts for building modules for Linux-ck kernel
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 458
Popularity: 0.094674
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-26 13:15 (UTC)

Latest Comments

« First ‹ Previous 1 .. 256 257 258 259 260 261 262 263 264 265 266 .. 308 Next › Last »

fincan commented on 2012-06-02 05:48 (UTC)

ck patches are ready...

graysky commented on 2012-05-30 18:31 (UTC)

Thx... Now we just need bfs.

skydrome commented on 2012-05-30 17:36 (UTC)

http://algo.ing.unimo.it/people/paolo/disk_sched/patches/3.4.0-v3r4

<deleted-account> commented on 2012-05-27 15:58 (UTC)

Yup, this patch works fine for me. Thanks for taking this forward - that is very nice of you.

graysky commented on 2012-05-26 15:50 (UTC)

Also - https://bugs.archlinux.org/task/30028

graysky commented on 2012-05-26 15:34 (UTC)

I actually do not like DKMS... can you verify that the patch you supplied produces the desired results? I am glad to add it if so (code is dependent on that pkg being installed).

<deleted-account> commented on 2012-05-26 13:00 (UTC)

Can you kindly include the below patch to linux-ck.install so that DKMS autoinstall service runs after each kernel install? I prefer this method rather than invoking DKMS service on each system boot. --- linux-ck.install.old 2012-05-26 18:23:07.240130815 +0530 +++ linux-ck.install.new 2012-05-26 18:26:36.502330478 +0530 @@ -8,6 +8,13 @@ echo ">>> Generating initial ramdisk, using mkinitcpio. Please wait..." mkinitcpio -p linux${KERNEL_NAME} + pacman -Q dkms &>/dev/null + hasdkms=$? + if [ $hasdkms -eq 0 ]; then + echo ">>> Running the DKMS autoinstall service..." + dkms autoinstall -k ${KERNEL_VERSION} + fi + # compat symlinks for the official kernels only if [ -z "${KERNEL_NAME}" -o "${KERNEL_NAME}" = "-lts" ]; then loaders="$(find /boot -name syslinux.cfg -or -name extlinux.conf -or -name grub.cfg -or -name menu.lst)" @@ -53,6 +60,13 @@ depmod ${KERNEL_VERSION} echo ">>> Generating initial ramdisk, using mkinitcpio. Please wait..." mkinitcpio -p linux${KERNEL_NAME} + + pacman -Q dkms &>/dev/null + hasdkms=$? + if [ $hasdkms -eq 0 ]; then + echo ">>> Running the DKMS autoinstall service..." + dkms autoinstall -k ${KERNEL_VERSION} + fi } post_remove() {

<deleted-account> commented on 2012-05-23 02:36 (UTC)

@felixonmars @ValdikSS I think uksm is now official supported here: https://aur.archlinux.org/packages.php?ID=58802 And I've seen this interface on the user manual the first day I installed uksm, I am actually thinking this idea(remote debugging) is cool. Every other APPs have this feature nowadays, I just hate to dump my all messy stuff(i.e. /proc info, dmesg, core dumps....etc) if I see a bug and told to do so ---- that sounds more like they are debugging me! :P

felixonmars commented on 2012-05-23 02:19 (UTC)

@ValdikSS Hi, I e-mailed author of uksm and got his reply. This is documented but not that easy to find :P “usr_spt_enabled: Testing interface for future feature of “remote bug reporting”. Currently this interface is enabled by default for testing —- this will make uksmd send a meaningless udp message from your machine every 2 mintues. You can disable it by echo 0 > usr_spt_enabled. (via:http://kerneldedup.org/en/projects/uksm/uksmdoc/usage/).” And he stated they will split these codes so it won't be too confused.

« First ‹ Previous 1 .. 256 257 258 259 260 261 262 263 264 265 266 .. 308 Next › Last »