Re[2]: HELP: problems compiling wine
Thanks to Oliver [EMAIL PROTECTED] and Will [EMAIL PROTECTED] for their prompt answer. Appending `-L /usr/X11R6/lib' to the command line made it. I have wine (version 960824) installed on my box. I tried it with MS-Word 6.0c, MS-Excel and Matlab 4.2c (all 16bit applications) and they run to my satisfaction. I have not tested them thorougly but I am quite impressed already. I think that if we (debian-users) could test and report bugs to the developers this piece of software would soon be very very usable. Thanks again for this wonderful system to the Debian developers! Lazaro -- Lazaro D. Salem E-mail: [EMAIL PROTECTED] RF-Rogaland Research Phone: +47 51 87 50 00 P.O.Box 2503, Ullandhaug Direct: +47 51 87 50 65 N-4004 Stavanger, NORWAY Fax: +47 51 87 52 00 __ Reply Separator _ Subject: Re: HELP: problems compiling wine Author: olly@lfix.co.uk at RF Date:17.09.97 12:51 In message [EMAIL PROTECTED], writes: gcc -o wine controls/controls.o files/files.o graphics/graphics.o graphics/metafiledrv/metafiledrv.o graphics/x11drv/x11drv.o ipc/ipc.o loader/loader.o memory/memory.o misc/misc.o msdos/msdos.o multimedia/multimedia.o objects/objects.o resources/resources.o scheduler/scheduler.o win32/win32.o windows/windows.o debugger/debugger.o graphics/win16drv/win16drv.o if1632/if1632.o miscemu/miscemu.o -lXpm -lXext -lX11 -lm ld: cannot open -lXpm: No such file or directory make: *** [wine] Error 1 However libXpm is on the system. Try adding `-L /usr/X11R6/lib' to the command line, so that gcc knows where to look for libXpm. I think that, by default, it only looks in /lib and in /usr/lib. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://lfix.co.uk/oliver PGP key from public servers; key ID 32B8FAA1 Make it idiot-proof, and someone will breed a better idiot. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re[2]: HELP: problems compiling wine
After my post about my wine experience, Brian commented: Subject: Re: HELP: problems compiling wine Author: [EMAIL PROTECTED] at RF Date:18.09.97 10:54 I tried it with MS-Word 6.0c, MS-Excel and Matlab 4.2c (all 16bit applications) and they run to my satisfaction. I have not tested them thorougly but I am quite impressed already. You got Word-6 to run under it? Wow! I never been able to get it to run ever under the 9708xx versions. Excel runs pretty well, though it does crash occasionally. Brian ( [EMAIL PROTECTED] ) -- -- Generated by Signify v1.02. For this and more, visit http://www.verisim.com/ Yes. Word 6.0c runs with wine version 970824. However in a post to the newsgroup somebody reported that in the last wine realease (of 970914?) MS-Word 6.0c is broken. I am running Debian 1.3.1 (as of end of August 29 + a few upgrades from bo-updates), on my old good i486/33MHz with 16 MB RAM and 16 MB swap partition. The load is about 1 when running Wine + Word and Matlab and appbar (a task bar a la NextStep for MS-Win 3.11). I got some messages which I could not dechipher yet. Wine is slow to load but I don't perceive it a slow when writing documents. I haven't tested raw speed of other programs like for example Matlab 4.2c but graphics on the last were fast enough for me. The color/font configuration needs probably to be tuned. I haven't read the documentation yet. (I am in moving period so I have no much time right now). As it had happened with Debian GNU/Linux, _it_would _really_boost_ _wine_development if many people in this list give it a try ... AND report bugs. Well...that's just my humble opinion. Thanks, Lazaro -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: bug ?: Disappearing DOS partitions
If you haven't fixed your problem, I can help you. Just send us what your able to see from DOS (with DOS FDISK) and/or from linux with cfdisk and with fdisk if you have it on your system (they do not present the same information as far as I remember). Just a comment to what Bruce said: I think DOS cares which partition is the extended one. I think it wants it to be partition 4, but I'm not sure I remember that correctly. I don't think that's true. Maybe MS-DOS FDISK cares about that but not MS-DOS. I mean, I have tried and used many different configurations of extended partition where the extended partition has been the 1 the 2 or whatever you want. Comment: in fact we should be more specific as what's the meaning of 1st, 2nd. as you could write the information about the 2nd partition (not starting at the first cyilinder) in the 1st line of your partition table. IN any case I thing there is no such a limitation from the MS-DOS side. What MS-DOS FDISK cannot handle is to create more than one FAT _primary_ partitions. If one already exists then it allows you to create an extended one only. There is however an old good DOS application which is more flexible than MS FDISK and has been long used by the BSD people. Its name is PFDISK and can be found (both source and DOS binary) in for example NetBSD ftp under the tools tree (check out www.NetBSD.org). PFDISK would also allow you to modify (save first a copy of your PT from within PFDISK writing to a file in the DOS partition) the master partition table. This master partition table contains info of only 4 partitions and it is located at the beginning of your HD. I can help you with more details if you need. FYI, I also had several primary DOS partitions. MS-DOS sees them all. I've done it on my system with both versions 5.0 and 6.x of MS-DOS. If your unseable DOS partitions were primary (just check what cfdisk sees as DOS partitions: if they are on /dev/?daN with ? = s or h and N 4, then they were logical partitions in the extended partition; else if N5 they were primary partitions and (forget FDISK) you could recover them with DOS PFDISK and the info you got from linux cfdisk/fdisk (I can help you if you need it). Hope this helps and that it is not too late. Lazaro -- Lazaro D. Salem E-mail: [EMAIL PROTECTED] RF-Rogaland Research Phone: +47 51 87 50 00 P.O.Box 2503, Ullandhaug Direct: +47 51 87 50 65 N-4004 Stavanger, NORWAY Fax: +47 51 87 52 00 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
HELP: problems compiling wine
Hi, I would appreciate any hint to work around this error I get when trying to compile wine (970828). configure and make depend worked ok, but when trying: mafalda# make [snip...] make[1]: Leaving directory `/usr/src/wine970824/miscemu' gcc -o wine controls/controls.o files/files.o graphics/graphics.o graphics/metafiledrv/metafiledrv.o graphics/x11drv/x11drv.o ipc/ipc.o loader/loader.o memory/memory.o misc/misc.o msdos/msdos.o multimedia/multimedia.o objects/objects.o resources/resources.o scheduler/scheduler.o win32/win32.o windows/windows.o debugger/debugger.o graphics/win16drv/win16drv.o if1632/if1632.o miscemu/miscemu.o -lXpm -lXext -lX11 -lm ld: cannot open -lXpm: No such file or directory make: *** [wine] Error 1 However libXpm is on the system. Here is a complete listing of the libraries under X11R6: mafalda# ls -l total 5395 drwxr-xr-x 6 root root 2048 Sep 16 06:15 . drwxr-xr-x 7 root root 1024 Sep 12 00:28 .. -r--r--r-- 1 root root 703 Apr 29 20:56 .text_extras_menu -r--r--r-- 1 root root 2409 Apr 29 20:56 .textswrc -r--r--r-- 1 root root 444 Apr 29 20:56 .ttyswrc drwxr-xr-x 19 root root 1024 Sep 15 23:28 X11 drwxr-xr-x 2 root root 1024 Sep 12 00:29 Xaw95 drwxr-xr-x 2 root root 1024 Sep 12 00:29 help -rw-r--r-- 1 root root65592 Jun 20 16:49 libFS.a lrwxrwxrwx 1 root root 13 Sep 15 23:28 libICE.so - libICE.so.6.3 lrwxrwxrwx 1 root root 13 Sep 6 17:52 libICE.so.6 - libICE.so.6.3 -rwxr-xr-x 1 root root74656 Jun 20 16:52 libICE.so.6.3 lrwxrwxrwx 1 root root 14 Sep 12 00:26 libMrm.so.0 - libMrm.so.0.76 -rw-r--r-- 1 root root58928 Feb 7 1997 libMrm.so.0.76 lrwxrwxrwx 1 root root 14 Sep 15 23:28 libPEX5.so - libPEX5.so.6.0 lrwxrwxrwx 1 root root 14 Sep 6 17:47 libPEX5.so.6 - libPEX5.so.6.0 -rwxr-xr-x 1 root root 233456 Jun 20 16:52 libPEX5.so.6.0 lrwxrwxrwx 1 root root 12 Sep 15 23:28 libSM.so - libSM.so.6.0 lrwxrwxrwx 1 root root 12 Sep 6 17:47 libSM.so.6 - libSM.so.6.0 -rwxr-xr-x 1 root root30580 Jun 20 16:52 libSM.so.6.0 lrwxrwxrwx 1 root root 13 Sep 15 23:28 libX11.so - libX11.so.6.1 lrwxrwxrwx 1 root root 13 Sep 6 17:47 libX11.so.6 - libX11.so.6.1 -rwxr-xr-x 1 root root 657676 Jun 20 16:52 libX11.so.6.1 lrwxrwxrwx 1 root root 13 Sep 15 23:28 libXIE.so - libXIE.so.6.0 lrwxrwxrwx 1 root root 13 Sep 6 17:47 libXIE.so.6 - libXIE.so.6.0 -rwxr-xr-x 1 root root40836 Jun 20 16:52 libXIE.so.6.0 -rw-r--r-- 1 root root11440 Jun 20 16:49 libXau.a lrwxrwxrwx 1 root root 13 Sep 15 23:28 libXaw.so - libXaw.so.6.1 lrwxrwxrwx 1 root root 13 Sep 6 17:47 libXaw.so.6 - libXaw.so.6.1 -rwxr-xr-x 1 root root 223112 Jun 20 16:52 libXaw.so.6.1 -rw-r--r-- 1 root root 355432 Feb 13 1997 libXaw95.a lrwxrwxrwx 1 root root 15 Sep 12 00:29 libXaw95.so - libXaw95.so.6.1 lrwxrwxrwx 1 root root 15 Sep 12 00:29 libXaw95.so.6 - libXaw95.so.6.1 -rwxr-xr-x 1 root root 273096 Feb 13 1997 libXaw95.so.6.1 -rw-r--r-- 1 root root37174 Jun 20 16:49 libXdmcp.a -rw-r--r-- 1 root root 3906 Jun 20 16:49 libXdpms.a lrwxrwxrwx 1 root root 14 Sep 15 23:28 libXext.so - libXext.so.6.3 lrwxrwxrwx 1 root root 14 Sep 6 17:52 libXext.so.6 - libXext.so.6.3 -rwxr-xr-x 1 root root38632 Jun 20 16:52 libXext.so.6.3 lrwxrwxrwx 1 root root 12 Sep 15 23:28 libXi.so - libXi.so.6.0 lrwxrwxrwx 1 root root 12 Sep 6 17:47 libXi.so.6 - libXi.so.6.0 -rwxr-xr-x 1 root root26080 Jun 20 16:52 libXi.so.6.0 lrwxrwxrwx 1 root root 13 Sep 12 00:26 libXm.so.0 - libXm.so.0.76 -rw-r--r-- 1 root root 850432 Feb 7 1997 libXm.so.0.76 lrwxrwxrwx 1 root root 13 Sep 15 23:28 libXmu.so - libXmu.so.6.0 lrwxrwxrwx 1 root root 13 Sep 6 17:47 libXmu.so.6 - libXmu.so.6.0 -rwxr-xr-x 1 root root67856 Jun 20 16:52 libXmu.so.6.0 lrwxrwxrwx 1 root root 12 Sep 15 23:28 libXp.so - libXp.so.6.2 lrwxrwxrwx 1 root root 12 Sep 6 17:52 libXp.so.6 - libXp.so.6.2 -rwxr-xr-x 1 root root22748 Jun 20 16:52 libXp.so.6.2 -rw-r--r-- 1 root root73798 Feb 3 1997 libXpm.a lrwxrwxrwx 1 root root 13 Sep 16 06:15 libXpm.so - libXpm.so.4.7 lrwxrwxrwx 1 root root 13 Sep 8 23:59 libXpm.so.4 - libXpm.so.4.7 -rwxr-xr-x 1 root root48772 Feb 3 1997 libXpm.so.4.7 -rw-r--r-- 1 root root 5220 Jun 20 16:49 libXss.a lrwxrwxrwx 1 root root 12 Sep 15 23:28 libXt.so - libXt.so.6.0
Support for the 3Com 3C900 (Etherlink PCI) network card?
It seems there is no module support for the 3Com 3C900 Etherlink PCI card in the standard kernel (version 2.0.x). However I found there are some updated source code and a compiled module in: http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html Has anybody tried the compiled module? Will it work with on a debian system running 2.0.27 or 2.0.29 ? or...? (I remeber reading something about the header in debian were the last stable ones instead of the latest found in the original kernel source). Any comment from those who had experience with this cards will be appreciated. Thanks. -- Lazaro D. Salem E-mail: [EMAIL PROTECTED] RF-Rogaland Research Phone: +47 51 87 50 00 P.O.Box 2503, Ullandhaug Direct: +47 51 87 50 65 N-4004 Stavanger, NORWAY Fax: +47 51 87 52 00 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
help: lost network connection after upgrading 1.1 to 1.2
Hi, After upgrading from Debian 1.1 to 1.2 I lost my network connection. I must confess it was not a clean upgrade in the sense that i had to dpkg -i and dpkg -r a few times netbase (now 2.0.9-1)and netstd (now 2.12-1). I thought I just upgraded witohout modifying the configuration files but I may (must) be wrong. Here the simptopms 1) At boot time and after the message: starting /usr/sbin/sendmail the machine seems like sleeping for 2-3 minutes. Something similar when halting/rebooting it. I guess that It cannot resolve IP addresses, since when I try: # telnet localhost localhost: Host name lookup failure # 2) My /etc.hostname, /etc/init.d/networks, hosts.allows and hosts.deny seem to be ok (as before when everything worked). I think my /etc/hosts.conf is also correct: --- order hosts, bind multin on --- 3) I also noticed that , for example when telnet localhost I get some errors: eth0 transmit timed out, status 0073, resetting. ring data dump: dirty_tx 0 cur_tx 16 (full) cur_rx 0. Can be this message be related to the name resolution described above? --- The output below might be useful for you to help me: # route Kernel IP routing table DestinationGateway Genmask Flags Metric Ref Use Iface localnet * 255.255.0.0 U 0 0 1 eth0 127.0.0.0 * 255.0.0.0U 0 0 2 lo defaultcisco.rf.no 0.0.0.0 UG1 0 0 eth0 # ifconfig loLink encap:Local Loopback 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: 136 errors:0 dropped:0 overruns:0 TX packets: 136 errors:0 dropped:0 overruns:0 loLink encap:10Mbps Ethernet HWaddr 00:80:5F:6C:6A:99 inet addr:138.37.67.79 Bcast:138.37.255.255 Mask 255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets: 0 errors:0 droppped:0 overruns:0 TX packets: 0 errors:3 dropped:0 overruns:0 Interrupt:11 Base address:0x1000 DMA chan:4 -- What else should I check to fix my network connection? Thanks for any help/pointer. Lazaro -- Lazaro D. Salem E-mail: [EMAIL PROTECTED] RF-Rogaland Research Phone: +47 51 87 50 00 P.O.Box 2503, Ullandhaug Direct: +47 51 87 50 65 N-4004 Stavanger, NORWAY Fax: +47 51 87 52 00 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Links to package's bugs on the package web-page
Hi It would be nice to see links to the Bug Tracking System (BTS) from the web pages the individual packages can be downloaded on www.debian.org. Those interested in upgrading individual packages would so be able to check the reported bugs before starting the process which might break their working systems. By the way, I was just curious about the way NetBSD implements their BTS (they use GNATS). For those interested, have a look at http://www.netbsd.org/Misc/send-pr.html. and http://www.netbsd.org/Misc/query-pr.html for query about known bugs. I think Debian would benefit from something like that Thanks, Lazaro -- Lazaro D. Salem E-mail: [EMAIL PROTECTED] RF-Rogaland Research Phone: +47 51 87 50 00 P.O.Box 2503, Ullandhaug Direct: +47 51 87 50 65 N-4004 Stavanger, NORWAY Fax: +47 51 87 52 00 Two questions: 1. What's good about GNU libc? 2. Whose libc is libc5? LIBC5 is GNU libc with substantial patches for Linux. LIBC6 is GNU libc with the Linux support merged back in to the main source thread. GNU calls these LIBC 1 and 2. We call it LIBC6 on Linux because our version numbers didn't follow the GNU ones. All Linux distributions will go to LIBC6. There are no hold-outs that I know of. Bruce Date: Mon, 7 Apr 1997 17:01:47 -0400 (EDT) From: Jean Pierre LeJacq [EMAIL PROTECTED] To: debian-user@lists.debian.org cc: debian-user@lists.debian.org Subject: Re: xemacs and emacs Message-ID: [EMAIL PROTECTED] Content-Type: TEXT/PLAIN; charset=US-ASCII I have both working fine on my system which is based on the unstable branch. Didn't have to do anything special. -- Jean Pierre On Mon, 7 Apr 1997, Steve Hsieh wrote: Can someone explain why the xemacs and emacs packages can't coexist on the same Debian system? (What would it take to make them coexist?) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: bash profile question
For the prompt, I have the following line in my ~/.bash_profile and ~/.bashrc use: export PS1=[EMAIL PROTECTED]:\w\\n[\#]\\$ which produces, for example [EMAIL PROTECTED]:~/bin [3]$ ls -laR or [EMAIL PROTECTED]:/usr/src/linux [4]# ls -laR \$ gives you a different prompt char ($ or #) when logged as a normal user or as root; \u gives the username; \h gives the hostname; \w the present working directory (with shorted $HOME, i.e., ~); \n is a carriage return which I use since I have too long pathnames so I prefer to have the prompt and history command number in the next line. The special characters (like \n and \$) require you to escape them by preppending a backslash. You'll find this and more in the bash manpage. I also used to have slightly different prompts in bash_profile and .bashrc to distinguish between login and non login sessions. lazaro. [EMAIL PROTECTED] __ Reply Separator _ Subject: bash profile question Author: debian-user@lists.debian.org at cclink Date:04.10.96 23:36 I know you can use your .bash_profile to let you see the current directory and a prompt ( like in dos or os/2 ) I do have a profile which does this but was wondering if some people could post their profiles so maybe I can choose another which I like more or something like that. Carved upon my stone, my body lie but still I roam From Metallica ( anywhere I roam ) Marcel Burggraeve ( aka Pearl_Jam on irc ) http://www.cistron.nl/~graeve -- 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[2]: Scsi errors
At 07:55 PM 9/25/96 -0500, you wrote: Are there any kernels that are known to work _for_sure_ with an AHA-1542CF?? Maybe that's my problem... Mike My 0.0001$ contribution: I've also been running Linux 1.0.9, 1.2.13 and now 2.0.6 with the AHA1542CF and only had problems when forgetting to terminate the CD-ROM at the end of the chain [is has not internal resistors :-( ]. I never had problems with the HDs at the end of the chain as they are internally terminated. In my case, the total length of the SCSI bus is slightly below 2 m. I usually have two SCSI HD disks and the CD-ROM on it. I remember several postings last year and the SCSI FAQ comp.?.hardware.scsi mentioning how sensible to termination problems the Adaptec cards were. __ Reply Separator _ Subject: Re: Scsi errors Author: debian-user@lists.debian.org at cclink Date:26.09.96 14:54 At 07:55 PM 9/25/96 -0500, you wrote: Are there any kernels that are known to work _for_sure_ with an AHA-1542CF?? Maybe that's my problem... Mike I've been running a AHA-1542CF since the 1.x kernel series with no trouble at all. I know have two systems with them in there running 2.0.15 and 1.2.10. I did have a problem before with the scsi cable which I posted to here - basically what it kept doing was writing to the hard drive in wrong places, corrupting things when accessing the cdrom I have connected. Turned out that it was the cable and I've never had any trouble since then. Perhaps it could be the hard drive, but then again, I wouldn't know about that - both my scsi disks are SCSI-2 and yours is a SCSI-3, perhaps it doesn't like them for some reason? Regards ...Karl -- Karl Ferguson, Tower Networking Pty Ltd (ACN: 072 322 760)[EMAIL PROTECTED] t/a STAR Online Services [EMAIL PROTECTED] Tel: +61-9-455-3446 Fax: +61-9-455-2776 http://www.star.net.au/
Re[4]: Am I the Only One Waiting??
On 25.09.96 04:17 Guy Maor [EMAIL PROTECTED] wrote: On Tue, 24 Sep 1996 [EMAIL PROTECTED] wrote: Therefore the newest postings archived on the server and mirrors are those of June 96. Don't hold your breath :-) Check again; they're being updated now. There's a glitch right now so that postings past about mid September aren't there, but that should be fixed very soon. Guy Something might still be wrong. As of 25-Sep-96 8:30 GMT+1, and pointing my browser to http://www.debian.org/List-Archives I find: Debian Linux mailing list archives You can subscribe or unsubcribe to these mailing lists using a form. Public mailing lists [snip] debian-changes: Package upgrades announcements June 1996 January 1996 [snip] debian-user: Help and discussion among users of Debian June 1996 May 1996 [snip] __ Reply Separator _ Subject: Re: Re[2]: Am I the Only One Waiting?? Author: debian-user@lists.debian.org at cclink Date:25.09.96 04:17 On Tue, 24 Sep 1996 [EMAIL PROTECTED] wrote: Therefore the newest postings archived on the server and mirrors are those of June 96. Don't hold your breath :-) Check again; they're being updated now. There's a glitch right now so that postings past about mid September aren't there, but that should be fixed very soon. Guy
Re[2]: Trashed disk
I you have an Adaptec card, you may want to check the disk using the utilities provided with the card to test the disk (alt-A at boot time before linux is booted). You can also check the grown defects list with the MS-Windows utilities provided with EZSCSI. Don't know if there is some linux utility providing the same functionality. good luck! lazaro [EMAIL PROTECTED] __ Reply Separator _ Subject: RE: Trashed disk Author: debian-user@lists.debian.org at cclink Date:25.09.96 08:51 From my SCSI days of long ago... I believe your disk is telling you that it tried to write to a sector = but that when it went to read it back to verify the data written was = correct, the verify failed. Typically SCSI disks will then automatically = reallocate the bad sector with some reserved sectors at the end of the = disk. To find out for sure if the disk is saying this, you would need = the tech manual for your fujitsu disk and look up the codes contained in = the sense data. If this is the case and you're consistently seeing these messages, I'd = say your disk is spiraling downward. Eventually the disk will run out of = sectors to re-map and a SCSI write will fail. If Linux does not support = its own remapping on failed writes (does anyone know if it does?) you'll = probably get a panic, your system will halt and you'll probably have a = hell of a time trying to repair the volume and remount it to back it up. Your disk could last for years to come or it could fail in minutes. My = experience with these types of failures is that they tend to spiral = relatively quickly (hours to days). I'd back up immidiately and start = shopping for SCSI hard drives (almost free these days). Al Youngwerth [EMAIL PROTECTED] -- From: Bill Wohler[SMTP:[EMAIL PROTECTED] Sent: Tuesday, September 24, 1996 1:30 AM To: [EMAIL PROTECTED] Subject:Trashed disk Folks, I've just noticed that I've been getting the following messages for the last couple of weeks. Sep 24 00:00:28 gbr kernel: scsi0: MEDIUM ERROR on channel 0, id 2, lun 0, CDB: 0x03 00 00 00 10 00=20 Sep 24 00:00:28 gbr kernel: Current error sr08:11: sns =3D f0 3 Sep 24 00:00:28 gbr kernel: ASC=3D10 ASCQ=3D 0 Sep 24 00:00:28 gbr kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x06 0xc0 0xe9 0x28 0x00 0x00 0x00 0x00 0x10 0x00 0x00 0x80=20 Sep 24 00:00:28 gbr kernel: scsidisk I/O error: dev 08:11, sector 442568 My first reaction is to toss the disk, but I thought I'd see if anyone on this list would offer that it is salvageable (and if so, what precautions would be necessary). It's an old Fujitsu that I bought used 2.5 years ago and it's been running non-stop since.
Re[6]: Am I the Only One Waiting??
'm talking about the archives on the *ftp* mirrors in /debian/debian-lists. Sorry if that was not obvious. The archives on the web site should be up before too long also. Guy Great! thanks a lot Guy. One related question: How can I add the bunch of messages to my mail box so to read them off line with say mail or exmh? I use exmh that but if with other MUA is easier for this job just let me know. And what about doing that on HPUX 9.0 at work using Softbench mail? Lazaro [EMAIL PROTECTED]
Script to produce bug reports?
Hi, I was planning to write a script to make the bug reporting process semiautomatic. With a standard form, and leaving place for an Additional comments field would be IMO a step forward for the project: Std form+Script - FastEasy to report - - Easier to read/bounce duplicates/fix === Better system However I had no time in the last weeks to produce something usable and I forgot what I have done and what I haven't. Has any one tried this idea before? Lazaro [EMAIL PROTECTED] --- P.S. I found myself many times accepting bugs just to avoid writing a bug report. My excuses are 1) I don't have an Internet connection at home where I run Debian/Linux. 2) I still have problems to make my Debian/Linux on a portable HD network/mail aware at work. That makes bug reporting not an easy task for me.
Re[2]: Filename case - the simple solution ...
somebody wrote (Sorry, I don't get always the original poster address ): Resolving the case problem can also be solved VeRy simply by typing the one magical word... case - NEXT TIME - when you do your FTP'ing don't forget to use the case statement. It may not be that simple as that. There maybe other reasons for the uppercases in filenames. I found out that some tarred files using DOS PDTAR under DOS, render uppercase filenames when untarred on Unix systems. So the other solutions posted still apply and may be handy. lazaro [EMAIL PROTECTED]
Re: special boot disks
It is true. only a brief description is given. but you may want to read the config files with which the special kernels were created. They are in the same directory as the special-kernel packages. I also remember reading some (brief) info in the FAQ (not too much) lazaro [EMAIL PROTECTED] __ Reply Separator _ Subject: special boot disks Author: debian-user@lists.debian.org at cclink Date:23.09.96 19:12 In preparing for debian 1.1 installation I find that the standard installation boot disk does not support the hardware I have. I have found a variety of special boot disks in /buzz/special-kernels, but no description of the hardware configurations each supports. Where on the debian ftp site will I find such descriptions? Thanks for any help. Richard
Re[2]: Am I the Only One Waiting??
Guy Maor writes: Date:24.09.96 08:31 On Mon, 23 Sep 1996, Paul T. McNally wrote: I've been dying to read this list in the archive version for the month of July. I know it is probably huge and I can wait, I just wanted to know about when it will be accessible via www.debian.org! Until the issue with www.debian.org is cleared up, the archives are (and will continue to be) available at any ftp mirror in /debian/debian-lists. Guy I remember a posting of the maintainer of the debian-users list archives saying he had problems to fix things up before the end of September due to lack of time. Therefore the newest postings archived on the server and mirrors are those of June 96. Don't hold your breath :-) lazaro [EMAIL PROTECTED]
Re: need help: error opening terminal con80x25 during instal
change console to linux. As you can check that is the entry in the terminfo database. I think the change occurred in the 1.3.x development stage of Linux. lazaro [EMAIL PROTECTED] __ Reply Separator _ Subject: need help: error opening terminal con80x25 during install Author: debian-user@lists.debian.org at cclink Date:23.09.96 20:58 Hi, I asked this question earlier but got no answer. Would very much like to try debian but can't run dselect. Please take a quick look... it can't be a difficult one: After having installed debian for the first time and logging in as root I got the opportunity to install packages with dselect. However, when dselect started, it gave the message: error opening terminal con80x25 and quit, leaving me with an almost empty system. The TERM variable was indeed con80x25. Changing it to console did'nt help. Does anybody know what I did wrong? Thanks for helping! ===Servalys Analytical Chemistry Services= Wybo H. Dekker| Deilsedijk 60 | tel (31)345-652164 [EMAIL PROTECTED] | 4158 CH Deil, The Netherlands | fax (31)345-652383
Re[2]: dosemu 0.60.3-1 won't run
I just want to report that I got dosemu 0.60.3-1 to work (or whichever the version is in the Debian 1.1 stable tree is) when booting from the hdimage instead of booting from the floppy. I must also admit that I got the message ERROR: can't get floppy parameter of /dev/fd0 (Interrupted system call) when trying to boot from the floppy, and then kicked off. lazaro [EMAIL PROTECTED] __ Reply Separator _ Subject: Re: dosemu 0.60.3-1 won't run Author: debian-user@lists.debian.org at cclink Date:21.09.96 08:19 Paul Christenson \[N3EOP\] wrote: I'm trying to run dosemu, version 0.60.3-1. However, whenever I go to I haven't been able to get dosemu to run with Debian 1.1.4 (kernel 2.0.6) either. Both systems I installed it on (completely different hardware) die after the following output: Linux DOS emulator 0.60.3 $Date: 1995/05/06 16:25:30 $ Last configured at Wed Nov 1 22:45:35 1995 on diannau, Linux 1.2.13 #5 Wed Oct 11 09:57:23 MST 1995 Bugs, Patches New Code to linux-msdos@vger.rutgers.edu DPMI-Server Version 0.9 installed ERROR: can't get floppy parameter of /dev/fd0 (Interrupted system call) error exit: (5,0x0005) in_sigsegv: 0 ignore_segv: 0 Not a good day to die! After looking at the DOSEMU home page, I decided that it is probably a kernel problem. They recommend dosemu-0.64.0.tgz for 2.0.x kernels. I got that and the compile fails with the interesting message: --- make[1]: *** No rule to make target `/usr/Makefile', needed by `include/kversion .h'. Stop. make[1]: Leaving directory `/usr3/src/dosemu-0.64.0/src' make: *** [default] Error 2 --- However, the latest development version for 2.0.x kernels (dosemu-0.63.1.80) compiles cleanly. I haven't been able to get it to run yet because when I attempt to load the module emumodule.o, I get an error message to the effect that the package was compiled for the 2.0.0 kernel while I am running the 2.0.6 kernel. Probably something to do with the Debian kernel header files. I just got it to compile this morning and hope to sort out the emumodule.o problem this evening when I get home from work. BTW, the DOSEMU development work is located at: http://www.ednet.ns.ca/auto/rddc and the DOSEMU homepage is at: http://www.ednet.ns.ca/~macleajb/dosemu.html Raymond -- -- Dr. Raymond Rusk --|\^/|Internet: - Network Services _|\| |/|_ [EMAIL PROTECTED] University of Victoria Voice: (604) 721-7654 -- Victoria, BC V8W 3P4 _./|\._ Fax: (604) 721-8778 ---
Re: dosemu 0.60.3-1 won't run
I remember I needed to install the xcompat package. did you? Maybe you want to check that if no better solution is at hand :-) lazaro [EMAIL PROTECTED] __ Reply Separator _ Subject: dosemu 0.60.3-1 won't run Author: debian-user@lists.debian.org at cclink Date:20.09.96 19:18 I'm trying to run dosemu, version 0.60.3-1. However, whenever I go to run it, I get: = moe:~ dosmoe:~ dos dos: can't load library '/usr/lib/libX11.so.6' Unknown error dos: can't load library '/lib/libX11.so.6' Unknown error dos: can't find library 'libX11.so.6' moe:~ = However, I do have /usr/X11R6/lib/libX11.so.6 on the system. Symlinking does not help. Help??? -- +---+ . | Technical Support Engineer, Cyclades Corporation | | 800/88-CYCLADES (882-9252) or (510)770-9727, x258 | | Maker of High Performance Multiport Serial Cards | +---+
single Debian on HD for two boxes?
Hi, I didn't succeed yet to share my portable 1GB SCSI-HD with Debian 1.1 (w/updates up to 1.1.8) to run Linux on two different boxes: Box 1) Non-internet connected (although planning and intranet). clone PC w/ i486/DX33 + 16MB RAM + 540MB SCSI HD (SCSI ID-1) + NE2000 NIC clone Box 2) Internet connected box at work. Compaq i586/90Mhz + 16MB RAM + PCI-IDE 633MB HD PCI-Ethernet AM79C970KC on board. I have problems in my connection to the local network when at work. The same applies to mail (can send but not receive mail). Cannot ftp either except to localhost. I can ping localhost but I can't see any other host in the net. I am sure is a config problem as I managed to see the network in a previous install on the same machine. I read the documentation but I am still stumped. What output would you like to see to be able to help me? or Where should i start looking to solve the problem? Is there any post-installation netconfig script? by now I modified the config files manually (/etc/init.d/network I guess and /etc/resolv.config i my memory serves me). Has anybody tried this sharing the whole file-system in a HD approach? I am sure there can be additional details to take into account if one goes for two different root systems (one on his own partition). Some reflections: - At home I have an ISA AHA 1542CF SCSI adapter while at work I have a ISA AHA 1542CP SCSI adapter (plug play aware) so the fs can live on /dev/sda without any problem. - I also managed to make Linux to recognize the PCI ethernet chip onboard AM79C970KC. The NE2000 at home is also recognized without problem. I don't think the different cards can make a problem as far as the kernel recognizes both. Thank you for your help, Lazaro [EMAIL PROTECTED]
Re: Debian Linux Installation problem
Unless you're inserting the wrong disk, it looks like a kernel bug. Send it to Linus. lazaro [EMAIL PROTECTED] __ Reply Separator _ Subject: Debian Linux Installation problem Author: debian-user@lists.debian.org at cclink Date:19.09.96 22:14 I have run into a strange problem while trying to install Debian Linux 1.1. I downloaded the boot, root and base image files (3.5), rawrote the image files to floppies and booted off the boot floppy. At the boot prompt, I entered w/ the boot floppy still inside the floppy drive. I inserted the root floppy disk after being prompted to do so. After enter, my box just hung up. Here is what I can copy from the screen: Ramdisk driver initialized: 16 ramdisks of 4096K size ide: 430FX (Triton) on PCI bus 0 function 57 [for some reason, VX is not] ide0: BM-DMA at 0x9000-0x9007 [being correctly identified] ide0 timing: (0xa207) sample_CLKs=3, recovery_CLKs=2 master: fastDMA=off PreFetch=on IORDY=on fastPIO=on slave: fastDMA=off PreFetch=off IORDY=off fastPIO=off ide1: BM-DMA at 0x9008-0x900f ide1 timing: (0x8000) sample_CLKs=5, recovery_CLKs=4 master: fastDMA=off PreFetch=off IORDY=off fastPIO=off slave: fastDMA=off PreFetch=off IORDY=off fastPIO=off hda: WDC AC21200H, 1222MB w/ 128kB Cache, LBA, CHS=621/64/63, DMA ide0 at 0x1f0-0x1f7, 0x3f6 on irq14 Floppy drive(s): fd0 is 1.44M Started kswapd v1.4.2.2 FDC 0 is an 8272A NCR53c406a: no available ports found PPA: unable to initialise controller at 0x378, error 2 scsi: 0 hosts scsi: detected total lance.c: PCI bios is present, checking for devices... Partition chec: hda: hda1 VFS: Insert root floppy disk to be loaded into ramdisk and press Enter RAMDISK: Compressed image found at block 0 stack segment: CPU: 0 EIP: 0010: [?00169ea5] EFLAGS: 00010246 eax: ebx: 005f ecx: 00ef ecx: f000ef6f esi: 0009 edi: 00fe8020 ebp: f000ef6f esp: 00258738 ds: . Process swapper (pid: 1, process nr: 1, stackpage=00258000) Stack: .. .. .. Call Trace: [0016aa05] Code: 0f b6 5d 00 fb 10 0f 87 6a ff ff ff 0f b6 4d 01 d3 6c 24 [the machine just hung up at this point] Configuration: AMD K5-90 on Triton VX board, Western Digital AC21200 1282MB IDE (one 200MB DOS partition), S3 Trio64 based video card, 16MB RAM I would really appreciate if someone could kindly help me out of this. Thanks. A. R. ABID [EMAIL PROTECTED]
Re: Q. about dosemu package
Yves Arrouye [EMAIL PROTECTED] wrote: Subject: Q. about dosemu package Author: debian-user@lists.debian.org at cclink Date:20.09.96 08:25 [snip] 2. I only have Windows 95 on my machine. Is it possible to boot its DOS from Dosemu? Or should I make a hard-disk file with a 6.x DOS? I have no experience w/Windows95 but another alternative is to have a hard disk image, which is afile on your linux filesystem pretending to be a DOS fs. 3. Does any of you have succeeded in using Windows 3.1 under dosemu? If so, I'd like to be helped (in private mail, please). In the accompanying documentation dosemu warns you about the danger of trying that. In short, Windows is not usable under dosemu. lazaro [EMAIL PROTECTED]
Re: where's man ??
Hi Chris, Subject: where's man ?? Author: debian-user@lists.debian.org at cclink Date:18.09.96 09:11 I just installed Debian 1.1 and I logged on as root. First thing I notice, there are no editors installed. Not one. You would think this would be a required thing... another thing... 'man' doesn't seem to exist! Logged in as root, typing 'man man' gives command not found -- and it's not in /usr/bin. what gives?? - Try ae (anthony's editor). The vi clones, emacs as well as the others editors must be installed (type `dselect' or `dpkg -i your_favorite_package_name'. They are not in the base system that you got from the tree 1.44 base disks. - The same applies to man. You have to install the corresponding package. Regards, lazaro [EMAIL PROTECTED]
Re: Mouse
There is not support for busmice in the standard boot disk kernel. Try # dmesg | grep -i mouse to see if your mouse was detected by the installed kernel. You will probably get no output, so you can confirm that the kernel does not know about your mouse. Otherwise you should see the line recognizing the bus mouse. Solution: You will have to recompile the kernel (download the kernel-source_2.0.6.deb, etc, etc.) If you have installed the linuxdoc package (check the name as my memory may not serve here) then try to look at the Busmouse howto (in Debian the doc is under /usr/doc/... ). A last word... yes. it takes times to known any new OS... and since Linux + Debian are moving targets, that's the price you pay. cheers, lazaro [EMAIL PROTECTED] __ Reply Separator _ Subject: Mouse Author: debian-user@lists.debian.org at cclink Date:17.09.96 05:25 Hi, I've just installed the X11 distribution (xbase, xserver-s3 and xfntbase). When I try startx it comes back with no mouse found or a message to that effect. I am using a Dell P120t with a bus mouse connected to the on board interface. I see quit a few mouse devices in /dev. Which one is active? How can I extract this information without having to turn to the experts? A minor observation on the Web sites I have looked at so far with respect Linux and Debian. From my point of view as a UNIX user, DOS/Windows/Embedded programmer there is very little on-line information available that I can make sense of. Probably in 6 months time I'll understand about half of it Maybe I'm looking in the wrong places, maybe the philosophy is only those who know can learn, maybe I don't have the right IQ, but the fact is that up till now I have come up to a brick wall. The information available in the HOWTOs is very good, but from an initial startup point of view, if things go wrong I need to browse through a couple of MB of data, not very productive. As I said, maybe I'm looking in the wrong places, please any advice that may be advantageous. Simon Martin[EMAIL PROTECTED] Old software engineers never die, they just fail to boot Any Trademarks used in this document are recognized as Registered Trademarks of their respective owners.
Re: how to exclude a directory from find?
You wrote: Subject: how to exclude a directory from find? Author: debian-user@lists.debian.org at cclink Date:11.09.96 21:33 I'm trying to search for unused files, but I want to exclude a directory from the search. I tried cd /scratch find . -atime +7 -path ./var -prune -o -print but it doesn't work. Any clues? Carlos If you're only interested in regular files, try adding the `-type f' to the find command, e.g., $ cd /scratch find . -type f -atime +7 -path ./var -prune -o The -print flag is not really needed as is executed by default. Certainly it would be nice to have something like: $ find . -type !d to match files which are not directories, but I don't know if something like that is possible for find. So if can take your question and rephrase it: Is there any kind of logical not affecting a flag in find? Something similar to the `grep -v regexp' as opposed to `grep regexp'. Answers are welcome. When I need something like that, I always end up adding the flag -ls to `find', and piping to `grep -v pattern'. Just to give you an idea of what I have in mind (I haven't tried this... would you?) $find . -ls | grep -v dr and if only the filename list is what you need, pipe the ouptut to `cut -c column_number_here- '. As it is written above it will fail, as it filters out a filename with the string `draconiano ', but you got the idea. right? I repeat the above is a dirty/slow/inefficient/ugly/ and _imperfect_ solution :-). I am guessing the ?s attempt to catch any of `the single characters r w x s or - which may appear in the permission string written due to the `-ls' flag to `find'. I am sure there might be better ways of specifying the pattern to match (maybe grep'ing -v all the possibilities : `drwxrwxrwx ', `drwxrwxrw- ', etc). The space at the end is important and the double quoting too to avoid the shell to expand the patttern. Of course, this may not be a solution for including in shell scripts, but if you do it once in a while it might work. Cheers, Lazaro [EMAIL PROTECTED] PS. BTW, the man page for gnu find is the 1st one I recommend to learn thoroughly (I should do it again :-).
Re: Strange problems with mc.
Scheetz (warf) writes: Subject: Strange problems with mc. Author: debian-user@lists.debian.org at cclink Date:12.09.96 04:59 Just recently I have begun having strange problems with midnight commander. After some time some of the keys stop working. This usually involves the arrow keys, but occasionaly the function keys stop working as well. When this happens pressing the key produces characters at the prompt, but no results. In the case of the arrow keys I can quit mc, type reset at the prompt and return to mc with functional arrow keys. In the case of the function keys killing the process and resetting the terminal does not fix the problem. However, if I log out and log back in mc again works fine. I am using the 3.2.1-1 version of mc. I have updated several package recently (don't clearly remember which ones) and installed xpdf. Has anyone had similar problems? Anybody have any idea what's happening? Well I have just an idea of what may be the problem if that happens under X. If you have the problem on the console too, just forget this message. It smells like a terminfo/termcap problem. xterm have usually such a problem. I experienced the same running mc on HP machines with broken terminfo database. In the manual of mc there is some info about how to fix that. hope it helps, lazaro [EMAIL PROTECTED]
Debian 1.2 release date?
Hi folks, Is the release of Debian 1.2 around the corner as scheduled? Thanks for such a good job! lazaro [EMAIL PROTECTED]
Re: Getty ports - dumb question
I hope its a typo since ttyN is not the same as ttySN (N=0,1,etc) e.g., terminals vs. serial lines. Said that, by default I had more that the really existing serial lines (ttySN) configured To fix that edit the file you'll get after # find /etc | xargs grep tty I remember editing that file as recommended in it. Bruce: That could be part of the installation process in Debian 1.2 maybe. __ Reply Separator _ Subject: Getty ports - dumb question Author: [EMAIL PROTECTED] at cclink Date:09.09.96 10:02 I did a ps and found these getty ports running: 186 2 S 0:00 /sbin/getty 9600 tty2 187 3 S 0:00 /sbin/getty 9600 tty3 188 4 S 0:00 /sbin/getty 9600 tty4 189 5 S 0:00 /sbin/getty 9600 tty5 190 6 S 0:00 /sbin/getty 9600 tty6 I only have 2 serial ports ttyS0 and ttyS1. Should these getty ports be running? How are these ports accessed? Are they physical RS-232 ports? Jim
Re: Dosemu
I had no problem in running dosemu (deb package 0.60.1?) that came with Debian 1.1 with kernel 2.0.6 (I recompiled the kernele for other reasons so I don't know if the standard in boot.bin could have give any trouble to dosemu) Write to me if I can help you. Lazaro __ Reply Separator _ Subject: RE: Dosemu Author: debian-user@lists.debian.org at cclink Date:06.09.96 02:44 On 04:17:39 [EMAIL PROTECTED] wrote: Has anyone succeeded in getting the latest versions of Dosemu to work? I can successfully compile, but can't insmod emumodule. Insmod dumps fifteen or so lines saying: x undefined ... Loading failed! The module symbols (from linux-2.0.7) don't match your linux-2.0.7 What's going on?? Seems as if there are some system modules ( I use a very modularized kernel ) which are not loaded. However, I use kerneld, so all neccessary mods should be there. Someone please help!! Thanx... :-) No, it doesn't work here either. My I-Connect CD was cut on 12 june. I haven't fussed with it at all, but just wanted to respond that in my case it doesn't work either. Paul
dosemu and bochs? (it was WABI)
Hi, DOSEMU I installed (not without some minor problems) dosemu_0.60.1-3.deb yesterday. It couldn't boot from the real floppy so I had to create an image of it in /var/lib/dosemu/bdisk as suggested in the config.dist - renamed to /etc/dosemu.conf. I also had to modify the latter to boot from the floopy image instead of booting from the real the floppy. Then I managed to boot from the hdimage, but still have problems to recognize the floppy when I dir a: dosemu dies. Q: Any suggestion? Besides I had some problems when running xdos or dos -X in an xterm. It doesn't recognize all the keys. I think it can be related to some of the problems I had with the linux binary midnight commander running in an xterm (absent when running on a linux console). Q:Has anybody experience the same? May that be related to a bad terminfo database? BOCHS --- There was an interesting article (IMO well written) by the developer of bochs in the September issue of the Linux Journal. It is a CPU independent 32 bit dos emulator w 80086/80286 instruction set support. It is shareware: 25 US$. http://world.std.com/~bochs is the link to get it. Q:Has anybody out there tried/debian-packaged it? and, How stable is it? lazaro [EMAIL PROTECTED]
dosemu and bochs? (it was WABI)
Hi, DOSEMU I installed (not without some minor problems) dosemu_0.60.1-3.deb yesterday. It couldn't boot from the real floppy so I had to create an image of it in /var/lib/dosemu/bdisk as suggested in the config.dist - renamed to /etc/dosemu.conf. I also had to modify the latter to boot from the floopy image instead of booting from the real the floppy. Then I managed to boot from the hdimage, but still have problems to recognize the floppy when I dir a: dosemu dies. Q: Any suggestion? Besides I had some problems when running xdos or dos -X in an xterm. It doesn't recognize all the keys. I think it can be related to some of the problems I had with the linux binary midnight commander running in an xterm (absent when running on a linux console). Q:Has anybody experience the same? May that be related to a bad terminfo database? BOCHS --- There was an interesting article (IMO well written) by the developer of bochs in the September issue of the Linux Journal. It is a CPU independent 32 bit dos emulator w 80086/80286 instruction set support. It is shareware: 25 US$. http://world.std.com/~bochs is the link to get it. Q:Has anybody out there tried/debian-packaged it? and, How stable is it? lazaro [EMAIL PROTECTED]
Re: minimal system
Please, don't threat with the microstuffit :-) Concerning your not very specific question here is my rule of Thumb: No matter how large your HD is you will end up filling it. seriously, you may want look at the Debian FAQ revamped recently (great job!) under any debian mirror in /doc/FAQ/ or in http://sgk.phast.umass.edu/FAQ/debian-faq.html Shortly, Yes. You can have more that a reasonable Debian installation with X and TeX and Emacs and reasonable space for home directories within 120MB + swap. lazaro [EMAIL PROTECTED] __ Reply Separator _ Subject: minimal system Author: debian-user@lists.debian.org at cclink Date:29.08.96 10:41 can anyone advise a new debian user on a scenario in which a useable system can be installed on a 120 meg hard drive with a 20 meg swap on another disk? If I can't use it for much then it seems that I would be better off going back to microstuffit- not all bad but thanks 1allMike List
Re: Debian on a Compaq Prosignia 4/66
Yes Dave, You can have Debian Linux on your compaq. This is from a previous posting I sent to this list: I find this LOADLIN scheme a very flexible one. I find the related DOS applications rdev, pfdisk and ext2tools good companions to this DOS booting scheme. A DOS readln or readkey utility (or BE ASK in NORTON UTIL) is also handy for creating extremely configurable DOS bat files to manage the most complex scenarios you can imagine. Misc: This is the only method I found to boot linux on Compaq with PCI on board as linux need to relocates the PCI services through a DOS driver provided by COMPAQ. Syslinux or LILO cannot make linux see the PCI chips (Linus Torvald said). Disclaimer: LILO is very good,... this is just an alternative. Lazaro [EMAIL PROTECTED] This is what you have to try: 1) Get the Software package sp116.zip provided by Compaq (at www.compaq.org?). Run sp116.exe contained in it to extract MOVEPCI.SYS and MOVEPCI.DOC. Read that documentation. If it suits your machine (it works for my Deskpro 590 and reported to work with Deskpro XL both compaq boxes with PCI on board) keep reading. Otherwise get more info from COMPAQ and come back later to point 3. 2) Now that the driver lets linux recognize the PCI on board, you need to replace the SYSLINUX method of for booting. A good alternative is the DOS executable LOADLIN. Once you get it: Make a DOS boot floppy with DEVICE=MOVEPCI.SYS as the first line in CONFIG.SYS. Then you can load Linux with loadlin from DOS from config itself with a SHELL=LOADLIN .. or from AUTOEXEC.BAT Or from the DOS command line. If everything went smooth to this point, you shall see that Linux detects the PCI chips on board during bootup. You may also want to make a customized Debian-type boot disk by: a)copying everything except syslinux in the Debian standard 1996-07-14 boot disk (you don't need a special kernel) onto a _DOS_bootable_ disk; b)preppending DEVICE=MOVEPCI.SYS to the config.sys; and c) copying the LOADLIN stuff. I find adding some menuing DOS utilities and a small editor very handy to fix things on the road in case I need it. And that's all! just a pity XFree86 doesn't support the Compaq graphic cards. But you can try (10'minutes working demo) the X server from ftp.xinside.com to test X applications on the Debian linux box. Just keep track of the files installed as I had some problems with the scripts provided. If you get stucked or find this guide too brief to make ANY sense out of it :-) just write me privately for more details (I have written something about this where is it?) Also, have a look at a related WEB page: a href=http://www-c724.uibk.ac.at/liedl.html;Klaus Liedl/a,a href=mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]/a/i/h4 iPage last modified: Mon Oct 9 10:41:10 MET 1995/ip This kind soul used to mantain a page related to the deskpro XL. I find the info very useful from fixing Linux on my Deskpro 590 with a PCI Net card on board. cheers, lazaro [EMAIL PROTECTED] __ Reply Separator _ Subject: Debian on a Compaq Prosignia 4/66 Author: debian-user@lists.debian.org at cclink Date:23.08.96 21:55 We were just given a Compaq Prosignia 4/66 with 40 MB RAM and a 1.05 GB SCSI drive to user as a DB Server. Our preference is to run it under Linux. However, it has a built-in SCSI controller. So far we have tried Debian 1.1, 1.1.6, and all of the Debial 2.0.5 alternate boot disks with no luck in detecting and working with the SCSI controller... DOS does work on the system as did Novell 3.12. The system arrived without documentation. So far the email to Compaq asking for the SCSI controller equivalent has not been answered. Any suggestions? TIA, Dave
Re: lilo installation on IDE disk 500 megabytes
You only need to copy the kernel image to the DOS partition, for example: cp /boot/vmlinuz-2.0.6 ./dos/vmlinuz Then when you've booted DOS type (make a batch :-) loadlin vmlinuz root=/dev/hda2 ro Or have alook at the loadlin documentation. Some tips for advanced use of this boot scheme: - You may prefer to name the kernel copied to the DOS partition with a more descriptive name, like l960714.std (for the standard kernel image of 1996-07-14). This will help when trying different kernels (diff configs or diff just versions or special kernels or...) - You can copy the kernel to a floppy and boot from the floppy with a minimal DOS config.sys (to save memory LOADLIN needs). - You can make a batch file or for DOS 6.0 use menus in config.sys and/or autoexec.bat to load different kernels or systems with root on different partitions (not your case). I find this LOADLIN scheme a very flexible one. I find the related DOS applications rdev, pfdisk and ext2tools good companions to this DOS booting scheme. A DOS readln or readkey utility (or BE ASK in NORTON UTIL) is also handy for creating extremely configurable DOS bat files to manage the most complex scenarios you can imagine. Misc: This is the only method I found to boot linux on Compaq with PCI on board as linux need to relocates the PCI services through a DOS driver provided by COMPAQ. Syslinux or LILO cannot make linux see the PCI chips (Linus Torvald said). Disclaimer: LILO is very good,... this is just an alternative. Lazaro [EMAIL PROTECTED] P.S. I could send you a copy of my setup if you want. __ Reply Separator _ Subject: lilo installation on IDE disk 500 megabytes Author: debian-user@lists.debian.org at cclink Date:22.08.96 07:39 I am trying to install the 7-14-96 debian release on a machine with over 500 megabytes on an IDE hard disk. I want to have a DOS partition and a linux partition. At present fdisk shows: Device Boot BeginStart End Blocks Id System /dev/hda111 356 179392+ 6 DOS 16-bit =32M /dev/hda2 * 357 357 966 307440 83 Linux native /dev/hda3 967 967 99916632 82 Linux swap fdisk also displays a warning: The number of cylinders for this disk is set to 1025. This is larger than 1024, and may cause problems with: 1) software that runs at boot time (e.g., LILO) The lilo documentation says: Note that large partitions that only partially extend into the forbidden zone are still in jeopardy even if they appear to work at first, because the file system does not know about the restrictions and may allocate disk space from the area beyond the 1024th cylinder when installing new kernels. Lilo suggests either using LOADLIN or booting from the DOS partition: In order to accomplish this, the DOS partition is mounted read-write, a directory (e.g. /dos/linux) is created, all files from /boot are moved to that directory, /boot is replaced by a symbolic link to it, the kernels are also moved to the new directory, their new location is recorded in /etc/lilo.conf, and finally /sbin/lilo is run. I tried creating a subdirectory c:\linux in DOS, then from linux: mkdir ./dos mount /dev/hda1/linux ./dos cp /boot ./dos At this point, I got some warning or error messages. It looks as though file names got truncated, and in some cases discarded completely. From ls /boot: System.map-2.0.6 chain.b any_b.b map any_d.b mbr.b boot.0302os2_d.b boot.b vmlinuz-2.0.6 From ls ./dos: any_b.bmap any_d.bmbr.b boot.030 os2_d.b boot.b system.map chain.b I would appreciate some hand-holding at this stage. Exactly what commands do I type to carry out the lilo instructions (specifically, the symbolic link and copying the kernel)? Or would I be better off trying loadlin? Sorry this has been such a long post. Thanks for your patience!
Re[2]: Need help to set right ownerships
Hi Ken,
Yes.. I know that should have made in a different way and yours is one of the
possibilities (provided that there are not files beginning with two dots like
/home/lds/..a_weird_name_for a file. I know that under the ksh I could have
used
# cd /home/lds ; chown -R lds:users .[!.]* .??* *)
to match all files which do not begin with two dots (like ..) AND the files
which begin with two dots but have more than two characters like ..a
:-( :-(
But now that I made the mistake I need to fix it! :-)?
I have not done yet, still waiting for suggestions.
Thanks,
lazaro [EMAIL PROTECTED]
__ Reply Separator _
Subject: Re: Need help to set right ownerships
Author: debian-user@lists.debian.org at cclink
Date:21.08.96 02:45
At 12:04 PM 8/20/96 cet, you wrote:
Hi,
Anybody can help me, please? I really need to be sure how to fix this.
Logged as root I did:
# cd /home/lds ; chown -R lds.users * ; ls -laR | more
and noticing that I forgot to change the ownership of the (hidden) dot files
I typed:
# chown -R lds:users ~/.*
Uc! the `*' expands to `.' among others. By the time I noticed my two
mistakes and pressed CTRL-C, I had already changed the ownership of /root,
/home, and some subdirs in /var and /usr.
I saved on a floppy a list (find $dir -exec ls -laR {} \; | grep lds
users) with $dir set to /usr and /var. I fixed the ownerships of /root and
/home by hand and the I typed
# shutdown -r now
That was not very clever :-( but I was thinking of fixing everything when
having
more time, from an emergency base system I have on a separate 16MB partition.
I am not quite sure how to deal with the files in /var which are written at
boot time ... ooops! and at shutdown tooo! :-(
Maybe it help to mention that I have /, /var, /usr, /usr/local and /home (and
swap) on separate partitions.
Right now I know which files have the wrong ownership but do not know what
should be the right one. I thought of setting the ownership to root:root to
the
files in the list and then fix by hand those who shoud be owned by other
system
group (news, mail,...etc). I think that then I should proceed by fixing
file by
file, i.e.,
0)Fixing those in /var/lib/dpkg (any pointer about how to do it?)
1)removing all installed packages except those flaged as essential (base),
2)comparing file by file with a fresh Debian 1.1.x base system (I have one).
3)Reinstalling again the packages.
Any suggestion to make it as safer/cleaner/greener/faster as possible will be
greatly appreciated. A script maybe to do it automatically?'
I am not suscribed to the list right now so please answer this to
my private e-mail. Thank you very much,
Lazaro [EMAIL PROTECTED]
You should have used chown -R lds:users ./.[a-zA-Z]*
---
Key fingerprint = D6 A7 D7 8C 92 CB 42 FD 60 D5 62 1C D7 B9 EA 8E
Ken Gaugler N6OSK Hybrid Networks, Inc. Cupertino, Calif.
URL: www.hybrid.com (home: [EMAIL PROTECTED] URL: users.aimnet.com/~keng)
The life of a Repo Man is ALWAYS INTENSE...
Help: how to fix ownership of /var /.. ?
(reposting looking forward to get some answers)
Hi Debian-users,
Some files under /var and /usr are normally owned by root:systemgroup
were the string systemgroup above can be root, staff, adm , mail, news ...etc
Q: Will the bootup break something if the ownership of /var/... are set to
root:root instead?
I am asking this because I want to be sure how to fix the following mistake.
Logged as root I typed,
# cd /home/lds ; chown -R lds:users *
and to change the ownership of the (hidden) files beginning with a period under
/home/lds I typed in the hurry and by mistake:
# chown -R lds:users ~/.*
Ouch! two errors in one line :-(
`~' is interpreted as /root and `*' expands to `.' among others like .. which
the whole system tree. By the time I pressed CTRL-C, I had already changed the
ownership of /root, /home, and some subdirs in /var and /usr to lds:users.
To fix this I first saved a list of the damaged files
# find $dir -exec ls -laR {} \; | grep lds users \
/floppy/fix_me.lst
where $dir were set to /usr and /var. I fixed the ownership of /root and
/home by hand and then halted the system with
# shutdown -r now
so I could fix the ownership problem from an emergency Debian 1.1. base
system I have on a separate 16MB partition.
Specifically I am not quite sure how to deal with the files in /var which are
written at boot time ... ooops! and at shutdown too! :-(
On the messed up system I have /, /var, /usr, /usr/local and /home (and swap)
on separate partitions if that info is useful to you.
From the listing I saved in the file fix_me.lst on the floppy, I know _which_
files have the wrong ownership. What I do not know is what was the original
ownership, although for some of the files I can check the emergency
minimal base system on the 16MB partition.
My present idea to fix this problem is:
1) Set the ownership to root:root to all the files listed in /floppy/fix_me.lst
2) Fix by hand those who should be owned by other system group (like adm, mail,
news,...etc). Those files present in the base system should not pose any
problem, as I can just check the clean emergency minimal base system. Or maybe I
am missing something?
However it is not completely clear to me how to deal with some files which may
have been created after installing non-base packages.
Q: May they have had different from root:root ownership too?.
Another possibility would be to:
1') Remove (not purge) all the packages I installed on top of the base
system.
2') Fix ownership of included in base files by checking with the minimal base
system.
3') Reinstall packages
Any suggestion to make it as safer/cleaner/greener/faster as possible will be
greatly appreciated. Thank you very much for any idea/suggestion/pointer,
Lazaro
[EMAIL PROTECTED]
Help: need to fix ownership of /var/...
Reposting message with slight modifications as I haven't got any answer yet.
-
Hi,
Some files under /var and /usr are normally owned by root:systemgroup
were the string systemgroup above can be root, staff, adm , mail, news ...etc
Q: Will the bootup break something if the ownership of /var/... are set to
root:root instead?
The question is related to a mistake I made. Logged as root I typed,
# cd /home/lds ; chown -R lds:users *
and to change the ownership of the (hidden) files beginning with a period under
/home/lds I typed in the hurry and by mistake:
# chown -R lds:users ~/.*
Ouch! two errors in one line: `~' is interpreted as /root and `*' expands to
`.' among others like .. which
the whole system tree. By the time I pressed CTRL-C, I had already changed the
ownership of /root, /home, and some subdirs in /var and /usr to lds:users.
To fix this I first saved a list of the damaged files
# find $dir -exec ls -laR {} \; | grep lds users \
/floppy/fix_me.lst
where $dir were set to /usr and /var. I fixed the ownership of /root and
/home by hand and then halted the system with
# shutdown -r now
so I could fix the ownership problem from an emergency Debian 1.1. base
system I have on a separate 16MB partition.
Specifically I am not quite sure how to deal with the files in /var which are
written at boot time ... ooops! and at shutdown too! :-(
On the messed up system I have /, /var, /usr, /usr/local and /home (and swap)
on separate partitions if that info is useful to you.
From the listing I saved in the file fix_me.lst on the floppy, I know _which_
files have the wrong ownership. What I do not know is what was the original
ownership, although for some of the files I can check the emergency
minimal base system on the 16MB partition.
My present idea to fix this problem is:
1) Set the ownership to root:root to all the files listed in /floppy/fix_me.lst
2) Fix by hand those who should be owned by other system group (like adm, mail,
news,...etc). Those files present in the base system should not pose any
problem, as I can just check the clean emergency minimal base system. Or maybe I
am missing something?
However it is not completely clear to me how to deal with some files which may
have been created after installing non-base packages.
Q: May they have had different from root:root ownership too?.
Another possibility would be to:
1') Remove (not purge) all the packages I installed on top of the base
system.
2') Fix ownership of included in base files by checking with the minimal base
system.
3') Reinstall packages
Any suggestion to make it as safer/cleaner/greener/faster as possible will be
greatly appreciated. Thank you very much for any idea/suggestion/pointer,
Lazaro
[EMAIL PROTECTED]
Need help to set right ownerships
Hi,
Anybody can help me, please? I really need to be sure how to fix this.
Logged as root I did:
# cd /home/lds ; chown -R lds.users * ; ls -laR | more
and noticing that I forgot to change the ownership of the (hidden) dot files
I typed:
# chown -R lds:users ~/.*
Uc! the `*' expands to `.' among others. By the time I noticed my two
mistakes and pressed CTRL-C, I had already changed the ownership of /root,
/home, and some subdirs in /var and /usr.
I saved on a floppy a list (find $dir -exec ls -laR {} \; | grep lds
users) with $dir set to /usr and /var. I fixed the ownerships of /root and
/home by hand and the I typed
# shutdown -r now
That was not very clever :-( but I was thinking of fixing everything when having
more time, from an emergency base system I have on a separate 16MB partition.
I am not quite sure how to deal with the files in /var which are written at
boot time ... ooops! and at shutdown tooo! :-(
Maybe it help to mention that I have /, /var, /usr, /usr/local and /home (and
swap) on separate partitions.
Right now I know which files have the wrong ownership but do not know what
should be the right one. I thought of setting the ownership to root:root to the
files in the list and then fix by hand those who shoud be owned by other system
group (news, mail,...etc). I think that then I should proceed by fixing file by
file, i.e.,
0)Fixing those in /var/lib/dpkg (any pointer about how to do it?)
1)removing all installed packages except those flaged as essential (base),
2)comparing file by file with a fresh Debian 1.1.x base system (I have one).
3)Reinstalling again the packages.
Any suggestion to make it as safer/cleaner/greener/faster as possible will be
greatly appreciated. A script maybe to do it automatically?'
I am not suscribed to the list right now so please answer this to
my private e-mail. Thank you very much,
Lazaro [EMAIL PROTECTED]
Re[2]: Installing Linux over a LAN
When I installed Debian 2 days ago, I was wishing that instead of the 3
base floppies, it could at least use a .tar.gz file containing
the same stuff somewhere on an existing ext2 partition. A small change
(?) like that would make the install a lot easier.
It is possible to do so. you have to make base1_1.tgz accessible (e.g. I
mounted the fs from the shell at vc #2) before installing the base system.
It is explained in the installation menu.
long explanation:
I cannot recall it exactly but I think that within DOS (or a working linux) I
copied/downloaded base1_1.tgz to the root on my DOS fs, began the installation
process with the Debian boot and root disks, and _before_ installing the base
system I switched to vc 2, and
mkdir /mydos ; mount -t msdos /dev/your_partition_where_you_find_the_tgz /mydos
and switched back to vc 1 whe I choose the Install the base system option.
At that stage, the installation script looks for the tgz'ed base under on the
1st or 2nd level of any fs under / . If it finds it it wont ask for the
floppies.
Try it!
Lazaro [EMAIL PROTECTED]
__ Reply Separator _
Subject: Re: Installing Linux over a LAN
Author: debian-user@lists.debian.org at cclink
Date:12.08.96 07:36
On Sun, 11 Aug 1996, Bruce Perens wrote:
For Debian, you can do the installation using the 5 floppies, and then all
other software can be auto-loaded by dselect via FTP. We can do better
than that, and will in 1.2 if I get time (or a volunteer to work on the
installation system).
When I installed Debian 2 days ago, I was wishing that instead of the 3
base floppies, it could at least use a .tar.gz file containing
the same stuff somewhere on an existing ext2 partition. A small change (?)
like that would make the install a lot easier.
--
#!/usr/bin/perl -pl- ,,ep) ayf |)nj,,
$_=reverse lc$_;s@@''@g;y/[]{A-R}()a-y1-9,!.?`'/][}Joey Hess
{)(eq)paj6y!fk7wuodbjsfn^mxhl5Eh29L86`i'%,/;[EMAIL PROTECTED]@|@g# [EMAIL
PROTECTED]
He. He. He. - - Herman Toothrot
Re[2]: new to debian; some questions
What about modifying the options in the file /etc/adduser.conf? Btw, there is a typo in that file equivilant (AFAIR) instead of equivalent ... does that qualify for a bug Ian? ;-) Lazaro [EMAIL PROTECTED] _ Reply Separator _ Subject: Re: new to debian; some questions Author: debian-user@lists.debian.org at cclink Date:10.08.96 19:11 Joey Hess writes (new to debian; some questions): ... Does debian use the user groups system that redhat uses, that makes each user be in a group containing only themselves, so the umask can be set to 002? I see in /etc/group that each user does get placed in their own group. But I see in /etc/profile that the umask is set to 022.. Can I change that to 002 safely? Yes, you can, but adduser will edit it when it installs people's .profile's anyway. Ian.
Re: Installing Linux over a LAN
Alan wrote: Subject: Installing Linux over a LAN Author: [EMAIL PROTECTED] at cclink Date:11.08.96 06:16 The is a nice page about setting a micro-lan in http://www.panix.com/~hypertyp/tcpip/tcpstart.html The example is given for a mac connected to a Linux box have a nice weekend, lazaro [EMAIL PROTECTED]
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
Re[2]: shutdown: non-existing PID
Phil, Michael, Maybe pstree (and friends mentioned in the man page) can help you to trace the problem Lazaro [EMAIL PROTECTED] __ Reply Separator _ Subject: Re: shutdown: non-existing PID Author: debian-user@lists.debian.org at cclink Date:07.08.96 02:39 On Tue, 06 Aug 1996 15:42:37 +0200 Michael Gaertner ([EMAIL PROTECTED]) wrote: shutdown -h now console-message: start-stop-daemon:warning: failed to kill 218: No such process Indeed there is no PID 218. BTW the pid-number changes with every shutdown. I think it has something to do with X Windows because I have another debian-system without X Windows installed - and I don't get this message. I have the same minor problem, and it's '/etc/init.d/xdm stop' which causes the t rouble. From what I've found, start-stop-daemon will kill the process tree of the daemon to stop. In case of xdm, it will try to kill xdm first, then X. But, xdm kills X too when it's about to shutdown. The message appears when xdm ki lls X before start-stop-daemon. Sometimes, no message appears, and I assume that happens when start-stop-daemon kills X before xdm. I have no fix yet. (It's only a minor annoyance) Phil.
Re: Adding nfs and ip modules to base
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
Re: lost lib
To exactly know which library a given command (say foo) needs you can try $ ldd foo If you don't find the library referenced ( e.g. library_name) in your system with: $ find / library_name) you can locate that library by $ zgrep library_name Contents.gz so you can install the package. lazaro [EMAIL PROTECTED] Reply Separator _ Subject: lost lib Author: debian-user@lists.debian.org at cclink Date:07.08.96 08:13 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. Thanks in advance for any help finding this library. Bob Hmmm... I did a 'find / -name librl.so.2' on my system and I found no such library... weird! Would you like to double check the library name again just in case. One more thing, I did happen to have 'librle.so.1' I don't know if that helps you or not. Good luck Mike...
Re: dselect/dpkg problem: install/remove
Hi, where is local/binary ?? I _think_ is a local filesystem or directory where you put your any extra package which is not present under the stable|contrib|non-free tree. For example you can put ther a) Your own packages like a custom kernel created out of the kernel-source and made (autoamtically) kernel-image-custom.deb b) the ftp'ed partial tree if you don't have the CD Anybody knows of other use for it? 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 ..I can't install the pac kage, can't re-install the package, and dselect/dpgk won't remove it! ^ It happened to me too with dselect when I run out of space in /usr (The size of the packages being selected and the free space on the filesystem would have helped... Ian, Bruce are you listening?). In my case, only the front-end dselect could not install or remove those unstable packages. This however worked for me: 1) Quit dselect 2) Install the unstable packages with dpkg -i giving the full path something like: # dpkg -i /cdrom/stable/binary-i386/devel/kernel-source-2.0.6-0.deb That will install the package and update the files dselect needs to configure/remove/purge or whatever you want to do next with the package within dselect. As I do not clearly understand the package system yet, I'm afraid to simply delete the packages and mess up dpkg's database. Don't worry, you're not alone :-). Just read the documentation you find _many_ times untill you get the feeling. dpkg --help | less and all the manual pages mentioned in the fake dpkg manpage (man -k dpkg can help too). But be patient... the Debian packaging system is a several years project so _it is_ a complicated and _excelent_ system! look also at the /var/lib/dpkg/info to learn by example what comes with every package. In my case, the package_name.list file for the unstable packages in that directory was missing ...and that confused dselect. Lazaro [EMAIL PROTECTED] __ Reply Separator _ Subject: dselect/dpkg problem: install/remove Author: debian-user@lists.debian.org at cclink Date:07.08.96 10:26 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 ??) 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 As I do not clearly understand the package system yet, I'm afraid to simply delete the packages and mess up dpkg's database. I can't install the package, can't re-install the package, and dselect/dpgk won't remove it! Coming from the SlackWare Distribution, I learned how to compile install programs using make, so there was no problem using the code to create a kernel boot floppy, which I now use to bring up the system. There are some problems with this too, but that will wait for another time. Can anyone help?
Re: Debian-1.1.3
The latex related packages were not in 1.1.2 You can find the changes in Changelog under /buzz-updates/.. If you read the messages will notice that stable, Debian-1.1.x and Debian-1.1-fixed _always_ are just links to the real files, no matter what the value of x. You can zgrep ls-lR.z at the root to check. regards, Lazaro ([EMAIL PROTECTED]) _ Reply Separator _ Subject: Debian-1.1.3 Author: debian-user@lists.debian.org at cclink Date:02.08.96 20:23 Hi all, I noticed 1.1.3 up on the master debian ftp site. Where is the doc that states the changes from 1.1.2? As far as I see it, its just a link back to the Debian-1.1-fixed (just like 1.1.2 had) Jim === Jim Gerace Senior Systems Engineer email: [EMAIL PROTECTED] www: http://www.kasinet.com
Re: dpkg-ftp or installing via FTP
- dpkg-ftp is a separate program under projects/experimental (chek withint the zgrep ls-lR.gz (only 100Kb ;-) - yes dselect will do itif you have all or just what you know you need. My experience is that you never now exactly all the dependencies so if you don't have all Anyway you can install partially with dselect, and if you don't have all what you need to resolve the dependencies, just switch to the next virtual console (alt-Fn) and ftp the missing package. Then switch back and resolve the problem within dselect. - Also, If dpkg-ftp is an option for you, maybe mounting NFS the whole thing is also viable (check the mirrors page). good luck! __ Reply Separator _ Subject: dpkg-ftp or installing via FTP Author: debian-user@lists.debian.org at cclink Date:02.08.96 21:36 Hi guys, I grabbed and installed dpkg-ftp. But I see no mention of any ftp usage when I run dpkg --help. Is there supposed to be a separate binary called dpkg-ftp? Because I can't find any... I'm trying to download the latest Debian distribution via FTP, but I've had problems both with ncftp and with dftp. I was hoping dpkg-ftp would be a better solution... Another suggestion was to mirror debian. How much space is required to mirror? Can a mirror be partial? Lastly, once I've gotten all that's required from FTP, is dselect a good method to use for performing the install? Thanks, Ricardo
Unidentified subject!
Hi I would like to have a floating Debian system on my external SCSI HD. At home I have no (network ...yet :) and at work I have a connection through ethenet. I think have resolved all the details except a proper network connection. At install, I said I had network and gave the IP addres of: my host at work, the network, gateway and DNS. However something wrong happens with the email. I can send mail, but I cannot receive any. Sendmail creates huge logs for every bounce (it tries every 30' by default). I can ftp and telenet but other people cannot telnet or ftp into my machine although I modified the /etc/hosts.deny and /etc/hosts.allow Q1) Maybe I should not use the DNS and rout through my own /etc/hosts? Is there any advantage? Q2) Is there any script to do this things being taken by hand ? Q3) Can I use dinstall? That's the script one runs when installing the system for 1st time. I imagine its in the boot and saved a copy before rebooting... Can I use it to REconfigure the net, maybe I missed something during the installation? I notice that modconf is available in sbin/ but what about the other modules related to net configuration? Any net guru out there can help me to configure the system? Maybe not on-line in this list so as to save bandwidth. Thank you, Lazaro [EMAIL PROTECTED] P.S. I read a lot in the Network admin quide, but that was 1 year ago... :-)
LILO vs LOADLIN (was Re: LILO and W95)
Hi The DOS+LOADLIN solution is in my opinion a very practical and safe one. I read much safer than LILO somewhere and some time ago, but I cannot recall why nor if it has changed with the last versions of LILO for which horror histories abound. Anybody knows? There is however at least one situation that none of LILO or SYSLINUX can cope with: The Compaq boxes with a PCI SCSI and or Ethernet card on board. The problem is that Linux cannot address the PCI services on them (Ref: Linus Torvald). This is the case, at least, for the Compaq Deskpro and the high end XL series. There was a page on the WWW for Linux on these last. But...DOS+LOADLIN can cope with it: Compaq provides a DOS driver (luckily Novell Netware has the same problem as Linux :) called MOVEPCI which re-addresses PCI services and exits. Then one can load via MS-DOS LOADLIN. A CONFIG.SYS on top of MS-DOS 5.0 that worked for me is: - Cut here DEVICE=\MOVEPCI.SYS SHEL=\LOADLIN \vmlinuz root=/dev/sda6 ro - Cut here This and all the variants you can imagine like(take them alone or combined) LOADLIN from AUTOEXEC, within a menuitem (DOS 6.xx), many different kernels and/or root on different partitions, with the kernel image on HD or FD (yes, two moderatly large kernels + LOADLIN + MOVEPCI...fit in one FD!) and you can of course pass old the boot parameters you one in a line or (if too long for DOS) in a file. And if in a floppy is readable/transportable from/to any DOS machine around (the same good point of Syslinux used on Debian). I think LOADLIN is a good (and versatile) choice. I prefer it to LILO unless somebody can show me a good reason to not. P.S. Yes, I know that with Syslinux you can fit 3 kernels on one floppy + a tiny editor (I have DOS screen editor of size=4096 bytes!) __ Reply Separator _ Subject: Re: LILO and W95 Author: debian-user@lists.debian.org at cclink Date:02.08.96 07:26 On Thu, 1 Aug 1996, nathan work wrote: ok, i just loaded linux after w95 for the first time. i know very little about linux or unix for that matter and i'm having a real problem - 95 will not 'recognize' LILO, and boots right into 95. i didn't have this problem with 3.1. what i need is for someone to be gracious enough to take me by the hand and show me how to overcome this (to keep w95 from controling what's booted). please email me if you'd like: What I have done is similar to what Susan suggest in using LOADLIN, but I have setup a menuitem in config.sys to handle it. The line I use in the config.sys file is: shell=c:\loadlin.exe c:\vmlinuz root=/dev/hda6 ro This assumes my root file system is on hda6. This way when I boot I have the option presented to me. It is very much like LILO, but is all done through DOS/WIN95 utilities (when I started using linux, I was more comfortable doing it this way). --- Kenny Wickstrom | gnu - a new generation in s/w devel/support [EMAIL PROTECTED] | Linux - a much improved Un*x clone (847)740-4008 | Debian - a Linux distribution setting the #include std-disclaimer |standard for future distributions
Log of reported problems with 1.1.2/2.0.6
It was Re: Debian 1.1.2 NFS Module not loading Re: nfs module doesn't load in 2.0.6 As a Log, this must be a long posting. I just try to find connections between what I think are related problems. --- I did the following experiments: Experiment #1 - On a clean 16MB partition I tried the 1996_7_14 installation disk set (with Linux 2.0.6) which I dowloaded last week from buzz-updates/... - I then got error messages with with undefined symbols when in the Configure the system stage of the installation script. It was difficult to read the scrolled off messages ... and then I was on the installation menu again ---Bruce... would it be possible to generate a log of the installation to trap those errors?, maybe sleep them if no logging is conveniente/possible. - I could finish the configuration, w/ creation of the boot and all that. - I rebooted chose rebooot (in fact halted) the system. - I decided not to use the system in that state (I didn't check how the system would have behaved at run time). I was thinking of mounting that fresh install (even with no root password :-) to investigate the problem later. I had no time yet. Considering that some people is starting to use the kernels 2.0.6 after Debian 1.1.2, I decided to come back and look closer to the problem. Can anybody check this fresh Debian 1.1.2 install problem ...a spare 16MB partition (you could use your swap for a while) will be enough. Just a comment: The disks I used, were under ../buzz-update/.. since Jul 14 but not in ../buzzed-fixed/... (linked to Debian-1.1.1 and stable) untill last weekend (between friday and sunday) when the the tree problem was fixed by Guy Maor. The same disks appeared under the ../stable/... tree under the new name 1996-07-14 and Debian 1.1.2 was released just after that. Guy already posted that there are the same disks. (check postings included below) Experiment #2. - Forget the disk set of experiment #1: I now started from an old Debian 1.1 working system (the same you find under buzz or Debian-1.1 with the kernel 2.0.0) installed with the standard boot dsks of 1996_6_11 - I downloaded dpkg-1.2.11elf and (dselect/dpkg) installed kbd, perl-..., and the kernel-image-2.0.6 from updates/... which was announced together with Debian 1.1.2. Maybe I dowloaded them from stable = Debian-1.1.2 but those are the same now. I was on master.debian.ftp - I reboot the machine (linux 2.0.6) and... ... at boot time I managed to read again the same messages as in experiment #1: ... undefined symbols in .../modules/... undefined symbols in .. /modules/... - One of the lines had the string nfs (Eureka! it coincides with the other reports) I Tried dmesg | more but did not work. ---May I suggest again to redirect 2 last_boot.log That's all. Lazaro P.S. Related postings follow in reverse chronological order This %/%# mail reader (cc-mail for windows) is configured in such a way that I cannot see who the original sender is. Sorry. -- Lazaro D. Salem E-mail: [EMAIL PROTECTED] RF-Rogaland Research Phone: +47 51 87 50 00 P.O.Box 2503, Ullandhaug Direct: +47 51 87 50 65 N-4004 Stavanger, NORWAY Fax: +47 51 87 52 00 On 1996-07-31 04:54 I've recompiled my kernel (and, yes, I've remembered to 'make modules' and 'make modules_install'), but when I boot now, I get an error message saying that it can't find the modules. I'm using Kernel 2.0.6 and modules 2.0.0 Whats wrong? On 1996-07-31 00:32 I get a lot of unresolved symbols when trying to install via NFS from the newest release on ftp.debian.org. trying to do a insmod nfs get a screenful of those too. On Sun, 28 Jul 1996 [EMAIL PROTECTED] wrote: I think that is related to something I noticed today when trying to install Debian 1.1.1 with the installation disks set 1996_7_14 (whatch out! I did not say 1996-07-14 boot disk set which corresponds to the new Debian 1.1.2 just released yesterday). They're one and the same. A user suggested naming them as -MM-DD which is ISO recommended. By the way the mantainer included the version number in the name of the control files so if you dpkg-name -a kernel*.deb you get the funny name kernel-source_2.0.6_2.0.6-0.deb as it happened with version 2.0.0 included in Debian 1.1. That's done on purpose so you can install more than one kernel. Guy -Lazaro Salem (that's me) wrote last Sunday: I think that is related to something I noticed today when trying to install Debian 1.1.1 with the installation disks set 1996_7_14 (whatch out! I did not say 1996-07-14 boot disk set which corresponds to the new Debian 1.1.2 just released yesterday). When configuring the system during the installation I managed to read some header .. modules... missing sorry it was too fast to read, but I realized that there was a conflict between
dselect --- It was: Re[2]: Is buzz-fixed?
I changed the subject of this posting because I want to follow this thread now: On 29.07.96 17:27 Jim [EMAIL PROTECTED] writes: Subject: Re: Is buzz-fixed (- stable- Debian-1.1.x - Debian ) FIXE .. ... Lazaro P.S. It would be nice to have quickstart guide at hand to help Debian newcomers to understand/use dselect. Any idea? The main screen is quite informative, in the select option one can get keystrokes help and that's all you need to know (IMHO, but ok I'm working with it for months now). Erick I am a Debian newcomer (not a Linux newcomer, came over from slackware) and thought the dselect was very overwhelming the first 5 minutes, less overwhelming after the first hour, and figured it out with the onscreen help texts after a few. Agreed. I am thinking in those first 5', ...although, I must confess, it took me longer to feel at ease with dselect :-) MUCH more powerful than anything slackware has. Of course. That's why I asked for a pointer to a dselect's quickstart- like guide, ...and not a pointer to a Slackawre mirror :-). IMHO those 5' _may_ frighten many potential Debian users. I agree that you get used to it,... and even love it! But be honest, and try to remember how did you feel about using Slackware's setup the first 5'`? Now compare it to your dselect 1st experience. I know that may be very difficult to have both a catchy interface and a powerful packaging system, but is not impossible. It just requires work. From what I heard many will agree that dselect can be (and is) overwhelming at first. It might be then useful to make explicit that not so nice feeling and contribute with our feedback to the project. Some questions could help us in the process: - Where were you expecting to find this particular function? - What was there, where you didn't expected it to be? - What were you waiting to get when typing that key? and more generally: - What was confusing with dselect during those 5'? and so on... Here is a list with what I recall from my first experience using dselect: 1) I didn't feel the need (as a newcomer I was) to have so many possibilities to choose the menu options by three different methods (letters, numbers, and cursor keys). Having at most two (keep the cursor keys and numbers please :) would have made it much simpler _to_ME_ as a 1st time user. After those 5', I know that those 3 possibilities exist, but... who cares, I use always the same one, as probably you do. Somebody will argue that flexibiity is a strong features for advanced users I would answer that power users would use dpkg instead. That's the whole point of dselect: hide the complexities (powerfull features) of dpkg under a front-end, namely, dselect. 2) The Help function may be an exception (leave as many routes to it as possible) as many (DOS-Linux converted) might be used to have help on F1 so ... why not? it won't hurt, and it is unobtrusive for those who don't want to use it. The installation Menu of Debian offers it there and it is nice to find things where we expect them to be. 3) Another one: When proceeding with the installation (I don't remeber if it is the same when removing packages) the message Skipping unselected packagename ... Skipping unselected packagename ... scrolls on my screen with a long list. It takes a lot of time (i/o from/to screen is slow, remeber?) and I can hear dselect accessing my HD intermitently (=slow). What about suppressing that printing which doesn't give _me_ any useful information. Again it may give information _to_you_, but remeber, you are not a 1st time user. A --verbose option if you like could be handy (I haven't check in fact). A compromise would be to print the whole list of the unselected packages at the beggining/end of the main proper installation process. 4) This last one is really trivial and more of style concern. In the openning screen I would expect the name and version number of dselect at the top line (one line), maybe the copyright info below and all that well separated from the following Main menu. Presently the name is at the top, then the Menu, and after it the name and version again. You could say: Why? What's wrong with the present placement of those strings? and you have the nice colors too!!. I could give you _my_own_good_reason (I think I have one in fact) but that may not suite you. The idea behind what I am saying is: let's not argue about dselect (there is a alt.dselect.advocacy for that purpose :) I just want to see if we can agree on why this or that style|feature makes dselect look overwhelming during those first 5'. It shouldn't be difficult since many will agree on that 1st impression. -- I think these four comments are enough to begin. An then... what? well...if most of the users agree that this particular feature of dselect is confusing, it wouldn't be difficult for Ian (or even a volunteer) fix that? The idea, I repeat, is try to see if we
Re[2]: Is buzz-fixed (- stable- Debian-1.1.x - Debian ) F
On 29.07.96 17:27 Jim [EMAIL PROTECTED] writes: Subject: Re: Is buzz-fixed (- stable- Debian-1.1.x - Debian ) ... At 10:44 PM 7/26/96 +0200, you wrote: In my opinion (hope I am wrong) the buzz-fixed/ tree under ftp.debian.org:/debian/ and the other directories pointing to it through symlinks (including stable/) do NOT reflect the changes made under buzz-updates/ and therefore is NOT fixed besides its name. Perhaps the mirror isn't up to date yet? (Just guessing). Jim the problem I mentioned was fixed in the meantime, on friday precisely (and maybe minor edges were ironed out during the weekend). That's real fast! ... thank you again Guy for pointing it out in your previous posting today.
Re[2]: Debian 1.1.2 is Released
This is what I found from the debian-announce mailing list Date: 20 Jul 96 18:01 UT Format: 1.6 Distribution: stable Urgency: High Maintainer: Helmut Geyer [EMAIL PROTECTED] Source: procps Version: 1.01a-1 LAzaro __ Reply Separator _ Subject: Re: Debian 1.1.2 is Released Author: debian-user@lists.debian.org at cclink Date:29.07.96 03:24 You are missing important things: Why is procps-1.01a not included? Try a ps alx with debian and you will see. Guy Maor ([EMAIL PROTECTED]) wrote: : Debian 1.1.2 is on the master site. Within a few days, you should see : it on the mirrors. : : Changes from Debian-1.1.1 are: : base-1.1.0-14 : boot-floppies-1.1.1-10 : boot disks 1996-07-14 : kernel-headers, kernel-image, kernel-source 2.0.6 : xosview 1.3.2-4.1 : : Changes from Debian-1.1 are the above and: : dpkg 1.2.11 : kbd 0.91-3 : perl, perl-debug, perl-suid 5.003-2 : qpopper 2.1.4-3 : : For more information on what bugs these updates fix, see : Debian-1.1-updates/ChangeLog. : : Debian-1.1.2, also reachable as Debian-1.1-fixed, stable, and : buzz-fixed, is a symlink copy of Debian-1.1 with the updates from : Debian-1.1-updates applied. : : : Guy :
Re: Seg faulting on installation of base...
I got also a seg fault but may be because I was using the VC #2 to mount other partitions floppy HD msdos and Linux ext2 :-) But that happen before installing the system (I was just trying yo copy base1_1.tgz to avoid installing from floppies. In a second attemt I succeeded. That was today. A week ago I also tried and I got error readiong from the diskettes as you describe ( i did not know that that was a seg fault (today's experience was more wexplicit as I could read the message on the terminal #2). I do not know what happened yet. I just want to tell you that doubled checked the diskettes and they were legible. I tried again with new diskettes and succeeded. I tried again wwith the old ones and no problem. In summary: try and try and try. Maybe is something in the kernel whichwhere small things might not have been ironed out yet. Try this if you have time to experiment: Boot with the boot disk (I used the June 16 - set) when asked for inserting the root, trry inserting one of the base set ( I did it by mistake with #3). No problem, Linux (The kernel is in charge yet!!) see the problem and asks you politely to insert the root disk (with slightly diff message compred to the 1st time so things are going on internally). Ok then insert the root disk. pif! kernel panic! I wrote down the codes I'll send to linux later (I have to work now.. sorry) For my config (standard: ISA i486-DX33 + 16MBRAM + AHA1542 + 2 SCSI disks no NIC) I could repeat the kernel 3 times did not try more :-) I am afraid we'll have to wait for a while with 2.0.0 if robustness is your main concern. or... keep trying. just read that deb 1.1.2 was realesed. Check the new release is under stable/ (see my previous post) and coincied with buzz-updates/ Happy hacking! lazaro __ Reply Separator _ Subject: Seg faulting on installation of base... Author: debian-user@lists.debian.org at cclink Date:27.07.96 23:48 Ok, I'm installing Debian-1.1-fixed from 3.5 floppies, and everything works just fine until it actually starts to install the base system. Installation prompts me for the first disk, I put it in, it starts installing and the gives me a Segmentation Fault. That's it. I've gotten it to do as much as 240K, but it usually stops around 60-100K. Then, of course, it wants me to try again. I'm running a Pentium 100 with 40 megs of ram, and I'm installing onto a 290 meg partition. I do have a 16 meg swap partition set up, and I'v tried everything from redoing the floppies to using a different rawriter... li'l help, please? ###Christian D. Jones Math, CompSci, Music, y'know--whatever... # #Harvey Mudd College Linde 212--x71443, (909)607-1443 WI ###340 E Foothill Blvd http://red-october.st.hmc.edu/ BS #Claremont, CA 91711 Stupid--the Team, not the movie. TR
Re[4]: 1.1 problems
Well, a simple test to see whether (whichever) Linux kernel can recognize the busmouse is by reading the booting screeen. If the busmouse detection has been compiled in you should see at the very beggining just a few lines after the Loading ... : Bus mouse detected and configured If your screen flies (as mine .-) in front of you try: # dmesg | grep mouse As you will see Debian 1.1 and 1.1.1 did not have the busmouse supported by the kernel (0.93R6 kernels 1.2.13 did). A pity because I have one too :-). Under buzz-updates/ you should find all the changes made to 1.1 --they were not included in buzz-fixed/ -Debian-1.1.x/ -stable/ as of last friday however (see my previous post). You should also find under ../special buzz-updates/special-kernels/ 6 kernel config files with different options set. Among those different compilation options, guess what... the configuration of busmice. Most of them either are such that the CONFIGURE_BUSMICE (or something like that) is not set, or is just set as loadable module. In the installation scripts of debian installations set (june 16 and July 14) there was no mention about busmice modules. I agree. I haven't checked out Debian 1.1.2 which has just been released. happy hacking :-) Lazaro __ Reply Separator _ Subject: Re: Re[2]: 1.1 problems Author: Mark Phillips [EMAIL PROTECTED] at cclink Date:28.07.96 04:05 Hi Rick, (Or are you Mark? :-) I am in fact Mark. DO you know if one can do somethiong similar to be able to recognize the busmouse? I am not sure if busmice drivers can be loaded as modules. Again 0.93 (linux 1.2.13) recognized at boot time. It not the case with 1.1 or 1.1.1 unsing Linux 2.0.0 and 2.0.6 respectively. I cannot check it on my system because I am on the road without my box. And unfortunately I am not able to help you. I imagine busmice drivers would be loadable as modules, but it is a guess. Try emailing to debian-user@lists.debian.org Sorry I am not able to help further. Mark.
Re[2]: Seg faulting ....
Hi again Sorry for the typos in my previous posting. Subject: Re: Seg faulting on installation of base... Author: debian-user@lists.debian.org at cclink Date:28.07.96 18:02 Errata: or... keep trying. just read that Debian 1.1.2 was realesed. PLease check that the new release is under stable/ (see my previous post) and that those files are the same as those under buzz-updates/ But linux instead of Linus was the most offensive one but not the only :-) My sincere apologies for those who speak and write proper English and of course to Linus. Happy hacking! lazaro
Re[2]: Is buzz-fixed (- stable- Debian-1.1.x - Debian ) F
Nopp... it was not a mirror. As I said in my post I was pointing to ftp.debian.org. If you check there, there has been som reorganization during Friday and Saturday by Maor. Read a previous posting by Guy announcing the release of 1.1.2. Follow this thread... I am checking things now and something does not fit. the files in question (Changelog under updates) at ftp.debian.org are not readable now (maybe something is working on them?) Happy Hacking. Lazaro __ Reply Separator _ Subject: Re: Is buzz-fixed (- stable- Debian-1.1.x - Debian ) FIXE Author: debian-user@lists.debian.org at cclink Date:27.07.96 06:39 In my opinion (hope I am wrong) the buzz-fixed/ tree under ftp.debian.org:/debian/ and the other directories pointing to it through symlinks (including stable/) do NOT reflect the changes made under buzz-updates/ and therefore is NOT fixed besides its name. Perhaps the mirror isn't up to date yet? (Just guessing). P.S. It would be nice to have quickstart guide at hand to help Debian newcomers to understand/use dselect. Any idea? The main screen is quite informative, in the select option one can get keystrokes help and that's all you need to know (IMHO, but ok I'm working with it for months now). Erick
Re: Debian 1.1.2 is Released
As Guy says, Wait a few days before downloading. Things are not yet (IMHO) completely fixed _everywhere_ or at best slightly confusing. To make it clear, and as Guy announced, the new boot set is: Changes from Debian-1.1.1 are: base-1.1.0-14 boot-floppies-1.1.1-10 boot disks 1996-07-14 kernel-headers, kernel-image, kernel-source 2.0.6 xosview 1.3.2-4.11996-07-: Please, in case you're in doubt, remember: The 1.1.2 is under the name 1996-07-14 and not 1996_7_14 (this last is the one that since 2 weeks ago under buzz-updates/ without being stable/ or friends being properly linked to it). The files corresponding to the announced 1.1.2 release are time-stamped on Friday or Saturday 27 (os! and even today...I am looking at them right now... As I thought somebody was fixing things not so long ago now) here is what I see _now_ ftp://ftp.debian.org/debian/buzz-fixed/disks-i386/ Up to higher level directory .message Sun Jul 14 14:18:00 1996 Symbolic link 1996-07-14/ Sat Jul 27 00:48:00 1996 Directory 1996_6_16/Sat Jul 27 00:48:00 1996 Directory READMESun Jul 14 14:18:00 1996 Symbolic link current Sat Jul 27 00:48:00 1996 Symbolic link install.html Sun Jul 14 14:18:00 1996 Symbolic link make-floppies Sun Jul 14 14:18:00 1996 Symbolic link special-kernels/ Sat Jul 27 00:48:00 1996 Directory And for those of you who need the special kernels (look at the config-[0-5] files ) ftp://ftp.debian.org/debian/buzz-fixed/disks-i386/special-kernels/ boot1440_2.0.5-0.bin Sat Jul 27 00:48:00 1996 Symbolic link boot1440_2.0.5-1.bin Sat Jul 27 00:48:00 1996 Symbolic link boot1440_2.0.5-2.bin Sat Jul 27 00:48:00 1996 Symbolic link boot1440_2.0.5-3.bin Sat Jul 27 00:48:00 1996 Symbolic link boot1440_2.0.5-4.bin Sat Jul 27 00:48:00 1996 Symbolic link boot1440_2.0.5-5.bin Sat Jul 27 00:48:00 1996 Symbolic link config-0 Sat Jul 27 00:48:00 1996 Symbolic link config-1 Sat Jul 27 00:48:00 1996 Symbolic link config-2 Sat Jul 27 00:48:00 1996 Symbolic link config-3 Sat Jul 27 00:48:00 1996 Symbolic link config-4 Sat Jul 27 00:48:00 1996 Symbolic link config-5 Sat Jul 27 00:48:00 1996 Symbolic link kernel-image-2.0.5... Sat Jul 27 00:48:00 1996 Symbolic link kernel-image-2.0.5... Sat Jul 27 00:48:00 1996 Symbolic link kernel-image-2.0.5... Sat Jul 27 00:48:00 1996 Symbolic link kernel-image-2.0.5... Sat Jul 27 00:48:00 1996 Symbolic link kernel-image-2.0.5... Sat Jul 27 00:48:00 1996 Symbolic link kernel-image-2.0.5... Sat Jul 27 00:48:00 1996 Symbolic link Before you rush, check if your kernel on the installation boot disk (is a DOS FAT remember? has the around Jul 14 date. If so. Wait a few days a download the new ones. I heard and noticed that 2.0.0 had some buggy kbd but maybe some other important things were broken in it (refer to Changelog and _ask_!) As far as I am concerned, I will wait a few days before upgrading _anyway_. Thanks for the job folk of Debian. A suggestion (or a wish): it would be nice if _all_ the Debian releases, were announced through the debian-announce and comp.os.linux.announce Happy hacking! Lazaro P.S. If you insist I can prepare a longer posting with more details but don't panic. Just wait until the mantainers work it out, and I am sure they have done a lot of the fixing as far as the tree structure is concerned. Notice that the opening message when pointing your browser to ftp.debian.org/debian has been modified last friday. As I write this PS ls-lr.gz is not accessible. It's yesterdays version (with the fixes done today not reflected in it) so by the time you read this you can maybe see the new one and just forget all my commments... I hope. __ Reply Separator _ Subject: Debian 1.1.2 is Released Author: debian-user@lists.debian.org at cclink Date:27.07.96 05:59 Debian 1.1.2 is on the master site. Within a few days, you should see it on the mirrors. Changes from Debian-1.1.1 are: base-1.1.0-14 boot-floppies-1.1.1-10 boot disks 1996-07-14 kernel-headers, kernel-image, kernel-source 2.0.6 xosview 1.3.2-4.1 Changes from Debian-1.1 are the above and: dpkg 1.2.11 kbd 0.91-3 perl, perl-debug, perl-suid 5.003-2 qpopper 2.1.4-3 For more information on what bugs these updates fix, see Debian-1.1-updates/ChangeLog. Debian-1.1.2, also reachable as
Re[2]: X and mice problems ?
Shaya Potter [EMAIL PROTECTED] says: On Fri, 26 Jul 1996, David J. Evans wrote: I've recently switched from RedHat to Debian 1.1 and am experiencing problems with X. I had previously run X successfully on Redhat and so assumed that there would be no problem. ... Fatal server error: Cannot open mouse (No such device) __ David J. Evans AMS, Virology Research Group, The University of Reading Whiteknights, P.O. Box 228, Reading RG6 6AJ Tel : +44 (0)118 9318893 Fax : +44 (0)118 9316537 http://skpc10.reading.ac.uk/ The kernel you are using might not have ps/2 mouse support compiled in, try remaking and when you configure it, include mouse support (it's under the character device setting). Another possibility, even though it doesn't appear so from you error message, could be if you are running gpm. ... Shaya Potter [EMAIL PROTECTED] It is not gmp. Debian runs a script that kills gpm before you start X ..clever hmm!) so it is definitely the compiled kernel you are using the cause of the error. Check under special-kernels for a new kernel to boot from, or build a new one with mouse support. Alternatively (the simplest maybe), from the Config files to build the kernel I found in Debian (see release stable = 1.1.2) it seems that the 2.0.x kernels support loadable drivers (i.e., module) for the busmice, but I could not find those for the busmice. You check uner /lib/modules/2.0.x/... I think. Hope it helps, Lazaro P.S. If your kernel supports the Bus Mouse you see it at boot time Try dmesg | grep mouse
Re: nfs module doesn't load in 2.0.6
I think that is related to something I noticed today when trying to install Debian 1.1.1 with the installation disks set 1996_7_14 (whatch out! I did not say 1996-07-14 boot disk set which corresponds to the new Debian 1.1.2 just released yesterday). When configuring the system during the installation I managed to read some header .. modules... missing sorry it was too fast to read, but I realized that there was a conflict between the kernel and the configuration at the level kernel module interaction. Avoid using the packages kernel-source_2.0.6-0.deb (image and headers are based/related to these source) originally time stamped around July 14/15. By the way the mantainer included the version number in the name of the control files so if you dpkg-name -a kernel*.deb you get the funny name kernel-source_2.0.6_2.0.6-0.deb as it happened with version 2.0.0 included in Debian 1.1. Can this be considered a bug report I don't dare to :-) Noticed that the new kernels are 2.0.5 and not 2.0.6 (it would be nice to know why this step back ...:-) Happy hacking, Lazaro __ Reply Separator _ Subject: nfs module doesn't load in 2.0.6 Author: debian-user@lists.debian.org at cclink Date:27.07.96 06:11 I just upgraded from 2.0.0 to 2.0.6 including modules and now I get many undefines when installing nfs module. like: nfs_mknod undefined nfs_sillyrename_cleanup undefined . .. ... Loading failed! The module symbols (from linux-2.0.6) don't match your linux-2.0.6 Any way to fix this? Other mods load fine. the nfs loaded fine in 2.0.0 Thanks for any info, Jim === Jim Gerace Senior Systems Engineer email: [EMAIL PROTECTED] www: http://www.kasinet.com
Re: impact of Caldera announcements
Maybe you want to check a related article in the August issue of the Linux Journal (www.ssc.com) or point your browser to www.lasermoon.com for the Linux FT 1.2 distribution. cheers, lazaro __ Reply Separator _ Subject: impact of Caldera announcements Author: debian-user@lists.debian.org at cclink Date:28.07.96 22:00 Hello, I was reading that Caldera has some very important announcements regarding the linux system; posix, and standards. does anyone here have any thoughts on how this will impact the direction of the debian project? allan bart There is no Life, Truth or Substance in Matter Page 468 Science Health
Is buzz-fixed (- stable- Debian-1.1.x - Debian ) FIXED?
Hi, This is more for the mirror mantainers... but also for the impatient users: In my opinion (hope I am wrong) the buzz-fixed/ tree under ftp.debian.org:/debian/ and the other directories pointing to it through symlinks (including stable/) do NOT reflect the changes made under buzz-updates/ and therefore is NOT fixed besides its name. Or is it maybe that Debian-1.1.1 should not contain the updates to the June 16th 1.1 release in contradiction with the logging message? Something doesn't fit. For example, here is what you would get if you point your browser to ftp://ftp.debian.org/debian/buzz-fixed/disks-i386 Current directory is /debian/buzz-fixed/disks-i386 Up to higher level directory .message Sun Jul 14 14:18:00 1996 Symbolic link 1996_6_16/Sun Jul 14 14:18:00 1996 Directory READMESun Jul 14 14:18:00 1996 Symbolic link current Sun Jul 14 14:18:00 1996 Symbolic link install.html Sun Jul 14 14:18:00 1996 Symbolic link make-floppies Sun Jul 14 14:18:00 1996 Symbolic link special-kernels/ Tue Jul 23 11:10:00 1996 Directory while pointing to buzz-updates/... you will get the newer updated files: Current directory is /debian/buzz-updates/disks-i386 Up to higher level directory 1996_7_14/Tue Jul 23 11:10:00 1996 Directory special-kernels/ Tue Jul 23 11:09:00 1996 Directory I am sure there may be other tests one could do to confirm that this is the problem. This is the simplest one I found (it took me more to find the problem than to write this letter ;-) What confused me was that .message under debian states that stable/ points to the latest Debian-1.1.x, while in fact stable/ points to buzz-fixed/ (which turned out not to be fixed :). Hope this helps. Enjoy Debian GNU/Linux! :-) Lazaro P.S. It would be nice to have quickstart guide at hand to help Debian newcomers to understand/use dselect. Any idea? -- Lazaro D. Salem E-mail: [EMAIL PROTECTED] RF-Rogaland Research Phone: +47 51 87 50 00 P.O.Box 2503, Ullandhaug Direct: +47 51 87 50 65 N-4004 Stavanger, NORWAY Fax: +47 51 87 52 00
