Sometimes you want to back the whole thing up. In the old days we would do a full backup a week and then daily incrementals. In those days a big disk was 80MB and we just used 6250bpi half-inch mag tape.
Actually, once people start playing with decompressed video (i.e., home or semi-pro editing), then it it isn't unusal to have massive files knocking around and nowhere to put them.
No, Microsoft have been extremely poor engineers. Buffer exploits and the problems of null terminated strings were a known issue when when Outlook was developed.
Please remember that the 'preview' feature in Outlook is enabled by default so you can be vulnerable without explicitly downloading anything. I don't know about you but don't you find that pretty scary?
I worked with a computer manufacturer about 20 years ago and in all our design documents for software, we had an explicit section addressing security implications. We had to think carefully about features that would allow the execution of arbitrary code. Microsoft have made their money by being irresponsible engineers. It costs money to do things properly so we get stuff from them that crashes and has secutity holes.
To come back to your car example, it is a bit like Ford saying, we built it - the prototype went twice round a test track and now lets sell it.
If you look around, you will discover that there are a number of "Reverse Engineering" tools for working with source code. When you dive into someone elses codebase, it can be challenging to work out exactly what is happening, even when the documentation is good (hah!!!!). You still need to be able to extract the design - an interesting problem for event driven aps.
Is you have source code, reverse engineering is legal, but the idiots on the hill have forbidden us from doing this with binaries. Many issues are similar though.
I should qualify this by saying that I have been ekeing out a living trying to support a legacy ap the size of the Linux kernel but with much poorer structure and documentation.
It just sems a pity that you can't produce a series of binary patches to XP so that the rest of us could use this. It certainly would be a great toy to have for developers.
In any case, well done to you and your colleagues. My download (wget not the Bittorrent) is going slowly, so I haven't had a chance to play yet.
Yes, you can take any distribution but they need to include some assembler macros to replace instructions (I guess, PUSHF and POPF for one) and rebuild the system That is, it isn't quite the original distro anymore and the distro can't self build. Actually, this seems very much like plex86-lite's approach.
If the existing behavior of INtel kernel mode instructions when called from user mode was always consistent (i.e., a trap), then it would be *much* easier to emulate the instructions inside a user-mode VM.
All it takes is for Intel to provide a proper 'V' bit - but frankly, after all these years of architectural holes I do wonder.
It is true that their 'CVS' tree isn't - it s a BK tree with all the flames seen on the kernel lists. However the ISO contains their complete 1.0 sources.
As for the BK license - you can't use it to develop a competing project but if you separate your work via BK from the work you do on a.n.other version control system, then nobody is going to complain too much.
I know you are being funnz but it raises an interesting point. If you have access to the XP source code through an academic license, does this mean that you are 'tainted' from contributing to the Linux kernel?
For example, in earlier days, it was relatively easy to get hold of commercial OS sources without selling your soul (or signing an NDA). For example, I used the source code to write a couple of neat hacks which were available withing the user group.
Are these guys now going to have problems after they have seen at least the lowest levels of XP (I guess, the Hardware Abstraction Layer).
They used Gnutella, because they needed to use a protocol that could be extracted without legal problems from the source code. Kazaa have already shown themselves to be litigatious. Their code has been reverse engineered in the form of Kazaa-lite, but the authors wanted to use something that wouldn't open them up to problems under the DMCA (yes, ironic isn't it). ED2K would possibly have been a more popular protocol and also available throught the public domain clients like eMule.
To publish something that relies on reverse engineering puts you open to charges under the DMCA. Reverse engineering PD software is easy (you have the source). Reverse engineering a closed source program isn't exactly impossible, look at Kazaa-lite, for example. However there are other PD clients to more popular networks such as eMule for ed2k (no disassembly required).
So you can still say that the RIAA's IP address is sharing movies and the MPAA's IP address is sharing MP3s for other networks.
I didn't mention the PIREPS, because these weren't apparently so interesting for medium or longer-term forecasting - unless they gave a section of atmosphere across many altitudes (ideally via a weather balloon). What I heard was the most interesting was around sea-level because it was the interface between sea and air where a lot of interesting things happen (like hurricanes brewing). The only long-term pheonomena that they wanted at altitude were the jet streams.
Oh an satellites were great, but only for showing what was happening 'on-top'.
Although the reporting stations aren't every mile. That would be kinda overkill I think.
Firstly I'm not a weather man, but a long time ago I know some people who did do that kind of thing (well they were more programmers than meteorologists), but they were always crying out for more data. They didn't want the butterfly whos wings are setting off all those hurricanes but they definitely want finer grained data.
The big problem is that a lot of the weather happens at sea. Apparently many ships have automatic reporting but they are mostly in the sea-lanes leaving great holes elsewhere. These gaps are why the accuracy falls off over a week.
The weather people said they wanted idealy a 10Km grid, but at sea they are often lucky to get 1000Km.
You forgot the use of a file system like Rubber Hose to provide deniabile encryption.
Remember that you can't avoid giving the Feds your keys, and scrubbing the disk is an admission of guilt. This is the really scary thing.
The above file system was designed for use by human rights activists in third-world dictatorships (or the UK). It now seems to be appropriate for the US as well. It seems particularly useful if you are a journo with stuff like the dirt on the whitehouse or no. 10 (i.e. a 'source') then given the access that governments have, you really don't want to store it anywhere where it can be got at.
It seems a shame that very little work has been done on this system in recent times, there may be others though.
Do you know what the word is about patch integratiuon. Although there are fixes, many of the patches are frozen out as they alter functionality on w.6. Will they end up in 2.6.1? I guess kgdb not, as Linus hates kernel debuggerers - but the aio and so on would be *really* nice.
Before puting their investor's money into a company, a VC company should perform a due dilligence evaluation. If the risks were not fully examined and addressed, then the VC company can be sued by their investors.
VC is always a bit of a gamble, since 2001, a very large gamble. However, it smells like they didn't examine SCO's claims very well. They were undoubtedly hoping for an exit via a trade sale to IBM but, it appears they have underestimated the reaction that "All your Unixes belong to us" has brought. They probably weren't even aware of the BSD settlement (maybe not Darl either).
Um, there have been a number of improvements to the scheduler which specifically address this sort of issue. Perfect, it won't be, but it will be a lot better than the 2.4 series kernel.
What I wouls really like is for Andrew Morton's MM patches to be adopted. They bring in proper asynchronous I/O support and that will eventually dramatically help response times (however only as utilities get rewritten to adopt this). However. the improvements to X responsiveness seem to be here now.
any substance that is designed or has the capability to cause death or serious injury
Not that whatver you say about intent, and the Jury is already in about the addictive qualities which have been designed into cigarettes. The point is that it is a substance that kills millions a year in the US alone.
I don't like cigarettes, but I do agree with you about the level of harm. However, it should be interesting to show how out of hand the DoJ is getting.
Something similar. I had taken an 11/23 for a project and installed RSX-11M. Regrettablz the system kept crashing as it had run out of pool (kernel dynamic memory).
I checked the meachine and it looked ok, but something was cuasing the interrupts to go to blazes and the pool was full of terminal buffers. Eventually I had found that some bright sprk at manufacturing has connected an internal loopback connector (not external) and that was causing the machine to crash.
I was working at Dec with a smaller 11, part of a special turnkey bankig system. We had overnight crashes for the same reason. Eventually, we negotiated that the cleaning staff would never touch red plugs.
Um, there is actually a lot of single-track railroad in India with very occassional passing points.
When the train is going the a/c isn't needed because the air blowing through the open doors and windows cools things down. OTOH, you can spend a lot of time waiting at the crossing points. Then it gets really hot.
A Law Enforcement Authority (LES) can gain a warrant to listen to a particular number. This is great with fixed lines, but next to useless for mobiles. Does Osama have a contract with an airtime reseller? He would do what the drug dealers do and get mobiles that are not on a contract or are stolen.
The subject of the surveillance then makes a phone call, but you don't know what number he is using - so your warrant with the Judges signature doesn't help much.
You may observe tge phone call but you can't get an intercept because even if you know the local BSE, it may be handling 16 calls simultaneously. Under such circumstancesm off air intercepts are the only simple solution. Even then you would need to determine which conversation you wanted (GSM uses TDMA to seperate calls on a particular frequency).
Buran flew once (properly, and into space). The vehicle was still being tested and life-support was incomplete. The thing is that when they landed the thing, they did it in cross-winds that are considered out operational parameters for the shuttle. NASA was, despite everything, quite impressed.
What I liked, is that you didn't need a ferry for Buran. You strapped on some gas turbines and it could transport itself from A to B. That really impressed a lot of people.
As long as there is recycling for plastics available, A CD is recyclable. The problem is that a CD isn't "clean" in that it usually has a label and the aluminium reflecting layer which must be separated so the plastic is pure.
Slashdot Mirror
Actually, once people start playing with decompressed video (i.e., home or semi-pro editing), then it it isn't unusal to have massive files knocking around and nowhere to put them.
we do need bigger backup media. HDs are usually 80GB plus, how do we back them up (particularly if the HD is full of ripped media)?
Please remember that the 'preview' feature in Outlook is enabled by default so you can be vulnerable without explicitly downloading anything. I don't know about you but don't you find that pretty scary?
I worked with a computer manufacturer about 20 years ago and in all our design documents for software, we had an explicit section addressing security implications. We had to think carefully about features that would allow the execution of arbitrary code. Microsoft have made their money by being irresponsible engineers. It costs money to do things properly so we get stuff from them that crashes and has secutity holes.
To come back to your car example, it is a bit like Ford saying, we built it - the prototype went twice round a test track and now lets sell it.
Is you have source code, reverse engineering is legal, but the idiots on the hill have forbidden us from doing this with binaries. Many issues are similar though.
I should qualify this by saying that I have been ekeing out a living trying to support a legacy ap the size of the Linux kernel but with much poorer structure and documentation.
It just sems a pity that you can't produce a series of binary patches to XP so that the rest of us could use this. It certainly would be a great toy to have for developers.
In any case, well done to you and your colleagues. My download (wget not the Bittorrent) is going slowly, so I haven't had a chance to play yet.
Yes, you can take any distribution but they need to include some assembler macros to replace instructions (I guess, PUSHF and POPF for one) and rebuild the system That is, it isn't quite the original distro anymore and the distro can't self build. Actually, this seems very much like plex86-lite's approach.
All it takes is for Intel to provide a proper 'V' bit - but frankly, after all these years of architectural holes I do wonder.
As for the BK license - you can't use it to develop a competing project but if you separate your work via BK from the work you do on a.n.other version control system, then nobody is going to complain too much.
For example, in earlier days, it was relatively easy to get hold of commercial OS sources without selling your soul (or signing an NDA). For example, I used the source code to write a couple of neat hacks which were available withing the user group.
Are these guys now going to have problems after they have seen at least the lowest levels of XP (I guess, the Hardware Abstraction Layer).
They used Gnutella, because they needed to use a protocol that could be extracted without legal problems from the source code. Kazaa have already shown themselves to be litigatious. Their code has been reverse engineered in the form of Kazaa-lite, but the authors wanted to use something that wouldn't open them up to problems under the DMCA (yes, ironic isn't it). ED2K would possibly have been a more popular protocol and also available throught the public domain clients like eMule.
To publish something that relies on reverse engineering puts you open to charges under the DMCA. Reverse engineering PD software is easy (you have the source). Reverse engineering a closed source program isn't exactly impossible, look at Kazaa-lite, for example. However there are other PD clients to more popular networks such as eMule for ed2k (no disassembly required).
So you can still say that the RIAA's IP address is sharing movies and the MPAA's IP address is sharing MP3s for other networks.
Oh an satellites were great, but only for showing what was happening 'on-top'.
The big problem is that a lot of the weather happens at sea. Apparently many ships have automatic reporting but they are mostly in the sea-lanes leaving great holes elsewhere. These gaps are why the accuracy falls off over a week.
The weather people said they wanted idealy a 10Km grid, but at sea they are often lucky to get 1000Km.
Remember that you can't avoid giving the Feds your keys, and scrubbing the disk is an admission of guilt. This is the really scary thing.
The above file system was designed for use by human rights activists in third-world dictatorships (or the UK). It now seems to be appropriate for the US as well. It seems particularly useful if you are a journo with stuff like the dirt on the whitehouse or no. 10 (i.e. a 'source') then given the access that governments have, you really don't want to store it anywhere where it can be got at.
It seems a shame that very little work has been done on this system in recent times, there may be others though.
Do you know what the word is about patch integratiuon. Although there are fixes, many of the patches are frozen out as they alter functionality on w.6. Will they end up in 2.6.1? I guess kgdb not, as Linus hates kernel debuggerers - but the aio and so on would be *really* nice.
VC is always a bit of a gamble, since 2001, a very large gamble. However, it smells like they didn't examine SCO's claims very well. They were undoubtedly hoping for an exit via a trade sale to IBM but, it appears they have underestimated the reaction that "All your Unixes belong to us" has brought. They probably weren't even aware of the BSD settlement (maybe not Darl either).
What I wouls really like is for Andrew Morton's MM patches to be adopted. They bring in proper asynchronous I/O support and that will eventually dramatically help response times (however only as utilities get rewritten to adopt this). However. the improvements to X responsiveness seem to be here now.
I don't like cigarettes, but I do agree with you about the level of harm. However, it should be interesting to show how out of hand the DoJ is getting.
I checked the meachine and it looked ok, but something was cuasing the interrupts to go to blazes and the pool was full of terminal buffers. Eventually I had found that some bright sprk at manufacturing has connected an internal loopback connector (not external) and that was causing the machine to crash.
I was working at Dec with a smaller 11, part of a special turnkey bankig system. We had overnight crashes for the same reason. Eventually, we negotiated that the cleaning staff would never touch red plugs.
When the train is going the a/c isn't needed because the air blowing through the open doors and windows cools things down. OTOH, you can spend a lot of time waiting at the crossing points. Then it gets really hot.
The subject of the surveillance then makes a phone call, but you don't know what number he is using - so your warrant with the Judges signature doesn't help much.
You may observe tge phone call but you can't get an intercept because even if you know the local BSE, it may be handling 16 calls simultaneously. Under such circumstancesm off air intercepts are the only simple solution. Even then you would need to determine which conversation you wanted (GSM uses TDMA to seperate calls on a particular frequency).
What I liked, is that you didn't need a ferry for Buran. You strapped on some gas turbines and it could transport itself from A to B. That really impressed a lot of people.
As long as there is recycling for plastics available, A CD is recyclable. The problem is that a CD isn't "clean" in that it usually has a label and the aluminium reflecting layer which must be separated so the plastic is pure.
However, I might strike through one or two clauses and add some of my own. They might not accept it, but it would be fun anyway.