You are not logged in.
Hello all. I hope I am posting this in the right place...
So, I come from Linux Mint, and they have a thread dedicated to the users top tips for newbies. I think Arch would benefit from something simillar, but for Arch of course.
As a complete beginner to Arch, I have very few tips except for...
-Read the wiki
-Use google
-Be prepared to put in effort to install the system
-Don't be afraid to ask for help
What are your guys top tips for beginners?
I am diagnosed with bipolar disorder. As it turns out, what I thought was my greatest weakness is now my greatest strength.
Everyday, I make a conscious choice to overcome my challenges and my problems. It's not easy, but its better than the alternative...
Offline
1. Use your system.
2. Found a problem? Yes -> go to 3. No -> go to 1.
3. Read wiki.
4. Problem solved? Yes -> go to 1. No -> go to 5.
5. Cry.
6. Rinse and repeat.
just looking around.
Offline
Heh, I like that so much that I turned it into a flowchart! I hope thats okay with you. Link below...
http://postimg.org/image/anc1qlsqj/
As a programmer, I find flowcharts very useful for seeing what your algorithim or whatever it may be is supposed to do.
I am diagnosed with bipolar disorder. As it turns out, what I thought was my greatest weakness is now my greatest strength.
Everyday, I make a conscious choice to overcome my challenges and my problems. It's not easy, but its better than the alternative...
Offline
Sure, sir.
Unfortunately, i can't see the picture. Maybe our government policy about censorship already this bad. (Not a joke, you can find about Indonesian censorship @ ddg / your favorite search engine.)
just looking around.
Offline
Offline
Ah, okay. Which image site would be able to host pictures where you can view them?
I am diagnosed with bipolar disorder. As it turns out, what I thought was my greatest weakness is now my greatest strength.
Everyday, I make a conscious choice to overcome my challenges and my problems. It's not easy, but its better than the alternative...
Offline
Ah, okay. Which image site would be able to host pictures where you can view them?
Pomf.se, maybe?
@karol, wow, you are really the ArchLinux archiver.
just looking around.
Offline
Read the wiki, yes, but especially follow it for installation. There is really no problem at all installing Arch if you just do that.
Tim
Offline
when installing, understand what each step is for and why you're doing it. Don't move on until you do understand.
Offline
I saw on another thread that you are in high school. I started with computers when I was your age. It was a good decision. It was also the mid 1970s.
I would try to find a mentor with whom you can meet in person. See if you can find a local user group around your school or a local college.
Most importantly, remember to turn the thing off on occasion -- go outside, meet people, ski, hike, whatever.
<dad mode> And don't neglect your studies. </dad mode>
Last edited by ewaller (2014-11-30 16:47:39)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
PS.: The "Blame Allan" is the most relevant part of this chart.
Nice flowchart, I'll show it to some of my friends who are beginning with Arch.
Last edited by thiagowfx (2014-11-30 18:15:20)
Offline
0. Don't update in mission critical situations. This applies to each and every operating system on this side of the light barrier.
1. Pay close attention to all the *.archlinux.org pages. There is information everywhere. As a hint what you should belooking for, did you know...
... that you can use the packages page to ...
... ... read the changelog of the package (but not of the software itself)?
... ... look at the PKGBUILD file for each package and read the applied patches?
... that you can set the bug tracker to "all projects" instead of just "Arch Linux"?
... that the AUR has an RSS feed, that you can filter for your AUR packages?
... that the main page has a news section?
... ... with an RSS feed?
... that every section and thread in the bbs has an atom feed, that you can filter in your client for everything relevant to your interests?
... that you can find the Arch planet on the homepage?
... ... and that even the planet has a feed?
... that you can subscribe to mailing lists on the home page?
... that there is a slight chance you might drown in information, if you subscribe to every feed and list without a proper filter in place?
2. Never copypasta into the terminal.
3. If you cannot name every file it will overwrite (blindfolded, at gunpoint, high on angel dust, in the middle of the practical part of an affaire du coeur), don't use --force with pacman.
4. Prepend this to every command you are about to invoke for the first time.
5. Learn how to use the AUR prior to using any AUR helpers. Then try to use a rather primitive helper (search and fetch packages) and build your own script around it.
6. Avoid third party repositories, unless you really know what you are up to. Ponder over the dangers of third party repositories, until you understand why building your own packages should be the first option in your mind.
7. Avoid dogmatic thoughts. There is no god behind vim or emacs, there is no One Way Of Unix. Be suspicious of those, who say systemd is (good|bad). Shun those who curse about pulseaudio, avoid those who praise it.
8. Using Arch Linux might get you laid, talking about it does not.
9. Speaking of that... I probably don't have to tell you that and since you are in high school (according to that other post) you probably already have to cater to your basic needs, but make sure...
... that Flash runs in your browser, does not lag, has sound and no weird colors.
... ... before you have visitors. You will not hear the end of it, if you don't.
... that you have means to mount external drives.
... ... with any possible exotic file system (ntfs and stuff like that).
... ... ... before you have visitors. You will not hear the end of it, if you don't. Alternatively, make sure to carry an XFS formatted USB drive every time you visit other people.
... that you know how to configure automatic screen blanking.
... ... before you have visitors. People will simply dress and leave the moment you start reading the Xorg documentation.
A. Create a cronjob, that scans for and deletes every non system file that does not have a backup routine of some sort. You did not want to keep that file anyway, why postpone the inevitable?
B. Have a look at the bash-completion package.
C. The password is "ken sent me" ↑↑↓↓←→←→BA.
Last edited by Awebb (2014-11-30 18:57:52)
Offline
First off, Xyne, that is an amazing flow chart.
That said, I've avoid breakage more than once by reading the forums before running a system upgrade, and also waiting a day before upgrading certain core components (the kernel mostly). It takes about 5-10 minutes to go though the forums if you do it everyday, and its easier to avoid a problem then it is to fix one.
[edit] That piece of advice of mine is in addition to reading the front page.
Last edited by nstgc (2014-11-30 19:08:44)
Offline
If you are too lazy to read the news, there is always pacnanny.
Offline
If you are too lazy to read the news, there is always pacnanny.
Or https://www.archlinux.org/packages/comm … /pacmatic/
Edit: Also, read https://bbs.archlinux.org/viewtopic.php?id=57205
Last edited by karol (2014-11-30 19:18:26)
Offline
Aw, most of the important stuff's been covered already. Hmmm... ILoveCandy. That's amusing for a while. There, I've made my contribution to budding minds.
Offline
It used to be a well-guarded secret, now it's in the wiki! The world is clearly going in the wrong direction.
;-)
Offline
Create a cronjob, that scans for and deletes every non system file that does not have a backup routine of some sort. You did not want to keep that file anyway, why postpone the inevitable?
Hehehehehe. I started really pushing thoughts like this to my friends and family members.
"This is a flash drive, and flash drives eventually fail. If you were to stick this into a computer in one hour from now and found out it no longer worked, what would you do? Do you have a backup?"
Offline
Assume every breakage is PEBKAC.
Debug ruthlessly until you conclusively disprove that premise.
Then, and only then, blame Allan...
Offline
Hilariously informative. Solid advice!
Offline
Check the news page before performing system updates, or consider using something like pacmatic that checks it and the mailing lists for you.
syn_ @ irc.freenode.net
Offline
keep current backups of home and pacman packages (learn to use rysnc), often times Syu forces me to re-install older rev packages (packages I've added, not the core stuff), learn to edit pacman.conf for packages that break with system updates. i migrated from Ubuntu to Mint to Arch, the Arch leap was at the insistence of my son who is far more advanced in linux (i was mostly windozing around in Mint) so Arch still way over my head almost 2yrs later, sorry i am a slow learner but really enjoy Arch anyway. And thanks for good advice syn42 (and others)
∞ hard times make the strong, the strong make good times, good times make the weak, the weak make hard times ∞
Offline
Man
Last edited by ackt1c (2022-11-05 13:20:04)
Offline
I read through all this many times but I didn't find it:
Break all the rules mentioned above (that is, the ones concerning backups, security etc). But ONLY if you have time to fix it afterwards :-).
And if you are sure you know that you are a masochist. Ehem ;-)
And then: Don't blame anyone. Try to do that by yourself.
It's 106 miles to Chicago we got a full tank of gas, half a pack of cigarettes, its dark and we're wearing sunglasses.
Offline