5 ms·
Holy crapola - they are putting a Lua interpreter in the kernel, and it has access to some limited calls. This is partly driven by "we need device drivers and
by lifeisstillgood 13y ago
Holy crapola - they are putting a Lua interpreter in the kernel, and it has access to some limited calls.
This is partly driven by "we need device drivers and no one understands C anymore", partly because it's cool, but mostly because Moores law is still alive and well. They are putting a scripting language in a kernel ! Forget write your app in python / perl / Ruby then optimise in C - the raw power argument is going to overwhelm us all.
I heard a stat the other day - that a greetings card, the kind that plays a silly tune, has more processing power than all computers on the planet in 1960. And we should expect a similar growth in the next 50 years. Even if that's out by two orders of magnitude just let it sink in.
I think we are at a Cambrian explosion period - where the goal is to try out every possible new body shape, as fast as possible and see which ones get the Darwin seal of approval.
New organisation forms are possible, some for the first time in human history, new ways of thinking and communicating - it's stuff like this that makes one realise the water around the frog is getting hotter.
(Still it's worth remembering that most train companies in 19C England failed and the average return for stockholders was 10% - just because the world will change beyond recognition does not mean industry stocks is a great return)
- recuter 13y agoLua can be sandboxed quite effectively, can you elaborate on your concerns?
- vor_ 13y agoWhat concerns?
- scott_karana 13y agoGP was probably in response to ketralnis' comment. :)
- ketralnis 13y agorecuter's comment already existed when I wrote mine, so it couldn't be in response to me
- robert-wallis 13y agosprintf buffer overflow in the string library https://github.com/LuaDist/lua/commit/52eff16f51750cf47afaa5ac27a8705a1c580859#diff-5fa4a598e8e43f285d6fb9add1a47182R890 https://github.com/LuaDist/lua/commit/52eff16f51750cf47afaa5... This library is not included in NetBSD as far as I can tell: http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/modules/lua/?only_with_tag=MAIN http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/modules/lua/?onl... But it's an indication that it shouldn't be included in a Kernel.
- tedunangst 13y agoYou linked to a 24,000 line diff to point out what exactly?
- robert-wallis 13y agowait for it... the exact section of the code that contains the "sprintf" I mentioned will pop into your screen. Just be patient.
- Sanddancer 13y agoThere were buffer overflows in the Linux kernel in 2012 ( http://www.securityfocus.com/bid/53401 http://www.securityfocus.com/bid/53401 ). Should we not have filesystems in the kernel either?
- pdpi 13y agoWell... No, if you're a proponent of the micro-kernel design.
- robert-wallis 13y agoCertainly the string library, of all places, should be using secure code. I'm sure there are sooo many people running Linux on pre-OSX Mac harddrives formatted with HFS that could be hacked with a buffer overflow. Are you seriously arguing that buffer overflows in the kernel are not a big deal?
- tonyplee 13y agoHaven't they been keep saying that about JAVA - Just Another Vulnerability Announcement? Mac just turn off JAVA completely in user space and NetBSD is putting Lua in kernel? NSA: "I have a dream! Someday, a script language will be in BSD kernel, so I can ping an script into the kernel" :-)
- ketralnis 13y agoKernel programming is an eternal struggle between people trying to pull more into the kernel for performance, and people trying to pull stuff back out for safety and modularity. We've all seen the arguments about the in-kernel HTTP daemons and whatnot. I tend to be on the side that says that more things should be pulled out. > This is partly driven by "we need device drivers and no one understands C anymore" I don't buy this argument. Who are the people * Using NetBSD * having cutting-edge hardware for which drivers don't exist * deciding to write device drivers * that have device specs/docs needed to write them * that don't know/want to use C * that would do it if only they could write it in a scripting language? Do these people exist? I assert that the far more common case is that the device specs, documentation, BIOS, etc. aren't accessible. If that's true, they couldn't write the driver regardless of the language, C is hardly the limiting factor here
- gwu78 13y ago"Do these people exist?" This is spot on. When you hear NetBSD developers arguing about proposals (or commits, ex post facto, like here), there is often mention of "users". But these are mostly fictional. I think it's safe to say most NetBSD users are comfortable working with C. I reckon it's not much different with OpenBSD: most changes they make are for the benefit of the developers themselves, to suit personal preferences, than for the benefit of other "users". (And that's perfectly acceptable, I think.) Of course, these changes can benefit users beyond simply those who make them and those who approve them, but those users are not the ones driving the changes.
- groovy2shoes 13y agoThis is spot on. When you hear NetBSD developers arguing about proposals (or commits, ex post facto, like here), there is often mention of "users". But these are mostly fictional. I think this is true of much open source software. Just for the sake of example, a few years ago the Gnome devs removed some printer config options because they decided the "users" didn't need so many options. It's not that Gnome doesn't have users, but the developers seemed to have some notion of a type of user that didn't really exist. I think more often than not, fictional users are used as justification for the addition of some nice-to-have feature, but of course I'm just speculating.
- fafner 13y agoAre they using regular Lua? Because LuaJIT can actually be quite fast. Snabb Switch is written mostly in Lua and it features Linux userland ethernet device drivers. http://blog.lukego.com/blog/2013/01/03/snabb-switchs-luajit-ethernet-device-driver/ http://blog.lukego.com/blog/2013/01/03/snabb-switchs-luajit-... (edit: link to the code https://github.com/SnabbCo/snabbswitch/tree/master/src/apps/intel https://github.com/SnabbCo/snabbswitch/tree/master/src/apps/...) btw. there once was a project which added a Scheme interpreter to the Linux kernel. Sadly it's dead now: http://www.abstractnonsense.com/schemix/ http://www.abstractnonsense.com/schemix/
- maximilianburke 13y agoI'm not sure they would be well suited together, NetBSD has a huge list of old hardware they support; I don't think Mike Pall will be porting LuaJIT to m68k anytime soon.
- baldfat 13y agoMoore's law will be over by 2025 (We have 12 years or so). Semi-conductor will allow a separation of just 3 - 5 atoms to the conducting part. The belief is that quantum physics will allow the electrons to go through "walls" at that point and the switch will always be closed. I think we will go back to the days of 640k where there is a ceiling and we will just have to refine for "large" projects. Software and not hardware will be Moore's law BUT only for a extreme circumstances. The Golden Age is coming to an end in our life time.