Tiny Core Extensions > TCE Talk

Request for ca-certificates

<< < (2/5) > >>

Juanito:
Sure, please go ahead  :)

Rich:
Hi andyj
ca-certificates updated in TC16 x86 and x86_64.
Please check one of them out and make sure it works correctly.

Paul_123:
For reference piCore already had


--- Code: ---[ -d /usr/local/etc/ssl/certs ] || mkdir -p /usr/local/etc/ssl/certs
--- End code ---

Although its a bit redundant, as it could have been fixed your way.  I'll change my scripts for the next time I update piCore.   Although packages like these are architecture independent.

andyj:

--- Quote from: Rich on December 08, 2025, 08:46:44 AM ---Yes, the openssl startup script is creating  /usr/local/etc/ssl/certs.

--- End quote ---


--- Code: ---Dec  8 20:09:07 www-vm authpriv.notice sudo:       tc : TTY=unknown ; PWD=/mnt/sr0/cde/optional ; USER=root ; COMMAND=/bin/mkdir -p /tmp/tcloop/openssl
Dec  8 20:09:07 www-vm authpriv.notice sudo:       tc : TTY=unknown ; PWD=/mnt/sr0/cde/optional ; USER=root ; COMMAND=/bin/mkdir -p /tmp/tcloop/ca-certificates
Dec  8 20:09:07 www-vm authpriv.notice sudo:       tc : TTY=unknown ; PWD=/mnt/sr0/cde/optional ; USER=root ; COMMAND=/bin/mkdir -p /tmp/tcloop/openssh

--- End code ---

The load order is right, but I get an error on the console saying the directory can't be found. The directory is there this time but it's empty. I don't have the updated ca-certificates extension, I'm waiting on mirrors. Could this be a race problem? When I run update-ca-certificates from the command line after it boots it works as expected.

Rich:
Hi andyj

--- Quote from: andyj on December 08, 2025, 03:20:46 PM --- ... Could this be a race problem? ...
--- End quote ---
It does sound like it. Kind of like when the kernel queues a write
until it's convenient to complete it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page