/usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require': libruby19.so.1.9: cannot open shared object file: No such file or directory - /usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/narray.so (LoadError)
from /usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from ./image_stack.rb:8:in `'

now one might be forgiven in thinking that this means that ruby cant find the file

  narray.so  

but this isnt actually the case.

ldd /usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/narray.so
        linux-vdso.so.1 =>  (0x00007fff82bff000
        libruby19.so.1.9 => not found
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f65c7b1c000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f65c775e000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f65c805a000)

so next thing to do is to look to see if you have a libruby19.so.1.9 somewhere on your system

 >locate libruby19.so.1.9

in my case the answer was no, when a library is missing the first place it looks to find it is the current directory, so instead of adding complication in the

/usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ 

directory. i just made a link

cd /usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/
ln -s /usr/local/rvm/rubies/ruby-1.9.3-p194/lib/libruby.so.1.9.1 ./libruby19.so.1.9
ldd ./narray.so
        linux-vdso.so.1 =>  (0x00007fff8c3ff000)
        libruby19.so.1.9 => /usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/libruby19.so.1.9 (0x00007f7411580000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f7411275000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7410eb7000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f7410c9a000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f7410a92000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f741088d000)
        libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f7410654000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f7411bef000)

which fixed my issues, now why narray didnt use the right name the lib in the first place i dont know….

grub rescue>

which is not the most helpful of prompts in the world…

first of all, find your disk

ls

it’ll look like (hdx,y)
but perhaps the

 ,y 

wont be visible.
if so try a

 1 

set prefix=(hd0,1)/grub

then try

insmod (hd0,1)/grub/linux.mod

if that works try adding in a coupld more modules

 insmod ext2.mod 

 insmod gzio.mod 

OK all looks good at this stage i hope.
now were are in grub2 so make sure to set

set root=(hd0,1)
set prefix=(hd0,1)/grub 

use

 ls 

to find out the name of your initrd and vmlinuz files

linux /boot/vmlinuz-3.0.0-1 root=/dev/sda3 ro
initrd /boot/initrd.img-3.0.0-1
boot

and then voilia it should boot appropriately. then rerun grub-setup

source for this came from how to fix grub
Another good resource for grub is Ubuntu grub resource

begin
 location = "Klyuchevskoy"
 local_prefix = "/depot/webcams/from_kasatochi/"
 command_remote="ssh -p 2222 anatexis.net 'find /export/whale/webcam-data/#{location}/*' | sed 's#/export/whale/webcam-data/##g' | grep jpeg > gorilla-filelist.txt"
 command_local="find /depot/webcams/from_kasatochi/#{location}/* | sed 's\##{local_prefix}\#\#g' | grep jpeg > local-filelist.txt"
 system(command_remote)
 system(command_local)
 puts " reading "
 gorilla = File.open('gorilla-filelist.txt', 'rb') { |file| file.read }
 puts "read gorilla"
 local = File.open('local-filelist.txt', 'rb') { |file| file.read }
 puts "read local"
 set_gorilla = gorilla.split("\n")
 set_local = local.split("\n")
 puts set_gorilla.count
 puts set_local.count
 set_final = set_local - set_gorilla
 puts set_final.count
 newFile = File.open("./tar-filelist.txt", "w")
 set_final.each { |item|
 newFile.puts "./#{item}"
 }
 pwd=(%x[pwd]).chomp
 final_command="cd #{local_prefix} && tar --files-from=#{pwd}/tar-filelist.txt -vzc | ssh -p2222 anatexis.net 'tar -vxz -C/export/whale/webcam-data/'"
 puts final_command
 system(final_command)
end

find ./* | grep  svn > exclude.txt
tar cv --file=proj.tar  --exclude-from=./exclude.txt ./trunk


did the job nicely

In ruby I have begun to use 1.9 getting ubuntu to automatically use 1.9 instead of 1.8 has been an issue, as has incompatible gems. Next I want to play with ruby waves, a rails alternative.

All linked together via wifi. Or at least that was the case til a power cut washed away the settings of the main gateway router connected to the dsl.

No matter what I did, I couldn’t get them all talking to each again. Restoring the settings backup didn’t work either. So I figured I would update it to the latest dd-wrt firmware, a day of playing at tftp and repeated reflashings later I went from having a linksys wrt54 brick to having a working router.

Now I used to do the networking over wds but I soon discovered that you need the same firmware version on every router, this wasn’t the case before, I guess I was just lucky.

A day later and now I have 3 routers all with the latest dd-wrt firmware. But can I get wds going stabely no! By now I am a little frustrated so I gave up with getting wds to work and am now just using client bridging, no range increase for the wifi, but atleast it seems stable.

HANDY ONE-LINERS FOR SED (Unix stream editor) Oct. 29, 1997
compiled by Eric Pement version 4.3
Latest version of this file is always at

FILE SPACING:

# double space a file

sed G

# triple space a file

sed 'G;G'

# undo double-spacing (assumes even-numbered lines are always blank)

sed 'n;d'

NUMBERING:

# number each line of a file (simple left alignment). Using a tab (see
# note on ‘\t’ at end of file) instead of space will preserve margins.

sed = filename | sed 'N;s/\n/\t/'

# number each line of a file (number on left, right-aligned)

sed = filename | sed 'N; s/^/ /; s/ *\(.\{6,\}\)\n/\1 /'

# number each line of file, but only print numbers if line is not blank

sed '/./=' filename | sed '/./N; s/\n/ /'

# count lines (emulates “wc -l”)

sed -n '$='

TEXT CONVERSION AND SUBSTITUTION:

# IN UNIX ENVIRONMENT: convert DOS newlines (CR/LF) to Unix format

sed 's/.$//'

# IN DOS ENVIRONMENT: convert Unix newlines (LF) to DOS format

sed 's/$//' # method 1

sed -n p # method 2

# delete leading whitespace (spaces, tabs) from front of each line
# aligns all text flush left

sed 's/^[ \t]*//' # see note on '\t' at end of file

# delete trailing whitespace (spaces, tabs) from end of each line

sed 's/[ \t]*$//' # see note on '\t' at end of file

# delete BOTH leading and trailing whitespace from each line

sed 's/^[ \t]*//;s/[ \t]*$//'

# insert 5 blank spaces at beginning of each line (make page offset)

sed 's/^/ /'

# align all text flush right on a 79-column width

sed -e :a -e 's/^.\{1,78\}$/ &/;ta' # set at 78 plus 1 space

# center all text in the middle of 79-column width. In method 1,
# spaces at the beginning of the line are significant, and trailing
# spaces are appended at the end of the line. In method 2, spaces at
# the beginning of the line are discarded in centering the line, and
# no trailing spaces appear at the end of lines.

sed -e :a -e 's/^.\{1,77\}$/ & /;ta' # method 1

sed -e :a -e 's/^.\{1,77\}$/ &/;ta' -e 's/\( *\)\1/\1/' # method 2

# substitute (find & replace) “foo” with “bar” on each line

sed 's/foo/bar/' # replaces only 1st instance in a line

sed 's/foo/bar/4' # replaces only 4th instance in a line

sed 's/foo/bar/g' # replaces ALL instances in a line

# substitute “foo” with “bar” ONLY for lines which contain “baz”

sed '/baz/s/foo/bar/g'

# substitute “foo” with “bar” EXCEPT for lines which contain “baz”

sed '/baz/!s/foo/bar/g'

# reverse order of lines (emulates “tac”)

sed '1!G;h;$!d'

# reverse each character on the line (emulates “rev”)

sed '/\n/!G;s/\(.\)\(.*\n\)/&\2\1/;//D;s/.//'

# join pairs of lines side-by-side (like “paste”)

sed 'N;s/\n/ /'

SELECTIVE PRINTING OF CERTAIN LINES:

# print first 10 lines of file (emulates behavior of “head”)

sed 10q

# print first line of file (emulates “head -1″)

sed q

# print last 10 lines of file (emulates “tail”)

sed -e :a -e '$q;N;11,$D;ba'

# print last line of file (emulates “tail -1″)

sed '$!d'

# print only lines which match regular expression (emulates “grep”)

sed -n '/regexp/p' # method 1

sed '/regexp/!d' # method 2

# print only lines which do NOT match regexp (emulates “grep -v”)

sed -n '/regexp/!p' # method 1, corresponds to above

sed '/regexp/d' # method 2, simpler syntax

# print 1 line of context before and after regexp, with line number
# indicating where the regexp occurred (similar to “grep -A1 -B1″)

sed -n -e '/regexp/{=;x;1!p;g;$!N;p;D;}' -e h

# grep for AAA and BBB and CCC (in any order)

sed '/AAA/!d; /BBB/!d; /CCC/!d'

# grep for AAA or BBB or CCC (emulates “egrep”)

sed -e '/AAA/b' -e '/BBB/b' -e '/CCC/b' -e d

# print only lines of 65 characters or longer

sed -n '/^.\{65\}/p'

# print only lines of less than 65 characters

sed -n '/^.\{65\}/!p' # method 1, corresponds to above

sed '/^.\{65\}/d' # method 2, simpler syntax

# print section of file from regular expression to end of file

sed -n '/regexp/,$p'

# print section of file based on line numbers (lines 8-12, inclusive)

sed -n '8,12p' # method 1

sed '8,12!d' # method 2

# print line number 52

sed -n '52p' # method 1

sed '52!d' # method 2

sed '52q;d' # method 3, efficient on large files

# print section of file between two regular expressions (inclusive)

sed -n '/Iowa/,/Montana/p' # case sensitive

SELECTIVE DELETION OF CERTAIN LINES:

# print all of file EXCEPT section between 2 regular expressions

sed '/Iowa/,/Montana/d'

# delete duplicate lines from a sorted file (emulates “uniq”). First
# line in a set of duplicate lines is kept, the rest are deleted

sed '$!N; /^\(.*\)\n\1$/!P; D'

# delete ALL blank lines from a file (same as “grep ‘.’ “)

sed '/^$/d'

# delete all CONSECUTIVE blank lines from file except the first; also
# deletes all blank lines from top and end of file (emulates “cat -s”)

sed '/./,/^$/!d' # method 1, allows 0 blanks at top, 1 at EOF

sed '/^$/N;/\n$/D' # method 2, allows 1 blank at top, 0 at EOF

# delete all CONSECUTIVE blank lines from file except the first 2:

sed '/^$/N;/\n$/N;//D'

# delete all leading blank lines at top of file

sed '/./,$!d'

# delete all trailing blank lines at end of file

sed -e :a -e '/^\n*$/N;/\n$/ba'

SPECIAL APPLICATIONS:

# remove nroff overstrikes (char, backspace) from man pages

sed "s/.`echo \\\b`//g" # double quotes required for Unix  environment

sed 's/.\x08//g' # hex expression for GNU sed (octal is "\010")

# get Usenet/e-mail message header

sed '/^$/q' # deletes everything after first blank line

# get Usenet/e-mail message body

sed '1,/^$/d' # deletes everything up to first blank line

# get Subject header, but remove initial “Subject: ” portion

sed '/^Subject: */!d; s///;q'

# get return address header

sed '/^Reply-To:/q; /^From:/h; /./d;g;q'

# parse out the address proper. Pulls out the e-mail address by itself
# from the 1-line return address header (see preceding script)

sed 's/ *(.*)//; s/>.*//; s/.*[:<] *//'

# add a leading angle bracket and space to each line (quote a message)

sed 's/^/> /

# delete leading angle bracket & space from each line (unquote a message)

sed 's/^> //'

# remove most HTML tags (accommodates multiple-line tags)

sed -e :a -e 's/<[^<]*>/ /g;/
# extract multi-part uuencoded binaries, removing extraneous  header

# info, so that only the uuencoded portion remains. Files passed to

# sed must be passed in the proper order. Version 1 can be entered

# from the command line; version 2 can be made into an executable

# Unix shell script. (Modified from a script by Rahul Dhesi.)
sed '/^end/,/^begin/d' file1 file2 ... fileX | uudecode # vers. 1
sed '/^end/,/^begin/d' $* | uudecode # vers. 2
# zip up each .TXT file individually, deleting the source file  and

# setting the name of each .ZIP file to the basename of the .TXT  file

# (under DOS: the "dir /b" switch returns bare filenames in all  caps).
echo @echo off >zipup.bat
dir /b *.txt | sed "s/^\(.*\)\.TXT/pkzip -mo \1 \1.TXT/"  >>zipup.bat
TYPICAL USE:
Sed takes one or more editing commands and applies  all of

them, in sequence, to each line of input. After all the commands  have

been applied to the first input line, that line is output and a  second

input line is taken for processing, and the cycle repeats. The

preceding examples assume that input comes from the standard input

device (i.e, the console, normally this will be piped input). One or

more filenames can be appended to the command line if the input does

not come from stdin. Output is sent to stdout (the screen). Thus:
cat filename | sed '10q' # uses piped input
sed '10q' filename # same effect, avoids a useless "cat"
sed '10q' filename > newfile # redirects output to disk
For additional syntax instructions, including the way to apply  editing

commands from a disk file instead of the command line, consult "sed &

awk, 2nd Edition," by Dale Dougherty and Arnold Robbins (O'Reilly,

1997; http://www.ora.com), "UNIX Text Processing," by Dale Dougherty

and Tim O'Reilly (Hayden Books, 1987) or the tutorials by Mike Arst

distributed in U-SEDIT2.ZIP (many sites). To fully exploit the power

of sed, one must understand "regular expressions." For this, see

"Mastering Regular Expressions" by Jeffrey Friedl (O'Reilly, 1997).

The manual ("man") pages on Unix systems may be helpful (try "man

sed", "man regexp", or the subsection on regular expressions in "man

ed"), but man pages are notoriously difficult. They are not written to

teach sed use or regexps to first-time users, but as a reference  text

for those already acquainted with these tools.
QUOTING SYNTAX:
The preceding examples use single quotes ('...')

instead of double quotes ("...") to enclose editing commands, since

sed is typically used on a Unix platform. Single quotes prevent the

Unix shell from intrepreting the dollar sign ($) and backquotes

(`...`), which are expanded by the shell if they are enclosed in

double quotes. Users of the "csh" shell and derivatives will also  need

to quote the exclamation mark (!) with the backslash (i.e., \!) to

properly run the examples listed above, even within single quotes.

Versions of sed written for DOS invariably require double quotes

("...") instead of single quotes to enclose editing commands.
USE OF '\t' IN SED SCRIPTS:
For clarity in documentation, we have  used

the expression '\t' to indicate a tab character (0x09) in the  scripts.

However, most versions of sed do not recognize the '\t'  abbreviation,

so when typing these scripts from the command line, you should press

the TAB key instead. '\t' is supported as a regular expression

metacharacter in awk, perl, and in a few implementations of sed.
VERSIONS OF SED:
Versions of sed do differ, and some slight  syntax

variation is to be expected. In particular, most do not support the

use of labels (:name) or branch instructions (b,t) within editing

commands, except at the end of those commands. We have used the  syntax

which will be portable to most users of sed, even though the popular

GNU versions of sed allow a more succinct syntax. When the reader  sees

a fairly long command such as this:
sed -e '/AAA/b' -e '/BBB/b' -e '/CCC/b' -e d
it is heartening to know that GNU sed will let you reduce it to:
sed '/AAA/b;/BBB/b;/CCC/b;d'
In addition, remember that while many versions of sed accept a  command

like "/one/ s/RE1/RE2/", some do NOT allow "/one/! s/RE1/RE2/",  which

contains space before the 's'. Omit the space when typing the  command.
OPTIMIZING FOR SPEED:
If execution speed needs to be increased  (due to

large input files or slow processors or hard disks), substitution  will

be executed more quickly if the "find" expression is specified  before

giving the "s/.../.../" instruction. Thus:
sed 's/foo/bar/g' filename # standard replace command
sed '/foo/ s/foo/bar/g' filename # executes more quickly
sed '/foo/ s//bar/g' filename # shorthand sed syntax
On line selection or deletion in which you only need to output  lines

from the first part of the file, a "quit" command (q) in the script

will drastically reduce processing time for large files. Thus:
sed -n '45,50p' filename # print line nos. 45-50 of a file
sed -n '51q;45,50p' filename # same, but executes much faster
If you have any additional scripts to contribute or if you find  errors

in this document, please send e-mail to the compiler. Indicate the

version of sed you used, the operating system it was compiled for, and

the nature of the problem. Various scripts in this file were written

or contributed by:
]]>
			http://anatexis.net/wordpress/?feed=rss2&p=28
		0
		
		
		
		http://anatexis.net/wordpress/?p=27&utm_source=rss&utm_medium=rss&utm_campaign=updated-wordpress-and-things
		http://anatexis.net/wordpress/?p=27#comments
		Mon, 21 Dec 2009 18:02:03 +0000
		admin
				

		http://anatexis.net/wordpress/?p=27
		
			Seems to be working fine so far, but if you notice anything funky then please let me know!

]]>
			http://anatexis.net/wordpress/?feed=rss2&p=27
		0
		
		
		
		http://anatexis.net/wordpress/?p=22&utm_source=rss&utm_medium=rss&utm_campaign=installing-open-instrumentation-on-ubuntu-64bit
		http://anatexis.net/wordpress/?p=22#comments
		Fri, 04 Dec 2009 02:08:57 +0000
		admin
				
		
		
		

		http://anatexis.net/wordpress/?p=22
		
			I have a Syscomp Circuit Gear  Oscilloscope, its a nice little USB device…. but they dont supply drivers that work under 64bit Linux,

however, i did find that someone had done the work to make them work under 64bit Suse, and saved it as a RPM file.
getting this into Ubuntu proved to be an issue….

first i downloaded the amd64 file from here http://software.opensuse.org/search?q=syscomp-cgr
then i installed alien, use this to convert package format’s
>sudo apt-get install alien
if one then tries to convert the rpm you get this
>sudo alien syscomp-cgr-1.12-5.1.x86_64.rpm
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
error: incorrect format: unknown tag
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
warning: syscomp-cgr-1.12-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 27805e33
Unpacking of 'syscomp-cgr-1.12-5.1.x86_64.rpm' failed at /usr/share/perl5/Alien/Package/Rpm.pm line 155.
This is a result of this bug in the ubuntu package…. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509444
using the suggested work around you get …
>cat syscomp-cgr-1.12-5.1.x86_64.rpm  | rpm2cpio | lzma -d | cpio -ivd
which produces a series of files under a usr, directory.  copying these all to the right places…
>sudo cp ./usr/bin/* /usr/bin/
>sudo cp ./usr/lib/syscomp /usr/lib/
>sudo cp ./usr/share/doc/syscomp /usr/share/doc/syscomp/
Meant that i could run the program…
>syscomp-cgr
Error in startup script: can't find package Img
 while executing
"package require Img"
 (file "/usr/lib/syscomp/CGR101-1.12/main.tcl" line 51)
so I then installed the tcl/tk package Img
> sudo apt-get install libtk-img-dev
which seems to make everything work! just run syscomp-cgr and the program loads right up and found the Oscilloscope without a problem.
]]>
			http://anatexis.net/wordpress/?feed=rss2&p=22
		0
		
		
		
		http://anatexis.net/wordpress/?p=20&utm_source=rss&utm_medium=rss&utm_campaign=ploticus-scripts
		http://anatexis.net/wordpress/?p=20#comments
		Tue, 27 Oct 2009 16:33:16 +0000
		admin
				
		
		
		

		http://anatexis.net/wordpress/?p=20
		
			I have found it very usefull to use ploticus to create simple plots via scripts this script plots a time lines, for things like volcanic eruptions.

svn link
the ploticus script looks like this
svn link
]]>
			http://anatexis.net/wordpress/?feed=rss2&p=20
		0