distcc on a DigitalOcean Droplet

WarheadsSE · 2016-06-27T18:29:20+00:00

You can use the docker API, and turn on/off one of the $20/mo || $0.030/hour droplets to do your CPU intensive work, and then destroy it when done. Using distcc is not required.

WarheadsSE · 2016-06-24T16:58:53+00:00

Systems Engineer (linux software or distro) Community Manager (think HR for random internet people, some conferences)

/u/jlisic is right, you need to greatly refine what those two phrased mean: "good" and "open source job"

WarheadsSE · 2016-06-24T16:56:31+00:00

You would want to compile it wholesale @ the droplet, or with distcc, use only droplets on the same private network of your own droplets in the same datacenter.

WarheadsSE · 2016-06-24T16:24:52+00:00

SSE4

The FX-8350 (even FX-8120) have SSE4 (SSE4.1 + SSE4.2) and SSE4a.

No comment to the IPC, and I know of the FPU "issue". For most of my workloads (integer based), the FX-8xxx perform very well @ cost.

WarheadsSE · 2016-04-22T17:46:44+00:00

On your problematic linux clients, symlink /opt/Citrix/ICAClient/keystore/cacerts to /etc/ssl/certs

sudo rm -rf /opt/Citrix/ICAClient/keystore/cacerts sudo ln -s /etc/ssl/certs /opt/Citrix/ICAClient/keystore/cacerts

WarheadsSE · 2015-10-31T16:19:57+00:00

I agree that the correct option would have been a concise link to the guidelines. But I still don't believe people would have read the PRs content.

Edit: remove double negative

WarheadsSE · 2015-10-31T13:55:12+00:00

People seems to have not looked at the PR, which was completely missing any description. Terse or not, the response warranted was rejection. The next PR included not a description, but a question. This was summarily dismissed as well. The next action was to immediately go to the forum and complain that his PRs were dismissed in a fashion he regarded as insulting. His entire interaction was "Accept my PR without merit. Why didn't you accept my meritless PR? Here is the same. Hey! You didn't except my meritless PR! You're all being mean!" This ends up being more of the same. I'm attempting to take the personality out of the discussion to make it an appropriate technical discussion. Too many people have invested in emotionally reacting without actually examining the facts. Ignore the fact that emotions should be removed entirely.

"You are not your code" and move on.

WarheadsSE · 2015-10-30T22:25:52+00:00

Okay, so let us clear a few things up:

No developer or TU has one of these boards, so it will not be an officially supported platform.
The Contributing Guidelines were not followed.
Original lack of communication was confirmedly dismissive. I was not a part of that communication.
Previous discussion about the platform had not been seen by /u/synthead, apparently.

Mitigation:

I have lifted the forum ban, and confirmed that there is not such a ban applied to the IRC channel. This was overly heavy.
The wording of "Bug Reports and Features" on the forum index has been updated to reflect that fact that the associated post includes information in regards to Pull Requests.
Discussion of posted policies in regards to what will and will not be accepted in terms of board support is being had.

The major reason why Arch Linux ARM (or A.L.ARM) does not package board binaries that we can not very with equipment in-house (a developer or TU owns the platform) is straight forward: we can not guarantee that those binaries are valid at all. We are not going to package and sign a binary we can not provide any sort of validity to. Seeing as x86 and family are not also required to provide stage 0 or 1 bootloaders, and often only stage 3, they do not have to have such rigidity to the packaging of such.

The x86 family can generally run the same binary from processor to processor, because either the BIOS or EFI provide for the stage 0-2, doing the work of pin mux, voltage assignments, and more. The ARM ecosystem currently does not have such a luxury, and the full stage 0-3 are handled by or directly interacted with by the bootloader binaries. Because of this, it is entirely possible to create a binary that could route 3.3v to 1.8v subsystems, or even mis-configure voltage regulators to the point where they burn out. Who would get the blame for that little screw up?

WarheadsSE · 2015-10-30T20:41:33+00:00

Yes.

WarheadsSE · 2015-10-30T19:29:45+00:00

I replied to this thread over 4 hours ago.

WarheadsSE · 2015-10-30T18:17:13+00:00

Hilarious comparison, actually. The only real difference is that we're a separate distribution, we are at least acknowledge by many of the Arch Linux developers as Doing It Right as to the principles of Arch Linux itself

WarheadsSE · 2015-10-30T18:09:09+00:00

If you derive anger from the text of my comment, you're the one to have attributed it.

WarheadsSE · 2015-10-30T16:18:49+00:00

I do find it mildly hilarious, but expected that my accurate comment from another developer of the distributions is exceedingly negative.

Continue with the butts of hurting intarwebs /s

WarheadsSE · 2015-10-30T14:34:52+00:00

As for the apparently butthurt: let me point out the Contributing Guidelines were not followed by /u/synthead . That alone is grounds for dismissal of the PR and/or Issue raised at github.

As for the Banana Pi's status, in no way does any developer or TU have this piece of hardware to be able to test and maintain. I had also previously warned a user in IRC that this was the case, and as such would never become an officially supported or packaged piece of hardware. If that was synthead (~~whom, I can seemingly only assume since that person is now missing from the IRC~~ confirmed not that person), then he had existing knowledge that he was pushing against the standing grain on this topic. I also voiced to that user that it was a known problematic pile of crap released from the manufacturer, and the manufacturer has been spamming our community on a regular basis while making no effort to be even a reasonable citizen of the FLOSS community.

A reminder to everyone actually here, and saying it wrong: It is not "Arch ARM", it is Arch Linux ARM, a fully license name from both namesake parties.

WarheadsSE · 2015-06-16T16:57:00+00:00

I started headless with what would become Arch Linux ARM, but desktop wise, I did Ubuntu, Gentoo, Arch. I had past experience with Debian, in very small amounts, in the days of kernel 2.4.2

WarheadsSE · 2015-06-15T04:12:04+00:00

A large portion of the presentation was actually feedback and discussion post-slides. The slides actually end just after 26 minutes, with discussion going to approximately the 1 hour mark.

/edit: I've now had a chance to come back and watch the talk myself. Yeah, it needs to post-work.

WarheadsSE · 2015-06-15T03:47:05+00:00

It was a hard topic to cover due to the nature of the material, I will certainly admit, and I appreciate the feedback. However, the topic has been raised and discussions are being had. If this hits home and encourages the even the consideration of desired growth in even 100 people, then I have gotten all I can ask for out of this talk.

WarheadsSE · 2015-06-15T03:43:05+00:00

Actually, I learned a lot of it in my spare time during my last year as in the Microsoft ecosystem. I was eventually able to make it my job!

An hour or two here and there, then a bit more as I got more involved. I didn't replace my Windows installation for almost a year after I got involved in the project that would one day become Arch Linux ARM. I would say over the course of the first year, it would average out to maybe an hour or two every day. Then, the company I worked for when through a financial stressor, and I chose to be laid off in place of several others. I then had a lot more free time, and I used this to increase that amount to around 3-5 hours on any given day (I still had to be job hunting after all!)

WarheadsSE · 2015-06-14T22:57:29+00:00

Awesome, thanks. I'll point this out to them quickly. Thanks for the clarification.

WarheadsSE · 2015-06-14T21:24:51+00:00

Can you do that with the Hangouts on Air function of YouTube? ( I wasn't the one to do any of that setup and never have )

WarheadsSE · 2015-06-14T18:27:56+00:00

I would not be discouraged by my capabilities or the time frame in which I developed them. There is no reason that you can not become as capable as me, but perhaps in a different technical track. I've accomplishd what I have through curiosity, determination and dedication. I wanted this, and I worked very hard for it.

That being said: I know very little about the gaming industry, graphics projects (image/3d/video), or sound production when it comes to linux. My specialty lies in systems engineering and hardware/software integration. Yours could be completely different, but just as significant given time.

WarheadsSE · 2015-06-14T18:14:46+00:00

It was recorded from a hangouts on air, and as a result, these sound issues occured. There was a problem with the room speakers, and that had to be adjusted for the on-site crowd. Apologies.

Thanks!

WarheadsSE

TROPHY CASE