Re: multiple smarthosts with exim
On Fri, Feb 02, 2001 at 04:46:55PM +0100, Michel Dänzer wrote: > > > Has anyone managed to have exim try to forward messages to more than one > smarthost? I've tried several things like multiple smarthost: entries, giving > several hostnames seperated by colons in one entry, etc. No luck so far. It > just tries the first one and freezes the message if it fails. > > I am also interested in how to manage multiple smarthosts. In addition, I would like to know how to setup authenticifaction for each smarthost and how to direct specific messages from specific senders to different smarthosts. I have posted a similar question of www.exim.org's mailing list just recently and have recieved no response. -- wcrowshaw
Regarding 7500 debian install
Thanks for letting me ask you several questions. And I will cc them to debian-powerpc. So here they are: 1) Do you have X up and running? 2) Do you use /dev/ttyS0 for your modem ppp connection or do you use /dev/cua0? 3) Have you had any success running diald? I'm sure I have other questions, but this is just a start. Obviously, for my question, you can deduce that I have problems with my 7500 with regard to X, pppd, and diald. I'm running potato, kernel 2.2.17 and attempting to use X 3.3.6-10. Thanks once again. -- wcrowshaw On Wed, Jan 31, 2001 at 01:59:56PM -0500, Daniel Eisenbud wrote: > Sure, go ahead. I'd suggest that you CC the list in the process so that > other people on the liist (and reading the archives later) get the > benefit too, but either way. > > -Daniel > > On Tue, Jan 30, 2001 at 06:17:22PM -0500, [EMAIL PROTECTED] <[EMAIL > PROTECTED]> wrote: > > I see from this post that you are running Debian on a 7500 like me. If you > > don't mind, could I ask you a couple of questions about your setup and > > see if you have experienced some of the same problems I have experience? > > > > -- > Daniel E. Eisenbud > [EMAIL PROTECTED]
Question about X on 7500...
Amazingly I finally got X (3.3.6) to work on my 7500. All I did was use an altered version of an XF86Config file from my LinuxPPC install. I also used the xservers they supply with their distribution: xpmac and XFree68_FBDev. Both xpmac and XFree68_FBDev work, but for some reason I have no mouse support on my xpmac. XFree68_FBDev is somewhat fuzzy, but it has a mouse. So what do you think is wrong with the potato binary of X 3.3.6 shipped with Debian powerpc? Could you recall what you did to get Debian's X binary to run on on your 7500? Thanks, -- wcrowshaw
Re: modem not working
I'm running debian potato with kernel 2.2.18 and pppd 2.2.11 on a PowerMac 7500 with a SupraExpress 56k. I had a problem with the /dev/ttyS0 device that I was using for my modem. It would dial up but it just never could establish a pppd connection. Finally tried the old /dev/cua0 and now it works. I don't really understand why though. I think it is somehow related to the modem and the mac 8-pin serial port. Using /dev/cua0 could help, but then again it might not be supported in kernel 2.4.1. If who need to know how to create /dev/cua0, let me know and I will tell you how. Hope this helps somewhat. On Sun, Feb 11, 2001 at 04:56:49PM +0100, Sebastiaan wrote: > Hi, > > I am new to Debian on PowerMac, so I hope my question will be a piece of > cake for you. > > I have a powermac 7300, debian potato, fresh compiled kernel 2.4.1 and a > supraexpres 33.6 modem. > > The problem: I can not connect the internet. I can call my ISP with > minicom and everything seems to be ok, but when calling in with pon or > wvdial, pppd stops. It seems from the logfiles that the problem is this: > > Serial connection established. > ioctl(PPPIOCGFLAGS): invalid argument > tcsetattr: Invalid argument > Exit. > > I do not know if this is modem related, kernel or architecture (ppc). It > worked under YDL (Redhat for PPC) and 2.2.12. I compiled ppp as a module > (including the ppp_generic, ppp_deflate, etc). > I have no problems with 2.4.1 on my i386 machine. > > What is wrong? > > Thanks in advance, > Sebastiaan > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X keyboard settings on Mac...
I'm using X 3.3.36 on potato. Comparing XF86Config files between my debian install and my linuxppc install, I found the following difference: On debian ppc XF86Config, there is the line: XkbKeymap "macintosh" On linuxppc, there is no such line, instead: XkbKeycodes "macintosh" XbkTypes "default" XkbCompat "default" XkbSymbols "macintosh/us" XkbGeometry "macintosh" XkbRules "xfree86" XkbModel "pc101" Does anyone know why they are different and should I make my Debian file look more like my linuxppc XF86Config? Perhaps I should just leave it alone, because debian X works fine, following the linux mantra "it works, but I don't know why" -- wcrowshaw
[Q] Upgrading the kernel to run MOL
I am trying to get mol running on my debian potato install. I downloaded the mol rpm of version 0.9.53-2, aliened and installed it. After a few other steps I, molstart notified me that it needs kernel 2.0.4-test10. So I found a pre-compiled version on the net, and set it up as follows: As root, I put the vmlinux produced by untarring and unzipping the tar.gz file of linux-ppc in the /boot. I also placed the System.map file accompanying vmlinux in /boot. I also placed the modules that came with it in /lib/modules/2.0.4-test10. I also put a copy of vmlinux on my MacOS partition in folder /System Folder/kernel images for bootx. I also created a symbolic link between /vmlinux and /boot/vmlinux (the new kernel). Now I get the following error message upon rebooting, and I don't know what my next step should be: --begin excerpt Parallelizing fsck version 1.18 (11-Nov-1999) fsck.ext2: No such file or directory while trying to open /dev/sdb5 (null): The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock e2fsck -b 8193 fsck failed. Please repair manually and reboot. Please note that the root file system is currently mounted read-only. To remount it read-write: # mount -n -o remount,rw/ CONTROL-D will exit from this shell and REBOOT the system --end excerpt Now /dev/sdb5 is my root partition. How can I fix this problem? What should I do next? And when I do it, can I easily go back to kernel 2.2.17 which came from my stable potato? Although I want to run MOL, I don't want to lose any functionality with a newer unstable kernel.
Re: [Q] Upgrading the kernel to run MOL (revisited..)
On Sat, Feb 17, 2001 at 02:44:37PM -0600, Charles Sebold wrote: > On 24 Shevat 5761, [EMAIL PROTECTED] wrote: > > I am happily running MOL right this minute with 2.2.18 and potato. > > I don't think I would ever upgrade my kernel without compiling it > myself, by the way. Too likely to bring about troubles like you > describe. Compiling your own kernel isn't that difficult either. If > you tell the list what your hardware is perhaps some kind soul will > send you a .config file for the kernel build that will match (I've got > an 8600 and I think most of you people are NewWorld users these > days). > -- > Charles Sebold > -- I took your advice and found all I need in the Nov. and Dec. list archives. I compiled my first debian kernel 2.2.18 (yipee) and installed. Then I download the mol sources 0.9.53 (the same source which made the rpm that, when installed, claimed I need kernel 2.4.0.) Problem is that I ran into a build problem that i can't figure out. I searched the archives and found no similar compile problem. Compile fails, and I think it has something to do with missing headers. Here's the beginning of the stderr output. -- ++ BUILDING ++ Entering '/usr/src/mol-0.9.53/debugger' Entering '/usr/src/mol-0.9.53/debugger/../mon' gcc -pipe -O2 -Wall -fomit-frame-pointer -mmultiple -I../include -c -o ppc-dis.o ppc-dis.c In file included from ppc-dis.c:23: sysdep.h:30: ansidecl.h: No such file or directory In file included from ppc-dis.c:24: ../include/dis-asm.h:13: bfd.h: No such file or directory In file included from ppc-dis.c:24: ../include/dis-asm.h:47: field `flavour' has incomplete type ../include/dis-asm.h:49: field `arch' has incomplete type --end of excerpt The error message goes on for some lines, but I think those follow from the headers the compiler said it was missing: sysdep.h, ansidecl.h, dis-asm.h. (dis-asm.h) comes in the include directory of the mol source, yet the makefile doesn't seem to be able to find it. any clues about the other files, and what going wrong here? thanks -- wcrowshaw
Java on debian ppc...
I noticed the other day at www.linuxppc.org/software that there is a big release of Java JDK from blackdown. Has anybody tried these out on a debian potato powerpc? Just curious. -- [EMAIL PROTECTED]
Re: [Q] Upgrading the kernel to run MOL (revisited..)
Thanks for the help on binutils-dev > see above. you will also need to apply my patch to get it to link > later. my patch also fixes make install to go into /usr/local where > it belongs. I also found the patches that you mentioned posted in the list archive. After I was finally successful in applying them (used the --ignore-whitespace option), I have encountered another problem when I try to make. Make fails and outputs one line: Rules.make:118: *** missing separator. Stop. Reviewing your patches, I did find one which altered line 118 of the Rules.make file. It involves adding the -lelf option to the gcc compile command. I would attach a copy of your patch to this e-mail message, but it wouldn't matter because even when I remove the -lelf option which the patch added, I get the same error message. Any idea about the "*** missing separator" and how to get around it. ps. I applied your patches to the 0.9.53 source. -- william crow
MOL
Sometime last month there was a thread about connecting MOL to the linux install running it using a faux ethernet connection. After alot of experimentation and the some kind assistance from another poster I have managed to make this connection. I can mount my linux home directory as a AppleShare Volume on the MOL side. Pretty damn cool! Yet, I am not completely satisfied. With the proper set up, I thought as well that I could ftp or telnet into the linux install running MOL. But I haven't managed to do so. I would like to even run a web browser on the MOL side and surf the internet through the faux ethernet connection. If any one could give me some tips, I would really appreciate it. Here are details about my linux setup an ethernet with two hosts. The ethernet is 192.168.1.0 (localnet) and the hosts are 192.168.1.1 (zooey), my installs hostname, and 192.168.1.2 (fran). I have the ethernet interface eth0 connected to zooey and my current kernel routing table looks like this: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 127.0.0.1 127.0.0.1 255.255.255.255 UGH 0 0 0 lo 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 On the MOL side, I have the following setup: AppleTalk Control Panel "Connect Via" set to "Ethernet" and AppleTalk activated. TCP/IP Control Panel "Connect Via" set to "Ethernet" "Configure" set to "Manually" I.P. Address set to 192.168.1.2 Subnet Mask set to 255.255.255.0 Router Address set to 192.168.1.1 All other fields are left blank. Like I said, this setup allows me to mount linux directories as AppleShare Volumes, but it does not allow me to telnet, ftp to linux. It also does not allow me to browse the internet (once I have established a ppp connection to my isp). How should I change this setup to make these things happen? Should I make zooey a nameserver, as well as a router? I have done alot of experimenting with the kernel routing tables, but to know avail. Once again, help would be greatly appreciated. Once I get everything working, I am planning to write a detailed how-to about connecting MOL through ethernet to the Linux side of things. Thanks, -- wcrowshaw