Hi, Martin Mewes schrieb: > > Robert Schiele <[EMAIL PROTECTED]> wrote : >> On Tue, Sep 27, 2005 at 01:18:53PM +0200, Andreas Jaeger wrote: > >>> The problem with this is that it's difficult to come up with a >>> general solution for partitioning that works for everybody. The >>> questions are what to do in case of a new installation with >>> unpartitioned disks and what with partitioned ones? If somebody >>> comes up with a verbal algorithm on how to handle the general >>> problem, I'll get our partitioner team on board for discussion. >>> Does anybody have such general algorithm? >> I think the most general algorithm is: "This damn partitioner should >> always exactly propose what I expect him to propose in any arbitrary >> situation! Ah, and by the way it should double the disk space on >> every installation time." --- You will add this to the feature list >> for 10.1, won't you? ;-) > > As the proposer of this item I think YaST should indeed come up with "Do > the right thing (tm)" ;-). > > In first instance YaST should know about "Usage-Profiles". > The follwing examples are just what they are and subject to talk about. > These examples could apply on systems with already partitioned HDDs as > well.
Please don't take the following criticism personally, it's only my part of the discussion and I could be wrong. With already partitioned systems, it gets much more complicated and your scheme is no longer applicable. > a) Standard-Usage (2 HDDs unformatted) This is not standard at all. I would say that all cases with unformatted disks are something only an advanced user sees. Another problem is that you specify 2 HDDs as standard. By that definition, any laptop would be sub-standard. > c) Server-Usage (4 HDDs unformatted) > > /dev/hda > /dev/hda1 /boot 100M > /dev/hda2 swap (2 times RAM) Why does everybody want swap to be twice the RAM size? There is no reason for that. Besides that, having swap on a disk which is mostly inactive will help. So moving swap to the disk with /var and /tmp makes sense. > /dev/hda3 / (Rest of hda) > > /dev/hdb > /dev/hdb1 /home (complete disk space) Add /dev/hdc to /home by using RAID or using it for backups. > /dev/hdc > /dev/hdc1 /opt (50% of disk space) > /dev/hdc2 /usr (Rest of hdc) Disagree. Useless waste of space. And it will slow down booting. > > /dev/hdd > /dev/hdd1 /var (complete disk space) Now that is an idea which makes some sense. However, I would split that disk into /tmp and /var, each taking half of it. > /home should always be mounted on the HDD with the most > available disk space to my intention. Unless $PLACE_TO_DUMP_LARGE_FILES!=/home. I regularly compile packages from source and I have /storage for tarballs (and openSUSE .ISOs) and /sources for unpacked sources. That keeps fragmentation on both file systems low and /home is free of clutter and can be backed up easily. Regards, Carl-Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
