Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!nirvo!kdg From: kdg@nirvo.uucp (Kurt Gollhardt) Newsgroups: comp.unix.i386 Subject: Re: inittab action entries under ISC 386/ix Summary: Create inittab entries via /etc/conf/init.d Keywords: bootwait sysinit rebooting after rebuild Message-ID: <25341456.2145@nirvo.uucp> Date: 12 Oct 89 04:34:28 GMT References: <965@dialogic.UUCP> <1989Oct5.010113.1530@esegue.segue.boston.ma.us> Reply-To: kdg@nirvo.UUCP (Kurt Gollhardt) Organization: Nirvonics Inc., Plainfield, NJ Lines: 48 >In article <965@dialogic.UUCP> alan@dialogic.UUCP (Alan Murphy) writes: >>Hi, >> I am developing device drivers under ISC 386/ix 3.2 and I >>need to be able to create an inittab entry at build time. ... >>(basically the operation involves downloading code to a controller at >>power up time). ... You *can* create rc2.d entries, as suggested by others, but if you *do* want an inittab entry instead, the way to do it is to create a file named /etc/init.d/foo, where foo is the name of your driver module. The system constructs /etc/inittab by concatenating /etc/conf/cf.d/init.base with /etc/init.d/*. Actually, you're probably building this as an installable package (with Driver.o, Sdevice, etc. files for your driver). In this case, you would just make a file named "Init" at the top level of your tree, and this will be installed as /etc/conf/init.d/foo. Note: the lines in /etc/conf/init.d/foo have a slightly different format than /etc/inittab. Whereas inittab is: id:rstate:action:process /etc/conf/init.d/foo is: action:process or rstate:action:process The 'id' is automatically generated, and the default rstate is '2'. Also, if you want an rc script instead of an inittab line, the "correct" way to do this is by putting in a file named "Rc", which gets installed as /etc/idrc.d/foo, and is automatically invoked upon entering init level 2. (Note: when creating this module, the file permissions must allow execution by root.) The counterpart to this for system shutdown is the "Shutdown" file - installed automatically as /etc/idsd.d/foo. [This information is detailed in the UNIX System V/386 Release 3.2 Integrated Software Development Guide and its ISC equivalent.] -- Kurt Gollhardt \ Nirvonics, Inc. -- Plainfield, NJ Kurt.Gollhardt@nirvo.uucp /\ Software Design and Consulting ...!rutgers!nirvo!Kurt.Gollhardt / \ "It's all about people; not you and me or him and her, but *us*."