NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Skywalker
Dec 13, 2007NETGEAR Expert
Getting started How-To
Requirements:
1) RAIDiator-4.00c1-p2 or later.
2) The APT addon. Install it using the Frontview web UI under System -> Update -> Local Update.
3) The EnableRootSSH addon. Again, install using the Frontview web UI under System -> Update -> Local Update. This will allow you to SSH in to the NAS and bring up a shell command prompt.
Now what?
After those requirements are met, you should be able to run the standard Debian command "apt-get" to download and install packages for everything you need for development, including the headers for the non-standard packages used for the ReadyNAS.
Examples:
# apt-get update
# apt-get install libc6-dev
# apt-get install gcc
# apt-get install gdb
# apt-get install libtag1-dev
# apt-get install uuid-dev
Compiling natively on the ReadyNAS is slow. How about a cross-compiler?
You can grab a tarball of a cross-compiler to compile using an x86 system from here. It includes gcc, g++, and development headers, for use on Linux-based systems. Extract the tarball from your root directory to ensure things are placed in the correct path.
WARNING!
Please note that you can get your ReadyNAS into peril easily by overriding some of the system libraries and utilities. Do not do your development on a system you don't have a backup of as you may end up re-installing the firmware or worse yet, doing a factory default.
1) RAIDiator-4.00c1-p2 or later.
2) The APT addon. Install it using the Frontview web UI under System -> Update -> Local Update.
3) The EnableRootSSH addon. Again, install using the Frontview web UI under System -> Update -> Local Update. This will allow you to SSH in to the NAS and bring up a shell command prompt.
Now what?
After those requirements are met, you should be able to run the standard Debian command "apt-get" to download and install packages for everything you need for development, including the headers for the non-standard packages used for the ReadyNAS.
Examples:
# apt-get update
# apt-get install libc6-dev
# apt-get install gcc
# apt-get install gdb
# apt-get install libtag1-dev
# apt-get install uuid-dev
Compiling natively on the ReadyNAS is slow. How about a cross-compiler?
You can grab a tarball of a cross-compiler to compile using an x86 system from here. It includes gcc, g++, and development headers, for use on Linux-based systems. Extract the tarball from your root directory to ensure things are placed in the correct path.
WARNING!
Please note that you can get your ReadyNAS into peril easily by overriding some of the system libraries and utilities. Do not do your development on a system you don't have a backup of as you may end up re-installing the firmware or worse yet, doing a factory default.
129 Replies
Replies have been turned off for this discussion
- melleinAspiranti've also tried apt-key update
gpg: key 6070D3A1: "Debian Archive Automatic Signing Key (4.0/etch) <ftpmaster@debian.org>" not changed
gpg: key ADB11277: "Etch Stable Release Key <debian-release@lists.debian.org>" not changed
gpg: key BBE55AB3: "Debian-Volatile Archive Automatic Signing Key (4.0/etch)" not changed
gpg: key F42584E6: "Lenny Stable Release Key <debian-release@lists.debian.org>" not changed
gpg: key 55BE302B: "Debian Archive Automatic Signing Key (5.0/lenny) <ftpmaster@debian.org>" not changed
gpg: key 6D849617: "Debian-Volatile Archive Automatic Signing Key (5.0/lenny)" not changed
gpg: Total number processed: 6
gpg: unchanged: 6 - ScouserAspirantBrand new Pro 6 with 4.2.19.
MainStore:~# apt-get update
Get:1 http://archive.debian.org etch Release.gpg [1033B]
Get:2 http://archive.debian.org etch Release [67.8kB]
Get:3 http://archive.debian.org etch/main Packages [5477kB]
Get:4 http://www.readynas.com 4.2.19/ Release.gpg [490B]
Get:5 http://www.readynas.com 4.2.19/ Release [738B]
Ign http://www.readynas.com 4.2.19/ Release
Get:6 http://www.readynas.com 4.2.19/ Packages [18.3kB]
Fetched 5566kB in 3s (1535kB/s)
Reading package lists... Done
W: GPG error: http://www.readynas.com 4.2.19/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B7F02108D553259A
W: You may want to run apt-get update to correct these problems
MainStore:~# apt-key update
gpg: key 6070D3A1: "Debian Archive Automatic Signing Key (4.0/etch) <ftpmaster@debian.org>" not changed
gpg: key ADB11277: "Etch Stable Release Key <debian-release@lists.debian.org>" not changed
gpg: key BBE55AB3: "Debian-Volatile Archive Automatic Signing Key (4.0/etch)" not changed
gpg: key F42584E6: "Lenny Stable Release Key <debian-release@lists.debian.org>" not changed
gpg: key 55BE302B: "Debian Archive Automatic Signing Key (5.0/lenny) <ftpmaster@debian.org>" not changed
gpg: key 6D849617: "Debian-Volatile Archive Automatic Signing Key (5.0/lenny)" not changed
gpg: Total number processed: 6
gpg: unchanged: 6
MainStore:~# apt-get update
Get:1 http://archive.debian.org etch Release.gpg [1033B]
Hit http://archive.debian.org etch Release
Ign http://archive.debian.org etch/main Packages/DiffIndex
Hit http://archive.debian.org etch/main Packages
Get:2 http://www.readynas.com 4.2.19/ Release.gpg [490B]
Hit http://www.readynas.com 4.2.19/ Release
Err http://www.readynas.com 4.2.19/ Release
Get:3 http://www.readynas.com 4.2.19/ Release [738B]
Ign http://www.readynas.com 4.2.19/ Release
Ign http://www.readynas.com 4.2.19/ Packages/DiffIndex
Hit http://www.readynas.com 4.2.19/ Packages
Fetched 1229B in 1s (758B/s)
Reading package lists... Done
W: GPG error: http://www.readynas.com 4.2.19/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B7F02108D553259A
W: You may want to run apt-get update to correct these problems
MainStore:~#
Anybody got a clue where to go next? - ScouserAspirantI found this explanation and possible solution via a Google search.
Can somebody please tell me if it is safe to try this?
Also, what keyserver should I use?
TIA
When updating the Debian based system, it may happens that the apt-get displays an error message like:
W: GPG error: ftp://ftp.debian.org/ testing Release:
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 010908312D230C5F
W: There is no public key available for the following key IDs:
010908312D230C5F
This is a new feature of the apt-get system that guarantee the authenticity of servers for updating Debian.
Solution
Simply type the following commands, taking care to replace the number of the key that displayed in the error message:
gpg --keyserver pgpkeys.mit.edu --recv-key 010908312D230C5F
gpg -a --export 010908312D230C5F | sudo apt-key add - - WhoCares_MentorIt is safe but it won't help you since as you can see from the fingerprint (the number after NO_PUBKEY) it's a different key you're going to import using the commands you mentioned. So for the moment there is no other method as to wait until 4.2.20 comes out which as chirpa stated above should have a proper signature.
-Stefan - ScouserAspirantOh! I presumed I would use the key B7F02108D553259A in the command. Will that not work?
- ScouserAspirantAch! dumn me. Yes I understand now. Oh well waiting with baited breath ;)
- smaungAspiranti get this,
xxxxxx:~/.gnupg# gpg --keyserver pgpkeys.mit.edu --recv-key B7F02108D553259A
gpg: requesting key D553259A from hkp server pgpkeys.mit.edu
gpgkeys: key B7F02108D553259A not found on keyserver
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0 - WhoCares_MentorWhich, as I tried to point out in my previous posts, is the expected behavior since the key simple isn't publicly available. So there's no way to get rid of that and related error messages right now.
-Stefan - goran1973Aspirant:idea:
Hello all.
I am new in this forum and any help from you I will appreciate.
I need information, documents, tool list for NAS technology.
Also I will appreciate list of the most frequent software issues which you was face with.
Thank you in advance.
Best regards. WhoCares? wrote: So for the moment there is no other method as to wait until 4.2.20 comes out which as chirpa stated above should have a proper signature.
-Stefan
Is this sorted now, per chance? I'm not seeing (or understanding) any mention in the release notes.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!