Comment # 12 on bug 1178797 from Frederic Crozat

(In reply to Lukas Ocilka from comment #11)
> It's not YaST who sets the elevator, it's the user/customer. The point here
> is
> that our customers might depend (or rather think they depend) on it.
> 
> YaST offers the UI to set that variable, customers use it and they don't get
> what they expected. There are obviously two options: 1. removal of the
> feature
> or 2. replacing with new functionality (how is an implementation detail).
> 
> The current solution in /usr/lib/udev/rules.d/60-io-scheduler.rules LGTM, but
> I'm not the one to decide if that is enough to replace the old functionality.
> 
> **Frederic, Rado: What do you think? Removal or new implementation?**

I'm tempted to say both:
- remove the old way, since it doesn't work anymore (and make sure we have a RN
entry for that in 15SP3)
- have a new feature to set IO scheduler (which is then handled by udev rules).