Hi All: Found that this issue was not resolved yet for fc7. Personally I would leave the default as it is (100MB->/boot,XXXMB->swap and the resto for /) but the bug discussion does have some details that should be avoided (The issue with the newbie realizing that it would be better to separate the home and OS way after he has finished the installation.) To suggest a solution I would do something like (100MB->boot--- XXXMB->swap---10GB->/ --- the rest for /home :) but thats just me.... I tested it in kickstart and gui installs, everything seems to be fine. So I think its sensible to close the bugs. The diff:
diff -ubB anaconda-11.2.0.40/installclass.py anaconda-11.2.0.40-JG/installclass.py --- anaconda-11.2.0.40/installclass.py 2007-03-08 23:03:32.000000000 +0100 +++ anaconda-11.2.0.40-JG/installclass.py 2007-03-28 17:16:53.000000000 +0200 @@ -421,7 +421,7 @@
def setDefaultPartitioning(self, partitions, clear = CLEARPART_TYPE_LINUX, doClear = 1, useLVM = True): - autorequests = [ ("/", None, 1024, None, 1, 1, 1) ] + autorequests = [ ("/", None, 1024, 10240, 1, 1, 1) ]
bootreq = getAutopartitionBoot() if bootreq: @@ -429,6 +429,7 @@
(minswap, maxswap) = iutil.swapSuggestion() autorequests.append((None, "swap", minswap, maxswap, 1, 1, 1)) + autorequests.append(("/home", None, 1024, None,1,1,1 ))
if doClear: partitions.autoClearPartType = clear
On Wed, 2007-03-28 at 17:26 +0200, Joel Andres Granados wrote:
Found that this issue was not resolved yet for fc7. Personally I would leave the default as it is (100MB->/boot,XXXMB->swap and the resto for /) but the bug discussion does have some details that should be avoided (The issue with the newbie realizing that it would be better to separate the home and OS way after he has finished the installation.) To suggest a solution I would do something like (100MB->boot--- XXXMB->swap---10GB->/ --- the rest for /home :) but thats just me.... I tested it in kickstart and gui installs, everything seems to be fine.
The problem is "is 10 gigs enough?" And on multilib platforms, it only barely is today. Which means that as someone upgrades and wants to add more software, it's not going to be anymore.
If we had online shrinking of ext3 filesystems, it'd be a little easier as the theoretical future tool for disk handling could do a resize when you need it. But right now, it just leads to user pain.
Jeremy
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jeremy Katz wrote:
On Wed, 2007-03-28 at 17:26 +0200, Joel Andres Granados wrote:
Found that this issue was not resolved yet for fc7. Personally I would leave the default as it is (100MB->/boot,XXXMB->swap and the resto for /) but the bug discussion does have some details that should be avoided (The issue with the newbie realizing that it would be better to separate the home and OS way after he has finished the installation.) To suggest a solution I would do something like (100MB->boot--- XXXMB->swap---10GB->/ --- the rest for /home :) but thats just me.... I tested it in kickstart and gui installs, everything seems to be fine.
The problem is "is 10 gigs enough?" And on multilib platforms, it only barely is today. Which means that as someone upgrades and wants to add more software, it's not going to be anymore.
FYI, I installed all of FC 5 CD software and all the stuff in extras just to see what was there. 21G was required.
Regards, Greg
Jeremy Katz wrote:
On Wed, 2007-03-28 at 17:26 +0200, Joel Andres Granados wrote:
Found that this issue was not resolved yet for fc7. Personally I would leave the default as it is (100MB->/boot,XXXMB->swap and the resto for /) but the bug discussion does have some details that should be avoided (The issue with the newbie realizing that it would be better to separate the home and OS way after he has finished the installation.) To suggest a solution I would do something like (100MB->boot--- XXXMB->swap---10GB->/ --- the rest for /home :) but thats just me.... I tested it in kickstart and gui installs, everything seems to be fine.
The problem is "is 10 gigs enough?" And on multilib platforms, it only
IMO it really depends what you are doing with the box. I have an old laptop that is more than happy with 10G of /. of course more than once I have reached the limit but nothing that an "apt-get clean" cant solve (I have also had to uninstall some unused packages, but thats another issue).
barely is today. Which means that as someone upgrades and wants to add more software, it's not going to be anymore.
If we had online shrinking of ext3 filesystems, it'd be a little easier as the theoretical future tool for disk handling could do a resize when you need it. But right now, it just leads to user pain.
I agree with you.
Jeremy
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
I don't see any problem in adding another 10Gigs to the ceiling of the / partition. With the size of current harddrives I don't think thats an issue. So ending up with (100MB->boot---XXXMB->swap---20G(max)-> /---The rest for /home). I use 20G based on the reply that stated that fc5 ate up 21G. I really doubt that the beginner will install ALL the packages. The 20G / is not for installing all the packages anyway, but to allow the beginner to add some other nifty applications once he gets use to the operating system (Assuming that the user would choose the default package list is also reasonable given that he has chosen the default partition scheme). Its also useful to keep the home partition (user's stuff) from disappearing whenever the user wants to reinstall or something.
IMHO the separation of / and /home with 20G for / and the rest for /home accomplishes the two objective that it is meant for: 1. Provide the possibility of growth in / 2. separate user info from os stuff so that it is "protected" in reinstall, upgrade and other situations where the / needs to change.
The diff is attached. regards
--- installclass.py-11.2.0.40 2007-03-29 13:17:57.000000000 +0200 +++ installclass.py 2007-03-29 13:18:56.000000000 +0200 @@ -421,7 +421,7 @@
def setDefaultPartitioning(self, partitions, clear = CLEARPART_TYPE_LINUX, doClear = 1, useLVM = True): - autorequests = [ ("/", None, 1024, None, 1, 1, 1) ] + autorequests = [ ("/", None, 1024, 20240, 1, 1, 1) ]
bootreq = getAutopartitionBoot() if bootreq: @@ -429,6 +429,7 @@
(minswap, maxswap) = iutil.swapSuggestion() autorequests.append((None, "swap", minswap, maxswap, 1, 1, 1)) + autorequests.append(("/home", None, 1024, None,1,1,1 ))
if doClear: partitions.autoClearPartType = clear
anaconda-devel@lists.fedoraproject.org
-
Greg Morgan -
Jeremy Katz -
Joel Andres Granados