Mailinglist Archive: opensuse-bugs (7182 mails)
| < Previous | Next > |
[Bug 355247] New: reluctant mount coreutil
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 22 Jan 2008 04:32:36 -0700 (MST)
- Message-id: <bug-355247-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=355247
Summary: reluctant mount coreutil
Product: SUSE Linux 10.1
Version: Final
Platform: i686
OS/Version: SuSE Linux 10.1
Status: NEW
Severity: Major
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: estellnb@xxxxxxxxx
QAContact: qa@xxxxxxx
Found By: Community of Practice
user mode mounts can cause a lot of problems:
1.) remount is supposed to succeed if mount succeeds:
2.) umount is refused if dev is mounted several times by user
/dev/ram1 on /mnt/ram type ramfs (rw,noexec,nosuid,nodev)
/dev/ram1 on /mnt/ram type ramfs (rw,noexec,nosuid,nodev)
3.) privileges of user mount point remain reset
erlaubt
Consequently it is possible to mount /dev/ram1 as user, but not to access
/dev/ram1 after mounting unless a root user resets the privileges of the mount
point. That simply does not make sense. I would suggest mount to execute a
chown for user mounts ('user' or 'users' mount option) on the mount point and
additionally a chmod g+u for mounts with the 'users' option on the mount point.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Summary: reluctant mount coreutil
Product: SUSE Linux 10.1
Version: Final
Platform: i686
OS/Version: SuSE Linux 10.1
Status: NEW
Severity: Major
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: estellnb@xxxxxxxxx
QAContact: qa@xxxxxxx
Found By: Community of Practice
user mode mounts can cause a lot of problems:
1.) remount is supposed to succeed if mount succeeds:
mount /mnt/rammount: Nur „root“ kann dies tun
mount -o remount /mnt/ram
2.) umount is refused if dev is mounted several times by user
mount|grep ram/dev/ram1 on /mnt/ram type ramfs (rw,noexec,nosuid,nodev)
/dev/ram1 on /mnt/ram type ramfs (rw,noexec,nosuid,nodev)
umount /mnt/ramumount: /mnt/ram scheint mehrfach eingehängt zu sein
mount|grep ram/dev/ram1 on /mnt/ram type ramfs (rw,noexec,nosuid,nodev)
/dev/ram1 on /mnt/ram type ramfs (rw,noexec,nosuid,nodev)
3.) privileges of user mount point remain reset
ls -ld /mnt/ramdrwxrwxrwx 3 elm users 72 2007-06-05 10:39 /mnt/ram
mount /mnt/ramdrwxr-xr-x 2 root users 0 2008-01-22 12:27 /mnt/ram
ls -ld /mnt/ram
chown elm:users /mnt/ramchown: Ändern des Eigentümers von „/mnt/ram“: Die Operation ist nicht
erlaubt
sudo chown elm:users /mnt/ramroot's password:
ls -ld /mnt/ramdrwxr-xr-x 2 elm users 0 2008-01-22 12:27 /mnt/ram
grep ram /etc/fstab/dev/ram1 /mnt/ram ramfs noauto,user 0 0
Consequently it is possible to mount /dev/ram1 as user, but not to access
/dev/ram1 after mounting unless a root user resets the privileges of the mount
point. That simply does not make sense. I would suggest mount to execute a
chown for user mounts ('user' or 'users' mount option) on the mount point and
additionally a chmod g+u for mounts with the 'users' option on the mount point.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |