Re: Mathematica [was What is the typical response from i-Connect?]
On 10 Mar 1997, Norris Preyer wrote: [EMAIL PROTECTED] (John Zachary) writes: Also, has anyone experience with Mathematica 3.0 on Debian? I called and chatted to a nice lady at Wolfram who told me that as long as a.out and ELF binaries are supported, Mathematica plays nice with Linux. However, you never know if there are other 'gotchas' lurking underneath the surface. John I don't know what the bit about a.out is about, for file reports: Mathematica: ELF 32-bit LSB executable, Intel 386, version 1, stripped Version 3.0 is *very* nice, with the entire 1400 page book available via on-line help, along with classy typography. It also takes 116Mb for a full install, as well as Motif (I don't know if lesstif would work). It seems very fast and stable---Wolfram Research took the time to do this right. I have Mathematica 3.0 installed, and it didn't require motif. The 3.0 version is very nice My alternative was mathematica for win95, and the win95 version was very slow compared to the linux version. I've not yet experimented with notebook--html pages and the like, but there's lots of fun stuff to explore. Is there a Linux (or Debian) Mathematica group?? --Norris -- Norris Preyer (541) 962-3310 (office) Physics Program (541) 962-3873 (fax) Eastern Oregon State College [EMAIL PROTECTED] La Grande, OR 97850 http://140.211.64.20/npreyer.html Scott Stanley Applied Mechanics and Engineering Sciences Dept. University of California, San Diego La Jolla, CA 92093-0411 [EMAIL PROTECTED]
Re: Idea for the burner
On Thu, 6 Mar 1997, William Chow wrote: On Fri, 7 Mar 1997, J.P.D. Kooij wrote: Like, dselect is a great and easy tool, but there is no manpage for it... Dselect is pretty intuitive once you get the hang of it, but it needs to be a bit better before I call it a great and easy tool. There were a couple of times that dselect purged things I didn't want to, because I didn't go through the whole list and checked everything, etc. I think dselect needs to be layed out better, but to tell you the truth, I have no idea how to represent that amount of information in an easy to read format. The current system is workable, but I don't believe it necessarily is ideal. This is probably due to the side effect of having a LOT of packages in the Debian system. While it may be a headache to run dselect and go through all those packages, I guess it's better than having very few packages... I will say that I really like dselect. I have never felt the need to sort through how to use dpkg since I use dselect for all of my package installation and removal. However, I think dselect could benefit alot from an option that will allow you to display the changes which are selected before you actually jump in and do them. I to have had dselect either install or remove packages that I didn't intend (no doubt because I made some stupid slip of the fingers). But, in any case, it might be nice to preview what is going to be done before actually doing it. There are far to many packages to be able to confidently go through the selection process and know exactly what is going to be done. It would be tragic to accidently purge the x-windows configuration files or something like that. Also, I think it would be better to drop info (sorry, you die-hards GNUdes out there.) Lets have all the info stuff as lynx-enabled HTML, it provides I believe you can have the best of both possible worlds with convertors. That way you can have HTML/postscript/texinfo/whatever sources of essentially the same document. Not everyone will have lynx, and not everyone will use texinfo, etc. I hate to step on any toes here, but we certainly need something in addition to info. I understand that emacs does a nice job with these files, but I have never felt like I had the system resources to spend on emacs, and I have never had the stamina to work through info. Two things that I think might be nice in the ``getting started'' type documentation for Debian would be more information on using dselect, and a section on other places to look for documentation. I just skimmed back through the documentation used for my Debian install last fall (I am a convert from slackware) and I find no mention of the /usr/doc directory, info (for what it is worth), the basic Linux HowTo's, or even man pages. The man pages, while obvious to those who have used u*ix for a while may are not so obvious to a newbie or even someone who has used u*ix for a while as a general user. Seems like a mention of all of the available documentation (web address included) would be nice to put out there. It might help get people started on solving their problems. Scott
Re: Module Errors!!
On Thu, 6 Mar 1997, Kael Rowan - CPTS666 wrote: I just installed a fresh version of Debian 1.2 on my Pentium 166 with hardly any modifications to the recommended setup in dselect, (except I chose to install the kernel source), and I just recompiled the kernel using it's default options almost exactly (except no SCSI support, etc), and keep getting these messages: Running /etc/init.d/boot... Activating swap... Checking root file system... Parallelizing fsck version 1.06 (7-Oct-96) /dev/hda2: clean, 15323/104040 files, 147108/415296 blocks Loading modules: vfat Initialization of vfat failed psaux kill_fasync: wrong version or undefined Loading failed! The module symbols (from linux-2.0.27) don't match your linux-2.0.27 serial Serial driver version 4.13 with no serial options enabled tty00 at 0x03f8 (irq = 4) is a 16550A tty01 at 0x02f8 (irq = 3) is a 16550A 3c59x ether_setup: wrong version or undefined register_netdev: wrong version or undefined dev_kfree_skb: wrong version or undefined dev_alloc_skb: wrong version or undefined eth_type_trans: wrong version or undefined netif_rx: wrong version or undefined unregister_netdev: wrong version or undefined Loading failed! The module symbols (from linux-2.0.27) don't match your linux-2.0.27 I got those wrong version or undefined errors on another system as well so I just ended up removing all the lines in all my startup scripts that had the word module in them :) What do I do??? I assume in the compilation of the kernel you did basically the following steps, make config make dep make clean make zImage or make zlilo followed by make modules make modules_install /sbin/depmod -a You must make sure and complete the process by recompiling and installing the modules. The depmod command at the end creates the dependencies file at /lib/modules/Kernel_Version/modules.dep The depmod should be run automatically by one of the startup scripts. But nice to do it by hand A better explanation of this is given in the file /usr/src/kernel-source-2.0.27/Documentation/modules.txt Scott
Re: now what
On Fri, 7 Mar 1997, MR DAVID C STEIN wrote: So I downloaded my debian base sysetem now what do I do?? Where do I go??? Is xwindows the next thing I need?? This will depend on what you want to do and what do you want your machine to be able to do?? The most obvious options are setting up the modem, printing, and x-windows. Also someone showed me how to mount a floppy disk mount -t msdos /dev/fd0 /floppy How do I unmount it umount /floppy Check out the man page for mount, umount and fstab. Where is a file that shows me basic unix commands to type at the propmt? This one you will probably want to get a basic unix book that goes over these commands. There are alot of good books out there. But, the most absolutely basic commands are, unix | Dos equivalent --- ls | dir rm | del cp | copy mv | rename There are a great deal of options available for these commands, and a look through the man pages for them would be worth while. Try man ls for instance. prefereably in ascii sice my modem is on my dos machine and I haven't figured what to do with tar.gz etc.. yet pkunzip doesn't know what to do with that in dos The .gz files are compressed using gzip. Check out the commands gzip and gunzip. Also the tar command to extract the files from the .tar file that results from gunzip AAA.tar.gz. A command like tar -xvf File_Name.tar will extract the files from a tar archive. Thanks for the info. This should give you a start. Check out the man pages for these commands. At the bottom of a man page there is a list of other related commands, for instance man mount has at the bottom; . . . FILES /etc/fstab file system table /etc/mtab table of mounted file systems /etc/mtab~ lock file /etc/mtab.tmp temporary file SEE ALSO mount(2), umount(2), fstab(5), umount(8), swapon(8), nfs(5), mountd(8), nfsd(8), mke2fs(8), tune2fs(8), los- etup(8) This will help you figure out the files and commands that are related. Have fun. Scott Stanley Applied Mechanics and Engineering Sciences Dept. University of California, San Diego La Jolla, CA 92093-0411 [EMAIL PROTECTED]
Re: running script files.
On Thu, 7 Feb 2036, A. M. Varon wrote: Hi to all, It seems that shell scripts i have made in my debian distrib. doesn't run. you need to put ./ in front in order for it to execute. i have chmod the script it to be executable, my bash shell is in /etc/shells, and my first line in my shell script is #!/bin/bash. what seems to be the problem? lshell? Thanks in advance, andre The problem isn't in your scripts at all. It is in the path set up for your shell. Once you log in, type the command ``set''. This will list a number of lines of variables that are defined for your login shell. One will look like, path(/home/sstanley/bin /usr/local/bin /usr/bin /bin /usr/bin/X11 /usr/sbin . /sbin) or like PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11 depending on whether you use tcsh or bash for your login shell. In any case, this is the list of directories that are searched when you type a command. The thing to notice is that you need the ``.'' in the path for it to find commands in the current directory (as in the first example above). Otherwise, you have to type ./Command_Name to specify explicitly where the command is. This can be set by editing the .tcshrc (if you use tcsh) or .bash_profile (for bash) files in your root directory to add ``.'' to your path. There is likely a ``set path= ...)'' command already in this file. Just edit it to add ``.''. Once the file is changed, log out and then log back in. Everything should work fine then If this is not relatively clear, send me email Scott
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] |
Re: x windows
On Sat, 1 Mar 1997 [EMAIL PROTECTED] wrote: Hello, well i got 1.2.2 installed and i was wondering about x windows, could anyone tell me how much disk space i will need to run this. i have an old 386 with 4m ran and 20mb of swap space. When I first installed X on my machine, I only had 8mb of ram. I discovered that when I was running X, I was paging continuously. I don't know if there is any official recommendation, but I am afraid the 4mb of ram isn't going to be enough. I have heard of a ``small'' implementation of X, which if memory serves used less disk space and memory. Unfortunatly I don't know much about it Hopefully someone else might. Scott looking forward to hearing from you. allan - Name: Allan W. Bart, Jr. E-mail: [EMAIL PROTECTED] Date: 3/1/97 Time: 1:26:20 PM This message was sent by Chameleon -
Re: lprm says Permission denied (fwd)
On Sat, 1 Mar 1997, John Goerzen wrote: This is *not* an acceptable fix. Other packages, for isntance Samba, will **NOT** work with lprng. This is nice to know Sounds like the thing to do is work on lpr to get it working. Besides, I am running into as many problems getting lprng to work as I was lpr. But, I think the lpr problems might be easier to track down 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. Scott On Wed, 26 Feb 1997 [EMAIL PROTECTED] wrote: Much Deleted. The real fix seems to go to lprng. That's the official position of the maintainer as well, as stated in a msg. to this list last year. I'll do it as soon as I have a chance. If the recommended fix (by the package maintainer even) is to switch from lpr to lprng, shouldn't lpr be switched out of Standard and lprng moved from Optional into Standard? I just happen to be having some problems setting up lpr as well. I think I'll switch to lprng before spending any more time. Scott Carlos -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] |
Mail list problems??
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
Re: dselect and lprng...
On Thu, 27 Feb 1997, Bob Clark wrote: Scott, The message Nothing to get simply means that dselect found the package already on your system. Go ahead and install and it should work. Then you'll be give the option to delete the package file. --Bob Oddly enough, I have never looked at lprng before, so there is no way it found it on my system. When I complete the install process, it still says I want to install it, but that it isn't installed. It is almost as if dselect does not recognize that I want to install the package, so it does not hunt for it on the FTP site. Scott Scott Stanley wrote: I was just trying to download and install the lprng package from stable using dselect 1.4.0.7 with the ftp Access method. Basically, I went into Select, and selected the package lprng (I got the dependencies window saying lprng recommended magicfilter, but I did not select magicfilter). The select menu item for lprng looks like; _* Opt net lprng none2.4.2-1 lpr/lpd printer spooling When I exit (pressing Enter) and Install, I get -- Processing status file... Processing Package files... stable... contrib... non-free... Constructing list of files to get... Approximate total space required: 0k Available space in ../../../../../dosc/Debian/1.2: 235632k Nothing to get. Processing downloaded files...(for corrupt/old/partial) Nothing to get??? If I go back into the Select option after this aborted attempt, it still says I want to install lprng, just like is shown above. Seems like I must be doing something silly, I just can't figure out what Any help is appreciated. Scott
Re: dselect and lprng...
On Fri, 28 Feb 1997, David Wright wrote: (I'm the person who suggested running update in dselect.) I couldn't find lprng at ftp.mcc.ac.uk so I went to ftp.debian.org and it wasn't there either, except in bo. So it's a mystery to me whence came Opt net lprng none 2.4.2-1, but no surprise that dselect couldn't download it. Thanks... I'll get it from bo. Why didn't I think of just looking for it?? Scott -- David Wright, Open University, Earth Science Department, Milton Keynes MK7 6AA U.K. email: [EMAIL PROTECTED] tel: +44 1908 653 739 fax: +44 1908 655 151
Re: Package configuration philosophy
On Thu, 27 Feb 1997, Craig Sanders wrote: On Wed, 26 Feb 1997, Yoav Cohen-Sivan wrote: Debian comes up in a much rawer form after install - for instance, no prompt beyond the basic # for root and $ for the user (RedHat gives you the now famous username /home/username$ prompt). # and $ are standard/expected prompts. if you want something different, customise it yourself. I think you are missing my point. I'm not just talking about the prompt or X11 or any other specific package, but the whole shabam. No, i'm not missing your point at all. I just happen to disagree with it. One of the things I *like* about debian is that it doesn't inflict anyone else's aesthetic tastes on me. I don't have to edit a lot of configuration files to undo some hideously garish display - it's plain and simple and I can uglify/prettify it according to my own personal (bad) taste rather than someone else's. I agree entirely with this. What might be nice is if there were mini howtos available on setting up some of the possible options. Say for instance color in an xterm. I have seen alot of traffic about this one (which I save for when I might actually get around to trying to set this up). Another example would be changing the prompt. Not everyone who installs Debian as a newbie knows how to do these things, and quite often what seems straight forward to the experienced *nix users is only that straight forward due to years of experience I am sure the required information is in the man pages, but sometimes you just don't know where to look. Unfortunately, this type of documentation generally doesn't sound like much fun to create (as if any type of documentation was ``fun'' to create). Scott -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Package configuration philosophy
On Wed, 26 Feb 1997, Jason Gunthorpe wrote: On Thu, 27 Feb 1997, Craig Sanders wrote: On Wed, 26 Feb 1997, [iso-8859-1] Nicolás Lichtmaier wrote: If someone is going to evaluate an entire distribution on a prompt (even if there are other factors), I'm not going to be upset if they don't choose Debian. I'm no talking about just the prompt. We're talking about good and comfortable defaults, default settings should be like suggestions of how things can be done. Good defaults is very important in a distribution, IMHO. IMO, debian HAS good defaults. clean simple without a lot of stuff to undo when you want to customise it to YOUR preferred settings. Making default settings too pretty/complex tends to stifle both learning creativity...instead of just one thing to learn/change at a time, you have to undo a lot of changes (or at least learn what they do) or risk breaking a working setup. I wonder if it would be possible to make a package that included a good degree of the typical customizations? I have setup 3 debian machines right from the ftp server in the past month and there are things I change right off the bat, the prompt is one, the .inputrc (to include home/end keys) some of the aliases, enable color ls etc The problem with this is that the defaults the package developer likes are unlikely to conform to the particular taste of every user. This sounds like a good option for an individual to create for their particular needs. Might be a neat idea... It would certainly speed the process up when doing installations on multiple machines. Stifling learning is one thing, but having to do the same setup again and again is pain -- which is why I wonder if a package could be made? Jason -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Package configuration philosophy
On Wed, 26 Feb 1997, Jason Gunthorpe wrote: On Wed, 26 Feb 1997, Scott Stanley wrote: On Wed, 26 Feb 1997, Jason Gunthorpe wrote: On Thu, 27 Feb 1997, Craig Sanders wrote: I wonder if it would be possible to make a package that included a good degree of the typical customizations? I have setup 3 debian machines right from the ftp server in the past month and there are things I change right off the bat, the prompt is one, the .inputrc (to include home/end keys) some of the aliases, enable color ls etc The problem with this is that the defaults the package developer likes are unlikely to conform to the particular taste of every user. This sounds like a good option for an individual to create for their particular needs. Might be a neat idea... It would certainly speed the process up when doing installations on multiple machines. This is true, but the installation of the package is up to the Debian user, it's not forced, there could even be multiple conflicting packages with conflicting UI styles : Encourage a 'learn by example' type of approach. Several conflicting packages might work... But it is easy to install a package and still not learn anything about how these defaults are actually set up (or what files were even added to the system for that matter.) This would significantly speed up setting up a system, but will only promote learning if the changes are brought to the installers attention. If an explanation of how the defaults were set was placed in /usr/doc as part of the package, this might be work (I am sure there is a good way to find out what files are included in a package without this documentation, but that brings another variable into the learning curve) Scott -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
G77 in stable
Does anyone know the status of the package g77_0.5.19-2 I just tried to download this package from stable at ftp.debian.org, and got a message saying the file was not there. Debian-1.2-fixed/binary-i386/devel/g77_0.5.19-2.deb: No such file OR directory. It does show up in the list of packages available in stable, however. Scott Stanley [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Cant get kernel-package!
On Tue, 21 Jan 1997, Kendrick Myatt wrote: when I use dselect to try and get kernel-package, i get into an infinite loop with dependencies on packages perl and libc5. I + them and they get *, but when I enter, I go back to dependencies and there they are again, still showing *! I X'd back and tried again from start, chose ftp, looked at packages, kernel-package was STILL selected, and I STILL got into the same boat when i tried to continue. Trying to purge those two packages was the bright idea I had, but I soon realized I would have to remove most of my system once the dependencies were ruled out :( I'm trying again to see if I can get kernel-package and it's 3 dependencies (the source and that other thing...) then I Q'd on the perl... *sigh* Now it's downloading all kinds of packages I didn't ask for, cron3.0, perl5.003, dpkg1.4, etc... I know it is probably just that I was not used to dselect, but I have had this type thing happen quite a bit myself. Would it make sense to add an option to dselect which allows you to list out all of the pending installations/removals of packages before actually going through the process. I don't have this happen as much anymore, but I sure did in the beginning... Scott S. What did I screw up, and is there some way to globally reset dselect, as I believe I have done something to really confuse it :( Thanks for any help.. I'll keep working on this end :) Regards, Kendrick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: problem with installation
I am in the middle of an upgrade from Debian 1.1 to 1.2 right now and ran into the same problem. Download the libc5 from the unstable directory. It seems that a few packages got into stable when the libc5 they needed wasn't. An easy fix though Oh, if you need/want the libc5-devel package, you'll need to get it from unstable as well. Scott Stanley -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
