Why you (probably) shouldn't use an Arch Linux install script

[@icarius9272]

The next thing is: I use Arch without Archinstall btw

[@EricMurphyxyz]

Based

[@Marc42]

Gave you like no. 70, and I'm terribly sorry!

[@laughingvampire7555]

nah, is going to be "I use LFS btw"

[@GEOEGII555]

And then: I use arch without archinstall and pacstrap btw

[@samuelnick9190]

I love candy BTW 🌚

[@goldibollocks]

Manually installing Arch cured my depression... at least for a day No seriously, it made me feel like I had accomplished something and even though it took some time to get everything running, it didn't feel like wasted time but like actually learning something about computers/linux. Was a really positive experience!

[@eekee6034]

These things are good if you've got a lot of time and need to use it productively. Maybe I should get back into Linux... but sadly, my form of depression tends to shut down the reasoning part of my brain just when I need it most. This results in _rage against the machine, not letting me do what I want!!!_ lol It could be turned into a comedy sketch. I've tried to use more straightforward OSs from BSDs to Plan 9 From Bell Labs, but the story is always the same in the end: A task seems easy, but when I'm deep into getting it done, a door opens into what feels like a whole new world of complexity and my brain just reacts with _raaayyyggge!_ lol "Stupid machiiiine!!!"

[@MaxJM711]

​@@eekee6034Hey man! Hope things get better for you. Normally the same kinda happens to me, actually happened while installing Arch lol had some trouble with the memory partitions and with pacstrap and got very frustrated with it. In the end I took it as an opportunity to learn: installed Endeavour OS and I'm using it to learn how Arch related stuff like dependencies and packages work, no regrets at all!

[@weirdo3116]

i just don't understand why every installation guide I see for arch is wildly different. or at least it feels that way.

[@0xCAFEF00D]

I was disappointed that I learned less than I expected. Despite my goals to learn I used pacstrap and it does the work for you really aside from bootloader and partitioning the rest is system configuration (arguably it's all system configuration but I think my point is clear). The wiki is very good at guiding you in the direction of understanding the system more but because of the arch install process you're not learning about how Linux systems are for the most part you're mostly learning a set of tools that are common or have been installed and are given snippets that are useful to configure them. But you rarely learn what these tools do for you really. A fresh arch linux user couldn't tell you if they could replace any of those tools easily or not. There's very few tools you know if you could replace. The one big exception to that that I like is the approach to the AUR on the wiki. They encourage you to understand the package descriptions. That really helps open up the idea of how simple (except sometimes laborious if you were to fetch every dependancy yourself) software installation really is on arch. Especially how helpers aren't really useful but it gives a small glimpse into packages that you don't really get with normal use of pacman. I think there should be a Linux install distro or process that's designed for you to understand the system. Not really intended to be a good system just something that gets you to the point where you have a basic familiarity with what happens at a lower level when you do certain actions. Things like how a keyboard press is processed or how a device is detected and attached to the system. An arch install doesn't even mention udev. If you install the system you should feel you want to read about device files block devices a little bit. The two three paragraphs on wikipedia are fine, not linux kernel documentation. Someone who's installing arch through the manual process won't understand why "everything is a file on linux". You get the black box view of the system. Why that should be an install and not just people taking their own time to understand their system. I think it has special appeal to be building your thing as you learn it. And it also leaves you with a smaller subset of the system to understand at any point of time. For instance when you reach the step of having installed the minimal subset that allows you to throw a ping, you know nothing else is needed for this. But I'm not asking to create /usr /etc /bin /sbin and set permissions. That's too manual and repretitive you learn nothing. Being told that the filesystem looks like that for what reason and what the use is is good enough. I'm asking to dip my toes in every part of the system so I at least know the names. And for important components of the system I should have a basic familiarity when it's done.

[@eekee6034]

@@0xCAFEF00D Very interesting. I knew Linux pretty well; I built Linux install from scratch before I tried Gentoo, before Arch even existed, so I was wondering how an Arch install would really look to a new user. Thanks for writing it up.

[@alangamer50]

My Linux experience: -Use archinstall -"Wow this so much easier than internet made it seem" -Why my audio not working -"Go read the manual fucker" -Fight with PulseAudio for 5 attempts -Realize PulseAudio was working the whole time and bluez was the problem -Fight with bluez for 3 hours -It finally works -Never more proud of myself

[@0fficechair]

-realize that the grub archinstall doesn’t work with my dell bios

[@BerserkerErik]

​@@0fficechairYup had the same issue a while back.

[@alvinbontuyan8083]

-installs and hooks up pipewire and every problem immediately dissapears

[@spaceghostmiid]

i absolutely hate the "go read the manual" people in the linux community. sometimes i really don't feel like reading several paragraphs about why and how different commands work on a page so bright it scorches my retinas out. sometimes i just want to copy and paste a couple commands in my terminal and have my problem solved without learning about the ins and outs of a package i'm going to configure one time ever.

[@blobzilla6944]

thats me with linux mint 😭

[@jhonyortiz5]

People will learn more by doing it the "wrong" way than by not doing it at all. The script isn't perfect, it doesn't teach you as much, but it makes it approachable. No one starts by painting a mona lisa. You start by drawing apples, or coloring books. That's what the script is. Is place to start for those that maybe are too scared to even start. And the same is true for arch distros. I agree, often there is problems with them. But it's better than having people never even try arch. Learning slowly, at your own pace is valid. You don't need to jump knees deep into building your own system. I've learned a lot by just solving problems as they come instead trying to learn all at once. I definitely think this video is well intended but very much off the mark.

[@FeTetra]

i actually find that the arch install script offers more depth and customization over using a standard gui installer and i learned a bit of new stuff from it

[@jhonyortiz5]

@@FeTetra that's awesome because it only means that people WILL learn from it even if they are not learning everything at once. It's guided learning and that's more approachable.

[@FeTetra]

@@jhonyortiz5 I personally hate the gatekeepers and find that the way I learned Linux to begin with is letting it in slowly and archinstall is a good way to install arch and use it in an easy and mentally manageable way for the first time, and that's not to say you can't later reinstall it without arch install for a more custom experience

[@jhonyortiz5]

@@FeTetra exactly, 100% agree 👍

[@laughingvampire7555]

if you care about learning then stop posing with Arch/Gentoo and use LFS

[@averageweird8158]

Arch has become the same thing as Souls games, the same passive-agressive attitude of "it's okay if you don't like it, but if you don't like it you are inferior"

[@thingbing3092]

"You're not a real Arch user if you heal"

[@reckermatouvc]

as someone who both uses Arch and platinum'ed Dark Souls, I sadly have to agree that both communities are often unbearable because they feel like they'll lose their bragging rights if it becomes accessible...

[@Kagawwy]

Gatekeeping is based

[@ainz2579]

​​@@reckermatouvc well they do. if you can't install arch without arch install you are eventually gonna nuke your system but if you can but don't want to because you actually have a life and can't spend 3 hours installing an os then its ok and with soulsborne games,if it becomes accessible then its just another AAA title and its ok if you can't enjoy a game like that because you have low T and fold in the face of adversity

[@plebisMaximus]

Yea nah. I've installed Arch both ways and the only thing manual installation taught me was that I'm in fact capable of following instructions. I learned far more fighting with Debian to get non-free repos set up. Arch isn't a specialist piece of software for the elite of the elite, it's just a bit of a cumbersome OS. With archinstall you get a functional and fine system in no time at all that anyone can use. It can break, yes, but so can any other rolling release distro and either you can fix it or you can't and will have to reinstall. The install process won't teach you to fix a fucked bootloader, learning to fix Arch is no different to learning to fix Tumbleweed or Void or whatever else. You learn because you have to after you installed a rotten update, not because you went through the obnoxious process of manually partitioning drives in cfdisk.

[@justadude8716]

finally a sane take

[@coffee-es9di]

I agree and disagree. AS LONG AS, you have some sort of IT knowledge beforehand, and have developed nicely the skills of, and for the sake of simplicity lets call it "following and understanding instructions you knew nothing", you are good on skipping the manual installation. If its your first real practical experience and dont really know the theory of everything that's needed to do when manually installing, doing it and skipping archinstall its a nice idea, because while it gives you the IRL experience, you also get to read and understand many things, like how partitioning works, how disks works, how packages and filesystem structure works, etc. But, if you already knew some of that stuff beforehand THOUGH you may never have done it manually, you are ready to go on archinstall.

[@h2oant546]

It really does feel like the Arch community is just trying to gate keep an OS. My first few times I installed it manually, took me like 30-40 minutes to setup. While for Archinstall it takes like 10 minutes at max to get everything done and working just fine. So far been enjoying Arch. Went from W10 -> W11 -> Dual boot Mint + W11 -> Dual boot Arch + W11.

[@coffee-es9di]

@@h2oant546 Maybe, but I dont really care. I mean, at least it is insanely well documented EVERYWHERE, there are communities that not only gatekeep even harder than what arch might, but also have NO INFO whatsoever anywhere. Also, at least for me, I dont think Arch comm is gate keeping, its mostly for the memes and sure there's always a couple A-holes that are like that, but overall, Jesus, I had a worst time on Hyprland...

[@JWJ212]

@@h2oant546 I had no problem installing Arch my first time ever trying Linux. It really isn't that bad IF you know how to read. Knowing how to read is NOT as common as you might think. I have had multiple friends come to me and want to "get off evil windows 11 and go to arch". Every single time they fuck something up just because they simply don't read. Arch isn't that big of a skill requirement if you know what you're doing in general but if you have zero ability to comprehend information it isn't for you.

[@breddie_is_rookie]

This video's narration is kinda similar to Mental Outlaw's, with innumerous 4chan-tier meme references and doing something technical that is related to the subject. Next, we will be expecting a cooking video on how to make some Midwestern stew or something

[@EricMurphyxyz]

Lifting videos coming soon

[@breddie_is_rookie]

@@EricMurphyxyz We are awaiting for them

[@BB_Sebring]

Mental Outlaw is much more critical of normies and Windows Users. Eric Murphy is much more understanding of the limitations of Linux

[@Yusha7135]

Mental Outlaw pretends to be more knowledgeable than he actually is. Much prefer Eric's videos.

[@breddie_is_rookie]

@@Yusha7135 well, agreed. The world is your oyster, I am just floating in it

[@owletkami8018]

You don't need to use arch to learn all this stuff. Spending enough time doing projects in any system will force most users who are curious to learn these technologies

[@XatxiFly]

Probably true, but it sounds like an Arch install might be an efficient way to do a lot of it all at once, which personally I would prefer

[@semyonboyk0]

Maybe it's because I started my Linux journey from Gentoo, but I find installing Arch very simple, given how amazing their Wiki is. The installation process itself teaches you more than some Linux courses :D

[@EricMurphyxyz]

I agree, the Arch Wiki is an incredible resource

[@no_name4796]

If you have an entire day to install arch is definitly worth it

[@alexal4]

Indeed, it is very simple and once you did it once it takes just few minutes to install it. I made a simple script witch install arch with dwm from the scratch automatically and it takes about 6 minutes to complete all installations.

[@jabahunter]

The guy that just did the "install gentoo" and then lived

[@folksurvival]

@@no_name4796 It only takes about an hour.

[@seanzhang3873]

But the thing is not everyone has unlimited amount of time install it manually. Some people might of just need it up and running asap.

[@besnikrrustemi]

The main reason i use arch btw, is because the first time i tried it / installed it, i noticed how blazing fast my haswell laptops did run compared to distributions like ubuntu, mint, elementary etc etc. Now i use window manager (qtile) with arch and basically my complete setup with all the software that i use gives me an install below 700 packages in total (compared to 2000+ on other distros). No bloat, customized the way i want to and super efficient and happy with it.

[@xnour2]

To be fair, Debian based distros break packages into significantly smaller chunks compared to Arch and its derivatives.

[@gwgux]

The best thing about doing the manual Arch install multiple times is that as you learn, you can start scripting it and automate how you're going to install your base system every time. This is incredibly handy if you're building different types of systems on Arch (desktops, servers, etc.) and want to ensure you start at a consistent base for all of them so you'll always know how all your systems will work every time you build them.

[@AnalyticMinded]

Here's a few other reasons not to use Manjaro: the constant f ups, the incremental bloating, inconsistent updates (the latest update came over a month after the last one and it's huge, so expect about 15 minutes of downloading and updating), not being able to update an outdated program from their repositories for weeks, etc. This week I'm saying goodbye to Manjaro on my laptop after almost 3 years. Good thing I had my desktop PC with Arch to keep me sane. A reason not to use EOS: if you want your system setup exactly to your specifications, be prepared to uninstall a lot of unwanted/unneeded pre-packaged programs, in which case just spend the time to install vanilla Arch. Otherwise, it's a fine distro. Lastly, yes, it's true: installing Arch is not that difficult. The first time is a little bit nerve-wracking, but it's nothing out of this world. If anything, it's just time-consuming. And you do learn some things about Linux while prepping the install. So, don't follow instructions mindlessly: make the effort to learn something about your system.

[@EricMurphyxyz]

I used Manjaro for a few months in the past and I had the same issues. I've been meaning to make a video ranting about Manjaro for a while, but I haven't gotten around to it yet.

[@Proferk]

@@EricMurphyxyz good video idea

[@EricMurphyxyz]

@@Proferk Coming this week

[@dhupee]

Use EOS for half a year now after moving from fedora I would say it's great for someone who wants benefits of Arch, already comfortable with command line or basic troubleshooting of Linux, but don't really want spend time manually installing arch nor have specific need like manually install Arch Also been using EOS for making 'kickstart' script in VM, quite useful compare to if install Arch, the stuff would take more time Also, I think most of the prepackaged stuff can be unchecked on the calamares before the install That's my opinion, thx

[@Ra-Ra_Ra-Ra_Ra-Ra]

What if I'm been hate weird vanilla Arch, that's be means, i hate myself too?

[@Seacat17]

Nah, I just want to use my system and customize it if I want to...

[@lauchaufraedern]

Installing Arch on my own was a great introduction into Arch. I learned how to do some stuff like partitioning, using pacman, installing GRUB etc. throughout the installation which was helpful later. And the wiki is so well, that it shouldn't be that hard to install it manually.

[@weirdo3116]

did you use the wiki? cause it's easy to follow in terms of just copy pasting stuff. but i have no idea what's going on lmao.

[@SubaruPickle]

@@weirdo3116 i used wiki the first time i tried to install, but there was a lot of command that arch didn't recognize, command that were working on tutorial , video etc... the script solved that issue.

[@scg02]

idc im still gonna use archinstall

[@BenjaminAlternate]

B A S E D (same btw, i can learn the ins and outs of computers other ways. I jsut want a nice distro that i can program on tbh)

[@nagatouzumaki99]

lol. based

[@LordDSP3]

I tried doing that now my laptop is fucked, I'll need to do it over

[@mopugnothee]

If you're new to linux installing a derived distro can help to have an idea on which packages to install (endeavouros install is really good for that) and if you're new to the distro, it permits to see the bigger picture of it. archinstall script is just a layer above the step by step installation guide provided by archlinux, after that you have to do everything by yourself and its amazing

[@rotteegher39]

> I remember using archinstall to install archlinux because I was lazy. > Few weeks later I got a broken system and didn't know how to fix. > Eventually reinstalled everything the right way... > Understood how stupid I was and that I could even easily fix my previous problem > Installed archlinux the third time on old mac book air 2017 > Currently learning to how to do installing Gentoo with dualboot the right way because I learned from my mistakes. > I use Arch btw

[@UnknownVans]

i feel like the "right" way to go about it is to start off with like Mint or Ubuntu (I don't like Ubuntu as much, but it's a decent place to start). Personally, that's where I started and using those gave me a way to start off and learn the operating system and I guess ease myself into it. The elitism that comes with Arch Linux and the stories about how difficult it is and how often it breaks scared me away for a couple years, but after trying it out (yes, I used arch install), I had no issues at all myself. By the way, I'm not saying "you're wrong" or anything like that, this is just my personal experience and I really feel like rather than manually installing arch being the so-called "tutorial", that should go to using more user-friendly or "starter" linux systems such as the ones I previously mentioned, because those can get you familiar with things like pulseaudio, customizing your desktop, whatever you want to learn and do to get familiar, and from there, when you go into arch install you can say "oh, yeah, I had no issues with grub and I liked that one just fine, and KDE Plasma (or Gnome or whatever) was nice, I'll use that. And I'll need pulseaudio so I can use my headphones" etc etc and from there it's just about learning YAY instead of like apt.

[@jabahunter]

This guy is making me uninstall Arch and reinstall it without archinstall

[@PhthaloJohnson]

I'm not really sure what the script does to make things that much easier, it just gives you the steps you need to take and the options you have. The wiki will tell you to do exactly what the installer does, basically. The difference is that you are guided along the way and given sane defaults, which is nice for a beginner, probably also nice to get it working fast.

[@nhefner]

I used debian and fedora based distros for many years when i first got into linux. I just recently decided to switch to Arch and I used the install script. I went the minimal install route and installed my own display manager, window manager, etc. I found the script a great middle ground for someone like me who knows a good amount about linux and just wants to get an Arch install up and running. I went through probably a dozen iterations in VMs before finalizing a setup I was happy with and I would definitely recommend doing those VM test runs before performing the final install.

[@nostalgianinja]

There's some credence to this: Learning to install Arch manually allows you to understand your system a little better and know what to do in order to automate it. A customized ArchInstall script after creating your own is fun to tinker with. Especially once you know your configuration you could automate the whole installation process and not have to bother with the manual installation process. That being said, I find it better as a tool to mess with instead of something to rely upon at first glance. Personally, to each their own. ArchInstall has its uses, but would definitely recommend people to start out by manually installing a couple of times on a VM, before moving to hardware. I *do* use ArchInstall for when I can't be assed, but I do know the manual process pretty well enough to finish an install within 10 minutes.

[@dm8579]

The Wiki is super easy to follow, but it also isn't explaining much about what is happening, so people with no previous experience aren't really learning much anyway, they just copy the commands as they see them. At the end of the day it didn't really matter if they used a script or installed it manually. I say you learn more by actually using Arch than fumble with the installation.

[@weirdo3116]

you hit the nail on the head with that last part. I went to the wiki to see how easy it was and I was surprised that it was almost the opposite of what this guy said. Sure it's easy in terms of all I need to do is copy paste commands. But I have NO idea what's going on. at this point I'd rather just use the Archinstall script and get to using arch. way easier to learn that way then what every the wiki is saying.

[@roxsonixx]

While I understand the value in following the wiki and installing manually, if you just want to compute on Arch I don't see why the script matters. Why do you care how another Arch user installed Arch?

[@helgi2925]

they are crazy :D

[@samyt681]

arch elitists and gatekeeping

[@chickenbobbobba]

@@samyt681 everyone seems to forget that archinstall stores user and some disk encryption passwords in plaintext. its worth just spending the extra half an hour to an hour to do it the traditional way, even for that peace of mind

[@jackelofnar]

I think your wrong especially about endeavour. New arch users generally need a community to help them once they hit problems but eventually they will migrate to pure arch.

[@madthumbs1564]

They need to learn how to use a search engine, chatgpt, wikis, instructions etc.

[@WinterHawke]

I went from from Fedora > Endeavor > ArchInstall. I like arch but don't really want to do all the tedious install stuff manually. The only reason I switched to Arch is because I wanted to run a WM that Endeavor didn't have a flavor for and it was eaisier to start from a clean slate. The install process isn't very much like using your system day-to-day anyway. Most of the things you do, you'll never do again or do very rarely. The part I cared about was setting up my WM. If you just want to use Arch you can 100% run Endeavor and move to Arch if and when you want too.

[@YrmiZ]

Been installing manually many times, but I love how fast this scripts does basic install.

[@GHNeko]

I used Arch Install specifically to make the process easier, but I did so with the understanding that I would have to learn a lot more on my own after I got the install done. This was also testing out Nobara and realizing that I really really wanted rolling updates/releases instead of stable/LTS stuff because I was already in the mindset of fixing everything myself as I was cutting Windows cold turkey and going perma linux on my desktop.

[@bobpeters61]

Besides, the archinstall script asked for information I still didn't know even after having gotten the manual install process down to inner-child's play. I still had to research and know it was Pipewire, versus Pulse-Audio for example. You really expect someone freshly enraged at Windows to know that stuff?

[@creepergd4884]

For me I have installed it both ways, and I enjoy arch install for the easily replicable systems as well as it automatically making scripts for things that you would otherwise have to write yourself. For me, I will use the xorg profile so that it installs just a base system with xorg and nvidia drivers and then I build the system from there.

[@IsntGwen]

I always skip a tutorial

[@dstm45]

People should stop with i gotta suffer mentality just use arch however you like

[@IsaacMcMillan-u7i]

I think the best way to install arch is to put on mutahar's video and put up the wiki in another tab and go to town. From my experience the Wiki is really hard to understand in some places, and having a video to clear things up is nice. The bootloader part got me a few days ago since the wiki was confusing in its wording.

[@chickenbobbobba]

agreed. i had to reinstall grub because i accidentally put it on nvme0n1p1 rather than nvme0n1, which is an easy mistake to make

[@sindurwavesismaturf]

I took more time assembling my pc on a Sunday evening than anticipated and therefore did not have a lot of time to install Arch the correct way as I needed this PC for work the following day. Archinstall was very useful in this regard. Even though the OS was not setup the way I wanted, I could at least use my IDE on the following morning and then spend the evening setting it up properly

[@autovozo5725]

I will defend Endeavour OS till my last breath

[@souravsingh768]

Can we create a script to install it ?

[@alexal4]

Never say never...

[@stugeh]

Yup. a few years back i installed manjaro and that was a complete cluster fuck, much later found endeavour os and its been absolutely perfect and the best linux experience ive had. Since installing endeavour os ive also installed vanilla arch in a vm and didnt find i really learned much that i didnt already know or couldnt figure out if a similar problem arose on my endeavour install. If you've ever dual booted and ran a system with multiple drives you already know about managing partitions, file systems, mounting drives etc.. Copying the command from arch wiki instead of doing that in a gui doesn't make much of a difference learning wise, youre still going to be reading the same article. I found that moving from a DE to standalone WMs was a much larger leap in learning how my system works than simply installing arch. Idk, seems like a bit of a strange argument to make, noone installs arch or a closely related distro without already knowing before hand there will be more tinkering than on something like ubuntu regardless of if it comes with a calamares installer.

[@folksurvival]

A wasted life spent defending a Linux distro fork.

[@fabianmuhlberger6153]

This is a bit like beginning to learn how to code in C vs. python. While python has a low entry with a lot of tools that help you get started easily. Programming in C on the other hand would usually have some prerequisites, having an IDE or installing the compiler yourself. If you choose to DIY, you are confronted with a lot of things at once, making it very hard at the beginning with the need of research. And therefore learning ABOUT programming and not how to program. At least, this was the rabbit hole I entered when I started learning to program. Best

[@PhthaloJohnson]

This is not a fair analogy at all. Getting started in C might actually be easier, because getting a language server in VS Code, Vim or Emacs is the same process for both of them. Most linux distros come with both the C and python compiler engines out of the box. I would argue both python and C have their unique newbie gotchas. My point is that getting started with either is just as easy. Obviously, python is much easier to use. On the other hand, using the Arch installer and the manual installation will both create an Arch linux environment. The difference is that the installer will guide you along the way with some sane defaults, while the manual installation will not. There is no practical benefit for most people not to use the installer. Most people need the internet, they need audio and they need a gui; it just so happens that the installer gives them sane choices for all of those. Even if you want a manual install for learning, it might be a good idea to follow the installer options as a guide and install the packages manually.

The thing about Arch is that it is collectively (maybe subconsciously) designed in a way that you must know the decisions you take for installing the systems. Once you use an installer, it takes decisions for you for the sake of practicality. And that not-knowing-what-was-decided comes back to bite you, so you will be greatly harmed for trying to save some minutes from the manual steps. Arch is a meta-distribution, it is really the wiki and repositories. That's why each Arch installation is practically a different distribution. That makes all the difference and explains why using uniform installers does not match using Arch the manual way.

[@george1717]

I personally like the 'do it yourself' of Arch for everything except disk management. I used archinstall for that, but set up everything else by hand, which was very rewarding.

[@XatxiFly]

I appreciate this, you're the first person I've seen explicitly recommend a manual install for noobs. I'd been assuming the installer was the better choice if you don't have really specific configuration plans (or an ego need to do it the "cool" way lol) and are happy to accept some tried-and-true defaults to save labor, but thinking of it as a learning process to make things easier later makes a lot of sense and appeals to me. I had been wondering whether the emphasis on how easy or difficult an *install* is might give a skewed impression of what ongoing use, troubleshooting, and maintenance of a system is going to be like, because the challenge of any long-term project for me is almost always more about the retention and upkeep than it is about the upfront research investment (I'm the kind of AuDHD autistic who likes to absorb 200 consecutive hours of information about a topic and then put it down for several months while I cycle through other interests lol). But different strokes, just good to know what kind of install experience you're picking for yourself I guess.

[@dudeguy7988]

I manually installed arch on my desktop a couple times, once vanilla arch, next artix, then when I found out how unreasonably much depended on systemd, I installed arch again. Then on my laptop I used the archinstall script because I was lazy and I wanted btrfs for its backup capabilities and only knew how to setup ext4.

[@taidee]

Warning! Vanilla Arch, especially with a tiling window manager is addictive. After years of this I just can't run other setups.

[@Vran4743]

After breaking it multiple times I think the archinstall stript is a great thing.

[@MrRyuken555]

I have installed Arch the manual way numerous times. But have recently moved to Arcolinux as I already understand Arch really well and Arcolinux just removes the tedium of installing the base Arch and additional configurations. Arcolinux is 98% Arch just with most things already configured and it just works.

[@DDO204]

I understand your view, but I don't need to be painful to install it. You don't need to learn how to fix a thing before it broke, learn when it brake if it breaks. I installed with archinstall a month ago, i had to learn how to fix and understand everything you mentioned as i needed to fix it.

[@Hexspa]

I installed manually yesterday. Without ChatGPT I probably would not have been able to do it in a day. Yes, the wiki has all the info but it’s not exactly easy to follow. It’s stuffed with caveats, colored boxes and links to pages with unique layouts that makes it extra challenging to follow. Frankly, it’s a bit labyrinthine and it seems to be so almost for the sake of it. Criticisms aside, the hardest part is dealing with the vertical learning curve, depending on your previous knowledge. Like, I knew what disk partitions are but got a little stuck when the first sector had to be the default value. Or then they don’t really make clear what the advantages of fdisk vs lsblk are in a way that someone without much experience could understand. Etc. Ok, so I really didn’t put aside the criticisms. Anyway, the installation itself is relatively easy. Figuring out exactly what is actionable in the wiki is virtually Herculean for noobs.

[@voidpointer398]

I don't think it should matter how are you installing an OS, you should be able to perform tasks you need to perform in an efficient way using that OS I have also installed arch using archinstall and it os running just fine I am a software devloper and my experience is great with arch Also with time users can learn arch and how it works along the way

[@gmcenroe]

I've done both, manual install and arcolinux. I get enough work with fixing things and customizing desktops such as my current desktop bspwm. I have also read a lot of the wiki because I have the time to do it, even though I probably use my MacBook Pro M2 Pro as my daily driver. My old PC desktops and laptops get Linux OS, one arch, one linux mint with a variety of desktop environments.

[@spaceghostmiid]

i just did my first arch installation to revive an old laptop and i didn't even know there was an installation script until after i had already done a full manual installation, downloaded all my packages, and set up hyprland.

[@Raftzard]

I understand your point and I agree: as a new comer from linux, I learned I lot installing arch without the install script. Then, the next couple of times I installed, I went on and used it, with the base knowledge I had acquired. Recently I had a problem dualbooting win11 and arch in different ssds, and that knowledge helped me.

[@AnonEMoose-mr8jm]

The final redpill is Linux from Scratch. At the end of the day, do you really know how often your packages are updated? How big is the team that maintains your packages? That's the biggest reason I like Guix. It allows you to be flexible with your system but gives the user a great deal of power. Nix started it all with declarative configs and reproducible builds. Guix took it a step further by using a real programming langauge instead of a DSL. Time will show that it will make a very big difference.

[@airwolf1337]

I just installed Arch by hand (as you suggested), just to find out, that my Lenovo T500 uses BIOS / MBR, and i made GPT partitions! As i wanted to install GRUB, grub told me it wont install because of GPT. So i can not boot my Arch install and have to it all over again! Welcome to Linux! xD

[@airwolf1337]

4h later, i managed to boot Arch (yaaaay) and now im connected to my wifi, but i dont get an ip from the router. bad wpa_supplicant!

[@eclipsos8187]

I learned that it matters if your in the user or root when you download something. Dont download programs within the download file while in root permissions. It screws up systems that try to refrence that program and makes system confused.

[@MrUploader14]

I disagree, installing Arch Linux manually doesn't really teach you anything except how to copy and paste commands. Mostly due to the Arch installation guide assuming you know all the basic concepts of an OS installation. if you actually want to learn something install Gentoo as that installation guide is far superior. And even then it really doesn't teach out much outside if file structures, config files, and package installation. The best way to learn about Linux is to just use it, come across problems and try to fix them. And the Arch community needs to be more welcoming everyone starts from somewhere, if your going to link them to the arch wiki link them to the page that may be the solution or at least help them find the solution to their problem.

[@marcosramirez385]

I've gone through a few rounds of installing Arch the manual way that I learned to write a script for the most basic setup and just install what I want later. Sometimes I'll just install the base and just use the TTY with CMD Line apps or TUI. Browse the web with elinks or watch a video with mpv not really issue.

[@xWatexx]

After doing LFS, I will absolutely use pacstrap at the very least. Also, it was definitely super easy and quick to install compared to LFS. Feels like a breath of fresh air.

[@commanderlars]

The amount of people who misunderstood this video is literally baffling to me. The whole point is that "if you need an easy mode, arch as a whole is just not for you" Insisting upon using arch when you KNOW it's not for you is like eating soup with a fork... you can, but why? Installation is literally the entry point into the whole experience. If you don't like that, you won't like the system. It's not gatekeeping, for fucks sake.

[@TheLegitAlpha]

Remember that Debian was notoriously hard to install once. The thing with archinstall is you still need to configure the thing correctly.

[@AbdulRafay-vi6hz]

okay, here is the thing, You should Install arch linux using the command line, in this way, you will learn a lot, I have install arch Linux using command line like 2 to 3 times only, I know what is happening under the hood, but now, I don't have time to install arch Linux using command line, so I am glad they made a short arch script that would get you a simple clean server or a window manager, I am using Arch linux with Awesome Window Manager years and I love it, it make life, easy.

[@randospawn7495]

Nah bro, I already understood this was a manual thing. But I don't want to waste time installing manually when I could just easily setup and build the fun bits from there.

[@andrespalma.6364]

I used to be scared of installing Arch manually and stickt with the archinstall script, which was annoying bc sometimes it could randomly break and not even understand why (literally the arch install script is a 50 50 roulette). After i decided to actually learn how to do it manually it didnt break even once and it ran very smoothly

[@gamer8622]

This is the most "well actually 🤓☝️" type of video ever. The VAST majority of ppl dont even want to open terminal, let alone fuck around on a wiki page for hours learning the "manual approach" to install arch. Linux in general has got to get more accessible to noob users who just want to run their desktop and go. Being a nerdy gatekeeper and replying RTFM or telling ppl to go out and learn themselves when you could easily answer a question or help someone out is why linux is still only 4% of users. Arch is the most popular distro there is and it needs to be more user friendly for every skill level. The installer works fine and is very easy to use.

[@usellstech-ip2sg]

Arch does not need to get easier, and the majority of Linux distros you will find are user friendly. The video may come off a bit rude but the point stands that you will have a greater understanding of your system, which is good for when something breaks. Good day and happy computing!

[@usellstech-ip2sg]

And I don't use arch (btw)

[@BWGPEI]

Haven't tried this yet, but you deserve credit for getting that job done. You may have convinced me to try it, so Thank You!

[@FurqanHun]

I shifted to fedora around 1-2months ago, and installed arch using archinstall on a vm to test arch. I was actually going to do it manually and even did till the partition and then was like its gonna take longer than i expected and formatted the disk and used archinstall, in my defense i installed arch just to test arch and keep something in backup if fedora goes bye bye. I might install it manually in future just for the sake of installing arch but rn im fine, i alr know a bunch of stuff as i had to troubleshoot sometimes on fedora (though i had way less problems than others) and also i just watch people install arch and see random videos just incase i might face something in future💀

[@ForexStoryteller]

I use arch btw.... As long as you understand the base of the system, more or less starting with the package management, you can make any distro any way you like, arch is just custom from scratch. I did it the hard way 🤷🏻‍♂️ and it took an entire day, but its what I want. I can see both sides of the arguments where not one answer is always going to be right, because hardware and kernals and so on are different, but .. I'd also argue that to start, it would be smarter to use the script, because you're still going to get plenty of trial and error with the rest, the script just gets you started. Still no GUI, just a user login ttyl terminal 🤷🏻‍♂️ so why gatekeep?

[@malibucastle]

I agree 100% … I decided to jump into Linux knowing nothing about it. After a couple videos searches I decided to install Arch Linux using Archinstall. After using it daily for about a month I wiped my ssd and installed it manually. Learned more about Arch during the manual install than I did in a single month of daily use.

[@AgentBurgers]

I wonder what your thoughts on ZorinOS

[@mpx41]

You are really overselling the importance of disk partitioning and ability to run sudo pacman -S gnome. And googling errors with arch is still a thing. The only difference with ubuntu - instead of a command to run you'll get an action (e.g. restart you bluetooth service) which you can also google and in most of the cases the first link would be the arch wiki where you can find the exact commands to run. In reality the only skill you need to start using more or less any distro is the ability to read terminal output and the docs.

[@k.b.tidwell]

You know the old saying, "Pick your battles". And better yet, "Pick a hill to die on". Having installed pure Arch a handful of times, meaning once, and Arch derivatives many, many times, I'd say this discussion is like that. You need to look at your life and decide if the glory(?) of running Arch successfully is worth the vaporized time that will be required to master what has to be mastered...or if you have Bigger Things that take precedence. I had a really good experience with Garuda, but I'm not running it because it coddled me so that when I had to build programs, I just didn't care anymore, got frustrated, and went to something else. I get exactly what you're saying, unfortunately I'm not special enough yet to enjoy self-flagellation. That's not sarcasm. I simply have work I need to get done instead of spending a lot of time on system creation. One day when I'm rich and can spend a lot of my time manipulating time and space, I'll go back and enjoy Arch the way it was forged in the deepest levels of software comfort Hell to be. With deb-based systems, you're coddled up front, and then kind of coddled later too. Arch-based derivatives coddle you up front, then throw thine flailing mind upon the rack later. Pure Arch starts with a thump to the nads, and then progresses from there. That's what this video is saying in a nutshell.

[@MiteBlueRuby]

i heard how hard it was to install normally but archinstall wouldnt work properly so i installed manually and it is actually easier than it seems

[@danielton9577]

I've installed Arch both ways, and have used Linux for 20 years, and I think archinstall is a good thing. Granted, it installs a very minimal version of whatever desktop you desktop, so you'll still have to tinker with it after installation, and enable things like printing and Bluetooth, but it's a very useful tool to have if you need to reinstall for whatever reason. Arch is pretty much your only option if you want to use brand-new hardware or you don't want any distro-specific customizations to your software, or if you want to run obscure window managers or desktops. Gatekeeping is not cool.

[@Duckleet-Website]

I used arch for years. I don’t remember the last time I fixed anything do you? I tend to set a system and not fuck around with it

[@callmeplayer8185]

Arch linux is my 2nd distro.(From fedora) And I did it manually and this is so true. I learned a lot more from booting it manually and. I managed to somehow forget to install grub bootloader

[@chaos523]

Just installed the arch using the manual way and oh man, it was amazing! I think using Arch kinda gives you a mindset of independence. I'm getting more and more fond of this distro because you have, and dare I say, the ultimate freedom to everything! Try it out yourself before judging it!

[@supertigerroadtrip5193]

Garuda already comes with most modifications I apply anyway. Also comes with quality of life stuff. To me, manually installing Arch is a waste of time for me, if in basically going to build Garuda Linux anyway.

[@woyttas]

Funny how I went from Endeavor / Manjaro to a manual Arch install because I couldn't get all my hardware to work without breaking the OS. Sure it took longer, but I got everything to function properly even better than it did under Windows. It was a few years ago though. Nowadays I use a custom Windows 10 cause a few games I enjoy don't work under Linux. I might give it another try though, just for fun.

[@adambester3673]

I'll stick with Garuda for now thanks, but i will keep your words in mind. I am pretty new to Linux and would have chosen something other than an arch based distro to start out with but debian, ubuntu and fedora based distros just do not work with my hardware because of a really dumb quirk of my motherboard.

[@ulawan5]

I actually support the "installation as familiarization" approach tbh I'll probably never try Arch, but in modding my DSi, I've been left with a lot of confusion about functionality and where to find certain settings. When things ALWAYS come pre-packaged to do them the "easy" way, it's got tradeoffs like with food, you trade convenience for wholesomeness a lot of the time sometimes the best route is to grow your own produce or bake your own bread, and if you want it bad enough, you'll make it to your own tastes And a beauty of the world I think is the infinite variability of all the humans living here!

[@cenewton3221]

There is nothing wrong with using an Arch-based distro. With pacman & AUR it's a great way to have access to the vast majority of apps. Many who want a rolling release will also find Arch appealing. From my experience the best two are Arco & Garuda as they offer additional utilities for maintaining the rolling releases over time, in addition to the fact they have multiple versions of their distro. Yes there is a lot to be learned from doing a vanilla/from scratch Arch install but having done that several times over the years, it's nice to have pre-built distros that save a bunch of time in getting a system up & running. Not all of us are "by the way" types of people. Some of us just want to get to work quickly & be able to do updates without borking our system.

[@zekiz774]

I daily drive Arch for 4-5 years now and never installed it manually. I still love it and its still my favorite distro... at least for now. Maybe ill switch to Nixos soon.

[@Max-kd6vz]

First time linux user. Decided to install Arch cause our IT guy at work uses it and is a really cool and knowledgable dude. Used archinstall script, ran into issues, spent a couple hours diagnosing the issues, fixed them all, now I have a fully functional linux laptop. Would manually installing be better? definitely. But it would be slower and I was trying to get it installed in a limited amount of time.

[@Beersandsmokes]

Setting up encryption manually on two drives is such a pain, that’s the reason I use the archinstaller

[@fadedtimes]

I tried manually, and it reminded me of installing redhat back in the 90's. I then tried the script and crashed it. I managed to fix the install script by wiping all my partitions using fdisk. Then I installed it 4 times until I finally got it to work how I wanted. The install wouldnt work on wifi, then had a hard time getting ethernet working post install, then didn't have a sudo user, and finally the 4th try I got it, only to have my bios complain I was in legacy boot mode and then had to switch to uefi. Was a fun few hours

[@media-magic]

Remember one thing: the more complicated the installation process is......THE HIGHER THE PRESSURE OF EXPECTATION. I have used Arch both installed the complicated way and by the script called archinstall (made by Arch Linux) and the performance power is exactly the same...

[@eekee6034]

I had high expectations to start with, and was disappointed by every "simple" Linux installer I encountered. :) But I specifically expected to be able to use the tools I was familiar with, and I found it very rare for an installer to be clear on how to use those tools in cooperation with the installer.

[@Fizcakesprite]

In my opinion, most of this info can be learned without even using Arch. If you can say yourself though that you have understood, and read the manual, and can use it to your advantage without troubleshooting, then you are an Arch User

[@user-kc4dj8mb6m]

After abandoning the buggy archinstall scripts, finally I learned installing arch is that simple. The thing that really matter is just to mount the root directory onto /mnt of the usb driver's system and try to pacstrap on that directory. Then setup the boot option maybe if you want a dual boot. And you are done.

[@NithinSunnyKrishna]

When I installed Arch for first time using auto install, it bricked my personal usb. 🤣 The Diy mentality thing you mentioned is right I learned a lot and had a fun of troubleshooting where only one installation video didnt worked for me😅

[@dacueba-games]

I'm not special. What distro will be fun?

[@kobeneilson6717]

I feel like I did something wrong, I installed arch via manual method the first time, however I didn’t feel like I understood Linux any more. I think I should just install arch a few times to practice

[@nimrod7075]

Not using archinstall to learn how to do it. I cant even install arch with archinstall because i want to dualboot it from my macbook and the manual disk configuration confuses me. An everytime i make an error i often cant cancel so i have to reboot. There are a ton of guides for archinstall, but they all skip the manual disk configuration and just pick the swipe all option

[@oglothenerd]

I personally prefer EndeavourOS, because of the update notification thing.

[@melanovapedia7924]

I couldn't agree more. I use Arch many years and still reinstall Arch with *_"old ways or Arch wiki strong recommended it"_* , it's so easy tho.

[@amdkits]

for me i dont have access to ethernet cable so after installing my pc went into tty mode and cant do anything from there

[@theonewhocodesalot9101]

I just would like to thank you because of this video i got the motivation to install arch linux at first it looked very difficult but when i followed a a persons arch install guide on youtube i finally found it to be easy and decided to install it on a virtual machine i had a basic arch install and decided to get a de or wm so i got dwm and it did not work so i reinstalled it and found the problem and i got i3 working even though it isn't much it feels like a great achievement and now i can install arch linux confidently thank you so much for inspiring me to one day have a great arch linux setup

[@BroMomento69]

I’m installing arch rn but I have to keep inputting nomodeset to avoid black screens on boot, and after I installed sddm and plasma the boot hangs. It sucks to get past an error and then suddenly run into a new issue but I guess that’s part of the process

[@albatross7]

You do realise that this isn’t 1960s anymore, right? Technology improves for a reason. If it were for command line basement dwellers put in charge tech projects, we wouldn’t have smartphones, digital video, GUI softwares in the first place. All you’ll be doing is fixing your operating system on command line all the time. Thank god you people can only make noise within your own bubble with zero impact outside of it.

[@dreamhollow]

Installing Arch Linux manually is really, really good for learning how Linux actually works. Using the install script really defeats the whole point of installing Arch; it's much more about the journey than the destination.

[@paullee107]

I do like archfi - even tho it's a bit long in the tooth - but agree that users should have a strong understanding of the cli install process before using any script to deploy a system.

[@PunkrockNoir-ss2pq]

The hardest part about installing arch is remembering to install dhcpcd and iwd

[@CarlWilde-v6d]

John le Carré’s Arch based spy novel - “Tinker tinker tinker tinker”

[@SerdceDanko]

If you manually write commands from Arch wiki to install it - it doesn't give you extra knowledge nor makes you smarter. So script is great cause it saves a lot of time.

[@generimposter]

You've given me some motivation to try to install Arch Linux manually (on a virtual machine)