I want to install the bare minimum of Debian Wheezy on an embedded controller with 128Mb flash.
So far I found the nice debootstrap method for installing, like described here. This end up with 157Mb disk usage after adding ssh.
Someone created a nice image for RasPi with have 118Mb, see here.
Additionally I tried shrinking by this guideline here, but it also dont succeed much.
Currently the controller is running with EmDebian Grip occupies 79Mb with 182 packages installed. But under Wheezy it needs much more.
So what packages are the absolute minimum needed?
Thanks
Achim
Related
I am currently working on building eviction sets on different ARM platforms, so for simplicity I want to use huge pages. Unfortunately, I don't seem to be able to do so on the Cortex A8 on the BeagleBone Black running Debian 10 (32 bit), which is the recommended Debian image from the BeagleBoard website. The kernel version displayed by uname -r is 4.19.94-ti-r73.
The first thing I find weird that cat /proc/meminfo does not display anything about huge pages. Furthermore, I followed the instructions on the official Debian wiki site for enabling huge pages, but after running sysctl -p at the end it just says that vm/nr_hugepages does not exist.
The Cortex A8 user guide clearly says that different page sizes are supported by the TLB, up to a size of 16MB. So what am I missing here? Is there even a possibility to allocate huge pages or is it just not possible for my setup?
I am not the most experienced in this topic, so I can't rule out that I missed something, but as far as I know I've looked all over the internet and can't find anything helpful. So any suggestion will do!
We develop a server-side solution and to ease its deployment we would like to provide our cutomers with two options:
1. Docker image
2. VM image in OVA format
The images should be automatically created by our build machine.
As of today, we use packer for this purpose. First we create docker image and then update that image in preconfigured virtual machine image (using 'virtualbox-ovf' builder). This works pretty well, but there are some problems with this solution.
First, our vm includes docker framework and two OSes (host's and docker's), so our VM image is ~twice bigger than docker. Second, to base our solution on another linux distro, we should manually configure new VM machine.
We are looking for 'Dockerfile'-style solution to create and configure VM automatically and then export it in OVA format. 'virtualbox-iso' builder is the obvious way to do this, but the building process will be much longer.
If you are willing to use Debian as your base OS then you could look at TurnKey Linux's TKLDev. It's probably a bit of a learning curve initially but it's a pretty cool thing IMO (although I'm very biased - see below disclaimer). TKLDev will build you a TurnKey (Debian based) ISO with your software installed on top. Then using Buildtasks you can convert the ISO to OVA, VMDK, LXC, Docker, OpenStack, etc...
Unfortunately Buildtasks is not very well documented but significant chunks of it are in bash so if you are handy with a Linux commandline you could work it out. Otherwise ask on the TurnKey forums.
The initial development (from Packer to TKLDev) may take a little while, but once the heavy lifting is done the creation of an ISO (in a guest VM on a moderm multicore CPU PC) takes about 10-15 mins and the OVA probably another ~5; Docker another ~5.
If you wanted to make it build automatically then you could use a hook to trigger a fresh TKLDev build (including the buildtasks image creation) everytime a commit was made to a repo. I know that git supports this but I assume that other version control systems allow something similar.
Also if the appliance that you are making is open source then perhaps it could be added to the TurnKey Linux library?
Disclaimer: I work with TurnKey Linux. :)
FWIW this is essentially the process we use to create our library of appliances in most virtualisation formats known to human kind!
My goal is to build up a recommendation system and after going through many articles, I came across Mahout as a simple, yet effective way to go on. I already have XAMPP installed on my system.
How can I install Mahout? I need the complete instructions since I have neither worked with cygwin before, nor have I worked with Hadoop, and everywhere I see, I see these two mentioned very frequently. I first need to install it on my localhost before going on installing it on the server.
Here is a detailed instructions page to install Apache Mahout with Hadoop in windows. Its bit tedious, but can be done anyway.
http://alans.se/blog/2010/mahout-on-hadoop-in-cygwin/
Just wondering if it's possible and what the best route might be to run a full-on Linux distro within my existing distro? It would be great to for instance run Arch Linux within a chroot, jail, etc.. I believe people are doing this on Chromium for example.
I would require that whatever fs loaded, I can install packages using pacman and that my changes are kept intact.
I have tried the Virtualbox route by the way and there is a pretty nasty bug involving double mouse pointers on rotated host screens that I can't seem to get around.
I should mention that I'll be using this chroot environment for development, maybe running the odd X client to be exported remotely, etc..
I followed the chroot guide at https://wiki.archlinux.org/index.php/Change_Root and basically installed a whole Arch system within a nested chroot according to the Arch Linux installation guide and I'm now able to switch to the environment at will.
There is a tool https://github.com/fsquillace/junest that does everything automatically for you (downloads and unpacks ArchLinux distro inside some folder and chroots there).
Has anyone gotten VisualWorks running under OpenBSD? It's not an officially supported platform, but one of the Cincom guys was telling me that it should be able to run under a linux compatibility mode. How did you set it up?
I already have Squeak running without a problem, so I'm not looking for an alternative. I specifically need to run VisualWorks's Web Velocity for a project.
Thanks,
if you're wondering about setting up linux compatibility mode and you're running the GENERIC kernel:
# sysctl kern.emul.linux=1
to enable at boot uncomment the kern.emul.linux=1 line in /etc/sysctl.conf
See the OpenBSD FAQ, specifically section 9.4 - Running Linux Binaries on OpenBSD.
Typically there are more steps needed then just kern.emul.linux=1 unless you have statically linked (i.e. completely stand-alone) binaries. The good news is that packages exist that contain Linux libs, and they are easy to install. This is all detailed in the above link.