I know we posted a news item back in November about the deprecation of old school rc.d scripts, but the current silent removal thing is not real cool, and one never knows what package is going to fail to start up next. Last week it was openvpn, today it appears samba has lost its script.
We should post a news item saying "scripts are disappearing as of now, please be aware", as any machine booted remotely gives absolutely zero indication that some service startup failed until you try to actually use the service. Also, rumor has it a community package exists to catalog these old rc.d scripts once they are removed, but `pacman -Ss initscripts` and `pacman -Ss rc.d` found me nothing. Giving our users (and hell, other developers) at least a bit of heads up would be awesome here.
Thanks, -Dan
Am 28.01.2013 16:46, schrieb Dan McGee:
I know we posted a news item back in November about the deprecation of old school rc.d scripts, but the current silent removal thing is not real cool, and one never knows what package is going to fail to start up next. Last week it was openvpn, today it appears samba has lost its script.
There are relevant mailing list posts about it:
https://mailman.archlinux.org/pipermail/arch-dev-public/2013-January/024291.... https://mailman.archlinux.org/pipermail/arch-dev-public/2013-January/024295....
I don't know where the mentioned package is, I couldn't find it.
I don't really see the problem - we said that we will not support non-systemd systems starting January, and that is what is happening.
Am 28.01.2013 16:46, schrieb Dan McGee:
I know we posted a news item back in November about the deprecation of old school rc.d scripts, but the current silent removal thing is not real cool, and one never knows what package is going to fail to start up next. Last week it was openvpn, today it appears samba has lost its script.
We should post a news item saying "scripts are disappearing as of now, please be aware", as any machine booted remotely gives absolutely zero indication that some service startup failed until you try to actually use the service. Also, rumor has it a community package exists to catalog these old rc.d scripts once they are removed, but `pacman -Ss initscripts` and `pacman -Ss rc.d` found me nothing. Giving our users (and hell, other developers) at least a bit of heads up would be awesome here.
Sure, we could post a news item that people need to migrate to systemd right now. But on the other hand we already did this: https://www.archlinux.org/news/end-of-initscripts-support/ It also clearly stated that support will be removed without any further notice. Those who are caught by this didn't do their sysadmin's homework anyway (e.g. reading news posts) Anyway, if anybody wants to put up a last reminder that might be a good idea.
I also did remove initscripts support from all my packages including devtools and logrotate scripts which call systemctl now.
Greetings,
Pierre
On Mon, Jan 28, 2013 at 4:46 PM, Dan McGee dpmcgee@gmail.com wrote:
I know we posted a news item back in November about the deprecation of old school rc.d scripts, but the current silent removal thing is not real cool, and one never knows what package is going to fail to start up next. Last week it was openvpn, today it appears samba has lost its script.
As there has been no announcement of anyone taking responsibility for the rc scripts, I'd assume that anyone still using them are basically on their own now.
We should post a news item saying "scripts are disappearing as of now, please be aware", as any machine booted remotely gives absolutely zero indication that some service startup failed until you try to actually use the service.
Makes sense.
Also, rumor has it a community package exists to catalog these old rc.d scripts once they are removed, but `pacman -Ss initscripts` and `pacman -Ss rc.d` found me nothing. Giving our users (and hell, other developers) at least a bit of heads up would be awesome here.
I know Lukas intended to do something along these lines, and indeed there is a repository [0], but apparently it is not shipped as a package (yet?).
Lukas, what is your plan with this? It would be good to know if and how you intend to deal with this stuff and include it in the announcement.
IMNSHO, it would probably be best to just unequivocally declare the rc scripts as dead and unsupported rather than try to play catch-up now. Official rc scripts support is really something we should have discussed and planned in December, not a month after things stopped working...
Cheers,
Tom
[0]: https://projects.archlinux.org/svntogit/community.git/tree/sysvinit-scripts/trunk.
On 28 January 2013 21:30, Tom Gundersen teg@jklm.no wrote:
IMNSHO, it would probably be best to just unequivocally declare the rc scripts as dead and unsupported rather than try to play catch-up now.
I agree with this, no half measures. :)
You made the announcement [1] in early November; title was pretty clear; time-frame was provided. There's nothing else left to do now but to drop the initscripts and sysvinit packages.
[1] https://www.archlinux.org/news/end-of-initscripts-support/
arch-dev-public@lists.archlinux.org