Tuesday, April 27, 2010

How Much Of Woman's Body Should Be Muscle

recordings save from the hard disk of a digital disk recorder

On the desktop machine once an end to Ubuntu and Gnome. Now squeeze runs Debian with KDE (My first steps with KDE outside of virtual machines). Ubuntu 10.04 Lucid Lynx always comes out soon and there seems to me a rolling release distribution just right. Actually I wanted to take Arch, but there are still a few problems. Moreover, I do not like that the packages are not signed and I exclude one-in-the-middle attacks and compromised server can not mirror. Debian's package management still likes me very much because I like to stick to it. And I like KDE now also getting better.

  • Always on the bleeding edge side of life
  • :) Well, almost ... : D on the netbook runs Ubuntu already 10:04 Lucid Lynx and will remain there probably is. When the it is important to me that it just works. And since Ubuntu does his job really well, even if I disturb a few peculiarities.

Saturday, April 24, 2010

Dua For Babies Having Stomach Pain

Goodbye Ubuntu, Gnome

"). The following figure illustrates the problem. If the port is not forwarded properly, can to connect the client with the server. The lower arrow, however, shows the connection with configured port forwarding.

However, there is sometimes the problem is that you can pass on that system either can not or that the port can not cope with the opposite configuration. Especially with a remote desktop connection in which you want help with a computer problem is that often the case. Although most such systems are already at ease with the house building a Reverse Connection (such as VNC), but you can still come across applications, where such a functionality is missing. Since it would be good if the entire connection can build backward, so that no one but the other self forward this port must.

It can be with simple command-line tools to build any connection backward. The most suitable is socat

: Socat is an excellent program that can combine different data streams together. This is exactly what you can do is quite simple: churning

Socat The client on the actual server side connects with both the actual server and with a Socat server on the client side. The client then connects to the server Socat. Since both instances Socat forward the data streams each (Input → Output and vice versa), client and server can now communicate as usual with one another:

But looks like from a practical implementation? First of all you have to leave on the client side, the port forward the router. In the following example, worked with Port 55 555. Now we start on the client side, the Socat server: socat TCP-LISTEN

: 55555 TCP-LISTEN: 8080

Socat The server now listens on ports 55 555

and 8080 (the client connects to later on that port) and connects them.

On the server side of the Socat client starts:

socat TCP: hostname: 55555 TCP: localhost: 8080 So there is a connection to Socat server is established (the

hostname must be modified accordingly be and must be known, of course, but the IP is simply a page, www.wieistmeineip.de

find out.), and this is connected to the local server (in this case the server listens on port therefore
 
8080, therefore the alternative HTTP port).

Last you need to connect only the client with the Socat server. This requires data only on the compound localhost and the corresponding port change (in the example

8080).

course is easy to see that the effort is not to be underestimated. But it may do in some situations paid off handsomely. And not as technically savvy users must be on the other hand, no longer a port forwarding and take care of its IP address. The command can also be easily transferred via Instant Messenger, so that the command will be copied only in a terminal needs. Of course, the approach is not for other application very useful.
 

Friday, April 23, 2010

Average Daycare Prices In Miami

Goodbye bypass NAT obstacle: Reverse Connections with Socat

That the Fritz Box from the house of AVM Berlin GmbH is among the most popular DSL router in Germany is one, is certainly not a miracle. (If also clear, inside Linux, send out: D) The features are really first class, these processes can, even a Telnet access unlock, so you can directly access the interior of the red box. However, I was still surprised when I searched today after a caller monitor for Linux. While there are some programs and scripts on the net, but nothing that really appealed to me right. At first I thought that this information may also be provided via UPnP

be, but it is much easier: Simply select on a telephone connected to the combination # 96 * 5 * and wait for the beep. Then opens Fritz! Box

the TCP port 1012

and outputs on this information on all incoming calls. It's simple, but brilliant! The key combination

# 96 * 4 * Other key combinations such as

# 96 * 1 * or # 96 * 0 *

to the WiFi on or off I had already known, but this neat feature remained undetected for years.

Linux users can easily view the way the information available with

netcat or socat favorite of mine

. The solution is obviously not very nice and elegant, but for a quick test it is always enough: fritz.box nc-u 1012 socat TCP: fritz.box: 1012 STDOUT stefan @ stefan-desktop: ~ $ socat-u TCP: fritz.box: 1012 STDOUT 17:04:10 10:04:33; RING, 0, 015xxxxxxxxx; 03xxxxxxxxx; Sxxx; 17:04:10 10:04:36; DISCONNECT, 0, 0,

I've done the fun and me small shell script written, which the incoming data from the Fritz Box reads and displays about the notification system:

# / bin / sh

get_element () {

 
echo "$ line"!
     
=
message

=



 if     [     "$cmd"     =     "CALL"     ]  ;   then  
interface = $( get_element 4 )
caller = $( get_element 5 )
target = $( get_element 6 )

title = "Outgoing Call"
message = "Target: $ target \u0026lt;br> Caller: caller \u0026lt;br> $ interface: $ interface" elif [ "$ cmd" = "RING" ] ; then caller = $ ( get_element 4) target = $ ( get_element 5) = $ ( interface get_element 6 )

if [ -z "$caller" ] ; then
caller = "hidden"
fi

title = "Incoming Call"
message = "Caller: $caller<br>Target: $target<br>Interface: $interface"
elif [ "$cmd" = "CONNECT" ] ; then
interface = $( get_element 4 )
number = $( get_element 5 )

title = "Connection Established"
message = "Number: $caller<br>Interface: $interface"
elif [ "$cmd" = "DISCONNECT" ] ; then
length = $( get_element 4 )
length_min = $(( length/60 ))
length_s = $(( length%60 ))

title = "Connection Closed"
message = "Length: $length_min min $length_s s"
fi

if [ "(" -n "$ title" ")"-a "(" -n "$ message" ")" ] ; then message = "Date: $ date time \u0026lt;br> Connection ID: $ connid \u0026lt;br> $ message" notify-send-i "gtk-dialog -info " " $ title " "$ message" fi done} while true; Thurs sleep list 60 done syntax highlighter: Pygments . Here in the blog to display the script wraps may! Simply copy a file and it should work. should the way for other manufacturers to cut a slice of quiet times. Negative glaring example is of course Apple, all of their really excellent (and overpriced: D) restrict devices so so much that they reach their full potential can not even begin to. Settings and simplicity are not mutually exclusive and to keep the user for the last few morons in my opinion is not a good concept ...

Saturday, April 17, 2010

Veet Cream Not For Genital

AVM - Berlin's vote off

The renaming of my project is now complete: The former "gWallpapers" "desktop nova" is. Only a few days ago, the latest releases, but there are surprisingly quite a lot of feedback, which I am of course immensely. A search on Google is already tons of hits. Most come from blogs, but even a YouTube video is. And I saw it myself yet managed to change the name everywhere. Unfortunately, I have made in the release still has some big goof, so I have released within two days, three versions. But now it is running again almost everything. Only the old settings are unfortunately not used because the program is now looking elsewhere for its configuration file. The old file can, however, relatively easy to ship the new location: $ rm-r ~ / config / desktop nova / $ mv ~ / .config / gwallpapers ~ / .config / desktop nova $ mv ~ / .config / desktop nova. gwallpapers.xml ~ / .config / desktop nova / $ desktopnova.xml sed-i-e 's / gwallpapers / desktop nova / g' ~ / .config / desktop nova / desktopnova.xml were again too few new bugs reported and asked questions . In Development Branch are already some updates, so a new version should also not all has been too long in coming. However, the translation work via Launchpad not currently, as well as the template name may have changed. Because first of patience is required. I hope that the hard-working translator but feels that in the future does not depend on help with the project. A big thank you to this point, all the translators;) A Debian package for the new version I have also been created. If all goes well then maybe it is officially included in Debian. This would then be available, so installation is simplified considerably in the next version of Ubuntu. If that works, then I look and perhaps also for other distributions like Fedora or Arch Linux. I am very happy it immensely, that the project is probably more successful than I would have expected. In Ubuntu Popularity Contest had the package "gwallpapers" installation in about 140 countries. I think that's been all sorts, after all, the package is not officially represented in the sources and the participation in the data transmission is disabled by default. Therefore, the actual number of installations on Ubuntu systems to be a lot more left, other distributions once left out. I think the spread anyway surprising since I've actually never run large advertising work. I have a project on my website and two German (!) Announced Ubuntu forums, so it's amazing that so often occurs in foreign-language blogs and forums. But the more people find pleasure in the project, the better it is, of course:)