Hello SUN-managers,
last week I asked:
-> Here my problem:
-> I am trying to strip down the standard distributed SOLARIS Version, because
-> we do not need the hole functionality of the core system and our persistent
-> memory (harddisk or something else) have an limited size. In the SOLARIS
-> documentation I can find only descriptions on the package level. I am looking
-> for an description of the filesystem, which describes the functionality
-> for any directory (better for any file) and the dependencies between files.
-> The dependencies I need to find out whether, can I delete the file (because I
-> do not need the functionality) or not (because this file is used by another file
-> or functionality /that I need/ too).
Thanks a lot to everybody who responses:
feldt@phyast.nhn.uoknor.edu
jimc%jtsv16@jts.com
ericb@telecnnct.com
cal@soac.bellcore.com
But unfortunately I do not get any reply, which covers the hole problem.
The most helpful reply was:
I haven't seen this explicitly written anywhere. That stinks. There also
does not appear to be a bundled utility to provide a pretty picture of
the info you want. Generally, packages in the same family have dependencies
(e.g. SUNWleoow & SUNWleou depend on SUNWleo) but they don't usually extend
to other packages per se. That is, you could install openwindows without
installing any graphics drivers.....perfectly legitimate for servers but
pretty useless for end users.
What you can do is a full install on a system (perhaps temporarily). You can
find out ALL the package names by simply typing pkginfo -l. Then you can
examine the pkgmap file located in each /var/sadm/pkg/<pkg_dir>. This file
tells you all path info as :
->pkgmap(4) File Formats pkgmap(4)
->
->NAME
-> pkgmap - package contents description file
->
->DESCRIPTION
-> pkgmap is an ASCII file that provides a complete listing of
-> the package contents. It is automatically generated by
-> pkgmk(1) using the information in the prototype file.
->
-> Each entry in pkgmap describes a single ``deliverable object
-> file.'' A deliverable object file includes shell scripts,
-> executable objects, data files, directories, etc. The entry
-> consists of several fields of information, each field
-> separated by a space. The fields are described below and
->
->
Example
--------
seawasp# cd /var/sadm/pkg/SUNWowdv
seawasp# cat pkgmap
: 1 468
1 i copyright 2576 32618 733083069
1 i depend 842 3882 733083070
1 d none kernel 0755 root sys
1 d none kernel/drv 0755 root sys
1 i pkginfo 356 28972 733254753
1 d none usr 0775 root sys
1 d none usr/kernel 0755 root sys
1 d none usr/kernel/drv 0755 root sys
1 f none usr/kernel/drv/win 0755 root sys 135400 20085 733209435
1 f none usr/kernel/drv/win.conf 0644 root sys 120 8844 733209435
1 f none usr/kernel/drv/winlock 0755 root sys 12808 6061 733209454
1 f none usr/kernel/drv/winlock.conf 0644 root sys 128 9694 733209455
seawasp#
Another reply was about a company which solved the same problem:
VenturCom takes standard SVR4.2 and adds a fully-preemtive, real-time kernel,
and a fast contiguous file system. They also have a package which is and
Embedded SVR4.2 system. They have customers that run it out of PROM's, so
it's small and compact, yet still fully SVR4.2 base complient.
==== Joerg Bruchertseifer
==== jb@uebemc.siemens.de
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:11 CDT