* Minicom fails
@ 2002-12-19 8:48 Peter
0 siblings, 0 replies; 4+ messages in thread
From: Peter @ 2002-12-19 8:48 UTC (permalink / raw)
To: linux
Hi,
After I run a RH7.3 upgrade I can't access anymore minicom as a user.
I get the following message:
]$ minicom
Device /dev/ttyS0 lock failed: Operation not permitted.
No problem accessing it as su and /dev/ttyS0 is set to chmod a+rw.
How will I get my minicom back as a user?
Thanks & regards
--
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 4+ messages in thread
* Minicom fails
@ 2002-12-19 8:50 Peter
0 siblings, 0 replies; 4+ messages in thread
From: Peter @ 2002-12-19 8:50 UTC (permalink / raw)
To: linux
Hi,
After I run a RH7.3 upgrade I can't access anymore minicom as a user.
I get the following message:
]$ minicom
Device /dev/ttyS0 lock failed: Operation not permitted.
No problem accessing it as su and /dev/ttyS0 is set to chmod a+rw.
How will I get my minicom back as a user?
Thanks & regards
--
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Minicom fails
[not found] <200212190804.04757.sotl155360@earthlink.net>
@ 2002-12-20 7:00 ` Peter
2002-12-20 12:55 ` Frank Roberts - SOTL
0 siblings, 1 reply; 4+ messages in thread
From: Peter @ 2002-12-20 7:00 UTC (permalink / raw)
To: linux-newbie
Peter said:
> After I run a RH7.3 upgrade I can't access anymore minicom as a user.
> I get the following message: ]$ minicom Device /dev/ttyS0 lock failed:
> Operation not permitted.
Thanks Frank!
The first thing I did was reading the man pages after the opening failure. I
got nothing out of it.
What I did now was setting the group of /var/lock to user and I can open
minicom again.
Was this the right way to do it?
Regards
--
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Minicom fails
2002-12-20 7:00 ` Peter
@ 2002-12-20 12:55 ` Frank Roberts - SOTL
0 siblings, 0 replies; 4+ messages in thread
From: Frank Roberts - SOTL @ 2002-12-20 12:55 UTC (permalink / raw)
To: Peter, linux-newbie
If it works you are correct.
Frank
On Friday 20 December 2002 02:00, Peter wrote:
> Peter said:
> > After I run a RH7.3 upgrade I can't access anymore minicom as a user.
> > I get the following message: ]$ minicom Device /dev/ttyS0 lock failed:
> > Operation not permitted.
>
> Thanks Frank!
>
> The first thing I did was reading the man pages after the opening failure.
> I got nothing out of it.
>
> What I did now was setting the group of /var/lock to user and I can open
> minicom again.
>
> Was this the right way to do it?
>
> Regards
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-12-20 12:55 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-12-19 8:50 Minicom fails Peter
[not found] <200212190804.04757.sotl155360@earthlink.net>
2002-12-20 7:00 ` Peter
2002-12-20 12:55 ` Frank Roberts - SOTL
-- strict thread matches above, loose matches on Subject: below --
2002-12-19 8:48 Peter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox