Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Dec 2001 11:21:00 -0800 (PST)
From:      Matthew Dillon <dillon@apollo.backplane.com>
To:        Robert Watson <rwatson@FreeBSD.ORG>
Cc:        Peter Wemm <peter@wemm.org>, Terry Lambert <tlambert2@mindspring.com>, freebsd-arch@FreeBSD.ORG
Subject:   Re: Proposed auto-sizing patch to sysinstall (was Re: Using a larger block size on large filesystems) 
Message-ID:  <200112101921.fBAJL0I48202@apollo.backplane.com>
References:   <Pine.NEB.3.96L.1011210140216.4035N-100000@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
:> Seriously though, I like the concept but I wonder if it would be better
:> query the user..  ie: something like:  "(D)elete this partition or
:> (M)erge the space into parent?" 
:> 
:> Otherwise it becomes harder to delete /home, carve out some space for
:> something and recreate a new slightly smaller /home. 
:
:I have to admit I prefer this behavior: on the initial read through of
:Matt's description, I said to myself "But what if I just wanted to delete
:the partition, not merge it into another?"  With the D key defined as
:proposed, it would be a lot harder to do this.  I'm all for saving
:keystrokes, but not if it makes something useful like that substantially
:more complicated (or counter-intuitive).
:
:On a related note, is it currently possible to look at the partition list
:and see which ones are auto-sized and might behave that way?  Or
:alternatively, the output might read:
:
:  Partition      Mountpoint   Desired size   Actual size
:  /dev/ad0s1e    /home        50% (1.2GB)    1GB
:
:Something to give an indication of the behavior that will result from
:doing something to the adjacent partitions.

    It not that complicated.  The vast majority of people use 'A'uto
    on an empty partition table.  There wouldn't be any confusion.

    Another alternative would be to turn off the 'D'elete feature
    and have 'A'uto cycle through a number of different configurations.
    I don't see much of a difference, though I suppose we could put in
    some esoteric configurations like root-only (/) configs and such.
    It gets messy though because there are dozens of combinations... for
    example, root-only-with-swap, root-only-without-swap.  I think it is
    far easier to be given a base set and 'D'elete what you don't want,
    and to partition things up manually for anything we can't cover with
    that.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>

:Robert N M Watson             FreeBSD Core Team, TrustedBSD Project
:robert@fledge.watson.org      NAI Labs, Safeport Network Services


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200112101921.fBAJL0I48202>