Re: rev 1.61 of /sys/netinet/in.c breaks ISDN
On Fri, Dec 07, 2001 at 09:01:12PM +0100, Joerg Wunsch wrote: > As Ruslan Ermilov wrote: > > > > phk has chosen 0.0.0.1 since it obviously cannot be a meaningful > > > statically configured address. > > > OK, but is it really necessary? It's much simpler to add routes > > over P2P interfaces using the interface name ... > > You need to configure /some/ interface address for the remote end > anyway, and it must not clash with any other routing table entry, > since "ifconfig ... up" always adds an entry for the remote IP address > for p2p interfaces. > Only if you have INET address configured on an interface. > (Actually, it even tries to enter it twice, so > you get a meaningless "Address already exists." message when bringing > a p2p interface up with ifconfig.) > > The politically correct solution to negotiate the remote PPP address > would have been to change the routing table entry after negotiating > the address, of course. However, this seemed to be too much hassle > for the small&simple intent of sppp(4), in particular considering that > the only added value compared to the 0.0.0.1 hack would be that you > can reach the IP address of your peer directly. > Why not just bring the interface up first, then negotiate an address, then add it to interface? [Please DO NOT exclude my personal address when replying -- I didn't ask for it (as many do) through the Mail-Followup-To: header.] Cheers, -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dhclient busted for -current?
On Sat, 8 Dec 2001 02:07:22 -0500, Jeremy Parker <[EMAIL PROTECTED]> wrote: > I have also experienced this issue, caused me a lot of trouble. The only > workaround I have figured out, is to bring up the interface with an IP > address, then start dhclient and it seems to work. > > This is a very recent problem for me as well. > Running -current from Thursday evening on a Latitude CPx with a 3Com 3C575, dhclient to a FreeBSD 4.4-stable server, no issues. Are you asking for specific options (my dhclient.conf is empty)? are you using a reservation? Best Regards, PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stable->current busted
Mathieu Arnold wrote:
>
> Warner Losh wrote:
> >
> > 4.4-r -> current build is very broken right now. I'll investigate and
> > fix.
>
> last time I did it, I had a problem with install, adding LDFLAGS+=
> -static to src/usr.bin/xinstall/Makefile fixed the problem.
> the problem was using install linked to libc.so.4 to do something like
> this :
> rm libc.so.4
> install libc.so.4
> which was failing for obvious reasons :)
I think this will fix it:
http://people.freebsd.org/~peter/compat.diff
I would have liked to change the 'beforeinstall' to 'afterinstall' in
Makefile.inc, but afterinstall seems to not be usable. Another option is
this:
Index: Makefile.inc
===
RCS file: /home/ncvs/src/lib/compat/Makefile.inc,v
retrieving revision 1.8
diff -u -r1.8 Makefile.inc
--- Makefile.inc22 Sep 2001 08:11:24 - 1.8
+++ Makefile.inc8 Dec 2001 21:04:42 -
@@ -3,7 +3,7 @@
LIBCOMPATDIR?= ${LIBDIR}/compat/aout
.if defined(LIBS) && !empty(LIBS)
-beforeinstall: __remove-stale-libs
+maninstall:: __remove-stale-libs
__remove-stale-libs: .PHONY
.for lib in ${LIBS}
.if exists(${DESTDIR}${SHLIBDIR}/${lib})
.. but if there was ever any abuse of bsd.*.mk in our tree, this would be
it. It hooks onto the manpage install hook so that it can remove the
old libraries *after* the compat libraries are installed.
I think the first one is cleaner though. It moves the 4.x libraries to /
usr/lib/compat first, then attempts to install new ones over the top. If
something goes wrong trying to install the new ones, at least the old
libraries will still be in /usr/lib/compat.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: rev 1.61 of /sys/netinet/in.c breaks ISDN
As Ruslan Ermilov wrote: > > You need to configure /some/ interface address for the remote end > > anyway, and it must not clash with any other routing table entry, > > since "ifconfig ... up" always adds an entry for the remote IP address > > for p2p interfaces. > Only if you have INET address configured on an interface. That's the purpose of an sppp interface. You can't do anything with it unless an INET address has been configured to it. (In the case of an automatic dialer -- which is what many ISDN users are using -- you need the IP traffic generated by normal routing in order to trigger the ISDN dialout.) > Why not just bring the interface up first, then negotiate an address, > then add it to interface? Because it'll become a chicken-and-egg problem: the interface would never start negotiating PPP in that case. There are other PPP implementations available for people who want a full-blown one; sppp is meant to be the simplest (and smallest) PPP implementation that is useful for synchronous data carriers. > [Please DO NOT exclude my personal address when replying -- I didn't > ask for it (as many do) through the Mail-Followup-To: header.] You got it. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
wi driver: firmware %i.%i problem?
Here's a data point for you Warner. I have an Intel PRO 2011 802.11b adapter (Symbol Spectrum24 OEM) card. Works just fine under -current and the wi driver. After a yesterday's rebuild I noticed the wi driver displaying this on booting. $ dmesg FreeBSD 5.0-CURRENT #3: Sat Dec 8 19:32:20 GMT 2001 root@ernest:/usr/obj/usr/src/sys/TPAD . wi0 at port 0x280-0x2c7 iomem 0xd4000-0xd43ff irq 9 flags 0x1 slot 0 on pccard0 wi0: 802.11 address: 00:02:b3:04:b8:b8 wi0: using RF:PRISM2 MAC:HFA3841, Firmware: %i.%i variant %i $ I'm not sure if the %i is a problem the kernel printf or with my card. I'm still using the stock pccard.conf file with the 0x1 flag. The card works fine. BTW, it's using version 2.xx firmware from Intel. I am not seeing the dhclient problem reported by others. Thanks, -- Alan Edmonds [EMAIL PROTECTED] London, England To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wi driver: firmware %i.%i problem?
* Alan Edmonds <[EMAIL PROTECTED]> [011208 17:42] wrote: > > Here's a data point for you Warner. I have an Intel PRO 2011 > 802.11b adapter (Symbol Spectrum24 OEM) card. Works just fine > under -current and the wi driver. After a yesterday's rebuild > I noticed the wi driver displaying this on booting. > > $ dmesg > FreeBSD 5.0-CURRENT #3: Sat Dec 8 19:32:20 GMT 2001 > root@ernest:/usr/obj/usr/src/sys/TPAD > . > wi0 at port 0x280-0x2c7 iomem 0xd4000-0xd43ff irq 9 flags 0x1 slot 0 on pccard0 > wi0: 802.11 address: 00:02:b3:04:b8:b8 > wi0: using RF:PRISM2 MAC:HFA3841, Firmware: %i.%i variant %i > $ > > I'm not sure if the %i is a problem the kernel printf or > with my card. I'm still using the stock pccard.conf > file with the 0x1 flag. The card works fine. > BTW, it's using version 2.xx firmware from Intel. > > I am not seeing the dhclient problem reported by others. %i is because I lost a flamewar to get %i added to kernel printf, it has been fixed. About your card, you may have luck checking your vendor's site for a firmware upgrade. Upgrading my cards (Addtron) really worked wonders. -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/kern subr_diskmbr.c
Bernd Walter <[EMAIL PROTECTED]> wrote: > 32 times for each disk on booting with most of 30 disks. > Possibly it's triggered by vinums drive scanning. Yep, same here (and it is triggered by vinum). > What can I do about these messages? Remove it. It should not have been there in the first place, at least not without an "if (bootverbose) ..." in front of it. It isn't telling any news anyway, because you certainly already knew that your disks are using DD mode, and the last word is telling "(ignored)" which is the intented and expected action to happen anyway. I do understand Peters gripe about broken BIOSes that try to interpret fdisk tables (where the fdisk table is actually in the domain of the boot block itself). The comments tell a bit more about it. But adding pointless messages that flush the boot log and possibly hide important boot messages can't be goo. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/kern subr_diskmbr.c
:boot block itself). The comments tell a bit more about it. But :adding pointless messages that flush the boot log and possibly hide :important boot messages can't be goo. : :-- :cheers, J"org .-.-. --... ...-- -.. . DL8DTL Yes, Goo in the computer is wery, wery bad! -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NO AL PARO
;ACUERDO MOYANO-CAVALLO-DAHER CONOCE UD. EL ACUERDO EXISTENTENTE ENTRE MOYANO, DAHER Y CAVALLO? EL MISMO CONSISTE EN EL PARO PROGRAMADO PARA EL JUEVES.- CON ESTE PARO, - QUE NO DEFIENDE PARA NADA LOS INTERESES DE LA CLASE TRABAJADORA CAVALLO SE ASEGURA UN DIA "MUY NECESARIO" DE TRANQUILIDAD BANCARIA Y MOYANO Y DAHER, LLEVANDO LAS MASAS A LA PLAZA INTENTANTAN CONVALIDAR SUS RESPECTIVOS LIDERAZGOS.- EL DERECHO DE HUEGA, COSTO MUCHAS VIDAS Y AÑOS PARA SER CONSTITUCIONALMENTE RECONOCIDO NO SE DEJE ENGAÑAR EL FUTURO DEL PAIS NO PASA POR ADHERIR A UN PARO ENGAÑOSO; SINO PORQUE ENTRE TODOS LOS ARGENTINOS CONSTRUYAMOS UN PROYECTO DEL PAIS QUE QUEREMOS NO PRESTE SU APOYO AL PARO, NO LE HAGA EL JUEGO A LOS ESPECULADORES FINANCIEROS Y A LOS BANCOS ROMPA LA TRAMA SINIESTRA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/kern subr_diskmbr.c
Joerg Wunsch wrote: > Bernd Walter <[EMAIL PROTECTED]> wrote: > > > 32 times for each disk on booting with most of 30 disks. > > Possibly it's triggered by vinums drive scanning. > > Yep, same here (and it is triggered by vinum). > > > What can I do about these messages? > > Remove it. It should not have been there in the first place, at least > not without an "if (bootverbose) ..." in front of it. It isn't > telling any news anyway, because you certainly already knew that your > disks are using DD mode, and the last word is telling "(ignored)" > which is the intented and expected action to happen anyway. There shouldn't *be* bootblocks on non-boot disks. dd if=/dev/zero of=/dev/da$n count=1 Dont use "disklabel -B -rw da$n auto". Use "disklabel -rw da$n auto". Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/kern subr_diskmbr.c
On Sat, Dec 08, 2001 at 05:09:11PM -0800, Peter Wemm wrote: > Joerg Wunsch wrote: > > Bernd Walter <[EMAIL PROTECTED]> wrote: > > > > > 32 times for each disk on booting with most of 30 disks. > > > Possibly it's triggered by vinums drive scanning. > > > > Yep, same here (and it is triggered by vinum). > > > > > What can I do about these messages? > > > > Remove it. It should not have been there in the first place, at least > > not without an "if (bootverbose) ..." in front of it. It isn't > > telling any news anyway, because you certainly already knew that your > > disks are using DD mode, and the last word is telling "(ignored)" > > which is the intented and expected action to happen anyway. > > There shouldn't *be* bootblocks on non-boot disks. I usually have a /boot/loader.work and a /boot/kernel.work for updating. What is wrong about having spare bootblocks? In fact I already needed them twice and the diskspace is unused anyway. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: truss(1) is back in business
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes: > des 2001/12/08 16:35:30 PST > > Modified files: > sys/fs/procfsprocfs.c procfs_ioctl.c > Log: > Fix various bugs in the debugging code and reenable it. > > Revision ChangesPath > 1.3 +0 -2 src/sys/fs/procfs/procfs.c > 1.2 +9 -7 src/sys/fs/procfs/procfs_ioctl.c Thought you'd like to know. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: truss(1) is back in business
On Sun, Dec 09, 2001 at 01:38:03AM +0100, Dag-Erling Smorgrav wrote: > Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes: > > des 2001/12/08 16:35:30 PST > > > > Modified files: > > sys/fs/procfsprocfs.c procfs_ioctl.c > > Log: > > Fix various bugs in the debugging code and reenable it. > > > > Revision ChangesPath > > 1.3 +0 -2 src/sys/fs/procfs/procfs.c > > 1.2 +9 -7 src/sys/fs/procfs/procfs_ioctl.c > > Thought you'd like to know. > Thanks! -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
