IRC log started Mon Mar  8 00:00:01 1999
[msg(TUNES)] permlog 1999.0308
ωνω SignOff yery: #TUNES (Read error to yery[benetnash.ffke-campus.mipt.ru]: EOF from client)
ωνω Fare has changed the topic on channel #Tunes to: Reflective Computing System - http://www.tunes.org/
ωνω binEng [bineng@dialup41-1-34.swipnet.se] has joined #tunes
ωνω SignOff Fare: #TUNES (Ping timeout for Fare[esmeralda.enst.fr])
ωνω Fare [rideaufr@esmeralda.enst.fr] has joined #Tunes
ωνω binEng [bineng@dialup41-1-34.swipnet.se] has left #tunes []
ωνω binEng [bineng@dialup41-1-34.swipnet.se] has joined #tunes
<binEng> hey, someone here?
ωνω SignOff Fare: #TUNES (Ping timeout for Fare[esmeralda.enst.fr])
ωνω SignOff binEng: #TUNES (I understand.)
12:10pm
ωνω Fare [rideaufr@esmeralda.enst.fr] has joined #Tunes
<Fare> Gakuk?
04:00pm
ωνω _QZ [brand@p0wer.qzx.com] has joined #tunes
<Fare> hum
05:20pm
ωνω SignOff Fare: #TUNES (Back to the Tunes OS project -- /whowas Fare)
ωνω Marsology [Marsology@ip34.reno.nv.pub-ip.psi.net] has joined #Tunes
<Marsology> Hello.
<_QZ> hello
<_QZ> what brings u to #tunes?
<Marsology> A fascination with operating system design.
<_QZ> u seen brix?
07:50pm
<Marsology> brix? no.
>>> _QZ [brand@p0wer.qzx.com] requested PING 920951548 461579 from #tunes
<_QZ> brix?
<abi> brix is a free portable protected memory-space preemptive multi-threading multi-user persistent object-oriented high-speed easy-to-use distributed OS located at http://www.qzx.com/brix
<Marsology> I was browsing www.tunes.org and saw the link here.
<Marsology> Hmm. brix is certainly buzzword-enabled.
<_QZ> :)
<Marsology> The recent boom in alternative OS projects is a very good thing, IMHO...
<_QZ> brix is pretty much like tunes
<Marsology> Is it open source?
<_QZ> cept brix will be here WAY before tunes even gets any code written
<_QZ> brix will be open source, but not right now
<Marsology> hmmm.
<Marsology> what processor/hardware architectures does it support?
<_QZ> making the OS open source and open to changes means it will never take off
<Marsology> or should I just read the web page and shut up? :-)
<_QZ> right now it supports x86
<Marsology> ahh.
<_QZ> but only the kernel is machine dependent
<Marsology> hmmm.
<Marsology> do they say how large the kernel is?
<_QZ> they?
<_QZ> i am the one making brix
<Marsology> Oh.
<Marsology> Cool :-)
<Marsology> So how big's the kernel? :-)
<_QZ> the kernel will be about 6-8k when finished
<Marsology> not bad... couple months of porting work to a new CPU type, plus drivers...?
<_QZ> i already have alot of the drivers done
<Marsology> yes, but I assume many of them would have to be rewritten or modified on a different hardware platform....?
<_QZ> vesa frame buffer support will let it run on any vesa card
<_QZ> ya
<_QZ> i will probably port it to the 6811 after the x86 version is ready
<_QZ> and maybe the ppc
<Marsology> 6811? wow. You have a machine based on a 6811? what is it?
<_QZ> not a computer
<_QZ> robot
<Marsology> Hmm. Never heard of it...
<_QZ> never heard of what?
<Marsology> a 6811 robot.
<_QZ> uhh
<_QZ> the 6811 is like THE cpu to make robots with
<Marsology> Ahh. I thought you were referring to some commercial product.
<_QZ> its a kick butt little chip
<Marsology> based on the general 68k ISA?
<_QZ> no
08:00pm
<Marsology> Hmmm.
<Marsology> So what distinguishes Brix from other systems?
<_QZ> everything
<Marsology> lol, ok
<_QZ> it has nothing in common with existing systems
<_QZ> it doesnt have apps
<Marsology> ahh. data-oriented?
<_QZ> yup
<Marsology> oh, there it is - document-centric interface
<_QZ> u send action messages to objects
<_QZ> the language is integrated into the UI
<_QZ> perfectly integrated
<Marsology> huh. that's interesting.
<Marsology> how do you program it?
<_QZ> instead of apps u build collections of tools that all work on a type of data object
<_QZ> u program the tools
<_QZ> tools are kinda like functions
<Marsology> I see.
<Marsology> Interesting. Are you using the FLUX kit?
<_QZ> hahah no
<_QZ> do u think my kernel could be 8k with flux?
<Marsology> Depends on how you do it :-)
<_QZ> and when i say kernel i mean boot sector+setup code+kernel
<_QZ> the setup code is about 4k
<Marsology> Nifty.
<Marsology> So what boot drivers do you use?
ωνω dino [dino@pm-ppp119.triton.net] has joined #tunes
<dino> hellos
<Marsology> Hello.
<_QZ> as in storage driver?
<_QZ> i have a floppy driver right now
<Marsology> QZ: yes. you have to boot somehow...
<Marsology> floppy eh... planning to do SCSI too?
<_QZ> the setup code uses int 13h to load the floppy drivers and ofs drivers and then everything else is loaded by brix
<_QZ> scsi and ide will come along later
<Marsology> Hmmm. Fun.
08:10pm
<Marsology> So does the TUNES project have any timetable for shipping code, or is it still in "meander along and figure out our philosophy" mode?
<_QZ> haha
<_QZ> tunes will begin coding sometime in the 30th century :)
<_QZ> but tunes is a fat os
<_QZ> its compiler is part of the kernel
<Marsology> You don't like it much eh?
<_QZ> it uses too much fairy dust
<Marsology> I don't know, I can see certain advantages to having a code generator in a kernel...
<Marsology> in theory, that lets the platform porter/system administrator tailor binaries to the specific hardware...
<_QZ> but tunes will not be able to run on limited machines
<Marsology> but I suppose the principle could be extended until you had all software integrated in the kernel, a la Xerox Star
<_QZ> its compiler is the only way it can have protection
<Marsology> Ahh.
<_QZ> it proofs all code that is run
<_QZ> and then it inserts check points into the code to monitor it
<Marsology> that seems like a rather ambitious endeavour.
<_QZ> cuz tunes doesnt use any hardware protection
<_QZ> and tunes merges functions together
<_QZ> as in all apps into one
<_QZ> the way it handles multitasking is done by taking the code streams from app A and app B and merging them into a single stream
<_QZ> so it never actually changes tasks
<_QZ> that requires continuous code relocation as the system is operating
<Marsology> It sounds like you are not particularly fond of TUNES :-)
<_QZ> i prefer an os that can run on any machine
<_QZ> brix can scale from a watch OS to a server OS
<_QZ> tunes cant be either of those 
<_QZ> its too fat to fit in the limited resources of a watch and i doubt it could work as a server OS
08:20pm
<_QZ> other than that tunes and brix are much alike
<_QZ> u watch star trek?
08:30pm
<Marsology> erk.
<Marsology> Hello.
<Marsology> Off making dinner.
08:50pm
ωνω SignOff Marsology: #TUNES (Ping timeout for Marsology[ip34.reno.nv.pub-ip.psi.net])
ωνω SignOff dino: #TUNES (Hey!  Where'd my controlling terminal go?)
ωνω lar1 [larman@208.254.230.212] has joined #tunes
<lar1> HI
<_QZ> hi
<lar1> Does RH 5.1 use libc5?
<_QZ> no
<lar1> It uses that glib thing?
<_QZ> glibc2
<lar1> Will things for just glibc work?
<_QZ> glibc=libc5
<_QZ> glibc2=libc6
<lar1> Then wy are there 2 directorys in the RH site?  Libc5 and glibc?
<_QZ> they probably named it glibc instead of glibc2
<lar1> Ok
<_QZ> rpm's for rh5 wont work on earlier versions of rh
<lar1> Do you think the latest version of the xfree86 SVGA server will have the bugfix for my vidcard?
<_QZ> heh
<_QZ> what card?
11:20pm
<lar1> Trident Cyber 9385
<_QZ> is there no xfree server for it?
<lar1> I don't think so
<lar1> Not on the xfree ftp
<_QZ> u should find another server that has support for it
<lar1> Like what?
<_QZ> the xfree svga server doesnt use the acceleration on yer card
<lar1> I have acceleration?
<_QZ> uhh probably
<_QZ> most cards do
<lar1> What other server would have support for it?
<_QZ> odd accelx doesnt have that card listed
<_QZ> how old is it?>
<lar1> Not very old... couple months... Its in my laptop
<_QZ> ohhh
<_QZ> that explains why its not in my list
<lar1> accelx has it in the laptop drivers
<_QZ> then get accelx
<lar1> $$$$$$$$$$$$$$
<_QZ> warez
<lar1> How big is it?
<_QZ> ax is 18meg
<_QZ> dunno about lx
<lar1> Hmmm, what is the best Linux warez place?
<_QZ> i would think lx would be a meg or two smaller since there a fewer laptop cards
<_QZ> i got mine on efnet in like #warez4free or something
<_QZ> just hop on the bots and see if they have it
<_QZ> maybe #linuxwarez
11:30pm
<lar1> On DALNet?
<_QZ> efnet
<lar1> Ok
<lar1> I'll take a look-- BBRB
ωνω SignOff lar1: #TUNES (Leaving)
11:40pm
ωνω SignOff _QZ: #TUNES (BRiX [http://www.qzx.com/brix] :: sleep)
[msg(TUNES)] newlog 1999.0309
IRC log ended Tue Mar  9 00:00:00 1999