1238371875 J * FireEgl Proteus@2001:470:e056:1:4::9
1238373830 J * nenolod nenolod@petrie.dereferenced.org
1238374481 J * saulus_ ~saulus@c207144.adsl.hansenet.de
1238374890 Q * saulus Ping timeout: 480 seconds
1238374890 N * saulus_ SauLus
1238378453 J * aj__ ~aj@e180192152.adsl.alicedsl.de
1238378880 Q * derjohn_foo Ping timeout: 480 seconds
1238379441 Q * Piet Quit: Piet
1238382606 J * nas ~chatzilla@opengw.lga.net.sg
1238382650 M * nas guys has anyone of you tried this vserver version (2.6.28.7 -- vs2.3.0.36.8) on debian lenny?
1238382656 M * nas how is it so far?
1238385851 Q * balbir_ Ping timeout: 480 seconds
1238386512 J * balbir_ ~balbir@122.172.58.57
1238387030 Q * FireEgl Remote host closed the connection
1238387051 Q * scientes Ping timeout: 480 seconds
1238387380 Q * balbir_ Quit: Ex-Chat
1238387402 J * balbir_ ~balbir@122.172.58.57
1238387437 Q * arew264 Remote host closed the connection
1238387961 J * scientes ~scientes@75-165-23-30.tukw.qwest.net
1238388030 J * FireEgl FireEgl@173-16-9-10.client.mchsi.com
1238389352 Q * aj__ Ping timeout: 480 seconds
1238389861 J * doener ~doener@i59F55306.versanet.de
1238389947 Q * doener_ Ping timeout: 480 seconds
1238391535 Q * SauLus Remote host closed the connection
1238392704 J * cluk ~cluk@p5B17F77B.dip.t-dialin.net
1238393013 J * sharkjaw ~gab@149-240-82.oke2-bras6.adsl.tele2.no
1238393032 Q * balbir_ Ping timeout: 480 seconds
1238393057 Q * hparker Quit: Read error: 104 (Peer reset by connection)
1238393459 J * davidkarban ~david@193.85.217.71
1238393862 Q * nas Quit: ChatZilla 0.9.83 [Firefox 3.0/2008061015]
1238394287 J * jz ~jesper@gw.comsys.informatik.uni-kiel.de
1238394604 N * jz jze
1238394669 J * esa bip@62.123.8.120
1238395133 J * esa` bip@62.123.8.131
1238395152 Q * esa Ping timeout: 480 seconds
1238395473 J * balbir_ ~balbir@59.145.136.1
1238395748 Q * cluk Quit: Ex-Chat
1238396060 J * nas ~chatzilla@opengw.lga.net.sg
1238396117 M * nas guys there is no initrd-tools in lenny but my vserver kernel creation involves this step "make-kpkg -–revision=1 –-initrd kernel-image"
1238396128 M * nas will it be ok without the initrd option
1238397599 M * pmjdebru1jn depends on how you configured your kernel
1238397618 M * pmjdebru1jn if your storage drivers are built-in (instead of modules) you're probably fine...
1238398078 J * pmenier ~pme@LNeuilly-152-22-72-5.w193-251.abo.wanadoo.fr
1238398339 J * saulus ~saulus@c207227.adsl.hansenet.de
1238398670 J * Punkie ~Punkie@2a01:5f0:1:80:216:d4ff:fe05:5987
1238398671 J * ktwilight ~ktwilight@91.178.149.196
1238398905 Q * ktwilight_ Ping timeout: 480 seconds
1238398937 J * harobed ~harobed@pda57-1-82-231-115-1.fbx.proxad.net
1238399235 N * pmjdebru1jn pmjdebruijn
1238399981 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk
1238399996 M * bastiaan re
1238400010 M * bastiaan Bertl_zZ: not yet
1238400033 M * bastiaan Bertl_zZ: 2.6.26-1-vserver-686 #1 SMP Fri Mar 13 21:04:35 UTC 2009 i686 GNU/Linux
1238400070 M * bastiaan Bertl_zZ: I am about to write a bug report / mail to linux-vserver and debian people, also to ask for more information
1238400257 M * BenG bastiaan, only just arrived, what have you found? I'm using that kernel too
1238400308 M * bastiaan BenG: all outgoing ipv6 connections from all vservers originate from the same IP adress 
1238400320 M * bastiaan BenG: which is the last IP adress added to the interface
1238400333 M * bastiaan BenG: (so the last vserver that has started)
1238400367 M * BenG welll found!
1238400380 M * BenG not using ipv6 here
1238401753 J * yarihm ~yarihm@20-53-239-77-pool.cable.fcom.ch
1238402748 J * gnuk ~F404ror@pla93-3-82-240-11-251.fbx.proxad.net
1238403221 J * ktwilight_ ~ktwilight@91.178.147.190
1238403566 Q * yarihm Quit: This computer has gone to sleep
1238403617 Q * ktwilight Ping timeout: 480 seconds
1238404433 Q * scientes Ping timeout: 480 seconds
1238405144 J * thierryp ~thierry@zircon.inria.fr
1238405169 Q * BenG Quit: I Leave
1238406647 J * ktwilight__ ~ktwilight@91.178.152.180
1238406647 Q * ktwilight_ Read error: Connection reset by peer
1238406774 J * ktwilight_ ~ktwilight@91.178.152.209
1238407131 Q * ktwilight__ Ping timeout: 480 seconds
1238407246 J * ktwilight__ ~ktwilight@91.178.144.63
1238407420 N * Bertl_zZ Bertl
1238407424 M * Bertl morning folks!
1238407454 M * Bertl bastiaan: please try with a different kernel first, the 2.6.26 debian kernel is known to be broken ...
1238407635 Q * ktwilight_ Ping timeout: 480 seconds
1238407693 J * cga ~weechat@194.244.1.164
1238407980 J * cluk ~cluk@p5B17F77B.dip.t-dialin.net
1238408097 M * Bertl nas: only very special kernel setups work without initramfs since 2.6.17 or so, I would not suggest to create those setups unless you know exactly what you are doing ... any distro updated in last three years simply has to provide tools to build and config the initramfs
1238408109 Q * cehteh Ping timeout: 480 seconds
1238408373 J * kir ~kir@swsoft-msk-nat.sw.ru
1238408463 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk
1238408854 M * bastiaan Bertl: really? Isn't it the official kernel of debian 5.0 ?
1238408893 M * sid3windr bastiaan: does that mean it can't be broken? :P
1238408920 M * bastiaan Bertl: you're right about that btw, if I try my old 2.6.22.19 kernel there are no ipv6 related problems
1238408956 M * bastiaan sid3windr: well I wonder about what's wrong with that kernel, and what would be the replacement kernel for stable
1238408979 M * bastiaan if I go back tot 2.6.22 I get scary warnings about my file systems
1238409025 M * Bertl try with 2.6.27.x or 2.6.28.x
1238409124 M * bastiaan is there a repository for pre-build kernels with that version?
1238409158 M * bastiaan better question: is there a repository with pre-build >2.6.26 kernels for stable?
1238409178 M * ard bastiaan is probably capable of building kernels himself :-)
1238409181 M * bastiaan (yes I can also build my own of course)
1238409199 M * ard and that's my advise ;-)
1238409204 M * bastiaan ard: http://wiki.welmers.net/en/Building_Debian_Kernel :)
1238409253 M * bastiaan but I prefer debian-maintained kernel packages, actually
1238409254 A * ard would leave out the initrd part
1238409263 A * ard never builds a kernel that needs one
1238409288 A * ard wonders where bastiaan was yesterday...
1238409301 M * bastiaan ard: that would mean you build machine-specific kernels for each server?
1238409313 M * bastiaan server... -> machine
1238409341 M * ard yes, I build 2..4 types of kernels: 64 bit core2 and P4, and 32bit P3, and one for my workstation
1238409352 M * ard it satisfies the need for 300 servers or so :-)
1238409352 M * bastiaan ard: yesterday? I was driving a bit arround to make away my hangover
1238409352 M * Bertl bastiaan: well, you have to talk to the debian kernel maintainers then :)
1238409363 M * bastiaan ard: (of saturday)
1238409404 M * Bertl and yes, a system specific kernel makes a lot more sense than using a generic distro kernel (which includes the kitchensink)
1238409425 M * ard at home I also have about 5 kernels. (mips and arm also ;-) )
1238409441 M * bastiaan ow I'm on #vserver
1238409475 M * ard yes :-)
1238409478 M * bastiaan a little mistaken (it's still sort of monday-morning)
1238409611 M * bastiaan but I'll try to fix that with debian people
1238409638 M * ard the ipv6 problem?
1238410109 A * ard is going to build a 2.6.29
1238410130 A * ard 's workstation keeps panicking (probably a reiser bug)
1238410214 M * Bertl still using reiserfs?
1238410236 M * ard It's a *very* *old* installation ;-)
1238410248 M * ard well, not that old, 2004 or 2005 or so
1238410303 M * ard around 2005/2006 we decided to use ext3 with btree options instead of reiserfs, since we have nothing but trouble with reiserfs and 2.6 kernels
1238410322 M * ard although at home it still works (2003 installation)
1238410337 M * Bertl yeah, well, btrfs to the rescue :)
1238410359 M * pmjdebruijn talking about SciFi are we?
1238410370 M * Bertl it's in 2.6.29 actually
1238410380 M * pmjdebruijn declared stable?
1238410401 A * ard is going to test it on his workstation
1238410405 M * Bertl most features in 2.6.29 require 'EXPERIMENTAL' as config
1238410409 A * ard is now fixin a serial console
1238410425 M * Bertl but as the kernel is declared stable, the filesystems are too, no? :)
1238410429 M * pmjdebruijn didn't they only just declared the ondisk dataformat preliminary stable
1238410441 M * pmjdebruijn Bertl: I really don't think so
1238410464 M * Bertl probably as stable as reiserfs ever was :)
1238410471 M * pmjdebruijn hehe
1238410484 M * pmjdebruijn Bertl: that's true depending on your opinion on ReiserFS
1238410493 M * Bertl I loved the idea reiserfs introduced, but the code and implementation was always horrible
1238410514 M * Bertl and I never ever had a good experience with reiserfs in production
1238410517 M * pmjdebruijn http://btrfs.wiki.kernel.org/index.php/Changelog
1238410892 M * pmjdebruijn the more I work with other filesystems, the more I appreciate ext3
1238410926 M * ard it has 1 big problem: > 32768 directories
1238410930 Q * nas Remote host closed the connection
1238410939 M * ard or is that issue already addressed?
1238410958 M * pmjdebruijn no, I think that got addressed in ext4
1238410965 M * pmjdebruijn for that's no  issue here
1238410968 M * pmjdebruijn is it for you?
1238410975 M * ard yes :-)
1238410977 M * pmjdebruijn ok
1238410980 M * pmjdebruijn well there xfs then
1238410984 M * pmjdebruijn and ext4 soon
1238410994 M * pmjdebruijn the last import fix to ext4 will make it into 2.6.30
1238410998 M * Bertl well, I'm experiencing strange behaviour with ext3 on very large filesystems ... like mkdir taking a minute to finish and so
1238411001 M * ard Hmmm, reiser4 was more stable in my tests than xfs or jfs
1238411015 A * pmjdebruijn never consider reiser4 for anything
1238411030 M * pmjdebruijn ard: the fact that it never made it into mainline, tell something about code quality
1238411033 M * ard we've tried ext4, reiser4 and ext3
1238411034 M * pmjdebruijn xfs had issues with that as well
1238411046 M * pmjdebruijn simply because at the beginning the xfs port was pretty poor
1238411064 M * Bertl xfs is still mutating every second release
1238411066 M * ard well, xfs and jfs were in mainline, but I've had even more problems with them than with reiser 3 ;-)
1238411117 M * pmjdebruijn define "problems"?
1238411138 M * ard in the jfs case I first suspected drbd, and then I quit using drbd, and it still just locked somewhere
1238411139 M * pmjdebruijn Bertl: yeah
1238411159 M * ard probably some race conditions with locking
1238411167 M * ard or better with unlocking
1238411173 M * pmjdebruijn uhm
1238411193 M * pmjdebruijn ard: you're not supposed to mount for a single block device on two servers
1238411196 M * pmjdebruijn it's not a clustered fs
1238411204 M * ard drbd is a raid1
1238411212 M * ard and even with remote connected, jfs locked
1238411219 M * ard and even without drbd, jfs locked
1238411224 M * pmjdebruijn what raid it is doesn't matter
1238411231 M * pmjdebruijn you can ever only mount jfs once
1238411241 M * ard yes, that has nothing to do with drbd
1238411251 M * pmjdebruijn true
1238411269 M * pmjdebruijn many folks think with drbd that you can magically mount the fs multiple times
1238411281 M * pmjdebruijn anyway
1238411288 M * pmjdebruijn most fs problems arise from unreliable storage
1238411292 M * ard well, you have to do a lot of work for drbd to expert 2 writable block devices ;-)
1238411297 M * pmjdebruijn some filesystems just handle the unreliable storage better
1238411337 M * ard well, with unreliable storage you should at least see something in the kernel log
1238411349 M * pmjdebruijn xfs is rock solid if the block device is reliable... but it tends to crash and burn when the block device isn't reliable
1238411349 M * ard these systems were fine, except for the jfs partition.
1238411404 M * ard but maybe jfs was never really tested on NUMA smp systems ;-)
1238411416 M * ard and it probably already is fixed
1238411443 A * ard loves the rebuildtree from reiserfs
1238411471 M * ard if that was available for other filesystems...
1238411702 M * Bertl well, what would I need a --rebuild-tree on a reliable filesystem for?
1238411720 A * ard knows it from experience:
1238411776 M * ard imagine you are tired, but you still want to finish that backup solution on your nas, and the backup is a second partition on that nas, coffee is unavailable
1238411817 M * ard then you mkfs.ext3 the backuppartition, ignoring the warnings about the xfs, since you know it is the right one
1238411828 M * ard and then you remember it's the wrong one
1238411871 M * ard I've looked really hard how to recover the xfs filesystem from a disaster like that
1238411902 M * Bertl well, I tend to zero out the disk before I format them ... don't think that the --rebuild-tree will handle that gracefully :)
1238411918 M * ard and a rebuildtree is really possible with xfs, since all data has neat little magic markers
1238411941 M * Bertl anyway .. off to get some work done ... bbl
1238411947 M * ard O/~
1238411971 N * Bertl Bertl_oO
1238411996 Q * zbyniu Ping timeout: 480 seconds
1238412241 J * zbyniu ~zbyniu@ip-62.181.188.13.static.crowley.pl
1238413429 N * ensc Guest815
1238413439 J * ensc ~irc-ensc@p57AA59B3.dip.t-dialin.net
1238413439 J * sunkencity ~joel@81-232-47-162-no38.business.telia.com
1238413546 Q * Guest815 Ping timeout: 480 seconds
1238413864 Q * aaronyy Quit: No Ping reply in 90 seconds.
1238413872 J * aaronyy ~aaronyy@cpe-74-72-228-187.nyc.res.rr.com
1238414044 J * aaronyy_ ~aaronyy@cpe-74-72-228-187.nyc.res.rr.com
1238414044 Q * aaronyy Read error: Connection reset by peer
1238414078 J * yarihm ~yarihm@guest-docking-nat-2-105.ethz.ch
1238414533 J * Pazzo ~ugelt@reserved-225136.rol.raiffeisen.net
1238415005 J * Piet ~piet@asteria.debian.or.at
1238416171 J * ghislainocfs21 ~Ghislain@adsl2.aqueos.com
1238416361 Q * ghislainocfs21 
1238416454 J * ghislainocfs21 ~Ghislain@adsl2.aqueos.com
1238416476 Q * ghislainocfs2 Ping timeout: 480 seconds
1238416508 J * cga_ ~weechat@82.84.187.144
1238416586 Q * cga Ping timeout: 480 seconds
1238416886 J * jrdnyquist ~jrdnyquis@slayer.caro.net
1238417433 J * aaronyy ~aaronyy@cpe-74-72-228-187.nyc.res.rr.com
1238417434 Q * aaronyy_ Read error: Connection reset by peer
1238417974 J * richi_ ~richi@85-126-150-194.work.xdsl-line.inode.at
1238418053 M * richi_ Hello, i got a small problem. I need to use the portmap for unfs3(userspace nfs). Otherwise LTSP wouldnt find the nfs port. There is no solution to set the port over the kernel parameters.  And i don't want to change the init.
1238418120 M * richi_ so if i start the portmap on interface 127.0.0.1 then start unfsd, Then i stop portmap and thatn start portmap on interface 192.168.10.10, then everything work, is there a other solution... the option -l doesnt work...it listen on 127.0.0.1 or on 192.168.10.10 
1238418141 M * richi_ some idea or workaroung?
1238418664 Q * bono Quit: Leaving
1238419011 Q * pmenier Ping timeout: 480 seconds
1238419654 M * Bertl_oO richi_: I don't see the problem, why not run the portmap inside the guest (should bind to all interfaces, including the guest's lo and ethX
1238419771 J * bono bono@114-45-225-125.dynamic.hinet.net
1238419903 M * richi_ Bertl_oO: now i got confused - should the portmap only run on the host or in the guest too?
1238419965 M * richi_ and if it run in the guest two should i run it wit -l i <ip> or without?
1238420393 J * cehteh ~ct@pipapo.org
1238420912 M * Bertl_oO well, I presume you want to run the unfs3 in the guest, no?
1238420928 M * Bertl_oO in that case, you most likely want to run the portmapper too there
1238421285 M * richi_ ur right, but the portmap doesnt listen on localhost
1238421297 M * richi_ it listen only on 127.0.0.1 OR on 192.168.10.10 and not on both
1238421316 Q * jze 
1238421348 M * Bertl_oO what kernel/patch do you use, and what is your guest config?
1238421354 M * richi_ unfs3 can register nfs.. i need to start portmap on 127.0.0.1  then start portmap and then i need top stop portmap and start it again on ip 192.168.10.10
1238421380 M * richi_ i use the one in debian lenny...
1238421412 M * Bertl_oO the broken 2.6.26 one?
1238421458 M * richi_ is it broken? the kernel is 2.6.26 but i don't knwo wich vserver path...
1238421480 M * richi_ patch*
1238421494 M * Bertl_oO well, yeah, that one is broken ... ask the debian folks for a new one, preferably 2.6.27.x (or 2.6.28)
1238421541 M * sid3windr I'm afraid the debian folks will only present you with a new one in 1.5-2.5 years
1238421568 M * Bertl_oO for the guest config, I presume you have a single IP assigned to the guest?
1238421593 Q * sunkencity Quit: sunkencity
1238421640 M * richi_ debian is always old ;)
1238421669 M * Bertl_oO old is fine, broken is not ...
1238421675 M * richi_ maybe there will be a new one in sid, otherwise i will compile a new one...
1238421679 M * Bertl_oO but yeah, you can go back to the 2.6.22 kernels
1238421689 M * richi_ is there no bug fix for 2.6.26?
1238421707 M * richi_ i don't like old things...
1238421709 M * Bertl_oO nobody uses 2.6.26 as 2.6.27.x is long term maintained
1238421723 M * Bertl_oO (and 2.6.26 is already unmaintained)
1238421732 Q * BenG Quit: I Leave
1238421733 M * richi_ is 2.6.27? i have tested it on a other maschine and i got big trouble...
1238421765 M * Bertl_oO but yes, the debian folks could probably fix up the 2.6.26 kernel, but it seems there is no desire whatsoever to do that
1238421855 M * Bertl_oO so, if my assumption about your guest config is correct, then I'd suggest to add a ~single_ip to the nflags
1238421878 M * Bertl_oO (in the guest config)
1238421943 Q * nenolod Quit: 2.6.29-rc7/paravirt/xen/dom0 -> 2.6.29-git/paravirt/xen/dom0 (exciting, i know)
1238421945 M * pmjdebruijn I really don't understand why Debian went with 2.6.26 anyways
1238421955 A * pmjdebruijn always rolls his own kernels on Debian
1238421988 M * richi_ so i will search for a 2.6.28 kernel, or patch it on my own...
1238422018 M * ktwilight__ richi_, what problems do you have with 2.6.27.x?
1238422096 M * richi_ 2.6.27x with a old one i got allways crashes/freezes..but couldn remember couse i used 2.6.28
1238422228 J * sunkencity ~joel@c-4f66cf22-74736162.cust.telenor.se
1238422262 Q * balbir_ Ping timeout: 480 seconds
1238422282 M * richi_ wich patch should i use for the kernel - experimental?
1238422395 M * richi_ so i need drbd, vserver...
1238422711 M * Bertl_oO you already have an experimental patch in the 2.6.26 kernel
1238422728 M * Bertl_oO (and a broken one too, so experimental should be fine :)
1238422768 M * ktwilight__ richi_, http://linux-vserver.org/Welcome_to_Linux-VServer.org take your pick
1238422975 J * nenolod nenolod@petrie.dereferenced.org
1238423062 J * pmenier ~pme@LNeuilly-152-22-72-5.w193-251.abo.wanadoo.fr
1238423407 M * pmjdebruijn richi_: do you remember to what the crashes we're related?
1238423411 M * pmjdebruijn we had some issues with bnx2
1238423754 Q * Punkie Quit: Leaving
1238423877 J * balbir_ ~balbir@59.145.136.1
1238423956 M * richi_ pmjdebruijn: no sry, but it was under sidux...
1238424086 M * [Guy] how can I increase shmmax in/of a vserver?
1238424091 N * [Guy] Guy-
1238424114 M * Bertl_oO just set the proper values in the guest config
1238424166 M * Guy- doesn't it inherit the value from the host?
1238424223 M * Bertl_oO it gets the kernel defaults, it is a new namespace
1238424243 M * Guy- OK, thanks
1238424466 Q * balbir_ Ping timeout: 480 seconds
1238424740 Q * davidkarban Quit: Ex-Chat
1238424980 Q * sunkencity Ping timeout: 480 seconds
1238425050 Q * sharkjaw Remote host closed the connection
1238425313 M * richi_ so thx for the help. i will compile a new one with the patch, so see you later :)
1238425370 M * Bertl_oO you're welcome!
1238425581 Q * AndrewLee Quit: leaving
1238426082 J * dowdle ~dowdle@scott.coe.montana.edu
1238426366 Q * harobed Ping timeout: 480 seconds
1238427256 Q * thierryp Quit: ciao folks
1238428280 N * cga_ cga
1238428795 J * SlackLnx ~SlackWare@85.139.11.169
1238428967 Q * richi_ Remote host closed the connection
1238429759 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1238430420 J * hparker ~hparker@2001:470:1f0f:32c:290:96ff:fe50:40fa
1238430621 Q * mog Quit: Coyote finally caught me
1238430641 J * mog ~mog@c-68-62-169-246.hsd1.al.comcast.net
1238430958 Q * arekm Quit: leaving
1238431058 J * sunkencity ~joel@h114n4c1o1036.bredband.skanova.com
1238431115 Q * aaronyy Ping timeout: 480 seconds
1238431530 Q * sunkencity Quit: sunkencity
1238431648 J * larsivi ~larsivi@70.84-48-63.nextgentel.com
1238431914 J * arekm arekm@carme.pld-linux.org
1238432022 Q * kir Quit: Leaving.
1238432225 Q * esa` Quit: Coyote finally caught me
1238432437 N * pmenier pmenier_off
1238434464 J * hijacker ~hijacker@87-126-142-51.btc-net.bg
1238435160 Q * bono Quit: Leaving
1238435274 Q * Pazzo Quit: Ex-Chat
1238435366 Q * doener Quit: leaving
1238435703 J * thing1 ~kittens@fire.cs.bath.ac.uk
1238435717 M * thing1 Morning all
1238435731 M * thing1 Which is the current manual to read as regards loopback?
1238435748 M * thing1 I'm aware this is an RTFM question, I'm just not sure which FM to RT
1238435797 M * mnemoc depends on the version you run
1238435813 M * thing1 2.3
1238435825 M * thing1 As packaged with the Debian Lenny kernel
1238435836 M * thing1 Just upgraded etch -> lenny and it's broken :-(
1238435852 A * mnemoc will avoid to troll
1238435884 M * mnemoc thing1: unless you got singleip enabled you get a 127. mapped to each 127.0.0.1
1238435909 M * thing1 Sorry - seriously wasn't trying to troll, just give context.
1238435913 M * thing1 Thanks for your help.
1238435937 M * mnemoc no no, I tend to bash against debian
1238435946 M * mnemoc thing1: but you can also set (in /etc/vservers/$guest) what ip to map there
1238435978 M * thing1 I checked the flowers page but I couldn't see which file was needed for this
1238436000 M * mnemoc search for lback
1238436013 M * thing1 I think I did; I'll try again.
1238436044 M * mnemoc http://www.nongnu.org/util-vserver/doc/conf/configuration.html
1238436051 M * mnemoc /etc/vservers/vserver-name/interfaces
1238436066 M * thing1 Just found it.
1238436066 M * mnemoc lback: The guest's loopback address.
1238436070 M * thing1 I suck - sorry.
1238436075 M * mnemoc :)
1238436075 M * thing1 I'll give it a go.
1238436076 M * mnemoc np
1238436113 J * balbir_ ~balbir@122.172.58.57
1238436350 J * doener ~doener@i59F55306.versanet.de
1238436456 M * thing1 mnemoc : That's the trick, all works now, thanks muchly
1238436477 M * thing1 Should I / Can I add this to the wiki to save you getting repeats?
1238436482 M * thing1 If so, where?
1238436496 J * derjohn_mob ~aj@98.21.204-77.rev.gaoland.net
1238436569 M * mnemoc thing1: any contribution to the wiki is welcomed. no idea what's the right place for it
1238436660 M * thing1 OK, I'll try to find somewhere that looks appropriate.  Apologies for any toes trodden upon :-)
1238437058 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk
1238437288 M * thing1 http://linux-vserver.org/Upgrading_from_Etch_to_Lenny
1238437302 M * thing1 Linked from http://linux-vserver.org/Documentation#Guides_and_Howtos
1238437306 M * thing1 Hope that helps.
1238437320 Q * DLange Ping timeout: 480 seconds
1238437538 Q * cluk Quit: Ex-Chat
1238437665 Q * gnuk Quit: NoFeature
1238437785 J * AndrewLee ~andrew@210.240.39.7
1238437834 Q * AndrewLee 
1238437860 J * AndrewLee ~andrew@210.240.39.7
1238437929 Q * AndrewLee 
1238437998 J * AndrewLee ~andrew@210.240.39.7
1238438196 Q * AndrewLee 
1238438265 J * AndrewLee ~andrew@210.240.39.7
1238438959 Q * derjohn_mob Ping timeout: 480 seconds
1238439152 Q * jrdnyquist Quit: Leaving
1238439176 J * sunkencity ~joel@h114n4c1o1036.bredband.skanova.com
1238439208 Q * thing1 Quit: using sirc version 2.211+KSIRC/1.3.12
1238439610 J * jrdnyquist ~jrdnyquis@64.132.40.63
1238439968 Q * yarihm Quit: This computer has gone to sleep
1238440381 J * tanjix1 tanjix@mozart.star-hosting.de
1238440566 Q * tanjix Ping timeout: 480 seconds
1238441245 J * scientes ~scientes@75-165-66-24.tukw.qwest.net
1238441734 J * imcsk8 ~ichavero@148.229.1.11
1238441736 J * ichavero_ ~ichavero@148.229.1.11
1238442108 Q * sunkencity Quit: sunkencity
1238442712 J * ghislainocfs2 ~Ghislain@adsl2.aqueos.com
1238443030 J * harobed ~harobed@arl57-1-82-231-110-14.fbx.proxad.net
1238443036 Q * ghislainocfs21 Ping timeout: 480 seconds
1238443826 J * DLange ~DLange@dlange.user.oftc.net
1238443859 Q * harobed Ping timeout: 480 seconds
1238443928 Q * hijacker Quit: Leaving
1238443931 P * cga got a DELL??? update you BIOS with http://github.com/cga/dellbiosupdate.sh/tree/master ;)
1238444339 M * Bertl_oO off to bed now .. have a good one everyone!
1238444345 N * Bertl_oO Bertl_zZ
1238444511 Q * BenG Quit: I Leave
1238444725 Q * bonbons Quit: Leaving
1238445217 J * cga ~weechat@82.84.187.144
1238447492 J * sunkencity ~joel@h114n4c1o1036.bredband.skanova.com
1238447992 J * harobed ~harobed@arl57-1-82-231-110-14.fbx.proxad.net
1238449236 J * yarihm ~yarihm@77-56-182-18.dclient.hispeed.ch
1238449807 J * derjohn_mob ~aj@98.21.204-77.rev.gaoland.net
1238450004 Q * cga Quit: got a DELL??? update you BIOS with http://github.com/cga/dellbiosupdate.sh/tree/master ;)
1238451091 Q * harobed Ping timeout: 480 seconds
1238451207 Q * pmenier_off Ping timeout: 480 seconds
1238451424 J * pmenier_off ~pme@LNeuilly-152-22-72-5.w193-251.abo.wanadoo.fr
1238452320 Q * balbir_ Ping timeout: 480 seconds
1238452983 J * balbir_ ~balbir@122.172.59.118
1238454312 Q * dowdle Remote host closed the connection
1238454434 N * ensc Guest888
1238454444 J * ensc ~irc-ensc@77.235.182.26
1238454537 J * hparker|laptop ~hparker@2001:470:1f0f:32c:290:96ff:fe50:40fa
1238454552 Q * Guest888 Ping timeout: 480 seconds
1238454901 Q * hparker Ping timeout: 480 seconds
1238455036 Q * hparker|laptop Ping timeout: 480 seconds
1238456482 Q * yarihm Quit: This computer has gone to sleep
1238456768 J * hparker ~hparker@2001:470:1f0f:32c:290:96ff:fe50:40fa