Why not to move all fs code (ufs, procfs, isofs, etc) to /sys/fs? It allready
contain hpfs subdir. What you guys think about it?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Ilmar S. Habibulin wrote:
Why not to move all fs code (ufs, procfs, isofs, etc) to /sys/fs? It allready
contain hpfs subdir. What you guys think about it?
This has been discussed and considered a GOOD IDEA but it hasn't
happenned yet. there is also teh miscfs directory that could be
I'm not able to get X11 connection forwarding to work anymore. I've tracked
it down to the packet sent for SSH_CHANNEL_X11_OPEN being completely bogus,
therefore trying to extract the "proto" and "data" fails, and the connection
doesn't work.
Has anyone tried it recently and gotten it to work?
On 17-Apr-00 Brian Fundakowski Feldman wrote:
I'm not able to get X11 connection forwarding to work anymore.
Just a data point, it works fine in 4-stable (about a week old).
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
At 10:01 -0400 04/17/2000, Brian Fundakowski Feldman wrote:
Has anyone tried it recently and gotten it to work?
Yes, sure. Check your config file.
$ cat ~/.ssh/config | grep ^ForwardX11
ForwardX11 yes
--
KEK, High Energy Accelerator
"Robert" == Robert Watson [EMAIL PROTECTED] writes:
Robert Not sure if this should go to -current or -stable, since we
Robert seem to get a lot of instant MFC's these days :-). I upgraded
Robert a notebook from 4.0-RELEASE to -STABLE last night. After
Robert doing so, I noticed that the
An attempt to kldload driver suddenly failed with
message from Subject. Everything was ok before.
Sources cvsuped hour ago, kernel and driver recompiled.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
John Hay wrote:
: Are there any datasheets available for this bridge ?
Yes. However, I've had several reports of the lucent wavelan bridge
working flawlessly.
I recall (but might be wrong) that most if not all sucess stories are
on notebooks with the TI-1225 on the motherboard. Maybe
hello!
all right ... things take longer then we expect them to take.
the kernel (everything cvsup'd on saturday) boot fine and the array
controller is detected just perfect. also fdisk'ing, disklabel'ing and
newfs'ing the drive was no problem. i copied almost the whole current source
tree on
hello, people,
i was playing with setrlimit(), break() and mmap() in freebsd 4.0 and
in CURRENT, and i have a couple of questions:
1. kernel code for break() syscall checks if the requested value for the
data segment size is more than RLIMIT_DATA, and, if yes, it just returns
On Mon, 17 Apr 2000, Shin-ichi YOSHIMOTO wrote:
At 10:01 -0400 04/17/2000, Brian Fundakowski Feldman wrote:
Has anyone tried it recently and gotten it to work?
Yes, sure. Check your config file.
That doesn't explain the failures here. Look. The initial
SSH_CHANNEL_X11_OPEN is totally
I have a machine which isn't doing much right now, so I have decided
to set it up as an automatic "FreeBSD Build checker".
Once per day the machine cvsups, checks out a virgin source tree,
tries to build GENERIC, GENERIC98, LINT and world. If any of these
builds fail it will send a report
I have a machine which isn't doing much right now, so I have decided
to set it up as an automatic "FreeBSD Build checker".
Welcome to the current.freebsd.org game. :)
Once per day the machine cvsups, checks out a virgin source tree,
tries to build GENERIC, GENERIC98, LINT and world. If
Hi,
I have a patch against these warnings. They are the result of a function
being called with a pointer to a function rather than a string...
/otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1655:
warning: passing arg 1 of `warning' from incompatible pointer type
In message [EMAIL PROTECTED], "Jordan K. Hubbard" writes:
That said, I've also done a singularly bad job of actually letting
people know that build-reports even exists so I wouldn't expect you or
anyone else (except maybe Bill Paul) to have known about it. It's
just an alias on hub.freebsd.org
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: awi.o(.text+0x3b4): undefined reference to `memcmp'
: awi.o(.text+0x3cf): undefined reference to `memset'
What I want to know is why I don't get these with the GENERIC + awi
config file I have :-(
Warner
To Unsubscribe: send mail to
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: awi.o(.text+0x3b4): undefined reference to `memcmp'
: awi.o(.text+0x3cf): undefined reference to `memset'
What I want to know is why I don't get these with the GENERIC + awi
config file I
But does this also check the kernels ? It was my understanding that
it only did world/release ?
It only does the world/release (and it's the chrooted make release
"world build" which is reported on, not the host system's BTW) but
could easily add a kernel build just for the benefit of the
: awi.o(.text+0x3b4): undefined reference to `memcmp'
: awi.o(.text+0x3cf): undefined reference to `memset'
What I want to know is why I don't get these with the GENERIC + awi
config file I have :-(
Are you compiling with optimization turned on? I believe mem* are
inlined if optimization
I didn't know here to send this, but I thought that other people trying
to keep current might have had this problem before:
When I run cvsup with the default cvsup file from
/usr/share/examples/cvsup/cvs-supfile (after putting in the correct cvsup
server address) it crashes:
bash-2.03# cvsup
In message [EMAIL PROTECTED] Nate Williams writes:
: Are you compiling with optimization turned on? I believe mem* are
: inlined if optimization is enabled.
Don't think so. Both build -O.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
: Are you compiling with optimization turned on? I believe mem* are
: inlined if optimization is enabled.
Don't think so. Both build -O.
Poul's build may not have optimization turned on, since it's controlled
by /etc/make.conf.
Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
In message [EMAIL PROTECTED] Nate Williams writes:
: : Are you compiling with optimization turned on? I believe mem* are
: : inlined if optimization is enabled.
:
: Don't think so. Both build -O.
:
: Poul's build may not have optimization turned on, since it's controlled
: by
: : Are you compiling with optimization turned on? I believe mem* are
: : inlined if optimization is enabled.
:
: Don't think so. Both build -O.
:
: Poul's build may not have optimization turned on, since it's controlled
: by /etc/make.conf.
It isn't something specific to Poul's
In message [EMAIL PROTECTED] Nate Williams writes:
: I thought that the use of mem* and friends violated KNF.
They do, iirc. However, this driver tries to be maximally portable
and choses to use the NetBSD convention. I've added compat code so
that differences between the two drivers can be
LINT is now building again. I went ahead and fixed the vtdriver not
defined problem by removing it from isa_comapt.h.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, Apr 17, 2000 at 11:17:15PM +0200, Poul-Henning Kamp wrote:
Once per day the machine cvsups, checks out a virgin source tree,
tries to build GENERIC, GENERIC98, LINT and world. If any of these
builds fail it will send a report like this.
On Sundays the report will always be sent.
On Mon, Apr 17, 2000 at 05:51:35PM -0400, Patrick Bihan-Faou wrote:
I have a patch against these warnings. They are the result of a function
being called with a pointer to a function rather than a string...
...snip...
Should I just send a PR ?
You should send a PR to the GCC developers, not
This has been fixed in both -STABLE and -CURRENT a week ago. The left
button is working, the timeout is just to long. Read moused manpage
and set the timeout to 200ms as a workaround (this is the default
according to the manpage, but not according to the code in
4.0-RELEASE).
Sam
200 msec
On 17 Apr, Jason wrote:
I didn't know here to send this, but I thought that other people trying
to keep current might have had this problem before:
When I run cvsup with the default cvsup file from
/usr/share/examples/cvsup/cvs-supfile (after putting in the correct cvsup
server address) it
This happened to me when I was using cvsup-bin. I didn't want all of the
modula overhead. Any ideas?
Tom Veldhouse
[EMAIL PROTECTED]
On Mon, 17 Apr 2000, Stephen J. Roznowski wrote:
On 17 Apr, Jason wrote:
I didn't know here to send this, but I thought that other people trying
to keep
"Jordan K. Hubbard" wrote:
But does this also check the kernels ? It was my understanding that
it only did world/release ?
It only does the world/release (and it's the chrooted make release
"world build" which is reported on, not the host system's BTW) but
could easily add a kernel
On Tue, Apr 18, 2000 at 01:45:57PM +1000, Bruce Evans wrote:
Should I just send a PR ?
No, there is already a PR for this (15549).
Doh! The problem is in our code, not the FSF code. Fixed.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
- Forwarded message from "David E. O'Brien" [EMAIL PROTECTED] -
Log:
Change our ELF binary branding to something more acceptable to the Binutils
maintainers.
...
Note that a new kernel can still properly load old binaries except for
Linux static binaries branded in our old
On Fri, Apr 07, 2000 at 11:39:09AM -0400, Donn Miller wrote:
/kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0!
I was discussing this issue with Robert Watson the other day on
IRC. The issue is more complicated than just removing the notification
in sys/netinet/if_ether.c.
It's
David O'Brien wrote:
- Forwarded message from "David E. O'Brien" [EMAIL PROTECTED] -
Log:
Change our ELF binary branding to something more acceptable to the Binutils
maintainers.
...
Note that a new kernel can still properly load old binaries except for
Linux static
On 2000-Apr-18 08:07:45 +1000, "Jordan K. Hubbard" [EMAIL PROTECTED] wrote:
As for the lists being tedious and long: I've sorted the content by
relevance, and it was my hope that over time they would shrink to
zero if we annoyed people enough with them.
I think that's too much annoyance,
On Tue, Apr 18, 2000 at 03:25:35PM +1000, Peter Jeremy wrote:
On 2000-Apr-18 08:07:45 +1000, "Jordan K. Hubbard" [EMAIL PROTECTED] wrote:
As for the lists being tedious and long: I've sorted the content by
relevance, and it was my hope that over time they would shrink to
zero if we annoyed
38 matches
Mail list logo
