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.
to the options section would apply that mask, but I don't think that will help you much.
The problem you are having is your mounting it as root so only root would have rw permissions, you can fix this by changing the line to
What's the difference between prefacing a command with sudo vs. entering su and the password then entering each command and exiting?
I entered the "sudo umount" command and was prompted for a password. I entered the root password and got a "Sorry, try again." After three failed attempts I was returned to a $ prompt. I tried again with the same results. I know I'm keying it in right; it's the same password I use for Admin on my Windows system, it works for "su", and on the fifth and sixth attempts I keyed it in with a single finger, one character at a time.
I tried again with my user password and received "username is not in the sudoers file. This incident will be reported." Unfortunately, on subsequent attempts I now receive this message instead of a password prompt.
sudo uses YOUR password, it's used so you can give some users admin rights (to some or all commands) without giving out the root pass.
Sudo also preserves your environment, so you can run GIUs ar root without logging in as root (gksu, kdesu etc. are wrappers for su or sudo depending on how it's setup, on ubuntu its a wrapper for sudo).
Because in ubuntu the root account is disabled by default (though most users enable it right after install, like me) sudo is used to run administrative tasks by asking for the users password and only works if the user is setup in the /etc/sudoers file. sudo really replaces su as you can get a login shell with "sudo -i"
Thanks for the sudo answer, but as I noted I get a "username is not in the sudoers file. This incident will be reported." response when I use my password. Would entering the umount and mount commands after entering su and the root password accomplish the same thing, or must I troubleshoot the sudo problem before I can make progress on the read-only share problem?
This is a Red Hat 9 installation, not Ubuntu, if that makes any difference. Since I'm trying to do all of this from the command line, I'm not sure the distro would affect the process.
All you have to do to resolve the sudo problem would be to add yourself to the admin group, but yes, su followed by the umount & mount commands would work fine. I just like sudo for the convenience since I have it setup so I dont need to enter my password (don't do that unless you have a strong password and know who has access to your box).
mount //server/share$ /home/username/domainshare -t smbfs -o \
ls -l /home/username/domainshare/filename
if the user/group are the same unmount it again and use "cifs" insted of "smbfs"
The umount command works cleanly. After entering it, the share disappears.
After keying in the mount command and pressing Enter, the cursor dropped to the next line and has remained there. No error messages, no # or $ prompt, just a cursor blinking at the beginning of a blank line. Hitting Enter a couple of times generates two more blank lines.
If I open a second command window I can cd to the share and view the contents, but
that is strange, it seems that mount isn't finishing whatever it's doing for some reason. Is the share on the server setup to give you read-write access or just read-only?
Also when you mount with "-t smbfs" it's not mount that's working it's smbmount, smb protocol is quite old and is only really here for compatability, cifs is the newer version (I think from XP up windows works with cifs), so maybe see what happens when you try cifs