Let me add that the script you are thinking about learning to write could be done with Bash scripting - Python is a bit of overkill, maybe? (Not trying to say learning Python might not be a good thing for you, but Bash is already there, and ready to go on any Linux machine.)
(I don't know what you might already know, but think of Bash scripting kind of like old-fashioned MS-DOS Batch files on steroids if that will help.)
There are all kinds of great articles out there on Bash scripting, and web sites that have a lot of ready-made "script recipes" that might give you a jump-start on what you want.
A gentle intro to the subject from Linux.com.
https://www.linux.com/learn/tutorials/284789-writing-a-simple-bash-script-This is from the Linux Documentation Project, and a great place to start.
http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO.htmlThis from IBM DeveloperWorks makes clear why Bash is a good choice, and has some great pointers, too.
http://www.ibm.com/developerworks/linux/library/l-bash/index.htmlMendel Cooper at the University of Illinois has put together one of the most definitive guides to Bash scripting I've ever seen, available online for free.
http://www.museum.state.il.us/ismdepts/library/linuxguides/abs-guide/A lot of what's involved,
no matter what language you write in, is knowing what to write to get your tasks accomplished. If you know how what you want to do is most easily accomplished, it'll be a snap no matter what language it's written in. (Good design is the key to good programming. Time well spent in the design phase will tend to cut time in the coding and debug phases tremendously, and help you turn out better, more efficient, and more compact code.)
If these installs are "pure" PCLinuxOS LXDE, a simple replacement of the users' ~/.config/ folders that relate to LXDE should do the trick for ya without disturbing user data that may be on the machine. I
think the folders and files of interest would be (and where a folder is listed, all files and subfolders are of interest):
| ~/.config/leafpad | - folder for the default text editor for LXDE |
| ~/.config/libfm | - folder for libraries for PCManFM |
| ~/.config/lxautostart | - folder controlling what LXDE starts up automatically on login |
| ~/.config/lxpanel | - folder controlling how the LXDE Panel is configured |
| ~/.config/lxsession | - folder controlling how the LXDE session is configured, including the desktop |
| ~/.config/lxterminal | - folder controlling how LXTerminal is configured |
| ~/.config/openbox | - folder controlling OpenBox, if you use it as your window manager |
| ~/.config/pcmanfm | - folder controlling configuration of PCManFM |
| ~/.config/lxtask.conf | - file controlling how LXDE Task Manager is configured. |
| ~/.config/user-dirs.dir | - file controlling what DBUS uses for user directories? (Still learning about this...) |
| ~/.config/user-dirs.local | - file controlling how DBUS behaves in the local environment? |
It might be "cheaper" to just replace the entire ~/.config/ hierarchy, but this affects application configurations and a lot of other stuff, too. (Might be what you want?)
You might also look into what /etc/skel does for a Linux System - basically it provides sane "defaults" for user accounts when they are created. Alterations here affect all users, and are only to be undertaken if you're SURE all users need to be affected.
Just17's questions about student accounts and such are right on the money. Answering these will help define the tasks any program would have to accomplish.
Trying to administer computers used by bright young students (who always have a propensity for surprising even the best system administrator) is a real challenge. It's an environment where you'll learn fast or die - you'll get sharper at Linux because you have to.
Good luck, and good hunting, Crow!
Later ON,
D
