1kyle

[Log in to get rid of this advertisement]

This horrible perennial has returned again -- there were problems in suse 9.1 with this, fixed in 10.0 but is now back again with a vengeance. in beta 8.

I've got an external (Windows) usb hard drive (/dev/sdb1)

I've got a folder /extdisk1 which has READ permissions for EVERYBODY.

if I type at a console mount -t ntfs -o ro /dev/sdb1 /extdisk1 the disk mounts but I can ONLY access it as root.

From every other user I just see a Locked folder and even as root I can't change the permissions.

Grhhhhhhhhhh OK I know it's a beta but I'm having more than enough issues with this.

I'm "Triple" booting between 'Doze XP, SUSE 10.0 (my main running system) and 10.1 so testing 10.1 isn't too much of a hassle.

Cheers

-K

Keruskerfuerst

This is BETA SOFTWARE.

reddazz

These kind of problems whould be reported to the Suse developers. If you are using development versions, you have to expect bugs, if you want something thats stable, then use the official release versions.

broch

this is not a bug. SuSE 10.1 will not use submount anymore. It is possible that at this point developers could not decide yet, what to implement. Personally I am using ivman, nice and easy to install.
You will have exactly the same problem if you will try to install kernel 2.6.16 on SuSE 10.0 (HEAD kernel does not have subfs anymore).
ivman supports automounting of all devices I am using: dvd(recorder),cd(recorder), USB stick, camera (powershot s50), zip (parallel), floppy.

you can get ivman from here: http://ivman.sourceforge.net/
you will have to modify /etc/fstab, and for automatic start you will have to add symlink to your GUI session (e.g. ~/.kde/Autostart or ~.xsession or ~.xinitrc or whatever Gnome is using)

1kyle

I know -- that's why I'm testing it.

Reporting this stuff as I explained is to see if others also have this problem and to see if anybody has done anything to either find a fix or get round the problem.

People should be GLAD that this stuff is being tested so that when the FINAL (or even a release candidate) comes out it will have most of these problems fixed.

I usually post these sorts of errors on a public forum BEFORE reporting to Bugzilla because I want to make sure it's a REAL BUG I've found and not that I've done something stupidly or haven't read the documentation correctly.

Just answering a post with "It's a Beta" doesn't help ANYBODY --

I'd assume that anybody messing around with a beta expects errors and isn't idiotic enough to use it as a "production" type system.

Also if you don't check stuff out BEFORE reporting a bug the Bugzilla database will become so large and full of "User Errors" that it won't be worth looking at.

Cheers

-K

smiley_lauf

I agree whole hartedly with you on this one. Too many false-positives bugs will just generate chaos, and beside whos says production ready do not have bugs? Errors, leads to a better screening for bugs, that can be better diagnosed and then treated. Also, because of forums like these new users can learn from others errors and figure out the solutions easily. Testing dev versions is choice we make because believe in contributing to the development.

On another matter, any luck with a response from the OpenSUSE forums..I have been waiting for one for days.It seems they are not that keen to watch for beta testers problems?

abisko00

Hi 1kyle!

I guess you might get this kind of response, because you make the impression of being emotionally very involved. Your posts make it appear like you acctually are expecting to get a bug-free beta and you are very disappointed about finding some. It is just an impression that at least I got from these posts. I think you would get more elaborate answers if your post looked like you lined-out above: A clear report of 1. I have this problem. 2. Do you have this problem? 3. Did you solve it? 4. How?
I guess this wouldn't produce answers of the above type.

Don't get me wrong, I am not attempting to teach you anything about writing your posts. Just my

Keruskerfuerst

Instead of making a post here, go to www.opensuse.org and fill a bug report out. Makes much more sense to me.

broch

how you can file a bug if this is by design (removed subfs)? At least at this stage developers removed subfs but have not add a replacement. They know about automount.

read this:
http://en.opensuse.org/Meetings/Stat...-21/transcript

The are looking for a replacement, when they will find a good subfs alternative, then they will add automount back.