ed?

[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 time I pointed my
eyes to dmesg output and found interesting thing:

> ed0:  irq 12 at device 9.0 on pci0
> ed0: address 00:00:21:c7:5b:a7, type NE2000 (16 bit) 
> devclass_alloc_unit: ed0 already exists, using next available unit number
> isa0:  on motherboard
> ed1: not probed (disabled)

So, what should do kernel when I insert new ISA ethernet into my machine and
enable ed0 ? Logic tells that ed0 will change its name to ed1, and
new card will stay ed0.

Why my pnp ethernet was found as ed0 but not ed1 ?

So, I would ask -- is this feature or bug ? If I am temporary changing my
network devices configuration can I be sure that ethernet names will not
be automaticly changed ?

-- 
Sincerely Yours,   | [EMAIL PROTECTED]  (primary)
Alexey Zelkin  | [EMAIL PROTECTED] (home)
   | ICQ: #6196584,  FIDO: 2:460/12.26


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

Re: Patch for Alpha/AXP

[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 need it any
> >more than the x86 does, unless I've missed something.
> 
> As dev_t is now a struct, we cannot track dev_t for SYSCTL.  It has to
> be udev_t.  sys/i386/i386/cons.c should be doing the same as the alpha
> version, rather than vice versa.  
> 
> To quote Bruce: "alpha/alpha/cons.c should be identical with
> i386/i386/cons.c and not in a machine-dependent place.  All current
> differences are bugs" :-)

hmmm.. guess it's time for me to bring out my MI cons.c that I did a
long time ago and dust it off??  Bruce kinda vetoed it, but I also didn't
have the courage to commit it back then...  and it's not hard to make
it MI

-- 
  John-Mark Gurney  Voice: +1 541 684 8449
  Cu Networking   P.O. Box 5693, 97405

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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

Re: PLIP is still broken :(

[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 lacking,
but ought to have, is a ``gang'' notion to claim several resources at
once.)

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED]  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick


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

diskless booting broken

[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.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #1: Tue Jul 27 14:46:14 EDT 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/BOOTP
AlphaStation 500 or 600 (KN20AA)
<.snip...>
bootpc_init: wired to interface 'de1'
bootpc_init: using network interface 'de1'
Bootpc testing starting
bootpc hw address is 0:0:f8:0:xx:yy
My ip address is 152.3.x.y
Server ip address is 152.3.x.y
Gateway ip address is 0.0.0.0
Server name is xxx.cs.duke.edu
boot file is /freebsd/diskless.alpha/boot/netboot
Subnet mask is 255.255.0.0
rootfs is 152.3.x.y:/freebsd/diskless.alpha
rootdev=0x error=6,  panic: cannot mount root (2)

panic
Stopped at  Debugger+0x2c:  ldq ra,0(sp) <0xfc5e3ca0>   



The rootdev is never set, so the mount is never attempted in
vfs_mountrootfs. 

The appended hack (in the spirit of the first MFS_ROOT fix by John
Birrell) seems to fix it temporarily.  Can somebody with a clue please
look into this?

Thanks,

Drew

--
Andrew Gallatin, Sr Systems Programmer  http://www.cs.duke.edu/~gallatin
Duke University Email: [EMAIL PROTECTED]
Department of Computer Science  Phone: (919) 660-6590


Index: vfs_conf.c
===
RCS file: /home/ncvs/src/sys/kern/vfs_conf.c,v
retrieving revision 1.31
diff -u -b -B -c -r1.31 vfs_conf.c
cvs diff: conflicting specifications of output style
*** vfs_conf.c  1999/07/03 17:40:31 1.31
--- vfs_conf.c  1999/07/27 21:17:31
***
*** 134,140 
return ;
}
mp->mnt_flag|= MNT_ROOTFS;
! 
/*
 * Attempt the mount
 */
--- 134,142 
return ;
}
mp->mnt_flag|= MNT_ROOTFS;
! #if defined (BOOTP_NFSROOT) || defined (NFS_ROOT)
!   err = VFS_MOUNT(mp, NULL, NULL, NULL, p);
! #else 
/*
 * Attempt the mount
 */
***
*** 158,163 
--- 160,166 
if (err != ENXIO)
break;
}
+ #endif
if (err) {
/*
 * XXX should ask the user for the name in some cases.


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

Re: MAKEDEV (or sh?) broken

[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 breaking expr...

 Brian Fundakowski Feldman  _ __ ___   ___ ___ ___  
 [EMAIL PROTECTED]   _ __ ___ | _ ) __|   \ 
 FreeBSD: 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

Need help testing mods to nos-tun

[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 facilities for testing my changes thoroughly.  If
you're interested, please take a look at http://www.spatula.net/nos-tun/
and see if it is now hopelessly broken.  I'm especially interested in
getting anyone who may already be using nos-tun and anyone who is using it
across platforms to test my changes.

More documentation about my changes can be found at the URL above, along
with diffs & source code.

Please send any feedback to me so I can correct any problems before doing
a send-pr with the enhancements, thereby avoiding my looking like a
complete imbecile.

   Nick

--
"Unlike me, many of you have accepted the situation of your imprisonment 
 and will die here like rotten cabbages!"
 - Number-6, "The Prisoner: Free For All"
My PGP public key:http://www.spatula.net/pubkey.txt
Nick Johnson, version 1.5   http://www.spatula.net/



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

Library question/challenge

[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 magic number in "/usr/lib/libc.so.3"

This is netscape4.5 on CURRENT tracked since October 1998.

One change since my previous builds is that I uncommented compat22 and 
compat3x prior to making world.

I have the default aout ld path in /etc/defaults/rc.conf, none in 
/etc/rc.conf.

A ldconfig -aout -r | head -2 yields:

/var/run/ld.so.hints:
search directories: /usr/lib/aout:/usr/lib/compat/aout:
/usr/X11R6/lib/aout:/usr/local/lib/aout

[ it has about 66 libs in this hints file ]

I also get the above error when trying to install a newer netscape.

Can it be I need to rebuild my XFree? I currently run 3.3.3.1 compiled
under ELF and with a.out support AFAIK, else I couldn't have been
running netscape before. Timestamp of /usr/X11r6/lib/aout is July 21st.

/usr/lib/aout is dated March 20th
/usr/lib/compat/aout is July 26th
/usr/local/lib/aout is empty

Anything you guys can think of, want to inspect, want me to test, because
I cannot see where it goes wrong exactly.

Thanks,

-- 
Jeroen Ruigrok van der Werven  asmodai(at)wxs.nl
The BSD Programmer's Documentation Project 
Network/Security SpecialistBSD: Technical excellence at its best
Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...?


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

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

[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 in
a random access fashion, instead the file is treated as a byte stream.
Though I can't remember exactly, I think I created (> 2GB) tar files under
Linux once too.  I know SCO and other commercial OSes have addition file
functions for large files which use 64bit integers to overcome this
limitation.  As Linux lacks this feature I am considering giving freeBSD (or
any of the other BSDs) a try.  Of course this leaves me wondering whether to
try the pre-4.0 or the 3.2 version.

- Original Message -
From: Joe Gleason <[EMAIL PROTECTED]>
To: NT Workstation User <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, July 27, 1999 4:05 PM
Subject: Re: Does freeBSD or any related freeBSDs support file larger than
2GB on 32bit x86 platforms


> 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 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
> > support but I am uncertain whether freeBSD supports files larger than
2GB
> on
> > 32bit x86 platforms.  Anybody know the answer to this question.  Also if
> > only a peticular version supports it, let me know so I can get the
correct
> > version.  The program that I am trying to get to run under freeBSD or
> Linux
> > is the Microfocus cobol runtime.  Everything else in that COBOL
> development
> > package works except the actual runtime, which just happens to support
> large
> > files (> 2GB) for the COBOL databases.  This is why I fugure its dying
> under
> > Linux, so does freeBSD on 32bit x86 platforms support files > 2GB?
> >
> >
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-stable" in the body of the message
> >
>




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

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

[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 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
> support but I am uncertain whether freeBSD supports files larger than 2GB
on
> 32bit x86 platforms.  Anybody know the answer to this question.  Also if
> only a peticular version supports it, let me know so I can get the correct
> version.  The program that I am trying to get to run under freeBSD or
Linux
> is the Microfocus cobol runtime.  Everything else in that COBOL
development
> package works except the actual runtime, which just happens to support
large
> files (> 2GB) for the COBOL databases.  This is why I fugure its dying
under
> Linux, so does freeBSD on 32bit x86 platforms support files > 2GB?
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
>



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

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

[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]>
Sent: Tuesday, July 27, 1999 3:54 PM
Subject: Does freeBSD or any related freeBSDs support file larger than 2GB
on 32bit x86 platforms


> 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
> support but I am uncertain whether freeBSD supports files larger than 2GB
on
> 32bit x86 platforms.  Anybody know the answer to this question.  Also if
> only a peticular version supports it, let me know so I can get the correct
> version.  The program that I am trying to get to run under freeBSD or
Linux
> is the Microfocus cobol runtime.  Everything else in that COBOL
development
> package works except the actual runtime, which just happens to support
large
> files (> 2GB) for the COBOL databases.  This is why I fugure its dying
under
> Linux, so does freeBSD on 32bit x86 platforms support files > 2GB?
>
>




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

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

[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
support but I am uncertain whether freeBSD supports files larger than 2GB on
32bit x86 platforms.  Anybody know the answer to this question.  Also if
only a peticular version supports it, let me know so I can get the correct
version.  The program that I am trying to get to run under freeBSD or Linux
is the Microfocus cobol runtime.  Everything else in that COBOL development
package works except the actual runtime, which just happens to support large
files (> 2GB) for the COBOL databases.  This is why I fugure its dying under
Linux, so does freeBSD on 32bit x86 platforms support files > 2GB?




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

Re: [Fwd: Tun interface related panic]

[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.2-STABLE) even using ppp cvsup'ed and 
>builded
> > today.
>
> I've fixed it in -current, not yet in -stable.  You could try the
> latest ppp archive from my web site if you want to confirm whether
> or not the fix works.

No, you misunderstood me. I'm usually using on my 3.2 box the ppp compiled from the 
current
sources of 4.0 (BTW ppp from 3.2 doesn't have this bug). When I've wrote that sources 
was
cvsup'ed today I mean 4.0 sources not 3.2.

-Maxim
--
"We believe in the Power and the Might!"
(Manowar, 1996)

Maxim V. Sobolev, Financial Analyst,
Vega International Capital
Phone: +380-(44)-246-6396
Fax: +380-(44)-220-8715
E-mail: [EMAIL PROTECTED]
ICQ: #42290709





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

Re: [Fwd: Tun interface related panic]

[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 and 
>builded
> today.

I've fixed it in -current, not yet in -stable.  You could try the 
latest ppp archive from my web site if you want to confirm whether 
or not the fix works.

> -Maxim

-- 
Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
     <[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: [Fwd: Tun interface related panic]

[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.

-Maxim



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

coda in STABLE

[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
paragraph). Earlier on the same page, -CURRENT is mentioned, but not -STABLE.

Does -CURRENT have different kernel hooks for coda than -STABLE? If so,
does anybody know if work is progressing to back-port the changes?

If anybody has any general experience of coda on FreeBSD, and feels like
sharing it, I'm keen to listen :)


Joe


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

Re: MAKEDEV (or sh?) broken

[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.03# cd /dev ; sh MAKEDEV all
> > MAKEDEV: arith: syntax error: "?† ž† "
>
> I saw a similar error ("arith:") once when I had compiled /bin/sh
> with high optimization (ok, that was with gcc, not egcs).
> So, as a wild guess, maybe you did use some high optimization
> and hit a bug in egcs?

No, I'm not using high optimisation (I think my -O2 can be considered
relatively safe). But to check for shure I've recompilled sh with -O and it
yeld exctly the same result as it was with -O2.

-Maxim
--
"We believe in the Power and the Might!"
(Manowar, 1996)

Maxim V. Sobolev, Financial Analyst,
Vega International Capital
Phone: +380-(44)-246-6396
Fax: +380-(44)-220-8715
E-mail: [EMAIL PROTECTED]
ICQ: #42290709





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

Re: MAKEDEV (or sh?) broken

[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
+ umask 037
+ name=da
+ blk=4
+ chr=13
+ expr da0 : ..\(.*\)
+ unit=0
+ sh MAKEDEV da0s0h
MAKEDEV: arith: syntax error: "?† ž† "

usage: mknod name [b | c] major minor
/sbin/mknod da0b
+ sh MAKEDEV da0s1
+ sh MAKEDEV da0s2
+ sh MAKEDEV da0s3
+ sh MAKEDEV da0s4
+ umask 77
sh-2.03# sh -x MAKEDEV da0s0h
+
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
+ umask 037
+ name=da
+ blk=4
+ chr=13
+ expr da0s0h : ..\([0-9]*\)s
+ unit=0
+ expr da0s0h : ..[0-9]*s\([0-9]*\)
+ slice=0
+ expr da0s0h : ..[0-9]*s[0-9]*\(.*\)
+ part=h
+ oldslice=0
+ slice=1
+ dkitos 1
+ local s
+ s=
+ echo
+ slicename=
+ dkminor 0 0 1 2
+ echo 65538
+ minor=65538
+ mknod da0 b 4 65538
+ rm -f da0
+ /sbin/mknod da0 b 4 65538
+ chown root.wheel da0
+ mknod rda0 c 13 65538
+ rm -f rda0
+ /sbin/mknod rda0 c 13 65538
+ chown root.wheel rda0
+ slice=0
+ dkminor 0 0 0 0
+ echo 0
+ minor=0
+ dkitop 0
+ local p
+ p=a
+ echo a
+ partname=a
+ mknod da0a b 4 0
+ rm -f da0a
+ /sbin/mknod da0a b 4 0
+ chown root.wheel da0a
+ mknod rda0a c 13 0
+ rm -f rda0a
+ /sbin/mknod rda0a c 13 0
+ chown root.wheel rda0a
+ dkminor 0 0 0 1
MAKEDEV: arith: syntax error: "?† ž† "

+ minor=
+ dkitop 1
+ local p
+ p=b
+ echo b
+ partname=b
+ mknod da0b b 4
+ rm -f da0b
+ /sbin/mknod da0b b 4
usage: mknod name [b | c] major minor
+ die 2 /sbin/mknod da0b b 4 failed
+ echo /sbin/mknod da0b
/sbin/mknod da0b
+ exit 2
sh-2.03# exit

Script done on Tue Jul 27 15:34:56 1999





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

Re: MAKEDEV (or sh?) broken

[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  _ __ ___   ___ ___ ___  
 [EMAIL PROTECTED]   _ __ ___ | _ ) __|   \ 
 FreeBSD: 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: MAKEDEV (or sh?) broken

[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 (yesterday I installed fresh word and
since that I'm not undertake any activity which might replace /bin/sh):

Script started on Tue Jul 27 14:26:45 1999
sh-2.03# which sh
/bin/sh
sh-2.03# ls -l /bin/sh
-r-xr-xr-x  1 root  wheel  349808 Jul 26 19:05 /bin/sh
sh-2.03# exit

As you can see paths is right and /bin/sh is not a symlink. Mergemaster
yields similar results, so it can't be my local MAKEDEV fault.

-Maxim
--
"We believe in the Power and the Might!"
(Manowar, 1996)

Maxim V. Sobolev, Financial Analyst,
Vega International Capital
Phone: +380-(44)-246-6396
Fax: +380-(44)-220-8715
E-mail: [EMAIL PROTECTED]
ICQ: #42290709





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

Re: MAKEDEV (or sh?) broken

[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 MAKEDEV all
> ...
> Script done on Tue Jul 27 13:16:57 1999
> 
> -Maxim
> --
> "We believe in the Power and the Might!"
> (Manowar, 1996)
> 
> Maxim V. Sobolev, Financial Analyst,
> Vega International Capital
> Phone: +380-(44)-246-6396
> Fax: +380-(44)-220-8715
> E-mail: [EMAIL PROTECTED]
> ICQ: #42290709
> 
> 
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 

 Brian Fundakowski Feldman  _ __ ___   ___ ___ ___  
 [EMAIL PROTECTED]   _ __ ___ | _ ) __|   \ 
 FreeBSD: 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

MAKEDEV (or sh?) broken

[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 da0b
MAKEDEV: arith: syntax error: "?† ž† "

usage: mknod name [b | c] major minor
/sbin/mknod da1b
MAKEDEV: arith: syntax error: "?† ž† "

usage: mknod name [b | c] major minor
/sbin/mknod da2b
MAKEDEV: arith: syntax error: "?† ž† "

usage: mknod name [b | c] major minor
/sbin/mknod da3b
MAKEDEV: arith: syntax error: "¶† "

usage: mknod name [b | c] major minor
/sbin/mknod wd0b
MAKEDEV: arith: syntax error: "¶† "

usage: mknod name [b | c] major minor
/sbin/mknod wd1b
MAKEDEV: arith: syntax error: "?† ¶† "

usage: mknod name [b | c] major minor
/sbin/mknod wd2b
MAKEDEV: arith: syntax error: "?† ¶† "

usage: mknod name [b | c] major minor
/sbin/mknod wd3b
MAKEDEV: arith: syntax error: "?† ž† "

usage: mknod name [b | c] major minor
/sbin/mknod od0b
MAKEDEV: arith: syntax error: "µ† ?† "

usage: mknod name [b | c] major minor
/sbin/mknod wfd0b
MAKEDEV: arith: syntax error: "?† ž† "

usage: mknod name [b | c] major minor
/sbin/mknod vn0b
sh-2.03# exit

Script done on Tue Jul 27 13:16:57 1999

-Maxim
--
"We believe in the Power and the Might!"
(Manowar, 1996)

Maxim V. Sobolev, Financial Analyst,
Vega International Capital
Phone: +380-(44)-246-6396
Fax: +380-(44)-220-8715
E-mail: [EMAIL PROTECTED]
ICQ: #42290709





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

Re: aio and fd patches

[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).  This is a bit of a work in progress, but I've been
> > running these patches here for over a month with good performance and
> > no new detriment to stability.  There should be no stability impact on
> > code which doesn't utilize aio routines.
> > 
> > I'm also interested in whether anyone is working to get the patches from
> > Ville-Pertti Keinonen for file descriptor referencing committed.  These
> > are important for aio and other more critical subsystems.
> > 
> > You can see my report of issues in kern/12053.  I somehow managed to
> > include a mangled and outdated version of the patch with that report, so
> > that patch shouldn't be integrated.  An updated patch is available at
> > http://tfeed.maxwell.syr.edu/aio-diff
> 
> If someone else running each of these patch sets is willing to vouch 
> for their direct applyability to -current and their ongoing 
> functionality, I'll commit them immediately.
> 
> Sorry that your work has been basically ignored; it looks like there 
> are no committers actively working on this right now.

I have been meaning to look at these patches, it's just that I haven't
had a -current box to do testing on, but soon (like the end of the
week), I should have a box that I can do testing, and if so, I'll make
sure that these function, and if so, commit them...

-- 
  John-Mark Gurney  Voice: +1 541 684 8449
  Cu Networking   P.O. Box 5693, 97405

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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

Re: aio and fd patches

[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
> running these patches here for over a month with good performance and
> no new detriment to stability.  There should be no stability impact on
> code which doesn't utilize aio routines.
> 
> I'm also interested in whether anyone is working to get the patches from
> Ville-Pertti Keinonen for file descriptor referencing committed.  These
> are important for aio and other more critical subsystems.
> 
> You can see my report of issues in kern/12053.  I somehow managed to
> include a mangled and outdated version of the patch with that report, so
> that patch shouldn't be integrated.  An updated patch is available at
> http://tfeed.maxwell.syr.edu/aio-diff

If someone else running each of these patch sets is willing to vouch 
for their direct applyability to -current and their ongoing 
functionality, I'll commit them immediately.

Sorry that your work has been basically ignored; it looks like there 
are no committers actively working on this right now.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




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