The collected works of skywriter - Page 6

that was intended for other people. if you knew enough to identify the relevant fault tolerance technique, you should know that stuff already.



you don't need the machine to learn about that stuff...

so, knowledge about programming a fault tolerant system and knowledge about systems engineering derived from having a representative system are two different things.

with respect to programming, i suspect you may learn some things, or perhaps not. it depends on how the system exposes the fault tolerance to the application level, and thus provides a way for faults in the application programming to propagate through the system as undetectable faults, or compromise the integrity of the fault tolerance of the system. my opinion is it is a poor design that allows either, and thus the only insight would be derived from missing functionality that if implemented would provide a basis exposing ways to defeat the system.

on the subject of systems engineering: having done fault tolerant design for the enterprise space for a long time, i'm pretty confident saying that 'having a fault tolerant system' provides only superficial insight into fault-tolerant design, and the the best way to get insight into such a system employing said techniques is to read the literature (which only gets you the theoretical background) and/or learn how to do the design work and get experience in the practical aspects of fault tolerant systems design.

in a hardware fault tolerant architecture, much about what provides the fault tolerance is not exposed in terms in control, or observability except on a diagnostic, or retry level. both of which should only be accessed in a privileged state otherwise they provide methods for defeating the fault tolerance. They are generally not provided in general documentation since this often provides a way for competitors to generate FUD.

i suppose though, like any determined person that if you want to spend a lot of time to figure out how it works then you'll find something out. surely having the relic in front of you helps in this regard. so, please post away!

ah, yes the O3!

i'm taking bets now! time to start a poll: http://forums.nekochan.net/viewtopic.php?f=6&t=16723039

since the new sgi has resurrected two old sgi names to invigorate their product line, which be next?!?!

* if you don't find your favorite, add your own to the comments!

* be the first on your block to be a big name branding expert!

* amaze your friends!

* terrify your enemies!

* get them while they're hot!

* nothing is too crazy folks! run wild!

btw there are SO many to choose from! http://www.sgi.com/company_info/trademarks/sgi.html

i should have said 'trademarks'. and certainly it means a lot to many people.

well, there was an onyx4, but i don't remember an onyx yet. so, 3 or 5 which ever :)

dude, you are ruining my thread!

all gods little indy's cried today.

jeepers! already?? i missed the press release...

i guess we got something here!

exactly. besides not enough red!

there isn't. it's just off the shelf servers

does anyone have any good experience with using a VNC between windows and OSX?

the primary use case will be running the VNC server on a windows 7 HTPC, and doing some basic configuration stuff from a client running on OSX. i don't need the flash or video to get handled. i just need to be able to monkey with the HTPC while someon else is using the TV to watch cable.

so, what's a good VNC that works with this use case?

hrm. i tried the remote desktop thing. on the windows machine i get the remote assistance controls. but there is no remote desktop controls. time to start figuring out the issues... *sigh* nothing is ever straightforward for me.

so, i guess the problem here is that home premium can't have remote desktop functionality. wow, talk about having your balls cut off.

time for plan B

whatever that may be.

back to square one.

so, the problem is that i can't find a windows server and osx client for the same version of VNC. i didn't want to litter my machines with various versions of each/ i was hoping someone else had been able to solve something basic.

google is no help yet, and all the VNC's i've looked at either don't satisfy the above, or in one case cost money. i don't want to spend money to find out the descriptions were wrong, or i didn't read them correctly.

so, anyone have a windows 7 home premium server/home and a mac osx 10.5 or 10.6 VNC running?

ps, i tried some windows 7 hack to enable it. typically it didn't work. i'm to sure wtf it did to my install though :(

ok, success. on the windows 7 HTPC (connected to TV) i have the tightvnc server. and on the Mac OSX i have Chicken of the Sea client.

so, no matter how i set the server side; i can't get more than 800x600 pumped out of the VNC server. there is no windows setting for it either.


blah...

isn't there some half-assed GNU pascal to c wrapper like they do for fortran.

next total BS result:
i removed tightvnc and loaded realvnc.
it came up displaying the correct screen size on the local client - you could see everything from the server screen. great full screen on both sides.

however, the mouse scaling was wrong. the 1024x600 addressing of the mouse on the local machine didn't scale to the servers 1920x1080, it only addressed 1024x600 of the server screen. the client shows the cursor in the bottom right hand corner, and it was only near 1024x600 coordinate of the server's screen. as you got closer to the top left hand corner the cursors tracked closer together. note: this discrepancy is not show at all on the local machine. it LIES about the cursor position.

why am I having all the fun with this? I believe the general trend toward better software functionality in PC software has resulted directly into more idiotic errors for me. as if everyone's success is intimately linked to my own failure. never has any of this crap actually looked like people claim. only MacOS has excepted me from this torture.

the problems, whatever which ever they are seem to be tied to the physical size of the client i'm using vs the server. things are not translating/scaling/noodlating correctly. *Sigh*

i don't think NT AXP supports italics.

oh i do, when i'm getting paid for it.

actually i'm doing everyone the honor of knowing how to read, and what these products are, without needless punctuation and formatting. forums are informal, you're not getting graded on grammar. the italics actually make it hard to read because they render so poorly; which is why you don't see anyone else using them.

but, seriously where do you get the idea that italicizing the names of products is even correct grammar? so me the rule and i'll shut up.

so, you condemn me for not capitalizing based on your need to defend the use of the rules of grammar, but there is no grammatical reason you could find for your use of italics. i didn't think so, your stance has no defense. fine ignore away, you've lost your basis for italics other than the need to look fancy.

there, that's all i was looking for.

thanks!

too bad that was after UltraViolet was defined. i would really have preferred an x86 ccNuma solution based on AMD's hacking a proprietary ccNuma porotocol on top of hypertransport, rather than Intel's ground up ccNuma solution QPI.

now it's just another x86 socket in an off the shelf reference design commodity server.

crzy, why is it good for you?

I use R all the time



also Excel for quick stuff.

if this is true with $/green MIP, then yes it's the right decision for rackable/sgi.

that's an alphaserver worth having!

As April 3rd approaches, and the tide of positive reviews roll in sensuous waves of delight ( http://gizmodo.com/5507037/ipad-mega-meta-review-works-great-no-surprises?skyline=true&s=i ) only one questions remains: When will you get yours?

* please, if you have something negative to say, and who doesn't from time to time, make your own thread. this thread in not the one you're looking for.

i forgot to supply my own answer! so then, i'll be waiting until the 3G/32GB version comes out and i don't see any reason to delay the purchase. if in the event there are problems with the product, it will be addressed as rework in one form or another eventually, and there's no sense in depriving myself of one since there is no alternative worthy of my attentions.

i need 3G for when i'm on the road, and at work. our wifi network uses RSA SecureID authentication which isn't supported in a compatible way with iPhoneOS. 32GB seems about right extrapolating from my 16GB iPhone usage.

wozniak is a boob.

sure there's a compiler for 6.2. the 6.2 IDO installs a compiler. what am i missing?

welp, i have three CD's i also loaded on 6.2, IDL, IDF, and IDO. at least that's what i marked on the CD's . i didn't have originals.

so what do you suppose i have here? after i load them i have full functioning compilers. i don't have a machine up and running at the moment to check the contents. oh well... what's in a name anyway, or in this case an abbreviation.

thanks joe! it was pretty confusing looking at the pile of cd's i had for 6.2. sadly i have no remaining use for them.

oh hamei! could it be true?!

http://searchdatacenter.techtarget.com/news/article/0,289142,sid80_gci1508584,00.html

Disney Sea!