May 2001 - openSUSE Users - openSUSE Mailing Lists

Handling unknown users in Email Server II
by Mark Knecht 09 May '01

09 May '01

Hi, I can't find any documentation on the web site or in the manual. In SuSE Email Server II, what happens to mail for unknown users? (I.e. - user1(a)domain.com, where domain.com is being received by Email Server II, but user1 is not defined.) Does it bounce? Can I set up a collection basket for all email sent to the domain that doesn't have a specific matching user account? Thanks, Mark

2 1

[PCMCIA] RFI HOT ISDN 100cc
by Oliver Ob 09 May '01

09 May '01

Hi folks, I found no way to get the above named (see subject) to work, it has been recognized as "Sedlbauer Speedstar" under Windoze and does its job well there, but actually however, it #is# not that card, and I am stuck in my tries to get the beast to work for me... looks like rodeo somewhay or what have you! :-) the problem I have is as follows (quoted from boot): " Loading ISDN drivers ... /dev/isdnctrl: No such device PCMCIA: Starting services: PCMCIA: using scheme: SuSE cardmgr[129]: starting, version is 3.1.17 PCMCIA: cardmanager is running cardmgr[129]: watching 2 sockets cardmgr[129]: initializing socket 0 ... snip ne2000 working etc. ... done modprobe: modprobe: Can't locate module ippp0 DHCLIENT: The device ippp0 is not available at the moment. DHCLIENT: Please check if the driver is set up correctly. /dev/isdninfo: No such device Starting isdn4linux on device ippp0 /dev/isdninfo: No such device /sbin/init.d/rc2.d/S05i4l: ippp0 doesn't exist in /proc/net/dev Check ISDN hardware configuration and activate " ok now that the ne2000 works fine, how can I most effectively approach this ISDN problem? Has anyone an UNDERSTANDABLE step-by-step help for my problem? I have scanned all the howtos on PCMCIA but cannot see any help on how to get the RFI HOT ISDN 100cc to work under linux, the rfi service has not answered yet and sedlbauer says "it is RFi..." so now?????? -- *º¤., ¸¸,.¤º*¨¨¨*¤Oliver@home*º¤., ¸¸,.¤º*¨¨*¤

1 0

Re: mkbootdisk for SuSE?
by Jim Osborn 09 May '01

09 May '01

"S.Toms" <smotrs(a)mindspring.com> writes: >jo>The RedHat utility is just a nice shell script, >jo>easy enough to hack as necessary for the SuSE environment. > > I use the following within my .alias file to do similar > >function mkbootdisk { > fdformat -n /dev/fd0h1440 > if [ -f /boot/vmlinuz ]; then > echo bootdisk: Kernel found, copying to bootdisk... > cp /boot/vmlinuz /dev/fd0 > else > echo bootdisk: Enter location of kernel > read kpath > if [ "$kpath" ]; then > if [ -f $kpath ]; then > echo bootdisk: Kernel found, copying to bootdisk... > cp $kpath /dev/fd0/vmlinuz > else > echo bootdisk: Unable to locate $kpath... > fi > else > echo bootdisk: Unable to locate kernel... > fi > fi >} Thanks for sharing that script, S. The really interesting capability of the RedHat script is its making of the initrd image, which is necessary if, for example, the kernel uses a modular scsi driver and can't get to the hard disk without the initial ramdisk. I do plan to hack that RedHat script eventually, if only as a learning experience to better understand initrd. But for now, I've followed the good advice of folks here and on another list and taken the easy way out. First, eliminate the need for initrd: compile that scsi driver right into the kernel. After all, when would it ever get unloaded? Lastly, to allow booting with my "backup" image, the SuSE distro kernel with its modular scsi and accompanying initrd: let lilo handle the details. I made a special bootfloppy lilo conf file, "lilo-floppy.conf," containing this: vga = normal read-only prompt timeout = 50 boot = /dev/fd0 map = /floppy/lilo-map compact image = /boot/vmlinuz root = /dev/sda2 label = linux image = /boot/vmlinuz-backup root = /dev/sda2 label = backup initrd = /boot/initrd To make the bootdisk, mount a clean floppy on /floppy and copy /boot/chain.b to it. Then run lilo -C lilo-floppy.conf unmount the floppy. Enjoy. To see all the labels, hit <TAB>. I'm indebted to Soren Jacobsen on another list for this idea. FWIW, Jim

1 0

Re: [SLE] vmware 2.0.4
by Purple Shirt 09 May '01

09 May '01

Well line 2 was a comment. I went ahead and deleted the comment line. No go still. /lib/modules/2.4.2-4GB/build/include/linux/config.h: At top level: /lib/modules/2.4.2-4GB/build/include/linux/config.h:2: parse error before `1' /lib/modules/2.4.2-4GB/build/include/linux/config.h:4: undefined or invalid # directive /lib/modules/2.4.2-4GB/build/include/linux/config.h:8: undefined or invalid # directive /lib/modules/2.4.2-4GB/build/include/linux/config.h:13: undefined or invalid # directive /lib/modules/2.4.2-4GB/build/include/linux/config.h:16: undefined or invalid # directive /lib/modules/2.4.2-4GB/build/include/linux/config.h:20: undefined or invalid # directive . . . I don't know if the file is wrongly formatted or something. Well there is a lot of crap output and then this: /lib/modules/2.4.2-4GB/build/include/linux/reiserfs_fs_sb.h:235: storage size of `j_join_wait' isn't known /lib/modules/2.4.2-4GB/build/include/linux/reiserfs_fs_sb.h:253: storage size of `j_journal_list' isn't known /lib/modules/2.4.2-4GB/build/include/linux/sched.h:211: storage size of `mmap_sem' isn't known .././linux/driver.c:93: storage size of `linuxState' isn't known make[2]: *** [driver.o] Error 1 make[2]: Leaving directory `/tmp/vmware-config3/vmmon-only/driver-2.4.2-4GB' make[1]: *** [driver] Error 2 make[1]: Leaving directory `/tmp/vmware-config3/vmmon-only' make: *** [auto-build] Error 2 make: Leaving directory `/tmp/vmware-config3/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please have a look at "http://www.vmware.com/download/modules/modules.html". Execution aborted. mk >From: Steven Hatfield <ashari(a)knightswood.net> >Reply-To: ashari(a)knightswood.net >To: "Purple Shirt" <purpleshirt(a)hotmail.com>, suse-linux-e(a)suse.com >Subject: Re: [SLE] vmware 2.0.4 >Date: Wed, 9 May 2001 09:24:38 -0400 > >On Tuesday 08 May 2001 08:15 pm, Purple Shirt wrote: > > Thanks for the reply. I copied the files to /usr/src/linux/include/linux > > > > Got me a step further: > > > > /lib/modules/2.4.2-4GB/build/include/linux/config.h:2: unterminated > > character constant > >This usually means that you have a string that is missing the double quotes >at the end, so open up config.h at line 2 and check for something that >looks >like: > >#define SOMECONST "some text > >note the missing double quote at the end. Just add the double quote and try >to compile again. > >The rest of these errors are ancilliary to the first one. > >Good luck! >-Steven > > > make[2]: *** [driver.d] Error 1 > > make[2]: Leaving directory > > `/tmp/vmware-config1/vmmon-only/driver-2.4.2-4GB' make[1]: *** [deps] >Error > > 2 > > make[1]: Leaving directory `/tmp/vmware-config1/vmmon-only' > > make: *** [auto-build] Error 2 > > make: Leaving directory `/tmp/vmware-config1/vmmon-only' > > Unable to build the vmmon module. > > > > For more information on how to troubleshoot module-related problems, >please > > have > > a look at "http://www.vmware.com/download/modules/modules.html". > > > > Execution aborted. > > > > > > > > From: Lenz Grimmer <grimmer(a)suse.de> > > > > >To: <suse-linux-e(a)suse.com> > > >Subject: Re: [SLE] vmware 2.0.4 > > >Date: Tue, 8 May 2001 10:54:36 +0200 (CEST) > > > > > >On Sat, 5 May 2001, Purple Shirt wrote: > > > > Ok so you finally installed lx_suse24 from the 7.1 tree. Remember >the > > > > kernel packages in the update tree are older. Now you figure vmware >is > > > > ready to get done installing. But no SuSE calls its kernel 2.4.2-4Gb > > > > (ver 11) but it's kernel from source is 2.4.2 (SuSE-6)and vmware > > > > chokes. > > > > > >See the reasoning above. All files that need to be replaced to properly > > >build the kernel are in /boot: vmlinuz.autoconf.h, vmlinuz.config and > > >vmlinuz.version.h. vmlinuz.autoconf.h and vmlinuz.version.h. have to be > > >copied into /usr/src/linux/include/linux/{version,autoconf}.h Now the > > >compilation should do fine. > > > > _________________________________________________________________ > > Get your FREE download of MSN Explorer at http://explorer.msn.com > >-- >To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com >For additional commands send e-mail to suse-linux-e-help(a)suse.com >Also check the FAQ at http://www.suse.com/support/faq and the >archives at http://lists.suse.com > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com

2 1

Re: [SLE] Where are newer 2.4.x kernels
by Thibaut Cousin 09 May '01

09 May '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Actually, I'm now struggling with the fact that after doing the 2.4.2 > binary update, the network driver (8139too.o) can't detect the network > card, and so I've lost my network connection. (I'm sending this very post > from a different machine.) And so far I haven't succeeded in reverting the > binaries to 2.4.0 either, so my next tack is to work from the kernel > sources and recompile. That has the advantage of stripping out lots and > lots of unneeded stuff, since the default kernel is configured to include > almost everything at least as a module. I think I know where this comes from. Your network card driver was loaded as a module. I guess the module was in initrd. Here is how recreate the initrd file everytime you install a new kernel : 1. Install the new kernel. 2. Go into /boot. There you must have vmlinuz_24 and initrd_24. 3. Type the following : mk_initrd -k vmlinuz_24 -i initrd_24 4. Rerun LILO with the command "lilo" and reboot. That's it ! By the way, can the SuSE developers add a post-install script to the RPM file to run mk_initrd automatically ? - -- Thibaut Cousin email : cousin(a)in2p3.fr web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6+Vbjv1vqsTa1E4oRAsJwAJ9JWnbC6sxedEdXR5yFb4DKy1DQDwCglUsS RiwxOPIC3Wy/WsJ7kMdrL24= =RGks -----END PGP SIGNATURE-----

1 0

Re: [SLE] [OT] Microsoft maldesign and drive letters
by Paul Abrahams 09 May '01

09 May '01

peter hollings wrote: > Paul -- > > Good points. But unless I'm mistaken, the plot gets deeper. Suppose you've > just added a new HD (as I have) because you've run out of space. Further, I > wanted to re-allocate my files for performance and other reasons: a WinOS > partition, swap partition, programs partition and a user files partition > (all in addition to my SuSE partitions). This seems to leave me with a huge > problem with my Windoze registry: everything in the registry will point to > C: and there's no way I have yet figured out how to move my files around and > simultaneously update the registry other than reinstalling everything!! This is really OT, we know, but ironically enough, the SuSE list seems to be one of the best places around for irreverent but useful Windows advice. I've observed that for some programs, but not MSWord in particular, if you move them, Windows makes an attempt to update its shortcuts and registry to point to the new location. So before the Grand Upheaval, you might try moving one program you *can* reinstall to a different drive and see what happens to it, just as an experiment. My guess is that you'll never be able to move Office, though; I think that its ownership verification tests will prevent that. > I > understand PartitionMagic has a feature called MagicMover, but as far as I > can tell it only moves whole partitions (and not files within a partition) > while updating the registry. It can do drive letter switches without actually moving anything, but it can't treat different parts of the content of a partition differently. > Of course, with Linux this problem seems to be > easily resolved by simply copying files to their new partitions and > reassigning the partitions/mount points. Of course, indeed! The drive letter fiasco goes back to early DOS days when machines (fancy ones at that!) had two floppy drives, A: and B:. To be fair, though, Unix has its own bits of useless history: the choice of 8 as the default tab spacing because that was handy for some long-bygone DEC assembly language. Totally inappropriate for C, C++, or Java, of course. For other stone-age features, look at the man page for stty. Or contemplate the terms "console" and "core dump". Paul

1 0

Re: [SLE] [OT] Rebuilt computer just beeps
by Paul Abrahams 09 May '01

09 May '01

Thanks to all for the pointers to the beep codes. Alas, it didn't help; it's an Award bios and a no-name motherboard. And none of the descriptions of beep codes mention continual, regular beeping; they all describe groups of beeps or sequences of up to 11 single beeps. This guy beeps until I shut him off. The motherboard has slots for both DIMMs and SIMMs. I've tried using a 128MB DIMM from another computer but couldn't seem to get it to seat properly. (The original 32MB DIMM I was trying is probably bad, since the other [working] computer didn't recognize it.) I'm thinking of trying to pick up a pair of SIMMs (which is what was there when I last used the board), but I don't want to waste my money on SIMMs for a board that wouldn't run anyway. So perhaps I should turn the question around: if you start up a motherboard with no memory, is it likely to emit continual regular beeps? Paul

6 7

Re: [SLE] lprng and lprold
by Andrei Verovski 09 May '01

09 May '01

>Hello, > > I've noticed a problem with lprng. It does not happen all the time, and >I'd >like to know if some of you have it too... > Sometimes after (successfully) printing something the lp daemon stops >working. It is still in memory, its status is still "running", but when I >print something else with the lpr command I get a "printer not ready" >message. I have to stop/restart the lp daemon by hand... > This happened on three machines with local parallel printers, but never >happened at my work (the printers are networked). > This does not happen with lprold. Any comment ? I had the same with lpr old, until I re-configured printers using YaST2. Andrei

2 1

nics modules
by stephane parenton 09 May '01

09 May '01

hi all ! I've a slight problem... I'm trying to set-up a gateway. I've taken an old computer (486 DX2/66) that has 2 nics (one token ring and one ethernet) to do this... this computer ran fine with the 2 nics under RH 6.2. I changed the hard drive, and started to install a SuSE 7.0... the first problem is to find the appropriate modules.... I've found a smc ultra module on a 6.4 module disk but not on the 2 modules disks of the 7.0, but it won't pass, even with the rh6.2 parameter (io and irq) found on conf.modules). The problem is different with the tropic card, because the module exists, but won't pass either, even with the parameter found... So what could be wrong ?... Am I missing something big ?... TIA Stephane Parenton

1 0

SuSE 2.4.2 kernel: Associated tpctl package?
by Steven Augart 09 May '01

09 May '01

I've been running 7.1 with the SuSE packaged 2.4.2 kernel update on my machines. Ran into trouble with the IBM Thinkpad 600: The ``tpctl'' package only provides modules in /lib/modules/2.4.0. This is not the modules directory used by any of the 7.1 releases or updates of the k_deflt* package(s). The CD's k_deflt_24.rpm uses /lib/modules/2.4.0-4GB. The CD's k_deflt.rpm uses /lib/modules/2.2.18. The SuSE-Updated updated k_deflt_24.rpm uses /lib/modules/2.4.2-4GB. I tried just copying the tpctl modules from /lib/modules/2.4.0 to the other directories; of course, it didn't work because the kernels were compiled with different symbol tables. Then I tried doing a build from the tpctl source RPM, with ``rpm -bc''. Another miserable failure; get the error message make[1]: Entering directory `/usr/src/packages/BUILD/tpctl_1.0/tpctl' gcc -L../lib -I../include -Wall -Wcast-align -Wstrict-prototypes -O2 -Wno-uninitialized -DLINUX -DVIAGRA -o tpctl.o -c tpctl.c tpctl.c:46: term.h: No such file or directory make[1]: *** [tpctl.o] Error 1 Has anybody built modules for the stock SuSE 2.4.0-4GB, 2.2.18, or 2.4.2-4GB? By the way, I thought I would provide such myself. So I tried to build the SuSE 2.4.2-4GB directly from the sources installed by SuSE-Update/7.1/d2/lx_sus24-2.4.2.SuSE-5.i386.rpm. I did not get quite the same kernel out as the SuSE-Update k_deflt24 one; here is an extract from the differences in the System.map: --- System.map-2.4.2-4GB-distrpm Fri Mar 2 04:14:14 2001 +++ System.map-2.4.2-rebuilt-4GB Sat Apr 7 19:53:41 2001 @@ -175,62 +175,62 @@ c010a9c0 t mark_screen_rdonly c010aa28 T sys_vm86old c010ab0c T sys_vm86 -c010ac08 t do_sys_vm86 +c010ac14 t do_sys_vm86 c010acfc t do_int c010ae18 T handle_vm86_trap c010aef0 T handle_vm86_fault c010b644 t irq_handler c010b694 t do_vm86_irq_handling -c010b910 t putreg +c010b900 t putreg +c010b9b0 t getreg +c010ba04 T sys_ptrace So, I'm willing to build the proper RPMs for others, but I don't want to do that if I can't even reproduce the distributed kernel. Any help? --Steve Augart

3 2