Remember all the faux-geeks that went to school during the dot-com-bomb for the money?
No, but I remember the raging debates on Slashdot and many encouraging the faux-geeks not to go to school as it was "a waste of time and money", opting instead to encourage them to become system administrators. I contend the software development fall out from the dot-com bust was applied heaviest on the ones who skipped school in favor of becoming perl hackers and *nix administrators. Those with a C.S. or Comp.E. degree had credentials to fall back. The ones without (the ones chasing the carrot) are more likely the ones who are working the less favorable jobs depending on your own perspective.
Its tried and true, if you have a solid background and good skills you'll succeed in any software field: embedded systems, OS development, OSS, etc...
...in taking a program and just removing all the newlines and saying "hey, I did a P2P program in 9 lines"? Its not really 9 lines, its 9 visual lines but far more executable lines.
What is really needed is publicly-available source code that anyone can view.
Why would that help? By the same basic reason you put forth against a paper receipt: just because they give you source code listing A doesn't mean they actually use source code listing A in the machine. There's nothing to stop a malicous entity from publishing one set of source code and using another for the actual machine. Unless you plan on compiling and running the source code at the voting booth source code is just as useless as a paper receipt.
I live in the Northern-Chicago area and have had to dial 1-847-xxx-xxxx for quite sometime now.
Minix is not for general use
on
The End Of Minix?
·
· Score: 3, Informative
I'm a bit tired of reading about the Minix vs. Linux debate when its apparent that most don't realize that Tanenbaum et al. did not write Minix as a general purpose OS. Minix was written as a teaching tool for operating systems classes. Tanenbaum has refused to add more "user" features to Minix because he wanted an educational Unix clone students could interact and program with without getting lost. Writing an operating system that a student can understand and learn from is a lot harder than writing an operating system that only already-knowledgable-programmers can work on. So in the future please be kind to Mr. Tanenbaum or at least do a touch of research before blasting him with "in your face Tanenbaum" statements I've read here. I realize siding with Tanenbaum on/. is not a popular position but the one thing that really gets me upset here is when people blast a good man (Tanenbaum) who's done a lot of good work over blind advocacy to on operating system.
Oh and just to make sure I get modded down as Troll...let us all remember this quote from Mr. Tanenbaum's books: "The desire for a free production (as opposed to educational) version of Minix led a Finnish student, Linux Torvalds, to write Linux. This system was developed on Minix and originally supported various Minix features (e.g., the Minix file system)". So yes if you are a Linux fan remember Linux's roots come from Minix so trashing Minix its tantamount to trashing your parents.
I may be in the minority here but I believe you should start with some syntax before you teach design. Implementing a quality design will require syntax that most courses take weeks to get to, speaking from a C++ standpoint specifically but I believe it holds true for other languages as well. What's the point in showing someone how structures should interact if they don't have the slighest idea on how to transform that into code.
Basic rule of software: do the right things before you worry about doing the right things well. Learning the syntax is doing the right things, proper design is doing the right things well.
Lurk on this for a little while (be prepared for 200+ messages per day):
http://www.tux.org/lkml/
Watch for to do lists or bug reports to go flying by on the list and start there. Its probably best if you don't try to implement something from scratch your first time out. Start slow and learn the inner workings first.
TCP has some congestion control already, fast retransmission followed by additive increase-multiplicative decrease...but the problem with this idea when I read it is that using UDP you have no guarantee that the "equations" are getting to the receiver. Maybe I missed something but it seems to me that if an equation is lost there is no way to complete the information transfer and no way to tell the sender "hey, I didn't get it!"
I was not trying to as you say "bash Linux as an RTOS", just explaning my reasoning why I don't recommend it in any products I work on. As for not having the source code, every commercial RTOS I have worked with gives us the source code. Embedded systems rely on the stability of their OS far more than other commercial software, if the system I currently work on fails my customer has to put someone in a truck and drive somewhere and that ticks them off something fierce. So I need a good feeling about the OS I choose from the get-go. As for things getting fixed because there's a large cadre of people working on it, there is no guarantee that it will get fixed. When meeting deadlines with large sums of hard money on the line, I need to be able to call someone and say "fix this or you don't get paid". Again I'm not trying to flame on Linux, just trying to advance my opinion on a very Linux biased website.
Sorry to anyone who believes Linux is THE choice for everything, its not. As a real time embedded developer who has done some work on Linux device drivers I have yet to suggest Linux as an option when the OS choice has come up. I agree with the author when he cringes at some of the commentary in the Linux source code, I'm supposed to stake my name and my company's name on an OS with comments like: "/* This is a hack..." in the kernel? And say we do go with Linux and a problem with the OS comes up what should we do? Post to the linux-kernel mailing list and hope it gets fixed? Assign one of our developers to fix it? We don't hire OS programmers for the very reason that we buy our OS, we're DSP engineers. Most companies won't go with Linux because of the fact if something breaks they can't submit a bug report and withhold payment until it gets fixed.
I'm an avid Linux user at home but for fault-intolerant real time systems, I would feel a bit uneasy recommending Linux for an embedded system just yet. Once I go 6 months without a story on/. where a major fault has been introduced or missed in the Linux kernel I may rethink my opinion but until then I'll be suggesting that we buy our RTOS.
I must start off by saying I am an AT&T Broadband customer who just got his service back after a 4 day absence. I could go on and on about what a poor decision the business people at AT&T and Excite made but that's be done to death. I'm posting to salute the network engineers who are moving 100's of thousands of subscribers per day! They have nothing to do with the business end of this whole mess but I have never seen a panic induced migration move so quickly! I have some choice words for people wearing suits in this but hey to you guys in jeans and a tshirt working ling hours in raised floor network offices, nice job.
First off: managers don't like ultimatums. They usually won't give in just for the sake of not giving you implied "change this or else" power to be used at a later date as well.
Secondly, while you may be unhappy with the quality of the product, your opinion does not matter from a business standpoint. The only opinion that matters is the customer. If the customer is happy with the quality of the product being produced, you'll have real trouble effecting any change. I've been in a similar situation and I'll bet most of us have, deal with it or walk.
Frankly if Slashdot becomes any kind of a major influence in a wartime situation, I'm moving to a small island and starting my own army. Outside of complaining that the US Govt. isn't running Linux on everything that contains a microprocessor or wondering what Natalie Portman looks like in fatigues I don't see posibilites for Slashdot being involved in a combat situation.
Actually LinuxPPC does have difficulty getting anything out of Apple, they get a bit more out of Motorola but the core of LinuxPPC is a handfull of hardcores hacking on the hardware until it works.
If you can, figure out roughly what you want to do when you are done with school and find out what you need to get that job. I work on embedded systems and we'll only talk to Computer Engineering students because they have hardware knowledge and that is key in embedded systems. Also remember that as a Computer Engineering student you'll get exposure to formal design practices which you may or may not get in a CompSci program.
According to Silberschantz and Galvin: "An operating system is a program that acts as an intermediary between a user of a computer and the computer hardware. The purpose of an operating system is provide an environment in which a user can execute programs [..] An operating sytem acts as a resource allocation system that manages access to resources such as CPU time, memory space, file storage space, I/O devices, etc [..] An operating system also acts as a control program that controls the execution of user programs to prevent errors and improper use of the computer."
Funny, I didn't see GUI listed. Maybe he should have claimed that Unix is not an acceptable operating system to some.
A number of years ago a psychologist (I can't remember his name or the school he was at) placed a chimp in a box without any stimuli or outside contact for over a month, they called it the Well of Dispair experiement. They observed that the chimp became depressed and sickly. Animal rights activists called it cruel......and yet we do the same to most of our workers in almost every industry.
Well then there's one sure way to speed up the process.....grab a C book, subscribe to the linux kernel mailing list and hit the keyboard!!! Everyone who is involved speeds things up a bit, even if you are just beta testing you may find a bug faster than everyone else.
I'm kinda in the middle on this....the interests of students looking for lecture notes (they should've gone to class anyway but that's neither here nor there) versus the univeristies' sole right to sell, and that's what they're doing, the knowledge contained within their professors' heads. I don't believe some third party has a right to make money off information the university is paying professors to bring, so why not adopt a GPL mentality: you can charge for the media and the effort to copy the data onto said media but not for the data itself. See how many of these places keep selling lecture notes if they can only charge for paper and copies. Although a legistlature adopting a policy that they didn't invent from scratch is very unlikely.
I must also say its a pretty sad note on a number of students at our university levels that businesses that engage in this behavior can survive and thrive. I kinda doubt the majority of thier clients were good students who happend to come down with the flu for a day or two.
Slashdot Mirror
Remember all the faux-geeks that went to school during the dot-com-bomb for the money?
No, but I remember the raging debates on Slashdot and many encouraging the faux-geeks not to go to school as it was "a waste of time and money", opting instead to encourage them to become system administrators. I contend the software development fall out from the dot-com bust was applied heaviest on the ones who skipped school in favor of becoming perl hackers and *nix administrators. Those with a C.S. or Comp.E. degree had credentials to fall back. The ones without (the ones chasing the carrot) are more likely the ones who are working the less favorable jobs depending on your own perspective.
Its tried and true, if you have a solid background and good skills you'll succeed in any software field: embedded systems, OS development, OSS, etc...
...in taking a program and just removing all the newlines and saying "hey, I did a P2P program in 9 lines"? Its not really 9 lines, its 9 visual lines but far more executable lines.
What is really needed is publicly-available source code that anyone can view.
Why would that help? By the same basic reason you put forth against a paper receipt: just because they give you source code listing A doesn't mean they actually use source code listing A in the machine. There's nothing to stop a malicous entity from publishing one set of source code and using another for the actual machine. Unless you plan on compiling and running the source code at the voting booth source code is just as useless as a paper receipt.
The Milwaukee store is significantly bigger than the Chicago store near Foster, much more stuff!
I live in the Northern-Chicago area and have had to dial 1-847-xxx-xxxx for quite sometime now.
I'm a bit tired of reading about the Minix vs. Linux debate when its apparent that most don't realize that Tanenbaum et al. did not write Minix as a general purpose OS. Minix was written as a teaching tool for operating systems classes. Tanenbaum has refused to add more "user" features to Minix because he wanted an educational Unix clone students could interact and program with without getting lost. Writing an operating system that a student can understand and learn from is a lot harder than writing an operating system that only already-knowledgable-programmers can work on. So in the future please be kind to Mr. Tanenbaum or at least do a touch of research before blasting him with "in your face Tanenbaum" statements I've read here. I realize siding with Tanenbaum on /. is not a popular position but the one thing that really gets me upset here is when people blast a good man (Tanenbaum) who's done a lot of good work over blind advocacy to on operating system.
Oh and just to make sure I get modded down as Troll...let us all remember this quote from Mr. Tanenbaum's books: "The desire for a free production (as opposed to educational) version of Minix led a Finnish student, Linux Torvalds, to write Linux. This system was developed on Minix and originally supported various Minix features (e.g., the Minix file system)". So yes if you are a Linux fan remember Linux's roots come from Minix so trashing Minix its tantamount to trashing your parents.
Ahhh, don't we have something like that already known as a social security number?
I may be in the minority here but I believe you should start with some syntax before you teach design. Implementing a quality design will require syntax that most courses take weeks to get to, speaking from a C++ standpoint specifically but I believe it holds true for other languages as well. What's the point in showing someone how structures should interact if they don't have the slighest idea on how to transform that into code.
Basic rule of software: do the right things before you worry about doing the right things well. Learning the syntax is doing the right things, proper design is doing the right things well.
/me getting off soapbox
According to this article at CNN, MS is saying RH did little to popularize Linux.
Read this: http://www.xml.com/ldd/chapter/book/index.html
Lurk on this for a little while (be prepared for 200+ messages per day):
http://www.tux.org/lkml/
Watch for to do lists or bug reports to go flying by on the list and start there. Its probably best if you don't try to implement something from scratch your first time out. Start slow and learn the inner workings first.
TCP has some congestion control already, fast retransmission followed by additive increase-multiplicative decrease...but the problem with this idea when I read it is that using UDP you have no guarantee that the "equations" are getting to the receiver. Maybe I missed something but it seems to me that if an equation is lost there is no way to complete the information transfer and no way to tell the sender "hey, I didn't get it!"
I was not trying to as you say "bash Linux as an RTOS", just explaning my reasoning why I don't recommend it in any products I work on. As for not having the source code, every commercial RTOS I have worked with gives us the source code. Embedded systems rely on the stability of their OS far more than other commercial software, if the system I currently work on fails my customer has to put someone in a truck and drive somewhere and that ticks them off something fierce. So I need a good feeling about the OS I choose from the get-go. As for things getting fixed because there's a large cadre of people working on it, there is no guarantee that it will get fixed. When meeting deadlines with large sums of hard money on the line, I need to be able to call someone and say "fix this or you don't get paid". Again I'm not trying to flame on Linux, just trying to advance my opinion on a very Linux biased website.
Ummm, just about every commercial RTOS I've worked with gives you the source code, kinda important to doing embedded development to have that.
Sorry to anyone who believes Linux is THE choice for everything, its not. As a real time embedded developer who has done some work on Linux device drivers I have yet to suggest Linux as an option when the OS choice has come up. I agree with the author when he cringes at some of the commentary in the Linux source code, I'm supposed to stake my name and my company's name on an OS with comments like: "/* This is a hack..." in the kernel? And say we do go with Linux and a problem with the OS comes up what should we do? Post to the linux-kernel mailing list and hope it gets fixed? Assign one of our developers to fix it? We don't hire OS programmers for the very reason that we buy our OS, we're DSP engineers. Most companies won't go with Linux because of the fact if something breaks they can't submit a bug report and withhold payment until it gets fixed.
/. where a major fault has been introduced or missed in the Linux kernel I may rethink my opinion but until then I'll be suggesting that we buy our RTOS.
I'm an avid Linux user at home but for fault-intolerant real time systems, I would feel a bit uneasy recommending Linux for an embedded system just yet. Once I go 6 months without a story on
I must start off by saying I am an AT&T Broadband customer who just got his service back after a 4 day absence. I could go on and on about what a poor decision the business people at AT&T and Excite made but that's be done to death. I'm posting to salute the network engineers who are moving 100's of thousands of subscribers per day! They have nothing to do with the business end of this whole mess but I have never seen a panic induced migration move so quickly! I have some choice words for people wearing suits in this but hey to you guys in jeans and a tshirt working ling hours in raised floor network offices, nice job.
In addition to seeing a glimpse of what could be him behind Samuel L. Jackson in the traier, IMDB has him listed as a cast member:
.... Jar Jar Binks/Achk Med-Beq
Ahmed Best
So much for that bit of improvement that could have been between EpI and EpII.
First off: managers don't like ultimatums. They usually won't give in just for the sake of not giving you implied "change this or else" power to be used at a later date as well.
Secondly, while you may be unhappy with the quality of the product, your opinion does not matter from a business standpoint. The only opinion that matters is the customer. If the customer is happy with the quality of the product being produced, you'll have real trouble effecting any change. I've been in a similar situation and I'll bet most of us have, deal with it or walk.
Frankly if Slashdot becomes any kind of a major influence in a wartime situation, I'm moving to a small island and starting my own army. Outside of complaining that the US Govt. isn't running Linux on everything that contains a microprocessor or wondering what Natalie Portman looks like in fatigues I don't see posibilites for Slashdot being involved in a combat situation.
Actually LinuxPPC does have difficulty getting anything out of Apple, they get a bit more out of Motorola but the core of LinuxPPC is a handfull of hardcores hacking on the hardware until it works.
If you can, figure out roughly what you want to do when you are done with school and find out what you need to get that job. I work on embedded systems and we'll only talk to Computer Engineering students because they have hardware knowledge and that is key in embedded systems. Also remember that as a Computer Engineering student you'll get exposure to formal design practices which you may or may not get in a CompSci program.
According to Silberschantz and Galvin: "An operating system is a program that acts as an intermediary between a user of a computer and the computer hardware. The purpose of an operating system is provide an environment in which a user can execute programs [..] An operating sytem acts as a resource allocation system that manages access to resources such as CPU time, memory space, file storage space, I/O devices, etc [..] An operating system also acts as a control program that controls the execution of user programs to prevent errors and improper use of the computer."
Funny, I didn't see GUI listed. Maybe he should have claimed that Unix is not an acceptable operating system to some.
A number of years ago a psychologist (I can't remember his name or the school he was at) placed a chimp in a box without any stimuli or outside contact for over a month, they called it the Well of Dispair experiement. They observed that the chimp became depressed and sickly. Animal rights activists called it cruel......and yet we do the same to most of our workers in almost every industry.
Ah, maybe you should making an understandable argument to backup your widespread insulting.
You may be an economist but you are obviously no logician.
Well then there's one sure way to speed up the process.....grab a C book, subscribe to the linux kernel mailing list and hit the keyboard!!! Everyone who is involved speeds things up a bit, even if you are just beta testing you may find a bug faster than everyone else.
--End of recruiting speech
I'm kinda in the middle on this....the interests of students looking for lecture notes (they should've gone to class anyway but that's neither here nor there) versus the univeristies' sole right to sell, and that's what they're doing, the knowledge contained within their professors' heads. I don't believe some third party has a right to make money off information the university is paying professors to bring, so why not adopt a GPL mentality: you can charge for the media and the effort to copy the data onto said media but not for the data itself. See how many of these places keep selling lecture notes if they can only charge for paper and copies. Although a legistlature adopting a policy that they didn't invent from scratch is very unlikely.
I must also say its a pretty sad note on a number of students at our university levels that businesses that engage in this behavior can survive and thrive. I kinda doubt the majority of thier clients were good students who happend to come down with the flu for a day or two.