aakash berde writes:
> I used
> pkgmk -o -d . -r / command
If all of your files are actually found on your system relative to /
(the system's root directory), then that command makes sense, and
should work. If that's not where the files exist, then you have to
*tell* pkgmk where to find them.
For example, suppose you have this:
/export/my-project/build/usr/bin/foo
/export/my-project/build/usr/bin/bar
Then you might have this in your prototype file:
f none usr/bin/foo 0755 root bin
f none usr/bin/bar 0755 root bin
And you'd invoke pkgmk like this:
pkgmk -o -d . -r /export/my-project/build
> Here files are installed at local folder.
> I want to copy the files from my local folder to /usr/bin.
That's not what pkgmk does. Pkgmk makes a package -- which you (or
someone else) can then install using pkgadd.
If all you want to do is add files to an existing directory as part of
the build process, see the install(1M) command instead.
(Note that /usr/bin belongs to the system and that you shouldn't be
placing anything there anyway. See the filesystem(5) man page for
details.)
> I do not want it that in request script asking user for base directory.
> How I can achieve that with any script or additional statements in
> present scripts?
I don't understand why what you're doing would involve any request
scripts or any other scripting.
> I want to run my application when system gets restart everytimes.
Then you need to create a file in one of the /etc/rc*.d/ directories
or (for S10 and above) create a service manifest.
> Can anyone send some idea on this. which script I need to create and
> what contenets script will contain.If possible please explain it with
> an example.can I use the script already in /etc/init.d/ for
> imq/pppd/aac?
Yes ... but you need to put it in /etc/rc*.d for it to do something.
See the documentation in those directories.
> I think I need to implement a script in /etc/init.d/ as well as in
> /etc/rc2.d/ , /etc/rc3.d/, etc/rcS.d/.
> But I do not exactly how that will work.
The 'init' process automatically runs those things at boot time.
Nothing, by the way, looks in /etc/init.d. That's mostly a
convenience directory and a way to allow administrators to run the
provided init scripts by hand without having to grovel through the
rc*.d directories.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
