[00:13] ErKa (keryell@keryell.pck.nerim.net) left irc: Ping timeout: 480 seconds [01:20] ctp (~ctp@brsg-4d0790cc.pool.mediaWays.net) joined #fai. [01:23] kugg (~kugg@user184.77-105-210.netatonce.net) left irc: Ping timeout: 480 seconds [06:45] kugg (~kugg@user184.77-105-210.netatonce.net) joined #fai. [06:51] jesus. das fai-setup auf ubuntu hängt... [07:14] fai-guy (~fai-guy@p57B9BD83.dip0.t-ipconnect.de) joined #fai. [07:55] make-fai-nfsroot on ubuntu 7.10 (fai 3.2.1) does not seem to produce a working nfsroot [08:12] ErKa (keryell@m2.wifi.enstb.org) joined #fai. [08:29] Nick change: \sh_away -> \sh [08:32] Nick change: \sh -> \sh_away [08:35] Mrfai (~lange@kueppers.informatik.uni-koeln.de) joined #fai. [09:13] Mrfai: have you seen siretard lately? [09:20] where can i find a good tftpd setup howto ... i like to run tftpd on a different server than dhcpd [09:28] oz_: no [09:29] fai-guy: use the parameter next-server in dhcpd.conf [09:30] Mrfai: kewl, thx ... [09:33] i generated with fai-chboot my pxelinux.cfg for the test host, there is "initrd=initrd.img-install" in it. but i dont have a initrd.img-install ... is it a bug or my fault ? [09:36] in /srv/tftp/fai is only a vmlinuz-install which will loaded correctly [09:47] vmlinuz-install is only used in FAI < 3.2. [09:47] in FAI >=3.2 we use something like vmlinuz-2.6.18-5-486 and initrd.img-2.6.18-5-486 [09:47] ok, i use 3.2.4 [09:48] but why fai-chboot generates this entry ? [09:48] fai-chboot -h: I have fai-chboot version 3.4.3 15-november-2007 [09:49] fai:/srv/tftp/fai# fai-chboot -h [09:49] fai-chboot version 3.4.3 15-november-2007 [09:49] this was my shell call fai-chboot -IBv opensuse-fai-test [09:51] which kernel and initrd files are in your $nfsroot/boot? [09:56] vmlinuz-2.6.18-5-486 and initrd.img-2.6.18-5-486 [10:41] ok, i changed the file by hand and now it works, but why does it generate these entries [10:42] I guess you have also initrd.img-install in your nfsroot. man fai-chboot, look for -s [10:43] Mrfai: no it isnt there [10:43] http://paste.debian.net/44798 [10:45] kriebly (~moho@wisdom.Stanford.EDU) left irc: Ping timeout: 480 seconds [10:56] fai-guy: remove (rm) your entries in pxelinux/.cfg directory, Then recreate them using fai-chboot. It must not create an entry with initrd.img-install, because the string install is not used in fai-chboot [10:58] ok, i deleted both C0A832DB and default and run fai-chboot again but there is vmlinuz-install again inside [11:03] what did fai-chboot -v..... say? [11:03] do you have multiple nfsroot on this system? Maybe fai-chboot is looking into another nfsroot [11:13] fai:/srv/tftp/fai/pxelinux.cfg# fai-chboot -IBv -v opensuse-fai-test [11:13] Booting kernel vmlinuz-install append initrd=initrd.img-install ip=dhcp FAI_FLAGS=verbose,sshd,reboot [11:13] opensuse-fai-test has 192.168.50.219 in hex C0A832DB [11:14] hmmpf, this should pasted at paste.debian.net <-- my fault ;-) [11:15] an no, i only have one nfsroot [11:17] fai:/srv/tftp/fai/pxelinux.cfg# find / -name 'vmlinuz-install*' -o -name 'initrd-install*' [11:17] /srv/tftp/fai/vmlinuz-install [11:18] there is the only vmlinuz-install ... on the whole maschine i dont have any initrd-install [11:19] the system is upgraded from 3.1.8 to 3.2.x and the nfsroot was builded new at this upgrade [11:23] sorry, you should also remove /srv/tftp/fai/*-install [11:23] then try fai-chbott again [11:23] jcastang (~jcastang@laptop-147-210-128-147.labri.fr) joined #fai. [11:23] hi [11:23] Mrfai: fine, now it works [11:24] maybe it was trash from the 3.1.8 [11:24] sure [11:24] I am wondering if I could set specific packages to be installed in base.tgz (like language-pack-fr) to have setup process In french or do I have to do it manually ? [11:34] what do you mean by setup process? [11:34] allee (~ach@allee.mpe.mpg.de) left irc: Remote host closed the connection [11:34] There are two location where you may need the french packages. Inside the nfsroot and in base.tgz. [11:35] and set LANG=fr or such [11:35] yep [11:37] jcastang (~jcastang@laptop-147-210-128-147.labri.fr) left irc: Ping timeout: 480 seconds [11:44] Mrfai, i've told long ago that there will be people wanting fai in different languages :-) which reminds me to write this blog post about how we use a wiki to write+maintain debian-edu-doc and translate it.. [11:49] h01ger: Mrfai do you know who should be contacted to report a bug in https://code.launchpad.net/~fai/+archive ? [11:50] oh, it is already fixed... [11:52] by half. [11:55] oz_, according to https://bugs.launchpad.net/ubuntu/+source/reportbug-ng/+bug/175508 these bugs should be filed against bugs.debian.org/fai ;-) /me giggles [11:55] hehe [11:56] it's only half of a bug: if you surf on the page looking for the repository for gutsy, it's preselected with "hardy" instead of "gutsy". [11:57] but I'll retest it with a browser without my javascript iron-coat. ;) [11:58] h01ger: I think I'll try to report it via the button on the page...just it's soo long. [11:58] I'd prefer a simple email address... [11:58] and this repository just offers fai 3.2.1 [11:59] but I think this version still has the nfsroot bug [11:59] Action: oz_ changes seats & [12:02] siretart (siretart@tauware.de) joined #fai. [12:02] h01ger: sorry, I jsut forgot to rejoin this channel after the last server reboot :) [12:02] np :) welcome back :) [12:50] jcastang (~jcastang@laptop-147-210-128-147.labri.fr) joined #fai. [12:52] ctp (~ctp@brsg-4d0790cc.pool.mediaWays.net) left irc: Ping timeout: 480 seconds [13:03] schurig (~schurig@pD95F9826.dip0.t-ipconnect.de) joined #fai. [13:04] hmm, I'm trying to boot a fai 3.2.4 nfsroot via pxe. Unfortunately, I get: [13:04] Begin: Mounting root filesytem... [13:04] /init: .: Can't open scripts/life [13:05] is something wrong with my kernel command line? [13:05] append initrd=initrd.img-2.6.18-5-486 ip=dhcp root=/dev/nfs boot=life nfsroot=192.168.233.xx:/srv/fai/nfsroot,v3,tcp,nolock,rsize=8192,wsize=8192 FAI_FLAGS=verbose,createvt FAI_ACTION=install [13:12] this line looks good. I guess you do not have live-initramfs inside your nfsroot. [13:13] Mrfai: it's there: [13:13] chroot /srv/fai/nfsroot/live/filesystem.dir dpkg -l "*initr*" [13:13] ii live-initramfs 1.95.2-1 Debian Live initramfs hook [13:14] hmm, but I just found out: it's "boot=live", not "boot=life" [13:19] use fai-chboot to create your pxelinux.cfg files [13:24] Mrfai: okay, did that [13:24] Mrfai: now the nfsroot get's mounted [13:24] Mrfai: but it starts busybox [13:24] Mrfai: if I do "ls", I can see that it's the nfsroot, e.g. there's live, live.log, live.vars in it [13:25] no, that inside the initrd I guess [13:25] you may need to add root-server to dhcpd.conf, since fai-chboot does not add your server IP address to the nfsroot= definition [13:26] okay [13:53] Mrfai: fai-chboot made things worse [13:53] Mrfai: now I can see in my syslog: RRQ from 192.168.233.11 filename fai/pxelinux.0 [13:54] Mrfai: and I can see on the computer that it first tries to pxelinux.cfg/, than pxelinux.cfg/ and so on, but I don't see any additional RRQ line from in.tftpd [13:55] Mrfai: also, in pxelinux.0 binary has a date from today now, so I guess somehow this got updated [13:59] this is all fine. [13:59] did you set next-server in dhcpd.conf? [14:00] Mrfai: no, just "server-name" [14:00] you have to use next-server with newer dhcp daemons [14:01] Mrfai: thanks, looks much better now [14:02] from the fai changelog: * dhcpd.conf: next-server is needed in dhcpd3 >=3.0.3 [15:37] Hmm, I still have a problem. Somehow the nfsmount never works. I tries to mount, fails, and put's me in the busybox shell. [15:38] from a different box, I can "mount -t 192.168.233.xx:/srv/fai/nfsroot /tmp/x" without any problem [15:39] but from the busybox, I cannot do "nfsmount 192.168.233.xx:/srv/fai/nfsroot /tmp/x" (and also not with the usual options, like -t v3,nolock,soft,...) [15:39] I already tried "unfs3" and "nfs-user-server" (on Debian Etch) [15:41] with "unfs3" I get something about response too short, with nfs-user-server i just get "rpc failed: 2" [15:45] oh, found a blog about this: http://www.myelin.co.nz/post/2007/5/28/ [15:46] allee (~ach@allee.mpe.mpg.de) joined #fai. [15:48] mikap, Tip 2: fai is another way to get a "cloned" system... :) [15:51] nfsmount sucks [15:52] Action: oz_ thinks "ubuntu sucks more" [15:52] not a very productive comment, sorry. [15:54] is it normal with newer nfsroots that there is just one single folder in it? [15:54] called "live"? [15:55] fai-setup just told me that everything went fine, but sowhat this nfsroot looks strange to me [15:56] oz_: yep, this is normnal [15:57] oz_: no, the nfsmount that is used inside fai's initial ramdisk can only be used with nfs-kernel-server. It refuses to mount if the NFS server is run by unfs3 (a userspace NFS) or by nfs-user-serv (a different user-space NFS server) [15:57] okay, so one needs "boot=live" as kernel parameter? [15:58] schurig: user-space-nfs is not really an alternative to kernel-nfs [15:58] jcastang (~jcastang@laptop-147-210-128-147.labri.fr) left irc: Quit: Ex-Chat [15:58] I tried it some time ago, and I got a lot of permission problems, but I can't recall it in detail. [15:59] oz_: user-space-nfs worked without any problem an older fai (where the kernel did directly mount nfs, without an initial ramdisk) [15:59] schurig: just sweitch to kernel-nfs (if you can, for me it was easy) and you should be fine [15:59] oz_: yeah, but finding this out did cost me 4 hours. Therefore: it used to work with older fai, now it doesn't, the culplit is nfsmount, so nfsmount sucks [16:00] find the diff, and fix it, then. [16:00] :-) [16:00] oz_: you should use fai-chboot. [16:00] Mrfai: why? and how do you know that I haven't called it yet? [16:01] Action: oz_ is stunned [16:01] schurig: fai >3.2.x now recommends nfs-kernel-server, and not user space server any more. [16:01] I did not switch to k-nfs because of fai, iirc [16:01] I think because of the homedirs and some programs. [16:01] schurig: so this is a minor hit that FAI works best using nfs-kernel-server :-) [16:03] Action: oz_ just fired up the amd64box (zubuntu 7.10) to install a i386 box [16:03] nfsroot was created on another i386 box, though [16:04] Mrfai: maybe the "recommend" is not enought. It actually doesn't work with neither unfs3 nor nfs-user-server. [16:05] Mrfai: but you can also not change that into a "conflict", because if someone doesn't use nfs-booting at all with fai, then it would be perfectly OK to have another NFS daemon installed [16:06] Mrfai: so maybe fai-setup should emit a big, fat warning that it doesn't work with one of those two packages [16:09] schurig: patches are welcome :-) [16:10] ErKa (keryell@m2.wifi.enstb.org) left irc: Remote host closed the connection [16:10] okay, now the nfs-installation did succeed [16:15] Action: oz_ is eager if his fai-zubuntu setup work now [16:17] sowhat it always stops with "Can't open /scripts/live" ... [16:17] oz_: hmm, so far I did about 100 fai-setups, just today I switched to 3.2.4 and run into a bunch of time-consuming problems [16:17] ... and this is correct, it's not there. [16:18] oz_: it should be there, e.g. you should have a /srv/fai/nfsroot/live/filesystem.dir/usr/share/initramfs-tools/scripts/live [16:18] schurig: if you don't have it, the your make-fai-nfsroot had a problem [16:19] schurig: that is present [16:19] but somewhow I think that is needed in the initrd as well? [16:19] oz_: yes, in the initrd it is needed as well [16:20] it's known bug in 3.2.1 [16:21] oz_: hmm, I'm on 3.2.4 [16:21] and now I'm going home [16:21] schurig (~schurig@pD95F9826.dip0.t-ipconnect.de) left irc: Remote host closed the connection [16:21] ubuntu? [16:21] oh fuck, he cold have told me what repository he is using... [16:22] cpilka (cpilka@popper.thc.nat.tu-bs.de) joined #fai. [16:23] hi folks. afaik fai uses crypt for root's passwd. does it also support md5 hashes? how to generate md5 passes? [16:23] Nick change: cpilka -> ctp [16:24] ctp: FAI is using md5 for a long time. [16:26] from the fai guide (newer version, not yet on the web page): [16:26] To generate a md5 hash for the password use this [16:26] echo "yoursecrectpassword" | mkpasswd -Hmd5 -s [16:29] Mrfai, uups, didnt see it in my guide ;-) thx [16:35] I wonder...http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444079 tells to remove live-initramfs from NFSROOT and add nfs-common... [16:35] let's see. [16:36] if you remove live-initramfs FAI will no work. [16:37] sorry not that easy. [16:37] live-initramfs can be removed from NFSROOT, since now the package fai-nfsroot depends on it [16:37] thx for that info...somewhat I read this in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444079 [16:37] So it's really needed. [16:38] ah, it's just no needed in NFSROOT anymore, okay [16:38] Mrfai: any recommendation for a apt-get repo for ubuntu? [16:39] should be fine it I youre the cologne repository, or not? [16:39] yep, koeln should be fine [16:39] Mrfai: last trouble i have is that my "append ..." line after fai-chboot is too long. bootstrapping the client fails cause the last parameters are not interpreted. the line: [16:39] okay, if this doesn't work I give up with ubuntu-fai. [16:40] append initrd=initrd.img-2.6.23.9-unionfs ip=dhcp root=/dev/nfs nfsroot=/srv/fai/nfsroot boot=live FAI_FLAGS=verbose,sshd,createvt,reboot FAI_ACTION=install [16:40] so FAI_ACTION is ignored. do you have a hint how to solve this behaviour? [16:41] check if cat /proc/cmdline has the whole line [16:41] then check variables.log [16:41] I remember, there was a problem with longer kernel append lines. I have to look for it again [16:44] Mrfai: ok, i made the append line shorter: [16:44] oz_: I have to admit that I have been incredibly busy at work, so I couldn't really look after fai in ubuntu [16:44] append initrd=initrd.img-2.6.23.9-unionfs ip=dhcp root=/dev/nfs nfsroot=/srv/fai/nfsroot boot=live FAI_FLAGS=verbose,sshd,createvt FAI_ACTION=install [16:44] oz_: seems that I can employ a student, which will also look at this [16:45] /proc/cmdline: "... FAI_ACTION=i" [16:45] siretart: if you can offer some contract: I have some free time ;) [16:46] ctp: the debian kernel support up to 1024 chars in the command line IIRC. [16:46] oz_: fai'ng ubuntu suckz. tried it for more than a week with gutsy and hardy. both without success [16:47] Mrfai: hmhm [16:47] ctp: yea, but may ppl asked me to try it. :-( [16:47] i was asked too :-) [16:47] just because ubuntui has the fancy look, and the "additional drivers" as they say [16:48] so I do it. Did so many sicj thing when I dealt with solaris... I fear nothing anymore. :) [16:49] ctp: best would be, if one you run "fai-cd" from it... [16:49] that's my goal. [16:50] ctp: linux sources: include/asm-i386/setup.h: #define COMMAND_LINE_SIZE 256 [16:50] but you have less than 256. But 256 is in Debian. [16:51] oz_: you're german, aren't you? so if you have some time, you can help me on writing a howto. i did it for debian (http://wiki.slashconcept.com/index.php/Fully_Automatic_Installation_FAI_with_Debian_GNU_Linux_4.0_Etch_Howto) and started for ubuntu (http://wiki.slashconcept.com/index.php/Fully_Automatic_Installation_FAI_with_Ubuntu_7.10_Gutsy_Gibbon_Howto). [16:51] ctp: what editor are you using? [16:51] ctp: I'll lok into it! [16:52] Mrfai, hm, ok. thx for the info. good to know such determining factors [16:53] oz_: what do you mean with editor? its a wiki. for all editing stuff im using vim [16:53] ctp: no, I mean what editor are you using to edit your config files [16:54] it's less that 124 chars, below the debian limit [16:55] oz_: vim [16:55] during our utf-8 migration phase I experience strange things in files, which could not be read correctly anymore. that's why I ask. [16:55] some editors "hide" special chars [16:56] vim is very okay, hm. [16:56] Mrfai (~lange@kueppers.informatik.uni-koeln.de) left irc: Quit: leaving [16:57] you should check the sources of your kernel [16:57] maybe it's the limit? [16:57] oz_: 124 chars are the limit? [16:57] no, normally not. [16:58] but iirc, you used a special kernel, so you need to check this [16:58] ok [16:59] no its 144 chars [17:00] oz_: argh. where do you have it from? [17:00] ? [17:00] what "it"? [17:01] the 144 chars [17:02] save your append to a file and run 'wc -m' on it. [17:02] hmhm: #define COMMAND_LINE_SIZE 2048 in my sources [17:02] so, no prob here. [17:02] I'd move around the options [17:02] in your case... [17:03] i did it. same behaviour [17:03] you cold rename the kernel 10 chars shorter. :) [17:03] strange bug you found there. [17:04] i think one needs to wrap strace around it to get a clue what is going wrong there. [17:05] fai-guy (~fai-guy@p57B9BD83.dip0.t-ipconnect.de) left irc: Quit: leaving [17:05] running amd64 here. perhaps it only occurs on amd64 fai [17:05] oh. maybe. [17:06] does /proc/cmdline show more chars if you shorten the append? [17:06] you could ask on the kernel mailing list... [17:07] yepp, i'll do it definitely ;-) [17:07] tell us the outcvome :) [17:07] i'm back again in 5 mins (trying some stuff out) [17:08] ctp: you did not write in the article that you did not suceed with gutsy and hardy [17:09] hardy is the new 8.10? [17:11] oz_, i didn"t yet. i hope to get it running from feisty and update the stuff to gutsy via fai [17:12] hardy will be released in april 08 [17:14] ctp: https://code.launchpad.net/~fai/+archive is somewhat misleading [17:14] it by default say "hardy", but it does not exist yet [17:17] oz_, mal kurz in deutsch. ziemlich abgefahren: ich habe den append string nun abgekuerzt (einiges weggelassen). cat /proc/cmdline sagt mir nun: "... FAI_ACTION=install BOOT_IMAGE=vmli". wo kommt das BOOT_IMAGE=vmli her? gibt /proc/cmdline lediglich den append teil aus? da steht es naemlich nicht drin *verwirrt* [17:27] find -type f -exec grep BOOT_IMAGE= {} \; könnte helfen [17:27] wow das ist echt hart [17:44] oz_, das einzige, was ich zu diesem thema gefunden habe nach einem grep auf nfsroot: [17:44] nfsroot/live/filesystem.dir/usr/sbin/mkrescue:# image=`cat /proc/cmdline | sed "s/.*BOOT_IMAGE=//" | sed "s/ .*//"` [17:44] ctp: könnte was damit zu tun haben... [17:44] also wertet /proc/cmdline auch das kernelimage aus der menu.lst aus [17:45] Action: oz_ ist grad besucht worden [17:45] allee (~ach@allee.mpe.mpg.de) left irc: Remote host closed the connection [18:18] ErKa (keryell@keryell.pck.nerim.net) joined #fai. [18:22] my fai is nearly working perfect, BUT during install client i get a "Calling task_chboot" -> i have to accept manually rsa key fingerprint for my fai server. how to accept it automatically [18:55] h01ger: oh, sure :) [regarding "fai is another way to get a cloned system"] - even a better way ;) sometimes you only have the needs for a 1:1 clone without the possibility/time for a FAI-setup, though I'd like to have something like a simple gui for setting up FAI for classic scenarios ;)) [19:33] Action: h01ger nods :) [19:36] fai-guy (~fai-guy@p54BD78B0.dip.t-dialin.net) joined #fai. [19:36] fai-guy (~fai-guy@p54BD78B0.dip.t-dialin.net) left irc: [19:44] no one here has an idea how to accept server's ssh key automatically on my fai clients? [19:55] fcopy it to /root/.ssh/known_hosts, put it in /etc/ssh/, run "ssh server | yes" in a script... [20:05] tostado (~tostado@dslc-082-082-046-013.pools.arcor-ip.net) joined #fai. [20:06] hi [20:08] h01ger, thx, you're my hero today ;-) [20:09] ctp, you're welcome [20:09] hi tostado [20:10] hi holger [20:10] schon unterwegs ? [20:12] Action: h01ger ist in madrid, ja :) [20:26] kann mir jemand weiterhelfen ? [20:26] ist dt. o. engl. besser ? [20:31] ctp (cpilka@popper.thc.nat.tu-bs.de) left irc: Quit: Leaving [20:32] ok i just try to figure our problem out: we did a quick install of fai-server on a ubuntu gutsy server and after fai-setup was finished properly we cannot boot via pxe. [20:32] tostado: why not? [20:32] ctp (thcuser@carnap1.thc.nat.tu-bs.de) joined #fai. [20:32] the client gets an ip, tries to boot via tftp and the error is trying to load: pxelinux.cfg/.... [20:33] oh, sounds like a problem in your pxelinux config [20:33] but on the server there is an empty pxelinux.cfg dir [20:33] place a file called 'default' with the config in it [20:34] which config ? [20:34] your pxelinux config. what kernel and what initrd with whta kernel parameters to boot [20:35] hmm... seems i have to study a bit pxelinux.... [20:35] good idea :) [20:36] h01ger: hm, "yes yes | ssh myserver" doesnt work. it does not pipe the "yes" :-( is it a standard behaviour that the clients ask to accept the server's ssh key manually? it happens after fai has reported the install duration (so performing task_chboot) [20:48] sepski (~sep@217.17.211.51) joined #fai. [20:50] Bluemoon (~mj@altf4.org) joined #fai. [20:51] nabend [20:53] @siretart: ok, the kernel boots now. Then i get a kernel panic... shit [20:53] tostado: unionfs related? [20:54] vfs: cannot mount root fs or so... [20:54] i just have 1 sec to see the error... then it scrolls away [20:54] I remember a launchpad bug against the ubuntu kernel for that [20:55] I'd suggest to install feisty in the nfsroot [20:55] and install gutsy from that [20:55] cannot open root device "nfs" or so... [20:56] we had gutsy in the nfsroot and fried with feisty now [20:56] the same.... [20:57] I use feisty nfsroot at my university with stock kernels, so I can confirm that this works [20:58] forgot the say that the gutsy server is a xen host, maybe that could be a hint ? [20:59] oh yes, xen is broken [20:59] I've been able to trigger strange segfaults when running inside xen, which are not reproducible outside [20:59] this is also documented in some bugreport [21:00] interestingly, they happened only with fai for me [21:00] cf https://bugs.edge.launchpad.net/ubuntu/+source/fai/+bug/159536 [21:02] yes i had the same error, but we could fix the segfaults. But anyway, the best should be to use a clean ubuntu server install ... [21:03] tostado: how did you fix the segfaults? [21:04] (hope i remember it well enogh) when fai-setup makes a debootstrap, it needs to move the tls libs out of the way [21:05] mv $NFSROOT/lib/tls $NFSROOT/lib/tls.disabled [21:06] this line i inserted in the make-fai-nfsroot script [21:06] we had the same problem with debootstrap and xen-tools [21:12] hm. I remember to have had libc6-xen installed. hmmm [21:13] ctp, man ssh :) [21:13] libc6-xen takes care of disabling tls. afaik thats the only diff to libc6 [21:14] but that could be the same problem, different fix... mine wasn't the cleanest fix [21:14] i will try on another server... [21:15] what will be easy for us when we want to install ubuntu feisty on the clients: a ubuntu oder debian server running fai-server ? [21:16] tostado: I'd say ubuntu, with the ubuntu-fai packages from the team's ppa [21:16] because that's why I'm using myself [21:16] the team's ppa ? [21:17] h01ger, i've read it. i'm asking cause i am not sure if i have forgotten something to configure in fai configs. so in default installation fai clients do not accept server's ssh key automatically before task_chboot? [21:18] tostado: https://edge.launchpad.net/~fai/+archive [21:23] ctp, probably, dunno for sure. put that key in /etc/ssh/known_hosts in the nfsroot [21:23] ok [21:43] hm, anyone here has ever seen this message (task_chboot): "SERVER not defined. Can't change network boot connection"? [21:43] s/connection/configuration ;-) [21:58] siretart: thanks i will try them on a clean gutsy install [22:12] tostado, as said, i cannot help you much with ubuntu... [22:15] h01lger: no problem, as long as others are helpful here :) [22:16] i will probably ask you again after the first successful installation ;) [22:33] ctp (thcuser@carnap1.thc.nat.tu-bs.de) left irc: Quit: Leaving [22:33] ctp (thcuser@carnap1.thc.nat.tu-bs.de) joined #fai. [22:33] ctp (thcuser@carnap1.thc.nat.tu-bs.de) left irc: [22:33] ctp (thcuser@carnap1.thc.nat.tu-bs.de) joined #fai. [22:37] tostado, :) [22:37] enjoy! ;) [22:47] sepski (~sep@217.17.211.51) left irc: Quit: Leaving [22:54] tostado (~tostado@dslc-082-082-046-013.pools.arcor-ip.net) left irc: Quit: Lost terminal [23:48] lazyb0y_ (~henning@v683.vanager.de) left irc: Remote host closed the connection [00:00] --- Fri Dec 14 2007