General TC > Tiny Core on Virtual Machines

Installed TC on VMWARE 6.7 with open-vm-tools but tools are not running

<< < (2/4) > >>

LeonStraathof:
Thanks again for the help, the verbose option gave me a silly answer that made a lot of sense (disk full). Most OS variants give other messages/problems when your disk is full, but i guess the stateless nature of TC prevents those other problems. I still like TC although the learning curve is steep and information is scattered. The fact that the wiki seems to be down forever does not help to get to information (User authentication is temporarily unavailable. If this situation persists, please inform your Wiki Admin). But the forum seems to bee a great place with a lot of dedicated people. I just wish there was more online reading material for people who are starting with TC.

I have 2 other questions:
1 What are the official minimal specs for TC because i found out the hard way that it is not the advertised memory footprint that is on the site. Sure when it is running the consumption is low, but to boot it (get it to a running state) takes more so sounds bit of false advertising to me. I can do trial and error to figure out the approx. minimal requirements but if anyone can tell would be nice.

2 I still want to configure this as a bridge and could not figure out if there is a ready made TCE. To explain in more detail what i am trying to build:
I want a small as possible ESX VM that boots stateless (not interested in anything being saved of the user session) and acts as a bridge between 2 network adapters. One network adapter is a virtual vmxnet3 adapter the other one will be a physical adapter that is connected to the VM via passthrough. The physical adapter will in most cases be one of the many Realtek gigabit chipset types. Since VMware ESX 7 does not support linux drivers anymore only native ESX drivers, using a dedicated VM as a bridge is my solution for using not supported nic's on ESX. I got it working with a Debian install that i set as autoboot first VM when the ESX host starts and it works like a charm. The reason i looked at TC to replace the Debian solution is size (the smaller the better) and the fact that TC is stateless (i want it to boot clean each time it boots and no live kernel updates and other stuff changing the machine over time). Any idea how i could build something that would just bridge automatically when it sees 2 network adapters?

Rich:
Hi LeonStraathof

--- Quote from: LeonStraathof on October 27, 2020, 09:37:54 AM --- ... I still like TC although the learning curve is steep and information is scattered. The fact that the wiki seems to be down forever does not help to get to information (User authentication is temporarily unavailable. If this situation persists, please inform your Wiki Admin).  ...
--- End quote ---
There is a mirror of the Wiki here:
http://wiki.tinycorelinux.net/doku.php?id=wiki:start
You could take an hour and read this very fine book here:
http://tinycorelinux.net/corebook.pdf
And you probably already found the FAQ:
http://tinycorelinux.net/faq.html


--- Quote --- ... 1 What are the official minimal specs for TC because i found out the hard way that it is not the advertised memory footprint that is on the site. ...
--- End quote ---
That number changes over time as new releases come out. Resources are not dedicated to measuring it since the
issue almost never comes up anymore.

--- Quote --- ... I can do trial and error to figure out the approx. minimal requirements ...
--- End quote ---
Since you want to do more than simply boot, you will have to do that anyway. Any "minimum RAM numbers" assume
a bare system with no applications installed and running.


--- Quote --- ... 2 I still want to configure this as a bridge and could not figure out if there is a ready made TCE. ...
 ... I got it working with a Debian install that i set as autoboot first VM when the ESX host starts and it works like a charm. ...
--- End quote ---
What application(s)/daemons did you start under Debian to accomplish your goal? That information can be used to see
if the TCEs you need exist. Don't spout out systemd (sysconfig) commands. They don't exist in Tinycore.

LeonStraathof:
Hey Rich, thanks for the reply, and pointing me to the mirror of the wiki that really helps me a lot. Also thanks for pointing out the book in pdf format, already made corrections to my machine thanks to info in the book (made a vm with the HD connected to ide as claimed to be the best solution for ESX in some forum posts, but the book stated that is should use paravirtualized scsi as thats is the supported solution) This small change made the vm boot even faster so i am a very happy camper.

About the minimal specs, it aint that big of a issue because this must by far be the smallest distro anyway. It's just that the numbers on the website seem to be from a ancient version. It's like Microsoft stating that they have a Windows version that can run on 256kb of memory, which is no lie in 1985 they had Windows 1.0 that did exactly that.

Already started digging in making your own extentsions so even if the extension i need does not exist yet i guess i could make it myself. I will retrace my steps on the Debian machine first to give a complete answer here first. Because if it already exists no need to reinvent the wheel.

Still the way this OS behaves is fundamently different then other linux variants. The concept that it creates an running environment from essentially merging the content of several archive files is very smart. However when i look at what most people are trying to do with this OS is making a machine that is not completly stateless which is the opposite of what this OS is very good at.

Rich:
Hi LeonStraathof
This may be of use to you:
http://tinycorelinux.net/11.x/x86/tcz/iproute2.tcz.info
There's a 64 bit version available too. You didn't specify which architecture you were interested in.

There's a brief answer here:
https://unix.stackexchange.com/questions/255484/how-can-i-bridge-two-interfaces-with-ip-iproute2

This fellow, discontent with the iproute2 documentation, set up his own documentation page with examples:
https://baturin.org/docs/iproute2/


--- Quote from: LeonStraathof on October 27, 2020, 12:07:17 PM --- ... Still the way this OS behaves is fundamently different then other linux variants. The concept that it creates an running environment from essentially merging the content of several archive files is very smart. However when i look at what most people are trying to do with this OS is making a machine that is not completly stateless which is the opposite of what this OS is very good at.
--- End quote ---
So, your one of those guys who pays attention, reads documentation, and takes the time to comprehend what's going on?
I see we're going to have to keep an eye on you. ;D

andyj:
I have one of what you are looking for, but my gateway VM is also diskless, I have another VM running dhcp/bootp and lighttpd to boot it using PXE. It's as stateless as can be, I don't know how I could save anything for persistence even if I wanted to. You say bridging which is not the same as routing and firewalling. Are the two NICs on the same network/subnet or different networks/subnets?

Navigation

[0] Message Index

[#] Next page

[*] Previous page