| PLEX86 | ||
|
First | Previous | Next | Last Where should the type information be: in tags and descriptors 414 Typical implementations require a single memory bit for a fixed number of memory bytes to indicate whether an item is... Where should the type information be: in tags and descriptors 415 That is almost entirely sheer incompetence - and it is not just SPARC, but almost every RISC designer and... Where should the type information be: in tags and descriptors 416 Dan, Thanks for the Mondrian reference. I am not certain what you mean about "flipping protection attributes". I agree that protection ought to be done at an object level and not at a page or... Where should the type information be: in tags and descriptors 417 Here's an example of what I'm driving at (using Ada syntax, but the same applies to many other languages): type... Where should the type information be: in tags and descriptors 418 Aw heck, I'll byte too :-) The first time I saw this, circa perhaps 1970, it was some CAD data interchange... Where should the type information be: in tags and descriptors 419 system's C. That must have been fun as long as you avoided the alligators. Right. :-). That's when my word, thingie, helps a lot when discussing aspects. If I... Where should the type information be: in tags and descriptors 420 jmfbahciv) writes: A good suggestion. In fact, I'm in the process of reworking the programs in our system to convert existing binary files to ASCII format. In the bad old days, with slower machines... Where should the type information be: in tags and descriptors 421 Heh heh ... giggle. There certainly are some potentially very serious issues as more and more "stuff" gets more and more connected. My current concerns run more toward some of the... Where should the type information be: in tags and descriptors 422 that is for gov. work. there was a situation involving industrial espionage and theft of product secrets. there... Where should the type information be: in tags and descriptors 423 snip decimal discussion Prime 50-series machines are multics-like segmented machines. They have several addressing modes; but in all cases you have to handle segments of 64k 16-bit words. There are a... Where should the type information be: in tags and descriptors 425 The C and C++ compilers haven't been proven correct either. That doesn't make any of these compilers useless. It's certainly the case that a bug in a compiler *could* render a bounds checking feature... Where should the type information be: in tags and descriptors 428 Usually there will be an operator that will let you get at the bits of any type to inspect them. When generating numbers, usually one is allowed to put numbers together as... Where should the type information be: in tags and descriptors 429 Bit field operations may be needed for all data types. Tags probably get ignored for these. In the Burroughs large system architecture, anyone can write a... Where should the type information be: in tags and descriptors 430 On Fri, 08 Apr 2005 15:23:57 +1200, Brian Boutel I also would love to read it again; I may even have some of... Where should the type information be: in tags and descriptors 431 This is one of those religious arguments that are very hard to settle rationally: - the Unix-TOPS-10 argument: Every file... Where should the type information be: in tags and descriptors 432 the imps significantly increased the entry level costs for connecting to the arpanet. furthermore ... with the imps they had a homogeneous network... Where should the type information be: in tags and descriptors 433 The complaints about ODS-RMS are red herrings. The real complaint here is that the tools on a particular OS weren't designed to do what... Where should the type information be: in tags and descriptors 434 Still fighting the DECsystem 10-20 versus VAX battles? RMS - the Record Management System - doesn't particularly care what is in the file, unless it is told to impose some particular... Where should the type information be: in tags and descriptors 435 Sigh! I'm not talking about a file on the system. I'm talking about a file system that is arranged based on RMS. IIRC, you're too young. :-) Exactly! That is precisely the... Where should the type information be: in tags and descriptors 436 B ? Why B instead of U ? +--------------- I forgot. (It *was* back in 1965, after all.) I *think* it had something to do with the kind of tape drive... Where should the type information be: in tags and descriptors 437 Eh? Would it help to know that I wired adding machines? Or worked on 5-bit KSR's and wrote dialed line protocol code for Telex? Or was once a... Where should the type information be: in tags and descriptors 438 No, I'm not talking about chronological age but DECage. Until you know how the work evolved, you can't... Where should the type information be: in tags and descriptors 439 Want the long list or the short one? Here are some that I know about for certain, various time frames from 1960 to 1980. DOS, DOS, CTOS... Where should the type information be: in tags and descriptors 440 Well ... um ... no ... it's not that simple. When someone says "transfer a file from one system to another", they didn't really tell me enough. If the goal is... Where should the type information be: in tags and descriptors 441 The successful Reiserfs is a database pretending to be a filesystem; even moreso with version 4. What's good about it... Where should the type information be: in tags and descriptors 442 Not posted to the principals, who know this, but to people not familiar with these technologies. Please note that none of that makes such breaches impossible. To... Where should the type information be: in tags and descriptors 443 Edward A. Feustel memory be Windows, recoded, more Porting Linux to a new architecture is something that has occurred many times. Of course, in one of the threads on this topic... Where should the type information be: in tags and descriptors 444 That wouldn't have flown. The managers with the money (not necessarily the IT PHB) was... Where should the type information be: in tags and descriptors 445 Yep. a happen and I don't see why we would undercut our profit makers. Note that I don't understand much about this stuff. But DEC (logically) went from providing timesharing to single-task... Where should the type information be: in tags and descriptors 446 Good to hear from you. What's happened with computers since 1983 is that there are fewer and fewer large central systems, and more and more work is done on... Where should the type information be: in tags and descriptors 447 The innovator's dilemma" ... It is not so much «often blindsided» but I believe more like ''deliberately ignored''. Some people suspect that many company decisions are taken primarily with... Where should the type information be: in tags and descriptors 448 Exactly. The small computer were bought from the same manufacturer that sold them the main frame. A lot of this had to do with staying with a... Where should the type information be: in tags and descriptors 449 In this case, the TOPS-20 system was brought in because they were already familiar with DEC from... Where should the type information be: in tags and descriptors 450 systems Sigh! I'm not trying to declare that this was the way all of DEC's biz went. I am claiming that most of it went this way. Since you're talking about -20 and 11-70... Where should the type information be: in tags and descriptors 451 Neither was our niche. One of our problems was that we were ignoring our niche and trying to be something we weren't. And declaring that VMS is the one, and only... Where should the type information be: in tags and descriptors 452 vm370-cms contribution to vms. in the early 70s, customers were buying up vm370-cms and the development group was growing like mad. the group had first absorbed... Where should the type information be: in tags and descriptors 453 of course, endicott complained long & loud ... and finally it was decided that endicott could pick up responsibility for vm370 ... however all the burlington people still had to move to... Where should the type information be: in tags and descriptors 454 The "mongolian horde" technique (aka "army of golems"). If you can make it work at all, the best quality you can hope for is "adequate". IBM had better success with... Where should the type information be: in tags and descriptors 455 On Thu, 21 Apr 2005 17:30:58 +0200, Jan Vorbrüggen Were they the same clock speed? Now, my experience with performance is largely limited to PL-I code and ISTM... Where should the type information be: in tags and descriptors 456 Just a data point about what was known at the time. After the May 17th cancellation of the KL10 followon we had a session with beer and pizza; this was the friday... Where should the type information be: in tags and descriptors 457 That's correct, and at the same time it is correct that «Bell wasn't allowed to... Where should the type information be: in tags and descriptors 458 The 32:16 was a lovely piece of kit - even had a fairly usable menuing system over Unix, and a word processor that looked a lot like Wang's dedicated WP systems... Where should the type information be: in tags and descriptors 459 I think you have never seen an embedded system of the era. What do you think the target market was for... Where should the type information be: in tags and descriptors 460 On Thu, 14 Apr 2005 20:12:15 -0700, Lawrence Statton N1GAK-XE2 Very true, but not that surprising, under the circumstances. :-) They certainly... Where should the type information be: in tags and descriptors 461 Micheal H. McCabe) writes: IIRC VS-9 was originally called VMOS (Virtual Memory Operating System) when RCA had it. When Univac took it over, the new name VS-9 was part line, but I did... Where should the type information be: in tags and descriptors 462 I think that I'm confused about the Series 80... I was remembering a list of systems that... Where should the type information be: in tags and descriptors 463 there was this joke in the early MVS time-frame that CMS had a 64kbyte MVT simulator (built into the... Where should the type information be: in tags and descriptors 464 it depends when you are tallking about ... late 70s and continuing into the 80s, there was increasing bloat ... with more and more code migrating to... Where should the type information be: in tags and descriptors 465 On Fri, 08 Apr 2005 00:33:22 GMT in alt.folklore.computers, Peter More comparable in basic functionality and approach to TOPS-10-20; but with full protection supported so that production users... Where should the type information be: in tags and descriptors 466 Eh? It was perfectly usable from line-mode terminals, as was MVT-MVS, and I used it that way. The majority of the evolution has been in the mindsets of... Where should the type information be: in tags and descriptors 467 Nick Maclaren In my recollection, it worked okay on HDX IBM terminals like the 2741, I don't recall having a favorable... Where should the type information be: in tags and descriptors 468 do. 3270. behind I did try ZED briefly but probably not enough to be a 1st DAN black belt, whereas with... Where should the type information be: in tags and descriptors 469 Hmm. I have done some ergonomic analysis of that, and my conclusions are that, yes, it is... Where should the type information be: in tags and descriptors 470 Nick Maclaren are would not (Sorry Nick, I'll get to your point later. I'm really replying to two separate but related items here.) Actually, the 3270 interface was an... Where should the type information be: in tags and descriptors 471 very early in rexx cycle (when it was still called rex and before it was released) ... i wanted to demonstrate the usefulness of rex as not... Where should the type information be: in tags and descriptors 472 so one of the CP source enhancements indirectly arose from when i was originally doing cp67 pageable kernal code and trying to figure out the... Where should the type information be: in tags and descriptors 473 That was my point. The majority of the evolution has been the fact that one can put a system in one's home....and now anywhere. Did I write that... |
|||||