This installer is universal. It supports systemd and SYSV init and containers. It must read the local configuration to determine what the user already has in place and what must still be created. As set forth in the initial discussion in July of last year when first brought to the forums, please read the mission statement;
I will take exception to “Just remove the check for anything in /etc/systemd”.
Why am I only hearing of this objection now?
All the feedback I’ve had to date has been in favor of this amount of detail and checking.
I reviewed the code last night (again). I can and will accommodate changes which improve. I will not, however, nullify what has been done unless overwhelming feedback from the community is voiced. (I know you’re all following along)
HOWEVER,
-
Linux isn’t meant for just those of us who like “hard core OS’s” anymore. Look at how far Ubuntu has deviated from “standard” yet it’s the #1 distro.
-
I’m the one who has to support it here in the forums. I can’t count how many NOOB errors I’ve had to deal with.
-
We all make config errors when setting things up. Isn’t it about time the software point such things out versus beating our heads against the desk trying to find out where we have a typo or bad permissions? How many wasted hours have we all spent trying to track such things down only to find that total PEBKAC moment?
-
As I’m about to start my day supporting the forums, reviewing the ticket list, I already see several threads which are obvious user configuration problems and not “bugs”. Plex has enough of its own bugs, it doesn’t need the help from the community (lol).
Again,
- Work with me. Help me iterate into the absolute best solution for everyone
- Don’t tell me how to support my product this late in the game as it won’t happen.
