did I correctly update to TC16?

[Stefann]

Hi,
Please forgive me if I ask something overly simple.

With the release of TC16 I for the first time did a system update.
At this moment only at my "staging system" (a $15 H510 thin client),
my "production system" (home control system on even more ancient 500Mhz Via Eden single core processor) I will do only if I'm convinced all is ok.....

What I did:

Code: [Select]

- download the "Tiny Core, 23Mb x86" iso on my Macbook
- mount on my Macbook
- copied core.gz to TC system: /mnt/sda1/tce/boot/core16.gz
- copied vmlinuz to TC system: /mnt/sda1/tce/boot/vmlinuz16
- modified /mnt/sda1/tce/boot/extlinux/extlinux.conf:
>>> duplicated the profile I was using
>>> changed core.gz to core16.gz & vmlinuz to vmlinuz16 for the duplicated profile
>>> set the duplicated profile as  "default boot" in extlinux.conf

reboot --> works!!!

Than used the apps tool (I used the GUI version over VNC) and asked to update extensions, I all updated them.
Note:
I get a load of "Error could not verify ._####.tcz (with ### being multiple filenames)
I checked on my "production system" still on TC15 and it does the same so its not related to upgrade

Tested GUI over VNC, SSH, Samba, gcc, python >> all works
Soooo.....
1/ looks like it works
2/ little concern on the "could not verify errors" but as they are the same on my TC15 system that runs like a charm since summer 2024 I don't feel extremely alarmed (but it would be nice to be able to run update without all those errors)

3/....... is this a correct way?
>> I did not use the other files on the iso >> is that bad? did I miss something?

[Juanito]

Are you using the same tce folder?

It sounds like you have some extensions present locally that are no longer present in the 16.x repo.

[Stefann]

Thanks,

on TC16 I get:

Code: [Select]

Error Could not verify ._Xlibs.tcz
Error Could not verify ._Xprogs.tcz
Error Could not verify ._Xvesa.tcz
Error Could not verify ._aterm.tcz
Error Could not verify ._bzip2-lib.tcz
Error Could not verify ._fltk-1.3.tcz
Error Could not verify ._flwm.tcz
Error Could not verify ._freetype.tcz
Error Could not verify ._imlib2-bin.tcz
Error Could not verify ._imlib2.tcz
Error Could not verify ._libICE.tcz
Error Could not verify ._libSM.tcz
Error Could not verify ._libX11.tcz
Error Could not verify ._libXau.tcz
Error Could not verify ._libXcursor.tcz
Error Could not verify ._libXdmcp.tcz
Error Could not verify ._libXext.tcz
Error Could not verify ._libXfixes.tcz
Error Could not verify ._libXfont.tcz
Error Could not verify ._libXmu.tcz
Error Could not verify ._libXrender.tcz
Error Could not verify ._libXt.tcz
Error Could not verify ._libfontenc.tcz
Error Could not verify ._libjpeg-turbo.tcz
Error Could not verify ._libpng.tcz
Error Could not verify ._libxcb.tcz
Error Could not verify ._wbar.tcz
Error Could not verify linux-6.6_api_headers.tcz
Error Could not verify usb-serial-6.6.8-tinycore.tcz

but on the original TC15 I get:

Code: [Select]

Error Could not verify ._Xlibs.tcz
Error Could not verify ._Xprogs.tcz
Error Could not verify ._Xvesa.tcz
Error Could not verify ._aterm.tcz
Error Could not verify ._bzip2-lib.tcz
Error Could not verify ._fltk-1.3.tcz
Error Could not verify ._flwm.tcz
Error Could not verify ._freetype.tcz
Error Could not verify ._imlib2-bin.tcz
Error Could not verify ._imlib2.tcz
Error Could not verify ._libICE.tcz
Error Could not verify ._libSM.tcz
Error Could not verify ._libX11.tcz
Error Could not verify ._libXau.tcz
Error Could not verify ._libXcursor.tcz
Error Could not verify ._libXdmcp.tcz
Error Could not verify ._libXext.tcz
Error Could not verify ._libXfixes.tcz
Error Could not verify ._libXfont.tcz
Error Could not verify ._libXmu.tcz
Error Could not verify ._libXrender.tcz
Error Could not verify ._libXt.tcz
Error Could not verify ._libfontenc.tcz
Error Could not verify ._libjpeg-turbo.tcz
Error Could not verify ._libpng.tcz
Error Could not verify ._libxcb.tcz
Error Could not verify ._wbar.tcz
So: I guess TC16 has 2 applications "no longer in 16.x repo": linux-6.6_api_headers.tcz & usb-serial-6.6.8-tinycore.tcz
(kind of sad because I use the usb-serial package, the other is probably a dependancy)
But anyways.... that's a very understandable thing.

The bigger thing:
"where do all the ._lib****.tcz errors come from?"
"and a couple of "non lib" but still ._***.tcz errors"
Those are already present on TC15

Note:
I did install TC15 for 1st time last summer. It succeeded after many "loops", I'm not a super linux wizard but I'm persistent so got it to work. With that said... It can easily be a leftover of my many attempts at that time.
So... should I do a clean install?
> that's a bit scary as I'm running the system headless so I would need to at least be able to create a bootable usb with samba & ssh operational.
> Or alternatively... simply remove the tcz's... its complaining about... but that's also scary.
> but... if shit hits the fan I can physically pull the system from the basement and get it to my desk. That's just 2x an extra hour.

[Juanito]

I’m not sure why you have extensions named ._*tcz.

As an example, do you have files named ._Xlibs.tcz and Xlibs.tcz in your tce/optional folder?

[Stefann]

I checked... they are not in tce/optional folder.

I will do a find from root to see where it comes from.
that will be tomorrow. now have other obligations.

thanks

[Stefann]

Ok…
At least your answer made me aware “this is not common tinycore”. So…I googled and found it….
I’m not exactly sure what happened but appearantly it’s created by my MacBook. It’s probably spotlight that is indexing my tinycore. Pfew.

I also found the files,
When I was in tce/optional and did “ls -al” I could not find the files.
However, when in tce/optional and doing “ls -al ._*” I indeed found them all.
Note: all have same size: 4096 bytes. That is probably an Apple-thing.

All but one are from July 27 2024. That is when I got my first install done. That is than “kind of logical” and simply throwing away should be ok.

However…. One is from yesterday. An Apache dependency file.
Now I think I know what happened: I used Apple texteditor program to open that file to check the structure.
So.. at least Apple texteditor is creating them.

Mhh… mystery kind of solved.
Thanks for at least making me aware “this is not normal tinycore”.

Back to the original question:
> did I do a “decent update”?
> is it a bad thing that I only used the core.gz and vmlinuz files and nothing else from the iso?
> is it bad to rename them to core16.gz and vmlunuz16? (And actually, if not, is there a reason such is not standard?)

[Stefann]

Holy crap…
Just did “sudo find -name ._*” from root.

Looks like every file I ever touched or copied has a ._ sister.
Gosh…

[Stefann]

Ok,…
I found the full explanation of “why” the ._foo files are on my tinycore.
In short:
- I normally use my MacBook to manipulate and edit files and connect to tinycore via samba.
- Mac uses HFS filesystem with separate data&resource handling.
- Mac creates ._foo files when saving files on non HFS filesystem.

Full explanation here: https://www.cnet.com/tech/computing/invisible-files-with-prefix-are-created-on-some-shared-volumes-and-external-disks/

To prevent creation of .DS_Store Files:

Code: [Select]

Run in Mac terminal window
defaults write com.apple.desktopservices DSDontWriteNetworkStores true

This prevents creation of .DS_Store files on any network connected drive that specific Mac
Creation of ._foo files cannot be prevented, but they should be safe to delete as the resource information is only applicable for Mac specific reasons (did not test this yet myself but based on what I found it should be safe).

To delete ._foo files:

Code: [Select]

From parent directory (so from root directory if doing full system):

1/ locate all files: find . -type f -name '._*'
2/ check output, make sure you feel ok if all get removed
3/ delete them: find . -type f -name '._*' -delete

It may be necessary to run with “sudo”, I personally do 1st run without sudo and only run with sudo if needed.

My learnings…
- I normally use my MacBook over samba to do file handling and start editor on my MacBook to edit files. This workflow creates ._foo files as it involves a mixed use of mac HFS filesystem and tinycore non-HFS filesystem.
- for all editing this is not really a problem. These files are all in the “source code folder”. It’s actually just a limited set of files. It’s all in my “application area” which is relatively limited. I can keep doing this.
- for file handling this creates unnecessary clutter. File handling can be anywhere on my system and potentially creates pollution in my system. I recently had to create a .tcz extension for python and that extension may now very well have ._foo content (still need to check).
So…. For “non user space file manipulation” I will either stick to Linux commandline OR use flwm from tinycore gui over VNC on my mac.

I normally use tinycore in textmode. I sofar did the simple file handling from commandline but used the MacBook when moving or copying stuff “over far distances” for reason that commandline typing needs to be very precise for that. I will stop doing that.

    [Edit]: Changed  save  to  safe, 2 places.  Rich