ShareFS not reflecting changes

If I read things, Rob has updared Sharefs. Many thanks. I’m just rebuilding all roms I build to include this and will report back what I find.. Again, many thanks

Hi John,

You should also be aware of an issue with the latest ROM’s and it appears when using JetDirectFS/UniServe for network printing that may need some checking with RComp.

Though the article says Iyonix it is any 19/3/23 ROM as far as I can tell that has the issue.

Rool article link

OK..Based on tests on iMx6, on RockPro64, and between the 2
ROOL stack works as expected… no surprise there
ROD stack – built within the last week, so beyond what is probably in the field – works between machines as expected but not within the same machine. We’ll look into that.

FWIW. all ROMs built yesterday. Stack built on the 16th.

Rob. Thanks for the fix.

I how have ShareFS 3.62 in a recent nightly built ROM on the Pi 400, but still have 3.61 on the ARMX6. I can extract the new ShareFS module using Verma, but where should I put it on the ARMX6 so that it overrides the 3.61 during boot?

I can extract the new ShareFS module using Verma

The ROM builds are machine specific, translating a ROM module into a different machine could be unpredictable. Fortunately there is a ShareFS in PlingSystem, which is built to a common standard.

PlingSys.!System.310.Modules.Network.ShareFS

Install that on the iMX then place an Obey file to call it in PreDesk, but name the file such that it is run after SetupNet.

RMEnsure ShareFS 3.62 RMLoad System:Modules.Network.ShareFS

And the difficult bit, remember to remove it afterwards. It won’t cause any issues later but it will be extraneous junk.

Excellent, detailed answer. Thank you.

Excellent, detailed answer.

But unfortunately I haven’t got the advice to work. I named the Obey file

~SetupShareFS

Invalid Error Block address: &20002B44

ADT at &20400DB8

But unfortunately I haven’t got the advice to work.

Oh dear etc.. It was tested here yesterday on the Titanium with the ROOL Inet stack and again just now with the ROD Inet stack. All good, as expected.

The ShareFS in PlingSystem is a 32bit build. What happens if it is directly double clicked on? I do not have an iMx.

But unfortunately I haven’t got the advice to work. I named the Obey file

Why not just put the ShareFS module out of the downloaded System Resources zip directly in to !Boot.Choices.Boot.PreDesk..works for me on my iMX6 as after a reboot I have ShareFS 3.62 not 3.61 running.

Why not just put the ShareFS module out of the downloaded System Resources zip directly in to !Boot.Choices.Boot.PreDesk

Indeed, that is the quickest and easiest way to test something.

The downside to that is that there is no version check. One really does have to remember to remove it when no longer required as ShareFS 3.63 and later be over written.

A better, safer, general purpose method is to create a folder, put the module in it with a !Run obey file containing :-

RMEnsure ShareFS 3.62 RMLoad <Obey$Dir>.ShareFS

It is all in one place and got rid of with a single delete.

There is no naming issue as PreDesk does directories after files.

I should have suggested this in the first place.

A better, safer, general purpose method is to create a folder, put the module in it with a !Run obey file …..

Thanks, done that for ARMX6. Is it ok to do the same thing on a pi4?

Is it ok to do the same thing on a pi4?

Yes.

Having now carefully read, re-read and fully taken the above advice (!), ShareFS 3.62 is now live on this iMX6. Many thanks for your patience.