Requires internet connection for base install #817
Comments
|
I was able to use my phone for hotspot and confirmed that 4GB of data was pulled. This is problematic, as I literally just downloaded an ISO of equal size that was completely up to date and contained the same packages, so what is going on here? |
|
Can you capture /root/clr-installer.log and add it here, please? This should contain more detailed messages about attempting offline installation. |
installing from 42150 |
|
Mine looks very similar. But still exists with latest ISO (guaranteed fully up to date). Completely ridiculous to deploy an entirely broken installer that ignores the 4gb download you just did, to download another 4gb from the net, with packages EXACTLY IDENTICAL to what's on the ISO. I literally can't believe it's possible for a bug this ridiculous to exist. You don't need a log to reproduce this. Just try it. This isn't some one off thing. It also persists in the text mode installer. I change telemetry, set a user، change time zone, select destructive install on a disk, and literally nothing else. No packages selected. |
Because it's not a bug. I spent a while in the source code investigating this. That's just not what was implemented. The |
|
Oh. Well, that works. But it's far from ideal, nor is it best practice to require a workaround for what should be a basic functionality (and is, in most other OS's). It's definitely still an issue. It's never mentioned during the install, doesn't really adhere to common sense, negates the use of delta files and hammers the network system twice for every install (costing tremendous bandwidth waste for the default installation for users and you alike), and is generally not how any other distribution works. Since efficiency is king for clear Linux in many other ways, something so wildly antipathic to that ethos sticks out like a sore thumb. How can one save the yaml file and get it to persist through a reboot into the command line installer mode? Alternatively, how can one call up the command line when already booted and point to the file? What's implemented seems like a hack, and doesn't match the spirit of what was announced years ago, and doesn't make intuitive or UI design sense. Rather than have users deeply research how to go through this runaround, why can't the installer simply proceed with an offline installation exactly like the command line one would? More fundamentally, what's the point of even having your own installer if it is so incomplete (yes, I use the superlative "so" because this is a gaping oversight in a graphical installer and violates most best principles) compared to other installers already out there? I think this is still a bug. The desire to acknowledge it as a coding technicality or simply a (substantial) UI and usability misstep notwithstanding, it clearly needs to be fixed/improved to meet user expectations of basic functionality. |
|
I need a checkbox that adds the Unless the GUI installer and the CLI installer are different entities and operate in completely different fashions. |
I agree, that makes sense. I do want to point out that offline installation in Clear Linux works completely differently than in other distributions. For an RPM-based distro, for example, they just need to include repodata and a pile of RPMs in the image, and ask
But it's still about 2.5 GB. |
|
Looks like there's some more chatter on the issue, and the --offline flag also doesn't work anymore. There is a workaround script in the thread: #808 |
Agree. Nothing in the announcement implies --offline or other requirements exist to perform an offline install, and in my case I was not even doing the live install - just the standard one (but I agree both should be able to offline install direct from the mounted iso as the default behavior, just like most other distros). For test system environments, offline install is a thing that needs to work, and it being broken effectively removes Clear as a possible distro for use in any secure / air gapped environment.
I believe that is broken as well. |
This was supposedly fixed in 2019.
But with absolutely nothing configured or installed, no bundles selected, here's what the live installation CD does.
When it fails, I get kicked back to the installer and cannot progress.
Kernel 6.10.12 (very recent, build 42440) live desktop.
Clearly a bug
The text was updated successfully, but these errors were encountered: