Hi,
ignoring the ranting and putting the enlightening philantrophic
comments aside, on a pure technical level, being the author of procd, I
dont think this is a good idea. procd is an opt-in feature for those
that want to use it. there has never been a requirement to make it
baseline. USE_PROCD=1 is only intended for the owrt specific core
services that want to make use of the advanced features. owrt is a linux
system and thus should by default be able to run SYSV init style rc.d
scripts. anything else would be a very daring thing to do. To be honest
I dont even understand the motivation of wanting to make this opt-out.
John
On 02/08/2019 18:38, Reiner Karlsberg wrote:
Although not a developer of openwrt itself, but a happy (?) user, I
have to agree to the statement below.
PROCD=1 default is a NOGO for me.
Simple reason,as mentioned already: Software, which is not documented,
does not exist.
Which is a requirement, we had to obey to already half a century ago.
When I wrote my first Assembler code.
For me, this is another step of openwrt into bloatware, as it becomes
more and more "obfuscated",
the simple user like me not giving any idea, how it is supposed to work.
Which breaks another old principle of software development: Egoless
programming.
Not only the coder should understand, how it works.
Open Source is heading into Closed Source.
Back to the roots.
My few cents.
Reiner Karlsberg
Am 02.08.2019 um 18:18 schrieb Kevin 'ldir' Darbyshire-Bryant:
On 2 Aug 2019, at 16:00, Hannu Nyman <[email protected]> wrote:
Hauke Mehrtens kirjoitti 2.8.2019 klo 17.42:
On 7/23/19 3:37 PM, Petr Štetiar wrote:
Transition period for init script migration was long enough, let's
make USE_PROCD=1 default now so there's enough time to convert the
remaining services/init scripts for the next release.
Signed-off-by: Petr Štetiar <[email protected]>
---
package/base-files/files/etc/rc.common | 113
++++++++++---------------
1 file changed, 47 insertions(+), 66 deletions(-)
Do you know how many packages in the package feed and the main
repository are still not using procd?
External repositories, not the package feed, will probably be affected
most, but I think we do not have to care and there were many years to
convert.
Acked-by: Hauke Mehrtens <[email protected]>
Hauke
I do not remember seeing ever a general call for converting the old
packages to using procd. In that sense this proposed change to
switch the default comes a bit surpise.
Quick search in the packages feed repo reveals that there are 281
instances of "/etc/rc.common" and only 205 instances of USE_PROCD.
So, likely about 75 packages in the packages feed repo only are
using the old syntax without procd.
Has a decision been made to declare the old-style init file invalid?
Will it be possible to still use the syntax? What is the new
"override" to indicate the usage of the old syntax?
Or will the proposed change disable the packages using the old init
file syntax totally?
My reading of the change is that old syntax is basically dropped.
Wish for: We should be using procd and to that end I started looking
at converting the ‘important to me’ packages: ddns & miniupnpd.
Real life: Documentation is confusing vs real life which is just
plain different. See adblock startup script as an excellent example
of **** that just isn’t documented.
I gave up and left the process feeling very angry.
KDB
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
