On Mon, Apr 17, 2000 at 10:03:25PM -0700, Steve Kargl wrote:
> > brandelf -t Linux /compat/linux/sbin/ldconfig
> Does this mean that we can re-brand any statically
> linux binary if it fails?
Yes. Just like the above.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail t
On Tue, 18 Apr 2000, 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 people
On Tue, 18 Apr 2000, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Peter Jeremy write
> s:
>
> >IMHO, it's not such a bad idea. freebsd-current _is_ the place to
> >report problems with -current, why can't the report be produced by a
> >daemon? All the MUA's I've ever used allowed
In message <[EMAIL PROTECTED]>, Nar
vi writes:
>The summary of summaries would roughly look like this:
>
> Subject: -current build report
>
> Success: world, generic
> Fail: lint
The First part of the email is a summary just like that.
--
Poul-Henning Kamp | UNIX since
On Tue, 18 Apr 2000, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Nar
> vi writes:
>
> >The summary of summaries would roughly look like this:
> >
> > Subject: -current build report
> >
> > Success: world, generic
> > Fail: lint
>
> The First part of the email is a
In message <[EMAIL PROTECTED]>, Nar
vi writes:
>> >The summary of summaries would roughly look like this:
>> >
>> >Subject: -current build report
>> >
>> >Success: world, generic
>> >Fail: lint
>>
>> The First part of the email is a summary just like that.
>>
>
>See what Boris Pop
subscribe freebsd-current
subscribe cvs-all
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Some time ago -core requested that linprocfs should move into the linuxulator.
Nothing has happend on that account, so -core is now forced to take action.
This is the announcement that linprocfs will be removed from the -current
tree in 72 hours, giving the involved parties a final deadline fo
I presume this means that it should remain part of the standard system
but that the source should be moved to /sys/i386/linux?
as long as it remains part of the system I don't care where it lives..
It's too massively important to totally drop. Having it as a port was
a losing proposition.
Julia
Julian Elischer wrote:
> I presume this means that it should remain part of the standard system
> but that the source should be moved to /sys/i386/linux?
>
> as long as it remains part of the system I don't care where it lives..
> It's too massively important to totally drop. Having it as a port
In message <[EMAIL PROTECTED]>, Peter Wemm writes
:
>Julian Elischer wrote:
>> I presume this means that it should remain part of the standard system
>> but that the source should be moved to /sys/i386/linux?
>>
>> as long as it remains part of the system I don't care where it lives..
>> It's too
Now I got lost of
/usr/include/sys/event.h:159: warning: `struct timespec' declared inside
parameter list.
because include it.
Please fix somehow.
--
Andrey A. Chernov
<[EMAIL PROTECTED]>
http://nagual.pp.ru/~ache/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
In article [EMAIL PROTECTED]> you write:
>Now I got lost of
>
>/usr/include/sys/event.h:159: warning: `struct timespec' declared inside
>parameter list.
>
>because include it.
>Please fix somehow.
I'm looking at this now.
--
Jonathan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
Peter Wemm wrote:
>
>
> The biggest problem is that it re-opens a security hole that
> was explicitly patched in procfs.
then look at the hole, don't remove it.
That's throwing the baby out with the bathwater..
It's a godsend when trying to run Linux binaries.
>
> Also, the way I see it, the
here too
Donn Miller wrote:
> ===> librsausa
> mkdir: openssl: File exists
> cp /usr/src/secure/lib/librsausa/../libcrypto/opensslconf-i386.h
> openssl/openssl
> conf.h
> *** Error code 1
> 1 error
> *** Error code 2
> 1 error
> *** Error code 2
> 1 error
> *** Error code 2
> 1 error
> *** Error
Poul-Henning Kamp wrote:
>
> Fully agreement here, and that was also what the core decision said:
> only visible to processed run under the linuxolator.
This sounds like a very poor decision to me..
It doesn't help the security issue at all and it
makes it more difficult to find out what is goi
On Tue, Apr 18, 2000 at 08:38:47AM +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Jordan K. Hubbard" writes:
> >> IMHO, it's not such a bad idea. freebsd-current _is_ the place to
> >> report problems with -current, why can't the report be produced by a
> >> daemon?
> >
> >Bec
> Poul-Henning Kamp wrote:
>
> >
> > Fully agreement here, and that was also what the core decision said:
> > only visible to processed run under the linuxolator.
>
> This sounds like a very poor decision to me..
> It doesn't help the security issue at all and it
> makes it more difficult to fi
:In article [EMAIL PROTECTED]> you write:
:>Now I got lost of
:>
:>/usr/include/sys/event.h:159: warning: `struct timespec' declared inside
:>parameter list.
:>
:>because include it.
:>Please fix somehow.
:
:I'm looking at this now.
:--
:Jonathan
this just means you have:
int fuba
I'd like to recommend the following patches. Adding the option
"CLK_USE_TSC_ANYWAY" allows my laptop to use the TSC even though it
is "flakey". This option should not be set by default.
/usr/src/sys/i386/isa:
*** clock.c.ORIGTue Apr 18 09:45:52 2000
--- clock.c Tue Apr 18 10:21:49 2
Has Brian or Michael or anyone been able to verify whether my patch
below fixes the reported vm_object_shadow panics yet? I'd like to get
it committed (or scrapped).
-Matt
Index: vm_map.c
=
Any ideas as to the cause of the following errors in current. I have
(2)isa non-pnp cards.. SB16(pcm) and a ne2000(ed0). The only other card
is an AGP TNT2 video card.
Apr 17 23:07:42 telecast /kernel: unknown0: at port
0x20-0x21,0xa0-0xa1 irq 2 on isa0
Apr 17 23:07:42 telecast /kernel: unknown
< said:
> Any ideas as to the cause of the following errors in current.
Harmless.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi,
> I'd like to recommend the following patches. Adding the option
> "CLK_USE_TSC_ANYWAY" allows my laptop to use the TSC even though it
> is "flakey". This option should not be set by default.
I saw the same kind of patches and my laptop has this w/o any problems
for long time.
I'd like to
On Tue, Apr 18, 2000 at 10:17:36AM -0700, Matthew Dillon wrote:
>
> :In article [EMAIL PROTECTED]> you write:
> :>Now I got lost of
> :>
> :>/usr/include/sys/event.h:159: warning: `struct timespec' declared inside
> :>parameter list.
> :>
> :>because include it.
> :>Please fix somehow.
> :
> :I
In message <[EMAIL PROTECTED]>, Mitsuru IWASAKI writes
:
>Hi,
>
>> I'd like to recommend the following patches. Adding the option
>> "CLK_USE_TSC_ANYWAY" allows my laptop to use the TSC even though it
>> is "flakey". This option should not be set by default.
>
>I saw the same kind of patches and
Out of the ether, Poul-Henning Kamp spewed forth the following bitstream:
> >> I'd like to recommend the following patches. Adding the option
> >> "CLK_USE_TSC_ANYWAY" allows my laptop to use the TSC even though it
> >> is "flakey". This option should not be set by default.
> >
> >I saw the sam
In message <[EMAIL PROTECTED]>, Alan Clegg writes:
>Out of the ether, Poul-Henning Kamp spewed forth the following bitstream:
>
>> >> I'd like to recommend the following patches. Adding the option
>> >> "CLK_USE_TSC_ANYWAY" allows my laptop to use the TSC even though it
>> >> is "flakey". This o
After building a new kernel yesterday after a cvsup the following
appeared.
Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
2000-06-01 to get rid of block devices
I did a MAKEDEV all and the message still persists.
Regards,
--
Ted Sikora
Jtl Development Group
[EMAIL PROTECTED
Did you install an updated MAKEDEV script?
I *think* the point is that you need to bet rid of block devices, and to
do so, you need a MAKEDEV script that doesn't make them...
Just a guess
On Tue, 18 Apr 2000, Ted Sikora wrote:
> After building a new kernel yesterday after a cvsup the fol
On Tue, 18 Apr 2000, Ted Sikora wrote:
> After building a new kernel yesterday after a cvsup the following
> appeared.
>
> Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
> 2000-06-01 to get rid of block devices
> I did a MAKEDEV all and the message still persists.
>
ls -l /
Garrett Wollman wrote:
>
> < said:
>
> > Any ideas as to the cause of the following errors in current.
>
> Harmless.
Not totally harmless. PNPBIOS is causing a conflict, which is causing a
kernel panic on my system. Since I haven't had a chance to track it
down, I can't be more specific.
Mo
"Chris D. Faulhaber" wrote:
>
> On Tue, 18 Apr 2000, Ted Sikora wrote:
>
> > After building a new kernel yesterday after a cvsup the following
> > appeared.
> >
> > Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
> > 2000-06-01 to get rid of block devices
> > I did a MAKEDEV a
In message <[EMAIL PROTECTED]> Ted Sikora writes:
: Any ideas as to the cause of the following errors in current. I have
: (2)isa non-pnp cards.. SB16(pcm) and a ne2000(ed0). The only other card
: is an AGP TNT2 video card.
I don't see any error messages here :-). The problem is that PNPBIOS
was
Is anyone working on BlueTooth support for freeBSD?
david
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: If it is because the bios fiddles the frequency all the time we
: should maybe understand the APM bios better.
There were issues with some APM BIOSes not resetting this on resume,
but I think that we properly store/restore the state now.
In message <[EMAIL PROTECTED]> Ted Sikora writes:
: Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
: 2000-06-01 to get rid of block devices
: I did a MAKEDEV all and the message still persists.
I get this message when the output of ls -l | egrep ^b is empty.
Warner
To Unsub
In message <[EMAIL PROTECTED]> Bob Martin writes:
: Not totally harmless. PNPBIOS is causing a conflict, which is causing a
: kernel panic on my system. Since I haven't had a chance to track it
: down, I can't be more specific.
PNPBIOS isn't causing the conflict. It is merely allowing us to
det
subscribe
__
Get Your Private, Free Email at http://www.hotmail.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, Apr 18, 2000 at 09:48:11AM +0200, Poul-Henning Kamp wrote:
> Listen, we are talking about an email which is shorter than the
> list of open PRs, and if people actually *DO* something about it
> it will get shorter fast
>
> The only reason it is a long report right now is that people are
On Tue, Apr 18, 2000 at 01:34:11PM -0600, Warner Losh wrote:
>
> I get this message when the output of ls -l | egrep ^b is empty.
\begin{AOL mode}
M To
\end{AOL mode}
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
In message <[EMAIL PROTECTED]>, "David O'Brien" writes:
>On Tue, Apr 18, 2000 at 01:34:11PM -0600, Warner Losh wrote:
>>
>> I get this message when the output of ls -l | egrep ^b is empty.
>
>\begin{AOL mode}
>M To
>\end{AOL mode}
Hmm, that sounds weird...
At what ti
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: At what time does the message come relative to the mounting of the
: root filesystem ? Before or after ?
I get mine when nfs starts up.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the bo
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>: At what time does the message come relative to the mounting of the
>: root filesystem ? Before or after ?
>
>I get mine when nfs starts up.
Any chance you have a bdev on one of the nf
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: In message <[EMAIL PROTECTED]>, Warner Losh writes:
: >In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: >: At what time does the message come relative to the mounting of the
: >: root filesystem ? Before or after ?
: >
: >I get
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>: In message <[EMAIL PROTECTED]>, Warner Losh writes:
>: >In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>: >: At what time does the message come relative to the mounting of the
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: >Almost none. I don't actually mount nfs partitions until I type mount
: >foo:/bar /bar. There's no network card active at that time anyway...
:
: But does the nfs filesystems you mount have any bdevs on them ?
I've not mounted any fil
[John cc'd]
Can (both of) you try the source distribution ?
I was having a problem on cvsup2.uk.FreeBSD.org where clients kept
getting disconnected. The problem went away (it seems) after I
installed the source port (install ports/net/cvsup before
cvsup-mirror).
I'm an advocate of the ``sou
Brian Somers wrote:
>
> [John cc'd]
>
> Can (both of) you try the source distribution ?
> > This happened to me when I was using cvsup-bin. I didn't want all of the
> > modula overhead. Any ideas?
>
> It's not modula any more !!!
Was it re-written in C or C++? Or, how about this -- a versi
On Wed, 19 Apr 2000, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Warner Losh writes:
> >In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
> >: In message <[EMAIL PROTECTED]>, Warner Losh writes:
> >: >In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
> >: >: At what t
On Tue, Apr 18, 2000 at 11:30:40AM -0800, Southwell wrote:
> Is anyone working on BlueTooth support for freeBSD?
I doubt it. We typicaly wait for someone to actually ship something
before going through the pain of trying to implement support for it.
Bluetooth has been demoed extensivly, but I do
On Tue, 18 Apr 2000, Matthew Dillon wrote:
...
> Has Brian or Michael or anyone been able to verify whether my patch
> below fixes the reported vm_object_shadow panics yet? I'd like to get
> it committed (or scrapped).
Seems to fix the panic im my case.
Thanks for the patch.
Bye!
--
This patch introduces a new bug. While it does guarantee that
the assertion in vm_object_shadow isn't tripped over, it doesn't
clear the OBJ_ONEMAPPING flag on the newly created shadow object.
(New objects are created with OBJ_ONEMAPPING set.) Consequently,
we'll have two overlapping mappings to
:
:This patch introduces a new bug. While it does guarantee that
:the assertion in vm_object_shadow isn't tripped over, it doesn't
:clear the OBJ_ONEMAPPING flag on the newly created shadow object.
:(New objects are created with OBJ_ONEMAPPING set.) Consequently,
:we'll have two overlapping map
It would be good to be ahead of the game rather than behind it on this
occasion --
I am still trying to find out about getting IEEE 1394 support -- cards have
been available to me for at least 3 years!!
My two peenorth anyway
David
- Original Message -
From: "Brooks Davis" <[EMAIL PROTE
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Bob Martin writes:
> : Not totally harmless. PNPBIOS is causing a conflict, which is causing a
> : kernel panic on my system. Since I haven't had a chance to track it
> : down, I can't be more specific.
>
> PNPBIOS isn't causing the conflict.
On Tue, Apr 18, 2000 at 05:01:28PM -0800, Southwell wrote:
> It would be good to be ahead of the game rather than behind it on this
> occasion --
Well, get started then. ;-) Most people currently writing code have
better things to do then write drivers for vaporware. The problem is
that, people
On Tue, 18 Apr 2000, Alan Cox wrote:
> This patch introduces a new bug. While it does guarantee that
> the assertion in vm_object_shadow isn't tripped over, it doesn't
> clear the OBJ_ONEMAPPING flag on the newly created shadow object.
> (New objects are created with OBJ_ONEMAPPING set.) Conseq
I'll remove (or change) the assertion later this evening
unless I hear protests to the contrary.
Alan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, 18 Apr 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Ted Sikora writes:
> : Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
> : 2000-06-01 to get rid of block devices
> : I did a MAKEDEV all and the message still persists.
>
> I get this message when the ou
Brian Somers wrote:
> [John cc'd]
>
> Can (both of) you try the source distribution ?
>
> I was having a problem on cvsup2.uk.FreeBSD.org where clients kept
> getting disconnected. The problem went away (it seems) after I
> installed the source port (install ports/net/cvsup before
> cvsup-mi
John Polstra wrote:
>
> Brian Somers wrote:
> > It's not modula any more !!!
>
> Eh? Sure it is. It would be too much work to rewrite it in a
> different language.
I was curious as to why you chose modula. Were you used to using the
language, or did it seem like the best choice for cvsup?
In article <[EMAIL PROTECTED]>,
Jason <[EMAIL PROTECTED]> 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 pu
Cameron Grant wrote:
>
> cg 2000/04/18 12:11:39 PDT
>
> Modified files:
> sys/dev/sound/pciemu10k1.c
> Log:
> try the fix from creative bugzilla for nmi problem
>
> Obtained from:creative labs bugzilla
This is definitely an improvement, it doesn't spont
> Brian Somers wrote:
> >
> > [John cc'd]
> >
> > Can (both of) you try the source distribution ?
>
> > > This happened to me when I was using cvsup-bin. I didn't want all of the
> > > modula overhead. Any ideas?
> >
> > It's not modula any more !!!
>
> Was it re-written in C or C++? Or, h
> >> This happened to me when I was using cvsup-bin. I didn't want all of the
> >> modula overhead. Any ideas?
> >
> > It's not modula any more !!!
>
> Eh? Sure it is. It would be too much work to rewrite it in a
> different language.
Oops, I meant it's not the same version of modula :-/
>
66 matches
Mail list logo
