nealian

require 'socket'

s = TCPSocket.new("104.131.107.153", 12121)
p s.gets
second_line = false
last_line = []
point = 0
s.each_line do |line|

  puts line

nealian

Keybase proof

I hereby claim:

• I am nealian on github.
• I am wopr (https://keybase.io/wopr) on keybase.
• I have a public key whose fingerprint is B712 B251 1DA2 D19D 150E 72F8 5B5B 790B DC20 AAAE

To claim this, I am signing this object:

nealian

EXCL = 
#Include every .c file that will become an object in EXCL, as well as any other .c files to not make in this dir
C_FILES = $(filter-out $(EXCL),$(wildcard *.c))
PROGRAMS = $(C_FILES:.c=)
# For each main program named <main>.c, make a variable <main>_OBJS with .o files to add,
# and <main>_LIBS with libraries to link with -l



# Everything after this is generic

nealian

// based on work from http://cs.baylor.edu/~donahoo/practical/CSockets/practical/
/*
 *   C++ sockets on Unix and Windows
 *   Copyright (C) 2002
 *
 *   This program is free software; you can redistribute it and/or modify
 *   it under the terms of the GNU General Public License as published by
 *   the Free Software Foundation; either version 2 of the License, or
 *   (at your option) any later version.
 *

nealian

sysvinit-jar buttemplate

This is a but.sh template for creating /etc/rc.d/init.d scripts for Java jar files. (Slightly based on the EPEL init-script template, and intended for an el6 machine, though I'm sure it would work with many, many more systems.)

Other daemons?

After making this template, of course I realized that this could very easily be modified to do any other daemon, so I did just that, though it was honestly pretty trivial.

Prerequisites

This, of course, requires but.sh.

nealian

sysvinit buttemplate

This is a but.sh template for creating /etc/rc.d/init.d scripts. (Slightly based on the EPEL init-script template, and intended for an el6 machine, though I'm sure it would work with many, many more systems.)

This is actually a modification of a different gist, for jar init scripts on el6, but I soon realized that it could be used for any forking daemon just fine.

Prerequisites

This, of course, requires but.sh The template itself requires only bash and gnu-coreutils.

nealian

.desktop file buttemplate

This is a but.sh template for creating .desktop files, which are used for menu entries and links in most Linux desktop environments. Built against the specification

Prerequisites

This, of course, requires but.sh The template itself requires only bash and gnu-coreutils.

Variables

Required:

• ENTRY_TYPE -- one of Application, Link, or Directory

nealian

systemd-unit file buttemplate

This is a but.sh template for creating a systemd unit file (.automount, .device, .mount, .path, .scope, .service, .slice, .socket, .swap, .timer, ...)

Prerequisites

This, of course, requires but.sh The template itself requires only bash and gnu-coreutils.

Variables

The valid section names are:

nealian

# Disk DescriptorFile
version=1
CID=${vmdk_cid}
parentCID=ffffffff
createType="fullDevice"

# Extent description
RW ${vmdk_sectors} FLAT "${vmdk_dev}" ${vmdk_skip:-0}

# The disk Data Base 

nealian

<?xml version=\"1.0\"?>
<VirtualBox xmlns=\"http://www.innotek.de/VirtualBox-settings\" version=\"1.14-linux\">
  <Machine uuid=\"{${vbox_uuid}}\" name=\"${vbox_name}\" OSType=\"${vbox_OSType}\" snapshotFolder=\"${vbox_snapshotFolder}\">
    <Description>${vbox_Description}</Description>
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid=\"{${vbox_vmdk_uuid}}\" location=\"${vbox_vmdk_location}\" format=\"VMDK\" type=\"Normal\"/>
      </HardDisks>
    </MediaRegistry>
    <ExtraData>