IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 2 March 2017 (all times are UTC)
| 00:01 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection) | |
| 01:10 | Grembler has left IRC (Grembler!~Ben@cpc87179-aztw31-2-0-cust6.18-1.cable.virginm.net, Quit: I Leave) | |
| 01:42 | bennabiy has left IRC (bennabiy!~bennabiy@unaffiliated/bennabiy, Remote host closed the connection) | |
| 02:39 | bennabiy has joined IRC (bennabiy!~bennabiy@unaffiliated/bennabiy) | |
| 03:43 | buiu has joined IRC (buiu!49f5b851@gateway/web/freenode/ip.73.245.184.81) | |
| 03:43 | <buiu> hello
| |
| 03:52 | buiu has left IRC (buiu!49f5b851@gateway/web/freenode/ip.73.245.184.81, Ping timeout: 260 seconds) | |
| 04:43 | cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg) | |
| 04:51 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 05:17 | cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 258 seconds) | |
| 05:17 | cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg) | |
| 05:18 | Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, Ping timeout: 268 seconds) | |
| 05:22 | Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack) | |
| 05:49 | Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, Read error: Connection reset by peer) | |
| 05:49 | halfwit has joined IRC (halfwit!~root@unaffiliated/halfwit) | |
| 05:50 | <gehidore> o/ halfwit
| |
| 05:50 | <halfwit> o/
| |
| 05:50 | <gehidore> alkisg might be someone to talk to about the type of *thing* which you're after
| |
| 05:50 | <halfwit> ok.
| |
| 05:51 | <gehidore> iirc they're appx UTC +2 so latency might be in our best interest
| |
| 05:51 | <halfwit> Oh yeah. No worries
| |
| 05:51 | <gehidore> I just think with what ltsp does and what you're doing there might be some common ground that they'd have some advice towards what you're doing
| |
| 05:53 | <halfwit> Yeah, this looks on par certainly with what I'm hoping to achieve.
| |
| 05:54 | I'm certainly extending the terminal analogy quite thin, but the fundamentals aren't different.
| |
| 05:54 | <gehidore> nbd might be something to look at as well
| |
| 05:57 | <alkisg> Good morning
| |
| 05:58 | gehidore: I didn't see any questions asked... ?
| |
| 05:58 | halfwit: what's that you're after?
| |
| 06:01 | <halfwit> alkisg: I'm doing a bit of research on the feasibility of setting up diskless clients on some devices I have here, using PXE on my more powerful system, I haven't ran into any specific questions yet, other than if anyone has done this (with full graphical clients), how was it in practice
| |
| 06:02 | <gehidore> sorry if it's off topic alkisg.
| |
| 06:02 | <halfwit> alkisg: But eventually I may get in to various caching and synchronization methods, and would rather try the ear of people who have done this frequently, rather than just trial and error
| |
| 06:02 | I'll just idle :p
| |
| 06:03 | <gehidore> also good morning alkisg
| |
| 06:03 | <alkisg> halfwit: sure... I'm not sure why you won't be using ltsp directly, but if you do want to do it manually, yeah you'll find that ltsp has seen/solved most of the issues you'll bumped into
| |
| 06:04 | <halfwit> alkisg: I'm still researching what's out there, I certainly will look into using it directly.
| |
| 06:04 | <alkisg> !ltsp-pnp
| |
| 06:04 | <ltsp> ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
| |
| 06:05 | <alkisg> halfwit: if you like, try that ^, it'll take you about 1h including the OS installation, and will give you a good perspective on what ltsp is about
| |
| 06:05 | <halfwit> ok.
| |
| 06:06 | Statler has joined IRC (Statler!~Georg@p579FE574.dip0.t-ipconnect.de) | |
| 06:09 | <halfwit> alkisg: Thanks!
| |
| 06:09 | <alkisg> np
| |
| 06:38 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 07:06 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 240 seconds) | |
| 07:40 | mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk) | |
| 07:48 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 07:55 | Grembler has joined IRC (Grembler!~Ben@cpc87179-aztw31-2-0-cust6.18-1.cable.virginm.net) | |
| 08:09 | Statler_ has joined IRC (Statler_!~Georg@mail.lohn24.de) | |
| 08:11 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 258 seconds) | |
| 08:55 | cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 260 seconds) | |
| 09:08 | cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg) | |
| 09:43 | prof has joined IRC (prof!c233ebd1@gateway/web/freenode/ip.194.51.235.209) | |
| 09:43 | prof is now known as Guest2175 | |
| 09:59 | markus_e92 has left IRC (markus_e92!~markus_e9@91-115-22-19.adsl.highway.telekom.at, Ping timeout: 258 seconds) | |
| 10:01 | markus_e92 has joined IRC (markus_e92!~markus_e9@62-46-96-73.adsl.highway.telekom.at) | |
| 10:01 | Guest2175 has left IRC (Guest2175!c233ebd1@gateway/web/freenode/ip.194.51.235.209, Ping timeout: 260 seconds) | |
| 10:58 | lurky_work has left IRC (lurky_work!~url_work@220-128-110-82.HINET-IP.hinet.net, Read error: Connection reset by peer) | |
| 11:23 | url_work has joined IRC (url_work!~url_work@220-128-110-82.HINET-IP.hinet.net) | |
| 12:37 | markus_e92 has left IRC (markus_e92!~markus_e9@62-46-96-73.adsl.highway.telekom.at, Ping timeout: 260 seconds) | |
| 12:40 | markus_e92 has joined IRC (markus_e92!~markus_e9@62-46-96-73.adsl.highway.telekom.at) | |
| 12:45 | Faith has joined IRC (Faith!~paty_@unaffiliated/faith) | |
| 13:26 | Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack) | |
| 13:45 | yanu_ has left IRC (yanu_!~yanu@178-116-57-70.access.telenet.be, Read error: Connection reset by peer) | |
| 13:45 | yanu has joined IRC (yanu!~yanu@178-116-57-70.access.telenet.be) | |
| 14:37 | ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu) | |
| 15:24 | mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving) | |
| 15:30 | zama has left IRC (zama!~zama@unaffiliated/stryx/x-3871776, Quit: leaving) | |
| 15:32 | zama has joined IRC (zama!~zama@unaffiliated/stryx/x-3871776) | |
| 15:52 | Statler has left IRC (Statler!~Georg@p579FE574.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 15:53 | Statler_ has left IRC (Statler_!~Georg@mail.lohn24.de, Quit: Leaving) | |
| 15:53 | Statler has joined IRC (Statler!~Georg@mail.lohn24.de) | |
| 16:43 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 16:54 | Grembler has left IRC (Grembler!~Ben@cpc87179-aztw31-2-0-cust6.18-1.cable.virginm.net, Quit: I Leave) | |
| 17:46 | ZAJDAN has joined IRC (ZAJDAN!4d30954b@gateway/web/freenode/ip.77.48.149.75) | |
| 17:47 | <ZAJDAN> hello..I am facing a problem that booting client return: connection: Connection timed out
| |
| 17:48 | in syslog: Mar 2 17:20:38 debian in.tftpd[15868]: tftp: client does not accept options
| |
| 17:49 | <alkisg> ZAJDAN: does this happen in all clients, or just one?
| |
| 17:50 | And, distro/version?
| |
| 18:04 | <ZAJDAN> Debian 8 x64 ..there I build client arch i386
| |
| 18:06 | I testet just one client
| |
| 18:07 | physical client...but I could also try virtaul machine
| |
| 18:15 | <alkisg> !tftp
| |
| 18:15 | <ltsp> tftp: Here's a page to help you troubleshoot TFTP problems in Ubuntu: https://help.ubuntu.com/community/UbuntuLTSP/Troubleshooting/TFTP
| |
| 18:15 | <alkisg> In that page, there are instructions for how to test the tftp server
| |
| 18:16 | E.g. by trying to download a file from another client
| |
| 18:16 | Check that your tftp server works fine
| |
| 18:18 | <ZAJDAN> what I forgot say is that DHCP options I have on Mikrotik
| |
| 18:18 | I do not use DHCP on the machine where runs tftp
| |
| 18:19 | but it will not be the problem what I have
| |
| 18:26 | I created one virtual machine a have tried to boot from network..same problem
| |
| 18:27 | so it will be something with tftp-hpa
| |
| 18:31 | <alkisg> Right, follow that page to verify if tftpd-hpa is ok or not
| |
| 18:33 | <ZAJDAN> ok on my debian I do: /etc/init.d/tftpd-hpa restart [ ok ] Restarting tftpd-hpa (via systemctl): tftpd-hpa.service.
| |
| 18:33 | ps -aux |grep tftp root 18904 0.0 0.0 14996 148 ? Ss 19:32 0:00 /usr/sbin/in.tftpd --listen --user tftp --address 0.0.0.0:69 --secure /srv/tftp
| |
| 18:34 | so I see the tftp runs
| |
| 18:36 | but !!!!! systemctl status tftp-hpa ● tftp-hpa.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
| |
| 18:36 | hmmmm
| |
| 18:57 | halfwit has left IRC (halfwit!~root@unaffiliated/halfwit, Quit: WeeChat 1.7) | |
| 18:57 | <alkisg> Debian and Ubuntu are going to default to dnsmasq for tftp and dhcp services (and possibly dns)
| |
| 18:57 | You might want to use that instead..
| |
| 18:57 | Ther's also ltsp-config dnsmasq to automate the config
| |
| 18:57 | !proxydhcp
| |
| 18:57 | <ltsp> proxydhcp: A proxy DHCP server is defined by the PXE specification as a server which sends auxiliary boot information to clients, like the boot filename, tftp server or rootpath, but leaves the task of IP leasing to the normal DHCP server. More info: https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP
| |
| 18:57 | <alkisg> !ltsp-pnp
| |
| 18:57 | <ltsp> ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
| |
| 19:27 | Statler has left IRC (Statler!~Georg@mail.lohn24.de, Remote host closed the connection) | |
| 19:38 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 19:56 | gehidore has left IRC (gehidore!~username@unaffiliated/man, Quit: WeeChat 1.7) | |
| 19:57 | gehidore has joined IRC (gehidore!~username@unaffiliated/man) | |
| 20:15 | <ZAJDAN> this is irony :_) on LTSP is recommended DNSMASQ
| |
| 20:39 | Faith has left IRC (Faith!~paty_@unaffiliated/faith, Quit: Leaving) | |
| 21:11 | lucas__ has joined IRC (lucas__!~lucas@186.227.186.18) | |
| 21:11 | lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Ping timeout: 268 seconds) | |
| 21:37 | matute has joined IRC (matute!c87bb75b@gateway/web/freenode/ip.200.123.183.91) | |
| 21:38 | <matute> Hi all, I'm kind of new to LTSP, so sorry if I ask something too basic, I've been trying to resolve something for many hours now and I thought I could get some help here.
| |
| 21:39 | <alkisg> Shoot
| |
| 21:39 | <matute> I've installed in a fres Debian 8 a standalone server
| |
| 21:39 | (apt-get install ltsp-server-standalone)
| |
| 21:40 | I've got it running and I can boot a client using PXE just fine. But when I ltsp-chroot in the server and install something in /opt/ltsp/amd64 I don't see it using my thin client session
| |
| 21:40 | <alkisg> Did you run ltsp-update-image at some point?
| |
| 21:41 | <matute> I feel like the thin client session (PXE one) is not enclosed in the /opt/ltsp/amd64 enviroment
| |
| 21:41 | <alkisg> Do you have an /opt/ltsp/images/amd64.img file on the server?
| |
| 21:42 | <matute> I haven't got the images directory
| |
| 21:42 | I'm not using NBD
| |
| 21:43 | I created the client image (ltsp-build-client)
| |
| 21:43 | <alkisg> OK. SO, you have a thin client, and you login there, and now you're on the server :)
| |
| 21:43 | <matute> then I ltsp-chroot'ed into it and installed rdesktop
| |
| 21:43 | <alkisg> So if you install something on the server, and not in the chroot, you'll see it in the thin client session
| |
| 21:43 | rdesktop? when you say "thin client session", what do you mean?
| |
| 21:44 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 21:44 | <alkisg> Do you login to a windows server, or to the ltsp server?
| |
| 21:44 | <matute> what I 've done is the opposite, but yes. I installed "rdesktop" (apt-get install rdesktop) having chrooted before
| |
| 21:45 | I'm always talking about linux and thin clients, it just happens to be that the program I installed is the rdesktop client
| |
| 21:45 | could have been any other
| |
| 21:45 | <alkisg> Which desktop environment are you using?
| |
| 21:45 | <matute> gnome 3
| |
| 21:45 | (and I'm already starting to hate it a bit)
| |
| 21:45 | <alkisg> And when you login to the client, you see gnome 3, right?
| |
| 21:45 | <matute> yeap
| |
| 21:46 | I see gnome 3
| |
| 21:46 | <alkisg> And there's no rdesktop there, right?
| |
| 21:46 | <matute> I can login
| |
| 21:46 | but the session is exactly as if I had login in the server
| |
| 21:46 | right
| |
| 21:46 | <alkisg> That's what thin clients are for
| |
| 21:46 | So, you need to install rdesktop directly on the server /
| |
| 21:46 | Not in the chroot
| |
| 21:47 | <matute> ok, I get it.
| |
| 21:47 | <alkisg> If you apt-get get install rdesktop on the server, then you'll see it directly on the client
| |
| 21:47 | But, there are other options in ltsp
| |
| 21:47 | What are your client specs? CPU/RAM?
| |
| 21:47 | <matute> varies a lot
| |
| 21:47 | <alkisg> Do you have anything with less than 1 GB RAM?
| |
| 21:48 | <matute> the PC i'm working on right now (the thin client of course) is a 4GB dual core diskless
| |
| 21:48 | I would say nothing below de 1GB mark
| |
| 21:48 | <alkisg> !thin-client-bandwidth
| |
| 21:48 | <ltsp> I do not know about 'thin-client-bandwidth', but I do know about these similar topics: 'thin-clients-bandwidth'
| |
| 21:48 | <alkisg> !thin-clients-bandwidth
| |
| 21:48 | <ltsp> thin-clients-bandwidth: A small explanation why thin clients can't perform well with video, lots of screen updates etc: https://sourceforge.net/p/ltsp/mailman/message/35694699/
| |
| 21:48 | <matute> that's a robot right?
| |
| 21:48 | <alkisg> I wrote a message to the ltsp mailing list a couple of days ago, read about it
| |
| 21:48 | Yes
| |
| 21:48 | So, in that link I explain the downsides of thin clients,
| |
| 21:49 | and end up suggesting that people should use ltsp fat clients,
| |
| 21:49 | which are still diskless and netbooted from the same server image
| |
| 21:49 | But there, you install rdesktop to the chroot, like you tried to do, not on the server
| |
| 21:49 | And rdesktop ends up running with the client cpu/ram, not with the server cpu/ram
| |
| 21:49 | <matute> sorry for my ignorance, is that the nbd model?
| |
| 21:49 | <alkisg> It can work with either nbd or nfs, it doesn't matter much
| |
| 21:50 | nbd is just 2.5 times faster
| |
| 21:50 | LTSP has supported fat clients for a lot of years, but for some reason there are many cases where users don't know about them
| |
| 21:50 | <matute> I usually use ltsp-localapps to achieve that
| |
| 21:50 | <alkisg> The newest and easiest way to maintain an ltsp installation, is ltsp-pnp:
| |
| 21:51 | !ltsp-pnp
| |
| 21:51 | <ltsp> ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
| |
| 21:51 | <alkisg> Right, now everything is a localapp
| |
| 21:51 | And it's a lot more stable and easy to maintain
| |
| 21:51 | ltsp-pnp works in debian too, if you google about it vagrant has written a how-to (might be a bit old though)
| |
| 21:52 | <matute> ok I will read carefully what you wrote, I 've been dealing with a couple of working LTSP installations but this is the first time I install one from scratch
| |
| 21:52 | <ZAJDAN> if I have instaled lstp-server and want to use lstp-pnp...should I unistall lstp-server?
| |
| 21:53 | <matute> Only thing is that I like (and kind of need) to understand what's going on, so I see I have a lot of reading ahead
| |
| 21:53 | Thanks a lot for your help, I appreciate it a lot
| |
| 21:54 | <alkisg> ZAJDAN: if you want the stock ltsp-pnp, you would need to replace tftpd-hpa with dnsmasq, and delete the chroot
| |
| 21:54 | matute: np
| |
| 21:54 | syntaxerrormmm has joined IRC (syntaxerrormmm!~syntaxerr@net-93-148-8-168.cust.dsl.teletu.it) | |
| 21:54 | <alkisg> If you guys have 1 hour, you could set up ltsp-pnp with ubuntu-mate 16.04 in a new computer, and see how it's supposed to work
| |
| 21:55 | (1 hour includes both the os installation and the ltsp part)
| |
| 21:55 | <syntaxerrormmm> hi guys, I have issues with epoptes not sharing the "server" monitor. Machines are all 14.04 64bit with 5.10.1
| |
| 21:55 | <ZAJDAN> ok so I will unistall tftp-hpa and lstp-server
| |
| 21:55 | <alkisg> You'll see that the clients that have >512 MB RAM run a whole lot better as fat clients
| |
| 21:55 | ZAJDAN: keep ltsp-server, remove tftpd-hpa (not tftp-hpa, that's the client)
| |
| 21:56 | syntaxerrormmm: is epoptes running? ps aux|grep epoptes
| |
| 21:56 | <ZAJDAN> ok ok
| |
| 21:56 | <syntaxerrormmm> on the server? Sure, I can see all the powered-on clients
| |
| 21:56 | <matute> I'll give it a try
| |
| 21:56 | <syntaxerrormmm> (btw thx alkisg)
| |
| 21:56 | <alkisg> syntaxerrormmm: ah, do you mean the "broadcast screen" command?
| |
| 21:56 | <matute> thanks alkisg!
| |
| 21:56 | <alkisg> You're welcome :)
| |
| 21:56 | <syntaxerrormmm> alkisg: yes, sorry
| |
| 21:57 | <alkisg> syntaxerrormmm: hmm, it's 0:00 here, mind if I see that with "remote support" so that it's faster?
| |
| 21:57 | !vnc-edide
| |
| 21:57 | <ltsp> vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
| |
| 21:57 | <syntaxerrormmm> quite complex but can try
| |
| 21:57 | <ZAJDAN> the DNSMASQ..will I need it when DHCP provide my Mikrotik router?
| |
| 21:57 | <syntaxerrormmm> I am on VPN connected to VNC on a machine with the server
| |
| 21:58 | <alkisg> ZAJDAN: yes, for tftpd
| |
| 21:58 | syntaxerrormmm: if your host is linux, you could do this instead:
| |
| 21:58 | !vnc-dide
| |
| 21:58 | <ltsp> vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
| |
| 21:58 | <alkisg> ...and share your host screen instead of the server screen
| |
| 21:59 | <syntaxerrormmm> thx, doing it in a second...
| |
| 22:03 | <matute> read what you wrote Alkis, I get it. still got some doubts but I will do my homework before throwing questions... by the way I didn't know that Mate was called like that because of the Yerba Mate (which I'm drinking right now, in Argentina... ) Bye and thanks again!
| |
| 22:04 | <alkisg> bb!
| |
| 22:04 | matute has left IRC (matute!c87bb75b@gateway/web/freenode/ip.200.123.183.91, Quit: Page closed) | |
| 22:05 | <ZAJDAN> ltsp-pnp is also for debian?
| |
| 22:05 | <alkisg> Yes, google for a how to debian ltsp-pnp
| |
| 22:06 | <syntaxerrormmm> docente!
| |
| 22:06 | sorry, wrong window ;)
| |
| 22:07 | <ZAJDAN> do I understand, that ltsp-pnp is not a package, but method?
| |
| 22:08 | <alkisg> syntaxerrormmm: I think the problem was ufw, but now with the tests that client needs a reboot
| |
| 22:09 | <syntaxerrormmm> don't know if you have a little more time, will reboot now
| |
| 22:09 | <alkisg> syntaxerrormmm: if service ufw stop + client reboot doesn't fix it, come again tomorrow morning greek time
| |
| 22:09 | You're in Italy, right? Should be ok for you...
| |
| 22:09 | ZAJDAN: right, it's a method, not a package
| |
| 22:09 | <syntaxerrormmm> yes, I am
| |
| 22:10 | don't know if I can manage in the morning, but I will contact you as soon as possible
| |
| 22:10 | <alkisg> Try to login now...
| |
| 22:10 | <syntaxerrormmm> (lab is also remote for me)
| |
| 22:10 | <ZAJDAN> alkisg: ok..thnx....so with this method I cannot use as DHCP router Mikrotik? there is possible set Options for PXE
| |
| 22:11 | <alkisg> ZAJDAN: sure you can
| |
| 22:11 | <ZAJDAN> super
| |
| 22:11 | <syntaxerrormmm> seems working now, don't understand why others were working but not this one
| |
| 22:12 | <alkisg> syntaxerrormmm: the problem was ufw and random ports in epoptes
| |
| 22:12 | So, the wrong random ports were blocked
| |
| 22:12 | But other random ports were allowed
| |
| 22:12 | <syntaxerrormmm> ok. So you will advice for disabling ufw?
| |
| 22:12 | <alkisg> Broadcasting selects a random port to send the broadcast...
| |
| 22:12 | Yes unfortnately epoptes isn't very firewall friendly at the moment
| |
| 22:13 | There's a bug report filed for that, and a patch exists
| |
| 22:13 | <syntaxerrormmm> alkisg: thank you very much. I do owe you a lot, really.
| |
| 22:13 | (and also some schools in italy do ;) )
| |
| 22:14 | <alkisg> https://bugs.launchpad.net/epoptes/+bug/1244975
| |
| 22:14 | You're welcome. Paypal donations accepted. :P :D
| |
| 22:14 | Good night everyone!
| |
| 22:14 | <syntaxerrormmm> alkisg: I will, for sure
| |
| 22:14 | good night and thanks again :)
| |
| 22:15 | <ZAJDAN> which distribution is the best for LTSP-PNP ?
| |
| 22:18 | <alkisg> ZAJDAN: I maintain it's ubuntu version, but debian is fine too, maybe a bit less documented
| |
| 22:19 | ZAJDAN: if you don't mind, follow this part exactly, it'll work even with your router:
| |
| 22:19 | !ltsp-pnp
| |
| 22:19 | <ltsp> ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
| |
| 22:19 | * alkisg waves and really goes afk now :) | |
| 22:21 | <ZAJDAN> debian has for ltsp-pnp old documentation
| |
| 22:24 | in my case on the server will not run DHCP server, so I am not sure how to continue
| |
| 22:24 | https://wiki.debian.org/LTSP/Howto .....I ended on point 3.
| |
| 22:54 | fisek has joined IRC (fisek!c1a59449@gateway/web/freenode/ip.193.165.148.73) | |
| 23:39 | syntaxerrormmm has left IRC (syntaxerrormmm!~syntaxerr@net-93-148-8-168.cust.dsl.teletu.it, Quit: leaving) | |
| 23:39 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection) | |