What happens on 1/1/2022 with current FreeBSD Servers running DirectAdmin?

roman_m

Verified User
Joined
May 5, 2005
Messages
193
Location
Ukraine, Kiev
I understand that you need updates if you want to continue running DA on FreeBSD systems. Dropping support means we release no updates at all. So running DA on FreeBSD becomes unfeasible.

Backporting the fixes is exactly the efforts we want to avoid because FreeBSD user-base is minuscule.

Would you be willing to test out DA 1.642 build for FreeBSD? Build id 4a38a5301c046acba29dd2dfb9fcb1c9c9ce903c.
Thanks, 1.642 works well on FreeBSD 13.1 with binary patch for 'tar --ignore-failed-read'. Now I have all I need (including modern file manager in custom 'enhanced' skin).

% /usr/local/directadmin/directadmin info

commit sha: 4a38a5301c046acba29dd2dfb9fcb1c9c9ce903c
OS slug: freebsd_amd64
detected OS slug: freebsd_amd64
package: directadmin_4a38a5301c046acba29dd2dfb9fcb1c9c9ce903c_freebsd_amd64.tar.gz
gettext support: yes
gettext path: /usr/local/directadmin/data/lang
eol timestamp: 1640995200
eol time: Jan 1 00:00 2022


% readelf -d /usr/local/directadmin/directadmin

Dynamic section at offset 0x17577c8 contains 28 entries:
Tag Type Name/Value
0x0000000000000001 NEEDED Shared library: [libexecinfo.so.1]
0x0000000000000001 NEEDED Shared library: [libm.so.5]
0x0000000000000001 NEEDED Shared library: [libthr.so.3]
0x0000000000000001 NEEDED Shared library: [librt.so.1]
0x0000000000000001 NEEDED Shared library: [libc++.so.1]
0x0000000000000001 NEEDED Shared library: [libcxxrt.so.1]
0x0000000000000001 NEEDED Shared library: [libgcc_s.so.1]
0x0000000000000001 NEEDED Shared library: [libc.so.7]
0x000000000000000c INIT 0x4c5698
0x000000000000000d FINI 0x1255af8
0x0000000000000004 HASH 0x400280
0x000000006ffffef5 GNU_HASH 0x413800
0x0000000000000005 STRTAB 0x46c7c0
0x0000000000000006 SYMTAB 0x428888
0x000000000000000a STRSZ 319496 (bytes)
0x000000000000000b SYMENT 24 (bytes)
0x0000000000000015 DEBUG 0x0
0x0000000000000003 PLTGOT 0x1d589e8
0x0000000000000002 PLTRELSZ 8640 (bytes)
0x0000000000000014 PLTREL RELA
0x0000000000000017 JMPREL 0x4c34d8
0x0000000000000007 RELA 0x4c0358
0x0000000000000008 RELASZ 12672 (bytes)
0x0000000000000009 RELAENT 24 (bytes)
0x000000006ffffffe VERNEED 0x4c0268
0x000000006fffffff VERNEEDNUM 5
0x000000006ffffff0 VERSYM 0x4ba7c8
0x0000000000000000 NULL 0x0
 

fln

Administrator
Staff member
Joined
Aug 30, 2021
Messages
358
Could you share some details why binary patch for tar --ignore-failed-read is needed? And what the patch actually change?

If everything works fine I could mark this build as available upgrade for all existing FreeBSD installations.
 

roman_m

Verified User
Joined
May 5, 2005
Messages
193
Location
Ukraine, Kiev
Could you share some details why binary patch for tar --ignore-failed-read is needed? And what the patch actually change?
bsdtar does not support --ignore-failed-read, it exits if launched with '--ignore-failed-read'. The default bsdtar behaviour is to skip failed / unreadable files (eg sockets/pipes).

% tar --ignore-failed-read cf tar: Option --ignore-failed-read is not supported Usage: List: tar -tf <archive-filename> Extract: tar -xf <archive-filename> Create: tar -cf <archive-filename> [filenames...] Help: tar --help

The ticket about this issue is #40270 in your helpdesk, and no fix for it in 1.63.9, so I just find a bytestrings matched '--ignore-failed-read' then replaced them with 0x020 in a directadmin binary itself, sorry.

If everything works fine I could mark this build as available upgrade for all existing FreeBSD installations.
Yes, it's running fine and do all the job it needs to do.

EDIT: I does not use custombuild. All my system packages is native pkg or ports builded. I maintain a private pkg repo for all my FreeBSD/DA servers, so updating/upgrading is not a problem. If custombuild is shipped with gnutar, so this issue with '--ignore-failed-read' is not an issue at all. I prefer bsdtar.
 
Last edited:

fln

Administrator
Staff member
Joined
Aug 30, 2021
Messages
358
There is new build d7744c8cd599ea493cd8413ccadbb904e057381b without --ignore-failed-read but otherwise identical to the one you tested-out. It is marked as a latest version for FreeBSD systems. It should trigger new version available notification in the GUI.
 

roman_m

Verified User
Joined
May 5, 2005
Messages
193
Location
Ukraine, Kiev
There is new build d7744c8cd599ea493cd8413ccadbb904e057381b without --ignore-failed-read but otherwise identical to the one you tested-out. It is marked as a latest version for FreeBSD systems. It should trigger new version available notification in the GUI.
Thank you and have a nice day!
 
Top