On Wednesday, April 01, 2015 07:11:29 PM Mateusz Lemusisk wrote:

I can go with that.

Apart from that, the antergos project is trying to build an graphical installer, and it holds itself as close as possible to arch linux. -- Sent from my toaster

I actually have a tool I use to create Arch Linux OS. It works pretty well for me. It's used to generate USB {H,S}DD OSes. https://github.com/bluerider/mkportarch/blob/master/mkportarch Regards, Mark

On Wed, 1 Apr 2015 14:46:48 -0300 Bráulio Bhavamitra wrote:

On Wed, Apr 1, 2015 at 2:00 PM, Mark Lee wrote:

...

On Wednesday, April 01, 2015 01:53:57 PM Bráulio Bhavamitra wrote:

...

Hello all,

After some many years, I'm back to ArchLinux. One thing that took me time was to read the manuals and run all the commands for installation.

That made me wonder on how automation might help things get easier and faster on install. Could you please tell the current works on that?

The result of my work was this script:

https://github.com/brauliobo/gitconfig/blob/master/histories/archinstall.sh

...

cheers, bráulio

To Barulio,

Interesting; but Arch is insistent on KISS for the system as a priority. Your script seems to specific to a particular wireless module (ath9k) and still requires some user interactions judging from your use of "nano".

About KISS, as I said it took some time and learning for me to understand and run commands, because there are MANY SIMPLE commands and configurations. Some automation would make it more KISS.

That depends on how you define KISS. It could make it more simple for the user, but it makes the system more complex. If it's something that needs to be done exactly the same way over and over, a script makes sense (arch-chroot is a good example). For something that will vary from system to system and configuration to configuration, automation just gets in the way. Doug

On 04/01/2015 06:53 PM, Bráulio Bhavamitra wrote:

...

Hello all,

After some many years, I'm back to ArchLinux. One thing that took me time was to read the manuals and run all the commands for installation.

That made me wonder on how automation might help things get easier and faster on install. Could you please tell the current works on that?

I think it's for the best that the installation stays like this. Archlinux has always strived for minimalism and simplicity. It's really not that hard to install, although it does require some basic shell knowledge and the wiki does a pretty good job of explaining how to install. I believe this is by design, and should remain like this. I'm always telling people that Archlinux is NOT for complete novices or people who want to click-solve everything and are afraid of the console.

This is what makes archlinux stand out, there are plenty of distros that have fancy python/whatever graphical installers. I don't use them anymore, but I respect them, and should be around if we want Linux to be adopted more. Indeed. I'm impressed by the graphical installers, but arch's installation is actually very easy.

The 'hardest' part is remembering which basic configs to change (e.g., locale, hostname, timezone). Otherwise, installing pretty much just involves: 1) Partitioning the drive using gdisk/fdisk/cfdisk/cgdisk 2) Formatting each partition 3) Mount each partition 4) pacstrap /mnt all of your packages here 5) arch-chroot /mnt; install bootloader and genfstab; change hostname or do any preconfiguration 6) Reboot into new arch installation. Same steps as the graphical installers, really, except that you get to easily preinstall several packages. My hdd began failing this past weekend. All I had to do was back up my configs, dump a list of installed packages (pacman -Qqe), install arch, and pacstrap the list of installed packages. I was up and running within 1.5 hours. It's hard to beat that simplicity. --Stephen

On 04/04/15 at 06:47pm, Roman Neuhauser wrote:

# brauliobo@gmail.com / 2015-04-01 13:53:57 -0300: Hello all,

After some many years, I'm back to ArchLinux. One thing that took me time was to read the manuals and run all the commands for installation.

That made me wonder on how automation might help things get easier and faster on install. Could you please tell the current works on that?

The result of my work was this script: https://github.com/brauliobo/gitconfig/blob/master/histories/archinstall.sh

https://wiki.archlinux.org/index.php/FAQ , Judd Vinet "Arch is what you make it"