/srv/irclogs.ubuntu.com/2008/03/18/#ubuntu-installer.txt

superm1cjwatson, something about that still doesn't click though to me.  If the installer favors setting up an extended partition with logical partitions, how do you boot to them?  If you let the DOS MBR stick, it, can't have an active extended partition..?00:03
cjwatsonthat only applies if the user deliberately asks for the boot loader to be put on a logical partition00:04
cjwatsonby default, we put it in the MBR00:04
cjwatsonand the BIOS (only some BIOSes, at that) only cares that there exists a bootable primary partition - it doesn't have to be the one you end up chaining to00:05
superm1ah well then we are going to need to wander down the path of a partition recipe instead00:05
superm1support was added in for such recipes to ubiquity this cycle, correct?00:06
cjwatsonhas been there since automation in general was added in gutsy00:06
cjwatsondoes the DOS MBR really refuse to boot from a logical partition?00:06
cjwatsoncan it boot from an extended partition instead? you can install GRUB there00:07
superm1yeah.  I putzed around with it for a bit this afternoon until michael_e_brown indicated that to me and it made sense00:07
michael_e_brownhey00:07
cjwatsonerr, I think00:07
cjwatsonmaybe not00:07
* michael_e_brown catches up00:07
cjwatsonbut, yeah, if you're using a boot loader that can't deal with it, it's totally reasonable to force the partition to be primary in your recipe00:07
michael_e_browncjwatson, we have DOS MBR, which cannot chain to a partition PBR in an extended partition00:08
superm1and with the way the factory process handles things, it will *have* to be a dos mbr.00:08
michael_e_browncjwatson, previously, partman put / on primary sda300:08
michael_e_browncjwatson, but now for some reason, it is putting / (and, by extension, /boot) on logical partition00:09
cjwatsonI know, I made the change00:09
cjwatsonit makes much more sense for just about all other boot loader arrangements00:09
michael_e_browncjwatson, so does automatic ubiquity now support using recipes for partman?00:09
cjwatson00:06 <cjwatson> has been there since automation in general was added in gutsy00:09
cjwatsonthat didn't need anything special, it's just a standard consequence of using partman-auto00:09
michael_e_brownok. didnt know that.00:10
cjwatsonweakening the primary partition constraint on / makes certain partitioning scenarios a lot simpler00:11
superm1i'll put together a recipe then and give a run tomorrow morning with that00:11
michael_e_browncjwatson, the problem is that /boot needs to be on a primary00:11
cjwatsonthe PC partition table format is very restrictive with regard to primary partitions; it caused practical problems, for instance, with standard auto-resize installs of Ubuntu on stock Dell machines00:11
cjwatsonno, that is not true in general00:12
cjwatsonit is true if you're chaining from DOS MBR00:12
michael_e_brownin our specific case.\00:12
cjwatsonbut if you're using GRUB in the MBR (the standard Ubuntu approach) it's not the case00:12
michael_e_brownunderstood.00:12
cjwatsonin your case, overriding the standard partition recipes with a custom one is definitely reasonable00:13
cjwatsonand I'll have a think about whether we can support DOS MBR in a more inline fashion00:13
michael_e_browncjwatson, it isnt a big deal if we can do a recipe which superm1 is working on00:13
cjwatsonright, should be dead easy00:13
superm1well i'll do it tonight before i head to bed at least.  dinner for now :)00:14
=== ebel_ is now known as ebel
rajucjwatson, i am getting error while booting the live cd ( which i created based on the docs given in ubuntu )04:58
rajucjwatson, error is like "/bin/sh can't access tty ; job control turned off"05:00
rajui took the gutsy livecd of 22 kernel05:01
=== superm1_ is now known as superm1
CIA-24ubiquity: cjwatson * r2571 ubiquity/ (debian/changelog ubiquity/components/language.py): * Run fontconfig-voodoo as root (LP: #203086).10:31
=== cjwatson_ is now known as cjwatson
=== cjwatson_ is now known as cjwatson
CIA-24ubiquity: evand * r2572 ubiquity/ (debian/changelog ubiquity/frontend/noninteractive.py):14:42
CIA-24ubiquity: * Properly return in debconf progress functions in the noninteractive14:42
CIA-24ubiquity:  frontend. Thanks Colin Watson.14:42
CIA-24ubiquity: * Print progress updates on a new line again in the noninteractive14:42
CIA-24ubiquity:  frontend.14:42
evandsuperm1: ^14:42
superm1evand, fixing packages installation? :)14:43
evandThat will fix the apt not finding packages on the CD bug.14:43
superm1oh just progress14:43
superm1that's still great14:43
superm1probably resolves the 1000 percent bug14:43
evandprobably not actually, I imagine that bug relates to my lack of use of some of the other progress bits.  But I will fix that, it's on my list, it's just not as high a priority as some of the other items.14:44
evandsuperm1: but r2572 definitely fixes installing oem-config for me.14:44
superm1very good.  we'll be able to preseed languages and such then again too14:46
superm1thanks for tracking that one down.14:47
* superm1 pulls updates to see what in the devil this fix actually ended up being :)14:47
evandsuperm1: cjwatson is definitely the one to thank on this one.14:48
superm1thanks a bunch cjwatson :)14:49
cjwatsonsuperm1: I suspect (and this is just zen debugging) that the reason it broke was that the incorrect implementations of progress functions caused the progress bar to be cancelled, which maps to status 30 from any of the db_progress command14:49
cjwatsons14:49
cjwatsonwhich would probably cause things to bail out14:49
superm1interesting that without a progress bar it bails though?14:50
superm1i didn't realize it was so dependent14:50
cjwatsonthere's still a progress bar under the hood, even if it isn't displayed14:50
cjwatsonit's calling db_progress, and the frontend is setting up the internal structures and replying appropriately14:50
cjwatsonit just wasn't stubbed out in quite the right way14:50
superm1ah14:50
superm1with the beta coming up, assuming we run into no more issues with noninteractive, will you guys be building a DVD at beta time?14:51
cjwatsonI'd expect so, although whether it gets tagged as beta depends on whether we manage to get testing for it14:55
superm1okay well if it goes in a day or two after beta that's fine, just so long as we can have a dvd mastered with a collection of these fixes so we can get all the testing with language packages preseeded and such in14:58
cjwatsonthere should be an n-daily DVD build at the very least15:10
mario_limonciellevand, preseed files get loaded on the fly when ubiquity/d-i starts, not at boot, right?  They are just "specified" from the kernel command line18:00
evandmario_limonciell: no, they get loaded as part of casper18:03
mario_limonciellevand, oh that would explain why my changes weren't looking like they took effect with each run :)18:04
evandscripts/casper-bottom/24preseed18:04
evandheh18:04
mario_limonciellcan i rerun that script after the OS is started to reseed?18:04
evandI generally just cat seed | debconf-set-selections18:04
mario_limonciellokay that will do18:04
mario_limonciellthanks18:04
evandyou're welcome18:04
mario_limonciellevand, out of curiosity, if you preseed an expert recipe, would it actually show up on the page where you select partitioning layouts?18:16
CIA-24ubiquity: evand * r2573 ubiquity/ (debian/changelog ubiquity/frontend/gtk_ui.py):18:20
CIA-24ubiquity: * When clicking back from the advanced partitioner, go back to the first18:20
CIA-24ubiquity:  partitioning page rather than the keyboard page. Thanks Jonathan18:20
CIA-24ubiquity:  Riddell.18:20
evandmario_limonciell: no, not unless you ran ubiquity with --automatic, but then it would skip the page entirely.18:23
evandwell, skip the UI portion of the page18:23
evandit still runs the d-i code18:23
mario_limoncielloh i see18:24
mario_limonciellokay curiosity number 2: if it's just running the d-i code,  would it be possible to preseed say a LVM install provided all the right debconf variables are set?18:26
evandno, because ubiquity sucks in only the d-i components it actually uses18:27
evandand partman-lvm is not among them18:27
mario_limoncielloh boo :(18:27
mario_limonciellthat would have been a really neat workaround to use18:27
evandheh, sorry18:27
evandpossibly Intrepid, but we'll find out for sure in May.18:27
mario_limonciellit would really only have benefited on the systems that we were going to do dm-raid on18:28
mario_limonciellsince dm-raid fell through and all18:28
mario_limonciellso not a big loss18:28
evandah, I was just going to say18:28
mebrownmario_limonciell, ping18:42
mebrownmario_limonciell, nm...18:46
CIA-24ubiquity: evand * r2574 ubiquity/bin/ubiquity: Typo19:03
mario_limonciellmebrown, hey i'm here19:07
mebrownis there a way to manually mount a partition from the cmdline but supress the automount message that pops up in gnome?20:39
mebrowneg. when I mount the Dell reinstallation partition on /dev/sda2, it pops up an autorun dialog20:39
evandmebrown: see bug 19912920:40
ubotuLaunchpad bug 199129 in ubiquity "Auto-resize install fails to mount drive" [Undecided,New] https://launchpad.net/bugs/19912920:40
evandhttps://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/199129/comments/9 specifically might work20:41
ubotuLaunchpad bug 199129 in ubiquity "Auto-resize install fails to mount drive" [Undecided,New]20:41
evandotherwise you can play whack-a-mole on the nautilus/gnome-vfs gconf keys like we've been doing in ubiquity20:41
mebrownhmm... thanks20:42
mebrownI'll try it.20:42
mebrownevand, not complaining, just think it is funny that this is the cmdline in my .desktop file for this:20:43
mebrownExec=gnome-terminal --hide-menubar -x sudo sudo hal-lock --interface org.freedesktop.Hal.Device.Storage --exclusive --run /bin/bash /usr/local/bin/make-dvd.sh20:43
mebrowngnome terminal runs sudo which runs hal-lock which runs /bin/bash which runs my script20:43
mebrownthat's *almost* longer than my script20:43
mebrown:)20:43
evandlol20:43
mebrownevand, doesnt appear to work for me21:01
mebrownevand, this is running on a full desktop after install21:01
evandIs that double sudo a pasting error?21:01
evandI don't think run lets you pass arguments21:03
mebrownevand, I messed that up. but it still doesnt work after fixing21:03
evandI'd get rid of the /bin/bash.21:03
mebrownah.21:05
mebrownI get it.21:05
mebrownappears to work. thanks!21:06
mebrownputting quotes around the cmd also works21:06
evandmebrown: you're welcome21:06
mebrowndoh.21:06
evandah, good call21:06
mebrownthe window popped up again21:06
mebrownjust took a few more seconds21:06
evandargh21:06
evandhrm21:07
mebrownExec=gnome-terminal --hide-menubar -x sudo hal-lock --interface org.freedesktop.Hal.Device.Storage --exclusive --run "/bin/bash /usr/local/bin/make-dvd.sh"21:08
mebrownthats what I have so far.21:08
mebrownit runs, but it obviously doesnt lock something21:08
mebrownas I get an autorun dialog21:08
mebrownWell, a partial solution: delete the autorun.inf. Problem is that I still get a nautilus browser popup.21:10
evandSo the alternative solution is to unset the appropriate gconf keys and then set them back when you're done running.  These would be...21:13
evand /desktop/gnome/volume_manager/automount_drives, /desktop/gnome/volume_manager/automount_media, /apps/nautilus/desktop/volumes_visible, /apps/nautilus/preferences/media_automount, /apps/nautilus/preferences/media_automount_open21:14
evandit's ugly and GNOME has a habit of changing these on us.21:14
mebrownhmm...21:14
evandstill trying to figure out why hal-lock wont work though21:14
evandas that seems to be the most elegant solution21:14
mebrownthe autorun dialog was a complete showstopper as users will invariably click the wrong thing.21:15
mebrownsince I've gotten it to just a nautilus popup, that *may* be sufficient for now21:15
mebrown(esp. since nautilus goes away when the DVD create is finished)21:15
xivulonwhat is the status of bug #8497 ? I see it has been marked as fixed upstream21:40
ubotuLaunchpad bug 8497 in grub "grub guessed BIOS disk order incorrectly" [Medium,Confirmed] https://launchpad.net/bugs/849721:40
michael_e_brown_shouldnt grub use EDD so it doesnt have to guess?21:57
TheMusoWhat is everybody's thoughts on disabling the running of pulseaudio in only-ubiquity mode? Speech doesn't rely on it, so it can do without it, and I've tested code here that disables it successfully.21:57
TheMusoPulseaudio is only run because of gnome-settings-daemon honouring gconf values.21:58
michael_e_brown_no screen reader for ubiquity?21:59
TheMusomichael_e_brown_: Not quite. What I'm saying is that the screen reader's speech output component can work with or without pulseaudio, so its pointless to run pulseaudio just for that, and most people won't be using speech anyway.22:00
michael_e_brown_ah22:00
michael_e_brown_makes sense, i suppose22:00
TheMusoSo even now when you boot only-ubiquity, pulseaudio is running, whether you know it or not.22:00
mario_limonciellTheMuso, well what's the advantage of going through that effort to do it though?22:03
mario_limonciella 1-3 meg memory savings?22:03
TheMusomario_limonciell: Yes, I was expecting this to be raised. :)22:04
mario_limonciellit may be useful to keep in place especially if ubiquity-slideshow ever materializes.  but to that same level its easy to add back22:04
michael_e_brown_just for reference, every meg helps22:04
michael_e_brown_on my PS3 with 200MB of RAM, current state of gutsy is sad22:05
mario_limonciellmichael_e_brown, well ppc already has it's fair share of "kill me processes" :)22:05
TheMusoThe only other issue that needs resolving for speech to work now, is for the ubiquity-dm session to be able to refresh knowledge of groups via pam or whatever it does, so that the ubuntu user can actually talk to the audio device.22:05
armandhello y a des gens22:53

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