search for: lkl

...integrates with wifi (probably building on hwsim). The 'inside' interfaces aren't really a problem - just have a specific device ID for this, and then write a normal virtio kernel driver for it. The 'outside' interfaces are where my thinking breaks down right now. Looking at lkl, the outside is just all implemented in lkl as code that gets linked to the library, so in UML terms it'd just be extra 'outside' code like the timer handling or other netdev stuff we have today. Looking at qemu, it's of course also implemented there, and then interfaces with the re...

...integrates with wifi (probably building on hwsim). The 'inside' interfaces aren't really a problem - just have a specific device ID for this, and then write a normal virtio kernel driver for it. The 'outside' interfaces are where my thinking breaks down right now. Looking at lkl, the outside is just all implemented in lkl as code that gets linked to the library, so in UML terms it'd just be extra 'outside' code like the timer handling or other netdev stuff we have today. Looking at qemu, it's of course also implemented there, and then interfaces with the re...

...lding on hwsim). > > The 'inside' interfaces aren't really a problem - just have a specific > device ID for this, and then write a normal virtio kernel driver for it. > > The 'outside' interfaces are where my thinking breaks down right now. > > Looking at lkl, the outside is just all implemented in lkl as code that > gets linked to the library, so in UML terms it'd just be extra 'outside' > code like the timer handling or other netdev stuff we have today. > Looking at qemu, it's of course also implemented there, and then > in...

...lding on hwsim). > > The 'inside' interfaces aren't really a problem - just have a specific > device ID for this, and then write a normal virtio kernel driver for it. > > The 'outside' interfaces are where my thinking breaks down right now. > > Looking at lkl, the outside is just all implemented in lkl as code that > gets linked to the library, so in UML terms it'd just be extra 'outside' > code like the timer handling or other netdev stuff we have today. > Looking at qemu, it's of course also implemented there, and then > in...

On Fri, Jul 22, 2016 at 11:15:55AM +0200, Pino Toscano wrote: > On Tuesday, 12 July 2016 20:37:56 CEST Richard W.M. Jones wrote: > > Libguestfs 1.32 was released on 2016-01-06, which is over 6 months > > ago. In fact the previous stable version of libguestfs (1.30) was > > released on 2015-07-21, almost exactly 12 months ago. Are we heading > > for a 6 month release

On Sun, Mar 20, 2016 at 05:28:05PM +0200, Török Edwin wrote: > On 03/20/2016 14:30, Richard W.M. Jones wrote: > > v1 was here: > > > > https://www.redhat.com/archives/libguestfs/2016-March/thread.html#00157 > > Thanks, this is much better than looking at 'ts -i' output. > > BTW I have use 'git am' to apply them to latest git HEAD and try it.

On Windows, there exist at least two APIs for dealing with the Registry: The Win32 API (RegCreateKeyA, RegCreateKeyW, etc.) works with null-terminated ASCII or UTF-16 strings. The native API (ZwCreateKey, etc.), on the other hand works with UTF-16 strings that are stored as buffers+length and may contain null characters. Malware authors have been relying on the Win32 API's inability to

...) { + printf("error: SetValueKey: 0x%08x\n", rc); + exit(1); + } +} diff --git a/images/special b/images/special new file mode 100644 index 0000000000000000000000000000000000000000..8aa4f2254af7b52f0a79061a7288c2128eee7b63 GIT binary patch literal 8192 zcmeHLziU%b6h28COhb#$Ul4=fYx@MLKL!^^6)M(2Dk4tBk~GnVmnM=(q~Z`n)IUHs zhkyk;I61kvcM)}{1Q$C94muRkP^1{Y@7_GxmnJ$170!YC?z!ijckape-TNS?oV$K) zEF!{jqOm&ic<4<8s>CoT)Lkl$)hjY3XCy0gl9wVzMQ%!2(s-6IPszCCVDruT2G&8` z9AXO0qq1!fXx39_w@ooxh$5f}C<2OrBA^H;0*Zhlpa>`eioicbU^bI4nho&(K9Haf zz;(UVY8CyX^5XN4gX|5^c6x_M9~H=AzX(EF)H...

Hey hope this opne is a "make senser". Has anyone tried the "Subject line" combo?, I''ve compiled a dozen src.rpm kernel 3.0 and 3.1 packages with no luck to try native upstream Dom0 kernel support with no success, just a kernel oops and constant reboots. I followed Fedora''s wiki on building a custom kernel, even used F16''s .config which also was a

Hey hope this opne is a "make senser". Has anyone tried the "Subject line" combo?, I''ve compiled a dozen src.rpm kernel 3.0 and 3.1 packages with no luck to try native upstream Dom0 kernel support with no success, just a kernel oops and constant reboots. I followed Fedora''s wiki on building a custom kernel, even used F16''s .config which also was a

...xocI1D8LbGUPD^M-=9<!0o+Pn@>%t?b`O?q3U5^R7+UB>k0a zL45ml>jmYT<}1=pH#4NAvx>Eecbi%*ei*j*=i2UGkd}V)VR>lyM^q=#;(Meh3hE)% z#nl27(jB$?yTthyk5n9}@4LNO7mPu(Low)M43cmlC}l^2hePo~?|+Pmo%+jQ&5Hro zZ{B`zS~8C*<<<1sR}*Xd9(aBfMIYTF))x(sgq~_n=yq(0pWyjh`B4d;sf)k2Yu}EJ z7C#DJUu0MHiMsgklkLUDvg3+^ArF%k!zZ7AJ$NVZUy-+Q at wq9%9}3t09$yN&m3ZYw ztr5kKaZUfl`WYBA|J04)DMIUE#jIcNO$Ue9EIzz_s^`7h_Wrj{dlI!t<LgGlZl9rU zRf6XE0pFl*Z=!CK#AhQ1o#z^kiM95g%T={FF4^s>x1$;#exfLL$QJe3@&Uis)58aI zy&lmIjxcdmZ8J+!c~y(!`I)7{oIWWM>*4LQp51$^@jz<K<bx2SdkCZ6kPt_Nh!Cd` zA&j!(zCqcrX7x%~(...