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


Channel log from 29 May 2017   (all times are UTC)

00:09vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
00:35lucascastro has joined IRC (lucascastro!~lucas@186.227.186.18)
01:28lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Remote host closed the connection)
01:29lucascastro has joined IRC (lucascastro!~lucas@186.227.186.18)
05:01cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
05:30lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Remote host closed the connection)
06:20ricotz has joined IRC (ricotz!~ricotz@p5B2A93BB.dip0.t-ipconnect.de)
06:20ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:20johnsmith has joined IRC (johnsmith!~Adium@182.69.120.68)
06:21Statler has joined IRC (Statler!~Georg@p4FC1FE06.dip0.t-ipconnect.de)
06:34
<alkisg>
!ltsp-source
06:34
<ltsp>
ltsp-source: at http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/files
06:35
<alkisg>
!forget ltsp-source
06:35
<ltsp>
The operation succeeded.
06:35
<alkisg>
!learn ltsp-source as at https://git.launchpad.net/ltsp/tree/
06:35
<ltsp>
The operation succeeded.
06:35
<alkisg>
!source
06:35
<ltsp>
My source is at http://supybot.com/
06:35
<alkisg>
!ltsp
06:35
<ltsp>
ltsp: LTSP is the Linux Terminal Server Project, the open source thin client solution. You can find it at http://www.ltsp.org
06:35
<alkisg>
!forget ltsp
06:35
<ltsp>
The operation succeeded.
06:35
<alkisg>
!ltsp
06:35
<ltsp>
I do not know about 'ltsp', but I do know about these similar topics: 'ltsp-upstream', 'ltsp-trunk', 'ltsp42', 'bestltspdistro', 'ltsp5', 'ltspsource', 'ltsp-discuss', 'ltsp-developer', 'kiwi-ltsp', 'ltsp-update-image', 'ltsp-update-sshkeys', 'ltspfs-source', 'ltsp-sources', 'ltsp-bug', 'ltsp_config.d', 'ltsp-update-kernels', 'ltsp6', 'pkg-ltsp-debian', 'pkg-ltsp-ubuntu', 'ltsp-pnp', 'non-ltsp', 'ltsp-docs', 'ltsp-info', (1 more message)
06:35
<alkisg>
!ltsp-trunk
06:35
<ltsp>
ltsp-trunk: The LTSP code is at https://code.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk
06:35
<alkisg>
!forget ltsp-trunk
06:35
<ltsp>
The operation succeeded.
06:36
<alkisg>
!ltsp-upstream
06:36
<ltsp>
ltsp-upstream: Comitters to the LTSP upstream branch on launchpad: https://launchpad.net/~ltsp-upstream
06:36
<alkisg>
!ltsp42
06:36
<ltsp>
ltsp42: The latest version of LTSP is version 4.2. You can find out all information about it on http://wiki.ltsp.org/twiki/bin/view/Ltsp/LTSP-42
06:36
<alkisg>
!forget ltsp42
06:36
<ltsp>
The operation succeeded.
06:36
<alkisg>
!bestltspdistro
06:36
<ltsp>
bestltspdistro: whatever you prefer
06:36
<alkisg>
!ltsp5
06:36
<ltsp>
ltsp5: ltsp5 is The next version of LTSP, and the future of Thin Client computing on GNU/Linux. http://wiki.ltsp.org/twiki/bin/view/Ltsp/Ltsp5
06:36
<alkisg>
!forget ltsp5
06:36
<ltsp>
The operation succeeded.
06:36
<alkisg>
!ltspsource
06:36
<ltsp>
ltspsource: https://code.launchpad.net/~ltsp-upstream
06:37
<alkisg>
!forget ltspsource
06:37
<ltsp>
The operation succeeded.
06:37
<alkisg>
!ltspfs-source
06:37
<ltsp>
ltspfs-source: at http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltspfs-trunk/files
06:37
<alkisg>
!forget ltspfs-source
06:37
<ltsp>
The operation succeeded.
06:37
<alkisg>
!learn ltspfs-source as at https://git.launchpad.net/~ltsp-upstream/ltsp/+git/ltspfs/tree/
06:37
<ltsp>
The operation succeeded.
06:38
<alkisg>
!non-ltsp
06:38
<ltsp>
non-ltsp: It's better to direct your questions to the most suitable channel. For example, for questions that are not specific to LTSP, you might try distro-specific channels, such as #ubuntu, #debian, #suse, #fedora etc.
06:38
<alkisg>
!ltsp_config.d
06:38
<ltsp>
ltsp_config.d: You can create /opt/ltsp/i386/usr/share/ltsp/ltsp_config.d/ and put scripts in it that dynamically set lts.conf variables. Those scripts are sourced by LTSP, not executed.
06:38
<alkisg>
!dpkg-ltsp-debian
06:38
<ltsp>
Error: "dpkg-ltsp-debian" is not a valid command.
06:38
<alkisg>
!pkg-ltsp-debian
06:38
<ltsp>
pkg-ltsp-debian: https://code.launchpad.net/~vagrantc/ltsp/ltsp-debian-packaging is a mirror of http://anonscm.debian.org/loggerhead/pkg-ltsp/ltsp-debian-packaging/files
06:38
<alkisg>
!forget pkg-ltsp-debian
06:38
<ltsp>
The operation succeeded.
06:38
<alkisg>
!forget pkg-ltsp-ubuntu
06:38
<ltsp>
The operation succeeded.
06:38
<alkisg>
!ltsp
06:38
<ltsp>
I do not know about 'ltsp', but I do know about these similar topics: 'ltsp-upstream', 'bestltspdistro', 'ltsp-discuss', 'ltsp-developer', 'kiwi-ltsp', 'ltsp-update-image', 'ltsp-update-sshkeys', 'ltsp-sources', 'ltsp-bug', 'ltsp_config.d', 'ltsp-update-kernels', 'ltsp6', 'ltsp-pnp', 'non-ltsp', 'ltsp-docs', 'ltsp-info', 'ltsp-pnp-debian', 'ltsp-git', 'ltsp6bugs', 'ltsp_config_env', 'ltsp-source', 'ltspfs-source'
06:39
<alkisg>
!ldm
06:39
<ltsp>
ldm: LDM is the LTSP Display Manager, required for LTSP thin/fat clients, because it authenticates the users to the server via SSH.
06:39
<alkisg>
!forget ldm
06:39
<ltsp>
The operation succeeded.
06:39
<alkisg>
!ldm
06:39
<ltsp>
I do not know about 'ldm', but I do know about these similar topics: 'ldm-trunk', 'ldm-source', 'ldm-dualhead', 'ldm-po', 'worldmap', 'LDM_SESSION', 'LDM_PASSWORD_HASH'
06:39
<alkisg>
!ldm-source
06:39
<ltsp>
ldm-source: at http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/files
06:39
<alkisg>
!forget ldm-source
06:39
<ltsp>
The operation succeeded.
06:39
<alkisg>
!learn ldm-source as at https://git.launchpad.net/~ltsp-upstream/ltsp/+git/ldm/tree/
06:39
<ltsp>
The operation succeeded.
06:39
<alkisg>
!ldm-trunk
06:39
<ltsp>
ldm-trunk: The LTSP Display Manager (LDM) code is at https://code.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk
06:39
<alkisg>
!forget ldm-trunk
06:39
<ltsp>
The operation succeeded.
06:39
<alkisg>
!ldm-po
06:39
<ltsp>
ldm-po: To see if LDM is translated in your language: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/files/head:/po/ If it isn't, send a mail with the translation to the ltsp-developers mailing list.
06:40
<alkisg>
!forget ldm-po
06:40
<ltsp>
The operation succeeded.
06:40
<alkisg>
!ldm-dualhead
06:40
<ltsp>
ldm-dualhead: see: https://bugs.launchpad.net/ltsp/+bug/693151
06:40
<alkisg>
!forget ldm-dualhead
06:40
<ltsp>
The operation succeeded.
06:40
<alkisg>
!LDM_SESSION
06:40
<ltsp>
LDM_SESSION: to specify a default session for clients, run ls /usr/share/xsessions , see the filename.desktop that you're interested in, and then put LDM_SESSION="filename". For example, LDM_SESSION="gnome-fallback" or LDM_SESSION="ubuntu".
06:40
<alkisg>
!learn ldm as LDM is the LTSP Display Manager, required for LTSP thin/fat clients, because it authenticates the users to the server via SSH.
06:40
<ltsp>
The operation succeeded.
06:41
<alkisg>
!learn LTSP as LTSP is the Linux Terminal Server Project, the open source thin/fat client solution. You can find it at http://www.ltsp.org
06:41
<ltsp>
The operation succeeded.
06:49mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
07:09mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Read error: Connection reset by peer)
07:11mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
07:17atulmodi has joined IRC (atulmodi!01177c85@gateway/web/freenode/ip.1.23.124.133)
07:18
<atulmodi>
i have installed LTSP but thinpc are not getting the screen (greeter) what can be issue. I have followed all steps they have explained
07:18
can someone help me with this
07:19
<alkisg>
Hi atulmodi
07:19
Which distro/version are you using?
07:19
<atulmodi>
ubuntu 16.04
07:19
<alkisg>
which steps have you followed, some tutorial?
07:19
<atulmodi>
http://www.havetheknowhow.com/Configure-the-server/Install-LTSP.html
07:20
http://www.havetheknowhow.com/Configure-the-server/Configure-LTSP.html
07:20
<alkisg>
How much RAM do your clients have?
07:21
<atulmodi>
512 MB
07:21
<alkisg>
And what cpu? E.g. pentium 4, at how many GHz?
07:21
<atulmodi>
that don't know, I will find out, but those are getting used right now with Ubuntu 10.04 server and its working fine there
07:22
now we have bought new server so we are installing new OS
07:22
<alkisg>
I was asking in order to propose thin or fat client mode to you
07:22
!ltsp-pnp
07:22
<ltsp>
ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
07:22
<alkisg>
This is the best tutorial on how to install ltsp
07:22
(if you want to start from the beginning)
07:23
If you want to troubleshoot the installation you made... what is the last message that you see when the clients boot?
07:24
<atulmodi>
how to check that clients boot
07:24
please tell me
07:24
<alkisg>
With your eyes
07:24
Check the client and see what message it says
07:24
Then write it here so that we see how far it goes
07:25
Here is one example: https://www.novell.com/coolsolutions/img/19873-2lg.jpg
07:25
Do you see the client loading the kernel? initrd? etc
07:26
<atulmodi>
so which log file to check, that's what I was asking, can you tell that
07:26
On the thinpc blank screen is coming,
07:27
<alkisg>
Before the blank screen, what does the pc show
07:27
<atulmodi>
ok give me a min.
07:27
<alkisg>
On the server, one file to check is /var/log/syslog, but we want the client screen more than the server logs
07:29
<atulmodi>
but client computer are not possible
07:29
this file /var/log/syslog, i can get yuo
07:30
<alkisg>
it's not possible to see the client screen, and what messages it shows before going blank?
07:30
Why is it not possible?
07:30
<atulmodi>
root@hostserver:~# tail -f /var/log/syslog May 29 12:59:32 hostserver dhcpd[1546]: DHCPINFORM from 192.168.5.88 via em1 May 29 12:59:32 hostserver dhcpd[1546]: DHCPACK to 192.168.5.88 (00:24:8c:a6:ea:dc) via em1 May 29 12:59:42 hostserver dhcpd[1546]: DHCPINFORM from 192.168.5.61 via em1 May 29 12:59:42 hostserver dhcpd[1546]: DHCPACK to 192.168.5.61 (00:1e:8c:c6:22:2a) via em1 May 29 13:00:10 hostserver dhcpd[1546]: DHCPINFORM from 19
07:31
<alkisg>
!pastebin
07:31
<ltsp>
pastebin: try !paste
07:31
<alkisg>
!paste
07:31
<ltsp>
paste: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
07:31
<alkisg>
Use pastebin to put syslog
07:31
<atulmodi>
!paste
07:31
<ltsp>
paste: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
07:32
<atulmodi>
<script src="https://pastebin.com/embed_js/Q0N8T4yX"></script>
07:33
<alkisg>
OK so this shows the client got an IP
07:33
Nothing more
07:33
<atulmodi>
We have 256 mb RAM
07:33
<alkisg>
Now you need to show the client screen messages
07:33
<atulmodi>
for client
07:34
ok in couple of min. i get
07:34
that screen appears for 1 sec. how to capture that
07:35
i am talking about thinpc
07:35
<alkisg>
!quiet
07:35
<ltsp>
quiet: to enable the Debian kernel and initramfs to show up more messages, in order to better troubleshoot the boot process, remove "quiet" from /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
07:35
<alkisg>
!quiet-splash
07:35
<ltsp>
quiet-splash: to disable the splash screen in Ubuntu, in order to see any boot error messages, run sudo gedit /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default and remove quiet splash plymouth:force-splash vt.handoff=7
07:35
<alkisg>
Remove "quiet splash" in that file
07:35
And reboot the client
07:40
<atulmodi>
I don't find this in the file u explained
07:41
<alkisg>
On the server, run: ls -l /var/lib/tftpboot/ltsp/*/pxelinux.cfg/default
07:41
What is the output?
07:42
<atulmodi>
lrwxrwxrwx 1 root root 4 May 24 14:19 /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default -> ltsp
07:44
<alkisg>
See, so that's the file you were looking
07:44
You need to open it and remove "quiet splash" from there
07:44
<atulmodi>
ya in that the thing which you told I couldn't find
07:44
can I past that data here
07:45
<alkisg>
In pastebin, yes
07:47
<atulmodi>
<script src="https://pastebin.com/embed_js/tKdm7Wpy"></script>
07:48
did you got this file Sir
07:48
<alkisg>
Yes; it appears that you already removed "quiet splash", maybe your tutorial did that
07:49
Do you have another client to test with?
07:49
<atulmodi>
ya we have 10+ clients
07:49
i told them to get me 1 picture via mobile
07:49
but they are unable to capture picture of screen due to speed at which it goes away
07:49
<alkisg>
I mean a client with completely different hardware
07:50
For example, a new laptop
07:50
Or a desktop pc
07:50
Because those might show the messages without them going away
07:51
<atulmodi>
No we don't have that
07:51
is there any other method to identify
07:51
<alkisg>
You can use virtual clients, for example
07:51
!kvm
07:51
<ltsp>
kvm: Virtual thin client: kvm -m 256 -vga vmware -ctrl-grab -no-shutdown -net nic,model=virtio -net user,tftp=/var/lib/tftpboot,bootfile=/ltsp/i386/pxelinux.0
07:51
<atulmodi>
right now i am doing following steps from this link >> https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
07:51
<alkisg>
Are you following the steps on the existing installation, or on a new installation?
07:52
<atulmodi>
till this min. i was following existing installation
07:52
<alkisg>
Because if you already have a broken installation, the ltsp-pnp guide won't fix it
07:52
<atulmodi>
when i am writing this side by side i am installing it again
07:52
over the old one
07:53
<alkisg>
So if you have installed isc-dhcp-server there, how will dnsmasq work?
07:53
You can't have 2 dhcp servers
07:53
Don't use the new guide over the old installation, it won't work
07:53
<atulmodi>
ohh
07:53
<alkisg>
You would need to clean the old installation, or do a new one
07:54
<atulmodi>
I will do as per your steps
07:54
if possible
07:54
if that works
07:54
i have to reboot the server because this command didn't worked >> ltsp-config dnsmasq
07:56
So what should i do
07:56
<alkisg>
I sent you a personal message, did you see it?
07:56
here in irc
07:57
<atulmodi>
No Sir
07:57
yes
07:57
yes
07:57
<alkisg>
OK
07:58
<atulmodi>
ok got it, but can you please help me with existing one
08:02atulmodi has left IRC (atulmodi!01177c85@gateway/web/freenode/ip.1.23.124.133, Quit: Page closed)
09:36johnsmith has left IRC (johnsmith!~Adium@182.69.120.68, Quit: Leaving.)
09:37johnsmith has joined IRC (johnsmith!~Adium@182.69.120.68)
09:37johnsmith has left IRC (johnsmith!~Adium@182.69.120.68, Client Quit)
09:40Statler has left IRC (Statler!~Georg@p4FC1FE06.dip0.t-ipconnect.de, Remote host closed the connection)
10:11markus_e92 has left IRC (markus_e92!~markus_e9@91-115-156-221.adsl.highway.telekom.at, Ping timeout: 240 seconds)
10:14markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-152-97.adsl.highway.telekom.at)
11:22johnsmith has joined IRC (johnsmith!~Adium@182.69.120.68)
12:01gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
12:41lucascastro has joined IRC (lucascastro!~lucas@186.227.186.18)
13:15lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Read error: Connection reset by peer)
13:17lucascastro has joined IRC (lucascastro!~lucas@186.227.186.18)
13:22adrianorg has joined IRC (adrianorg!~adrianorg@179.177.215.193.dynamic.adsl.gvt.net.br)
13:40GodFather has joined IRC (GodFather!~rcc@47.33.250.142)
14:24mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
15:05johnsmith has left IRC (johnsmith!~Adium@182.69.120.68, Quit: Leaving.)
15:25GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 240 seconds)
15:53lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Ping timeout: 260 seconds)
16:12raphr has joined IRC (raphr!~raphr@cxr69-8-82-240-20-129.fbx.proxad.net)
16:15
<raphr>
hi ! with ltsp pnp I am using LDM_AUTOLOGIN=true and same username/password on several clients. Is there a way to have this user local (from the chroot) instead of ssh mounted ?
16:19markus_e92 has left IRC (markus_e92!~markus_e9@91-115-152-97.adsl.highway.telekom.at, Ping timeout: 245 seconds)
16:21markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-152-97.adsl.highway.telekom.at)
16:32johnsmith has joined IRC (johnsmith!~Adium@122.162.163.149)
17:02gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
17:02johnsmith has left IRC (johnsmith!~Adium@122.162.163.149, Quit: Leaving.)
17:15
<alkisg>
raphr: do you want to use a local home dir, that would be lost on reboot?
17:16johnsmith has joined IRC (johnsmith!~Adium@122.162.163.149)
17:16johnsmith has left IRC (johnsmith!~Adium@122.162.163.149)
17:17
<raphr>
yes. non persistent settings is well suited for my needs
17:17
<alkisg>
raphr: do you think the RAM is enough for that, or would you need temporary storage from the server?
17:17
E.g. suppose a user just surfs for a few hours, and his .cache folder grows a lot
17:18
Or downloads a few files or works on a few new files
17:19
<raphr>
it just lanch a remote desktop session vmware horizon view client with minimal openbox windows manager
17:19
<alkisg>
OK
17:19
So, one way is this
17:19
Create a user on the server, let's call it ltsp
17:20
And put RCFILE_01="mkdir -p /home/ltsp; chown 1234:1234 /home/ltsp" to lts.conf
17:21
That way the authentication for the user will still happen on the server, but the content will be local\
17:21
Because the ltsp scripts will see that the /home/ltsp dir exists, so they won't try to sshfs mount it from the server
17:21
<raphr>
great
17:23
but this user has got some files in the profile
17:24
.config and some home scripts
17:25
maybe put this in a tar and untar isttead of mkdir ?
17:25
<alkisg>
No
17:25
Create an ltsp user on the server\
17:25
Populate/use it normally
17:26
Then put /home/ltsp in /etc/ltsp/ltsp-update-image.excludes\
17:26
So that ltsp-pnp won't exclude it, and it will be in the generated image
17:26
Hrm
17:26
Better yet, you could serve it with nbd
17:27
i.e. instead of using tar, to create an .ext4 image of /home/ltsp, and use nbd-server to mount it to client /home
17:27
This also gives writing space if you serve it with copy-on-write mode of nbd-server
17:27
Anyway, 3 options, do whichever is easier for you
17:27
The best one is nbd-based
17:27
<raphr>
OK thank you !
17:28
<alkisg>
It also allows to easily update the home/ltsp without reupdating the ltsp image
17:29
<raphr>
you're right. I'll try nbd option. nbd mounting is lts.conf parameter ?
17:30
<alkisg>
No, you'll need an RCFILE for that, or better yet an ldm login script, so that it's cleared on every login
17:30
So that if the user logs out and in again, the previous user data is cleared
17:30
(and it also allows fetching new /home/ltsp image from the server without even client reboot)
17:32
<raphr>
brillant. Not sure if i'll succed but I'll try.
17:32
Thank you
17:32
<alkisg>
You're welcome
17:45raphr has left IRC (raphr!~raphr@cxr69-8-82-240-20-129.fbx.proxad.net, Quit: ChatZilla 0.9.93 [Firefox 53.0.3/20170518000419])
17:45lucascastro has joined IRC (lucascastro!~lucas@201.57.40.146)
18:52gbaman has joined IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com)
20:01markus_e92 has left IRC (markus_e92!~markus_e9@91-115-152-97.adsl.highway.telekom.at, Ping timeout: 240 seconds)
20:04markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-152-97.adsl.highway.telekom.at)
20:15lucascastro has left IRC (lucascastro!~lucas@201.57.40.146, Remote host closed the connection)
20:22
<alkisg>
!cheap-client
20:22
<ltsp>
cheap-client: (#1) http://www.gearbest.com/tv-box-mini-pc/pp_343636.html, or (#2) https://www.aliexpress.com/store/product/New-arrival-Beelink-Pocket-Z83-Windows-10-Mini-PC-Z8300-64bit-1-84GHz-2GB-RAM-32GB/1871240_32640039781.html
20:29ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
20:44
<quinox>
that *is* cheap
20:46
I recently bought an Intel NUC, while not this cheap it's also pretty cheap
20:46
works like a charm
20:59
(not specifically as LTSP client)
21:00
a Raspberry Pi Zero W costs $10... amazing times
21:38gehidore is now known as cloudflare_hates
21:38cloudflare_hates is now known as gehidore
21:47GodFather has joined IRC (GodFather!~rcc@47.33.250.142)
23:46gbaman has left IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com, Remote host closed the connection)
23:47gbaman has joined IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com)
23:51gbaman has left IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com, Ping timeout: 245 seconds)
23:57gbaman has joined IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com)