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


Channel log from 26 November 2010   (all times are UTC)

00:01alkisg has quit IRC
00:05bobby_C has quit IRC
00:17bobby_C has joined #ltsp
00:45alkisg has joined #ltsp
00:48mardok has joined #ltsp
00:48
<mardok>
Is there a way to get a LTSP server working on PowerPC?
00:49mistik1_ has joined #ltsp
00:52mistik1 has quit IRC
00:52mistik1_ is now known as mistik1
00:58alkisg has quit IRC
01:25
<sep>
mardok, use --arch when you make the chroot with ltsp-build-client i'd guess
01:34shogunx has joined #ltsp
01:40
<johnny>
mardok, sure, if there's a build of that distribution that somewhat matches the host distro
01:41
like, if there's no powerpc version of the current ubuntu distro release already for powerpc, you won't be able to build a client
01:42
and, once you do that, you have to actually build the client distro from powerpc
01:42
from the powerpc machine
01:42
then you can copy it back to the server, and serve it up
01:42
then all you have to worry about is setting up yaboot of whatever remote boot method it uses
01:42
s/of/or/
02:09gnunux has joined #ltsp
02:11gnunux has quit IRC
02:36geckozo6 has left #ltsp
02:44dobber has joined #ltsp
02:50sweetpi has quit IRC
02:51alkisg has joined #ltsp
02:58sutula has quit IRC
02:59sutula has joined #ltsp
03:09Appiah has quit IRC
03:10Appiah has joined #ltsp
03:15Da-Geek has joined #ltsp
03:25gorkhaan has joined #ltsp
03:53ogra_ac_ is now known as ogra_ac
03:58BenG has joined #ltsp
03:59
<BenG>
heya all
03:59
good morning
03:59
I'm trying to run a Debian Squeeze based LTSP-5 on a vserver (i.e. Linux-vserver), most things work really well
04:00
sound, video, nbd root image
04:00
some stuff doesn't: USB keys and NBD swap to be precise
04:01
swap documentation does not work for sure
04:01
as in /usr/share/docs/ltsp-server/swap - instruction don't work
04:01
if anyone is in a remotely similar situation, please check in with me and we'll swap notes
04:02
has anyone NBD swap or USB keys working on Debian Squeeze?
04:14gorkhaan has quit IRC
04:53alkisg has quit IRC
05:06ogra_ac has quit IRC
05:16
<BenG>
wow, 1 hour and no response!
05:16
is anybody home?
05:19ogra_ac has joined #ltsp
05:28gorkhaan has joined #ltsp
05:35alkisg has joined #ltsp
05:39BenG has quit IRC
06:14ogra_ac_ has joined #ltsp
06:17ogra_ac has quit IRC
06:18pingufan has joined #ltsp
06:19ogra_ac_ has quit IRC
06:21
<pingufan>
Hello, I want to ask here in parallel to #kiwi-ltsp as there are only a few users. I was running openSuSE 11.1 with kiwi-ltsp and did an upgrade to 11.3 a few days ago. Now I noticed that ltsp is not working any more. The client boots the loader, but the last line sais: "Could not find kernel image: boot/linux", followed by boot: _
06:21
Please, can somebody help me? I am a novice with ltsp.
06:22ogra_ac has joined #ltsp
06:24
<Hyperbyte>
pingufan, probably means there's a problem in your tftpboot directory.
06:26
Check your tftpboot directory, to see if there's kernel images in there and if pxelinux.cfg/default correctly references those images
06:28mgariepy has joined #ltsp
06:28
<mgariepy>
morning everyone !
06:29
<Hyperbyte>
Good afternoon Marc. :-)
06:33
<pingufan>
Hyperbyte: I see a wrong IP in the default file, pointing to 192.168.0.254. My server is 10.0.0.4 where KIWI is installed. Must I edit that?
06:40
Should the image directory inside the tftp server contain a kernel image? This dir is now empty!
06:45
I'm afraif I will have to setup everything new, but I must leave for one hour. Can somebody then guide me, please?
06:50
<Hyperbyte>
pingufan, I'm not 100% sure what your tftpboot directory should look like and/or how you can regenerate it (someone else will be able to help you with that)
06:50
I do hope I pointed you into the right direction at least.
07:29mgariepy has quit IRC
07:42mgariepy has joined #ltsp
07:50gorkhaan has quit IRC
07:50shogunx has quit IRC
07:50otavio has quit IRC
07:50NeonLicht has quit IRC
07:50mistik1 has quit IRC
07:50alexqwesa has quit IRC
07:50johnny has quit IRC
07:50Mobe_ has quit IRC
07:53shogunx has joined #ltsp
07:53mistik1 has joined #ltsp
07:53alexqwesa has joined #ltsp
07:53johnny has joined #ltsp
07:53Mobe_ has joined #ltsp
07:53otavio has joined #ltsp
07:53NeonLicht has joined #ltsp
08:08Uzzi has joined #ltsp
08:09gorkhaan has joined #ltsp
08:09
<Uzzi>
hi I've this error: this workstation isn't authorized to connect to server I've do ltsp-update-sshkeys and ltsp-update-image. but the error is the same
08:10
<pingufan>
Hyperbyte: Thank you. You don' know which community-repositories I will need to upgrade kiwi-ltsp on SuSE 11.3 ?
08:11
I accidently uninstalled the kiwi boot images and find no source for them.
08:11
<Uzzi>
Is it possible to have dhcp server on ip and ltsp server on other ip?
08:13
<ogra_ac>
pingufan, there should be a #kiwi-ltsp channel, note that the suse implementation massively differs from all other ltsp implementations
08:14
<pingufan>
I am logged in there, too. 6 persons, all of them appear not to be at their keyboards... :(
08:14
<ogra_ac>
well, dont expect much knowledge about kiwi in here
08:14
<alkisg>
Uzzi: distro/version?
08:17
<Uzzi>
debian
08:18
lenny
08:18
<alkisg>
Uzzi: are you using nbd?
08:18
<Uzzi>
no
08:18
<alkisg>
Debian doesn't need ltsp-update-image since it's using NFS
08:18
<Uzzi>
only nfs
08:18
<alkisg>
So don't run that command on debian
08:18
<Uzzi>
ok
08:18
<alkisg>
!SCREEN_08
08:18
<ltspbot`>
alkisg: "SCREEN_08" :: To get a root shell on a Debian thin client, put SCREEN_07=ldm, SCREEN_08=shell and SCREEN_DEFAULT=07 to lts.conf.
08:19
<alkisg>
Get a root shell, and try: ssh user@server
08:19
Change "user" to an existing username, but leave "server" exactly as it is, don't change it.
08:19
See if you get any warnings about ssh keys there.
08:20
<Uzzi>
Nov 26 14:33:19 ServerFillea ltsp: # Creating dsa-hostkey for 172.16.6.50 Nov 26 14:33:19 ServerFillea ltsp: # Creating rsa-hostkey for 172.16.6.50 only these
08:21
<alkisg>
Uzzi: I mean in the ssh command
08:21
Not in any logs
08:21
See what I wrote above
08:21
<Uzzi>
* Restarting OpenBSD Secure Shell server sshd [ OK ]
08:22
<alkisg>
Uzzi: erm, do you need me to write more specific steps?
08:22
Can you get a root shell on a thin client?
08:22
As written above?
08:26
<Uzzi>
root@ltsp:/#
08:26
<alkisg>
Nice. Now, run: ssh user@server
08:26
(04:18:47 PM) alkisg: Change "user" to an existing username, but leave "server" exactly as it is, don't change it.
08:26
(04:18:59 PM) alkisg: See if you get any warnings about ssh keys there.
08:30
<Uzzi>
alwayse command not found
08:30
<alkisg>
What is alwayse?
08:30
The command was "ssh"
08:30
<Uzzi>
yes
08:30
<alkisg>
Yes, ssh is there
08:30
You can't connect without ssh.
08:32
<Uzzi>
ltsp login: root ----->bash:root: command not found---->root@ltsp:/#----->ssh---->Password----->
08:34
<alkisg>
I don't understand what you're saying.
08:34cyberorg has quit IRC
08:34
<alkisg>
Did you run "ssh user@server"?
08:34
<Uzzi>
And after always Login incorrect
08:34
<alkisg>
If you can't ssh, then it's not an ltsp problem
08:34
<Uzzi>
in other client yes no problem
08:35
now i'm opening a ssh session, to see the log and reboot or reload services
08:35
<alkisg>
Sorry, I can't understand what you're saying or trying to do. Goodbye.
08:35
<Uzzi>
:(
08:36
<alkisg>
I hope this isn't impolite, I really can't understand :(
08:36
<Uzzi>
I've an ssh session opened now
08:41
I think ssh works fine
08:42
Nov 26 15:36:08 ServerFillea sshd[20306]: pam_unix(sshd:session): session opened for user andrea by (uid=0)
08:44
<alkisg>
The steps above were specifically to test ssh from *thin client local shells*
08:44
That way you would test the ssh keys *in your chroot*
08:44cyberorg has joined #ltsp
08:44
<alkisg>
It was not about ssh in general...
08:44
Anyway, need to go, bye.
08:45
<Uzzi>
ok I'm tryng do it
08:46
in chroot ssh works fine too
08:47
<alkisg>
No, not in chroot. In the local client shell.
08:47
Bye.
08:47alkisg has quit IRC
08:52pingufan has left #ltsp
08:54gnunux has joined #ltsp
08:55
<gnunux>
hi
09:09mikkel has joined #ltsp
09:27Uzzi has quit IRC
09:31mgariepy has quit IRC
09:38alkisg has joined #ltsp
09:49gnunux has quit IRC
09:55mgariepy has joined #ltsp
10:07Da-Geek has quit IRC
10:18komunista has joined #ltsp
10:23komunista has quit IRC
10:25komunista has joined #ltsp
10:38Kicer86 has joined #ltsp
10:45dobber has quit IRC
11:39alexqwesa has quit IRC
11:41alexqwesa has joined #ltsp
11:43alkisg has quit IRC
12:02GodFather has joined #ltsp
12:06novacaine has joined #ltsp
12:09vagrantc has joined #ltsp
12:10
<novacaine>
hi all. i'm a teacher in a italian high school, today we installed the ltsp server in one of our labs as an experiment hoping to migrate every labs to linux systems...but i miss something on the working properties: the thin client should see only the files in /opt/ltsp/i386 ?
12:10GodFather has quit IRC
12:11
<novacaine>
i can't undestand why the thin client log in with the server users. i tried to chroot on /opt/ltsp/i386 and make an user
12:11
but the thin client doesn't see it
12:11
<vagrantc>
novacaine: the thin client itself will only see files inside /opt/ltsp/i386, but you typically log into the server from the thin client, and so your session is actually running on the server...
12:12
novacaine: think of the thin client as an extra monitor, keyboard and mouse for the server.
12:12
<novacaine>
i logged in the thin client with the same user of the server, i installed an application and i saw that it was installed on the server not on the /opt/ltsp
12:13
<vagrantc>
correct.
12:13
<novacaine>
ok but i think of / and /opt/ltsp as two roots. where do I should create users for the thin clients?
12:13
<vagrantc>
you create users, install applications, etc. all on the server.
12:13
<novacaine>
so why is necessary to set up a root on /opt/ltsp if the thin clients see users and application of the server?
12:14
<vagrantc>
for a typical setup... there are other modes of operation, called fat clients, where it's more complicated
12:14
novacaine: that's the operating system that the thin client boots.
12:15
novacaine: people log into the server *though* the thin client.
12:15
novacaine: so the thin client needs a basic environment to be able to allow the users to do that.
12:16
novacaine: are you familiar with ssh? this is basically ssh with X forwarding... i.e. ssh -X (or specifically, ssh -Y)
12:16
<novacaine>
ok but let's imagine a thing, it could bootstrap from the same root of the server, there is no conceptual problem? we create the /opt/ltsp root just to have a minimal client ? right?
12:17
yes, i saw the ltsp today for the first time and i thought it was ssh with x forwarding..
12:19
vagrantc: so the /opt/ltsp directory exists just to have a minimal boot and avoid the thin client to boot from the "big" server that could have an heavier system?
12:19
<vagrantc>
novacaine: more or less
12:20
<novacaine>
ok and what i miss? :)
12:20
<vagrantc>
i don't know what you've missed
12:20
i mean, having an environment dedicated to the thin client alone allows to do customizations specific to the thin-client, which would be trickier if you shared it for multiple purposes.
12:21alkisg has joined #ltsp
12:22
<novacaine>
ok but i can't understand if i want to install an application for the thin clients, i have to install on the server root and not in /opt/ltsp, i mean i have to to apt-get install xx and not chroot /opt/ltsp... apt-get ...
12:23
<vagrantc>
because you're logged into the server
12:23
<novacaine>
so which kind of personalizaiont can I do on the (opt/ltsp
12:23
<vagrantc>
!docs
12:23
<ltspbot`>
vagrantc: "docs" :: For the most current documentation, see https://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_LtspDocumentationUpstream
12:23* vagrantc wonders if that's actually up to do
12:24
<vagrantc>
novacaine: there are infinite possibilities... what do you *want* to do?
12:26
<novacaine>
ok ok i just wanted to figure out which was the role of the /opt/ltsp if we see users and apps of the server...
12:29
<vagrantc>
it is the minimal operating system to boot to LDM, which is essentially a GUI frontend to ssh -X
12:29
(it's a bit of a white lie, in that it can do lots of other things, but that's the default use)
12:30
<novacaine>
ok it's as i've thought
12:30
<vagrantc>
novacaine: now that you understand that... the things where you would actually mess with the chroot more directly would be "localapps", where some of the applications actually do run on the thin-client itself, but most run on the server
12:31
and then another thin called fat clients, where all of the applications run on the thin-client itself
12:32
and remoteapps, where most applications are run on the thin-client hardware, but some are run on the server
12:32
just to keep you on your toes :)
12:33
but the defaults are just plain thin-clients, where everything is running on the server :)
12:33
(well, nearly everything)
12:33
obviously X itself is running on the thin-client
12:34
<novacaine>
ok i'v got it. i saw localapps today because we think that some apps like firefox is better if they run on the clients
12:35
<vagrantc>
if your clients are powerful enough, playing with localapps or maybe even fat clients is worth exploring
12:36
though even with all those technologies, i think the user is still located on the server itself.
12:36
<novacaine>
ok i say you that i've not read a lot of docs, but let's imagine that i want all the thin clients to shut down at a specific hour, i need to set up cron on /opt/ltsp.... of i can do this via ltsp.conf?
12:36
<vagrantc>
there's an lts.conf option for that
12:36
!lts.conf
12:36
<ltspbot`>
vagrantc: "lts.conf" :: http://manpages.ubuntu.com/lts.conf
12:40
<novacaine>
ok thank you for all....
12:40
maybe we will do a revolution in our school...but i think it's a bit hard :)
12:42
<vagrantc>
it is difficult... hopefully worth it :)
12:42
one nice thing is you can fairly easily set up the infrastructure to dual-boot an OS from the disk and network
12:43johnny has left #ltsp
12:45
<novacaine>
yes we did this today. cause there are a lot "bureaucratic" difficult to set up a dual "disk" boot so we decided to use ltsp so we just have to modify one machine...
12:46
but here in italy in the school microsoft still rule...no one has enough skill to work on linux...
12:46
we're a bit late in the public administration
12:53alkisg has quit IRC
12:56
<novacaine>
vagrantc: is there some app to control the thib client? i saw thin-client-manager but i think it lacks a lot of tings
12:57
<vagrantc>
i think thin-client-manager is unmaintained... not sure about alternatives
12:58
alkisg (who just left) has been working on something
12:58
<novacaine>
ok maybe i will ask in the future
13:18mikeshultz has joined #ltsp
13:19
<mikeshultz>
Look for resources on server hardware and what kind of resources would be needed per client. Can any of you point me in the right direction?
13:21
Just found the ServerSizing wiki page. n/m
13:34johnny has joined #ltsp
13:44vagrantc has quit IRC
13:47vagrantc has joined #ltsp
14:06spectra has quit IRC
14:09spectra has joined #ltsp
14:22vagrantc has quit IRC
14:24vagrantc has joined #ltsp
14:28sweetpi has joined #ltsp
14:39sweetpi has quit IRC
14:46johnny has left #ltsp
14:47johnny has joined #ltsp
14:57vagrantc has quit IRC
15:10vagrantc has joined #ltsp
15:20alexqwesa has quit IRC
15:29vagrantc has quit IRC
15:37johnny has left #ltsp
15:40novacaine has quit IRC
16:01Kicer86 has quit IRC
16:13mgariepy has quit IRC
16:31mikkel has quit IRC
16:54vmlintu has quit IRC
17:07vagrantc has joined #ltsp
17:19johnny has joined #ltsp
17:28mikeshultz is now known as mikeshultz-away
17:28mikeshultz-away has left #ltsp
17:31ogra_ac_ has joined #ltsp
17:35ogra_ac has quit IRC
17:48mordocai has quit IRC
17:49mordocai has joined #ltsp
18:12bobby_C has quit IRC
18:21johnny has left #ltsp
18:24mardok has quit IRC
18:57vagrantc has quit IRC
19:01vagrantc has joined #ltsp
19:03johnny has joined #ltsp
19:06litlebuda has joined #ltsp
19:23komunista has quit IRC
19:36zz_evil_root is now known as evil_root
19:39evil_root is now known as zz_evil_root
19:58johnny has left #ltsp
20:02johnny has joined #ltsp
20:07Damianos has joined #ltsp
20:08Damianos has left #ltsp
20:19ogra has quit IRC
20:32ogra has joined #ltsp
20:41vagrantc has quit IRC
20:49vagrantc has joined #ltsp
21:58shogunx has quit IRC
22:08shogunx has joined #ltsp
22:11vagrantc has quit IRC
22:19litlebuda has quit IRC
22:37alexqwesa has joined #ltsp
22:53BWMerlin has joined #ltsp
23:19shogunx has quit IRC
23:21shogunx has joined #ltsp