Completely unrelated to your work, but the name "Moxie Marlinspike" sounds wonderful. It's obvious why you chose "Marlinspike", after all as a sailor it's an object that you may have found useful (and it's not that uncommon to have a last name that is a tool or a trade). But the first name you chose - why did you choose it? Looking around for references to Moxie the most prominent one is for one of the earliest carbonated beverages sold in the world, which doesn't sound too probable as an origin.
LinuxFr.org : Why porting the userland utilities from NetBSD? Is the goal to become a BSD-like system?
Andrew Tanenbaum : We think NetBSD is a mature stable system. Linux is not nearly as well written and is changing all the time. NetBSD has something like 8000 packages. That is enough for us.
That suggests to me that Tanenbaum doesn't actually know what Linux is. Linux is just a kernel. Userland packages and how well (or not) they may be written have nothing to do with Linux. How many of the 8000 NetBSD packages are also available in Debian, for example? I would wager the vast majority, and they change "all the time" as much as they do when being run on Linux (the packages that aren't shared is probably the BSD equivalent of the base tools, like ls, grep, cp et al. I don't think the base userland GNU tools that run on Linux change all that often either).
Mac OSX is effectively BSD, though - the proof of the pudding and all that is that when I'm writing system software tools on my OSX machine, to port them to OpenBSD or NetBSD, I simply have to run "make". However, to port to Linux there's usually one or two small #ifdefs I have to add to get it to work (and of course, for Windows generally quite a lot more). While it might not be a BSD kernel, it feels like a family member of BSD when writing system tools.
So all the sectarian violence in Northern Ireland (where Christians are killing Christians over trivial differences in their religious beliefs) doesn't count?
Not only did Greece lie, but Wall Street colluded with Greece to help them hide the debts. And the nascent eurozone, in a breathless headlong rush to get the euro going failed to do their due diligence.
Hmm. I'm not sure I follow: Because the police are every bit as dangerous as the drug dealers, I should break into a shop and help myself to an HD television? Hmmmm....
You're wrong: Britain actually slavishly and pedantically implements every European directive to its fullest and most exact extent. The population resents this: the French tends to ignore EU directives as they please, the Germans love it, the Italians and Irish are too chaotic to implement them. It's only the British who fully implement them and then resent it.
British civil servants love the EU because it allows them to implement all sorts of rules in a jobsworthy manner then blame it on the EU when anyone complains.
Shoving our problems in a small concentrated spot in the ground (nuclear) where you know where they are and keep them from harm is a lot better than letting them spread out worldwide (CO2 from coal) where you can't stop it from adding to AGW.
Not all servers acommodate huge databases. There are plenty of servers that have to service high numbers of users for tasks which are not computationally or memory intensive. 32 bit is likely to be better for these kinds of tasks.
In the case of Turbo Pascal, probably pretty much everything was in that.exe. Don't forget there was no dynamic linking of libraries, let alone much in the way of libraries on MS-DOS in the first place. There would have been various int# calls within the executable to call the "operating system" but the OS (BIOS + DOS) itself wasn't all that much bigger.
Certainly in the case of the likes of spreadsheet programs for 8 bit systems, at most you probably had a 16K ROM in addition to the program itself, so still less than ~40K for the entire system.
Surely it's the person's choice if they want to take something that may reduce mental acuity or have health effects? It's their own body, we shouldn't be legislating what people do to themselves.
If we were to start legislating against anything that someone does to themselves because it may cause them harm, we'd end up banning skydiving, riding motorcycles, cycling, going outdoors in the summer without sunblock etc. etc. etc., in other words the full-on nanny state.
One thing you may consider as well as your EPROM programmer is making a NOR flash adapter for the old boards you're using, so you can use a cheaper, much easier to program NOR flash chip (NOR flash is byte addressable, just like old EPROMs. Indeed, the pinning on many of the standard parts is very similar to older EPROMs) when you're tinkering with stuff.
The advantage of flash is that erasing is a much easier operation, and programming is all 5 volt (so is the erasing). Therefore if you're tinkering with some hardware, you can very quickly reprogram a flash IC to try again if there's something wrong with what you wrote, rather than going through all the bother of using a UV eraser. It's quite easy to roll your own flash programmer, too, since erasing/programming is done by sending codes to the chip which are listed in the datasheet.
(If it were me I'd still get the EPROM programmer too, I would use flash for tinkering, and when the tinkering is over use an EPROM of the correct period for the hardware in question so the hardware looks as right as possible).
Boot process is not a feature of the CPU architecture. Boot process is a feature of the motherboard that the CPU is on or the SOC that the CPU lives inside of.
I have an x86 machine that will not boot anything PC-like (a rather old Garmin handheld with an embedded 80386). The lack of a BIOS is more of a reflection that ARM is typically in embedded systems, not that you can't make a standard BIOS for one.
ARM is *NOT* based on the 68000 design, it was an original CPU design by Acorn computers of Cambridge, England (ARM originally stood for Acorn Risc Machine) for their desktop computers in the late 1980s and during the 90s. ARM bears absolutely no resemblance to 68000.
Sophie Wilson and Steve Furber, the designers of the ARM, were inspired by the simple architecture of the 6502, but the ARM is not based on that either (the ARM does not resemble the 6502 either, nor is it based on the 6502).
There's no wonder you only get voicemail and no replies. If you bought or rented a property near an existing airfield, the FAA is probably tired of it.
If you bought a property near a pipeline, then they will ignore you for that too, because pipeline patrol (who tend to use helicopters and light aircraft) have a bona fide need to fly low. Do your due diligence next time you look for a place to live!
If you don't like aircraft or aircraft noise, don't live in a house near an airfield. Aircraft must descend below 1000 feet to take off and land, and the rules explicitly allow aircraft to fly over congested areas as low as they need for the purposes of taking off and landing.
He is *NOT* breaking the rules. The actual rule says EXCEPT for approach and departure from a landing site, an aircraft must remain 1000 feet above a congested area. If he is flying from an airfield, he was on approach or departure. Therefore he can fly low because to be able to land you have to actually descend at some time. You can't come over the fence of the airfield at 1000 feet and expect to land.
It is not breaking the rules. The rules explicitly say it is OK. The problem is people buy houses near airfields and then get all surprised when aircraft take off and land at airfields, and aircraft necessarily have to be low when they take off and land. Usually it's because the homeowner didn't do their due diligence and check that there was a nearby airfield before they bought their house.
It's funny how Hitch-hiker stuff seems to have a bearing on real life so often...
"...and the Triganic Pu has its own very special problems. Its exchange rate of eight Ningis to one Pu is simple enough, but since a Ningi is a triangular rubber coin six thousand eight hundred miles along each side, no one has ever collected enough to own one Pu. Ningis are not negotiable currency, because the Galactibanks refuse to deal in fiddling small change"
And I bet the banks would refuse to deal with this gigantic gold coin.
Beauty is always in the eye of the beholder, but there really are very, very few airliners that are actually beautiful. I think Boeing have finally built a beautiful airliner, and it's the wing that makes the 787 so beautiful, from its graceful curve in-flight, to the tapered winglets and the high aspect ratio that makes the aircraft look very reminiscent of a modern carbon fibre glider, to even things like the flight deck windows which blend into the design.
As I said, beauty is in the eye of the beholder, but these are probably the only airliners I would actually call "beautiful":
- Lockheed Constellation, with its gracefully curved and tapering fuselage (from an era where everyone else's airliner looked like a sausage with wings). - Concorde. I don't think I need to explain. (No, the Tu-144 doesn't qualify, although superficially similar to Concorde as in it has delta wings, it's actually pretty ugly - the wing doesn't have Concorde's graceful 3 dimensional shape, the flight deck windows just look awful and those canards...good grief). - And now the Boeing 787.
Yes, there are probably others that people find beautiful of course, and I've probably missed or forgotten some (I think the last version of the Comet, the Comet 4 strongly qualifies with the engines hidden in the wings) but the three above are the ones I find most aesthetically pleasing.
This is not about PV. This is about thermal solar collection, which also allows the storage of energy (focus sunlight on a tower, melt salt, store reasonably large amounts of energy in molten salt so as to be able to continue generating during the night).
Slashdot Mirror
Completely unrelated to your work, but the name "Moxie Marlinspike" sounds wonderful. It's obvious why you chose "Marlinspike", after all as a sailor it's an object that you may have found useful (and it's not that uncommon to have a last name that is a tool or a trade). But the first name you chose - why did you choose it? Looking around for references to Moxie the most prominent one is for one of the earliest carbonated beverages sold in the world, which doesn't sound too probable as an origin.
This stands out in the interview:
That suggests to me that Tanenbaum doesn't actually know what Linux is. Linux is just a kernel. Userland packages and how well (or not) they may be written have nothing to do with Linux. How many of the 8000 NetBSD packages are also available in Debian, for example? I would wager the vast majority, and they change "all the time" as much as they do when being run on Linux (the packages that aren't shared is probably the BSD equivalent of the base tools, like ls, grep, cp et al. I don't think the base userland GNU tools that run on Linux change all that often either).
Mac OSX is effectively BSD, though - the proof of the pudding and all that is that when I'm writing system software tools on my OSX machine, to port them to OpenBSD or NetBSD, I simply have to run "make". However, to port to Linux there's usually one or two small #ifdefs I have to add to get it to work (and of course, for Windows generally quite a lot more). While it might not be a BSD kernel, it feels like a family member of BSD when writing system tools.
So all the sectarian violence in Northern Ireland (where Christians are killing Christians over trivial differences in their religious beliefs) doesn't count?
Financially inefficient is probably the meaning of "inefficient" in this instance.
Not only did Greece lie, but Wall Street colluded with Greece to help them hide the debts. And the nascent eurozone, in a breathless headlong rush to get the euro going failed to do their due diligence.
Hmm. I'm not sure I follow: Because the police are every bit as dangerous as the drug dealers, I should break into a shop and help myself to an HD television? Hmmmm....
Have you ever tried to apply for one of those as a postgraduate? You get turned down on the grounds of being "overqualified".
Not only that, Britain's banks are heavily exposed to Irish debt, so what happens in the eurozone hugely affects Britain.
You're wrong: Britain actually slavishly and pedantically implements every European directive to its fullest and most exact extent. The population resents this: the French tends to ignore EU directives as they please, the Germans love it, the Italians and Irish are too chaotic to implement them. It's only the British who fully implement them and then resent it.
British civil servants love the EU because it allows them to implement all sorts of rules in a jobsworthy manner then blame it on the EU when anyone complains.
The waste problem from coal and oil and gas stations hasn't gone away either. Should we not build any power stations?
Shoving our problems in a small concentrated spot in the ground (nuclear) where you know where they are and keep them from harm is a lot better than letting them spread out worldwide (CO2 from coal) where you can't stop it from adding to AGW.
Not all servers acommodate huge databases. There are plenty of servers that have to service high numbers of users for tasks which are not computationally or memory intensive. 32 bit is likely to be better for these kinds of tasks.
In the case of Turbo Pascal, probably pretty much everything was in that .exe. Don't forget there was no dynamic linking of libraries, let alone much in the way of libraries on MS-DOS in the first place. There would have been various int# calls within the executable to call the "operating system" but the OS (BIOS + DOS) itself wasn't all that much bigger.
Certainly in the case of the likes of spreadsheet programs for 8 bit systems, at most you probably had a 16K ROM in addition to the program itself, so still less than ~40K for the entire system.
Surely it's the person's choice if they want to take something that may reduce mental acuity or have health effects? It's their own body, we shouldn't be legislating what people do to themselves.
If we were to start legislating against anything that someone does to themselves because it may cause them harm, we'd end up banning skydiving, riding motorcycles, cycling, going outdoors in the summer without sunblock etc. etc. etc., in other words the full-on nanny state.
One thing you may consider as well as your EPROM programmer is making a NOR flash adapter for the old boards you're using, so you can use a cheaper, much easier to program NOR flash chip (NOR flash is byte addressable, just like old EPROMs. Indeed, the pinning on many of the standard parts is very similar to older EPROMs) when you're tinkering with stuff.
The advantage of flash is that erasing is a much easier operation, and programming is all 5 volt (so is the erasing). Therefore if you're tinkering with some hardware, you can very quickly reprogram a flash IC to try again if there's something wrong with what you wrote, rather than going through all the bother of using a UV eraser. It's quite easy to roll your own flash programmer, too, since erasing/programming is done by sending codes to the chip which are listed in the datasheet.
(If it were me I'd still get the EPROM programmer too, I would use flash for tinkering, and when the tinkering is over use an EPROM of the correct period for the hardware in question so the hardware looks as right as possible).
Boot process is not a feature of the CPU architecture. Boot process is a feature of the motherboard that the CPU is on or the SOC that the CPU lives inside of.
I have an x86 machine that will not boot anything PC-like (a rather old Garmin handheld with an embedded 80386). The lack of a BIOS is more of a reflection that ARM is typically in embedded systems, not that you can't make a standard BIOS for one.
ARM is *NOT* based on the 68000 design, it was an original CPU design by Acorn computers of Cambridge, England (ARM originally stood for Acorn Risc Machine) for their desktop computers in the late 1980s and during the 90s. ARM bears absolutely no resemblance to 68000.
Sophie Wilson and Steve Furber, the designers of the ARM, were inspired by the simple architecture of the 6502, but the ARM is not based on that either (the ARM does not resemble the 6502 either, nor is it based on the 6502).
There's no wonder you only get voicemail and no replies. If you bought or rented a property near an existing airfield, the FAA is probably tired of it.
If you bought a property near a pipeline, then they will ignore you for that too, because pipeline patrol (who tend to use helicopters and light aircraft) have a bona fide need to fly low. Do your due diligence next time you look for a place to live!
If you don't like aircraft or aircraft noise, don't live in a house near an airfield. Aircraft must descend below 1000 feet to take off and land, and the rules explicitly allow aircraft to fly over congested areas as low as they need for the purposes of taking off and landing.
He is *NOT* breaking the rules. The actual rule says EXCEPT for approach and departure from a landing site, an aircraft must remain 1000 feet above a congested area. If he is flying from an airfield, he was on approach or departure. Therefore he can fly low because to be able to land you have to actually descend at some time. You can't come over the fence of the airfield at 1000 feet and expect to land.
It is not breaking the rules. The rules explicitly say it is OK. The problem is people buy houses near airfields and then get all surprised when aircraft take off and land at airfields, and aircraft necessarily have to be low when they take off and land. Usually it's because the homeowner didn't do their due diligence and check that there was a nearby airfield before they bought their house.
It's funny how Hitch-hiker stuff seems to have a bearing on real life so often...
"...and the Triganic Pu has its own very special problems. Its exchange rate of eight Ningis to one Pu is simple enough, but since a Ningi is a triangular rubber coin six thousand eight hundred miles along each side, no one has ever collected enough to own one Pu. Ningis are not negotiable currency, because the Galactibanks refuse to deal in fiddling small change"
And I bet the banks would refuse to deal with this gigantic gold coin.
Beauty is always in the eye of the beholder, but there really are very, very few airliners that are actually beautiful. I think Boeing have finally built a beautiful airliner, and it's the wing that makes the 787 so beautiful, from its graceful curve in-flight, to the tapered winglets and the high aspect ratio that makes the aircraft look very reminiscent of a modern carbon fibre glider, to even things like the flight deck windows which blend into the design.
As I said, beauty is in the eye of the beholder, but these are probably the only airliners I would actually call "beautiful":
- Lockheed Constellation, with its gracefully curved and tapering fuselage (from an era where everyone else's airliner looked like a sausage with wings).
- Concorde. I don't think I need to explain. (No, the Tu-144 doesn't qualify, although superficially similar to Concorde as in it has delta wings, it's actually pretty ugly - the wing doesn't have Concorde's graceful 3 dimensional shape, the flight deck windows just look awful and those canards...good grief).
- And now the Boeing 787.
Yes, there are probably others that people find beautiful of course, and I've probably missed or forgotten some (I think the last version of the Comet, the Comet 4 strongly qualifies with the engines hidden in the wings) but the three above are the ones I find most aesthetically pleasing.
This is not about PV. This is about thermal solar collection, which also allows the storage of energy (focus sunlight on a tower, melt salt, store reasonably large amounts of energy in molten salt so as to be able to continue generating during the night).
http://buscon.rae.es/draeI/SrvltConsulta?TIPO_BUS=3&LEMA=lumia
It's in the DRAE. Might not be used much, but it's a perfectly cromulent word.
One Japanese car company even called a car Laputa.