On Sat, 3 Jan 2004 03:47, Eric F Crist wrote:
> On Thursday 01 January 2004 11:46 pm, Malcolm Kay wrote:
[not Malcolm Kay]
> > > > $ df -h
> > > > Filesystem Size Used Avail Capacity Mounted on
> > > > /dev/ad0s3a 1008M 92M 835M 10% /
> > > > /dev/ad0s2 1020M 19M 1001M 2% /dos
> > > > /dev/ad0s3g 4.8G 69M 4.3G 2% /home
> > > > /dev/ad0s3e 3.9G 3.9G -260.5M 107% /usr
> > > > /dev/ad0s3f 1008M 27M 900M 3% /var
> > > > /dev/ad0s1 24G 22G 2.9G 88% /nt
> > > > procfs 4.0K 4.0K 0B 100% /proc
> > > > /dev/da0s1 61M 61M 632K 99% /umass
[not Malcolm Kay]
> > > The two partitions appear to be adjacent. If they are, Partition Magic
> > > (or similar) could merge those two partitions non-destructively, and
> > > your problem would be solved.
[The next is Malcolm Kay]
> > This sounds like a disaster --- partition magic works with MS
> > partitions or in FBSD terms slices -- to the best I my knowledge it does
> > not know about BSD style partitions.
[The next is Eric F Crist]
> Partition Magic can recognize a type 165 (freebsd) partition, but it does
> not support merging/resizing of these. It does support the linux partition
> scheme, however.
Please read my words carefully:
Yes, Partition Magic recognises partitions in the MS partitioning scheme,
known as slices in FreeBSD, including those labeled as BSD (type 165).
These have device names (under FBSD) of the form ad0s1, ad0s2, ads0s3 etc.
However, I do not believe it knows anything of BSD partitions which
subdivide such a slice. These have device name of the form ad0s3a, ad0s3b,
Native Linux uses only slices (MS style partitioning). It knows something of
BSD partitioning in order to mount (foreign) BSD file systems.
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"