5 ms·
Make your own. Most Unix tutorials are particularly poor: as Unix attracts people who like technology (good thing), documentation is technology focused rather t
by nailer 18y ago
Make your own. Most Unix tutorials are particularly poor: as Unix attracts people who like technology (good thing), documentation is technology focused rather than task focused (bad thing).
* Logging in
* Making a test file. Making folders, copying, moving, removing files and folders.
* Show how the filesystem standard sorts files by type (binary, system binary, library, config files and service scripts) and by importance (required to recover the system in an emergency).
* Disk management - learning how volumes are attached to different folders (the filesystem table), and how volumes are named
* Installing software packages
* Starting, stopping, restarting, and checking the status of services
* Managing processes, using kill/killall and kill -KILL/killall -KILL
- notauser 18y agoFor normal people, diagrams help. A tree diagram of the file system, labeled with what goes where and why, seems to fix about 99.99% of problems new users have getting to grips with Linux. /bin/what ???
- nailer 18y agoOh and two more: * Ensure they know that commands are assumed to work, and won't show show any output if they do work - eg, a file copy. If they don't work, they'll see an error message. * Tell people what things mean. Copy, list, move. Binary. Variable. Et Cetera. Init table. Filesystem table. By showing people that these aren't arbitrary letter combinations, but actually have real meaning, you'll make them easier to remember.
- manvsmachine 18y agoWhile it doesn't cover all the topics you mentioned, http://www.linuxcommand.org/ http://www.linuxcommand.org/ is definitely worth a look as it has more of a task-based approach. The SuperMan pages are great; they organize all the man pages for common packages into categories based on functionality (eg, text processing, multimedia, networking, etc).
- deleted 18y ago[deleted]