full access to ext4 files/dirs from win 7?

[rikona]

On Thu,  9 Sep 2021 15:10:08 -0400 (EDT)
Robert Heller <heller at deepsoft.com> wrote:

> At Thu, 9 Sep 2021 11:46:40 -0700 "Ubuntu user technical support,?
> not for general discussions" <ubuntu-users at lists.ubuntu.com> wrote:
> 
> > 
> > On Thu, 9 Sep 2021 11:34:58 +0200
> > Liam Proven <lproven at gmail.com> wrote:
> >   
> > > On Thu, 9 Sept 2021 at 08:59, rikona <rikona at sonic.net> wrote:  
> > > >
> > > > I may have done that when I set up the box - I tried to make it
> > > > like the 16.04 box, which did work with win.    
> > > 
> > > Hang on. You did not make this clear. These are different
> > > computers?  
> > 
> > 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.  
> 
> OK, you have two options:

Thanks much for the info!

> 1) The complicated, but allows for "transpatent" pointy-clicky via 
>    Mess-Windows explorer, way:
> 
>     Install Samba Server on the Ubuntu box:
>     
>     sudo apt update
>     sudo apt install samba
>     
>     Then you need to do a basic simple Samba set up (instructions
> available on the web), configuring shares as you desire. The shares
> will show up as available network shares on the MS-Windows machine,
> and when connected to, will show up in Mess-Windows explorer, just
> like local files. 

I think this is what I set up in configuring the new Kub box to be like
the 16.04 box, and what I am trying to use now. Has what looks like
permissions problems, so may not have set it up right. Just did some
copy tests. Copies to the Kub box are owned by 'nobody', 'noGroup', and
have severe access problems, probably as a result.

Also just noted that, in trying to edit a Kub file via the net, win7
creates a new dir entry called "core" which seems to be the edited
document. The original file name is still there but does not get
changed with an edit/save, and 'core' is locked - can't be
accessed/copied/renamed, etc. Not sure what's going on there...

> 2) Simpler way:
> 
>     Install openssh-server on the Ubuntu box:
>     
>     sudo apt update
>     sudo apt install openssh-server
>     sudo systemctl enable sshd
>     sudo systemctl restart sshd
>     
>     Then install a SSH client package on the MS-Windows machine (eg
> Putty). 
>     Now you can use Putty's scp and sftp clients to access files on
> the Ubuntu machine.  Not quite as pointy-clicky, but less work
> setting up.

This sounds good as an option - will try it. Doesn't have to be
super-pointy-clicky - just needs to work well. :-)) Will this likely
have the same permission issues as the above, though? Not clear if the
different permission policies in win/linux transfers will be permanent
issues.

Thanks for describing those options!

> >   
> > > That changes everything.
> > >   
> > > > OK - nice to know that seems like a good solution. Would it
> > > > work as well if the NTFS disk was on the Kub box, and not on
> > > > the win box? I do most stuff on the Linux box, the win box is
> > > > mostly for special win-only SW that I'd like to work directly
> > > > with files on the Kub box.    
> > > 
> > > Hang on again!
> > > 
> > > You said that Windows could access the contents of drives
> > > formatted with Ubuntu.
> > > 
> > > This is nothing whatsoever to do with networking.
> > > 
> > > If you are talking about network connections then YOU *MUST* SAY
> > > SO.
> > > 
> > > Please explain again more clearly what is going on, including
> > > details of what machines and how they are connected.  
> > 
> > OK, multiple boxes:
> > A semi-retired 16.04 Ubuntu box, rarely used now
> > A new Kubuntu box, set up like the 16.04 [similar pgms, file
> > organization, etc]
> > A becoming-old win 7 box, mostly win-only pgms, costly to upgrade
> > them to win 10/11, so keeping the older ones
> > a Mac, used much like the Kub box [gives me dozens more open
> > browser & work pages :-) ]
> > None are dual boot, all on the same LAN, all box interactions of any
> > kind [edit, new, copy, etc] are hardwired via the LAN/router.
> > Phones - occasionally interact with boxes via WiFi 
> > 
> > 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.
> > 
> > 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. :-)
> > 
> > Sorry for the confusion, and thanks for the help. Please let me
> > know if any more info would be helpful.
> > 
> >   
>