IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 13 November 2009   (all times are UTC)

00:18japerry has joined #ltsp
00:19alkisg_work has joined #ltsp
00:24Egyptian[Home] has quit IRC
00:26Egyptian[Home] has joined #ltsp
00:58alkisg_work has quit IRC
01:16Appiah has quit IRC
01:22alkisg_work has joined #ltsp
02:00alkisg_work has quit IRC
02:06Appiah has joined #ltsp
02:14Selveste1 has joined #ltsp
02:19alkisg has joined #ltsp
03:07Egyptian[Home]1 has joined #ltsp
03:12Selveste1_ has joined #ltsp
03:20Egyptian[Home] has quit IRC
03:26Selveste1 has quit IRC
04:01lucascoala has quit IRC
04:18alkisg has quit IRC
04:25Selveste1_ has quit IRC
04:37Selveste1_ has joined #ltsp
04:39alkisg has joined #ltsp
04:50wimiko has joined #ltsp
05:01pimpministerp has joined #ltsp
05:01pimpministerp has quit IRC
05:02alkisg has quit IRC
05:11wimiko has quit IRC
05:27Selveste1_ has quit IRC
05:30tryltsp has joined #ltsp
05:30
<tryltsp>
Hello Guys
05:32
Wath ne next step after tftp nbi tranferr? I have ltsp5 works fine wit pxe but wen i try flopy boot, a get only tftp nbi transfer done.
05:33
some one could helpme?
05:34
ltsp5+ubuntu 9.1+ltsp4.2
05:34
9.10
05:45vvinet has quit IRC
05:47
<tryltsp>
some one?
06:05alkisg has joined #ltsp
06:05
<tryltsp>
noone?
06:06
somebody here, try ltsp5+ubuntu 9.10?
06:06
<alkisg>
Yeah, works ok...
06:07
<tryltsp>
alkisg: I get it works fine too with pxe, but wen i try boot wint floopy, the boot proccess, stop in tftp download nbi.
06:07
alkisg: do you have any ideia?
06:08
<alkisg>
Well, download a newer floppy with gpxe
06:08
!gpxe
06:08
<ltspbot>
alkisg: "gpxe" is the successor to etherboot. You can find it at: http://etherboot.org/wiki/index.php
06:08
<alkisg>
http://rom-o-matic.net/gpxe/gpxe-0.9.9/contrib/rom-o-matic/
06:09
<tryltsp>
alkisg: thanks
06:09
<alkisg>
You're welcome
06:09
<tryltsp>
lest go try :D
06:09
<alkisg>
I've heard of others with your problem
06:09
..and it was solved by a newer disk. But maybe someone should actually file a bug in ubuntu-ltsp..
06:10
<tryltsp>
its good to hear :D
06:15pmatulis has joined #ltsp
06:26tryltsp has quit IRC
06:27tryltsp has joined #ltsp
06:28
<tryltsp>
alkisg: Thaks again, my problem was fixed :D
06:28
<alkisg>
tryltsp: you're welcome, but if you want, do file a bug to get the .nbi thing solved
06:29
https://bugs.launchpad.net/ubuntu/+source/ltsp
06:29
<tryltsp>
alkisg: ok
06:31smuggman has joined #ltsp
06:33smuggman has quit IRC
06:34smuggboy has joined #ltsp
06:38
<smuggboy>
hello @all. i have a little problem with ltsp. i have set up a ltsp server and its working fine. i have configured autologin for some clients but dont know how to logout or shutdown the client properly. when i logout the gnome session it automatically relogin because of autologin. i can only shutdown the client holding the power-button some secons and so teh session isn't cloed properly
06:39
i have found some hints in german here: http://www.lug-kr.de/wiki/LinuxTerminalServer but this is for kde only because of dcop: http://www.lug-kr.de/wiki/LinuxTerminalServer
06:40
do anyone have an idea how i can shutdown the client and close the x-session properly?
06:46tryltsp has left #ltsp
06:59scottmaccal has joined #ltsp
07:16ogra_ has joined #ltsp
07:17ogra has quit IRC
07:20cpnogueira has joined #ltsp
07:26vvinet has joined #ltsp
07:35wimiko has joined #ltsp
07:35wimiko has left #ltsp
07:36wimiko has joined #ltsp
07:41alkisg has quit IRC
07:48cpnogueira has left #ltsp
07:56cpnogueira has joined #ltsp
07:57Selveste1_ has joined #ltsp
08:00FrozenZia has joined #ltsp
08:03
<elias_a_>
FrozenZia: Hi, Paul :)
08:03
FrozenZia: Welcome! :)
08:04Selveste1__ has joined #ltsp
08:11alkisg has joined #ltsp
08:14bobbyC has joined #ltsp
08:14
<elias_a_>
alkisg: May I proudly present: a new dude on the channel from Finland!
08:15
FrozenZia has been infected by me, I guess :)
08:15mikkel has joined #ltsp
08:15
<alkisg>
welcome FrozenZia :)
08:16
Isn't asmo also from Finland?
08:20
<FrozenZia>
tx - yeah, he is.
08:20Selveste1_ has quit IRC
08:20
<FrozenZia>
I'm only 95% from Finland, though, as I live here. Originally called New Mexico, USA home...
08:22
Hey - silly question, how do I tell which of my nics (on the server) is supposed to be the one connected to "the network", and which is controlling the terminals?
08:22jammcq has joined #ltsp
08:24Selveste1__ has quit IRC
08:24
<FrozenZia>
(i.e. I don't remember which one I specified as the "active" one or whatever when I installed the server, and now I'm changing my network configuration, trying to get around this kernel panic problem I'm having
08:24
)
08:26Selveste1__ has joined #ltsp
08:26
<alkisg>
FrozenZia: just do ifconfig -a
08:26
You'll see which one has ip=192.168.0.1...
08:27
(or, cat /etc/network/interfaces)
08:28
<FrozenZia>
alkisg: ...and the "server - client" connection is handled with the .154 address I guess.
08:29
<alkisg>
Hm???
08:29
Only one of them should have 192.168.0.X
08:29
That's your ltsp facing nic
08:29
The other one should be on a different subnet
08:30
(the LTSP-facing one may have .1 or .254 depending on stuff...)
08:30scottmaccal has quit IRC
08:30
<FrozenZia>
Hmmm. Well, I got the answer to my question in any case, but I still may have network config issues after this then...
08:31
<alkisg>
Yeah if they are on the same subnet, you'll have problems
08:32Selveste1___ has joined #ltsp
08:32Selveste1__ has quit IRC
08:34
<FrozenZia>
Ok, well, now if I just change the IP for that LTSP nic, is that gonna "fix" things, or are there other things that will need doing (like with iptables or something?)
08:35
<alkisg>
What are your IP addresses now?
08:35
And, distro/version?
08:35
<FrozenZia>
Right now all I have is: LTSP server on "normal" network (192.168.0.102), and
08:35
Karmic -edubuntu
08:36
then a tiny 8-port switch with the other nic (192.168.0.154) plus terminal
08:36
<alkisg>
You mean .254?
08:36
<FrozenZia>
yes - right.
08:36
<jammcq>
both nics are 192.168.0.? ?
08:36
<alkisg>
OK, then do this:
08:36
sudo gedit /etc/network/interfaces
08:37
Change 192.168.0.254 to 192.168.1.254
08:37
sudo gedit /etc/ltsp/dhcpd.conf
08:37
Change *all* occurences of 192.168.0 to 192.168.1
08:37
sudo ltsp-update-sshkeys
08:37
sudo ltsp-update-image
08:37
Ah, I forgot to tell you to restart networking & dhcp3-server
08:38
update-image and ssh-keys should be executed *after* you restart networking
08:38
After that, you should be ok.
08:38
<FrozenZia>
Ok, well, I've also got to reinstall dhcp3 anyway, as I removed ti earlier...
08:38
<alkisg>
Heh :)
08:39
<FrozenZia>
And was there something to put in the /etc/dhcp3/dhcp.conf file that told it to be ignored?
08:39
(and use ltsp version instead)
08:39
<alkisg>
After you do the changes to 192.168.1.X, and if it doesn't work, post dhcp3.conf... but I think you'll be ok
08:41Brian_H has joined #ltsp
08:50rjune has joined #ltsp
08:51
<FrozenZia>
alkisg: hmmm... trouble... /etc/network/interfaces should I also change the "network" and "broadcast"?
08:52
Yes, it seems so...
08:52Gadi has joined #ltsp
08:52
<FrozenZia>
restarting networking says "ignoring unknown interface eth1=eth1.
08:54Selveste1____ has joined #ltsp
09:06
<FrozenZia>
Should I have dnsmasq-dhcp running? I seem to have, based on syslog error messages...
09:07Selveste1___ has quit IRC
09:07
<Gadi>
only if you intend to use it
09:07
:)
09:08
<FrozenZia>
Gadi: I just don't recall setting it up, so wondered if it was somehow part of the default setup with Karmic
09:08
<alkisg>
FrozenZia: run the following commands, and then upload all the screen output to pastebot
09:09
cat /etc/network/interfaces
09:09
ifconfig -a
09:09
cat /etc/ltsp/dhcpd.conf
09:09
dpkg -l dhcp3-server
09:09
dpkg -l dnsmasq
09:09
!pastebot
09:09
<ltspbot>
alkisg: "pastebot" is The LTSP pastebot is at http://pastebot.ltsp.org. Please paste all text longer than a line or two to the pastebot, as it helps to reduce traffic in the channel. A link to the content will be pasted in the channel.
09:10
<alkisg>
Karmic (and older Ubuntu versions) have dnsmasq-base by default, but not dnsmasq.
09:14
<elias_a_>
FrozenZia: Where in New Mexico?
09:15
<FrozenZia>
argh. Postbot ei nyt tunnu toimivan.
09:16
09:16
Oops. sorry!
09:16
That is, Postbot doesn't seem to be working...
09:17scottmaccal has joined #ltsp
09:17
<FrozenZia>
and elias got that other part.
09:17scottmaccal has quit IRC
09:19
<elias_a_>
FrozenZia: You're quite a similar lingual mess as I am :)
09:19
<alkisg>
FrozenZia: you can also use http://paste.ubuntu.com/
09:20
<FrozenZia>
http://paste.ubuntu.com/317870/
09:21
elias_a_: yep - I'm on a strange keyboard (Qwerty) as well, and that's throwing me off. I normally use svorak.
09:22
<alkisg>
Right. Well, remove dnsmasq, you usually shouldn't have both dnsmasq AND dhcp3-server....
09:23
Then do: sudo invoke-rc.d dhcp3-server restart
09:23
After that you should be OK, ready to boot the clients...
09:25
<FrozenZia>
09:25
<alkisg>
Yup
09:28
<FrozenZia>
09:28
<alkisg>
Ξεκίνησε; good!
09:28
;)
09:29
<FrozenZia>
but I still need to update my image, no?
09:29
<alkisg>
Yeah, and the ssh-keys
09:29
sudo ltsp-update-sshkeys && sudo ltsp-update-image
09:31Gadi has left #ltsp
09:32
<smuggboy>
a little question: after login from ltsp client on the server is a 32M Tmpfile create (like /tmp/tmp.YMXNd28eRX) and a process nbd-server startet... but when i hard-poweroff the client the file stays existent and nbd-server is still running - is that a normal behavor? and if yes how often should i clean up nbd-server processes?
09:34um|U has quit IRC
09:37alkisg has quit IRC
09:42Selveste1____ has quit IRC
09:43
<FrozenZia>
my ltsp client boot hangs, and complains that it can't connect to nbd-server.
09:44
Tried to restart nbd-server, and it claims not to be able to open config file.
09:47evilx has left #LTSP
09:48vvinet has quit IRC
09:57um|U has joined #ltsp
09:58rjune has quit IRC
10:01mushroomtwo is now known as mushroomblue
10:12staffencasa has joined #ltsp
10:16jordiA65 has joined #ltsp
10:20Ahmuck has joined #ltsp
10:27stgraber has quit IRC
10:27stgraber has joined #ltsp
10:27scottmaccal has joined #ltsp
10:29dro has joined #ltsp
10:32rjune has joined #ltsp
10:33jach has joined #ltsp
10:34alkisg has joined #ltsp
10:39
<dro>
jammcq: you done moving all the documentation to sourceforge?
10:40
<jammcq>
yep
10:41
<sbalneav>
jammcq: Main page might need some fixups
10:41
top links don't work.
10:41
<jammcq>
it ALL needs some fixups
10:41
<sbalneav>
yeah.
10:41
<jammcq>
main html page?
10:41
<sbalneav>
yeah, the homepage itself
10:42
<jammcq>
works here
10:42
try reloading
10:42
<sbalneav>
ok
10:42shawnp0wers has joined #ltsp
10:42
<sbalneav>
Hm, when I click on any of the "dowloads, documentatation support" links, they're still pointing to twiki
10:43
<jammcq>
what's the link?
10:43
<sbalneav>
durf
10:43
I think it was my squid proxy
10:43
<jammcq>
ah
10:43
<rjune>
LOL
10:43
<sbalneav>
i expired the cache
10:43
<jammcq>
there ya go
10:44
<sbalneav>
Hmmm
10:44
<rjune>
all better scotty?
10:44
<sbalneav>
I'll have to find a new place to host:
10:44
!docs
10:44
<ltspbot>
sbalneav: "docs" is For the most current documentation, see http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspDocumentationUpstream
10:44
<jammcq>
yep
10:44
the new wiki is a fine place for that
10:45
<sbalneav>
Sure, but I don't have shell access to upload the pdf's html's etc.
10:45
<jammcq>
and I've still got all the old files, just need to get them migrated into mediawiki
10:45
sbalneav: do you need shell access? And, if you do, I can give you that
10:45
in fact, I SHOULD give you that
10:45
<sbalneav>
they used to sit in http://ltsp.org/~sbalneav/blah
10:45
<jammcq>
no point in me being the only one
10:46
<sbalneav>
I'll take whatever I can get :)
10:46
<jammcq>
you won't have a homedir, but you will be able to put them somewhere that you can point to on the web
10:46
<sbalneav>
That's fine.
10:47
<jammcq>
my office is MUCH quieter now that the old Amd server is turned off
10:47
it was the loudest thing in my data center
10:48
probably used more electricity than all the rest of my servers combined
10:48
<alkisg>
Urm what? Sourceforge, mediawiki? Should I call for some press people?
10:48
<sbalneav>
alkisg: jammcq migrated all the old wiki data to the sourceforge wiki.
10:49
<alkisg>
Link?
10:49
<sbalneav>
www.ltsp.org
10:49
wiki link :)
10:49
<alkisg>
Nice! http://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_Documentation
10:50
A lot of red links though, so is upstream documentation going to be hosted in sf from now on?
10:50
Ooops sorry
10:50
<sbalneav>
jammcq: there still seems to be a LOT of red links. This just stuff that's not properly linked in yet, i.e. we need to edit these pages?
10:52
<jammcq>
I need to take the old files that I have, run them through my converter and paste them into the Mediawiki edit form
10:53
there will be red links for the next week or so, as I move through those
10:53
<sbalneav>
Ah, so they're not all done yet. OK, np
10:53
<jammcq>
yeah, not nearly done
10:53woodthechuck has joined #ltsp
11:01alkisg has quit IRC
11:15alkisg has joined #ltsp
11:15woodthechuck has quit IRC
11:20alkisg has joined #ltsp
11:31smuggboy has quit IRC
11:31Lns has joined #ltsp
11:37hersonls has joined #ltsp
11:45mushroomblue has quit IRC
11:46mushroomblue has joined #ltsp
11:48jordiA65 has quit IRC
12:01
<FrozenZia>
hey - n00b here - trying to get my client to boot. It gets an IP address, and things go well for a time, but then it stalls during nfs-top script and complains about not being able to reach the nbd-server...
12:03
<alkisg>
FrozenZia: so, is your nbd server running?
12:03
sudo netstat -nap|grep 2000
12:03
<FrozenZia>
alkisg: (this is after you helped me earlier, and having done the image-update, etc...
12:03
)
12:04
Well, yeah, id that's how I check, that shows tcp listening on port 0.0.0.0:2000
12:04
s/id/if
12:05
but /etc/init.d/nbd-server restart I think complained about a missing config file...
12:05
<alkisg>
After complaining, does it drop you to busybox?
12:05
No no don't do that
12:05
It's started from inetd, so you shouldn't run it directly
12:05
<FrozenZia>
yes it does.
12:06
<alkisg>
sudo invoke-rc.d openbsd-inetd restart
12:06
Erm I'm not sure what happens if you run it directly... is it easy to reboot the server, just to be sure?
12:07
<johnny>
FrozenZia, you're not supposed to manually use /etc/init.d/nbd-server
12:08
oh.. alkisg already said that
12:08
hey alkisg !
12:08
<alkisg>
Hi Γιάννη :)
12:08
(=johnny in Greek :))
12:12
<FrozenZia>
ok, well, that invoke didn't seem to get the desired result, so will try a reboot. B4 I do, though,
12:13
I earlier in the week managed to remove all the "bits" which tell the system it should run dhcp server on startup -- how should I fix that?
12:14
(extremely low, humble bowing for my ignorance, and begging your collective patience...)
12:14
<alkisg>
You deleted the init script? Urm, I'm not sure what its name is, as I don't use dhcp3-server myself... I always use dnsmasq
12:15
Why don't you reinstall dhcp3-server to make it come back?
12:15
<FrozenZia>
Well, I thought of that, but it then didn't seem to agree that it was ever removed (i.e. said it was present, so would not install)
12:16
perhaps apt-get purge dhcp3-server?
12:16
<alkisg>
sudo apt-get install --reinstall dhcp3-server
12:21japerry has quit IRC
12:23
<FrozenZia>
should I need to do any updates at this point? (sshkeys + image?)
12:25
<johnny>
no..
12:25CAN-o-SPAM has joined #ltsp
12:31scottmaccal has joined #ltsp
12:33
<scottmaccal>
Happy Friday all.
12:33
<FrozenZia>
ok, argh. Still no joy, and it's getting close to my bedtime...
12:34
any other clues?
12:42Kicer86 has joined #ltsp
12:50dro has quit IRC
12:50scottmaccal has quit IRC
12:51rjune has quit IRC
13:02rjune has joined #ltsp
13:04squarepeg has joined #ltsp
13:07ftherese has joined #ltsp
13:08
<ftherese>
I'm reading: https://help.ubuntu.com/community/UbuntuLTSPJauntyPrinting
13:08
And I am curious to know if this solution takes into account a local ltsp printer
13:09
with multiple ltsp servers
13:10
My problem is, currently I have four ltsp servers and the thin client which hosts the printer does not always connect to the same server
13:11
so in order to deal with this situation, I have cups installed on all four servers
13:11
<rjune>
ftherese, that seems like a bad way to do it
13:11
<ftherese>
I agree
13:11
<rjune>
why not force that terminal to one server?
13:12
<ftherese>
how/where?
13:12
It always has the same IP address
13:12
that should be enough right?
13:12
<rjune>
well. not really
13:13
<ftherese>
I mean... if the cups server goes out to the same ip address every time
13:13
<rjune>
from the sounds of what you said, that terminal gets a DHCP response back from a different server each time.
13:13
ftherese, yeah, that should do it.
13:14
what I would do is set DHCP on three servers to ignore that terminal, then configure it on the fourth
13:14
<ftherese>
ahhh
13:14
where is the documentation on that?
13:14
<rjune>
host registration part is easy.
13:14
it's the ignoring I would have to look up.
13:14
<ftherese>
yeah... me too
13:14tux_440volt has joined #ltsp
13:14
<ftherese>
I have it included by mac address in the current dhcp
13:15
on all four servers
13:15
so no matter what server it receives DHCP from it goes to 192.168.1.7
13:15
<rjune>
http://linux.derkeiler.com/Newsgroups/comp.os.linux.networking/2006-01/msg00145.html <-- that might do it for you
13:16shawnp0wers has quit IRC
13:16
<ftherese>
I'm looking at it... booting keyword
13:17
host mediamvp {
13:17
hardware ethernet xx:xx:xx:xx:xx:xx;
13:17
ignore booting;
13:17
}
13:18
I am going to give that a try... thanks
13:22
let me get this straight logically - The thin client with the printer HAS to be attached to the same server as the CUPS server?
13:24
<alkisg>
FrozenZia: so you're getting a busybox?
13:27
<ftherese>
It seems to me like the ltsp server and the cups server could be two separate machines, and the thin client with the printer attached (having the same ip address each time) just publishes and receives to the cups server
13:28
But if I understand correctly, the thin client with the printer has to boot from an ltsp server that is also running cups
13:29
<johnny>
isn't there some lts.conf setting for that..
13:29
<rjune>
ftherese, HAS? no.
13:30
ftherese, they can be two seperate machines, realistically the print server only needs to be running CUPS and sharing the printer.
13:30
ftherese, however, it's easier on you if it's on a static address and only talks to one server.
13:30
only one place to configure, not four
13:44Selveste1____ has joined #ltsp
13:53spectra has quit IRC
14:02alkisg has quit IRC
14:04squarepeg has quit IRC
14:05cpnogueira has quit IRC
14:05squarepeg has joined #ltsp
14:07alkisg has joined #ltsp
14:16dro has joined #ltsp
14:23mushroomtwo has joined #ltsp
14:23wimiko has quit IRC
14:25mushroomb1ue has joined #ltsp
14:25mushroomtwo has quit IRC
14:25mushroomblue has quit IRC
14:26mushroomb1ue is now known as mushroomblue
14:34mushroomtwo has joined #ltsp
14:38mushroomblue has quit IRC
14:38mushroomtwo is now known as mushroomblue
15:01hersonls has quit IRC
15:03Kicer86 has quit IRC
15:07pmatulis has quit IRC
15:25johnny has left #ltsp
15:37scottmaccal has joined #ltsp
15:51dro has quit IRC
15:52tux_440volt has quit IRC
15:59
<ftherese>
is it still necessary to add the ltsp local printer as a jetdirect printer in cups? or can it be added as usb:// (that's what the newer documentation seems to suggest)
16:01
I would like to try the thin client local printer as usb with it's own driver to see if it improves speed problems
16:03
<FrozenZia>
alkisg: yeah, I get a BusyBox. Unfortunately this stuff's at work, and I won't be back there 'til Monday, so have to return to the problem then. But if you have any tips, I'm glad to hear them before then.
16:04
<alkisg>
FrozenZia: I would tell you to try the nbd-client mounting command manually, to see the error message...
16:06
<FrozenZia>
that "sudo invoke-rc.d openbsd-inetd restart" command?
16:06
<alkisg>
No no from the busybox, on the client
16:06japerry has joined #ltsp
16:07
<alkisg>
nbd-client 192.168.1.254 2000 /dev/nbd0 -persist
16:07
Try that on Monday and see what it tells you
16:08
<FrozenZia>
(long story, but I sort of still *am* at work - I may just have to give that a try b4 I head home...)
16:20jach has quit IRC
16:55alkisg has quit IRC
16:57scottmaccal has quit IRC
16:59mikkel has quit IRC
17:04CAN-o-SPAM has quit IRC
17:06
<FrozenZia>
Ok, alkisg left already, but if anyone can help, here's what happened in my case, After nbd-client 192.168.1.254 2000 /dev/nbd0 -persist
17:06
I got:
17:07
(at the busybox on the terminal)
17:07vagrantc has joined #ltsp
17:07
<FrozenZia>
http://paste.ubuntu.com/318214/
17:07jammcq has quit IRC
17:13bobbyC has quit IRC
17:19scottmaccal has joined #ltsp
17:24leio has quit IRC
17:29leio has joined #ltsp
17:39japerry has quit IRC
17:41Sarten-X2 has quit IRC
17:53pmatulis has joined #ltsp
17:56japerry has joined #ltsp
18:09japerry has quit IRC
18:16sergiodlc has joined #ltsp
18:17
<sergiodlc>
Hi! Whenever I connect my USB flash drive to my thin client it shows only garbage
18:18
Can you help me with that?
18:27sergiodlc has left #ltsp
18:33Egyptian[Home]1 has quit IRC
18:35Egyptian[Home] has joined #ltsp
18:45staffencasa has quit IRC
18:51Lns has quit IRC
19:11vagrantc has quit IRC
19:14lucascoala has joined #ltsp
19:16ftherese has quit IRC
19:22ftherese has joined #ltsp
19:23Brian_H has quit IRC
19:43johnny1 has joined #ltsp
19:49lucascoala_ has joined #ltsp
19:57lucascoala has quit IRC
19:57pmatulis has quit IRC
20:42johnny1 has left #ltsp
21:09scottmaccal has quit IRC
21:17japerry has joined #ltsp
21:19squarepeg_ has joined #ltsp
21:29alexqwesa__ has joined #ltsp
21:33squarepeg_ has quit IRC
21:42alexqwesa_ has quit IRC
22:08alkisg has joined #ltsp
22:52FGXR6 has joined #ltsp
22:52F-GTSC has quit IRC
23:31alexqwesa__ is now known as alexqwesa