> I say with 99% certainty that assigning 0.0.0.0 to
> the interface is a requirement of dhcp.
>
> You can't stop using it and expect dhcp to work.
The Linux folks stopped doing it:
2.0 supported the net interface 0.0.0.0 IP address convention (meaning
the kernel should accept all IP pack
>What does it say before this info?
In dmesg.boot (after `boot -v' at the loader prompt):
uhci0: port 0xe000-0xe01f irq 15 at device
7.2 on pci0
uhci0: LegSup = 0x0010
uhci_run: setting run=0
uhci_run: done cmd=0x80 sts=0x20
uhci_run: setting run=1
uhci_run: done cmd=0x81 sts=0x0
usb0: on
Oops, I seem to have made a mistake in the XDR patch that I included
with lockd-0.2. I have re-rolled the patch with a corrected patch.
As such, and to avoid confusion, I have re-labeled this as lockd-0.2a.
Once again, the URL is:
http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2a.tar.gz
Have fun.
Thomas D. Dean wrote:
>
> I had this problem a week ago.
>
> It was caused by my booting the kernel directly.
>
> 0:da(0,a)/kernel
>
> Using
>
> 0:da(0,a)/boot/loader
>
> cures the symptoms.
There's a PR on it, including a patch. See
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=17422
Th
On Fri, 7 Apr 2000, Thomas D. Dean wrote:
> I had this problem a week ago.
>
> It was caused by my booting the kernel directly.
>
> 0:da(0,a)/kernel
>
> Using
>
> 0:da(0,a)/boot/loader
>
> cures the symptoms.
Ohhh!!
This explains why i get the same top: nlist failed error in 5.0.
This might be a bit touchy, but I'm rather curious -- how will the
BSDI merger affect your lockd work? It seems like your work on lockd
(esp. client side & statd interoperation issues) could be speeded up
if you had access to the BSDI sources..
Cheers,
Drew
---
>
> On Fri, 7 Apr 2000, David Holloway wrote:
>
> > I say with 99% certainty that assigning 0.0.0.0 to
> > the interface is a requirement of dhcp.
> >
> > You can't stop using it and expect dhcp to work.
>
> Yes, RFC2131 clause 4.1 says:
>
>DHCP messages broadcast by a client prior to tha
On Fri, 7 Apr 2000, David Holloway wrote:
> I say with 99% certainty that assigning 0.0.0.0 to
> the interface is a requirement of dhcp.
>
> You can't stop using it and expect dhcp to work.
Yes, RFC2131 clause 4.1 says:
DHCP messages broadcast by a client prior to that client obtaining
I apologize profusely for the delay of this, but lockd-0.2 is out.
The URL is: http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2.tar.gz
A couple of notes on this release:
1) the statd hooks to lockd are not yet done (or started)
2) you need a patched libc (for XDR64 types). I have included the x
"Rodney W. Grimes" <[EMAIL PROTECTED]> wrote:
>David Holloway <[EMAIL PROTECTED]> wrote:
>>>Mathew Kanner wrote:
>>>I haven't tried this but how about changing the
>>>/sbin/dhclient-script to not use 0.0.0.0 as the address that wakes
>>>up the interface.
>>
>> No...
>
>Yes... that is just the typ
I had this problem a week ago.
It was caused by my booting the kernel directly.
0:da(0,a)/kernel
Using
0:da(0,a)/boot/loader
cures the symptoms.
tomdean
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
You wrote:
> > rey:/usr/home/mirko> top
> > top: nlist failed
> > rey:/usr/home/mirko> vmstat
> > vmstat: undefined symbols:
> > _cp_time _kmemstatistics _bucket _zlist
>
> I heard rumors that this problem occurs when you doesn't use /boot/loader to
> boot your
> kernel. If so, it is bad practi
[EMAIL PROTECTED] wrote:
> Ciao!
>
> I've upgraded my system from 3.4 to 4.0-stable last night, with new /dev
> and new /etc but now I'm getting these errors:
>
> rey:~/Sources/gnustep/core/base> uname -a
> FreeBSD rey.procom2.it 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 7 01:02:03
> CEST 2000
>
In message <[EMAIL PROTECTED]> Julian Elischer writes:
: Is there a howto on how to convert drivers from the old to new
: form?
Not completely. Just look at ep or ed drivers and do it the same way
:-)
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in
In message <[EMAIL PROTECTED]> Anton Berezin writes:
: It is an issue of personal relationships and politics, not the technical
: one. Tom Christiansen uses OpenBSD and advocates Perl to it (and other
: way around).
tchrist lives in Boulder, as does millert (Todd Miller) and the high
tech commin
Ciao!
I've upgraded my system from 3.4 to 4.0-stable last night, with new /dev
and new /etc but now I'm getting these errors:
rey:~/Sources/gnustep/core/base> uname -a
FreeBSD rey.procom2.it 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 7 01:02:03
CEST 2000
[EMAIL PROTECTED]:/mnt/amy/lpub/free
> Is there a howto on how to convert drivers from the old to new
> form?
Hmmm, I would be interested too. I would like to convert the if_ar
and if_sr drivers, but they are not as straight foward as the "normal"
drivers, because a chip can have two channels and a card can have two
chips. Or maybe
> No...
Yes... that is just the type of thing the link local RFC reserved address
space is for.
> In message <[EMAIL PROTECTED]>, Mathew Kanner writes:
> >On Apr 07, Donn Miller wrote:
> >> Since I started using a cable modem and dhclient, my system has been
> >> literally overwhelmed with mess
> > > The message in question can be extremely useful in case there is IP address
> > > clash on the local network. I suggest we just change the code in question to
> > > ignore clashes over 0.0.0.0 address only.
> >
> > No, don't do that, anyone arping 0.0.0.0 on any network around here
> > I su
Mark,
I had some free time today so I started converting perl 5.6.0 to bmake.
So far, I've gotten libperl to build and plan to keep at the rest of it.
Given my schedule, it will probably take me another week to get the build
right and another week or so to test its integration with build/instal
> FreeBSD dhclient-script assigns 0.0.0.0 address to the interface in PREINIT
> in order to bring interface up. Windows seems to do that as well or
> there is no sane explanation for the relatively big number of these nasty
> messages I am getting every time MediaOne network goes down and several
I have the same impression fom reading dhclient sources.
On 07-Apr-00 David Holloway wrote:
> I say with 99% certainty that assigning 0.0.0.0 to
> the interface is a requirement of dhcp.
>
> You can't stop using it and expect dhcp to work.
>
--
E-Mail: Alexander
I say with 99% certainty that assigning 0.0.0.0 to
the interface is a requirement of dhcp.
You can't stop using it and expect dhcp to work.
In message <[EMAIL PROTECTED]>, "Alexander N. Kabaev" writes:
>FreeBSD dhclient-script assigns 0.0.0.0 address to the interface in PREINIT
>in order to brin
No...
In message <[EMAIL PROTECTED]>, Mathew Kanner writes:
>On Apr 07, Donn Miller wrote:
>> Since I started using a cable modem and dhclient, my system has been
>> literally overwhelmed with messages like:
>>
>> /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0!
>>
>
> I ha
I have seen that situation before as well
and there may be more slight tolerance-style improvements
that could be made but I can't think of any at the moment.
In message <[EMAIL PROTECTED]>, Donn Miller writes:
>This is a multi-part message in MIME format.
>--ABD696746D33D54680111FE2
> > The message in question can be extremely useful in case there is IP address
> > clash on the local network. I suggest we just change the code in question to
> > ignore clashes over 0.0.0.0 address only.
>
> No, don't do that, anyone arping 0.0.0.0 on any network around here
> I sure as heck w
FreeBSD dhclient-script assigns 0.0.0.0 address to the interface in PREINIT
in order to bring interface up. Windows seems to do that as well or
there is no sane explanation for the relatively big number of these nasty
messages I am getting every time MediaOne network goes down and several PCs
sha
> The message in question can be extremely useful in case there is IP address
> clash on the local network. I suggest we just change the code in question to
> ignore clashes over 0.0.0.0 address only.
No, don't do that, anyone arping 0.0.0.0 on any network around here
I sure as heck want to know
On Fri, 7 Apr 2000, Julian Elischer wrote:
> Is there a howto on how to convert drivers from the old to new
> form?
>
> for example if_sr.c no longer shows up (or is even probed) in
> 4.0-stable. I've looked here and there but I can't figure out if there
> is some ISA_SHIM option needed (it's
Could we stop this nonsense thread now? No one is against it. The only
reason why it is not in the tree is that no one has the time to actually
implement the change.
If someone wants it in the tree, do the work and submit it to the
current maintainer of Perl in FreeBSD.
Thanks in advance.
Nick
Is there a howto on how to convert drivers from the old to new
form?
for example if_sr.c no longer shows up (or is even probed) in
4.0-stable. I've looked here and there but I can't figure out if there
is some ISA_SHIM option needed (it's not in LINT if so).
There seemes to be lotsa complicated
On Fri, 7 Apr 2000, Maxim Sobolev wrote:
> > After the conversion, "old style" ports will no longer be accepted.
>
> How about those unlucky, which are patiently waiting for their destiny in the
> PR database? I personally have several and would like to know if any activity
> from my side is req
Trivial patch attached :)
On 07-Apr-00 John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Alexander N. Kabaev <[EMAIL PROTECTED]> wrote:
>> The message in question can be extremely useful in case there is IP address
>> clash on the local network. I suggest we just change the code in questio
In article <[EMAIL PROTECTED]>,
Alexander N. Kabaev <[EMAIL PROTECTED]> wrote:
> The message in question can be extremely useful in case there is IP address
> clash on the local network. I suggest we just change the code in question to
> ignore clashes over 0.0.0.0 address only.
I agree.
John
--
On Apr 07, Donn Miller wrote:
> Since I started using a cable modem and dhclient, my system has been
> literally overwhelmed with messages like:
>
> /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0!
>
I haven't tried this but how about changing the
/sbin/dhclient-script to
The message in question can be extremely useful in case there is IP address
clash on the local network. I suggest we just change the code in question to
ignore clashes over 0.0.0.0 address only.
On 07-Apr-00 Donn Miller wrote:
> Since I started using a cable modem and dhclient, my system has bee
Since I started using a cable modem and dhclient, my system has been
literally overwhelmed with messages like:
/kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0!
Man, these messages were pouring out of syslogd like mad, and my
/var/log/messages* files had to be deleted, because they
Thus spake Maxim Sobolev ([EMAIL PROTECTED]):
> How about those unlucky, which are patiently waiting for their destiny in the
> PR database? I personally have several and would like to know if any activity
> from my side is reqired.
Let the committers do that. It's a trivial fix.
If you change s
What does it say before this info? Shared interrupt?
USB does work on SMP (or at least in some cases).
> uhci_timeout: ii=0xc0a601c0
> uhci_timeout: ii=0xc0a601c0
> uhci_timeout: ii=0xc0a601c0
> usbd_new_device: addr=2, getting first desc failed
> uhub_explore: usb_new_device failed, error=TIME
> >- USB Keyboards
> >- Keyboard in DDB debugger does not work.
>
> In what configuration does it not work? I can use my USB keyboard in
> DDB without problems on a dual PPro box (4.0-STABLE) with a UHCI
> controller (VIA 83c572) card and a Pentium box (3.4-STABLE) with Intel
> PIIX3 here..
>To Do list for the USB project:
[...]
>- USB base stack and general items.
I am currently having trouble with Gigabyte GA-6BXD, dual Pentium III
motherboard. If I boot a UP kernel (5.0-CURRENT), the PIIX4 USB
controller works fine.
If I boot a SMP kernel (the only difference from the UP kerne
We want to update our system perl5. It'll take some work. If you want
to do the work, your patches will be greatly appreciated by our perl5
maintainer, Mark Murray <[EMAIL PROTECTED]>.
Since nobody here has offered to do any _work_ on incorporating perl
5.6.0 into FreeBSD 5.0-CURRENT, please w
>To Do list for the USB project:
>
>Let meknow if you would like to participate in any way, or you have
>done one of the items below!
[...]
>- USB Keyboards
>- Keyboard in DDB debugger does not work.
In what configuration does it not work? I can use my USB keyboard in
DDB without problems o
If've put up a list of things that need to be done still in the FreeBSD
USB stack. The list is _big_. I'll be adding things as they come up.
http://www.etla.net/~n_hibma/usb/usb.pl
A lot of the items are not that difficult to do and if you feel like
taking up a little project, start
On Fri, Apr 07, 2000 at 12:57:16AM -0400, Alexander N. Kabaev wrote:
> I am perfectly aware of the way OpenBSD builds contrib software. I am
> just making a point that they have found perl 5.6.0 is stable enough
> to be included into their OS.
It is an issue of personal relationships and politic
At 12:57 AM -0400 2000/4/7, Alexander N. Kabaev wrote:
> I am perfectly aware of the way OpenBSD builds contrib software. I am just
> making a point that they have found perl 5.6.0 is stable enough to be
> included into their OS.
It's my understanding that we already have a better and
Satoshi Asami wrote:
> After the conversion, "old style" ports will no longer be accepted.
How about those unlucky, which are patiently waiting for their destiny in the
PR database? I personally have several and would like to know if any activity
from my side is reqired.
-Maxim
To Unsubscrib
auth 6df833c4 unsubscribe freebsd-current [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
FYI.
-PW
===
From: [EMAIL PROTECTED] (Satoshi Asami)
Subject: HEADS UP: ports Makefiles being updated soon
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Date: Fri, 7 Apr 2000 01:15:16 -0700 (PDT)
Message-Id: <[EMAIL PROTECTED]>
Hello world,
As we have been discussing on the ports list, we have de
On Fri, Apr 07, 2000 at 03:56:52PM +0800, Stephen Hocking-Senior Programmer PGS SPS
Perth wrote:
> now a version of gas that supports 3dnow! instructions without bugs. It's one
The base Binutils (which includes gas) is being upgraded. There are
several groups that need to be addressed in the u
I've been following the GLX stuff for Matrox G400s and noticed that there's
now a version of gas that supports 3dnow! instructions without bugs. It's one
of the snapshots by H.J. Lu - 2.9.5.0.34, found at
ftp://ftp.varesearch.com/pub/support/hjl/binutils/
Any chance of this making its way into
On Thu, 6 Apr 2000, Matthew Dillon wrote:
>
> :The version of Linux kernel source that I have uses the first:
> :
> :asmlinkage long sys_getppid(void)
> :{
> : int pid;
> : struct task_struct * me = current;
> : struct task_struct * parent;
> :
> : parent = me->p_opptr;
> : f
52 matches
Mail list logo
