MicroCore Linux version are quite old about gns3-registry HOT 11 CLOSED

We plan to update them.

A nice to have is a packer script allowing to rebuild the appliance.

from gns3-registry.

If it helps I could create an updated tinycore appliance. I would just use the images from Brezlar, verify RAM usage and description.

from gns3-registry.

I will check during the week if it's hard to create a packer script.

It could be nice if anyone can take the packer script, add a package without the need to do all the configuration by hand.

from gns3-registry.

I just played a little bit with packer and generated a first test version, see https://github.com/ehlers/gns3-registry/commit/5e9f0fcc1de62cd14ef7b35647104227ade896ad

from gns3-registry.

Awesome !

On Tue, Oct 6, 2015 at 2:54 PM Bernhard Ehlers [email protected]
wrote:

I just played a little bit with packer and generated a first test version,
see ehlers@5e9f0fc
https://github.com/ehlers/gns3-registry/commit/5e9f0fcc1de62cd14ef7b35647104227ade896ad

—
Reply to this email directly or view it on GitHub
#18 (comment).

from gns3-registry.

Updated my Tiny Core packer to support V4.x, tested only with 4.7.7. Also some cleanup done.

Next step is to create a packer for NETem.

from gns3-registry.

Do you want to make a PR for tiny core? I can merge it, build and push an
image on sourceforge.

On Wed, Oct 7, 2015 at 9:41 AM Bernhard Ehlers [email protected]
wrote:

Updated my Tiny Core packer to support V4.x, tested only with 4.7.7. Also
some cleanup done.

Next step is to create a packer for NETem.

—
Reply to this email directly or view it on GitHub
#18 (comment).

from gns3-registry.

Well, I could. But for me there are some open questions:

• What packages should be included? Currently I added openssh, ipv6, iptables, iproute2, tcpdump and iperf3. Is something important missing?
• How to name it? Since V4.2 (since 2012) the Tiny Core guys no longer use the term MicroCore, therefore I used TinyCore. But a GUI version would also use that name.

from gns3-registry.

We can name it core because it's the name of the ISO.

For package I suggest a naked version with nothing and a network admin toolbox where we put all the require package.

I can take care of polishing stuff.

from gns3-registry.

Just created the PR. I think it's better, if I leave that polishing to you. I'm not good in that,

from gns3-registry.

I have opened issues for stuff like openvswitch

from gns3-registry.