Re: State of skarnet.org projects

I'd like to know what is your view and feeling of this expanding base, what does it mean to you, and whether you see an influence of the project by the growing popularity. If I can interpret this announcement correctly you seem already to be reacting to the Debian s6 incorporation fiasco more

State of skarnet.org projects

Hello, A small update on my current projects. - Most important skarnet.org packages are due a new release. If only to fix a bug that prevents them from properly installing shared libraries in some cases. - The release hasn't been cut yet because things are still evolving and I don't wan

Re: The "Unix Philosophy 2020" document

Another try: . Your efforts are commendable, but r/linux is, like most "general purpose, general audience" fora, a cesspool of ignorance and mediocrity - so the result was predictable. :D (Even if the moderator was well-intentioned, they have p

Re: The "Unix Philosophy 2020" document

If there's important pressure to have cgroups support, I will probably end up applying some version or another of jlyo's patch to s6-supervise Duh, no, I spaced out big time there. jlyo's patch is about namespaces support, not cgroups support. No modification to the supervisor is necessary to su

Re: Mailing list archives?

See ? Please be aware that due to a bug in the HTML displayer (which I still haven't delved into), some messages will be printed incorrectly. In that case, the messages are also available at https://www.mail-archive.com/supervision@list.skarnet.org/ -- Lauren

Re: The "Unix Philosophy 2020" document

I also wonder if someone on this mailing list is interested in actually implementing a cgroup-based babysitter as is outlined in the post, perhaps packaged together with standalone workalikes of the cgroup chainloaders (`create-control-group' etc) from nosh? Is there real pressure to have this?

Re: The "Unix Philosophy 2020" document

I have written a dedicated "s6/s6-rc vs systemd" post on the Gentoo forums, which I believe have included convincing responses to most common arguments by systemd proponents: . That is awesome, and you are doing very important work. (The kind o

Re: s6 usability

However - what is the concrete suggestion from the Debian guys what Laurent should do? The Debian people are happy with putting execline binaries in a separate directory that is not in the default PATH. They don't see a problem with that. And the thing is, nobody will notice a problem either

Re: s6 usability

You can sling all the insults you want, but the fact is ... the fact is, I have explained this multiple times on this very list, I am tired of seeing the same fallacy come up again and again, and I am tired of repeating myself. fine with me, as long as the distro cooperates. But if the distro

Re: s6 usability

That being said, is having your stuff on the executable path such an advantage? I don't know, why does Unix like to have its binaries in /bin? Why does PATH exist? What is the nature of an executable? You have two hours. December 2019 featured book: Rapid Learning for the 21st Century Ah,

Re: s6 usability

If you're referring to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906250#37 then, well, you are fighting against POSIX. There's little choice for Debian in the matter. Taking a hardline stance on such "legal" issues is part of their identity as a distro. No, you're falling for the prete

Re: s6 inotify

I'm looking for filesystem events similar to systemd.path in s6. My run script has to execute a binary when file "/tmp/testlog" is present. Can you please let me know which s6 program will help me achieve this. Hi Raghu, inotify(7) is a Linux extension, so it's not implemented in s6, which

Re: runit patches to fix compiler warnings on RHEL 7

I hope you find this comment useful. Yes, it was a very useful UX return, thank you. I think I'm going to work on an early version of s6-frontend, which will only provide daemontools-style and/or runit-style command emulation (depending on build-time options), and maybe a preliminary version

Re: runit patches to fix compiler warnings on RHEL 7

The browser is vastly superior for learning all about unfamiliar or moderately familiar software, but for the quick lookup of something you primarily know about, there's no substitute for a quick "man execlineb". https://lmgtfy.com/?q=execlineb&iie=1 -- Laurent

Re: s6 usability

From a Linux distribution perspective, there's also the question of if s6 can be made a drop-in replacement for daemontools, since it does follow djb's naming scheme. In gentoo, there are various packages that depend on virtual/daemontools; for example, the nullmailer test suite uses ipcserver. Fr

Re: runit patches to fix compiler warnings on RHEL 7

What about mandoc? The colour of this bikeshed is not up for debate. If you want man pages for skaware, provide me with: 1. a reasonable source format (e.g. not roff, so mandoc is right out) 2. a tool that can be built using *only* a C compiler (so as to keep bootstrapping skaware easy), that c

Re: runit patches to fix compiler warnings on RHEL 7

Reading more, it seems the answer is yes: Our replies crossed. Glad you found what you needed in the doc. :) -- Laurent

Re: s6 usability (was: runit patches to fix compiler warnings on RHEL 7)

sure, that was just an idea for Jan, he could just create a dir somewhere, populate it with symlinks he prefers to the original s6 tools and put this dir in front of the PATH when running s6 since it seems the utilities do not bother under what name they run. Right, but I've heard enough people

Re: runit patches to fix compiler warnings on RHEL 7

OK, great! I just sent my patch series in a separate reply. I'm happy to have a tech discussion about it, and I could possibly change the patch series based on the discussion, or if it is determined that my patch series should not be accepted, I would accept that as well. Eh, "fix old compil

Re: s6 usability (was: runit patches to fix compiler warnings on RHEL 7)

Would it be acceptable to you and them to put the binaries in /bin/s6 and then very early in the boot add /bin/s6 to the path? This isn't a lot different from what djb did with /command, except it's not off the root, which everyone seems to hate. s6 binaries aren't a problem for Debian; but a

Re: s6 usability (was: runit patches to fix compiler warnings on RHEL 7)

the solution here could be a simple symlink to the original s6 tool without the prefix if you prefer (maybe even located in an other dir than /bin). That would be a decision for users, not software authors - else it would defeat the point of not invading the namespace. Daemontools is still aroun

Re: The "Unix Philosophy 2020" document

Friendly reminder that: - systemd discussion, even criticism, is off-topic, unless it's a deep technical analysis of a part of systemd and whether or not implementing equivalent functionality would be relevant to supervision systems. If you want to rant against systemd, it's certainly a heal

s6 usability (was: runit patches to fix compiler warnings on RHEL 7)

As a relatively new convert to supervision software, my reasons for preferring runit over s6 are, in order of priority: Hi Jan, Thank you a lot for this feedback. This is very useful UX return. Let me address the points one by one. 1) Debian ships with a working and maintained runit-init p

runit or s6 (was: runit patches to fix compiler warnings on RHEL 7)

For submitting patches, I'd recommend working with the Void Linux project. They can be found at #xbps on Freenode IRC. Void Linux has used runit as their init system for the past 5 years: Their implementation is very reliable and mature. Yes, but OP wants to fix compiler warnings on RHEL7. Do yo

Re: runit patches to fix compiler warnings on RHEL 7

I am reluctant to bring this up because I am not a neutral third party, but this is frankly a conversation that needs to be had. - This mailing-list accepts all discussions about process supervision software. It also accepts patches to such software (but rather than cold sending patches, pleas

Re: s6-log can create current with 640?

Not quite. People find uses for these things, and as the SUS rationale points out, for every potentially useless external equivalent of a (non-special) built-in command someone has come up with an arcane actual use for it. Even "cd". Oh, definitely. And if my bathtub had a built-in trumpet,

Re: s6-log can create current with 640?

A little bit more thought has resulted in a generic script which can implement any of the useless POSIX-required ``regular shell builtin'' Yeah, so it's another one of those functions that only make sense as shell builtins but that are still also implemented as external commands. Beats me why sy

Re: s6-log can create current with 640?

I'd mistakenly assumed execlineb knew where its friends were; though in hindsight its a bit much to assume that execlineb internally changes the PATH. The real question is, why is there a "umask" binary that's not the one from execline? Non-chainloading non-builtin umask is nonsense, just like n

Re: s6-log can create current with 640?

My initial attempt #!/usr/local/bin/execlineb -P s6-setuidgid uucp redirfd -r 0 /services/ntp/fifo umask 037 /usr/local/bin/s6-log -b n14 r7000 s10 S300 !"/usr/bin/xz -7q" /var/log/ntpd Hi Dewayne, - Is there a reason why you're using a manually created fifo instead of the built-in l

Re: qmail.org down?

Is qmail.org down? Is it down forever? Is it down & out? Unfortunately, it looks down forever. netqmail.org is alive, though - but I don't know whether the list of qmail patches is available somewhere. The qmail list would probably know. ;) -- Laurent

[announce] skarnet.org September 2019 release

Hello, New versions of all the skarnet.org packages are available. (This only concerns software that already has a numbered release. Packages that are git-only because they are not complete enough to warrant an initial release yet, such as bcnm, have been updated in git, but are not mentioned h

Re: chpst -u and supplementary groups

Yes. Apparently everyone re-implementing daemontools does something like this. So that brings me back to my original question: is there consensus that the historical behaviour is a bug? Or are there valid use cases¹? I don't think the historical behaviour is a *bug*, because the historical beha

Re: s6-linux-init: Actions after unmounting filesystems

Simply excluding filesystems doesn't help when the root filesystem is on one of these devices that needs teardown actions after being unmounted. In that case, the only workable solution is to have PID1 pivot_root() to a tmpfs with the teardown/reboot tools in it. That way you can actually fully un

Re: s6-linux-init: Actions after unmounting filesystems

Sorry if I read this thread too hastily, but why not just keep /proc etc mounted, as was seemingly the way with s6-linux-init <=v0.4.x.x (and therefore slew)? Since the asymmetry is by nature, simply respecting it appears to be one minimalist way. The umount command basically performs a "umount

Re: s6-linux-init: Actions after unmounting filesystems

There are certain setups that require doing something after filesystems are unmounted. Two examples are LVM logical volumes and LUKS encrypted volumes, but I suppose there must be more cases. In any such setup, the shutdown sequence would include a 'vgchange -a n' command or 'cryptsetup close' com

Re: A better method than daisy-chaining logging files?

Thanks Pica. I've sent the ktraces to Laurent and will update when possible. Please send your mails to the mailing-lists, not to me personally. I'm not always available for help, but other people on the mailing-list may be. For large files (such as traces), you can pastebin them somewhere, a

Re: A better method than daisy-chaining logging files?

FYI: The fifo queue permissions, which the jail sees pr---w 1 mylogger www 0B May 31 13:27 apache24-error| Ah, so the www group is the one that writes to the fifo. Got it. Then you don't need mylogger to belong to the www group (and it's probably better for privilege separation that i

Re: A better method than daisy-chaining logging files?

# s6-svc -a /run/scan/apache24-error-log The result is a directory containing -rw-r--r-- 1 mylogger www 0B Jun 17 15:34 state -rw-r--r-- 1 mylogger www 0B Jun 17 15:34 lock -rwxr--r-- 1 mylogger www 329B Jun 17 15:34 previous -rw-r--r-- 1 mylogger www 0B Jun 17 15:34 current

Re: [Announce] s6.rc: a distribution-friendly init/rc framework

Assuming the number of syslog logging scripts is fairly small (a few for daemons in an anticipated list, and perhaps one for the rest; I think this scheme is actually already in use by most syslog users), what about setting up a group of s6-log consumer services, and use a chainloading program

Re: A better method than daisy-chaining logging files?

I just attempted to link an apache24 instance to its log files via a bundle, which isn't acceptable to s6-rc-compile. The approach attempted was to chain: 1. apache24 (longrun) and is a producer-for apache24-log 2. apache24-log (bundle) is a consumer-for apache24, with contents, the following, tw

[announce] s6-linux-init-1.0.1.0

Hello, Following some UX reports in the #s6 IRC channel, a new version of the s6-linux-init package is out. * s6-linux-init-1.0.1.0 - - Binaries have less restrictive permissions. Root-only binaries are now readable (though still not executable) by normal users. - A

Re: where is the right place to run s6-rc from ?

but when using such a catch-all logger to log s6-svscan's own output there is no need for the "rc" service to have its own logger since everything it outputs goes into this catch-all logger. That's the end goal. That's what s6-linux-init-1.0.0.0 does. What you call the "rc" service is named "run

Re: killall test run

That seems to be the route that Adélie has taken. With an execline script, /lib/s6/s6-svscanboot, configured in an /etc/inittab 'respawn' entry. This results in a supervised s6-svscan (by sysvinit), and a supervised catch-all logger. Yes. I am also currently working on integrating s6-linux-init

Re: Managing difficult log files

So an intermediate reader appears to be a sound workaround. Does anyone have a better solution than ErrorLog “|'execlineb –Pc fdmove 1 0 s6-fdholder-retrieve /s/live/servicedirs/s6rc-fdholder/s ‘pipe:s6rc-w-final-logger’ fdswap 0 1 sh -c "read X; echo ${X}" 1. "cat" should work instead of your

Re: emergency IPC with SysV message queues

Please stop breaking threads. This makes conversations needlessly difficult to follow, and clutters up mailboxes. i do that intentionally since i find the opposite easier to follow. that leads often to complaints on other lists aswell. Oh? And the other complaints haven't given you a clue? We

Re: interesting claims

The Question: As a newbie outsider I wonder, after following the discussion of supervision and tasks on stages (1,2,3), that there is a restrictive linear progression that prevents reversal. In terms of pid1 that I may not totally understand, is there a way that an admin can reduce the system ba

[announce] s6-linux-init-1.0.0.0

Hello, A new version of the s6-linux-init-package is out. * s6-linux-init-1.0.0.0 - - It is a complete rewrite, and very different from the 0.4 series. - The s6-halt, s6-poweroff and s6-reboot commands have disappeared. - The s6-linux-init-maker remains; it has the

Re: what init systems do you use ?

The signal used to request a configuration reload from sysvinit is SIGUSR1 if I recall correctly It must have been SIGHUP (at least in sysvinit-2.88dsf), which reloads /etc/inittab. SIGUSR1 only closes and reopens /dev/initctl. :) -- Laurent

Re: race condition in killall

However, both sysvinit's and BusyBox's kilall5 make a kill(-1, SIGSTOP) call before going through the PID list and selectively sending the requested signal (and I guess Linux does not deliver SIGSTOP to the process that contains the call, or it would be pointless), and make a kill(-1, SIGCONT) cal

Re: emergency IPC with SysV message queues

Please stop breaking threads. This makes conversations needlessly difficult to follow, and clutters up mailboxes. Your mailer certainly has a "Reply" or a "Reply to group" feature, that does not break threads; please use it. that is wrong. just read the msg queue when a signal arrives (say S

Re: SysV shutdown util

you need to be able to convey more information to pid 1 than a few signals can. such as ? what more information than the runlevel (0 or 6, maybe 1 to go into single user) does SysV init need to start the system shutdown ? The time of the shutdown. The "shutdown" command isn't necessarily inst

Re: ipc in process #1

IMO process #1 should be solely signal driven. i guess there is no need for further ipc by other means, escpecially for those that require rw fs access to work (eg fifos, unix sockets). The devil is in the details here. Theoretically, yes, you're right. In practice, only using signals to cont

Re: s6-log problem with +regex

However without any control directive, the result is: s6-log: usage: s6-log [ -d notif ] [ -q | -v ] [ -b ] [ -p ] [ -t ] [ -e ] [ -l linelimit ] logging_script Though running s6-log without a control directive is probably a little silly, perhaps the requirement to have one may be worthwhile m

Re: s6-log problem with +regex

Thank-you for s6-rc and friends. I came across two items: 1. the s6-log in testing requires a control directive. In my testing without a T, t, n $VALUE for example, the s6-log command failed. "s6-log 1", which does nothing but send stdin straight through to stdout, works for me on both Linux an

Re: how to handle system shutdown ?

but one can do without it and call the shutdown script by hand which in the end does the reboot(2) call itself, thats perfectly possible and the classical BSD way, so process #1 does not even need to do the system shutdown itself. That's relying on a behaviour that Linux implements, and possibl

Re: interesting claims

So Laurent's words from http://skarnet.org/software/s6/ were just part of a very minor family quarrel, not a big deal, and nothing to get worked up over. This very minor family quarrel is the whole difference between having and not having a 100% reliable system, which is the whole point of supe

Re: further claims

haven't you claimed process #1 should supervise long running child processes ? runit fulfils exactly this requirement by supervising the supervisor. Not exactly, no. If something kills runsvdir, then runit immediately enters stage 3, and reboots the system. This is an acceptable response to t

Re: interesting claims

"suckless init is incorrect, because it has no supervision capabilities, and thus, killing all processes but init can brick the machine." a rather bold claim IMO ! where was the "correct" init behaviour specified ? where can i learn how a "correct" init has to operate ? For instance: https://ar

Re: ezmlm mail headers

there is a "problem" when ezmlm meets gmail: There's much more than one problem ^^" It's difficult for gmail and mailing-lists to coexist. People using gmail regularly get unsubscribed because gmail fails to answer probes several times in a row. It's a pain, and there's not much I can do abou

Re: catch-all logger service

it should not be to much of an effort to add this functionality to s6-svscan (and perp(d) for that). You need to be able to take "no" for an answer. -- Laurent

Re: s6 style "readiness notification" with perpd

how is that ? what if 2 services (non-interdependent, to be started concurrently) specify/use the same fd (number) to write their readiness notification message to ? how could perpd tell which of the 2 nofied it ? It doesn't matter what the number is that the service sees. As long as perpd crea

Re: s6-svscan catch-all logger service

i think this feature does not require too much "ad-hoc" C code in the svscan source. it is easy to do that in C while it becomes hard to impossible do write a shell script that does it (ok, in execline this seems to be possible, but you need that package installed then). You need to have execl

Re: s6-linux-init-1.0.0.0 (was: special s6-svscan/perp(d) catch-all logger service option)

I saw this a couple of days ago in the Git repository. So, what's your stance on the (soon to be) 'old' execline stage1, stage3 and .s6-svscan/SIGxxx files approach? Will you consider it deprecated, or just an alternative to the s6-linux-init-1.0.0.0 approach? Are the version 0.4.0.1 s6-linux-init

Re: s6 style "readiness notification" with perpd

does s6-supervise listen to the given "readiness notification" fd ? seems so to me. Yes, it does. that is the reason s6 style "readiness notification" would be hard to do directly with perpd since it is a more integrated solution that does not use intermediary supervise processes. It would

Re: special s6-svscan/perp(d) catch-all logger service option

hello, i am a new subscriber to this mailing list. Hi Jeff, and welcome! i saw that daemontools-encore svscan provides an option to specify a special catch-all logging service for svscan and its child supervise processes: (...) it would be very nice for s6(-svscan) and perp(d) to provide suc

[announce] skarnet.org March 2019 release

Hello, New versions of all the skarnet.org packages are available. (This concerns only software that already has a numbered release. Packages that are git-only because they are not complete enough to warrant an initial release yet, such as bcnm, have been updated in git, but are not mentioned

Re: Generic interrupt command?

That's a tough call. On the one hand, it makes simple constructs safer. On the other, it adds complexity to interpreting the data programmatically ( the test / [ program errors for integer comparisons with text, and using scanf() to pull in the values for libc style programs wouldn't be so simp

Re: s6 bites noob

just take this as a data sample for what can happen when a random noob tries to use s6. Although unpleasant (not gonna lie), it was a very useful user experience report, thank you. Among other things, it comforts me in the belief that a user interface layer on top of s6 + s6-rc + s6-linux-init

Re: Generic interrupt command?

Not outputting anything causes kill (on my system at least) to exit non 0 Not outputting anything isn't an option, for the case where -o pid is used in addition to other fields. The field number and order must be respected. It's probably best to use some OOB indicator. How about NA, which I a

Re: Generic interrupt command?

Be careful, though. If the service is down, kill will use -1 for the PID, and will probably signal everything in your system except PID 1. That's a good point. Should s6-svstat use 0 as the "service is down" pid value instead, to avoid this ? -- Laurent

Re: s6 bites noob

But run not existing when supervise starts is a different case from run disappearing after supervise is already running. No, it's not. First, s6-supervise starts and initializes the state of the service to "down, wanted up" (unless there's a ./down file in which case the service isn't wanted

Re: s6 bites noob

s6-supervise aborts on startup if foo/supervise/control is already open, but perpetually retries if foo/run doesn't exist. Both of those problems indicate the user is doing something wrong. Wouldn't it make more sense for both problems to result in the same behavior (either retry or abort, pref

Re: Is s6/s6-rc ready to be the ubiquitous init?

1) Where can I find the s6/s6-rc project's preferred directories for everything? If there is *one thing* you should know about s6, and that you should convey to your readers, it is that *it does not provide, or care about, policy*. I thought it would be abundantly clear by now. That means th

Re: Generic interrupt command?

I think a cool addition to runit program sv and s6's s6-svc would be a command to send an arbitrary signal to the daemon being supervised. Yes, that would be a nice feature. I've been thinking about it for some time. Unfortunately, that's not at all suited to the way the control program communic

Re: How best to ensure s6-managed services are shut down cleanly?

I _think_ that with my naive current setup, what actually happens is: - systemd sends a SIGTERM to s6-svscan; - s6-svscan sends a SIGTERM or SIGHUP to all s6-supervise processes, depending on what they are supervising, and then runs the finish program; - the s6-supervise for postgresql sends a

Re: s6 bites noob

s6-svc -wu -u serv/foo/ will start it, but never exits. Likewise, s6-svc -wd -d serv/foo/ will stop it, but never exits. Now that is probably due to your setup, because yours is the only report I have of it not working. Update: just tonight I received another report of the exact same symptom

Re: s6 bites noob

mkdir test s6-svscan --help Well, that was surprising and unpleasant. It ignores unknown arguments, blithely starts a supervision tree in the current dir (my home dir), and spams me with a bunch of supervise errors. Ok, kill it. Next test: s6-svscan test Do you always run programs you don't k

Re: s6 problems logging

Yup, I get a log message to the console when I send an email. Try stracing doorknob: "strace -v -s 256 /usr/sbin/doorknob -fs" in your run script. Check that the messages it's sending to its stdout are properly terminated with a newline or null character. (Messages sent to the console will appea

Re: Is s6/s6-rc ready to be the ubiquitous init?

Months ago IBM bought Redhat, and IBM might not want to throw a million a year at a dev group devoted to keeping the systemd leaky boat afloat. Meanwhile, just today another major systemd snafu emerged. I think you're deluded if you think systemd's going away by a top-down decision. Corporate li

Re: Can s6 be enough?: was s6-ps

When Debian acquires a properly working s6-rc package, the answer to my question degenerates to "why not?" But for now, for the Debian person who only installs via package, s6-rc is out of the question, so my question was, isn't s6 itself good enough? Then maybe you should ask Debian instead, "

Re: Can s6 be enough?: was s6-ps

Eliminate dependency on udevd from oneshot startup scripts. One example among others: Kernel events are used to automatically load dynamic kernel modules. Say you need to mount a filesystem of a type that's not known in your core kernel, but you have a module for that. Either you manually modpr

Re: s6-ps

- The execline library is required to build a few of s6's utilities (typically: s6-ftrig-listen). - The execlineb binary is required for use of the !processor directive in s6-log. - Some of the other binaries provided by execline are used by s6 utilities, for instance s6-fdholder-store. "Re

Re: Can s6 be enough?: was s6-ps

Everybody appreciates the preceding two features, but personally, I don't think they're absolutely necessary. Runit has neither, yet it works just fine for most things. It really depends on what "most things" are. Small, server-only appliances? sure. Distributions where you can start all the one

Re: s6-ps

It occurs to me that s6-ps would gain from having an "exe" column. That functionality: - isn't available in procps. I modelled the available columns from procps' ones. Although that doesn't mean much, because there are many more columns available now in recent versions of procps than there are

Re: Log rotation issue with runit

Why would it be wrong to just keep appending to `current' instead of moving it to `.u' file? (see my patch at end of bug thread) On a crash, it is possible that a file you're writing to gets corrupted. For the integrity of your logs, it's better to move that potentially corrupted file to another

Re: More Answers

* https://unix.stackexchange.com/a/489949/5132 This may be of interest to people looking for some (brief) comparative analysis. Including the further reading. (-: Thanks for the heads-up! I posted an answer in complement to yours. We really need to settle on some terminology. I don't like

[announce] skarnet.org Summer 2018 release

Hello, New releases of some skarnet.org packages are available, as well as a new package. * skalibs-2.7.0.0 --- This is a major version release of skalibs, so compatibility with previous versions is not guaranteed. Make sure to also upgrade the rest of the skarnet.org stac

Re: s6-rc live state and database format upgrades

* s6-rc-format-upgrade was called with a compiled database that is not the exact 0.4.0.x equivalent of the one currently associated with the live state directory (i.e. other that a database created with s6-rc-compile from version 0.4.0.x and the exact same service definitions). It would probabl

Re: [RFC] prctl: (Please do not!) Deprecate non PR_SET_MM_MAP operations

The subject of deprecating and removing the API that permits this came up recently on the Linux Kernel Mailing List. I raised my concerns, and the Linux Kernel developers have been laudably responsive on the subject. As I said to them, I would welcome a better API, that allows setting these t

[announce] execline-2.5.0.0

Hello, execline-2.5.0.0 is out. It is with a very heavy heart that I must do this release. User reports have come in by the hundreds and they are almost unanimous (sorry, Colin): they don't like the 2.4.0.0 change, pretending it hurts readability (as if), and writability too, of execline scr

[announce] execline-2.4.0.0

Hello, execline-2.4.0.0 is out. As you all know by now, the main obstacle to adoption of skaware by distributions and mainstream Unix folks is the user interface; so, the obvious next improvements to skarnet.org software is to provide interfaces people are comfortable with. This is true for s

Re: [announce] skarnet.org Spring 2018 release

* s6-2.7.1.0 -- Make that s6-2.7.1.1, since a stupid (non-critical, but annoying if you prefer your warnings to be displayed when something goes wrong rather than when things work normally) made it through. ^^' -- Laurent

[announce] skarnet.org Spring 2018 release

Hello, New releases of some skarnet.org packages are available. * skalibs-2.6.4.0 --- - Bugfixes. - Several new functions, including a small FIFO library for generic object queues (genqdyn.h). https://skarnet.org/software/skalibs/ git://git.skarnet.org/skalibs * A ne

Re: [Announce] s6.rc: a distribution-friendly init/rc framework

On a second thought, what about (at least a attempt at) solving the human (political) problems by human means (propaganda, but of the factually correct type)? It's not a political problem, it's a religious problem. You just cannot convince people that your UI is better, any more than you can co

Re: [Announce] s6.rc: a distribution-friendly init/rc framework

In their defence, I don't think any mainstream distribution makes this kind of modifications easy. IMO it's safe to assume a new init system means a new distribution (possibly derived from something larger). And that is why I intend to start with smaller, more flexible, less inertia-driven dist

Re: [Announce] s6.rc: a distribution-friendly init/rc framework

What about using "slew.rc" and changing the installation path from `/etc/s6' to `/etc/slew'? That's all fine with me, but it may have connotations in English that you don't want to associate with a project aimed at stability and friendliness :) To be honest, I find the idea not very appealin

Re: [Announce] s6.rc: a distribution-friendly init/rc framework

s6.rc [1] is an attempt to bridge the gap between the elegant foundation provided by s6/s6-rc and an init/rc system that implements the main functionalities beneficial for distributions. s6.rc features a preprocessor that generates source directories for use with s6-rc from given templates. The p

Re: Compatibilities between runit and s6 (re: Incompatibilities between runit and s6?)

You have prompted me to fill in a long-standing dangling hyperlink. * http://jdebp.eu./FGA/slashpackage.html If I may add my two cents: I think you're mixing two very different things in this page. There is the slashpackage convention for installed packages, i.e. visibility of executables in

Re: Compatibilities between runit and s6 (re: Incompatibilities between runit and s6?)

Note that s6 has been using a configure/make/sudo make install building scheme since 2014, and supports FHS as well as slashpackage, so it can be easily packaged for any distribution. :P -- Laurent

Re: Incompatibilities between runit and s6?

Thanks. I would rather you write one small unit file then me needing to write ten or fifteen of them. Done. https://skarnet.org/software/s6/s6-svscan-not-1.html#systemd I did not follow Jonathan's suggestion to use a .path unit file, because the other examples on this page assume that the sc

<    1   2   3   4   5   6   7   >