00:30 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
04:13 | peanutbutterandc has joined IRC (peanutbutterandc!~peanutbut@2400:1a00:bb10:3b5a:7c24:bf82:3e81:2bc0) | |
04:19 | <peanutbutterandc> alkisg, is there any chance that you are around?
| |
04:20 | ...or anybody else who might be willing to give me a few pointers regarding ltsp image configuration?
| |
04:21 | I can't wrap my head around where the users come from. In the clients. For me, the clients could only log in as the pre-existing users in the ltsp server computer.
| |
04:22 | and here's another thing: it seems that if two clients log in as the same user, their changes kinda' over-writes each other's (wallpaper changes, nothing serious tested so far)
| |
04:22 | I wonder if there is a way to create 5 users (I have 4 client computers set-up), and prevent a user from being logged in twice at the same time.....?
| |
04:23 | ltsp is wonderful, BTW. I'll be digging around in the docs and doing some experiments in the meantime then
| |
05:22 | <alkisg> peanutbutterandc: morning, reading...
| |
05:23 | LTSP users are server users. Users don't need to exist at all in the vm/image/chroot.
| |
05:25 | To limit connections, see https://github.com/ltsp/ltsp/discussions/357
| |
05:34 | <peanutbutterandc> alkisg, Good morning! Thank you for the information. It's very helpful.
| |
06:21 | peanutbutterandc has left IRC (peanutbutterandc!~peanutbut@2400:1a00:bb10:3b5a:7c24:bf82:3e81:2bc0, Quit: Leaving) | |
06:54 | RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro) | |
07:20 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
07:22 | peanutbutterandc has joined IRC (peanutbutterandc!~peanutbut@2400:1a00:bb10:3b5a:ac58:e9a0:618c:ec6e) | |
07:22 | <peanutbutterandc> alkisg, hey there... what might be the reason a ltsp client get stuck at 'TFTP.....' while booting (after autoselect uidonly.kpxe)?
| |
07:24 | <alkisg> !undi
| |
07:24 | <ltspbot> I do not know about 'undi', but I do know about these similar topics: 'uefi'
| |
07:25 | <alkisg> !learn undionly.kpxe as Undionly.kpxe fails to work with some NICs. Test if ipxe.pxe works for all your clients instead: sudo wget boot.ipxe.org/ipxe.pxe -O /srv/tftp/ltsp/undionly.kpxe
| |
07:25 | <ltspbot> The operation succeeded.
| |
07:26 | <peanutbutterandc> alkisg, Thank you!
| |
07:26 | <alkisg> np
| |
07:27 | <peanutbutterandc> (also, i think that if I manually `ltsp dnsmasq` again, it works.... it has been working every now and then)
| |
07:27 | but i'll check it out.....
| |
07:32 | RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.) | |
07:54 | <peanutbutterandc> alkisg, update: ipxe.kpxe as undionly doesn't seem to resolve the issue
| |
07:54 | woernie has left IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Remote host closed the connection) | |
07:54 | <alkisg> peanutbutterandc: does this happen to any client at that point, or to just some specific clients?
| |
07:55 | <peanutbutterandc> it's happening to 2 clients w/ the original undionly.kpxe
| |
07:56 | let me check w/ the fake one on the other client too
| |
07:56 | <alkisg> peanutbutterandc: were they booting previously? The problem I'm talking about it permanent, undionly.kpxe doesn't work in some NICs; if it worked yesterday, then it's another problem
| |
07:57 | Can you upload a screenshot of the client screen?
| |
07:57 | <peanutbutterandc> okay.... it seems to work.... w/ ipxe.kpxe now
| |
07:57 | the clients are booting
| |
07:58 | i was on another setup yesterday... booting virtual clients w/ virtual ltsp server. but now, w/ a real deployment, things are.... heading south in ways i never thought of before
| |
08:09 | peanutbutterandc has left IRC (peanutbutterandc!~peanutbut@2400:1a00:bb10:3b5a:ac58:e9a0:618c:ec6e, Remote host closed the connection) | |
08:56 | woernie has joined IRC (woernie!~werner@ipservice-092-210-077-142.092.210.pools.vodafone-ip.de) | |
09:08 | woernie has left IRC (woernie!~werner@ipservice-092-210-077-142.092.210.pools.vodafone-ip.de, Ping timeout: 264 seconds) | |
09:08 | woernie_ has joined IRC (woernie_!~werner@ipservice-092-210-077-142.092.210.pools.vodafone-ip.de) | |
10:12 | gvy has left IRC (gvy!~mike@altlinux/developer/mike, Ping timeout: 264 seconds) | |
11:41 | woernie_ has left IRC (woernie_!~werner@ipservice-092-210-077-142.092.210.pools.vodafone-ip.de, Ping timeout: 256 seconds) | |
11:41 | woernie has joined IRC (woernie!~werner@ipservice-092-210-077-142.092.210.pools.vodafone-ip.de) | |
11:43 | woernie has left IRC (woernie!~werner@ipservice-092-210-077-142.092.210.pools.vodafone-ip.de, Remote host closed the connection) | |
11:57 | Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:85ba:b9d4:7b25:b2d0) | |
13:00 | gvy has joined IRC (gvy!~mike@altlinux/developer/mike) | |
13:01 | telex has joined IRC (telex!teletype@94.247.40.156) | |
13:15 | Aison0 has left IRC (Aison0!~Asion0@2a02:168:200f:110:85ba:b9d4:7b25:b2d0, Ping timeout: 272 seconds) | |
13:42 | woernie has joined IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de) | |
13:47 | Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19) | |
14:12 | woernie has left IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Remote host closed the connection) | |
14:13 | woernie has joined IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de) | |
14:57 | Aison0 has left IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 272 seconds) | |
15:02 | Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19) | |
15:07 | peanutbutterandc has joined IRC (peanutbutterandc!~peanutbut@27.34.48.183) | |
15:09 | <peanutbutterandc> alkisg, Hey there.... I think I need your help again. So, I suppose I should explain the deployment. I have 1 laptop that will be the server. And 4 laptops that will be the clients. Connected via a desktop switch. So, given the circumstance, perhaps I should `ltsp dnsmasq` a little different? Or should I use a 'ip address shared w/ other computers' kind of network from network manager? Any pointers, please?
| |
15:11 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
15:15 | Aison0 has left IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 264 seconds) | |
15:21 | Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19) | |
15:43 | Aison0 has left IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 265 seconds) | |
15:43 | <alkisg> peanutbutterandc: they're connected with the switch, and how do they get internet access? Isn't there a router involved?
| |
15:43 | <peanutbutterandc> alkisg, not at all. It's just a LAN.
| |
15:44 | But all laptops have a wireless interface and also an ethernet port.
| |
15:44 | I want to connect them all via ethernet. And ignore wireless for the moement
| |
15:44 | *moment
| |
15:44 | <alkisg> peanutbutterandc: ok, we ignore wireless, but you're saying they won't go online, right?
| |
15:45 | <peanutbutterandc> I was trying to look at setting up a dhcp server w/ dnsmasq.... but i thought it might conflict w/ what ltsp does
| |
15:45 | <alkisg> There's no browsing involved, no internet, ok?
| |
15:45 | <peanutbutterandc> alkisg, yes, sir!
| |
15:45 | <alkisg> in that case, you need to set a static ip =192.168.67.1 to the ltsp server's nic
| |
15:45 | LTSP has already configured dnsmasq to be a dhcp server there
| |
15:45 | But you need that specific ip
| |
15:45 | <peanutbutterandc> alkisg, Ah... that is something that I have to do manually!? Reading the man page, I thought `ltsp dnsmasq --proxy-sth=0` would do it for me....
| |
15:46 | I see...
| |
15:46 | <alkisg> peanutbutterandc: ltsp doesn't set the server ip
| |
15:46 | <peanutbutterandc> that makes sense
| |
15:46 | <alkisg> It configures dnsmasq, but you need to set the ip in network-manager
| |
15:46 | <peanutbutterandc> it is as easy as doing it graphically in the network manager!?
| |
15:47 | may I ask you to please connect to my server for a moment please?
| |
15:47 | !vnc
| |
15:47 | <ltspbot> I do not know about 'vnc', but I do know about these similar topics: 'kvm-vnc', 'uvnc-dide', 'vnc-alkisg', 'vnc-dide', 'vnc-edide', 'x11vnc'
| |
15:47 | <peanutbutterandc> !x11vnc
| |
15:47 | <ltspbot> x11vnc: One way to share a graphical screen with a remote person is: [local pc] port forward 5500, run: vncviewer -listen [remote pc] sudo apt-get install x11vnc; x11vnc -noshm -connect <technician-ip>
| |
15:47 | <peanutbutterandc> wait... what was that?
| |
15:48 | <alkisg> This one is the generic one; the others with -alkisg are for me
| |
15:49 | !vnc-dide
| |
15:49 | <ltspbot> 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.
| |
15:49 | <peanutbutterandc> just a sec please
| |
15:50 | I think it's done
| |
15:50 | I'm recording the screen this time as this is a real machine and not a virtual one
| |
15:51 | <alkisg> peanutbutterandc: you want your sever to serve over wifi?
| |
15:51 | <peanutbutterandc> alkisg, no sir. over wire. ethernet
| |
15:52 | <alkisg> peanutbutterandc: hmm, vnc is too slow for some reason, one frame per minute
| |
15:52 | Can you open the network connection editor?
| |
15:52 | <peanutbutterandc> that sucks....
| |
15:53 | certainly
| |
15:53 | it was actually right there... network connections
| |
15:54 | <alkisg> peanutbutterandc: can't operate, vnc too slow. Name it 192.168.67.1, give it static ip=192.168.67.1, and activate it
| |
15:54 | No gateway or dns needed there
| |
15:54 | <peanutbutterandc> Certainly!
| |
15:54 | is it okay if I name it ltsp-link (or sth similarly corny)?
| |
15:54 | <alkisg> Sure
| |
15:55 | Plain LTSP, LTSP-no-internet, whatever you like
| |
15:55 | I'm still getting one frame per minute; I'll see what you're doing in 30 seconds... :D
| |
15:55 | Looks good, now activate it
| |
15:56 | <peanutbutterandc> done
| |
15:56 | How do I activate it? o.O
| |
15:56 | I sound like an idiot
| |
15:56 | <alkisg> You click on the network icon to the bottom, and select ltsp-link
| |
15:56 | You'll need to actually plug the wire to the switch first
| |
15:56 | Now it says 'disconnected' because you have no wire
| |
15:56 | <peanutbutterandc> oh certainly
| |
15:56 | <alkisg> Right
| |
15:57 | Now click "connection information"
| |
15:57 | You should see the ip
| |
15:57 | Scroll down the menu, it should be there
| |
15:57 | Hmm, it should be under vpn connections, try to wheel down
| |
15:57 | Looks good
| |
15:57 | Now boot a client
| |
15:58 | <peanutbutterandc> ip a shows that 192.168.67.1/24
| |
15:58 | yes sir booting.... perhaps i should `ltsp dnsmasq --proxy-sth=0` just to be sure
| |
15:58 | .... i don't remember whether or not i did that right
| |
15:58 | --proxy-dhcp=0
| |
15:58 | shall i?
| |
15:59 | hmmm.... it appears i've done that already
| |
15:59 | <alkisg> no
| |
15:59 | <peanutbutterandc> so okay
| |
15:59 | <alkisg> you don't need proxy=0
| |
15:59 | nor real=1
| |
15:59 | <peanutbutterandc> i don't....? so I should perhaps just do a bare `ltsp dnsmasq`?
| |
15:59 | <alkisg> yes
| |
15:59 | <peanutbutterandc> okay
| |
15:59 | on it right now
| |
16:00 | <alkisg> Didn't the client boot already?
| |
16:00 | The 192.168.67.x/24 subnet is active unless you run ltsp dnsmasq --real-dhcp=0
| |
16:00 | <peanutbutterandc> ummm.....
| |
16:00 | it's at pxe
| |
16:00 | ooooh
| |
16:00 | there it is!
| |
16:00 | booting up
| |
16:00 | <alkisg> So it would be active anyway, no matter what you did so far. OK, nice
| |
16:01 | <peanutbutterandc> just a moment please I am actually cheating and only using a local link for the moment... i'll use a switch and boot another one as well
| |
16:01 | neato!
| |
16:01 | thank you very much
| |
16:01 | did i tell you that i kinda' sorta' found a bug-ish thingy today?
| |
16:01 | <alkisg> Trisquel is supposed to be more open-source enforcing than debian?
| |
16:02 | What bug?
| |
16:02 | <peanutbutterandc> alkisg, endorsed by papa stallman and the fsf :D
| |
16:02 | <alkisg> Hehe
| |
16:02 | Pave the way, we'll follow
| |
16:02 | <peanutbutterandc> so, if a user is a member of the group 'nopasswdlogin'.... if I try to log in, it'll bring me back to the login screen
| |
16:02 | happened to me today. and almost made me cry :D
| |
16:03 | <alkisg> That tells your DM that no password is needed, so you need to specify it in ltsp.conf
| |
16:03 | Since you didn't, it won't work over sshfs, only over nfs
| |
16:03 | It's expected behavior
| |
16:04 | <peanutbutterandc> the default config (with `ltsp nfs` as a command as per the installation guide) is infact sshfs?
| |
16:04 | <alkisg> Hmm, I wonder if simplescreenrecorder was causing vnc to show only one frame per minute...
| |
16:04 | <peanutbutterandc> ah!!!!
| |
16:04 | <alkisg> Yes, nfs is for rootfs, sshfs for home
| |
16:04 | <peanutbutterandc> oooooh
| |
16:05 | <alkisg> !ltsp-nfs
| |
16:05 | <ltspbot> ltsp-nfs: Configure NFS exports for LTSP: https://github.com/ltsp/ltsp/blob/master/docs/ltsp-nfs.8.md
| |
16:05 | <peanutbutterandc> can you use this vnc now?
| |
16:05 | <alkisg> ...while in the man page, there's an example on how to set up nfs home, if you want it
| |
16:05 | vnc => no, it still sucks
| |
16:05 | <peanutbutterandc> I see....
| |
16:06 | <alkisg> It's probably related to the internet connection between us, and mine is good, 250 mbps :P
| |
16:06 | <peanutbutterandc> Hmmm... so that means that I fix my ltsp.conf and things will work.... and I can have the guarantee that one user will be logged in in only 1 client
| |
16:06 | i'll look at that
| |
16:06 | <alkisg> (closed vnc)
| |
16:06 | <peanutbutterandc> yes... my internet connection is to blame. I admit. :D
| |
16:06 | oh thanks
| |
16:07 | whoa this man page is quite loooong!
| |
16:07 | <alkisg> !forget ltsp-nfs
| |
16:07 | <ltspbot> The operation succeeded.
| |
16:08 | <alkisg> !learn ltsp-nfs as Configure NFS exports for LTSP: https://ltsp.org/man/ltsp.conf/
| |
16:08 | <ltspbot> The operation succeeded.
| |
16:08 | <peanutbutterandc> could you please throw me what I'm supposed to look for? in order to have nopasswdlogin?
| |
16:08 | <alkisg> !forget ltsp-nfs
| |
16:08 | <ltspbot> The operation succeeded.
| |
16:08 | <peanutbutterandc> okay this one.... looking at it then
| |
16:08 | <alkisg> !learn ltsp-nfs as Configure NFS exports for LTSP: https://ltsp.org/man/ltsp-nfs/
| |
16:08 | <ltspbot> The operation succeeded.
| |
16:08 | <alkisg> peanutbutterandc: that last one
| |
16:09 | It's a small page, read the examples section
| |
16:10 | <peanutbutterandc> On it right now!
| |
16:10 | Thanks!
| |
16:11 | wait... but if I export /home over nfs, I don't get to place a system whereby concurrent logins of the same users are prevented, right?
| |
16:11 | <alkisg> peanutbutterandc: this was for nopasswdlogin to work
| |
16:12 | It's not related to concurrent logins
| |
16:12 | To avoid concurrent logins, see the link that I sent to you yesterday
| |
16:12 | <peanutbutterandc> oh... okay.... um... I'd much rather prevent concurrent logins than have nopasswd logins
| |
16:12 | yes, the /etc/security hack
| |
16:12 | <alkisg> Hmm?
| |
16:12 | No, it was an ltsp discussions thread
| |
16:12 | <peanutbutterandc> https://github.com/ltsp/ltsp/discussions/357
| |
16:13 | echo "@onelogin - maxlogins 1" > /etc/security/limits.d/local.conf
| |
16:13 | <alkisg> Right
| |
16:13 | But note that it won't work currently, even though it's the correct path :D
| |
16:13 | well, if you do that AND nfs home, it will work
| |
16:13 | <peanutbutterandc> okay... so not worth going that route I suppose.... at the moment then :D
| |
16:14 | ooooh..... hmmmmm
| |
16:14 | that's interesting
| |
16:14 | that means I also get nopasswdlogins
| |
16:14 | neat
| |
16:14 | <alkisg> Are you sure you don't want to enable autologin instead?
| |
16:15 | pc1 would login as user1 automatically, etc
| |
16:15 | <peanutbutterandc> alkisg, oooh how do i do that!?
| |
16:15 | <alkisg> man pages!
| |
16:15 | To the rescue!
| |
16:15 | <peanutbutterandc> oh okay. which one please!?
| |
16:15 | there are so many!!!
| |
16:15 | <alkisg> !ltsp.conf
| |
16:15 | <ltspbot> ltsp.conf: Configuration file for LTSP: https://ltsp.org/man/ltsp.conf/
| |
16:15 | <peanutbutterandc> oh okay! thanks!
| |
16:16 | <alkisg> So people complain that I write too little, some that I write too much. Can't please them all! :D
| |
16:16 | *some
| |
16:16 | <peanutbutterandc> alkisg, I'll try not to write a blog about ltsp someday. (once I start blogging someday) - and instead try to contribute to the wiki :P
| |
16:20 | well, alkisg, thank you very much once again for helping me out. I hope you have a great day! We shall certainly meet in irc again (when i inevitably bump my head into another wall) Thank you for your guidance and patience.
| |
16:21 | <alkisg> np
| |
16:21 | <peanutbutterandc> (:
| |
16:21 | peanutbutterandc has left IRC (peanutbutterandc!~peanutbut@27.34.48.183, Quit: Leaving) | |
16:32 | antares2021 has joined IRC (antares2021!bc4ed3f5@245.211.78.188.dynamic.jazztel.es) | |
16:37 | <antares2021> Good afternoon. I have two issues to comment, working with raspios in a ltsp ubuntu 20 installation. First, all updates/install of the raspios software (packages, etc) MUST be done with the NFS_RW condition enabled? I realized that after switching to LTSP mode netbooting, all the LTSP servers were available for login, and with the main server user
| |
16:37 | you can even install software, etc... but maybe you install it on the server, not in raspios? Because I left a lot of things working that I am not able to found now
| |
16:39 | Among those things, several installed programs but also I miss the ability to print to a labelprinter through USB. It turns out that I get a 'permission denied' when accessing /dev/ttyAMA0 when one week ago I was able to do print and get the applications running. Some of them it even doesn't find the file of the command!!
| |
16:39 | woernie has left IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Ping timeout: 264 seconds) | |
16:39 | <alkisg> antares2021: the easiest way is to have an administrative rpi, like it says in the documentation
| |
16:40 | And you can toggle administrative / non-administrative, from a line in /srv/ltsp/raspios/etc/ltsp/ltsp.conf
| |
16:40 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
16:41 | <alkisg> About /dev/tty*, run `ls -l /dev/tty*` and see the group; possibly dialout; the user needs to be in that group to access that device
| |
16:42 | peanutbutterandc has joined IRC (peanutbutterandc!~peanutbut@27.34.48.183) | |
16:42 | <antares2021> alksig: I guess administrative pi is when you boot it with NFS_RW mode?? Sorry, I am not aware of that administrative rpi in the docs. And also: the permissions shold be given to the users (all the future raspberry pi users) in the server, isn't it?
| |
16:42 | <peanutbutterandc> alkisg, ....and I'm back. I rebooted the server.... and now I'm geting a PXE-E32: TFTP open timeout. Any ideas please?
| |
16:44 | this is quite strange. it's that same client that was booting just flawlessly just a reboot ago
| |
16:48 | .....and restarting dnsmasq fixed it....
| |
16:48 | curioser and curioser....
| |
16:48 | let me poke around a bit. This is interesting
| |
16:54 | <antares2021> alksig: Ok, I've found some info in the IRC logs from march 3, 2020... I'll try to follow that
| |
16:58 | Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19) | |
16:59 | <peanutbutterandc> yeah.... the clients are stuck at TFTP..... PXE-E32: TFTP open timeout about each reboot of the server
| |
17:04 | <antares2021> alksig: I wonder if you will appreciate if I try to convert this issue into a page for the wiki
| |
17:06 | <alkisg> antares2021: permissions on the server, yes
| |
17:06 | antares2021: eeeh personally I've no need for wiki pages, but I do write them for you guys
| |
17:07 | <peanutbutterandc> ^ :D
| |
17:07 | Thanks for the wiki :D
| |
17:07 | <alkisg> The best idea is for people to maintain their own ltsp wiki pages, as notes, so that they are useful to THEM, and so that others may also benefit
| |
17:08 | Aison0 has left IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 265 seconds) | |
17:08 | <peanutbutterandc> so... like blogs? :D
| |
17:09 | <alkisg> peanutbutterandc: no, in the ltsp wiki, https://github.com/ltsp/ltsp/wiki
| |
17:09 | Blogs are not gathered in one place
| |
17:09 | So it's hard to search them for info
| |
17:10 | <peanutbutterandc> yeah... I was trying to refer to your admonition to not write blogs at the very start of the wiki :D
| |
17:10 | Anyways, any idea why my ltsp server stops working on reboot (as in clients get stuck at PXE-E32: TFTP open timeout). But if I `systemctl restart dnsmasq`, the clients start booting again
| |
17:10 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Remote host closed the connection) | |
17:11 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
17:11 | <peanutbutterandc> I can't have this happen on me at the school (for which I'm sorta' volunteering)... the kids looked at me today with so much disappointment in their eyes.
| |
17:12 | <antares2021> alksig: yes, I meant ME to write one of those pages of ltsp wiki (just for saving your time of doing that), as you say at the very first page of the wiki. Guess some nice markdown will do the trick
| |
17:17 | <peanutbutterandc> antares2021, might you have some ideas regarding why my clients get stuck at tftp..... after my server reboots?
| |
17:21 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 264 seconds) | |
17:21 | woernie has joined IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de) | |
17:27 | <antares2021> peanutbutterandc: I have no clue. I've reading the irc log before I logged in today and saw your issue... and sounds like Martian to me. Sorry :(
| |
17:28 | <peanutbutterandc> antares2021, I see. It's all right. Thank you anways (:
| |
17:33 | <alkisg> (07:10:47 PM) peanutbutterandc: Anyways, any idea why my ltsp server stops working on reboot ==> grep -r bind-interfaces /etc/dnsmasq.d
| |
17:33 | Remove that, it's a bug in libvirt+dnsmasq
| |
17:33 | <antares2021> peanutbutterandc: However, I had some issues with dnsmasq when port 53 was used by another service, so dnsmasq couldn't start. Maybe you have a similar issue there, something that at some point makes dnsmasq not function properly... imagine a service/whatever that starts before dnsmasq, prevents dnsmasq from starting and the service itself stops
| |
17:33 | after system startup...
| |
17:34 | too late XDDD
| |
17:34 | <alkisg> antares2021: yes I understood, it's nice if people volunteer to contribute, I was just noting that wiki pages aren't useful to me, but to other users
| |
17:41 | <peanutbutterandc> alkisg, Awesome! It works now. Thank you very much!
| |
17:42 | antares2021, Yes, that, too, was troubling me. But that has been resolved on my machine by now. Thanks for the ip, nevertheless
| |
17:42 | *tip
| |
18:12 | peanutbutterandc has left IRC (peanutbutterandc!~peanutbut@27.34.48.183, Quit: Leaving) | |
18:31 | antares2021 has left IRC (antares2021!bc4ed3f5@245.211.78.188.dynamic.jazztel.es, Quit: Connection closed) | |
19:29 | woernie has left IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) | |
19:37 | RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro) | |
19:37 | Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:85ba:b9d4:7b25:b2d0) | |
19:47 | Aison0 has left IRC (Aison0!~Asion0@2a02:168:200f:110:85ba:b9d4:7b25:b2d0, Ping timeout: 265 seconds) | |
19:59 | Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19) | |
20:09 | flaep has joined IRC (flaep!59f50f1c@i59F50F1C.versanet.de) | |
20:13 | <flaep> Hi, just a quick question. Is ltsp nfs only and no longer supports nbd?
| |
20:14 | <alkisg> Hi flaep, it's very easy to use nbd with the new ltsp, but it's not automated
| |
20:14 | I started adding support for it, but nfs was so much more stable that I removed it
| |
20:14 | nbd currently has a lot of drawbacks, and the only benefit is that it also supports block devices instead of files
| |
20:15 | <flaep> alkisg thank you for your answer.
| |
20:15 | <alkisg> Configuring /etc/nbd-server/conf.d and customizing ltsp.ipxe for nbd, should take less than 5 minutes
| |
20:15 | No other tasks should be necessary
| |
20:15 | <flaep> I was a bit confused since its still mentioned a was the default with5
| |
20:16 | ok will do
| |
20:16 | <alkisg> Indeed it was, in ubuntu
| |
20:16 | flaep: why do you want nbd?
| |
20:16 | (debian was still using nfs as the default if I recall properly)
| |
20:17 | <flaep> iam currently working at project that still uses ltsp5 and we want to upgrade of cause
| |
20:17 | <alkisg> But why you don't want to switch to nfs? You can use ltsp5 and ltsp21 at the same time with no issues, even if one is nbd and the other is nfs
| |
20:18 | <flaep> iam switching back and forth between ltsp and ltsp5 documentation
| |
20:18 | I never said i dont want to switch ^^.
| |
20:18 | <alkisg> Btw, ltsp21 should be able to boot an ltsp5 image without even running ltsp image at all
| |
20:19 | <flaep> Just wanted to make sure I am not missing anything
| |
20:19 | <alkisg> Wait
| |
20:19 | You have ltsp21, and you want to boot an ltsp5 image using nbd, and you don't know how to configure nbd now?
| |
20:19 | In that case, you can just run the old ltsp-config nbd command
| |
20:20 | <flaep> cool.
| |
20:20 | <alkisg> :ltsp5
| |
20:20 | set img x86_32
| |
20:20 | set cmdline ro root=/dev/nbd0p1 nbdroot=${srv}:/opt/ltsp/i386 init=/sbin/init-ltsp forcepae
| |
20:20 | kernel /ltsp/${img}/vmlinuz initrd=ltsp.img initrd=initrd.img ${cmdline}
| |
20:20 | initrd /ltsp/${img}/initrd.img
| |
20:20 | boot || goto failed
| |
20:20 | And that's my ltsp5 entry for ltsp.ipxe; yours would use nbd0 instead of nbd0p1 there
| |
20:21 | So that you can select "ltsp5" from the blue ipxe menu...
| |
20:22 | <flaep> thank you
| |
20:22 | <alkisg> np
| |
20:23 | <flaep> have a nice day/evening what ever ^^
| |
20:23 | <alkisg> To you too
| |
20:24 | <flaep> bye
| |
20:24 | flaep has left IRC (flaep!59f50f1c@i59F50F1C.versanet.de, Quit: Connection closed) | |
20:42 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
21:37 | RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.) | |
21:58 | Aison0 has left IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 265 seconds) | |
22:56 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Read error: Connection reset by peer) | |
22:56 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |