From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] ed.c on Unix v5
Date: Sat, 19 Dec 2015 07:12:20 -0500 (EST) [thread overview]
Message-ID: <20151219121220.EC3A718C0A3@mercury.lcs.mit.edu> (raw)
> From: Mark Longridge <cubexyz at gmail.com>
> if one looks at /lib/libc.a via 'ar t getpid.o' you can see the object
> file getpid.o
Library, schlibrary! The important question is 'is it in the kernel source'?
(Although now that I think about it, if the library routine tries to use a
non-existent system call, it should return an error. It would be interested
to disassemble the library routine, and see what it thinks it is doing.)
Noel
next reply other threads:[~2015-12-19 12:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 12:12 Noel Chiappa [this message]
2015-12-19 12:40 ` Mark Longridge
-- strict thread matches above, loose matches on Subject: below --
2015-12-19 15:47 Noel Chiappa
2015-12-19 15:10 Noel Chiappa
2015-12-19 15:22 ` Random832
2015-12-19 13:56 Noel Chiappa
2015-12-17 15:13 Mark Longridge
2015-12-19 2:27 ` Dave Horsfall
2015-12-19 8:34 ` Mark Longridge
2015-12-19 14:57 ` Random832
2015-12-19 16:18 ` John Cowan
2015-12-19 17:02 ` Craig Lennox
2015-12-19 20:05 ` Random832
2015-12-19 18:36 ` Marc Rochkind
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=20151219121220.EC3A718C0A3@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
/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).