Author(s):	Martin Kealey
Location	OGGB4
Date	jan Wed 14	Days Raw Files
Start	10:40	First Raw Start	10:32
Duration	1:40:00	Offset	0:07:22
End	12:20	Last Raw End	12:24
Chapters	00:00
Total cuts_time	100 min.

http://lca2015.linux.org.au/schedule/30276/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Bashing_the_Shell_Advanced_Scripting.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	You may know Bash as the command-line interpreter for most Linux users, but it is also the default shell script interpreter in many Linux distributions. This tutorial would suit people who: * have fallen into being a sysadmin and need to understand what they've gotten their hands on; * have been using the command-line for a while and have started writing small scripts to automate some of your tasks, but have often encountered strange or puzzling behaviour; * have tried looking at the scripts in /etc/init.d, and been found gibbering under the bed hours later; * want to understand the differences between classic Bourne shell, POSIX shell, Bash, Dash and Ksh; * have used other programming languages but have found the Shell too arcane. To gain the most benefit from this tutorial, it would be helpful to have either some programming experience, or at least a year of reasonably extensive use of the command-line. Included: * a brief history of Shells * process & environment management * common pitfalls and techniques to avoid them * guidance on "best practice" * special features for interactive use * when to give up and use something else Bring your problems, curiosity, and curly questions, for a hands-on session with worked examples. markdown
Comment:	production notes