[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:	DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:	Welcome to the Digital UNIX Conference
Moderator:	SMURF::DENHAM

Created:	Thu Mar 16 1995
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	10068
Total number of notes:	35879

9298.0. "What are /etc/sysconfigtab.xx ?" by BIS10::BRUSCHE () Wed Mar 26 1997 10:33


	On a V4.x system /etc contains (besides the regular sysconfigtab)
	a series of sysconfigtab files with extensions .2, .3 .4 ,..upto .33

	What is the purpose of those sysconfigtab.nn files, apparently
	installed by the OSFHWBASE4nn subset ??

	What are the consequences of deleting them ( eg by someone thinking
	they are older versions of sysconfigtab) ??


	In any case they are not documented in the sysconfig or sysconfigtab
	man pages.

	JB.

T.R Title User Personal
Name Date Lines

9298.1 osfboot, boot-link and sysconfigtab.* NETRIX::"[email protected]" Karl Ebner Wed Mar 26 1997 12:37 29

T.R	Title	User	Personal Name	Date	Lines
9298.1	osfboot, boot-link and sysconfigtab.*	NETRIX::"[email protected]"	Karl Ebner	`Wed Mar 26 1997 12:37`	29
	JB, In 4.0 osfboot was modifed to support the dynamic linking of modules to create a vmunix kernel. This technology is refered to as boot-link (ing) and is documented in the Device Driver Tutorial for third party device driver developers. This technology was shipped and supported in 4.0 and is intended to allow at installation time the integration of files from a base UNIX CDROM and one or more products kits to create a boot kernel. osfboot looks at the RPB to determine the system type (ie 1,2...31 an integer). It then looks into /etc to find the sysconfigtab.system_type to determine the core files that are required to link/build a kernel for this hardware platform. These files are linked along with those supplied by the product kits to make this initial kernel at installation boot time. There is an excellent description of this process in the Guide To Writing Product Kits. Deleting these files would potentially prevent a kit developer from from being able to test a new Product Kit using osfboot. Thanks, Karl [Posted by WWW Notes gateway]

JB,

In 4.0 osfboot was modifed to support the dynamic linking
of modules to create a vmunix kernel. This technology is
refered to as boot-link (ing) and is documented in the
Device Driver Tutorial for third party device driver 
developers.

This technology was shipped and supported in 4.0 and
is intended to allow at installation time the integration
of files from a base UNIX CDROM and one or more products
kits to create a boot kernel. osfboot looks at the RPB 
to determine the system type (ie 1,2...31 an integer).
It then looks into /etc to find the sysconfigtab.system_type
to determine the core files that are required to link/build
a kernel for this hardware platform. These files are 
linked along with those supplied by the product kits to 
make this initial kernel at installation boot time. There
is an excellent description of this process in the
Guide To Writing Product Kits.

Deleting these files would potentially prevent a kit
developer  from from being able to test a new Product 
Kit using osfboot.

Thanks,
Karl

[Posted by WWW Notes gateway]