NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
How I got apt update and install to work (with Debian Jessie retired)
OK, so I started off creating my own local Debian repository. Not recommended -- it's a lot of work. But with a lot of Googling and experimenting, I finally got apt to work using an online source. ...
So, John____ , just to clarify [because I'm in the same boat you were in], you're back in 6.10.9 and able to do app updates via the web interface? Or are you doing it over SSH?
I've managed to revert back to 6.10.9 after foolishly upgrading without checking what was being changed (honestly, never in my wildest dreams did I think they were going to purposefully wreck their users this hard), but everything is still broken on my end insofar as updating apps via the web interface is concerned.
Langzik_NAS wrote:
I've managed to revert back to 6.10.9 ... but everything is still broken on my end insofar as updating apps via the web interface is concerned.
Did you re-apply the mods in this thread? They are needed to get most installs to work.
Hey StephenB
I only braved the 6.10.9 install last night 😨; after all the unsolicited excitement from the 6.10.10 update ☠️, I was too afraid of things getting worse; it was enough for one evening (😅).After my cooldown period, I took the plunge today & went through the mods posted by sensei Sandshark (which you referred people to as a solution in the forums):
https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/How-I-got-apt-update-and-install-to-work-with-Debian-Jessie/m-p/2325295/highlight/true#M200147& I took some pointers (ex. renaming the original file) from Astra03 's post:
https://community.netgear.com/t5/New-ReadyNAS-Users-General/ReadyNAS-OS-6-10-10-released/m-p/2365563/highlight/true#M53652It worked on one NAS device ("NAS 01") ✊, but I already had PLEX updated on my other NAS ("NAS 02"), so I couldn't test it there 😞. Installing Nano was a great idea, but I needed to use the -f flag to force the install:
apt-get install nano -fHaving said that, given that I was able to install Nano [on "NAS 02"] after applying the mods, I'm confident I'll be able to update PLEX on that device as well.
Thanks again StephenB , Sandshark , Astra03 & anyone/everyone else that banded together to find a solution to this [frankly, ridiculous & unnecessary] problem; this should've been rectified by Netgear, but since they obviously couldn't be bothered to set things right, thanks for stepping up & being the heroes our community needed today ✊.
I'm glad it worked for you. I have no idea why you need the -f option to install nano, but thanks for sharing in case somebody else has an issue with it.
But while I don't like making excuses for Netgear, they are actually doing the right thing not making this a part of an OS update. Setting it to allow unauthenticated sources is a (small, and IMHO acceptable for home use) potential security hole. Users need to choose for themselves whether or not it's acceptable to them.
Of course, with 6.10.10, they decided to go the other direction and prevent users from deciding to allow it, which is unacceptable.
Of course, they should have upgraded ReadyNAS OS to a newer Linux base a long time ago, but now I wonder if they haven't been planning this exit from the NAS business for a while, and that's the reason they didn't do it.
I have no idea why you need the -f option to install nano
One NAS device in particular is a problem-child for me (I can't even get SMB to work on it anymore; not sure how or why, but it's a major pain-point). This was probably the first device I applied to patch to, so it likely gave me issues, after which point I'll have simply opted to apply the -f flag by default when installing it on the other NAS device.
[as for the rest...]
I agree with everything you said; I understand the motive, but disagree with the outcome/execution they opted for. It would've been better for them to inform the user via disclaimer and create a switch of sorts to turn off app functionality based on the user's preference & risk appetite. Moreover, it's crazy that they didn't even give a warning window prior to the user applying the update. Most of us assume updates are here to fix bugs & issues, but rarely do we consider a situation where a core function is simply torn out of OS... Anyway, I could go on forever, but I know I'm preaching to the choir here lol. My point is simply that the update's outcome was wildly unacceptable in my view; it should never have happened, and they should've restored what they broke immediately after, when users became confused, alarmed, and steeped in regret. Now they'll have a chunk of users who are either:
- cursing their product [not knowing the situation, but knowing the outcome],
- frustrated [because they realize what's happened, but don't have the technical confidence/competence to fix it], or
- feeling distrust towards Netgear/ReadyNAS [knowing what happened, having reverse-engineered the outcome, and having turned off all update-related activity].
All of these outcomes are damaging for not only the users & ReadyNAS, but also Netgear [in regard to reputation & reliability]. For example, every time I think about Netgear now, I'll be thinking about this issue; how can I recommend Netgear's products as a solution to anything/anyone in the future? They'd REALLY have to do something special to woo me... and even then, I'd [unfortunately] have a very hard time trusting them now.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
