66-update completes without issue as john

But as root:
66-update: info: save state of tree: boot-user
66-update: info: save service(s) list of tree: boot-user
66-update: info: update /run/66/tree/0/boot-user to: /tmp/boot-user:6GQVvU/boot-user
66-tree: info: Disabled successfully tree: boot-user
66-tree: info: Deleted successfully: boot-user
66-tree: info: Created successfully tree: boot-user
66-tree: info: Enabled successfully tree: boot-user
66-tree: info: Ordered successfully: boot-user starts after tree: root
66-update: info: enable service(s) of tree: boot-user
66-update: info: update db: /run/66/tree/0/boot-user to: /var/lib/66/system/boot-user/servicedirs/db/boot-user
s6-rc-update: fatal: unable to take lock on /run/66/tree/0/boot-user and /run/66/tree/0/boot-user/compiled: Device or resource busy
66-update: fatal: unable to update: /run/66/tree/0/boot-user to: /var/lib/66/system/boot-user/servicedirs/db/boot-user
After that action (at 16:36) the two paths list as:
john # ll /run/66/tree/0/boot-user
Permissions Size User Date Modified Name
lrwxrwxrwx    31 root 23 Nov 16:36  compiled -> /tmp/boot-user:6GQVvU/boot-user
.rw-r--r--     0 root 23 Nov 16:36  lock
.rw-r--r--    10 root 23 Nov 13:57  prefix
lrwxrwxrwx    17 root 23 Nov 13:57  scandir -> /run/66/scandir/0
drwxr-xr-x     - root 23 Nov 13:57  servicedirs
.rw-r--r--    10 root 23 Nov 13:57  state
john # ll /var/lib/66/system/boot-user/servicedirs/db/boot-user
Permissions Size User Date Modified Name
.rw-r--r--  2.3k root 23 Nov 16:36  db
.rw-r--r--     0 root 23 Nov 16:36  lock
.rw-r--r--    24 root 23 Nov 16:36  n
.rw-r--r--  2.7k root 23 Nov 16:36  resolve.cdb
drwxr-xr-x     - root 23 Nov 16:36  servicedirs
john #
So I have trees for boot, root and boot-user

`sudo 66-update root` is successful `update db: /run/66/tree/0/root to: /var/lib/66/system/root/servicedirs/db/root`

boot and boot-user fail. I'm assuming some difference in permissions between the root, boot and boot-user directories so will investigate.
Thanks for the advice. My dry runs were bullet proof & disassembly was my next thought.

But I've been accumulating cruft with every experiment since crossing to arch/66/s6 from debian world and I decided to take the other approach and build from fresh. It was also a good chance to test our how automatically yay would refill my system. Quite well actually. Hardest thing was that I couldn't find a good wine64 aur so I ended up compiling the source.

So whatever was wrong isn't with this one and I'll remember this thread should I have issues again, thanks.

Powered by Obarun