1519782385 M * Bertl_oO off to bed now ... have a good one everyone! 1519782386 N * Bertl_oO Bertl_zZ 1519809573 N * Bertl_zZ Bertl 1519809577 M * Bertl morning folks! 1519809586 M * Ghislain hello bertl 1519811527 M * Ghislain 4.9.85 out... sight 1519811548 M * Bertl great! 1519811728 M * Ghislain there is no end to the daily kernel realease :p 1519814151 M * Le_Coyote Anything of interestin that new version? 1519816247 Q * gratuxri Ping timeout: 480 seconds 1519816451 J * gratuxri ~gratuxri@104.207.150.19 1519817202 M * Bertl depends on what you consider interesting ... see https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.85 for details 1519817207 N * Bertl Bertl_oO 1519818654 Q * Aiken Remote host closed the connection 1519819300 Q * any0n Remote host closed the connection 1519819319 J * any0n ~k@5PUAAAR1T.tor-irc.dnsbl.oftc.net 1519830643 Q * zerick Quit: No Ping reply in 180 seconds. 1519830715 J * zerick ~zerick@irc.quassel.zerick.io 1519833521 Q * click Remote host closed the connection 1519836742 Q * gratuxri Remote host closed the connection 1519837709 J * gratuxri ~gratuxri@104.207.150.19 1519841657 M * Ghislain 4.9.85 compile, run and testfs/testme ok 1519845117 J * obeardly ~obeardly@12.153.3.33 1519846593 J * Aiken ~Aiken@2001:44b8:2168:1000:b26e:bfff:fe2a:b951 1519849839 M * obeardly This is probably a stupid question, but what does --context mean? Is the integer you give it just a unique identifier for that VM? 1519850680 M * Bertl_oO 15 years ago when Linux-VServer was young, we decided to use integers as unique identifiers for a group of processes also known as context 1519850707 M * Bertl_oO this was also used for networking as 'network contexts' 1519850756 M * Bertl_oO the context ids 0 and 1 are special and originally numbers above 32767 were assigned dynamically 1519851418 Q * guerby Ping timeout: 480 seconds 1519851517 J * guerby ~guerby@ip165.tetaneutral.net 1519852929 M * obeardly Bertl_oO: Thanks! 1519853032 M * obeardly When I built my first vserver VM it built it's root directory under: /etc/vservers/test_vm/vdir 1519853048 M * obeardly I thought it built under the /vserver directory 1519853913 M * obeardly Can I force it to build under /vserver/vm_name/ ? 1519854670 M * Bertl_oO by default, guests are built under /vservers/ 1519854686 M * obeardly It didn't do that. I wonder what I screwed up. 1519854691 M * Bertl_oO note that debian thinks that this is bad and thus changes the default to some other place 1519854701 M * obeardly Oh, okay 1519854713 M * Bertl_oO somewhere in /var/lib or so 1519854718 M * obeardly I'm on Devuan, which scrapes it's packages from Debian 1519854726 M * obeardly and it stores them in /etc/vservers 1519854739 M * Bertl_oO that's where the config goes 1519854757 M * obeardly That's also where the root file system went 1519854767 M * Bertl_oO and /etc/vservers//vdir usually is a symlink to the rootfs 1519854806 M * obeardly There was no symlink. It all was living under /etc/vservers. 1519854829 M * Bertl_oO how did you install util-vserver? 1519854905 M * obeardly Via the Devuan/Debian package. Probably a bad idea, right? 1519854939 M * Bertl_oO maybe, don't know 1519854962 M * Bertl_oO but in this case you have to contact the maintainer about the problem 1519855115 M * obeardly It's not a huge deal. I'll create the necessary symlinks to make it all work the way I want it to. You answered my question though. Now I know that the build space is defined by the util-vserver package. 1519855126 M * obeardly Thanks again! You've been a great help. 1519855212 M * Bertl_oO check out the 'great flower page' you can also configure the vdir base 1519855232 M * obeardly great flower page? 1519855310 M * Bertl_oO http://www.nongnu.org/util-vserver/doc/conf/configuration.html 1519855360 M * Bertl_oO search for 'vdirbase' 1519855475 M * obeardly Can you enable direct SSH access to the guest systems? 1519855557 M * Bertl_oO when you have sshd running on a guest, then you can ssh into the guest if that's what you mean 1519855588 M * obeardly Okay. I noticed that if you don't have it running, and you try to ssh into it, instead of shutting you down, it kicks you to the host OS. 1519855595 M * Bertl_oO if you want to use ssh to back-door a guest, that can be done as well, but has some security implications 1519855625 M * Bertl_oO the observation you made is kind of wrong :) 1519855659 M * Bertl_oO what really happens is that you are most likely running an unrestriced sshd (binds to all available IPs) on the host, which is not advised to do 1519855700 M * Bertl_oO if you restrict the host sshd to host only IPs (listen address) then it will not bind to guest IPs 1519855777 M * Bertl_oO you can find this (and other useful questions with answers) in our FAQ 1519855779 M * Bertl_oO Frequently_Asked_Questions 1519855784 M * Bertl_oO http://linux-vserver.org/Frequently_Asked_Questions 1519855800 M * obeardly It must default to unrestricted sshd. And thanks. Yes, I've been digging through the docs, there is just a lot there.