Do you need to do anything special? It seems like there's a --noipv4ll
switch on invocation of dhcpcd or a noipv4ll
option for /etc/dhcpcd.conf
Sources: https://manpages.debian.org/buster/dhcpcd5/dhcpcd.8.en.html
If dhcpcd failed to obtain a lease, it probes for a valid IPv4LL address (aka ZeroConf, aka APIPA). Once obtained it restarts the process of looking for a DHCP server to get a proper address. When using IPv4LL, dhcpcd nearly always succeeds and returns an exit code of 0. In the rare case it fails, it normally means that there is a reverse ARP proxy installed which always defeats IPv4LL probing. To disable this behaviour, you can use the -L, --noipv4ll option.
https://wiki.archlinux.org/title/Avahi
By default, if you are getting IP using DHCP, you are using the dhcpcd package. It can attempt to obtain an IPv4LL address if it failed to get one via DHCP. By default this option is disabled. To enable it, comment noipv4ll string
Bold: disabled on their configuration, because they place the option there by default.
I ran the Adelie 1.0rc2 "no DE" installer and dropped into Tools/Terminal to test. From the default, yes, dhcpcd will set up IPv4LL after failing to get a lease:
Rebooted and added noipv4ll
to the end of /etc/dhcpcd.conf before trying to get a lease.
And dhcpcd exited without configuring IPv4LL (APIPA):
Those all seem like very good reasons to make SDDM (or other graphical login) an option as well and not auto-select it whenever a DE or WM is selected.
If you're asking me, I agree that documentation doesn't need to be pre-selected in the "Custom" option; being an option and being unselected informs the user that by default the documentation won't be there if it's not selected and the user can decide accordingly.
Confirmed that this also happens on VMWare Workstation.
I think I'm interpreting this correctly. I chose a Custom Install in Horizon, with the options:
Horizon finished the install and I booted into the new system: never reached GUI, VTY 7 only had a blinking cursor
Opened another VTY and tried $ startx
and # startx
: "not found"
Tried again with the same options and this time saved the installfile and opened it to check what's being installed:
Installed a "Standard" configuration and opened the installfile to compare:
X11
and sddm
packages are being installed on "Standard" but are missing on "Custom"
Shouldn't the selection of any item from "Desktop Environments" or "Windows Managers" automatically add X11 (and probably sddm as well, to manage the DE)?
One part of this issue looks like issue #321 (closed) (installer not having enough permissions); try the workaround mentioned there.
The other part can be an issue by itself; the LiveCD installers don't activate DHCP by default - and if it has anything to do with missing wpa_supplicant, it also happens to me on a VirtualBox VM with only an Ethernet card (eth0). I have to drop to a rootshell and dhcpcd eth0
to activate the network interface.
But if you run horizon-ui
as root, then the installer has permissions, and can autoconfigure DHCP in the "Automatic" installer step; the other symptoms are likely to also go away.
That's basically it. I chose "pt" layout on HorizonUI, and the KDE on the hard disk has "en-us" installed, and "pt-pt" still has to be added manually in KDE's settings afterwards. Other installation variants couldn't be tested.
I can put any value I want, and Horizon will let me proceed, not validating the fields or trying to configure an interface and then ping the chosen DNS server and/or Adélie's repos as a sanity check. I have configured:
And Horizon just let me hit Continue (F8)
without signaling any error.
After booting from one of the 1.0rc2 LiveISOs (tested MATE and LXQt variants), HorizonUI ("Applications > System Tools > System Installation" on MATE) doesn't work when launched from the GUI:
Workaround:
Open a Terminal window, jump to a rootshell, open # horizon-ui
from root
Hello. As much as I understand that Adélie is very close to Alpine, and most versions of Alpine do not include manpages by default, I think it's unnecessarily user-hostile to not include them and it sets Adélie very much apart from most mainstream distros as an "expert-only" distro. Text compresses very easily. and man decompresses pages on the fly. They are not installed in the MATE or LXQt ISO, are not installed on hard disk by the "Standard" option of HorizonUI (the only one from 1.0rc2 that completed installation), and on the "Custom" installation options it's not selected by default. Unfortunately I wasn't able to test any custom installation options, HorizonUI failed every time. But that's another issue.
Well, from what I can see on my VM's activity while installing Adélie 1.0rc2, everything is always installed from Adélies repos or mirrors and nothing comes from the ISO; AFAICT, the ISO is just the binaries needed to run Horizon-UI. [edit to add] Which would mean that this issue seems to be basically unsolvable, unless you have a local copy of the repos and modify horizon-ui to go look in there; Adélie installation from ISO requires network access.