My First Arch Linux Installation - Drunk Edition - Chris Titus Tech
video description
Date: 2022-03-20
Related videos
Comments and reviews: 10
Gerd
Just in case: Xorg is what's called a display server. It handles drawing graphics on your screen and it handles your input devices so that you can interact with those graphics. Your graphical applications, such as the window manager for example just -connect- to the display server to tell it where things should be and what they should look like, and the display server draws them on your screen. That is of course a somewhat simplified explanation, since especially Xorg does quite a few things more. But that's basically why you need it.
Wayland is the hot new thing that's supposed to replace some functionality of Xorg, mainly because Xorg, or rather the -X Window System- will turn 35 next year. It's kind of old, kind of slow, kind of messy, tries to do too many things, some of which most people don't use, and it does them in a sometimes a bit convoluted manner, which is maybe a bit un-unixy. (remember: do one thing, and do it well). Wayland, although often referred to as such is not a display server itself, but a protocol. The actual display server that uses this protocol is called Weston. But Wayland and Weston to this day have not reached a point where they can replace Xorg, mainly because many applications still don't support them directly. Often times when you run Wayland/Weston, you also run Xorg to be able to display your applications. This is possible because they have made Xorg capable of talking to Wayland, and that is called XWayland. So, when you are in your Weston based Desktop environment, that sits on top of Wayland, and launch an Xorg-based application, Weston will call XWayland to run it. Confused yet?
reply
Just in case: Xorg is what's called a display server. It handles drawing graphics on your screen and it handles your input devices so that you can interact with those graphics. Your graphical applications, such as the window manager for example just -connect- to the display server to tell it where things should be and what they should look like, and the display server draws them on your screen. That is of course a somewhat simplified explanation, since especially Xorg does quite a few things more. But that's basically why you need it.
Wayland is the hot new thing that's supposed to replace some functionality of Xorg, mainly because Xorg, or rather the -X Window System- will turn 35 next year. It's kind of old, kind of slow, kind of messy, tries to do too many things, some of which most people don't use, and it does them in a sometimes a bit convoluted manner, which is maybe a bit un-unixy. (remember: do one thing, and do it well). Wayland, although often referred to as such is not a display server itself, but a protocol. The actual display server that uses this protocol is called Weston. But Wayland and Weston to this day have not reached a point where they can replace Xorg, mainly because many applications still don't support them directly. Often times when you run Wayland/Weston, you also run Xorg to be able to display your applications. This is possible because they have made Xorg capable of talking to Wayland, and that is called XWayland. So, when you are in your Weston based Desktop environment, that sits on top of Wayland, and launch an Xorg-based application, Weston will call XWayland to run it. Confused yet?
reply
yvrelna
You can run visudo using a different editor by setting your EDITOR environment variable when running it. For example,
# EDITOR=nano visudo
The reason why you usually don't want to just simply use edit /etc/sudoers directly is because visudo does a syntax check of the file before letting you quit editing the file. If you don't have a syntactically valid sudoers file, it won't overwrite the /etc/sudoers file. This is usually important because if you are running as regular user and edits the file using -sudo visudo- and you make a syntax error in /etc/sudoers, you would not be able to rerun -sudo visudo- as sudo won't know the correct permission to apply to your user.
This might not really be that much of a big deal since you are already root and if you are in chroot, you can always just quit the chroot and use the main system to fix permissions on your chroot-ed system.
reply
You can run visudo using a different editor by setting your EDITOR environment variable when running it. For example,
# EDITOR=nano visudo
The reason why you usually don't want to just simply use edit /etc/sudoers directly is because visudo does a syntax check of the file before letting you quit editing the file. If you don't have a syntactically valid sudoers file, it won't overwrite the /etc/sudoers file. This is usually important because if you are running as regular user and edits the file using -sudo visudo- and you make a syntax error in /etc/sudoers, you would not be able to rerun -sudo visudo- as sudo won't know the correct permission to apply to your user.
This might not really be that much of a big deal since you are already root and if you are in chroot, you can always just quit the chroot and use the main system to fix permissions on your chroot-ed system.
reply
Gerd
As for that -wheel- group: Notice the commented out line that starts with %wheel in the sudoers file? Had you just uncommented it, it would have made it so that all users in the -wheel- group have sudo permissions. That's basically what the group does. It's not necessarily called -wheel- on every distribution. On some it might be called sudoers, or even administrators.
You just added your user account specifically, and you were unsure if this is the right way. It probably isn't the recommended way, but it works, and as far as I'm concerned: If it works, it's right. Especially on a system that's effectively only being used by a single person, you really don't need user groups.
reply
As for that -wheel- group: Notice the commented out line that starts with %wheel in the sudoers file? Had you just uncommented it, it would have made it so that all users in the -wheel- group have sudo permissions. That's basically what the group does. It's not necessarily called -wheel- on every distribution. On some it might be called sudoers, or even administrators.
You just added your user account specifically, and you were unsure if this is the right way. It probably isn't the recommended way, but it works, and as far as I'm concerned: If it works, it's right. Especially on a system that's effectively only being used by a single person, you really don't need user groups.
reply
Aitch
First Arch install performed in 20 minutes after a party? Wow. I just did my first yesterday in about 3 hours AND I was sober.
Also, I'm confused. You installed the xfce4 group, which includes xfwm window manager, then installed a different window manager, but configured your system to exec startxfce4 which, unless I'm mistaken, starts the xfwm window manager. Actually, I shouldn't be confused...you were drunk'd after all :-)
reply
First Arch install performed in 20 minutes after a party? Wow. I just did my first yesterday in about 3 hours AND I was sober.
Also, I'm confused. You installed the xfce4 group, which includes xfwm window manager, then installed a different window manager, but configured your system to exec startxfce4 which, unless I'm mistaken, starts the xfwm window manager. Actually, I shouldn't be confused...you were drunk'd after all :-)
reply
MrNihilist74
I installed arch Linux with a zen graphical installer. It was buggy as hell. Maybe because of the install or the choices I made. I have installed ubuntu with gnome, ubuntu studio, Linux mint, and manjaro. They all seemed ok. Installed Debian. Lan would not work. I'm going to stick with Kubuntu with the KDE plasma. For me, it seems to work the best.
reply
I installed arch Linux with a zen graphical installer. It was buggy as hell. Maybe because of the install or the choices I made. I have installed ubuntu with gnome, ubuntu studio, Linux mint, and manjaro. They all seemed ok. Installed Debian. Lan would not work. I'm going to stick with Kubuntu with the KDE plasma. For me, it seems to work the best.
reply
Theodoric
Your video doesn't work sorry bro, this is a bullsht how to! Don't waste your time!!! You left out so many things and you forgot to tell ppl how to save nano? It's like your trying to finish so you can go have another drunk or some sht.
reply
Your video doesn't work sorry bro, this is a bullsht how to! Don't waste your time!!! You left out so many things and you forgot to tell ppl how to save nano? It's like your trying to finish so you can go have another drunk or some sht.
reply
octet33
The X window system is responsible for giving apps a standard way to draw GUIs to the screen, kinda like what early versions of Windows did for DOS. Xorg is simply a popular version of X Window System on Linux.
reply
The X window system is responsible for giving apps a standard way to draw GUIs to the screen, kinda like what early versions of Windows did for DOS. Xorg is simply a popular version of X Window System on Linux.
reply
Peter
Conclusion: you can even install Arch when you are drunk, it has gotten that easy. :p
A nice variation on the -assemble a PC while you are drunk- to show how easy it is.
reply
Conclusion: you can even install Arch when you are drunk, it has gotten that easy. :p
A nice variation on the -assemble a PC while you are drunk- to show how easy it is.
reply
Ashkangames
Normal people when they are drunk: they do something and regret it later
Giga chads when they get drunk: make a linux install toutorial
reply
Normal people when they are drunk: they do something and regret it later
Giga chads when they get drunk: make a linux install toutorial
reply
Jonas
Oh, my god, what coincidence! When I was thinking: -He seems to be drunk-, you tell: -I'm not drunk-, but u r. Everybody see your eyes ;)
reply
Oh, my god, what coincidence! When I was thinking: -He seems to be drunk-, you tell: -I'm not drunk-, but u r. Everybody see your eyes ;)
reply
Add a review, comment
Other channel videos
