Bug 29981 - Reiser 4 & 5 request consideration, effectively NEW FACILITY REQEST
Summary: Reiser 4 & 5 request consideration, effectively NEW FACILITY REQEST
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL: https://reiser4.wiki.kernel.org/index...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-01 10:18 CET by kiriakos bel
Modified: 2022-02-01 20:24 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description kiriakos bel 2022-02-01 10:18:31 CET
This is not a bug, but a request for consideration to include reiser 4 & 5 filesystems in Mageia, if possible!
Comment 1 Morgan Leijström 2022-02-01 12:32:28 CET
Thank you for the interest.

We dropped Reiser4 ten years ago as it was not working then.
Bug 5680

I have read it have been maintained since then, but do not aim to be included in mainstream linux.
To me, Reiser5 seem still too new, but this is not my cup of tea.

CC kernel&drivers, and tools maintainers for comment/consideration.

Another request for filesystem, OpenZFS, is in Bug 17245

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=17245
URL: (none) => https://reiser4.wiki.kernel.org/index.php/Why_Reiser4
CC: (none) => fri, kernel, mageiatools

Comment 2 Lewis Smith 2022-02-01 20:24:45 CET
Thanks Morgan for your helpful comment.
> I have read [Reiser4] do not aim to be included in mainstream linux
It looks as if Reiser4 is (will be) a dead duck.

As for Reiser5 being too new, Reiser was always rather in this state - for the brave.

I think kernel is the best opinion to have about this, so assigning the bug there. [Re-assign if appropriate]. Leaving 'tools' CC'd.

Summary: Reiser 4 & 5 request consideration => Reiser 4 & 5 request consideration, effectively NEW FACILITY REQEST
CC: kernel => (none)
Assignee: bugsquad => kernel


Note You need to log in before you can comment on or make changes to this bug.