From: Jan Willem Stumpel <jstumpel@planet.nl>
To: Robert Komar <rkomar@telus.net>
Cc: Jan Willem Stumpel <jstumpel@planet.nl>,
dosemu <linux-msdos@vger.kernel.org>
Subject: Re: cannot map temp file pool
Date: Tue, 19 Sep 2006 21:16:23 +0200 [thread overview]
Message-ID: <45104207.1070603@my.home> (raw)
In-Reply-To: <Pine.LNX.4.64.0609191131150.9202@robpc3.home.org>
Robert Komar wrote:
> It's not just the permissions that are important, but whether
> you can directly execute files within the temporary filesystem.
> Run 'mount' and see if tmpfs is mounted with the 'noexec'
> option. If it is, then that's at least one of your problems.
Aha..
vega:/home/jws# mount
/dev/hda5 on / type ext2 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,nodev)
/dev/hda6 on /dosd type vfat (rw,noexec,nosuid,nodev,umask=000)
automount(pid2284) on /misc type autofs
(rw,fd=4,pgrp=2284,minproto=2,maxproto=4)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
vega:/home/jws#
There doesn't seem to be a filesystem actually called tmpfs but
there is devshm which has the "type" tmpfs.
Is this a clue? Maybe I should make some link. I wonder what
tricks were performed by my latest Debian dist-upgrade.
For completeness, here is /etc/fstab:
# /etc/fstab: static file system information.
#
# <file system><mount point><type><options> <dump><pass>
/dev/hda5 / ext2 defaults,errors=remount-ro 0 1
/dev/hda6 /dosd vfat defaults,rw,user,umask=000 0 0
/dev/hda7 none swap sw 0 0
proc /proc proc defaults 0 0
/dev/fd0 /floppy auto defaults,user,noauto 0 0
/dev/hdc /cdrom iso9660 defaults,ro,user,noauto 0 0
/dev/hdd /cdrw iso9660 defaults,user,noauto 0 0
procyon:/ /nfs nfs defaults,noauto,rw 0 0
vega:/home/jws#
There is no tmpfs, but there never was, and dosemu always worked
(until today).
Regards, Jan
next prev parent reply other threads:[~2006-09-19 19:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 12:27 cannot map temp file pool Jan Willem Stumpel
2006-09-19 13:24 ` Damyan Ivanov
2006-09-19 15:24 ` Jan Willem Stumpel
2006-09-19 16:21 ` Robert Komar
2006-09-19 16:48 ` Mike McCarty
2006-09-19 18:12 ` Jan Willem Stumpel
2006-09-19 18:34 ` Robert Komar
2006-09-19 19:16 ` Jan Willem Stumpel [this message]
2006-09-19 20:17 ` Bart Oldeman
2006-09-19 20:58 ` Mike McCarty
2006-09-19 21:05 ` Bart Oldeman
2006-09-20 9:56 ` Jan Willem Stumpel
2006-09-20 16:21 ` Mike McCarty
2006-09-20 17:03 ` Jan Willem Stumpel
2006-09-20 17:11 ` Mike McCarty
2006-09-20 22:06 ` Claudia Neumann
2006-09-21 11:17 ` Jan Willem Stumpel
2006-09-21 17:56 ` Claudia Neumann
2006-09-19 19:15 ` Alain M.
-- strict thread matches above, loose matches on Subject: below --
2006-09-24 17:37 Stas Sergeev
2006-09-24 20:41 ` Jan Willem Stumpel
2006-09-25 3:45 ` Stas Sergeev
2006-09-25 8:54 ` Jan Willem Stumpel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45104207.1070603@my.home \
--to=jstumpel@planet.nl \
--cc=linux-msdos@vger.kernel.org \
--cc=rkomar@telus.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox