Tiny Core Base > TCB Q&A Forum

did I correctly update to TC16?

<< < (2/2)

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: ---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
--- End code ---

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: ---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.
--- End code ---


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

Navigation

[0] Message Index

[*] Previous page