<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Raspberry Pi on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/raspberry-pi/</link><description>Recent content in Raspberry Pi on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 05 Dec 2014 13:11:00 +0100</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/raspberry-pi/index.xml" rel="self" type="application/rss+xml"/><item><title>Running OpenVPN on a hosted server and internally on a Rasperry Pi</title><link>http://blog.marko-apfel.de/posts/running-openvpn-on-a-hosted-server-and-internally-on-a-rasperry-pi/</link><pubDate>Fri, 05 Dec 2014 13:11:00 +0100</pubDate><guid>http://blog.marko-apfel.de/posts/running-openvpn-on-a-hosted-server-and-internally-on-a-rasperry-pi/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;h3 id="motivation"&gt;Motivation&lt;/h3&gt;
&lt;p&gt;How about a secure access from outside into the own home network? So we can maintain machines, change configurations, getting files, .. from where ever we are. For this we let a VPN tunnel be established between a local RPi in our network to a hosted server. If this hosted server that offers a web based console we only need a web browser to access our own resources at home.&lt;/p&gt;</description></item><item><title>Replace or keep existing configuration files during Linux updates/upgrades</title><link>http://blog.marko-apfel.de/posts/replace-or-keep-existing-configuration-files-during-linux-updates-upgrades/</link><pubDate>Thu, 20 Nov 2014 17:03:00 +0100</pubDate><guid>http://blog.marko-apfel.de/posts/replace-or-keep-existing-configuration-files-during-linux-updates-upgrades/</guid><description>&lt;p&gt;During updating/upgrading a fresh Moebius installation on a RaspberryPi with&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;apt-get update &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; apt-get upgrade
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;it brought this question:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-txt" data-lang="txt"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Configuration file `/etc/issue&amp;#39;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;==&amp;gt; Modified (by you or by a script) since installation.
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;==&amp;gt; Package distributor has shipped an updated version.
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;What would you like to do about it ? Your options are:
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Y or I : install the package maintainer&amp;#39;s version
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;N or O : keep your currently-installed version
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;D : show the differences between the versions
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Z : start a shell to examine the situation
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;The default action is to keep your current version.
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;*** issue (Y/I/N/O/D/Z) [default=N] ?
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The default hint not to do that is mainly for longer running installations to avoid an overwriting of existing configuration files. In case of a fresh installation you should confirm with &lt;code&gt;Y&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>