You are not logged in.
at least ext4 is still receiving some love:
http://git.kernel.org/?p=linux%2Fkernel … mit&s=ext4
Offline
Let's look how Fedora handles this:
http://cvs.fedoraproject.org/viewvc/rpm … iew=markup
If I understand it right meanwhile almost all later features past 2.6.27 release have been going later into 2.6.27.xx series. But it's still called "ext4dev". Fedora only applies 2 ext4 related patches
# Filesystem patches
ApplyPatch linux-2.6.27-ext4-rename-ext4dev-to-ext4.patch
ApplyPatch linux-2.6.27.9-ext4-cap-check-delay.patch
To me it seems safe to take this over and rename the FS for us too and mkinitcpio should be able to boot into it.
Offline
Just stopping by to say: I really like this idea, and please continue your great work!
Offline
If I understand it right meanwhile almost all later features past 2.6.27 release have been going later into 2.6.27.xx series. But it's still called "ext4dev".
That was my understanding when I looking into this kernel a while ago. At that stage all the ext4 commits had just been backported. So applying those patches should be fine.
Offline
I have no seperate /boot partition and / is ext4 created by a kernel/e2fsprogs around 2.6.28 or 29. The boot failed when mkinitcpio detected the partition as ext4 filesystem and gave a panic.
Sorry for my bad english because this is exactly what i meant. What i have read is that it should works if you have a /boot partition with ext2.
If i'm wrong than this is no problem but if i'm right than there is no reason to remove the module. But will stop it because i don't want to critize you for your fantastic work.
Offline
2.6.27.31-2 is up for both arches and _should_ fully support ext4 filesystem. So far I couldn't reboot my ext4 system, because it's busy with uploading other stuff for some hours.
Though I don't expect any trouble try it only with non critical ext4 root filesystem partitions. You've been warned.
When we can canfirm this kernel well booting also into ext4 it's a major step to get real "fallback" state.
Offline
I could boot my ext4 system without any trouble and with a clean dmesg output. Go and test it. It should be soon ready to move to production systems.
Offline
I like this idea very much, thank you! Maybe adding ksplice support is easier for a less-often updated kernel, too. This would improve Arch on server even more.
Offline
When is kernel26-lts going to core?
Offline
today we had a new release 2.6.27.32 - I will build packages later tonight and then the signoff procedure starts again. feel free to give user signoffs on the arch-general list then (not many devs use that kernel it seems so signoffs come slowly).
Offline
new .32 version is broken:
Offline
2.6.27.33-1 in testing for signoff. I hope we can move it soon to core.
Offline
==> Running command: /sbin/mkinitcpio -k 2.6.27.33-lts -c /etc/mkinitcpio.conf -g /boot/kernel26-lts.img
:: Begin build
ERROR: module 'ext4' not found
Looks like it wasnt properly renamed.
Edit: It's not the renaming. It wasnt built.
find /lib/modules -name ext4*
/lib/modules/2.6.30-bfs/kernel/fs/ext4
/lib/modules/2.6.30-bfs/kernel/fs/ext4/ext4.ko
/lib/modules/2.6.30-ARCH/kernel/fs/ext4
/lib/modules/2.6.30-ARCH/kernel/fs/ext4/ext4.ko
x86_64 btw. :-)
Edit2: I'm gonna boot into that kernel now, since it looks like you built ext4 into the kernel (why?). CONFIG_EXT4_FS=y
I think it's better to keep it as a module, just like all the other fs', too.
Last edited by buddabrod (2009-09-10 18:03:18)
Offline
Ext4 support has been built into the kernel without a special reason. I commited to trunk to build it next time as module like all other filessystems.
functionality is not affected. afaik there's no more need to have the module in mkinitcpio.conf for the default and lts kernel. it should be autodetected.
Offline
functionality is not affected. afaik there's no more need to have the module in mkinitcpio.conf for the default and lts kernel. it should be autodetected.
You be realy sure that a boot image without the filesystem(s) module(s) can mount the root device at bootup? If yes, this would be nice and new for me. Or do you mean that mkinitcpio detect them even in every case?
Offline
if it's directly in the kernel you dont need to care about it.
But I think Andy meant that if you have the filesystems hook in your mkinitcpio.conf, you dont need to worry either.
Offline
if it's directly in the kernel you dont need to care about it.
That is clear.:)
But I think Andy meant that if you have the filesystems hook in your mkinitcpio.conf, you dont need to worry either.
Ah okay this is nice option for doing this too, thanks.
Offline
i don't know if it"s possible to add the kernel26-lts to desktop user, even though it is intented for server,i read on http://wiki.archlinux.org/index.php/Enh … _Stability , it propose to use it in reason of stability, but i wonder since the kernel-lts haven't any third party module, it means nvdia and virtualbox and vmware may fail, further more the current kernel is on 2.26.30, i am afraid it won't work(eg: Xorg), does anyone here use desktop boot with kernel26-lts and kernel 2.26.30? thanks
Offline
@Mug Okay, i can't speak exactly for the kernel26-lts package because i use my own kernel26-stable package with 2.6.27 for a longer time as a fallback kernel.
But i can say that nivida 185.18.36 (and xorg with the old method "xorg.conf not empty") works with the 2.6.27 kernel without a problem. The question from my view is more why to do this. As the wiki said the goal of 2.6.27 is that this is the kernel with long time support for having a kernel for a server or as fallback kernel.
Soory, i can't say anyhing about virtualbox and vmware (i prefer to use kvm ) but i think both know that 2.6.27 is an important kernel series and so i can imagine that they will work too. Therefore i don't think it is a problem to copy the PKGBUILD's, change the name plus the lines for using the kernel26-lts and test it.
Offline
From my week of experience, kernel26-lts is more stable than 2.6.30.5. On my server, I continually had NFS errors in my dmegs and the server would panic once in a while. Since booting my server more than a week ago, not even one dmesg entry has been added, stability is perfect.
Offline
hi Attila, i installed the kernel26-lts on my pc, as i thought, it can't boot properly Xorg, my nvidia module are compiled on kernel 26.30-3 , so does the virtual-box modules. i have to recompile the virtualbox modules, actually just reinstall it, it will compiled their module automatically. and i have to do Xorg --configure to make xorg work, my networkmanager module are losted,i can't find a way to restore them, and i can't really get nvidia modules work, seems they refuse the reinstall procedure, since i don't have all my old package in cache, it quite difficult to restore all the things without internet,finally i decided to give up,since my current kernel work perfectly, and i 'm not holding a server.
in my opinion it's possible to make all things work with kernel26-lts, i may need to find all incompatible modules,and recompile them on new kernel.
i may make an effort next time i have more spare time.
Offline
@Mug I'm surprised that nvidia don't works for you (or do i missunderstood you?). But you have two ways to do it:
1. Edit the PKGBUILD "pkgname=nvidia-lts" + "_kernver" and the install file "KERNEL_VERSION" (sorry i don't know exactly the uname output of kernel26-lts). Than build your package and install it. I think the most confusion comes because you don't make your own package with another name.
2. I prefer to install nvidia manual (because i do it in this way longer than i use arch) and than you have only to install the modul with the "--kernel-module-only" option. In this case you can break your package management but perhaps for a first test you download the same version as the arch package have (185.18.36) and do this for your kernel26-lts. You can find the module here:
/lib/modules/$(uname -r)/kernel/drivers/video/nvidia.ko.
For the other things, vmware and networkmanager, im not the right because i don't use them. Perhaps the switching of kernel26-lts and kernel26 is for your configuration too complicated and it is better to spend the time with other things.:)
Offline
If using lts in parallel with 30, I wouldnt worry about recompiling nvidia or vbox modules. The whole point is to have a proper fallback option for kernel updates, so the likely usage for booting into lts would be quick single user mode fixes... no X
Offline
Just wanted to say that kernel26-lts-i686 works on my desktop, all partitions are ext4.
Thanks for this great job!
Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd
Offline
Thank you very much. While I love Arch for its simple elegant minimalist approach, I prefer stability in some cases. I still don't have a ext4 partition, and have yet to enable testing on my systems. I love having the lts available for my little home server. I also like having a backup kernel to boot into on my main desktop and laptop just in case.
I trust Microsoft about as far as I can comfortably spit a dead rat.
Cinnamon is a wonderful desktop
"Faith is the substance of things hoped for, the evidence of things not seen."
Offline