Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.acorn.networking > #5188 > unrolled thread

Connecting LanMan98 to Raspberry Pi 5

Back to article view | Back to comp.sys.acorn.networking

Contents

  Connecting LanMan98 to Raspberry Pi 5 Brian Howlett <news-spamtrap@brianhowlett.me.uk> - 2025-05-27 22:08 +0100
    Re: Connecting LanMan98 to Raspberry Pi 5 John <newsmcc@blueyonder.co.uk> - 2025-05-28 10:34 +0100
      Re: Connecting LanMan98 to Raspberry Pi 5 Bob Latham <bob@sick-of-spam.invalid> - 2025-05-28 11:23 +0100
        Re: Connecting LanMan98 to Raspberry Pi 5 Bob Latham <bob@sick-of-spam.invalid> - 2025-05-28 11:46 +0100
        Re: Connecting LanMan98 to Raspberry Pi 5 John <newsmcc@blueyonder.co.uk> - 2025-05-28 15:12 +0100
          Re: Connecting LanMan98 to Raspberry Pi 5 Brian Howlett <news-spamtrap@brianhowlett.me.uk> - 2025-05-28 18:19 +0100
    Re: Connecting LanMan98 to Raspberry Pi 5 druck <news@druck.org.uk> - 2025-05-28 21:19 +0100
      Re: Connecting LanMan98 to Raspberry Pi 5 Bob Latham <bob@sick-of-spam.invalid> - 2025-05-29 09:49 +0100
        Re: Connecting LanMan98 to Raspberry Pi 5 Theo <theom+news@chiark.greenend.org.uk> - 2025-05-29 10:39 +0100
          Re: Connecting LanMan98 to Raspberry Pi 5 Chris Hughes <news13@noonehere.co.uk> - 2025-05-29 10:53 +0100
            Re: Connecting LanMan98 to Raspberry Pi 5 Bob Latham <bob@sick-of-spam.invalid> - 2025-05-29 11:36 +0100
              Re: Connecting LanMan98 to Raspberry Pi 5 Theo <theom+news@chiark.greenend.org.uk> - 2025-05-29 13:13 +0100
                Re: Connecting LanMan98 to Raspberry Pi 5 Bob Latham <bob@sick-of-spam.invalid> - 2025-05-29 14:53 +0100
                  Re: Connecting LanMan98 to Raspberry Pi 5 Theo <theom+news@chiark.greenend.org.uk> - 2025-05-29 16:29 +0100
                    Re: Connecting LanMan98 to Raspberry Pi 5 Bob Latham <bob@sick-of-spam.invalid> - 2025-05-30 11:34 +0100
                      Re: Connecting LanMan98 to Raspberry Pi 5 Theo <theom+news@chiark.greenend.org.uk> - 2025-05-30 12:38 +0100
                        Re: Connecting LanMan98 to Raspberry Pi 5 Bob Latham <bob@sick-of-spam.invalid> - 2025-05-31 11:10 +0100
                          Re: Connecting LanMan98 to Raspberry Pi 5 Theo <theom+news@chiark.greenend.org.uk> - 2025-05-31 21:11 +0100
                            Re: Connecting LanMan98 to Raspberry Pi 5 Bob Latham <bob@sick-of-spam.invalid> - 2025-06-01 13:00 +0100
      Connecting LanMan98 to Raspberry Pi 5 Dnews <dnews@triffid.co.uk> - 2025-05-29 18:32 +0100

#5188 — Connecting LanMan98 to Raspberry Pi 5

Hi.

I recently acquired a Raspberry Pi 5, and am looking to connect to it from 
RISC OS using LanMan 98, so far with no success.

Has anyone got a similar setup working, and if so, what are the correct 
settings (on both systems)?

I haven't used Linux in about a decade, so my memory is in severe need of 
a refresh...

I have LanMan 98 connected to my Windows PC and my Synology NAS without 
issue, so I know it is working OK.
-- 
Brian Howlett
-----------------------------------------
I installed a skylight in my apartment.
The people who live above me are furious!

[toc] | [next] | [standalone]

#5189

In article <7fb3c1235c.BrianNews@brianhowlett.me.uk>, Brian
Howlett <news-spamtrap@brianhowlett.me.uk> wrote:

> Has anyone got a similar setup working, and if so, what
> are the correct settings (on both systems)?

Not quite.

I wrote a couple of articles for the WROCC Newsletter some
time ago. One was for connecting to a Windows PC and the
other for connecting to a Linux PC.

I had a lot of help from Bob Latham who supplied
information on connecting to a Pi. If you want me to, I can
send you copies of the articles.

If you let me have a valid email address, I'll let you have
them, either as Impression documents or as PDF files.

If you use my address for this list, it should reach me.

John

-- 
John
newsmcc@blueyonder.co.uk
j dot mccartney atte blueyonder dot co dot uk

[toc] | [prev] | [next] | [standalone]

#5190

In article <5c2406133fnewsmcc@blueyonder.co.uk>,
   John <newsmcc@blueyonder.co.uk> wrote:
> In article <7fb3c1235c.BrianNews@brianhowlett.me.uk>, Brian
> Howlett <news-spamtrap@brianhowlett.me.uk> wrote:

> > Has anyone got a similar setup working, and if so, what
> > are the correct settings (on both systems)?


> I had a lot of help from Bob Latham who supplied
> information on connecting to a Pi. 

Thanks for the mention John.


I have not tested every distro of linux but I have tested the
13/05/2025 release of Raspberry Pi OS lite, found here..
https://www.raspberrypi.com/software/operating-systems/

To get that to play nicely the key is this...

Add the following 5 lines to the file /etc/samba/smb.conf

--------------------------------------
# Allow SMB1 connections for RISC OS.
   server min protocol=NT1
#   client min protocol=NT1
   ntlm auth=yes
unix extensions = no
---------------------------------------

In that file you'll find a line workgroup = WORKGROUP
and just under that a heading of Networking.

I chose to add the lines as the first item in "Networking"

I found it easiest to do this with nano as in: 
  sudo nano /etc/samba/smb.conf

Add the lines and that's basically it!


I also wanted to share the root on my Pis and to do that...

Add the following, I chose just above [printers]

 
[root]
   comment = root
   path = /
   writeable = yes
   only guest = no
   directory mask = 0777
   create mask = 0777
   force user = root
   force group = root
   public = no
   follow symlinks = yes
   wide links = yes


That will give you access to root.

Then you may find that other shares from the pi set by default can
annoy. To get rid ...

add the line 

   available = no

to the list under [homes] [print$]


To finish off, save with Cntrl-X, Y, <ret>

sudo systemctl restart smbd 

You should now be good to go.


Bob.

[toc] | [prev] | [next] | [standalone]

#5191

In article <5c240a807ebob@sick-of-spam.invalid>,
   Bob Latham <bob@sick-of-spam.invalid> wrote:

Sorry, forgot a few things...

To install samba in the first place ..
   sudo apt-get install samba samba-common-bin

Then after saving all the changes mentioned before in smb.conf you
have to set an smb password that you use from LM98. 

So for username pi and password bob....


sudo smbpasswd -a pi
enter password for pi user as 'bob' TWICE !!.

sudo systemctl restart smbd

Can't think of anything else on the linux end.

On RiscOS, the LM98 file...

Server: 192.168.1.15
Share: root
User: pi
Password: bob

You can use a name instead of the IP address.
eg.
Server: mypi5


That's it, I think.

Bob.




> I have not tested every distro of linux but I have tested the
> 13/05/2025 release of Raspberry Pi OS lite, found here..
> https://www.raspberrypi.com/software/operating-systems/

> To get that to play nicely the key is this...

> Add the following 5 lines to the file /etc/samba/smb.conf

> --------------------------------------
> # Allow SMB1 connections for RISC OS.
>    server min protocol=NT1
> #   client min protocol=NT1
>    ntlm auth=yes
> unix extensions = no
> ---------------------------------------

> In that file you'll find a line workgroup = WORKGROUP
> and just under that a heading of Networking.

> I chose to add the lines as the first item in "Networking"

> I found it easiest to do this with nano as in: 
>   sudo nano /etc/samba/smb.conf

> Add the lines and that's basically it!


> I also wanted to share the root on my Pis and to do that...

> Add the following, I chose just above [printers]

>  
> [root]
>    comment = root
>    path = /
>    writeable = yes
>    only guest = no
>    directory mask = 0777
>    create mask = 0777
>    force user = root
>    force group = root
>    public = no
>    follow symlinks = yes
>    wide links = yes


> That will give you access to root.

> Then you may find that other shares from the pi set by default can
> annoy. To get rid ...

> add the line 

>    available = no

> to the list under [homes] [print$]


> To finish off, save with Cntrl-X, Y, <ret>

> sudo systemctl restart smbd 

> You should now be good to go.


> Bob.

[toc] | [prev] | [next] | [standalone]

#5192

In article <5c240a807ebob@sick-of-spam.invalid>, Bob Latham
<bob@sick-of-spam.invalid> wrote:

> Thanks for the mention John.

My pleasure, Bob.

At least, Brian now has it from the horse's mouth.

John

-- 
John
newsmcc@blueyonder.co.uk
j dot mccartney atte blueyonder dot co dot uk

[toc] | [prev] | [next] | [standalone]

#5193

On 28 May, John <newsmcc@blueyonder.co.uk> wrote:

> In article <5c240a807ebob@sick-of-spam.invalid>, Bob Latham
> <bob@sick-of-spam.invalid> wrote:

>> Thanks for the mention John.

> My pleasure, Bob.

> At least, Brian now has it from the horse's mouth.

> John

Thanks, guys. I'll give it a go and report back if I have any issues.
-- 
Brian Howlett - Email to From: address deleted unseen
-----------------------------------------------------
Karl Marx's grave. Just another Communist Plot?

[toc] | [prev] | [next] | [standalone]

#5194

On 27/05/2025 22:08, Brian Howlett wrote:
> I recently acquired a Raspberry Pi 5, and am looking to connect to it from
> RISC OS using LanMan 98, so far with no success.

Instead of compromising my Raspberry Pi 5 NAS by enabling the old 
horribly insecure SMB1 just for LanmanFS/98, I'm using the same NFS 
shares from my RISC OS Pi 4 that the other Linux Pi's use.

Once !SunFish is configured using the crashy front end, the back end 
filing system is rock solid and I've not had a single problem with it in 
a decade.

---druck

[toc] | [prev] | [next] | [standalone]

#5195

In article <1017r4e$3dqre$1@dont-email.me>,
   druck <news@druck.org.uk> wrote:
> On 27/05/2025 22:08, Brian Howlett wrote:
> > I recently acquired a Raspberry Pi 5, and am looking to connect to it from
> > RISC OS using LanMan 98, so far with no success.

> Instead of compromising my Raspberry Pi 5 NAS by enabling the old 
> horribly insecure SMB1 just for LanmanFS/98, 

Sure it is insecure but for me it's worth the small risk when used
for music player pi machines.

> I'm using the same NFS 
> shares from my RISC OS Pi 4 that the other Linux Pi's use.

> Once !SunFish is configured using the crashy front end, the back
> end filing system is rock solid and I've not had a single problem
> with it in a decade.

The front end of Sunfish is terrible and I think the security on NFS
is difficult to comprehend but as Dave says once setup sunfish is
very good indeed.

I use NFS sunfish to maintain my music library on a synology NAS.
LanMan98 has awful problems with utf-8 characters often used for
continental classical music. Some characters if present in a file
name can stop LM98 listing the file at all, it can't see it.

    Char             PC value  PC keyboard     UTF-8 & Sunfish value.
Apostrophe              146     [Alt]0146        &E2, &80, &99
inverted commas 66      147     [Alt]0147        &E2, &80, &9C
inverted commas 99      148     [Alt]0148        &E2, &80, &9D
hyphen                  150     [Alt]0149        &E2, &80, &93

All of the above prevent Lanman98 from showing a file with these
chars in the name. For LM98 the file does not exist.

If you setup sunfish to use "no translation" (I think that's what it
was called) then you can get the actual bytes used for the utf-8 code
in the linux device. It is testament to how awful the sunfish front
end is, I've just tried to check the "no translation" setting name
and could not find way in to do so.

Summary, LM98 is much nicer to use but easily broken by utf-8 chars
but I don't think it was designed for that, it was designed to store
RISCOS files in the PC world and then pull them back and it does that
very well

Sunfish, horrible to setup, you need to pour a good drink first, but
once setup gives much better results.


Bob.

[toc] | [prev] | [next] | [standalone]

#5196

Bob Latham <bob@sick-of-spam.invalid> wrote:
> Sunfish, horrible to setup, you need to pour a good drink first, but
> once setup gives much better results.

If I remember correctly, the Sunfish file (ie the thing in a Filer
window you double click on to open an NFS share) is just a text file with
the config options.  Try dragging it to a text editor and seeing what's
inside.  If the frontend is problematic, it may be easier just to edit the
config file directly.

Theo

[toc] | [prev] | [next] | [standalone]

#5197

In message <lKm*sRGdA@news.chiark.greenend.org.uk>
          Theo <theom+news@chiark.greenend.org.uk> wrote:

> Bob Latham <bob@sick-of-spam.invalid> wrote:
>> Sunfish, horrible to setup, you need to pour a good drink first, but
>> once setup gives much better results.

> If I remember correctly, the Sunfish file (ie the thing in a Filer
> window you double click on to open an NFS share) is just a text file with
> the config options.  Try dragging it to a text editor and seeing what's
> inside.  If the frontend is problematic, it may be easier just to edit the
> config file directly.

It is a Text file with different icon, and I have edited that file as 
needed to get it to work.

Ideally though the frontend really needs to be fixed properly as for 
non-techy users it gives a bad impression of the software.



-- 
Chris Hughes

[toc] | [prev] | [next] | [standalone]

#5198

In article <5f9e8b245c.chris@mytardis>,
   Chris Hughes <news13@noonehere.co.uk> wrote:
> In message <lKm*sRGdA@news.chiark.greenend.org.uk>
>           Theo <theom+news@chiark.greenend.org.uk> wrote:

> > Bob Latham <bob@sick-of-spam.invalid> wrote:
> >> Sunfish, horrible to setup, you need to pour a good drink first,
> >> but once setup gives much better results.

> > If I remember correctly, the Sunfish file (ie the thing in a
> > Filer window you double click on to open an NFS share) is just a
> > text file with the config options.  Try dragging it to a text
> > editor and seeing what's inside.  If the frontend is problematic,
> > it may be easier just to edit the config file directly.

> It is a Text file with different icon, and I have edited that file
> as needed to get it to work.

To be honest, that sounds exactly like LM98 to me. Nothing in normal
Sunfish use appears to be a drag-able file to me. However, I have
found a file that describes my NAS connection at:

SDFS::Minim.$.!Boot.Choices.Sunfish.mountsave.red/volume1/music

It contains this...

Protocol: NFS3
Server: RED
Export: /volume1/music
uid: 0
gid: 0
gids:
umask: 022
Transport: TCP
ShowHidden: 1
FollowSymlinks: 5
CaseSensitive: 1
UnixEx: 0
TranslateWin: 1
DefaultFiletype: FFF
AddExt: 1
unumask: 600
MaxDataBuffer: 0
Pipelining: 0
Timeout: 20
Logging: 0

It may use other wording but nothing about "no conversion".

I wish I understood uid, gid and gids but I don't, the more I read
about them the more confused I become. I realise I'm probably wrong
but this security system seems to be a confused, complex, dog's
breakfast to me compared to a username and password expected
everywhere else.

> Ideally though the frontend really needs to be fixed properly as
> for non-techy users it gives a bad impression of the software.

Ah-men to that.

Bob.

[toc] | [prev] | [next] | [standalone]

#5199

Bob Latham <bob@sick-of-spam.invalid> wrote:
> To be honest, that sounds exactly like LM98 to me. Nothing in normal
> Sunfish use appears to be a drag-able file to me. However, I have
> found a file that describes my NAS connection at:
> 
> SDFS::Minim.$.!Boot.Choices.Sunfish.mountsave.red/volume1/music

That's the one.

> It contains this...
> 
> Protocol: NFS3
> Server: RED
> Export: /volume1/music
> uid: 0
> gid: 0
> gids:
> umask: 022
> Transport: TCP
> ShowHidden: 1
> FollowSymlinks: 5
> CaseSensitive: 1
> UnixEx: 0
> TranslateWin: 1
> DefaultFiletype: FFF
> AddExt: 1
> unumask: 600
> MaxDataBuffer: 0
> Pipelining: 0
> Timeout: 20
> Logging: 0
> 
> It may use other wording but nothing about "no conversion".

Is it perhaps the 'TranslateWin: 1'?

> I wish I understood uid, gid and gids but I don't, the more I read
> about them the more confused I become. I realise I'm probably wrong
> but this security system seems to be a confused, complex, dog's
> breakfast to me compared to a username and password expected
> everywhere else.

Let me try...

The thing to understand about NFS is that it's designed for a business
network where every machine is run by the same people.  Security is governed
by who is able to connect to the network, not by passwords.  Think back to
the 1980s when all we had was wired ethernet and laptops weren't a thing and
you get the idea.  This mode of NFS is now called sec=sys.

So what you had was a big server in the basement and a number of clients
(Unix workstations typically) networked to it.  One administrator controlled
them all - that meant that administrator 'root' on the server was 'root' on
the workstations, and individual user accounts on the server were mirrored
by user accounts on the clients.

Unix has the idea of 'user id' and 'group id' which are numbers - there's
files (/etc/passwd and /etc/group) which translate them to names for
niceness, but fundamentally they're numbers.  eg I might be user 1002 and
that user is in groups 34, 67, 88 and 915 - these numbers are the user id
'uid' and group ids 'gid' respectively.  Every file is owned by a user and a
group, ie I can access files owned by user 1002 or is owned by one of the
groups that I'm in (and gives me user read/write or group read/write
permissions).

When you connect to a original NFS server your machine said 'hey, I'm user
1002 and today I'm group 34' (my uid=1002 and gid=34) and the server would
say, ok here's the filesystem, you can only read and write the files that
user 1002 and group 34 have access to.  Note no authentication whatsoever,
but that's ok because I'm logged into my workstation as user 1002 and the
administrator doesn't give me rights to change that.  So I login to my
workstation with a local password, I can see the files on the server but I
only have access to files that user 1002 and its groups have access to.  All
is fine.

In case you don't want everyone to access your server you can limit them
based on IP addresses - eg only the IP address range 192.168.44.0/24 is
allowed to access the server, or IP 192.168.44.7 is only allowed to access
this part of the server as that user.  On Unix/Linux these settings are in
an 'exports' file which is typically found at /etc/exports.  Again this
works because access to the network is strictly controlled.


However 'PCs' aren't like this - there's no shared administrator that
controls every PC and makes sure that they only say 'hey, I'm user 1002' and
not 'hey, I'm user 1004' and get access to someone else's files.  So in the
late 80s a thing called PC-NFS came along which used usernames and passwords
instead of just asserting what uid/gid you are.  Unfortunately this didn't
catch on (but there are still some traces lying around to trip people up).


That was the state up until NFSv3.

When NFSv4 along came Kerberos (or 'sec=krb5'), which uses cryptographic
'tickets' as a way of proving your identity.  You authenticate with an
authentication server (password, key, fingerprint, whatever) and you get a
ticket.  You hand the ticket over to the NFS server which allows you access
to the files.

v4 has this solid user-based security but unfortunately Sunfish doesn't
implement it, it's stuck on v3.  So that means you have to fall back on the
original setup where you restrict access based on IP addresses only.

So what of the uid/gid settings in Sunfish?  This is what to send to the
server 'which user should I pretend to be'.  uid=0/gid=0 is the
administrator 'root' which means 'access any files' (although there is a
setting root_squash on the server which can block root access).  If you had
a user on the server, by setting these to the uid and gid of that user you
could access the files as if you're that user.

But fundamentally there is no security in NFSv3 because a rogue client could
just claim to be whatever uid/gid they want to be.  The only protection is
to lock things down at the network level - don't allow things you don't
trust access to the network.  That's how things have to be with NFSv3.

An NFSv4 version of Sunfish would be a fine thing, but it's a fair bit more
complex than v3 and seems nobody has tackled it.

Theo

[toc] | [prev] | [next] | [standalone]

#5200

In article <kKm*GpHdA@news.chiark.greenend.org.uk>,
   Theo <theom+news@chiark.greenend.org.uk> wrote:
> Bob Latham <bob@sick-of-spam.invalid> wrote:

> > It may use other wording but nothing about "no conversion".

> Is it perhaps the 'TranslateWin: 1'?

Actually I don't think it is. I think translateWin refers to the
option "Translate characters that are illegal on Windows" I presume a
value of 1 is on and 0 is off.

By working on getting NFS server running on a pi I found the wording
is in fact

Encoding: No Conversion.

That's what seems to me to reveal 2,3,4, byte utf-8 codes as they are
stored on my NAS. Very useful, wish LM98 could get near that.

> > I wish I understood uid, gid and gids.

> Let me try...

Wow thanks Theo. I have read that twice already, It's going in,
slowly but it's going in. Another 6 or 7 reads and maybe just maybe...

Thanks a lot Theo good of you.
 
Today I managed to get an NFS share working from a pi. It was a hack
I'm sure but it worked.

For anyone interested what I did was...

install NFS package.
   sudo apt-get install -y nfs-kernel-server

Some say it should be 3 packages ...
   sudo apt-get install -y nfs-kernel-server portmap nfs-common
but I found the second two were already installed.

Edit the file: /etc/exports
add lines like this...

/testbob 192.168.1.0/24(rw,sync)
/home 192.168.1.0/24(rw,sync)

Then restart the server.
sudo /etc/init.d/nfs-kernel-server restart

Permissions then show their ugly head. I found that 
      chmod 707 pi     (as in /home/pi)
fixed that problem for me.

Can I do that for the entire machine for full access?


The front end on sunfish is doing my head in! If you rename or
shorten the connection name you lose the ability to change any
settings, it locks down and I can't find a way back. Real pain.


Thanks again for the help.

Cheers,

Bob.

[toc] | [prev] | [next] | [standalone]

#5201

Bob Latham <bob@sick-of-spam.invalid> wrote:
> Wow thanks Theo. I have read that twice already, It's going in,
> slowly but it's going in. Another 6 or 7 reads and maybe just maybe...
> 
> Thanks a lot Theo good of you.
>  
> Today I managed to get an NFS share working from a pi. It was a hack
> I'm sure but it worked.
> 
> For anyone interested what I did was...
> 
> install NFS package.
>    sudo apt-get install -y nfs-kernel-server
> 
> Some say it should be 3 packages ...
>    sudo apt-get install -y nfs-kernel-server portmap nfs-common
> but I found the second two were already installed.
> 
> Edit the file: /etc/exports
> add lines like this...
> 
> /testbob 192.168.1.0/24(rw,sync)
> /home 192.168.1.0/24(rw,sync)
> 
> Then restart the server.
> sudo /etc/init.d/nfs-kernel-server restart
> 
> Permissions then show their ugly head. I found that 
>       chmod 707 pi     (as in /home/pi)
> fixed that problem for me.
> 
> Can I do that for the entire machine for full access?

My guess is that root_squash is default.  You're coming in as root
(uid=0/gid=0) and Linux is saying "no you can't be root, I'll make you the
lowest-privilege 'nobody' user instead".  That's why you have to give the
tree 707 permission, because the last 7 means 'give the world
read/write/execute' which means anyone including 'nobody' can access it..

So I think you have two options.  If you add 'no_root_squash' as in
"(rw,sync,no_root_squash)" then you can access any file as root.

Or you could set your uid/gid to match the ones on the Pi.  To find them
out, run the 'id' command:

$ id
uid=1000(bob) gid=1000(bob)
groups=1000(bob),4(adm),20(dialout),24(cdrom),27(sudo),29(audio),44(video),
46(plugdev),60(games),100(users),102(input),105(render),110(netdev),
993(gpio),994(i2c),995(spi)

If you tell Sunfish to use uid=1000, gid=1000 then you'll be able to access
files as user 'bob' can on the server.  But you can't access other files
that Bob can't normally access.

The first option makes it easy but is less secure.  The second limits the
damage that can be done to those files owned by Bob, so you couldn't eg
delete system files.

> The front end on sunfish is doing my head in! If you rename or
> shorten the connection name you lose the ability to change any
> settings, it locks down and I can't find a way back. Real pain.

I'm not sure if you can drag the config file to Sunfish's icon to open it
again to tweak the settings?

Theo

[toc] | [prev] | [next] | [standalone]

#5203

In article <lKm*B9HdA@news.chiark.greenend.org.uk>,
   Theo <theom+news@chiark.greenend.org.uk> wrote:
> Bob Latham <bob@sick-of-spam.invalid> wrote:

> So I think you have two options.  If you add 'no_root_squash' as in
> "(rw,sync,no_root_squash)" then you can access any file as root.

> Or you could set your uid/gid to match the ones on the Pi.  To find
> them out, run the 'id' command:

I've tried the easier method of adding 'no_root_squash' and it
appears to work but not quite. It displays all of the directories in
/ the same as Lanman98 and I know some of those are virtual
directories but they display in both systems.

What doesn't work is /boot/firmware where important files like
config.txt should be but the whole directory is empty from sunfish.

I have 'follow symbolic links' switched on, any suggestions?>

Thanks.

Bob.

[toc] | [prev] | [next] | [standalone]

#5204

Bob Latham <bob@sick-of-spam.invalid> wrote:
> In article <lKm*B9HdA@news.chiark.greenend.org.uk>,
>    Theo <theom+news@chiark.greenend.org.uk> wrote:
> > Bob Latham <bob@sick-of-spam.invalid> wrote:
> 
> > So I think you have two options.  If you add 'no_root_squash' as in
> > "(rw,sync,no_root_squash)" then you can access any file as root.
> 
> > Or you could set your uid/gid to match the ones on the Pi.  To find
> > them out, run the 'id' command:
> 
> I've tried the easier method of adding 'no_root_squash' and it
> appears to work but not quite. It displays all of the directories in
> / the same as Lanman98 and I know some of those are virtual
> directories but they display in both systems.
> 
> What doesn't work is /boot/firmware where important files like
> config.txt should be but the whole directory is empty from sunfish.
> 
> I have 'follow symbolic links' switched on, any suggestions?>

/boot is a separate mounted partition (the FAT one on the SD card) and NFS
doesn't follow mount points by default.  I think you need the 'crossmnt'
option in addition to 'no_root_squash' to allow NFS to see into the mounted
filesystem.

Theo

[toc] | [prev] | [next] | [standalone]

#5205

In article <jKm*WyMdA@news.chiark.greenend.org.uk>,
   Theo <theom+news@chiark.greenend.org.uk> wrote:
> Bob Latham <bob@sick-of-spam.invalid> wrote:
> > In article <lKm*B9HdA@news.chiark.greenend.org.uk>,
> >    Theo <theom+news@chiark.greenend.org.uk> wrote:
> > > Bob Latham <bob@sick-of-spam.invalid> wrote:

> > > So I think you have two options.  If you add 'no_root_squash'
> > > as in "(rw,sync,no_root_squash)" then you can access any file
> > > as root.
> > 
> > > Or you could set your uid/gid to match the ones on the Pi.  To
> > > find them out, run the 'id' command:
> > 
> > I've tried the easier method of adding 'no_root_squash' and it
> > appears to work but not quite. It displays all of the directories
> > in / the same as Lanman98 and I know some of those are virtual
> > directories but they display in both systems.
> > 
> > What doesn't work is /boot/firmware where important files like
> > config.txt should be but the whole directory is empty from
> > sunfish.
> > 
> > I have 'follow symbolic links' switched on, any suggestions?>

> /boot is a separate mounted partition (the FAT one on the SD card)
> and NFS doesn't follow mount points by default.  I think you need
> the 'crossmnt' option in addition to 'no_root_squash' to allow NFS
> to see into the mounted filesystem.

In the file /etc/exports I have:

/ 192.168.1.0/24(rw,sync,no_root_squash)

This works-ish It shows all the root directories the same as LM98
does. But it shows directories as empty, specifically /boot/firmware.
There are are others.

So I added crossmnt to the line ..
/ 192.168.1.0/24(rw,sync,no_root_squash,crossmnt)

I don't know if that's the correct way.

Now we get errors, strange errors.

Error when reading Sunfish::LinnPi/.$.boot.firmware - NFS call failed
(Stale NFS filehandle)

Thanks.

Bob.

[toc] | [prev] | [next] | [standalone]

#5206

Bob Latham <bob@sick-of-spam.invalid> wrote:
> 
> In the file /etc/exports I have:
> 
> / 192.168.1.0/24(rw,sync,no_root_squash)
> 
> This works-ish It shows all the root directories the same as LM98
> does. But it shows directories as empty, specifically /boot/firmware.
> There are are others.
> 
> So I added crossmnt to the line ..
> / 192.168.1.0/24(rw,sync,no_root_squash,crossmnt)
> 
> I don't know if that's the correct way.
> 
> Now we get errors, strange errors.
> 
> Error when reading Sunfish::LinnPi/.$.boot.firmware - NFS call failed
> (Stale NFS filehandle)

Hmm, I don't know.  Maybe it doesn't like crossmnt for some reason.

You could try making a second export for /boot or /boot/firmware and add a
second mount for Sunfish?

Theo

[toc] | [prev] | [next] | [standalone]

#5207

In article <kKm*IITdA@news.chiark.greenend.org.uk>,

> Hmm, I don't know.  Maybe it doesn't like crossmnt for some reason.

> You could try making a second export for /boot or /boot/firmware
> and add a second mount for Sunfish?

Thanks for all the help Theo.

Bob.

[toc] | [prev] | [next] | [standalone]

#5202

In article <1017r4e$3dqre$1@dont-email.me>,
   druck <news@druck.org.uk> wrote:
> On 27/05/2025 22:08, Brian Howlett wrote:
> > I recently acquired a Raspberry Pi 5, and am looking to connect to it
> > from RISC OS using LanMan 98, so far with no success.

> Instead of compromising my Raspberry Pi 5 NAS by enabling the old 
> horribly insecure SMB1 just for LanmanFS/98, I'm using the same NFS 
> shares from my RISC OS Pi 4 that the other Linux Pi's use.

> Once !SunFish is configured using the crashy front end, the back end 
> filing system is rock solid and I've not had a single problem with it in 
> a decade.

> ---druck

Mmnnn, Rather interesting thread...

Though I've tried a number of times in the past, I've never managed to get
the Sun thing to do anything/work.

So I still use LM98 (2.08)

Dave

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.acorn.networking

csiph-web