nimbius

wow! almost a decade old and still runs :) 256M is about what you'd get out of a Raspberry pi, but the dimension is chewing up 200 watts of power whereas the pi wouldnt use more than 1 watt. have you removed all unnecessary modules from the kernel? are you running 32 bit or 64 bit? have you run smart diagnostics to make sure your disk is healthy? how long does it take to write a 1gb file to the disk (/dev/zero using dd.)

Ive got a few funtoo images in gentoo, built from the recovery CD of course. I can offer a few pointers certainly :) dont disable ipv6 unless there is an explicit (and good) reason. EG you're running HPC in an infiniband cluster or something, or RDMA over converged ethernet. enable VMXNET3 ethernet driver in the kernel. this is a faster driver not because Linux is better at using it, but because the VMWare hypervisor doesnt have to work to virtualize an ethernet driver. ensure the video card in the vsphere console is set to intel, or some manageable low-overhead card, and X should just work with stock drivers. Granted, you can use VESA and such but 2d accelleration wont be available using GL. dont run vmware tools. its a crutch for people who dont have a monitoring solution. it poisons the kernel to snoop processes for io stats in order to manage backend storage allocations, which can actually degrade performance in large VMWare environments with MCLOCK set to 0. VMXNET3 has already been included in the kernel for ages now, so again, avoid this "toolset"

dhcpcd would need the ability to solicit multiple lease requests from the dhcp server, which im not sure is something its capable of. the dhcp server would also need the ability to track multiple leases, not just renewals, from a single mac. presently the only way to do this is through static range assignments in dhcpd, but it still doesnt solve the problem of a client that can solicit N+1 requests. youll need to assign the IP's as static in gentoo. if you have a number of servers to do this on, and wanted to use DHCP as an automation tool, you may want to consider chef, ansible, or salt to help.

ive no experience with ZFS, however it should be as simple as adding the --zfs flag to genkernel. consider this to be similar to how users EFI stub boot gentoo using LUKS and LVM.

This is mostly a thread to endorse firewall and ipv6 as defacto elements of the container offering from Funtoo. Among the reasons it should be considered: Firewall: 1. An internet presence without a firewall encourages abuse and is a poor practice that contributes to the harm of the internet and its users. 2. Firewalls can and should be used as a learning tool to help grow the understanding of Funtoo and Linux in general. learning firewall implementation makes for a better user. 3. iptables provides a wealth of other neat tools to help users learn basics and advanced concepts of networking such as masquerade and DPI. 4. the consequences of a breech far outweigh the repercussions of expanded conntrack overhead, whatever it may be. a compromised container can put funtoo in RBL territory and reputation system blacklists. our users deserve firewalls and freedom from the 'one rotten egg' type of bans on subnets enforced by google and cisco. 5. its FUN to play in iptables http://shortround.net/2010/09/24/making-an-image-flip-proxy/ IPv6: 1. "Do IT" --S. LeBouf. 2. ARIN insisted we have our collective ducks in a row in 2012. Its had meaningful support in the kernel since 2006. its support at the carrier level is ubiquitous. most ISP's offer a v6 address, if not a subnet, for the user. 3. nearly every hosting provider on earth supplies a v6 subnet to their customer. If we continue treating IPv6 as an option and subject to interest, we tacitly imply a shortcoming in Funtoo. 4. ipv6 ipsec extensions are the security we need in 2016. modular headers, ndp, stateless and stateful configuration and host based routing isnt something thats going away. 5. even your cellphone uses IPv6. if you're a T-Mobile subscriber your stack to the tower is almost entirely v6. 6. its fun to play with new things. ipv6 load balancing is super neat. developing new software that uses ipv6 means your container will have to support ipv6. for containers to be competitive, attractive and useful, it means they have to support things that every other container supports.