[02:03] This is my maiden voyage into the world of instant messaging & I have no idea how the system works. [02:03] I installed the deb package for xchat-gnome, then xchat and I seem to be broadcasting to this group right now. [02:03] Is that correct? [02:04] I take it other listeners are informed somehow by their system when a new message has been posted. [02:05] Then they may choose to look at the new input or not. If they do look at the new message, they may or may not respond. Right? [03:22] Evening all [03:23] pianonut: We see what you type [03:23] And you see what we type :) [03:33] That part I know. === n2diy_ is now known as n2diy [08:30] Hello! Did anyone have expiriense with LTSP5 in Edubuntu Gutsy? [08:31] not in gutsy, but I have played with LTSP [08:31] what is your issue? [08:33] I just plan to use it. Will it work correctly with Xeon Quad core? [08:34] that is a kernel issue. If Ubuntu/Edubuntu runs correctly on it without LTSP, it will work find with it [08:38] And one more question. Thin clients need a RAM, isn't it? [08:38] yes, due to the applications they are running [08:39] basically, the more RAM the happier you are as a person, but then your server isn't swapping [08:46] Thank you, Burgundavia === [1]Netham45 is now known as Netham45 === RichEd-1 is now known as RichEd [11:30] hi ogra_cmpc [11:30] hey [11:31] just checked my tavel details ... 29h30 from my house to boston [11:31] eeek [11:31] mine must be below 13h this time [11:31] and could not get any other seats apart from middle of the normal rows [11:31] ughh [11:31] 8h flight, 3h trainride plus hanging around at the aitrport [11:32] not too bad .. [11:32] but you switch planes, dont you ? [11:32] hi all. i'm still getting that error checking out the bzr doco. [11:32] kgoetz@wesnoth:~/public_html$ bzr branch http://bazaar.launchpad.net/~ubuntu-core-doc/ubuntu-doc/edubuntu-hardy [11:32] bzr: ERROR: Invalid http response for http://bazaar.launchpad.net/%7Eubuntu-core-doc/ubuntu-doc/edubuntu-hardy/.bzr/repository/inventory.knit: Bad status line received [11:33] anyone got a clue? [11:33] ask in #bzr ? [11:33] ogra_cmpc, ok, i'll head in there [11:33] they migth know more [11:35] * RichEd wonders if ogra's typing dyslexia tday is accountable to mental fatigue or adult fingers on the little classmate keyboard [11:35] both i guess :) [11:38] * ogra_cmpc needs another reboot [13:19] for the logs: my issues with bzr revolve arround my http-proxy. bypassing the proxy bzr is working [13:30] oh, is lists.ubuntu.com laggy today, I answered 5 minutes ago to RichEd's mail and my mail isn't on the list yet :) [13:30] usually it takes 5seconds :) [13:33] release announcements come via there? [13:33] * Kamping_Kaiser wonders how big the hardy docs will be [13:34] Kamping_Kaiser: A4 ? [13:34] DeMoNSeEd, all mailing list mail comes via there ... (including the announcement lists indeed) [13:34] RichEd, yay for standards [14:00] Morning all [14:11] hey ogra [14:11] how ya been [14:28] RichEd-1 hi [15:01] i'm still somewhat of a noob and i'm trying to installed gutsy server (on new HP proliant ML 350) and the install fails at "build chroot". any suggestions as to why and how to fix? just start the install again? or is it a known issue? [15:01] s/installed/install [15:10] Hi, anyone around to answer questions [15:10] ? [15:10] i: yes [15:11] musashi1: Define "fail"? Does it give you an error message? [15:11] OK, have just recently upgraded (actually, fresh install) to Gutsy... [15:11] Feisty server was more or less working fine [15:12] Problem I'm having now is that I plug a USB flash drive into the server and it recognises fine ... but plug the same drive into any of the thin clients and no response [15:12] Nothing in server's mtab or /media [15:13] Try creating a /var/lib/tftpboot/ltsp/i386/lts.conf that contains: [15:13] [Default] [15:14] LOCALDEV=True [15:14] See if that makes a difference. [15:14] OK, trying ... [15:15] Heya [15:16] Nope, nothing [15:16] sbalneav: yes, i don't recall the exact warning but it's a nice red screen saying to the effect "installing failed at step build ltsp chroot you can try again" trying again also fails --> returns to error screen. [15:17] sbalneav: i did just start the install again from the beginning so i'll see what happens [15:18] i_: Did you restart the terminal? [15:18] Yes, 2 terminals, neither worked [15:18] You might want to run through: http://wiki.ubuntu.com/DebugLocalDev [15:18] OK [15:21] Does it matter that lsmod | grep fuse returns with a 1 as the final digit rather than a 3 as shown on that page? [15:21] No, just so long as it returns the line. [15:21] That means the module's loaded [15:21] OK, still going ... [15:23] All good up to step 4 ... continuing [15:26] OK, having a problem @ Step 1: Setting a root password in the LTSP chroot [15:27] Set the root password successfully but then can't log in on the text console of the terminal, even on the server - any ideas? [15:27] Username is "root", right? [15:29] sbalneav: Hello? [15:30] right [15:30] OK, so can't login at the console - any idea what the problem might be? [15:30] Did you rebuild the image with ltsp-update-image? [15:30] At what stage was I supposed to do that? [15:31] After the password change [15:31] Up on the server [15:31] How do I issue that command? [15:31] ltsp-update-image :) [15:31] as root [15:31] Sorry! [15:32] OK to sudo, or do I have to chroot? [15:33] sudo ltsp-update-image [15:33] jsgotangco: sorry dude leavin for airport [15:33] bye guys [15:33] OK, doing that now - 27% [15:33] bye [15:33] sbalneav ogra see you in boston [15:35] It's still saying that the login is incorrect... [15:38] Have you rebooted since you rebuilt the image? [15:38] No - shall I do that? [15:39] yes [15:41] sbalneav: I've rebooted and I still can't login as root on the console. [15:45] ok, here's the complete overview of the procedure. [15:45] on the server [15:45] sudo chroot /opt/ltsp/i386 [15:45] passwd [15:45] [15:45] [15:46] exit [15:46] sudo ltsp-update-image [15:46] wait [15:46] when done, reboot [15:46] ctl-alt-f1 [15:46] text login as root/password [15:47] OK, that's exactly what I did before but I'm in the process of doing it again (updating image @ 18%) [15:48] Image @ 76% [15:49] Rebooting ... [15:50] sbalneav: Once again, I cannot login as root from the console ... [15:50] Changing the password is fine - don't worry, it is the password for root that is being changed [15:51] It just doesn't work from the console [15:52] okay, build ltsp chroot failed again. is there anything i can check to see what it might be? i think i will also burn a new cd [15:52] i_: So, on the thin client, you're pressing control-alt-f1 [15:53] getting a text login screen [15:53] No, I've done all of this on the server [15:53] Tried on the client earlier [15:53] Well, that's wrong [15:53] Same problem [15:53] you do it on the thin client [15:53] on the thin client, control-alt-f1 [15:53] login as root/password [15:54] OK, it's working on the thin-client now [15:54] Apologies for that. [15:54] ogra, ogra_cmpc: Can you accept a mail I sent to the mailing-list with the wrong mail account or shall I resend ? [15:55] which ml? [15:55] edubuntu-devel [15:55] ok [15:55] looks like I'm subscribed with @stgraber.org instead of @ubuntu.com, I'm changing that now [15:59] argh, in fact it seems that the mail address is correct so why hasn't the mail reached the ML (my SMTP server logs say it was correctly queue on lists.ubuntu.com MX ...) [16:00] i dont see anything in tewh queue [16:01] ok, I'll send it again and if it doesn't show up in the hour I'll ping a sysadmin [16:01] sbalneav: OK, stuck @ Step 3: Did the ltsp udev rules fire? ... Checked flash drive in server and it shows up as sdb1 ... just in case, I'll repartition it anyway and see if that helps [16:01] yeah, looks like something thats worth an rt ticket [16:02] stgraber, lists.ubuntu.com ist very slow this days [16:04] yes, but someone sent a mail at 16:30 and it's now on the list, mine was sent at 14:00 [16:06] hola [16:06] una pregunta [16:06] english better¿? [16:08] i want to use the same account with my pupils, but firefox, said that i have to close the program to load it again from another computer [16:08] how can i fix that [16:08] ?¿ [16:08] you cant [16:09] firefox, openoffice and gnome really freak out if several processes use teh same config [16:09] aha [16:09] create a user per client [16:09] or so [16:09] and, using another web browser?¿ [16:10] not sure if there are any that can cope with that [16:10] puff, the problem is my pupils will not remember user and password [16:10] use autologin ... its a bit work to set that up for every single client though [16:10] So, use autologin [16:13] ok, but the idea is to have a different desktop for every level [16:13] with specific icons for each one [16:14] What do you mean, a different desktop for every level? [16:14] yes i use edubuntu [16:15] so, i have exercisses for 3 grade in primary, prepared with icons in the desktop [16:15] and a account called "3grade" [16:16] Well, you can't run multiple terminals off of one login. [16:16] the log in by that account and uses the same made desktop [16:16] Gnome, openoffice, and firefox do not like that. [16:17] aha [16:17] and, may i use the same desktop for a group [16:17] ?¿ [16:17] No [16:17] Well, you could set up a group in sabayon [16:17] but you'll still need individual userids [16:17] is that gentoo?¿ [16:18] no [16:18] Sabayon's a tool to allow you to customize desktops [16:18] It can be installed in edubuntu [16:18] but you can't get away from creating multiple userids [16:20] sbalneav: Step 2 (dmesg) shows that the client recognises the plug event but the ltsp udev rules don't seem to be firing; I've reformatted the flash drive twice, once using fdisk and mkdosfs as suggested in your page, and also using GParted to see if that helped ... no result [16:21] This flash drive used to be recognised fine by both server and clients, when running the Feisty server [16:21] bryang: the other console is empty (i.e. no infor or error messages). [16:22] bryang: i am going to reboot and check the cd for errors [16:23] bryang: wait, f4 has a bunch of output [16:24] i_: is there a /var/run/drives? [16:24] Yes (on the client) [16:24] bryang: ltsp-client-builder failed with error code 1 [16:25] there is a bunch of other "stuff" there. some about packeage doesn't exist - skipping [16:25] is there any subdir underneath /var/run/drives [16:25] one about siocsifadder device doesn't exist. i have no idea what that means :) [16:26] musashi1: Something's wrong with your network interface [16:27] sbalneav: any idea what? the dhcp part went off without a hitch. are we talking bad nic or something else? [16:27] No idea [16:27] sbalneav: There are 4 (cdrom, floppy, and 2 scsidisks) [16:28] sbalneav: Interesting result when I try to attempt Step 4: Can you manually issue a mount command? ... [16:29] The command results in attempting to connect to the server but when I'm asked to supply the root password, permission is denied... [16:30] you need to be logged in on the GUI screen for that [16:30] else teh ssh tunnel isnt established and iut asks for teh root pw [16:31] I'm already logged into the GUI ... just found one of the problems... changed root password using sudo passwd root and now granted permission but ... [16:32] nooo [16:32] As mentioned in Step 4, it's resulted in an error ... [16:32] there is no root user involved anywhere [16:32] if you get asked for a root PW the tunnel isnt working [16:32] Sorry ogra, I meant I changed the root password on the server ... [16:32] OK, here's the error I got: [16:35] ogra_cmpc: Where exactly am I supposed to issue the command from? [16:35] the console of teh client [16:36] Ok, just tried that and it says ssh: server: Name or service not known [16:36] but kdm is running ? [16:36] err [16:36] ldm [16:36] and you are properly logged in through it [16:36] How can I check? [16:37] ps ax|grep ldm [16:37] on the client console [16:37] its the default login manager [16:37] and one of teh core parts to make ltspfs work [16:37] OK, got a standard result for ldm [16:38] whats a standard result ? [16:38] is it running or not? [16:38] 7218 pts/2 S+ 0:00 grep ldm [16:38] no ldm running [16:38] thats your problem then [16:38] So what do I do now [16:39] without the ssh socket ldm creates localdev wont work [16:39] well, teh question is how you got in that state [16:39] OK, I was originally running Feisty - everything was more or less OK [16:39] did you tweak around in lts.conf ? [16:40] No - not on Feisty at all [16:40] so are you on feisty or gutsy ? [16:40] * ogra_cmpc doesnt understand [16:40] Just tweaked the lts.conf in /var/... today for the first time - but never had flash drives working since upgrading to Gutsy [16:41] how did you upgrade ? [16:41] bryang: cd checks out okay. assuming that test works. [16:41] did you properly rebuild the client root with ltsp-build-client ? [16:41] Used the alternate CD first ... but didn't allow it to download new packages from the net [16:42] That resulted in server that could only host 6-8 clients - and very poorly at that [16:42] The remainder of the clients wouldn't even "see" the DHCP server when attempting to connect via the network [16:43] Something's wrong with something [16:43] I run 50 clients off my server. [16:43] One of my servers, I should say [16:43] No, but now I did a fresh install of Gutsy and all 19 clients are working fine, except for this flash drive problem [16:44] Are the users members of the fuse group? [16:44] When I say working fine, I mean they all connect and login - haven't really used it long enough to see if there are any other problems [16:44] All users are members of the fuse group - checked that as per your instructions [16:45] so thats a fresh gutsy install atm ? [16:45] or an upgraded one ? [16:45] Yes, that's a fresh install - there's only one thing I messed around with [16:45] To save the original user accounts, I made a backup of /etc ... I already had /home on another partition ... [16:46] are you using ldap ? [16:46] When I rebuilt the server with the fresh Gutsy install ... [16:46] No LDAP [16:46] well, check that the number for teh fuse group wstill matches whats set in /etc/passwd and /etc/grou would be my first guess [16:47] ... OK, checking... [16:48] hmm, but still, no ldm is a bad thing and thats surely not caused by teh servers passwd file [16:48] OK fuse group ID: 117 ... [16:49] and /dev/fuse has teh right perms [16:49] (owned by the fuse group) [16:49] No, owned by root and group = fuse [16:50] good [16:50] thats all fine then [16:50] so if ldm isnt running, i wonder how you log in on your clients [16:51] Pretty quickly, actually! Faster than in Feisty... [16:51] i assume you had a graphical login window [16:51] Yes [16:51] hmm [16:51] What does the date and time look like in the bottom right? [16:51] do you have SCREEN_07=startx or something similar werid in your lts.conf? [16:52] Of the client login screen? [16:52] yeah [16:52] 25.10. 18:47 [16:52] no ip ? [16:52] Sorry, IP is there as well 192.168.0.250 [16:52] yeah, ldm's running [16:53] and (ltsp) or so in the front [16:53] Yes ltsp (and not the name of the server as it used to be in Feisty) [16:53] good, then ldm is running [16:53] i wonder why you didnt see it in teh clients processlist [16:53] I'll try again [16:54] 7723 pts/2 S+ 0:00 grep ldm [16:55] Where are you running this command? [16:55] Terminal on the client [16:55] In the text screen? ctl-alt-f1? [16:55] Not console (I mean Ctrl-Alt-F1) [16:56] Sorry, I mean I'm running it from Applicatons-Terminal [16:56] nah [16:56] right [16:56] that's wrong [16:56] hehy [16:56] you need to do it on the ctl-alt-f1 [16:56] OK ... [16:56] As root? [16:56] when you run it on the gnome-terminal, you're on the server [16:57] since the gnome terminal's running on the server, you're looking at server processes [16:57] everything you do on the graphic login is running on the server, NOT on the thin client itself. [16:57] as root, yes. [16:58] OK, gettinga lot of output, what are you looking for? [16:58] ldm vt7 :6 [16:58] Right, got that [16:58] ok, so you're running ldm [16:58] Good stuff [16:59] I've noticed that the fuse group isn't listed in /etc/passwd [16:59] that's because it's a group [16:59] so it's listed in /etc/group [17:00] so, on the thin client [17:00] in ctl-alt-f1 [17:00] yes ... [17:01] you should have a /var/run/ldm_socket something file, yes? [17:01] checking .. [17:01] hey sbalneav. I'm having trouble figuring something out, how does the client know that it should boot from the 386.img file? the only reference I can get to it is in /etc/inetd.conf. not in dhcpd.conf or pxelinux.cfg. [17:01] Yes [17:01] highvoltage: it depends what port you go to, what image you get [17:02] ldm_ocket_vt7_192.168.0.254 [17:02] so 2000 is i386 [17:02] ldm_socket_vt7_192.168.0.254 [17:02] ok, so on c-a-f1, [17:02] if you do a: [17:03] ssh -S /var/run/ldm_socket_vt7_192.168.0.254 192.168.0.254 ltspfsmounter /tmp add [17:03] what happens? [17:03] sbalneav: aaaaaaaaah [17:05] Tried to write ... [17:05] sbalneav: how do the clients know that they should look at port 2000? is it built into the kernel? [17:05] fuse: failed to exec fusermount: Permission denied [17:05] Error: /tmp/.s1081-ltspfs/tmp is not mounted [17:08] ok [17:08] failed to exec fusermount: Permission denied [17:08] on the server [17:08] as a user [17:08] On the client as a user [17:08] do an "id" [17:08] either or [17:08] paste the results [17:09] uid=0(root) gid=0(root) groups=0(root) [17:09] No [17:09] on the graphical login [17:09] logged in as a regular user [17:11] To make this a little easier, I'm just going to install XChat on the server so that I can paste the result [17:11] I'm using my own laptop for this so far [17:12] (I mean this chat, not the rest of the stuff!) [17:13] Right this is i_ here: [17:13] Here's the result: [17:13] s1081@BSCL02-SERVER:~$ id [17:13] uid=1081(s1081) gid=1082(s1081) groups=4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),29(audio),30(dip),46(plugdev),104(scanner),117(fuse),1082(s1081) [17:15] grep fuse /etc/passwd [17:15] grep fuse /etc/group, sorry [17:16] s1081@BSCL02-SERVER:~$ grep fuse /etc/group [17:16] fuse:x:117:s1001,s1002,s1003,s1009,s1014,s1016,s1004,s1006,s1008,s1012,s1013,s1015,s1017,s1005,s1011,s1018,s1019,s1020,s1021,s1022,s1010,s1024,s1007,s1023,s1025,s1026,s1027,s1035,s1029,s1037,s1039,s1030,s1031,s1032,s1034,s1038,s1036,s1040,s1028,s1041,s1042,s1043,s1044,s1045,s1046,s1047,s1048,s1049,s1050,s1033,s1051,s1052,s1053,s1054,s1055,s1056,s1057,s1058,s1060,s1059,s1061,s1062,s1063,s1064,s1065,s1066,s1067,s1072,s1068,s1070,s1074,s1078,s1075,s1071,s1073,s1 [17:16] 076,s1077,s1079,s1080,s1069,s1081,s1082 [17:16] musashi1, sorry, just back now, catching up on sb [17:17] You running ldap or something? [17:17] No [17:17] Perhaps the problems lies in how I transferred the user accounts over to Gutsy from Feisty ... [17:18] ls -la /bin/fusermount [17:18] I backed up the default files when I did the fresh install of Gutsy ... and then I copied over the files I had from Feisty (i.e. /etc/passwd, etc) [17:18] s1081@BSCL02-SERVER:~$ ls -la /bin/fusermount [17:18] -rwsr-xr-- 1 root messagebus 19668 2007-09-19 03:01 /bin/fusermount [17:18] yup [17:19] what you did was bad [17:19] Don't copy the whole file [17:19] extract out YOUR users and groups, and leave the systems stuff (uid/gids < 500) as is [17:20] as they get added, changed and removed. [17:20] Your fuse group is now different [17:20] and that's your problem [17:20] You, of course, saved the ones that come with gutsy, right? :) [17:20] OK, like I said, I've got the original files that were present when I first installed Gutsy ... I'll use the data in there and do what you said [17:21] yeah, what twigged me into it is, on my gutsy, fuse is 118 [17:21] So to be precise: We're talking about /etc/passwd; /etc/shadow; /etc/groups ... [17:21] right. [17:21] Any other files? [17:21] I should look out for? [17:21] well, those are the only ones to bring over. [17:21] How much did you copy across? [17:21] just those 3? [17:22] Yes, just those [17:22] Just out of interest, what was the correct way of doing the transfer [17:22] ? [17:22] Well, here's what I do: [17:22] I make sure all my groups and users start at 1000 [17:23] so what I do is: [17:23] make a copy of the existing [17:23] sort them, so it's all in numeric order [17:24] pull across all the stuff that's 1000 or greater from passwd, group [17:24] shadow, I just manually have to make sure there's nothing system-y mixed in with the regular users. [17:25] how many users do you have? [17:26] Just over 80 [17:26] easy, then [17:26] I manage 250 :) [17:26] Now, the group file looks a little tricky ... [17:26] yeah, put back the origs, then just add your users on to the end. [17:27] (Done the passwd file) [17:27] as new features get added, new system uids/gids get added/removed, so copying the whole thing's not guarenteed to work. [17:27] In the Feisty group file, a lot of my users are members of groups with ID < 1000 [17:27] I'm going to have to manually edit each of these lines afterwards, right? [17:28] Obviously, I can easily copy and paste their primary group details (> 1000) [17:29] Sure, but in the ling run, youmight want to get them all greater than 1000 [17:29] By the way, fuse ID in my /etc/group file is 106 - is that OK? [17:29] then you could do cool things like: [17:29] awk '$3 > 999 {print $0}' /etc/passwd [17:30] which would show you all "your" entries [17:30] sorry: [17:30] awk -F: '$3 > 999 {print $0}' /etc/passwd [17:30] as for the fuse group, if that's the one that was there from the fresh install, it's fine. [17:31] when you look at /bin/fusermount is should be root:fuse [17:31] But I'll have to add all the users to the group, on that line, right? [17:32] right. [17:32] And for all the other groups they used to belong to? [17:32] yes [17:32] So waht [17:32] So what's the quickest, most efficient way of doing that? [17:33] Me? I'd write a script. [17:34] so something like: [17:34] (off the top of my head) [17:34] for ((I=1000; I<1099; I++)); do [17:35] adduser s$I fuse [17:35] adduser s$I someothergroup [17:35] etc [17:35] done [17:36] OK, that's fairly straightforward but [17:36] or, do it from the results in awk: [17:36] s1081, bryang wrote a nice script for adding users. maybe could be tweaked for what you need. [17:36] There's gotta be an easier way for the average teacher who wants to upgrade his server to Gutsy ... [17:37] s1081: yeah, or one trying to install one :) [17:37] Sure, the gui manager [17:37] What, create all of the user accounts all over again, one by one? [17:37] System->Administration->Users and groups [17:37] Beleive it or not, that's what a lot of people do. [17:37] The only other idea I had was to write a script to use the useradd, groupadd commands to set it all up [17:38] That's another good way. [17:38] As in, forget about what I had from Feisty and just start fresh in Gutsy [17:38] A lot of teachers also use LDAP, and/or active drecktory, so they just re-attach to that. [17:38] or better yet have auth via a directory of some sort [17:39] that will come at one point [17:39] OK, so what's with the Users and Groups that it doesn't sort the users alphabetically? [17:39] ubuntu server is working on it [17:39] once they are done we'll inherit it [17:40] (likely to happen in hardy) [17:41] Right, I'm done editing the files - I'll just reboot and see how it all goes [17:41] Or do I not need to reboot? [17:42] Shouldn't need to. [17:42] what's the ownership of /bin/fusermount look like now? [17:42] Alright, client is rebooting at least ... [17:44] bryang: would it be worth trying the network install you mentioned? [17:45] musashi1: not really, just references the same bits [17:45] okay [17:45] what is current state of server [17:45] just looking for options [17:45] waiting for me to give it something to do :) [17:45] installed failed, checked cd, now just waiting [17:46] Ahh, it hasn't worked - yet, at least [17:46] I'm going to try to reboot the server as well [17:46] musashi1: so maybe do the install again, then at failure point, we can do some t/s on alt consoles [17:47] But the group details look fine, though [17:47] bryang: okay, will fire it up again. [17:47] * bryang wishes you had the iLO port going to make this easier ;) [17:50] that would be cool [17:50] but behind the firewall [17:50] well, installation's away... [17:51] musashi1: if thats a normal install thats failing it would probably make sense to keep /var/log/syslog from the installer environment and attach it to a bug ;) [17:51] i moved to a different nic. someone said it might be a networking issue so worth a try [17:51] what exactly does happen ? [17:51] ogra_cmpc: i'll try that [17:52] ogra_cmpc: it fails to install ltsp chroot [17:52] i don't recall the exact warning but it's a nice red screen saying to the effect "installing failed at step build ltsp chroot you can try again" trying again also fails --> returns to error screen. [17:52] ltsp-build-client error [17:52] thats the released iso ? [17:52] right [17:52] to both [17:53] note there were bugs up to RC [17:53] downloaded just the other day [17:53] you can watch the client build process on console 4 while the progressbas sits at the 50% MARK [17:54] just hit alt-f4 [17:54] that should revel at least the error [17:54] note that moaning about pty not mounted and dbconf warnings are normal there [17:54] checked that last time --> ltsp-client-builder failed with error code 1 [17:54] *debconf [17:55] well, the stuff that causes that error would be miore intresting :) [17:55] it must be above in the log [17:56] i'll try and find that when/if it fails again [17:56] Hi folks. got some speed issues I'm seeing in Edgy thin clients. I think it relates to DRI, and I'm wondering if anyone knows how to activate this feature on thin clients with Edubuntu? [17:56] ogra: Can't use scp-remote; on Edgy this command wasn't implemented yet! [17:57] cberlo: you need to install the linux-restricted-modules package in teh chroot and follow the usual procedure to enable binary drivers [17:57] cberlo: oh, right [17:57] edgy is ancient :) [17:57] The usual procedure? As in list it in the lts.conf? [17:57] NO AS DESCRIBED ON TEH WIKI [17:57] OOPS [17:57] ogra_cmpc: Hey, it's still supported! :) But I'd love to move to Gutsy. Very tempting, but I need everything stable and tested.... [17:57] * ogra_cmpc curses the tiny keyboard of teh classmate [17:58] ogra_cmpc: Where on the wiki? Didn't come across that... [17:58] search for binary drivers [17:58] ogra_cmpc: Thanks! Will do! [17:58] note that you will only be able to support either nvidia or ait ... both at the same time doesnt work [17:59] *ati [17:59] they both replace the GL libs with their own versions [17:59] Ummm... This is an Intel 810 chipset... [17:59] that should just work out of teh box [18:00] ogra_cmpc: i can't make heads or tails of all that log info. is there a way to output it to a file that i can paste somewhere? [18:00] So I should be getting DRI already? I specified i810 in the lts.conf as the default driver. [18:00] musashi1: its savede to /var/log/syslog in teh installer [18:00] on console2 you can start a shell [18:01] but from a console how do i save it to say a flash drive? [18:01] cberlo: yes, but it could be that we didnt install teh mesa dri libs in teh client chroot back then [18:01] you should have teh kernel related stuff running [18:01] ogra_cmpc: Okay. So which package is that in and/or where can I check to see if that's in there? [18:01] (i.e. DRI) [18:02] something with mesa and dri in teh package name [18:02] i have no briowser around [18:02] so i cant look up stuff for you [18:02] orgra: Got this one in there: libgl1-mesa-dri [18:02] packages.ubuntu.com might help [18:02] sounds about right [18:03] install that in teh chroot [18:03] It's already there... :( [18:04] look for mesa glx as well [18:04] ogra_cmpc: Yep, that one's in there, too. [18:05] hmm, no idea then [18:05] Nothing else I'd have to do to enable DRI on the thin client? It should "just work"? [18:06] for i810 ? yes [18:06] i didnt have any i180 cards during edgy development so i cant say much about ltsp and GL support there [18:06] i know compiz works out of teh box here on gutsy on teh i810 client i have now [18:07] Alright. Guess I'll just have to play with it a bit and see if I can get it to work properly. Wait -- you're using compiz on a thin client?? [18:10] yeah, its incredibly fast [18:11] Well, guess I'll see if I can load up a test server here. That sounds like it would fix that issue for me. Running a Windows program on WINE and video update speed is glacial. Runs great on my laptop here, though, so it's not a problem with WINE/Linux/good video. [18:11] ogra_cmpc: Vanilla edubuntu install will work "out of the box"? [18:12] gutsy, that is. [18:12] yes [18:12] yep [18:24] sbalneav: ogra_cmpc: It's finally working - thanks for all your help - greatly appreciated ... I'm giving up for the day; You guys deserve gold medals - keep up the good work. [18:24] :) [18:25] Don't think you've seen the last of me ... now that I know where you guys are ... [18:28] ogra_cmpc, what's the wilress card again? [18:29] wireless [18:29] ?? [18:29] ogra_cmpc, the one the classmate brings [18:29] ralink [18:29] you said it was not intel [18:29] rt73usb based [18:30] ogra_cmpc, thanks [18:39] bryang: any suggestions on how to get the log to you (or anyone else)? it failed again [18:39] bryang: could it be an acpi issue?? [18:41] musashi1: do you have an USB key you could store it on? [18:42] yes [18:42] so use that one :) [18:42] but how do you mount a usb in a console [18:42] with the mount command [18:43] plug it in ... wait a second .... type: dmesg [18:43] will fdisk -l tell me the dev name? [18:43] at the end of teh output you should see teh device name [18:43] hold on, it's in another room [18:48] 8.04 is going to be pretty nice, I'm guessing. LTS, feature-rich, well-tested.... Looks like things are coming along nicely for Edubuntu. It may just have a future in my school board... [18:49] great now my stupid win box won't read the flash drive. [18:49] musashi1, ext3 fs or something like that ? [18:49] well it was a fat32 drive [18:50] ok.. [18:50] i think i fried it somehow. my ubuntu lappy won't read it either [18:51] care to do a tune2fs -l ? [18:51] dont forget to unmount ;) [18:52] if you unplugged it without unmounting, data can be corrupt [18:52] yeah. [18:52] i did that when I was using pcbsd. [18:53] it refused to mount, had to use debugfs to kick out 'recover_needed [18:53] or something like that from the features of the drive. [18:54] it wont unmount [18:54] invalid argument [18:54] the command is umount [18:54] right [18:55] i did umount /dev/sda [18:55] wrong? [18:55] umount [18:55] ah, right [18:56] * musashi1 wishes he was more cli literate :( [18:58] uh, any idea where it's mounting? /mnt is empty [18:58] where you told it to :) [18:59] (in the mount command) [18:59] did you mount in the first place ? [19:00] no. thought it auto mounted [19:00] ubuntu's udev i think mounts it in /media/## [19:00] there is no /media [19:00] it a busybox shell [19:00] if that matters [19:04] try doing blkid [19:04] i mean typing blkid [19:04] okay, created dir /mnt/usb and mounted. cp file to it. verified it's there. still can't umount [19:04] used umount /mnt/usb [19:05] says invalid argument [19:06] oops, was still in that dir. d'oh [19:10] for your reading pleasure :) http://dpaste.com/23351/ [19:10] that's the whole log [19:10] free virtual beer to who ever can pinpoint the problem :) [19:13] Is there anyone here that can help an edubuntu newbie with thin client questions? [19:13] ogra_cmpc: around ? [19:14] i am trying to set up edubuntu 7.10 thin clients [19:15] ogra, ogra_cmpc: the ML still doesn't like me, can I mail you and you forward it to the list ? [19:21] line 6237 has the failure for build-ltsp [19:22] * musashi1 wonders what line 6235 means [19:31] could it be a bad CD issue? i'm going to burn a new one and try (burning on ubuntu this time) [19:50] starting install again with new CD. my laptop would only burn at 28x though. hope that isn't too fast. in the past it tended to cause problems. [19:51] this line from syslog is puzzling --> "tsp-client-builder: ltsp-build-client options: --mirror file:///cdrom --security-mirror none --skipimage" [19:52] then "(process:25542): SIOCSIFADDR: No such device" [19:52] and then failure --> "WARNING **: Configuring 'ltsp-client-builder' failed with error code 1" [20:20] bryang: if this fails again i'm going to cry [20:25] musashi1: hmm, that line 6235 looks like it was called incorrectly (and some of those options are not in the --help output) [20:26] at least on my running system [20:27] try grabbing this log next time [20:27] /var/log/ltsp-server-build.log [20:28] since that is where output goes according to the ltsp-server.postinst script [20:31] fwiw, ltsp-build-client is called with no options, so ignore that assessment ;) === ogra_cmpc_ is now known as ogra_cmpc [20:51] * musashi1 cries, screams, puts fist through wall [20:53] You're not actually giving us any information on what your network is like. [20:53] what would you like to know? [20:54] Maybe you could tell us a little bit about your network, internet access, what the machine is, how many nics you've got in the machine, how much ram, what kind of processor, you know. Information :) [20:54] there is no network connected yet, except for the uplink via dhcp [20:55] sys = dual zeon, 4GB RAM, 3 NIC, 3x160GB RAID5 LUN [20:55] well, there is internet and the server does get a dhcp IP, machine is a hp proliant 350 with 1 on board nic and two others 4gb of ram 2 xeon dual core cpus. some of this info was supplied way above :) [20:55] * musashi1 too slow [20:55] model = HP ml350 [20:56] So, there's 3 onboard nics [20:56] true [20:56] I didn't see it. [20:56] Have you tried disabling in bios all the nics that arent used? [20:57] on one the mobo, two in pci slots (right bryang?) [20:57] sbalneav: no [20:57] pci-express slots, but yes [20:57] They're in pci slots? [20:57] Maybe try yanking them, since the failure you're getting is a network related one. [20:58] worth a try musashi1, I haven't done any installs on pci-x nic systems [20:59] okay [20:59] and worst case can swap some for those ;) [21:02] okay, yanked and trying again... [21:03] sbalneav: you'll notice that all three NICS were found during bootup by hw-detect.hotplug [21:03] (process:25542): SIOCSIFADDR: No such device" means some interface address wasn't found. [21:03] We've tested on one nic and two nic systems [21:04] Maybe we've got a bug that causes it to fail on 3 nics [21:04] or, maybe something in the kernel doesn't like one of the cards [21:04] * bryang sees light turn on ;) [21:04] or, maybe some udev rule doesn't like 3 nics [21:04] or who knows. [21:05] fwiw, I did install feisty on a three nic system (so may in fact be a new issue) [21:05] What I *do* know is, neither the machine, or the edubuntu machine will respond do crying, screaming, or fists in plasterboard. :) So, we'll try this. [21:06] * bryang appreciates the help, for sure [21:06] And maybe this won't work either, but then that'll be another datapoint to add to the graph :) [21:08] sbalneav: machine won't respond but makes me feel better. i've been at this for 6 hours now :) [21:09] sbalneav, it does look like possibly some NIC re-ordering is happening throughout the install [21:09] Entirely possible. [21:10] musashi1, was the log posted from when you did an install from one of the PCI NICs ? [21:11] bryang: i think so [21:11] brb [21:11] ogra_cmpc: Finally back from installing a test server here. From a fresh load, I'm trying to connect a Dell GX100 over PXE/MBA (the one with the i810 video card I need to work with) and not getting any X at all. Haven't even logged into the system once since installing. Suggestions? [21:11] sbalneav: if this works i owe you a virtual beer...or maybe bryang does :) [21:12] * musashi1 crosses fingers. installastion's away [21:13] musashi1, do you get the option to go to next step of installation ? [21:19] cberlo: could be bug 149006 [21:19] Launchpad bug 149006 in ltsp "ltsp does not configure xorg.conf correctly" [Undecided,New] https://launchpad.net/bugs/149006 [21:19] create a /var/lib/tftpboot/ltsp/i386/lts.conf [21:19] and make sure to have X_COLOR_DEPTH=24 in there [21:19] if it doesnt work with 24, try 16 [21:20] RichEd: ?? [21:20] hi ogra ... [21:20] shouldnt you be in the air ? [21:20] yep ... international lounge at johannesburg airport [21:20] trying th enew louge card ? [21:20] thanks to the new lounge card [21:20] indeed [21:20] heh, snap [21:20] free beer (as in free beer) ... snacks ... comfy chairs ... AND ... drum roll .... [21:20] tdrrrrrrrrr [21:21] smoking lounge [21:21] * ogra_cmpc dances wildly [21:21] I have to make a new compressed image after? [21:21] cberlo: not if you use /var/lib/tftpboot/ltsp/i386/lts.conf [21:21] and of course ... internet access :) [21:21] indeed [21:21] wow, that makes travveling a lot easier [21:21] ogra_cmpc: Alright, I'll give it a go. [21:22] * ogra_cmpc wished he had had that card back in warsaw [21:22] me too in a number of crappy airports ... [21:22] i guess warsaw executive lounge may have been as styling as say ... a small german village bus station ;) [21:23] lol, yes [21:24] i mamnageed my first successfull install btw ... i'll write a small gui tool for that during travel ... i still like the principle of the squashfs :) .... [21:24] Hey, I see GUI! :) [21:25] so that way the image will only be 650M [21:25] bryang: next step? you mean after failure on the chroot stuff? i didn't try. figured failure == failure [21:25] and be installable from any kind of USB device [21:26] ogra_cmpc: Okay, now that I'm Gutsy and have GUI, what do I need to get DRI? [21:26] cberlo: congrats ... (i think that bug justifies a stable release upgrade it hits many ppl) [21:26] cberlo: try to enable desktop effects in teh appearance settings [21:26] Okay [21:27] Desktop Effects could not be enabled. [21:27] hmm [21:27] Which, I am gonna guess probably means my card is too wimpy to pull this off? [21:28] well, i dont know if there are i810 cards that are not dri capoable [21:28] the ones i had in my hands all were [21:28] but that were pretty recent ones [21:28] Is there a way I can do something like "lspci" on the thin client? [21:28] * RichEd waves to ogra ... heading to flight #2 ... may chat to you from schipol [21:29] * ogra_cmpc waves [21:31] Is it "X_SERVER" or "XSERVER" to set default server? [21:32] no unde5rscore [21:33] try the intel server btw, thats probably better [21:33] Okay. Thanks. I'll play with it more tomorrow and let you know how it works out! :) [21:53] sbalneav: bryang no failure this time but now with only 1 nic i get a different msg (no interface for ltsp dhcpd config found). install is continuing. [21:53] guess it didn't like the pcie nics or didn't like 3. [21:55] That's fine, so long as it completes, then we can fix up the nic and the dhcpd afterwards. [21:56] yupper, agreed [21:56] success!! i now have a thin client server with 1 nic :) rebooting. [22:00] the desktop has landed :) [22:01] schweet [22:01] can i put one of the nics back to see if it likes pcie? [22:02] sure [22:02] will it try to configure it? [22:02] we know how to get back here ... now ;) [22:02] on a reboot that is [22:02] should see it, and assign it as eth1, likely [22:03] okay, i'll stick one back in and see what happens [22:03] we will have to manually configure it to server clients [22:03] s/server/serve/ [22:04] and for completeness we could try another install w/just two (to flesh out a bug report) ;) [22:06] not another install... [22:06] heh, (at least) one more for the good of the community [22:06] i think i did 5 today [22:07] maybe tomorrow but not today [22:07] * bryang nods [22:11] seems okay with the second nic. it boots and ifconfig shows eth0 and eth1 [22:15] i have to head out soon. thanks sbalneav, bryang. as promised :) http://laughingsquid.com/wp-content/uploads/anchor_beer.jpg [22:17] priv msg has details to conf that interface [22:19] hello- is there anyone here that has used dell gx110's as edubuntu thin clients? [22:23] /q [22:26] cya. thanks again === JordanC is now known as JordanC[BedSecks === JordanC[BedSecks is now known as JordanC[Secks]