Re: upgrading just one stable package to testing version
OR... you could simply download the ssh testing deb file and install that... (don't know what the dependencies are though). - Original Message - From: Jeremy Lunn [EMAIL PROTECTED] To: Toby Thain [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, March 17, 2002 1:42 PM Subject: Re: upgrading just one stable package to testing version On Sun, Mar 17, 2002 at 11:03:51AM +1100, Toby Thain wrote: I've just upgraded one Debian 2.2 machine from stable to testing and other 2.2 stable machines can't ssh into it (Disconnecting: Bad packet length 1349676916). So I'd like to upgrade ssh on the client machine to the testing version. But I don't know how to do this other than adding testing to the apt-get sources, dselect upgrade, etc., which will upgrade everything. Can anyone explain to me how to be more selective? I'm not sure how this related to debian-isp but anyway you could add testing to your sources.list and do: apt-get update apt-get -u install ssh Then either take it out again or create an /etc/apt/preferences file with something along the lines of: Package: * Pin: release a=testing Pin-Priority: 50 -- Jeremy Lunn Melbourne, Australia http://www.jabber.org/ - the next generation of Instant Messaging. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] http://www.zentek-internaitonal.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: booting from CompactFlash Cards
On Sun, Mar 17, 2002 at 01:35:44AM -0500, Jeff S Wheeler wrote: Where do you buy your CF cards that are bootable, and the IDE adapters? I would like to do the same thing and would really appreciate it if you would send me over your vendor information. Part numbers would be nice if you have them handy, too! I bought CF to IDE adapters from ACS (http://www.acscontrol.com). $20 each, you can order online. The CF cards I use are no-name 128 MB cards bought from a local retailer. I believe there's nothing special about them, except they were the cheapest around :) As stated on ACS website, if your application works with IDE drives, it will work with a CF card and our CF to IDE adapter. -- Nicolas BOUGUES Axialys Interactive -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: upgrading just one stable package to testing version
On Sun, Mar 17, 2002 at 11:03:51 +1100, Toby Thain wrote: I've just upgraded one Debian 2.2 machine from stable to testing and other 2.2 stable machines can't ssh into it (Disconnecting: Bad packet length 1349676916). The SSH in stable only supports version 1 of the SSH protocol; if you configure your testing machine to accept that older version of the protocol (by putting Protocol 2,1 in /etc/ssh/sshd_config and restarting ssh), SSH-ing from your stable machines works. So I'd like to upgrade ssh on the client machine to the testing version. But I don't know how to do this other than adding testing to the apt-get sources, dselect upgrade, etc., which will upgrade everything. Can anyone explain to me how to be more selective? You'll need testing's apt (plus its depencencies) for that. The following should work (though I'm not aware of people actually using this configuration as most simply fully upgrade to testing, so you may want to use the -s flag to apt-get to see what it intends to do before actually doing these steps): - add testing entries to /etc/apt/sources.list in addition to the entries for stable - apt-get update - apt-get install apt - create an /etc/apt/preferences with contents Package: * Pin: release a=stable to have apt default to the stable versions - install testing's ssh by requesting it explicitly: apt-get -t testing install ssh HTH, Ray -- Professionele hackers kunnen uw bedrijf veel schade berokkenen. Snail-mail spam van het Nederlands Normalisatie-Instituut -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: upgrading just one stable package to testing version
I have done this to all except 2 of my stable servers, many of them remotely. The one problem is that the libc6 upgrade requires you to restart a few programs (ie, exim, inetd, ssh). You may have other programs on the machine that the upgrade doesn't detect, and must be restarted manually. An easily solution is just to restart the entire machine. Andrew Tait System Administrator Country NetLink Pty, Ltd E-Mail: [EMAIL PROTECTED] WWW: http://www.cnl.com.au 30 Bank St Cobram, VIC 3644, Australia Ph: +61 (03) 58 711 000 Fax: +61 (03) 58 711 874 It's the smell! If there is such a thing. Agent Smith - The Matrix - Original Message - From: J.H.M. Dassen (Ray) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 18, 2002 1:41 AM Subject: Re: upgrading just one stable package to testing version On Sun, Mar 17, 2002 at 11:03:51 +1100, Toby Thain wrote: I've just upgraded one Debian 2.2 machine from stable to testing and other 2.2 stable machines can't ssh into it (Disconnecting: Bad packet length 1349676916). The SSH in stable only supports version 1 of the SSH protocol; if you configure your testing machine to accept that older version of the protocol (by putting Protocol 2,1 in /etc/ssh/sshd_config and restarting ssh), SSH-ing from your stable machines works. So I'd like to upgrade ssh on the client machine to the testing version. But I don't know how to do this other than adding testing to the apt-get sources, dselect upgrade, etc., which will upgrade everything. Can anyone explain to me how to be more selective? You'll need testing's apt (plus its depencencies) for that. The following should work (though I'm not aware of people actually using this configuration as most simply fully upgrade to testing, so you may want to use the -s flag to apt-get to see what it intends to do before actually doing these steps): - add testing entries to /etc/apt/sources.list in addition to the entries for stable - apt-get update - apt-get install apt - create an /etc/apt/preferences with contents Package: * Pin: release a=stable to have apt default to the stable versions - install testing's ssh by requesting it explicitly: apt-get -t testing install ssh HTH, Ray -- Professionele hackers kunnen uw bedrijf veel schade berokkenen. Snail-mail spam van het Nederlands Normalisatie-Instituut -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
what do you do with detected relay attempts?
I have just realised that I wasn't getting postfix relay block alerts under my new postfix set up (on a small Email list system). So I've twigged the right setting and am now getting the very satisfying messages like: In: MAIL FROM:[EMAIL PROTECTED] Out: 250 Ok In: RCPT TO:[EMAIL PROTECTED] Out: 554 [EMAIL PROTECTED]: Relay access denied which, of course, has the IP address and sender name in the subject line of the alert to me. A quick check confirms that they are congruent so I think I should report it to the system. I currently report all spam I get to abuse.net and spamcop.net as I want the anonymity I think they given my reports. Now I'm not sure of the best way to report something like the above. What do other people do? TIA, Chris -- Chris Evans [EMAIL PROTECTED] Consultant Psychiatrist in Psychotherapy, Rampton Hospital; Associate RD Director, Tavistock Portman NHS Trust; Hon. SL Institute of Psychiatry *** My views are my own and not representative of those institutions *** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Exim + POP3 + quota problems
Marcin Owsiany wrote: Hi! Here's my setup: - a potato box (sounds cool, doesn't it? :-) - exim delivers mail to /var/mail/user - qpopper is my POP3 server - there is a user quota for /var partition - /var/spool/pop is a symlink to /usr/local/pop - there is no user quota for /usr/local partition - all users use POP3 to fetch their mail - also, a few users do read mail via local MUAs, so disabling locking in qpopper is not possible The problem is that from time to time the following thing happens: - the size of a user's mailbox in blocks becomes equal to the user's quota on /var - because the user may not use any more blocks on that partition, qpopper is unable to create a lockfile (/var/mail/user.lock) and exits with -ERR maillock: cannot lock '/var/mail/foo': 1 - because of that the user is unable to fetch her mail How do you guys cope with that problem? The only solution I could come up with is switching to Maildir delivery, but might be painful... Maybe there's some solution I've overlooked? Argh... yes, use Maildir, have procmail deliver locally, drop qpopper for courierpop, qmail's pop server, or any of the other Mailbox-aware servers. You'll have a lot less trouble in the long run IMHO. The changeover isn't really that painful either. Been a while since I dealt with qpopper, but wasn't the lock actually /var/spool/pop/user.pop (the temporary copy of the user's mailbox)? If that's correct, mount /var/spool on a different partition from /var/mail, and only enable quotas on /var/mail. If you've got any load on the server, you'll want /var/spool, /var/log, and /var/mail on seperate drives for performance anyhow. -- _ Rich Puhek ETN Systems Inc. _ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mail Servers
I hate asking this, but I thought that this would be the fastest way to get the answer. I may be setting up a mail server for a factory. From what little I know so far, it will be for all a mail server for all five hundred employees. (one in each location) so they can check work related email. I was thinking about using woody, but have the following 2 questions. 1 What is the max user limit that woody + exim will support 2 Could someone point me to a good pointer / how-to for this. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
