linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: xlp <xlp@emtel.net.co>
To: linux-c-programming@vger.kernel.org
Subject: Offtopic.
Date: Mon, 29 Jul 2002 08:26:01 -0500	[thread overview]
Message-ID: <20020729082601.C896@nietzsche.metrotel.net.co> (raw)

Hi, I am writting document in spanish about UNIX programming because I have
found that south american universities are focused on Windows, The students
and teachers think the computer science is Windows, they dont know others
OSes, They dont motivate students to understand OSes internals, I dont
understand Why the degree is "system engienering" if they dont know about
memory manipulation, threads, procress, IO, debuggers, etc.
Why study 5 year of engineering if they will work doing clicks and running
'wizards' ? Where are the south american researcher?, Where is the curiosity?.

I read a documentain that describe signals and It says there are 4 types of
'signal handling enviroments': BSD, SysV unreliable, SysV reliable y POSIX.
What does that means? What are those 'enviroments'?
How can I know which enivorement use certain OS ?
What is "POSIX"?

Also, I am trying to cover all UNIX-like oses in my documentation (HPUX, aix,
sunos, DGUX, *bsd, sco, linux), I'd like to know What is the best computer
science-oriented way to call all those OSes? "Unix based OSes", "Unix like 
OSes" or just "UNIX" ?

bye friends!.

 


             reply	other threads:[~2002-07-29 13:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-29 13:26 xlp [this message]
2002-07-29 13:29 ` Offtopic Carlos Fernandez Sanz
2002-07-29 16:33 ` Offtopic Darío Mariani
2002-07-29 17:43   ` Offtopic xlp
2002-07-30  6:44 ` Offtopic Glynn Clements
  -- strict thread matches above, loose matches on Subject: below --
2003-06-25 19:56 offtopic Fabio Miranda Hamburger
2003-06-25 20:43 ` offtopic Jan-Benedict Glaw
2003-06-26 16:57   ` offtopic Fabio Miranda Hamburger
2003-06-26 22:43     ` offtopic Glynn Clements

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020729082601.C896@nietzsche.metrotel.net.co \
    --to=xlp@emtel.net.co \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).