Re: p5 ports don't respect LOCALBASE
Rich Winkel wrote: According to Lowell Gilbert: Rich Winkel <[EMAIL PROTECTED]> writes: The p5 ports seem especially bad about this. I understand the need for perl to be able to find its local packages, so after I There are ways to find perl packages without expecting them in LOCALBASE. --- Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mSyslog port and FreeBSD
Matt Edwards wrote: (wow, big surprise for me;) I have a few questions, but the one I must ask is, has anyone on a FreeBSD box got this to work WITH mysql? Have you tried to contact with a port maintainer ([EMAIL PROTECTED])? --- Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
the Donations Liaison Officer
Hello. Who is the Donations Liaison Officer? It's not clear from http://www.freebsd.org/donations/index.html -- Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: the Donations Liaison Officer
Giorgos Keramidas wrote: On 2004-07-04 06:25, Sergey Matveychuk <[EMAIL PROTECTED]> wrote: Who is the Donations Liaison Officer? It's not clear from http://www.freebsd.org/donations/index.html Originally, it was Michael Lucas who was the DLO, if my memory doesn't fail me. Unless this changed during the one year I've been away, he's still the guy behind the donations@ mail alias. Is it very important to know the exact person though? The mail alias points to the right person at any time. Not really. I've just miss "Just contact us at [EMAIL PROTECTED] with your offer" phrase. It should be made as mailto: link there. I've Cc: this to www@ and doc@ as offer. -- Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
route entries after ICMP redirect
I've got some problem with route entries that was created after ICMP redirect messages. They are never expired. Our default gateway (it's a HP switch) send ICMP redirect messages if it see a short path to destination. It's makes it not so overloaded. But pathes sometime changed. There is no problem with Windows workstations, they are rebooted daily. But my FreeBSD boxes hold dinamic route entries forever. I've looked through RFCs and Stevens' books and found no answer on what TTL for this entries. Now I just add route flush as cron job. But may be there is another way? -- Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: route entries after ICMP redirect
[EMAIL PROTECTED] wrote: If you want to handle this in a more clever way than a cron job you could write a small daemon which reads routing messages and does "the right thing" for whatever your situation is. I've explore a code and found I can do quite easy addition for dynamic routes - fill an expire field, check it periodicaly and remove expired entries (just like for arp entries). I think to do a sysctl variable for indication what time will set as expire values and set it to zero by default (no expires). -- Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: route entries after ICMP redirect
Uwe Doering wrote: This has been fixed in CVS in MAIN (rev. 1.52) and MFC'ed to RELENG_4 (rev. 1.37.2.5) and RELENG_5 (rev. 1.51.4.2) a couple of weeks ago: Oh, thank you! And thanks to [EMAIL PROTECTED] -- Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
diff: memory exhausted
How can I compare two big text files? -- Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: diff: memory exhausted
Chuck Swiger wrote: Sergey Matveychuk wrote: How can I compare two big text files? Does the -H option help any? (How big is big?) -H does not help. With the same message. It an output of mysqldump. 12Mb. -- Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: diff: memory exhausted
Dan Nelson wrote: or you can try installing the textproc/2bsd-diff port which apparently doesn't try to load the files into RAM, so it can work on large files more easily. Yes! That's it. Thanks! -- Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/etc/exports - a strange restriction
I'd like to share some directories hierarchy under /usr file system, but I don't want to share all /usr at all. On these lines in /etc/exports: /usr/tinderbox -ro -alldirs -maproot=0:0 localhost i get an error message: mountd[347]: -alldirs requested but /usr/tinderbox is not a filesystem mountpoint Why so strict restriction? -- Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /etc/exports - a strange restriction
Norbert Koch wrote: /usr/tinderbox -ro -alldirs -maproot=0:0 localhost As far as I know, it is a restriction of the nfs specification. If you only want to export a single directory, you could e.g. use mount_null/mount_nullfs(8). Well, in my example remote host is localhost. But if I need to share files on a network? I've made a quick look at RFC1813 but could not find this restriction. But why this restriction anyway for? It's very unconvenient. -- Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
passwords in /etc/group
Hello. How can I use password in /etc/group? If I can't, why man groups keep silence about it? Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
man malloc
I know it may be stupid, but I can't understand this sentence from malloc(3) man page: " The allocated space is suitably aligned (after possible pointer coercion) for storage of any type of object. " What does "suitable aligned for storage of *any* type of object" means? What is pointer coercion? I have no pointer before malloc() returns. -- Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: man malloc
Chuck Swiger wrote: What does "suitable aligned for storage of *any* type of object" means? On some platforms, it is either desirable or required that, say, a 8-byte double is stored at a memory location which is is also aligned to 8-bytes: Oh, it was told for different architectures. It's quite clear for me now. What is pointer coercion? I have no pointer before malloc() returns. Right. Well, malloc returns a (void *), but most people want to use the memory malloc returns to hold their own arrays, structs, whatever, which means that you need to be able to coerce the (void *) malloc gave you into whatever pointer type you want to actually use. So the memory malloc gives you needs to be aligned so that it's OK to be used for even the most restrictive datatype known to the system, commonly 8, 16, or 32 bytes. Pointer coercion means a type cast? I see now. I read it as 'force change of pointer value' before. Thanks, guys! -- Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bind9: dir for files with dynamic updates
Hi. As I can see there is a directory for dynamic updates: /var/named/etc/namedb/dynamic. But files with dynamic updates still placed next to zones files (/var/named/etc/namedb/master). I've looked for an option for it in documentation but failed. So, how can I use /var/named/etc/namedb/dynamic? -- Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: p7zip 4.20 -> 4.29
Andrew P. wrote: Last update was 4 months ago, wake up already :-) Yes, it's my mistake. I remember I've checked the port update but forget I still not commit it because of problems with build. -- Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade across NFS
Michael Collette wrote: > This problem only occurs when using portupgrade. Both pkg_delete and > pkg_deinstall work without error. Also, everything else in the process > that portupgrade goes through appears to work properly. Just that > /var/db/pkg directory won't delete when NFS mounted. Have you tried the last (2.1.1) version? I've fixed a few problems and one of them looks like yours. But it's not relate to NFS however. -- Dixi. Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade confusing '-P' and '-p'?
[EMAIL PROTECTED] wrote: > Hi, > > I'm in the middle of configuring a repeatable jail installation with some > ports - in a nutshell, I want to install from locally built packages, but > if not available locally I want to build the port myself _and_ create a > package for future repetition. To prevent remote fetching, I set the > PKG_FETCH variable to /bin/false as recommended. Here's the part I found > curious: I don't understand how you plan to build a port without of fetching of a distfile? -- Dixi. Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"