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


Channel log from 4 January 2013   (all times are UTC)

00:47Parker955_Away is now known as Parker955
00:50alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47)
00:52andygraybeal_ has left IRC (andygraybeal_!~andy@h16.69.213.151.dynamic.ip.windstream.net, Quit: Ex-Chat)
01:03adrianorg_ has left IRC (adrianorg_!~adrianorg@177.134.58.217, Ping timeout: 260 seconds)
01:18Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
01:46vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
02:11Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 265 seconds)
02:27Parker955 is now known as Parker955_Away
02:47Parker955_Away is now known as Parker955
04:03Parker955 is now known as Parker955_Away
04:06Parker955_Away is now known as Parker955
04:08SmallR2002 has joined IRC (SmallR2002!~quassel@c-98-253-173-240.hsd1.il.comcast.net)
05:10telex has left IRC (telex!~telex@freeshell.de, Ping timeout: 255 seconds)
05:20telex has joined IRC (telex!~telex@freeshell.de)
05:32telex has left IRC (telex!~telex@freeshell.de, Ping timeout: 255 seconds)
05:49telex has joined IRC (telex!~telex@freeshell.de)
06:26bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
06:36Parker955 is now known as Parker955_Away
07:27Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
07:37Hyperbyte has left IRC (Hyperbyte!jan@middelkoop.cc, Read error: Connection reset by peer)
07:41Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 255 seconds)
07:43vmlintu has joined IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi)
08:20Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
08:31komunista has joined IRC (komunista!~slavko@adsl-195-168-234-074.dynamic.nextra.sk)
08:51dobber has joined IRC (dobber!~dobber@213.169.45.222)
09:04leio has left IRC (leio!~leio@gentoo/developer/leio, Quit: No Ping reply in 180 seconds.)
09:04leio has joined IRC (leio!~leio@gentoo/developer/leio)
10:22Hyperbyte has joined IRC (Hyperbyte!jan@middelkoop.cc)
10:34MonkWitDaFunk has joined IRC (MonkWitDaFunk!~yaaic@199-7-158-72.eng.wind.ca)
10:51Gremble has joined IRC (Gremble!~Ben@cpc29-aztw23-2-0-cust144.18-1.cable.virginmedia.com)
10:53Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 255 seconds)
11:07Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
11:41adrianorg_ has joined IRC (adrianorg_!~adrianorg@177.156.226.130)
12:07Ukir1 has joined IRC (Ukir1!~chatzilla@120.174.108.74)
12:45Ukir1 has left IRC (Ukir1!~chatzilla@120.174.108.74)
12:50ltspuser_49 has joined IRC (ltspuser_49!2597e653@gateway/web/freenode/ip.37.151.230.83)
12:53ltspuser_49 has left IRC (ltspuser_49!2597e653@gateway/web/freenode/ip.37.151.230.83, Client Quit)
12:57Gremble has left IRC (Gremble!~Ben@cpc29-aztw23-2-0-cust144.18-1.cable.virginmedia.com, Quit: I Leave)
12:58markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)
13:18Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Read error: Operation timed out)
13:20adrianorg_ has left IRC (adrianorg_!~adrianorg@177.156.226.130, Ping timeout: 246 seconds)
13:23ddmcse has joined IRC (ddmcse!~ddunn@23-25-213-225-static.hfc.comcastbusiness.net)
13:57ddmcse has left IRC (ddmcse!~ddunn@23-25-213-225-static.hfc.comcastbusiness.net, Quit: Leaving)
14:17
<sbalneav>
Morning all
14:25alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, Quit: Хана X'ам !!!)
14:25alexqwesa_ has joined IRC (alexqwesa_!~alex@109.172.12.47)
14:33
<knipwim>
hey Scotty
14:33
<sbalneav>
hey knipwim
14:49bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Quit: Leaving.)
15:10adrianorg_ has joined IRC (adrianorg_!~adrianorg@177.156.226.130)
15:24adrianorg_ has left IRC (adrianorg_!~adrianorg@177.156.226.130, Ping timeout: 264 seconds)
15:40jammcq has joined IRC (jammcq!~jam@c-98-209-67-190.hsd1.mi.comcast.net)
15:40
<jammcq>
good morning friends
15:42
<sbalneav>
morning jammcq
15:42
<jammcq>
hey Scotty !!!!!!!!!!
15:44mnevans has joined IRC (mnevans!8008b09d@gateway/web/freenode/ip.128.8.176.157)
15:48
<mnevans>
Hello LTSP World. I am having trouble booting an i386 client (Intel N270 CPU, 1600 series client from disklessworkstations.com), built on an amd64 host under Debian/Wheezy (testing).
15:48
The first error message is: "Can't execute /usr/bin/test: Exec format error".
15:49
I do note the kernel is labeled 486, not 386, FWIW.
15:49
<jammcq>
sounds like a good kernel, but bad libraries
15:49
<mnevans>
No problem booting this client before, built on same host except under Ubuntu 10.04-12.04.
15:49
<jammcq>
you probably have filesystem image built on 64-bit libs
15:50
when building the ltsp image, there's a way to tell it you want 32-bit instead
15:50
<mnevans>
@jammcq: I did rebuild the client this morning in case something went wrong there, but didn't see any error messages.
15:50
I did pass arch=i386 to ltsp-build-client, and it appeared to do that build...
15:50
<jammcq>
hmm
15:51
i'm at the edge of my ability to help
15:51
<mnevans>
Under /opt/ltsp/i386/lib I see a directory i386-linux-gnu with lots of libraries.
15:52
There is also a directory: lib64.
15:52
Only one file: ld-linux-x86-64.so.2 there.
15:53
Per error message, I did ltsp-chroot, then which exec - no answer.
15:54
as chroot, /usr/bin/test returns nothing. Maybe that is a red herring?
15:56
<jammcq>
test doesn't return anything
15:56
at least not on stdout
15:56
<sbalneav>
mnevans: How did you build the chroot? did you add --arch i386?
15:56
<jammcq>
do: /usr/bin/test; echo $?
15:57
<mnevans>
@jammcq, stdout is: 1.
15:58
@sbalneav, yes, ltsp-build-client --arch i386. I did it a second time this morning to confirm I didn't make that mistake the first time.
15:59
<sbalneav>
mnevans: --arch=i386, or --arch i386?
15:59
IIRC, it's the second. That mucks me up personally every time :)
15:59
<jammcq>
'=' shouldn't matter
16:00
if we're using proper posix Getopt for parsing the args
16:00
<mnevans>
@ sbalneav, copying and pasting from the command line: ltsp-build-client --arch i386
16:00
<sbalneav>
I think it doesn, AFAIK I don't think we ARE using the getopts, but I'd have to check.
16:01
<mnevans>
It looks like it did create the i386 libraries. ls -l /opt/ltsp/i386/boot/ is here: http://pastebin.com/1kSJRgbn
16:04
<sbalneav>
Hmmm, odd. Vagrant's our debian master, maybe keep an eye out for him.
16:04
vagrantc's his IRC nick.
16:05
<jammcq>
he's west-coast so prolly won't see him for another hour or so
16:05vagrantc has joined IRC (vagrantc!~vagrant@c-98-232-129-196.hsd1.or.comcast.net)
16:05vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
16:05
<jammcq>
heh
16:05
and then... he reconnects
16:06* vagrantc waves
16:06
<muppis>
vagrantc, you followed the logs?
16:06
<vagrantc>
muppis: nope
16:07
something exciting there?
16:07
<muppis>
8.04:40 < sbalneav> Hmmm, odd. Vagrant's our debian master, maybe keep an eye out for him.
16:07
18.04:53 < sbalneav> vagrantc's his IRC nick.
16:08* vagrantc checks logs
16:10
<mnevans>
@sbalneav, jammcq, thanks, I am checking into a configuration problem in dhcpd.conf. I have a mix of i386 and amd64 clients. I think the i386 client may not be getting the right root path. Trying specifying root path in each client stanza...
16:10
<vagrantc>
mnevans: ltsp-chroot --arch i386 dpkg --print-architecture
16:11
mnevans: check you logs for which NFS mount (or NBD image) it's using.
16:11
i *think* both should show up in /var/log/syslog
16:11Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
16:12
<mnevans>
@vagrantc, my once and future hero... --print-architecture says i386.
16:12
Should be using the default nfs mount, as with amd64 clients.
16:12
<vagrantc>
mnevans: do you actually need the 64-bit env? because your 64-bit thin clients could just run the 32-bit OS
16:12
<mnevans>
I have a car with 4 cylinders, why not just use two? :)
16:13
<vagrantc>
from a maintenance point of view, why use two cars when one will work? twice the maintenance overhead
16:13
<mnevans>
Actually I ride a bike most days... good point.
16:13
<vagrantc>
that said, you'll need to make sure DHCP points it to the correct rootpath on a per-client basis.
16:14
and a bike, dare i show my bias, is even better :)
16:14
<mnevans>
Don't get me started on bikes... love them, but this is an ltsp forum.
16:15
<vagrantc>
i'd set i386 as the default, and then on a per-client basis use 64-bit.
16:15
that way it'll work by default, but you can selectively set up 64-bit if you want.
16:15
or just use i386 all-around... wheezy does have support for multiple kernel images using ifcpu64
16:16
<mnevans>
I was using options root-path = "/opt/ltsp/amd64"; in the subnet stanza, but I guess I need to change that. Only one i386 client in typically use, the rest amd64, so maybe I'll just set that.
16:16
<vagrantc>
ah, yes, that's another way to do it.
16:16
<mnevans>
In the client stanza, should options root-path = "/opt/ltsp/i386"; simply do it?
16:16
<vagrantc>
yup
16:16
<mnevans>
And I have to comment out the subnet options root-path declaration?
16:17
<vagrantc>
i can't see your dhcpd.conf, so a little hard to say exactly what to do :)
16:17
<mnevans>
Sorry... pastebin?
16:18
<vagrantc>
if you want.
16:18
i usually use a global delcaration for most settings, and then only change the ones i need on a per-client basis
16:21alexqwesa_ has left IRC (alexqwesa_!~alex@109.172.12.47, Quit: Хана X'ам !!!)
16:23
<mnevans>
@vagrantc, balneav, jmmcq, That solved it. I needed: option root-path "/opt/ltsp/i386"; in my i386 client stanzas.
16:23
<vagrantc>
mnevans: you can also use "group" settings in dhcpd.conf ...
16:24
<jammcq>
there ya go, another satisfied customer :)
16:24
<vagrantc>
i.e. group lowly-i386 { root-path "/opt/ltsp/i386" ; client { hardware mac:add:dress } ; }
16:25
<mnevans>
@vagrantc, I had another debian ltsp question; I see gnome3 doesn't work in ltsp for me (Debian/Wheezy). Gnome3 does work in a direct install of debian wheezy . Is that an ltsp problem, or a gdm problem?
16:25
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686511
16:25
<markit>
hi, just reading the log, but I can't understand if the "=" in --arch i386 is mandatory or not. Googling around and checking my notes I see it used or missing
16:26
<mnevans>
Ah - the group settings - right. But I am doing client-by-client MAC address-based declarations of who's allowed on the client network already.
16:27
@markit, a question I can actually answer! Because it just came up and others answered it for me... I used ltsp-build-client --arch i386.
16:28
<markit>
mnevans: hi, first, in irc we don't prefix nic names with @, second thanks but I want to know if is mandatory or not
16:28
mnevans: looking at man pages online seems that the '=' is not used, but I've some notes with it
16:30alexqwesa_ has joined IRC (alexqwesa_!~alex@109.172.12.47)
16:30
<mnevans>
markit, re: first, I stand corrected. I'm relatively new to chat, that was just an attempt to reply directly to people helping me here.
16:31
<jammcq>
markit: the '=' shouldn't be necessary
16:31
<markit>
mnevans: ops, sorry, my answer looked (was) harsh, no intention, I'm just disturbed by children and other stuff
16:31
<jammcq>
ltsp-build-client is using 'getopt'
16:31
which understands long-options
16:31
<markit>
mnevans: apologises
16:31
<mnevans>
markit, no worries here!
16:31
<markit>
jammcq: I'm trying to have a look at the source
16:32
<vagrantc>
it definitely works without the =, and there's one way to find out if it would work with the = ...
16:32
<markit>
jammcq: btw, hi :) happy to see you around
16:32
jammcq: but I'm not familiar with getopt or this stuff
16:32
<jammcq>
:) thanks
16:32
<vagrantc>
ltsp-build-client is doing some wacky wrappering around getopt, so i'm not positive the --arch=i386 will work correctly, but it might.
16:32
<jammcq>
from the getopt manpage:
16:32alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
16:32
<jammcq>
A long option normally begins with `--' followed by the long option name. If
16:32
the option has a required argument, it may be written directly after the long
16:32
option name, separated by `=', or as the next argument (ie. separated by white‐
16:32
space on the command line).
16:33
so --arch=i386 and --arch i386
16:33
have the same meaning
16:33
<vagrantc>
yes, but we're not using getopt in a vacuum.
16:33
<markit>
I see, thanks a lot
16:33
<knipwim>
hey alkisg, i thought you would be on a slope somewhere now
16:33
<jammcq>
but it is being used, right?
16:33
<vagrantc>
it'll probably work.
16:33
<markit>
yes, in the code is there
16:33
<alkisg>
Hi guys... just got back :)
16:33
<vagrantc>
jammcq: yes, but...
16:33
<markit>
# Parse the commandline options
16:33
<jammcq>
but... if it's not, then I'd consider that a bug
16:33
<markit>
if ! TEMP=`getopt -o '' --long $PARAMS -n "$0" -- "$@"`; then
16:34
brb, will read the log later
16:34
<knipwim>
alkisg: you live near mountains with snow?
16:34
<vagrantc>
jammcq: but it *does* work after testing just moments ago.
16:34
so, --arch i386 or --arch=i386 are equivalent.
16:34
<jammcq>
yes, mnevens proved it works with whitespace
16:34
<alkisg>
knipwim: There are 2 places for ski half an hour away, but we prefer going to another bigger one, 2 hours away
16:34* vagrantc always used it with whitespace
16:35
<knipwim>
nice one
16:35
<jammcq>
I usually do whitespace too
16:35
just out of habit
16:35
<mnevans>
I made a positive contribution to the chat.. first time... I'm beaming with pride!
16:35
<jammcq>
mnevans: I know the feeling. first time for me here in quite a while
16:36* vagrantc is happy to see jammcq and sbalneav around again
16:36
<mnevans>
jammcq, no first time for me: ever!
16:36
<jammcq>
well... glad the team was able to help you out
16:36
<mnevans>
vagrantc, I found a small bug when installing debian/wheezy/ltsp fresh to server. Not sure if it is worth a bug report.
16:37
<jammcq>
if you don't report it, it may never get fixed
16:39
<mnevans>
The standard installation (ltsp-server-standalone) , gives the line in /etc/default/isc-dhcp-server, DHCP_CONF=/etc/dhcp/dhcpd.conf . It should be /etc/dhcp3/dhcpd.conf . Note the "3".
16:39
That took me a good hour to find and fix... would be nice to save others the trouble. Not really a bug, is it?
16:40
<jammcq>
not sure that's LTSP's problem
16:40* jammcq leaves that for others to comment on
16:40
<mnevans>
No, maybe it is part of isc-dhcp-server that installed that file to /etc/default?
16:40
<alkisg>
`dpkg -S /etc/default/isc-dhcp-server` would tell you that
16:41
<mnevans>
alkisg, I get: dpkg-query: no path found matching pattern /etc/default/isc-dhcp-server
16:46
<vagrantc>
mnevans: /etc/dhcp3/dhcpd.conf is a legacy location not used since lenny
16:46
mnevans: but what to you mean by "standard installation" ?? i don't know what you're referring to.
16:47
<mnevans>
vagrantc, interesting, why would it show up with a wheezy ltsp-server-standalone install? Because I used the default and it is using NFS and not NBD image?
16:47
<vagrantc>
mnevans: i don't understand what you're saying is actually happening though
16:47
<mnevans>
(I should mention: fresh install. I never met lenny.)
16:48
<vagrantc>
mnevans: what is referring to DHCP_CONFIG=/etc/dhcp3/dhcpd.conf ?
16:48adrianorg_ has joined IRC (adrianorg_!~adrianorg@177.156.226.130)
16:48
<mnevans>
Oops, I am probably not making sense then, sorry...
17:02Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 252 seconds)
17:03
<mnevans>
What I did to install ltsp to a fresh debian/wheezy (testing) alpha 7 install: apt-get install ltsp-server-standalone. Then added include "/etc/ltsp/dhcpd.conf"; to bottom of /etc/dhcp3/dhcpd.conf (installed by ltsp-server-standalone?).
17:05
Then modified /etc/default/isc-dhcp-server to reflect NIC setup on server. Then service isc-dhcp-server restart. Then /etc/init.d/nfs-kernel-server start. Then build the clients and configure dhcpd.conf.
17:05dobber has left IRC (dobber!~dobber@213.169.45.222, Remote host closed the connection)
17:06
<vagrantc>
mnevans: what referenced "/etc/dhcp3/dhcpd.conf" ?
17:07dhani has joined IRC (dhani!b4f8af41@gateway/web/freenode/ip.180.248.175.65)
17:08
<mnevans>
It was /etc/default/isc-dhcp-server, the line there was: DHCPD_CONF=/etc/dhcp/dhcpd.conf .
17:09
<vagrantc>
and that's the correct thing...
17:10
mnevans: was there some website that referenced "/etc/dhcp3/dhcpd.conf"? was it an error log somewhere? was it messages from little faeries? where did this come from?
17:12
<mnevans>
vagrantc, to start the isc-dhcp-server, I think it looks to /etc/default/isc-dhcp-server and within that file (delivered by the apt faeries?) it points to /etc/dhcp/dhcpd.conf. So when I tried to just start the service, it failed.
17:12
Until I changed the line in /etc/default/isc-dhcp-server accordingly.
17:12
So where'd it come from? Install of something related to ltsp-server-standalone, I am guessing.
17:14
<vagrantc>
i still don't understand...
17:14
<mnevans>
Let's see: according to http://packages.debian.org/wheezy/amd64/isc-dhcp-server/filelist isc-dhcp-server installed /etc/dhcp/dhcpd.conf ... but I got /etc/dhcp3/dhcpd.conf.
17:15
<vagrantc>
mnevans: so you're saying you have /etc/dhcp3/dhcpd.conf by default in a fresh install?
17:16
<mnevans>
Yes, seems so. I am now looking at http://packages.debian.org/wheezy/ltsp-server-standalone and it says dhcp3-server is a virtual package provided by isc-dhcp-server.
17:17
Let me check my apt logs...?
17:18Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
17:19
<mnevans>
more history.1.log (from install date) | grep dhcp just shows install of isc-dhcp-server. Trying to recall how to query apt for which files were installed...
17:21
output of apt-cache showpkg isc-dhcp-server is here: http://pastebin.com/FxHVhG0n
17:21
Provides: 4.2.2.dfsg.1-5+deb70u2 - dhcp3-server
17:24
But dpkg -L isc-dhcp-server gives this: http://pastebin.com/9GLLJH5t
17:24
which lists /etc/dhcp/dhcpd.conf . So I am also confused as to why I got /etc/dhcp3/dhcpd.conf.
17:27
Here's a clue: I have both /etc/dhcp/ and /etc/dhcp3/ directories. I followed the directions on the Debian LTSP/Howto (dating to lenny?) and modified /etc/dhcp3/dhcpd.conf for the include pointing to /etc/ltsp/dhcpd.conf.
17:28
I still don't know where /etc/dhcp3 came from. Now I can see why vagrantc was confused by my question.
17:31alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
17:33
<mnevans>
Correction: I had to create /etc/dhcp3/dhcpd.conf with the sole line: include "/etc/ltsp/dhcpd.conf"; in /etc/dhcp/dhcpd.conf is quite a nice list of examples to which I can append the include.
17:33
Maybe as punishment I should help revise the ltsp/howto for Wheezy?
17:33
:)
17:34
<vagrantc>
mnevans: heh.
17:34
wiki.debian.org/LTSP* pages need some love, that's for sure.
17:34
<mnevans>
Right. Who would want my help? (with friends like these, who needs enemies?) ;-)
17:35
<vagrantc>
probably should just create an LTSP/HowtoWheezy and start from scratch, really.
17:37
mnevans: so it's https://wiki.debian.org/LTSP/Howto that pointed you to /etc/dhcp3/dhcpd.conf
17:37telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
17:38
<mnevans>
Perhaps. I'm not much good at wiki but I do have the beginnings of an html page of notes; maybe it would be easy for someone to check and convert/post into said wiki?
17:38
<vagrantc>
at this point, i'd almost recommend using dnsmasq and "ltsp-config dnsmasq" instead of isc-dchp-server
17:38telex has joined IRC (telex!~telex@freeshell.de)
17:38
<vagrantc>
oh no, i think i forgot to include the /etc/exports.d/ltsp.exports ... *sigh*
17:39
i wanted that in the package by default, so it wouldn't require configuration. *ugh*
17:39
there are a lot of really confusing comments on that page... ugh.
17:43Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 255 seconds)
17:46LTSP_ has joined IRC (LTSP_!4d366b19@gateway/web/freenode/ip.77.54.107.25)
17:46
<LTSP_>
Hello there
17:46
Can anyone help me with LTSP and startx
17:46
??
17:47
<mnevans>
vagrantc, I recently made the switch from ubuntu to debian b/c I like the stability and usability better... I would be happy to help in any way I can, to clarify the debian ltsp install howto. Would follow your lead here
17:48
especially if it involved changes to the way the packages installed and configured themselves.
17:48
<LTSP_>
mevans have you tested the startx and rdesktop on it?
17:49
<mnevans>
LTSP_, how are you using startx?
17:49
<LTSP_>
yes! I am trying
17:49
...
17:50
in the lts.conf simply placed startx
17:51
i have created a lts.conf file in /var/lib/tftpboot/ltsp/i386
17:51
and everything seems to be working
17:51
ldm
17:51
and telnet
17:51
but startx and rdesktop are stuck!
17:52
<mnevans>
LTSP_, what distribution?
17:52
<LTSP_>
5
17:52
<mnevans>
Ubuntu?
17:52
<LTSP_>
nope
17:52
Debian
17:52
Debian 6
17:53dhani has left IRC (dhani!b4f8af41@gateway/web/freenode/ip.180.248.175.65, Ping timeout: 245 seconds)
17:53
<mnevans>
I don't have experience with Debian 6; am working in Wheezy/testing. Things might be different.
17:53
<LTSP_>
i have already tested lubuntu and i had the same errors so i thought to give Debian a try
17:53
but is your rdesktop working?
17:54
if i pass to a different console and start startx it works
17:54
<vagrantc>
LTSP_: startx/xdmcp are pretty much deeprecated.
17:54
<mnevans>
My basic lts.conf is here: /opt/ltsp/amd64/etc/lts.conf (not in /var/lib/tftpboot...)
17:54
And telnet also I would think?
17:54
and includes only the lines: LTSP_CONFIG=True
17:54MonkWitDaFunk has left IRC (MonkWitDaFunk!~yaaic@199-7-158-72.eng.wind.ca, Ping timeout: 246 seconds)
17:54
<LTSP_>
so what should i use to directly connect to a remote windows desktop
17:54
<mnevans>
SOUND=True
17:54
LOCALDEV=TRUE
17:55
that's all.
17:55
<vagrantc>
LTSP_: if you're using squeeze with NFS, you need to edit /opt/ltsp/i386/etc/lts.conf
17:55
<mnevans>
How are you using rdesktop? I also use this, but to connect from the ltsp server to windows boxes on a lan.
17:55
<vagrantc>
LTSP_: if you're using NBD, then you'd use /var/lib/tftpboot/ltsp/i386/lts.conf
17:55
<LTSP_>
right
17:55
!
17:55
Thats what i did
17:56
and if i change anything to test it works
17:56
<vagrantc>
LTSP_: which one?
17:56
<LTSP_>
using NBD
17:56
Im only trying to connect to a remote windows desktop but i still cant see the login windows
17:56
<vagrantc>
LTSP_: in order to use xdmcp (i.e. startx), you need a server that's running a display manager that supports the XDMCP protocol and is configured to do so.
17:56
<LTSP_>
only a black screen
17:57
<vagrantc>
i don't know rdesktop very well
17:57
<LTSP_>
but lets say i use SCREEN1 ldm SCREEN2 rdesktop
17:57
<mnevans>
LTSP_, what is your rdesktop command? I guess this is outside the chat scope...
17:58
<LTSP_>
if i connect to the tty5 console
17:58
and login with root and password
17:58
<vagrantc>
LTSP_: you can't use 01 through 06 on debian squeeze
17:58
<LTSP_>
after that i do startx and rdesktop and everything works
17:58
<vagrantc>
LTSP_: without disabling entries in /opt/ltsp/i386/etc/inittab
17:59
<LTSP_>
ok!
17:59
im going to try to change it
17:59
<vagrantc>
LTSP_: i'd recommend just using 07-12
17:59
then you don't have to rebuild the image.
17:59
<LTSP_>
correct!
17:59Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
18:02
<LTSP_>
still no good
18:03
i have changed it to screen 8 and 9
18:04
<vagrantc>
LTSP_: 08 and 09 ?
18:04
LTSP_: i.e. SCREEN_08 and SCREEN_09
18:04
<LTSP_>
right!
18:05
<vagrantc>
with rdesktop?
18:05
<LTSP_>
yes
18:05
i can only connect at screen1
18:05
to my LTSP server
18:05
<vagrantc>
what do you mean at screen1 ?
18:05
<LTSP_>
ldm
18:06
<vagrantc>
ldm usually runs on SCREEN_07 by default.
18:06
<LTSP_>
i can the the login screen and use it normally
18:06
<vagrantc>
there are usually gettys on 01-06
18:06
LTSP_: the console login screen?
18:06
<LTSP_>
no
18:06
the graph login screen
18:06
<vagrantc>
you sure it's on SCREEN_01 ?
18:07
<LTSP_>
yes
18:07
i press ctrl+alt+f1
18:07
<vagrantc>
LTSP_: comment out all the SCREEN entries in your lts.conf, and then set SCREEN_07=shell
18:07
then boot a thin client, what do you get?
18:08
<LTSP_>
one moment
18:11
its booting...
18:12
<vagrantc>
it should bring you to a root shell without login
18:12
<LTSP_>
righ
18:12
right thats what i have
18:13
<vagrantc>
ok.
18:14
LTSP_: so, let's recap what your issues are:
18:14
<LTSP_>
now i what to connect direclty to a windows remote desktop connection
18:14
after searching a while everyone talks about rdesktop and xfreerdp
18:14
<vagrantc>
1) ldm doesn't log into your LTSP server? 2) you want to connect to a windows server? 3) you want to connect to your linux server using XDMCP?
18:15
<LTSP_>
and if i place a screen with "SCREEN_08 = rdesktop -f 192.168.1.1" i should have a full screen remote desktop connection
18:15
<vagrantc>
xfreerdp is a fork of rdesktop
18:15
<LTSP_>
ok
18:16
on the shell if i login and after that run startx and rdesktop everything works
18:17
<vagrantc>
192.168.1.1 is the IP of your windows server?
18:17
<LTSP_>
yes
18:17
as an example
18:17
but now i would like to do that directly without the knoledge of the user
18:17
*knowledge
18:18
is that possible?
18:18* vagrantc looks up the older version of the rdesktop script
18:19
<vagrantc>
shoould be, just might have some syntax issues
18:19
<LTSP_>
some say it might be the x that is not starting on boot time
18:20
<vagrantc>
LTSP_: does SCREEN_07 give an ldm login screen?
18:20
<LTSP_>
yes
18:21
<vagrantc>
LTSP_: try SCREEN_08=rdesktop 192.168.1.1
18:21
<markit>
I'm in fat chroot with -c, how is that that apt-get update works fine in the host, but in chroot I've a pari of "NO_PUBKEY 83FBA1751378B444" and "NO_PUBKEY 3C72607B03AFA832"?
18:22
<LTSP_>
already have
18:22
nothing...
18:22
<vagrantc>
LTSP_: you told me you did "rdesktop -f 192.168.1.1"
18:22
LTSP_: i'm suggesting without the "-f"
18:23
<LTSP_>
ahhh ok
18:23
sorry
18:23
does the -f affects?
18:23
<vagrantc>
fullscreen mode
18:23
<LTSP_>
is just for full screen
18:24
<vagrantc>
forget it. i don't know rdesktop, no sense trying.
18:25
LTSP_: alternately, i'd reccomend using RDP_SERVER=192.168.1.1 and RDP_OPTIONS=-f and SCREEN_08=rdesktop
18:25ltspuser_72 has joined IRC (ltspuser_72!69ecb525@gateway/web/freenode/ip.105.236.181.37)
18:25
<LTSP_>
right i already have tried everything...
18:25
but still no good
18:26
i have to give up and forget ltsp
18:26
<vagrantc>
maybe.
18:26
you could also try a newer version of LTSP
18:26
what's in squeeze is getting pretty old
18:26
xfreerdp might work better.
18:26
<LTSP_>
what should i use?
18:27
and what linux distro?
18:27
<vagrantc>
experiment, or give up, your call.
18:27ltspuser_72 has left IRC (ltspuser_72!69ecb525@gateway/web/freenode/ip.105.236.181.37, Client Quit)
18:27
<LTSP_>
ubuntu?
18:27
<mnevans>
LTSP_, sorry, checking back. What I do is login to a graphical desktop environment on the ltsp server, then I have an alias to connect to the windows machine.
18:28
<LTSP_>
how?
18:29
<mnevans>
e.g. in /etc/bash.bashrc, I have alias win1='rdesktop -u [username] -g [screenresolution] [lan_ip]:[port]'
18:29
(I have set up in each windows machine to use that port for an rdesktop connection.)
18:29
The user types 'win1' in a terminal window to start the rdesktop connection.
18:31
<vagrantc>
wow. we really need to fix the rdesktop screen script if people are resorting to such hacks :(
18:32
although the main ltsp developer who used it... hasn't been around much :(
18:32
<LTSP_>
:D
18:32
I have seen many people with the same problem
18:33
<vagrantc>
LTSP_: i can try it with LTSP wheezy using xrdp, but i have no windows environment to try with.
18:33
<mnevans>
I didn't even know there was an rdesktop screen script! But what I described works. A lot of times we are logging into the winboxes remotely, not from a client.
18:35
<LTSP_>
ok thanks i am going to lose a little more time with it...
18:35
Thank you for your help!
18:40
<vagrantc>
wish i could be more helpful
18:42
<mnevans>
vagrantc, IMHO, you are the best! Along with everyone else on this channel. My thanks as well to all of you. I have a great working environment thanks to LTSP.
18:43mnevans has left IRC (mnevans!8008b09d@gateway/web/freenode/ip.128.8.176.157, Quit: Page closed)
18:45
<markit>
vagrantc: btw, isn't rdesktop obsolete and freerdp or somethign like that much better?
18:48LTSP_ has left IRC (LTSP_!4d366b19@gateway/web/freenode/ip.77.54.107.25, Quit: Page closed)
18:53gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
19:06
<vagrantc>
markit: xfreerdp is a fork of rdesktop that is actually maintained, yes.
19:06
don't know if there's anything rdesktop can do that xfreerdp can't yet.
19:15
<markit>
vagrantc: support to latest rdp protocol, I think
19:16
<vagrantc>
markit: that's the other way around, no?
19:16Parker955_Away is now known as Parker955
19:16
<markit>
vagrantc: let's start from the beginning. He wants rdesktop to connect to M$crapOS
19:17
rdesktop is outdated as far as I know, and I've seen there is a new project, http://www.freerdp.com/
19:17
that it's much better and manteined
19:17
why you mentioned xfreerdp instead?
19:18* vagrantc forgets if squeeze's LTSP supports xfreerdp
19:19
<markit>
food time, will be back later, see you
19:20
<vagrantc>
yeah, xfreerdp support wasn't added till almost a year after the version in squeeze
19:20
wheezy should hopefully use xfreerdp by default
19:22
<||cw>
rdesktop isn't so much outdated as it just a limited feature client
19:28risca has joined IRC (risca!~risca@h240n6-n-a31.ias.bredband.telia.com)
19:33Parker955 is now known as Parker955_Away
20:18Parker955_Away is now known as Parker955
20:31alexqwesa__ has joined IRC (alexqwesa__!~alex@109.172.12.47)
20:35adrianorg_ has left IRC (adrianorg_!~adrianorg@177.156.226.130, Read error: Operation timed out)
20:35alexqwesa_ has left IRC (alexqwesa_!~alex@109.172.12.47, Ping timeout: 276 seconds)
20:36ltspuser_77 has joined IRC (ltspuser_77!5fed7cae@gateway/web/freenode/ip.95.237.124.174)
20:39ltspuser_77 has left IRC (ltspuser_77!5fed7cae@gateway/web/freenode/ip.95.237.124.174)
20:41alexqwesa__ has left IRC (alexqwesa__!~alex@109.172.12.47, Read error: Connection reset by peer)
20:41alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47)
20:51Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
21:21risca has left IRC (risca!~risca@h240n6-n-a31.ias.bredband.telia.com, Quit: Lämnar)
21:39adrianorg_ has joined IRC (adrianorg_!~adrianorg@177.156.226.130)
21:40mgariepy has left IRC (mgariepy!mgariepy@ubuntu/member/mgariepy, Remote host closed the connection)
21:58gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
22:06Gremble has joined IRC (Gremble!~Ben@cpc29-aztw23-2-0-cust144.18-1.cable.virginmedia.com)
22:28vmlintu has left IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi, Ping timeout: 276 seconds)
22:41alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, Read error: Connection reset by peer)
22:41alexqwesa_ has joined IRC (alexqwesa_!~alex@109.172.12.47)
22:56markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, )
22:57Gremble has left IRC (Gremble!~Ben@cpc29-aztw23-2-0-cust144.18-1.cable.virginmedia.com, Quit: I Leave)
23:32Parker955 is now known as Parker955_Away
23:39andygraybeal_ has joined IRC (andygraybeal_!~andy@h239.203.130.174.dynamic.ip.windstream.net)
23:41Parker955_Away is now known as Parker955
23:43Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
23:52komunista has left IRC (komunista!~slavko@adsl-195-168-234-074.dynamic.nextra.sk, Quit: Leaving.)