Re: [Discuss] "Stack Script" (shell script) to build Ubuntu LAMP + on Linode
> From: greg.rundl...@gmail.com [mailto:greg.rundl...@gmail.com] On Behalf > Of Greg Rundlett (freephile) > > So, now that I'm looking at Vagrant, Juju [1], Ansible [2], Puppet [3] and > others as well as revisiting the general virtualization landscape (e.g. LXC, > Docker, CoreOS). > > Does anyone have their favorite deployment tips, playbooks or stories to > share? One of my coworkers is absolutely in love with vagrant, but I don't like it because it only plays easily nice with a local virtualbox. For him, he's doing experimental or development drupal work, that works great. For me, I'm operating infrastructure to support people, I need to interact with a much broader set of vmware, aws, digital ocean - which vagrant technically *can* do, but the added complexity negates the benefit. It's just a wrapper around ansible/whatever anyway. So I just use ansible and forget vagrant. The thing I like about ansible, besides the obvious - Ok, here's the obvious - In the past, machines were sometimes not well documented, and even if they were well documented, following the documentation was manual and error prone (hence you writing your script). By writing executable documentation, you get repeatability and it becomes trivial to spin up a development machine that exactly clones the production system, then make a change on development and test, and apply the change to production. Ok, so besides the obvious, I like the fact that I don't need a dedicated control machine. I can do stuff locally on my mac, which ssh's out to the target machines to do my work for me. I find, however, that if you have any windows administrators on your team, it becomes worthwhile to build a dedicated control machine - some linux box that everyone ssh's into in order to run ansible commands. Because even with cygwin, there is no ansible on windows. (Last I knew, as far as I know.) All that script stuff you wrote is how I used to do things. The language in ansible makes a lot of that stuff trivial. For example, how do you script "Go into the my.conf file, find the [FooBar] section, and if the 'whizbang' feature is in there, edit it to 5, otherwise create a line 'whizbang=5'" ... Yes it can be done, but it's a pain. But this type of configuration setting is just a line in ansible. Because that's what it's designed for. And what if assumptions were made in your script that are no longer correct when you run the script? The shell script is likely to fail horribly doing terrible things. Ansible will just report the error on the specific machine, and stop running on that machine. ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] [OT] digitizing old 78rpm records? ELP laser turntable services?
Also, I remember reading about using a flatbed scanner to rip old records. No pointers for you, but might be another area to research. --- Steven Santos Director Simply Circus, Inc. 86 Los Angeles Street Newton, MA 02458 P: 617-527-0667 F: 617-934-1870 E: ste...@simplycircus.com On Tue, Apr 7, 2015 at 10:57 PM, John Abreau wrote: > Thanks! That looks like a good starting point. > > On Tue, Apr 7, 2015 at 5:19 PM, Steven Santos > wrote: >> >> http://www.lp2cd.com/ >> --- >> Steven Santos >> Director >> Simply Circus, Inc. >> 86 Los Angeles Street >> Newton, MA 02458 >> >> P: 617-527-0667 >> F: 617-934-1870 >> E: ste...@simplycircus.com >> >> >> On Tue, Apr 7, 2015 at 12:12 AM, John Abreau wrote: >> > Doesn't do 78s; it only plays at 33.3 and 45 rpm. And the needle would >> > probably destroy the 78s while trying to play them. >> > >> > >> > On Mon, Apr 6, 2015 at 11:34 PM, Steven Santos >> > wrote: >> >> >> >> For $40 this might be worth trying: >> >> >> >> http://www.amazon.com/exec/obidos/ASIN/B0029QRA1U/transfermymusic-20 >> >> >> >> >> >> --- >> >> Steven Santos >> >> Director >> >> Simply Circus, Inc. >> >> 86 Los Angeles Street >> >> Newton, MA 02458 >> >> >> >> P: 617-527-0667 >> >> F: 617-934-1870 >> >> E: ste...@simplycircus.com >> >> >> >> >> >> On Sun, Apr 5, 2015 at 9:45 AM, Kent Borg wrote: >> >> > The frustrating (or amazing) thing about 78s is they are not >> >> > "information" >> >> > devices they are "industrial": They have big grooves that make big >> >> > excursions and they whip by really fast, all to make noise rather >> >> > directly. >> >> > There is no amplifier in an old Victrola, yet it makes a room full of >> >> > sound. >> >> > The 78 record isn't just information, it is a big part of the sound >> >> > reproduction system, and playing it is destructive. But you knew >> >> > that. >> >> > >> >> > I have a related problem, I inherited a zillion slides from my >> >> > parents' >> >> > world travels. How to digitize them? There were two obvious routes: >> >> > use >> >> > some >> >> > service or buy a slide scanner. Pricing the services was scary--not >> >> > bad >> >> > for >> >> > a few but crazy expensive for a lot. Looking that reviews of scanners >> >> > I >> >> > was >> >> > disappointed with the quality, and they can be slow. >> >> > >> >> > So I took the homebrew approach and crafted my own "scanner". Right >> >> > now >> >> > there is a lot of competition in the high-end camera market, so I >> >> > bought >> >> > the >> >> > fanciest DSLR any normal person should buy with his/er own money, and >> >> > I >> >> > am >> >> > taking pictures of the slides. >> >> > >> >> > A macro lens, a light box, a tripod, a black plastic food container >> >> > with >> >> > a >> >> > hole in it upside down to move the slide up from the >> >> > less-than-perfect >> >> > diffuser (use distance to diffuse and throw small patterning out of >> >> > focus), >> >> > a remote release, wooden bracing to hold the camera more steady...and >> >> > a >> >> > bunch of futzing...and I can see the film grain. >> >> > >> >> > My wife and I can digitize slides as fast as we can individually pull >> >> > them >> >> > out of a Carousel, puff off the dust, place them in the upside down >> >> > food >> >> > container, and return them. In about the time that it would take to >> >> > pack >> >> > up >> >> > a batch to send out, we are done with that batch. Well, not done yet, >> >> > but on >> >> > a recent long weekend visit to the ol' homestead we digitized over >> >> > four >> >> > thousand slides, and that's a good fraction of the total >> >> > >> >> > >> >> > As for 78s, I might be crazy...but a 78 side usually only runs >> >> > 3-something >> >> > minutes of low-fidelity sound. There isn't much fundamental >> >> > information >> >> > there, a high quality photo (or several stitched) of a record side >> >> > might >> >> > capture it all. Then it is a "simple matter of programming" to >> >> > recover >> >> > the >> >> > sound! You could even crop out the label details for your metadata. >> >> > >> >> > Googling "optical record groove software"... >> >> > >> >> > Amazing recovering of audio from paper recordings: >> >> > >> >> > >> >> > https://mediapreservation.wordpress.com/2012/06/20/extracting-audio-from-pictures/ >> >> > >> >> > A hacker who demonstrated he could get something audible from LP >> >> > photos: >> >> > http://www.cs.huji.ac.il/~springer/DigitalNeedle/index.html >> >> > >> >> > There are plenty of general purpose open source imaging processing >> >> > libraries >> >> > available, maybe there is specific useful software available from the >> >> > Irene >> >> > project?? >> >> > >> >> > >> >> > -kb >> >> > >> >> > ___ >> >> > Discuss mailing list >> >> > Discuss@blu.org >> >> > http://lists.blu.org/mailman/listinfo/discuss >> >> > >> >> ___ >> >> Discuss mailing list >> >> Discuss@blu.org >> >> http:
[Discuss] Ubiquiti Networks is creatively violating the GPL
I've mentioned Ubiquiti Networks's products on the list here a few times, and have since purchased some of their hardware. Disappointingly I read the posting below. -Tom Four ways Ubiquiti Networks is creatively violating the GPL http://libertybsd.net/ubiquiti/ ...they have been violating the GPL. However, because they did it creatively, most people don't know about it, and Ubiquiti still hasn't come into compliance. ... [They refuse] to provide the source to their modified bootloader, even though they made changes that introduced security vulnerabilities. ... It would be natural to think that the binaries that Ubiquiti provides were compiled from the source code that Ubiquti provides. As it turns out, for a large number of their releases, the kernel source given does not correspond to the kernel in the official firmware images. ... It's possible that this was just a mistake, but remember that people have complained about this without much of a response. ... ...I have been trying to contact Ubiquiti for the past year about the issue of the u-boot source code. ... In fact, I even got a copyright holder of u-boot to ask for the source, and they still haven't provided it. From my conversations with Ubiquiti, I have found that they claimed that it's alright to refuse to provide source code to GPL-licensed software if "This decision was taken with the security of the users in mind". ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Ubiquiti Networks is creatively violating the GPL
I contacted Riley to see if he's brought this to the FSF or Software Freedom Conservancy for help. It's good to ask people politely to comply with the law; and good to out them when they persistently refuse. Greg Rundlett http://eQuality-Tech.com http://freephile.org On Wed, Apr 8, 2015 at 1:37 PM, Tom Metro wrote: > I've mentioned Ubiquiti Networks's products on the list here a few > times, and have since purchased some of their hardware. Disappointingly > I read the posting below. > -Tom > > > Four ways Ubiquiti Networks is creatively violating the GPL > http://libertybsd.net/ubiquiti/ > > ...they have been violating the GPL. However, because they did it > creatively, most people don't know about it, and Ubiquiti still hasn't > come into compliance. > ... > [They refuse] to provide the source to their modified bootloader, even > though they made changes that introduced security vulnerabilities. > ... > It would be natural to think that the binaries that Ubiquiti provides > were compiled from the source code that Ubiquti provides. As it turns > out, for a large number of their releases, the kernel source given > does not correspond to the kernel in the official firmware images. > ... > It's possible that this was just a mistake, but remember that people > have complained about this without much of a response. > ... > ...I have been trying to contact Ubiquiti for the past year about the > issue of the u-boot source code. ... In fact, I even got a copyright > holder of u-boot to ask for the source, and they still haven't > provided it. > > From my conversations with Ubiquiti, I have found that they claimed > that it's alright to refuse to provide source code to GPL-licensed > software if "This decision was taken with the security of the users in > mind". > > ___ > Discuss mailing list > Discuss@blu.org > http://lists.blu.org/mailman/listinfo/discuss > ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
[Discuss] Request to the community
Hello Boston Linux Community! I am looking for three software developers who would be willing to discuss their experiences writing and developing open source software products. The conversation will take about 30 minutes and I will be asking about the differences between open source and proprietary software development. This is not a job interview nor is it a sales/marketing pitch. I will not ask you to discuss anything that is proprietary or personal. Why am I doing this? I recently applied for a Product Manager position at a company that develops open source products. They like my skills and background but asked that I get a better understanding of how the Open Source development process really works. The best way to move up the learning curve is to talk to people who have the actual experience. Please e-mail me directly if you are interested. I cannot offer you any compensation but I will buy you a round of wings and beer should I land this position. Best regards, Bruce -- Bruce Wolfeld brw...@gmail.com ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Request to the community
Good one. Actually, and going along with that, I would say that in the development cycle, there is a big difference. I had never actually experienced a windows shop development environment until recently. Since we are open, and share code, we don't really need to worry about things like proprietary files going along with our code to keep it "secret" or encrypted. Like for example .snk files. I work on a fork of remastersys (linuxrespin now) and we are completely open with our code. We work together using GIT and share updates. We have a changelog and chat in IRC. Sometimes we use ventrillo to collaborate. We actually meet in person also. From what I've seen in a few meetings I attended for Windows devs... they have this thing called a Code Review. I like to call it "Show and tell for programmers". Even if they just changed one thing from 10 to 21, they show it. Their coding is inferior. I apologize, but it is in my experience. Instead of functional requirements documents or business requirements documents, they call new "features" bugs or issues. Maybe it's just the shop I have seen. Open Source development teams are different. It gets really interesting when you have Free software people working with Open Source People. Then, it's a challenge. The Open people might want to use Google Hangouts and groups while the Free Software people would never and want to use Etherpad. Anyway, if I could, I would always select in this order: 1. Free Software Project 2. Open Source Project 3. No Projects or the long sleep... Check out Karl Fogel's book on projects: http://www.amazon.com/Producing-Open-Source-Software-Successful/dp/0596007590 Quoting Jack Coats : unless you are Ubiquiti evidently ... :-( ... bummer, I like their equipment. ... ubnt.com Their equipment is based on open source software, but they don't seem to think that they have to make available what they use, just some version. On Wed, Apr 8, 2015 at 6:03 PM, Dan Ritter wrote: On Wed, Apr 08, 2015 at 04:26:14PM -0400, Bruce W wrote: > Hello Boston Linux Community! > > I am looking for three software developers who would be willing to discuss > their experiences writing and developing open source software products. > The conversation will take about 30 minutes and I will be asking about the > differences between open source and proprietary software development. This > is not a job interview nor is it a sales/marketing pitch. I will not ask > you to discuss anything that is proprietary or personal. It's really very simple. When you work in proprietary software, any time you buy somebody else's product/library/application/service, you need to pay them and also follow the terms of their proprietary license. When you work in open source software, you need to follow the terms of their open source license. When you produce whatever product or service, you need to be in compliance with the terms of the licenses of all the products you used, proprietary and open source, or else you will be sued. See? Very simple. -dsr- ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss -- <> ... Jack "Whatever you do, work at it with all your heart"... Colossians 3:23 "Anyone who has never made a mistake, has never tried anything new." - Albert Einstein "You don't manage people; you manage things. You lead people." - Admiral Grace Hopper, USN "Tell me and I forget. Teach me and I remember. Involve me and I learn." - Ben Franklin ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Request to the community
I had the same math requirement for my CS degree in '74. Many people have argued that CS doesn't need anything but programming language classes to code. They are right. But it is the rest that gives the perspective to design, test, innovate, in addition to code. Reasonable basic coding doesn't need a well rounded background, but a reasonable coder isn't all they cold be with the proper tools. The same argument goes for '3 month coder mill coders' vs college graduates. But as I retire, what I think means less to others than it used to. ... (queue the theme to Lion King - about the circle of life) ... Time to go be grumpy elsewhere ... Jack On Wed, Apr 8, 2015 at 7:44 PM, Marcia K Wilbur wrote: > Well, that's actually a relief to hear - somewhat. > The computer science program here requires the equivalent to a minor in > math. In fact, with 2 more courses, one could have a double major. Calc 1, > 2, 3, Diff Q, and Probability are required. > Yea, from my work experience with Windows, I don't think someone who makes > a min larger than a max has much math background... > > > Quoting Richard Pieri : > > On 4/8/2015 7:55 PM, Marcia K Wilbur wrote: >> >>> Even if they just changed one thing from 10 to 21, they show it. >>> Their coding is inferior. I apologize, but it is in my experience. >>> >> >> Your experience isn't a Windows thing. It's a "your company hires as >> close to minimum wage as it can get away with because code monkeys are a >> dime a dozen" thing. See previous discussion about the value of hard math >> as a part of a well-rounded education. It's also a "performance reviews are >> based on quantity of code check-ins rather than quality of code check-ins" >> thing. >> >> -- >> Rich P. >> ___ >> Discuss mailing list >> Discuss@blu.org >> http://lists.blu.org/mailman/listinfo/discuss >> > > > > ___ > Discuss mailing list > Discuss@blu.org > http://lists.blu.org/mailman/listinfo/discuss > -- ><> ... Jack "Whatever you do, work at it with all your heart"... Colossians 3:23 "Anyone who has never made a mistake, has never tried anything new." - Albert Einstein "You don't manage people; you manage things. You lead people." - Admiral Grace Hopper, USN "Tell me and I forget. Teach me and I remember. Involve me and I learn." - Ben Franklin ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Request to the community
Well, that's actually a relief to hear - somewhat. The computer science program here requires the equivalent to a minor in math. In fact, with 2 more courses, one could have a double major. Calc 1, 2, 3, Diff Q, and Probability are required. Yea, from my work experience with Windows, I don't think someone who makes a min larger than a max has much math background... Quoting Richard Pieri : On 4/8/2015 7:55 PM, Marcia K Wilbur wrote: Even if they just changed one thing from 10 to 21, they show it. Their coding is inferior. I apologize, but it is in my experience. Your experience isn't a Windows thing. It's a "your company hires as close to minimum wage as it can get away with because code monkeys are a dime a dozen" thing. See previous discussion about the value of hard math as a part of a well-rounded education. It's also a "performance reviews are based on quantity of code check-ins rather than quality of code check-ins" thing. -- Rich P. ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Request to the community
unless you are Ubiquiti evidently ... :-( ... bummer, I like their equipment. ... ubnt.com Their equipment is based on open source software, but they don't seem to think that they have to make available what they use, just some version. On Wed, Apr 8, 2015 at 6:03 PM, Dan Ritter wrote: > On Wed, Apr 08, 2015 at 04:26:14PM -0400, Bruce W wrote: > > Hello Boston Linux Community! > > > > I am looking for three software developers who would be willing to > discuss > > their experiences writing and developing open source software products. > > The conversation will take about 30 minutes and I will be asking about > the > > differences between open source and proprietary software development. > This > > is not a job interview nor is it a sales/marketing pitch. I will not ask > > you to discuss anything that is proprietary or personal. > > It's really very simple. > > When you work in proprietary software, any time you buy somebody else's > product/library/application/service, you need to pay them and also follow > the terms of their proprietary license. > > When you work in open source software, you need to follow the > terms of their open source license. > > When you produce whatever product or service, you need to be in compliance > with the terms of the licenses of all the products you used, proprietary > and open source, or else you will be sued. > > See? Very simple. > > -dsr- > ___ > Discuss mailing list > Discuss@blu.org > http://lists.blu.org/mailman/listinfo/discuss > -- ><> ... Jack "Whatever you do, work at it with all your heart"... Colossians 3:23 "Anyone who has never made a mistake, has never tried anything new." - Albert Einstein "You don't manage people; you manage things. You lead people." - Admiral Grace Hopper, USN "Tell me and I forget. Teach me and I remember. Involve me and I learn." - Ben Franklin ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Request to the community
On Wed, Apr 08, 2015 at 04:26:14PM -0400, Bruce W wrote: > Hello Boston Linux Community! > > I am looking for three software developers who would be willing to discuss > their experiences writing and developing open source software products. > The conversation will take about 30 minutes and I will be asking about the > differences between open source and proprietary software development. This > is not a job interview nor is it a sales/marketing pitch. I will not ask > you to discuss anything that is proprietary or personal. It's really very simple. When you work in proprietary software, any time you buy somebody else's product/library/application/service, you need to pay them and also follow the terms of their proprietary license. When you work in open source software, you need to follow the terms of their open source license. When you produce whatever product or service, you need to be in compliance with the terms of the licenses of all the products you used, proprietary and open source, or else you will be sued. See? Very simple. -dsr- ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Request to the community
On 4/8/2015 7:55 PM, Marcia K Wilbur wrote: Even if they just changed one thing from 10 to 21, they show it. Their coding is inferior. I apologize, but it is in my experience. Your experience isn't a Windows thing. It's a "your company hires as close to minimum wage as it can get away with because code monkeys are a dime a dozen" thing. See previous discussion about the value of hard math as a part of a well-rounded education. It's also a "performance reviews are based on quantity of code check-ins rather than quality of code check-ins" thing. -- Rich P. ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
