459 reputation
413
bio website docsalvage.info
location Tallahassee, FL
age 59
visits member for 1 year, 11 months
seen yesterday

Unix/Linux software developer in dozens of languages since 1981 with 15 years in Oracle database design and administration.

Projects (most recent first)

  • Developing Zim desktop wiki (for notes) to GtkDialog conversion program to allow automatic creation of checklists for installs, etc. from Zim notes pages. Utilizes bash and 600+ line awk program.
  • Conversion from Tomboy/GNote to Zim for all writing.
    • Zim links to execute or edit scripts with Geany
  • Migrating from Ubuntu Linux to Puppy Linux due to dislike of Unity and Gnome3.
  • Save the world (or at least my sanity) by re-electing President Barak Obama and rescuing congress from the fanatics now running it.
    • 2012-11-06 DONE
      project scope change...
      part 2 improved but not completely doable at this time
  • JavaScript/jQuery-based composing and programming environment inspired by Jeremy Ruston's TiddlyWiki.

Oct
9
revised Why is variable assignment preceding command ignored?
added solution
Oct
9
revised Why is variable assignment preceding command ignored?
added 82 characters in body
Oct
9
awarded  Custodian
Oct
9
reviewed Approve suggested edit on Why is variable assignment preceding command ignored?
Oct
9
asked Why is variable assignment preceding command ignored?
Oct
8
comment Maintain screen session when executing shell script on boot
Have you patched Bash for the shellshock vulnerability? That patch removes some of bash's ability to execute commands fed to it on stdin as the screen may be doing. Try it with the old, unpatched version of bash that was on your system. That would be the quickest way to rule that out.
Oct
2
answered exit shell script from a subshell
Sep
26
comment What is the severity of the new bash exploit (shellshock)?
How can this vulnerability be exploited against a desktop user?
Sep
8
revised Recovering from 'grub rescue>' crash
docsalvage -> docsalvager
Aug
25
accepted Recovering from 'grub rescue>' crash
Aug
3
revised Recovering from 'grub rescue>' crash
changed "antique" to "classic"
Aug
2
revised Recovering from 'grub rescue>' crash
added BusyBox links, consistent highlighting, wordsmithing, adjusted bullet indenting
Aug
2
asked Recovering from 'grub rescue>' crash
Aug
2
answered Recovering from 'grub rescue>' crash
Jul
23
awarded  Notable Question
Jul
2
awarded  Curious
Jun
28
comment Shortest way to extract last 3 characters of base (minus suffix) filename
Added bash version to internal help for function argsNumber.
Jun
28
revised Shortest way to extract last 3 characters of base (minus suffix) filename
added bash version to internal help of argsNumer function
Jun
28
comment Shortest way to extract last 3 characters of base (minus suffix) filename
You are right that "$#" is the widely documented systax for "number of arguments." However, I've just reverified that "${#@}" is equivalent. I wound up with that after experimenting with the differences and similarities between positional arguments and arrays. The later comes from the array syntax which apparently is a synonym for the shorter, simpler "$#" syntax. I've altered and documented argsNumber() to use "$#". Thanks!
Jun
28
revised Shortest way to extract last 3 characters of base (minus suffix) filename
replaced function argsNumber and added resources