On Mon, Jan 07, 2008 at 12:43:05PM -0500, Scott Gifford wrote:
> joseph lockhart <[EMAIL PROTECTED]> writes:
>
> > ok, checked my computer today and found strange output
> > on ttys1 which i only use for boot messages,
> >
> > [A[Dj[2~[G[Cp;vy[Co[D+ut [Dc +[Ci
--- Scott Gifford <[EMAIL PROTECTED]> wrote:
> joseph lockhart <[EMAIL PROTECTED]>
> writes:
>
> > ok, checked my computer today and found strange
> output
> > on ttys1 which i only use for boot messages,
> >
> > [A[Dj[2~[G[Cp;vy[Co[D+ut [Dc +[C
joseph lockhart <[EMAIL PROTECTED]> writes:
> ok, checked my computer today and found strange output
> on ttys1 which i only use for boot messages,
>
> [A[Dj[2~[G[Cp;vy[Co[D+ut [Dc +[Ci[Dx+ryi[D+
> ri[D+ri[D+rc[C6[D[1~i+ 6[D[1~9[2+i 6[1~[yejsw
>
> [password:
It&#x
On Jan 6, 2008 3:23 PM, joseph lockhart <[EMAIL PROTECTED]> wrote:
> ok, checked my computer today and found strange output
> on ttys1 which i only use for boot messages,
>
> [A[Dj[2~[G[Cp;vy[Co[D+ut [Dc +[Ci[Dx+ryi[D+
> ri[D+ri[D+rc[C6[D[1~i+ 6[D[1~9[2+i 6[1~[yejsw
>
>
ok, checked my computer today and found strange output
on ttys1 which i only use for boot messages,
[A[Dj[2~[G[Cp;vy[Co[D+ut [Dc +[Ci[Dx+ryi[D+
ri[D+ri[D+rc[C6[D[1~i+ 6[D[1~9[2+i 6[1~[yejsw
[password:
no results on google, altavista, or any other search
engine that i could think of
[EMAIL
On Mon, Feb 23, 2004 at 10:31:59AM -0600, Mark Gillingham wrote:
>
>
> Why does dmesg report an extra zero in the ttyS* above (i.e., 00 and
> 01)? Is that my problem? Am I anticipating ttyS0 and ttyS1 and getting
> in actuality ttyS00 and ttyS01? If so do I create /dev/tty
rep tty is:
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
These results check with the BIOS.
My ttyS* devices are:
ls /dev/ttyS*
/dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3
Why does dmesg report an extra zero in the ttyS* above (i.e., 00 and
01)? Is that my pro
On Saturday, February 21, 2004, at 05:30 PM, Bill Marcum wrote:
The BIOS settings for the serial ports should be clearly labeled.
Maybe your internal ports are disabled; try "dmesg | grep tty"
The result is the same as the BIOS settings on a similar box:
ttyS00 at 0x03f8 (irq = 4) is a 16550A
tty
On Thu, Feb 19, 2004 at 04:23:35PM -0600, Mark Gillingham wrote:
> When I issue a setserial or statserial command on ttyS0 or ttyS1, both
> internal ports, the commands hang and I just ^C out. The commands on
> ttyS2 and ttyS3 behave normally. Since I mostly ignore the internal
>
On Thu, Feb 19, 2004 at 04:23:35PM -0600, Mark Gillingham wrote:
> When I issue a setserial or statserial command on ttyS0 or ttyS1, both
> internal ports, the commands hang and I just ^C out. The commands on
> ttyS2 and ttyS3 behave normally. Since I mostly ignore the internal
>
When I issue a setserial or statserial command on ttyS0 or ttyS1, both
internal ports, the commands hang and I just ^C out. The commands on
ttyS2 and ttyS3 behave normally. Since I mostly ignore the internal
serial ports when I installed, I bet I missed something. Something
might be amiss in
2003 at 06:49:15AM +0200, Andrea Tasso wrote:
> > > > hi all,
> > > > pppd does not connect any more (to another pc with null modem cable), it used
> > > > to work perfectly.
> > > > the command
> > > >
> > > > pppd -detach deb
ny more (to another pc with null modem cable), it used to
> > > work perfectly.
> > > the command
> > >
> > > pppd -detach debug crtscts 192.168.6.1:192.168.6.2 lock /dev/ttyS1 38400
> > >
> > > gives no output, and finally exits
> >
mmand
> >
> > pppd -detach debug crtscts 192.168.6.1:192.168.6.2 lock /dev/ttyS1 38400
> >
> > gives no output, and finally exits
> >
> > if I strace it
> >
> > the last string is
> > open("/dev/ttyS1", O_RDWR
> >
> > my
On Wed, Sep 03, 2003 at 06:49:15AM +0200, Andrea Tasso wrote:
> hi all,
> pppd does not connect any more (to another pc with null modem cable), it used to
> work perfectly.
> the command
>
> pppd -detach debug crtscts 192.168.6.1:192.168.6.2 lock /dev/ttyS1 38400
>
&g
hi all,
pppd does not connect any more (to another pc with null modem cable), it used to work
perfectly.
the command
pppd -detach debug crtscts 192.168.6.1:192.168.6.2 lock /dev/ttyS1 38400
gives no output, and finally exits
if I strace it
the last string is
open("/dev/ttyS1", O
On Mon, Dec 16, 2002 at 11:45:51PM -0500, Shawn Lamson wrote:
> On Mon, 16 Dec 2002 20:19:18 -0800
> "jeffrey j wilkman" <[EMAIL PROTECTED]> wrote:
>
> >
> >
> > hi,
> >
> > i accidentally destroyed my /dev/ttyS1 file, the file for my m
On Mon, 16 Dec 2002 20:19:18 -0800
"jeffrey j wilkman" <[EMAIL PROTECTED]> wrote:
>
>
> hi,
>
> i accidentally destroyed my /dev/ttyS1 file, the file for my modem.
> is ther an easy to recover this file?? i just upgraded from potato
> to woody, so i don&#x
hi,
i accidentally destroyed my /dev/ttyS1 file, the file for my modem.
is ther an easy to recover this file?? i just upgraded from potato
to woody, so i don't have even the option of starting over. is there
some way to get a coy of the file?
thank you very much
jeffrey j wi
Marcelo Chiapparini wrote:
>Hi to all!
>
>I am in a bit trouble. I deleted the /dev/ttyS1 file. Now I can't use the
>modem. The file exist in another machine (both of them run potato 2.2r4). How
>can I recover the file? Is a matter of copy the file to a floppy and copy
High,
On Fri, 21 Dec 2001, Marcelo Chiapparini wrote:
> Hi to all!
>
> I am in a bit trouble. I deleted the /dev/ttyS1 file. Now I can't use the
> modem. The file exist in another machine (both of them run potato 2.2r4). How
> can I recover the file? Is a matter of copy
Hi to all!
I am in a bit trouble. I deleted the /dev/ttyS1 file. Now I can't use the
modem. The file exist in another machine (both of them run potato 2.2r4). How
can I recover the file? Is a matter of copy the file to a floppy and copy back
in the first machine?
Thanks in advance fo
Quoting Piotr Krukowiecki ([EMAIL PROTECTED]):
> But let me quote:
>
> > Debian has to be built for people who *do* care, so advice that
> > compromises security is not to be welcomed here
>
> For me it says sth like this:
> Debian is only for users who care about security, so if you don't, we
>
On Fri, 08 Sep 2000, John Hasler wrote:
> Piotrek writes:
> > So say how it should be, but don't say me how i should do it.
>
> When you ask for free help on a mailing list or newsgroup you get the
> answers people see fit to give you. Statements such as this just might
> result in someone who c
Piotrek writes:
> So say how it should be, but don't say me how i should do it.
When you ask for free help on a mailing list or newsgroup you get the
answers people see fit to give you. Statements such as this just might
result in someone who could answer your questions deciding to ignore you
fro
gt; > > >
> > > > > pppd removes g+w from /dev/ttyS1 after it is started. So next time I
> > > > > have
> > > > > to be root to use my modem (and to connect to internet). How to make
> > > > > pppd
> > > > > st
5 22:48 /dev/psaux
crw-rw1 root dialout4, 64 May 5 22:48 /dev/ttyS0
crw-rw1 root dialout 4, 65 May 5 22:48 /dev/ttyS1
crw-rw1 root dialout4, 66 May 5 22:48 /dev/ttyS2
crw-rw1 root dialout4, 67 May 5 22:48 /dev/ttyS3
$ ls -lu
Quoting Piotr Krukowiecki ([EMAIL PROTECTED]):
> On Mon, 04 Sep 2000, David Wright wrote:
>
> > Quoting Mario Olimpio de Menezes ([EMAIL PROTECTED]):
> > > On Mon, 4 Sep 2000, Piotr Krukowiecki wrote:
> > > >
> > > > pppd removes g+w from /
USM Bish writes:
> "wvdial" and other dial scripts like ppp-go, pon etc which finally call
> up pppd, needs to be run with root privileges.
Any member of the 'dip' group can run pon. Root privileges are not needed.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
> Wrong again ;)
> At least with wvdial. With pon/poff it's all ok. i don't have to
> be in group dialout nor have g+w permission on /dev/ttyS1. If
> /dev/ttyS1 is g+w while starting pppd, pppd removes it and puts
> back on exit.
> But if i use wvdial, /dev/ttyS1 h
On Mon, 04 Sep 2000, David Wright wrote:
> Quoting Mario Olimpio de Menezes ([EMAIL PROTECTED]):
> > On Mon, 4 Sep 2000, Piotr Krukowiecki wrote:
> > >
> > > pppd removes g+w from /dev/ttyS1 after it is started. So next time I have
> > > to be root to use
On Mon, 4 Sep 2000, David Wright wrote:
> Quoting Mario Olimpio de Menezes ([EMAIL PROTECTED]):
> > On Mon, 4 Sep 2000, Piotr Krukowiecki wrote:
> > >
> > > pppd removes g+w from /dev/ttyS1 after it is started. So next time I have
> > > to be root to use
Quoting Mario Olimpio de Menezes ([EMAIL PROTECTED]):
> On Mon, 4 Sep 2000, Piotr Krukowiecki wrote:
> >
> > pppd removes g+w from /dev/ttyS1 after it is started. So next time I have
> > to be root to use my modem (and to connect to internet). How to make pppd
On Mon, 4 Sep 2000, Piotr Krukowiecki wrote:
> Hi
>
> pppd removes g+w from /dev/ttyS1 after it is started. So next time I have
> to be root to use my modem (and to connect to internet). How to make pppd
> stop removing it ?
better: add users that need to use modem t
Quoting Piotr Krukowiecki ([EMAIL PROTECTED]):
> Hi
>
> pppd removes g+w from /dev/ttyS1 after it is started. So next time I have
> to be root to use my modem (and to connect to internet). How to make pppd
> stop removing it ?
You don't want to do that. You want to allow
Hi
pppd removes g+w from /dev/ttyS1 after it is started. So next time I have
to be root to use my modem (and to connect to internet). How to make pppd
stop removing it ?
--
Peter
irc: #Debian.pl
A long time ago, in a galaxy far, far way, someone said...
> When I tried wvdial for the first time (it was set up for me during
> the Dialup installation), it said, "Cannot open /dev/ttyS1: Permission
> denied."
>
> I know a little something about permissions, but I do
>>>>> "Lane" == Lane Lester <[EMAIL PROTECTED]> writes:
Lane> When I tried wvdial for the first time (it was set up for me
Lane> during the Dialup installation), it said, "Cannot open
Lane> /dev/ttyS1: Permission denied."
You probab
When I tried wvdial for the first time (it was set up for me during
the Dialup installation), it said, "Cannot open /dev/ttyS1: Permission
denied."
I know a little something about permissions, but I don't know about
that one!
Lane
Lane Lester / Madison County, Georgia USA
Something, it seems that efax is the culprit, keeps changing the
permissions on /dev/ttyS1. The following illustrates the problem (alias
l="ls -la --color=tty"):
-
$groups
jhspies adm mail news dialout fax floppy audio dip cdskrywers
jhspies-22
On Tue, May 25, 1999 at 06:15:41PM -0400, Bob Hilliard wrote:
> Ingo Hohmann <[EMAIL PROTECTED]> writes:
<...>
> > one of the cron scripts seems to change access rights
> > on /dev/ttyS1 once in a while to
<...>
> pppd changes /dev/ttyS1 (if that is the mo
Ingo Hohmann <[EMAIL PROTECTED]> writes:
> Hi,
>
> one of the cron scripts seems to change access rights
> on /dev/ttyS1 once in a while to
>
> crw-r- 1 root dialout4, 65 May 25 19:40 /dev/ttyS1
>
> (should have write access for dialout)
>
>
Hi,
one of the cron scripts seems to change access rights
on /dev/ttyS1 once in a while to
crw-r- 1 root dialout4, 65 May 25 19:40 /dev/ttyS1
(should have write access for dialout)
Does someone know, which script does this?
thank you in advance
Ingo
--
Ingo Hohmann, Otto
David Wright writes:
> In the first instance, fuser /dev/ttyS1 will tell you the PID of any
> process using it. Secondly, check it's crw-rw 1 root dialout 4, 65
> Mar 3 17:20 /dev/ttyS1 and that you're in dialout (type groups).
Check /var/lock for stale lock files.
--
Quoting Robert King ([EMAIL PROTECTED]):
> Hi,
>I'm having trouble getting my serial line to work on a 486 at home. It
> has a working slackware install on one disk and I'm endeavouring to
> install hamm on a new disk. Whenever I try anything with ttyS1, I'm told
Hi,
I'm having trouble getting my serial line to work on a 486 at home. It
has a working slackware install on one disk and I'm endeavouring to
install hamm on a new disk. Whenever I try anything with ttyS1, I'm told
its already in use. How do I work out what's causing thi
lowing lines:
> >
> > pppd 2.3.5 started by root, uid 0
> > tcgetattr: input/output error (5)
> > Exit.
> >
> > Ok, I went back a few steps. I pulled down the PPP-HowTo and slog
> > through the advice it has (which isn't 100% the same as t
[EMAIL PROTECTED] writes:
> Perhaps your modem is a PLUG and PLAY modem or a winmodem of some thought ?
Sigh. What's frustrating is this isn't the first person to ask this
question. As I said in my post:
> > I'm trying to get a ppp connection running on an external modem
> > plugged into COM2 o
t error (5)
> Exit.
>
> Ok, I went back a few steps. I pulled down the PPP-HowTo and slog
> through the advice it has (which isn't 100% the same as the default Hamm
> setup). I discovered that using Minicom, I didn't get any response to AT
> commands sent to /dev/ttyS
#x27;t 100% the same as the default Hamm
setup). I discovered that using Minicom, I didn't get any response to AT
commands sent to /dev/ttyS1.
I rebooted the system and use Lilo to boot MS-Dog. Kermit saw a modem on
COM2 and I was even able to use it to dial my ISP and transfer some more
stuf
If my ppp connection drops (due to phone line disconnect) I cannot
anymore
use /dev/ttyS1 (e.g. for reconnecting ppp).
Any attempt to touch the device will hand, like
stty -a
Bob Hilliard writes:
> I have been troubled with intermittently changed permissions on
> /dev/ttyS1,...
> Why does pppd find it necessary to fiddle with these permissions
> anyway?
Security, I assume. Perhaps you could have pppd talk to a symlink?
--
John Hasler
[EMAIL PROTECTED]
I have been troubled with intermittently changed permissions on
/dev/ttyS1, and have been searching for some cron job that might have
caused it. Your comments about the pppd source gave me a clue. I
thought that if pppd changes these permissions, then restores them on
exit, an abnormal exit
My permissions for /dev/ttyS1 are normally:
bob:vc-2:bob>ls -l /dev/ttyS1
crw-rw 1 root dialout4, 65 Mar 31 19:28 /dev/ttyS1
The group rw is necessary for minicom to access the modem. From
time to time minicom complains that it cannot access /dev/ttyS1.
Whenever t
If I set pppd to dial out on anything but ttyS1, it won't route.
The modem will dial and connect, but the routing table is not updated.
What have I forgotten to change?
Dave 'Kill a Cop' Cinege (ak
On Sun, 6 Oct 1996, Bill Roman wrote:
> > I've tried enabling the port by adding the proper entry to inittab
> > (working from memory at the moment) as follows:
> >
> > S1:234:respawn:/etc/getty ttyS1 DT9600 vt100
>
> Note that executables have been banish
> > I've tried enabling the port by adding the proper entry to inittab
> > (working from memory at the moment) as follows:
> >
> > S1:234:respawn:/etc/getty ttyS1 DT9600 vt100
>
> long time. Try /sbin/getty, and you may get sufficient functionality
> w
Kevin Traas wrote:
>
> I've tried enabling the port by adding the proper entry to inittab
> (working from memory at the moment) as follows:
>
> S1:234:respawn:/etc/getty ttyS1 DT9600 vt100
Note that executables have been banished from /etc by FSSTND for a
long time. Try
t
> >to do things the other way around (for several reasons) and I can't.
> >Being able to do it one way indicates the cable is fine.
> >
> >I've read the Serial HOWTO.
> >
> >I've tried enabling the port by adding the proper entry to inittab
>
to do it one way indicates the cable is fine.
>
>I've read the Serial HOWTO.
>
>I've tried enabling the port by adding the proper entry to inittab
>(working from memory at the moment) as follows:
>
>S1:234:respawn:/etc/getty ttyS1 DT9600 vt100
>
>I then ran "
I've read the Serial HOWTO.
I've tried enabling the port by adding the proper entry to inittab
(working from memory at the moment) as follows:
S1:234:respawn:/etc/getty ttyS1 DT9600 vt100
I then ran "init q". Running "ps la" didn't show getty running on S1.
On Thu, 19 Sep 1996, Ed Down wrote:
> I'm trying to configure my modem and, as recommended in the Serial-HOWTO,
> I've been using kermit to test it out. Problem is that /dev/ttyS1, which
> is the serial port my modem is on, seems to only allow root access. Anyone
> recommen
Ed> I'm trying to configure my modem and, as recommended in the
Ed> Serial-HOWTO, I've been using kermit to test it out. Problem is that
Ed> /dev/ttyS1, which is the serial port my modem is on, seems to only
Ed> allow root access.
Add yourself to the "d
I'm trying to configure my modem and, as recommended in the Serial-HOWTO,
I've been using kermit to test it out. Problem is that /dev/ttyS1, which
is the serial port my modem is on, seems to only allow root access. Anyone
recommend a fix? Also any tips on mgetty setup would be appreciated.
Ed
64 matches
Mail list logo
