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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Originally Posted by NGIB
My opinion about root access - it's my computer and I should have access to it. I understand the need for security on a multiuser system; however, for my personal computer it's whatever works simply and sudo works...
I'm of a similar opinion but I prefer "su -". Sudo is OK but you've reminded me to sort out the passwordless sudo on my pi as I think that's a step too far.
If you have broadcom wireless and are relying on that to work during install, you're out of luck however as I don't know of any distributions which redistribute their firmware.
I tend to do the debootstrap method of installing debian. One advantage is that you basically install debian in a chroot environment with an already running linux with the firewall and networking needs already done. Which allows you to get the networking up to par on the chroot install before you actually boot it. And other perks like putting a non-pae kernel on it and slapping it on a USB storage device destined for a different machine.
I was under the impression that /etc/sudoers came with the sudoers package. Am I mistaken?
Since sudo is a common tool, I imagine it is included in every distribution. (I have not checked the guts of every distro to see what is and is not installed, so there may be distros without it.) Systems like Debian do not have sudo enabled. It must be enabled and configured by those who need it.
Last edited by Randicus Draco Albus; 06-24-2014 at 01:40 AM.
what do you mean by "enabled"? Installed? Configured in a manner you don't like?
Yes, that was part of my puzzlement as well. I have been using Debian for a rather long time and I don't recall any versions that didn't come with the sudo package already installed. That package does include a sudoers file. I still have no idea of what an "ignorant abuse of sudo" is. Is it any different from an "ignorant abuse" of su. And is there such a thing as "an intelligent abuse"? Or is the the "ignorant" inserted for dramatic effect?
Oh, and congratulations on attaining guru-hood.
Installed by default in debian, sure. Enabled for users in the sudo group, sure. But users are not in the sudo group by default, and some folks prefer that. Normally if I need root permissions, I'm going to be doing more than one command. As in "apt-get update" and "apt-get dist-upgrade". So prefixing a sequence of commands with sudo in front of every command is wasted keystrokes for me. When I could just su to root.
I can see where sudo might be preferred for a company where full trust isn't given to all employees. But for my home desktop(s) where I'm basically the ONLY (known) user, it's wasted effort. And wasted drive space if I never use it. And a potential security hole if misconfigured. And... And... And... As I look at the raspbian defaults and cringe a little more everyday. That passwordless sudo, those rpc and nfs modules not as modules, that dated debian squeeze aroma. And I guess the arch image also has rpc and nfs non-modules. That wasted ram on a low ram piece of hardware. Probably just a personal preference, but geez louise.
It's all a matter of taste and preference. I enable sudo, because I'm sometimes forgetful. I run the risk of logging in as root and forgetting that I did, leaving my computer in root. I don't like to do that, so I mostly use sudo, which is set to time out in 5 minutes if I forget about it. If I'm going to do an update, I don't want to even type in the update and dist-upgrade separately, so I have an alias set to do both, using sudo. It's my computer, and if I want to use sudo, then by god I'll use sudo. If you or others want to rant about it, rant on. The Debian wiki plainly says that sudo is the preferred way, and I prefer it, so that's what I use. I do use su for some things, and have no issues with using it when needed, nor with anyone else using it exclusively. I just resent the snobs who think they know what's best for everyone in the world, when clearly they don't.
Q: if I use an RJ45 connection during the install might the installed system then support the Broadcom network chipset?
Only if you install the driver(s) for the chipset. Which will likely require proprietary firmware. And depending on the age of the device it may not be the default firmware that is accessible from a distros defaults. It's enough of a hassle that I use a standalone router to handle my wireless needs. In most cases it is possible to make the device work in linux. But YMMV and you might find that something like ndiswrapper works better than something like b43. Or vice versa.
In my case I use an asus rt-n12 which gives me a wireless method over ethernet for the client machines. In repeater mode for the asus firmware, and with client_bridge using ddwrt. With a side affect of having the capabilities of being the wifi access point for up to 4 wired devices. Which is a pretty good deal for a $40 device.
Debian is great. I switched to it after having used Ubuntu 10.04 as my first Linux distro, and there was really nothing hard about it (contrary to what I had been expecting). Debian worked out of the box for me (Just be sure to enable the non-free repositories).