[04:13] <roasted_> Hey fellas. Is there a way to customize the login screen of Edubuntu clients?
[04:13] <roasted_> on LTSP
[05:21] <doctormo> roasted_: Sure, what would you like to do?
[12:37] <highvoltage> good morning
[12:42] <mhall119> good morning
[13:46] <mgariepy> good morning everyone
[15:30] <Ahmuck-Sr> doctormo: wouldn't roasted just be able to subnet the dhcp3 server on the ltsp box and be golden?
[15:37] <Ahmuck-Sr> http://www.opennms.org/ - i'm curious, could this be used for thin/fat client monitoring?
[16:02] <doctormo> Ahmuck-Sr: Yes, but dhcp is a funny old thing.
[16:04]  * Ahmuck-Sr really should get his CIS degree
[17:09] <Roasted> whats up fellas
[17:40] <Ahmuck-Sr> hi roasted
[17:40] <mgariepy> Hello Roasted
[18:01] <Roasted> hey guys
[18:01] <Roasted> trying to do that dhcp swap now
[18:01] <highvoltage> so is anyone feeling like fixing some edubuntu bugs today?
[18:01]  * highvoltage got one patch for nanny so far at least
[18:02] <Roasted> so... little lost here.
[18:02] <Roasted> if I'm adding LTSP and using a Windows DHCP environment, do I need the MAC of EACH machine that will be using LTSP, or just the MAC of the LTSP server?
[18:03] <alkisg> Ah today is the bug day?
[18:03] <alkisg> highvoltage: any specific requests?
[18:03] <alkisg> Or we can just pick one we prefer?
[18:03] <alkisg> Roasted: do you mind if you send the boot filename to all of your clients, ltsp or not?
[18:03] <alkisg> If not, then you don't need any mac
[18:04] <Roasted> is this just to limit which systems can pxe boot to LTSP?
[18:04] <alkisg> Yup
[18:04] <Roasted> like if I DONT do this, and I PXE boot all 500 systems in the building then they'll all probe the LTSP box?
[18:04] <alkisg> So if you don't have a specific reason to limit them, just leave it for everyone
[18:04] <alkisg> Yup
[18:04] <Roasted> well, I don't want to limit it now, because if we set it up it may be nice to walk into any lab and fire one up for demonstration purposes to my boss.
[18:05] <highvoltage> alkisg: good question
[18:05] <alkisg> Right, so don't specify any macs now
[18:05] <Roasted> I was surprised. In my bench test yesterday I ran 10 systems off of my laptop.
[18:05] <Roasted> core 2 duo, 4gb ram
[18:05] <highvoltage> alkisg: best would be if you could scratch your own itches
[18:05] <Roasted> granted I maxed out my ram at nearly 3.8gb, but each system had gimp, open office, and firefox running with web browsing.
[18:05] <Roasted> the proc was relatively calm too, with only occasional spikes.
[18:05] <highvoltage> alkisg: otherwise you could browse our buglist and find something that looks interesting...
[18:06] <highvoltage> https://bugs.edge.launchpad.net/~edubuntu-bugs/+packagebugs
[18:06] <alkisg> Ty, I'll have a look
[18:06] <Roasted> If I do this with the LTSP Box on the main network, we'll be on a 10.52 IP scheme instead of 192.168. As a result, I would need to change my static IP of the LTSP box. No problem, I can do that. My concern is I tried this yesterday and I wasn't able to PXE boot when I changed my static IP. Do I have to change a PXE entry anywhere to correspond with my new static IP?
[18:06] <highvoltage> cool :)
[18:07] <highvoltage> Roasted: you'll have to edit dhcpd.conf in /etc/ltsp (if you installed ltsp-server-standalone) or /etc/dhcp (if you didn't)
[18:07] <alkisg> Roasted: your dhcp configuration in your windows server
[18:08] <Roasted> highvoltage, I won't be runnign DHCP on the LTSP box, I'll be removing it here shortly. As a result, I would be editing /etc/dhcp, right?
[18:08] <alkisg> And probably restart the windows dhcp service
[18:08] <highvoltage> you might also have to edit a few other files based on your configuration (wherever you had IPs listed) and at least /etc/hosts
[18:08] <Roasted> highvoltage, what would I need to edit in hosts? just the IP?
[18:08] <highvoltage> Roasted: ah, then you don't need to be editing the dhcp file on the server
[18:08] <Roasted> what
[18:08] <Roasted> really
[18:08] <Roasted> this ubuntu doc says I need to
[18:08] <Roasted> https://help.ubuntu.com/community/UbuntuLTSP/LTSPWindowsDHCP
[18:08] <Roasted> by adding those 3 entries to the DHCP service
[18:09] <highvoltage> that doc says to remove the dhcp server
[18:09] <Roasted> on LTSP
[18:09] <Roasted> then a few lines lower it says login to your windows server and load the DHCP config screen
[18:10] <Roasted> then add those 3 entries
[18:10] <highvoltage> yes, that's on the windows dhcp server
[18:10] <Roasted> right
[18:10] <Roasted> oh wait
[18:10] <Roasted> wait
[18:10] <Roasted> wait
 Roasted: ah, then you don't need to be editing the dhcp file on the server - you menat the LTSP server....
[18:10] <highvoltage> if you use a windows dhcp server then you don't have to configure the dhcp server on your ubuntu machine
[18:10] <Roasted> I thought you meant the windows server...
[18:10] <Roasted> my apologies
[18:10] <alkisg> Hmm that page isn't very good. Uninstalling dhcp3-server will make ltsp-server get uninstalled when apt-get --auto-remove is next used.
[18:11] <Roasted> someone here linked me to it yesterday
[18:11] <Roasted> *shrug*
[18:11] <alkisg> That was me
[18:11] <Roasted> :P
[18:11] <Roasted> I thought so
[18:11] <alkisg> But the page still isn't good :)
[18:11] <Roasted> lol
[18:11] <Roasted> that's reassuring
[18:11] <Roasted> shall I follow thorugh with it?
[18:11] <alkisg> See the other page I linked you to, with the proxy dhcp, and *only* follow the steps to uninstall dhcp from there
[18:12] <Roasted> that one looks like its more of a headache
[18:12] <alkisg> See the *only* part above
[18:12] <alkisg> It's just 3 lines
[18:12] <Roasted> the "only" part?
[18:13] <Roasted> install dnsmasq, config dnsmasq, create a dnsmasq config file, adjust pxelinux.cfg/default....
[18:13] <alkisg> *only* follow the steps to uninstall dhcp from there
[18:13] <Roasted> I think I like the other link more :P
[18:13] <Roasted> oh
[18:13] <alkisg> Not the dnsmasq, not pxelinux, not not not
[18:13] <Roasted> so I use both guides?
[18:13] <Roasted> just different parts of eahc?
[18:13] <alkisg> Erm ok
[18:13] <alkisg> I thought I'd save me some time
[18:13] <alkisg> This takes longer
[18:13] <alkisg> Here let me get you the 3 lines
[18:14] <alkisg> sudo apt-get install ltsp-server  # This may update ltsp-server instead
[18:14] <alkisg> sudo apt-get install ltsp-server  # So do it twice to be certain
[18:14] <alkisg> sudo apt-get --yes --auto-remove purge ltsp-server-standalone
[18:14] <alkisg> Those 3 lines remove the dhcp3-server part of the ltsp installation
[18:14] <Roasted> okay
[18:15] <Roasted> but I'd still be adding those 3 entries to the windows DHCP server, right
[18:15] <alkisg> Right
[18:15] <Roasted> gotcha
[18:16] <Roasted> so these 3 lines, the 3 entries to windows dhcp, and aside from changing my LTSP server IP to something within the proper scope, we're done then
[18:16] <alkisg> When you change your IP you also need to change your /etc/hosts, unless you change it from network manager
[18:16] <Roasted> naw I'm using interface file
[18:16] <Roasted> I didnt change it in /etc/hosts yesterday. I wonder if thats why I wasnt able to PXE boot.
[18:17] <alkisg> Hmm no scratch that
[18:17] <alkisg> The default installation doesn't contain the server IP in /etc/hosts
[18:17] <Roasted> yeah I just did nano on it and didnt see...
[18:17] <Roasted> wonder why I was failing to pxe boot then
[18:17] <alkisg> With which dhcp serveR?
[18:17] <alkisg> The ubuntu one?
[18:17] <Roasted> yes
[18:17] <Roasted> I changed my IP on it
[18:17] <Roasted> and I wasnt able to PXE boot from there
[18:17] <alkisg> You needed to change /etc/ltsp/dhcpd.conf then
[18:17] <Roasted> oh
[18:17] <alkisg> And restart dhcp
[18:18] <Roasted> what am I changing, just the subnet range?
[18:18] <Roasted> subnet 192.168.0.0 netmask 255.255.255.0 {
[18:18] <Roasted>     range 192.168.0.20 192.168.0.250;
[18:19] <Roasted> I'd just change the range to 10.52.0.1 (start of windows dhcp scope) to 10.52.1.254 (end of windows dhcp scope) right?
[18:20] <alkisg> You won't be needing this, you'll be using the windows server
[18:20] <Roasted> I understand. I'm just trying to understand what I did wrong yesterday.
[18:20] <alkisg> Then yes, you would just change the subnet
[18:20] <Roasted> good deal
[18:21] <Roasted> I'm going to test it now :P
[18:21] <Roasted> just for sake of learning
[18:21] <alkisg> But, beware, your windows clients will get an IP from that
[18:21] <alkisg> So they won't have internet access etc etc
[18:21] <Roasted> oh no, I'm on a secluded LAN with this setup
[18:21] <alkisg> OK
[18:22] <Roasted> here we go...
[18:22] <Roasted> hahaha. bingo.
[18:22] <Roasted> you're the man alkisg
[18:22] <Roasted> if you ever come to PA, drinks are on me
[18:23] <Roasted> alright, time to get this windows thing rolling and see how we do
[18:24] <alkisg> Good luck :)
[18:24] <Roasted> dumb question tho. even if I have 64 bit edubuntu installed, Im booting 32b images right
[18:25] <alkisg> It depends on if you put `--arch i386` as a parameter to ltsp-build-client
[18:25] <Roasted> what's LTSP's default behavior?
[18:26] <alkisg> ls -l /opt/ltsp/images
[18:26] <alkisg> If you see i386, you got i386
[18:26] <alkisg> If you see amd64... you know
[18:26] <Roasted> gotcha. we're on 386. good deal.
[18:26] <alkisg> The default behavior is chroot arch == server arch
[18:26] <Roasted> hows that make sense...
[18:26] <Roasted> Im on 64 bit...
[18:26] <Roasted> on the server
[18:27] <alkisg> Are you sure?
[18:27] <Roasted> x86_64 is listed under uname -a
[18:27] <Roasted> is that 64?
[18:27] <alkisg> Yes
[18:27] <Roasted> I mean it addresses 3.9gb of ram
[18:27] <Roasted> so
[18:28] <Roasted> I wonder how I got 386 for the clients yet 64 on the server
[18:28] <alkisg> 32bit also addresses 4gb ram
[18:28] <alkisg> With -pae extensions, on by default
[18:28] <Roasted> oh
[18:28] <Roasted> but if uname -a says Im on 64 bit...
[18:28] <alkisg> So maybe you did put --arch i386 in your ltsp-build-client after all
[18:29] <Roasted> I didn't even know that existed until you told me just now.
[18:29] <Roasted> So I'm doubtful that I did.
[18:29] <alkisg> How did you install LTSP?
[18:29] <Roasted> I just wanted to make sure we were using 32b images since our hardware is older hardware.
[18:29] <Roasted> Edubuntu 10.10 64 bit DVD
[18:29] <Roasted> hit the checkbox for LTSP
[18:29] <Roasted> ran through the installer
[18:29] <Roasted> I have a 2nd box here with Edubuntu that I installed from the same DVD. I wonder what that says
[18:29] <alkisg> Hmm maybe it has a 32bit chroot, I haven't done that as we're using localized chroots here
[18:30] <alkisg> highvoltage would know :)
[18:30] <Roasted> to be honest it makes sense to me to use 64b server, 32b clients
[18:30] <Roasted> since people would be utilizing older hardware for thin clients in some cases
[18:30]  * highvoltage emerges
[18:31] <Roasted> he awakens!
[18:31] <alkisg> highvoltage: on edubuntu 64 bit, the chroot installed is 32 bit?
[18:32] <highvoltage> ah, yes. on edubuntu we always do 32bit ltsp chroots from the installer (64bit won't work on many thin clients, such as anything Atom based, and there's very rarely benefit with 64bit on clients)
[18:32] <highvoltage> Roasted: ^^^
[18:32] <Roasted> nice
[18:32] <Roasted> thanks :)
[18:33] <highvoltage> if you use ltsp-build-client after installation, then it will use your current architecture as default, but for the edubuntu installer it made sense to always go for 32bit
[18:33] <Roasted> off topic question
[18:33] <Roasted> is there a way to edit the login screen
[18:33] <highvoltage> yes
[18:33] <highvoltage> the LDM themes are in /usr/share/ldm/themes in the thin client chroot
[18:34] <highvoltage> you can add a new one there and specify it in lts.conf
[18:34] <Roasted> okay. I thought so. I replaced bg.png and put in a different image, also named bg.png, but it didnt take, so it confused me a little bit
[18:35] <alkisg> Did you run ltsp-update-image?
[18:35] <Roasted> probably not
[18:35] <Roasted> as root?
[18:36] <alkisg> With sudo, yes
[18:36] <Roasted> Error: chroot /opt/ltsp/amd64 doesn't exist.
[18:36] <Roasted> hmm
[18:37] <highvoltage> Roasted: yeah, the way you did it will be a bit risky because your changes will be over-written again if you install updates
[18:37] <Roasted> well, I did it on my laptop, which is just a test-drive machine
[18:37] <Roasted> I got my other box fired up here for real testing
[18:37] <highvoltage> Roasted: you might want to add a "-a i386" to let it know that it should update the i386 chroto and not a 64bit one
[18:38] <alkisg> Roasted: since you have a different chroot arch than the server arch, you always need to add --arch i386
[18:38] <Roasted> I see
[18:38] <Roasted> looks like its owrking
[18:38] <Roasted> creating 4.0 file system
[18:41] <Roasted> highvoltage, is there an official guide somewhere to changing the theme properly?
[18:41] <highvoltage> Roasted: nope
[18:41] <highvoltage> Roasted: but I'll answer any questions about it if you write us one :)
[18:42] <Roasted> well if you tell me how to do it, I'll make a guide for it. :P
[18:43] <alkisg> Don't forget to put your findings to the windows dhcp page as well :P :D
[18:43] <highvoltage> Roasted: I just have to look into a few other things too now but we can go through it a bit later
[18:43] <Roasted> sounds good
[18:50] <Roasted> seems as if I have tanked something badly
[18:50] <Roasted> my login screen is all gray, no images whatsoever, and wont log any users in
[18:51] <Roasted> thankfully its my laptop install which... doenst matter
[18:51] <Roasted> still curious on what happened tho. it worked until I ran that command. lol...
[18:51] <highvoltage> that command builds the new squashfs image based on the changes you have made
[18:52] <Roasted> the only change I made was the background image
[18:52] <Roasted> maybe it doesnt like it
[18:52] <Roasted> but theres also a button here, all white with a red X in the center, as if that didnt fly either
[18:52] <Roasted> ah well, I wont be bothered by that for now.
[18:56] <Roasted> is there by chance a way to revert it back to normal without reinstalling edubuntu?
[18:57] <alkisg> Put the old background image?
[18:57] <alkisg> And re-run ltsp-update-image/
[19:04] <Roasted> didnt work
[19:05] <alkisg> Then you must have changed something else too
[19:05] <alkisg> If you don't remember what, you can rebuild the chroot
[19:05] <alkisg> I.e. sudo rm -rf /opt/ltsp && sudo ltsp-build-client --arch i386
[19:05] <alkisg> (will take some time)
[19:12] <Roasted> is there a forum for LTSP so I can ask questions there instead of bugging you guys?
[19:13] <mgariepy> #ltsp
[19:13] <mgariepy> but most ppl here are in there too :)
[19:14] <Roasted> thanks :)
[20:01] <highvoltage> well, what would be faster is:
[20:01] <highvoltage> sudo chroot /opt/ltsp/i386 apt-get --reinstall install ldm-themes
[20:01] <highvoltage> and then ltsp-update-image
[20:02] <Roasted> already done :P
[20:02] <Roasted> Im working on another issue at the moment
[20:02] <Roasted> I just asked it in LTSP if you're curious at taking a gander. it has me stumped.
[20:04] <doctormo> highvoltage: Have you had any thoughts about draft4? If you have no more concerns, then we can announce and release?
[20:09] <highvoltage> doctormo: nothing that jumps out at me yet, it's already in today's daily build :)
[20:09] <doctormo> Fantastic, although I haven't produced all the sizes and aspects that might be required.
[20:39] <doctormo> highvoltage: I had to do some editing to get it to fit widescreen, please review
[20:42] <highvoltage> doctormo: except for some changes in the hills I couldn't see any other changes, but it looks good
[20:43] <doctormo> highvoltage: It's 1MB, just so a quick refresh
[20:43] <doctormo> You should see the version with the pink guides
[20:43] <doctormo> That show what each screen resolution would see
[20:43] <highvoltage> ok, I see the pink lines
[20:44] <highvoltage> I think it looks good
[20:46] <doctormo> highvoltage: How do you ship it? just ship the widescreen version and set it to crop?
[20:47] <Roasted> why would my users time out when trying to log in? all I did was add windows dhcp to the mix.
[20:48] <doctormo> Roasted: If the windows dhcp isn't giving correct info and the machines are not online... that would be an issue.
[20:48] <doctormo> I forget if ltsp does seconard network connections
[20:48] <Roasted> doctormo, I would *assume* that by them coming to the login screen that it would have the proper info.
[20:48] <Roasted> let me do a direct cat5 line from my server to a laptop and see if it does the same thing
[20:48] <Roasted> one second
[20:49] <Roasted> crap. I cant. I dont have dhcp on it.
[21:22] <highvoltage> doctormo: currently, it's just stretched over whatever screen you have
[21:22] <highvoltage> Roasted: heh, if you took a second to think about that you'd realise that before plugging it in. take it easy :)
[21:24] <highvoltage> Roasted: I haven't configured a windows DHCP server yet, but what is the information you put in there? (I thought it was in scrollback but I couldn't find it)
[21:29] <Roasted> highvoltage, https://help.ubuntu.com/community/UbuntuLTSP/LTSPWindowsDHCP
[21:30] <Roasted> theres 3 lines of info that was put in
[21:30] <Roasted> I did not put it in, the network admin here did. He showed me how it works though, as we already have several other "rules" in place since we have VOIP here, and our VOIP phones require similar entries to be made.
[21:30] <Roasted> highvoltage, it took him a matter of 20 seconds to do it.
[21:38] <highvoltage> Roasted: what did he use for the IP address?
[21:38] <Roasted> of the LTSP box?
[21:38] <Roasted> highvoltage, ^
[21:39] <Roasted> highvoltage, I'm still doing small scale testing. I just grabbed a DHCP IP and had him use that for the entry.
[21:39] <highvoltage> Roasted: no, on the Windows DHCP server
[21:39] <Roasted> we're working now
[21:39] <highvoltage> ok
[21:39] <Roasted> so technically my LTSP box is on DHCP.
[21:40] <Roasted> but the box Im running it on isnt one Ill actually use in the classrooms.
[21:40] <Roasted> when I do Ill certainly static it
[21:40] <Roasted> highvoltage, my problem was when I changed the IP I had no idea I had to run the sshkeys command to update them or whatever.
[21:40] <Roasted> that fixed my login hanging problem though.
[21:40] <Roasted> highvoltage, aside from changing the IP and needing to run that command, is there any other instances where running the sshkeys command and image update command would be useful?
[22:38] <doctormo> highvoltage: How much space do you have for the desktop wallpaper and is it packaged?
[22:39] <stgraber> doctormo: 1.8GB give or take
[22:40] <stgraber> that's how much we have left on the dvd
[22:40] <doctormo> I could make an entire gallery of moving desktop backgrounds with that ;-)
[22:42] <highvoltage> doctormo: I thought that your moving backgrounds are svg and take up very little space :)
[22:42] <highvoltage> doctormo: it's in the edubuntu-artwork package
[22:42] <doctormo> highvoltage: Ah those aren't moving, they're just evolving.
[22:43] <doctormo> So the image @ 2560x1600 is ~1MB, that takes care of the biggest resolutions.
[22:43] <doctormo> And it's at widescreen and I've checked that full screen should take.
[22:43] <doctormo> We'll need to set it to not stretch
[22:46] <doctormo> highvoltage: Testing says it should be set to "Zoom" in the xml configuration.
[23:25] <highvoltage> doctormo: ok, I'll update it