Re: (solved) Re: wireless fail after stretch installation
Jude DaShiell <jdash...@panix.com> writes: ... > Many ways exist to solve this problem and it took a while to find out > what to do and how because there's more and better support from > debian-users than is in debian wiki If you can see a way to improve the information on the wiki, please go ahead and do so -- that's what wikis are for, after all. > or debian documentation. We also have a bug tracker, and patches are generally welcome. > I had learned how to do this earlier but apparently an individual > known as longwind from China ran into this problem after I had learned > to solve it on this end and the original message I read from Brian had > a solution I hadn't read earlier and hadn't tried yet which involved > far fewer steps. Fortunately I have a hard drive available so I will > try Brian's solution out on this end and see how it works. Contributions can take a while to get incorporated, but if you come up with an improvement for the documentation and/or the code (assuming that it doesn't break things elsewhere) it will generally get used. Please take notes during your testing, and try to find a way to use your findings that will help people bumping into the same issue in future. > Thanks for your assistance and interest. Thank you for your future contributuons :-) Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Re: (solved) Re: wireless fail after stretch installation
Jude DaShiell <jdash...@panix.com> writes: > The least debian-boot membership could do would be to have a note come > up for installers to execute a shell and do the file copy before > rebooting once hard drive got mounted. This is a problem for wifi users > with no impact for ethernet users. Your tone does not encourage a civil response, but you're going to get one anyway I'm afraid. Since you didn't bother to say what you are complaining about in any useful way, I thought I'd look at the first post in the first thread referred to in the mail from Brian, which is about the fact that desktop-configured wifi connections don't come up until someone logs in. Given that one has generally specified the wifi password as the user in the desktop environment, or at least indicated the fact that you want to connect to that network, it would be inappropriate for the wifi to come up earlier, because that might allow other users on the machine to access a network that was intended to be private. There is generally an option available in network manager that allows one to indicate that the connection should be made available to others. Ticking that box should make it come up at boot time AFAIK. This seems to have very little to do with the installer. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Re: Netinst with preseed
Charles Chambers ccha...@gmail.com writes: On 05/27/2015 07:20 AM, Philip Hands wrote: Charles Chambers ccha...@gmail.com writes: Hi, Phil: And I've looked further. There's a step by step out there that describes the following steps: 1) Wipe USB drive. 2) Copy (via dd) boot.img to it. I'm guessing that boot.img is an image of a VFAT file system, with something like grub4dos on it (which supports booting ISO images from the filesystem). That's a completely different thing from dd-ing the ISO itself. For it to work, the ISO needs to be able to find it's own image on any old file system (which ours are built to do). If that floats your boat, fine. The boot.img is extracted from boot.img.gz, which is found at, for example, here: http://ftp.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/hd-media/ Ah, righto. No, that's just a VFAT file system image, with syslinux on it to make it bootable -- it's effectively a Floppy image, which most BIOSs will accept on a USB stick as an oversized floppy, and therefore try to boot. I think fdisk is just being confused by the data near the start of that (look at the numbers in the fdisk output, and you'll see that they're nonsense). ... You could resize it to get at the whole drive (to answer 1) ). Delete /dev/sdb2-4? There are no partitions -- it's a file system slapped straight onto the device. You'd need to resize the vfat, for which I believe you could use the package 'fatresize' -- although I'm doubtful that you're on the right track, so before you bother with that you'd want to check that it does actually boot and detect the preseed.cfg I'm not sure that we look at the filesystem containing the ISO, when it's been loop-mounted (as would be the case here, assuming it works) in order to find a default preseed, but I guess that it's going to be mounted on /hd-media, so if not at least you ought to be able to specify it by it's path. As for question 3) well, you're copying (dd) a file system to the stick, and then copying an ISO into that file system, so you get no partitions. Don't file systems exist only in partitions? No. The file system comes in when you dd boot.img, and it creates four partitions. No, it doesn't. On the fdisk output, I have accomplished step 2. Kparted and Gparted both agree at that same point that there are no partitions, but fdisk shows 4 partitions, thus none can be added. I'm assuming that the four partitions are embedded in boot.img and created as part of the dd operation. fdisk is just being confused, which is why you're mounting the device itself. I was describing dd-ing the ISO directly to the stick. Our ISO images contain a partition table and boot loader as a bit of magic to make the stick bootable. It turns out that one seems to be able to add partitions, which is what I was on about. I can double check that, but IIRC I tried and could not. The remaining issue would be getting the new partition mounted, and the preseed.cfg therein used, preferably automatically. The objective is a unattended USB install with an edittable preseed.cfg, and optionally additional packages and firmware files included on the media. Windows does it with a customizable unattended.txt (I think) and a system integration tool to select the installation options. If you're using netinst, then the machine must have networking, in which case you might want to consider specifying the preseed as a URL -- then you can edit the preseed on your HTTP server, and never need to update the USB stick. In fact, if you have the relevant control of your network, you could probably dispense with the USB stick and use PXE booting instead. You may find this helpful: http://hands.com/d-i/ in particular the url= stuff. It's also possible to modify the menu presented at boot, if you remaster the ISO, which you might want to do in order to make it (dangerously) do an automated install without prompts. Look in the isolinux directory. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Re: mdadm and UUIDs for its component drives
On Sun, 26 Jun 2011 14:42:03 +0100, Luke Kenneth Casson Leighton
luke.leigh...@gmail.com wrote:
On Sun, Jun 26, 2011 at 2:25 PM, Andrew McGlashan
andrew.mcglas...@affinityvision.com.au wrote:
I hear what you are saying, but I had a related problem which was similar.
well... it's funny, because this is exactly what i need.
Anyway the long and short of it is, I can use mdadm without regard to
what devices are found, such as /dev/sda /dev/sdb /dev/sdc and the like as I
rely purely on the UUID functionality, which as you know, mdadm handles
perfectly well. ;-)
:)
well. that was nice. the scenario you describe is precisely what i
sort-of had planned, but didn't have the expertise to do so was going
to recommend just two drives and then rsync to the other two.
_however_, given that you've solved exactly what is needed / best /
recommended for when you have 4 external drives (which i do) that's
bloody fantastic :)
ok, i bring in phil now, who i was talking to yesterday about this.
what he said was (and i may get this wrong: it only went in partly) -
something along the lines of remember to build the drives with
individual mdadm bitmaps enabled. this will save a great deal of
arseing about when re-adding drives which didn't get properly added:
only 1/2 a 1Tb drive will need syncing, not an entire drive :) the
bitmap system he says has hierarchical granularity apparently.
What I said was: internal bitmaps
madam(8):
-b, --bitmap=
Specify a file to store a write-intent bitmap in. The
file should not exist unless --force is also given. The
same file should be provided when assembling the array.
If the word internal is given, then the bitmap is stored
with the metadata on the array, and so is replicated on
all devices. If the word none is given with --grow mode,
then any bitmap that is present is removed.
To help catch typing errors, the filename must contain at
least one slash ('/') if it is a real file (not 'internal'
or 'none').
Note: external bitmaps are only known to work on ext2 and
ext3. Storing bitmap files on other filesystems may
result in serious problems.
and I probably also gave my half-arsed understanding of what that means.
Feel free to consult actual documentation for a proper understanding of
reality.
also, he recommended taking at least one of the external drives *out*
I think I said: WTF? You buy a machine that had 4 hot swap SATA bays,
and you're plugging crappy external USB drives into it instead? Are you
mental? (or at least, if I didn't say that out loud, that's what I was
thinking ;-)
I must say that I'm a little beffuddled about how you managed to make
the system sensitive to which device contains which MD component -- I
seem to remember you mentioning that you had devices listed in your
mdadm.conf -- just get rid of them.
The mdadm.conf on one of my servers looks like this:
=-=-=-=-
DEVICE partitions
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST system
MAILADDR root
ARRAY /dev/md/2 metadata=1.2 UUID=65c09661:02fc3a16:402916d3:5d4987f4
name=sheikh:2
ARRAY /dev/md/3 metadata=1.2 UUID=e82f516b:64bf463c:adf65c9c:fd728d05
name=sheikh:3
ARRAY /dev/md/4 metadata=1.2 UUID=56adc7ca:c7097e9b:00ac12c0:d1d278f2
name=sheikh:4
ARRAY /dev/md/5 metadata=1.2 UUID=6c5362e4:74b56fad:8c74a317:e4dce6d0
name=sheikh:5
ARRAY /dev/md/6 metadata=1.2 UUID=99ed31bd:cc608687:76f7b5a3:7bca24bc
name=sheikh:6
ARRAY /dev/md/7 metadata=1.2 UUID=87cdaf12:94c2a356:4ba1d3bd:c80ac3b3
name=sheikh:7
ARRAY /dev/md/8 metadata=1.2 UUID=08e708b8:0989607b:d99709d2:8b5e4d58
name=sheikh:8
ARRAY /dev/md/11 metadata=1.2 UUID=210e1b53:3937b017:c947361e:2d2884b1
name=sheikh:11
=-=-=-=-
No mention of devices, which is a good job because that machine seems
to randomise the device mapping on each boot, and is capable of moving
them about when running if you pop the drive out of the machine and back
in again.
As also mentioned somewhere in the docs, the output of the command:
mdadm --examine --scan
can be used to populate the relevant bits of mdadm.conf
Cheers, Phil.
--
|)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/
|-| HANDS.COM Ltd.http://www.uk.debian.org/
|(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND
pgpufrVxAMzIe.pgp
Description: PGP signature
Re: [Debian-uk] ftp.uk.debian.org ill?
On Sun, May 10, 2009 at 02:41:57PM +0100, Harry Rickards wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/10/09 12:09, Julian Gilbey wrote: Is it my imagination, or is ftp.uk.debian.org missing a *lot* of binary packages at the moment? I just tried updating my testing machine, and hit about 60 403's; a look at the directory listings via http://ftp.uk.debian.org/debian/pool shows that there are loads of missing files, such as libg/libgems-ruby/rubygems_1.3.2-1_all.deb. Julian ___ Debian-uk maillist - debian...@chiark.greenend.org.uk http://www.chiark.greenend.org.uk/mailman/listinfo/debian-uk I don't know if it's my problem or if it's the repo's problem, but similar to this I haven't been able to download *any* packages from the repository, since this morning. There were about 20 updates available, 1 403'd and the rest said they were downloading at my usual speed, but stayed at 0%. Changing to the ftp.debian.org repo fixed this. By the looks of it, the Kent mirror of ftp.uk.debian.org seems to be alright. The url is http://www.mirrorservice.org/sites/ftp.debian.org/debian/. As the debian-uk list seems to be very quiet, I've also CC'ed this to the debian-user list/ The RAID controller had a bit of a brain hemorrhage today, and decided that it would throw a load of bad blocks, which put several of the file-systems into read-only. If you were trying to access things at that point, you'll have had trouble. I was under the impression that the subsequent reboot had sorted things out. Can anyone confirm/deny this? Cheers, Phil. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Using rsync to mirror debian
G.Angely [EMAIL PROTECTED] writes: Do not know the squid cache. I will look for it. If you install squid, and add lines like this to /etc/squid.conf: refresh_patterndebian.org/.*\.deb$ 129600 100% 129600 refresh_patterndebian.org/.*Packages 120 20% 360 Then it will keep copies of any packages you download for several months (or until it runs out of space). You run squid on a machine with loads of disk space (your mirror machine say), and change the cache_dir setting to match the amount of space you have. The, on all the debian machines, put this in your /etc/profile: http_proxy=http://squidhost.domain.com:3128/ export http_proxy (replace squidhost.domain.com with the machine you installed squid on) You'll also have to tell squid about your firewall proxy setup. Before doing all this, ask your firewall admin if they already have a cache. Once you've done that, apt-get will work as normal, but the second machine you upgrade on will get all the packages from the squid cache, instead of re-downloading them. You can also point your web browsers at squid, and get speed improvements while browsing as well. P.S.: When I try mailing to debian-user@lists.debian.org, I got an undelivered email error: Your message cannot be delivered to the recipient because his/her mail box storage limit has exceeded. That's very odd --- which machine is generating this warning? Could you try that again, and if there is still a problem, and it seems that the bounce is being generated by one of our machines, please forward the bounce you get to [EMAIL PROTECTED]. Please include any other details you think might be relevant. Cheers, Phil.
Re: OpenBSD Secure Shell
Jim McCloskey [EMAIL PROTECTED] writes: When I did an upgrade against `froozen' today, the post-install script for OpenBSD Secure Shell hung. PS reports it as a zombie process. The last message to the console was: Unpacking replacement ssh ... Setting up ssh (1.2.3-2) ... 1.2.3-3 fixes this. In the mean time, you can Ctrl-C out of the postinst script, and apt-get will either set it up correctly the second time through , or you can select the configure option from dselect, or run: dpkg --pending --configure Starting OpenBSD Secure Shell server: sshd. The server was not started. (I had answered NO when asked if I wanted the server configured with the SUID bit set.) I was able to fix things (I think---haven't tried it much yet) by running dpkg --configure ssh , Yup, that'll do it. It's because sshd doesn't close its file descriptors, which while wrong didn't used to cause problems, but debconf notices and hangs. Cheers, Phil.
Re: Please tell me this is curable...
Patrick Kirk [EMAIL PROTECTED] writes: Can you recall the name of any of these Windows utilities? Or has nayone done this in the past and have the awk script lying about? The problem is the lf - crlf switch. Just reverse it. There will be posts saying this won't work but it will. You'd think it doesn't work because what about valid crlf pairs in the original data. But they get changed to crcrlf by the ascii Ah, good point. Assuming it's true: perl -ne 's/\r\n/\n/g; print;' broken.tar fixed.tar should do the trick. Cheers, Phil.
[off topic] Slashdot announce 2.0beta2
Here's a comment I tried to post at slashdot, but slashdot is a bit broken, so I'll mention it here before people get overexcited: I seem to have caused a little confusion here. I needed to create some new CD images, because enough new bug fixes had hit the archive to make it worthwhile, and if I do that I have to differentiate the versions somehow: hence a directory name of 2.0beta1 for the first lot, and 2.0beta2 for the second. Of course, as soon as I did the 2.0beta2 CD images, I was told how to fix a booting problem we've been having with the CD's so there was a good reason to instantly go to version 2.0beta3 of the CD's. This should not be taken to mean there's anything radically different between the 2.0beta2 and 2.0beta3 CD images (the only difference is the order in which the files are put into the CD image) That said, it seems reasonable to say that Debian 2.0 is into it's second phase of testing. It's just that there wasn't an ``official'' delineation between 2.0beta and 2.0beta2 (except by me choosing a particular moment to freeze my mirror) I'm not sure how useful it is to worry about the beta versions of the distribution, but of course it must be done for the CD images, so that we know to which versions any bug reports apply. Just one more thing. If anyone has burnt CDs using 2.0beta2 images, don't bother worrying about what is different with 2.0beta3 --- the answer is nothing, except the file order, which was only done to improve the bootability of the images on machines with certain BIOS's I hope that's a little clearer. Cheers, Phil. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: stopping pppd redial with persistent connection
[EMAIL PROTECTED] said: How do I get pppd to block totally when this happens. Ideally this should stop pppd from dialing at all till someone manually restarts it. Use diald to maintain the link, and set dial-fail-limit: DIALD(8) DIALD(8) dial-fail-limit Sets the maximum number of consecutive failed connection attempts diald will allow. If this limit is exceeded diald will block further connec tions until an unblock command is issued on the command FIFO. If this is set to 0 diald will not enforce any limit. The default value is 0. When this condition occurs diald will issue the follow ing message to the system logs: Too many dialing failures in a row. Blocking con nection. This command is intended for use at sites that need to avoid the possibility of diald attempting a large number of long distance phone calls to a machine that is not operating correctly. Once diald blocks the connection an operator can investigate the cause, correct the problem, and then issue the unblock command to allow diald to continue. Cheers, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem dialing in w/AutoPPP/PAP! Help!
I can verify that turning off shadow passwords fixes the PAP problem. This is unacceptable. And it's already reported in bug 16044. Oh well. It this the case with ppp-pam installed ? If you are using ppp for dial-in, with PAP authentication, I was assuming that people will be using PAM too. Install ppp-pam_2.3.2-2.deb to get PAM support. Also ppp_2.3.2-2.deb has shadow support (I hope), where ppp_2.3.2-1.deb did not, so you could try that. There is a problem with the non-pam ppp's handling of password aging, so on the whole I'd prefer if people used PAM for dial in. I'd be interested to hear how people get on with PAM, since I don't use PAP for dial-in, so have trouble testing it. BTW I'm hoping to get pppd to be able to detect the presence of libpam at run-time, and so get rid of the ppp-pam package in the future. Cheers, Phil. PPP Meister [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: pppd
I just upgraded, using dselect, to pppd 2.2.3, and now pon doesn't work. It overwrote my /etc/ppp.chatscript file and deleted my /etc/ppp.options_out file. I reinstated them, and that didn't help. You probably want to look at /etc/ppp/peers/provider and co. Could you give me a rundown on your old setup (old version of ppp, files that got trashed etc.), and what happened to it, so I can stop it from happening to others and/or get the postinst to tell you what's happening. Cheers, Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Looking for New Maintainers
ppp Philip Hands [EMAIL PROTECTED] netdiag Philip Hands [EMAIL PROTECTED] I'm on these --- I've just been putting my effort into testing bo rather than worrying about my packages at present. Now that 1.3's released I'll do something about them. Cheers, Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Fixed! (Re: mgetty isn't answering the phone (ioctl problem))
In my experience, I've had to turn MGETTY OFF when I wanted to make an outbound PPP call. Dunno exactly why. I can dial out when I have MGETTY running, if I dial out with something like Minicom. Sounds like your pppd is not getting its locks right. Possible causes: 1) it has not been told to use locks (``lock'' on the command line or in the options file sorts this out) 2) You may be mixing /dev/ttyS? with /dev/cua? devices --- mgetty doesn't like cua's and you should not use them at all on a port that mgetty is using. 3) pppd has been compiled to put the locks in the wrong place. If you run: strings /usr/sbin/pppd | grep LCK you should get ``/var/lock/LCK..'' --- If not you need a different pppd. A clasic symptom of this sort of locking failure is that you will see mgetty's attempts to reset the modem in the logs of the outgoing chat --- Mgetty doesn't know you're still using its line, so it goes ahead and resets it almost as soon as you start dialing. Cheers, Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: support for USRobitics modems under mgetty
What USRobotics modems need special support? We have been running Debian mgetty on two Linux boxes with both USR Courier and Sportster models for a very long time without any problems. The USRobotics flag in mgetty/policy.h activates a patch I wrote to get a Courier V.32+Fax (UK version) Modem to work. It sorts out a couple of problems: A bug in the implementation of FCC that causes the modem to use 14k4 as the minimum fax speed; and a different approach to the fax speed switch foolishness that some modems indulge in. So if your USR fails to work with fax machines that doesn't support 14k4, or if you can only get faxing to work by running the modem at 19k2 at all times, then you probably have one of the modems in question. As mentioned in the code, some (or maybe all) later models don't need it. Cheers, Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: TCP/IP SMB Connections
Which brings me to question number 1: Where do I get TCP/IP protocol for Windoze for Workgroupies? Microsoft's techs were no help. Whats TCP/IP? one said.. snicker ftp://ftp.microsoft.com/bussys/Clients/WFW/TCP32B.EXE You need two things: The 32 bit TCP stack (TCP32B.EXE); and the 32 bit support for Windows (which has been called all sorts of things. The copy I'm using at present comes in a file called OLE32S13.EXE) I'm afraid I cannot remember which directory this is in, and the layout of MS's ftp site makes no sense to me so I can't even guess :-( Also, they call the files silly names (the 32 bit stuff was called something like PW1118.EXE at one point). And of course question number 2: Does anyone have any quick warnings that will save me some trouble, that they can let me know about? First set up the 32-bit stuff (run the self-extracting archive, then run the setup that gets created), then add the TCP stack (run the self-extract, then use ``Network Setup'' to add a protocol). I find that samba performance is better if I remove the other protocols, since I run no non-TCP stuff on the network, browsing works much faster if it isn't trying to use anything other than TCP. I think the samba docs. have more info on setting WfWg up as well. Hope that helps. Cheers, Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: newsreader problem?
On Sun, 29 Sep 1996, David Puryear wrote: I've problem with Netscape3.0 newsreader in Linux. When I do 'Show All Newsgroup', I don't get the complete(which I get when I do this in Windoz) list. I tried knews and had same problem. I don't use much of Windoz, so I would really like to make this work. Any ideas? I noticed the same thing. Does it say it transfers 1KB, then stop? I thought it was a problem with a new ISP that my wife calls. Maybe it's a new bug in Netscape v3.0. It used to work... I get similar behaviour if I point Netscape at a locally running nntpcache that I was experimenting with, but not if I go to my ISP's news server via an IP-masquerading firewall. I thought it was the nntpcache I was playing with, I'll have another look now that it seems to be Netscape. Cheers, Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Help with diald?
Hello, I'm trying to use diald, but have problems. If I use '/etc/init.d/ppp start' ^ Don't do that, /etc/init.d/ppp starts pppd as a daemon, whereas diald wants to start pppd itself after the connect script exits, iff it returns 0. as my connect script (and have no ip-up because ppp will call its own) I see in my log things like diald: connect to x diald: starting pppd but nothing happens really; in addition, why does diald says it starts pppd when the manual page says this is the task of the connect script? To quote the man page: connect p Use the executable or shell script p to set up the serial line. This normally dials the modem and starts up the remote SLIP or PPP session. The com ^^ It says connect starts the _remote_ ppp session, it then exits and lets diald start the local pppd. So I'd like to get help on setting up diald so that I can reuse most of my existing pppd setting (chat script and ip-up/ip-down scripts). You need to be careful not to give any options to pppd that you can specify via diald, since diald passes them on for you anyway. Your /etc/ppp/options file is likely to end up with nothing in it. I'd like to know, too, how I can arrange things so that when I mail to someone outside my domain diald does not try to dial. If you're using sendmail, create a file called that reads as follows: --start of /etc/service.switch-- aliases files hosts files --end of /etc/service.switch-- This tells sendmail to use file lookups for hosts and aliases, thus avoiding the DNS lookup that is bringing the line up. You also need to tell it not to attempt immediate delivery, by setting the delivery mode to queue (look for ``DeliveryMode'' in /usr/doc/sendmail/op.txt.gz) Thanks in advance, Yves. Cheers, Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
