Building esos: wget on util-linux-2.36.1.tar.xz during make gives http error 403 / forbidden

26 views

Skip to first unread message

Steffen Hansen

unread,

Jul 18, 2025, 2:00:38 PMJul 18

to esos-users

Trying to build esos with Intel IGC support.

Partly following the original guide and partly this here thread: DRBD failing after upgrade

When running step 11: "make -j4 -w -Orecurse > /tmp/bootstrap.out 2>&1" I get an error in /tmp/bootstrap.out when it tries to download util-linux-2.36.1.tar.xz

[bootstrap.out]

### Fetching /home/sthan/development/esos/work/dist_files/util-linux-2.36.1.tar.xz
wget -t 5 -P /home/sthan/development/esos/work/dist_files http://download.esos-project.com/dist_files/util-linux-2.36.1.tar.xz
--2025-07-15 09:59:07-- http://download.esos-project.com/dist_files/util-linux-2.36.1.tar.xz
Resolving download.esos-project.com (download.esos-project.com)... 104.18.14.222, 104.18.15.222, 2606:4700::6812:fde, ...
Connecting to download.esos-project.com (download.esos-project.com)|104.18.14.222|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2025-07-15 09:59:12 ERROR 403: Forbidden.

[/bootstrap.out]

Following the thread linked to above, and re-running without -j4 (Step.12) give the same error so I never get an chroot_build.sh file.

Question 2. Should there be output when running "sudo make symlink"?

BR - and thank you,

Steffen

Steffen Hansen

unread,

Aug 1, 2025, 3:31:07 PMAug 1

to esos-users

update on this.

I got the above wget error when playing around with building esos at work. Figured out I could find the sources elsewhere and just drop them in ~/work/dist_files and the script would see them and skip that step. When doing it at home, I didn't get the error, so guessed someone might have fixed some permissions in the meantime. Yesterday when I tried at work again I got the same error.

Anyway - I have done several builds now - both with the igc driver as module or fixed in the kernel. No matter what, esos will not see the I226-V nic. The NIC is seen in e.g. kern.log but and the driver can be loaded (as module) or seen as active when fixed - but no matter, no 2.5Gb NIC to be seen as active anywhere.