[00:03] [raphael] (n=raphael@raphael.netpark.at) left irc: Read error: 104 (Connection reset by peer)
[00:03] [raphael] (n=raphael@raphael.netpark.at) joined #rocklinux.
[00:22] Action: fake off for today
[00:22] <fake> cya
[00:23] <fake> ls
[00:45] _BoS_ (n=BoS@dslb-088-072-034-217.pools.arcor-ip.net) left irc: Read error: 104 (Connection reset by peer)
[00:47] blindcod1r (n=blindcod@tor/session/x-f65a7c9ab949ff36) joined #rocklinux.
[00:47] blindcoder (i=id@tor/session/x-6f1105f9de1651b3) left irc: Nick collision from services.
[00:48] Nick change: blindcod1r -> blindcoder
[00:50] _BoS_ (n=BoS@dslb-088-072-034-120.pools.arcor-ip.net) joined #rocklinux.
[01:10] kasc_ (n=kasc@dslb-084-060-106-111.pools.arcor-ip.net) joined #rocklinux.
[01:19] kasc (n=kasc@dslb-084-060-102-118.pools.arcor-ip.net) left irc: Read error: 110 (Connection timed out)
[01:19] Nick change: kasc_ -> kasc
[08:29] <blindcoder> moin
[08:33] <mnemoc> moin blindcoder :)
[08:43] <_BoS_> moin
[08:45] <th> moin
[08:50] <th> i feel better now.
[08:51] <th> 335 builds total, 335 completed fine, 0 with errors.
[08:51] <th> and this finished as well
[08:51] <th> cool
[08:57] <th> well subversion does not really require apache.
[08:57] <th> but you wont get apr stuff in it without
[08:58] <th> you propably can't run a webdav server then
[08:58] <th> but it's a perfect client though.
[08:58] <th> see bbs target (pkgsel)
[08:58] <th> no apache - but subversion for checkouts
[08:59] <[raphael]> actually I like those lightweight subversion packages, without apache, since that has little dependencies, and for clients it's just fine
[09:01] <th> lets inspect the 600 issue
[09:01] <th> i cant really believe it.. hmm
[09:01] <th> 640
[09:01] <th> but right.
[09:01] <th> something is wrong
[09:02] <blindcoder> 640? where?
[09:02] <th> /usr/include/apr_lib.h for example. part of subversion:dev
[09:02] <[raphael]> th, it was 600, 
[09:02] <th> this happens in current trunk with bbs pkgsel
[09:03] <th> [raphael]: i have a fresh build here with 640 which is bad enough cause the group is root as well
[09:03] <[raphael]> I see
[09:06] <th> that would be a subversion bug. which i cant really believe
[09:07] <th> this only happens if apache is not installed and subversion uses (and installs!) it's own apr
[09:07] <th> damn
[09:08] <th> apache:apr has right permissions
[09:08] <th> so this is a bug when selecting subversion without apache
[09:09] <blindcoder> chmod is your friend :)
[09:09] <th> [raphael]: who needs that apr_*.h files?
[09:09] <th> we would need to split this away in subversion:apr
[09:09] <th> well no. it's just sick
[09:10] <th> is apr from apache? and subversion holds a vendor branch of it?
[09:10] <th> so we have some hold apr version which subversion shipped?
[09:10] <th> subversion: usr/bin/apr-config
[09:10] <th> subversion: usr/lib/libapr-0.so.0.9.7
[09:11] <th> the modes for the libs are okay
[09:14] <th> hmmm should we use flyspray?
[09:14] <th> if so someone should go through the old bugs and mark them obsolete/delete them
[09:14] <th> or file them "still recent"
[09:15] <th> we have 3 year old reports in there
[09:16] <stf^rocklinux> hi all
[09:16] <blindcoder> moin stf^rocklinux 
[09:16] <th> 210 entries at this moment
[09:16] <th> mornging stf
[09:16] <stf^rocklinux> th: that reminds me; I still cannot login to flyspray, have my password mailed to me or create a new account :(
[09:17] <th> ok
[09:17] <th> i try to take care of that
[09:17] <stf^rocklinux> A long time ago it used to work for me...
[09:17] <stf^rocklinux> th: maybe you could try to login with my account or create a test account with my name and send the login and password to me for a test
[09:18] <th> what was your account name?
[09:18] <stf^rocklinux> th: stf
[09:18] <th> NAK
[09:18] <th> there is no stf now.
[09:18] <th> create yourself a new one please
[09:18] <stf^rocklinux> hmm...
[09:20] <stf^rocklinux> th: I registered as stf now... should I receive a confirmation email or something?
[09:21] <[raphael]> th: Subversion provides developer libraries, so you can write your own software around svn, those apr files are probably used to write extensions in connection with apache
[09:21] <th> [raphael]: no
[09:21] <[raphael]> no, what?
[09:21] <th> [raphael]: apr is the apache portable runtime library
[09:22] <th> subversion uses it.
[09:22] <th> and thus provides it if it's not already there
[09:22] Action: blindcoder now killing the -community tree
[09:22] <blindcoder> done
[09:23] <[raphael]> ah, ok
[09:23] <[raphael]> th, but in this case we could supress subversion installing it at all
[09:23] <th> stf^rocklinux: i still cant see you in the users list
[09:23] <[raphael]> subversion itself doesn't need the headers to be installed
[09:23] <th> [raphael]: are you sure?
[09:24] <[raphael]> for using subversion as a program your (most certainly) don't need the headers, and no, I'm not sure since I didn't test it, but that sounds reasonable to me
[09:24] <[raphael]> the question is whether tweaking the "standard behaviour" of a package is reasonable
[09:24] <th> stf^rocklinux: you can't login, can you?
[09:25] <stf^rocklinux> th: no, I always get "Login failed"
[09:25] <th> [raphael]: of course you dont need it for the clients
[09:25] <th> stf^rocklinux: your account creation was not successfull then. let's see if i can create an account
[09:25] <stf^rocklinux> th: and I have cookies enabled ...
[09:25] <stf^rocklinux> th: please do so
[09:28] <th> blindcoder, stf^rocklinux: i added both of you to the flyspray admin group.
[09:28] <th> i dont know exactly what this means.
[09:28] <th> but i guess that way you are able to kill old bugs
[09:28] <blindcoder> YAY
[09:29] <th> blindcoder: i know you do have a habbit of killing.
[09:29] <th> ;-)
[09:29] <blindcoder> MUAHAHAHAHA
[09:29] Action: blindcoder goes to kill a few bugreports as won't fix
[09:29] <stf^rocklinux> th: thanks for creating a flysprac account for me, it works now :)
[09:29] <blindcoder> security patches for glibc22? WON'T FIX!
[09:30] <th> it's 210 now...
[09:30] <th> in that state it does not make sense to add new bugs like the subversion:apr issue
[09:30] <blindcoder> diediedie();
[09:30] <blindcoder> we need mail reminders there, too :)
[09:30] <th> they SHOULD be possible but i dont know
[09:31] <th> blindcoder: perhaps you can test a bit and confirm they DONT work.
[09:31] <th> blindcoder: then see if a new version of flyspray is available which fixes the problem. or if this is a config problem after all
[09:31] <blindcoder> okay
[09:31] <stf^rocklinux> blindcoder: reminders sent to rock-devel if new bugs are opened would be nice 
[09:31] <blindcoder> but first I'm gonna kill kill kill some reporst :D
[09:32] <blindcoder> stf^rocklinux: I'll go from the oldest patches to the newest. you the other way?
[09:33] <stf^rocklinux> blindcoder: ok, but I'll be afk from 10:00 to 19:00 today ... 
[09:33] <blindcoder> heh, okay
[09:35] <blindcoder> "A maintainer/patch-submitter must take a look into the flist to avoid stupid mistakes like usr/usr usr/etc usr/games/bin ... !"
[09:35] <blindcoder> Closed as "Works for me" :D
[09:36] <th> blindcoder: wanna have a new resolution?
[09:36] <th> blindcoder: like "obsolete">
[09:37] <th> you can configure them in the "resolutions" menu
[09:37] <blindcoder> sounds fine
[09:37] <th> well
[09:37] <th> we have deferred
[09:39] <th> daja77_: you should comment/vote on 2006021615383712705
[09:44] <th> anyone wants to test my crystal build of r7247?
[09:45] <[raphael]> th, I probably have a test machine
[09:45] <th> cool
[09:45] <th> would you test it?
[09:45] <[raphael]> yes, indeed :)
[09:45] <th> great
[09:46] <[raphael]> probably, not within a few days though
[09:46] <th> no problem.
[09:46] <th> i'll just upload it and let you know then.
[09:46] <[raphael]> but I have a machine at my sisters... this one needs a ROCK
[09:46] <th> it includes fixes of the CLT errata
[09:46] <[raphael]> yes, that would work fine
[09:46] <[raphael]> CLT?
[09:46] <th> kde-3.5.1
[09:46] <th> [raphael]: chemnitzer linux tag
[09:46] <[raphael]> ah, good
[09:46] <th> [raphael]: errata is on the website
[09:48] <[raphael]> looks good
[09:50] <[raphael]> th, you used the "vanilla" crystal target?
[09:50] ija_ (n=ija@212.80.242.28) joined #rocklinux.
[09:50] <[raphael]> so that also includes KOffice I hope?
[09:51] <th> [raphael]: vanilla trunk-r7472 and vanilla crystal target. pentium2-optim. and bootdisk(486)
[09:52] <daja77_> i dunno if that patch works ..
[09:52] <th> [raphael]: it does. in an old version 1.4.2
[09:52] <th> daja77_: perhaps you could state your objections or opinions so that the patch creators can improve?
[09:52] <th> daja77_: currently it's just stalled.
[10:03] ija (n=ija@212.80.242.77) left irc: Nick collision from services.
[10:03] Nick change: ija_ -> ija
[10:06] <th> [raphael]: r7247 that is. mixed it up.
[10:08] <[raphael]> th, good, KOffice 1.4.2 is just fine... I prefer stable versions over beta versions
[10:08] <th> ok
[10:10] <[raphael]> ah, it turns out that even pentium2 is just optimal since the machine is, AFAIK, a p2
[10:10] <[raphael]> :)
[10:10] <[raphael]> breakfast time....
[10:27] <th> i got a mail from flyspray!
[10:27] <blindcoder> heh
[10:27] <blindcoder> from me closing a bug?
[10:27] <th> Benjamin Schieder (blindcoder) has closed the following task. You are                           
[10:27] <th> receiving this because you are on the notification list.                                        
[10:28] <blindcoder> which one?
[10:28] <blindcoder> I closed a few already :)
[10:28] <th> that was the glibc22 thing
[10:28] <th> stf^rocklinux: and i got one from you
[10:28] <th> Task #211: build env doesn't have TZ set, which breaks fontconfig                               
[10:28] <blindcoder> ah
[10:28] <th> stf^rocklinux: this is still an issue which i found recently
[10:28] <th> stf^rocklinux: only if you dont set TZ in your build host.
[10:28] <th> stf^rocklinux: but you are not forced to do so.
[10:29] <th> so was that mailing working all the time?
[10:30] <blindcoder> yes
[10:30] <blindcoder> but only to people who want to be notified
[10:30] <blindcoder> there doesn't seem to be a general notification optino
[10:31] <blindcoder> okay, two pages of bugs I won't close
[10:32] <blindcoder> and another one from r.r. bites the dust
[10:41] <netrunner> does anyone want to take a look at the diff of my tree? I have no time for one more month to submit them ...
[10:41] <th> netrunner: that's a hard job
[10:41] <netrunner> th: I know :)
[10:41] <netrunner> well ... maybe I'll find some time tomorrow. 
[10:42] <blindcoder> third page
[10:42] <owl> moin
[10:45] <blindcoder> rr must be cursing right now :D
[10:47] <th> because of the mail notifications?
[10:47] <blindcoder> yes :)
[10:47] <th> he'll propably join here. or mailfilter
[10:47] <blindcoder> I closed at least two dozen bugs from him
[10:53] <blindcoder> okay, I'm done closing stuff
[10:53] <blindcoder> now there are 4 pages of bugs left
[11:36] <th> http://iso.rocklinux.de/rock-ftp/official/test-releases/crystal-r7247_cd1.iso
[11:37] <blindcoder> 7247 is when?
[11:37] <th> pretty trunk
[11:37] <th> pretty HEAD
[11:38] <blindcoder> sweet
[11:38] <th> only the arm patches missing
[11:38] <th> that's my latest crystal build
[11:38] <th> with errata from clt fixed
[11:38] <th> that's after joining fake's and my latest journals
[11:38] <blindcoder> \o/
[11:38] <blindcoder>  |
[11:38] <blindcoder> / \
[11:43] blindcoder (n=blindcod@tor/session/x-f65a7c9ab949ff36) left irc: Remote closed the connection
[11:44] blindcoder (n=blindcod@tor/session/x-9de18e99bd14892b) joined #rocklinux.
[11:45] <th> http://iso.rocklinux.de/rock-ftp/official/test-releases/
[11:45] <th> including tarball
[11:46] <[raphael]> great, thanks th
[11:46] <th> bbs bootable iso on its way
[11:47] <[raphael]> th, the crystal iso already includes the bootstrap, no? so it's bootable?
[11:47] <th> we are talking of three different targets here.
[11:47] <th> boot, bbs, crystal
[11:47] <th> both iso images contain the boot target
[11:47] <th> so they are both bootable
[11:48] <th> bbs has nothing to do with bootability
[12:18] <fake> moin!
[12:18] <th> moin fake
[12:19] <fake> th: got some sleep? ;)
[12:19] <th> fake: yea
[12:19] <th> fake: 12h sleep.
[12:19] <th> fake: now i'm fine again
[12:19] <blindcoder> moin fake 
[12:19] <fake> th: yeah!
[12:19] <fake> arm & gcc patches didn't harm test build
[12:19] <blindcoder> fake: regarding the initrd recreation issue...
[12:20] <fake> blindcoder: yeah, let's discuss that
[12:20] <blindcoder> fake: okay, here's my point
[12:20] <blindcoder> fake: I need to change initrd configuration for filesystem encryption
[12:20] <th> fake: did you test that on crystal?
[12:20] <fake> th: no, minimal + bootdisk
[12:20] <fake> th: all code paths covered
[12:21] <blindcoder> fake: so I setup encryption from stone, reboot, encrypt, change configuration, recreate initrd
[12:21] <fake> blindcoder: i can see that. but you also have to agree that the initrd must be recreated when installing a new initrd.img
[12:22] <blindcoder> fake: I don't know what you mean by new initrd.img
[12:22] <blindcoder> fake: that one is created by mkinitrd
[12:22] <fake> blindcoder: the linux26 package runs mkinitrd in the build system
[12:22] <blindcoder> fake: why?
[12:22] <blindcoder> I think it should be run post-installation
[12:22] <fake> blindcoder: at that time, /etc/fstab contains /dev/root as root filesystem - which obviously won't work :)
[12:23] <fake> blindcoder: with it being created kernel-build-time, i can trigger the rebuild whenever /boot/initrd.img is updated
[12:23] <blindcoder> fake: okay. so why not just touch /recreate_initrd?
[12:23] <fake> blindcoder: where?
[12:24] <blindcoder> fake: would trigger initrd recreation
[12:24] <fake> blindcoder: where should i touch it?
[12:24] <blindcoder> fake: where you currently recreate the initrd in your patch
[12:24] <blindcoder> if any_installed "boot/initrd.img" ; then
[12:24] <blindcoder> touch /recreate_initrd
[12:24] <blindcoder> fi
[12:24] <fake> blindcoder: in the postinstall script, it checks wether any package created or updated /boot/initrd.img
[12:25] <th> fake: that's sick.
[12:25] <th> i think we should stop linux26 from calling mkinitrd and use our own one post-install
[12:25] <fake> the problem i have with doing it from an _init_ script is - if it fails, i'm b0rked
[12:25] <blindcoder> th: we just found out that that won'tm work
[12:25] <blindcoder> hmm, true
[12:26] <blindcoder> what would be a good alternative?
[12:26] <blindcoder> recreating the initrd immediately when necessary?
[12:26] <fake> besides, init scripts shouldn't be used for such a purpose imho
[12:26] <fake> yes.
[12:26] <fake> in stone, triggered after changes in the dmcrypt part
[12:26] <th> blindcoder: why does it not work?
[12:26] <blindcoder> well, I want a central way t recreate it whenever necessary
[12:26] <blindcoder> current and future stuff
[12:26] <blindcoder> 12:25 < fake> blindcoder: at that time, /etc/fstab contains /dev/root as root filesystem - which obviously won't work :)
[12:26] <fake> the central way is to trigger 'mkinitrd' ;-)
[12:26] <blindcoder> @th
[12:27] <blindcoder> fake: it is now
[12:27] <fake> what's wrong with that?
[12:27] <th> blindcoder: well - that would be build-time
[12:27] <blindcoder> fake: what will be when we switch to initramfs
[12:27] <th> blindcoder: i'm talking of after everything is installed
[12:27] <blindcoder> fake: then we have to grep everywhere for mkinitrd and change them to mkinitramfs
[12:27] <th> fake: i agree!
[12:28] <fake> whenever a new / updated linux26 package is installed, the initrd needs to be recreated. that's why i chose to 'watch' /boot/initrd.img
[12:28] <fake> ( i didn't test wether the symlink is touched in a package update, but it's in the flists, so the postinstall should be triggered anyways )
[12:28] <blindcoder> if any_installed /boot/vmlinuz* ?
[12:29] <fake> blindcoder: on ppc, it's called vmlinux, on rs6000 it's calld zImage ...
[12:29] <blindcoder> :(
[12:29] <blindcoder> okay, then watch initrd.img
[12:29] <blindcoder> but still
[12:30] <blindcoder> when we change to initramfs then we have to grep through the whole tree and maybe miss something
[12:30] <blindcoder> or we make mkinitrd -> mkinitramfs
[12:30] <blindcoder> a symlink
[12:30] <fake> then let's call it mk1ststage
[12:30] <fake> or something
[12:30] <blindcoder> *idea*
[12:30] <blindcoder> root@ceres:~# mkinitrd
[12:31] <blindcoder> mkinitrd: I am deprecated. Use mkinitramfs.
[12:31] <blindcoder> mkinitrd: Calling it now... have a nice day
[12:31] <blindcoder> exec mkinitramfs
[12:31] <blindcoder> exec mkinitramfs "$@"
[12:31] <fake> problem solved? ;-)
[12:31] <blindcoder> yes, think so :)
[12:31] <blindcoder> I'll rework my patch
[12:31] <fake> very kewl.
[12:32] <fake>  i hate the rubygem-packages
[12:33] <fake> th: didn't you have ruby experience?
[12:33] <th> yes
[12:33] <blindcoder> so far I just don't know how I'm going to do it
[12:33] <fake> th: can you confirm that gem install -l failing doesn't return an error code ?
[12:34] <blindcoder> I'm within the initrd and need to recreate it from there
[12:34] <fake> blindcoder: on 'exit' from the dmcrypt stone screen, ask wether to re-create the initrd... for exmample?
[12:34] <blindcoder> yes, no big deal
[12:34] <fake> *example
[12:34] <blindcoder> fake: BUT
[12:34] <th> fake: i dont do gems
[12:34] <fake> yes?
[12:34] <fake> th: hrm.
[12:35] <blindcoder> fake: reboot -> encrypt filesystems -> adapt dmcrypt configuration -> _recreate initrd_ -> continue initrd sntartup
[12:36] <fake> is stone involved in 'adapt dmcrypt configuration' ?
[12:36] <blindcoder> no
[12:36] <fake> i c
[12:36] <fake> any scripts / tools for automation ?
[12:36] <blindcoder> the dmcrypt configuration is in /etc/conf/dm/mounts
[12:36] <blindcoder> in the form
[12:36] <blindcoder> <device> <status>
[12:36] <fake> you have to recreate the initrd from inside the initrd o_O ?
[12:36] <blindcoder> <device> <mountpoint> <status>
[12:37] <blindcoder> adapting after encryption means changing <status> from encrypt to encrypted
[12:37] <blindcoder> and then you have to recreate the initrd
[12:38] <blindcoder> no, I need an automaton to recreate the initrd under certain conditions
[12:38] <fake> so, i boot into the initrd, encrypt my fses, mount them by hand, chroot, edit /etc/conf/dm/mounts and run mkinitrd ?
[12:38] <blindcoder> no
[12:38] <blindcoder> you have a running system
[12:38] <fake> aye
[12:38] <blindcoder> start stone
[12:39] <blindcoder> set your / filesystem to 'encrypt'
[12:39] <blindcoder> stone creates the config: /dev/foo / encrypt
[12:39] <blindcoder> recreates the initrd
[12:39] <blindcoder> you reboot
[12:39] <blindcoder> the initrd asks you for a passphrase to encrypt the filesystem with
[12:39] <blindcoder> encryption is done
[12:39] <blindcoder> the initrd then adapts the dmcrypt configuration:: /dev/foo / encrypted
[12:39] <th> and could reboot now
[12:40] <blindcoder> and _now_ I need an automaton to recreate the initrd
[12:40] <blindcoder> th: the system will then boot up normally
[12:40] <th> why do you need to recreate initrd?
[12:40] <fake> but you can't re-create the initrd from inside the initrd - you will have to do the whole chroot thing
[12:40] <blindcoder> th: because /etc/conf/dm/mounts is part of the initrd
[12:40] <th> becauuse you need /etc/conf/dm/*?
[12:41] <fake> blindcoder: can't you detect somehow if it has already been encrypted?
[12:42] <fake> blindcoder: like, grep 'encrypted' /dev/hdaX ? ;-)
[12:42] <fake> blindcoder: anyways, after ' the initrd then adapts the dmcrypt configuration:: /dev/foo / encrypted' you could do:
[12:43] <blindcoder> fake: unfortunately I can't autodetect that
[12:43] <th> blindcoder: would be cool if initrd can be smart enough to know what to do without /etc/conf/dm/mounts
[12:43] <blindcoder> th: it could ask the user :P
[12:44] <fake> blindcoder: mount $rootfs /root && chroot /root /bin/bash -> run a script that mounts /sys, proc and dev -> mkinitrd -> exit ; reboot
[12:44] <fake> blindcoder: that *is* an option
[12:44] <fake> blindcoder: asking the user i mean
[12:44] <blindcoder> yes, but not a good one
[12:44] <th> blindcoder: as a fallback. that's ok
[12:44] <blindcoder> it's an emergency option
[12:44] <blindcoder> hmm
[12:44] <fake> blindcoder: if i encrypt my root filesystem, i usually know what i'm doing ;)
[12:45] <blindcoder> fake: yes, but you really don't want to always tell the initrd that
[12:45] <th> so the fallback could state:
[12:45] <blindcoder> *idea*
[12:45] <th> "initrd has not been recreated you now have to answer to me"
[12:45] <blindcoder> th: won't work because the initrd will still have the old information
[12:45] <blindcoder> please let me phrase my idea
[12:45] <blindcoder> in the main initrd script (linuxrc) do the following:
[12:46] <blindcoder> recreateinitrd=0
[12:46] <blindcoder> ...
[12:46] <blindcoder> [ ${recreateinitrd} -ne 0 ] && chroot /root/ /sbin/mkinitrd
[12:46] <blindcoder> exec chroot /root/ /sbin/init "$@"
[12:46] <blindcoder> and the plugins then determine if an initrd recreation is necessary
[12:47] <fake> which plugins?
[12:47] <blindcoder> the dmcrypt plugin, for example
[12:47] <fake> wait
[12:47] <fake> you say you boot up the system normally after encrypting the filesystems ?
[12:47] <blindcoder> of course
[12:47] <fake> aha!
[12:47] <fake> missing information ;)
[12:47] <blindcoder> what else would I do?
[12:48] <fake> i see why you chose the initscript
[12:48] <fake> i have an idea
[12:49] <fake> you could replace /etc/inittab after ecnrypting, so it doesn't start getty, but one script on the first terminal
[12:49] <blindcoder> eww
[12:49] <fake> there you could re-create the initrd, inform the user what just happened, etc
[12:49] <fake> and then re-boot cleanly
[12:49] <fake> you could eben force a stage 1 boot
[12:49] <blindcoder> that reboot is unnecessary
[12:50] <fake> with  exec chroot /root /sbin/init 1
[12:50] <blindcoder> urgs
[12:50] <blindcoder> no
[12:50] Last message repeated 2 time(s).
[12:50] <fake> s/stage/runlevel/
[12:50] <blindcoder> that's the GNU way: GNU's Not Userfriendly
[12:50] <blindcoder> what's wrong with 12:48 < blindcoder> [ ${recreateinitrd} -ne 0 ] && chroot /root/ /sbin/mkinitrd
[12:50] <fake> i would not mind that behaviour. after all, i don't want to continue working before anything is 'finalized' and working
[12:51] <fake> blindcoder: nothing ;-)
[12:51] <blindcoder> fake: but after the dmcrypt plugin finishes everything _sholud_ be finalised
[12:51] <blindcoder> fake: okay :)
[12:51] <blindcoder> then I will do it that way :)
[12:52] <fake> blindcoder: i mean, i would re-boot to see wether it actually worked before creating more things i don't want to loose 8)
[12:52] <blindcoder> of course, but I can assure you that it does work :)
[12:52] <blindcoder> I'm using it on a day-by-day basis
[12:53] <fake> things tend to break when i try them, hehe
[12:54] <blindcoder> fake: and it's just a matter of pride to tell people: sensitive data? sure, just setup encryption, enter your passphrase, reboot and your data is as safe as your passphrase is :)
[12:54] <blindcoder> fake: _please_ break it
[12:54] <blindcoder> I want to know of each and every brekage
[12:54] <blindcoder> I'm very proud of the rockinitrd and the dmcrypt plugin
[12:54] <blindcoder> so please go ahead
[13:04] <fake> blindcoder: i will try at home
[13:05] <blindcoder> thanks
[13:05] <blindcoder> I will go home in an hour or -so
[13:06] <fake> lucky you -_-
[13:07] <blindcoder> hey, it's friday
[13:07] <blindcoder> and I have made enough overtime this week
[13:07] <blindcoder> and last week
[13:07] <blindcoder> and the week before...
[13:09] Action: blindcoder feels overworked
[13:09] <blindcoder> 1/3 of submaster patches are mine :)
[13:13] <blindcoder> ARGH
[13:13] <blindcoder> THOSE AUSTRIANS ARE SO FREAKING RETARDED!!1!
[13:13] <blindcoder> ...
[13:13] <blindcoder> no offense meant to present company
[13:15] <blindcoder> up til now, the software for a specific release was always completely included on the install cds
[13:15] <blindcoder> but now
[13:15] <blindcoder> part of the software is no longer on the cds
[13:15] <blindcoder> but only on the intranet servers
[13:15] <blindcoder> and OF COURSE our network can cope with any kind of network configuration we have to configure for our customers
[13:16] <blindcoder> and OF COURSE the network operator here allows foreign machines into the network
[13:16] <blindcoder> and before anyone asks: _no_, we can _not_ just add another ip address to the machine
[13:17] <blindcoder> because the software is so freaking stupid that it completely wets itself if it discovers an IP address that it isn't licensed for
[13:17] <blindcoder> I need a coffee
[13:17] <blindcoder> and a cold shower
[13:17] <blindcoder> and feierabend >_<
[13:28] <fake> definitely ;)
[13:34] Action: blindcoder off
[13:36] <daja77_> re
[14:43] owl (n=owl@193.93.28.218) left irc: "you don't need me, if you're not willed to believe me."
[15:04] owl (n=owl@193.93.28.218) joined #rocklinux.
[15:44] <daja77_> gah sf downloads are still a pain
[15:47] owl (n=owl@193.93.28.218) left irc: "brb"
[15:48] owl (n=owl@193.93.28.218) joined #rocklinux.
[16:43] daja77 (n=daja77@dslb-088-072-039-243.pools.arcor-ip.net) joined #rocklinux.
[16:55] daja77_ (n=daja77@dslb-088-072-048-112.pools.arcor-ip.net) left irc: Read error: 110 (Connection timed out)
[17:55] <th> cyrus experts here?
[19:07] <stf^rocklinux> re
[19:19] <th> stf^rocklinux: you're 21 minutes too late.
[19:19] <th> 09:35:43 < stf^rocklinux> blindcoder: ok, but I'll be afk from 10:00 to 19:00 today ... 
[19:19] <th> bad boy
[19:20] <th> oh 10 minutes only
[19:20] <th> i'm sorry
[19:20] <th> still!
[19:20] <stf^rocklinux> th: actually I'm back home since ~ 18:00 ;)
[19:21] <stf^rocklinux> th: we were allowed to leave the "Lehrwerkstätte" earlier
[19:30] <stf^rocklinux> got me some extra time to read the IRC log and mails
[19:31] <stf^rocklinux> and I think arc welding is fun, but not if you have to do it 5 hours long ^^
[19:32] <stf^rocklinux> that arc welding "basic training" is part of my study, you know...
[19:37] <fake> hehe
[19:37] Action: fake having fun with asterisk
[19:37] <netrunner> what kind of fun?
[19:38] <fake> configuring our queue
[19:38] <fake> the welcome queue that is
[19:38] <fake>  -- Stopped music on hold on SIP/phone2
[19:40] <fake> o_O
[19:45] <icelbox> *sighs* I know that too well
[19:48] <fake> that moh is getting on my nerves already
[19:49] <netrunner> how is atd, running as "daemon", supposed to remove atjob files that are mode 600 and created/owned by 'root'?
[19:49] <fake> anyway, i'm off for today
[19:50] <fake> by being +s'ed ?
[19:50] <netrunner> my atd is not +sed
[19:50] <fake> hm...
[19:50] <fake> anyway - cu tomorrow
[19:51] <fake> visitors from .de arriving soon, have to clean up a little 8)
[19:51] <netrunner> cu
[19:52] <stf^rocklinux> cu
[20:38] <th> stf^rocklinux: does your vote on my rescue-target patch mean that you're playing with my rescue target?
[20:38] <stf^rocklinux> no
[20:39] <stf^rocklinux> th: I found out there are at least two different ways to use the vote feature:
[20:39] <stf^rocklinux> 1) a vote means: I tested the patch and it worked
[20:40] <stf^rocklinux> 2) a vote means: I think the patch is worth testing
[20:41] <stf^rocklinux> I used to use vote like in 1) but now I prefer 2)
[20:42] <stf^rocklinux> with 2) the least I do is read the patch for obvious errors...
[20:43] <stf^rocklinux> and of course I try to understand what the patch is about ^^
[20:44] <th> yea
[20:44] <th> we need to different votes for this
[20:44] <th> i think that'll be in smng
[20:44] <th> clifford: it will?
[20:46] <stf^rocklinux> I think it would be useful to see in sm which patches were successfully tested by someone
[20:48] <stf^rocklinux> were 'tested' is rather vague... could also be called 'ready to apply' or something
[20:50] <stf^rocklinux> see it as a double vote :P
[20:53] <th> yea
[21:35] <fake> wee! 64bit userland is up
[21:36] <fake> 32 bit non-static lilo from the old userland in my mbr - let's hope i never need to update my kernel 8)
[21:36] <fake> well, of course it's not the non-static lilo in my mbr, but in /usr/sbin
[21:53] <th> fake: did you cross compile that?
[21:53] <th> would you upload a bbs build?
[21:53] <fake> th: i can upload the minimal-gems
[21:53] <fake> th: but you'll have to come up with your own ideas on how to install it 8)
[21:54] <fake> th: i can also upload bbs gems
[21:54] <fake> once i got xorg to compile...
[21:54] <fake> right now it complains that it doesn't support the C64, hehe
[21:55] <fake> (floating point operation, of course)
[23:53] <esden> hi everyone
[23:54] <owl> hi esden 
[23:54] <esden> hi owl 
[23:54] <esden> owl: one thing: V for Vendetta is a must see
[23:54] <esden> and I think you will like at least the message of the film
[23:54] <esden> for further details read my blog *GG*
[23:57] <owl> esden: hehe. well... i guess i will may be watch it if it arrives in ND's cinemas... cough*
[23:57] <esden> owl: I hope you will ;)
[23:57] <owl> what about your photography? long time seen no new pics... 
[23:58] <owl> yes, i tthink so... but i guess first i will watch the cabaret on march, 28 ;)
[23:58] <owl> ever seen 'martin buchholz'?
[23:59] <esden> owl: I lack harddisk space at the moment. My photoshop installation is not working and the biggest problem I lack time. But the next days it should change as my laptop gets repaired, my life gets more coordinated and my usb external disk comes back from repair...
[23:59] <esden> owl: no I have not seen him
[00:00] --- Sat Mar 18 2006