I'm fortunate to have several systems. I've noticed that the standard generic kernels have one common feature amongst all the system's I've loaded it on. They run approximately 60% of full potential and even seems to fatigue on moderate system load.
I just took a look at the 10.04 Beta today, and I realized that the Examples folder ( with the logo, video, and audio clips) is sorely outdated. The logos are not the same as they are today ( old font ) and the video is very low-quality, and ends with the song information, with the title of 'Pornstar'.
Because netbooks are machines that are made for a very specific task that is quite different from 'normal' desktop use, there are several programs installed that 95% or even 100% of the users will not use. For example:
- Brasero. I'm pretty sure that almost nobody uses his netbook to burn cd's.
- XSane Image Scanner.
- Assistive Technologies. The size of the devices doesnt make it very accessable for the less capable.
- PalmOS Tools. Who does even use a palm these days anyway?
Written by andremachado the 26 Mar 10 at 23:09.
New
Currently, there is a huge effort to made Ubuntu boot faster, but the great issue is what, when Ubuntu - as well as other Linux distros - boots up, it loads many services to support a large variety of hardwares and configurations.
That is convenient for end user what can, for example, easily, connect a printer and work with it immediatelly. BUT, if user have not a printer, Cups, the Linux printer server, will be loaded and stay occupying system memory in vain, because it will never be used. Similarly, if user wants print only one document and save your energy, if he turns on his printer for just do it and turn it off after, Cups will continue in memory.
Written by Nunslaughter the 16 Mar 08 at 16:12.
New
To me, the loud intro sound and system beep are very annoying on the LiveCD!
It happened a couple of times that I used the LiveCD in the middle of the night on my notebook, and the loud intro sound and system beep at shutdown are just very annoying if there are other people sleeping in the same room or even home.
Or even if it isn't at night, these sounds are useless and you can't adjust the volume before the intro. Maybe delete the system beep and lower the volume of the intro?
The Ubuntu installation process could use more idiot-proofing with respect to checking that the Minimum System Requirements are being met BEFORE the end user gets into a frustrating situation that completely "turns them off" from Ubuntu (before they can even install it).
Namely: what if a novice user gets an Ubuntu Desktop install CD, but the Live CD grinds to a painful, eternal stall because there is not enough RAM, or the CPU is too slow?
These users wouldn't know what to do next if their computer froze on them: is their computer broken? Who is to be blamed? Themselves (making a wrong choice)? Their hardware? Ubuntu? Who? Most users haven't got any sort of troubleshooting skills or experience to narrow this down, and could very likely just give up, which would be a shame.
They should be warned about any basic hardware inadequacy BEFORE X windows starts, and they should be gracefully pointed towards doing the right thing if necessary: locating (on the internet), and downloading, and booting from the Alternate Installation CD instead.
A timely, simple script on the Live CD (run at boot time) that checks the current hardware, then prints a helpful text message on the console if necessary (halting further booting) would go a long way to saving these users a lot of frustration!
This relatively simple fix would go a long way towards making Ubuntu more "humane."
Most users installing Ubuntu will by default attempt to install from the Live CD (Desktop version). But for people with older computers that do not meet the Minimum System Requirements, they are currently expected to be technically knowledgeable enough to intelligently choose the right kind of installation CD first: Desktop Version or Alternate Installation CD.
This could be a huge stumbling block to A HUGE NUMBER of potentially new Ubuntu users, who are such novices that:
-they never RTFM, (namely https://help.ubuntu.com/community/Installation/SystemRequirements ) and know that they should instead install from the "Alternate Installer." Moreover, these novice users don't even know what RTFM means. It would be prudent to assume that must users DO NOT READ ANY DOCUMENTATION WHATSOEVER before they attempt to use the Live CD.
Currently, when installing Ubuntu, we can't tell whether the hardware will be recognized and supported until the installation is over, or by digging through incomplete on-line documentations.
Why not create a Wizard, that will be run-able from either the Live-CD or Wubi, that will detect the hardware, and report what works?
This way we can avoid frustrating users that will discover post install that their video card is black listed (so Compiz doesn't work), having compatibility problems with several chipsets (like jmicron), non-working web cams, unsupported multi-monitor setups, etc.
When you know in advance what you're facing, it is easier to cope, instead of wasting time and discovering after the fact that the hardware is not fully supported.
for example:
Running the hardware wizard from Wubi on my main machine will yield the following result (based on my actual experience installing Hardy):
Hardware discovered:
(X) motherboard: MSI Neo 965 - known problem - unsupported jMicron chipset, the system will not be bootable.
(V) Video card: Nvidia 8800gts 320mb - hardware support is available.
(X) Dual screens: Dual screens are not properly supported using the propriety nvidia drivers.
(X) Printer: Epson pixma ip1500 - printer is not supported.
(V) scanner: HP (something) - supported.
(X) Webcam: Samsung (something) - webcam not supported.
(V) iPod : supported.
(V) Palm Pilot m505: supported.
On my laptop:
(V) Motherboard: compal (something) Supported.
USB memory devices are very frequently badly pre-formatted, so that it is impossible to successfully create a bootable USB disk, unless the device is re-formatted.
Examples I have seen:-
- use of "superfloppy" format, rather than partitioned
- no MBR boot code
- ancient (e.g. Windows 95) MBR boot code that has difficulty on modern hardware
- incorrect partition maps (LBA differs from CHS values)
- "bootable" partition flag omitted
- "bootable" partition flag set to bad value (0x70)
- sector size not 512 bytes (this can't be fixed by reformatting)
- odd CHS geometry that causes problems with some BIOS code
- use of U3 or similar devices with extra "CD-ROM" partition
- partition type in MBR differs from actual filesystem type
gparted is a good graphical tool that allows the user to create/delete/modify/move partitions easily. partimage is a tool that allows users to backup and restore partitions to/from compressed image files.
To me it makes sense to merge the functionality of partimage into gparted to create one unified tool for management of partitions.
This enhanced gparted would add valuable functionality to the LiveCD - the ability to backup a known good installation before "nuking" it.
Use-case:
Joe Schmoe buys a laptop from large retailer PCs-R-Us. The laptop comes pre-configured with Windows, however an install CD is not provided - instead an installer is provided on a hidden partition. Joe wants to install his favourite Linux distribution, but first wants to backup an image of his hard drive, just in case he should need to restore it later.
Joe could use the enhanced gparted tool on the Ubuntu LiveCD to make a backup image of his system (saving this image to a DVD or external drive), then nuke the drive ready for the Ubuntu install.
Joe now has the ability to revert back to the factory configuration should he, for any reason, decide to do so.