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
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
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
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
___
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
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.
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
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
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
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
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
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
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
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 sys/types.h. This sys/_types.h file, in turn, does
not define any of the actual symbols. Let's say that some include
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
The above lines came from FreeBSD's /usr/include/sys/stat.h
Note that it includes sys/_types.h and not sys/types.h
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
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
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
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
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
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
Hello,
just for completeness, I want to provide a simple program that causes
a kernel panic when invoked with the argument /dev/ugen0:
#include stdio.h
#include stdlib.h
#include fcntl.h
#include sys/types.h
#include poll.h
#include errno.h
int main(int argc, char *argv[])
{
int fd;
int
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
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
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
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.
F
Dirk GOUDERS h...@musashi.et.bocholt.fh-ge.de 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
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
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
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
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
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
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
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
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
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?
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?
37 matches
Mail list logo
