Tiny Core Linux
dCore Import Debian Packages to Mountable SCE extensions => General dCore Talk => Topic started by: PDP-8 on May 26, 2019, 06:53:53 AM
-
Just wondering if Devuan might be a good fit for Dcore?
No need to rehash all the systemd stuff found elsewhere.
BUT, wonder from purely a technical standpoint, if Devuan's detachment from systemd hooks in Gnome and elsewhere might be beneficial.
Again - just wondering - not looking to pick a political agenda fight.
-
I like the sound of that, especially as I'm about to try dCore myself.
Could I just use Devuan packages, or would that cause some kind of problem with dCore(?).
-
I did make and test a dCore-ascii made from Devuan Ascii, but Devuan Packages files pull from both Devuan and Debian repos with a prefix of DEVUAN or DEBIAN in front of the path to the file name on the server contained in the Packages file. Devuan only hosts on it's servers the packages like udev that are different from the Debian repo, otherwise it pulls from Debian servers. And there is no simple way to factor this into the dCore routines.
I would like to use Devuan for a dCore simply for the lack of systemd, time will tell how long it is possible to run a current Debian style Linux without using systemd as the init process. I may revisit Devuan in the future.
-
Ah, good to know... just thinking out loud here ...
If one wanted to stick to a more classic init, I think the MX Linux guys pull from Debian Stable, but use the sysv init - BUT have the "shims" installed so that systemd is just ignored.
And, like Devuan, if one wants to use systemd, they can do so. For MX it might be a bootloader option to run systemd.
And to show I'm not paranoid, I wonder if TinyCore could benefit from using busybox / systemd as the init? Heresy? I'm kind of afraid to ask. :)
-
There’s no plan to use systemd.
-
I can verify that with the latest rc I'm testing.
When trying to fix what appears to be a locale problem with my a/u/xterms, I tried using a systemd localectl and here is what came up in big bold red characters:
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to create bus connection: Host is down.
So there you go. Reassuring to some.