test
test
Re: gzip and dpkg problem
On Thu, 6 Jun 1996, Ian Jackson wrote: > > Please do tell us what the problem is if you find out. Telling us > which ways of logging in cause the problem and which don't will help > us a lot :-). > Well, I just checked and even the latest(?) version, 2.0.7i, of getty_ps sets the SIGPIPE signal to SIG_IGN. So it likes like we need to just stay away from getty_ps altogether (at least on ttys where pipes will be used). Leland Lucius __ Y_ a_ m_ b_ o_ | The leanest, meanest, fightinest sweet tater on Earth! oo o oo o o | o o o | [EMAIL PROTECTED] o ooo o | -- -- -- -- -- -- | http://www.millcomm.com/~llucius (maybe one day)
Re: gzip and dpkg problem
Hi, OK, haven't done much yet, but here's what I've done to check the getty/gzip/dpkg problem. On Thu, 6 Jun 1996, Ian Jackson wrote: > This is a bug in one of: > Your inetd, telnetd, rlogind, if you're logging in over the > network (some versions of the Debian netbase and/or netstd > packages had this problem). I've never tried to use dpkg this way. > Your shell (I know of no shells that cause this problem). I'm using bash, so if it's bash I'm really screwed... but it's not (keep reading) > The getty you're using. > (Some versions of getty_ps are known to have this problem.) This looks like the problem! OK, I can't try this on the computer I mentioned in my first message, cause I had to have it running so I plopped slackware on it-will put debian back on tonight. So instead, on my other debian comp, here's what I did: my /etc/inittab 1:2345:respawn:/sbin/agetty 9600 tty1 2:23:respawn:/sbin/agetty 9600 tty2 3:23:respawn:/sbin/getty_ps tty3 9600 linux 4:23:respawn:/sbin/getty_ps tty4 9600 linux 5:23:respawn:/sbin/getty_ps tty5 9600 linux So using both, here's what happened: cat /dev/zero | true on tty1 and tty2 : got "Broken pipe" error msg on tty3+ : got "cat: write error: Broken pipe" error msg using dpkg to install samba-1.9.14.deb (this was the package I was trying to install on the other computer that prompted my 1st message) on tty1 and tty2 : did ok on tty3+ : got same error message about gzip -dc so this looks like fairly conclusive evidence for me. > The login you're using (I know of no problem here). Can't help there. Except for the getty differences, I'm just using bash on a tty, no su, no telnet, nothing special. > Any program which started one of the above, or which is in > the calling chain for dpkg. Can't help again. OK, there was also a message about this problem happening in an xterm/rxvt I tried using tcsh as root in an xterm and did get errors, but that was due to my tcsh configuration errors rather than the one that gives you the gzip -dc error message. So I can't really say whether this would be the same type problem as mine. I'm very ignorant about all the inner workings of terminals, getty's, etc., so I did try launching X from both agetty and getty_ps, but that didn't seem to matter either. Well, from my end, the getty issue seems to be where the problem was coming from. Thanks for everyone's help! That problem was really bugging me. If anyone has any other tests they'd like for me to run, just let me know and I'd be happy to help. -Paul Schoenly Auburn University [EMAIL PROTECTED]
login and bash on a hardwired terminal.
Thanks to Dirk and Guy, I got getty running on ttyS1 to a Data General terminal (ok, ok, but I got it for free. In fact I have 6 of them) but I still have problems. Pressing return on the terminal causes getty to put up the login message and prompt, just as it should. After entering a user name (getty kicks off login) a short line of garbage that looks like it would like to say Password but actually says: P8^w'd and then moves up to the previous line and prints: dwarf (the user name) entering the password for dwarf at this point creates a spew of reverse video spam across several lines and eventually produces a reverse video prompt. All input typed at the keyboard from this point on is reverse video. Anything that I type is displayed ok on the terminal. Anything that bash returns to the terminal is hopeless garbage. I have tried several terminal types (setting TERM=vt100|tty does no good) What do I need to do to get login and bash to work? TIA, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Re: login and bash on a hardwired terminal.
On Thu, 6 Jun 1996, Dale Scheetz wrote: > Thanks to Dirk and Guy, I got getty running on ttyS1 to a Data General > terminal (ok, ok, but I got it for free. In fact I have 6 of them) but I > still have problems. Install ncurses-term, and use one of these terminal types. $ toe | grep -i 'data general' dg200 data general dasher 200 dg460-ansi Data General Dasher 460 in ANSI-mode dg6053 data general 6053 dg211 Data General d211 dg450 data general 6134 Guy
1.1-Beta install problem with Buslogic controller
I was trying to install the 1.1-Beta of Debian Linux and my system hung during the intial boot. I was using the Jun 3 version of boot1440.bin. My system is a 100 MHz Pentium PCI box with 32 MB RAM. It has an Award Bios. I have a Buslogic BT-956C PCI Wide SCSI Host Adapter with a Fujitzu 2 GB hard disk (it has 2075 cylinders). Boot finds my Buslogic controller and says it is initialized succesfully. It detects the Fujitzu drive. The last line is: Detected scsi disk sda at scsi0, channel 0, id 0, lun 0 It then hangs with the drive light on. I also have a scsi cd-rom and tape drive installed. I was surprised that it claims: scsi0: Target 0: Synchronous at 10.0 mega-transfers/second I thought the 956C was a wide FAST scsi controller that ran at 20 megabits per second. Is that the problem? Or is it the fact that DOS (I have a msdos partition on /dev/sda1) thinks it has only 1024 cylinders? I know the machine is okay because I had been using it to run a Slackware version of Linux with kernel 1.2.13. Also the Slackware 3.0.3 boot disk recognizes the drive proberly and will allow me to boot. I quit after fdisk'ing the drive because I decided I wanted a more upgradable system. Using the old slackware install I never could get LILO to work but Loadlin was fine. Please don't tell me I must use Slackware or Red Hat. Larry Loos Show-Me Nete-mail: [EMAIL PROTECTED] 1417 N Henderson http://www.showme.net/ Cape Girardeau, MO 63701 314/334-9322
Re: login and bash on a hardwired terminal.
On Thu, 6 Jun 1996, Dale Scheetz wrote: > Thanks to Dirk and Guy, I got getty running on ttyS1 to a Data General > terminal (ok, ok, but I got it for free. In fact I have 6 of them) but I > still have problems. > Pressing return on the terminal causes getty to put up the login message > and prompt, just as it should. After entering a user name (getty kicks off > login) a short line of garbage that looks like it would like to say > Password but actually says: > > P8^w'd > > and then moves up to the previous line and prints: > > dwarf (the user name) > > entering the password for dwarf at this point creates a spew of reverse > video spam across several lines and eventually produces a reverse video > prompt. All input typed at the keyboard from this point on is reverse > video. Anything that I type is displayed ok on the terminal. Anything that > bash returns to the terminal is hopeless garbage. > > I have tried several terminal types (setting TERM=vt100|tty does no good) > > What do I need to do to get login and bash to work? > Maybe you could nose around in /etc/termcap and find something that has to do with Data General. vt100 probably isn't going to help you. Regards, Eric
Re: printing in debian/unix is hard...
Carlos Carvalho ([EMAIL PROTECTED]) wrote: : using apsfilter. It's more flexible than magicfilter, btw. The config Please explain this. Last time I used "apsfilter", it was horrible to set up (that was more than 1 year ago). Winfried
Re: 1.1-Beta install problem with Buslogic controller
Larry Loos <[EMAIL PROTECTED]>: > I was surprised that it claims: > scsi0: Target 0: Synchronous at 10.0 mega-transfers/second > I thought the 956C was a wide FAST scsi controller that ran at 20 > megabits per second. The transfer number is correct. It does the same number of transfers per second as the narrow devices, but moves twice as much data in each transfer. Of course this is only to "wide" devices. > I know the machine is okay because I had been using it to run a > Slackware version of Linux with kernel 1.2.13. OK, I have appended a long list of driver configuration arguments to the end of this message. The driver is different since 1.2.13 . Please try to use the arguments to disable stuff like tagged queueing. You would use them at the "boot: " prompt of the installation floppy, and you would have to edit /etc/lilo.config to put them in your LILO configuration or give them as arguments to LOADLIN. IF you can't figure it out, please write to Leonard N. Zubkoff at <[EMAIL PROTECTED]>. He is the author of the driver, and he wants to know about any cases where it does not work. Even if you do figure it out, it might be a good idea to tell him what you had to do. > Using the old slackware install I never could get LILO to work but > Loadlin was fine. Sometimes this is a BIOS problem. If LILO still doesn't work, try to use it on a partition that is all below 1024 cylinders. > Please don't tell me I must use Slackware or Red Hat. They don't yet offer the 2.0 kernel yet and we do, that's all. Falling back to an older kernel is easy enough to do with Debian, but I bet you will be able to work around this. Thanks Bruce /* BusLogic_Setup handles processing of Kernel Command Line Arguments. For the BusLogic driver, a Kernel command line entry comprises the driver identifier "BusLogic=" optionally followed by a comma-separated sequence of integers and then optionally followed by a comma-separated sequence of strings. Each command line entry applies to one BusLogic Host Adapter. Multiple command line entries may be used in systems which contain multiple BusLogic Host Adapters. The first integer specified is the I/O Address at which the Host Adapter is located. If unspecified, it defaults to 0 which means to apply this entry to the first BusLogic Host Adapter found during the default probe sequence. If any I/O Address parameters are provided on the command line, then the default probe sequence is omitted. The second integer specified is the Tagged Queue Depth to use for Target Devices that support Tagged Queuing. The Queue Depth is the number of SCSI commands that are allowed to be concurrently presented for execution. If unspecified, it defaults to 0 which means to use a value determined automatically based on the Host Adapter's Total Queue Depth and the number, type, speed, and capabilities of the detected Target Devices. For Host Adapters that require ISA Bounce Buffers, the Tagged Queue Depth is automatically set to BusLogic_TaggedQueueDepth_BB to avoid excessive preallocation of DMA Bounce Buffer memory. Target Devices that do not support Tagged Queuing use a Queue Depth of BusLogic_UntaggedQueueDepth. The third integer specified is the Bus Settle Time in seconds. This is the amount of time to wait between a Host Adapter Hard Reset which initiates a SCSI Bus Reset and issuing any SCSI Commands. If unspecified, it defaults to 0 which means to use the value of BusLogic_DefaultBusSettleTime. The fourth integer specified is the Local Options. If unspecified, it defaults to 0. Note that Local Options are only applied to a specific Host Adapter. The fifth integer specified is the Global Options. If unspecified, it defaults to 0. Note that Global Options are applied across all Host Adapters. The string options are used to provide control over Tagged Queuing and Error Recovery. If both Tagged Queuing and Error Recovery strings are provided, the Tagged Queuing specification string must come first. The Tagged Queuing specification begins with "TQ:" and allows for explicitly specifying whether Tagged Queuing is permitted on Target Devices that support it. The following specification options are available: TQ:DefaultTagged Queuing will be permitted based on the firmware version of the BusLogic Host Adapter and based on whether the Tagged Queue Depth value allows queuing multiple commands. TQ:Enable Tagged Queuing will be enabled for all Target Devices on this Host Adapter overriding any limitation that would otherwise be imposed based on the Host Adapter firmware version. TQ:DisableTagged Queuing will be disabled for all Target Devices on this Host Adapter. TQ: Tagged Queuing wil
F77 has gone missing?
I just went back to working on Octave and don't seem to have F77 any more. I have been keeping pretty up to date on the devel section. Anyone know what happened to it? TIA, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Re: login and bash on a hardwired terminal.
On Thu, 6 Jun 1996, Guy Maor wrote: > On Thu, 6 Jun 1996, Dale Scheetz wrote: > > > Thanks to Dirk and Guy, I got getty running on ttyS1 to a Data General > > terminal (ok, ok, but I got it for free. In fact I have 6 of them) but I > > still have problems. > > Install ncurses-term, and use one of these terminal types. > > $ toe | grep -i 'data general' > dg200 data general dasher 200 > dg460-ansi Data General Dasher 460 in ANSI-mode > dg6053 data general 6053 > dg211 Data General d211 > dg450 data general 6134 > I installed ncurses-term-1.9.9e-1.deb but when I do the toe above I get: infocmp: can't open terminfo file BUGS. Any Ideas? Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Re: F77 has gone missing?
Dale Scheetz writes: Dale> I just went back to working on Octave and don't seem to have F77 any Dale> more. I have been keeping pretty up to date on the devel Dale> section. Anyone know what happened to it? There never was one. Take your pick among f2c with fort77 or g77. -- Dirk Eddelb"uttel http://qed.econ.queensu.ca/~edd
Re: login and bash on a hardwired terminal.
On Fri, 7 Jun 1996, Dale Scheetz wrote: > I installed ncurses-term-1.9.9e-1.deb but when I do the toe above I get: > > infocmp: can't open terminfo file BUGS. toe is Table Of Entries. It just lists all the available terminfo entries with a description. If you ran it with no options and it gave you this error, that means you have a file called 'BUGS' somewhere in your /usr/lib/terminfo tree. toe couldn't parse it because it wasn't a terminfo file. Go look for this file BUGS, and see what package is generating it. It's not in ncurses-term-1.9.9e-1. Regarding your terminal, match the model # with one of those terminals and use that as your TERM setting. Guy
Re: F77 has gone missing?
On Fri, 7 Jun 1996 [EMAIL PROTECTED] wrote: > > Dale Scheetz writes: > Dale> I just went back to working on Octave and don't seem to have F77 any > Dale> more. I have been keeping pretty up to date on the devel > Dale> section. Anyone know what happened to it? > > There never was one. Take your pick among > f2c with fort77 > or > g77. > I ended up making a link to g77 and things work better. Thanks, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Re: login and bash on a hardwired terminal.
On Fri, 7 Jun 1996, Guy Maor wrote: > On Fri, 7 Jun 1996, Dale Scheetz wrote: > > > I installed ncurses-term-1.9.9e-1.deb but when I do the toe above I get: > > > > infocmp: can't open terminfo file BUGS. > > toe is Table Of Entries. It just lists all the available terminfo > entries with a description. > > If you ran it with no options and it gave you this error, that means > you have a file called 'BUGS' somewhere in your /usr/lib/terminfo > tree. toe couldn't parse it because it wasn't a terminfo file. > > Go look for this file BUGS, and see what package is generating it. > It's not in ncurses-term-1.9.9e-1. Here's the 'ls -a /usr/lib/terminfo' . .. 0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z a b c d e f g h i j k l m n o p q r s t terminfo u v w x y z > > Regarding your terminal, match the model # with one of those terminals > and use that as your TERM setting. > I looked in /etc/termcap (is this the right place?) and found dg460-ansi. When I added this to the line in inittab for getty and -HUP init the results of the login are exactly the same. Am I doing this right? It acts like the termtype is being totally ignored, or at least not passed to login and bash. Is there any way that I can check the termtype of this process from the console? That is, can I find out what termtype the bash on ttyS1 is from a root login at the console? TIA, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Re: F77 has gone missing?
Dale> I ended up making a link to g77 and things work better. I wouldn't do that. Whenever I compiled octave here, ./configure was perfectly capable of working with either f2c or g77, maybe with the help of a --with-f2c argument, but that's about it. If you make a link f77, one program one day will think it's native Fortran which it is not. -- Dirk Eddelb"uttel http://qed.econ.queensu.ca/~edd
Re: login and bash on a hardwired terminal.
On Fri, 7 Jun 1996, Dale Scheetz wrote: > Here's the 'ls -a /usr/lib/terminfo' Why did you send me that? The BUGS file is probably in one of those subdirs. Since I don't want an ls -R /usr/lib/terminfo in my mbox, I'll reveal the magic incantation 'find /usr/lib/terminfo -name BUGS'. > I looked in /etc/termcap (is this the right place?) no. ncurses uses terminfo. > Is there any way that I can check the termtype of this process from the > console? cat /proc/xxx/environ | xargs -0n1 will you show you the environment of pid xxx. grep for TERM. Guy
1.1 upgrade?
Where are current instructions on upgrading from debian 0.93 to 1.1 ? --Zachary
Re: 1.1 upgrade?
On Fri, 7 Jun 1996, Zachary DeAquila wrote: > > Where are current instructions on upgrading > from debian 0.93 to 1.1 ? > The notes and upgrade script that I wrote will soon be available in debian/upgrade. Until then, you can find them at: ftp://dwarf.polaris.net/debian/upgrade This site is on-line from 10am til 2pm and 7pm til 10pm weekdays. I will make an anouncement when they get to the mirrors, after I move them. Luck, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
EMAIL! HELP!
Hi everyone, I am having terrible email problems. It seems my email works only 50% of the time, one of three things happen each time i send/receive an email (1) I get it (2) It disappears into oblivion (3)or i get this message Date: Sat, 8 Jun 96 01:57 EST From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: mail failed, returning to sender |- Message log follows: -| no valid recipients were found for this message |- Message text follows: | Received: by electric.rain.aic.net.au id <[EMAIL PROTECTED]> (Debian /\oo/\ Smail3.1.29.1 #29.33); Sat, 8 Jun 96 01:57 EST Message-Id: <[EMAIL PROTECTED]> Date: Sat, 8 Jun 96 01:57 EST From: kaneda (Mikiel Mifsud) This message is telling me iam sending the message to myself, which iam not. I am using smail and pine and havnt had problems (i hope) until recently. The only thing that could be the problem (?) is that i have a softlink from my mailbox in /var/spool to my home directory (because my / is full) ANY help MUCH appreciated PS i tried purging and reinstalling pine/smail/mailx to no avail:( -- __o/\ Michael Mifsud -- `\ < /\/ \_On parole from Uni Of Wollongong Penitentiary -- ___( )/( )___/ [EMAIL PROTECTED]
Re: login and bash on a hardwired terminal.
> Dale Scheetz <[EMAIL PROTECTED]> writes: > On Fri, 7 Jun 1996, Steve Preston wrote: >> One explanation that would fit this behavior is that your terminal >> is configured to expect more stop bits than the linux box is >> sending. > This is a very nice idea, except that it ignores the fact that getty > can print the login message to the terminal just fine. It is only > login and bash that don't seem to talk right. I don't see how getty > could send slow enough to not error and login not. They are both > using the same driver, aren't they? Yes, they use the same driver, but your problem starts when getty exec's login. So I suspect that login is changing the characteristics of the tty. I just looked at the termios manpage, and it is possible to set the number of stop bits to 1 or 2 (see the CSTOPB constant). It is also possible to set the number of databits (see the CSIZE constant) to anything from 5 to 8. It could be that getty sets csize and cstopb to liberal values, like 8 data bits and 2 stop bits, and login sets one and/or the other to smaller values. >From bash or whatever shell, you can try saying stty cs8 cstopb -- Steve Preston ([EMAIL PROTECTED])
Re: big problems with installation
> > BTW: When will 1.1 be released? > > I am uploading yet another pass at the installation floppies today. > We're also dealing with some FTP site problems. I'm going to make a new > "stable" archive this week, and will let that propogate out to all of > the FTP mirrors. We then will give it a few more days of testing and make > the release. > By then, Linux 2.0 should already been released.
Re: login and bash on a hardwired terminal.
On Fri, 7 Jun 1996, Steve Preston wrote: > One explanation that would fit this behavior is that your terminal is > configured to expect more stop bits than the linux box is sending. > > When you are typing and the linux box is echoing, there are long > pauses (relative to a single bit time) between each character. With > these pauses, it is irrelevant how many stop bits the linux box sends, > since the stop bits blend in with the pause. That is, the pause after > a character consists of a bunch of extra stop bits. > > However, when the linux box is sending characters as fast as it can, > then the start bit of the next character follows immediately after > however many stop bits were sent previously. > > If the receiver is expecting 2 stop bits, and the linux box is only > sending 1, then the receiver will detect framing errors or, if it > ignores framing errors, it will simply get out of sync. That is why > you see only six characters instead of the 9 in the "Password:" > prompt. > This is a very nice idea, except that it ignores the fact that getty can print the login message to the terminal just fine. It is only login and bash that don't seem to talk right. I don't see how getty could send slow enough to not error and login not. They are both using the same driver, aren't they? Thanks for the idea, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Will Debian 1.1 have emacs-19.31?
Will the officially release Debian 1.1 include emacs-19.31? It would be nice since I've converted our SGI and Convex machines already and I'd like to run the same version on the soon to be installed Debian workstations. -- David M. Cooke [EMAIL PROTECTED]
boot floppy problems
I've refrained from getting into the internals of "dialog", but it does not look as if I have any choice. The core dump in "modconf" and the suppression of character echo in the boot floppy are both caused by a (reasonably simple) bug in dialog concerned with its trying to render a string that is too wide for its window. Thus, I'll fix that this weekend and release a new boot floppy set. Thanks Bruce -- Pixar's "Toy Story": Over 1/3 Billion dollars world box office so far. Bruce Perens AB6YM [EMAIL PROTECTED]http://www.hams.com/
Re: ghostscript 3.53
It is the Aladdin version of gs you want. It is in the non-free directory. --Derek Lee
Re: login and bash on a hardwired terminal.
> Dale Scheetz <[EMAIL PROTECTED]> writes: > Thanks to Dirk and Guy, I got getty running on ttyS1 to a Data General > terminal (ok, ok, but I got it for free. In fact I have 6 of them) but I > still have problems. > Pressing return on the terminal causes getty to put up the login message > and prompt, just as it should. After entering a user name (getty kicks off > login) a short line of garbage that looks like it would like to say > Password but actually says: > P8^w'd > and then moves up to the previous line and prints: > dwarf (the user name) > entering the password for dwarf at this point creates a spew of reverse > video spam across several lines and eventually produces a reverse video > prompt. All input typed at the keyboard from this point on is reverse > video. Anything that I type is displayed ok on the terminal. Anything that > bash returns to the terminal is hopeless garbage. One explanation that would fit this behavior is that your terminal is configured to expect more stop bits than the linux box is sending. When you are typing and the linux box is echoing, there are long pauses (relative to a single bit time) between each character. With these pauses, it is irrelevant how many stop bits the linux box sends, since the stop bits blend in with the pause. That is, the pause after a character consists of a bunch of extra stop bits. However, when the linux box is sending characters as fast as it can, then the start bit of the next character follows immediately after however many stop bits were sent previously. If the receiver is expecting 2 stop bits, and the linux box is only sending 1, then the receiver will detect framing errors or, if it ignores framing errors, it will simply get out of sync. That is why you see only six characters instead of the 9 in the "Password:" prompt. I don't know if ttyS1 can be configured to send more stop bits. Perhaps your terminal can be configured to expect fewer. -- Steve Preston ([EMAIL PROTECTED])
Re: Will Debian 1.1 have emacs-19.31?
David M Cooke writes: David> Will the officially release Debian 1.1 include emacs-19.31? [EMAIL PROTECTED]:~> emacs --version 19.31.1 [EMAIL PROTECTED]:~> cat /etc/debian_version 1.1 Debian 1.1 is in official beta-test and can be installed safely. Expect the official release Real Soon Now (TM). Emacs-19.31 seems a little more alert than 19.30. Nice job, Mark! -- Dirk Eddelb"uttel http://qed.econ.queensu.ca/~edd
ghostscript 3.53
I know that gs 3.53 is out for a while but I couldn't find it in the debian ftp site. Since only version 3 or later supports my printer (canon BJC 600), can anyone tell me where to find the deb file?
Re: login and bash on a hardwired terminal.
On Fri, 7 Jun 1996, Guy Maor wrote: > On Fri, 7 Jun 1996, Dale Scheetz wrote: > > > Here's the 'ls -a /usr/lib/terminfo' Ooops, how dull of me :-) > > Why did you send me that? The BUGS file is probably in one of those > subdirs. Since I don't want an ls -R /usr/lib/terminfo in my mbox, > I'll reveal the magic incantation 'find /usr/lib/terminfo -name BUGS'. > This yields nothing. There is no BUGS file in and subs of /usr/lib/terminfo.? > > I looked in /etc/termcap (is this the right place?) > > no. ncurses uses terminfo. > /usr/lib/termifo or /etc/terminfo? These are conciderably different. /etc/terminfo only has a (ansi) d (dump) l (linux) s (sun) v (vtxxx) and x (xterm...) > > Is there any way that I can check the termtype of this process from the > > console? > > cat /proc/xxx/environ | xargs -0n1 > will you show you the environment of pid xxx. grep for TERM. > This works! It tells me that the bash running on ttyS1 is, in fact, running with the termtype passed by getty. However, none of the termtypes I have tried have made any difference at all! I have tried: ansi, dumb, dg6134, and dg640-ansi with no effect at all. I would suspect the terminal, except getty writes cleanly to the terminal. It is only login and bash that misbehave. Still banging my head, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Re: Will Debian 1.1 have emacs-19.31?
[EMAIL PROTECTED] wrote: > > David M Cooke writes: > David> Will the officially release Debian 1.1 include emacs-19.31? > > [EMAIL PROTECTED]:~> emacs --version > 19.31.1 Where is the .deb file? I checked unstable/binary/editors and found: -r--r--r-- 1 daemon ftp-linu 5071046 Mar 7 03:40 emacs-19.30-1.deb -r--r--r-- 1 daemon ftp-linu 2806228 Mar 7 03:42 emacs-el-19.30-1.deb thanks. -- David M. Cooke [EMAIL PROTECTED]
Re: Will Debian 1.1 have emacs-19.31?
David> Where is the .deb file? Oh, sorry, I must have taken emacs-19.31 from the developers system. The public archive lags a little, mostly a day, sometimes a little longer. Expect to see emacs-19.31 in unstable/binary/editors any time now. -- Dirk Eddelb"uttel http://qed.econ.queensu.ca/~edd
Re: login and bash on a hardwired terminal.
On Fri, 7 Jun 1996, Steve Preston wrote: > >From bash or whatever shell, you can try saying > stty cs8 cstopb Ok! We are narrowing the field. The above command locks up the terminal big time, but... stty cs7 cstopb fixes it! Now the question is: How do I get login to leave the stop bits alone? I can put the above command into .bashrc, but this will not fix login and I will still get the bunged password prompt. Looks like it's time to talk with Guy :-) Thanks for all the help, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Problem with telnet login
I recently upgraded one of our machine's base packages and other packages to the latest 1.1 versions. Now when attempting to telnet to the machine, a connection is established, the issue file is printed and then we see this: You must exec login from the lowest level shell. Connection closed by foreign host. Anyone have a clue on what might be the cause of this? Any suggestion would be helpful. Thanks. -- Brian Sulcer <[EMAIL PROTECTED]> | Gibson USA System Administrator | Nashville, Tennessee Worldwide Net Services | (615) 871-4500 ext 275
Re: login and bash on a hardwired terminal.
On Fri, 7 Jun 1996, Dale Scheetz wrote: > This yields nothing. There is no BUGS file in and subs of > /usr/lib/terminfo.? I'm only assuming there is because of your weird error. I got the same error when I manually created a file called BUGS. > /usr/lib/termifo or /etc/terminfo? These are conciderably different. > /etc/terminfo only has a (ansi) d (dump) l (linux) s (sun) v (vtxxx) and x > (xterm...) /usr/lib/terminfo is the full terminfo library, but may not be available on boot. /etc/terminfo presumably contains the console entry. If you boot off this terminal, be sure and copy the right terminfo entry into here. > I would suspect the terminal, except getty writes cleanly to the terminal. > It is only login and bash that misbehave. You told me in other mail that the problem was fixed with 'stty cs7 cstopb'. I think I know what the problem is, login doing a vhangup() when it shouldn't, but I have to think if my solution is safe. I'll get back to you. Guy
Re: Problem with telnet login
On Fri, 7 Jun 1996, Brian Sulcer wrote: > You must exec login from the lowest level shell. > Connection closed by foreign host. There appears to be some utmp corruption and login isn't checking for it. login-1.0.5 should fix this (it just checks if the entry is stale; there's still a race condition somewhere corrupting it). You can get this package off master.debian.org in /debian/Incoming. I will do a dinstall run later today so if it's not there, look in /debian/unstable/binary/base. Or wait a day or 2 for it to hit your mirror. Temporarily you can fix the problem by starting an xterm and killing it. That will clear out the dud utmp entry. Guy
printing .lj files
Does anyone know how to prevent a blank page from being printed at the end of the print job when printing a .lj file created using dvilj? Couldn't find anything in the lpr or dvilj manpage. Any help would be appreciated. Thanks in advance.---Richard
Re: printing .lj files
Richard Lovison ([EMAIL PROTECTED]) wrote on 7 June 1996 18:35: >Does anyone know how to prevent a blank page from being printed at the >end of the print job when printing a .lj file created using dvilj? >Couldn't find anything in the lpr or dvilj manpage. Any help would be >appreciated. We had this problem also, but it disappeared when I upgraded to 1.1, at least up to now. Carlos
