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


Channel log from 29 January 2007   (all times are UTC)

00:11pdjbarbe1 has joined #ltsp
00:15g333k_laptop has quit IRC
00:26pdjbarbe2 has quit IRC
00:49PMantis has quit IRC
00:53oldwolf has quit IRC
01:21MoL0ToV has joined #ltsp
02:32codey has joined #ltsp
02:32
<codey>
hi there
02:32
anyone around? got some problem with my ltsp setup..
02:32
clients do not set there own hostname anymore :/
02:32
=> wrong resolution for x
02:47vanya has joined #ltsp
03:17SiCk has joined #ltsp
03:42
<sep>
codey, what did you change ?
03:44
codey, if you defined a hostname file in the chroot i think it overrules the hostname from dhcp/dns. Personaly i use mac address directly in lts.-conf
04:11Sp0oKeR has joined #ltsp
04:25slipttees has joined #ltsp
04:28slipttees has quit IRC
04:28slipttees has joined #ltsp
04:36Avatara has joined #ltsp
05:07plamengr has joined #ltsp
05:07plamengr has left #ltsp
05:11ogra has joined #ltsp
05:24vlt is now known as vlt|afk
05:36slipttees is now known as slipttees|work
05:57kaminski-ltsp-br has joined #ltsp
05:58
<kaminski-ltsp-br>
jammcq: good mornin'
06:25msinhore has joined #ltsp
06:43antgel_ has joined #ltsp
06:48
<antgel_>
hi, is ltsp-build-client a muekow-only thing? i've looked, but it's not obvious to me
06:48
<ogra>
yes it is
06:49
<antgel_>
ogra: thanks. i should have read more docs before getting going - my users need local printing and i'm not sure that muekow supports that
06:50
<ogra>
it does from edgy on ...
06:51
(or etch if you use debian)
06:51
<antgel_>
ogra: i'm using etch
06:51
:)
06:51
ogra: are you involved in development?
06:51
<ogra>
yep
06:53
<antgel_>
ogra: you sounded knowlegeable :)
06:53
<ogra>
heh :)
06:54
<antgel_>
so let me ask you this...
06:54
i've set up a basic ltsp system here, all works great, but can't quite get my head around local printing
06:55
<ogra>
look if lp_server is in the client chroot somewhere
06:55
<antgel_>
i understand that i need a stanza in lts.conf with the hostname, but how do i know a machine will always get a certain hostname?
06:55
<ogra>
i'm not sure debian kept it ...
06:55
<antgel_>
do i bind hostname to mac address somehow?
06:56
<ogra>
use the MAC address :) .... i never use hostnames
06:56
<antgel_>
ogra: oh, you can do that in lts.conf?
06:56
<ogra>
sure
06:57
<antgel_>
so why would anyone want to mess around with hostnames and dhcp?
06:57
<ogra>
there is an example lts.conf including a printserver setup in /opt/ltsp/i386/usr/share/doc/ltsp-client
06:57
(unless debian ripped that out)
06:57
<antgel_>
it's there
06:58
hmm. lp_server OTOH appears to not be present
06:58egypcio has quit IRC
06:59
<antgel_>
does this mean i need to use ltsp 4 - rm /opt/ltsp and install it again with ltspadmin instead of apt?
07:00
ogra: nb the lts.conf example doesn't contain anything about mac addresses ;)
07:02
<ogra>
it does in the ubuntu package
07:03
well, you could use ubuntu edgy instead
07:03
printing works there for sure
07:04
<antgel_>
ogra: i know, but this is on an existing server and it's too much churn to reinstall the OS
07:05
i don't think users will notice a difference with v4, from what i gather it's more an infrastructure thing (v5)
07:05
<ogra>
what kind of printer is that ?
07:05
<antgel_>
a crappy usb samsung ml-1610
07:05
<ogra>
https://launchpad.net/~ogra/+branch/ltsp/feisty-ltsp-jetpipe
07:06
pull that bzr branch, and use the diff of the last two versions
07:06
its the netx generation print server for ltsp ... you need top copy the pieces in place manually, but it works
07:08
<antgel_>
i swear i just don't get all these new-fangled tools - whether it's ruby on rails on launchpad, the simplicity confuses me :)
07:09
s/on/or
07:09andresmujica has joined #ltsp
07:10
<ogra>
there is a link to the bazaar homepage on the LP page ... it has howtos
07:12cliebow_ has joined #ltsp
07:14
<antgel_>
i'll have a look - thanks
07:15vlt|afk is now known as vlt
07:15yopla has joined #ltsp
07:17yopla has left #ltsp
07:21
<antgel_>
ogra: when you say "use the diff of the last two versions", what do you mean? in my world, i use one version or another :)
07:21
<SiCk>
what exactly does ltsp-build-client do, anyone?
07:22
<antgel_>
SiCk: heh, it creates an ltsp install using your package manager
07:22
i say heh as i wasn't sure either
07:22
<SiCk>
ah
07:22
<ogra>
get the output of bzr diff -r455..457 for that branch
07:22
there was only one file added and three lines chnaged in the initscript of the ltsp client
07:23
<SiCk>
i'm hoping if i run that, it'll set my clients back to their defaults
07:23
after my kiosk booboo
07:23
<ogra>
so add that file and change these lines and it should even work to print on debian clients ;)
07:23
SiCk, rm -rf /opt/ltsp/i386 first
07:23
then you can rebuild
07:24
but why didnt your kiosk work ?
07:24
<SiCk>
first it was looking for a theme that didnt exist, got that sorted and it started saying it'd logged the machine out before 10 seconds
07:25
the machine was freezing up at that point
07:26
so i'll rebuild and try again
07:26
<ogra>
how much mem doe it have ?
07:26
*does
07:26
<SiCk>
128 i think
07:26
<ogra>
that should suffice
07:26
<SiCk>
but it booted linux before the kiosk thing
07:26slipttees|work is now known as slipttees
07:26
<SiCk>
yeah
07:27
<ogra>
did you add the users home4dir to the right variables, so it gets RW ?
07:27
<SiCk>
did everything that was in the directions... if it didnt mention it then probably not... haha
07:28
ill try it again after this rebuild anyway and see what happens
07:32
back in an hour everyone. back soon
07:33
<ogra>
make sure to have it in the copy_dirs variable in /opt/ltsp/i386/etc/default/ltsp-client-setup
07:33
as well as "/var/lib/gdm" needs to be in rw_dirs#
07:33
-#
07:34FernandoMM has joined #ltsp
07:35
<SiCk>
i'll talk to you later about it if you're around ogra :) thanks mate.
07:46meduxa has joined #ltsp
07:47andresmujica has left #ltsp
07:51slipttees has quit IRC
07:54RiXtEr has joined #ltsp
08:13
<antgel_>
ogra: okay, got the diff. just a case of copying jetpipe to usr/sbin and manpage to usr/man? where does start_printer go?
08:14pscheie has joined #ltsp
08:14
<pscheie>
morning all
08:15
<antgel_>
ogra: and when it's installed, is it just a case of configuring as per http://ltsp.mirrors.tds.net/pub/ltsp/docs/ltsp-4.1-en.html#AEN696?
08:17
ogra: and another thing. don't i need the ip address / hostname of the workstation in order to configure the print queue?
08:28etyack has joined #ltsp
08:31PMantis has joined #ltsp
08:32_gentgeen_ has quit IRC
08:32gentgeen__ has quit IRC
08:34stibs has joined #ltsp
08:37jammcq has quit IRC
08:38jammcq has joined #ltsp
08:38stibs has left #ltsp
08:38jammcq has quit IRC
08:38jammcq has joined #ltsp
08:38
<jammcq>
g'morning
08:39
<pscheie>
hey jammcq
08:39
<etyack>
morning
08:40
<pscheie>
jammcq: any idea why shutting down an ipaq via ltspinfo would prevent the ipaq from responding to a wake-on-lan packet?
08:40gentgeen__ has joined #ltsp
08:40
<jammcq>
pscheie: there's various "shutdown" modes
08:40
<pscheie>
The ipaq wakes up if I've shut it down via its power switch, but not if shutdown via ltspinfo
08:41
Can I control those modes in ltspinfo?
08:42
apparently the switch mode leaves the NIC in wol mode
08:42
<jammcq>
umm
08:42
it's been a long time since I looked at that
08:42
<pscheie>
I've read elsewhere about people trying to get the kernel to leave the nic in wol-aware mode
08:42
don't know much more at this point
08:43
what does ltspinfo -s do exactly?
08:44
<jammcq>
it does a '/sbin/init 0'
08:44
<pscheie>
hmm...
08:44jcaceres has joined #ltsp
08:45
<jammcq>
runlevel 0 does: /etc/rc.shutdown
08:45
which does a: /sbin/haltsys
08:45Gadi has joined #ltsp
08:45
<jcaceres>
hello guys, i have a question, i've seen that when a terminal loose conection with the server it starts obcesing trying to get conecter to the server againg, is it posible to me the terminal take another action?
08:46Avatara has quit IRC
08:47
<jcaceres>
i mean beacuse i have to servers and i would like to make the terminal conects to the other server
08:47
<Gadi>
jcaceres: just for X or for NFS as well?
08:47
if, just for X, there is some X load balancing code on the wiki
08:48
you can use that to modify startx
08:48
http://wiki.ltsp.org/twiki/bin/view/Ltsp/WorkInProgress#X_Load_Balancing
08:49
<jcaceres>
i have two servers in the same lan and some of the terminals conect to one or another server ramdomly, but those are identicals servers
08:50
i know that it's needed to reboot the terminal to make a nother nfs conection, so i would like to know if it's posible to make that happen
08:50Avatara has joined #ltsp
08:51
<jammcq>
jcaceres: if you've booted a thin client, and mounted it's root filesystem via NFS, and that NFS server goes away, you are pretty much stuck, until either that server comes back, or you reboot the server
08:52
<jcaceres>
instead of trying to connect to the same server again i would like the terminal reboots it's self and get the dhcp offer from the other server
08:56
so, is it possible to program the thin client to take other actions?
08:56monteslu has joined #ltsp
08:57
<jcaceres>
jammcq, with pxe i load in to mamommry of a terminal a small linux, is that correct?, can i modify that small limux to take other actions?
08:58
<jammcq>
no, that's not correct
08:58
you load a kernel and an initramfs
08:58
<g333k_work>
hi, what jcaceres wants to know is if the clients could reboot itself when the server goes away
08:58ogra_ has joined #ltsp
08:58
<jammcq>
which then does a NFS mount to get the real root filesystem
08:59
<Gadi>
jcaceres: why not just edit "startx" such that the user has to hit a key within a certain amount of time to reconnect after X dies, otherwise the terminal reboots
08:59
<jammcq>
and the initramfs is freed up
08:59
<Gadi>
that should *still* work even when NFS drops, since startx will be in RAM
08:59ogra has quit IRC
09:05
<jammcq>
Gadi: hmm, not likely. startx may still be in ram, but it's a shell script, and it's gonna call other commands that may or may not be in ram
09:05
<Gadi>
all you would need is bash which is already in RAM
09:07
<jammcq>
maybe i don't know what you are trying to do
09:08vlt is now known as vlt|afk
09:11
<jcaceres>
Gadi, in my experince, whe nfs goes out i can do nothing in the terminal, i do not have even a bash
09:11
<Gadi>
you would still have the "startx" shell
09:13mistik1 has quit IRC
09:14
<Gadi>
jcaceres: try adding these lines to the end of startx:
09:14
TMOUT=5
09:14
read restartx && echo "Restarting X..." && exit 0
09:14
shutdown -r now
09:15
<jcaceres>
u mean "/opt/ltsp/i386/etc/screen.d/startx"?
09:15
<Gadi>
right
09:15
(and on a test server, please)
09:16
(TMOUT can be made longer, too, in practice)
09:16
5 seconds may be too short
09:17
also, you *may* need to change the first line of startx to: #!/bin/bash
09:17
I'm not sure if TMOUT is a "bash" thing or a "sh" thing
09:17
<jcaceres>
hummm, ok, but to execute shutdown wouldn't it need to have the shoulddown script?
09:17
<Gadi>
I think shutdown does exist
09:17
oh
09:17
right
09:18
because of NFS
09:18
duh
09:18
<jcaceres>
shutdown exist ut in the server
09:18
exactly
09:19
so, what is exactly what remains in the terminal that can be modified to reboot the terminal
09:20
<Gadi>
not much
09:21
<jammcq>
you need a ram-based os on the thin client
09:21
that's not what ltsp is
09:22
<Gadi>
or a statically compiled shutdown command that can be copied to /tmp when the thin client boots up
09:22
<pscheie>
could one build a module that is loaded as an option that does this?
09:22
<jcaceres>
jammcq, i have some doub's about what u said aboy the kernel and initramfs
09:22
<jammcq>
doubts?
09:22
<Gadi>
questions
09:22
<jammcq>
tell me more
09:22
<Gadi>
jcaceres: brazillian?
09:23
jammcq: doubts = "questions"
09:23
<jammcq>
Gadi: I know what 'doubts' means. i'm wondering what his 'doubts' are :)
09:23
<Gadi>
ah, ok
09:23
just clarifying ;)
09:23* jammcq has been around the block once or twice
09:23
<jcaceres>
i dont exaclt udnertadn what the kernel and the initramfs doesm where can i get some documentation about it?
09:23
<Gadi>
I know. I've been the one chasing you ;)
09:23
<jcaceres>
Gadi, peruvian
09:23monteslu has quit IRC
09:24
<jammcq>
ah, peruvian, that's not to far from brazil :)
09:24
<jcaceres>
no, we are good neighbors,
09:24
<cliebow_>
jammcq: i am looking over windows dhcp response to ibook..i have next server ip address as my ltsp server..but server hostname comes up "not given"..think this is significant?
09:25
<jammcq>
hostname of the server doesn't sound important, but with windows dhcp, who knows
09:25
<pscheie>
Gadi: Could your oss-alsa sound package break a previously working client's sound?
09:25
I dusted off an old client with an ISA SB card last night
09:26
used to work great pre-ltsp 4.2
09:26
<cliebow_>
bootfilrname is correct..almost seems that the arp resolution is what is borking it
09:26
<Gadi>
pscheie: you may need to specify the correct alsa module
09:26
<pscheie>
but I got all kinds of ALSA errors when it booted up
09:26
syntax?
09:27
<jcaceres>
jammcq, where can i gat info about that kernel that is loaded, and initramfs?
09:27sbalneav has joined #ltsp
09:27
<pscheie>
OTOH, when I put in a cheap 'We Rook You' brand PCI sound card, which had never worked previously, it worked just fine
09:28
<jammcq>
Scotty !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
09:28
<Gadi>
pscheie: are you specifying SMODULE_01?
09:28
<pscheie>
no
09:28
didn't try that
09:28
<sbalneav>
Morning all!
09:29
<Gadi>
pscheie: you may need to specify the right sound module
09:29
like you did with the maestro3 cards
09:29
and then let me know
09:29
I'll update the list
09:29
<cliebow_>
ogra_:any feel for significance of arp resolution for macintosh netboot?
09:29
<pscheie>
correction: yes, I did specify the SMODULE_01 = "sb ..."
09:29
<Gadi>
if you need "sb", use "snd-sb8" or "snd-sb16"
09:30
<pscheie>
had to, since the card is ISA
09:30
<jammcq>
cliebow_: arp resolution has to work, no getting around that
09:30
<Gadi>
(8-bit or 16-bit)
09:30
<jammcq>
i'm wondering why you think it's not working
09:30
<pscheie>
16
09:30
<Gadi>
so, use "snd-sb16"
09:30
instead of "sb"
09:30
<pscheie>
what's the diff, as far as module loaded?
09:30MoL0ToV has quit IRC
09:31
<Gadi>
("sb" = OSS, "snd-sb*" = ALSA)
09:31
<pscheie>
oh, sorry, missed what you just wrote
09:31
okay, I'll try it tonight. Thanks.
09:31
I suppose if I'd looked at the
09:31
<antgel_>
what do i set in lts.conf for uk keymap? i've looked but me and ltsp documentation don't get on so well :)
09:32
<cliebow_>
looking at the packets i see no arp is-at packets..from any machjine..at least in the few seconds i captured
09:32
<pscheie>
audiolist-alsa file, I'd have seen that (?)
09:32
<jammcq>
cliebow_: how are you capturing the packets?
09:32
<cliebow_>
wireshark on a hub
09:33
<jammcq>
with a filter?
09:33
or no filter
09:33
<cliebow_>
with ibook and my aantichrist laptop..no filter
09:33
<jammcq>
are you seeing the 'who has' arp requests?
09:33
<pscheie>
Actually, looking at audiolist-alsa, I don't see any mention of 'SoundBlaster'
09:33
<jcaceres>
cliebow, some card cannnot capture some packets in wireshark, i am not sure why
09:34
<Gadi>
pscheie: "SoundBlaster" is kind of a catch-all generic
09:34
<cliebow_>
who has from a bunch of diff machines
09:34
<jammcq>
but no arp replies?
09:34
<pscheie>
right, but what should one look for when one has an actual SB (TM) card?
09:34
<cliebow_>
jcaceres:when netbooted from linux all is great..dont think it can be the card
09:34
<pscheie>
I suppose even then 'it depends' because they probably change chipsets
09:35
between models
09:35
<cliebow_>
no replies..on the network..but i should let it run a while to be sure
09:35
<Gadi>
pscheie: could be. When you have a chance, at a shell on the terminal, try and get the PCI id
09:36
<pscheie>
If it's ISA, is there a PCI id?
09:36
<Gadi>
ah, true
09:36
good point
09:36* Gadi keeps swinging and missing today
09:36
<pscheie>
Like I said, the PCI card I tossed in there worked right out of the box, and it had never worked before
09:36* Gadi looks around for a pinch hitter
09:36
<cliebow_>
need a longer vine Gadi 8~)
09:37* pscheie pats Gadi on the back in thanks for that one
09:37
<Gadi>
:)
09:38
<pscheie>
now my box of stubborn PCI audio cards is empty, while my box of ISA cards is overflowing
09:38
should probably just pitch the ISA cards
09:39
This dusty old client--P166, no drives, just a DisklessWorkstations NIC w/bootprom is good for demos, showing off old equip that's lihgtning fast
09:39
<cliebow_>
i see no is at packets on the network after ohh 45 seconds
09:40
ohh i see one..
09:40
from the managed switch
09:43andresmujica has joined #ltsp
09:43msinhore has quit IRC
09:43msinhore has joined #ltsp
09:50mistik1 has joined #ltsp
09:53tiagovaz has joined #ltsp
09:59efra has joined #ltsp
09:59
<efra>
Morning everybody
10:00andresmujica has left #ltsp
10:02
<cliebow_>
efra:mornings
10:07antgel__ has joined #ltsp
10:07andresmujica has joined #ltsp
10:08antgel_ has quit IRC
10:11bricode has joined #ltsp
10:13mistik1 has quit IRC
10:17etyack has quit IRC
10:17msinhore has quit IRC
10:19msinhore has joined #ltsp
10:22vanya has quit IRC
10:38slipttees has joined #ltsp
10:43mistik1 has joined #ltsp
11:13vagrantc has joined #ltsp
11:17Avatara has quit IRC
11:18antgel__ has quit IRC
11:33monteslu has joined #ltsp
11:40sepski has joined #ltsp
11:50jbrett has quit IRC
11:50jbrett has joined #ltsp
11:56msinhore has quit IRC
11:58monteslu has quit IRC
12:12meduxa has quit IRC
12:45irule has joined #ltsp
12:59RiXtEr has quit IRC
13:07Blinny has joined #ltsp
13:14
<Blinny>
Hi - I followed the directions at http://dipe.de/tipps/ltsp_nvidia to get my nvidia hardware acceleration going, however I'm having trouble combining this approach with fixing my ImPS/2 usbmouse and its scrollwheel. If I custom-define a xorg configuration, I can get the mouse to work but not the module or x4_module for hardware acceleration.
13:14
Unfortunately I'm not sure which directive is preventing the scrollwheel from functioning correctly.. (Maybe Input Device CorePointer or AlwaysCore?)
13:16
I had thought it was ZAxisMapping, but with the nVidia method, those directions show up in the (strangely, two) Mouse sections in /tmp/XF86Config.1 on the client.
13:17irule has quit IRC
13:18SiCk has quit IRC
13:21bobby_C has joined #ltsp
13:22
<vagrantc>
anyone have opinions, and ideally links to more info, regarding nfs over tcp vs. nfs over udp ?
13:30plamengr has joined #ltsp
13:30plamengr has left #ltsp
13:30Blinny has quit IRC
13:48cliebow_ has quit IRC
13:55sepski has quit IRC
14:08Blinny has joined #ltsp
14:09craigbass1976 has joined #ltsp
14:10
<Blinny>
I have a special xorg configuration file in /tftpboot/lts/ltsroot/etc -- in lts.conf I specify it with XF86CONFIG_FILE = xorg_configuration_file -- when the client terminal boots it says "xorg_configuration_file not found!" -- is there a special permission setting or path I should be giving? lts.conf.readme says to just put it in that directory and provide the filename.
14:10
<vagrantc>
Blinny: full path
14:10
<craigbass1976>
Can someone give me a brief rundown of what you need to get ltsp up and running? I just got off the phone with a school IT guy and he's having a bunch of trouble. I got, over the phone, what his error was, but the syntax may be off. pxe-> eb no pxe err
14:11
I'd never heard of any pxe being involved, but I have never tried ltsp either...
14:11
<pscheie>
craigbass1976: clients can boot using pxe or etherboot
14:12
<craigbass1976>
Is there a walkthrough anywhere for getting it going from start to finish?
14:13
<vagrantc>
craigbass1976: what distro?
14:13
<Blinny>
vagrantc: Lemme check it. Thanks.
14:14
<pscheie>
There's the ltsp wiki: http://wiki.ltsp.org/twiki/bin/view/Ltsp/LTSP-42#Installation_of_LTSP_4_2
14:14Blinny has quit IRC
14:14
<craigbass1976>
Any. Right now I guess he's running k12 ltsp 6 which I believe is fedora-based
14:15
<pscheie>
yes, k12ltsp is fc-based, latest version is on fc6
14:15
Installation is dead simple
14:15
<craigbass1976>
It jsut comes with the install discs?
14:15
<pscheie>
yes
14:15
<craigbass1976>
Wonder why he's having trouble...
14:15
<pscheie>
During installation, it's one of two installation choices, and it's selected by default
14:15
To mess it up, you have to really try
14:15
<craigbass1976>
is etherboot easier to set up than pxe?
14:16
<pscheie>
There's nothing really to setup
14:16
<vagrantc>
pxe is actually easier, i would say.
14:16
<craigbass1976>
I'm still running FC5. Is it available for my distro?
14:16
<vagrantc>
but not by a lot.
14:16
<pscheie>
sure, LTSP can be added to most distros
14:17
or you can still download the k12LTSP 5 which is FC5
14:17
<vagrantc>
could be an old PXE implementation on your thin-clients
14:17
some of the older network cards were really buggy
14:17
<craigbass1976>
I'm worried about rpm hell though, checking yum repos...
14:17
<pscheie>
How is he booting the clients?
14:17
Net boot setting in bios? etherboot floppy?
14:17
<craigbass1976>
I'm not sure.
14:18
I think he might have tried it both ways
14:18
<pscheie>
etherboot floppy is pretty easy
14:18Blinny has joined #ltsp
14:18
<pscheie>
what exactly does he see?
14:18
<Blinny>
vagrantc: Yeah that didn't work either. It still says "File not found!"
14:18
<pscheie>
Is the client getting an IP address? Is it downloading a kernel?
14:18
<vagrantc>
Blinny: full path, relative to /opt/ltsp/i386 ?
14:19
<Blinny>
vagrantc: Wouldn't the full path be relative to the terminal's root?
14:19
<vagrantc>
Blinny: yeah.
14:19
<Blinny>
vagrantc: The lts.conf says to put this file in /tftpboot/lts/ltsroot/etc/
14:19
<pscheie>
knowing where it's failing will make fixing it much easier
14:19
<craigbass1976>
As far as I know, only the error I pasted, but I didn't talk very long with him. He also said the server was giving out addresses on the wrong interface
14:19
No idea. I'll set it up at home then talk to him again.
14:19
<vagrantc>
Blinny: hm... i'm not real familiar with ltsp 4.x
14:19
<craigbass1976>
Do you need a honking server for just one client?
14:20
<Blinny>
vagrantc: (unless I should create /opt/ltsp/i386/tftpboot...)
14:20
<pscheie>
no
14:20
<Blinny>
craigbass1976: No.
14:20
<craigbass1976>
Ok.
14:20
Thanks folks.
14:20
<pscheie>
I'm using a P3 700mhz laptop for testing 3 clients
14:20craigbass1976 has quit IRC
14:21
<pscheie>
vagrantc: do some NICs come with PXE booting abilities?
14:21
<vagrantc>
pscheie: yes, any recent NIC will have PXE built-in.
14:21
s,any,most,g
14:22
<pscheie>
even cheapo Realtek 8139 cards?
14:22
<vagrantc>
recent, as in the last 5-7 years or so.
14:22* vagrantc isn't sure.
14:22* pscheie has never bothered to read the docs with 8139 cards
14:24
<Blinny>
Aergh.
14:25
Dontchya need a recent BIOS to do hands-off no-floppy booting though?
14:27
Where is the X configuration file found for a typical, no-options-specified booting client?
14:27
<pscheie>
anyone have recommendations on a good gigabit card for use in a server?
14:28
I've heard Intels don't tax the CPU as much as, say, Realtek based cards
14:29
<Blinny>
pscheie: I've used both Broadcom NBM5708 and Intel's 82571EB cards
14:30
ack
14:30
:s;NBM;BCM
14:30Blinny has left #ltsp
14:31
<bricode>
I've got PXE on a Realtek 8100.
14:32Blinny has joined #ltsp
14:32
<Blinny>
oops
14:40
<bricode>
vagrantc: Are you using the NFS for fat clients?
14:41
<vagrantc>
bricode: i've played with doing it a little, but not for more than 1-2 machines yet.
14:42
<bricode>
vagrantc: I've been playing with both setups as well. I've noticed a few odd things with the fat client setup.
14:43nofxx has joined #ltsp
14:43
<vagrantc>
bricode: i've only experiemented with anonymous logins- no network authentication or home directory mounting
14:43
<nofxx>
Hello!! xD I'm using ubuntu 6.10 with ltsp... when some clients with a ecs mb semprom 64 AM2 tries to connect I get a ACPI: Getting cpuindex acpiid 0x1 .... then Kernel panic... and the thin client won't boot..... I don't have idea what it is... please help
14:44cliebow_ has joined #ltsp
14:45
<bricode>
vagrantc: I did some network monitoring. It takes 86 MB from boot to login screen in thin client mode.
14:46
<nofxx>
does ubuntu alternate comes with ltsp5 ? should be better for me ? booting fat clients thu PXE
14:46
14:47
<bricode>
vagrantc: Whoops. Wrong results.
14:48
vagrantc: Fat client setup (Edubuntu w/Gnome) 70 MB from boot to login screen, 115 MB from boot to Desktop (after login).
14:49
vagrantc: Thin client (Edgy/Gnome) start to desktop: 85.6 MB.
14:49
<Blinny>
nofxx: Have you tried passing "acpi=off noacpi" to the client via an option 128 setting in dhcpd.conf ?
14:49
<nofxx>
Blinny: gonna try it now!
14:49
<bricode>
vagrantc: It's odd because I woule have thought the thin client version would be much better on transfer.
14:49tiagovaz has quit IRC
14:50
<Blinny>
nofxx: Read here: http://wiki.ltsp.org/twiki/bin/view/Ltsp/KernelOptions
14:50
<bricode>
vagrantc: Also noticed that fat client uses ~30kbit/s to do NFS maintenance...not really sure what it's doing, but might have scalability issues.
14:51
<Blinny>
wait I don't think you want noacpi.. I think that's for noapic (;
14:51
damn acronyms...
14:52
<nofxx>
Blinny: ty for the help man! ...hmm it reads ACPI.. adv conf and power interface....hehe from wikipedia
14:53
<cliebow_>
nofxx: add ltsp5 with apt-get install ltsp-server-standalone
14:53
<Blinny>
nofxx: APIC == 'advanced programmable interrupt controller"
14:54
<nofxx>
cliebow: ty, gonna try...
14:54
<vagrantc>
bricode: it bet a huge portion of the thin-client data transfer is LDM.
14:54
<nofxx>
Blinny: damn acronyms... xD
14:55
gonna try to fix with my current and then make another install for the server with ltsp 5 to compare
14:55
<bricode>
vagrantc: To run the xorg server locally?
14:56
<nofxx>
Blinny: i need to change /tftpboot/lts/2.4.26-ltsp-2/pxelinux.cfg/default so... right ?
14:56
hhehe.... noacpi=true ?? xD
14:57
<vagrantc>
bricode: no- that will be about the same, however, when using LDM, i bet it loads more files than GDM... ldm is written in python with glade, and reads a lot of files....
14:57
<Blinny>
nofxx: Yeah, I think you could do it that way. The way I know of is editing dhcpd.conf with 'option' flags.
14:57
<vagrantc>
bricode: compare it to a thin-client boot configured to use XDMCP instead of LDM ...
14:58
<Blinny>
nofxx: And you want to use "acpi=off"
14:58
<bricode>
vagrantc: Good point.
14:59
<nofxx>
Blinny: i'm a lil lost... using this common mb boot thu lan I'm using etherboot pxe?
14:59* vagrantc wonders if there is much optimization that could be done for ldm ...
14:59
<nofxx>
*etherboot or pxe
14:59
<Blinny>
nofxx: I have no idea. Which are you using?
14:59
nofxx: Why not just put it in dhcpd.conf so it covers both bases?
14:59
<vagrantc>
there aren't many systems which have etherboot built in
15:00
i suspect it's pxe
15:00
<nofxx>
Blinny: more then perfect!
15:00
<bricode>
Does anyone have a decent link to the current state of Local Apps?
15:00
<vagrantc>
bricode: for ltsp 5 ?
15:00
<bricode>
vagrantc: Yeah. In particular under Ubuntu.
15:01efra has quit IRC
15:01
<nofxx>
Blinny: option option-128 e4:45:74:68:00:00;
15:01
option option-129 "acpi=off"; rock on?
15:01
<vagrantc>
bricode: i don't think there's been much development. it's dependent on a lot of the same stuff that the FAT client stuff is waiting on (network authentication, primarily, i think)
15:02
<bricode>
vagrantc: Yeah, I was confused when I first tried the fat client build. It was like it's own little install in /opt/ltsp
15:02
<Blinny>
nofxx: Yes.
15:02
<vagrantc>
bricode: yes, that's the whole point.
15:03
bricode: to make better use of high-end clients
15:03
bricode: and reduce the load on the server ...
15:03
<bricode>
vagrantc: Are people thinking of using it as a ro system so that multiple clients can use it at the same time?
15:03
<vagrantc>
bricode: yes.
15:04
<bricode>
vagrantc: and do time sensitive applications.
15:04
<vagrantc>
bricode: that is, as far as i know, the only way people are intending to use it.
15:04
bricode: right, it's much easier to do media-intensive applications locally ...
15:04
<bricode>
vagrantc: and mounting /home as r/w using some authentication scheme?
15:04
<Blinny>
nofxx: Be sure to restart dhcpd so that the values take.
15:04
<bricode>
vagrantc: Yeah, video and voip are much better in the fat client setup.
15:05
<vagrantc>
bricode: probably ...
15:09
<Blinny>
nofxx: I've gotta go. If that doesn't work, then try setting "acpi=off" in your 'default' file. (Mine is at /tftpboot/lts/pxe/pxelinux.cfg)
15:09
G'luck.
15:09Blinny has quit IRC
15:13cliebow_ has quit IRC
15:14J45p3r_ has joined #ltsp
15:14markit has joined #ltsp
15:16bronze has quit IRC
15:17andresmujica has quit IRC
15:18jammcq has quit IRC
15:25psyco-obiwan has quit IRC
15:30klausade has quit IRC
15:31psyco-obiwan has joined #ltsp
15:33andresmujica has joined #ltsp
15:39J45p3r_ has quit IRC
15:56
<PMantis>
Anyone here that can help work some sed magic?
15:57
echo /var/spool/asterisk/monitor/q8008--1170090472.305-out.WAV | sed s/^.*\(...\)$/\1/
15:57
= no joy
15:57
Expecting: WAV (only print the last 3 letters)
15:57
Shouldn't be this hard!!
16:03
<sbalneav>
you need:
16:03
sed -e "s/^.*\(...\)$/\1/"
16:03
/usr/legal/home/aicra/.imap/Junk/new# echo /var/spool/asterisk/monitor/q8008--1170090472.305-out.WAV | sed -e "s/^.*\(...\)$/\1/"
16:03
WAV
16:04
<nofxx>
hum..i'm trying to add the "option option-128" acpi=off... but it says "option-128 unkown option"
16:04
<PMantis>
Ugh
16:04
<sbalneav>
nofxx: Are you booting etherboot?
16:05
Or PXE?
16:05
<PMantis>
sbalneav, Thanks! So -e = actually process regex, and not whatever you feel like?
16:05
:)
16:05
<nofxx>
sbalneav: im trying to understand that too..hehe.. I'm booting from a ecs nforce motherboard... with the build in lan boot
16:06
built-in
16:06
<sbalneav>
nofxx: It's probably pxe
16:06
<nofxx>
sbalneav: cool... the problem is im having a "acpi cpuiindex 0x1" then in the next line "Kernel panic" and the client dosen't boot
16:07
<sbalneav>
take a look at the pxelinux.cfg/default file in your tftp area.
16:07
<nofxx>
on a older machine here it boots sucesfully... its a nforce2 mb
16:07
sbalneav: ok..let me see
16:11
sbalneav: the file has only 1 line "DEFAULT vmlinuz ro initrd=initrd.img quiet splash"
16:11
<sbalneav>
Add the "noacpi" option before the "splash"
16:12
<nofxx>
gotcha.. ""DEFAULT vmlinuz ro initrd=initrd.img quiet noacpi splash"
16:12
need to restart it?
16:13
<sbalneav>
You'll need to reboot the client.
16:13
<nofxx>
yup.. restarted it... same error...... I mean the server
16:15
<sbalneav>
The SERVER's getting this error?
16:15
Or the client?
16:15
<nofxx>
the client
16:15
"ACPI: Getting cpuindex for acpiid 0x1"
16:15
next line:
16:15
Kernel Panic - not sync.....
16:16
<sbalneav>
I'd say the kernel doesn't like that mobo on the client.
16:17
<nofxx>
sbalneav: wow dude.. thats bad... there are 40 computers! the same mb hhahaha
16:18
i tryed the option of ACPI in the bios.... there is not a DISABLE>. heheh
16:18
there is S1, S3 and S1&S3
16:20
too hard to try another kernel ?
16:27
<vagrantc>
nofxx: try "acpi=no" instead of "noacpi"
16:27
er...
16:27
acpi=off
16:28
<nofxx>
cool...let's see.. ty
16:30
vagrantc: now the acpi error is gone...hum... but the Kernel Panic is there....
16:30
so wasn't that causing the kernel panic.... sh**
16:31
26.116630] Kernel panic - not syncing: Attempted to kill int!
16:31
26.116668]
16:31
blank like the last one...
16:31
*blank line
16:33
*kill init
16:37sbalneav has quit IRC
16:40
<nofxx>
humm..someone told me here earlier, but no history here... what's the command to upgrade to ltsp5 ? i'm on ubuntu
16:40
maybe.. who knows... 5 get support for this mobo
16:48andresmujica has left #ltsp
16:59bobby_C has quit IRC
17:02bricode has quit IRC
17:04
<mistik1>
anyone around?
17:05
I have a network question, If I wanted to probe for an unused subnet on the network what would be the best way to go about it?
17:14J45p3r has joined #ltsp
17:22
<cliebow>
mistik1: got me..you r subnet mask is?
17:26markit has left #ltsp
17:27
<nofxx>
there are support for more mobos on v5?
17:27
<cliebow>
jammcq: can you redirect my mail for me...wife wants to switch isps again
17:27
v5?
17:28
<nofxx>
I have a Kernel panic: sync...... and a blank like after.... just it... dont know how to debug it
17:28
ltsp v5
17:28
5.0
17:28
dunno
17:28
*blank line
17:28
<cliebow>
ahhh..it kernel panics just afger kernel loads?
17:29
<nofxx>
yup... after the network boot.. found the server.. download somthing...
17:29
screen goes blank
17:29
then...error
17:29
<cliebow>
so the initramfs isnt being loaded?what kernel are you using?
17:30
<nofxx>
cliebow: sorry man.. I'm new.. but I get there... hehe... dont know about ititramfs... let me see...... how to check the kernel?
17:30
<cliebow>
like grep filename /etc/dhcpd.conf..assuming that is where dhcpd.conf is
17:30
<nofxx>
the client pc is a ecs nforce motherboard... for amd socket am2
17:31
<cliebow>
dhcpd.conf should be pointing to some kernel
17:31
<nofxx>
in a nforce2 mobo it runs perfect... checking that.. 2 secs
17:32
<cliebow>
../lts/vmlinuz--->
17:34
some mobos just suck..ntw
17:34Faithful has joined #ltsp
17:34
<nofxx>
i have vmlinuz... and vmlinuz-2.6.17.10-386
17:35
but that is not on /etc/dhcp or /etc/ltsp/dhcp or /pxelinux.cfg/default xD
17:36
this guy bought 40 pcs with the same mobo for his cyber cafe...
17:36
oh my...
17:36
hahah
17:37
<cliebow>
where is dhcpd.conf?anyway..if you look in like /tftpboot/lts do you have vmlinuz-2.6.16.1-ltsp-2?
17:38Sp0oKeR has quit IRC
17:38
<nofxx>
dhcpd.conf on /etc/ nothing on it
17:38
and /etc/ltsp/ ... its working.. i guess
17:39andresmujica has joined #ltsp
17:39
<nofxx>
inside /tftpboot/ltsp/i386/ i have vmlinuz-2.6.17.10.-386 too
17:39
not vmlinuz-2.6.16.1-ltsp-2
17:41
sorry, dhcpd is in /etc/dhcp3/ not only /etc/
17:41
.conf
17:41
i'm on ubuntu 6.10, btw
17:42
<cliebow>
ohhh..is this ubuntus ltsp or ltsp4.3 installed from ltspadmin?
17:42
must be 4.2
17:42
<nofxx>
how to check ? dont have this executable
17:43
<cliebow>
or is it all mixed in together?
17:43
you installed with ltsp-server-standalone
17:44
<nofxx>
yes
17:44
downloaded a ton of things
17:45
<cliebow>
you/ll notisw vmlinuz is a simlink to to vmlinuz-2.6-->
17:45
<nofxx>
true
17:46
<cliebow>
there is also a file named initrd there too even though it really is an initramfs
17:46
<nofxx>
yup! .img
17:46
<cliebow>
you are pxe booting these terminals?
17:47
<nofxx>
i guess so... I'm using the built in network boot
17:47
its a nforce C51PV chipset
17:47
onboard lan
17:47
<cliebow>
it seems like for some reason the initrd is not being recognized
17:48
ogra:feel free to smack me up side of the head anytime
17:48
<nofxx>
a nforce2 mobo worked... have I said that ?heh
17:48
<cliebow>
i need ot look on my lappie.bbiab
17:49
<nofxx>
ok!
17:55cliebow_ has joined #ltsp
17:56
<nofxx>
the last words before the panic are:
17:56
Loading vmlinuz.........
17:56
Loading initrd.img..............
17:56
Ready.
17:56
<cliebow_>
nofxx:have you editted /var//lib/tftpboot/ltsp/i386/pxelinux.cfg/default?
17:57
<nofxx>
only to place "acpi=off" there
17:57
its one line.. let me see
17:57
"DEFAULT vmlinuz ro initrd=initrd.img quiet noacpi splash"
17:58
sorry
17:58
"DEFAULT vmlinuz ro initrd=initrd.img quiet acpi=off splash"
17:59
<cliebow_>
wouldnt work before the dit either huh
17:59
wouldnt work before the edit either huh
17:59
<nofxx>
without the no acpi it showed something like "ACPI: getting cpuindex 0x1"
17:59
and the panic
17:59
now only the panic... heheh
18:04
my laptop just booted perfect too!!! godam*&*&* this mobo!
18:04
<cliebow_>
want to post all you know about the mobo..numbers..model?
18:05
Gigabyte GA-K8N51GMF-9??
18:05
<nofxx>
sure.. ECS C51GM-M / northbridge nvidia C51PV/G / southbridge MCP51/G
18:05
its with a semprom 64...am2
18:07
wow man... this ltsp thing is really awesome.... perfect on the lap....
18:08
<cliebow_>
that is the client?? a 64 bit client?
18:08
<nofxx>
yes... the guy want to save the hd money
18:09
and later put hd and vga to play games
18:10
oh my.... you can't boot 64 bits?
18:11
<cliebow_>
you have 40 64 bit clients? holy..this sounds.. like a ? for ogra..i dont know if the current kernel will do it.perhaps yo can use the generic kernel..which has smp support..it isd out of my keagur..
18:12
<vagrantc>
is the server 64 bit?
18:12
<nofxx>
40 clients, 4 servers, wasn't me who tought about this setup.. heheh.. just appeared here
18:12
yes
18:12
I was thinking about using ubuntu server 64... should be better?
18:13
<cliebow_>
use the 64 bit server kernel?
18:13
what kernel is runing the server?
18:13
/boot/grub/menu.lst shouls sat
18:14
<nofxx>
the only way I remember is to wait for the screensaver shows it to me.. xDD
18:14
<mistik1>
you should be able to boot a 64bit proc with a 32bit kernel no probs
18:14
<nofxx>
kiddin.. sorry.. what is the command ?
18:14
<cliebow_>
mistiki1: seemslike the initrd wont load
18:15
<mistik1>
uname
18:15
<cliebow_>
nofxx:uname -r..sorry senior moment here..
18:15
<nofxx>
2.6.17-10 generic
18:16
<cliebow_>
i defer to mistik1
18:18
i am out of my league nsfxx...
18:18
<mistik1>
If this is the Ubuntu stuff its best to ask them guys how to work that out
18:19
<nofxx>
ok...gonna try my luck there.... ty guys!!
18:20
murphy's law 88797: when you buy more then 39 units of the same hardware, it'll not work for you.
18:33
humm.... in my daemon.log ... i have
18:33
"in.tftpd[5067]: tftp: client does not accept options"
18:34
could be related?
18:35FernandoMM has quit IRC
19:02
<cliebow>
hmmm. maybe see what tftp server you have?? dpkg -L|grep tftp..somethinmg likr that
19:06
<nofxx>
ok.. i'm givin up of using ubuntu... what is the best distro to use ltsp ??
19:13Gadi has left #ltsp
19:17jammcq has joined #ltsp
19:17
<jammcq>
hello
19:18Faithful has quit IRC
19:18Faithful has joined #ltsp
19:29andresmujica has left #ltsp
19:48bricode has joined #ltsp
19:55Jfrost has joined #ltsp
19:55Jfrost has left #ltsp
20:01andresmujica has joined #ltsp
20:05PMantis has quit IRC
20:09Aaron|Feldman has joined #ltsp
20:09J45p3r has quit IRC
20:30andresmujica has left #ltsp
20:40
<vagrantc>
!bestltspdistro
20:40
<ltspbot`>
vagrantc: "bestltspdistro" is whatever you prefer
20:40
<vagrantc>
nofxx: got that?
20:40
<bricode>
cute
20:41
<nofxx>
vagrantc: hi man.... no.. no go... acpi is off.. the acpi error goes away
20:41
but still the kernel panic
20:41
i dont know how to debug it...
20:41
<vagrantc>
nofxx: i was asking ltspbot about which is the best ltsp distro ...
20:42
<nofxx>
ahhh..huahauh sorry...
20:42
xD
20:42
<vagrantc>
nofxx: ok, so you're currently running ubuntu ...
20:42
<nofxx>
yup.;;;; i386
20:42
<vagrantc>
are you loading via pxe or etherboot?
20:43
<nofxx>
pxe... its a ecs mobo..with a semprom 64 am2
20:43
<vagrantc>
is "quiet" in your boot arguments? like in pxelinux.cfg/default
20:43
<nofxx>
fat client without hard disk
20:43
yes
20:43
quiet acpi=off splash
20:43
<vagrantc>
remove it and see if it gives you any more useful information
20:43
<nofxx>
cool
20:45
booting..let's see
20:45
<vagrantc>
of course now, you may have information overload ... but ...
20:46
<nofxx>
yes.. i see....2 more lines before panic:
20:46
Capability LSM initialized
20:46
NET: Registered protocol family 17
20:46
Kernel panic....
20:46
xxxx] "blank line"
20:46
<vagrantc>
so, your server and all the thin clients are amd64 ?
20:47
<nofxx>
yes
20:47
<vagrantc>
have you installed amd64 binaries ?
20:47
or just the i386 version?
20:47
<nofxx>
nope.. the server is i386
20:48
<vagrantc>
but the hardware could support 64 bit?
20:48
<nofxx>
i used the simple installer..never used ltsp.... ltsp-server-standalone i think....
20:48
yes.. it is running nice...
20:48
now that you are saying this, 32 bits pcs are booting.....
20:48
but i dont have abother 64 mobo to test here...
20:48
<vagrantc>
and the 64 bit ones aren;t ?
20:48
ok ...
20:48
<nofxx>
the server is running i386 nice, i mean
20:49
i was away from the linux world later... the 64 versions are working cool nowdays?
20:49
<vagrantc>
nofxx: you could build an amd64 LTSP environment, and then copy it to your i386 server ...
20:49
so i hear
20:50
<nofxx>
vagrantc: thats sounds cool... there is some tuto ?
20:50
or maybe its better I install ubuntu 64 ?
20:50
then the ltsp image will be 64 too ??
20:51
<vagrantc>
right, but you should (at least in theory) be able to build a 32 bit LTSP environment on a 64 bit server. it's trickier the other way around.
20:51
so you could have both a 64 bit and 32 bit environment ...
20:51
<nofxx>
wait.... running 32 easy to put 64 too... that's it ?
20:51
sorry
20:51
<vagrantc>
though really, the 32 bit environment should work for your 64 bit hardware ...
20:51
<nofxx>
vagrantc: so I heard.. xD
20:51
hehe
20:52
<vagrantc>
nofxx: well, you can have /opt/ltsp/i386 and /opt/ltsp/amd64 on the same server ...
20:52petre has joined #ltsp
20:52
<nofxx>
vagrantc: there is no way to debug this ? the daemon.log looks the same with a succesful boot
20:52
<vagrantc>
nofxx: it's easier to build /opt/ltsp/i386 on a 64 bit server than it is to build /opt/ltsp/amd64 on a 32 bit server.
20:52
<nofxx>
ahh got it
20:53
gonna go 64 then....
20:53
<vagrantc>
but i have 0 experiences with amd64 architecture ...
20:53
it's all just theory to me.
20:57vlt|afk has quit IRC
20:59
<nofxx>
the panic comes after Net: Registered protocol.... its easy to search this boot script to what comes next?
20:59
<vagrantc>
and there's absolutely no more information?
20:59
<nofxx>
nope.. just a blank line after
20:59andresmujica has joined #ltsp
21:02sbalneav has joined #ltsp
21:02
<sbalneav>
Evening all
21:02* vagrantc wonders what ubuntu did with the prodigious quantities of kernel messages you should be getting
21:02
<jammcq>
Scotty !!!!!!!!!!!!!!!!!!!!!!!!!!!
21:02
<sbalneav>
Hey hey
21:02
<vagrantc>
sbalneav: howdy!
21:02
<sbalneav>
It ate 'em.
21:02
<jammcq>
yum yum
21:03
<sbalneav>
Hola!
21:03
<nofxx>
vagrantc: i found a log: NET: Registered protocol family 17
21:03
Using IPI Shortcut mode
21:03
<vagrantc>
nofxx: well, you might want to try making the server native 64 bit, and seeing if it still happens. but having both 64 bit and 32 bit LTSP environments will mean your DHCP configuration will have to be a little more complicated.
21:03
nofxx: doesn't really tell me much.
21:04
<nofxx>
heheh..ok
21:04
<vagrantc>
nofxx: can you find your tftp server's logs ? maybe in /var/log/syslog
21:04
<nofxx>
vagrantc: yes.. i understand the config part...
21:04
<vagrantc>
nofxx: grep -i tftp /var/log/syslog
21:04
<nofxx>
only 32 will fit.. and be easier...
21:04
yup... I have syslog opened here...
21:05
the logs looks the same for the sucessful and unsucessful ones
21:05
<vagrantc>
the main thing i'm wondering is if it's loading the initramfs image
21:05
<nofxx>
only error (on both): intftpd : tftp: client does not accept options"
21:06vlt|afk has joined #ltsp
21:06
<nofxx>
when you boot in the first screen it goes to "Ready."
21:06
vmlinuz.......................
21:06
<vagrantc>
nofxx: dpkg -l tftpd-hpa ?
21:06
<nofxx>
img(somehing)........................
21:06
Ready.
21:06
then blanks... and kernel panic
21:06
let me try the last command
21:07
<vagrantc>
hmmm.... weird. i thought amd64 was backwards compatible with i386 ...
21:08
<nofxx>
0.42-1ubuntu2
21:08
HPA tftp server
21:19
<bricode>
amd64 is a weird beast occasionally
21:23
<nofxx>
i can't find documentation about clients running 64....that is the point
21:24
think there are few 64 clients out there....he bought am2 semproms to later buy hard disks and vga for games...
21:29yanu_ has joined #ltsp
21:29petre has quit IRC
21:34Aaron|Feldman has left #ltsp
21:35kaos01 has joined #ltsp
21:38
<kaos01>
sorry about the question but where does one get the files to place in /tftpboot for ltsp-4.2 ?
21:40
<nofxx>
i'll try edubuntu 64.. just a question... i think its like kaos01.. you always have to download a whole new system ? it tooks hours on ubuntu... that ltsp-server-standalone
21:40yanu has quit IRC
21:41
<kaos01>
where do i get stuf flike vmlinuz-2.6.17.8-ltsp-1 from for ltsp-4.2 ?
21:43
anyone ?
22:00
<jammcq>
kaos01: run ltspadmin, that will download everything you need
22:01
<vagrantc>
nofxx: yes, it's building an entire ubuntu system using ubuntu packages.
22:02
nofxx: if you have a CD, you can mount it and point to the CD ... --mirror file:///path/to/mounted-cd
22:12andresmujica has left #ltsp
23:14mistik1 has quit IRC
23:14mistik1 has joined #ltsp
23:29
<kaos01>
ok, i nearly got ltsp-4.2 working one problem with local device support, ltsp-server-pkg-fedora-0.1-1.i386.rpm I cant install my machine is 64 bit hence have /usr/lib64/libfuse.so.2 and not /usr/lib/libfuse.so.2
23:30
anyone any ideas ?
23:37
<Megant__>
I guess that you need to get that 32-bit library from somewhere.
23:43
<kaos01>
mmm yum doesnt seem tobe of use
23:48sbalneav has quit IRC
23:58vagrantc has quit IRC