Re: ISO image available?

2001-04-13 Thread Jordan Hubbard

They're not in ISO format, but releases from both -stable and -current
are available from releng4.freebsd.org and current.freebsd.org (hmm,
there should also be a stable.freebsd.org - I'll request that).
From those bits, it's pretty easy to make an image with mkisofs/mkhybrid

- Jordan

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



Re: ISO image available?

2001-04-13 Thread Jordan Hubbard

 There used to be a similar snapshot server for -stable, but it seems to
 have disappeared.

Hurm?  releng4.freebsd.org has been around for ages.  Before that it
was called releng3.freebsd.org, hence the name change.

- Jordan

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



Re: SOMAXCONN -- not tunable?

2001-04-13 Thread Alfred Perlstein

* Bruce Evans [EMAIL PROTECTED] [010412 22:25] wrote:
 On Thu, 12 Apr 2001, Jonathan Lemon wrote:
 
  In article local.mail.freebsd-current/[EMAIL PROTECTED] 
you write:
  Here are patches to make SOMAXCONN tunable from the config files.
  
  Right now, it's not possible to override SOMAXCONN.
  
  sysctl -w kern.ipc.somxconn=1024
  
  SOMAXCONN is just a compile time default, and yes it is not 
  currently tunable at config time.  Does it really have to be?
 
 Of course it doesn't have to be tunable at config time.
 
  Just stick it in /etc/sysctl.conf, and it gets set before most
  things are started in the system.
 
 Changing the actual limit using either the sysctl or an option breaks
 SOMAXCONN.  I think the correct fix is to never define it change
 whatever uses it to use sysconf(_SC_SOMAXCONN).  Similarly for all
 other manifest constants that aren't actually constant.

Actually, the correct fix is most likely to redefine it to -1. :)

Either that or remove it from the namespace.  Or just leave it alone,
afaik listen called with a backlog larger than the sysctl limit
just truncates it down to that limit.

What do you think?

/usr/src % grep -r SOMAXCON * 
contrib/perl5/ext/Socket/Socket.pm: SOMAXCONN
contrib/perl5/ext/Socket/Socket.pm:sub SOMAXCONN();
contrib/perl5/ext/Socket/Socket.xs: if (strEQ(name, "SOMAXCONN"))
contrib/perl5/ext/Socket/Socket.xs:#ifdef SOMAXCONN
contrib/perl5/ext/Socket/Socket.xs: return SOMAXCONN;
contrib/perl5/lib/Exporter.pm:use Socket qw(!/^[AP]F_/ !SOMAXCONN !SOL_SOCKE
T);
contrib/perl5/pod/perlipc.pod:listen(Server,SOMAXCONN)  
|| die "listen: $!";
contrib/perl5/pod/perlipc.pod:listen(Server,SOMAXCONN)  
|| die "listen: $!";
contrib/perl5/pod/perlipc.pod:listen(Server,SOMAXCONN)  
|| die "listen: $!";
contrib/perl5/pod/perlipc.pod:is SOMAXCONN.
contrib/perl5/pod/perlipc.pod:  Listen= SOM
AXCONN,
contrib/perl5/t/lib/ph.t:SOCK_RAW SOCK_RDM SOCK_SEQPACKET SOCK_STREAM SOL_SO
CKET SOMAXCONN
contrib/sendmail/libmilter/libmilter.h:#if SOMAXCONN  20
contrib/sendmail/libmilter/libmilter.h:# define MI_SOMAXCONNSOMAXCONN
contrib/sendmail/libmilter/libmilter.h:#else /* SOMAXCONN */
contrib/sendmail/libmilter/libmilter.h:# define MI_SOMAXCONN20
contrib/sendmail/libmilter/libmilter.h:#endif /* SOMAXCONN */
contrib/sendmail/libmilter/main.c:static int backlog= MI_SOMAXCONN;
crypto/heimdal/kadmin/kadm_conn.c:  if (listen (s, SOMAXCONN)  0) {
crypto/heimdal/kdc/connect.c:if(type == SOCK_STREAM  listen(d-s, SOMAXCON
N)  0){
crypto/heimdal/lib/kadm5/ipropd_master.c:if (listen(fd, SOMAXCONN)  0)
crypto/heimdal/lib/roken/mini_inetd.c:  if (listen (fds[i], SOMAXCONN)  0)
crypto/heimdal/lib/roken/roken-common.h:#ifndef SOMAXCONN
crypto/heimdal/lib/roken/roken-common.h:#define SOMAXCONN 5
crypto/kerberosIV/ChangeLog:* appl/kx/kx.h: Remove SOMAXCONN and add KX_PORT
crypto/kerberosIV/ChangeLog:fallback definitions for SOMAXCONN, STDIN_FILENO
, and
crypto/kerberosIV/appl/kx/common.c:   listen (s[i].fd, SOMAXCONN)  0)
crypto/kerberosIV/appl/kx/kxd.c:if (listen (sock, SOMAXCONN)  0) {
crypto/kerberosIV/kadmin/admin_server.c:if (listen(admin_fd, SOMAXCONN)  0)
crypto/kerberosIV/lib/roken/mini_inetd.c: if(listen(s, SOMAXCONN)  0){
crypto/kerberosIV/lib/roken/mini_inetd.c: if(listen(s, SOMAXCONN)  0){
crypto/kerberosIV/lib/roken/roken-common.h:#ifndef SOMAXCONN
crypto/kerberosIV/lib/roken/roken-common.h:#define SOMAXCONN 5
crypto/kerberosIV/server/kerberos.c:listen(sock, SOMAXCONN);
crypto/kerberosIV/slave/kpropd.c:ret = listen(s, SOMAXCONN);
crypto/openssl/crypto/bio/b_sock.c:#define MAX_LISTEN  SOMAXCONN
lib/libc/net/getaddrinfo.3: if (listen(s[nsock], SOMAXCONN)  0) {
lib/libc/rpc/rpc_soc.c: _listen(fd, SOMAXCONN);
lib/libc/rpc/svc_generic.c: _listen(fd, SOMAXCONN);
sbin/mountd/mountd.c:   listen(tcpsock, SOMAXCONN);
sbin/mountd/mountd.c:   listen(tcp6sock, SOMAXCONN);
sys/conf/options:SOMAXCONN  opt_inet.h
sys/kern/uipc_socket.c:static int somaxconn = SOMAXCONN;
sys/kern/uipc_socket.c:SYSCTL_INT(_kern_ipc, KIPC_SOMAXCONN, somaxconn, CTLFLAG_
RW,
sys/sys/socket.h:#ifndefSOMAXCONN
sys/sys/socket.h:#defineSOMAXCONN   128
sys/sys/sysctl.h:#defineKIPC_SOMAXCONN  3   /* int: max leng
th of connection q */
usr.sbin/rpcbind/rpcbind.c: listen(fd, SOMAXCONN);

-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
http://www.egr.unlv.edu/~slumos/on-netbsd.html

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



Re: SOMAXCONN -- not tunable?

2001-04-13 Thread Garrett Wollman

On Fri, 13 Apr 2001 04:01:25 -0700, Alfred Perlstein [EMAIL PROTECTED] said:

 Actually, the correct fix is most likely to redefine it to -1. :)

POSIX.1-200x draft 5 has this to say:

Implementations shall support values of backlog up to
SOMAXCONN, defined in sys/socket.h

If listen( ) is called with a backlog argument value that is
less than 0, the function behaves as if it had been called
with a backlog argument value of 0.  A backlog argument of 0
may allow the socket to accept connections, in which case the
length of the listen queue may be set to an
implementation-defined minimum value.

So, SOMAXCONN is supposed to be a minimum maximum.

-GAWollman


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



miibus/fxp intel etherexpress broken

2001-04-13 Thread Darren Henderson


I had a functional install of -current which was created back on Jan 11th of
this year. 

I cvsup'd yesterday (4/12. I had also tried this on 4/4) fixxed what I
needed too from UPDATING and RELNOTES, built and installed world and a new
kernel.

fxp now fails.

Searching back I saw that fxp now requires miibus and that is in there but I
don't see anything else that has changed. Is there something else I need to
tweak to get this to work again?

Kernel config and dmesg output below...


MOXIE config
-
#

machine i386
cpu I586_CPU
ident   MOXIE
maxusers32

#makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols

options INET#InterNETworking
options FFS #Berkeley Fast Filesystem
options SOFTUPDATES #Enable FFS soft updates support
options MFS #Memory Filesystem
options MD_ROOT #MD is a potential root device
options NFS #Network Filesystem
options NFS_ROOT#NFS usable as root device, NFS required
options MSDOSFS #MSDOS Filesystem
options CD9660  #ISO 9660 Filesystem
options PROCFS  #Process filesystem
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=15000#Delay (in ms) before probing SCSI
options UCONSOLE#Allow users to grab the console
options USERCONFIG  #boot -c editor
options VISUAL_USERCONFIG   #visual boot -c editor
options KTRACE  #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options P1003_1B#Posix P1003_1B real-time extensions
options _KPOSIX_PRIORITY_SCHEDULING
options KBD_INSTALL_CDEV# install a CDEV entry in /dev

options DIAGNOSTIC

# firewall
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=100

device  random

device  isa
device  eisa
device  pci

# Floppy drives
device  fdc

# ATA and ATAPI devices
device  ata
device  atadisk # ATA disk drives
device  atapicd # ATAPI CDROM drives
options ATA_STATIC_ID

# SCSI Controllers

device  adv

# SCSI peripherals
device  scbus   # SCSI bus (required)
device  da  # Direct Access (disks)

# atkbdc0 controls both the keyboard and the PS/2 mouse
device  atkbdc
device  atkbd
device  psm

device  vga

# splash screen/screen saver
device  splash

# syscons is the default console driver, resembling an SCO console
device  sc

# Floating point support - do not disable.
device  npx

# Serial (COM) ports
device  sio

# Parallel port
device  ppc
device  ppbus   # Parallel port bus (required)
device  lpt # Printer


# PCI Ethernet NICs.
device  miibus
device  fxp # Intel EtherExpress PRO/100B (82557, 82558)

device  ep

# Pseudo devices - the number indicates how many units to allocated.
device  loop# Network loopback
device  ether   # Ethernet support
device  tun # Packet tunnel.
device  pty # Pseudo-ttys (telnet etc)
device  md  # Memory "disks"

# The `bpf' pseudo-device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
device  bpf #Berkeley packet filter



dmesg
-
Rebooting...
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #0: Fri Apr 13 09:33:04 EDT 2001
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MOXIE
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 166194014 Hz
CPU: Pentium/P55C (166.19-MHz 586-class CPU)
  Origin = "GenuineIntel"  Id = 0x544  Stepping = 4
  Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX
real memory  = 67108864 (65536K bytes)
avail memory = 61964288 (60512K bytes)
Preloaded elf kernel "kernel" at 0xc034b000.
Intel Pentium detected, installing workaround for F00F bug
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Host to PCI bridge at pcibus 0 on motherboard
pci0: PCI bus on pcib0
isab0: PCI-ISA bridge at device 1.0 on pci0
isa0: ISA bus on isab0

Re: readline.h 1.12 incompatible with gdb.291/gdb/top.c 1.2, I think

2001-04-13 Thread David O'Brien

On Fri, Apr 13, 2001 at 06:40:42PM +0400, Andrey A. Chernov wrote:
 Yes. Backward-compatible prototypes was enabled very recently
 to help old applications. I didn't expect it break gdb compilation again

I need to update my box to test.  It will probably be  2-3 hours and it
will be fixed.

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