[06:44] siggg (~jean@tra78-5-88-172-128-32.fbx.proxad.net) joined #fai. [07:26] ErKa (keryell@m11.wifi.enstb.org) joined #fai. [07:46] Mrfai (~lange@suenner.informatik.uni-koeln.de) joined #fai. [10:16] istaz (~olivier@30.168-247-81.adsl-dyn.isp.belgacom.be) joined #fai. [10:16] hi all [10:17] stupid question : what method do you use to generate the FAI password in FAIBASE.var ? [10:18] I don't remember how i did it before; my co-worker tell me he used htpassw but it doesn't seem to work [10:18]  man mkpasswd [10:18] echo "yoursecrectpassword" | mkpasswd -Hmd5 -s [10:18] thanks a lot [10:30] if you put a file in a certain class in the directory /fai/files, the script which fcopy it should be compulsorily in the same class? [10:31] You may also put the fcopy command in the class DEFAULT, then this one fcopy commands can handle you templates for all classes. [10:34] only in class DEFAULT? cause I have two différent version of my file /etc/cups/printers.conf one in class SALLE_9 and one in class SALLE_3 and I have put a fcopy in an script in my class MAIN (to which every computer belongs) and it didn't copy anything [10:35] It's ok to out the fcopy command in your class MAIN. Read shell.log to see why this fcopy did not anything. [10:37] permission denied. [10:37] ok it's my fault /o\ [10:37] which permission does fai need to acceed the files? [10:38] *access [10:48] is it possible to order the nics in a different way using fai config ? i have one onboard and one pci. card the onboard have pxe, but the pci get eth0 after the kernel boots [11:31] istaz: read and execute [11:31] sep: known problem [11:32] sep: not easy to fix, try to influence the order of modules that are loaded by the kernel. This is done inside the initrd [11:32] but fai runs as root in the nfsroot - so it's a bit strange - sure that the target is mounted read-write, and you don't have some other strange problem? [12:00] Mrfai: for all user? ? [12:03] istaz: as I said above: fai runs as root on installation, so, not for all but only for root... [12:04] lazyb0y: I don't have the no_root_squash option enabled so it make sense that it doesn't work [12:05] in fact since I stupidly created my user on the server as "fai" I forgot that i wasn't the same user accessing the data [12:06] istaz: when you don't have no_root_squash for the nfsroot (ineterstiung question: why???), I guess you have many other problems, haven't you? [12:07] and when your server has a normal user account called fai, you'll also have trouble saving logs and calling chboot... [12:07] fai-chboot, that is [12:14] lazyb0y: no idea why, I didn't write the config file, I juste took up the maintaince of the system wich was designer more than 2 years ago [12:16] and it doesn't seem like it's using fai-chboot [12:16] fai was at version 2.10 [12:18] free-x (~oleg@site.lycos.de) joined #fai. [12:20] lazyb0y: in fact I don't even know what chboot is for [12:21] Action: istaz is doing a man fai-chboot [12:23] oh it's for network booting, we don't use that, we boot via CD. PXE doesn't work well with our optical fiber network [12:24] Mrfai (~lange@suenner.informatik.uni-koeln.de) left irc: Quit: leaving [12:27] sugarmice (~timc@chiark.greenend.org.uk) joined #fai. [12:27] Morning guys. I've got an odd problem with the way certain machines are built by our FAI server, and I'm somewhat confused by it [12:28] 99% of the time, it builds machines absolutely correctly [12:28] But some machines, while it builds without errors, the resulting machine can't configure its network interfaces [12:28] And this appears to be because /dev/shm is completely empty (mounted, but empty) [12:29] Anyone have any idea what I need to look at here? This is FAI 3.1.8, building 32-bit etch machines [12:39] istaz: ah. [12:40] sugarmice: random problems are great :) [12:40] sugarmice: so, it's the same machines, and the same configs which sometimes work and sometimes don't? and their install logs look always "correct"/without errors? [12:43] The state seems to be stable; a give machine will either always work, or never work. [12:43] It looks like some sort of race condiion [12:44] I've just looked at a problematic machine, and the problems seems to be that /etc/init.d/ifupdown is not being run [12:44] sugarmice: you install all of them at the same time? [12:44] No [12:52] Or if it is being run, it's failing. This may not be a FAI bug at all, of course - it may be a race condition in the standard etch distribution [12:58] I don't seem to be able to find any error messages printed by anything in /etc/rcS.d though - where does that stuff go? [13:03] hum ... I created a password the way MrFai indicated but I noticed something strange [13:03] if I do a : fai@di-fai:/fai/config$ export ROOTPW=$1$Yzigllbq$xGz80FWIL7q.kAGCMqnQd/ [13:03] then fai@di-fai:/fai/config$ env |grep ROOT [13:03] ROOTPW=.kAGCMqnQd/ [13:04] it get trunkated [13:05] if I do a : fai@di-fai:/fai/config$ export ROOTPW=\$1\$Yzigllbq$xGz80FWIL7q.kAGCMqnQd/ [13:05] oups [13:06] if I use \$1\$ it works [13:11] sugarmice (~timc@chiark.greenend.org.uk) left irc: Quit: This message intentionally left blank [13:18] ok I just had to use ' instead of ". Where are you basic bash knowledges when you need them? [13:52] cd [13:52] err [13:55] chtp (~ctp@p578b5976.dip0.t-ipconnect.de) joined #fai. [13:58] nabend. habe einige probleme ein 32 bit nfsroot zu bauen auf einem 64 bit system. der client bekommt immer 64 bit kernel per pxe (pxelinux.0), obwohl ich fai-setup aufrufe mit "FAI_DEBOOTSTRAP = .. -- arch i386" in /etc/fai/make-fai-nfsroot.conf. hat jemand eine idee, was ich noch beachten muss? [13:59] chtp: benutze ein 32 Bit system zum bauen der nfsroot... [13:59] dann auf den 64bit server kopieren. [14:00] oz_: habe dummerweise kein 32 bit system mehr :-( [14:00] chtp: ? warum das eine 32bit nfsroot? [14:00] s/das/dann/ [14:00] oz_: hm, dieses --arch flag ist doch genau dafür gedacht oder nicht? [14:01] oz_: für embedded devices. auf den will man aber nicht wirklich ein fai bauen. [14:02] chtp: na, ein 32 bit system ist schnell beschafft, oder? [14:02] das andere wär eine komplizierte sache [14:03] oz_: ich überlege gerade ein chroot mit 32 bit aufzubauen und darin fai zu installieren. war wäre denn dein anderer vorschlag? [14:06] chroot oder eben ne andere 32 bit kiste [14:20] ErKa (keryell@m11.wifi.enstb.org) left irc: Ping timeout: 480 seconds [14:37] ErKa (keryell@keryell.pck.nerim.net) joined #fai. [15:09] sepski (~sep@217.17.211.51) joined #fai. [15:29] ErKa (keryell@keryell.pck.nerim.net) left irc: Ping timeout: 480 seconds [16:35] just a tought (I don't know if it's has already been fixed in the latest version) : I have seen that you can now put your base.tgz [16:36] in basefiles/ [16:36] but if you provide a different base.tgz you probably also want a different sources.list [16:37] I modify mine by hand but it would be nice to have it done automatically [17:30] chtp: ich verstehe dein problem nicht ganz. Du sagst, du hast probleme beim nfsroot bauen, und dann "der client bekommt einen 64 bit kernel" - das nfsroot bauen hat doch mit pxe nix zu tun?! [17:30] ein 32 bit nfsroot sollte kein problem sein, wenn man die --arch setzt in den fai debootstrap options [17:31] und welchen kernel dein system per pxe bekommt, stellst du am besten in der pxelinux config ein [17:31] hmm, ah, moment, und da machts auch schon klick vielleicht :) [17:32] welches fai nutzt du denn? 3.2.x? [18:11] ErKa (~keryell@keryell.pck.nerim.net) joined #fai. [18:56] sepski (~sep@217.17.211.51) left irc: Quit: Leaving [19:46] chtp (~ctp@p578b5976.dip0.t-ipconnect.de) left irc: Ping timeout: 480 seconds [20:27] ErKa (~keryell@keryell.pck.nerim.net) left irc: Ping timeout: 480 seconds [22:40] siggg (~jean@tra78-5-88-172-128-32.fbx.proxad.net) left irc: Ping timeout: 480 seconds [23:50] istaz_ (~olivier@177.236-243-81.adsl-dyn.isp.belgacom.be) joined #fai. [23:55] istaz__ (~olivier@18.245-242-81.adsl-dyn.isp.belgacom.be) joined #fai. [23:57] istaz (~olivier@30.168-247-81.adsl-dyn.isp.belgacom.be) left irc: Ping timeout: 480 seconds [23:58] istaz_ (~olivier@177.236-243-81.adsl-dyn.isp.belgacom.be) left irc: Ping timeout: 480 seconds [00:00] --- Tue Apr 1 2008