See also:

https://www.instructables.com/id/Linux-hints-II/

Just a few quickie ideas I put togethr that might be of interest. I have tried to keep each of them to one step.

Step 1: Install an MsWindows driver on linux.
Step 2: Message of the day,
Step 3: Library conflicts.
Step 4: Beaglebone black.
Step 5: Couple of simple simple command line clocks.
Step 6: Pogoplug V2
Step 7: Network printing.
Step 8: Create animated gifs easily
Step 9: Openwrt Chilli hotspot.
Step 10: Web and the command line working together.
Step 11: Squeezebox multimedia server.
Step 12: Firefly
Step 13: Yet another music server.
Step 14: Package group installer.
Step 15: Insecure wifi host.

Step 16.Bad b;ocl messages

Step 17 Minimal arch install starter.

Step 18 Capture the command line or ascii movies.

Step 19 Generic command line

Step 20 A few linux games

Step 21Linux for the impaired

Step 22 Linux version

Step 23 Random numbers

Step 24 Bash bug.

Step 25 Network printer install

Step 26 Command line to gui

See also: https://www.instructables.com/id/Multiple-network-cards/

Set up a legacy mswindows wifi card in linux..(Make sure your card was installed properly while the machine was off.)

Download and extract the mswindows drivers for the card

Unzip the files to a local directory

$ unzip aw*

Fw1130.bin FwRad17.bin radio17.bin TNET1130.INF
FwRad16.bin radio16.bin tnet1130.cat tnet1130.sys

Install the interfacing software.

$ sudo apt-get install ndiswrapper-common ndiswrapper-utils-1.9  ndiswrapper-dkms

To see if your card is tetected.

$ lspci

…

00:0b.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface

…

$ sudo modprobe  ndiswrapper

…

wlan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DORMANT qlen 1000

…

Install wifi card driver (driver will usually be a .INF file

$ sudo ndiswrapper -i TNET1130.INF

$ ndiswrapper -l

tnet1130 : driver installed
device (104C:9066) present

Set ip ip for the card

$ ip addr

…

link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

…

Check the current config of your card.

$ iwconfig

wlan1 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:10 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

From here you should be able to configure your card.



------------------------------------------

In case you can not get the ndisrapper module:
Get kernel version
# uname -a
Append the kernel version to apt-get linux-headers-
# apt-get install linux-headers-3.2.0-4-686-pae
Get ndissrapper source
# apt-get install ndiswrapper-source
#apt-get remove
Remove the kernel setup and then reinstall
# apt-get remove ndiswrapper-dkms
# apt-get install ndiswrapper-dkms
You should see it being isntalled to the kernel.

$ sudo ldconfig

$ hash -r

Convert a series of pictures into an animated gif is real easy. First you want to collect all the pictures together and order them by name in the order you want them to appear.

<a href="http://www.imagemagick.org/download/binaries/" rel="nofollow">  http://www.imagemagick.org/download/binarie
>

-----------------------------------------------------------
How to quickly and easily take a short film and turn it into a gif.


Make or use an empty directory for the intermediate pictures.

$ mkdir gifit
$ cd !$

Move the movie to that directory

Split out gif and reassemble at a slower speed.

convert a.gif %02d.png
convert -delay 6 -loop 0 *.png animation.gif

Gifs to avi

convert test.gif old%02d.jpg
ffmpeg -r 25 -i old%02d.jpg -y -an new.avi

Installation instructions for forked-daapd
------------------------------------------

There are two ways to install forked-daapd: from a tarball or from the git
tree. The tarball contains a working build system and pre-generated ANTLR3
parsers; the git tree doesn't and requires more tools to generate the build
system and the ANTLR3 parsers.

In both cases the installation procedure is the traditional ./configure;
make; make install. Please read this file carefully before proceeding.


System-specific requirements:
 - Linux:
   + glibc 2.13+ (bugfix: process-wide setgroups(), glibc BZ#10563)
   + libasound (ALSA sound support - or you can use OSS4)
 - FreeBSD:
   + OSS4 sound support
   + libiconv

Tools:
 - The clang C compiler from the LLVM project. forked-daapd uses Blocks,
   an extension to the C language that is not supported by gcc. Along with
   clang, you'll also need the Blocks runtime, libblocksruntime.

 - pkg-config
 - gperf 3.x
        from <http://www.gnu.org/software/gperf/>

Libraries:
 - libantlr3c (ANTLR3 C runtime, version 3.2 for tarball builds)
        from <http://www.antlr.org/download/C>
 - Avahi client libraries (avahi-client), 0.6.24 minimum
        from <http://avahi.org/>
 - sqlite3 3.5.0+ with unlock notify API enabled (read below)
        from <http://sqlite.org/download.html>
 - libav 0.6+/0.7+ (or ffmpeg 0.5.1+)
        from <http://libav.org/releases/>
 - libconfuse
        from <http://www.nongnu.org/confuse/>
 - libdispatch
        /!\ Read below
 - libtre
        from <http://laurikari.net/tre/download/>
 - libavl
        /!\ Read below
 - MiniXML (aka mxml or libmxml)
        from <http://minixml.org/software.php>
 - gcrypt 1.2.0+
        from <http://gnupg.org/download/index.en.html#libgcrypt>
 - zlib
        from <http://zlib.net/>
 - libunistring 0.9.3+
        from <http://www.gnu.org/software/libunistring/#downloading>
 - libflac (optional - FLAC support)
        from <http://flac.sourceforge.net/download.html>
 - taglib (optional - Musepack support)
        from <http://developer.kde.org/~wheeler/taglib.html>
 - libplist 0.16+ (optional - iTunes XML support)
        from <http://github.com/JonathanBeck/libplist/downloads>

If using binary packages, remember that you need the development packages to
build forked-daapd (usually named -dev or -devel).

libdispatch for Linux and its dependencies can be found in the Debian archive;
you need at least libdispatch from SVN rev 197 + Debian patches (Linux support),
libkqueue 0.9.2 and libpthread_workqueue 0.7. At this time, it's probably
easiest to use whatever versions happen to be in Debian unstable.

libavl is not the GNU libavl. There doesn't seem to be an upstream website
anymore, but you'll find the source tarball alongside the forked-daapd
release tarballs (see below for the URL). Alternatively, you can fetch it from
any Debian mirror, too (it'll be in /debian/pool/main/liba/libavl).

sqlite3 needs to be built with support for the unlock notify API; this isn't
always the case in binary packages, so you may need to rebuild sqlite3 to
enable the unlock notify API (you can check for the presence of the
sqlite3_unlock_notify symbol in the sqlite3 library). Refer to the sqlite3
documentation, look for SQLITE_ENABLE_UNLOCK_NOTIFY.


Note about libav (ffmpeg)
-------------------------

libav (ffmpeg) is a central piece of forked-daapd and most other FLOSS
multimedia applications. The version of libav you use will potentially have a
great influence on your experience with forked-daapd.

The following versions of libav (ffmpeg) are supported and known to work:
 - ffmpeg 0.5.x: has issues with metadata (tags) extraction, notably with
   MP3 files and ID3 tags in general;
 - libav 0.6.x: known to work better with regard to metadata extraction;
 - libav 0.7.x: better yet

Note that forked-daapd uses libav since the ffmpeg/libav fork during the
0.6.x series.


Building from the git tree
--------------------------

Gitweb: <http://git.debian.org/?p=users/jblache/forked-daapd.git>
Git tree: <git://git.debian.org/users/jblache/forked-daapd.git>

Required tools:
 - ANTLR v3 is required to build forked-daapd, along with its C runtime
   (libantlr3c). Use at least version 3.1.3 of ANTLR v3 and the matching
   C runtime version.

 - Java runtime: ANTLR is written in Java and as such a JRE is required to
   run the tool. The JRE is enough, you don't need a full JDK.

 - autotools: autoconf 2.63+, automake 1.10+, libtool 2.2. Run autoreconf -i
   at the top of the source tree to generate the build system.

 - gettext: libunistring requires iconv and gettext provides the autotools
   macro definitions for iconv.

Start by generating the build system by running autoreconf -i. This will
generate the configure script and Makefile.in.

The configure script will look for a wrapper called antlr3 in the PATH to
invoke ANTLR3. If your installation of ANTLR3 does not come with such a
wrapper, create one as follows:

  #!/bin/sh
  CLASSPATH=...
  exec /path/to/java -cp $CLASSPATH org.antlr.Tool "@"

Adjust the CLASSPATH as needed so that Java will find all the jars needed
by ANTLR3.

The parsers will be generated during the build, no manual intervention is
needed.


Building from the tarball
-------------------------

Download URL: <http://alioth.debian.org/~jblache/forked-daapd/>

When building forked-daapd from a release tarball, the usual ./configure;
make; make install procedure applies.

FLAC and Musepack support are optional. If not enabled, metadata extraction
will fail on these files.

Support for iTunes Music Library XML format is optional. Use --enable-itunes
to enable this feature.

Recommended build settings:
 ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --enable-flac --enable-musepack

After installation, edit the configuration file, /etc/forked-daapd.conf and
adjust the values at your convenience.

forked-daapd will drop privileges to any user you'll specify in the
configuration file if it's started as root. It's recommended to create a
dedicated user without login privileges.

This user must have read permission on your library (you can create a group for
this and make the user a member of the group, for instance) and read/write
permissions on the database location ($localstatedir/cache/forked-daapd by
default).

You'll need an init script if you want to start forked-daapd at boot. A simple
init script will do, forked-daapd daemonizes all by itself and creates a
pidfile under /var/run. Different distributions have different standards for
init scripts and some do not use init scripts anymore; check the documentation
for your distribution.

For dependency-based boot systems, here are the forked-daapd dependencies:
 - local filesystems
 - network filesystems, if needed in your setup (library on NFS, ...)
 - networking
 - NTP
 - Avahi daemon

The LSB header below sums it up:

### BEGIN INIT INFO
# Provides:          forked-daapd
# Required-Start:    $local_fs $remote_fs $network $time avahi
# Required-Stop:     $local_fs $remote_fs $network $time
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: media server with support for RSP, DAAP, DACP and AirTunes
# Description:       forked-daapd is an iTunes-compatible media server for
#                    sharing your music library over the local network with RSP
#                    clients like the SoundBridge from Roku and DAAP clients like
#                    iTunes. It can also stream music to AirTunes devices.
### END INIT INFO

Tasksel is a neat program as it will allow to install a set of programs for a specific purpose. If you only install the base (command line) system, this is a great way to add only what you need. That way you do not have to go willy nilly looking for everything that miight be needed to install a web server. What is installed will vary depending on what Debian based distro you use. This is even true between hardware platforms(i.e. X86, X86-64, Arm, PPC, and etc).

Redhat also has as a group install but it is not menu driven.

To get a list of groups
$ sudo yum grouplist | less
Then to installl
$ sudo yum groupinstall "group name"

i.e.
$ sudo yum groupupdate 'Development Tools'

On Debian and the like:

$ sudo apt-get install tasksel

You can easily select install the lamp (Linix, Apache2, Mysql, and PHP) to set up a minimal web server. While doing that you can tell the system not to install the gui desktop to make a lean and trim system. You can also install several options at once, but you need to be careful.

To see what packages a system has available to install, you can use the command: (varies from distribution to distribution). It will even tell you what is installed.

$ sudo tasksel --list-tasks

i server Basic Ubuntu server i openssh-server OpenSSH server u dns-server DNS server u lamp-server LAMP server i mail-server Mail server u openstack Openstack u postgresql-server PostgreSQL database i print-server Print server .... .... .... etc etc

You can also see what programs are included in a specific package

$ sudo tasksel --task-packages server update-notifier-common python-zope.interface python-chardet python-lazr.restfulclient python-serial w3m python-pam vim-runtime curl python-wadllib libpcsclite1 python-simplejson vim .... .... .... etc etc

You can still install and remove individual packages the old fashion way. I will not dwell on all the options, but you can always

$ man tasksel

for more details.

-------------------------------------------

Additional information:

Keep a list of installed packages:

$ dpkg –get-selections > installed-software.log read $ dpkg (dash)(dash)get-selections > installed-software.log

To use for another system: $ dpkg –set-selections < installed-software.log read $ dpkg (dash)(dash)set-selections < installed-software.log $ apt-get dselect-upgrade

Wicd

You must remove network-manager to get wicd to work. Check to see if network-manager is installed and see if, after you installed the driver, your wireless is already working in the notification area of your desktop manager. You may already be good to go.

wicd (Wireless Interface Connection Daemon) is a lightweight alternative to NetworkManager. It is environment-independent, making it suitable for all desktop environments, including GNOME, Xfce, LXDE, and Fluxbox. Like NetworkManager, wicd is configured via a graphical interface. Your wireless interface should not be referenced within Debian's /etc/network/interfaces file.

1. Update the list of available packages and install the wicd package:

   $ su
   # aptitude update
   # aptitude install wicd

2. Amend /etc/network/interfaces to contain only the following:

   # This file describes the network interfaces available on your system
   # and how to activate them. For more information, see interfaces(5).
   
   # The loopback network interface
   auto lo
   iface lo inet loopback

   Note: as of wheezy it is fine to have your wireless interface in /etc/network/interfaces (it might even be required, not sure)

3. If not already performed, add your regular user account to the netdev group and reload DBus:

   # adduser yourusername netdev
   # /etc/init.d/dbus reload

4. Start the wicd daemon:

   # /etc/init.d/wicd start

5. Start the wicd GUI with your regular user account: 

   # exit
   $ wicd-client -n

See also wicd frequently asked questions.

Command Line

Scan for available networks and get network details:

$ su
# iwlist scan

Now edit /etc/network/interfaces. The required configuration is much dependent on your particular setup. See the following example to get an idea of how it works:

# my wifi device
auto wlan0
iface wlan0 inet dhcp
        wireless-essid [ESSID]
        wireless-mode [MODE] 

For further information on available configuration options, see man interfaces, man wireless and /usr/share/doc/wireless-tools/README.Debian.

You can now bring your interface up and down with the usual ifup and ifdown commands. If you added auto wlan0 as in the example above, the interface should be brought up automatically during boot up.

wpa_supplicant

wpa_supplicant is a WPA client and IEEE 802.1X supplicant.

The wpasupplicant package provides wpa-* ifupdown options for /etc/network/interfaces. If these options are specified, wpa_supplicant is started in the background when your wireless interface is raised and stopped when brought down.

• GNOME and KDE users shouldn't configure wpa_supplicant manually. Use NetworkManager as explained above.

Before continuing, install the wpasupplicant package:

• $ su
  # aptitude update
  # aptitude install wpasupplicant

WPA-PSK and WPA2-PSK

Also known as "WPA Personal" and "WPA2 Personal" respectively.

1. Restrict the permissions of /etc/network/interfaces, to prevent pre-shared key (PSK) disclosure:

   # chmod 0600 /etc/network/interfaces

2. Open /etc/network/interfaces in a text editor:

   # sensible-editor /etc/network/interfaces

3. Define appropriate stanzas for your wireless interface, along with the SSID and PSK. For example:

   auto wlan0
   iface wlan0 inet dhcp
       wpa-ssid mynetworkname
       wpa-psk mysecretpassphrase

   The "auto" stanza will bring your interface up at system startup. If not desired, remove or comment this line.
4. Save the file and exit the editor.

5. Bring your interface up. This will start wpa_supplicant as a background process.

   # ifup wlan0

Additional wpa-* options are described within /usr/share/doc/wpasupplicant/README.modes.gz. This should also be read if connecting to a network not broadcasting its SSID.

For general /etc/network/interfaces information, see the interfaces(5) man page.

WPA-EAP

For networks using EAP-TLS, you are required to establish a wpa_supplicant configuration file and provide the client-side certificate. An example WPA2-EAP configuration file can be found at /usr/share/doc/wpasupplicant/examples/wpa2-eap-ccmp.conf.

Once available, reference your configuration file in /etc/network/interfaces. For example:

• auto wlan0
  iface wlan0 inet dhcp
      wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

More information can be found in the wpa_supplicant.conf(5) man page. A fully-commented wpa_supplicant configuration file example is at /usr/share/doc/wpasupplicant/README.wpa_supplicant.conf.gz.

Switching Connections

To switch between multiple distinct configurations:

• GNOME users should use "Menu System > Administration > Network". (n.b. this doesn't work in etch)

• Console users can

  • use logical interfaces, as

    iface wlan_home inet dhcp
        wpa-ssid mynetworkname
        wpa-psk mysecretpassphrase

    # ifup wlan0=wlan_home

  • use ifscheme, see the example configuration at alwayssunny.com.

  • You can use guessnet(8) to switch profiles automatically by your location.

Security consideration

1. Every member of a network can listen to other members' traffic (whether it's an unencrypted public hot-spot, or a WEP/WPA/WPA2, or LAN). Use SSL/TLS protocols (HTTPS, IMAPS...) or VPN to preserve your privacy.

2. WEP is so insecure that it is basically equivalent to not using any encryption at all.

3. WPA1 is deprecated. Use WPA2 instead.

4. Make sure you use a strong pass-phrase.

Index of /archlinux/iso/2014.01.05

	Name	Last modified	Size	Description
	Parent Directory		-
	arch/	05-Jan-2014 03:26	-
	archlinux-2014.01.05-dual.iso	05-Jan-2014 03:41	528M
	archlinux-2014.01.05-dual.iso.sig	05-Jan-2014 03:41	287
	archlinux-2014.01.05-dual.iso.torrent	05-Jan-2014 03:41	30K
	archlinux-bootstrap-2014.01.05-i686.tar.gz	05-Jan-2014 03:42	75M
	archlinux-bootstrap-2014.01.05-i686.tar.gz.sig	05-Jan-2014 03:42	287
	archlinux-bootstrap-2014.01.05-x86_64.tar.gz	05-Jan-2014 03:44	77M
	archlinux-bootstrap-2014.01.05-x86_64.tar.gz.sig	05-Jan-2014 03:44	287
	md5sums.txt	05-Jan-2014 03:44	220
	sha1sums.txt	05-Jan-2014 03:44	244

Sometimes every once in a while, you find an old generally unused command, but now you find it is very valuable. One such command is know as ttyrec. As the name suggests, you can probably record what is typed at the terminal. This is excellent for documentation purposes. It is a must for people who do any amount of work on the command line. An example: recently did a remote install of Arch linux on a remote machine. It would have been nice to have a record of all the work done.

Well how do you use it? There are actually two parts of the system. ttyrec does the recording and ttyplay will playback what you have recorded. So you will want to invoke ttyrec with a filename (for later playback,) which will generate a new shell or prompt. Go ahead and trpe in the coomands you want to do, then when you are finnished, use d to exit the the recording. You will see the word exit to confirm the exit of the ttyrec program.

$ sudo apt-get install ttyrec
$ ttyrec filename
$ echo hello world
hello world
$d exit

Now to playback what your have typed in exactly as you have typed it then use:

$ ttyshow filename

The playback will show everything as it was done like a movie.Now anytime you want to check out what you did during the recording session, it is at your fingertips. Also too makes for great educational media.

also perfect for recording online sessions say like using telnet.

$ ttyrec starwars
$ telnet towel.blinkenlights.nl

control-d

$ ttyplay starwars.

A few linux games you may or many not know about.

http://www.cahilig.net/2011/07/29/100-best-free-and-high-quality-linux-games

https://www.google.com/#q=top%20100%20free%20linux%20games

Sometimes I forget how lucky I am to see. Not everyone has that gift. If you do not have that gift, does not mean you should be limited in using computers. Traditionally you had to let someone install linux for you, Several Linux distros now allow even the seeing and or hearing impaired to install and use Linux. As a test for myself, I took the Debian linux distro to see if I could install and use it blindfolded. As many times as I have done the text install of Linux, I did not do very well with the audio commanded install of Debian Linux (www.debian.org). I am sure they have improved it. Then again they mever advertized it as a distro for the blind. (You use the speech synthesis option). Later you might need to install Orca if you want to use the gui.

But then you can use the distros meant to be used for the handicapped such as Arch (http://talkingarch.tk/). They even have an audio not video tutorial. You could also use Vinux (vinuxproject.org/) or Sonar (http://sonargnulinux.com/). Sonar is recommeded byt the TLLTS podcast team.

There are some excellent text based utilities to start of with before you venture into the gui.

Some of my favorite programs are:

alsa sound modules – music and to support speech programs (and voice recording)

Twidge – twitter client

links2 – internet browser

ps2ascii – convert postscript files to text files.

bashpodder – audio podcast collector

alpine sendEmail – email client tools

irssi – interrelay chat

centerim – instant messaging client

vim can be used as and editor or word processor, there are many others.

antiword – for dealing with proprietary word procesing formats.

screen – allows you to easily switch remote sessions

ledger – accounting program

curl wget – web page and file extracting tools

bash – the built in programming language that can be used with awk, sed, sort tr figlet (make your own database or game programs as well as other tools).

ImageMagick suite – manipulate graphics

cadubi tetradraw – ascii drawing programs

opensched – schedule formater.

hnb – notetaking and outlining

moc mplayer aplay ffmpeg – audio tools and players.

nget newbueter – newsreader

pal – calendar/planner program

cdrecord – burn cd’s and back up computer.

ssh and other tools. – network administration/file amangement

espeak festival – voice synthesis (great for having your computer read outloud documents) Who needs a Kindle?

wyrd - calendaring program.

The bottom line is that you can do word processing. spreadsheets. database, email, listen to podcasts or even hear documents spoken. Who could ask for more? Happy computing

Download file

$ chmod +x release.sh

$ ./release.sh

Ubuntu 12.04.4 LTS

$ ./release.sh

Arch Linux

Play the lottery? Here is a simple random number generator to pontificate the numbers. Run it as many times as there are picks.<br> 
 lg.sh:
 echo Lottery generator
 echo
 echo -n "Enter number of balls: "
 read nodf
 echo -n "Enter number of choices: "
 read b
 declare -i X=$b
 for i in $(seq 1 1 $nodf)
 do
 NUM=$[ ( $RANDOM % $X ) + 1 ];
 echo "The winner is for ball number $i:" $NUM
 done
 
 
 $ ./lg.sh
 Lottery generator
 
 Enter number of balls: 5
 Enter number of choices: 50
 The winner is for ball number 1: 32
 The winner is for ball number 2: 43
 The winner is for ball number 3: 23
 The winner is for ball number 4: 18
 The winner is for ball number 5: 38
 
Don't forget to "chmod +x" it. Great for choosing winners randomly in a
 contest. Write the number down after each toss. I will let you mod the 
code to save the numbers.
 
 Note: it does not check for duplicates.

<p>lg.sh:>
echo Lottery generator
echo
echo -n "Enter number of balls: "
read nodf
echo -n "Enter number of choices: "read b</p><p>declare -i X=$b</p><p>for i in $(seq 1 1 $nodf)</p><p>do</p><p>NUM=$[ ( $RANDOM % $X ) + 1 ];</p><p>echo "The winner is for ball number $i:" $NUM</p><p>done</p><p>$ ./lg.sh
Lottery generator
Enter number of balls: 5
Enter number of choices: 50
The winner is for ball number 1: 32
The winner is for ball number 2: 43
The winner is for ball number 3: 23
The winner is for ball number 4: 18
The winner is for ball number 5: 38
>Don’t forget to “chmod +x” it. 

Great for choosing winners randomly in  a contest. Write the number down after each toss. I will let you mod  the code to save the numbers.
Note: it does not check for duplicates.

Another way to do it.

usage ./rndom choicesperball numberofballs 
./rndom.sh 50 5
Choices per ball are 50 and the number of balls is 5
Ball number 1 is 35
Ball number 2 is 31
Ball number 3 is 6
Ball number 4 is 42
Ball number 5 is 3

$ cat rndom.sh

#!/bin/bash
clear
echo "Choices per ball are $1 and the number of balls is $2"
echo
for (( c=1; c<=$2; c++ ))
do
    echo "Ball number $c is $[($RANDOM % $1)]"
done

Note: this is a good way to give out prizes at a meeting. Just make sure everyone has their own number.
One last variation: 

$ shuf -i 1-49 -n18 | xargs -n6
41 34 28 4 36 45
7 2 31 25 38 14
44 32 6 17 11 46

$ shuf -i 1-49 -n24 | xargs -n6
41 13 10 45 29 30
47 43 33 9 32 34
18 36 14 44 48 8
38 31 26 6 35 39

$ shuf -i 1-49 -n28 | xargs -n7
34 10 5 45 43 35 2
42 18 7 22 30 47 23
13 6 19 49 48 4 11
24 8 20 29 31 17 27
</p>

Per ArsTechnica:

Security vulnerability in the GNU Bourne Again Shell (Bash), the command-line shell used in many Linux and Unix operating systems, could leave systems running those operating systems open to exploitation by specially crafted attacks. “This issue is especially dangerous as there are many possible ways Bash can be called by an application,” a Red Hat security advisory warned.

The bug, discovered by Stephane Schazelas, is related to how Bash processes environmental variables passed by the operating system or by a program calling a Bash-based script. If Bash has been configured as the default system shell, it can be used by network–based attackers against servers and other Unix and Linux devices via Web requests, secure shell, telnet sessions, or other programs that use Bash to execute scripts.

Because of its wide distribution, the vulnerability could be as wide-ranging as the Heartbleed bug, though it may not be nearly as dangerous. The vulnerability affects versions 1.14 through 4.3 of GNU Bash. Patches have been issued by many of the major Linux distribution vendors for affected versions, including: Red Hat Enterprise Linux (versions 4 through 7) and the Fedora distributionCentOS (versions 5 through 7)Ubuntu 10.04 LTS, 12.04 LTS, and 14.04 LTSDebianA test on Mac OS X 10.9.4 ("Mavericks") by Ars showed that it also has a vulnerable version of Bash. Apple has not yet patched Bash, though it just issued an update to "command line tools."

While Bash is often thought of just as a local shell, it is also frequently used by Apache servers to execute CGI scripts for dynamic content (through mod_cgi and mod_cgid). A crafted web request targeting a vulnerable CGI application could launch code on the server. Similar attacks are possible via OpenSSH, which could allow even restricted secure shell sessions to bypass controls and execute code on the server. And a malicious DHCP server set up on a network or running as part of an “evil” wireless access point could execute code on some Linux systems using the Dynamic Host Configuration Protocol client (dhclient) when they connect. There are other services that run on Linux and Unix systems, such as the CUPS printing system, that are similarly dependent on Bash that could be vulnerable. There is an easy test to determine if a Linux or Unix system is vulnerable. To check your system, from a command line, type: $ env x='() { :;}; echo vulnerable' bash -c "echo this is a test"If the system is vulnerable, the output will be: vulnerable this is a test

An unaffected (or patched) system will output: $ env x='() { :;}; echo vulnerable' bash -c "echo this is a test" bash: warning: x: ignoring function definition attempt bash: error importing function definition for `x' this is a test

The fix is an update to a patched version of the Bash shell. To be safe, administrators should do a blanket update of their versions of Bash in any case.

-------------------------------------------------------------------------------------------------

My ubuntu 14.04 system before the update:

$ env x='() { :;}; echo vulnerable' bash -c "echo this is a test" vulnerable this is a test

After the update: $ env x='() { :;}; echo vulnerable' bash -c "echo this is a test" bash: warning: x: ignoring function definition attempt bash: error importing function definition for `x' this is a test

Setting a network printer is easy as setting up most any other printer.
You need to know about the printer location make and model. You will also need some administrative rights to install the printer. In this case, we will be using the Cups web based utility to accomplish adding the printer. First, if you do not already have access, you need access.

$ sudo adduser $USER lpadmin

Adding user `eddie' to group `lpadmin' ...

Adding user eddie to group lpadmin

Done.

Note: for more command line goodies, see http://www.cups.org/documentation.php/options.html

Whew, that is all the command line you need to do. Now you need to open your web browser to "localhost:631". Localhost is just a generic name so you do not have to use your real ipaddress. When you first go to cups, you will be asked some rudimentary questions about your setup.

Then you need to choose a printer.

On this network you have one print server that has two parallel ports and one usb port. Notice that cups recognized the equipment (make sure it is turned on!). You could have just as well chose a local printer if that was the one you wanted to use. You can always add more printers later. For now we are choosing pportusb3 or the third port on the printer server that has a usb interface.

The we can choose the printer manufacturer. Press continue. In our case, we have an HP printer. Pretty common nowadays. For the computer to be able to communicate and control the printer, you need what is known as a printer driver. Tradidionally you would have to go find the printer install CD/ DVD. Fortunately Cups already has quite a few printer drivers to choose from. So the printer driver install media will be pretty much a drink coaster.

Our printer is an OfficeJet 6110. Awesome, that is one of the available drivers! So press add printer and let the driver be installed. Then you will need to install the default options. Go with the existing default options till you have seen a print out. You can easily change these options later. Press set default option.

Your printer shoudl be pretty much setup now. You can go the admin pull down menu and print a test page to see if any default options need to change..

Once you have chosen to print a test page, you will get a message at the bottom of the screen about the page being printed.

You are now done with the printer setup. You can visit the other menus or just close the browser. Now the next time you need to print, the print option should show you your printer.

With Linux does not mean you have to do everything via the command line.
For example you might want to import a picture into Tuxpaint. That requires you know what command to use and know where the file to be converted is.

$ tuxpaint-import file2bconverted.ext

Now you could make the program semi gui with using the zenity command.

tpimport.sh

[code]

#================================

#

# Tuxpaint file import catcher

#

#=================================

# Assignments

# --------------------------------

szAnswer=$(zenity --file-selection --title="Select a file to convert to tuxpaint")

datafile=$szAnswer

#=================================

#

# Data input

#---------------------------------

tuxpaint-import $datafile

[/code]

Once you create the file, you will want to make it executable.

$ chmod +x tpimport.sh

From there you could run the program with:

$ ./tpimport.sh

or you would get sort of a gui with:

Then you would get the file selector.

You can select the file to convert from there without knowing a bunch of commands to get to where the file is. Now we can go one step farther and create an icon that can be easily double clicked to execute the shell file. To do that you want to create a launcher. Just right click where you want the launcher to reside such as at the desktop and then click on create launcher.

You will want to select a name for the launcher and even choose a graphic for the launcher but the most important is to choose the tpimport.sh as the file to execute.

Of course, I have already chose the command.

Then finally you have an icon to double click without having to deal with the command line. Tada!

For more information on Zenity: http://linux.die.net/man/1/zenity