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 ubuntosaure the 25 Jan 09 at 11:37.

With the coming of the new filesystem EXT4, create a mode which optimizes the performance on SSD drives.

With the coming of the new filesystem EXT4, create a mode which optimizes the performance on SSD drives.

Written by r0g the 27 Jan 09 at 05:43.

I don't know if there would be any design trade-offs between speed and lifespan in such a profile but SSD's short write lifespan issues are a bit of a myth so if a call needs to be made between them we should go for speed!

See this site for why it's only a problem on the smallest of devices...

http://www.storagesearch.com/ssdmyths-endurance.html

I don't know if there would be any design trade-offs between speed and lifespan in such a profile but SSD's short write lifespan issues are a bit of a myth so if a call needs to be made between them we should go for speed! See this site for why it's only a problem on the smallest of devices... http://www.storagesearch.com/ssdmyths-endurance.html

Written by TuxHHG the 19 Apr 09 at 09:53.

Like laptop-mode there can be a package that change all ssd related points in one way.

Like laptop-mode there can be a package that change all ssd related points in one way.

Written by HacKurx the 2 Jul 10 at 07:06.

Why not make the SSD option in the installer for all file systems.
It is easy to create it, simply activate SSD mode in ext4 and btrfs and write "noatime" into /etc/fstab.

Here's how it could look like:

Why not make the SSD option in the installer for all file systems. It is easy to create it, simply activate SSD mode in ext4 and btrfs and write "noatime" into /etc/fstab. Here's how it could look like: <a target="_blank" href="http://mabul.org" title="Hebergement d'images "><img src="http://moe.mabul.org/up/moe/2010/07/02/img-09055667j8x.png" alt="Hebergement d'images" /></a>

Written by caliga82 the 31 Aug 10 at 21:48.

(This may be just an addition/clarification to solution #1)

If a SSD is detected, the installer should inform the user how suitable a certain filesystem system is. In particular, if it supports the TRIM command.
Depending on the user's experience, there could be just an indicator (green, thumbs up...) or a complete explanation of the benefits of a filesystem with TRIM.

(This may be just an addition/clarification to solution #1) If a SSD is detected, the installer should inform the user how suitable a certain filesystem system is. In particular, if it supports the TRIM command. Depending on the user's experience, there could be just an indicator (green, thumbs up...) or a complete explanation of the benefits of a filesystem with TRIM.

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 ml2 the 24 Jan 09 at 15:58.

Implement a progress-bar which shows the password strength in the installer and user management tool.

Low strength = red;
middle strength = orange;
hight strength = green.

Thanks to Peter Koopman, who originally came up with the idea.

Implement a progress-bar which shows the password strength in the installer and user management tool. Low strength = red; middle strength = orange; hight strength = green. Thanks to Peter Koopman, who originally came up with the idea.

Written by gargouille the 30 Jan 09 at 02:55.

Solution #1 is an excellent idea. I think this could be expanded to have options for a password policy. These options could be available in System > Administration > Users and Groups. Check box options: (require uppercase & lowercase letters, require combination of numeric and alpha). A drop down box could also be added for the required minimum password size.

Solution #1 is an excellent idea. I think this could be expanded to have options for a password policy. These options could be available in System > Administration > Users and Groups. Check box options: (require uppercase & lowercase letters, require combination of numeric and alpha). A drop down box could also be added for the required minimum password size.

Written by kornelix the 22 Aug 09 at 14:38.

Follow the model of Gparted. Grub2 is an application on a bootable CD or USB stick.

1. user boots grub2 from CD or USB stick
2. user is presented with a list of all bootable OSs
3. user can remove unwanted entries and customize the titles
4. user hits "install grub" button
5. user reboots and sees his/her boot menu

If the bootloader gets hosed or another OS is installed, just repeat 1-5. Ideally all user menu changes would be preserved with newly installed systems added to the menu that is presented for edit.

Another option would be to add a "live" grub2 installer to the Ubuntu installer CD. Note that legacy grub1, unlike grub2, can boot from a CD, but generating the menu is horrible.

Follow the model of Gparted. Grub2 is an application on a bootable CD or USB stick. 1. user boots grub2 from CD or USB stick 2. user is presented with a list of all bootable OSs 3. user can remove unwanted entries and customize the titles 4. user hits "install grub" button 5. user reboots and sees his/her boot menu If the bootloader gets hosed or another OS is installed, just repeat 1-5. Ideally all user menu changes would be preserved with newly installed systems added to the menu that is presented for edit. Another option would be to add a "live" grub2 installer to the Ubuntu installer CD. Note that legacy grub1, unlike grub2, can boot from a CD, but generating the menu is horrible.

Written by thipv the 5 Sep 09 at 08:37.

This would be the definitive solution.
No more problems after installing new OS.

I don't know if Canonical can do anything to make this possible, but at least could support and work together with the OpenBIOS project.

This would be the definitive solution. No more problems after installing new OS. I don't know if Canonical can do anything to make this possible, but at least could support and work together with the OpenBIOS project.

Written by Fabian Andres the 2 Nov 09 at 20:07.

This should be an application placed in

System > Administration > Startup Administration

Like this one:


KGRUBEditor

(KGRUBEditor unfortunately only works with the old Grub, not with GRUB2.)

Of course, the application would need Root permissions to start (The user should type his password). It would be nice if an application like this was natively installed.

This should be an application placed in System > Administration > Startup Administration Like this one: <img src="http://img511.imageshack.us/img511/7025/adminl.jpg" /> <a href="http://www.kde-apps.org/content/show.php?content=75442"> KGRUBEditor </a> (KGRUBEditor unfortunately only works with the old Grub, not with GRUB2.) Of course, the application would need Root permissions to start (The user should type his password). It would be nice if an application like this was natively installed.

Written by ahayzen the 24 Jan 10 at 16:57.

Use the time zone location given in the installation process to determine the weather location.

Use the time zone location given in the installation process to determine the weather location.

Written by tntricker the 24 Jan 10 at 18:11.

Have the option to use an IP lookup service to guess the current location. Then display that locations weather data on the widget. This would only be used if there was no location set.

Have the option to use an IP lookup service to guess the current location. Then display that locations weather data on the widget. This would only be used if there was no location set.

Written by Akerbos the 25 Jan 10 at 07:22.

1. User Setting
2. IP lookup
3. Time zone

1. User Setting 2. IP lookup 3. Time zone

Written by spocky the 1 Feb 10 at 14:39.

When using mobile 3g to connect to internet an assistant is supporting you once you entered your location - voila
another point to be handled centrally

When using mobile 3g to connect to internet an assistant is supporting you once you entered your location - voila another point to be handled centrally

Written by euxneks the 5 Feb 10 at 03:56.

As #3, but on IP change, try to determine if the user has changed locations and popup a dialog asking if they'd like to change their location to the one guessed. This would be useful for people who are moving, or traveling constantly.

As #3, but on IP change, try to determine if the user has changed locations and popup a dialog asking if they'd like to change their location to the one guessed. This would be useful for people who are moving, or traveling constantly.

Written by maxolasersquad the 11 Feb 10 at 03:10.

If the user has a GPS chip in their computer, have a radio button to auto update the lat/long based on the gps coordinates.

If the user has a GPS chip in their computer, have a radio button to auto update the lat/long based on the gps coordinates.

Written by _nob the 17 Feb 10 at 11:49.

Which is exactly for this reason already integrated into the Desktop. See also http://brainstorm.ubuntu.com/idea/17734/

Which is exactly for this reason already integrated into the Desktop. See also http://brainstorm.ubuntu.com/idea/17734/

Written by lowlux the 15 Apr 10 at 21:05.

what about a stand alone weather bug app? that intergrets with the weather icon and GeoClue plus everything talked about in the above or comments...

what about a stand alone weather bug app? that intergrets with the weather icon and GeoClue plus everything talked about in the above or comments...

Written by SuNk8 the 3 May 10 at 16:05.

Prevention is better than Cure.
Ubuntu comes with a very cool System Testing app: checkbox-gtk
Let System Testing be one of the (optional) steps in the Live installer.

So, a newbie user can easily check and actually know if his/her PC will work fine after the upgrade.
If not, they can wait till their issues are resolved and then go for the upgrade.

Testers can just skip the step and go for the install.

Prevention is better than Cure. Ubuntu comes with a very cool System Testing app: checkbox-gtk Let System Testing be one of the (optional) steps in the Live installer. So, a newbie user can easily check and actually know if his/her PC will work fine after the upgrade. If not, they can wait till their issues are resolved and then go for the upgrade. Testers can just skip the step and go for the install.

Written by SuNk8 the 4 May 10 at 02:52.

Introduce an advanced mode where users are asked questions concerning their hardware. A questionnaire will improve the experience of the user and get the correct information from them about the hardware specs.
The installer will then check on the online database and also include drivers for those entries.

Also, we might move some other entries like bootloader configuration in this mode.

Introduce an advanced mode where users are asked questions concerning their hardware. A questionnaire will improve the experience of the user and get the correct information from them about the hardware specs. The installer will then check on the online database and also include drivers for those entries. Also, we might move some other entries like bootloader configuration in this mode.

Written by snadrus the 5 May 10 at 19:29.

'lsusb' and 'lspci' list all the hardware Linux can touch. devicekit loads drivers for these items or defers it (for scanners, printers, etc). Once done, if we have hardware that we couldn't use, lets report that hardware back to Ubuntu.

'lsusb' and 'lspci' list all the hardware Linux can touch. devicekit loads drivers for these items or defers it (for scanners, printers, etc). Once done, if we have hardware that we couldn't use, lets report that hardware back to Ubuntu.

Written by LCollins the 10 May 10 at 04:21.

Same as #1, but have the option the report the lack of hardware capabilities to Ubuntu, to help self-improvement. Also check with Ubuntu that the problems have not already been sorted (in case installation CD is out of date.

Same as #1, but have the option the report the lack of hardware capabilities to Ubuntu, to help self-improvement. Also check with Ubuntu that the problems have not already been sorted (in case installation CD is out of date.

Written by Richard.Kolodziej the 31 May 10 at 12:06.

http://kmuto.jp/debian/hcl/

http://kmuto.jp/debian/hcl/

Written by Bubble the 13 Jun 11 at 10:39.

Ubuntu should search for a hardware manufacturer, to manufacture Ubuntu-"All-in-One" PCs that just work and distribute them via store.ubuntu.com.

Do it like Apple (or Google ChromeOS), provide a few basic systems (for example Ubuntu Notebook, Ubuntu Netbook, Ubuntu Cube PC, Ubuntu Workstation) with Simple Names (Not like Manufacturer X ELGX-423544ES) and good design.

Example:

http://usrnametaken.deviantart.com/art/UbuntuBOX-211559873

So please Ubuntu, be a non-DRM-fanatic, free and OpenSource Apple.

Ubuntu should search for a hardware manufacturer, to manufacture Ubuntu-"All-in-One" PCs that just work and distribute them via store.ubuntu.com. Do it like Apple (or Google ChromeOS), provide a few basic systems (for example Ubuntu Notebook, Ubuntu Netbook, Ubuntu Cube PC, Ubuntu Workstation) with Simple Names (Not like Manufacturer X ELGX-423544ES) and good design. Example: http://usrnametaken.deviantart.com/art/UbuntuBOX-211559873 So please Ubuntu, be a non-DRM-fanatic, free and OpenSource Apple.

Written by DeMus the 1 Nov 09 at 08:02.

See above.

Place all the Grub related files and folders in the /boot folder again. Now with grub2 they are also in /etc and subfolders thereof.
When using a RAID it is easy to keep /boot as a separate partition out of the RAID and all other folders inside the RAID. Now since also /etc holds important bootfiles it is much more difficult to work with a RAID.

See above. Place all the Grub related files and folders in the /boot folder again. Now with grub2 they are also in /etc and subfolders thereof. When using a RAID it is easy to keep /boot as a separate partition out of the RAID and all other folders inside the RAID. Now since also /etc holds important bootfiles it is much more difficult to work with a RAID.

Written by dstansby the 1 Nov 09 at 10:20.

Instead of tying users down to Grub 2, I think we should have a setting in the advanced options so you can choose your bootloader. I should be set as Grub 2 default though, so normal users use the latest version.

Instead of tying users down to Grub 2, I think we should have a setting in the advanced options so you can choose your bootloader. I should be set as Grub 2 default though, so normal users use the latest version.

Written by robinparriath the 3 Nov 09 at 07:25.

This would help in reducing the complaints. Startup manager already allows us to select the default OS to boot.

The additional capabilities it needs is:
- Editing the entries ( names like Ubuntu, Linux kernel xx.xx.xx is good, but I like Karmic Koala better
- Splash screen! This is one feature of Grub legacy, that I miss a lot. Okay, if it's available in Grub2, I just don't know how to configure it. GUI please

That's my list. Its just that I don't think going back to Grub legacy is wise. Sometimes, the 1-2 seconds of boot time can be better utilized elsewhere :)

This would help in reducing the complaints. Startup manager already allows us to select the default OS to boot. The additional capabilities it needs is: - Editing the entries ( names like Ubuntu, Linux kernel xx.xx.xx is good, but I like Karmic Koala better - Splash screen! This is one feature of Grub legacy, that I miss a lot. Okay, if it's available in Grub2, I just don't know how to configure it. GUI please That's my list. Its just that I don't think going back to Grub legacy is wise. Sometimes, the 1-2 seconds of boot time can be better utilized elsewhere :)

Written by dwfinley the 5 Dec 09 at 00:32.

Grub2 is fun for geeks and a trap for others. When users create a second system or add a second disk, Grub2 wrecks everything as soon as the new system fails or is removed. Give users an option of installing an invisible bootloader that doesn't grab everything in sight and deliberately prevent recovery. Most users are happy to select a boot drive in the bios.

Grub2 is fun for geeks and a trap for others. When users create a second system or add a second disk, Grub2 wrecks everything as soon as the new system fails or is removed. Give users an option of installing an invisible bootloader that doesn't grab everything in sight and deliberately prevent recovery. Most users are happy to select a boot drive in the bios.

Written by ccsidea the 30 Aug 10 at 03:27.

Make a Grub that can be installed stand alone from a disk
to make a boot menu similar to GAG. Let it find Windows,
Dos or whatever and be able to boot into any Linux system.

Finding the required files on there partitions.

That way if Windows breaks and needs reinstalling you
don't loose linux too, because you can just install a
boot on the MBR that can access any other OS.

Make a Grub that can be installed stand alone from a disk to make a boot menu similar to GAG. Let it find Windows, Dos or whatever and be able to boot into any Linux system. Finding the required files on there partitions. That way if Windows breaks and needs reinstalling you don't loose linux too, because you can just install a boot on the MBR that can access any other OS.