From: Steve Beaty <beaty@emess.mscd.edu>
To: root@chaos.analogic.com
Cc: beaty@emess.mscd.edu (Steve Beaty), linux-kernel@vger.kernel.org
Subject: Re: sigaction, fork, malloc, and futex
Date: Thu, 6 May 2004 15:41:34 -0600 (MDT) [thread overview]
Message-ID: <200405062141.i46LfYVg017800@emess.mscd.edu> (raw)
In-Reply-To: <Pine.LNX.4.53.0405041928170.14876@chaos> from "Richard B. Johnson" at May 04, 2004 07:37:50 PM
> Sure buggy code. There are only a few things you can do from
> a signal handler and I'm fairly sure fork() isn't one of them.
well, one should only set values and deal with them somewhere in
signal handlers, but...
> Did you just invent this as a way of concatenating system calls
> to see what works? Surely you don't have a program that does this
> do you?
well, yes, but it is a classroom assignment so not "real" code.
the assignment is to create a simulated disk drive (a process) via
a "system call" that signals a "kernel". perhaps we should really
fork and exec...
--
Dr. Steve Beaty (B80) Associate Professor
Metro State College of Denver beaty@emess.mscd.edu
VOX: (303) 556-5321 Science Building 134C
FAX: (303) 556-5381 http://clem.mscd.edu/~beatys/
next prev parent reply other threads:[~2004-05-06 21:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 20:15 Steve Beaty
2004-05-04 22:30 ` chris
2004-05-04 22:56 ` Zan Lynx
2004-05-04 23:16 ` Andreas Schwab
2004-05-06 21:37 ` Steve Beaty
2004-05-06 22:22 ` Zan Lynx
2004-05-06 21:36 ` Steve Beaty
2004-05-04 23:37 ` Richard B. Johnson
2004-05-06 21:41 ` Steve Beaty [this message]
2004-05-05 0:38 ` Edgar Toernig
2004-05-06 21:47 ` Steve Beaty
[not found] <1SeIE-Dy-17@gated-at.bofh.it>
[not found] ` <1ShG9-2Yt-11@gated-at.bofh.it>
2004-05-04 23:57 ` Pascal Schmidt
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=200405062141.i46LfYVg017800@emess.mscd.edu \
--to=beaty@emess.mscd.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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
all inboxes | Powered by JetHome®