T2 IRC Log: 2007-03-02

This is the log as captured by an IRC bot in the channel. The statements are those of the individual people and might not neccessarily reflect the policy and legal rules as set forth by the T2 SDE Project.

« prev | next »

--- Log opened Fri Mar 02 00:00:25 2007
00:15 < Stelz> 'night Shingoshi
00:29 -!- d-marc [n=d-marc@HSI-KBW-085-216-123-180.hsi.kabelbw.de] has quit ["KVIrc 3.2.4 Anomalies http://www.kvirc.net/"]
01:31 -!- mtr_ [n=Michael@kobz-590ca492.pool.einsundeins.de] has joined #t2
01:40 -!- mtr [n=Michael@kobz-590ca49f.pool.einsundeins.de] has quit [Read error: 60 (Operation timed out)]
01:40 -!- mtr_ is now known as mtr
04:08 -!- idealm [n=ideal@CPE-203-45-99-98.nsw.bigpond.net.au] has joined #t2
04:30 -!- idealm [n=ideal@CPE-203-45-99-98.nsw.bigpond.net.au] has quit [Read error: 104 (Connection reset by peer)]
04:30 -!- idealm_ [n=ideal@CPE-203-45-99-98.nsw.bigpond.net.au] has joined #t2
05:39 < Shingoshi> Back again
08:13 -!- mtr_ [n=Michael@kobz-590cb60d.pool.einsundeins.de] has joined #t2
08:20 -!- LMJ_Work [n=c3196415@laf31-2-82-224-107-105.fbx.proxad.net] has joined #t2
08:21 -!- mtr [n=Michael@kobz-590ca492.pool.einsundeins.de] has quit [Read error: 60 (Operation timed out)]
08:21 -!- mtr_ is now known as mtr
08:23 < LMJ_Work> moin moin
08:23 < LMJ_Work> gcc error on stage2 from a desktop target from Trunk :
08:24 < LMJ_Work> !> /tmp/ccPyk0Wf.s: Assembler messages:
08:24 < LMJ_Work> !> /tmp/ccPyk0Wf.s:885124: Fatal error: can't close .libs/gnu-xml.o: No space left on device
08:24 < LMJ_Work> but got some free space
08:45 < rxr> re
08:48 < Stelz> rehi rxr
08:49 < Stelz> moin LMJ
08:52 < Shingoshi> Hi guys!
08:54 < rxr> hi Shingoshi, Stelz and LMJ_Work
08:54 [Users #t2]
08:54 [@ChanServ] [ idealm_] [ LMJ_Work] [ rxr ] [ Stelz ]
08:54 [ Capey ] [ juri_ ] [ mtr ] [ Shingoshi] [ valentin]
08:54 [ CIA-8 ] [ LMJ ] [ R4gnar0k] [ sparc-kly]
08:54 -!- Irssi: #t2: Total of 14 nicks [1 ops, 0 halfops, 0 voices, 13 normal]
09:17 < Shingoshi> Hallo!
09:20 < CIA-8> rene * r22788 /trunk/package/base/file/file.desc: * updated file (4.19 -> 4.20)
09:36 < LMJ_Work> moin Shingoshi & rxr
09:36 < LMJ_Work> you saw my previous messages rxr ?
09:39 < CIA-8> rene * r22789 /trunk/package/editors/tea/ (hotfix.patch tea.desc): * updated tea (15.0.1 -> 16.0.4)
09:39 < rxr> no space left ?
09:47 < CIA-8> rene * r22790 /trunk/package/graphic/fbv/fbv.desc: * updated fbv (0.99 -> 1.0b)
09:50 < CIA-8> rene * r22791 /trunk/package/x11/rox-filer/rox-filer.desc: * updated rox-filer (2.4.1 -> 2.6)
09:55 < CIA-8> susan * r22792 /trunk/package/gnome2/rhythmbox/rhythmbox.desc: * updated rhythmbox (0.9.7 -> 0.9.8)
09:56 < LMJ_Work> yep rxr
09:56 < LMJ_Work> i have free space on the device ;)
09:56 < rxr> that but that's on /tmp
09:56 < rxr> maybe you have a tmpfs that is nearly full ?
10:03 < CIA-8> rene * r22793 /trunk/package/themes/murrine/murrine.desc: * updated murrine (0.41 -> 0.51)
10:20 < CIA-8> rene * r22794 /trunk/package/games/freedroid_rpg/freedroid_rpg.desc: * updated freedroid_rpg (0.10.0 -> 0.10.1)
10:44 < CIA-8> rene * r22795 /trunk/package/filesystem/nfs-utils/ (hotfix.patch nfs-utils.desc): * updated nfs-utils (1.0.10 -> 1.0.11)
11:08 < CIA-8> rene * r22796 /trunk/architecture/avr32/ (kernel.conf kernel.conf.m4 pkg_linux26_post.conf):
11:08 < CIA-8> * most AVR32 systems (right now anyway) have quite limitted RAM setups
11:08 < CIA-8> and not all parts of the kernel build (e.g. VGA console support does
11:08 < CIA-8> not :-), thus force an exactly matching kernel config, for now
11:09 -!- idealm_ [n=ideal@CPE-203-45-99-98.nsw.bigpond.net.au] has quit [Remote closed the connection]
12:31 -!- sepp [n=sepp@p213.54.168.196.tisdip.tiscali.de] has joined #t2
12:31 < sepp> moin :)
12:37 < rxr> moin sepp :-)
12:37 < rxr> http://www.t2-project.org/developer/soc.html
12:38 < rxr> ^- any notes ?
12:38 < sepp> working multilib sounds good
12:42 < sepp> well, i dont really know what llvm is good for
12:44 < rxr> it's a Low Level Virtual Machine and compiler tool infrastructure
12:44 < rxr> among high-level opimization and link optimization among a whole lot of other stuff
12:45 < rxr> it allows compiling C/C++/et al. into bytecode that can be just-in-time run in the LLVM ...
12:45 < rxr> Apple pays the top developers these days ...
12:45 < sepp> so you run everything on a vm and optimize everything at runtime?
12:45 < rxr> yes
12:45 < sepp> like the dynamo thing hp did some years ago
12:45 < rxr> do not know dynamo
12:46 < rxr> T2 could build arch independant packages then :-)
12:46 < rxr> the C++ compiler framework of LLVM is as good that GCC people think about integratino .-)
12:46 < rxr> and apple hired the lead developer
12:46 < sepp> they wrote an pa vm reading pa machine code and with jit runtime optimization upto 30% speed increase
12:46 < rxr> it's said the next OSX will dynamically optimize the OpenGL engine based on LLVM ...
12:48 < Shingoshi> Are you saying that pkgs would run on any machine, and be optimized just before execution.
12:49 < sepp> sounds like smalltalk :)
12:49 < Shingoshi> rxr: ^^ ??
12:50 < Shingoshi> Is that what LLVM is about?
12:50 < CIA-8> rene * r22797 /trunk/architecture/avr32/kernel.conf: * avr32/kernel.conf v2
12:50 < rxr> Shingoshi: yes, could
12:50 < Shingoshi> How far off?
12:51 < rxr> Shingoshi: follow the llvm link on the soc page and read over the documentation ß
12:51 < rxr> far off ?
12:51 < Shingoshi> How long before realization?
12:52 < Shingoshi> Konq isn't linking/
12:52 < Shingoshi> Let me try firefox.
12:53 < rxr> Shingoshi: depends when someone volunteers to take a look and do the work
12:55 < sepp> it sounds interesting but i see no real benefit, beside you-can-do-it
12:56 < Shingoshi> Where are the links supposed to go? I could do some of that, but then I need priviledges to do so.
12:56 < sepp> llvm.org
12:56 < rxr> sepp: zero-install alike target could build once and run anywhere
12:56 < rxr> just the llvm would need to have support
12:56 < rxr> beside potentially beeing faster as LLVM has link-time optimization and the LVM can optimiize at runtime
12:57 < rxr> e.g. bounds checks and even inline just-in-time ...
12:57 < rxr> and it can be used as just an alternative compiler
12:57 < rxr> optimizing a bit different from gcc ...
12:58 < rxr> sepp: that is the same for the other OS kernel integration parts, it can be done, but we do not have a direct benefit, aside easing using those, installing packages out of one meta-data repository and the like
12:58 < rxr> and PR of course ...
12:59 < Shingoshi> Can you use this compiler now?
12:59 < Shingoshi> I just downloaded it.
13:01 < sepp> :)
13:01 < LMJ_Work> well, i disabled tmpfs rxr
13:03 < Shingoshi> rxr: Can you use this compiler now? I am ready to run configure on my system now.
13:04 < sepp> not now, it is a project idea ...
13:05 < Shingoshi> But the LLVM is fully functional code?
13:07 < rxr> yes
13:07 < rxr> but not in wide use, thus it has rough edges .-)
13:07 < Shingoshi> Why not use this now for all further compilations of our projects?
13:07 < Shingoshi> Rough enough to do harm?
13:11 < Shingoshi> rxr: ^^ ??
13:11 < Shingoshi> Would it compromise our system?
13:13 < rxr> because such changes take time
13:13 < rxr> we have an installed user-base we want to deliver with regularly, stable update
13:15 < Shingoshi> So what if there existed a situation where LLVM was using T2 to develop their system? Wouldn't that help everyone to iron out the bugs better?
13:15 < rxr> LLVM does not need T2 to develop their compiler ... :-)
13:16 < rxr> as the GCC folks need no specific distribution to develop on ...
13:16 < Shingoshi> Is it better or just different?
13:16 < Shingoshi> Oh,ok
13:16 < Shingoshi> So, how would we benefit from this now, if we could?
13:18 < Shingoshi> juri_: Are you still here? If so, check out the LLVM system. Combined with T2, I think you would be guaranteed a higher level of multi-arch functionality>
13:19 < Shingoshi> rxr: Is that right?
13:19 < Shingoshi> Tell me. How can I build this so that you can use it?
13:20 < Shingoshi> You may not have the time, but I do.
13:21 < Shingoshi> I am running the compilation now.
13:23 < Shingoshi> It just crashed. Oh well.
13:24 < rxr> Shingoshi: when I write all the details down here I can implement it in the same time anyway ... :-)
13:24 < Shingoshi> ok
13:24 < rxr> maybe check llvm out and test it out ...
13:25 < rxr> the multi-arch bytecode is unique to LLVM, regarding the optimizations it is better in some areas and different in others. ...
13:25 < Shingoshi> But let me see if I am correct. If we built T2 on LLVM, T2 would have a higher level of cross-arch functionality?
13:26 < rxr> not a higher level
13:26 < rxr> we have this already
13:26 < rxr> but then you would have one binary that runs in the LVM of all architectures
13:26 < Shingoshi> f/com.o This is the error I have.
13:27 < Shingoshi> So this would mean that once you have llvm installed on a system, any system that has it would use the same binaries as the rest?
13:29 < Shingoshi> rxr: f/com.o This is the error I have.
13:32 < Shingoshi> I am wondering if it crashed on the compilation of ada? Slamd64 doesn't have a working ada/gnat. I've run into trouble with this before. It is really why I went looking for a better build system and found yours.
13:37 < Shingoshi> rxr: Do you have a target which just builds compilers? Is it even possible to do only that?
13:37 < sepp> i like SDECFG_ABORT_ON_ERROR_AFTER, such a neat name :)
13:38 < Shingoshi> rxr: Can I build just kernel, glibc, and gcc as a target?
13:39 < Shingoshi> bbl8r
13:39 < rxr> sepp: yeah, I love that one, too
13:40 < rxr> Shingoshi: just building compilers is possible, yes
13:42 < sepp> why does it the opposite?
13:44 < rxr> sepp: mnemocs wonder logic ...
13:45 < rxr> we're off for lunch - cu
13:56 < Shingoshi> Then that's what I will do as my first target.I will build all the development software you have available with the kernel included.
13:57 < Shingoshi> Can I use the embedded target as my template?
13:57 < Shingoshi> No extraneous pkgs.
14:02 < Shingoshi> rxr: Do you have the lilo pkg.
14:03 < Shingoshi> Found it.
14:04 < Shingoshi> rxr: Can I simply use the following in my target to build all available libraries: lib* ?
14:04 < Shingoshi> Are wildcards useable in targets?
14:06 < sepp> you can use them in pkgsel etc
14:07 < sepp> target/generic/pkgsel/10-minimal-xorg.in ...
14:07 < Shingoshi> I mean in the 00-minimal.in?
14:08 < Shingoshi> Can I just have a line which reads; X lib*
14:10 < sepp> that will enable 250 packages starting with 'lib'
14:10 < sepp> most probably not what you want :)
14:11 < Shingoshi> That's ok. A lot of times, other pkgs won't build without them. So I want to start out with every possible dependency being built to begin with.
14:12 < Shingoshi> Am I still wrong?
14:12 < sepp> you do not want "X lib*" because it will build every package starting with "lib"
14:13 < sepp> a gazillion things you do not want for sure
14:13 < Shingoshi> Yes, every lib.
14:14 < Shingoshi> The X appears on every line in 00-minimal.in.
14:14 < sepp> not every lib, lib* does not match glibc ...
14:14 < sepp> X means enable, O disable
14:14 < Shingoshi> No, I have glibc already included.
14:14 -!- LMJ_Work [n=c3196415@laf31-2-82-224-107-105.fbx.proxad.net] has left #t2 []
14:15 < Shingoshi> Will building lib* cause other pkgs to be built also? Or only those I have explicitly stated.
14:16 < sepp> pkgsel does no dependency checking or something like that
14:16 < Shingoshi> Maybe I can create a target just for libs?
14:17 < Shingoshi> How long would it take to build just the 00-minimal.in and nothing else?
14:17 < sepp> on a modern box some hours
14:18 < sepp> 4 maybe
14:18 < Shingoshi> Opteron 1.8G dual-core
14:19 < sepp> try it :)
14:19 < sepp> i dont know exactly
14:20 < Shingoshi> Well, I can let it run and go to bed for awhile.
14:24 < Shingoshi> rxr: I hate to keep asking you this. But I really would like to know specifically how to create my pkgs as .tlz. I would rather do it in one step, than having to go back and fix it later. I can use slack's makepkg to do it, but I don't know where. Is this something I specify during Config/target? Can I tell it to use makepkg to pkg the binaries?
14:28 < Shingoshi> I am reading Config now.
14:28 < Shingoshi> Again.
14:28 < sepp> there is an option named SDECFG_PKGFILE_TYPE
14:29 < sepp> under expert options
14:29 < sepp> '- Binary package format' ...
14:30 < sepp> is .tlz tar.lzo?
14:31 < Shingoshi> no. lzma
14:32 < Shingoshi> sepp: .tlz is lzma.
14:34 < sepp> well, if it is important for you, you could add lzma support
14:37 < Shingoshi> It's important in that I am building packages to replace slackware's own.
14:37 < Shingoshi> Real Important!
14:38 < Shingoshi> Is lzma support not already included?
14:39 < sepp> no
14:39 < Shingoshi> Your pkgs have some sort of desc file, right?
14:39 < sepp> yes, readable files
14:39 < sepp> ascii
14:40 < Shingoshi> Where are the pkgs built into binaries? If I knew that, I could intercept that and run makepkg there instead.
14:40 < Shingoshi> ascii is good.
14:40 < sepp> scripts/Build-Target
14:41 < Shingoshi> Is that where the SDECFG_PKGFILE_TYPE comes in?
14:42 < sepp> yes
14:42 < Shingoshi> Basically, I will need to replace the line with my own code to use makepkg instead.
14:42 < Shingoshi> I can read the T2 desc into makepkg for slack-desc files.
14:43 < sepp> yes, add one case lmza
14:43 < sepp> lzma
14:43 < sepp> guess you can use it together with tar
14:44 < Shingoshi> During running of Config, or can I edit the Config itself?
14:44 < sepp> uhm, what?
14:44 < sepp> i am too slow to follow today
14:44 < Shingoshi> No, I need to use makepkg instead, or else slack pkgtools won't recognize them as pkgs.
14:45 < Shingoshi> Inside the Config file in /scripts. Can I edit it to always use my pkg format as the default?
14:46 < sepp> you can once you added support for .tlz to the scripts
14:46 < Shingoshi> I need to do something like: cp desc slack-desc for slackware.
14:47 < Shingoshi> So I need to edit /scripts/Config
14:48 < sepp> sorry, i dont know a thing about slackware
14:49 < Shingoshi> sepp: ^^ ?? I mean on T2's end. I can take care of slack's end. But I need to know which lines to edit in Config to permanently change this.
14:50 < sepp> grep SDECFG_PKGFILE_TYPE
14:50 < sepp> :)
14:51 < sepp> i have to run away now, cu
14:51 < Shingoshi> I did that. But I can't find SDECFG_PKGFILE_TYPE=***
14:52 < Shingoshi> I found all sorts of $SDECFG_PKGFILE_TYPE
14:52 < Shingoshi> But no SDECFG_PKGFILE_TYPE=***
14:55 < sepp> look into Build-Target and find the SDECFG_PKGFILE_TYPE things
14:55 < sepp> and maybe the other places like config.in
14:56 < sepp> cu later :)
14:58 < Shingoshi> I think I finally found it. Thank you!
14:58 < Shingoshi> Bye!
15:03 < LMJ> moin moin
15:14 < Shingoshi> Hallo!
15:16 < rxr> btw. I strongly suggest to name those files .tar.lzma
15:17 < rxr> the short forms are arely used anyway, and as you see everyone here guessed it's lzo and no lzma ...
15:18 < Shingoshi> I have it specifically written as tlz ) compressor=lzma ;;
15:19 < Shingoshi> It's possible pkgtools-tukaani will recognize .tar.lzma as a valid pkg format. I need to check.
15:21 < Shingoshi> I can create a second line to state what you have suggested.
15:21 < Shingoshi> So that there will be both.
15:33 < Shingoshi> I just checked with Larhzu. It doesn'currently do that. He said he could change it though.
15:34 < Shingoshi> He's the one who wrote the lzma patch.
15:34 < Shingoshi> patches!
16:17 < Shingoshi> If X is use, and O is don't, what is "="?
16:18 < Shingoshi> In 00-minimal.in?
16:19 < Shingoshi> bbl
16:31 < rxr> = is get default state from the package
16:39 < Shingoshi> ok. Thank you.
16:40 < Shingoshi> If I add our lzma patch to the mc pkg dir, will that auto patch mc with lzma, or do I have to specify it somewhere as well?
16:42 < rxr> mc as in midnight commander?
16:42 < Shingoshi> yes
16:42 < rxr> yes patches are auto-applied
16:43 < Shingoshi> So I can add as many patches as I want by simply dropping them in the pkg's dir?
16:53 < rxr> yes
16:57 < Shingoshi> Amazing!! I am definitely in LOVE!!!
17:02 < juri_> i'm disapointed to find llvm isn't GPL'd or LGPL'd or BSD'd.
17:03 < Shingoshi> Hi beautiful! I missed that! So what is it?
17:04 < Shingoshi> It seems to be one of those university licenses like the ones from MIT.
17:05 < Shingoshi> It's a modification of GPL.
17:06 < juri_> AKA, incompatible with my code.
17:06 < Shingoshi> The license is very brief.
17:06 < juri_> no-one has built linux on top of llvm, so openmosix dosent apply.
17:06 < Shingoshi> How so!
17:06 < Shingoshi> How does it restrict you?
17:07 < juri_> honestly, i'm not sure. i just stay away from non-FSF approved licenses as a rule. ;)
17:07 < juri_> there are other problems with it, as well.
17:07 < Shingoshi> Explain/
17:07 < Shingoshi> Let me say, I am glad you are still here!
17:08 < juri_> well, until your kernel/OS runs under LLVM, migrating tasks would be akin to migrating LLVMs between machines. you wouldnt get the "neat features".
17:09 < Shingoshi> It seems that you would build one kernel for all machines. But I may be wrong.
17:09 < juri_> you could make a "new" type of process handler that executed llvm under your linux kernel.. that'd work. but without one, making llvm and OM work together is a far far far away goal.
17:09 < Shingoshi> I am seriously interested in this in a LTSP system.
17:10 < juri_> get to coding, instead of kicking around ideas all the time. :P
17:10 < Shingoshi> So, what can I do to assist you?
17:10 < juri_> see above. ;P :P
17:10 < Shingoshi> I saw it. How do I compile quilt?
17:10 < rxr> well - llvm is userspace, so the llvm processed would just be mirgrated around
17:11 < juri_> good question. i dunno. i just apt-get it. ;)
17:11 < Shingoshi> I'm not Debian.
17:11 < rxr> a xen like approach, that is run the kernel in a LLVM is a totally different, not yet existing project
17:11 < rxr> it would mean several man year of establishing some LLVM on bare metal to run a single generic kernel in that
17:11 < juri_> llvm would be neat as a binary type and scheduler/integrated_interpreter, in the standard kernel.
17:11 < rxr> that definetly a huge research project far from beeing trivial ...
17:12 < juri_> if the kernel posessed a machine interpreter of any sort inside of it, we could migrate processes using OM between those mchine interpreters, without moving the interpreter itsself.
17:13 < juri_> think: BOCHS in the kernel.
17:13 < Shingoshi> This is why I brought you here. juri_ I am really PLEASED!!
17:14 < juri_> shingoshi: i'm afraid i'm "off topic" for this channel. ;P
17:14 < juri_> tho, it was worth the visit, just to get shown llvm. not that i'll be working toward that soon... its just nice to see.
17:14 < Shingoshi> I don't think so.This is a build environment. Can you build OM on T2?
17:15 < juri_> rxr said it best earlier: GCC does not need a distribution to wrk on their compiler. neither does openmosix need one to work on our kernel patches.
17:15 < Shingoshi> Please stay here. At least monitor it.
17:15 < juri_> or, more to the point, with debian and fai, i've already built my own, thanks. :)
17:16 < juri_> i'll stay until its boring, or obviously time to go. the last 24 hours werent dead boring. ;P
17:16 < Shingoshi> But one thing I have seen already which you may have missed. You can't impose Debian on others and expect OM to be for everyone.
17:17 < Shingoshi> To require pkgs that are specifically Debian is a deterrent.
17:18 < Shingoshi> It's like saying, you can't run OM unless you run Debian!
17:18 < juri_> e dont. we have packagers for redhat, and other systems.
17:19 < juri_> usually, a member of a distribution comes to us, saying they want to handle openmosix for their distro.
17:19 < Shingoshi> That's where T2 comes in. You then have a system which is not specific to Debian, which now it is, if I have to have quilt.
17:19 < juri_> and theres a large group of live-cd builders that suround us.
17:19 < juri_> quilt is free software. you can build it on any distro. its not our fault your distro dosent make it easy to install. :)
17:20 < Shingoshi> I looked in the pkg and could find a configure.
17:20 < Shingoshi> couldn't find configure
17:20 < juri_> not all packages use configure scripts. :)
17:21 < Shingoshi> Let me check again for the Makefile.
17:22 < Shingoshi> I am sorry. I must have been in the wrong pkg. quilt has configure.
17:23 < Shingoshi> Well at least 0.46 does. I must have gotten a binary of 0.6-5
17:24 < Shingoshi> I will go back and try and find the source for 0.6-5 of quilt. SORRY. I was wrong, at least partly.
17:25 < Shingoshi> I see what's wrong. The latest version of quilt is java.
17:26 * juri_ raises eyebrow.
17:28 < Shingoshi> http://quilt.sourceforge.net
17:28 < Shingoshi> quilt is a java development tool. Do I have the wrong quilt?
17:29 < Shingoshi> Am I laying on this bed without covers?
17:29 < Shingoshi> OMG
17:30 < juri_> try savannah.nongnu.org/projects/quilt/
17:30 < Shingoshi> Thank you!
17:32 < Shingoshi> Ok, I had the right one to begin with. I went to the wrong site and found another. So everything should be ok.
17:36 < Shingoshi> I can't build it, Needs glibc-2.4. That's what started all of this to begin with. A very circuititous path indeed. I had trouble building glibc. And that's what led me here to T2. Because Slamd64 is incomplete for some larger things.
17:36 < Shingoshi> I was trying to build OM recently.
17:36 < juri_> the circle is complete, eh? :)
17:37 < Shingoshi> That's how I got distracted. Yes, circle complete!
17:38 < Shingoshi> So I really do need to build T2 first. Just so I can have all of the build tools I need for other projects.
17:40 < Shingoshi> So that also answers your earlier question if I tried to build OM. Answer, yes.
17:44 < Shingoshi> I just installed quilt. Slamd64 had it as a pkg through one of the third party devels.
17:44 < Shingoshi> So now, I can try and build OM. Life is funny!
17:45 < Shingoshi> juri_: ^^ !!
17:54 < juri_> yay? :)
18:05 < Shingoshi> This is the command to run to get the kernel version: version=$(ls ./kernel | grep 2.6) That's for my build script.
18:12 < Shingoshi> Don't I have to do "make modules", and "make $DESTINATION_PATH modules_install"?
18:12 < Shingoshi> And I also think I need to build the headers as well?
18:13 < Shingoshi> juri_: ^^ ??
18:21 < Shingoshi> juri_: What is this about the devutils dir? Can that be inside my $DESTINATION_PATH?
18:30 < juri_> honestly, i dont think many of us get that far. ;)
18:31 < juri_> yes, you'll have to perform your distro's normal method of replacing your kernel, whatever that may be.
18:36 < Shingoshi> Please check this and tell me what to fix with headers: http://rafb.net/p/WfBMW656.html
18:38 < Shingoshi> You've been nagging me to build openMosix, and you guys can't even do so. Thanks a lot!
18:38 < juri_> we can, we just dont. ;P
18:38 < juri_> you mistake what i'm saying. the directions at present are for building, for the point of finding bugs.
18:38 < Shingoshi> Yes, I forgot to put devutils in there.
18:39 < Shingoshi> OK.
18:39 < juri_> you've got one built, and aparently are intent on trying to use it. but as is, the 2.6 stuff wont migrate a "normal" process.
18:39 < Shingoshi> Other than that, It is virtually unusable.
18:40 < juri_> bingo! :P
18:40 < Shingoshi> Damn!
18:40 < Shingoshi> LOL LOL LOL
18:40 < juri_> why do you think i've been saying we need to work on it? :)
18:40 < Shingoshi> OK
18:40 < juri_> i'll go ahead and flesh out the docs, and how to reproduce the "first bug".
18:41 < juri_> but that wont be done till monday at the latest. i'm two bugs behind (gift, and alsa), and i really need to treat them.
18:41 < Shingoshi> Why couldn't you start with a working running kernel and move on from there?
18:41 < juri_> whats in svn is a working, running kernel. i think. ;)
18:42 < juri_> i dont have it running on any hardware myself, i just built a box for it last night.
18:42 < Shingoshi> You THINK???? lol lol
18:42 < Shingoshi> Can I at least run my system with it?
18:42 < Shingoshi> Forget about the clustering.
18:42 < juri_> i believe so. ;P
18:43 < Shingoshi> Ok, That's better.
18:43 < juri_> i've got an earlier version running on one of my laptops.
18:43 < juri_> but, i dont have the current version running.
18:43 < Shingoshi> Are there earlier versions which are KNOWN to run?
18:44 < juri_> yes, earlier versions had more functionality, but no, i dont know what exact svn release number.
18:44 < juri_> so, if you run that kernel, tell me, so i'll know we havent broken anything too horribly. ;)
18:45 < juri_> BRB, lunch.
18:45 < Shingoshi> Is it possible for your team to follow the example of the main kernel team, and keep at least one perfectly running default kernel?
18:46 < Shingoshi> Kind of like 2.6 for stable, and 2.7 for devel.
18:46 < juri_> not enough manpower.
18:46 < juri_> for that, we'd need a known feature to test.
18:47 < juri_> now, i'll do that, since you've expressed an interest.. but it'll be a few days before i have "this version works for X, this version dosent"
18:47 < Shingoshi> There would be no need for more manpower. If you had that, more people would be willing to run them for testing and report bugs back to you.
18:47 < Shingoshi> Great!!!
18:48 < juri_> i dont disagree. i've just been working on the build system, to get you this far. :)
18:48 < Shingoshi> I am glad you are here with us!!!!
18:48 < juri_> i may not be, longterm. i am, after all, offtopic for a distro channel. ;P
18:48 < rxr> (t2 is not yet another distribution ... :-)
18:49 < Shingoshi> Stick with me. You'll see that you ARE in the right place!!!
18:50 < Shingoshi> It needs something like this to give it the extra oomph to attract more users. You could help with that. Besides, you seem to be brilliant!
18:50 < juri_> most kernel hackers are. ;P
18:51 < Shingoshi> You are every bit as capable as I in conceptualizing. You proved that earlier in your discussion with rxr about llvm.
18:51 < Shingoshi> We need stronger concepts!
18:52 < Shingoshi> Cohesive concepts.
18:53 < Shingoshi> rxr: We are not the very far from it.
18:53 < Shingoshi> You let me bring more people on here, and it will be!
18:53 < Shingoshi> JoinT@ Ventures!
18:53 < Shingoshi> JoinT2 Ventures!
18:54 < Shingoshi> That's what I am talking about/
18:54 < Shingoshi> Making T2 a very strong and lively distribution.
18:55 < Shingoshi> LMJ: Have you set up that link on the site yet?
18:55 < LMJ> no Shingoshi
18:55 < Shingoshi> Either that, or rxr give me one on the main site.
18:56 < LMJ> the new website is just a test atm
18:56 < Shingoshi> Then I need to build the real thing, so we can see real results, now.
18:57 < Shingoshi> That is what I am dedicated to.
18:57 < Shingoshi> Build T2!
18:57 < Shingoshi> To get you that manpower you need.
18:58 < Shingoshi> We need.
19:03 < LMJ> yes ;)
19:03 < Shingoshi> So let me do my job!
19:03 < LMJ> i think you can write a new on the new website, i will publish it
19:04 < Shingoshi> This may seem like a small result, but I don't consider juri_ being here small or insignificant. And this is just the first. I can do a lot more.
19:05 < Shingoshi> So give me the space I need on the test site as soon as you can.
19:06 -!- sepp_ [n=sepp@p213.54.37.95.tisdip.tiscali.de] has joined #t2
19:06 < Shingoshi> I want it right between Developer and Contact Us. Header: JoinT2 Ventures
19:10 < Shingoshi> juri_: Devutils is simply the directory I need to direct the build to find the scripts there?
19:10 < Shingoshi> Do those scripts become a part of the pkg itself?
19:12 < Shingoshi> Or are they only used during the build?
19:14 < juri_> i think they're only used during the build.
19:14 < R4gnar0k> moin
19:14 * R4gnar0k yawns
19:14 < Shingoshi> So then I only need to export their path for the build?
19:15 < juri_> i'm doubting you even need to do that.
19:15 -!- sepp [n=sepp@p213.54.168.196.tisdip.tiscali.de] has quit [Read error: 60 (Operation timed out)]
19:15 < juri_> just call the scripts by their full path names, when you need them.
19:15 < Shingoshi> Gooday R4gnar0k
19:17 < rxr> moin R4gnar0k
19:17 < R4gnar0k> how goes?
19:17 * R4gnar0k is heading off to NZ for a week today
19:17 < Shingoshi> I don't know where or when they are called to do that. So I think it is better to simply specifiy their location once and for all.
19:20 * R4gnar0k wonder what I walked into
19:22 < rxr> NZ ?
19:23 < Shingoshi> Don't complain. Or I'll go there instead of you!
19:24 < R4gnar0k> new zealand
19:24 < Shingoshi> yes!!!
19:25 < Shingoshi> It has got to be one of the most beautiful places on earth.
19:25 < CIA-8> rene * r22798 /trunk/package/develop/libtasn1/libtasn1.desc: * updated libtasn1 (0.3.8 -> 0.3.9)
19:25 < rxr> R4gnar0k: lucky you
19:25 < rxr> R4gnar0k: have a good holiday
19:25 < rxr> it's holidy, isn't it ?
19:26 -!- d-marc [n=d-marc@HSI-KBW-091-089-003-097.hsi2.kabelbw.de] has joined #t2
19:27 < d-marc> hi
19:29 < rxr> hi d-marc
19:30 < R4gnar0k> rxr: I wish it was holiday :p
19:31 < rxr> oh
19:31 < rxr> what's up over there then ?
19:34 < R4gnar0k> part of the company I work for :p
19:42 < Shingoshi> I knew you didn't sound too enthusiastic.
19:42 < R4gnar0k> lol
19:42 < Shingoshi> Don't complain, My earlier remark is still true!
19:43 < Shingoshi> BEAUTIFUL!!!
19:57 < CIA-8> rene * r22799 /trunk/package/security/clamav/clamav.desc: * updated clamav (0.90 -> 0.90.1)
20:01 -!- d-marc [n=d-marc@HSI-KBW-091-089-003-097.hsi2.kabelbw.de] has quit ["KVIrc 3.2.4 Anomalies http://www.kvirc.net/"]
20:02 < rxr> ok - I leave, too
20:02 < rxr> time for the evening dinner and thinking about what's up with 2.6.20, an SD card and my embedded boards ... :-)
20:02 < rxr> cu all
20:02 [Users #t2]
20:02 [@ChanServ] [ juri_] [ R4gnar0k] [ Shingoshi] [ valentin]
20:02 [ Capey ] [ LMJ ] [ rxr ] [ sparc-kly]
20:02 [ CIA-8 ] [ mtr ] [ sepp_ ] [ Stelz ]
20:02 -!- Irssi: #t2: Total of 13 nicks [1 ops, 0 halfops, 0 voices, 12 normal]
20:12 < Stelz> cu rxr
20:13 < Shingoshi> bye rxr
20:37 -!- misl [n=chatzill@84-104-172-187.cable.quicknet.nl] has joined #t2
20:38 < misl> hi folks
21:43 -!- juri_ is now known as sailorjuri_
22:09 -!- sepp [n=sepp@p85.212.62.135.tisdip.tiscali.de] has joined #t2
22:17 -!- sepp_ [n=sepp@p213.54.37.95.tisdip.tiscali.de] has quit [Read error: 60 (Operation timed out)]
22:18 -!- sailorjuri_ is now known as juri_
22:32 -!- misl [n=chatzill@84-104-172-187.cable.quicknet.nl] has quit ["Chatzilla 0.9.75 [Firefox 1.5.0.10/2007021601]"]
22:55 -!- d-marc [n=d-marc@HSI-KBW-091-089-000-088.hsi2.kabelbw.de] has joined #t2
22:56 -!- d-marc [n=d-marc@HSI-KBW-091-089-000-088.hsi2.kabelbw.de] has left #t2 ["Time makes no sense"]
22:58 -!- idealm [n=ideal@CPE-203-45-99-98.nsw.bigpond.net.au] has joined #t2
23:44 < Shingoshi> rxr: Is the switch supposed to be numeric 0, or alpha O in the 00-minimal.i?
23:54 < Shingoshi> rxr: -oldconfig is not supported for new configs.
23:55 < R4gnar0k> hm?
23:56 < Shingoshi> And build is complaining about lua.
23:57 < Shingoshi> I tried generic. no luck.
23:57 < Shingoshi> What is lua, and do I need it.
23:57 < R4gnar0k> yes you do
23:57 < Shingoshi> What is it?
23:57 < R4gnar0k> www.lua.org
23:58 < Shingoshi> Ok, but do I then have to compile this beforehand, yes?
23:58 < R4gnar0k> afaik you do need to have the lua package installed in your host system, yes
23:59 < R4gnar0k> oh nvm. no you don't
--- Log closed Sat Mar 03 00:00:14 2007