I took a C & Unix course from a Dr Lan at the University of Missouri-Columbia. I posted a few of his test questions to the comp.lang.c group. The funny thing is that dmr replied with the same answer as I put on the test and got it wrong. After getting a D in the class I went through the fromal appleals process. When I showed dr lan the answer was in the k&r book, hs said he didn't recognize the auhority of that book. Since the asst dean of engr knew about the book and who wrote it, it made my point clear but I only got a B out of the class. Now what is the standard shell under unix? everyone say "seashell". Problem is the idiot is still teaching.
Conoco (a midwestern oil company) was sold on the idea that they could get their company logo on the staplers and that would help prevent them from disappearing. What a scam. The result was once they new red staplers with the logo arrived, people started taking them home. I suspect 1/2 the staplers at the highschool had walked off from the oil company. I suspect that Conoco ended up buying something like 10 times more because people were stealing them.
There are two ways to look at the H1B visas. One is that they are close to modern slavery. The other is they are a training time. It teaches you how American compaines work so when you get kicked out of the country, you can go home and start writing code for the same compaines. 3com has just sacked many of their developers and are moving most of their R&D work off to India.
My 86 VW Jetta's manual recomended no using more than two tanks of > 90% ethanol between tanks of gasoline unless you get the dealer to put on the ethaanol kit.
I ran accross an article that showed that people that donate blood tend to have fewer heart and stroke problems than people that don't. Some of the studies show that donating just once a year keeps iron levels down. They went on to discuss iron levels vs hear attacks in men vs women.
Now the people I know that give blood frequenly tend to be in good heath and none of them seem to be over weight so I thought I would look in to this some more. What I found is there could be a number of reasons: 1) Iron levels. Its not convincing. 2) The kind of people that give blood aren't the kinds to get worked up over stilly stuff. Lower stress. 3) Oil change? Water and alcohol can move in and out of the system with ease but other things can't. To some toxins it seems to be a closed system. 4) bad spirits? They used to use leaches to suck the bad sprints out of people and there was quite a bit of scientific papers about the practace for the time. I don't know what they did with the drunk leaches.
The Red Cross seeems to have some info about why giving bloodis good for you but its not convincing. One thing I did find is one blood bank said they don't like to promote the healt benifits because it draws the wrong kind of people.
But the reasons are much different than they imply.
The bigest natural competitor to a typical songbir id a pigeon. I've been told (by someone who does research on penguins) that every pigeon tends to displace at least 20 native birds in Australia.
Pigeons where brought here because the sailors used to drink their boold as a cure for scurvy but now they idiots feed them in the parks and their populations are growing.
Its interesting that cats are getting a major blame for the decreasign numbers of songbirds when the pigeons are teh major cause.
I figure the SUV is more of a moral question of do you want to continue to support the problems in the middle east. The oil consuption difference between using SUVs and not in the US is the difference of spending tens of billions every year in Middle East peach keeping and letting it all become Europes problem. Without SUV's the US wouldn't need to import any Middle east oil.
115.2k isn't the data rate. At 115kbaud, the stop bit (or is that start bit?) is just ignored noise and you send either 0x00 or 0xff if you want to send a high or low signal.
Where I work sells a small micro that hooks up to 4 channels and mounts in a nice rackmount box and sends the data out a 9600 baud serial line. I've got a small program that read teh data, shoves it in/tmp so mrtg can pull it out every 5 minutes. I also know when people leave the computer room door open.
I also free form type. I also free from type. I've been looking at the keys vs fingers when I typed that. How odd, I favored two fingers the first time I typed that and three the latter.
Back to what I was going to say. I don't like ergonomic keyboards, a few minutes with them, and I feel like I'm being forced into a position to type. Its quite uncomfortable.
My typing style is more like the home row is CapsL,a,s,d and j,k,l,; I will often hit t with my right hand.
Some people have flat hands (the fingers are all about the same length) and others have more pointy fingers where the pinky will be much shorter than the pointing finger. I'm one of the pointy fingers people so I'm wondering if that helps encourage me to free form type.
Large projects are getting much safer. Most modern skyscraper projects don't kill anyone and have few or no major injuries. When the Empire State Building was built, it was common to have a person die or be injured beyond the ability to ever work again for every floor you went up. When the St Louis Arch was built (1963-65), it was expected that accidents would kill three people. The result was none. Since the deaths in thouse projects were big news, people worked hard to make sure they didn't continue. For exaple in Panama, the discover that the bugs were the biggest killer and the solving that problem led to a much safer workplace since after those problems were solved, they started looking into the reasons of why workers would get crushed. Up to that point, the people getting crushed were such a small majorty of the deaths that it went virtual unnoticed.
Most major projects cost lives. The Empire State building, cost 7. The Panama Canal lost thousands. Hoover Dam kileld at least 112. Apollo costs hundreds but we only hear about 3.
All of those projects resulted in reseach so the projects after them were safer. Large projects involve risk. The people helping with the progress know those risks.
There are just so many problems with xml that I tend to ignore it. I wasn't even thinging about the scoping issue when I wrote that, I was thinking about stack depth. In that case if your code had to figure out the current record could fit in the current scope or the prior one, the decision matrix would also grow without bounds. Unless you have the option of fully rejecting any malformed xlm file, your asking for trouble.
I think your well versed in the world of users dealing with the output. Most of the stuff I do, the users are way at the other end of the pipeline. Any error message must be passed out of band to the user and that make the systems excessively complicated (aka buggy).
At work we process batches of transactions. We insinst on one of two simple ascii formats. So far we find that about 90% of the people can't get their 1st test batch to us correctly. About 50% can't convert from a test tag to their tag without messing up something else (think s/test/their_uid/ ). If these people can't build ascii files, how are they going to build xml files? Our business requires that we process as much as the file as we can so we have some strange rules about failing gracefuly.
Missing tags are an issue when they create the case where they build up stack state. This very same thing is a major reason netscape (prior to 6) crashed. Assume you have a language that uses { and } to define scope. What happens when they get lost: { record 1 { record 2 { record 3
when it should have been { record 1 } { record 2 } { record 3 }
If your language allows nesting like {record 1 { some_other_record 2 { some_other_record_3 }}} then you hit the problem.
My problem with XML is I can always make a file that will break programs that expect XML. I can't make a file that breaks grep.
Maybe when they get a logo, they will have two versions and a script to change one to the other like the network tool "satan" wich would rename it to "santa" or some such thing.
Ever run a debugger that wasn't designed to be used interactivly? Its amazing what you can do when you have a person with the ability to make a choice.
You can hit a theoretical worst case every time you run low on memory or get a malformed input. real world production systems deal with these two conditions all the time. So its ok to have your banks payment system grab all the memory because the latest version of some popular program forgot a closing tag?
Lets say you have an application that has 1 mb of memory. Now assume you need to process a file that is 10mb. Now assume that the file is broken in some common way (say a closing tag is gone). How do you parse the file in this case?
For some clues, read up about how TeX works since its parser has the same issues. It's parsing has the same problems and Dr. Knuth has written about why its bad. TeX deals with it by dumping the stack and going interactive on the user. Non-interactive programs don't have that option and when the job description includes malformed input, there are difficult problems to solve.
Any bets on when Apple will introduce a "fast cock" feature to their system?
So why do people insist on calling clocks that are ahead "fast" and ones that are behind "slow". They may be correct assumptions if the clock was set at some point but a clock can be behind but fast.
Don't use the master clocks unless you need that kind of accuracy (then ask them and they will give the the names of better servers).
Do a traceroute out out of your net and see if you can find a few other servers. $ ntpdate -v -u 64.39.2.65 will tell you if its running ntp or not. Pick a few of your upstream and go with that. If you have several upstream routes/providers then ntp will make sure you get the correct time if one of them gets way out of sync.
Re:Most cablemodem/DSL head-end routers have the t
on
Do You Have The Time?
·
· Score: 2
You ISP does this because they tend to run cisco gear and its easier to configure it to do NTP than to set the silly clock. If you care about your logs having the right times, its a good thing to have the clock set.
conf t ntp master ntp server 139.130.6.25 ntp server someother.server (Please pick something better than my ISP's upstream router, this one won't be very good for you)
I've meet someone who uses GPS to find out how much his country (Sweeden) moves. He has a plot of most of Europes movments. The plots are on an sheet of paper in actual scale. Aparently Sweeden moves a few inches a year.
Didn't any of the XML supporters every study parsing in their CS classes? Or are they just web control freaks that didn't bother with anything past highschool. Oh wait, I'm talking about w3c so of course they are contorl freaks. At least most people ingored them.
The problem with XML is that it diverges into two dinstict worst cases. One requires and infinite amount of memory, the other and infinite amount of time. Both of these are bad things and much study of algorithms is about avoiding both of these conditions. Odd thing is most people in the IT field today have no clue about why this happens or even that it can happen. Of course these are the same programmers that coudn't describe a quicksort if they had to or descibe something in BNF grammar. And we wonder why most programmers today just produce garbage.
Slashdot Mirror
I took a C & Unix course from a Dr Lan at the University of Missouri-Columbia. I posted a few of his test questions to the comp.lang.c group. The funny thing is that dmr replied with the same answer as I put on the test and got it wrong. After getting a D in the class I went through the fromal appleals process. When I showed dr lan the answer was in the k&r book, hs said he didn't recognize the auhority of that book. Since the asst dean of engr knew about the book and who wrote it, it made my point clear but I only got a B out of the class. Now what is the standard shell under unix? everyone say "seashell". Problem is the idiot is still teaching.
Conoco (a midwestern oil company) was sold on the idea that they could get their company logo on the staplers and that would help prevent them from disappearing. What a scam. The result was once they new red staplers with the logo arrived, people started taking them home. I suspect 1/2 the staplers at the highschool had walked off from the oil company. I suspect that Conoco ended up buying something like 10 times more because people were stealing them.
There are two ways to look at the H1B visas. One is that they are close to modern slavery. The other is they are a training time. It teaches you how American compaines work so when you get kicked out of the country, you can go home and start writing code for the same compaines. 3com has just sacked many of their developers and are moving most of their R&D work off to India.
My 86 VW Jetta's manual recomended no using more than two tanks of > 90% ethanol between tanks of gasoline unless you get the dealer to put on the ethaanol kit.
I ran accross an article that showed that people that donate blood tend to have fewer heart and stroke problems than people that don't. Some of the studies show that donating just once a year keeps iron levels down. They went on to discuss iron levels vs hear attacks in men vs women.
Now the people I know that give blood frequenly tend to be in good heath and none of them seem to be over weight so I thought I would look in to this some more. What I found is there could be a number of reasons:
1) Iron levels. Its not convincing.
2) The kind of people that give blood aren't the kinds to get worked up over stilly stuff. Lower stress.
3) Oil change? Water and alcohol can move in and out of the system with ease but other things can't. To some toxins it seems to be a closed system.
4) bad spirits? They used to use leaches to suck the bad sprints out of people and there was quite a bit of scientific papers about the practace for the time. I don't know what they did with the drunk leaches.
The Red Cross seeems to have some info about why giving bloodis good for you but its not convincing. One thing I did find is one blood bank said they don't like to promote the healt benifits because it draws the wrong kind of people.
But the reasons are much different than they imply.
The bigest natural competitor to a typical songbir id a pigeon. I've been told (by someone who does research on penguins) that every pigeon tends to displace at least 20 native birds in Australia.
Pigeons where brought here because the sailors used to drink their boold as a cure for scurvy but now they idiots feed them in the parks and their populations are growing.
Its interesting that cats are getting a major blame for the decreasign numbers of songbirds when the pigeons are teh major cause.
I figure the SUV is more of a moral question of do you want to continue to support the problems in the middle east. The oil consuption difference between using SUVs and not in the US is the difference of spending tens of billions every year in Middle East peach keeping and letting it all become Europes problem. Without SUV's the US wouldn't need to import any Middle east oil.
115.2k isn't the data rate. At 115kbaud, the stop bit (or is that start bit?) is just ignored noise and you send either 0x00 or 0xff if you want to send a high or low signal.
/tmp so mrtg can pull it out every 5 minutes. I also know when people leave the computer room door open.
Where I work sells a small micro that hooks up to 4 channels and mounts in a nice rackmount box and sends the data out a 9600 baud serial line. I've got a small program that read teh data, shoves it in
I also free form type.
I also free from type.
I've been looking at the keys vs fingers when I typed that. How odd, I favored two fingers the first time I typed that and three the latter.
Back to what I was going to say. I don't like ergonomic keyboards, a few minutes with them, and I feel like I'm being forced into a position to type. Its quite uncomfortable.
My typing style is more like the home row is
CapsL,a,s,d and j,k,l,; I will often hit t with my right hand.
Some people have flat hands (the fingers are all about the same length) and others have more pointy fingers where the pinky will be much shorter than the pointing finger. I'm one of the pointy fingers people so I'm wondering if that helps encourage me to free form type.
Large projects are getting much safer. Most modern skyscraper projects don't kill anyone and have few or no major injuries. When the Empire State Building was built, it was common to have a person die or be injured beyond the ability to ever work again for every floor you went up. When the St Louis Arch was built (1963-65), it was expected that accidents would kill three people. The result was none. Since the deaths in thouse projects were big news, people worked hard to make sure they didn't continue. For exaple in Panama, the discover that the bugs were the biggest killer and the solving that problem led to a much safer workplace since after those problems were solved, they started looking into the reasons of why workers would get crushed. Up to that point, the people getting crushed were such a small majorty of the deaths that it went virtual unnoticed.
Most major projects cost lives. The Empire State building, cost 7. The Panama Canal lost thousands. Hoover Dam kileld at least 112. Apollo costs hundreds but we only hear about 3.
All of those projects resulted in reseach so the projects after them were safer. Large projects involve risk. The people helping with the progress know those risks.
There are just so many problems with xml that I tend to ignore it. I wasn't even thinging about the scoping issue when I wrote that, I was thinking about stack depth. In that case if your code had to figure out the current record could fit in the current scope or the prior one, the decision matrix would also grow without bounds. Unless you have the option of fully rejecting any malformed xlm file, your asking for trouble.
I think your well versed in the world of users dealing with the output. Most of the stuff I do, the users are way at the other end of the pipeline. Any error message must be passed out of band to the user and that make the systems excessively complicated (aka buggy).
At work we process batches of transactions. We insinst on one of two simple ascii formats. So far we find that about 90% of the people can't get their 1st test batch to us correctly. About 50% can't convert from a test tag to their tag without messing up something else (think s/test/their_uid/ ). If these people can't build ascii files, how are they going to build xml files? Our business requires that we process as much as the file as we can so we have some strange rules about failing gracefuly.
Missing tags are an issue when they create the case where they build up stack state. This very same thing is a major reason netscape (prior to 6) crashed.
Assume you have a language that uses { and } to define scope. What happens when they get lost:
{ record 1
{ record 2
{ record 3
when it should have been
{ record 1 }
{ record 2 }
{ record 3 }
If your language allows nesting like
{record 1 { some_other_record 2 { some_other_record_3 }}}
then you hit the problem.
My problem with XML is I can always make a file that will break programs that expect XML. I can't make a file that breaks grep.
So now if I give a talk for IEEE, only I get busted?
Maybe when they get a logo, they will have two versions and a script to change one to the other like the network tool "satan" wich would rename it to "santa" or some such thing.
Ever run a debugger that wasn't designed to be used interactivly? Its amazing what you can do when you have a person with the ability to make a choice.
You can hit a theoretical worst case every time you run low on memory or get a malformed input. real world production systems deal with these two conditions all the time. So its ok to have your banks payment system grab all the memory because the latest version of some popular program forgot a closing tag?
Lets say you have an application that has 1 mb of memory. Now assume you need to process a file that is 10mb. Now assume that the file is broken in some common way (say a closing tag is gone).
How do you parse the file in this case?
For some clues, read up about how TeX works since its parser has the same issues. It's parsing has the same problems and Dr. Knuth has written about why its bad. TeX deals with it by dumping the stack and going interactive on the user. Non-interactive programs don't have that option and when the job description includes malformed input, there are difficult problems to solve.
Any bets on when Apple will introduce a "fast cock" feature to their system?
So why do people insist on calling clocks that are ahead "fast" and ones that are behind "slow". They may be correct assumptions if the clock was set at some point but a clock can be behind but fast.
I resent your remarks!
I use NTP because I'm to lazy to set the damn clock.
Is anyone else getting the source forge add with the clock face?
I know what your up to. Your tring to build a device that will let you find that anoying cricket at night arn't you?
Don't use the master clocks unless you need that kind of accuracy (then ask them and they will give the the names of better servers).
Do a traceroute out out of your net and see if you can find a few other servers.
$ ntpdate -v -u 64.39.2.65
will tell you if its running ntp or not. Pick a few of your upstream and go with that. If you have several upstream routes/providers then ntp will make sure you get the correct time if one of them gets way out of sync.
You ISP does this because they tend to run cisco gear and its easier to configure it to do NTP than to set the silly clock. If you care about your logs having the right times, its a good thing to have the clock set.
conf t
ntp master
ntp server 139.130.6.25
ntp server someother.server
(Please pick something better than my ISP's upstream router, this one won't be very good for you)
Got any more info on that black box? I figure it would be a great project for a small linux box that can do ntp...
I've meet someone who uses GPS to find out how much his country (Sweeden) moves. He has a plot of most of Europes movments. The plots are on an sheet of paper in actual scale. Aparently Sweeden moves a few inches a year.
Didn't any of the XML supporters every study parsing in their CS classes? Or are they just web control freaks that didn't bother with anything past highschool. Oh wait, I'm talking about w3c so of course they are contorl freaks. At least most people ingored them.
The problem with XML is that it diverges into two dinstict worst cases. One requires and infinite amount of memory, the other and infinite amount of time. Both of these are bad things and much study of algorithms is about avoiding both of these conditions. Odd thing is most people in the IT field today have no clue about why this happens or even that it can happen. Of course these are the same programmers that coudn't describe a quicksort if they had to or descibe something in BNF grammar. And we wonder why most programmers today just produce garbage.