I have a debian 1.3.1 system on which I have a modem for
periodic remote access. Dial-in has worked nicely for some
time. However I needed to check/reset the modem
configuration, so I fired up minicom (cu isn't my cup of tea,
and I've previously used minicom to do this, but not on this
syst
As I was used to agetty and minicom cooperating nicely on an ancient Slackware
box, I expected this to work on this much more recent Debian box .
I use mgetty at home, but didn't really want to have to deal with its
complexities for the situation at hand.
The situation's more or less under cont
Miquel van Smoorenburg wrote:
>According to Andrew MacIntyre:
>> As I was used to agetty and minicom cooperating nicely on an
>> ancient Slackware box, I expected this to work on this much more
>> recent Debian box .
>
>That is because that worked with the cua/ttyS devices (kernel based
>locking
On the bo (1.3.1) system I tried this on, I got:
vesta# dpkg -S /sbin/getty
getty: /sbin/getty
Which as I said, lead me up a blind ally.
>From your response, I have just tried:
vesta# dpkg -s getty
Package: getty
Essential: yes
Status: install ok installed
Priority: required
Section: base
Insta
4 matches
Mail list logo
