sergiolp

7 ms·

1.
by sergiolp 10y ago
For Mail/Calendar/Contacts/Tasks you should really consider Evolution. I've switched ~2 years ago, and it's amazing. Stable, sleek, and with tons of options. It has a bad reputation because, back in the day, it was
2.
by sergiolp 10y ago
Centralization is a _huge_ privacy issue. Specially when combined with real world data, like a phone number. Let's assume OWS is playing nice, and they really don't store any relevant metadata. How can we be sure that a third part
3.
by sergiolp 10y ago
That comes from upstream's README.md. I've never payed any attention to it, but now that you've pointed it out, I'm seriously considering changing that paragraph, or adding a note/disclaimer somewhere. After all the
4.
by sergiolp 10y ago
Telegram-FOSS (the FOSS friendly fork you can find on F-Droid, not the official app on Play Store) maintainer here. Telegram is NOT a "secure messaging app".
5.
by sergiolp 10y ago
Three days ago, a Jolla C replaced an iPhone 5S as my main phone. To be fair, me using iOS was just a kind of an experiment. Before that, I was using a CM build without Google Apps using FDroid as unique app repository. I must say that, whi
6.
by sergiolp 10y ago
At flexVDI, we use Xamarin for building our macOS client (Xamarin.Mac), sharing most of the code with the client for Windows, built with Visual Studio. Both of them, link against a shared library which implements core functionality, written
7.
by sergiolp 10y ago
I'm not talking about the efficency of the resulting binary, but the "distance" from what the programmer is thinking , to what the machine will really do. Compiler optimizations aside, C does a pretty good job at this. It&#x
8.
by sergiolp 10y ago
I can't help but think they're trying to fix something that isn't broken at all. Adding new abstraction layers rarely helps when doing systems programming. You (as in "the developer") want to be as near to the machi
9.
by sergiolp 11y ago
Sorry if I'm too harsh, but saying that ZoL is "rock solid" and "production ready" sounds like a joke to my ears. ZFS is an extremely complex filesystem, and it took Sun _years_ of internal testing first, and hundre
10.
by sergiolp 11y ago
The OSF vs GNU Mach thing is not a problem. It was years ago, but I managed to run a Hurd translator statically linked against a slightly modified glibc on OSF Mach (the one bundled with MkLinux, you can see its code on my repo https:&#x2F
11.
by sergiolp 11y ago
A curious (and probably unintended) side effect, is that if its implementation of the Mach API is complete enough, this should allow to run Hurd user space server/translators on FreeBSD. Not sure if useful, but would be cool (in a weir
12.
by sergiolp 11y ago
Communication would've happened, but probably between far less actors. So, you have a communication channel which is orders of magnitude slower, and bigger communication needs. Not good. That said, about the reliability point, I agree
13.
by sergiolp 11y ago
I don't know about the others, but at least both QNX and Minix3 cheated a little, i.e. allowing servers to write directly to other user space programs. Also, the presence of microkernel+multiserver systems is still quite symbolic in co
14.
by sergiolp 11y ago
You've just hit the nail right on the head.
15.
by sergiolp 11y ago
I don't know about other implementations, but I remember the original design of l4hurd (based on L4Ka), was even more complex. I'd same this applies to all "pure" multiserver designs.
16.
by sergiolp 11y ago
Some years ago, I've spent a lot of time studying GNU Mach and Hurd (I've also made some small contributions). I think I can say that I now both pretty well. I even started a project to preserve OSF Mach + MkLinux source code ( ht
17.
by sergiolp 12y ago
Of course, a virtualized Guest will have a performance penalty. With that phrase I meant that, following this guide, you can make use of the Virtualization Extensions from the Cortex-A7 which powers the Raspberry Pi 2. This is pretty useful
18.
by sergiolp 12y ago
Sorry, we've underestimated the attention this post was going to get. We've just assigned more resources to that machine. Let's hope that'll be enough to bear with the warm, warm hug of Hacker News ;-)
19.
Enabling KVM Virtualization for Raspberry Pi 2(blog.flexvdi.es)
59 points by sergiolp 12y ago|20 comments
20.
by sergiolp 12y ago
While reading "LINUX is obsolete (1992)", this relatively unknown article has come to my mind. It's a pretty good read about a real world implementation of a microkernel architecture, and the tricks they had to do to obtain a
21.
Linux on the OSF Mach3 microkernel (1996)(bat8.inria.fr)
13 points by sergiolp 12y ago|4 comments
22.
by sergiolp 12y ago
I did some small contributions to GNU Hurd years ago, but still, this made me giggle: Of course 5 years from now that will be different, but 5 years from now everyone will be running free GNU on their 200 MIPS, 64M SPARCstation-5.
23.
Running Fuzix OS on Z80pack(sinrega.org)
1 points by sergiolp 12y ago|0 comments
24.
by sergiolp 12y ago
Nice, just a few weeks ago I finished my port of socz80 to DE0-nano ( https://github.com/slp/socz80-de0_nano ). Apparently, the original socz80 is already supported on Fuzix, so it should run here too. More retro-fun!
25.
by sergiolp 12y ago
On the linpack test, the KVM domain should have been configured for inheriting the CPU extensions from the host (or, alternatively, cherry picking the extensions relevant for such test). For the rest, I think an updated KVM vs. Xen vs. VMWa
26.
Enabling KVM virtualization on ARM(blog.flexvm.es)
30 points by sergiolp 12y ago|3 comments