That's it!
It works.
Thank you very much.
Daniel.

On Tue, 17 Nov 1998, Kenneth Stephen wrote:

> Daniel,
> 
>       This sounds very much like the situation where `dip` is not suid.
> From the superuser id, do 'chmod u+s /usr/bin/dip' and try again.
> 
>       I dont know if suid is a requirement for `dip` to work (the answer
> is probably yes since the general policy is that only root has write
> access to devices), but that is the only way I could get it to work.
> 
>       As regards your second question, take a look at the linux-newbie
> faq at http://www.linux-learn.org/faqs
> 
> Regards,
> Kenneth
> 
> There is no such thing as luck. 'Luck' is nothing but an absence of bad luck.
> 
> On Tue, 17 Nov 1998, Daniel wrote:
> 
> > Sorry they all are locked and I have permission denied on modem, ttyS0 &
> > cua0.
> > This appenned since I moved from the slackware to Red Hat distribution.
> > 
> > Also when I want to execute a file I have to type  ./ before the command.
> > I wonder why?
> > Thank you again.
> > 
> > On Tue, 17 Nov 1998, Kenneth Stephen wrote:
> > 
> > > Daniel,
> > > 
> > >   If your /dev/modem device is actually a symbolic link to
> > > /dev/ttyS0, try port ttyS0.
> > > 
> > > Regards,
> > > Kenneth
> > > 
> > > There is no such thing as luck. 'Luck' is nothing but an absence of bad luck.
> > > 
> > > On Mon, 16 Nov 1998, Daniel wrote:
> > > 
> > > > When I want to get connected on Internet and use a dip script, if I'm not
> > > > in supervisor mode, I receive the following message:
> > > > 
> > > > >> port modem
> > > > PORT: terminal port set to "modem".
> > > > DIP: tty: lock: (/var/lock/LCK..modem): Permission non accord�e.
> > > > DIP: can't open - problems with locking modem
> > > > 
> > > > I destroyed the file /var/lock/LCK..modem,
> > > > no difference.......
> > > > 
> > > > also with minicom I have this:
> > > > Device /dev/modem is locked.
> > > > 
> > > > How can I be unlocked ?
> > > > Free me please.
> > > > Thank you.
> > > > Daniel.
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > 
> > 
> > 
> 
> 
> 

Reply via email to