Mailinglist Archive: opensuse-features (365 mails)

< Previous Next >
[openFATE 308426] Update to reiser4 on opensuse 11.3x
  • From: fate_noreply@xxxxxxx
  • Date: Tue, 2 Mar 2010 14:12:05 +0100 (CET)
  • Message-id: <feature-308426-9@xxxxxxxxxxxxxx>
Feature changed by: Andreas Jaeger (a_jaeger)
Feature #308426, revision 9
Title: Update to reiser4 on opensuse 11.3x

- openSUSE-11.3: Unconfirmed
+ openSUSE-11.3: Rejected by (a_jaeger)
+ reject date: 2010-03-02 14:11:48
+ reject reason: It's not in the upstream kernel.
Requester: Important

Requested by: Glenn Doig (doiggl)

see announcement from
built rpms

#1: Glenn Doig (doiggl) (2009-12-08 06:24:01)
Alse seeĀ  ->

#2: Andreas Jaeger (a_jaeger) (2009-12-08 10:20:38)
I propose to reject this until it's in the upstream kernel and we take
that kernel - and even then only as experimental filesystem.

#3: Glenn Doig (doiggl) (2010-01-03 07:04:48)
built rpms ->

#4: Jeff Mahoney (jeff_mahoney) (2010-01-04 09:54:18)
What is the proposal here? If it's just to include the reiser4 KMP, I
don't have any objections do that since there is a maintainer other
than me looking after it. For actually integration with the
distribution, I'm firmly against it. We don't want to add full support
for a file system with an unknown future. We'd either need to drag
around the code (and maintain it) forever or leave users with supported
configurations out in the cold.

#5: Jan Engelhardt (jengelh) (2010-01-09 01:56:17) (reply to #4)
By "integration" I suppose you mean making it show up in yast2. I find
it reasonable not to show it in yast2 for exactly that argument
(uncertain future), but by default only. Let's say, if the user passes
a "reiser4" boot param, then yast2 offers it in the dropdown box.
Similar to you needing the "xfs" boot parameter on Fedora/anaconda to
make XFS selectable.

openSUSE Feature:

< Previous Next >
This Thread
  • No further messages