[00:50] fxcp_ (~ctp@brsg-d9befbed.pool.mediaWays.net) joined #fai. [00:57] fxcp (~ctp@brsg-d9beebc0.pool.mediaWays.net) left irc: Ping timeout: 480 seconds [03:09] fxcp__ (~ctp@brsg-d9bee6da.pool.mediaWays.net) joined #fai. [03:16] fxcp_ (~ctp@brsg-d9befbed.pool.mediaWays.net) left irc: Ping timeout: 480 seconds [03:18] any recommendation/experience with ldap backin dhcpd? [03:18] *backing [03:19] got thinking about how to roll out a new kickstart/mgmt LAN and thought it might be nice [07:48] ErKa (keryell@m6.wifi.enstb.org) joined #fai. [08:14] siggg (~jean@91-172-140-128.rev.libertysurf.net) joined #fai. [08:53] Mrfai (~lange@kueppers.informatik.uni-koeln.de) joined #fai. [08:59] fxcp__ (~ctp@brsg-d9bee6da.pool.mediaWays.net) left irc: Ping timeout: 480 seconds [09:12] ErKa (keryell@m6.wifi.enstb.org) left irc: Ping timeout: 480 seconds [09:20] ErKa (keryell@dhcp1.info.enstb.org) joined #fai. [09:31] fxcp__ (~ctp@brsg-d9bee6da.pool.mediaWays.net) joined #fai. [09:57] ErKa (keryell@dhcp1.info.enstb.org) left irc: Ping timeout: 480 seconds [10:54] ErKa (keryell@m6.wifi.enstb.org) joined #fai. [11:21] ErKa (keryell@m6.wifi.enstb.org) left irc: Ping timeout: 480 seconds [12:42] bayoffire (~bayoffire@213.180.168.238) joined #fai. [12:56] Felix (~Felix@pD9F50EE1.dip.t-dialin.net) joined #fai. [12:56] Felix (Felix@pD9F50EE1.dip.t-dialin.net) left #fai. [12:57] I have a question that I asked here last week about automatically reboot the client after installation. [12:57] I use pxe boot and the client boots from pxe again after installation. I found the command "fai-chboot -o" to disable that. But i think, there should be a way to do that automatically. Could anyone help me? [12:57] @sepski: are you here? [13:02] normally the install client itself does this in the task chboot [13:02] have a llok at the log file fai.log [13:03] There should be someting like this: [13:03] The install took 816 seconds. [13:03] Calling task_chboot [13:03] disable pxe config for 134.95.9.136 in hex 865F0988 [13:09] ok, I'll check that [13:10] ErKa (keryell@m6.wifi.enstb.org) joined #fai. [13:55] rgsteele||work (~rgsteele@75.147.74.137) joined #fai. [14:38] ErKa (keryell@m6.wifi.enstb.org) left irc: Ping timeout: 480 seconds [14:55] ErKa (keryell@m6.wifi.enstb.org) joined #fai. [15:20] rgsteele||work (~rgsteele@75.147.74.137) left irc: Ping timeout: 480 seconds [15:39] ErKa (keryell@m6.wifi.enstb.org) left irc: Ping timeout: 480 seconds [15:56] kumy (~malorent@193.252.149.222) joined #fai. [15:57] hi there [15:57] we're trying to set FAI to install Ubuntu Hardy Heron but we get read-only filesystem errors on boot [15:58] we've searched quite a bit but can't find why this happens [15:58] it seems the unionfs is not created by FAI [15:58] kumy: what do you use as a server? [15:59] this is fai-server 3.2.4+svn4837 [15:59] make-fai-nfsroot said everything went OK when we generated the nfsroot [15:59] which distribution, I mean? O.K. looks like ubuntu [15:59] and we have other nfsroots installing sarge and etch already [16:00] hardy is ubuntu [16:00] the server already works, it's been used to install etch and sarge for more than 3 years [16:00] yes, but you did until now only say you want to _install_ ubuntu, that must nozt be the same on the server side :) [16:00] ErKa (keryell@dhcp1.info.enstb.org) joined #fai. [16:00] what do you mean? [16:01] kumy: you always have an install server, and this server is running some distribution. and then you have an install client - the machine you weant to install [16:01] they can be different [16:01] from what I understand, once the client has a working nfsroot, it's on its own to install no? [16:01] sure, the server is running debian etch [16:01] ah ;) [16:02] and you make a different nfsroot for ubuntu? [16:02] yes [16:02] why? [16:02] you can just unpack a different base image. [16:02] hmmmm [16:02] at least I can confirm that this way works :) [16:02] we've always made one nfsroot per distribution we want to install [16:03] :s [16:03] ok, it must not be wrong, but I don't know the pitfalls [16:03] ok [16:03] so the way you do it is that you have one nfsroot for all your distros [16:03] and you regenerate the base.tgz ? [16:03] I always found it easier to have one nfsroot, so I know the basic install system is always the same and behaving the same [16:04] that sounds interesting indeed [16:04] checkout the description of the "basefiles" configspace directory in the fai-guide [16:04] year, I also prefer that way [16:05] especially when it comes to more different distributions, you don#t want to hassle with a, say centOS nfsroot or something like that ;) [16:05] hehe [16:05] well, we use kickstart for centos [16:05] and yes, your boot problem should be solved when you use the working etch nfsroot [16:06] hmmm [16:06] kumy: you don't have to, you can install all systems from a single configspace :) [16:06] ok [16:07] sounds nice :) [16:07] Felix (~FelixP@brln-4dba01bb.pool.einsundeins.de) joined #fai. [16:07] but then [16:08] how do you generate specific base.tgz without regenerating the nfsroot? [16:10] the base.tgz is not used when you have a matching file in the basefiles dir of the configspace [16:10] well the file you put in the basefiles is a base.tgz no? [16:10] as in, it's a tar file that can be used as a base system [16:11] kumy, please read the fai-guide ;) [16:11] yes, but it is named by a class [16:12] yes [16:12] yes, it's a tar file. very similar to base.tgz buit containing a different distribution [16:12] like basefiles/HARDY_I386.tgz [16:12] and HARDY_I386.tgz is the base.tgz for hardy i386 [16:12] like that, but IIRC it must be *.tar.gz (would be too easy to guess when it would be .tgz ;) ) [16:13] right, if you define the host to have a class HARDY_I386 [16:13] base.tgz will then be exchanged in favor of that file [16:14] yes I understand that part [16:14] I'm just wondering if there is a specific command to generate HARDY_I386.tar.gz [16:14] or if I have to generate a nfsroot and extract the base.tgz from it [16:15] i've made a package with some helper scripts dfor this, it's in the svn peoples tree [16:15] it's written in the fai code [16:15] yes I saw now oz_ [16:15] it's just a debootstrap; chroot apt-get clean; rm etc/resolv.conf; tar [16:16] :) [16:16] the generation for creating the hardy base tgz is nowhere in fai currently [16:16] yeah, but you need to have the debootstrap for hardy ion place :) [16:16] yes of course :) [16:16] ok thanks for your help [16:16] I will try this [16:16] :) [16:16] anyway, checkout (and report bugs) http://faiwiki.informatik.uni-koeln.de/index.php/FAI_multi-distribution [16:17] ok thanks :) [16:20] yes it works, thanks so much lazyb0y :) [16:23] when you find some time, it would be great to hear if the centos stuff works for you, too [16:24] Hallo, mein name ist felix und ich bin relativ neu "bei" fai. ich habe ein problem mit der datei /etc/fai/apt/sources.list . ich bekomme es nicht hin dass das nfsroot vernünftig gebaut wird. Es kommen nach dem punkt "Creating base.tgz" nur noch Fehlermeldungen das er den Host 192.168.1.1 nicht finden konnte. der mirror ist auf der localen maschine, mit file:/ hat es nciht funktioniert und jetzt kriege ich scheinbar die sources.list nicht rich [16:24] niert. ich habe bis jetzt alles so wie in der dokumentation gemacht. könnt ihr mir vllt sagen wo mein fehler liegt? [16:24] yay, fai installing etch, lenny, CentOS, ubuntu [16:24] neat [16:27] Felix: und was ist 192.168.1.1 bei dir? steht das irgendwo ub /etc/fai oder /etc? [16:28] hast Du den FAI Server da vielleicht mit dem fai-cd.iso von der FAI Website gebaut? oder sonst irgendwie mit der fai-cd? [16:28] das ist der rechner auf dem sowohl fai installiert ist und wo der lokale mirror liegt [16:29] pack mal bitte die ganze fehlermeldung nach paste.debian.net [16:29] und deine /etc/fai/apt/sources.list [16:29] nein, habe ihc nicht, ich habe debian lenny mit der standard installation aufgesetzt und bin dann wie in der dokumentation vorgegangen [16:30] bzw. besser: versuche mal, die sources.list, so wie sie in /etc/fai/apt/soures.list liegt, zu benutzen und schaue, ob du dann noch ein paket installieren kannst [16:30] okay, könnte aber nen bisschen dauern, der ist nicht am netzwerk angeschlossen, moment [16:30] lazyb0y: ok [16:31] Felix: wir sind so lange hier, bis wie weg sind ;) [16:31] lazyb0y: now we have a problem with the FAI_ETC_DIR variable. I wonder what is the usual way of dealing with that. As long as we used one nfsroot per distro, there was no need to play with that, but now FAI copies /etc/apt/sources.list to the target [16:31] and this doesn't work [16:31] kumy: hmm, nevery paid any attention to this variable :) [16:32] basically, didn't know it exists [16:32] it defaults to /etc on the nfsroot [16:32] so after the tarball is extracted, FAI copies /etc/apt/sources.list to /tmp/targe/etc/apt/sources.list [16:32] and it updates the hardy installation with etch packages ;) [16:32] which can be problematic [16:32] ah, ok [16:33] by looking at the code, I saw that there is a FAI_ETC_DIR which defines where to find the etc dir to copy to the target [16:33] I'm not sure this is the right approach [16:33] you need a hook for prepareapt thta copies the "right" sources list with fcopy, and runs apt-get update and skipts the internal fai task [16:33] ok [16:33] check out the sample configspace mentioned in the wiki page [16:33] ok thanks [16:34] then you don#t need to worry about FAI_ETC_DIR [16:34] ok :) [16:46] okay, die kiste will im moment rein gar nicht so wie ich, ich setze sie jetzt noch einmal neu auf und bin dann wieder hier :) [16:46] bis gleich [17:17] Felix (~FelixP@brln-4dba01bb.pool.einsundeins.de) left irc: Ping timeout: 480 seconds [17:38] siggg (~jean@91-172-140-128.rev.libertysurf.net) left irc: Ping timeout: 480 seconds [17:56] ErKa (keryell@dhcp1.info.enstb.org) left irc: Ping timeout: 480 seconds [17:56] Felix_P (~FelixP@brln-4dba1ca5.pool.einsundeins.de) joined #fai. [18:09] Nic0 (~courtel@fw.tls.cena.fr) left irc: Quit: Leaving. [19:04] Felix_P (FelixP@brln-4dba1ca5.pool.einsundeins.de) left #fai (Kopete 0.12.7 : http://kopete.kde.org). [19:06] Mrfai (~lange@kueppers.informatik.uni-koeln.de) left irc: Quit: leaving [19:43] fxcp__ (~ctp@brsg-d9bee6da.pool.mediaWays.net) left irc: Ping timeout: 480 seconds [19:51] siggg (~jean@tra78-5-88-172-128-32.fbx.proxad.net) joined #fai. [20:08] siggg (~jean@tra78-5-88-172-128-32.fbx.proxad.net) left irc: Remote host closed the connection [20:10] siggg (~jean@tra78-5-88-172-128-32.fbx.proxad.net) joined #fai. [22:07] siggg (~jean@tra78-5-88-172-128-32.fbx.proxad.net) left irc: Ping timeout: 480 seconds [23:33] ErKa (keryell@keryell.pck.nerim.net) joined #fai. [00:00] --- Wed Mar 4 2009