I got SUSE running how I would like and decided to hook up my 500gb SATA drive (NTFS formated) to watch some movies. I mounted it using YasT. When I tried to open a movie, it lagged my machine out like crazy. Sensing an issue I went to unmount it and saw that my main hard drive, which has about 450gb free, had 12. I logged out thinking it would reset it and when I went to log on it said:
“User’s $Home/.dmrc file is being ignored. File should be owned by user and have 644 permission.”
It also mentioned not having enough space. I logged on as root in safe mode as it wouldn’t let my normal account log on, and changed it so the hard drive would not mount at all, and then logged on as I normally do. Everything seems ok, but my question is what did I do wrong, and what should I do so it just reads off the extra drive and does not mount it in my home folder as it did?
IBC drunk schrieb:
> I got SUSE running how I would like and decided to hook up my 500gb
> SATA drive (NTFS formated) to watch some movies. I mounted it using
> YasT. When I tried to open a movie, it lagged my machine out like crazy.
> Sensing an issue I went to unmount it and saw that my main hard drive,
> which has about 450gb free, had 12. I logged out thinking it would reset
> it and when I went to log on it said:
>
> “User’s $Home/.dmrc file is being ignored. File should be owned by user
> and have 644 permission.”
>
> It also mentioned not having enough space. I logged on as root in safe
> mode as it wouldn’t let my normal account log on, and changed it so the
> hard drive would not mount at all, and then logged on as I normally do.
> Everything seems ok, but my question is what did I do wrong, and what
> should I do so it just reads off the extra drive and does not mount it
> in my home folder as it did?
Well, it sounds as if you chose your home directory, or possibly even
/home, as the mount point for your NTFS drive. Which is a bad idea for
several reasons I won’t go into details now.
Normally SUSE should mount hotpluggable external drives automatically
when they are connected, in a directory named after the disk label,
created dynamically below /media which exists for that purpose. If that
doesn’t work for SATA I’d recommend you do it the same way manually,
ie. use a mount point of, for example, /media/moviedisk.
So where should I create a mount point then? Should I just make it mount in any folder, and this drive is an internal one as well. I don’t know if that should make a difference.
On 2008-08-31, IBC drunk <IBC_drunk@no-mx.forums.opensuse.org> wrote:
>
> So where should I create a mount point then? Should I just make it mount
> in any folder, and this drive is an internal one as well. I don’t know
> if that should make a difference.
Technically, you can create a mount point anywhere.
But it’s normally done in the /mnt directory.
The exception to this are removeable volumes, which the system creates a
mount point for in /media. But then, those are made by the system.
–
Hanlon’s Razor:
Never attribute to malice that which is
adequately explained by stupidity.
IBC drunk schrieb:
> So where should I create a mount point then? Should I just make it mount
> in any folder,
Like rikishi said, it doesn’t really matter. But it shouldn’t be a
folder with existing content as that would be hidden by the mount.
Either create a new, empty folder in a place you like, or use one
of the conventional mount points below /mnt or /media.
> and this drive is an internal one as well. I don’t know
> if that should make a difference.
The only difference is one of convenience. Internal drives are
seldom added or removed, so they tend to get assigned mount points
relating to their use (/data, /var/spool/imap, whatever). External
drives are connected or disconnected more frequently, so most
people prefer mount points that help identifying the drive.
First, when editing fstab it created 2 more files, .fstab.swo and .fstab.swp. I believe those may be 2 backup files in case I screwed this up. I recovered fstab as it said to. May I delete those now?
Secondly, although I thought I had changed the files, I did not due to the fact that I was not the superuser. So my question to you is, as embarrassingly simple as this is, when editing files is sudo vi filename good enough? And is there a way I can do this graphically as I like to know all my options.
IBC drunk schrieb:
> When I try to create the mount point, it takes the files on the new
> internal, and takes up space on the current hard drive. I am mounting
> this wrong?
I’m afraid I don’t understand what you are trying to say.
Could you rephrase this? Perhaps show some real system output
illustrating the problem?
IBC drunk schrieb:
> I looked at this again and realized 2 things:
>
> First, when editing fstab it created 2 more files, .fstab.swo and
> .fstab.swp. I believe those may be 2 backup files in case I screwed this
> up. I recovered fstab as it said to. May I delete those now?
IIRC these are temporary working files of vim. You can delete them.
But if they are lying around that normally means that the editor
session was terminated abnormally, ie. something went wrong when
you quit the editor.
> Secondly, although I thought I had changed the files, I did not due to
> the fact that I was not the superuser. So my question to you is, as
> embarrassingly simple as this is, when editing files is sudo vi
> -filename- good enough?
Hm, I actually prefer “sudoedit”, but “sudo vi” should work just as
well. How did you leave vi? Normally via ZZ or :x, or something else?
> And is there a way I can do this graphically as
> I like to know all my options.
I’m afraid I’m not much good with GUI questions. I prefer command
line by far, as I feel I know more about my options that way.