You are not logged in.
Pages: 1
Hey all, so although I am not sure if this is the place to post this, it seemed the closest.
I came to archlinux "awhile ago" and it has always been tied, if not just behind, gentoo linux as my favourite Linux. I liked arch because it had the technical tweeky side of gentoo, without the compiling and tedious setup. So I used to keep both on my HDD, and would boot into either dependant upon my mood.
Having recently acquired a netbook (hp mini 1000) with an SSD and an intel atom, I decided compiling was not for it. So archlinux it was. Got openbox up and running for the first time, pypanel and wbar, a pretty wallpaper and it felt home enough.
Now with a few problems arising here and there (sound issues, another forum post for that) I am beginning to realise I still have yet to get to grips with archlinux, get under the hood, I would like to make the move from user to power user, understand more about how arch linux works and how I can make it work and bend to my every need
I am a 17 year old student currently at college (high school in american terms) and during my spare time do alot of python programmer (started my own two projects and also helping out with the grubng probject) so I would say I know my way around a computer to an extent, but if I am going to be using archlinux more and more (which I definitely am) I should be able to get myself out of any sticky situations that may or may not arise. I do not mind reading tedious documents that are dificult to decipher or whatever documentation is available.
Any suggestions where to start?
Sorry this is all kind of long but yet stil vague, to sum up I would like to get to know archlinux, and linux in general, to a greater extent. I can already do basic things like piping, starting processes in the background, checking which are running, killing them off, I'm a huge fan of emacs, but I want more
Hope this is enough, Thanks all in advance.
Chris.
Offline
Did you try to read Arch Wiki ?
Anyway the best way to learn is to do. So to acquire experiences you can search the others problems on this forum and try to resolve them.
Offline
best way i've found is to install packages you're interested in, get them to work, set up your network, go through config files, and generally get involved with both the software on your computer and the community (through forums). both asking and answering questions.
You can also check out any projects you're interested in, and look at the code, bugs, and other things about them, and see what they need and how you can help.
IOW, get involved in what interests you, and learn from your good and bad experiences.
"I know what you're thinking, 'cause right now I'm thinking the same thing. Actually, I've been thinking it ever since I got here:
Why oh why didn't I take the BLUE pill?"
Offline
You'll be fine Just use the Wiki, Google, and the forums (plus the forum search) judiciously.
I've found the best way to learn Linux is by going out on limbs and breaking stuff, then fixing what's broken yourself. Not kidding.
Using Slackware (more vanilla) and Linux from Scratch may also further your 'education', once you have a good handle on Arch
Offline
Using Slackware (more vanilla) and Linux from Scratch may also further your 'education', once you have a good handle on Arch
+1 for LFS, that will teach you more than you ever want to know about how linux works. make sure you have about a week of free time though
"I know what you're thinking, 'cause right now I'm thinking the same thing. Actually, I've been thinking it ever since I got here:
Why oh why didn't I take the BLUE pill?"
Offline
I am a 17 year old student currently at college (high school in american terms) and during my spare time do alot of python programmer.
Wow. Exactly the same here.
Any suggestions where to start?
I installed it this way:
- Printed the Beginners Guide
- Burned a CD with the Arch Iso
- Spent two days installing it exactly the way I wanted and fixing errors
That already gave me a lot of knowledge. I almost have the entire guide in my head now. Next, for every problem I find, I will search for it for quite some time before asking for help.
This is the important part, because once searching for apparently simple problems you will find solutions for a handful of things that will start the process all over again.
It might seems idiot. Searching is an obvious part. But when doing it, be aware of the extra things that come along with it.
Offline
One of the things that I like to do is browse the forums and look for problems.
If I know how to fix the problem and a solution hasn't already been provided I'll post. However, when I don't know the solution I usually read through the thread to and see if a solution has been posted and if the posted solution worked for the OP.
Take caution however. Don't take ever solution you read as being a solution to the problem at hand. (I have a whole rant on this)
Offline
Thank you all for your replies, I have tried my hand at LFS twice in the past, the first being when I had no way near the required knowledge and it failed. The second time, my brother pulled out my power cord to use it himself... never bothered continuing after that.
I have also tried my hand at slackware, but was never a fan. Although as the saying says, if you learn slackware, you learn Linux.
I often browse around the forums, see and problem and have no idea as to how to solve it. That is the stage I would like to get it, I already have started helping out with an open source project written in python, but I still just do not feel "at one" with arch yet. I've scoured through the wiki, I guess it is just me being nitty and gritty.
With gentoo, in its early days, it would break often which would force me to find a fix and thus I would know more. Now its getting more and more stable and this is becomming less of a problem, but with leaving USE flags out and compiling programs in general there is still enough errors to keep me happy. Arch linux is far to stable although most would argue this is a good point, it doesnt force me to explore the underlying system and fix what is broken. Which is what I would really want to do, but I don't know how.
Thanks for all your replies,
Ducky.
Offline
Yup, the LFS docs are great. Between the Arch Wiki and LFS docs, you should be good to go (though I really, really like the FreeBSD Handbook as well )
Arch Linux + sway
Debian Testing + GNOME/sway
NetBSD 64-bit + Xfce
Offline
Enable the testing repo in /etc/pacman.conf. That will give you a few headaches to solve. Arch will not be as stable as it is then
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Pages: 1