Although there are techniques for safely testing nuclear rockets on earth and some nuclear rocket testing going on, space researchers are still a bit too timid to go ahead with a nuclear rocket program. The advantages of nuclear rockets over conventional rockets include massive reduction in rocket mass and increase in specific impulse. Testing of nuclear rockets on the Moon (which is already highly radioactive due to constant bombardment from the solar wind) will prepare us for a fast journey to Mars, i.e., weeks not years. Then we can make multiple trips and build massive ships for journeys to the outer planets.
How very StarTrek of you. Unfortunately you assume that other build blocks for life were tried and abandoned on earth. Most biologists do not believe that.
That's what the regexp ment. You don't convert it to english and the interpret the result, you read it in the language it was written (i.e., a bastardized regexp/english combination).
Just for reference if I were to do:
ls -1 | grep 'j[a|b]c'
in a suitable directory I would get:
jac jbc
i.e., I would get all matching facts. So assuming we had a directory with all the questions about space, the regexp in the topic would enumerate the two questions I stated above. Of course, I'm assuming the semantics of {word|otherword} is the same as [a|b] but with words instead of letters, but I believe that was the intent.
Ultimately the best archive format for recovery will be one that just duplicates the whole archive twice over, doubling space requirements and improving immunity to lost sectors on drives.
Obviously you know nothing about error correction, so STFU.
It sure does. That's the most annoying thing about being an Open Source advocate, there's all these people around us who have principles and morals. It just makes you sick.
Imagine the situation: my kernel is running, I need to install a module to access [insert piece of proprietary hardware here]. I type: insmod foo.o, I get the above error message. What do I have to do to get this working? I have to go download the kernel source, find the right part, hack my kernel, possibly download the insmod source, hacking that, reboot my machine and try inserting the module again. Unfortunately my machine is running a scientific study that I've been working on for two years. I really need the results that are going to spit out in the next 4 minutes and I really need to put them on their proprietary piece of hardware that I've got a perfectly good driver for. I can't reboot my machine, I'm fucked, and all because some clueless moron thought it would be a good idea to enforce the GPL in code. Just because I can hack the kernel to get rid of it doesn't mean it isn't DRM.
Some kernel developers require that symbols exported by their code must only be used by modules with a GPL compatible license. These symbols are exported by EXPORT_SYMBOL_GPL instead of the normal EXPORT_SYMBOL. GPL-only symbols exported by the kernel and by other modules are only visible to modules with a GPL-compatible license, these symbols appear in/proc/ksyms with a prefix of 'GPLONLY_'. insmod ignores the GPLONLY_ prefix on symbols while loading a GPL licensed module so the module just refers to the normal symbol name, without the prefix. GPL only symbols are not made available to modules without a GPL compatible license, this includes modules with no license at all.
Who the hell wrote that? Why was the patch accepted? What part of "I'm in control of my own computer" was too confusing for this guy to understand? Just to make it absolutely perfectly clear, when I say 'insmod foo.o' I expect foo.o to be loaded into the kernel. The only reason why it shouldn't is if there is a dependancy that would make it not work (but I expect to be able to insmod -f throught that). I do not want my kernel checking the license of foo.o and determining whether or not I am allowed to insert the module.
Even if you make the claim that you have the right to refuse someone who doesn't GPL their module to link to your module, that has absolutely nothing to do with me. It's a matter between you and the guy who isn't GPLing his module. Me, as a user, are free to link any two pieces of software together that I like. You have absolutely no legal claim to stop me. It's my computer. I thought this all was pretty obvious and it was only the stupid corporations that think they can control our lives who write software to stop me doing what I want to do with my computer, now I'm finding linux kernel developers are doing the same.
If you want to set a "tainted" flag, if you want to show me a warning, that's just fine, go right ahead, but don't ever stop me from doing what I want with my computer. Now I'm going off to hack my kernel to remove this insanity. Who knows, I might post a patch on the kernel mailing list.
How many companies have you worked for? How many of those companies had a decent workflow? How many of these companies could tell you how many bugs they fixed last year or which programmer consistently hit their productivity estimates? The problem with the sink or swim method of running software companies is that everyone is sinking and the people who are swimming are dragging them along.
Ahh.. no. Following a proper defect tracking procedure is even more important during maintenance than during development. Students don't get taught anything about defect tracking. They also don't get taught how to read software and understand big systems, two skills that are imperative to a maintenance programmer.
Get used to rebooting your machine or figure out how to get Bochs to compile with the debugger enabled
Write a bootloader (I know Grub rocks, but you need the experience)
Write a keyboard driver
Write a video driver
Write a scheduler
Write a shell
Write a filesystem driver
Write a network driver
Try to port gcc to your OS
Write yet another revolutionary GUI
Write everything else
Congratulations you've got yet another monolithic kernel based hobby OS that no-one is interested in but you.
If you want something remotely interesting, try seperating as much of that junk in the kernel as you can into userland. Pentiums now have system calls that are 5 to 10 times faster than they used to be. Think about writing applications that communicate using shared memory pages. If one app writes a page and then instructs the kernel to map that page into another process, the kernel can do that rediculously fast. That's 4k (or more if you're using bigger pages) that has transfered from one process to another in the space of a single system call.
> Dear Sir, > > I am currently seeking a full time programmer to perform general > maintenance and feature enhancements on my C++ code base. The software is > an open source decompiler that is used by our engineers for the recovery > of lost source code. The entire code base is over 216 thousand lines of > code and over 6 years old. I am hoping to hire this full time developer > towards the end of the first quarter of 2004. This would be a long term > appointment, hopefully with the addition of a new programmer each year for > the next 5 years. If your company is interested, please forward me > details of your rates and availability.
We would definately be interested in assisting you.
We charge 1850 USD per man - month of development.
Looking forward to hearing from you.
Regards,
Z. M. Karbhari Managing Director - CygNET Systems Pvt. Ltd URL : www.cygnetsoft.com Email : karbhari@cygnetsoft.com Voice : +91-20-6134980, +91-20-6129357, +91-20-6125365 Fax : +91-20-6129357
don't design a UI by what they think is "perfectly obvious". They don't write code based on conversations that they've had with their manager either. They follow specifications and process, but US workers are too good for software process. They throw up their hands at requirements gathering. They think their such top shit that they don't need a software discipline. That's what I got out of the article:
As I meet programmers and executives, I hear lots of talk about quality and focus and ISO and CMM certifications and getting the details right. But never - not once - does anybody mention innovation, creativity, or changing the world.
Indian developers have a dedication to professionalism that you just can't buy in the US, and that's the point, it's not about money, because no matter how much money you throw at US engineers they refuse to be professionals.
I used to work there, the office has shut down and the proprietors have moved onto other things. Apparently they're looking for opportunities to do more with their code base but I don't have any more information about that.
Writing code for the Playstation 2's vector units is not exactly easy. There are no C compilers for the VU (Codeplay went out of business last year) so that means you have to sit down and write asm. Usually a game company will write some T&L code to go on the VU and then never touch it again, doing most the work on MIPS core. The VU can be used for a heck of a lot more than that. Unfortunately no-one can afford to do large amounts of programming on the VU because VU-asm programmers are hard to come by and the software they produce is impossible to maintain.
What would be perfect is a compiler that could take ordinary C code and turn it into MIPS+VU0+VU1 code automatically, taking the best advantage of all the machine's resources. Unfortunately this pretty much exists in the realm of science fiction.
"Open Source languages", "algorithms proprietary", some people really shouldn't string words together.
Although there are techniques for safely testing nuclear rockets on earth and some nuclear rocket testing going on, space researchers are still a bit too timid to go ahead with a nuclear rocket program. The advantages of nuclear rockets over conventional rockets include massive reduction in rocket mass and increase in specific impulse. Testing of nuclear rockets on the Moon (which is already highly radioactive due to constant bombardment from the solar wind) will prepare us for a fast journey to Mars, i.e., weeks not years. Then we can make multiple trips and build massive ships for journeys to the outer planets.
How very StarTrek of you. Unfortunately you assume that other build blocks for life were tried and abandoned on earth. Most biologists do not believe that.
Is Pluto a planet?
Is Sedna a planet?
That's what the regexp ment. You don't convert it to english and the interpret the result, you read it in the language it was written (i.e., a bastardized regexp/english combination).
Just for reference if I were to do:
ls -1 | grep 'j[a|b]c'
in a suitable directory I would get:
jac
jbc
i.e., I would get all matching facts. So assuming we had a directory with all the questions about space, the regexp in the topic would enumerate the two questions I stated above. Of course, I'm assuming the semantics of {word|otherword} is the same as [a|b] but with words instead of letters, but I believe that was the intent.
Come on, it's a wonder GTK 2.2.4 ever got a win32 port.
sneak more porn into future Maxis titles.
The article is a summary.
Obviously you know nothing about error correction, so STFU.
It sure does. That's the most annoying thing about being an Open Source advocate, there's all these people around us who have principles and morals. It just makes you sick.
Imagine the situation: my kernel is running, I need to install a module to access [insert piece of proprietary hardware here]. I type: insmod foo.o, I get the above error message. What do I have to do to get this working? I have to go download the kernel source, find the right part, hack my kernel, possibly download the insmod source, hacking that, reboot my machine and try inserting the module again. Unfortunately my machine is running a scientific study that I've been working on for two years. I really need the results that are going to spit out in the next 4 minutes and I really need to put them on their proprietary piece of hardware that I've got a perfectly good driver for. I can't reboot my machine, I'm fucked, and all because some clueless moron thought it would be a good idea to enforce the GPL in code. Just because I can hack the kernel to get rid of it doesn't mean it isn't DRM.
Who the hell wrote that? Why was the patch accepted? What part of "I'm in control of my own computer" was too confusing for this guy to understand? Just to make it absolutely perfectly clear, when I say 'insmod foo.o' I expect foo.o to be loaded into the kernel. The only reason why it shouldn't is if there is a dependancy that would make it not work (but I expect to be able to insmod -f throught that). I do not want my kernel checking the license of foo.o and determining whether or not I am allowed to insert the module.
Even if you make the claim that you have the right to refuse someone who doesn't GPL their module to link to your module, that has absolutely nothing to do with me. It's a matter between you and the guy who isn't GPLing his module. Me, as a user, are free to link any two pieces of software together that I like. You have absolutely no legal claim to stop me. It's my computer. I thought this all was pretty obvious and it was only the stupid corporations that think they can control our lives who write software to stop me doing what I want to do with my computer, now I'm finding linux kernel developers are doing the same.
If you want to set a "tainted" flag, if you want to show me a warning, that's just fine, go right ahead, but don't ever stop me from doing what I want with my computer. Now I'm going off to hack my kernel to remove this insanity. Who knows, I might post a patch on the kernel mailing list.
How many companies have you worked for? How many of those companies had a decent workflow? How many of these companies could tell you how many bugs they fixed last year or which programmer consistently hit their productivity estimates? The problem with the sink or swim method of running software companies is that everyone is sinking and the people who are swimming are dragging them along.
Ahh.. no. Following a proper defect tracking procedure is even more important during maintenance than during development. Students don't get taught anything about defect tracking. They also don't get taught how to read software and understand big systems, two skills that are imperative to a maintenance programmer.
What we need are programmers that are taught software process.
Congratulations you've got yet another monolithic kernel based hobby OS that no-one is interested in but you.
If you want something remotely interesting, try seperating as much of that junk in the kernel as you can into userland. Pentiums now have system calls that are 5 to 10 times faster than they used to be. Think about writing applications that communicate using shared memory pages. If one app writes a page and then instructs the kernel to map that page into another process, the kernel can do that rediculously fast. That's 4k (or more if you're using bigger pages) that has transfered from one process to another in the space of a single system call.
That's gotta get ported. Use WINE or something.. just do it.
Face it, Miguel is a Microsoft stooge. This is about as opaque as the Soviet overthrow of the Afghanistan monoarchy.
back in 1997!
Still seems perfectly ok to me.
> Dear Sir,
>
> I am currently seeking a full time programmer to perform general
> maintenance and feature enhancements on my C++ code base. The software is
> an open source decompiler that is used by our engineers for the recovery
> of lost source code. The entire code base is over 216 thousand lines of
> code and over 6 years old. I am hoping to hire this full time developer
> towards the end of the first quarter of 2004. This would be a long term
> appointment, hopefully with the addition of a new programmer each year for
> the next 5 years. If your company is interested, please forward me
> details of your rates and availability.
We would definately be interested in assisting you.
We charge 1850 USD per man - month of development.
Looking forward to hearing from you.
Regards,
Z. M. Karbhari
Managing Director - CygNET Systems Pvt. Ltd
URL : www.cygnetsoft.com
Email : karbhari@cygnetsoft.com
Voice : +91-20-6134980, +91-20-6129357, +91-20-6125365 Fax : +91-20-6129357
As I meet programmers and executives, I hear lots of talk about quality and focus and ISO and CMM certifications and getting the details right. But never - not once - does anybody mention innovation, creativity, or changing the world.
Indian developers have a dedication to professionalism that you just can't buy in the US, and that's the point, it's not about money, because no matter how much money you throw at US engineers they refuse to be professionals.
One dude hacking a compiler does not a company make.
I used to work there, the office has shut down and the proprietors have moved onto other things. Apparently they're looking for opportunities to do more with their code base but I don't have any more information about that.
What would be perfect is a compiler that could take ordinary C code and turn it into MIPS+VU0+VU1 code automatically, taking the best advantage of all the machine's resources. Unfortunately this pretty much exists in the realm of science fiction.
Guess you havn't heard of remote kernel bugs.