[00:13] liona29 (~liona29@ANantes-257-1-120-128.w90-25.abo.wanadoo.fr) joined #fai.
[00:14] baikonur (~simon@120-133.79-83.cust.bluewin.ch) left irc: Quit: Client exiting
[00:16] liona29 (~liona29@ANantes-257-1-120-128.w90-25.abo.wanadoo.fr) left irc: 
[00:39] ErKa (~keryell@m156.net85-168-208.noos.fr) left irc: Ping timeout: 480 seconds
[01:12] meandtheshel1 (~markus@85.127.112.221) left irc: Quit: Leaving.
[01:26] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Ping timeout: 480 seconds
[03:22] liona29 (~liona29@ANantes-257-1-120-128.w90-25.abo.wanadoo.fr) joined #fai.
[03:24] liona29 (~liona29@ANantes-257-1-120-128.w90-25.abo.wanadoo.fr) left irc: 
[08:11] itais (~itais@62.81.119.138.static.user.ono.com) joined #fai.
[08:14] i-R2D2 (~deed@tor-irc.dnsbl.oftc.net) left irc: Ping timeout: 480 seconds
[08:22] i-R2D2 (~deed@tor-irc.dnsbl.oftc.net) joined #fai.
[08:24] ErKa (~keryell@ridee.info.enstb.org) joined #fai.
[08:33] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai.
[08:43] Mrfai (~lange@kueppers.informatik.uni-koeln.de) joined #fai.
[08:53] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Ping timeout: 480 seconds
[09:11] <Bokeh> yawn
[09:11] <Bokeh> morning
[09:21] okay (~oops@129.175.204.73) left irc: Quit: Ex-Chat
[09:34] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai.
[09:37] <lazyb0y_> mfl: sounds like a very interesting feature - would mind filing a wishlist report?
[09:44] ErKa (~keryell@ridee.info.enstb.org) left irc: Ping timeout: 480 seconds
[10:02] sepski (~sep@217.17.211.51) joined #fai.
[10:05] <Mrfai> mfl: currently it's only possible by defining a negated class. So if you have a class FOO, also define a class NOTFOO, which is only defined if FOO is not defined. But please file a wishlist bug. 
[10:32] <mfl> Mrfai: ok, that's what i already did... :)
[10:33] sepski (~sep@217.17.211.51) left irc: Quit: Leaving
[10:35] <mfl> lazyb0y_,Mrfai: i'll file a wishlist bug as soon as my installations run...  thanks!
[10:41] MT_ (~MT@dove.informatik.tu-muenchen.de) joined #fai.
[10:41] Nick change: MT -> Guest162
[10:41] Guest162 (~MT@dove.informatik.tu-muenchen.de) left irc: Read error: Connection reset by peer
[10:41] Nick change: MT_ -> MT
[10:57] Mrfai (~lange@kueppers.informatik.uni-koeln.de) left irc: Quit: leaving
[10:57] Mrfai (~lange@suenner.informatik.uni-koeln.de) joined #fai.
[11:06] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Remote host closed the connection
[11:06] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai.
[11:33] paula35 (~paula35@ANantes-257-1-120-128.w90-25.abo.wanadoo.fr) joined #fai.
[11:35] paula35 (~paula35@ANantes-257-1-120-128.w90-25.abo.wanadoo.fr) left irc: 
[13:00] meandtheshell (~markus@85.127.112.221) joined #fai.
[13:39] itais (~itais@62.81.119.138.static.user.ono.com) left irc: Quit: See you
[13:49] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Remote host closed the connection
[13:49] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai.
[14:01] <Bluemoon_> moin moin
[14:03] <Bluemoon_> ich habe hier ein problem mit dhcp, wenn ich einen fai-client boote und er soll per dhcp eine ip bekommen, so geht das nicht, wenn ich aber im selben rechner eine grml-cd boote so bekomme ich mit dieser eine ip ueber den dhcp-server
[14:03] <Bluemoon_> was koennte das denn sein?
[14:50] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Remote host closed the connection
[14:51] <Mrfai> direkt beim PXE boot oder spaeter wenn der kernel schon gebootet hat? Welche Netzwerkkarte? Die die NEtzwerkkarte auf PXE eingestellt?
[14:51] lidi20 (~lidi20@d033.dhcp212-198-248.noos.fr) joined #fai.
[14:51] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai.
[14:52] lidi20 (~lidi20@d033.dhcp212-198-248.noos.fr) left irc: 
[15:00] <Bluemoon_> Mrfai, PXE nicht, ich boote per floppy
[15:01] <Bluemoon_> also wenn der kernel versucht eine IP zu bekommen
[15:24] <Mrfai> aber die netzwerkkarte ist aktiviert?
[15:29] <Bluemoon_> jepp
[15:29] <Bluemoon_> es geht ueber ein dhcp-relay, kann das vielleicht der grund sein?
[15:30] <Bluemoon_> das komische ist, das der dhcp-server ein offer schickt und dieses auch ankommt
[15:30] <Bluemoon_> nur wird es nicht vom fai-client angenommen
[15:30] <Mrfai> natuerlich. Aber du solltest ja im log sehen ob die dhcp request ueberhaupt nakommen
[15:30] <Mrfai> ok
[15:31] <Mrfai> was fuer eine floppy? etherboot, rom-o-matic? 
[15:31] <Bluemoon_> eine mit make-fai-bootfloppy erstellte
[15:31] <Bluemoon_> also iso-image
[15:32] <Bluemoon_> s/also/als/
[15:33] <Mrfai> probier doch mal eine mit rom-o-matic erstellt. Dann hast du ganz normales PXE.
[15:34] <Bluemoon_> ich kann hier leider kein pxe nutzen weil hier schon so ein ZEN-netware PXE rumschwirrt
[15:40] <Mrfai> doof. Dann soll das ZEN PXE einfach ruhig sein wenn dein Rechner PXE macht.
[15:44] <Bluemoon_> das sage ich ja auch immer meinen netware-kollegen aber die meinen, dass sie diesen crap brauchen :)
[15:49] Mrfai (~lange@suenner.informatik.uni-koeln.de) left irc: Quit: Lost terminal
[15:49] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Read error: Connection reset by peer
[15:50] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai.
[16:09] Jahman (~oops@129.175.204.73) joined #fai.
[16:09] <Jahman> hi
[16:11] <Jahman> i have a little problem with nfs. When the client boot, the script nfs-premount failed(message mount Device or resource busy). On my nfs server, i have the following log message: Nov  7 17:05:04 dpt72 mountd[5561]: refused unmount request from 192.168.0.20 for /root (/): not exported
[16:12] <Jahman> why the client attempt to unmount /root on the server ?
[16:26] <Jahman> okay it was my  nfsroot variable in my pxeconfig.cfg/default. I need set up it by /media/stock/fai/nfsroot/live/filesystem.dir/ and not just /media/stock/fai/nfsroot/
[16:58] Jahman (~oops@129.175.204.73) left irc: Quit: Ex-Chat
[17:08] Mrfai (~lange@xdsl-213-196-242-172.netcologne.de) joined #fai.
[17:08] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Ping timeout: 480 seconds
[17:10] <lazyb0y_> Bluemoon_: ich hatte mal sonen effekt, als ich mit einem kernel, der auf ip_pnp_auto konfiguriert ist(oder iwe das heit, also dhcp auf kernel-ebene), dass er nur offers von authoritative dhcp's angenommen hat - das sah da auch so aus, wie du es beschreibst.
[17:11] <lazyb0y_> ich weiss nicht, ob es schon in fai 3.2 geht, eine bootfloppy zu machen - da dort ein normaler kernel ohne diese option genutzt wird, sollte das da nicht passieren
[17:37] <h01ger> bootfloppies werden in 3.2.1 gearnicht mehr unterstützt. etherboot
[17:37] <h01ger> rom-o-matic.net
[17:37] <h01ger> steht im wiki
[17:37] <Mrfai> h01ger: hatten wir schon. Er kann kein PXE nutzen
[17:40] <h01ger> axo
[17:49] <Bluemoon_> re
[17:50] <Bluemoon_> lazyb0y_, ja, das scheint echt am kernel-dhcp zu liegen
[17:50] <Bluemoon_> ein gebootetes grml in der selben VM macht dhcp ohne probleme
[18:03] <Mrfai> Bluemoon_: kannst du von CD booten? Dann koenntest du den kernel mit initrd von CD booten.
[18:04] <Bluemoon_> von cd kann ich booten, fuer diese rechner habe ich aber noch fai 3.1
[18:05] <Bluemoon_> fai 3.2 habe ich erst auf einer testbox
[18:59] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai.
[19:00] meandtheshell (~markus@85.127.112.221) left irc: Quit: Leaving.
[19:11] sobersabre (~bilbo@89-138-77-31.bb.netvision.net.il) joined #fai.
[19:11] <sobersabre> hi guys.
[19:11] <sobersabre> what can cause the machine to fail to unzip/untar the base.tgz file ?
[19:12] <sobersabre> and suddenly loose the FAI server..
[19:12] <sobersabre> It's a LAN. 
[19:12] <sobersabre> although mixed speeds etc., but still a lan.
[19:13] <sobersabre> the partitioning succeeds, but after that the machine fails on extracting base.tgz ( if I am not wrong ) I am not at the machine now.
[19:23] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Ping timeout: 480 seconds
[19:27] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai.
[19:31] <lazyb0y_> ich habe schon mehrmals rom-o-matic getestet, und es hat nie geklappt. 
[19:48] <Mrfai> sobersabre: check the cables. read fai.log. Any error messages?
[19:48] <sobersabre> I can connect to the machines. nothing suspicious.
[19:48] <Mrfai> can you ping them?
[19:48] <sobersabre> is it possible that the kernel gets pushed, but the base.tgz is stuck with "bad cables" thing ?
[19:48] <sobersabre> I can ping them.
[19:49] <Mrfai> ping them with larger packets
[19:49] <sobersabre> hmm.
[19:49] <sobersabre> :)
[19:49] <sobersabre> ok
[19:49] <sobersabre> doing it.
[19:49] <sobersabre> moment.
[19:50] <MT> what about ssh?
[19:52] <Mrfai> good idea. can you ssh to them?
[19:53] i-R2D2 (~deed@tor-irc.dnsbl.oftc.net) left irc: Remote host closed the connection
[19:54] <sobersabre> I can ssh
[19:54] <sobersabre> I can read log.
[19:55] <sobersabre> pings pass.
[19:55] <MT> anything useful in the logs?
[19:55] <MT> what if you do the base extraction manually?
[19:55] <sobersabre> I tried -s 65507
[19:55] <sobersabre> MT: where is it located ?
[19:56] <MT> the base or the logs?
[19:56] <sobersabre> and another one: can you md5 your base.tgz ?
[19:56] <sobersabre> the base
[19:56] <sobersabre> I know where logs are.
[19:57] <sobersabre> it says /var/tmp/base.tgz
[19:57] <MT> the base is /var/tmp/base.tgz
[19:57] <sobersabre> 1b97d98974df6962a141ba21c1c0d972  base.tgz
[19:57] <sobersabre> can you compare to your md5sum ?
[19:57] <MT> which FAI version, which distribution?
[19:58] <MT> I think it's highly unlikely that there are any similar base.tgz around
[19:58] <MT> with the same md5sum
[19:59] i-R2D2 (~deed@tor-irc.dnsbl.oftc.net) joined #fai.
[20:00] Unnamed-KLBK- (~UnnamedKL@aaxy240.neoplus.adsl.tpnet.pl) joined #fai.
[20:00] <Mrfai> sobersabre: IMO it makes no sense to compare md5 of base.tgz. They will differ.
[20:00] <Mrfai> any error messages in fai.log or from dmesg?
[20:01] <Mrfai> call top and see if a process is running
[20:01] <Mrfai> during extracting the base
[20:02] Unnamed-KLBK- (UnnamedKL@aaxy240.neoplus.adsl.tpnet.pl) left #fai (Mówisz po polsku? Zapraszam na #polska_).
[20:07] <sobersabre> moment.
[20:07] <sobersabre> there's one strange thing.
[20:07] <sobersabre> I remember that in the <hex IP without dots> files I have no mentioning of UDP.
[20:08] <sobersabre> but the booting system somehow has an nfs mount via UDP, with wierd options.
[20:08] <sobersabre> how come this can happen ?
[20:08] <Mrfai> tcp for NFS mounts is better
[20:08] <Mrfai> sobersabre: gbit LAN?
[20:08] <MT> check your tftpd logs to find out which file it used for booting
[20:08] <sobersabre> Mrfai, it's a mix of 100 and 1000 links.
[20:09] <MT> gbit/100mbit won't work properly for NFS-over-udp
[20:09] <sobersabre> this leaves not many choices but to use TCP.
[20:09] <Mrfai> gbit LAN and NFS over UDP may cause problems
[20:09] <MT> :-)
[20:09] <sobersabre> it cause.
[20:09] <Mrfai> MT: 100mbit is fine, gbit can cause problems
[20:10] <sobersabre> anyway, I wonder WHY I have seen udp
[20:10] <sobersabre> anyway.
[20:10] <sobersabre> strangeness continues:
[20:10] <sobersabre> uptime:
[20:10] <MT> but mixing them hardly works at all
[20:10] <sobersabre> 23:01:51 up  5:53,  1 user,  load average: 1.00, 0.97, 0.91
[20:10] <sobersabre> something is definetely fishy.
[20:10] <MT> is it maybe still pulling base.tgz?
[20:11] <sobersabre> /dev/root on / type nfs (rw,vers=2,rsize=4096,wsize=4096,hard,nolock,proto=udp,timeo=11,retrans=2,sec=sys,addr=132.68.206.225)
[20:11] <sobersabre> WHY udp ?!?!
[20:11] <sobersabre> I don't understand this.
[20:11] <MT> cat /proc/cmdline ?
[20:12] <sobersabre> last line is "Extracting /var/tmp/base.tgz"
[20:13] <sobersabre> ip=dhcp root=/dev/nfs nfsroot=/srv/fai/nfsroot FAI_FLAGS=verbose,sshd,createvt FAI_ACTION=install BOOT_IMAGE=vmlinuz-install
[20:13] <MT> that might all be solved by solving this udp issue
[20:14] <sobersabre> found it.
[20:14] <sobersabre> for some reason there are 4 machines with this above line.
[20:14] <sobersabre> but the rest ( normal ) are:
[20:14] <sobersabre> vmlinuz-install ip=dhcp  root=/dev/nfs nfsroot=/srv/fai/nfsroot,v3,tcp,intr FAI_FLAGS=verbose,sshd,createvt FAI_ACTION=install
[20:15] <sobersabre> as you can see, tcp, intr and v3 are specifically put.
[20:15] <sobersabre> hm.
[20:15] <sobersabre> I hate gremlins.
[20:15] <sobersabre> At least I know there are some.
[20:15] <MT> are you damn sure it has found an appropriate config file
[20:16] <Mrfai> some versions of fai-chboot set tcp and v3, the newer version does not need it any more, since newer kernel and kernel with initrd automatically uses v3 and tcp
[20:16] <MT> (and did not use some default config)
[20:16] <sobersabre> I user fai-chboot -I for the rest.
[20:16] <sobersabre> s/user/used/
[20:16] <sobersabre> wierdo one.
[20:17] <sobersabre> what does "boot=live" mean ?
[20:17] <sobersabre> I remember removing it for some reason.
[20:18] <MT> that's required for live-initramfs
[20:18] <MT> assuming you are consistently using FAI >= 3.2
[20:19] <MT> (including an NFSROOT generated by FAI >= 3.2)
[20:19] <sobersabre> I am using fai-kernels 1.17, and the rest is 3.2.1
[20:19] <sobersabre> NFSROOT generated with 3.2.1
[20:20] <MT> FAI 3.2.1 doesn't really like fai-kernels anymore I think
[20:20] <MT> you should be using a standard kernel
[20:20] <sobersabre> hm...
[20:20] <sobersabre> shall I remove the package ?
[20:20] <MT> hmm, no idea, Mrfai?
[20:21] <sobersabre> how can I point fai to use standard kernel ?
[20:21] <sobersabre> shall I remove and run fai-setup ?
[20:21] <MT> It will do so by default
[20:21] <Mrfai> if you have FAI 3.2.1 on your install server, you will only need to rebuild your nfsroot (fai-setup) which also copies the plain kernel with initrd to your tftp directory
[20:21] <sobersabre> ok.
[20:21] <MT> make-fai-nfsroot will do
[20:22] <Mrfai> right make-fai-nfsroot will copy the kernel and initrd
[20:22] <sobersabre> ok. I will try this. hoping for the best.
[20:22] <Mrfai> save your old nfsroot
[20:22] <Mrfai> before doing this
[20:22] <Mrfai> and use -v
[20:24] <sobersabre> ok.
[20:24] <sobersabre> I have no sentiments for the old nfsroot though.
[20:24] <sobersabre> :)
[20:46] <sobersabre> hmm
[20:46] <sobersabre> got this one:
[20:46] <sobersabre> chroot: cannot run command `update-initramfs': No such file or directory
[20:47] <sobersabre> where have I sinned ?!
[20:47] <stockholm> sobersabre: you know that very well!
[20:47] <Mrfai> paste your log of make-fai-nfsroot to paste.debian.net
[20:47] <stockholm> sobersabre: repent!
[21:10] <sobersabre> you mean the output of make-fai-nfsroot -v ?
[21:13] Nick change: MT -> Guest40
[21:13] Guest40 (~MT@dove.informatik.tu-muenchen.de) left irc: Read error: Connection reset by peer
[21:13] MT_ (~MT@dove.informatik.tu-muenchen.de) joined #fai.
[21:13] Nick change: MT_ -> MT
[21:16] Mrfai_ (~lange@xdsl-213-196-242-181.netcologne.de) joined #fai.
[21:16] <Mrfai_> yep
[21:16] Mrfai_ (~lange@xdsl-213-196-242-181.netcologne.de) left irc: 
[21:18] Mrfai (~lange@xdsl-213-196-242-172.netcologne.de) left irc: Ping timeout: 480 seconds
[21:18] Mrfai (~lange@xdsl-213-196-242-181.netcologne.de) joined #fai.
[21:53] <sobersabre> http://paste.debian.net/41736
[21:55] <sobersabre> Mrfai, have you got it ?
[21:55] Action: Mrfai reading it
[21:55] <sobersabre> omg...
[21:56] <sobersabre> maybe this is a "blank" error. i.e. everything seems ok, but I am getting a heart attack from "aborting" etc.
[21:56] <Mrfai> no, things are missing
[21:57] <MT> hmm, no linux-image ...
[21:57] <Mrfai> no package linux-image... is installed
[21:57] <Mrfai> :-)
[21:57] <MT> :-)
[21:57] <Mrfai> 2 seconds too late ;-)
[21:58] <MT> sobersabre, which hardware architecture is this?
[21:58] <sobersabre> install_packages: executing chroot /srv/fai/nfsroot/live/filesystem.dir dpkg -C
[21:58] <sobersabre> install_packages: executing chroot /srv/fai/nfsroot/live/filesystem.dir apt-get clean
[21:58] <sobersabre> chroot: cannot run command `update-initramfs': No such file or directory
[21:58] <sobersabre> intel, I use 686 intel kernel.
[21:59] <sobersabre> hmm... what a flooder.
[21:59] <MT> Mrfai, how does make-fai-nfsroot know whether it should use I386, AMD64, etc
[21:59] <sobersabre> I guess uname -m
[21:59] <sobersabre> it doesn't know much about the clients.
[22:00] <MT> sobersabre: could you do chroot /srv/fai/nfsroot dpkg --print-installation-architecture
[22:00] <MT> please
[22:00] <sobersabre> I will moment.
[22:00] <sobersabre> Mrfai, I am adding:
[22:00] <sobersabre> linux-image-2.6.18-5-686
[22:01] <sobersabre> to the line:
[22:01] <sobersabre> PACKAGES install I386
[22:01] <sobersabre> I mean after that line, after lilo, grub etc.
[22:01] <sobersabre> I this seems ok?
[22:01] <Mrfai> sobersabre: /etc/fai/NFSROOT should already contain the name of the linux-image package
[22:02] <sobersabre> well, somehow it doesn't
[22:02] <Mrfai> use the original /etc/fai/NFSROOT from the package. 
[22:02] <sobersabre> maybe I shall rerun fai-setup ?
[22:02] <Mrfai> no
[22:02] <Mrfai> I think do did an upgrade from FAI 3.1 to 3.2 and did not use the new /etc/fai/NFSROOT.
[22:02] <Mrfai> you are still usingthe old version of NFSROOT
[22:03] <MT> sobersabre, would you mind pasting /etc/fai/NFSROOT ?
[22:03] <sobersabre> hmm... talent. that's what I call talent
[22:03] <sobersabre> Mrfai,  you're correct, as usual.
[22:03] <sobersabre> shall I simply replace with stock NFSROOT ?
[22:04] <Mrfai> didn't the upgrade asked you which version to use?
[22:04] <sobersabre> I am usually conservative about this :) 
[22:04] <sobersabre> 1st time I get it on the bad side 
[22:04] <Mrfai> ok, that was your fault.
[22:04] <Mrfai> yes just use the stock new one
[22:04] <sobersabre> I have never blamed anyone esle, except gremlins.
[22:04] <sobersabre> :)
[22:04] <MT> did you do any changes to the old NFSROOT file?
[22:05] <MT> -> you might want to merge them
[22:05] <MT> but most probably the stock version is just fine
[22:05] <sobersabre> now I tried to do, I will now replace. but I want 686 kernel. 
[22:05] <sobersabre> not 486
[22:05] <sobersabre> any advantage to 486 ?
[22:05] <sobersabre> I have no 486 machines.
[22:06] <Mrfai> you do not need 686 kernel during installtion.
[22:06] <Mrfai> this is the kernel for installtion only. You may ewant to adjust /srv/fai/config/package_config/...
[22:06] <Mrfai> there you define the kernel for your new system
[22:06] <sobersabre> this I have done already.
[22:07] <Mrfai> sobersabre: I hope to get the FAI questionnaire from you after you've installed with your new FAI version.
[22:07] <sobersabre> anyway, the annotying thing:
[22:08] <sobersabre> make-fai-nfsroot -v 2>&1 > output.txt
[22:08] <sobersabre> and it still somehow prints something on stdout
[22:08] <MT> I think you should do make-fai-nfsroot -v > output.txt 2>&1
[22:08] <sobersabre> shall I  ( make-fai-nfsroot -v ) 2>&1 > output.txt ?
[22:08] <sobersabre> hmm..
[22:09] <sobersabre> I guess you're right. but ... why doesn't the other way work ? the effect seems to be the same... ( to me )
[22:10] <sobersabre> I mean seems to have been supposedly
[22:10] <Mrfai> sobersabre: that's shell magic
[22:10] <sobersabre> I wrote a shell that didn't mind that.
[22:10] <sobersabre> :)
[22:10] <sobersabre> I remember discussing this with the partner... 
[22:10] <sobersabre> convincing him: "but bash already works like that!"
[22:11] <MT> Note  that  the order of redirections is significant.  For example, the
[22:11] <MT>        command
[22:11] <MT>               ls > dirlist 2>&1
[22:11] <MT>        directs both standard output and standard error to  the  file  dirlist,
[22:11] <MT>        while the command
[22:11] <MT>               ls 2>&1 > dirlist
[22:11] <MT>        directs  only the standard output to file dirlist, because the standard
[22:11] <MT>        error was duplicated as standard output before the standard output  was
[22:11] <MT>        redirected to dirlist.
[22:11] <MT> man bash
[22:12] <sobersabre> yep
[22:14] <sobersabre> MT: http://paste.debian.net/41742 my old NFSROOT
[22:15] <MT> hmm, I think you had added (at least) subversion-tools build-essential
[22:15] <sobersabre> tru
[22:15] <sobersabre> but that was before I've added that to classes.
[22:16] <sobersabre> the results:
[22:16] <sobersabre> dpkg --print-installation-architecture
[22:16] <sobersabre> i386
[22:16] <sobersabre> after chroot to /srv/fai/nfsroot
[22:17] <MT> ok, I guess that's all fine once you use the new NFSROOT file
[22:18] <sobersabre> running now.
[22:18] <sobersabre> will see what's going on then.
[22:32] <sobersabre> which key is used to sign fai packages ?
[22:33] <Mrfai> my key: AB9B66FD
[22:33] <Mrfai> why?
[22:34] <sobersabre> I think I don't have it... checking.
[22:37] <sobersabre> which keyserver has it ?
[22:39] <sobersabre> ok. found it :)
[22:44] <sobersabre> the saga continues, though:
[22:44] <sobersabre> http://paste.debian.net/41745
[22:44] <sobersabre> now some destination is missing.
[22:45] <sobersabre> can somebody look at this ?
[22:45] <MT> ah, that one is well known
[22:45] <MT> mom
[22:45] <sobersabre> moment then.
[22:46] <MT> you need to update make-fai-nfsroot.conf as well
[22:46] <MT> you are missing the TFTPROOT variable
[22:47] <sobersabre> ok
[22:47] <sobersabre> I know it's value though
[22:47] <sobersabre> :)
[22:47] <sobersabre> Thanks!!!
[22:50] <sobersabre> Danke sch?n.
[22:50] <sobersabre> Why do I actually need: FAI_DEBOOTSTRAP="etch http://ftp.debian.org/debian"
[22:50] <sobersabre> ?
[22:50] <MT> :-)
[22:51] <sobersabre> I have local mirror.
[22:51] <MT> otherwise make-fai-nfsroot wouldn't know how to call debootstrap
[22:51] <MT> then feel free to put the local mirror there
[22:51] <MT> (I think)
[22:51] <sobersabre> I'll do that.
[22:59] <MT> I'll get to bed, good luck sobersabre!
[23:04] Action: Mrfai me too
[23:04] Mrfai (~lange@xdsl-213-196-242-181.netcologne.de) left irc: Quit: leaving
[23:07] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Ping timeout: 480 seconds
[23:08] <sobersabre> thanks all
[23:08] <sobersabre> :) 
[23:10] <sobersabre> schlaf gut, treum s?ss  
[23:10] <sobersabre> byebye
[23:10] sobersabre (~bilbo@89-138-77-31.bb.netvision.net.il) left irc: Quit: Leaving
[00:00] --- Thu Nov  8 2007