[systemd-devel] systemctl condreload - Is it a thing?
$SUBJECT pretty much says it all. It seems to work, but I can't find any mention of it in the documentation or with my Google searches. Is it deprecated and going away? Thanks! -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemctl condreload - Is it a thing?
Am 30.01.19 um 17:07 schrieb Ian Pilcher: > $SUBJECT pretty much says it all. It seems to work, but I can't find > any mention of it in the documentation or with my Google searches. > > Is it deprecated and going away? "condrestart" and "condreload" are working just fine and aliases for "try-reload" and "try-restart" as with the olld service-command while if find "try" a dumb wording to be honest given that it's executed based on the condition "is that service running" and not "tried" ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemctl condreload - Is it a thing?
On Wed, Jan 30, 2019 at 6:07 PM Ian Pilcher wrote: > $SUBJECT pretty much says it all. It seems to work, but I can't find > any mention of it in the documentation or with my Google searches. > > Is it deprecated and going away? > It's an old "compatibility alias" added in ~v20. (Apparently, ALT Linux wanted to just do a straightforward "service O V" → "systemctl V O" substitution or something like that.) I don't know if it'll be removed or not, but as is the general rule with everything not in official documentation, I would say _don't rely_ on its existence (unless it was specifically added for your use case). https://github.com/systemd/systemd/commit/64e5f1b721d76948e2987f65841dc087f684e1de http://git.altlinux.org/people/piastry/packages/?p=service.git;a=commitdiff;h=ba51a53881638ff0d93172ae3778329b2d5b316e -- Mantas Mikulėnas ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemctl condreload - Is it a thing?
On Mi, 30.01.19 10:07, Ian Pilcher (arequip...@gmail.com) wrote: > $SUBJECT pretty much says it all. It seems to work, but I can't find > any mention of it in the documentation or with my Google searches. > > Is it deprecated and going away? The official name for "condreload" is "try-reload-or-restart". The "condreload" name is supported still to make things easier for compat cases, but I'd recommend not using it anymore. It's unlikely to go away anytime soon though. Generally, in systemd when we want to de-emphasize something redundant or deprecated stuff we stop documenting it while still supporting it, so that people stop using it slowly. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemctl condreload - Is it a thing?
On 1/30/19 10:19 AM, Lennart Poettering wrote: The official name for "condreload" is "try-reload-or-restart". The "condreload" name is supported still to make things easier for compat cases, but I'd recommend not using it anymore. It's unlikely to go away anytime soon though. Makes sense. (I suspected that might be the case, but I was thrown off by the "or-restart" part.) Generally, in systemd when we want to de-emphasize something redundant or deprecated stuff we stop documenting it while still supporting it, so that people stop using it slowly. Well, that's one way to increase mailing list traffic. ;-) Thanks! -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Bugfix release(s)
On Di, 29.01.19 23:31, Ryan Gonzalez (rym...@gmail.com) wrote: > It's donotreply-systemd-...@refi64.com though I had already subscribed it > to the mailing list with a temporary route to my own email and then turned > off receiving messages, ... I'm guessing the whitelist would be better > though? Hmm. So I added this to the whitelist. And I just tagged v241-rc2, but no email appears to have been generated. Did you see the Github hook on your server? Or is this just some "pre" vs. "rc" artifact? Thanks, Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [ANNOUNCE] v241-rc2 tagged
Quick heads-up! I just tagged -rc2 of v241. Please test and report back. The next tag is most likely going to be the final v241, hence last chance to find bugs that need to be fixed pre-release. https://github.com/systemd/systemd/releases/tag/v241-rc2 Thanks, Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Bugfix release(s)
Unfortunately, it likely was. I updated the webhook to also log when a tag is ignored for the future and also changed it to use the rc tag. -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else https://refi64.com/ On Wed, Jan 30, 2019, 12:34 PM Lennart Poettering wrote: > On Di, 29.01.19 23:31, Ryan Gonzalez (rym...@gmail.com) wrote: > > > It's donotreply-systemd-...@refi64.com though I had already subscribed > it > > to the mailing list with a temporary route to my own email and then > turned > > off receiving messages, ... I'm guessing the whitelist would be better > > though? > > Hmm. So I added this to the whitelist. And I just tagged v241-rc2, but > no email appears to have been generated. Did you see the Github hook > on your server? Or is this just some "pre" vs. "rc" artifact? > > Thanks, > > Lennart > > -- > Lennart Poettering, Red Hat > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Fail to load network modules properly
Well after analysing dmesg I see that only difference between successful and failed boot is the time when ext4 main partition is mounted for the second time. In failed boot it is mounted between cfg80211 module and wl module. Detailed dmesg listing is in my first message. That is why I asked is there any possibility to force loading cfg80211 module only after main partition is mounted for the second time. I assume that is should be done somehow by systemd. But I'm not experienced enough to solve this by myself. Łukasz Słaboń On Tue, Jan 29, 2019 at 4:50 PM Colin Guthrie wrote: > Łukasz Słaboń wrote on 28/01/2019 19:23: > > Yes, as far as I know it should load firmware. Is there a possibility to > > force loading wl driver and module only after partition is mounted? I > > assume that something systemd scripts needs to be changed to force > > different boot sequence. > > Firmware is usually stored in the /usr tree. systemd typically requires > that /usr is available from early boot (i.e. before modules are > initialised). > > If /usr is a separate partition, it is the job of the initrd to ensure > /usr is mounted prior to pivoting into systemd on the filesystem. > > If the module is compiled into the kernel or included in the initrd, > then the firmware file would also typically have to be included in the > initrd too. > > dracut takes care of all this for you, not sure about other initrd > generators. > > Col > > -- > > Colin Guthrie > gmane(at)colin.guthr.ie > http://colin.guthr.ie/ > > Day Job: > Tribalogic Limited http://www.tribalogic.net/ > Open Source: > Mageia Contributor http://www.mageia.org/ > PulseAudio Hacker http://www.pulseaudio.org/ > Trac Hacker http://trac.edgewall.org/ > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] GithHub / private repos
If we're actually discussing private repos for reporting security issues then Github product is not helpful. It seems that most of the projects use private mailing lists for that. For example, Linux kernel has secur...@kernel.org and another one for coordination with distributions - more details here https://www.kernel.org/doc/html/v4.18/admin-guide/security-bugs.html So I think something like systemd-secur...@lists.freedesktop.org is the way to go. Alex On Sat, Jan 26, 2019 at 3:42 PM Lennart Poettering wrote: > > On Di, 15.01.19 21:21, Alex Dzyoba (a...@dzyoba.com) wrote: > > > When you create a new organization you can choose "Team For Open > > Source" plan. Here is the link > > https://github.com/account/organizations/new > > > > Though, I don't know if it's possible to upgrade the existing systemd > > organization, sorry. Maybe it's possible to contact github support to > > ask for this. > > So I had a closer look at this, and found this: > > https://help.github.com/articles/github-s-products/ > > IIUC "GitHub Team for Open Source" doesn't actually add anything we > need. Because what we need would actually be the ability for arbitrary > people (i.e. not people who necessarily are members of our systemd > team on github) to send us private PRs and issues in order to handle > security issues. > > It appears to me that plan does not provide the core need we have: > allow those random folks from the Internet to report security issues > in privacy to us... Or what am I missing? > > Lennart > > -- > Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel