Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If you want to construct your distribution piece-by-piece with no assumptions, bare bones or however you decide, but yet want an awesome package manager, then doing a Debian Net Install is perfect for you.
And yes, *buntu is Debian based, but thats only the base. They add several of their own things. Debian is far less assuming and simple, it thinks of its users as "they know what they are doing."
A Debian Net Install literally places the entire Debian system and all the repositories you enable in front of you, and you fully customize your system to have whatever you want. If you don't want ANY packages, you can install the Oh So basic system.
You can even configure Debian to have experimental, bleeding-edge repositories, so you have the most up to date system available.
This sounds like it would be the best for me. It looks to give me exactly what I want without throwing me into the trenches of complete unfamiliarity just yet. I'm not very concerned with a bleeding-edge repo as long as the software in the standard one works to my liking.
Thanks for the help everyone. I know the 'what distro should I use' questions probably gets a little old around here.
He was responding to me.
Anyways, that's a god way of learning. But most people won't do so unless they are forced to. If you use a distro like Slackware,arch or gentoo then you have no other options but using the CLI. You automatically look up commands, google , read man pages and learn about using CLI. If your distro comes with a GUI package manager, I doubt as a newbie you will lookup and type commands instead.
He was responding to me.
Anyways, that's a god way of learning. But most people won't do so unless they are forced to. If you use a distro like Slackware,arch or gentoo then you have no other options but using the CLI. You automatically look up commands, google , read man pages and learn about using CLI. If your distro comes with a GUI package manager, I doubt as a newbie you will lookup and type commands instead.
He was responding to me.
Anyways, that's a god way of learning. But most people won't do so unless they are forced to. If you use a distro like Slackware,arch or gentoo then you have no other options but using the CLI. You automatically look up commands, google , read man pages and learn about using CLI. If your distro comes with a GUI package manager, I doubt as a newbie you will lookup and type commands instead.
The CLI was what converted me from a Windows user to a Linux user. The first few times I used various Linux distros I tried to use them like Windows only with access to free software and maybe some GUI configuration in Gnome. I would occasionally have to do something in the command line and it felt so stripped down and awkward. Then I started doing some software development in the CLI and things changed very quickly. The CLI went from being this awkward and 'useless' thing to something I realized was so incredibly powerful. Now I do everything in the CLI and find myself feeling very constrained on my Windows computer. If all you ever do is use it as a textual representation of window navigation then it will seem worthless, but once you start to learn the power of certain commands it changes everything.
The CLI was what converted me from a Windows user to a Linux user. The first few times I used various Linux distros I tried to use them like Windows only with access to free software and maybe some GUI configuration in Gnome. I would occasionally have to do something in the command line and it felt so stripped down and awkward. Then I started doing some software development in the CLI and things changed very quickly. The CLI went from being this awkward and 'useless' thing to something I realized was so incredibly powerful. Now I do everything in the CLI and find myself feeling very constrained on my Windows computer. If all you ever do is use it as a textual representation of window navigation then it will seem worthless, but once you start to learn the power of certain commands it changes everything.
The CLI is a beautiful but intricate and powerful interface. Windows?! HaHa. I don't call it a "command prompt," anymore. I call it "useless."
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.