Archiv der Kategorie: Linux

Linux Topics

Connect from Host to VBox guest via serial console

Today I need to connect to the serial console of a VBox instance to test the serial console boot and connection of the guest system (ArchServer that is). There seem to be a lot of ways on how to do this, I am just explaining, what works for me, using Arch Linux as the Host:

  • socat UNIX-CONNECT:/home/triplem/com1 TCP-LISTEN:8040
  • telnet localhost 8040


This was not working, in that I always received strange Characters in my terminal as soon as I used e.g. the cursor keys. This did not work, even after changing the terminal emulation to VT100 and all others.


The same is true for socat unix-client:/home/triplem/com1 stdout

I do not seem to be able to work with this kind of stuff, the following tip was not working as well:
Work with VBox and serial console.

IRC: nick/channel temporarily unavailable

I am using the public ZNC (an IRC bouncer) from globalshellz.org for my access to the freenode IRC network. I have had a minor problem when I connected to my ZNC. Since my away nick was not registered to my account (which is triplem btw), I have had to „login“ each time when I connected to the ZNC and my nick was changed from triplem[a] to triplem. So, I started my IRC client (XChat btw) and forgot to type in my password again, this lead to a problem that my nick was temporarily unavailable. To resolve this I looked on the freenode page and found the following easy solution:

  1. Registered my away nick with /nick triplem[a] and /msg nickserv group (of course I needed to login to my account, which was not a problem, since several nicks are already grouped to my main nick and I just chose one of those).
  2. I released the original nick (triplem) with the following command: /msg nickserv release triplem , and everything was fine.

Hope this helps you as well. And if you would like to meet me on IRC, you can take a look into the following channels:

  • #shellium
  • #globalshellz
  • #netburst
  • #archserver

Probably we meet us there 😉

Git: split repository into several smaller ones

In our company we did create a new project using git as the repository. The repository is central on our development server as well as on each developers machine. Previously we used SVN, so the whole team is still used to a central repository, and furthermore our infrastructure (Redmine, Hudson, …) needs access to the repository.

After creating the project, we did several refactorings and splitted the whole project into several smaller ones. We did this all in one repository, without any problem. But because e.g. Hudson needs access to a single project, and we wanted to build all components standalone, we had a problem. We needed to split the git repository.

To solve this issue, first we needed to push all changes to the new repositories (note that we pushed the whole project into different repositories, to keep the whole history). For this to work, we first copied the whole project into different directories (named after the project names) and then executed the following script:


#!/bin/sh
cd $1.git
git remote rm origin
git remote add origin ssh://mmay@server.tst/srv/git/$1.git
git push origin master

After this is done, the new repositories needed to get cleaned up:


cd $1.git
pwd
git filter-branch --subdirectory-filter $1 HEAD -- -- all
git reset --hard
git gc --aggressive
git prune

After this, we removed the projects from the original projects, but kept the repository itself, just to have all the initial history before the split into several components with different subdirectories.

Hope that this helps you as well 😉

PS: Some of this stuff was taken from http://stackoverflow.com/questions/359424/detach-subdirectory-into-separate-git-repository.

More thoughts on the ALM Stack

I am just thinking, that just providing some Toolset, like the ALM Stack is not enough. There is some documentation needed, not only for configuration, maintance and usage of the ALM Stack, but also some hints and best practices for the handling of projects.

Since we are already providing a wiki in our toolbox (Redmine contains a wiki), we will most probably provide an initial project in Redmine which will be configured the „right“ way and contain some documentation.

Most of these best practices are already documented elsewhere, so we will mostly provide links to these resources, as well as additional resources we can provide ourselves.

If you have any input on this, do not hesitate to contact me anytime.

My ALM thoughts

Yesterday we released a new ALM Stack based on ArchServer, which replaces the beforehand already known „Arch Linux Development Stack„. I guess the name change was needed due to the fact that the underlying architecture changed from Arch Linux to ArchServer and furthermore the ALM in the name shows more appropriate what the purpose of this stack really is.

The goal of this software stack is really, to release a full working stack of tools needed for a Application Lifecycle Management. The selection we chose (Maven, Hudson, Nexus, Sonar and Redmine) is pretty much a best-of-breed solution. One of the main ALM-Software components (IDE) is still missing though. Since this is not a server-side component, it would be really hard to provide this as well. But I guess we should provide an instance of Eclipse with all needed Plugins pre-installed (Mylyn with Redmine Plugin, Git, m2eclipse and probably more…). The same could be done for IntelliJ Idea, which I do like a lot as well, lately.

Something, which should be implemented as well, is most probably ReviewBoard or Gerrit for Reviewing code changes. This is IMHO not needed in all cases of software development, but in some (eg. the Android development and/or the KDE developers).

A real nice thing would be to provide a kind of „Installation procedure“ to install all components in one step with some personalizations as well (e.g. Hostname of the ALM Stack host). Furthermore some real documentation is needed, so that the „customer“ will find the answers to all their questions.

If you would like to participate, do not hesitate to write an email to me 😉

ArchServer – ALM Stack

Please take a closer look onto the newest addition of the ArchServer distribution. I have just published a ALM (Application Lifecycle Management) Stack for this distro with all ALM related tools already installed.

The stack contains the following components:

You can find all scripts to install such a stack (I named the stack Archlinux Development Stack earlier on, but it should now be called ArchServer ALM Stack), on Github. There is also additional information about this stack. In the near future I hope to add more components as well as more documentation. The documentation should then be also put into the ArchServer.org wiki.

The Virtualbox image itself can be found on our mirror at http://mirror.archserver.org/iso/vbox/ArchServer-ALMStack-20110101-i686.vdi.lzma. The image is lzma-compressed, so you need lzma to decompress the image.

ArchServer Kernel Update

The last weekend was a busy weekend for me. I have updated the kernel of ArchServer to its latest incarnation 2.6.32.11. If you find time, please try out ArchServer and test the newest Kernel version.