Re: aufs5 GIT release (v6.0-rc1)
Dear J.R.O. Firstly - huge thanks for all the effort you have put into AUFS over the years. As you know, Puppy Linux has used an AUFS patched kernel for many years (an original design choice by Barry Kauler) and many of Puppy's unique features are based on AUFS facilities. AUFS patched kernels are still regularly produced in both 32-bit and 64-bit variants (but not currently a 32-bit 6.1 version - this may need to be rectified): [1]https://github.com/puppylinux-woof-CE/woof-CE/actions/workflows/kern el-kit.yml and these are then used in various Puppy Linux system builds: [2]https://github.com/puppylinux-woof-CE/woof-CE/actions [3]https://github.com/peabee/releases/releases The decision on which kernels to support is, of course, yours. Hopefully 5 series AUFS patched kernels will remain buildable for some time to come. If and when the AUFS patches start to fail we have a variety of strategies to pursue we can switch our system builds to a different kernel; we can cease building new versions of the older systems entirely; we can generate our own AUFS patches to overcome the problem if simple - e.g. as we did for 5.4: [4]https://github.com/puppylinux-woof-CE/woof-CE/blob/testing/kernel-ki t/patches/aufs_sources/k5.4.x.patch We can also move away from using AUFS patched kernels to using OverlayFS instead. This has already started to happen. The resulting systems do lose some functionality but are gradually being improved to the point where they are quite viable. e.g. Bookworm Pup64 10.0.1 [5]https://forum.puppylinux.com/viewtopic.php?t=8690 So the bottom line is we will be sad if some LTS kernels gradually cease to have AUFS capabilities, but will no doubt be able to live with the situation if you decide to allocate your scarce resources differently. Thanks again. PeeBee References 1. https://github.com/puppylinux-woof-CE/woof-CE/actions/workflows/kernel-kit.yml 2. https://github.com/puppylinux-woof-CE/woof-CE/actions 3. https://github.com/peabee/releases/releases 4. https://github.com/puppylinux-woof-CE/woof-CE/blob/testing/kernel-kit/patches/aufs_sources/k5.4.x.patch 5. https://forum.puppylinux.com/viewtopic.php?t=8690
Re: aufs5 GIT release (v6.0-rc1)
Hi Tomas, Tomas M: > Although I am not PeeBee, and I recognize that your email was not > directed at me, I feel compelled to share my thoughts as a long-time > AUFS user. I hope my perspective may assist you in making good > decision. Yes, you are definetly one of the oldest aufs user. And I remember your past donations many years ago, also you put a call out other people for donations. That is a good motivation for me to keep developing aufs. > version. I firmly believe that if any specific user desires > maintenance for older kernel versions, they might consider offering > you compensation, such as ongoing financial contributions, for as long > as they require you to sustain that older version. Fair enough. But I will consider again and again when I ask the user donation to keep older versions. Anyway I appriciate your opinion/suggestion and support. J. R. Okajima
Re: aufs5 GIT release (v6.0-rc1)
Hello Okajima-san, let me express my heartfelt gratitude to you for your dedication to maintaining AUFS over so many years. Although I am not PeeBee, and I recognize that your email was not directed at me, I feel compelled to share my thoughts as a long-time AUFS user. I hope my perspective may assist you in making good decision. I would be entirely satisfied if you were to maintain AUFS only for Linux version 6.1 and later. In fact, I would still be content if you chose to support AUFS solely for the newest stable Linux kernel version. I firmly believe that if any specific user desires maintenance for older kernel versions, they might consider offering you compensation, such as ongoing financial contributions, for as long as they require you to sustain that older version. I understand that some decisions can be challenging, particularly when there's a risk of disappointing others. While I know you strive not to let people down, I also recognize that pleasing everyone is an unattainable goal, so attempting to do so would be futile. Thank you for taking the time to consider my viewpoint. Sincerely, Tomas M slax.org On Wed, Aug 23, 2023 at 4:44 PM J. R. Okajima wrote: > > Hello PeeBee, > > A year ago, I posted to this ML saying I was going to stop maintaining > aufs5.10--aufs5.14 versions. > And you replied, > > PeeBee: > > Many thanks - would you consider maintaining support for LTS 5.10 - EOL > > = Dec, 2026 ?? > > And I kept maintaining aufs5.10 and later. > > But maintaining many versions is a really tough and hard work for me > (currently aufs5.10--aufs6.x). > Now I am seriously considering stop supporting aufs5.10--aufs6.0, which > means I support one last longterm version (linux-v6.1) and later. > I hope you would accept. > > > J. R. Okajima >
Re: aufs5 GIT release (v6.0-rc1)
Hello PeeBee, A year ago, I posted to this ML saying I was going to stop maintaining aufs5.10--aufs5.14 versions. And you replied, PeeBee: > Many thanks - would you consider maintaining support for LTS 5.10 - EOL > = Dec, 2026 ?? And I kept maintaining aufs5.10 and later. But maintaining many versions is a really tough and hard work for me (currently aufs5.10--aufs6.x). Now I am seriously considering stop supporting aufs5.10--aufs6.0, which means I support one last longterm version (linux-v6.1) and later. I hope you would accept. J. R. Okajima
Re: aufs5 GIT release (v6.0)
"J. R. Okajima": > - git repositories for aufs6 will appear in a week or two. I was going to create new repositores for aufs6 on github, but I couldn't. aufs5-linux.git on github is a fork of torvalds/linux.git, and github doesn't allow me to create a new fork of the repository which I already made a fork. Obviously I could make a brand new empty aufs6-linux.git repo, but in this case I had to push all git-objects in mainline. That is unrealistic. So I decided to rename aufs5-linux.git and aufs5-standalone.git on github to aufs-linux.git and aufs-standalone.git respectively. And they will have the branches for aufs6 series. If you have a clone (or a fork) of aufs5 repositories, please rename them to non-versioned name. I guess .git/config is the place. J. R. Okajima
aufs5 GIT release (v6.0)
o news - linux-v6.0 is released and aufs5.x-rcN branch supports it. - note that core file produced by linux-v6.0 is broken. the bug is fixed just after linux-v6.0 is released. - git repositories for aufs6 will appear in a week or two. J. R. Okajima
aufs5 GIT release (v6.0-rc4 and v5.10.140)
o news - new branch aufs5.10.140 is released - aufs5.x-rcN branch simply follows the mainline v6.0-rc4 - no new features and fixes are added J. R. Okajima
Re: aufs5 GIT release (v6.0-rc1)
aufs5 GIT release (v6.0-rc1)
o news When linux-v6.0 (not -rcN) is released, current GIT repos (aufs5-linux and aufs5-standalone) will be replaced by aufs6-*, and I will stop maintaining aufs5.10--aufs5.14 branches. Aufs5.x-rcN branches in this replease is for linux-v6.0-rc1. No new features but some behaviours changed in the mainline. - unlink(2) and rmdir(2) in NFS is broken, and they may result NULL-pointer-access. - access(2) in tmpfs changed its error code. J. R. Okajima - aufs5-linux.git#aufs5.10..aufs5.19 Nothing - aufs5-linux.git#aufs5.x-rcN aufs: v6.0-rc1, aop->migrate_folio() and remove ->isolate_page()/putback_page() aufs: v6.0-rc1, de-const-fy the param of vfs_setattr() - aufs5-standalone.git Ditto - aufs-util.git Nothing
