| |
| |
| |
|
Page: 1 2 3 4
Comments:
<0> what is the technical term for 'voluntarily giving away cpu possession'. so basicly the inverse of preemption?
<1> yield
<2> Cooperation?
<0> ah. yes. that was it. thanks
<0> google patent search is fun, by the way
<3> code search is funner
<3> search for funny stuff on the comments
<3> you find all sorts of colorful things
<0> you won't find a fart deodorizer in the code search
<1> yeah gooents is good, got sick of the ****ty ibm search
<4> geist: got the cables made and working properly, as a note: data lines reversed should hurt the port, just give "Device not accepting address" errors
<1> shoud not
<4> yes, shouldnt :)
<4> my ports still work
<4> go the USB2.0 hub hot glued to drinking straw pieces to the motherboard >:)
<1> loco
<4> Thermal 1: ok, 109.4 degrees F
<4> is that reasonable for a CPU?
<5> yeah
<5> but it's getting a little high
<4> good bc this is a fanless nemiah and i wasnt sure what's a good temp for the cpu
<4> eieio: it's fanless, 109.5 is the highest i've seen it hit
<5> that's fine. what chip?
<4> nemiah something
<4> 800mhz via nemiah C9
<4> "thin client" i turned into a workstation
<4> oops!
<6> meep
<5> yo
<7> Whee.
<6> moop
<5> sup dudes?
<6> here i come
<6> coming to... get ya
<2> Here I am.. on the road again.. ;)
<5> Here i am, rock you like a hurricane...
<5> woot, finally more content for the site
<5> i keep meaning to go through all my stuff and put it up, but i rarely do :-/
<4> yay
<4> geist: So far so good with my custom cables
<4> fits nicely inside the case
<5> songs: http://www.coreytabaka.com/index.php?r_s=541&r_p=544&flog_id=19
<4> Thermal 1: ok, 132.8 degrees F
<4> that, however worries me
<6> nn: fantastic
<5> nn: yeah that's gettin on the hot side
<4> put the aluminum cover back on and it went from 104 to 132.8
<4> err 109
<6> 132? nah, that's fine
<4> geist: what's a 'warning' and 'danger' point for a via nemiah? it's fanless CPU
<6> beats me
<4> Im thinking i could probably do good to improve heatsink to case transfer
<4> maybe put a few degF off that way
<6> of course you could also just get a real computer
<4> Im really not down for a fan in this
<6> the vias are nice and all, but they do really ****
<4> geist: ahh but this is so little and convenient :)
<4> i truly dont have much space
<4> and this sits nicely behind my LCD
<6> however I have found it to be a decent test for code running on a 'slow' cpu
<4> i dont even have room for a CRT anymore
<4> ahh.. the speed of this is just right
<4> does everything i ask of it without any delays
<4> i think maybe a fan might be a good idea after all.. i'll find something small and quiet shouldn't be too terrible
<6> i think mine has a fan on it
<4> mines only 800mhz, a fanless model
<5> nn: you could go peltier
<4> eieio: i think just a small, kinda slow fan wouldnt be too terrible and would be very cheap
<4> it wouldnt add much noise and cash is rather tight still having just moved recently to nyc
<5> ahso
<4> Thermal 1: ok, 125.6 degrees F
<4> 5 minutes with the cover off dropped 7 deg
<3> woo, I can play "money" on my b***
<6> grats
<5> coo
<5> i put up a (home) recording of stumbeline i did a few years back.
<8> I have a b***
<8> but no strap, nor a b*** amp =P
<8> I'm using a audio amp (a quite good one at that, it has analog VUs =D)
<5> heh, i used to use my computer with DSP hardware. but it blew out in a storm :(
<8> =[
<8> bad thing is that my eletrical install is crap
<8> for example
<5> only the DSP and the sound card and the sound card PCI slot went bad though
<8> if I touch the string with bare foot while the shower is on I get shocked =P
<5> oof
<8> not to say all the noise, wee
<5> dammit, i hate how sometimes hibrunating windows messes with loading apps after it comes back up
<8> ok, back to reading about memory managers
<8> and slapping moskitos
<5> do you think it's better, in general, to register individual syscall handler interfaces for each module (read C compiliation unit) with access to the internal parts of the module, or have a single syscall handler that uses exported API of the other modules. the tradeoff being, the first method can potentially be more efficient with direct access to any structures in the module; the second method requires a bit more code, but also re
<6> line got cut off there
<6> ' more code, but also re'
<5> is there a line length limit?
<5> ...but also reinforces good exposed API that dynamic kernel modules can take advantage of
<9> there is, but good clients send don't discard the rest of the message but send a second one
<5> ah, guess trillian isn't among them maybe
<5> maybe i'll start using ircII again
<8> I know that irssi does
<5> a finer point of the trade off is that some things a syscall handler may need to do aren't necessarily good candidates for exporting to other modules
<5> but a central handler eliminates the need to iterate a list of registered handlers to find the correct handler for a particular syscall
<5> except for dynamic modules that expose syscall interfaces, those must necessarily reside in a list
<5> i'm probably splitting hairs
<8> go for the the second one
<5> what's your reasoning?
<8> reinforces good exposed API that dynamic kernel modules can take advantage of
<8> yep, that's me, always overengineering things ;)
<5> heh
<5> the first method is more general though (and also what i'm currently using). i can remove an entire subsystem by removing it's target from the build.
<8> if you setup some nice macro vodoos you can do that too
<8> unless I misunderstood you, the second method is more or less what the linux kernel does?
<5> also statically compiled modules/subsystems are largely indistinguishable from dynamic modules
<8> haha, ##c looks like a warzone
<5> damn there's a lot of people in there
<8> ##c++ could be renamed ##nazi too
<8> hmm, just a question, how easy is it to port gcc to a new OS?
<8> or glibc, rather
<8> :s/easy/hard if apropriate =]
<5> medium
<5> it's not hard per se, just a lot of things to handle
<8> but is it like, just grunt work (replace syscall here and there, here and there, here and there)?
<5> umm, no it's more than that. there is a lot of coordination that has to be done with the way the platform (OS) handles different things, and the architecture, and the combination of the two....
<8> argh, where do all these mosquitoes come from >=(
<5> standing water?
<8> arch == i386?
<8> eieio: I mean, the house is pretty much sealed from the outer world, unless the fly inside the AC =P
<5> could be, check your AC condensation trap. if it's full of water you could have them growing in it
<8> in the mean time, let's just finish this gl*** o water and spray under the table =P
<8> this paging stuff is confusing
<5> one time, when i lived with roommates, we had a sack of potatoes that went bad on top of the fridge. we kept wonder where all the mayflies were coming from until one day we found the bag dripping down the side of the fridge.
<5> it was the nastiest thing i've ever seen or smelled
<8> eww
<8> how much time?
<5> umm, i guess it must have been a month or so old
<8> ewwwwww
<5> it was kind of behind some stuff, so we didn't see it
<5> squirming liquid potatoes, that is
<2> lmao
<2> Sounds like fun.
<2> Especially cleaning the fridge afterwards.
<5> yeah, that was an exercise in gag reflex control
<2> Haha
<2> Gag or vomit? :P
<5> you couldn't really smell it until we moved the bag
<5> both
<2> Heh
<2> You've created an eco-system on your fridge! Hilarious.
<2> And how dare you destroying it again by moving the bag..!
<5> yeah, we were laughing the whole time, which didn't really help with the whole vomit control thing
Return to
#osdev
or
Go to some related
logs:
#css
guysoft.com
\pL+ perl
#qemu
#centos
audioscrobbler handshake 5b
17th most popular language
#fluxbox
#lisp
how to install iperf ubuntu 5.10
|
|