Re: C++ exceptions are broken in FreeBSD with gcc-compiled code?
Oh, this mail reminds me... > >I am not able to reproduce the problem here; I will compile the > >updated sources tonight to check if that changes anything: ...that I forgot to report that I did a cvsup and rebuild the system (7.0-STABLE), tonight. That did not change anything: I am not able to reproduce Yuri's problem on my machine. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: C++ exceptions are broken in FreeBSD with gcc-compiled code?
> > It works fine for me too, using FreeBSD 6-stable and the built-in gcc
> > 3.4.6
> > as well as with gcc 4.2.4 20080305 installed from ports.
> > No need to use -pthreads in either case
>
> This means that this issue is STABLE-7.0 specific.
I am not able to reproduce the problem here; I will compile the
updated sources tonight to check if that changes anything:
# uname -sr
FreeBSD 7.0-STABLE
# g++ --version
g++ (GCC) 4.2.1 20070719 [FreeBSD]
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
# cat exc.C
#include
#include
using namespace std;
int main() {
try {
throw string("String");
} catch (string s) {
cout << "Caught an exception \"" << s << "\"\n";
}
}
# g++ -o exc exc.C
# ./exc
Caught an exception "String"
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] newsyslog - don't compress first log file
> Ah -- well, then: by all means. I'm even more willing to test other
> folks' work than I am to hack away at code. :-}
>
> And since I had tested my own Perl script, I think I should be able to
> help out with this. :-)
>
> And "after Sunday" is not a problem at all: thank you!
I tested the changes that allow to specify that n logfiles should not
be compressed and attach a patch for version 1.107 of newsyslog.c to
this mail. The changes do not handle cases of changes to the
configfile while compressed and uncompressed logfiles already exist.
Again, here is a configfile example:
# logfilename [owner:group]mode count size when flags [/pid_file]
[sig_num]
/var/log/example.log644 89100 * J39
Then, I have a question concerning the code:
(void) snprintf(file1, sizeof(file1), "%s.%d", ent->log,
ent->numlogs);
(void) snprintf(zfile1, sizeof(zfile1), "%s%s", file1,
COMPRESS_POSTFIX);
snprintf(jfile1, sizeof(jfile1), "%s%s", file1,
BZCOMPRESS_POSTFIX);
Is there a reason why the third call of snprintf is not casted to
(void)?
Dirk
--- newsyslog.c.origSun Aug 12 14:13:38 2007
+++ newsyslog.c Sun Aug 12 14:36:51 2007
@@ -127,6 +127,8 @@
struct ptime_data *trim_at; /* Specific time to do trimming */
unsigned int permissions; /* File permissions on the log */
int flags; /* CE_COMPACT, CE_BZCOMPACT, CE_BINARY */
+ int nuncompact; /* number of rotations that should not
+* be compressed; -1 turns this off */
int sig;/* Signal to send */
int def_cfg;/* Using the rule for this file */
struct conf_entry *next;/* Linked list pointer */
@@ -1187,6 +1189,11 @@
}
for (; q && *q && !isspacech(*q); q++) {
+ if (isdigit(*q)) {
+ working->nuncompact = strtol(q, NULL, 10);
+ while(isdigit(*(q+1))) q++;
+ continue;
+ }
switch (tolowerch(*q)) {
case 'b':
working->flags |= CE_BINARY;
@@ -1456,6 +1463,12 @@
(void)rename(zfile1, zfile2);
}
change_attrs(zfile2, ent);
+ if ((flags & (CE_COMPACT | CE_BZCOMPACT)) &&
+ (ent->nuncompact != -1) &&
+ (numlogs_c == ent->nuncompact)) {
+ free_or_keep = KEEP_ENT;
+ save_zipwork(ent, NULL, ent->fsize, file2);
+ }
}
if (ent->numlogs > 0) {
@@ -1494,7 +1507,8 @@
swork = NULL;
if (ent->pid_file != NULL)
swork = save_sigwork(ent);
- if (ent->numlogs > 0 && (flags & (CE_COMPACT | CE_BZCOMPACT))) {
+ if (ent->numlogs > 0 && (flags & (CE_COMPACT | CE_BZCOMPACT))
+ && ent->nuncompact == -1) {
/*
* The zipwork_entry will include a pointer to this
* conf_entry, so the conf_entry should not be freed.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] newsyslog - don't compress first log file
> We could extend the 'count' field to accept 'N+M'. N being the number of > plain log files and M the number of compressed ones. > > This would also negate the need for a new flag. It could also be done with a numerical flag "n" where n is a number that specifies the extension of the logfile up to which no compression should be done. An example configfile entry for 90 rotate logs and 40 uncompressed ones would look as follows: # logfilename [owner:group]mode count size when flags [/pid_file] [sig_num] /var/log/example.log644 89100 * J39 I already implemented that approach and am currently testing it. When finished, I will post a patch so that David can try it, but that will not happen before Sunday, because I am a little bit busy with other things. Most of the changes handle the compressed and uncompressed logs and it will be little work to modify it for the N+M count-field approach. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] newsyslog - don't compress first log file
> How about using the flag "0" similar to that in newsyslog written by > Theodore Ts'o of MIT Project Athena: Sorry, I have to correct myself: The flag "0" appears in the enhanced version of newsyslog that is maintained by Greg A. Woods. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] newsyslog - don't compress first log file
> How about aditional flag ("X") to newsyslog, which don't compress first
> log file?
How about using the flag "0" similar to that in newsyslog written by
Theodore Ts'o of MIT Project Athena:
0 The 0 flag means that the most recent archive of the log
file (i.e. the one that ends in ``.0'') should not be
compressed even when the Z flag is given. (This flag may
also be specified as P for compatability with NetBSD.)
This flag is necessary when managing log files written
directly to by long-running processes (eg. smail, httpd,
etc.). This flag also makes it more convenient to browse
through the most recently archived log file without hav-
ing to first uncompress it or use tools like zmore, or
zgrep, etc.
Best regards,
Dirk
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cloning a FreeBSD HDD
Hi, > This is my first day on the list so please pardon me if I am on the wrong > list and any mistakes I make. > > I would like to create a bootable clone of a HDD running BSD version 4.8. I > have experience of cloning linux machines successfully but understand that > freebsd is a little different. please, try to clone your disk as described in the FAQ "9.2. How do I move my system over to my huge new disk?": http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NEW-HUGE-DISK Following that advice results in a bootable clone of your disk. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: My wish list for 6.1
> > By the way, I tried to search the archive (doc@) for a possible > > earlier discussion of this subject but have a hard time to find proper > > words to search for... > > http://lists.freebsd.org/pipermail/freebsd-doc/2005-October/009027.html Thanks! Well, seems as if some people's heads are already working on this subject... Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: My wish list for 6.1
> Yep, I really like this. The current mess is impossible to maintain > (and also impossible to read). Yesterday I tried to update the kernel > configuration chapter to cover 6.0, but I gave up since there are "do > this for 4.X, do that for 5.X, and maybe this too for 6.X" everywhere. Seems as if my imagination was correct ;-) By the way, I tried to search the archive (doc@) for a possible earlier discussion of this subject but have a hard time to find proper words to search for... Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: My wish list for 6.1
> This is exactly the idea that I have been pimping to anyone who will > listen for the last three months or so. I also think that it is > advantageous for users who are using, say 4.2, to be able to find > documentation for 4.2 without having to interpret a nest of "if you have > 4.x do this, if 5.0 through 5.3 do that, else do the other". I don't > think it's a lot of work to just branch the handbook (and FAQ > if we decide to keep it) - in fact, for me, it would be a definite win - > at release time, but it just doesn't seem to be what other people want > done. I would like to add that I could imagine that it would be easier for authors to just change/add some documentation that matches the target release and not to have to think about "if version=something else ..." constructs. Also, sometimes it is good to be able to just throw away things that are out-of-date. > I would encourage those interested to ask about it on [EMAIL PROTECTED] Well, I would be surprised if that hasn't already been discussed. Have to search the archives... Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: My wish list for 6.1
> On Monday 19 December 2005 04:34, Dirk GOUDERS wrote: Well, I did not write the quoted text, but Scott Long did. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: My wish list for 6.1
> 3. Full review and update of the install docs, handbook, FAQ, etc. > There are sections that are embarrassingly out of date (one section of > the handbook apparently states that we only support a single brand of > wifi cards). A co-worker of mine tried to install 6.0 using just the > handbook install guide, and discovered that it really doesn't match > reality anymore, in both big and small ways. Contact me directly if > you would like his list of comments. I am wondering if it wouldn't be advantageous to have "versioned" documents that just cover one specific release and not to cover all realeases in single documents. I could imagine that it is harder to cover everything in single documents than to perhaps copy the existing documentation when a new branch is created and edit it to match just the new release. Maybe, I do not realize how much more work this would be but it would probably enforce regular reviews of the documentation and the readers would benefit from it. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: preferable way to control kernel module
> >>Shouldn't that be no problem if he sets the offset parameter to
> >>SYSCALL_MODULE to NO_SYSCALL (get the next free offset)?
> >
> >
> > But then you have to communicate the syscall number out to your userland
> > applications somehow, and the applications have to know how to invoke a
> > syscall by hand (perhaps they could use the syscall() function, but still)
> .
> >
> It is not a big problem. Look at the following piece of code:
>
>
> /* Kernel module portion of code. */
> static int my_syscall = NO_SYSCALL;
> static struct sysent my_sysent = {
> 2, /* sy_arg */
> (sy_call_t *)&my_func /* sy_call */
> };
> SYSCALL_MODULE(my_syscall_name, &my_syscall, &my_sysent,
> NULL, NULL);
>
>
> /* User-land portion of code. */
> int get_syscall(const char *syscall_name)
> {
> struct module_stat stat;
> int mod_id;
> int syscall_num;
>
> if ((mod_id = modfind(syscall_name)) < 0)
> return (-1);
>
> stat.version = sizeof(stat);
> if (modstat(mod_id, &stat) < 0)
> return (-1);
>
> return (stat.data.intval);
> }
>
> ...
>
> syscall_num = get_syscall("my_syscall_name");
>
> /* Issue a syscall with necessary parameters. */
> syscall(syscall_num, ...);
That is roughly what I accidently played with, today.
Don't know about the probability that there may be no free offset,
though.
Dirk
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: preferable way to control kernel module
> > Thank you for advise. But I wonder: what is wrong with syscall approach > > (via SYSCALL_MODULE macro)? > > I just haven't done one personally. I think there's also a lot more potenti > al > for collisions when trying to pick a syscall number versus picking a string > name for a sysctl or /dev entry. Shouldn't that be no problem if he sets the offset parameter to SYSCALL_MODULE to NO_SYSCALL (get the next free offset)? Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Include files that depend on include files
> The above lines came from FreeBSD's /usr/include/sys/stat.h > > Note that it includes and not > > There are many other examples in the FreeBSD system includes, at > least once you get to the 5.x-series of FreeBSD. I don't remember > if we were doing that in the 4.x-series. In 4.x I did not find any referece to but Jeremie pointed me to another example. And now, I also can have a look at the newer version of stat.h via cvsweb. Thanks a lot. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Include files that depend on include files
> > Can you point me to a real-life example where such a mechanism is > > used? I'd like to have a closer look at it. > > /usr/include/sys/types.h :-) Thank you :-) Now, I found the comment in /usr/include/machine/ansi.h that also describes this mechanism. Thanks for all other answers, as well. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Include files that depend on include files
> To get around this in user-space, we do things like create > /usr/include/sys/_types.h > > And then our include files include *that* file, and do not include > the standard . This file, in turn, does > not define any of the actual symbols. Let's say that some include > file needs to know what typedef for 'off_t' is. The sys/_types.h > file defines __off_t, and then the include file which needs off_t > will do something like: > > #include > #ifndef _OFF_T_DECLARED > typedef __off_t off_t; > #define _OFF_T_DECLARED > #endif > > Thus, it has only defined the one name it actually needs, instead > of defining all of the standard symbols in the real sys/types.h. Can you point me to a real-life example where such a mechanism is used? I'd like to have a closer look at it. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Include files that depend on include files
> This is intentational. We try to avoid having headers bring in more > then absolutly required when included. I'm not sure what your second > question means. With my second question I wanted to ask if this intention is only for kernel level code or a general one. I am asking this, because somewhen in a project that I was not actually participating in I heard or read a rule that roughly said: "all include files have to include all files they depend on and compile cleanly", but that project was on a user space program. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Include files that depend on include files
Hello, I am currently playing with the KLD facility on a 4.11-STABLE system and noticed that there are some include files that need other files included before them, e.g. sys/module.h and sys/linker.h cannot be preprocessed/compiled without including other necessary files before them. Is that intentional? And if yes, is there a difference of such a "rule" between "kernel include files" and those that are normally included in "user space code"? Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Finding an illegal instruction in gnucash/guile
> gdb claims the problem is in libguile. I've tried rebuilding it with > different CPU and optimisation options (in case I've triggered a gcc > bug) but the SIGILL remains. > > I've had a look through google and not found anything relevant. > > Does anyone have any suggestions other than rebuilding the ports from > scratch with different CPUTYPE and/or CFLAGS? (I'm currently using > CPUTYPE=athlon-xp and CFLAGS=-O -g). I had a similar (if not the same) problem on a 4.11-STABLE machine. Actually, I am running gnucash on two different 4.11-STABLE machines -- on one, it worked, on the other, where I installed it some days ago it didn't. Then, I cvsup'ed both machines and the first port I installed on both was gnucash (the only difference betweeen the two machines was the order the ports were installed) and now, it works on both machines. This information seemed too few to me to file a PR but maybe it helps you. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: page fault in ugenpoll()
> The control endpoint /dev/ugen0 does not support polling. But > polling /dev/ugen0.X should work, where "X" is a number. > > "ugenpoll()" in "/sys/dev/usb/ugen.c" should have something like this added: > > if(control endpoint) return POLLNVAL; /* and not "return EIO;" */ > > Please file a PR on this issue using: > > >Category: usb Thank you. I modified ugen.c in the way you suggested and filed a PR. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: page fault in ugenpoll()
Hello,
just for completeness, I want to provide a simple program that causes
a kernel panic when invoked with the argument /dev/ugen0:
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
int fd;
int nfd;
char *path = argv[1];
struct pollfd pfd[1];
fd = open(path, O_RDWR);
if ( fd < 0 ) {
fprintf(stderr, "%s: %s\n", path, strerror(errno));
exit(1);
}
pfd[0].fd = fd;
pfd[0].events = POLLHUP;
pfd[0].revents = 0;
nfd = poll(pfd, 1, 10);
if ( nfd < 0 ) {
fprintf(stderr, "poll(2): %s\n", strerror(errno));
exit(1);
}
printf("nfd = %d\n", nfd);
close(fd);
exit(0);
}
> Hello,
>
> on a machine
>
> FreeBSD karga.hank.home 4.11-STABLE FreeBSD 4.11-STABLE #2: Thu May 19 12:32
> :50 CEST 2005 [EMAIL PROTECTED]:/usr/src/sys/compile/KARGA i386
>
> I am playing with a Cryptoflex e-gate USB token and get kernel
> panics when invoking a program openct-control to access it:
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x3
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc027177b
> stack pointer = 0x10:0xccde7d40
> frame pointer = 0x10:0xccde7d50
> code segment= base 0x0, limit 0xf, type 0x1b
> = DPL 0, pres 1, def32 1, gran 1
> processor eflags= interrupt enabled, resume, IOPL = 0
> current process = 173 (ifdhandler)
> interrupt mask = bio
> trap number = 12
> panic: page fault
>
> The IP points to the following line in the function ugenpoll (line
> 1445 in ugen.c):
>
> switch (sce->edesc->bmAttributes & UE_XFERTYPE)
>
> Examining sce with gdb gives:
> (kgdb) print sce
> $1 = (struct ugen_endpoint *) 0x68c060
> (kgdb) print sce->edesc
> Cannot access memory at address 0x68c064.
> (kgdb)
>
> The software that I am trying to use might be erroneous, but I am
> wondering that it causes kernel panics by accessing /dev/ugen0.
>
> Dirk
> ___
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
page fault in ugenpoll()
Hello, on a machine FreeBSD karga.hank.home 4.11-STABLE FreeBSD 4.11-STABLE #2: Thu May 19 12:32:50 CEST 2005 [EMAIL PROTECTED]:/usr/src/sys/compile/KARGA i386 I am playing with a Cryptoflex e-gate USB token and get kernel panics when invoking a program openct-control to access it: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x3 fault code = supervisor read, page not present instruction pointer = 0x8:0xc027177b stack pointer = 0x10:0xccde7d40 frame pointer = 0x10:0xccde7d50 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 173 (ifdhandler) interrupt mask = bio trap number = 12 panic: page fault The IP points to the following line in the function ugenpoll (line 1445 in ugen.c): switch (sce->edesc->bmAttributes & UE_XFERTYPE) Examining sce with gdb gives: (kgdb) print sce $1 = (struct ugen_endpoint *) 0x68c060 (kgdb) print sce->edesc Cannot access memory at address 0x68c064. (kgdb) The software that I am trying to use might be erroneous, but I am wondering that it causes kernel panics by accessing /dev/ugen0. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.4-RELEASE: 3c905B-TX only works in promicuous mode
> Have you tried turning off RXCSUM? Sorry that I forgot to mention that I also tried to turn off RXCSUM as well as VLAN_MTU. Those changes also did not help. Dirk ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.4-RELEASE: 3c905B-TX only works in promicuous mode
Hello, I installed 5.4-RELEASE on one of my machines and have the problem that my 3c905B-TX NIC seems to accept packets only when in promiscuous mode. (I first noticed, that everything works when tcpdump is running and then just used `ifconfig xl0 promisc' to get the NIC working) Sending packets seems to work, because if I try to ping another machine and run tcpdump on the ping-target, I see the ARP requests as well as the ARP replies but the replies don't seem to get accepted/recognized by the ping-source -- until I put the NIC on the ping-source into promiscuous mode. Once the 5.4-machine knows the ping-target's MAC address (after having been in promiscuous mode), I see the echo requests and replies on the ping-target but the replies also don't get accepted/recognized by the ping source. When I use another NIC (RealTek 8139 10/100BaseTX) on the 5.4-machine, everything works fine. Also, the 3c905B-TX NIC worked fine under 4.11-STABLE. As everything works fine when I use another NIC, I thought that there might be a problem with the xl driver and I tried to use the earliest if_xl.c and if_xlreg.h from the RELENG_5 branch but that didn't help. Then, I tried to use the driver files that were used in the 4.11-STABLE version under which the NIC worked well, but that turned out not to be such a trivial task. I would be glad if someone could give me a hint on how I can solve this problem? Dirk Here are some details about my network setup: # ifconfig xl0 xl0: flags=28943 mtu 1500 options=9 inet 192.168.252.9 netmask 0xff00 broadcast 192.168.252.255 inet6 fe80::250:daff:fedf:1c4d%xl0 prefixlen 64 scopeid 0x1 ether 00:50:da:df:1c:4d media: Ethernet autoselect (100baseTX ) status: active # netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.252.1 UGS 00xl0 127.0.0.1 127.0.0.1 UH 00lo0 192.168.252link#1 UC 00xl0 192.168.252.1 link#1 UHLW1 17xl0 192.168.252.2 00:50:22:e9:74:37 UHLW0 89xl0430 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%xl0/64 link#1UC xl0 fe80::250:daff:fedf:1c4d%xl0 00:50:da:df:1c:4d UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#2UHL lo0 ff01::/32 ::1 U lo0 ff02::%xl0/32 link#1UC xl0 ff02::%lo0/32 ::1 UC lo0 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ECU files and MLB BIOS
Hi, I am having understanding/translation problems, again. Can anyone help me with the terms "ECU files" and "MLB BIOS" (Hackers section of the FAQ)? Thanks, Dirk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: More press
> Dirk GOUDERS writes: > > Oh, sorry -- my "browse-url-at-mouse" function made > > > > http://www.zdnet.com/zdtv/screensavers/answerstips/story/02c36562c23246242 c00.html > > > > of it... > > Netscape uses commans to separate parameters to the OpenURL command. > Fortunately, the API is open and documented, so there's nothing to > stop someone from writing a small command-line util that does the > equivalent of "netscape -remote" except faster and better. Well, having read all of your remarks, I noticed, that emacs' lisp code "browse-url.el" causes the generation of http://www.zdnet.com/zdtv/screensavers/answerstips/story/02c36562c23246242 c00.html instead of http://www.zdnet.com/zdtv/screensavers/answerstips/story/0%2c3656%2c2324624%2 c00.html I fixed that (little) problem on my machine and sent a bug-report. Now, I enjoy loading URLs containing commas :-) Dirk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: More press
> Dirk GOUDERS <[EMAIL PROTECTED]> writes: > > Oh, sorry -- my "browse-url-at-mouse" function made > > > > http://www.zdnet.com/zdtv/screensavers/answerstips/story/02c36562c23246242 c00.html > > > > of it... > > Netscape uses commans to separate parameters to the OpenURL command. > Fortunately, the API is open and documented, so there's nothing to > stop someone from writing a small command-line util that does the > equivalent of "netscape -remote" except faster and better. Well, having read all of your remarks, I noticed, that emacs' lisp code "browse-url.el" causes the generation of http://www.zdnet.com/zdtv/screensavers/answerstips/story/02c36562c23246242 c00.html instead of http://www.zdnet.com/zdtv/screensavers/answerstips/story/0%2c3656%2c2324624%2 c00.html I fixed that (little) problem on my machine and sent a bug-report. Now, I enjoy loading URLs containing commas :-) Dirk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: More press
> > > > > There is a short but sweet[1] article on ZDNet today regarding FreeBSD: > > > > > > http://www.zdnet.com/zdtv/screensavers/answerstips/story/0,3656,2324624,00.html > > > > Hmm, can't find that sweet thing -- typo? > > Nope, it worked fine for me. Given how short it is, this article really packs > a POSITIVE punch for FreeBSD. Here's the text: > > *SNIP* Oh, sorry -- my "browse-url-at-mouse" function made http://www.zdnet.com/zdtv/screensavers/answerstips/story/02c36562c23246242c00.html of it... Anyway, thanks for the text :-) Dirk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: More press
> > > > > There is a short but sweet[1] article on ZDNet today regarding FreeBSD: > > > > > > > > http://www.zdnet.com/zdtv/screensavers/answerstips/story/0,3656,2324624,00.html > > > > Hmm, can't find that sweet thing -- typo? > > Nope, it worked fine for me. Given how short it is, this article really > packs > a POSITIVE punch for FreeBSD. Here's the text: > > *SNIP* Oh, sorry -- my "browse-url-at-mouse" function made http://www.zdnet.com/zdtv/screensavers/answerstips/story/02c36562c23246242c00.html of it... Anyway, thanks for the text :-) Dirk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: More press
> There is a short but sweet[1] article on ZDNet today regarding FreeBSD: > > http://www.zdnet.com/zdtv/screensavers/answerstips/story/0,3656,2324624,00.html Hmm, can't find that sweet thing -- typo? Dirk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: More press
> There is a short but sweet[1] article on ZDNet today regarding FreeBSD: > > http://www.zdnet.com/zdtv/screensavers/answerstips/story/0,3656,2324624,00.html Hmm, can't find that sweet thing -- typo? Dirk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SURVEY: Sound cards that work under FreeBSD
Hi Warner, > : The only line I had to add to my kernel config file was: > : > : device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 > : > : (This causes a message "pcm0 not found" to appear at boot time but > : just ignoring it seems to be o.k. - allthough I would prefer > : not to see it, at all.) > > device pcm0 > > does the trick for me. I think that will work in 3.2. > > -current fixes the problem with psm0 not found. > Thanks for the hint! I got rid of the error message :-) What I still don't understand is the following message at boot time: pcm1: using I/O space register mapping at 0xe400 I am wondering why there is a message concerning pcm1 instead of pcm0... Dirk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: SURVEY: Sound cards that work under FreeBSD
Hi Warner, > : The only line I had to add to my kernel config file was: > : > : device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 > : > : (This causes a message "pcm0 not found" to appear at boot time but > : just ignoring it seems to be o.k. - allthough I would prefer > : not to see it, at all.) > > device pcm0 > > does the trick for me. I think that will work in 3.2. > > -current fixes the problem with psm0 not found. > Thanks for the hint! I got rid of the error message :-) What I still don't understand is the following message at boot time: pcm1: using I/O space register mapping at 0xe400 I am wondering why there is a message concerning pcm1 instead of pcm0... Dirk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SURVEY: Sound cards that work under FreeBSD
Here's the information about the sound card I am working with: > 1) The sound card make and model/chipset. Please be as specific as you can > with >board rev numbers if possible. Please include wether the card is ISA or > PCI. My sound card is a SBPCI128 by Creative Labs. > 2) FreeBSD version(s) it was tested with. List *all* versions of FreeBSD for >which you can verify that the sound card does/doesn't work (don't include >-BETA or -SNAP releases but dates on -STABLE and -CURRENT branches are >welcome). I only used the card with FreeBSD 3.2 > 3) Appropriate lines from your kernel config file / PNP setup. i.e. what did >you have to do to get this card working? Did you need patches not > committed >to a particular branch (if so URLs would be welcome)? Do you use OSS > drivers >instead? The only line I had to add to my kernel config file was: device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 (This causes a message "pcm0 not found" to appear at boot time but just ignoring it seems to be o.k. - allthough I would prefer not to see it, at all.) > 4) Sample dmesg output for properly configured device. Show the world what >boot messages relate to the device after properly configured. These are the messages that appear previous to the message "pcm0 not found": es1: rev 0x01 int a irq 5 on pci0.9.0 pcm1: using I/O space register mapping at 0xe400 > 5) Miscellaneous notes. State anything "not obvious" to the casual FreeBSD >user. Good examples might be, "volume is 0 by default, use mixer(1) to >adjust at boot time," or "sh MAKEDEV snd1 for the 1st device, not snd0." I had to build the audio device snd1: # cd /dev # sh MKDEV snd1 and to use the mixer to set the volume to another value than 0. I use the following script /usr/local/etc/rc.d/mixer.sh at boot time: #!/bin/sh /usr/sbin/mixer vol 60:60 pcm 60:60 cd 60:60 > 6) Is it OK to publish your e-mail address / name as the contributor of this >information? You may type in an anti-spam version of your e-mail address >below if you would like that option instead. Well, I guess, I should not be listed as the contributor, because I catched these information out of the mailing lists and would prefer the original poster to appear as the contributor. Cheers, Dirk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: SURVEY: Sound cards that work under FreeBSD
Here's the information about the sound card I am working with: > 1) The sound card make and model/chipset. Please be as specific as you can with >board rev numbers if possible. Please include wether the card is ISA or PCI. My sound card is a SBPCI128 by Creative Labs. > 2) FreeBSD version(s) it was tested with. List *all* versions of FreeBSD for >which you can verify that the sound card does/doesn't work (don't include >-BETA or -SNAP releases but dates on -STABLE and -CURRENT branches are >welcome). I only used the card with FreeBSD 3.2 > 3) Appropriate lines from your kernel config file / PNP setup. i.e. what did >you have to do to get this card working? Did you need patches not committed >to a particular branch (if so URLs would be welcome)? Do you use OSS drivers >instead? The only line I had to add to my kernel config file was: device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 (This causes a message "pcm0 not found" to appear at boot time but just ignoring it seems to be o.k. - allthough I would prefer not to see it, at all.) > 4) Sample dmesg output for properly configured device. Show the world what >boot messages relate to the device after properly configured. These are the messages that appear previous to the message "pcm0 not found": es1: rev 0x01 int a irq 5 on pci0.9.0 pcm1: using I/O space register mapping at 0xe400 > 5) Miscellaneous notes. State anything "not obvious" to the casual FreeBSD >user. Good examples might be, "volume is 0 by default, use mixer(1) to >adjust at boot time," or "sh MAKEDEV snd1 for the 1st device, not snd0." I had to build the audio device snd1: # cd /dev # sh MKDEV snd1 and to use the mixer to set the volume to another value than 0. I use the following script /usr/local/etc/rc.d/mixer.sh at boot time: #!/bin/sh /usr/sbin/mixer vol 60:60 pcm 60:60 cd 60:60 > 6) Is it OK to publish your e-mail address / name as the contributor of this >information? You may type in an anti-spam version of your e-mail address >below if you would like that option instead. Well, I guess, I should not be listed as the contributor, because I catched these information out of the mailing lists and would prefer the original poster to appear as the contributor. Cheers, Dirk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 "Starfire" ethernet controller driver and plus question compaq presario dec et
o.k., Bill, I'll try to translate it for you: > > $B?9ED$G$9!#(B My name is Morita. > > > > > > These are Adaptec's replacements for its older DEC 21x4x-based multiport > > > > $B$3$N%I%i%$%P!<$OL5$/$J$k$N$G$7$g$&$+!)(B->DEC 21x4x-based > > no more supllyed ->DEC 21x4x-based Are these drivers lost? (Maybe in the meaning of no more supported.) > > Sorry, but I'm just a dumb american: I can't read this. > > > > line of adapters. All cards support 10/100 speeds in full or half duplex . > > > The multiport cards consist of multiple AIC-6915 chips linkec via a PCI > > > to PCI bridge. Currently I have only tested the ANA-62022 dual port card , > > > however all of them should work equally well. The 64-bit cards will work > > > in a 32-bit slot on most newer machines. > > > > > > > $B%3%s%Q%C%/!!(BPRESARIO$B!!(B2274$B!!$K(BFreeBSD3.2$B%$%s%9%H!<%k$7$?$N$G$9$,!"(B > > NIC$B!'!!(BDEC 21143-based > > $B$H%S%G%*%+!<%I!'(bsis5598$...@_dj$,$&$^$/$$$-$^$;$s!"8=:_(B > > $BF0$+$7$F$k(B > > $BJ}$,$$$i$7$?$i65$($F$/$...@$5$$!#(B I installed FreeBSD 3.2 on a Compaq PRESARIO 2274 but my DEC 21143-based NIC and SiS5598 video card do not work well (maybe at all). Can you please tell me, how to get them work? > > I can't read this either. :( I guess, I understood the question, but I cannot answer it. Can you? Dirk > > -Bill > > -- > = > -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu > Work: wp...@ctr.columbia.edu | Center for Telecommunications Researc h > Home: wp...@skynet.ctr.columbia.edu | Columbia University, New York City > = > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" > = > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 "Starfire" ethernet controller driver and plus question compaq presario dec et
o.k., Bill, I'll try to translate it for you: > > $B?9ED$G$9!#(B My name is Morita. > > > > > > These are Adaptec's replacements for its older DEC 21x4x-based multiport > > > > $B$3$N%I%i%$%P!<$OL5$/$J$k$N$G$7$g$&$+!)(B->DEC 21x4x-based > > no more supllyed ->DEC 21x4x-based Are these drivers lost? (Maybe in the meaning of no more supported.) > > Sorry, but I'm just a dumb american: I can't read this. > > > > line of adapters. All cards support 10/100 speeds in full or half duplex . > > > The multiport cards consist of multiple AIC-6915 chips linkec via a PCI > > > to PCI bridge. Currently I have only tested the ANA-62022 dual port card , > > > however all of them should work equally well. The 64-bit cards will work > > > in a 32-bit slot on most newer machines. > > > > > > > >$B%3%s%Q%C%/!!(BPRESARIO$B!!(B2274$B!!$K(BFreeBSD3.2$B%$%s%9%H!<%k$7$?$N$G$9$,!"(B > > NIC$B!'!!(BDEC 21143-based >$B$H%S%G%*%+!<%I!'(BSiS5598$B$N@_Dj$,$&$^$/$$$-$^$;$s!"8=:_(B > > $BF0$+$7$F$k(B > > $BJ}$,$$$i$7$?$i65$($F$/$@$5$$!#(B I installed FreeBSD 3.2 on a Compaq PRESARIO 2274 but my DEC 21143-based NIC and SiS5598 video card do not work well (maybe at all). Can you please tell me, how to get them work? > > I can't read this either. :( I guess, I understood the question, but I cannot answer it. Can you? Dirk > > -Bill > > -- > = > -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu > Work: [EMAIL PROTECTED] | Center for Telecommunications Researc h > Home: [EMAIL PROTECTED] | Columbia University, New York City > = > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" > = > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
