[00:06] <N1ghtCrawler> cjwatson: I have finally found the file, but it's sort of empty.. Only containing "Set -e <newrow> cdrom-checker"
[00:08] <N1ghtCrawler> nevermind again..
[00:08] <N1ghtCrawler> Looking in wrong file..
[00:29] <N1ghtCrawler> I think i fount where he mounts the cdrom now.
[00:30] <N1ghtCrawler> manualtime!
[00:32] <N1ghtCrawler> if i understand the thing rigt to use mount --bind i have to mount the cd first. Then mount --bind /cdrom/ubuntu /cdrom?
[00:34] <N1ghtCrawler> can i simply do "<original mount command && mount --bind /cdrom/ubuntu /cdrom?
[01:19] <N1ghtCrawler> WHOW! It seemed to work!
[08:10] <cjwatson> N1ghtCrawler: that's what I was thinking, though it's a bit of a guess. It'd probably be a good idea to change /usr/lib/finish-install.d/15cdrom-detect to umount /cdrom twice as well.
[11:49] <marchino> ciao! i'm trying to install ubuntu from an usbdrive but i get "no installer iso image were found"
[11:49] <marchino> the iso image is mounted in /cdrom
[21:34] <blahblahx> I have made my own distro based off ubuntu 7.10. when you run the test iso, ubiquity seems to act funny. if you choose a language other than english to install with, then after install you get the error "language failed with exit code 127". However, the language is installed and works, just I can't figure out why the error pops up. What does it mean?
[21:51] <blahblahx> anyone?
[21:58] <blahblahx> awesome
[21:59] <binarical-app> so yeah your post is kinda the same as what you were saying in there
[21:59] <binarical-app> why dont you just work around it .... ignore it
[21:59] <blahblahx> well im developing under someone else who wants that to be fixed, plus, that kinda thing looks bad in a distro
[22:00] <blahblahx> you know about linux mint? i am making a community version of it
[22:00] <binarical-app> you could edit some files, uncomment the specific error output
[22:00] <blahblahx> how so?
[22:01] <binarical-app> well for each kind of configuration or language there is a method (especially in open source ) to edit your own stuff
[22:02] <blahblahx> not completely following you
[22:03] <binarical-app> the program has many functions built into it, if your solution to the problem of "developing software" is simply to get an error to shut up then, disable the error option
[22:03] <blahblahx> like i want to make some change (be it editing a file or installing something) so that this doesn't come up
[22:03] <binarical-app> thats pretty general
[22:03] <binarical-app> but your gonna have to digg it yourself man
[22:04] <binarical-app> if you want to get into that nitty gritty, then you have to find someone who either knows, like the developers or , some other genius
[22:04] <blahblahx> wait i got more info
[22:06] <blahblahx> as soon as i open ubiquity and click to begin it, the error pops up. it says, "language failed with exit code 127. further information may be found in /var/log/syslog. Do you want to try running this step before continuing? If you do not, your installation may fail entirely or may be broken.".
[22:07] <binarical-app> what is in var/log/syslog .....can you read the output please
[22:08] <blahblahx> on the livecd?
[22:08] <binarical-app> are you developing?
[22:09] <binarical-app> look man there are alot of wikis on how to make your own this and your own that, sometimes if you wanna have fun and experiment then go ahead and give those things a shot
[22:09] <blahblahx> ill be back in a bit sorry
[22:13] <binarical-app> does he even know what a bug report is?
[22:43]  * binarical-app dons the Dunc cap