Skip to contentSkip to conversation

Using modem under dosemu 1.1.5

DISCUSSION Ralph Alvy 5 participants 10 messages Jul 13, 2003 – Jul 15, 2003

lore
Share & tools
lore

Ralph Alvy

author
#0 lore raw

I think this may be the last thing I need to get everything I need to run under dosemu ... I can't get access to the modem, which I have connected to my serial port on com 1. I have

	$_com1 = "/dev/modem"

But when I load dosemu 1.1.5, I see this:

ERROR: tty: lock: (/var/lock/LCK..modem): Permisssion denied

I tried to resolve this by putting myself in the groups uucp and lock, but that fails to solve it.

#1 lore raw

Ralph,

Check the permissions on /dev/ttyS0 (or 1 etc) and on whatever it links to. On my Slackware 9.0 system the /dev/ttyS0 links to /dev/tts/0 which was set read/write for root only. Changed it to read/write everyone (0666 I think) and everything worked great. Also, if you are using devfs you might need to modify /etc/devfsd.conf to save permissions accross re-boots.

Hope this helps,
Rick Knight
([email protected])

Quoted 15 lines · Ralph Alvy

I think this may be the last thing I need to get everything I need to run under dosemu ... I can't get access to the modem, which I have connected to my serial port on com 1. I have

    $_com1 = "/dev/modem"

But when I load dosemu 1.1.5, I see this:

ERROR: tty: lock: (/var/lock/LCK..modem): Permisssion denied

I tried to resolve this by putting myself in the groups uucp and lock, but that fails to solve it.

-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#2 lore raw
In reply to Ralph Alvy

Am Sonntag, 13. Juli 2003 19:49 schrieb Ralph Alvy:

Quoted 4 lines

I think this may be the last thing I need to get everything I need to run under dosemu ... I can't get access to the modem, which I have connected to my serial port on com 1. I have

Quoted 9 lines
	$_com1 = "/dev/modem"

But when I load dosemu 1.1.5, I see this:

ERROR: tty: lock: (/var/lock/LCK..modem): Permisssion denied

I tried to resolve this by putting myself in the groups uucp and lock, but that fails to solve it.

Hi,

it is not the permission for /dev/ttyS1 but the directory /var/lock must exist and you must have wright permission for this directory, otherwise dosemu will not access the port.

Regards

Claudia

#3 lore raw

I'm suprised to see that I cannot add [write] permissions to others for the /var/lock dorectory. It just stays at 775. Has anyone else had this or know why? i'm using rh9.

Quoted 29 lines · Claudia Neumann

Am Sonntag, 13. Juli 2003 19:49 schrieb Ralph Alvy:

Quoted 4 lines

I think this may be the last thing I need to get everything I need to run under dosemu ... I can't get access to the modem, which I have connected to my serial port on com 1. I have

Quoted 9 lines
	$_com1 = "/dev/modem"

But when I load dosemu 1.1.5, I see this:

ERROR: tty: lock: (/var/lock/LCK..modem): Permisssion denied

I tried to resolve this by putting myself in the groups uucp and lock, but that fails to solve it.

Hi,

it is not the permission for /dev/ttyS1 but the directory /var/lock must exist and you must have wright permission for this directory, otherwise dosemu will not access the port.

Regards

Claudia

-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

author
#9 lore raw
In reply to Claudia Neumann
Quoted 16 lines · Claudia Neumann

Am Sonntag, 13. Juli 2003 19:49 schrieb Ralph Alvy:

Quoted 4 lines

I think this may be the last thing I need to get everything I need to run under dosemu ... I can't get access to the modem, which I have connected to my serial port on com 1. I have

Quoted 9 lines
	$_com1 = "/dev/modem"

But when I load dosemu 1.1.5, I see this:

ERROR: tty: lock: (/var/lock/LCK..modem): Permisssion denied

I tried to resolve this by putting myself in the groups uucp and lock, but that fails to solve it.

Quoted 7 lines

Hi,

it is not the permission for /dev/ttyS1 but the directory /var/lock must exist and you must have wright permission for this directory, otherwise dosemu will not access the port.

Regards

Claudia

I *have* write permission for that directory, but I can only use the modem under dosemu as root.

#4 lore raw
In reply to Justin Zygmont

Hi there,

Quoted 4 lines · Justin Zygmont

I'm suprised to see that I cannot add [write] permissions to others for the /var/lock dorectory. It just stays at 775. Has anyone else had this or know why? i'm using rh9.

You can, but I think you'll find that in your startup scripts, Red Hat have put a command which sets those permissions at boot time. It's a historical Unix-type thing. You shouldn't need to be doing that to files in /var/lock anyway, it's a terrible security hole.

73,
Ged.

#5 lore raw

Am Montag, 14. Juli 2003 08:28 schrieb Ged Haywood:

Quoted 12 lines

Hi there,

Quoted 3 lines · Justin Zygmont

I'm suprised to see that I cannot add [write] permissions to others for the /var/lock dorectory. It just stays at 775. Has anyone else had this or know why? i'm using rh9.

You can, but I think you'll find that in your startup scripts, Red Hat have put a command which sets those permissions at boot time. It's a historical Unix-type thing. You shouldn't need to be doing that to files in /var/lock anyway, it's a terrible security hole.

You could change the lock-directory in your .dosemurc for example to

$_ttylocks = "/home/user/dosemu/lock"

and the problem with wright permission and security is solved.

Regards

Claudia

#6 lore raw

I got it now, all it was the $ttylocks setting in dosemu.conf. This should be set to /var/lock instead of the default "" which points to the depreciated /usr/spool/uucp directory, that didn't exist.

Quoted 28 lines · Claudia Neumann

Am Montag, 14. Juli 2003 08:28 schrieb Ged Haywood:

Quoted 12 lines

Hi there,

Quoted 3 lines · Justin Zygmont

I'm suprised to see that I cannot add [write] permissions to others for the /var/lock dorectory. It just stays at 775. Has anyone else had this or know why? i'm using rh9.

You can, but I think you'll find that in your startup scripts, Red Hat have put a command which sets those permissions at boot time. It's a historical Unix-type thing. You shouldn't need to be doing that to files in /var/lock anyway, it's a terrible security hole.

You could change the lock-directory in your .dosemurc for example to

$_ttylocks = "/home/user/dosemu/lock"

and the problem with wright permission and security is solved.

Regards

Claudia
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

author
#7 lore raw

Hmmm...doesn't seem to help me. I still get the same error message as usual.

Quoted 44 lines · Justin Zygmont

I got it now, all it was the $ttylocks setting in dosemu.conf. This should be set to /var/lock instead of the default "" which points to the depreciated /usr/spool/uucp directory, that didn't exist.

Quoted 22 lines · Claudia Neumann

Am Montag, 14. Juli 2003 08:28 schrieb Ged Haywood:

Quoted 4 lines

Hi there,

On Sun, 13 Jul 2003, Justin Zygmont wrote:

Quoted 9 lines
Quoted 3 lines

I'm suprised to see that I cannot add [write] permissions to others for the /var/lock dorectory. It just stays at 775. Has anyone else had this or know why? i'm using rh9.

You can, but I think you'll find that in your startup scripts, Red Hat have put a command which sets those permissions at boot time. It's a historical Unix-type thing. You shouldn't need to be doing that to files in /var/lock anyway, it's a terrible security hole.

You could change the lock-directory in your .dosemurc for example to

$_ttylocks = "/home/user/dosemu/lock"

and the problem with wright permission and security is solved.

Quoted 8 lines

Regards

Claudia
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#8 lore raw

this is with rh9, which are you using? What are the permissions for /var and /var/lock?

Quoted 56 lines · Ralph Alvy

Hmmm...doesn't seem to help me. I still get the same error message as usual.

Quoted 41 lines · Justin Zygmont

I got it now, all it was the $ttylocks setting in dosemu.conf. This should be set to /var/lock instead of the default "" which points to the depreciated /usr/spool/uucp directory, that didn't exist.

Quoted 22 lines · Claudia Neumann

Am Montag, 14. Juli 2003 08:28 schrieb Ged Haywood:

Quoted 4 lines

Hi there,

On Sun, 13 Jul 2003, Justin Zygmont wrote:

Quoted 9 lines
Quoted 3 lines

I'm suprised to see that I cannot add [write] permissions to others for the /var/lock dorectory. It just stays at 775. Has anyone else had this or know why? i'm using rh9.

You can, but I think you'll find that in your startup scripts, Red Hat have put a command which sets those permissions at boot time. It's a historical Unix-type thing. You shouldn't need to be doing that to files in /var/lock anyway, it's a terrible security hole.

You could change the lock-directory in your .dosemurc for example to

$_ttylocks = "/home/user/dosemu/lock"

and the problem with wright permission and security is solved.

Quoted 8 lines

Regards

Claudia
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Quoted 5 lines

-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html