Hello,
About two years ago, there was some talk on the Busybox mailing-list
about the need for a version of "mdev" that would not use a separate
process for every uevent (as a hotplug manager does) but that would act
as a daemon, able to handle a series of uevents - typically read from
the net
Hi all,
I've been learning about s6 through the s6-overlay. What I would like to do is
take a .env file full of x=y lines and have that define env vars before running
a program. I suspect there is a clever and easy way to do that. However, I'm
not so clever. The best I've found so far is the s6
> #!/bin/sh
> exec env -i $(cat /path/to/xyz.env) /path/to/xyz
And of course you should be careful with the contents in `xyz.env'.
On Mon, Oct 23, 2017 at 01:30:57PM -0700, Monty Zukowski wrote:
> I've been learning about s6 through the s6-overlay. What I would like
> to do is take a .env file ful
On Tue, Oct 24, 2017 at 09:25:37AM +0800, Casper Ti. Vector wrote:
> > #!/bin/sh
> > exec env -i $(cat /path/to/xyz.env) /path/to/xyz
> And of course you should be careful with the contents in `xyz.env'.
>
You can do the same with
#!/bin/sh
while read A ; do
export "$A"
done < "$1"
exec prog..
I tried rewriting the whole thing in execline and while I'm pretty sure
it's doable it's not easy.
A direct translation of Casper's script to execline could be:
#!/command/execlineb -P
backtick LIST { cat /path/to/xyz.env }
importas -nsd"\n" LIST LIST
env -i ${LIST}
/path/to/xyz
It's not as
On Tue, Oct 24, 2017 at 06:22:46AM +, Laurent Bercot wrote:
> > I tried rewriting the whole thing in execline and while I'm pretty sure
> > it's doable it's not easy.
>
> A direct translation of Casper's script to execline could be:
>
> #!/command/execlineb -P
> backtick LIST { cat /path/to/
