{"id":1674,"date":"2025-10-11T14:03:40","date_gmt":"2025-10-11T19:03:40","guid":{"rendered":"https:\/\/zewwy.ca\/?p=1674"},"modified":"2025-10-11T14:18:48","modified_gmt":"2025-10-11T19:18:48","slug":"installing-corepure64","status":"publish","type":"post","link":"https:\/\/zewwy.ca\/index.php\/2025\/10\/11\/installing-corepure64\/","title":{"rendered":"Installing CorePure64"},"content":{"rendered":"

<\/span>Back Story<\/span><\/h1>\n

So in my previous post I shared how to setup a very small footprint Linux server called Linux Core: Installing Core Linux \u2013 Zewwy’s Info Tech Talks<\/a><\/p>\n

but…… I tried getting docker running on it was hit with an error “Line 1: ELF: File not found”.<\/p>\n

\"\"<\/a><\/p>\n

AI, after giving all the required command to do a “manual install”, stated, “duuuuurrrrrrrrrrrrrr docker don’t give 32 bit binaries”, to which I was replied huh… I guess I installed 32 bit Core Linux… do they have 64bit versions?<\/p>\n

It gave me some dumb link to some dumb third party source.. the answer is yes.. here: Index of \/16.x\/x86_64\/release\/<\/a><\/p>\n

So here we go again….<\/p>\n

<\/span>Installing CorePure64<\/span><\/h1>\n

Step 1) Download Install image CorePure64-16.0.iso<\/p>\n

Step 2) get x64 bit hardware, or create a VM that supports 64 bit. I have 64 bit hypervisors, so I will create a VM as I did in my first post.<\/p>\n

\"\"<\/a><\/p>\n

This time 2 CPU, 1 GB RAM, 60GB HDD, thin, VMparavirtual scsi controller, EFI enabled with secure boot, let’s see if this works out…. No boot… Flip boot settings to BIOS mode… ISO boots.. ah man FFS its x64 based but still relies on BIOS for booting… that sucks… of well moving on….<\/p>\n

<\/span>Booting and Installing Core Linux<\/span><\/h2>\n

Attach ISO boot. Core Linux boots automatically from ISO:<\/p>\n

\"\"<\/a><\/p>\n

For some reason the source doesn\u2019t tell you what to do next. type tc-install and the console says doesn\u2019t know what you are talking about:<\/p>\n

\"\"<\/a><\/p>\n

AI Chat was kind enough to help me out here, and told me I had to run:<\/p>\n

tce-load -wi tc-install<\/pre>\n
Which required an internet connection:<\/p>\n
\"\"<\/a><\/p>\n
However even after this, attempting to run gave the same error.. mhmm, using the find command I find it, but it needs to be run as root, so:<\/p>\n
sudo su\r\n\/tmp\/tcloop\/tc-install\/usr\/local\/bin\/tc-install.sh<\/pre>\n
\"\"<\/a><\/p>\n
C for install from CDrom:<\/p>\n
\"\"<\/a><\/p>\n
Lets keep things frugal around here:<\/p>\n
\"\"<\/a><\/p>\n
1 for the whole disk:<\/p>\n
\"\"<\/a><\/p>\n
y we want a bootloader (It\u2019s extlinux btw located [\/mnt\/sda1\/boot\/extlinux\/extlinux.conf}):<\/p>\n
\"\"<\/a><\/p>\n
Press enter again to bypass \u201cInstall Extensions from..\u201d<\/p>\n
3 for ext4:<\/p>\n
\"\"<\/a><\/p>\n
Like the install source guide says add boot options for HDD (opt=sda1 home=sda1 tce=sda1)<\/p>\n
\"\"<\/a><\/p>\n
last chance\u2026 (Dooo it!) y:<\/p>\n
\"\"<\/a><\/p>\n
Congrats\u2026 you installed TC-Linux:<\/p>\n
\"\"<\/a><\/p>\n
Once rebooted the partition and disk free will look different, before reboot, running from memory:<\/p>\n
\"\"<\/a><\/p>\n
after reboot:<\/p>\n
\"\"<\/a><\/p>\n
Cool, the install process was 100% the same as the 32bit process…<\/p>\n
but running uname -m we see we are now 64 bit instead of 32 bit.<\/p>\n
<\/span>Changing TC Password<\/span><\/h2>\n
Step 1) Edit \/opt\/.filetool.lst (use vi as root)
\n\u2013 add etc\/passwd and etc\/shadow<\/p>\n
\"\"<\/a><\/p>\n
Step 2) run:<\/p>\n
filetool.sh -b<\/pre>\n
Step 3) run<\/p>\n
passwd tc<\/pre>\n
Step 4) run<\/p>\n
filetool.sh -b<\/pre>\n
\"\"<\/a><\/p>\n
Now reboot, you may not notice that it applied due to the auto login, however, if you type exit to get back to the actual login banner, type in tc and you will be prompted for the password you just set. Now we can move on to the next step which is to disable the auto login.<\/p>\n
<\/span><\/span>Disable Auto-Login<\/span><\/h2>\n
Step 1) Run<\/p>\n
sudo su\r\necho 'echo \"booting\" > \/etc\/sysconfig\/noautologin' >> \/opt\/bootsync.sh<\/pre>\n
Step 2) Run<\/p>\n
filetool.sh -b\r\nreboot<\/pre>\n
<\/p>\n
K on to the next fun task\u2026 static IP\u2026<\/p>\n
<\/span>Static IP Address<\/span><\/h2>\n
For some reason AI said I had to create a script that runs the manual step\u2026 not sure if this is the proper way\u2026 I looked all over the Wiki:\u00a0wiki:start \u2013 Tiny Core Linux Wiki<\/a>\u00a0I can\u2019t find nothing.. I know this works so we\u2019ll just do it this way:<\/p>\n
Step 1)\u00a0 Run:<\/p>\n
echo \"ifconfig eth0 192.168.0.69 netmask 255.255.255.0 up\" > \/opt\/eth0.sh\r\necho \"route add default gw 192.168.0.1\" >> \/opt\/eth0.sh\r\necho 'echo \"nameserver 192.168.0.7\" > \/etc\/resolv.conf' >> \/opt\/eth0.sh\r\nchmod +x \/opt\/eth0.sh\r\necho \"\/opt\/eth0.sh\" >> \/opt\/bootlocal.sh\r\nfiletool.sh -b<\/pre>\n
Step 2) reboot to apply and verify.<\/p>\n
It didn’t work, but is I add “sleep 2” just before \/opt\/eth0.sh in the bootsync.sh file, then it works, not the greatest but I’ll take it for now.<\/p>\n
<\/span>Updates?<\/span><\/h2>\n
Tiny Core Linux<\/strong>, updating is a bit different from traditional distros. Here’s how it works:<\/p>\n
<\/div>\n
<\/span>\ud83d\udd04 Updating Tiny Core Linux<\/span><\/h3>\n
Tiny Core doesn’t have a single tc-update<\/code> command for the whole system, but it does have tools for updating extensions<\/strong> and managing packages:<\/p>\n
<\/span>\ud83e\uddf0 Extension Update<\/span><\/h4>\n
Use the tce-update<\/code> command to update installed extensions:<\/p>\n
\n
\n
bash<\/div>\n<\/div>\n
\n
\n
tce-update\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
This checks for newer versions of your installed .tcz<\/code> extensions and updates them.
\n\ud83d\udce6 Other Useful Commands<\/p>\n