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


Channel log from 8 April 2010   (all times are UTC)

00:19alkisg has joined #ltsp
01:59vagrantc has quit IRC
02:07Brend has joined #ltsp
02:07
<Brend>
alkisg: Ping!
02:52Selveste1 has quit IRC
03:29try2free has joined #ltsp
03:31daya has quit IRC
03:51daya has joined #ltsp
03:55nubae_ has joined #ltsp
03:56nubae has quit IRC
03:59BbT0n has joined #ltsp
03:59
<BbT0n>
hi all
04:00
i have a problem with LTSP V5 in debian 5.0 ! It work with PXe .... my TTY is chroot, but when i want connect with graphical interface, is not chrooted .... have you got an idea ?
04:00
<Appiah>
chrooted X ?
04:01
it's not supposed to be chrooted , you are working on the server
04:01nubae has joined #ltsp
04:02nubae_ has quit IRC
04:03
<BbT0n>
Appiah, ok, i run LTSP, but i want chrooted my customer in /opt/I386/..... why it run with TTY1 and not with my Graphical Interface ? I must share my graphic environement with the server ?
04:04
<Appiah>
Never done anything like that
04:04
sorry
04:04
<BbT0n>
Appiah, are you shure ? It's not secure ?
04:05
<Appiah>
LTSP has no chrooted X , not default , no ltsp tool to do that. Maybe you can find someone who has done that in here
04:05
think some people have discussed different solutions for this in the mailing list
04:06
<alkisg>
BbT0n: you need to have a desktop environment installed on the server, if that's what you're asking.
04:06
The clients use the desktop environment on the server, so they can't work if the server doesn't have a DE.
04:08
<BbT0n>
No my DE work, i can connect it ! but is not chroot
04:08
Appiah, ok so it's impossible ......
04:09
<Appiah>
BbT0n: uhmm whats impossible?
04:10
Someone was talking about Ltsp+lxc
04:11
<BbT0n>
Appiah, my ltsp work but TTY7 is not chroot, i share my home with server, but in command line i'm chrooted ....
04:11
lxc ???
04:11
<Appiah>
yes , you are supposed to work on the server thats how LTSP works
04:12
you can edit lts.conf to make TTY6 local cmd line
04:12
or tty# maybe
04:12
http://lxc.sourceforge.net/
04:12
<BbT0n>
Appiah, ok i go see it
04:13
<Appiah>
but you will have to do some research , like I said, I never done anything like that
04:13
and so far I have yet to talk to someone using such solution
04:16try2free has left #ltsp
04:32daya has quit IRC
04:32Selveste1 has joined #ltsp
04:35
<BbT0n>
Appiah, why would i use lxc, i cant chroot my X for ltsp ? Because the last problem for me is chroot desktop in /opt/..... for my light customer. I present lstp in my classrom ;) thx for your help
04:36
<Appiah>
well I dunno thats maybe one solutions
04:36
-s
04:36
like I said above, I have not done this nor do I know anyone who want this
04:36Egyptian[Home] has quit IRC
04:36
<Appiah>
you can try to ask on the mailing list and here
04:36
if you find something please mail it out
04:37
maybe locking down the users is enough (check out sabayon)
04:41
<alkisg>
BbT0n: ldm uses ssh to connect to the server, so you want it to connect to a chroot instead?
04:42
Maybe you can use ChrootDirectory in sshd_config for that.
04:46
<BbT0n>
alkisg, nice it's good idea i can't test it now, have you test it ?
04:46
<alkisg>
No
04:46
It's usually easier to have a separate ltsp server
04:46
<BbT0n>
because XDMCP is in SSH ?
04:46
<alkisg>
LTSP doesn't use XDMCP
04:46
<Appiah>
:D
04:47
<BbT0n>
alkisg, easier, not for me now, my command line environement work chrooted
04:47
<alkisg>
It uses ssh for authentication, and then it either uses ssh -X or some xauth magic...
04:47
BbT0n: how exactly did you chroot it?
04:47
<Appiah>
its already chrooted...
04:47
when the client pxe boots
04:48
<alkisg>
BbT0n: can you describe in more words what have you already done and what you want to do? Maybe there's a misunderstanding that could be solved more easily than having to invent a new method
04:48Egyptian[Home] has joined #ltsp
04:48
<BbT0n>
alkisg, ok my ltsp with PXe work, but they are just my command line TTY1 witch chrooted in /opt/I386...., but when my customer connect in X in TTY7, it's not chrooted i share my environement with server
04:49
<alkisg>
BbT0n: yes, that's by design
04:49
So you want fat clients? or you still want to work on the server, but on a new chroot?
04:51
If you want to work on a new chroot, you'd have to create one, because the one LTSP creates doesn't have all the necessary programs for a user session...
04:51
If you want fat clients (== a big chroot with everything on it), then you'd need a very recent ltsp version
04:51
(ubuntu and maybe you could change it a little to work on debian as well)
04:54
<BbT0n>
alkisg, ok nice for give your time for help a newbie than me :p
04:55
alkisg, i run my LTSP5 in DEbian 5.0, i want chroot my customer in /opt/.... for all client with command line and X, but X don't work :) Maybe if i use ubuntu it's more easier
04:56
alkisg, i want exploid ltsp because it's good idea for recycle a old computer
04:59
<alkisg>
BbT0n: why do you want it chrooted?
04:59
For security?
05:00
<BbT0n>
alkisg, because i don't want my customers share the fillesystem with server ;)
05:00
alkisg, yes for security
05:00
<alkisg>
BbT0n: erm, ok. You could create a new chroot then for them
05:01
Make a new partition on the server
05:01
Install debian on it, so that you have 2 debian partitions
05:01
Then try the chrootdirectory on sshd_config, it might wark
05:01
*work
05:02
To be clear: you need 2 chroots for what you want to do: one for LTSP, and one for the user session.
05:02
I don't think anyone has tested this before.
05:02
<BbT0n>
alkisg, thx ! I I am already looking to chrootdirectory ....
05:03
alkisg, I'm the first ;) i test it this night
05:03
alkisg, i will be back in this channel !!
05:04
alkisg, i say it the next time
05:07
alkisg, enjoy your food !!! see you ;)
05:08BbT0n has quit IRC
05:14Selveste1 has quit IRC
05:31bobby_C has joined #ltsp
05:39alkisg has quit IRC
05:53Egyptian[Home] has quit IRC
05:55Selveste1 has joined #ltsp
05:57daya has joined #ltsp
06:06Egyptian[Home] has joined #ltsp
06:14hersonls has joined #ltsp
06:35daya has quit IRC
06:36Selveste1 has quit IRC
06:36pmatulis has joined #ltsp
06:39Selveste1 has joined #ltsp
06:41C_tek has joined #ltsp
06:44Selveste1_ has joined #ltsp
06:44Selveste1 has quit IRC
07:00Selveste1_ has quit IRC
07:01Selveste1_ has joined #ltsp
07:07alkisg has joined #ltsp
07:14nubae_ has joined #ltsp
07:14nubae has quit IRC
07:15nubae_ is now known as Nubae
07:15Nubae has joined #ltsp
07:19artista_frustrad has quit IRC
07:26ogra has quit IRC
07:27ogra has joined #ltsp
07:30scottmaccal has joined #ltsp
07:32artista_frustrad has joined #ltsp
07:34mikkel has joined #ltsp
07:39C_tek has quit IRC
07:41C_tek has joined #ltsp
07:55C_tek has left #ltsp
08:12japerry has quit IRC
08:18Selveste1_ has quit IRC
08:19Selveste1_ has joined #ltsp
08:32bladernr_ has joined #ltsp
08:59GodFather_ has joined #ltsp
09:01GodFather_ is now known as GodFather
09:02Gadi has joined #ltsp
09:08GodFather has quit IRC
09:13starkeeper has joined #ltsp
09:13
<starkeeper>
hi, I have a probleme with the install of ltsp-cluster
09:13
can anyone help me ?
09:15
<Appiah>
describing the problem would be a great start
09:16
<starkeeper>
When i attempt to login on a client I have the message "No response from server, reboot" and in the log of lbserver I have code 400, message Bad request syntax('getkey')
09:19
<vbundi>
hmm try running ltsp-update-sshkeys
09:20
<starkeeper>
on the ltsp root or on the ltsp app ?
09:20
how do they communicate ?
09:21
<vbundi>
on the ltsp server
09:21
do that, update your image and reboot
09:29
<starkeeper>
It doesn't make any difference
09:30
<vbundi>
ah I didn't notice that you were doing ltsp-cluster
09:31
sorry can't off too much more assistance.. :(
09:31
<starkeeper>
ok, i think that the probleme is in the communication between the ltsproot and the ltspapp
09:33
thank you for your help, i go to post in the list
09:34bladernr_ has quit IRC
09:35starkeeper has quit IRC
09:48bladernr_ has joined #ltsp
09:59
<sbalneav>
alkisg: pong
10:00
<alkisg>
Hi sbalneav
10:00
About the socket question yesterday? I was looking to dup() some descriptor and then exec() /bin/sh, but it turns out that `nc` already had implemented this :)
10:01
So after implementing it, I realized I could use nc -e /bin/sh instead :)
10:02
<sbalneav>
Yeah, nc's a great little util
10:11vaix has left #ltsp
10:21Selveste1__ has joined #ltsp
10:22Selveste1_ has quit IRC
10:29ogra_cmpc has quit IRC
10:29staffencasa has joined #ltsp
10:30ogra_cmpc has joined #ltsp
10:30Selveste1__ has quit IRC
10:30Selveste1__ has joined #ltsp
10:30
<vbundi>
!lts.conf
10:30
<ltspbot`>
vbundi: "lts.conf" :: http://manpages.ubuntu.com/lts.conf
10:46
<vbundi>
is there a way to connect to my terminal server like the old days with tsclient XDMCP? or am I stuck using a virtual machine type terminal
10:48Faithful has quit IRC
10:48
<Gadi>
SCREEN_07=xdmcp
10:49
<vbundi>
I mean, I want to connect, for example, from my laptop to the server from an application within the OS rather than PXE boot
10:50
<Gadi>
freenx?
10:51
<vbundi>
ahh ok
10:52
<Gadi>
did gdm drop xdmcp support?
10:53
<vbundi>
I can't connect to my server using the XDMCP option with tsclient
10:53
but not sure if that means they 'dropped' it
10:54
<Gadi>
vbundi: oh - well then, you may simply need to enable it
10:54
and then you can do things the goold old wway
10:54
:)
10:54
<vbundi>
Gadi: thats kinda what I am wondering here.. it gives me some error messages rather than just ignoring it
10:55
<Gadi>
does System->Administration->Login Window give any options for remote?
10:57ogra_cmpc has quit IRC
10:59ogra_cmpc has joined #ltsp
11:02Faithful has joined #ltsp
11:02
<vbundi>
hmm it won't let me unlock it
11:03
doesn't look like the feature is there anyway
11:04
but for some reason my server won't let me open something that requires superuser privileges, the gksudo window pops up, after entering my password nothing happens
11:07Selveste1__ has quit IRC
11:07
<sbalneav>
Gadi: From the configuration, yes. You have to add it via the config files now.
11:07
there's no graphical login config for xdmcp anymore.
11:15Brend has quit IRC
11:16Brend has joined #ltsp
11:23japerry has joined #ltsp
11:23randomuser has quit IRC
11:37mikeshultz has joined #ltsp
11:46vagrantc has joined #ltsp
11:52rjune has quit IRC
12:01CAN-o-SPAM has joined #ltsp
12:13CAN-o-SPAM has quit IRC
12:40
<bladernr_>
Hey all... I was here last night going nuts trying to get LTSP to work in a VM setting...
12:41
Turns out, my problem was that my LTSP Server VM only had one NIC which the Ubuntu installer did not like when configuring dhcpd for LTSP
12:41
<alkisg>
You can just change dhcpd.conf if you have 1 nic
12:41
<vbundi>
bladernr_: you just have to change your dhcpd.conf
12:41
<bladernr_>
SO, I added a second NIC to the VM and install went well... however, afterwards, I tried booting a thin client and while it DID get an IP address, it did not PXE boot.
12:42
alkisg, vbundi: that's easy, but I never did find exactly WHAT I needed to change in dhcpd.conf to indicate a single nic, besides, I shouldn't have to do that anyway, the installer should be smart enough to do the config for me (IMHO)
12:42johnny has left #ltsp
12:43
<bladernr_>
in any case, I added the second NIC and it was happy after that without any manual intervention afterwards... but now, as I just mentioned, the thinclient doesn't find an image once it tries to boot.
12:43johnny has joined #ltsp
12:43
<alkisg>
bladernr_: the installer can't assign a static IP for your NIC when you only have 1 NIC, because it's on a "public" network, not a private one
12:43
<vbundi>
bladernr_: so, fresh install on the VM with 2 nics, or you added the nic after the install
12:44
<alkisg>
So it can't configure /etc/network/interfaces and dhcpd.conf for you.
12:44
<bladernr_>
ahhh... but if said single NIC is already configured via static IP? and if it's using it's own internal network, why can't it just alias the internal IP to the nic? (just learning here, not trying to sound snarky)
12:45Selveste1__ has joined #ltsp
12:45
<bladernr_>
Oh, but that was just for an update anyway, I now have learned :) that the proper way is to have two NICs from the get go, to avoid headaches and such
12:46
<vbundi>
bladernr_: if proper == default then I suppose ;)
12:46
<alkisg>
bladernr_: anyway what's the last message you see in the client?
12:46
Loading pxelinux? loading vmlinuz?
12:47
<bladernr_>
vbundi: well, proper == default || least painful
12:47
<vbundi>
bladernr_: your VM LTSP server is bridged ethernet to your ethX on your machine right?
12:48
<bladernr_>
alkisg: http://pastebin.ubuntu.com/411153/ that's the VM Log for the thinclient machine
12:49
<vbundi>
bladernr_: I'm guessing that your VM LAN isn't quite right for what you're trying to do
12:50
<bladernr_>
vbundi: kinda... default VirtualBox setup, so eth0 on the Server VM is plugged into the 10.0.2 network inside VBox (NAT). eth1 is on an internal only 192.168.0 network and serving the dhcp for the LTSP services
12:50
<vbundi>
bladernr_: can you explain how your VM NICs are configured on the LTSP server and on your Virtual thin client?
12:50
<bladernr_>
thin client is also configured to use internal only network, no NAT, or Bridge
12:51
right now, it's a PXE issue I think... MAYBE...
12:51highvoltage has quit IRC
12:51
<vbundi>
bladernr_: so you have your thin client configured to talk to on the 'internal only' network?
12:51highvoltage has joined #ltsp
12:52
<alkisg>
bladernr_: that's a vmware client? does it support boot from lan? Because it says not supported yet...
12:52
<bladernr_>
its not vmware, it's virtualbox
12:52
and it does PXE
12:53
http://pastebin.ubuntu.com/411154/ thats the error the client is showing during PXE
12:53
<vbundi>
bladernr_: I know with VMware, it serves ip addresss to the internal lan
12:53
<alkisg>
OK, that's more like it
12:53
<vbundi>
bladernr_: ah
12:53
<alkisg>
bladernr_: which version is that again?
12:53
<bladernr_>
version of what?
12:53
<alkisg>
9.10?
12:53
Ubuntu
12:53
<bladernr_>
10.04
12:54
latest beta2 updates
12:54
errr... I meant latest beta2 ISO spin
12:54
<alkisg>
grep DIRECTORY /etc/default/tftpd-hpa
12:55
<bladernr_>
alkisg: /var/lib/tftpboot
12:55
<alkisg>
ok, then: grep filename /etc/ltsp/dhcpd.conf
12:55
<bladernr_>
should be somewhere else I bet
12:55
<vbundi>
no thats right
12:56
<bladernr_>
-- /ltsp/i386/pxelinux.0 and /ltsp/i386/nbi.img
12:56
<alkisg>
ok, then: ls /var/lib/tftpboot/ltsp/i386/pxelinux.0
12:56
<vbundi>
bladernr_: are you running 64 bit LTSP?
12:56
<alkisg>
(that's an i386 server with i386 clients?)
12:56vbundi has quit IRC
12:57
<bladernr_>
it's supposed to be... it's 64bit 10.04
12:57
and the client is configured as a 64bit system
12:57
<alkisg>
bladernr_: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/203954
12:57
You need to configure dhcpd.conf manually for 64 bit systems
12:58vbundi has joined #ltsp
12:58
<vbundi>
xchat crash x(
12:58
<bladernr_>
oh crap... that's been around since Karmic?! 0.0
12:58
0.o
12:58
sigh...
12:58
<alkisg>
No, it's much older :)
12:59
<vbundi>
?
12:59
<alkisg>
vbundi: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/203954
12:59
<bladernr_>
oh yeah, it is, isn't it... just realized it was opened prior to UDS-Karmic...
12:59
<vbundi>
ah so your i386 image wasn't built or what
13:00
<bladernr_>
ok... hrmmm... so before I start randomly hacking, I need to s/amd64/i386/g, yes?
13:00
<alkisg>
No it's just a problem with dhcpd.conf
13:00
bladernr_: the opposite
13:00
s/i386/amd64
13:00
<bladernr_>
woops... yeah
13:01
sorry, I blame the pollen and my goopy eyes... it's hard working when everything is blurry
13:01
:-)
13:01nubae_ has joined #ltsp
13:01
<vbundi>
are you using 64bit clients too?
13:02
<bladernr_>
vbundi: yes... I'm a 64bit snob like that ;-)
13:02Nubae has quit IRC
13:02
<vbundi>
ok just checking ;)
13:02
<bladernr_>
I believe I can do both, but I need to build a 32bit image first and add extra stuff to dhcpd.conf, though
13:02
at least that's how I understand it
13:02
<vbundi>
correct
13:04
<alkisg>
Either that or a pxelinux menu. In previous versions you'd also have to mess with ports and inetd.conf, but now it's done automatically.
13:05
<vbundi>
I think that it should ask what type of clients you're going to be using when you install LTSP... I'm using a 64bit LTSP server too but I plan on running 32 on my clients... I would think that this is the more common setup
13:05nubae has joined #ltsp
13:06
<johnny>
it is.. that's why fedora and gentoo's ltsp default to i386/x86 vbundi
13:06
<bladernr_>
that would be nice, but honestly, it would be better, IMHO, if it would just automagically configure for both if running on a 64bit OS, because you never know
13:06
<johnny>
altho.. i imagine in about 2 years.. the default will be amd64 all around
13:06
bladernr_, not possible..
13:06nubae_ has quit IRC
13:06
<johnny>
not with the current structure anyways..
13:06
we have to tell the client which image to use beforehand..
13:06
so it would require dhcp sections for each
13:06
<alkisg>
With the new pxelinux it's possible
13:07
<johnny>
ah..
13:07
well that would be neat
13:07
<alkisg>
But Ubuntu's pxelinux is stack in 3 years ago...
13:07
<vagrantc>
first, i get a bug report saying amd64 should default to i386. so i switched it to amd64... then i get a bug report saying that instlaling i386 on amd64 is unexpected behavior. so i switched it to the simplest case; install the same architecture.
13:07
<johnny>
bladernr_, get that fixed for us please :)
13:07
<alkisg>
...and we have lots and lots more clients not booting because of this
13:07
<bladernr_>
well, that's something to shoot for then... feature requests
13:07
<johnny>
vagrantc, well.. do you have this pxelinux alkisg is talking about? :)
13:07
<bladernr_>
heh... I can't get nothing done... I'm just a code monkey who's helping out with ISO testing
13:07
<johnny>
you could just build both then :)
13:07
<vbundi>
vagrantc: why can't you just get it right? ;P
13:08
<alkisg>
vagrantc: is ubuntu using the same logic for dhpcd.conf as debian?
13:08
<vagrantc>
i've got syslinux 3.71 on debian/stable and 3.85 on debian/testing
13:09
alkisg: not sure
13:09
<alkisg>
Because while installing from the amd64 cd, dhcpd.conf has i386 paths there
13:09
That was bladernr_'s problem...
13:09
<vagrantc>
right
13:09
that's a problem on debian, too
13:09
<alkisg>
Ah, ok, I thought you said "i switched it to the simplest case; install the same architecture."
13:09
<vagrantc>
alkisg: well, it installs the same architecture, but still leaves all the configuration for i386
13:09
<vbundi>
vagrantc: the current dhcpd config makes sense if the i386 is built on install
13:10
<vagrantc>
dhcpd is also not automatically enabled on debian
13:10
<alkisg>
Well the configuration files should at least match the generated chroot, I believe...
13:10
<vbundi>
so you build BOTH, default config is to boot i386 on all... if you want to specifically boot amd64, you'll have to make the changes
13:10
<vagrantc>
so requires manual configuration no matter what
13:11nubae_ has joined #ltsp
13:11
<johnny>
vbundi, not necessarily
13:11
<vbundi>
maybe comments in the default configuration file to give a heads up would help
13:11
<johnny>
if the client could tell the server what arch it is, the problem would be solved
13:11
via pxe
13:11
we'd just send it which one it was
13:11nubae has quit IRC
13:11
<vbundi>
johnny: sure, but I've got 64bit capable machines that I also want to run 32bit
13:11
<vagrantc>
building both is tricky for CD installs, as you can fit both architectures on one CD...
13:12
<alkisg>
vbundi: well in any case you'd need to specify those manually
13:12
<vagrantc>
we could probably use the architecture-detection code in pxelinux and just use the appropriate default, if present.
13:12
<vbundi>
vagrantc: could script a build-ltsp-client --arch XXX somewhere? unfortunately this would break if you didn't have a network connection at install
13:12
<alkisg>
But autodetecting amd64/i386 would be a nice feature, and the new pxelinux has some support for that
13:13
<vagrantc>
egads. ubuntu's syslinux is older than debian/stable!
13:13
<alkisg>
vagrantc: they have some problems in integrading it with gfxboot, and they don't have the time to get a new version
13:14
I've hit several occations where I had to download pxelinux from sid to boot some clients
13:14
They wouldn't boot with the Ubuntu one...
13:14nubae_ has quit IRC
13:16nubae has joined #ltsp
13:16
<vagrantc>
debian-installer includes isolinux and either cpuidtest.c32 or ifcup64.c32 to detect the appropriate architecture for CDs that support multiple architectures
13:19
<vbundi>
bladernr_: did your client end up booting now?
13:19
<bladernr_>
vbundi: sure did. worked great too
13:20
<vbundi>
right on
13:20
<bladernr_>
at least for the little bit I did with it... if I ever get enough hardware to do this on bare metal, I'd like to play more with it, but that's off a ways in the future
13:20
Hrmmm... what architectures can you build the client images for?
13:21
I know i386 and amd64... any others?
13:23
<vagrantc>
in theory, most architectures in debian are supported... in practice, i don't know that most work. :)
13:23
i have tested armel using qemu
13:27
<bladernr_>
was just wondering about ... say... sparc and older mac... heh... I even have a couple old NeXT Stations I could try ;-)
13:27
just nothing I can spare to serve as the server at the moment
13:27
<vbundi>
NeXT?!
13:27
<johnny>
older macs work
13:27
but you have to build the chroot on the mac
13:27
older as in imac
13:27
the first generation
13:27
<bladernr_>
vbundi: yeah... NeXT... heh
13:28
<vbundi>
bladernr_: lucky
13:28
<bladernr_>
imac... nah... I was thinking much older... heh... not IIGs old, but close... proformas, etc
13:28
vbundi: where are you?
13:29
ugh... telus... europe somewhere?
13:29
<vbundi>
haha
13:29
Canada
13:29
<bladernr_>
Oh... well then...
13:30
want them?
13:30
heh
13:31
<vbundi>
naw, I'm just jokin around, hell, I'm 25.... I remember seeing NeXT stations when I when I was little thinking they were awesome because they were black computers :P
13:32
<bladernr_>
well, they ARE awesome and not just because they are black computers... granted, I believe my blackberry has more memory, power and storage than the NeXTs do
13:33
<vbundi>
yeah my Dad's a network admin, and I remember him saying they were awesome when they got them
13:34
but yeah, really I don't know much about em
13:34
<bladernr_>
they're ... "appliances" would be the best word for them.
13:34
a step above thin clients perhaps... but pretty cool for what they are
13:34
plus.. as you said, they're black
13:35
and have neat keyboards
13:35
<vbundi>
where'd you get them?
13:40nubae_ has joined #ltsp
13:40
<johnny>
bladernr_, yeah right.. linux won't even boot on those
13:40nubae has quit IRC
13:43
<bladernr_>
vbundi: a guy I knew in Raleigh, NC had them and gave them to me when he moved to another state... also gave me an Apple Network Server (looks like a mini-fridge, and runs AIX) and a stack of sparcs and Macs
13:43
<vbundi>
neat
13:56
<bladernr_>
By the way, I think I forgot, but thanks everyone for the help in getting that LTSP server working. I appreciate it!
14:06vagrantc has quit IRC
14:33ogra_cmpc has quit IRC
14:34ogra_cmpc has joined #ltsp
14:38scottmaccal has quit IRC
14:42cliebow has quit IRC
15:01pmatulis has quit IRC
15:02vagrantc has joined #ltsp
15:11
<vbundi>
anyone else having problems getting to the cups admin page 'localhost:631' in lucid?
15:11
I have cupsd running but no cups web gui
15:11
<johnny>
why are you using the web gui?
15:12
<vbundi>
I've always done it that way I guess
15:12
<johnny>
as sudo/root do netstat -ltpn | grep 631
15:12
it's probably not started by default anymore
15:12
<vbundi>
on my laptop it is
15:12
<johnny>
i don't see a need to use it for most use cases anyways..
15:12
same distro?
15:12
same version rather
15:12
<vbundi>
yep
15:12
<johnny>
both using lucid?
15:12
<vbundi>
yes
15:12
<alkisg>
vbundi: works for me
15:12
<johnny>
you may have started it on my laptop..
15:13
<vbundi>
netstat reveals cupsd is listening on 631
15:13
<johnny>
ah
15:13
<vbundi>
bound to all ips
15:13
<johnny>
well i never use the webgui.. too ugly
15:13
<vbundi>
lol
15:13
<johnny>
don't have to use it often
15:13
the regular printer config handles most of my needs
15:13
<vbundi>
yeah I just use it to check stuff or print test pages
15:13
what, you use system-config-printer?
15:13
<johnny>
you can do it in the regular gui too tho
15:13
yes, it comes with fedora
15:14
but also ubuntu i think
15:14
<vbundi>
yes it's there
15:14
imo the web gui is much nicer, but that's moot
15:14
<alkisg>
vbundi: so what do you get with wget http://localhost:631 -O -
15:14
?
15:14
<vbundi>
sec
15:15
alkisg: a bunch-o-html to my terminal
15:15
<alkisg>
vbundi: and you don't get any html if you try with your browser?
15:15
Which browser is that?
15:15
<vbundi>
chromium/firefox
15:16
<alkisg>
Hmm any proxies?
15:16
<vbundi>
however I'm trying to view it remotely on the lan
15:16
<johnny>
firewall?
15:16
<vbundi>
still -- netstat shows it's bound to 0.0.0.0
15:16
<johnny>
sounds like firewall
15:16
<alkisg>
Ah, I think it doesn't answer to remote requests by default
15:16
I think it's blocked by the cups configuration itself
15:16
<johnny>
ah.. so it binds to 0.0.0.0, but doesn't answer?
15:16
sounds reasonable
15:17
<vbundi>
johnny: huh?
15:17
I think you guys are right though... it's not answering remotely
15:17
tried on my laptop that can bring it up on a local browser... I cant bring it up remotely
15:18
<vagrantc>
might be able to use ssh port forwarding to make it appear local.
15:18
<johnny>
or just edit the config :)
15:18
<vagrantc>
either ssh -R or -L
15:19
yeah, that's an option too..
15:19
<alkisg>
administration => allow remote
15:19
<vbundi>
after poking in /etc/cups/cupsd.conf I see that it has 'Listen localhost:631'; 'Listen /var/run/cups/cups.sock'
15:19
<alkisg>
From the local web ui
15:19
<vbundi>
alkisg: yea I think that'll work, or maybe changing to Listen 192.168.1.0:631
15:20
<johnny>
not sure why Listen localhost would uhmm.. make it bind to 0.0.0.0
15:20
somebody needs to redo the cups config file
15:20
<vbundi>
johnny: I know right? doesn't 0.0.0.0 = all? not local?
15:20
:q
15:41ogra_cmpc has quit IRC
15:41mikkel has quit IRC
15:54ogra_cmpc has joined #ltsp
16:07ltspbot has joined #ltsp
16:08ltspbot` has quit IRC
16:16hersonls has quit IRC
16:21japerry has quit IRC
16:22japerry has joined #ltsp
16:27alkisg has quit IRC
16:28artista_frustrad has quit IRC
16:29Lns has joined #ltsp
16:33newbie_ has joined #ltsp
16:33
<newbie_>
guten abend / good evening
16:49
<highvoltage>
guten abend newbie_
16:50
<newbie_>
bin am verzweifeln, gut jemanden zu lesen der Deutsch spricht
16:50pmatulis has joined #ltsp
17:15Faithful has quit IRC
17:22newbie_ has quit IRC
17:30Faithful has joined #ltsp
17:30Egyptian[Home] has quit IRC
17:31bobby_C has quit IRC
17:35Egyptian[Home] has joined #ltsp
17:55Gadi has left #ltsp
18:03mikeshultz has quit IRC
18:09patrice has joined #ltsp
18:10roy_hobbs has joined #ltsp
18:11
<roy_hobbs>
Is there a definitive list of the utilities required in the chroot?
18:13* patrice was looking for the LocalAppsSupport document from the 'LTSP for Fedora' at this link (https://fedorahosted.org/k12linux/wiki/LocalAppsSupport)
18:13
<patrice>
but i get a "Not Found" web page
18:14
is it cause that has not been created? anyone know if that is the case or if it is a bad URL
18:15* patrice is new to LTSP and was looking at how to auto launch a custom application on client from FC10 prebuilt image
18:16
<vagrantc>
roy_hobbs: there was a list of features...
18:16* vagrantc rummages around
18:19
<roy_hobbs>
Well, I read that whole PDF that we were talking about last night, and I've been sifting through the */docs directories in ltsp-upstream/ltsp-trunk
18:23
<vagrantc>
there was a page where we came up with the ltsp5 specifications on the old wiki...
18:24
that was more about core functionality, than specific binaries...
18:25
<roy_hobbs>
You're not talking about this are you: 'MueKow specification page'
18:26
So what happened, the wiki crashed a while back and everything was lost?
18:26
<vagrantc>
it wasn't all lost, but it wasn't all moved over, either, since much of it was content for ltsp 4.x and earlier and more misleading than helpful.
18:27
well, there was the link to the page: http://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_Documentation
18:28
roy_hobbs: the muekow specifications was significantly older.
18:29
<roy_hobbs>
I might just install Debian or Ubuntu in a VM, and take a look at what's going on there to get started
18:30
<vagrantc>
basically, it needs to support the screen scripts in ltsp-trunk/client/screen.d and ltspfs...
18:31
roy_hobbs: to get a list of files in each of the important client-side packages: http://packages.debian.org/lenny/i386/ltsp-client-core/filelist
18:31
roy_hobbs: also look at ltspfsd-core and ltspfs ... and for server-side, ltsp-server, ldm-server and ltspfs
18:31
<roy_hobbs>
ok, thanks
18:32
<vagrantc>
should probably drop configure-x.sh one of these days... :)
18:32
<roy_hobbs>
do you use debian or ubuntu personally? I noticed that you've had a decent number of commits for those branches on launchpad
18:32
<vagrantc>
i've been the primary debian maintainer/developer working on ltsp since 2006
18:33
maybe 2005, depending on how you look at it
18:33
<roy_hobbs>
Should I start with the client or server, or do they both pretty much need to be done at once?
18:33
<vagrantc>
i'll see if someone can dig up the old specifications page
18:34
roy_hobbs: the easiest thing i think is to just get the ltsp-server stuff building a basic chroot, and then work on building the client packages to install into the chroot
18:34
roy_hobbs: so arch ships binary tarballs for packages?
18:35
<roy_hobbs>
What I want to do is get a working thinclient before i start worrying about making tidy packages
18:35
well, yes and no =)
18:36
<vagrantc>
well, you can get the network booting stuff without even having any ltsp-client specific packages
18:36
<roy_hobbs>
all core packages are precompiled, but the PKGBUILD (a simple text file that specifies how to create the package) is readily accessible to be built on anyone's system
18:37
and there is also a user repository which only hosts the PKGBUILDs, so stuff from there must be compiled manually
18:37
We do have this: http://aur.archlinux.org/packages.php?ID=572 but it seems useless
18:38
<vagrantc>
roy_hobbs: yeah, that's for ltsp 4.x
18:43highvoltage has quit IRC
18:44
<roy_hobbs>
btw, stop me when you've had enough of me for the time being
18:44
<vagrantc>
heh
18:44
<roy_hobbs>
is there a script that's supposed to actually build out the dir structure of the chroot?
18:44
non of the build-client stuff looks like it does that
18:45
I've been looking around for and /init script referenced in the PDF
18:47
<vagrantc>
roy_hobbs: debian/ubuntu both use debootstrap, which installs a base system into a chroot ... so all that stuff is handled in the packages themselves.
18:48gavmac has joined #ltsp
18:53staffencasa has quit IRC
18:53
<roy_hobbs>
lucky virtualbox supports pxe
18:53
luckily*
18:56gavmac has quit IRC
18:56gavmac has joined #ltsp
18:56gavmac has left #ltsp
19:07roy_hobbs has left #ltsp
19:11bladernr_ has quit IRC
19:26bladernr_ has joined #ltsp
19:30patrice has quit IRC
19:43highvoltage has joined #ltsp
19:58Lns has quit IRC
20:15try2free has joined #ltsp
20:20nubae_ has quit IRC
20:31pmatulis has quit IRC
20:50morfic is now known as Machinist
20:55japerry_cat has joined #ltsp
20:59japerry has quit IRC
20:59japerry_cat is now known as japerry
21:12bladernr_ has quit IRC
21:33Faithful has quit IRC
21:35Machinist is now known as morfic
22:24try2free has left #ltsp
22:27abeehc has quit IRC
22:37abeehc has joined #ltsp
23:17alkisg has joined #ltsp
23:25japerry has quit IRC
23:25japerry has joined #ltsp
23:52ogra_cmpc has quit IRC
23:53ogra_cmpc has joined #ltsp