Now this is a real guide, you tell what, why and how to do things Not just random youtuber making video to get views I hope you're going to keep making these, I'm new to linux
Hey thanks so much for watching and commenting! I will indeed be making more videos, especially introductions to various topics for anyone new to Linux :)
Thank you for the very good videos, i only installed with the arch install and only used very little, but i changed machines and will soon do it manualy now. Thanks again, will follow to learn more about what i can do with arch.
Awesome, video on what is next when installing Arch. A lot of very good information to continue creating your own system. Anyone brave enough to get in front of a camera and do these videos has my respect. I have some tips about configuring SUDO that can help. First, I want to point out a syntax tip for the /etc/sudoers file. Notice when looking at the sudoers file there was a % in front of wheel. The % indicates the following name is a group. Without the % the name is a user account. Second, making changes to /etc/sudoers has the risk of when the package maintainers make a change to that file it can be replaced when upgrading the package. I have not run Arch to know if there is a warning about hat or not. If there is and you don’t notice you will lose your changes. If you look at the bottom of the sudoers file you will see an include statement to include files in the /etc/sudoers.d directory. SUDO looks for files in this directory and appends them what was in the sudoers file. This directory is not touched by the package managers except to be created on initial install of the SUDO package. To add yourself or a group to the list of sudoers use your favorite editor to create a file in the /etc/sudoers.d directory with a line like that of the entry shown in the video for wheel in the sudoers file. For example (note do not include the quote marks and substitute your user name for user): “user ALL=(ALL) ALL” will give a user named user SUDO privileges requiring a password. You can also use “user ALL=(ALL) NOPASSWD: ALL” to sudo without requiring a password. As I recall the file names can be anything, but I generally have seen them start with a number and include the name being included. For our example the name will be something like: 010-user. One last thing you can remove SUDO status by removing the file or if you want to maybe establish it later just add ~ to the end of the name like 010-user~. When looking at files in /etc/suders.d sudo ignores files that end with ~ or include a period . in them. Sorry about the long length of this message but the more I typed the more it seems that needed to be said.
Hello, thank you so much for commenting! I really appreciate your thorough explanation. There's always more to learn and it's very helpful to have comments like this. For Arch, either editing /etc/sudoers or using a drop-in file in /etc/sudoers.d is viable, according to the wiki; but maybe it is better practice to stick to drop-in files as you've suggested.
NOTE: #!/bin/sh will be necessary to run shell commands from your xprofile. You can add this in as the top line, it is called a "shebang" and it is used to instruct how the file should be parsed. Please bare with me as I get used to recording! If I do forget something while recording I will always make note in the description. Add the following lines to your ~/.xinitrc file for a KDE Plasma installation allowing for use of ~/.xprofile: #!/bin/sh [ -f /etc/xprofile ] && . /etc/xprofile [ -f ~/.xprofile ] && . ~/.xprofile export DESKTOP_SESSION=plasma exec startplasma-x11
wow thank you now i know (at least for the moment lol) how to install software through the back door lol this is actully potentally shorter than apt install yourpackage although im assuming it HAS to be capital s -S is a minor inconvience but ill probably adapt. heres a tip for YOU! run this command sudo -S tldr this is very valuable its man with examples i saw you S vim and i thought S was the command so i was like man S LOL
Most WMs have screen-locking functionality, though I do agree it can be buggier than a dedicated display manager. Thanks for watching and commenting :)
The last topic you address would be worth a separate video. I use DWM and have had trouble getting polkit, the ssh-agent and the like to work. I borrowed commands from people's dotfiles just to realized that they messed up my system. With 'exec dbus-launch --exit-with-session dwm", for example, dunst would not work (I could not even execute a simple notify-send command. My questions boild down to: What belongs into .bashrc, .bash_profile, .profile, .xprofile, .xinitrc and what services must be started for a system to run with startx. Login manager do some work for you, already, right, but that's not what I want.
So installing with yay makes the app files to be in .cache for yay? If i need to change the dwms config file for exemple ill be changing that file in yays cache? I cant find the "instalation" folder anywhere. Just making sure Keep it up, really liking your style of teaching.
I can see the influence from Luke Smith in your layout. I’ve been using LARBS for about a year now and I think I’m going to use these tutorials to rice a new user and learn some more practical skills. Thanks for the tutorials!
Haha for sure, Luke's videos and explanations have always been among the best. Awesome - glad to hear! No problem and thanks for watching and commenting.
I already have arch installed but your video popped up on my recommendations and I figured I’d give it a watch and maybe learn something new. I’m curious why you start KDE through xorg vs letting a display manager like sddm handle that. Is there an advantage to this setup or is it just for simplicity and reducing bloat?
Thanks so much for watching! I do find xorg/xinit to be simpler and easier to configure, but another important reason for me is that it also allows you to boot into a shell rather than a graphical environment, giving you immediate access to the command line before a more intensive program runs. An example of that in practice: if I have a software or hardware failure that is resulting in crashing/freezing once graphics are started, I can look at logs and troubleshoot right after I boot, instead of having to first disable the display manager by booting into the install medium and chrooting in. So in sum, xorg/xinit provides the user more control. However, as with many things, it ultimately comes down to personal preference :^)
@@BreadOnPenguins Ah, makes sense. I see you use a tiling manager so I’m sure it’s also habit. I’ve only used KDE and gnome so I just install the kde/gnome package group and it does all the config for starting GDM/SDDM.
I do not see the url in the description ? I could not see that you had on both sides of yay and it said critical after I pressed enter so I just cleared it and exited. I am no good at night doing this stuff lol Same thing the last three nights I am in bed watching then I get up and try things then the next day I see how easily I messed up lol
Hello, which url are you referring to? If I missed it happy to add Sometimes it takes a few tries to get something working haha, I'm sure you'll eventually get it!
@@BreadOnPenguins LOL at the 9:45 mark um I got it today like I said up to late doing this I was adding cloning into yay on the command line with it lol so dumb.
@@kevinDesRoches-vq1xe Gotcha, glad you figured it out! The url is with the 9:34 timestamp in the description but sadly UA-cam won't allow me to share hyperlinks until the channel is bigger
do you have any advice for switching from one DE to another in a graceful and clean way? say I want to remove KDE and install Gnome, what commands would you run? how would you get rid of all the random extra files laying around that could cause conflicts? Should I just reinstall Arch entirely in this case?
Hello, sure - First of all it is definitely not needed to reinstall Arch. You can use pacman -Rns to remove packages you've installed for KDE - those flags remove system configuration and unneeded dependencies. User configuration won't impact anything, but you can remove it if you choose - it'll be in dotfiles (so in directories like ~/.local and ~/.config). Then install Gnome and switch over your display init files or display manager to use it :-)
@@BreadOnPenguins cool thanks. do you think it would be wise to create a new user, and use the new DE with that user? so its essentially starting from a clean slate (new home folder etc) , and then remove the old user?
While I do believe your videos are a great resource. It is still overwhelming to install vanilla arch. This is why I'm going to stick by my voice to install endeavorOS KDE it's as close to arch that I want to get to.
Hey there, you can log out of your user account with the command "exit" (or you'll also be back at the login screen on a fresh boot); then use your root account to login - username 'root' and whatever password you had set for it on install. From there, you can use pacman to install vi, and use the visudo command :) Hope that helps!
@@BreadOnPenguins Hi again. Thank you for the patience to answer a noob question. I was able to follow your tutorial up almost the very end, but then something happened: I installed SDDM and the Nvidia proprietary drivers and configured Xorg X11 session, then whenever I tried to initialize Plasma, both through SDDM and through "startx", it would just give me a black screen with a cursor, and sometimes not even that. After a full night of tinkering I just figured out I can only start Plasma as root. Any ideas what I might have done wrong? I might be just that I'm dumb, but any hints whatsoever would be much appreciated.
@@ExNihilumHi, no problem. You may have a configuration mistake for your user account's xinitrc (or sddm conf); you can check through Xorg logs and the system journal (journalctl) for errors and see if anything gives a clue. If you're unable to figure out anything from that you can try setting up a brand new user and configuring from scratch - if your root account's configuration is working for getting Plasma to launch, you could copy/crosscheck with that. Good luck!
@@BreadOnPenguins I got it! It was the xinitrc file. Strange though, I wrote that file like 3 or 4 times. I probably messed up a few things during installation, but the point of installing Arch is learning about Linux anyway. Big thanks, I learned a lot from your videos.
Great video + the previous one, but I'll stick to Debian. Arch is just a massive headache, I would run it if I'll were on the latest and the greatest, but I'm not.
KDE is nice, its simple ans easy to use. But it crashes and breaks. That is one downside of KDE that it crashes and breaks or kernel goes into panic and you got to reinstall the entire OS. You try to fix it and fail resulting in nothing more but a force to reinstall the OS Which is why i recommend GNOME to People rather KDE Also if you going to use those custominasations to make the icons look nicer etc make sure that once you reach a big update those are supported because if they aren't this is just asking for Kernel to panic.
i did makepkg -si i got this!! ==> ERROR: You do not have write permission for the directory $BUILDDIR (/home/v/yay). Aborting... [v@v-hppaviliondesktoppc570p0xx yay]$ sudo su [sudo] password for v: [root@v-hppaviliondesktoppc570p0xx yay]# makepkg -si ==> ERROR: Running makepkg as root is not allowed as it can cause permanent, catastrophic damage to your system.
@@BreadOnPenguins i got the same error!!!!! [v@v-hppaviliondesktoppc570p0xx ~]$ cd yay/ [v@v-hppaviliondesktoppc570p0xx yay]$ ls PKGBUILD [v@v-hppaviliondesktoppc570p0xx yay]$ makepkg -si ==> ERROR: You do not have write permission for the directory $BUILDDIR (/home/v/yay). Aborting... [v@v-hppaviliondesktoppc570p0xx yay]$
One of the best explanations on Linux topics for beginners here on yt. Keep up with the great work!
Thank you so much - will do!
Now this is a real guide, you tell what, why and how to do things
Not just random youtuber making video to get views
I hope you're going to keep making these, I'm new to linux
Hey thanks so much for watching and commenting! I will indeed be making more videos, especially introductions to various topics for anyone new to Linux :)
I used Arch for almost 4 years, but now trying to test Ubuntu and Fedora. This video almost made me revert back to Arch again. Loving your channel
Haha fair enough! Thanks so much :)
Going to be jumping into Arch as a lifetime Windows user soon. I'm looking forward to it but also nervous, your videos have been helping a lot
It's awesome that you're making the switch to Linux, good luck! Glad to hear my videos have been helping :-)
Your content is so good, the best explanations on LInux I've seen in the many months I've been watching Linux content. Many thanks!
I'm really glad to hear that! No problem :)
I thought you were supposed to immediately call up all your friends, family, and neighbors and tell them which distro you use.
True, that's the #1 thing to do obviously
I hugely appreciate the time and effort you've put into making these videos! You are awesome!!
Honeslty thank you! Straight to the point and explained everything fairly well
You are very welcome, and thank you for watching!
Thank you for the very good videos, i only installed with the arch install and only used very little, but i changed machines and will soon do it manualy now. Thanks again, will follow to learn more about what i can do with arch.
Awesome, video on what is next when installing Arch. A lot of very good information to continue creating your own system. Anyone brave enough to get in front of a camera and do these videos has my respect. I have some tips about configuring SUDO that can help. First, I want to point out a syntax tip for the /etc/sudoers file. Notice when looking at the sudoers file there was a % in front of wheel. The % indicates the following name is a group. Without the % the name is a user account. Second, making changes to /etc/sudoers has the risk of when the package maintainers make a change to that file it can be replaced when upgrading the package. I have not run Arch to know if there is a warning about hat or not. If there is and you don’t notice you will lose your changes. If you look at the bottom of the sudoers file you will see an include statement to include files in the /etc/sudoers.d directory. SUDO looks for files in this directory and appends them what was in the sudoers file. This directory is not touched by the package managers except to be created on initial install of the SUDO package. To add yourself or a group to the list of sudoers use your favorite editor to create a file in the /etc/sudoers.d directory with a line like that of the entry shown in the video for wheel in the sudoers file. For example (note do not include the quote marks and substitute your user name for user): “user ALL=(ALL) ALL” will give a user named user SUDO privileges requiring a password. You can also use “user ALL=(ALL) NOPASSWD: ALL” to sudo without requiring a password. As I recall the file names can be anything, but I generally have seen them start with a number and include the name being included. For our example the name will be something like: 010-user. One last thing you can remove SUDO status by removing the file or if you want to maybe establish it later just add ~ to the end of the name like 010-user~. When looking at files in /etc/suders.d sudo ignores files that end with ~ or include a period . in them. Sorry about the long length of this message but the more I typed the more it seems that needed to be said.
Hello, thank you so much for commenting! I really appreciate your thorough explanation. There's always more to learn and it's very helpful to have comments like this.
For Arch, either editing /etc/sudoers or using a drop-in file in /etc/sudoers.d is viable, according to the wiki; but maybe it is better practice to stick to drop-in files as you've suggested.
This is exactly the kind of content I needed. Thank you so much.
NOTE: #!/bin/sh will be necessary to run shell commands from your xprofile. You can add this in as the top line, it is called a "shebang" and it is used to instruct how the file should be parsed.
Please bare with me as I get used to recording! If I do forget something while recording I will always make note in the description.
Add the following lines to your ~/.xinitrc file for a KDE Plasma installation allowing for use of ~/.xprofile:
#!/bin/sh
[ -f /etc/xprofile ] && . /etc/xprofile
[ -f ~/.xprofile ] && . ~/.xprofile
export DESKTOP_SESSION=plasma
exec startplasma-x11
This was really informative, thank you.
You're welcome, and thank you for watching!
Thank you for your content, very useful and clear🙏
No problem! Thanks for watching :-)
simply the best!
Open a bottle of beer and make a toast that everything went smoothly.
Thank you for the tutorial
Are you going to cover ricing?
wow thank you now i know (at least for the moment lol) how to install software through the back door lol this is actully potentally shorter than apt install yourpackage although im assuming it HAS to be capital s -S is a minor inconvience but ill probably adapt. heres a tip for YOU! run this command sudo -S tldr this is very valuable its man with examples i saw you S vim and i thought S was the command so i was like man S LOL
I'd love to get your first impressions of hyprland or a bit of a guide on DWM - heard that's a bit tricky
Thanks for the suggestions! I'll definitely be making some DWM guides.
Single monitor crew rise up! :D
I have two actually, but keep rocking one! I had just one for years. Lol
display managers are useful in case you are using screen locks since when the dispaly server dies it would go to the display manager not the tty
Most WMs have screen-locking functionality, though I do agree it can be buggier than a dedicated display manager. Thanks for watching and commenting :)
The last topic you address would be worth a separate video. I use DWM and have had trouble getting polkit, the ssh-agent and the like to work. I borrowed commands from people's dotfiles just to realized that they messed up my system. With 'exec dbus-launch --exit-with-session dwm", for example, dunst would not work (I could not even execute a simple notify-send command.
My questions boild down to: What belongs into .bashrc, .bash_profile, .profile, .xprofile, .xinitrc and what services must be started for a system to run with startx. Login manager do some work for you, already, right, but that's not what I want.
Idea: a video on how to get audio would be useful!
Thanks for suggesting!
Yes very easy to follow,you wold make a great teacher.Would this be applicable to it being on a virtual machine ?
Thank you! Yes it would :)
So installing with yay makes the app files to be in .cache for yay? If i need to change the dwms config file for exemple ill be changing that file in yays cache? I cant find the "instalation" folder anywhere. Just making sure
Keep it up, really liking your style of teaching.
I can see the influence from Luke Smith in your layout. I’ve been using LARBS for about a year now and I think I’m going to use these tutorials to rice a new user and learn some more practical skills. Thanks for the tutorials!
Haha for sure, Luke's videos and explanations have always been among the best.
Awesome - glad to hear! No problem and thanks for watching and commenting.
👍👍
Thanks for watching! :)
Have you been able to solve the first scroll getting ignored when entering a x11 window?
X is the everything window system.
I already have arch installed but your video popped up on my recommendations and I figured I’d give it a watch and maybe learn something new. I’m curious why you start KDE through xorg vs letting a display manager like sddm handle that. Is there an advantage to this setup or is it just for simplicity and reducing bloat?
Thanks so much for watching!
I do find xorg/xinit to be simpler and easier to configure, but another important reason for me is that it also allows you to boot into a shell rather than a graphical environment, giving you immediate access to the command line before a more intensive program runs. An example of that in practice: if I have a software or hardware failure that is resulting in crashing/freezing once graphics are started, I can look at logs and troubleshoot right after I boot, instead of having to first disable the display manager by booting into the install medium and chrooting in.
So in sum, xorg/xinit provides the user more control. However, as with many things, it ultimately comes down to personal preference :^)
@@BreadOnPenguins Ah, makes sense. I see you use a tiling manager so I’m sure it’s also habit. I’ve only used KDE and gnome so I just install the kde/gnome package group and it does all the config for starting GDM/SDDM.
I do not see the url in the description ? I could not see that you had on both sides of yay and it said critical after I pressed enter so I just cleared it and exited. I am no good at night doing this stuff lol Same thing the last three nights I am in bed watching then I get up and try things then the next day I see how easily I messed up lol
Hello, which url are you referring to? If I missed it happy to add
Sometimes it takes a few tries to get something working haha, I'm sure you'll eventually get it!
@@BreadOnPenguins LOL at the 9:45 mark um I got it today like I said up to late doing this I was adding cloning into yay on the command line with it lol so dumb.
@@kevinDesRoches-vq1xe Gotcha, glad you figured it out! The url is with the 9:34 timestamp in the description but sadly UA-cam won't allow me to share hyperlinks until the channel is bigger
@@BreadOnPenguins I know i tries to send you what i copied and pasted to you was not allowed
LOL I have 7 disto's on it now my latest was Kubutu supposed to be good and light,I think I am in over my head lol but fun
is there a way i can display arch wiki / homepage in dark theme without using manpages?
Yes - the extension Stylus lets you use custom stylesheets and it has a good library of user-contributed ones for most popular pages :-)
@@BreadOnPenguins oh cool thank you! :D
Small nit: for the beginners, maybe running
EDITOR=nano visudo
rather than installing vi as "visudo" expected might trip up the newbies less
Fair point - thanks for mentioning!
dude how do i install pacman
im getting sudo: pacman: command not found
do you have any advice for switching from one DE to another in a graceful and clean way? say I want to remove KDE and install Gnome, what commands would you run? how would you get rid of all the random extra files laying around that could cause conflicts?
Should I just reinstall Arch entirely in this case?
Hello, sure -
First of all it is definitely not needed to reinstall Arch.
You can use pacman -Rns to remove packages you've installed for KDE - those flags remove system configuration and unneeded dependencies. User configuration won't impact anything, but you can remove it if you choose - it'll be in dotfiles (so in directories like ~/.local and ~/.config). Then install Gnome and switch over your display init files or display manager to use it :-)
@@BreadOnPenguins
cool thanks. do you think it would be wise to create a new user, and use the new DE with that user? so its essentially starting from a clean slate (new home folder etc) , and then remove the old user?
Just a small question, why not Wayland?
I had actually attempted switching a few years ago but compatibility wasn't great back then. I may switch in the future.
@@BreadOnPenguins I think with Valve's interference, Wayland is gonna get better
While I do believe your videos are a great resource. It is still overwhelming to install vanilla arch. This is why I'm going to stick by my voice to install endeavorOS KDE it's as close to arch that I want to get to.
That's fair - go for whatever makes the most sense for your use case, that's always the best choice one could make :^) Have fun with Endeavor!
Can't install vi. Says I need to be sudo to install it, but I need to install it to be sudo LOL
I see you're root, how?
Hey there, you can log out of your user account with the command "exit" (or you'll also be back at the login screen on a fresh boot); then use your root account to login - username 'root' and whatever password you had set for it on install. From there, you can use pacman to install vi, and use the visudo command :)
Hope that helps!
@@BreadOnPenguins nice, thanks for the reply!
I'll try that later.
@@BreadOnPenguins Hi again. Thank you for the patience to answer a noob question. I was able to follow your tutorial up almost the very end, but then something happened: I installed SDDM and the Nvidia proprietary drivers and configured Xorg X11 session, then whenever I tried to initialize Plasma, both through SDDM and through "startx", it would just give me a black screen with a cursor, and sometimes not even that. After a full night of tinkering I just figured out I can only start Plasma as root. Any ideas what I might have done wrong? I might be just that I'm dumb, but any hints whatsoever would be much appreciated.
@@ExNihilumHi, no problem. You may have a configuration mistake for your user account's xinitrc (or sddm conf); you can check through Xorg logs and the system journal (journalctl) for errors and see if anything gives a clue. If you're unable to figure out anything from that you can try setting up a brand new user and configuring from scratch - if your root account's configuration is working for getting Plasma to launch, you could copy/crosscheck with that. Good luck!
@@BreadOnPenguins I got it! It was the xinitrc file. Strange though, I wrote that file like 3 or 4 times. I probably messed up a few things during installation, but the point of installing Arch is learning about Linux anyway. Big thanks, I learned a lot from your videos.
Great video + the previous one, but I'll stick to Debian. Arch is just a massive headache, I would run it if I'll were on the latest and the greatest, but I'm not.
Thanks, that's completely fair :-) It always comes down to personal preference.
your dwm and firefox rice remind me of luke smith's
Luke has done a lot for the community! I've definitely learned and gotten ideas from his vids.
I’m using arch btw
KDE is nice, its simple ans easy to use.
But it crashes and breaks.
That is one downside of KDE that it crashes and breaks or kernel goes into panic and you got to reinstall the entire OS. You try to fix it and fail resulting in nothing more but a force to reinstall the OS
Which is why i recommend GNOME to People rather KDE
Also if you going to use those custominasations to make the icons look nicer etc make sure that once you reach a big update those are supported because if they aren't this is just asking for Kernel to panic.
Median arch user
Fun Fact : There's penguin prostitution in exchange for rocks for the females to build their nests with.
Interesting one, I didn't know that - thanks for sharing!
i did makepkg -si i got this!! ==> ERROR: You do not have write permission for the directory $BUILDDIR (/home/v/yay).
Aborting...
[v@v-hppaviliondesktoppc570p0xx yay]$ sudo su
[sudo] password for v:
[root@v-hppaviliondesktoppc570p0xx yay]# makepkg -si
==> ERROR: Running makepkg as root is not allowed as it can cause permanent,
catastrophic damage to your system.
Hello, did you do the git clone step as root..?
You can redownload as your normal user and then try building
@@BreadOnPenguins i got the same error!!!!! [v@v-hppaviliondesktoppc570p0xx ~]$ cd yay/
[v@v-hppaviliondesktoppc570p0xx yay]$ ls
PKGBUILD
[v@v-hppaviliondesktoppc570p0xx yay]$ makepkg -si
==> ERROR: You do not have write permission for the directory $BUILDDIR (/home/v/yay).
Aborting...
[v@v-hppaviliondesktoppc570p0xx yay]$