08-06-2011
On Debian, pmount is the program that uses the plugdev group. I installed pmount. This program allows users to manually mount storage devices. Unfortunately, this is not what I need to do and Debian already has some daemon that automatically does this.
I am trying to use a logic device programmer which has a USB connection with wine running the Windows application program. Debian automatically mounts the USB device ok but the application program doesn't have write permission to use it.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do I save a script to a pen drive? (3 Replies)
Discussion started by: beginner1
3 Replies
2. Linux
Hi Folks,
I want to know how to mount usb device (cd,dvd etc) in linux,
Regards,
Manoj (4 Replies)
Discussion started by: manoj.solaris
4 Replies
3. Solaris
AM TRYING TO CONNECT A USB EXTERNAL DRIVE FOR BACKUP,THE USB SLOT IS AVAILABLE,BUT I DONT KNOW IF IT IS READY WHEN I CONNECT IT,AND WHAT COMMANDS DO I NEED.
tHANKS (10 Replies)
Discussion started by: tomjones
10 Replies
4. UNIX and Linux Applications
When I attach a USB storage device to my Solaris server, the mount point is coming up as /rmdisk/unnamed_rmdisk
Is there anyway I can have this device come up as a mounted device with a predetermined mount name eg /morespace rather than unnamed_rmdisk ? (0 Replies)
Discussion started by: jimthompson
0 Replies
5. UNIX for Dummies Questions & Answers
hi, I was wondering if there's a way to safely disconnect a usb device from computer, I ask this because in windows when you disconnect a usb pen with the safe removal, the pen light then turns off, while I tried removing the pen with solaris and the light was still on ? (2 Replies)
Discussion started by: freeware
2 Replies
6. Red Hat
Hi friends,
I wanna know how to block USB devices in my RedHat flavor Operating system.
regards,
Prakash (3 Replies)
Discussion started by: prakashkumar41
3 Replies
7. UNIX for Advanced & Expert Users
In linux system when a pnp usb device is plugged in then how does the system gets a notification of it?
I mean to say in linux usb system there is usb host controller above which is host controller driver above which is usb core.
So does the host controller/usb core keeps on polling the usb bus... (1 Reply)
Discussion started by: rupeshkp728
1 Replies
8. Ubuntu
hi all:
as we know , when usb flash disk plug in and aotu mounted , the default permission of the usb flash disk is 700. that means others have no permission . the question: how to make others have read/write permission when the aotu mounted usb flash disk pluge in ? thanks !! (0 Replies)
Discussion started by: arnold.king
0 Replies
9. UNIX for Dummies Questions & Answers
Hi all
unixware 7.1.3 I'm afraid ! I connected a usb tape drive and it was automatically recognised in the device list (sdiconfig -l) and created devices in /dev/rmt (ctape1 etc.). I could successfully read and write to the device.
Then unplugged the usb cable and plugged it back in again... (0 Replies)
Discussion started by: deel
0 Replies
10. UNIX for Advanced & Expert Users
Hi,
i am developing an application on an ARM 7 architatcure with a small Linux.
i want to run tar on a usb device (~10 Mb) but it runs realy slow. the command only takes 1% of cpu usage.
is there a way to improve the tar command or is the USB-Connection the bottleneck here? (4 Replies)
Discussion started by: louisk
4 Replies
LEARN ABOUT MOJAVE
wineserver
WINESERVER(1) Windows on Unix WINESERVER(1)
NAME
wineserver - the Wine server
SYNOPSIS
wineserver [options]
DESCRIPTION
wineserver is a daemon process that provides to Wine roughly the same services that the Windows kernel provides on Windows.
wineserver is normally launched automatically when starting wine(1), so you shouldn't have to worry about it. In some cases however, it can
be useful to start wineserver explicitly with different options, as explained below.
OPTIONS
-d[n], --debug[=n]
Set the debug level to n. 0 means no debugging information, 1 is the normal level, and 2 is for extra verbose debugging. If n is
not specified, the default is 1. The debug output will be sent to stderr. wine(1) will automatically set the debug level when start-
ing wineserver if the +server option is set in the WINEDEBUG variable.
-f, --foreground
Make the server remain in the foreground for easier debugging, for instance when running it under a debugger.
-h, --help
Display a help message.
-k[n], --kill[=n]
Kill the currently running wineserver, optionally by sending signal n. If no signal is specified, sends a SIGINT first and then a
SIGKILL. The instance of wineserver that is killed is selected based on the WINEPREFIX environment variable.
-p[n], --persistent[=n]
Specify the wineserver persistence delay, i.e. the amount of time that the server will keep running when all client processes have
terminated. This avoids the cost of shutting down and starting again when programs are launched in quick succession. The timeout n
is in seconds, the default value is 3 seconds. If n is not specified, the server stays around forever.
-v, --version
Display version information and exit.
-w, --wait
Wait until the currently running wineserver terminates.
ENVIRONMENT VARIABLES
WINEPREFIX
If set, the content of this variable is taken as the name of the directory where wineserver stores its data (the default is
$HOME/.wine). All wine processes using the same wineserver (i.e.: same user) share certain things like registry, shared memory and
kernel objects. By setting WINEPREFIX to different values for different Wine processes, it is possible to run a number of truly
independent Wine sessions.
WINESERVER
Specifies the path and name of the wineserver binary that will be launched automatically by wine. If not set, wine will try to load
/usr/bin/wineserver, and if this doesn't exist it will then look for a file named wineserver in the path and in a few other likely
locations.
FILES
~/.wine
Directory containing user specific data managed by wine.
/tmp/.wine-uid
The directory containing the server Unix socket and the lock file. These files are created in a subdirectory generated from the
WINEPREFIX directory device and inode numbers.
AUTHORS
The original author of wineserver is Alexandre Julliard. Many other people have contributed new features and bug fixes. Please check the
file Changelog in the Wine distribution for the complete details.
BUGS
If you find a bug, please submit a bug report at http://bugs.winehq.org. <http://bugs.winehq.org>
AVAILABILITY
wineserver is part of the Wine distribution, which is available through WineHQ, the Wine development headquarters, at
http://www.winehq.org/. <http://www.winehq.org/>
SEE ALSO
wine(1).
Wine 1.2-rc6 October 2005 WINESERVER(1)