home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.minix
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!news.udel.edu!udel!louie!minix
- From: "Henrik Schultz, Production Systems Group" <HENRIKS@odin.uniras.dk>
- Subject: Re: system call addition
- Message-ID: <1992Dec21.121054.18914@udel.edu>
- Originator: mmdf@louie.udel.edu
- Sender: usenet@udel.edu (USENET News Service)
- Nntp-Posting-Host: louie.udel.edu
- Organization: University of Delaware
- Date: Mon, 21 Dec 1992 13:09:49 GMT
- Approved: usenet=relay@louie.udel.EDU
- Lines: 22
-
- >This may be a really naive question, but it seems (at least outwardly) that
- >a simple way of adding a new system call would be simply to assign the name
- >of the call (in caps) in <minix/callnr.h> (preferably against an unused slot,
- >so as not to have to alter the maxm. # of system calls allowed) and assigning a
- >corresponding function in the table.c (of fs, mm. etc., depending on what the
- >function of the call is and where I would like to add it) (against of course
- >the same number).
-
- In my eyes it seems the way to do it. I've just implemented an older
- set of routines that allow for a HALT, SHUTDOWN and REBOOT command for
- MINIX 1.5.10.
- These commands makes use of a REBOOT system call, implemented in mm in
- exactly the way that you've described. I just had to recompile mm and build
- a new image, and it worked first shot. This call took over an (unused) slot
- in the command table though (#51 which is for accounting which probably nobody
- ever uses :-)
-
- Henrik
-
- (henriks@odin.uniras.dk)
- --
- Mail System (MMDF)
-