Re: make release broken

[Wilko Bulte]

On Fri, Jan 21, 2000 at 09:19:22AM +0200, John Hay wrote:

 Make release on current is broken. It dies with:
 
 --
  Filesystem is 1440 K, -52 left
  4000 bytes/inode, 10 left
 touch release.9
 0 blocks
 Setting up CDROM distribution area
 0 blocks
 0 blocks
 0 blocks
 0 blocks
 ...
 0 blocks
 0 blocks
 0 blocks
 cp: /usr/src/release/texts/HARDWARE.TXT: No such file or directory
 *** Error code 1
 
 Stop in /usr/src/release.
 *** Error code 1
 
 Stop in /usr/src/release.
 *** Error code 1
 
 Stop in /usr/src/release.
 ---
 
 It looks like the handling of HARDWARE.TXT in release/Makefile is broken.

Duh.. John Polstra is working on cvs-moving i386/HARDWARE.TXT to make
this file the starting point for the generic HARDWARE.TXT

There were some problems in doing this with cvs

I guess this needs some time to get resolved.

-- 
Wilko Bulte Arnhem, The Netherlands   - The FreeBSD Project 
WWW : http://www.tcja.nl  http://www.freebsd.org


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

collect2 and cplus-dem.c in binutils

[Max Khon]

hi, there!

will collect2 be built in base system?
btw binutils have in their libiberty cplus-dem.c which is incompatible
with that which is used in gcc 2.9x.x. the result is broken -frepo
in egcs and gcc-devel ports in -current.

I filed one PR about it but I was rather tired yesterday and did not
noticed that C++ demangler in gcc is more recent than that one in
binutils.

Affected tools are addr2line, nm, objdump and (most important) ld.
The problem can be fixed by using demangle.h and cplus-dem.c from
gcc when building libiberty for binutils.

/fjoe



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: cvsup 3.4-release to -current

[Andy Farkas]

On Thu, 20 Jan 2000, f.johan.beisser wrote:

 that's very accurate. you'd be better off getting a SNAP image and
 upgrading your system from that.
 
 that is, if you really need to do it now.
 
 i'd just wait, untill the final release, since it's coming up Real Soon
 Now.
 
 -- jan
 
 On Thu, 20 Jan 2000, Matt M. wrote:
 
  Just wondering what potential problems I am facing by going from
  3.4-release to -current. I was told on irc that my chances may not be
  well.
  
 
  +-//  f. johan beisser  //--+
   email: jan[at]caustic.org   web: http://www.caustic.org/~jan 
"knowledge is power. power corrupts. study hard, be evil."

Um, I thought we were supposed to be testing
4.0-current _before_ it goes -release... I am
going to upgrade my workstation (from 3.4 to
4.0) over this weekend, to help further the
cause...


--
 
 :{ [EMAIL PROTECTED]
  
Andy Farkas
System Administrator
   Speednet Communications
 http://www.speednet.com.au/
  




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

pci_write_config arg order

[Kenjiro Cho]

pci_write_config() and pci_cfgwrite() defined in sys/pci/pcivar.h 
have an unusual argument order:

pci_read_config(dev, reg, width)
pci_write_config(dev, reg, val, width)

pci_cfgread(cfg, offset, size)
pci_cfgwrite(cfg, offset, val, size)

Apparently, pcisupport.c and isp_pci.c misplace the 3rd and 4th args.

Could someone take a look?

Reported by Yoichi Shinoda [EMAIL PROTECTED]

-Kenjiro


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

rtld-elf, java + tya

[Max Khon]

hi, there!

applet_viewer bombs out with a lot of stuff in the output like this
(until killed -9):

ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
lark:~/bin$

latest jdk-1.1.8 port, tya 1.4, -current built from sources from 19 Jan

/fjoe



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

make release failure (HARDWARE.TXT)

[John W. DeBoskey]

Hi,

   I've seen the following error for the last 2 days since the
make release change to HARDWARE.TXT.

   CVS shows this file as removed from the head of the tree at
revision 1.30 but the Makefile is unconditionally attempting
to copy them in the ftp.1  cdrom.1 targets, followed by optionally
concatinating the ${MACHINE_ARCH} specific file.

   It appears that DIST_DOCS needs to be broken up into common
doc or the for loops over DIST_DOCS needs to become smarter.

   I have supplied a patch which I beleive fixes the problem
by allowing files misssing to be ignored. This of course means
accidental errors in DOC file removal or location movement become
harder to detect until someone actually checks the doc and sees that
portions are missing.

   The patch and actual error condition follow.

Thanks!
John

FreeBSD(root)/snap/release/usr/src/release %cvs diff -u Makefile
Index: Makefile
===
RCS file: /mirror/ncvs/src/release/Makefile,v
retrieving revision 1.527
diff -u -r1.527 Makefile
--- Makefile2000/01/19 22:48:50 1.527
+++ Makefile2000/01/21 13:25:01
@@ -527,7 +527,11 @@
@cd ${RD}  find floppies -print | cpio -dumpl ${FD}
@cd ${RD}/dists  find . -print | cpio -dumpl ${FD}
@for i in ${DIST_DOCS}; do \
- cp ${.CURDIR}/texts/$${i} ${FD}; \
+ if [ -f ${.CURDIR}/texts/$${i} ]; then \
+cp ${.CURDIR}/texts/$${i} ${FD}; \
+  else \
+echo "=== No common ${i} documentation"  ${FD}/$${i}; \
+  fi; \
  if [ -f ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ]; then \
 echo "=== Platform specifics for ${MACHINE_ARCH}"  ${FD}/$${i}; \
 cat ${.CURDIR}/texts/${MACHINE_ARCH}/$${i}  ${FD}/$${i}; \
@@ -560,7 +564,11 @@
@echo "CD_VERSION = ${BUILDNAME}"  ${CD_DISC1}/cdrom.inf
@echo "CD_VERSION = ${BUILDNAME}"  ${CD_DISC2}/cdrom.inf
@for i in ${DIST_DOCS}; do \
- cp ${.CURDIR}/texts/$${i} ${CD_DISC1}; \
+ if [ -f ${.CURDIR}/texts/$${i} ]; then \
+cp ${.CURDIR}/texts/$${i} ${CD_DISC1}; \
+  else \
+echo "=== No common ${i} documentation"  ${FD}/$${i}; \
+  fi; \
  if [ -f ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ]; then \
 echo "=== Platform specifics for ${MACHINE_ARCH}"  ${FD}/$${i}; \
 cat ${.CURDIR}/texts/${MACHINE_ARCH}/$${i}  ${CD_DISC1}/$${i}; \




touch release.9
0 blocks
Setting up CDROM distribution area
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
cp: /usr/src/release/texts/HARDWARE.TXT: No such file or directory
*** Error code 1

Stop in /usr/src/release.
*** Error code 1




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: error wich devices ad*

[joanra]

# mount -u -o rw /
mount: block device required

what is the problem? :(

thanks

-Mensaje original-
De: Nick Hibma [EMAIL PROTECTED]
Para: joanra [EMAIL PROTECTED]
CC: [EMAIL PROTECTED] [EMAIL PROTECTED]
Fecha: viernes, 21 de enero de 2000 10:53
Asunto: RE: error wich devices ad*


On Fri, 21 Jan 2000, joanra wrote:

 I have done all what you have told me to do, but it still doesn't work.
Now
 i have another problem, i have removed the DEVICES WD* (as you told me)
and
 i can't mount partitions. It mounts WD on / but just as READ-ONLY and i
 can't do anything, How could i mount it whith writing permisions to
continue
 trying things??

When in single user mode:

 mount -u -o rw /

and then

 mount -a -t ufs

When you then type

 mount

you should see
 /
 /var
 /usr
mounted. When you then exit from single user mode it should boot.

 PS: the error message at init is the same that appeared me the first time
 when i make: mount /dev/as2s1f /usr (for example), the error is:
 mount: device block required

You are sure you have an up to date kernel? This sounds very much like
you have an up to date userland but an old kernel. Block devices have
been removed from the kernel some weeks ago.

Nick


 please help
 -Mensaje original-
 De: Nick Hibma [EMAIL PROTECTED]
 Para: joanra [EMAIL PROTECTED]
 Fecha: jueves, 20 de enero de 2000 23:32
 Asunto: Re: error wich devices ad*


 
 Boot with kernel.old and remake all your devices:
 
  cp /usr/src/etc/MAKEDEV /dev/MAKEDEV
  cd /dev
  sh MAKEDEV all
 
 and make sure you update /etc/fstab as well. wd - ad, wcd - acd. Then
 do a to clean up your device tree:
 
  cd /dev
  rm -f wcd* wd* rwcd* rwd*
 
 Nick
 
 On Thu, 20 Jan 2000, joanra wrote:
 
  Hi when i run freebsd, display:
 
  Mounting root from ufs: /dev/ad2s1a
  no such device ad
  setrootbyname failed
  ffs_mountroot: can't find rootvp
  root mount failed: 6
  mounting root from ufs: wd2s1a
  swapon: /dev/ad2s1b: device not configure
  Automatic reboot in ptogress
  can't open /dev/ad2s1a: device not configured
 
  my fstab:
 
  # DeviceMountpoint
  /dev/ad2s1b none
  /dev/ad2s1a /
  /dev/ad2s1f /usr
  /dev/ad2s1e /var
  /dev/cd0c   /cdrom  cd9660
  proc/proc
 
  anyone help me please?
 
  P.S: i recompiled a new kernel, and i create the new devices ad*, and
my
 hd
  is seconday
 
  thanks
 
 
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with "unsubscribe freebsd-current" in the body of the message
 
 
 --
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]  USB project
 http://www.etla.net/~n_hibma/
 
 



--
[EMAIL PROTECTED]
[EMAIL PROTECTED]  USB project
http://www.etla.net/~n_hibma/





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: rtld-elf, java + tya

[Pascal Hofstee]

On Fri, Jan 21, 2000 at 06:42:51PM +0600, Max Khon wrote:
 hi, there!
 
 applet_viewer bombs out with a lot of stuff in the output like this
 (until killed -9):
 
 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55

I just today experienced the Exact same assertion failure when trying to
shutdown the GIMP.


-- 

  Pascal Hofstee - [EMAIL PROTECTED]

-BEGIN GEEK CODE BLOCK-
Version: 3.1
GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP--
t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+
--END GEEK CODE BLOCK--


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th)

[Will Andrews]

On Tue, Jan 18, 2000 at 02:48:25AM -0800, Frank Mayhar wrote:
 Interestingly, I rebuilt world with the latest pccardd changes and,
 suddenly, the 589D started working perfectly.  Unfortunately, the
 574BT doesn't work at all now.  It appears to configure properly, but
 it doesn't transmit or receive.

My 574BT works if you hardcode the pccardd IRQ to 9. I did this by
editing rc.pccard and replaced the pccard line with:

pccardd -i 9 -f ${pccard_conf}

It works fine for me. I think there's something wrong with pccardd, and
that's why it keeps using IRQs I don't even have specified in
pccard.conf. I should do more research on this, though.

--Will


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: cvsup 3.4-release to -current

[Will Andrews]

On Thu, Jan 20, 2000 at 09:21:13PM -0800, Matt M. wrote:
 Just wondering what potential problems I am facing by going from
 3.4-release to -current. I was told on irc that my chances may not be
 well.

You should read /usr/src/UPDATING (for -CURRENT). I won't say you shouldn't
use it since 4.0-RELEASE is probably going out within a month, and bugs
need to be worked out.

However, I wouldn't upgrade if I was using that particular machine for
production purposes. My -CURRENT box can crash to hell for all I care. My
-STABLE will stay -STABLE since it needs to be depended on.

-- 
Will Andrews [EMAIL PROTECTED]
GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ 
G+ e- h! r--+++ y?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: error wich devices ad*

[Nick Hibma]

Your userland is out of sync with your kernel. I suggest you tell us
what steps you took to get here. I'm referring to steps like:

- make world
- compile your kernel
- update /etc/fstab and the likes
- update /dev/MAKEDEV

and other things you could come up with that might be related to
modifying your system files.

See if you can get someone to send you a kernel. Boot from the first CD,
go to Fix-it/CDROM and then copy that kernel for example from a floppy
onto the mounted root partition as kernel.CURRENT and reboot again,
booting the new kernel.CURRENT.


Big question: Why do you run current if you don't read the mail
[EMAIL PROTECTED]?

Nick

On Fri, 21 Jan 2000, joanra wrote:

 # mount -u -o rw /
 mount: block device required
 
 what is the problem? :(
 
 thanks
 
 -Mensaje original-
 De: Nick Hibma [EMAIL PROTECTED]
 Para: joanra [EMAIL PROTECTED]
 CC: [EMAIL PROTECTED] [EMAIL PROTECTED]
 Fecha: viernes, 21 de enero de 2000 10:53
 Asunto: RE: error wich devices ad*
 
 
 On Fri, 21 Jan 2000, joanra wrote:
 
  I have done all what you have told me to do, but it still doesn't work.
 Now
  i have another problem, i have removed the DEVICES WD* (as you told me)
 and
  i can't mount partitions. It mounts WD on / but just as READ-ONLY and i
  can't do anything, How could i mount it whith writing permisions to
 continue
  trying things??
 
 When in single user mode:
 
  mount -u -o rw /
 
 and then
 
  mount -a -t ufs
 
 When you then type
 
  mount
 
 you should see
  /
  /var
  /usr
 mounted. When you then exit from single user mode it should boot.
 
  PS: the error message at init is the same that appeared me the first time
  when i make: mount /dev/as2s1f /usr (for example), the error is:
  mount: device block required
 
 You are sure you have an up to date kernel? This sounds very much like
 you have an up to date userland but an old kernel. Block devices have
 been removed from the kernel some weeks ago.
 
 Nick
 
 
  please help
  -Mensaje original-
  De: Nick Hibma [EMAIL PROTECTED]
  Para: joanra [EMAIL PROTECTED]
  Fecha: jueves, 20 de enero de 2000 23:32
  Asunto: Re: error wich devices ad*
 
 
  
  Boot with kernel.old and remake all your devices:
  
   cp /usr/src/etc/MAKEDEV /dev/MAKEDEV
   cd /dev
   sh MAKEDEV all
  
  and make sure you update /etc/fstab as well. wd - ad, wcd - acd. Then
  do a to clean up your device tree:
  
   cd /dev
   rm -f wcd* wd* rwcd* rwd*
  
  Nick
  
  On Thu, 20 Jan 2000, joanra wrote:
  
   Hi when i run freebsd, display:
  
   Mounting root from ufs: /dev/ad2s1a
   no such device ad
   setrootbyname failed
   ffs_mountroot: can't find rootvp
   root mount failed: 6
   mounting root from ufs: wd2s1a
   swapon: /dev/ad2s1b: device not configure
   Automatic reboot in ptogress
   can't open /dev/ad2s1a: device not configured
  
   my fstab:
  
   # DeviceMountpoint
   /dev/ad2s1b none
   /dev/ad2s1a /
   /dev/ad2s1f /usr
   /dev/ad2s1e /var
   /dev/cd0c   /cdrom  cd9660
   proc/proc
  
   anyone help me please?
  
   P.S: i recompiled a new kernel, and i create the new devices ad*, and
 my
  hd
   is seconday
  
   thanks
  
  
  
   To Unsubscribe: send mail to [EMAIL PROTECTED]
   with "unsubscribe freebsd-current" in the body of the message
  
  
  --
  [EMAIL PROTECTED]
  [EMAIL PROTECTED]  USB project
  http://www.etla.net/~n_hibma/
  
  
 
 
 
 --
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]  USB project
 http://www.etla.net/~n_hibma/
 
 
 
 

--
[EMAIL PROTECTED]
[EMAIL PROTECTED]  USB project
http://www.etla.net/~n_hibma/




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: passwords got smashed by make installworld

[Kris Kennaway]

On Fri, 21 Jan 2000, Brian Hechinger wrote:

 rebooted, tried to log in and couldn't.  not as root, not as my regular user.

Sounds like you clobbered your DES libcrypt libraries with non-DES ones,
and now you can't use your DES passwords.

Kris


"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

passwords got smashed by make installworld

[Brian Hechinger]

i'm just reporting this, i have no real info, other than it happened.

i installed the 2114 snapshot.  SUPed -current, uhm, two days ago i
think.  did a make buildworld at that time.  then yesterday evening i had
a chance to reboot my machine so i did make installworld (as well as a new
kernel with some options i wanted that i forgot to put in)

rebooted, tried to log in and couldn't.  not as root, not as my regular user.

wanted to track it down but didn't have the time to, just needed my box to
work.  all i had to do was boot into single user mode and use passwd to set
the passwords again.  

somebody should look at wednesdays' snapshot (unless this is known and fixed)
and see why a make installworld would bash passwords.

or maybe look at the 14th's snapshot, ah, whatever, in a rush, gotta go.

keep up the good work.  -current rocks.

-wonko 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

problems with mylex raid scsi

[Steven Jurczyk]

This message was sent from Geocrawler.com by "Steven Jurczyk" [EMAIL PROTECTED]
Be sure to reply to that address.

I try to install FreeBSD 4.0-CURRENT snapshot on 
server with have mylex accele raid 250 controler. 
FreeBSD installs on it without any problems, but 
can't boot from it. I try 2 and 8 GB BIOS mode, 
also FreeBSD and BIOS geometry (trick with small 
dos partition). Depending of situation boot 
loader shows Invalid slice, registers (int 0d, 
err 00, eip a658, cs f000) and System halted info 
or boot manager can't find loader (it bells when 
I select F1 - FreeBSD).

steve

Geocrawler.com - The Knowledge Archive


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: rtld-elf, java + tya

[John Polstra]

In article [EMAIL PROTECTED],
Max Khon  [EMAIL PROTECTED] wrote:
 hi, there!
 
 applet_viewer bombs out with a lot of stuff in the output like this
 (until killed -9):
 
 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55

Really?!  Augh.  Naturally this comes just hours after I have merged
the latest changes into -stable *sigh*.

Could you please make sure your src/libexec/rtld-elf is
up-to-date?  rtld.c should be at revision 1.41.

Then if you can give me a stack backtrace it would help a lot.

Thanks,
John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra  Co., Inc.Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th)

[Frank Mayhar]

Warner Losh wrote:
 In message [EMAIL PROTECTED] Will Andrews writes:
 : On Tue, Jan 18, 2000 at 02:48:25AM -0800, Frank Mayhar wrote:
 :  Interestingly, I rebuilt world with the latest pccardd changes and,
 :  suddenly, the 589D started working perfectly.  Unfortunately, the
 :  574BT doesn't work at all now.  It appears to configure properly, but
 :  it doesn't transmit or receive.
 : My 574BT works if you hardcode the pccardd IRQ to 9. I did this by
 : editing rc.pccard and replaced the pccard line with:
 : 
 : pccardd -i 9 -f ${pccard_conf}
 : 
 : It works fine for me. I think there's something wrong with pccardd, and
 : that's why it keeps using IRQs I don't even have specified in
 : pccard.conf. I should do more research on this, though.
 Are you sure that pccard_conf isn't set to /etc/pccard.conf.sample?
 I've *NEVER* seen pccardd use interrupts that it wasn't told about,
 and I've tried many times to reproduce this.

Just for the record, it turned out that the problem I saw with the 574BT
was cured by moving pcic0 from irq 11 (which the PCI bus had appropriated)
to irq 10.  I put the 574 on my last free IRQ, 3.  (Don't you hate laptops?)

Many, many thanks to Matt Dodd and Warner Losh for their help, patience,
suggestions and code!  They were terrific.

Now I'm looking forward to the newcard cardbus support so I can finally use
the 575BT which came with the laptop.  (Tapping fingers impatiently.  :-)
-- 
Frank Mayhar [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: rtld-elf, java + tya

[Russell L. Carter]

I've seen it with yesterdays current and libc_r threads, and it's intermittent.

Russell


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th)

[Warner Losh]

In message [EMAIL PROTECTED] Will Andrews writes:
: On Tue, Jan 18, 2000 at 02:48:25AM -0800, Frank Mayhar wrote:
:  Interestingly, I rebuilt world with the latest pccardd changes and,
:  suddenly, the 589D started working perfectly.  Unfortunately, the
:  574BT doesn't work at all now.  It appears to configure properly, but
:  it doesn't transmit or receive.
: 
: My 574BT works if you hardcode the pccardd IRQ to 9. I did this by
: editing rc.pccard and replaced the pccard line with:
: 
: pccardd -i 9 -f ${pccard_conf}
: 
: It works fine for me. I think there's something wrong with pccardd, and
: that's why it keeps using IRQs I don't even have specified in
: pccard.conf. I should do more research on this, though.

Are you sure that pccard_conf isn't set to /etc/pccard.conf.sample?
I've *NEVER* seen pccardd use interrupts that it wasn't told about,
and I've tried many times to reproduce this.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th)

[Warner Losh]

In message [EMAIL PROTECTED] Frank Mayhar writes:
: Now I'm looking forward to the newcard cardbus support so I can finally use
: the 575BT which came with the laptop.  (Tapping fingers impatiently.  :-)

Hope you are tapping something soft :-)  Wouldn't want you to hurt
yourself, or have others hurt you from the annoying racket :-)

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

even more breakage in current

[Bill Swingle]

I updated my source tree around 10pm PST last night (01/20) and made
world only to find it broken this morning. I reupdated my tree just now
and it doesnt look like any files that might fix this have been touched.
Anyone else seeing this?

cc -pg -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include 
-D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale 
-DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -c 
/usr/src/lib/libc/../libc/gen/wait3.c -o wait3.po
cc -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE 
-DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP 
-I/usr/obj/usr/src/i386/usr/include -I/usr/src/lib/libc/i386 -c 
/usr/src/lib/libc/../libc/i386/gen/_setjmp.S -o _setjmp.o
cc -DPROF -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE 
-DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP 
-I/usr/obj/usr/src/i386/usr/include -I/usr/src/lib/libc/i386 -c 
/usr/src/lib/libc/../libc/i386/gen/_setjmp.S -o _setjmp.po
/tmp/ccg65684.s: Assembler messages:
/tmp/cco65681.s: Assembler messages:
/tmp/cco65681.s:361: Error: invalid character '(' in opcode
/tmp/ccg65684.s:361: Error: invalid character '(' in opcode
*** Error code 1
*** Error code 1
2 errors
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
root@rooter:/usr/src$ cvs -Rq update -PdA
U etc/MAKEDEV
U etc/pccard.conf.sample
U usr.sbin/pccard/pccardd/cardd.c
U usr.sbin/pccard/pccardd/cardd.h
U usr.sbin/pccard/pccardd/file.c
root@rooter:/usr/src$ 

-Bill


-- 
-=| --- B i l l   S w i n g l e --- http://www.dub.net/
-=| [EMAIL PROTECTED]  - [EMAIL PROTECTED] - [EMAIL PROTECTED] 
-=| Different all twisty a of in maze are you, passages little




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

$B:#$,%A%c%s%9$G$9$h!*2>EP(B(B$BO?<uIUCf!c%@%&%s<+F09=C[!d(B(B

[b-support]

$B"#"#(B $B7HBSEEOC(B  $B:G?75!$N:G?75!\$7$/$O2<5-#U#R#L$K%"%/%;%9$7$F2<$5$$!#(B
http://cwj.to/link.cgi/ID=441/GO=linker/cwm/keitai_shop/gekiyasu/free.html

$B"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#(B

$BFMA3$N%a!<%k<:Ni$$$?$7$^$9!#$b$7!"A4$/6=L#$NL5$$FbMF$H(B
$B$*46$8$K$J$kMM$G$7$?$i!"$*e$N%]%8%7%g%s$,3NJ]$G$-$^$9$h!#(B
$B4X@>CO6h0J30$NJ}$O!"8r495!4pCO6I$,40@.$9$k$^$G(B
$B2>2q0wEPO?$G>R2p3hF0$G$-$^$9!#2>EPO?$OL5NA$G$9!*(B
  $B!1!1!1!1!1!1!1!1!1(B
$B#17nKv$K;%KZ!"El5~!";0=E!"9-Eg4pCO6I$,2TF03+;O$7$^$9!#(B

$B<+F09=C[$J$N$GAa$$!$A!"EPO?$7$?!$A$G$9!#(B
$B:#8=:_!"CN$j9g$$$NCf7xBgJ*%M%C%H%o!<%+!<$K@<$r$+$1$F$$$^$9$N$G!"(B
$B$"$J$?$NEPO?$N$[$&$,Aa$1$l$P$=$NJ}$?$A$,$"$J$?$N%@%&%s$K(B
$B$D$/2DG=@-$O$+$J$j$"$j$^$9!#(B

$B$H$j$"$($:$@$1$NEPO?$b#O#K!#3hF0$9$k$7$J$$$O$^$C$?$/<+M3!#(B
$B$b$&>/$7MM;R$r8+$?$$?M$bEPO?$@$1$J$i7P:QE*IiC4$O$$$C$5$$$J$7!#(B
$B$I$&$;EPO?$O%?%@$@$+$i!&!&!&!!$=$l$G$b%@%&%s$OIU$-$^$9!#(B
$B$H$j$"$($:EPO?$7$F$*$1$P!"$$$:$l$3$H$"$j!*!*!*(B

$B4JC1$J35MW$r=q$$$F$*$-$^$9$N$G>\$7$/$O(B
$B2qpJs#B#O#X!J(B06-6379-6583$B!!Am9g%a%K%e!<$O(B7000#$B!K(B
$B$G0z$-=P$7$F$/$@$5$$!#(B

$B$3$3$,%]%$%s%H!*!*(B $B!c0lHLBhFsR2pNA$,H/@8(B
$B#7!%3FCO$N%j!<%@!<$K$O!"7HBSEEOC$NDj3[%5!<%S%9$,$J$s$HL5NA!*(B

$B!c2q0wFCE5!d(B
$B#1!%@lMQ@~$rMxMQ$7$?;T30EEOC$NDj3[NA6b%5!<%S%9(B
$B#2!%$o$:$+#1#0?M$N>R2p$G2qe$K$h$kG[J,$"$j(B
$B#3!%8D?M8~$1%[!<%`%Z!<%8!J:n@.$+$i8x3+$^$G#1%v7n#8#3#31_!K(B
$B#4!%%Q%=%3%sK\BN#3#9#8#0#01_$GHNGd!J?7IJ!K(B
$B#5!%#N#T#T$h$j%Q%=%3%s$NL5NAG[I[!J(BIBM$B@=!K(B
$B#6!%#F#A#X>pJs%\%C%/%9$,L5NA%l%s%?%k(B
$B#7!%#W#e#b#T#V!J%$%s%?!<%M%C%HC$K1~$8$F<+M3JQ49!J%f%K%l%Y%k!"%P%$%J%j!e$NG[J,$"$j!JG/6bE*%\!<%J%9!K(B
$B#5?M>R2p$G$J$s$HKh7n$N2qHq$,L5NA$G$9!*(B

$B2>EPO?$r$44uK>$5$l$k>l9g$O!"2<$NEPO??=$79~$_Ms$K(B
$BI,MW;v9`$r5-F~$N>e!"JVAw$7$F2<$5$$!#(B

$B!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~(B
$B2>EPO??=$79~$_Ms(B
---
$B!J%U%j%,%J!K!!(B
---
$B$*L>A0(B


---
$B!J%U%j%,%J!K(B
---
$B")(B  ($BI,$:(B7$B7eHV9f$r$45-F~$/$@$5$$(B)


$B$4=;=j(B


---
$BEEOCHV9f(B


---
FAX$BHV9f(B


---
$BEE;R%a!<%k%"%I%l%9(B

---





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: rtld-elf, java + tya

[John Polstra]

In article [EMAIL PROTECTED],
Russell L. Carter [EMAIL PROTECTED] wrote:
 I've seen it with yesterdays current and libc_r threads, and it's intermittent.

Did this problem just start, or has it been there for awhile?  I
haven't changed the dynamic linker in -current since January 9, and
I'm wondering if a more recent change in a different part of the
system is causing trouble.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra  Co., Inc.Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: rtld-elf, java + tya

[Amancio Hasty]

I am fairly certain that Java + TYA worked before Jan 7 -- haven't
upgraded my system since then.

-- 
 Amancio Hasty
 [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Please help spread the CVSup mirror load more evenly

[John Polstra]

This is another in my series of occasional nags to try to get people
to use some of the less heavily loaded CVSup mirrors.  In the US
alone, we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org.
The newest, cvsup8, is a very high-capacity and well-connected site,
yet hardly anybody is using it.  Please give it a try!

You can find the full list of mirrors worldwide at:

http://www.freebsd.org/handbook/mirrors-cvsup.html

Remember, the mirrors are equivalent in the sense that they get
their updates from the master server at the same intervals (hourly).
There is nothing "better" about the lower-numbered mirrors, and they
don't get their updates any sooner or more reliably.  In fact, the
higher-numbered mirrors often have faster hardware simply because
they're newer.  Also, in particular, there's nothing special about
cvsup.FreeBSD.org -- it's simply an alias for cvsup1 and it gets its
updates the same way at the same intervals from the same master server
as all the other mirrors.

To choose a mirror site, try pinging the mirrors in your country.
Pick one with a low packet loss rate.  The round trip time doesn't
matter very much as long as it doesn't undergo wild variations.
Second, pick a site that's not too heavily loaded.  If your update
_ever_ fails because the server is too busy, then you should try a
different mirror -- because there are many mirrors that aren't even
close to their full loads even at the busiest of times.

Thanks for your cooperation.

John
---
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra  Co., Inc.Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: rtld-elf, java + tya

[Russell L. Carter]

|From [EMAIL PROTECTED] Fri Jan 21 11:23:14 2000
|
|In article [EMAIL PROTECTED],
|Russell L. Carter [EMAIL PROTECTED] wrote:
| I've seen it with yesterdays current and libc_r threads, and it's intermittent.
|
|Did this problem just start, or has it been there for awhile?  I
|haven't changed the dynamic linker in -current since January 9, and
|I'm wondering if a more recent change in a different part of the
|system is causing trouble.

I first saw it yesterday, and I've been building pretty regularly
on a tracking current box.  

This is a CORBA C++ application linking against ACE/TAO, i.e., not easy
to simplify.  I think I saw it maybe twice out of 50 builds.  I'm away
from that box right now, I'll pay more attention when I get back to
it tonight, and let you know if I can get any repeatability.

Russell

|
|John
|-- 
|  John Polstra   [EMAIL PROTECTED]
|  John D. Polstra  Co., Inc.Seattle, Washington USA
|  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa
|
|


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Amancio Hasty]

If the user does specifiy a cvsup , can you decide for the user which
server is best based upon some simple statistic?
-- 
 Amancio Hasty
 [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Josef Karthauser]

On Fri, Jan 21, 2000 at 10:43:39AM -0800, John Polstra wrote:
 
 To choose a mirror site, try pinging the mirrors in your country.
 Pick one with a low packet loss rate.  The round trip time doesn't
 matter very much as long as it doesn't undergo wild variations.
 Second, pick a site that's not too heavily loaded.  If your update
 _ever_ fails because the server is too busy, then you should try a
 different mirror -- because there are many mirrors that aren't even
 close to their full loads even at the busiest of times.
 
 Thanks for your cooperation.
 
 John

Can you make cvsup accept multiple servers to try in it's configuration
file?

Joe
-- 
Josef KarthauserFreeBSD: Take the red pill and we'll show you just how
Technical Manager   deep the rabbit hole goes. (http://www.uk.freebsd.org)
Pavilion Internet plc.  [[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[John Polstra]

In article [EMAIL PROTECTED], I wrote:

 To choose a mirror site, try pinging the mirrors in your country.

I have been reminded that a few mirrors (cvsup8 in particular) filter
pings.  Don't take ping failures as a certain indication that the
server is down.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra  Co., Inc.Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[John Polstra]

In article [EMAIL PROTECTED],
Amancio Hasty  [EMAIL PROTECTED] wrote:

 If the user does specifiy a cvsup , can you decide for the user which
 server is best based upon some simple statistic?

Some day I hope it's possible, but there's nothing like that
implemented currently.  Also there are some problems that must be
solved first.  CVSup needs a way to ensure that your "update" won't
in fact be a step backward in time.  For example, suppose you update
twice in rapid succession, first from server A and then from server
B.  Both servers update hourly, but at different times.  You happen to
hit them at a point where A has updated more recently than B.  In that
case you'll be unhappy because your second "update" will instead be a
"downdate" (backdate? bad date?).

This is solvable, but not as easily as you might think.  Lots of
complications arise when, for example, you interrupt an update in the
middle such that some files have been updated while others haven't.

There is discussion on all this in the mailing list archives
somewhere.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra  Co., Inc.Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Amancio Hasty]

So have the cvsup client do the pinging to the server and extract
its current work load or other vital statistic.



-- 
 Amancio Hasty
 [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: rtld-elf, java + tya

[John Polstra]

In article [EMAIL PROTECTED],
Amancio Hasty  [EMAIL PROTECTED] wrote:
 I am fairly certain that Java + TYA worked before Jan 7 -- haven't
 upgraded my system since then.

Yes, that assert that failed wasn't in the dynamic linker on January
7.  What I need to know is: did it start failing soon after January
9, or only just in the past few days?

Also I really need a stack trace of a failure to analyze.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra  Co., Inc.Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[John Polstra]

 Can you make cvsup accept multiple servers to try in it's configuration
 file?

I'll add that to the to-do list.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra  Co., Inc.Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ...(file transfer crashes system) ethernet driver or IP stack bug?

[arnee]

Bill Paul wrote:

 Of all the gin joints in all the towns in all the world, arnee had to walk
 into mine and say:

hehehhe... Oh no!! What did I walk into... a quicksand! :-)

 Ack...
 No, please...
 Stop, you're killing me...
 Aie!

 Oh for the love of *god*. Rip this thing out of your machine now. Put it
 on the ground. Stomp on it. Repeatedly. Then set it on fire. Bury the
 remains in the back yard. Then run - don't walk! - to your local computer
 store, put a crowbar in your wallet, and buy a better ethernet card.

hahhaha!! :-) I knew I would get this... I got this machine for free and used to run 
BeOS on it. It
is *not* a priority to have FreeBSD or any other OS running on this machine. Yes, I've 
thought of not
even taking the damn thing... but since I have another closet to place it in, what the 
heck... I'll
play with it.

 Don't whine, don't bitch, don't moan, don't complain that it works with
 Windows (actually, I bet it doesn't; not on that hardware, using bus
 master DMA for both controllers). Just do it.

Hmm... and yes not the best compare to my 3Coms, but I never thought that the ethernet 
card would be
that bad. And I would never base my decisions ("..whine, ..bitch, ..moan, ..complain") 
of using it
because the hardware works with win9x. I have 2 linux boxes, a freebsd 3.2 box, and  2 
other win9x
boxes using FA310TX and they work just fine. A couple of them connected to a 10Mbps 
3com hub (with 2
other boxes with 3Com NICs) and the others, plus this machine, connected to a 100Mbps 
Netgear hub
(with other boxes with 3Com NICs).

 You have a Cyrix CPU, and I'm willing to bet you've overclocked it. ("What?
 You mean that might have some effect on the situation?") You have a PCI
 chipset which the probe messages don't even identify, and you're using
 not one but *two* bus master devices on it, one of which is a PNIC ethernet
 controller that can barely do bus master DMA correctly on a good day. Not
 only that, but you have two ATA controllers in this machine, one of which has
 no devices on it, and you have the damn hard disk on the *second* controller.
 Why do you have two controllers? Why not just use the built-in one!

Yes, one would wonder why. But, it is some what of a catch 22 installing 4.0-current. 
I am using a
17gig (Ultra-ATA/66 capable) harddrive with a MB bios that can only handle 8.4gig 
(Ultra-ATA/33)
harddrive. And since I have a Promise Ultra-ATA/66 controller that 4.0-current 
supports.. why not!
Yes, I know there are other, in fact many other ways to make it work... one is by 
compiling a 3.4
kernel with a patch--or does 3.4-stable now supports the card (ATA/66)? However, there 
is no point,
and it's not feasible, of reverting the harddrive to an ATA/33, which the MB bios will 
not see
anyway, to make it work.

 Does this have something to do with the PNIC? Oh, probably. But I'm not going
 to even attempt to debug this. There's no way in hell I could duplicate this
 hardware configuration locally, and even if I did, I probably couldn't
 duplicate the exact same problem. And even if I could do *that*, I
 still wouldn't know how to fix it. I'm sorry, but I've pulled out enough
 hair over this damn chip. I'm sure I've wasted at least a couple months
 of my life trying to make this thing work reliably. I've added several
 software workarounds, I defaulted the stupid transmit threshold setting
 to store and forward mode. Well I've had it: no more. I'm through trying
 to bitchslap this rotten piece of silicon to its senses. I'm not going to
 go nuts every time somebody comes up with yet another oddball hardware
 combination. There's a limit to my patience and this chip has reached it.
 Now it's somebody else's turn to lose their sanity. I have the datasheet for
 the PNIC at http://www.freebsd.org/~wpaul/PNIC. You have the driver source.
 Somebody *else* try and figure it out, and then tell me then answer when
 you have it.

Well, I would say that my FreeBSD 3.2 box (with not so "oddball hardware combination" 
:-)) is doing
just fine with this NIC... and I bow my hat to you, thank you.

 That said, if you have overclocked this machine, then un-overclock it *right*
 *now* and never, ever do it again! PCI bus master DMA is goofy enough without
 people sticking their fingers in the works.

Although I don't remember overclocking it... I'll take a look.

 Man, why does PC hardware have to suck so hard.

 -Bill

Thanks for the insight and help.

arnee
"Ack.. a spider!! That damn "bug" always *gets* my attention! :-)
Sorry, just a little humor!



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Warning: ioctl(... TUNSLMODE ...) to be depricated....

[Brian Somers]

Unless there are objections in the next day or two, I'm going to 
deprecate the TUNSLMODE ioctl favour of TUNSIFHEAD.  Where TUNSLMODE 
prepended a sockaddr to each packet, TUNSIFHEAD will instead prepend a 
4-byte network-byte-order address family.

Jordan, I believe this change should go into 4.0-RELEASE rather than 
happening afterwards so that we have a minimal number of people 
(hopefully none) using TUNSLMODE.  TUNSLMODE was never MFC'd.

Cheers.

I wrote (on [EMAIL PROTECTED]):
  * Brian Somers [EMAIL PROTECTED] [000120 15:30] wrote:
   Hi,
   
   I know this is a while in coming, but now that I'm looking at getting 
   ppp(8) to talk IPv6 (with the help of some KAME patches), I've looked 
   at how TUNSLMODE is implemented... it doesn't look good to me.
   
   What's the rationale behind stuffing the entire sockaddr in front of 
   the packet ?  AFAIK the only information of any use is the address 
   family.
   
   By default, OpenBSD has a u_int32_t in front of every packet (I 
   believe this is unconfigurable), and I think this is about the most 
   sensible thing to do - I don't see that alignment issues will cause 
   problems.
   
   Alfred, this was originally submitted by you.  Do you have any 
   argument against me changing it to just stuff the address family 
   as a 4-byte network-byte-order quantity there ?
   
   Any other opinions/arguments ?
  
  No objections, I just did it as an excercise to implement something
  in the manpages.
 
 I think the best plan is if I remove TUNSLMODE and introduce (say) 
 TUNSIFHEAD.  If I reuse TUNSLMODE, I'll bump into all sorts of 
 problems.
 
 Now if someone was to say ``NetBSD does it this way'' I'd be 
 interested in copying that :*]
 
  -- 
  -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]

-- 
Brian [EMAIL PROTECTED][EMAIL PROTECTED]
  http://www.Awfulhak.org   [EMAIL PROTECTED]
Don't _EVER_ lose your sense of humour !  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Warning: ioctl(... TUNSLMODE ...) to be depricated....

[Jordan K. Hubbard]

 Jordan, I believe this change should go into 4.0-RELEASE rather than 
 happening afterwards so that we have a minimal number of people 
 (hopefully none) using TUNSLMODE.  TUNSLMODE was never MFC'd.

Do it. :)

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make release broken

[Wilko Bulte]

On Fri, Jan 21, 2000 at 09:19:22AM +0200, John Hay wrote:
 Stop in /usr/src/release.
 *** Error code 1
 
 Stop in /usr/src/release.
 *** Error code 1
 
 Stop in /usr/src/release.
 ---
 
 It looks like the handling of HARDWARE.TXT in release/Makefile is broken.

HARDWARE.TXT was missing. Should be corrected by a commit I've done 
15 minutes ago.

Wilko
-- 
Wilko Bulte Arnhem, The Netherlands   - The FreeBSD Project 
WWW : http://www.tcja.nl  http://www.freebsd.org


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Warner Losh]

In message [EMAIL PROTECTED] John Polstra writes:
:  Can you make cvsup accept multiple servers to try in it's configuration
:  file?
: 
: I'll add that to the to-do list.

I have a very crude script that does its own (fixed) round robin of
multiple servers.  It tries three times fast (yes, I know that's
likely bad) and then goes to the next one on the list.  If all else
fails, it will try the first one on the list in "forever" mode (with
the nice random retries).

I'll have to see about puitting into good shape and posting it.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: UDF

[Conrad Minshall]

At 1:20 AM -0800 1/15/00, Soren Schmidt wrote:
It seems Harold Gutch wrote:
 On Fri, Jan 14, 2000 at 09:29:58AM +0100, Soren Schmidt wrote:

  I have it on my TODO list, but I'm not started yet, and probably wont for
  some time to come.
  The reason I've put it on the backburner for now, is that DVD's can
  be read using the cd9660 filesystem, and that is sufficient for my
  needs for the time being.

 I was under the impression that this was only possible as long as
 the DVDs actually had an ISO9660 filesystem as well - which all
 of my DVDs have, but which still doesn't mean that there are no
 DVDs with only UDF, but no ISO9660 filesystem.

I'm pretty sure all DVD's produced to date have an iso9660 file sys
on them, but they might change that in the future, so having UDF
support would be a win for us in the long run.

DVD Forum's DVD-Video spec requires the UDF Bridge format, which gives you
both UDF and 9660 metadata without duplicating file data.  Commercial DVD
videos are currently using this format.  Bridge format is intended for
read-only usage - as far as I know all DVD-RAM use is and will be
restricted to "mono-metadata".


--
Conrad Minshall ... [EMAIL PROTECTED] ... 408 974-2749
Apple Computer ... Mac OS X Core Operating Systems ... NFS/UDF/etc
Alternative email address: [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Garance A Drosihn]

At 9:42 PM +0100 1/21/00, Jesper Skriver wrote:
On Fri, Jan 21, 2000 at 03:34:42PM -0500, Garance A Drosihn wrote:
  At 10:43 AM -0800 1/21/00, John Polstra wrote:
  This is another in my series of occasional nags to try to get
  people to use some of the less heavily loaded CVSup mirrors.
 
  Maybe you should make cvsup.freebsd.org as a rotary (of sorts),
  which returns a different IP address based on the callers IP
  address.  (or is that even possible?)  That way, any given
  host will always try the same cvsup server, but you'll be
  spreading the load out among the servers.

Dial-up users with dynamic ip address assignment ...

You don't do it based on the last digit in the ip address.  Do
it based on the first number, or maybe the first two numbers.
Ie, all IP addresses at RPI are 128.113.*.*, so they would all
get the same value for this DNS rotary.  If you did it in large
enough ranges, it should be pretty consistent even for people
coming in via dynamic IP addresses.

It'd still be a problem for someone who's on the move a lot,
of course (such as a laptop which is sometimes used on the RPI
campus, and other times is dialing in thru various ISP's around
the country).

And to my best knowledge, BIND does not support anything
like that.

Not directly, but I think there are ways you can have it call
some external procedure to do "load-balancing" for an IP
rotary.  We talked about doing this to address a problem here
at RPI, but then we figured out an alternate solution so we
didn't really get to the point of implementing it.  I don't
know if that external load-balancing procedure is given the
IP address of the host doing the lookup, for instance.

I'm just trying to come up with something that automatically
balances the load, while still making it pretty likely that a
given host will always get the same cvsup server.


---
Garance Alistair Drosehn   =   [EMAIL PROTECTED]
Senior Systems Programmer  or  [EMAIL PROTECTED]
Rensselaer Polytechnic Institute


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Wes Peters]

John Polstra wrote:
 
  Can you make cvsup accept multiple servers to try in it's configuration
  file?
 
 I'll add that to the to-do list.

A nice heuristic that attempts to minimize latency and maximize throughput
would be a nice feature to have.  For extra credit, reverse entropy as well.

Seriously, attempting to connect to a list of servers using record route
and minimizing the latency and/or hop count would be a great little feature
to add.  It would be a great feature to package into a library.

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Chuck Robey]

On Fri, 21 Jan 2000, Warner Losh wrote:

 In message [EMAIL PROTECTED] Chuck Robey 
writes:
 : I would think using a fixed order would be a really bad thing, causing
 : overload of the first server in line.  Did I misunderstand you?  How about
 : doing a script (say in perl, it has random numbers) that randomly picks
 : the server from a list? That way, the list could even be weighted, so as
 : to allow for greater or lesser machine resources (like net access).
 
 That's one of the things I have to fix up.  This script is good for
 me, but bad for everyone.  Enhancements like this would be a good
 thing.  Got time?

I don't know perl.  Darn.  Yes, I will learn perl.  Now.

 
 Warner
 


Chuck Robey| Interests include C  Java programming, FreeBSD,
[EMAIL PROTECTED]  | electronics, communications, and signal processing.

New Year's Resolution:  I will not sphroxify gullible people into looking up
fictitious words in the dictionary.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Chuck Robey]

On Fri, 21 Jan 2000, Warner Losh wrote:

 In message [EMAIL PROTECTED] John Polstra writes:
 :  Can you make cvsup accept multiple servers to try in it's configuration
 :  file?
 : 
 : I'll add that to the to-do list.
 
 I have a very crude script that does its own (fixed) round robin of
 multiple servers.  It tries three times fast (yes, I know that's
 likely bad) and then goes to the next one on the list.  If all else
 fails, it will try the first one on the list in "forever" mode (with
 the nice random retries).
 
 I'll have to see about puitting into good shape and posting it.

I would think using a fixed order would be a really bad thing, causing
overload of the first server in line.  Did I misunderstand you?  How about
doing a script (say in perl, it has random numbers) that randomly picks
the server from a list? That way, the list could even be weighted, so as
to allow for greater or lesser machine resources (like net access).



Chuck Robey| Interests include C  Java programming, FreeBSD,
[EMAIL PROTECTED]  | electronics, communications, and signal processing.

New Year's Resolution:  I will not sphroxify gullible people into looking up
fictitious words in the dictionary.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Louis A. Mamakos]

 A nice heuristic that attempts to minimize latency and maximize throughput
 would be a nice feature to have.  For extra credit, reverse entropy as well.
 
 Seriously, attempting to connect to a list of servers using record route
 and minimizing the latency and/or hop count would be a great little feature
 to add.  It would be a great feature to package into a library.

I fear that the effort expended to do anything more than the easy 20% will
be wasted.  Trying to second-guess end-to-end network characteristics by
reading the tea-leaves of a traceroute-like probe is going to be very hard.
You should measure the characteristics which are exposed to your application,
if possible, and make decisions based on that.

For instance, on UUNET's backbone network (of which I happen to know quite a 
lot about since I did some of the original architecture) has an extensive
layer-2 ATM and Frame Relay component used to do traffic engineering.  Even
though there are multiple layer-2 hops through switches, you can't see any
of that using a traceroute-like mechanism.  And forget about record route
options; that's going to cause the packet to go through the slow forwarding
path of the router, which is essentially completely unrelated to experience
the packet has without the record route option, other than taking the same
path.

As John mentioned earlier, what your probably most interested in is
patch quality (e.g., minimum packet loss) first and latency second as
far as network characteristics are concerned.  Simply measure them if
you choose rather than trying to understand why the latency is what is.
Trying to predict path quality based on observed topology is hard to
do in an automated fashion.  Sure, you can employ some simply heuristics
as a human (e.g., don't go through MAE-EAST - it sucks there) and the
occasional traceroute will reduce your candidate list of servers to a
likely set which won't suck and are in the same hemisphere.

I fear trying to be significantly more clever than that and simple 
measurements is Very Hard and can probably get you a Ph.D. or a bunch
of $$$ or both.  If you succeed.

louie



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Andre Oppermann]

Garance A Drosihn wrote:
 
 At 10:43 AM -0800 1/21/00, John Polstra wrote:
 This is another in my series of occasional nags to try to get people
 to use some of the less heavily loaded CVSup mirrors.  In the US
 alone, we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org.
 The newest, cvsup8, is a very high-capacity and well-connected site,
 yet hardly anybody is using it.  Please give it a try!
 
 Maybe you should make cvsup.freebsd.org as a rotary (of sorts),
 which returns a different IP address based on the callers IP
 address.  (or is that even possible?)  That way, any given
 host will always try the same cvsup server, but you'll be
 spreading the load out among the servers.

Thats not so easy. What about this:

cvsup   IN CNAMEcvsup1.freebsd.org.
cvsup   IN CNAMEcvsup2.freebsd.org.
cvsup   IN CNAMEcvsup3.freebsd.org.
cvsup   IN CNAMEcvsup4.freebsd.org.
cvsup   IN CNAMEcvsup5.freebsd.org.
cvsup   IN CNAMEcvsup6.freebsd.org.
cvsup   IN CNAMEcvsup7.freebsd.org.
cvsup   IN CNAMEcvsup8.freebsd.org.

If you simply put "cvsup.freebsd.org" into your supfile you'll get
randomly one of them. This should spread the load fairly well. If
you want a special one then simply put "cvsupX.freebsd.org" into
you supfile.

Aint that easy?

I don't see any appearant reson (short of network connectivity) that
one *needs* to get always the *same* server.

-- 
Andre


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Jesper Skriver]

On Fri, Jan 21, 2000 at 11:06:40PM +0100, Andre Oppermann wrote:
 Garance A Drosihn wrote:
  
  At 10:43 AM -0800 1/21/00, John Polstra wrote:
  This is another in my series of occasional nags to try to get people
  to use some of the less heavily loaded CVSup mirrors.  In the US
  alone, we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org.
  The newest, cvsup8, is a very high-capacity and well-connected site,
  yet hardly anybody is using it.  Please give it a try!
  
  Maybe you should make cvsup.freebsd.org as a rotary (of sorts),
  which returns a different IP address based on the callers IP
  address.  (or is that even possible?)  That way, any given
  host will always try the same cvsup server, but you'll be
  spreading the load out among the servers.
 
 Thats not so easy. What about this:
 
 cvsup IN CNAMEcvsup1.freebsd.org.
 cvsup IN CNAMEcvsup2.freebsd.org.
 cvsup IN CNAMEcvsup3.freebsd.org.
 cvsup IN CNAMEcvsup4.freebsd.org.
 cvsup IN CNAMEcvsup5.freebsd.org.
 cvsup IN CNAMEcvsup6.freebsd.org.
 cvsup IN CNAMEcvsup7.freebsd.org.
 cvsup IN CNAMEcvsup8.freebsd.org.
 
 If you simply put "cvsup.freebsd.org" into your supfile you'll get
 randomly one of them. This should spread the load fairly well. If
 you want a special one then simply put "cvsupX.freebsd.org" into
 you supfile.
 
 Aint that easy?
 
 I don't see any appearant reson (short of network connectivity) that
 one *needs* to get always the *same* server.

This has been discussed regulary ...

You will risk hitting 2 different server in 2 rapid cvsup run's, where
the first may be more up to date than the next, as Jordan wrote earlier
in this thread ...

/Jesper

-- 
Jesper Skriver, jesper(at)skriver(dot)dk  -  CCIE# 5456
Work:Network manager @ AS3292 (Tele Danmark DataNetworks)
Private: Geek@ AS2109 (A much smaller network ;-)

One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Andrew Reilly]

On Fri, Jan 21, 2000 at 04:24:41PM -0500, Chuck Robey wrote:
 On Fri, 21 Jan 2000, Warner Losh wrote:
  In message [EMAIL PROTECTED] Chuck Robey 
writes:
  : I would think using a fixed order would be a really bad thing, causing
  : overload of the first server in line.  Did I misunderstand you?  How about
  : doing a script (say in perl, it has random numbers) that randomly picks
  : the server from a list? That way, the list could even be weighted, so as
  : to allow for greater or lesser machine resources (like net access).
  
  That's one of the things I have to fix up.  This script is good for
  me, but bad for everyone.  Enhancements like this would be a good
  thing.  Got time?
 
 I don't know perl.  Darn.  Yes, I will learn perl.  Now.

sh has random numbers.  Spelled "jot -r".

-- 
Andrew


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Louis A. Mamakos]

  Maybe you should make cvsup.freebsd.org as a rotary (of sorts),
  which returns a different IP address based on the callers IP
  address.  (or is that even possible?)  That way, any given
  host will always try the same cvsup server, but you'll be
  spreading the load out among the servers.
 
 Thats not so easy. What about this:
 
 cvsup IN CNAMEcvsup1.freebsd.org.
 cvsup IN CNAMEcvsup2.freebsd.org.
 cvsup IN CNAMEcvsup3.freebsd.org.
 cvsup IN CNAMEcvsup4.freebsd.org.
 cvsup IN CNAMEcvsup5.freebsd.org.
 cvsup IN CNAMEcvsup6.freebsd.org.
 cvsup IN CNAMEcvsup7.freebsd.org.
 cvsup IN CNAMEcvsup8.freebsd.org.

This is wrong two ways.

First, the data associated with a CNAME is supposed to be the
cannonical name of a host, and not another domain name with only
a CNAME resource record.

Second, a domain name can at most a single CNAME record associated
with it, and other other record types.  BIND will (should) barf on a
zone file containing the example you listed.

 If you simply put "cvsup.freebsd.org" into your supfile you'll get
 randomly one of them. This should spread the load fairly well. If
 you want a special one then simply put "cvsupX.freebsd.org" into
 you supfile.

You could play some DNS games to get this effect, though it's not
clear what the randomness of the list of resource records is supposed
to be.  Certain the DNS protocol doesn't define any randomness.

 I don't see any appearant reson (short of network connectivity) that
 one *needs* to get always the *same* server.

See previous mesasge from John regarding doing two successive updates
where the servers are not synchronized with the same version files.

Is this really a problem that demands solutions this complicated?  The
solution isn't necessarily a technological one;  a simple email message
reminding people of other servers might be sufficient :-)

louie




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

when is FreeBSD-4.0 up for release ?

[Mohit Aron]

Hi,
wasn't the release date set for Jan 15 ? Anyone knows the new 
tentative date ? Thanks,


- Mohit


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: when is FreeBSD-4.0 up for release ?

[Will Andrews]

On Fri, Jan 21, 2000 at 04:14:47PM -0600, Mohit Aron wrote:
 Hi,
   wasn't the release date set for Jan 15 ? Anyone knows the new 
 tentative date ? Thanks,

That was the Feature Freeze (tm). Jordan hasn't made any "official"
announcements about the Feature Freeze yet, I don't think.

Anyway, the release should be out a few weeks after the Code Freeze
(tm), which should be around February 7th or 15th. Personally, I think
it'll be March before 4.0-RELEASE hits the door.

--
Will Andrews [EMAIL PROTECTED]
GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ 
G+ e- h! r--+++ y?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Andre Oppermann]

Brad Knowles wrote:
 
 At 11:06 PM +0100 2000/1/21, Andre Oppermann wrote:
 
   Thats not so easy. What about this:
 
   cvsupIN CNAMEcvsup1.freebsd.org.
   cvsupIN CNAMEcvsup2.freebsd.org.
   cvsupIN CNAMEcvsup3.freebsd.org.
   cvsupIN CNAMEcvsup4.freebsd.org.
   cvsupIN CNAMEcvsup5.freebsd.org.
   cvsupIN CNAMEcvsup6.freebsd.org.
   cvsupIN CNAMEcvsup7.freebsd.org.
   cvsupIN CNAMEcvsup8.freebsd.org.
 
 As I understood the rules of good Domain Administration,
 everything that is publicly visible in your network needs to have an
 MX record.  But with this scheme you can't give cvsup.freebsd.org an
 MX record, because pointing an MX at a CNAME violates the RFC.

You can, simply do this:

cvsup   IN MX   10 hub.freebsd.org

No violation of any RFC whatsoever.

 Personally, I would much prefer the CPAN solution of a program
 that takes the IP address of the query source, and then using
 knowledge of what IP addresses are generally located where in the
 world (available via the whois maps in the various regions, which
 could presumably be imported and stored locally), returns a short
 list of addresses in the preferred order.  For those networks where
 multiple addresses may have equal "cost", it can then randomize for
 load balancing purposes.

Don't go by whois, it does not reflect the physical connectivity. Go
by BGP path length if you want to do something like this.

 It requires either a hacked nameserver program for this one zone,
 or the code to handle this has to be incorporated into cvsup itself,
 so that you distribute the logic and CPU processing time to all the
 clients.

There are commecial nameservers which decide upon bgp path length but
it'll cost some big $$$.

-- 
Andre


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: when is FreeBSD-4.0 up for release ?

[Warner Losh]

In message [EMAIL PROTECTED] Mohit Aron writes:
:   wasn't the release date set for Jan 15 ? Anyone knows the new 
: tentative date ? Thanks,

No.  Jan 15 was a feature freeze.  Likely first part of Feb for a
release, but no date has been widely circulated.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Steve Kargl]

Andre Oppermann wrote:
 Jesper Skriver wrote:
  
 
  You will risk hitting 2 different server in 2 rapid cvsup run's, where
  the first may be more up to date than the next, as Jordan wrote earlier
  in this thread ...
 
 Does it matter? Who cvsup's regulary more than once or twice a day?
 Committers AFAIK do cvs directly.
 

%cvsup
Damn!  Forgot I don't want src-sys -- Hit ^C.
%vi ~/supfileRemove src-sys
%cvsup

or

%cvsup
Damn!  Forgot I want to remove sup/src-sys/refuse -- Hit ^C.
%rm sup/src-sys/refuse
%cvsup

Yes, I've done both scenarios.

-- 
Steve


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Matthew Hunt]

On Fri, Jan 21, 2000 at 11:39:24PM +0100, Andre Oppermann wrote:

 Does it matter? Who cvsup's regulary more than once or twice a day?
 Committers AFAIK do cvs directly.

I "cvs co" from my local copy of the repository, which is kept
up-to-date using cvsup.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Andre Oppermann]

Louis A. Mamakos wrote:
  cvsup IN CNAMEcvsup1.freebsd.org.
  cvsup IN CNAMEcvsup2.freebsd.org.
  cvsup IN CNAMEcvsup3.freebsd.org.
  cvsup IN CNAMEcvsup4.freebsd.org.
  cvsup IN CNAMEcvsup5.freebsd.org.
  cvsup IN CNAMEcvsup6.freebsd.org.
  cvsup IN CNAMEcvsup7.freebsd.org.
  cvsup IN CNAMEcvsup8.freebsd.org.
 
 This is wrong two ways.
 
 First, the data associated with a CNAME is supposed to be the
 cannonical name of a host, and not another domain name with only
 a CNAME resource record.

??? Are all cvsupX.freebsd.org also CNAME's?

 Second, a domain name can at most a single CNAME record associated
 with it, and other other record types.  BIND will (should) barf on a
 zone file containing the example you listed.

It does not. It will round-robin over the CNAME's.

  If you simply put "cvsup.freebsd.org" into your supfile you'll get
  randomly one of them. This should spread the load fairly well. If
  you want a special one then simply put "cvsupX.freebsd.org" into
  you supfile.
 
 You could play some DNS games to get this effect, though it's not
 clear what the randomness of the list of resource records is supposed
 to be.  Certain the DNS protocol doesn't define any randomness.

But bind does.

  I don't see any appearant reson (short of network connectivity) that
  one *needs* to get always the *same* server.
 
 See previous mesasge from John regarding doing two successive updates
 where the servers are not synchronized with the same version files.

Who cvsup's regurlary more than once or twice a day? Committers AFAIK
do cvs directly.

 Is this really a problem that demands solutions this complicated?  The
 solution isn't necessarily a technological one;  a simple email message
 reminding people of other servers might be sufficient :-)

Yea, then all swamp cvsup8.freebsd.org and John has to send another
message that there are still cvsup[2-7].freebsd.org idling around.
Just kidding... But you get the point?

-- 
Andre


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[sthaug]

  Second, a domain name can at most a single CNAME record associated
  with it, and other other record types.  BIND will (should) barf on a
  zone file containing the example you listed.
 
 It does not. It will round-robin over the CNAME's.

See the documentation for the multiple-cnames option in BIND 8.2.2:

   If yes, multiple CNAME resource records will be allowed for a domain
   name. The default is no.  Allowing multiple CNAME records is against
   standards and is not recommended. Multiple CNAME support is available
   because previous versions of BIND allowed multiple CNAME records, and
   these records have been used for load balancing by a number of sites.

So I'd say this is not a good idea.

Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Possible IPv6-related problem

[Jos Backus]

Some more information: I can not reproduce the problem with a -current as of
yesterday on my home system. I'll re-check my system at work next week and let
you know.

-- 
Jos Backus  _/ _/_/_/  "Reliability means never
   _/ _/   _/   having to say you're sorry."
  _/ _/_/_/ -- D. J. Bernstein
 _/  _/ _/_/
[EMAIL PROTECTED]  _/_/  _/_/_/  use Std::Disclaimer;


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Andre Oppermann]

Jesper Skriver wrote:
 
 On Fri, Jan 21, 2000 at 11:06:40PM +0100, Andre Oppermann wrote:
  I don't see any appearant reson (short of network connectivity) that
  one *needs* to get always the *same* server.
 
 This has been discussed regulary ...

Must have been some time ago...

 You will risk hitting 2 different server in 2 rapid cvsup run's, where
 the first may be more up to date than the next, as Jordan wrote earlier
 in this thread ...

Does it matter? Who cvsup's regulary more than once or twice a day?
Committers AFAIK do cvs directly.

-- 
Andre


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Andre Oppermann]

Matthew Hunt wrote:
 
 On Fri, Jan 21, 2000 at 11:39:24PM +0100, Andre Oppermann wrote:
 
  Does it matter? Who cvsup's regulary more than once or twice a day?
  Committers AFAIK do cvs directly.
 
 I "cvs co" from my local copy of the repository, which is kept
 up-to-date using cvsup.

OK, then you should hardwire your cvsup server to cvsup[1-8]. You can
master cvs so you can master this. Cvsup.freebsd.org is used by Joe
Random and he wont be cvsupping more than once a day.

-- 
Andre


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Matthew Hunt]

On Fri, Jan 21, 2000 at 11:56:11PM +0100, Andre Oppermann wrote:

 OK, then you should hardwire your cvsup server to cvsup[1-8]. You can
 master cvs so you can master this.

I do.  Thanks for your vote of confidence in my abilities, though.
If you meant "committers use cvs directly or hardwire their
cvsup server", maybe you should have written that.

-- 
Matthew Hunt [EMAIL PROTECTED] * UNIX is a lever for the
http://www.pobox.com/~mph/   * intellect. -J.R. Mashey


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Louis A. Mamakos]

  Second, a domain name can at most a single CNAME record associated
  with it, and other other record types.  BIND will (should) barf on a
  zone file containing the example you listed.
 
 It does not. It will round-robin over the CNAME's.

If it does, than this is a bug in BIND.  The DNS is not defined to
work this way.   Semantically, it doesn't make sense to have more
than one CNAME record.  The CNAME resource record is supposed to
contain the cannonical name for the domain name that it's associated
with.  There can be only one cannonical name.

And it appears that in the latest BIND, they've seen the error of their
ways:

  multiple-cnames
   If yes, then multiple CNAME resource records will be allowed for a do-
   main name.  The default is no. Allowing multiple CNAME records is
   against standards and is not recommended.  Multiple CNAME support is
   available because previous versions of BIND allowed multiple CNAME
   records, and these records have been used for load balancing by a num-
   ber of sites.

In any case, this has turned into a debate on how to (ab)use BIND and
the DNS, and is well off topic.

 Yea, then all swamp cvsup8.freebsd.org and John has to send another
 message that there are still cvsup[2-7].freebsd.org idling around.
 Just kidding... But you get the point?

My only point is that the first response to a problem isn't to necessarily
pull out emacs and start hacking away on code. 

louie




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Andre Oppermann]

[EMAIL PROTECTED] wrote:
 
   Second, a domain name can at most a single CNAME record associated
   with it, and other other record types.  BIND will (should) barf on a
   zone file containing the example you listed.
 
  It does not. It will round-robin over the CNAME's.
 
 See the documentation for the multiple-cnames option in BIND 8.2.2:
 
If yes, multiple CNAME resource records will be allowed for a domain
name. The default is no.  Allowing multiple CNAME records is against
standards and is not recommended. Multiple CNAME support is available
because previous versions of BIND allowed multiple CNAME records, and
these records have been used for load balancing by a number of sites.
 
 So I'd say this is not a good idea.

Ah, well, ok. I used it extensively with bind 8.1.2 in an internal
application in a big bank to get approx. load distribution with
Windumb clients (they always take the first record in the list
returned).

Anyway, if multi CNAME is no good then do:

cvsup   IN A198.104.92.71  ; cvsup1.freebsd.org
cvsup   IN A205.149.189.91 ; cvsup2.freebsd.org
... and so on

This is legal, is it?

-- 
Andre


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Andre Oppermann]

Matthew Hunt wrote:
 
 On Fri, Jan 21, 2000 at 11:56:11PM +0100, Andre Oppermann wrote:
 
  OK, then you should hardwire your cvsup server to cvsup[1-8]. You can
  master cvs so you can master this.
 
 I do.  Thanks for your vote of confidence in my abilities, though.
 If you meant "committers use cvs directly or hardwire their
 cvsup server", maybe you should have written that.

Sorry, I didn't want to offend you. I apologise.

-- 
Andre


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[John Baldwin]

On 21-Jan-00 Andre Oppermann wrote:
 Jesper Skriver wrote:
 
 On Fri, Jan 21, 2000 at 11:06:40PM +0100, Andre Oppermann wrote:
  I don't see any appearant reson (short of network connectivity) that
  one *needs* to get always the *same* server.
 
 This has been discussed regulary ...
 
 Must have been some time ago...

Yes, every few months it seems.

 You will risk hitting 2 different server in 2 rapid cvsup run's, where
 the first may be more up to date than the next, as Jordan wrote earlier
 in this thread ...
 
 Does it matter? Who cvsup's regulary more than once or twice a day?
 Committers AFAIK do cvs directly.

No, cvs is much slower than cvsup.  I, for one, cvsup the repository itself
and then do cvs operations locally against that.

 -- 
 Andre
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Andre Oppermann]

Louis A. Mamakos wrote:
 
   Second, a domain name can at most a single CNAME record associated
   with it, and other other record types.  BIND will (should) barf on a
   zone file containing the example you listed.
 
  It does not. It will round-robin over the CNAME's.
 
 If it does, than this is a bug in BIND.  The DNS is not defined to
 work this way.   Semantically, it doesn't make sense to have more
 than one CNAME record.  The CNAME resource record is supposed to
 contain the cannonical name for the domain name that it's associated
 with.  There can be only one cannonical name.
 
 And it appears that in the latest BIND, they've seen the error of their
 ways:
-snip-

OK, I did it with bind 8.1.2, see my other response to Steinar.

 In any case, this has turned into a debate on how to (ab)use BIND and
 the DNS, and is well off topic.

Back on topic. Do it instead with A records.

Joe Random goes for cvsup.freebsd.org and highly likely wont be
cvsupping more than once a day. Others who do can hardwire to one
specific cvsup server. The best of both worlds with just a few key
strokes and now complies with every imaginable RFC. Uh, I better don't
pray for it.

  Yea, then all swamp cvsup8.freebsd.org and John has to send another
  message that there are still cvsup[2-7].freebsd.org idling around.
  Just kidding... But you get the point?
 
 My only point is that the first response to a problem isn't to necessarily
 pull out emacs and start hacking away on code.

Yea, it is easier to do in a regular zone file then to implement the
network measurement logic into cvsup.

-- 
Andre


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Ben Rosengart]

On Sat, 22 Jan 2000, Andre Oppermann wrote:

 Ah, well, ok. I used it extensively with bind 8.1.2 in an internal
 application in a big bank to get approx. load distribution with
 Windumb clients (they always take the first record in the list
 returned).
 
 Anyway, if multi CNAME is no good then do:
 
 cvsup IN A198.104.92.71  ; cvsup1.freebsd.org
 cvsup IN A205.149.189.91 ; cvsup2.freebsd.org
 ... and so on
 
 This is legal, is it?

Not only is it legal, but I believe BIND will return all the A records
to any query, and will rotate them.

--
 Ben Rosengart

UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Creative ViBRA16X Problem (fwd)

[Jeremy L. Stock]

Thought I'd post this to -current also since it gives a little more detail
(I hope). I can't believe I'm the only one experiencing this since it's
still around when I do a fresh install from a snapshot. Not a huge deal for
me since I can use Windows for audio, but I'd rather use FreeBSD again. I'm
sure this will get addressed before 4.0R. I just wanted to make sure it's a
known issue.

-- 
Jeremy L. Stock [EMAIL PROTECTED]
ICQ 46329337
Fax # 612-629-6540 
-- Forwarded message --
Date: Tue, 18 Jan 2000 22:14:44 -0600 (CST)
From: Jeremy L. Stock [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Creative ViBRA16X Problem

I posted this on -current almost a week ago and only received one response
that didn't solve the problem. Audio hasn't played correctly for me since
December 27th.  Now when I try to play audio, it just stutters.

I'm not sure when it broke since I went from -current as of the 27th to
-current as of the 11th and now earlier today. The problem still remains
even after a total reinstall. 

I just wanted to make sure you were aware of it and make sure you had a
chance to correct it before 4.0R. Here's some info. Let me know if
you need anything else.

Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #0: Tue Jan 18 20:00:28 CST 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/NIC
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 350796057 Hz
CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU)
  Origin = "AuthenticAMD"  Id = 0x58c  Stepping = 12
  Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX
  AMD Features=0x8800SYSCALL,3DNow!
real memory  = 134217728 (131072K bytes)
avail memory = 127315968 (124332K bytes)
Preloaded elf kernel "kernel" at 0xc02c2000.
sbc0: Creative ViBRA16X at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 10 
drq 0,1 on isa0
sbc0: setting card to irq 10, drq 0, 1
pcm0: SB DSP 4.16 (ViBRA16X) on sbc0
unknown0: Game at port 0x201 on isa0

And from boot -v (Let me know if I left an important section out)

Trying Read_Port at 203
CTL0043: start dependant
CTL0043: adding irq mask 0x20
CTL0043: adding dma mask 0x2
CTL0043: adding dma mask 0x8
CTL0043: adding io range 0x220-0x22f, size=0x10, align=0x1
CTL0043: adding io range 0x330-0x331, size=0x2, align=0x1
CTL0043: adding io range 0x388-0x38b, size=0x4, align=0x1
CTL0043: start dependant
CTL0043: adding irq mask 0x6a0
CTL0043: adding dma mask 0xb
CTL0043: adding dma mask 0xb
CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20
CTL0043: adding io range 0x300-0x331, size=0x2, align=0x30
CTL0043: adding io range 0x388-0x38b, size=0x4, align=0x1
CTL0043: start dependant
CTL0043: adding irq mask 0x6a0
CTL0043: adding dma mask 0xb
CTL0043: adding dma mask 0xb
CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20
CTL0043: adding io range 0x300-0x331, size=0x2, align=0x30
CTL0043: start dependant
CTL0043: adding irq mask 0x6a0
CTL0043: adding dma mask 0xb
CTL0043: adding dma mask 0xb
CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20
CTL0043: start dependant
CTL0043: adding irq mask 0x6a0
CTL0043: adding dma mask 0xb
CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20
CTL0043: adding io range 0x300-0x331, size=0x2, align=0x10
CTL0043: adding io range 0x388-0x397, size=0x4, align=0x4
CTL0043: start dependant
CTL0043: adding irq mask 0x6a0
CTL0043: adding dma mask 0xb
CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20
CTL0043: end dependant
CTL7005: start dependant
CTL7005: adding io range 0x201-0x201, size=0x1, align=0x1
CTL7005: start dependant
CTL7005: adding io range 0x200-0x20f, size=0x1, align=0x1
CTL7005: end dependant
isa_probe_children: disabling PnP devices
isa_probe_children: probing non-PnP devices
sbc0: Creative ViBRA16X at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 10 drq 0,1 
on isa0
sbc0: setting card to irq 10, drq 0, 1
pcm0: SB DSP 4.16 (ViBRA16X) on sbc0
pcm: setmap 2d000, 2000; 0xc7814000 - 2d000
pcm: setmap 2f000, 2000; 0xc7816000 - 2f000
unknown0: Game at port 0x201 on isa0

pnpinfo output:

Checking for Plug-n-Play devices...

Card assigned CSN #1
Vendor ID CTL00f0 (0xf0008c0e), Serial Number 0x
PnP Version 1.0, Vendor Version 16
Device Description: Creative ViBRA16X PnP

Logical Device ID: CTL0043 0x43008c0e #0
Device Description: Audio
TAG Start DF
Good Configuration
IRQ: 5  - only one type (true/edge)
DMA: channel(s) 1 
8-bit, not a bus master, count by byte, , Compatibility mode
DMA: channel(s) 3 
8-bit, not a bus master, count by byte, , Compatibility mode
I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10
[16-bit addr]
I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2
[16-bit addr]
I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4
[16-bit addr]
TAG Start DF
Acceptable Configuration
IRQ: 

Re: Please help spread the CVSup mirror load more evenly

[Wes Peters]

Steve Kargl wrote:
 
 Andre Oppermann wrote:
  Jesper Skriver wrote:
  
 
   You will risk hitting 2 different server in 2 rapid cvsup run's, where
   the first may be more up to date than the next, as Jordan wrote earlier
   in this thread ...
 
  Does it matter? Who cvsup's regulary more than once or twice a day?
  Committers AFAIK do cvs directly.
 
 
 %cvsup
 Damn!  Forgot I don't want src-sys -- Hit ^C.
 %vi ~/supfileRemove src-sys
 %cvsup
 
 or
 
 %cvsup
 Damn!  Forgot I want to remove sup/src-sys/refuse -- Hit ^C.
 %rm sup/src-sys/refuse
 %cvsup
 
 Yes, I've done both scenarios.

Perhaps an option to CVSup to test a group of servers and render a "rating"
for each, or to choose a "best" one.  Then an intelligent human being could
use this information to occasionally change which cvsup server they use.

Such a tool wouldn't be specific to CVSup, of course, and probably already
exists in benchmarks.  Suggestions?

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[David O'Brien]

On Fri, Jan 21, 2000 at 11:11:17AM -0800, John Polstra wrote:
 I have been reminded that a few mirrors (cvsup8 in particular) filter
 pings.  Don't take ping failures as a certain indication that the
 server is down.

On Fri, Jan 21, 2000 at 11:22:33AM -0800, Amancio Hasty wrote:
 So have the cvsup client do the pinging to the server and extract
 its current work load or other vital statistic.


I have to agree with Amancio.  Otherwise how are we to determine if
cvsup8 is worth our time?  I personally will not be switching to it until
I can determine it is a better path for me.

Possibly, being ping'able should be be a requirement to being a CVSup
mirror.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Warner Losh]

:  Does it matter? Who cvsup's regulary more than once or twice a day?
:  Committers AFAIK do cvs directly.
: I "cvs co" from my local copy of the repository, which is kept
: up-to-date using cvsup.

When I'm making lots of commits, I'll do 10-20 cvsups in a day, but
usually it is more like 3-5 depending on what I need to track.  I
cvsup the tree itself and co from there.

That's why I wrote the script I did.  I'll clean it up tonight and
post it.

Warner



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: when is FreeBSD-4.0 up for release ?

[David O'Brien]

On Fri, Jan 21, 2000 at 05:33:53PM -0500, Will Andrews wrote:
 On Fri, Jan 21, 2000 at 04:14:47PM -0600, Mohit Aron wrote:
  Hi,
  wasn't the release date set for Jan 15 ? Anyone knows the new 
  tentative date ? Thanks,
 
 That was the Feature Freeze (tm). Jordan hasn't made any "official"
 announcements about the Feature Freeze yet, I don't think.

What do you mean?  JKH said there would be a Feature Freeze on Jan 15 and
it happened.  What more did JKH need to say on the topic?

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: even more breakage in current

[David O'Brien]

On Fri, Jan 21, 2000 at 02:22:51PM -0800, Jason Evans wrote:

 I did a 'make includes' during my testing, so I didn't have this
 problem.
...
 
 In any case, doing a 'make includes' will get you past this.

But this is not a very satisfiable bootstrap requirement.
We need to keep in mind that that
cd /usr/src
cvs up
make world

is how it is done.  If things wont build, then a solution w/in the
"world" Makefiles need to be found.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Amancio Hasty]

  My only point is that the first response to a problem isn't to necessarily
  pull out emacs and start hacking away on code.
 
 Yea, it is easier to do in a regular zone file then to implement the
 network measurement logic into cvsup.

Yes, it is a rather cool idea to rotate on the cvs servers without
respect to latency, work load  or rate of service response from 
the server.




-- 
 Amancio Hasty
 [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Amancio Hasty]

Hi David,

John can implement a ping echo packet protocol for cvsup whose
response can have "cool" information on the server. Steven's
book on Networking already has the code for doing network latency
calculations . It is more like if John has the time to implement
such scheme 




-- 
 Amancio Hasty
 [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Brooks Davis]

On Fri, Jan 21, 2000 at 04:47:42PM -0700, Wes Peters wrote:
 Perhaps an option to CVSup to test a group of servers and render a "rating"
 for each, or to choose a "best" one.  Then an intelligent human being could
 use this information to occasionally change which cvsup server they use.
 
 Such a tool wouldn't be specific to CVSup, of course, and probably already
 exists in benchmarks.  Suggestions?

For the actual testing, netperf would probalby be a good choice assuming
the server admins will cooperate (or the server was integrated into
cvsupd).  The normal version is a standalone program, but there is a
libritized version as part of the gloperf daemon which is part of the
globus project (www.globus.org).

As to storing the list of ratings, it would be really nice if such a
tool cached them on a per-subnet bases so us telecommuters can move
around and cvsup from random ethernet ports with dhcp support.  In
general, ratings based on network performance are likely to be good for
quite some time.  The things you probably wouldn't want to cache would
be servers loads.  Randomly wondering off on a tangent, if clients had
nice caches of network information, it might be nice if servers would keep
eachother informed of their loads so if they were unnecessicairly busy
though could say "go away, here's a list of everyone else's loads so you
can pick a good one next time."

Of course this is all idle chit-chat until the decididly non-trivial
problem of out of sync servers is solved.

-- Brooks

-- 
"They that can give up essential liberty to purchase a little temporary
safety, deserve neither liberty nor safety." -- Benjamin Franklin.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Ben Rosengart]

On Fri, 21 Jan 2000, David O'Brien wrote:

 Possibly, being ping'able should be be a requirement to being a CVSup
 mirror.

I don't think it makes sense to try to dictate network policy to people
who are doing the FreeBSD Project a favor.  Anyway, an application-level
round-trip time measurement would probably be more accurate, because
some routers treat ICMP and TCP packets differently.

--
 Ben Rosengart

UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Warning: ioctl(... TUNSLMODE ...) to be depricated....

[Dag-Erling Smorgrav]

Brian Somers [EMAIL PROTECTED] writes:
 Unless there are objections in the next day or two, I'm going to 
 deprecate the TUNSLMODE ioctl favour of TUNSIFHEAD.  Where TUNSLMODE 
 prepended a sockaddr to each packet, TUNSIFHEAD will instead prepend a 
 4-byte network-byte-order address family.

Don't take it out quite yet. I asked Alfred to implement TUNSLMODE for
a reason; I was working on some VPN software at the time. There are
cases where you want a full sockaddr, not just the address family. The
next-hop address is not necessarily the same as the destination
address, if the interface is in broadcast mode (as opposed to ptp).

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Rodney W. Grimes]

 Hi David,
 
 John can implement a ping echo packet protocol for cvsup whose
 response can have "cool" information on the server. Steven's
 book on Networking already has the code for doing network latency
 calculations . It is more like if John has the time to implement
 such scheme 

You don't even need to modify the protocol.  Just write a small
tcp program that times the 3 way handshake on open to all the
servers, take the one with the sortest time and spit that out
for the user to stuff in his cvsupfile.

15 lines of perl should be more than enough :-)

-- 
Rod Grimes - KD7CAX @ CN85sl - (RWG25)   [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: when is FreeBSD-4.0 up for release ?

[Chuck Robey]

On Fri, 21 Jan 2000, Will Andrews wrote:

 On Fri, Jan 21, 2000 at 03:33:19PM -0800, David O'Brien wrote:
  What do you mean?  JKH said there would be a Feature Freeze on Jan 15 and
  it happened.  What more did JKH need to say on the topic?
 
 I lost some mail from early this week, but I didn't get anything from
 Jordan saying the FF was in effect. He said it would be in effect
 January 15th - not necessarily that it went into effect.
 
 Perhaps I'm just twisting words a little bit.

You really must not have been listening, Will.  Jordan did everything
*including* falling down laughing at about 3-4 different sets of folks who
misinterpreted feature freeze to mean code freeze.  I could understand,
somewhat, you making that mistake, but missing the fact of the feature
freeze itself?

I think it was David O'Brien, in fact, who posted it here in 2 inch high
letters!  No kidding.

You must have been hitting the delete key too fast, on several different
days.



Chuck Robey| Interests include C  Java programming, FreeBSD,
[EMAIL PROTECTED]  | electronics, communications, and signal processing.

New Year's Resolution:  I will not sphroxify gullible people into looking up
fictitious words in the dictionary.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Creative ViBRA16X Problem (fwd)

[Kenneth Wayne Culver]

I have the same soundcard, and as of right now, the only problem I have
with it is that sometimes it will play static instead of the sound I
wanted it to play.


=
| Kenneth Culver  | FreeBSD: The best OS around.|
| Unix Systems Administrator  | ICQ #: 24767726 |
| and student at The  | AIM: AgRSkaterq |
| The University of Maryland, | Website: (Under Construction)   |
| College Park.   | http://www.wam.umd.edu/~culverk/|
=

On Fri, 21 Jan 2000, Jeremy L. Stock wrote:

 Thought I'd post this to -current also since it gives a little more detail
 (I hope). I can't believe I'm the only one experiencing this since it's
 still around when I do a fresh install from a snapshot. Not a huge deal for
 me since I can use Windows for audio, but I'd rather use FreeBSD again. I'm
 sure this will get addressed before 4.0R. I just wanted to make sure it's a
 known issue.
 
 -- 
 Jeremy L. Stock   [EMAIL PROTECTED]
 ICQ 46329337
 Fax # 612-629-6540 
 -- Forwarded message --
 Date: Tue, 18 Jan 2000 22:14:44 -0600 (CST)
 From: Jeremy L. Stock [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Creative ViBRA16X Problem
 
 I posted this on -current almost a week ago and only received one response
 that didn't solve the problem. Audio hasn't played correctly for me since
 December 27th.  Now when I try to play audio, it just stutters.
 
 I'm not sure when it broke since I went from -current as of the 27th to
 -current as of the 11th and now earlier today. The problem still remains
 even after a total reinstall. 
 
 I just wanted to make sure you were aware of it and make sure you had a
 chance to correct it before 4.0R. Here's some info. Let me know if
 you need anything else.
 
 Copyright (c) 1992-2000 The FreeBSD Project.
 Copyright (c) 1982, 1986, 1989, 1991, 1993
   The Regents of the University of California. All rights reserved.
 FreeBSD 4.0-CURRENT #0: Tue Jan 18 20:00:28 CST 2000
 [EMAIL PROTECTED]:/usr/src/sys/compile/NIC
 Timecounter "i8254"  frequency 1193182 Hz
 Timecounter "TSC"  frequency 350796057 Hz
 CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU)
   Origin = "AuthenticAMD"  Id = 0x58c  Stepping = 12
   Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX
   AMD Features=0x8800SYSCALL,3DNow!
 real memory  = 134217728 (131072K bytes)
 avail memory = 127315968 (124332K bytes)
 Preloaded elf kernel "kernel" at 0xc02c2000.
 sbc0: Creative ViBRA16X at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 10 
 drq 0,1 on isa0
 sbc0: setting card to irq 10, drq 0, 1
 pcm0: SB DSP 4.16 (ViBRA16X) on sbc0
 unknown0: Game at port 0x201 on isa0
 
 And from boot -v (Let me know if I left an important section out)
 
 Trying Read_Port at 203
 CTL0043: start dependant
 CTL0043: adding irq mask 0x20
 CTL0043: adding dma mask 0x2
 CTL0043: adding dma mask 0x8
 CTL0043: adding io range 0x220-0x22f, size=0x10, align=0x1
 CTL0043: adding io range 0x330-0x331, size=0x2, align=0x1
 CTL0043: adding io range 0x388-0x38b, size=0x4, align=0x1
 CTL0043: start dependant
 CTL0043: adding irq mask 0x6a0
 CTL0043: adding dma mask 0xb
 CTL0043: adding dma mask 0xb
 CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20
 CTL0043: adding io range 0x300-0x331, size=0x2, align=0x30
 CTL0043: adding io range 0x388-0x38b, size=0x4, align=0x1
 CTL0043: start dependant
 CTL0043: adding irq mask 0x6a0
 CTL0043: adding dma mask 0xb
 CTL0043: adding dma mask 0xb
 CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20
 CTL0043: adding io range 0x300-0x331, size=0x2, align=0x30
 CTL0043: start dependant
 CTL0043: adding irq mask 0x6a0
 CTL0043: adding dma mask 0xb
 CTL0043: adding dma mask 0xb
 CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20
 CTL0043: start dependant
 CTL0043: adding irq mask 0x6a0
 CTL0043: adding dma mask 0xb
 CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20
 CTL0043: adding io range 0x300-0x331, size=0x2, align=0x10
 CTL0043: adding io range 0x388-0x397, size=0x4, align=0x4
 CTL0043: start dependant
 CTL0043: adding irq mask 0x6a0
 CTL0043: adding dma mask 0xb
 CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20
 CTL0043: end dependant
 CTL7005: start dependant
 CTL7005: adding io range 0x201-0x201, size=0x1, align=0x1
 CTL7005: start dependant
 CTL7005: adding io range 0x200-0x20f, size=0x1, align=0x1
 CTL7005: end dependant
 isa_probe_children: disabling PnP devices
 isa_probe_children: probing non-PnP devices
 sbc0: Creative ViBRA16X at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 10 drq 0,1 
on isa0
 sbc0: setting card to irq 10, drq 0, 1
 pcm0: SB DSP 4.16 (ViBRA16X) on sbc0
 pcm: setmap 2d000, 2000; 0xc7814000 - 2d000
 pcm: setmap 2f000, 2000; 0xc7816000 - 2f000
 unknown0: Game at port 0x201 on isa0
 
 pnpinfo output:
 
 Checking 

Re: when is FreeBSD-4.0 up for release ?

[David O'Brien]

On Fri, Jan 21, 2000 at 07:02:10PM -0500, Will Andrews wrote:
 On Fri, Jan 21, 2000 at 03:33:19PM -0800, David O'Brien wrote:
  What do you mean?  JKH said there would be a Feature Freeze on Jan 15 and
  it happened.  What more did JKH need to say on the topic?
 
 I lost some mail from early this week, but I didn't get anything from
 Jordan saying the FF was in effect. He said it would be in effect
 January 15th - not necessarily that it went into effect.

So every little date event needs a confirmation??   Why isn't the fact
that JKH didn't resend the event not mean that it is in effect?

Ok, for everyone that isn't sure that today is Friday after looking at you
calander last night which announced Jan 21st is Friday:


  ###
# #   ### 
#   #  # #
#   # #   
#   # #
#   ###
#   # 



###
##  ## ## #   #
### ###   #  # # #
### ###  ## #
##  ###  ## #
##   #  ###  ## #
### ##   ## #

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[David O'Brien]

On Fri, Jan 21, 2000 at 07:03:51PM -0500, Chuck Robey wrote:
 I don't know ... I think it might be a good idea for the cvsup client to
 make a connection to a cvsup master, get redirected from that master to
 the actual handler of the connection, and then work.  That way, a config
 file on the master could be set up to know the capabilities of the other
 machines (network availability, machine speed, etc) and dole out
 connections weighted on that.

How is a cvsup master to know anything about the path from me to any
given cvsup mirror?  Knowing something about the path from me to the
master and the path from the master to the mirror tells zero about the
path from me to the mirror.

Being on an .EDU network, I have a *very* different path to other .EDU
machine participating in Inetnet2.  My path to cvsup3 is a prime example.
This "cvsup master" will have no idea about this.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Rodney W. Grimes]

   Hi David,
   
   John can implement a ping echo packet protocol for cvsup whose
   response can have "cool" information on the server. Steven's
   book on Networking already has the code for doing network latency
   calculations . It is more like if John has the time to implement
   such scheme 
  
  You don't even need to modify the protocol.  Just write a small
  tcp program that times the 3 way handshake on open to all the
  servers, take the one with the sortest time and spit that out
  for the user to stuff in his cvsupfile.
  
  15 lines of perl should be more than enough :-)
  
 Hi,
 
 Thats gross server load balancing . The network travel time
 does not tell you how how loaded the machine is or the server.

It may be gross to the server but it is optimal to the networks :-)

 
 There are  couple of RFCs on network load balancing with 
 respect to servers or services and I am sure that there
 are also widely available research papers. 

Most of those concentrate on balancing the load on the server
itself.  How about balancing the load on the network paths,
I doubt very much that we have a server load problem near as
much as we have a network load problem due to people not
having ready access to the data that says ``this server is
closest network wise to me''.


-- 
Rod Grimes - KD7CAX @ CN85sl - (RWG25)   [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[David O'Brien]

On Fri, Jan 21, 2000 at 07:27:08PM -0500, Will Andrews wrote:
 Traceroute works fine.

Traceroute can be annoying to use as it is much slower.  And not all
routers respond "properly" to it.


 If you knew the history of fadeto.blackened.com, you'd know why ICMPs
 are filtered out

I really don't give a rats a** about fadeto.blackened.com.  I am part of
FreeBSD and that is what I care about.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Chuck Robey]

On Fri, 21 Jan 2000, David O'Brien wrote:

 On Fri, Jan 21, 2000 at 07:03:51PM -0500, Chuck Robey wrote:
  I don't know ... I think it might be a good idea for the cvsup client to
  make a connection to a cvsup master, get redirected from that master to
  the actual handler of the connection, and then work.  That way, a config
  file on the master could be set up to know the capabilities of the other
  machines (network availability, machine speed, etc) and dole out
  connections weighted on that.
 
 How is a cvsup master to know anything about the path from me to any
 given cvsup mirror?  Knowing something about the path from me to the
 master and the path from the master to the mirror tells zero about the
 path from me to the mirror.
 
 Being on an .EDU network, I have a *very* different path to other .EDU
 machine participating in Inetnet2.  My path to cvsup3 is a prime example.
 This "cvsup master" will have no idea about this.

I guess it means, is the main component trying to be balanced the server
resources or the network resources.  I may be wrong, but I think that the
server resources are more likely to be the most important bottleneck, and
this method detects that, with minimal network effects.

If you think that it's really the network that's going to be the
bottleneck, then you wouldn't want to use this method.  I don't think I'm
wrong, but I'm willing to listen to arguments on it.

 
 


Chuck Robey| Interests include C  Java programming, FreeBSD,
[EMAIL PROTECTED]  | electronics, communications, and signal processing.

New Year's Resolution:  I will not sphroxify gullible people into looking up
fictitious words in the dictionary.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Rodney W. Grimes]

 On Fri, 21 Jan 2000, David O'Brien wrote:
 
  On Fri, Jan 21, 2000 at 07:03:51PM -0500, Chuck Robey wrote:
   I don't know ... I think it might be a good idea for the cvsup client to
   make a connection to a cvsup master, get redirected from that master to
   the actual handler of the connection, and then work.  That way, a config
   file on the master could be set up to know the capabilities of the other
   machines (network availability, machine speed, etc) and dole out
   connections weighted on that.
  
  How is a cvsup master to know anything about the path from me to any
  given cvsup mirror?  Knowing something about the path from me to the
  master and the path from the master to the mirror tells zero about the
  path from me to the mirror.
  
  Being on an .EDU network, I have a *very* different path to other .EDU
  machine participating in Inetnet2.  My path to cvsup3 is a prime example.
  This "cvsup master" will have no idea about this.
 
 I guess it means, is the main component trying to be balanced the server
 resources or the network resources.  I may be wrong, but I think that the
 server resources are more likely to be the most important bottleneck, and
 this method detects that, with minimal network effects.
 
 If you think that it's really the network that's going to be the
 bottleneck, then you wouldn't want to use this method.  I don't think I'm
 wrong, but I'm willing to listen to arguments on it.

I think, and am pretty sure as hostmaster for cvsup4, that the bottleneck
is a combination of both.  We use the max connection limit to control
the load on the server, and simply refuse connections beyond the acceptable
load limit.  As far as I know none of the servers run unlimited connection
counts so we already have a load controlling mechanism.

I know from a network bandwidth point of view I can tell when someone
with T-1 or better comes on and pulls a full copy from us, it shows up
quite nicely in the load graphs.

I also know from looking at our logs that some people would get faster
cvsup's if they changed which mirror they are pulling from.  (Anyone
directly attached to Verio should no longer be using us, but the new
Verio provided server instead.)

-- 
Rod Grimes - KD7CAX @ CN85sl - (RWG25)   [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Wes Peters]

Amancio Hasty wrote:
 
   My only point is that the first response to a problem isn't to necessarily
   pull out emacs and start hacking away on code.
 
  Yea, it is easier to do in a regular zone file then to implement the
  network measurement logic into cvsup.
 
 Yes, it is a rather cool idea to rotate on the cvs servers without
 respect to latency, work load  or rate of service response from
 the server.

Thank you.  I was beginning to wonder if I am the only one here who thinks
blind round-robin DNS is a bad hack.

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[David O'Brien]

On Fri, Jan 21, 2000 at 08:56:29PM -0500, Chuck Robey wrote:
 I guess it means, is the main component trying to be balanced the server
 resources or the network resources.  I may be wrong, but I think that the
 server resources are more likely to be the most important bottleneck, and

Not really.  If I have a poor network connection to the CVSup mirror
used, then I'll spend much long connected to it.  Thus causing a higher
"load" on the mirror.  Where "load" is either one of the connection
slots, or actual kernel resource load if I have 20% packet loss and thus
cause a lot of retransmissions to occur.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: problems with mylex raid scsi

[Mike Smith]

 I try to install FreeBSD 4.0-CURRENT snapshot on 
 server with have mylex accele raid 250 controler. 
 FreeBSD installs on it without any problems, but 
 can't boot from it. I try 2 and 8 GB BIOS mode, 
 also FreeBSD and BIOS geometry (trick with small 
 dos partition). Depending of situation boot 
 loader shows Invalid slice, registers (int 0d, 
 err 00, eip a658, cs f000) and System halted info 
 or boot manager can't find loader (it bells when 
 I select F1 - FreeBSD).

It'd help if you could sort out this pile of details and list the actual 
combinations that you tried; at the moment I can't even begin to guess at 
the cause of your problem(s).

More or less in summary:

Invalid slice- you have the geometry mixed up
Bootmanager beep - you have the geometry mixed up differently
Register dump- looks like a BIOS bug, but hard to tell without eax
System halted- should have register dump, see above

If you can offer some more details, I can work on trying to reproduce the 
problem.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: cvsup 3.4-release to -current

[Scott Burns]

"Matt M." wrote:

 Just wondering what potential problems I am facing by going from
 3.4-release to -current. I was told on irc that my chances may not be
 well.

 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message

I tried upgrading to 4.0-CURRENT from 3.4-RELEASE, and the buildworld
worked fine, but the installworld was interrupted part of the way
through the install by a signal 12 to sh.  I tried doing it from
3.4-RELEASE a few times, as well as from 3.4-STABLE on the same box, and
I got the same error every time.  I ended up booting to the 3.4 install
disk and reinstalling 3.4 with sysinstall to fix it, because sh and csh
would crash with a signal 12 every time.

I got the following error each time:

=== bin/sync
install -c -s -o root -g wheel -m 555   sync /bin
install -c -o root -g wheel -m 444 sync.8.gz  /usr/share/man/man8
=== bin/test
install -c -s -o root -g wheel -m 555   test /bin
*** Signal 12

Stop.
*** Error code 12

---
Scott Burns
[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: even more breakage in current

[Bruce Evans]

On Fri, 21 Jan 2000, Jason Evans wrote:

 On Fri, Jan 21, 2000 at 10:11:57AM -0800, Bill Swingle wrote:
...
  cc -DPROF -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include 
-D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale 
-DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -I/usr/src/lib/libc/i386 -c 
/usr/src/lib/libc/../libc/i386/gen/_setjmp.S -o _setjmp.po
  /tmp/ccg65684.s: Assembler messages:
  /tmp/cco65681.s: Assembler messages:
  /tmp/cco65681.s:361: Error: invalid character '(' in opcode
  /tmp/ccg65684.s:361: Error: invalid character '(' in opcode

This happens when libc/i386/DEFS.h and libc/i386/gen/setjmp.S are current
(as of Jan 21) but machine/asm.h is out of date.

 I moved some definitions from src/lib/libc/i386/DEFS.h to
 src/sys/i386/include/asm.h.  If the build system is looking at the
 installed version of asm.h rather than the version in the source tree, this
 error will occur.  I did a 'make includes' during my testing, so I didn't
 have this problem.
 
 It's my understanding that the build system is supposed to be sophisticated
 enough to avoid such bootstrapping issues, but I don't understand it all
 that well.  Can someone explain whether this is a bug in the build system,
 or if I should be doing something different?

Everything should just work in this case, provided machine/asm.h is up
to date.  All you could do better is commit machine/asm.h first so that
there is no window of inconsistency.

 In any case, doing a 'make includes' will get you past this.

Don't use `make includes' unless you are familiar enough with the build
system not to need it.  It _causes_ problems like this by defeating the
build system (it gives a set of includes that tends not to match the
libraries).  It happens to fix the problem in this case (at least if you
install only machine/asm.h).

Test header changes using `NOCLEAN=1 make buildworld'.  NOCLEAN is now
fairly robust.

Bruce



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Please help spread the CVSup mirror load more evenly

[Warner Losh]

In message [EMAIL PROTECTED] "David O'Brien" writes:
: "load" on the mirror.  Where "load" is either one of the connection
: slots, or actual kernel resource load if I have 20% packet loss and thus
: cause a lot of retransmissions to occur.

Hmmm.  A thought just occurred to me.  There's no need to measure
these things.  Lookup all the IP addresses.  Do a non blocking
connection to each of these machines.  First one to come back with the
REL16_1 response wins, and all the others get closed and you use that
one.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: even more breakage in current

[Bruce Evans]

On Fri, 21 Jan 2000, Jason Evans wrote:

 I often do a 'make includes' to be able to iteratively test changes.  Once
 I'm happy that the changes are sound, there is no way to assure that the
 changes didn't cause a bootstrapping problem like this one.

`make includes' breaks your test environment.  The problem is harder for
developers.  Developers have to install new headers to test them (except
for system header in the SHARED=symlinks case, which is very convenient
for development but is almost equivalent to an automatic `make includes'
since most header changes are in system headers).  I don't see any better
ways to test header changes before committing them than to keep a
separate tree which is almost current, apply the changes to that tree,
and do a `NOCLEAN=1 make buildworld' on it.  I rarely do this :-).

 This is the second time that this has been a problem for me.  The first
 time I caught it and put a hack in the libc_r Makefile:
 
 CFLAGS+=-I${.CURDIR}/../../include
 
 Marcel said that this is not appropriate for reasons I didn't understand.
 If this isn't appropriate, and the build system is structured such that it
 pulls definitions from the installed headers, then what *is* the correct
 solution?

The build system installs the necessary headers at the necessary times.
The above gets in its way by doing the equivalent of installing headers
before they are ready to be used.  I think it currently doesn't actually
cause in problems in libc_r/Makefile, because libc_r doesn't have any
tools that need to be built with the old includes.

Bruce



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Here's what I'm using

[Warner Losh]

OK.  I said I'd clean this up and send this out.  Well,  I didn't get
as much ceanup done as I'd have liked.  The order of hosts is
arbitrary and works for me.  I'm sure this could be improved,
especially to make the order random.

Warner

#!/bin/sh

if [ -z "$1" ]; then
hosts=" \
cvsup7.freebsd.org \
cvsup8.freebsd.org \
cvsup6.freebsd.org \
cvsup4.freebsd.org \
cvsup3.freebsd.org \
cvsup2.freebsd.org \
cvsup1.freebsd.org \
cvsup5.freebsd.org \
"
else
hosts=$1
shift
fi
echo "Will try hosts $hosts"
for host in $hosts; do
echo "Using host $host"
for i in 1 2; do
if cvsup -1 -P m -s -g ~/bin/sup/fbsd-supfile -L 2 -h $host $*; then
exit;
fi
done
done


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: rtld-elf, java + tya

[Max Khon]

hi, there!

On Fri, 21 Jan 2000, John Polstra wrote:

 Really?!  Augh.  Naturally this comes just hours after I have merged
 the latest changes into -stable *sigh*.
 
 Could you please make sure your src/libexec/rtld-elf is
 up-to-date?  rtld.c should be at revision 1.41.

yes. my src/libexec/rtld-elf/rtld.c is 1.41
 
 Then if you can give me a stack backtrace it would help a lot.

I'll try to get backtrace on Monday (when I'll get to the office)

/fjoe



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: indirection in bus space

[KATO Takenori]

Do you remember this topic?  I have revised the indirection support
patch.  What I have changed are:
  - to make diff files more readable
  - introduce the bus_simple_create_bsh() that creates
a bus_space_handle_tag from a base address.

I have made PC98 GENERIC98 kernel and i386 LINT kernel and both of
them can be compiled.

Changed and new files are as follows:
  alpha/include/bus.h
  i386/include/bus.h
  i386/include/bus_at386.h (new file)
  i386/include/bus_pc98.h (new file)
  i386/i386/nexus.c
  i386/isa/isa.c
  dev/advansys/adv_isa.c
  dev/advansys/adv_pci.c
  pci/amd.c
  pci/isp_pci.c

I put new files and diffs as follows:
  http://www.FreeBSD.ORG/~kato/busspace/index.html
 INDEX

  http://www.FreeBSD.ORG/~kato/busspace/alpha_bus.h.diff
 diff between old bus.h and new bus.h

  http://www.FreeBSD.ORG/~kato/busspace/i386_bus.h
 i386/include/bus.h

  http://www.FreeBSD.ORG/~kato/busspace/bus_at386.h
 i386/include/bus_at386.h

  http://www.FreeBSD.ORG/~kato/busspace/bus_at386.h.diff
 diff between old bus.h and bus_at386.h

  http://www.FreeBSD.ORG/~kato/busspace/bus_pc98.h
 i386/include/bus_pc98.h

  http://www.FreeBSD.ORG/~kato/busspace/bus_pc98.h.diff
 diff between old bus.h and bus_pc98.h

  http://www.FreeBSD.ORG/~kato/busspace/isa.c.diff
 diff of i386/isa/isa.c

  http://www.FreeBSD.ORG/~kato/busspace/nexus.c.diff
 diff of i386/i386/nexus.c

  http://www.FreeBSD.ORG/~kato/busspace/adv_isa.c.diff
 diff of dev/advansys/adv_isa.c

  http://www.FreeBSD.ORG/~kato/busspace/adv_pci.c.diff
 diff of dev/advansys/adv_pci.c

  http://www.FreeBSD.ORG/~kato/busspace/amd.c.diff
 diff of pci/amd.c

  http://www.FreeBSD.ORG/~kato/busspace/isp_pci.c.diff
 diff of pci/isp_pci.c

Thank you.

---+--+
KATO Takenori [EMAIL PROTECTED]  |FreeBSD   |
Dept. Earth Planet. Sci, Nagoya Univ.  |The power to serve!   |
Nagoya, 464-8602, Japan|  http://www.FreeBSD.org/ |
   |http://www.jp.FreeBSD.org/|
 FreeBSD(98) 3.3R-Rev. 01 available!   +==+


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message