<emmett1>
farkuhar: why not rewrite rc script in posix?
<emmett1>
avoid bashism
<emmett1>
so using CRUX is not stricly required bash installed
zorz_ has joined #crux-musl
<SiFuh_>
emmett1: I agree, but everything is written in bash
<emmett1>
SiFuh_: yeah pkgmk
<emmett1>
i just thought maybe we should ship ksh as default shell in CRUX-MUSL, but everything is tied with bash
<SiFuh_>
emmett1: I have re-written the rc scripts. Now I am slowly intergrating all into one rc to get rid of rc.shutdown, rc.multi, rc.single
<SiFuh_>
I have not bothered with the gay colour stuff. But I have left it open for future addition
<emmett1>
nice. wheres the source?
<emmett1>
i could write mine too
<emmett1>
SiFuh_: does *BSD has colours on boot?
<SiFuh_>
Nope. Only the blue background and white text from the kernel only. The rc scripts are not in colour
<emmett1>
then i dont think we need colour at all
<emmett1>
just keep it simple
<SiFuh_>
Me too.
<emmett1>
why not focus make it better instead of make it colourful. which is looks gay. not BSD at all.
zorz_ has quit [Quit: leaving]
<farkuhar>
dlcusa: "Good, cheap, fast" <- These are meant to describe the production process, not the finished product. With good and cheap that's not much of a distinction, but when it comes to fast, a startup script can boot the system rapidly (finished product) even if its author took a long time to deliver (production process).
<farkuhar>
So regarding your claim that we already expected /etc/rc to be fast and good, that seems to be applying the standards to the finished product. Anyway, we can still aim for perfection in whatever we propose to jaeger and jue, simply by ignoring the dictum about having to jettison one of the three measures (a dictum that only applies when the production is being done on contract with an external client).
<farkuhar>
It's a bit of an oversimplification to describe the production process using only three dimensions (quality, cost, and time to delivery). While those three dimensions are of greatest concern to a business executive, a project made up of volunteers (who aren't getting paid for their labors) can consider other aspects of the production process and the finished product.
<SiFuh_>
farkuhar: I was thinking about rc.functions
<dlcusa>
farkuhar, you are, of course, correct regarding the standard application, intended as what a vendor asks his customer--cheap means the cost to the customer, good means the quality (conformance to specifications, including the quality of the specifications themselves), and time being how long the customer must wait for delivery. I, however, was applying that old saw to the free software coder and the user of his software, not
<dlcusa>
the intended application. Kindly allow some imperfections in the interest of making it, dare I say, pithy. :-)
<SiFuh_>
Pithy Linux
<SiFuh_>
farkuhar: alright. I think will send it to emmett1 for testing
SiFuh has quit [Remote host closed the connection]
SiFuh has joined #crux-musl
<farkuhar>
I tried to buy us some time by replying with https://git.crux.nu/tools/rc/issues/1#issuecomment-619 , after jue suggested creating a PR. Eventually they'll want something stable that they can review. So please post the latest version of SiFuh's rc scripts, and I'll take them for a test drive too.