Stop removing Init- Scripts from packages!

[karog]

$this->bbcode_second_pass_quote('WarheadsSE', 'W')e're working on it, but, hey, I have to have bread and water.

[xenoxaos]

Arch Linux has actually been warning of this since November.

https://www.archlinux.org/news/final-sy ... n-warning/
$this->bbcode_second_pass_quote('', 'A')s previously announced, initscripts are no longer receiving any testing and support has been dropped from various packages. Any users still using them should switch to systemd.
initscripts, sysvinit and the various rc scripts are being removed from the repositories to avoid any confusion about their status.

[darkside401]

Which in fact means that the Oxnas devices must be stated as unsupported by Arch Linux.

[WarheadsSE]

It isn't that they are unsupported, as such. Is it?

Sure, I can delete the entire section, kill the OS tarballs, and purge the device listing. Is that what you would prefer?

[darkside401]

Of course that is not what i want, but in my oppinion the really special thing about Arch is that you can update it to run the newest software version without any problems, and that is not possible with the Oxnas devices.

Would it be possible to have a special repo for the Oxnas devices which include the software with the init.d scripts?
I mean the software doesnt require systemd to run, it is only a matter to include the old init.d scripts in the packages.

The problem is that i dont work so long with Arch to now hard it might be to revert the packages back to sysvinit.
It might requires the old Packagebuilds prior to that ones which removed the init scripts and update it to the newest software versions, am i right?

$this->bbcode_second_pass_quote('xenoxaos', 'A')rch Linux has actually been warning of this since November.

[darkside401]

Or to have an own user contributed repo for the Oxnas devices, problem is i am no to this. Idont now how maintaining a repo works, or what kind of server you need etc.
I mean i will regulary update my Transmission, Samba and Sabnzbd installation.
As long as there are not huge changes the startup procedure of that services i should be manageable even for a quite normal user like me to get that stuff reintegrated.

Really helpful would be to have the PackageBuilds from before the removal of the initscripts, so we would have something like a blueprint, which only has to be modified for newer software versions.

[sethjvm]

Is the issue with the PLX hardware one that can be overcome with money? or time? or would it require a full time development staff such as PLX had before they divested the group that did the development? I am obviously not a developer or software guru so the details of what needs to be done are beyond my understanding. I don't know how many PPP users there are out there that visit this site but perhaps a bounty could be set and users can contribute if that would help. I understand that the issue is not for a lack of trying and am very appreciative of the efforts of WarheadSE and the others.

I see several options for people using a PPP.

1. Can www.archlinuxarm.org or some other benevolent entity host a wiki page for PPP users to post and share pre-systemd rc.d and conf.d files?

2. Move to something like optware on the PPP firmware/software.

3. Purchase different hardware (goflex or rasberry pi or...) to run Archlinuxarm

4. Move to debian since that is the "stable" brand of linux. (Yeah, I know that people will say it is not a brand and it is not really stable.)

5. Quit complaining, back up your rc.d and conf.d files and continue to use the 2.6.31 kernel with fingers crossed hoping that the developers are able to trace and fix the cache corruption problem and not discover some other PLX hackery.

6. Revert back to the Pogoplug software

[dinjo]

4. The only thing which is holding me up to move to debian is lack of newer packages or is there a alternatives ?

And i know there a rootfs for debian sometime back but after the new kernel flash (back porting) it also stopped working

[dinjo]

Can someone post deluge and deluge web init script