1249258332 Q * nou Ping timeout: 480 seconds
1249258419 J * Elton08643 ~Delphi@201008145180.user.veloxzone.com.br
1249258886 Q * Elton08643 Read error: Connection reset by peer
1249259062 J * nou Chaton@causse.larzac.fr.eu.org
1249259378 J * Elton04675 ~Delphi@201008145180.user.veloxzone.com.br
1249259773 Q * Elton04675 Remote host closed the connection
1249259901 J * takeru ~takeru@nttkyo119073.tkyo.nt.ftth.ppp.infoweb.ne.jp
1249260234 Q * Piet Remote host closed the connection
1249260330 J * Piet ~piet@28IAABCOO.tor-irc.dnsbl.oftc.net
1249261067 J * Elton05919 ~Delphi@201008145180.user.veloxzone.com.br
1249261160 Q * Elton05919 Remote host closed the connection
1249261829 J * Elton05163 ~Delphi@201008145180.user.veloxzone.com.br
1249262591 Q * Elton05163 Read error: Connection reset by peer
1249263337 J * Elton00880 ~Delphi@201008145180.user.veloxzone.com.br
1249263435 Q * Elton00880 Remote host closed the connection
1249264889 Q * takeru Quit: takeru
1249266581 J * takeru ~takeru@nttkyo119073.tkyo.nt.ftth.ppp.infoweb.ne.jp
1249267145 J * Elton04653 ~Delphi@201008145180.user.veloxzone.com.br
1249267208 Q * Elton04653 Remote host closed the connection
1249267340 Q * gnarface Read error: Connection reset by peer
1249267867 J * gnarface ~gnarface@dsl081-036-235.lax1.dsl.speakeasy.net
1249268063 J * Elton03163 ~Delphi@201008145180.user.veloxzone.com.br
1249268266 N * Elton03163 Elton02136
1249268302 Q * Elton02136 Read error: Connection reset by peer
1249268557 J * Elton09385 ~Delphi@201008145180.user.veloxzone.com.br
1249268563 Q * Elton09385 Read error: Connection reset by peer
1249268575 J * saulus_ ~saulus@c207172.adsl.hansenet.de
1249268685 J * Elton05262 ~Delphi@201008145180.user.veloxzone.com.br
1249268741 Q * Elton05262 Remote host closed the connection
1249268982 Q * saulus Ping timeout: 480 seconds
1249268988 J * Elton05891 ~Delphi@201008145180.user.veloxzone.com.br
1249268992 N * saulus_ SauLus
1249269002 Q * Elton05891 Read error: Connection reset by peer
1249269233 J * Elton08614 ~Delphi@201008145180.user.veloxzone.com.br
1249269277 Q * Elton08614 Remote host closed the connection
1249269584 J * Elton02687 ~Delphi@201008145180.user.veloxzone.com.br
1249269610 Q * Elton02687 Remote host closed the connection
1249270788 Q * takeru Quit: takeru
1249271200 Q * hparker Quit: Read error: 104 (Peer reset by connection)
1249272587 J * Elton01474 ~Delphi@201008145180.user.veloxzone.com.br
1249273188 Q * Elton01474 Remote host closed the connection
1249273461 J * Elton07707 ~Delphi@201008145180.user.veloxzone.com.br
1249273484 Q * Elton07707 Remote host closed the connection
1249274027 J * Elton08743 ~Delphi@201008145180.user.veloxzone.com.br
1249274244 Q * Elton08743 Read error: Connection reset by peer
1249274560 J * Elton09860 ~Delphi@201008145180.user.veloxzone.com.br
1249274574 Q * Elton09860 Read error: Connection reset by peer
1249275440 N * Bertl_zZ Bertl
1249275444 M * Bertl morning folks!
1249275809 J * docelic_ ~docelic@78.134.195.168
1249276002 J * scientes ~scientes@97-113-166-22.tukw.qwest.net
1249276051 J * Elton02586 ~Delphi@201008145180.user.veloxzone.com.br
1249276102 Q * docelic Ping timeout: 480 seconds
1249276429 Q * Elton02586 Quit: Ping timeout: 480 seconds
1249276476 J * Elton09314 ~Delphi@201008145180.user.veloxzone.com.br
1249276547 M * Bertl Elton09314: please fix your client/connection!
1249276683 Q * Elton09314 Read error: Connection reset by peer
1249276979 M * fback morning Bertl :-)
1249277034 M * theocrite Hi all.
1249277090 M * theocrite How many people here set the context of the guest by hand ? And how many let it be random ?
1249277184 M * theocrite I personaly (on my home servers) make it the same as the last byte of my ip address (ie : 192.168.1.$ctx), so it's easier to remember, but I can't convince someone we should keep this method on a shared server.
1249277224 J * Elton06440 ~Delphi@201008145180.user.veloxzone.com.br
1249277381 M * gnarface i'm curious about contexts too
1249277386 M * gnarface so far i've been setting all mine manually
1249277398 M * gnarface to seperate 2-byte integers
1249277414 M * gnarface but i'm curious about what the danger is in setting them to the same number
1249277428 M * gnarface is there ever a reason you might want to?
1249277437 M * gnarface maybe to simplify private networking amongst guests?
1249277447 M * gnarface or is it always a bad idea for memory security or something?
1249277513 Q * Elton06440 Remote host closed the connection
1249277579 M * Bertl identical context number means that the guest(s) will share the same process (or network) space
1249277626 M * Bertl but as util-vserver creates the context for each guest, it is very likely to 'just fail', when you assign the same xid/nid twice
1249277669 J * Elton06999 ~Delphi@201008145180.user.veloxzone.com.br
1249277697 M * Bertl Elton06999: last warning :)
1249277946 Q * Elton06999 Remote host closed the connection
1249278431 J * Elton09783 ~Delphi@201008145180.user.veloxzone.com.br
1249278511 Q * puck Ping timeout: 480 seconds
1249278521 Q * Elton09783 Remote host closed the connection
1249278676 J * Elton00890 ~Delphi@201008145180.user.veloxzone.com.br
1249278943 Q * Elton00890 Remote host closed the connection
1249279368 J * Elton09494 ~Delphi@201008145180.user.veloxzone.com.br
1249279438 J * puck ~puck@leibniz.catalyst.net.nz
1249279462 Q * Elton09494 Remote host closed the connection
1249279625 J * Elton05236 ~Delphi@201008145180.user.veloxzone.com.br
1249279723 Q * Elton05236 Read error: Connection reset by peer
1249279878 J * Elton09952 ~Delphi@201008145180.user.veloxzone.com.br
1249280396 Q * balbir_ Ping timeout: 480 seconds
1249280621 M * Bertl off for now ... bbl
1249280626 N * Bertl Bertl_oO
1249280673 Q * Elton09952 Remote host closed the connection
1249280913 J * Elton04144 ~Delphi@201008145180.user.veloxzone.com.br
1249281369 Q * Elton04144 Read error: Connection reset by peer
1249282781 J * balbir_ ~balbir@59.145.136.1
1249282854 Q * balbir_ Remote host closed the connection
1249282991 J * dna ~dna@55-197-103-86.dynamic.dsl.tng.de
1249283079 J * sharkjaw ~gab@149-49-95.oke2-bras6.adsl.tele2.no
1249283495 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr
1249283680 J * ghislainocfs21 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr
1249283977 Q * ghislainocfs2 Ping timeout: 480 seconds
1249285661 J * davidkarban ~david@193.85.217.71
1249286472 J * balbir_ ~balbir@59.145.136.1
1249287518 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1249287528 J * BWare ~itsme@ip-80-113-1-198.ip.prioritytelecom.net
1249287864 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk
1249288468 J * gnuk ~F404ror@pla93-3-82-240-11-251.fbx.proxad.net
1249291075 J * friendly ~friendly@ppp118-208-195-205.lns10.mel6.internode.on.net
1249293487 J * geb ~geb@AOrleans-253-1-64-186.w92-140.abo.wanadoo.fr
1249293527 M * geb hi
1249294817 Q * geb Ping timeout: 480 seconds
1249295126 J * geb ~geb@AOrleans-253-1-64-186.w92-140.abo.wanadoo.fr
1249295445 N * Bertl_oO Bertl
1249295463 M * Bertl back now ...
1249295583 M * BWare wb ;)
1249295777 M * geb hi Bertl :)
1249296187 Q * balbir_ Ping timeout: 480 seconds
1249297998 Q * friendly Quit: Leaving.
1249298072 Q * sid3windr Remote host closed the connection
1249298236 J * sid3windr luser@bastard-operator.from-hell.be
1249300448 J * doener ~doener@i59F565BD.versanet.de
1249300468 J * pmjdebru1jn pascal@jester.pcode.nl
1249300647 Q * pmjdebruijn Ping timeout: 480 seconds
1249300676 J * asl_ ~zombo@p57A1FFF6.dip.t-dialin.net
1249301099 Q * asl Ping timeout: 480 seconds
1249301889 J * hparker ~hparker@2001:470:1f0f:32c:290:96ff:fe50:40fa
1249302043 J * elesouef ~elesouef@212.51.177.50
1249302174 Q * BenG Remote host closed the connection
1249303232 Q * geb Ping timeout: 480 seconds
1249303956 J * geb ~geb@AOrleans-253-1-64-186.w92-140.abo.wanadoo.fr
1249304203 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk
1249304570 J * r ~vava@p5496F482.dip.t-dialin.net
1249304859 Q * geb Ping timeout: 480 seconds
1249304953 J * duckx ~Duck@81.57.39.234
1249304981 Q * VavaR Ping timeout: 480 seconds
1249305372 J * geb ~geb@AOrleans-253-1-64-186.w92-140.abo.wanadoo.fr
1249305394 J * Elton04592 ~Delphi@201008145180.user.veloxzone.com.br
1249305886 Q * Elton04592 Read error: Connection reset by peer
1249306069 M * Bertl nap attack ... bbl
1249306074 N * Bertl Bertl_zZ
1249308001 Q * sharkjaw Remote host closed the connection
1249308199 J * uva bno@118-160-165-119.dynamic.hinet.net
1249308747 Q * nou Ping timeout: 480 seconds
1249309421 Q * geb Quit: /
1249309882 J * geb ~geb@AOrleans-253-1-64-186.w92-140.abo.wanadoo.fr
1249310563 J * dowdle ~dowdle@scott.coe.montana.edu
1249310583 J * nou Chaton@causse.larzac.fr.eu.org
1249311282 Q * geb Ping timeout: 480 seconds
1249312086 Q * davidkarban Quit: Ex-Chat
1249312290 Q * scientes Ping timeout: 480 seconds
1249312942 J * mxs_ mxs@p4FCCB2DE.dip.t-dialin.net
1249313257 Q * mxs Ping timeout: 480 seconds
1249313712 J * Elton09507 ~Delphi@189.82.137.165
1249313728 Q * Elton09507 Read error: Connection reset by peer
1249313887 J * Elton00406 ~Delphi@189.82.137.165
1249313916 Q * Elton00406 Read error: Connection reset by peer
1249314374 J * Elton02279 ~Delphi@189.82.137.165
1249315025 J * balbir_ ~balbir@122.172.27.40
1249316616 Q * ManaPirat Remote host closed the connection
1249317214 Q * Elton02279 Read error: Connection reset by peer
1249317465 J * ousado__ ~johnny@p5B3C1280.dip0.t-ipconnect.de
1249317770 J * imcsk8 ~ichavero@148.229.1.11
1249317872 Q * ousado_ Ping timeout: 480 seconds
1249319550 Q * gnuk Quit: NoFeature
1249319626 Q * Snow-Man Ping timeout: 480 seconds
1249319647 J * dna_ ~dna@55-197-103-86.dynamic.dsl.tng.de
1249320025 Q * dna Ping timeout: 480 seconds
1249320284 J * Elton05877 ~Delphi@189.82.137.165
1249320608 Q * Elton05877 Read error: Connection reset by peer
1249320916 N * Bertl_zZ Bertl
1249320923 M * Bertl back now ...
1249321105 J * Elton06494 ~Delphi@189.82.137.165
1249321137 M * Bertl Elton06494: please fix your client and/or connection, or I'll have to ban you
1249321183 Q * Elton06494 Remote host closed the connection
1249321387 Q * docelic_ Quit: http://www.spinlocksolutions.com/
1249323362 Q * nenolod Read error: Operation timed out
1249323376 J * nenolod nenolod@petrie.dereferenced.org
1249323665 J * Snow-Man ~sfrost@tamriel.snowman.net
1249323877 Q * doener Ping timeout: 480 seconds
1249324166 J * Kmos ~gothicx@kmos.user.oftc.net
1249326264 M * theocrite I guess the client is fixed now :)
1249327840 M * FIChTe bertl are you here?
1249327846 M * Bertl yup
1249327849 M * FIChTe :)
1249327868 M * FIChTe are you gonna build a patch for 2.6.30.4?
1249327881 M * Bertl probably, does the old one fail to apply
1249327884 M * Bertl ?
1249327890 M * FIChTe i didnt try
1249327895 M * FIChTe i will try it right now
1249327899 M * Bertl k, let me know
1249327901 M * FIChTe k
1249327938 M * gnarface what is the best kernel to be running these days?
1249327960 M * FIChTe 2.6.30
1249327965 M * gnarface i heard about the big security issue around 2.6.30 or 2.6.30.1 i think it was?
1249327968 M * FIChTe if you want both kvm and vserver
1249327980 M * gnarface did they ever fix the security issue up 2.6.30.x?
1249327987 M * gnarface oh
1249327995 M * gnarface what if i don't give a shit about kvm then which kernel?
1249328003 M * FIChTe which security hole do you mean?
1249328014 M * FIChTe then probably 2.6.27
1249328017 M * gnarface the one from slashdot last week
1249328026 M * FIChTe yeah its fixed
1249328031 M * FIChTe in almost every distri
1249328045 M * gnarface http://it.slashdot.org/article.pl?sid=09/07/18/0136224
1249328055 M * gnarface null pointer referencing
1249328060 M * gnarface yuck
1249328070 M * FIChTe so i know in debian its fixed
1249328181 M * gnarface yea there is that file attrs bug with debian stable though
1249328196 M * gnarface so you gotta build from source
1249328209 M * gnarface to avoid that 2.6.26 issue
1249328238 M * FIChTe or just backport the debian upstream kernel as i do
1249328263 M * gnarface oh yea i suppose i could do that
1249328317 M * Bertl well, the debian kernels might fix _some_ things, but they are generally as buggy as mainline :)
1249328333 M * gnarface indeed
1249328336 M * gnarface well good to know
1249328759 M * FIChTe bertl
1249328765 M * FIChTe patch applies
1249328781 M * Bertl good :)
1249328825 M * FIChTe http://paste.linux-vserver.org/13228
1249328837 M * FIChTe now lets compile ;)
1249329339 J * dkg ~dkg@lair.fifthhorseman.net
1249329359 M * dkg what is the capability to set to allow access to /proc/fs within a vserver?
1249329758 M * gnarface i'm new here but i was under the impression that access to /proc was a bad idea for security reasons?
1249329777 M * Bertl dkg: why do you need/want that?
1249329866 M * dkg nfs-kernel-server, unfortunately :/
1249329876 M * dkg does that just not mix with vserver?
1249329881 M * dkg should i take a different approach?
1249329900 M * gnarface isn't there a vserver-nfs patch or something?
1249329901 M * gnarface wait
1249329919 M * gnarface or a vserver option for enabling nfs server capabilitis?
1249329927 M * gnarface capabilities
1249329928 M * Bertl dkg: do you plan to run a kernel-nfs _inside_ a guest?
1249329944 M * dkg that's what i'm considering, yes
1249329985 M * Bertl don't do it .. there is no advantage in that over running it on/from the host, and you have to give a lot of capabilities to the guest
1249330015 M * Bertl either switch to userspace nfs-server (which works quite fine inside a guest) or run it on the host, possible with IP restrictions or such
1249330022 M * dkg ok, fair enough.
1249330059 M * dkg i don't think nfs-user-server is as fully-featured as i want in this instance
1249330066 M * dkg so i'll look at the other options.
1249330068 M * dkg thanks for the advice.
1249330091 M * Bertl you can still use the util-vserver tools to further restrict permissions to the nfs-kernel thread
1249330099 M * Bertl (but only to some extend)
1249330130 M * gnarface dkg: what distro are you on?
1249330139 M * dkg yeah, and portmap etc will need to run in the host as well :/
1249330159 M * dkg gnarface: i'm using debian, but i don't mind patching things or trying to feed changes upstream.
1249330206 M * Bertl dkg: you can run portmap wherever you want :)
1249330213 M * Bertl it doesn't need to be the host ...
1249330238 M * gnarface dkg: i've noticed there is a vserver-debiantools package that seems to be an alternate to util-vserver
1249330253 M * gnarface depending on whether you're running unstable or not you may get better behavior out of one or the other
1249330257 M * dkg gnarface: vserver-debiantools seems outdated from what i've seen.
1249330263 M * dkg i try to avoid it.
1249330277 M * mugwump I thought that was just a bunch of scripts layered over it
1249330293 M * mugwump the last thing util-vserver needs is more shell scripts
1249330296 M * gnarface well the only significant difference i noticed was that on sid, vserver-debiantools will warn you not to build a sid guest, while util-vserver will just happily build a broken one
1249330332 M * gnarface you must build lenny or earlier then upgrade after
1249330384 M * gnarface other than that yea it seemed like a pretty superficial wrapper around util-vserver with an only slightly friendlier looking interface 
1249330471 M * gnarface i didn't try the lenny one
1249330483 M * mugwump yeah, for some reason best known only to debootstrap maintainers old debootstraps can never seem to make newer debian chroots
1249330485 M * gnarface everything in debian stable is dated as hell
1249330493 M * gnarface thats why its stable
1249330532 M * Bertl stable is an alias for ancient :)
1249330583 M * mugwump there should be nothing wrong with the approach imho
1249330672 M * mugwump but changing virtually everything about stuff which shouldn't imho change, like the packaging system (eg debconf and helpers), and the debootstrap madness says to me that there are some basic problems they have with getting design right
1249330860 M * gnarface yea the process flow is great but the software design seems to border on demented
1249330912 M * gnarface but i have a feeling that if i knew enough about the internals of it there would be a fair justification 
1249330986 M * dkg mugwump: on the one hand it sounds like there's a complaint that debian is too old
1249330995 M * dkg on the other hand you're complaining that it changes too much
1249331429 Q * BenG Quit: I Leave
1249331449 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk
1249331456 Q * BenG 
1249331513 M * mugwump dkg: actually it's a complaint that the wrong things change
1249331555 M * mugwump or, there is no forward thinking and clean design in the fundamental parts of the system
1249331574 M * mugwump eg system V never needed to overhaul its package management system every release
1249331592 M * mugwump it was a simpler packaging system which could do more
1249331607 M * mugwump and I really don't see why debootstrap should not be able to build future releases properly
1249331972 M * gnarface hmm. well a good point
1249332006 M * gnarface i wonder if it has anything to do with scalability concerns
1249334348 Q * larsivi Remote host closed the connection
1249334594 J * larsivi ~larsivi@70.84-48-63.nextgentel.com
1249335254 M * FIChTe i hate apple ffs
1249335473 M * FIChTe bertl btw. kernel build was successful for debian kernel linux-2.6_2.6.30-5 for both i386 and amd64
1249335549 N * PowerKe_ PowerKe
1249335742 Q * dna_ Quit: Verlassend
1249336249 M * pmjdebru1jn FIChTe: Apple FFS?
1249336258 M * pmjdebru1jn does Apple use FFS?
1249336926 M * FIChTe apple uses nvidia chipsets :/
1249338374 M * gnarface you hate nvidia too?
1249338982 Q * imcsk8 Quit: This computer has gone to sleep
1249340607 Q * dowdle Remote host closed the connection
1249340866 Q * Kmos Quit: return unless user.signoff?
1249340955 Q * bonbons Quit: Leaving
1249341306 Q * duckx Quit: Client exiting
1249341828 J * asl ~zombo@p57A1F8DC.dip.t-dialin.net
1249341982 Q * asl_ Ping timeout: 480 seconds
1249342213 Q * C14r Ping timeout: 480 seconds
1249343037 Q * gnarface Remote host closed the connection
1249343545 J * gnarface ~gnarface@dsl081-036-235.lax1.dsl.speakeasy.net