[comp.sys.hp] 7.0 Disk Partitioning

randy@aplcomm.jhuapl.edu (RANDALL SCHRICKEL (NCE) x7661) (11/05/90)

Still working on a very slow transition to 7.0. (Thanx to INGRES for that, not 
HP.) I heard a long time back that the partitioning scheme was to be much more
flexible in 7.0. Can't find my printed copy of the release notes; and the on-
line copy says "See the printed release notes". Could anyone offer some insight
into what new can be done in 7.0? I'd basically just like to change the part-
ition sizes to anything I'd like. I'd also like to know what's in the printed
notes that I'm missing. Thanx. 
--
	Randy Schrickel randy@aplcomm.jhuapl.edu
	Johns Hopkins Applied Physics Lab
	Laurel, MD 20723
	"Life goes on, long after the thrill of living has gone."

joseph@hpuplca.HP.COM ( Joseph Hohl ) (11/06/90)

> Still working on a very slow transition to 7.0. (Thanx to INGRES for that, not
> HP.) I heard a long time back that the partitioning scheme was to be much more
> flexible in 7.0. Can't find my printed copy of the release notes; and the on-
> line copy says "See the printed release notes". Can anyone offer some insight
> into what new can be done in 7.0? I'd basically just like to change the part-
> ition sizes to anything I'd like. I'd also like to know what's in the printed
> notes that I'm missing. Thanx. 
> --
> 	Randy Schrickel randy@aplcomm.jhuapl.edu
> 	Johns Hopkins Applied Physics Lab
> 	Laurel, MD 20723
> 	"Life goes on, long after the thrill of living has gone."
> ----------

The 7.0 release provided additional partitions over release 3.1. Sections
12 through 15 are the additional partitions. The disktab file shows the 
partition layout in it's comments as follows:

#
# This file contains the disktab entries for the current sectioning
# scheme
#
# Note that sector sizes are in terms of DEV_BSIZE units which is
# defined to be 1024 bytes.
#
#
#	Section layout:
#
#	-----------------------------------------
#	6                        ^         ^     
#	----------------------   |   ---   |     
#	0            15          | 7  ^    |     
#	---------                |    |    |     
#	         -------------   |    |    |
#	1            14    ^     v    |    |     
#	------------------ | -------- |    | 2   
#	10                 |     ^    |    |     
#	------------------ |     |    |    |     
#	3             ^    | 13  |    |    |     
#	-----------   |    |     | 11 | 12 |     
#	4      ^      | 8  |     |    |    |     
#	------ | 9    |    |     |    |    |     
#	5      v      v    v     v    v    v     
#	-----------------------------------------
#
#
# The default layouts for file systems is as follows: 
#
# Common for all devices: 
#
# 	Section 6	boot section
# 	Section 0 	root file system
# 	Section 1	swap section
# 	Section 3	/tmp
#
# For most devices (no Section 10): 
# 	Section 4	/usr
# 	Section 5	/mnt
#
# For larger devices (have Section 10):
# 	Section 4	/usr
# 	Section 5	/extra
# 	Section 10 	/mnt
#
# For very small devices (no Section 4 or 10):
# 	Section 5	/usr
#
# If a user wants to recreates /tmp section, we recommend it block size 8k and
# fragment size 8k also for optimum performance.  For all other sections
# We recommend the default block size of 8k and fragment size of 1k for a
# good tradeoff of space saving and performance.

jsadler@misty.boeing.com (Jim Sadler) (11/06/90)

>The 7.0 release provided additional partitions over release 3.1. Sections
>12 through 15 are the additional partitions. The disktab file shows the 
>partition layout in it's comments as follows:

Adding 4 partitions sizes to the stupid idiotic ^%T^#^$@#@$!!, choices
that HP provides, is NOT!! what I call flexible.

Everytime that I install a new system, HP's scheme of partitioning drives
me NUTS!!  It NEVER fits the application for which the machine was bought.
It cause security problems because of HP refusual to support a modern
NFS (there is this ability of NFS to export directories(heard of it HP?))

I've complained about this before over a year (or was it 2 years?) ago.
If Boeing manufactured airliners like HP does software we would be
flying canvas covered aircraft.

In case you can't tell I installed another 8XX machine and its
partitions don't make sense either.

jim sadler
206-234-9009	email	uunet!bcstec!jsadler | jsadler@misty.boeing.com