General TC > Tiny Core in Containers

TinyCoreLinux 13.x docker container on x86-64

<< < (2/2)

Rich:
Hi rhermsen

--- Quote from: rhermsen on October 28, 2024, 03:46:54 PM --- ... Suspect background a process didn't work.
--- End quote ---
What you have done is block the completion of tc-config until bootlocal.sh completes.

Some things don't belong in bootlocal.sh, kmaps for example. This explains why and
describes the timing of events:
https://forum.tinycorelinux.net/index.php/topic,23698.msg148996.html#msg148996

The blueman.tcz.info suggests bluez should be started before a GUI:
https://forum.tinycorelinux.net/index.php/topic,25702.msg164798.html#msg164798

When it comes to automatically starting programs, scripts, daemons, etc., the basic rules of thumb are:
1. Things that need to run before a GUI are started (like kmaps) should go into  /opt/bootsync.sh.
2. Things that need to run after a GUI are started (like starting a GUI app) should go into  ~/.X.d.
3. Things that are not sensitive to when they are started can go into  /opt/bootlocal.sh  which runs in the background.

When starting something from numbers 1 or 3, you need to specify a full path. They run before any user is logged in.

Item 2 is unique to each user.

rhermsen:
Hi Rich,
Thanks for all the info. Will keep this for reference...

Tested with just 'touch /tmp/bootlocal_started' in /opt/bootlocal.sh
and 'touch /tmp/bootsync_started' in /opt/bootsync.sh.

After boot I only see 'bootsync_started' in /tmp.

No idea why background a process is not working during bootup.
And indeed understand it is blocking the completion of the lines in tc-config following bootsync.sh if '/opt/bootlocal.sh' is not a background process.

After bootup 'sudo /opt/bootlocal.sh &' is normally working.

Navigation

[0] Message Index

[*] Previous page