--- Log opened Wed Dec 01 00:00:54 2004
00:17 -!- sparc-kly [~sparc-kly@64.237.130.173] has quit ["Leaving"]
00:40 -!- madtux [~mike@200.91.101.97] has quit ["leaving"]
02:52 -!- kensai [~kensai@64.237.129.108] has joined #t2
03:17 -!- kensai [~kensai@64.237.129.108] has quit ["Leaving"]
03:35 -!- sparc-kly [~mubex@64.237.130.173] has joined #t2
03:35 -!- sparc-kly [~mubex@64.237.130.173] has quit [Client Quit]
03:50 -!- sparc-kly [~mubex@64.237.130.173] has joined #t2
05:44 -!- _martin_ [~martin@brln-d9ba09f2.pool.mediaWays.net] has quit [Read error: 110 (Connection timed out)]
05:47 -!- _martin_ [~martin@brln-d9ba09ef.pool.mediaWays.net] has joined #t2
05:57 -!- Netsplit kornbluth.freenode.net <-> irc.freenode.net quits: jsaw, daja77, nullslack, _Ragnar_, CIA-9, mnemoc
05:58 -!- Netsplit over, joins: CIA-9, nullslack, mnemoc, jsaw, daja77, _Ragnar_
05:58 -!- Netsplit kornbluth.freenode.net <-> irc.freenode.net quits: CIA-9
05:59 -!- Netsplit over, joins: CIA-9
07:23 -!- rxr_ [~rene@p213.54.229.86.tisdip.tiscali.de] has joined #t2
07:23 -!- Topic for #t2: T2 | the system development environment | http://www.exactcode.de/t2 | C++ people around, too
07:23 -!- Topic set by rxr [] [Mon Nov 29 02:10:27 2004]
07:23 [Users #t2]
07:23 [ _martin_] [ CIA-9 ] [ jsaw ] [ nullslack] [ rxr ] [ sparc-kly]
07:23 [ _Ragnar_] [ daja77] [ mnemoc] [ praenti ] [ rxr_] [ valentin ]
07:23 -!- Irssi: #t2: Total of 12 nicks [0 ops, 0 halfops, 0 voices, 12 normal]
07:23 -!- Channel #t2 created Sun Aug 8 21:15:33 2004
07:23 -!- Irssi: Join to #t2 was synced in 11 secs
07:30 -!- nullslack [~nullslack@203.190.73.220] has quit [Read error: 110 (Connection timed out)]
07:32 -!- rxr [~rene@p213.54.247.80.tisdip.tiscali.de] has quit [Read error: 60 (Operation timed out)]
10:29 -!- mnemoc [~amery@200.75.27.12] has quit [Read error: 110 (Connection timed out)]
10:32 -!- mnemoc [~amery@200.75.27.4] has joined #t2
11:25 -!- You're now known as rxr
11:25 < rxr> re
11:47 < rxr> Python 2.4 Released
11:47 < rxr> Posted by Eugenia Loli-Queru on 2004-11-30 15:59:39 UTC
11:47 < rxr> The python final release of Python 2.4 was just released. Python 2.4 is the result of almost 18 month's worth of work on top of Python 2.3. New features are, but not limited to, function decorators, generator expressions, a number of new module and more.
12:04 < CIA-9> rene * r4902 /trunk/package/fonts/gpl-fonts/ (gpl-fonts.conf gpl-fonts.desc):
12:04 < CIA-9> * added two more fonts to the gpl-font package that I'm about rename
12:04 < CIA-9> in a second
12:06 < CIA-9> rene * r4903 /trunk/package/fonts/gpl-fonts/ (6 files): * gpl-fonts -> john-stracke-fonts rename part I
12:08 < CIA-9> rene * r4904 /trunk/package/fonts/ (gpl-fonts/ john-stracke-fonts/): * gpl-fonts -> john-stracke-fonts rename part II
12:09 < CIA-9> rene * r4905 /trunk/package/fonts/john-stracke-fonts/ (6 files):
12:09 < CIA-9> * gpl-font -> john-stracke-font rename part III (I managed to mistype
12:09 < CIA-9> a comma for a dot .... - don't ask ...)
12:09 < rxr> ^- too early for me ...
12:16 < mnemoc> at least they are together on keyboard :)
12:17 < CIA-9> rene * r4906 /trunk/package/fonts/john-stracke-fonts/ (john-stracke-fonts.conf john-stracke-fonts.desc):
12:17 < CIA-9> * fixed john-stracke-fonts to actually install the right files
12:17 < CIA-9> to injected the checksums
12:26 < CIA-9> rene * r4907 /trunk/package/fonts/john-stracke-fonts/john-stracke-fonts.conf: * fixed john-stracke-fonts to install the files owned by 0:0
13:26 < rxr> cool ug:
13:26 < rxr> bug even:
13:26 < rxr> https://bugs.freedesktop.org/show_bug.cgi?id=1903
13:29 < jsaw> re
13:29 < jsaw> hi rxr
13:29 < jsaw> hi mnemoc
13:32 < jsaw> rxr: ping
13:37 < rxr> pong
13:37 < rxr> moin jsaw
13:37 < rxr> hi mnemoc !
13:37 < jsaw> rxr, are you familiar with asm in C?
13:38 < rxr> ouh - barely
13:38 < jsaw> pasting a few lines now...
13:38 < rxr> I hate the syntax as used in GCC - especially the clobbers ...
13:38 < jsaw> int mmx_init(void)
13:38 < jsaw> {
13:38 < jsaw> int mmx_available = 0;
13:38 < jsaw> asm volatile (
13:38 < jsaw> /* Get CPU version information */
13:39 < jsaw> "pushl %%eax\n\t"
13:39 < jsaw> "pushl %%ebx\n\t"
13:39 < jsaw> "pushl %%ecx\n\t"
13:39 < jsaw> "pushl %%edx\n\t"
13:39 < jsaw> "movl $1, %%eax\n\t"
13:39 < jsaw> "cpuid\n\t"
13:39 < jsaw> "andl $0x800000, %%edx \n\t"
13:39 < jsaw> "movl %%edx, %0\n\t"
13:39 < jsaw> "popl %%edx\n\t"
13:39 < jsaw> "popl %%ecx\n\t"
13:39 < jsaw> "popl %%ebx\n\t"
13:39 < jsaw> "popl %%eax\n\t"
13:39 < jsaw> : "=m" (mmx_available)
13:39 < jsaw> : /* no input */
13:39 < jsaw> );
13:39 < jsaw> return mmx_available;
13:39 < jsaw> }
13:39 < jsaw> The original code ends with -> : "ebx", "ecx", "edx" <-
13:39 < jsaw> (after /* no input */)
13:40 < jsaw> But the fact, that all these registers are saved on the stack doesn't make this line necessary, or?
13:40 < rxr> hm
13:40 < rxr> why do you modify it at all?
13:40 < jsaw> gcc 3.4 complains about ebx being clobbered...
13:41 < jsaw> (package root)
13:42 < jsaw> rxr: I'll just add the patch, the result is identical, but gcc 3.4 compiles it...
13:43 < rxr> I do not think the clobbers are necessary ...
13:43 < jsaw> good.
13:44 < rxr> but the clobbers are such a fragile thing - I already read bizzare details about them on the gcc list - but they are so unintuitive that I always forget the details after some days ...
13:45 < daja77> s/%ebx/%edx/h should fix that ...
13:45 < rxr> there was s.th. about results of "C code" scheduled between the "asm code" due to missing clobbers ... - but if there are such details it will not matter here since the function has no other surrounding code anyway
13:45 < jsaw> daja77: look at the code, edx is already used!
13:45 < daja77> oh in that case ...
13:46 < rxr> yes - sasving ebx is right - it must not be clobbered and it is indeed not ...
13:46 < daja77> just remembered that fix for libsdl ..
13:46 < mnemoc> hi rxr, jsaw, daja77
13:46 < rxr> I think due to volative the code is not re-scheduled anyway - so no register clobbers should be ok - due to restoring them all
13:47 < rxr> damn - I can not type today ..
13:49 < rxr> jsaw: news about stlport and lates binutils?
13:50 < jsaw> rxr: builds!
13:50 < rxr> cool!
13:50 < rxr> do you have multimedia stuff installed and could check if ardour compiles without the gcc34.patch then?
13:50 < jsaw> I think the new binutils changed from error to warning only.
13:50 < rxr> good
13:51 < jsaw> because the log contains the .rodata <-> .gnu.linkonce.t things still
13:51 < jsaw> also ooo progresses further, but at some point it breaks again.
13:51 < rxr> :-(
13:52 < jsaw> yeah, it's not gcc 3.4 ready
13:52 < jsaw> the ximian guys, who's build system I use, still use gcc 3.2, so ....
13:52 < rxr> the major dists are at gcc-3.4 IIRC, suse and fedora and such ...
13:52 < rxr> maybe they have patches ?
13:53 < jsaw> oh, btw, how do I inject "-fpermissive" for gxx for the command wrapper?
13:53 < jsaw> their patches are already gathered in the ximian build system.
13:54 < rxr> CXX_WRAPPER_INSERT and so ...
13:54 < jsaw> a damn, I used GXX_WRAPPER_INSERT, that's why...
13:54 < rxr> yeah ...
13:58 < rxr> xemacs utf8 is damn stupid - i just semi ruined my file:
13:58 < rxr> - 2002-01-17: Ren Rebe
13:58 < rxr> + 2002-01-17: Renebe
13:58 < rxr> - tons of ...
13:58 < jsaw> oh oh...
13:59 < rxr> damn - should have recoded it before opening it .....
14:03 * rxr thinks about using utf8 exlusively now ...
14:03 < rxr> any user experience here?
14:03 -!- nzg [~tschmidt@s15173431.rootmaster.info] has joined #t2
14:12 < sparc-kly> moin all
14:12 < rxr> moin sparc-kly
14:23 < rxr> jsaw: yep - ardour now builds without gcc34 patch^Whack
14:26 < jsaw> your machine is definitely faster then mine...
14:27 < rxr> did you compile ardour, too?
14:27 < rxr> model name : AMD Athlon(TM) XP 2500+
14:27 < CIA-9> rene * r4908 /trunk/package/audio/ardour/gcc34.patch: * the binutils update obsoleted the ardour/gcc34.patch^Whack
14:28 < jsaw> == 12/01/04 14:29:00 =[5]=> Finished building package ardour.
14:28 < jsaw> model name : Intel(R) Pentium(R) 4 CPU 2.26GHz
14:33 < rxr> == 12/01/04 14:34:11 =[9]=> Finished building package stlport.
14:33 < rxr> took 5 minutes ... ;-)
14:36 < jsaw> *grummel*
14:36 < rxr> I know why I invested into a AMD cpu - a year ago or so ...
14:42 -!- kensai [~xlinux@ool-18be3a49.dyn.optonline.net] has joined #t2
14:44 -!- kensai [~xlinux@ool-18be3a49.dyn.optonline.net] has quit ["[BX] Bob Barker uses BitchX. Have your BitchX spayed or neutered."]
14:47 -!- praenti [~praenti@mail.obster.org] has quit [Read error: 104 (Connection reset by peer)]
14:47 -!- praenti [~praenti@mail.obster.org] has joined #t2
15:51 -!- madtux [~mike@200.91.101.97] has joined #t2
15:51 < madtux> hello.
15:52 < mnemoc> hullo madmax
16:08 -!- nullslack [~nullslack@203.190.73.220] has joined #t2
16:09 < rxr> guten morgen madtux !
16:09 < rxr> hi nullslack
16:09 < mnemoc> rxr: can rock people legally fork your handbook?
16:09 < rxr> yes
16:09 < nullslack> rxr, greetings rxr!!!
16:09 < rxr> but they can not sell printed editions without asking me ...
16:10 < mnemoc> rxr: only restricted to selling?
16:10 < rxr> mnemoc: yes
16:10 < rxr> do they have new discussions going on?
16:11 < mnemoc> blindy has created a wiki
16:11 < mnemoc> http://scavenger.homeip.net/rockdoc/
16:11 < rxr> yep - but it is ot based on my handbook as far as I can see ...
16:12 < mnemoc> the reason argued to do it was the restrictions over the handbook
16:12 < rxr> I read it - but I did not wanted to send mail to the list ...
16:13 < daja77> erh only one of the reasons ...
16:13 < rxr> and if they can not read the open documentation license I used it is their problem if they want to start from scratch with no documentation at all
16:13 < mnemoc> daja77: the handbook can be improved to solve the other reasons
16:13 < madtux> rxr: why not GPL it?
16:14 < madtux> rxr: btw guten morgen mein freund, Wie geht es dir?
16:14 < rxr> because this is exactly what I do not want: other people getting rich selling my handbook ...
16:14 < daja77> gpl is no good for bools
16:14 < daja77> books
16:15 < madtux> ok cc then
16:15 < rxr> well people that can not write well formed sentences themselfs arguing the handbook is not well writen or so is just stupid ...
16:17 < jsaw> <- getting sth. to fill stomach, brb
16:17 < rxr> cu jsaw
16:17 < rxr> madtux: cc what ?
16:17 < mnemoc> i think he means "use creative commons"
16:18 < rxr> is selling printed editions restricted in creative commons ?
16:19 < daja77> you can do that
16:19 < daja77> but you don't have to
16:19 < madtux> rxr: check it out, it might the solution for you
16:19 < madtux> :)
16:19 < rxr> this is exactly why I choose - open publication license with option B .. - so what is the difference ... ?
16:19 < daja77> it is quite easy and clear
16:19 < madtux> http://creativecommons.org/
16:19 < rxr> well - I have a solution since the beginning ...
16:20 < madtux> ok.
16:21 < rxr> Open Publication License with Option B is exactly what I want and needed
16:21 < rxr> without any of the options it is even OSI approved ...
16:21 < rxr> I just restrict commercial publications with option B ...
16:21 < daja77> well the discussion is not that you should change the license
16:22 < rxr> afaihs it was also that the license is not free enought and they are not allowed to continue on it ..
16:27 < daja77> as i said, it is not only the license
16:28 < rxr> yes I know - the content is so bad ...
16:28 < daja77> not bad
16:28 < daja77> but addressing a different audience
16:28 < rxr> and what audience is the handbook adressing?
16:29 < daja77> linux newbies
16:29 < rxr> pah - nonsensec ...
16:29 < rxr> nonsense even
16:29 < madtux> not necesarily linux newbies
16:29 < rxr> just that it also covers the basics does not mean it is for newbies only
16:29 < madtux> but newbies in the matters of build kits
16:29 < madtux> but as rxr should not be exclusively for newbies
16:30 < daja77> .oO (why i even try to talk about)
16:30 < rxr> it intended to cover all - as a complete handbook - so when some qnx or windows expert get does use Unix / Linux first I expect to have the basics in the handbook ...
16:30 < madtux> i would say it should be a very complete document that be either a step by step guide for new users.. or a quite decent reference guide for developers
16:30 < madtux> or skilled / power users
16:30 < rxr> the only newbie chapters I see are permissions and such ...
16:31 < rxr> even devfsd is very interesting for linux experts from suse or so never seen it before ...
16:31 * rxr at work again - this does not yield anything ...
16:31 < daja77> of course not
16:31 < madtux> :)
16:32 < rxr> no idea what "of course" should intend ...
16:32 < rxr> btw if you have still not noticed it: ROCK Linux is missing users because even Linux exports fail to use it in a way to be productive ... - so better do not argue that the handbook does cover too many basics ...
16:39 < daja77> nice it grew a lot since my last visit
16:39 < rxr> ?
16:41 < daja77> the handbook
16:41 < rxr> which one - my or the wiki
16:42 < daja77> yours
16:42 < rxr> nice to hear
16:42 < daja77> the wiki just started yesterday ;)
16:43 < rxr> when did you take the last look to my handbook?
16:43 < daja77> well i guess the differences between rock and t2 would not be covered in it
16:43 < daja77> a few months ago
16:44 < rxr> currently I started to document them - but only to 2.0 - 2.1 contains far too much junk - if I'm allowed to say this here ...
16:45 < daja77> you are free to say whatever you want here, just don't expect me to share that opinion
16:46 < rxr> maybe you could tell what you like in 2.1 ...
16:48 < daja77> i like the generic packages and split packages e.g.
16:50 < rxr> cool - the AV220 does now work - basically - with some hacks in the source ...
16:50 < daja77> the what?
16:50 < rxr> a scanner ...
16:50 < daja77> :)
17:05 < madtux> shame on u daja77
17:05 < daja77> ?
17:05 < madtux> just teasing u
17:05 < daja77> :p
17:14 < rxr> hey - this channel stays friendly!
17:20 < madtux> rxr: Good, otherwise i wouldn't iddle here
17:21 < madtux> ;0)
17:43 -!- CIA-9 [~CIA@to.je.spocco.com] has quit [Read error: 113 (No route to host)]
18:07 < nullslack> is t2 stable and secure to be deployed as a production system?
18:07 < nullslack> considering that it uses bleeding edge packages
18:09 < madtux> stable yes, "default security" is never enough, you are supposed to take of the security for your systems according to your own needs
18:09 < madtux> - my very personal opinion -
18:14 < nullslack> ...i asked this because almost all security writers advice to stay away from development versions of packages if you are deploying it on production sytems
18:17 < madtux> i used rocklinux for years on my servers at an isp that i used to work for... not a problem in 4 years
18:17 < madtux> now i will move them to t2
18:20 < nullslack> whoaa...i'm convince ;) but t2 is diff'rent right? it uses bleeding edge packages, much updated than the rock packages right?
18:21 < rxr> nope
18:22 < rxr> the rock people also "try" to be up-to-date ...
18:22 < madtux> i think rxr is better for this answer
18:22 < madtux> nullslack: the 2 update freaks rock had are no longer there
18:23 < rxr> 2 update freaks ?
18:23 < madtux> rxr and i used to make LOTS of package updates
18:23 < madtux> rxr: no offense by the "freaks" expression i hope
18:23 < nullslack> ic...so ur the 2 update freaks! lol
18:23 < rxr> nope
18:24 < rxr> everyone wants the packages in-use to be up-to-date
18:24 < rxr> in fact many updates include vital security fixes, too
18:26 < nullslack> i wish there's a more minimal template with needed packages only for booting and then start building on that base
18:26 < rxr> you are free to strip it down further ...
18:28 < nullslack> yeah...but it's taking time to choose what packages to exclude...and some of the packages are new to me ;(
18:31 < nullslack> i have tried doing it with slackware...i just installed from the "a" base packages. trial and error...then just recently i got it to work with a total of 29 packages and 92 MB of diskspace ;)
18:44 < nullslack> hmmm...is loopback support really needed for building t2?
18:44 < rxr> for image creation ...
18:45 < nullslack> for building the iso?
18:45 < nullslack> only?
18:46 < rxr> yes
18:50 < rxr> for stuff like creating the initrd and such - mostly at the end of the bootdisk target ...
18:52 < nullslack> ic...how can i customize the kernel...i mean deselecting modules to be compiled
18:59 < rxr> mom
19:01 < nullslack> ?
19:12 < rxr> phoning
19:13 < nullslack> oh ;)
19:13 < rxr> so
19:13 < rxr> in the expert options you can alter the kernel config style ..
19:14 < rxr> defaul is to build a resonable configured kernel - and all possible modules
19:14 < rxr> you can change to not build the modules ... or to specify singles options or inject a whole own config there ...
19:14 < rxr> just take a look
19:14 * rxr shortly away ...
19:16 < nullslack> thnx
19:57 < madtux> rxr: interesting:
19:57 < madtux> grep: package/fonts/gpl-fonts/gpl-fonts.desc: No such file or directory
19:58 < madtux> one of the errors i got as i've been downloading my sources
20:10 < madtux> ok nevermind the error went away
20:27 < madtux> ti who ever cares:
20:27 < madtux> == 13:31:10 =[0]=> Building base/linux-header [2.6.8.1 2.1.0-beta].
20:27 < madtux> my t2 build just began
20:27 < mnemoc> :D
20:29 < nullslack> what's linux24 for?
20:30 < mnemoc> what's a kernel for?
20:30 < mnemoc> o what's that package for?
20:30 < nullslack> i mean it builds for 2.6 right?
20:30 < nullslack> and the 2 are downloaded by default
20:31 < madtux> unless u ask it not to :)
20:32 < nullslack> so..why 2 by default? instead of just choosing one
20:32 < mnemoc> nullslack: why no?
20:32 < madtux> i'm not the one to decide this.. if it was on my hands it would just be 2.6
20:33 < madtux> though many still like 2.4
20:33 * madtux looks at mnemoc as he says that
20:33 < mnemoc> between 2.6.7 and 2.6.8 360 files were deleted and 580 created
20:33 < mnemoc> is that a sign of stability?
20:34 < mnemoc> i created a repo for linux26 to try to migrate PAX patch with a help of gnuarch's star-merge
20:35 < mnemoc> but most of the patches files no longer exist
20:35 < mnemoc> so my try of porting the patch failed
20:46 < nullslack> !> make: Cross_CC_not_built_so_far_cc: Command not found
20:46 < nullslack> !> make: *** [gzip.o] Error 127
20:46 < nullslack> == 12/02/04 03:52:08 =[1]=> Aborted building package gzip.
20:46 < nullslack> ;(
20:47 < mnemoc> nullslack: what failed before?
20:48 < nullslack> mnemoc, what do u mean?
20:48 < mnemoc> before that package, something else failed?
20:49 < nullslack> nope...but before that it's the linux-header build
20:51 < nullslack> i don't know if this might help --> !> checking if `#!' works in shell scripts
20:51 < mnemoc> Cross_CC_not_built_so_far_cc <--- that's clear enought
20:52 < nullslack> what does that mean?
20:53 < nullslack> oh well...i'll try to check out t2 again and start fresh
20:53 < mnemoc> i guess you configured your Build wrong
20:54 < mnemoc> don't checkout again, just update
20:56 < nullslack> update?
20:56 < nullslack> svn update?
20:56 < mnemoc> yep
20:56 < nullslack> ok...thnx
20:57 < mnemoc> remove that broken config and try Config again
20:57 < mnemoc> if you don't really know what an option does, don't change it
20:57 < mnemoc> and Build-Target again
20:58 < madtux> and most important if you start to get frustrated you kick mnemoc to release the anger
20:58 < madtux> :)
20:58 < mnemoc> thank you
20:58 < madtux> you are welcome :)
20:58 < madtux> Create symlink usr/spool/locks (../../var/lock) ...
20:58 < madtux> ln: creating symbolic link `/home/mike/Projects/t2/t2-trunk/build/system-2.1.0-b
20:58 < madtux> eta-x86-pentium-mmx-32-desktop-expert/usr/spool/locks' to `../../var/lock': No s
20:58 < madtux> uch file or directory
20:59 < madtux> ha!
20:59 < madtux> la tengo
20:59 < madtux> mm... no, no la tengo
21:00 < mnemoc> existe el ../../var '
21:00 < mnemoc> ?
21:00 < madtux> sipis
21:00 < madtux> pero algo sumamente interesante
21:00 < madtux> si te vas a build/$config/
21:01 < madtux> haces un ls
21:01 < madtux> usr, bin, lib etc.. som symlinks de build/$config/ROCK/tools.cross/$dir
21:02 < madtux> PERO var esta estatico en build/$config/
21:02 < madtux> ha!..
21:02 < madtux> y en build/$config/ROCK/tools.cross/var/
21:02 < madtux> NO existe lock
21:02 < madtux> me pregunto pq..
21:02 < mnemoc> :\
21:03 < madtux> y lo ma sinteresante:
21:03 < mnemoc> habilita el XTRACE
21:03 < madtux> Create symlink usr/spool (../var/spool) ...
21:03 < madtux> Create symlink usr/spool/locks (../../var/lock) ...
21:03 < madtux> ln: creating symbolic link `/home/mike/Projects/t2/t2-trunk/build/system-2.1.0-b
21:03 < madtux> eta-x86-pentium-mmx-32-desktop-expert/usr/spool/locks' to `../../var/lock': No s
21:03 < madtux> uch file or directory
21:03 < mnemoc> madtux: we are at #t2
21:03 < madtux> vez que justo antes del error.. acaba de hacer un link al mismo directorio..
21:03 < madtux> urrrgs..
21:03 < madtux> sorry folks..
21:04 < nullslack> thnx again...btw, is it ok if the "Abort when a package-build fails" is enabled?
21:04 < mnemoc> yes
21:04 < nullslack> ok
21:04 < madtux> mnemoc: anyways... if you notice is just weird to notice that one line before in the log it gave no error
21:05 < madtux> mnemoc: you definitly want to enable that
21:06 < madtux> lets see what xtrace says
21:06 < mnemoc> abort when fails; retry broken; and XTRACE are mandatory to me :)
21:07 < madtux> yeah damn i'm loving this..
21:07 < madtux> :)
21:08 < madtux> i missed action so badly
21:08 < mnemoc> hehehe
21:09 < madtux>
21:09 < madtux> Create symlink usr/spool/locks (../../var/lock) ...
21:09 < madtux> ===[main_dt:39 (last $?=0)> ln -fsn ../../var/lock /home/mike/Projects/t2/t2-tru
21:09 < madtux> nk/build/system-2.1.0-beta-x86-pentium-mmx-32-desktop-expert/usr/spool/locks
21:09 < madtux> ln: creating symbolic link `/home/mike/Projects/t2/t2-trunk/build/system-2.1.0-b
21:09 < madtux> eta-x86-pentium-mmx-32-desktop-expert/usr/spool/locks' to `../../var/lock': No s
21:09 < madtux> uch file or directory
21:09 < madtux>
21:10 < nullslack> can i safely do rm -rf in t2-trunk/config/cfgdir
21:10 < madtux> yeah
21:10 < nullslack> thnx
21:10 < madtux> nullslack: NEVER rm -rf build/ or so
21:10 < madtux> in that case use scripts/Cleanup
21:10 < madtux> :)
21:11 < nullslack> copy! ;0
21:11 < nullslack> ;)
21:11 < madtux> :P
21:12 < nullslack> Minimalistic package selection + XFree86 ...hmmm not xorg?
21:12 < mnemoc> don't use that template
21:13 < nullslack> Minimalistic package selection <-- how bout this one?
21:13 < madtux> mnemoc: nullslack i initially created it for rock linux but it needs to be cleanup
21:13 < mnemoc> yes
21:14 < mnemoc> madtux: rene updated it
21:14 < madtux> oh great
21:14 < madtux> :)
21:16 < nullslack> ./scripts/Download -required will download the ones with "X" in packages?
21:16 < madtux> mnemoc: i believe my problem could be due to an extra ../
21:17 < mnemoc> it looks fine to me
21:17 < mnemoc> debug.sh :p
21:17 < madtux> :P
21:21 < mnemoc> madtux: does usr/spool/ exist?
21:22 < nullslack> how much diskspace do i need to build "Minimalistic package selection"?
21:22 < mnemoc> you are fine with 1.5G
21:25 < madtux> mnemoc: yes
22:06 < nullslack> what if i have built an iso already using the minimalistic template, but i want to add xorg...is it just easy as building xorg then make a new iso?
22:06 < mnemoc> yes
22:07 < nullslack> and all the packages that depends on X?
22:07 < mnemoc> using pkgsel you enable the other packages and run Build-Target again
22:07 < nullslack> oh...so i'll have to run ./scripts/Config again?
22:09 < mnemoc> ./scripts/Config -oldconfig will not show you the UI
22:10 < mnemoc> you can write directly to config/$foo/pkgsel file
22:11 < nullslack> ic...like "X xorg", right?
22:12 < mnemoc> yep
22:12 < mnemoc> but a minimal xorg includes more than that
22:13 < nullslack> whoaa..."run Build-Target" again...will it recompile all packages again?
22:13 < mnemoc> nope
22:13 < mnemoc> built pacakges are not rebuilt
22:13 < mnemoc> http://svn.exactcode.de/t2/trunk/target/mnemosyne/pkgsel/Console/X.ask
22:13 < mnemoc> this is the very minimal to build xorg
22:15 < nullslack> it will not compile if one of those "dependencies"? is not installed?
22:15 < mnemoc> yep
22:15 < rxr> re
22:16 < mnemoc> moin rxr
22:16 < rxr> moin mnemoc
22:16 < nullslack> what's mnemosyne btw?
22:16 < mnemoc> my target, incompletely ported to t2
22:17 < nullslack> oh...i haven't noticed ;)
22:17 < rxr> it seems I need to update the minmal+xfree a bit more ;-)
22:17 < nullslack> rxr, make that xorg ;)
22:18 < nullslack> alright! i've finished dowloading all files from minimalistic template excluding linux24 only
22:19 < rxr> ;-)
22:19 < rxr> linux24 and linux26 exist for choice ...
22:19 < rxr> just to set a period under the discussion ;-)
22:20 < nullslack> i will not broke anything right if i "mv" t2 to another partition?
22:21 < rxr> nullslack: what do you exactly plan to do?
22:21 < nullslack> rxr, but it is both downloaded if you use minimalistic template...choice is loss ;)
22:21 < nullslack> rxr, i have only 400 MB left and i want to move it to a 3GB partition
22:23 < rxr> it is preselection - you can still tune it ;-)
22:23 < rxr> when you want to use the minimal ISO on two boxes - ones does not boot 2.6 it is a big win ,-)
22:23 < nullslack> yes...with some help and guidance from u guys ;)
22:23 < madtux> rxr: talking about isos.. do u have any news for me? :)
22:23 < rxr> package selection in T2 3.0 will get easier
22:24 < rxr> with automated dependency stuff - and optional grphical graph visualization ;-)
22:24 < rxr> .oO(ISOs)
22:24 < rxr> there was s.th. ...
22:24 < nullslack> rxr, and the timeframe? ;)
22:24 < madtux> rxr: :)
22:24 < rxr> ouhm - 3.0 is next year - at some time ...
22:24 < rxr> first we need to get out 2.1 this month
22:24 < madtux> i like your realistic timelines :)
22:25 < mnemoc> =)
22:25 < nullslack> yeah...christmas present!
22:25 < rxr> to be clean 3.0 is to be plan for + 1 year from now ... - so end 2005 ...
22:25 < rxr> first 2.1 now - and 2.2 or so on the way as we see demand
22:26 < rxr> including the usual maintenance releases on the way ...
22:26 < rxr> like 2.1.1 and so ...
22:33 < nullslack> == 05:43:28 =[0]=> Building base/linux-header [2.6.8.1 2.1.0-beta].
22:33 < nullslack> ;)
22:33 < madtux> :)
22:33 < madtux> ph34r
22:34 < nullslack> oh...the build will continue even if i didn't load loop, right?
22:34 < nullslack> madtux, lol
22:37 < nullslack> modprobe: Can't locate module loop
22:37 < nullslack> ;(
23:31 < nullslack> == 12/02/04 06:27:10 =[1]=> Aborted building package 00-dirtree.
23:31 < nullslack> madtux, same error as yours ;(
23:32 < madtux> nullslack: mm... quite interesting
23:32 < madtux> nullslack: what's the build host's distro and version?
23:32 < madtux> nullslack: if this is not a build host related error i will fix it tonight from home as i will launch 6 different builds tonight on my little lab
23:33 < madtux> and do some bug hunting
23:33 < madtux> :)
23:36 < nullslack> slackware 10.0
23:37 < madtux> i should have realized that out of ur nick :)
23:37 < nullslack> lol
23:39 -!- madtux [~mike@200.91.101.97] has quit ["leaving"]
--- Log closed Thu Dec 02 00:00:55 2004