Re: Someone using COMPAT_SVR4(_32) ?

[Dave McGuire <mcguire%neurotica.com@localhost>]

On 08/02/2017 01:34 AM, Maxime Villard wrote:
> What I'm saying is, if someone here is interested in doing this
> work, there is no reason to remove compat_svr4.

  Whether that's the case or not, there is STILL no reason to remove it.
 It can be disabled in kernel builds, and if someone needs it, either
now or in the future, they can enable it and either take the risks or
fix the bugs.

> No one, and I'm just here to do some survey, and ask people how they
>  use compat_svr4 if they do. When I have some basic idea on the 
> subject, I can open a discussion. Nothing less, nothing more.

  No.  In your first message on this subject, you stated that your
intention was to remove this functionality:

  "I plan to remove both of them, but I'd like some feedback."

  This was pretty clear to me.  "I plan to remove both of them" is not
the same thing as "I'm just here to do some survey".

> It is curious to see how you (John, Dave and Eduardo) are trying to 
> put some drama in this thread, while I'm just asking how people use 
> compat_svr4.

  No, you're not "just asking how people use compat_svr4".  You
announced a PLAN to remove it.

> I understand that you three do not use compat_svr4, because if you 
> were, you would have told me already. That's fine, I'm not accusing 
> you of anything, I'm just asking.

  Fallacious logic.  I myself have used it, I don't currently, but I may
in the future.  It's not up to you to decide that I will no longer have
the option.

  Very few of the people who run this software are on this mailing list.
You will reach almost none of the users with your survey attempts.
Removing functionality that has been there for a couple of decades is
not a good approach.  You seem to have a desire to contribute effort.
If you're able, why don't YOU take a whack at fixing the bugs.  I'm a
programmer too; I realize that just deleting the code is quicker and
easier.  But in the 24 years that I've been using this OS, we've rarely
if ever taken that approach.  And knowing something about how this OS is
used in the field, it's dangerous, and is virtually guaranteed to cause
someone else a great deal of heartburn in the future.

  Your approach is tantamount to hostage-taking: "Drop what you're doing
and maintain this piece of code, or I will remove it!"  A more
reasonable approach would be something like: "There are problems in this
code, is anyone working on this?  If not, I'll take a whack at it."

  I really shouldn't have to explain this to you, but I guess it takes
all kinds these days.

              -Dave

-- 
Dave McGuire, AK4HZ
New Kensington, PA