Re: diald
On Fri, 9 Aug 1996, Tim O'Brien wrote: > Does anyone know how to get diald to work? I'm almost there; I can get it to > do it's thing, dial, connect to my ISP, start sending data, but after about > 30 seconds, diald kills pppd, and reports that it has timed out waiting for > ppp to connect. :/ Since I was in the middle of receiving an html document > from the web, I'd say it's safe to assume that pppd was already connected. > Anyone got any ideas how I can cure this VERY annoying problem? I had this same problem and tracked it down to the ppp-connect-with- diald script referenced by /etc/diald.options. I assumed from the script's name that it would invoke ppp and connect, but alas it was only meant to make the physical connection to my ISP and exit. Diald takes over then and invokes pppd. This leads to the second problem: /etc/ppp/options pointed to my chatscript (/etc/ppp/chatscript) so when diald started pppd, pppd tried to reconnect with chat which of course didn't work so well. In short, make sure your ppp-connect-with-diald only runs chat (with the appropriate script) and exits, and that pppd does not automatically execute chat and you should be home free. Unfortunately, I don't remember if this was the way things were setup when I installed or if I messed them up. If the former, perhaps this is a packaging glitch? If the latter I seem to learn the most when I do something stupid (and I'm learning all the time). Good luck, Owen
Re: How do I get GATEWAY2000 PS/2 mouse to work or The Case of The Missing Modules)
Mike Taylor wrote: > > On Thu, 8 Aug 1996, Mark Edward Johnston wrote: > > > > > I have installed Linux (Debian 1.1) on a friend's computer, > > but can't get X to work as it complains about not being able to > > find the mouse. > > > > The system is a Gateway 2000 DX2/66 with Cirrus Logic 5434 > > and what seems to be a "PS/2" mouse. > > > > I have linked /dev/mouse -> /dev/psmouse (-> /dev/psaux) > > and set Protocol and Device in XF86Config to "PS/2" and > > "/dev/mouse" respectively. > > > > Any help would be appreciated, > > > > Mark Johnston ([EMAIL PROTECTED]) > > > > > > PS: Does anybody know if PS/2 mouse support is in the default kernel in > > Debian 1.1.3 ?? Is this a valid question ? The debian 1.1.x kernel as distributed supports the PS/2 mouse as a Module. The only problem is that the binary distribution does not contain a complete set of modules. I got the required module by compiling the kernel using the existing debian configuration file. This generated a full set of modules. I manually added the missing module to my configurating and the mouse started working. NOW The Greater Question for the Debian package maintainers is: Why isn't a complete set of modules distributed with the binaries? I've seen the same PS/2 mouse question over and over again. It's a very simple problem to solve, but a pain in the butt for someone that's never compiled a kernel. MY SUGGESTION: Add a complete set of modules to the distribution package. Jim <[EMAIL PROTECTED]>
Re: diald
On Fri, 9 Aug 1996, Tim O'Brien wrote: > Does anyone know how to get diald to work? I'm almost there; I can get it to > do it's thing, dial, connect to my ISP, start sending data, but after about > 30 seconds, diald kills pppd, and reports that it has timed out waiting for > ppp to connect. :/ Since I was in the middle of receiving an html document > from the web, I'd say it's safe to assume that pppd was already connected. > Anyone got any ideas how I can cure this VERY annoying problem? I had this same problem. Unfortunately you are the only other person I have seen who has this problem, so I never found any official fixes. All I can suggest is to make sure you have the latest version of pppd and the latest kernel, or an older version of pppd and an older kernel. All I can figure that there are certain combinations of pppd and kernels that have this problem. Mine works now with the latest kernel and pppd (I think the 'f' version). Yes this is definitely one of the most annoying problems I have seen. Just when you think it is working fine, it hangs up on you :-( Tony.
Re: Serial ports...
Sherwood Botsford <[EMAIL PROTECTED]> writes: > CAVEAT I'm an ignoramlepuss about Linux/Debian. [ good info about serial ports deleted ] I do recall a discussion recently where someone posted text from the maintainer of the Linux kernel's serial port code that essentially said that cua* devices were no longer really supported, and that you should always use ttyS* when possible. I was having some trouble with cua* at the time (for dialout), and sure enough, switching to ttyS* fixed the problem. -- Rob
dump for a.out?
Hi guys, I'm really needing to use the dump utility to schedule my backups. My problem is that dump requires libc5.x, and I'm still running libc4.x. I tried upgrading libc, but it runs into other dependency conflicts, and it seems to me that unless I start upgrading *everything*, which I can't afford to do now (due to downtime), I'm SOL. So, question: Is the source for dump available so I can compile it myself with the old libs? Help! ;-) ricardo
Re: Ught Oh =O
Well .. a common feature of most virus tools (Norton) is to clean up the boot block .. it looks like your boot block got swiped. Best thing to do is get a boot disk .. if you don't have one .. download one from a linux ftp site .. my guess is any version will do the trick. Mount your hard drive and rerun lilo. I know these probably aren't the best directions .. but it has been a while since I used lilo. -- Michael > > Hey everyone, > > Ught.. U... Ohhh... > > Heh, I have a problem. > I got a virus on my Windows partition ( And YES I did scan it first with > norton ). > But After I debugged, and fixed as much as I could, everything looked > good... > But now on boot up - LILO dosent show... It just boots into win - blows ( > oops, I meant Wondows ;). Is there some string or sommand I enter in > somewhere ? any advice ? > ( Please take in mind I have only had Linux for about 3 weeks ). > > Aron > [EMAIL PROTECTED] > [EMAIL PROTECTED] > >
diald
> On Fri, 9 Aug 1996 08:19:24 -0500, [EMAIL PROTECTED] (Tim O'Brien) > said: > Does anyone know how to get diald to work? I'm almost there; I can get it to > do it's thing, dial, connect to my ISP, start sending data, but after about > 30 seconds, diald kills pppd, and reports that it has timed out waiting for > ppp to connect. :/ Since I was in the middle of receiving an html document > from the web, I'd say it's safe to assume that pppd was already connected. > Anyone got any ideas how I can cure this VERY annoying problem? Take a look at /etc/ppp/options. Almost everything should be commented out--when using diald, it seems to work best if ppp gets its options straight from diald. I was having a similar problem, and it turned out my ppp options file had a "connect" line in it that was causing two chats to be running at once, fighting over the line. Also, use the "defaultroute" option if you haven't already turned that on. The default diald options file seems to be set up for something like an ISDN connection, where setting up the connection only takes a couple of seconds. I changed all the timeouts to be 5 - 10 minutes, and that seems to work well. If those simple fixes don't help, turning on debugging for all the pieces involved (pppd: debug 1 and kdebug 1, chat: -v, diald: debug -1). This generates quite a pile of output, but I found it very helpful in getting diald to work. Now, except for some annoying intermittent problems with chat, diald is working perfectly, and in combination with ip masquerade, I've got two Macs and a Pentium Pro happily sharing one modem. -Randy -- http://cogsci.ucsd.edu/~gobbel/ NOTICE: I DO NOT ACCEPT UNSOLICITED COMMERCIAL EMAIL MESSAGES OF ANY KIND. I CONSIDER SUCH MESSAGES PERSONAL HARRASSMENT AND A GROSS INVASION OF MY PRIVACY. By sending unsolicited commercial advertising/solicitations (or otherwise on or as part of a mailing list) to me via e-mail you will be indicating your consent to paying John R. (Randy) Gobbel $1,000.00 U.S.D./hour for a minimum of 1 hour for my time spent dealing with it. Payment due in 30 days upon receipt of an invoice (e-mail or regular mail) from me or my authorized representative.
Re: diald
The problems that I was having with this a WHILE ago had to do with the fact that I was using a cua device rather than a ttyS device. I don't know why this must be, but if you are using a cua device switch to its ttyS counterpart, and cross your fingers :) Michael > > Does anyone know how to get diald to work? I'm almost there; I can get it to > do it's thing, dial, connect to my ISP, start sending data, but after about > 30 seconds, diald kills pppd, and reports that it has timed out waiting for > ppp to connect. :/ Since I was in the middle of receiving an html document > from the web, I'd say it's safe to assume that pppd was already connected. > Anyone got any ideas how I can cure this VERY annoying problem? > > Thanks, > Tim > > --- > I am Pentium of Borg. Division is futile. You will be APPROXIMATED! > > [EMAIL PROTECTED] <-- (Primary email) > > --- > > >
eth0: Memory squeeze, dropping packet
While using the dpkg-ftp option within dselect - I am able to get the few packages that I requested - HOWEVER - I also get these messages at random locations in my download session eth0: Memory squeeze, dropping packet eth0: Memory squeeze, dropping packet eth0: Memory squeeze, dropping packet eth0: CU wedged, status 0240 , resetting ... couldn't get a free page eth0: Memory squeeze, dropping packet eth0: Memory squeeze, dropping packet eth0: Memory squeeze, dropping packet Any body care to shine some light on what this is all about? Thanx in advance...
Virus of some kind?
I subscribed to this list yesterday and started getting messages today... I noticed some people replying to a worrying message. After reading all the directions, I downloaded the debian files and rawrite2.exe. I made the disks, switched from OS/2, and started up DOS. The first thing I noticed was that LILO wasn't showing up any more. I figured it was some accidental thing, but wasn't that big of a deal. After switching to DOS, I rebooted with the disk in the drive, and it started chugging away. However, after reading for a few seconds, the hard drive light flickered, the screen cleared, the disk drive light went off, and I got the message "PRESS A KEY TO REBOOT." After doing so, I noticed that LILO still wasn't starting. (Skipping a few steps here.) I fired up Norton's Disk Editor and checked the MBR of drive 1, which is where I had LILO. I noticed the usual assembled gibberish, complete with the world "LILO" at the top. Then I checked the rest of the MBR and saw something ominous, even if I didn't catch it at the time: the words, "I am Li Xibin." I figured this was some kind of odd LILO error message. I didn't catch on to the fact that this was a virus until after I'd checked the boot record for the Debian disk - it sported the same phrase, which was NOT located in the BOOT1440.BIN image file. As it is, I still thought it might only be a LILO thing until I saw that it was cutting off an error message for the boot disk. (Remember, I'm used to Slackware Linux, which uses LILO even for bootkernel disks.) Using fdisk/mbr fixed the MBR, even if it did blast away the last traces of LILO, and using diskedit to manually copy a single sector cleaned the bootkernel disk. (Then I got a flash of inspiration and used an old copy of LOADLIN and a distribution kernel to boot Linux instead.) So, what I'm trying to say is: this trouble ONLY showed up after using RAWRITE2 and the Debian stuff. Using RAWRITE seems to work (except when the MBR is already infected). In fact, the one time I managed to get the bootkernel working from DOS is when I used RAWRITE on an older version of the bootkernel image. This is a little suspicious to me. I thought it was possible that the virus came in earlier, but I find this unlikely for the following reasons. First, I made the original images under OS/2, and since OS/2 doesn't even allow read access to a given sector on the hard disk, it's unlikely that my MBR was infected there. However, it's possible that the disk was infected, and when I tried to boot the disk, it did bad things to my MBR (this is confirmed; the virus spreads to disks on read or write access which goes through DOS, and to the hard disks when an infected disk is started). I'm probably very incorrect in all these statements, and wronging a large number of people as well, but someone who can get at the FTP site from the administrator's side might want to check this out. The virus SEEMS to be gone, though; we'll see if it reappears without use of any Debian stuff. Sorry to be writing such a long message that may very well be inappropriate. However, this may be of interest to at least the Win95 user who seemed to have the same problem. -- Barid Bel Medar [EMAIL PROTECTED] Knights of the CosmosShayol Ghul Resort and Health Spa -- "I am returning this otherwise good typing paper to you because someone has printed gibberish all over it and put your name at the top." - English Professor, Ohio University --
iCBS
Is the iCBS in Debian 1.1 working properly? I remember when I was upgrading my RedHat 3.0.3 to Kernel 2.0.X and the README's said that iCBS was broken in kernel 2.X. thnx in advance. Mike...
Re: diald
Tim> Does anyone know how to get diald to work? I'm almost there; I can Tim> get it to do it's thing, dial, connect to my ISP, start sending data, Tim> but after about 30 seconds, diald kills pppd, and reports that it has Tim> timed out waiting for ppp to connect. :/ Since I was in the middle of Tim> receiving an html document from the web, I'd say it's safe to assume Tim> that pppd was already connected. Anyone got any ideas how I can cure Tim> this VERY annoying problem? Diald can be configured to do almost everything. Using it "out of the box" with Eric Schenk's original /etc/diald.conf as packaged for Debian, I also noticed that I could die after some seconds, claiming inactivity. You can either modify to diald.conf so that it always stays up longer. What I did was to add a this to /etc/ppp/ip-up # send a couple of pings ping -c 20 -s 2048 -i 15 my.isp.provider >/dev/null Recently, I created a fifo /etc/diald.fifo, set the option fifo /etc/diald.fifo in /etc/diald.options and wrote the following script to issue commands as $ dial force etc. This is quite handy as a one-command interface for other scripts. Hope this helps, Dirk - /usr/local/bin/dial --- #!/bin/sh # # dial --- communicate via fifo `/etc/diald.fifo' with the diald daemon # # edd 12 Jul 96 if [ $# -ne 1 ] then echo "Usage: dial " exit 1 fi case "$1" in block|unblock|force|unforce|down|up|delay-quit|quit|reset|queue) echo $1 >> /etc/diald.fifo ;; *) echo "Unknown (or unsupported) command: $1" exit 1 ;; esac exit 0 - -- Dirk Eddelb"uttel http://qed.econ.queensu.ca/~edd
Re: installation boot fails with standard bootdisk on 486SX/33
On Aug 9, 8:18am, [EMAIL PROTECTED] wrote: > Subject: installation boot fails with standard bootdisk on 486SX/33 : : Installation fails on this old machine shortly after hitting return : at the 'Boot Parameters' prompt using the standard bootdisk. Linux : 1.2.13 runs fine. : : I suspect (based upon bug reports) that APM is enabled in the kernel : on the standard bootdisk and that this is the problem. : >-- End of excerpt from [EMAIL PROTECTED] On my system (brand-new AMD-486DX4-120), the error that I get tells me that the failure is occuring as the kernel is being decompressed. This would suggest that APM is *not* the problem, as the kernel (if it does have APM support) has not yet started to run. I have seen postings on this mailing list that claim that the problem is level 2 cache, level 1 cache, EDO RAM on a board that doesn't support it, or generic hardware instability. Some 486sx system boards do have cache. If this is the case, try turning off the cache and see if that fixes the problem. If it does, report it as a bug. ...and now for the soapbox... Given the type of problem you've reported, you might hear the infamous "hardware instability that doesn't show up when running DOS or older versions of Linux because the newest Linux makes your machine work harder" cop-out. This is a completely invalid argument, IMO. I've heard it several times (not in the message quoted above :). If I can run older versions of Linux, and a new one shows up that doesn't run, then I claim that the problem is in the new software. I've already had this happen once. I ran Linux 1.0.8 without problems on a board with a Cyrix 486DLC-40. When I installed 1.2.8 I started getting frequent, random SIGVEC errors. These would often bring the system to its knees, forcing a power cycle. I heard from several others who had the same problem, but the only help we ever got were suggestions that we should buy new motherboards. I finally gave in, because I wanted a math co-processor and a faster CPU, and I wanted to get the *&^&@#%^! machine running (and because I'd finally saved up enough money). So, I have just purchased my new motherboard (with the AMD chip), and 1.2.8 runs very well. I have not seen any SIGVECs at all since the upgrade. Now I'm being told that I can't install Debian with the 2.0.x kernel because my hardware is incompatible? This just doen't make sense! >>From what I've seen in the few days I've been on this mailing list, there are several people out there who are having trouble installing Debian because of conflicts with the cache. Of those, several are running an older version of Linux successfully, or have managed to install the system by temporarily turning off the cache, and have no problems decompressing the kernel from the hard disk. Sorry if I sound a bit peeved about all this... ...but I am. Chris -)- -- Christopher R. Hertel -)- University of Minnesota [EMAIL PROTECTED] Networking and Telecommunications Services
Re: HELP color-ls not working.....
On Thu, 8 Aug 1996, Michael J. Cotherman wrote: > I get the following when I eval color-ls, but do not get colors... > As you can see, I did do the color=yes thingy > any help would be appreciated... Michael, if you are still running fileutils-3.12, and you have color-ls installed, then the command `eval dircolors` should execute the commands you show below, and your ls should be colorized on tty terminals. By default, this included the console, xterm-color, rxvt, etc. If you are using the latest fileutils-3.13, then you need to do something else (see below). > LS_COLORS='no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31 :*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:'; > export LS_COLORS; > LS_OPTIONS='--8bit --color=tty -F'; > export LS_OPTIONS; > alias ls='/usr/bin/color-ls $LS_OPTIONS '; > alias dir='/usr/bin/color-ls $LS_OPTIONS --format=vertical'; > alias vdir='/usr/bin/color-ls $LS_OPTIONS --format=long'; > alias d=dir; > alias v=vdir; With the integration of color-ls directly into the fileutils package, a few things have changed. dircolors no longer sets up aliases or shell scripts to colorize ls, dir, and vdir. Here is an excerpt from a .bashrc which sets up aliases after running dircolors: # set up color-ls eval `dircolors /home/syrus/.dir_colors` alias d='ls -F --color=auto' alias v='ls -l --color=auto' alias vdir='ls -l --color=auto' alias dir='ls -F --color=auto' Note that color=tty has been changes to color=auto. See the documentation for other change information. Syrus. -- Syrus Nemat-Nasser <[EMAIL PROTECTED]>UCSD Physics Dept.
Re: Ught Oh =O
On Thu, 8 Aug 1996, Diggewrote: > Hey everyone, > > Ught.. U... Ohhh... > > Heh, I have a problem. > I got a virus on my Windows partition ( And YES I did scan it first with > norton ). > But After I debugged, and fixed as much as I could, everything looked > good... > But now on boot up - LILO dosent show... It just boots into win - blows ( > oops, I meant Wondows ;). Is there some string or sommand I enter in > somewhere ? any advice ? > ( Please take in mind I have only had Linux for about 3 weeks ). > > Aron > [EMAIL PROTECTED] > [EMAIL PROTECTED] > Lilo probably got erased from the boot sector of your hard disk when you disinfected it. Reinstall lilo from the base disks and you should be fine. Hope this helps, Shaya -- Shaya Potter [EMAIL PROTECTED]
Re: How do I get GATEWAY2000 PS/2 mouse to work
Thanks to all who replied to this posting. I have now got the mouse working. To summarise : Support for PS/2 mouse is not in the kernel on the standard Debian boot disk, either built in or as a module. Thus, to use a PS/2 mouse one has to obtain a kernel with the required support. The special kernel 1 has the neccessary psaux.o module, so obtaining the corresponding image package, installing it, and adding "psaux" to the appropriate config file (/etc/modules ? I can't remember) will do the job. Ideally, however, I would have liked to compile a kernel which supported the PS/2 mouse, as well as some other features of the GATEWAY 2000, such as APM, and use that. I downloaded and installed the kernel source package from 1.1.3, configured it, and tried to make the image by doing ./debian.rules This did not work, however - the make failed (after the best part of an hour had elapsed) when it was unable to find "as86". I could not find as86 anywhere on my system, and so was stuck. Am I doing something wrong, or is it the case that the kernel-source package is flawed ? BTW, when I tried to config under X with make xconfig, tk failed with a complaint about there being no such colour as "gray" !?!? Any ideas here ? Some suggestions : - The default boot disk should have PS/2 mouse support available as a module, since the PS/2 mouse seems a reasonably common device, and new users will not be happy if they have to go to great lengths just to get their mouse working. - The modules.tgz file on the special kernel 1 boot disk is corrupted. If this was fixed I could have obtained the module I needed by extracting it from this file. - The apparent dependency of the kernel compilation procedure on as86 should be resolved - if this file is neccessary then it should be in one of the packages upon which the kernel-source package depends. Thanks again for everyone's help, Mark Johnston.
Re: Recommendations on mother boards?
On Thu, 8 Aug 1996, Douglas Bates wrote: > I will soon be purchasing a custom system to run Debian GNU/Linux. Since > I must get bids from different vendors, I might as well give detailed > specifications if that will enhance the performance with Linux. > > Does anyone have comments on specific Pentium Pro motherboards? > > For example, Bruce Perens mentioned on this list some time ago that > the combination of the IDE controller in the Triton chipset with an > EIDE drive is as fast as fast, wide SCSI. I found that the system I > was using had the Triton chipset and enabled the Triton-specific > optimizations in the kernel. The results were very pleasing. > That would depend on how hard the disk subsystem is being hammered. SCSI's advantage is that it can handle multiple outstanding requests at the same time, while EIDE has to wait for one to complete before it can start a second one. Under a single tasking OS, this is ok, but if you have a a hundred or so user processes fighting over the disk, this becomes a losing proposition. Check out the results when you have a fast/wide scsi 2 drive on a good controller, with a a few meg of cache on the drive. (This allows the drive to start being clever and resort the queue'd I/O's for fastest return. E.g. If the head is on cylinder 7, and it gets a read request for cylinder 2000, and cylinder 500, it will do the 500 on the way to the one for 2000.) For a personal workstation, I don't think you would notice the difference, until you are doing enough that you have to swap. Pushing one process out to disk while reading a new one off the disk puts strain on the disk... > Are there similar things to look for when purchasing a motherboard today? > > Please e-mail me and I will summarize to the list. > > -- > Douglas Bates[EMAIL PROTECTED] > Statistics Department608/262-2598 > University of Wisconsin - Madisonhttp://www.stat.wisc.edu/~bates/ > > Sherwood Botsford |Unsolicited email that advertises commercial Physics Dept |activities will consitute a request for U of Alberta |spellchecking of all words of less than three Edmonton, AB, |characters. I charge $US500 for this service. T6G 2J1 |There is no warranty of correctness of this service.
Re: chat bugs
On Fri, 9 Aug 1996, Yves Arrouye wrote: > > - If I put "quiet" flags (\q) on both my username and password strings, it > > only recognizes the first one, i.e., it puts my password into the log > file! > > I have only one \q for my passwd, and it's in the log file too :-(. The \q option is a toggle switch, so the second \q turns logging back on. Move the second \q after the password. btw, I had to read the chat source to discover this, so it's probably reasonable to call it a bug in the man page. Guy
No "dir" on main Debian ftp servers!
Hi there, For the last 24 hours I keep getting empty output from "ls" and "dir" on master.debian.org and ftp.i-connect.net. My guess it's some mis-configuration at these servers (aren't they the same host?). Thanks. --Amos --Amos Shapira| "Of course Australia was marked for 133 Shlomo Ben-Yosef st. | glory, for its people had been chosen Jerusalem 93 805 | by the finest judges in England." ISRAEL[EMAIL PROTECTED] | -- Anonymous
Re: MBONE crashes
> >Hi, > >in case some MBONE maniac is out there... > >I've just modified the 2.0.6 kernel for multicast support, and I started >mrouted ver 3.8. It looked fine, and we manage to establish a "tunnel" >with another remote machine connected with the rest of MBONE. But every >time I start vat or nv on a machine in the same local network where the >Linux mrouted runs, the Linux box crashes leaving a lot of messages in >/var/log/messages, starting with: > >Aug 9 10:59:28 smallLinux kernel: general protection: >Aug 9 10:59:28 smallLinux kernel: CPU:0 >Aug 9 10:59:28 smallLinux kernel: EIP:0010:[<00143c9b>] >Aug 9 10:59:28 smallLinux kernel: EFLAGS: 00010202 >... >Aug 9 10:59:28 smallLinux kernel: Aiee, killing interrupt handler >Aug 9 10:59:28 smallLinux kernel: kfree of non-kmalloced memory: >... > >Can somebody help me? > >fabrizio > Wow! This sounds interesting. I had been thinking about installing MBONE on my Linux box. If you get this to work, will you consider creating a .deb? There is a group, and a particular leader of that group, that are into MBONE, and I believe have installed MBONE on Linux. Please see hi home page and contact directly if you are interested. see http://www.epm.ornl.gov:80/~dunigan/ Keep up the good work... -- /--\ | 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: Ught Oh =O
note that some anti-virus software will decide that lilo *is* a boot sector virus :-) so you may want to just give up and use loadlin...
Linux as a 100Mb/sec router?
Anyone using Linux with Dec ethernet 100Mb ethernet cards? I'm wondering if it's suitable as I have an application that might need 2 x 100Mb ports and a 10Mb port - thinking of running it on a P120. It would need to run gated & take a full routing table ( >37K routes). Is Linux up to that yet - I havn't been following any of the networking or routing lists as of late - still running 1.2.13! Gordon
fileutils 3.13-3 seems to be messed up
I just installed fileutils 3.13-3, and now my 'ls' is screwed up. I removed color-ls as it said I was supposed to. I remember reading about how color-ls is now included in fileutils. However there is no color-ls file in my /usr/bin directory anymore, there is a dircolors file though, doing a dpkg -S dircolors tells me its from the fileutils package. Why did fileutils install dircolors and not color-ls? Am I missing something here? Thanks Shaya -- Shaya Potter [EMAIL PROTECTED]
Re: Cannot compile mouse support - help!
> The file /dev/inportbm clearly exists, it is character special (10,2) and >it does have appropriate ownership and permissions. So what does the error >"No such device" mean? "No such device" means that while the name exists in the filesystem, the kernel doesn't have any idea what c/10/2 actually *is*. Perhaps you don't have the needed support in the kernel, or the needed module loaded?
Re: catch 22?
Hi Paul -- You said: > My CD is on a SB16 card. I've told the new kernel > NOT to load modules (N to kerneld) and somehow, what is now > happening is SB driver loads during boot, and then later in the > boot process I see loading modules, and you guessed it, it loads > sbpcd as a module also! The modules listed in /etc/modules will be loaded during boot time whether or not kerneld has been enabled. > Only the module doesn't see the line > passed to the kernel specifying the parameters for sbpcd, so it > polls for every darn possible address and clone drive! Now my > systems takes about ten minutes to boot! >From the documentation in /usr/doc/modules, I would infer you have to put a line like sbpcd irq=NNN io=NNN into /etc/conf.modules. Maybe you have to give sbpcd a number like sbpcd1; I don't know. I'm also not sure of which particular arguments are accepted by this module, but I'd guess they can be deduced from the kernel sources. HTH? Susan Kleinmann
Re: How do I get GATEWAY2000 PS/2 mouse to work ? (fwd)
Hey, I had trouble with a PS/2 mouse to.. As many have.. I dont know if this will work, but it did for me. ( I even got this advice from this list a few weeks ago ). In the XF86Config file, edit it... And where it says " Device Pointer " Or somthing of that matter, it might say " /dev/mouse ".. Delete that and enter in its place " /dev/psaux " Hope this helps b4 you go through the work of re-compiling... Lata Gata Aron [EMAIL PROTECTED]
Re: Re^2: How do I get GATEWAY2000 PS/2 mouse to work ? (fwd)
on the other hand, most laptops with builtin mouse or trackball or force stick or glidepoint seem to use the PS/2 interface... which is an argument (polite request :-) for having it in the default kernel. Can't free up the IRQ in that case either...
Re: MBONE crashes
Hi -- I searched DejaNews for "mbone & linux" and got many "hits". Rather than repeat all of them here, I think it would be better if you repeated the search yourself and picked the responses that are most relevant to you. The upshot seems to be that there were multicast problems in kernels preceding 2.0.8. HTH, Susan Kleinmann
chat bugs
> On Fri, 9 Aug 1996 12:41:02 +0200, Yves Arrouye <[EMAIL PROTECTED]> said: >> - If I put "quiet" flags (\q) on both my username and password strings, it >> only recognizes the first one, i.e., it puts my password into the log file! > I have only one \q for my passwd, and it's in the log file too :-(. > Yves. I'm still scratching my head over the other oddities, but I've solved the "\q" problem: first, it turns out that the switch is a toggle! So, if you put two "\q"'s in your script, the first one turns on quiet mode, the second one turns it off! This is basically a bug in the documentation, which makes it sound as if you should put a "\q" at the start of each string you don't want logged. I put a \q at the start of my username only, and now both it and my password show in the logs as "??". Second, you need to put the whole string in single quotes, or the '\' character will be snarfed by the shell, and the wrong string will be sent to the host. -Randy -- http://cogsci.ucsd.edu/~gobbel/
Anyone know of a DHCP server for Linux that assigns addresses dynamically?
The DHCP extensions that are included in the bootp server that comes with Debian appear to require you to enter all the host information. Is this true? Are there any DHCP servers for Linux that dynamically assign IP addresses? Thanks, Al Youngwerth [EMAIL PROTECTED]
Serial ports...
On Wed, 7 Aug 1996, Richard G. Roberto wrote: > On Wed, 7 Aug 1996, Mark Phillips wrote: > > > >When installing gpm, I set my mouse device to /dev/ttys0... Then, I = > > >pointed everything else that wanted a mouse device to /dev/mouse. = > > > > What is the difference between > > > > /dev/ttys1, /dev/cua1 and /dev/mouse (a soft link) > > > > and when should each be used? > > > > Thanks, > > > > Mark Phillips. ([EMAIL PROTECTED]) > > > > > > Mark, > > This is an old explanation that I'm not sure still holds > true, but ... > > A cu device is for DCE devices (Data Communications > Equiptment), basically modems, etc. A tty device is for DTE > devices (Data Terminal Equiptment), basically terminals, > serial input devices (mice), etc. The /dev/mouse should be > a link to /dev/ttyxx where xx is probably S0 or S1, etc. > You don't need to have /dev/mouse to have the mouse work, > its just there to conveniently identify the mouse port. > > I hope that's helpful, and if anybody knows a better, more > modern explanation, please do :-) > CAVEAT I'm an ignoramlepuss about Linux/Debian. Under Nextstep, the serial ports work like this: /dev/ttya /dev/ttya (/dev/ttyb) is used for "incoming" connections from directly connected terminals without CTS/RTS flow control. When /dev/ttya is open(2)'ed, the device driver asserts the DTR (data terminal ready) signal. Opens of the /dev/ttya device name do NOT block waiting for the RS-232 DCD (car- rier detect) signal to be asserted. /dev/ttya should be specified in the file /etc/ttys for directly connected terminals. If a serial line is opened with the /dev/ttya device name, it may not be opened with the /dev/ttyda or /dev/cua device names. /dev/ttyfa /dev/ttyfa (/dev/ttyfb) operates identically to /dev/ttya except that RTS/CTS flow control is supported on 68040-based systems. See the section below on RTC/CTS flow control. /dev/ttyda /dev/ttyda (/dev/ttydb) is used for "incom- ing" connections from modems. When /dev/ttyda is opened, the device driver asserts DTR and then blocks waiting for the modem to assert DCD (indicating that a con- nection has been established with a remote modem). When DCD is asserted by the modem the open system call returns. If DCD is deasserted by the modem, further reads and writes to the device will return the error EIO (i/o error); if the tty is the control- ling terminal for the process a SIGHUP will be sent to the process. /dev/ttyda is typically used in the file /etc/ttys for connecting modems used for dial-up logins. If a serial line is opened with the /dev/ttyda device name, it may not be opened with the /dev/ttya. A serial line opened with the /dev/ttyda device name may also be opened with the /dev/cua device name. Inter- locks between the /dev/ttyda and /dev/cua device names are described below. /dev/ttydfa/dev/ttydfa (/dev/ttydfb) operates identi- cally to /dev/ttyda except that RTS/CTS flow control is supported on 68040-based systems. See the section below on RTC/CTS flow con- trol. /dev/cua /dev/cua (/dev/cub) is used for "outgoing" connections to auto-dial modems. When /dev/cua is opened, the device driver asserts DTR and does NOT block waiting for the modem to assert DCD. No action is taken by the driver when the modem asserts or de- asserts DCD. /dev/cua is typically used by programs like "uucp" and "tip" that need access to auto- dial modems. If a serial line is opened with the /dev/cua device name, it may not be opened with /dev/ttya. A serial line opened with the /dev/cua device name may also be opened with the /dev/ttyda device name. Interlocks between the /dev/ttyda and /dev/cua device names are described below. /dev/cufa /dev/cufa (/dev/cufb) operates identically to /dev/cua except that RTS/CTS f
diald
Does anyone know how to get diald to work? I'm almost there; I can get it to do it's thing, dial, connect to my ISP, start sending data, but after about 30 seconds, diald kills pppd, and reports that it has timed out waiting for ppp to connect. :/ Since I was in the middle of receiving an html document from the web, I'd say it's safe to assume that pppd was already connected. Anyone got any ideas how I can cure this VERY annoying problem? Thanks, Tim --- I am Pentium of Borg. Division is futile. You will be APPROXIMATED! [EMAIL PROTECTED] <-- (Primary email) ---
installation boot fails with standard bootdisk on 486SX/33
Installation fails on this old machine shortly after hitting return at the 'Boot Parameters' prompt using the standard bootdisk. Linux 1.2.13 runs fine. I suspect (based upon bug reports) that APM is enabled in the kernel on the standard bootdisk and that this is the problem. I propose to install on another machine and create a custom bootdisk for this old (but useful) dog. Does anyone have any pointers or is there a suitable bootdisk image somewhere I can use? I am installing from the August Pacific HiTech CD and have internet access. Thanks, Michael Laing
Re: Ught Oh =O
> Heh, I have a problem. > I got a virus on my Windows partition ( And YES I did scan it first with > norton ). > But After I debugged, and fixed as much as I could, everything looked > good... > But now on boot up - LILO dosent show... It just boots into win - blows ( > oops, I meant Wondows ;). Hmm. Looks like something (the virus, windows95 during a reinstall or perhaps your anti-virus software) overwrote your master boot record. > Is there some string or sommand I enter in > somewhere ? any advice ? > ( Please take in mind I have only had Linux for about 3 weeks ). Here's what should work: - Get or remake the Debian boot disk (first disk of the 6-set) using rawrite. - Boot with that disk. On the lilo prompt, press tab and say Linux root=/dev/hda4 ro (presuming /dev/hda4 == 4th partition on first drive) is your Linux root partition. - Linux should boot more or less normal now. Log in, and rerun "lilo". Hope this helps, Ray -- UNFAIR Term applied to advantages enjoyed by other people which we tried to cheat them out of and didn't manage. See also DISHONESTY, SNEAKY, UNDERHAND and JUST LUCKY I GUESS. - The Hipcrime Vocab by Chad C. Mulligan
MBONE crashes
Hi, in case some MBONE maniac is out there... I've just modified the 2.0.6 kernel for multicast support, and I started mrouted ver 3.8. It looked fine, and we manage to establish a "tunnel" with another remote machine connected with the rest of MBONE. But every time I start vat or nv on a machine in the same local network where the Linux mrouted runs, the Linux box crashes leaving a lot of messages in /var/log/messages, starting with: Aug 9 10:59:28 smallLinux kernel: general protection: Aug 9 10:59:28 smallLinux kernel: CPU:0 Aug 9 10:59:28 smallLinux kernel: EIP:0010:[<00143c9b>] Aug 9 10:59:28 smallLinux kernel: EFLAGS: 00010202 ... Aug 9 10:59:28 smallLinux kernel: Aiee, killing interrupt handler Aug 9 10:59:28 smallLinux kernel: kfree of non-kmalloced memory: ... Can somebody help me? fabrizio
chat bugs
> - If I put "quiet" flags (\q) on both my username and password strings, it > only recognizes the first one, i.e., it puts my password into the log file! I have only one \q for my passwd, and it's in the log file too :-(. Yves.
Re: Help needed using Sun 'automount' map with Debian's amd.
> > Err. doesn't seem to be in my /usr/doc/amd: > Ah, silly me. That should have been /usr/doc/examples/amd ... As for the documentation, try 'info amd'. Yours, Dominik Kubla
Re^2: How do I get GATEWAY2000 PS/2 mouse to work ? (fwd)
> On Thu, 8 Aug 1996, Mike Taylor wrote: > Lots of people seem to have problems getting PS2 mice up. My Gateway + > PS2 worked fine under Slackware 3.0, but I still can't get it to work > under Debian. I have tried all the stuff that you tried plus > compiling a custom kernel (with the Debian source package) but no dice. > My (admittedly cowardly) solution: cheap serial mouse. My experience is that there are a couple of good hardware reasons for getting serial mice instead of PS/2 mice: -- we accidentally fried a BIOS chip by delivering a static charge through a PS/2 mouse. This has never happened with a serial mouse, and leads me to suspect that the PS/2 connector (or at least the connector we used to have on our R.I.P. Asus '486 motherboard) is less robust against static than an serial connector. -- removing the PS/2 mouse frees up an IRQ. -- one never knows if/when PS/2 mouse is going to be available in a downloaded kernel, whereas serial support is virtually always there. I have had some problems with some serial mice though, particularly those cheap ones which change their state when the power goes off. Cheers, Susan Kleinmann
Re: nfs.o module in version 2.0.6
Why has this been on the ftp site for weeks now? NFS installation is all we do around here and the "fixed" version is one that does not work. Mr A Birdi ([EMAIL PROTECTED]) wrote: : : : Dear users, : : This is in reply to some of the queries regarding the nfs module in : version 2.0.6 of the kernel. At least two people have responded with : the advice to recompile the kernel which seems to be a succesful : approach. : : I have discovered however that the problem lies with the module nfs.o : itself. Lazaro Salem ([EMAIL PROTECTED]) was kind enough to send me : his recompiled version of nfs.o which works fine with the kernel : supplied with Debian 1.1.3. Thus, a solution to the problem is to : merely recompile the module and not necessarilly the entire kernel. If : there is enough interest, I can upload the nfs.o module which Lazaro : supplied to me to some public site until the Debian maintainers fix : the problem. Please write me if you would like this to happen. : : Alvin : : -- : - :| Alvin BirdiEmail: [EMAIL PROTECTED] | :| School of Economic Studies Tel: 0161 275-4791 | :| University of Manchester Fax: 0161 275-4812 | :| Manchester M13 9PL UK | : - :
Re: Consensus about /bin/perl.
On 8 Aug 1996, Rob Browning wrote: > > So what was the decision about /bin/perl, and the packages that depend > on it right now (kernel-*, etc). Should it be a symlink, or should > these packages just be fixed? In a nutshell, all perl scripts should use /usr/bin/perl, *not* /bin/perl. Christian
HELP color-ls not working.....
I get the following when I eval color-ls, but do not get colors... As you can see, I did do the color=yes thingy any help would be appreciated... LS_COLORS='no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:'; export LS_COLORS; LS_OPTIONS='--8bit --color=tty -F'; export LS_OPTIONS; alias ls='/usr/bin/color-ls $LS_OPTIONS '; alias dir='/usr/bin/color-ls $LS_OPTIONS --format=vertical'; alias vdir='/usr/bin/color-ls $LS_OPTIONS --format=long'; alias d=dir; alias v=vdir; Thank you, mike cotherman [EMAIL PROTECTED]
Re: linux.debian.user newsgroup (Re: printing and .profile problems)
In your email to me, Stuart Lamble, you wrote: > > In article <[EMAIL PROTECTED]> Susan Kleinmann wrote: > : > : Hi Chris -- > : > : You said: > : > I tried to post to the linux.debian.user newsgroup without success. > > : There isn't any newsgroup -- just this mailing list. > > Actually, linux.debian.user exists, but it appears to be a gateway from > the mailing list to USENET - it doesn't seem to work the other way > around. :-( I can read from it, but it doesn't seem to reach the mailing > list if I post to it. Ah... then your news person doesn't have the news set up correctly. The list is moderated, so it should get mailed when you try to post to it. Tim -- [EMAIL PROTECTED] "I believe the children are our future. Teach them well and let them lead the way." -- George Benson "The Greatest Love of All" ** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.**
Re: catch 22?
Thanks to all the Debian L'ers for the suggestions on how to deal with this problem, especially Dwarf, Guy, Jim and Heiko. I did manage to correctly get a fresh source and image installed by using Heiko's suggestion (or a very close version of it)! I changed the status file to read " purge ok not-installed" and that did fake out dpkg. Thanks guys! Appreciate all the help. But, now, another has shown up! You guys are gonna get tired of me stumbling around. Seems if I didn't have bad luck, I'd have none at all. My CD is on a SB16 card. I've told the new kernel NOT to load modules (N to kerneld) and somehow, what is now happening is SB driver loads during boot, and then later in the boot process I see loading modules, and you guessed it, it loads sbpcd as a module also! Only the module doesn't see the line passed to the kernel specifying the parameters for sbpcd, so it polls for every darn possible address and clone drive! Now my systems takes about ten minutes to boot! Almost as long as my Vax's at work! :-) Anyone tell me what question I answered wrong to cause this? Paul
Re: Cannot compile mouse support - help!
Hi again all, This is a narrowing-down question to my earlier post. What does it mean when gpm gives me the following error message: gpm: /dev/inportbm: No such device The file /dev/inportbm clearly exists, it is character special (10,2) and it does have appropriate ownership and permissions. So what does the error "No such device" mean? Thanks. -jj
Re: chat bugs
Randy Gobbel <[EMAIL PROTECTED]> writes: > I installed Debian Linux 1.1 on my new Pentium Pro a couple of weeks ago. so > far everything mostly works great, but I've noticed that the chat program > seems to have a number of problems: Just a personal experience: I had all kinds of trouble with the modem that came with my Gateway 2000 (the Telepath internal -- almost a Sportster, made by USR for Gateway). I had dropped connections, chat problems with recognizing REPORT and ABORT strings, etc. When I recently replaced it with an external Courier, *all* the problems vanished. Anyone want a cheap internal modem :> -- Rob
Re: How do I get GATEWAY2000 PS/2 mouse to work ? (fwd)
On Thu, 8 Aug 1996, Mark Edward Johnston wrote: > > I have installed Linux (Debian 1.1) on a friend's computer, > but can't get X to work as it complains about not being able to > find the mouse. > > The system is a Gateway 2000 DX2/66 with Cirrus Logic 5434 > and what seems to be a "PS/2" mouse. > > I have linked /dev/mouse -> /dev/psmouse (-> /dev/psaux) > and set Protocol and Device in XF86Config to "PS/2" and > "/dev/mouse" respectively. > > Any help would be appreciated, > > Mark Johnston ([EMAIL PROTECTED]) > > > PS: Does anybody know if PS/2 mouse support is in the default kernel in > Debian 1.1.3 ?? Is this a valid question ? > > > > > PS/2 support is not there for 1.1.2. I suspect it is not there for 1.1.3. To get it you will have to use a special kernel or compile one yourself. Lots of people seem to have problems getting PS2 mice up. My Gateway + PS2 worked fine under Slackware 3.0, but I still can't get it to work under Debian. I have tried all the stuff that you tried plus compiling a custom kernel (with the Debian source package) but no dice. My (admittedly cowardly) solution: cheap serial mouse. Mike
Re: The "*" character (was: Latex )
if you prefer the bash behavior of ignoring the pattern failure, just set nonomatch in tcsh or csh.
Re: Anyone want xanim as a deb package
Michael Alan Dorman writes: -> Shaya Potter <[EMAIL PROTECTED]> writes: -> -> > I just got xanim compiled on my system with full for cinepack and indeo -> > enconding, I also compiled in sound, but I have no idea if it works since -> > I don't have a sound card on my linux box. If anyone want it, I will try -> > to put it together as a package. It should be pretty easy just one file -> > is neccesary to run it. -> -> Please be sure to check on the redistributability of the cinepak and -> indeo code---I'm not sure it can be redistributed _at all_, and I'm -> fairly certain that it would have to go in non-free. xanim compiled with the cinepack and indeo codecs would almost certainly have to go in as non-free. As a matter of fact, the cinepack and indeo codecs are not distributed as source, but as object files. Not sure what the 'rules' are regarding that. -Larry -- Larry Daffner| Linux: Unleash the workstation in your PC! [EMAIL PROTECTED] / http://web2.airmail.net/vizzie/ "I believe every human has a finite number of heartbeats. I don't intend to waste any of mine running around doing exercises." --Neil Armstrong
Re: Consensus about /bin/perl.
Rob Browning <[EMAIL PROTECTED]> writes: > So what was the decision about /bin/perl, and the packages that depend > on it right now (kernel-*, etc). Should it be a symlink, or should > these packages just be fixed? > > Just wanted to know so know whether or not I should create the link or > patch the scripts on my systems. The Linux FSSTND 1.2 clearly says: /usr/bin/perl, /usr/bin/python, and /usr/bin/tcl should reference the perl, python, and tcl shell interpreters, respectively. They may be symlinks to the physical location of the shell interpreters. It would make sense to have scripts access it where you can expect it. FSSTND compliant Perl scripts would definitely use /usr/bin/perl. Dan -- Daniel Quinlan <[EMAIL PROTECTED]> / Member of the LPF http://www.bucknell.edu/~quinlan / http://www.lpf.org
The "*" character (was: Latex )
Mark Phillips writes: > >It would be helpful if you could tell us what version of the packages > >you have installed. For example, if you would run this commands: > > > > dpkg -l *tex* > > I noticed that this doesn't work under tcsh, but does work under > bash. Is there a difference between how the * character is treated > under the two shells? It differs from shell to shell and even within a given shell: marin215# tcsh # echo *tex* echo: No match. # set nonomatch # echo *tex* *tex* # In csh, having nonomatch set asks the shell not to say it can't do a wildcard expansion but rather to pass the argument (as if it was quoted, then) to the command. The surest way to get consistent results is to quote ;-) Yves.
Re: How do I get GATEWAY2000 PS/2 mouse to work ? (fwd)
Mark Edward Johnston wrote: > > I have installed Linux (Debian 1.1) on a friend's computer, > but can't get X to work as it complains about not being able to > find the mouse. > > The system is a Gateway 2000 DX2/66 with Cirrus Logic 5434 > and what seems to be a "PS/2" mouse. > > I have linked /dev/mouse -> /dev/psmouse (-> /dev/psaux) > and set Protocol and Device in XF86Config to "PS/2" and > "/dev/mouse" respectively. > > Any help would be appreciated, > > Mark Johnston ([EMAIL PROTECTED]) > > PS: Does anybody know if PS/2 mouse support is in the default kernel in > Debian 1.1.3 ?? Is this a valid question ? As I and a friend frieend with a Gateway 2000 have finally discovered, that is a very good question. No, PS/2 mouse support is not in not compiled in and doesn't appear to be available as a module. You'll need to reconfigure and recompile. Once you have installed the kernel-source package you want, follow the directions in /usr/src/linux/debian.README. I hope this helps.
Re: Nearly perfect!
About that uucp SMART_HOST line again, try using the uucp-dom mailer rather than the std. uucp mailer. It uses the smtp mailer rules for rewriting envelope addresses. Aside from that, youd have to show uucico logs for both sides to make sure the mail was still addressed correctly on the server side. -- === = Randall Shutt = = RaveNet Systems, Inc= ===
Re: Anyone want xanim as a deb package
On 8 Aug 1996, Michael Alan Dorman wrote: > Shaya Potter <[EMAIL PROTECTED]> writes: > > > I just got xanim compiled on my system with full for cinepack and indeo > > enconding, I also compiled in sound, but I have no idea if it works since > > I don't have a sound card on my linux box. If anyone want it, I will try > > to put it together as a package. It should be pretty easy just one file > > is neccesary to run it. > > Please be sure to check on the redistributability of the cinepak and > indeo code---I'm not sure it can be redistributed _at all_, and I'm > fairly certain that it would have to go in non-free. > > Which isn't to say I wouldn't like to see the package---just that this > is one that probably needs all its proverbial ts crossed and is dotted. > > Mike. > I talked to Mark Podlipec, the author, and he said that there should be no problem of just giving the binary away, the only problem is if you give away the .o files that you download form Mark's ftp site and compile in. If I were to give those away I would have to distribute the copyright notices also. However, it still has to be in the non-free section because Mark's copyright says that only non-commercial use is permitted. I will include the copyright notices for all the included software though, to be on the safe side, even though Mark said it isn't neccessary. Shaya -- Shaya Potter [EMAIL PROTECTED]
About CD delivery delays from I-Connect and Bruce Perens
Simon Shapiro of I-Connect and I both had serious family emergencies at the same time. I lost about a week of work time, I don't know how much Simon is losing. Please bear with us if you are waiting for a CD. Thanks Bruce
Re: Floppy won't boot with internal cache enabled
On Thu, 8 Aug 1996 [EMAIL PROTECTED] wrote: > > ... Don't forget > >to pop out and replace the floppy - the data could be read from a disk > >block cache rather than the floppy if you don't do that. ... > > Does this note mean that one can replace floppy disks without unmounting > and mounting in between? Or were the 'umount' and 'mount' implied by > "pop out"? If they were, wouldn't the 'umount' and 'mount' alone be > sufficient without physically removing the disk? There are other ways to get data from a floppy besides mounting and unmounting, mtools or just raw data (ie - dd). Those could be fooled but shouldn't be on most floppy drive. Use fdflush if you're nervous. Guy
Re: Floppy won't boot with internal cache enabled
> ... Don't forget >to pop out and replace the floppy - the data could be read from a disk >block cache rather than the floppy if you don't do that. ... Does this note mean that one can replace floppy disks without unmounting and mounting in between? Or were the 'umount' and 'mount' implied by "pop out"? If they were, wouldn't the 'umount' and 'mount' alone be sufficient without physically removing the disk? Just Curious
chat bugs
I installed Debian Linux 1.1 on my new Pentium Pro a couple of weeks ago. so far everything mostly works great, but I've noticed that the chat program seems to have a number of problems: - If I put ABORT "NO CARRIER" in my script, it sometimes erroneously aborts when it sees a "CARRIER 28800" message (but works most of the time). - If I put "quiet" flags (\q) on both my username and password strings, it only recognizes the first one, i.e., it puts my password into the log file! - I tried to put a second "TIMEOUT" string into the script, to make it shorter after the initial prompt was detected, but instead of taking it as a timeout directive, it just looks for the string "TIMEOUT" coming over the connection. Has anyone else noticed similar problems? I'm going to take a look at the source, and will fix the bug if I find it. -Randy -- http://cogsci.ucsd.edu/~gobbel/
Real Audio
Greetings .. Has anyone had any luck getting the real audio client to run on your Debina Linux Box. I'm not sure if there is some sort of sound driver incompatibility or not, but I've tried installing the most recent kernel 2.0.6 (from debian source) and the most recent USS/Lite sound driver. Whenever the real audio client tries to run all I get is static. I am using the most recent debian packages (stable) TIA, Michael
More questions on upgrading...
Hi! I've mirrored most of the debian distribution, and I've gone thru the select process in dselect. Basically I'm ready to perform a full upgrade to Debian-1.1 now. But I'm still weary of doing it because I don't want to have much downtime since my server is used for others dialing in. My main question is: Debian-1.1 is all ELF. My current system is a.out, including the kernel. If I go ahead with the upgrade from dselect, will my current 1.2.13-a.out kernel still be useable once the upgrade is complete? Or will I have to upgrade the kernel as well (which means I'd have to immediately reboot the server). I want to be able to go thru with the upgrade but not reboot immediately. I want to keep the server running while I go thru the kernel upgrade process (like compiling a new 2.0.x kernel). Also, will the current mgetty and pppd I have (a.out) work with the upgraded Debian? I will still upgrade those, but, similar to the kernel issue, I'd like to be able to continue using my current mgetty/pppd setup and upgrade those in a timely fasion. Suggestions are welcome! :) Ricardo
Re: linux.debian.user newsgroup (Re: printing and .profile problems)
In article <[EMAIL PROTECTED]>, Stuart Lamble <[EMAIL PROTECTED]> wrote: >Actually, linux.debian.user exists, but it appears to be a gateway from >the mailing list to USENET - it doesn't seem to work the other way >around. :-( I can read from it, but it doesn't seem to reach the mailing >list if I post to it. Indeed you cannot post to it. The linux.* groups should be set as _moderated_ groups, and you'll have to have a few special addresses in your moderators file. I'll include them below. Fix your news server or ask your provider to fix it. Proof of this is that I _am_ writing this from trn :) # Linux moderators host. linux.act.*:[EMAIL PROTECTED] linux.*:[EMAIL PROTECTED] Mike. -- Miquel van| Cistron Internet Services --Alphen aan den Rijn. Smoorenburg, | mailto:[EMAIL PROTECTED] http://www.cistron.nl/ [EMAIL PROTECTED] | Tel: +31-172-419445 (Voice) 430979 (Fax) 442580 (Data)
Re: The "*" character (was: Latex )
> >It would be helpful if you could tell us what version of the packages > >you have installed. For example, if you would run this commands: > > > > dpkg -l *tex* > > I noticed that this doesn't work under tcsh, but does work under > bash. Is there a difference between how the * character is treated > under the two shells? '*tex*' works with both shells. bash will not replace a clobber pattern with the empty string if no match is found, tcsh does (AFAIK). bash(1) # Pathname Expansion # After word splitting, unless the -f option has been set, # bash scans each word for the characters *, ?, and [. If # one of these characters appears, then the word is regarded # as a pattern, and replaced with an alphabetically sorted # list of pathnames matching the pattern. If no matching # pathnamesarefound,and the shell variable # allow_null_glob_expansion is unset, the word is left # unchanged. If the variable is set, and no matches are # found, the word is removed. When a pattern is used for # pathname generation, the character `.'' at the start of # a name or immediately following a slash must be matched # explicitly, unless the shell variable glob_dot_filenames # is set. The slash character must always be matched # explicitly. In other cases, the `.'' character is not # treated specially. and bash(1) set # -u Treat unset variables as an error when per- # forming parameter expansion. If expansion # is attempted on an unset variable, the # shell prints an error message, and, if not # interactive, exits with a non-zero status. # 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
Re: IP forwarding and/or Masquerading
On 8 Aug 1996, Kai Grossjohann wrote: > Type `route' and see what kinds of routes you have. I had to add the > following command to my /etc/ppp/ip-up script: > > route add -net default ippp0 Putting `default' in /etc/ppp/options should also work. Guy
Re: Help needed using Sun 'automount' map with Debian's amd.
On Thu, 8 Aug 1996, Dominik Kubla wrote: > > Look at /usr/doc/amd there is a (untested!) script to convert automount to > amd maps. Err. doesn't seem to be in my /usr/doc/amd: [EMAIL PROTECTED]:[/usr/doc/amd] #ls -la total 5 drwxr-xr-x 2 root root 1024 Jun 13 09:37 ./ drwxr-xr-x 105 root root 3072 Aug 2 13:50 ../ -rw-r--r-- 1 root root 635 May 18 16:31 KNOWN_BUGS [EMAIL PROTECTED]:[/usr/doc/amd] #dpkg -l amd Desired=Unknown/Install/Remove/Purge | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ NameVersionDescription +++-===-==- ii amd upl102-3 The 4.4BSD automounter. ... And 'upl102-3' is the most recent version on ftp.debian.org (and there's no amd waiting in Incoming). A script would nice... what would have been nicer is if they had been compatible with each other. But hey, this is Unix. They *had* to be incompatible, just for the princple of the thing. Btw, could explain to me the format of amd's map... The manpage isn't very verbose on the topic: Lookups within the speci fied directories are handled by amd, which uses the map defined by mapname to determine how to resolve the lookup. Generally, this will be a host name, some filesystem information and some mount options for the given filesys tem. The last sentence is all we get for a description of the format. (In fact I'm very much tempted to file that as a bug against amd. Can I? :-) ) It's a bit like saying the fstab format is a "generally a device, a mount point and some mount options"... *not* good enough if you've never seen a fstab. Thanks in advance for your help... Christian
Ught Oh =O
Hey everyone, Ught.. U... Ohhh... Heh, I have a problem. I got a virus on my Windows partition ( And YES I did scan it first with norton ). But After I debugged, and fixed as much as I could, everything looked good... But now on boot up - LILO dosent show... It just boots into win - blows ( oops, I meant Wondows ;). Is there some string or sommand I enter in somewhere ? any advice ? ( Please take in mind I have only had Linux for about 3 weeks ). Aron [EMAIL PROTECTED] [EMAIL PROTECTED]
