I am 94% Addicted to Coffee
asciidoc: FAILED: [tabledef-default] missing section: [tabletags-header]I am 94% Addicted to Coffee
It has been a while since the last entry, but I’ve been busy like hell and on a holiday as well.
But a short update was in order.
I’m now running a PFSense server on a Lanner netbox (FW-7530) as my firewall. My old Soekris 4801 could not keep up with my 90Mbps internet connection. The Soekris could only cope with about 45Mbps so that’s not very good. The Lanner gives me 88.9Mbps and that’s about the limit of the internet connection. Very nice.
Last time I blogged that the developers of git are a really busy
bunch.
Well, they really are. I found out I almost missed a complete release, so with this set I’m catching up.
Today I build version 1.7.0.3.
By now, you know where to find them.
The next entry will be more interresting, not only git building.
The developers of git are a really busy bunch. Today a new git
(1.7.0.2) arrived, again, so I did build the RPM’s.
By now, you know where to find them.
On my own server I tried to build the Git RPM’s and that worked, but on the server at work it borked on building the documentation.
The message I got was
asciidoc: FAILED: [tabledef-default] missing section: [tabletags-header]and Google has never heard of it.
Both servers are running CentOS 5.4 i386, so no differences there. I
started looking for the responsible program and I found out that at home
I have asciidoc version 8.5.1 and at work I have
asciidoc version 8.5.3.
It’s been a while, but now there is a new version of the MySQLBackup script.
This version has a few enhancements and some configuration options were added.
The main new feature is that it now supports multiple dumps per day. The old backups will be removed, of course, but only when they are over a day old.
An added configuration option is that it’s no possible to choose whether you want the databases locked during the backup.
Today I saw that git version 1.7.0.1 was out and while I missed out on 1.7.0 I decided it was time for some RPM’s again.
Well, NOT. The sources built like a charm and I’m using 1.7.0.1 now for the daily work.
The big problem is the documentation, as always. When I want to build
the docs, the build proces fails with some strange table-header and
table-definition error, that even Google has never heard off.
Today I saw that a new version of Nanoblogger was released, so I decided to update.
I thought this would be a breeze, but it turned out that Kevin (the maintainer of Nanoblogger) changed a lot between the last two versions. Nanoblogger calls (in my setup) Markdown to format the webpages and that’s where it stopped. A little debugging got things going again and I mailed Kevin the patch.
I guess it will be resolved in the next release.
This morning a git (1.6.6.1) arrived with a copule of nice bug fixes.
I created complete CentOS5 RPM’s for this again.
These new RPM’s can be found in the files section.
They have started again, those EU nitwits. When does the EU just stop with this madness?
Stop them now and (re)sign the petition against software patents.
Today I upgraded my NanoBlogger software from version 3.3 to version 3.4.1.
This whole process was completely painless. Just installed Nanoblogger 3.4.1 and regenerated everything and that was it.
A quick `side by side' compare of the old and the new one revealed nothing special.
If you see any errors, please let me know.
When I was installing a new server I thought that it would be nice to
have the server display a nice banner when I contact it. With OpenSSH
this is rather easy to achieve. Just setting the Banner option in
/etc/ssh/sshd_config should do the trick. I also thought it would be
nice to have the servername displayed, created with
Figlet. So when I login the screen should look
something like this:
A new git (1.6.6) arrived and I thought I should create RPM’s for this
again.
These new RPM’s can be found in the files section.
A new git (1.6.5.3) arrived and I thought I should create RPM’s for
this again.
This turned out to be rather tedious and frustrating.
Running rpmbuild -ba git.spec
as usual gave me an error
I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
/home/tonk/rpmbuild/BUILD/git-1.6.5.2/Documentation/git-add.xml:2: warning: \
failed to load external entity "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"Hmm, never seen that one before. Digging around in the Makefile and
adding a lot of `echo`s to display some debugging info, I found it.
Within a mixed Linux and Microsoft Windows network I ran into the following problem:
A host with the hostname linux1.firm.local could be ping`ed and found
with `nslookup and dig, but it was impossible to start a ssh
session. The result kept being: Unknown host.
Playing Cherlock Holmes revealed that this had to do with Avahi and
mdns, so with the .local part of the hostname.
In my /etc/nsswitch.conf the hosts: line read: (Using Ubuntu 8.04)
A co-worker at our company found a VMware image for an ancient UNIX version, called UNIX V7. This version dates back to the good old days of 1979, and therefore it is now already 30 years old. He found this at Nordier.
It’s is incredible that a UNIX version of so long ago already supports multi-processing and multi-user.
I tried to run this version of UNIX on my VMware server version 2.0, but it got stuck at the command prompt. I could have spent a great deal of time getting it to work, but playing with KVM recently, I decided to convert the image to KVM.
Again, there is a new version of the Git Version Control System available, named version 1.6.5.1. This version contains some bug-fixes, no feature enhancements.
This new version (1.6.5.1) is now packaged and online in the files
section.
Enjoy!
This morning I found out that there is a new version for the Git Version
Control System. This new version (1.6.5) in now packaged and online in
the files section.
Enjoy!
At our local radio station (Omroep Groesbeek) we use OpenFiler version 2.3 for our storage solution.
Yesterday, however, we didn’t have a storage solution but a storage problem. None of the exported disks could be accessed, neither through Samba nor NFS. Further investigation showed that the operating disk was completely kaputt. I tried to make a clone of the disk with CloneZilla but the clone failed and the new file systems where unusable as well.
Using git on a daily basis now, it bugged me that there are no RPM’s for git on CentOS 5.3. At the git download site it’s possible to download versions for Fedora 9, but that’s not what I want or need.
So I decided to make my own. Downloading the source, unpacking and
running make git.spec gave me a basic spec file to start with.
After minor tweaks I tried to cook the RPM, but I was in for a surprise.
Some time ago I told you about the vigit program, to combine editing
and submitting to git. This had some disadvantages, that made me search
for a better solution.
I found this in the git filtering capabilities.
The major problem was that the file was modified by vigit after it
was checked in to git. This means that the command
git diffalways showed differences. That was something I didn’t like at all. But I do like some version info in the file. And the git-hash as well.
OK, it took some time, but the holidays where in my way.
I finally switched completely to git, the best version control system out there, at this moment.
I found a bug in the vigit program, that I corrected and my header
program is now default for git and I have removed CVS. Nobody should use
that anymore, because it’s rather old and served it’s purpose.
I’m now experimenting with git filters to make the checkin and checkout better and that there’s no difference between the file on disk and the one in the repository.
At work we now have a very nice SAN with two machines running VMware vSphere. I did try to add fibre storage to the VMware machines and that didn’t work. I did get a lot of errors and unknown problems. Even Google never heard of them. One of those was ~ Error during the configuration of the host: Failed to get disk partition information ~
Googling for this and more generic terms pointed me to a hint to partition the disk on the VMware server itself and then create a VMFS filesystem onto it. Well, that should be easy enough.
Oke, that’s it. Ubuntu Jaunty up and running. After hardly two hours of installing and configuring it’s done. I have Ubuntu up and running. With zsh, Firefox 3.5, OpenOffice 3.1 (although I never use it), all the VPN connections I need, TeX Live, Mutt, ext4, XFCE 4.6, Wifi, webcam and all the things I forgot.
I didn’t need Google, hack it or whatever. Just configure it the way I want. Out of the box, no problems.
It was a long time ago that I created a Geek Code Block for myself. As I aged this block aged with we, so it was about time I updated it.
Take a look at the about page to see the new code. I also added a decoded version for those who do not like to decode stuff.