Re: Detecting PnP devices upon module load

2000-02-12 Thread Doug Rabson

On Fri, 11 Feb 2000, Steve Hocking wrote:

 
 Are there any existing examples of this happening? I'm doing a version of the 
 Linux joystick driver ported to FreeBSD and of course some of the devices are 
 PnP.

You need to dike out the unknown driver (near the end of
sys/isa/isa_common.c). I'll fix this properly after 4.0 if Matt Dodd
doesn't beat me to it.

--
Doug Rabson Mail:  [EMAIL PROTECTED]
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




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



Re: hard lock under 3.4-STABLE

2000-02-12 Thread David Malone

On Fri, Feb 11, 2000 at 06:03:16PM -0800, Matthew Dillon wrote:

 I presume its the client that is locking up?   If you remove the
 server binary and the client takes a page fault on the binary,
 and does not have the page in the cache, what is supposed to happen
 is that the program is supposed to seg fault when the NFS read fails.
 It's quite possible that there is a bug in dealing with this situation
 and if you can get it repeatable we can probably fix it fairly easily.

I did some experiments with this sort of thing a few months ago.
I think you can kill 3.X NFS client machines by truncating a binary
on the NFS server. You can also make the machine extreamly slugish
by catching SIGBUS and SIGSEGV in an executable and then causing
one of these signals once the binary is modified. We see it quite
frequently with people using MPI.

I'll see if I can reproduce any of these effects and let you know
how to do it.

David.


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



Diskless Workstation with Etherboot

2000-02-12 Thread Dan Diephouse

I have been trying to turn a 486 that I have into a diskless workstation
and have not gotten very far.  I have compiled Etherboot, and set up the
server with tftp and bootp.  I have both daemons enabled.  When I boot
up the 486 machine tcpdump yields this:

[root:dragon]# tcpdump -i de0 -e
tcpdump: listening on de0
11:34:14.767283 0:0:b2:0:0:be Broadcast ip 342: 0.0.0.0.0 
255.255.255.255.bootps: (request) xid:0x52850a00 secs:9 [|bootp]
11:34:24.653629 0:0:b2:0:0:be Broadcast ip 342: 0.0.0.0.0 
255.255.255.255.bootps: (request) xid:0x52850a00 secs:18 [|bootp]
.
.
.
and so on.

Bootp then complains, "bootpd[350]: sendto: Can't assign requested
address"

As you can see, I'm not getting very far.  Below are my configuration
files, please EMail back if you need other ones.

Thank You,

Dan Diephouse

bootptab:

.default:\
:hn:\

:sm=255.255.255.0:\
:ds=199.182.120.203:\
:gw=192.168.2.1:\
:hd=/usr/data/exports/tftpboot:\
:bf=null:\
:vm=rfc1048:\
:to=auto:\
:ra=255.255.255.255:

nebula:\
:tc=.default:\
:ha=b2be:\
#:ha=02026767
:bf=kernel:\
:ip=192.168.2.3:

The DISKLESS machine:

machine "i386"
cpu "I386_CPU"
cpu "I486_CPU"
ident   DISKLESS
maxusers32

options MATH_EMULATE#Support for x87 emulation
options INET#InterNETworking
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep
this!]options MFS #Memory Filesystem
options MFS_ROOT#MFS usable as root device,
"MFS" req'ed
options NFS #Network Filesystem
options NFS_ROOT#NFS usable as root device,
"NFS" req'ed
options MSDOSFS #MSDOS Filesystem
options "CD9660"#ISO 9660 Filesystem
options "CD9660_ROOT"   #CD-ROM usable as root. "CD9660"
req'edoptions PROCFS  #Process filesystem
options "COMPAT_43" #Compatible with BSD 4.3 [KEEP
THIS!]
options SCSI_DELAY=15000#Be pessimistic about Joe SCSI
device
options UCONSOLE#Allow users to grab the console

options FAILSAFE#Be conservative
options USERCONFIG  #boot -c editor
options VISUAL_USERCONFIG   #visual boot -c editor
options KTRACE  #ktrace(1) syscall trace support

options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores

options BOOTP   # Use BOOTP to obtain IP
address/hostname
options BOOTP_NFSROOT   # NFS mount root filesystem using BOOTP
info
#options BOOTP_NFSV3 # Use NFS v3 to NFS mount root
options BOOTP_COMPAT# Workaround for broken bootp daemons.


config  kernel  root on wd0

controller  isa0
controller  pnp0# PnP support for ISA
controller  eisa0
controller  pci0

# Floppy drives
controller  fdc0at isa? port "IO_FD1" bio irq 6 drq 2
diskfd0 at fdc0 drive 0
diskfd1 at fdc0 drive 1

# IDE controller and disks
options "CMD640"# work around CMD640 chip deficiency
controller  wdc0at isa? port "IO_WD1" bio irq 14
diskwd0 at wdc0 drive 0
diskwd1 at wdc0 drive 1

controller  wdc1at isa? port "IO_WD2" bio irq 15
diskwd2 at wdc1 drive 0
diskwd3 at wdc1 drive 1

# ATAPI devices
options ATAPI   #Enable ATAPI support for IDE bus
options ATAPI_STATIC#Don't do it as an LKM
device  acd0#IDE CD-ROM
device  wfd0#IDE Floppy (e.g. LS-120)

# atkbdc0 controls both the keyboard and the PS/2 mouse
controller  atkbdc0 at isa? port IO_KBD tty
device  atkbd0  at isa? tty irq 1
device  psm0at isa? tty irq 12

device  vga0at isa? port ? conflicts

# splash screen/screen saver
pseudo-device   splash

# syscons is the default console driver, resembling an SCO console
device  sc0 at isa? tty

# Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver
#device vt0 at isa? tty
#optionsXSERVER # support for X server
#optionsFAT_CURSOR  # start with block cursor
# If you have a ThinkPAD, uncomment this along with the rest of the PCVT
lines
#optionsPCVT_SCANSET=2  # IBM keyboards are non-std

# Floating point support - do not disable.
device  npx0at isa? port IO_NPX irq 13

# Serial (COM) ports
device  sio0at isa? port "IO_COM1" flags 0x10 tty 

bad floppies lock ttys

2000-02-12 Thread Victor Ivanov

  I don't think this is the very right place to put this message, but I
don't really want to subscribe to high-traffic mailing lists and maybe
this is a device problem...
  The device is /dev/fd0 (standart 1,44 IDE floppy, controller fdc). When
accessing bad floppy disks the kernel complains for a while and then all
virtual consoles lock... ttyv*, ttyp* (used by telnet) and don't know
about serials. Total lock, when you type it doesn't appear. Everyhing else
seem to work fine (networking, routing, services...); the debuger
(ddb) too, but I don't know what to do with it :). The solution is the F0
key (Ctrl+Alt+RESET).
  
  ...



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



Re: My views on Eclipse/BSD

2000-02-12 Thread Daniel C. Sobral

Peter Wemm wrote:
 
 One key thing to keep in mind is that copyrights apply automatically
 regardless of age, contracts etc.  You have no right to copy a copyrighted
 work unless the right to do so is given to you (or you have statutory
 rights such as making backups etc).  In this case, you don't have the right
 to redistribute it except those granted by the license with it's
 conditions.  If you don't accept the license or cannot because you're under
 the age of being able to enter into a contract or whatever, then you can't
 redistribute it *period*.  You can download it (they are distributing it,
 not you), and do pretty much whatever you like with it once they've given
 it to you, but you can't give it to anyone else.  This means that if you
 were under 18 etc, you probably could use it for commercial purposes if you
 believed the license didn't apply.  (And Lucent/whoever *do* own the
 copyright on the additional Eclipse stuff).

So... basically... you can't redistribute GPL code unless law permits
you to enter contracts? How funny... :-)

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"If you consider our help impolite, you should see the manager."


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



Re: Diskless Workstation with Etherboot

2000-02-12 Thread Dan Diephouse

This is a leftover from me trying a different Ethernet card.  It does not
work without that lineI still get the same symptoms.

Thanks,

Dan Diephouse

Parag Patel wrote:

 On Sat, 12 Feb 2000 11:40:29 EST, Dan Diephouse wrote:

 nebula:\
 :tc=.default:\
 :ha=b2be:\
 #:ha=02026767
  ^ ^^^
 :bf=kernel:\
 :ip=192.168.2.3:

 I hope this isn't what's in your file.  bootpd won't parse past the
 comment and see the subsequent two lines.  All lines must be connected
 with a backslash-newline without any intervening comments.

 Hope this helps.

 -- Parag Patel



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



accounting, ppp

2000-02-12 Thread Egervary Gergely

hello,

[moving from -questions, as no answers received]

I'm running a PPP dialup server. (mgetty-autoppp) Is there any way to do
login accounting (like solaris' PAM modules, or linux pam_limits.so)

Basically, I have to limit simultaneous connections, and monthly login
times.

-- mauzi



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



Kernel messages, msgbuf and syslog

2000-02-12 Thread Andrzej Bialecki

Hi,

I was wondering if there is any way currently to emit a message from
within kernel, so that syslogd can pick it up later on, but without
spoiling the standard message buffer. AFAIK, there is no way to do it
right now.

The reason I'm asking is that quite a few programs (most notably
ipfw) spit countless messages to kernel msgbuf, thus overwriting any other
important info.

Is there any interest among people to implement such feature?

Andrzej Bialecki

//  [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com)
// ---
// -- FreeBSD: The Power to Serve. http://www.freebsd.org 
// --- Small  Embedded FreeBSD: http://www.freebsd.org/~picobsd/ 




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



CMOS clock won't do 2000

2000-02-12 Thread Brian Beattie

I have an older 486 system, running 3.4R that has a cmos clock that seems
to be unwilling to accept years out side the range 94-99.  The bios seems
willing to set dates between 1994-2099, but after reboot any year not
between 94-99 is converted to {20,19}94.

What I have done is to go into i386/isa/clock.c and in the routines
inittodr, resettodr, is to add 6 to and subtract 6 from the years
respectively.  I was wondering if anybody had any better ideas.

Brian Beattie| The only problem with
[EMAIL PROTECTED]  | winning the rat race ...
www.aracnet.com/~beattie | in the end you're still a rat



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



Re: rpc.lockd

2000-02-12 Thread Doug White

First of all, don't crosspost to both -hackers and -current.  They tend to
cover the same audience.

On Fri, 11 Feb 2000, David E. Cross wrote:

 I realize that we are all very busy and the coming 4.0-RELEASE has also
 compounded things, but I have heard nothing back on the rpc.lockd that
 was released just a short time ago.  I take it no news is good news and
 we can start the process of bringing it into the source tree? :)

4.0-RELEASE is in code freeze, so it won't make in there.  I suspect
someone will be available to get it into -CURRENT after 4.0 ships.

Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED] |  www.FreeBSD.org



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



A can ping C, but not B

2000-02-12 Thread Leif Neland

I got 4 machines at home on an Ethernet coax.
A-B-C-D.
B is FreeBSD server (samba), the rest is win98 (C is split win/fbsd).

C and D talks fine to B. A talks nicely to C (haven't tried to D), but very poorly to 
B. 
I got ping losses of 1 out of 3 to 4 from A to B, but no loss A to C.

I then took the T-plug from A and put it on a hub, and UTP from hub to A.
Still 100% from A to C, but now no ping at all from A to B!

What's going on? Standing waves? I got proper terminators either end.

The cable is assembled of well 10 shorter pieces with "empty" T-plugs, could that be a 
problem?

Leif




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



Re: CMOS clock won't do 2000

2000-02-12 Thread Wes Peters

Brian Beattie wrote:
 
 I have an older 486 system, running 3.4R that has a cmos clock that seems
 to be unwilling to accept years out side the range 94-99.  The bios seems
 willing to set dates between 1994-2099, but after reboot any year not
 between 94-99 is converted to {20,19}94.
 
 What I have done is to go into i386/isa/clock.c and in the routines
 inittodr, resettodr, is to add 6 to and subtract 6 from the years
 respectively.  I was wondering if anybody had any better ideas.

Is the clock chip socketed?  Are BIOS updates available for the motherboard?

-- 
"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-hackers" in the body of the message



Re: CMOS clock won't do 2000

2000-02-12 Thread Peter Wemm

Brian Beattie wrote:
 I have an older 486 system, running 3.4R that has a cmos clock that seems
 to be unwilling to accept years out side the range 94-99.  The bios seems
 willing to set dates between 1994-2099, but after reboot any year not
 between 94-99 is converted to {20,19}94.
 
 What I have done is to go into i386/isa/clock.c and in the routines
 inittodr, resettodr, is to add 6 to and subtract 6 from the years
 respectively.  I was wondering if anybody had any better ideas.

Also watch out for day-of-month and day-of-week calulations done in the
cmos chip.  It's a shame you couldn't set it for 1972 which matches the
year 2000 date, day, and leap year sequences exactly.

Cheers,
-Peter



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



Re: My views on Eclipse/BSD

2000-02-12 Thread Peter Wemm

"Daniel C. Sobral" wrote:
 Peter Wemm wrote:
  
  One key thing to keep in mind is that copyrights apply automatically
  regardless of age, contracts etc.  You have no right to copy a copyrighted
  work unless the right to do so is given to you (or you have statutory
  rights such as making backups etc).  In this case, you don't have the right
  to redistribute it except those granted by the license with it's
  conditions.  If you don't accept the license or cannot because you're under
  the age of being able to enter into a contract or whatever, then you can't
  redistribute it *period*.  You can download it (they are distributing it,
  not you), and do pretty much whatever you like with it once they've given
  it to you, but you can't give it to anyone else.  This means that if you
  were under 18 etc, you probably could use it for commercial purposes if you
  believed the license didn't apply.  (And Lucent/whoever *do* own the
  copyright on the additional Eclipse stuff).
 
 So... basically... you can't redistribute GPL code unless law permits
 you to enter contracts? How funny... :-)

It depends on whether you consider a redistribution license a contract or
not. If it says somthing to the effect of "in order to redistribute this,
these are the conditions you must follow", that's not necessarily a
contract.  You don't have any obligations, unless you want the right to
distribute it.

However, if it's a "click here to accept" in order to download something,
then thats closer to a contract as it's getting you to accept obligations
regardless of whether you distribute it or not.  This covers things like
"no commercial use" and so on.  You can generally only impose restrictions
on *usage* via some sort of contract.

The GPL is very much the former.  You can pretty much do whatever you damn
well please with it and have absolutely no obligations.  But to get the
right to distribute the copyrighted code (or derivatives), then the license
spells out the conditions under which you can distribute it.  The BSD
license is similar - you don't have any obligations unless you want to
distribute it.

Cheers,
-Peter



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



Re: bonnie still trustable?

2000-02-12 Thread Greg Lehey

On Friday, 11 February 2000 at 10:49:24 +0100, Christoph Kukulies wrote:
 PIII/500, 128 MB

 I'm wondering if this is trustable:

 bonnie -s 400
 File './Bonnie.14321', size: 419430400
 Writing with putc()...done
 Rewriting...done
 Writing intelligently...done
 Reading with getc()...done
 Reading intelligently...done
 Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done...
   ---Sequential Output ---Sequential Input-- --Random--
   -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks---
 MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU  /sec %CPU
   400 20015 73.7 18369 22.9  6750 12.6 22308 81.5 22467 26.0  93.8  1.0
  
 ?


 wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ff on isa
 wdc0: unit 0 (wd0): IBM-DPTA-372050, DMA, 32-bit, multi-block-16
 wd0: 19574MB (40088160 sectors), 39770 cyls, 16 heads, 63 S/T, 512 B/S

There are lies, damn lies, and statistics.  I'm sure that the results
mean something; the real question is, what do you want them to mean?

If you're trying to measure the storage device, rawio (Ports
Collection) is a much better choice.

Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers


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