[00:34] Nick change: cdub -> cgone [00:46] Nick change: Bertl_oO -> Bertl [00:47] hi all, what's up? [00:52] Nick change: Doener_zZz -> Doener [00:52] hi [00:52] hi Doener! [00:52] hi Bertl [00:52] Bertl! :) [00:52] Who's enrico btw? [00:53] Action: ensc [00:53] Because both 0.27.199 and 0.28.190 appear to be broken out of the box with vs1.3.6. (Haven't tried 1.2.4 yet). [00:53] If I disable the v13 api in configure 0.28.190 works. [00:54] yes, I know. Kernel interface does not seem to be complete [00:54] Ahh, ok, so what should I run? (If I want to help test development stuff) [00:57] dunno, for now, it will be probably the best to keep v13 disabled. Perhaps, Bertl releases vs0.07/1.37 soon... [00:59] Ahh, okie. [01:19] serving (~serving@213.186.188.205) joined #vserver. [01:28] _Zoiah (Zoiah@matryoshka.zoiah.net) joined #vserver. [01:29] Zoiah (Zoiah@matryoshka.zoiah.net) left irc: Ping timeout: 492 seconds [01:31] Filther (Filther@nilus-745.adsl.datanet.hu) left irc: Ping timeout: 492 seconds [01:46] Nick change: cgone -> cdub [02:31] frz around? [02:44] Bertl: im setting up debian for you on the Ultra 10 now. [02:44] Bertl: any particular config you want? [02:44] hum ... [02:45] what you consider best ... [02:45] well, development and kernel building stuff should be present ... [02:45] _shuri (~shushushu@vserver.electronicbox.net) left irc: Ping timeout: 483 seconds [02:46] enrico, any special config you would prefer for userspace testing? [02:46] Bertl: yeah working on that now. i have a 2Gb ext3 root fs and a 6gb ext2fs mounted under /vservers. im currently playing with dselect and trying to remove all teh unneeded vruft and find teh stuff i need for the kernel devleopment etc. and security.debian.org seems to be down so i havent gotten any security updates yet. [02:46] Bertl: I told two tests in my posting already [02:47] and im going to be building and installing a 2.4.25-pre8 kernel. [02:47] by the way, the quota stuff is trickier than I thought ... [02:47] current CVS supports the VHOST functions too, so they can be tested in a similar way too [02:48] im alos going ot try out the vserver patches just for teh fun of it. but the default kernel will just be a clean 2.4.25-pre8 [02:48] ensc: I meant for the sparc ;) [02:50] I do not know sparc enough to suggest anything for it [02:50] okay, we'll see ... [02:51] you should be able to install anything you need with dselect or apt once im finished with it. it will be a few days until rob patches it into our network. i just wanted to know if you wanted the disks partitioned in any special way or anything. [02:51] ah,, godd point, almost forgot about that ... [02:52] right now its a 2gb ext3 root and a 6gb ext2 /vservers partition. and a 200mb swap. [02:52] it would be great to 2 boot partitions, and 1-3 mountable partitions which can be easily reformatted ... (for vserver test) [02:52] ifi have to redo it and reinstall debian id like to know before i get too into cleaning things up. [02:53] so about 100-200MB for the vserver test parts ... [02:53] maybe 2 100MB and 1 2GB ... or something like that ... [02:54] is that possible? what partition scheme does sparc use? [02:54] hmm what if i jsut do the roto and swap partitions and let you slice up the free untouched space however you like? [02:54] hmm, good idea ... [02:54] Bertl: it uses sun disklabel.at least for the boot partitions. [02:54] i think you can use LVM on it. [02:55] i havent played too much with linux on sparc. [02:55] hmm, okay, lvm sounds good, I use that on all my servers ... [02:55] but using just the sun disk label i know you can have up to 7 partitions including root swap and the whole disk partition. [02:56] do i have to do anythign special to set up lvm or can that be doen after a normal root/swap has been set up on the disk? [02:56] okay, that should be sufficient anyway .. [02:56] lvm is no problem at a later time ... [02:56] (at least not on x86 ;) [02:57] probably much the same on sparc id imagine. [02:57] i might eb able to give you serial consoel access too but im not sure about that yet. [02:57] would certanly make changing kernels easier since you could access teh silo prompt and the openprom. [02:58] hmm, that would be nice ... [02:58] shouldn't be too hard, well, technically ... [02:59] anyway, thanks for your time, I'm sure it will help us ... [02:59] ok well looks like everythign is mostly set then. just have to remove the 6gb partition and get rid of most of the useless cruft. [03:00] im really not a fan of debian at all. [03:00] dselect is more painful than helpful to me so far and teh debian web site could be much easier to navigate. [03:00] install aptitude ;) it is far more comfortable than dselect [03:00] but i think i hear one of you guys was used to debian. [03:01] well, I know it better than gentoo for example ;) [03:01] Doener: i will try that thank. [03:01] thanks even. [03:02] oh yeah much cleaner looking. [03:02] okay folks, my pillow is calling, and very loud too 8-) [03:02] how can you sleep with such a loud pillow ? ;) [03:02] hehe, good night Bertl [03:03] Rik, well it gets quite quiet when I'm there ;) [03:03] okay, have a good wossname everyone, cu tomorrow ... [03:03] Nick change: Bertl -> Bertl_zZz [03:05] woah cool it supports xterm mouse events. [03:05] havent used a curses app that did that before. [03:07] yeah, but on the other hand it uses the same keys for the menu as gnome-term... [03:07] dont know anything about gnome term. i use aterm. or dtterm when im in CDE. [04:33] _shuri (~shushushu@vserver.electronicbox.net) joined #vserver. [05:07] loger joined #vserver. [05:11] i might be able ot get my hands on a dual cpu ultra2. so you guys can test vserver code on an SMP ultrasparc box. [06:09] Nick change: riel -> surriel [07:04] suhcoolbro (~Suh@216-161-89-245.ptld.qwest.net) joined #vserver. [07:21] ftp21 (mree@c-67-160-157-145.client.comcast.net) joined #vserver. [07:22] hey, I installed debian 3.0r2.. should I be using the [07:22] kernel patch for debian kernels or do I need to download some upgrade? [07:25] hmm.. anyone alive here? [07:30] kestrelw (~athomas@o2rosock0a.optus.net.au) left irc: Ping timeout: 480 seconds [07:37] can anyone give me some clues? I have several debian related questions [07:56] kestrelw (~athomas@o2rosock0a.optus.net.au) joined #vserver. [07:58] Nick change: Bertl_zZz -> Bertl [07:58] morning everyone ... [07:58] hi ftp21! [08:01] suhcoolbro (~Suh@216-161-89-245.ptld.qwest.net) left irc: Quit: NO CARRIER [08:02] <_shuri> 24:03 [08:02] <_shuri> good morning:P [08:02] <_shuri> god night for me hehe [08:03] good night! [08:08] Hi :-) [08:08] hi, you had some issues with debian? [08:08] bert; you know anything about vserver on debian? [08:08] yeah [08:09] well, I don't know much about debian, but I guess I can help with vserver ;) [08:09] how can I tell if it is installed? [08:09] debian, or vserver? [08:10] hehehe, vserver :-D [08:10] http://vserver.13thfloor.at/Stuff/testme.sh [08:10] run that on the host ... [08:10] I think it is, but it was aweful easy [08:10] ok [08:12] uh [08:12] :-( [08:12] not good [08:12] let's hear? [08:12] Linux-VServer Test [V0.06] (C) 2003-2004 H.Poetzl [08:12] Can't set the new security context [08:12] : Function not implemented [08:12] chcontext failed! [08:12] Can't set the ipv4 root (Function not implemented) [08:12] chbind failed! [08:12] Linux 2.4.18-bf2.4 i686/chcontext 0.29/chbind 0.29 [J] [08:13] hmm, okay, that _all_ seems a lot outdated ... [08:13] how do I update it? [08:13] do you have a problem with a non-debian kernel? [08:13] nope [08:13] and do you know how to build a kernel by yourself? [08:13] I have done it.. but simple stuff (on freebsd) [08:14] and I had instructions ;-) [08:14] but I would like to try [08:14] okay, basically you download the latest 2.4.24 or 2.4.25-pre8 from ftp.kernel.org [08:14] and then you get appropriate patches from www.13thfloor.at/vserver [08:14] ok [08:15] do you prefer the stable feature poor version, or the development version? [08:18] is development stable at all? [08:22] well, it is not considered that stable, so it's called development, instead of stable ;) [08:22] but I guess it would be called instable or experimental, if it would be that instable ;) [08:27] what do you run? [08:27] well, basically all versions from time to time ... including experimental ... [08:30] do you sell hosting on yours? [08:30] nope, I don't ... [08:31] :-) [08:34] but probably stable is what you want, if you are going to sell vservers to your customers ... [08:42] ok, so I have downloaded and untarred 2.4.24 [08:43] do I need to put it anywhere special [08:43] no, although /usr/src/ is a good place ... [08:43] k [08:46] okay for stable you get the patch at: [08:47] http://www.13thfloor.at/vserver/s_release/v1.24/patch-2.4.24-vs1.24.diff.bz2 [08:47] put it in /usr/src too for example ... [08:47] then patch the kernel like this: [08:47] cd linux-2.4.24 [08:47] bzcat ../patch-2.4.24-vs1.24.diff.bz2 | patch -p1 [08:48] if you have a .config for your current kernel, you can now use that one, otherwise you'll have to either use a default kernel setup, or edit the kernel settings by hand ... [08:50] given there is an existing .config, copy that into the linux-2.4.24 dir, and execute [08:50] make oldconfig [08:50] if there isn't such a file/config, you can get the default by [08:51] yes '' | make oldconfig [08:51] or by doing make menuconfig [08:51] and saving the new defaults ... [09:01] ok, I have the file [09:02] patch-2.4.24-vs1.24.diff in my /usr/src/linux-2.4.24 dir [09:02] so now I type patch -p1 patch-2.4.24-vs1.24.diff [09:02] okay, move it one level up [09:02] ? [09:02] k [09:02] /usr/src/patch-2.4.24-vs1.24.diff [09:02] then enter the kernel source dir: [09:03] cd /usr/src/linux-2.4.24 [09:03] and do [09:03] patch -p1 <../patch-2.4.24-vs1.24.diff [09:03] debian:/usr/src/linux-2.4.24# patch -p1 <../patch-2.4.24-vs1.24.diff [09:03] patch unexpectedly ends in middle of line [09:03] patch: **** Only garbage was found in the patch input. [09:03] debian:/usr/src/linux-2.4.24# [09:03] hmm, you downloaded the bz2, and stored it as .diff, right? [09:04] check that with file ../patch-2.4.24-vs1.24.diff [09:04] I have a file called -rw-r--r-- 1 root staff 2519 Feb 2 21:32 patch-2.4.24.bz2 a [09:04] also [09:04] is that the file? [09:04] hmm, okay label it as on the download ... patch-2.4.24-vs1.24.diff.bz2 [09:05] let me re-download to make sure [09:05] okay [09:06] ok I have patch-2.4.24-vs1.24.diff.gz [09:06] okay, put it in /usr/src [09:06] enter the kernel dir with 'cd /usr/src/linux-2.4.24' [09:06] k, should I unzop it 1st? [09:06] nope [09:06] k one sec [09:06] we do that in one step ... [09:07] drwxr-xr-x 15 root root 4096 Feb 2 21:41 .. [09:07] drwxr-xr-x 15 573 573 4096 Feb 2 22:03 linux-2.4.24 [09:07] -rw-r--r-- 1 root src 33616 Feb 2 22:07 patch-2.4.24-vs1.24.diff.gz [09:07] debian:/usr/src# [09:07] okay [09:07] ok now I am in the linux-2 etc dir [09:07] okay [09:07] zcat ../patch-2.4.24-vs1.24.diff.gz | patch -p1 [09:08] debian:/usr/src/linux-2.4.24# zcat ../patch-2.4.24-vs1.24.diff.gz | patch -p1 [09:08] patch unexpectedly ends in middle of line [09:08] patch: **** Only garbage was found in the patch input. [09:08] debian:/usr/src/linux-2.4.24# [09:08] :-( [09:08] how do you download that files? [09:08] let me use wget [09:08] I used lynx [09:08] one min [09:09] woohoo, ok everything patched [09:09] now what? [09:09] now do you have such an .config file? [09:09] maybe in /boot/blabla.config ? [09:10] hol don [09:10] the process you just did, is known as patching the kernel, by the way ... [09:11] I have a file called config-2.4.18-bf2.4 in /boot [09:11] yeah, that is probably your current config file ... [09:11] ok [09:11] copy that into the kernel tree as .config [09:11] the do [09:11] make oldconfig [09:11] and try to answer the questions as appropriate ... [09:12] so cp config-2.4.18-bf2.4 /usr/src/linux... [09:12] ? [09:12] if you do not know the answer, choose the default, by pressing enter ... [09:12] cp /boot/config-2.4.18-bf2.4 /usr/src/linux-2.4.24/.config [09:12] ok, now in the linux-2.4.24 dir I type make oldconfig? [09:13] yes [09:14] ug [09:14] * IP: Virtual Server Configuration [09:14] * [09:14] virtual server support (EXPERIMENTAL) (CONFIG_IP_VS) [N/y/m/?] (NEW) [09:14] The IPv6 protocol (EXPERIMENTAL) (CONFIG_IPV6) [N/y/m/?] (NEW) [09:14] Kernel httpd acceleration (EXPERIMENTAL) (CONFIG_KHTTPD) [N/y/m/?] (NEW) [09:14] did I mess up just hitting enter there? [09:15] nope ... [09:15] k ;-) [09:16] wow, that was a lot of I had to hit [09:17] says to type make dep now [09:17] well, those where new features since 2.4.18 ... [09:17] ok :-) so type make dep? [09:17] make dep >../Dep.log [09:17] that actually saves you the useless output into that file .. [09:18] but shows you any warnings/errors ... [09:18] debian:/usr/src/linux-2.4.24# make dep >../Dep.log [09:18] md5sum: MD5 check failed for 'hfc_pci.c' [09:18] md5sum: can't open hfc_pci. [09:18] md5sum: can't open hfc_pci [09:18] debian:/usr/src/linux-2.4.24# [09:18] ok done [09:18] make bzImage modules >../Build.log [09:20] this part takes awhile ;-) [09:21] yup, you can probably reduce that time a lot, if you configure the kernel to only build drivers/modules you actually need ... [09:21] (but that is something for the next step) [09:22] ok, bad idea to run exec login in xterm... [09:22] Doener (~doener@pD9E12D35.dip.t-dialin.net) left irc: Quit: Leaving [09:25] Doener (~doener@pD9E12D35.dip.t-dialin.net) joined #vserver. [09:44] ok, thats done now [09:44] finally [09:45] good, now we install that kernel and the modules ... [09:45] ok [09:45] you can do that via make install or by hand, whatever you prefer? [09:45] um.. dont care [09:46] whatever is best I guess [09:46] okay, then we do it manually (more control) [09:46] Do I need to be in front of the box? I am over ssh right now [09:46] hmm depends, what bootloader do you use? [09:46] lilo? grub? [09:47] yeah, hol don [09:48] hmm.. not sure.. is there a way to check? [09:48] well, if you boot that box, what does it 'usually' display, (no need to check though) [09:49] I had someone install debian on it today. and I have never watched the boot screen [09:49] lemme look in messages [09:49] no need, as I said ... [09:50] oh ok [09:50] :-P [09:50] so what do we do now? [09:50] well, what did you do now? ;) [09:50] type more /var/log/messages [09:50] okay, check for a directory in /boot which is called grub [09:50] hold on [09:51] does it exist? [09:51] nope [09:51] okay, then you probably using lilo ... [09:51] :-D [09:51] okay, from within the kernel source dir ... do: [09:51] _shuri (~shushushu@vserver.electronicbox.net) left irc: Read error: Connection reset by peer [09:52] cp -va arch/i386/boot/bzImage /boot/vmlinuz-2.4.24-vs1.24 [09:52] and [09:52] cp -va System.map /boot/System.map-2.4.24-vs1.24 [09:52] do you use lvm or something similar? [09:52] whats lvm? [09:53] done with those copies [09:53] okay, then probably not (lvm = logical volume manager) [09:53] nope ;-P [09:53] okay, you know how to use vi (or some other editor?) [09:53] vi is fine [09:53] okay, edit /etc/lilo.conf [09:54] I am in it [09:55] okay, you see a section which contains your 'current' kernel? [09:55] _shuri (~shushushu@vserver.electronicbox.net) joined #vserver. [09:55] something like this: [09:55] image=/boot/vmlinuz [09:55] label=failsafe [09:55] yes [09:55] # Boot up Linux by default. [09:55] # [09:55] default=Linux [09:55] image=/vmlinuz [09:55] label=Linux [09:55] read-only [09:56] thats the start of the area right? [09:56] okay, copy that entire section, starting with the image... [09:56] and change the following: [09:56] image=/boot/vmlinuz-2.4.24-vs1.24 [09:57] and label=VServer [09:57] ok hang on [09:57] leave the rest as is/was ... [09:58] done [09:58] okay, now run 'lilo' [09:58] just type lilo? [09:58] yup [09:59] from any dir? [09:59] yup [09:59] debian:/usr/src/linux-2.4.24# lilo [09:59] Added Vserver [09:59] Skipping /vmlinuz.old [09:59] Fatal: No images have been defined or default image doesn't exist. [09:59] debian:/usr/src/linux-2.4.24# [09:59] hmm, did you rename that /vmlinuz.old ? [09:59] no, it was already in there [10:00] # Boot up Linux by default. [10:00] # [10:00] default=Linux [10:00] image=/boot/vmlinuz-2.4.24-vs1.24 [10:00] label=Vserver [10:00] read-only [10:00] # restricted [10:00] hmm, interesting, you probably messed up the existing default entry ... [10:00] # alias=1 [10:00] image=/vmlinuz.old [10:00] label=LinuxOLD [10:00] read-only [10:00] optional [10:00] # restricted [10:00] # alias=2 [10:00] thats what it has [10:00] and the .old was there b4 [10:00] where is the 'original' part, I told you to copy? [10:01] 07:57 < Bertl> okay, copy that entire section, starting with the image... [10:01] the part that says /boot is what I changed [10:01] um ok, so I messed up.. what lines should I fix? [10:02] well, do it now 'the other way around' [10:02] copy the entire image=/boot/vmlinuz-2.4.24-vs1.24 ... section [10:02] and rename the image= to image=/vmlinuz [10:02] and the label= to label=Linux [10:02] _shuri (~shushushu@vserver.electronicbox.net) left irc: Quit: changing servers [10:02] but keep the image=/boot/vmlinuz-2.4.24-vs1.24 and label=VServe [10:02] OHHHHHH, so add a new section [10:03] yup ;) [10:05] _shuri (~shushushu@vserver.electronicbox.net) joined #vserver. [10:05] ok [10:05] # Boot up Linux by default. [10:05] # [10:05] default=Linux [10:05] image=/vmlinuz [10:05] label=Linux [10:05] read-only [10:05] # restricted [10:05] # alias=1 [10:05] image=/boot/vmlinuz-2.4.24-vs1.24 [10:05] label=Vserver [10:05] read-only [10:05] # restricted [10:05] # alias=1 [10:05] image=/vmlinuz.old [10:05] label=LinuxOLD [10:05] read-only [10:05] optional [10:05] # restricted [10:05] # alias=2 [10:05] thats what I have now [10:05] okay, now run lilo again [10:06] debian:/usr/src/linux-2.4.24# lilo [10:06] Added Linux * [10:06] Added Vserver [10:06] Skipping /vmlinuz.old [10:06] debian:/usr/src/linux-2.4.24# [10:06] looks better ... [10:06] is it going to load Vserver 1st tho? [10:06] you have a way to reboot the machine if it doesn't come up? [10:06] cuz the machine is 5 miles away and I am lazy [10:06] Yeah, get in the car ;-) [10:07] okay, so you do not want that, right? [10:07] right [10:07] okay, we add just another line to that lilo file ... [10:07] ok [10:07] below label=Vserver [10:08] append="panic=10 auto" [10:08] that should help you in 90% of all cases where something goes wrong ... [10:08] image=/boot/vmlinuz-2.4.24-vs1.24 [10:08] label=Vserver [10:08] append="panic=10 auto" [10:08] read-only [10:08] # restricted [10:08] # alias=1 [10:08] okay, rerun lilo [10:09] done [10:09] the default for lilo is now to boot the 'old' working kernel [10:09] we now tell the amchine to try the new kernel once ... [10:09] ok [10:09] if that fails (not with a panic or something critical), the machine will reboot automagically with the old kernel ... [10:10] _shuri (~shushushu@vserver.electronicbox.net) left irc: Quit: changing servers [10:10] lilo -R Vserver [10:10] done [10:10] and now reboot with shutdown -r now [10:10] will it remember my IP/etc when it reboots? [10:10] yes, everything should work as before ... [10:10] rebooting [10:11] I should take this chat and make a help file [10:11] thank you very much [10:11] np, a help would be nice though ... [10:11] :-D [10:11] you know, linux-vserver is a wiki, you can add pages there easily ... [10:12] I will save/edit this when we are done and post it there [10:12] :-D [10:14] i'm starting to get nervous ;-) [10:14] hmm, no need yet ... takes some time ... [10:14]