full access to ext4 files/dirs from win 7?

[Liam Proven]

On Thu, 9 Sept 2021 at 20:48, rikona <rikona at sonic.net> wrote:
>
> Yes. Sorry I didn't make that more clear. Many list folks have dual
> boot. I don't have that on any box, so I wasn't thinking in that way.
> All connections between OSs/boxes is via the LAN.

If we are only talking over the network then any and all
considerations of filesystems are totally irrelevant.

The local OS is what reads the local disks. So long as the local OS
can read the disk, that is *all* that matters. The OS on the other end
of the network does not know or care about the filesystems on the
other end of the wire.

Imagine I am on the phone to you. I speak English and Mandarin. You
speak English and French. I ask you for some information in a book. It
doesn't matter if your book is in French and I don't speak French; *I
am not reading the book.* I can't even *see* the book. *You* are
reading the book. So long as you can read it and tell me the info in
it, the language is irrelevant.

So by asking about OSes being able to read/write filesystems, you were
implicitly saying these were local disks and no networking was
involved.

> There are often access issues between these boxes, and the issue seems
> dependent on which box pair is involved. Primary interest is between Kub
> & win7, since I do most stuff on Kub, but need to use the win-only pgms.
> That was the topic of this discussion.

Better but still not really enough info.

What programs on what machines are accessing the other machines, how?
I assume it is all over TCP/IP, but (for example) are you using Samba
and SMB shares, or GNOME/KDE file managers looking at SMB shares, or
NFS shares, or FTP, or something else?

If you are accessing Windows shares from Linux then probably you are
using SMB. If so, are you mounting them from the command line (which
means Samba) or are you opening them in some graphical file manager?

You said KDE. I do not use it, but I guess it means Konqueror. Konqi
can directly access SMB shares and show their contents without you
mounting them.

If you mount them at a command prompt, you are using Samba. If you
don't mount them just browse graphically then you're *not* using
Samba, you're using the file manager's internal SMB access facilities.
But you don't say, so we don't know.

#1 consideration: you need matching user IDs on both ends.

Let's say the Linux box has user ID "rik" and password "mypass". Then
you need a Windows account called "rik" with a password of "mypass" --
even if you never log in using that ID, you need to create one.

> What I'd like to end up with is the ability to do ANY file/dir op on ANY
> box, from ANY other box, maintaining security of course. Maybe a lot to
> ask, but would sure be nice. :-) Sort of like the "net is the computer"
> phrase we used to hear. :-)

Make sure all your usernames on all machines are *EXACTLY* the same,
including capitalisation. Also ensure all your passwords match.

> Sorry for the confusion, and thanks for the help. Please let me know if
> any more info would be helpful.

Quite a lot more needed, I'm afraid.

If you are accessing Linux machines from Windows, all the above
applies, and more.

Samba maintains its own user and password database, separately from
the Linux one. You need to ensure these match and all the Linux
entries have matching Samba entries. I use a web-admin tool called
Webmin for this.

So now you have 3 sets of IDs:
[1] Windows usernames / passwords
[2] Linux usernames / passwords
[3] Samba usernames / passwords

For an easy life, ensure all 3 are matched, both IDs *and* passwords.

This makes a lot of pain go away.

Note: Windows has both long and short usernames. We are talking about
the short ones here; the long ones are cosmetic and largely
irrelevant.


-- 
Liam Proven – Profile: https://about.me/liamproven
Email: lproven at cix.co.uk – gMail/gTalk/gHangouts: lproven at gmail.com
Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven
UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053