Re: Documentation - I see squares
In a lot of man pages, and some of the documentation in /usr/doc there are there little squares or cryptic $%^ thingees. I guess that there's something I've missed somewhere... What have/haven't I done? On the assumption that you ran into some highlighting or underlining markup, then you might try running your documents through a smart pager that's able to do something reasonable with such things. Try this: export MANPAGER=/usr/bin/less (Of course, this only works if you have the 'less' package installed.) If it works for you, then you might want to put this line into your .bashrc or whatever startup script you use. If the problem is that the documents you're looking at are gzip'd then you'll want to read them with zless, by executing, e.g., zless /usr/doc/man/README.gz I don't think that's the problem, less is my PAGER, and I know about zcat. Most of the text is quite readable. The little squares are often where I'd expect an apostrophe to be, and some of the funny codes are B7 for example. It looks like a bit of hex. John F.
Re: Why is PPP so screwed up!?!?!
Cool off, man. What they seem to be talking about IS a Debian issue. Although ppp support IS compiled into the kernel, the pppd is separate, and the method by which you establish a connection, be it through pon, or a custom script like I use, because as far as I know pon will not redial through busy signals, IS a function of your distribution. When you have to run a script that invokes chat, or does whatever to make a ppp connection, and you're trying to figure out what options to use for pppd, I don't think that the proper response is that it is a kernel only issue so stop bitching about it here. Besides, half of this thread seems to be about the fact that Debian in general is not intutive to set up, whether it is your ppp connect script or whatever, and I agree, there does need to be some progress in this area. I think that this is single largest drawback to the Debian distribution in my opinion. Regardless, screaming at people for discussion ppp configuration in the Debian user list is definately not the answer, especially since everything to do with setting up ppp is NOT a kernel issue. Shawn Asmussen On Sun, 2 Mar 1997 [EMAIL PROTECTED] wrote: thats intuitive Why can't you guys give it up! ITs not a Debian thing dude! Its compiled into the kernel itself (ppp support). It is NOT a Debian issue! I do agree that someone (how about you?) could make it better by writing something, from your perspective that might help. BUT STOP PUTTING IT ON DEBIAN, OR ANY OTHER DISTRIBUTION! If you want to see more of it, monitor the FreeBSD questions forum sometime! FreeBSD supports two (different) ways of invoking PPP to establish a net link. If you want to do some serious whinning about it, try FreeBSD! Now, quit the bitchin' and get busy putting your ideas down so it will benefit everyone else. Thats the idea here. You guys been bantering this back and forth for over a week now. All the whinin' and cryin' won't make a damn bit of difference. So, knock it off, and put your energy to good use. Or, go somewhere else and bitch.
Re: lprm says Permission denied (fwd)
On Sun, 2 Mar 1997, Hamish Moffatt wrote: On Mar 03, 1997 at 08:58:41PM +1100, Craig Sanders wrote: well, actually i had a few initial hassles getting the win95 box to print with the PCL driver. Postscript worked fine (through ghostscript to my HP4L), but PCL failed. Eventually somebody on debian-user suggested that I put check_for_nonprintable no in /etc/lpd.conf - as Strange, because I don't have that in smb.conf, and I print PCL to my new HP5L from Win95 boxes just fine. The 'check_for_nonprintable' is in lpd.conf, NOT smb.conf. I vaguely recall that this was such a FAQ that it was made the default setting (dont take my word for it though) Craig
Re: Procmail recipe.
On Sun, 2 Mar 1997, Elie Rosenblum wrote: Or you could just use the built in macros ^TO and ^FROM: :0 * ^TO.*debian-user * ^FROM.*debian-user debian-user-l-inbox Since ^TO will match all the addressing mechanisms procmail can check, To:, Apparently-To:, Cc:, and any others it knows about. In fact, the ^FROM should be rather extraneous (and anyway, the debian list server doesn't rewrite the headers the way I like them, so it doesn't do redirects right). I find that this doesn't work reliably (i'm not sure if the two * lines are ANDed or ORed - I think it's AND). I have to do something like: :0 E * ^TO.*debian-user $MAIL/Lists/debian/user/incoming :0 E * ^FROM.*debian-user $MAIL/Lists/debian/user/incoming Craig
Re: Mail list problems??
On Sun, 2 Mar 1997, Gregory Vence wrote: It's happening to me too. Scott Stanley wrote: Every time I post to the debian user mail list I am getting 5-10 error messages saying the mail could not be delivered. Although, I do get a copy of the mail sent back to me from the list. I am wondering if this is related to the problems with the mail list, or if I am the only one getting these errors Scott Bruce is working on fixing it. At least debian-user and debian-devel seem to have this problem. Look for some receint posts by him with 'mail' in the title. I don't know if he said a time frame. He's just working on it. Enjoy -- Greg. -=- Daniel Robbins School of Medicine Computer Services University of New Mexico [email:[EMAIL PROTECTED]
Problems with FVWM-2
I upgraded to fvwm2 today and ran into a few problems. Some of these may be worthy of bug reports, but I thought I'd mention them here first. - The postinst of fvwm2 fails if you ask it to convert fvwm1 rc files to the new format and gawk is not present. fvwm2 should either depend on gawk or the postinst should just ignore this error. The source of the error was found by trying to run fvwmrc_convert by hand. - The .fvwm2/init.hook would not be executed unless I added the line AddToFunc InitFunction as the end of the .fvwm2/post.hook file. Without this line, it was as though the init.hook file didn't even exist. - When using desktops, a keybinding of Key F1 A M Desk 0 1 Key F2 A M Desk 0 2 Key F3 A M Desk 0 3 Key F4 A M Desk 0 4 Key F5 A M Desk 0 5 Key F6 A M Desk 0 6 Key F7 A M Desk 0 7 Key F8 A M Desk 0 8 would not work when the mouse was on the root window. I tried other settings other than A and could get none to flip screens unless the mouse was on top of a window. I have since switched back to the larger desktop (instead af multiple desktops) and use the above keybindings with with the GotoPage function and everything works fine. - The FvwmPager does not have the correct aspect ration. Each of the virtual screens is a long and narrow rectangle instead of a square. The horizontal scale seems to be about 3/4 of what it was under fvwm1. I have no reference to compare the vertical scale. Brian ( [EMAIL PROTECTED] ) --- measure with micrometer, mark with chalk, cut with axe, hope like hell
Re: does anyone mind if I post my ppp output...
On Sun, 2 Mar 1997, Richard Morin wrote: Sorry to carry the ppp thing on, but I just can't get it to work with pon. I currently dial in with minicom and evoke pppd manually. Does anyone mind if I post the output from both to see what I'm not doing right? I'll send private if anyone volunteers to have a look. IMO, sending your output is the correct thing to do. It is much more productive than discussions about the virtues of a user friendly ppp setup which does not presently exist. Unfortunately, I'm no ppp expert, so I'm not likely to have the right answer. But, please do post real technical questions to the list. That's what the list is for. Thanks. Syrus. -- Syrus Nemat-Nasser [EMAIL PROTECTED]UCSD Physics Dept.
Re: Procmail recipe.
On Sun, 2 Mar 1997, Elie Rosenblum wrote: * ^From .*debian-user* * ^To: .*debian-user* * ^Cc: .*debian-user* even more tidy: * ^(From|To|Cc):.*debian -!-
Re: 56k baud modem (x2)
I'm refering to using the 56k upgrade to their 33.6 modems. It's some kind of driver (not ISDN) for working on regular analog lines. It might be something that reloads EEPROM or such. I'm looking for success and real connect speeds. Sometimes people with 33.6k only get on at 28.8k or 24k. From looking at it, and reading other lists, the other end has to have a digital connection. So, you can't just connect 56k user - 56k user... it must be done 56k user - 56k provider with special USR gear. Also, I remember bringing up the fact that its illegal (in the US) to run at speeds over 46k (or similar) over the analog lines... so legally, you can't go that fast. I'm assuming that this is going to be overturned shortly, since several companies are coming up with 56k technology. I personally would just assume go ISDN.
Re: 56k baud modem (x2)
Is the 56kb USR upgrade compatible with linux? I tired of 14.4. Almost certainly. I use a 56K ISDN 'pseudo-modem' all the time. Even though this box isn't internally the same as the real USR modem [snip] I'm refering to using the 56k upgrade to their 33.6 modems. It's some kind of driver (not ISDN) for working on regular analog lines. It might be something that reloads EEPROM or such. I'm looking for success and real connect speeds. Sometimes people with 33.6k only get on at 28.8k or 24k. I haven't used the 56k modem myself, I'm just relaying what I've heard on an ISP mailing list... 33.6k is pushing the limit of a regular analog line. The 56k X2 modem requires that the ISP have a digital connection to the telco. That means that the connection between you and your ISP is half digital: you --analog-- telco --digital-- ISP If the setup is the regular analog only connection, it is very unlikely that you will get faster than 33.6k. In all probability, if you can't get 33.6k with your current line, you won't be able to get 56k either. 2nd hand info. Take it fer what it's worth.
Printer problem
This is not a debian specific problem, but since I am running debian this is as good a place as any to post. I just bought an Epson Stylus color 500 printer. When I print a document generated by LaTeX, converted to postscript with dvips, only part of the page is printed. The rest is printed on the following page. Then another new page is started with the next new page of the document. When I preview with ghostscript, the page layout is fine. When I try to print color output, using the stcolor device in ghostscript, pages just run through the printer, getting no output. The pertinent entries from my printcap follow ... ps|ps|ps|Epson Stylus Color 500:\ :lp=/dev/lp1:sd=/var/spool/lpd/lp:\ :sh:pw#80:pl#72:px#1440:mx#0:\ :if=//usr/spool/lpd/lp/psfilter:\ :af=/var/log/lp-acct:lf=/var/log/lp-errs: color|color|color|Epson Stylus Color 500:\ :lp=/dev/lp1:sd=/var/spool/lpd/lp:\ :sh:pw#80:pl#72:px#1440:mx#0:\ :if=//usr/spool/lpd/lp/colorpsfilter:\ :af=/var/log/lp-acct:lf=/var/log/lp-errs: Here is /usr/spool/lpd/lp/psfilter ... #!/bin/sh /usr/bin/gs -sDEVICE=eps9high -sOutputFile=- -q - and /usr/spool/lpd/lp/colorpsfilter ... #!/bin/sh /usr/bin/gs -sDEVICE=stcolor -sOutputFile=- -q - Thanks for any help. Wayne +---+ | R. Wayne McCorkleVoice: (505) 522-9236| | New Mexico State University Fax: (505) 522-9389| | Physical Science Laboratory Email: [EMAIL PROTECTED] | | Computation and Simulation Division URL: http://essex.nmsu.edu/~rmccorkl | +---+
Re: Why is PPP so screwed up!?!?!
Shawn, Well, I respectively disagree. This thread has been going for so long, most of the chatter is NOT about how to establish a connect. What I was seeing here was all this crap about how screwed up Debian was, and how screwed up PPP was, and The real truth is that if someone sees a NEED, like I said, then they should do something about it, if they can, and to Debian for the benefit of all. One message after another, that if uSlop this, or uSlop that just ticked me off! I've been on this list for over two years now, don't post many messages to be sure, but I had seen my fill the last few weeks with all the attacks on Bruce, for this and that, and this damn thing got started. I'd seen enough. If you think the doc is lacking than write some, if you're capable. I read the list to learn something and to follow the Debian development, and personnally I think these guys do a terrrific job with it. If you are capable and able, help them out by adding something where you see a need. I'm not capable of that, or knowledgeable enough. But all this whining don't get it either. Paul Why can't you guys give it up! ITs not a Debian thing dude! Its compiled into the kernel itself (ppp support). It is NOT a Debian issue! I do agree that someone (how about you?) could make it better by writing something, from your perspective that might help. BUT STOP PUTTING IT ON DEBIAN, OR ANY OTHER DISTRIBUTION! If you want to see more of it, monitor the FreeBSD questions forum sometime! FreeBSD supports two (different) ways of invoking PPP to establish a net link. If you want to do some serious whinning about it, try FreeBSD! Now, quit the bitchin' and get busy putting your ideas down so it will benefit everyone else. Thats the idea here. You guys been bantering this back and forth for over a week now. All the whinin' and cryin' won't make a damn bit of difference. So, knock it off, and put your energy to good use. Or, go somewhere else and bitch.
Re: Mail and News with UUCP over TCP/IP
You might want to look ath the March issue of Linux Journal (the one with Perl on the cover). There is a fairly lengthy article about e-mail and news via uucp. Time is the best teacher, unfortunately it kills all of it's students Rob MacWilliams [EMAIL PROTECTED] N9NPU
Re: Documentation - I see squares
John Foster [EMAIL PROTECTED] writes: In a lot of man pages, and some of the documentation in /usr/doc there are there little squares or cryptic $%^ thingees. I guess that there's something I've missed somewhere... What have/haven't I done? On the assumption that you ran into some highlighting or underlining markup, then you might try running your documents through a smart pager that's able to do something reasonable with such things. Try this: export MANPAGER=/usr/bin/less [snip] I don't think that's the problem, less is my PAGER, and I know about zcat. Most of the text is quite readable. The little squares are often where I'd expect an apostrophe to be, and some of the funny codes are B7 for example. It looks like a bit of hex. You're reading an ISO-8859-1 (8-bit) document with `less' in it's 7-bit mode. You can do one of two things -- 1. $ export LC_CTYPE=iso_8859_1 $ less filename 2. $ less -r filename The first is the preferred solution, but requires you to have set up all the locale data correctly. The second just punts the 8-bit char to your display. In either case, your display has to support 8-bit characters, and show them meaningfully. `xterm' can handle it. I haven't checked the console (I'm sitting on a Solaris box right now) - Hari -- Raja R Harinath -- [EMAIL PROTECTED] When all else fails, read the instructions. -- Cahn's Axiom Our policy is, when in doubt, do the right thing. -- Roy L Ash
Re: 56k baud modem (x2)
GV == Gregory Vence [EMAIL PROTECTED] writes: SK --Susan G. Kleinmann wrote: SK Hi Greg -- You asked: GV Is the 56kb USR upgrade compatible with linux? I tired of 14.4. GV :) SK Almost certainly. I use a 56K ISDN 'pseudo-modem' all the SK time. Even though this box isn't internally the same as the SK real USR modem you're talking about, the software configuration SK under Linux would be exactly the same. GV I'm refering to using the 56k upgrade to their 33.6 modems. GV It's some kind of driver (not ISDN) for working on regular GV analog lines. It might be something that reloads EEPROM or GV such. GV I'm looking for success and real connect speeds. Sometimes GV people with 33.6k only get on at 28.8k or 24k. I assume you're talking about the flash upgrade for the Couriers. You should just need to run it once from a DOS box, and it will reprogram the EEPROM to (allegedly) work with X2. Sportsters require a chip replacement. If you're talking about neither one of these, then I don't know what you're referring to. As far as real connect speeds, I've seen estimates that 5% of the country has the right hardware on the other end of the telephone switch to support 56kbps technology. Also, USR hasn't actually shipped the equipment that's needed on the ISP side to support 56K. (You can't just plug 2 56K modems together and have it work). So, as far as real connect speeds, you're unlikely to get real data on 56K yet, and it's highly unlikely that any data you get will be applicable to you. -Larry -- Larry Daffner| Linux: Unleash the workstation in your PC! [EMAIL PROTECTED] / http://web2.airmail.net/vizzie/ Brook's Law: Adding manpower to a late software project makes it later.
SSL-Apache: Will there be a Debian package?
A few weeks ago, there was mention of an SSL-Apache package. Is this still being put together? When and where could I find that? Karl M. Hegbloom [EMAIL PROTECTED] http://www.inetarena.com/~karlheg Debian GNU 1.2 Linux 2.0.29t
AWE32 problems.
I just can't get the AWE32 sound card to work under debian. It works fine under dos,95, or NT. I've installed all the patches and tried running it with kernel 2.0.27, 2.0.29, and 2.1.26 with no success. I use the I/O ,IRQ and DMA values out of the manual which match the ones in 95. The card is plug and play. If anyone know of the setting that work or have any ideas please let me know. Thanks! IRQ: 5 DMA: 1 and 5
Re: 56k baud modem (x2)
Larry 'Daffy' Daffner wrote: As far as real connect speeds, I've seen estimates that 5% of the country has the right hardware on the other end of the telephone switch to support 56kbps technology. Also, USR hasn't actually shipped the equipment that's needed on the ISP side to support 56K. (You can't just plug 2 56K modems together and have it work). So, as far as real connect speeds, you're unlikely to get real data on 56K yet, and it's highly unlikely that any data you get will be applicable to you. Here's the basics. Several ISP's in Atlanta are in beta or using it. I've currently got a 14.4. I don't know if my location would even take full advantage of 33.6. However, I'm willing to try. I'm not about to spend the bucks to install ISDN in an appartment and then have to do it again when I move to a house. :) So far, Larry, you're the closest to an answer of experiance. Thanx -- Greg.
Re: Procmail recipe.
:0 E * ^TO.*debian-user $MAIL/Lists/debian/user/incoming :0 E * ^FROM.*debian-user $MAIL/Lists/debian/user/incoming You can OR them like so: * ^(TO|From.*)debian-user
Re: Documentation - I see squares
It might have to do with striping the 8th bit of a byte before it gets displayed on the terminal. For man, try the -7 option . That might not help you at all, but since the other responses from the list has not fix your problem yet, that is what I would investigate until a better suggestion arrives. Also, you may want to try different fonts, who knows. Or, try different options to /usr/bin/setterm, it might be. And if you find out, please, post the solution. Ioannis Tambouras [EMAIL PROTECTED], West Palm Beach, Florida Signed pgp-key on key server. On Mon, 3 Mar 1997, John Foster wrote: In a lot of man pages, and some of the documentation in /usr/doc there are there little squares or cryptic $%^ thingees. I guess that there's something I've missed somewhere... What have/haven't I done? John.
Re: Documentation - I see squares
I don't think that's the problem, less is my PAGER, and I know about zcat. Most of the text is quite readable. The little squares are often where I'd expect an apostrophe to be, and some of the funny codes are B7 for example. It looks like a bit of hex. Try adding export LESSCHARSET='latin1'to your profile. Paul Serice
Re: Documentation - I see squares
On Mon, 3 Mar 1997, John Foster wrote: I don't think that's the problem, less is my PAGER, and I know about zcat. Most of the text is quite readable. The little squares are often where I'd expect an apostrophe to be, and some of the funny codes are B7 for example. It looks like a bit of hex. I think this is related to your font tables. If it's in text mode then you might have changed fonts using one of the font tables in /usr/lib/kbd/consolefonts which lacks a few chars. I saw the same thing on a 486 I setup last week, but neigther my 486 or 6x86 do this. The only thing I can think of is that the 486 had it's font set using setfont while the other two had the font set from the bios with vga=extended in lilo. Jason
Windows NT and SAMBA
Does any know how I can get NT workstation to work with SAMBA the way WIN95 does. Any help will be appreciated -OZ -- NAME Oz Dror, Santa Monica, California EMAIL [EMAIL PROTECTED] Linux since 8/15/94 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: Documentation - I see squares
Raja R Harinath [EMAIL PROTECTED] writes: John Foster [EMAIL PROTECTED] writes: [snip] You're reading an ISO-8859-1 (8-bit) document with `less' in it's 7-bit mode. [snip] In either case, your display has to support 8-bit characters, and show them meaningfully. `xterm' can handle it. I haven't checked the console (I'm sitting on a Solaris box right now) In my experience it doesn't always do a wonderful job, since it doesn't have all the characters needed (which might be the original problem, actually). This can be fixed by doing something like: $ setfont -u lat1.uni lat1-16.psf -- Carey Evans * [EMAIL PROTECTED] Linux and Linux-like systems such as UNIX(R) and FreeBSD... - Yggdrasil Computing, [EMAIL PROTECTED]
Re: X tries to start XIE and PEX but wont
Randy R Dees [EMAIL PROTECTED] writes: I have just done a clean install from a 1.2.2 CDROM and am having troubles starting X. I got the base system installed, and then installed the X stuff. I selected xbase, xserver-vga16, fvwm2, and xserver-svga for the initaial install. I did allow xdm to set up. upon reboot, I get the nice xlogin widget, and if i enter a bad login it works properly, ie it says improper login. If I login correctly, I get a band of static along the top of the screen and then x restarts and I have the login widget again. [snip] The PEX and XIE errors probably have nothing to do with it - the X server looks for them in case you've got them installed and if you haven't, it complains but gets on with things. I also get the static along the top of the image, after I exit my window manager to return to the xdm login, but X is working properly. I tried loading the xext module to fix this but get the same messages. How do I kill this problem, and get X working correctly? More likely, your .xsession or the system Xsession isn't executable, so no programs get run, or it is executable but exits back to xdm straight after being run. Check your .xsession-errors, and see whether you can get an xterm with usernameenterpasswordf1. -- Carey Evans * [EMAIL PROTECTED] Linux and Linux-like systems such as UNIX(R) and FreeBSD... - Yggdrasil Computing, [EMAIL PROTECTED]
Re: Why is PPP so screwed up!?!?!
hi, This ppp issue is dragging for weeks! i like to suggest a book like Linux Secrets by Naba Barkati. From IDG Books. Please, this is *not* a sales pitch. I was having problems setting up ppp. And after reading the book, i setup my ppp within 2 hours. No problems whatsover. The ppp script(you have to tinker the script to your own likings.) was for the slakware. so i installed it on a slakware. After a while, I transferred it in my debian dist. and I was pleasantly surprised when it worked quite without any modifications. Just my 2 cents. Andre M. Varon Bacolod City Technical Head Philippines Lasaltech, Inc. 6100 E-mail : [EMAIL PROTECTED] Web Page: http://www.mozcom.com/ bacolod/andre.htm TeleFax : 433-3520
library problems
THe gdbm (and probably others) library isnt set up correctly with regards to sym links in /usr/lib ln -s libgdbm.so.1.7.3 libgdbm.so Is this an ok mailing list to post such problems or should I go through the debian bug tracking system? More library problems.. has anyone managed to get ftplib working? I'm getting undefined references to the function calls, even though I've linked in the library (-lftp). Silvio
Re: lprm says Permission denied (fwd)
John == John Goerzen [EMAIL PROTECTED] writes: John Goerzen writes: This is *not* an acceptable fix. Other packages, for isntance Samba, will **NOT** work with lprng. Why won't samba not work with it? Please file an appropriate bug against the samba package. John Because Samba depends on the output formats of the lp* John commands, in particular, lpq. It parses the output and John converts it to the format suitable for displaying to Windows John users. John Since LPRNG's lpq is different that LPR's lpq output, samba John cannot parse it correctly. -- John Goerzen | Running Debian John GNU/Linux (www.debian.org) Custom Programming | John [EMAIL PROTECTED] | A suggestion for people using Lprng and having problems is to check out the Lprng mailing list (10-20 messages a day - see the doc dir. for info). I joined a few weeks ago and they have covered this problem (Samba) and many others; and Patrick Powell (the author) is extremely helpful in fixing problems and adding new features - this is perhaps yet another good reason to switch to Lprng (how much new development is occurring with lpr ?), Adrian
Re: AWE32 problems.
Dark Lord of Sith wrote: I just can't get the AWE32 sound card to work under debian. It works fine under dos,95, or NT. I've installed all the patches and tried running it with kernel 2.0.27, 2.0.29, and 2.1.26 with no success. I use the I/O ,IRQ and DMA values out of the manual which match the ones in 95. The card is plug and play. If anyone know of the setting that work or have any ideas please let me know. Thanks! IRQ: 5 DMA: 1 and 5 It is possibly becuase your sound card is PnP and you need the PnP patch or download the isapnptools from sunsite.unc.edu lawrence
XFree86 3.2 performance problem ?
Hi! Has anyone else noticed that, since the upgrade to 3.2, X seems to be slower ? I have a P120 with 48 Mb and a Stealth64 Video 2000 (S3) with 2Mb DRAM. I use 1024x768 with 16 bpp. After the upgrade I noticed that my WM (AfterStep) took about 2-3 seconds more to load and the window drawing is also a bit slower. I didn't think about it though, but yesterday I started xbmbrowser in a directory where I keep a lot of pixmaps (800+). It took forever to load so I killed it after about 10 minutes. Top showed that the XServer consumed 85-95 % of the CPU load. After that, I reinstalled my old S3 server (3.1.2 from Debian 1.1) and the problems mentioned above disappeared. Has anoyone had a similar experience ? Thanks in advance Robert -- Robert Sickeldalemail: [EMAIL PROTECTED] Frontec Network Services AB (All statements above are my own, not my employers.) --
Fixed == Documentation - I see squares
To refresh, there were strange little squares and odd bits of hex scattered through the manpages. This reply fixed it: I don't think that's the problem, less is my PAGER, and I know about zcat. Most of the text is quite readable. The little squares are often where I'd expect an apostrophe to be, and some of the funny codes are B7 for example. It looks like a bit of hex. Try adding export LESSCHARSET='latin1'to your profile. Paul Serice Thanx to all who replied! John Foster
Shadow-Support
Hi, some time ago I've installed the shadow-packages. But now where have the gone? Is there now shadow-Support now? What about security? Stefan Walder *---* Dipl. Ing. Stefan Walder (techn. Ang. in der EDV-Systemtechnik) Universitaetsstrasse 150 E-Mail: [EMAIL PROTECTED] Werkstofftechnik IA 2/47 Tel.: (0)49(0)234-700-5952 D-44780 Bochum Fax:(0)49(0)234-7094-104 *---*
X tries to start XIE and PEX but wont (fwd)
Add the following lines to the xinitrc file to the Modules section. Load pex5.so ^^^ Load xie.so ^^ but I dont know the exact name of that libraries. FInd them by dpkg --listfiles xext -- Forwarded message -- Date: Sun, 2 Mar 1997 13:57:40 -0500 (EST) From: Randy R Dees [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: X tries to start XIE and PEX but wont I have just done a clean install from a 1.2.2 CDROM and am having troubles starting X. I got the base system installed, and then installed the X stuff. I selected xbase, xserver-vga16, fvwm2, and xserver-svga for the initaial install. I did allow xdm to set up. upon reboot, I get the nice xlogin widget, and if i enter a bad login it works properly, ie it says improper login. If I login correctly, I get a band of static along the top of the screen and then x restarts and I have the login widget again. A look at the errors on the console identifies that PEX ecxtension not loaded and XIE extension not loaded. I kill xdm with /etc/init.d/xdm stop and try just starting it with startx, same thing. If I just run X, however, I get a blank grey screen with a cursor and no window manager. I tried loading the xext module to fix this but get the same messages. How do I kill this problem, and get X working correctly? Thanks Randy
unsubscribe
unsubscribe
Upgrade from unstable aka This is the end ...
Hi, I have a problem (and possible bug raport). Last night I've (tried) upgraded my 1.1 upgraded from stable from unstable. It went like usual (several iterations of install and some manual dpgk installs), and suddenly, after upgrade of the dpkg itself it broke. It keeps seying Symbol sysinfo not resolved and refuses to do anything else. I'm suspecting some dynamical library mismatch since sysinfo is the name of the system call and there is no such command. Another problem is with bash 2.0. It does not handle LOCALE properly. If I set LANG to pl_PL it just kills itself. Does anybody have any advices ? (specially to the dpkg problem) Pawel. -- Pawel T. JochymInstitute of Nuclear Physics e-mail: [EMAIL PROTECTED]Cracow, Poland tel. 37-02-22 ext. 269
Re: Documentation - I see squares
| export MANPAGER=/usr/bin/less | | (Of course, this only works if you have the 'less' package installed.) | | If it works for you, then you might want to put this line into your | .bashrc or whatever startup script you use. | | If the problem is that the documents you're looking at are gzip'd then | you'll want to read them with zless, by executing, e.g., | zless /usr/doc/man/README.gz | |I don't think that's the problem, less is my PAGER, and I know about zcat. |Most of the text is quite readable. The little squares are often where I'd |expect an apostrophe to be, and some of the funny codes are B7 for |example. It looks like a bit of hex. You probably have not set your 'LESSCHARSET' environment variable; try either: export LESSCHARSET=latin1 or: setenv LESSCHARSET latin1 -- Ronald van Loon ([EMAIL PROTECTED]) I am waiting as fast as I can! I want patience, and I want it *NOW*! - Bethany J. Parkhurst
How to get your lan on the internet
Debians: Following is a description of the steps I took to implement ip masquerading via a firewall. This allows computers on a lan to access the internet via a dynamically allocated PPP link. In a nutshell, it facilitates the functionality inherent within a class B internet domain without having a class B domain. B-E-A-W-R-E if you do this, there is the potential that some external entity, human or otherwise could infest your computer, network or nodes causing accidental or malicious damage. Check your deamons. Special thanks to Terry Dawson for his HOWTO ( Debian Doc file NET-2-HOWT0) entitled Linux NET-2/3-HOWTO v3.5 Dated January 16, 1996. Even though this doc is a little out dated, it got me on the right track. 1. Make certain IP firewall and masquerading are configure into you Linux kernel (go to /usr/src/linux and read. I included everything that has to to with networking into the kernel and not as a module) 2. Make sure your ip link to your ISP is running properly. 3. Set the default route of all nodes on your lan to your Linux box using the ip address of your network interface. ( you don't know the ip address of your ISP interface because its dynamic). 4. If your Linux box has its DNS running you can use it or else use your ISPs DNS. 5. Type in /etc/init.d/ppp stop 6. edit /etc/init.d/network and append the following line. ipfwadm -F -a accept -m -P all -S XXX.XXX.XXX.0/24 -D 0.0.0.0/ Where XXX.XXX.XXX is your network ip address or the first three octets of your lan interface 7. Type in /etc/init.d/ppp start 8. Ping only seems to work from the Linux host even though all protocols are enabled (ICMP, TCP, UDP), so from a host on your lan, telnet, or set your browser to your favorite location. 9. To view your active firewall list rules enter ipfwadm -Fl 10. To view your active masquerading list enter ipfwadm -Ml (*NOTE*: by default masquerades have a time out value and will only show up in a listing if any are present. You have to move some traffic through your Linux box. Cool eh! Peter IannarelliLive hard, die young, that way you make a gook looking corpse .
UNSUBSCRIBE
UNSUBSCRIBE
Re: A NFS problem
On Thu, 27 Feb 1997, Martin Stromberg wrote: Perhaps the server only can export the directories in the export file; try mounting with mount -t nfs 141.48.54.2:/usr/local/linux /mnt. I really don't know a lot about nfs mounting, but trying won't hurt. I forgot to mention that I also tried this. I also tried to mount another Linux box which worked everey time before but failed in the circumstances I described. If you have another linux box running you could make a statically (or try with the dynamically) linked ping and copy it to a floppy and then mount that floppy on /dev/fd0 on the box you are trying to get connected. I will try that. But I do wonder if you have nfs compiled into the kernel or as module or not at all? Yes, Susan G. Kleinmann compiled it into the kernel. The error message is completely different if you havn't NFS or NFS has to be loaded as module but can't be found. Hopefully helpful, Hope that ping gives further hints (I will report tomorrow). Hopefully there are other ideas. Andreas.
Re: shared library tutorial?
On Feb 28, Dale Martin wrote Can anyone point me to an online reference on how to compile and use shared libraries? Check out ELF: from the Programmer's Perspective by H.J. Lu: http://www.debian.org/Documentation/elf/elf.html ftp://tsx-11.mit.edu/pub/linux/packages/GCC/elf.ps.gz HTH, Ray -- Cyberspace, a final frontier. These are the voyages of my messages, on a lightspeed mission to explore strange new systems and to boldly go where no data has gone before.
Re: 56k baud modem (x2)
I don't know why not. There is nothing different about the modem - computer interface, AFAIK. On Mar 2, Gregory Vence wrote: Is the 56kb USRupgrade compatible with linux? I tired of 14.4. :) Thanx -- Greg. -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] |
Re: lprm says Permission denied (fwd)
I had tried the first item you suggested before reverting back to normal lpr, I do recall. I also seem to remember that in some of Samba's documentation, the lprng option was mentioned, while in other areas where the options for printing were listed, lprng was not mentioned. I do not recall if I tried the second thing, but lpq, lprm, and lpr all worked fine from the local box, and lpr worked from Win95. If somebody could print, I would think that they would also have permission to view the queue. On Mar 3, Craig Sanders wrote: On Sun, 2 Mar 1997, John Goerzen wrote: i've got it running on my system, using lprng magicfilter with . samba no problems. it works. Not in my experience. I also tried lprng, magicfilter, and samba. I found the same nonprintable option and turned it off. The Win95 box appeared to print correctly, BUT it could NOT view the print queue, delete sent jobs, etc. With lpr instead of lprng, the Win95 box could do all of that like it is supposed to be able to. a couple of things that might help: 1. check your /etc/smb.conf. Does it have a line like: printing = lprng in the [global] section see man pages for samba and smb.conf - samba has specific support for lprng. 2. check your /etc/lpd.perms - you may not have set up the permissions correctly to allow the win95 box to see the queue and/or delete jobs. craig -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] |
Re: Procmail recipe.
The FFrom and rom words are indications of file locking problems. If you go to http://www.rosat.mpe-garching.mpg.de/mailing-lists/procmail/ and do a search with a word ffrom you'll find that many others have had these problemes too. Here's a small excerpt: FFrom is generally an indication of a locking problem: procmail is running into another process writing to the mailspool (possibly another copy of procmail). I use procmail at our school so I don't know if the procmail(s) and mail user agent (Elm, pine ...) are conflicting each other in Debian. Chapter 4.3 in the Debian policy manual tells about mail processing on Debian systems, see http://www.debian.org/Documentation/policy.html/ch4.html#s-mail. It might be helpful to check how the locking is done in procmail and your mail reader. The commands 'procmail -v' and 'elm -version' tell what the locking scheme is. Don't know the command in pine. Craig Small wrote: I found that the 'From ' that appears at the start of the message was losing or gaining some 'F's (ie FFFrom or rom ). Needless to say, I've turned procmail off. But is it a bug or have I done something wrong. If it is a bug, I'll put a bug in for it. The procmailrc file looks like [most of the correctly looking procmailrc cut] :0: ^ Maybe the lock file needs to specifed correct name? Just guessing... * ^X-Mailing-List: .*debian-user.* $MAILDIR/deb // Heikki -- Heikki Vatiainen * [EMAIL PROTECTED] Tampere University of Technology * Tampere, Finland
Re: Why is PPP so screwed up!?!?!
[Now over the next day, I'll get about 10 bounces. Can someone fix the flippin' list? How about an Errors-to: header? ] On Sun, 2 Mar 1997, Shawn Asmussen wrote: Cool off, man. What they seem to be talking about IS a Debian issue. Although ppp support IS compiled into the kernel, the pppd is separate, and the method by which you establish a connection, be it through pon, or a custom script like I use, because as far as I know pon will not redial Hmm.. Better not tell that to my system. pppd keeps redialing until it gets connected.. Jason Costomiris | Finger for PGP 2.6.2 Public Key [EMAIL PROTECTED] | There is a fine line between idiocy My employers like me, but not| and genius. We aim to erase that line enough to let me speak for them. | --Unknown http://www.jasons.org/~jcostom
Re: Why is PPP so screwed up!?!?!
Furthermore, saying its NOT is the documentation is just totatlly wrong! If you chose NOT to install the HOWTO'S or INFO, And how would I go about doing that? I've got 5 install disks and a machine with a modem that can only get to the net via PPP. I'd install the HOWTO's with dselect but, you see, I can't get PPP going. See there? It's kind of a chicken-n-egg problem. the PPP HOWTO? Yes, I've read the Serial HOWTO. I've read the PPP HOWTO. I've even read the PPP RFC. I know what IPCP does and I know what LCP does. But I shouldn't have to. I didn't have to read the LILO HOWTO to get my machine to boot Linux. I didn't have to read anything about the timezone system to get the timezone set right. I didn't have to read about mount(1), or mke2fs(1), or mknod(1), or anything else like that. Oddly, the Debian install program handled it all for me, as it should. But it's lack of any setup for PPP... it's lack of even *mentioning* that PPP is on the system already... seems to indicate that there was almost a conscious decision to throw the user to the lions on this part. Linux, any of the distributions, comes with enough doc to keep you busy, and make you real smart, if you just take the time to look at it! Its all there man, all of it. I'm not saying that it isn't. What I'm asking is: What percentage of the 10-30MB of documentation does a new Debian user have to read before they are sufficiently informed to take 5 [EMAIL PROTECTED]@ disks home and install it on a machine that only has PPP as a way of accessing the net? 50%? 10%? If you go to the debian home page, you'll find the link for the instaltion guide. The guide doesn't say Go and read these 200 choice HOWTO's. It bascally says: Here's how to get the disk images. Here's how to make the diskettes. Here's how to install it. Be well and prosper.. I'd begin to entertain the idea that I was out in left field if the install guide even simply MENTIONED something like Oh, if you want to use PPP, go read this other document first - Joe
Re: teTeX kind of broken
Christoph Martin [EMAIL PROTECTED] writes: Marcelo Magallon writes: On 28 Feb 1997, Christoph Martin wrote: The obvious solution is to remove all TeX files conflicting with teTeX before installing teTeX, but this is not user friendly, nice, cool, etc. You have no other chance. dpkg can't handle all (more than one) the replaces. Then, to the maintainer, PLEASE, include instructions about this unless we want to see the question How do I upgrade TeX? n+1 times on debian-user... I'm guessing something in the lines of In dselect [R]emove packages *first*, *then* [I]nstall them would work, but a bit more Where do you want to put these instructions? I have posted instructions to debian-user and debian-devel. If you put it in the preinst script it is to late. descriptive/less cryptic. Also, isn't there a workaround for the latex bug? I wouldn't like to see that question either, considering THERE IS a known solution. The only solution I know is to do it in the right order, but how do you enforce this? Some ideas on workarounds for the dpkg bug: What about a dummy package tetex-convertion? tetex-convertion replaces every old tex package. tetex-convertion conflicts with every old tex package. tetex-convertion is (pre)required by new tetexpackages Perhaps, one dummy package for each old tex package could solve the problem if the above approach fails. PS: I can't try myself these approchs. -- Alair Pereira do Lago [EMAIL PROTECTED] http://www.ime.usp.br/~alair Computer Science Department -- Universidade de S~ao Paulo -- Brazil
Re: 56k baud modem (x2)
John Goerzen wrote: I don't know why not. There is nothing different about the modem - computer interface, AFAIK. On Mar 2, Gregory Vence wrote: Is the 56kb USRupgrade compatible with linux? I tired of 14.4. :) I was just checking to make sure that the upgrade wasn't some Windoze driver that made the modem work only for W95...
Re: X tries to start XIE and PEX but wont
Randy R Dees wrote: I have just done a clean install from a 1.2.2 CDROM and am having troubles starting X. I got the base system installed, and then installed the X stuff. I selected xbase, xserver-vga16, fvwm2, and xserver-svga for the initaial install. I did allow xdm to set up. [...] A look at the errors on the console identifies that PEX ecxtension not loaded and XIE extension not loaded. I kill xdm with /etc/init.d/xdm stop The PEX and XIE extensions aren't responsible for this trouble. You don't need them to run X. Most likely the file /etc/ld.so.conf misses the line '/usr/X11R6/lib'. Add it and run ldconfig. Naturally you must be root to do that. Ulf
Re: 56k baud modem (x2)
On Sun, 2 Mar 1997, Daniel Stringfield wrote: Also, I remember bringing up the fact that its illegal (in the US) to run at speeds over 46k (or similar) over the analog lines... so legally, you can't go that fast. I'm assuming that this is going to be overturned shortly, since several companies are coming up with 56k technology. Actually, the FCC regs say nothing about *how fast* traffic can go. They only say how much voltage you can send up the line. Anyhow, USR's inferior implementation of 56k was sending so much voltage up the line, they had to cut it to 53k. Lucent/Rockwell hasn't shown this problem. In fact, whereas USR shows 53k downlink/33.6k uplink, Lucent is doing 61k downlink/47k uplink, and is within the voltage spec. Jason Costomiris | Finger for PGP 2.6.2 Public Key [EMAIL PROTECTED] | There is a fine line between idiocy My employers like me, but not| and genius. We aim to erase that line enough to let me speak for them. | --Unknown http://www.jasons.org/~jcostom
Re: Problems with mouse.
Marc Abrams wrote: Things are changing at NetForward! http://www.netforward.com/changes.shtml ~~~ Brown, Paul, BROWNPA2 wrote: I have just installed the latest version of Debian GNU/Linux (v 1.2 I think) and when it came to the device installation section I asked it to install the MS Bus Mouse driver. When the system boots up it says that it has found the bus mouse, however when I tried to install XFree86 it could not find any mouse attached no matter what device I told it to use. To try and see if I could access the mouse from outside X I obtained the gpm module and installed it, but to no avail, it to did not show any signs of being able to access the mouse, no errors, but no mouse either. This is my exact setup : Debian GNU/Linux 1.2 Old Microsoft Inport Bus Mouse Adapter Card and Mouse msbusmouse module installed saying that device is /dev/msmouse gpm installed with device set to /dev/msmouse and type set to any of bm/ms or bare When gpm goes into it's test phase it says that it connects to /dev/msmouse fine, but none of the types give me any joy. Can anybody help ? I have read some older messages from this mailing list that said something about needing to get a new kernel version, is this still required for the latest version of Debian GNU/Linux. If so what do I have to get and where do I get it from ? Many thanks in advance to anybody who is able to help. Regards, Paul Brown Add the -R option to your gpm configuration, and that should work. It did for me. marc. Hi, I found the same problem using an PS/2 mouse, we fixed installing a new kernel. Download kernel source, and then configure to your conditions. I think that is better that download a kernel image. saul
Re: Shadow-Support
On Mon, 3 Mar 1997, Stefan Walder wrote: some time ago I've installed the shadow-packages. But now where have the gone? Is there now shadow-Support now? What about security? I'm also concerned about this, but not terribly because I run Debian on personal machines, not ones intended to be used as servers. Doesn't PAM fix this? (I assume the plan is to move to PAM...) Douglas L Stewart [EMAIL PROTECTED] http://pobox.com/~douglas
Re: Shadow-Support Debian roadmap
Hi Stefan, I do still see them in 'project/experimental' (This is at Uni Mainz.): -rw-r--r-- 1 110 425 44862 Dec 6 11:54 shadow-login_960810-1_i386.deb -rw-r--r-- 1 110 425 43594 Dec 6 11:52 shadow-login_960810-1_m68k.deb -rw-r--r-- 1 110 425255326 Dec 6 11:54 shadow-passwd_960810-1_i386.deb -rw-r--r-- 1 110 425245940 Dec 6 11:52 shadow-passwd_960810-1_m68k.deb -rw-r--r-- 1 110 425 19846 Dec 6 11:53 shadow-su_960810-1_i386.deb -rw-r--r-- 1 110 425 19296 Dec 6 11:52 shadow-su_960810-1_m68k.deb -rw-r--r-- 1 110 425 14977 Dec 6 11:53 shadow_960810-1.diff.gz -rw-r--r-- 1 110 425343134 Dec 6 11:53 shadow_960810-1.tar.gz Besides, I think I read something about shadow becoming standard in 1.3. This raises the question whether there is something like a roadmap for the further development of Debian publically available... Just curious ;-) Regards, Andree -- | Institute of Geophysics phone: +49 40 4123 4389 ANDREE LEIDENFROST | University of Hamburg fax: +49 40 4123 5441 Geophysicist | Bundesstrasse 55 e-mail: [EMAIL PROTECTED] | D-20146 Hamburgwww: www.app-geoph.dkrz.de
Re: lprm says Permission denied (fwd)
On Sun, 2 Mar 1997, Craig Sanders wrote: actually, it's completely untrue. samba works very well with lprng. lprng has removed the possibility to automatically remove Files after printing. This is however necessary to remove spooled jobs. How do you work around this problem? Nils -- \ /| Nils Rennebarth --* WINDOWS 42 *-- | Schillerstr. 61 / \| 37083 Göttingen | ++49-551-71626 Micro$oft's final answer | http://www.nus.de/~nils
Re: Documentation - I see squares
A few manpages are formatted in a style that less doesn't completely clean up. Most seems to handle these a little better. Most detects and unzips gzip'd documents automatically. Bob At 05:50 PM 3/2/97 -0500, Susan G. Kleinmann [EMAIL PROTECTED] wrote: In a lot of man pages, and some of the documentation in /usr/doc there are there little squares or cryptic $%^ thingees. I guess that there's something I've missed somewhere... What have/haven't I done? On the assumption that you ran into some highlighting or underlining markup, then you might try running your documents through a smart pager that's able to do something reasonable with such things. Try this: export MANPAGER=/usr/bin/less (Of course, this only works if you have the 'less' package installed.) If it works for you, then you might want to put this line into your .bashrc or whatever startup script you use. If the problem is that the documents you're looking at are gzip'd then you'll want to read them with zless, by executing, e.g., zless /usr/doc/man/README.gz Hope that helps. Susan Kleinmann
Re: lprm says Permission denied (fwd)
William Chow [EMAIL PROTECTED] writes: On Sat, 1 Mar 1997, John Goerzen wrote: This is *not* an acceptable fix. Other packages, for isntance Samba, will **NOT** work with lprng. Doesn't getting rid of name canonizing in lpr work? Just get the source of an older version of lpr or unpatch the current sources or get an older lpr binary and it should work. Does this break lpr over network? I prefer to have canonizing in lpr work correctly instead of removing canonizing. Perhaps someone just needs to get the lpr source code and do debugging on it... True ... Sven -- Sven Rudolph [EMAIL PROTECTED] ; WWW : http://www.sax.de/~sr1/
Re: lprm says Permission denied (fwd)
Scott Stanley [EMAIL PROTECTED] writes: Can anyone tell me what the differences are between lpr and lprng. In what ways has lprng been ``enhanced and extended'', to quote the package description. Read /usr/doc/lprng/Intro.txt.gz and others. Sven -- Sven Rudolph [EMAIL PROTECTED] ; WWW : http://www.sax.de/~sr1/
Re: lprm says Permission denied (fwd)
Craig Sanders [EMAIL PROTECTED] writes: On Sun, 2 Mar 1997, Hamish Moffatt wrote: On Mar 03, 1997 at 08:58:41PM +1100, Craig Sanders wrote: well, actually i had a few initial hassles getting the win95 box to print with the PCL driver. Postscript worked fine (through ghostscript to my HP4L), but PCL failed. Eventually somebody on debian-user suggested that I put check_for_nonprintable no in /etc/lpd.conf - as Strange, because I don't have that in smb.conf, and I print PCL to my new HP5L from Win95 boxes just fine. The 'check_for_nonprintable' is in lpd.conf, NOT smb.conf. I vaguely recall that this was such a FAQ that it was made the default setting (dont take my word for it though) Currrently it is only default in the version that is in experimental (because it has some other bugs). It will be default in the next Debian release. Sven -- Sven Rudolph [EMAIL PROTECTED] ; WWW : http://www.sax.de/~sr1/
help - need to read a floppy from SCO
Hello all... I have a disk with some information on it that came from an SCO box (some version that was current about 3 years ago - 3.0 ODT ?). I recall that the disk was formated with the format command native to SCO. If im not mistaken the disk was mounted over /floppy and a tar file was copied straight to the mount point. As best as I can remember... Ive tried to mount this disk with a mount /dev/fd0 /floppy -t sysv, with no luck. Can anybody out there offer any suggestions. ... a very large thanks in advance ... regards dave
Re: lprm says Permission denied (fwd)
Adrian Phillips [EMAIL PROTECTED] writes: A suggestion for people using Lprng and having problems is to check out the Lprng mailing list (10-20 messages a day - see the doc dir. for info). I joined a few weeks ago and they have covered this problem (Samba) and many others; and Patrick Powell (the author) is extremely helpful in fixing problems and adding new features - this is perhaps yet another good reason to switch to Lprng (how much new development is occurring with lpr ?), That's the reason why a) using LPRng and b) maintaining a Debian package for LPRng is much easier for me compared to lpr. BTW: There are maintained versions of lpr, but there are that many (the *BSDs, and probably some Linux versions). Unfortunately the *BSD versions don't compile on Linux, and I don't know which Linux-ported lpr versions are well-maintained. Sven -- Sven Rudolph [EMAIL PROTECTED] ; WWW : http://www.sax.de/~sr1/
netscape: Floating Point Exception,
Hello I Loaded something like netscape-v30-export.x86-unknown-linux-elf.tar.gz I got the exec-ready-to-use file I ran it .. and it said: Floating point exception (core dumped). Haa. It was too simple to work so easily ! What is wrong ? Is there a better release without any problem for linux Debian ? Regards, --:-) Jean-Paul Lacharme. GREQAM UMR 6579 au CNRS Centre de la Vieille Charite. 2, rue de la Charite. 13002 Marseille. FRANCE Tel.: 0491140731/Fax:0491900227
Re: Why is PPP so screwed up!?!?!
Joe Emenaker writes: I'd begin to entertain the idea that I was out in left field if the install guide even simply MENTIONED something like Oh, if you want to use PPP, go read this other document first Well, you weren't. Is anyone about to start a project to solve this problem? I'm willing to help. -- John HaslerThis posting is in the public domain. [EMAIL PROTECTED]Do with it what you will. Dancing Horse Hill Make money from it if you can; I don't mind. Elmwood, Wisconsin Do not send email advertisements to this address.
UNSUBSCRIBE
UNSUBSCRIBE
UNSUBSCRIBE
UNSUBSCRIBE
unsubscribe
unsubscribe
UNSUBSCRIBE
UNSUBSCRIBE
Re: lprm says Permission denied (fwd)
On Mon, 3 Mar 1997, John Goerzen wrote: I had tried the first item you suggested before reverting back to normal lpr, I do recall. I also seem to remember that in some of Samba's documentation, the lprng option was mentioned, while in other areas where the options for printing were listed, lprng was not mentioned. I do not recall if I tried the second thing, but lpq, lprm, and lpr all worked fine from the local box, and lpr worked from Win95. If somebody could print, I would think that they would also have permission to view the queue. I have switched back to regular lpr myself. I tried lprng briefly, but the errors I was getting didn't make any sense to me at all, so I just switched back to regular lpr. I still haven't fixed my lpr problem, but I think I am getting closer. Basically, what is happening is that when I print a file, the printer starts up but all that comes out is a blank page. I know there is still a line feed problem (as there is initially with many printers), but the file I am printing has text on the first line that should show fine. I have worked through the printing HowTo, but I haven't managed to figure this one out. When I print a file, it is getting sent to the spool directory just fine, but somewhere between there and the printer, all the data is being lost.. Scott On Mar 3, Craig Sanders wrote: On Sun, 2 Mar 1997, John Goerzen wrote: i've got it running on my system, using lprng magicfilter with . samba no problems. it works. Not in my experience. I also tried lprng, magicfilter, and samba. I found the same nonprintable option and turned it off. The Win95 box appeared to print correctly, BUT it could NOT view the print queue, delete sent jobs, etc. With lpr instead of lprng, the Win95 box could do all of that like it is supposed to be able to. a couple of things that might help: 1. check your /etc/smb.conf. Does it have a line like: printing = lprng in the [global] section see man pages for samba and smb.conf - samba has specific support for lprng. 2. check your /etc/lpd.perms - you may not have set up the permissions correctly to allow the win95 box to see the queue and/or delete jobs. craig -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] |
ethernet routing problem?
I've been setting up Debian 1.2.4 (25 Jan.: Cheapbytes distribution) on two new Pentium 150 systems and I can't get network routing over ethernet to work. Installation of netbase and netstd seemed to go well using dselect, except for an unsurprising temporary problem in finding the right i/o port for the ethernet card. I'm using the D-link DE220P, which the ne driver easily finds. Ifconfig gives this report, which I believe shows correct configuration of the driver to the card: eth0 Link encap:10Mbps Ethernet HWaddr 00:80:C8:2D:7D:8F inet addr:192.54.242.228 Bcast:192.54.242.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 TX packets:4117 errors:0 dropped:0 overruns:0 Interrupt:11 Base address:0x220 Pinging the localhost works fine, but pinging anything else on the network (even the immediately adjacent device connected via coax) produces no result. I'm sure it's not a wiring problem because the rest of the machines on the network are not affected and I get the same negative results using ping on both new machines, which are wired into the network in different locations in the office. Trying ftp produces the error: no route to host. So I assume this is some sort of routing problem. The problem is identical on both machines with the new distribution. I've compared everything I can think of to another machine we have running Debian 1.1 (dating from last June). All the files in init.d appear to be the same (/etc/init.d/net*). The machine with 1.1 works fine. Does routed or gated need to be running? I can't find gated on any of the machines; routed is commented out in the network init files. I tried uncommenting it and rebooting to no effect. More reports and file contents: netstat -rn: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.54.242.00.0.0.0 255.255.255.0 U 1500 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 3584 0 0 lo 0.0.0.0 192.54.242.21 0.0.0.0 UG 1500 0 0 eth0 /etc/hosts: 127.0.0.1 localhost 192.54.242.17 mach1.wlu.camach1 192.54.242.18 mach2.wlu.camach2 192.54.242.200 astro.wlu.caastro 192.54.242.201 nestor.wlu.ca nestor . 192.54.242.228 pressprt.wlu.ca pressprt# this machine /etc/resolv.conf: domain wlu.ca search wlu.ca nameserver 192.54.242.17 192.54.242.18 /etc/networks: localnet192.54.242.0 /etc/host.conf: order hosts,bind multi on Processes: (among others) PID TT STAT TIME COMMAND 1 ? S 2:33 init [2] 2 ? SW 0:00 kflushd 3 ? SW0:00 kswapd 9 ? S 0:00 update 114 ? SW 0:00 nfsiod 115 ? SW 0:00 nfsiod 116 ? SW 0:00 nfsiod 117 ? SW 0:00 nfsiod 426 ? S 0:00 /sbin/syslogd 428 ? S 0:00 /sbin/klogd 435 ? S 0:00 /sbin/kerneld 485 ? S 0:00 /usr/sbin/apache -d /home/httpd/html 493 ? S 0:00 /usr/sbin/lpd 501 ? S 0:00 /usr/sbin/xntpd 519 ? S 0:00 /usr/sbin/xntpd 647 ? S 0:00 /usr/sbin/cron 654 ? S 0:00 /usr/bin/X11/xdm 656 1 S 0:00 -bash 657 2 S 0:00 /sbin/getty 38400 tty2 658 3 S 0:00 /sbin/getty 38400 tty3 659 4 S 0:00 /sbin/getty 38400 tty4 660 5 S 0:00 /sbin/getty 38400 tty5 661 6 S 0:00 /sbin/getty 38400 tty6 6062 ? S 0:00 /usr/sbin/inetd 6647 ? S 0:00 /usr/sbin/named 6060 ? S 0:00 /usr/sbin/rpc.portmap Any help is much appreciated. Thanks. --Steve Izma, Wilfrid Laurier University Press Waterloo, Ont., Canada N2L 3C5 (519) 884-0710 ext. 6125 FAX: (519) 725-1399 [EMAIL PROTECTED] or [EMAIL PROTECTED]
Re: Why is PPP so screwed up!?!?!
We have someone who wrote a PPP set-up program that isn't ready for prime time. When it is ready, it will be part of the system. Bruce -- Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502 Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3
Re: I can't build kernel; cpp 2.7.2.1-5, gcc 2.7.2.1-5, libc 5.4.20-1, kernel-source-2.0.27-2
Manoj Srivastava [EMAIL PROTECTED] writes: Pardon what maybe a silly question, but do you have libc5-dev and ncurses-dev installed? manoj Sure. $ dpkg -s ncurses3.0-dev Package: ncurses3.0-dev Status: install ok installed [skip] $ dpkg -s libc5-dev Package: libc5-dev Status: install ok installed [skip] The trouble was in /usr/include/ctype.h, when I said #include linux/ctype.h, gcc compiles O.k., but ld still does complain about _ctype. Here is /usr/include/ctype.h $ cat /usr/include/ctype.h #include_next ctype.h #undef isalnum #define isalnum(c) (isalpha(c) || isdigit(c)) $ Well, I'm going to install libc5-5.23 tonight, I hope, this stupid trouble will gone. -- Alexey V. Naidyonov | mailto:[EMAIL PROTECTED] Tula State University | http://www.ocnit.tsu.tula.ru/~growler/
Re: Why is PPP so screwed up!?!?!
Jason Costomiris wrote after: On Sun, 2 Mar 1997, Shawn Asmussen wrote: Cool off, man. What they seem to be talking about IS a Debian issue. Although ppp support IS compiled into the kernel, the pppd is separate, and the method by which you establish a connection, be it through pon, or a custom script like I use, because as far as I know pon will not redial Hmm.. Better not tell that to my system. pppd keeps redialing until it gets connected.. yup, same here. which is nice 'cause i can reboot the remote machine and walk away confident that the connection will be re-established. what a relief. also, i have found modular ppp support to work just fine as opposed to compiling it in. m* -- The Shining One --
Installing my SB16
Hello, I want to install my Soundblaster 16 (Value Edition) unter Debian. How? Thanx. bjoern
unsubscribe
[no subject]
unsubscribe
Re: AWE32 problems.
On Mon, 3 Mar 1997, Lawrence Chim wrote: Date: Mon, 03 Mar 1997 20:29:34 +1000 From: Lawrence Chim [EMAIL PROTECTED] To: debian-user@lists.debian.org, Dark Lord of Sith [EMAIL PROTECTED] Subject: Re: AWE32 problems. Dark Lord of Sith wrote: I just can't get the AWE32 sound card to work under debian. It works fine under dos,95, or NT. I've installed all the patches and tried running it with kernel 2.0.27, 2.0.29, and 2.1.26 with no success. I use the I/O ,IRQ and DMA values out of the manual which match the ones in 95. The card is plug and play. If anyone know of the setting that work or have any ideas please let me know. Thanks! IRQ: 5 DMA: 1 and 5 It is possibly becuase your sound card is PnP and you need the PnP patch or download the isapnptools from sunsite.unc.edu lawrence isapnptools is available as a .deb package. Haven't tried it yet, but it is installed. Does anyone know if it is possible for a pnp sound card to configure without that package, on previous versions of debian? I'm havin a heck of a time getting sound support compiled into my kernel, and now I think it is because its a pnp card. Funny thing is with deb 1.1 I was able to config my kernel for sound no problem. ahh I'm just havin' a bad week, first pon, now my sound...virtual scream I feel better now... As someone mentioned before config problems are _not_ fun. Rich M [EMAIL PROTECTED]
(Fwd) ZIP-drive (parellel) under Debian (fwd)
Tom asked me to pass this message along to the list, so here it is. -- Forwarded message -- Date: Tue, 4 Mar 1997 06:38:37 + 12 From: Tom Butz [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: (Fwd) ZIP-drive (parellel) under Debian --- Forwarded Message Follows --- From: Self midland To:Dale Scheetz [EMAIL PROTECTED] Subject: ZIP-drive (parellel) under Debian Reply-to: [EMAIL PROTECTED] Date: Tue, 11 Feb 1997 20:43:45 Hi Dale, would you please pass on the following. Thanks, Tom. *** The parallel ZIP-drive works without a hitch: Debian recognises it as /dev/sda4, in fact it is a hard-disk. MS-DOS thinks it's a big floppy though, according to MSD.EXE after I ran GUEST.EXE (off the support floppy that came with the drive). Debian doesn't require any support from MS-DOS, it just runs like any other hard-disk (use 'fdisk' to set up the partition-table, and then 'mkfs' to create a file-system). A warning, however: do not set your parallel port to 'Enhanced Parallel Port' - leave it set to 'Standard Parallel Port', otherwise you will have time-out problems formatting it under Debian (my experience). (Might be coincidental). Speedwise Debian would beat MS-DOS hands down anyway, and shouldn't really need that last bit of tweaking. If you format it under MS-DOS you can still mount it under Debian: it doesn't complain about the lack of a partition-table. Read and write work like a dream. Thanks for such an excellent system. Application note: under Linux you can use one task to back up your MS-DOS things on a ZIP-drive, while doing some typing/translating in another task. Try the same running MS-DOS... ***
Re: Why is PPP so screwed up!?!?!
1. what do you expect for free? you are talking as if you have some RIGHT to DEMAND that things get done according to YOUR needs. Nobody would mind if you politely asked how do i get this working? - but you antagonise people by demanding your system is fucked, fix it for me!. We're all volunteers here, debian developers users alike...we dont have to put up with your abusive attitude. 2. if you have a problem then you are more likely to get help by sticking to the technical issues rather than starting things off by saying how crappy useless broken debian is. We know debian isn't perfect. If you have constructive suggestions to make, then make them, but don't expect everyone to jump immediately and say yes master! at once, master!. If you can improve things, then work on improving them - debian development is OPEN. The distinction between debian developers and debian users is not very clear-cut. If you have flames, then keep them to yourself (or save them for some commercial software support line) Nobody decides to ...throw the user to the lions... on this or any other poing in debian. Package developer's are only human (and they're volunteers...some even have real lives outside of computers and the net and debian)...they CANT think of and cater for every situation. If you, or any user, has constructive suggestions to make then make them. 3. some things are complex. some things do require a willingness to read documentation. some things do need a little brainpower to figure out. A fair amount of DIY attitude is needed if you want to run a unix system. This is especially true for someone who calls themselves a SysAdmin and an ISP. There's a lot more to the job than just the title. An ISP who doesn't understand PPP and who is unwilling to read documentation (But I shouldn't have to.) is one who i would have no hesitation in recommending people to steer clear of. There is a particular logical, methodical way of thinking/seeing which is very useful for solving technical problems...you don't seem to have it. 4. it seems to me that you are in this for the flaming and not to resolve your technical problems. You seem to respond only to those replies which have the most flame potential and completely ignore those which have reasonable suggestions for things you could try (e.g. my multi-point post of a few days ago was completely ignored) 5. debian-user is a much more pleasant mailing list without all the flames. I suggest that everyone ignore any further posts from you until you learn some manners. 6. I donate my time to try to help out people on this mailing list for free. I do this sort of support for a living, and spending time helping out in here is one of my ways of putting some energy back into debian. However, I am not willing to do that for anyone as abusive as you. I'm a volunteer and dont have to put up with such shit. Contact me for my standard consulting rates if you want any further email support from me. 7. You get what you pay for. caveat emptor. craig
Re: How to get your lan on the internet
On Mon, 3 Mar 1997, QUALITY ASSURANCE wrote: Debians: 6. edit /etc/init.d/network and append the following line. ipfwadm -F -a accept -m -P all -S XXX.XXX.XXX.0/24 -D 0.0.0.0/ Where XXX.XXX.XXX is your network ip address or the first three octets of your lan interface Use: ipfwadm -F -a accept -m -P all -S x.x.x.0/24 -D 0.0.0.0/0 -W eth0 That will at least help prevent 'hackers' ; Jason
list server coming back up
The list server will be back up properly in a few hours. It is currnetly running from a backup site, and I think we're going to transition it to operate from Bucknell U. soon. Thanks Bruce -- Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502 Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3
