[00:41] bmoney (g0d@CC4-24.207.131.200.charter-stl.com) joined #vserver.
[00:50] <bmoney> hello?
[00:55] <phil_> sladen: i used the release 1.22 to patch my kernel and i used the util-vserver-0.26.tar.bz2 version of the utils
[00:55] <phil_> is that wrong?
[00:56] <bmoney> so this isn't compatible with RH9?
[01:30] ensc (~ircensc@ultra.csn.tu-chemnitz.de) left irc: Ping timeout: 512 seconds
[01:44] netrose (~john877@CC3-24.171.21.47.charter-stl.com) joined #vserver.
[01:47] bmoney (g0d@CC4-24.207.131.200.charter-stl.com) left irc: 
[02:19] Nick change: Bertl_oO -> Bertl_zZ
[03:09] kungfuftr (~scott@jadis.narnia.org.uk) got netsplit.
[03:09] CosmicRay (~jgoerzen@glockenspiel.complete.org) got netsplit.
[03:10] CosmicRay (~jgoerzen@glockenspiel.complete.org) returned to #vserver.
[03:14] kungfuftr (~scott@jadis.narnia.org.uk) returned to #vserver.
[03:33] <sladen> phil_: if you fetch 0.29 it should work
[04:07] <phil_> okay
[04:07] phil_ (~phil@20.22.204.212.sr2.DTM1.ip.versanet.de) left irc: Quit: Client Exiting
[04:27] Nick change: Doener -> doener_aw
[07:48] Nick change: doener_aw -> doener_zz
[07:58] RAJ_Onlin (RAJ_Online@202.9.130.197) joined #vserver.
[08:31] RAJ_Onlin (RAJ_Online@202.9.130.197) left irc: Ping timeout: 480 seconds
[09:03] riel (~riel@riel.netop.oftc.net) left irc: Ping timeout: 480 seconds
[10:00] loger joined #vserver.
[10:32] noel- (~noel@pD9E0963D.dip.t-dialin.net) joined #vserver.
[10:40] noel (~noel@pD9FFA7E6.dip.t-dialin.net) left irc: Ping timeout: 504 seconds
[12:16] Nick change: noel- -> noel
[13:20] serving (~serving@213.186.190.138) left irc: Ping timeout: 480 seconds
[13:34] <virtuoso> re
[13:49] tanjix (~tanjix@p5091F054.dip.t-dialin.net) joined #vserver.
[13:49] <tanjix> hi @ll
[13:50] <virtuoso> tanjix: hi
[13:53] tanjix (~tanjix@p5091F054.dip.t-dialin.net) left irc: Client Quit
[14:59] tanjix (ViRu_@pD904A061.dip.t-dialin.net) joined #vserver.
[15:12] serving (~serving@213.186.189.219) joined #vserver.
[15:34] phil_ (~phil@20.22.204.212.sr2.DTM1.ip.versanet.de) joined #vserver.
[15:36] <phil_> hi
[15:39] <tanjix> hi
[15:43] phil_ (~phil@20.22.204.212.sr2.DTM1.ip.versanet.de) left irc: Remote host closed the connection
[15:44] phil_ (~phil@20.22.204.212.sr2.DTM1.ip.versanet.de) joined #vserver.
[16:02] Nick change: Bertl_zZ -> Bertl
[16:02] <Bertl> hi everyone!
[16:03] <tanjix> hi bertl
[16:04] <Bertl> how are you?
[16:04] <tanjix> fine, thanks
[16:04] <Bertl> all configuration issues solved?
[16:04] <tanjix> still now
[16:04] <tanjix> not
[16:11] <Bertl> hmm, what issues remain?
[16:16] <tanjix> that not all vservers start on starting up the hostsystem
[16:24] Doener_zZz (~doener@pD9588786.dip.t-dialin.net) joined #vserver.
[16:25] <Bertl> tanjix: which ones do not start up, what is the pattern?
[16:32] doener_zz (~doener@pD9E12B01.dip.t-dialin.net) left irc: Ping timeout: 512 seconds
[17:04] <tanjix> sry, was afk... you need the context number (S_CONTEXT) ?
[17:10] infowolfe (~infowolfe@pcp04891550pcs.frnkmd01.md.comcast.net) joined #vserver.
[17:11] <infowolfe> hey Bertl, good morning
[17:11] <Bertl> morning infowolfe!
[17:12] <Bertl> tanjix: no I would like to know what the not-starting servers have in common ...
[17:13] <tanjix> Bertl: can't follow you, sry
[17:13] <infowolfe> oh, bertl, have you seen ensc today?
[17:14] <Bertl> enrico, are you around?
[17:26] virtuoso (~shisha@ip114-115.adsl.wplus.ru) left irc: Ping timeout: 480 seconds
[17:27] <Bertl> infowolfe: seems hes not there ... still without a network connection over the holidays ...
[17:28] <infowolfe> ah..
[17:31] <Bertl> what do you need, maybe I can help?
[17:32] <infowolfe> from the vskel passwd.pl i get the following:
[17:32] <infowolfe> -- /usr/sbin/vserver --nodev --silent cstrike1 exec /usr/bin/passwd --stdin root
[17:33] <infowolfe>  /usr/lib/util-vserver/save_s_context: fork: Resource temporarily unavailable
[17:33] <Bertl> hmm, looks like the process limit is too low ...
[17:34] <infowolfe> how do you suggest i fix it?
[17:34] <Bertl> did you try his newest tools?
[17:34] <Bertl> http://www-user.tu-chemnitz.de/~ensc/util-vserver/util-vserver-0.27.tar.bz2
[17:35] <infowolfe> i was actually just about to :-p
[17:35] <infowolfe> involved in a furious discussion on freenode's #gentoo-dev about fc :-D
[17:35] <Bertl> fc?
[17:36] <Bertl> fc like fc1?
[17:36] <infowolfe> fibre channel
[17:36] <infowolfe> like fc-sf
[17:36] <infowolfe> since fc-al is "too slow" lmfao
[17:36] <infowolfe> ... at least according to some of the guys in #gentoo-dev
[17:37] <infowolfe> 01[09:36] <wli> ciaranm: The rig I saw in '00 was an ia32 NUMA box with 16 nodes, one switch for each cpu cabinet (4 nodes), 4 adapters for each node, one bridge for each disk cabinet. Or I might be 01confusing the bridges and switches.
[17:37] <infowolfe> stuff that makes me drool
[17:38] virtuoso (~shisha@ip114-115.adsl.wplus.ru) joined #vserver.
[17:39] <Bertl> hi virtuoso!
[17:39] <Bertl> infowolfe: you are pasting black text again ...
[17:39] <infowolfe> sorry
[17:39] <infowolfe> nvm then :-p
[17:49] <infowolfe> it did it again
[17:50] <infowolfe>  /usr/lib/util-vserver/save_s_context: fork: Resource temporarily unavailable
[17:50] <infowolfe> Bertl, anything you'd like to see?
[17:57] <Bertl> hmm, yes, the vserver config ...
[17:58] <infowolfe> which particular part?
[17:58] <infowolfe> or email the whole works to you
[17:58] <Bertl> web page?
[17:58] <infowolfe> ok
[17:59] <infowolfe> http://thor.hardcore-linux.net/cstrike1.conf
[18:00] <Bertl> try to raise the -u 200 to -u 1000 just for a test ...
[18:00] <Bertl> which kernel patches do you use on that host?
[18:01] <infowolfe>  2.4.23-vs1.3.1
[18:01] <infowolfe> same behavior with -u 1000
[18:05] <Bertl> hmm, could you try with vs1.22 .. maybe a bug ...
[18:06] <infowolfe> it'd require a reboot
[18:06] <infowolfe> but no problem
[18:09] <infowolfe> hey bertl? why is 1.22 1.22 instead of 1.2.2
[18:10] <Bertl> ahh, you are the first one to notice _and_ ask ...
[18:10] <infowolfe> it's just odd... and seems out of the normal naming convention (and if i hadn't had a problem booting my router this morning due to it being 1.22 instead of 1.2.2 it wouldn't have been fresh on my mind :-D)
[18:10] <Bertl> well, first I thought about a numbering scheme like 1.00, 1.01, 2.00, 2.01, 2.02 ...
[18:11] <Bertl> but then decided to use the kernel scheme (even/odd)
[18:12] <infowolfe> that doesn't make sense though...
[18:12] <infowolfe> was 1.20 your 20th iteration?
[18:12] <infowolfe> nevermind... i just caught on
[18:12] <Bertl> but to simplify that I 'just' removed the last dot for the stable releases, with the idea, that stable and devel would be easy to distinguish this way ...
[18:13] <infowolfe> building 1.22 now
[18:13] <Bertl> so 1.22 is actually 1.2.2
[18:13] <Bertl> I guess I get into troubles if I do more than 9 bugfix releases ;)
[18:13] <infowolfe> lol
[18:23] <infowolfe> it's a 1.3.1 bug
[18:23] <infowolfe> util-vserver-0.27, vs1.3.1 causes the error... vs1.22 does not
[18:23] <infowolfe>  /usr/bin/passwd: invalid option -- -
[18:23] <infowolfe> usage: passwd [-f|-s] [name]
[18:23] <infowolfe>        passwd [-x max] [-n min] [-w warn] [-i inact] name
[18:23] <infowolfe>        passwd {-l|-u|-d|-S|-e} name
[18:26] <infowolfe> doesn't help that gentoo's passwd won't accept passwords from stdin :(
[18:26] <infowolfe> actually, that doesn't seem right...
[18:32] <infowolfe> Bertl, that problem above seems to be a 1.3.1 bug... but i'm not sure where's it's manifesting itself... or why
[18:32] <Bertl> okay ...
[18:32] <Bertl> try to lower the -u to 200 again ... and then maybe to 100
[18:33] <Bertl> and just for the fun of doing it, reboot with 1.3.1 and try if it works after the reboot, but maybe? fails later on?
[18:33] <infowolfe> vs1.22 does the right thing... *but* i'm not sure if --stdin is supposed to be passed to /usr/bin/passwd OR to /usr/sbin/vserver
[18:34] <Bertl> I guess not ... passwd clears ever input ... for security, maybe usermod would be a better choice?
[18:34] <infowolfe> Bertl, not my problem, i'm just going to replace the passwd.pl with a print statement :-D
[18:34] <Bertl> hmm ...
[18:34] <infowolfe> after i do the testing for you
[18:34] <infowolfe> -u 200 and then -u 100?
[18:35] <Bertl> yes ... and see if 1.3.1 works after a reboot ...
[18:35] Nick change: surriel -> riel
[18:38] <infowolfe> -u 200 works
[18:39] <Bertl> hi rik, how was your xmas?
[18:41] <infowolfe> Bertl -u 100 also works with vs1.22
[18:41] <infowolfe> want me to go back to 1.3.1 now?
[18:42] <Bertl> if it isn't a too big annoyance, yes please ;)
[18:42] <infowolfe> no problem
[18:43] <infowolfe> doing it now
[18:46] <infowolfe> checking 1.3.1 with -u 100 again
[18:49] <infowolfe> Bertl, it's 1.3.1
[18:49] <infowolfe>  /usr/lib/util-vserver/save_s_context: fork: Resource temporarily unavailable
[18:49] <Bertl> okay, thanks ... I'll have a look at the code right now ...
[18:50] <infowolfe> let me know if you'd like me to test
[18:50] <infowolfe> i'll switch my /usr/src/linux back over to the 1.3.1 tree to make a diff easier for you
[18:50] <Bertl> hmm, you could give the 'unofficial' 1.3.2 a try ... maybe I fixed it already ;)
[18:51] <infowolfe> umm, ok
[18:51] Action: infowolfe rushes back to reverse the 1.3.1 patch
[18:51] <Bertl> http://vserver.13thfloor.at/Experimental/patch-2.4.23-vs1.3.2.diff
[18:52] <Bertl> a tip, regarding different kernel builds ...
[18:52] <Bertl> you can do the following, without any issues:
[18:52] <Bertl> a) tar xjf linux-2.4.23.tar.bz2
[18:52] <Bertl> b) cp -la linux-2.4.23 linux-2.4.23-vs1.22
[18:52] <Bertl> b) cp -la linux-2.4.23 linux-2.4.23-vs1.3.1
[18:52] <Bertl> b) cp -la linux-2.4.23 linux-2.4.23-vs1.3.2
[18:53] <Bertl> c) cd linux-2.4.23-vs1.22
[18:53] <infowolfe> building vs1.3.2
[18:53] <Bertl> d) bzcat ../patch-2.4.23-vs1.22.diff.bz2 | patch -p1
[18:53] <infowolfe> Bertl, i like patch -Rp1 though :-p
[18:53] <Bertl> yeah sure ... whatever you prefer ;)
[18:53] <infowolfe> I like /usr/src/linux to actually be whatever i'm currently running normally
[18:54] <Bertl> it just saves a _lot_ of time and doesn require much space, and  ln -s linux-2.4.23-vs1.22 linux is an option too ;)
[19:01] <infowolfe> 1.3.2 reboot now
[19:05] <infowolfe> trying now
[19:07] <infowolfe> Bertl, it's present in 1.3.3 also
[19:07] <infowolfe> oops
[19:07] <infowolfe> s/1.3.3/1.3.2/
[19:07] <infowolfe>  /usr/lib/util-vserver/save_s_context: fork: Resource temporarily unavailable
[19:09] <infowolfe> Bertl, i'm thinking that it's directly related to the --nodev code portions
[19:10] <infowolfe> or perhaps the --silent portion
[19:10] <infowolfe>  /usr/sbin/vserver --nodev --silent cstrike1 exec /usr/bin/passwd is what is being run
[19:27] <infowolfe> Bertl, any ideas?
[19:27] <Bertl> not yet ...
[19:28] <infowolfe> alright, the test string is right there... it should be easy to see if the bug is still there (finding out what else broke is the pain :-p)
[19:29] <infowolfe> oh, and btw, 1.3.2 isn't ready yet... it hung starting sshd for about 3 minutes before i killed the process via ctrl-c and then rebooted back into 1.22
[19:32] Nick change: tanjix -> tanjix[afk]
[19:32] <infowolfe> Bertl, is there a guide for understanding what showattr outputs?
[19:32] <infowolfe> [root$thor]::cstrike1> showattr bin/mount
[19:32] <infowolfe> bin/mount       00008010
[19:34] <infowolfe> what the hell... i can't modify any files "created" by vskel!
[19:34] <infowolfe> can't replace, can't modify, can't do anything to them, can't even delete them!
[19:43] Action: infowolfe feels stupid
[19:43] <infowolfe> nevermind :-p
[20:07] phil__ (~phil@49.18.204.212.sr1.DTM1.ip.versanet.de) joined #vserver.
[20:07] phil_ (~phil@20.22.204.212.sr2.DTM1.ip.versanet.de) left irc: Read error: No route to host
[20:10] stubbsd (~stubbsd@217.206.216.194) joined #vserver.
[20:10] <stubbsd> anybody around that could clear up a question for a newbe to vserver?
[20:12] <infowolfe> stubbsd, go for it
[20:12] <infowolfe> if it's easy, i can handle it, if not, Bertl isn't away, so he can take care of it :-D
[20:13] <stubbsd> thanks, I have setup a vserver but thing that try to bind to 0.0.0.0 fail inside it,
[20:13] <infowolfe> stubbsd, that's a security feature :-p
[20:14] <stubbsd> do I have to use the chbind inside the vserver?
[20:14] <infowolfe> stubbsd, no, you need to set things like apache "Listen *" to "Listen <vserver-ip>:80"
[20:14] <stubbsd> If the vserver is limited to only one IP, can I set it up so if a service binds to 0.0.0.0 that get that IP?
[20:15] <infowolfe> no
[20:15] <infowolfe> you have to specify that ip for that service afaik
[20:15] <stubbsd> sh**t..
[20:15] <infowolfe> sorry, man...
[20:15] <stubbsd> I have a service that does allow me to :-(
[20:15] <infowolfe> what service?
[20:15] <stubbsd> krb524d
[20:15] <infowolfe> Bertl: ping
[20:17] <infowolfe> stubbsd, what distribution is the vserver?
[20:18] <stubbsd> I've cooked the kernel from the 1.22 
[20:18] <stubbsd> and the 2.4.23 kernel
[20:18] <infowolfe> stubbsd, what i'm asking, the virtual server you're running, is it redhat, mandrake, suse, other?
[20:18] <stubbsd> gentoo.
[20:19] <infowolfe> :-D
[20:19] <stubbsd> sorry.
[20:19] Action: infowolfe hugs stubbsd
[20:19] <infowolfe> i run gentoo :-p
[20:19] <stubbsd> cool.
[20:19] <infowolfe> how virtualized are you?
[20:20] <infowolfe> i have gentoo running inside my vservers and on my host with *no* startup problems :-D
[20:22] <stubbsd> sorry about that, the gnome "go have a brake came up, just killed it." :-)
[20:22] <infowolfe> lol
[20:22] <stubbsd> infowolfe, how did you do it, what about the depend's in the init scripts?
[20:22] <infowolfe> :-D
[20:22] <infowolfe> i'm +v on #gentoo-dev on freenode :-p
[20:23] <infowolfe> here's the basics...
[20:23] <stubbsd> keep getting kicked from gentoo-dev :-( "I'm just a low life.."
[20:24] <infowolfe> lol
[20:25] <infowolfe> i made friends with some devs in #gentoo and had some questions on building ebuilds
[20:26] <infowolfe> lol
[20:26] <infowolfe> umm, what're your current flood settings for /m?
[20:26] <stubbsd> confuison strikes.
[20:26] <stubbsd> ?
[20:26] <infowolfe> actually, nevermind
[20:27] <stubbsd> infowolfe, what are flood setting, 
[20:27] <infowolfe> http://thor.hardcore-linux.net/fixme.sh
[20:28] <infowolfe> umm, they're settings for your irc client that automatically ignore someone if they flood you with too many messages in too short of a time period
[20:28] <stubbsd> cool thanks,
[20:28] <infowolfe> that link is where to get the "fixme.sh"
[20:28] <infowolfe> you should run it inside the vserver from /
[20:28] <stubbsd> got it, simple but great.
[20:29] <infowolfe> that's the first thing
[20:29] <stubbsd> what logger are you using in the vertual servers?
[20:29] <infowolfe> i've also edited most of the stuff in /etc/init.d/
[20:29] <infowolfe> i use syslog-ng
[20:29] <stubbsd> my fails opening the kernel.
[20:29] <infowolfe> check http://thor.hardcore-linux.net/syslog-ng.conf for the configuration file i use
[20:30] <stubbsd> star,
[20:31] <infowolfe> that goes in /etc/syslog-ng/
[20:31] <infowolfe> then just restart it and you're good
[20:31] <infowolfe> and you should *really
[20:31] <stubbsd> back in a min. :-)
[20:32] <infowolfe> *really* add /sbin/depscan.sh as the 11th line of /sbin/rc (it's a plain text file, just edit it with your favorite editor)
[20:40] phil__ (~phil@49.18.204.212.sr1.DTM1.ip.versanet.de) left irc: Quit: Client Exiting
[20:45] <stubbsd> infowolfe, just done that and on startup depscan.sh fire off **lots** of awk proccess (just brougth the machine down) :-(
[20:46] <stubbsd> that's 2G of RAM, lol
[20:46] <stubbsd> sorry, not dead, just pooly
[20:47] <infowolfe> stubbsd, then something else is wrong
[20:48] <infowolfe> stubbsd, how did you build the vserver?
[20:49] <stubbsd> I thing I put the depscan.sh in the wrong file.... (lol) sorry one min...
[20:49] <infowolfe> where did you put it?
[20:52] <infowolfe> stubbsd, depending on how fast your connection is, i can tar a "fixed" gentoo vserver for you
[20:52] <stubbsd> /etc/rc.conf --------- it ran, and ran, :-)
[20:52] <infowolfe> if you don't mind apache, postfix, mysql, mod_php and some other stuff
[20:53] <infowolfe> oops :-p
[20:53] <infowolfe> lol
[20:53] <infowolfe>  umm, /etc/rc.conf != /sbin/rc :-p
[20:53] <infowolfe> but i'm sure you know that now
[20:54] <infowolfe> btw, depscan.sh regenerates all your runtime directories and locks'n'stuff for starting a gentoo distro :-D
[20:55] <stubbsd> what else did you do to the init.d files?
[20:55] <stubbsd> thank,
[20:56] <stubbsd> s/thank/thanks/
[20:56] <infowolfe> do you mind having apache, postfix, syslog-ng, mysql, mod_php, gentoolkit, and a few other toys installed by default?
[20:56] <stubbsd> I could easly clean them up, so no.
[20:57] <infowolfe> ok
[20:57] <infowolfe> then i'll start the tar
[20:57] <stubbsd> infowolfe, I owe you a pint!
[20:57] <infowolfe> no you don't
[20:57] <infowolfe> you owe me your soul, bwa ha ha ha ha (just kidding)
[20:58] Action: stubbsd runs like hell
[20:58] <Bertl> can I get a piece of it?
[20:58] <infowolfe> sure... but only if you use it for collision testing :-p
[20:58] <stubbsd> you know what they say, in for a peny in for a pound.
[20:58] <infowolfe> lol
[20:59] <stubbsd> infowolfe, where are you based?
[20:59] <infowolfe> baltimore, md
[20:59] <infowolfe> stubbsd, what kinda internet connection do you have?
[20:59] <stubbsd> 2mbit, 
[20:59] <stubbsd> hdsl
[20:59] <infowolfe> hrm... (does some math in head)
[20:59] <infowolfe> it'll take you about as long to download this as it'll take you to download a redhat iso
[21:00] <infowolfe> and it's latest and greatest gentoo 2004.0 
[21:00] <infowolfe> (should be up-to-date) including emerge sync unless they've committed a lot to cvs lately :-p
[21:00] <stubbsd> is that unstable ie ACCEPT_KEYWORDS=">x86" or something else?
[21:01] <infowolfe> no, ACCEPT_KEYWORDS="x86" not ~x86
[21:01] <stubbsd> s/>x86/~x86/
[21:01] <infowolfe> umm, ooh, what're your cflags?
[21:01] <stubbsd> great,
[21:02] Action: stubbsd runs round the room, gime, gime gimeeeee...
[21:02] <infowolfe> http://thor.hardcore-linux.net/make.conf
[21:02] <infowolfe> that's what the minor stuff has been built with
[21:02] <infowolfe> (apache, mod_php, mysql, postfix)
[21:03] <stubbsd> are you using distcc?
[21:03] <infowolfe> not actively
[21:03] <stubbsd> are, its going on p4 not athlon-xp :-(
[21:04] <infowolfe> don't worry about it
[21:04] <infowolfe> it doesn't matter that much
[21:04] <stubbsd> does it still work
[21:04] <infowolfe> change the make.conf flags
[21:04] <infowolfe> and btw, apache doesn't start by default :-p
[21:04] <stubbsd> no worrys.
[21:05] <infowolfe> do you have a working mailer on your system?
[21:05] <stubbsd> not as such.
[21:05] <Bertl> okay, I found the nproc issue!
[21:05] <infowolfe> it's nrpoc?
[21:06] <infowolfe> sweet
[21:06] Action: infowolfe mutters about sydlexia
[21:06] <infowolfe> dangit... :(
[21:06] <stubbsd> lol
[21:06] <infowolfe> that wasn't on purpose
[21:06] <infowolfe> although quite funny :-D
[21:06] Action: infowolfe laughs
[21:06] <Bertl> yes, it's the nproc option, in combination with my beginning change to the rlimit system ;)
[21:06] <infowolfe> ah...
[21:07] <Bertl> I guess I have to fix that ... before 1.3.2 is released ...
[21:07] <infowolfe> stubbsd, would you mind sending me the output of your cat /proc/cpuinfo?
[21:07] <stubbsd> no
[21:07] <infowolfe> stubbsd, chip@capalon.com
[21:08] <infowolfe> i'd like to compare it to see if there might be any runtime issues
[21:08] <infowolfe> most of the time, athlon-xp flags only really matter when doing multimedia afaik
[21:12] <infowolfe> hey stubbsd, i'm thinking it'd be a good idea to rebuild everything once you've got my image and then tar it back up for backup purposes
[21:14] <infowolfe> stubbsd: PING
[21:15] <stubbsd> email is on its way
[21:15] <infowolfe> stubbsd, i'm going to post a link to this thing, when you've got it, chroot into it (don't turn it on as a vserver yet) adjust the make.conf flags to your liking and then emerge -fe world && emerge -e world
[21:16] <stubbsd> is there any whay to say emerge world, rebuild everying, not just update?
[21:16] <stubbsd> thanks.
[21:16] <infowolfe> that's it
[21:16] <stubbsd> ok.
[21:17] <infowolfe> oh, and you'll definitely want to adjust make.conf to your own liking, it's currently setup the way *i* like it...
[21:17] <stubbsd> ready,
[21:17] <infowolfe> which can be seen @ http://thor.hardcore-linux.net/make.conf
[21:17] <infowolfe> bzip2'ing to save you some bandwidth :-p
[21:17] <stubbsd> what are you connected to?
[21:17] <infowolfe> huh?
[21:18] <infowolfe> 100Mbit Level3 
[21:18] <stubbsd> sorry, what size is you pipe, if you know what I me.
[21:18] <infowolfe> where are you located?
[21:18] <stubbsd> uk
[21:18] <infowolfe> traceroute thor.hardcore-linux.net
[21:18] <infowolfe> and let me know what the ping between you and me is
[21:18] Action: stubbsd sulks in the corner, every onces pipe is bigger than his.
[21:19] <infowolfe> stubbsd, don't fret... i know a gentoo dev that is on dialup!
[21:19] <MrBawb> hehe
[21:19] <MrBawb> happy new year everyone :)
[21:19] <infowolfe> happy new year...
[21:21] <infowolfe> stubbsd, nice box, btw
[21:21] Action: infowolfe thinks everyone has a faster processor than him...
[21:21] <stubbsd> not want to play fair no pinging thor.hardcore-linux.net
[21:22] <stubbsd> it only takes about 40 mins for an iso anyway.
[21:22] <stubbsd> my own box is a apple 17" powerbook running gentoo (ppc) :-)
[21:23] <infowolfe> stubbsd, someone on your end must be filtering icmp, because i don't :-p
[21:23] <stubbsd> oh well,
[21:24] <stubbsd> infowolfe, how's the baking going. 
[21:25] <infowolfe> stubbsd, go looking in about 15 minutes for http://thor.hardcore-linux.net/gentoo.tar.bz2 (or when you get the email)
[21:25] <stubbsd> cool, thanks
[21:25] <infowolfe> i have to run out for a few minutes, i'll ping you when i'm back
[21:25] <stubbsd> I'm going to have to be off, wife. I will see you around.
[21:27] <stubbsd> squedualed for 30mins :-).. see you
[21:28] stubbsd (~stubbsd@217.206.216.194) left #vserver (Leaving).
[21:45] netrose (~john877@CC3-24.171.21.47.charter-stl.com) left irc: Ping timeout: 480 seconds
[21:50] RoMo (rmoriz@rmoriz.cpan.de) joined #vserver.
[21:50] <RoMo> hi
[21:50] <RoMo> i have some problem with vserver 1.22 + vquota on 2.4.23 - software raid1 devices don't get synced on reboot
[21:50] <RoMo> anyone knows this problem?
[22:24] <RoMo> ok seems to be a 2.4 kernel issue unrelated to vserver
[22:44] <Bertl> good to know
[23:37] netrose (~john877@CC3-24.171.21.47.charter-stl.com) joined #vserver.
[23:45] Nick change: Bertl -> Bertl_oO
[23:58] tanjix[afk] (ViRu_@pD904A061.dip.t-dialin.net) left irc: 
[00:00] --- Thu Jan  1 2004