1204934472 Q * ftx Ping timeout: 480 seconds 1204934527 Q * ||Cobra|| Ping timeout: 480 seconds 1204934643 Q * arachnist Ping timeout: 480 seconds 1204934686 Q * dowdle Remote host closed the connection 1204934855 Q * yarihm Quit: This computer has gone to sleep 1204936157 J * yarihm ~yarihm@brln-4d0517db.pool.mediaWays.net 1204936728 Q * dna_ Quit: Verlassend 1204938327 J * xdr_ ~xdr@141-173-96-87.cust.blixtvik.se 1204938327 Q * xdr Read error: Connection reset by peer 1204940551 Q * yarihm Quit: Leaving 1204940601 J * doener_ ~doener@i577BBF2C.versanet.de 1204941012 Q * doener Ping timeout: 480 seconds 1204945967 N * lMgUf_IWT Hollow 1204952041 J * balbir ~balbir@122.167.183.239 1204954207 Q * balbir Ping timeout: 480 seconds 1204954895 J * balbir ~balbir@122.167.195.83 1204956065 M * nkukard harry, bud ... could you shoot me your grsec patch for 2.6.22? I think they made some changes in 22 which breaks the previous grsec patch? 1204956617 J * hparker ~hparker@linux.homershut.net 1204957715 J * ||Cobra|| ~cob@pc-csa01.science.uva.nl 1204959146 Q * doener_ Quit: leaving 1204961406 Q * hparker Quit: Read error: 104 (Peer reset by connection) 1204961480 J * JonB ~NoSuchUse@77.75.164.169 1204961486 J * Julius ~julius@p57B254EE.dip.t-dialin.net 1204961742 J * arachnist arachnist@plzdie.kthxbai.pl 1204962004 J * hijacker ~Lame@87-126-142-51.btc-net.bg 1204963126 Q * padde Remote host closed the connection 1204963131 J * padde ~padde@patrick-nagel.net 1204965388 J * ftx ~ftx@dslb-084-060-234-173.pools.arcor-ip.net 1204965650 M * Supaplex is vserver available ontop of UML? do I have to apply a patch to a vanilla kernel for this? 1204966067 Q * ftx Read error: Connection reset by peer 1204966079 Q * JonB Quit: This computer has gone to sleep 1204966088 J * ftx ~ftx@dslb-084-060-245-232.pools.arcor-ip.net 1204966371 J * ktwilight_ ~ktwilight@140.98-67-87.adsl-dyn.isp.belgacom.be 1204966787 Q * ktwilight Ping timeout: 480 seconds 1204967024 N * DoberMann[ZZZzzz] DoberMann 1204967027 J * friendly12345 ~friendly@ppp59-167-152-238.lns4.mel6.internode.on.net 1204967071 J * ktwilight ~ktwilight@56.88-66-87.adsl-dyn.isp.belgacom.be 1204967286 J * JonB ~NoSuchUse@77.75.164.169 1204967447 Q * ktwilight_ Ping timeout: 480 seconds 1204967568 J * ktwilight_ ~ktwilight@238.70-66-87.adsl-dyn.isp.belgacom.be 1204968007 Q * ktwilight Ping timeout: 480 seconds 1204968578 Q * brc Ping timeout: 480 seconds 1204968729 J * julius_ ~julius@p57B25960.dip.t-dialin.net 1204969161 Q * Julius Ping timeout: 480 seconds 1204969617 J * ktwilight ~ktwilight@91.111-66-87.adsl-dyn.isp.belgacom.be 1204969972 Q * ktwilight_ Ping timeout: 480 seconds 1204970403 J * rgl ~rgl@lx2-84-90-10-215.netvisao.pt 1204970407 A * rgl waves 1204970735 Q * balbir Read error: Operation timed out 1204970911 Q * cehteh Ping timeout: 480 seconds 1204971483 J * balbir ~balbir@122.167.176.189 1204972396 J * zbyniu_ ~zbyniu@host13-188.crowley.pl 1204972401 Q * zbyniu_ 1204973925 Q * balbir Read error: Operation timed out 1204975296 J * brc bruce@megarapido.cliquerapido.com.br 1204976509 Q * hijacker Quit: Leaving 1204978027 P * friendly12345 1204980237 Q * kiorky Ping timeout: 480 seconds 1204980878 N * Bertl_zZ Bertl 1204980893 M * Bertl morning folks! 1204981142 Q * Aiken Quit: Leaving 1204981978 J * ste ~stejules@dslb-084-056-136-078.pools.arcor-ip.net 1204981986 Q * ste 1204982607 Q * JonB Quit: This computer has gone to sleep 1204983364 M * mnemoc hi, has anyone used busybox's init inside a guest? 1204983629 J * cehteh ~ct@pipapo.org 1204983749 M * Bertl mnemoc: yep, my test image has busybox installed, you can use that as init as well, but it needs some preparations 1204983752 J * JonB ~NoSuchUse@77.75.164.169 1204983838 M * mnemoc Bertl: in my try reboot/halt/poweroff return "no" :\ and i have no clue what may be causing it... do you? 1204983921 M * Bertl do your reboot/halt/poweroff link to busybox too? 1204983973 M * mnemoc yes 1204984047 M * Bertl supposed to work then, but was a long time ago, maybe it got broken ... 1204984061 M * daniel_hozac strace? 1204984079 M * mnemoc compiling it right now :) 1204984149 M * mnemoc kill(1, SIGTERM) = -1 ESRCH (No such process) 1204984150 M * mnemoc doh 1204984171 M * mnemoc wth 1204984178 M * Bertl interesting ... pid 1 issue? 1204984181 M * mnemoc 28473 root 528 S init 1204984204 M * Bertl check which pid is set as initpid (in proc) 1204984217 M * daniel_hozac did you set the initstyle to plain? 1204984239 M * mnemoc yes, plain 1204984265 M * daniel_hozac what kernel? 1204984277 M * mnemoc 2.6.21.7-vs2.2.0.3-dist 1204984292 M * mnemoc ignore the -dist 1204984324 M * mnemoc Bertl: where on proc is this initpid field? 1204984336 J * kiorky ~kiorky@82.231.146.43 1204984350 M * daniel_hozac /proc/virtual//info 1204984390 M * mnemoc Init: 28473 1204984413 M * mnemoc same as ps inside the guest 1204984584 M * Bertl wb kiorky! 1204984603 M * Bertl didn't we fix quite a number of issues since 2.2.0.3? 1204984640 M * mnemoc any which may be related to this? 1204984708 M * Bertl I think we have a changelog somewhere ... 1204984739 M * mnemoc what i don't get is why runit takes pid 1 fine, and bb's doesn't on the same host 1204984775 M * mnemoc both using plain 1204984780 M * Bertl that's indeed interesting, especially with the _same_ pid 1204984895 M * mnemoc there is any way to vserver start so i can show you useful details? 1204984937 M * mnemoc i assume strace can be too much in that case :p 1204984937 M * Bertl nah, but I'd be interested in the /proc/virtual//{info,status} of both guests 1204984944 M * mnemoc ok 1204985030 M * mnemoc Bertl: http://rafb.net/p/xbXDXM76.html 1204985202 M * Bertl ans busybox inside the guest (as init) shows up in ps auxwww as pid 28473, yes? 1204985234 M * mnemoc yes 1204985255 M * mnemoc 28473 root 528 S init 1204985272 M * mnemoc ps is from bb too 1204986095 M * Bertl can you try with a different kernel (maybe in qemu) just to check? 1204986238 Q * kiorky Ping timeout: 480 seconds 1204986399 J * kiorky ~kiorky@82.231.146.43 1204988348 M * mnemoc Bertl: i'll prepare something for that... but i wont be able to give you feedback until tuesday or so :( 1204988361 M * Bertl okay, TIA 1204988426 M * daniel_hozac mnemoc: have you tried with the bb ps in the runit guest? 1204988445 M * Bertl hmm, good point 1204988479 M * mnemoc daniel_hozac: 1m 1204988613 M * mnemoc 10483 root 580 S runit 1204988719 M * mnemoc how is this? who does the initpid -> 1 translation? 1204988848 M * daniel_hozac does ls -l /proc show /proc/1? 1204989616 M * mnemoc nope 1204989683 M * mnemoc daniel_hozac: how does procps's ps get the list of processes? 1204989752 M * mnemoc kill -s INT 1 1204989753 M * mnemoc bash: kill: (1) - No such process 1204989768 M * mnemoc on the runit guest, where ps shows a process 1 1204989857 A * mnemoc is convised now he will have to build a new kernel 1204990106 M * daniel_hozac yeah, that was fixed in 2.2.0.6. 1204990480 M * daniel_hozac odd, i don't recall us fixing /proc/1 recently... 1204990533 M * daniel_hozac oh, hmm. it's fixed in the 2.3 branch, but not in the 2.2 branch. 1204990614 M * daniel_hozac http://people.linux-vserver.org/~dhozac/p/k/delta-initpid-fix05.diff 1204990651 M * Bertl ah, nice 1204990794 M * daniel_hozac http://people.linux-vserver.org/~dhozac/p/k/delta-ocfs2-fix01.diff is also missing from 2.2. 1204990811 M * Bertl okay, will schedule an update for 2.6.22.x 1204991111 M * daniel_hozac http://vserver.13thfloor.at/Experimental/delta-keydep-fix01.diff is missing too. 1204991111 Q * kiorky Read error: Connection reset by peer 1204991164 M * daniel_hozac those were the only bug fixes i found in the 2.2-2.3 diff. 1204991268 M * Bertl okay, thanks! 1204991613 J * kiorky ~kiorky@cryptelium.net 1204991969 M * mnemoc Bertl: should i wait for 2.2.0.7 then? 1204992061 M * Bertl will take a little, as I'm busy right now, but you might want to try the two patches 1204992075 M * Bertl (three, actually :) 1204992331 M * daniel_hozac Bertl: what do you think of http://people.linux-vserver.org/~dhozac/p/k/delta-tun-feat02.diff ? 1204992458 M * Bertl hmm, how is that supposed to be used? 1204992522 M * Bertl I mean, what happens if: 1204992523 M * daniel_hozac right now, any guest can grab any tun, if they have /dev/net/tun. i'd like to restrict that. 1204992537 M * Bertl - the guest 'assigns' a host ip 1204992572 M * Bertl - the guest grabs an existing tun 1204992587 M * Bertl - the guest closes a host/other guest tun? 1204992637 M * daniel_hozac the latter two cases are what i want to deal with. as-is, if you have two guests using tuns, they can mess with eachother's interfaces. 1204992638 M * Bertl the SETNID ioctl is for the host/admin, I presume, but what keeps the guest from calling it? 1204992654 M * daniel_hozac hmm, true, that check is missing. 1204992670 M * Bertl I'd prefer to make that a syscall command 1204992715 M * daniel_hozac makes sense... 1204992716 M * Bertl the 'assign ip' case should check for guest assigned IPs and allow those IMHO 1204992743 M * daniel_hozac there's no assigning of IP addresses allowed by this patch. 1204992833 M * daniel_hozac it only aims to restrict the possibility of one guest binding to another guest's tun interface. 1204992943 M * daniel_hozac i don't think letting the guest assign addresses makes much sense. our structure does not have interfaces in it, so they could potentially mess with the networking by putting an address on the wrong interface... 1204993419 J * Infinito ~argos@201-10-138-162.gnace701.dsl.brasiltelecom.net.br 1204995293 Q * nenolod Quit: i'm always up for some rough cybersex on sundays 1204995305 J * nenolod ~nenolod@ip70-189-74-69.ok.ok.cox.net 1204995783 Q * julius_ Quit: Verlassend 1204996181 J * Linus ~nuhks@bl7-149-44.dsl.telepac.pt 1204998141 M * weasel how are we looking on the vserver for 2.6.24 front? 1204998409 M * Bertl we'll see .. maybe I find a little time the upcoming week 1204999859 J * balbir ~balbir@122.167.176.189 1205002666 Q * Infinito Remote host closed the connection 1205004930 Q * rgl Read error: Connection reset by peer 1205004941 J * rgl ~rgl@lx2-84-90-10-215.netvisao.pt 1205005510 N * DoberMann DoberMann[PullA] 1205011027 J * hparker ~hparker@linux.homershut.net 1205011255 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1205011647 Q * ktwilight Ping timeout: 480 seconds 1205011697 P * click [IRSSI] 1205012907 J * ktwilight ~ktwilight@91.111-66-87.adsl-dyn.isp.belgacom.be 1205013358 J * kiorky_ ~kiorky@cryptelium.net 1205013366 Q * kiorky Read error: Connection reset by peer 1205013440 J * Aiken ~james@ppp118-208-56-200.lns4.bne1.internode.on.net 1205013828 J * FireEgl FireEgl@adsl-61-136-247.bhm.bellsouth.net 1205014082 Q * bonbons Quit: Leaving 1205015443 Q * samuel Quit: samuel 1205017120 Q * JonB Ping timeout: 480 seconds 1205017467 J * ViRUS ~mp@p57A6E9B6.dip.t-dialin.net 1205017706 J * virtuoso_ ~s0t0na@ppp91-122-24-88.pppoe.avangarddsl.ru 1205017708 Q * ||Cobra|| Ping timeout: 480 seconds 1205018112 Q * virtuoso Ping timeout: 480 seconds 1205018333 Q * ftx Ping timeout: 480 seconds 1205018517 Q * hparker Quit: Read error: 104 (Peer reset by connection) 1205020003 J * Julius ~julius@p57B25960.dip.t-dialin.net