Nice, man. I can still remember my install on my daily driver before I even tried. I kinda looked online to make sure I didn't miss anything, and because of that, I even removed my second NVMe. But the install itself was not the issue - it was the desktop part, specifically XFCE. I was so used to XFCE that I overlooked KDE, and that was a mistake. I did manage to fix most of it, but after one night, I was sleepy and somehow one update broke my backup system and my Arch install after that. And because I had locked everything, it was a damn hell. I now just use Fedora - I don't have time for Arch issues at the moment
Lol well done, got further than I did! If you want specifically arch for practical reasons not just the intimacy of knowing all the parts, I've had a lot of luck with the archinstall script. All the arch with none of the install!
you dont need grub on uefi systems to launch linux, with arch you can add an entry to the motherboard nvram to boot using efistub, that way you are using the kernel itself as the efi boot file, using the uefi itself as the only bootloader is possible and i love that because i dont have to deal with grub
i think doing this has just shown you that it isnt straight forward, i encourage you to tinker around a bit more with partitioning and with how pacman works you didnt fucked up the install, at the final you had arch actually installed correctly, you just hadnt networking enabled, probably because there was no dhcp server so your device didnt got an ip address and a dns server to query to and that is the reason why installing xorg-server failed and the reason why chroot /mnt wasnt working is because it shouldnt, that was something done for the instalation, now that you had it installed, you didnt had to do chroot tldr; you were pretty close, just missing networking and a bit of knowledge about partitioning, chroot and confusing some files with directories (doing cat to directories or creating directories where there should be a file) so i think the next attempt if you want you will get it right, because you were really close, hope this helps, good video, showing the reality to specially newcomers who think from what others say that it is not hard because "it is just reading and following the wiki"
Nice, man. I can still remember my install on my daily driver before I even tried. I kinda looked online to make sure I didn't miss anything, and because of that, I even removed my second NVMe. But the install itself was not the issue - it was the desktop part, specifically XFCE. I was so used to XFCE that I overlooked KDE, and that was a mistake. I did manage to fix most of it, but after one night, I was sleepy and somehow one update broke my backup system and my Arch install after that. And because I had locked everything, it was a damn hell. I now just use Fedora - I don't have time for Arch issues at the moment
I've used both Gnome and KDE extensively, and I quite like them both, I've also dabbled with LXDE and its pretty great as well
Lol well done, got further than I did! If you want specifically arch for practical reasons not just the intimacy of knowing all the parts, I've had a lot of luck with the archinstall script. All the arch with none of the install!
Knowing all the parts makes it quite a bit more practical
One day I'll get there, I want to learn
you could always use the `archinstall` command to install arch - it might be a little easier for you.
I subscribe for the white friend (toilet bowl) in the background
Hell Yeah Brother
good job, tyasg!
Thank You!
cool
Ah so a normal install lol
not bad for a first attempt. i still remember mine. i installed everything perfectly but forgot grub so i couldn't even do anything
you dont need grub on uefi systems to launch linux, with arch you can add an entry to the motherboard nvram to boot using efistub, that way you are using the kernel itself as the efi boot file, using the uefi itself as the only bootloader is possible and i love that because i dont have to deal with grub
Thanks!
what dark magic is this
@@H3cJP everything is optional in arch😭
i think doing this has just shown you that it isnt straight forward, i encourage you to tinker around a bit more with partitioning and with how pacman works
you didnt fucked up the install, at the final you had arch actually installed correctly, you just hadnt networking enabled, probably because there was no dhcp server so your device didnt got an ip address and a dns server to query to and that is the reason why installing xorg-server failed
and the reason why chroot /mnt wasnt working is because it shouldnt, that was something done for the instalation, now that you had it installed, you didnt had to do chroot
tldr; you were pretty close, just missing networking and a bit of knowledge about partitioning, chroot and confusing some files with directories (doing cat to directories or creating directories where there should be a file)
so i think the next attempt if you want you will get it right, because you were really close, hope this helps, good video, showing the reality to specially newcomers who think from what others say that it is not hard because "it is just reading and following the wiki"
Thank you! Yeah I have learned a lot from this.
DID I JUST WATCH YOU DELETE YOUR WINDOWS INSTALL NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO (you are hurting me severely)
Windows Sux lol
hey wait a minute
*i recognize you*
do you now?