Not just another which linux distro is best for me thread.

[coolred]

I want to learn to use the command line and edit the files when needed, not just browse the web and listen to music with something other then windows. I have messed with a few distros here and there. Ubuntu as of late, and I can use it fine for day to day tasks. But little stuff gets to me about it. Like the forward and back buttons not working on my MS intellimouse explorer. To get thos eto work, you have to edit some file. I don't remember, as I haven't done it yet. And while that would teach me something, I am wondeirng if its the best way to learn.

Obviously i could go after a gentoo install, which I have tried before. Many people say that is a great learning experience. But since those that don't know how to do it, basically read how from the guide, is that really teaching you anything, or is it more like copying off a freind.

So what do you think is the best way to learn to minipulate linux like a pro?

 

[nweaver]

start by fixing the problems you may have (like buttons on the mouse) and move into automating tasks, like backups, or creating scripts for common tasks you do. Start using network services, (turn off DHCP on your router, and set it up on your box).

Gentoo gets into some kernel stuff, but it's still not any easier/harder to "learn command line" stuff...other then the default install is non gui, and it leaves yous (possibly) without a gui.


Learn to do your everyday work from CLI is the easiest.

 

[coolred]

So, now how do I go about learning how to do every day work from the CLI? And your saying just to stick with ubuntu while I do this?

Also one other question, is the only differance between ubuntu and kubuntu, the fact that kubuntu uses KDE as opposed to gnome?

 

[coolred]

Well I just setup ubuntu again. My screen resolution will only allow 640x480. I assume because the nvidia drivers were not installed. So I went to the Ubuntu guide to see how to install them. I started doing what it says, but it seems as though nothing I type in the command line is doing what it should. I see no results from anything i type. I know I am typing the stuff right, so what else can be the problem.


Edit, i take that back, I was able to make a backup of sources.list using the comman line. But when I type something like sudo apt-get update, i don't see anything happen, doe sit happen in the background? I assume it would launch the apt get program and do its work. Also typing sudo gedit /etc/apt/aoruces.list, does nothing. I assume it is meant to open a file editing app, but it does not. Not sure what the deal is.

 

[kamper]

I was getting a little tired of not learning a whole lot using fedora and I was bored this weekend so I decided to play around with openBSD.

The install was a small learning experience and it doesn't come with kde or gnome by default so that kept me on the commandline (and hitting man pages at a much higher rate than usual). Then, for shits and giggles, I decided to rebuild the kernel. That involved getting the sources from cvs, doing a compile and then learning a little about the bootstrap kernel loader so that I didn't have to replace the old one with my new version. The documentation made it all pretty easy (although grabbing the sources took an insanely long time) and it's definitely something I've never done on linux. I'm back in linux right now but when I have free time I'll go back and rebuild the userland (just for the sake of learning) and fool around with the package system to get a more familiar window manager installed. Overall it's been a very fun learning experience but if you're not good with the commandline then I would definitely recommend doing it on a spare machine so that you can have a stable desktop left over for safety and to keep a browser open with lots of documentation

 

[keeleysam]

Fedora Core 3

 

[n0cmonkey]

Originally posted by: kamper
I was getting a little tired of not learning a whole lot using fedora and I was bored this weekend so I decided to play around with openBSD.

The install was a small learning experience and it doesn't come with kde or gnome by default so that kept me on the commandline (and hitting man pages at a much higher rate than usual). Then, for shits and giggles, I decided to rebuild the kernel. That involved getting the sources from cvs, doing a compile and then learning a little about the bootstrap kernel loader so that I didn't have to replace the old one with my new version. The documentation made it all pretty easy (although grabbing the sources took an insanely long time) and it's definitely something I've never done on linux. I'm back in linux right now but when I have free time I'll go back and rebuild the userland (just for the sake of learning) and fool around with the package system to get a more familiar window manager installed. Overall it's been a very fun learning experience but if you're not good with the commandline then I would definitely recommend doing it on a spare machine so that you can have a stable desktop left over for safety and to keep a browser open with lots of documentation

I see the lack of KDE and gnome on a default install as a feature.

 

[nweaver]

Originally posted by: n0cmonkey

Originally posted by: kamper
I was getting a little tired of not learning a whole lot using fedora and I was bored this weekend so I decided to play around with openBSD.

The install was a small learning experience and it doesn't come with kde or gnome by default so that kept me on the commandline (and hitting man pages at a much higher rate than usual). Then, for shits and giggles, I decided to rebuild the kernel. That involved getting the sources from cvs, doing a compile and then learning a little about the bootstrap kernel loader so that I didn't have to replace the old one with my new version. The documentation made it all pretty easy (although grabbing the sources took an insanely long time) and it's definitely something I've never done on linux. I'm back in linux right now but when I have free time I'll go back and rebuild the userland (just for the sake of learning) and fool around with the package system to get a more familiar window manager installed. Overall it's been a very fun learning experience but if you're not good with the commandline then I would definitely recommend doing it on a spare machine so that you can have a stable desktop left over for safety and to keep a browser open with lots of documentation

I see the lack of KDE and gnome on a default install as a feature.

I agree

 

[Mesix]

If you want to dive face-first into command line, just hiht ctrl-alt-f2

 

[kamper]

Originally posted by: n0cmonkey
I see the lack of KDE and gnome on a default install as a feature.

I'm not complaining. I liked being dropped straight into a regular terminal for once and I don't like how all the fancy linux distros default to a graphical login. I fully intend to install at least kde at some point but I like that I'm forced to do to it myself because it's a good learning experience. So long as there's decent documentation, doing stuff from scratch is fun.

 

[P0ldy]

You do learn stuff on a gentoo install (not stage3, presumably), but most if it is watching gcc compile. Reading the guide is having your hand held, certainly, but so much of linux is reading, whether it's howtos or installation notes or whatever anyway, so I don't see much difference. At least after the first ten pages you'll be able to fdisk like nobody's business.