1256083228 M * geb i could test on some hosts if you like :)
1256083296 M * geb Bertl, do you are interested for getting a vserver for dev/backup/what you want , or you already have a ton of those ?
1256083304 M * tam geb, thanks for the offer :)  I'm pretty sure I stripped anything that could be considered sensitive data from it, but I'd rather not pass it around if I can avoid it :)
1256083337 M * geb 'k :)
1256083513 M * Bertl geb: depends on the conditions and the service I get :)
1256083643 M * geb amd64, free, best effort, a public ipv4, a v6, rss: 256, ~5-10go of disk space, and a part of the cpu :)
1256083684 Q * laurent Ping timeout: 480 seconds
1256083774 J * laurent ~laurent@AToulouse-157-1-34-173.w86-201.abo.wanadoo.fr
1256083803 M * Bertl geb: IP(s)?
1256083862 M * geb it will be difficult to provide you more than one or two ipv4
1256083992 M * geb off for now... i have some courses in a few hours, we can talk about that after if you like (if 'll be very pleased to offer you a vserver :) )
1256083996 M * geb have a good night :)
1256084003 M * Bertl k, cya
1256084020 Q * geb Quit: /
1256084090 M * Piet Hi Bertl + daniel_hozac. I heard you're getting more engaged in lxc development, is this correct?
1256084124 M * Bertl not really, well at least not directly :)
1256084126 M * Piet I'm wondering whether your plans are in terms of further development of linux-vserver and lxc. Do you plan to continue maintaining both in the future?
1256084179 M * Piet so linux-vservers will continue to be maintained for a while?
1256084179 M * Bertl we are 'involved' so far as LXC re-implements Linux-VServer, and we re-integrate the mainline features in Linux-VServer (to reduce the patch)
1256084207 M * Piet i see
1256084218 M * Bertl and yes, Linux-VServer will be maintained till the point where LXC can do all the things we do for years now :)
1256084243 M * Piet so, the next 5 years at least ;-)
1256084258 M * Bertl that would be my assumption as well *G* 
1256084315 M * Piet ok, that makes me feel easier. now it's just the issue of debian supposedly dropping support for linux-vserver after squeeze
1256084327 M * Piet which is supposedly < 5 years
1256084350 M * Bertl well, do you use a debian kernel atm?
1256084360 M * Piet yes
1256084368 M * Bertl really? which one?
1256084382 M * Piet 2.6.26
1256084397 M * Bertl despite all the known issues? that's interesting ...
1256084463 M * Piet http://packages.debian.org/lenny/linux-image-2.6-vserver-amd64
1256084466 M * Piet this one
1256084522 M * Piet i'm aware of the issue you run into when migrating guests into or out of such a system
1256084533 M * Piet but i don't do this
1256084542 M * Piet are there others?
1256084555 M * daniel_hozac the question is more, what issues aren't there...
1256084562 M * Bertl quite a number actually .. we had to put up a wiki page
1256084632 M * Piet could you point me to it, please?
1256084642 M * Bertl looking for it as we speak ...
1256084672 M * Piet http://wiki.linux-vserver.org/Installation_on_Debian#Issues_with_the_current_2.6.26_Kernel
1256084673 M * Bertl http://linux-vserver.org/Installation_on_Debian
1256084677 M * Piet probably this
1256084681 M * Bertl yep, correct
1256084691 M * Piet i'll read over it again, thanks
1256084735 M * Bertl btw, it's not just migrating guests in/out, it's also updating to the next/previous kernel 
1256084977 Q * laurent Ping timeout: 480 seconds
1256084981 M * Piet ok, but i can recover from this using the fix you provide there, right?
1256085022 M * Piet i.e. when i upgrade th kernel, i can go over those steps and then run the existing vservers with the new kernel?
1256085030 M * Bertl well, it will be some work to fix up the flags
1256085070 J * laurent ~laurent@AToulouse-157-1-8-115.w86-201.abo.wanadoo.fr
1256085088 M * Bertl but yeah, you can recover :)
1256085104 M * Piet it didn't seem like it would be much more than a couple custom 'find' invocations
1256085104 M * daniel_hozac http://people.linux-vserver.org/~dhozac/t/save-vsdata.sh might help with that.
1256085125 M * Piet thank you, daniel_hozac 
1256085171 M * Piet ok, so i'm not using unification, and i'm not currently using hard cpu scheduling either, just hard memory limits for now
1256085202 M * Piet which means i am still affected by the security issues and the migration issue
1256085233 M * Piet the migration issue i can recover from, and the security risk is something i cannot assess. 
1256085249 M * Piet is this easily exploited if i'm not using unification?
1256085259 M * Bertl still you are happy with the debian kernel :)
1256085284 M * daniel_hozac unification has nothing to do with it.
1256085300 M * Piet i'm not saying i'm happy with it, i'm just wondering how urgent it is to build my own
1256085473 M * Piet hmm apparently there's no debian linux-vserver kernel in squeeze-backports or squeeze, that would have been my easiest option.
1256085515 M * Piet does one of you provide readymade and signed debian kernel images by chance?
1256085516 M * Bertl the thing is, I use a distro kernel every now and then (especially if I need a machine setup quick and dirty), but I do not understand the obsession administrators seem to have with the debian kernels
1256085562 M * daniel_hozac there is a repository, check the mailing list.
1256085582 M * Bertl there is _zero_ advantage of using a prebuilt (debian) kernel, but a number of disadvantages to it ... so I'm still trying to grasp the motivation behind it ...
1256085600 M * Piet Ideally, you get free security support, you'll know when you need to install updates or move away fro something. This didn't work so well here, but it usually works well.
1256085636 M * tam I've been rolling my own since .99pl16...
1256085679 M * Bertl Piet: so, how does that work for you, e.g. today a kernel exploit becomes known, how does that help you with a debian distro kernel?
1256085687 M * Piet I guess it's not just Debian, it's probably sysadmins in general
1256085745 M * Piet Bertl: Using debsecan, I'll be notified about the issue in very short time, and can apply counter measures.
1256085762 M * Bertl okay, like?
1256085838 M * Piet that depends on the security issue. I can disable a service temporarily so I'm no longer exposed to the issue.
1256085854 M * Bertl and you couldn't do that with a custom kernel?
1256085910 M * Piet I could, but I would not get notified
1256085929 M * Bertl so, debian stops notifying you when you use a custom built kernel?
1256085933 M * Piet I'd need to roll my own again, too.
1256085951 M * Bertl you need to install the new one from debian too (and reboot)
1256086029 M * Piet Like on every other OS I know of, if you install unpackaged or packaged-but-not-official software you will not get notice from Debian when this is affected by security issues.
1256086138 M * Piet Another reason not to roll your own kernel is that you can usually rely on the stock kernels to be well tested.
1256086161 M * Piet I..e you save a lot of time testing your customized kernel before deploying it.
1256086166 M * Bertl as proven by the long history of perfect debian Linux-VServer kernels :)
1256086204 M * arachnist Bertl: my sarcasm-o-meter has just exploded
1256086236 M * Piet It may not sound convincing for you, since that's the point of view from which I assume you look on Debian, but my point of view is that it usually works wella nd linux-server in Debian is an exception to the rule.
1256086246 M * Bertl don't get me wrong, I'd be happy to have perfectly tested, well tuned debian Linux-VServer kernels
1256086304 M * Bertl but the fact is, that even distributions like debian, do not give much about testing or fixing issues outside the 'mainline' path
1256086343 M * Bertl and compared to 'mainline' kernels, the distro kernels are even less tested and more broken as we see
1256086371 M * Piet I'm not sure why these packages were more often than not problematic, and I don't want to suggest a reason, since I simply cannot measure it. But seeing that stock kernels already have problems does not make me want to roll my own, it rather makes me think twice if it appears to be such a complex task
1256086372 M * Bertl besides that, they are bloated, which is understandable if you consider the original purpose of a distro kernel
1256086453 M * Piet Right, distro kernels being complex is an argument for rolling your own, true.
1256086648 M * Piet Anyway, I think I have provided some valid reasons to consider stock kernels to be of value, out of a sysadmins' point of view. I'm sure others could add more to this, if you want to listen to them, too.
1256086682 M * Bertl okay, thanks :)
1256086712 M * Piet thanks, too, I'm glad you'll continue development.
1256086748 M * Bertl feel free to speed things up by helping out somewhere (or donating something)
1256086877 M * arachnist Piet: for stock kernels to be of value, they have to be maintained properly. with a large set of identical machines and stock kernels being lesser quality than what a competent sysadmin could deliver, would you still choose to run a stock distribution kernel?
1256087208 M * Piet arachnist: the point is, how much less is that quality, does it introduce security issues which are likely to be exploitable (not just 'exploited') in the way you use a software, does it introduce stability problems you cannot cope with, and how much do you loose on the contrary.
1256087238 M * Piet it's always a matter of assessing your needs and options.
1256087246 M * Piet and risks
1256087389 M * Piet Bertl: i'm afraid i don't have much income these days, so am just self-sustaining, so I won't be able to donate. I'm also involved in a couple other things so don't have much free time to spend on linux-vserver or any other project i'm not already involved in. So I'm sorry I cannot currently support linux-vserver development other than by filing bugs and possibly discuss on the mailing lists.
1256087439 M * Piet I'm always happy to provide my POV on things if you should ever need it.
1256087471 M * Bertl good to know ...
1256089200 M * Piet Sorry if that's disappointing, I value your work very much.
1256089400 J * imcsk8 ~ichavero@189.155.102.123
1256089663 M * Bertl no problem, I'm not easily disappointed ... have fun
1256090331 M * Piet And you.
1256090401 Q * imcsk8 Quit: This computer has gone to sleep
1256090526 M * tam Bertl- Did you get that tar ball?
1256090726 M * Bertl yep, sec
1256090758 J * imcsk8 ~ichavero@189.155.102.123
1256091543 Q * imcsk8 Quit: This computer has gone to sleep
1256091579 M * Bertl tam: well, first, it's not really Linux-VServer related, you can check that by simply doing chroot /path/to/guest (which will hang too)
1256091630 M * Bertl I'm currently trying to figure what happens, but looks like something is trying to write to /dev/log before the logger is started (repeatedly)
1256091675 M * tam I believe that...
1256091823 M * tam running the chroot by hand, I had not considered that
1256092031 M * tam OH MY GOD.
1256092040 M * tam I know what the issue is.
1256092043 A * tam curses himself.
1256092054 Q * nkukard_ Quit: Leaving
1256092116 M * Bertl it seems to be bash which causes this
1256092181 M * Bertl (but could as well be a (preload) library)
1256092342 M * tam So, I was messing around with ldap authentication for users
1256092370 M * tam and it turns out, that if you put ldap before files in /etc/nsswitch.conf, you'll be a sad camper when i comes time to restart your vserver.
1256092393 M * tam bash will try to log to /dev/log before klog is started
1256092394 M * Bertl especially if ldap does not answer :)
1256092397 M * tam yep
1256092409 A * tam head -> wall.
1256092438 M * Bertl glad it could be resolved and joined the 99% of non-Linux-VServer related issues :)
1256092469 M * tam me too.
1256094068 J * saulus_ ~saulus@c152249.adsl.hansenet.de
1256094475 Q * SauLus Ping timeout: 480 seconds
1256094477 N * saulus_ SauLus
1256096495 J * derjohn_foo ~aj@c152236.adsl.hansenet.de
1256096908 Q * derjohn_mob Ping timeout: 480 seconds
1256101648 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr
1256102122 M * yang Bertl: do you have a pre-made kernel .config for i386 ?
1256102171 J * yarihm ~yarihm@77-58-27-102.dclient.hispeed.ch
1256102776 J * Piet_ ~piet@04ZAABNEW.tor-irc.dnsbl.oftc.net
1256102833 Q * Piet Ping timeout: 480 seconds
1256103373 Q * yarihm Ping timeout: 480 seconds
1256105249 M * ghislainocfs2 i do not know what it is intended for but there exist http://vserver.13thfloor.at/ExperimentalT/2.6.24-rc6-vs2.2.x.config
1256105262 M * ghislainocfs2 beware i do not tell bertl put it here for use by others
1256105274 M * ghislainocfs2 i just tell this file exist
1256105337 M * ghislainocfs2 best bet for a start is to  zcat  /proc/config.gz then work on it :)
1256106135 J * davidkarban ~david@199.123.broadband11.iol.cz
1256106322 J * ncopa ~ncopa@90.149.48.245
1256106726 J * sharkjaw ~gab@64.28.12.166
1256106800 J * yarihm ~yarihm@77-58-27-102.dclient.hispeed.ch
1256106858 Q * yarihm 
1256107230 Q * derjohn_foo Ping timeout: 480 seconds
1256108420 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk
1256108570 M * Bertl off to bed now ... have a good one everyone!
1256108609 N * Bertl Bertl_zZ
1256108826 J * derjohn_foo ~aj@tmo-100-84.customers.d1-online.com
1256108959 Q * BenG Quit: I Leave
1256111884 J * kir ~kir@swsoft-msk-nat.sw.ru
1256113991 J * mrfree ~mrfree@host1-89-static.40-88-b.business.telecomitalia.it
1256114087 J * Shinsaku ~Shinsaku@chello089076140236.chello.pl
1256115382 Q * DreamerC Quit: leaving
1256115398 J * DreamerC ~DreamerC@122-116-181-118.HINET-IP.hinet.net
1256115872 Q * DreamerC Quit: leaving
1256115888 J * DreamerC ~DreamerC@122-116-181-118.HINET-IP.hinet.net
1256120720 J * renihs ~lemming@83-65-34-34.arsenal.xdsl-line.inode.at
1256120801 M * renihs hmm what could be missing if the "vserver guest name" does not show up on the logical ip-adresses on the host itself?
1256120815 M * renihs e.g eth0:wiki Link encap: ....
1256120906 M * renihs in essence, the logical ips of the vserver guests dont show up at all on the vserver host system
1256120928 M * PowerKe you tried: ip a l
1256124581 J * Pazzo ~ugelt@reserved-225136.rol.raiffeisen.net
1256124856 J * blathijs ~matthijs@drsnuggles.stderr.nl
1256124901 M * blathijs How does vserver relate to the mainlain containers work (lxc)?
1256124935 M * blathijs Will LXC replace the vserver patches, hinder vserver's work, or is lxc work from the vserver patches perhaps?
1256125792 Q * scientes Ping timeout: 480 seconds
1256126229 M * _Shiva_ blathijs: see recent (<- yesterday) discussion on this channel: http://irc.13thfloor.at/LOG/2009-10/LOG_2009-10-20.txt
1256126320 J * doener ~doener@i59F54FFE.versanet.de
1256126328 M * _Shiva_ blathijs: or http://irc.13thfloor.at/LOG/2009-10/LOG_2009-10-15.txt starting @ 1255627806
1256126344 M * blathijs _Shiva_: Thanks
1256126421 M * _Shiva_ Bertl_zZ: the archives need to be searchable :-) (CC-ping @ Hollow)
1256126425 Q * doener_ Ping timeout: 480 seconds
1256126440 Q * Shinsaku 
1256126452 M * SpComb and Ctrl-f doesn't qualify? :)
1256126482 M * _Shiva_ SpComb: if you know on what day exacly you want to look for - then yes :-)
1256126520 A * SpComb has a HyperEstraier-powered IRC log search
1256126538 M * SpComb but the irssi log format used in those logs looks neat, have a link for it somewhere?
1256126798 Q * marl_scot Ping timeout: 480 seconds
1256127507 N * Bertl_zZ Bertl
1256127507 Q * davidkarban Read error: Connection reset by peer
1256127512 M * Bertl morning folks!
1256127549 J * davidkarban ~david@199.123.broadband11.iol.cz
1256127567 M * ncopa morning
1256127569 M * Bertl _Shiva_: google usually does a good job in indexing them
1256127626 A * ncopa is working on wizard (cli script) to set up an alpine vserver
1256127630 M * Bertl renihs: doesn't show up where? and what kernel/patch/tool versions?
1256127637 M * Bertl ncopa: cool!
1256127650 M * ncopa well, vserver guests that is
1256127656 M * ncopa and template
1256127661 M * ncopa i think vserver host is working
1256127820 M * renihs Bertl, shows (not) up in:  ifconfig -a ,kernel: 2.6.22-vs2.2.0.7, utils: 0.30.215-r3
1256127848 M * _Shiva_ Bertl: you mean with site-search? like: http://www.google.de/#q=site%3Airc.13thfloor.at+lxc
1256127886 M * Bertl renihs: how is the IP configured (on the host, in the guest config/interfaces)
1256127917 M * renihs in the guest its being set with /etc/vserver/interfaces
1256127922 M * Bertl _Shiva_: yes, I think we also have a search link for that on 13thfloor.at
1256127928 M * renihs the host itself, hmm its a gentoo, i assume with ifconfig / or ip 
1256127952 M * Bertl I'm interested in the /etc/vservers/<name>/interfaces part
1256127988 M * Bertl _Shiva_: 
1256127995 M * Bertl http://www.13thfloor.at/vserver/search/
1256128053 M * renihs Bertl, /etc/vserver/template/interfaces/0/ includes files: dev (eth0), ip (some private ip), and prefix (24)
1256128087 M * _Shiva_ Bertl: tnx
1256128141 M * Bertl renihs: so, then you are using secondaries, not aliases (which IMHO is a good thing) thus the alias name is not present (on host or guest)
1256128183 M * renihs Bertl, hmmm good pointer hmm let me check that
1256128187 J * balbir_ ~balbir@122.248.163.1
1256128239 M * Bertl renihs: you can, if you really want :) use the 'name' entry to make it an alias
1256128267 M * renihs Bertl, hmm hold on, which "name" entry are you refering to (or which alias?)
1256128399 M * Bertl let me explain: in the old ages (centuries ago :) network interface aliases were introduced to allow to configure more than one IP per interface ... they take the form <dev>:<name>
1256128462 M * Bertl almost a century ago, they were 'replaced' by a new way to specify additional addresses, called 'secondaries' which basically add another IP to the same interface (no :<name> part necessary)
1256128514 M * Bertl the 'old' tool to manage interfaces is 'ifconfig', which should have been replaced (several years ago) with 'ip' from 'iproute(2)'
1256128546 M * Bertl now, if you put an entry 'name' in /etc/vservers/<guest>/interfaces/<id>/
1256128563 M * renihs (reading but on phone)
1256128566 M * Bertl it will be used (on guest startup, so shut the guest down before chaning)
1256128580 M * Bertl to form an alias, <dev>:<name>
1256128614 M * Bertl if that one is missing, you'll get the modern 'secondary' which doesn't have a separate :<name> part
1256128684 M * ghislainocfs2 bertl: does they have different behavior kernel wise  alias or secondaries ?
1256128720 M * Bertl slighly, but only on the inquiry part
1256128736 M * Bertl i.e. ifconfig is not able to see secondaries
1256129132 M * renihs Bertl, so using iproute2 would solve the issue
1256129137 M * renihs which is "standard" since 1995 :)
1256129142 M * renihs let me check that
1256129167 M * Bertl depends on what you consider 'the issue' :)
1256129309 M * renihs hmm in ip addr show i see the secondary ip
1256129321 M * renihs it would be nice to correlate that to the vserver guest name though hmmm
1256129346 M * Bertl well, there could be several guests using the same IP :)
1256129358 M * renihs hmm true, that i didnt consider
1256129371 M * Bertl but a simple script, walking the config tree, checking for 'ip' entries would work
1256129380 M * renihs Bertl, hmm thats exactly my though
1256129383 M * renihs thought :)
1256129402 M * Bertl it could list all the assigned IPs, if you tend to change them on the fly, you could also check with /proc/virtnet first
1256129477 M * renihs perfect! exactly what i wanted :)
1256129482 M * renihs thanks alot (as always)
1256129515 J * thierryp ~thierry@home.parmentelat.net
1256129525 M * Bertl you're welcome! if you actually write such a script, it might be nice to post it on the ML and/or link it on the wiki
1256129745 M * renihs Bertl, shouldnt be an problem, at least the script will have some "quality" aspects then :)
1256129786 M * renihs (usually my scripts and those from my collegues are functional but plain ugly :)
1256129954 M * daniel_hozac tail /etc/vservers/*/interfaces/*/ip is what i use...
1256129967 M * arekm was some new company sponsoring vserver development recently?
1256129984 M * daniel_hozac or, on systems where that's too long, grep '' /etc/vservers/*/interfaces/*/ip
1256130024 M * Bertl arekm: you mean the stabilization (and besides DreamHost)?
1256130053 M * arekm dreamhost, that was it
1256130088 M * renihs daniel_hozac, y, for me that would suffice too, but i guess i will make some vip or alike script (for special admins)
1256130140 M * arekm uhnm, they don't support ipv6 I guess, badd :>
1256130161 M * Bertl hehe, don't worry, we'll get to it ...
1256130430 M * arekm ehehe, and they specify cpu power in MHz for vserver
1256130481 Q * mrfree Ping timeout: 480 seconds
1256130793 J * jrdnyquist ~jrdnyquis@slayer.caro.net
1256130861 Q * Piet_ Remote host closed the connection
1256131014 J * Piet_ ~piet@04ZAABNOY.tor-irc.dnsbl.oftc.net
1256131149 J * mrfree ~mrfree@host1-89-static.40-88-b.business.telecomitalia.it
1256131389 M * Bertl arekm: but you know, the fastest way to speed-up the ipv6 fix is to help with the test script
1256131456 M * arekm I know, I'm too lazy, I admit :-(
1256131498 M * arekm doing too much in parallel at work
1256132052 J * raceme ~tof@ombos.raceme.org
1256132061 M * raceme hello
1256132283 M * Bertl hey raceme!
1256132338 M * raceme this is driving me nut... I fail to make a dummy network config on 2.2 vserver. I dedicated a eth0 alias to a vserver (eth0:31), so i've got nodev, ip and prefix... In the guest ssh bind to 0.0.0.0 fails :(
1256132342 M * raceme hello Bertl !
1256132347 J * barismetin ~baris@wlab34.inria.fr
1256132425 M * daniel_hozac did you restrict your host's sshd to the host's IP address(es)?
1256132451 M * raceme daniel_hozac: I knew that I forgot something essential :(
1256132553 Q * mrfree Ping timeout: 480 seconds
1256132566 M * raceme daniel_hozac: thanks it was that
1256133116 J * Shinsaku ~Shinsaku@chello089076140236.chello.pl
1256133601 Q * sharkjaw Remote host closed the connection
1256134074 Q * thierryp Quit: ciao folks
1256134078 Q * hijacker Quit: Leaving
1256134200 J * mrfree ~mrfree@host1-89-static.40-88-b.business.telecomitalia.it
1256134248 J * thierryp ~thierry@home.parmentelat.net
1256134453 Q * derjohn_foo Ping timeout: 480 seconds
1256134828 Q * mrfree Ping timeout: 480 seconds
1256135414 M * Bertl off to buy some groceries ... bbl
1256135421 N * Bertl Bertl_oO
1256135501 Q * balbir_ Ping timeout: 480 seconds
1256135718 M * ncopa where should i send patches for util-vserver?
1256135725 M * ncopa to the vserver mailing list?
1256135869 J * derjohn_foo ~aj@80.85.196.112
1256136291 J * mrfree ~mrfree@host1-89-static.40-88-b.business.telecomitalia.it
1256136337 M * mnemoc ncopa: yes
1256137089 Q * thierryp Quit: ciao folks
1256137675 J * ryker ~ryker@199.117.46.145
1256137718 M * ryker hi all.  I'm surprised I couldn't find this when googling, but can I run an NFS server in a guest?
1256137732 M * ryker I'm trying to setup NFSv4, but even NFSv3 would be fine
1256137810 M * ryker I've never setup nfsv4 at all before, so I'm not sure if the error I'm getting is because I messed up, or a vserver guest issue
1256137824 M * ryker when I try to start the nfs service, I get: 'Error: RPC MTAB does not exist'
1256138207 M * ghislainocfs2 ryker: if you do the same in the host does it fail ?
1256138223 M * ryker i don't have nfs setup on the host.  trying to avoid that.
1256138239 M * ryker looking at the init script, it looks like it's looking for 'sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs'
1256138247 M * ryker and this isn't available in a guest
1256138256 M * ryker it is on the host though
1256138283 M * ghislainocfs2 why is isn't ? is it a standard file  or something else ?
1256138376 Q * Shinsaku Ping timeout: 480 seconds
1256138499 M * ryker not sure
1256138601 M * ryker yeah, it seems to be a valid mount point that I can browse
1256138606 M * ryker sunrpc is a kernel module
1256138639 M * ryker that is, i can browse it on the host, not guest
1256138647 M * ryker so, i guess i'll do some more research
1256138649 M * ryker thx
1256138749 M * ghislainocfs2 ok sry not being able to help more :)
1256138796 M * ryker ghislainocfs2: you've helped
1256138810 M * ryker i think i'm going to try a bind mount and see if that works
1256138904 Q * FloodServ synthon.oftc.net services.oftc.net
1256138984 J * FloodServ services@services.oftc.net
1256139192 J * geb ~geb@earth.gebura.eu.org
1256139240 M * ryker well, doing a bind mount kind of worked.  Now I get a different error about not being able to access modules.dep
1256139241 M * geb hi
1256139270 M * ryker hi geb 
1256139279 Q * davidkarban Quit: Ex-Chat
1256139993 J * dna_ ~dna@p54BC9FEA.dip0.t-ipconnect.de
1256140329 Q * kir Quit: Leaving.
1256141099 J * dna__ ~dna@p54BC9FEA.dip0.t-ipconnect.de
1256141192 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1256141481 Q * dna_ Ping timeout: 480 seconds
1256141547 Q * mrfree Ping timeout: 480 seconds
1256141584 Q * Pazzo Quit: Bye!
1256141750 J * imcsk8 ~ichavero@148.229.1.11
1256142647 N * Bertl_oO Bertl
1256142648 M * Bertl back now ...
1256142693 M * Bertl ryker: what are you trying to accomplish?
1256142829 N * DoberMann[ZZZzzz] DoberMann[PullA]
1256144267 Q * geb Ping timeout: 480 seconds
1256144923 N * Piet_ Piet
1256144946 J * geb ~geb@79.82.4.173
1256145168 Q * derjohn_foo Ping timeout: 480 seconds
1256145696 J * derjohn_foo ~aj@80.85.196.112
1256145981 J * dna_ ~dna@p54BC9FEA.dip0.t-ipconnect.de
1256145993 Q * barismetin Remote host closed the connection
1256146372 Q * dna__ Ping timeout: 480 seconds
1256147447 J * dna__ ~dna@p54BC9FEA.dip0.t-ipconnect.de
1256147588 Q * dna_ Ping timeout: 480 seconds
1256149673 Q * dna__ Read error: Connection reset by peer
1256149828 J * dna_ ~dna@p54BC9FEA.dip0.t-ipconnect.de
1256151441 Q * derjohn_foo Ping timeout: 480 seconds
1256152138 N * laurent lau
1256152194 P * lau bye vservers' addict!
1256152653 Q * dna_ Ping timeout: 480 seconds
1256152869 Q * ryker Quit: leaving
1256153195 Q * FireEgl Ping timeout: 480 seconds
1256153200 J * dna_ ~dna@p54BC9FEA.dip0.t-ipconnect.de
1256153799 J * FireEgl FireEgl@173-16-9-10.client.mchsi.com
1256154010 J * scientes ~scientes@174-21-161-91.tukw.qwest.net
1256158183 J * derjohn_foo ~aj@c152236.adsl.hansenet.de
1256159626 Q * DreamerC Ping timeout: 480 seconds
1256160358 J * dna__ ~dna@p54BC9FEA.dip0.t-ipconnect.de
1256160385 N * DoberMann[PullA] DoberMann[ZZZzzz]
1256160537 Q * dna__ 
1256160728 Q * dna_ Ping timeout: 480 seconds
1256160821 J * blues ~blues@dqr83.neoplus.adsl.tpnet.pl
1256160938 Q * blues_ Ping timeout: 480 seconds
1256161307 Q * bonbons Quit: Leaving
1256161341 M * micah Bertl: do you know when was the TB scheduler added?
1256161425 M * Bertl hmm, a few years ago, why?
1256161463 M * daniel_hozac during the 1.9 cycle, IIRC.
1256161628 M * micah Bertl: we identified that the TB scheduler was missing in the debian lenny kernel, I'm trying to find out if the TB scheduler was in etch. that would make it a regression that can be fixed in a stable update
1256161650 M * daniel_hozac yes, it was in etch.
1256161667 M * daniel_hozac just... not a very good version of it.
1256161680 M * daniel_hozac (surprise surprise)
1256161700 M * Bertl micah: a regression in a debian kernel?
1256161730 M * micah could it be possible?!
1256161740 M * Bertl nah!
1256161744 M * micah you are right, it must not be possible
1256161746 M * micah ;)
1256161855 M * micah i'm trying to understand delta-sigkill-fix01.diff... it seems like maybe
1256161866 M * micah may let you send signals to init that you shouldn't be able to? no
1256161891 M * micah i dont understand it, why pid needs to be > 1 when it already checks for initpid?
1256161934 M * Bertl because there are pid spaces too
1256162032 M * micah pid spaces are like pid contexts?
1256162044 M * geb haha
1256162056 M * Bertl kind of, just mainline and a little different
1256162076 M * Bertl think virtualization instead of isolation
1256162128 M * micah is this the e. biederman implementation?
1256162162 M * daniel_hozac among others.
1256162185 M * Bertl I think he isn't even credited somewhere :)
1256162204 M * geb micah, somebody told me about a possible tag of vserver as deprecated in squeeze , i am a bit sceptic ... do you know if there is something like it planned ?
1256162254 M * geb maybe it is just a new urban legend :)
1256162437 M * micah geb: the current kernel team thinks that is the plan, but that is like 3 years from now, so who knows
1256162444 M * micah 3 years ago the kernel team was very different
1256162521 M * micah hmm, maybe its because pid needs to be > 1 because initpid is wrong, but then why not drop initpid?
1256162581 M * geb Bertl, only  3 years left ... and you'll be unable to troll about debian :)
1256162599 M * micah hehe
1256162608 M * geb micah, i just find http://lists.debian.org/debian-kernel/2009/10/msg00613.html :)
1256162617 M * micah yes thats right
1256162686 M * zbyniu Bertl: hi, last you merged some patches from PLD, but you made a typo, here is fix - http://pld.pastebin.com/f5eab5642
1256162758 M * micah aha: https://lists.linux-foundation.org/pipermail/containers/2008-October/013823.html
1256162791 M * Bertl zbyniu: ah, yeah, copy/paste error
1256162845 M * Bertl will be fixed in the next release
1256163154 M * zbyniu thnx :)
1256163177 M * Bertl thanks for spotting it! I presume, somebody actually uses it on ppc?
1256163325 M * geb micah, anyway, fell free to ask for testing, help, etc if it could help... :)
1256163369 M * micah geb: heheh, maybe you can work on building the next sid/testing kernel ;)
1256163428 M * zbyniu Bertl: hmm, i think somebody was in nov 2008
1256163474 Q * ghislainocfs2 Quit: Leaving.
1256163484 M * geb micah, is there a specific debian+vserver mailinglist ?
1256163713 M * micah geb: no, its just the debian-kernel list
1256163770 M * geb ok thanks
1256163954 M * geb i'll subscribe and look at kernel generation,testing,stabilisation process
1256164008 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk
1256164701 M * geb off for now, good bye everyone
1256164712 M * Bertl cya
1256164808 Q * geb Quit: /
1256165448 J * FredR ~frederic@vedra.tuxonet.be
1256165451 M * FredR Hello
1256165489 M * FredR i'm logging into the vserver in ssh... if i type reboot, the host reboots, why
1256165650 M * arachnist FredR: because you have bad things in /dev in the vserver
1256165652 M * daniel_hozac have you restricted your host's sshd to the host's IP address(es)?
1256165690 M * arachnist FredR: that, or there's a possibility that you use a bind-mount from the host for /dev
1256165728 M * FredR i only mount proc
1256165756 M * FredR i'm reading the faq (how can i reboot the guest ;-)
1256165940 M * FredR thank you
1256165942 Q * FredR Quit: leaving
1256165979 Q * imcsk8 Quit: Leaving
1256168104 J * carnage_ ~carnage@voip-colo-74-86-148-74.link2voip.com
1256168222 Q * carnage Ping timeout: 480 seconds
1256168554 Q * micah resistance.oftc.net larich.oftc.net
1256168617 J * micah ~micah@micah.riseup.net
1256169484 Q * jrdnyquist resistance.oftc.net charm.oftc.net
1256169484 Q * mugwump resistance.oftc.net charm.oftc.net
1256169484 Q * agaffney resistance.oftc.net charm.oftc.net
1256169484 Q * tam resistance.oftc.net charm.oftc.net
1256169484 Q * mEDI_S resistance.oftc.net charm.oftc.net
1256169484 Q * mnemoc resistance.oftc.net charm.oftc.net
1256169484 Q * gerrit resistance.oftc.net charm.oftc.net
1256169500 J * jrdnyquist ~jrdnyquis@slayer.caro.net
1256169500 J * mugwump ~samv@watts.utsl.gen.nz
1256169500 J * agaffney ~agaffney@71-81-81-131.dhcp.stls.mo.charter.com
1256169500 J * mnemoc ~amery@shell.opensde.net
1256169500 J * mEDI_S ~medi@255.255.255.255.li
1256169500 J * tam ~tam@gw.nettam.com
1256169500 J * gerrit ~gerrit@ionscale.com