|00:01||alkisg has quit IRC|
|00:05||bobby_C has quit IRC|
|00:17||bobby_C has joined #ltsp|
|00:45||alkisg has joined #ltsp|
|00:48||mardok has joined #ltsp|
Is there a way to get a LTSP server working on PowerPC?
|00:49||mistik1_ has joined #ltsp|
|00:52||mistik1 has quit IRC|
|00:52||mistik1_ is now known as mistik1|
|00:58||alkisg has quit IRC|
mardok, use --arch when you make the chroot with ltsp-build-client i'd guess
|01:34||shogunx has joined #ltsp|
mardok, sure, if there's a build of that distribution that somewhat matches the host distro
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
and, once you do that, you have to actually build the client distro from powerpc
from the powerpc machine
then you can copy it back to the server, and serve it up
then all you have to worry about is setting up yaboot of whatever remote boot method it uses
|02:09||gnunux has joined #ltsp|
|02:11||gnunux has quit IRC|
|02:36||geckozo6 has left #ltsp|
|02:44||dobber has joined #ltsp|
|02:50||sweetpi has quit IRC|
|02:51||alkisg has joined #ltsp|
|02:58||sutula has quit IRC|
|02:59||sutula has joined #ltsp|
|03:09||Appiah has quit IRC|
|03:10||Appiah has joined #ltsp|
|03:15||Da-Geek has joined #ltsp|
|03:25||gorkhaan has joined #ltsp|
|03:53||ogra_ac_ is now known as ogra_ac|
|03:58||BenG has joined #ltsp|
I'm trying to run a Debian Squeeze based LTSP-5 on a vserver (i.e. Linux-vserver), most things work really well
sound, video, nbd root image
some stuff doesn't: USB keys and NBD swap to be precise
swap documentation does not work for sure
as in /usr/share/docs/ltsp-server/swap - instruction don't work
if anyone is in a remotely similar situation, please check in with me and we'll swap notes
has anyone NBD swap or USB keys working on Debian Squeeze?
|04:14||gorkhaan has quit IRC|
|04:53||alkisg has quit IRC|
|05:06||ogra_ac has quit IRC|
wow, 1 hour and no response!
is anybody home?
|05:19||ogra_ac has joined #ltsp|
|05:28||gorkhaan has joined #ltsp|
|05:35||alkisg has joined #ltsp|
|05:39||BenG has quit IRC|
|06:14||ogra_ac_ has joined #ltsp|
|06:17||ogra_ac has quit IRC|
|06:18||pingufan has joined #ltsp|
|06:19||ogra_ac_ has quit IRC|
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: _
Please, can somebody help me? I am a novice with ltsp.
|06:22||ogra_ac has joined #ltsp|
pingufan, probably means there's a problem in your tftpboot directory.
Check your tftpboot directory, to see if there's kernel images in there and if pxelinux.cfg/default correctly references those images
|06:28||mgariepy has joined #ltsp|
morning everyone !
Good afternoon Marc. :-)
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?
Should the image directory inside the tftp server contain a kernel image? This dir is now empty!
I'm afraif I will have to setup everything new, but I must leave for one hour. Can somebody then guide me, please?
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)
I do hope I pointed you into the right direction at least.
|07:29||mgariepy has quit IRC|
|07:42||mgariepy has joined #ltsp|
|07:50||gorkhaan has quit IRC|
|07:50||shogunx has quit IRC|
|07:50||otavio has quit IRC|
|07:50||NeonLicht has quit IRC|
|07:50||mistik1 has quit IRC|
|07:50||alexqwesa has quit IRC|
|07:50||johnny has quit IRC|
|07:50||Mobe_ has quit IRC|
|07:53||shogunx has joined #ltsp|
|07:53||mistik1 has joined #ltsp|
|07:53||alexqwesa has joined #ltsp|
|07:53||johnny has joined #ltsp|
|07:53||Mobe_ has joined #ltsp|
|07:53||otavio has joined #ltsp|
|07:53||NeonLicht has joined #ltsp|
|08:08||Uzzi has joined #ltsp|
|08:09||gorkhaan has joined #ltsp|
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
Hyperbyte: Thank you. You don' know which community-repositories I will need to upgrade kiwi-ltsp on SuSE 11.3 ?
I accidently uninstalled the kiwi boot images and find no source for them.
Is it possible to have dhcp server on ip and ltsp server on other ip?
pingufan, there should be a #kiwi-ltsp channel, note that the suse implementation massively differs from all other ltsp implementations
I am logged in there, too. 6 persons, all of them appear not to be at their keyboards... :(
well, dont expect much knowledge about kiwi in here
Uzzi: are you using nbd?
Debian doesn't need ltsp-update-image since it's using NFS
So don't run that command on debian
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.
Get a root shell, and try: ssh user@server
Change "user" to an existing username, but leave "server" exactly as it is, don't change it.
See if you get any warnings about ssh keys there.
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
Uzzi: I mean in the ssh command
Not in any logs
See what I wrote above
* Restarting OpenBSD Secure Shell server sshd [ OK ]
Uzzi: erm, do you need me to write more specific steps?
Can you get a root shell on a thin client?
As written above?
Nice. Now, run: ssh user@server
(04:18:47 PM) alkisg: Change "user" to an existing username, but leave "server" exactly as it is, don't change it.
(04:18:59 PM) alkisg: See if you get any warnings about ssh keys there.
alwayse command not found
What is alwayse?
The command was "ssh"
Yes, ssh is there
You can't connect without ssh.
ltsp login: root ----->bash:root: command not found---->root@ltsp:/#----->ssh---->Password----->
I don't understand what you're saying.
|08:34||cyberorg has quit IRC|
Did you run "ssh user@server"?
And after always Login incorrect
If you can't ssh, then it's not an ltsp problem
in other client yes no problem
now i'm opening a ssh session, to see the log and reboot or reload services
Sorry, I can't understand what you're saying or trying to do. Goodbye.
I hope this isn't impolite, I really can't understand :(
I've an ssh session opened now
I think ssh works fine
Nov 26 15:36:08 ServerFillea sshd: pam_unix(sshd:session): session opened for user andrea by (uid=0)
The steps above were specifically to test ssh from *thin client local shells*
That way you would test the ssh keys *in your chroot*
|08:44||cyberorg has joined #ltsp|
It was not about ssh in general...
Anyway, need to go, bye.
ok I'm tryng do it
in chroot ssh works fine too
No, not in chroot. In the local client shell.
|08:47||alkisg has quit IRC|
|08:52||pingufan has left #ltsp|
|08:54||gnunux has joined #ltsp|
|09:09||mikkel has joined #ltsp|
|09:27||Uzzi has quit IRC|
|09:31||mgariepy has quit IRC|
|09:38||alkisg has joined #ltsp|
|09:49||gnunux has quit IRC|
|09:55||mgariepy has joined #ltsp|
|10:07||Da-Geek has quit IRC|
|10:18||komunista has joined #ltsp|
|10:23||komunista has quit IRC|
|10:25||komunista has joined #ltsp|
|10:38||Kicer86 has joined #ltsp|
|10:45||dobber has quit IRC|
|11:39||alexqwesa has quit IRC|
|11:41||alexqwesa has joined #ltsp|
|11:43||alkisg has quit IRC|
|12:02||GodFather has joined #ltsp|
|12:06||novacaine has joined #ltsp|
|12:09||vagrantc has joined #ltsp|
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:10||GodFather has quit IRC|
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
but the thin client doesn't see it
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...
novacaine: think of the thin client as an extra monitor, keyboard and mouse for the server.
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
ok but i think of / and /opt/ltsp as two roots. where do I should create users for the thin clients?
you create users, install applications, etc. all on the server.
so why is necessary to set up a root on /opt/ltsp if the thin clients see users and application of the server?
for a typical setup... there are other modes of operation, called fat clients, where it's more complicated
novacaine: that's the operating system that the thin client boots.
novacaine: people log into the server *though* the thin client.
novacaine: so the thin client needs a basic environment to be able to allow the users to do that.
novacaine: are you familiar with ssh? this is basically ssh with X forwarding... i.e. ssh -X (or specifically, ssh -Y)
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?
yes, i saw the ltsp today for the first time and i thought it was ssh with x forwarding..
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?
novacaine: more or less
ok and what i miss? :)
i don't know what you've missed
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:21||alkisg has joined #ltsp|
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 ...
because you're logged into the server
so which kind of personalizaiont can I do on the (opt/ltsp
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|
novacaine: there are infinite possibilities... what do you *want* to do?
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...
it is the minimal operating system to boot to LDM, which is essentially a GUI frontend to ssh -X
(it's a bit of a white lie, in that it can do lots of other things, but that's the default use)
ok it's as i've thought
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
and then another thin called fat clients, where all of the applications run on the thin-client itself
and remoteapps, where most applications are run on the thin-client hardware, but some are run on the server
just to keep you on your toes :)
but the defaults are just plain thin-clients, where everything is running on the server :)
(well, nearly everything)
obviously X itself is running on the thin-client
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
if your clients are powerful enough, playing with localapps or maybe even fat clients is worth exploring
though even with all those technologies, i think the user is still located on the server itself.
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?
there's an lts.conf option for that
vagrantc: "lts.conf" :: http://manpages.ubuntu.com/lts.conf
ok thank you for all....
maybe we will do a revolution in our school...but i think it's a bit hard :)
it is difficult... hopefully worth it :)
one nice thing is you can fairly easily set up the infrastructure to dual-boot an OS from the disk and network
|12:43||johnny has left #ltsp|
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...
but here in italy in the school microsoft still rule...no one has enough skill to work on linux...
we're a bit late in the public administration
|12:53||alkisg has quit IRC|
vagrantc: is there some app to control the thib client? i saw thin-client-manager but i think it lacks a lot of tings
i think thin-client-manager is unmaintained... not sure about alternatives
alkisg (who just left) has been working on something
ok maybe i will ask in the future
|13:18||mikeshultz has joined #ltsp|
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?
Just found the ServerSizing wiki page. n/m
|13:34||johnny has joined #ltsp|
|13:44||vagrantc has quit IRC|
|13:47||vagrantc has joined #ltsp|
|14:06||spectra has quit IRC|
|14:09||spectra has joined #ltsp|
|14:22||vagrantc has quit IRC|
|14:24||vagrantc has joined #ltsp|
|14:28||sweetpi has joined #ltsp|
|14:39||sweetpi has quit IRC|
|14:46||johnny has left #ltsp|
|14:47||johnny has joined #ltsp|
|14:57||vagrantc has quit IRC|
|15:10||vagrantc has joined #ltsp|
|15:20||alexqwesa has quit IRC|
|15:29||vagrantc has quit IRC|
|15:37||johnny has left #ltsp|
|15:40||novacaine has quit IRC|
|16:01||Kicer86 has quit IRC|
|16:13||mgariepy has quit IRC|
|16:31||mikkel has quit IRC|
|16:54||vmlintu has quit IRC|
|17:07||vagrantc has joined #ltsp|
|17:19||johnny has joined #ltsp|
|17:28||mikeshultz is now known as mikeshultz-away|
|17:28||mikeshultz-away has left #ltsp|
|17:31||ogra_ac_ has joined #ltsp|
|17:35||ogra_ac has quit IRC|
|17:48||mordocai has quit IRC|
|17:49||mordocai has joined #ltsp|
|18:12||bobby_C has quit IRC|
|18:21||johnny has left #ltsp|
|18:24||mardok has quit IRC|
|18:57||vagrantc has quit IRC|
|19:01||vagrantc has joined #ltsp|
|19:03||johnny has joined #ltsp|
|19:06||litlebuda has joined #ltsp|
|19:23||komunista has quit IRC|
|19:36||zz_evil_root is now known as evil_root|
|19:39||evil_root is now known as zz_evil_root|
|19:58||johnny has left #ltsp|
|20:02||johnny has joined #ltsp|
|20:07||Damianos has joined #ltsp|
|20:08||Damianos has left #ltsp|
|20:19||ogra has quit IRC|
|20:32||ogra has joined #ltsp|
|20:41||vagrantc has quit IRC|
|20:49||vagrantc has joined #ltsp|
|21:58||shogunx has quit IRC|
|22:08||shogunx has joined #ltsp|
|22:11||vagrantc has quit IRC|
|22:19||litlebuda has quit IRC|
|22:37||alexqwesa has joined #ltsp|
|22:53||BWMerlin has joined #ltsp|
|23:19||shogunx has quit IRC|
|23:21||shogunx has joined #ltsp|