SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Given my anticipation for a certain game, I've decided, under the circumstances, to use this kernel. I'm not much for release candidates, preferring instead to wait for a point release before compiling it, but I've had some issues come up with the 4.11 series, and decided to give it a whirl. I am much pleased with 4.12. Not only does it not complain about my Corsair M65 gaming mouse, but it doesn't complain about EFI_MEMMAP not being enabled. Both minor annoyances, but I'm glad to see them gone anyway. I've noticed a minor tick upward in system stability as well. I'm wondering if it has to do with the new schedulers in the new kernel. The newest NVIDIA driver works with it as well. Another win.
Anyway, I'm glad I took the risk. I'm looking forward to seeing this released.
Yes, thank you. I looked at your patch on Sunday when I saw your name in the commit logs.
I don't have a UFS File System any more but I wonder if they'll backport your Patch into 4.4.72, etc ?
The same code is in 4.4.71 ...
Thanks for sharing !
-- kjh
Code:
<snip ~linux/fs/ufs/super.c ; lines 812-818>
812 uspi->s_dirblksize = UFS_SECTOR_SIZE;
813 super_block_offset=UFS_SBLOCK;
814
815 /* Keep 2Gig file limit. Some UFS variants need to override
816 this but as I don't know which I'll let those in the know loosen
817 the rules */
818 switch (sbi->s_mount_opt & UFS_MOUNT_UFSTYPE) {
<snip>
aaazen --
...
I don't have a UFS File System any more but I wonder if they'll backport your Patch into 4.4.72, etc ?
The same code is in 4.4.71 ...
Probably not and for most folks not needed.
The fs/ufs patch fixes a UFS filesystem bug that started with Linux 4.8.4 where copying a file from a UFS filesystem that is larger than 2GB gets truncated down to 2GB.
So they don't have to backport the patch to 4.4 or any kernel older than 4.8.4.
There is a possible use for the patch in older kernels if you are using the R/W feature of UFS. It might help to write files larger than 2GB. But I have not tested the R/W feature of UFS and UFS R/W is not turned on in Slackware kernels.
On a related note, there is another patch for FreeBSD partitions on MSDOS partitioned disks.
That block/partitons patch makes all the FreeBSD sub-partitions visible on Linux including the swap and other sub-partitions. This patch is only in the 4.12 series for now, but could also be backported to earlier kernels.
4.4.43 for x86_64 is already available at https://dusk.idlemoor.tk/linux-4.4/x86_64/
The others (4.4.43 for i686, and 4.9.4 for x86_64 and i686) should follow in the next couple of hours
This is entirely automatic and still quite experimental. Testing? I've heard of it. Feedback welcome
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.