Re: IPSEC/IPSEC_ESP module(s)
On Tue, Jul 31, 2001 at 04:55:53PM -0600, [EMAIL PROTECTED] wrote: Has anyone attempted to make a loadable module out of IPSEC yet? I doubt it would be possible: it has hooks all through the network code. Kris PGP signature
No Subject
dear I had been upgrade my system from BSD4.3-RELEASE to BSD5.0-CURRENT but I found fatal question that is my 3c905B AHA2940 maybe use the same irq(14).As this my 3c905B do nothing. How can i do? Can't thankful enougth to you! Also I found I could not use su . suken === http://sms.163.comÍøÒ׶ÌÐÅ ·¢×ÔÄÚÐÄ http://love.163.com Ç£ÒÁÖ®ÊÖ¹²ÏíÈËÉú»¶Ó飡NEW£¡ http://alumni.163.com ±ÌÔÆÌ죬»ÆÒ¶µØ£¬Ð£Ô°Ç黳ÒÀÈçÎô To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntpd 4.1
On Thu, 02 Aug 2001 14:07:38 +0100, Mark Murray wrote: Now that ntpd 4.1.0 has been released (finally!), I'll upgrade current very soon. :-) :-) :-) Unless David Mills can be convinced to manage his documentation in a sensible fashion, this will be the last upgrade for which I'll be doing HTML - mdoc transcription. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: IPSEC/IPSEC_ESP module(s)
Have we come to a decision on when we're going to either drop floppy support or consider a different version of GENERIC for the CDROM installation? Along the lines of droping floppy support: I just managed to setup a DHCP/TFTP/NFS diskless boot server that boots the floppy install images. Unfortunatly, it did require nfs. So even if floppy install is discontinued, it would be very nice to have support for installing from PXE. If anyone wants details let me know off-line. brad To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntpd 4.1
Ollivier Robert wrote: Now that ntpd 4.1.0 has been released (finally!), I'll upgrade current very soon. The question I have is the following: authentication was done with md5 code builtin and I disabled DES support (not supported anymore). Now, with 4.1, it can be linked to openssl but it is still an optional component. I'm a bit reluctant to force openssl for just ntpd. Any ideas / comments ? Why not to use libmd5? -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntpd 4.1
According to Maxim Sobolev: libmd I meant. That's a possibility but it already has its own md5/des code. It is just that authentication through openssl is available and many 5.x / 4.x have it by default... It is required by sshd and friends but crypto is still optional. -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #46: Wed Jan 3 15:52:00 CET 2001 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
!RE: IPSEC/IPSEC_ESP module(s)
This gives me the opportunity to ask a question I have been wondering for a while... I've been building kernels with IPSEC support and was unclear what kind of load this puts on the system by default. If IPSEC has hooks into all the networking code, does this become an issue on slow or otherwise heavily loaded hardware? Currently I am running FreeBSD 4.2 [not current] on my NFS server. Is IPSEC desirable in this configuration or not? [I'm behind a firewall.] Also, I can't decide whether to comment out the IPv6 code or not in the kernel configuration file. I would like to support the new protocols, but don't want to unnecessarily burdon the system. My NFS server [on my home network] is working like a champ with only 48 megs of RAM (!). I am using it to mount my home directories. The reason this comes up for me is that someone from SSH Communications recently told me that IPSEC supports IPv6. Does this mean that if I enable IPSEC in the kernel, I should also make sure to enable the IPv6 code? I would deeply appreciate it if someone could shed some light on this subject for me. Regards, On Friday, August 03, 2001 10:39 AM, Sheldon Hearn [SMTP:[EMAIL PROTECTED]] wrote: On Fri, 03 Aug 2001 10:40:24 CST, Brad Huntting wrote: Have we come to a decision on when we're going to either drop floppy support or consider a different version of GENERIC for the CDROM installation? Along the lines of droping floppy support: I just managed to setup a DHCP/TFTP/NFS diskless boot server that boots the floppy install images. Unfortunatly, it did require nfs. I take it from all the peripheral postings that the answer to my questions is no. :-) I wonder how we even begin to decide such a thing. By the way, even if floppy support is not discontinued, there's nothing holding back the development of more flexible non-floppy kernel arrangements. Perhaps that's the route to take, before we even think about dropping floppies. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Glen M. Gross Unix Technical Support Specialist Symark Software 5716 Corsa Avenue, Suite 200 Westlake Village, CA 91362 http://www.symark.com [EMAIL PROTECTED] [EMAIL PROTECTED] Main: 800-234-9072 or 818-865-6100 Main fax: 818-889-1894 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
named -u bind
Are there any reasons not to use -u bind flag for named by default? # Or importing code to use chroot from OpenBSD? -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project bind.diff
You have WON your FREE nights!!!
English Español Escape to Paradise...! El Rancho Villas Mazatlan, Mexico Dear Friend: You've been selected to take 1 night free for each one you pay in our resort at Mazatlan, Mexico. That's right !! Pay 1 night and get another one FREE!! This opportunity goes to only selected people, so take advantage of this unique offer you'll never see again a lodging offer like this one. Your next vacation half the price!! Why don't you take a rest in the wonderful beach of Mazatlan, Mexico. This is your opportunity. Make it possible for you. If you use this wonderful opportunity, I'll also give you a 20% discount over drinks and food in our restaurant. The delicious flavors you're will taste there are going to be unforgettable, believe me! I send you our addresses for more information, just in case you are interested in the offer I'm sending you. If you want to use this benefit, please refer the code below to make this offer valid: fRpromo0802 Promotion Validity: from Aug 15 to Dec. 15, 2001; excluding Thanksgiving week. Web Sites: www.elrancho.com.mx www.elranchovillas.com e-mail: [EMAIL PROTECTED] Reservations: Tel: (1)716-0606 Fax: (1)716-9777 US Canada: 1-888-596-5760 Mexico: 01-800-717-1991 To be removed from our mailing list, please send us a blank email to [EMAIL PROTECTED] with the word REMOVE in the subject line. Escapa al paraíso...! Villas El Rancho Mazatlán, México Hola amigo: Haz sido seleccionado para llevarte una noche gratis por cada una que pagues a nuestro hotel en Mazatlán, México. Es en serio !! Paga 1 noche y te llevas otra totalmente GRATIS!! Esta oportunidad se da sólo a personas muy selectas, asi que aproveche esta única oferta. Jamás vera una oferta igual en lo que a alojamiento se refiere. Sus próximas vacaciones por la mitad de precio!! Por qué no tomar un descansito en las maravillosas playas de Mazatlán, México. Esta es su oportunidad. Hágala posible por usted. Es más, si usted hace uso de esta increíble oportunidad, además le regalo un 20% de descuento en alimentos y bebidas en nuestro restaurante. Los sabores delicios que probara ahí, serán inolvidables, créame! Para más información, le mando nuestras direcciones electrónicas, sólo en el caso de que se interese por la oferta que le he hecho. Si quiere usar el beneficio, por favor indique el codigo que sigue para hacer válida esta oferta: fRpromo0802 Vigencia de la promoción: de Agosto 15 a Diciembre 15 del 2001; se excluye la semana de Thanksgiving (Festividad en EE.UU.) Web Sites: www.elrancho.com.mx www.elranchovillas.com e-mail: [EMAIL PROTECTED] Reservaciones: Tel: (1)716-0606 Fax: (1)716-9777 México: 01-800-717-1991 US Canada: 1-888-596-5760 Para ser removido de nuestra lista de correo, por favor envíenos un email en blanco a la siguiente
Re: /home: mount pending error: blocks 14 files 3
On Thu, 02 Aug 2001 10:42:29 +0100, Brian Somers wrote: If the error keeps turning up, I would guess that you have a 0 or empty fsck field in /etc/fstab and fsck -s therefore not fixing the problem. Nope. I have passno set for the filesystem on which I also see this. I used to have background fsck enabled, but I disabled it because of horrid unkillable fsck behaviour. Perhaps background fsck did something nasty to my filesystem that normal fsck isn't seeing? The soft-updates code stores two block counts and two file counts in the superblock so that df(1) can give sane answers for filesystems where soft-updates is enabled. fsck(8) fixes them up (and frees off the bitmaps etc) on my machines ok. Ciao, Sheldon. -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.freebsd-services.com/brian@[uk.]FreeBSD.org Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: IPSEC/IPSEC_ESP module(s)
Kris Kennaway [EMAIL PROTECTED] writes: On Fri, Aug 03, 2001 at 02:25:56AM +0900, Hajimu UMEMOTO wrote: Is there any chance to enable IPSEC in GENERIC? I'm not sure how much that would bloat the kernel..there may not be space for it on the install floppy. I might misunderstand how the make-bootfloppies process works, but isn't it possible to add IPSEC to GENERIC and have dokern.sh remove it for the kernel that gets put on the floppies? If so, that's what I think we should do. /assar To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntpd 4.1
According to Garrett Wollman: I'd like to have the AUTOKEY functionality available if at all possible. Goodnews: the first run I've done of configure with --with-crypto=autokey give me no dependencies on openssl (which is necessary for public key stuff). -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #46: Wed Jan 3 15:52:00 CET 2001 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /home: mount pending error: blocks 14 files 3
Am I desynched? I went to single-user, tried to do a fsck -s, and found there is no such option. Also, the /etc/fstab didn't need changed at all. It is already proper. Needless to say, going to single-user, running just `fsck -y /dev/ad0s1g` fixed the problem, although it noted no errors. Could there be a bug in softupdates again? Below is a copy of the top of the manpage for the version of fsck on my -current, and a copy of my [unmodified since ???] /etc/fstab. --- FSCK(8) FreeBSD System Manager's ManualFSCK(8) NAME fsck - file system consistency check and interactive repair SYNOPSIS fsck [-dvplfyn] [-B | -F] [-l maxparallel] [-t fstype] [-T fstype:fsoptions] [special | node ...] # DeviceMountpoint FStype Options Dump Pass# /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1e /usrufs rw 2 2 /dev/ad0s1f /varufs rw 2 2 /dev/ad0s1g /home ufs rw 2 2 /dev/ad0s1h /tmpufs rw 2 2 /dev/ad1s1e /misc ufs rw 2 2 /dev/da0s1 /ms-dog msdosfs rw 0 0 /dev/cd0c /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 proc/usr/compat/linux/proc linprocfs rw 0 0 #argus:/misc/argus.misc nfs rw 0 0 --- In case you feel like asking, my cheetah died, and all I could afford was a big IDE at the time, the 'cuda winblowz is on is still alive tho... One of these days... Brian Somers wrote: The error means that your machine crashed with soft-updates enabled, leaving 14 blocks and 3 files still allocated on disk (using up blocks inodes). If the error keeps turning up, I would guess that you have a 0 or empty fsck field in /etc/fstab and fsck -s therefore not fixing the problem. To fix it, correct fstab and run fsck -B. I've never had this before, and I have traced the message to ufs/ffs/ffs_vnops.c on line 634. I have recently noticed [since my last svsup] that this is happening on boot and shutdown [in which case, the messasge is also in the same file, but for umount conditions]. I am not a filesystem expert.. How concerned should I be? This is -current a week or two old [before all the lockup threads began]... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntpd 4.1
Maxim Sobolev wrote: Ollivier Robert wrote: Now that ntpd 4.1.0 has been released (finally!), I'll upgrade current very soon. The question I have is the following: authentication was done with md5 code builtin and I disabled DES support (not supported anymore). Now, with 4.1, it can be linked to openssl but it is still an optional component. I'm a bit reluctant to force openssl for just ntpd. Any ideas / comments ? Why not to use libmd5? libmd I meant. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: What's touching my executables?
Will Andrews [EMAIL PROTECTED] writes: Probably the recent change (IIRC) that someone turned running an executable into a mtime change. Which change is that? /assar To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntpd 4.1
Now that ntpd 4.1.0 has been released (finally!), I'll upgrade current very soon. :-) :-) :-) The question I have is the following: authentication was done with md5 code builtin and I disabled DES support (not supported anymore). Now, with 4.1, it can be linked to openssl but it is still an optional component. I'm a bit reluctant to force openssl for just ntpd. Can you make it so that if NO_OPENSSL is not defined, then openssl is used? M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: IPSEC/IPSEC_ESP module(s)
On Fri, 03 Aug 2001 10:40:24 CST, Brad Huntting wrote: Have we come to a decision on when we're going to either drop floppy support or consider a different version of GENERIC for the CDROM installation? Along the lines of droping floppy support: I just managed to setup a DHCP/TFTP/NFS diskless boot server that boots the floppy install images. Unfortunatly, it did require nfs. I take it from all the peripheral postings that the answer to my questions is no. :-) I wonder how we even begin to decide such a thing. By the way, even if floppy support is not discontinued, there's nothing holding back the development of more flexible non-floppy kernel arrangements. Perhaps that's the route to take, before we even think about dropping floppies. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
What's touching my executables?
-CURRENT (Jul 25), alpha. An increasing number of executables on that box are sporting ever newer mtimes. This appears to have been going on ever since the Jul 25 update. There is no clear pattern which executables are touched. md5 comparisons with previous backup levels (using a Jul 13 copy of md5) suggest that the executables have not been changed. For various reasons I consider it unlikely that I'm dealing with a security issue here, although I'm looking into that as well. Can anybody think of a technical explanation? -- Christian naddy Weisgerber [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: IPSEC/IPSEC_ESP module(s)
On Fri, Aug 03, 2001 at 10:14:51AM +0200, Sheldon Hearn wrote: On Thu, 02 Aug 2001 21:44:27 CST, Warner Losh wrote: I'd love to do that, but it would have to be removed for the install disks. The kernel already is too fat for them :-( Have we come to a decision on when we're going to either drop floppy support or consider a different version of GENERIC for the CDROM installation? FWIW: the alpha is suffering from exactly the same problem. There a 3 (or more) floppy install set was proposed. Wilko -- | / o / / _ Arnhem, The Netherlands email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: IPSEC/IPSEC_ESP module(s)
On Thu, Aug 02, 2001 at 11:54:00AM -0600, Brad Huntting wrote: Brad [EMAIL PROTECTED] writes: Has anyone attempted to make a loadable module out of IPSEC yet? Kris [EMAIL PROTECTED] responds: I doubt it would be possible: it has hooks all through the network code. What about makeing the individual encription and authentication schemes loadable modules? I don't know; currently these aren't individually selectable anyway. Kris PGP signature
Re: IPSEC/IPSEC_ESP module(s)
In message [EMAIL PROTECTED] Hajimu UMEMOTO writes: : On Thu, 2 Aug 2001 02:57:55 -0700 : Kris Kennaway [EMAIL PROTECTED] said: : : kris On Tue, Jul 31, 2001 at 04:55:53PM -0600, [EMAIL PROTECTED] wrote: : : Has anyone attempted to make a loadable module out of IPSEC yet? : : kris I doubt it would be possible: it has hooks all through the network : kris code. : : Is there any chance to enable IPSEC in GENERIC? I'd love to do that, but it would have to be removed for the install disks. The kernel already is too fat for them :-( Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntpd 4.1
On Fri, 03 Aug 2001 08:52:19 +0200, Ollivier Robert wrote: Unless David Mills can be convinced to manage his documentation in a sensible fashion, this will be the last upgrade for which I'll be doing HTML - mdoc transcription. Don't hold your breath then, he repeated two days ago he didn't want to change the way he manages the documentation. I hold my breath for very little, these days. :-) What blows my mind is that he's not even willing to use slightly more translatable markup. He's just totally anti anything other than his own paradigm, which is that local documentation is dead and the web is the only place to put it. *mutter* Ciao, Sheldon. Sheldon Hearn Prime Apostle of the Church of Disillusioned Saints To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /home: mount pending error: blocks 14 files 3
On 02-Aug-01 Sheldon Hearn wrote: On Thu, 02 Aug 2001 09:33:41 MST, John Baldwin wrote: I get these messages when I reboot or crash before the background fsck finishes sometimes. Sometimes I get them when the filesystems are clean, too. They always happen when the previous boot did a background fsck, however. Then you're not seeing the whole problem. :-) As I said, I'm not using background fsck any more and have had several fsck runs report the filesystem as clean since I turned it off. Hmm, any more. I didn't see them at all until I started using background fsck. *shrug* I get them all the time though myself. I thought they were a feature of background fsck. Perhaps they aren't. :( Maybe fsck is failing to clean your filesystem or something ? A boot -s followed by a successful fsck should get rid of them. I was seeing them at Usenix and mentioned it to Kirk. He explained their nature -- ie, you've just got some blocks and inodes marked in use that shouldn't be. Or maybe these numbers are the only thing corrupt about your fs so they're not being re-written after fsck finishes ??? Ciao, Sheldon. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.freebsd-services.com/brian@[uk.]FreeBSD.org Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /home: mount pending error: blocks 14 files 3
On Thu, 02 Aug 2001 11:21:21 EST, Jim Bryant wrote: Could there be a bug in softupdates again? In fsck, more likely. This is why background fsck is enabled by default, I guess -- to get the bugs shaken out. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Keeping User Database loaded in Mem
use one of the client/server authentication methods and write the server part in a way that it keeps it in memory (of course the user database is usually in cache if you are doing a lot of authentication) On Fri, 3 Aug 2001, :: Patrick Tracanelli :: wrote: Hello you all; I want to know if there is a working way to keep FreeBSD's user database loaded in memory. The reason's for that is very clear, if i keep my spwd.db loaded the access to it won't be a disk access, so this will speedup any forms of authentication... The reason is that i want to avoid SQL databases in some cases where the system database works better to me. I have calculated that a database amount of 3000 (+/-) users would need about 7.6MB of memory, what sounds very good to me... If there isn't a way to it, yet, that is something i would love to see when -CURRENT becomes -RELEASE... it's an idea :) Best Regards Peace []'z Eksffa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ntpd 4.1
On Thu, 2 Aug 2001 12:25:13 +0200, Ollivier Robert [EMAIL PROTECTED] said: The question I have is the following: authentication was done with md5 code builtin and I disabled DES support (not supported anymore). Now, with 4.1, it can be linked to openssl but it is still an optional component. I'd like to have the AUTOKEY functionality available if at all possible. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: IPSEC/IPSEC_ESP module(s)
Brad [EMAIL PROTECTED] writes: Has anyone attempted to make a loadable module out of IPSEC yet? Kris [EMAIL PROTECTED] responds: I doubt it would be possible: it has hooks all through the network code. What about makeing the individual encription and authentication schemes loadable modules? brad To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: IPSEC/IPSEC_ESP module(s)
On Thu, 2 Aug 2001 02:57:55 -0700
Kris Kennaway [EMAIL PROTECTED] said:
kris On Tue, Jul 31, 2001 at 04:55:53PM -0600, [EMAIL PROTECTED] wrote:
Has anyone attempted to make a loadable module out of IPSEC yet?
kris I doubt it would be possible: it has hooks all through the network
kris code.
Is there any chance to enable IPSEC in GENERIC?
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: !RE: IPSEC/IPSEC_ESP module(s)
On Fri, Aug 03, 2001 at 11:28:09AM -0700, Glen Gross wrote: This gives me the opportunity to ask a question I have been wondering for a while... I've been building kernels with IPSEC support and was unclear what kind of load this puts on the system by default. If IPSEC has hooks into all the networking code, does this become an issue on slow or otherwise heavily loaded hardware? Currently I am I wouldn't expect it to be a significant issue. The reason this comes up for me is that someone from SSH Communications recently told me that IPSEC supports IPv6. Does this mean that if I enable IPSEC in the kernel, I should also make sure to enable the IPv6 code? I would deeply appreciate it if someone could shed some light on this subject for me. IPSEC supports IPv4 as well :-) The comment just means that it works with both. Kris PGP signature
Re: named -u bind
Jun Kuriyama [EMAIL PROTECTED] writes: At Fri, 03 Aug 2001 19:50:24 -0700, Dima Dorfman wrote: IIRC the last time this came up somebody said something about it not being able to read zonefiles in some odd places where they like to put them. I.e., they want it to run as root so they can set their zonefile mode 600 or something. If they are running on -stable, is it possible to change default behaviour on -current to use bind account? Don't ask me, I wasn't one of those people. *I* won't object to this change; I was just warning you that somebody might, for that reason. # Or importing code to use chroot from OpenBSD? Import code? BIND can run in a chroot just fine. Sorry for my poor explanation. This means to get a part of shell code in /etc/rc of OpenBSD to prepare chroot environment. This seems users can use chroot'ed named easily with only setting variables at /etc/rc.conf. This seems like a good idea whether it's the default or not. The only thing is that something running in a chroot should be built statically, unless you also want to stick libc and friends in there. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Ïðåäëàãàåì ïðèîáðåñòè â ñîáñòâåííîñòü àäìèíèñòðàòèâíîå çäàíèå â Êàçàíè (Òàòàðñòàí, Ðîññèÿ): - Îáùàÿ ïëîùàäü 910 êâ. ì; - 2 ýòàæà; - Áîëüøîå êîëè÷åñòâî ïîìåùåíèé îò 7 äî 200 êâ.ì; - Ñîáñòâåííàÿ òåððèòîðèÿ - çåìåëüíûé ó÷àñòîê 0,101 Ãà. Çäàíèå - áûâøàÿ ñòîëîâàÿ ðå÷íîãî ïîðòà. Èìååò âûãîäíîå ðàñïîëîæåíèå: - íàïðîòèâ çäàíèÿ - âòîðîé ïî âåëè÷èíå îïòîâûé ïðîäóêòîâûé ãîðîäñêîé ðûíîê; - óäîáíûå ïîäúåçäíûå ïóòè; - áëèçêî ê öåíòðó ãîðîäà - 5 ìèí. åçäû; - áëèçêî ê æ/ä âîêçàëó - 5 ìèí. åçäû; - ðÿäîì ðå÷íîé ïîðò; - ðÿäîì æ/ä ïóòè. Çäàíèå èäåàëüíî ïîäõîäèò äëÿ ðàçìåùåíèÿ îôèñà ïðåäñòàâèòåëüñòâà Âàøåé êîìïàíèè â Òàòàðñòàíå èëè Ïîâîëæüå. Âîçìîæíà êîìïîíîâêà îôèñ/ñêëàä. Âñå êîììóíèêàöèè ïîäâåäåíû. Çäàíèå òðåáóåò ðåìîíòà (ïîëíàÿ âíóòðåííÿÿ îòäåëêà, âêëþ÷àÿ íîâûå îêîííûå è äâåðíûå áëîêè). Çäàíèå íàõîäèòñÿ â ÷àñòíîé ñîáñòâåííîñòè. Çåìëÿ - â áåññðî÷íîì ïîëüçîâàíèè. Öåíà çäàíèÿ - ÁÎËÅÅ ×ÅÌ ÄÎÑÒÓÏÍÀ. Åñëè âû çàèíòåðåñîâàíû â ïîëó÷åíèè îò íàñ áîëåå ïîäðîáíîé èíôîðìàöèè î äàííîì îáúåêòå, îòïðàâüòå ïóñòîå ïèñüìî ïî àäðåñó: [EMAIL PROTECTED] Ïðè ýòîì â Òåìå ñîîáùåíèÿ ÎÁßÇÀÒÅËÜÍÎ óêàæèòå: Ïðèøëèòå ïîäðîáíóþ èíôîðìàöèþ. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: rpc.umtall dumps core on each startup/shutdown
On Thu, 2 Aug 2001, Maxim Sobolev wrote: I found that the rpc.umntall program from time to time starts dumping a core at each startup/shutdown. Removal of /var/db/mountab helps for certain period of time, but eventually the problem reoccurs. Attached please find backtrace of two cores (sig11 on shutdown and sig6 on startup) and mountab from the affected machine. Please fix. I am observing this problem on two 5-CURRENT machines updated today. I haven't seen this, but I consistently see chunk already free messages. The differences is probably just due to my use of /etc/malloc.conf - aj. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: rpc.umtall dumps core on each startup/shutdown
In message [EMAIL PROTECTED], Maxim Sobolev writes: I found that the rpc.umntall program from time to time starts dumping a core at each startup/shutdown. Removal of /var/db/mountab helps for certain It seems to be a bug in the rpc library (thank $deity for libefence when tracking down such bugs :-). The rpcbind client code in libc keeps a cache of DNS lookups, but it is missing a strdup() when it copies a string from the cache. Investigating this has shown up a few bugs I introduced to rpc.umtall in my last set of changes, so I'll fix those too. Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
rpc.umtall dumps core on each startup/shutdown
To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Investors and Collectors of Militaria
Title: Untitled Document Investors and Collectors of Militaria Endorsed and signed by the Australian Chief of Army Lieutenant General Peter Cosgrove For information and to order Opportunities for organisations Remove me from list To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI: Clock problems in -current
I forgot: Even if I define CLK_USE_*_CALIBRATION (and get no error messages after defining debug.acpi.timer_test), the Off/2 error still persist. Ok. I'm going to revert to the safe read code in a few minutes. Can you update and let me know if you're still wildly off? I'm having a hard time believing that your timer is really running at double pace, but I guess anything is possible. If it still does, I'll add some code to check it with the TSC. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
HEADS UP: ACPI changes
I've made a couple of minor changes to the ACPI code: - Fixed (hopefully) PCI interrupt routing, thanks to [EMAIL PROTECTED] who was able to actually test (and correct) my code. - Changed the way ACPI timers are treated to be more pessimistic. It looks like we can't assume that the average ACPI timer is properly implemented. This is a pain; a good timer takes about 350 cycles to read on my PIII/500 laptop, wheras the safe read takes about 1050 cycles. (~700ns vs. 2us respectively). The code will still optimise if a known-good timer is detected. To test your ACPI timer, first check to see which one you have. Look at the output of 'pciconf -lv'. If you have an Intel chipset, chances are that we already know about it, and the code will do the right thing. For example: none0@pci0:7:3: class=0x068000 card=0x chip=0x71138086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82371AB PIIX4 Power Management Controller' class= bridge subclass = PCI-unknown This is the PIIX4M, (rev=0x03), known to be reliable. If you have a non-Intel chipset and you want to try it out, say set debug.acpi.timer_test=yes at the loader prompt, then boot. If your timer has problems, you should see messages like: acpi_timer0: timer is not monotonic: 0x1d52ab4f,0x1d52ab4e,0x1d5b89ea being displayed at random intervals. If after several minutes you do not see any of these messages, please send me the output of 'pciconf -lv' and I'll see whether we can safely detect your ACPI timer. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/dev/acpica acpi_pcib.c
This should fix problems people were having with PCI interrupt routing and ACPI. Please report any problems... msmith 2001/08/03 01:38:49 PDT Modified files: sys/dev/acpica acpi_pcib.c Log: Shoud build resources in the _CRS buffer. Oops. Submitted by: [EMAIL PROTECTED] [EMAIL PROTECTED] Revision ChangesPath 1.13 +2 -2 src/sys/dev/acpica/acpi_pcib.c -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: no new snapshot onftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/
wosch What happens? Is -current now so unstable that we cannot make a wosch snapshot anymore? current.jp.FreeBSD.org is for you until current.freebsd.org is back again; it's not a *mirror*, but has almost same features. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: What's touching my executables?
On Thu, 2 Aug 2001, David Greenman wrote: On Thu, Aug 02, 2001 at 06:28:59PM +, Christian Weisgerber ([EMAIL PROTECTED]) wrote: Probably the recent change (IIRC) that someone turned running an executable into a mtime change. There was no such change. I proposed a change that would update the atime, but that was not committed because it has some bad side effects. I didn't see that. I saw when you objected to me fixing the bug many years ago :-). The atime update was too slow for executables on nfs filesystems. I only used it to reduce the number of non-conformances found by the NIST Posix test suite. There is now a PR about this bug (kern/25777) with a very broken patch in it (it assume that all filesystems are ufs and hacks on ufs's IN_ACCESS flag). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
no new snapshot on ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/
Hi, the last -current snapshot is 6 weeks old. ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20010618-CURRENT/, What happens? Is -current now so unstable that we cannot make a snapshot anymore? -Wolfram -- Wolfram Schneider [EMAIL PROTECTED] http://wolfram.schneider.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: no new snapshot onftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/
No, the machine is dead and we haven't managed to get a replacement going yet. Hopefully in late August, as soon as everyone involved is back from vacation. - Jordan From: Wolfram Schneider [EMAIL PROTECTED] Subject: no new snapshot on ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/ Date: Thu, 2 Aug 2001 16:59:13 +0200 Hi, the last -current snapshot is 6 weeks old. ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20010618-CURRENT/, What happens? Is -current now so unstable that we cannot make a snapshot anymore? -Wolfram -- Wolfram Schneider [EMAIL PROTECTED] http://wolfram.schneider.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: libpam build broken in current
On Tue, Jul 31, 2001 at 08:53:56AM -0700, Manfred Antar wrote: libpam will not build if you don't have the stock ssh installed. I use ssh from ports. (libpam)502}make === modules === modules/pam_deny === modules/pam_ftp === modules/pam_nologin === modules/pam_opie === modules/pam_permit === modules/pam_radius === modules/pam_rootok === modules/pam_securetty === modules/pam_ssh building shared library pam_ssh.so /usr/libexec/elf/ld: cannot find -lssh pam_ssh should probably live under secure/ -- it's useless to people who don't have crypto installed. Kris PGP signature
quick query
sorry to bug this list with this question. I'd like to test the newer ray(4) driver that's in -CURRENT. What snapshot should I install? Is there anything else I should know before installing -CURRENT? (besides what the cutting edge section of the handbook says) Regards, Paul [EMAIL PROTECTED] http://www.tribble.net/ A free society is one where it is safe to be unpopular. -- Adlai Stevenson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: named -u bind
Date: Fri, 03 Aug 2001 19:50:24 -0700 From: Dima Dorfman [EMAIL PROTECTED] Are there any reasons not to use -u bind flag for named by default? IIRC the last time this came up somebody said something about it not being able to read zonefiles in some odd places where they like to put them. I.e., they want it to run as root so they can set their zonefile mode 600 or something. That sounds like someone overdoesed on perversity. I've been running named with user group bind (53) for nearly 2 years without significant problems: I made the directory named uses /var/namedb; everything in there is (still) owned by root, except for the sec subdirectory, which is owned by bind. (That is where the local copies of files retrieved from zone transfers go, for the zones for which my system is a slave. Having the named process unable to modify other files is a Good Thing. Oh, yeah: I also made /etc/named.conf a symlink to /var/namedb/named.conf.) I also made /var/run mode 1777, so that /var/run/named.pid could get created with minimal hassle. (Since the box has no general-purpose logins no keyboard, I have reasonable confidence that a local user isn't likely to abuse this.) Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
