Re: Feature suggestions: optionally placing home folder into separate partition during ubuntu install
That is a common misconception. Reinstalling Ubuntu on the same partition doesn't lose the user's data either. A problem that is both real and more interesting, is working out why so many people have that misconception, and how we can correct it. Is this really a misconception? I thought there was a point in time that you did need to have a separate /home for what we are talking about. You needed a separate home for that until Hardy, if memory servers. So it's not an ancient feature, but it's not exactly new at this point either. Also, do you know how widespread the policy is? ie, is it Ubuntu only, debian based distros, or all of linux? I have no idea. I imagine it's part of Ubiquity, not debian-installer, which would make it Ubuntu-specific. I imagine you would have to make it part of the gui of whatever installer supports it if you wanted more people to use the feature. Otherwise, it is a bit too complicated to communicate to people. You can't really expect people to follow every precise direction you give them, and in this case if they don't, they could loose their data. Maybe you could put a button that offers to reuse an existing partition layout, clean installing but saving use data. The button could go next to the install side by side and use entire disk options and maybe scan fstab for the partition layout. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: LiveCD optimisations
Hello Louis, Louis Simard [2010-11-01 17:10 -0400]: AdvanceCOMP is packaged in maverick universe as advancecomp. jpegoptim is packaged in maverick universe as jpegoptim. Could these programs be added to the build scripts, or would that be discouraged since they're in universe? Would these optimisations be a case for inclusion into main? Yes, of course. I added some work items for advancecomp and jpegoptim to the spec. Thanks! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: More LiveCD space optimizations
John McCabe-Dansted [2010-10-08 0:07 +0800]: We could test each file to ensure the image is identical, perhaps using pngtopnm, and md5sum. This would be especially important for jpegrescan/jpgcrush, which is at version 0.0.0-1. I use a simple test script for this kind of check, see https://bugs.launchpad.net/ubuntu/+source/advancecomp/+bug/671599/comments/1 Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: More LiveCD space optimizations
On 10/08/2010 04:54 AM, Matthias Klose wrote: [ compression related discussion removed ] So maybe we can save some MB with better compression, but we can save more by not including files at all. Of course this requires inspection of the packages included on the liveCD. In the past we did identify some issues and did add some diagnostics to the live CD build logs [1]. Of course you can't run anything and lengthen the live CD build, but some additional diagnostics maybe could be run. In the past we did see wasted space: snip / - firefox and xulrunner shipping duplicate .js files Well, Firefox is no longer built on top of xulrunner, so this is necessary, especially with the PGO optimizations if we can get them. If webkit has sufficient accessibility and we can port yelp to webkit, we can drop xulrunner from the CD. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
