Re: superuser telnet login refused
Thanks to all who replied. I only do this with systems that are not connected to the internet. This one is experimental, but I like to have an old 386 system for making kernels or whatever. I edited the /etc/passwd file to set paul and root to have no password. Now, I just telnet in as paul and do an su. If the machine was connected to the Internet, I would only allow telnet logins of "guest" type. The reason for this crude setup is that I have virtual IP running and the Win95 box is getting web, ftp, samba, and telnet services from the Linux server. I can jump over to the telnet window to change a cgi script and then go to the browser window and test it. I would like to convert to a Linux client. Has anybody had good results running X on a 486DX-66 with 8mb? The 386's are working great as test servers! I am seeing a 2 mbit/sec ftp rate on a machine built from "leftovers". Paul Wade Backwoods Hacker E-Zine - "Roughing it in a digital world"
DEBIAN Linux on floppy disks
Hi Debian Linux users: I am a Linux novice and I have a Slackware Linux distribution installed on my Toshiba 105CS Satellite, which works fine. I am planning to install DEBIAN Linux on to my Laptop. Unfortunately I have no CD-ROM drive avail- able with this Laptop which make this attempt impossible. I have one CD-ROM with the DEBIAN Linux distribution on it. As I am able to run this CD on a Windows-based PC-System WIN95 on a seperat computer I thought it might be possible to make floppys, like I did with the Slackware distribution. I soon realized that a lot of files are too large to fit onto the disk. Is there anybody out there ...who can give me some advises how I can solve this problem. Many thanks to all of you. Fritz Ilg
Re: loss of routing info with 2.0.0
Rick Hawkins <[EMAIL PROTECTED]> writes: > I have compiled the 2.0.0 kernel (successfully), but lost my routing > info in the process (coming from 1.3.95). "route" only shows the > machine itself. > > If i manually add the missing router & gateway, it works fine, but i > lose this on reboot. I don't know if this is related, but I lost all net connectivity on one of my ethernet connected machines today when I upgraded to 2.0. It turned out that the difference was that the machine had NETMASK="255.255.0.0" instead of NETMASK="255.255.255.0". When I changed this in /etc/init.d/network, the problem went away. -- Rob
kernel-package
Kernel-package seems to be in the project/experimental directory of the archive. I don't know why... Bruce
Debian 1.1 will include the Linux 2.0 kernel
I see everyone wants to know. Yes, I will include the Linux 2.0 kernel in the latest boot disk set, which will be uploaded this evening. I also have a kernel-image package, although I am not the official kernel maintainer. Thanks Bruce
Re: help me?
On Tue, 11 Jun 1996, Chris Nielsen wrote: > I just downloaded what I think is Debian Linux v.93R6 And I need help > installing > it. I have three files called "1440_base_floppy_[1|2|3]", as well as what > appear to be > root and boot files on my d:. I have created a seperate partition on my C: > for MS-DOS, > and left an un-partitioned area of about 100 meg for debian. What do I do > now? the > three main files don't fit on one floppy disk, at least not one formatted by > Windows > 95, and neither will the boot floppy (after it's un-gziped). Also, Should I > go ahead > and partition that 100 meg I left on c:, and Should I wait for the Beta 1.1 > to become > stable before I install? Thanks for you help, it's really appreciated! Hi Chris. Whether you choose to install 0.93R6 or Beta 1.1 (which now resides in the "unstable" directory), you will need to use a program called rawrite.exe in msdos to write the files you mentionned directly to pre-formatted floppies. You cannot copy the files using the dos "copy" command, or the disks will not work for the installation. The program, rawrite, should be available on the ftp site where you found the floppy images, perhaps in a directory called "tools" or something. You may find that 100MB will not be enough to create more than a simple system, but that depends on what you choose to install. I suggest that you use the 1.1 Beta version. In the directory with the floppy disk images, you will find a document which explains in detail how to intall the 1.1 Beta system from floppy disks. This information is also available at the Debian www page http://www.debian.org under the 1.1 Beta link near the top of the page. Good Luck. Syrus. -- Syrus Nemat-Nasser <[EMAIL PROTECTED]>UCSD Physics Dept.
Re: traceroute 1.1 upgrade problems
> traceroute: IP_HDRINCL:Protocol not available Probably you're still running the 1.2.13 kernel, but the new traceroute uses some features only in 1.3... at least that's why I see that message.
help me?
I just downloaded what I think is Debian Linux v.93R6 And I need help installing it. I have three files called "1440_base_floppy_[1|2|3]", as well as what appear to be root and boot files on my d:. I have created a seperate partition on my C: for MS-DOS, and left an un-partitioned area of about 100 meg for debian. What do I do now? the three main files don't fit on one floppy disk, at least not one formatted by Windows 95, and neither will the boot floppy (after it's un-gziped). Also, Should I go ahead and partition that 100 meg I left on c:, and Should I wait for the Beta 1.1 to become stable before I install? Thanks for you help, it's really appreciated!
Re: linux2.0
Derek Lee <[EMAIL PROTECTED]> writes: > I am afraid I am not familiar with the kernel-package package. > Is this a package to build any kernel version and install it in > a debian way? Bingo. I'm using it as we speak. I'm not sure if it has made it to the unstable tree on all the mirrors yet, but it should soon. When you get it, the docs are /usr/doc/kernel-package, as expected. -- Rob
Re: linux2.0
On Tue, 11 Jun 1996, [EMAIL PROTECTED] wrote: > Would the release of debian 1.1 use the new stable Linux (v2.0)? Yes, Debian 1.1 will ship with a 2.0 kernel. (In fact, the latest available kernel will generally be made available as the kernel-image-2.0.xx-0.deb). Austin
Re: stty vs setserial
Dale Scheetz <[EMAIL PROTECTED]> writes: > I can point setserial at a particular port, but can't seem to tell it to > set the stop bits to two. > I can tell stty to set the stop bits, but can only seem to use it while on > the tty in question. Is there any way to point stty at the port I want > changed? Unless I'm mistaken, the paradigm is stty options < /dev/tty-whatever Hope that helps. -- Rob
loss of routing info with 2.0.0
I have compiled the 2.0.0 kernel (successfully), but lost my routing info in the process (coming from 1.3.95). "route" only shows the machine itself. If i manually add the missing router & gateway, it works fine, but i lose this on reboot. help! :) rick
FAQ: Work-Needing and Prospective Packages
Work-Needing and Prospective Packages for Debian Linux Sven Rudolph, [EMAIL PROTECTED] $Id: packages.sgml,v 1.18 1996/06/11 19:54:00 sr1 Exp sr1 $ __ Table of Contents: 1.General Questions 1.1. What is Debian Linux 1.2. Purpose of this document 1.3. What do I need to know in order to become a package maintainer ? 1.4. Feedback 2.Packages that have no current maintainer 3.Packages that the maintainer wants to give away 4.Packages that someone is working on 5.Programs that aren't available yet in Debian 5.1. Programming and development: 5.2. Mail software: 5.3. USENET news software: 5.4. Math packages: 5.5. Graphics: 5.6. Misc Tools: 5.7. Editors: 5.8. Games: 5.9. X11: 5.10. Communication 5.11. TeX 5.12. Networking 5.13. System Tools 5.14. Text utilities 6.Programs that someone should write 7.Beyond packages __ 1. General Questions 1.1. What is Debian Linux Please read the Debian Linux FAQ. The Debian Linux WWW server is at http://www.debian.org/ , the FAQ is located at http://www.debian.org/FAQ/ . The FAQ is available via FTP at ftp.debian.org:/debian/doc . 1.2. Purpose of this document This document is intended to identify areas that need your contributions. It provides information that hopefully changes quite often, so it supplements the Debian Linux FAQ. 1.3. What do I need to know in order to become a package maintainer ? Please read the documents at ftp://ftp.debian.org/debian/doc/package- developer/ . The packaging guidelines are included in the dpkg-1.1.0 package. You should subscribe to the debian-devel mailing list, details are given in the FAQ. 1.4. Feedback Please send additions, corrections, suggestions and wishes to Sven Rudolph [EMAIL PROTECTED] Please mention to which version of this document your comments refer. 2. Packages that have no current maintainer Packages listed in this section are still part of Debian (unless they have too many bugs), but the maintainer had reasons to not continue maintaining it. (Remember: Debian is mainly produced by volunteers who are not paid for maintaining Debian packages.) If you find that you need to discontinue maintaining a package, send me an e-mail. If you believe that the following list is incomplete, i.e., that there are other packages in the Debian distribution that currently have no active maintainer, send me an e-mail. If you would like to maintain one of the packages listed here, send me an e-mail. previously maintained by Ian Murdock [EMAIL PROTECTED] : o acm o aout-librl (this package might be unnecessary now) o elisp-manual o glibcdoc o metamail o pmake previously maintained by Ian Jackson [EMAIL PROTECTED] : o trn 3. Packages that the maintainer wants to give away Packages listed in this section are still part of Debian, but the maintainer wants to find a new maintainer. It isn't as urgent to find a new maintainer as in the previous section. If you maintain Debian packages that you would like to hand off, send me an e-mail, then I will add this package to this section. If you would like to maintain one of the packages listed here, write to the current maintainer of this package. currently maintained by Sven Rudolph [EMAIL PROTECTED] : o seyon currently maintained by David Engel [EMAIL PROTECTED] : o tclX currently maintained by Christian Linhart [EMAIL PROTECTED] : o statserial o tgif o xarchie currently maintained by Ian Jackson [EMAIL PROTECTED] : o m4 o cron currently maintained by Jim Robinson [EMAIL PROTECTED] : o pari currently maintained by Michael Meskes [EMAIL PROTECTED] Aachen.DE : o xsysinfo o xcolors o xautolock 4. Packages that someone is working on Programs listed in this section aren't yet available as Debian packages, but someone is working on providing a package. If you would like to work on one of these packages please contact the responsible person listed below. Chris Fearnley [EMAIL PROTECTED] : o dome (http://www.netaxs.com/ cjf/jpegs.html) o and probably : xli, Tix, povray [EMAIL PROTECTED] (Karl R. Sackett) : o CLX - Common Lisp Xlib implementation o PCL - Portable Common Loops for GCL Dale Miller [EMAIL PROTECTED] : o lclint (ftp://larch.lcs.mit.edu/pub/Larch/lclint/ ) Richard Kaszeta [EMAIL PROTECTED] : o xmotd Mike Wilson [EMAIL PROTECTED] : o mule Sven Rudolph [EMAIL PROTECTED] : o xbill o NCSA Mosaic (waiting for 2.7) "behan (b.) webster" [EMAIL PROTECTED] o sxpc (Simple Xwindows Protocol Compresser) o qfax (multi-user e-mail extension to efax). [EMAIL PROTECTED]: o
Trantor T130B SCSI Configuration
First, thanks to all who assisted me with the Tulip+2940 kernel-- as it turns out, debian 1.1 ships with the tulip driver as a dynamically loadable module... so, merely adding 'tulip' to /etc/modules fixes the lacking driver problem!!! [though, tulip didn't work for me-- i had to use the *other* 21040 driver]. Anyway, NEXT PROBLEM: I'm now building an older 486 DX/2 with Debian 1.1beta. I have already built it once using the internal 80 MB IDE drive [blech!], but have recently obtained a Trantor T130B SCSI card (and already have a 400 MB SCSI drive I can recycle). BUT; I'm having a hard time configuring *something* such that Debian recongizes the drive. I'm pretty sure it is recognizing the controller card [then again, maybe not]. I suspect that I have not correctly terminated the SCSI bus, but need some assistance in figuring out *exactly* how it should be terminated. Specifically, the SCSI controller card has a 25-pin port on the back (YUCK!) and a 50 pin connector on the board. The dip switches are set such that it is IRQ 5 at port 350H (0x350?). It is an NCR53c400 based controller card. The 50 pin connector has three terminating resistor packs ajacent to it... SO: Question: I want to connect a Seagate ST1480N drive to the card via the internal 50 pin connector... What needs to be terminated and how should the drive be configured? Specifically, does the 25 pin connector on the back need a terminator? Should the terminating resistor packs on the card remain on the card? How should the drive be configured? Tech specs on the Trantor are here:
Re: superuser telnet login refused
binnxr9gL1hks.bin Description: application/pgp-message
Re: linux2.0
Rob Browning wrote: > > I'm not sure if it'll be packaged in time for the initial 1.1 release, > but it'll certainly be available shortly thereafter. > > Anyway, using the new kernel-package package, it's pretty trivial to > do it yourself. > I am afraid I am not familiar with the kernel-package package. Is this a package to build any kernel version and install it in a debian way? Derek
Re: linux2.0
[EMAIL PROTECTED] writes: > Would the release of debian 1.1 use the new stable Linux (v2.0)? I'm not sure if it'll be packaged in time for the initial 1.1 release, but it'll certainly be available shortly thereafter. Anyway, using the new kernel-package package, it's pretty trivial to do it yourself. -- Rob
Re: ncr-810 support?
Dale Martin <[EMAIL PROTECTED]> wrote: ] It would appear that the boot disks for debian 1.1 beta don't have ] generic ncr-810 SCSI support - the .93 disks did. Are there ] alternative boot disks available with this support? I perused the ] installation document and saw no mention of it. I ran in to this same problem. I made a custom boot disk with the NCR driver. It's available at: ftp://ftp.cs.colorado.edu/users/kuzminsk/boot-disk.gz It's not the latest and greatest version kernel, and it doesnt mimick the Debian boot disk exactly, but it's worked well for me. Sebastian Kuzminsky [EMAIL PROTECTED]
linux2.0
Would the release of debian 1.1 use the new stable Linux (v2.0)? --Derek Lee
Re: Packages need libc.so.4
"Larry Loos" <[EMAIL PROTECTED]> writes: > I'm doing my first install of Debian Linux using the 1.1-Beta. I have > the initial system installed and now I'm trying to install the > packages that I want. When I tried I got many errors that say it > needs libc.so.4. Where is it? Where did you get the packages you're installing? Most of the new packages depend on libc5, the ELF libc. It should have been installed when you upgraded to Debian 1.1. If you have old packages which depend on libc4, and you still need to use for some reason, you can get the libc4 (not libc4-dev) package from the development tree. It provides libc4 binary compatibility. -- Rob
traceroute 1.1 upgrade problems
I just upgraded my 0.93 laptop to 1.1, and now traceroute doesn't work... traceroute to anyplace returns traceroute: IP_HDRINCL:Protocol not available any ideas anyone?
stty vs setserial
I can point setserial at a particular port, but can't seem to tell it to set the stop bits to two. I can tell stty to set the stop bits, but can only seem to use it while on the tty in question. Is there any way to point stty at the port I want changed? 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: superuser telnet login refused
On Sun, 9 Jun 1996, Paul Wade wrote: > Before installing Debian Linux, I was able to log in > as root over telnet. Now it is refused. I am simply > using a Windows system as a Linux console over > ethernet. How do I fix this? man securetty
Re: Packages need libc.so.4
On Mon, 10 Jun 1996, Larry Loos wrote: > I'm doing my first install of Debian Linux using the 1.1-Beta. I have > the initial system installed and now I'm trying to install the > packages that I want. When I tried I got many errors that say it > needs libc.so.4. Where is it? Hmm... Many packages need libc4? Are you sure you've got 1.1-beta, (i.e. from the unstable tree)? Because very few packages in there still depend on libc4. Anyhow, the package that contains libc.so.4 is "libc4" and it is in the devel section. Christian
Re: Packages need libc.so.4
A list reader kindly replied: > in unstable/devel/libc4-4.6.27-15.deb . Are you sure you're installing > packages from the correct tree (_un_stable)? Packages that depend on libc4 > are > in the a.out binary format, which is being replaced by ELF. I received several private messages from readers of the list. I was not using the correct tree as this person suggested. I will move to the 'unstable' directory. I realize that 1.1-Beta is supposted to move to stable sometime on the 12th so I will need to watch the mirrors to get the correct ones. Thanks to everyone who offered help. Larry Loos Show-Me Nete-mail: [EMAIL PROTECTED] 1417 N Henderson http://www.showme.net/ Cape Girardeau, MO 63701 314/334-9322
Re: Howto upgrade 0.93 --> 1.1
Juhani Luhtanen writes ("Howto upgrade 0.93 --> 1.1"):
> Is there anywhere a simple step-by-step guide on how to go and upgrade
> one's debian?
1. Install the latest a.out dpkg from the `upgrades' directory, for
example `dpkg --install dpkg-1.2.3.deb'.
2. Run dselect and go through Access/Update/Select/Install/Remove in
order.
Ian.
Re: Packages need libc.so.4
In your email to me, Larry Loos, you wrote: > > I'm doing my first install of Debian Linux using the 1.1-Beta. I have > the initial system installed and now I'm trying to install the > packages that I want. When I tried I got many errors that say it > needs libc.so.4. Where is it? > > I'm obviously a newbie to Debian and appreciate any help some kind > soul will give me. Dselect can search for it... just do '/libc' and you'll find it. Tim -- [EMAIL PROTECTED] "Try not. Do, or do not. There is no try." -- Yoda ** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.**
dselect ( dpkg 1.2.3 (i386 elf)) unable to install 1.1
Hi, I want to upgrade my debian 1.0 to 1.1. I have installed the new dpkg (1.2.3 elf) then followed the steps in dselect. then dselect failed in the Install step with the following error: Running dpkg -iGROEB /u2/debian/binary find: /u2/debian/binary/admin/tob-0.14-1.deb: No such file or directory find: /u2/debian/binary/base/adduser-1.99-1.deb: No such file or directory find: /u2/debian/binary/hamradio/p10cfgd-1.0-3.deb: No such file or directory find: /u2/debian/binary/misc/mailcrypt-3.4-1.deb: No such file or directory find: /u2/debian/binary/misc/ncurses-term-1.9.9e-1.deb: No such file or directoy find: /u2/debian/binary/net/mirror-2.8-5.deb: No such file or directory find: /u2/debian/binary/net/xntp-doc-3.5c-1.deb: No such file or directory find: /u2/debian/binary/tex/latex2e-doc-1.6-0.deb: No such file or directory find: /u2/debian/binary/tex/xypic-3.2-4.deb: No such file or directory find: /u2/debian/binary/text/apsfilter-4.9.1-6.deb: No such file or directory find: /u2/debian/binary/text/gsfonts-2.62-2.deb: No such file or directory find: /u2/debian/binary/text/igerman-2-3.deb: No such file or directory -- find: /u2/debian/binary/text/texidoc-3.7-1.deb: No such file or directory find: /u2/debian/binary/text/wgerman-2-3.deb: No such file or directory find: /u2/debian/binary/x11/xfnt100-3.1.2-6.deb: No such file or directory find: /u2/debian/binary/x11/xfnt75-3.1.2-6.deb: No such file or directory find: /u2/debian/binary/x11/xfntbase-3.1.2-4.deb: No such file or directory find: /u2/debian/binary/x11/xfntbig-3.1.2-6.deb: No such file or directory find: /u2/debian/binary/x11/xfntcyr-3.1.2-6.deb: No such file or directory find: /u2/debian/binary/x11/xfntpex-3.1.2-3.deb: No such file or directory find: /u2/debian/binary/x11/xfntscl-3.1.2-7.deb: No such file or directory find: /u2/debian/binary/x11/xmanpages-3.1.2-6.deb: No such file or directory find: /u2/debian/binary/devel/autoconf-2.10-2.deb: No such file or directory find: /u2/debian/binary/devel/CGI-modules-2.75-3.deb: No such file or directory find: /u2/debian/binary/devel/dejagnu-1.3-4.deb: No such file or directory find: /u2/debian/binary/devel/kernel-headers-1.99.7-0.deb: No such file or direy find: /u2/debian/binary/devel/kernel-source-1.99.7-0.deb: No such file or direcy find: /u2/debian/binary/doc/manpages-1.11-4.deb: No such file or directory dpkg: subprocess find returned error exit status 1 installation script returned error exit status 1. Press RETURN to continue. The problem is that all these files do exists. and when in type for example find /u2/debian/binary/x11/xfntscl-3.1.2-7.deb I get: /u2/debian/binary/x11/xfntscl-3.1.2-7.deb This confirms that find is OK and that I have the file, but dselect does not think that I have the file Any help will be appreciated -Oz < NAME Oz Dror, Santa Monica, California EMAIL [EMAIL PROTECTED] <> PHONE Fax (310) 396-5798 -BEGIN PGP PUBLIC KEY BLOCK- Version: 2.6.2 mQBtAzA/tLQAAAEDAKUy/TEjQ/jiZ+9/WJb/+NHxqkvOxGZ3W/F2JCNm5v5ZTZz+ BVZC9GM/I+plQ8xz+7B+KhDSVax8gxNTAkJ+I7P/zAP2ZDMwVf4lq5ZFxMJC+7c7 ET+hNtmQUt8vCVR8hQAFEbQZT3ogRHJvciA8ZHJvckBuZXRjb20uY29tPg== =EU23 -END PGP PUBLIC KEY BLOCK- >
Re: superuser telnet login refused
In your email to me, Paul Wade, you wrote: > > Before installing Debian Linux, I was able to log in > as root over telnet. Now it is refused. I am simply > using a Windows system as a Linux console over > ethernet. How do I fix this? Fix it? It's not really broken. The 'normal' security rules say no root logins from anywhere but the console so you can't get your root password sniffed... if you want to 'break' the security on your system, look at /etc/securetty Tim -- [EMAIL PROTECTED] "Try not. Do, or do not. There is no try." -- Yoda ** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.**
Linux 2.0 and Debian 1.1
Hi, Is Linux 2.0 going to be included in Debian 1.1 once it's release? Thanks. -- Arthur D. Jerijian | "Who on earth can blame them? Ah, no wonder the [EMAIL PROTECTED] | men of Troy and Argives under arms have suffered [EMAIL PROTECTED] | years of agony all for her, for such a woman. [EMAIL PROTECTED] | Beauty, terrible beauty!" [EMAIL PROTECTED] | Homer, the king of all poets
Re: Packages need libc.so.4
On Mon, 10 Jun 1996, Larry Loos wrote: > I'm doing my first install of Debian Linux using the 1.1-Beta. I have > the initial system installed and now I'm trying to install the > packages that I want. When I tried I got many errors that say it > needs libc.so.4. Where is it? > This is in the libc4 package in section devel. 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 --
ncr-810 support?
It would appear that the boot disks for debian 1.1 beta don't have generic ncr-810 SCSI support - the .93 disks did. Are there alternative boot disks available with this support? I perused the installation document and saw no mention of it. Thanks, Dale
Dselect + NFS
Hi, I have just had something strange happening to me. I tried to update some packages using dselect with the NFS option. When going into the install option I would get an error from find about not being able to find the directory. The strange thing though is that the directory was correct and the available packages were correctly updated. Mounting the partition by hand and using dselect works. I recently updated dpkg so I thought there might be a problem with it. Has anyone had something similar happen to them? Am I just doing something really stupid? Thanks in advance, Luis.
NFS install - follow up
Hi again, I just noticed I didn't metion that I am running debian 1.1 (beta) and dpkg -s dpkg gives: Package: dpkg Essential: yes Status: install ok installed Priority: required Section: base Maintainer: Ian Jackson <[EMAIL PROTECTED]> Version: 1.2.3elf Replaces: dpkgname Pre-Depends: libc5 (>= 5.2.18-2), ncurses3.0 Conflicts: dpkgname Description: Package maintenance system for Debian Linux This package contains the programs which handle the installation and removal of packages on your system. . The primary interface for the dpkg suite is the `dselect' program; a more low-level and less user-friendly interface is available in the form of the `dpkg' command. Sorry and thanks! Luis
superuser telnet login refused
Before installing Debian Linux, I was able to log in as root over telnet. Now it is refused. I am simply using a Windows system as a Linux console over ethernet. How do I fix this? Paul Wsde
Linux 2.0 in Debian 1.1
As Linux 2.0 already released, I think it should be included in the debain 1.1 official release.
Re: Problem with telnet login
> I remember seeing in the kernel mailing list that pre2.0.13 breaks > incoming telnets. Are you by chance using this kernel? > > Gerry > [EMAIL PROTECTED] It turns out that the problem was with the version of login I had installed. The maintainer pointed me to the newest version and that fixed the problem. Thanks to all who responded. -- Brian Sulcer <[EMAIL PROTECTED]> | Gibson USA System Administrator | Nashville, Tennessee Worldwide Net Services | (615) 871-4500 ext 275
testing ...
I haven't heard anything from the list in a while, just checking to see if I'm still subscribed! Thanks Richard G. Roberto [EMAIL PROTECTED] 201-739-2886 - whippany, nj -- *** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. ***
Re: gzip and dpkg problem
[EMAIL PROTECTED] writes ("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).
It should be a simple fix to getty_ps; if anyone packages it for
Debian this will be an easy thing to do at the same time.
Ian.
Re: EMAIL! HELP!
On Thu, 6 Jun 1996, Fundamental wrote: > 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) You probably should have partitioned the disk so that /var and/or /var/spool were separate partitions. Too late for that now, unless you want to reformat. You can still add another drive and mount a partition as /var if you want. Another way to do this is to move the mail spool directory to a partition with more space available. e.g. if /usr has lots of free space, try doing the following: mkdir -p /usr/spool cp -af /var/spool/mail /usr/spool rm -rf /var/spool/mail ln -s /var/spool/mail /usr/spool/mail This is the reason why i tend to mount extra drives/partitions as general purpose directories (e.g. /usr1, /usr2, /usr3 etc) rather than as special purpose directories (e.g. /var/spool/mail, /var/spool/news). It gives me the flexibility to move spool directories etc around on my system from one disk to another, and just change the sym link in /var/spool to point to the new location. e.g. on my system, /usr2 (a 540MB quantum scsi) has a directory called /usr2/spool. /usr3 (a 650MB Micropolis scsi) also has /usr3/spool. news spool is in /usr2/spool/news, and mail is in /usr3/spool/mail. I want nn's database on a separate drive from the main news spool (to minimise disk thrashing) so that's in /usr3/spool/nn. With appropriate sym links in /var/spool, I don't even have to recompile anything - it all works transparently to the programs. $ ls -alF /var/spool | grep -- "->" lrwxrwxrwx 1 root root 16 Jun 10 17:32 mail -> /usr3/spool/mail/ lrwxrwxrwx 1 root root 16 Jun 10 17:32 news -> /usr2/spool/news/ lrwxrwxrwx 1 root root 14 Jun 10 17:32 nn -> /usr3/spool/nn/ Some people will probably think that this is an ugly way of doing things - and i can see their point. But for me, the flexibility is worth a little bit of ugliness. Craig
inconsistency between base and sysvinit packages!
I tried to send this to debian-bugs, but it hasn't been delivered for 2 days, so I'm posting it here as well. Carlos --- start of forwarded message (RFC 934 encapsulation) --- From: Mail Delivery Subsystem <[EMAIL PROTECTED]> Subject: Returned mail: Cannot send message for 2 days Date: Sun, 9 Jun 1996 16:26:50 -0700 - Transcript of session follows - 451 [EMAIL PROTECTED] timeout waiting for input 421 master.debian.org (TCP)... Deferred: Connection reset by peer during greeting wait with master.debian.org [headers trimmed] The newer base packages create /dev/tty* with permission rw-rw. This causes an error when you try to open an xterm/rxvt window. They quit with "couldn't open a pseudo-terminal" msg. I don't know whose fault it is. However, the newest sysvinit has this command in the boot script: chmod 666 /dev/tty[pqrs]* So there seems to be a disagreement between the maintainers, no? Carlos PS: please Cc: me, I don't get debian-bugs. Carlos --- end ---
Re: gzip and dpkg problem
On Mon, 10 Jun 1996, Ian Jackson wrote: > > It should be a simple fix to getty_ps; if anyone packages it for > Debian this will be an easy thing to do at the same time. > Yep, it looks REAL simple. It there isn't a current maintainer, I'll package it up. L.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
Miquel van Smoorenburg writes ("Re: gzip and dpkg problem"):
> In article <[EMAIL PROTECTED]>,
> Ian Jackson <[EMAIL PROTECTED]> wrote:
> >This means that SIGPIPE was set to SIG_IGN when dpkg started. For
> >reasons too complicated to explain here this means that dpkg can't do
> >proper error trapping (it always gets an error indication, and can't
> >tell whether it's really an error).
>
> Can't you just set signal(SIGPIPE, SIG_DFL) first thing in the
> main() function of dpkg? And if not, could you tell me why not
> (sounds interesting ;))
Yes, I *could* do that. However, if I did I would simply be covering
up a problem which ought to be a problem for many programs other than
dpkg but which isn't solely because of sloppy programming.
If I add any code to dpkg with respect to this it'll be a check which
makes it bomb out with an informative message. See, for example, my
approach to trying to run dpkg with a bad PATH.
Ian.
'nobody' doesn't exist?
Hmmm, I keep getting
inetd[3543]: getpwnam: nobody: No such user
messages on my xconsole. The 'nobody' user is defined in /etc/passwd,
so what's going on? As far as I know, I'm running the latest
development ("unstable") release of Debian (1.1).
It's not fatal, just annoying. Mostly I'm curious as to what's causing
it.
//Petri
Re: Help wanted :-)
>I think it would be sufficient for people to list their qualifications >and let the customer decide. The Better Business Bureau approach of keeping a file of complaints might also be useful.
Re: login and bash on a hardwired terminal.
> Now the question is: How do I get login to leave the stop bits alone? /etc/gettydefs is used for this, but debian has no support for it.. hmm.. guess thats a login problem. Greetings Bernd -- (OO) -- [EMAIL PROTECTED] -- ( .. ) [EMAIL PROTECTED],ka.sub.org} http://home.pages.de/~eckes/ o--o *plush* 2048/A2C51749 [EMAIL PROTECTED] +4972573817 *plush* (OO) If privacy is outlawed only Outlaws have privacy
last 1.1 upgrade problem fixed with NAG FORTRAN
Dear Debian-Linux colleagues: A few days ago, I had mentioned in this newsgroup a problem I was having with using my commercial license of NAG Fortran on the new Debian 1.1 upgrade. I wish to report here the fix to the problem. As one might expect, the problem is due to Debian 1.1 being an all-elf installation while earlier versions were either all-aout or mixed-aout-elf. It turns out that my system was mixed, and already had the old libc4 libraries loaded. Since my version of NAG is an a.out system, I had originally thought that I needed to specifically point the compiler to the a.out libraries on my system. However, as it turned out, the compiler needed the a.out version of the gcc compiler. More specifically, the NAG compiler looks for a hard-coded /usr/bin/gcc to execute. I simply had to create a symlink ln -s /usr/i486-linuxaout/bin/gcc /usr/bin/gcc after renaming /usr/bin/gcc to /usr/bin/gcc.elf, and my normal NAG compile commands will work. The Debian 1.1 conveniently makes available several of the old a.out packages under the /usr/i486-linuxaout tree. If someone can dream up a more intelligent way of pointing apps between gcc(aout) and gcc(elf), I would appreciate it. As it stands now, I will have to manually change gcc each time I want to use NAG FORTRAN and an elf-binary build. Incidently, the NAG folks told me I had to purchase an elf-upgrade of the compiler to get it to work on my system. Since my kernel is now built to run both elf and aout executables, that is not the case. -- /--\ | James D. Freels, P.E._i, Ph.D. | Phone: (423)576-8645 | | L | | Oak Ridge National Laboratory | FAX:(423)574-9172 | H | I | | Research Reactors Division | Internet: [EMAIL PROTECTED] | F | N | | P. O. Box 2008 | Reactor Technology | I | U | | Oak Ridge, Tennessee 37831-6392 | world's best neutrons! | R | X | |--| | out the 10Base-T, through the router, down the T1, over the | | leased line, off the bridge, past the firewall...nothing but Net | \--/
Re: gzip and dpkg problem
On Thu, 6 Jun 1996, Ian Jackson wrote:
> Paul Schoenly writes ("gzip and dpkg problem"):
> ...
> > $ dpkg --install package_x.deb
> ...
> >gzip:stdout: Broken pipe
> >dpkg-deb: subprocess gzip -dc returned error exit status 1
> >dpkg: error processing package_x.deb (--install)
> > subprocess dpkg-deb --control returned error exit status 2
> >Errors were encountered... (and so on)
>
> This means that SIGPIPE was set to SIG_IGN when dpkg started. For
> reasons too complicated to explain here this means that dpkg can't do
> proper error trapping (it always gets an error indication, and can't
> tell whether it's really an error).
>
[ much stuff deleted ]
>
> 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 :-). If you don't want to bother trying to install packages
> (and it sometimes works even if the bug is present), try:
> cat /dev/zero | true
> If the bug isn't present this produces just `Broken pipe' (assuming
> you're using bash as your shell). If the bug is present it will
> produce `cat: write error: Broken pipe'.
ok, I am pretty sure I can blame this on xsm. Whenever I try this
test in rxvt start by xsm or in rxvt started from that original rxvt,
it fails, if I start rxvt from a window manager (fvwm2) which is
itself started by xsm, the test does not fail. Strange. I guess fvwm resets
that handler correctly.
Re: sysklogd upgrade
Richard Lovison writes ("sysklogd upgrade"):
> I recently upgraded from syslogd 1.3-2 to sysklogd 1.3-6 manually using
> dpkg. When I started dselect I was informed that syslogd and sysklogd were
> in conflict, the configuration files for syslogd were still on the system.
> I proceeded to purge syslogd but was informed I couldn't because it was a
> required package. I'm not sure what is happening here. Can anyone help?
This is a bug. I'll change it in dpkg 1.2.4. You should be able to
purge a package that is marked as essential if it is no longer
installed due to having been replaced.
If syslogd is written properly there should be no problems with
syslogd 1.3-2 remaining in the `config-files' state.
Ian.
Packages need libc.so.4
I'm doing my first install of Debian Linux using the 1.1-Beta. I have the initial system installed and now I'm trying to install the packages that I want. When I tried I got many errors that say it needs libc.so.4. Where is it? I'm obviously a newbie to Debian and appreciate any help some kind soul will give me. Larry Loos E-Mail: [EMAIL PROTECTED] Show-Me Net, Inc.http://www.showme.net/ 573/334-9322 or 573/431-1245 (Work)
Re: Problem with telnet login
I remember seeing in the kernel mailing list that pre2.0.13 breaks incoming telnets. Are you by chance using this kernel? Gerry [EMAIL PROTECTED] On Fri, 7 Jun 1996, Brian Sulcer wrote: > 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 >
where are the newsgroups???
Where are the debian news groups? Have they completely shut down or do we need to resubscribe (again)? -- /--\ | James D. Freels, P.E._i, Ph.D. | Phone: (423)576-8645 | | L | | Oak Ridge National Laboratory | FAX:(423)574-9172 | H | I | | Research Reactors Division | Internet: [EMAIL PROTECTED] | F | N | | P. O. Box 2008 | Reactor Technology | I | U | | Oak Ridge, Tennessee 37831-6392 | world's best neutrons! | R | X | |--| | out the 10Base-T, through the router, down the T1, over the | | leased line, off the bridge, past the firewall...nothing but Net | \--/
Re: login and bash on a hardwired terminal.
On Fri, 7 Jun 1996, Dale Scheetz wrote: > On Fri, 7 Jun 1996, Steve Preston wrote: > > 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 :-) Sounds like you've nearly got it working, but here's a tip for you: Rather than change s/w settings on the unix box, change the setup on the terminal(s) so that they are as 'standard' as possible. This means, if the terminal setup allows it, set them to 8 data bits, 1 stop bit, no parity. Also, unless the term's native mode provides features you need, set the terminal to emulate vt-100 or similar. This way, you (or whoever logs in on the terminal) can avoid having to have special case stuff in ~/.bashrc, ~/.bash_profile to set the environment properly according to where they've logged in from. It also follows the KISS principle - Keep It Simple Stupid - which i've found is a damn good principle to follow :-) i went down the same 'terminals are cheap/free so use them' path when i first started with linux a few years ago...in fact, multi-user & cheap/free dumb terminals was one of the main reasons i originally switched to linux. So if you're still having troubles email me and i'll do what i can to help you out. email me directly...i just accepted a new job and dont have as much time to read the mailing lists as i used to. Another way of doing it: If you CAN'T for some reason set the terminal as above, then you'll have to edit /etc/rc.boot/0setserial to do an 'stty cs7 cstopb' or whatever else is needed on the terminal. Setting the line characteristics of a hardwired terminal should be done BEFORE getty or login run on the terminal - i.e. during the bootup process. Also, if you do this you might want to put something like the following in /etc/profile, to force the right settings every time someone logs in (just in case the previous logged in user mucked up the stty settings): if [ "`tty`" = "/dev/ttyS1" ] ; then stty cs7 cstopb alias exit='stty cs7 cstopb ; exit' alias logout='stty cs7 cstopb ; logout' fi This runs the right stty command at login, and aliases 'exit' and 'logout' to make sure they're set properly on logout. Craig
