Main page
[00:21] kmin (n=kmin@netblock-68-183-26-145.dslextreme.com) joined #ltsp.
[00:22] [kmin] hi room
[00:22] [kmin] i need help
[00:23] Selveste1___ (n=Selveste@wnn72114.wireless.dtu.dk) joined #ltsp.
[00:23] [kmin] hi Selveste1___
[00:24] [Selveste1___] kmin: Morning :)
[00:25] [kmin] :D well it is midnight here but thanks
[00:25] [kmin] i need help
[00:25] [kmin] is this the right room for that kind of questions ?
[00:27] otavio (n=otavio@debian/developer/otavio) left irc: Read error: 110 (Connection timed out)
[00:31] [kmin] anyone?
[00:32] [kmin] it is strange that a room with this many people in it is so quiet :)
[00:39] [alkisg] !ask
[00:39] [ltspbot] alkisg: "ask" :: Don't ask to ask a question, simply ask it, and if someone knows the answer, they'll respond. Please hang around for at least 15 minutes after asking a question, as not everybody constantly monitors the channel.
[00:39] [alkisg] kmin: ^
[00:39] [kmin] ok here is the problem
[00:40] [kmin] i installed ubuntu ltsp server and i fixed the dhcp.conf in the /etc/ltsp
[00:40] [kmin] now when i try to boot from the network
[00:41] [kmin] i see the pxe loader get the image then i see the ubuntu logo
[00:41] [kmin] and after afew second i keep seeing something like this:
[00:41] [kmin] udhcpc[ ]: started
[00:42] [kmin] udhcpc[ ]: send requiest
[00:42] [kmin] udhcpc[] : no lease failing
[00:42] Barbosa (n=Barbosa@189.114.39.182) joined #ltsp.
[00:42] [kmin] and it keeps repeating it self for ever
[00:43] [kmin] i know the dhcp server is up and running
[00:43] [kmin] any idea?
[00:43] [alkisg] See the syslogs
[00:44] otavio (n=otavio@debian/developer/otavio) joined #ltsp.
[00:44] [kmin] what should i look for in it?
[00:46] [alkisg] Messages from dhcp3-server, seeing if it gets the request, and why it's unable to give a lease
[00:47] [kmin] this is the only thing in syslog
[00:47] [kmin] Jan 18 22:38:53 ubuntu dhcpd: DHCPDISCOVER from 00:02:55:57:71:6f via eth0
[00:47] [kmin] Jan 18 22:38:53 ubuntu dhcpd: DHCPOFFER on 192.168.7.222 to 00:02:55:57:71:6f via eth0
[00:47] [kmin] Jan 18 22:38:58 ubuntu dhcpd: No hostname for 192.168.7.222
[00:47] [kmin] and it keeps repeating
[00:48] [alkisg] Hmmm strange is that vanilla Karmic?
[00:48] [alkisg] (with no PPAs in the sources etc?)
[00:48] [kmin] no the 9.10 release
[00:49] [kmin] i forgot the name
[00:50] [kmin] do u know if there is anything else that i need to manually enable ? nbd? some sort of swap? nfs?
[00:51] [kmin] the only thing that i turned on after i installed the server was dhcp
[00:51] [kmin] by the way after i restart the client pxe fails to boot
[00:52] [kmin] it seems that some how i manage to kill the dhcp after the first request
[00:52] Selveste1___ (n=Selveste@wnn72114.wireless.dtu.dk) left irc: Read error: 54 (Connection reset by peer)
[00:52] Selveste1___ (n=Selveste@wnn72114.wireless.dtu.dk) joined #ltsp.
[00:55] Barbosa_ (n=Barbosa@189.114.39.182) left irc: Read error: 110 (Connection timed out)
[01:00] [kmin] let me ask u this do both of dhcp.conf files (the one in the tlsp dir and the other one) get executed or only the one in /etc/tlsp/?
[01:01] [kmin] cause i don't have a leae time in that one
[01:05] [alkisg] kmin: Can you upload your /etc/ltsp/dhcpd.conf to http://ltsp.pastebin.com ?
[01:07] [kmin] 1 min
[01:07] gnunux (n=emmanuel@194.167.18.244) joined #ltsp.
[01:08] [alkisg] (Karmic is the name for 9.10, btw...)
[01:09] [gnunux] hi
[01:11] [alkisg] Hello
[01:16] [kmin] http://ltsp.pastebin.com/m21243ba0
[01:22] [alkisg] option broadcast-address 192.168.0.255;
[01:23] [alkisg] kmin ^^ fix that and retry
[01:23] [kmin] oops
[01:25] otavio (n=otavio@debian/developer/otavio) left irc: Read error: 110 (Connection timed out)
[01:27] [vagrantc] alkisg: yes, but if you *only* want ltsp-client-core installed, there's no way to do it the way you had it
[01:27] otavio (n=otavio@debian/developer/otavio) joined #ltsp.
[01:27] [vagrantc] alkisg: i often do that for testing
[01:28] *** vagrantc waves to otavio
[01:28] [alkisg] vagrantc: well, isn't the current one a broken behaviour?
[01:28] [vagrantc] alkisg: i don't see how
[01:29] [vagrantc] alkisg: it's the responsibility of the person using --early-packages and --late-packages to not do stupid things.
[01:29] [alkisg] The --early-packages parameter says that it enables me to specify some packages
[01:29] [alkisg] It doesn't say that it prevents the necessary packages to be installed...
[01:29] [vagrantc] alkisg: so we should be more explicit, or do some error checking.
[01:29] [vagrantc] alkisg: but the point of it was to override the defaults.
[01:29] [alkisg] vagrantc: or we can do the other thing I said, ...
[01:30] [alkisg] (08:23:47 À¼) alkisg: (or we could move the assignment in 000-basic-configuration in the before-install) phase)
[01:30] [alkisg] ^^^ that one
[01:30] [alkisg] I think that covers all of the cases.
[01:30] [vagrantc] alkisg: i suppose... ideally, we wanted all the configuring to happen in the "configuration" phase of things...
[01:31] [vagrantc] alkisg: no, the way you suggest is no different, actually
[01:31] [alkisg] There are 4 sources of configuration:
[01:31] [alkisg] 1) ltsp-build-client.conf
[01:31] [alkisg] 2) defaults
[01:31] [alkisg] 3) command line parameters
[01:31] [alkisg] Hmmm maybe 3 :)
[01:32] [alkisg] The correct order to evaluate them probably is:
[01:33] [vagrantc] defaults are overridden by conf, which are overridden by commandline
[01:33] [alkisg] lower=defaults, a little above that = ltsp-build-client.conf, higher priority = commandline
[01:33] [alkisg] Right
[01:33] [vagrantc] so i think the correct behavior is the way it was, which is why i reverted it.
[01:33] [vagrantc] i routinely use the option in a particular way, and i don't think it's broken, just not adequately documented.
[01:34] [vagrantc] alkisg: more approriate would be to specify an --extra-packages option or some such, so it doesn't override the defaults...
[01:34] [alkisg] vagrantc: OK so the early_packages isn't clear in the docs
[01:34] [alkisg] It should state that it REPLACES the defaults
[01:34] [vagrantc] sure.
[01:35] [vagrantc] and late-packages as well.
[01:35] [alkisg] And if you don't specify ltsp-client-core or such there, it results in a broken chroot
[01:35] [vagrantc] sure.
[01:35] [alkisg] So, in WHICH parameter may a user just install ADDITIONAL stuff?
[01:35] [vagrantc] late-packages
[01:36] [vagrantc] as far as i recall, that shouldn't have a default, at least the way debian implements it... i think ubuntu might be a little different.
[01:37] [vagrantc] KERNEL_PACKAGES get added to LATE_PACKAGES
[01:38] [alkisg] So it's possible that an Ubuntu user doesn't want to install ltsp-client, ldm and dbus, and replace them with something else?
[01:38] [alkisg] OK
[01:38] [vagrantc] there is one significant difference: late-packages happens after the init script rearranging, so you will get init scripts kicking it
[01:38] [vagrantc] alkisg: yes, it is possible that any user may not want to install ltsp-client ldm and dbus.
[01:38] [alkisg] OK, sorry for me misunderstanding the meaning of that option
[01:39] [vagrantc] alkisg: say they want a console-only application...
[01:39] [vagrantc] alkisg: sorry it wasn't clearer.
[01:39] [alkisg] I'll revert them to Ubuntu as well
[01:39] [vagrantc] there's a reason the --extra-help option is there ...
[01:39] [vagrantc] there's so many possible options, but i wouldn't recommend people see most of them by default.
[01:40] [alkisg] I was just trying to gather the most significant options in the ltsp-build-client.conf configuration file,
[01:40] [vagrantc] ah, ubuntu and debian have diverged on the 020-kernel-selection plugin...
[01:40] [alkisg] so that I can e.g. initialize them with sane values (arch=i386 etc)
[01:40] [alkisg] vagrantc: unreleated: wouldn't it be better to use debconf seeding for popcon?
[01:41] [alkisg] Instead of trying to change the value after the installation?
[01:41] [vagrantc] alkisg: also look at the difference between Debian/Ubuntu/000-basic-configuration
[01:41] [alkisg] Yes, I need to revert that change for Ubuntu as well
[01:42] [vagrantc] alkisg: the way ubuntu has 000-basic-configuration, it overrides values set in ltsp-build-client.conf, whereas in debian it only sets the defaults if not already specified.
[01:43] [alkisg] Thanks, I'll fix that.
[01:44] [vagrantc] alkisg: so fixing that might avoid the need for some of your changes
[01:45] [vagrantc] i noticed that a *long* time ago and guess it never got fixed
[01:45] [alkisg] I was careful about the changes, I just thought that EARLY_PACKAGES and LATE_PACKAGES were exceptions, in which the user would only *add* more packages, and not replace the defaults
[01:46] [vagrantc] yeah, no problem, it's not obvious
[01:46] [kmin] well i fixed that but that was not the problem
[01:47] [kmin] i still get the same thing
[01:47] [alkisg] Did you restart dhcp3-server ?
[01:47] [kmin] couple of times :)
[01:48] [alkisg] You don't have any other dhcp servers around that would mess your configuration, right?
[01:48] [kmin] no
[01:49] [vagrantc] alkisg: good to see your commits... i'd best get some sleep. :)
[01:49] [alkisg] vagrantc: again, thanks for correcting me :)
[01:49] [kmin] base on the ip address that the pxe gets, it gets it from the dhcp server that i have
[01:49] [alkisg] pxe is another matter
[01:49] [kmin] (i turned off the one on the router)
[01:49] [alkisg] kmin: Do you have a standalone (non-thin-client) pc around that you could use to test things?
[01:50] [kmin] yup
[01:50] [alkisg] ok, boot it with Ubuntu or something
[01:50] [kmin] this whole thing is inside vm
[01:50] [alkisg] And first try to see if dhclient succeeds,
[01:51] [alkisg] and if it does, then install udhcpc and see if that one succeeds as well
[01:53] [kmin] dhclient works i tested it before
[01:53] [kmin] but i have no idea what udhcpc is :D
[01:53] [alkisg] sudo apt-get install udhcpc
[01:53] [elias_a] Has someone tested using Novell client on LTSP?
[01:55] [elias_a] I have a need for this. There are no .deb packages for the novell client and there have been some problems when trying to install it with alien from rpm files.
[01:55] [kmin] btw I did rm /var/log/syslog
[01:55] [kmin] and did touch /var/log/syslog
[01:55] [elias_a] Do you think this is doable or am I trying to commit a painful suicide?
[01:55] [kmin] but since then the syslog file has remained empty why?
[01:59] [zamba] you can run ltsp over a WAN?
[01:59] [zamba] you basically just need a local dhcp that points to the tftp server, right?
[01:59] [zamba] (it's a 100 Mbit/s wan)
[01:59] [zamba] before you ask
[02:02] [alkisg] kmin: sudo chown syslog:adm /var/log/syslog
[02:02] vagrantc (n=vagrant@c-76-27-239-73.hsd1.or.comcast.net) left irc: "leaving"
[02:03] [alkisg] zamba: you'd need the wireless drivers and wpa keys etc in the initramfs
[02:04] [alkisg] You'd also need to boot from lan first, as only a very few wireless cards support network booting
[02:04] [alkisg] (or have the kernel in a local media)
[02:04] [alkisg] zamba: so it's doable, but hard to do it
[02:08] Selveste1___ (n=Selveste@wnn72114.wireless.dtu.dk) left irc: Remote closed the connection
[02:09] [kmin] brb
[02:09] kmin (n=kmin@netblock-68-183-26-145.dslextreme.com) left #ltsp.
[02:13] [zamba] alkisg: wan, not wifi :)
[02:13] Selveste1 (n=Selveste@wnn72114.wireless.dtu.dk) joined #ltsp.
[02:13] [zamba] alkisg: this is going to be wired networking
[02:13] [alkisg] zamba: heh sorry :)
[02:13] [alkisg] zamba: you'll need some ports open, and you can either boot with a local gpxe or with a local dhcp server
[02:14] [zamba] local gpxe means a boot media? like flash or cd?
[02:14] [alkisg] Yes
[02:14] [alkisg] Either that, or a dhcp server around
[02:14] [zamba] alkisg: yeah
[02:14] [zamba] alkisg: i'd go for the dhcp
[02:14] [zamba] alkisg: but it's "doable"?
[02:14] [alkisg] Yeah sure it is
[02:14] [zamba] alkisg: should be any problems with tftp?
[02:14] [alkisg] Just be careful about security
[02:15] [alkisg] No, it's common to have a different tftp server than the application server
[02:18] [zamba] ok
[02:18] [zamba] what methods of load balancing exist? if any?
[02:19] cyberorg (n=cyberorg@opensuse/member/Cyberorg) left irc: Read error: 110 (Connection timed out)
[02:50] kmin (n=kmin@netblock-68-183-26-145.dslextreme.com) joined #ltsp.
[02:53] [kmin] ok when i try to run udhcpc i get this
[02:54] [kmin] SIOCGIFINDEX failed!: No such device
[02:54] [kmin] but the dhcp server is working just fine
[02:59] [kmin] so just to give some back ground
[02:59] [kmin] i installed a ltsp server (ubuntu) and now when i am trying to boot a client
[03:00] [kmin] after the pxe get the image and after the ubuntu logo comes up
[03:00] [kmin] i keep getting this message :
[03:03] [kmin] :D nm
[03:03] [kmin] some new stuff is happening
[03:09] [kmin] it is working thanks everyone
[03:09] kmin (n=kmin@netblock-68-183-26-145.dslextreme.com) left #ltsp.
[03:10] Pod2 (n=pd213@untangle1.hughes.cam.ac.uk) joined #ltsp.
[03:23] [zamba] hehe
[03:27] [zamba] solutions for running windows applications in a ltsp session?
[03:27] [zamba] preferably terminal services.. if the licensing allows it
[03:28] [Appiah] wine ?
[03:29] [Appiah] or rdesktop to a windows server
[03:50] [Appiah] what did you have in mind zamba ?
[03:51] [zamba] Appiah: something like that, yeah
[03:51] [Appiah] something like what? :)
back next →
1 2 3 4 5 6
up
Generated by logs2html module for eggdrop v.2.3.4
Find latest version at http://sourceforge.net/projects/logs2html or http://shmupsik.osetia.org