Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
well...you tell me, does this look right? or should I add something? sickness# mount /dev/ad0s1a on / (ufs, local) /dev/ad0s1e on /home (ufs, local) /dev/ad0s1f on /usr (ufs, local) /dev/ad0s1g on /usr/local (ufs, local) /dev/ad0s1h on /usr/src (ufs, local) /dev/ad0s1d on /usr2 (ufs, local) procfs on /proc (procfs, local) linprocfs on /usr/compat/linux/proc (linprocfs, local) thx, Dave John Abreau wrote: >David Loszewski <stealth215 at mediaone.net> writes: > >>I did what you suggested and I still got the same error when trying to >>do a 'startx' under a different user otherthan root. >> >>I did a 'ls -l' on wrapper to see what it came up with for permissions >>and whis is what I got: >> >> sickness# ls -l /usr/X11R6/bin/Xwrapper >> -rwsr-xr-x 1 root wheel 7602 Sep 4 20:52 /usr/X11R6/bin/Xwrapper >> >>thx, >>Dave >> > >Hm. If the binary is set-uid root, but it still complains that it isn't, >then I can think of only two possibilities: either the filesystem it's on >is mounted nosuid, or it's misinterpreting some other condition and >reporting >it incorrectly. For instance, if it's complaining because it cannot write >to an nfs-mounted directory. > >The third possibility, of course, is that there's another factor I'm >overlooking :-P > >As for the filesystem, here's an example of what I mean: > > % mount > .... > /dev/sda3 on / type ext2 (rw) > .... > /dev/hdd1 on /disk2 type ext2 (rw,noexec,nosuid,nodev,user=jabr) > >Note that my root filesystem is mounted with the option "rw" (read/write), >whereas my /disk2 filesystem is mounted with a bunch of options including >"nosuid". The "nosuid" option tells the system to ignore the set-uid flag >on the file. > > > >
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |