Next step would be to start doing the same for PHP 5.3 (back porting from PHP 5.4, and later on also from PHP 5.5). This can be in use for RHEL 6.x (as LTS support for Debian Squeeze was recently finished).
A long time ago Ken Thompson wrote something called Reflections on Trusting Trust. If you've never read this, go read it right now. It's short and it's something everyone needs to understand. The paper basically explains how Ken backdoored the compiler on a UNIX system in such a way it was extremely hard to get rid of the backdoors (yes, more than one). His conclusion was you can only trust code you wrote. Given the nature of the world today, that's no longer an option.
Every now and then I have someone ask me about Debian's Reproducible Builds. There are other groups working on similar things, but these guys seem to be the furthest along. I want to make clear right away that this work being done is really cool and super important, but not exactly for the reasons people assume. The Debian page is good about explaining what's gong on but I think it's easy to jump to some false conclusions on this one.
This month I marked 171 packages for accept and rejected 42. I also sent 3 emails to maintainers asking questions. It seems to be that another quiet month is behind us. Nevertheless the flood of strange things in NEW continued this month. Hmm, weird world ..
Sorry for the total newb question (and if this is the wrong venue, I'll take this to a more appropriate sub), but I can't really seem to find much info about Deepin on this sub, or anywhere else on Reddit. I'm currently looking for a replacement distro, and as a predominately Windows user with some osx experience, Deepin seemed pretty intriguing. But all of the threads that mention Deepin are filled with comments like "sweet, going to try it now!" with little said on the actual results. Too bad, because it really seems like a nice looking distro, though I admit I know next to nothing in the broad scope of Linux distros.
I've tried Elementary a bit as well, but otherwise, I'm a total newb. This may probably be better on the /r/linux4noobs sub, but since Deepin seems pretty niche right now, I'm not sure how much traction I'd get.submitted by /u/thereisnoentourage2
Linus Torvalds: Things continue to be fairly calm, although I'm pretty sure I'll still do an rc7 in this series.
Hello, need some help from community. Feel free to ask question about current state.
Also, i will be prefer not disclosure much, for reason ms-skype dont ruin my work too early by do some changing protocol again. But you feel free to ask some technical details or at general, how it work at all./u/skypeopensource
Explain like it's a party and you're talking to the completely uninitiated and you make the mistake of saying "oh yea... that's an Apple, I don't do Apple." Then they mistake of asking "Well what do y'all use at work?" You must now explain Linux. Go. Please. So I don't have to ramble on about the symbiosis between embedded industrial systems and Linux ever again.submitted by /u/foreverska
Last week, we reported news on the release of the GParted 0.26.0 open-source partition editor software, and now Curtis Gedak informs us about the availability of GParted Live 0.26.0-1.
Softpedia has been informed by 4MLinux developer Zbigniew Konojacki about the general availability of his 4MLinux 17.0 independent, desktop-oriented GNU/Linux distribution.
Where can I find online references that describe a Linux/Unix project setup? Its quite surprising that googling for this turning up little useful references or tutorials.
I am looking for descriptions of general project setups; ie, 'Its usually considered industry standard to have a INSTALL file, ChangeLog file, Makefile, etc. And these files should reside in the root folder.'. More importantly I am looking for references that inform me of the format of these files and what each file does, ie, 'The ChangeLog format should be X and its purpose is Y'.
Coming from Windows development this is kindof new to to me.submitted by /u/sqzr
hackerboards: FriendlyARM's $60, open spec "NanoPC-T3" single-board computer runs Android or Linux on an octa-core Cortex-A53 SoC packed with wireless and media interfaces, plus 8GB eMMC.
Things continue to be fairly calm, although I'm pretty sure I'll still
do an rc7 in this series.
There's nothing particularly scary in here - there's a fix for a
long-standing infiniband interface problem, but since you actually
have to have the hardware for that, it's not like that is going to
affect all that many people, and the workaround was pretty
straightforward. The bulk of the rest is really just the normal random
noise. Drivers (sound, gpu, ethernet being the bulk of it),
architectures (arm, s390, x86), networking is the bulk of it.
Shortlog appended for your edification,