VirtualBox to LXC migration.

It has been quiet the last months here, but there were reasons for that. The most time consuming reason was that I started to brew beer, but there were some other projects too.

The home server project got some big changes. The virtual machines were migrated from VirtualBox¬† to LinuX Containters. This makes the system a whole lot faster, and makes that you can use lighter machines to run this project. The new Raspberry should do fine. Anyway, it took some time before I could document it all, but now it’s ready (I hope).

The firewall configuration is replaced. I used to use firewallbuilder, but that project was abandoned. So I decided to write some scripts that generates the firewall rules using some configuration files. These are available as Slackware package too.

Progress migration to Slackware.

All articles original written for Arch Linux are now converted to Slackware, or are now more or less universal articles. Only the article about VoIP base installation needs more work. Most Slackware based packages are available now on the Slackware extra download site.

I am planning to add a whole new series of articles, Sound engineering and Sound on Linux. For a bit over 40 years I do things with sound, music and bands. That means I have seen everything from tubes to digital sound processing. Computers, and so Linux too, are becoming more important on sound production. In the studio this is already for a few years, but now it is more and more used for live sound as well.

New download site for my Extra Slackware packages.

All Extra Slackware packages are removed from this site, and hey are now available from it’s own site. This makes the sources for the packages available too and it looks more like a general Slackware packages tree. This move removes some load from this site, it became too slow because the file database was getting big.

In the meantime, most articles are rewritten for Slackware again, just eight to go and they are done.

Happy New Year and some updates

First of all, a happy new year to all our readers. The site has now a facebook page, so FB users can now more easy follow a number of changes on this site. Use the like buttons or the button in the header to go there.

Syslinux boot

Syslinux boot

The reworking of the existing articles from Arch Linux into Slackware Linux is making good progress. It’s a good opportunity to make some articles more or less distribution independent.

Today I wrote a new article to finish the basic system installation using syslinux as boot loader and so that the basic installation is now a more complete story.

Only One Server to go..

That’s right, just one server that I maintain is still running Arch Linux. This server is in another part of town, so I need to go there to migrate that one to Slackware. The virtual Linux on that server is already migrated because that can be done via the Internet. Such a thing is just a matter of preparing a new virtual root disk on a local system and install it on the remote server. A reconfigure of the disks and reboot and such virtual server is up and running again in a few minutes. This is just one of the advantages of using virtual servers.

At first I didn’t want to put the complete Slackware packages from my repository on line, but this week I decided to make these packages available for download. Lets see how it goes with the limited bandwidth here.

Half of the articles about the home server are adjusted to Slackware, slowly the rest will follow.

Progress dropping Arch

In the last weeks I prepared the move of the virtual routers from Arch Linux to Slackware 14.0. Now two routers and two web servers are running Slackware again. The largest work will be the host that runs the virtual machines. A lot of packages need to be prepared to minimize the downtime. Luckily I used to have two root partitions so that the system can run dual boot with two distro’s. This allows me to reboot Arch if it takes too long or if extra packages need to be build. This can happen as the host server has all the network drives with the packages and sources.

Read More …

Back to Slackware

Up to now the home server project and articles were based on Arch Linux. Before I wrote these articles I had mostly used Slackware, but for this project I used Arch because it was more flexible at that time. But things change over time, and not always for the better. The first problems with Arch started when they abandoned the net-tools package. The scripts that should replace this functionality are still not good enough for this server project and possible for a lot of other projects.

Read More …

Network configuration is much better now.

About a year ago I wrote an message about the deprecation of net-tools. Finally after a little more then a year the “new” scripts can do almost anything what the old scripts could do. The Arch Wiki is not yet up to date, but at least the network configuration now works for regular servers. It only doesn’t work on the Home Server itself if you use a virtual gateway server. Then you must still use the old network-legacy package that you can download from this site.

I have updated the articles that used the network-legacy method as temporary solution.