Quoting Petter Adsen (pet...@synth.no): > On Mon, 13 Apr 2015 20:21:49 +0300 > Reco <recovery...@gmail.com> wrote: > > Let's see as I didn't have OS design in mind. Something like: > > > > Exit codes and their value in real life. > > Strings handling, memory allocation. > > Process control and daemonisation (sp?). > > Signal handling. > > Inter-process communication (sockets, pipes). > > IP protocol use and abuse. > > Shared memory. > > Threads. > > Libraries and their usage. > > Just to pipe in here, these are among the things that I want an > understanding of - especially numbers 3, 4, 5, 6 and 9. With extra > focus on 9 and 6b :) Also things like communication between processes > and devices, file systems, etc. I want to learn how to find out why > things work the way they do, if that makes sense.
If you want to understand the basics, there is any number of tutorials on the web. If you want to play with them, then pick a language and go to a web page like https://docs.python.org/3/library/index.html and write some toy programs. Most of these facilities have wrappers that save you having to write C code to create, say, a couple of sockets that talk to each other. If you try this in C and it doesn't work, it might take you half a day to decide whether you've misunderstood the socket concept or just made a programming error. As Reco said, > > [...], and for the complex program you'll probably want > > something else as by today's standards C has poor result/effort ratio. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150413213643.gl7...@alum.home
