Re STTY
Nathan E Norman <finn@midco.net> wrote:
> "Hey, my system's all FUBAR and I'm pissed off. You jerks at Debian
> hosed it up - *I* didn't do it. Fix it now or I'll really be pissed"
No not at all. Debian 1.3.1 is/was the dogs parts, I loved/love it. I
have spent years with Linux now, and through that period I have used
Slackware <shudder> and Redhat. But then I discovered Debian... Whoooo Heee!
Debian may or may not be too blame for what happened here, but to be honest
I couldn't care less. The point is it *HAS* happened, and it *MUST* be
fixable, since many of you on here say "It works fine" ?
So I was trying to either work out how to use some sort of stty setting (in
/etc/profile perhaps) to correct the problem, or to purge and re-install a
package which might not have installed right.
> There is a dpkg command to reinstall all currently installed packages,
> but I'll be damned if I can remember what it is ...
Thank you, I will investigate this path !
> Sorry my tech support isn't quite up to your expectations. I'll be sure
> to return your money.
If no-one knows the answer then fine? I would have rather got a load of
mails saying "Sorry I can't help" than all the ones I did saying "Works here
great - YOU must have hosed you box".
I *KNOW* it's hosed it someway, I *KNOW* it works for everyone else. What I
really want though is a fix ! OK I know thats a near impossible question to
answer, but hints on contoling packages and the likes wouldn't have gone a
miss :)
Debian is/was the best Linux I have ever seen. But this problem NEEDS to be
cured, if it can't then I have to take steps to work around it. I really do
not want to install from scratch and start again... If I have to do that
then I may as well go back to 1.3.1 and restore from tape. 1.3.1 *IS* the dogs
parts when it comes to Linux. With 2.0 I still have my doubts, but would like
to give it the chance to prove itself before zapping it.
Cheers
--
Nidge Jones
Reply to: