Comments for All things digital http://www.allthingsdigital.nl Thoughts about things digital Wed, 18 Jan 2012 20:40:11 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Setting up VNC desktop sharing by David van Enckevort http://www.allthingsdigital.nl/2011/02/03/setting-up-vnc-desktop-sharing/comment-page-1/#comment-138 David van Enckevort Wed, 18 Jan 2012 20:40:11 +0000 http://www.allthingsdigital.nl/?p=18#comment-138 If you use the built-in VNC client on the Mac to control the shared screen and you might notice that copy & paste between the Mac and the shared screen isn't working. Using a different VNC client (e.g. Chicken of the VNC) will solve this. If you use the built-in VNC client on the Mac to control the shared screen and you might notice that copy & paste between the Mac and the shared screen isn’t working. Using a different VNC client (e.g. Chicken of the VNC) will solve this.

]]> Comment on Create a DNS redirector with Apache RewriteMaps by David van Enckevort http://www.allthingsdigital.nl/2012/01/17/create-a-dns-redirector-with-apache-rewritemaps/comment-page-1/#comment-137 David van Enckevort Wed, 18 Jan 2012 18:31:35 +0000 http://www.allthingsdigital.nl/?p=110#comment-137 Rob, that's true. However it is very easy to change that and add the path to the redirect by changing the RewriteRule to this: <code> RewriteRule ^/(.*) ${redirector:%{HTTP_HOST}|http://www.example.com}/}$1? [R,L] </code> The .* is a regular expression matching everything and by putting it in parenthesis you tell the rewrite engine that you want to refer to it again later. The $1 is the back reference to this. Rob, that’s true. However it is very easy to change that and add the path to the redirect by changing the RewriteRule to this:

RewriteRule ^/(.*) ${redirector:%{HTTP_HOST}|http://www.example.com}/}$1? [R,L]

The .* is a regular expression matching everything and by putting it in parenthesis you tell the rewrite engine that you want to refer to it again later. The $1 is the back reference to this.

]]> Comment on Create a DNS redirector with Apache RewriteMaps by Rob Hooft http://www.allthingsdigital.nl/2012/01/17/create-a-dns-redirector-with-apache-rewritemaps/comment-page-1/#comment-136 Rob Hooft Wed, 18 Jan 2012 18:23:32 +0000 http://www.allthingsdigital.nl/?p=110#comment-136 David, the redirector you describe ignores the path completely. How would you optionally add the path to the redirect, i.e. http://bla.example.com/foo/bar redirects to http://wiki.example.com/index.php/bla/foo/bar? One may not want that option for all redirected domains, but it may sometimes be handy. David, the redirector you describe ignores the path completely. How would you optionally add the path to the redirect, i.e. http://bla.example.com/foo/bar redirects to http://wiki.example.com/index.php/bla/foo/bar? One may not want that option for all redirected domains, but it may sometimes be handy.

]]> Comment on Maven 3 and the versions dilemma by Werner Keil http://www.allthingsdigital.nl/2011/04/10/maven-3-and-the-versions-dilemma/comment-page-1/#comment-134 Werner Keil Tue, 03 Jan 2012 12:02:30 +0000 http://www.allthingsdigital.nl/?p=34#comment-134 We ran into many of these during earlier projects last year. Right now Maven 3 seems to have solved it a bit by making module version numbers optional. So if you have a very consistent module structure, changing it in the master POM and all entries could solve it, plus consequently using <strong></strong> in that master POM instead of everywhere. There is an issue I just came across, that using <strong>${project.version}</strong> in the dependencyManagement of the master POM refers to the version of the individual module, not the master, so you may end up hardcoding the numbers of each module in addition to the master's version number. Maybe there's another version number for that master, but I haven't come across many people using it yet. Other than that using dependencyManagement at least makes life much easier also regarding version numbers. We ran into many of these during earlier projects last year.
Right now Maven 3 seems to have solved it a bit by making module version numbers optional. So if you have a very consistent module structure, changing it in the master POM and all entries could solve it, plus consequently using in that master POM instead of everywhere.

There is an issue I just came across, that using ${project.version} in the dependencyManagement of the master POM refers to the version of the individual module, not the master, so you may end up hardcoding the numbers of each module in addition to the master’s version number. Maybe there’s another version number for that master, but I haven’t come across many people using it yet. Other than that using dependencyManagement at least makes life much easier also regarding version numbers.

]]> Comment on Configuring Red Hat Enterprise Linux 5 or CentOS 5 for IPv6 by Configuring Red Hat Enterprise Linux 5 or CentOS 5 for IPv6 | All … | unixsecure test http://www.allthingsdigital.nl/2011/02/27/configuring-red-hat-enterprise-linux-5-or-centos-5-for-ipv6/comment-page-1/#comment-22 Configuring Red Hat Enterprise Linux 5 or CentOS 5 for IPv6 | All … | unixsecure test Sat, 05 Mar 2011 22:06:43 +0000 http://www.allthingsdigital.nl/?p=25#comment-22 [...] Configuring Red Hat Enterprise Linux 5 or CentOS 5 for IPv6 | All … This entry was posted in Uncategorized and tagged enterprise, network, rhel, short, short-post, [...] [...] Configuring Red Hat Enterprise Linux 5 or CentOS 5 for IPv6 | All … This entry was posted in Uncategorized and tagged enterprise, network, rhel, short, short-post, [...]

]]>