after installing i'm not able to boot from client through pxe..getting DHCP not found error

05:14

<alkisg_web>

That's a very very old tutorial, it might have issues

05:14

Don't use it

05:14

Use either ltsp-manager or ltsp-pnp:

05:14

!ltsp-pnp

05:14

<ltsp>

ltsp-pnp: ltsp-pnp is the recommented method to install and maintain LTSP for "usual" setups. Since it doesn't involve chroots, it requires little to no command line to maintain it. It automatically supports both thin and fat ltsp clients. https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp

05:14

<alkisg_web>

Best, use ltsp-manager

05:16

<achyut>

which one easy to install as i have not enough knowledge on linux

05:16

<alkisg_web>

This one:

05:16

!ltsp-manager

05:16

<ltsp>

ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager

05:17

<achyut>

also let me know whcih is the best desktop to install LTSP

05:17

Statler has joined IRC (Statler!~Georg@p579FE37C.dip0.t-ipconnect.de)

05:19

<achyut>

also let me know whcih is the best desktop to install LTSP

05:19

<alkisg_web>

It says that in the page, read the page. It's best to use MATE. It also has a link to download the cd.

cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Remote host closed the connection)

13:40

mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)

14:23

markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)

14:26

<markit>

hi, is not strictly ltsp related but I need for a script to modify /etc/cups/cups-browsed.conf. Is there in GNU/Linux a command to modify config files that are key=value or key value? And if the key is not found, add the "key value" pair automatically?

14:26

btw, cupsd.conf has 'key=value' while cups-browsed.conf is 'key value' (space)!

14:43

<||cw>

markit: of hand I don't know, one usually does those things with awk and/or sed though

14:43

a more general and active linux-focused channel would probably be a better place to ask

14:48

vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)

14:49

<alkisg>

markit: afaik, the cupsctl command that I told you yesterday parses and modifies that file

14:53

<vagrantc>

alkisg: so, ltsp-manager is now waiting in NEW: https://ftp-master.debian.org/new.html

14:54

<alkisg>

I saw it! Cool!

14:55

<vagrantc>

some things are waiting a few months, hopefully we'll be luckier than that :)

14:55

<alkisg>

Haha

15:11

<fzimper>

Hi! Any tips on how to run ltsp-manager from a fat-client? ltsp-remoteapps doesn't work

15:12

<vagrantc>

interesting use-case :)

15:13

<fzimper>

Well, should be a pretty common one, don't you think so?

15:13

<alkisg>

fzimper: did you enable ltsp-remoteapps in lts.conf?

15:13

!epoptes

15:13

<ltsp>

epoptes: Epoptes is a computer lab administration and monitoring tool. It works on Ubuntu and Debian based labs with LTSP or non-LTSP servers, thin and fat clients, standalone workstations, NX clients etc. More info: http://www.epoptes.org

15:13

<alkisg>

epoptes.org/doc/fats or something, there's documentation on how to run remoteapps there

* sutula thought he saw a bug report by vagrantc some time ago related to NBD, but was hoping the channel had some better solutions.

16:05

<sutula>

Also, I have not seen any instructions on how to configure my DHCP server, so have adapted from what I used to use ages ago. Maybe this is the issue?

16:08

<vsuojanen>

sutula: are you first time asking this here after starting you adventure to setup a new LTSP server?

16:09

<sutula>

vsuojanen: A few weeks ago I was given the guidance to try 16.04 and ltsp-manager here

16:10

<vsuojanen>

did you ask the bot or someone here?

16:10

<sutula>

Asked the channel, someone in the channel answered thru the bot

16:13

That was on 8/28

16:18

<vsuojanen>

I have been very long away from this channel. I don't know where to continue guiding. the DHCP server should not need anymore LTSP specific configurations as it should not be initially setup on the LTSP server

16:22

the ltsp-pnp instructions guide you to a setup which uses dnsmasq and external dhcp server.

16:25

<sutula>

Maybe I am struggling because the old ltsp server/clients are coexisting on the same network. I am trying to take one client and boot from the new server until I have it working, and not take down the old clients yet.

16:26

I have been able to do that by changes in my DHCP server's config file, but maybe I am messing up the stuff dnsmasq would have done?

16:26

* sutula will study dnsmasq

16:27

<vsuojanen>

if you have enough resources on some machine setup a quick virtual environment and start with http://wiki.ltsp.org/wiki/Ltsp-manager

16:29

<sutula>

Thanks for the repointer...when I checked about a week ago, steps 5 and 6 pointed to empty pages. They have content now.

16:32

<vsuojanen>

yeah. it may be the issue. np

16:32

<sutula>

This makes me think I should re-update my server and try again...perhaps things have been fixed last few days.

16:36

<vsuojanen>

from wiki that the services on LTSP server itself would not have changed that much from ltsp-pnp instructions. http://wiki.ltsp.org/wiki/Ltsp-manager/Initial_setup

16:37

but Ltsp-manager, it should be well tested if it is published and recommended here

16:39

<sutula>

So far, my symptoms point to confusion between my main DHCP server and dnsmasq that ltsp-manager configures. Your comments have at least given me somewhere to look. Thanks!

16:40

<vsuojanen>

sutula: one thing with the setup is almost every time boot the LTSP server after the client image is updated

16:44

I mean after the client image is first time created. The purpose of course is that LTSP server should not have to be rebooted after image updates. but that time is when you setup your server or change the server ip

16:47

<sutula>

OK, thanks! Looking at what ltsp-manager has done with dnsmasq config file, I can see that my old/main DHCP server is stepping on values. Starting there and will try again.

alkisg: Should you have time for a last question, I'd really like to stick with ltsp-manager but do have a few older i386 clients. Is there some manual steps I can take to build i386 images while the server and most clients are amd64, or is it an all-or-nothing?

20:27

<alkisg>

sutula: if you read the docs, you'll see that it says "use i386 if you have both amd64 and i386 clients"

20:27

If you don't have any machines with 16+ GB RAM, there's no reason to use amd64

20:27

(with 16+ GB RAM there's a bug where i386 gets too slow)

20:28

Now, if for some reason you don't want that, yes you can build an i386 chroot, but it's not a very well documented feature of ltsp

20:29

ifcpu64 of pxelinux allows you to automatically select the correct chroot, and ltsp has some code for that somewhere

20:29

<sutula>

alkisg: I did see it in the docs, but wondered whether it was reasonable to supplement i386 by hand

20:29

I'm guessing it's dicey given fat client support?

20:29

<alkisg>

Do you have machines with 16+ GB RAM?

20:29

<sutula>

I don't, so i386 can work

20:29

<alkisg>

Right

20:30

You only get 5% less speed, and gain some free RAM, so it's not a significant difference

20:30

So just install the server with i386 live cd

20:30

<sutula>

It's a "start install all over", but should go faster now that I've been through it 3 times :)

20:30

<alkisg>

Hehe

20:30

<sutula>

thanks much for the consulting!

20:30

<alkisg>

np; i should start charging for that :P

20:30

* alkisg waves

20:31

* sutula would be glad to send beer money

20:32

<||cw>

you also only have the speed penalty if the clients have more than 4GB ram

I’m working to get my fat 16.04 clients to authenticate to AD and I think I’m most of the way there.

23:55

The server is running on a 2 NIC setup. I can ssh into the server from a computer on the WAN (ssh ADuser@server.ip.address) and it works!

23:58

When I login via ssh, it creates the user on the server, but with none of the folders e.g. ~/Desktop. However, then when I log in sitting directly at the server, it logs in and creates that home directory structure. Nice!