WebHosting Paid by #1Payday.Loans


   The ROCK Linux project has been discontinued in 2010. Here are the old data for the historical record!

--- Log opened Tue Feb 17 00:00:37 2004
00:19 -!- holyolli [~holyolli@port-212-202-30-65.reverse.qsc.de] has quit ("Leaving")
00:31 -!- A-Tui [~aitor@cable74a018.usuarios.retecal.es] has joined #rocklinux
01:04 < daja77> https://www.kuro5hin.org/story/2004/2/15/71552/7795
01:11 < A-Tui> hola daja77, do you use sylpheed?
01:12 -!- jchoisy [~jchoisy@ALamentin-102-1-1-75.w81-248.abo.wanadoo.fr] has joined #rocklinux
01:20 -!- jchoisy [~jchoisy@ALamentin-102-1-1-75.w81-248.abo.wanadoo.fr] has quit ("leaving")
01:20 < daja77> yes
01:22 < A-Tui> and runs ok the gpgme plugin?
01:23 < daja77> no
01:24 < A-Tui> sylpheed shows you a message telling that gnupg it's not correctly installed?
01:25 < daja77> yes
01:26 < mnemoc> .oO( daja77 is quite verbose today )
01:26 < A-Tui> :)
01:26 * daja77 is on the way to bed :D
01:26 < daja77> n8 you all
01:27 < mnemoc> sleep well daja77 
01:27 < daja77> thx
01:27 < A-Tui> buenas noches da
01:27 < A-Tui> buenas noches daja77
01:35 -!- jsaw_ [~jsaw@p3EE1E20C.dip.t-dialin.net] has joined #rocklinux
01:52 -!- jsaw [~jsaw@pD9506B4D.dip.t-dialin.net] has quit (Read error: 110 (Connection timed out))
02:17 -!- Nebukadneza` [~daddel9@dsl-213-023-058-158.arcor-ip.net] has joined #rocklinux
02:28 -!- capchaos [~capchaos@p213.54.68.209.tisdip.tiscali.de] has quit ("There is no spoon.")
02:36 -!- Nebukadneza [~daddel9@dsl-082-082-077-241.arcor-ip.net] has quit (No route to host)
02:39 -!- A-Tui [~aitor@cable74a018.usuarios.retecal.es] has quit ("Satanás, el infierno es demasiado dulce!")
03:30 -!- sten [~sten@24.64.187.183] has joined #rocklinux
03:30 < sten> where can I get a rescue image?  (tarball or iso)
03:32 < sten> or should I try to build a minimal, vanilla-ROCK target?  (I've been unsuccessfully trying to build a "minimal packages/advanced template" with a dROCK target)
03:33 < mnemoc> minimal and minimal+xfree86 are for generic, not for drock
03:33 < mnemoc> you can use it but nobody has tested it :)
03:33 < sten> ;-)
03:34 < mnemoc> bootdisk is designed to be rescue disk too
03:34 < sten> really!
03:34 < mnemoc> yep
03:34 < sten> (the old-style rescue-1.5.tar.bz2, untar to partition, run lilo, build from there)
03:34 < sten> ?
03:35 < mnemoc> r.i.p.
03:35 < mnemoc> bootdisk, load 2nd stage, option 7 exec kiss, do what ever you want
03:36 < sten> I gathered that much.  Does the bootdisk target have compiler, libraries, etc?
03:39 < mnemoc> nope
03:40 < mnemoc> well, it has on build time, but that's not put on the images
03:41 < mnemoc> if you set any target to 'cross compile' you will get only that, boot+compiler. just before stage 2.
03:42 < sten> oh...  Most people install from an iso, or build from a running ROCK system these days eh?  (I'm a few years out of date)
03:42 < mnemoc> yep
03:43 < mnemoc> sten: for elders minimal/generic is there :)
03:45 < sten> mnemoc: I'm going to try a minimal/generic build tonight then.  Out of curiousity, are generic, and dROCK's package configurations still different?  (a minor example:  the bash_profile of dROCK was more colourfull in the past)
03:45 < mnemoc> dROCK got merged inside ock as 'desktop' target
03:45 < sten> I read that the tree's were merged, but thought that dROCK might have retained custom after-build configuration
03:45 < mnemoc> with some building/installing differences with the generic
03:46 < sten> what kind of differences?  (the end result is the same then, yeah?)
03:47 < mnemoc> the end result of desktop is dROCK :)
03:47 < mnemoc> the end result of generic is.... nothing coherent :\
03:48 < sten> :-)  I plan on building my system package-by-package from a minimal/generic target.  I could still, theoretically, manually add to my system until I have a dROCK installation, yes?
03:48 < mnemoc> almost
03:49 < mnemoc> target/desktop also has some extra patches, different PS1, etc...
03:50 < sten> ah.  That's what I was wondering.
03:50 < mnemoc> take a look to target/desktop directory
03:51 < sten> ah, here's the /etc/profile patch I was thinking of
03:52 < sten> what is this for:
03:52 < sten> # special adaptions for the desktop target
03:52 < sten> [ -e $confdir/$pkg.conf ] && . $confdir/$pkg.conf
03:52 < sten> postinstall="cat <<- EOT >> $root/etc/syslog.conf
03:52 < sten> #
03:52 < sten> # output warnings to vc/10 - dRock
03:52 < sten> #
03:52 < sten> *.warning                               /dev/vc/10
03:52 < sten> EOT"
03:52 < sten> (sorry for the flood)
03:52 < mnemoc> np
03:53 < mnemoc> set syslogd to output warnings to tty10
03:53 < sten> as well as logging them in the usual location?
03:55 < sten> heh, I just realized why the file confused me:  I've never seen comments inside of "quotes" before.  (what is the term for "ing"?)
03:55 < sten> hmm, I could manually apply these patches...
03:58 < sten> mnemoc: config.in does what exactly?  Is this the config file which specifies which packages/repositories are built during ./scripts/Build-Target, or is it something deeper?
03:59 < esdentem> hi ho
04:00 < sten> hi ho,
04:01 < esdentem> sten: config.in located where?
04:01 < esdentem> in scripts?
04:02 < sten> rock-src/target/desktop
04:02 < sten> (I'd like to start with a minimal/generic, with the option of rolling it into dROCK down the road)
04:02 < sten> (but minimalistic)
04:03 < esdentem> this file is being processed when you run scripts/Configure ... and contains configuration directives specific for the desktop target
04:04 < esdentem> sten: the best solution if you ask me is to build generic target with minimal+xfree86 template 
04:04 < esdentem> install and add packages you want to have with scripts/Emerge-Pkg
04:04 < sten> that's the plan ;-)
04:04 < esdentem> then do it ;)
04:06 < sten> I'm working on it, as we speak.  I was just wanted to verify that I could mold my minimal/generic target into a full-featured dROCK system later on, if I so choose
04:10 < mnemoc> re
04:10 < esdentem> with dROCK you mean the desktop target ... and if I am not mistaken it is only a different package selection ... then generic ... and some settings are different in the config
04:10 < esdentem> let me see ...
04:10 < sten> yeah, a sysklogd patch, and an /etc/profile patch
04:10 < mnemoc> package selection, .waring -> vc/10 and PS1
04:10 < sten> (I hope that's all)
04:10 < sten> PS1?
04:10 < mnemoc> profile patch :)
04:11 < mnemoc> colors of the 'standard' prompt
04:11 < sten> oh, I have a variable called $PS1!
04:11 < sten> so that's where you customize it!
04:11 < mnemoc> yeah
04:12 < mnemoc> and kernel config
04:12 < mnemoc> 4 differences only
04:12 < sten> which I don't need...  (I'm picky about my kernel config)
04:12 < esdentem> sten: yes it is only the package selection + different kernel.conf different /etc/profile file the vc/10 messaging and that is it
04:13 < sten> it'll be easy enough to patch when I'm up and running then ;-)
04:13 < esdentem> and that are changes that I would not call very needy ... and you can add that changes after you installed generic+minimal+xfree86
04:13 < sten> what is the status of building with linux26 support?
04:14 < sten> (as standard kernel)  Do I even need to build a kernel as part of the target?
04:14 < esdentem> I tryed to build with linux26 .. but I got errors ... but the problem can be that I am not building on rocklinux but on fedora
04:14 < esdentem> I am not sure
04:14 < sten> ok, I'll upgrade to linux26 later
04:15 < esdentem> sten: use linux24 for now ... you can switch to 26 later ... all userland tools are capable of linux26
04:15 < mnemoc> fake has been fixing linux26 support
04:15 < esdentem> as far as I know
04:15 < sten> hmm, maybe it'll make it into rc5
04:16 < esdentem> who knows perhups ... 
04:17 < mnemoc> sten try to start from HEAD instead of an old rc
04:17 < sten> how is trunk different from HEAD?
04:17 < esdentem> mnemoc is right ;)
04:18 < mnemoc> trunk==HEAD :)
04:18 < sten> thanks
04:19 < esdentem> de nada ;)
04:25 < sten> a great way to occupy time while waiting for a subversion sync, is to fold paper cranes out of chocolate wrappers... very tricky
04:26 < mnemoc> o_O
04:26 < esdentem> rofl
04:27 * esdentem needs to renew his origami knowledge ;)
04:27 < sten> ;-)
04:27 -!- kandinski [~kandinski@80-28-219-118.adsl.nuria.telefonica-data.net] has joined #rocklinux
04:32 < sten> will this remove gcc2 from my build, if I put in the "Edit package selection rules":  pkgfilter sed '/ gcc2 / { s/^X /O /p; d; };'
04:33 < esdentem> you only have to write -gcc2 there
04:33 < sten> esdentem:  oh, cool.   thanks.
04:33 -!- blindcoder [~blindcode@p50801776.dip.t-dialin.net] has quit (Read error: 60 (Operation timed out))
04:36 -!- blindcoder [~blindcode@pD9E4FD73.dip.t-dialin.net] has joined #rocklinux
04:36 < sten> eh, Target=generic/minimal wants to build headers and kernels for both linux 2.4 & 2.6
04:37 < esdentem> let it do it ...
04:37 < mnemoc> sten: both kernels are part of the template
04:37 < esdentem> but ... in scripts/Config in the experts section disable paranoia checks
04:37 < esdentem> otherwise one of that packages will yeld an error
04:38 < esdentem> because of overlapping files ... if I am not mistaken
04:38 < mnemoc> esdentem: not needed (at least here)
04:38 < sten> mnemoc: doesn't linux26 have build issues though?
04:38 < esdentem> ahh ok
04:38 < esdentem> sten: that are only headers not the kernel itself
04:39 < mnemoc> sten: don't worry :) but if you *want* to skip lx26 compeltely add - linux26 to your pkgsel
04:39 < sten> esdentem: ah, headers & src only.  Are packages built against the linux26 headers or linux24?
04:41 < sten> esdentem: if both are installed
04:41 < mnemoc> sten: on Config you choose a 'default'
04:41 < mnemoc> sten: everything is build against that 'default'
04:41 < mnemoc> pkgsel: Config -> Expert -> Package Selection -> '- linux26*'    <-- remove linux26 completely
04:41 < sten> mnemoc: it is probably safest to build against linux24 for now.  When I upgrade to linux26, I just need to rebuild dhcpcd & glibc; right?
04:43 < mnemoc> and module-init-tools
04:43 < sten> I learned about module-init-tools the hard way already ;-)
04:44 < mnemoc> =)
04:45 < sten> do I need to let Build-Target build me a kernel, or can I remove linux24?  (it takes FOREVER to build!)
04:46 < mnemoc> i have a patch for that waiting since dicember :(
04:47 < mnemoc> you must have one binary kernel in your build list
04:47 < sten> ok
04:48 < mnemoc> if not, current config will remove kernel headers and kernel sources from it, silently
04:48 < esdentem> ok .. I go to bed .. have fun and succsess sten ;)
04:48 < esdentem> good night
04:48 < sten> esdentem: good night
04:48 < mnemoc> good night esdentem 
04:54 < sten> mnemoc: for some reason gnome & tons of X software appears in my "current package list," although I have selected template minimal.  What is going on?
04:58 < mnemoc> hm?
04:59 < mnemoc> how many packages does Config title said you have enabled?
04:59 < sten> mnemoc: is the "current package list" updated to reflect chosen template?
04:59 < mnemoc> yes
05:00 < sten> 197 packages
05:00 < mnemoc> that's ok
05:00 < sten> there's even stuff like enlightenment 0.17 cvs in my "current packages list"
05:01 < sten> doesn't that seem odd?
05:01 < mnemoc> but it's not prefixed with X
05:01 -!- januar [~januar@dsl-203-113-218-21.vic.netspace.net.au] has joined #rocklinux
05:01 < mnemoc> they are 'O'
05:01 < sten> ohhhh
05:01 < sten> mnemoc: thanks ;-)
05:01 -!- januar [~januar@dsl-203-113-218-21.vic.netspace.net.au] has left #rocklinux ()
05:01 < mnemoc> using pkgsel you can enable them if you want
05:01 * sten feels a little bit dumb in a blond way
05:01 < mnemoc> of course at your own risk
05:02 < mnemoc> sten: don't worry, ROCK has evolved a bit since 1.5 :)
05:07 < mnemoc> i'll go to sleep, good luck =)
05:07 < mnemoc> cu
05:08 < sten> mnemoc: night.  thanks for the help 
05:13 -!- Paul__ [Paul@adsl-68-94-40-155.dsl.rcsntx.swbell.net] has joined #rocklinux
05:14 -!- Paul__ [Paul@adsl-68-94-40-155.dsl.rcsntx.swbell.net] has quit ("Leaving")
05:14 -!- _snyke [~snyke@eros.bingo-ev.de] has joined #rocklinux
05:15 -!- snyke [~snyke@eros.bingo-ev.de] has quit (Read error: 104 (Connection reset by peer))
06:11 -!- esden [~weasel@apollo.bingo-ev.de] has joined #rocklinux
06:11 -!- Topic for #rocklinux: ROCK Linux approaching 2.0 - join now - https://www.rocklinux.org/rock20.html
06:11 -!- Topic set by ChanServ  [Mon Feb  2 20:19:18 2004]
06:11 (Users #rocklinux)
06:11 [ __spectre__] [ daniel_ ] [ ija      ] [ Nebukadneza`] [ saskatoon] 
06:11 [ Aard       ] [ darix   ] [ jsaw_    ] [ netcrow     ] [ SMP      ] 
06:11 [ alanjwylie ] [ esden   ] [ kandinski] [ netrunner   ] [ snyke    ] 
06:11 [ blindcoder ] [ esdentem] [ kasc     ] [ owl         ] [ sten     ] 
06:11 [ clifford   ] [ fake    ] [ mistik1  ] [ praenti     ] [ tfing    ] 
06:11 [ cytrinox   ] [ Freak   ] [ mnemoc   ] [ rolla       ] [ th       ] 
06:11 [ daja77     ] [ hannes  ] [ msw      ] [ rxr         ] [ true     ] 
06:11 -!- Irssi: #rocklinux: Total of 35 nicks [0 ops, 0 halfops, 0 voices, 35 normal]
06:11 -!- Channel #rocklinux created Mon Aug  4 00:11:35 2003
06:12 -!- Irssi: Join to #rocklinux was synced in 14 secs
06:13 -!- mistik1_ [rasta@ool-44c02046.dyn.optonline.net] has joined #rocklinux
06:26 -!- mistik1 [mistik1@2001:618:400:0:0:0:44c0:2046] has quit (Read error: 113 (No route to host))
06:33 -!- kandinski [~kandinski@80-28-219-118.adsl.nuria.telefonica-data.net] has quit ("Going... going... gone")
07:08 -!- Nebukadneza` [~daddel9@dsl-213-023-058-158.arcor-ip.net] has quit (Read error: 104 (Connection reset by peer))
07:09 -!- Nebukadneza`` [~daddel9@dsl-082-082-076-191.arcor-ip.net] has joined #rocklinux
07:13 -!- trekkie3k [k3t@pD9005756.dip.t-dialin.net] has joined #rocklinux
07:49 -!- cytrinox` [~dj-nail2@p213.54.186.103.tisdip.tiscali.de] has joined #rocklinux
07:49 -!- cytrinox [~dj-nail2@p213.54.188.37.tisdip.tiscali.de] has quit (Read error: 110 (Connection timed out))
08:23 < netrunner> *want* https://www.local6.com/print/2847577/detail.html?use=print
08:32 -!- nookie471 [~nookie@217-68-184-193.cable.primacom.net] has joined #rocklinux
08:32 -!- nookie471 is now known as nookie
08:32 -!- daniel_ [~nookie@217-68-184-193.cable.primacom.net] has quit (Read error: 104 (Connection reset by peer))
08:56 -!- Baldzius [~user@213.226.136.82] has joined #rocklinux
08:56 < Baldzius> moin
09:19 -!- nookie [~nookie@217-68-184-193.cable.primacom.net] has quit (Remote closed the connection)
11:14 < blindcoder> moin
11:25 -!- Baldzius [~user@213.226.136.82] has quit ()
12:05 -!- YDS [proxyuser@104-128.dialup.itte.kz] has joined #rocklinux
12:35 -!- kasc_ [kasc@dsl-213-023-062-136.arcor-ip.net] has joined #rocklinux
12:48 -!- kasc [kasc@dsl-082-082-216-033.arcor-ip.net] has quit (Read error: 110 (Connection timed out))
12:48 -!- kasc_ is now known as kasc
12:48 -!- YDS [proxyuser@104-128.dialup.itte.kz] has quit (Connection reset by peer)
12:49 -!- YDS [~where@104-128.dialup.itte.kz] has joined #rocklinux
14:10 < sten> yay, I made it to stage 2 today
14:12 -!- kandinski [~kandinski@80-28-219-118.adsl.nuria.telefonica-data.net] has joined #rocklinux
14:24 -!- saskatoon [~saskatoon@dialin-145-254-190-112.arcor-ip.net] has quit (Client Quit)
14:24 < netrunner> https://www.kuro5hin.org/story/2004/2/15/71552/7795
14:30 -!- trekkie3k [k3t@pD9005756.dip.t-dialin.net] has quit (Read error: 60 (Operation timed out))
14:31 -!- trekkie3k [k3t@pD950289E.dip.t-dialin.net] has joined #rocklinux
14:33 -!- YDS [~where@104-128.dialup.itte.kz] has quit ("I go in hacked world............ :(")
14:34 < sten> netrunner: haha, reading article now
14:38 < daja77> moin
14:39 < rolla> re
14:39 < daja77> hi rolla 
14:40 -!- saskatoon [~saskatoon@dialin-145-254-190-112.arcor-ip.net] has joined #rocklinux
14:41 < daja77> re saskatoon 
14:46 < saskatoon> daja77: re
14:46 < saskatoon> daja77: the system is shuting down
14:47 < daja77> O_o which?
14:51 < daja77> call me blind, but rene said sth about he wrote sth to orkut, can't find any pos
14:51 < daja77> +t
14:52 < blindcoder> mike said that
14:53 < daja77> ic, is rxr at orkut?
14:53 * netrunner thinks messages about rocklinux are not in a good place on orkut (stopped using it)
14:54 < daja77> well the mailinglists and logs of this chan are in google as well
14:55 < netrunner> daja77: but that board has restricted access. 
14:57 < cytrinox`> moin
14:58 < daja77> lol found fefe and alan cox in orkut
15:08 -!- holyolli [~holyolli@port-212-202-30-65.reverse.qsc.de] has joined #rocklinux
15:08 < holyolli> moin
15:09 < daja77> moin holyolli 
15:09 < holyolli> huhu daja77 :)
15:35 < netrunner> daja77: how many friends does alan cox have?
15:35 < blindcoder> moin
15:36 < daja77> 113 iirc
15:38 < blindcoder> orkut is overrun by geeks
15:40 < daja77> yep found lots of kernel guys in it
15:57 -!- vegai [~vegai@195.218.66.135] has joined #rocklinux
15:58 < vegai> howdy, couple of small questions which I don't think can be found in manuals...
15:58 < vegai> 1) does rock depend on devfs? 2) is there a manifesto of some kind?
15:59 < daja77> 1) depends on version 2) no
16:08 < vegai> oy! really nice net configuration
16:08 < vegai> daja77: hmm, ok. So, perhaps rc5 doesn't depend on it?
16:10 < daja77> it doesn't
16:18 < daja77> https://unix.rulez.org/~calver/pictures/ruslinux.jpg
16:28 < holyolli> *lol*
16:29 < darix> teamwork: https://sege.nu/hypermail/humor/att-0003/01-teamwork.jpg 
16:29 -!- Nebukadneza`` [~daddel9@dsl-082-082-076-191.arcor-ip.net] has quit ("Client exiting")
16:30 < daja77> O_o
16:30 < fake> hi
16:30 < daja77> ho fake 
16:44 -!- Netsplit wells.freenode.net <-> irc.freenode.net quits: esdentem, th, cytrinox`
16:44 -!- Netsplit over, joins: cytrinox`, esdentem, th
16:44 -!- vegai [~vegai@195.218.66.135] has quit (Remote closed the connection)
16:57 < mnemoc> moin
17:05 < fake> hi mnemoc 
17:08 * rolla fucking hates his company
17:10 < mnemoc> hi fake, rolla
17:11 < tfing> yo everybody
17:12 < mnemoc> hi tfing 
17:32 -!- capchaos [~capchaos@p213.54.115.197.tisdip.tiscali.de] has joined #rocklinux
17:50 < blindcoder> hi hi and rehi
17:50 < capchaos> Hi blindy
17:58 -!- netrunne1 [~andreas@p5080241B.dip0.t-ipconnect.de] has joined #rocklinux
18:04 < sten> glibc23 failed in stage 5 :(
18:04 < sten> error is cannot find linux headers
18:06 -!- netrunner [~andreas@p508026D3.dip0.t-ipconnect.de] has quit (Read error: 60 (Operation timed out))
18:08 < mnemoc> sten: uhm?
18:08 < mnemoc> hi blindcoder 
18:10 < mnemoc> sten: that code change just yesterday to not need linux2[46]-source to build libc
18:10 < sten> mnemoc:  I sync'd at ~4:00 GMT
18:11 < sten> mnemoc: maybe closer to 8:00 GMT
18:11 < mnemoc> sten: maybe cliff's patch was buggy :\
18:11 < mnemoc> sten: w8
18:12 < sten> mnemoc: to make matters even more confusing:  my build/target/root/usr/include/linux looks normal
18:13 < mnemoc> -                --with-headers=$root/usr/src/linux/include --with-gd=/usr \
18:13 < mnemoc> +                --with-headers=$root/usr/include/linux --with-gd=/usr \
18:14 < mnemoc> that changed on r2353
18:15 < sten> mnemoc: my $root/usr/src/linux/include doesn't have any .h's.  Just dir's for each arch
18:15 < mnemoc> hm?!
18:16 < sten> yeah, it's a normal linux-2.4.24-rock too.  (not even a linux26 issue)
18:16 < sten> mnemoc:  shouldn't "+                --with-headers=$root/usr/include/linux --with-gd=/usr \
18:16 < sten> <mnemoc> that changed on r2353
18:17 < sten> usr/src/linux/include/linux
18:17 < sten> err, I mean $root/usr/src/linux/include, be $root/usr/src/linux/include/linux
18:17 < sten> ?
18:17 < sten> because that has the .h's
18:17 < sten> (.h's are the headers, yeah?)
18:18 < mnemoc> the '-' has the previous code, the + is the broken-current one
18:18 < mnemoc> s/has/was/
18:18 < mnemoc> package/base/glibc23/glibc23.conf line... 37?
18:19 < mnemoc> revert it
18:20 < sten> ok.  And then re-run Build-Target, starting at stage 5?
18:20 < mnemoc> rm $root/var/adm/logs/5-glibc23
18:21 < sten> "./scripts/Build-Target -job 5-glibc23" should work, yeah?
18:21 < mnemoc> sure =)
18:22 < sten> mnemoc: by the way, I don't need to run Puzzle, or any of that, after changing package/base/glibc23/glibc23.conf, do I?
18:23 < mnemoc> nope
18:24 < sten> haha, it found the new/updated files automatically.  (and printed a pretty message)  ROCK 2.0 is even more fun then I remember 1.5
18:24 < mnemoc> =)
18:25 < mnemoc> welcome back =)
18:27 < sten> it definitely feels like home :-)
18:28 < sten> out of curiousity, what do you think of udev?  From what I've been reading, it is superceding devfs for > linux-2.6
18:28 < mnemoc> ^^
18:29 < mnemoc> they are _trying_ to do devfs on userspace using hotplug
18:30 < sten> how does the rockplug approach differ?  (rockplug is another "new" thing for me)
18:30 < mnemoc> rockplug is like hwscan but improved
18:31 < sten> so it doesn't use this udev userspace approach?  (meaning there's a hybrid hwscan + devfs)
18:31 < mnemoc> kind of
18:32 < mnemoc> jsaw_ author it, he can give you details i don't know, for me it's the hwscan replacemente :p
18:35 < sten> mnemoc: I found a README in the rockplug subversion repository.  reading it now
18:39 < sten> mnemoc: yeah, I think you're right about rockplug as hwscan replacement/improvement.  It doesn't have the overarching "reform the system" goals of udev.  (although apparently udev is LSB compatible, whereas devfs is not)
18:40 < mnemoc> i'm more than happy with devfs :)
18:41 < sten> I probably will be too.  I've been using Slackware for a while now, so many a dynamic /dev scares me ;-)
18:41 < sten> s/many/maybe
18:42 < mnemoc> i would like to know if devfs has mantainer again :\
18:43 < daja77> it has
18:44 < mnemoc> [daja77]! 
18:44 < mnemoc> daja77: who?
18:45 < daja77> dunno, just read it in zack's kernel news last months
18:45 < sten> is devfs really closer to BeOS, FreeBSD, and IRIX's implementations of /dev; then udev is?
18:45 < daja77> it is just saner :)
18:47 < sten> I read that it has race conditions.  (are these pretty rare?)    (I'm leaning towards devfs, by the way, but the udev author has a lot of bad stuff to say about devfs, and I'm curious how much of these "bad things" affect me)
18:55 < mnemoc> i never knew how real those 'bad things' were, from the begining people stated goosh's was a wrong aproach, until he got pissed enough to quit. and kernel ppl gladly taged devfs as 'obsolete'
18:56 < mnemoc> s/goocsh/gooch/ :o
18:57 < sten> ah.  Yeah, the VFS guy (I forget his name) was/is against devfs, because he thinks that because it can be done in userspace, it automatically should be.  (personally, I disagree in this case)
18:57 < mnemoc> they tag it 'obsolete' even before having a single line of code to replace it.... that was absurd imho
18:57 < sten> udev is vaporware?
18:58 < sten> I thought they moved it into userspace...
18:58 < mnemoc> udev is userspace
18:58 < sten> so " before having a single line of code to replace it"?
18:58 < sten> (didn't they cut the entire idea out of the kernel)
18:59 < mnemoc> idea!=code
18:59 < sten> but they defered to userspace
18:59 < sten> I think that /dev management is the kernel's job too.
19:00 < sten> at any rate, I think I have a good handle on it now.  thanks
19:01 < mnemoc> :)
19:01 < mnemoc> daja77: how was your exam?
19:01 -!- Nebukadneza [~daddel9@dsl-082-082-076-191.arcor-ip.net] has joined #rocklinux
19:03 < daja77> mnemoc: have it on thursday
19:06 < mnemoc> daja77: do u know where/why .gz manpages get silently uncompressed?
19:06 < daja77> nope
19:06 < mnemoc> :(
19:07 < daja77> but i remember there was sth like on ml before
19:35 < blindcoder> build-pkg IIRC
19:35 < blindcoder> there's even a comment there
19:36 < blindcoder> just grep for man
19:43 < praenti> hi
19:43 < praenti> daja77: here?
19:44 < praenti> ping daja77 :-)
19:48 < praenti> hmm. slow connection or packet loss :-(
19:48 < blindcoder> hi praenti 
19:48 < praenti> hi blindcoder 
20:10 < sten> oh no....
20:11 < sten> How do you resume a Build-Target?  When it aborted on 5-glibc23 earlier today, I restarted with "./scripts/Build-Target -job 5-glibc23"
20:11 < sten> how do I finish the build?
20:12 < praenti> sten: simple run ./scripts/Build-Target
20:12 < praenti> the system continue with last package
20:12 < praenti> s/last package/the last package/
20:13 < praenti> so if 5-glibc23 aborted, the scripts will try to build them again
20:14 < sten> praenti: I fixed 5-glibc23, and the next package is 5-gcc3, so it'll pick that up and move on, right?
20:14 < praenti> sten: mom. abort your build. you must set a option first
20:15 < sten> praenti: where?
20:15 < sten> praenti: (the 5-glibc23 build completed successfully, but Build-Target stopped)
20:16 < praenti> in ./scripts/Config you can set "Retry building broken packages"
20:16 < praenti> so if a package is not complete it will be build again
20:16 < sten> praenti: the package is fine
20:17 < sten> I need to continue with my build
20:17 < sten> (I fixed the package)
20:17 < praenti> but where is your problem then
20:17 < praenti> the build is continued by ./scripts/Build-Target automatically
20:18 < praenti> and Build-Target only aborts if s.th. is wrong with a package
20:18 < praenti> or you as user stop it
20:18 < sten> thank you.  I was trying to verify if ./scripts/Build-Target would continue, after manually ./scripts/Build-Target -job 5-glibc23
20:19 < sten> because 5-glibc23 failed earlier.  (I fixed it)
20:19 < sten> I'm paranoid about throwing out six hours of compilation time
20:20 < praenti> sten: should. because the package list is checked from the beginning and for each package in $root/var/adm/logs/stage-packagename.log
20:21 < praenti> if an $root/var/adm/logs/stage-packagename.err is there the script know, that s.th. was wrong with building the package
20:21 < praenti> if no log is there, the scripts build the package, because it is not build yet
20:22 < sten> praenti: yup.  And it uses this list of logs to know what stages to skip?
20:22 < praenti> so the key is the $root/var/adm/logs/ directory
20:22 < praenti> not exactly. you can take a look into $your-rock-dir/config/$configname
20:23 < praenti> normally rock-2.0.0-rc/config/default
20:24 < praenti> there is a packages file
20:24 < praenti> the packages are sorted by the build priority
20:25 < praenti> and in front of each line you have s.th. like X -----5---9 984.000
20:25 < sten> praenti: yeah, just like old times.  (the last ROCK I used was 1.5)  I don't remember being able to resume builds back then.  (which is why I'm super-paranoid)
20:25 < praenti> :-)
20:26 < praenti> sten: ahh. then you know this syntax... but dont edit the file. it is generated by ./scripts/Config
20:27 < sten> praenti: ok.
20:29 < sten> praenti: if I edited it, I could bypass the package.desc, which wouldn't be a clean way to do things anyway
20:30 < praenti> sten: the problem you would get is that ./scripts/Build-Target would work with your change until you execute ./scripts/Config
20:31 < praenti> sten: ./scripts/Config generates the file from the *.desc on each startup :-)
20:31 < praenti> because of that Config is so slow :-(
20:32 < sten> praenti: ah.  I was wondering about that.  I seem to remember having to manually run ./scripts/Puzzle, or something similar, after modifying a .desc.  (I've learned that Puzzle is run automatically now)
20:33 < praenti> yes. it is integrated in configure, but only for the *.desc
20:33 < praenti> *.conf *.patch ... are read at runtime
20:34 < praenti> and ./scripts/Download reads the urls files and chksum directly from the *.desc
20:35 < sten> that makes sense.  It's easier to re-patch, reconfigure, and fix broken urls that way
20:35 < sten> s/that/this
20:35 < praenti> yeah
20:38 < sten> I'm really glad that there's a generic/minimal target.  I freaked out when I learned that there were no rescue.tar.bz2's anymore, because I like to build ROCK from minimalistic roots.  (and I only have an althon-750)
20:38 < praenti> i will leave now. must have some sleep tonight...
20:38 < praenti> cu
20:38 < sten> night
20:46 < esdentem> hi all
20:47 < fake> hi esden
20:48 < esdentem> hi fake 
20:48 < blindcoder> wow, esdentem is alive :)
20:58 < esdentem> blindcoder: yes from time to time ;)
20:58 * esdentem searching reports about problems with kernel 2.6 and e1k network cards
20:59 < esdentem> somehow when I load the driver there is no device listed by ifconfig
20:59 < esdentem> I mean no eth0 ... :(
20:59 * blindcoder happy on 2.4 :)
21:00 < esdentem> blindcoder: :P
21:03 * rolla is ahppy with his 2.6 kernel
21:08 < esdentem> ahhh that card is not e1000 but 3C996 so the driver is called BCM5700 *sigh*
21:08 < esdentem> as it seems
21:32 -!- kandinski_ [~kandinski@80.26.152.187] has joined #rocklinux
21:46 -!- kandinski [~kandinski@80-28-219-118.adsl.nuria.telefonica-data.net] has quit (Read error: 110 (Connection timed out))
21:48 -!- kandinski_ is now known as kandinski
21:51 * netrunne1 asks himself where to get ssh for the zaurus
21:51 -!- netrunne1 is now known as netrunner
22:04 -!- rolla [maisenhe@adsl-66-136-183-237.dsl.stlsmo.swbell.net] has quit ("Changing server")
22:22 < fake> netrunner: what cpu? x-scale?
22:28 -!- kasc_ [kasc@dsl-082-082-216-221.arcor-ip.net] has joined #rocklinux
22:28 < netrunner> fake: jup. c700
22:33 < fake> netrunner: running ?
22:33 < fake> os i mean
22:41 -!- kasc [kasc@dsl-213-023-062-136.arcor-ip.net] has quit (Read error: 113 (No route to host))
22:41 -!- kasc_ is now known as kasc
23:00 < netrunner> qtopia
23:01 < netrunner> I borrowed it because I want to buy one, and it's nice to test the handling before actually buying.
23:02 -!- kandinski [~kandinski@80.26.152.187] has left #rocklinux ("Leaving")
23:28 -!- mistik1_ is now known as mistik1
23:57 -!- holyolli [~holyolli@port-212-202-30-65.reverse.qsc.de] has quit ("Leaving")
23:58 -!- capchaos [~capchaos@p213.54.115.197.tisdip.tiscali.de] has quit (Read error: 60 (Operation timed out))
--- Log closed Wed Feb 18 00:00:51 2004