Recent Posts

61

TCE Bugs / Re: seatd & copy2fs.flg

« Last post by aus9 on January 25, 2026, 08:43:57 PM »

@Rich
I think I am going to re-look at using install script after all. But have no experience at this copy2fs.flg. I could not find it as a bootcode....https://distro.ibiblio.org/tinycorelinux/faq.html#bootcodes
so if I wanted to test my updated seatd....with whatever I build...where is this flag please? The PDF section 1.9 mentions this is a copy mode...but how do I test it please?

I did find mention of copy2fs.flg under /etc/init.d/tc-config/tc-config but that appears to suggest I have
Preload drivers needed for tce/opt/home on lvm/RAID etc.......which I do not have

alternatively.....after I test it my end which is mount mode with persistent home ....I could pm M-A-X ask him to move his current seatd somewhere safe , download my updated TCE and he can decide if my changes suit?

62

TCE Bugs / Re: seatd & copy2fs.flg

« Last post by aus9 on January 25, 2026, 06:10:07 PM »

16x early test results....not sure which desktop you are using.
I have dropped the install script entirely and info file will say something like
"If you see ..../run/seatd.sock, refusing to start....... then run $ sudo rm -rf /run/seatd.sock"

labwc and weston tested works as expected with....note I tend load lots
sudo seatd -g staff -n /run/seatd.sock & dbus-run-session labwc -s lxterminal
sudo seatd -g staff -n /run/seatd.sock & XDG_SESSION_TYPE=wayland dbus-run-session weston

woodland fails and will need a rebuild
sway....is not recognising our .profile change setting up the XDG_RUNTIME_DIR
so sway will need a rebuild as I launch sway with a ~/.local/bin/sw

Have not bothered to look at 17x until I fix and submit 16x first. Thanks for reading

63

TCE Bugs / Re: seatd & copy2fs.flg

« Last post by aus9 on January 25, 2026, 05:18:21 PM »

I have seen this post. The info files for labwc and weston are both ignoring my suid efforts by stating that members have to use sudo
Let me rebuild and drop all  SUID and re-test  for 16x and 17x.

I no plans to update 15x

64

General TC Talk / Re: Building Another Logger

« Last post by MTCAT on January 25, 2026, 02:33:55 PM »

Hi Rich,

Oh, okay, thanks for the explanation of what the extended partition is, didn't know that.

Bad news is, I think I wrecked my main backup pen drive with all the thrashing in the BIOS, I was having issues with the Quick Boot and Enhanced Boot and POST tests where it seemed that sometimes the pen drive would get completely missed and would end up booting in Lubuntu even, and other times, would hang halfway through booting TC (like before loading extensions even), and other times would hang at the vesamenu screen (to select regular or real time TC) after the 10 second count-down was complete (would hang at second 1), so with all this thrashing many times I couldn't shut down the computer properly, and I think it finally "bit" me.

Image below shows what I get now when I try to boot with my "primary" backup pen drive, I get an "input/output" error from /opt/bootsync.sh, I even went into /opt and tried to look inside bootlocal.sh, and some of the other scripts (with cat, and tail), and also got an "input/output" error. Also, my home directory, /home/tc is completely empty.


https://forum.tinycorelinux.net/index.php?action=dlattach;topic=27965.0;attach=7188


Luckily I have a second, almost complete backup pen drive, it's only missing the digitemp temperature sensor software. So that seems to be running okay and I think I'm done hacking on the BIOS now, it seems to be working okay, hopefully?, using the same settings as in the BASE and with the updated video BIOS for the PixelQi screen.

So I think I'm going to pull apart my BASE receiver anyway, and make about 6 copies of its boot pen drive, and can then also change out the U-Blox CMOS battery since that one has been in there for a couple of years already.

Thanks,

David

65

Release Candidate Testing / Re: Core v17.0beta1

« Last post by Juanito on January 25, 2026, 11:57:45 AM »

Any headway on xf86-video-vmware.tcz for 32-bit?

It was posted yesterday or the day before in the 16.x and 17.x repos

66

Release Candidate Testing / Re: Core v17.0beta1

« Last post by andyj on January 25, 2026, 10:53:45 AM »

Any headway on xf86-video-vmware.tcz for 32-bit?

Also, what is the -s option for /usr/bin/version for? It currently returns the same as -l and default.

If it was

Code: [Select]

s) echo "${RESULTS%%-*}" instead of

Code: [Select]

s) echo "${RESULTS##*_}" it would return just the major.minor version. Apparently it is meant for something else?

67

TCE Bugs / Re: seatd & copy2fs.flg

« Last post by Rich on January 25, 2026, 10:42:42 AM »

Hi M-A-X
Welcome to the forum.

... Root cause of the problem may be related to the seatd installation script which seems to be not compatible with the copy2fs.flg ...

Exactly correct. The  tce.install/  includes this:

Code: [Select]

# make SUID
rm -rf /usr/local/bin/seatd*
LOOP=/tmp/tcloop/seatd/usr/local/bin
cp $LOOP/seatd* /usr/local/bin
chmod a+s /usr/local/bin/seatd*
When using  copy2fs.flg  the extension does not get mounted to  /tmp/tcloop/seatd.
As a result, the  cp  command copies nothing to replace the deleted files.

I think confirming the files are symbolic links prior to deleting might be prudent, maybe
something like this:

Code: [Select]

# make SUID
LOOP=/tmp/tcloop/seatd/usr/local/bin
if [ -d "$LOOP" ]
then
    rm -rf /usr/local/bin/seatd*
    cp $LOOP/seatd* /usr/local/bin
fi
chmod a+s /usr/local/bin/seatd*
Maybe you should PM the extension maintainer aus9 and see
what he thinks.

68

Release Candidate Testing / Re: Core v17.0beta1

« Last post by Rich on January 25, 2026, 10:00:53 AM »

Hi aus9
Is this what you think is a problem:

...

Code: [Select]

----- Snip -----
tc@box:/tmp/tcloop/glibc_add_lib/usr/lib$ ls ../../lib/libmvec.so.1
../../lib/libmvec.so.1
 ----- Snip ----- ...

That's not a link. You prepended a relative path (../../) to the file name
you are looking for:

Code: [Select]

tc@box:~$ cd /usr/local/lib
# The relative path used in the  ls  command gets prepended to the result.
tc@box:/usr/local/lib$ ls ../../../lib/ld-linux-x86-64.so.2
../../../lib/ld-linux-x86-64.so.2

# Walk up the path and repeat
tc@box:/usr/local/lib$ cd ..
tc@box:/usr/local$ ls ../../lib/ld-linux-x86-64.so.2
../../lib/ld-linux-x86-64.so.2

tc@box:/usr/local$ cd ..
tc@box:/usr$ ls ../lib/ld-linux-x86-64.so.2
../lib/ld-linux-x86-64.so.2

# Even the forward slash gets prepended if included in the command.
tc@box:/usr$ cd ..
tc@box:/$ ls /lib/ld-linux-x86-64.so.2
/lib/ld-linux-x86-64.so.2

tc@box:/$ ls lib/ld-linux-x86-64.so.2
lib/ld-linux-x86-64.so.2
tc@box:/$

69

Release Candidate Testing / Re: Core v17.0beta1

« Last post by Juanito on January 25, 2026, 09:53:20 AM »

For me that's the correct way to do things - i.e. the symlink is relative:

Code: [Select]

/tmp/tcloop/glibc_add_lib/usr/lib$ ls -l libmvec.so
..libmvec.so -> ../../lib/libmvec.so.1
Maybe a problem with submitqc?

70

Release Candidate Testing / Re: Core v17.0beta1

« Last post by aus9 on January 25, 2026, 09:09:09 AM »

this is question on a TCE if I look at
http://tinycorelinux.net/17.x/x86_64/tcz/glibc_add_lib.tcz.list

SNIP
/lib/libmvec.so.1
SNIP
/usr/lib/libmvec.so

I am not sure the sym link is working correctly. Feel free to correct my inference

Code: [Select]

ls -al  /usr/lib/libmvec.so
lrwxrwxrwx 1 root root 44 Jan 25 21:20 /usr/lib/libmvec.so -> /tmp/tcloop/glibc_add_lib/usr/lib/libmvec.so

tc@box:/tmp/tcloop/glibc_add_lib/usr/lib$ ls -al libmvec.so
lrwxrwxrwx 1 root root 22 Dec 11 19:43 libmvec.so -> ../../lib/libmvec.so.1
tc@box:/tmp/tcloop/glibc_add_lib/usr/lib$ ls ../../lib/libmvec.so.1
../../lib/libmvec.so.1

# the real file
ls -al /lib/libmvec.so.1
lrwxrwxrwx 1 root root 42 Jan 25 21:20 /lib/libmvec.so.1 -> /tmp/tcloop/glibc_add_lib/lib/libmvec.so.1

submitqc is not seeing it a sym link...it claims that even though I have glibc_add_lib.tcz in the dep file
submitqc is still reporting I am missing libmvec.so.1
I am suggesting we have too many sym links ...that is the real file in ram drive is a sym link and then you have a sym link to a sym link. Maybe an install script to resolve?

thanks for reading