aldelaro5
Paper Mario P
- Joined
- May 20, 2013
- Messages
- 9,724
- NNID
- aldelaro5
- 3DS FC
- 3050-7721-6617
HIIIIIIIIIIIIIIIIIIIIIII
So, in case you don't follow me on twitter......this happened:
FalKoopa (might also interest @Flight too), I am no longer goign to use Linux Mint, but instead, I am now going to use Arch Linux for......probably the rest of my life lol
BUT ALDE, falkoopa migth say, WHY THE DJBDHCBDHCYCBYD???
Well, it;s a long story so, I'll first cover why I felt to NOT use Linux Mint so suddenly.
Because Linux Mint is awesome! You jsut isntall it and omg the os has everything you need, it has a lot of support so google helps, most of the stuff are easy to use and you have a quite high degree of doign whatever the freak you want because it's linux!
.....except that there is some drawbacks that ONLY 2 DAYS AGO, I realised how annoying they were in long term. See, Ubuntu, Linux Mint and even Debian does what's called a "fixed" release cycle what it means is that periodically, the os gets upgraded with the newest (but not always the greatest, more on that later) packages AVAILABLE AT THE TIME OF THE RELEASE! They do this because they could first check the newest packages, test them and fix as many bugs as possible to make the os VERY solid and stable in the long run so for a distro made to be user friendly......yeah it's a smart decision. The packages still gets developped and updated, the fixed release distros will jsut not care to do it between releases unless it;'s very improtant like security and stuff.
So, the idea here is you get (it takes soem time granted) potentially outdated software that won't get updated until.....months or 2 freaking years in the case of mint. Debian stable is worse, it's undetermined, but it takes soem years, altough debain testing is constantly updated untill a deep freeze which takes 6 months, but anyway, you get the idea, in long term, you are missing out, but it;s rock solid.
So, for me, why did this became a problem?
Because I keep wanting to run the lattest stuff for multiple reasons, higher ogl capabilities, bugfixes that I REALLY need (like that recording sampling rate or that bluez bug with wiiu pro controller), lattest dolphin for newest features, even compilers to compile these newer stuff. There's A LOT of reasons for me to get the lattest as fast as possible and unfortunately, mint is really hindering that because it keeps freezing their stuff so each 2 years, I have to reinstall......another annoying thing, why can't I jsut have updated packages and leave as that?
For short, it annoys me to wait and the other thing that I realised was slightly annyoing is, they expect you to not touch too much about critical stuf......but I do that a lot and with very good reasons. the fact they packaged the distros for you makes it hard to get what you need and what you don;t need and what is safe to be removed, or critical, it's harder to figure out on an os you didn;t even configured. Oh also, I am getting a lot of experience, if it;s broken, I coudl fix it so I don;t care too much on loosing stability.
There was an alternative which was to use debian testing in linux mint debian edition......that failed miserably when testing it in a vm I made. It's not designed to work anyway, but I tried.
So, I explored alternatives to fix this problem and this is where I heard about "rolling" releases distros.
What this means is the os gets only released once: the initial release and it is NEVER EVER released again, NEVER. Instead, what happens is the packages the os would have gets directly updates and the os will simply get them (though the user is responsible for this so he can decide what to upgrade and stuff). Only on one command, the user basically upgraded everything.
This has a couple of advantages. You never have to reinstall, you are always going the get the lattest releases, you are most likely will be able to run everything since everything is updated etc.... The thing to watch is because it rolls, it can mean that an upgrade can break stuff since, so it's less stable, but since the user is already responsible for what to upgrade......well it's also expected that you are responsible for fixing these. In other words, you get bleeding edge software, but you are responsible for the stability.
And the msot known distors using rolling releases is Arch Linux, but it took me some hours to realise why it's so appreciated.
So, finalyl I can describe it, what the freak is Arch Linux?
It is one of the most minimalistic distros you can get. It is designed around the principle of "DIY", you build the os, it;s not done for you, you install everything you need and nothign more. The install isn;t even done on gui, you have to do everything a graphical installer would.....in command line. And EVEN if you manage to isntall it, you are not getting a gui, you are still in command line and if you want the gui, jsut install it. EVEN the installation install the msot basic stuff.....don;t even expect to get the x server.....yes, you have to even install x.
As for how the isntallation of stuff works, pretty simple, it;s done with......pacman (NO, NOT THE GUY IN SSB4, NO).
ok it's stands for PACkage MANager ok? thanks.
anyway, it;s basically the apt-get of debian and derivatives, you can install, remove, upgrade and so on and so forth. The default repository are called the "community" one so everything in there is officially supported and you pick what you want and if there's updates, you LITTERALLY run jsut one command..... sudo pacman -Syu (that u from what I heard is VERY important so). Nothign too diffiferent, except that Arch Linux has one thing that imo makes it so awesome: the AUR
No, it;s not a country code, it's an acronym that stands for Arch User Repository. View it like a GIANT ppa made of all the ppas you can wish on earth, it;s basically that, but with a twist. These packages aren't binairies, they are sources and in fact, they are JUST build script. This does mean you have to git clone (there's programs that does make it a bit easier however), but the main difference is building. The packages are build script, they are DESIGNED to jsut work. this means that if soemthing goes wrong when building it, that means you can report the package maintainer or comment because it';s likely not your fault if it;s supposed to work (though, check the comments for fixes, erros can happen because of you, but the building is SUPPOSED to work).
So what's awesome about it?
It is managed by the Arch users, yes, everyone can submit packages (they of course get reviews and such). Because of this, it has EVERYTHING. I seriously mean everything, on the tests I did on a vm I made, they had the dolphin development branch, my twitch gui client I like to use, lattest mesa, LATTEST CITRA EVEN!, and probably everything that possibly exists since they are jsut using thir git sources and they make buildscripts. As for why not just community, well if the packages gets good enough, it is pushed to community, but there is so much on the aur that I don't expect them to maintain the very specific cases like me having the lattest dolphin all the time.
Oh and yes, these can be updated easilly because you build packages which pacman installs after so it knows where to check.
So, what about the install? iosn't it complicated?
......yes, took me 3 hours to get cinnamon running on a vm, around 1 hours on my real machine because of....a weird wifi card thing (i will tell my install adventure after ). The really good thing about this is, it;s SOOOOOOO well documented. God, this is NOT like ubuntu or mint, they tell EVERYTHING and they tell so much that you coudl read their wiki made for arch and it could apply to every linux distros with how much they tell you. They don't really guide you, they tell you how to do things. I learned in 3 hour:
But here;s the thing, if I was able to do that withotu crying (though, I got help by someone I knew), I don't think a broken package can stop me tbh, you jsut downgrade it in worst cases.
So this is why I decided to switch, I wanted the lattest, I ddin;t care to be responsible for stability because I have 2 years of experience and I fidn the idea very interesting. bonus: it's a lot more customisable because you get jsut what you need and you can do everything. plus, the fact I can talkto you now means it;s fine (I still have a lot of stuff to do lol).
So want to know how the install went?
FalKoopa I think you'll love that story
So first, you burn an iso which is the lattest snapshot of the basic stuff, updated constantly. Even if it wasn;t one comamnd upgrades everything. One thing to note, the iso is 700 mb.....that;s 2 times less then mint cinnamon, wow!
So you boot to it and then you boot the 64bit (who uses 32 bit anyway?) and then......you get a command prompt on a root account......
OMG PANIC WHAT THE FREAK DO I DO??
well, I had a cell phone to check the beginner guide that tells you how to install and the steps to do it, but the cd kindly provides a txt files, altough, I will admit, that is a very trimmed version of the fuil guide, pls, use the full guide because otherwise, you might actully cry. a second tty can help here btw.
So the very first thing you should check is configure your internet. If it's wired, you are likely ok, if it;s wireless, there's a surpringly easy to use thing to connect to a network via cli, it;s not hard to use tbh. Now, here I ran into a problem where my card didn;t wnat to know anything so I switched to my old card and I could have a network, ping is usefull btw.
if you ahve internet, good, now you need to do the partitioning stuff. That actually.....is the hardest part lol. You have to do lots of command and read docs on how to put the partitions, what type they are and how long they are. Seriously, it's nothing like a gui, it's hard and annoying.
Next, give filesystem format, that honestly is very simple.
Next, you mount them which is......fairly easy because you mount them to /mnt and how you view it is view /mnt as your future / root of your os.
Before you chroot to it (you root AND change where you run), you do a little thign and this is where you install your stuff. It's quitew a lot and it will isntall essential stuff like gcc. After, a lot of little stuff, editiong locale files, eritting your hostname, configuring timezone, add a user, set password, etc.... you even have to tell that this user can use sudo, lol.
The final step really is to install the boot loader, I chose grub because I like it. It's.....very easy to install. After, you can fianlyl reboot into your new os (that btw, was the hardest of the thing).
OH NO COMMAND PROMPT HELP!
This is however where it starts to be fun. Your first priority is get a gui cause....cli is annoying. So you install x and here';s thign thing for you: X works by default. You don't have to configure it, you can, but you don't need to. This is what made me realise how....complicated the process of bulding the os is, but it;s not that badm, you jsut install stuff. After x comes the dispaly manager! here, I tried mdm, but.......mdm isn;t very friendly with systemd so I used gdm which is the gnome one. As for the desktop environemnt, I choose cinnamon because why the freak niot? iot was int he repos, I want it
After you enabled gdm and start it OMG THERE';S GRAPHICS!
WE MADE IT!
After you realise how itchy your eyes from the light (lol), you can login and you get a VERY basic environemnt, even worse than windows basic.
Btw, I spent 30 minutes tryign to fix soemthign because cinnamon was jsut displaying the background and nothign else so I was annoyed to not have my panel and then I eventually relaised "oh, it;s not set as the primairy monitor......FAIL!". yeah
Anyway this is where you install basic stuff like pulseaudio or bluez for bluetooth, firefox and such. You now have a basic system and you can do anything to it, even lick it if you're into it!
I just got some stuff fixed here like I isntalled lots of font packs so JP characters works, but yhe idea here is you start VERY barebones. Like, seriosuly, I coudln;t even do ifconfig because you need to isntall net-tools......yeah it;s very basic.
Because of this, it's goign to be as light as it can be and ONLY have what you want.
And it;s also never goign to be behind in software so never need to upgrade
This is why I switched, I love the idea, and I can;t wait to see where this will lead me. Now, I do wonder, FalKoopa , would you be ready for this adventure?
So, in case you don't follow me on twitter......this happened:
FalKoopa (might also interest @Flight too), I am no longer goign to use Linux Mint, but instead, I am now going to use Arch Linux for......probably the rest of my life lol
BUT ALDE, falkoopa migth say, WHY THE DJBDHCBDHCYCBYD???
Well, it;s a long story so, I'll first cover why I felt to NOT use Linux Mint so suddenly.
Because Linux Mint is awesome! You jsut isntall it and omg the os has everything you need, it has a lot of support so google helps, most of the stuff are easy to use and you have a quite high degree of doign whatever the freak you want because it's linux!
.....except that there is some drawbacks that ONLY 2 DAYS AGO, I realised how annoying they were in long term. See, Ubuntu, Linux Mint and even Debian does what's called a "fixed" release cycle what it means is that periodically, the os gets upgraded with the newest (but not always the greatest, more on that later) packages AVAILABLE AT THE TIME OF THE RELEASE! They do this because they could first check the newest packages, test them and fix as many bugs as possible to make the os VERY solid and stable in the long run so for a distro made to be user friendly......yeah it's a smart decision. The packages still gets developped and updated, the fixed release distros will jsut not care to do it between releases unless it;'s very improtant like security and stuff.
So, the idea here is you get (it takes soem time granted) potentially outdated software that won't get updated until.....months or 2 freaking years in the case of mint. Debian stable is worse, it's undetermined, but it takes soem years, altough debain testing is constantly updated untill a deep freeze which takes 6 months, but anyway, you get the idea, in long term, you are missing out, but it;s rock solid.
So, for me, why did this became a problem?
Because I keep wanting to run the lattest stuff for multiple reasons, higher ogl capabilities, bugfixes that I REALLY need (like that recording sampling rate or that bluez bug with wiiu pro controller), lattest dolphin for newest features, even compilers to compile these newer stuff. There's A LOT of reasons for me to get the lattest as fast as possible and unfortunately, mint is really hindering that because it keeps freezing their stuff so each 2 years, I have to reinstall......another annoying thing, why can't I jsut have updated packages and leave as that?
For short, it annoys me to wait and the other thing that I realised was slightly annyoing is, they expect you to not touch too much about critical stuf......but I do that a lot and with very good reasons. the fact they packaged the distros for you makes it hard to get what you need and what you don;t need and what is safe to be removed, or critical, it's harder to figure out on an os you didn;t even configured. Oh also, I am getting a lot of experience, if it;s broken, I coudl fix it so I don;t care too much on loosing stability.
There was an alternative which was to use debian testing in linux mint debian edition......that failed miserably when testing it in a vm I made. It's not designed to work anyway, but I tried.
So, I explored alternatives to fix this problem and this is where I heard about "rolling" releases distros.
What this means is the os gets only released once: the initial release and it is NEVER EVER released again, NEVER. Instead, what happens is the packages the os would have gets directly updates and the os will simply get them (though the user is responsible for this so he can decide what to upgrade and stuff). Only on one command, the user basically upgraded everything.
This has a couple of advantages. You never have to reinstall, you are always going the get the lattest releases, you are most likely will be able to run everything since everything is updated etc.... The thing to watch is because it rolls, it can mean that an upgrade can break stuff since, so it's less stable, but since the user is already responsible for what to upgrade......well it's also expected that you are responsible for fixing these. In other words, you get bleeding edge software, but you are responsible for the stability.
And the msot known distors using rolling releases is Arch Linux, but it took me some hours to realise why it's so appreciated.
So, finalyl I can describe it, what the freak is Arch Linux?
It is one of the most minimalistic distros you can get. It is designed around the principle of "DIY", you build the os, it;s not done for you, you install everything you need and nothign more. The install isn;t even done on gui, you have to do everything a graphical installer would.....in command line. And EVEN if you manage to isntall it, you are not getting a gui, you are still in command line and if you want the gui, jsut install it. EVEN the installation install the msot basic stuff.....don;t even expect to get the x server.....yes, you have to even install x.
As for how the isntallation of stuff works, pretty simple, it;s done with......pacman (NO, NOT THE GUY IN SSB4, NO).
ok it's stands for PACkage MANager ok? thanks.
anyway, it;s basically the apt-get of debian and derivatives, you can install, remove, upgrade and so on and so forth. The default repository are called the "community" one so everything in there is officially supported and you pick what you want and if there's updates, you LITTERALLY run jsut one command..... sudo pacman -Syu (that u from what I heard is VERY important so). Nothign too diffiferent, except that Arch Linux has one thing that imo makes it so awesome: the AUR
No, it;s not a country code, it's an acronym that stands for Arch User Repository. View it like a GIANT ppa made of all the ppas you can wish on earth, it;s basically that, but with a twist. These packages aren't binairies, they are sources and in fact, they are JUST build script. This does mean you have to git clone (there's programs that does make it a bit easier however), but the main difference is building. The packages are build script, they are DESIGNED to jsut work. this means that if soemthing goes wrong when building it, that means you can report the package maintainer or comment because it';s likely not your fault if it;s supposed to work (though, check the comments for fixes, erros can happen because of you, but the building is SUPPOSED to work).
So what's awesome about it?
It is managed by the Arch users, yes, everyone can submit packages (they of course get reviews and such). Because of this, it has EVERYTHING. I seriously mean everything, on the tests I did on a vm I made, they had the dolphin development branch, my twitch gui client I like to use, lattest mesa, LATTEST CITRA EVEN!, and probably everything that possibly exists since they are jsut using thir git sources and they make buildscripts. As for why not just community, well if the packages gets good enough, it is pushed to community, but there is so much on the aur that I don't expect them to maintain the very specific cases like me having the lattest dolphin all the time.
Oh and yes, these can be updated easilly because you build packages which pacman installs after so it knows where to check.
So, what about the install? iosn't it complicated?
......yes, took me 3 hours to get cinnamon running on a vm, around 1 hours on my real machine because of....a weird wifi card thing (i will tell my install adventure after ). The really good thing about this is, it;s SOOOOOOO well documented. God, this is NOT like ubuntu or mint, they tell EVERYTHING and they tell so much that you coudl read their wiki made for arch and it could apply to every linux distros with how much they tell you. They don't really guide you, they tell you how to do things. I learned in 3 hour:
- how to create partitions in cli and format them
- how to format partitions in cli
- how systemd works and how to use it
- how to setup the locale
- how to setup a netowrk in cli
- how to use pacman for basic uses
- how to isntall X
- how to install a dispaly manager and a desktop environeemnt
But here;s the thing, if I was able to do that withotu crying (though, I got help by someone I knew), I don't think a broken package can stop me tbh, you jsut downgrade it in worst cases.
So this is why I decided to switch, I wanted the lattest, I ddin;t care to be responsible for stability because I have 2 years of experience and I fidn the idea very interesting. bonus: it's a lot more customisable because you get jsut what you need and you can do everything. plus, the fact I can talkto you now means it;s fine (I still have a lot of stuff to do lol).
So want to know how the install went?
FalKoopa I think you'll love that story
So first, you burn an iso which is the lattest snapshot of the basic stuff, updated constantly. Even if it wasn;t one comamnd upgrades everything. One thing to note, the iso is 700 mb.....that;s 2 times less then mint cinnamon, wow!
So you boot to it and then you boot the 64bit (who uses 32 bit anyway?) and then......you get a command prompt on a root account......
OMG PANIC WHAT THE FREAK DO I DO??
well, I had a cell phone to check the beginner guide that tells you how to install and the steps to do it, but the cd kindly provides a txt files, altough, I will admit, that is a very trimmed version of the fuil guide, pls, use the full guide because otherwise, you might actully cry. a second tty can help here btw.
So the very first thing you should check is configure your internet. If it's wired, you are likely ok, if it;s wireless, there's a surpringly easy to use thing to connect to a network via cli, it;s not hard to use tbh. Now, here I ran into a problem where my card didn;t wnat to know anything so I switched to my old card and I could have a network, ping is usefull btw.
if you ahve internet, good, now you need to do the partitioning stuff. That actually.....is the hardest part lol. You have to do lots of command and read docs on how to put the partitions, what type they are and how long they are. Seriously, it's nothing like a gui, it's hard and annoying.
Next, give filesystem format, that honestly is very simple.
Next, you mount them which is......fairly easy because you mount them to /mnt and how you view it is view /mnt as your future / root of your os.
Before you chroot to it (you root AND change where you run), you do a little thign and this is where you install your stuff. It's quitew a lot and it will isntall essential stuff like gcc. After, a lot of little stuff, editiong locale files, eritting your hostname, configuring timezone, add a user, set password, etc.... you even have to tell that this user can use sudo, lol.
The final step really is to install the boot loader, I chose grub because I like it. It's.....very easy to install. After, you can fianlyl reboot into your new os (that btw, was the hardest of the thing).
OH NO COMMAND PROMPT HELP!
This is however where it starts to be fun. Your first priority is get a gui cause....cli is annoying. So you install x and here';s thign thing for you: X works by default. You don't have to configure it, you can, but you don't need to. This is what made me realise how....complicated the process of bulding the os is, but it;s not that badm, you jsut install stuff. After x comes the dispaly manager! here, I tried mdm, but.......mdm isn;t very friendly with systemd so I used gdm which is the gnome one. As for the desktop environemnt, I choose cinnamon because why the freak niot? iot was int he repos, I want it
After you enabled gdm and start it OMG THERE';S GRAPHICS!
WE MADE IT!
After you realise how itchy your eyes from the light (lol), you can login and you get a VERY basic environemnt, even worse than windows basic.
Btw, I spent 30 minutes tryign to fix soemthign because cinnamon was jsut displaying the background and nothign else so I was annoyed to not have my panel and then I eventually relaised "oh, it;s not set as the primairy monitor......FAIL!". yeah
Anyway this is where you install basic stuff like pulseaudio or bluez for bluetooth, firefox and such. You now have a basic system and you can do anything to it, even lick it if you're into it!
I just got some stuff fixed here like I isntalled lots of font packs so JP characters works, but yhe idea here is you start VERY barebones. Like, seriosuly, I coudln;t even do ifconfig because you need to isntall net-tools......yeah it;s very basic.
Because of this, it's goign to be as light as it can be and ONLY have what you want.
And it;s also never goign to be behind in software so never need to upgrade
This is why I switched, I love the idea, and I can;t wait to see where this will lead me. Now, I do wonder, FalKoopa , would you be ready for this adventure?