Changes

|<blockquote><blockquote>::'''Scripting Demo (user account management):''' [ ]<br><br>'''Scripting Skills:'''<blockquote><ul><li>x</li><li>x</li><li>x</li><li>x</li><li>x</li><li>x</li><li>x</li><li>x</li><li>x</li></ul></blockquote><br><br>'''Practical Consideration for scripting in lab2:<br><blockquote>

::Expose students to manipulate data files to efficiently create several user accounts at the same time. This topic should be teachable and emphasize the usefulness of the awk command. Zenity not really required in this case, and should move away from too many zenity examples: use shell scripts to assist the Linux admin. Perhaps have students create a bin directory in the /root account as a collection point of these shell scripts. Could use zenity to create a dialog box to select specific operations. Additional zenity dialog boxes can use text-boxes to obtain information such as username, fullname, etc. It is noted that other important user management operations like '''aging''' user accounts is not included (should this be included for example, temporary accounts for projects within an organization).<br><br>::'''Practical Consideration for scripting in lab4:''' '''Possible "teachable area" to add as end of lab4 for students to learn manipulating data files for mass (batch) processing'''. Do students create simple bash shell script, add elements, then have them copy and paste, then run this more complex script? Is lab2 too long for scripting element to be included? Key elements of scripting elements should be contained in information boxes in lab. Should midterm and/or final exam contain a scripting question? (recommended)<br><br>

|}