0

Ubuntu to go: Installing Linux onto a usb flash drive

by

Another lost article, originally from May 4, 2009

Putting Ubuntu on a flash drive, can seem a daunting task. But if you follow these steps, you’ will have a portable secure operating system.

Here’s what you”ll need:

A computer with:

USB Ports
256 meg of ram
cdrom
USB flash drive (at least 4 G)
32 bit Ubuntu 9.04 Install CD (desktop)
(download from here: Download Ubunutu)
A live (hot) internet connection

WARNING: CHOOSING THE WRONG DEVICE CAN RENDER YOUR HARD DRIVE UNBOOTABLE. IF YOU’RE NOT SURE, YOU MAY WANT TO REMOVE THE PLUGS FROM YOU HARD DRIVE BEFORE STARTING.

1. Boot off the install cd.

2. Choose Install Ubuntu and hit enter

3. When you come to the screen that says: “Prepare disk space” (step 4 of 7) on top,
choose “specify partitions manually (advanced)”

4. the usb drive (on my system) is called /dev/sdc

5. delete the partition on this drive, so you can start fresh.

6. It should show /dev/sdc
free space (size of drive — 8065 mb in my case — 8 G)

7. Select the “free space” for the usb drive by single clicking it (left mouse button)

8. Select “new partition” on the bottom of the screen.

We are going to create a 1 G fat32 partition for windows, and then the rest for linux.

Windows (will become /dev/sdc1)
New Partition should read: Primary
Size should be: 1024 meg
Beginning
Use as FAT32 file system
Mount Point: /dos

Select the remaining “free space” for the usb drive by single clicking it (left mouse button)

8. Select “new partition” on the bottom of the screen.

Linux (will become /dev/sdc2)
New partition should read: Primary
Size should be the remaining full size of the USB Drive (7039 meg)
Beginning
Use as ext2 file system (we want a “non-journaled” file system)
(USB flash drives do NOT have a fast transfer rate (4-5 meg tops), so we want a non-journaled file system)

Mount Point should be / (root directory)

The great thing is that windows will NOT see any of the Linux on the flash drive. However, Linux WILL see the windows partition. So you can easily exchange information between Windows and Linux.

to see the Windows Partition in Linux simply go into terminal mode (after the install of course) and type:

cd /dos (that was the mount point we created above)

So it should look like this before proceeding to the next step:

Devices Type Size
/dev/sdc1 fat32 1023
/dev/sdc2 ext2 7039

9. Hit forward and you will see “Who are you?” (screen 5 of 7) fill out as desired.

10. if you get the message “there are no users or operating system suitable for importing from” error – that’s normal – (step 6 of 7) just go forward.

11. When you arrive at step 7 of 7, this is the tricky part. “Ready to Install” We need to make the flash drive bootable.

There is an “advanced” tab at the bottom right of the screen. Click on that.

Click on “Install Boot Loader” and choose the correct DEVICE (not partition) device. In my case /dev/sdc

WARNING: CHOOSING THE WRONG DEVICE CAN RENDER YOUR HARD DRIVE UNBOOTABLE. IF YOU’RE NOT SURE, YOU MAY WANT TO REMOVE THE PLUGS FROM YOU HARD DRIVE BEFORE STARTING.

12. Click on install, and sit back. Like Alton Brown says: “Your patience WILL be rewarded!”

13. Boot up off your usb drive, and we are going to make a performance enhancement.

14. Open up a terminal window and type

cd /etc # go to the /etc directory

sudo cp fstab fstab.org # make a copy of the file structure table (always have a path back!)

sudo nano fstab

change “relatime” to “noatime”

from: http://en.wikipedia.org/wiki/Fstab

By default Linux records when files are last accessed, modified and created. This behaviour can be controlled with the noatime option, which will prevent this information from being recorded. The advantage might be a performance increase, especially when files are accessed and modified often.

control+o to write the file changes, then control+x to exit.
(hold down the control key, and hit the letter)

NOTE: if you screw up fstab, your system may NOT boot. DON’T panic!

boot into recovery mode, then choose “Drop to root shell prompt with out networking”

mount -o remount rw / # mount root as read/write access

cd /etc # change to /etc

rm fstab # removes the existing (hosed) fstab

cp fstab.org fstab # copy back the original fstab

15. Install updates and enjoy! You now have in your pocket, a secure, portable operating system.

if you do a df (display free) at terminal mode you will see that Linux
has used approximately 2.5 G (yes with “X” installed) and have about 4G free!

16. One caution. In order to avoid file corruption, I always “shutdown” when done using my ubuntu2go flash drive. Removing the flash drive before the system has shutdown, may result in file corruption.

0

Configuring APC (American Power Conversion) UPS Support for Linux

by

This was an old article from June 23, 2009 that was somehow lost.

Installing APC (American Power Conversion) UPS (Un-interruptible Power Source) Support for Ubuntu Linux

(debunking the half truths)

Information garnered from: apcupsd.org

first step

sudo apt-get install apcupsd

1. HALF-TRUTH: Problem
2.6 kernels use udev and some distributions to not configure it to automatically create /dev/usb/hiddev?? as they should, causing apcupsd to fail to locate the UPS.
Workaround

Edit the file /etc/udev/rules.d/50-udev.rules, and add the following:

KERNEL=”hiddev*”, NAME=”usb/hiddev%n”

This results in a boot time error in Ubuntu, and doesn’t work.

TRUTH: This doesn’t work, don’t use it.

——–

2. HALF-TRUTH: Problem
On some systems such as Slackware 10.0, no USB devices will show up (see the next section).
Workaround

Add the following to rc.local

mount -t usbdevfs none /proc/bus/usb

TRUTH: mount requires root access:

nwayno@H:/$ sudo mount -t usbdevfs none /proc/bus/usb
[sudo] password for nwayno:
mount: unknown filesystem type ‘usbdevfs’

And that didn’t work, but here’s why:

From man mount (output)

Earlier, usbfs was known as usbdevfs.
So the mount really should look like this:

sudo mount -t usbfs none /proc/bus/usb

3. Verifying Device Detection and Driver

To make sure that your USB subsystem can see the UPS, just do this from a shell prompt:

cat /proc/bus/usb/devices

and sure enough, this is what I got:

T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=051d ProdID=0002 Rev= 1.06
S: Manufacturer=American Power Conversion
S: Product=Back-UPS BR 800 FW:9.o2 .D USB FW:o2
S: SerialNumber=QB0351236370
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 24mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 6 Ivl=10ms

This is what my apcupsd.conf file looks like:

Important things to change in the following:

UPSNAME WaynoUps # name for ups
UPSCABLE usb # type of cable
UPSTYPE usb # yes it’s usb
NISIP 0.0.0.0 # this is what made networking work chg from localhost
DEVICE

nwayno@Homer:/etc/apcupsd$ cat apcupsd.conf

#—– BEGIN /etc/apcupsd/apcupsd.conf —–
## apcupsd.conf v1.1 ##
#
# for apcupsd release 3.14.4 (18 May 2008) – debian
#
# “apcupsd” POSIX config file

#
# ========= General configuration parameters ============
#

# UPSNAME xxx
# Use this to give your UPS a name in log files and such. This
# is particulary useful if you have multiple UPSes. This does not
# set the EEPROM. It should be 8 characters or less.
UPSNAME WaynoUps

# UPSCABLE
# Defines the type of cable connecting the UPS to your computer.
#
# Possible generic choices for
are:
# simple, smart, ether, usb
#
# Or a specific cable model number may be used:
# 940-0119A, 940-0127A, 940-0128A, 940-0020B,
# 940-0020C, 940-0023A, 940-0024B, 940-0024C,
# 940-1524C, 940-0024G, 940-0095A, 940-0095B,
# 940-0095C, M-04-02-2000
#
UPSCABLE usb

# To get apcupsd to work, in addition to defining the cable
# above, you must also define a UPSTYPE, which corresponds to
# the type of UPS you have (see the Description for more details).
# You must also specify a DEVICE, sometimes referred to as a port.
# For USB UPSes, please leave the DEVICE directive blank. For
# other UPS types, you must specify an appropriate port or address.
#
# UPSTYPE DEVICE Description
# apcsmart /dev/tty** Newer serial character device,
# appropriate for SmartUPS models using
# a serial cable (not USB).
#
# usb Most new UPSes are USB. A blank DEVICE
# setting enables autodetection, which is
# the best choice for most installations.
#
# net hostname:port Network link to a master apcupsd
# through apcupsd’s Network Information
# Server. This is used if you don’t have
# a UPS directly connected to your computer.
#
# snmp hostname:port:vendor:community
# SNMP Network link to an SNMP-enabled
# UPS device. Vendor is the MIB used by
# the UPS device: can be “APC”, “APC_NOTRAP”
# or “RFC” where APC is the powernet MIB,
# “APC_NOTRAP” is powernet with SNMP trap
# catching disabled, and RFC is the IETF’s
# rfc1628 UPS-MIB. You usually want “APC”.
# Port is usually 161. Community is usually
# “private”.
#
# dumb /dev/tty** Old serial character device for use
# with simple-signaling UPSes.
#
# pcnet ipaddr:username:passphrase
# PowerChute Network Shutdown protocol
# which can be used as an alternative to SNMP
# with AP9617 family of smart slot cards.
# ipaddr is the IP address of the UPS mgmt
# card. username and passphrase are the
# credentials for which the card has been
# configured.
#
UPSTYPE usb
DEVICE

# POLLTIME
# Interval (in seconds) at which apcupsd polls the UPS for status. This
# setting applies both to directly-attached UPSes (UPSTYPE apcsmart, usb,
# dumb) and networked UPSes (UPSTYPE net, snmp). Lowering this setting
# will improve apcupsd’s responsiveness to certain events at the cost of
# higher CPU utilization. The default of 60 is appropriate for most
# situations.
#POLLTIME 60

# LOCKFILE # Path for device lock file. Not used on Win32.
LOCKFILE /var/lock

# SCRIPTDIR # Directory in which apccontrol and event scripts are located.
SCRIPTDIR /etc/apcupsd

# PWRFAILDIR # Directory in which to write the powerfail flag file. This file
# is created when apcupsd initiates a system shutdown and is
# checked in the OS halt scripts to determine if a killpower
# (turning off UPS output power) is required.
PWRFAILDIR /etc/apcupsd

# NOLOGINDIR # Directory in which to write the nologin file. The existence
# of this flag file tells the OS to disallow new logins.
NOLOGINDIR /etc

#
# ======== Configuration parameters used during power failures ==========
#

# The ONBATTERYDELAY is the time in seconds from when a power failure
# is detected until we react to it with an onbattery event.
#
# This means that, apccontrol will be called with the powerout argument
# immediately when a power failure is detected. However, the
# onbattery argument is passed to apccontrol only after the
# ONBATTERYDELAY time. If you don’t want to be annoyed by short
# powerfailures, make sure that apccontrol powerout does nothing
# i.e. comment out the wall.
ONBATTERYDELAY 6

#
# Note: BATTERYLEVEL, MINUTES, and TIMEOUT work in conjunction, so
# the first that occurs will cause the initation of a shutdown.
#

# If during a power failure, the remaining battery percentage
# (as reported by the UPS) is below or equal to BATTERYLEVEL,
# apcupsd will initiate a system shutdown.
BATTERYLEVEL 5

# If during a power failure, the remaining runtime in minutes
# (as calculated internally by the UPS) is below or equal to MINUTES,
# apcupsd, will initiate a system shutdown.
MINUTES 3

# If during a power failure, the UPS has run on batteries for TIMEOUT
# many seconds or longer, apcupsd will initiate a system shutdown.
# A value of 0 disables this timer.
#
# Note, if you have a Smart UPS, you will most likely want to disable
# this timer by setting it to zero. That way, you UPS will continue
# on batteries until either the % charge remaing drops to or below BATTERYLEVEL,
# or the remaining battery runtime drops to or below MINUTES. Of course,
# if you are testing, setting this to 60 causes a quick system shutdown
# if you pull the power plug.
# If you have an older dumb UPS, you will want to set this to less than
# the time you know you can run on batteries.
TIMEOUT 0

# Time in seconds between annoying users to signoff prior to
# system shutdown. 0 disables.
ANNOY 300

# Initial delay after power failure before warning users to get
# off the system.
ANNOYDELAY 60

# The condition which determines when users are prevented from
# logging in during a power failure.
# NOLOGON [ disable | timeout | percent | minutes | always ]
NOLOGON disable

# If KILLDELAY is non-zero, apcupsd will continue running after a
# shutdown has been requested, and after the specified time in
# seconds attempt to kill the power. This is for use on systems
# where apcupsd cannot regain control after a shutdown.
# KILLDELAY 0 disables
KILLDELAY 0

#
# ==== Configuration statements for Network Information Server ====
#

# NETSERVER [ on | off ] on enables, off disables the network
# information server. If netstatus is on, a network information
# server process will be started for serving the STATUS and
# EVENT data over the network (used by CGI programs).
NETSERVER on

# NISIP
# IP address on which NIS server will listen for incoming connections.
# This is useful if your server is multi-homed (has more than one
# network interface and IP address). Default value is 0.0.0.0 which
# means any incoming request will be serviced. Alternatively, you can
# configure this setting to any specific IP address of your server and
# NIS will listen for connections only on that interface. Use the
# loopback address (127.0.0.1) to accept connections only from the
# local machine.
#NISIP 127.0.0.1
#
# change ip from local host to any interface GU 07/07/2009
#
NISIP 0.0.0.0

# NISPORT default is 3551 as registered with the IANA
# port to use for sending STATUS and EVENTS data over the network.
# It is not used unless NETSERVER is on. If you change this port,
# you will need to change the corresponding value in the cgi directory
# and rebuild the cgi programs.
NISPORT 3551

# If you want the last few EVENTS to be available over the network
# by the network information server, you must define an EVENTSFILE.
EVENTSFILE /var/log/apcupsd.events

# EVENTSFILEMAX
# By default, the size of the EVENTSFILE will be not be allowed to exceed
# 10 kilobytes. When the file grows beyond this limit, older EVENTS will
# be removed from the beginning of the file (first in first out). The
# parameter EVENTSFILEMAX can be set to a different kilobyte value, or set
# to zero to allow the EVENTSFILE to grow without limit.
EVENTSFILEMAX 10

#
# ========== Configuration statements used if sharing =============
# a UPS with more than one machine

#
# Remaining items are for ShareUPS (APC expansion card) ONLY
#

# UPSCLASS [ standalone | shareslave | sharemaster ]
# Normally standalone unless you share an UPS using an APC ShareUPS
# card.
UPSCLASS standalone

# UPSMODE [ disable | share ]
# Normally disable unless you share an UPS using an APC ShareUPS card.
UPSMODE disable

#
# ===== Configuration statements to control apcupsd system logging ========
#

# Time interval in seconds between writing the STATUS file; 0 disables
STATTIME 0

# Location of STATUS file (written to only if STATTIME is non-zero)
STATFILE /var/log/apcupsd.status

# LOGSTATS [ on | off ] on enables, off disables
# Note! This generates a lot of output, so if
# you turn this on, be sure that the
# file defined in syslog.conf for LOG_NOTICE is a named pipe.
# You probably do not want this on.
LOGSTATS off

# Time interval in seconds between writing the DATA records to
# the log file. 0 disables.
DATATIME 0

# FACILITY defines the logging facility (class) for logging to syslog.
# If not specified, it defaults to “daemon”. This is useful
# if you want to separate the data logged by apcupsd from other
# programs.
#FACILITY DAEMON

#
# ========== Configuration statements used in updating the UPS EPROM =========
#

#
# These statements are used only by apctest when choosing “Set EEPROM with conf
# file values” from the EEPROM menu. THESE STATEMENTS HAVE NO EFFECT ON APCUPSD.
#

# UPS name, max 8 characters
#UPSNAME UPS_IDEN

# Battery date – 8 characters
#BATTDATE mm/dd/yy

# Sensitivity to line voltage quality (H cause faster transfer to batteries)
# SENSITIVITY H M L (default = H)
#SENSITIVITY H

# UPS delay after power return (seconds)
# WAKEUP 000 060 180 300 (default = 0)
#WAKEUP 60

# UPS Grace period after request to power off (seconds)
# SLEEP 020 180 300 600 (default = 20)
#SLEEP 180

# Low line voltage causing transfer to batteries
# The permitted values depend on your model as defined by last letter
# of FIRMWARE or APCMODEL. Some representative values are:
# D 106 103 100 097
# M 177 172 168 182
# A 092 090 088 086
# I 208 204 200 196 (default = 0 => not valid)
#LOTRANSFER 208

# High line voltage causing transfer to batteries
# The permitted values depend on your model as defined by last letter
# of FIRMWARE or APCMODEL. Some representative values are:
# D 127 130 133 136
# M 229 234 239 224
# A 108 110 112 114
# I 253 257 261 265 (default = 0 => not valid)
#HITRANSFER 253

# Battery charge needed to restore power
# RETURNCHARGE 00 15 50 90 (default = 15)
#RETURNCHARGE 15

# Alarm delay
# 0 = zero delay after pwr fail, T = power fail + 30 sec, L = low battery, N = never
# BEEPSTATE 0 T L N (default = 0)
#BEEPSTATE T

# Low battery warning delay in minutes
# LOWBATT 02 05 07 10 (default = 02)
#LOWBATT 2

# UPS Output voltage when running on batteries
# The permitted values depend on your model as defined by last letter
# of FIRMWARE or APCMODEL. Some representative values are:
# D 115
# M 208
# A 100
# I 230 240 220 225 (default = 0 => not valid)
#OUTPUTVOLTS 230

# Self test interval in hours 336=2 weeks, 168=1 week, ON=at power on
# SELFTEST 336 168 ON OFF (default = 336)
#SELFTEST 336

#—– END /etc/apcupsd/apcupsd.conf —–

————-

4. Testing

HALF-TRUTH: Run apctest by invoking it with no arguments.

It will read your installed apcupsd.conf configuration (so it knows where to find the UPS) and then it will present you with the following output:

nwayno@H:/etc/apcupsd$ apctest

Could not create apctest.output: Permission denied
2009-06-22 18:18:59 Could not create apctest.output: Permission denied
apctest 3.14.4 (18 May 2008) debian
Could not create apctest.output: Permission denied
Checking configuration …
Could not create apctest.output: Permission denied
Attached to driver: usb
Could not create apctest.output: Permission denied
sharenet.type = DISABLE
Could not create apctest.output: Permission denied
cable.type = USB_CABLE
Could not create apctest.output: Permission denied

You are using a USB cable type, so I’m entering USB test mode
Could not create apctest.output: Permission denied
mode.type = USB_UPS
Could not create apctest.output: Permission denied
Setting up the port …
Could not create apctest.output: Permission denied

TRUTH: apctest requires ROOT access

nwayno@H:/etc/apcupsd$ sudo apctest

2009-06-22 18:16:59 apctest 3.14.4 (18 May 2008) debian
Checking configuration …
Attached to driver: usb
sharenet.type = DISABLE
cable.type = USB_CABLE

You are using a USB cable type, so I’m entering USB test mode
mode.type = USB_UPS
Setting up the port …
Hello, this is the apcupsd Cable Test program.
This part of apctest is for testing USB UPSes.

Getting UPS capabilities…SUCCESS

Please select the function you want to perform.

1) Test kill UPS power
2) Perform self-test
3) Read last self-test result
4) Change battery date
5) View battery date
6) View manufacturing date
7) Set alarm behavior
8 ) Set sensitivity
9) Set low transfer voltage
10) Set high transfer voltage
11) Quit

Select function number: 11

2009-06-22 18:17:14 End apctest.
nwayno@H:/etc/apcupsd$

5. HALF Truth:

and the client machine side: (SuSE)

## apcupsd.conf v1.1 ##
UPSCABLE ether
UPSTYPE net
LOCKFILE /var/lock
DEVICE server-network-address:3551
UPSCLASS standalone
UPSMODE disable
POLLTIME 10

infact it won’t work as is:

Change POLLTIME to NETTIME

so the file on the CLIENT looks like:

## apcupsd.conf v1.1 ##
UPSCABLE ether
UPSTYPE net
LOCKFILE /var/lock
DEVICE 192.168.0.102:3551
UPSCLASS standalone
UPSMODE disable
NETTIME 10

NOTE: You may need to bring down the firewall on the server side:

sudo ufw disable

6. and if we did our home work right — pulling the plug:

Broadcast Message from root@H (somewhere) at 17:09 (SERVER/UBUNTU)

Power failure on UPS WaynoUps. Running on batteries. (SERVER/UBUNTU)

Broadcast Message from root@P (somewhere) at 17:09 (CLIENT/SuSE)

Power failure on UPS WaynoUps. Running on batteries. (CLIENT/SuSE)

Broadcast Message from root@H (somewhere) at 17:10 (SERVER/UBUNTU)

Power has returned on UPS WaynoUps… (SERVER/UBUNTU)

Broadcast Message from root@P (somewhere) at 17:10 (CLIENT/SuSE)

Power has returned on UPS WaynoUps… (CLIENT/SuSE)

(thanks to Loni/lornix.com) for her assistance in figuring out why the client side wouldn’t work.

ADDENDUM: thanks Loni

1

Dear Comcast — I am NOT an idiot

by

Dear Comcast:

Today I interacted via telephone with one of your offshore tech support agents, since I was unable to go online. customer.comcast.net was unable to tell me of any outages in my area. One of my online experiences was with a computer anyway since it failed the Turing test.

Your Customer Service mark would vastly improve if you would stop assuming that the customer is an idiot.

Routers have absolutely nothing to do with whether or not my modem is online. I do not need to go out and buy and new modem.

If the modem is offline — That is controlled by your equipment, NOT mine.

LISTEN!

Wayno

0

How to adjust the skip time during playback in mythtv

by

skip forward/back setting in mythtv

Thank you jya_ from #mythtv-users (irc.freenode.net) for identifying the location to change the skip time for playback using mythtv.

By default, mythtv skips 30 seconds FORWARD using the Right Arrow Key (->) symbol, and skips 5 seconds BACK using the Left (< - ) symbol on the keyboard. I wanted to change the skip back time to 15 seconds instead of 5...but where did they hide the setting?

The adjustment is in mythfrontend.

Navigate to the settings from mythfrontend:

Setup -> Video -> Playback Groups -> Default

Your screen looks like:

skip forward/back setting in mythtv

Or whatever works for you. Thanks jya_.

Wayno

0

mythtv schedules are scrambled by eit scan

by

EIT Scan and Mythtv

Everytime I looked at the the schedules in mythtv I had gotten from Schedules Direct, They were scrambled. The titles and the times would be correct, but the description did NOT match the programme. I contacted Schedules Direct and found out about something called EIT. Event Information Table. EIT is part of the ATSC standard.

EIT information is transmitted along with the programme from over-the-air broadcasts. The effect is, the EIT information “updates/replaces/clobbers/fubars” the information already present from Schedules Direct, and scrambles the schedule listing.

If you are getting scheduling information from Schedules Direct you need to disable/uncheck the scan in mythtv-setup, Video Sources.

Your screen should look like:

EIT Scan and Mythtv

Many thanks to Robert K. from Schedules Direct.

Wayno

0

How to update the google talk / hangouts plugin for Linux

by

Google Hangouts Plugin

This threw me for a loop! Literally.

I wanted to use Google Hangouts, but it told me I needed to update the plugin.

I downloaded the plugin, installed it, fired up hangouts again, only to be told, I had to update the plugin again! The screen looks something like this:

Google Hangouts Plugin

What the? I just installed the plugin! How could you tell me I needed to install it again?

I did a sanity check.


apt-cache policy google-talkplugin

I got back the following:

google-talkplugin:
Installed: 3.10.2.0-1
Candidate: 4.9.1.0-1
Version table:
4.9.1.0-1 0
500 http://dl.google.com/linux/talkplugin/deb/ stable/main amd64 Packages
*** 3.10.2.0-1 0
100 /var/lib/dpkg/status

The page Google had sent me to, was trying to install the version 3.10 plugin. That isn’t going to work.

apt-cache policy shows me the installed version, 3.10 and the current version in the repo. 4.9!

So I told it to get the latest version in the repository.


sudo apt-get install google-talkplugin

When I redid the apt-cache policy it showed:

google-talkplugin:
Installed: 4.9.1.0-1
Candidate: 4.9.1.0-1
Version table:
*** 4.9.1.0-1 0
500 http://dl.google.com/linux/talkplugin/deb/ stable/main amd64 Packages
100 /var/lib/dpkg/status

and behold!

hangouts plugin

Wayno

Ubuntu Linux Shell Scripts Repository – [DOWNLOAD!]

by

Ok, Jeremy here from deep inside (that was a metaphor) Dynamic Designz Web-Development = hard at work on developing new and interesting articles for my readers at http://dynamicdesignz.net/log on various tech aspects of the world! Including but not limited to our FAVORUITE subject here at pkill-9.com! – UBUNTU LINUX!

Yes! I am here to tell you about a little project I am working on that is nothing short of anything I have ever really seen before in the Linux community and if not at least the Ubuntu community, an online FTP/WGET-based repository for a wide array of Ubuntu bash-based programming, (try saying that ten times fast!) – these are various ‘little’ scripts I personally have written to automate some of the most obscure tasks in Linux to the average user such as access to ‘hidden’ configuration files in Ubuntu as well log files, system and network init services and various networking scripts, NOT TO MENTION; scripts to automate some of the more daunting tasks in Kali Linux formally known as Backtrack – the hacker linux distro!

Although the archive is not entirely complete to my spcifications I have zipped and uploaded a hefty sized folder full of these scripts available for download OF COURSE, for FREE!

On a more personal note, I started to write an article on my blog explaining all this with copies of download mirrors in different formats but still have not finished it, I wanted to put it on here at pkill-9 so that some of Wayno’s readers could see it and enjoy it as well and hopfully as much as I do!

As usual you are free to modify, remodify, redistribute and share! – Please by all means if you can build off of what I started and make them better, please DO and re-upload them! I would love a copy…

Anyway… Here are the Mirrors!

wget http://dynamicdesignz.net/log/uploads/2014/01/scripts.tar
wget http://dynamicdesignz.net/scripts.zip

Here you can look at an entire list and download one script at a time via my public Dropbox account!
https://www.dropbox.com/sh/08fv596vbdny9hk/bf6rO3e2Oa

OR DOWNLOAD THE FULL LIST DIRECTLY FROM DROPBOX HERE!
https://www.dropbox.com/s/5c1kam7fgagzlfe/scripts.tar

-For more information on this list or to have your version re-uploaded to this location please email me: j.fuller@dynamicdesignz.net

-Jeremy

0

How to setup Kindle on an android based device

by

kindle_settings

I am a n00b when it comes to the Kindle world. When The Narrow Road came out with their e-book version, I was eager to read. As I discovered, there are no posts on how to set up an Android based device for Kindle.

The following assumes you have an account with amazon.com

1. Download and install the Kindle application from the Android Play Store. Sign into the Kindle application.

2. We need to get some information from the Kindle Application. To access the settings, you will see 3 horizontal lines (see picture below) in the top LEFT of the screen (it is depicted on the top right here, but the 3 horizontal lines are what you are looking for in the top LEFT.). Press that, and it will open up the menu.

kindle_login

3. We want to access the settings, so again press the settings button (see screen above).

4. The information we are after is Send to Kindle Email Address (highlighted in Red Below.) Write that down, we will use that later.

kindle_settings

5. Now we want to login to our amazon account. Go to the dropdown menu under your account (see below), and LEFT click on Manage Your Kindle.

manage_kindle

6. Click on Personal Document Settings on the left (see red highlight.) We want to add Add A New Approved Email Address.

personal_document_settings

7. Add the email address you will be emailing the document from.

Otherwise, you will get an email saying,

Dear Customer,

The following document, sent to you by yourname@youremail.com could not be delivered to your Kindle because the sender is not in your Kindle approved e-mail list.

(Been there, done that)

8. And now…..remember that email address we wrote down in step 4? Now we compose an email with the attachment. (Note for Kindle books we want to email the book as a mobi attachment to the address obtained in step 4.)

email_kindle_book

9. Et voilà:

mobi_book_on_kindle

0

Comcast removes clear qam channels from their system

by

comcast channel scan

comcast_scan

The nation’s largest cable tv provider, Comcast provided clear qam (or local channels in High Definition withOUT a cable box) over their cable system. Apparently, that has now come to an end.

A channel scan today yielded only 2 channels. Both Comcast info-mercial channels.

So if you were counting on tuners like the hdhomerun to tune and record cable channels, those days are ended.

Comcast could NOT be reached for comment.

Wayno

1 2 3 4 5 19 20