ed?

1999-07-27 Thread Alexey M. Zelkin
Hello ! I am running CURRENT from 27 jul. So, I have PCI PnP Ethernet Adaptor and wrote in kernel config: > controller pnp0 > device ed0 at isa? disable port 0x280 irq 10 iomem 0xd8000 As usually this string included ethernet driver code into kernel and my card was found automaticly. But this

Re: Patch for Alpha/AXP

1999-07-27 Thread John-Mark Gurney
Kazutaka YOKOTA scribbled this message on Jul 24: > > >> I am afraid this is not quite right. > >> > >> Bruce, Doug and I are currently in discussion to fix this. > > > >Hrm. Why does the AXP cons.c track udev_t while the x86 verson > >doesn't? As best as I can tell, the AXP doesn't seem to ne

Re: PLIP is still broken :(

1999-07-27 Thread Garrett Wollman
< said: > This is also something that should be changed since we are to modify > things anyway, it introduces un-needed delays (and jitter) in the > interrupt delivery. Plus, the resource manager has built-in hooks to manage resources which are time-shared by multiple devices. (The thing it's l

diskless booting broken

1999-07-27 Thread Andrew Gallatin
Diskless (BOOTP_NFSROOT,NFS_ROOT) booting appears to be broken in -current. (at least on alpha, haven't tried x86): net0:> boot kernel.de1 /kernel.de1 data=0x261540+0x253f8 syms=[0x8+0x30ae0+0x8+0x232eb] Entering kernel.de1 at 0xfc325c80... Copyright (c) 1992-1999 The FreeBSD Project. Co

Re: MAKEDEV (or sh?) broken

1999-07-27 Thread Brian F. Feldman
Actually, all recursive executions of it need to be -x too. The easiest way (if there's no environment variable for it, I don't recall), is to put "set -x" at the top of MAKEDEV. This will help, and then I'll understand much more. Thanks. I have a feeling it might be improper optimization breakin

Need help testing mods to nos-tun

1999-07-27 Thread Nick Johnson
I've made a few modifications to nos-tun in an attempt to make it a bit more robust and also to give it the ability to adapt to a link with an IP address that may change while the tunnel is up. I'd like to share my modifications with the rest of the community but... ...I lack sufficient faciliti

Library question/challenge

1999-07-27 Thread Jeroen Ruigrok/Asmodai
[ in case this should've been -questions, please redirect this thread there ] Hi, after a make world on the 26th I tried to start netscape today and got a library error: /usr/libexec/ld.so: warning: /usr/lib/libc.so.3: minor version -1 older than expected 0, using it anyway ld.so failed: bad

Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms

1999-07-27 Thread NT Workstation User
Ummm, I'm not sure whether tar files count. See the 2GB file limit under Linux comes from the maximum value of a 32bit signed integer. Because the file system calls use those 32bit integers a file's size is limited to 2GB, at least if you want random access. tar files generally aren't accessed

Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms

1999-07-27 Thread Joe Gleason
I am uncertain about the emulation issues, but I know my backup tar files often exceed 4GB on x86 systems. I have done this with versions FreeBSD 2.2.2-3.2. I have never heard it mentioned before, so I assume it works on all versions. Probably a UFS thing. Joe Gleason Tasam > I am having a pec

Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms

1999-07-27 Thread NT Workstation User
I forgot, please forward a copy of any responses to my email address as I am not a member of any of these lists. - Original Message - From: NT Workstation User <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> S

Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms

1999-07-27 Thread NT Workstation User
I am having a pecular problem trying to run SCO binaries under the iBCS emulation in Linux. I figure the problem may be related to Linux lacking the necesary functionality to support files larger than 2GB which this SCO binary supports. I was thinking of trying freeBSD with its SCO emulation sup

Re: [Fwd: Tun interface related panic]

1999-07-27 Thread Maxim Sobolev
Brian Somers wrote: > > Brian Somers wrote: > > > > > Ok, I found the culprit in ppp. I'm committing a change now. > > > > > > Thanks for the report ! > > > > It seems that have found other culpit, because I'm continuing to see "Error: >ip_Input: > > deflink: wrote 0, got Input/output error" (3

Re: [Fwd: Tun interface related panic]

1999-07-27 Thread Brian Somers
> Brian Somers wrote: > > > Ok, I found the culprit in ppp. I'm committing a change now. > > > > Thanks for the report ! > > It seems that have found other culpit, because I'm continuing to see "Error: >ip_Input: > deflink: wrote 0, got Input/output error" (3.2-STABLE) even using ppp cvsup'ed

Re: [Fwd: Tun interface related panic]

1999-07-27 Thread Maxim Sobolev
Brian Somers wrote: > Ok, I found the culprit in ppp. I'm committing a change now. > > Thanks for the report ! It seems that have found other culpit, because I'm continuing to see "Error: ip_Input: deflink: wrote 0, got Input/output error" (3.2-STABLE) even using ppp cvsup'ed and builded today

coda in STABLE

1999-07-27 Thread Joe Abley
Hi, >From /sys/coda/coda.h on 3.2-STABLE, it looks like the version in the tree is 3.1. At http://www.coda.cs.cmu.edu/download.html#gpl_notice it is mentioned that version 5 clients and servers are not backwards compatible with version 4 (and by inference, previous versions, hence my first parag

Re: MAKEDEV (or sh?) broken

1999-07-27 Thread Maxim Sobolev
Philipp Mergenthaler wrote: > Hi, > > On Tue, Jul 27, 1999 at 01:20:55PM +0300, Maxim Sobolev wrote: > > On my CURRENT system cvsup'ed and builded yesterday when I'm trying to > > do "cd /dev; sh MAKEDEV all" I see following errors: > > > > Script started on Tue Jul 27 13:14:47 1999 > > sh-2.

Re: MAKEDEV (or sh?) broken

1999-07-27 Thread Maxim Sobolev
Here it is. -Maxim Script started on Tue Jul 27 15:34:02 1999 sh-2.03# sh -x MAKEDEV da0 + PATH=/sbin:/bin/:/usr/bin:/usr/sbin:/usr/local/bin:/sbin:/usr/sbin:/usr/local/sbin:/bin:/usr/bin:/usr/X11R6/bin + umask 77 + dkrawpart=2 + dkcompatslice=0 + dkrawslice=1 + disk_umask=037 + tape_umask=017

Re: MAKEDEV (or sh?) broken

1999-07-27 Thread Brian F. Feldman
Isolate a specific case of MAKEDEV (not just all) that will demonstrate this, sh -x it, and send it to me. Failing that, set -x and do ./MAKEDEV all, and send me this output. That's where we need to go next to try to find out what is wrong. Brian Fundakowski Feldman _ __ ___ ___ ___ _

Re: MAKEDEV (or sh?) broken

1999-07-27 Thread Maxim Sobolev
"Brian F. Feldman" wrote: > On Tue, 27 Jul 1999, Maxim Sobolev wrote: > > > On my CURRENT system cvsup'ed and builded yesterday when I'm trying to > > do "cd /dev; sh MAKEDEV all" I see following errors: > > Did you somehow replace Bourne with BASH? Check. No, in any way I didn't replaced it (ye

Re: MAKEDEV (or sh?) broken

1999-07-27 Thread Brian F. Feldman
On Tue, 27 Jul 1999, Maxim Sobolev wrote: > On my CURRENT system cvsup'ed and builded yesterday when I'm trying to > do "cd /dev; sh MAKEDEV all" I see following errors: Did you somehow replace Bourne with BASH? Check. > > Script started on Tue Jul 27 13:14:47 1999 > sh-2.03# cd /dev ; sh MAKE

MAKEDEV (or sh?) broken

1999-07-27 Thread Maxim Sobolev
On my CURRENT system cvsup'ed and builded yesterday when I'm trying to do "cd /dev; sh MAKEDEV all" I see following errors: Script started on Tue Jul 27 13:14:47 1999 sh-2.03# cd /dev ; sh MAKEDEV all MAKEDEV: arith: syntax error: "?† ž† " usage: mknod name [b | c] major minor /sbin/mknod da0

Re: aio and fd patches

1999-07-27 Thread John-Mark Gurney
Mike Smith scribbled this message on Jul 27: > > > > I'm interested in finding someone to help me get the aio patches I've > > written committed into -current. These fixes make the aio routines much > > more useful for io on sockets than they are now (each io op on a socket > > blocks an aiod).

Re: aio and fd patches

1999-07-27 Thread Mike Smith
> > I'm interested in finding someone to help me get the aio patches I've > written committed into -current. These fixes make the aio routines much > more useful for io on sockets than they are now (each io op on a socket > blocks an aiod). This is a bit of a work in progress, but I've been > r