Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 27 |
Nodes: | 6 (0 / 6) |
Uptime: | 55:04:11 |
Calls: | 481 |
Calls today: | 13 |
Files: | 1,071 |
Messages: | 95,803 |
Posted today: | 2 |
My God, how did we all manage running services before systemd came along?
Jim Jackson , dans le message <slrnvlk56u.2qa.jj@iridium.wf32df>, a crit:
My God, how did we all manage running services before systemd came along?
Badly, with services that have crashed and nobody noticed for weeks.
Some teams have been working on better replacement for SysV init, but
without the industrial strength of Red Hat they could only stay niche.
Badly, with services that have crashed and nobody noticed for weeks.
Some teams have been working on better replacement for SysV init, but
without the industrial strength of Red Hat they could only stay niche.
Kenny McCormack, dans le message <vjec09$1jpju$1@news.xmission.com>, a
crit:
Badly, with services that have crashed and nobody noticed for weeks.
Some teams have been working on better replacement for SysV init, but
without the industrial strength of Red Hat they could only stay niche.
I wrote that, not you, liar.
It is not clear whom you are calling a "liar".
My post made it clear that you wrote the content
and I was only correcting
your inadvertent failure to fix the Subject line.
Only in the last 15 years or so did corps start to force
their ideas into linux.
Nobody can “force” their ideas into Open Source.
Lawrence D'Oliveiro , dans le message <vjfob3$2vfl9$4@dont-email.me>, a
écrit :
Nobody can “force” their ideas into Open Source.
Of course they can. Have enough hired developers contribute to the
project, bully the project leader into resigning ...
Oracle tried that sort of thing, with the Open Source projects it
inherited from Sun. Remember what happened? The contributors left
wholesale to set up a fork. And the forks ended up doing better than the originals.
So no, it pays not to antagonize the Open Source community. They have long memories.
Lawrence D'Oliveiro , dans le message <vjg88j$36h24$5@dont-email.me>, a
écrit :
Oracle tried that sort of thing, with the Open Source projects it
inherited from Sun. Remember what happened? The contributors left
wholesale to set up a fork. And the forks ended up doing better than
the originals.
So no, it pays not to antagonize the Open Source community. They have
long memories.
Your example proves that it does not always work.
Your example does not prove that it never works.
We have an example proving that its it working at least once.
On Thu, 16 Jan 2025 17:17:50 -0000 (UTC), Waldek Hebisch wrote:
Rather that vendors can (an will) break compatibility when they want.
But they cannot lock Open Source users into their product.
And actually systemd is an example of thing that users are essentially
forced to use regardless if they want it or not ...
It is one of many choices of init/service-management systems. You have
your choice of distros with or without it.
Certainly for headless (no graphics) purposes, it is still comparatively
easy in Debian to replace systemd ...
On Sat, 18 Jan 2025 20:00:35 -0000 (UTC), Jim Jackson wrote:
Certainly for headless (no graphics) purposes, it is still comparatively
easy in Debian to replace systemd ...
Or why not use Devuan, which explicitly sets out to be Debian-without-systemd?
On 2025-01-16, Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
On Thu, 16 Jan 2025 17:17:50 -0000 (UTC), Waldek Hebisch wrote:
Rather that vendors can (an will) break compatibility when they want.
But they cannot lock Open Source users into their product.
And actually systemd is an example of thing that users are essentially
forced to use regardless if they want it or not ...
It is one of many choices of init/service-management systems. You have
your choice of distros with or without it.
Certainly for headless (no graphics) purposes, it is still comparatively
easy in Debian to replace systemd with the old sysv-init(or alternative
init) stuff. Though I'm not sure for how long that will be true. But you don't >even need to switches distros.
On Sat, 18 Jan 2025 20:00:35 -0000 (UTC)
Jim Jackson <jj@franjam.org.uk> wibbled:
On 2025-01-16, Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
On Thu, 16 Jan 2025 17:17:50 -0000 (UTC), Waldek Hebisch wrote:
Rather that vendors can (an will) break compatibility when they want.
But they cannot lock Open Source users into their product.
And actually systemd is an example of thing that users are essentially >>>> forced to use regardless if they want it or not ...
It is one of many choices of init/service-management systems. You have
your choice of distros with or without it.
Certainly for headless (no graphics) purposes, it is still comparatively >>easy in Debian to replace systemd with the old sysv-init(or alternative >>init) stuff. Though I'm not sure for how long that will be true. But you don't
even need to switches distros.
Where do you get all the /etc/rc* files from that init requires?
On 2025-01-20, Muttley@DastardlyHQ.org <Muttley@DastardlyHQ.org> wrote:
On Sat, 18 Jan 2025 20:00:35 -0000 (UTC)
Jim Jackson <jj@franjam.org.uk> wibbled:
On 2025-01-16, Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
On Thu, 16 Jan 2025 17:17:50 -0000 (UTC), Waldek Hebisch wrote:
Rather that vendors can (an will) break compatibility when they want. >>>>But they cannot lock Open Source users into their product.
And actually systemd is an example of thing that users are essentially >>>>> forced to use regardless if they want it or not ...
It is one of many choices of init/service-management systems. You have >>>> your choice of distros with or without it.
Certainly for headless (no graphics) purposes, it is still comparatively >>>easy in Debian to replace systemd with the old sysv-init(or alternative >>>init) stuff. Though I'm not sure for how long that will be true. But you >don't
even need to switches distros.
Where do you get all the /etc/rc* files from that init requires?
Good call. I'd done an upgrade from the previous version of PiOS that
I'd switched from systemd to sysv-init. That upgrade (yes I know it's
not recommended, but it is possible) put systemd back, so when I did the >switch to sysv-init again, the startup files were still in situ!
But they appear to be there as the package orphan-sysvinit-scripts
https://packages.debian.org/search?keywords=orphan-sysvinit-scripts
I'd switched from systemd to sysv-init. That upgrade (yes I know it's
not recommended, but it is possible) put systemd back, so when I did the switch to sysv-init again, the startup files were still in situ!
On Mon, 20 Jan 2025 17:02:51 -0000 (UTC)
Jim Jackson <jj@franjam.org.uk> wibbled:
https://packages.debian.org/search?keywords=orphan-sysvinit-scripts
Good to know they're available but I wonder how long that'll last?
On Thu, 12 Dec 2024 11:26:01 -0000 (UTC), Muttley wrote:
Only in the last 15 years or so did corps start to force
their ideas into linux.
Nobody can “force” their ideas into Open Source. Ideas only get adopted for their intrinsic merit, not because of any big-budget marketing
campaign to tell everyone how wonderful it is.
What would be the business model for such a marketing campaign, anyway?
And once something gets wide adpotion compatibility concerns frequently
mean that intrinsically better ideas have no chance.
On Tue, 14 Jan 2025 20:28:21 -0000 (UTC), Waldek Hebisch wrote:
And once something gets wide adpotion compatibility concerns frequently
mean that intrinsically better ideas have no chance.
Open Source projects seem less hidebound by that. Look at the way things
have evolved, with old “traditional” *nix ideas being supplanted by new ones: netstat/ifconfig by iproute2, X11 by Wayland, various hacky audio things by first PulseAudio and then PipeWire, sysvinit by systemd (and
other options) etc.
Just goes to show, there is no “vendor lock-in” in the Open Source world.
Rather that vendors can (an will) break compatibility when they want.
And actually systemd is an example of thing that users are essentially
forced to use regardless if they want it or not ...
On Thu, 16 Jan 2025 17:17:50 -0000 (UTC), Waldek Hebisch wrote:
Rather that vendors can (an will) break compatibility when they want.
But they cannot lock Open Source users into their product.
And actually systemd is an example of thing that users are essentially
forced to use regardless if they want it or not ...
It is one of many choices of init/service-management systems. You have
your choice of distros with or without it.