Re: 2.2.12 bug in mount(2) or what?
Miquel van Smoorenburg (miquels@cistron.nl)
24 Nov 1999 12:22:00 +0100
In article <cistron.Pine.SCO.3.94.991124110139.26981A-100000@tyne.london.sco.com>,
>Have a look at this, please:
>
># grep cdrom /etc/fstab
>/dev/cdrom /mnt/cdrom iso9660 noauto,ro,exec,user,dev 0 0
># mount /mnt/cdrom
># grep cdrom /etc/mtab
>/dev/cdrom /mnt/cdrom iso9660 ro,noexec,nosuid 0 0
># id
>uid=0(root) gid=0(root)
>groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)
># uname -a
>Linux einstein.london.sco.com 2.2.12 #1 Wed Sep 29 08:15:49 BST 1999 i686
>unknown
>
>now, why is "exec" turned into "noexec"? Since I am root, I therefore have
>all capabilities (ignoring all those modern "capabilities" stuff until I
>understand them) and so mount should do what it is told. What is wrong
>here?
It is the utility mount(8) and not the system call mount(2) that does
this. So it's not a kernel issue at all.
But to answer your question, read the man page for mount(8) and
pay attention to the "user" flag that you specified in /etc/fstab
Mike.
--
First things first, but not necessarily in that order.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/