Jemiolo, John wrote:
> for one, to access a drive on unix as a device you access it as rrz??c on
> unix (true64), the "c" label spans the entire drive.
That is correct but a partition type is "unused".
> If you install linux
> on it you would over-write data in partition a and b.
But Linux does not have any problems with this. This partition "c" is
not _required_ by Linux but it is not incompatible with it. Actually a
default installation by Hard Data, as we ship it, will have that
partition (and probably also "d" and "e" and maybe "f") just in case a
disk will be used in a machine which boots Tru64 as well. The only
problem is that this leaves you with a maximum seven of _data_
partitions instead of eight. If you really need that one partition more
then it is not hard to "steal" it back.
This hard limit of eight partitions may be the biggest trouble
for BSD type partitioning as disks are growing larger and larger.
An OS kind is totally irrelevant in that.
> Didn't say it could
> not be done, you will have to muck with the partitions and make sure the
> ones you use do not overlap.
Not much "mucking" is really involved. :-) The only thing is that
one has to use '-f' flag to 'swriteboot' to convince it that yes,
you know what you are doing, when writing a boot block over an unused
partition "c". This does not create any incompatible partition
> -----Original Message-----
> From: Michal Jaegermann [mailto:firstname.lastname@example.org]
> Jemiolo, John wrote:
> > True64 (Unix) and Linux, have incompatible partition requirements, although
> > both use bsd type labels.
> For example??? I really would like to know.
Axp-list mailing list
This archive was generated by hypermail version 2a22 on Fri Sep 1 05:03:57 2000 PDT
Send any problems or questions about this archive to email@example.com.