samba - Jan 2025 - Samba in a dual boot environment

In response to the last comment, generally speaking, is the AD aspect of dual
booting challenging even with an external standalone Samba share? Overall we do
not have much experience with dual booting, but having separate computers for
each OS is not an option.


-------- Original Message --------
On 1/16/25 8:03 AM, Rowland Penny via samba <samba at lists.samba.org>
wrote:
>  On Thu, 16 Jan 2025 16:44:16 +0100
>  Christian Naumer via samba <samba at lists.samba.org> wrote:
>  
>  > I'll try to describe the "pitfalls":
>  >
>  > * You need to have your data on a separate partition with the NTFS
>  > file system -> Windows can only read these.
>  >
>  > * You need to mount that partition under Linux. That works, BUT ACL
>  > support is limited and interaction with Samba and NTFS might have
>  > issues if your ACLs are complex. Then you need to share that
>  > partition or a directory on there with both Samba and Windows.
>  
>  Saying 'limited' is a bit weak, I would say ACL support is
virtually non
>  existent, the permissions you see when you mount an NTFS share on Linux
>  are totally fictitious.
>  
>  >
>  >
>  > Since you have no AD the computername should be the same under
>  > Windows and Linux. You need to create the users in both the OSes.
>  > There is no way to sync the users.
>  
>  The OP never said that there was no AD and you do not need the same
>  users, you just need to know who they are on the other OS, at least on
>  the Linux side.
>  
>  >
>  > All doable just wanted to point out the pitfalls.
>  
>  Dirty great crevasses, I'd say ;-)
>  
>  >
>  > Did you want to sync the files between the two OSes by Dropbox? So
>  > you would use up twice the space? That would also work.
>  >
>  > If you are firm with Linux the dual boot should also be viable for
>  > you.
>  
>  I would never recommend dual booting and trying to access one OS
>  partition from the other OS, too many things can go wrong, this is one
>  reason I stopped dual booting over 15 years ago.
>  
>  Rowland
>  
>  
>  --
>  To unsubscribe from this list go to the following URL and read the
>  instructions:  https://lists.samba.org/mailman/options/samba
>  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 322 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.samba.org/pipermail/samba/attachments/20250122/0453da56/signature.sig>

On Wed, 22 Jan 2025 14:36:24 +0000
componentscience via samba <samba at lists.samba.org> wrote:
> In response to the last comment, generally speaking, is the AD aspect
> of dual booting challenging even with an external standalone Samba
> share? Overall we do not have much experience with dual booting, but
> having separate computers for each OS is not an option.
> 
When you dual boot two OS's, you usually have each OS in its own
partition and each OS boots okay. If you then try to connect from one
OS to the other os's partition, then this is where the problems can
start.

Windows requires an NTFS filesystem, but Linux requires a partition
formatted in ext4, btrfs etc, anything but NTFS. Windows can mount a
Linux partition, but usually read only and it is basically the same
with regards to Linux mounting a Windows partition.

If what you are thinking of doing is starting the computer in one OS
and then connecting to the other OS's partition and changing things,
then I cannot recommend doing this.

You could add a third partition and connect to this from either OS, but
if you do this, I would suggest formatting it with exfat and only using
it for storing low privileged items.

You will need to install Windows first, otherwise you will have to fix
the Linux install after installing Windows. You should also be aware
that Windows updates have been known to stop Linux booting in a dual
boot setup.

Have you considered running one of the OS's in a VM on the other ?

Rowland

Am 22.01.25 um 15:36 schrieb componentscience via samba:
> In response to the last comment, generally speaking, is the AD aspect of
dual booting challenging even with an external standalone Samba share? Overall
we do not have much experience with dual booting, but having separate computers
for each OS is not an option.
> 
If the samba share is on another computer not in the AD this should work 
fine and easy.
Just be aware that you need a computer account in the AD for each 
operating system. So you have to join the domain twice. Once with each OS.
If you have 2 computer accounts you could also join the standalone Samba 
server to the AD. In this case it does not matter.

Regards

Christian