Difference between revisions of "User:Ted"

From Wiki at Neela Nurseries
Jump to: navigation, search
m (→‎Other Things To Explore)
m (→‎Bash Shell Scripting)
Line 103: Line 103:
  
 
Shell scripting and use of built-in shell commands is a really practical knowledge to employ, when working in Unix-like environments.  One common task is to find all the instances of a given file or program.  The <code>locate</code> command can perform this kind of search, but it's results don't show whether the file instances differ.  To check at the rough level of file size, we can use a one-line shell script technique involving shell piping, to "long list" the results of the <code>locate</code> command, like this . . .
 
Shell scripting and use of built-in shell commands is a really practical knowledge to employ, when working in Unix-like environments.  One common task is to find all the instances of a given file or program.  The <code>locate</code> command can perform this kind of search, but it's results don't show whether the file instances differ.  To check at the rough level of file size, we can use a one-line shell script technique involving shell piping, to "long list" the results of the <code>locate</code> command, like this . . .
 +
  
 
<pre>
 
<pre>
 
   $ for file in `locate tavrasm | grep 'asm$'`; do ls -l ${file}; done
 
   $ for file in `locate tavrasm | grep 'asm$'`; do ls -l ${file}; done
 
</pre>
 
</pre>
 +
 +
 +
Hmm strange, the above command calls `grep` with a pattern that ends in the shell end-of-line anchoring character $, and appears to filter for results of `locate` which end in 'asm'.  But on 2017-09-12 needed to add a "one or more wildcard" character pattern to limit search results for instances of `locate` results ending in 'qemu':
 +
 +
 +
<pre>
 +
$ locate qemu | grep '.*qemu$'
 +
</pre>
 +
 +
 +
Why the apparent difference in command invocation?  Need to test . . .  - TMH
 +
  
  

Revision as of 18:29, 12 September 2017

-- 2017-07-21 शुक्रवार --
Ted's page on <a href="https://neelanurseries.com">Neela Nurseries</a> Wiki


OVERVIEW

This wiki document a starting point of Ted's notes on Linux use and configuration, Open Source Software and web development. Recent summer 2017 efforts of Ted's are focused on several high-level programming language and web development frameworks, which can be studied and used separately but are often glued together to achieve meaningful tasks and end-user tools and interfaces. This personal page of Ted's notes on Neela Nurseries wiki not yet well organized, but here as a quick stash point for holding useful references, and a starting point for more complete and formal documentation.



Web Site Building Blocks - Summer 2017 Work

 
The following tools and web and programming frameworks are all part of Ted's volunteer efforts with ASI web site, and in-progress study of how to configure and customize shopping carts, article and document management pages, and easy-to-read easy-to-adjust web page layouts using CSS and third party, open source frameworks:



These are the first topics on which Ted wants to gather together notes. Hard to remember all details regarding pitfalls encountered, solutions found, and ideas for improving the configuration and use experience of these softwares . . . - TMH




Linux Packages

- 2017-07-31 सोमवार -


This section a starting point for notes on Linux packages, namely Debian and Ubuntu packages. Focus here is on userland software, and which packages are needed to set up various tools sets in a working Unix / Linux environment . . .

  • libreoffice-base
  • postfix . . . see section below
  • gpm
  • ctags
  • vim-doc
  • vim-scripts
  • xfonts-cyrillic
  • devhelp
  • distcc . . . distributed compiling of C and C++ programs across multiple machines


Postfix


Linux packages for Raspberry Pi system




Bash Shell Scripting

Shell scripting and use of built-in shell commands is a really practical knowledge to employ, when working in Unix-like environments. One common task is to find all the instances of a given file or program. The locate command can perform this kind of search, but it's results don't show whether the file instances differ. To check at the rough level of file size, we can use a one-line shell script technique involving shell piping, to "long list" the results of the locate command, like this . . . 


  $ for file in `locate tavrasm | grep 'asm$'`; do ls -l ${file}; done


Hmm strange, the above command calls `grep` with a pattern that ends in the shell end-of-line anchoring character $, and appears to filter for results of `locate` which end in 'asm'. But on 2017-09-12 needed to add a "one or more wildcard" character pattern to limit search results for instances of `locate` results ending in 'qemu': 


$ locate qemu | grep '.*qemu$'


Why the apparent difference in command invocation? Need to test . . . - TMH




Aboriginal Linux



QEMU Emulator

Notes on QEMU, an emulator which can help with building and configuring Linux systems to run on embedded computers and development boards. Ted noting 2017-09-08 that to compile today's latest QEMU source, a 2.10.x release, needed to install Debian stretch packages pkg-config, libglib2.0-dev, dhautoreconf.



Other Things To Explore

Dublin Core . . .

3D Graphics, mathematics behind and programming:

PC Video, Bochs VBE Extensions:

Webvanta:



References

Apache2 configuration:

Couple of MediaWiki and publishing issues to look into, which came up during wiki configuration:

Some Hindi language and UTF-8 encoding references, to be factored to a dedicated wiki page later:

Linux programs and utilities:




Retrieved from "https://wiki.neelanurseries.com/index.php?title=User:Ted&oldid=130"