You are not logged in.
When using a notebook with no access to LAN cables/ports, you have to execute these before executing archinstall itself:
iwctl
station wlan0 connect WIFI_NAME
WIFI_PASSWORD
exit
It would be more intuitive to type "archinstall" to open a UI (simple as archinstall's UI) for selecting wi-fi networks, then opening archinstall.
Offline
If you code it and submit a pull request I suspect it may be considered. But only so much can be automated: you need to specify the network and enter the password yourself - so a UI doesn't really help here other than to address discomfort with typing commands on the command line. And frankly, if typing commands in a text terminal is off-putting to you, then arch is really a bad choice of distro in the first place.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
If you code it and submit a pull request I suspect it may be considered. But only so much can be automated: you need to specify the network and enter the password yourself - so a UI doesn't really help here other than to address discomfort with typing commands on the command line. And frankly, if typing commands in a text terminal is off-putting to you, then arch is really a bad choice of distro in the first place.
It also solves the problem of having to memorize the commands when you only have that OSless notebook as smart device, avoiding typos such as iwlct , iwclt, wlan1 station connect, etc.
Offline
The iso has tab completion and man pages / help output. But more broadly, the archinstall script is meant for experienced users who would surely know how to connect to a network.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
The Arch wiki is very useful but sometimes there is so much information there that a newbie could easily get confused and can easily get lost trying to understand things even for an experienced linux user.
Online
MAYBl8, did you post in the wrong thread? Or in what way does that connect to the topic here?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
The iso has tab completion and man pages / help output. But more broadly, the archinstall script is meant for experienced users who would surely know how to connect to a network.
That's unfortunate. That's the only inconsistency in archinstall's design, and it happens to be a very noticeable one for Wi-Fi-only installations.
I'm curious, why are LAN connections automatic? Shouldn't we also, for sake of consistency for experienced users, have to manually configure a LAN connection?
Offline
Because wired connections do not require any user input or manual configuration (unless the user wants something specific like a static IP - and, guess what, then they need to do that manually). So clearly you're just trolling now. I'll not feed you any more.
Last edited by Trilby (2024-06-28 12:12:59)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I'm curious, why are LAN connections automatic? Shouldn't we also, for sake of consistency for experienced users, have to manually configure a LAN connection?
because they can be automated
in a usual personal network with a isp-provided modem/router/wifi-ap combo device it can be expected said device runs a dhcp server - hence just run a dhcp client and plug a cable between the two is sufficient
wifi on the other hand in fact does require at least srlecting the network, and a passphrase if one is in place
the one thing that may can be made mor convenient is to run a short scan for available networks and display them in a list so at least selecting the correct network is easier - but you still have to give the password
implementing WPS would be overkill - as mentioned: atchinstall isn't meant for newbs but as a helper for experienced users - which can to be expected either know how to setup wifi or have wired connection available
Offline
Fernando M. Muniz wrote:I'm curious, why are LAN connections automatic? Shouldn't we also, for sake of consistency for experienced users, have to manually configure a LAN connection?
because they can be automated
in a usual personal network with a isp-provided modem/router/wifi-ap combo device it can be expected said device runs a dhcp server - hence just run a dhcp client and plug a cable between the two is sufficient
wifi on the other hand in fact does require at least srlecting the network, and a passphrase if one is in place
the one thing that may can be made mor convenient is to run a short scan for available networks and display them in a list so at least selecting the correct network is easier - but you still have to give the password
implementing WPS would be overkill - as mentioned: atchinstall isn't meant for newbs but as a helper for experienced users - which can to be expected either know how to setup wifi or have wired connection available
Oh I see, so the fact that archinstall made Arch Linux very accessible is complete accidental/unintended?
That explains why the second reply by @Trilby seemed contradictory to archinstall 's purpose.
Offline
more or less, yes
Arch Linux is targeted towards users who have at least basic experience with linux and know thier way around - it's not meant for users new to Linux at all
hence it's expected that everyone who wants to use the archinstsll script has completed the regular manual install at least a couple times so they know what the script does and what information to provide - it's a helper to speed up the otherwise manual install
but: it has it's flaws as it's quite general and hence makes a few assumptions and takes shortcuts
I gave it a try once and can see its use for more rapid deployment - but for a single machine I'm faster just going the manual install
Offline