On Tuesday 16 May 2017 06:07:12 pm Rick Thomas wrote:
> We have two alternatives, as I see it.
>
> 1) What we’re doing now: hold off on any updates until the attached bug is
> fixed by Paravel Systems.
>
That's the least risky.
Assuming a decent firewall, that's what I would do.
( Note: Par
On May 17, 2017, at 08:25, Rob Landry <41001...@interpring.com> wrote:
> There are two ways to insure you don't get put off the air by an update. You
> can test each update on a duplicate Rivendell machine that is not on the air,
> and only after verifying that it doesn't break Rivendell on that
On May 16, 2017, at 15:10, Rick Thomas wrote:
> We’ve been holding off installing the Rivendell 2.15.3-1 update, hoping to
> see a fix for this bug.
>
> But with all the activity over the NSA zero-day exploits released a few
> months ago, it’s becoming imperative that we get the security updat
On Wednesday 17 May 2017 09:59:57 am Richard Gorbutt wrote:
> Many way to mitigate potential disasters. Always protect the cash-flow (and
> have fun!)
In case Richard forgot to mention it, always protect the cash-flow !!
On Wednesday 17 May 2017 09:57:02 am Tom Van Gorkom wrote:
> So I'm curious
On Wed, 17 May 2017, Tom Van Gorkom wrote:
So I'm curious as to whether any of you have a way to log into your airplay
machines or other boxes on Riv at night or weekends from home if something
isn't right? I use TeamViewer and it has saved me lots of time when I get a
call that something isn't
We have VPNs into our station from remote locations and I can bring up a VPN on
my laptop if I’m
traveling. From there I can use ssh with X11 forwarding or start a VNC session.
Other than that, the internal network is pretty much hidden from the public
internet.
Running pfSense on your choice o
Broadcaster Engineers have for years dined on stories of various OS patches
breaking systems and will continue to do so. Even very high level ultra
high availability broadcasters like the ones I work for etc. However we are
very risk averse so no upgrades ever get applied in a production
environmen
-5535
Cell: (703) 585-2101
A Service of the Independent Media Foundation
From: rivendell-dev-boun...@lists.rivendellaudio.org
on behalf of Tom Van Gorkom
Sent: Wednesday, May 17, 2017 9:57:02 AM
To: Cowboy
Cc: Rivendell-Dev
Subject: Re: [RDD] Please fix this
So I'm curious as to whether any of you have a way to log into your airplay
machines or other boxes on Riv at night or weekends from home if something
isn't right? I use TeamViewer and it has saved me lots of time when I get
a call that something isn't sounding right or shouldn't be playing on the
On Wednesday 17 May 2017 08:25:38 am Rob Landry wrote:
> Myself, I prefer
> the second approach, not fixing what isn't broken.
Which I've been advocating for many, many years.
Sometimes Rob and I disagree.
Through his entire post, this is not one of 'em !
Some of you know that I wrote Spam-
Doing *any* updates on a working on-air Rivendell system introduces the
possibility of putting you off the air.
That's because the people working on the various packages that go into
CentOS don't know about Rivendell and don't test the effect of their
updates on Rivendell. Most of the time,
Thanks, Lorne and Steve. I’ll keep your advice in mind the next time we
re-organize our studio network. This re-org may actually happen sometime in
the next couple of years as we are planning a move to new quarters. So it’s
actually a good thing you pointed that out now.
Enjoy!
Rick
On May
Rick,
I'm a little surprised here - I don't know why you would put a playback
machine on a network connection that has direct access to the internet.
For best security practices it should be on a private network without
internet access.
Even though Linux is much more secure then other OSes, what
: [RDD] Please fix this bug...
That’s essentially option 2 by another name. It has the same problems. If
doing it breaks something in Rivendell, we’re off the air.
Perhaps one of the support folks can tell us which of the 4 update packages
from the Paravel repo it’s safe to uncheck?
Thanks
That’s essentially option 2 by another name. It has the same problems. If
doing it breaks something in Rivendell, we’re off the air.
Perhaps one of the support folks can tell us which of the 4 update packages
from the Paravel repo it’s safe to uncheck?
Thanks!
Rick
> On May 16, 2017, at 3:11
IIRC you can choose not to apply certain updates by unchecking them in the
Software Update dialog window.
Sent from my iPhone
> On May 16, 2017, at 6:07 PM, Rick Thomas wrote:
>
> We are using the CentOS-6 that is part of the Rivendell Broadcast Appliance
> system from Paravel Systems. We ha
We are using the CentOS-6 that is part of the Rivendell Broadcast Appliance
system from Paravel Systems. We have a paid-up support contract. It’s really
great, and we love it a lot! Thanks for all the wonderful features!
Now the problem:
The Rivendell 2.15.3-1 update appears along with more
On Tuesday 16 May 2017 03:10:46 pm Rick Thomas wrote:
> We’ve been holding off installing the Rivendell 2.15.3-1 update, hoping to
> see a fix for this bug.
>
> But with all the activity over the NSA zero-day exploits released a few
> months ago, it’s becoming imperative that we get the security
Rick,
We do not have any influence over development of the CentOS Linux
distribution, only the Rivendell code. What version of CentOS are you
using? CentOS 5 has reached end of life and is no longer updated. You may
want to consider updating to CentOS 7 if your version of the distro is no
longer
Dear Rivendell developers,
We’ve been holding off installing the Rivendell 2.15.3-1 update, hoping to see
a fix for this bug.
But with all the activity over the NSA zero-day exploits released a few months
ago, it’s becoming imperative that we get the security updates from CentOS that
this is b
20 matches
Mail list logo