Marcus Grenängen - Linuxhttps://grenangen.se/taxonomy/term/6
ensystemd timers for DuckDNShttps://grenangen.se/node/93
<div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"><div class="field-items"><div class="field-item even" property="content:encoded"><p>I had to migrate a couple of cron jobs over to systemd timers. This is a short walk through on how I did it for my DuckDNS updater.</p>
<p>Basically, we need to create two files under /etc/systemd/system or /etc/systemd/user dep. on your specific needs.</p>
<p>For DuckDNS I created the config under /etc/systemd/system. So any filenames or paths that are not rooted paths are in relation to /etc/systemd/system, so adjust accordingly for your own needs.</p>
<p><b>duckdns.timer</b></p>
<pre>
[Unit]
Description=DuckDNS update every 5min
[Timer]
OnBootSec=5min
OnCalendar=*:0/5
[Install]
WantedBy=basic.target
</pre><p>
<b>duckdns.service</b></p>
<pre>
[Unit]
Description=Updates DuckDNS records
[Service]
Type=oneshot
ExecStart=/usr/bin/sh -c 'echo url="https://www.duckdns.org/update?domains=[YOUR_DOMAIN_NAME_HERE]&amp;token=[YOUR_TOKEN_HERE]&amp;ip=" | curl -k -K -'
</pre><p>
<b>Uhm, what is all that jibberjabber...</b><br />
There are a couple of new things here that are very different compared to how you would configure this in your crontab.</p>
<p>First, you have to have a service defined for a timer, otherwise it just won't work, if you have documentation saying otherwise, please let me know.</p>
<p>Second, the service is defined as a oneshot service, this is important for the DuckDns updater since it should not be running all the time. And the timer will invoke it every time it elapses, and once done there is nothing more for it to do.</p>
<p>Third, the format for the timer config, <code>OnBootSec=5min</code> this ensures that after the system boots, it will wait for 5min before issuing the first run of the timer. <code>OnCalendar=*:0/5</code> means that we want the timer to be invoked every 5min. For a nice detailed walk through on how timers works under systemd, see <a href="https://wiki.archlinux.org/index.php/Systemd/Timers" target="_blank">https://wiki.archlinux.org/index.php/Systemd/Timers </a></p>
<p>And finally, you will have to replace <code>[YOUR_DOMAIN_NAME_HERE]</code> and <code>[YOUR_TOKEN_HERE]</code> with your own domain and token from the <a href="https://www.duckdns.org" target="_blank">DuckDNS dashboard</a>.</p>
<p>Once you have created the above files, you will need to start the service part of it to ensure that it works as expected.</p>
<p>Issue:</p>
<pre>systemctl start duckdns.service</pre><p>
Validate that your timer has been registered:</p>
<pre>
systemctl list-timers
</pre><p>
You should see some output from the list-timers command similar to this:</p>
<pre>
NEXT LEFT LAST PASSED UNIT &gt;
Wed 2018-08-01 19:10:00 CEST 3min 9s left Wed 2018-08-01 19:05:04 CEST 1min 46s ago duckdns.timer
</pre><p>
Make sure that your duckdns.timer shows up in the output. If everything looks good, or not, journalctl is your friend to query state and logs for services.</p>
<p>For example, if you want to see the logs for the duckdns.service, issue:</p>
<pre>
journalctl -u duckdns.service
</pre><p>
Make sure that you can see output similar to this:</p>
<pre>
Jul 31 20:20:02 hawk systemd[1]: Starting Updates DuckDNS records...
Jul 31 20:20:02 hawk sh[3030]: % Total % Received % Xferd Average Speed Time Time Time Current
Jul 31 20:20:02 hawk sh[3030]: Dload Upload Total Spent Left Speed
Jul 31 20:20:04 hawk sh[3030]: [316B blob data]
Jul 31 20:20:04 hawk sh[3030]: OK
</pre></div></div></div><section class="field field-name-field-tags field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Tags:&nbsp;</h2><ul class="field-items"><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/6" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Linux</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/158" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">systemd</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/159" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">cron</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/142" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">crontab</a></li></ul></section>Wed, 01 Aug 2018 17:02:08 +0000SneWs93 at https://grenangen.sehttps://grenangen.se/node/93#commentsUbuntu 16.04 - Unity - Laggy window resize when using NVIDIA GPUshttps://grenangen.se/node/92
<div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"><div class="field-items"><div class="field-item even" property="content:encoded"><p>After some time trying to ignore the resize window lag I hit my limit, every time I have chrome, chromium or any electron enabled app running the window resizing becomes excruciatingly slow in Unity.</p>
<p>After some searching around and looking in Chrome/Chromiums bug databases it seems that whenever you run the browser with GPU acceleration enabled this issue occurs. If it's NVIDIAS fault or if it's the devs behind Chrome/Chromium I can't say... But I did manage to find a fix for it.</p>
<p><b><i>Do note that this doesn't apply if you're using the Nouveau driver.</i></b></p>
<p><b>So, how to fix it?</b><br />
In Chrome/Chromium you can just go in under Settings and expand the Advanced options, you will find a checkbox there named "Use hardware acceleration when available", uncheck and restart and that one is fixed.</p>
<p>If you use electron based apps such as Skype for Linux Alpha; Sublime; Atom; or Slack you will need to modify each applications launcher file and add</p>
<pre>--disable-gpu</pre><p> to it's startup args.</p>
<p>I'll provide an example of how I fixed Sublime Text, rinse and repeat for any other electron app you have installed and if needed.</p>
<pre>
$ locate sublime_text.desktop
/usr/share/applications/sublime_text.desktop
vi /usr/share/applications/sublime_text.desktop
</pre><p>
When you have opened up the file, find the Exec= part and insert --disable-gpu like this</p>
<pre>
Version=1.0
Type=Application
Name=Sublime Text
GenericName=Text Editor
Comment=Sophisticated text editor for code, markup and prose
Exec=/opt/sublime_text/sublime_text --disable-gpu %F
Terminal=false
MimeType=text/plain;
Icon=sublime-text
Categories=TextEditor;Development;
StartupNotify=true
Actions=Window;Document;
</pre><p>
That's it, hopefully this will get you smooth responsive window resizing restored while we wait for a fix from the NVIDIA and/or Chrome/Chromium teams.</p>
<p>Happy Hacking!</p>
</div></div></div><section class="field field-name-field-tags field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Tags:&nbsp;</h2><ul class="field-items"><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/148" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Ubuntu</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/6" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Linux</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/155" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">GPU</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/156" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Fix</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/157" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Window Resizing</a></li></ul></section>Fri, 03 Feb 2017 20:21:13 +0000SneWs92 at https://grenangen.sehttps://grenangen.se/node/92#commentsUbuntu 16.04 WiFi issues - How to perhaps fix it for you as well...https://grenangen.se/node/86
<div class="field field-name-field-image field-type-image field-label-hidden view-mode-rss"><div class="field-items"><figure class="clearfix field-item even" rel="og:image rdfs:seeAlso" resource="https://grenangen.se/sites/default/files/styles/large/public/field/image/logo-ubuntu_cof-orange-hex.png?itok=tQ_kKf8i"><img typeof="foaf:Image" class="image-style-large" src="https://grenangen.se/sites/default/files/styles/large/public/field/image/logo-ubuntu_cof-orange-hex.png?itok=tQ_kKf8i" width="285" height="285" alt="" /></figure></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"><div class="field-items"><div class="field-item even" property="content:encoded"><p>There have been plenty of reports regarding WiFi issues on Ubuntu 16.04. The majority of issues seems to stem from suspend/resume issues where the network would not re-connect, show the wrong icon in the top bar or similar.</p>
<p>The temporary workaround for this is to restart the network manager if you have no network at all, or, if you have network but the nm applet is showing the wrong status, just restart the nm applet. </p>
<p>Restart network manager.</p>
<pre>sudo service network-manager restart</pre><p>
Restart the nm applet.</p>
<pre>killall nm-applet &amp;&amp; nm-applet &amp;</pre><h3>How to fix it</h3>
<p>So, this might or it might not work for you dep. on what issue you've been experiencing. But this did solve it for me on two different laptops.</p>
<p>Lets start with figuring out what WiFi chip we have.</p>
<pre>sudo lshw -class network</pre><p>
The result should look something like this:</p>
<pre>
snews@TuxBook:~$ sudo lshw -class network
*-network
description: Wireless interface
product: Wireless 7265
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlp2s0
version: 59
serial: 60:57:18:78:f9:92
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-28-generic firmware=16.242414.0 ip=192.168.1.20 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn
resources: irq:49 memory:f7000000-f7001fff
</pre><p>
With the above information available to us we can go to work and try to solve the resume from suspend issue.</p>
<pre>sudo vi /etc/pm/config.d/config</pre><p>
In this file, paste the following</p>
<pre>SUSPEND_MODULES="iwlwifi wlp2s0" </pre><p>
The values for the suspend_modules dep. on the output from the lshw command. In my case I see that my driver is named iwlwifi and that the logical name for my chip is wlp2s0. Hence I add those to the suspend_modules line.</p>
<p>Now, issue a restart of the network manager</p>
<pre>sudo service network-manager restart</pre><p>
Now you should be able to suspend your laptop and when you resume it, WiFi should get reconnected automatically, and you should see the correct network type indicator in the nm applet.</p>
<p>The above might also work for you, so give it a try and see what happens.</p>
<p>UPDATE: It seems that as of 16.04.1 this is not an issue for me any more. </p>
<p>Resources:<br /><a href="http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues">http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues</a> - This details the /etc/pm/config.d/config config, but I had to modify it a little bit to make it work on my two laptops. </p>
</div></div></div><section class="field field-name-field-tags field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Tags:&nbsp;</h2><ul class="field-items"><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/6" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Linux</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/148" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Ubuntu</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/149" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">WiFI</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/150" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Troubleshooting</a></li></ul></section>Fri, 08 Jul 2016 19:17:18 +0000SneWs86 at https://grenangen.sehttps://grenangen.se/node/86#commentsFixing SUSE Tumbleweed Live ISO boot hanghttps://grenangen.se/node/85
<div class="field field-name-field-image field-type-image field-label-hidden view-mode-rss"><div class="field-items"><figure class="clearfix field-item even" rel="og:image rdfs:seeAlso" resource="https://grenangen.se/sites/default/files/styles/large/public/field/image/Tumbleweed-black-green.png?itok=Gc1wN1yu"><img typeof="foaf:Image" class="image-style-large" src="https://grenangen.se/sites/default/files/styles/large/public/field/image/Tumbleweed-black-green.png?itok=Gc1wN1yu" width="480" height="203" alt="" /></figure></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"><div class="field-items"><div class="field-item even" property="content:encoded"><p>I had some issues with the SUSE Tumbleweed live image when booting from a USB stick. I used the live-fat-stick (<a href="https://github.com/cyberorg/live-fat-stick">https://github.com/cyberorg/live-fat-stick</a>) from Ubuntu to create my USB stick.<br />
If you get a hang during boot where Journaling won't complete you most likely are hitting this issue. What happens here is that it tries to mount a persistence partition, and this will fail and it will just try and try again without succeeding...</p>
<div style="clear:both">
To work around this issue you need to edit the grub boot config and add the following line.
</div>
<pre style="clear:both">
kiwi_hybridpersistent=no
</pre><p>This will disable the step of trying to mount the persistent partition.</p>
</div></div></div><section class="field field-name-field-tags field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Tags:&nbsp;</h2><ul class="field-items"><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/47" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">SUSE</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/6" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Linux</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/146" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Tumbleweed</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/147" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Kiwi</a></li></ul></section>Sun, 17 Jan 2016 21:31:41 +0000SneWs85 at https://grenangen.sehttps://grenangen.se/node/85#commentsRunning Mono from crontabhttps://grenangen.se/node/78
<div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"><div class="field-items"><div class="field-item even" property="content:encoded"><p>When I tried to get crontab to execute one of my mono compiled assemblies it failed with the error of not being able to resolve the assembly. The problem, after some investigation boiled down to the very simple fact of it not executing the script from the expected working directory. Easy enough to fix, just have crontab execute a cd into the working directory, and from there, execute with a relative path. Problem solved.</p>
<p><b>This is the shell script that I’m invoking from crontab:</b></p>
<pre>
#!/bin/sh
mono --runtime=v4.0.30319 MonoDaemon.exe "/home/username/project/worker/logs"
</pre><p><b>And this was my initial crontab entry:</b></p>
<pre>*/15 * * * * /home/username/project/worker/my-daemon.sh</pre><p><b>And this is the way to get it to actually execute from the expected working folder:</b></p>
<pre>*/15 * * * * ( cd /home/username/project/worker &amp;&amp; ./daemon.sh )</pre><p>Notice the parenthesizes and the &amp;&amp;, this allows cron to first switch directory followed by executing the script. Problem solved!</p>
<p>So if you ever have problem scheduling a Mono executable from crontab, check your expected working folder to allow the mono runtime to be able to resolve your assemblies properly.
</p>
</div></div></div><section class="field field-name-field-tags field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Tags:&nbsp;</h2><ul class="field-items"><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/7" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Mono</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/142" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">crontab</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/6" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Linux</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/19" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Development</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/143" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Scheduling</a></li></ul></section>Tue, 25 Jun 2013 12:26:55 +0000SneWs78 at https://grenangen.sehttps://grenangen.se/node/78#commentsopenSUSE 12.1 - Soon to be releasedhttps://grenangen.se/node/68
<div class="field field-name-field-image field-type-image field-label-hidden view-mode-rss"><div class="field-items"><figure class="clearfix field-item even" rel="og:image rdfs:seeAlso" resource="https://grenangen.se/sites/default/files/styles/large/public/field/image/Geeko-button-bling3.png?itok=WY-GwHIN"><img typeof="foaf:Image" class="image-style-large" src="https://grenangen.se/sites/default/files/styles/large/public/field/image/Geeko-button-bling3.png?itok=WY-GwHIN" width="256" height="256" alt="" /></figure></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"><div class="field-items"><div class="field-item even" property="content:encoded"><p>It will soon be released, and I'm already up N running 12.1 RC 1, it's performing well after some minor tweaks.</p>
<p>First of all, if your running a NVIDIA gfx card, you might have some issues booting you're machine, but that's easy to fix, in Grub, add the following as a boot flag: </p>
<p><code>nomodeset</code></p>
<p>After working around that, it's just a matter of adding it as a persistent option to Grub. The easiest way to do is to open YaST and go into boot, select your boot entry and add nomodeset at the end of the boot options.</p>
<p>It's a good sign that most stuff just works in this RC, and I believe that the new openSUSE release will be able to pull over some Ubuntu users due to Unity not being all that good.</p>
</div></div></div><section class="field field-name-field-tags field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Tags:&nbsp;</h2><ul class="field-items"><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/8" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">openSuSE</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/6" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Linux</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/121" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Desktop</a></li></ul></section>Sun, 23 Oct 2011 21:46:33 +0000SneWs68 at https://grenangen.sehttps://grenangen.se/node/68#commentsopenSUSE 11.4 GMhttps://grenangen.se/node/40
<div class="field field-name-field-image field-type-image field-label-hidden view-mode-rss"><div class="field-items"><figure class="clearfix field-item even" rel="og:image rdfs:seeAlso" resource="https://grenangen.se/sites/default/files/styles/large/public/field/image/suse-logo-big.png?itok=C6vNG0ja"><img typeof="foaf:Image" class="image-style-large" src="https://grenangen.se/sites/default/files/styles/large/public/field/image/suse-logo-big.png?itok=C6vNG0ja" width="180" height="180" alt="" /></figure></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"><div class="field-items"><div class="field-item even" property="content:encoded"><p>After the dust has settled and I've used the GM release for a couple of days I thought that I would write up what does and doesn't work for my part. </p>
<p><b>Stuff that doesn't work</b><br />
VMWare workstation; It will not compile the needed modules after install. A patch was made for 11.4 RC1 if I remember correctly, but it doesn't seem to be updated to support the GM release yet. </p>
<p><b>Stuff that just works</b><br />
Amazingly enough, the prop. ATI drivers works without a hitch for my part (Radeon HD 5850). It's the first time ever that it just works out of the box by downloading and executing the installer from the AMD/ATI website. </p>
<p>KDE 4.6 is a breeze to use, everything is working out of the box, and it looks smashing! You won't regret running KDE this time. At least I don't.</p>
<p>Well, since everything is working as it should with 11.4 there's not much more to say. Just a very big thanks from my part to Novell and the openSUSE developers and the community!</p>
</div></div></div><section class="field field-name-field-tags field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Tags:&nbsp;</h2><ul class="field-items"><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/8" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">openSuSE</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/6" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Linux</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/33" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">KDE</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/45" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">ATI</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/49" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Virtualization</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/74" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">VMWare</a></li></ul></section>Sun, 13 Mar 2011 14:59:32 +0000SneWs40 at https://grenangen.sehttps://grenangen.se/node/40#commentsopenSUSE 11.4 < 24h to releasehttps://grenangen.se/node/39
<div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"><div class="field-items"><div class="field-item even" property="content:encoded"><p>In about 21 hours, writing time. openSUSE 11.4 will be released into the wild. Finally. This is one release I've really waited for. Aldo I have been running it on my main machine for the past week via the RC2 release, but it's always nice to be able to do that final upgrade to the stable GM release.</p>
<p>So, what's new in openSUSE 11.4? Well, a lot, as usual =)</p>
<p> * KDE 4.6<br />
* Kernel 2.6.37<br />
* LibreOffice (First stable release)<br />
* And many many more...</p>
<p>KDE 4.6 is really something special. First of, it just works, second... well, it's just so gorgeous to look at. And maybe the most important part, it doesn't get in your way, it just is there, ready to serve in a very beautiful and rapid way!</p>
<p>If you are like me, a long time openSUSE/SUSE Linux user, tomorrow is a day to note in the calendar. And even celebrate.</p>
<p>Happy openSUSE 11.4 to everyone!</p>
</div></div></div><section class="field field-name-field-tags field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Tags:&nbsp;</h2><ul class="field-items"><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/8" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">openSuSE</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/6" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Linux</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/33" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">KDE</a></li></ul></section>Wed, 09 Mar 2011 20:06:20 +0000SneWs39 at https://grenangen.sehttps://grenangen.se/node/39#commentsopenSUSE 11.4https://grenangen.se/node/37
<div class="field field-name-field-image field-type-image field-label-hidden view-mode-rss"><div class="field-items"><figure class="clearfix field-item even" rel="og:image rdfs:seeAlso" resource="https://grenangen.se/sites/default/files/styles/large/public/field/image/opensuse-logo_sm-300x193.png?itok=zTAZV_28"><img typeof="foaf:Image" class="image-style-large" src="https://grenangen.se/sites/default/files/styles/large/public/field/image/opensuse-logo_sm-300x193.png?itok=zTAZV_28" width="300" height="193" alt="" /></figure></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"><div class="field-items"><div class="field-item even" property="content:encoded"><p>Soon, a new version of openSUSE will be released. It will bring many nice improvements, but for my part, the most important one is KDE 4.6. I think that I might have used this line before, but it's really what I do feel about KDE. "KDE 4 is finally ready for mainstream usage". KDE 4 in it's early releases was horrible to say the least.</p>
<p>KDE 4.6 is so much easier to use, and the overall experience just feels awesome, it doesn't get in my way while working with something, it just works and enables me to work in a more efficient way.</p>
<p><a href="http://www.kde.org/announcements/4.6/screenshots/46-w09.png"><img src="http://www.kde.org/announcements/4.6/screenshots/46-w09.png" style="width:510px;height:307px;" alt="" title="" /></a></p>
<p>If you are a Ubuntu user, try openSUSE, you will most probably never go back to Ubuntu =). And most importantly, you will realize how limited Gnome actually is.</p>
<p>11.4 also includes the almost famous 200 line kernel patch that improves UI responsiveness and desktop experience: <a href="http://www.osnews.com/story/24042/The_200_Line_Linux_Kernel_Patch_that_Does_Wonders">http://www.osnews.com/story/24042/The_200_Line_Linux_Kernel_Patch_that_D...</a></p>
<p>Read about the RC release <a href="http://news.opensuse.org/2011/02/26/opensuse-11-4-rc2-steps-out/" target="_blank">here</a></p>
</div></div></div><section class="field field-name-field-tags field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Tags:&nbsp;</h2><ul class="field-items"><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/8" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">openSuSE</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/6" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Linux</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/73" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">11.4</a></li></ul></section>Tue, 01 Mar 2011 21:37:23 +0000SneWs37 at https://grenangen.sehttps://grenangen.se/node/37#commentsA brand spanking new sitehttps://grenangen.se/node/34
<div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"><div class="field-items"><div class="field-item even" property="content:encoded"><p>I have finally finalized the migration to <a href="http://drupal.org/" target="_blank">Drupal 7</a>. The server has also moved to a new cloud based server provided by <a href="http://www.linode.com/" target="_blank">Linode</a>.</p>
<p>Drupal 7 is, pure joy to work with, it has been drastically improved since last time I used Drupal (6.1.x something) . Go get your <a href="http://drupal.org/download" target="_blank">own copy</a> and try it out! =)</p>
<p>The Drupal theme I use is developed by <a href="http://www.kiwi-themes.com/" target="_blank">http://www.kiwi-themes.com/</a></p>
<p>If you are looking for a cheap and really cool Linux based cloud service, look no further. Linode is the answer, it just blows me away seeing how easy they have made setting up a new Linux based server, from registration and payment to a server up and running,
</p></div></div></div><section class="field field-name-field-tags field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Tags:&nbsp;</h2><ul class="field-items"><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/6" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Linux</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/70" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Cloud</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/19" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Development</a></li><li class="field-item odd" rel="dc:subject"><a href="/taxonomy/term/71" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">Drupal</a></li><li class="field-item even" rel="dc:subject"><a href="/taxonomy/term/72" typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">CMS</a></li></ul></section>Mon, 28 Feb 2011 21:14:25 +0000SneWs34 at https://grenangen.sehttps://grenangen.se/node/34#comments