[00:02] Can I rm initrd.img.old and vmlinuz.old from / ? [00:02] those should be mere symlinks. [00:03] so, yes, if you really wish to. If you use GRUB (which one does by default), you can use tabbed path-completion at the GRUB prompt anyhow. [00:04] what is the link between these files and GRUB ? [00:05] those symlinks point to their respective files in /boot [00:05] they only exist if you either 1) install another Debianised linux package using dpkg, or 2) create them manually [00:06] GRUB is the default boot loader, and its configuration file uses those symlinks. Those entries normally point to the second set of linux images. [00:08] Is the second set a "kind of emergency files" ? [00:09] yes, the entries point to the older, previously installed linux set. [00:09] i.e., "backup" [00:10] Did GRUB will automaticaly switch to it in case of a bad luck ? [00:11] no. [00:11] I did a updated from 7.04 to 7.10. And there is now a initrd.img -2.6.20-16, initrd.img -2.6.20-14 and initrd.img -2.6.20-16.bak. [00:11] yes, that's correct. [00:12] I just want to understand what's "under the hood" [00:12] what would you like me to explain regarding those three files specifically? [00:14] I just started to explore files and folders from / . Now I have to read http://www.gnu.org/software/grub/ ;) [00:15] Do I have to keep the old one (initrd.img -2.6.20-14 and initrd.img -2.6.20-16.bak) ? [00:16] I thought there was "cleaning" after an upgrade... [00:18] 2.6.20-16 is a newer package than 2.6.20-14. There are numerous security errata applied. [00:18] you want to understand what's under the hood, read the linuxfromscratch howto :) [00:18] where??? [00:18] then you'll really understand :) [00:18] web search it [00:18] You may choose to remove the 2.6.20-14 linux packages if 2.6.20-16 does not introduce any regressions. [00:18] web ?? (I'm jocking) [00:18] I do not recommend removing the backup initramfs image /ever/. [00:18] i don't say "google it" anymore... [00:19] i use other search engines too afterall [00:20] Is it the right channel to LEARN BY QUESTIONS, or am I to boring ? [00:21] well you should learn by reading first [00:21] and then ask questions [00:22] Thanks. Humility is the path to knowledge... [00:22] this prolly isn't the right channel .. but i don't know what would be the best for that [00:22] except for #gnulinux101 (sadly it doesn't exist) [00:23] i'm always willing to help folks learn stuff when i have time.. unless they are going to work with me on open source projects [00:23] then i spend all sorts of time :) [00:23] see you soon. === valles_ is now known as effie_jayx [03:08] We have 15 old PII 400 with 512MB RAM, including hard drive, that we wanted to recycle at school. [03:09] What would be the best? A powerful server with LSTP and light clients or a medium server with heavy clients and LDAP and MySQL? === effie_jayx is now known as effie-jayx === meduxa is now known as toscalix [10:15] Damned, just recently I found a link to an edu-something site, which had the recent version of libflashsupport as a .deb package, but I am unable to find that site again. The version from vdbonline.net is over 1 year old, and a recent version is supposed to operate more stable. Anyone seen the site I mean? [13:00] some of my LTSP clients don't start their Xserver anymore since updating the server to gutsy [13:01] locally X works with the i810 driver - I tried changing it to 'intel' [13:02] after the boot process, the system stops with blinking a '-' in the upper left corner of the display [13:03] Ctrl-Alt-F1 - is there any error-message? [13:04] nope, just the login prompt [13:05] I don't know where to look for logs :/ [13:06] /var/log/Xorg.0.log ? [13:06] Joris_, some intel cards try to forcefully run at 32bt colordepth but aret capable of that ... [13:06] try X_COLOR_DEPTH=24 for them [13:06] ogra: tried that too, sorry :/ [13:06] Bauer|: that's on the server? [13:07] Bauer|: I mean LTSP server, xorg client [13:08] ogra: 16bit even [13:08] I am thinking the client [13:09] how would I login into it? [13:11] now thats a good question :p i don't know :p i would think ogra knows? [13:11] define SHELL_07=ldm SHELL_02=shell [13:11] that spawns a shell on tty2 [13:11] in lts.conf ? [13:11] ad keeps to try to configure and start X on tty7 [13:11] yep [13:14] [00:02:A5:23:FA:85] [13:14] SHELL_07=ldm [13:14] SHELL_02=shell [13:15] is that correct? it appears not to work [13:20] thats correct [13:20] should work [13:21] doesn't... login on tty1, failed X on 7 [13:22] tty2 [13:22] ? [13:23] ctl+alt+f2 [13:23] err [13:23] yep [13:23] there should be a rootshell running [13:23] 1, 2, 3 are empty [13:23] then yur lts.conf isnt read or the MAC is wrong [13:24] hmm, mac = copypaste, so that should be ok [13:25] if lts.conf isn't read that could explain wy setting the xserver or colordepth doesn't solve anything [13:25] does your lts.conf lie in the path thats defined in the filename directive in your dhcpd.conf ? === Janet32766_ is now known as Janet32766 [13:25] thats where it should reside [13:26] you do upgrade you image after editing lts.conf? [13:26] Bauer|: no, I didn't' - should I? [13:27] i have to rebuild my image after editing lts.conf [13:27] ogra: no, it doesn't: option root-path "/opt/ltsp/i386" and /var/lib/tftpboot/ltsp/i386/lts.conf [13:27] Bauer|, not if you have your lts.conf in the right path [13:28] Joris_, "filename" not root-path [13:28] root-path isnt used at all in gutsy ltsp [13:28] (only there for backwards compatibility) [13:29] tought so, it's commented in that file there :) [13:29] filename "/ltsp/i386/pxelinux.0"; and filename "/ltsp/i386/nbi.img";, so it should be ok? [13:30] right [13:32] hmm, thats strange [13:33] trying with inotify o the file [13:33] you didntput links into that folder or something i suppos [13:33] e [13:33] (tftp isnt capable of following links ... ) [13:33] I did, to figure out another problem - but removed them again [13:33] (especially not outside its own root (/var/lib/tftpboot/)) [13:35] according to inotify, my lts.conf is not being read :s [13:36] (iwatch -e access /var/lib/tftpboot/ltsp/i386/lts.conf /opt/ltsp/i386/etc/lts.conf does not register any reads- [13:37] in.tftpd[1240]: RRQ from 192.168.0.78 filename /lts.conf [13:38] in.tftpd[1240]: sending NAK (1, File not found) to 192.168.0.78 [13:39] something is really really wrong [13:40] without changing anything, the client now does request the lts.conf [13:40] and is now unresponsive, blinking with the caps and scroll lock [13:41] maybe it's better to reinstall the server completely [13:42] (screen hangs on kubuntu progress bar btw) [13:42] its missing the path [13:42] filename /lts.conf must be filename /ltsp/i386/lts.conf [13:43] are you sure the dhcpd you configure is actually used ? [13:43] good question [13:43] paste your config to a pastebin [13:47] http://pastebin.com/m67a7298b [13:48] and your tftp line in inted.conf has "-s /var/lib/tftpboot" at the end ? [13:48] yes, can you refresh that url? [13:49] open http://pastebin.com/m54c93530 rather :) [13:49] whats pxelinux.0\377 ?? [13:49] thats broken [13:50] also: ls -la /var/lib/tftpboot/ltsp would be intersting [13:50] I tried copying the file because some clients request that [13:50] no, thats an internal code of PXE [13:51] ah, oh :/ [13:51] that's also giving me problems... [13:51] show me ls -la /var/lib/tftpboot and ls -la /var/lib/tftpboot/ltsp [13:52] http://pastebin.com/m1284b79b [13:52] (staring on line 54) [13:53] yeah, nothing suspicious [13:53] make a backup of your lts.conf, wipe the i386 dir and run: sudo ltsp-update-kernels [13:53] then copy the lts.conf back [13:53] that should clean up anything you could have broken [13:55] ok :D [13:56] boots without the caps/scroll blink again, but still no xserver [13:56] shell ? [13:56] neither :( [13:57] why did you put the |uniq in the lts.conf part ? [13:57] whitespace [13:58] ergh [13:58] there are no double entries of any kind I think [13:58] sillyness [13:58] * ogra headdesks ... [13:59] s/SHELL/SCREEN/ [13:59] ouch :D [13:59] blind me [13:59] great [14:00] you can drop SOUND,LOCALDEV and SYLOG_HOST ther are set by default to these values [14:00] *they [14:03] ughm [14:03] [00:02:A5:23:FA:85] [14:03] SCREEN_07=ldm [14:03] SCREEN_02=shell [14:03] right? [14:03] yeah [14:03] doesn't work :/ [14:04] but the file is requested, according to inode [14:04] did it fix your PXE error on the other terminals ? [14:05] nope, no idea how [14:05] any info in the logs ? [14:06] with your triple -v you should see everthing tftpd does [14:07] just the not found \337 [14:08] RRQ from 192.168.0.78 filename /ltsp/i386/boot/pxelinux.0\377 -> NAK [14:08] your is clean now btw ? [14:08] err [14:08] your /var/lib/tftpboot/ltsp/i386/ [14:08] I think so [14:08] I ran the kernel update thing [14:09] whats boot ?? [14:09] thats shouldnt be there [14:09] a symlink to . [14:09] did I break that too? :( [14:09] but you just wiped that dir [14:09] how can it be there again [14:10] I don't know [14:10] there should only be three links (vmlinuz, initrd.img and nbi.img) [14:10] manually removed it, ltsp-update-kernels and now itt's gone [14:10] and one subdir pxelinux.cfg [14:10] http://pastebin.com/m54c83221 [14:11] no pxelinux.0? [14:11] sure [14:11] the dir looks good now [14:12] I'll retry [14:12] what's wrong with that /ltsp/i386/boot/pxelinux.0\377? [14:13] client boots, but no X and no shell [14:13] well, i wonder how you get the boot in there [14:13] it shouldnt be there [14:14] something is really wonky, either in your chroot or with the setup of your server [14:14] and NO /var/lib/tftpboot/ltsp/i386/lts.conf read!!?! [14:14] pfff [14:14] I think something went really wrong with the gutsy upgrade of this machine [14:14] you are not running another dhcpd in your network or so ? [14:15] yes, but it is pointing to me as it's next-file [14:15] next-server [14:15] upgrade ? [14:15] or something [14:15] but you rebuilt the chroot as advised i hope [14:15] it was a 6.06/7.07 and updated it to 7.10 [14:15] certainly, I rebuilt the chroot [14:17] hmm [14:17] do you have any other tftpd running ? [14:17] on the network? not sure, but not on this server [14:17] ok [14:18] how does your /opt/ltsp/i386/boot/pxelinux.cfg/default look like ? [14:18] (paste here, should be one line) [14:18] root@dotkomserver:~# cat /opt/ltsp/i386/boot/pxelinux.cfg/default [14:18] DEFAULT vmlinuz ro initrd=initrd.img quiet splash [14:18] looks fine [14:19] /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default has the same content i suppose [14:19] identical [14:21] i really dont understand how it gets the boot in there :/ [14:21] it could be I did it, but I don't tremember [14:22] ogra: I can reinstall the server :? [14:22] directly from 7.10 [14:22] yes, but i'dlike to find the cause :) [14:23] is there a way to run ltsp 4.1 and 5.0 together? [14:24] cause i need ltsp 4.1 for my netvista devices and the other pcs from the system running under 5.0 [14:24] mcfloppy_, there surely is, but i bet its a lot work to set up the servers right [14:24] ogra: I'd be more than happy to dig further into this, but: [14:24] not today, I have to get going [14:25] and also: they are depending on me getting a lot of clients functional, I don't know how long the current situation can persist [14:25] dpkg -l ltsp-server ? [14:26] it's installed [14:26] and chroot /opt/ltsp/i386 dpkg -l ltsp-client-core [14:26] 138 files [14:26] i want to compare te versions :) [14:26] ogra hmm kay, [14:26] what would you do? [14:27] http://pastebin.com/m741771bf [14:27] mcfloppy_, well most easy would be to have two different networks (a NIC each) for the different implementations and direct either to different files in the dhcpd.conf [14:28] Joris_, ok [14:28] orga du sprichst doch deutsch, oder? [14:28] if oyu start splitting on a higher level it gets more tricky [14:28] mcfloppy_, jup [14:28] ogra: you can email me at my nickname @v5.be... I'll come back to this channel to haunt you some more later [14:28] ogra bitte lass uns das in deutsch klären... [14:28] query oder so [14:29] #edubuntu-de :) [14:29] ogra: thanks and have a nice weekend [14:29] ciao [15:26] Heya === Janet32766_ is now known as Janet32766 === nixternal_ is now known as nixternal [22:32] Is there a grub boot option in Ubuntu/Edubuntu Gutsy to boot the server kernel directly? I need this for correct hardware detection for my Proliant servers... [22:33] as in, from the live/install cd