[00:04] 0.28 release candidate has been uploaded at http://www-user.tu-chemnitz.de/~ensc/util-vserver/rc/ Please test it; I am planning to make it the final 0.28 tomorrow [00:05] 0.27.90, that's it? [00:05] yep [00:06] okay, will check them ... [00:19] I am off now guys. Talk to you tomorrow [00:19] cu! [00:19] miller7 (none@213.239.180.106) left irc: Quit: ring ring it's 7am, move yourself to go again [00:23] suhcoolbro (~Suh@216-161-89-245.ptld.qwest.net) left irc: Quit: NO CARRIER [00:24] Bertl ! [00:24] I am going to patch and compile now [00:24] are these ok ? [00:24] delta-2.4.25-pre6-vs1.3.5-vs1.3.6pre2.diff linux-2.4.24.tar.bz2 linux-vserver-1.3.5.tar patch-2.4.25-pre6.gz [00:24] ? [00:25] looks good so far ... except for the linux-vserver-1.3.5.tar [00:25] ok which to use then ? [00:25] http://vserver.13thfloor.at/Experimental/patch-2.4.25-pre6-vs1.3.5.diff [00:26] got it [00:26] sequence of course is: linux-2.4.24.tar.bz2, patch-2.4.25-pre6.gz, patch-2.4.25-pre6-vs1.3.5.diff, delta-2.4.25-pre6-vs1.3.5-vs1.3.6pre2.diff [00:27] ok [00:50] loger joined #vserver. [00:50] Bertl: ofcourse, I generally do make-kpkg anyhow. :) [00:51] I just attempted it on another box I'm also trying to get going (running 2.6.0) and it gives the same result [00:51] qwerty: which vserver patch, I mean ... [00:52] oh, the ... latest, .04 I believe [00:52] yeah, .04 [00:53] the experimental patch for 2.6.0 [00:53] okay, please get the util-vserver package form enrico and try again [00:54] I tried the source earlier, it was having issues compiling - I'll see if I can't find a binary [00:55] so is there a config option that needs to be compiled into the kernel or what? [00:55] if you have issues, talk with enrico, he knows how to solve them ... [00:55] k [00:55] qwerty: no, no option, but I havent tested the vserver-tools on 2.6 yet ... [00:55] qwerty: which compiler? gcc-2.9x or gcc-3.3? [00:56] 3.3 [00:57] hmm, should compile there [00:57] perhaps e2fsprogs problems... :( [00:58] it's having issues in the configure, "sorry do not know how to include ext2fs.h" [00:59] any ideas? [00:59] yes, does https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=112448 help you? [01:00] you are using e2fsprogs-1.35, right? [01:00] 1.34+1.35 [01:00] debian package [01:01] yes, it is broken for C++ (like the RH package) [01:01] just reorder line 980 in the way described in the bugreport [01:01] that's probably it. [01:01] great [01:01] thanks! I'll try that [01:06] ensc: at least you added a comment to your bugreport ;) [01:07] maharaja: I do not know if it is fixed upstream already; it is in bitkeeper there and I can not access it to verify it [01:08] else, I would write an upstream report, but without verification, I do not make this for development snapshots [01:08] i c [01:08] Action: maharaja is back to his c167 scripts... [01:08] hmm c167? [01:09] yes, microc and stuff. i've got a test tomorrow. and started to study about 2hrs ago [01:14] Bertl: Linux freezfed.none.dom 2.4.25-pre6-vs1.3.6 #3 Thu Jan 22 17:20:49 EST 2004 i686 i686 i386 GNU/Linux [01:14] cool, and how is it? [01:15] I am using vserver-tools .29 . [01:15] /usr/local/sbin/vserver: line 530: ulimit: max user processes: cannot modify limit: Invalid argument [01:15] hmm, do they still work? [01:16] 49152 50 868MB 44kB m04.25 m00.52 497d02h26 vv00 [01:16] ad ulimit: that is a kernel issue [01:16] you have to use -HS instead of -H in the config file since 2.4.23 ... [01:17] at least I think that this is the reason for that message?! [01:18] I can't ssh into vserver . [01:18] I did vserver vv00 enter [01:18] Error: /proc must be mounted and readable [01:18] To mount /proc at boot you need an /etc/fstab line like: [01:18] In the meantime, `mount /proc /proc -t proc' [01:18] To set the permissions, `chmod 755 /proc' [01:18] but I am in [01:18] /proc is secure by default, you'll have to 'enable' some entries first ... [01:19] . [01:19] Linux-VServer Test [V0.03] (C) 2003 H.Poetzl [01:19] chcontext failed! [01:19] chbind is working. [01:19] ipv4root: 0100007f/00ffffff ipv4root_bcast: ffffffff ipv4root_refcnt: 2 [01:19] Linux 2.4.25-pre6-vs1.3.6 i686/chcontext 0.27/chbind 0.27 [E] [01:21] hmm, interesting, please try again with a newer version ... http://vserver.13thfloor.at/Stuff/testme.sh [01:21] ensc: sorry to bother you.. still having problems just configuring util-vserver - I'm getting "Sorry, do not know, how to include ext2fs.h" [01:22] w. [01:22] . [01:22] Linux-VServer Test [V0.03] (C) 2003 H.Poetzl [01:22] chcontext failed! [01:22] chbind is working. [01:22] ipv4root: 0100007f/00ffffff ipv4root_bcast: ffffffff ipv4root_refcnt: 2 [01:22] Linux 2.4.25-pre6-vs1.3.6 i686/chcontext 0.27/chbind 0.27 [E] [01:22] . [01:22] I tried it w/ ac_cv_header_ext2fs...=no, but still gives the same result [01:22] it is the same script [01:23] Linux-VServer Test [V0.06] (C) 2003-2004 H.Poetzl [01:23] qwerty: when fixing ext2fs.h header, this ac_cv... is not needed [01:24] i just did wget http://vserver.13thfloor.at/Stuff/testme.sh [01:24] and it saved it as testme.sh.1 ;) [01:24] well, I don't think that's the issue I'm having (yet) - it fails in the configure, not the compile [01:25] does configure succeeds without warnings? [01:25] no [01:25] it stops when it's checking [01:25] Bertl: no . it is v0.03 [01:26] for ext2fs.h compatibility/usability [01:26] qwerty: can you give me a link to your config.log? [01:26] serving: okay, maybe you suffer under some advanced (micro$oft) caching effect [01:26] I can paste it [01:27] Bertl: ms wrote wget ? ;) [01:27] qwerty: please not, it are >2500 lines ;) [01:27] serving: no, I mean between your server and mine ... [01:27] I'll make a copy of that one under a new name ... [01:27] ensc: hrm... good poing. [01:27] s/poing/point [01:28] serving: http://vserver.13thfloor.at/Stuff/testme.sh-0.06 [01:28] # cp -va testme.sh testme.sh-0.06 [01:28] `testme.sh' -> `testme.sh-0.06' [01:29] Linux-VServer Test [V0.06] (C) 2003-2004 H.Poetzl [01:29] chcontext is working. [01:29] chbind is working. [01:29] Linux 2.4.25-pre6-vs1.3.6 i686/chcontext 0.27/chbind 0.27 [E] [01:29] --- [01:29] [001]# succeeded. [01:29] [011]# succeeded. [01:29] [031]# succeeded. [01:29] [101]# succeeded. [01:30] [102]# succeeded. [01:30] [201]# succeeded. [01:30] [202]# succeeded. [01:30] much better ;) [01:30] which tools go with this ? [01:31] well, best would be 0.27.198 or later ... [01:31] or is it a vs.conf isssue ? [01:31] ensc: any ideas? [01:31] serving: the ulimit? [01:31] Bertl: I dont know whatto add in vs.conf [01:31] and where [01:32] progress? :) [01:32] (with stability) [01:32] qwerty: without config.log I can not say very much [01:33] meebey: do you have _any_ stability issues? [01:34] serving: are you still talking about the ulimit issue, or what? please elaborate! [01:36] Bertl: yes . ulimit at statup and I can not do vserver vs stop [01:36] it reports that it is not running [01:36] but it is [01:36] Bertl: no, I ask because of the killer tests, with the last development state [01:36] hmm, do they have any issues? have you tested them? [01:38] (I mean the latest devel releases) [01:38] Bertl: trying to stop vs gives : [01:38] Stopping the virtual server vv00 [01:38] Error: /proc must be mounted and readable [01:38] To mount /proc at boot you need an /etc/fstab line like: [01:38] In the meantime, `mount /proc /proc -t proc' [01:38] To set the permissions, `chmod 755 /proc' [01:38] Server vv00 is not running [01:39] serving: you have to enable some proc entries ... [01:39] i would if I knew how [01:39] :) [01:40] 20:39 < Zoiah> cmdline devices filesystems meminfo self stat version [01:40] 20:39 < Zoiah> cpuinfo execdomains loadavg mounts slabinfo uptime [01:40] in the vs.conf ? [01:40] nope, you do this with the setattr tool of 0.27.199 ;) [01:40] or with the vproc tool on my page ... [01:40] ok. lemme see [01:41] the tool is available for stable and devel ... [01:41] Yay! I'm quoted. ;) [01:42] Bertl: where is .27.199 ? i can find http://www.13thfloor.at/vserver/d_release/v1.3.5/util-vserver-0.27.tar [01:43] hmm, probably not available yet, at least not as package ... but let me see if I can upload my package somewhere ... [01:43] hmm, you probably won't be able to use a rpm, right? [01:44] I guess that will be the better solution for now: http://www.13thfloor.at/vserver/s_release/v1.24/vproc-0.01.tar.bz2 [01:44] Bertl: i ll have to uninstall the rpms [01:45] ok. i ll try that one first [01:48] now. vproc -D !? i realy dont understand what this tool does [01:48] okay, let me explain ... [01:48] (well I'll look for the mail, I sent to the mailing lsit, and copy that ;) [01:49] a url of the archives will do too [01:50] http://list.linux-vserver.org/archive/vserver/ [01:51] http://list.linux-vserver.org/archive/vserver/msg05865.html [01:55] does this make sense to you now? [01:56] if there are still questions, just ask ... [01:57] well, I am supposed to hide the meminfo from the vs . This should be run b4 I start a vs . [01:57] doesn't matter, it can be changed while everything is running ... [01:57] right now. I have 2 stock vservers running of the sam evs that I cant stop [01:58] well, you _can_ stop them, but probably their xid wasn't entered in the /var/run/vserver/.ctx correctly ... [01:58] do you use static xids? [01:58] S_CONTEXT= [01:58] no [01:59] well, then you'll have to figure the context id from the vps output ... [02:00] i cant vps [02:00] Error: /proc must be mounted and readable [02:00] To mount /proc at boot you need an /etc/fstab line like: [02:00] In the meantime, `mount /proc /proc -t proc' [02:00] To set the permissions, `chmod 755 /proc' [02:00] PID CONTEXT [02:00] well, as I said, you 'should' enable some /proc entries first ;) [02:01] 23:41 < Bertl> 20:39 < Zoiah> cmdline devices filesystems meminfo self stat [02:01] version [02:01] 23:41 < Bertl> 20:39 < Zoiah> cpuinfo execdomains loadavg mounts slabinfo uptime [02:01] I tried to do what the msg said and : mount: proc already mounted [02:01] well, that is because the message is wrong! [02:01] :)) [02:02] but the coder of ps, never thought about the possibilities vserver now have ... [02:02] ok. how "would" I enable some /proc entries first ? [02:02] vproc -e /proc/* [02:02] would enable all entries in /proc ... [02:03] vproc -e /proc/{meminfo,stat,cpuinfo,loadavg,slabinfo,uptime} [02:03] would be a sane default I guess ... [02:03] i did the * and I was able to stop one instance of vs . [02:04] the second is still running and it has no server naem [02:04] name [02:04] check for the context id ... [02:04] vps [02:06] 49152 [02:08] qwerty (~root@65.126.127.3) left irc: Quit: Leaving [02:09] well, enter that number in /var/run/vservers/wossname.ctx [02:09] a bunch of 49152 UNKNOWN . kill 49152 and vkill 49152 [02:09] oh i c [02:11] mexcell (~root@65.126.127.3) joined #vserver. [02:11] it is down [02:12] Hello, all [02:12] hi mexcell! [02:13] Question: I sent some information about a test I ran on 2.6.1 with the latest vserver. I was wondering how I could help with the 2.6 testing, etc. [02:13] Bertl: what do I need to set to solve the "vserver: line 530: ulimit" errro at startup ? [02:15] mexcell: thanks for the info, good point, well actually best would be to do some network testing, as I'm not entirely sure the network part was ported correctly ... [02:15] serving: please show me your /etc/vserver/wossname.conf [02:15] especially the S_LIMIT stuff, or how is that called? [02:16] S_CONTEXT=49157 [02:16] S_PROFILE=prod [02:16] OK - happy to do so - once I can get a functioning context other than 0 . . . :-) [02:16] hmm, you did try the testme.sh, right? [02:16] me ? [02:17] Bertl: To whom are you speaking? :-) [02:19] Yes, I have. You were actually talking to one of my guys earlier - qwerty - he sent you the results. [02:19] *sigh* I'm always speaking to the last person talking, or I'll specify it, now with : [02:19] so mexcell> OK - happy ... [02:20] and then Bertl> hmm, ... [02:20] means that the message was meant for mexcell ... [02:20] Right [02:21] chcontext and chbind are failing. (and I'm flailing. . .) [02:21] Bertl: only 2 entries in vv00.ctx [02:22] Bertl: S_CONTEXT=49157 and S_PROFILE=prod ;) [02:22] serving: /etc/vservers not /var/run/vservers ;) [02:22] sorry. [02:22] I issread that. I ll post it . 1 sec [02:24] mexcell: well, he was trying to compile the util-vserver tools, I guess he should have succeeded by now, so the testme.sh output should be friendlier (more green ;) [02:24] Right - I'll go check on his luck - BRB. [02:25] http://213.186.190.24/vserver/vv00.conf [02:26] mexcell: no, I lied, it's not friendlier ... [02:26] He didn't get it going - same compile issue. [02:27] well, vserver script probably fail atm. but starting services by hand should work ... [02:27] He went on to another task. [02:27] hmm. [02:27] so I should be able to chcontext and start things myself in a change root? [02:28] yes, that should work, try with chbind and chcontext on the host ... [02:28] should even work with vserver-0.29 ... [02:28] ok - just a sec. [02:29] almost all issues are related to the missing proc information, I guess I'll add this in 0.05 (although it is depriciated, it'll help testing a lot) [02:30] when do you have time for testing 2.6 vserver stuff, in the near future? and are you interested in testing it? [02:32] I am interested in testing it - it would actually help a new dev farm I am building a lot. [02:32] I can test any time you need it, and I can put another person on it almost full time if it will help. [02:32] okay, because if I know somebody is going to test it, it's much more fun for me to code on that ... [02:33] Bertl: http://213.186.190.24/vserver/vv00.conf [02:33] ULIMIT="-H -u 1000" [02:33] ULIMIT="-HS -u 1000" [02:33] and the ulimit message is gone ;) [02:33] cool . [02:33] I can understand that - I was involved in the linux kernel for alpha back in the 2.0.30 days - hard to find testers that wanted to really help. [02:37] Bertl: how do yo uknow all this stuff ? :)) oh yeah , you wrote it ;) [02:37] well, no I did not ... but I use it ;) [02:38] actually this behaviour was introduced with 2.4.23 linux kernel ... [02:38] they changed the way rlimits work, and do error checking ... [02:39] on a vanilla 2.4.22 kernel ulimit -H -u 1000 was no problem ... [02:39] on 2.4.23 kernel it fails .. with the message you already know ... [02:39] vserver just happens to 'use' ulimit ;) [02:41] Ok - we are getting closer. I can chbind, chcontext, and chroot myself into something that almost works. [02:41] :-) [02:41] yeah, thought so, only the proc info is missing ... well it moved to /proc/virtual/* [02:43] I can't see anything but 0 in vserver-stat. Most everything says I don't have a ctx enabled kernel, and running sshd doesn't show up in ps in the new context. [02:43] The good news is that the running processes in the new context don't show up in 0 either. [02:44] well, they should show up in the context itself, and in context 1, try with chcontext --ctx 1 ps auxwww [02:44] and if you find the sshd there ... [02:44] try again with chcontext --ctx ps auxwww [02:46] Bertl: I started vs and entered it. I can not do ps ax inside anymore. authentication is failing for ssh "Failed password for root from 192.168.0.1" [02:46] Hmm - looks like there may be other issues with the sshd. I can see the inetd instance for that context. [02:48] Bertl: ifconfig show only one iterface eth0:vv00 . no lo [02:48] Yep - found it. I forget to manually config the new IP I needed for the bind. [02:49] serving: what is the problem with ps inside the context? [02:50] Bertl: Error: /proc must be mounted [02:50] To mount /proc at boot you need an /etc/fstab line like: [02:50] In the meantime, mount /proc /proc -t proc [02:51] seems like some /proc entries are missing ... hmm, are we going in circles here? [02:51] what do you see if you do 'ls /proc' inside the vserver ... [02:52] here it comes [02:52] 1 6893 6913 7286 7337 7396 7407 7412 7417 7427 bus driver ide kcore mdstat net slabinfo tty [02:52] 6852 6894 6929 7287 7351 7397 7408 7413 7418 7545 cmdline execdomains interrupts kmsg misc partitions stat uptime [02:52] 6874 6895 6930 7292 7366 7398 7409 7414 7419 7549 cpuinfo fb iomem ksyms modules pci swaps version [02:52] 6882 6896 7213 7302 7385 7399 7410 7415 7420 7737 devices filesystems ioports loadavg mounts scsi sys virtual [02:52] 6892 6897 7280 7314 7391 7406 7411 7416 7426 7781 dma fs irq locks mtrr self sysvipc [02:54] please do a 'strace -fF -s 1000 -x ps ax' and put the output somewhere on the web, or send it via mail/dcc [02:54] (inside the vserver of course) [02:55] ok [03:00] Hmm - found something interesting in the vserver script: [03:00] while running set -o xtrace on the script: [03:01] the ctx is set to 0 when it tries to run. [03:01] Bertl: http://213.186.190.24/vserver/ps1 [03:02] which immediately causes the "Invalid argument" because that isn't legal. [03:04] serving: 'vproc -e /proc/meminfo', should fix it .. [03:05] vproc: unable to stat /proc/meminfo [03:05] hmm, you already tried some options on that one, right? [03:05] hehe [03:05] try chcontext --ctx 1 vproc -e /proc/meminfo [03:05] just the one you specified earlier with the * [03:06] no no, you most likely did -E on it ... [03:07] as it is one of my examples, I guess you tried them out ;) [03:08] maybe. I have new info overload after this session :)) [03:08] ps is working now [03:08] ok - I can get the vserver script to work, but it writes out S_CONTEXT=0 to /var/run/vservers/.ctx - and fails the next time for obvious reasons. [03:09] Removing that file allows it to run once more. [03:09] Once I get that cleaned up, to whom would I submit a patch? [03:09] you can replace the save_s_context script by something reading /proc/self/vinfo instead of /proc/self/status ;) [03:10] Bertl: ok now all is working "fine" did we pass the test ? [03:10] well, you can send the patch to Jacques ... [03:10] sorry that was for mexcell ;) [03:11] right. [03:11] serving: you passed the test 8-) thank you for testing ... [03:12] and it means, I can release vs1.3.6 because it is tested ;) [03:12] sure. I ll keep running it for while and see. Once you have another one let me know . I ll be happy to do it again for you [03:12] great! [03:13] bye for now [03:13] have a nice whatever! [03:14] btw - feel free to contact me for testing on 2.6 - also I have access to SMP x86-64 machines that can be used for testing - they are engineering boxen. [03:15] hey that would be great! [03:15] is that offer also valid for 1.3.x on 2.4.x stuff? [03:16] sure [03:16] I get to do this kind of thing - it is one of the few perks I get from being the boss. [03:16] ;-) [03:18] well, in that case, I would kindly ask you to 'try' to compile the 1.3.6 prerelease on x86_64, because I suspect it doesn't pass the compiler yet ... [03:18] sure - I'll take a look at it first thing tomorrow, actually. [03:18] np, thanks in advance ... [03:19] well - save_s_context is working, but the vserver script still fails second time. - lack of S_PROFILE, perhaps. Where would I go to look into that? [03:20] hmm, the profile has nothing to do with the kernel ... so that couldn't be it ... [03:20] hmm - I can still run it if I get rid of the var/run file [03:21] I'm still getting invalid argument [03:21] from which invocation? [03:21] here is the command - thanks to xtrace - /usr/sbin/chbind --ip 192.168.30.10 --bcast 192.168.30.255 /usr/sbin/chcontext --flag lock --flag nproc --secure --ctx 49162 --hostname base.dev.possibilityforge.net /usr/lib/vserver/save_s_context /var/run/vservers/base.dev.ctx /usr/lib/vserver/capchroot --suid root . /bin/bash -login [03:22] from the second invocation - first (after removing the file) works fine [03:22] the context is running now? [03:22] before I redid save_s_context, the --ctx piece was --ctx 0 - guess that wasn't the only problem. [03:23] should be - but vserver-stat doesn't show it, so. . . [03:23] /usr/sbin/chcontext --ctx 49162 true (gives?) [03:24] can't set - guess it isn't running, rats. Just a sec. [03:24] yeah - that was it. a simple vserver start issue. [03:25] BTW - the server we are testing this on is x86_64 - but running a 32-bit kernel. [03:26] hmm, interesting ... [03:26] yeah - appears to be running more or less fine. [03:28] Well, I'll post a patch (dead simple) tomorrow for save_s_context. Looks like we have the basics running. vserver-stat is still a little funny, etc. Would it help if I took a look at switching them to the new proc entry? [03:29] sure, that would speed up testing I guess, but it should be done for util-vserver, because most new features are not supported by vserver [03:30] the scripts should not be too different anyway ... [03:30] Right - I guess I should take a closer look at Paul's problem with the header file then. [03:31] After We can compile util-vserver, then I could help with the shift. [03:31] yeah, stay in contact with enrico, I guess he knows how to get this running ... [03:32] Sure - he can grab my address from the list, too. I'll help anyway that I can. I'll talk to you later. I'm going to go grab a bite. [03:32] Thanks for the help. [03:33] thank you for testing, have a good one ... [03:33] mexcell (~root@65.126.127.3) left irc: Quit: Leaving [05:08] Nick change: Doener -> doener_zzz [07:31] meebey (meebey@meebey.net) left irc: Remote host closed the connection [07:32] meebey (meebey@meebey.net) joined #vserver. [07:32] morning meebey! [07:50] vat (vat@pD9E375D7.dip0.t-ipconnect.de) left irc: Ping timeout: 492 seconds [07:50] vat (vat@pD9E3757F.dip0.t-ipconnect.de) joined #vserver. [09:54] ccooke (~ccooke@spc1-walt1-4-0-cust238.lond.broadband.ntl.com) left irc: Ping timeout: 492 seconds [10:20] noel- (~noel@p50859979.dip.t-dialin.net) joined #vserver. [10:28] noel (~noel@pD9FFA1C7.dip.t-dialin.net) left irc: Ping timeout: 504 seconds [10:37] okay, good night, everyone ... [10:37] Nick change: Bertl -> Bertl_zZ [10:53] Nick change: noel- -> noel [11:07] serving- (~serving@213.186.190.24) joined #vserver. [11:07] serving (~serving@213.186.190.24) left irc: Ping timeout: 492 seconds [11:26] je (~je@hd5e25b7f.gavlegardarna.gavle.to) joined #vserver. [11:42] suhcoolbro (~Suh@216-161-89-245.ptld.qwest.net) joined #vserver. [12:07] ccooke (~ccooke@spc1-walt1-4-0-cust238.lond.broadband.ntl.com) joined #vserver. [12:22] mcp (~hightower@wolk-project.de) joined #vserver. [12:43] click (click@gonnamakeyou.com) joined #vserver. [12:44] ccooke (~ccooke@spc1-walt1-4-0-cust238.lond.broadband.ntl.com) left irc: Ping timeout: 480 seconds [12:57] mids (mids@mids.student.utwente.nl) joined #vserver. [14:15] miller7 (none@213.239.180.106) joined #vserver. [14:15] hello people [14:34] hi [16:50] piero (~chatzilla@yogi-13.sissa.it) joined #vserver. [17:30] maharaja (maharaja@ipax.tk) left irc: Ping timeout: 501 seconds [18:35] piero (~chatzilla@yogi-13.sissa.it) left irc: Quit: ChatZilla 0.8.11 [Mozilla rv:1.2.1/20030225] [19:00] loger joined #vserver. [19:19] anyone around? [19:21] no [19:21] I'm not here either [19:27] we're all gone [19:27] click and go [19:27] maharaja (~maharaja@ipax.tk) joined #vserver. [19:27] or something like that :) [19:28] hm, I want a proper SSL-implementation on my ircd, but I'm too lazy to write one from scratch. [19:28] *grmph* I hate being lazy [19:29] you could use stunnel [19:29] then you dont need to write anything [19:45] hm. [19:45] for the server-part? [19:48] yes [19:49] Nick change: BobR -> BobR_oO [19:58] anyone willing to help me find out why my vserver kernel is unable to mount root fs after reboot? [20:01] Nick change: Bertl_zZ -> Bertl [20:01] Nick change: BobR_oO -> BobR [20:02] hmm, maybe I? [20:03] :) [20:03] just give me a second Bert to see if I'm realy stupid and my fstab file is wrong :) [20:06] how can I see what is my filesystem for a partition? [20:06] via fdisk? [20:07] hmm, what is 'your filesystem'? [20:07] mount [20:07] well, the mount is wrong :) [20:07] /dev/ROOT on / type xfs (rw,noatime) [20:07] xfs? [20:07] no, this is the Gentoo mount (CD) [20:07] this is in the /etc/fstab [20:08] well, I didn't probably change it write in the fstab :) [20:08] or if that one is missing, in /proc/mounts ... [20:08] /dev/hda3 / reiserfs rw 0 0 [20:08] ok [20:08] Last message repeated 1 time(s). [20:08] so my fstab is wrong :) [20:08] as it shows: /dev/hda3 / ext3 noatime 0 1 [20:09] obviously wrong [20:10] that can be, no big deal, the fstab is just a file ... [20:10] oh [20:11] the only use for it, is to provide options for incomplete mounts [20:11] the actual mounts are recorded in mtab, if -n isn't used [20:11] hmmm [20:11] # CONFIG_REISERFS_FS is not set [20:11]