• can lead to health issues: it forces the user to assume a bad position in front of the screen; this can affect the eyes and the backbone; It's bad enough many people have a bad posture in front of the computer as it is, no need to pump up Scoliosis' position in the laundry list of modern day health risks

The numpad forces eye focus and users' hands to be way off center. The touchpad looks as if it was thrown to the side by accident Note how the designer tried to offset the misalignment forced by the numpad by "positioning" the touchpad closer to center, but not in line with the space bar (and the keyboard)

• ugly design: it simply looks ugly; why do people think Apple didn't jump into this stupid bandwagon? Because it's ugly design!

Without numpad the position is almost perfect! The symmetry of the laptop improves on the design. Notice how the touchpad is also centered.

• the numpad is useless for the vast majority of people, and those who need numpads, already use them at desktop (keyboard) or, can buy numpads
• it's more expensive to manufacture (more moving parts, more complex wiring and more expensive materials - plastic is cheaper than plastic+copper+rubber)
• less resilient: more ways to fail, higher risk to get liquids inside
• bad mechanical design: wider keyboard means less distance from the edge to the keyboard, which can mean a more fragile case
• makes the laptop heavier: the plastic or material that covers the keys would be enough to cover the insides; the extra rubber, wiring, support etc, add extra weight
• it kills the opportunity to use the real estate for other useful things (or things which improve the overall design): speakers, volume keys, finger print readers, other special function keys, LEDs or other output devices

1. You use global variables This would have to be both the most common idiom that just makes my teeth grind. Defined types exist for a bloody reason. Global variables make it incredibly difficult to reason about what is going to happen when I use a particular global variable (see also You don t write documentation ), and I get no feedback if I typo a global variable name. Add in a healthy heaping of lack of namespacing , and you ve basically guaranteed that your module will be loudly cursed.

2. You use parameterised classes I ve never managed to work out why parameterised classes even exist. They ve got all the problems of regular classes, as well as all the problems of types. There was a fantastic opportunity with parameterised classes to fix some of the really annoying things about regular resources, such as doing conflict checking on parameters and only barfing if there was a conflict but no, if you define the same class twice, even with identical parameters, Puppet will smack you on the hand and take away your biscuit. FFFFFFUUUUUUUUUUUU-

3. You fail at using fail() Modules are supposed to be reusable. That s their whole reason for existence. One of the benefits of Puppet is that you can provide an OS-independent interface for configuring something. However, unless you re some absolute God of cross-platform compatibility, you will only be writing your module to support those OSes or distros that you, personally, care about. That s cool if you don t know anything about OS X, you probably shouldn t be guessing at how to support something on that platform anyway. However, when you do have some sort of platform-specific code, for the love of pete, have a default or else clause that calls fail() with a useful and descriptive error message, to indicate clearly that you haven t included support for whatever environment the module s being used in. Failing to do this can cause some really spectacular explosions, because the rest of your module assumes that certain things have been done in the platform-specific code, and when it hasn t hoo boy.

4. You don t write documentation Yes, it isn t easy to write good documentation. I know that. But without documentation, your module is going to be practically unuseable. So if you don t have docs, your module is basically useless. Well done, you.

5. You have undeclared dependencies This also includes declaring your dependencies in a non-machine-parseable manner; I m not going to grovel through your README for the list of other modules I might need; I have machines to do that kind of thing for me. If I try to use your module, and it craps out on trying to reference some sort of type or class that doesn t appear at all related to your module, I will call into question your ancestry, and die a little more inside.

6. You use common packages without even trying to avoid the pitfalls OK, to be fair this is, ultimately, Puppet s grand fuckup, not yours, but you at least need to pretend to care There is no sane, standardised way in Puppet for multiple modules to install the same package. Let s say that a module I write needs to have a compiler. So I package "gcc": . Then someone else s module also wants a compiler, so it also package "gcc": . FWAKOOM! says Puppet. What the fuck? says the poor sysadmin, who just wanted both a virtualenv and an RVM environment on the one machine. Basically, using packages is going to make your module suck. Does that mean that this makes wide distribution of a large repository of modules written by different people nigh-on impossible? Yes. Fantastic.

1. You use global variables This would have to be both the most common idiom that just makes my teeth grind. Defined types exist for a bloody reason. Global variables make it incredibly difficult to reason about what is going to happen when I use a particular global variable (see also You don t write documentation ), and I get no feedback if I typo a global variable name. Add in a healthy heaping of lack of namespacing , and you ve basically guaranteed that your module will be loudly cursed.

2. You use parameterised classes I ve never managed to work out why parameterised classes even exist. They ve got all the problems of regular classes, as well as all the problems of types. There was a fantastic opportunity with parameterised classes to fix some of the really annoying things about regular resources, such as doing conflict checking on parameters and only barfing if there was a conflict but no, if you define the same class twice, even with identical parameters, Puppet will smack you on the hand and take away your biscuit. FFFFFFUUUUUUUUUUUU-

3. You fail at using fail() Modules are supposed to be reusable. That s their whole reason for existence. One of the benefits of Puppet is that you can provide an OS-independent interface for configuring something. However, unless you re some absolute God of cross-platform compatibility, you will only be writing your module to support those OSes or distros that you, personally, care about. That s cool if you don t know anything about OS X, you probably shouldn t be guessing at how to support something on that platform anyway. However, when you do have some sort of platform-specific code, for the love of pete, have a default or else clause that calls fail() with a useful and descriptive error message, to indicate clearly that you haven t included support for whatever environment the module s being used in. Failing to do this can cause some really spectacular explosions, because the rest of your module assumes that certain things have been done in the platform-specific code, and when it hasn t hoo boy.

4. You don t write documentation Yes, it isn t easy to write good documentation. I know that. But without documentation, your module is going to be practically unuseable. So if you don t have docs, your module is basically useless. Well done, you.

5. You have undeclared dependencies This also includes declaring your dependencies in a non-machine-parseable manner; I m not going to grovel through your README for the list of other modules I might need; I have machines to do that kind of thing for me. If I try to use your module, and it craps out on trying to reference some sort of type or class that doesn t appear at all related to your module, I will call into question your ancestry, and die a little more inside.

6. You use common packages without even trying to avoid the pitfalls OK, to be fair this is, ultimately, Puppet s grand fuckup, not yours, but you at least need to pretend to care There is no sane, standardised way in Puppet for multiple modules to install the same package. Let s say that a module I write needs to have a compiler. So I package "gcc": . Then someone else s module also wants a compiler, so it also package "gcc": . FWAKOOM! says Puppet. What the fuck? says the poor sysadmin, who just wanted both a virtualenv and an RVM environment on the one machine. Basically, using packages is going to make your module suck. Does that mean that this makes wide distribution of a large repository of modules written by different people nigh-on impossible? Yes. Fantastic.

i  = j  = k  = ijk = -1

r + ix + jy + kz

q = (r + ix + jy + kz)
q* = (r - ix - jy - kz)

  q   =  (qq*) =  (r  + x  + y  + z )

  u   = 1

q = 0 + ivx + jvy + kvz

r = cos  /2 + u sin  /2

q  = r q r*

q  = s (r q r*) s*
    = (sr) q (r*s*)
    = (sr) q (sr)*
t   = s r
q  = t q t*

g = (0, ax, ay, az) / norm(0, ax, ay, az)
v = (0, 0, 0, 1)

a = g   v
  = u sin  

cos   = g   v

cos  /2 =  ((1 + cos  )/2)
sin  /2 =  ((1 - cos  )/2)

q = cos  /2 + u sin   sin  /2 / sin  

   cos x cos y cos z + sin x sin y sin z +
i (sin x cos y cos z - cos x sin y sin z) +
j (cos x sin y cos z + sin x cos y sin z) +
k (cos x cos y sin z - sin x sin y cos z)

sin x   x
cos x   1

1 + xyz + i (x - yz) + j (y + xz) + k (z - xy)

1 + ix + jy + kz

g = r (0 0 0 1) r*

This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.

• #707442 src:scim-chewing: "scim-chewing: FTBFS: conftest.c:68: undefined reference to shl_load'"
  add upstream patch, fixing version requirement, upload to DELAYED/2
• #716759 openshot: "openshot: mlt 0.9.0-1 renames python-mlt5 => python-mlt"
  fix dependencies, upload to DELAYED/2
• #723867 dpkg-sig: "dpkg-sig: FTBFS with perl 5.18: POD errors"
  fix POD for perl 5.18 compatibility, upload to DELAYED/2
• #723869 src:freetable: "src:freetable: FTBFS with perl 5.18: POD errors"
  fix POD for perl 5.18 compatibility, upload to DELAYED/2
• #723969 mapivi: "mapivi: Program does not start by too may errors"
  add patch for perl 5.18 compatibility, upload to DELAYED/2
• #724054 src:exrtools: "exrtools: FTBFS: no dependency information found for /usr/lib/x86_64-linux-gnu/libpng12.so.0 (used by debian/exrtools/usr/bin/pngtoexr)"
  tag unreproducible, then closed by submitter
• #724915 src:gpaint: "gpaint: FTBFS: image_processing.o: undefined reference to symbol 'log@@GLIBC_2.2.5'"
  add patch from Ubuntu / Daniel T Chen, upload to DELAYED/2
• #725526 src:getdata: "getdata: FTBFS: dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision"
  propose a solution
• #725534 src:gummi: "gummi: FTBFS: automake errors"
  propose a patch, accepted by maintainer
• #725554 src:pimd: "pimd: FTBFS: dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision"
  propose solutions
• #725570 src:pgfincore: "pgfincore: FTBFS: dpkg-buildpackage: error: dpkg-source -b pgfincore-1.1 gave error exit status 255"
  propose a patch
• #725591 src:ruby-passenger: "ruby-passenger: FTBFS: make[1]: /usr/bin/ruby1.8: Command not found"
  propose a patch
• #725599 src:squid3: "squid3: FTBFS: cp: cannot stat '/ PKGBUILDDIR /debian/tmp/usr/share/man/man8/basic_db_auth.8': No such file or directory"
  propose a patch
• #726730 tuxguitar: "tuxguitar: uninstallable in sid"
  fix dependencies (pkg-java)

#!/bin/sh
set -e # Exit on first error
rootdir="$1"
cd "$rootdir"
cat <<EOF > etc/apt/sources.list
deb http://http.debian.net/debian/ jessie main contrib non-free
EOF
# Install non-free binary blob needed to boot Raspberry Pi.  This
# install a kernel somewhere too.
wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
    -O $rootdir/usr/bin/rpi-update
chmod a+x $rootdir/usr/bin/rpi-update
mkdir -p $rootdir/lib/modules
touch $rootdir/boot/start.elf
chroot $rootdir rpi-update

sudo ./vmdebootstrap \
    --variant minbase \
    --arch armel \
    --distribution jessie \
    --mirror http://http.debian.net/debian \
    --image test.img \
    --size 600M \
    --bootsize 64M \
    --boottype vfat \
    --log-level debug \
    --verbose \
    --no-kernel \
    --no-extlinux \
    --root-password raspberry \
    --hostname raspberrypi \
    --foreign /usr/bin/qemu-arm-static \
    --customize  pwd /customize \
    --package netbase \
    --package git-core \
    --package binutils \
    --package ca-certificates \
    --package wget \
    --package kmod

• Rob Walling talked about actual, concrete numbers when discussing his current project's revenues. There's a ton of handwavy stuff out there on the internet, but real numbers are tough to beat. What makes it especially nice is that they also felt "real": they're good numbers, no doubt about it, but not stratospheric, science fiction numbers that leave you feeling like "ok, whatever, but that's not the planet I live on". They're numbers that make you think "maybe, if things go well, I could do that too".
• The number of "I'm from X, but live in Y" people at the conference was high. Irish but live in Spain, American but live in Japan. Or maybe just noticeable because I'm in that category myself. There were people attending from the US, Europe, Japan, South Africa, and even Australia. Impressive!
• Almost all of the speakers had very specific, concrete advice that I can and will apply to LiberWriter, time permitting. I read, and have read, a lot of business books. Most of them are kind of fluffy, truth be told, in that they've got one decent idea, and a lot of filler to turn what could have been a tight, ten-page article into a book. This was quite different in that there were a whole lot of tips and tricks being thrown out.
• Rob's wife Sherry gave a talk about life with an entrepreneur. Having two kids and a wonderful wife myself, it's a point of view that I was very interested in hearing about. Judging from the people I chatted with, this was not your typical "startup" conference with a bunch of 20-somethings with no family and no ties - a lot of the other people attending had kids to think about as they launch their ventures. A question I asked of Rob was how much of a leap he took from consulting to working on his own products, with the answer being that he's actually pretty risk adverse. No Silicon Valley story about betting the house and everything else on the company - apparently, revenues from the web sites and products were good enough that there wasn't even really a leap to make when he quit consulting.
• The size of the conference was just right: enough people that I didn't quite manage to meet everyone, but not so many that it was overwhelming. In downtime between talks, and during dinners, breakfasts, lunch and so on, the speakers were very available to chat with.
• Patrick McKenzie seems to have stumbled into his life's calling as someone working at the border of software and marketing. The amount of advice, anecdotes, and data that he was continually spinning off was incredible. He comes across as being a down-to-earth, approachable, friendly person.
• Part of the balancing act the organizers have to work with is where people are at: some people had an idea but no concrete business. Some of us (me) make some money but not too much. Others have viable businesses that they make enough to live off of, and then there are those who seem pretty much 'set'. It's difficult to find people to speak to each audience without losing some of the others.
• The thing I liked the most about a lot of what was discussed was that it seems realistic. Few people at the conference were from Silicon Valley, and yet... they're successful! I like hearing about success stories that work out really well for the people involved, but still feel like something attainable. People should be looking to emulate the successful guys here, not looking at extreme outliers like Bill Gates or Mark Zuckerberg.
• I'm used to tech conferences, where it's all about the technology. There was very little actual tech talk at MicroConf - it seems like everyone knows their stuff and was interested in learning about marketing, sales, and so on.

**Description**
Linux Malware Detect (LMD) is a malware scanner for Linux released under the
GNU GPLv2 license, that is designed around the threats faced in shared hosted
environments. It uses threat data from network edge intrusion detection systems
to extract malware that is actively being used in attacks and generates
signatures for detection. In addition, threat data is also derived from user
submissions with the LMD checkout feature and from malware community resources.
The signatures that LMD uses are MD5 file hashes and HEX pattern matches, they
are also easily exported to any number of detection tools such as ClamAV.
**Features**
- MD5 file hash detection for quick threat identification
- HEX based pattern matching for identifying threat variants
- statistical analysis component for detection of obfuscated threats (e.g: base64)
- integrated detection of ClamAV to use as scanner engine for improved performance
- integrated signature update feature with -u update
- integrated version update feature with -d update-ver
- scan-recent option to scan only files that have been added/changed in X days
- scan-all option for full path based scanning
- checkout option to upload suspected malware to rfxn.com for review / hashing
- full reporting system to view current and previous scan results
- quarantine queue that stores threats in a safe fashion with no permissions
- quarantine batching option to quarantine the results of a current or past scans
- quarantine restore option to restore files to original path, owner and perms
- quarantine suspend account option to Cpanel suspend or shell revoke users
- cleaner rules to attempt removal of malware injected strings
- cleaner batching option to attempt cleaning of previous scan reports
- cleaner rules to remove base64 and gzinflate(base64 injected malware
- daily cron based scanning of all changes in last 24h in user homedirs
- daily cron script compatible with stock RH style systems, Cpanel & Ensim
- kernel based inotify real time file scanning of created/modified/moved files
- kernel inotify monitor that can take path data from STDIN or FILE
- kernel inotify monitor convenience feature to monitor system users
- kernel inotify monitor can be restricted to a configurable user html root
- kernel inotify monitor with dynamic sysctl limits for optimal performance
- kernel inotify alerting through daily and/or optional weekly reports
- e-mail alert reporting after every scan execution (manual & daily)
- path, extension and signature based ignore options
- background scanner option for unattended scan operations
- verbose logging & output of all actions

    # wget "http://ftp.cyconet.org/debian/sources.list.d/restricted-cyconet.list" \
        -O /etc/apt/sources.list.d/restricted-cyconet.list
    # aptitude update
    # aptitude -t restricted install maldetect

Filed under: English SUSE Weblate 0 comments Flattr this!