About this blog

Entries in this blog

Well, I wanted to play with VirtualBox on Funtoo again.
Setup metro to create a custom stage3, added my stuff I use.
All went well, chrooted into the new install, did all the normal setup stuff.
Rebooted into the new install. all was fine in the world.
Adjusted my VM's to use VirtualBox, and even finally got OS X to work right virtualised.
Then the bullshit. How the fuck do you autostart vm's on boot.
Went down the google rabbit hole, all the info was based on other Distros or outdated info.
Fuck!!!!
So I did what any self respecting person would do. I built a rc startup script.
Well (4) actually.
So here they are.
1) vbox.example - this is the /etc/conf.d file - set options there. rename file to the name of the service - vbox.myvm
2) vbox.tmpl - this is the rc script that goes in to /etc/init.d, then create symbolic link to the vm name, use like netif.tmpl
# ln -s /etc/init.d/vbox.tmpl /etc/init.d/vbox.myvm
3) vboxd.start - goes into the /etc/vboxd dir - starts the vm. The correct vm config is passed to the script by init script
4) vboxd.stop - goes into the /etc/vboxd dir - stops the vm. The correct vm config is passed to the script by init script
And that's it.
I can run as any user, VirtualBox segments the available vm's according to user, so a VM under ckurlinski will not show up under root.
Nice for some things, suck for writing a init script.
All VM's will run under created user, and can be set to start / stop with different parameters: headless , saved state.
Sends info to dmesg also.
The last thing I would like to do is create a portage package.... Not even sure where to start on that .....
Thanks for sharing.

Not sure how many people out there are like me, but here is a project I just about to complete for a client.
I'm not in the IT industry, I'm in construction, a master plumber by trade, but do a lot of building management system integrations, and a lot of really specialty projects, like custom fire pits with iPad controls, high end pools ( we're talking 100K gal completely automated, heat pump / solar water heater for potable water, large solar systems ( looking forward to trying out the Tesla Power Wall ). Generally, anything that requires a computer interface, I'll do. Basic anything is boring, and not for me.
Well, this leads my to my latest project that's wrapping up. (3) Years ago, I did a pool system for a client, but they didn't have time to build a structure over the equipment, and over the last (3) years the equipment is starting to fail, the Bahamian sun and sea is brutal on this kind of stuff. So I proposed to he client to build a structure over the equipment to protect it. He said great idea, what will it cost, and I went huh?
After some thought and a lot of design work, I draw some plans up and priced it to the client, and he said great, when can you start.
So here is the original design.
And here is the final structure without paint.
The only modification from the original design was the doors, which I custom built from Number 1 grade fir, and used some left over epi wood for the siding. Sanding and painting is all that is left.

I'm a big fan of trying anything new, but the cardinal rule for me is this:
Don't mess with the data. If you don't what to lose those irreplaceable pics of grandma, keep it on a separate drive.
This is my mantra. I love playing with my system, updating, tweaking, and exploring.
But this can be dangerous to your data.
This is also the reason why I chosen to use zfs as my storage for all my data. I can get to it from just anywhere. If it's unix(-like), I can download the kernel modules and access it.
I feel like zfs is the becoming the unix(-like) version of fat32. Let me explain.
I just did some consulting on a smartos job, but I had to p2v an existing Windows 2k3 server, with a dying hard drive.
Smartos is great an all, but it is really not setup to virtualise an existing machine.
So I place the failing drive into my setup, created a zvol the same size as the failing drive, dd the old drive to the new zvol.
Created a new KVM instance, and booted the thing up.
After some general cleanup and a massive amount of defragging, I had a good image ready for production.
Smartos side of things was fine, json took a little getting used to, helps finding a good validating editor, zfs send | zfs receive, brought up the zvol, and away I went with the client configuration, igmadm create and all. Now the setup is in production, and all seems to be well.
But the real point of this endeavour is this, ZFS is getting to the point of being truly cross platform.
The only thing that can't read ZFS is windows, and that access is a samba share away.
As much as I like Smartos, I love Funtoo. If I was going to roll out a data centre with clean installs, then Smartos is a great base.
But p2v a small business client, not so sure.
That's why I'm thinking about a Smartos like Funtoo usb bootable read-only install, and keeping with the way Funtoo is, basically a recipe for using the existing tools to create it, because that is the right way to do it.
Our BDFL gives us the tools to do anything we want with his creation, we as users of Funtoo, get to assemble it as we need to get the job done.
This is my idea, bootable usb Funtoo minimal, bare essential tools, read only root, builtin zfs kernel and xen hypervisor.
Now just to figure out how to do it........