This Guy Needs Help Mounting NTFS As User

This is the only way I've managed to mount ntfs as user:

/dev/hda1 /mnt/hda1 ntfs auto,users,exec,ro,umask=0222 0 0

I had made a comment(#) in fstab that this was a bug fix, but I don't recall what it referenced (maybe the umask/read-only?).

q

Thanks qtech for the info. I don't currently have a drive with NTFS loaded on it (that I can experiment with) so I was limited in what I could try. Almost makes me want to load Windows on a box to see what happens... Nah!

Hopefully russ1960 will check this out

Jon

Try manually creating the mount point.

As root:

# mkdir --mode=555 /mnt/hda1

Then you'll either need to use the mount command to mount the partition, or reboot so that fstab will get re-processed.

Do I put this command in fstab?

Sorry for the confusion. You will need to remove the line from fstab.

If the line below,

/dev/hda1 /mnt/hda1 ntfs auto,users,exec,ro,umask=0222 0 0

is in your fstab file,

And you then cut and paste this line into a terminal (as root or su):

mkdir --mode=555 /mnt/hda1

Press enter.

Type exit and hit enter.

Reboot.

Hopefully this will get you closer to where you want to be.

If it fails, please post your current fstab file so we know how things stand.

q

Ok. Maybe try the above process again, but remove this line from "dynamic entries"-

/dev/hda1 /mnt/flash vfat,ext2,hfsplus noauto,users,dev,sync,dirsync

I'm pretty sure hda1 is not going to be a "flash" drive. If you are using a "flash" drive, go ahead and remove it for the moment.

I can't recall if there is a trick to getting the new line to stick in "static entries". Jon? Anyone? Do we have a mount point yet?

OK, this is what I don't understand. Russ, the post above: is that the complete /etc/fstab? The reason I ask is that qtech's asking to remove the /dev/hda1 from the "dynamic" section, but I don't see a "dynamic" section in your post above (and that should be the only section that get's new "magic stuff" put in). Second, why does your version of Mepis keep creating a "flash" entry?

Russ, I'm not asking this to sound like I'm asking a bunch of silly questions or to imply that you are not doing things, I'm asking to be sure that we are all on the same page. So forgive me if my questions seem a little stupid (I'm feeling that way right now). Is your "hda" drive an IDE drive physically inside the case? It's not a USB drive and not connected through a PCMCIA card in any way right?? Cause I can't figure out why you would keep getting that /mnt/flash directory created!!

Here's an idea. Since I don't see a "dynamic" section in you fstab, let's put one there! Modify your /etc/fstab file and put this line on the last line below everything else. Just cut/paste the line so spacing is exact:

# Dynamic entries below, identified by 'users' option

We have now created a dynamic section with no entries!

Remove or comment out the /dev/hda1 line with /mnt/flash.
Remove or comment out any references to /dev/hda1.
File the fstab file.

If you haven't already done it, follow qtech's advice above to make a /mnt/hda1 directory.

Do not create an entry in fstab for /dev/hda1.

What I want to find out is: What is Mepis creating when it finds a "new" partition? It should create a "non-dynamic" entry in /etc/fstab for /dev/hda1 pointing to /mnt/hda1 with whatever kind of file system it figures out!

Russ, after you do all of the above, reboot your system. Don't even worry about seeing whether you can/can't mount. Simply post the new, improved, tweaked-by-mepis /etc/fstab file. I wanna see what this sucker's putting in place

There was a post here a few days back on how to disable the creation of entries in fstab, but that will require modifying scripts (/usr/sbin/buildfstab and /usr/sbin/addfstab) and I don't want you to do that just yet.

Also, something I just found in two of the build scripts, so I don't know if it's useful or not yet: Russ, do you have a file called /tmp/fstab.$$.tmp on your system? Just let me know if it exists or not. How about you qtech?

Don't give up Russ! We'll get this (insert explitive here) going yet

Jon

Great news Russ! We'll beat this thing into submission yet!

My guess was that because there was no "# Dynamic..." reference in the /etc/fstab file, that somehow it was getting messed up by the /usr/sbin/buildfstab or /usr/sbin/addfstab commands.

OK, next change. Leave the "# Dynamic..." line in place and move the /dev/hda1... line above it. Or move "# Dynamic..." back to the bottom of fstab. We want to leave a spot for "dynamic" file systems but move /dev/hda1 above it since it's not dynamic now is it?

File the file, cross your fingers, arms and legs and reboot and see what happens.

Now, to your other questions: Regarding the lan startup. The Mepis OS Center attempts to start up all network interfaces even if they don't exist. It's more of an annoyance than anything, and it won't hurt, but if you want to get rid of those extra messages close your eyes (sorry). No, go into the Mepis OS Center and enter the root password. Go to the System Configuration, then Network Interfaces section. In the right-hand section, across the top you will find a bunch of tabs. The first two, Status and Misc show what interfaces are set up and start the loopback interface. Click on the Misc tab and you'll notice a checkbox "Start lo at system boot". It should be checked. The next tab, eth0, will have a similar checkbox, "Start at system boot". It also should be checked. The next tab, eth1, unless you have a second hard lan connection, should probably have the checkbox TURNED OFF. Ignore the Wireless tab, but continue to the ath0, ra0 and wlan0 tabs. Depending upon what type of wireless connection you have, if any, you will only need to set the checkbox on one of them. Oh, one other subtlety: if you make any change in any tabbed area make sure you click the Apply button at the bottom of the window. A minor "feature" of the OS Center is that it doesn't carry over changes from one tab to the next. So, once you've made all your changes to the OS Center, click Close.

Now to the /home/warren directory. Warren's the guy who created Mepis. I guess he just wants to have an account on every system

Did you actually get this user created on your installed system? To get rid of it, go into the Mepis OS Center and enter the root password. Then choose the System Configuration and then User Accounts. Across the top you will see an Add User and Delete User tab. Choose the Delete User tab. Select which user (warren) to delete, and if you check the "Delete user home directory" checkbox then /home/warren will be deleted.

That's enough for now. Let me know how everything goes

Jon

Re: lo eth0 eth1 ath0 ra0 wlan0

I suppose "eth" means ethernet, but what are the others for?

My only network interface is to a "wired" external router, which is connected to an ADSL bridge to the internet. I could potentially have another computer connected to the router, but that's not the case right now.

I left lo and eth0 enabled, and disabled eth1, ath0, ra0 and wlan0. My internet connection still works, so I guess that was the right thing to do.

Al,

Yes, "eth" refers to ethernet, now used as a generic reference to hard-wired network cards in Linux. And, of course, computer folks start counting at zero, hence eth0, eth1...

Unless you're making a computer into a router or some other system that needs multiple network connections, you will normally only have a single card (eth0).

The ath0, ra0 and wlan0 network connections are different wireless (WiFi) cards. Not too long ago Mepis only had a tab for ath0 and wlan0. I don't know what types of cards are detected and used by ra0 and wlan0, but my DLink dwl-650 PC card has an Atheros driver and so uses the ath0 tab.

Jon

Thanks for the explanation.

Russ, I'm glad to hear that things are continuing to be well with you and your system. I'm glad that we have been able to help you.

It's nice that you and your computer will have a "Windependence Day" (not my term)

Jon