/srv/irclogs.ubuntu.com/2008/09/13/#ubuntu-mobile.txt

matteohi all00:09
matteowhat are tha lpia compiler flags?00:11
=== ALo is now known as ALoGeNo
=== foka_ is now known as foka
persiachuck: A couple people have tried it on the EeePC : general consensus is the 1) It takes a *long* time to install without feedback, and 2) the EeePC is not a MID.  Look for Ubuntu Mobile in intrepid.02:18
persiaian_brasil: -monitor stdio puts the KVM monitor in the shell from which you launched KVM, which can give you useful metacontrol of your instance.02:18
ian_brasilpersia: ok thanks02:21
ian_brasilre-rolling the squashfs makes the hd work for its money ;)03:11
persiaian_brasil: /tmp on tmpfs can help with that.03:11
persiaAlso, the 20080913 image appears to have suffered a mishap, so one still can't install (although it's usable as a live image).03:12
ian_brasili don't understand03:12
persiaI added the following to /etc/fstab:03:13
persiatmpfs /tmp tmpfs nodev,nosuid 0 003:13
ian_brasilah,ok03:14
persiaWhat that does it create a /tmp that is half the size of physical RAM, and anything stored in /tmp goes to RAM.  In practice, much of it ends up being committed to swap, but it means that it only gets written to disk when the space in /tmp exceeds the cache buffers, rather than immediately, which can speed up operations on temporary files for machines with slower access to secondary storage (not SSD)03:14
persia(or even not 10K drives - just having a 7200, 5400, or slower drive makes this a win)03:15
persiaOf course, the downside is that one wants to clean up /tmp to hibernate, and it's in RAM, so if one is short RAM, it may limit the size of what one can put in /tmp.03:15
ian_brasili will try that for sure. its a good job you are always here and don't sleep much persia ;)03:19
persiaian_brasil: I do sleep.  That's why it took me so long to answer your question about -monitor.03:19
ian_brasilok..well thanks anyway03:23
ian_brasildamn, out of space again03:26
ian_brasilit is annoying that it gets right to the end before this error03:27
persiaIt's hard to know how well the chroot will compress in advance, and when it copies the squashfs, there might just not be enough room.03:28
persiaAlso, still out of space after running apt-get clean?  Is this a different issue?03:29
persiaLastly, do you have firefox installed?  Some of the earlier images did, and you might be able to remove it to regain space.03:29
ian_brasili will try and remove firefox03:31
persiaYou might also install deborphan and see what else can be dropped.  Alternately pull a new image :)03:33
ian_brasili think the space issue is going to cause a lot of confusion/questions..i think i will write a wiki page about this at some point03:48
persiaProbably best if you just mention it as a warning on the current wiki page.  I think you are the primary user of this now: ogra and I have used it some, but not to the extent you use it.03:54
ian_brasilOK..space is a concern in order that the image fits on a 512MB pen drive , right?03:56
ian_brasiljust want to clarify this03:56
persiaWell, it's of interest to me, as I only have one pen drive > 512M, but they sell them at the corner store here, so it's not essential or anything.03:59
persiaAnyway, the current images are well over 512M, so since that criteria hasn't been met, it's not worth trying to enforce it unless you have a good idea about which packages we would do better without, and we can try to find out why they are being installed.04:00
ian_brasili am asking why is there the 20MB additional size limit when you are working inside the chroot...i missed that part of the conversation earlier04:04
persiaian_brasil: It's just an arbitrary number.04:05
persiaEssentially, the VFAT image needs enough extra space to hold the kernel, the manifests, the preseeding, and the boot configuration files.04:05
persia20M was determined as a number that would probably handle all that without much fuss.04:06
persiaAfter the images were available, ogra put together the image-editing script, which opened new possibilities.04:06
persiaAt this point, it's a matter of debate whether the image should contain more empty space (longer downloads, but more flexible) or stay small.04:06
persiaPersonally, I think it's better to stay small, and upgrade an installed system, but that's currently blocked on https://launchpad.net/ubuntu/+source/debian-installer/20080522ubuntu14/+build/71583804:07
ian_brasilah i understand now04:07
persiaWith luck, the image generated in ~21 hours will work for installs.  If not, I'm 100% certain the image generated in ~69 hours will allow installs.04:08
persia(I very much suspect the image generated in ~45 hours will be identical to the one in ~21 hours)04:09
ian_brasili am in the camp of longer downloads with more space...with this you can make a larger theme and customize more for an OEM04:13
persiaian_brasil: I guess, but I'd suspect most OEMs would prefer the even greater flexibility of generating the images themselves.04:14
persiaTo do that, just use the squashfs-editing portion of the image-editor script, and then create a VFAT image of sufficient size, and stuff in the squashfs, kernel, preseeds (likely different for OEMs anyway), manifests (also likely different for replicable installs), and boot hints.04:15
persiasyslinux the VFAT image, and you're done.04:16
persiaThe key part here is that the OEM likely wants to change the preseeds and manifests to change the way the install works.04:16
persiaFor someone just playing around, adding a couple packages to the image works.  This is also very important when testing changes to enable new hardware.04:17
persiaFor hardware enablement, once it's complete, I'd hope to get support into the official images.04:17
persiaFor installing a couple fun packages that someone always uses, 20M (or maybe 30M) ought be enough.  Too much size makes latency *very* painful for those of us with long-haul connections to cdimage.ubuntu.com04:18
persiaAlso, for folk with download caps, an extra 100M every few days can add up quickly to a 2G or 3G ceiling.04:18
ian_brasilI suppose this depends to a certain extent on the OEM. In my experience some do not want to get involved in this level of customization...they just ask can I put my own applications and my own theme on ume...a quick and easy way to do enable this to happen could give this sector a good kickstart...maybe a community maintained larger vfat image might work for this? 04:31
persiaian_brasil: Could be, although I'd think putting together a script to expand the VFAT is probably easier, both to maintain, and to get hosted.04:33
persiaI'm thinking just something that takes an existing .img as an argument, and a second argument that says how much space to add.  It then creates a VFAT that is the desired amount larger, and copies in the contents, for later use with the image editor.04:33
persiaDoes that sound useful to you>04:34
persias/>/?/04:34
ian_brasilthat sounds extremely useful to me04:36
persiaIt's also not that big, and reusable.04:37
ian_brasiland a much better idea than big downloads04:37
persiaI'm chasing a few other things today, but if you've time to put something together, I'm happy to test, or act as a sounding board if you want to talk through something.04:38
ian_brasilok...i will try to hack something up this weekend for that04:38
persiaian_brasil: Oh, right, it's still Friday night for you :)04:40
ian_brasilyes, talking of which it is time to sleep! thanks again for the advice04:42
persiaHave a good night.04:44
=== asac_ is now known as asac
crevettehey people16:43
crevettejust a dumb question, bluez 4 is not targeted for intrepid?16:43
=== Snookie is now known as Guest83413
=== foka_ is now known as foka
=== Snookie is now known as Guest83869
=== Guest83869 is now known as snookie
=== snookie is now known as Guest82291
=== Guest82291 is now known as snookie
=== snookie is now known as Guest94106
=== Snookie is now known as Guest96899
=== Guest96899 is now known as snookie
=== snookie is now known as Guest11420
=== Guest11420 is now known as snookie2

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!