Difference between revisions of "Talk:Basic Linux Command Line for Builders"
Jump to navigation
Jump to search
(linux command notes) |
|||
Line 1: | Line 1: | ||
I always give an example of a man page. -- [[User:MichaelWestwind|MW]] 12:10, 27 Aug 2005 (PDT) | I always give an example of a man page. -- [[User:MichaelWestwind|MW]] 12:10, 27 Aug 2005 (PDT) | ||
+ | |||
+ | ;This page on linuxcommand.org: http://linuxcommand.org/lts0040.php ... could fill an hour of a class with just that. | ||
+ | ;Would talk about this, possibly: | ||
+ | *location of common information, e.g., processor information in the file system | ||
+ | *symbolic links, in relation to GRUB, available kernels, etc. | ||
+ | *Read and write, from the standpoint of both a user and an operating system | ||
+ | *linux can teach you about how an operating system works because you can look at the steps individually. | ||
+ | *a big problem with cl students is they want to start learning about how an operating system works, but even small questions in that direction blow up really quickly. |
Revision as of 12:52, 5 March 2010
I always give an example of a man page. -- MW 12:10, 27 Aug 2005 (PDT)
- This page on linuxcommand.org
- http://linuxcommand.org/lts0040.php ... could fill an hour of a class with just that.
- Would talk about this, possibly
- location of common information, e.g., processor information in the file system
- symbolic links, in relation to GRUB, available kernels, etc.
- Read and write, from the standpoint of both a user and an operating system
- linux can teach you about how an operating system works because you can look at the steps individually.
- a big problem with cl students is they want to start learning about how an operating system works, but even small questions in that direction blow up really quickly.