samba - Aug 2021 - DC controller and DNS

?? Ok...............
This is not good news. BUT:

 ??? I can:

1)?? convert the packages that you indicated and install them. I have no 
idea if this will work.

2)? deep six the Slackware and setup a Debian machine. I have no idea 
how this will affect
the user that is connected to the controller at the moment. The Debian 
DC will have a different
IP than the Slackware.

 ??? I am not sure if I should spend any time with choice number one as 
I don't know what will
happen.

On 8/4/21 03:02, Rowland Penny via samba wrote:
> On Tue, 2021-08-03 at 17:37 -0400, ve2cii--- via samba wrote:
>>      You could be right about something missing.  Let me know if there
>> is
>> something required that
>> is not on my list and I will see if it is missing.
>>       I have not done a slackware install using dhcpd since
>> slackware-10.0. Everything I do is
>> all manual, and since the Slackware network manager is crap I
>> usually
>> leave that out and
>> do it manually. So I never noticed the empty resolv.conf file. This
>> is
>> why I run Debian on
>> my laptop, which uses WIfi. But I digress!!
>>
> OK, I officially give up, to build Samba, you need python3 and these
> packages (amongst others):
>
> python3-cryptography python3-dbg python3-dev python3-dnspython python3-
> gpg python3-iso8601 python3-markdown python3-matplotlib python3-pexpect
> python3-pyasn1
>
> I cannot find 32-bit versions of the above packages.
>
> You cannot make bricks without straw, not unless your name is Moses.
>
> Can you really not use another distro ? Or upgrade to 64-bit Slackware
> at least ?
>
> Rowland
>
>
>

On Wed, 2021-08-04 at 08:48 -0400, ve2cii--- via samba
wrote:
>     Ok...............
> This is not good news. BUT:
> 
>      I can:
> 
> 1)   convert the packages that you indicated and install them. I have
> no 
> idea if this will work.
It may, or may not, work. Whichever, it will be a very lot of work. As
you already have a Samba AD DC, I would create a new Debian Computer,
using Louis's repo and join it as a DC to the domain. Then transfer the
FSMO roles to the new DC and demote the original DC.
> 
> 2)  deep six the Slackware and setup a Debian machine. I have no
> idea 
> how this will affect
> the user that is connected to the controller at the moment. The
> Debian 
> DC will have a different
> IP than the Slackware.
This shouldn't be a problem, just change the clients nameserver to
point to the new DC.
> 
>      I am not sure if I should spend any time with choice number one
> as 
> I don't know what will
> happen.
> 
Probably a lot of work that will get you nowhere.

Rowland