Re: printing and .profile problems
Success! Thanks to everyone's copious outpouring of hints and advice, I easily fixed both my .profile and my printing problems. 1. I'm using bash and sure enough both the .bash_profile and .bashrc files were sitting right there in the user's home directory waiting to be noticed. I'm guessing that Slackware must not install those files there which is why I didn't have this problem previously. 2. I fixed the problem of the user not being able to print by fixing ownerships and permissions, namely: rwxrwsr_x root lp /usr/spool/lpd/hp4p and changed the five files, /usr/spool/lpd/hp4p/.seq, /errs, /input_filter, /lock and /status to ownership root.lp. (Under Slackware these ownerships were root.daemon). Thanks again for all the help. Warning, I hope everyone realizes now that I will return with many more problems now that these two are fixed. But not now, got to go to work. Chris Beamis
Debian-Talk List Downtime
Hi folks, this list is not very active so no one would have noticed that the debian-talk incarnation of majordomo was not working for the last few weeks. Hehe, we installed debian on the list servers host... and, in short, messed up with the lists we are carrying in the changeover. All I have is an earlier list with about half the members, so, if you don't want to be on debian-talk then please unsubcribe again, and the grandest of apologies for any inconvenience. To: [EMAIL PROTECTED] Subject: nada unsubscribe debian-talk OR, use this web interface; http://www.vv.com.au/cgi-bin/vv/mailserv/majordomo -- Mark Constable (+61 7 55275724) http://vv.com.au
Re: The "*" character (was: Latex )
On Thu, 08 Aug 1996 10:34:27 +1000 Mark Phillips ([EMAIL PROTECTED]
edu.au) wrote:
> >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?
By default, bash expands shell metacharacters (*?[]) only if they're a match
({} rules are the exception, they're always expanded). Otherwise, bash passes
the metacharacters to the invoked program.
Tcsh will complain and abort if it cannot expand some metacharacters. You need
to quote them.
Solution: always quote shell metacharacters when you want to pass them to a
program.
Phil.
Re: Two bug reports on installation floppies
At 01:33 PM 8/8/96 +0800, Lindsay Allen wrote:
>2) Something amiss with hostname. When I boot I get the message:
>none: Host name lookup failure
I came across the same thing. A closer look at /etc/init.d/network learned
that if one selects 'none' for the Gateway, an entry GATEWAY=none is added
to this file.
The:
route add default gw ${GATEWAY} metric 1
command results in the message you encountered.
This seems like a minor bug in the script to me, but is easily overcome by
changing 'none' in your system ip-number. Or am I committing a sin against
the laws of ip here?
Success,
Erik van der Meulen
[EMAIL PROTECTED]
Consensus about /bin/perl.
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. Thanks -- Rob
How do I get GATEWAY2000 PS/2 mouse to work ? (fwd)
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 ?
Re: printing and .profile problems
At 05:49 PM 8/7/96 -0400, Susan G. 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. > There is a group called linux.debian.user that I can access with my News Xpress program operating under Win3.1. I just checked to be sure and all the messages in this thread were there. Is it just a mirror of this mail group and not a real newsgroup? >I'm not sure what you mean that dselect didn't set up the printer >"correctly", in this sense: the various files and directories for >lpr and lpd can be configured in any one of several ways, >using a variety of approaches. The HOWTO's refer to Linux in general, and >not to the Debian distribution in particular. Debian uses these >permissions for directories in /usr/spool/lpd: > >drwxrwsr-x 2 root lp 1024 Jul 27 14:20 lp1/ >drwxrwsr-x 2 root lp 1024 Aug 7 16:15 lp2/ > >where lp1 and lp2 correspond to 2 different stanzas in /etc/printcap. > >User 'lp' is defined this way in /etc/passwd: >lp:*:7:7:lp:/var/spool/lpd:/bin/sh > >and group 'lp is defined this way in /etc/group: >lp:*:7:lp > >If you've changed many of those things, you might want to try the >settings above and see if they work. > >Good luck, >Susan Kleinmann > What I meant when I said that lpr didn't work was simply that when I tried using it nothing came out of the printer. I didn't try to diagnose it, I just set up the way I always have in the past. I'm preparing to try these hints plus all the others I've received and will report back. Thanks Chris Beamis >
Re: Supported fast graphics cards?
> > I've been asked which graphics card to get for a purchase of 5 > systems to run Linux. There are a lot of new cards out there > and new versions of cards I was familiar with but enough has > changed that I'm not sure exactly what to specify. > > I and some friends have Mach64 cards at home that we bought about > a year ago and are very hapily running Debian Linux on but what > would I specify to get a XFree86 X-Server compatible graphics > card now? > > If you have a recomendation for a _specific_ model of graphics > card that you know works (1280x1024x256), please let me know. > It will speed my search. > > Thanks. > > -- > > David M. Cooke [EMAIL PROTECTED] > I have one of the newer Mach64 cards. From what I've heard basically all of the Mach64 cards are supported by the latest versions of XFree86. I must point out though that the Mach64 cards that are about 1 year old work just great with the current release of XFree86 but that the ones that are about 6 months old or so are only supported by the newest current beta release of the server. So, if you are planning to get Mach64 cards.. you shouldn't have a problem getting them to work but you will have to use the newest beta release of XFree86 which I don't believe is currently available in the Debian release. Cheers! Richard.. - Richard Dansereau Email: [EMAIL PROTECTED] Home page: http://pobox.com/~rdanse Electrical and Computer Engineering - University of Manitoba - Canada -
Re: The "*" character (was: Latex )
On Thu, 8 Aug 1996, Mark Phillips wrote: > > 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? Yes, there is a difference when the globbing doesn't expand to anything. In this case bash passes the word with the wildcards while tcsh just errors. For example: $ ls $ echo *tex* *tex* $ ./nosuchfile *tex* bash: ./nosuchfile: No such file or directory. $ tcsh > echo *tex* echo: No match. > ./nosuchfile *tex* ./nosuchfile: No match. tcsh is pretty broken to issue make it seem as if commands that don't exist are issuing errors. Guy
Re: Adding nfs and ip modules to base
[EMAIL PROTECTED] writes: > > > Hi, > > During installation I was prompted to select some modules to > install. > > I wanted nfs but it replied > > nfs_mknod undefined > nfs_sillyrename_create undefined > nfs_create undefined undefined > nfs_mkdir undefined undefined > nfs_lookup_cache undefined undefined > nfs_rename undefined undefined > nfs_lookup undefined undefined > nfs_nfs_rmdir undefined undefined > nfs_link undefined > nfs_refresh_inode undefined > nfs_symlink undefined > nfs_unlink undefined > Loading failed ! The module symbols > (from linux-2.0.6) don't match your linux-2.0.6 > Installation failed > > For the internet protocol drivers it said: > Can't locate module console > > And for my ne2000 card: > ne.c : Module autoprobing not allowed > append "io=0xNNN" values > > (Howabout pointer to Ethernet Howto in Installation doc > where values to try above can be found) > > I also tried (with identical results): > modprobe -t fs nfs.o > > > Fortunatly, can still use computer since didn't overwrite > previous system. However, can't install Debian since cannot > mount the nfs drive where distribution will be kept. > I get exactly the same set of problems and also have a half-formed 1.1 system. Any help is certainly appreciated. -- - | Alvin BirdiEmail: [EMAIL PROTECTED] | | School of Economic Studies Tel: 0161 275-4791 | | University of Manchester Fax: 0161 275-4812 | | Manchester M13 9PL UK | -
Re: Two Questions
>Tim O'Brien wrote: > >> Someone correct me if I'm wrong, but I think there is a problem with the >> Diamond card. If memory serves me well, Diamond does not publicize code >> to drive their cards without signing a non-disclosure agreement. Since >> Linux includes all source code under GNU, this would break the NDA and >> cause all sortsa trouble. > >Well You wrong .. :)... It was just that you had to invoke a -bpp 16 >switch when you started X... BUT I think your answer still applys >for the Matrox cards... Diamond was like that before (2 years ago or so) Ok, I stand corrected. As a matter of fact, I think it was probably about 2 years or so ago that I heard this. Tim --- I am Pentium of Borg. Division is futile. You will be APPROXIMATED! [EMAIL PROTECTED] <-- (Primary email) ---
Nearly perfect!
It seems that I have nearly conquered my uucp and sendmail installation. Thanks to the contribution of this list, no doubt. Receiving mail works like a charm. Outbound mail gets queued as one might expect. Uucico does its jobs. Log files show my mail has left my machine. It just does not arrive at its destination! As I said, nearly perfect. The only difference I notice between my new setup and my old Slackware/HDB/sendmail configuration is that uustat -a gives: Executing rmail ncm.nl!eme with the new box Executing rmail [EMAIL PROTECTED] with the old configuration As far as I know both should be valid. I really have no clue as to what goes on, I do not even get some sort of bounce (after eight hours that is). I was hoping anyone out here might have an idea as to what might still be wrong. My sendmail.mc file is listed below, just in case. Thanks all for any comment! Erik van der Meulen [EMAIL PROTECTED] [EMAIL PROTECTED] -- # # This file is used to configure sendmail for use with Debian systems. # divert(0) VERSIONID(`@(#)sendmail.mc 8.7 (Linux) 3/5/96') OSTYPE(debian)dnl FEATURE(masquerade_envelope)dnl FEATURE(use_cw_file)dnl FEATURE(use_ct_file)dnl FEATURE(redirect)dnl FEATURE(nodns)dnl define(`confTO_QUEUEWARN', `1d')dnl MAILER(local)dnl MAILER(smtp)dnl Cwavondel.xs4all.nl MASQUERADE_AS(avondel.xs4all.nl)dnl ## Custom configurations below (will be preserved) MAILER(uucp)dnl define(`SMART_HOST', uucp:xs4all) -- My setup: ISP is called: xs4all.nl UUCP node: avondel
Re: what files does dselect/dpkg use to discern choices?
On Tue, 6 Aug 1996, David C Winters wrote: > > Now, to explain the question, since I can't understand the > Subject: line and I wrote it myself... > > I've got approximately 50 machines I need to build. My best > option for the initial system build, unless I've missed something, would > be to run deselect on one machine, then take a deselect-generated file > containing my selections and exporting that file to all the other > machines, so I can just start up dselect and choose "Install" without > having to go through "Select" on each. > How can I accomplish this? Which file(s) do I need to export in > order to make this happen? And, is there a better way to achieve the > same results? > I would suggest you look at UpGrade and base_list in the upgrades directory. The script was written to upgrade the base section, but is general in nature and will run on any list you make. If you start with the base system list, you can add the other packages you wish to upgrade. It is your responsibility to deal with depends (that is, packages that another package depends on must appear in the list first), but once you have a list that works, you only need to copy the script and the list to the other machines you wish to upgrade and run it. Since the script checks to see whether the package on the list has already been upgraded, you can continue to use the list, into the indefinate future, to do incremental upgrades as new versions of packages become available, or you can wait till the next release and use your old list. Any packages you wish to add to your installation just goes into the list in the proper place to obtain all it's dependancy needs. Check it out and let me know if it will work for you, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Re: printing and .profile problems
On Tue, 6 Aug 1996, chris beamis wrote: > > 2. another problem, which I didn't have under Slackware, is using a .profile > in the user's home area. I have just one line in it, "alias 'lo'=exit" which > has always worked before but the lo commanded doesn't get recognized. I also > tried renaming the file to .login but still no luck. Any ideas? > This line should look like: alias lo='exit' but NOT like: alias 'lo'=exit Did it work?!?!?!?!? Leszek Gerwatowski TG S.A Warsaw, Poland
Re: catch 22?
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes: >I've managed to get myself in a catch-22 kind of dilemma. In an effort >to get a working 2.0.0 kernel with the proper options to support IP >masquerading, somehow or other both my kernel-image and kernel-source >packages have gotten to a state where I'm stuck fast! I cannot >successfully build a kernel at this point, and I can't remove or reinstall >either of the packages. Attempting to reinstall results in errors >during the prerem or postrem scripts for both the source and image >package. Attempting to remove, errors with a recommendation to reinstall >(which fails of course!--hence the dilemma) before attempting to remove! >I am stuck in that proverbial hard place. > I had the same problem with a virgin Debian 1.1 installation. I investigated and found that the kernel-image/kernel-source postinst and prerm scripts reference "#! /bin/perl". However, on my virgin Debian 1.1 installation, there was no symlink from /bin/perl to /usr/bin/perl! I manually created the symlink and that fixed the problem. I've been meaning to report this as a bug - but I haven't figured out how to do that yet... - Jim
Re: Discrepancies between mirror sites
In your email to me, Mark Phillips, you wrote: > > > Mark> Is there any way for mirror to discern timezone differences and > > Mark> adjust times accordingly? If the answer is no, then surely we should > > Mark> ask all debian mirrors not to alter time stamps? > > > >We could try to persuade _all_ mirrors to use > > use_timelocal=false > > This suggestions seems very sensible. Is there an official way to > persuade? Easy! (In my case) Done on sun10.sep.bnl.gov and llug2.sep.bnl.gov. Both are updating the time/date stamps off master.debian.org right now. Tim -- [EMAIL PROTECTED] "Have you ever seen an atom, Little bits of everything floating by, Take a good look at them, Collectively they compose all you see including your eye" - "Whoops" - Blues Traveler ** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.**
Re: The "*" character (was: Latex )
Mark Phillips wrote: : : >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? Under sh-lish shells `*' expands to all files, if any, or to '*' itsself, if no files/dirs match. Under csh-lish shells `*' expands to all files, if any, or to _nothing_ (and a note `no match') if nothing matches. AFAIK ... Heiko -- email : [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] pgp : A1 7D F6 7B 69 73 48 35 E1 DE 21 A7 A8 9A 77 92 finger: [EMAIL PROTECTED] [EMAIL PROTECTED]
Help needed using Sun 'automount' map with Debian's amd.
We have a Sun lab where all the home directories are automounted using Sun's 'automount' command. Now we're adding 20 Debian boxes to this lab. The home directories are all 'automounted' under /home/users (so user 'foo' has home dir /home/users/foo). Where to get each home dir is described by the NIS map 'auto.home'. Entries in the map look like this: foo orion.ee.mcgill.ca:/.home.9/& where user 'foo' is the NIS key for the map and 'orion.ee.mcgill.ca:/.home.9' is where foo's home dir is located. How do I get amd to work with that setup? Please help... We need to get this working... and we need it bad. Christian
Re: Floppy won't boot with internal cache enabled
On Tue, 6 Aug 1996, Steve Gaarder wrote: > I am installing Debian 1.1.1 on a generic clone with an AMD 486 on an > Opti-based motherboard. If I have the internal cache enabled in setup, > I get the error "invalid compressed format" after the "uncompressing > Linux" message. If I disable the cache, it boots fine. It boots ok > from the hard drive either way. Anyone know what is going on? This message indicates that incorrect data was read from the floppy. Since disabling the cache fixes it, you have verified that the floppy itself contains valid data and the problem comes after that. Guy Maor: > Try to enable it but make the timings more conservative. > You're probably seeing hardware problems; your L2 cache is being > addressed too quickly. Good idea. Try it. I have another suggestion if that does not work. If I am not mistaken, loading the root disk is the first place where the Linux floppy driver is used. The boot disk is read using BIOS. Try to exercise the floppy from Linux with your cache enabled by writing a large file to it, popping out and re-inserting the floppy, and reading back the file. Use "md5sum" to see if the data matches. 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. This block cache has nothing to do with the cache you are enabling and disabling. If there's a problem, I would suspect the Linux floppy driver (which sometimes needs to be tuned for various systems), but it could be something that is solved by changing a DMA speed setting in your BIOS set-up menu as well. Thanks Bruce
Re: catch 22?
On Wed, 7 Aug 1996 [EMAIL PROTECTED] wrote: > Thanks for the try Guy, but no help there. Been there, done that. The > remove (or forced install) doesn't work either, for the same reason. > The prerem and/or the postrem script fails. Actually, I thought the force > option would be the answer, but I haven't been successful with it yet. You'll have to examine the prerm or postrm in question to see why it fails. You'll then have to correct the problem so you can remove the package. Be sure and file a bug report explaining the problem. Guy
System.map
I've compiled custom kernels that weren't part of any debian distribution yet (2.0.7 patched with aic7xxx fixes). In /var/adm/messages there's a complaint that the booting kernel couldn't read the map. Checking old /var/adm/messages, it appears that what's wanted is the file System.map which appears to be in the directory where I built the kernel. How should I set things up so this file is found? Also, how serious is it when it's not found? A third question. I noticed a file called "debian-rules" in the source directory for one of the distribution kernels. Should I use this to make a debian-style installation of my custom kernel, or only if I want to make a particular custom kernel into a debian package? If I should use it, what extra files (besides kernel-2.x.x.tar.gz) do I need? Thanks Danny Heap, UCSF, California St., Room 102, SF CA, 94122 [EMAIL PROTECTED], voice: (415) 476-8910, fax: (415) 476-1508
Re: Floppy won't boot with internal cache enabled
Steve Gaarder wrote: > > I am installing Debian 1.1.1 on a generic clone with an AMD 486 on an > Opti-based motherboard. If I have the internal cache enabled in setup, > I get the error "invalid compressed format" after the "uncompressing > Linux" message. If I disable the cache, it boots fine. It boots ok > from the hard drive either way. Anyone know what is going on? > > thanks, I had this problem when I used EDO RAM on a motherboard that did not support EDO...just a thought mike cotherman
Re: printing and .profile problems
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. > Anyway, I just installed Debian 1.1.2 in late July (my first Debian > installation), with a few problems. ... > > 1. dselect didn't configure lpr correctly so I did it myself using the > printing HOWTO which I've done successfully many times before with Slackware > releases. Now root can print but users get the message, "usr can't create > /usr/spool/lpd/hp4p/.seq". This is with the permissions on that file set to > rw_rw_r as the HOWTO says. I tried changing the permissions to rw_rw_rw but > then a user gets the message "usr can't create > /usr/spool/lpd/hp4p/tfA006Aa01777". As far as I know I have the permissions > set correctly in all the directories leading to this file, but this seems > like a permission problem. I'm stuck! I'm not sure what you mean that dselect didn't set up the printer "correctly", in this sense: the various files and directories for lpr and lpd can be configured in any one of several ways, using a variety of approaches. The HOWTO's refer to Linux in general, and not to the Debian distribution in particular. Debian uses these permissions for directories in /usr/spool/lpd: drwxrwsr-x 2 root lp 1024 Jul 27 14:20 lp1/ drwxrwsr-x 2 root lp 1024 Aug 7 16:15 lp2/ where lp1 and lp2 correspond to 2 different stanzas in /etc/printcap. User 'lp' is defined this way in /etc/passwd: lp:*:7:7:lp:/var/spool/lpd:/bin/sh and group 'lp is defined this way in /etc/group: lp:*:7:lp If you've changed many of those things, you might want to try the settings above and see if they work. Good luck, Susan Kleinmann
Re: The "*" character (was: Latex )
Mark, When using wildcards in bash, the shell attempts to expand them, but if it finds nothing that matches the specified pattern, it passes the wildcard string to the command. Quoting the wildcard pattern causes the shell to pass it as a single argument to the command. In your case, since there was no file in the directory you were executing from that matched the pattern *tex*, bash behaved as if you had quoted the pattern. Since I don't use tcsh, I couldn't say for certain, but my understanding is that it treats wildcards in a slightly different manner - always attempting the expansion and returning an error message if the no matches are found. To pass an argument containing wildcards, the pattern must be quoted. This would explain why: bash$ dpkg -l *tex* worked, and: tcsh% dpkg -l *tex* did not. In any case, as a matter of good style, you should always quote wildcards when you don't want them expanded - even if you know you can get away without it. Hope this clarifies things... Gerry
Re: printing and .profile problems
Just a note .. if you have a ~/.bash_profile file than bash will ignore your .profile file. Don't forget everyone here is making an assumption you are using the bash shell .. if you are using a csh derivative than the .profile will be ignored and those same commands will not work. The csh version of an alias is alias lo 'logout' Good luck, Michael > > At 03:13 PM 8/7/96 +0200, [EMAIL PROTECTED] wrote: > >On Tue, 6 Aug 1996, chris beamis wrote: > > > >> > >> 2. another problem, which I didn't have under Slackware, is using a > >> .profile > >> in the user's home area. I have just one line in it, "alias 'lo'=exit" > >> which > >> has always worked before but the lo commanded doesn't get recognized. I > >> also > >> tried renaming the file to .login but still no luck. Any ideas? > >> > > > >This line should look like: > > > >alias lo='exit' > > > >but NOT like: > > > >alias 'lo'=exit > > > >Did it work?!?!?!?!? > > > > > >Leszek Gerwatowski > >TG S.A > >Warsaw, Poland > > > > > > Leszek, > Sorry, I should have mentioned that it is the same .profile which I've > always used successfully with Slackware releases. I was going from memory > which is the only reason I got the quotes wrong. There is something else > going on causing bash or something to ignore my .profile. > > Thanks anyway. > > Chris Beamis > >
Re: getting the mouse to work
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 :-) Good luck! Richard G. Roberto [EMAIL PROTECTED] 201-739-2886 - whippany, nj -- *** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. ***
Re: The "*" character (was: Latex )
>Hi Mark -- >You asked: >> because I'd said: >> >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? > > >What I'd written was actually not right for either shell. > >I should have written: > > dpkg -l "*tex*" > >The problem is that without the quotes, the shell expands the argument >first, before handing it to dpkg. If there's a file in your current >directory with a name that matches *tex*, then that file, and only that >file, is fed to dpkg. This is not what's intended of course. > >So I tried the correct usage (with the quotes) under tcsh and it worked >fine. But the interesting thing is that dpkg -l *tex* actually _works_ when run under bash, leading me to think that the bash shell doesn't expand the argument first. Mark.
Re: catch 22?
On Tue, 6 Aug 1996 [EMAIL PROTECTED] wrote: > Is there some way to force dpkg to reinstall (or remove) in spite of the > error it encounters attempting to remove the older package first? Type `dpkg --force-help' for instructions on forcing options. I think you want --force-remove-reinstreq. Be forewarned that you can seriously damage your installation with some of these options. Guy
Re: Cannot compile mouse support - help!
Hi jj, You are lucky! we must be the only Debian Linux users with the same mouse and graphic card on this planet :-). From reading your mail it seems you have gone all the way through it... Oooops!!! Wait a minute. Try: # gpm -t 'bm' -m /dev/inportbm Remember from the busmouse HOWTO: one thing is the protocol (busmouse) and the other the hardware interface or device driver (/dev/inportbm) For me it worked "out of the box". Well, you already know... after recompiling as you did. I have choosen busmouse compiled in, but it should work as a a module too. I prefer to see that the "...mouse is detected" when running dmesg. The only difference between your setup and mine is the interrupt which I have on IRQ=5 (I thought it was the default for this mouse!). But maybe you don't want that because of conflicts... Anyway, this is just to give you some hope: busmouse (inportbm) on IRQ5 + ATI Ultra works fine for somebody else. Just a comment I find useful to minimize the changes when switching mice (serial <-> busmouse). I don't use the real device names (ttySn or inportbm) but a link to them via: # (cd /dev ; ln -sf inportbm mouse) or # (cd /dev ; ln -sf ttyS0 mouse) and start both gmp (look at /etc/init.d/gpm ) and X (look at etc/X11/XF86Config) by pointing to /dev/mouse. Then only change you need to do when switching mice is the protocol: [bm|ms] for gpm and [Busmouse|Microsoft(<-check please)] for X. e.g. for gpm gpm -t bm # -m is /dev/mouse is default. or gpm # ms is the default and mouse is the default too! Check the sintax on the man page. Hope it helps! Lazaro <[EMAIL PROTECTED]> P.S. Warning to other newcomers and busmice owners: The standard 2.0.6 kernel in the boot.bin 1996-07-14 disks does not include the module for busmice). Under special-kernels/.. many of the 2.0.5 images do support the busmice drivers as modules. The Config with whiche they were created is there too. For me was easier to recompile :-) >_ Reply Separator _ >Subject: Cannot compile mouse support - help! >Author: debian-user@lists.debian.org at cclink >Date:08.08.96 15:43 > > >Hi all, > > I'm trying to compile mouse support into my kernel (2.0.6), but for the >life of me I can't get the mouse to function. I have a busmouse on an >ATI Graphics Ultra + card (which the HOWTO says is a regular busmouse, >NOT an ATI busmouse). When I run MSD under dos, it reports a busmouse >using IRQ4. So far, so good. > > When I try to use the mouse (gpm -m /dev/inportbm) I just get the >message "/dev/inportbm - No such device". So I tried removing the >inportbm and recreating it (mknod /dev/inportbm c 10 2); running the >"file" command on the new inportbm indicates that it is a character >special (10, 2). Still no luck - no such device. > > > I've tried compiling with busmouse support and NO serial support, >compiling with serial support and NO busmouse support, and compiling >with both busmouse AND serial support. In all cases I get "no such device" >when using /dev/inportbm. On the two kernels with serial support, the >gpm -m /dev/ttys0 command does not fail with an error, but it does not >provide any visible mouse support either. And I have checked that >busmouse.h #defines MOUSE_IRQ = 4. I set both serial and busmouse support >to be in the kernel, not in modules. > > I've read the busmouse-HOWTO and the FAQ and have not been able to >solve this problem. Does anybody have any ideas what I'm doing wrong here? >The mouse works fine under DOS/Windows, so it shouldn't be a hardware problem. > > Thanks all. > >-jj
Unable to mount IDE ATAPI CDROM
Hi, I installed Debian GNU/Linux base system using floppies ( 0.93R6 kernel 1.2.13) My problem is, I have a IDE ATAPI Mitsumi 4X CD ROM connected to first IDE as secondary device which is recognized at boot time hdb: FX001DE, ATAPI, CDROM I also notice that it loads 'isofs' filesystem . When I try to mount it by 'mount -t iso9660 /dev/hdb /cdrom' the system hangs ! so is with the following commands 1. mount -t iso9660 -r /dev/hdb /cdrom 2. mount -o ro /dev/hdb /cdrom 3. mount /dev/hdb /cdrom 4. mount -t iso9660 /dev/hdb /cdrom -o,ro,block=2048 The only way out is to hard reset (switch off/on) the system. I had Slackware running (Kernel 1.2.13) which recognizes my CD ROM. My system configuration --- Pentium -75MHz RAM -8Mb First IDE: 1.2 Gb Hard disk , IDE ATAPI mitsumi CD ROM. Second IDE: 1.6 Gb Hard disk , blank. PS/2 - Bus Mouse. SVGA - Cirrus chip set. Thanks in advance for any advice. Sincerely, Shankar
Supported fast graphics cards?
I've been asked which graphics card to get for a purchase of 5 systems to run Linux. There are a lot of new cards out there and new versions of cards I was familiar with but enough has changed that I'm not sure exactly what to specify. I and some friends have Mach64 cards at home that we bought about a year ago and are very hapily running Debian Linux on but what would I specify to get a XFree86 X-Server compatible graphics card now? If you have a recomendation for a _specific_ model of graphics card that you know works (1280x1024x256), please let me know. It will speed my search. Thanks. -- David M. Cooke [EMAIL PROTECTED]
Re: catch 22?
On 14:19:59 Guy Maor wrote: >>On Tue, 6 Aug 1996 [EMAIL PROTECTED] wrote: > >> Is there some way to force dpkg to reinstall (or remove) in spite of the >> error it encounters attempting to remove the older package first? > >Type `dpkg --force-help' for instructions on forcing options. I think >you want --force-remove-reinstreq. Be forewarned that you can >seriously damage your installation with some of these options. > >Guy Thanks for the try Guy, but no help there. Been there, done that. The remove (or forced install) doesn't work either, for the same reason. The prerem and/or the postrem script fails. Actually, I thought the force option would be the answer, but I haven't been successful with it yet. Paul
HELP ON DNS
Hello, Firstly let me introduce myself as a B. Tech Computer Science and Engineering student at University of Mauritius. For my final year, I have to do a project namely: 'Design and Implementation of a Dynamic Domain Name Server for host configuration on a LAN.' If, for e. g., a new server joins the LAN, the Domain Name Server automatically updates a lookup table automatically. TCP/IP protocol is being used to implement. We are planning to proceed as follows: As soon as a new server joins the network, it broadcast its ethernet address. When the name server gets the message then sends a packet using the ethernet address to the server and gives it a name and an IP address. Then the name server pings the new server to see if everything is OK. I shall be much grateful how can I find the said new server using ethernet address? Please send me some more information on the netbeui protocol. Thank you for your attention Osman - E-mail: [EMAIL PROTECTED] Date: 08/07/96 Time: 19:16:31 -
Re: XServer for ET4000/W32p hangs!!
On Wed, 7 Aug 1996, Mark Phillips wrote: > Hi, > > I have a friend who I am trying to help install debian 1.1. He has an > ET4000/W32p graphics card. I installed the appropriate server, went > through the xbase-configure program to create an XF86Config file, and > then ran "X -probeonly 2> out.txt" to try and get a clock line. The > system just hung and I had to do a Ctr-Alt-Del to get out. > > I couldn't work out what the problem was. Any ideas? I include the > out.txt file below. There are many problems with the ET4000/W32 cards. You can try a beta version from XFREE or try my solution--replace the card with one that works under the present XFREE86 distribution. Syrus. -- Syrus Nemat-Nasser <[EMAIL PROTECTED]>UCSD Physics Dept.
Re: Floppy won't boot with internal cache enabled
On Tue, 6 Aug 1996, Steve Gaarder wrote: > I am installing Debian 1.1.1 on a generic clone with an AMD 486 on an > Opti-based motherboard. If I have the internal cache enabled in setup, > I get the error "invalid compressed format" after the "uncompressing > Linux" message. If I disable the cache, it boots fine. It boots ok > from the hard drive either way. Anyone know what is going on? I don't see how this could happen with an L1 cache (internal), but it could with an L2 (external). Were you perhaps enabling and disabling the external? Try to enable it but make the timings more conservative. You're probably seeing hardware problems; your L2 cache is being addressed too quickly. Guy
Re: unreliable service of I-Connect
On Tue, 06 Aug 1996 09:24:01 GMT, you wrote: >I am to in this situation: waiting for the CD for 4 weeks. I can't >have any response from Simon Shapiro (I-Connect) on my order since 2 >weeks so I am considering to ftp the files and master a CD for my use. > >bye, Daniel > > >-- >Daniel ANDRE, [EMAIL PROTECTED]IRIS Technologies > 155 rue Jules Delcenserie, Bat B3 > 59700 MARCQ en BAROEUL, FRANCE > > I have ordered two Debian CDs in July (one about the 1st of July, one about the 15th) and I have received them two weeks later in each case, so I am glad to say I am very pleased with i-connect. Hubert Fauque [EMAIL PROTECTED]
Re: catch 22?
Jim Pick wrote on 08 Aug 1996 04:44:21 +1000: wb2oyc> <...> In an effort to get a working 2.0.0 kernel with the wb2oyc> proper options <...> results in errors during the prerem wb2oyc> or postrem scripts for both the source and image package. Jim> I had the same problem with a virgin Debian 1.1 installation. Jim> I investigated and found that the kernel-image/kernel-source Jim> postinst and prerm scripts reference "#! /bin/perl". Jim> However, on my virgin Debian 1.1 installation, there was no Jim> symlink from /bin/perl to /usr/bin/perl! I manually created Jim> the symlink and that fixed the problem. This is Bug#3951 I think. I had the same problem. Cheers, Graham
Re: dselect/dpkg problem: install/remove
> I tried to use dselect to > purge the kernel-source package and again dpkg crashed, this time > leaving me with a hung system. All I could do was power cycle my > machine since the keyboard was apparently frozen and I could not > log in on any other consoles. This left me with a bad disk which > I cannot fix because now e2fsck crashes with a segmentation > fault. It's not likely that dpkg/dselect put the system in this state on its own. Things that wedge the system and then make e2fsck not run generally have to do with the shared library files containing corrupt data. This could be a problem with the data on the disk, or bad RAM. Probably a re-install would be a good idea at this point, since the data on the disk is suspect. We have taken some hits because we were using a brand-new Linux 2.0 kernel, but this does not sound like one of those. People get upset when I point at hardware, because of course Windows 95 runs fine on the system and the power-on test passes. However, many people on this list have found that Linux exercises features of your system that DOS and Windows don't ever touch. We get a lot of "I really didn't believe it was hardware but then I fixed the hardware and it got better" email. I run Debian on 5 different computers without stability problems. Thanks Bruce
Re: The "*" character (was: Latex )
Hi Mark -- You asked: > because I'd said: > >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? What I'd written was actually not right for either shell. I should have written: dpkg -l "*tex*" The problem is that without the quotes, the shell expands the argument first, before handing it to dpkg. If there's a file in your current directory with a name that matches *tex*, then that file, and only that file, is fed to dpkg. This is not what's intended of course. So I tried the correct usage (with the quotes) under tcsh and it worked fine. Cheers, Susan
VFS: inode busy on removed device 03:01
I just set up a Linux system on a Syquest EZ135 removable IDE drive. Everything seems to work but I get this message (the one on the subject line) about 36 times during boot when the disk is being mounted. It also throws in the message: VFS: Root device 03:01: prepare for Armageddon Fortunately, Armageddon hasn't arrived, at least I don't think it has. Everything seems to work ok after the boot is complete. I also got this same message while LILO'ing the disk; LILO said it didn't install but my system boots just fine from the EZ135 anyway. It really doesn't appear to be causing any problems, I was just wondering if anyone out there knew what it meant. Thanks, Al Youngwerth [EMAIL PROTECTED] P.S. These Syquest drives are great. $119 list price for the IDE version with one disk. Very fast (uses the same technology as a hard drive).
Re: printing and .profile problems
At 03:13 PM 8/7/96 +0200, [EMAIL PROTECTED] wrote: >On Tue, 6 Aug 1996, chris beamis wrote: > >> >> 2. another problem, which I didn't have under Slackware, is using a .profile >> in the user's home area. I have just one line in it, "alias 'lo'=exit" which >> has always worked before but the lo commanded doesn't get recognized. I also >> tried renaming the file to .login but still no luck. Any ideas? >> > >This line should look like: > >alias lo='exit' > >but NOT like: > >alias 'lo'=exit > >Did it work?!?!?!?!? > > >Leszek Gerwatowski >TG S.A >Warsaw, Poland > > Leszek, Sorry, I should have mentioned that it is the same .profile which I've always used successfully with Slackware releases. I was going from memory which is the only reason I got the quotes wrong. There is something else going on causing bash or something to ignore my .profile. Thanks anyway. Chris Beamis
Re: a memory + SCSI error??
I hesitate to burden the list with an email that's more reminiscent of "Days of our Lives" than a bug report, but having suggested a couple of days ago that there might be problems with Linux's handling of memory or SCSI interfaces, I thought it might be constructive to report that the problems I encountered had nothing to do with Linux, Debian, or any of the utilities I was using, and everything to do with cleaning. I also thought it might be useful to summarize 'lessons learned'. In order to clean the inside of the box that had the 9 GB drive on it, the outer casing of the box had to be slid off. The box hadn't been constructed all that perfectly, so when the lid was finally removed, the drive heads got a real physical jolt. Basically, I was over-optimistic about the ruggedness of the Micropolis drive (which is now 2 years old). I suspect that the heads were misaligned when the box casing was removed, and that caused the errors when I rebooted. (The answer to questions about what I used for cleaning is: a nearly dry damp cloth. I gave the box lots of opportunity to dry after I cleaned it, so I don't think the two drops of water in the cloth was a problem. In fact I suspect that cleaning without a little water is sometimes more of a problem, due to static.) Lessons learned: -- Running fsck once on a broken partition isn't enough. It must be run more than once, especially if fsck ever asks: ... Ignore? -- Use 'reboot -n' after running fsck (suggestion from Sherwood Botsford). -- (of course) back up early and often. Reading and then applying the documentation on the 'tob' backup script is not only a lot less painful than going through the trauma that I went through for the last two days; it is actually pleasurable reading, a real rarity! Thanks to all for sympathy and suggestions while I was in the pits. Susan Kleinmann
Re: catch 22?
On 7 Aug 1996, Jim Pick wrote: > I had the same problem with a virgin Debian 1.1 installation. I > investigated and found that the kernel-image/kernel-source postinst > and prerm scripts reference "#! /bin/perl". > > However, on my virgin Debian 1.1 installation, there was no > symlink from /bin/perl to /usr/bin/perl! I manually created the > symlink and that fixed the problem. > > I've been meaning to report this as a bug - but I haven't figured out > how to do that yet... You don't need to report it, it's a known bug. It's been fixed in Debian 1.1.something. Christian
Re: lost lib
On Tue, 6 Aug 1996, Robert Van Horn wrote: > When I try to use ftp I get a message "ftp: can't find library 'librl.so.2'" > I also am not able to find this library any of the places I looked. I believe librl is the old a.out readline library. Are you running Debian 0.93r6? I highly encourage you to upgrade. Guy
Re: XServer for ET4000/W32p hangs!!
Syrus Nemat-Nasser wrote: : On Wed, 7 Aug 1996, Mark Phillips wrote: : : > Hi, : > : > I have a friend who I am trying to help install debian 1.1. He has an : > ET4000/W32p graphics card. I installed the appropriate server, went [snipped] : : There are many problems with the ET4000/W32 cards. You can try a beta : version from XFREE or try my solution--replace the card with one that : works under the present XFREE86 distribution. To clarify the situation: 3.1.2 had a few problems that caused them to not work with ET4000/W32 revisions A or B. (I have a revision A at home, FWIW.) These bugs have been fixed, and 3.1.2E works fine on my home system. I would suggest that you install 3.1.2, but not configure it, from the debian packages; move it to another directory (or tar it up), and replace it with the 3.1.2E distribution from ftp.xfree86.org or its mirrors. This should rectify the situation. -- Windows is not the answer. Windows is the question. Linux is the answer. http://sunsite.unc.edu/mdw/ for all your PC software requirements.
Re: printing and .profile problems
> On Tue, 6 Aug 1996, chris beamis wrote: >> 1. dselect didn't configure lpr correctly so I did it myself using the >> printing HOWTO which I've done successfully many times before with Slackware >> releases. Now root can print but users get the message, "usr can't create >> /usr/spool/lpd/hp4p/.seq". This is with the permissions on that file >> set to >> rw_rw_r as the HOWTO says. I tried changing the permissions to >> rw_rw_rw but then a user gets the message "usr can't create >> /usr/spool/lpd/hp4p/tfA006Aa01777". As far as I know I have the >> permissions set correctly in all the directories leading to this file, >> but this seems like a permission problem. I'm stuck! On the couple of Linux boxes I've set up recently, the directories under /usr/spool/lpd are chown'd either root or lp, and they're all chgrp'd lp. I have the permissions set to 775 (ie, rwxrwxr-x) and I haven't run into any problems so far. (The benefit of my following up with this is I'm sure someone will let me know if these perms will cause problems I haven't forseen or encountered...) > > 2. another problem, which I didn't have under Slackware, is using a .profile > > in the user's home area. I have just one line in it, "alias 'lo'=exit" which > > has always worked before but the lo commanded doesn't get recognized. I also > > tried renaming the file to .login but still no luck. Any ideas? On Wed, 7 Aug 1996 [EMAIL PROTECTED] wrote: > This line should look like: > alias lo='exit' First, the original message doesn't state what shell is being used. The construction of the sample alias command indicates it's of the Bourne family, but doesn't pin it down further than that. My answer assumes that the GNU Bourne-Again shell (bash, typically /bin/bash) is the subject. The single quotes are only necessary in cases where the command to be aliased contains spaces. I generally make more use of self- defined functions than aliases, but the single quotes are only needed in an example such as alias pico='pico -e -k -w -x -z' (This is using the pico that accompanies pine v3.94; don't know if earlier pico versions support all of these arguments.) David [EMAIL PROTECTED] aka [EMAIL PROTECTED] Office: 3503 WeH, x86720
Re: dns
sure, just specify: primary my.private.domain file.db and all dns lookups for my.private.domain will work. If you're talking about your "customers'" machines, that's a little tougher... the easiest trick is to set them up to have cacheing DNS nameservers, and set: forwarder slave (this is the obsolete keyword, look in the docs for the new keyword) I mention using cacheing DNS servers on your customer boxes. Since you're on a radio network, this is a good idea. If you can't do that, then make sure your customers always point ONLY to nameservers that can speak authoritatively for my.private.domain. Paul From: [EMAIL PROTECTED] (Mahoney, Hugh M.) Subject: dns I would like to set up a dns on linux. This name server will serve a private domain encompassing a wireless network. I will very shortly have dial-in access to a ISP to provide internet visibility to wireless network users. Is it possible to configure a private dns to resolve a name query and in the event the query fails forward the query to the Internet Service Providers domain name server ? Private names must be resolved locally by the linux dns and never require resolution over the internet. The private domain, at this time is not recognized by the internet community and names specific to the private domain cannot be resolved. Each private name would be entered manualy into a private dns cache. Any suggestions ?
Re: Help needed using Sun 'automount' map with Debian's amd.
Look at /usr/doc/amd there is a (untested!) script to convert automount to amd maps. Dominik Kubla (Maintainer)
Re: Adding nfs and ip modules to base
I had the same probs as Jay, and performed the same solution as Lazaro, with equal success. I used the kernel building package 'make-kpkg' to build my custom kernel. Jim > Hi Jay, > There have been some postings (since the 1.1.2 release) to this list > reporting the same problem. Check last week's ones as I sent a kind of > reports-log. I heard of no answers so I am not sure whther we are > exceptions# to the rule. > > My solution was to reinstall 1.1 (stable tree) download & install the > packages in the updates. Among them the kernel-source-2.0.6-0.i386.deb > (please check the name) but not the kernel-image. > I the recompiled the 2.0.6 with the debian script to create a kernel-image > package. Look at kernel source tree for a debian. . > As a result I got the kernel-image-2.0.6-choose.your.tag.here.deb which I > installed with dpkg (instructions are in the debian script) > Now I have a custom (leaner) kernel and no problems so ever with the > "undefined" messages. > > Lazaro > [EMAIL PROTECTED]> >__ Reply Separator _ >Subject: Adding nfs and ip modules to base >Author: debian-user@lists.debian.org at cclink >Date:07.08.96 05:25 > > >Hi, > >During installation I was prompted to select some modules to >install. > >I wanted nfs but it replied > > nfs_mknod undefined > nfs_sillyrename_create undefined > nfs_create undefined undefined > nfs_mkdir undefined undefined > nfs_lookup_cache undefined undefined > nfs_rename undefined undefined > nfs_lookup undefined undefined > nfs_nfs_rmdir undefined undefined > nfs_link undefined > nfs_refresh_inode undefined > nfs_symlink undefined > nfs_unlink undefined > Loading failed ! The module symbols > (from linux-2.0.6) don't match your linux-2.0.6 > Installation failed > >For the internet protocol drivers it said: > Can't locate module console > >And for my ne2000 card: > ne.c : Module autoprobing not allowed > append "io=0xNNN" values > > (Howabout pointer to Ethernet Howto in Installation doc > where values to try above can be found) > >I also tried (with identical results): > modprobe -t fs nfs.o > > >Fortunatly, can still use computer since didn't overwrite >previous system. However, can't install Debian since cannot >mount the nfs drive where distribution will be kept. > >Have read the Module-Howto and related Docs but can't find >a solution to these problems. I fed the first line of nfs >error message to dejanews using 200,000 linux messages and it >found nothing ! It looks simple, since the >messges don't seem cryptic, but what do I know ... > >Thanks in advance for any enlightenment, >Jay > > > > === Jim Gerace Senior Systems Engineer email: [EMAIL PROTECTED] www: http://www.kasinet.com
Cannot compile mouse support - help!
Hi all, I'm trying to compile mouse support into my kernel (2.0.6), but for the life of me I can't get the mouse to function. I have a busmouse on an ATI Graphics Ultra + card (which the HOWTO says is a regular busmouse, NOT an ATI busmouse). When I run MSD under dos, it reports a busmouse using IRQ4. So far, so good. When I try to use the mouse (gpm -m /dev/inportbm) I just get the message "/dev/inportbm - No such device". So I tried removing the inportbm and recreating it (mknod /dev/inportbm c 10 2); running the "file" command on the new inportbm indicates that it is a character special (10, 2). Still no luck - no such device. I've tried compiling with busmouse support and NO serial support, compiling with serial support and NO busmouse support, and compiling with both busmouse AND serial support. In all cases I get "no such device" when using /dev/inportbm. On the two kernels with serial support, the gpm -m /dev/ttys0 command does not fail with an error, but it does not provide any visible mouse support either. And I have checked that busmouse.h #defines MOUSE_IRQ = 4. I set both serial and busmouse support to be in the kernel, not in modules. I've read the busmouse-HOWTO and the FAQ and have not been able to solve this problem. Does anybody have any ideas what I'm doing wrong here? The mouse works fine under DOS/Windows, so it shouldn't be a hardware problem. Thanks all. -jj
Re: printing and .profile problems
Hi Chris - Is there an existing .bash_profile in that directory? I believe Debian by default gives you one. If so, .profile will not be read: Login shells: On login (subject to the -noprofile option): if /etc/profile exists, source it. if ~/.bash_profile exists, source it, else if ~/.bash_login exists, source it, else if ~/.profile exists, source it. (from the man page) So you could rework it one way or another to get your command sourced. (You can also instead just put it in .bashrc, which practically always gets read by interactive shells. But why leave this .profile ambiguity hanging anyway? :-) The other possibility is less likely: that you are somehow running a sub-shell, not a login shell. If you were using an xterm this might be the case. But any login from a console prompt should be a login shell, and read the startup files as specified above. Specifying login behavior, or the .bashrc solution, would work if it was a sub. Hth, -- Ed Donovan [EMAIL PROTECTED]
Re: Floppy won't boot with internal cache enabled
Guy Maor wrote: > > On Tue, 6 Aug 1996, Steve Gaarder wrote: > > > I am installing Debian 1.1.1 on a generic clone with an AMD 486 on an > > Opti-based motherboard. If I have the internal cache enabled in setup, > > I get the error "invalid compressed format" after the "uncompressing > > Linux" message. If I disable the cache, it boots fine. It boots ok > > from the hard drive either way. Anyone know what is going on? > > I don't see how this could happen with an L1 cache (internal), but it > could with an L2 (external). Were you perhaps enabling and disabling > the external? Try to enable it but make the timings more > conservative. You're probably seeing hardware problems; your L2 cache > is being addressed too quickly. > > Guy I had problems like this a couple years back when I was installing OS/2 on a Dell Machine (486,66mhz).. The installation would fail if I didn't disabel both L1 and L2 caches.. But I ripped out the TsengLab GFX card (VLB) and all troubles went away.. Ripping out gfx card is often not a option but the Dell MB had a Cyrrus Logic Chip on it...
Two bug reports on installation floppies
As I see it, the installation floppies (1996-07-14) have three problems: 1) There are unresolved sysmbols in the nfs and de4x5 modules. 2) Something amiss with hostname. When I boot I get the message: none: Host name lookup failure at the point where boot executes hostname --file /etc/hostname. I have edited /etc/issue to show hostname.domain and getty comes out with elm.(none). HTH Lindsay
Re: Ftp method in dselect
On 6 Aug 1996, Andy Guy wrote: > Al Youngwerth <[EMAIL PROTECTED]> writes: > > Guy: could you move dpkg-ftp into unstable, this would avoid these > problems. I agree... IMHO, the current version of dpkg-ftp is certainly good enough for 'unstable'. And since we're including it with the base disks now, it seems illogical to hide the .deb in project/experimental. Christian
dns
I would like to set up a dns on linux. This name server will serve a private domain encompassing a wireless network. I will very shortly have dial-in access to a ISP to provide internet visibility to wireless network users. Is it possible to configure a private dns to resolve a name query and in the event the query fails forward the query to the Internet Service Providers domain name server ? Private names must be resolved locally by the linux dns and never require resolution over the internet. The private domain, at this time is not recognized by the internet community and names specific to the private domain cannot be resolved. Each private name would be entered manualy into a private dns cache. Any suggestions ?
RE: catch 22?
On 23:36:54 [EMAIL PROTECTED] wrote: >> masquerading, somehow or other both my kernel-image and kernel-source >> packages have gotten to a state where I'm stuck fast! > >Before you try anything drastic, check the #!/... line of the >post-install scripts for the kernel. Mine pointed to a non- >existent perl. Either modify the script(s) or create a link >to the correct Perl. Once I had created the link, the install >went forward without a hitch. > Owen, Thanks for suggesting caution. Others have suggested the scripts having that error also. However, I have managed to resolve the dilemma. I tried Heiko's suggestion and edited my status file. I changed the kernel-source and image status to "purge ok not-installed". Then ran dselect, since I wanted to install a few other packages as well. All went fine! Except that now the postinst script fails. This is not dibilatating however as the source is now intact and the original kernel image (and the compressed) are where they should be. I believe this same error occured on the initial install of the kernel stuff as well. Paul
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? Thanks, Mark.
Re: Anyone want xanim as a deb package
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.
Recommendations on mother boards?
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. 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/
Re: XServer for ET4000/W32p hangs!!
>On Wed, 7 Aug 1996, Mark Phillips wrote: > >> Hi, >> >> I have a friend who I am trying to help install debian 1.1. He has an >> ET4000/W32p graphics card. I installed the appropriate server, went >> through the xbase-configure program to create an XF86Config file, and >> then ran "X -probeonly 2> out.txt" to try and get a clock line. The >> system just hung and I had to do a Ctr-Alt-Del to get out. >> >> I couldn't work out what the problem was. Any ideas? I include the >> out.txt file below. > >There are many problems with the ET4000/W32 cards. You can try a beta >version from XFREE or try my solution--replace the card with one that >works under the present XFREE86 distribution. Hmm, I thought it was supposed to work. Anyway, what cards would you recommend as being good and reliable, working well under the present XFree86? Thanks, Mark.
Re: XServer for ET4000/W32p hangs!!
On Thu, 8 Aug 1996, Mark Phillips wrote: > >On Wed, 7 Aug 1996, Mark Phillips wrote: > > > >There are many problems with the ET4000/W32 cards. You can try a beta > >version from XFREE or try my solution--replace the card with one that > >works under the present XFREE86 distribution. > > Hmm, I thought it was supposed to work. Anyway, what cards would you > recommend as being good and reliable, working well under the present > XFree86? I have used several versions of the Diamond Stealth 64 cards. I replaced a Stealth 32 (ET4000) with a Stealth 64 (S3 868 with 2M VRAM). I use a VLB Stealth 64 864 DRAM at home. I've also used the PCI version of the Stealth 64 DRAM with the Trios64 chipset at work--this one is now selling locally for as little as $77 in San Diego. The problem with Diamond is that they change their hardware versions almost every month, but all of the above work well and are accelerated with the S3 sever. I think it is probably possible to do better and/or go cheaper, but I've stuck with these cards on all of my machines. I spent about a day trying to get the W32 server to work with that Stealth 32. That was several months back. I read the postings on the Linux news groups and found that people were having limited success with the beta versions of XFREE, but they could not even get more than 256 colors. That's when I decided to swap the card with someone at work who doen't run Linux. Good luck. Syrus. -- Syrus Nemat-Nasser <[EMAIL PROTECTED]>UCSD Physics Dept.
Re: So which email package do you ,use
> W " "Bart," "Jr writes: W> so which email package do you folks like? For high-volume email users, I recommend Gnus which is a combined mail/news reader package for Emacs. Emacs is a Debian package and contains Gnus. kai -- What's a signature?
RE: catch 22?
> I've managed to get myself in a catch-22 kind of dilemma. In an effort > to get a working 2.0.0 kernel with the proper options to support IP > masquerading, somehow or other both my kernel-image and kernel-source > packages have gotten to a state where I'm stuck fast! Before you try anything drastic, check the #!/... line of the post-install scripts for the kernel. Mine pointed to a non- existent perl. Either modify the script(s) or create a link to the correct Perl. Once I had created the link, the install went forward without a hitch. Good luck, Owen
Anyone want xanim as a deb package
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. Shaya Potter [EMAIL PROTECTED]
Re: printing and .profile problems
Chris, I had the same problem with my profile. My work around was editing (creating?) the .bash_profile file. At least I think that's it, I'm at school now. It's just like .profile , but renamed to confuse us ! Good luck. Mike. On Wed, 7 Aug 1996, chris beamis wrote: > >> 2. another problem, which I didn't have under Slackware, is using a > >> .profile > >> in the user's home area. I have just one line in it, "alias 'lo'=exit" > >> which > >> has always worked before but the lo commanded doesn't get recognized. I > >> also > >> tried renaming the file to .login but still no luck. Any ideas? > > Leszek, > Sorry, I should have mentioned that it is the same .profile which I've > always used successfully with Slackware releases. I was going from memory > which is the only reason I got the quotes wrong. There is something else > going on causing bash or something to ignore my .profile. > > Thanks anyway. > > Chris Beamis > >
Re: The "*" character (was: Latex )
>> But the interesting thing is that dpkg -l *tex* actually _works_ when >> run under bash, leading me to think that the bash shell doesn't expand >> the argument first. >> >Are you sure you tried dpkg -l *tex* in a directory where you know there's >a file whose name matches the pattern *tex*, and whose name is not that >of a debian package? On my system both bash and tcsh behaved the same way. Very strange. Here is what I did on my system under bash: (mark, destiny)$ ls Maelstromgnuchesscmaelstromxonix Maelstrom_sound gnuchessnmirrormagic xp-replay acm gnuchessrnethack xpat2 acms gnuchessxpostprintxpilot cmailgnugopxboard xpilots fortune gnushogi xasteroids xshogi game gnushogirxbattle xsok gnuangnushogixxboard xtet42 gnuchess kill-acmsxinvadersxtron (mark, destiny)$ dpkg -l *tex* 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 +++-===-==- un X11-text-viewer (no description available) pn amslatex (no description available) pn amstex (no description available) pn auctex (no description available) pn bibtex (no description available) pn gettext (no description available) pn hyperlatex (no description available) pn latex(no description available) pn latex2e-doc (no description available) pn latex2rtf(no description available) ii nb-tex 2.1-1 NTeX package ii nb-texi 2.1-1 NTeX package ii ntex2.1-1 NTeX package ii nx-etex 2.1-1 NTeX package ii nx-mtex 2.1-1 NTeX package un tex (no description available) pn texbin (no description available) pn texidoc (no description available) ii texinfo 3.7-1 The GNU Project's documentation formatting s pn texlib (no description available) pn texpsfnt (no description available) pn textfm (no description available) ii textutils 1.19-1 The GNU text file processsing utilities. ii untex 9210-4 Remove LaTeX commands from input. (Which incidently is the same as what I get when I use the quotes) Mark.
Japanese support
Is there any support under Debian Linux for displaying or editing Japanese text?
nfs.o module in version 2.0.6
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: printing and .profile problems
On Wed, 7 Aug 1996, chris beamis wrote: > > Leszek, > Sorry, I should have mentioned that it is the same .profile which I've > always used successfully with Slackware releases. I was going from memory > which is the only reason I got the quotes wrong. There is something else > going on causing bash or something to ignore my .profile. > > Thanks anyway. > > Chris Beamis Is it named .profile? I have a .profile in /etc/ but in my home directory I use ".bash_profile" and ".bash_rc". [EMAIL PROTECTED]/GNU__1.1___Linux__2.0.11___ "Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come." -- Matt Groening
Re: printing and .profile problems
At 11:19 PM 8/6/96 -0700, you wrote: > >Hi, I hope I'm doing this right. I tried to post to the linux.debian.user >newsgroup without success. > >Anyway, I just installed Debian 1.1.2 in late July (my first Debian >installation), with a few problems. I've fixed some of them thanks to this >forum, but there are two among the many left that I'm trying to fix right now. > >1. dselect didn't configure lpr correctly so I did it myself using the >printing HOWTO which I've done successfully many times before with Slackware >releases. Now root can print but users get the message, "usr can't create >/usr/spool/lpd/hp4p/.seq". This is with the permissions on that file set to >rw_rw_r as the HOWTO says. I tried changing the permissions to rw_rw_rw but >then a user gets the message "usr can't create >/usr/spool/lpd/hp4p/tfA006Aa01777". As far as I know I have the permissions >set correctly in all the directories leading to this file, but this seems >like a permission problem. I'm stuck! Try this chmod 777 /usr/spool/lpd/hp4p/ and then chmod u+t /usr/spool/lpd/hp4p/ It sounds to me like lpr needs this area as a scratch pad before printing. Chmod u+t sets the sticky bit, which allows users to erase only files they create. This should clear up your problem, and if some Unix guru out there noticed my syntax was wrong please point out to the world so I don't make the same mistake myself ;>. Mike... >Thanks in advance for any help. > >Chris Beamis np
linux.debian.user newsgroup (Re: printing and .profile problems)
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. Just FWIW. (and, again FWIW, I'm mailing this to debian-user, not posting it.) -- Windows is not the answer. Windows is the question. Linux is the answer. http://sunsite.unc.edu/mdw/ for all your PC software requirements.
Re: dselect/dpkg problem: install/remove
> "john" == John Houwen <[EMAIL PROTECTED]> writes: > I seem to have a similar problem with dselect/dpkg, but not > with the dpkg-ftp option (haven't gotten that far yet) > The dselect package has given me problems from the first. I > made a few errors in my 1st attempt at the CDRom install, > but managed to get most of the selected packages unpacked & > installed. Where dselect hung was on the > kernel-source/kernel-headers packages. (where is > local/binary ??) [snip] This sounds like the problem that I'm having. I installed debian on a new system and all went well until I tried to use dselect to install the kernel-source package. While doing that, dpkg crashed with a segmentation fault. So I tried to use dselect to purge the kernel-source package and again dpkg crashed, this time leaving me with a hung system. All I could do was power cycle my machine since the keyboard was apparently frozen and I could not log in on any other consoles. This left me with a bad disk which I cannot fix because now e2fsck crashes with a segmentation fault. It looks like I'm going to have to reformat my hard disk and reinstall from scratch. :( I don't have any answers for you, but you are not alone. I'm tempted to try a different distribution in hopes of getting a stable system. I'll let you know if I come up with any solutions. Mike -- Michael A. Miller [EMAIL PROTECTED] Nuclear Physics Lab, University of Illinois, Urbana-Champaign PGP public key at http://www.uiuc.edu/ph/www/miller5>
Re: printing and .profile problems
In article <[EMAIL PROTECTED]>, chris beamis <[EMAIL PROTECTED]> wrote: >2. another problem, which I didn't have under Slackware, is using a .profile >in the user's home area. I have just one line in it, "alias 'lo'=exit" which >has always worked before but the lo commanded doesn't get recognized. I also >tried renaming the file to .login but still no luck. Any ideas? Check if there's a file called ".bash_profile" in the user's home directory (there probably will be; it's the default). If so, then bash will execute that when you start a login shell, and ignore the .profile. Try sticking the alias in ".bash_profile" or ".bashrc". >Thanks in advance for any help. No problem, hope it helps. -- M a l c . . . | "We've checked, and it's definitely not a bug. ([EMAIL PROTECTED]) | It's fixed in the new release." -- Help line.
Re: dselect/dpkg problem: install/remove
In article "John Houwen" <[EMAIL PROTECTED]> writes: > >I have tried to remove these packages, but upon running either >dselect or dpkg I get something along the lines of "Package is in an >unstable/condititon please re-install before attempting to remove" > The kernel-image, kernel-source and kernel-package packages have a bug in the installation scripts. The prerm and preinst scripts refer to #! /bin/perl . Unfortunately, on a virgin Debian 1.1 system, there is no /bin/perl. The solution is to create a symlink from /usr/bin/perl to /bin/perl. Then you should be able to de-install and re-install the kernel packages no problem. - Jim
Re: Compose characters in X
> which puzzles me. Why does the order differ? (BTW, in a mono xterm it > works like under Emacs.) I'm even more surprised, as color_xterm maintainer -- because color_xterm should only differ from mono xterm in, you guessed it, color features... as far as I can tell I'm building it with the same sources and options as the xbase xterm is using...
Re: printing and .profile problems
>2. another problem, which I didn't have under Slackware, is using a .profile >in the user's home area. I have just one line in it, "alias 'lo'=exit" which >has always worked before but the lo commanded doesn't get recognized. I also >tried renaming the file to .login but still no luck. Any ideas? If .bash_profile or .bash_login are present .profile will not be used >From the bash info file > -- File: features.info, Node: Bash Startup Files, Next: Is This Shell Interactive?, Prev: Invoking Bash, Up: Bash Specific Features Bash Startup Files == When and how Bash executes startup files. For Login shells (subject to the`~/.profile' exists, then source it. If `~/.bash_profile' exists, then source it, else if `~/.bash_login' exists, then source it, else if `~/.profile' exists, then source it.
Re: The "*" character (was: Latex )
Hi Mark -- You said: > Very strange. Here is what I did on my system under bash: > > (mark, destiny)$ ls > Maelstromgnuchesscmaelstromxonix > Maelstrom_sound gnuchessnmirrormagic xp-replay > acm gnuchessrnethack xpat2 > acms gnuchessxpostprintxpilot > cmailgnugopxboard xpilots > fortune gnushogi xasteroids xshogi > game gnushogirxbattle xsok > gnuangnushogixxboard xtet42 > gnuchess kill-acmsxinvadersxtron > (mark, destiny)$ dpkg -l *tex* > 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=ba d) > ||/ NameVersionDescription > +++-===-==-== == > un X11-text-viewer (no description available) > pn amslatex (no description available) > pn amstex (no description available) > pn auctex (no description available) > pn bibtex (no description available) > pn gettext (no description available) > pn hyperlatex (no description available) > pn latex(no description available) > pn latex2e-doc (no description available) > pn latex2rtf(no description available) > ii nb-tex 2.1-1 NTeX package > ii nb-texi 2.1-1 NTeX package > ii ntex2.1-1 NTeX package > ii nx-etex 2.1-1 NTeX package > ii nx-mtex 2.1-1 NTeX package > un tex (no description available) > pn texbin (no description available) > pn texidoc (no description available) > ii texinfo 3.7-1 The GNU Project's documentation formatting s > pn texlib (no description available) > pn texpsfnt (no description available) > pn textfm (no description available) > ii textutils 1.19-1 The GNU text file processsing utilities. > ii untex 9210-4 Remove LaTeX commands from input. > > > (Which incidently is the same as what I get when I use the quotes) > What you got was correct. Your directory listing shows no files which match *tex*. Therefore, the shell couldn't expand *tex* to anything in your directory, and therefore passed the string *tex* to dpkg, which expanded it on its own. If: -- you have a file whose name matches *tex* in the current working directory, AND if the name of that file _is not_ the name of a Debian package, then dpkg wouldn't be able to infer its status. You'd get a message "No packages found matching ." -- you have a file whose name matches *tex* in the current working directory, AND if the name of the file _is_ the name of a Debian package, then dpkg -l would be able to look up its status and report it. -- you do not have a file whose name matches *tex* in the current working directory, then the shell passes *tex* to dpkg, which expands the regexp in its administrative directories. HTH, Susan
Re: catch 22?
> >manually created the symlink Jim, THANKS! I'll give that a try.best suggestion I've heard today :-) Paul > >- Jim
Re: The "*" character (was: Latex )
Hi Mark -- You said: > in response to: > >Hi Mark -- > >You asked: > >> because I'd said: > >> >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? > > > > > >What I'd written was actually not right for either shell. > > > >I should have written: > > > > dpkg -l "*tex*" > > > >The problem is that without the quotes, the shell expands the argument > >first, before handing it to dpkg. If there's a file in your current > >directory with a name that matches *tex*, then that file, and only that > >file, is fed to dpkg. This is not what's intended of course. > > > >So I tried the correct usage (with the quotes) under tcsh and it worked > >fine. > > But the interesting thing is that dpkg -l *tex* actually _works_ when > run under bash, leading me to think that the bash shell doesn't expand > the argument first. > Are you sure you tried dpkg -l *tex* in a directory where you know there's a file whose name matches the pattern *tex*, and whose name is not that of a debian package? On my system both bash and tcsh behaved the same way. Susan
ifconfig refuses to configure loopback address
I'm trying to install Debian 1.1 and can't seem to get the loopback
device configured. At boot up the error:
SCIOADDRT: Invalid argument
appears when the /etc/init.d/network script runs. The offending line
in this script is:
route add -net 127.0.0.0
ifconfig reports (output below) that the loopback interface does not
have the inet addr that I expect it to have (nor the one that it had
under Debian 0.93R6, BTW).
Any help or pointers appreciated. Mike.
Here's the output from ifconfig:
lo Link encap:Local Loopback
inet addr:255.255.255.255 Bcast:127.255.255.255 Mask:255.0.0.0
[which used to read:
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
]
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0
TX packets:0 errors:0 dropped:0 overruns:0
eth0 Link encap:10Mbps Ethernet HWaddr 00:A0:24:0D:08:7E
inet addr:xxx.yyy.zzz.164 Bcast:xxx.yyy.zzz.191 Mask:255.255.255.192
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1074 errors:0 dropped:0 overruns:0
TX packets:135 errors:0 dropped:0 overruns:0
Interrupt:5 Base address:0x300
Here's the current /etc/init.d/network script:
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
IPADDR=xxx.yyy.zzz.164
NETMASK=255.255.255.192
NETWORK=xxx.yyy.zzz.128
BROADCAST=xxx.yyy.zzz.191
GATEWAY=xxx.yyy.zzz.129
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
route add default gw ${GATEWAY} metric 1
And, FWIW, here's the 0.93R6 /etc/init.d/network:
#! /bin/sh
# network: establish the network connection.
# $Id: network,v 1.1 1995/02/19 20:29:29 imurdock Exp $
# Configure the loopback device.
ifconfig lo 127.0.0.1
route add 127.0.0.1
# Configure the ethernet device or start SLIP/PPP below.
IPADDR="xxx.yyy.zzz.164"# Your IP address.
NETMASK="255.255.255.192" # Your netmask.
NETWORK="xxx.yyy.zzz.128" # Your network address.
BROADCAST="xxx.yyy.zzz.191" # Your broadcast address (blank if none).
GATEWAY="xxx.yyy.zzz.129" # Your gateway address.
/sbin/ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
/sbin/route add -net ${NETWORK}
/sbin/route add default gw ${GATEWAY} metric 1
Re: Compose characters in X
> Yves Arrouye writes: Yves> If only Motif would get these keys too, and differentiate Yves> between backspace and delete, I'd be really happy. I think Motif uses a way that involves the Multi_key keysym. Assign this keysym to some key and see if you can use it as a Compose key for Motif programs. (For me, Multi_key worked just fine for Emacs, too. On a SPARC Solaris 2.5 machine, though.) kai -- What's a signature?
Re: IP forwarding and/or Masquerading
> James D LaPlaine writes: Jamie> I'm still struggling to get my PPP connection working Jamie> properly. Although the chat script is making the connection, Jamie> I can;t send any packets to any machine other than the one I Jamie> am dailing in on. Even then it only works a little, I can't Jamie> even ping that machine (or myself, whether I have ppp running Jamie> or not.) 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 Substitute the right device for ippp0 -- I'm using ISDN. You probably want modem or cua0 or ttyS0 or something, which ever device you have specified in /etc/ppp/options. kai -- What's a signature?
Re: Compose characters in X
> Yves Arrouye writes:
Yves> - one user under VIP couldn't search because / is a prefix
Yves> key too :-(
Look at the function iso-accents-customize. Here's what I set up for
German:
; put this in site-start.el or in .emacs
(eval-after-load
"iso-acc"
'(progn
(setq iso-languages
(cons '("german" (?\" (?A . ?Ä) (?O . ?Ö) (?U . ?Ü)
(?a . ?ä) (?o . ?ö) (?u . ?ü)
(?s . ?ß) (?< . ?«) (?> . ?»)))
iso-languages))
(iso-accents-customize "german")))
But I think the default value of iso-languages has a value for french,
just German was missing -- let this be for the benefit of the German
readers of this mailing list...
kai
--
What's a signature?
special-kernels
I recently posted a problem I was having installing a "special-kernel" with the boot disk during the installation procedure. Gilbert Ramirez responded indicating he had the same problem (error in format archive) with these kernels, and the culpret was the "modules.tgz" file on the boot disk. It is corrupt. I can verify that. I needed to do what Gilbert did, and that was to gunzip, un-tar, re-tar, and re-gzip the file, and put it back on the boot disk. The install went fine after that. (I did remove a module or two I wouldn't need to be sure it would fit back on the floppy). Of course if your computer is in the state of installing debian, you won't be able to do these things on THAT machine, and if you don't have a spare linux/unix computer, your ingenuity skills will be challenged. You can test the modules.tgz file on the boot disk by doing a "tar -tzvf /modules.tgz" looking for an "unexpected EOF" error message at the end of the tar list. Steve Millard Harrisburg, Pa. USA - - - - - - - - - - - - - - - - - - - - - - - It ain't what you don't know that hurts you, but what you do know that just ain't so. - - - - - - - - - - - - - - - - - - - - - - -
