Actually it is fairly easy to get a kit car or a complete home built car certified in the UK. A friend has done two. It helps if the basic frame comes from a real car though. However, his conversion was quite radical (making a three wheeler out of a Mini subframe) and it was certified.
Unfortunatelly, you see a couple of 'jets' at the rear of the car that stick out sideways. The inspection definitely doesn't like sticking out bits that may cause problems with other vehicles or pedestrians.
I don't think I ever had a major problem with SYSGEN. It seemed to work ok most of the time with me and definitely was easier than most versions of Win until Win2K.
Digital really screwed up with their earlier IP support under VMS. It seems to work ok now, but rgrettably much of the port seems to have been done by people who didn't understand VMS well enough or the Unix implementation layer.
I take issue with what you say on the I/O. The problem is that few people worked out that in VMS, an I/O operation is expensive so it is advqntageous to transfer more than a byte at a time. I agree that the checking and logging costs, but how often did you have to do an ANALYZE/DISK/REPAIR on VMS? Even on a disk that was cluster mounted, the files seemed quite safe since VMS V3.1.
RMS is great too, as long as you use it and don't try to layer another file system on top of it.
This and VMS clusters is why some people I know can't get away from it yet. All of this could be implemented under Linux (roll your own file system - no worries). The trouble is that management is worried about large scale systems programming, they want a vendor to do it (and be blamed if things go wrong).
Yes, the PL/1 and VAX C compilers used the CODEGEN project which had the idea of using a common compiler backend and to make it responsible for optimisation, etc. I *really* don't understand why because I put some VAX Debug Symbol Table (DST) support into GCC and that worked fine. What I couldn't do was to fix the bugs in the VAX debuggers C language module (it does the expression and address parsing).
I would disagree with you about RMS, but then I would, having used it to coordinate shared access to indexed files across processes and a cluster. The only solution under any Un*x system is to use a DBMS. Oh and recovery unit journalling, you could even have that too! The end result is a lot faster than any DBMS.
The oneness applied to RMS as well, whichever language you used, you could always access an RMS file. If you really didn't want RMS, you could just open a file on a block level and DIY, which what many DBMS systems did.
I'm curious as to why you didn't like Cutler's systems. RSTS/E was one gigantic hack and proved as difficult as RSX-11D to support (as reflected in the prices). The M exec was lightweight and was used as the basis of one of the most successful healthcare systems of all time (MUMPS). It was a building block rather than a solution in its own right which was it was much loved by solution providers. I have seen steel mills, ATC systems, chemical plant control systems all based around the 11 and RSX-11M/S.
M support for paged memory (necessary for the PDP-11/60 and 70) was officially opposed by management because of the RSX-11D system (similarly named but no relation) had the place at the top of the range. Cutler implemented the changes in a weekend "for in-house debugging purposes because Digital had a lot of 11/60s around at one stage". The hack became known outside (the customers had the Exec source code and the SYSGEN tool so it was obviously there) and Digital was pressed to support it. Towards the end RSX had shared libraries, I and D space support and many other neat ideas (including a modularised exec). Many of these concepts didn't travel again to VMS until comparatively recent times.
Whilst Cutler was a good exec 'hacker', I guess he had problems in larger teams and this is perhaps why NT sucks so much. Many of the issues with NT seem to come down from weak leadership, leading to the API of the month competition. Note that the original NT design had the GUI running in user-space. It was too slow, so MS moved it to kernel space, bugs and all, which then haunted NT up until Win2000.
Largely, yes. Some of their stuff, frankly, sucked. For example, the early implementations of PL/1 and VAX/C. In the latter case, we just used GCC for VAX/VMS and it worked fine. The docs were excellent and unlike MS, there were very few really internal APIs and they weren't being revised every six months.
And it is still stable which is why it is being used for electronic trading.
This is why the largest electronic derivatives exchange in the world runs on VMS. Many other exchanges also use VMS. They do so for a reason, it takes on a bundle of work and doesn't die. If you have redundant hardware, it will stay up for ever, just failing over between hardware when it craps out.
Incidentally, Cutler started by writing RSX-11M then 11M+, a 16-bit operating system. He then went onto writing VMS and later the Digital PL/1 compiler before he left.
Digital got very little from MS apart from the promise to use their hardware platform for NT. The Windows API definitely has no relation to any of the APIs on VMS although some bits may be similar because of the former Digital engineers.
As the for command language, the original DOS/CPM commands derived from another 16-bit Digital operating system, RSTS/E. Both RSTS/E and M+ eventually started supporting Digital Command Language (DCL) which became fully developed under VMS (much like a Unix shell). The file types go back to the RSTS/E and RSX days.
The version numbers that you complain about are a feature of the VMS file system. They allow you to keep a few old versions of files around easily so you always have the possibility to revert to a previous version.
They memory manager is not particularly slow unless there is a high demand for memory and not enough physical memory available, and even Linux has problems there. The real issue of VMS as a platform is the overhead associated with process creation, now partly circumvented with threads.
Even in 88 all you have to do was to enable the secure attention logon. You then got the logon prompt with a break key and nothing could intercept that.
Actually it was remarkable easy to set up security on VMS. The real issue was monitoring the security alarms.
Most of the hacks were through social engineering. The others were due to imperfect parameter checking. As the system matured, it got even more tight on the hecks and most of the holes disappeared.
Just hunt around for references to VMSclusters and the Distributed Lock Manager. There are attempts at copying both but they really aren't as well implemented. SMP was also very good on VMS. The exec (kernel) of VMS was a nvery neat piece of engineering which was positively anal about parameter checking, so not a lot went wrong that way.
The problem is that although for many years, Digital didn't give sources, but they gave away source listings. Regrettably they stopped after VMS 4.5. However the system was exceptionally well documented and it was possible to write some neat hacks (for example, I did one to fetch somebody elses command line history buffer). It was far from as open as Linux. However, many old VMS people have fallen in love with Linux because it is so accessible.
Yes, Dave Cutler engineered the VMS Kernel and the NT Kernel. He was not responsible for all of VMS so could not bring all the knowhow with him (in the early days, Digital and Microsoft were good friends as NT was also targeted at their Alpha chip). In particular, he didn't bring along the file system or security concepts (Andy Goldstein was responsible for that) and he didn't bring along the distributed lock manager, which was essential to the smooth running of VMS Clusters.
I have one machine still on up2date and one on Red Carpet. The Red Carpet updater has been going for all of this year and in the beginning, it was dependency hell (reminded me of DLLs under Win). However since about Easter, it has been very stable. The only issue is if I trigger so many dependencies that/var is filled up with incomming rpms.
If you don't want beta, just don't subscribe to the beta releases. The other stuff seems fine. This particular system is an RH7.1ish 2.4.19 kernel with Ximian Gnome.
The oage doesn't have anything about IOS/boot helper downloads. Well if you manage to get hold of the code legally, running the code on a non-CISCO platform is kind of interesting as an academic exercise.
On of the original principles established back when IBM was king is that if you built a workalike, they still must sell you the software. This is not Warez, Crackz or anything else, this getting fair use, as long as you legally source PIX.
There may well be, but check out Despair for the perfect antidote. After working alongside and suffering from the bs emerging from the mouthes of Management Consultants, I am in frank admiration for how much can be paid for so little.
It takes too long. A while back before the infitada (either of them) I was diving off Eilat. The security interrogation on the way back was so invasive, that they had no chance to X-ray us or put us through the metal detector as the flight would miss its slot.
It seems one of the main techniques used by the interrogators on this and a previous visit to Israel was to deliberately provoke people and to see their reaction. If you travel with a companion, you will be cross-checked by interviewing you both independently.
Some of this checking is done by El Al, some by IDF people. Either way, it represents a very long check-in and a massive investment for the extra staff. Neither of which is very economic.
If someone can come up with an alternate way to ensure passenger safety, a lot of people would be interested. I just don't think mind-reading comes into it!!!
It is more complicated, remember LAME aint an MP3 encoder!. Technically LAME is an encapsulation of and patch to specimen source from the Frauenhofer Lab. This code may not be sold (a problem for people selling dists) but it is certainly possible to make it available for free download.
We would like to reassure the poster that a dedicated group of software developers are busy tring to put the latest of Internet Explorer features into Mozilla. High on the list are the Javascript vulnerabilities thast you all know and love.
If you would like to help make Mozilla truely IE compatible, please contact us to make it happen!!!
I'm sure that more than a few CEO's of listed corporations would qualify. Someone once said about their approach to solving crimes was to follow the money. These guys tend to be close to the feeding trough and certainly have an interest in overpromoting their companies to shareholders.
Misteaks (sic) in Email addresses cause more problems than than with postal addresses. With postal addresses, the postal service does a remarkable job of sorting out ambiguous delivery instructions. If you screw-up an Email address, it gets bounced.
In any case, the contact info for many organisations now comes from their web pages. For example, if I want to contribute money to the German Red Cross for their relief work for those caught out by the flooding, then just look them up on the web, their address is there, as well as how to contribute (incidentally, a good cause as nature can outdo Osama every time).
Misteaks (sic) in Email addresses cause more problems than than with postal addresses. With postal addresses, the postal service does a remarkable job of sorting out ambiguous delivery instructions. If you screw-up an Email address, it gets bounced.
In any case, the contact info for many organisations now comes from their web pages. For example, if I want to contribute money to the German Red Cross for their relief work for those caught out by the flooding, then just look them up on the web, their address is there, as well as how to contribute (incidentally, a good cause as nature can outdo Osama every time).
Many stores still don't sell region-free DVD players.
WHat is remarkable about it isn't what is being done, but who is selling it. HMV is a record label and was part of the EMI Group until 1998. EMI was also a film distributor in the UK. What interested me is that HMV do not seem to be bothered about the "party-line".
Yes you find my web page via Google, Altavista, Yahoo or whatever, great. Ok, you bookmark it, but how can you tell someone else about the page in meatspace oir over the telephone? xyz is much shorter and to the point.
I have been involved with a couple of non-profits with web sites. Both are of reasonable size and we often get telephone inquiries. It is much easier to say to somebody over the phone "check out www.xyz.org" than some horribly long name.
Very good point, but sorry that is what some non specialist computer users believe. They want to be able to type www.insert organisation here.org. We have seen incidents where a UK charity forgot to go for a.org (they had.org.uk). They then ended up in a dispute with a nasty little specimen who owned the.org and dirverted it to porn-sites. They don't really need the.org, but because the owner of the.org (who wanted to sell it) diverted the address, it became important to own that domain, because of all the people who didn't know the full address.
Yes, perhaps it would be better if we all had domain names without meaning and then relied on indexing services. Great, but how do I find that web site again? Bookmarking is great, but it only works on one computer. How can I tell you to check out www.643sda453fgasdf.org or would you rather I told you to check out www.xyz.org? Especially if xyz was a reasonable form of the name.
Final point, I hope I catch up with the mod of the poster as troll in m2. Tps12 makes a very good point, he isn't just stiring things.
Just think, it would be one heck of a plus to send the solution back in time with a quick hint to post it on "/.". Perhaps it is because it didn't happen and the usual trolls got there, that we can say that time-travel doesn't exist.
Slashdot Mirror
Unfortunatelly, you see a couple of 'jets' at the rear of the car that stick out sideways. The inspection definitely doesn't like sticking out bits that may cause problems with other vehicles or pedestrians.
Digital really screwed up with their earlier IP support under VMS. It seems to work ok now, but rgrettably much of the port seems to have been done by people who didn't understand VMS well enough or the Unix implementation layer.
I take issue with what you say on the I/O. The problem is that few people worked out that in VMS, an I/O operation is expensive so it is advqntageous to transfer more than a byte at a time. I agree that the checking and logging costs, but how often did you have to do an ANALYZE/DISK/REPAIR on VMS? Even on a disk that was cluster mounted, the files seemed quite safe since VMS V3.1.
RMS is great too, as long as you use it and don't try to layer another file system on top of it.
This and VMS clusters is why some people I know can't get away from it yet. All of this could be implemented under Linux (roll your own file system - no worries). The trouble is that management is worried about large scale systems programming, they want a vendor to do it (and be blamed if things go wrong).
Yes, the PL/1 and VAX C compilers used the CODEGEN project which had the idea of using a common compiler backend and to make it responsible for optimisation, etc. I *really* don't understand why because I put some VAX Debug Symbol Table (DST) support into GCC and that worked fine. What I couldn't do was to fix the bugs in the VAX debuggers C language module (it does the expression and address parsing).
The oneness applied to RMS as well, whichever language you used, you could always access an RMS file. If you really didn't want RMS, you could just open a file on a block level and DIY, which what many DBMS systems did.
M support for paged memory (necessary for the PDP-11/60 and 70) was officially opposed by management because of the RSX-11D system (similarly named but no relation) had the place at the top of the range. Cutler implemented the changes in a weekend "for in-house debugging purposes because Digital had a lot of 11/60s around at one stage". The hack became known outside (the customers had the Exec source code and the SYSGEN tool so it was obviously there) and Digital was pressed to support it. Towards the end RSX had shared libraries, I and D space support and many other neat ideas (including a modularised exec). Many of these concepts didn't travel again to VMS until comparatively recent times.
Whilst Cutler was a good exec 'hacker', I guess he had problems in larger teams and this is perhaps why NT sucks so much. Many of the issues with NT seem to come down from weak leadership, leading to the API of the month competition. Note that the original NT design had the GUI running in user-space. It was too slow, so MS moved it to kernel space, bugs and all, which then haunted NT up until Win2000.
And it is still stable which is why it is being used for electronic trading.
This is why the largest electronic derivatives exchange in the world runs on VMS. Many other exchanges also use VMS. They do so for a reason, it takes on a bundle of work and doesn't die. If you have redundant hardware, it will stay up for ever, just failing over between hardware when it craps out.
Incidentally, Cutler started by writing RSX-11M then 11M+, a 16-bit operating system. He then went onto writing VMS and later the Digital PL/1 compiler before he left.
Digital got very little from MS apart from the promise to use their hardware platform for NT. The Windows API definitely has no relation to any of the APIs on VMS although some bits may be similar because of the former Digital engineers.
As the for command language, the original DOS/CPM commands derived from another 16-bit Digital operating system, RSTS/E. Both RSTS/E and M+ eventually started supporting Digital Command Language (DCL) which became fully developed under VMS (much like a Unix shell). The file types go back to the RSTS/E and RSX days.
The version numbers that you complain about are a feature of the VMS file system. They allow you to keep a few old versions of files around easily so you always have the possibility to revert to a previous version.
They memory manager is not particularly slow unless there is a high demand for memory and not enough physical memory available, and even Linux has problems there. The real issue of VMS as a platform is the overhead associated with process creation, now partly circumvented with threads.
Even in 88 all you have to do was to enable the secure attention logon. You then got the logon prompt with a break key and nothing could intercept that.
Most of the hacks were through social engineering. The others were due to imperfect parameter checking. As the system matured, it got even more tight on the hecks and most of the holes disappeared.
The problem is that although for many years, Digital didn't give sources, but they gave away source listings. Regrettably they stopped after VMS 4.5. However the system was exceptionally well documented and it was possible to write some neat hacks (for example, I did one to fetch somebody elses command line history buffer). It was far from as open as Linux. However, many old VMS people have fallen in love with Linux because it is so accessible.
Yes, Dave Cutler engineered the VMS Kernel and the NT Kernel. He was not responsible for all of VMS so could not bring all the knowhow with him (in the early days, Digital and Microsoft were good friends as NT was also targeted at their Alpha chip). In particular, he didn't bring along the file system or security concepts (Andy Goldstein was responsible for that) and he didn't bring along the distributed lock manager, which was essential to the smooth running of VMS Clusters.
If you don't want beta, just don't subscribe to the beta releases. The other stuff seems fine. This particular system is an RH7.1ish 2.4.19 kernel with Ximian Gnome.
On of the original principles established back when IBM was king is that if you built a workalike, they still must sell you the software. This is not Warez, Crackz or anything else, this getting fair use, as long as you legally source PIX.
There may well be, but check out Despair for the perfect antidote. After working alongside and suffering from the bs emerging from the mouthes of Management Consultants, I am in frank admiration for how much can be paid for so little.
It seems one of the main techniques used by the interrogators on this and a previous visit to Israel was to deliberately provoke people and to see their reaction. If you travel with a companion, you will be cross-checked by interviewing you both independently.
Some of this checking is done by El Al, some by IDF people. Either way, it represents a very long check-in and a massive investment for the extra staff. Neither of which is very economic.
If someone can come up with an alternate way to ensure passenger safety, a lot of people would be interested. I just don't think mind-reading comes into it!!!
It is more complicated, remember LAME aint an MP3 encoder!. Technically LAME is an encapsulation of and patch to specimen source from the Frauenhofer Lab. This code may not be sold (a problem for people selling dists) but it is certainly possible to make it available for free download.
If you would like to help make Mozilla truely IE compatible, please contact us to make it happen!!!
I'm sure that more than a few CEO's of listed corporations would qualify. Someone once said about their approach to solving crimes was to follow the money. These guys tend to be close to the feeding trough and certainly have an interest in overpromoting their companies to shareholders.
In any case, the contact info for many organisations now comes from their web pages. For example, if I want to contribute money to the German Red Cross for their relief work for those caught out by the flooding, then just look them up on the web, their address is there, as well as how to contribute (incidentally, a good cause as nature can outdo Osama every time).
In any case, the contact info for many organisations now comes from their web pages. For example, if I want to contribute money to the German Red Cross for their relief work for those caught out by the flooding, then just look them up on the web, their address is there, as well as how to contribute (incidentally, a good cause as nature can outdo Osama every time).
WHat is remarkable about it isn't what is being done, but who is selling it. HMV is a record label and was part of the EMI Group until 1998. EMI was also a film distributor in the UK. What interested me is that HMV do not seem to be bothered about the "party-line".
I have been involved with a couple of non-profits with web sites. Both are of reasonable size and we often get telephone inquiries. It is much easier to say to somebody over the phone "check out www.xyz.org" than some horribly long name.
Yes, perhaps it would be better if we all had domain names without meaning and then relied on indexing services. Great, but how do I find that web site again? Bookmarking is great, but it only works on one computer. How can I tell you to check out www.643sda453fgasdf.org or would you rather I told you to check out www.xyz.org? Especially if xyz was a reasonable form of the name.
Final point, I hope I catch up with the mod of the poster as troll in m2. Tps12 makes a very good point, he isn't just stiring things.
Good way of making money quickly. Of coursem your time machine probably breaks SEC insider-trading rules.
Just think, it would be one heck of a plus to send the solution back in time with a quick hint to post it on "/.". Perhaps it is because it didn't happen and the usual trolls got there, that we can say that time-travel doesn't exist.