Re: Some suggestions on old-fashioned usage with s6 2.10.x

On Mon, Feb 15, 2021 at 02:54:52PM +, Laurent Bercot wrote: > The options! The options need to be all compatible. :) And for > "shutdown", they would never implement a wrapper themselves, I would > have to do it for them - which is exactly what I did, although it's > a C program that actually

Re: Some suggestions on old-fashioned usage with s6 2.10.x

(Apologies for the broken threading, I originally sent my answer with the incorrect From: and it was rightfully rejected.)

Re: Some suggestions on old-fashioned usage with s6 2.10.x

I do not really understand their excuse here. CLI incompatibility is trivially solvable by creating links (or so) for `halt' / `poweroff' / `reboot', and even the `shutdown' command can be a wrapper for an `atd' based mechanism. The options! The options need to be all compatible. :) And

Re: Some suggestions on old-fashioned usage with s6 2.10.x

(I am extremely sorry for delaying this mail so much. I have just done two major refactoring/overhaul projects in this vacation around the Spring Festival, and still have one remaining. These projects are a part of my formal occupation, but I would not have much low-distraction time best for

Re: Some suggestions on old-fashioned usage with s6 2.10.x

El vie, 29 ene 2021 a las 14:27, Guillermo escribió: > [...] Huh. Lots of apostrophes that shouldn't be there, and that I just couldn't see without a fixed width font... G.

Re: Some suggestions on old-fashioned usage with s6 2.10.x

El vie, 29 ene 2021 a las 0:07, Casper Ti. Vector escribió: > > Not using s6-linux-init has never been an explicit goal, [...] > > Currently I do not understand the `s6-linux-init-shutdown(d)' way > well, so the old-fashioned way is retained at least for now, [...] Forgive me if I'm

Re: Some suggestions on old-fashioned usage with s6 2.10.x

But even `s6-reboot' from older s6-linux-init, or `busybox reboot' with slew can already do that... Yes. And as your sharp mind undoubtedly noticed, those commands are not the same as "reboot". Which means burden on users. Yes, I also thought it was a small burden at first, but it's not.

Re: Some suggestions on old-fashioned usage with s6 2.10.x

On Fri, Jan 29, 2021 at 09:57:43AM +, Laurent Bercot wrote: > It may cost more *to you*, but there is real and significant value > in following existing interfaces that people are familiar with. Being > able to just use "reboot" instead of the, uh, slightly less intuitive > "s6-svscanctl -6

Re: Some suggestions on old-fashioned usage with s6 2.10.x

Currently I do not understand the `s6-linux-init-shutdown(d)' way well, so the old-fashioned way is retained at least for now, given its simplicity in implementation and seemingly better flexibility. Frankly it is my intuition that the new way costs more than the old way, but does not provide

Re: Some suggestions on old-fashioned usage with s6 2.10.x

Actually I do visit the CGit web interface fairly often Oh, my bad, the links in the skaware documents actually point to https://git.skarnet.org/something. Fair enough then, I have made git.skarnet.org an explicit alias to skarnet.org. Perhaps I need to batch change all

Re: Some suggestions on old-fashioned usage with s6 2.10.x

On Thu, Jan 28, 2021 at 10:41:24PM -0300, Guillermo wrote: > Out of curiosity, do you have a reason for wanting to keep the > "old-fashioned way"? Is it a goal of your project to depend on s6 and > s6-rc, but not current s6-linux-init? It seems to me that doing so > would be easier. It even looks

Re: Some suggestions on old-fashioned usage with s6 2.10.x

On Fri, Jan 29, 2021 at 12:07:11AM +, Laurent Bercot wrote: > I may change it back, but I don't think the current state is broken, > because you're not supposed to access git.skarnet.org via HTTP(S)! :P Actually I do visit the CGit web interface fairly often, using it as a poor man's GitHub

Re: Some suggestions on old-fashioned usage with s6 2.10.x

El jue, 28 ene 2021 a las 7:08, Casper Ti. Vector escribió: > > I did not actively follow the recent evolution of s6, and have just been > bitten badly by s6 2.10.x on my Alpine servers (where slew [1] is used > of course) when it comes along with other updates. > > [1]

Re: Some suggestions on old-fashioned usage with s6 2.10.x

BTW, seems to be returning empty HTTP replies now; both and work as expected though. That is a side effect of a recent s6-networking addition, where s6-tlsd passes the SNI server name to the application via an

Re: Some suggestions on old-fashioned usage with s6 2.10.x

On Thu, Jan 28, 2021 at 05:21:59PM +, Laurent Bercot wrote: > There is no really good solution, and I prefer a short, sharp pain > (when things break) followed by relief (when they're fixed) to a long > dull ache (maintaining compat code). I see. I personally prefer to retain compat code if

Re: Some suggestions on old-fashioned usage with s6 2.10.x

> major version upgrades may break things. As plain as day. > I prefer a short, sharp pain (when things break) followed by > relief (when they're fixed) to a long dull ache (maintaining > compat code). I could not agree more, it would also bring zero anyhow except than extra, likely convoluted,

Re: Some suggestions on old-fashioned usage with s6 2.10.x

I did not actively follow the recent evolution of s6, and have just been bitten badly by s6 2.10.x on my Alpine servers (where slew [1] is used of course) when it comes along with other updates. Sorry. This bears repeating: major version upgrades may break things. Compatibility is a good

Re: Some suggestions on old-fashioned usage with s6 2.10.x

On Thu, Jan 28, 2021 at 07:09:08PM +0800, Casper Ti. Vector wrote: > Moreover, `.s6-svscan/finish' (linked to `rc.halt') will still need its > $1 set to `reboot', `halt' or `poweroff' by `s6-svscan' on exec(). I did not realise the great simplification to the command line options of

Re: Some suggestions on old-fashioned usage with s6 2.10.x

On Thu, Jan 28, 2021 at 06:08:36PM +0800, Casper Ti. Vector wrote: > then move the `s6-svc -X' invocation from `rc.halt' into `rc.fin' The `s6-svc -a' invocation in `rc.halt' needs to be moved accordingly. Moreover, `.s6-svscan/finish' (linked to `rc.halt') will still need its $1 set to `reboot',