#kde #neon is not a fullblown distribution by now. It is based on a minimal installation of ubuntu 16.04 LTS and delivers nothing but a plain ubuntu base with an up2date plasmashell on it. no applications and other usefull additions whatsoever!!
you will have to install everything by hand – starting with “konsole” and “gtk3-breeze-engines” or things like “kate” and other stuff.
Therefore it’s probably a good idea to just use plain #kubuntu and add the neon package archive.
DisplayChdir .message true
# Lock all the users in home directory, ***** really important *****
Umask 022 022
First, determine which NIC will be used, and then check whether it supports the Magic Packet™ using
sudo ethtool <NIC>
where <NIC> is the device name of your NIC, e.g. eth0. This command will output some information about your the capabilities of your NIC. If this output contains a line similar to the following:
Supports Wake-on: <letters>
where <letters> contains the letter g, the NIC should support the WoL Magic Packet™ method (for the other letters look at man ethtool).
Enabling WoL in the NIC
To check whether WoL is enabled in the NIC, one could use
sudo ethtool <NIC>
and look for
If <letters> contains g and not d, then Magic Packet™ is enabled. However, if <letters> does contain d, WoL needs to be enabled by running the following command:
sudo ethtool -s <NIC> wol g
On most systems, issuing this command is required after each boot. If the system’s networking is configured via ifupdown, then it is easy to add the line up ethtool -s <NIC> wol g below the interface’s configuration stanza in /etc/network/interfaces. For example:
shahar@shahar-backup:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
iface lo inet loopback
# The primary network interface
iface eth0 inet static
up ethtool -s eth0 wol g
This will ensure that WoL is enabled in the NIC on each boot. Fore more information see the interfaces manual.
Test WoL by powering off the system and trying to send it the magic packet using:
i just released my first html5 android game (ever)
it is called “cool cows on ice” and features a cow (obviously) and some crazy kamikaze penguins that may, or may not help you finish a level…
you can touch and hold the cow and then throw it as precisely as you can into the target area.
the game is build completely with the amazing phaser.js framework and p2 physics
i used crosswalk 10 and intel xdk to package it
it also has ads (one interstitial in the menu – only once) and non-intrusive banners in the score screen – and the option to remove them
almost all the graphics and animations are created in gimp
the audio tracks are composed by good friend of mine (dj körner)
the –language part makes sure that it runs through (in my case) even with some “reserved” names as custom variable names.. (i am using the phaser framework and “static” for example is a common (otherwise not allowed) name for an attribute)
using advanced_optimations instead of simple_optimations would lead to a more obfuscated output but is not working properly if you include several other js files because it’s heavily renaming everything – starting with classes, methods, attributes, etc.
Comments Off on minimize you js files with closure-compiler
This is meant as response to all those Blogs that constantly repost the bullshit-comparison-chart that GFI “invented” – especially to this one. http://mywindows8.org/ios-os-x-beats-windows-become-vulnerable-operating-systems-2014/
Here is a more accurate chart:
FYI – bugs like shellshock (bash) seem to be included in the linux-kernel numbers which is of course total nonsense but i managed to resist adding the Internet Explorer vulnerabilities (242) to the numbers. I didn’t want to offend windows users. ; )
Please stop comparing public vulnerabilities of different importance of opensource systems to closed source systems. Guess why the number of LOW vulnerabilities is ? (or 0 in the original chart) – because the author doesn’t know… did you really think there wasn’t even ONE single unimportant flaw in windows fixed in 2014 ?
This reminds me of the “average zero-day response time” chart of 2012 where they just happened to include already fixed bugs in linux just because the current ones were related to them to tweak the numbers…
quote from an internal MS document:
“[t]o control mental output you have to control mental input. Take control of the channels by which developers receive information, then they can only think about the things you tell them. Thus, you control mindshare!”
Comments Off on Windows beats iOS and OS X and Linux and becomes the most vulnerable operating system of 2014