Nash Central (and GennyOS or whatever its called these days) is a pile of shit. I wouldn't use it if I were you. The guy does absolutely no error checking anywhere in his scripts (unless he's absolutely forced to) and when asked for help he says "Oh, it works on my machine...". Right. Like his machines are a wide enough spectrum to test almost all possible hardware setups on. Little tip for you guys wanting to write custom installers for Linux: do not assume that just cause it works on your machine it works on *everything* or *everyone elses*! I'd highly recommend you either follow the Arch Linux setup guide and use Talking Arch, or I can attempt to update my (definitely outdated) setup guide that has worked on both hardware/bare metal and virtual machines. And since its a guide, it can be adapted and altered, unlike an installer script. I'm sorry that this post was a rant, but this guys "auto-install" shit (that most of the time breaks in exactly the *wrong* places, like formatting disks or installing packages, and leaving your system useless) is getting ridiculous. I mean, OK, its really awesome that he can get android on there and all, but he should make it a guide instead of a script. The pace at which Arch Linux moves is far faster than he can update a script in, or even a guide in. A guide though provides the groundwork instructions, and they can be adapted to fit irregular situations. You can find the Arch Linux install guide at https://wiki.archlinux.org/index.php/in … ion_guide.

*sighs*

Well, I will finally take the plunge n install arch in a VM.
BTW, the more direct linkfor more info can be found here:

https://talkingarch.tk/

I think the thing for me, having enough patience for setting it up.

At some point, I'll be getting a Thinkpad 420 for Linux only tasks, to go alongside my Dell Venue11 Pro 7000 Windows tablet.

NB. Updated title of thread to reflect the discussion of all accessible-based Arch distros.

Hello:

I appreciate your feedback. When performing either an arch or android install, which step in the install fails? If the bootloader installed correctly, which is done for both BIOS and UEFI systems, remove the installer from the virtual drive and restart the machine. If installing android, I would recommend installing to a flash drive and restarting the physical machine booting from the newly created drive, as modern versions of android x86 do not run correctly in vmware due to what appears to be incompatibilities with the virtual GPU. Also, I have found that both jenux and android install correctly using both VirtualBox and qemu, although emulation of the PC speaker does not work using VirtualBox. Also, at post 2, do you have any recomendations to implement not only error checking, but recovery in case of errors, other than running the failing step over and over until it returns success, which is what is being done with package installation and certain other steps like adding users in the post-installation segment?

@6, performing a step over and over until it succeeds is not going to accomplish anything other than to mess everything up even worse, if it doesn't just sit there and look like its doing absolutely nothing. That's like me executing a while loop, passing in data that turns out to cause errors, but just continuing to try over and over with the same data and continuing to cause the same error over and over because I want to try and "force" the system to do what I want. If an error comes up, your only option is to either bale out, or try different methods (cleaning up after yourself on the way) and, if none of those other methods succeed, bailing out too. You have no other option, and attempting to force the issue will not only piss your users off, but it will waste valuable resources. Use the || operator on every command, or check every commands exit code. Do not just "hope" it works. That will only cause huge problems if you just run commands and hope to god they work (and then they don't, or you break something).