Maybe thats because there wasn't much else to do? Its hard to come up with 30 stories a year that aren't repeats or copies of someone else's stories.
The origial Trek did push difficult issues such as birth control, eugenics and racial issues. Kirk kissing Uhura was a major risk for TV in the late 1960's
The flight magazine I get every month or so from CASA has had several examples of it over the past few years.
There were some serious issues with weather access that was a major factor in the Sydney to Hobart race that ended so badly a few years ago as well. That search and rescue operation alone cost more than the BOM's operation budget for the same year.
You don't get aviation weather unless you are properly signed up and they have an account to charge to. And its not cheap either. You would think for the amount they charge, they would get it right a bit more often.
Australia does this. The result is lots of dead pilots and boaters every year because they didn't pay the money to get the services they need. The result is that other people end up paying far more for everything since the gov't is being too cheap.
Years ago my boy scout troop used Geritol and it mostly worked well for most guys but there tended to be one that it didn't work for. It worked within reason as well. If you were too close to the very high density mosquito breeding grounds, you would get bit.
The only way to stop it is to get enough people to fund laws that explicitly stop them. The current situation is mostly that there isn't anything on the books specific one way or the other and a few companies are trying to swing that to their side and the opposition only seems to be stopping that, not swinging legislation all the way to the other side.
What states have real licensed professional software engineers? I'm working on my computer engineering license in the state of Missouri via the apprenticeship rules but I have to work an additional year under the guidance of a another licensed engineer in the field and I can't find one. The real problem is professional engineers I've worked for are all retired or no longer have much use of their minds any more.
At one time recently my father was one of only 6 licensed computer engineers in the state of Missouri. The problem is his training is in analog computers.
On my system the binary file contains the last time when the service started. That means a file in/etc gets written with every boot.
And yes I'm saying complexity is bad and we should stick with what works (and it isn't dos)
the Solaris start order has been wrong since they 1st used the term solaris.
I currently work as a team of 3 and I'm the point guy when junk hits the fan. I've been a member of much larger teams (nearly 100) and I'm always the point guy who gets called out to fix what can't be fixed. I also make it clear that when I go away there is no way they are going to contact me at all (Dive N Queensland!)
My way of doing things may be the old BOFH way but I've got a mailing list in a yellow book which has almost a dozen people who can fix problem on my systems with out ever seeing them in a reasonable about of time from 1st (unix) principals. Can your team?
Of course I've blown away the concept of net work storage (it doesn't work in the real word) and built systems that don't depend on it. I've been doing this for over a decade and my systems cope will all kinds of unexpected outages. My most basic rule is KISS.
BS. I buy a system from sub because of its reputation. If that reputation isn't correct, the box gets owned and I never buy their junk again. If they can't provide a simple command line tool to keep their systems from being owned, its junk. And I don't buy junk.
Brand new V100 out of the box from sun. Put on a network and given an public ip address and while other things were done. Soon it started probing every machine on the test network.
That should not happen. With my production sun boxes, I purge everything rpc related and comment out all kinds of crud in inetd.conf. The base install is just wrong.
What you claim has been repeated by several others so I guess you got your incorrect info from a reliable source:-)
Software could always be copyrighted in the US. You just had to print it out and send it to the copyright office. This was done at least in the 1960s. All that changed was the copyrightability of stuff like tapes and diskettes.
There was little "trade secret" stuff in Unix. They shared the source with so many universities and the early contracts didn't mention trade secrests.
You also seem to be confusing System V development with SVR4. Sys V started out as a logical extenuation of System III which was already having problems with the extensions that the Version 8 were trying to bring back into it. Then there was the version that ran the ESS phone switches and would also run on the new 3B2 line. That was around the mid 1980s. SVR2 on the 3b2 would page (not swap, no real vm but its hardware supported it) and its idea of a network was uucp. Sun started selling workstations into AT&T and someone got the great idea to mix the sys V core with the sun networking and thats what R4 was. It was a bit embarrassing for AT&T to have to use a sun workstation as a front-end for stuff like their pixel machine as well. Because if issues of "not invented here", both sun and at&t thought they could rewrite all of it and get rid of all the old code. That upset IBM and DEC and HP who then decided to do their own project too.
Of course my memory of the facts my be as clouded by time as everyone else's. AT&T was a huge bureaucracy at the time right after the breakup there were lots of groups with no real direction and there might have many reasons for any action they took and today no one will know which reason was the real reason.
Ok, so they mix make with init as well. It was done over 20 years ago (and the current init file format allows for this)
There is a binary file living in/etc that changes with every boot. If it is newer than the xml files, it doesn't get recreated. Its a sqLite file in fact. If you insert stuff in that file in the right spot, it gets run even if you never touch the xml code.
I've never had dependency problems but the 1st thing I do when I get s solaris box is rename the Sxx to a proper order and nuke most of the useless ones. Then I add a & that should have been there for the last decade that sun seems to have forgot (but AT&T didn't)
I've found some very interesting things to do to the new system that can mess up a box in a way that the current tool set won't even let you see what is wrong. It appears to be a script kiddies back door dream. Sorry but that level of crud isn't going on a production system I run. If Sun insists on svc, thats fine, there are other OSs out there.
It seems to me that every time something in IT gets reinvented, its at least 10x as complex and only provides a slight improvement on the old system. When those improvements cause the complexity to rise to the level that prevents rapid tracing, then I've always found that its time to dump the system and look for a simpler solution.
They guy never saw the SVR4 code... talk about a mess. AT&T had nice clean code that worked well was efficient but didn't do networking very well at all. So they hopped into bed with Sun who had real good networking stuff from BSD. The result was the two of them spawned SVR4. The read system call in the old unix was short and sweet and fit on a vt100 screen. The new one took pages even when printed out and didn't do anything new. It was a rewrite for the sake of a rewrite.
There are some very clever things in Unix that you don't notice till someone redoes them and turns them into a stinking heap. For example the new Solaris 10 services. It does what init and inetd does but needs a binary config file which it rewrites on boots and when it changes stuff (ala windows registry for unix). Having been way too deep on too many broken systems, I don't like binary files that change that are essential for my os to work. But this is progress...
I want to know where these companies have their gateways. For example if I'm using the service in London, then anywhere in the US is fine but form Australia, I need to be able to use a gateway in the San Jose area and from Africa I'll want a gateway close to MAE or CIX East.
Does anyone have a list of of the different VoIP providers and where their gateways are?
Text parsing isn't hard on a CPU unless you do it in way that requires a huge about of stack or memory. Sort of like xml (or TeX or lisp). Did the people whoe came up with XML ever read Knuth's or Wirth's books or even look at the reasons behind they way lisp does things?
dump is specific to the file system. This is why bsd had "dump" and solaris has "usbdump". The dump program should go through the in-memory image of the file system and dump each inode out in a sane way being careful to make sure only a checkpointed image is written. This means you have to have a deep understanding of the internals of the specific filesystem in order to write a dump program.
I don't use any file systems that don't have a proper dump command written for them but I like to keep my data.
Your talking about "secrets", not "Trade Secrets" which are different. An IP lawyer is going to ask what "Trade Secret" was published and won't find any.
The Apple and ][ booth used Atari trade secrets. For example the video interlacing was a trick that Atari used to keep from having to have dram refresh circuitry and some of the font drawing hardware is a combination of several Atari trade secrets.
The problem is unreleased stuff isn't a "Trade Secret". A trade secret is something that is patentable but the company chooses not to patent it because they think they can hide it from their competitors. New products that are going to be released a few weeks don't fit into that.
Apple spent the money on the 1st round of this suit because it may lead to the insider who released the info. I expect that it might have been released by someone in marketing that knows that a trade show is a nasty place to release new stuff because the only ones watching are your loyal customers. Preaching to the choir doesn't bring in converts and their new products purpose is just that. This leak got many more people to watch the announcements and that will help Apples Sales.
Its basic system theory. I can't know all the interactions between all the systems so I can't account for everything. The easy test is to schedule some downtime and tell the system to reboot. If all goes to plan the system is back up in 90 seconds with most server (or 5 minutes for a cisco router).
At work we have 2 nearly identical systems that can each cope with the entire load and they don't need to talk to each other except for non real time things like end of month reports. The reboot test is a great way to keep from getting bitten by stupid things like a change in openssh's dealing with/dev/random where a change in the startup sequence means there isn't quite enough random state in the system to prevent a deadlock.
How do you know that the disk label is still working? Most OS's won't let you read it (since its cached). There are many parts of modern hardware that are essential to booting but can't be accessed outside of the reset sequence. There are things like flash bios that you can't test from a live system and that perpetual problem with hard disks of "will it wake up next time?"
I've got a few outstanding bugs with cisco because their NAT/PAT stuff doesn't come up quite the same way as when its entered so the only way to know if a config is going to "stick" is to bring the thing up from a full reset state.
I agree that a sysadmin should be able to come up with a full deadlock state diagram for the system but when that graph has more than 1000 nodes on it, the only sure way is a 'halt' and hit the reset switch but even that doesn't test a full start from a power off state.
I'm an early adopter and I don't see anything I'm going to buy. My next computer purchase might be one of the $500 apples if they can get me one before I read a sucky review (like review of a cheap video chip in the new imacs). I don't need any more disk space. I'll buy a gig sd card when they are below $70 and not before since I've never used most of my current sd memory or my usb memory stick but having a gig of tiny memory would be cool for some stilly reason.
I don't need another mp3 player. In fact I've given away at least two and the ones around the house never get used. (but I'm going to hack one for underwater use if I can get the oregon sci replacement headsets).
So Mr toy makers... impress me or you won't see my money. Get me a postscript color laser printer for $200 or get me a 7 inch LCD touch screen that will work in a midwest summer in a car. I don't need fancy software unless its real cool and I'm not into security snake oil. I would by security dongles if you provided open source source code to talk to the thing but I'm installing your binaries on my box. I don't need bigger hard drives since I've got nearly.55tb I can't use right now (thanks sun!). Maybe I'm getting to old for the toys but I haven't seen anything real impressive in a while.
Slashdot Mirror
Maybe thats because there wasn't much else to do? Its hard to come up with 30 stories a year that aren't repeats or copies of someone else's stories.
The origial Trek did push difficult issues such as birth control, eugenics and racial issues. Kirk kissing Uhura was a major risk for TV in the late 1960's
The flight magazine I get every month or so from CASA has had several examples of it over the past few years.
There were some serious issues with weather access that was a major factor in the Sydney to Hobart race that ended so badly a few years ago as well. That search and rescue operation alone cost more than the BOM's operation budget for the same year.
You don't get aviation weather unless you are properly signed up and they have an account to charge to. And its not cheap either. You would think for the amount they charge, they would get it right a bit more often.
BOM subscriptions
Step 2 is dead people.
Australia does this. The result is lots of dead pilots and boaters every year because they didn't pay the money to get the services they need. The result is that other people end up paying far more for everything since the gov't is being too cheap.
Maybe in the windows world. Stack smashing got very well known in the unix world after the Morris worm from 1988.
Years ago my boy scout troop used Geritol and it mostly worked well for most guys but there tended to be one that it didn't work for. It worked within reason as well. If you were too close to the very high density mosquito breeding grounds, you would get bit.
The only way to stop it is to get enough people to fund laws that explicitly stop them. The current situation is mostly that there isn't anything on the books specific one way or the other and a few companies are trying to swing that to their side and the opposition only seems to be stopping that, not swinging legislation all the way to the other side.
What states have real licensed professional software engineers? I'm working on my computer engineering license in the state of Missouri via the apprenticeship rules but I have to work an additional year under the guidance of a another licensed engineer in the field and I can't find one. The real problem is professional engineers I've worked for are all retired or no longer have much use of their minds any more.
At one time recently my father was one of only 6 licensed computer engineers in the state of Missouri. The problem is his training is in analog computers.
On build 72 it was stored in a sqlite database which looks binary to me.
I'll leave it to the script kiddies to provide an example of where the current design is wrong.
On my system the binary file contains the last time when the service started. That means a file in /etc gets written with every boot.
And yes I'm saying complexity is bad and we should stick with what works (and it isn't dos)
the Solaris start order has been wrong since they 1st used the term solaris.
I currently work as a team of 3 and I'm the point guy when junk hits the fan. I've been a member of much larger teams (nearly 100) and I'm always the point guy who gets called out to fix what can't be fixed. I also make it clear that when I go away there is no way they are going to contact me at all (Dive N Queensland!)
My way of doing things may be the old BOFH way but I've got a mailing list in a yellow book which has almost a dozen people who can fix problem on my systems with out ever seeing them in a reasonable about of time from 1st (unix) principals. Can your team?
Of course I've blown away the concept of net work storage (it doesn't work in the real word) and built systems that don't depend on it. I've been doing this for over a decade and my systems cope will all kinds of unexpected outages. My most basic rule is KISS.
BS. I buy a system from sub because of its reputation. If that reputation isn't correct, the box gets owned and I never buy their junk again. If they can't provide a simple command line tool to keep their systems from being owned, its junk. And I don't buy junk.
Brand new V100 out of the box from sun. Put on a network and given an public ip address and while other things were done. Soon it started probing every machine on the test network.
That should not happen. With my production sun boxes, I purge everything rpc related and comment out all kinds of crud in inetd.conf. The base install is just wrong.
What you claim has been repeated by several others so I guess you got your incorrect info from a reliable source :-)
Software could always be copyrighted in the US. You just had to print it out and send it to the copyright office. This was done at least in the 1960s. All that changed was the copyrightability of stuff like tapes and diskettes.
There was little "trade secret" stuff in Unix. They shared the source with so many universities and the early contracts didn't mention trade secrests.
You also seem to be confusing System V development with SVR4. Sys V started out as a logical extenuation of System III which was already having problems with the extensions that the Version 8 were trying to bring back into it. Then there was the version that ran the ESS phone switches and would also run on the new 3B2 line. That was around the mid 1980s. SVR2 on the 3b2 would page (not swap, no real vm but its hardware supported it) and its idea of a network was uucp. Sun started selling workstations into AT&T and someone got the great idea to mix the sys V core with the sun networking and thats what R4 was. It was a bit embarrassing for AT&T to have to use a sun workstation as a front-end for stuff like their pixel machine as well. Because if issues of "not invented here", both sun and at&t thought they could rewrite all of it and get rid of all the old code. That upset IBM and DEC and HP who then decided to do their own project too.
Of course my memory of the facts my be as clouded by time as everyone else's. AT&T was a huge bureaucracy at the time right after the breakup there were lots of groups with no real direction and there might have many reasons for any action they took and today no one will know which reason was the real reason.
Ok, so they mix make with init as well. It was done over 20 years ago (and the current init file format allows for this)
/etc that changes with every boot. If it is newer than the xml files, it doesn't get recreated. Its a sqLite file in fact. If you insert stuff in that file in the right spot,
There is a binary file living in
it gets run even if you never touch the xml code.
I've never had dependency problems but the 1st thing I do when I get s solaris box is rename the Sxx to a proper order and nuke most of the useless ones. Then I add a & that should have been there for the last decade that sun seems to have forgot (but AT&T didn't)
I've found some very interesting things to do to the new system that can mess up a box in a way that the current tool set won't even let you see what is wrong. It appears to be a script kiddies back door dream. Sorry but that level of crud isn't going on a production system I run. If Sun insists on svc, thats fine, there are other OSs out there.
It seems to me that every time something in IT gets reinvented, its at least 10x as complex and only provides a slight improvement on the old system. When those improvements cause the complexity to rise to the level that prevents rapid tracing, then I've always found that its time to dump the system and look for a simpler solution.
They guy never saw the SVR4 code... talk about a mess. AT&T had nice clean code that worked well was efficient but didn't do networking very well at all. So they hopped into bed with Sun who had real good networking stuff from BSD. The result was the two of them spawned SVR4. The read system call in the old unix was short and sweet and fit on a vt100 screen. The new one took pages even when printed out and didn't do anything new. It was a rewrite for the sake of a rewrite.
There are some very clever things in Unix that you don't notice till someone redoes them and turns them into a stinking heap. For example the new Solaris 10 services. It does what init and inetd does but needs a binary config file which it rewrites on boots and when it changes stuff (ala windows registry for unix). Having been way too deep on too many broken systems, I don't like binary files that change that are essential for my os to work. But this is progress...
I want to know where these companies have their gateways. For example if I'm using the service in London, then anywhere in the US is fine but form Australia, I need to be able to use a gateway in the San Jose area and from Africa I'll want a gateway close to MAE or CIX East.
Does anyone have a list of of the different VoIP providers and where their gateways are?
Its not a logical step forward. Study lisp and learn why.
Text parsing isn't hard on a CPU unless you do it in way that requires a huge about of stack or memory. Sort of like xml (or TeX or lisp). Did the people whoe came up with XML ever read Knuth's or Wirth's books or even look at the reasons behind they way lisp does things?
dump is specific to the file system. This is why bsd had "dump" and solaris has "usbdump". The dump program should go through the in-memory image of the file system and dump each inode out in a sane way being careful to make sure only a checkpointed image is written. This means you have to have a deep understanding of the internals of the specific filesystem in order to write a dump program.
I don't use any file systems that don't have a proper dump command written for them but I like to keep my data.
Your talking about "secrets", not "Trade Secrets" which are different. An IP lawyer is going to ask what "Trade Secret" was published and won't find any.
The Apple and ][ booth used Atari trade secrets. For example the video interlacing was a trick that Atari used to keep from having to have dram refresh circuitry and some of the font drawing hardware is a combination of several Atari trade secrets.
The problem is unreleased stuff isn't a "Trade Secret". A trade secret is something that is patentable but the company chooses not to patent it because they think they can hide it from their competitors. New products that are going to be released a few weeks don't fit into that.
Apple spent the money on the 1st round of this suit because it may lead to the insider who released the info. I expect that it might have been released by someone in marketing that knows that a trade show is a nasty place to release new stuff because the only ones watching are your loyal customers. Preaching to the choir doesn't bring in converts and their new products purpose is just that. This leak got many more people to watch the announcements and that will help Apples Sales.
Its basic system theory. I can't know all the interactions between all the systems so I can't account for everything. The easy test is to schedule some downtime and tell the system to reboot. If all goes to plan the system is back up in 90 seconds with most server (or 5 minutes for a cisco router).
/dev/random where a change in the startup sequence means there isn't quite enough random state in the system to prevent a deadlock.
At work we have 2 nearly identical systems that can each cope with the entire load and they don't need to talk to each other except for non real time things like end of month reports. The reboot test is a great way to keep from getting bitten by stupid things like a change in openssh's dealing with
How do you know that the disk label is still working? Most OS's won't let you read it (since its cached). There are many parts of modern hardware that are essential to booting but can't be accessed outside of the reset sequence. There are things like
flash bios that you can't test from a live system and that perpetual problem with hard disks of "will it wake up next time?"
I've got a few outstanding bugs with cisco because their NAT/PAT stuff doesn't come up quite the same way as when its entered so the only way to know if a config is going to "stick" is to bring the thing up from a full reset state.
I agree that a sysadmin should be able to come up with a full deadlock state diagram for the system but when that graph has more than 1000 nodes on it, the only sure way is a 'halt' and hit the reset switch but even that doesn't test a full start from a power off state.
I think I've been busted!
I'm an early adopter and I don't see anything I'm going to buy. My next computer purchase might be one of the $500 apples if they can get me one before I read a sucky review (like review of a cheap video chip in the new imacs). I don't need any more disk space. I'll buy a gig sd card when they are below $70 and not before since I've never used most of my current sd memory or my usb memory stick but having a gig of tiny memory would be cool for some stilly reason.
.55tb I can't use right now (thanks sun!). Maybe I'm getting to old for the toys but I haven't seen anything real impressive in a while.
I don't need another mp3 player. In fact I've given away at least two and the ones around the house never get used. (but I'm going to hack one for underwater use if I can get the oregon sci replacement headsets).
So Mr toy makers... impress me or you won't see my money. Get me a postscript color laser printer for $200 or get me a 7 inch LCD touch screen that will work in a midwest summer in a car. I don't need fancy software unless its real cool and I'm not into security snake oil. I would by security dongles if you provided open source source code to talk to the thing but I'm installing your binaries on my box. I don't need bigger hard drives since I've got nearly