Products > Test Equipment
Agilent E7495 linux root account
<< < (43/91) > >>
ke6iyc:
Thank you on the cable question.

As for the patching in place, has anyone ACTUALLY tried it?

I am out of state right now, and have a unit waiting for me at my hotel.  I would like to patch it (Would like to try out the Interference analyzer) before I return home, but not at the risk of bricking the unit.

Thanks a bunch to all!

Brian
technogeeky:

--- Quote from: ke6iyc on May 12, 2017, 04:36:04 pm ---Thank you on the cable question.

As for the patching in place, has anyone ACTUALLY tried it?

I am out of state right now, and have a unit waiting for me at my hotel.  I would like to patch it (Would like to try out the Interference analyzer) before I return home, but not at the risk of bricking the unit.

Thanks a bunch to all!

Brian

--- End quote ---

Once you connect to the unit via telnet, the the first thing you'll want to do is make a copy of all of the files in /flash. The easiest way to do this, in my opinion, is to setup a FTP server on your computer and run an ftp client on the E7495a. The easiest way to modify the elgato binary is simply to do it on your host computer (using a tool that does hex editing -- there are plenty of these for windows, osx, linux). Then, you can use the FTP client to get the file back.

The other obvious way to make a backup is to simply dump things onto the CF card, insert into host computer, copy, and put it back in.

Destroying the elgato binary won't brick the unit, as far as I know. You'll still have telnet access. Plus, you can just 'cp elgato elgato.original'. There is enough space to have a few copies of the binary around.


PA0PBZ:

--- Quote from: technogeeky on May 12, 2017, 06:27:09 pm ---you can just 'cp elgato elgato.original'. There is enough space to have a few copies of the binary around.

--- End quote ---

Yup, and a 'killall elgato' to make sure you are not trying to patch a running executable.
technogeeky:

--- Quote from: PA0PBZ on May 12, 2017, 06:33:33 pm ---
--- Quote from: technogeeky on May 12, 2017, 06:27:09 pm ---you can just 'cp elgato elgato.original'. There is enough space to have a few copies of the binary around.

--- End quote ---

Yup, and a 'killall elgato' to make sure you are not trying to patch a running executable.

--- End quote ---

For future reference, in Linux there is no risk of modifying a running executable. The entire process tree of the executable (e.g. elgato and anything it runs or calls) will only be able to reference the original file. I am about 99% sure this is the case, at least.
PA0PBZ:

--- Quote from: technogeeky on May 12, 2017, 06:36:48 pm ---For future reference, in Linux there is no risk of modifying a running executable. The entire process tree of the executable (e.g. elgato and anything it runs or calls) will only be able to reference the original file. I am about 99% sure this is the case, at least.

--- End quote ---

I was thinking about copying back the patched file, that doesn't work when it's running, not sure about patching.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod