| #include <string> | |
| #include <string.h> | |
| #include <fcntl.h> | |
| #include <cstdlib> | |
| #include <iostream> | |
| #include <fstream> | |
| #include <stdint.h> | |
| #include <vector> | |
| #include <glib.h> |
| /** | |
| * AD.c - Attachment dumper. | |
| *** | |
| * | |
| * This is a simple script which is designed to write out the attachments | |
| * from an email to disk. | |
| * | |
| * Compile like so: | |
| * | |
| * $ gcc -Wall -O2 ad.c -o ad $(pkg-config --libs --cflags gmime-2.6) |
| #!/bin/sh | |
| # | |
| # This is a simple alternative to /usr/bin/lsb_release which | |
| # doesn't require python. | |
| # | |
| # If /etc/os-release exists then we use that to output data | |
| # in a compatible format to the original lsb_release utility. | |
| # | |
| # I consider this script trivial enough to be in the public-domain, | |
| # but any patches or suggestsions will be welcome. |
| package Chronicle::Plugin::Generate::StaticPages; | |
| use strict; | |
| use warnings; | |
| =begin doc | |
| Create a table for the static-pages. |
| # | |
| # Build the driver. | |
| # | |
| all: driver | |
| clean: | |
| rm -f *.o core driver || true |
| /** | |
| * Launch a terminal when Ctrl-Alt-T is pressed. | |
| * | |
| * gcc -o ctrl-alt-t ctrl-alt-t.c -lX11 | |
| * | |
| * Steve | |
| * -- | |
| * | |
| * PS. Use xbindkeys like a normal person ;) | |
| * |
| package Power::Outlet::Osram; | |
| use strict; | |
| use warnings; | |
| use base qw{Power::Outlet::Common::IP}; | |
| use Device::Osram::Lightify::Hub; | |
| our $VERSION='0.16'; |
| /* | |
| * hashcheck_lsm.c - Steve Kemp | |
| * | |
| * This is a security module which is designed to prevent | |
| * the execution of unknown or (maliciously) altered binaries. | |
| * | |
| * This is achieved by computing an SHA1 digest of every | |
| * binary before it is executed, then comparing that to the | |
| * (assumed) known-good value which is stored as an extended | |
| * attribute alongside the binary. |
| #!/usr/bin/m4 | |
| # Define a macro for a tinc-protocol test | |
| define(`tinc', `$1 must run tcp with port 655 with banner "^0 \S+ 17$"') | |
| # builder.steve.org.uk | |
| tinc(`176.9.183.97') | |
| # master.steve.org.uk | |
| tinc(`176.9.183.98') |
Many linters are external (shell) commands you can invoke with a filename, and which exit with non-zero status-codes on failure.
The problems a given linter will report upon will obviously vary, but actually executing a linter automatically is broadly tool-agnostic, so automating is pretty simple: