Systemd 250 Released
lwn.net
Systemd 250 Released
1–10 of 204 posts
Re: Systemd 250 Released
#2minor issue, but anyone know how breaking changes are managed?
between ubuntu16 and ubuntu20 some unit file parameters have changed. I find it rather troubling that we can't maintain consistency.
Re: Systemd 250 Released
#3> The static lease DHCP server logic in systemd-networkd may now serve IP addresses outside of the configured IP pool range for the server.
See, see, taking lessons from C++. So someone requested a bug, and they got it. How could that be useful?
Re: Systemd 250 Released
#4> The static lease DHCP server logic in systemd-networkd may now serve IP addresses outside of the configured IP pool range for the server. See, see, taking lessons from C++. So someone requested a bug, and they got it. How could that be useful?
Systemd is a matryoshka doll of bugs.
How could that be useful?
Re: Systemd 250 Released
#5> The static lease DHCP server logic in systemd-networkd may now serve IP addresses outside of the configured IP pool range for the server. See, see, taking lessons from C++. So someone requested a bug, and they got it. How could that be useful?
Suppose you have a network 192.168.0.0/24, with the router at 192.168.0.1, and you want the DHCP server to hand out dynamic addresses from 192.168.0.50 to 192.168.0.240 to clients, and hand out static IPs from 192.168.0.2 to 192.168.0.49 to specific identified devices via static leases. Those static IPs are outside the configured IP range for the DHCP server, intentionally.
Re: Systemd 250 Released
#6At this point any system that is running this should not be called "UNIX derived" or "UNIX like" as systemd has subsumed all of the pre-existing architecture around system startup and management. Not arguing if that is a good or bad thing just saying we should stop putting systemd managed systems in the 'UNIX' column just like we don't put Windows NT systems in the UNIX column.
Re: Systemd 250 Released
#7At this point any system that is running this should not be called "UNIX derived" or "UNIX like" as systemd has subsumed all of the pre-existing architecture around system startup and management. Not arguing if that is a good or bad thing just saying we should stop putting systemd managed systems in the 'UNIX' column just like we don't put Windows NT systems in the UNIX column.
Agreed, also no judgement here as well.
I propose: "UNIX-ish" or Sysd type Linux.
Shit, what am I thinking!
GNU LINUX was the older discussion and development.
SYSTEMD LINUX is likely most applicable nomenclature, given current development.
Re: Systemd 250 Released
#8At this point any system that is running this should not be called "UNIX derived" or "UNIX like" as systemd has subsumed all of the pre-existing architecture around system startup and management. Not arguing if that is a good or bad thing just saying we should stop putting systemd managed systems in the 'UNIX' column just like we don't put Windows NT systems in the UNIX column.
[deleted]
Re: Systemd 250 Released
#9I just want to pre-empt the inevitable bitching about systemd to say I think it’s awesome and incredibly useful and consistent and powerful and I’d take it any day over the mess of stuff that filled systemd’s duties before.
Sure it isn’t perfect, but what software is?
And let me ask a question, if systemd is crap, why does every major distro use it? If it was truly crap then surely the distro builders would use the alternative?
Re: Systemd 250 Released
#10> The static lease DHCP server logic in systemd-networkd may now serve IP addresses outside of the configured IP pool range for the server. See, see, taking lessons from C++. So someone requested a bug, and they got it. How could that be useful?
DHCP protocol actively avoids specifying a policy - that is for the system administrator. It defines three 'mechanisms' for allocation [0]:
* automatic == permanent address
* dynamic == finite (time-limited) and possibly re-assignable to a different client
* manual == assigned by system administrator (and simply conveyed by DHCP)