[02:55] <jetole> Hey guys. Does anyone know how to see all options of a d-i line in preseed. For example, right now I am looking at d-i partman-auto/init_automatically_partition and I don't know what possible values I can place there are
[09:57] <maxagaz> can I send a file in attachment with the command mail ?
[12:09] <corecode_> jetole: you'll have to look at the template file
[12:10] <jetole> corecode_: where can I find the template file?
[12:10] <corecode_> in the packages
[12:10] <corecode_> it is a pain
[12:10] <corecode_> i'm always looking in the d-i svn
[12:11] <jetole> grrrrr
[12:12] <jetole> Well I solved the issue I was having with preseed and don't need but thought it would be worth looking into. If you say it's a pain and since I don't _need_ it then for now I will pass
[12:12] <jetole> thanks for the insight though
[12:13] <jetole> right now I am trying to figure out how to get puppet to run after preseed since in 10.04 it's told not to run by default as per /etc/default/puppet
[12:13] <corecode_> what is puppet?
[12:13] <corecode_> i have a line:
[12:14] <corecode_> d-i preseed/late_command string preseed_fetch customize_install.sh /target/tmp/customize_install.sh && in-target sh /tmp/customize_install.sh
[12:15] <jetole> I have no idea what that line does. Puppet is a systems config tools aimed at clusters. a puppet client connects to puppet master and puppet master tells the system how to be configured
[12:16] <jetole> i.e. always run this service. Make sure this file exists, restart this service if this file changes, make sure this user exists and is part of said groups etc etc
[12:17] <jetole> it's similar in concept to cfengine to but newer and although not based on the cfengine code you could say improved
[12:17] <corecode_> that line downloads a shell script
[12:17] <corecode_> and runs it
[12:17] <jetole> ah
[12:17] <corecode_> after installation
[12:18] <jetole> do you know if I have sed in the installer?
[12:18] <corecode_> you mean if you use that shell script?
[12:18] <corecode_> then you're running in a chroot of the installed system
[12:18] <jetole> no I mean if sed is available inside the installer
[12:18] <corecode_> you have everything you installed
[12:18] <corecode_> likely
[12:19] <jetole> ah thats true. I was thinking just as a final command run something like "sed -e 's/^START=no$/START=yes/' -i /target/etc/default/puppet
[12:19] <jetole> but since I have it in target I can do full path to sed in the target
[12:19] <jetole> so thanks for the insight on that
[12:19] <corecode_> just use my line :)
[12:20] <jetole> Where do I get that script from and how do I customize it?
[12:20] <corecode_> you write it yourself
[12:20] <corecode_> and it downloads it from the location of the preseed.conf file
[12:20] <jetole> and I place it in the ... thats what I was about to ask
[12:21] <corecode_> the boot path looks like:
[12:21] <corecode_> append console=tty0 console=ttyS0,115200n8 auto=true priority=critical interface=auto url=http://labospc40/preseed/./lucid-preseed.cfg vga=normal initrd=lucid-installer/amd64/initrd.gz --
[12:21] <jetole> and the in-target does ... actually that looks really cool now that I'm starting to understand it
[12:21] <corecode_> the /./ says "relative to this path"
[12:22] <jetole> neat
[12:22] <jetole> very neat
[12:23] <jetole> thanks
[12:24] <corecode_> do you by any chance have an idea how i can install over a lvm system?
[12:24] <corecode_> the installer complains
[12:24] <jetole> I think enabling puppet though is the only thing I need to do. You should really check it out.
[12:24] <jetole> http://www.puppetlabs.com/
[12:24] <corecode_> yea i heard about that
[12:25] <jetole> you mean over a previously existing LVM or is it asking you to confirm writes to the partition table
[12:25] <jetole> (since I have seen both)
[12:25] <corecode_> over an existing lvm
[12:25] <corecode_> that spans multiple disks
[12:25] <corecode_> i want to kill everything and start from scratch
[12:25] <jetole> nope but I have seen it
[12:25] <corecode_> but that doesn't seem to work
[12:26] <corecode_> maybe we should grab some wiki page and document our snippets
[12:26] <jetole> I haven't actually heard of lvm over multiple disks. I mean I have heard of it but never known anyone whose tried it. Have you considered linux raid
[12:26] <jetole> ?
[12:26] <jetole> I don't think I have anything to document
[12:27] <jetole> that trick you showed me though. Yeah thats worth it
[12:27] <corecode_> what do you mean, no lvm over multiple disks
[12:27] <corecode_> that's the whole point of it, no?
[12:28] <jetole> no
[12:28] <corecode_> oh.
[12:28] <jetole> for example I use lvm on all my VM servers to dynamically create virtual disks from the storage
[12:28] <jetole> which exists on hardware raid
[12:29] <corecode_> ah, we don't have hardware raid
[12:29] <corecode_> they are just research machines
[12:29] <jetole> no but there is software raid
[12:29] <corecode_> which happen to have two disks
[12:29] <jetole> you have a few options, linear is like jbod then their is raid 10, raid5 and raid6
[12:30] <corecode_> i'm just creating one big file system from the rest of the first disk and the whole second disk
[12:30] <jetole> Yeah I used the software raid on my home workstation the other day creating a raid1 / disk mirroring out of two drives without any hardware raid suppot
[12:30] <jetole> *support
[12:30] <jetole> corecode_: yeah that sounds like linear raid from the software raid to me
[12:30] <jetole> I know it can be done via LVM
[12:30] <jetole> I just have no experience with it
[13:56] <soren> corecode_: Spanning a volume group over multiple disks is /fine/. I do it all the time.
[15:30] <jetole> Does anyone know if there is anyway in a preseed file to enable a package that debian has disabled the package via /etc/default (in this case puppet). I seem to be having some issues with the late run command and I only need one package enabled to setup the rest of my systems (puppet is config management)
[15:37] <soren> You can't do it from late_command?
[15:45] <CIA-3> libdebian-installer: cjwatson * r207 ubuntu/ (3 files in 2 dirs): merge from Debian 0.69
[15:47] <CIA-3> libdebian-installer: cjwatson * r207 ubuntu/ (3 files in 2 dirs): merge from Debian 0.69
[15:48]  * ogra wonders why that came twice
[15:51] <cjwatson> I made a mistake and uncommitted
[15:51] <ogra> ah
[15:52] <CIA-3> libdebian-installer: cjwatson * r208 ubuntu/debian/changelog: releasing version 0.69ubuntu1
[16:06] <ogra> geez, do we get grub2 bugs hourly now ?
[16:35] <ogra> hmm, the last two seem actually not to be caused by people mis-editing their /etc/default/grub file
[17:11] <corecode_> cjwatson: is there a way to make the installer killall lvm setup?
[17:12] <corecode_> cjwatson: i tried dd'ing over the drives, but the kernel doesn't refresh its information then
[17:29] <jetole> soren: here is my late_command thats failing: d-i preseed/late_command string in-target sh /bin/sed -e 's/^START=no$/START=yes/' -i /etc/default/puppet
[17:29] <cjwatson> corecode_: there's a preseed for it somewhere, I don't remember the details offhand
[17:29] <cjwatson> jetole: why are you using 'sh' there?  it seems unlikely to help and will probably hinder
[17:29] <jetole> the actual command is giving an exit status of 2 during the install
[17:30] <cjwatson> corecode_: have you checked the installation guide?
[17:30] <cjwatson> # If one of the disks that are going to be automatically partitioned
[17:30] <cjwatson> # contains an old LVM configuration, the user will normally receive a
[17:30] <cjwatson> # warning. This can be preseeded away...
[17:30] <cjwatson> d-i partman-lvm/device_remove_lvm boolean true
[17:30] <jetole> cjwatson: I have never used in-target today and thats based on me changing the command from what someone else told me
[17:30] <jetole> cjwatson: how you you rewrite that?
[17:30] <cjwatson> jetole: well, I'd just drop the 'sh /bin/'
[17:30] <cjwatson> i.e. in-target sed ...
[17:33] <jetole> cjwatson: d-i preseed/late_command string in-target sed -e 's/^START=no$/START=yes/' -i /etc/default/puppet
[17:33] <jetole> ?
[17:33] <jetole> it knows the $PATH when I use in-target?
[17:36] <cjwatson> yes
[17:36] <cjwatson> well, it will have some default path or other, but /bin will certainly be in $PATH
[17:36] <jetole> great
[17:36]  * jetole tries this now
[17:40] <jetole> cjwatson: I'm hoping this works but regardless, thanks
[17:47] <jetole> cjwatson: well so far so good. The installer finished without an error
[17:57] <corecode_> cjwatson: i have device_remove_lvm set already\
[17:58] <corecode_> must be something else
[18:05] <corecode_> Because the volume group(s) on the selected device also consist of physical volumes on other devices, it is not considered safe to remove its LVM data automatically. If you wish to use this device for partitioning, please remove its LVM data first.
[18:05] <corecode_> yea, how do i do that?
[18:06] <corecode_> i tried dd if=/dev/zero of=/dev/sda
[18:06] <corecode_> but i can't tell the kernel that the lvm is gone now
[18:13] <jetole> corecode_: afaik and I haven't looked into this thoroughly nor am I an authority but it seems the overwrite existing lvm via preseed is broken in 10.04 since how to do it is documented in the ubuntu docs for preseed for 10.04 where they give you the exact line and you are the third or fourth person + myself who I have heard this from
[18:13] <corecode_> ah
[18:14] <corecode_> thanks
[18:14] <jetole> if/when you confirm it then file a bug and hopefully it should be fixed come 10.04.1
[18:24] <corecode_> i didn't even find ubuntu preseed docs yes
[18:25] <corecode_> last time i looked they didn't exist
[18:40] <corecode_> The volume group name used to automatically partition using LVM is
[18:40] <corecode_> already in use. Lowering the priority for configuration questions
[18:40] <corecode_> will allow you to specify an alternative name.
[18:40] <corecode_> huh?
[18:41] <corecode_> something is REALLy wrong
[18:41] <corecode_> i started with a clean disk
[18:41] <corecode_> well, wiped out 4MB at the beginning of the drive
[18:46] <corecode_> ah yea
[18:46] <corecode_> definitely a bug
[18:47] <corecode_> cjwatson: the parititoner needs to wipe the contents of the new partitions
[18:47] <corecode_> cjwatson: otherwise previously existing lvm partitions will be picked up and confuse the installer