/run instead, there's no need for a separate script.
Sure - ./finish is obvious - but there are reasons for
`./sth-to-be-started-once`,
so I wanted to know whether there is something and I'm unable to find it or
it's intentionally left out compared to daemontools-encore ;)
Cheers
--
Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
> Am 01.02.2021 um 13:20 schrieb Crest :
>
> On 01.02.21 12:59, Jens Rehsack wrote:
>> Hi,
>>
>> I'm struggling to figure out how to start a particular initialization when a
>> service first comes up (since service startup, system startup, or ever).
>&g
does with ./start seems pretty ok - and would be near
perfect if it were to wait for ./start to finish before running ./run.
s6 has a concept for ./finish - so I think a ./start concept is there as well
and I just can't find it. Can someone please nudge me on this?
Cheers
--
Jens Rehsack - rehs
This device won't disappear until someone manually extracts the BMC
mechanically from the machine or the BMC breaks (which causes power loss
anyway, so doesn't matter ...).
Best regards
--
Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
> Am 24.03.2020 um 17:07 schrieb Jens Rehsack :
>
>> Am 24.03.2020 um 13:30 schrieb Laurent Bercot :
>
>> I pushed a fix to the s6 git head, please tell me if it's working for
>> you.
>
> I have to fixup some dependencies in my build-infrastructure today,
>
o the s6 git head, please tell me if it's working for
> you.
I have to fixup some dependencies in my build-infrastructure today,
might become tomorrow before I can report.
Cheers
--
Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
Description: Binary data
Best regards
--
Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
link: (cd ".libs" && rm -f "libtest.so" && ln -s
> "libtest.so.1.0.0" "libtest.so")
> libtool: link: ( cd ".libs" && rm -f "libtest.la" && ln -s
> "../libtest.la" "libtest.la" )
>
> The resulting commands are different.
And they're different when you're using pkgsrc at all, since
they use cc, gcc, c++, ld, ... wrappers which add/change
arguments on purpose.
Check your work.log for details.
Cheers
--
Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
> Am 04.12.2019 um 17:49 schrieb J. Lewis Muir :
>
> On 12/04, Jens Rehsack wrote:
>>> Am 04.12.2019 um 06:30 schrieb J. Lewis Muir :
>>> Your rationale for using /etc/ld.so.conf makes sense to me.
>>>
>>> However, at
>>>
>>> h
y
> don't want to depend on a feature like /etc/ld.so.conf since it is only
> available on a subset of the supported platforms.
It's probably just because Joerg Sonnenberger, J. Perkins etc. understand
the implications of careless installation of relocatable binaries
is like playing Russian roulette. Especially when the system
administration doesn't know nor understand the implications of that.
Or short: PkgSrc knows about the human error, most Linux distros just
ignore that - because any Linux user, admin, developer ... is brilliant
and always careful. Continuing that would result in a flame - so ... ;)
Just a personal opinion.
Cheers
--
Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
> Am 26.10.2019 um 03:53 schrieb Guillermo :
>
> El vie., 25 oct. 2019 a las 17:01, Jens Rehsack escribió:
>>
>>> [...]
>>> configure:2634: result: no
>>>
>>> As you can see, only the equivalent of a skarnet.org 'choose cl' is used
&g
rt flags to identify sdkroot (when it's specified, you're
definitively in a cross-compile environment) and sysroot (that
is the stuff you can count on during compile and run time).
* move sysdeps dir into $(includedir)/skalibs/sysdepds
Cheers
--
Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
agic. And do you know: nowadays CMake scripts are even
more ugly than autoconf, the do not distinguish between sysroot and
sdkroot, mix host, build and target paths, have even more magic
deeply hidden in CMake core.
Waf has a similar history. Perl5 configure - a nightmare ...
Anyway - as long as you as author invest your effort so quick
and that kind of solution oriented - who am I to throw carrots :)
Cheers
--
Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
ntropy_linux.c
sno@beaker:~/prj/libressl-3.0.2$ grep -Rl SYS_getrandom /usr/include/
/usr/include/bits/syscall.h
/usr/include/x86_64-linux-gnu/bits/syscall.h
/usr/include/x86_64-linux-gnu/expat_config.h
Seems, there isn't much need in probing at configure stage ...
> * report the thing to libc-
ross-arm/2.32.0-r0/git/ld/testsuite/ld-cris/globsymw1.s
* binutils-cross-arm/2.32.0-r0/git/ld/testsuite/ld-cris/warn3.d
* binutils-cross-arm/2.32.0-r0/git/ld/testsuite/ld-cris/globsymw2.s
* binutils-cross-arm/2.32.0-r0/git/ld/testsuite/ld-cris/warn4.d
confirms the smell ...
Cheers
--
Jens Rehsack - reh
nings ?
Not by default.
But the issue smells more as a glibc issue than an ld issue.
Just the first shot I'd follow when encountering such a one ...
Cheers
--
Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
> Am 18.10.2019 um 09:30 schrieb Jens Rehsack :
>
>
>
>> Am 17.10.2019 um 22:12 schrieb Laurent Bercot :
>>
>>> A reasonable detection in configure stage is definitively to prefer.
>>
>> Not necessarily. It would work, obviously, but would bloat
the other places, Hurd+skalibs users
> will simply have to avoid ricing their paths.
As last way out ...
In practice I never encountered FQPN longer than 160 characters.
Cheers
--
Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
h_max;
int
foo(...)
{
#ifdef PATH_MAX
char mypath[PATH_MAX];
#else
char *mypath = alloca(computed_path_max);
#endif
...
}
Yes, not 100% satisfying - but maybe a saner way out than
-DPATH_MAX=4096.
Cheers
--
Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
s document.
>
> Maybe that thing is missing: if somebody would like to build a modern
> UNIX: what are practical steps to achieve it?
>
> Which tools, which interfaces (kernel, userland) are needed?
Cheers
--
Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
> Am 17.09.2019 um 20:38 schrieb Jens Rehsack :
>
>
>
>> Am 17.09.2019 um 20:11 schrieb Laurent Bercot :
>>
>> On 9/14/2019 2:11 PM, Jens Rehsack wrote:
>>> I don't have such a database and such a database is imposible to have.
>>
>> Tha
> Am 17.09.2019 um 20:11 schrieb Laurent Bercot :
>
> On 9/14/2019 2:11 PM, Jens Rehsack wrote:
>> I don't have such a database and such a database is imposible to have.
>
> That's a real shame, because it's the *only way* cross-compilation
> can ever work.
&
22 matches
Mail list logo
