3 ms·
Windows has nothing equivalent to systemd. Windows "Task Scheduler" is very simplistic and disorganized compared to systemd. systemd is definitely one of the ni
by okanat 2y ago
Windows has nothing equivalent to systemd. Windows "Task Scheduler" is very simplistic and disorganized compared to systemd. systemd is definitely one of the nicer things in the Linux world.
I like it a lot and my team uses it extensively to precisely specify the behavior of our embedded products. systemd has a low memory footprint for what it does. It also helps us make our products more secure by making it easier to isolate processes / different system services as much as possible. So the risk of getting hacked over a network service is reduced a lot. Without systemd we would be forced to create our own which wouldn't be as secure.
- akira2501 2y ago> Windows has nothing equivalent to systemd. The service manager? It manages services with many of the same features of systemd units, including advanced features, like firewall integration. This is combined with windows event system which provides many of the same features of the systemd journal. > making it easier to isolate processes / different system services as much as possible These features are built into the operating system. systemd provides a particular method of accessing them, but certainly not the only one. > So the risk of getting hacked over a network service is reduced a lot. Your risk of getting hacked has nothing to do with systemd. You are hoping that the easy process isolation features you're referencing actually work and thus _mitigate_ the potential damage of that hack. This is not bad strategy, but is on it's own, entirely incomplete. > Without systemd we would be forced to create our own which wouldn't be as secure. At the risk of being hyper critical, this is precisely the type of logic I would use to sell snake oil, too.