Written by frandavid100 the 22 Mar 08 at 10:55.
Category: Installation.
Related project:
Nothing/Others.
Status: New
Rationale
A separate partition for /home has been proposed for a long time in the forums. It implies some risks, though, so based on disk size Ubiquity should estimate the amount of space that should be left for / or whether a separate partition should be made at all. Then...
-The first time an user installs Ubuntu, he is given the option to set a separate /home. This option is selected by default, with a size for each partition based on a sane guess:
-Of course, he can just choose not to set a separate /home. This option will be selected by default if the results of the system test suggest that's the best thing to do.
-Manual install is also possible. Selecting it greys out everything related to separate /home, since it's implied that the user doesn't want to be guided.
-If the user set a separate /home, the next time he installs Ubuntu a new option appears and is selected by default, prompting to use the existing /home partition. All other options are still available, though.
I have always used a separate /home as well. Keeping /home after reinstallations is one major reason which has been mitigated by ubiquity preserving /home now (I didn't test that yet, though).
Either way ubiquity (the Live CD installer) should point this out clearly.
The other reason is that I want to use it from multiple Linux installations, but that's mostly a geek use case.
I have no idea what size / and /home should have by default,
I always use 6 GB for / and the rest for /home, but if someone wants to use huge databases, that'll break.
Thus I think we should stick to our current partitioning and rather improve the UI for keeping /home. There is always manual partitioning for people who actually care.
--
Preserving the contents of /home during installation has been implemented in the desktop CD installer (ubiquity) since Ubuntu 8.04. This is achieved by deleting the system files and directories that are about to be replaced and then continuing with a normal installation, leaving /home, /opt and others untouched. We decided against creating a separate /home partition as there is no correct answer for a /home partition, / partition size split for all users, and we felt the likelihood that whatever guess we came up with would be a major regression for a large subset of our users was quite high.
In addition to this, partitioning is a complex subject, one that is quite difficult for many non-technical users to understand. This difficulty is further complicated by a lack of safe, online partition resizing in Linux.
Please note that the functionality to preserve the contents of /home exists in Ubuntu, just not via the arguably dangerous implementation suggested here.
This needs to get done! But it's not so much an ubuntu problem; it's part of the debian way of installation, that we don't get a /home partition.
You CAN work around it, when you do the setup of your system, just be shure to leave a huge space on the disk as a logic partition (unused - just in case).
say hd0 is your ubuntu, hd1 is swap (special weapons and partitions) and hd2 to hdn can become whatever you want them to be.
AFTER the setup, you can divide and activate this partition and make it /home or install other unices (for testing etc). This is a very, very bad way of doing things. It is also very "proprietary" of debian; neither RedHat nor SuSE can work and rework a debian made partition system.
But the worst sucker is: you need to know a hell of a lot about GNU/Linux and debian BEFORE coming up with the right way to do it - and this means that in general you already have a system set up the wrong way, when you learn about how to do it right.
I would LOVE to get it solved, but I don't see how! We're debian desciples :o)
may be a drop down list to select one of the existing home folders (if user had a mandriva home and a gutsy home ad he dont want to merge them, he should ave more than one, so this option could be ambiguous)..
I think that user should do it manually, then. This feature intends to make life a bit easier for newcomers, therefore keeping it simple is essential if we want it to be of any use.
I'm sure the kind of user you mention knows how to create and mount a /home partition himself.
I see no reason at all to create a seperate home partition, it only makes things more complicated. The only thing that would be useful is the installer detecting existing home directories and/or partitions and preserving them, but there is no reason that home directory should be on a separate partition.
As the screenshots say, it prevents personal data and preferences from being lost if the system has to be installed.
Preserving /home directories on reinstall would be another way to do the same thing alright, but A) we don't have that, and B) having a separate partition gives me the psychological assurance that my data are safe even if the installer goes bogus.
There is a number of different reasons to have, not only a separate /home, but other filesystems.
1) Less risk of an unbootable system due to filesystem corruption. If everything is on one filesystem, you run that risk. Keep system files (which do not change often) on a separate filesystem than user data (which does change often) limits your risk. Also, it's a lot easier to run fsck on a system that can at least get to a shell, then have to boot from some liveCD and try to do it. Remember the saying, Don't put all your eggs in one basket.
2) Better Performance. Again, separating out stable data with (ever changing data) will cut down on non-contiguous storage. If you have a large disk where everything is in one filesystem, the data blocks are written throughout the entire disk. Since /boot / and /usr do not get many writes, the data will be written contiguous. However, /var constantly is changing removing adding files. This fs is best left on its own in a small segment of the disk so that the read/write head is not skipping all over the disk.
3) You can use different filesystem types for different purposes. ext3 is good for stability, reiserfs is good because you can extend or grow the fs without umounting it. You might use xfs on very large filesystems. Or you might want to mount some read-only or encrypted.
The issue of how much space to use in each filesystem was solved with LVM. It kills me to see systems using LVM, with everything in one LV that takes up all of the space in the volume group. Logical volumes should only be as big as needed at the time (with a little growing room). Then if you run out of space, you just extend the logical volume and filesystem to meet your needs. If you run out of disk space, you can add more disks and extend the filesystems some more. You use the disk space efficiently and the back-end makes sure the data is written efficiently to the disk blocks.
Wonderful idea, but there needs to be one key fix for this to be user-friendly. You see, when moving files between partitions, either nautilus or gvfs or ubuntu copies the files instead of moving them. This can be quite a surprise for new users who are used to a unified file system. By changing this behavior wherever it is implemented we can ensure a user-friendly experience so central to the core values of ubuntu linux.
Offering to create a separate home partition is a good idea, I support.
However, the system should select a sensible default and the user should not be asked about what to do unless he really wants to change the option. New Ubuntu users probably will be frightened if they are asked something like "Do you want to create a separate /home partition or store user data in root partition?"
Well, the system DOES (hypothetically) select a sensible default and suggest it to the user. As the related bug reads:
"The recommended options, based on HD size, would be:
1. The default should be to create a separate /home
2A. For the default option, if the hard drive is bigger than 20 GB, and it's a Ubuntu-only installation, 10 GB should go to / and the rest should go to /home
2B. If the hard drive is between 10 GB and 20 GB, and it's a Ubuntu-only installation, 5 GB should go to / and the rest to /home
2C. If the hard drive is less than 10 GB, there should not be a separate /home partition
3A. If the hard drive is bigger than 40 GB and a dual-boot, 10 GB should go to / and the rest to /home
3B. If the hard drive is between 30 GB and 40 GB and a dual-boot, 5 GB should go to / and the rest to /home
3C. If the hard drive is less than 30 GB and a dual-boot, there should be no separate /home partition".
The results are then displayed as recommended options and selected by default, so no user has to make a decision he's not sure about: he KNOWS that a specific option is recommended (the dialogue tells him so), and can go by it unless he really knows what he's doing and wants to decide otherwise. No reason to be scared here.
On the other hand there's no way to know if the user really wants to change the option if you don't ask him first, is there?
Also: Broomfighter, you got me a little lost there. How is moving files between partitions, or copying them instead, related to the topic? I'm afraid I'm not following you.
Wouldn't it just make more sense for /home to be installed into /usr/home instead, then mount /usr as a seperate partition? Then you wouldn't have to worry about your root partition blowing up with too many applications and the whole "how much space to leave for the system" question is negligable (5GB out to be enough for anyone, hehe;)
Then, when you need to reinstall your system (and preserve home/) then you can just delete the files under /usr/* except for home and format the system partition, and all is good.
Am I missing something here? It would seem to me that the whole reason Ubuntu installs all on one partition is because it is too complicated for the user to come up ahead of time what size he wants for each partition. If you make the /usr partition the extra one, and install home into it, that is probably 99% of any "additional" storage that would not have been predicted ahead of time.
"then you can just delete the files under /usr/* except for home"
I see your point, but wouldn't that defeat the purpose of the whole thing? I take it you mean the *user* has to delete everything, save /home? Or the installer does?
As for 5 GB being enough, I've been using a 5 GB root partition for a couple years, having installed everything I would possibly ever need and still have 1.5 GB free. However the installer would recommend leaving 10 GB just to be on the safe side. And well, default sizes can be changed anyway if the devs decide they're not the best. I don't really have a strong position towards *these* figures.
A separate home is a false sense of security. It does not decrease the chances of your disk failing. It does not decrease the chance of deleting your data. It does not improve performance.
It increases the installation complexity and introduces the possibility of the user running out of space somewhere.
The current default (all on one partition) is an elegant solution.
There is no benefit to a separate home. It's easier and safer to just do a proper backup.
"A separate home is a false sense of security. It does not decrease the chances of your disk failing. It does not decrease the chance of deleting your data. It does not improve performance".
It never intended to do any of those. It does keep your personal data and preferences if you reinstall the system. That's basically the point.
"It increases the installation complexity"
That's precisely what this idea is trying to solve. Did you even take a look at the mockups?
"It's easier and safer to just do a proper backup".
I agree with the "safer" part, but as I said, this idea's purpose is not to safeguard the user's data against hardware failure or own incompetence, so there's no point to that comparison. As for the "easier" part, please do take a look at the screenshots before saying that kind of things.
1. Your personal preferences cannot reliably be shared between different versions of applications. For example, you cannot guarantee that your dotfiles will apply to earlier versions of an application if you decide to revert to an older version. Not to mention the problems with sharing a home partition between two or more operating systems.
2. I did look at the mockups. It does increase complexity. The end-user should not even have to know the difference between system files and personal files.
Installing the OS is an incredibly large hurdle for non-geeks. The best thing we can do to help overcome this is make the installation as painless as possible. I think the current installer needs seven mouse clicks. Any addition decision/mouse clicks makes the process that much more of a challenge.
3. Easier means less complex. The user should not have to conceptualize how their disk is partitioned. There already is a separation between system and user files in any default installation. You don't need to partition to achieve this.
Maybe the installer could take a look at the target disk to see if there is already an intact filesystem there with a home folder and rename that to "home-backup"? Again, in that case, the installation should not be made more complicated by that.
1. True, but I cannot picture many newcomers reverting from a functional ubuntu release to an older one. Most of them will periodically install *newer* releases, though, containing newer application versions which, in most cases, will make use of their old preferences.
As for shared partitions, that is completely out of this idea's scope. This is meant for users who do not know what a partition is. The kind of people who most surely won't install several operating systems on the same machine, and with a shared /home partition.
Really, I can't see how your argumentation applies to this.
2. Please, look at the screens again. The user does not need to know the difference between personal and system files. The installer tells him what will happen in plain English and chooses good default options for him. He does not really have to read or understand anything, or make any -not one- additional mouse clicks. The point of it all is that he *can* change these settings, but does not have to. Separate /home goodness comes to him without doing a thing.
3. Finding your old preferences there when you reinstall is easier -as in less complex- than having to set them all again. It is also less complex than installing a backup tool, backing up your data and placing it back after install. It is also less complex than tracking down a "home-backup" folder that you might have or have not access to, or know that it exists, and for some reason is eating up your disk space, and copying everything -including hidden files- back to your /home.
Starting over again from scratch is probably the easiest, but most users would probably agree with keeping their settings and other stuff. The question here is, should they be able to? And how easy do we want to make it on them?
"I cannot picture many newcomers reverting from a functional ubuntu release to an older one."
It happens all the time. How many times have users (male and female) asked is there was a rollback feature? If your solution doesn't plan for that, it isn't ready for prime-time. And since you would have to get all of upstream to suddenly make their dotfiles backwards-compatible, you are in for a huge task.
"Most of them will periodically install *newer* releases, though, containing newer application versions which, in most cases, will make use of their old preferences. "
That's that a dist-upgrade is for. Not to mention that half of the time a user borks their system, the solution is to jettison the messed-up configurations in their home folder anyway.
"Please, look at the screens again."
I have. The most complicated part of the installer looks even more complicated.
"Starting over again from scratch is probably the easiest, but most users would probably agree with keeping their settings and other stuff. The question here is, should they be able to? And how easy do we want to make it on them?"
Starting from scratch doesn't get any easier than dragging and dropping the files you want to keep onto a backup drive and copying them back once you reinstall.
This is an excellent idea. This would help out the general public (non-code writers, like me) who want to move to Ubunutu (or other *nix) from a version they're on but are afraid that they might loose their stuff if they did. +1000
Why in the world would you create a separate partition for the home directory? This would require you to predict the size in advance and cause you to run out of disk space sooner.
It's always been a safe and sane practice under "redmond" legacy OSes to make a separate partition for user's data. Today it still minimizes data loss possibility in case of system fatality and consequent reinstallation, even though Win32 platform is too mature for that to happen as often as in its glorious past. Sad but true, Ubuntu hasn't reach even this level of stability yet. Linux is still under heavy development as a desktop platform. Take hardware accelerated rendering situation, for example: proprietary drivers, problems with laptop BIOSes ACPI support, developing Xorg. More of that, XGL and AIGLX are both "too alpha" to work flawless with compiz (the only way to match redmond's eye candy for today). XEGL (the first logically proper and clean solution) is only a sweet dream, while slow graphics and instability is a harsh reality. Considering this example, and overall rapid progress of desktop Linux solutions, it's no wonder that we *have to reinstall* Ubuntu from time to time, but not upgrade. Thus we loose our data from time to time. Separate /home partition policy would be a fine practice, especially in conjunction with proper system-wide settings backup/export/import software.
I found this option by accident whilst playing around with the network installer version of Debian. When it came to the disk partitioner it offered to create separate partition for / and /home.
I completed the installation but then went back to Ubuntu (it was on a Tosh Portege I was re-installing via PXE for testing so I wasn't worried about blowing away the Debian install). On re-install I just kept the existing partition scheme and re-formatted each and selected the relevant mount points.
I think this could be an excellent idea but it would need to be explained very clearly to the user during installation as it could easily scare off people coming from a windows background who don't understand how the Linux file system works!
Using a separate /home partition is a good practice (as others have indicated). This provides an easy way for new users to start using that good practice.
According to a recent mailing list post(1) this has been implemented: ubiquity now detects and preserves existing home directories while overwriting the rest of the system. There is no need to create a seperate partition for it.
This discussion fails to recognize the #1 reason to install to a separate /home partition: security. The partition can be set noexec so that malware won't be able to reside in the user area -- the only place it has ready access to.
Mounting /home and /tmp noexec are basic security procedures that Ubuntu isn't following ... and it should be. Some day, the Ubuntu community will be large enough to attract malware. Let's get ready for that time before it happens, eh?
Ubuwu: I have tried that twice, but both times it resulted in my /home data being destroyed. I hope some developer can shed some light on how exactly it works.
Daengbo: Would that mean that you couldn't run any executable files inside your /home? That would bring some usability problems wouldn't it?
Yes, it should be done since a separate home partition is the most convenient layout in most of the cases.
Also this would help to offer a new user a case sensitive (ext3) or case insensitive (jfs with -O option) partition. It seems that quite a lot new users encounter file system case sensitivity problem and the solution is very obscure and may come too late when the user has to backup and re-partition his system.
Auzy, first it is suggested as an option and second, you may have say 6Gb partition for / and the rest for /home and in an unlikely case you run out of / space you can always bind say /usr/local to a directory on your /home partition.
Wow... bind /usr/local to /home... doesn't that go against purpose of the arguments for either side?
Personally I have run quite tight on data many times... and if I know there is 5GB sitting there unused I'm annoyed.
I always found it curious how people would increase the complexity of their system management by partitioning into 4 or more partitions (in DOS/Windows)
And while I can appreciate the 'simplicity or re-install' argument, I don't really see why deleting all but the /usr directory is more difficult to implement.
And with journaling file systems the corruption factor seems considerably less.
In response to the developer comment pointing out that figuring out a default size would be hard, there could simply be a screen asking the user to move a slider to determine what percentage of their harddrive they wanted to use for data.
In lieu of making a separate /home partition the default behavior, why not at least offer the option (using whatever recommendations deemed appropriate)?
I can understand why the decision might be made not to make a separate /home partition the default behavior; however, I cannot understand why the *option* cannot be given. This idea is obviously one of the more popular ones on Brainstorm.
Giving default recommendations seems to be a viable solution. I think the 5GB/10GB root partition defaults, based upon overall HDD size, are perfect. Those who want a finer degree of control still have the option of manual partition configuration.
Oh, and those who are arguing that having separate root and home partitions presents more risk of running out of disk space: how many HDDs today are smaller than 60GB (or perhaps 40GB)? Anything smaller is either on a baseline laptop or else a ULCPC - neither of which is designed to be used for disk-space intensive activities (like media storage).
Desktop HDDs are measured in the hundreds of GBs - more than ample space to provide for separate root/home partitions without sacrificing meaningful disk space.
(And I am writing this on a mostly baseline dell*buntu Inspiron with a 60GB HDD.)
It seems to me that the developers are taking the easy way out on idea #5390. This idea has almost 3200 votes and the comment made by the developer was..."I don't know what the user wants..so we'll do nothing"..here is the actual quote:
"I have no idea what size / and /home should have by default,
I always use 6 GB for / and the rest for /home, but if someone wants to use huge databases, that'll break.
Thus I think we should stick to our current partitioning and rather improve the UI for keeping /home. There is always manual partitioning for people who actually care."
If the user selects "I care" ...then ask!!
Without changing the defaults on the installer, an option could be added which allows the user to select whether they are interested in making the a /home partition. If that option is selected the easiest way to do this is would probably be to offer a few options:
1. Setup "A" - default + /home of rest of hard disk
2. Setup "B" - Default + /home of X (user defined)
3. Setup "C" - I want to manually define my partitions (advanced)
I don't think the lack of information should be a show stopper for this popular idea!
Let me know what you guys think.
Thanks,
If I'd had a separate /home partition, I would have saved myself quite a bit of hardship when my Kubuntu Gutsy-to-Hardy upgrade got completely borked.
I had pretty good backups, and was able to recover almost everything (except for my KMail email from a period of about six months) - but a separate /home partition would have prevented the whole thing.
I even knew beforehand that I should have already re-partitioned my HDD, but never bothered to do so. Though, when I had to install Kubuntu Hardy from scratch, you can be sure that I took the time to put /home in its own partition.
So, what's easier:
1) Trying to teach people (newbies, Windows converts, etc.) how to perform backups, and how to restore backups - and then expecting them to perform them regularly?
or
2) Having a GUI option in Ubiquity to put /home in a separate partition?
(Note: I understand that the latter option does *not* preclude performing regular backups as a matter of best practice; however, the user data are much safer to begin with, if /home is in a separate partition - and those data are much better-protected against the kinds of events that would necessitate restoring from backup, such as a borked dist-upgrade.)
+1: having a separate /home is an extremely good idea. Besides, when the "preserve user files and settings; reinstall system files" option in Ubiquity is selected, the existing /etc/fstab should be scanned and mount points kept if possible.
I agree. Too many problems when users want to reinsintall his system, in most case he loses ALL HIS DATAS. So, please add this feature. Just add "Create /home" clearly, not in a advanced menu.
"In response to the developer comment pointing out that figuring out a default size would be hard, there could simply be a screen asking the user to move a slider to determine what percentage of their harddrive they wanted to use for data."
This is all a horrible idea. Users can't predict how much space they are going to need for each component of their system.
Please just use one partition. If there are problems with using only one partition, fix those problems. Don't require the user to deal with awful system-level details like this.
We are supposed to be making computers easier to use, not scaring people away. If you want to create a separate partition on your machine for every system folder, find another distro.
So, should *all* advanced settings during install be removed - in the name of "making computers easier to use, not scaring people away"?
Advanced options are both, for good reason. They are "advanced" in that most people needn't concern themselves with them, and can safely accept the defaults, and they are "options" in that they can be modified for those who know how and choose to do so.
The "find another distro" statement is unnecessary. Ubuntu is "Linux for human beings," not "Linux for idiots." It does not need to be dumbed down to the lowest common denominator.
Your condescending attitude is exactly what drives people away from Linux. There are plenty of other distros where disparaging users as "idiots" is the norm. So far Ubuntu is not one of them, and I hope it stays that way.
We have heard enough of the "X is exactly what drives people away from Linux" rhetoric, and chipbennet is not condescending. He, like L. Torvalds did years ago, is pointing a worrying trend in some projects, particularly GNOME, which for the sake of "usability by newbies" progressively remove advanced options. Thus, each new version comes with _less_ features than the former.
While we should indeed run away from the checkbox madness of the early versions of KDE and establish sane defaults for most values, removing _any_ advanced options to avoid scaring newbies is definitely dumb. I don't want to be forced to use the "alternate" CD to perform a LVM+crypto install!
Irony, thy name is "Endolith". Your assertion to "find another distro" is not only condescending, but it is also the essence of hubris.
You imply that my statement disparages users; however, you fail to realize that I was not disparaging *users* but rather *your* attitude toward those users.
My point was that *your* attitude assumes that users are idiots. My point (as Habbit understood) was that users are *not* idiots, and Ubuntu does not need to treat them as if they were idiots.
It is not disparaging toward users to assume that they will not be confused by adding a useful, advanced option during the installation process.
It *is*, however, disparaging toward users to assume that they:
1) Cannot predict (or at least reasonably estimate) how much disk space they will need for root and home partitions (or, simply accept the offered defaults),
2) Would consider dealing with a secure partitioning strategy to be "awful system-level details" (or, as is implied here, that they would be incapable of learning or understanding such details),
3) Would consider such an advanced option during installation to make their computer "harder to use", and that it would "scare them away".
These are assumptions that *you* made about users. I disagree with those assumptions, and believe that it is thse assumptions, that *you* made about users, that would render Ubuntu "Linux for Idiots".
I'm not a Linux expert. I've been using Kubuntu for less than a year, and Ubuntu for a few months before that. I would consider myself a "power" Windows user, but I am still very much learning my way in Linux.
I consider myself to be the middle ground. I enjoy learning the more advanced things, and believe myself capable of doing so - but I still understand how it is to be a "newbie".
I believe that almost *any* computer user is capable of using Ubuntu (though my personal preference is Kubuntu) - and therefore, Linux in general. I therefore do not believe that Ubuntu should be "dumbed down".
If a feature is beneficial then it should be implemented.
This feature is beneficial, and should be implemented. The non-curious users will continue to be happy using the install defaults. The more curious users may just learn something very beneficial about data management on their computer.
"Cannot predict (or at least reasonably estimate) how much disk space they will need for root and home partitions (or, simply accept the offered defaults)"
I am 100% certain that someone with no Linux experience cannot predict how much space will be taken up by their system files. This is absolutely not something that users should be forced to do during installation. Setting up a too-small partition for either system or home will cause serious problems down the line.
"The non-curious users will continue to be happy using the install defaults."
According to the description, the "install defaults" would be to present the user with a slider and ask them to predict the future. Average computer users do NOT understand partitioning and cannot predict how much space their Ubuntu installation is going to take in the future, and no, this does not make them "idiots".
"The more curious users may just learn something very beneficial about data management on their computer. "
Ubuntu is not a tool for teaching users Computer Science. It's an operating system that allows users to accomplish tasks, like writing a book, drawing a picture, or communicating with friends. Users should never be forced to learn how their system works in order to use it.
I agree 100% with the developer's comment; this is useful for people who are already knowledgeable about it, but most people are not, and it should not be the recommended default.
I am 100% certain that someone with no Linux experience cannot predict how much space will be taken up by their system files. This is absolutely not something that users should be forced to do during installation. Setting up a too-small partition for either system or home will cause serious problems down the line.
Likewise, I am 100% certain that said person with no Linux experience can with confidence accept an offered default for an advanced installation option.
According to the description, the "install defaults" would be to present the user with a slider and ask them to predict the future. Average computer users do NOT understand partitioning and cannot predict how much space their Ubuntu installation is going to take in the future, and no, this does not make them "idiots".
Again, the default is a configuration determined according to an algorithm based upon the disk size, with X GB for root and Y GB for home, or else use the entire disk with both root and home on a single partition. The user needs take no action to use the default configuration offered.
Ubuntu is not a tool for teaching users Computer Science. It's an operating system that allows users to accomplish tasks, like writing a book, drawing a picture, or communicating with friends. Users should never be forced to learn how their system works in order to use it.
Users *always* have to learn how their system works in order to use it. Always. There is no exception.
Nevertheless, presenting this option in no way requires the user to learn even on bit of information more than would have been required had the option not been presented. An acceptable default is offered, requiring no input or understanding from the user.
My point was not that presenting this option would *require* users to find out why the option is presented, but rather that those users who are curious may decide to learn about the option and why it is presented.
I agree 100% with the developer's comment; this is useful for people who are already knowledgeable about it, but most people are not, and it should not be the recommended default.
To the contrary, this option is useful for *everyone*, whether or not users are knowledgable about it.
"I am 100% certain that someone with no Linux experience cannot predict how much space will be taken up by their system files. This is absolutely not something that users should be forced to do during installation. Setting up a too-small partition for either system or home will cause serious problems down the line."
Likewise, I am 100% certain that said person with no Linux experience can with confidence accept an offered default for an advanced installation option.
"According to the description, the "install defaults" would be to present the user with a slider and ask them to predict the future. Average computer users do NOT understand partitioning and cannot predict how much space their Ubuntu installation is going to take in the future, and no, this does not make them "idiots"."
Again, the default is a configuration determined according to an algorithm based upon the disk size, with X GB for root and Y GB for home, or else use the entire disk with both root and home on a single partition. The user needs take no action to use the default configuration offered.
"Ubuntu is not a tool for teaching users Computer Science. It's an operating system that allows users to accomplish tasks, like writing a book, drawing a picture, or communicating with friends. Users should never be forced to learn how their system works in order to use it."
Users *always* have to learn how their system works in order to use it. Always. There is no exception.
Nevertheless, presenting this option in no way requires the user to learn even on bit of information more than would have been required had the option not been presented. An acceptable default is offered, requiring no input or understanding from the user.
My point was not that presenting this option would *require* users to find out why the option is presented, but rather that those users who are curious may decide to learn about the option and why it is presented.
"I agree 100% with the developer's comment; this is useful for people who are already knowledgeable about it, but most people are not, and it should not be the recommended default."
To the contrary, this option is useful for *everyone*, whether or not users are knowledgable about it.
Assuming that in most cases /home partitions have more free space than / it would make sense to link /tmp to something like "/home/.tmp".
This would really help if you have applications that produce large files in /tmp (like mplayer-plugin or flash), because you don't have to partition your / bigger in fear of running out of temporary space, when your /home has many GB left.
I am a relatively new user to Linux, Ubuntu specifically (about a month total), and on first install I felt forced into manually partitioning my drive to set it up for a dual boot environment.
Unfortunately I had no idea what a / or a /swap was, what they were used for, and how much space they needed. I think that more information in the manual partition setup would have kept me from making a 10g /swap the first time around.
When I first installed, I jumped in with both feet: customizing, installing apps, tweaking, etc. but, alas, I had a dual monitor setup (both being different sizes) and an ATI card, and I really wanted that cool compiz stuff to work.
Needless to say, there were no obvious 'system restore' options. After reinstalling several times trying to make things work, and losing all of my personal stuff, I gave up and put Feisty on the shelf.
Now, I have an Nvidia card and all is well. I have even lost some of that tentative nature and began to reinstall programs and customize my system.
I have since learned how to tar my stuff. Fortunately I haven't had a need to restore it.
My biggest fear with using Ubuntu: upgrading to Intrepid and breaking something (compiz, Nvidia, etc.) and flushing my /home folder down the drain -again-
I desperately want to move my /home to somewhere safe (in addition to the backups I make). Now that I realize that it is possible for the OS to function with / and /home on seperate partitions, I am off on a quest to find out if I can do this now, or if this is only an option at install.
oh, Ubuntu. Why must you make a relatively simple 'advanced' option so complicated.
It would be also great to create home in another hdd than system.
When we use Alpha or Beta versions of Ubuntu it will make life easier while formatting and reinstalling the system.
The system may ask us while installing if we have a separate home partition or hdd.
If we answer yes system may scan harddisks and partitions to find our old home.
After confirmation of home system will install itself to one harddrive and use the home in another haddrive.
Reinstallation of syetem will be so easy without backup.
I can't appreciate enough how easy having a dedicated filesystem for /home is. Something I've found it especially good for is using EXT2 IFS in Windows to view files I keep in /home but without having to mount / in Windows, putting it at risk.
I think Ubiquity does a pretty good job (as of Hardy) to make it easy to create or select an existing /home filesystem, which I think is more than enough for anyone who already understands the value of a dedicated /home.
It would be a healthy touch to give an option for a rational guess on what should be left for /home, but both a power and a frustration UNIX derivatives have is their scalability and what any one user plans to do is difficult for anyone to guess.
I'm afraid it's the least dis-beneficial option to have it all on one file system unless the user knows what they want to do with it, but if there's any meaningful way to determine distribution with minimal user input and little experience, I'm all for it.
Also, in some situations, it can be unhelpful to chop a disk drive into any more pieces than it needs to be.
The developper comment sucks :
He says that having a separated /home is really a good thing, that we could at least propose the option... but he will "stick to the current partitioning system".
Is it really so difficult to propose this option in the installer ? 'Cause, yeah, we can do it manually, but newbies are confused when they have to use the manual partitioning in order to have this /home separated (they need to create manually a /, /home and swap partition, indicate mount point, etc...)