1203984076 Q * morfoh Remote host closed the connection
1203984262 Q * mnemoc Ping timeout: 480 seconds
1203986581 Q * Aiken Quit: Leaving
1203986596 J * Aiken ~james@ppp118-208-56-200.lns4.bne1.internode.on.net
1203986896 J * onox ~onox@kalfjeslab.demon.nl
1203986909 M * onox does the vmsplice exploit work in vserver guests?
1203987337 M * Bertl yes
1203987370 M * onox does the user gets root access of its guest or root access of the host?
1203987693 Q * dowdle Remote host closed the connection
1203987724 M * michiel` onox: guest, but in theory it could get root access of the host (if the exploit was adapted for vserver)
1203987789 M * michiel` although I'm not sure about the capabilities, I think it's also possible to get those back (if the exploit was written to do that)
1203987818 M * Bertl yes, it seems definitely harder, ebcause you have no information about the kernel details though
1203987847 M * Bertl but if you know what kernel you are dealing with, and maybe some config details, you can probably do it
1203987931 M * onox hmm, there aren't really patches for .23, right?
1203987955 M * Bertl no, for 2.6.24 there are pre patches, but I'd stay with 2.6.22 for now
1203987974 M * onox yes, but gentoo only provides patches for .23
1203988009 M * onox <joke>maybe I should go back to 2.6.16.52</joke>
1203988026 M * michiel` :)
1203988081 M * onox Bertl: why no patches for .23?
1203988109 M * Bertl 2.6.23 was too broken to get Linux-VServer working on it
1203988119 M * onox too broken?
1203988129 M * Bertl yes, specifically in the virtualization area
1203988140 M * onox in other areas as well?
1203988167 M * Bertl well, I haven't looked/tried there :)
1203988311 M * onox last question: the vs2.2.0.x-grsec2.1.x patch adds only vserver to an already hardened kernel?
1203988319 M * onox or does it also provides grsec itself?
1203988371 M * Bertl IIRC, it is a combined patch
1203988484 M * onox ok
1203988491 M * onox I'm gonna sleep
1203988492 M * onox bye
1203988495 Q * onox Quit: zZzZ
1203988920 J * Wonka_ produziert@chaos.in-kiel.de
1203988959 Q * Wonka Read error: Connection reset by peer
1203988959 N * Wonka_ Wonka
1203989698 Q * rgl Quit: Saindo
1203990269 M * zbyniu btw, I've after-vs grsec patch
1203992547 J * hparker ~hparker@linux.homershut.net
1203992610 M * padde I get this in /var/log/crond in all my vservers (and the cronjobs aren't run):
1203992614 M * padde Feb 26 10:09:01 stshacom1 crond[20775]: Cannot make/remove an entry for the specified session
1203992619 M * padde Feb 26 10:09:01 stshacom1 crond[20775]: CRON (root) ERROR: failed to open PAM security session: Success
1203992623 M * padde Feb 26 10:09:01 stshacom1 crond[20775]: CRON (root) ERROR: cannot set security context
1203992636 M * padde i have no clue about PAM stuff :( anybody?
1203992664 M * padde restarting crond or even the whole vserver didn't help
1203992717 M * Bertl man 3 pam?
1203992747 M * padde Bertl: but why should I even have to change something with pam?
1203992765 M * Bertl no idea, I'd say, your guest is trying to do some pam authentication which fails
1203992779 M * Bertl no idea _what_ kind of pam stuff it is doing
1203992796 M * Bertl security context sounds like se-linux though
1203992818 Q * yarihm Quit: This computer has gone to sleep
1203992829 M * padde Bertl: hm... afaik my pam-configuration is the same on the host, and there vixie-cron works as it should
1203992857 M * Bertl maybe your host allows se-linux requests to the kernel?
1203992900 M * padde maybe ;) how do I check? i think I deactivated selinux, because I have no clue about that either
1203992948 M * Bertl http://www.mail-archive.com/amanda-users@amanda.org/msg36834.html (just as an example)
1203992994 M * Bertl so, I'd suspect your system/guest is doing se-linux stuff, which might work on the host, but will definitely fail on the guest
1203993021 M * Bertl best option is to remove the 'set context' stuff from your pam config
1203993038 M * padde Bertl: I see. thanks :)
1203993080 M * padde I think I have to read on SELINUX more...
1203993723 J * morfoh ~morfoh@kilo105.server4you.de
1203993785 J * mnemoc ~amery@kilo105.server4you.de
1203994279 J * ntrs_ ~ntrs@vs079.rosehosting.com
1203994434 M * padde Bertl: solved it: http://26maidenlane.net/blog/?p=6
1203994454 M * padde Bertl: the problem was 'pam_loginuid.so' - I had this problem earlier with sshd, but forgot about it in the meantime :(
1203994490 M * Bertl excellent, maybe add something to the FAQ/wiki on linux-vserver.org?
1203994498 M * padde Bertl: will do
1203994565 M * Bertl you might want to check http://oldwiki.linux-vserver.org/VServer+installation+Fedora+Core+5 (Search for 'Caution')
1203994581 M * Bertl (maybe you can reuse that somewhat)
1203994614 M * padde hehe, yeah, that's exactly what I would have written ;)
1203994655 M * padde i'll try to find a somewhat more prominent place and copy it there
1203994678 Q * ntrs Ping timeout: 480 seconds
1203994686 M * Bertl I think the FAQ section would be a good place
1203994719 M * padde yes, i also thought of that. i'll make an entry there, as soon as i finished getting those crons running on the vservers over here
1203994732 M * Bertl excellent, TIA!
1203994846 J * Linux ~nuhks@bl7-128-106.dsl.telepac.pt
1203995260 M * padde heh, i was waiting for the confirmation email from the wiki, until i found that procmail put it into the 'gentoo' folder (which i didn't expect) - because it came from a gentoo.org mail address
1203995366 M * Bertl hmm .. maybe Hollow should have a look at that ...
1203995407 Q * FloodServ synthon.oftc.net services.oftc.net
1203995635 J * balbir__ ~balbir@122.167.196.147
1203996064 Q * balbir_ Ping timeout: 480 seconds
1203996078 M * padde Bertl: done. now i get back to work ;) thanks for the assistance
1203996236 J * friendly12345 ~friendly@ppp59-167-75-63.lns1.mel6.internode.on.net
1203996257 M * Bertl you're welcome!
1203997549 Q * mire Ping timeout: 480 seconds
1203999247 J * mire ~mire@15-171-222-85.adsl.verat.net
1203999454 Q * balbir__ Ping timeout: 480 seconds
1204000310 J * aj__ ~aj@e180199122.adsl.alicedsl.de
1204000615 J * doener_ ~doener@i577B81E0.versanet.de
1204000678 Q * aj_ Ping timeout: 480 seconds
1204001027 Q * doener Ping timeout: 480 seconds
1204002319 M * Bertl okay, off to bed .. really tired now .. have a good one everyone!
1204002324 N * Bertl Bertl_zZ
1204002400 J * balbir__ ~balbir@59.145.136.1
1204002585 J * mire_ ~mire@225-171-222-85.adsl.verat.net
1204002730 Q * mire Read error: Operation timed out
1204005944 Q * mire_ Read error: Operation timed out
1204005981 J * sharkjaw ~gab@shell.ormset.no
1204007957 J * mire_ ~mire@225-171-222-85.adsl.verat.net
1204008639 Q * mire_ Ping timeout: 480 seconds
1204008784 Q * friendly12345 Quit: Leaving.
1204008836 J * friendly12345 ~friendly@ppp59-167-75-63.lns1.mel6.internode.on.net
1204008918 M * Slydder morning all
1204008950 A * Supaplex falls flat asleep into $bed zzzZZZZzzzz....
1204010366 J * JonB ~NoSuchUse@77.75.164.169
1204014015 J * bragon ~bragon@lucifer.bragon.info
1204014094 J * FloodServ services@services.oftc.net
1204014150 N * DoberMann[ZZZzzz] DoberMann
1204014345 J * yarihm ~yarihm@84-75-103-252.dclient.hispeed.ch
1204014434 J * dna ~dna@140-212-dsl.kielnet.net
1204014918 Q * JonB Ping timeout: 480 seconds
1204015895 J * ntrs ~ntrs@vs079.rosehosting.com
1204015987 M * hijacker morning Slydder 
1204016078 M * Slydder morning
1204016304 Q * ntrs_ Ping timeout: 480 seconds
1204016794 Q * Linux Read error: Connection reset by peer
1204017165 Q * yarihm Quit: This computer has gone to sleep
1204017201 J * yarihm ~yarihm@84-75-103-252.dclient.hispeed.ch
1204017743 Q * transacid Quit: Lost terminal
1204017811 J * transacid ~transacid@transacid.de
1204018043 J * ktwilight ~ktwilight@85.86-66-87.adsl-dyn.isp.belgacom.be
1204018273 Q * ktwilight_ Ping timeout: 480 seconds
1204018420 J * JonB ~NoSuchUse@130.226.210.8
1204018965 Q * aj__ Ping timeout: 480 seconds
1204019163 Q * yarihm Quit: This computer has gone to sleep
1204019409 Q * hparker Quit: g'nite
1204019498 J * chigital ~chigital@91.90.144.102
1204020149 J * yarihm ~yarihm@vpn-global-dhcp3-061.ethz.ch
1204020638 J * ard6 ~ard@2002:d9c4:2909:1::1
1204020698 J * mire_ ~mire@225-171-222-85.adsl.verat.net
1204022094 J * ntrs_ ~ntrs@vs079.rosehosting.com
1204022548 Q * ntrs Ping timeout: 480 seconds
1204022579 Q * ntrs_ Ping timeout: 480 seconds
1204023275 J * mire__ ~mire@29-171-222-85.adsl.verat.net
1204023669 Q * mire_ Ping timeout: 480 seconds
1204024221 Q * nkukard Quit: Leaving
1204024847 J * mire_ ~mire@75-170-222-85.adsl.verat.net
1204025089 Q * mire__ Read error: Operation timed out
1204025164 Q * Aiken Remote host closed the connection
1204025404 Q * friendly12345 Remote host closed the connection
1204025418 J * mire__ ~mire@41-169-222-85.adsl.verat.net
1204025469 Q * mire_ Read error: Operation timed out
1204025802 Q * bragon Read error: Connection reset by peer
1204025958 J * Punkie ~Punkie@goc.coolhousing.net
1204026268 Q * yarihm Quit: This computer has gone to sleep
1204026496 N * Bertl_zZ Bertl
1204026501 M * Bertl morning folks!
1204026625 M * JonB hi
1204026633 J * yarihm ~yarihm@vpn-global-dhcp3-061.ethz.ch
1204027269 Q * padde Remote host closed the connection
1204027344 J * padde ~padde@patrick-nagel.net
1204027874 J * lilalinux ~plasma@80.69.41.3
1204028641 J * ktwilight_ ~ktwilight@85.86-66-87.adsl-dyn.isp.belgacom.be
1204028641 Q * ktwilight Read error: Connection reset by peer
1204029303 M * alex_ morning
1204030678 J * kurty ~kurty@dyndsl-085-016-028-221.ewe-ip-backbone.de
1204030887 M * kurty hi, i want to install linux-vserver on my debian etch root. i installed linux-image-vserver-686 via aptitude and made a reboot, but the root doesn't come back online... does somebody know what could be the problem?
1204030911 M * JonB kurty: lots of problems
1204030917 M * JonB kurty: go look at the console
1204030990 M * kurty i rebooted the server with the installed kernel now...
1204030998 M * JonB kurty: yes?
1204031001 M * kurty with the old
1204031016 M * JonB what did it say when you rebooted with the new?
1204031023 M * kurty the normal 2.6.24.2 kernel
1204031036 M * JonB kurty: which vserver kernel are you using?
1204031051 M * kurty 2.6.18-6-vserver-686
1204031063 M * kurty installed with aptitude
1204031073 M * JonB using initrd?
1204031094 M * JonB what did the console say when you booted with the vserver kernel?
1204031119 M * kurty its a rootserver, i cant see that 
1204031120 M * kurty :D
1204031126 M * JonB kurty: riiight
1204031144 M * JonB kurty: maybe it would be an advantage to being able to see the console?
1204031151 M * JonB kurty: maybe using the net console?
1204031167 M * kurty could my logfiles help me?
1204031176 M * daniel_hozac unlikely.
1204031181 M * JonB that depends on how far it boots up
1204031193 M * kurty ah ok right
1204031195 M * kurty hm
1204031213 M * JonB kurty: suppose it boots all the way up, but because you forgot the network driver you can not reach it
1204031238 M * JonB but if it doesnt even mount / then you will not be able to see the log files at all
1204031264 M * kurty okay...
1204031985 M * kurty it seems that it does not boot... i've made an entry in /etc/inittab that creates a file when it comes in runlevel 2...
1204031993 Q * JonB Ping timeout: 480 seconds
1204032812 J * nkukard ~nkukard@vc-196-207-41-251.3g.vodacom.co.za
1204033093 J * rgl ~rgl@bl8-136-113.dsl.telepac.pt
1204033096 M * rgl hellooo
1204033252 M * daniel_hozac hi
1204033304 Q * balbir__ Ping timeout: 480 seconds
1204033737 J * ftx ~ftx@dslb-084-060-216-191.pools.arcor-ip.net
1204034088 Q * nkukard Read error: Connection reset by peer
1204034130 J * balbir__ ~balbir@59.145.136.1
1204034854 Q * FireEgl Ping timeout: 480 seconds
1204035159 Q * sharkjaw Quit: Leaving
1204035373 Q * chigital Ping timeout: 480 seconds
1204035881 J * chigital ~chigital@91.90.144.12
1204036474 J * nkukard ~nkukard@dsl-243-56-13.telkomadsl.co.za
1204037048 Q * chigital Ping timeout: 480 seconds
1204037259 Q * yarihm Quit: This computer has gone to sleep
1204037483 J * yarihm ~yarihm@vpn-global-dhcp3-061.ethz.ch
1204037568 J * chigital ~chigital@91.90.144.102
1204037678 Q * rgl Ping timeout: 480 seconds
1204037836 Q * yarihm Quit: This computer has gone to sleep
1204039159 Q * nkukard Ping timeout: 480 seconds
1204039214 Q * mick_work Quit: ChatZilla 0.9.81 [Firefox 2.0.0.11/2007112801]
1204040345 J * Nuhx ~nuhks@bl7-150-36.dsl.telepac.pt
1204040399 J * JonB ~NoSuchUse@77.75.164.169
1204040600 J * dupont-y ~dupont-y@tomintoul.ipv6.univ-nantes.fr
1204040730 Q * lilalinux Remote host closed the connection
1204040860 J * dowdle ~dowdle@scott.coe.montana.edu
1204041178 Q * Nuhx Ping timeout: 480 seconds
1204041218 Q * matthew_ Quit: brb
1204041542 J * matthew_ ~matthew@81.168.74.31
1204042258 J * onox ~onox@kalfjeslab.demon.nl
1204042319 Q * matthew_ Quit: brb
1204042497 J * matthew_ ~matthew@81.168.74.31
1204042603 J * ema ~ema@rtfm.galliera.it
1204042953 J * rgl ~rgl@bl8-136-113.dsl.telepac.pt
1204043061 J * besonen_mobile_ ~besonen_m@71-220-235-129.eugn.qwest.net
1204043080 Q * besonen_mobile__ Read error: Connection reset by peer
1204043277 Q * JonB synthon.oftc.net oxygen.oftc.net
1204043277 Q * mire__ synthon.oftc.net oxygen.oftc.net
1204043277 Q * houkouonchi synthon.oftc.net oxygen.oftc.net
1204043277 Q * brc synthon.oftc.net oxygen.oftc.net
1204043530 J * JonB ~NoSuchUse@77.75.164.169
1204043530 J * mire__ ~mire@41-169-222-85.adsl.verat.net
1204043530 J * brc bruce@megarapido.cliquerapido.com.br
1204043607 Q * chigital Ping timeout: 480 seconds
1204043823 J * FireEgl FireEgl@adsl-17-144-43.bhm.bellsouth.net
1204043970 Q * balbir__ Ping timeout: 480 seconds
1204044049 J * houkouonchi ~linux@65-116-251-178.dia.static.qwest.net
1204044218 J * Infinito ~argos@201-3-115-81.gnace701.dsl.brasiltelecom.net.br
1204044261 J * Nuhx ~nuhks@bl7-150-11.dsl.telepac.pt
1204044290 Q * Infinito 
1204044865 J * pmenier ~pme@LNeuilly-152-22-72-5.w193-251.abo.wanadoo.fr
1204044885 Q * onox Quit: leaving
1204045045 Q * JonB Quit: This computer has gone to sleep
1204045179 J * nkukard ~nkukard@196.212.73.74
1204045632 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1204045807 J * yarihm ~yarihm@vpn-global-dhcp3-036.ethz.ch
1204046141 Q * dupont-y Quit: Leaving
1204047879 J * hparker ~hparker@linux.homershut.net
1204047953 Q * weeble Ping timeout: 480 seconds
1204048040 J * ntrs ~ntrs@vs079.rosehosting.com
1204048792 J * weeble ~weeble@81.52.144.1
1204048810 Q * pmenier Quit: Konversation terminated!
1204049338 Q * yarihm Quit: This computer has gone to sleep
1204050259 J * dna_ ~dna@250-207-dsl.kielnet.net
1204050569 Q * dna Ping timeout: 480 seconds
1204050694 Q * Nuhx Quit: i'll be back
1204051027 J * mick_work ~clamwin@adsl-068-157-089-099.sip.bct.bellsouth.net
1204051084 J * Linus ~nuhks@bl7-136-84.dsl.telepac.pt
1204051095 A * Linus hi :)
1204051427 Q * rgl Read error: Connection reset by peer
1204051505 J * larsivi ~larsivi@144.84-48-50.nextgentel.com
1204051509 J * rgl ~rgl@bl8-134-94.dsl.telepac.pt
1204051795 Q * FireEgl Read error: No route to host
1204051899 J * balbir ~balbir@122.167.207.147
1204052191 J * chigital ~chigital@p4FE5DD35.dip.t-dialin.net
1204052249 Q * Punkie Quit: Odcházím
1204052918 J * mjt ~mjt@nat.corpit.ru
1204053517 J * FireEgl FireEgl@4.0.0.0.1.0.0.0.c.d.4.8.0.c.5.0.1.0.0.2.ip6.arpa
1204053554 J * hijacker_ ~Lame@87-126-142-51.btc-net.bg
1204053745 Q * ema Quit: leaving
1204053962 Q * FireEgl Read error: No route to host
1204054961 J * FireEgl FireEgl@4.0.0.0.1.0.0.0.c.d.4.8.0.c.5.0.1.0.0.2.ip6.arpa
1204055180 J * aj__ ~aj@212.23.103.29
1204055936 Q * aj__ Ping timeout: 484 seconds
1204056638 Q * sladen Ping timeout: 480 seconds
1204056783 J * JonB ~NoSuchUse@77.75.164.169
1204056979 J * sladen paul@starsky.19inch.net
1204057723 Q * DoberMann cation.oftc.net neutron.oftc.net
1204057723 Q * Guy- cation.oftc.net neutron.oftc.net
1204057723 Q * baldy cation.oftc.net neutron.oftc.net
1204057723 Q * stephan cation.oftc.net neutron.oftc.net
1204057723 Q * cohan cation.oftc.net neutron.oftc.net
1204057723 Q * vasko cation.oftc.net neutron.oftc.net
1204057723 Q * sannes cation.oftc.net neutron.oftc.net
1204057723 Q * snooze cation.oftc.net neutron.oftc.net
1204057723 Q * the-me cation.oftc.net neutron.oftc.net
1204057723 Q * ard cation.oftc.net neutron.oftc.net
1204057723 Q * AndrewLee cation.oftc.net neutron.oftc.net
1204057723 Q * ag- cation.oftc.net neutron.oftc.net
1204058528 J * DLange ~dlange@p57A33788.dip0.t-ipconnect.de
1204058774 J * vasko ~vasko@unreal.rainside.sk
1204058774 J * ag- ~ag@fedaykin.roxor.cx
1204058774 J * cohan ~cohan@koniczek.de
1204058774 J * AndrewLee ~andrew@flat.iis.sinica.edu.tw
1204058774 J * the-me Patrick@Linux-Dev.org
1204058774 J * stephan ~stephan@evilhackerdu.de
1204058774 J * baldy baldy@weltkugel.baldy.biz
1204058774 J * sannes ace@har.sagt.no
1204058774 J * snooze ~o@1-1-4-40a.gkp.gbg.bostream.se
1204058774 J * Guy- ~korn@elan.rulez.org
1204058774 J * ard ~ard@gw-tweakb16.kwaak.net
1204058774 J * DoberMann ~james@cap31-6-88-180-72-76.fbx.proxad.net
1204058838 Q * rgl Ping timeout: 480 seconds
1204059418 J * obluda ~obluda@ip-89-102-198-37.karneval.cz
1204059453 M * obluda hello could anyone help with settings qemu for booting winxp from real partition? 
1204059651 M * JonB obluda: i can not help you with that
1204059805 M * obluda JonB : hihi ok :-) thnx anyway ...
1204059991 M * arachnist obluda: doesn't qemu -hda /dev/fooXY work?
1204060006 M * arachnist well, aside from the missing drivers...
1204060031 M * mjt you can try -hda /dev/hda (or sda) - your real boot disk
1204060040 M * mjt and choose to run 'doze
1204060044 M * mjt s/run/boot/
1204060076 M * mjt /dev/sdaN will not work because doze will try to find a partition table there.
1204060091 J * Aiken ~james@ppp118-208-56-200.lns4.bne1.internode.on.net
1204060107 M * obluda i was goint through these steps 
1204060107 M * mjt besides, #kvm is --> that way ;)
1204060110 M * obluda http://wiki.archlinux.org/index.php/Qemu#Using_any_real_partition_as_the_single_primary_partition_of_a_hard_disk_image
1204060125 M * mjt or qemu... ;)
1204060136 M * obluda what i dont understand is the couting of the geometry and settings cylindres
1204060172 M * mjt well, it works with a whole disk (just don't try to load the same linux again :)
1204060201 M * obluda mjt : you mean just try that qemu -hda /dev/fooXY ?
1204060202 M * mjt i dual-boot doze this way here (or, rather, triple-boot ;)
1204060224 M * mjt /dev/sda , whatever your disk is
1204060235 M * mjt fooXY can be anything ;)
1204060236 M * obluda mjt : goin to try ... ;]
1204060250 M * mjt but be careful to not run the same linux!
1204060276 M * mjt or else it will wreak your linux filesystems
1204060297 M * obluda mjt : AAA
1204060303 M * obluda mjt : hell
1204060317 M * obluda mjt: i works but partially ... 
1204060360 M * mjt it either works or not. I don't understand "partially"
1204060368 M * obluda mjt : grub screen showed up .. but when i selected winxp64 message about that my cpu is not compatible with x64 architecrute appeared
1204060374 M * mjt "i'm just a bit pregnant"
1204060401 M * mjt so check your qemu settings
1204060407 M * obluda mjt : ok
1204060408 M * mjt it's all there
1204060419 M * mjt and really, #kvm is near here...
1204060427 M * obluda mjt : but thnx i didnt know that its gonna be so easy ... lol
1204060438 M * mjt (assuming it's kvm you're using)
1204060442 M * obluda mjt u think that kvm is better?
1204060449 M * obluda mjt qemu
1204060455 M * mjt kvm is based on qemu
1204060463 M * mjt fsvo "better"
1204060477 M * mjt like, it depends on the side you look at it from.
1204060506 M * mjt kvm uses hardware virtualisation abilities
1204060519 M * obluda mjt so i dont need it :-)
1204060521 M * mjt and emulates the rest using qemu
1204060553 M * mjt all modern x86 CPUs has support for hw virt
1204060565 M * obluda mjt hehe sure :-)
1204060579 M * mjt guest is running at full CPU speed, almost no overhead
1204060617 M * mjt but obviously kvm can't emulate CPU on another arch
1204060622 M * obluda mjt on athlon its the svm flag in cpuinfo ?
1204060636 M * mjt yes
1204060653 M * obluda mjt HMM ... i was reading something about xen ...
1204060663 M * obluda mjt what do u think about it thatone
1204060706 M * daniel_hozac i think that it is also off-topic for this channel :)
1204060720 M * obluda daniel_hozac :o) virtual servr :-)
1204060745 M * daniel_hozac Xen and qemu aren't in any way related to Linux-VServer...
1204060753 M * daniel_hozac other than that Linux-VServer works fine in either.
1204060775 M * obluda daniel_hozac heh it depends ...
1204060792 M * obluda daniel_hozac but ok .. ill look around .. thnx guys ...
1204060829 M * mjt that's why i pointed out that #kvm and #qemu are elsewhere ;)
1204060881 M * mjt obluda: but please note that it's better to use partition still, not a whole device.  Whole device is trivial for testing, and is trivial to break things hard, too.
1204060909 M * obluda mjt i'll remember that -)
1204060950 M * mjt back on-topic...
1204060965 M * mjt is there any help needed in porting stuff to 2.6.24+ ?
1204060988 M * daniel_hozac help is always appreciated...
1204061027 M * mjt what's the current state of things in that front?
1204061060 M * mjt i've seen some patches dated Jan this year.
1204061124 M * daniel_hozac scheduler is still unimplemented, namespace entering of the pid namespace needs special care, fakeinit isn't quite working yet, and of course, testing it all.
1204061213 M * mjt i wonder if vserver will ever be needed when net/pid/.. namespaces stuff will be completed upstream.
1204061229 M * mjt (it's not quite ready yet)
1204061273 M * daniel_hozac understatement of the year :)
1204061284 M * mjt well, container resource limits, filesystem quotas and barrier are not in mainline
1204061306 M * mjt the rest is userspace things
1204061307 M * daniel_hozac or COW.
1204061353 M * mjt cow is working in unionfs :)
1204061370 M * daniel_hozac or fakeinit.
1204061378 M * mjt (poor cow :)
1204061420 M * daniel_hozac things like reboot aren't working either.
1204061467 M * daniel_hozac BME finally got included in some recent version, i think...
1204061490 M * daniel_hozac but i'm not sure.
1204061571 Q * Linus Quit: i'll be back
1204061790 J * Linus ~nuhks@bl7-136-84.dsl.telepac.pt
1204061801 M * mjt b-blah. 2.6.22.19 changed something in arch/i386/kernel/ptrace.c so grsec patch does not apply... fixing it
1204061906 M * mjt ..and in ./x86-64/kernel/ptrace.c too
1204062668 J * rgl ~rgl@bl8-134-94.dsl.telepac.pt
1204062737 Q * FireEgl Ping timeout: 480 seconds
1204063057 Q * larsivi Quit: Konversation terminated!
1204063147 Q * hijacker_ Quit: Leaving
1204063468 Q * ftx Ping timeout: 480 seconds
1204064003 Q * virtuoso Ping timeout: 480 seconds
1204064402 Q * bonbons Quit: Leaving
1204064747 Q * nkukard Ping timeout: 480 seconds
1204064786 J * nkukard ~nkukard@196.212.73.74
1204064789 Q * arachnist Quit: leaving
1204064797 J * arachnist arachnist@insomniac.pl
1204065281 Q * arachnist Quit: brb
1204065288 J * arachnist arachnist@plzdie.kthxbai.pl
1204065382 J * ntrs_ ~ntrs@vs079.rosehosting.com
1204065491 Q * DLange Quit: Bye, bye. Hasta luego.
1204065804 Q * ntrs Ping timeout: 480 seconds
1204065980 Q * kurty 
1204066193 Q * dna_ Quit: Verlassend
1204066552 Q * obluda Quit: BitchX-1.1-final -- just do it.
1204067339 N * DoberMann DoberMann[ZZZzzz]
1204067388 J * aj__ ~aj@p5B23FC4B.dip.t-dialin.net
1204067441 J * friendly12345 ~friendly@ppp59-167-75-63.lns1.mel6.internode.on.net
1204067627 Q * JonB Ping timeout: 480 seconds
1204068063 J * arachnis1 arachnist@088156188145.who.vectranet.pl
1204068145 Q * arachnis1 
1204068904 Q * hparker Quit: Quit
1204069412 Q * aj__ Ping timeout: 480 seconds
1204069542 J * FireEgl FireEgl@4.0.0.0.1.0.0.0.c.d.4.8.0.c.5.0.1.0.0.2.ip6.arpa
1204069585 J * hparker ~hparker@linux.homershut.net