Written by vinlos the 29 Feb 08 at 10:46.

Ubuntu Brainstorm was updated in January 2009. Since the idea #1242 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #1242 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by Hetor the 31 Mar 09 at 12:57.

Create an option for installation disk that will install just Ubuntu's boot menu to make Ubuntu accessible after Windows installation.

Create an option for installation disk that will install just Ubuntu's boot menu to make Ubuntu accessible after Windows installation.

Written by stoffel the 31 Mar 09 at 21:39.

So, similar as the first solution, but with these differences:
* people do not understand "boot menu"
* it puts focus on the fact that the Windows installer is crap that can break the user's system, whilst at the same time pointing out Ubuntu has the tools to fix this crap

So, similar as the first solution, but with these differences: * people do not understand "boot menu" * it puts focus on the fact that the Windows installer is crap that can break the user's system, whilst at the same time pointing out Ubuntu has the tools to fix this crap

Written by cheesehead the 31 Mar 09 at 21:50.

LiveCD should check for an existing MBR or grub, and offer to reinstall grub only if the LiveCD finds an MBR or broken grub

LiveCD should check for an existing MBR or grub, and offer to reinstall grub only if the LiveCD finds an MBR or broken grub

Written by supermorph the 3 Apr 09 at 18:26.

as an option as WELL as placing grub into mbr , i would suggest Making a DUPLICATE of the mbr and place the mbr file in windows boot.ini and the vista bootmgr menu's (should windows be located in the install)

i had to re-do somebodys system, they was very dubious on linux (they had another distro and it didnt do wireless, so they over generalised and thought gnu/linux as a whole was not good) and i suggested to fix thier pc,
they left it with me, so i put thier media-centre xp first, all thier apps how they liked, installed a hidden user for me, and installed jaunty 9.04 at the end of the hdd, and made the users exactly like the xp, (both with firefox, and wine 4 ubuntu) i also took the liberty of extracting the installed mbr of ubuntu to a file "ubuntu.mbr" i called it, and placed it into thier xp partition (hidded,system applied) and added a menu "Ubuntu Linux" to thier boot.ini as the second option, i then proceeded to make a recovery image of this setup and put it to four dvd's with all of the dvd's bootable to a registered acronis 8 personal of myne, so if they restore it will ALWAYS work, and if they need whats on there they can remove the mbr and STILL use ubuntu (or put it back if they ask how to do it)

mabye this could be done, and add an option to restore this mbr file to the hdd in recovery mode on the live/alt disks?

sorry for the long post, but i think it will actually help because of the way i done things, theres no way ubuntu cannot be run in that configuration.

as an option as WELL as placing grub into mbr , i would suggest Making a DUPLICATE of the mbr and place the mbr file in windows boot.ini and the vista bootmgr menu's (should windows be located in the install) i had to re-do somebodys system, they was very dubious on linux (they had another distro and it didnt do wireless, so they over generalised and thought gnu/linux as a whole was not good) and i suggested to fix thier pc, they left it with me, so i put thier media-centre xp first, all thier apps how they liked, installed a hidden user for me, and installed jaunty 9.04 at the end of the hdd, and made the users exactly like the xp, (both with firefox, and wine 4 ubuntu) i also took the liberty of extracting the installed mbr of ubuntu to a file "ubuntu.mbr" i called it, and placed it into thier xp partition (hidded,system applied) and added a menu "Ubuntu Linux" to thier boot.ini as the second option, i then proceeded to make a recovery image of this setup and put it to four dvd's with all of the dvd's bootable to a registered acronis 8 personal of myne, so if they restore it will ALWAYS work, and if they need whats on there they can remove the mbr and STILL use ubuntu (or put it back if they ask how to do it) mabye this could be done, and add an option to restore this mbr file to the hdd in recovery mode on the live/alt disks? sorry for the long post, but i think it will actually help because of the way i done things, theres no way ubuntu cannot be run in that configuration. kind regards supermorph

Written by jamesisin the 7 Apr 09 at 06:38.

Create an ISO available to Ubuntu users (linked probably in the Help menu &c) which has been set up specifically for repairing version x.y of Ubuntu.

(Part of my "Keep the installer trim" philosophy.)

Create an ISO available to Ubuntu users (linked probably in the Help menu &c) which has been set up specifically for repairing version x.y of Ubuntu. (Part of my "Keep the installer trim" philosophy.)

Written by codeslicer the 27 Feb 09 at 20:33.

One of the options for a bootable partition in GParted would be to Reinstall Boot Manager, after which an option to install either GRUB or LILO on to the hard partition.

One of the options for a bootable partition in GParted would be to Reinstall Boot Manager, after which an option to install either GRUB or LILO on to the hard partition.

Written by TheLions the 1 Mar 09 at 20:41.

instead making repairing tool why not include a easy-to-understeand-do-it-yourself guide how to repair GRUB?

instead making repairing tool why not include a easy-to-understeand-do-it-yourself guide how to repair GRUB?

Written by josinalvo the 7 Mar 09 at 04:08.

There is a windows app called super grub disk that is able to solve the problem (The odd name comes from a live cd that does the same job)

I propose this app should be on the livecd, on that part that is acessible from windows (a.k.a. outside squashfs)

There is a windows app called super grub disk that is able to solve the problem (The odd name comes from a live cd that does the same job) I propose this app should be on the livecd, on that part that is acessible from windows (a.k.a. outside squashfs)

Written by pengo the 9 Mar 09 at 02:25.

This will probably get voted down for mentioning MICROSOFT, but as this problem is generally a problem with Windows rudely taking over from Grub, why not make a Windows application that installs or restores GRUB?

This will probably get voted down for mentioning MICROSOFT, but as this problem is generally a problem with Windows rudely taking over from Grub, why not make a Windows application that installs or restores GRUB?

Written by jekristiansen the 10 Jan 10 at 01:45.

It would be nice if there was an option to re-install boot loaders for both Ubuntu and Windows. Remove Ubuntu + Grub, and the Windows boot is missing.
Install Windows, and there's no Grub
I installed windows again because of that...

It would be nice if there was an option to re-install boot loaders for both Ubuntu and Windows. Remove Ubuntu + Grub, and the Windows boot is missing. Install Windows, and there's no Grub I installed windows again because of that...

Written by LordHawke13 the 8 Feb 10 at 04:34.

I suggest an application that will run the contents of a boot disk either to an internal guest display (as in a Virtual Machine) or to an attached external display (like a second monitor) to install an operating system for dual booting. Since it can be done from inside the host OS, it can suppress the secondary OS' process of overwriting the MBR, preserving the primary bootloader, and optionally writing entries to the bootloader's boot menu for chainloading the secondary OS. Such an app would eliminate the need of a bootable LiveCD as the bootloader will be intact and in no need of restoration.

I suggest an application that will run the contents of a boot disk either to an internal guest display (as in a Virtual Machine) or to an attached external display (like a second monitor) to install an operating system for dual booting. Since it can be done from inside the host OS, it can suppress the secondary OS' process of overwriting the MBR, preserving the primary bootloader, and optionally writing entries to the bootloader's boot menu for chainloading the secondary OS. Such an app would eliminate the need of a bootable LiveCD as the bootloader will be intact and in no need of restoration.

Written by pfelelep the 15 Feb 10 at 07:40.

25 years ago today, I was able to simply change mac os 6 boot folder by just removing or adding the Finder file. That was useable.
25 years ago today I was able to repair most non booting DOS issues by just typing SYS C: That was almost useable.

What do we have in 2010 ? A OS that breaks its own bootloader when you try to update it. And that's when you managed to install it in the first place... And if you're to fix it (I guess most debuting users will just wipe their disk and start over again from here) you have to download 3 different discs to try from (live, alt, supergrub) . That's progress I guess ?

Grub is excellent software, but its useability and reliability need to be reinforced !

What I need on the install disc is a tool that lets me :
step 1 : describe partitions in my system. no installer or tool can guess that stuff in a mildly sophisticated system. there could also be an automatic mode for simple 1 or 2 partition setups. LVM should always be natively supported.
Step 2 : choose mbr or grub partition target
Step 3 : Click Fix and reboot !

25 years ago today, I was able to simply change mac os 6 boot folder by just removing or adding the Finder file. That was useable. 25 years ago today I was able to repair most non booting DOS issues by just typing SYS C: That was almost useable. What do we have in 2010 ? A OS that breaks its own bootloader when you try to update it. And that's when you managed to install it in the first place... And if you're to fix it (I guess most debuting users will just wipe their disk and start over again from here) you have to download 3 different discs to try from (live, alt, supergrub) . That's progress I guess ? Grub is excellent software, but its useability and reliability need to be reinforced ! What I need on the install disc is a tool that lets me : step 1 : describe partitions in my system. no installer or tool can guess that stuff in a mildly sophisticated system. there could also be an automatic mode for simple 1 or 2 partition setups. LVM should always be natively supported. Step 2 : choose mbr or grub partition target Step 3 : Click Fix and reboot !

Written by leorolla the 11 Mar 10 at 17:26.

People who try Ubuntu for one day (perhaps because a friend insisted) and then decide to wipe it out, find themselves desperate when they realize that their computer is not working at all.
And they say that it's Ubuntu's fault!
And they are right!
In fact it is the installation of Ubuntu that has just broken the user's system.

If this or that OS is crap, it will be obvious from the facts. It is for the user, and only for the user, to come up with that conclusion.

What Ubuntu has to do is to be as good as it can, and other OS's won't provide equivalent tools.
As for today, they don't come even close, but who knows...

If an Ubuntu application will propose the user to "fix" the MBR, it should propose to "fix" the MBR in both directions: to replace the current MBR by Grub, or to replace it by another OS's bootloader.

No matter if it will do it at the Live CD, a Desktop application or an application to be run inside other OS's, it should offer both possibilities.

This would make Ubuntu inarguably superior.

People who try Ubuntu for one day (perhaps because a friend insisted) and then decide to wipe it out, find themselves desperate when they realize that their computer is not working at all. And they say that it's Ubuntu's fault! And they are right! In fact it is the installation of Ubuntu that has just broken the user's system. If this or that OS is crap, it will be obvious from the facts. It is for the user, and only for the user, to come up with that conclusion. What Ubuntu has to do is to be as good as it can, and other OS's won't provide equivalent tools. As for today, they don't come even close, but who knows... If an Ubuntu application will propose the user to "fix" the MBR, it should propose to "fix" the MBR in both directions: to replace the current MBR by Grub, or to replace it by another OS's bootloader. No matter if it will do it at the Live CD, a Desktop application or an application to be run inside other OS's, it should offer both possibilities. This would make Ubuntu inarguably superior. If the user chooses to fix the MBR using another OS's bootloader, and the application can still detect that some Linux partition, then it should implement an ingenious procedure to chainload Grub from the other OS (as described at Solution #5, for the case of Windows).

Written by checoimg the 1 Feb 11 at 03:06.

Auto restoring option on grub (don't tell me if it is posible or not).
Make Grub Reinstall itself until you enter Ubuntu and change that option, so after any change grub will overwrite the new loader and persist to be the used loader. Of course updating the list of OS and maybe add on Gparted a detct OS option in case of problems detecting new OS installed on same Hard Disk

Auto restoring option on grub (don't tell me if it is posible or not). Make Grub Reinstall itself until you enter Ubuntu and change that option, so after any change grub will overwrite the new loader and persist to be the used loader. Of course updating the list of OS and maybe add on Gparted a detct OS option in case of problems detecting new OS installed on same Hard Disk

Written by Theodore the 3 Apr 08 at 20:19.

Ubuntu Brainstorm was updated in January 2009. Since the idea #6351 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #6351 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by lavinog the 1 May 09 at 16:56.

Usually during a kernel update I get the 'what should be done about menu.lst'
I choose the same option every time.
A checkbox could be added to remember the choice for future updates.

Usually during a kernel update I get the 'what should be done about menu.lst' I choose the same option every time. A checkbox could be added to remember the choice for future updates.

Written by sventer the 7 Jun 10 at 15:31.

So my suggestions are:
1. Design those messages so that, when they pop up, they (the messages) can continue to wait for the user's acknowledgement before disappearing again, but let the underlying upgrade process continue past that point without waiting for the user acknowledgement.

2. Similarly, to prevent a delay at the end the "calculating the changes" part of the "Setting new software channels" downloading, is it not possible to provide a check-box or other option, which would allow a user to specify that the upgrade should continue without having the user specifically click to "Start Upgrade".. again, the information in the pop-up windows is useful to see, but I would like to have the option to allow my upgrade to continue on and get done.. I can always come back later and review the details etc.

So my suggestions are: 1. Design those messages so that, when they pop up, they (the messages) can continue to wait for the user's acknowledgement before disappearing again, but let the underlying upgrade process continue past that point without waiting for the user acknowledgement. 2. Similarly, to prevent a delay at the end the "calculating the changes" part of the "Setting new software channels" downloading, is it not possible to provide a check-box or other option, which would allow a user to specify that the upgrade should continue without having the user specifically click to "Start Upgrade".. again, the information in the pop-up windows is useful to see, but I would like to have the option to allow my upgrade to continue on and get done.. I can always come back later and review the details etc.

Written by korin43 the 9 Jul 09 at 09:32.

Instead of copying packages from the CD to hard drive as soon as the installer starts, the live CD should start preloading as much of the CD as possible into memory while it's asking the user questions like their locale and name. This should give a noticeable speed boost on computers with enough memory (and shouldn't slow anything down on computers that don't - it would just stop preloading when it runs out of memory).

Instead of copying packages from the CD to hard drive as soon as the installer starts, the live CD should start preloading as much of the CD as possible into memory while it's asking the user questions like their locale and name. This should give a noticeable speed boost on computers with enough memory (and shouldn't slow anything down on computers that don't - it would just stop preloading when it runs out of memory).

Written by Rodrigo the 12 Jul 09 at 15:38.

While you are answering questions the Setup program could be looking for networks, and maybe updating the packages list, so it does install the latest safety files, if the connection is fast, and the user wants.
Maybe asking:
would you like to download the latest safety updates, this could slow down the process of the installment in slower connections.
You wouldn't need to install something and then update it... it could be done in the same step

While you are answering questions the Setup program could be looking for networks, and maybe updating the packages list, so it does install the latest safety files, if the connection is fast, and the user wants. Maybe asking: would you like to download the latest safety updates, this could slow down the process of the installment in slower connections. You wouldn't need to install something and then update it... it could be done in the same step

Written by snadrus the 13 Jul 09 at 16:27.

Slackware did this 15 years ago!

Questions:
, ,

Then while installing: (progress bar underneath)
, , , etc

If it 'feels' slow while you fight the CPU for copy time, then they could always wait until it's finished (like it is now). Obviously those options wouldn't commit until you "finished" the install. This could save 5 minutes.

Slackware did this 15 years ago! Questions: <language>, <keyboard>, <partition> Then while installing: (progress bar underneath) <user info>, <timezone>, <popcon>, etc If it 'feels' slow while you fight the CPU for copy time, then they could always wait until it's finished (like it is now). Obviously those options wouldn't commit until you "finished" the install. This could save 5 minutes.

Written by tigr the 14 Jul 09 at 02:05.

As soon as user selects language (and if it differs from english) installer could start downloading required packages in background.

As soon as user selects language (and if it differs from english) installer could start downloading required packages in background.

Written by aaron.roydhouse the 15 Jul 09 at 12:32.

Great idea. I'd like to propose a very simple implementation of it; that is possibly also the fastest/most efficient way to achieve this.

Given many install targets now have much more spare RAM during an install than the size of a CD; linear read the whole CD image in RAM, mount as an ISO, and install from there.

Linear copying the whole CD is the fastest way to get the install image into RAM and would normally only take between 2 and 7 minutes. So can ask all the simple install questions while that happens. The run the entire current install process from the RAM-mounted ISO.

This feature would only be enabled on targets with more than a CD-worth of free RAM (everything with 1GB or more?). On install targets without enough space RAM, just use the same from-CD install process as now.

Great idea. I'd like to propose a very simple implementation of it; that is possibly also the fastest/most efficient way to achieve this. Given many install targets now have much more spare RAM during an install than the size of a CD; linear read the whole CD image in RAM, mount as an ISO, and install from there. Linear copying the whole CD is the fastest way to get the install image into RAM and would normally only take between 2 and 7 minutes. So can ask all the simple install questions while that happens. The run the entire current install process from the RAM-mounted ISO. This feature would only be enabled on targets with more than a CD-worth of free RAM (everything with 1GB or more?). On install targets without enough space RAM, just use the same from-CD install process as now.

Written by xfuser4 the 20 Jul 09 at 07:24.

There are several reasons why it is a bad idea to do anything in parallel before installation:

1. Loading from the disk during the user input phase of the installer could result in slow responsiveness of the user interface (at least on cheaper hardware, like my notebook, where disk accesses are resulting in a massive slow down of the system).

During the installation phase, Ubuntu should look very responsive - otherwise people will be disappointed.



2. Downloading locales or recent system updates during that phase is also a bad idea - at least, if you don't ask the user to do so. For several reasons:

- The user has an internet connection, that has a volume restriction (this is still usual in some places of the world). So you could destroy the quota of the user.

- To do any bigger access on the internet without notifying the user is generally a bad idea, because the user has not the impression to have the control over the system.

- Normally the user won't configure the WLAN settings, so this operation won't work at all.

There are several reasons why it is a bad idea to do anything in parallel before installation: 1. Loading from the disk during the user input phase of the installer could result in slow responsiveness of the user interface (at least on cheaper hardware, like my notebook, where disk accesses are resulting in a massive slow down of the system). During the installation phase, Ubuntu should look very responsive - otherwise people will be disappointed. 2. Downloading locales or recent system updates during that phase is also a bad idea - at least, if you don't ask the user to do so. For several reasons: - The user has an internet connection, that has a volume restriction (this is still usual in some places of the world). So you could destroy the quota of the user. - To do any bigger access on the internet without notifying the user is generally a bad idea, because the user has not the impression to have the control over the system. - Normally the user won't configure the WLAN settings, so this operation won't work at all. 3. The installation phase is the shortest phase of the system life time. Therefore it is a bad idea, to spend too much development time to it. The installation should work and should be user friendly - but no one really needs other fancy stuff there. Ubuntu installs already very much faster than Windows Vista, Windows XP and MacOS X. The installation is clean and user friendly. So it would be better, to solve other (more important) problems...

Written by r3l1c the 21 Jul 09 at 18:36.

When I saw Search for the "net" while asking questions I immediately had my concerns. Connecting to the internet without the users permission is a Micro$oft problem that I have no desire to include within my favorite operating system.

I think that is a really bad idea

I do like the other ideas though

When I saw Search for the "net" while asking questions I immediately had my concerns. Connecting to the internet without the users permission is a Micro$oft problem that I have no desire to include within my favorite operating system. I think that is a really bad idea I do like the other ideas though

Written by kir360 the 24 Jul 09 at 17:53.

interestingly, the installation of ubuntu to a USB stick finishes very quickly. this might be because the CD image is directly being copied to the USB stick.

We can adopt the same method in here. the installation finishes and the system restarts. then a one-time menu pops up to configure the user details, etc. only the installation partition and grub path has to be given earlier.

interestingly, the installation of ubuntu to a USB stick finishes very quickly. this might be because the CD image is directly being copied to the USB stick. We can adopt the same method in here. the installation finishes and the system restarts. then a one-time menu pops up to configure the user details, etc. only the installation partition and grub path has to be given earlier.

Written by Afroman10496 the 5 Aug 09 at 21:58.

Add an option for an Internet inatall.

Add an option for an Internet inatall.

Written by korin43 the 16 Aug 09 at 08:58.

Before starting the preloading thread, the live CD could check the clock speed and and amount of memory on the target computer. If it is below certain thresholds, the preload thread would not be started at all.

Where the lower bound should be is something that the Ubuntu developers should decide on, since they would know, but a simple example would be on a computer with 4 Gb of memory and a 3 Ghz Core 2 Duo, the Live CD would be loaded into memory (in the background). On a computer with 256 Mb of memory and a Pentium, it would not.

Before starting the preloading thread, the live CD could check the clock speed and and amount of memory on the target computer. If it is below certain thresholds, the preload thread would not be started at all. Where the lower bound should be is something that the Ubuntu developers should decide on, since they would know, but a simple example would be on a computer with 4 Gb of memory and a 3 Ghz Core 2 Duo, the Live CD would be loaded into memory (in the background). On a computer with 256 Mb of memory and a Pentium, it would not.

Written by nandayo the 14 Apr 09 at 16:24.

This should be really more logical ! Ext3 filesystem into one color, swap into another color, NTFS into another one, and so on ! (as GParted do finaly !) This would be really more visual and a more intelligent use of colors. Of course, each partition must be clearly delimited, to avoid consecutive partitions of the same filesystem to be few visible.

Here is an (ugly :-p ) example I made to illustrate :
http://img209.imageshack.us/my.php?image=56626046.png
(this is just an *ILLUSTRATION*, not a graphical proposition ! )

Maybe another suggestion : note by a symbol (a star for example) the partition containing an OS.

This should be really more logical ! Ext3 filesystem into one color, swap into another color, NTFS into another one, and so on ! (as GParted do finaly !) This would be really more visual and a more intelligent use of colors. Of course, each partition must be clearly delimited, to avoid consecutive partitions of the same filesystem to be few visible. Here is an (ugly :-p ) example I made to illustrate : http://img209.imageshack.us/my.php?image=56626046.png (this is just an *ILLUSTRATION*, not a graphical proposition ! ) Maybe another suggestion : note by a symbol (a star for example) the partition containing an OS.

Written by nandayo the 14 Apr 09 at 16:27.

This probably made a lot of user to loose their previous OS and data ! I suggest a more intelligent partitioning, which keep alive existing OS *and* other existing data partitions.

This probably made a lot of user to loose their previous OS and data ! I suggest a more intelligent partitioning, which keep alive existing OS *and* other existing data partitions.

Written by nandayo the 14 Apr 09 at 16:32.

Just some smart tooltip, or a "watizit ?", to let new users to understand what the partitioning tool is asking about mounting point.

Just some smart tooltip, or a "watizit ?", to let new users to understand what the partitioning tool is asking about mounting point.

Written by Clorox the 15 Apr 09 at 02:36.

Shouldn't be hard. It is much more advanced and should fit in the installer.

Shouldn't be hard. It is much more advanced and should fit in the installer.

Written by Kver the 19 Apr 09 at 06:02.

Make the colour bar a prominent tool instead of only a display.

- Use icons to help identify the partitions, such as a windows logo on detected windows installations, an Ubuntu logo for Ubuntu installs, and other icons for common types of partitions.
- Allow users to drag/stretch/squish partitions on the bar itself. Ie; squish a windows partition. Back or transparency could be used for empty space.
- Do NOT make it one colour/one filesystem type. If you have multiple partitions of the same type, it might appear as a single colour slab. Using alternating shades could correct this problem (dark/light/dark/light)
- Explain a partition on mouseover in a box underneath the bar.

Make the colour bar a prominent tool instead of only a display. - Use icons to help identify the partitions, such as a windows logo on detected windows installations, an Ubuntu logo for Ubuntu installs, and other icons for common types of partitions. - Allow users to drag/stretch/squish partitions on the bar itself. Ie; squish a windows partition. Back or transparency could be used for empty space. - Do NOT make it one colour/one filesystem type. If you have multiple partitions of the same type, it might appear as a single colour slab. Using alternating shades could correct this problem (dark/light/dark/light) - Explain a partition on mouseover in a box underneath the bar.

Written by Kver the 19 Apr 09 at 06:19.

A dropdown could be placed with several options, the selected being what it will do. Or more radio buttons could be added. These would be "smart" based on what is on the hard-drive(s), and which options would lose the least data.

Options could include:
- replacing the dominant partition (the single, largest partition will be deleted)
- shrinking all partitions (except swap) (it will try to scale by %)
- Wiping all small partitions (except swap) (keeping the largest partition and the swap, deleting all smaller partitions for space)
- Format * partition (* being a dropdown with any non-swap parition greater than 4.9gb)
- formatting (no explanation here)
- Manual

Tt would recommend a scheme based on the following, and would not show the option if the requirement isn't met:
#1 - Shrink partitions. If every partition (including Ubuntu) would have 10% of the HD's overall capacity as free space, recommend this option. Ie a 100gb hard drive would require 10gb of free space on each non-swap partition after the shrink.
#2 - Wipe small partitions. Use this option if the largest partition is at least 50% larger than non-swap partitions combined. If not, check #3.
#3 - Wipe the largest partition. Recommend this only if less than 20% of the partition is in use. Otherwise, recommend #4.

A dropdown could be placed with several options, the selected being what it will do. Or more radio buttons could be added. These would be "smart" based on what is on the hard-drive(s), and which options would lose the least data. Options could include: - replacing the dominant partition (the single, largest partition will be deleted) - shrinking all partitions (except swap) (it will try to scale by %) - Wiping all small partitions (except swap) (keeping the largest partition and the swap, deleting all smaller partitions for space) - Format * partition (* being a dropdown with any non-swap parition greater than 4.9gb) - formatting (no explanation here) - Manual Tt would recommend a scheme based on the following, and would not show the option if the requirement isn't met: #1 - Shrink partitions. If every partition (including Ubuntu) would have 10% of the HD's overall capacity as free space, recommend this option. Ie a 100gb hard drive would require 10gb of free space on each non-swap partition after the shrink. #2 - Wipe small partitions. Use this option if the largest partition is at least 50% larger than non-swap partitions combined. If not, check #3. #3 - Wipe the largest partition. Recommend this only if less than 20% of the partition is in use. Otherwise, recommend #4. #4 - Format. Always shown. #5 - Format * partition. Always shown. #5 - Manual. Never recommended, always shown, as serious damage can be done by a new user.

Written by aadityabhatia the 3 May 09 at 21:17.

Display some information about different directories and their purpose, such as:

/home Contains the home directories (personal storage) for each user on the system
/usr Contains system programs and other files for general users such as games, online help, and documentation
/tmp Contains temporary files that are erased upon reboot
/etc Contains configuration files for Linux and other installed software
/bin Contains the Linux system commands and programs (also called binaries)
/var Contains variable data that changes constantly when the system is running
... and so on.

This will help a basic user understand the system better by knowing the purpose of each directory. It is difficult to make changes once the system has been installed. Therefore the user will be able to make an informed one-time decision about allocating partitions to different directories.

Display some information about different directories and their purpose, such as: /home Contains the home directories (personal storage) for each user on the system /usr Contains system programs and other files for general users such as games, online help, and documentation /tmp Contains temporary files that are erased upon reboot /etc Contains configuration files for Linux and other installed software /bin Contains the Linux system commands and programs (also called binaries) /var Contains variable data that changes constantly when the system is running ... and so on. This will help a basic user understand the system better by knowing the purpose of each directory. It is difficult to make changes once the system has been installed. Therefore the user will be able to make an informed one-time decision about allocating partitions to different directories.

Written by delphiexile the 5 May 09 at 12:07.

As said in the title ; GParted is powerful tool , it just lacks simplicity for new comers to UBUNTU, we should keep it but simplify it.
ex:
1- Simplify the meaning of mount point
2- Simplify the error messages for public understanding.
... & more if you have !!

As said in the title ; GParted is powerful tool , it just lacks simplicity for new comers to UBUNTU, we should keep it but simplify it. ex: 1- Simplify the meaning of mount point 2- Simplify the error messages for public understanding. ... & more if you have !!

Written by danbhfive the 9 May 09 at 21:57.

Gparted is on the livecd anyway. Why not have it be an option? IE, there would be two "manually partition" options. One, for the current, low memory partitioner, and one for GParted.

This is how I remember it being done on Redhat, some ten years ago. Then, the options were autopartition, manually partition with the graphical partitioner, or manually partition with fdisk (yuk).

(Personally, I fire up GParted to partition before I do an install anyway. Like the original poster, I find the new partitioner too confusing.)

Gparted is on the livecd anyway. Why not have it be an option? IE, there would be two "manually partition" options. One, for the current, low memory partitioner, and one for GParted. This is how I remember it being done on Redhat, some ten years ago. Then, the options were autopartition, manually partition with the graphical partitioner, or manually partition with fdisk (yuk). (Personally, I fire up GParted to partition before I do an install anyway. Like the original poster, I find the new partitioner too confusing.)

Written by tuxxy the 13 May 09 at 01:53.

New users may not understand a separate /home partition fully, an idea is to illustrate to them the future benefits that it will bring to them such as updating and personal data reliability.

New users may not understand a separate /home partition fully, an idea is to illustrate to them the future benefits that it will bring to them such as updating and personal data reliability.

Written by gianni_casagrande the 30 Aug 09 at 08:04.

The partitioning process could be made simpler by adding a simplified option for Manual partitioning where a user can create custom partitions without needing to worry about mount points, filesystems etc.
The installation program will take care of making reasonable choices on mount points and fylesistems and creating a swap partition of resonable size.
There could be an option to create a separate /home partition with explained benefits and costs.

The installation program should advise simplified mode for manual partitioning to user that want to customize partition sizes but are not familiar with terms such as 'ext3' or 'swap partition'(like me for example).

The partitioning process could be made simpler by adding a simplified option for Manual partitioning where a user can create custom partitions without needing to worry about mount points, filesystems etc. The installation program will take care of making reasonable choices on mount points and fylesistems and creating a swap partition of resonable size. There could be an option to create a separate /home partition with explained benefits and costs. The installation program should advise simplified mode for manual partitioning to user that want to customize partition sizes but are not familiar with terms such as 'ext3' or 'swap partition'(like me for example).

Written by elias1884 the 29 Sep 09 at 22:06.

Add LVM and RAID Support to the application. Also these technologies should be supported in the LiveCD installer.

Add LVM and RAID Support to the application. Also these technologies should be supported in the LiveCD installer.

Written by waster the 2 Oct 09 at 07:48.

With >1 disk, the partitioner could do a quick benchmark to see what latency and throughput are, especially for SSD hardware. It could then say for example:

Mirror root across two fast disks
Put /tmp on a RAID0 array
Set up a video/music media mount point to get most capacity out of slower disks, not worrying about latency.
etc, etc.

You could even toggle how much data security you want vs speed, so a new user could benefit from RAID0 speed, RAID1, RAID5 etc securtity without knowing the details underneath.

Needless to say, LVM should be on top of all this, and the chunk/stripe size alignment should be set up automatically (currently this is only optimal by chance - beware!) and the readahead for LVM should have a much better default.

With >1 disk, the partitioner could do a quick benchmark to see what latency and throughput are, especially for SSD hardware. It could then say for example: Mirror root across two fast disks Put /tmp on a RAID0 array Set up a video/music media mount point to get most capacity out of slower disks, not worrying about latency. etc, etc. You could even toggle how much data security you want vs speed, so a new user could benefit from RAID0 speed, RAID1, RAID5 etc securtity without knowing the details underneath. Needless to say, LVM should be on top of all this, and the chunk/stripe size alignment should be set up automatically (currently this is only optimal by chance - beware!) and the readahead for LVM should have a much better default.

Written by _sebastian_ the 17 Jan 09 at 02:23.

How about a wizard (I think thats the right name according to gnome conventions...) which is run after first boot/login after installation.

This wizard could be a simple link hub to how-tos or a fully featured program (front end,gui) to do one or more of the following:

- install additional
-- fonts (for office)
-- cliparts
-- themes
- install programs
- add repositories
- set location for weather applet
- setup or migrate
-- IM profiles
-- users
-- network shares
-- ntp
-- WLAN (WEP2)
-- printer

How about a wizard (I think thats the right name according to gnome conventions...) which is run after first boot/login after installation. This wizard could be a simple link hub to how-tos or a fully featured program (front end,gui) to do one or more of the following: - install additional -- fonts (for office) -- cliparts -- themes - install programs - add repositories - set location for weather applet - setup or migrate -- IM profiles -- users -- network shares -- ntp -- WLAN (WEP2) -- printer and many more

Written by cheesehead the 17 Jan 09 at 14:20.

The system should figure out (or make a clever guess at) weather locations, ntp server, local network, internet access, printer, etc. instead of pestering non-technical users with technical questions.

The system should figure out (or make a clever guess at) weather locations, ntp server, local network, internet access, printer, etc. instead of pestering non-technical users with technical questions.

Written by _sebastian_ the 20 Feb 09 at 09:41.

Many good things could be linked with the information provided in the about me field, see idea 15083 for a few examples.

To make the "about me" more widely used it could be opened on first log in.

Many good things could be linked with the information provided in the about me field, see idea 15083 for a few examples. To make the "about me" more widely used it could be opened on first log in.

Written by Klau3 the 2 May 09 at 12:23.

First time Ubuntu boots a Dialog box should show up and ask the user if he would like to install proprietary software. If the decision was yes, these points should aper:

Install:
[ ] Microsoft fonts (Times New Roman...)
[ ] Video Codecs
[ ] Audio Codecs (including LAME)
[ ] Flash Player
[ ] Video Card driver

Average new users don't understand how to get these things working. My suggestion could prevent frustration and save time.

Maybe the pop up box could contain more informations like - “New to Ubuntu learn more etc.”....

First time Ubuntu boots a Dialog box should show up and ask the user if he would like to install proprietary software. If the decision was yes, these points should aper: Install: [ ] Microsoft fonts (Times New Roman...) [ ] Video Codecs [ ] Audio Codecs (including LAME) [ ] Flash Player [ ] Video Card driver Average new users don't understand how to get these things working. My suggestion could prevent frustration and save time. Maybe the pop up box could contain more informations like - “New to Ubuntu learn more etc.”....

Written by cyberix the 18 May 09 at 16:27.

I realize there is a problem with proprietary stuff, but the current direction seems scary too. Are we really going to offer the user a menu titled "The cool proprietary things that free software cannot provide you". This way we teach him to love those components over most of the system.

Maybe we should just automatically install the binary crap and make a menu titled "Evil stuff required to enable things" with easy removal options. And then warn the user that his system might break, if he removed the proprietary stuff as the monopolists wouldn't want him to do that.

I realize there is a problem with proprietary stuff, but the current direction seems scary too. Are we really going to offer the user a menu titled "The cool proprietary things that free software cannot provide you". This way we teach him to love those components over most of the system. Maybe we should just automatically install the binary crap and make a menu titled "Evil stuff required to enable things" with easy removal options. And then warn the user that his system might break, if he removed the proprietary stuff as the monopolists wouldn't want him to do that.

Written by Svargref the 9 Feb 10 at 19:00.

To save time, configure the system during installation

To save time, configure the system during installation <img src="http://img694.imageshack.us/img694/858/screenshot1ow.png">

Written by fractalorangejuice the 5 May 10 at 23:51.

A default screen resolution option during the installation would be nice. Sometimes when a lcd screen has a weird resolution like 1400 x 1050 it won't work at 800 x 600. Maybe a quick question before the GUI starts would be useful as a standard. Or a "Screen Resolution problems?" option at start up might be a good idea.

Once you have flagged the software/options/settings you want just prior to the partition stage a save installer settings to a flash drive option would save so much time.

A settings backup to a server for automatic re installation would be super cool.

A default screen resolution option during the installation would be nice. Sometimes when a lcd screen has a weird resolution like 1400 x 1050 it won't work at 800 x 600. Maybe a quick question before the GUI starts would be useful as a standard. Or a "Screen Resolution problems?" option at start up might be a good idea. Once you have flagged the software/options/settings you want just prior to the partition stage a save installer settings to a flash drive option would save so much time. A settings backup to a server for automatic re installation would be super cool.

Written by Oxwivi the 20 Oct 10 at 11:57.

When a program is chosen to be uninstalled, the user should be asked to if they want to just uninstall the program or completely remove it along with any extra files it has created.

Synaptic Package Manager should have this ability as well, attached to the complete removal option.

I've found using 'apt-get purge' get rids of the problem. Integrating the purge property in graphical package managers would be very useful.

When a program is chosen to be uninstalled, the user should be asked to if they want to just uninstall the program or completely remove it along with any extra files it has created. Synaptic Package Manager should have this ability as well, attached to the complete removal option. I've found using 'apt-get purge' get rids of the problem. Integrating the purge property in graphical package managers would be very useful.

Written by Lube the 8 Mar 11 at 19:37.

I'd like to see 2 separate programs:

1. More configuration during installation.
(network, proprietary stuff, add repositories, printer, etc)

2. User Account configuration after first login into a new account (including after installation).
(mail, IM, firefox, etc)

I'd like to see 2 separate programs: 1. More configuration during installation. (network, proprietary stuff, add repositories, printer, etc) 2. User Account configuration after first login into a new account (including after installation). (mail, IM, firefox, etc)

Written by spideylinux the 29 Feb 08 at 00:32.

Ubuntu Brainstorm was updated in January 2009. Since the idea #313 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #313 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by Alan Pope the 28 Feb 08 at 15:11.

Ubuntu Brainstorm was updated in January 2009. Since the idea #34 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #34 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by elias1884 the 15 Mar 09 at 01:50.

The GUI partitioning tool in the Fedora installer does support all we need. Go get it, integrate it in Ubiquity.

The GUI partitioning tool in the Fedora installer does support all we need. Go get it, integrate it in Ubiquity.

Written by mydoghasworms the 27 Apr 09 at 18:43.

It's not very obvious from the download site that to upgrade, you need the alternate install disc. The current download page (http://www.ubuntu.com/getubuntu/download ) does not even present the alternate disc as an option for download.

(Something in this direction was mentioned in the developer comment on #14064).

It's not very obvious from the download site that to upgrade, you need the alternate install disc. The current download page (http://www.ubuntu.com/getubuntu/download ) does not even present the alternate disc as an option for download. (Something in this direction was mentioned in the developer comment on <a href="/idea/14064/">#14064</a>).

Written by mydoghasworms the 30 Apr 09 at 07:08.

The problem as outlined in the developer comments on #14064 is that the CD ISO is not big enough to contain both a Live version and an upgrade repository.

The alternative would be to provide a DVD that is big enough to contain both.

The problem as outlined in the developer comments on #14064 is that the CD ISO is not big enough to contain both a Live version and an upgrade repository. The alternative would be to provide a DVD that is big enough to contain both.

Written by naxa the 11 May 09 at 23:06.

There should be an option to export my update-needs to a file for using it to download updates on a computer with internet.
The downloaded updates could be used then on the original computer. This would enable users with no or slow internet access to update more frequently with relative ease.

The exported list could either be a html file containing all the necessary links (to my default servers) or some standard format what needs a tool.

A downloader tool would also be nice feature for both of these (html/standarized file) versions. The html version then could have a link at the top of the page to select and download the downloader tool for the actual OS with internet. (For example if you need to download the stuff in an internet cafe with windows os). Or this tool could be stored on all installs of ubuntu and then copied to a pendrive / etc. with a gui/wizard when the export list is created.

There should be an option to export my update-needs to a file for using it to download updates on a computer with internet. The downloaded updates could be used then on the original computer. This would enable users with no or slow internet access to update more frequently with relative ease. The exported list could either be a html file containing all the necessary links (to my default servers) or some standard format what needs a tool. A downloader tool would also be nice feature for both of these (html/standarized file) versions. The html version then could have a link at the top of the page to select and download the downloader tool for the actual OS with internet. (For example if you need to download the stuff in an internet cafe with windows os). Or this tool could be stored on all installs of ubuntu and then copied to a pendrive / etc. with a gui/wizard when the export list is created.

Written by Egil S the 2 Mar 08 at 15:15.

Ubuntu Brainstorm was updated in January 2009. Since the idea #2487 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #2487 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by m0z4rt the 26 Aug 09 at 14:49.

check installation cd inside installer before write anything to disk

check installation cd inside installer before write anything to disk

Written by ssam the 27 Aug 09 at 13:25.

a quick check should always run. it could detect the most common burn errors.
* check size of CD
* check that some files exist

a quick check should always run. it could detect the most common burn errors. * check size of CD * check that some files exist

Written by Otus the 27 Aug 09 at 13:34.

The beginning of the installation process includes questions requiring user interaction. The installer should use this time to check the data in the background. While at it, most of the data could probably be cached for a faster installation overall.

The beginning of the installation process includes questions requiring user interaction. The installer should use this time to check the data in the background. While at it, most of the data could probably be cached for a faster installation overall.

Written by Ssdg the 27 Aug 09 at 14:21.

When you review your installation parameters, there should be a checkbox that allows the user to check for defects on the cd-rom before installation (say you've got to install ubuntu on a few computers or more, you'll check the CD the first time, do the install and just install next times).

Of course, the live CD will continue to work during the integrity check (games, firefox, ...) so you're not looking at a boring progress bar.

When you review your installation parameters, there should be a checkbox that allows the user to check for defects on the cd-rom before installation (say you've got to install ubuntu on a few computers or more, you'll check the CD the first time, do the install and just install next times). Of course, the live CD will continue to work during the integrity check (games, firefox, ...) so you're not looking at a boring progress bar.

Written by Darwin Survivor the 27 Aug 09 at 16:02.

Why are we checking the cd for integrity AFTER rebooting the machine and trying to use it instead of right after the problem would have occured (burning).

The best time to check the integrity of something is right after it is created. All ubuntu live cd's have and md5 checksums file (this is what the regular checker uses), why not have the cd burning software itself do this scan?

Burning software already verifies the cd against the iso file (default checked option), but it does not check against an md5 checksum file (which would also verify that the original ISO was valid).

Why are we checking the cd for integrity AFTER rebooting the machine and trying to use it instead of right after the problem would have occured (burning). The best time to check the integrity of something is right after it is created. All ubuntu live cd's have and md5 checksums file (this is what the regular checker uses), why not have the cd burning software itself do this scan? Burning software already verifies the cd against the iso file (default checked option), but it does not check against an md5 checksum file (which would also verify that the original ISO was valid).

Written by cos the 28 Aug 09 at 19:15.

Make the *default* download (that beginners will get) a zipped ISO. An alternative download for the usual raw ISO should also be provided for people who know the risks.
Even though this wouldn't necessarily help with failed CD burning, it should catch bad downloads at least.

Zip files can be extracted on both Linux and Windows without additional software, everybody knows how to use them, and they check file integrity while they are being extracted. This would help beginner users to catch download errors before they attempt to burn the iso to CD.

This also allows a README file to be included in the archive to explain what needs to be done, and what to do if you get extraction or burn errors, as well as explain why running the CD check before the installer is a good idea.

Of course, this would need an additional step to extract the zip, and more disk space -- a small price for beginners to pay, next to a failed OS installation!

Make the *default* download (that beginners will get) a zipped ISO. An alternative download for the usual raw ISO should also be provided for people who know the risks. Even though this wouldn't necessarily help with failed CD burning, it should catch bad downloads at least. Zip files can be extracted on both Linux and Windows without additional software, everybody knows how to use them, and they check file integrity while they are being extracted. This would help beginner users to catch download errors before they attempt to burn the iso to CD. This also allows a README file to be included in the archive to explain what needs to be done, and what to do if you get extraction or burn errors, as well as explain why running the CD check before the installer is a good idea. Of course, this would need an additional step to extract the zip, and more disk space -- a small price for beginners to pay, next to a failed OS installation!

Written by natureflow the 3 Sep 09 at 09:14.

The packaging system should detect broken packages automatically and repair them when internet connection is available.

So if there is a broken package on CD, installation won't fail and the system will repair the package later (when internet connection or a better CD is available)

The packaging system should detect broken packages automatically and repair them when internet connection is available. So if there is a broken package on CD, installation won't fail and the system will repair the package later (when internet connection or a better CD is available)

Written by CyberKiller the 9 Sep 09 at 11:36.

Metalink has checksum checking built in (MD5 and SHA1) so you always got a good file downloaded.

Metalink has checksum checking built in (MD5 and SHA1) so you always got a good file downloaded.

Written by albatroxx the 15 Sep 09 at 16:04.

Add an option to check the CD after a failed installation, it makes no sense to slow down 99% of all installations when the problem could be resolved by checking for errors only if something goes wrong

Add an option to check the CD after a failed installation, it makes no sense to slow down 99% of all installations when the problem could be resolved by checking for errors only if something goes wrong

Written by Jaksco the 18 Sep 09 at 02:38.

Have the installer automatically check (after Install Summary), but have a button or something for user to skip.

"During this helpful step, Installer takes a few moments to check the source disc itself before starting the installation process. If you see a message about a "failed checksum," then there may be an issue with your optical disc or optical drive (see the tips below).

Note: During this step, you may see a "Skip" button in the Installer window. If you haven't used your Install disc before (or recently), you should not skip this step."

(http://support.apple.com/kb/HT2956)

Have the installer automatically check (after Install Summary), but have a button or something for user to skip. "During this helpful step, Installer takes a few moments to check the source disc itself before starting the installation process. If you see a message about a "failed checksum," then there may be an issue with your optical disc or optical drive (see the tips below). Note: During this step, you may see a "Skip" button in the Installer window. If you haven't used your Install disc before (or recently), you should not skip this step." (http://support.apple.com/kb/HT2956)

Written by Lachu the 18 Sep 09 at 10:33.

If system starts, it have change to install normally. Ubuntu can check medium on file copy operation(installation process). If we have network connection, it could download broken part of CD's and fix packages/files.
(You can also put sha1/md5 sums of files on CD's, so the check can be done on installation process very easy and only broken files will be downloaded).
It should also allow to save patches on the pendrive/floppy disk, so it don't must been downloaded twice time.

If system starts, it have change to install normally. Ubuntu can check medium on file copy operation(installation process). If we have network connection, it could download broken part of CD's and fix packages/files. (You can also put sha1/md5 sums of files on CD's, so the check can be done on installation process very easy and only broken files will be downloaded). It should also allow to save patches on the pendrive/floppy disk, so it don't must been downloaded twice time.

Written by kakalaky the 29 Feb 08 at 02:36.

Ubuntu Brainstorm was updated in January 2009. Since the idea #531 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #531 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by ericpaulbishop the 10 Mar 10 at 15:53.

I created an alternate installer for doing RAID installs called salamander: www.salamander-linux.com, which is based on Ubuntu 9.10. You select the disks to include in the RAID array, the desired RAID level, file system and swap size and everything gets setup for you by the installer.

Maybe consider integrating this into the official installer? It already is configured so that users can select either the original installer or the RAID installer at the initial splash screen.

I created an alternate installer for doing RAID installs called salamander: www.salamander-linux.com, which is based on Ubuntu 9.10. You select the disks to include in the RAID array, the desired RAID level, file system and swap size and everything gets setup for you by the installer. Maybe consider integrating this into the official installer? It already is configured so that users can select either the original installer or the RAID installer at the initial splash screen.

Written by mattmyers83 the 8 Aug 09 at 20:00.

Create a graphical program that can support raid creation within the existing Ubuntu install.

Create a graphical program that can support raid creation within the existing Ubuntu install.

Written by Ssdg the 8 Aug 09 at 22:37.

Since there is no mean to create a raid within the existing install now, (according to mattmyers83). it might be usefull for server administrators to switch to raid after a few days running ubuntu. And because on well resources managing servers there is no X server, solution #1 can't work.

Since there is no mean to create a raid within the existing install now, (according to mattmyers83). it might be usefull for server administrators to switch to raid after a few days running ubuntu. And because on well resources managing servers there is no X server, solution #1 can't work.